Brush before you must see:
1. The brush machine package is based on the official closed beta leaked JUI 7.1 brush machine package production
2. Because it is inside the package must have some bugs, focusing on the main experience!
3. Please carefully read this post in the brush machine!
4. As long as you brush the rom any problems are not responsible, brush machine risk, play machine need to be cautious, although I have tested, but may be due to some unknown reasons will lead to brush machine failure!
First of all the rom for the crowd: Le pro3 (x720 x728) Cool s1
mod edit : links removed
installation:
Flash TWRP
Download the ROM
Clear Data and Cache
Flash ROM
Flash Gapps Beans
Reboot
ATTENTION: Only care for who install, I have not tested the downgrade to EUI again, I do not know if it's easy
gersonrsj said:
Brush before you must see:
1. The brush machine package is based on the official closed beta leaked JUI 7.1 brush machine package production
2. Because it is inside the package must have some bugs, focusing on the main experience!
3. Please carefully read this post in the brush machine!
4. As long as you brush the rom any problems are not responsible, brush machine risk, play machine need to be cautious, although I have tested, but may be due to some unknown reasons will lead to brush machine failure!
First of all the rom for the crowd: Le pro3 (x720 x728) Cool s1
LINK DOWNLOAD: https://drive.google.com/drive/folders/0BzifdSZRqGIsM3BWWkFGRUVrc3M
installation:
Download the ROM
Clear Data and Cache
Flash ROM
Flash Gapps Beans
Flash Supersu
Reboot
CREDITS BY: NAVIGATOR
Click to expand...
Click to collapse
Thank you
Basically eui6:laugh:
Are you Chinese?
linchanggui said:
Are you Chinese?
Click to expand...
Click to collapse
Chinese and English
哈哈哈哈。。。
Google Drive....
You need permission
Your request for access has been sent.
You will receive an email if and when your request is approved.
Wow looks very good. Nice UI
Looks like it's the first release (official-like) of Nougat update for our device Cool Changer S1 is basically LP3 brother. They have mostly the same hardware.
This google drive link requires permissions so I will upload it on MEGA for anyone who wants to try in few minutes and edit this post.
Edit: Mega
Nice!!!!
Thes1ev said:
Looks like it's the first release (official-like) of Nougat update for our device Cool Changer S1 is basically LP3 brother. They have mostly the same hardware.
This google drive link requires permissions so I will upload it on MEGA for anyone who wants to try in few minutes and edit this post.
Edit: Mega
Click to expand...
Click to collapse
Thanks very good
I'm impressed with the more fluid rom being alpha beta, some bugs but nothing that disrupts the use, tomorrow I'm going to test the battery apparently looks very good, Rom has multi-window
gersonrsj said:
I'm impressed with the more fluid rom being alpha beta, some bugs but nothing that disrupts the use, tomorrow I'm going to test the battery apparently looks very good
Click to expand...
Click to collapse
What bugs have you found?
Ascertion said:
What bugs have you found?
Click to expand...
Click to collapse
Is not getting root, and gps is giving some errors I have to test better
Guys what twrp did you use to flash this rom ? For me it replaced fastboot to some strange one. After flashing it bootlooped on the screen with CoolPod or w/e (first what you see after powering the phone).
Moreover when phone is in fast bootmode it make some squeaking noise...
I managed to flash it just now, lets see whats up.
@Thes1ev being carefull, I first extracted the recovery contained in the rom zip file, and flashed it to see it was a modified twrp, and able to decrpyt my storage (logic being, if it was faulty, I'd just fastboot flash darkos twrp back, and end the story there). Seeing as it was working, I then flashed the rom, it took a while longer than I expected, but it finished. Upon boot I did run into a problem, my keyboard wouldnt pop up to enter the decryption password lol, luckily I had my OTG adapter handy, and managed to input my pw with my usb keyboard
---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------
And, I see now there's no keyboard installed other than google voice typing, that explains it
trizex said:
I managed to flash it just now, lets see whats up.
@Thes1ev being carefull, I first extracted the recovery contained in the rom zip file, and flashed it to see it was a modified twrp, and able to decrpyt my storage (logic being, if it was faulty, I'd just fastboot flash darkos twrp back, and end the story there). Seeing as it was working, I then flashed the rom, it took a while longer than I expected, but it finished. Upon boot I did run into a problem, my keyboard wouldnt pop up to enter the decryption password lol, luckily I had my OTG adapter handy, and managed to input my pw with my usb keyboard
---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------
And, I see now there's no keyboard installed other than google voice typing, that explains it
Click to expand...
Click to collapse
I was on darkos twrp, flashed this room and it boot-looped at the beginning. Now I can't even turn off the phone as it automatically turns on and off and on etc... every few seconds on this fkn "Coolpad" screen. I can enter the recovery however can't transfer any rom into the card. Adb push stops after some time randomly before it manages to transfer any ROM into the sdcard...
Just realized it stopped rebooting when I plugged it into the charger.
Got root through SuperSU 2.79
Thes1ev said:
I was on darkos twrp, flashed this room and it boot-looped at the beginning. Now I can't even turn off the phone as it automatically turns on and off and on etc... every few seconds on this fkn "Coolpad" screen. I can enter the recovery however can't transfer any rom into the card. Adb push stops after some time randomly before it manages to transfer any ROM into the sdcard...
Click to expand...
Click to collapse
Fastboot and flash darkos twrp? Copy just the recovery.img through twrp, flash it, and then copy what you want?
trizex said:
Got root through SuperSU 2.79
Fastboot and flash darkos twrp? Copy just the recovery.img through twrp, flash it, and then copy what you want?
Click to expand...
Click to collapse
Fastboot is not working, power + vol down goes to black screen / turning off the phone.. I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it.
And the thing is while pushing big files(it takes few minutes) it randomly stops responding in the middle of a transfer. So I have to start again. Tried maybe 10~ times and still stopping transfer randomly.
Commands in console like fastboot oem device info gives < waiting for any device >
adb reboot bootloader
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
Thes1ev said:
Fastboot is not working, power + vol down goes to black screen / turning off the phone.. I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it.
And the thing is while pushing big files(it takes few minutes) it randomly stops responding in the middle of a transfer. So I have to start again. Tried maybe 10~ times and still stopping transfer randomly.
Commands in console like fastboot oem device info gives < waiting for any device >
adb reboot bootloader
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
Click to expand...
Click to collapse
I just reverted back to Omni, I had my twrp.img on the phone, flashed it, restored my backup, no problems. Also, i used fastboot to flash back zl1 original files (including bootloader itself), no issues there either. I know its silly, but its happened before, try another pc/usb cable?
I might hold off on flashing this. Seems like recovery and other partitions are included in this that may render certain devices unbootable.
Thanks for sharing though. Hopefully a Dev can make a more stable port.
Related
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
Guide to rooting infocus Epic 1 (for windows) for build 00.
This method is only tested on build 00IN_1_360 only. If you are on the older build, first update your phone to build 00IN_1_360 then proceed. Check Build number in settings->about phone.
Proceed at your own risk, I will not be help responsible if your phone bricks, Your warranty will be void after this. Also all phone data will be lost including data on internal memory like photos, etc after these steps so take necessary backups.
Prepare your system
1. Extract and Install MTK Driver Auto Installer v5.1632 (google it)
2. Install Phone F Driver (from phone CD-emulation/driver folder upon connecting your phone)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
4. Download latest SuperSU flashable zip file from here
5. Download twrp-3.0.3-0-epic1-noveritynoencrypt.zip from here, extract in the folder where you have installed adb and fastboot
6. Download noencryptnoverty_boot.zip from attachments and extract to folder where you have installed adb and fastboot
Steps to root:
1. Enable Developer options in phone settings (goto phone settings -> about phone -> tap build number 7 times)
1a. Enable OEM unlock
1b. Enable USB Debugging
2. Connect phone to computer, wait for hardware to auto install
3. open cmd as administrator
3a. goto the directory where adb and fastboot is installed
4. type command:
4a.
adb reboot bootloader
(Wait for phone to come in fastboot)
4b.
fastboot OEM unlock
(press vol up key on phone)
4c.
fastboot flash boot noveritynoencrypt.img
4d.
fastboot flash recovery recovery.img
4e.
fastboot reboot
You will get an phone orange state prompt, do not worry its normal. Phone may reboot once or twice. Wait for phone to normal bootup.
5. open cmd and type command
5e.
adb reboot recovery
Phone will reboot in recovery i.e. TWRP
6. Tap on Keep system read-only. Do not swipe to allow modifications. If TWRP asks for password, don't enter any press back.
7a. Tap Wipe -> Format Data. Come out to main menu, then click reboot and then recovery to restart recovery.
7b. Tap Wipe -> Advanced Wipe -> Select Dalvik /ART, Cache, Data and Internal Storage. This is important step, as these partitions are encrypted at the moment, so if you flash anything the phone rom may corrupt.
8. Come out and then Tap Reboot -> System
9. Once the phone is back, turn off the phone. Then power on with vol up key pressed to boot into TWRP
10. Tap Backup, select all partitions, select phone storage (SD card preferred) and take backup (optional step but highly recommended )
11. Now tap install, goto the location where you had copied SuperSU zip file, flash it.
Congratulations your Phone is rooted. Reboot, see SuperSU icon in app drawer.
Many thanks to @mujammil786 for providing stock files and @Bornstud for testing twrp builds
Special thanks to our devs @DespairFactor for modifying boot.img to disable Encryption and Verity and @kirito9 for creating TWRP for our device. Without their help, it wouldn’t have been possible.
MODS
(Take backup of your ROM/Data before applying any mods)
Viper4Android (Advanced Sound Enhancement)
Hugely Customizable and better than MaxxAudio or Dolby Atmos IMHO
Now working on our device Infocus Epic 1
Need to flash the 2 attached files via TWRP before installing the official app from HERE. Although latest version v2.5.0.5 also works, but i personally prefer v2.4.0.1 (busybox required)
(Note the attached files are not my work, they are picked from here and here. Say thanks to original contributors.)
Good V4A profile: HERE
Extract it to ViPER4Android Directory in internal Storage
Xposed
Needs no introduction. Every android enthusiast should know what it is. Anyway if you are new, xposed opens limitless ROM customization(s) and useful features via 100s of its modules.
Installation:
1. Flash framework xposed-v87-sdk23-arm64.zip from HERE via TWRP. Reboot after installation will take long time (~10 - 15 minutes)
2. Install app XposedInstaller_3.1.1.apk from HERE
Restoring phone back through SUT
If you are stuck somewhere or want to restore the phone factory state (like for when giving to repair), you can restore the phone back via SUT
Link for build 1280: https://firmwarefile.com/infocus-epic-1
Also dont turn off your phone as suggested in sut readme file. It only works when your phone is on. Check below vid for more instructions
https://m.youtube.com/watch?v=eV_cId5fC9E
Reduce battery consumption & phone temperature
Found an interesting thread, mod works on our device also
https://forum.xda-developers.com/red...tings-t3687897
I have tried both flavor 1 and flavor 2 over the past week. Results with flavor 1 were positive in the beginning but for some reason standby drain shot up after 3-4 days, not sure what the reason was.
On flavor 2, I have just disabled MTK perfservice by setting
ro.mtk_perfservice_support = 0 in build.prop
Yes this limits the a72 core to 1.5ghz, but i have noticed phone is heating less and need for charging the phone has reduced. I haven't noticed much drop in performance either, but that might be as I don't use intensive apps.
Mafioso said:
I've managed to unpack nb0 file through a688 tool, however its only successful in unpacking few files before it crashes with some array size error, but the good thing is I was able to extract the scatter file for this phone before it happened.
Anyway, I was hopeful that I would be able to make backup of Stock ROM and Recovery through it via spflash tools however as it turns out, spflash tool is giving me error while doing readback BROM ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003)
Not sure how to fix it, i've updated my drivers as well as i'm using latest version of spflash tool (SP_Flash_Tool_v5.1628_Win)
Attaching scatter file.
Click to expand...
Click to collapse
From where uve downloaded the stock firmware
Romeotamizh said:
From where uve downloaded the stock firmware
Click to expand...
Click to collapse
http://firmwarefile.com/infocus-epic-1
Mafioso said:
http://firmwarefile.com/infocus-epic-1
Click to expand...
Click to collapse
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Romeotamizh said:
Oh
Click to expand...
Click to collapse
Look in other sites bro for img files
Romeotamizh said:
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Look in other sites bro for img files
Click to expand...
Click to collapse
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Mafioso said:
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Click to expand...
Click to collapse
Ooh bro I'm happy to help but seriously i Duno about these kind of extensions hope u understand
Mafioso said:
I'm trying to root Infocus Epic 1, its a good budget phone with decent specs. Availability is only in India, not sure other regions. Anyway I'm having hard time to root it, since not much support is available. But so far, I have tried below things:
1. Tried to root with Kingroot, doesn't work .Probably because it is very new version of Marshmallow with Oct'16 patch level and kernel dated in dec 16.
2. Tried to generate scatter file via MTK Droid tool v2.5.3, after enable USB debugging in phone. The phone get detected in the tool, however create scatter file option in block map is disabled I've read somewhere, it might be due to MTK6797 (Helios x20) is quite new and is not yet fully supported by tool yet. Not sure if its true though. But if I can generate scatter file, I can extract phone's stock recovery via SPFlash tool readback to try a hand at porting twrp/cwm with some help..
3. Downloaded stock Infocus Epic 1 firmware in hope for recovering stock recovery.img or MTK scatter file, however on unpacking the firmware package, I found it contains unknown image file of nb0 extension which is it to be flashed via SUT Tool. Not sure how to unpack this file
Any more ideas, how can i atleast start with my quest to root/put custom recovery on this phone ? @Romeotamizh Pls help.
Click to expand...
Click to collapse
I can give u stock recovery of epic 1..
mujammil786 said:
I can give u stock recovery of epic 1..
Click to expand...
Click to collapse
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Mafioso said:
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Click to expand...
Click to collapse
I was able to extract it from last update zip
---------- Post added at 04:45 PM ---------- Previous post was at 04:33 PM ----------
Epic 1 stock recovery
https://drive.google.com/file/d/0B4FNo4vddleCNmpwcS1hS3FLam8/view?usp=drivesdk
mujammil786 said:
I was able to extract it from last update zip
Click to expand...
Click to collapse
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Mafioso said:
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Click to expand...
Click to collapse
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
mujammil786 said:
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
Click to expand...
Click to collapse
thanks, updated first post.
Mafioso said:
thanks, updated first post.
Click to expand...
Click to collapse
Thanks let's hope for best
I like this phone and the only thing lacking is Root, Hope someone will do it
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Mafioso said:
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Click to expand...
Click to collapse
My device does not get detect in fastboot can u show me screen shot of command u are trying....
mujammil786 said:
My device does not get detect in fastboot can u show me screen shot of command u are trying....
Click to expand...
Click to collapse
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Mafioso said:
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Click to expand...
Click to collapse
Ok will try thanx
bootloder get unlocked and locked too
ok so phone get detected in fastboot mode:victory: .was able to lock and unlock boot loader but without custom recovery it is no useful for us.
unlocked bootloader.
tried flashing Vernee_Apollo_Lite_P6(same spec. as epic 1) twrp recovery.
flashing done but after flashing phone refused to boot.
flashed stock recovery from update zip.
locked bootloader.
phone booted but erased internal memory after boot.
---------- Post added at 11:47 AM ---------- Previous post was at 11:44 AM ----------
do you know any guide for making twrp and i think phone will not boot if it detect any change in system partition i think
*** OUTDATED, WORK HAS NOW PROGRESSED TO POISON ROM, https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720 ***
Features
Removed Bloatware apps such as Twitter, Team Viewer etc.
Removed Dummy Play Store App
Removed Outdated versions of apps and replaced them with latest versions as of time of writing, like Playstore, Firefox, Kodi etc.
Used a Custom Launcher (Created by Ricky Divjakovski) to give device a fresh look.
Enter Key now works on External Keyboards
Known Bugs:
Play Store shortcut on Launcher does not work, Can open Playstore through Setting/Apps. ***Fixed***
Enter key on External Keyboard doesn't work. ***Fixed***
Navigation Bar does not come back if minimised without a reboot.
When you go to Settings/About/Status sometimes has an error and doesn't open, opens on second attempt though.
Any other bugs feel free to report.
***IMPORTANT ***
You need to be on Stock 7.1.2 Firmware before flashing the Custom Rom. So I recommend you make a backup of your existing Firmware if for any reason you want to go back to your Existing Firmware and setup. To make a backup, you need to get Custom Recovery (TWRP) installed, you need to install the right version of TWRP depending on your existing firmware. Download your existing Firmware Custom Recovery files from below.
TWRP FILES
If on Firmware 6.0.1 from here
If on Firmware 7.1.1 from here
If on Firmware 7.1.2 from here
INSTALLING CUSTOM RECOVERY
METHOD 1:
Download Ricky's Amlogic Flash Tool from AmlogicFlashTool.zip and follow the instructions from his thread over at https://forum.xda-developers.com/an...c/amlogic-devices-amlogic-flash-tool-t3745640.
METHOD 2:
1. Download ADB from here and install it on your pc, then open a command prompt (Windows 10 hold Shift and press Right Mouse button, will take you to Power Shell) in the directory of the custom recovery
2. Enable USB debugging, go to settings>about and click build number about 10 times, then go back to the main settings menu and you will see developer options, enter it and check allow USB debugging.
3. Connect to your device via IP address. go to settings>about>status and get your IP address. it should be something like 192.168.25.19
4. In CMD type the following commands, replace YOURIPADDRESS with the address we got from step 3
Code:
adb connect YOURIPADDRESS
adb push custom-recovery.img /sdcard/
adb shell su -c dd if=/sdcard/custom-recovery.img of=/dev/block/recovery
adb reboot recovery
TWRP BACKUP
Now go ahead and make a backup of your existing setup before proceeding any further. I recommend putting the backup onto a usb drive.
Step:
1. Go to Backup
2.If desired name your backup on name setting up top left hand corner, not necessary but can do if you like.
3. Select Storage: USB or SDCard depending on which one you are going to use. Click OK.
3. Swipe to Backup
4. Let it do it's thing, When finished remove usb/sd card and reboot to system.
5. Recommend putting a copy of your backup from your usb or sd card to your PC as well.
FLASHING 7.1.2 STOCK FIRMWARE
You need to download the Stock 7.1.2 firmware from here
Use the provided USB Burning tool to flash the firmware if you have a USB Male to Male cable. Video of how to here
Now 7.1.2 Stock is installed, you now have to flash the Custom Recovery (TWRP) for 7.1.2, follow the instructions earlier to install Custom Recovery with the 7.1.2 file.
CUSTOM ROM
NOTE: Remember to make sure you have a backup of your old existing firmware before flashing this custom rom
Instructions:
1. Download the 3/32GB T95Z Custom Rom 7.1.2.zip from here
and put it on a usb stick.
2. Reboot into recovery
3. Wipe Cache, System and Data
4. Go back to the main menu and select install, then choose the 3/32GB T95Z Custom Rom 7.1.2.zip and swipe to install!
Reboot and enjoy!
Please give 5 to 10 minutes on first reboot after flash.
Contributors
Ricky Divjakovski, whiteak
ROM OS Version: 7.x Nougat
Credits:
Magendanz (TWRP)
Snoop05 (Adb)
Version Information
Status: Testing
Great job! A whole range of ROMS for Amlogic devices is about to unveil once i release the rom skeletop package!
Hi on my device when i reboot to recovery after put TWRP by adb it's stuck on T95z plus logo... Any idea ?
after unplug the power cable and plug it again the box start, but i can't start in recovery by the adb... can u give me some help ?
Thanks by advance.
---------- Post added at 11:36 AM ---------- Previous post was at 11:31 AM ----------
I do that and i don't see any error..
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb connect 192.168.1.100
connected to 192.168.1.100:5555
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb push custom-recovery.img /sdcard/
custom-recovery.img: 1 file pushed. 6.6 MB/s (13793280 bytes in 1.986s)
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb shell su -c dd if=/sdcard/custom-recovery.img of=/dev/block/recovery
26940+0 records in
26940+0 records out
13793280 bytes transferred in 2.774 secs (4972343 bytes/sec)
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb reboot recovery
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>
Is your box 2/16gb or 3/32gb, you may be flashing the wrong TWRP.
whiteak said:
Is your box 2/16gb or 3/32gb, you may be flashing the wrong TWRP.
Click to expand...
Click to collapse
32Gb box and i take the twrp from your thread.
papla83 said:
32Gb box and i take the twrp from your thread.
Click to expand...
Click to collapse
Try this TWRP here
It's a earlier version, but I ported this one myself. It's the one I used until I found a newer version.
whiteak said:
Try this TWRP here
It's a earlier version, but I ported this one myself. It's the one I used until I found a newer version.
Click to expand...
Click to collapse
Same result, hang on t95Zplus logo and doesn't move....
papla83 said:
Same result, hang on t95Zplus logo and doesn't move....
Click to expand...
Click to collapse
And you definitely have a 3/32gb box, I don't know what could be the problem. I had the exact same problem, but it was because I was using the 2/16 version on my 3/32 box. You don't have any usb sticks plugged into the box either? if you do try pulling them out when flashing.
whiteak said:
And you definitely have a 3/32gb box, I don't know what could be the problem. I had the exact same problem, but it was because I was using the 2/16 version on my 3/32 box. You don't have any usb sticks plugged into the box either? if you do try pulling them out when flashing.
Click to expand...
Click to collapse
yes i have, i will try whitout sd card and usb stick and make a feedback
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
same result
can i brick my box if i flash it with the 16Gb model ? because maybe i can try with no risk ( the recovery doesn't start anyway )
Worst case is it should only do the same thing, I was pushing the 16gb model on my box a fair few times and all it did hang at the T95Z Plus logo.
whiteak said:
Worst case is it should only do the same thing, I was pushing the 16gb model on my box a fair few times and all it did hang at the T95Z Plus logo.
Click to expand...
Click to collapse
When i try to send twrp 16gb version to my box i have an error message failed to send file ( i use the amlogic adb tool by Ricky Divjakovski )...
papla83 said:
yes i have, i will try whitout sd card and usb stick and make a feedback
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
same result
can i brick my box if i flash it with the 16Gb model ? because maybe i can try with no risk ( the recovery doesn't start anyway )
Click to expand...
Click to collapse
By personal experience your best bet is to re flash the original rom with the usb flashing tool.
Once it is done you can try flashing different TWRP until you find one that work. Installing TWRP from the store just does not work on those device.
Installing SU also soft brick your device and normal recovery do not work.
Also to flash using to USB burning tool make sure you use the OTG USB port on your device (usually port no, 1).
whiteak said:
Known Bugs:
Play Store shortcut on Launcher does not work, Can open Playstore through Setting/Apps.
Navigation Bar does not come back if minimised without a reboot.
When you go to Settings/About/Status sometimes has an error and doesn't open, opens on second attempt though.
Any other bugs feel free to report.
Click to expand...
Click to collapse
I got play store to work on my original rom from the launcher after disabling it in the app settings, and replacing system/app/GoogleStore folder by the one from SuperCeleron 3/32g custom rom ans installing it from the apk. Might be worth a look to get it working on your rom.
Funny thing is that I tried to install SuperCeleron Rom on my machine but it brick it every time.
Also on initial setup after you have an option to give root acces or not and also to enables init.d support, I just can't remember where it was in the Droid settings on the launcher or the most advance settings in the apps folder. I will have to go thru all the settings to find them.
I tried your ROM but it disabled my Play Store in the launcher and in the apps and did not let me reinstall it for some reason. I had to go thru TotalCommander to be able to launch it. Since I did not want to fool around to restore it. I just flashed back my Rom.
I can live with the way my device perform right now has the most important part for me was Kodi.
Stuck at logo as well
I got everything to go just fine: ADB went smooth, TWRP running just fine, successful flash from microSD card, wiped cache, rebooted and waited 15 minutes and I'm just stuck at the logo
I even pulled AC and ejected the card and then plugged it in let it sit for 20 minutes and nothing but the logo still.
I'm 101% sure I'm have a 3G+32Gb T95z Plus (AP6225 WLAN)
LeMaestro said:
I got play store to work on my original rom from the launcher after disabling it in the app settings, and replacing system/app/GoogleStore folder by the one from SuperCeleron 3/32g custom rom ans installing it from the apk. Might be worth a look to get it working on your rom.
Funny thing is that I tried to install SuperCeleron Rom on my machine but it brick it every time.
Also on initial setup after you have an option to give root acces or not and also to enables init.d support, I just can't remember where it was in the Droid settings on the launcher or the most advance settings in the apps folder. I will have to go thru all the settings to find them.
I tried your ROM but it disabled my Play Store in the launcher and in the apps and did not let me reinstall it for some reason. I had to go thru TotalCommander to be able to launch it. Since I did not want to fool around to restore it. I just flashed back my Rom.
I can live with the way my device perform right now has the most important part for me was Kodi.
Click to expand...
Click to collapse
I want just have the best experience with this box, the box ,at this time and with this rom works, but i feel the works doesn't finish and i think we have a huge possibility with a finalised and optimised rom.
---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------
Semper 5 said:
I got everything to go just fine: ADB went smooth, TWRP running just fine, successful flash from microSD card, wiped cache, rebooted and waited 15 minutes and I'm just stuck at the logo
I even pulled AC and ejected the card and then plugged it in let it sit for 20 minutes and nothing but the logo still.
I'm 101% sure I'm have a 3G+32Gb T95z Plus (AP6225 WLAN)
Click to expand...
Click to collapse
Hi. sorry for the dumb question but do you wipe to the factory data too or only wipe cache ?
papla83 said:
Hi. sorry for the dumb question but do you wipe to the factory data too or only wipe cache ?
Click to expand...
Click to collapse
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Semper 5 said:
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Click to expand...
Click to collapse
Take a look here maybe you will find what you need.
https://forum.xda-developers.com/an...95z-plus-one-thread-files-recoveries-t3737040
I used the custom recovery for the 3/32Gb variant and it worked perfect, now I have a working TWRP.
papla83 said:
I want just have the best experience with this box, the box ,at this time and with this rom works, but i feel the works doesn't finish and i think we have a huge possibility with a finalised and optimised rom.
Click to expand...
Click to collapse
Me to I would like to have a few thing added or fixed in the launcher, but those guys just started to work on this a few days ago, so let give them time to make it better. I screw up my box enough in the last week so let be patient.
Semper 5 said:
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Click to expand...
Click to collapse
TWRP link updated, not sure why it unlinked but anyway should be good to download again.
LeMaestro said:
Take a look here maybe you will find what you need.
https://forum.xda-developers.com/an...95z-plus-one-thread-files-recoveries-t3737040
I used the custom recovery for the 3/32Gb variant and it worked perfect, now I have a working TWRP.
Me to I would like to have a few thing added or fixed in the launcher, but those guys just started to work on this a few days ago, so let give them time to make it better. I screw up my box enough in the last week so let be patient.
Click to expand...
Click to collapse
That link in the other thread links to my mega folder, can I ask which custom recovery you used the 3.1.1-0 or the 3.0.2, both should work, but just curious. Also so you did manage to flash my custom zip successfully and it did boot up? Not sure why people are having problems.
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
nea102 said:
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
Click to expand...
Click to collapse
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
I had used that guide, was following that when I was getting the out of space errors.
However, I got it all sorted in the end - I just downloaded a different (older) version of the firmware and that worked.
Help for you
samlis said:
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
Click to expand...
Click to collapse
Hi good day.
I have been following your work from another page, and now in XDA.
I had not read your message, and, I changed the recovery for the stock, and, I was an idiot to close the bootloader.
What happened? Brick simple on my cell phone, did not come out (because I fixed it) of the image of erecovery (EMUI) without tabs or options, a rather rare image.
How do I solve it:
1. I did not enter fastboot, I did not correctly enter the stock recovery (I had deleted the twrp), I had closed the bootloader (my stupidity)
2. Be patient and wait for the battery to run out (wait a day for it).
3. Open cmd and place the command to open the bootloader (fastboot oem unlock) and execute.
4. Put the device in fastboot mode when connecting to the laptop (I did not work several times, the fastboot came out with error FUNC No 10 and NO 2), after numerous attempts and not to let it charge the battery too much (because it was restarted and towards brick in the EMUI logo), correctly enter the fastboot and unlock, when you enter step 3 automatically, it will be executed. I had an advance in removing the cell phone from the brick.
5. It reboots and wonderfully happened to the Rom (that had previously installed), that is to say, the erase was not executed when the bootloader had previously closed.
6. As I had little energy, it was turned off, but I connected it and entered charging mode without restarting (before I did it).
7. Wait for a load of at least 5%, and install the Catuva21 TWRP from the tutorial.
8. I put it by command to restart in fastboot, but I generate error (Error Func No 10 and No 2).
9. I turn off the cell phone and with volume up and power key
10. Enter the TWRP correctly, verify that it is installed.
11. Restart system and log in to the system. I had not deleted anything, but to avoid problems, I hope to load 55% and execute the steps to install the rom.
12. Enjoy and dry spilled tears.
Experience lived and I hope you do not do something that developers do not advise.
Grcias and happy day.
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
heindrix said:
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
Click to expand...
Click to collapse
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
yoni sofer said:
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
Click to expand...
Click to collapse
take a look here, mate.
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Man, I think I have faulty hardware on my Umidigi One Max already. I was booted up in LineageOS, pulled up newpipe (third party youtube app) to watch videos, and out of nowhere my phone powered down, and booted straight into recovery (TWRP right now). I formatted, and restored the Umidigi stock ROM, and rebooted, and same thing, it boots straight into TWRP. No matter what I try, it boots directly into recovery. Anyone else had a similar issue?
Fixed .... See details
kgoerbig said:
Man, I think I have faulty hardware on my Umidigi One Max already. I was booted up in LineageOS, pulled up newpipe (third party youtube app) to watch videos, and out of nowhere my phone powered down, and booted straight into recovery (TWRP right now). I formatted, and restored the Umidigi stock ROM, and rebooted, and same thing, it boots straight into TWRP. No matter what I try, it boots directly into recovery. Anyone else had a similar issue?
Click to expand...
Click to collapse
Just for an update. I was able to get everything up and running. Some partition, I assume became very corrupt, or something along those lines. If someone runs into the situation where your Umidigi One Max only boots into recovery this might save you some time:
1. Firstly, from twrp I powered down.
2. I downloaded up the factory ROM, and extracted it.
https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
3. Loaded the scatter file in SPflash, but when I clicked download, and plugged in the OneMax the phone automatically powered up into TWRP recovery, and SPflash would time out (Ugh!). So I had to go OLD school. I run Ubuntu linux, but this can be done in windows too. Running adb commands to FORCE the images onto the phone. Run these commands:
Google how to install adb in windows...
A. adb reboot bootloader (this forces the phone in fastboot)
B. From dos / linux command-line change into the directory that contains Umidigi One Max factory images you downloaded/extracted.
C. Run these commands to force the important images onto the phone.
1. fastboot flash recovery recovery.img
2. fastboot flash boot boot.img
3. fastboot flash userdata userdata.img
4. fastboot flash system system.img
5. fastboot reboot
The system image contains the bulk of the OS (2GB).
If it gives you errors when you try to fastboot flash an image, you may need to unlock the bootloader to have access to write the images:
fastboot oem unlock
fastboot flashing unlock
fastboot flashing unlock_critical
To re-lock the bootloader at the later time, you issue these commands:
fastboot oem lock
fastboot flashing lock
fastboot oem relock
My phone booted happily, and retained IMEI keys too. Whew! Hope others find this helpful.
Happy you got your phone back
I had the recovery/bootloop issue also while attempting to put a gsi of Havoc 2.7 pie on here. Ended up with A Havoc 2.0 pie which is running great!!
I really enjoy this device, wondering if you have found a good camera app that eliminates some if not all of the pixel noise when using the back main camera?? Been looking for a while now and it's my only real issue with this phone.
prophetofthepath said:
I had the recovery/bootloop issue also while attempting to put a gsi of Havoc 2.7 pie on here. Ended up with A Havoc 2.0 pie which is running great!!
I really enjoy this device, wondering if you have found a good camera app that eliminates some if not all of the pixel noise when using the back main camera?? Been looking for a while now and it's my only real issue with this phone.
Click to expand...
Click to collapse
Hi prophetofthepath,
I have been using havoc 2.8 as my main driver, and have primarily used opencamera. Haven't had a ton of luck with the camera quality, as it is hit or miss on the quality.
I also use Magisk to fix other issues, including NFS. There is a Magisk module that activates nfc in custom ROMs.
For voice recognition feature to work with sms, I had to download a keyboard other than aosp's default keyboard (like Google's).
I'm not sure about your one max, but on my one max wifi speeds are awful! 30Mbps max download, even on 200Mbps networks! I've tried both stock and havok, and neither make a difference. Call reception is ok. Umidigi shouldn't skim costs where reception is concerned. I'm fairly certain, it's cheap internal antennas to blame. It gets me by though.
If you've picked up any tricks, be sure to comment.