Related
i have moto e2 xt1506 ...i tried to update it manually but instead i think i downgraded it....lol
now my device wont boot up its just showing boot menu....i clicked everything Normal powerup, Recovery, Factory but still its showing that menu again...
version downgraded for boot..
failed to validate boot image
fastboot reason : fall-through from normal boot mode
i think my ROM is busted...any solution to this? anyone?
rootedmind said:
i have moto e2 xt1506 ...i tried to update it manually but instead i think i downgraded it....lol
now my device wont boot up its just showing boot menu....i clicked everything Normal powerup, Recovery, Factory but still its showing that menu again...
version downgraded for boot..
failed to validate boot image
fastboot reason : fall-through from normal boot mode
i think my ROM is busted...any solution to this? anyone?
Click to expand...
Click to collapse
Idk why are you on 5.0
Anyways, get minimal fastboot and adb.
Flash twrp recovery built for Otus (Don't flash for surnia!)
That's it! Now you have an arsenal of ROMs! I use resurrection remix. Provides immence customization. But that's your choice. If you want simple and stock, AOSP is there. Resurrection for customization... Use CyanogenMod for having something in between customization and simple . all links can be found in the Original Android development section.
Happy Flashing!
PseudoDev said:
Idk why are you on 5.0
Anyways, get minimal fastboot and adb.
Flash twrp recovery built for Otus (Don't flash for surnia!)
That's it! Now you have an arsenal of ROMs! I use resurrection remix. Provides immence customization. But that's your choice. If you want simple and stock, AOSP is there. Resurrection for customization... Use CyanogenMod for having something in between customization and simple . all links can be found in the Original Android development section.
Happy Flashing!
Click to expand...
Click to collapse
thnx for reply some how i manged to make it to stock os...but as you suggested i will try to flash with others ROMs as well...:good:
Unfortunately Google Play Services Has Stopped Error
rootedmind said:
thnx for reply some how i manged to make it to stock os...but as you suggested i will try to flash with others ROMs as well...:good:
Click to expand...
Click to collapse
hey hi i flashed moto otus with cm-13.0-20160621-NIGHTLY-otus.zip ( 2016-06-21 ) and gapps after that.
after update i got Unfortunately Setup wizard Has Stopped Error...i managed to stop it but now i am getting Unfortunately Google Play Services Has Stopped Error this.
have you got any such error?
any solution? anyone?
Hi,
my OPX is currently running:
Android V5.1.1
Oxygen v2.2.3
and I'm looking to update to MM, either Oxygen or CM.
When I try the offered OTA Oxygen update, Oxygen 3.1.3, it fails to update.
When I try to do it via recovery, using OnePlusXOxygen_14_OTA_018_all_201609291837_741146bcf28e4587.zip, it installs but then hangs on reboot.
My bootloader is unlocked:
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
I'm running the stock recovery, but when I try to update it, I get this message:
Code:
fastboot boot OPX_MM_recovery.img
downloading 'boot.img'...
OKAY [ 5.575s]
booting...
FAILED (remote: dtb not found)
finished. total time: 6.908s
I've tried other recoveries, Sultan-TWRP-onyx-3.0.2-3_2016-10-23.zip, twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img, twrp-3.0.2-0-onyx-20161102-155427.img, all with the same result.
Any help welcome please!
maxnutter said:
Hi,
my OPX is currently running:
Android V5.1.1
Oxygen v2.2.3
and I'm looking to update to MM, either Oxygen or CM.
When I try the offered OTA Oxygen update, Oxygen 3.1.3, it fails to update.
When I try to do it via recovery, using OnePlusXOxygen_14_OTA_018_all_201609291837_741146bcf28e4587.zip, it installs but then hangs on reboot.
My bootloader is unlocked:
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
I'm running the stock recovery, but when I try to update it, I get this message:
Code:
fastboot boot OPX_MM_recovery.img
downloading 'boot.img'...
OKAY [ 5.575s]
booting...
FAILED (remote: dtb not found)
finished. total time: 6.908s
I've tried other recoveries, Sultan-TWRP-onyx-3.0.2-3_2016-10-23.zip, twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img, twrp-3.0.2-0-onyx-20161102-155427.img, all with the same result.
Any help welcome please!
Click to expand...
Click to collapse
U cannot update to mm recovery while u r in lollipop... So the opx mm recovery will not boot... Try reflashing opx stock lollipop recovery and then try to flash the ota 3.1.3
cva_kabil said:
U cannot update to mm recovery while u r in lollipop... So the opx mm recovery will not boot... Try reflashing opx stock lollipop recovery and then try to flash the ota 3.1.3
Click to expand...
Click to collapse
I've tried that numerous times and it doesn't work.
Is the mm recovery needed after the device is updated to MM?
Yes this is obvious, mm recovery is needed when you updated on mm os.
You can try to install fresh os lollipop with stock recovery, if all the things goes right,
Then try to install mm version of os 3.1.3 through stock recovery.
yuv93 said:
Yes this is obvious, mm recovery is needed when you updated on mm os.
You can try to install fresh os lollipop with stock recovery, if all the things goes right,
Then try to install mm version of os 3.1.3 through stock recovery.
Click to expand...
Click to collapse
It's not that obvious, I thought maybe you needed mm recovery to install mm, seeing as I can't get mm to install through lollipop recovery!
I've got lollipop OS, lollipop recovery, and MM update won't boot after installation.
maxnutter said:
I've tried that numerous times and it doesn't work.
Is the mm recovery needed after the device is updated to MM?
Click to expand...
Click to collapse
As u said before wen u flash 3.1.3 it hangs on reboot right? So wen u reboot manually again u r back to 2.2.3? Is it so?
There may be a problem with ur 3.1.3 zip file redownload it from here https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip and flash it
If that fails Try the following methods but i am not sure, hope it works
Lollipop stock recovery https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
Reflash this recovery in fastboot mode
Now try updating to marshmellow via recovery
If its not working then try this method
1.take a backup of all your apps contacts etc.,
2.try to revert back to 2.2.2 by flashing this - http://oxygenos.oneplus.net.s3.amaz...OTA_012_all_201607282126_44490f44e82446dc.zip do clear data and cache before flashing
3.Now go to recovery and flash 3.1.3 @maxnutter
Yes, that's right.
Flash 3.1.3, fails to boot.
Re flash 2.2.3, boots OK.
Sent from my ONE E1003 using Tapatalk
cva_kabil said:
As u said before wen u flash 3.1.3 it hangs on reboot right? So wen u reboot manually again u r back to 2.2.3? Is it so?
There may be a problem with ur 3.1.3 zip file redownload it from here https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip and flash it
If that fails Try the following methods but i am not sure, hope it works
Lollipop stock recovery https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
Reflash this recovery in fastboot mode
Now try updating to marshmellow via recovery
If its not working then try this method
1.take a backup of all your apps contacts etc.,
2.try to revert back to 2.2.2 by flashing this - http://oxygenos.oneplus.net.s3.amaz...OTA_012_all_201607282126_44490f44e82446dc.zip do clear data and cache before flashing
3.Now go to recovery and flash 3.1.3 @maxnutter
Click to expand...
Click to collapse
The first two don't work. Might try the last one over the weekend. Thanks.
maxnutter said:
The first two don't work. Might try the last one over the weekend. Thanks.
Click to expand...
Click to collapse
if you're on stock lollipop recovery just flash the full ROM 3.1. 3 zip within recovery mode. that's it.
*wipe data,dalvik,cache are recommended (factory reset).
seacowx said:
if you're on stock lollipop recovery just flash the full ROM 3.1. 3 zip within recovery mode. that's it.
*wipe data,dalvik,cache are recommended (factory reset).
Click to expand...
Click to collapse
He said he already tried it so many times
cva_kabil said:
He said he already tried it so many times
Click to expand...
Click to collapse
then he might missed something back there. 99 out of 100 was succeeded. and i've done twice from 2.2.1 and 2.2.3 to 3.1.3, nothing troubles if you doing it with proper ways.
I'll give it another go on Monday.
FYI, I soft bricked it, then recovered back to stock Rome and recovery (2.2.1?). It happily downloaded the 2.2.3 OTA update, but won't do 3.1.3.
Sent from my ONE E1003 using Tapatalk
Does the bootloader need to be locked for OTA? It's unlocked atm, so maybe that is causing the problem?
Sent from my ONE E1003 using Tapatalk
maxnutter said:
Does the bootloader need to be locked for OTA? It's unlocked atm, so maybe that is causing the problem?
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
the full ROM zip you wrote earlier that was exactly the same ver./number like mine. just make sure you ain't got the corrupted one.
no, bootloader needs to be unlocked all the time. or else you'll end up softbrick or even worse.
PS: I never did OTA update, I always flashed full ROM zip. it less errors and troubles. *clean flash more better
edit: you should try directly flash 3.1.3 from 2.2.1 (I only did factory reset) while 2.2.3 I did fully wipe system,data,etc.
seacowx said:
the full ROM zip you wrote earlier that was exactly the same ver./number like mine. the size should be 760.25 mb. (I checked with es file explorer pro). just to make sure you ain't got the corrupted one.
no, bootloader needs to be unlocked all the time. or else you'll end up softbrick or even worse.
PS: I never did OTA update, I always flashed full ROM zip. it less errors and troubles. *clean flash more better
edit: you should try directly flash 3.1.3 from 2.2.1 (I only did factory reset) while 2.2.3 I did fully wipe system,data,etc.
Click to expand...
Click to collapse
Is the bootloader unlocked out of the box?
Sent from my ONE E1003 using Tapatalk
maxnutter said:
Is the bootloader unlocked out of the box?
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
of course not. we do :
Code:
fastboot oem unlock
to get unlocked.
seacowx said:
of course not. we do :
Code:
fastboot oem unlock
to get unlocked.
Click to expand...
Click to collapse
So OTA shouldn't need the bootloader to be unlocked.
Sent from my ONE E1003 using Tapatalk
maxnutter said:
So OTA shouldn't need the bootloader to be unlocked.
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
I don't know about that, never did OTA update since I'm always rooted and modified system. but flashing new ROM/custom ROM needed unlocked bootloader. and as far as I know you need stock recovery in order to install OTA update.
seacowx said:
I don't know about that, never did OTA update since I'm always rooted and modified system. but flashing new ROM/custom ROM needed unlocked bootloader. and as far as I know you need stock recovery in order to install OTA update.
Click to expand...
Click to collapse
Pretty sure I have stock, the one with the Chinese text on the first menu, right?
Just wondering if unlocking the bootloader prevents the OTA update working.
Sent from my ONE E1003 using Tapatalk
maxnutter said:
Pretty sure I have stock, the one with the Chinese text on the first menu, right?
Just wondering if unlocking the bootloader prevents the OTA update working.
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
yes, as far as i remember. you could choose 'english' either in start menu.
no, the only thing that prevent you gt OTA update is rooted or modified system partition. or else you're on different ROM, indeed.
well, good luck with yours then.
I was flashing paranoid android 6.0.2 for my device. I downloaded the zip(from the official paranoid android website) and checked the md5 checksum, which did not match. However, like a total idiot, I flashed it nonetheless. On booting, the phone gets stuck on the boot logo. I tried booting into recovery(TWRP) and performing a factory reset to no avail. I redownloaded the flashable zip for Paranoid, successfully verified the md5 checksum and flashed it again, no avail. Restore a full backup from within TWRP, no avail. My phone still gets stuck on the bootlogo. I have looked all over every forum without any results. Please help me out? I would like to get it back to functional state and flash the rom again. As mentioned, I have access to my custom recovery and can connect to my device via fastboot. I am willing to give any other information you may need.
Thanks!
Shreyas
shreyasminocha said:
I was flashing paranoid android 6.0.2 for my device. I downloaded the zip(from the official paranoid android website) and checked the md5 checksum, which did not match. However, like a total idiot, I flashed it nonetheless. On booting, the phone gets stuck on the boot logo. I tried booting into recovery(TWRP) and performing a factory reset to no avail. I redownloaded the flashable zip for Paranoid, successfully verified the md5 checksum and flashed it again, no avail. Restore a full backup from within TWRP, no avail. My phone still gets stuck on the bootlogo. I have looked all over every forum without any results. Please help me out? I would like to get it back to functional state and flash the rom again. As mentioned, I have access to my custom recovery and can connect to my device via fastboot. I am willing to give any other information you may need.
Thanks!
Shreyas
Click to expand...
Click to collapse
What was your last rom? Did u upgrade ur bootloader?
You probably looking at mega unbrick guide
cva_kabil said:
What was your last rom? Did u upgrade ur bootloader?
Click to expand...
Click to collapse
I was running stock OxygenOS(>3.0.0) ROM.
shreyasminocha said:
I was running stock OxygenOS(>3.0.0) ROM.
Click to expand...
Click to collapse
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
cva_kabil said:
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
Click to expand...
Click to collapse
That said, should I follow a bricked guide before doing the above?
cva_kabil said:
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
Click to expand...
Click to collapse
Also, is there any way I can downgrade my bootloader?
shreyasminocha said:
Also, is there any way I can downgrade my bootloader?
Click to expand...
Click to collapse
Flash any 2.X.X ROM. One way is to fastboot flash old stock recovery and flash safest way I think. The other is to flash with twrp make sure after flashing the ROM to flash old twrp IMG after. Make sure you boot right back into twrp.
shreyasminocha said:
Also, is there any way I can downgrade my bootloader?
Click to expand...
Click to collapse
Assuming you're on OOS3 with TWRP for new bootloader,
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Flash twrp for old bootloader via fastboot, use this one https://dl.twrp.me/onyx/twrp-3.0.2-0-onyx.img
Done
-Now u hv sucessfully downgraded ur bootloader,flash PA or any supported roms
Used mega unbrick tool because I was unable to unlock bootloader and now I'm stuck at 1+ logo (powered by android disappears quickly), did you solve it?
edit: nevermind, adb sideload with stock OOS fixed it.
TravaPL said:
Used mega unbrick tool because I was unable to unlock bootloader and now I'm stuck at 1+ logo (powered by android disappears quickly), did you solve it?
edit: nevermind, adb sideload with stock OOS fixed it.
Click to expand...
Click to collapse
Tried mega unbrick. (bootloop)
Tried OOS3.1.4.zip via stock recovery and success message apears after installation but still bootloop (previusly it was on CM13)
Tried ADB sideload (but not booting)
i have access to ADB and Fastboot.
please help :crying:
iamsandiprathva said:
Tried mega unbrick. (bootloop)
Tried OOS3.1.4.zip via stock recovery and success message apears after installation but still bootloop (previusly it was on CM13)
Tried ADB sideload (but not booting)
i have access to ADB and Fastboot.
please help :crying:
Click to expand...
Click to collapse
Did you managed to sort it out? How?
Mega unbricked guide?
I accidentally flashed a Retail US version on my Moto Z Retail EU, and now I am having a "bad key" at the Warning on boot up. Can someone provide me with a 7.1.1 or 7.0 link for Retail EU for the XT1650-03? It's for the normal Moto Z, not Play or Force. I NEED an Retail EU Boot as I flashed a wrong one and I cannot go back to 6.0.1 to fix it, so my Boot is broken until someone gives me a proper EU one for 7.0 or 7.1.
Thanks in advance!
Note: I am getting this when trying to flash the "XT1650-03_GRIFFIN_7.0_NPLS25.86-17-3-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" files:
D:\MAIN FOLDER\Android\Moto Z\XT1650-03_GRIFFIN_7.0_NPLS25.86-17-3-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\GRIFFIN_NPLS25.86-17-3-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.078s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.805s]
finished. total time: 0.885s
So yeah, I need a boot image that isn't signed with a bad key for RETEU.
Fixed. Flashed a Retail US 7.0 STOCK ROM even though it said "bad key", and then I flashed erfanoabdi's "Stock" 7.1.1 ROM which flashed a working boot.img that doesn't cause this problem.
Thread closed.
i have same problem bro but i didn't understand your solved please help me
i have same problem bro but i didn't understand your solved please help me
anatete404 said:
i have same problem bro but i didn't understand your solved please help me
Click to expand...
Click to collapse
Flash this: https://forum.xda-developers.com/moto-z/development/rom-erfanrom-flashable-zip-t3646962
yanniclord said:
Flash this: https://forum.xda-developers.com/moto-z/development/rom-erfanrom-flashable-zip-t3646962
Click to expand...
Click to collapse
ok i will try flash it tomorrow but my phone still say bad key and didn't star i flash 7.0 with erorr and 6.0 with erorr
i see erorr bootloader not found when i flash with fastboot i mean my phone didn't boot in recovery or normal just fastboot
I am not understanding most of what you are saying, but I can prepare a little .zip with everything you need for you. I make a .bat file that you need to run which should do all the work for you.
anatete404 said:
...
Click to expand...
Click to collapse
Alright, here. Make sure that you have ADB installed System-Wide on your PC, you can use ADB-AIO for that if you don't have ADB and Fastboot Tools installed yet.
Anyways, once you have that, download my .rar file (Yes, .rar, install WinRAR if you don't have it, I won't use .zip in order to compress much more and save space and download time for you), and then run the "Moto Z Automated Flash.bat" file, it should do everything for you, but make sure to READ what I wrote in it, when it asks you to "Press Enter", please READ everything carefully, I will NOT explain further here, everything that you need to know is described and explained to you while you use the "Moto Z Automated Flash.bat" file as a form of guide.
In case you wonder, it is 3.5GB large because it contains the STOCK 7.0 ROM for the Moto Z (that you will flash first), and then the 7.1.1 ROM from erfanoabdi that you will flash through TWRP. It also contains TWRP (which will be flashed during the guide/bat file) and a logo.bin that covers over the stupid "N/A" at bootup.
RAR file download:
https://mega.nz/#!M9kCDQRQ!184HVnma8xGi1m0llqWcSSTdcYjLb9hToRSx0BkqwfI
i flash your rom bro when i flash i cant get recovery only fastboot please help me
try another Kernel flashing by TWRP https://forum.xda-developers.com/devdb/project/?id=17677#downloads
anatete404 said:
i flash your rom bro when i flash i cant get recovery only fastboot please help me
Click to expand...
Click to collapse
Would you please try to at least speak a little proper English and use punctuations, it's really hard to read.
i need flash for my phone i upload problem and info i am sorry about english but please help me
anatete404 said:
i need flash for my phone i upload problem and info i am sorry about english but please help me
Click to expand...
Click to collapse
Here is the latest official full firmware with october patch:
https://androidfilehost.com/?fid=889964283620761640
thx bro but this https://androidfilehost.com/?fid=889964283620761640
working to my info phone i uploaded photo
Benoe said:
Here is the latest official full firmware with october patch:
https://androidfilehost.com/?fid=889964283620761640
Click to expand...
Click to collapse
Hey your link doesn't work anymore. Is it for 7.0+ and RETEU? If so, please send it to me !
yanniclord said:
Alright, here. Make sure that you have ADB installed System-Wide on your PC, you can use ADB-AIO for that if you don't have ADB and Fastboot Tools installed yet.
Anyways, once you have that, download my .rar file (Yes, .rar, install WinRAR if you don't have it, I won't use .zip in order to compress much more and save space and download time for you), and then run the "Moto Z Automated Flash.bat" file, it should do everything for you, but make sure to READ what I wrote in it, when it asks you to "Press Enter", please READ everything carefully, I will NOT explain further here, everything that you need to know is described and explained to you while you use the "Moto Z Automated Flash.bat" file as a form of guide.
In case you wonder, it is 3.5GB large because it contains the STOCK 7.0 ROM for the Moto Z (that you will flash first), and then the 7.1.1 ROM from erfanoabdi that you will flash through TWRP. It also contains TWRP (which will be flashed during the guide/bat file) and a logo.bin that covers over the stupid "N/A" at bootup.
RAR file download:
https://mega.nz/#!M9kCDQRQ!184HVnma8xGi1m0llqWcSSTdcYjLb9hToRSx0BkqwfI
Click to expand...
Click to collapse
Hi,
I tried to unlock bootloader following instruction on Motorola website then my moto z play has "BAD KEY" and keep restarting with that message on the screen. I found and used your file but it didn't help my device out of the "BAD KEY". Please help. Thank you
Here is the last version at the moment of the Maze alpha ROM (tested only in 4GB version)
It's a complete ROM, not an OTA update, it can be flashed using the provided TWRP 3.2.1 version, I ported from a Jemmini (many thanks) version for Bluboo S1.
Unfortunately, the TWRP cannot be flashed (issue with the touch panel), only launched by fastboot.
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
There is also a SPFlashTool clean version of this ROM, useful in case of troubles (as official: no root, no busybox)
1- Reboot you phone in fastboot mode : adb reboot bootloader
2- Flash the provided TWRP : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3- Reboot to TWRP recovery
4- copy in your SDCARD and install, in the running TWRP, the downloaded ROM V09 : Maze_Alpha_4GB_v09_TWRP.zip
The first boot take some minutes so be patient.
Here the SPFlashTool versions :
MAZE_Alpha_4GB_V09_SPFT.zip
Here, if needed, my V09 TWRP backup (new one from 21/04/2018) :
TWRP_BACKUP_MAZE_Alpha_A_V09.zip
Credits to Jemmini and Magisk team.
Can you make this for the 6 gb version?
many thanks gonna ty it soon
Nautilus99 said:
Can you make this for the 6 gb version?
Click to expand...
Click to collapse
I do not have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
dreambo said:
I do note have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
Click to expand...
Click to collapse
Yes i know its sad, i did a backup of mine and root it but it didnt work the backup i had to do clean flash, if we can manage to have a twrp and a source of the stock roms we could make a deabloat and put update apps ( menssages, calendar etc) and put mods for awsome features i dont see RR or lineage putting thier hands on this phone
Thanks for this Rom.
Is there any root for the maze alpha x?
here
WiddleyScudds said:
Is there any root for the maze alpha x?
Click to expand...
Click to collapse
read
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
Click to expand...
Click to collapse
thorfr said:
read
Click to expand...
Click to collapse
I have an alpha x, not alpha.
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
rzoli71 said:
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
Click to expand...
Click to collapse
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
thank you
After I installed this rom, and freezed the hot knot, baidu_location FM Radio, etc, the BT connection did not break.
dreambo said:
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
Click to expand...
Click to collapse
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
ahorntaler said:
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
Click to expand...
Click to collapse
No I not have any source, I am just a simple user like any other.
If I have any source or if I can make a ROM for MAZE Alpha X, I will do it and I will share it with every body, as I do until now for the MAZE Alpha 4/64
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
iBolitN said:
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
Click to expand...
Click to collapse
Unfortunatly no. As you will see repeated times in the forum, people have issue with phone not booting after changing from stock recovery to twrp. This is do (most likely from) to verified boot setting. And by unlocking bootloader we can bypass verified boot. So without unlock you might get a successfull load into twrp, but android will not boot.
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
stargazer78 said:
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
Click to expand...
Click to collapse
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Thanks a lot for your reply....
the problem is that i cant boot into fastboot to unlock bootloader....
the phone bootloops all the time, shows the red state alert and even with vol+ pressed the menu to choose recovery or fastboot doesn't apear... thanks again.
dreambo said:
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Click to expand...
Click to collapse
Is there any way to unlock the bootloader in my situation or/and enter the fastboot mode in order to follow your steps... thanks.