Related
hi everyone
i have a tf700 at stock rom from asus
i rooted with kingo and unlocked with unlock tool version v7
then i tried to install twrp with fastboot
but i could not get the tablet to be seen by the computer
i did everything by the book, installed the asus drivers used a usb 2.0 port, but no use
so i installed twrp with twrp manager
but it said it failed
BUT when i rebooted into recovery it loaded twrp !!!
but i can not get to twrp by use of fastboot
cannot get the tablet in fastboot
HELP plaese
thanks
More info please.
Can you get to the bootloader screen?
What happens if you select RCK?
berndblb said:
More info please.
Can you get to the bootloader screen?
What happens if you select RCK?
Click to expand...
Click to collapse
hi,
first of all thanks for trying to help
much appreciated
well, using the buttons on the device i can't get to the bootloader screen
it just boots into the stock ROM
BUT i tried it from the the rom with bootmanager (software app from the playstore) and i can get to the bootloader screen
i see the standard three icons
RCK
android
wipe data
if i select RCK it boots TWRP
if i select android it boots the ROM
but i cannot get to this using the physical buttons on the device
volume down and power
Mhhh, can think of 2 reasons:
You're not holding the Volume button long enough.
The button is worn out. Does it work to turn down volume?
Hi all,
I thought it be good to warn all Alcatel Pixi 4 (4) owners. The current version of the stock rom of the 4034N, which is sold here in the NL has what I think is a terrible bug.
If you enable unlocking in the development options, go to the fastboot, all it takes is to unlock the flash and your phone will get stuck in the boot animation.
I tried to recover by formatting /data (/data is destroyed as could be expected to protect the userdata), but it does not solve the problem.
Flashing a custom ROM like CM13 solves this problem, but I bet this is the reason why I see so many calls on the Internet for Stock ROMs for the 4034N. Have not found a good stock ROM for it and also Alcatels Mobile Upgrade site does not seems to support the 4034N (probably still one software version for it, so no upgrade required yet?).
So better know what you are doing when messing with this phone.
Anybody got the same experience (I can confirm that this was tested by me and my friends with three different Pixi 4's)...
Best regards,
Peter
Good news!
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
I think I'm seeing the same problem with a 4034X (UK variant, as sold by Tesco Mobile). Unfortunately, the mobile update software isn't working for me as it's detecting that I've already got the latest version of the ROM installed already and won't let me install it again. AIUI, the CM13 system has a few issues, so I'd rather not go that root, so would still like a stock ROM if at all possible. Anyone have any pointers?
Hmm. Have managed to get beyond the resetting user data boot loop with the following procedure:
* boot to recovery (power + vol up)
* from recovery menu, choose "boot to bootloader"
* at bootloader, connect via USB to PC
* run "fastboot -w"
* run "fastboot boot <filename for twrp recovery image>"
* at twrp recovery menu, run the standard "wipe" options
* reboot
Haven't yet finished booting, but it's gone to the standard boot animation, which I never succeeded in getting to before.
Update: 8 minutes and counting into the boot process. Doesn't look like it's going to work.
One question worth asking: does this mean that *all* operations that cause a factory reset on an affected 4034 cause a boot loop? Or is it only unlocking the boot loader?
I managed to soft brick my 4034X simply by allowing my email program to encrypt the device. The encryption apparently failed and now it's stuck on boot animation. As @jh3141 said, the Acatel upgrade tool doesn't work. I guess I need to find a stock ROM, but my Googling hasn't found one yet. Can anyone help?
palbeda said:
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
Click to expand...
Click to collapse
Same here with a 4034D - got my phone back alive and still a unlocked bootloader. rooted it, works great.
Thanks!! :good:
i need help
Tampopo said:
Same here with a 4034D - got my phone back alive and still a unlocked bootloader. rooted it, works great.
Thanks!! :good:
Click to expand...
Click to collapse
Can you brake this down for me? am kind of new to all this but i really need to root my device
jh3141 said:
Hmm. Have managed to get beyond the resetting user data boot loop with the following procedure:
* boot to recovery (power + vol up)
* from recovery menu, choose "boot to bootloader"
* at bootloader, connect via USB to PC
* run "fastboot -w"
* run "fastboot boot <filename for twrp recovery image>"
* at twrp recovery menu, run the standard "wipe" options
* reboot
Haven't yet finished booting, but it's gone to the standard boot animation, which I never succeeded in getting to before.
Update: 8 minutes and counting into the boot process. Doesn't look like it's going to work.
Click to expand...
Click to collapse
Any luck with the UK version 4034X?
I'm stuck in the booting process just like you were.
me too - Pixi 4(4) chaos on unlocking.
Absolutely the same experience here.
I have nuked 2 of these trying to unlock. It is a brilliant phone, but this is a painful feature - as you describe.
My history is in one of the threads on this site. - I agree, I would love a stock ROM for it.
palbeda said:
Hi all,
I thought it be good to warn all Alcatel Pixi 4 (4) owners. The current version of the stock rom of the 4034N, which is sold here in the NL has what I think is a terrible bug.
If you enable unlocking in the development options, go to the fastboot, all it takes is to unlock the flash and your phone will get stuck in the boot animation.
I tried to recover by formatting /data (/data is destroyed as could be expected to protect the userdata), but it does not solve the problem.
Flashing a custom ROM like CM13 solves this problem, but I bet this is the reason why I see so many calls on the Internet for Stock ROMs for the 4034N. Have not found a good stock ROM for it and also Alcatels Mobile Upgrade site does not seems to support the 4034N (probably still one software version for it, so no upgrade required yet?).
So better know what you are doing when messing with this phone.
Anybody got the same experience (I can confirm that this was tested by me and my friends with three different Pixi 4's)...
Best regards,
Peter
Click to expand...
Click to collapse
I also softbricked my 4034X after unlocking the bootloader and couldn't get the phone to boot into recovery or the bootloader. I eventually managed to flash a stock ROM with SP Flashtool as described here https://www.getdroidtips.com/install-official-stock-rom-on-alcatel-pixi-4-4/ - this restored the ability to boot into recovery or bootloader but the ROM wouldn't boot so I couldn't enable developer settings to allow OEM unlocking. I then tried flashing the ROM for the dual-SIM version of the 4034X (risky!) and this booted and I was able to unlock the bootloader and flash TWRP recovery. The next problem was when & flashed CM13 and got an error message saying that TWRP couldn't access /data. It then got stuck in a recovery bootloop. Next I used TWRP to format all the partitions but it still couldn't access /data and broke the ability of the Mobile Upgrade Tool to read the phone. My next step is to try flashing a different custom recovery but I'm rapidly losing the will to live and would be very interested in any suggestions.
UPDATE - got it sorted by re-flashing the dual-SIM 4034X ROM (even though I have the single SIM version!), flashing ctr-6.6-4034 recovery, doing a normal wipe then formatting the /data partition then flashed CM13. I guess the data partition must have got corrupted.
I have exactly the same problem with pixi 4 4043f. I unlocked bootloader and then flashed following your instructions on that link you shared. But I see is a white screen frozen no options shown just booting voice behind.... I have flashed it several times but same results I still cant entry fastboot or recovery... Volume down + power or volume up + power dn take me anywhere just that frozen white screen with booting ring tone in the back and thats it... Kindly guide me
i had a similar problem, but i always wanted to flash cm13, so i was fine.
There is an amazing thread here for our device.
For those of you with the 4034X, i have ported cm13 to it specifically, bu there are too many bugs, but if anyone wants it, just tell me!
also, can i just say, softbrick if you oem lock aswell :,(
i wanted to test something, but after fastboot oem lock, and then fastboot reboot, i get an android being repaired? key combo's not working, adb/fastboot not responding, can't remember how i fixed it when i oem unlocked ...
edit-
got into recovery with key combo, now it's just to fix it!
Can any of you guys with the 4034N try this method of rooting? Without unlocking the bootloader?
Masgisk Rooting
kirito9 said:
Can any of you guys with the 4034N try this method of rooting? Without unlocking the bootloader?
Masgisk Rooting
Click to expand...
Click to collapse
For reference: I tried this on a stock 4034X and it failed (couldn't persuade it to boot the custom recovery without going through the full unlock process). Fortunately, there are now copies of the stock ROM available for download (e.g. https://androidfrog.com/a3nr9) so with any luck I won't need to go back to the dodgy CM13 port that constantly runs out of memory and soft-reboots...
Update: I've installed the stock ROM I linked to above, and it seems to be working pretty well. Only issue was that the scatter file that came with it was apparently broken. Fortunately, one that I had hanging around from attempts to fix this problem last time seemed to work with it. I've attached that to this message in case anyone else needs it.
jh3141 said:
For reference: I tried this on a stock 4034X and it failed (couldn't persuade it to boot the custom recovery without going through the full unlock process). Fortunately, there are now copies of the stock ROM available for download (e.g. https://androidfrog.com/a3nr9) so with any luck I won't need to go back to the dodgy CM13 port that constantly runs out of memory and soft-reboots...
Click to expand...
Click to collapse
Thanks, I'll be sure to add a notice for 4034X users in the Magisk guide. I have yet to see a stable CM13 ROM for MT6580 with 3.18.19 kernel. There seems to be an issue with this device chip and ROMs.
Finally got root on the Pixi4-4034
Hi everyone,
yeah I finally managed to root the alcatel Pixi 4-4 (4034) (3G MODEL). It was really tricky and there are quite some issues you have to deal with.
Therefore please read carefully my instructions and remember I am not responsible for any inconvenience, do it at your own risk.
First of all you have to unlock the bootloader and here comes the first problem. On the Pixi4 this operation leads to a sotfbick because the unlocking process deletes completely the data-partition. The phone can't boot anymore and ends in a bootloop.
To resolve this problem you must reflash the phone with SP-Flash-Tool. After reflashing the bootloader remains unlocked so that you should be able to continue with the rooting process. The second problem is that I could find only one working ROM for flashing. It is for the 4034X, my phone was a 4034D (dual SIM), after flashing I had an 4034X what means that my Pixi became a single-SIM phone, I can live with that.
Here are the necessary steps to obtain root on the Pixi4
1. UNLOCKING BOOTLOADER
- Go to settings -> about phone -> hit many times on "build number" till developer message appears
- Enable "OEM unlocking" located in developer options.
- Switch also "USB debugging" on
- Open the command prompt window (cmd)
- Connect the phone to the PC
- Boot into fastboot-mode by typing "adb reboot bootloader"
- Confirm the debug authorization window on the phone, check "always allow from this computer" (afterwards phone should boot into fastboot, otherwise retype the command above)
- Unlock bootloader by typing "fastboot oem unlock"
WARNING: this deletes the data-partition leading in a softbrick and bootloop,
you have to reflash the phone afterwards to continue rooting!
- Confirm the unlocking with the volume-up key
2. REFLASHING THE PHONE
- I found only this working firmware for the 4034X on this page like described by jh3141:
https://forum.xda-developers.com/android/general/warning-current-pixi-4-4-4034n-t3463154/page2
- You have also to use the scatter file described by jh3141
- After loading the scatter-file in SP-Flash-Tool you have to link the missing img-files in the SP-Flash-Tool-Window
- If you flash the 4034X firmware over an 4034D you will end in a single-SIM phone instead of a dual-SIM.
- After flashing the phone will boot again so that you can continue with flashing the twrp-img.
3. ROOTING THE PHONE
- To root the phone you have to install the twrp-image, the one for the Pixi 4034 you find it here:
https://forum.xda-developers.com/showpost.php?p=68049551&postcount=97
- Download and untar the file at the bottom of the page: twrp-3.1.0-0-4034.tar
- Open the command prompt window (cmd)
- Connect the phone to the PC
- Boot into fastboot-mode by typing "adb reboot bootloader"
- Flash twrp by typing "fastboot flash recovery twrp-3.1.0-0-4034.img"
- Download Super-SU "SR1-SuperSU-v2.78-SR1-20160915123031.zip" from
https://download.chainfire.eu/1003/SuperSU/
and put the zip-file on the phone (external or internal storage)
- With the phone switched off boot into twrp by holding power and volume-up keys togehter
- In twrp go to "Advanced" -> "Terminal" -> Type the following code:
echo "SYSTEMLESS=true" > /data/.supersu
- Go back and choose "Install" -> flash the Super-Su-file (SR1-SuperSU-v2.78-SR1-20160915123031.zip)
- Reboot and you’re done, you have root and super-su on the PIXI4
- If you want to uninstall system-apps proceed to the next step.
4. UNINSTALLING BLOADWARE APPS
- You can’t uninstall system-apps directly from the Android-OS,
if you delete the apps with some uninstall-tools it’s strange but the phone will reinstall them after a reboot.
- To succeed you must uninstall the apps in twrp
- Be careful, uninstalling the wrong apps will end in a bootloop or bootfreeze and you will have to reflash the phone starting at step 2.
- Boot into twrp -> go to "Mount" -> check "System" -> go back and choose "Advanced" -> "File Manager"
- In file-manager navigate to the appropriate app-folders and delete the .apk-files
- IMPORTANT: before rebooting you have to wipe the dalvik-cache
- Go to "Wipe" -> "Advanced Wipe" -> CHECK ONLY "Dalvik / ART Cache"
- Confirm wipe and reboot
I personally like the Pixi4-4034, it’s a very small one that is very useful as second phone especially on holidays .
Have fun.
i bricked my alcatel
i have an alcatel pixi 4 (4) 4034x and when i unlocked the bootloader it softbricked my alcatel, the only solution i did was relflash it using spflashtools
same problem
palbeda said:
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
Click to expand...
Click to collapse
I have exactly the same problem. But I haven't been able to find this Mobile_Upgrade_S_4.5.9. Any help will be greatly appreciated,
thnx,
Herman
update: i found the mobile upgrade tool. But it says the latest firmware is already installed. Earlier i tried spft, flashing seemed to go well but the phone stays in animation/bootloop.
Can anybody help?
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
@Asansi
I'm sorry I can't help you, but may I ask how you rooted the phone? I can't get mine to be properly rooted.
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
HackerAce said:
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
Click to expand...
Click to collapse
Apologies for ressurecring a zombie thread but, OP has a spark X and you have a Spark, so it would appear that you SENIOR person in that model failed at the very first hurdle.
Am still wonderng if there is an sign of a 7.0 compatible twrp for spark X? Don't suppose anyone has a link to the latest Spark X firmware either?
TWRP versions
Asansi said:
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
Click to expand...
Click to collapse
I've tried TWRP 3.0.2-0 (i.e. latest from https://dl.twrp.me/porridgek3/): it flashes Ok but it won't boot up afterwards. I've tried 3.0.2-0 but as you say "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. Have you progressed with this issue? BTW I've emailed TWRP Support (from their web page) asking if they have a working version.
Same problem here, It's pretty annoying. My sister's getting this same phone (on Android 6) soon so I might just make a full backup with TWRP on it and somehow restore it on my phone.
Systemless Root
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Systemless Root
ScreamingSteve said:
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Click to expand...
Click to collapse
Steve,
Have you tried the method detailed in post #7?
johnaaronrose said:
Steve,
Have you tried the method detailed in post #7?
Click to expand...
Click to collapse
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
TWRP
ScreamingSteve said:
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
Click to expand...
Click to collapse
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
johnaaronrose said:
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
Click to expand...
Click to collapse
Thanks a lot, I'll try your method, the explicit call to boot the TWRP image could really help.
Thanks for your extended explanation tho, showed me some new ways to eventually get this stuff to work.
Sent from my Wileyfox Spark X using XDA Labs
johnaaronrose said:
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Click to expand...
Click to collapse
Finally, your advice with "Fastboot boot twrp.img" worked magic!
Got twrp installed, but now I'm facing the same problem as you with the systemless root. I'll dig around a little and see what I can find.
Here is a beta working TWRP for V60.
Do NOT flash until you have a complete backup of your phone.
Flash at your own risk, you been warned
If and when you do flash it report back with bugs, what works what doesnt and what variant you used it on. helps with getting a better working recovery and fixing bugs
TWRP_LG_V60_BETA_2.0.img.7z
drive.google.com
tested on tmobile variant so far flashing and usb storage works, BUT backup system fails and does not reboot system. only reboots back to twrp, touch screen works on the first time use. If the screen times out and blacks out, you push on the power button to wake up the screen But the touch screen stops working. until the force reboot again. flashed stock abl_a and stock recovery but didnt go back to stock until you flash your stock boot.img.
blaze2051 said:
tested on tmobile variant so far flashing and usb storage works, BUT backup system fails and does not reboot system. only reboots back to twrp, touch screen works on the first time use. If the screen times out and blacks out, you push on the power button to wake up the screen But the touch screen stops working. until the force reboot again. flashed stock abl_a and stock recovery but didnt go back to stock until you flash your stock boot.img.
Click to expand...
Click to collapse
doesn't work with v60 ATT,boots in recovery ,but touch screen not working . (first attempt screen time was out ,but 2nd attempt booted in twrp while screen was on)
Karol75 said:
doesn't work with v60 ATT,boots in recovery ,but touch screen not working . (first attempt screen time was out ,but 2nd attempt booted in twrp while screen was on
Click to expand...
Click to collapse
So no touch screen functionality with att, got it thanks
i noticed that touch doesnt work if boot via commands touch only works with button combo
Could we get some info on where exactly to install this img to? Do we install to boot_a, boot_b or both?
MrHomebrew said:
Could we get some info on where exactly to install this img to? Do we install to boot_a, boot_b or both?
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
And the version listed above is certainly not current. TWRP 3.6.0-11 can be found on TG. Hopefully you know your way around Qfil.
hooutoo said:
fastboot flash recovery recovery.img
And the version listed above is certainly not current. TWRP 3.6.0-11 can be found on TG. Hopefully you know your way around Qfil.
Click to expand...
Click to collapse
(update) never mind i took care of it
you should provide a link instead if thats the case
So I wanted to make a backup using TWRP but apparently TWRP itself just didn't work.
So my main issue is that pressing almost anything doesn't give an input (Install works fine while Wipe only works when pressing but the actual UI is broken and I can't go back).
So at this point my phone is stuck in a TWRP bootloop since I cannot press the reboot option. Also, I tried flashing TWRP again and it didn't work. What should I do?
salamianchoivy said:
So I wanted to make a backup using TWRP but apparently TWRP itself just didn't work.
So my main issue is that pressing almost anything doesn't give an input (Install works fine while Wipe only works when pressing but the actual UI is broken and I can't go back).
So at this point my phone is stuck in a TWRP bootloop since I cannot press the reboot option. Also, I tried flashing TWRP again and it didn't work. What should I do?
Click to expand...
Click to collapse
When you connect via adb, then you can execute the commands described in the FAQ for TWRP and all other commands available in the shell.
Which version of TWRP are you using? The latest official one doesn't want to install for me, because it's 1MB larger than the actual recovery partition - could this have something to do with the strange behaviour?