Related
Introduction.
Sorry for my English, if I wrote something incorrectly, correct me!
Make sure you have installed the Asus's driver. If you have no idea or do not know how, ask.
I used ADB Android SDK ( h-t-t-p://developer.android.com/sdk/index.html , it is located in sdk\platform-tools), make sure ADB recognizes the PF2 before.
The command you type in the terminal:
adb devices
I have run ADB from Windows, but if you use Ubuntu (or Linux in general) basically the syntax is the same.
If you have never sent a file via ADB in recovery, give it a try with any file before proceeding with the guide, so you know what you're doing when you get to step 4 and, above all, if you fail you will not formatted PF2 in vain.
The command you type in the terminal:
adb push filename.extension /data/media
"adb" is the name of the exe file in the folder where you execute it, you can also write adb.exe is the same;
"push" is the command that sends the file;
"filename.extension" is the file you want to send (example update.zip). The file to be sent must be in the same folder as adb.
"/data/media" is the destination path where the file will be copied. In our case that is the internal memory of the PF2.
Obviously before starting any command you have to move to the folder containing the file adb.exe (sdk\platform-tools if you have downloaded the Google ADT)
The PF2 must have the original recovery.
I personally changed SKU from WWE to CHT and vice versa before writing this simple guide.
My PF2 had the bootloader unlocked when I made the change, it should work with the bootloader locked, but my advice is to unlock it before you play because if something goes wrong, there is a chance to do something through fastboot for revive him.
Here we go:
1. Copy to the phone's internal memory the firmware you want to install, then reboot into recovery.
2. Select "apply update from external storage" and choose the zip file to flash.
At this point the recovery changes the partition table and then restarts.
On reboot we will have a nice "Installation aborted", this because, being changed the partition table, the recovery can not find the file to flash as it the partition containing the data has been reformed losing its contents. So you will need to copy the file again via adb.
3. Select "wipe data / factory reset"
You need to do a wipe, because it formats the partition where we will send the file. Having just changed, the partition has not a file system and so it must be formatted to save something on it.
4. Send via adb the firmware:
adb push xxxx.zip /data/media
5. Wait until the firmware is sent to PF2. ADB has spent 148 seconds to send the WWE (~ 713 Mb) and 172 seconds to send the CHT (~ 813 Mb).
You will not see any progress bar, so do not panic and just wait for the terminal will show the message sending done.
6. Select "apply update from external storage" and choose the zip file to flash.
The recovery will restart again, but this time the partition will not be changed so it will proceed with the upgrade.
Finished updating the PF2 restarts.
I suggest you do a wipe after the update in order to have a clean installation.
It 'important to note that when you make a change from one SKU (WWE, TW, CHT etc ...) to another one, it goes beyond the point 2 only if the recovery changes the partition table.
If you have any doubt, ask, I'll be happy to update some step in more detail.
I hope you enjoy it.
gsep
I'll link this to the thread so others will have an easy time to find this
walaway said:
I'll link this to the thread so others will have an easy time to find this
Click to expand...
Click to collapse
Thanks
hope in our subsection in future.
gsep said:
My PF2 had the bootloader unlocked when I made the change, it should work with the bootloader locked, but my advice is to unlock it before you play because if something goes wrong, there is a chance to do something through fastboot for revive him.
Click to expand...
Click to collapse
Hi...thanks very much for the tips and very detailed instruction.....but, have u tried the steps without unlocking the bootloader? and if i want to go back tot he original SKU, i just need to replace the firmware.zip with the correct one from Asus web and repeat the whole thing? Just in case for warranty purposes....
Thanks again!!!
pgkia said:
Hi...thanks very much for the tips and very detailed instruction.....but, have u tried the steps without unlocking the bootloader? and if i want to go back tot he original SKU, i just need to replace the firmware.zip with the correct one from Asus web and repeat the whole thing? Just in case for warranty purposes....
Thanks again!!!
Click to expand...
Click to collapse
I only have tried with unlocked PF2.
For go back you have to follow always this guide.
gsep said:
Introduction.
Here we go:
1. Copy to the phone's internal memory the firmware you want to install, then reboot into recovery.
2. Select "apply update from external storage" and choose the zip file to flash.
At this point the recovery changes the partition table and then restarts.
On reboot we will have a nice "Installation aborted", this because, being changed the partition table, the recovery can not find the file to flash as it the partition containing the data has been reformed losing its contents. So you will need to copy the file again via adb.
3. Select "wipe data / factory reset"
You need to do a wipe, because it formats the partition where we will send the file. Having just changed, the partition has not a file system and so it must be formatted to save something on it.
4. Send via adb the firmware:
adb push xxxx.zip /data/media
5. Wait until the firmware is sent to PF2. ADB has spent 148 seconds to send the WWE (~ 713 Mb) and 172 seconds to send the CHT (~ 813 Mb).
You will not see any progress bar, so do not panic and just wait for the terminal will show the message sending done.
6. Select "apply update from external storage" and choose the zip file to flash.
The recovery will restart again, but this time the partition will not be changed so it will proceed with the upgrade.
Finished updating the PF2 restarts.
I suggest you do a wipe after the update in order to have a clean installation.
It 'important to note that when you make a change from one SKU (WWE, TW, CHT etc ...) to another one, it goes beyond the point 2 only if the recovery changes the partition table.
If you have any doubt, ask, I'll be happy to update some step in more detail.
I hope you enjoy it.
gsep
Click to expand...
Click to collapse
i read some where on modaco, walaway mention this can be done with TWRP instead? Flash with TWRP in fewer steps. Is this true?
Did not work with me, not sure why?
First of all thanks for the detailed steps.
I have went through your steps more than 9 times before I decided to start with it.
I am on CHT (10.4.12.24-0)) and want to move to WWE (Latest) with unlocked bootloader.
Everything is alright until i reached step 2 where "At this point the recovery changes the partition table and then restarts."
The phone did not restart? it went straight to "Installation aborted" and nothing happened? Nothing was changed.
Not sure if the issue with the downloaded package? I got it from Asus official website "WWE_PadFone2_user_10_4_12_24_UpdateLauncher" but renamed it to "WWE" for easier adb command?
Any help will be appreciated
Edit: Downloaded file was supposed to be extracted from the .zip package, what a silly mistake it worked like charm. Thanks!
Why???
Why do I want to do this? If I go from CHT to WWE would it make my phone more compatible with tmobile?
Locked SIM
Hi all,
I did a Change from WWE to TW. The Thing is that my phone was not unlocked. After flashing to TW it worked a day and after that the SIM MODUL is totally blocked (IMEI = 0). I can not use any SIM Card.
I try to unlock the bootloader by means of the "Unlocker" app from ASUS, but it always says:
"An unknown error occurs, which may be a network connection issue. please wait and tray again later"
I tried to:
* Use the latest Version of WWE or TW Firmware
* Use an old Version of WWE Firmware
without success...
Does anyone have similar Problem ?
so this works because the system partition is blank?
Greeting from Vietnam, and sorry for my English
So, you dont want to wait the official-update from your carier/country, you got the OTA file from somewhere else, i'm gonna show you how to flash it, step by step with some stricks
This might works with other phones (I think), but in this guide we'll doing stuffs with HTC One Mini Android 4.2.2, flashing 4.3 OTA file
Before you do anything, i suggest you should do a nandroid backup, so you can get back your official rom any time. This is very important, please google for it
(For those who dont know: to do this, you'll need Unlock bootloader, then installing a custom recovery, i recommend TWRP instead of CWM, i've got error with cwm once -> Get into Recovery Mode -> Backup -> Save it to your computer)
I've googled and tried some other ways to upgrade the phone, but it was not work, like:
http://forum.xda-developers.com/showthread.php?t=2573479
Flash another 4.2.2 ROM -> [Settings > About > Software update] -> Download (only) the OTA file -> Flash the stock recovery file -> Then the phone will alert "the update is downloaded and ready"
Click to expand...
Click to collapse
Well, that's the idea. But right after your download is done (in your phone), it turns out error: "Variant system version", saying your phone has been modified, and end up by delete the OTA file
Let's get started
1. Requirement, Your phone must be:
Disabled Fast Boot:
Settings > Power > Untick Fast boot
Click to expand...
Click to collapse
Enabled USB Debugging:
Settings -> Developer Options -> USB Debugging
If you do not see "Developer Options", Go to Settings > About phone > Software > More > click on build number 7 times. This should enable that section
Click to expand...
Click to collapse
Unlocked Bootloader
Got the S-Off (For HTC phones, to: be able to write to /system)
Installed a custom recovery (recommend TWRP)
The guide can be found at here: http://forum.xda-developers.com/showthread.php?t=2365506
2. Download the OTA file
You can use any OTA files, like the EU, the international,...
For HTC One mini, 4.3 OTA file can use this: OTA_M4_UL_JB43_SENSE55_MR_HTC_Europe_2.12.401.1-1.32.401.2_release_342200vz5jcl35ysxswchv.zip by http://forum.xda-developers.com/showpost.php?p=48404636&postcount=1
3. Flash the firmware
Extract the OTA file you'll get firmware.zip
Make sure you already got the fastboot.exe, adb.exe, AdbWinApi.dll, ... files -> Move all these files + the firmware, the OTA file into a folder like: D:\htc
Reboot your phone into Fastboot USB Mode
Power off > Hold the both Volume Down key + Power key several seconds > Fast Boot
(Use the Volume key to change the selection, the Power key to chose/enter)
Click to expand...
Click to collapse
Make sure your phone is recognized by fastboot and adb, to check:
fastboot devices
- and:
adb devices
Click to expand...
Click to collapse
In case you got error "Device not found" with adb: turn the phone into Recovery Mode, it will fix this, so you can do adb push, shell...
Relock the bootloader, so we can flash the firmware update:
fastboot oem lock
The phone will reboot
Click to expand...
Click to collapse
Reboot to OEM update mode:
adb reboot oem-78
The phone will show the white-text HTC
Click to expand...
Click to collapse
Flash the firmware.zip:
fastboot flash zip firmware.zip
You'll see a green progressbar on the screen, if not: do the command again
Click to expand...
Click to collapse
Unlock Bootloader from http://htcdev.com, install the TWRP Recovery again
fastboot flash unlocktoken Unlock_Code.bin
fastboot flash recovery Twrp-2.6.0.0.img
You might need to get the new Unlock_Code.bin from htcdev
Click to expand...
Click to collapse
Now your phone is wiped, the /sdcard/ folder is empty
4. Make the OTA Flash-able file
Download the sample.zip file at here, we'll rename it to: OTA-4.3.zip, see How to make a flashable zip at here: http://forum.xda-developers.com/showthread.php?t=2163974
Open OTA-4.3.zip with winrar or 7zip, you'll see 2 folders: META-INF/ and system/ . We're going to put data from the OTA file into this zip file (Notice that the system/ folder is empty)
From the extracted OTA file that you've downloaded (OTA_M4_UL_JB43_SENSE55_MR_HTC_Europe_2.12.401.1-1.32.401.2_release_342200vz5jcl35ysxswchv.zip) copy 2 folders: system/ and patch/ into OTA-4.3.zip, just drag and drop them to opened OTA-4.3.zip (by winrar), hit OK in the winrar popup
--> You might wonder why we're doing this: Why we put 2 folders from OTA_M4_UL_JB43_SENSE55_MR_HTC_Europe_2.12.401.1-1.32.401.2_release_342200vz5jcl35ysxswchv.zip to the new, almost empty OTA-4.3.zip; instead of delete all other files, folders from OTA_M4_UL_JB43_SENSE55_MR_HTC_Europe_2.12.401.1-1.32.401.2_release_342200vz5jcl35ysxswchv.zip
--> The anwser is: i have no idea, the second way just doesn't work, i tried
5. Flash the OTA Flash-able file
Copy the OTA Flash-able file (OTA-4.3.zip) into your phone, your phone can not boot up now, so we'll use adb push command
adb push OTA-4.3.zip /sdcard/
It may takes few minutes
Click to expand...
Click to collapse
Now simply Install Zip from recovery:
Boot into Recovery Mode > Install Zip > select OTA-4.3.zip
Click to expand...
Click to collapse
Reboot the phone, if everything goes well, it's showing a progressbar of the Apps installing
You're now in 4.3
Thank you for this information but unfortunately it didnt work for me.
windovv said:
You'll see a green progressbar on the screen, if not: do the command again
Click to expand...
Click to collapse
I do see the green progress bar and it moves to the right but....
the Fastboot/DOS window finishes the flash firmware command successfully but the green progress bar shown on the phone does not go to the very end.....
so at this point I reboot back to fastboot on the phone and then unlock the bootloader then follow the rest of your instructions....
Everything appears to be successful but when i boot the phone it displays the boot animation to the end then just stays there....The phone never goes past the boot animation
Ive managed to restore a backup so thats not a problem but im really struggling to install the 4.3 and sense 5.5 update using the other method shown at the beginning of your post and your method here
anyhow, looks my radio, HBOOT etc is updated now ive flashed the "firmware.zip" from my OTA
Sirius-C said:
Thank you for this information but unfortunately it didnt work for me.
I do see the green progress bar and it moves to the right but....
the Fastboot/DOS window finishes the flash firmware command successfully but the green progress bar shown on the phone does not go to the very end.....
Click to expand...
Click to collapse
I think this step is just fine, i've noticed that the progress bar was near to the end, not full of the bar. If you not sure about this, you can do this step (run this command) twice:
fastboot flash zip firmware.zip
You'll see a green progressbar on the screen, if not: do the command again
Click to expand...
Click to collapse
Everything appears to be successful but when i boot the phone it displays the boot animation to the end then just stays there....The phone never goes past the boot animation
Click to expand...
Click to collapse
It seems like you have just flashed the firmware.zip only, the rest of the OTA file has not been flashed successfully yet. The phone is now wiped, so it can't boot up
Reboot the phone, if everything goes well, it's showing a progressbar of the Apps installing
Click to expand...
Click to collapse
Notice that in some cases, there's no progressbar showing, but the phone still configuring itself, and it can takes about 5-10 miniutes
so at this point I reboot back to fastboot on the phone and then unlock the bootloader then follow the rest of your instructions....
Click to expand...
Click to collapse
At this step, pls install a custom recovery ~> goto recovery mode ~> File Management, you'll see that there're system folders, like /sdcard/, check out if they're empty or not...
Bottom line: make sure firmware.zip has been flashed (do the flash command twice), verify step 4 and step 5 in #1
Hello,
Many thanks for your reply.
I did flash the OTA zip after modifying it. I can only think that I did not wait long enough after the boot animation, although i did wait approx 5 minutes or more.
Since posting here I have managed to install the OTA update but I used the alternative method here:
http://forum.xda-developers.com/showthread.php?t=2573479
I already had an unlocked bootloader and S-OFF so I skipped that part of the tutorial...
But I was unsuccessful the first time because I did not SUPERCID, as I read passed it..
The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.
placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed
After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.
Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now
Thread was opened.
mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot
Would this work on Blu Vivo XI since same chipset?
sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer
Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof
mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!
UPDATE:
As i don't have much time, here is the link to our Alcatel tetra and ideal xtra development and support group on telegram.
ALL THE FILES THAT USED TO BE LINKED HERE ARE AVAILABLE AT THE MENTIONED TELEGRAM GROUP
https://t.me/Android_General_Chat
Any questions for myself need go there.
Thanks.
LgPWNd
Ok so I am here today to give you a TWRP recovery and A Liniage OS 16 Rom ported from a GSI.
And a quick how to on setting it all up..
DISCLAIMER:
I Am In No WAY responsible for ANYTHING YOU choose to do to your phone.
If you use this and your Dog eats your Cat, Your phone catches fire and burns down your house, or you loose all your game-saves pictures and other files it's NOT MY FAULT.
THIS WILL WIPE YOUR DATA AND FORMAT YOUR PHONE!!!
YOU'VE BEEN WARNED
MY FASTBOOT DOESN"T WORK !
See-This:
Just grab this package I made for @Sloogle_Flugelmann
https://drive.google.com/open?id=1CiGKCPGBJAPvl8R3_24kvdvrQB5V3abI
So requirements are :
#1: Willingness to format your phone and loose all apps and data.{MAKE A BACK-UP}
#2: ADB and Fastboot working on your PC.
#3: The Files I Will Link to or attach .
# Some Time to work on it, and half a Brain
There will be Two methods to accomplish basically the same thing,
Method 1 gives you the long way and it leaves you with the bare basic LOS 16 installed no root no gapps...
on the other hand Method 2 will leave you with LOS 16 and My favorite version of the pixil launcher and stock Gapps included and basically everything working.
METHOD 1-THE LONG ROAD:
STEP 1:
download the package that I will upload for everyone...
STEP 2:
Unlock your bootloader.... there may be multiple ways to do so but for me I enabled usb debugging and OEM unlocking in developers options {if you don't know how to do that you should run far away now !} then I gave the command
Code:
adb reboot bootloader
and this takes you to fastboot mode...
once there issue the following command to unlock your bootloader AND factory-reset the phone
Code:
fastboot oem unlock
then
Code:
fastboot reboot
Now your bootloader is unlocked and your device has been wiped in the process...
so let it boot up then go through the setup wizard and I just skip through everything as we will be wiping it once again in a minute... and just need to get to developer options and re-enable adb...
so do that...
STEP 3: Now that your bootloader is unlocked comes the fun stuff...
Firstly you need an SD-card with at least 4-6 GB free space and before continuing we want to move our LOS-16 System.img to our sd-card so we can install it from TWRP so once that's on the root of Sd-card's storage continue with this guide....
we need to disable DM-Varity to use twrp so we flash a magisk-patched-boot.img
so move the files Patched_boot.img AND twrp_alcatel_5059r_v3-2-3.img to a folder on desktop and open a command prompt /terminal/powershell-window at the file's location.. then issue this command to the phone .
Code:
adb reboot bootloader
and once again we are in fastboot mode.
now we want to use fastboot to replace the stock boot image and stock recovery with our patched boot image and twrp recovery image..
Code:
fastboot flash boot patched_boot.img
then
Code:
fastboot flash recovery twrp_alcatel_5059r_v3-2-3.img
after this we want to reboot to recovery using the hardware keys. because if we don't the stock system will erase our twrp and replace it with stock recovery on boot.
so we do
Code:
fastboot reboot
and soon as you press enter on your keyboard grab the phone and continually hold down the volume-up key and hold the power key .
once you see the alcatel logo and message about unlocked bootloader, you quickly release ONLY the power key for a second then repress and hold it for a count of 5 seconds. then release the power key again and quickly repress it for another 5 seconds and keep doing that for a moment until the screen flashes white then displays the TWRP splash screen.
once we are in twrp it'll ask for the encryption password...
WE DONT HAVE ONE , So just hit Cancel
then it'll ask about system modifications and whatnot,
just swipe to allow modifications.
now we want to head to Wipe > Advanced-Wipe > Format Data
you'll have to type in
Code:
yes
and let it do it's thing.
once done with that we need to reboot to recovery so click the back arrow several times until you are back at twrp's min screen.
head over to Reboot>Recovery
the phone should reboot right back to twrp, you shouldn't see the encryption password screen this time as we formatted DATA.
so now swipe to allow modifications and head back to
Wipe>Advanced-Wipe and check the boxes for system,dalvik-cache,cache,data....
then swipe to wipe them.
then you want to hit the back arrow again till at the main twrp screen again.
Head to Install click on select storage, choose your Sd-card
Click on install zip to change it to install image.
select the LOS image we moved to the Sd-card prieviously,
click on System as the install location.
and finally swipe to flash it.
let it do it's thing.
once completed you will want to click the back arrow again until main twrp screen and reboot to recovery once more....
now once in recovery again you swipe to allow modifications and need to replace the GSI's build.prop file with the one I am including in the zip.
I used adb to accomplish this...
on your PC move the included build.prop file to your working directory{folder your working out of}
and use the terminal/command prompt/powershell to give the following commands
Code:
adb devices
you should see the device identified by serial number and the word recovery next to it
then
Code:
adb shell
you should have a root shell on the device,
Code:
rm -rf /system/build.prop
then
Code:
exit
now your back to pc terminal so type:
Code:
adb push build.prop /system/build.prop
Code:
adb shell
back to root shell
Code:
chmod 0644 /system/build.prop
and then
Code:
reboot now
at this point your phone should reboot and everything was done correctly it'll go past the alcatel logo and bootlock message and then display the LOS 16 boot animation then it'll show a funny looking screen that has an android guy and the message " Please wait while your device is being encrypted"
it'll have a progress counter and when the count-down reacheds zero it'll just hang there....
that's ok, hold the power key until the phone reboots and you should get the los bootanimation followed by the LOS setup wizard start screen.
and you go through the set-up wizard and you'll be in LOS 16 PIE
Now if you want google apps to work there's a few more steps and they will be the same for both method 1 and method 2
if you flash gapps after rebooting from that you'll get a million messages about google play services and google apps crashing ... it's ok
you need to enable usb debugging in the LOS 16 and then sideload the apk ( Device+ID.apk )
Code:
adb sideload "Device+ID.apk"
once installed
open it to get the GSF registration number for your device.
then if you open the play store you'll be greeted by the google DEVICE UNCERTIFIED page...
Don't fret , this is why we fixed the build.prop to reflect our devices orig. build fingerprint...
So scroll down to the bottom of that page and see the last option about Custom Roms
there is a link there... long press that link and choose open in browser
you'll be greeted by the registration page for google...
make sure you are signed into google through your browser...( <---VERY IMPORTANT ) by opening another page to google gmail or the like and signing in with your google account.
then go back to the registration page and hit refresh ...
now it should recognize you by your gmail account in the top right corner i think.
anyhow... go to that ( Device+ID.apk ) that we sideloaded and click on the second set of numbers down the list it should mention (GSF) and choose copy . it'll copy the numbers to your clipboard.
now go back to the browser page from google about registration and paste the copied number into the place next to the (Register) button and then click the register button
it should then list your id converted to decimal on the page...
I did this several times from my PC and got no where but after doing it from the phone it's self a couple minutes later i clicked on one of the error messages about google play services and wholy-krap it finnally let me open google-play-store.
at this point your ready to go....
for an informative article with pictures about this check here:
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Now for Method 2
method two involves all the same steps as method 1 up until you get to TWRP... except that instead of moving the LOS16 system.img to your Sdcard before begining you'll want to extract the alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23.zip I've included and move that whole folder to the sdcard...then
go back and read method 1 and once you are booted into twrp for the first time STOP and come back here to Method 2
Now once you get to twrp the first time the first thing to do is click cancel on the encryption screen then swipe to allow modifications on the next screen. then once at the main twrp screen we need to make a back-up that we will likely never use...
so go to Backup>choose storage (micro sd-card) and then make a back-up, Name the back-up My-Backup so that you can easily find it later. to save space and time I'd recommend backing up just the boot partition.
that'll complete quickly...
now for the weird work-around/Dirty-Hack stuff
you should have the contents of alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23.zip a folder called (alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23) on the root of your sd-card's storage...
and we just made our first back-up from twrp of our boot partition.
so from the main twrp screen we go to Advanced>File-manageer>external_sd we should find a folder labeled(TWRP)
inside that should be a folder labled (BACKUPS) and inside that should be yet one more folder with your device's serial or android ID as the label mine is (49NJ6TORP****VRG) your's may read differently. and finally inside That folder you should find the back-up you previously made (My-Backup) if you followed my instructions.
now we need to go back to the root of our sd-card's storage by clicking (up a level) several times and then click on the folder i had you move there earlier (alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23) and once you click it you'll see files inside look down to the right hand corner in twrp
you should see a little blue folder button with a check-mark , Click that button
then it'll show you options....
click (Move) button then click (up a level) it'll look like it took you all the way back to the beginning top level of file manager, now we navigate to where we want the folder Moved to, so click external_sd > TWRP>BACKUPS>49NJ6TORP****VRG"or what-ever it named your device" > and when you see your (My-Backup) folder STOP... now click the folder button bottom right again, and you're presented with a screen saying moving blah blah blah : to : blah blah blah...
just swipe to move it there.
once you've done that click the back arrow to leave file manager and back out to the main twrp screen again...
Now click Restore>select storage> Micro Sdcard >ok and you should see two things to choose from...
(My-Backup) " the one you created earlier "
and
(alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23)
obviously choose the second one (alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23)
it'll ask you which partitons to restore
make sure ALL of the available boxes are checked should be boot, recovery, cache, and system
then swipe to restore...
after that's done we want to make sure we don't have any issues so back out to the main twrp screen
go to Wipe>Advanced Wipe and choose Dalvik/art Cache and also Cache and Data
swipe to wipe.
then back out once more and goto Wipe>Format Data and type yes and click the blue check mark on the keyboard to continue
after formating data
back out to main twrp screen and go to Reboot>System and if prompted choose NOT to install TWRP app
it wont work for you any way.
it should now reboot and do the please wait while encrypting your device thing again ...
after it counts down to zero it'll hang so just hold down the power button until it reboots and you'll get los boot animation followed by Los setup wizard.
go ahead and setup your device once completed the setup wizard you'll want to follow the part at the end of Method 1 above to get google apps and playstore working.....
then you're Done.
enjoy
NOTE with method two you'll also have a modified /system/etc/hosts file so you'll basically have ad malware and porn protection too. if you don't want that you can replace the content of your hosts file with
Code:
127.0.0.1 localhost
::1 localhost
from twrp etc.
if you like what I've done and want to motivate me to do even more please click thanks and consider a small donation of the price of a coffee or stout Beer
AIO-Package = https://drive.google.com/open?id=14fXqm4fjHtNJ8gm9M2SUdybuFAbIyHjJ
EDIT Somehow forgot to add the magisk patched boot.img to the file
will upload separately later
EDIT: 2
here's the zip with patched_boot.img
UNZIP IT
https://drive.google.com/file/d/1R8Sar9yx6mI7by02v83uEprmBOc7_9I1/view?usp=sharing
Edit 3:
Alternate "Better" recovery. !
there are two other recovery ports and I'd recommend either of them over this TWRP.
That being said, if you use method 2 to restore my back-up above...
Please do so with the twrp linked here as thats what made the back-up.
Here's The link to other better recoverys...
keep digging for it
almost there..
.
Link: https://forum.xda-developers.com/android/development/recovery-pitchblack-redwolf-recoverys-t3947609
EDIT 4:
Making Magisk Just WORK Dammit!
So here is something Nice, We now can have Magisk root on any Pie GSI's by flashing this zip-file .
NOTE TO THREAD HOPPERZ:
THIS IS INTENDED ONLY FOR THIS DEVICE.
IT WILL LIKELY WORK ALSO ON THE ALCATEL TETRA SINCE THE FILES AND PATH ARE THE SAME
DO NOT FLASH THIS TO ANYTHING ELSE!!!
Credit for this go's to a guy who figured out the lib file was missing in most gsi images,
My-self for putting it all together in a flashable zip.
and to @TheExploitedOne for his help fixing error 6 on my updater script and blindly flashing it first
The-Good-Stuff: https://drive.google.com/open?id=1qgZJyEOfVuN7POv_YKAunm-62oNRFhUb
Credit where it's due:
@Sloogle_Flugelmann and @riskybusiness
for the thread located:
https://forum.xda-developers.com/android/help/alcatel-idealxtra-5059r-root-t3885536
Which got me thinking....
also
@Andy Yan for building the GSI that I used to port this
@phhusson for all the work on treble and GSI'S that made this possible
@topjohnwu for magisk
and Alcatel / TCL for making it easy this time.
Ok so I found a way to disable forced encryption.
allowing TWRP to use our /Data partition again Yeay!!!
So here's how to do it...
Download the attached file from this post....
put it on your desktop or what ever folder your working out of...
Extract IT and find fstab.mt6739
open your terminal/CMD window and then boot to TWRP.
once in TWRP go ahead and go to Mounts>vendor
and make sure /vendor partition is mounted...
then go back to the pc and type...
Code:
adb shell rm -rf /vendor/etc/fstab.mt6739
Code:
adb push fstab.mt6739 /vendor/etc/fstab.mt6739
Code:
adb shell chmod 0644 /vendor/etc/fstab.mt6739
now go back over to fone, and in twrp back out to main screen and then go to wipe>format Data >type yes
let it do that....
once finished go ahead and reboot to android system
It'll boot up and takes a few minutes to go through the whole set-up wizard again.
but this time you will NOT see the darn little Encrypting the Krap out of android screen...
PROFIT !!!!!
Method 2:
NO PC NEEDED
Download attached file , EXTRACT IT , move fstab.mt6739 to your external sd card....
reboot to twrp,
in twrp at main screen go to
Mount>vendor and make sure /vendor is mounted, and mount> Micro SD Card make sure you have sdcard mounted...
then hit back arrow.
from main screen go to Advanced > File Manager > vendor > etc > fstab.mt6739
click the file and then click Delete
now scroll back to top (Up A Level) > (Up A Level) > external_sd
now look for the file you downloaded with the name fstab.mt6739
click on it then click Move
then once again vendor > etc
now click the little blue folder icon bottom right corner
It'll say,
Moving
Blahblahblah
to
Blahblahblah
just swipe to confirm
after that hit Back
now to fix the permissions
(up a level) > vendor > etc > click on fstab.mt6739
click on chmod
it'll show
Permissions
0000
go ahead and delete the zeros and then type 0644
then hit the checkmark to complete action (bottom right corner)
once done just hit back back back...
till main twrp screen
now to format data to remove the encryption...
back out to main screen and then go to wipe>format Data >type yes
let it do that....
once finished go ahead and reboot to android system
It'll boot up and takes a few minutes to go through the whole set-up wizard again.
but this time you will NOT see the darn little Encrypting the Krap out of android screen...
PROFIT !!!!!
If this helped you, please consider the thanks button....
If this saved your day maybe you'd like to buy me a cup of coffee?
ENJOY
Network unlock package available now
Ok so I have found a way to network unlock the fone but developing it has cost me nearly $80
I am considering sharing a restore package that you can use to restore a back-up from twrp to get your fone Unlocked for any GSM carrier...
But as I have seen NO ONE post in this thread yet, I'll save it...
I may even make it a gift for anyone who donates anything more than $3 to me for my time effort and expenses in developing all this stuff.
if anyone's interested either hit thanks and post about your interest here...
or shoot me a private message...
Got it fully rooted
I got the los 16 pie gsi rooted through a long combination of dirty hacks that in the end allows the official los 16 addonsu to work correctly.
Don't know if ill ever get around to sharing exact details but I will upload a rooted los 16 rom here very soon
will work on that getting that rooted system.img uploaded sometime this week hopefully
Alcatel Da And Auth Files
I scoured the net and finally took apart another program to get these but here's the AUTH & DA files for this device....
also going to add an archive containing all ALCATEL DA and AUTH files I have now....
of course it seems I'm the only one interested in this device...
so probably no one will ever think to look here for them...
but if you do , And if this helps in any way....
Don't forget to click thanks button
Come a long way on this device...
Too bad no one else seems interested ?
Fastboot mode is disabled on mine. adb reboot bootloader just restarts mine.
I have a fix for you
Sloogle_Flugelmann said:
Fastboot mode is disabled on mine. adb reboot bootloader just restarts mine.
Click to expand...
Click to collapse
I'll load up a lk.bin that you can flash using root and DD.
I'll include a ReadMe with exact instructions.
For temp root to flash the lk.bin you're gonna want to use mtk-su
I'll include everything needed in a zip and load it up here.
May take me a little bit since I'm hanging with the family for 4th.
Happy 4th of July
Sloogle_Flugelmann said:
Fastboot mode is disabled on mine. adb reboot bootloader just restarts mine.
Click to expand...
Click to collapse
@Sloogle_Flugelmann
Thanks for bringing that to my attention,
I been so busy developing for the tetra lately because no one seemed interested here.
If you go back and re-read OP,
I've added a fastboot fix zip with everything needed and instructions
the zip is for a windows user ,
for linux just replace the ./adb.exe with adb
in the commands issued to pc
Let me know if you need help.
LgPWN'd said:
@Sloogle_Flugelmann
Thanks for bringing that to my attention,
I been so busy developing for the tetra lately because no one seemed interested here.
If you go back and re-read OP,
I've added a fastboot fix zip with everything needed and instructions
the zip is for a windows user ,
for linux just replace the ./adb.exe with adb
in the commands issued to pc
Let me know if you need help.
Click to expand...
Click to collapse
Awesome! Thank you. Yeah I just got this phone as a secondary/backup phone and assumed nobody would even be interested in doing anything with this phone. Was kinda surprised to see any progress.
Also, I recommend using Wordpad because Notepad made it one long line of text
Regardless of what or how many times I try, I always end up on a stuck boot screen with circle crossing the screen on the LOS16 rom.
Sloogle_Flugelmann said:
Regardless of what or how many times I try, I always end up on a stuck boot screen with circle crossing the screen on the LOS16 rom.
Click to expand...
Click to collapse
It take a while to boot up
Did u try the backup/restore method?
It always takes mine a bit to boot up.
LgPWN'd said:
@Sloogle_Flugelmann
Thanks for bringing that to my attention,
I been so busy developing for the tetra lately because no one seemed interested here.
If you go back and re-read OP,
I've added a fastboot fix zip with everything needed and instructions
the zip is for a windows user ,
for linux just replace the ./adb.exe with adb
in the commands issued to pc
Let me know if you need help.
Click to expand...
Click to collapse
Can you patch fastboot in my Alcatel A7 XL?? Please, it's disabled...
I can use mtk-su since is arm64 MT6750.
Here is the lk.bin:
https://drive.google.com/file/d/1-ATD4aw5tQZHSWpvcM70qhdAcOYGCXKM/view?usp=drivesdk
Rortiz2;798[INDENT said:
[/INDENT]49897]Can you patch fastboot in my Alcatel A7 XL?? Please, it's disabled...
I can use mtk-su since is arm64 MT6750.
Here is the lk.bin:
https://drive.google.com/file/d/1-ATD4aw5tQZHSWpvcM70qhdAcOYGCXKM/view?usp=drivesdk
Click to expand...
Click to collapse
The issue will be this:
If I modify that in any way and you flash it
You will have a brick .
You can only flash modded images after you unlock the bootloader.
Best advice is to look for older or other copies of firmware from the manufacturer and hopefully one of those will allow you to get fastboot.
Anything not signed by manufacturer will brick u .
LgPWN'd said:
The issue will be this:
If I modify that in any way and you flash it
You will have a brick .
You can only flash modded images after you unlock the bootloader.
Best advice is to look for older or other copies of firmware from the manufacturer and hopefully one of those will allow you to get fastboot.
Anything not signed by manufacturer will brick u .
Click to expand...
Click to collapse
Ugh, so it will enter in a red state and it will refuse to boot...
So there's no any way?
PS: I can't find stock FW in any site...
LgPWN'd said:
@Sloogle_Flugelmann
Thanks for bringing that to my attention,
I been so busy developing for the tetra lately because no one seemed interested here.
If you go back and re-read OP,
I've added a fastboot fix zip with everything needed and instructions
the zip is for a windows user ,
for linux just replace the ./adb.exe with adb
in the commands issued to pc
Let me know if you need help.
Click to expand...
Click to collapse
LgPWN'd said:
It take a while to boot up
Did u try the backup/restore method?
It always takes mine a bit to boot up.
Click to expand...
Click to collapse
I left it for over 30 mins. I'll try the backup/restore method tonight.
UPDATE: The backup/restore method worked and I was able to get it booted. Thank you so much! This is awesome
What would u like to see for it next?
Sloogle_Flugelmann said:
Awesome! Thank you. Yeah I just got this phone as a secondary/backup phone and assumed nobody would even be interested in doing anything with this phone. Was kinda surprised to see any progress.
Also, I recommend using Wordpad because Notepad made it one long line of text
Click to expand...
Click to collapse
Ive got several other recoveries for it.
Going to start work on several other device specific
System images for it.
Open for suggestions
I've been intrested a while now!
NOTE: I do have fastboot now from your package
Are you able to upload a copy of the unlocked bootloader images? I currently can't use fastboot because it requires USB 2.0 rather than 3.0 (which is bs in my opinion). I just plan to flash the images and unlock without the data wipe. Thank you again for your work sir!!!!
You'll have to use fastboot to unlock bootloader.
TheExploitedOne said:
I've been intrested a while now!
NOTE: I do have fastboot now from your package
Are you able to upload a copy of the unlocked bootloader images? I currently can't use fastboot because it requires USB 2.0 rather than 3.0 (which is bs in my opinion). I just plan to flash the images and unlock without the data wipe. Thank you again for your work sir!!!!
Click to expand...
Click to collapse
No way around fastboot oem unlock....
But.
I've done it from another Android with a usbotg cable between the two
Hello everyone.
So I've been having some trouble changing my boot animation in my Pixel 4a running Android 12. I have tried every method I possibly can, and nothing seems to work. My device is rooted, and the bootloader unlocked. I have all necessary drivers updated, debugging enabled, etc etc.
I have tried:
Boot Animation apps - Just give error messages
Rebooting the bootloader into recovery to flash the .zip - This option isn't available in my boot recovery
5-6 different file manager apps - all of them won't let me either delete the original bootanimation.zip file or copy/paste the new one I have ready to go
Using a windows based root file manager - same as above
Is htis an Android 12 issue? Since it was released relatively recently I just need to wait for an updated method?
Any help would be appreciated. Thanks.
DKM-Eby said:
Hello everyone.
So I've been having some trouble changing my boot animation in my Pixel 4a running Android 12. I have tried every method I possibly can, and nothing seems to work. My device is rooted, and the bootloader unlocked. I have all necessary drivers updated, debugging enabled, etc etc.
I have tried:
Boot Animation apps - Just give error messages
Rebooting the bootloader into recovery to flash the .zip - This option isn't available in my boot recovery
5-6 different file manager apps - all of them won't let me either delete the original bootanimation.zip file or copy/paste the new one I have ready to go
Using a windows based root file manager - same as above
Is htis an Android 12 issue? Since it was released relatively recently I just need to wait for an updated method?
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Have you also enabled r/w permissions for the system partition?
Droidriven said:
Have you also enabled r/w permissions for the system partition?
Click to expand...
Click to collapse
Every time I try with my root file manager it says "error changing permissions." I'll add a screenshot of what they currently are.
The error on the bottom is after I added the check mark in the Owner row, under the S column. The other ones were already set.
DKM-Eby said:
Every time I try with my root file manager it says "error changing permissions." I'll add a screenshot of what they currently are.
The error on the bottom is after I added the check mark in the Owner row, under the S column. The other ones were already set.
Click to expand...
Click to collapse
Put a check in the box beside "recursive" in the upper part, and tap "apply" then, in the lower part, check the box beside "recursive" then tap "apply".
Droidriven said:
Put a check in the box beside "recursive" in the upper part, and tap "apply" then, in the lower part, check the box beside "recursive" then tap "apply".
Click to expand...
Click to collapse
Still gives error while trying to apply.
DKM-Eby said:
Still gives error while trying to apply.
Click to expand...
Click to collapse
Boot to recovery and choose the option to "wipe cache partition", if you have custom recovery, wipe the cache partition and the dalvik cache partition(DO NOT factory reset). After wiping cache(s), reboot the device and then see if that helps.
Any time you make a change of any kind to the system partition, rebooting to recovery and then wiping the cache partition(s) and then rebooting is usually required in order for the changes to take effect.
Droidriven said:
Boot to recovery and choose the option to "wipe cache partition", if you have custom recovery, wipe the cache partition and the dalvik cache partition(DO NOT factory reset). After wiping cache(s), reboot the device and then see if that helps.
Any time you make a change of any kind to the system partition, rebooting to recovery and then wiping the cache partition(s) and then rebooting is usually required in order for the changes to take effect.
Click to expand...
Click to collapse
There are no options in my recovery mode to wipe the cache for anything. The only thing available in recovery was to factory reset.
I also noticed something in Magisk - I installed the boot animation changer module, and when running it, it says it does not support my sunfish kernel. So I'm wondering if my Pixel 4a is just completely unable to perform this action?
DKM-Eby said:
There are no options in my recovery mode to wipe the cache for anything. The only thing available in recovery was to factory reset.
I also noticed something in Magisk - I installed the boot animation changer module, and when running it, it says it does not support my sunfish kernel. So I'm wondering if my Pixel 4a is just completely unable to perform this action?
Click to expand...
Click to collapse
You don't have a stock recovery if you don't see the option to wipe cache partition. Can you post a screenshot of what your recovery looks like.
If Magisk says it doesn't support your kernel, you need to see if there is a custom kernel available for Pixel 4a that it does support.