Related
Official updates for our M2 tablet,
although having installed another
recovery and root access, already.
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about ADB and flashing, which is explained in many other
threads here on our beloved XDA.
- Issue
When you used this guide (https://goo.gl/r04XjJ) or any other one to give your M2 tablet
another recovery and therefore root rights, you have now the problem, that EMUI will show
you new updates, but you are not able to install them, because of the missing stock recovery,
of course.
- Solution
So, you have to flash back the original stock recovery, getting the official update and then you
can flash back your TWRP recovery.
- Guide
1. You should start your EMUI update programme/app and start the download of your update.
When it is finished, it will ask you to reboot into recovery and install automatically. As you have
no stock recovery I strongly advise not to do so. Usually nothing happens, but there is one case
reported, where it somehow ****ed up the guy's tablet. I am not sure, if that story is true, but
well, I have warned you.
2. Just turn your tablet off after you have finished downloading the update (it will wait now in
the directory "HwOUC" on your tablet and it is called "update.zip" - just let it sleep there).
3. Start the tablet in the fastboot recovery mode, meaning plugging in the USB cable (connected
to the computer) and hold the buttons "power" and "volume down", immediately, until a white
screen appears, which is the fastboot recovery screen. It should tell you, it has the bootloader
unlocked, which is normal, because you did that earlier on with any of the other guides (see above).
4. Copy the downloaded stock recovery of your choice to your ADB directory. In my case this is
"c:\ADB", but this depends on your way of installation.
5. Now open up a command line in Windows (with Windows key + R) and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
6. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery stock-recovery.img
fastboot reboot
If you renamed the recovery file, then you have to consider that in the command, of course.
7. The device will reboot directly into the recovery, because it "sees" the update in the update
directory et voila ... you are getting your awaited update. Sometimes it will boot not into the EMUI
recovery directly, but then you hast have to start the tablet normally, open up the EMUI app and
download the update again and do the OTA update properly with the reboot it tells you to do,
when it is finished.
8. Okay, now you have received your update, but if you want to have back your TWRP, you just
have to turn off your tablet and boot into the fastboot recovery again (see 3.).
9. You have to copy your TWRP recovery to your ADB directory (in my case "twrp.img" in "c:\ADB").
10. Now open up a command line in Windows (with Windows key + R and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
11. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery twrp.img
fastboot reboot
12. The tablet will reboot and you are back to a working lovely updated M2 tablet.
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-802L and M2-A01L:
https://ufile.io/0df492 (all four recoveries here)
https://files.fm/u/aajdmadr (all four recoveries here)
https://www.file-upload.net/download-12438839/HuaweiM2recoveries.rar.html (all four recoveries here)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee appreciated.
...
..
.
+++ saved +++
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
what android version ?? M2-801L, thanks
Eagle-no1 said:
what android version ?? M2-801L, thanks
Click to expand...
Click to collapse
M2-A01L, not M2-801L. For all 8 models you find your ROMs here:
https://forum.xda-developers.com/me...om-8-0-models-stock-marshmallow-roms-t3535466
or
https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
or
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
xsycox said:
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
Click to expand...
Click to collapse
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Sent from my htc_pmeuhl using XDA Labs
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
5m4r7ph0n36uru said:
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
xsycox said:
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
Click to expand...
Click to collapse
After enabling magisk hide, you have to reboot your device. Got the 801L working with that and safetynet passes.
Noob Question on recovery files
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
myst771 said:
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
Click to expand...
Click to collapse
Sorry, I have been on vacation.
To be honest, I am not sure, if the recovery for M2-A01L works on M2-A01w, too, but you can just try it.
I think, there should not be that big a problem, because the recovery has nothing to do with Wi-Fi or LTE, at all. It is just important, that partition tables and drives are accessible the same way and well, I really think, there is not much difference in between the M2 10 models.
From M2 8 to 10 there is a difference, of course. That is why I uploaded both recoveries (for 802L and A01L).
Just use that guide (https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340) without the SuperSU flashing and my recoveries in this guide.
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Shocker580 said:
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Click to expand...
Click to collapse
Could upload the B010 fullstock ROM/firmware. Thus you could reset the device to the latest stock ROM using the /dload method and gain a factory rested Huawei, as if out of the box. Just quote me if you'd want me to upload and I'll share the link asap. Took that way myself as soon as I found the full stock ROM.
Sent from my htc_ocnuhl using XDA Labs
thanx
Dear xsycox
I have an issue where I updated my W version tablet to L version accidentally and I am having issue getting it back..
I am currently trying to get some help in this thread: https://forum.xda-developers.com/me...-m2-installed-wrong-update-zip-t3563105/page2
Can you please help me out? do you have any idea what ican do to get back to W version?
Thanks!
So this is all thanks to @tomiga and developer of Magisk and Odin. I’m not even tryin to take any credit for any of this.
Also, it's a rough draft, let me know if things need to be changed or clarified, though I'm not intending to keep this updated in the future.
1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
2. Settings>about tablet>tap on build number to get into developer settings.
3. Check OEM unlock, tablet resets and erases everything
4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
9. Connected tab to PC, opened command prompt, adb reboot bootloader
10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
11. Hit “start” in Odin
12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
15. Open Magisk Manager, it says tablet isn’t rooted.
16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
17. Tab rebooted fine
18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
20. Reboot.
21. ???
22. Profit?
mistermojorizin said:
So this is all thanks to @tomiga and developer of Magisk and Odin. I’m not even tryin to take any credit for any of this.
Also, it's a rough draft, let me know if things need to be changed or clarified, though I'm not intending to keep this updated in the future.
1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
2. Settings>about tablet>tap on build number to get into developer settings.
3. Check OEM unlock, tablet resets and erases everything
4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
9. Connected tab to PC, opened command prompt, adb reboot bootloader
10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
11. Hit “start” in Odin
12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
15. Open Magisk Manager, it says tablet isn’t rooted.
16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
17. Tab rebooted fine
18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
20. Reboot.
21. ???
22. Profit?
Click to expand...
Click to collapse
What directory is fastboot and ADB in????
ScottBroker said:
What directory is fastboot and ADB in????
Click to expand...
Click to collapse
Honestly, I don't think the directory should matter as long as adb and fastboot are in your environmental variables. And if they aren't, then just open a terminal in the directory you DO have adb and fastboot in....and run the commands from there.
https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
ScottBroker said:
What directory is fastboot and ADB in????
Click to expand...
Click to collapse
I already had adb/fastboot setup on my PC for my other phones, but didn't have the Samsung drivers. I installed the android SDK at some point to get the adb and fastboot drivers. Note, that unlike all of my other android devices, the tab S4 didn't respond to fastboot commands (for example, "fastboot devices" command in bootloader/download mode didn't return anything, which was unexpected). But Odin recognized it in that mode. So this doesn't rely on using any fastboot commands, just ADB.
Thanks for making a more user-friendly guide. I was considering doing so myself but got caught up with a lot of other stuff, so much appreciated.
mistermojorizin said:
1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
2. Settings>about tablet>tap on build number to get into developer settings.
3. Check OEM unlock, tablet resets and erases everything
4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
9. Connected tab to PC, opened command prompt, adb reboot bootloader
10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
11. Hit “start” in Odin
12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
15. Open Magisk Manager, it says tablet isn’t rooted.
16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
17. Tab rebooted fine
18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
20. Reboot.
21. ???
22. Profit?
Click to expand...
Click to collapse
It should be possible to avoid the second system reset in step 12 by flashing a modified system.img with the offending package(s) removed.
tomiga said:
Thanks for making a more user-friendly guide. I was considering doing so myself but got caught up with a lot of other stuff, so much appreciated.
Click to expand...
Click to collapse
I was able to root my Tab S4, but now my camera does not work. I tried installin xposed, and it didnt work, so I did a factory data reset and now when I set it up it was still rooted, but the camera does not work. Any suggestions before I flash the stock firmware back to it?????
ScottBroker said:
I was able to root my Tab S4, but now my camera does not work. I tried installin xposed, and it didnt work, so I did a factory data reset and now when I set it up it was still rooted, but the camera does not work. Any suggestions before I flash the stock firmware back to it?????
Click to expand...
Click to collapse
It sounds as if the kernel you flashed isn't compatible with the vendor.img of the firmware that you're on.
The rooting procedure described here uses a modified boot.img that may now be too old for the updated firmware that a lot of us have since received on our devices.
If that's the issue, you will either need to downgrade your firmware to match the one your kernel was built against (flashing vendor.img from that version is probably sufficient), or upgrade your kernel to match the firmware you're running now. That will entail modifying the new boot image for root in the same way as the one you downloaded as part of the rooting process.
This is why, in spite of feeling tempted, I'm personally holding off on rooting this device until I or someone else gets TWRP working on it.
ianmacd said:
It sounds as if the kernel you flashed isn't compatible with the vendor.img of the firmware that you're on.
The rooting procedure described here uses a modified boot.img that may now be too old for the updated firmware that a lot of us have since received on our devices.
If that's the issue, you will either need to downgrade your firmware to match the one your kernel was built against (flashing vendor.img from that version is probably sufficient), or upgrade your kernel to match the firmware you're running now. That will entail modifying the new boot image for root in the same way as the one you downloaded as part of the rooting process.
This is why, in spite of feeling tempted, I'm personally holding off on rooting this device until I or someone else gets TWRP working on it.
Click to expand...
Click to collapse
I just reflashed the stock image and I am back to normal
ScottBroker said:
I just reflashed the stock image and I am back to normal
Click to expand...
Click to collapse
Which will also align your camera firmware with your kernel again, but now you don't have root, right?
ianmacd said:
Which will also align your camera firmware with your kernel again, but now you don't have root, right?
Click to expand...
Click to collapse
No, and I have the wifi version
ScottBroker said:
No, and I have the wifi version
Click to expand...
Click to collapse
I have both root and camera working fine. Only difference I can tell from your software version is under Build Number mine has t830XXU1ARGH. Have you disabled any apps by chance? On one of my phones camera would crash if i disabled NFC service.
mistermojorizin said:
I have both root and camera working fine. Only difference I can tell from your software version is under Build Number mine has t830XXU1ARGH. Have you disabled any apps by chance? On one of my phones camera would crash if i disabled NFC service.
Click to expand...
Click to collapse
His problem was almost certainly due to his having ARH5 firmware on the device (specifically the vendor.img component) but an ARH1 kernel. Such mismatches usually present themselves in the form of a non-functional camera.
After upgrading the firmware past ARH5, the new boot image should be rooted, rather than flashing the older one given in the rooting instructions of this thread.
Please also note that @ashyx has started work on TWRP and even released an initial test build for the T820. I intend to give that a try this afternoon when I get home.
Sent from my SM-G965F using XDA Labs
ianmacd said:
His problem was almost certainly due to his having ARH5 firmware on the device (specifically the vendor.img component) but an ARH1 kernel. Such mismatches usually present themselves in the form of a non-functional camera.
After upgrading the firmware past ARH5, the new boot image should be rooted, rather than flashing the older one given in the rooting instructions of this thread.
Please also note that @ashyx has started work on TWRP and even released an initial test build for the T820. I intend to give that a try this afternoon when I get home.
Sent from my SM-G965F using XDA Labs
Click to expand...
Click to collapse
Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....
ScottBroker said:
Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....
Click to expand...
Click to collapse
flashfire won't open. i went through something like this on my fire hd 10, had to install an xposed module to trick flashfire into thinking we're back in an older time and install a really old version of flashfire. Otherwise, the newer version of flashfire would just close/won't open.
hope this all settles down to a working version soon
ScottBroker said:
Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....
Click to expand...
Click to collapse
TWRP is on the way. @ashyx is working on it. This thread is tracking the progress.
ianmacd said:
TWRP is on the way. @ashyx is working on it. This thread is tracking the progress.
Click to expand...
Click to collapse
Exciting stuff ?
Will this work for LTE? I don't see the option to oem unlock on my Verizon version. Does that mean locked bootloader?
machx1111 said:
Will this work for LTE? I don't see the option to oem unlock on my Verizon version. Does that mean locked bootloader?
Click to expand...
Click to collapse
Most likely. Verizon normally make them unlockable
Hi all,
I am trying to update my phone for three days now. Samsung a3 2017 aka a320fl
my constraints:
I only have a linux laptop running sparky (debian derivate)
Windows work laptop with win 10
My windows laptop always deletes necessary files (anti virus scan) and there is nothing i can do about it.
So i switched to my linux.
What i did:
I can get access to the regular adb shell, fastboot would just reboot not get me into download mode
I get my phone into that download screen (vol down-power-home), but then no connection possible
I turned on oem unlock / usb debugging
I tried heimdall but missing some files and i suppose the connection is not setup right
I found a linux version for odin... still no luck error 71
some adb commands that i found rely on "su" which is not available yet
so basically i am stuck at the first step
I would want a newer os since my rom is too old. Android 7.0 and one of my apps need at least 7.1
I would try lineage 17. But there are plenty of steps that i cannot get to work. Like orange/bootloader/....
But first things first.
So is there any one that could help me with the very first step?
this is what i would like to use
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble]
LineageOS 17.x Unofficial for Galaxy A3 2017 LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Quack), which is designed to increase performance and reliability over stock Android for your device...
forum.xda-developers.com
i found odin here:
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
i already found them days ago, but no luck in going through the process
my prior phone was a galaxy s3 mini, on which i installed cyanogen (the one with android 5, the newer ones were not really stable back then)
i have a a3 2017 with stock rom android 7.0 (not branded) and rooted.
now i was afraid of losing data while updating and got me a new a3 2017 to basically play around and test the install process. this one already has android 8.0.
but both of them are bloated as hell...
so my hopes:
- support the apps i like (sportractive in particular), it does not support android 7.0 anymore
- better battery life (i found that android 7.0 is not the best in dealing with bad cellular service, i have to switch to 2g manually to get me throug the day, 4g consumes over 100mA in standby)
- i would want to keep my message history of whatsapp and signal
- i bought drift racers(https://www.sturmkind-shop.com/dr-ft-racer-kaufen/), which would not work with my android 7.0
so no one that has ever done the rooting via linux?
thank you anyway!
Hi all,
i asked a friend to let me do some playing around.
I have odin on his pc.
odin seems to be able to connect to device (ID:COM is filled) when the device is turned on.
i switched (as mentioned before both OEM and USB Debugging to on in developer options.
but as soon as i put the device in "download mode" i cannot see the device anymore.
so the same behavior as with adb shell.
is there anything else i need to pay attention to?
should i boot with louder/home/power and trigger a process to load a file from sd?
i read that the file should be named recovery.img, is that correct?
ok, reinstalling usb drivers from samsung did the job.
now i can see the device in download mode.
i was able to flash the stuff from here: https://www.hardreset.info/samsung-root-files/
lets see how far i get ;-)
Hi all,
so i was finally able to get everything done.
most of the stuff could be done on the phone... so it does not matter if you have linux or not as a pc operating system.
first install the bootloader (twrp). (herefore i had to use odin, but unfortunately the linux version did not work for me)
great video here:
then with the bootloader (twrp) install orangefox bootloader.
with orangefox flash repartition script.
these steps are described here as well (thats the image i used/installed):
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble]
LineageOS 17.x Unofficial for Galaxy A3 2017 LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Quack), which is designed to increase performance and reliability over stock Android for your device...
forum.xda-developers.com
thats it for the system.
to get root access to your phone, this is a pretty good desciption:
How to Install Magisk on your Android Phone
Magisk is a powerful tool that can help you customize some aspects of your phone or even grant you root access. Here's how you can install it!
www.xda-developers.com
i followed the steps:
- get boot.img
- patch it
- flash it (with orangefox)
this looks like changing the bootloader was done with fastboot.
i will try to look at it later, but that seems like a way that is less related to the os of the pc you are using.
maybe (eventually) samsung is going to be a bit differen... but still a way without WINDOWS
subbamaggus said:
so my hopes:
- support the apps i like (sportractive in particular), it does not support android 7.0 anymore
- better battery life (i found that android 7.0 is not the best in dealing with bad cellular service, i have to switch to 2g manually to get me throug the day, 4g consumes over 100mA in standby)
- i would want to keep my message history of whatsapp and signal
- i bought drift racers(https://www.sturmkind-shop.com/dr-ft-racer-kaufen/), which would not work with my android 7.0
Click to expand...
Click to collapse
YEY!
all of my hopes were fulfilled
for all that are interested in that info
As i wrote in the ROM thread.
As of now i would recommend to keep AOD of.
On my device it never gave the CPU the chance to get in deep sleep mode.
which is why i ended up with like 5% per hour with no usage.
with the deep sleep i get pretty close to 1% per hour.
after a couple of hours that changed a bit...
i started a new thread for that purpose.
yesterday i had an install session with a friend (he has the same phone)
some things to consider:
- orange fox was not available right away. maybe i missed the step where it actually was set as active bootloader
- formatting of the device is also necessary, i have another device here, as soon as this is ready i will (hopefully) be able to tell when.
just for completeness:
i additionally installed "icon limit increased to 7",
Statusbar Notification Icon Limit Increased to 7, Android 12
These modules should increase Statusbar Notification Icon Limit to 7 Uploaded 1-7-22 Stock https://www.androidfilehost.com/?fid=17825722713688263520 ------------------------------------------------- If I helped, hit the Thanks Button...
forum.xda-developers.com
and you need the "kill camera", since sometimes the cam will hang.
for me i had to change the audio setting for calling:
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble]
LineageOS 17.x Unofficial for Galaxy A3 2017 LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Quack), which is designed to increase performance and reliability over stock Android for your device...
forum.xda-developers.com
I'm trying to install Lineage OS on my phone and I have followed all the steps (plus many more they just assume you'll know) from this site, up to configuration because adb no longer discovers my phone.
.\adb devices
.\adb fastboot bootload
literally anything to do with adb doesn't work but it did an hour ago. Now I'm worse off because my phone will only upload to bootload and not to the actual homescreen so there's no going in and double checking if my USB debugging is on (it was before the reset) and I can't access my phone at all, nor can I get things configured. I've updated the drivers via web, deleted and retried the drivers, and restarted the computer. I don't know what I'm supposed to have on my computer that would better upload the drivers. I don't have a clue what any of this is supposed to mean, I was forced to do all of this **** because of the recent Adroid 12 update that I couldn't get rid of without just getting a different OS. Please please please make it dumb for me and tell me how I can get my phone back and download this OS.
Try fastboot commands in bootloader
yesca213 said:
Try fastboot commands in bootloader
Click to expand...
Click to collapse
Yes fastboot commands work but I need to copy this in the command prompt
.\adb sideload copy-partitions-20210323_1922.zip
The tutorial says it isn't an optional step. When I try doing this with fastboot, it tells me:
fastboot: usage: unknown command sideload
Try "fastboot reboot" or "fastboot reboot bootloader"
yesca213 said:
Try "fastboot reboot" or "fastboot reboot bootloader"
Click to expand...
Click to collapse
Thanks! I tried it with no change. adb can still not discover my phone and it doesn't start back up, only brings me to FastBoot mode screen.
If it's Windows your using it may be a driver issue.
yesca213 said:
If it's Windows your using it may be a driver issue.
Click to expand...
Click to collapse
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
johnmtrowbridge said:
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
Click to expand...
Click to collapse
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
heyhowyoudoin said:
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
Click to expand...
Click to collapse
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
johnmtrowbridge said:
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
Click to expand...
Click to collapse
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
heyhowyoudoin said:
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
Click to expand...
Click to collapse
Yeah I'm gonna just have to try in a few hours because the only way Signal works on my desktop is if I verify it on my phone lol. Again, the phone is completely stuck on FastBoot mode and anytime I restart it it takes me right back, which I think is probably because of the recovery mode I just installed.
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
heyhowyoudoin said:
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
Click to expand...
Click to collapse
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
heyhowyoudoin said:
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
Click to expand...
Click to collapse
There wasn't a recovery version of 11 at the time that I could find, not for the 9 Pro. So what do I do now, do you know how I at least get my phone off of FastBoot mode to try this **** all over again?
johnmtrowbridge said:
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
Click to expand...
Click to collapse
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Index of /list/Unbrick_Tools/OnePlus_9_Pro
or download version for your phone from link above
heyhowyoudoin said:
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
Click to expand...
Click to collapse
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
heyhowyoudoin said:
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Click to expand...
Click to collapse
NA I'm in America
johnmtrowbridge said:
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
NA I'm in America
Click to expand...
Click to collapse
yes, that's what I mean. is your phone linked to t mobile?
at the moment it is not possible to install any custom OS from version 12 of android, not only lineageos
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Shipoftheline said:
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Click to expand...
Click to collapse
I can't enter to recocery after flashing android 13
Kirya27 said:
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Click to expand...
Click to collapse
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Lughnasadh said:
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Click to expand...
Click to collapse
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Kirya27 said:
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Click to expand...
Click to collapse
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Lughnasadh said:
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Click to expand...
Click to collapse
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Kirya27 said:
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Click to expand...
Click to collapse
Well, you didn't mention you were using the latest Platform Tools, so I suggested it as that's one of the 1st steps of troubleshooting in these situations. You also didn't specifically mention using Android Flash Tool, so I suggested that as well.
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
This sounds interesting. I'll try it today when I get home and post the results here.
Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
I tried the method that you described and indeed, for some time the phone worked on Android 13 (however, when it was turned on, it wrote that this device was suddenly damaged due to something, photo below). True, after 15-20 minutes of use, phone rebooted into the bootloop, just for no reason at all. I flashed exactly as you said, separately in each slot ...
I have had this screen when I soft bricked after flashing lineage os. I fixed it with flashtool. My exact setup is windows 11, flashtool through Microsoft edge with the options to force flash and wipe device checked in flashtool. Flashtool has rescued my p6pro many times with this setup.
fil3s said:
У меня был этот экран, когда я завис после прошивки Lineage OS. Починил флештулом. Моя точная настройка — это Windows 11, flashtool через Microsoft Edge с параметрами принудительной прошивки и очистки устройства, отмеченными во flashtool. С помощью этой настройки Flashtool много раз выручал мой p6pro.
Click to expand...
Click to collapse
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Kirya27 said:
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Click to expand...
Click to collapse
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
fil3s said:
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
Click to expand...
Click to collapse
I tired fastboot -w many times
Kirya27 said:
I tired fastboot -w many times
Click to expand...
Click to collapse
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
fil3s said:
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
Click to expand...
Click to collapse
Tried. It turns out the same as on the stock firmware
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
apis903 said:
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
Click to expand...
Click to collapse
They clearly designed these phones to fail. They implied they would be usable for 6 years, but like all previous google phones, it will brick itself within 2. This 6 Pro is definitely the last product I buy from Google. I've had 3 other Nexus/pixel phones, none of which lasted. My sister is still using my hand-me-down iPhone 7 that I dropped off a cliff.
I can't do iphones though, and I don't want to support slave labor.. so my options are extremely limited. I'm only going to buy smartphones produced in the USA. It's dangerously cheap to produce phones using the less strict labor and material laws of foreign countries, phones are being treated as disposable, which is unacceptable. My modified Nexus 5X is perfectly usable despite having half the CPU disabled and being a 7 year old phone, thanks to overclocking. Companies should not release a new device unless it is a worthy upgrade over the previous one. It should happen every 3 years, not every year.
I just hope other nerds wake up and stop supporting Google. We have to boycott Google until they create desirable products. Pixel is so undesirable that they spend their ad money on woke bull**** that no one cares about except the sheep, but they like iPhones. Google is just burning our money and ignoring our needs.
Edit: I'm just salty that I got scammed by Google. They lost all of their people who cared. Google is full of corrupt people who want to make a buck. Pixel 7 is essentially the exact same as Pixel 6. The lack of a pro mode in the camera app perfectly represents Google's priorities. It would take one developer a couple days to add such a feature to the app. Google is not doing ANYTHING good.