Related
[Q] ACER Z3/z130 Europ is there a CWM recovery & zip file of the original recovery
I've misteriously bicked my phone an remain locked in the boot proces....
Time to flash a new stock rom
as I'm flashing I prefer CMW as recovery above the unclear asus one (although I would like to be able to reflash the old one [warranty issues)
Can anyone give me a pointer scanned all of google (possibly the wrong way)
Thanks in advace]
dreuzel said:
I've misteriously bicked my phone an remain locked in the boot proces....
Time to flash a new stock rom
as I'm flashing I prefer CMW as recovery above the unclear asus one (although I would like to be able to reflash the old one [warranty issues)
Can anyone give me a pointer scanned all of google (possibly the wrong way)
Thanks in advace]
Click to expand...
Click to collapse
http://us.acer.com/ac/en/US/content/drivers - Click on O.S.
You'll find your stock system there. Instructions for loading it are included in the zip downloaded. I believe the EMEA Gen1 is for the generic worldwide version, but you might want to verify that. I know that the ORGFr one is for Orange France and the little "s" at the end would signify single SIM versions.
Found this guide to install recovery:
One. Loads Famaroot Just "Framaroot-1.9.1.apk" follow the link here.
http://forum.xda-developers.com/attachment.php?s=e12cbb38af7dd8a173308bb ...
The. Apk to be installed on the Z3 - Z3s / Once installed, it's ordered by phone root app Famaroot.
Two. TWRP 2.4.4.0 files stored on your SD-Card llllllll2510 to post the link here.
https://docs.google.com/file/d/0B0XQigIT17uEcDQtaDJ3U0UtOWc/edit?pli=1
PS. Files Name TWRP24Recovery_Z130_D10-02-14.img.
Do NOT paste it in a folder deep secret I do not find.
Three. Install app "[ROOT] Recovery Tools - Flasher" on the phone to me.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Then, with a flash TWRP 2.4.4.0 [ROOT] Recovery Tools - Flasher by.
Select top (Flash Recovery) and select the top (Other from Storage).
Then browse to the file TWRP24Recovery_Z130_D10-02-14.img. Flash to order
At the end of the process [ROOT] Recovery Tools - Flasher will ask you to reboot into recovery-mode or not.
I answered yes to the reboot to check the flash recovery ... we just finished it.
NOTE ***: It may cause damage to the machine. Or insurance
You must accept the risks in the operation of your own.
I found this on a forum that was in a foreign language to me and used Google Translate to get this info. You can find the original thread here:
http://droidsans.com/node/153986
For returning to stock for warranty issues, just use the original firmware you downloaded from Acer.
Tried the first part flashing the ROM using the provided stock Roms.
That failed it downloads but as soon as first real install occurs it rejects and aborts install access or accept error.
And returns the key part of the file name
I think? No expert at all ? The stock ROM updates do not match the previous ROM on my z30. Do not exactly know the specs of my original ROM proximus.... ??? Would have preferred gen ROM overriding all that stuff?
Or do I need to force adb/ fastboot only to load the system partition.???? But what is the adb/ fastboot command then exactly do I need to expand the zip a second time? After extract zip and instruction PDF?
Will delay cwm tarp after first signs of life of the phone.
Thanks for your answer
sometimes I know.
often I do not know.
Its always good to be able to ask.
Hello everybody !
Two days ago, I bought the Acer Liquid E3 (single SIM, not Duo), and after some research and a good thinking time, I went for rooting my device. I used the instructions provided on the official thread (actually, I used this simpler and french version provided by Shreps, since that's my mother tongue, but I checked that every step was the same).
I also checked that since my device is the single sim model, it wouldn't prevent the operations to go as intended. There is no clear info about this on the thread, but some guy having the same model as me didn't complain about anything, so I assumed he was able to root his phone with no problem.
As said in the instructions, I put the UPDATE-SuperSU-v1.99.zip file on my SD card, I installed the VCOM drivers to my computer, used SP Flash Tools to flash CWM 6.0.3.0 Recovery on my device, booted in Recovery mode (it was indeed CWM Recovery that booted), then navigated to :
install zip from sdcard > choose zip from sdcard > "UPDATE-SuperSU-v1.99.zip" > Yes - Install UPDATE-SuperSU-v1.99.zip
Everything seemed to go well, no error prompted and the operations ended with "Done !"
However, when I rebooted in normal mode ("reboot system now" in CWM Recovery) and checked with Root Checker, it was said that I wasn't root. SuperSU isn't installed, and when I manually look for the su binary, it can't be found neither in bin nor in xbin.
I did everything (from flashing CWM to install root from sdcard) again and again, and nothing changes. I tried to download again my SuperSU file or use an anterior version (v1.86) but it's still the same problem.
tl;dr : I tried to root via CWM Recovery, but even if no error prompts, su isn't neither in bin nor xbin.
Would you have an idea of what I'm doing wrong ? (And would be able to explain it to me in understable terms ? Even if I understand every step I've been through, I'm not very familiar with the rooting glossary...)
Also, by looking into the SuperSU zip, I found the installation script. Would it be dangerous to try these commands manually via ADB ? Could it work where the script failed (or help find the 'root' of the problem ?)
I have a last (but secondary) question : on the tuto from the official thread and its french version, it is said that I should change the name of "/system/recovery-from-boot.p" to "/system/recovery-from-boot.p.bak" to keep my custom Recovery ROM after a reboot, or the Stock Recovery would wipe it. As I failed to root the phone, I could change this file name, of course, but however, when I boot my phone into Recovery mode (unplugged from the computer), it boots directly on CWM Recovery.
It doesn't bother me as long as I have an operating Recovery ROM, but I was wondering if it was normal since I did nothing to keep CWM.
NB : I attached to this question a screenshot of the About menu of my Device, since it contains informations on my build version and maybe other things.
THIS DOWNLOAD CENTER IS THE RESULT OF DAYS WORK UPLOADING STUFF. IT TOOK A LOT OF EFFORT TO RESUME ALL THINGS TOGETHER. SO.....E N J O Y
NOTE : use all files with caution. Read threads before use, learn and use them carefully. I am not responsible for damaging/bricking your phone or other related stuff…
NOTE 2 : When having questions : DO ASK THEM IN THE "QUESTION&ANSWERS" forum or THE RELATED THREAD ! THNX !
Now, since I am using this A2017G phone from the first release day on and therefore following all stuff regarding stock rom, root etc. (except custom ROM department) , I thought it would be useful to share all my own files, tools and other stuff that I used since day 1.
There are different threads posting about files for all variant phones together (and not always up to date) and IMO also not bundle some major specific threads for A2017G which are ,again IMO, the most useful since I bought this splendid phone.
Therefore I want this a place for the A2017G model alone and keep it up-to-date where possible.
I do not pretend this will be a one of a kind but definitely sure it will bundle some things together that new users and others can use to (re-)find directly some specific file or thread.
All credits of course goes to those who spend their time to make things work!
I will update stuff if needed.
FACTORY IMAGES DIVISION : A2017G
Since day 1 ZTE released updates/stock factory image files. Most of the files are scattered all over the place or not existing anymore.
Therefore I took ‘some’ :cyclops: time to upload all my ORIGINAL stock files from ZTE otherwise they’re only wasted data on my harddrives.
These files could be useful to go back to whatever factory image you want or extract the necessary data from it.
The files are just renamed. Rename back (f.e. “update.zip”, "recovery.img"...) where necessary or if needed in a particularly thread or flash method :
note : Like i said these files are genuine, original downloads from ZTE. So, if you're not able to update as usual through settings (put file in root of extrernal SD) or via stock recovery (either with update from SD or ADB sideload (putting file in ADB folder on your PC)) or whatever...you're doing something wrong or...you've bad luck. Anyway, try harder :fingers-crossed:
note2 : the zip files are ready to use. There are no zips in zips. So extracting or whatever is not needed.
A2017G-MM-B03 : https://www.androidfilehost.com/?fid=889764386195898861
A2017G-MM-B03 stock recovery : https://www.androidfilehost.com/?fid=889764386195898860
A2017G-MM-B03 boot : https://www.androidfilehost.com/?fid=673368273298958442
A2017G-MM-B06 : https://www.androidfilehost.com/?fid=673368273298954543
A2017G-MM-B08 : https://www.androidfilehost.com/?fid=745425885120731436
A2017G-MM-B08 stock recovery : https://www.androidfilehost.com/?fid=745425885120731415
A2017G-MM-B08 boot : https://www.androidfilehost.com/?fid=817550096634772937
A2017G-MM-B09 : https://www.androidfilehost.com/?fid=673368273298955140
A2017G-MM-B10 : https://www.androidfilehost.com/?fid=817550096634769190
A2017G-MM-B10 stock recovery : https://www.androidfilehost.com/?fid=889764386195899093
A2017G-MM-B10 boot : https://www.androidfilehost.com/?fid=673368273298958443
A2017G-MM-B11 : https://www.androidfilehost.com/?fid=529152257862726439
A2017G-MM-B11 stock recovery : https://www.androidfilehost.com/?fid=889764386195899089
A2017G-MM-B11 boot : https://www.androidfilehost.com/?fid=817550096634772938
A2017G-N-B01 : https://www.androidfilehost.com/?fid=817550096634768963
A2017G-N-B01 stock recovery : https://www.androidfilehost.com/?fid=745425885120725539
A2017G-N-B01 boot : https://www.androidfilehost.com/?fid=889764386195902947
A2017G-N-B02 : https://www.androidfilehost.com/?fid=529152257862727042
A2017G-N-B02 stock recovery : https://www.androidfilehost.com/?fid=673368273298958444
A2017G-N-B02 boot : https://www.androidfilehost.com/?fid=817550096634772939
A2017G-N-FOTA-B01 to B02 : https://www.androidfilehost.com/?fid=529152257862723162
A2017G-N-FOTA-B02 to B04 : https://www.androidfilehost.com/?fid=817550096634768949
A2017G-N-B04 (australian) : https://www.androidfilehost.com/?fid=889764386195899120
(also flashable with trons bootstack+system / IMO the most stable version @ the moment)
According to ZTE the australian version is the same as used for the OTA B04 on german devices and on new sold phones for that region
A2017G-N-B04 stock recovery : https://www.androidfilehost.com/?fid=673368273298958445
A2017G-N-B04 boot : https://www.androidfilehost.com/?fid=889764386195902948
A2017G-N-B05 (spain) : https://www.androidfilehost.com/?fid=889764386195912222
A2017G-N-B05 stock recovery : https://www.androidfilehost.com/?fid=745425885120744960
A2017G-N-B05 boot : https://www.androidfilehost.com/?fid=817550096634782427
A2017G-N-FOTA-B04 to B05 : https://www.androidfilehost.com/?fid=889764386195919032
A2017G-N-B06 (turkey) : https://www.androidfilehost.com/?fid=817550096634795481
A2017G-N-B06 stock recovery : https://www.androidfilehost.com/?fid=889764386195927517
A2017G-N-B06 boot : https://www.androidfilehost.com/?fid=961840155545593447
A2017G-N-FOTA-B05 to B08 : https://androidfilehost.com/?fid=962021903579488106
A2017G-N-B08 (germany) : https://androidfilehost.com/?fid=673791459329058532
A2017G-N-B08 boot : https://androidfilehost.com/?fid=962021903579488691
A2017G-N-B08 stock recovery : https://androidfilehost.com/?fid=817906626617942655
A2017G-N-B09 (sweden) : https://androidfilehost.com/?fid=673791459329072549
A2017G-N-B09 boot : https://androidfilehost.com/?fid=817906626617951591
A2017G-N-B09 stock recovery : https://androidfilehost.com/?fid=745849072291693720
A2017G-N-FOTA-B08 to B10 : https://androidfilehost.com/?fid=962187416754466305
A2017G-N-FOTA-B09 to B10 : https://androidfilehost.com/?fid=890129502657590984
A2017G-N-B10 : https://androidfilehost.com/?fid=746010030569960734
A2017G-N-B10 boot : https://androidfilehost.com/?fid=818070582850499639
A2017G-N-B10 stock recovery : https://androidfilehost.com/?fid=962187416754467268
A2017G-N-FOTA-B10 to B12 : https://androidfilehost.com/?fid=1322778262903993524
A2017G-N-B12 : https://dl1.ztems.com/zxmdmp/downlo...K/ZTE/ZTE A2017G/452783/fota_B15_MR_B17_MR.up
A2017G-N-B12 boot : https://www.androidfilehost.com/?fid=1322778262904001038
A2017G-N-B12 stock recovery : https://www.androidfilehost.com/?fid=1322778262904001082
A2017G-O-B02 : https://forum.xda-developers.com/showpost.php?p=78045733&postcount=35
A2017G-O-B02 boot : https://androidfilehost.com/?fid=11410932744536994029
A2017G-O-B02 stock recovery : https://androidfilehost.com/?fid=11410932744536994031
A2017G-O-B03 : http://download.ztedevices.com/support/product/548/201812051059748/sd/20181212113602035.zip
A2017G-O-B03 boot : https://androidfilehost.com/?fid=11410963190603885505
A2017G-O-B03 stock recovery : https://androidfilehost.com/?fid=11410963190603883442
TWRP flashable Bootstack/Stocksystem Images
Previous version ( MM-B09 / N-B01 / N-B02 / N-B04 ) : https://forum.xda-developers.com/axon-7/development/stock-rom-a2017g-twrp-flashable-images-t3599069
A2017G-N-B05-bootstack : https://www.androidfilehost.com/?fid=889764386195912453
A2017G-N-B05-stocksystem : https://www.androidfilehost.com/?fid=961840155545578497
(Bootstack/Stocksystem (based on B05(spain)/ remind to flash SU2.79 after flashed both files !)
A2017G-N-B06-bootstack : https://www.androidfilehost.com/?fid=673368273298981646
A2017G-N-B06-stocksystem : https://www.androidfilehost.com/?fid=817550096634795513
(Bootstack/Stocksystem (based on B06(turkey)/ remind to flash SU2.79 after flashed both files !)
A2017G-N-B08-bootstack : https://androidfilehost.com/?fid=745849072291684863
A2017G-N-B08-stocksystem : https://androidfilehost.com/?fid=962021903579488675
(Bootstack/Stocksystem (based on B08(germany)/ remind to flash SU2.79 after flashed both files !)
A2017G-N-B09-bootstack : https://androidfilehost.com/?fid=673791459329066133
A2017G-N-B09-stocksystem : https://androidfilehost.com/?fid=962021903579497339
(Bootstack/Stocksystem (based on B09(??)/ remind to flash SU2.79 after flashed both files !)
A2017G-N-B10-bootstack : https://androidfilehost.com/?fid=673956719939825932
A2017G-N-B10-stocksystem : https://androidfilehost.com/?fid=890129502657589263
(Bootstack/Stocksystem (based on B10/ remind to flash SU2.79/magisk after flashed both files !)
A2017G-N-B10-FULL EDL : https://androidfilehost.com/?fid=746010030569960045
A2017G-N-B12-bootstack : https://androidfilehost.com/?fid=1322778262903993157
A2017G-N-B12-stocksystem : https://androidfilehost.com/?fid=1322778262903993549
(Bootstack/Stocksystem (based on B12/ remind to flash SU2.79/magisk after flashed both files !)
A2017G-N-B12-FULL EDL : https://androidfilehost.com/?fid=1322778262903993129
A2017G-O-B02-bootstack : https://androidfilehost.com/?fid=11410932744536994154
A2017G-O-B02-stocksystem : https://androidfilehost.com/?fid=11410932744536994370
A2017G-O-B02-FULL EDL : https://androidfilehost.com/?fid=11410932744536993760
A2017G-O-B03-bootstack : https://androidfilehost.com/?fid=11410963190603885509
A2017G-O-B03-stocksystem : https://androidfilehost.com/?fid=11410963190603892464
A2017G-O-B03-FULL EDL : https://androidfilehost.com/?fid=11410963190603874726
ROOT DIVISION : A2017G
IMO these are the most used recurring files and threads to start from scratch and use to root, unlock your phone and play around with :
Minimal ADB FASTBOOT tool : https://www.androidfilehost.com/?fid=529152257862726185
Axon7tool : https://www.androidfilehost.com/?fid=673368273298954280 thnx @tennear
Axon7toolkit v1.2.0 : https://www.androidfilehost.com/?fid=673368273298961049 thnx @bkores
Zadig driver tool v2.2 : https://www.androidfilehost.com/?fid=529152257862726183
Zadig driver tool v2.3 : https://www.androidfilehost.com/?fid=817550096634786647
SU2.65 (MM) : https://www.androidfilehost.com/?fid=529152257862726221
SU2.79 (N) : https://www.androidfilehost.com/?fid=529152257862726223
SU2.81 (N) : https://www.androidfilehost.com/?fid=745425885120734872
SU2.82 (N) : https://www.androidfilehost.com/?fid=961840155545568721
TWRP : Most important, i repeat most important :
!!! do NOT use TWRP 3.0.2.2 version to backup/restore - you will be most unhappy with your BRICKED phone (read threads about that) !!!
!!! so do update to lastest version TWRP 3.1.0.0 or newer as soon a you can !!!
OFFICIAL
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446
TWRP 3.1.0.0 : https://www.androidfilehost.com/?fid=529152257862720448
TWRP 3.1.1.0 : https://www.androidfilehost.com/?fid=889764386195900705
(TWRP 3.2.0.0 : https://androidfilehost.com/?fid=889964283620771093)
TWRP 3.2.1.0 : https://androidfilehost.com/?fid=673791459329066789
TWRP 3.2.2.0 : https://androidfilehost.com/?fid=5862345805528041048
TWRP 3.2.3.0 : https://androidfilehost.com/?fid=5862345805528069068
TWRP 3.3.0.0 : https://androidfilehost.com/?fid=1395089523397944924
CUSTOM thnx @NFound
TWRP 3.2.1.5 : https://androidfilehost.com/?fid=746010030569951007
TWRP 3.2.1.6 : https://androidfilehost.com/?fid=890129502657585390
TWRP 3.2.1.7 : https://androidfilehost.com/?fid=673956719939822011
TWRP 3.2.1.8 : https://androidfilehost.com/?fid=962339331458997156
MiFlash tool : https://www.androidfilehost.com/?fid=673368273298954241
EDL TOOL : https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759 thnx @djkuz
THE 1 MINUTE ULTIMATE DFU UNBRICK TOOL (no more opening of device/no EDL cable needed anymore) : https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
MISCELLANEOUS :
1. JoJoc System Tuning Battery Tweak by @nfsmw_gr :
V3.2 :
*script : https://forum.xda-developers.com/axon-7/how-to/tweak-jojoc-tuning-battery-focused-t3704831
*Magiskmodule V3.2
*SuperSU zip
V2.1 :
*script : https://forum.xda-developers.com/axon-7/how-to/tweak-jojoc-tuning-battery-focused-t3704831
*Magiskmodule V2.1
*SuperSU zip
2. Lockscreen PIN, Pattern & Password remover : https://androidfilehost.com/?fid=818222786056030640
3. Universal Bootloader B15 (7.1.1) : https://androidfilehost.com/?fid=673368273298930589 thnx @Unjustified Dev
4. Remove Bootloader Unlock Warning : https://androidfilehost.com/?fid=745849072291698596
info : https://forum.xda-developers.com/axon-7/how-to/guide-remove-unlocked-bootloader-screen-t3727493
SOME THREADS to ROOT and UPDATE A2017G :
Root,unlockBL…imo the place to be ! thnx @Controllerboy
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
TWRP flashable bootstack/stocksystems thnx @tron1
https://forum.xda-developers.com/axon-7/development/stock-rom-a2017g-twrp-flashable-images-t3599069
Root, fastboot, twrp after Nougat update thnx @Choose an username...
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
....
ON REQUEST :
1. MODEMS : by @Choose an username... : modem flasher for N-B01, N-B02 and N-B04 thnx @sToRm1nG
https://www.androidfilehost.com/?w=files&flid=172381
As a matter of fact the N-B02, N-B04 and N-B05 are the same.
So different nougat modems are :
N-B01 : https://www.androidfilehost.com/?fid=745425885120724885
N-B02,4 and 5 : https://www.androidfilehost.com/?fid=961840155545591899
N-B06 : basicly the same as N-B02,4 ,5 but a very small difference in size. Therefore the upload : https://www.androidfilehost.com/?fid=817550096634795810
N-B08 : https://androidfilehost.com/?fid=889964283620762049
N-B09 : https://androidfilehost.com/?fid=962021903579497257
N-B10 : https://androidfilehost.com/?fid=890129502657589880
N-B12 : https://www.androidfilehost.com/?fid=1322778262904001054
Oreo Modem:
O-B02 : https://androidfilehost.com/?fid=11410932744536994030
O-B03 : https://androidfilehost.com/?fid=11410963190603883450
2. Initial MM-B03 system stock sounds : https://androidfilehost.com/?fid=889964283620762508 ( thnx @Kenziner )
(old upload version)https://www.androidfilehost.com/?fid=673368273298967887
3. LOS14 sounds : https://androidfilehost.com/?fid=817906626617942936
If you feel the need for a specific file to post here, just PM me or comment. Thnx !
ENJOY !
ps : report when a link is down
This thread should be pinned, as there are a lot of important links to download, for our device. Thanks for this topic!
raystef66 said:
TWRP : Most important :
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446
TWRP 3.1.0.0 : https://www.androidfilehost.com/?fid=529152257862720448
TWRP : Useful :
TWRP 3.0.3.0 : https://www.androidfilehost.com/?fid=817550096634769206
TWRP 3.0.3.1 : https://www.androidfilehost.com/?fid=529152257862726447
TWRP 3.0.4.0 : https://www.androidfilehost.com/?fid=889764386195899070
Click to expand...
Click to collapse
I think you should only leave TWRP 3.1 here, or at least leave 3.1.0-0 and 3.0.2-2 by tenfar and a huge flashy disclaimer that says not to backup anything, and update it as fast as possible
Nice thread anyways
Strange but mine (A2017G B02) do not want to update automatically via system updater. It do not want to see B02 to B04 file. Yes, I renamed it do update.zip also I was trying A2017GV1.2.0B04.zip and also I was trying all SD location eg. FOTA folder and update folder - doesn't work.
PS. I just pointed FOTA and update folders on ss.
MrMD69 said:
Strange but mine (A2017G B02) do not want to update automatically via system updater. It do not want to see B02 to B04 file. Yes, I renamed it do update.zip also I was trying A2017GV1.2.0B04.zip and also I was trying all SD location eg. FOTA folder and update folder - doesn't work.
PS. I just pointed FOTA and update folders on ss.
Click to expand...
Click to collapse
You have to throw the update to the root of the storage. No idea if it doesn't work...
One more thing - I assume you checked it wasn't compressed again?? As in, when you open the ZIP, does a bunch of random crap appear or one ZIP inside? If there's only a ZIP then decompress it and try again
MrMD69 said:
Strange but mine (A2017G B02) do not want to update automatically via system updater. It do not want to see B02 to B04 file. Yes, I renamed it do update.zip also I was trying A2017GV1.2.0B04.zip and also I was trying all SD location eg. FOTA folder and update folder - doesn't work.
PS. I just pointed FOTA and update folders on ss.
Click to expand...
Click to collapse
All files are ready to use. There are no zips in zips.
If your phone is stock you can use the B02 to B04 fota. It should work as it is an original. Perhaps wipe cache first in stock recovery.
MrMD69 said:
Strange but mine (A2017G B02) do not want to update automatically via system updater. It do not want to see B02 to B04 file. Yes, I renamed it do update.zip also I was trying A2017GV1.2.0B04.zip and also I was trying all SD location eg. FOTA folder and update folder - doesn't work.
PS. I just pointed FOTA and update folders on ss.
Click to expand...
Click to collapse
Experienced the same issue. If you can't get the system updater to detect it, just install via the stock recovery. That worked perfectly for me.
1. It isn't compressed that's a ready to go zip.
2. Was trying all possible location especially few times root location of my SD card.
3. When I trying to update via stock recovery after clicking "apply SD update" it said "you are unable to apply SD update" - that one I also was trying with different locations.
When I was updating to B02 everything worked at the first try idk what happened to my phone
EDT. Wipe cache do not resolve the trouble. Also factory reset.
MrMD69 said:
1. It isn't compressed that's a ready to go zip.
2. Was trying all possible location especially few times root location of my SD card.
3. When I trying to update via stock recovery after clicking "apply SD update" it said "you are unable to apply SD update" - that one I also was trying with different locations.
When I was updating to B02 everything worked at the first try idk what happened to my phone
EDT. Wipe cache do not resolve the trouble. Also factory reset.
Click to expand...
Click to collapse
You can try also adb sideload in recovery. Put the update.zip in the adb folder and try with the specific adb command : adb sideload update.zip
I did that once.
You can also rename the .zip to .up in all cases and try again.
MrMD69 said:
1. It isn't compressed that's a ready to go zip.
2. Was trying all possible location especially few times root location of my SD card.
3. When I trying to update via stock recovery after clicking "apply SD update" it said "you are unable to apply SD update" - that one I also was trying with different locations.
When I was updating to B02 everything worked at the first try idk what happened to my phone
EDT. Wipe cache do not resolve the trouble. Also factory reset.
Click to expand...
Click to collapse
Ha. Experienced that too ?. All you gotta do is go into settings > advanced settings > developer options and then enable OEM unlocking. Then you should have no issues in recovery.
All factory images are uploaded and ready to use :cyclops:
Managed it to update via ADB - works flawlessly - thx for helping me !
@ raystef66
Thank you for your useful post. Just to mention that TWRP just has newer version 3.1.1-0 :
https://eu.dl.twrp.me/ailsa_ii/
dnlilas said:
@ raystef66
Thank you for your useful post. Just to mention that TWRP just has newer version 3.1.1-0 :
https://eu.dl.twrp.me/ailsa_ii/
Click to expand...
Click to collapse
Thnx. Good find ! Updated thread with download link:good:
Just flash img in your TWRP
Had contact with ZTE Germany and they confirmed me today that the Australian Full B04 Nougat zip (20170505161441337.zip) is also the firmware which is distributed on new sold phones in Germany and also the OTA B04 update is based on it. So no differences as ZTE said.
Uploaded the lastest flashable SuperSU 2.81 zip
Flashed it without any issues
Damn, can someone do this for the U.S. version, I'm looking for the B29 mm official zip from ZTE's website which isn't there anymore.
Latest SuperSU 2.82
For those who feel the urgent need to update their SuperSU (again )
version 2.82 (27.05.2017) available:good:tested OK:good:
@raystef66
I suggest you to add download link to stock boot.img to all places where currently you mention stock recovery download,
for coherent and practical reasons. recovery.img and boot.img could of course be extracted from ROM zip,
but it is not easy to download the ROM (about 2.4GB) to just get recovery or boot image.
Stock boot.img are important to install SuperSU or Magisk since the utilities need to patch it.
Also to add recovery.img + boot.img for A2017G-N-B02 and A2017G-N-B04:
A2017G-N-B02 : A2017GV1.2.0B02_boot.img, A2017GV1.2.0B02_recovery.img
A2017G-N-B04 : A2017GV1.2.0B04_boot.img, A2017GV1.2.0B04_recovery.img
Thank you.
dnlilas said:
@raystef66
I suggest you to add download link to stock boot.img to all places where currently you mention stock recovery download,
for coherent and practical reasons. recovery.img and boot.img could of course be extracted from ROM zip,
but it is not easy to download the ROM (about 2.4GB) to just get recovery or boot image.
Stock boot.img are important to install SuperSU or Magisk since the utilities need to patch it.
Also to add recovery.img + boot.img for A2017G-N-B02 and A2017G-N-B04:
A2017G-N-B02 : A2017GV1.2.0B02_boot.img, A2017GV1.2.0B02_recovery.img
A2017G-N-B04 : A2017GV1.2.0B04_boot.img, A2017GV1.2.0B04_recovery.img
Thank you.
Click to expand...
Click to collapse
As most of the time recovery will do the trick i uploaded them earlier. Rest could be extracted out of rom zip.
But as i do have them all, i will look into it on your request and add them where needed. Thnx!
EDIT : UPDATED !
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step :
(not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device)
What do you need :
> Pixel 3 phone with Android 10
> Unlocked bootloader on your Pixel device
> Latest ADB and FASTBOOT tools on your computer
1 ) Download the latest Android 10 factory image for your device ("Blueline" is the regular Pixel 3) :
Link > Android 10 factory image
2 ) Extract the "boot.img" file on your phone
3 ) Download latest Magisk Manager application on your phone and install it :
Link > https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched
5 ) Enable adb debugging on your Pixel phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
9 ) When i'ts done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings and rebooting your phone.
Note that this guide is actually for using adaway. I don't know if it will work for any other root related feature on your phone.
Great guide, thanks!
ibolito said:
11 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings.
Click to expand...
Click to collapse
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
bafforosso said:
Great guide, thanks!
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
Click to expand...
Click to collapse
Thanks its done!
I get a "This site can't be reached" message when I click the link for magisk manager in step 3. Not sure if anyone else sees it.
Thank you for making this guide!
Thanks, works perfectly!
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Oberbergler said:
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Click to expand...
Click to collapse
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
ibolito said:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
Click to expand...
Click to collapse
Thanks man Everything was right but I forgot to update adb and fastboot. Now I have root
ignore me -- im idiot.
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
So I have a problem, maybe someone can help me with.
Back in March I made the following post:
"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/
Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/
Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.
So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "
After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)
So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.
I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.
Any idea what I could do? Can't run the uninstaller and can't reroot... ???
thanks!
Have you checked if your patched boot.img matches the firmware on your phone?
Well it's the same one I used to flash the firmware.
I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.
Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
GohanBurner said:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
Click to expand...
Click to collapse
I had it working before I bodged a magisk module install
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.
- Latest magisk canary
- Used the same firmware
- No errors anywhere along the way
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img
To get the patched image over to my phone. It worked out great. I was able to reboot,
and see the root in Magisk Manager.
YMMV
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
I have also tried this multiple times. No errors, but I can't edit system files or add modules.
here it is for g530fz devices :
used : twrp 1.1.1-1
lk2nd (postmarketos): 0.12.0 msm916
a/ pmos "works" (not so well) on that device
b/ unfortunately, few "bugs" "maybe related" to hardware persists, mainly in the reactivity on touchscreen when locked on inactive since a while.
c/ perf is highly to low (paradox for pmos ;-) ) to use it as a "common daily smartphone", mean : if you want to escape gafamnt, mount your server on a phone, or specific usages : it would be perfect. But dont expect it to run netflix everyday in firefox or falkon, it might freeze for "not only" a while.
d/ my documentation/software related to it :
samsung_g520fz
Partagé avec kDrive, le Cloud Éthique.
kdrive.infomaniak.com
[lien noveart/tabdigital]
[lien noveart/free]
[lien noveart/androidfilehost]
see for each link, normally a .img file. Unforunately, only 1 was able to host a gigabyte-sized, .img file.
Please note, without the following bug being not solved, that device could NOT get postmarketos installed through twrp with zip file :
Fail to sideload recovery.zip (#1962) · Issues · postmarketOS / pmbootstrap · GitLab
Phone: motorola-harpia (Moto G4 Play XT1607) Recovery: tool: TWRP version: 3.2.1-0 Zip built...
gitlab.com
In addition : Don't know what is the exact issue, but I found a case, where it was fixed: https://gitlab.com/postmarketOS/pmbootstrap/-/issues/1962 , sadly they didn't document how to solve it properly.
e/ im going on something else now.. if you want ungoogled/ungafamnted android, take lineageos14.1 (gprimeltexx), the fastest/best choice for that device, for common usage
==roll back to androstock/lineageos?==
for G530FZ :
used : twrp 1.1.1-1
lk2nd (postmarketos): 0.12.0 msm916
android stock :
**download mode :
simply use odin with a tar ROM
lineageos :
**download mode :
use heimdall or odin to flash the twrp
used : twrp 1.1.1-1
**twrp/recovery mode :
use twrp to flash the lineageos zip file (install button)
I really advise you to use lineageos14.1 (andro7) for better compatibility/performance
postmarketos :
you have to use heimdall with lk2nd in download mode
**download mode :
use heimdall to flash lk2nd, then reboot in lk2nd (power+volDown at bootup)
**lk2nd screen :
fastboot erase system && fastboot erase userdata && fastboot flash userdata /home/koala/.local/var/pmbootstrap/chroot_native/home/pmos/rootfs/samsung-gprimeltexx.img &&fastboot reboot
[unfortunately because of a bug, twrp can't flash .zip files of postmarketos, on that device - .img, heavier, are the only way I had]
well tested :
lineage 14.1, but you *might* have to odin it, regarding this :
Hi guys
regarding the G530fz to solve the problem I had to be oriented to Lineage 14.
Why the cell data was not detected? I don't know, but I discovered a way to fix it :
I was used before to install Lineage by just injecting the image file into the phone, then format the /data partition by simple wipe.
And for others phone, it was working.
Looks like on samsung models, it's requiring steps differently :
1/ use odin to reinstall stock firmware regarding all four files : BL, AP, CP, CSC. In the downloaded archive of the stock firmware, all files matchs with those option with odin. It's necessary to add these four files.
Flash it
2/ The phone will start. After finished, you can restart it, but in download mode.
3/ then use again odin, but flash it with only three files, excluding AP. Replace BL by the twrp bootloader.
4/ If at reboot, it's stuck on a recovery start, even without pushing the vol buttons, reflash it again with only BL.
5/ proceed normally to install lineage : download correct image plus arm (it's arm32 if Im right) pico or nano opengapps, copy them to the phone by usb, flash it then wipe /data.
6/ it should work.
If not, I remember I had to firstly flash by stock factory with all four files of stock archive, then only three including twrp instead of factory BL, then only BL if it's booting in loop into recovery instead normal mode.
Normally, it should, with lienage, detect sim cards.
If you just flash it with twrp by BL/odin, twrp will be installed, lineage can be installed too, but GSM/3G/LTE modules might never work (in my case, it happened like it)