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 !
Related
I've recently looked into creating my own roms for some fun and learning experience.
The device I'm testing with is a Galaxy S4 (I9505)
I flashed a rom I obtained from Sammobile, the rom is a UK version and doesn't appear to be network locked.
After flashing the device with the rom everything has been fine. I then went on to root the phone and add ClockWorkMod.
ROM FILENAME: I9505XXUHOJ2_I9505YXYHOK1_I9505XXUHOJ2_HOME.tar.md5
All has been fine up until now.
I then downloaded Android Kitchen and got it setup on Ubuntu, added the ROM in and setup the workspace as instructed by nearly all tutorials.
I then added some custom APKs and enabled custom boot animations.
After which I chose to build from the working directory and went with the lazy mode.
This is where everything stops working out well.
To start off with CWM couldn't read the ZIP archive (Of the new ROM from Kitchen)
I couldn't get CWM to mount my SDCard. I tried everything.
In the end I pushed my custom ROM to the device using `adb push`, then CWM decided it would work and install.
However after install the phone reboots and gets stuck at the boot screen with the Samsung logo.
Did I do something wrong?
It feels wrong that Android Kitchen outputs a simple ZIP Archive with the following contents:
- data
- META-INF
- system
- boot.img
- flash_image
- modem.bin
But I don't know any better, tutorials fail to mention what to specifically expect other than a ZIP Archive.
To cut it short.
The ROM worked perfectly fine when I flashed it through Odin.
However after it went through Android Kitchen with no major changes on my part (I didn't touch any files myself other than to add two APKs)
followed by installation via CWM. The ROM suddenly is no longer working and shows "Recovery is not Seandroid Enforcing" followed by a line regarding the Kernel ontop of the boot screen.
I cant full read those two lines as the corner of the screen is cracked.
What changed?
Here's the info output from Kitchen:
Working folder information (v0.224)
Android OS version : 5.0.1
Device : jflte
Model : GT-I9505
ROM Name : TMFKSOFT-I9505
CSC version : I9505YXYHOK1
Rooted (Superuser app + su) : YES
Rooted (unsecured boot.img) : YES
BusyBox installed : NO
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : YES
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : NO
/system/app is deodexed : NO
modem.bin found : YES
ROM will wipe all data : NO
Additionally, apologies if I've posted this in the incorrect topic.
I'm completely new to the forums.
Let me know where it belongs if it's in the wrong place.
Quick Edit:
I've reflashed back to the original ROM mentioned, the .tar.md5 file and the device is perfectly fine again :/
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device (and all of your apps and settings are the same)
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again ( to be sure ) - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
10. make TWRP backup when needed
11 IF YOU WANT TO UPDATE TO B02 : use this methode https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
EDIT : when you want to get rid of the bootscreen which states that you have an unlocked bootloader, follow this procedure (very easy )
https://forum.xda-developers.com/showpost.php?p=71444728&postcount=496
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
raystef66 said:
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
Click to expand...
Click to collapse
I'm on stock B29, rooted, unlocked bootloader.
Been avoiding updates, but this looks promising to keep root.
Think it will work for me? Forgot to mention I have 3.0.4 twrp
HTC55555 said:
I'm on stock B29, rooted, unlocked bootloader.
Been avoiding updates, but this looks promising to keep root.
Think it will work for me?
Click to expand...
Click to collapse
Don't know exactly.
For G users the latest update before 7.0 was the B10. Therefore B10 is the necessary flash before G users can flash N
As long as you keep TWRP running ( as far as i know do not wipe system etc...therefore i mentioned earlier to not wipe anything) and your latest backup, you can always restore it.
Hmm... I did this a week ago and forgot to flash SuperSU. Messed up big time... Axon7tool gives the what() error, but people say that even if it successfully flashes the recovery, the stock recovery remains there.
So I need the inverse process... any idea how?
Choose an username... said:
Hmm... I did this a week ago and forgot to flash SuperSU. Messed up big time... Axon7tool gives the what() error, but people say that even if it successfully flashes the recovery, the stock recovery remains there.
So I need the inverse process... any idea how?
Click to expand...
Click to collapse
Perhaps this will help : https://forum.xda-developers.com/showpost.php?p=71444519&postcount=494
unplug usb when you give command to flash twrp recovery, otherwise it always reflashes stock recovery....
Hope that helps
Thanks for the reply! I'll have to figure out how to make axon7tool work now. Much appreciated
Dear raystef66!
I'm on Resurrection Remix now-2017G (it is 7.1.1 based).I would like to have a stock 7.1.1.Can i just do the steps in your post 1,without flash b10, just flash
7.1.1 stock bootstack, system and Super SU?Would it working solution, to go from Resurrection Remix to stock 7.1.1 on 2017g?And will be twrp still prsent after those steps?
Thanks in advance!
ValVK said:
Dear raystef66!
I'm on Resurrection Remix now-2017G (it is 7.1.1 based).I would like to have a stock 7.1.1.Can i just do the steps in your post 1,without flash b10, just flash
7.1.1 stock bootstack, system and Super SU?Would it working solution, to go from Resurrection Remix to stock 7.1.1 on 2017g?And will be twrp still prsent after those steps?
Thanks in advance!
Click to expand...
Click to collapse
IMO you have to flash b10 too. Would do no harm though as long as you don't fully wipe system to keep twrp. As long as you keep a backup of twrp you can always go back. In worst case you have to flash twrp again in edl axon7tool.
@ValVK I flashed B03, then B08, then B10, and THEN B01, like any normal update. That because I don't know if B10 is only an incremental update
But after you flash the stock system, remember to root! You'll lose TWRP otherwise
Thanks all for responces! If i will go that way-flash in Twrp b08, then b10 and then Nuga, what should i wipe first in Twrp-all inclusive System, or just Factory reset? And if i will go that way, should my Twrp still intakt? (I would like avoid to Flash Twrp again, seems bit risky for me).
I had the official bootloader unlock but it broke the com.android.phone process on 7.1.1.
They are working on getting it fixed and once fixed will make the root publicly avialble.
The official root works on b10 marshmallow and is very easy to install.
@ValVK o sorry, I only flashed B03 :silly:
You should flash B03 THEN update via the native sdcard update on mifavor
raystef66 said:
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device (and all of your apps and settings are the same)
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again ( to be sure ) - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
10. make TWRP backup when needed
EDIT : when you want to get rid of the bootscreen which states that you have an unlocked bootloader, follow this procedure (very easy )
https://forum.xda-developers.com/showpost.php?p=71444728&postcount=496
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
Click to expand...
Click to collapse
Hi, I am on the stock rom 7.0 nougat for the A2017G.
Can I just flash the leaked rom 7.1.1 for a2017g model??, I have no root, total stock.
Oliver Aa said:
Hi, I am on the stock rom 7.0 nougat for the A2017G.
Can I just flash the leaked rom 7.1.1 for a2017g model??, I have no root, total stock.
Click to expand...
Click to collapse
I suggest you wait for the 7.1.1 OTA update when you're not rooted etc.
I flashed through twrp the package made by tron1 for android 7.1.1 , the bootstack and supersu to make sure i have root install at the first boot but for some reason supersu framework gets deleted. I tried flashing supersu package multiple times and it gets deleted after boot up . How could i fix this ?
S0wL said:
I flashed through twrp the package made by tron1 for android 7.1.1 , the bootstack and supersu to make sure i have root install at the first boot but for some reason supersu framework gets deleted. I tried flashing supersu package multiple times and it gets deleted after boot up . How could i fix this ?
Click to expand...
Click to collapse
Did you follow my steps ? From which version did you come ? Were you already rooted....
Perhaps flash SU 2.79 (!) in edl mode and when it is resetting for a reboot, unplug your phone before it can reboot. You get a black screen. Just press Vol+/Power and when you see ZTE logo you release. Normaly you should/can enter TWRP.
But normaly my guide should work if you were rooted, BL unlocked and on stock ROM (B08 or earlier). I do not know which steps you already performed so it's just gessing.
What you guys think??
I want to know if I update my phone to this version, can I continue using xposed
Hello, can someone create TWRP files from the new B02 image?
Gesendet von meinem ZTE A2017G mit Tapatalk
@raystef66
I have a question:
Can step 8) be skipped? (flash 7.0=A2017GV1.1.0B01 bootstack and system, flash SU2.79).
Since in step 9) we will flash immediately 7.1.1B01=A2017GV1.2.0B01 bootstack and system, and flash SU2.79.
I guess step 8) is harmless, but not necessary. Is it true? Or are there other reasons for this?
Also maybe you could at end of this guide add a link to your another guide
https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
which continues the upgrade to 7.1.1B02=A2017GV1.2.0B02 keeping TWRP, unlock, fastboot and root?
Thank you.
dnlilas said:
@raystef66
I have a question:
Can step 8) be skipped? (flash 7.0=A2017GV1.1.0B01 bootstack and system, flash SU2.79).
Since in step 9) we will flash immediately 7.1.1B01=A2017GV1.2.0B01 bootstack and system, and flash SU2.79.
I guess step 8) is harmless, but not necessary. Is it true? Or are there other reasons for this?
Also maybe you could at end of this guide add a link to your another guide
https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
which continues the upgrade to 7.1.1B02=A2017GV1.2.0B02 keeping TWRP, unlock, fastboot and root?
Thank you.
Click to expand...
Click to collapse
IMO step 8 can not be skipped due to the fact you have to have 7.0 first. Could be wrong, but then again, it only last for a minute or so
I will ad the link to upgrade B01 to B02.
Thnx !
ps : did you get B02 with my method ? Pls post on thread if succeeded - thnx !
K6 POWER SOFTWARE UPDATE LINKS
s156 to s223 download link: http://phonedl.ota.lenovomm.com/dls/v6/K33_S156_170220_ROW_TO_K33_S223_170610_ROW_WC460DDB76.zip
(Thanks to NanuZn)
s222 to s223 download link:
http://phonedl.ota.lenovomm.com/dls/v6/K33_S222_170523_ROW_TO_K33_S223_170610_ROW_WCD418A4CF.zip
(Thanks to EthannSiva)
s156 to s222 download link: https://www.androidfilehost.com/?fid=745425885120738879
(Thanks to Karthick)
s150 to s156 download link:
http://phonedl.ota.lenovomm.com/dls/v6/K33_S150_161114_ROW_TO_K33_S156_170220_ROW_WCB6723108.zip
( Note: 1.Use stock recovery to flash... Rename ota.zip to update.zip... Put that update.zip file in root of sd card. 2. If you want to flash using twrp recovery, you need to edit updater-script to do so.)
UNLOCK BOOTLOADER SIMPLE GUIDE
Enable adb and OEM options in developer settings and conect your k6 via usb(also you need to download adb and fastboot utilities for your PC).
in CMD or a GNU/Linux Terminal you will need paste one per one line.
Code:
adb reboot bootloader
fastboot -i 0x17ef oem device-info echo "check bl"
fastboot -i 0x17ef oem unlock-go
INSTALL RECOVERY
You can get the recovery from karthick thread:
https://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-lenovo-vibe-k6-t3618912
Code:
fastboot -i 0x17ef flash recovery <recovery Name>.img
ROOT
just flash super su zip from chainfire in your recovery
You can find it here:
http://www.supersu.com/download
How to flash stock s156-s223 nougat OTA zip using TWRP recovery?
1. open OTA zip file in X-plore file manager..
2. Go to folder meta-inf/com/google/Android where updater-script has been located
3. Open updater-script as a txt(text) file in X-plore file manager & delete first & second line. (Stop when word ui-print come)
4. Go to menu, save it.. it will take several seconds/minutes to get saved changes.
5. Go to TWRP recovery & flash.
6. Enjoy stock nougat 7.0 for Lenovo k6 power.
OUR TELEGRAM GROUP
https://t.me/joinchat/AAAAAEPrej6nmzca5GK_fw
MANY THANKS FOR OUR COMMUNITY ON TELGRAM AND; @siva1234
STR4NG3R-GUY said:
K6 POWER SOFTWARE UPDATE LINKS
s156 to s223 download link: http://phonedl.ota.lenovomm.com/dls/v6/K33_S156_170220_ROW_TO_K33_S223_170610_ROW_WC460DDB76.zip
(Thanks to NanuZn)
s222 to s223 download link:
http://phonedl.ota.lenovomm.com/dls/v6/K33_S222_170523_ROW_TO_K33_S223_170610_ROW_WCD418A4CF.zip
(Thanks to EthannSiva)
s156 to s222 download link: https://www.androidfilehost.com/?fid=745425885120738879
(Thanks to Karthick)
s150 to s156 download link:
http://phonedl.ota.lenovomm.com/dls/v6/K33_S150_161114_ROW_TO_K33_S156_170220_ROW_WCB6723108.zip
( Note: 1.Use stock recovery to flash... Rename ota.zip to update.zip... Put that update.zip file in root of sd card. 2. If you want to flash using twrp recovery, you need to edit updater-script to do so.)
UNLOCK BOOTLOADER SIMPLE GUIDE
Enable adb developer settings and conect your k6 via usb(also you need to download adb and fastboot utilities).
INSTALL RECOVERY
You can get the recovery from karthick thread:
https://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-lenovo-vibe-k6-t3618912
ROOT
just flash super su zip from chainfire in your recovery
How to flash stock s156-s223 nougat OTA zip using TWRP recovery?
1. open OTA zip file in X-plore file manager..
2. Go to folder meta-inf/com/google/Android where updater-script has been located
3. Open updater-script as a txt(text) file in X-plore file manager & delete first & second line. (Stop when word ui-print come)
4. Go to menu, save it.. it will take several seconds/minutes to get saved changes.
5. Go to TWRP recovery & flash.
6. Enjoy stock nougat 7.0 for Lenovo k6 power.
OUR TELEGRAM GROUP
https://t.me/joinchat/AAAAAEPrej6nmzca5GK_fw
MANY THANKS FOR OUR COMMUNITY ON TELGRAM AND; @siva1234
Click to expand...
Click to collapse
:good:
Useful guide. Do you think bootloader re-lock and flashback stock recovery are also possible?
roti86 said:
Useful guide. Do you think bootloader re-lock and flashback stock recovery are also possible?
Click to expand...
Click to collapse
Yes and yes.
Sorry for the to late reply, if you want install stock recovery download your firmware and flash the recovery via fastboot, but if you want go back to stock flash the firmware via qfil(be careful and make a backup on your external storage if you lost the imei(efs, baseband) you can restore via your backup of TWRP).
recently bought k6 power,It came with marsmallow s150 and asked to update marshmallow s156.It was about 75mb.
After it,asked for nougat s223 which i know that has lots of bugs now.So ignored the update and simply disabled update notification
I'll stick with s156 till there is a clear cut bug free nougat version.No need to install unless i want headache
Lenovo has bad reputation for updating their devices.They ruin the next version of android.Simply disaster.
So I would all advise you to stick with s156.
Bro update to S229 .it has fixed some bugs nd ui becomes smoother then previous.
Hello
I have updated to s229 by system update, i want to go back to s156.
I m on official rom. Can you guys please help?
Can i use the full ota zip to downgrade? If no then, is there any way to get the official link to download rom, i don't trust the rom from other sources and file sharing sites.
Thanks
I never had issue on s 223 even just reset your device after upgrading android ....
welcome ,
Moto One Power Stock Rom Twrp Flashable
with bootloop protection , Flashes are done inside fastboot environment
and you will experience a aroma based hyper shell user interface.
things You need
Full stock room zip download below
Twrp Installer zip v3.2.x : link Thanks to @lalitjoshi06
Motorola One Power , ofcourse
Steps to flash :
If you are in custom rom or stock rom steps are all same
boot to twrp
flash the zip
Do not wipe or erase anything all are automated , just reboot Twrp and flash the zip
PS: FULL STOCK ROM can take a little while to flash . have patience.
PSo not wipe or erase anything all are coded to be done automatically
just boot Twrp an flash the zip
Download Link : here
XDA:DevDB Information
Stock ROM and Firmware for TWRP, ROM for the Motorola One Power
Contributors
nageen9211, [email protected]
ROM OS Version: 9.x Pie
Version Information
Status: Stable
Created 2019-03-29
Last Updated 2019-08-19
Reserved
Download Links
Nov,2018
Firmware Link : Download
Feb,2019
Full ROM link : Download
Firmware Link : Downlaod
March,2019 (PPT29.74-41-2
Full ROM link : Download | Install Instructions {Credits : @[email protected]
FIrmware Link : Download
April,2019:
Full ROM : download
Firmware link : download
March SP STOCK ROM Installation Instrucions:
All credits to : @[email protected]
All the files in the zip are pure fastboot files (sparsechunks)
INTRODUCING MOTO ONE POWER TWRP FLASHABLE VERY PURE STOCK ROM PPTS29.74-41-2
*The zip is created with fastboot environment and it flash the phone as how the fastboot in pc flashes .
*Instructions
*boot to twrp
*Important (unmount all parrions in twrp )
*You no need to wipe anything all wipes will be done inside fastboot environment
*Just unmount all partitions and flash the zip
nageen9211 said:
March SP STOCK ROM Installation Instrucions:
All credits to : @[email protected]
All the files in the zip are pure fastboot files (sparsechunks)
INTRODUCING MOTO ONE POWER TWRP FLASHABLE VERY PURE STOCK ROM PPTS29.74-41-2
*The zip is created with fastboot environment and it flash the phone as how the fastboot in pc flashes .
*Instructions
*boot to twrp
*Important (unmount all parrions in twrp )
*You no need to wipe anything all wipes will be done inside fastboot environment
*Just unmount all partitions and flash the zip
Click to expand...
Click to collapse
Do you have a guide on how to make a stock flash zip file. I want make one for my device as well. Or if I give you the files can you help me out?:fingers-crossed:
xperia_bird said:
Do you have a guide on how to make a stock flash zip file. I want make one for my device as well. Or if I give you the files can you help me out?:fingers-crossed:
Click to expand...
Click to collapse
#OT
it might vary from device to device.. in this what i did is:
* extracted partition dump from device using adb shell(need root)
Code:
dd if=/path/to/partition/ of=/sdcard/or/anything
* then made the zip (You can use mine just replace the files with your device correct files.. and you are good to go.
* othe guy did more amazing hacks.. like he made some fastboot envoronment in twrp and directly made zip from fastboot images.. although those images are pretty much same as extracted from sdb but sparsed you can have look on them too
hope it helped
nageen9211 said:
#OT
it might vary from device to device.. in this what i did is:
* extracted partition dump from device using adb shell(need root)
* then made the zip (You can use mine just replace the files with your device correct files.. and you are good to go.
* othe guy did more amazing hacks.. like he made some fastboot envoronment in twrp and directly made zip from fastboot images.. although those images are pretty much same as extracted from sdb but sparsed you can have look on them too
hope it helped
Click to expand...
Click to collapse
Thankyou for Reply and I want to try it. Because it might help me to get back to stock. But only problem is I have a stock rom on my computer. In my device is a custom rom installed. And cant go back to stock, because my device gets in bootloop after flashing stock rom.
Do you think when I make a flash zip, that I can bypass bootloop?
Bootlooping
xperia_bird said:
Thankyou for Reply and I want to try it. Because it might help me to get back to stock. But only problem is I have a stock rom on my computer. In my device is a custom rom installed. And cant go back to stock, because my device gets in bootloop after flashing stock rom.
Do you think when I make a flash zip, that I can bypass bootloop?
Click to expand...
Click to collapse
First you need to find the reason for bootlooping then only making the stock zip is possible
Actually installing stock ROM from pc should not give bootlooping if bootloop occcrs you messed up with files check whether the files belonging to your device model reply with device model and other stuffs
[email protected] said:
First you need to find the reason for bootlooping then only making the stock zip is possible
Actually installing stock ROM from pc should not give bootlooping if bootloop occcrs you messed up with files check whether the files belonging to your device model reply with device model and other stuffs
Click to expand...
Click to collapse
But how to take a log if i cant enter system or connect adb for trying find the reason of bootloop.
Do you maybe know a way?
xperia_bird said:
But how to take a log if i cant enter system or connect adb for trying find the reason of bootloop.
Do you maybe know a way?
Click to expand...
Click to collapse
Your device and model
[email protected] said:
Your device and model
Click to expand...
Click to collapse
Lenovo Z5, L78011.
nageen9211 said:
March SP STOCK ROM Installation Instrucions:
All credits to : @[email protected]
All the files in the zip are pure fastboot files (sparsechunks)
INTRODUCING MOTO ONE POWER TWRP FLASHABLE VERY PURE STOCK ROM PPTS29.74-41-2
*The zip is created with fastboot environment and it flash the phone as how the fastboot in pc flashes .
*Instructions
*boot to twrp
*Important (unmount all parrions in twrp )
*You no need to wipe anything all wipes will be done inside fastboot environment
*Just unmount all partitions and flash the zip
Click to expand...
Click to collapse
I tried an AOSP Rom and found out that VoLTE is not working. So I flashed to stock using this method.
All is now working, but I am repeatedly getting this error message regarding Motorola update being unsuccessful, which is burning down my battery faster.
What can I do about it?.
Please help.
Plz make multirom twrp for moto one
anurag_xpert said:
I tried an AOSP Rom and found out that VoLTE is not working. So I flashed to stock using this method.
All is now working, but I am repeatedly getting this error message regarding Motorola update being unsuccessful, which is burning down my battery faster.
What can I do about it?.
Please help.
Click to expand...
Click to collapse
is there any update available.. update that with fastboot firmware.. becuase for som ereason it cannot update for you..
nageen9211 said:
is there any update available.. update that with fastboot firmware.. becuase for som ereason it cannot update for you..
Click to expand...
Click to collapse
Thanks for the reply. I have downladed april fastboot flashable rom from Mororola updates (link shared at telegram channel) but when i unpacked it, there was no flash script inside, so I could not flash that stock rom and I am still getting this error.
If you or somebody can share that flashall.bat script, i will be thankful.
edit: managed to flash the latest official firmware using youtube tutorial by andro guruji.
All my data was also safe.
Thanks again.
Will I get official updates after flashing this stock rom??
flashall.bat error
nageen9211 said:
Download Links
Nov,2018
Firmware Link : Download
Feb,2019
Full ROM link : Download
Firmware Link : Downlaod
March,2019 (PPT29.74-41-2
Full ROM link : Download | Install Instructions {Credits : @[email protected]
FIrmware Link : Download
April,2019:
Full ROM : download
Firmware link : download
Click to expand...
Click to collapse
i got factory rom ie .tar file for moto one power
i try to flash from fastboot and using flashall.bat in the stock rom folwer it show error
the system cannot find the path specification
how to get ride from this
Directory error
lbcsc.clx said:
i got factory rom ie .tar file for moto one power
i try to flash from fastboot and using flashall.bat in the stock rom folwer it show error
the system cannot find the path specification
how to get ride from this
Click to expand...
Click to collapse
Do not open cmd directly go to the folder where your Moto system files present and press shift and write click then press open command window here then type fastboot commands
[email protected] said:
Do not open cmd directly go to the folder where your Moto system files present and press shift and write click then press open command window here then type fastboot commands
Click to expand...
Click to collapse
See the cmd in screenshot below
nageen9211 said:
Download Links
Nov,2018
Firmware Link : Download
Feb,2019
Full ROM link : Download
Firmware Link : Downlaod
March,2019 (PPT29.74-41-2
Full ROM link : Download | Install Instructions {Credits : @[email protected]
FIrmware Link : Download
April,2019:
Full ROM : download
Firmware link : download
Click to expand...
Click to collapse
Can you please post the link for the july patch or if possible please provide the link for july full stock rom. I am not able to update via OTP. Tried everything.
nageen9211 said:
welcome ,
Moto One Power Stock Rom Twrp Flashable
with bootloop protection , Flashes are done inside fastboot environment
and you will experience a aroma based hyper shell user interface.
things You need
Full stock room zip download below
Twrp Installer zip v3.2.x : link Thanks to @lalitjoshi06
Motorola One Power , ofcourse
Steps to flash :
If you are in custom rom or stock rom steps are all same
boot to twrp
flash the zip
Do not wipe or erase anything all are automated , just reboot Twrp and flash the zip
PS: FULL STOCK ROM can take a little while to flash . have patience.
PSo not wipe or erase anything all are coded to be done automatically
just boot Twrp an flash the zip
Download Link : here
XDA:DevDB Information
Stock ROM and Firmware for TWRP, ROM for the Motorola One Power
Contributors
nageen9211, [email protected]
ROM OS Version: 9.x Pie
Version Information
Status: Stable
Created 2019-03-29
Last Updated 2019-08-19
Click to expand...
Click to collapse
hi i am bricked my moto
now i back to fast boot mod
how can i flash stock rom by twrp?
help me
i am horrified to brick my device again
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)