Related
Hey I have a
SGP321 with:
Android version : 5.1.1 / kernel version : 3.4.0-perf-gbccb33a / Build number : 10.7.A.0.228
I cannot comprehend how to root it.
I managed to unlock bootloader, using FlashTool, and a code from Sony's developer page.
I want to install this rom:
Resurrection Remix M for Xperia Tablet Z (Wi-Fi/LTE)
It seems like rooting is failing due to the Android 5.1.1 .. Then where can I get the 4.4.2 firmware ?
I'm from Norway, and the device isn't locked to any carrier.
Deimos87 said:
Hey I have a
SGP321 with:
Android version : 5.1.1 / kernel version : 3.4.0-perf-gbccb33a / Build number : 10.7.A.0.228
I cannot comprehend how to root it.
I managed to unlock bootloader, using FlashTool, and a code from Sony's developer page.
I want to install this rom:
Resurrection Remix M for Xperia Tablet Z (Wi-Fi/LTE)
It seems like rooting is failing due to the Android 5.1.1 .. Then where can I get the 4.4.2 firmware ?
I'm from Norway, and the device isn't locked to any carrier.
Click to expand...
Click to collapse
To flash RR 5.7.4 you need to have a Recovery.
To root:
Download kingroot apk from below link and install it. Follow the steps in that app and your device will be rooted.
https://king-root.net/wp-content/KingrootV4.9.6.apk
To flash recovery:
Select: TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip from the link below. And follow the Read Me.txt to install recovery.
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26
TAKE A BACKUP OF YOUR DATA BEFORE YOU START TO DO ALL THESE.
I JUST HELP AND TAKE NO RESPONSIBILITY TO WHATEVER HAPPENS TO YOUR DEVICE.
All the best
@Deimos87
@Alok Bajaj
It's actually much much easier/faster to flash RR boot.img straghtforward (Flashtool -> Fastboot -> Select Kernel to Flash) and install .zip afterwards via built in recovery.
Cause NUT's recovery is kinda dated now, and is not meant to install custom ROMs, though it can do it on pollux, but very often is unable on pollux_windy.
I'm going to download and try.
I managed to brick the tablet into a continuous boot and reboot. But I am lucky enough to get it into flashmode...
I tried flashing some other original ROM, but it was for Vodafone in UK. I tried to recover it with the official Sony program (Essentials?), but it said that my device was rooted. But I guess its because I have unlocked the bootloader. I have also requested to be able to use Sony Emma/Embla or something for flashing.
I was trying to get to Android 4.4.2 or 4.4.4 to be able to root. Its so much software out there. It's like getting into a new territory of learning.
I managed to do something....
What I have done before was to open the bootlocker. If it did matter... Using newest flashtool.
I got an Spanish FTF Rom file from the Flashtool Site, SGP321_10.1.1.A.1.307_Customized_ES.ftf. Flashed it somehow using a elderly flashtool (0.9.18.6), could probably work on a newer one but God's will and such.
I then downloaded DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit. And installed SuperSU or something. Settings: USB Debug and allow unsigned/foreign APK's.
There is a gap in my memory here (maybe I started TabZ-lockeddualrecovery2.8.26-RELEASE.combined).
My tablet booted into a recovery mode after doing something on my PC with the tablet powered in normal system (USB debug), and I now have managed to select my desired, ROM, and Gapps (No clue what it is yet) and a kernel that they recommended.
Now its currently Optimizing my apps (Preinstalled I guess). 106 apps.
Update1:
Popup "Unfortunately, Setup Wizard has stopped". I did see some google stuff also do the same
I am trying to factory reset with wipe.
There was now a different recovery menu.. Hmm. I had to disconnect the battery to get out of the menu. ( I have opened the tablet beforehand).
Maybe its that GAPS stuff that didn't install...
If this fails again I will try and install gaps again inside recovery.
Deimos87 said:
Popup "Unfortunately, Setup Wizard has stopped". I did see some google stuff also do the same
I am trying to factory reset with wipe.
Click to expand...
Click to collapse
you need to install gaps right after ROM install, or you'll will have setup wizard error.
I managed to install Ressurection M.
It was very painfull, I had many tries over the course of 3 days.
I flashed a older spanish 4.4.2 (i think) firmware.
Then I rootet it using kingroot I think.
Then I installed TWRP.
Since the Sony tablet doesn't boot into recovery with keypresses I had to boot into recovery in software.
I then wiped about everything, I formated System partition also. Because If I do not the old applications will follow into the new ROM.
I then flashed Resurection M, and GAPPS on the same time. I do not remember If I also flashed the Kernel also now or after.
I think I concluded with that the Kernel had to be flashed at the same time.
If I did something wrong I just flashed the old spanish firmware over again and redo. I actually liked the old firmware due to it was much nicer user interface. The new one on Android 6 is kind of hard to manage. But I get more screenspace now.
A new Update for the ZenFone 3 Ultra is finally here. OTA Updates are live for eligible devices. This is not the Android 8.0 Update I was hoping as the Version number still shows 7.0 so lets hope I am wrong. Given the size I thought it might be the Android 8.0 Oreo Update but does not appear to be.
I have the WW Version and got the update notification this morning. It is 470.75MB in size and hopefully soon the full Firmware package will also be available for offline install.
Anyway, lets see how the firmware is and hope it fixes previously identified issues such as battery drain and others.
Enjoy!
I got it this morning as well, didn't think it was Oreo but hoping to see better performance........
DJMRLONG said:
I got it this morning as well, didn't think it was Oreo but hoping to see better performance........
Click to expand...
Click to collapse
So, is Ultra getting Oreo or not? What i hear are all rumours, nothing from the horses mouth.
australia here, today got OTA and now i have WW_14.1010.1804.74_20180605
still android 7.0
AWFRONT said:
A new Update for the ZenFone 3 Ultra is finally here.
Anyway, lets see how the firmware is and hope it fixes previously identified issues such as battery drain and others.
Enjoy!
Click to expand...
Click to collapse
not for my case, the update doesnt fix anything.
the battery drain is AMAZING. congrat Asus!
charged overnight, pull it at 100% in the morning, open 2 websites clicks 2-3 links, and battery down to 98%. whatttttt???
(not website with FHD photos, just normal websites with texts)
so anyone know wat the update about ?
I downloaded the update from Asus website and installed it manually cause my Ultra is rooted and didn't receive OTA. After downloading the zip file I placed it in the root of the phone (no folder), I rebooted the phone and after the boot I received a notification "update available". I taped on it and the whole process was automatic, the phone rebooted into twrp and from there it booted back into Android. After the first boot I didn't had installed anymore Magisk (no root) so in went to the PC and flashed once again the twrp image using fastboot mode (twrp was replaced with the stock recovery image during the update). From there (twrp) I flashed once again Magisk and everything was ok, I regained root access. With the exception of the security patch, witch is now from April 2018, everything seems to be the same as before the update.
lucian1983 said:
I downloaded the update from Asus website and installed it manually cause my Ultra is rooted and didn't receive OTA. After downloading the zip file I placed it in the root of the phone (no folder), I rebooted the phone and after the boot I received a notification "update available". I taped on it and the whole process was automatic, the phone rebooted into twrp and from there it booted back into Android. After the first boot I didn't had installed anymore Magisk (no root) so in went to the PC and flashed once again the twrp image using fastboot mode (twrp was replaced with the stock recovery image during the update). From there (twrp) I flashed once again Magisk and everything was ok, I regained root access. With the exception of the security patch, witch is now from April 2018, everything seems to be the same as before the update.
Click to expand...
Click to collapse
Hello. I would like to know how you rooted and installed twrp (without unlocking bootloader?)
Since to get update available, you need locked bootloader from what I understand.... so if you got update available, it appears your bootloader is still locked. But you are rooted and have custom recovery also. Thanks appreciate how you managed to root and install twrp without unlocking the bootloader.
mac231us said:
Hello. I would like to know how you rooted and installed twrp (without unlocking bootloader?)
Since to get update available, you need locked bootloader from what I understand.... so if you got update available, it appears your bootloader is still locked. But you are rooted and have custom recovery also. Thanks appreciate how you managed to root and install twrp without unlocking the bootloader.
Click to expand...
Click to collapse
I got my Ultra second hand and it camed with bootloader unlocked and magisk allready installed, so it was rooted and running latest firmware from Asus website at that time, several months ago, the firmware ww_1010.1804.64. in fastboot mode it said "unlocked" for the bootloader, so probably the seller used the unlock tool from Asus website to unlock the bootloader and after he flashed TWRP with the computer, by putting the phone in fastboot mode. You can find the TWRP zip file on a Indian site and download it with the Mega app. Just search on Google "TWRP zenfone 3 ultra".
Several days ago, I downloaded the new firmware from Asus website, ww_1010.1804.75 and placed the zip file in the root of the internal storage, under all the other folders. When I used the update system feature in the settings it didn't detect any update available, but after I rebooted the phone it appeared a notification message with "update available", I taped on it and the update was installed with TWRP and the phone rebooted. After reboot the TWRP image was replaced with the stock recovery from Asus and I had to go to the computer to flash TWRP image once again with the help of fastboot mode (also it said "unlocked " for the bootloader even after the update). From there (TWRP) I flashed back Magisk 16.0 zip file and everything is back to normal for me, I have the latest firmware from Asus and root.
understand now..thanks. So it did not do an ota update (my confusion) but did an update since you had the rom already in storage (hence the prompt for update available) ok thanks!
mac231us said:
understand now..thanks. So it did not do an ota update (my confusion) but did an update since you had the rom already in storage (hence the prompt for update available) ok thanks!
Click to expand...
Click to collapse
Anytime!!! Yes, that's it, it was no OTA update, only a notification prompt because I put the rom in the root of storage.
Hello,
I've uploaded some image files for Nokia 3.2 and want to share them.
I've packed some images for Nokia 3.2 00WW variant (e.g. Magisk, fastboot ROM) and will upload user images for the 00EEA variant, too.
It just needs some more time to upload completely.
EDIT: I transfered all the files to Mega.nz
https://mega.nz/folder/hVMTiCbT#OhmmxhtKabnNn2hWfiIgHQ
P.S. if someone has the european Variant and wants to provide matching Magisk Patched boot images just send me a link to those and i will add them to my Mega.nz folder
Hello,
i just uploaded the patched boot image december 2019 for the europe 00EEA version in other thread under https://forum.xda-developers.com/attachment.php?attachmentid=4929795&d=1579367908.
Perhaps you can add it to your google drive.
Greetings
Hi, sorry i didnt see it. Could you created a Copy of it with dm-verity disabled? You can do it with superr's kitchen. So that we have a magisk Image for GSIs.
Thanks
P.S. i will Upload the magisk patched image tomorrow.
EDIT: I can Just remove dm verity on my own. :silly:
I've created a Telegram Channel for Nokia 3.2
Updates regarding Source Code, the Google Drive mirror (magisk stuff,Firmwares etc.) And any helpful information will be posted by me on the Channel.
Note information inside ReadMe file on the Google Drive link
TA-1156 Qcn
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
chinovaso said:
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
Click to expand...
Click to collapse
Hi I don't have any qcn file. My Nokia 3.2 is currently being repaired. But I've found a tool what could help you.
https://www.getdroidtips.com/download-imei-qcn-tool/
Just test it and look if it works
chinovaso said:
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
Click to expand...
Click to collapse
Thank you s3tupw1zard, but I try this tool already, it works , *06# when it checks it shows the imei numbers but there still no a gsm signal.
Also the serial number is shown as 012345678E0000 and in *#*#4636#*#* servise menu when i chek says Mobile radio is oFF
How to flash using fastboot
Hey mate
Can u guide me through flashing magisk boot img
Im kinda of confused becoz of A B partitions
Any detailed guide would be appreciated
Im on latest January update 2020
Nokia 3.2 (deadpool)
chinovaso said:
Thank you s3tupw1zard, but I try this tool already, it works , *06# when it checks it shows the imei numbers but there still no a gsm signal.
Also the serial number is shown as 012345678E0000 and in *#*#4636#*#* servise menu when i chek says Mobile radio is oFF
Click to expand...
Click to collapse
Hi,
I can't help you in this case. Best would be if you send it in.
You can get your imei with 'fastboot getvar all' (without quotes) to send it in.
You need the imei for sending it in. Dont worry about warranty the ar not allowed anymore to denying warranty due to new google terms.
Just go to nokia website and order a repair.
No0bGuy said:
Hey mate
Can u guide me through flashing magisk boot img
Im kinda of confused becoz of A B partitions
Any detailed guide would be appreciated
Im on latest January update 2020
Nokia 3.2 (deadpool)
Click to expand...
Click to collapse
I write a short guide into a new thread. I pack some files for gsi flashing together.
You will find this guide in about 30 Minutes on the Nokia 3.2 Guides section
Hello,
i uploaded the january 2020 patched boot.img for the European 00EA with dm-verify=off.
Please include on your googledrive!
https://forum.xda-developers.com/attachment.php?attachmentid=4956671&d=1582404743
Greetings
Using these images
Hi All
i've bought a Nokia 3.2 for installing lineageOS ! So i could unlock it and installed this ASOP-Image (probably the 00WW-Version) thru ADB and fastboot with the result to get a crappy OS without WiFI.
At the end i needed about 10 days to get a connection (probably thru qualcomm-drivers) to the pc again, where i can use your (hopefully working) images.
In order to avoid a malfunctioning NOKIA, i am asking about the right way to install the 00EA-Version:
Again i can use adb and fastboot, so first step is to use flash-user-bin.bat for flashing boot.bin, dtbo.bin, system.bin, vendor.bin and vbmeta.bin !
Now there should be a working OS with WiFI, second step would be patching boot_jan2020_dmOFF_00EA.img and third step patching twrp-3.2-dpl-00eea.img.
At last it should be possible to install LineAgeOS thru Magisk Manager (or CWM) ?
Thanks for your advices
Your device needs the images with the same version. So boot.img from January combined with firmware from December lead into bugs like WiFi not working. Reboot to bootloader, there is a info where either 00WW (international Variant) or 00EEA (European Variant) is written. I've uploaded a GSI base for both variants on the Google drive Link at the beginning of this thread. You can find both base 7z Files Inside GSI folder. But be sure which Variant you have. After executing flash-all.bat execute the other bat file (it will flash magisk patched img with dm-verity removed) and after that finishes you can flash any GSI to system.
And you can't install ROMs through Magisk. It is Superuser. You need to be in Bootloader mode.
And USB debugging needs to be on and your PC needs to be authorized by your device. Just activate USB debugging in developer options and type adb devices. There should appear a prompt.
thx
for fast reply. It should be 00EEA, because i've bought it in Austria. I think, i have seen it in the settings/my phone too.
So i will use the GSI-Version tomorrow. With Magisk-Manager i should could load this TWRP-Image (on a SD-Card) too ?
Stupid Question: what is the meaning of the shortciut GSI ?
Regards
other bat-file
s3tupw1zard said:
Your device needs the images with the same version. So boot.img from January combined with firmware from December lead into bugs like WiFi not working. Reboot to bootloader, there is a info where either 00WW (international Variant) or 00EEA (European Variant) is written. I've uploaded a GSI base for both variants on the Google drive Link at the beginning of this thread. You can find both base 7z Files Inside GSI folder. But be sure which Variant you have. After executing flash-all.bat execute the other bat file (it will flash magisk patched img with dm-verity removed) and after that finishes you can flash any GSI to system.
Click to expand...
Click to collapse
Hi s3tupw1zard !
where is this other bat-File ? This GSI (generic system image)-Folder of 00EEA is empty, but i've used user_images_00EEA.7z and this is working perfectly.
In spite of it i would like to change booting (with magisk-patched.img). but this is existing for 00WW only. I've tried to flash twrp-Image too, but there i've got errors, so i've flashed user_images_00EEA completely again.
Thanks for your work
At last
i could create something, but still there is something missing !
I've downloaded boot_nodm_magisk_patched.img from shared googleDrive and patched it with MagiskManager.
Unfortunelately i tried to flash this file without renaming - so i had to reset to factory settings, because booting was not working.
After that, i was remembering to rename this boot-file to boot.img, flashed to factory new system - following flashing the system with LineAgeOS from Andy - https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/ (renamed it to system.img)
The result: booting procedure for working LineAgeOS needs about 5 minutes and wifi is missing !
Does anyone have a clue ?
Do i need to setup system with user-Image (December 2019) from Manuels Google Drive before ?
ThankYou for advices
Gerhard
Then you flashed the wrong boot.img.
You must look for your Version - 00WW or 00EEA - and you must have the corresponding security level to your firmware, means January or December ........
00ww - 00eea
page1875 said:
Then you flashed the wrong boot.img.
You must look for your Version - 00WW or 00EEA - and you must have the corresponding security level to your firmware, means January or December ........
Click to expand...
Click to collapse
thanks for reply.
If i am lucky, i will use boot_jan2020_dmOFF_00EA.img next time - but for now i have (possibly) corrupted partition table file and so device is ended in a fastboot-mode loop - Android ONE Logo flashes up less than 1 second
So hopefully with fastboot flash partition Firmware\gpt_both0.bin (gpt_both0.bin from Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL) i can restore partition table file in spite of this 00WW-Version.
Does anyone have seen firmware for 00EEA-Version ?
cheers
Idiots Guide
The reason for infinite bootloop and ADB-Flash error messeage 'FAILED (remote: partition table doesn't exist)' may be (as i remember) is to rename boot.bin from user_images_00EEA of our wizard to boot.img.
Resetting to factory defaults is not possible anymore - so beware of it !
After returning to Android 7.0 stock ROM (firmware RS98821d) on LG G5 RS988 from LineageOS 15.1 and then, in the following order, locking and unlocked the bootloader (implicitly clearing data and cache); flashing TWRP 3.2.3-0 recovery, using TWRP recovery to install jcadduono's "no-verity-opt-encrypt-6.1.zip" dm-verity disabler and SUperSU 2 .82 superuser root, and removing many of the Google Apps, I noticed that the "Regulatory & Safety" page of the system Settings app (Settings --> Regulatory & Safety) does not display the expected information. Instead of providing the FCC ID of the device, a screen with "Need to update" and "A radio interference is possible while using this wireless equipment." messages is instead displayed. I have attached a screenshot of the Regulatory & Safety page that I receive.
I had not checked the "Regulatory & Safety" page after flashing back to stock, but before making other changes.
Have others encountered the "Need to update" page before? Is the page normal after any of the changes I had listed above?
You really flashed a lot of things! To go back to stock did you just flash system.img or the whole kmz? In the first case maybe you might need to flash some other partition (modem.img maybe).
I switched some roms in the past, as you did, including Lineage, and now I'm on stock. By the way after flashing TWRP and Magisk and removing GMS/GSF/Chrome/GSuite and so on, I can still see the FCC declaration.
To go back to stock, I had first flashed codefire's RS98821c Android Marshmallow Complete Zip package for TWRP flashing. After that, I flashed the RS98821c KDZ file using LGUP with UPPERCUT to the device in Download Mode/LAF. I booted the stock ROM, and noticed that I could not boot to fastboot. I reflashed the RS98821c KDZ file in Download Mode/LAF, but it did not result in fastboot mode becoming available. I tried over-the-air updates, and, interestingly, the following over-the-air updates were offered individually and applied in the following and ascending order: RS98821d, RS98821a, RS98821b, RS98821c, and RS98821d. Fastboot mode recovery became available again after flashing the second RS98821d over-the-air update. I did notice that after flashing the first RS98821d over-the-air update that the Android version showed 6.0.1 and the system behaved much like RS98821c Android 6.0.1. After flashing the RS98821a over-the-air update (this file had a file size over 1 GB), the system then reported the Android version as 7.0 and firmware version RS98821a. After flashing the second RS98821d update, the system, fastboot, and recovery appeared to then behave and report correctly, notwithstanding the Regulatory & Safety page in the Settings app, which was not yet tested.
The device's original firmware, before I flashed LinageOS 15.1, was RS98821d. I decided to flash the RS98821c Android Marshmallow Complete Zip rather than an RS98821d Android Nougat Complete Zip to try to guard LAF flashing rejecting an older version KDZ. Unfortunately, the RS98821c KDZ is the most current one publicly released despite RS98821d being the current public firmware.
My thoughts:
Although Download Mode/LAF reports flash as successful, it may not truly be the case.
Perhaps LG Anti-rollback mechanisms maintain latest version of parts of a firmware. This may explain why the stock system did not behave as expected until the long sequence of over-the-air firmware updates were applied.
The Regulatory & Safety Settings app page might or might not rely on criteria unrelated to the flashing.
I have solved the issue described in this thread. After some more testing, it appears that the "Need to update" message is a stock ROM bug that manifests at various screen dpi, but not at the Settings app's Display Settings screen optional overrides.
Hello I have an ANE-LX3, my problem is the following: I have been trying to unlock the bootloader of my huawei p20 lite with HCU for two weeks but it tells me that the security patch is very new. What I did was download MRT FLASHING TOOL and an UPDATE.APP with System 8.0.0.046 (092Y) and everything was fine, I was able to unlock the bootloader, until I noticed that I no longer receive OTA updates
thanks
artur.mok12 said:
I noticed that I no longer receive OTA updates
Click to expand...
Click to collapse
IMO you have wrong Model and incomplete FW on board. I bet your build number is "system 0.0.046" and Model - unknown .
I don't know where you got this tutorial to unlock the bootloader, but for Kirin-devices it is not a good idea.
IMO you can try the following :
A) update via eRecovery & wi-fi
B) install Service ROM using dload method for your current EMUI version and region (but it will lock your BL again ! )
C) if you are still running EMUI 8, try update your phone via fastboot - flash cust.img, ramdisk.img , recovery_ramdisk.img and system.img ( extract the required files from Service ROM using Huawei Update Extractor).