Related
Yesterday I received an OTA from the Update center but as I am rooted and with custom recovery, I can't apply it.
Does anyone know where I can find the downloaded OTA file in my phone?
It's a 4.4 MB OTA for 10.5.A.0.230, and I have downloaded it on my phone but not applied as it gives me error everytime because it restarts on TeamWin recovery.
My ROM is this one:
Stock Nordic 4.4.2 10.5.A.0.230 Aroma for CWM + kernel
check using PC software. it may get installed
For me this is what I did, cause I used the stock rom and updated.
If your bootloader is unlocked you have to lock it first. Only Stock kernels do the updating work or else it will just skip through the boot process.
But I don't know about Teamwinrecovery so you have to try it and see.
Don't lock bootloader with the modified recovery installed Might brick your device
Thanks for the answers, but my bootloader is locked and kernel is stock.
I just need to know where the OTA is downloaded in my phone, so I may access it directly and check what it's included.
Sent from my C5503 using XDA Premium 4 mobile app
Same..;
I have exactly the same rom and got the same update yesterday.
Also not able to install.
I don't want to update with pc companion as I think i might loose root?
BarajaVLC said:
Does anyone know where I can find the downloaded OTA file in my phone?
Click to expand...
Click to collapse
The OTA update file is stored in /cache (need root to access), but it is not a .zip file like used by many other manufacturers — Sony uses a proprietary .pkg format for OTA updates, and currently there is no known way to unpack such files manually. Therefore the *.pkg file is useless for you, and the only way to update a phone with modified system files or unlocked bootloader is by using a PC.
Or, if you are already on 10.5.A.0.230, you may just ignore this update for now — it just adds the Google Music app, removes the Adobe Reader app (but it won't be removed if updating without wiping user data), and adds APN settings for more operators (which you probably don't need if mobile data already works for you).
kurtfimmers said:
I don't want to update with pc companion as I think i might loose root?
Click to expand...
Click to collapse
Yes, you will lose root (and any other system modifications you had), but Easy Root Tool should work with the 10.5.A.0.230 stock ROM even after the update.
sigprof said:
The OTA update file is stored in /cache (need root to access), but it is not a .zip file like used by many other manufacturers — Sony uses a proprietary .pkg format for OTA updates, and currently there is no known way to unpack such files manually. Therefore the *.pkg file is useless for you, and the only way to update a phone with modified system files or unlocked bootloader is by using a PC.
Click to expand...
Click to collapse
Thanks for all the help but there is nothing in the /cache/ folder that may be the OTA update.
I see three folders inside /cache
/backup
/lost+found
/recovery
Backup and lost+found are empty and inside /recovery
/recovery/fota/tmp/a/
/recovery/last_log
Everything is empty Anyways, I'll wait for the new 4.4.4 OTA
You really solved the problem?
BarajaVLC said:
Thanks for all the help but there is nothing in the /cache/ folder that may be the OTA update.
I see three folders inside /cache
/backup
/lost+found
/recovery
Backup and lost+found are empty and inside /recovery
/recovery/fota/tmp/a/
/recovery/last_log
Everything is empty Anyways, I'll wait for the new 4.4.4 OTA
Click to expand...
Click to collapse
If you can't make OTA work, even the 4.4.4 OTA will fail. I am not so versed in English, so I will say it in Layman terms.
You mentioned that you are rooted and installed custom recovery on 10.5.A.0.230, this means that your kernel is modified to allow for custom recovery.
The easy way to do it is to flash any FTF and rerun the entire update process anew. Make sure that you have 100% lost root and custom recovery.
The SUS(now PCC) actually downloads update in 5 chunks, and apply them. Flashtool join these chunks to a complete FTF file. This solution, however, means you have to have access to a computer that at least runs EXE programs. There is no way to do it on your mobile.
sigprof said:
The OTA update file is stored in /cache (need root to access), but it is not a .zip file like used by many other manufacturers — Sony uses a proprietary .pkg format for OTA updates, and currently there is no known way to unpack such files manually. Therefore the *.pkg file is useless for you, and the only way to update a phone with modified system files or unlocked bootloader is by using a PC.
Click to expand...
Click to collapse
Hi. Is it possible to directly flash this .pkg firmware (downloaded using Xperia Companion) using Flashtool? Is it the equivalent of a .FTF firmware file? Thanks.
Whenever I try to install it using Xperia Companion I get this error:
Code:
Code:
an error occured while updating your device.
Error code: kResultCode_DeltaUpdateResultDidReturnFail
I just got locked out of my phone while trying out lockscreen apps, and then when I tried to restore using TWRP, I got the message - unable to mount system as rw. Earlier, while taking a backup, mounting as read only was solving this problem, but obviously read only would not work in restore operation. I used PRF Creator to create a pre-rooted firmware. I used NUT's latest dual recovery, BETA-SuperSu 2.49 zip and the Indian LP 5.1.1 FTF that I downloaded using XperiFirm. I threw in the Xposed Framework as an added zip as well. Is this a common problem with TWRP or was I facing something specific? Is there a way to mount system as rw from within TWRP using the command shell?
[Update]: TWRP system mount as rw is working in LP 5.0.2. Only in 5.1.1 the problem persists. Any Backup-Restore operation now needs to go through LP 5.0.2 fresh install, root, install recovery and then restore.
There is a option to mount /system and unmount /system inside recovery.
If you are using a zip file which is the be flashed, check it's updater-script. From there you could further investigate.
You will see when you seaarch on @Nut s original twrp subject. You should find new twrp beta .22 there. http://nut.xperia-files.com/?ql=0849e100ec98cef32653090c81c9c97cf56fddb5
falptekin said:
You will see when you seaarch on @Nut s original twrp subject. You should find new twrp beta .22 there. http://nut.xperia-files.com/?ql=0849e100ec98cef32653090c81c9c97cf56fddb5
Click to expand...
Click to collapse
download the latest version it works great and can mount the system
it was a bug i think and it was fixed
Koodo Mobile: http://downloadmirror.co/android/tq/G900W8VLU1COI4_G900W8OYA1COI4_KDO.zip
SaskTel: http://downloadmirror.co/android/tr/G900W8VLU1COI4_G900W8OYA1COI4_BWA.zip
Virgin Mobile: http://downloadmirror.co/android/ts/G900W8VLU1COI4_G900W8OYA1COI4_VMC.zip
Bell Mobil: http://downloadmirror.co/android/tt/G900W8VLU1COI4_G900W8OYA1COI4_BMC.zip
Rogers: http://downloadmirror.co/android/tu/G900W8VLU1COI4_G900W8OYA1COI4_RWC.zip
Telus: http://downloadmirror.co/android/tv/G900W8VLU1COI4_G900W8OYA1COI4_TLS.zip
Fido Mobile: http://downloadmirror.co/android/tw/G900W8VLU1COI4_G900W8OYA1COI4_FMC.zip
Source: http://www.theandroidsoul.com/downl...1-update-g900w8vlu1coi4-with-root-info-85381/
Nice, which I've would I download for Wind Mobile?
If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?
Spacemonkie4207 said:
Nice, which I've would I download for Wind Mobile?
Click to expand...
Click to collapse
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.
hexavoodoomal said:
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.
Click to expand...
Click to collapse
Where can I find the proper apn settings?
Zehlek said:
If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?
Click to expand...
Click to collapse
use odin in pc
Spacemonkie4207 said:
Where can I find the proper apn settings?
Click to expand...
Click to collapse
Google it.
Whats new ?
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I have 900M so i cant install, maybe anyone can post anything, but 99% sure didnt have themes
Enviado de meu SM-G900F usando Tapatalk
brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I think it is more under the hood updates
Sent from my SM-G900W8 using Tapatalk
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.
daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
Only with custom kernel
Enviado de meu SM-G900F usando Tapatalk
Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
☺
daroco said:
Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
Click to expand...
Click to collapse
The way I usually root is to flash CF-Auto-Root-kltecan-kltevl-smg900w8.tar using odin. Can you try that?
I haven't updated yet until I'm sure root is there as I gave the phone to my wife.
thanks
Still bootloops when I flashed CF-Autoroot. it also installed the original recovery from another BL version. I reflashed TWRP and cleared cache and dalvik (not that I expected it to do much) but still the same. restored a nandroid and I had all kinds of apps FC. End result was to factory reset the phone to be in a stable condition. If this was a car I could get this damn thing running right! I should have learned more about programming while I was in school...... 2 kids and a mortgage I have no time for it now.
[HOWTO] Root your 5.1.1 G900W8VLU1COI4 firmware
daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results. [...]
Click to expand...
Click to collapse
mauriicio21 said:
Only with custom kernel
Click to expand...
Click to collapse
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
-------------------------------------------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rooted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions/symlinks list from your 5.1.1 firmware. I require it to be well prepared with my custom firmware for G900F. I believe that Android 5.1.1 for G900F is just a matter of a few days.
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Do you Know how can i get spanish on this Vertion plz. ? @_alexndr
_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Hope this helps, thanks for your help.
Here you go!
Just confirmed the camera can shoot in RAW format
Hello, everyone.
Even after flashing stock ROM with kdz your L90 may still display ROOTED in download mode or in the RCT test (open Telephone app and type 3845#*XXX# where XXX is your phone model, 410 for instance if you have a D410hn). The fix is relatively simple:
1. While still rooted, use a file manager with root access and navigate to /persist folder, then backup to a safe place (just in case you need them later) and delete these two files:
rct
rct.cfg
2. Reboot to recovery and do a full wipe: caches, data and system. It's important because maybe some files that trigger the rooted flag may be in /data/local/tmp, for instance;
3. Reboot to Download Mode (bootloader) and follow this tutorial to flash stock kdz:
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Before flashing kdz you shouldn't already see any ROOTED on screen, and after booting to stock the RCT tool should not display that your device is rooted anymore.
PS: I am not sure if deleting these two files will break anything, I have just did these steps and my device doesn't show ROOTED anymore. Ideally, you should backup /persist before rooting (I don't think it's possible anyway, at least not on Lollipop), or at least backup them just after rooting, so you can replace the files as explained is the treads bellow.
Credits
@Drachenminister - http://forum.xda-developers.com/showthread.php?t=2700992
@AriHell - http://forum.xda-developers.com/lg-g3/general/tot-reset-rct-root-check-tool-t2853627
@k0nane - http://forum.xda-developers.com/showthread.php?p=41136026#post41136026
READ, READ BEFORE PROCEEDING
YOU'VE BEEN WARNED
Ok, I wasn't going to create a new Thread for this but is really needed to keep this a little separate but in the same thread, so here i'll be updating base on current updates for each variant this Thread will contain Current Updates and as for now current updates are :
REQUIREMENTS :
- Plain and simple, you just need TWRP. Either via @tenfar or @tennear Tools or happens that you already have TWRP install.
ROOT:
If you are UNLOCK BOOTLOADER proceed with STEP 7, if not you'll need to use @tenfar Modded boot image base on your system update to get root access.
Each steps will contain 2 files which are:
1- BootStack
2- System+Boot
Q: Why 2 Flashable Zip Files?
A: Well cuz a lot of us know you CAN use / try other variant system image , i have separate what is just needed to for that purpose, meaning if A2017U want to give a shot to A2017G or A2017 software you will just need to Wipe Cache -Dalvik - Data and Flash the A2017G or A2017 Flashable system file or vice-versa.
The Bootstack just need to be flash ONCE per variant, the A2017G CAN'T use A2017U Bootstack (well you probably can but IS NOT RECOMMENDED) .
- A2017UV1.1.B35 (Nougat) (Post # 2 or Click Here)
- A2017.B10 (Post # 4 or Click Here)
- A2017G.B08 (Post # 3 or Click Here)
- A2017G Flashable Stock Recoveries (Post # 5 or Click Here)
-------------------------------------------------------------------------------------------------------------------------------
I'll be Updating this thread base on current Updates and please let's keep this thread clean and on-topic
-------------------------------------------------------------------------------------------------------------------------------
YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS
A2017UV1.1.0B35 NOUGAT Update
-----------------------
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N) / B19(N) / B25(N) / B32(N)
-----------------------------------------------------
Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important
1- Download the following zip files
- A2017UV1.1.0B35_bootstack_by_DrakenFX.zip
- A2017UV1.1.0B35_StockSystem_by_DrakenFX.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (Wipe Data if you aren't updating from B29-MM or B15-N)
5- Flash A2017UV1.1.0B35_bootstack_by_DrakenFX.zip( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- FlashA2017UV1.1.0B35_systemstock_by_DrakenFX.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT AND KEEP TWRP after flashing Stock System, download SuperSU v2.79 (Or your preferable Root method)
WARNING - WARNINGNOTE : YOU MUST FLASH SUPERSU OR VM-VERITY ZIP, IF YOU WANT TO KEEP TWRP, THE B32 UPDATE HAVE STRIP BOOLODER
8- REBOOT and Enjoy Nougat B35 Rooted or Just Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------.
.
.
.
YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS
A2017G.B09 Update ( Files Provided by @tron1 )
-----------------------
-----------------------------------------------------
UPDATING FROM B01, B02, B03, B05 , B06 or B08 Rooted or Stock
-----------------------------------------------------
1- Download the following zip files ( Thanks @tron1 for making the files )
- ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
- ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (I will say system as well but is up to you, i normally do wipe system if i'm flashing a system image).
5- Flash ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip ( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- Flash ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT after flashing Stock System, download SuperSU v2.65 which i have been mention before since day 1 and just flash the file.
8- REBOOT and Enjoy B09 Rooted or Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------.
.
. Here's the B08 Files in case are needed
. TWRP_A2017G.B08.BootStack_By_DrakenFX.zip
.
. TWRP_A2017G.B08.FStockSystem_By_DrakenFX.zip
.
..................................................................................................................................................................................................
.
. Here's the B06 Files in case are needed
. ZTE_A2017GV1.0.0B06_BootStack_by_DrakenFX.zip
. md5 : fa64983faaf4d37a26772dab53a61ff2
.
. ZTE_A2017GV1.0.0B06_StockSystem_by_DrakenFX.zip
. md5 : 3b34ac0d1c81248454666b9ae644da16
.
.................................................................................................................................................................................................
.
. Here's the B03 FIles in case are needed
. ZTE_A2017G.B03_BootStack_by_DrakenFX.zip
. md5 : ae0f260a9bd7ee486704842bc9efa202
.
. ZTE_A2017G.B03_StockSystem_by_DrakenFX.zip
. md5 : 5086d5a0d73e07a257b9f4cb4b7c7631
.
..................................................................................................................................................................................................
.
.
. Here's the TWRP B06 Flashable Stock Recovery
. TWRP_B06_StockRecovery.zip
.
. Here's the TWRP B08 Flashable Stock Recovery
. TWRP_B08_StockRecovery.zip
.
..................................................................................................................................................................................................
YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS
A2017.B10 Update
-----------------------
-----------------------------------------------------
UPDATING FROM B09 or Below Rooted B20
-----------------------------------------------------
1- Download the following zip files
- ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip
- ZTE_A2017V1.0.0B10_StockSystem_by_DrakenFX.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (I will say system as well but is up to you, i normally do wipe system if i'm flashing a system image).
5- Flash ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip ( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- Flash ZTE_A2017V1.0.0B10_StockSystem_by_DrakenFX.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT after flashing Stock System, download SuperSU v2.65 which i have been mention before since day 1 and just flash the file.
8- REBOOT and Enjoy B10 Rooted or Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------.
.
.B10 & B11 Flashable TWRP Files can be found here also :
https://www.androidfilehost.com/?w=files&flid=118419
.
.
----------------------------------------------
A2017G
Flashable Stock Recoveries
----------------------------------------------
Folder with A2017G Stock Recoveries B06 , B08 and B09
TWRP Stock Recoveries Flashable Zips
----------------------------------------------
Last Reserve for something else thread related
:good:
@DrakenFX could you please provide system dump or atleast tell me a way to extract everything of stock rom on my pc.
TheRoyalSeeker said:
@DrakenFX could you please provide system dump or atleast tell me a way to extract everything of stock rom on my pc.
Click to expand...
Click to collapse
System Dump for which variant? i know A2017G and A2017 are .dat but that can be converted to .img very easily, if you have windows you can use this Android DAT/IMG File Unpack and Repack V 2.0 , that's what i use to convert .dat to .img.
If you need more info just PM.
Can't seem to get Root access. Wipe Cache, Dalvik, Data and System. Flash the files in order: Bootstack > StockSystem > SuperSU 2.65 but it doesn't work. If I don't flash Root, it boots up accordingly.
AllAboutAndroids said:
Can't seem to get Root access. Wipe Cache, Dalvik, Data and System. Flash the files in order: Bootstack > StockSystem > SuperSU 2.65 but it doesn't work. If I don't flash Root, it boots up accordingly.
Click to expand...
Click to collapse
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.
xtermmin said:
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.
Click to expand...
Click to collapse
Let me try that now and will let you know asap!
AllAboutAndroids said:
Let me try that now and will let you know asap!
Click to expand...
Click to collapse
Let's us know I'm mins away from doing this but NEED root!!
S8ntsHaz3 said:
Let's us know I'm mins away from doing this but NEED root!!
Click to expand...
Click to collapse
Noooooope. I went back to Stock Recovery somehow...even though I had TWRP all along.
Sad days
xtermmin said:
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.
Click to expand...
Click to collapse
Trying this again!
S8ntsHaz3 said:
Sad days
Click to expand...
Click to collapse
Got TWRP back. I'm going to attempt the method above and let you know!
AllAboutAndroids said:
Trying this again!
Got TWRP back. I'm going to attempt the method above and let you know!
Click to expand...
Click to collapse
Awesome thanks !!!!
S8ntsHaz3 said:
Awesome thanks !!!!
Click to expand...
Click to collapse
Hmmm stuck at "Please Wait..."
Which method did you use to obtain root/TWRP?
S8ntsHaz3 said:
Which method did you use to obtain root/TWRP?
Click to expand...
Click to collapse
Using:
D:\Downloads\axon7root-us-b27>axon7root.exe -p 3 -r
That only gave me TWRP. I still can't get Root to work on the B27 Update.