Related
Hello everyone,
First of all, let me excuse if I make mistakes in english, because I'm french. Thanks a lot.
Thanks for these who could help me in this issue and who would take of their time to help me.
My position is this one :
________________________________________________________________________________________________________
Device bought in France (Europe)
Device : Slider SL101
Android Version : 3.2.1
Core Version : 2.6.36.3 [email protected] #1
Build number : HTK75.WW_epad-8.6.6.19-20111101
MobileDock Version : SL101-0202
Device is near Vanilla (I did install Superuser on it -i think-, but that's all, no other changes have been done).
When I start my device with POWER + VOL DOWN :
Black screen with Eee Pad logo in the middle + Asus logo at the bottom + NVidia logo at the bottom + white sentences at the top left of the screen telling
"Android ww_epad-user bootloader < e> released by "WW_epad-8.6.6.19-20111101.
Checking for android ota recovery
Checking for RCK... press key <VOL_UP> in 5 sec to enter RCK"
=> here, 2 solutions : either I press VOL_UP (A.), or I do nothing (B.)
A. if I press VOL_UP
A new sentence appears under the previous "Booting recovery kernel image".
Then, a new screen appears named "ClockworkMod Recovery v6.0.1.3" => in the middle of the screen is a rolling gear with a hat on it
B. if I do nothing
A new screen appears : black screen with two logos in the middle -a "Wipe Data" logo + a "Android" logo which is surrounded by a green light + sentences at the top left of the screen telling "OS will cold boot in 10 secs if the selected mode is not confirmed. Press <VOL_DOWN> to change mode, Press <VOL_UP> to confirm mode."
________________________________________________________________________________________________________
My questions are :
________________________________________________________________________________________________________
1. What are the names of theses different screens, so i can use the right vocabulary ? Why do we use them ? Brievely.
2. Is my device able to be on a newer Android version (4.4.2 ? or other ?) ? If yes, what do I need to do ?
3. Is there a way I can uninstall all "Default" applications installed on the device "AmazonKindle", "My Library", "MyNet" for example ?
3. Do you need more informations to answer my questions 1, 2 & 3 ? ^^ If yes, tell me and i'll try to give them
________________________________________________________________________________________________________
Thanks a LOT to all of you !
Bye
Hey there!
1. Situation A is called RECOVERY, in your case you have a costume one - a good start already!
I have no idea how situation B is called...
2. Yep, it is able to run 4.4.2, just like mine! Actually, I'm on it right now
What you are need to do is:
A. Download and install TWRP Recovery by sidneyk. Reboot to TWRP
B. Download and install KatKiss 4.4.2 ROM and gapps by timduru , and install them, duh!
C. Download and install the SL compatibility pack V2, install after rebooting to the ROM.
Install all these in advance!
Visit here to find the links.
If you are a noob, and you don't really know how to install... Don't be shy! Just say!
There are plenty of guides here, and if you need help - just ask
3. Once you have KitKat on your slider, PUFF! All these apps will be gone!
Hey ! First of all, thanks for your time to help ! Really !
Now, to answer to your answer ^^ :
1. OK
2. Good news for 4.4.2
A. Download and install TWRP Recovery by sidneyk. Reboot to TWRP
B. Download and install KatKiss 4.4.2 ROM and gapps by timduru , and install them, duh!
C. Download and install the SL compatibility pack V2, install after rebooting to the ROM.
Click to expand...
Click to collapse
==> Sorry, I really don't know how to do this :/
Install all these in advance!
==> what do you mean by this ?
Visit here to find the links.
==> I visited the page, but I don't really know what to do :/
3. Ok for that
I will answer asap to your replies coz i really wd like to go on a newer version of Android on this sexy slider
The Triple said:
Hey ! First of all, thanks for your time to help ! Really !
Now, to answer to your answer ^^ :
1. OK
2. Good news for 4.4.2
==> Sorry, I really don't know how to do this :/
Install all these in advance!
==> what do you mean by this ?
Visit here to find the links.
==> I visited the page, but I don't really know what to do :/
3. Ok for that
I will answer asap to your replies coz i really wd like to go on a newer version of Android on this sexy slider
Click to expand...
Click to collapse
Whoops, I meant download, not install, it was late that time
As I get home I'll post how to
HOW TO
Here is how to update your slider:
I recommend you to read a bit on costume recoveries and ROMs
Backup your data! (you can do it with titanium backup)
Download 2.6.3.9 TWRP Recovery ZIP by sidneyk here.
Download KatKiss 4.4.2 ROM, GApps and the SL compatibility pack V2 ZIPs by timduru from here.
Place all these ZIPs on a micro SD card.
Enter to recovery mod, install from the SD card the TWRP ZIP. Reboot to recovery. It should be now TWRP...
WIPE-->advanced wipe-->check cache, dalvik cache, data and SYSTEM.
Install KatKiss 4.4.2 ROM and gapps. Wipe cache & dalvik cache. Reboot system and wait.
After booting successfully to the ROM, power off your SL, boot it to recovery.
Install the SL comp. pack, wipe cache & dalvik cache, reboot system.
That's all
And don't forget:
/* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in the ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
DK5 said:
Reboot to recovery. It should be now TWRP...
Click to expand...
Click to collapse
Rebooting in recovery (for most recoveries) can be done by pressing the power button and volume down at the same time when your pad is off. If installed TWRP you do the same, but do an additional volume up press after you pressed Power button + volume down.
@DK5: some ppl dont know how to go in recovery or how to activate it.
kevroy said:
Rebooting in recovery (for most recoveries) can be done by pressing the power button and volume down at the same time when your pad is off. If installed TWRP you do the same, but do an additional volume up press after you pressed Power button + volume down.
@DK5: some ppl dont know how to go in recovery or how to activate it.
Click to expand...
Click to collapse
He mentioned in the OP he was able to enter recovery mode. He asked what is the term for the situation and I answered it is called recovery mode. Therefore, he should know how to get into recovery mode.
Moreover, using the internet is not harmful if something is unclear...
DK5 said:
Here is how to update your slider:
I recommend you to read a bit on costume recoveries and ROMs
Backup your data! (you can do it with titanium backup)
Download 2.6.3.9 TWRP Recovery ZIP by sidneyk here.
Download KatKiss 4.4.2 ROM, GApps and the SL compatibility pack V2 ZIPs by timduru from here.
Place all these ZIPs on a micro SD card.
Enter to recovery mod, install from the SD card the TWRP ZIP. Reboot to recovery. It should be now TWRP...
WIPE-->advanced wipe-->check cache, dalvik cache, data and SYSTEM.
Install KatKiss 4.4.2 ROM and gapps. Wipe cache & dalvik cache. Reboot system and wait.
After booting successfully to the ROM, power off your SL, boot it to recovery.
Install the SL comp. pack, wipe cache & dalvik cache, reboot system.
That's all
And don't forget:
/* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in the ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
1. I downloaded all 3 ZIPs from the links you gave me (KatKiss-4.4.2_019.zip ; KatKiss-4.4.2_019-sl101-compat-V2.zip ; signed_twrp-2.6.3.9_sl101).
2. I put them onto a microSD Samsung SD HC Class (2) 8Gb in FAT32 -- they are all 3 on the racine (i:\) and are not renamed.
3. my µSD in the Slider, I "power + vol_down" then go to clockworkmod recovery.
4. I choose "install zip from sdcard" => then "choose zip from sdcard"
5. text appears at the bottom telling
"E:unknown volume for path [/sdcard/]
E:Can't mount /sdcard/"
So, i cannot install any of the ZIPs.
What did I do wrong ? Or what do I need to do now ?
hello
do you have an idea ?
i really need your help :/
The Triple said:
hello
do you have an idea ?
i really need your help :/
Click to expand...
Click to collapse
I've searched a bit, you should do it too...
Try to place the TWRP ZIP on your SL and then continue the process.
Sent from my Nexus 5 using xda app-developers app
The Triple said:
hello
do you have an idea ?
i really need your help :/
Click to expand...
Click to collapse
Have a look at Frederuco's guide HERE. Now his guide applies to the TF101 and you have the slider but the previous post told you which ROM to download. Also, you have a rooted device, so all you have to do is flash the TWRP, reboot and boot into recovery and then flash the ROM and GAPPS.
A previous post advised you to put the TWRP on the Slider (not on the SD card) which may help, as the Slider s formatted to use an internal SD card (e.g. its memory) and an external SD card which maybe Clockwork Mod can't see, so putting the TWRP flash on the slider could be your answer. Once TWRP is installed, it can see both the internal and the external storage so you can install the ROM and GAPPS.
CWM for Galaxy Tab 4 10.1
From Wikipedia:
CWM replaces the stock recovery of your Android phone. Using this recovery you can then do various system level operations on your phone, such as create and restore images backups of your phone, flash a portion of or an entire custom ROM, and use other developer tools.
Click to expand...
Click to collapse
XDA:DevDB Information
Clockworkmod 6.0.5.0 Galaxy Tab 4 10.1 [SM-T530], ROM for the Samsung Galaxy Tab 4
Contributors
tgalal
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Current Stable Version: 6.0.5.0
Current Beta Version: 6.0.5.0
Created 2014-07-28
Last Updated 2014-07-28
Reserved
Attached is Clockworkmod v6.0.5.0 for Tab 4 10.1 (SM-T530)
Configuration for building: https://github.com/tgalal/android_device_samsung_matissewifi
Compiled kernel sources for SM-T530 from http://opensource.samsung.com/
This is still in testing, try at your own risk.
WARNING: THIS WILL TRIGGER KNOX COUNTER AND VOID YOUR WARRANTY
Install instructions:
Flash using Odin or Heimdall. For Heimdall extract the tarball first
heimdall flash --RECOVERY recovery.img
Click to expand...
Click to collapse
Feel free to submit changes/ report any bugs/enhancements
tgalal said:
Attached is Clockworkmod v6.0.5.0 for Tab 4 10.1 (SM-T530)
Configuration for building: https://github.com/tgalal/android_device_samsung_matissewifi
Compiled kernel sources for SM-T530 from http://opensource.samsung.com/
This is still in testing, try at your own risk.
Install instructions:
Flash using Odin or Heimdall. For Heimdall extract the tarball first
Feel free to submit changes/ report any bugs/enhancements
Click to expand...
Click to collapse
heimdall didn't work for me. But what I did (on rooted device) was:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p15 of=/sdcard/stock-recovery.img
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p15
reboot recovery
CWM is booting fine, but gives several errors:
Code:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't mount /cache/recovery/last_install
E: can't open /cache/recovery/last_install
on each operation. The log gives:
Code:
mount: mounting /dev/block/platform/msm_sdcc.1/by_name/cache on /cache failed: invalid argument
W: failed to mount /dev/block/platform/msm_sdcc.1/by_name/cache (file exists)
Also mount the external sdcard to /sdcard failed, this fixed it:
Code:
adb shell
rm /sdcard
mkdir /sdcard
mount /sdcard
but only temporary of course. In your image /sdcard is a link to /sdcard (to itself), so it can't work. For /cache however
Code:
adb shell
mount /dev/block/platform/msm_sdcc.1/by_name/cache /cache
worked just fine, until doing something. I can't find the issue here.
Not working on tab 4 10.1 wifi i cant find my sdcard and external sdcard
Skickat från min SM-T530 via Tapatalk
Please support galaxy tab4 sm T531 tnx
Please support Galaxy tab 4 T300NU
@tgalal
hi, thank you for your work and effort.
I may be getting one of these tabs to work on and had a question as to if i need degas boot image tools.
looking in you tree for matissewifi i noticed the inclusion of recovery.img-dt.
If i do come into the device I would first need to secure a back up of the original boot and recovery .img's
Any help, tips, pointers would be greatly appreciated.
I ask because i will need to perform the entire process from scratch regardless of existing source/work.
thank you for your time.
m
I have a backup of boot and recovery. IMG backed up and posted online for download for the t330nu
---------- Post added at 11:03 PM ---------- Previous post was at 11:03 PM ----------
If it helps for me to post download links let me know
@Setialpha, have u solved the mounting-problem ?
tgalal said:
CWM for Galaxy Tab 4 10.1
Clockworkmod 6.0.5.0 Galaxy Tab 4 10.1 [SM-T530], ROM for the Samsung Galaxy Tab 4
Created 2014-07-28
Last Updated 2014-07-28
Click to expand...
Click to collapse
Hi, thanks for your work here.
However, it seems that there still are a few issues that is not yet solved here. I'm thinking of the sdcard mounting reported by some users.
Is there perhaps any chance for an updated version that corrects these issues?
EDIT:
I just read through the similar thread for TWRP on the SM-T530.
From what I read there, there was similar problems with internal/external SD, but reading the latest posts there I got the understanding that the issues was solved and everything work as it should.
Now, I do have a "stupid" question. I have use CWM before on my phone, so I know basicly how it works. Does this TWRP do exactly the same thing as CWM, but using touch screen interface instead of the buttons?
regards
amyren said:
Now, I do have a "stupid" question. I have use CWM before on my phone, so I know basicly how it works. Does this TWRP do exactly the same thing as CWM, but using touch screen interface instead of the buttons?
regards
Click to expand...
Click to collapse
Yes. I was used to CWM and a little hesitant switching to TWRP, but it has all the same functionality, but with touch interface (as well as buttons) instead of just buttons. If anything, TWRP is more powerful, more functional, and more customizable. Plus these days there's just way more development support for TWRP. So yes, TWRP replaces all the functionality of CWM, just better lol.
TLDR: Yes
Edit: Make sure to look here, don't use any of the outdated builds
My bad
I think i did something wrong !
- just got my tab SM t530 & tried to have a working recovery to be able to install custom rom
- first i tried TWRP but could not manage to go to recovery, instead it would simply boot to android stock
- so i tought ok let's try to have Clockworkmod working : flashed the recovery.tar from this thread using Odin
the result is a very weird boot loop, where i see tons of weird graphical glitchs instead of the normal boot/recovery
on the top left of the screen i can read :
recovery booting (blue)
recovery is not SEAandroid Enforcing (red)
set warranty bit recovery (yellow)
after that i see the very fast graphic glitchs on the screen, then screen goes black with a white line or no pixel at all
and it stay stuck like this 1 min, then screen goes back to black.
This is a video showing what is happening : https://www.youtube.com/watch?v=90cknbPQjFE
and the only thing i can do is to reboot, but no matter what i do (button combination, it always go back to recovery)
I can't go back to download mode, so i can't restock my tablet or restore i backup.
any advice for me on how to proceed and get back from this mistake ?
b,
reflash a current working recovery via odin with the auto restart option unchecked
when the flash is done [res-ok]
disconnect tab and manually reboot to recovery - vol+ home power
m
moonbutt74 said:
b,
reflash a current working recovery via odin with the auto restart option unchecked
when the flash is done [res-ok]
disconnect tab and manually reboot to recovery - vol+ home power
m
Click to expand...
Click to collapse
How do i reflash anything without access to download mode ?
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Video of my problem above : https://www.youtube.com/watch?v=90cknbPQjFE
it seems this tab is on it's way to the dustbin, i flashed many devices, since a few years, never saw a brick like this.. :/
buzzworkers said:
How do i reflash anything without access to download mode ?
Click to expand...
Click to collapse
are you on hangouts ?
i had this same issue after flashing a twrp recovery build, the issue actually occured when i flashed back to philz.
before you do anything else,
1 search xda for instructions to get adb installed for your operating system,
2 accept that we will be flashing my philz build, so we can be on the same sheet of music, you can switch to whatever
afterwards
3 do better research on CURRENT WORKING recoveries
if you have adb installed already, plug your tab in and turn it on,
when you get your OS's signal that it's picked up the device run the following immediately
adb reboot-bootloader
which should with luck get you into odin mode
m
Thanks so much !
moonbutt74 said:
are you on hangouts ?
Click to expand...
Click to collapse
YES ! pm me ?
moonbutt74 said:
1 search xda for instructions to get adb installed for your operating system,
Click to expand...
Click to collapse
I have ADB already setup, but right now under the current boot mode i'm able to use, i get : error device not found
when i try to adb my device or just to get it's status..
moonbutt74 said:
2 accept that we will be flashing my philz build, so we can be on the same sheet of music, you can switch to whatever
afterwards
Click to expand...
Click to collapse
no worry, I know Philz recovery and used it a lot on other devices i owned.
moonbutt74 said:
3 do better research on CURRENT WORKING recoveries
Click to expand...
Click to collapse
I swear i will !!
b,
you have pm blocked , well screw it
start by holding down only power,
let it cycle once or twice
keep the tab connected to pc the entire time, you running a linux os by any chance ?
windows has mental problems
if linux picks it up have a terminal open and ready, prestart adb server
adb start-server
then have the following command ready
adb logcat
@buzzworkers
if that doesn't grab it , next we try a boot into safe mode, vol+ vol- power
when boot screen comes up release power but keep vol buttons held down.
moonbutt74 said:
b,
you have pm blocked , well screw it
start by holding down only power,
let it cycle once or twice
keep the tab connected to pc the entire time, you running a linux os by any chance ?
windows has mental problems
if linux picks it up have a terminal open and ready, prestart adb server
adb start-server
then have the following command ready
adb logcat
Click to expand...
Click to collapse
-
just sent you a link with my hangout link..would that work ?
i can switch back to arch linux but not sure i have the android suite installed there..
but if we are sure to have better results i can prepare the OS to have everything android
and then i come back here when i'm ready ?
No, unblock pm's.
you're goal is to get the tab back into odin mode OR get access via adb
moonbutt74 said:
No, unblock pm's.
you're goal is to get the tab back into odin mode OR get access via adb
Click to expand...
Click to collapse
OK i think I have my settings open to anyone to PM me now..
about ADB i'm now on my arch linux with the whole android sdk, platform-tools setup.
when i do adb get-state i have :
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
recovery
is that better ?
---------- Post added at 09:23 PM ---------- Previous post was at 09:21 PM ----------
when i do adb reboot-bootloader
it works, it actuall reboot my tab, but i'm back to the usual : recovery
and ends up with those weird graphic glitches..then goes black..
Totally new guide! Simple step by step toutorial
It took us a while to get root on our devices. Hopefully we did it! Now we can enjoy benefits of having rooted device (like Xposed Modules etc). We have working TWRP recovery which allows us to backup your phone, flash SuperSU binaries, mods and custom ROMs (actually we are working on it). First: read whole post, then download necessary files and read it again. This guide will allow you to root your BLU Pure XL/Allview X2 Soul Xtreme/Gionee Elife E8/Condor Allure A100 and other clones I don't know.
If you don't know what is 'root' & TWRP nor understand the whole idea of rooting your phone this post (or even most of the XDA community) is not for you! Read everything carefully.
POSTING BUG REPORT/PROBLEM/ISSUE!
jaiwalla said:
HELP!!!
Where am I going wrong?!?!
Click to expand...
Click to collapse
I don't know where are you wrong...!
Maybe you say something else? Maybe give me some logcat?
I would help you if I knew the problem. As for now for me you don't have any problem. Your post is useless in this form.
You have to learn how to tell the error/problem/bug before you post anything on any forum.
If you want me to help you solving this situation send me private message or edit your post and tell the problem in the right form*, please.
Cheers,
bemolx
*Right form looks like:
What's the problem?
Did you check whole thread before posting?
If possible give me logcat/shown error
Make sure you read main post carefully
What you will need to get it working:
ADB and Fastboot drivers
SuperSU flashable zip archive
TWRP Recovery image
PC & your phone
BUT!
Code:
Your warranty is now void.
Everything you're doing with your devices is on your own!
We're not responsible for any damage on your phone!
If you don't understand what's root it's good time to STOP!
Now we're starting!
Look carefully on files you need (I've mentioned them above) and scroll down for download links. Download every file we need.
Note:
At the bottom of this post you'll find two versions of TWRP: 3.1.0-x and 2.8.6.0. Let me explain the difference:
TWRP v3.1.0-x: this version has been compiled from scratch & made by me. It is the newest available recovery version at the moment and without bugs. More info in the thread linked below.
TWRP v2.8.6.0: this version has been ported from Xiaomi Redmi Note 2 & made by @acheron1502. It's not the newest but working one. It has some little bugs. More info in the thread linked below.
I suggest you to download v3.1.0-x because it will get further support by me. But it is your choice now.
Setting up our workstation
I hope you have already downloaded everything we need.
On your Desktop create a new folder (for example "root").
Find package with ADB drivers, open it and extract to the "root" folder.
Now find TWRP image and place it also in our "root" folder. This image should look like this:
Code:
twrp-3.1.0-0-x2xtreme.img
or
Code:
BLU_PURE_XL_TWRP.img
Let's rename it like this (see below) to make our rooting process easier
Code:
twrp.img
Now we're setting up your phone
Open 'Settings' application. Scroll down to 'About phone'. Click about seven times on 'Build number'. You should see: "You are now developer".
Now find 'Developer options', then 'Enable USB Debugging' and simply enable it.
Connect your phone to the PC. On PC: find SuperSU.zip and copy it on your phone.
OMG!!! Flashing!!!
Okay... That's the most important step.
Turn off your phone. Press 'power' & 'vol +' together. This key combo should boot up your phone into stock recovery mode.
Scroll down using 'vol -' to 'Reboot bootloader' and confirm pressing 'power'. This will boot your phone into Fastboot mode.
On PC: open "root" folder. Open Command Prompt here (LShift + right mouse click -> 'open cmd here')
In the Command Prompt type:
Code:
fastboot flash recovery twrp.img
This command will flash TWRP recovery on you phone.
After flashing process is done reboot you phone into TWRP by pressing 'vol +' and 'power'. When you see bootlogo get your finger from the 'power' button. You will see TWRP logo. You can unplug USB cable now.
We're almost here!
Now you should see TWRP main page same like in the screenshots I've attached to this post.
We must flash SuperSU binaries to get rooted phone. To do this press 'Install' button.
You should see list of files/folders on your phone. Navigate to the SU.zip and choose it by clicking on it.
TWRP will ask you for permission to flash that zip package. To allow it to do so swipe to the right slider on the bottom of the screen. Now SuperSU is installing.
After installation process is done press 'Reboot system now' button. Your device will reboot into your system.
Done!!!
And there you go! Your device should be now rooted with TWRP recovery installed. Check if your phone is rooted correctly by installing ROOT Checker. To make rebooting process much easier and faster you can download Quick Reboot.
Xposed Modules
There's an option to install Xposed Modules as I mentioned at the top of this post. Not every module is working but you can try it and let us know what's working.
To get it working you need:
Xposed Installer Alpha App (allows you to download and manage modules)
Xposed SDK zip (the most important thing)
Original thread with those files is linked below.
Note:
It's important what version of SDK you are downloading. Our device has 64-bit ARM MediaTek chipset so it is arm64 and it's running lollipop 5.1 ROM which equals sdk22. By that meaning the SDK zip you should download looks pretty much the same like this:
Code:
xposed-v80-sdk22-arm64.zip
Installing
Place both files on your phone's storage and reboot to recovery. Press 'Install' and navigate to sdk.zip. Choose it, confirm installation - when it's done reboot into system. Now use any file browser and find XposedInstaller.apk and install it.
Now you can download any module you want. Further instructions in post linked below.
How to unroot
Most of you would like to flash stock OTA etc.
To do this you have to have stock recovery installed.
First open SuperSU app, then scroll down and look for 'Clear/unroot' option. Choose it and follow on-screen instructions.
Then download stock recovery image (downloads for Elife E8 and Allure A100 will be available when someone provide me a link). Place it the 'root' folder (or just in the same directory with fastboot drivers etc.). Rename downloaded file into recovery.img.
Method 1 - using Fastboot
Reboot phone into bootloader mode. Open terminal in the 'root' folder and type
Code:
fastboot flash recovery recovery.img
Now reboot into system by pressing power button for a while.
Method 2 - using TWRP
Copy downloaded recovery onto your phone's storage. Reboot phone into recovery mode. Press 'Install', then change from installing zips to installing imgs (bottom right button). Navigate to downloaded recovery file and choose it. Confirm installation. After that reboot into system.
You should be now unrooted and able to flash OTA.
Downloads:
ADB & Fastboot drivers: link
TWRP Recovery: TWRP v3.1.0-0 (recomended) or TWRP v2.8.6.0 (unofficial)
SuperSU binaries by @Chainfire: link
Stock recovery: Pure XL & X2 Xtreme (extract .zip before renaming/installing)
TWRP Materialised - Dark / Light / Play
Xposed Modules
Special thanks go to the awesome team!
@FuMMoD
@acheron1502
@dexterxx
@spit85
Thank you guys. Without you it wouldn't be possible!
ENJOY!
Hey @bemolx ,
Since your thread is more of a HOW TO root, would it be OK if you move this into GENERAL and field all the rooting process questions there?
I will start a new Dev Thread for TWRP and all TWRP related development issues.
You can then use that new thread for all your download links.
EDIT:
Please use this link for TWRP in your guide.
bemolx said:
My friends and me figured out how to get root on our phones. By the way @acheron1502 made TWRP recovery which allows us flash Super SU 2.46 (Stable). Also you can flash Xposed Modules as you want.
HOW TO INSTALL:
Connect phone to your PC
Make sure you have adb and fastboot drivers installed
Download TWRP from this post
Download Super SU
Copy SU.zip to your phone's storage
Reboot phone into fastboot/bootloader mode
Flash recovery using: fastboot flash "downloadedrecoveryfilename"
Reboot to TWRP by pressing and holding Vol+ & power buttons (still in fastboot mode!)
In TWRP flash SU.zip, then reboot
What doesn't work:
- no adb in recovery
- you tell us
And there you go! Your device should be now rooted with TWRP recovery installed. Check if your phone is rooted correctly by installing ROOT Checker.
BUT!
Everything you're doing with your devices is on your own! We're not responsible for any damage on your phone!
Special thanks go to the awesome team!
@FuMMoD
@acheron1502
@dexterxx
@spit85
Thank you guys. Without you it wouldn't be possible!
ENJOY!
Click to expand...
Click to collapse
Do I have to install a particular driver for my Blu Pure XL for adb to recognize the phone is connected? Please provide a link to the driver you used. Also, please provide a link to the adb / fastboot you recommend. Thank you and great work to you all!!
acheron1502 said:
Hey @bemolx ,
Since your thread is more of a HOW TO root, would it be OK if you move this into GENERAL and field all the rooting process questions there?
I will start a new Dev Thread for TWRP and all TWRP related development issues.
You can then use that new thread for all your download links.
Click to expand...
Click to collapse
Okay, no problem
mhajii210 said:
Do I have to install a particular driver for my Blu Pure XL for adb to recognize the phone is connected? Please provide a link to the driver you used. Also, please provide a link to the adb / fastboot you recommend. Thank you and great work to you all!!
Click to expand...
Click to collapse
Just take a look at Google's development page - there are drivers needed to get it working. Nothing else
bemolx said:
Okay, no problem
Click to expand...
Click to collapse
Once it's moved, see of you can get it PINNED to top so everyone can find it easily.
It states unknown partition 'BLU_PURE_XL_TWRP' "error: cannot determine image filename for 'BLU_PURE_XL_TWRP' what can I do? Thanks
fastboot flash recovery filename.img
@bemolx, fix it
error: cannot load 'BLU_PURE_XL_TWRP' please help. Thanks
---------- Post added at 01:12 PM ---------- Previous post was at 01:04 PM ----------
dexterxx said:
fastboot flash recovery filename.img
@bemolx, fix it
Click to expand...
Click to collapse
Got it thanks a mil
bemolx said:
My friends and me figured out how to get root on our phones. By the way @acheron1502 made TWRP recovery which allows us flash Super SU 2.46 (Stable). Also you can flash Xposed Modules as you want.
HOW TO INSTALL:
Connect phone to your PC
Make sure you have adb and fastboot drivers installed
Download TWRP from this post
Download Super SU
Copy SU.zip to your phone's storage
Reboot phone into fastboot/bootloader mode
Flash recovery using: fastboot flash "downloadedrecoveryfilename"
Reboot to TWRP by pressing and holding Vol+ & power buttons (still in fastboot mode!)
In TWRP flash SU.zip, then reboot
What doesn't work:
- no adb in recovery
- you tell us
And there you go! Your device should be now rooted with TWRP recovery installed. Check if your phone is rooted correctly by installing ROOT Checker.
BUT!
Everything you're doing with your devices is on your own! We're not responsible for any damage on your phone!
Special thanks go to the awesome team!
@FuMMoD
@acheron1502
@dexterxx
@spit85
Thank you guys. Without you it wouldn't be possible!
ENJOY!
Click to expand...
Click to collapse
What about the Ono U1? It's an inexpensive phone with high end specs thanks again http://forum-lw-3.xda-cdn.com/images/smilies/wink.gif
Swarai said:
What about the Ono U1? It's an inexpensive phone with high end specs thanks again http://forum-lw-3.xda-cdn.com/images/smilies/wink.gif
Click to expand...
Click to collapse
It *might* work based on specs I saw on u1labs.com ...
Can you post the values in your /proc/partinfo so I can compare with ours?
acheron1502 said:
It *might* work based on specs I saw on u1labs.com ...
Can you post the values in your /proc/partinfo so I can compare with ours?
Click to expand...
Click to collapse
The specs haven't been updated yet, but the phone should be released soon along with the kernel source.
Swarai said:
The specs haven't been updated yet, but the phone should be released soon along with the kernel source.
Click to expand...
Click to collapse
Let's keep the development thread about this phone (Blu Pure XL) and other phones with the exact same base maker/model (ie. Gionee E8, Allview x2 Extreme). If you are asking about gaining root for a different phone and need some Mind-share from this group of people due to the other phone having a similar SOC, the best way is to open a new thread in the Q&A Section or the General Section, but I think you should wait until the phone is released first IMHO.
bemolx said:
7. Flash recovery using: fastboot flash "downloadedrecoveryfilename"
Click to expand...
Click to collapse
This should be fastboot flash recovery BLU_PURE_XL_TWRP.img
Also ... I requested this thread be moved to General and be Pinned for easy finding for anyone that has this phone
Guys,
1) THANKS for GREAT work!
2) Please provide more CLEAR / ACCURATE details on how to do this, because NOOBs (including myself) get very confused.
a) Link to adb / fastboot drives. Saying "they are in Google development section means nothing"
b) How do I "Reboot phone into fastboot/bootloader mode"??
This would help so many people root without bricking the phone.
Thank you once again!
levchikb said:
Guys,
1) THANKS for GREAT work!
2) Please provide more CLEAR / ACCURATE details on how to do this, because NOOBs (including myself) get very confused.
a) Link to adb / fastboot drives. Saying "they are in Google development section means nothing"
b) How do I "Reboot phone into fastboot/bootloader mode"??
This would help so many people root without bricking the phone.
Thank you once again!
Click to expand...
Click to collapse
Thanks for reply! Once I get a little more time I'll re-write this "how to".
Cheers
Everything should be now clear. I've added links for drivers etc. Also i've re-wrote it for better understanding
Sent from Nexus 5
I'm having issues with fastboot. It says it's blocked for security. Is there something required that isn't normally on android phones to get the fastboot method to actually allow me to enter fastboot? At the beginning was just going to recov ery and putting reboot into fastboot.
alaiwy said:
I'm having issues with fastboot. It says it's blocked for security. Is there something required that isn't normally on android phones to get the fastboot method to actually allow me to enter fastboot? At the beginning was just going to recov ery and putting reboot into fastboot.
Click to expand...
Click to collapse
Try to reboot manually to recovery, then you should see option 'reboot bootloader'. After choosing it follow my instructions
any1 have stock rom to reflash full rom , pure xl ?
This is a very nice budget tablet from Tablet Express. I found mine on eBay for $93.00, new + free shipping, and have been very pleased with it. I love that it came with Developer Options already on, had USB Debugging enabled right out of the box, and has a screen protector installed by the manufacturer. Add the fact that the bootloader isn't even locked, and you really can't go wrong with this device.
I used the AIO TWRP Compiler script by @yuweng, to build this recovery, it's a very efficient tool to work with and he put a lot of work into it. Many, many thanks there!!
Well, enough rambling, lets get started...
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
Verify Partition Scheme
Over the past few months, it seems some devices have different names for the partition scheme, either "nand" or "mmcblk". So, the first step will be to check which type you have before installing TWRP and rooting the device. Here's how you check:
1) Connect the device to your PC, and open a terminal
2) Type the following:
Code:
# to make sure the device is recognized:
adb devices
# result should be:
List of devices attached
00000000000000000000 device
# Now type:
adb shell
# followed by:
ls -al /dev/block/by-name
# First Line should be 1 of the 2:
# This is a "mmcblk" device
lrwxrwxrwx root root 2016-07-20 00:08 UDISK -> /dev/block/mmcblk0p1
# This is a "nand" device
lrwxrwxrwx root root 2016-07-20 00:36 UDISK -> /dev/block/nandk
Once you know which device type you have, follow the below directions accordingly.
Root (Works for Android 4.4.4 and 5.1.1)
Rooting the device is easy, there are two methods that I know work:
1) Install TWRP, then flash Chainfires current SuperSu zip, find it Here (<-- recommend method)
2) Using Kingo Root for PC, find it Here (Use the Root Again option)
Install TWRP
You should already have ADB installed on your PC, or BusyBox and Terminal Emulator installed on your tablet, I will not cover installation of either of those. And you should know which type of mount partitions your device is using. To get the TWRP recovery on your device, you have a few options:
1) Use ADB to "push" the image (Android 4.4.4 and 5.1.1)
2) Use the included shell script, via BusyBox and Terminal Emulator (Android 5.1.1 and the device must already be rooted to use this option)
Download the appropriate zip for your device, located below, under Downloads, and extract it to a convenient location on your PC. If using your Tablet, the shell scripts and TWRP image must be in the root directory ( / ) to work properly.
Using ADB (Android 5.1.1) on "nand" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push X10_twrp3.0.2.img /dev/block/nandf
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 5.1.1) on "mmcblk" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push x10_twrp_mmc.img /dev/block/mmcblk0p9
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 4.4.4)*As of now, KK uses "nand" ONLY
This is the only way I could get it to work right on KitKat, sorry, no Terminal Emulator for this one...
Put the X10_twrp2.8.7.0.img file in the same directory as your working ADB, then enter the following, one line at a time:
Code:
adb push X10_twrp2.8.7.0.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/X10_twrp2.8.7.0.img of=/dev/block/nandf
#After it finishes:
reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That wasn't too bad, was it?
Using Terminal Emulator (Android 5.1.1 using "nand" ONLY)
Put the X10_twrp3.0.2.img and twrp.sh files in the root ( / ) folder of your tablet, then open the Terminal Emulator, enter the following, one line at a time:
Code:
su
sh twrp.sh
The script will tell you when it's done, now, power off the tablet. Boot into recovery by pressing and holding the Volume Down and Power Buttons. When the Dragon Touch logo appears, release the Power Button but continue to hold Volume Down until TWRP boots.
I hope you enjoy my work, and keep in mind that I like to keep things up to date, when a new version of TWRP comes out, I'll build it and post it here.
Downloads
X10 TWRP for "nand" devices
X10 TWRP for "mmcblk" devices
~ Also see Extras Section Below ~
Credits
@yuweng (bunch of help there)
@MSF Jarvis
@trillwizzard (for mmc fix)
@amw2320 (for modified firmware)
TeamWin
Extras
Themes for TWRP
TWRP 3.x Themes for Tablets (Landscape Devices)
Factory Firmware
TabletExpress.com
Modified Firmware
X10-V2-5.1-amw-TWRP_SuperSU.img (Created by: @amw2320, has TWRP (nand) and SuperSu already installed)
Using PhoenixUSBPro
My "short" guide on using the PhoenixUSBPro tool can be found here
X10 Device Tree (For Android 5.1.1)
GitHub
Change Log
Change Log (Newest First)
Added modified stock firmware (8-20-16)
Added info about devices using "mmcblk" instead of "nand", provided TWRP for each (7-23-16)
Added TWRP 2.8.7.0 for KitKat (Android 4.4.4) users and flash instructions (5-19-16)
@NepoRood, great work! One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
I am sure the flag has dir rather than folder in its name, but you can easily confirm that from the thread and you have to use an absolute path for folder name, so include the device/vendor/codename also, before rootdir.
MSF Jarvis said:
One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
Click to expand...
Click to collapse
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
That's what I'm here for, no?
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Franzferdinan51 said:
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
NepoRood said:
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
Click to expand...
Click to collapse
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
MSF Jarvis said:
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
Click to expand...
Click to collapse
Thank you for the offer my friend!
I've only tried to build for one device, well 2 actually, both RCA (MT8127), both failed miserably. Even though I got a "successful" build (ie: no errors/make completed) CM12.1 wouldn't boot. Come to find out, the zip and system.img had limited files, I can't remember which, but not enough for a complete rom
So, I decided to learn everything I could about building TWRP (thanks for your help with that too )
I'll pull all the vendor blobs from the X10 and try to put together the device tree for rom building and get back to you.
Thanks Again,
Nepo
marshmallow
you think this tablet is able to be upgraded to marshmallow?
i found a rom for 6.0.1 that has the same processor A83T
it has the same processor so do you think it would flash?
Thanks!
the firmware is
A83T_N106_N1061L6BC_20160309
NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
The flag is actually this
Code:
RECOVERY_RAMDISK_DIRS += device/<vendor>/<codename>/ramdisk
As seen in this reverted commit
stickz42o said:
the firmware is
A83T_N106_N1061L6BC_20160309
Click to expand...
Click to collapse
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it here
PS, you can also use Phoenix Card to boot from External SD just to test
Ahhh Please Help?
@NepoRood
All images from TabletExpress Dragon Touch X10 10'' Android 5.1.
X10-HT-PW-V1-AL-5.1-A83T_N106_N1061L2BC_20151126
X10-HT-PW-V1-AL-4.4-20151104
X10-HT-PW-V2-AL-5.1-20150115
X10-HT-PW-V2-AL-4.4-20160116
A83T_N106_N1061L6BC_20160309-ok NOT WORKING. RED/WHITE BOOT SCREEN.
I have downloaded and flashed all these images and I cannot get TWRP to work? I have installed Via Adb and Terminal, but it will not flash the recovery.
All I get is the factory recovery. I can confirm it pushed it to device, but will not work.
Can someone else verify.
Regards
Paxster
For Users: The Best and Easy App to use is the PhoenixSuit (Just Google lol)
I'm using this one:
Paxster said:
X10-HT-PW-V2-AL-5.1-20150115
Click to expand...
Click to collapse
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
NepoRood said:
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it
PS, you can also use Phoenix Card[/URL] to boot from External SD just to test
Click to expand...
Click to collapse
I am going to try it tonight. I didn't know about the phoenixcard boot to test it. I will try that method and post my results if someone doesn't beat me to it
thanks for the info about the phoenixcard
I can't post a link till 10 posts for the firmware btw :/ i'll try to message it to you.
NepoRood said:
I'm using this one:
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes Recovery is in the same Dir as ADB. It confirms being sent in the Adb Window to my booted Tablet.
Also if I use a Terminal app, it is also confirmed as being flashed, but I still get a 3e recovery? So strange.
Its driving me nuts lol..
Q:Should it work with any V5.1 Android Firm? I am using X10-HT-PW-V2-AL-5.1-20150115 from tabletexpress.
Can you confirm what version yours is working on please.
UPDATE... 5 Hours later.. I managed to flash the TWRP on Android V4.4 using Rashr. and when in recovery the screen is corrupted, unable to use? and Twrp is in Landscape mode. Shall try this method on V5.1.
Regards
Paxster
PS: @stickz42o A83T_N106_N1061L6BC_20160309 Does not work. I posted above.. Red/White Stuck Boot.
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment PAXSTER.LOG So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Paxster said:
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment 3747215 So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Click to expand...
Click to collapse
When building, I ran into problems of only TWRP booting, turns out it was an init.rc and recovery.fstab issue. But, I had that fixed for the final release I'm using the exact same firmware as you are, and TWRP works perfectly.
Could you attach your TWRP log?
Hello, today I'll be guiding you to how to install LineageOS or other GSI ROMs on your A127F U7 device.
First, some precaution:
Rich (BB code):
/*
* knox_warranty_void: 0x01
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements:
Code:
* Unlocked bootloader
* Your device's firmware
* Android's platform tools.
* Magisk
* Odin
* U5, U6, U7 TWRP
* GSIs Image for the ROM you want to download
* physwizz's kernel
1) The first step you want to do is, unlock your bootloader. You can simply do that by enabling OEM Unlocking in Developer settings, (Can be unlocked by going to Settings > About Phone > Software Information > tapping "Build Number" 5 times then booting to download mode. (Connect to PC, shutdown your phone, then hold volume up and down buttons, then when you're on the download screen, hold volume up., then press volume up again) WARNING: THIS WILL ERASE YOUR DATA AND PERFORM A FACTORY RESET, SO BACKUP YOUR DATA WHEN NECESSARY.
2) Then, download the firmware you have for your firmware. How? Try visiting sites like samfw and find your firmware by searching A-127F and finding your country's baseband. Then download through your preferred method of downloading. Mine I login to Google, and downloaded through Google Drive, which is faster. (Though it will personally copy the firmware's file to you Google Drive and occupy space on it, so beware of that and delete the file afterwards, the file is in DRIVE > samfw_temporary_folder_dont_delete I assume it's safe to delete after download, so there's that.)
3) Extract the file, and adb push the AP_XXXXX file to your device. How? Download the Android platform tools to the above hyperlink, then extract it, go to the file and then type: e.g adb push [DIRECTORY WHERE YOU EXTRACTED YOUR FIRMWARE FILE]\AP_XXXXXX, [FILL IN THE FILE NAME] /sdcard/
4) Then boot up your device, set it up (minimally), download the magisk from below, (25.1-delta file) then install it. Then from the app, select Install Magisk > Patch from File then select the AP_XXXX file you've extracted from your firmware. Wait, for some minutes, and then see what is the file name.
5) Then pull the file and flash with Odin. (Download below) Use adb pull /sdcard/Download/magisk_patched-XXXX [See the magisk log for the file name] C:\Users\[your user]\Downloads\. Open Odin, select okay, when prompted, select AP, select the magisk_patched-XXXX file you've extracted from your phone, untick auto-reboot, then hit flash.
6) Go to stock recovery, again by pressing Volume Down +Power, then while connected to the PC, press Volume Up + Power then navigate via volume buttons and then press with power button, Wipe data/factory Reset
7) Turn off the phone (while connected to the PC) by pressing Volume Down + Power, then when turned off immediately press Volume Up + Volume Down. Go back to Odin, download the TWRP image below, and put it in AP slot and untick auto reboot. Then flash
8) Boot to recovery, by again Volume Down + Power, when turned off, Volume Up + Power, whilst connected to PC. ( See 6.) Now you've booted to TWRP Recovery. Go to Advance > Terminal then type multidisabler twice. (Very important)
9) Then download the GSI ROM you want to flash, extract it, then adb push it to your /sdcard/, just as you did with 3. (Here is a list of GSI's you can download) (Optional) Either use MTP or adb push to get into your device physwizz's kernel, and GApps (the guide will be in the second post, yet to find a way how to install it)
10) In the recovery, select Install > Install Image > select the GSI ROM's .img file you have, and select System Partition. (Optional) Then select Install Zip Then install physwizz's kernel.
11) Then, reboot, WAILA! There you have it, your own GSI ROM on your A127F U7 device. Enjoy
Credits: @physwizz, for his recovery and kernel ports. Without his hardwork, it wouldn't even be possible to install GSI for U7
How to install GApps.
Method 1 (tested and worked):
Download the A/B Google Apps VNDK Secure variant of Lineage. (In AndyYan's sourceforge page it would be bgS-vndk-secure):
extract the file as usual, and then rename the file as system.img.
Download the attachment below.
adb push both files to your /sdcard/ or any folder you prefer within /sdcard. (Though the files must be in the same directory) i.e. adb push system.img ChonDoe_Flasher.zip /sdcard
Go to TWRP > Install then select the ChonDoe_Flasher.zip,
and WAILA, you have now a working LineageOS with Gapps, it might work with other ROMs too!
Method 2, will post when I have tested it.
Credits: @chondoe for his flasher
--- Theory for flashing twice (disproven, you only need to flash once, here for archive purposes, you don't need to read it if you're not interested):
Go to TWRP > Install then select the ChonDoe_Flasher.zip, TWICE. Do not reboot only doing it once, or else it might bootloop. After flashing once, go back and then do it again. (If you accidentally did it once, tell me if it worked and I'll post the results)
(EXPLAINED: This is a theory of mine, though, I didn't test doing it only once, I'll try to do it once if I ever go back to stock ROM and see if it only requires once, but as of now I tried doing it twice and it worked [the logic behind this is, if you install the .img alone, it will boot-loop due to lack of storage, but the flasher uses e2fsck and resize2fs so along the process, it expands the file system and thereby allowing more space for installation. I theorize doing this once will not work because the script first installs/flash the .img before using e2fsck and resize2fs and therefore still lacks the file system space that it needs to boot, but if you do it twice, you will have already executed the two binaries and thereby allow space for a proper installation of the .img, so it will now boot and not get stuck on an infinite bootloop.])
My phone keeps bootlooping, i followed the tutorial strp by step, can you help me?
MaybeFazat said:
My phone keeps bootlooping, i followed the tutorial strp by step, can you help me?
Click to expand...
Click to collapse
Can you remember what firmware you had? Are you sure it's the right one for your device? Also, this is for A127F U7, make sure your device is compatible. Consequently, what GSI ROM have you flashed? This method only worked with LineageOS 19.1. bvS (by AndyYan). If the bootloop doesn't show the lineage logo, it may be that the GSI file is too big for the system partition, I have yet to found a way to expand our device's /system partition. Try AOSP 12.1 first, or download LineageOS 19.1 bvS from AndyYan's page, and see if it works.
Here https://sourceforge.net/projects/an...20221011-UNOFFICIAL-arm64_bvS.img.xz/download
juliano-oh! said:
Can you remember what firmware you had? Are you sure it's the right one for your device? Also, this is for A127F U7, make sure your device is compatible. Consequently, what GSI ROM have you flashed? This method only worked with LineageOS 19.1. bvS (by AndyYan). If the bootloop doesn't show the lineage logo, it may be that the GSI file is too big for the system partition, I have yet to found a way to expand our device's /system partition. Try AOSP 12.1 first, or download LineageOS 19.1 bvS from AndyYan's page, and see if it works.
Click to expand...
Click to collapse
Alright thanks for the info
Good work
juliano-oh! said:
Can you remember what firmware you had? Are you sure it's the right one for your device? Also, this is for A127F U7, make sure your device is compatible. Consequently, what GSI ROM have you flashed? This method only worked with LineageOS 19.1. bvS (by AndyYan). If the bootloop doesn't show the lineage logo, it may be that the GSI file is too big for the system partition, I have yet to found a way to expand our device's /system partition. Try AOSP 12.1 first, or download LineageOS 19.1 bvS from AndyYan's page, and see if it works.
Click to expand...
Click to collapse
And also, what gapps i need to use?
MaybeFazat said:
And also, what gapps i need to use?
Click to expand...
Click to collapse
That's what I'm currently struggling with, I can't find a GApps that work with any GSI since the /system partition is too small to even install GApps. There are critical and hard to follow tutorials out there that helps with increasing the /system parition but I have yet to try them since it, as I am informed, can hard brick your device. So I'm very cautious about that. @physwizz just recommends installing a ROM with GApps already installed in it (such as Pixel Experience) but I have yet to try that either.
MaybeFazat said:
And also, what gapps i need to use?
Click to expand...
Click to collapse
I accidentally duplicated my reply, sorry
juliano-oh! said:
That's what I'm currently struggling with, I can't find a GApps that work with any GSI since the /system partition is too small to even install GApps. There are critical and hard to follow tutorials out there that helps with increasing the /system parition but I have yet to try them since it, as I am informed, can hard brick your device. So I'm very cautious about that. @physwizz just recommends installing a ROM with GApps already installed in it (such as Pixel Experience) but I have yet to try that either.
Click to expand...
Click to collapse
Can you try magisk gapps?
juliano-oh! said:
Hello, today I'll be guiding you to how to install LineageOS or other GSI ROMs on your A127F U7 device.
First, some precaution:
Rich (BB code):
/*
* knox_warranty_void: 0x01
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements:
Code:
* Unlocked bootloader
* Your device's firmware
* Android's platform tools.
* Magisk
* Odin
* U5, U6, U7 TWRP
* GSIs Image for the ROM you want to download
* physwizz's kernel
1) The first step you want to do is, unlock your bootloader. You can simply do that by enabling
Code:
OEM Unlocking
in Developer settings, (Can be unlocked by going to
Code:
Settings > About Phone > Software Information > tapping "Build Number" 5 times[\CODE] then booting to download mode. (Connect to PC, shutdown your phone, then hold volume up and down buttons, then when you're on the download screen, hold volume up., then press volume up again) WARNING: THIS WILL ERASE YOUR DATA AND PERFORM A FACTORY RESET, SO BACKUP YOUR DATA WHEN NECESSARY.
2) Then, download the firmware you have for your firmware. How? Try visiting sites like samfw and find your firmware by searching [CODE]A-127F
and finding your country's baseband. Then download through your preferred method of downloading. Mine I login to Google, and downloaded through Google Drive, which is faster. (Though it will personally copy the firmware's file to you Google Drive and occupy space on it, so beware of that and delete the file afterwards, the file is in
Code:
DRIVE > samfw_temporary_folder_dont_delete
I assume it's safe to delete after download, so there's that.)
3) Extract the file, and
Code:
adb push
the
Code:
AP_XXXXX
file to your device. How? Download the Android platform tools to the above hyperlink, then extract it, go to the file and then type: e.g
Code:
adb push [DIRECTORY WHERE YOU EXTRACTED YOUR FIRMWARE FILE]\AP_XXXXXX, [FILL IN THE FILE NAME] /sdcard/
4) Then boot up your device, set it up (minimally), download the magisk from below, (25.1-delta file) then install it. Then from the app, select
Code:
Install Magisk > Patch from File
then select the AP_XXXX file you've extracted from your firmware. Wait, for some minutes, and then see what is the file name.
5) Then pull the file and flash with Odin. (Download below) Use
Code:
adb pull /sdcard/Download/magisk_patched-XXXX [See the magisk log for the file name] C:\Users\[your user]\Downloads\
. Open Odin, select okay, when prompted, select AP, select the magisk_patched-XXXX file you've extracted from your phone, untick auto-reboot, then hit flash.
6) Go to stock recovery, again by pressing Volume Down +Power, then while connected to the PC, press Volume Up + Power then navigate via volume buttons and then press with power button,
Code:
Wipe data/factory Reset
7) Turn off the phone (while connected to the PC) by pressing Volume Down + Power, then when turned off immediately press Volume Up + Volume Down. Go back to Odin, download the TWRP image below, and put it in AP slot and untick auto reboot. Then flash
8) Boot to recovery, by again Volume Down + Power, when turned off, Volume Up + Power, whilst connected to PC. ( See 6.) Now you've booted to TWRP Recovery. Go to
Code:
Advance > Terminal
then type
Code:
multidisabler
twice. (Very important)
9) Then download the GSI ROM you want to flash. Here is a list, then
Code:
adb push
then to your /sdcard/, just as you did with 3. (Optional) Either use MTP or
Code:
adb push
to get into your device physwizz's kernel, and GApps (the guide will be in the second post, yet to find a way how to install it)
10) In the recovery, select
Code:
Install > Install Image > select the GSI ROM's .img file you have, and select System Partition.
(Optional) Then select
Code:
Install Zip
Then install physwizz's kernel.
11) Then, reboot, WAILA! There you have it, your own GSI ROM on your A127F U7 device. Enjoy
Credits: @physwizz, for his recovery and kernel ports. Without his hardwork, it wouldn't even be possible to install GSI for U7
Click to expand...
Click to collapse
How it performs? Does it run smoother than OneUI? & Do you have screenshots?
MaybeFazat said:
Can you try magisk gapps?
Click to expand...
Click to collapse
I haven't tried it yet.
MaybeFazat said:
How it performs? Does it run smoother than OneUI? & Do you have screenshots?
Click to expand...
Click to collapse
It performs well, I haven't done any benchmark to see if it performs better than OneUI, but they are pretty different. Although, it performs pretty well in my opinion, and it boots very quickly (as in, the animation only has to run once and it boots already). Unfortunately, I don't have any screenshots, as I reverted back to stock since I need my Google account and Play Store, but you can try and search for "Lineage OS 19. X Screenshots" on Google and I doubt it will give you any different results.
juliano-oh! said:
I haven't tried it yet.
It performs well, I haven't done any benchmark to see if it performs better than OneUI, but they are pretty different. Although, it performs pretty well in my opinion, and it boots very quickly (as in, the animation only has to run once and it boots already). Unfortunately, I don't have any screenshots, as I reverted back to stock since I need my Google account and Play Store, but you can try and search for "Lineage OS 19. X Screenshots" on Google and I doubt it will give you any different results.
Click to expand...
Click to collapse
So i tried for the second time, with Lineage BgS (not BvS since i need gapps) but its bootlooping again, can you help me?
I can't, I tried that too but I haven't found a way to workaround this, sorry to disappoint. I'm guessing that the image is too big for the system that it won't boot. I only find the BvS to be working, and have not yet tried others, except for BgS, which gave me a bootloop too...
it will work for A127F/DSN?
smj320fn-galaxy said:
it will work for A127F/DSN?
Click to expand...
Click to collapse
Yes, but only for LineageOS vanilla, there's yet to find a way to install GApps. If you can live without GApps you can install this then. https://sourceforge.net/projects/an...20221011-UNOFFICIAL-arm64_bvS.img.xz/download
and if i have one ui 4.1 and u7 brinary i still can install it, and in the downloads it says twrp-a127f-u5 brinary?
smj320fn-galaxy said:
and if i have one ui 4.1 and u7 brinary i still can install it, and in the downloads it says twrp-a127f-u5 brinary?
Click to expand...
Click to collapse
yes, the U5 binary TWRP is compatible with U6 and U7
@MaybeFazat I updated the second post. You may now enjoy LineageOS with Gapps. Please tell me what has happened after you install. Feedback will be appreciated.