One Click ROOT+TWRP Recovery for Lollipop Stock Firmware -----------------------------------------------------------------------
I recommend you to use AutoRec For Lollipop 20H from @[B]bender_007[/B]
@ingoljosh includes all version of autorec (D855, D852, D850, LS990 ...) in his post : Flash TWRP With AutoRec
First use OneClic Script ( by @avicohh ) to root your G3
Then install and use AutoRec to install the recovery custom
-----------------------------------------------------------------------Only for D855Only Lollipop (not KitKat)
(16GB/2GB and 32GB/3GB variants)Use only this tuto in case of failure with the previous quoted methodCredit
- @6ril1 for all his advice and convinced me to publish this method here
- @somboons and his post for the LG G2 : [TOOLS] One Click ROOT+TWRP Recovery for Lollipop Stock Firmware
Somboons have modified One Root Script ROOT KitKat / Lollipop firmware that for One Click ROOT+TWRP D802 firmware 30a/30d and I have updated his work for the LG G3 D855
- @avicohh for his One click script
- @thecubed for Bumps!
- @Unjustified Dev for send_command and his New Root Method for LG Devices
- @Chainfire for SuperSU
- G3 tuto on Frandroid
---------------------------------------------Download Link for Lollipop 20H:
Mega LGG3-D855-OneClickRootRecoveryV1.1.zip
Box LGG3-D855-OneClickRootRecoveryV1.1.zip
Dropbox LGG3-D855-OneClickRootRecoveryV1.1.zip
md5 : 33c50a727eecc9402ae1551e818b9615
---------------------------------------------
NEW
Download Link for Lollipop 20P:
Mega LGG3-D855-OneClickRootRecovery-V20P.zip
Dropbox LGG3-D855-OneClickRootRecovery-V20P.zip
md5 : a5f1776215dc6e9792e57efae400dcae
Download Link for Lollipop 20G:
Mega LGG3-D855-OneClickRootRecovery-V20G.zip
Dropbox LGG3-D855-OneClickRootRecovery-V20G.zip
md5 : 624a30b28037a6ed7023ea1f245c2aa8
@6ril1 thank to him for the bump of the 20P and 20G boot :good:
20P and 20G --> If you are not root having applied this tool, copy UPDATE-SuperSU-v2.46.zip on your SDCARD , restart on recovery mode and flash UPDATE-SuperSU-v2.46.zip
For those who used the LGG3-D855-OneClickRootRecoveryV1.1.zip version (for 20H) on the firmware:
- 20P download this file : Kernel fixed by @6ril1 (v20p) --> http://forum.xda-developers.com/showpost.php?p=60770468&postcount=1019
- 20G download this file : Kernel fixed by @6ril1 (v20G) --> http://forum.xda-developers.com/showpost.php?p=60940277&postcount=220
And use Flashify or your custom recovery to install this boot
For more informations see here : http://forum.xda-developers.com/showpost.php?p=60913483&postcount=23
Thank's @black_horse_88
---------------------------------------------
changelog:
http://forum.xda-developers.com/showpost.php?p=59926518&postcount=91
older version:
Mega LGG3-D855-OneClickRootRecovery.zip
Box LGG3-D855-OneClickRootRecovery.zip
Dropbox LGG3-D855-OneClickRootRecovery.zip
md5 : 9f0dfaa556e33457163cb7d57ebc6b1d
(recovery includes in LGG3-D855-OneClickRootRecovery.zip file: TWRP 2.8.6.1 w. Splash Screens/Modem/F2FS)
Backup Data on SDCARD Before doing everything
How to install
1 - Install LG drivers if they are not installed yet.
2 - Make sure you are enable USB Debuging Mode . (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging)
{
"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"
}
3 - Connect your phone to pc on PTP mode
4 - Extract LGG3-D855-OneClickRootRecovery.zip and double click on the OneClick_ROOT_RECOVERY.bat file, to run the script.
5 - Follow the instructions.
If the phone not recognize, try to switch between MTP and PTP options.
Watch the screen of your smarphone you could see this popup asking you to access to the G3
Of course, accept
Your G3 reboot several times.
If you see this message , reboot the G3 manually into Download mode
6 - Enjoy ROOT+TWRP on Lollipop Firmware
7 - Verify if you are root, you have custom recovery and working Download Mode
Problems and solutions
1 - @somboons describes the manual procedure on his original publication for the LgG2. If you have errors during the script you can try the manual procedure.
somboons said:
Normally If doesn't work for people please checking port that connecting between device and computer or checking LG driver and Re-run script again or use Manual method
What does the automate script do ?
(For people can't use automate script we have to use manually ROOT+TWRP)
Make sure you are enable USB Debuging Mode . See this Method > Enable Debugging Mode
1. Pushing all stuff files
Run file
Command Prompt.bat
Click to expand...
Click to collapse
It will be show command DOS windows
C:\Users\M\Desktop\LGG3-D80230a-OneClickRootRecoveryV1.1>
Click to expand...
Click to collapse
Using command as below to push files to device
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp/ && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
adb.exe push aboot.img /data/local/tmp/aboot.img
adb.exe push laf.img /data/local/tmp/laf.img
adb.exe push boot.img /data/local/tmp/boot.img
adb.exe push recovery.img /data/local/tmp/recovery.img
Click to expand...
Click to collapse
2. Reboot to Download mode
3. When enter to Download mode successfully.We need to send command to connect device with computer
Send_Command.exe \\.\COM_PATH
Click to expand...
Click to collapse
COM_PATH . we can find with ports.bat command
Ex.
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>ports.bat
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>reg query HKLM\hardware\devicemap\SERIALCOMM
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGANDNETMDM0 REG_SZ COM3
\Device\LGANDNETDIAG1 REG_SZ COM4
A command that send to device when connecting to computer with Download Mode is
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>Send_Command.exe \\.\COM4
Click to expand...
Click to collapse
4. When we see this prompt
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>Send_Command.exe \\.\COM4
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#
Click to expand...
Click to collapse
Try to use this command to ROOT+TWRP
# sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Click to expand...
Click to collapse
5. When we see this message
ui_print - Disabling OTA survival
ui_print - Removing old files
ui_print - Placing files
ui_print - Post-installation script
ui_print - Unmounting /system and /data
ui_print - Done !
Please press Ctrl+C, and then type N and ENTER to reboot.
#
Click to expand...
Click to collapse
Try to use LEAVE command to restart device.
#LEAVE
Click to expand...
Click to collapse
6. Enjoy ROOT+TWRP
Click to expand...
Click to collapse
2- If you always have errors or blockings try this other manual method
1 - Apply this tuto : [GUIDE] New Root Method for LG Devices
2 - Then this one : http://forum.xda-developers.com/showpost.php?p=59931455&postcount=104
3 - If your G3 don't boot on system but you can go on Recovery and Download Mode
Your boot is not correctly flash and we have to make it by line of commands
Tuto here : http://forum.xda-developers.com/showpost.php?p=59962266&postcount=127
Good find, good job m8
Thanks for this solution and for the work done.
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Smowza said:
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Click to expand...
Click to collapse
+1
Sent from my LG-D855 using Tapatalk
Smowza said:
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Click to expand...
Click to collapse
Yes you can
it's the twrp 2.8.6.1 version
Nice work.
Thx for the credit.
Huge Improvement!
HI @jac10000,
This is great! Way better than what I have posted.
I assume that this can be repackaged to cater to other LG G3 variants, by simply replacing aboot.img, laf.img, boot.img (users need to have this "bump'd" prior), and recovery.img (need to be "bump'd" prior as well) from those of their respective LG G3 variants, correct?
EDIT: I have promoted your approach in my how-to thread: http://forum.xda-developers.com/showpost.php?p=59897649&postcount=455
topet2k12001 said:
HI @jac10000,
This is great! Way better than what I have posted.
I assume that this can be repackaged to cater to other LG G3 variants, by simply replacing aboot.img, laf.img, boot.img (users need to have this "bump'd" prior), and recovery.img (need to be "bump'd" prior as well) from those of their respective LG G3 variants, correct?
EDIT: I have promoted your approach in my how-to thread: http://forum.xda-developers.com/showpost.php?p=59897649&postcount=455
Click to expand...
Click to collapse
Yes I think it's possible. I don't know the others models of G3 and their specific characteristics for installing custom recovery
jac10000 said:
Yes I think it's possible. I don't know the others models of G3 and their specific characteristics for installing custom recovery
Click to expand...
Click to collapse
HI @jac10000,
Great to hear.
Based on my experience in the Imageprep thread, installation of custom recovery is the same. I'll go ahead and try it out with my D858HK. Will let you know!
Does it make any difference if I have the LG G3 D855 16GB/2GB variant?
Can anyone report back?
@afilbit It work for 16go/2go and 32go/3go variants
Any other host for the file? Mega is blocked in India :/
@alsiladka Ok I do that , just a moment
https://app.box.com/s/qyquibqpnsh6tiq0kf8a7on2kyelvmf7
jac10000 said:
@alsiladka Ok I do that , just a moment
Click to expand...
Click to collapse
What would I need to provide to make this work on a f460k G3 Cat6? I have not found a bump'd boot.img to start with and don't fully understand how to make one myself.
Works great for my LG G3 D855 16GB. Big thanks! [emoji2]
Has anybody tried it on D855TR Turkish version?
BoredKender said:
What would I need to provide to make this work on a f460k G3 Cat6? I have not found a bump'd boot.img to start with and don't fully understand how to make one myself.
Click to expand...
Click to collapse
I do not know the specific obligations for the f460k. But for the D855 I extracted from kitkat Kdz the aboot.img and laf.img and copy them in the tools folder. I think you must use specific recovery Twrp for the f460k. For the bump boot, I have ever install recovery and bump boot by this method and I use here le boot.img includes in it.
Bump stock lp kernel can be made with linux :
http://forum.xda-developers.com/showthread.php?p=59806620
You need unpackbootimg and mkbootimg bin (you can compile them from source).
For the recovery, open bump in linux or the windows tool made for open bump should do the job
Success
Successfully completed process. TWRP installed and Download mode works. LG Stock OS (V20h-EUR-XX) was rooted before using "No Downgrade" method.
Details of my phone -
LGD855
32GB (European Model),
Software Version: V20h-EUR-XX
Thank you OP! You have just opened a new world for me.
Related
[TOOL]"1-Click Transformer Root"-Root/Unroot/cwm/stock rec-TF101(G)/201/300T(G)/SL101
This may be the first completely automated tool for getting root on any ICS Asus Transformer - TF101 / TF101G / TF201 / TF300X / SL101 for all ICS firmware including the latest TF101(G) 9.2.2.6 / 9.2.2.4 and 9.2.1.27 / 9.2.1.25 / 9.2.1.21, TF201 9.4.2.28, TF300T 9.4.3.30 and TF300TG 9.4.4.40.
You can use it on any SBKv1 / SBKv2 / SBKv3 tablet including B70 / B80 / B90 as it is not NVFlash based.
Your data stays intact and OTA functionality is not lost. No more need to downgrade to get root.
You can also use it for flashing CWM recovery or returning to Asus stock recovery ( to re-enable OTA ). (TF101(G),SL101 only)
DOWNLOAD - "1-Click Transformer Root_1.1"
(v1.1) (TF101(G),TF201,TF300T(G),SL101 - See note dated 16-Jun below)
OR
DOWNLOAD - "1-Click Transformer Root" (v1.0) (TF101(G),SL101 only)
UPDATE 16-Sep-2012 - CWM updated to Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8).
Please download latest version of tool and extract to a new directory and run the tool and select option 3 (Install CWM recovery).
UPDATE 21-Aug-2012 - Segmentation fault fully fixed; unroot improved; Superuser replaced with SuperSU.
UPDATE 16-June-2012 - Version 1.1 out. All tablets supported, all ICS. TF101(G),TF201,TF300T(G),SL101!
v1.1 Uses a new exploit method and is much quicker and simpler. For the TF201/300X, only root/unroot options exist, no recovery installation. Everything works for the TF101(G),SL101.
UPDATE 15-June-2012 - Version 1.0 out for TF101(G)/SL101 only. Added unroot option.
- Before running this tool please kill Asus sync or any other tool that may be starting any competing ADB instances.
Please post your experiences and vote in the poll above. It'll be very helpful to improve this tool! Please try both versions of the tool and get some help in this thread before voting NO :fingers-crossed:
_______________________________________________________________________________________________________
1. If you're on a standard tablet and just need root (TF101(G),TF201,TF300T(G),SL101)
- Step 1. Download and extract
DOWNLOAD - "1-Click Transformer Root_1.1"
(v1.1) (TF101(G),TF201,TF300T(G),SL101 - See note dated 16-Jun above)
OR
DOWNLOAD - "1-Click Transformer Root" (v1.0) (TF101(G),SL101 only) - Step 2. Run "1-Click Transformer Root.bat" and let it continue over multiple reboots.
- You'll be root. And with stock Asus recovery.
{
"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"
}
2. If you have root and need Asus stock recovery. (TF101(G),SL101 only)
Why? To enable OTA and/or return to stock like conditions
- Step 1. Run "1-Click Transformer Root.bat". (v1.0)
- Step 3. You'll be presented with a menu. Choose option (4)
- You'll have stock Asus recovery
3. If you have root and need CWM recovery. (TF101(G),SL101 only)
Why? Nandroid backups and restores. Debrick. Flexibility. Numerous other reasons. ( but no OTA)
- Step 1. Run the tool "1-Click Transformer Root.bat". (v1.0)
- Step 2. You'll be presented with a menu. Choose option (3)
- You'll have CWM Recovery
4. If you have root, you can also choose to unroot (TF101(G),TF201,TF300T(G),SL101)
Why? Taking your tablet back to Asus for warranty. Uninstalling all changes done by this tool.
- Step 1. Run the tool "1-Click Transformer Root.bat" ( Either v1.0 (TF101(G),SL101 only) or v1.1 (TF101(G),TF201,TF300T(G),SL101))
- Step 2. You'll be presented with a menu. Choose option (1)
- You'll be unrooted. This will delete all trace of changes made by this tool.
- If the tool finds the stock Asus recovery file for your tablet, it will also flash the stock recovery.
- Unrooting only makes sense if you're otherwise on stock ROM and obtained root using this tool.
5. If you have root, you can reboot into recovery (TF101(G),TF201,TF300T(G),SL101)
Why? So you don't have to press Vol and Power buttons etc to get into recovery / ROM Manager can't reboot to recovery in the Transformer.
- Step 1. Run the tool "1-Click Transformer Root.bat" ( Either v1.0 (TF101(G),SL101 only) or v1.1 (TF101(G),TF201,TF300T(G),SL101))
- Step 2. You'll be presented with a menu. Choose option (2)
- You'll be rebooted into your current recovery, whatever it is.
_______________________________________________________________________________________________________
You will be presented with the menu only if you have root, else root in one step! :highfive:
You can run it multiple times to retry if it fails for any reason. It cleans up after itself.
You'll need:
- At least 50% battery
- USB debugging enabled on your device
- To run this tool on any Windows PC with a working direct internet connection (Proxy users see post #2)
- Please allow any driver installation (DPINST) dialogs to succeed. If automated ADB driver installation doesn't work, you can manually install them from the adb-drivers directory
- Please run the tool as Administrator
- Here's a small tutorial for beginners.
If the tablet is not being detected by the tool, please try any or all of the following:
- Disable and re-enable USB debugging on the tablet with the cable connected and the tool waiting
- Disconnect and reconnect the cable to the same or different USB port while the tool is waiting
- Reboot the PC and run the tool again
- Wait upto 5 mins while the tool is waiting before pressing Control-C to stop execution and running the tool again.
Credits - miloj for the new debugfs exploit method
- Wolf for the core exploit. This tool uses some new variations too.
- rayman84 and Bumble-bee for the excellent Blob Tools
- Transformer reboot to Recovery zephyr team - for the source code to show how to boot into recovery programmatically
_______________________________________________________________________________________________________
Following are some stock Asus files, rest are in the second post. (TF101(G),SL101 only)
There's no need to manually download your firmware specific file from here. The tool should do it automatically.
Recovery blobs (TF101(G),SL101 only)
This section is for the TF101(G),SL101 only
There's no more any need to manually download your firmware specific file from here. The tool should do it automatically.
- These are the stock recovery files needed for switching recoveries between CWM and stock.
- If you're behind a proxy, then don't double click the tool, open a DOS command prompt and cd to the '1-Click Transformer Root' directory and type:
Code:
SET http_proxy=http://your_proxy:proxy_port
"1-Click Transformer Root.bat"
to run the program.
- If you don't have internet, then fret not, you can manually download the Asus stock recovery from the second post and extract it in the 'Source' folder. Even if you don't do this, you will still have root.
THESE FILES ARE NOT NEEDED FOR GETTING ROOT, ONLY TO SWITCH BETWEEN CWM AND STOCK RECOVERY
SWITCHING RECOVERIES FEATURE ONLY WORKS ON THE TF101/TF101G/SL101
These are the stock Asus recovery files:
Neat tool, but you should print some errors on screen if the checks fail. Otherwise it just looks like it's frozen at the step. The checks are a bit overwritten, but good job!
Unrooted to test and seems to work, but it failed the busybox check and ADB check a couple times and froze, you may want to simplify the .bat a bit.
Thanks for your feedback. I have updated the tool with some more descriptive output.
I also added in Slider support.
I shall soon be uploading all the Slider recoveries too.
EDIT - I believe there are no special Slider recoveries. They run the same firmware as the TF101.
error
Sorry, it didn´t work for me.
He couldn´t copy any files because of an read-only file system(see attachment)
I tried it on an Asus slider(9.2.1.24) and copied the stock recovery blob into the source folder.
do you have any solution for that?
sry for my bad english=)
Mr.Age said:
He couldn´t copy any files because of an read-only file system(see attachment)
Click to expand...
Click to collapse
Hi,
Can you run the updated tool and send me the full ouput copied as text?
You can replace the first line in "1-Click Transformer Root.bat"
@echo off
to
@echo on
before running and then capture the full output as text.
Didn´t work with the updated Version.
i attached the output with @echo on
thx
Update, it seems that recovery mode ADB may need another set of ADB drivers to work.
The symptom is when you boot into CWM recovery, adb can't seem to connect to the tablet but it can do so fine when the tablet is in normal mode.
So the tool may fail after installing recovery.
This is happening on a Slider.
If anyone else with a Slider or even TF101 can confirm this then great.
Can you do a:
adb shell
to your tablet when in recovery mode?
If this tool seems to get stuck in recovery and waits there forever, then you can try installing the drivers located here:
http://forum.xda-developers.com/showthread.php?t=1379875
Both the android_apxusb.inf and android_winusb.inf file
And please report your findings.
worked!!
OK with your new version, he started in CWM-Recovery after installin, stayed for a while but wenn the PC installed the right drivers your tool continued and finished without any Problem!!!
Now i´m rooted with stock recovery!!Very nice
THANK YOU very much!!!
Hello,
It seems this tools didn't work on my TF101G either.
Attached is the whole process on the batch file.
Mok Jackson said:
Hello,
It seems this tools didn't work on my TF101G either.
Attached is the whole process on the batch file.
Click to expand...
Click to collapse
Looks like you're getting the:
adb server is out of date. killing...
error. This is because some other adb.exe version on your PC is starting up from somewhere.
You can, either:
1. Try again ( I have uploaded an updated version of the tool )
2. Kill any running adb.exe and any other tool that might be starting it and try again
3. Disable mock locations on the tablet if it's set and try again
4. I have uploaded an updated version of the tool. Try that.
5. Find all other versions of adb.exe on your PC and replace them with the one from this package ( I have just updated it with the latest adb.exe)
6. Remove any other versions of adb from your path if it's there.
That throws errors, but adb still works with it. I get it all the time, you can fix with a cd %dp% or similar.
Thing O Doom said:
you can fix with a cd %dp% or similar.
Click to expand...
Click to collapse
Thanks for that, do you have any more info on that?
Add this right under Echo off at the top of your bat. It changes to the current directory.
cd %~dp0
Thing O Doom said:
Add this right under Echo off at the top of your bat. It changes to the current directory.
cd %~dp0
Click to expand...
Click to collapse
Thanks for that. I was changing CWD earlier, but have used it anyways for proofing it more.
So it still doesn't solve other ADB instances of different versions coming and killing this one.
I tried t.
The only permanent solution I could find was to download the latest Platform SDK from Google (or better yet, use the ones provided by this tool - it's the current latest) and making sure that this ADB directory is in the user's PATH variable.
And the following files from the latest platform tools directory (or our tool) is replicated wherever adb.exe exists in the whole system:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
Nice, it works for me! I just rooted my Slider 101 with this tool, works great, no Porblems at all. Thanks vor this tool!
Thanks very much, much this worked with my TF101 using the universal naked drivers linked above. Now have root on ICS 9.2.1.24!
Sent from my Transformer TF101 using Tapatalk 2
Yes, i tried to replace all adb files under C:\Program files\asus with attached adb drivers, i can root my transformer successfully. Thanks for your help.
Here is the detail.
WINDOWS 7
TF101G
TW_epad_9.2.2.4
Great work, thank you very, very much! I love to use DroidWall and Titanium Backup...
I have my german Slider now for 2 days and was very happy to see, that there is a one-click-root-possibility. That makes the experience of the slider much better.
I am really very thankfull! And I hope, that the OTA Updates will work, but this only the future will show.
pf said:
And I hope, that the OTA Updates will work, but this only the future will show.
Click to expand...
Click to collapse
Hi!
Glad you're root! You can confirm if you're on Asus recovery by running the tool again. You will get a menu this time and choose option "5. Reboot into current recovery.".
It should reboot you into Asus recovery where you'll get an Android icon and it'll stay there. You'll have to physically reboot.
That confirms you're on stock Asus recovery and OTAs will work fine.
If, for any reason you get the CWM recovery menu, then fret not. You can always download your stock Asus recovery file from the second post and extract the files in the 'Source' directory and rerun the tool and choose option '4. Install Asus stock recovery.'
That should do the trick. Good luck!
Note: This thread is old. Currently you can just update the firmware and then root again using Easy Root Tool
This is a guide on how to update the Z1 Compact to any firmware without losing root on locked bootloader. For unlocked bootloader, please see post #3 ( http://forum.xda-developers.com/showpost.php?p=51254652&postcount=3 )
Requirements
Latest flashtool ( http://www.flashtool.net )
Rooted Z1 Compact (check here for how to root: http://forum.xda-developers.com/showthread.php?t=2642081 )
D5503_14.X.A.X.XXX_Generic_XX-nosystem.ftf from 'Firmwares' below
z1c-44-14.X.A.X.XXX-XX.system.flashable.zip from 'Firmwares' below
SuperSU ( http://download.chainfire.eu/supersu )
Latest Z1C-lockeddualrecovery(...).flashable.zip ( http://nut.xperia-files.com/ ) (atleast v2.7.117)
Firmwares
Here you can find some prepared firmwares. Note: Do not mix files from different firmwares!
Jelly Bean (4.3)
14.2.A.1.114 Generic UK (Darkimmortal)
z1c-43-uk.system.flashable.zip | share-online mirror
D5503_14.2.A.1.114_Generic UK-nosystem.ftf
Click to expand...
Click to collapse
KitKat (4.4)
14.3.A.0.681 Generic UK (Darkimmortal)
z1c-44-uk.system.flashable.zip | mega mirror
D5503_14.3.A.0.681_Generic_UK-nosystem.ftf | mega mirror
Click to expand...
Click to collapse
14.3.A.0.757 Generic DE 1279-6978 (louis0815)
z1c-44-14.3.A.0.757-DE.system.flashable.zip
D5503_14.3.A.0.757_GenericDE-nosystem.ftf | mediafire mirror
Click to expand...
Click to collapse
14.3.A.0.757 Generic NO 1279-4149 (nism0o)
z1c-44-14.3.A.0.757-NO.system.flashable.zip
D5503_14.3.A.0.757_GenericNO-nosystem.ftf
Click to expand...
Click to collapse
14.3.A.0.757 Generic UK 1279-4727 (codified)
z1c-44-14.3.A.0.757-UK.system.flashable.zip | gdrive mirror
D5503_14.3.A.0.757_Generic_UK-nosystem.ftf
Click to expand...
Click to collapse
14.3.A.0.757 Generic FR 1279-5365 (emilic)
See here: http://forum.xda-developers.com/showpost.php?p=52599589&postcount=385
Click to expand...
Click to collapse
14.3.A.0.761 Generic NO 1279-4149 (paul5425)
z1c-44-14.3.A.0.761-NO.system.flashable.zip
D5503_14.3.A.0.761_GenericNO-nosystem.ftf
Click to expand...
Click to collapse
Tutorial
You will not lose any data. It is still recommend to take a backup.
Copy D5503_14.X.A.X.XXX_Generic_XX-nosystem.ftf to your flashtool installation in the folder firmwares/
Put z1c-44-14.X.A.X.XXX-XX.system.flashable.zip on your sdcard (do not unpack)
Put Z1C-lockeddualrecovery(...).flashable.zip on your sdcard (do not unpack)
Download SuperSU and put on your SD card (do not unpack)
Go to the recovery menu and try flashing SuperSU. If it succeeds, proceed. Otherwise change recovery menu (TWRP is Volume DOWN)
In the recovery menu format /system (located under Mounts & Storage) (do not reboot!)
Install the following files in recovery (in this order)
z1c-44-14.X.A.X.XXX-XX.system.flashable.zip
Z1C-lockeddualrecovery(...).flashable.zip
SuperSU zip file
After installing go to Advanced => Power off (Power off might also be located under Power Options, depending on the recovery you use)
Boot your phone in flashmode (Hold volume down while phone is off and plug in your USB cable)
Open flashtool and flash D5503_14.X.A.X.XXX_Generic_XX-nosystem.ftf (select Wipe [Uncheck Data] and Exclude [Uncheck ALL])
You're done!
Hashes
D5503_14.2.A.1.114_Generic UK-nosystem.ftf
MD5: 47005E1E16B340A90B958919122F89AA
SHA1: 252C905F1F0213D809925BC32A955E421FE4C3E6
z1c-43-uk.system.flashable.zip
MD5: 6221178B6809EA943A0AB5654A9D6A2D
SHA1: 8B9BEAB4846927DED38018B93C56993BD017BFB8
D5503_14.3.A.0.681_Generic_UK-nosystem.ftf
MD5: 5D1BDD44DF531280984B60E810A87FFA
SHA1: 5ADE48599414BE47A0A7DD1BCB37C0F5518F7CCB
z1c-44-uk.system.flashable.zip
MD5: 148BDD3BEAEDE850CAF085ED82518FF9
SHA1: FB594821FBEA030657CA5D048DE2593194F18DF8
D5503_14.3.A.0.757_GenericDE-nosystem.ftf
MD5: D720CD278E0DB88F49FA22CBBE441720
SHA1: 3F4C47B841BD24511C30BB0E44030872BD93921A
z1c-44-14.3.A.0.757-DE.system.flashable.zip
MD5: 38FA3162C725B0E357FD8CDE1AA8CDE8
SHA1: F898DC9580D84D541C622307439B45A607A0A7A5
D5503_14.3.A.0.757_GenericNO-nosystem.ftf
MD5: 3E76A9E4DFE4BD6D2CE05DBBC0B09CB8
SHA1: 44EFFED69E881B08FF6F3AEEF0EDBE69C59187DC
z1c-44-14.3.A.0.757-NO.system.flashable.zip
MD5: A6B54DF73E5E0038152EC2AFFE4E7067
SHA1: DF6F497987D44F43ABF49C4BB98ECC49058F97C6
D5503_14.3.A.0.757_Generic_UK-nosystem.ftf
MD5: 915E348841834816216F4EFE6BB85D29
SHA1: 28EBCA4A3218E45C1C7B00C6DE494052A004DA0B
z1c-44-14.3.A.0.757-UK.system.flashable.zip
MD5: 9A8089751D964312E255ABC507AD1C90
SHA1: 2FC34DB65EA087C0D824502FE1E801027461EC49
D5503_14.3.A.0.761_GenericNO-nosystem.ftf
MD5: 3DD5723B43F834ED55E65A9B8DCCB0D2
SHA1: 84848D4C1ABBD4C2729E3BBCE0706A25379717F8
z1c-44-14.3.A.0.761-NO.system.flashable.zip
MD5: 771B257718FCE8CBE8E3EAE6F29B0765
SHA1: C737EEE5D1DB28F8F918A126A18EDCA7FAF8E5AF
Questions
I get an error in flashtool: "Cannot open bundle. Flash operation canceled"
You need the latest flashtool.
Click to expand...
Click to collapse
I am from Country XY but there is no firmware for my country? :crying:
It doesn't really matter what localization you use. The firmwares are almost the same. Your language will still be available.
Click to expand...
Click to collapse
Are these roms deodexed?
No. All roms are odexed.
Click to expand...
Click to collapse
I can't access recovery menu, when I boot my phone the light is orange, not green?
Somehow you lost your recovery menu. If your bootloader is locked you need to start again from the beginning of the rooting guide.
Click to expand...
Click to collapse
I have another error, which is not in this list!
Post it in the thread but note for successful help you need to provide the following:
dualrecovery version used
flashable system zip used
ftf no-system used
Click to expand...
Click to collapse
Proof
Confirmed working by pcpepik, Boes40 ( http://forum.xda-developers.com/showpost.php?p=51476157&postcount=156 ), tommy17 ( http://forum.xda-developers.com/showpost.php?p=51384084&postcount=125 ), mikk_11 ( http://forum.xda-developers.com/showpost.php?p=51341824&postcount=105 ) and many more on locked bootloader :highfive:
{
"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"
}
Credits
Darkimmortal
[NUT]
pcpepik
Hello,
Seems missing the download path of "Z1C-lockeddualrecovery(...)flashable.zip" and is it also copy to SD card?
Unlocked bootloader
Requirements
Latest flashtool ( http://www.flashtool.net )
fastboot and flashmode drivers installed
Z1 Compact with unlocked bootloader
ftf of firmware (check here http://forum.xda-developers.com/showthread.php?t=2631291 or general section for official firmwares)
SuperSU ( http://download.chainfire.eu/supersu )
Custom kernel with recovery (e.g. dualrecovery kernel or http://forum.xda-developers.com/showthread.php?t=2620794 )
Note: Kernel needs to be for the specific firmware version (dualrecovery kernel is only for latest firmware)
Tutorial
You will not lose any data. It is still recommend to take a backup.
Copy the firmware ftf to your flashtool installation in the folder firmwares/
Download SuperSU and put on your SD card (do not unpack)
Boot your phone in flashmode (Hold volume down while phone is off and plug in your USB cable)
Open flashtool and flash your ftf (select Wipe [Uncheck Data] and Exclude [Uncheck ALL])
After flashing, boot your phone in fastboot mode (Hold volume up while phone is off and plug in your USB cable)
Download a custom kernel and unzip until you have a file called *.img
Put the custom kernel inside the folder of flashtool called x10flasher_lib/
Open cmd and navigate to this folder (e.g. cd C:\flashtool\x10flasher_lib)
Execute the following command to flash the custom kernel (boot.img is the filename of the kernel, change if needed)
fastboot.exe flash boot boot.img
Boot your phone and go to the recovery menu
Note: This is different in some kernels, default is to hold volume up when the led lights up
Optional: If you are using dualrecovery kernel, flash the kernel flashable zip
Flash SuperSU zip
You're done!
Confused about point 5 : Install Z1C-lockeddualrecovery(...)flashable.zip
and warning post 1 : Do not try to flash the dualrecovery, you will end up stuck at boot logo!
So what to install on point 5?
Boes40 said:
Confused about point 5 : Install Z1C-lockeddualrecovery(...)flashable.zip
and warning post 1 : Do not try to flash the dualrecovery, you will end up stuck at boot logo!
So what to install on point 5?
Click to expand...
Click to collapse
Whoops, forgot to delete that step. Fixed now, thanks
what to do with error in flashmode :Cannot open bundle. Flash operation canceled
and point 5 should be power options, not advance
Boes40 said:
what to do with error in flashmode :Cannot open bundle. Flash operation canceled
and point 5 should be power options, not advance
Click to expand...
Click to collapse
You need latest flashtool. Ok thanks, for the tip, which recovery are you using? It's advanced in CWM.
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Boes40 said:
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Click to expand...
Click to collapse
Same!
I have rooted Z1c with Android 4.4!
Hurry!
But supersu can't update. Some app can't rooted (eg. Greenify), Es explorer can't mount system r/w...
Titanium is still working though, Latest Xposed (beta) isn't, no root.
Boes40 said:
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Click to expand...
Click to collapse
Root should still work. But to fix the problem, try this.
Download SuperSU from here: ( http://download.chainfire.eu/supersu )
Copy the file su from the folder arm to somewhere on your phone. (e.g. /tmp)
Give correct permissions (755)
Then copy it to /system/xbin and overwrite the old one.
Please let me know if it worked.
Boes40 said:
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Click to expand...
Click to collapse
Could we update SuperSu from Play?
Or how can we solved: We have root, but we have an not working supersu...
Problem is I can't copy the file with rootexplorer. First time RE opens it asks for root, press yes of course but it looks it doesn't get root.
Boes40 said:
Problem is I can't copy the file with rootexplorer. First time RE opens it asks for root, press yes of course but it looks it doesn't get root.
Click to expand...
Click to collapse
What is the error message? And have you tried with adb?
And can you check if your system flashable zip has the same hash as in the first post?
With Root Explorer, first mesage is :The current file sytem is r only. Do you want to remount as r-write and continue the operation, / yes / su already exists. Do you want to overwrite it? / yes / Copy failed su to /system/xbin
Haven't tried with adb, how please?
How to check the hash?
thanks
zxz0O0 said:
What is the error message? And have you tried with adb?
And can you check if your system flashable zip has the same hash as in the first post?
Click to expand...
Click to collapse
After run esexplorer and granted supersu: 1. screenshot
After run supersu: 2.
After update normal (we don't have CWM...): 3.
Root checker: 4.
Supersu: 5.
All working except supersu...
Boes40 said:
With Root Explorer, first mesage is :The current file sytem is r only. Do you want to remount as r-write and continue the operation, / yes / su already exists. Do you want to overwrite it? / yes / Copy failed su to /system/xbin
Haven't tried with adb, how please?
How to check the hash?
thanks
Click to expand...
Click to collapse
Copy the new su binary to /tmp then do
adb shell
su
chown root:root /tmp/su
chmod 755 /tmp/su
mount -o remount,rw -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
cp /system/xbin/su /system/xbin/su.old
mv /tmp/su /system/xbin/su
papzi57 said:
After run esexplorer and granted supersu: 1. screenshot
After run supersu: 2.
After update normal (we don't have CWM...): 3.
Root checker: 4.
Supersu: 5.
All working except supersu...
Click to expand...
Click to collapse
Have you tried to replace su binary as I posted above and post #11 ?
Just followed ur instructions!
After successful flashing I can still enter Recovery.
Xposed Installer NOT working, requires writing permissions!
mount -o remount,rw -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
error:
block/platform/msn_sdcc.1/by-name/system /system
mount : Operation not permitted
255|[email protected]:/ #
for adb wich mode need: fastboot or flashmode or normal. (I forgotten...)
Su binary can't replace: permission denied
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
CLEAR/DELETE DALVIK-CACHE FOLDER FROM "/data/dalvik-cache" IN ROOT EXPLORER OR TWRP AFTER INSTALLING BOOT IMAGE TO ALLOW SYSTEM TO ADJUST
##FLASH THE LATEST SUPERSU ZIP BELOW##
P.S. I NOTICE IT IS NO LONGER SYSTEM-LESS MODE. SO WE CAN TRIM THE SUPERSU SYSTEM-LESS CONTENT FROM THE RAMDISK.
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
If you have ISSUES WITH DATA SPEEDS in certain areas, especially if you tether, GO INTO THE DIALER and DIAL *#*#4636#*#* then ACCESS PHONE INFORMATION and SELECT CDMA auto (PRL) UNDER SET PREFERRED NETWORK TYPE. LTE seems to be problematic in certain areas with speeds dropping to 150kbps and with this solution you'll be getting about 600 to 700kbps so at least it'll be a gain until you get into an area with better LTE coverage. In a good coverage area, I get download speeds of up to 5 to 7 mbps with LTE on, but in bad areas, CDMA works better. If you want to tether with a wireless third party solution make sure to run in a terminal window or adb shell as root : pm disable com.htc.tetheringguard
DOWNLOAD BOOT IMAGE: http://forum.xda-developers.com/attachment.php?attachmentid=3917986&d=1477604429
DOWNLOAD SUPERSU BETA: https://download.chainfire.eu/1009/SuperSU/SR2-SuperSU-v2.78-SR2-20161029143931.zip?retrieve_file=1
DOWNLOAD SCRIPTS: http://forum.xda-developers.com/attachment.php?attachmentid=3863279&d=1472880351
DOWNLOAD PIE FIX: http://forum.xda-developers.com/attachment.php?attachmentid=3844539&d=1471383163
DOWNLOAD BOOT IMAGE TOOL : http://forum.xda-developers.com/attachment.php?attachmentid=3917995&d=1477605263
DOWNLOAD HTC DRIVERS AND MINIMAL ADB + FASTBOOT: http://forum.xda-developers.com/attachment.php?attachmentid=3868562&d=1473328405
ANDBLOCKDEV.sh from scripts zip will speed up file input and output speeds, its contents have been incorporated into the boot image so the scripts files are for your own archival.
The zip DESIRE626SIMGTOOL.zip contains the android image kitchen and the 6.0.1 Boost Desire 626S boot image contents already extracted into two folders split_img and ramdisk with recent modifications. Enjoy!
http://www.vysor.io/ is a great tool to control your android device from a computer within chrome. You should try it out.
I provided a zip named HTCDrivers.zip containing the installation for both fastboot and adb drivers for the Boost Desire 626S, and minimal adb and fastboot. This will help you connect your device up with Vysor.
COPY the FILES; fastboot.exe, adb.exe, AdbWinUsbApi.dll and AdbWinApi.dll FROM - C:\Program Files (x86)\Minimal ADB and Fastboot - TO - C:\Windows\System32 - AND - C:\Windows\SysWOW64
Once you have installed the drivers for HTC devices,
and copied the minimal adb and fastboot files specified above to both system folders, you should be able to run adb commands without a problem by just opening a command prompt as administrator,
and RUNNING the command:
adb devices
- to start the adb server. This will allow connection with Vysor.
##########
For those who prefer nightbreed813's 6.0.1 slim rom version, I uploaded 601VPNDIALOGSFIX.zip to fix the issue with authorizing VPN clients, but first YOU HAVE TO CREATE /system/priv-app/VpnDialogs in Root Explorer or any other root filesystem browser, then reboot to TWRP recovery and flash the zip.
DOWNLOAD VPNFIX : http://forum.xda-developers.com/attachment.php?attachmentid=3860930&d=1472669879
##########
Also, you can get your MSL/SPC security code easily.........
Use the info in this thread to get your MSL/SPC security code so you can write new values to NV entries in the modem. Some values are locked but you can change the BC config for both LTE and CDMA so that would at least be helpful.
INFO HERE: http://forum.xda-developers.com/spri...k-sim-t3314755
##########
Android settings can be changed in the terminal for three namespaces; system, global and secure.
In the terminal run:
settings list system
settings list global
settings list secure
For each namespace all associated settings and their values will be listed. To change a setting type:
settings put system setting_name_here value_here
settings put global setting_name_here value_here
settings put secure setting_name_here value_here
##########
{
"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"
}
Look now has working VPN......
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
anthonykb said:
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
Click to expand...
Click to collapse
Will this run on the Metro Variant?
As far as I know no but you can try in case it might.
Enter these commands in a new terminal window:
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
The backup boot image can be flashed from the sdcard in TWRP recovery if the device fails to boot into the system after flashing the boot image contained in the zip in the attachments.
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
MetroPCS Boot Image
GotHeart said:
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
Click to expand...
Click to collapse
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
anthonykb said:
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
Click to expand...
Click to collapse
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
GotHeart said:
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
Click to expand...
Click to collapse
I meant so you tried the boost version and it wouldn't boot?
anthonykb said:
I meant so you tried the boost version and it wouldn't boot?
Click to expand...
Click to collapse
No i havent tried it yet
GotHeart said:
No i havent tried it yet
Click to expand...
Click to collapse
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
Then unzip the 601bootimg.zip file with Zarchiver in the Play Store and flash the extracted boot image.
anthonykb said:
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
Click to expand...
Click to collapse
Okay ill do it now and let you know
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
GotHeart said:
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
Click to expand...
Click to collapse
Flash back the backed up boot image in TWRP and see if the sdcard mounts right. The mount point contained in the boost boot image is probably wrong for the the sdcard/emmc in the metropcs phone.
I did but my sdcard got corrupted so i was forced to format it.
GotHeart said:
I did but my sdcard got corrupted so i was forced to format it.
Click to expand...
Click to collapse
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
anthonykb said:
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
Click to expand...
Click to collapse
Its nothing important lol.any chance you can share what you did or how?
Use the Android Image Kitchen by osm0sis
GotHeart said:
Its nothing important lol.any chance you can share what you did or how?
Click to expand...
Click to collapse
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
anthonykb said:
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
My mistake i was in a hurry when i typed that last reply.
Im aware of how to unpack/repack boot images and i appreciate the link,but i was wondering what modifications that were made.if youd prefer not to share,i can upload my boot image if youd like to make the modifications yourself.im just trying to make this compatible with the metro version.
The same modifications done for the Boost Desire 626S might not work well for the MetroPCS version so upload the image you backed up yesterday as an attachment in a reply post and I'll work on it.
Thanks a ton!
MetroPCS Boot Image
GotHeart said:
Thanks a ton!
Click to expand...
Click to collapse
Run busybox top in the terminal on your phone and post some screenshots so I can see what might need to be done. We want to see what processes would be the culprit behind bogging down precious processor time and reducing the snappiness of the device in reacting to realtime input and handling current requests.
Is anyone working on rooting this device? I just bought one and it seems to be a really nice tablet, except I'd prefer something other than touchwiz. Although I'd be perfectly happy with just rooting at least.
If there's no one rooting it, could someone help me find the resources to learn how to possibly root this device myself? I'm a beginner with modding android but I pick up things quickly so I'd like to at least give it a shot.
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Mefody said:
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
Thank you so much! It worked perfectly!
You should post a thread detailing your instructions. Hell, I'll do it if you're too busy
shahmir_k said:
Thank you so much! It worked perfectly!
You should post a thread detailing your instructions. Hell, I'll do it if you're too busy
Click to expand...
Click to collapse
OK! Make this thread, cause I'm working now on TWRP for this tablet.
Please after thread creating place here link to it... :good:
Thank you for the solution
Mefody said:
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
Thank you so much. I am a newbie to the whole rooting android thing. I came across this post when trying to root my SM-T385 tab and thought it was too complicated. I tried many other simpler methods and nothing worked. Finally, I took my time figure out your solution and lo-behold it actually works.:good:
I am now a proud owner of a rooted android tablet.
Thank you for the detailed write-up. Just got a new SM-T380 (already on 7.1.1) and would like to have root.
I followed the instructions and got to the Odin Flash part and the tablet came up with "Only official released binaries are allowed to be flashed". Had to hard reset to get it to boot again (w/o root).
Anyone know of a workaround or why didn't work on this one?
crewdog said:
Thank you for the detailed write-up. Just got a new SM-T380 (already on 7.1.1) and would like to have root.
I followed the instructions and got to the Odin Flash part and the tablet came up with "Only official released binaries are allowed to be flashed". Had to hard reset to get it to boot again (w/o root).
Anyone know of a workaround or why didn't work on this one?
Click to expand...
Click to collapse
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Mefody said:
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Click to expand...
Click to collapse
Thanks. I don't see "OEM unlock" in the developer now, so think I'm in the penalty box for a week. Bummer.
Mefody said:
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Click to expand...
Click to collapse
What's the firmware build number?
Im having the same issue, help please?
ashyx said:
What's the firmware build number?
Click to expand...
Click to collapse
My SM-T380 build number is: NMF26X.T380DXU1AQI7
Can't find a way to boot T380 to fastboot mode to run "fastboot oem unlock" unless it can somehow be done with ADB.
Thanks!!!
ashyx said:
What's the firmware build number?
Click to expand...
Click to collapse
I'm on T385XXU1AQJ3-20171116091340 now:
PDA/AP Version - T385XXU1AQJ3
CSC Version - T385OXE1AQJ1
MODEM/CP Version - T385XXU1AQHE
Build Date - 2017-10-30
OS - Nougat 7.1.1
Link to original firmware.
Link to patched "boot.img".
I see, You are guru in TWRP assembling . . .
So here is some sources & technical infos:
Link to kernel OpenSource.
Tablet technical name: gta2slte
Partition sizes from command "dd i= ... o= ..."
BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3674210304
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053993984
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432
joeyw007 said:
Can't find a way to boot T380 to fastboot mode to run "fastboot oem unlock" unless it can somehow be done with ADB.
Thanks!!!
Click to expand...
Click to collapse
There is no "Fastboot Mode" in this model, like in many other from Sansung, HTC ets. Samsung also insert absolutely bad for ROM-creators KNOX system.
So here is S-shot for OEM is unlocked (and tablet is rooted)... But there no chances for "fastboot"
{
"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"
}
Under Linux I use Heimdall. Here is screen, where device are detected & ready to be flashed.
One thing about Heimdall... Version from repos didn't work with our device. So we have to compile it from Benjamin-Dobell github where this bug are fixed yet.
Building source is trivial:
Code:
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make
OEM Unlock Enabled On New Update
I contacted Samsung and spoke with them about the OEM unlock feature missing from developer options and explained I needed to root my table for development purposes for work. They gave me the usual reply of we don't support rooting. I replied I'm not asking you to. I'm asking you to unlock the boot loader on a device I bought, belongs to me and should be allowed to modify as I see fit. I am aware of security and warranty issues please do something about this. Remember Apples DE boggle. A few days later an OTA update puts the feature in my developer options. Coincidence or did they listen? Who knows. I will be trying the root procedure as soon as the new rom downloads and I can get the boot.img from the AP Block. I'll let you guys know how it comes out.
Root Achieved!!! For Cellular South Build T380XAR1AQK3
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
OK with the new update the boot loader can be unlocked from dev options and the above method for rooting is %100 successful. Just make sure to tell Magisk Manager under settings to output patched boot.img to odin mode "img.tar" then just flash the patched_boot.img.tar via the AP slot with Odin.
joeyw007 said:
Who knows. I will be trying the root procedure as soon as the new rom downloads and I can get the boot.img from the AP Block. I'll let you guys know how it comes out.
Click to expand...
Click to collapse
I know at last 3 person with the same situation... Sometimes, when we try to change region of firmware or try to root it out by progs like Kingo, Kingroot & CF-Autoroot it seems to Samsung, that You are dangerous hacker - and it set the 1-week "penalty" mode. So OEM-unblocking became disabled during this penalty period.
Like I said Who Knows, I am Curious...
I am curious if anyone missing the OEM Unlock feature in dev options running build T380DXU1AQI7 before this morning received an OTA update to build number T380XAR1AQK3 with the ability to unlock your bootloader from dev options. I haven't changed regions successfully flashed anything to this tablet and have had it for a month. OEM unlock appeared after OTA update this morning. Now I'm rooted and all is well. Before restarting your tablet if you root this build I would suggest turning OEM Unlocking on again after rooting, as it wipes your tablet, otherwise you will get an error message about not being able to boot unauthorized binaries and have to repeat the process.
Mefody said:
I'm on T385XXU1AQJ3-20171116091340 now:
PDA/AP Version - T385XXU1AQJ3
CSC Version - T385OXE1AQJ1
MODEM/CP Version - T385XXU1AQHE
Build Date - 2017-10-30
OS - Nougat 7.1.1
Link to original firmware.
Link to patched "boot.img".
I see, You are guru in TWRP assembling . . .
So here is some sources & technical infos:
Link to kernel OpenSource.
Tablet technical name: gta2slte
Partition sizes from command "dd i= ... o= ..."
BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3674210304
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053993984
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432
Click to expand...
Click to collapse
If you could try this build of TWRP out. It's built using the T380 kernel, but should work for the T385 also.
https://androidfilehost.com/?fid=889964283620778312
.
ashyx said:
If you could try this build of TWRP out. It's built using the T380 kernel, but should work for the T385 also.
Click to expand...
Click to collapse
Thanks a lot!!! It works commonly fine!
Two moments:
1. CPU Temperature too high, as for me May be path to termal probe not correct.
2. /data partition are unmount. I think it's due to uncorrect "footer".
I started on github TWRP repo, but I have no enough experience - my build on minimal twrp-7. 1. manifest builds OK, but after flashing I have boot-loop.
Maybe You will kindly find some time to look at this repo: https://github.com/mefody1971/android_device_samsung_gta2slte
Some info regardly temperature & /data partition
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053977600 # 8053993984 - 16384 (footer)
TARGET_USE_CUSTOM_LUN_FILE_PATH := "sys/class/android_usb/android0/f_mass_storage/lun/file"
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_CUSTOM_CPU_TEMP_PATH := /sys/devices/virtual/thermal/thermal_zone1/temp
In attachment I put recovery.log
Mefody said:
Thanks a lot!!! It works commonly fine!
Two moments:
1. CPU Temperature too high, as for me May be path to termal probe not correct.
2. /data partition are unmount. I think it's due to uncorrect "footer".
I started on github TWRP repo, but I have no enough experience - my build on minimal twrp-7. 1. manifest builds OK, but after flashing I have boot-loop.
Maybe You will kindly find some time to look at this repo: https://github.com/mefody1971/android_device_samsung_gta2slte
Some info regardly temperature & /data partition
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053977600 # 8053993984 - 16384 (footer)
TARGET_USE_CUSTOM_LUN_FILE_PATH := "sys/class/android_usb/android0/f_mass_storage/lun/file"
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_CUSTOM_CPU_TEMP_PATH := /sys/devices/virtual/thermal/thermal_zone1/temp
In attachment I put recovery.log
Click to expand...
Click to collapse
The errors you are seeing are due to an encrypted data partition. TWRP doesn't support Samsungs encryption method yet.
To mount DATA you need to FORMAT the DATA partition and flash my encryption patch to disable encryption which you can find in my sig.
When I post a proper thread all instructions will be there. For now you can consult any one of my TWRP threads for more info.
ashyx said:
The errors you are seeing are due to an encrypted data partition. TWRP doesn't support Samsungs encryption method yet.
To mount DATA you need to FORMAT the DATA partition and flash my encryption patch to disable encryption which you can find in my sig.
When I post a proper thread all instructions will be there. For now you can consult any one of my TWRP threads for more info.
Click to expand...
Click to collapse
OK! Thanks a lot!!! Will find all available info and try to play with formatting /data partition & setting on Your patch.
Awaiting Your special thread for this device. Anyway - You did a great job :good:
ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL
Installing an OTA.zip Update with ADB Sideload
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -
Click to expand...
Click to collapse
In this thread you will find different ways to install an OTA update :
Via ADB SIDELOAD (this post) - Via Recovery Mode - Via Local Upgrade
I am writing this tutorial on ADB Sideload, one more on this topic, in order to be able to push an OTA Zip update, which for some reason could not be done properly.
Sometimes manufacturers allow users to make links or zip files of OTA updates available to other users. Once you have downloaded the OTA zip file, you will need this tutorial to proceed with the installation.
I borrowed the first two screenshots from the web so that I could explain clearly with pictures.
In the end it is very simple and requires little command line knowledge. But you will need to check some things:
- Firmware stock
- Unmodified system partition
- Third party apps like Magisk, Xposed Framework, and as a precaution TWRP Recovery should not be installed on your smartphone
Before starting, here is the list of prerequisites to perform the sideloading of the OTA package.
1. Have a backup of your data, even if theoretically performing a sideload will not erase your data,
2. Download the USB Drivers from the manufacturer, or the latest one from Google ( Link )
3. If you haven't already done so, you must download and install Android SDK Platform-tools (platform-tools_r33.0.2-windows.zip)
4. Don't forget to push on this folder "platform-tools" the file named "Global full Nothing OS 1.1.0.zip" - for example- that you need
4. And finally you will have to activate the USB debugging of your Phone(1) : to do so, you have to go to : Settings => System => Advanced => Type 7 times on the build number => once done, a pop-up will appear and will tell you that you have become a "Developer" => On some devices you will have to type in the Pin code.
5. Once you have become a developer => go back to System => Developer Options => Enable the USB Debug toggle
6. That's it if you are ready to do a Sideload, but also other operations!
{
"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"
}
These prerequisites are essential for this and a number of other operations.
You are ready, the tension is rising! You will succeed!
To do this, you must reboot your Phone(1) into the standard recovery system and you have 2 ways to reboot into Recovery.
1. You can use the hardware key combination specific to your smartphone.
2. Or use the ADB command
Booting into Recovery Stock mode with the ADB command
You go to the start screen of your PC and in the search bar you type:
Code:
cmd
and then press Enter. The command prompt starts.
Depending on where you have placed your "Platform-tools" folder you type:
Code:
C:\WINDOWS\system32>cd c:\platform-tools
and you should see on your command line screen
Code:
c:\platform-tools>
Once you are in your Platform-tools folder, connect your smartphone to your PC, making sure that USb debugging is effective.
Type the following command: adb devices and you should see the identification of your smartphone
When you run an ADB command, you should see an RSA key prompt on your smartphone screen asking you to allow USB debugging. Press OK to allow it.
Type the following command: adb reboot recovery
Then the command: adb sideload "file name".zip - For the example, I typed the full name of the file, but you can rename the file shorter like "nothing_ota".zip
That's it, normally the installation is started and you just have to wait for the update to be installed on your device. Once the installation is successful, you can restart your device.
I hope this tutorial has helped you to push an OTA.zip update.
Go ahead now
Installation via recovery mode
The recovery mode of the Phone(1) is similar to that of the Google Pixel. This allows you to easily sideload the update packages via the recovery interface.
To perform this process, here are the steps and requirements:
Have downloaded the .zip file of the update to your computer
Your Phone(1) must be recognised by the ADB command on your computer
The Process:
Go to your Shell terminal, then run the recognition command:
Code:
adb devices
then the command :
Code:
adb reboot recovery
On your Phone(1) screen, you should see this "No command"
While pressing the Power button, press the Volume Up button then release both buttons quickly. The Android recovery menu should be visible.
Nothing Phone 1 recovery mode
On your Phone(1) screen, select the option: Apply update from ADB.
On your computer, run the command:
Code:
adb devices
This should return the serial number of the device with the 'sideload' next to its name, indicating that your device is connected to the computer in sideload mode.
On your computer, run the command:
Code:
adb sideload "filename".zip
The "filename" part should be replaced with the full path, followed by the name of the file downloaded in step 1.
The update will be installed on your phone.
Once the installation is complete, select "Reboot system now" on your phone to reboot into the new version.
Well done, you have installed the new update of Nothing OS to your Phone(1) with success
To date I still haven't received my phone(1). Once I have it in my hands, I will make screenshots about this tutorial.
Install OTA using Local Upgrade method
Create a folder named “ota” (without the quotes) at the root of the internal storage. Meaning outside every folder.
Copy the OTA update ZIP file from above to that folder.
Open the phone app and Dial ##682##
This should launch an offline update tool.
The tool will scan for an OTA file from internal storage and install it.
If that fails, you can manually browse for the OTA package.
After selecting the OTA file, the wizard will apply the update.
Reboot the device and you are on the latest firmware.
Reserved 3
I think also after update, reboot, redo the step and sideload also Magisk for keep root
Pho3nX said:
I think also after update, reboot, redo the step and sideload also Magisk for keep root
Click to expand...
Click to collapse
Yes I agree, but those tutos are for everyone, and everyone doesn't rooted his smartphone like us
So I won't confuse them
hello, thanks for the guide, when I do all the steps without any problems and reboot, it opens with the old version, where could I be doing wrong?
This will work to downgrade the phone also?
pankspoo said:
This will work to downgrade the phone also?
Click to expand...
Click to collapse
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone
sh4tteredd said:
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone
Click to expand...
Click to collapse
So we can use your Windows tool to downgrade ?
pankspoo said:
So we can use your Windows tool to downgrade ?
Click to expand...
Click to collapse
I won't downgrade this phone at all. Btw maybe I'm wrong and it can work but I'm not sure and I don't suggest to do it
Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.
demiii said:
Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.
View attachment 5716899
Click to expand...
Click to collapse
Which version of ADB Sideload do you use ?
Post 1 or Post 2
Sib64 said:
Which version of ADB Sideload do you use ?
Post 1 or Post 2
Click to expand...
Click to collapse
What I did was reboot to recovery, navigate to Apply Update via Sideload through the recovery interface and from there entered the command adb sideload filename.zip so i guess it is the method in post 2
UPDATE:
I have tried the method in Post 1 and this error shows up:
UPDATE 2:
I have tried revoking USB DEBUGGING authorization, adb kill-server, adb start-server and authorizing again
I have tried deleting adbkey and adbkey.pub files in C:Users/$Name/.android
I have tried following suggestions about solving this error both from this and this StackOverflow thread
Nothing worked for me.
You don't need to use ADB to sideload an OTA, the nothing phone contains an OTA updater In the phones os already, the only thing you need the computer for is to move the OTA to the phone
Here is what someone on the nothing discord said to do and it worked
dont sideload
Create a folder named “ota” (without the quotes) at the root of the internal storage of your phone. Then copy the update ZIP file to that folder.
Dial `*#*#682#*#* `to open up the offline update tool.
You can also use an activity launcher app to locate and execute the “OfflineOTAUpgrade” tool. The package name of the tool is com.nothing.OfflineOTAUpgradeApp.
Hi, I have just tried your method but an error window pops up:
Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?
Ky0sHiR0 said:
Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?
Click to expand...
Click to collapse
You can only upgrade not downgrade
demiii said:
Hi, I have just tried your method but an error window pops up:
View attachment 5717197
Click to expand...
Click to collapse
If you go on nothing discord and put that error maybe they can help