Develop Bugs

[ROM] EZbase v3.0 [25/04/2011] - odin / heimdall - Easy Full Graphical How-To

{
"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"
}
EZbase, is a fully deodexed and zipaligned pre rooted odin / heimdall image for people wanting to move from stock ROM's to custom ROM's. It used by a lot of people for a recovery image if it all goes wrong, simply flash this and you on a stock Samsung image with root and 2e recovery.
Still testing the new recovery & kernel so attached is a copy of EZbase with stock CWM Recovery, until the new recovery has been 100% tested!
Screenshots:
Main Recovery - Recovery Backup - Recovery Install - EZOdin​
Features:
Gingerbread & Froyo
Simple Recovery Menu
Added:
RomManager 3.0.xxx
TitaniumBackup 3.7.2
Notes:
Please read the EZbase How-To v2.00 - http://nfye.eu/EZbase/i9000/EZbase-2.00.pdf
Donators:
Euphoria
Thanks To:
RazvanG - 3-Button Combo Fix
Tr0jAn - Testing & Documentation Review
​

Downloads:
EZbase How-To
ROM
Gingerbread EZbase v4.0
Froyo EZbase v2.0
Other
EZOdin
Android Debug Bridge (a.k.a. adb)​

Reserved
Reserved 10 Chars

This is a Step by Step guide how to flash EZbase to your Samsung Galaxy S.​
There are lots of different ways to flash ROMs to your Samsung Galaxy S, Personally I use heimdall but thats because I use *nix. I find this one to be easiest and fastest for windows users.
If you complete this guide there the worlds your oyster, simply copy different mods/ROMs to the SD Card and flash directly from there going back to your base at any time should you need to revert back.
If you have any issues what so ever, the best place to begin is a clean EZbase flash.
NOTE: No root or anything is required, you can simply do this on a stock Samsung ROM.
Contents
What you need
Flash EZbase
Install Custom ROM
Other Information
ADB - Android Debug Bridge
Enable Debugging Mode
Mass Storage
Download Mode
Recovery Mode
3-Button Combo Fix
Warning!
There have been many reports about a problematic batch of Samsung Galaxy S phones that are not able to boot into recovery or download mode. If you are going to flash a ROM please make sure you can enter these modes before doing ANYTHING. See the 3-button combo fix if you cannot access Recovery Mode.
What you need:
EZOdin - http://nfye.eu/EZbase/i9000/EZOdin.exe
EZbase
Custom ROM (only if you wish to use a third party ROM)
- E.G. insanity - http://forum.xda-developers.com/showthread.php?t=843019
Nice to Have
Android Debug Bridge (a.k.a. adb) - http://nfye.eu/EZbase/i9000/adb.zip
Download all the EZOdin, EZbase CSC, PDA, PHONE and PIT if you do not have Samsung Kies installed, The Samsung USB Drivers will be required to. For simplicity sake place all the files into a single directory e.g. c:\toolkit\ however they can be placed where you like, hopefully in the future I might get all the requirements into an installer.
If you do not have Samsung Kies installed please install the Samsung USB Drivers and make sure your device is recognised by the OS. Once all the pre requisites have been fulfilled, then please continue to Step One or Step Two. If Samsung Kies is used please make sure you kill all Samsung Kies related services that are running (kies, tray agent, etc.)
Check that your phone has sufficient power, unplug your phone if it is plugged into USB or wall charger. Type *#0228# in to the dialler and check Voltage is at least 3800(mV).
Flash EZbase
Repartition is not mandatory, but it does not hurt to repartition the phone.
Start Phone in Download Mode (No Cable Attached)
Open EZOdin.
- Check Re-Partition
- Select EZbase.pit as PIT
- Select EZbase-PDA-XWJS3.tar.md5 as PDA
- Select EZbase-PHONE-XXJVE.tar.md5 as PHONE
- Select EZbase-CSC-XXJV1.tar.md5 as CSC
Connect Phone with USB Cable - Once ID:COM is yellow you are safe to continue.
Select Start
Complete, now wait for your phone to fully start-up before you continue with anything.
Install Custom ROM
Copy the ROM onto the Internal SD Card. This can be done via adb or placing your phone in USB debug mode and mounting the USB as storage.
Reboot the phone in recovery mode
Select "Install ZIP File"
Select "choose zip from sdcard"
Select "insanity-0.x.x.zip"
Select "Yes - Install"
Wait a while it installs the new ROM.
Select "Reboot Phone"
NOTE: As this is a de-odex`d ROM, First boot will take some time.
Other Information
ADB - Android Debug Bridge
To use the Android Debug Bridge you need to enable Debugging Mode first. Once enabled you will be able to use ADB and do a number of things.
Enable Debugging Mode
Press "Menu"
Select "Settings"
Select "Applications"
Select "Development"
Check "USB debugging"
Select "Yes"
Connect the phone to the USB cable and plug the other end directly into the PC.
NOTE: The computer should start installing the necessary ADB drivers. A total of three devices will be installed (Samsung Android Composite ADB Interface, Samsung Android USB Modem, Samsung USB Composite Device.
You should also now see two icons in the notification area.
Mass Storage
It is possible to mount the internal SD and microSD card as storage on your local pc, this is useful if you do not wish to use adb to copy files around.
If you wish to use your device as Mass Storage:
Pull down the notification area
Select "USB connected"
Select "Connect USB storage"
You should now be able to see your device in explorer
You should always safely eject the storage
Select "Turn Off"
Download Mode
To enter download mode, you hold the Volume Down + Home + Power. See image bellow:
Recovery Mode
To enter download mode, you hold the Volume Up + Home + Power See image bellow:
3-Button Combo Fix
You will need the following:
adb
root
xvi32 - http://nfye.eu/EZbase/i9000/xvi32.exe
P-SBL.tar.md5 - http://nfye.eu/EZbase/i9000/P-SBL.tar.md5
How To Check is Phone is Compatible:
adb shell
$ su (a superuser request will be displayed on the phone screen, accept it).
# dd if=/dev/block/bml1 of=/sdcard/bml1.dump
# exit
C:\adb pull /sdcard/bml1.dump
Open the bml1.dump file with XVI32.
- Search (in ASCII Mode) for OFNI.
If the block reads "[email protected]" just follow the tutorial below, as it is safe to fix.
NOTE: If it reads "x0" then STOP as this FiX will BRICK your phone if applied.
Open EZOdin
- Select the "P-SBL.tar.md5" as PDA file.
- Check "Bootloader Update"
Connect Phone with USB Cable and place phone in download mode (ADB method)
Once "ID:COM" is yellow you are safe to continue.
Select "Start"
NOTE: It should take three seconds to complete. After the update phone will reboot automatically. Do this at your own risk!

Reserved
Reserved Number 2

I was looking for this. Thanks. Will try insanity after this.
Darky's 9.3|Voodoo 5.4.1|ZSJPE|Lagfix OFF

Thanks again nitr8, I will use this on your next update of Insanity rom...
Nice

Great stuff - used EZBase earlier before flashing Insanity 0.6.6.
Like rixsta will use this method before future Rom flashes
Sent from my GT-I9000 using XDA Premium App

Thank you nitr8 =]

As always if you need any help man give me a call

Is this EZOdin safe/tested?
How is it different than the original (besides the UI, ofc)?

RayearthX said:
Is this EZOdin safe/tested?
How is it different than the original (besides the UI, ofc)?
Click to expand...
Click to collapse
Do you think I would release this untested? Yes its been tested, its STOCK Odin, with a revamped UI.

nitr8 said:
Do you think I would release this untested? Yes its been tested, its STOCK Odin, with a revamped UI.
Click to expand...
Click to collapse
YES! You could release it just for testing purposes
Just wanted to be sure.

RayearthX said:
YES! You could release it just for testing purposes
Just wanted to be sure.
Click to expand...
Click to collapse
it is check out post2

Nice you're pulling this up now!
I wondered, why you didn't release this.
Cheers,
Joël
Sent from my GT-I9000 using XDA Premium App

Darkyy said:
Nice you're pulling this up now!
I wondered, why you didn't release this.
Cheers,
Joël
Click to expand...
Click to collapse
It was ready a while back, we was about to do it and then a new firware came out and it got put on the back burner
My phone was on 6.6 but as it needed testing I redid it as per the written instructions just so we knew it worked 100%
IF people follow the guide then they SHOULD get a 100% working insanity rom with no hassle.. (we live in hope )
TrOjAn

Thanks for this, it's a nice initiative. I've been doing the same, just with different files from samfirmwares + I've needed to install a kernel to get easy access to root + cwm so this lets me skip that part
One thing though, you might want to either put this in your guide, or alternatively modify the app, but that Odin you have is version 1.7.. which has given me trouble (Windows 7, 32bit) in the past. Odin 1.82 works fine so just as a tip for people who might have problems getting odin to work
Aside from that this is a great idea!

akselic said:
One thing though, you might want to either put this in your guide, or alternatively modify the app, but that Odin you have is version 1.7.. which has given me trouble (Windows 7, 32bit) in the past. Odin 1.82 works fine so just as a tip for people who might have problems getting odin to work
Aside from that this is a great idea!
Click to expand...
Click to collapse
Hmm.. strange, Im on 1.7 Windows 7 32bit and I have not seen any issues.
What sort of issues have you had??
TrOjAn

TrOjAnUK said:
Hmm.. strange, Im on 1.7 Windows 7 32bit and I have not seen any issues.
What sort of issues have you had??
TrOjAn
Click to expand...
Click to collapse
odin either not connecting or just standing there doing nothing, never found out why but after using 1.82 its worked fine so I never felt like going back
and your files work with the standard odin anyway so it's not a big deal

akselic said:
odin either not connecting or just standing there doing nothing, never found out why but after using 1.82 its worked fine so I never felt like going back
and your files work with the standard odin anyway so it's not a big deal
Click to expand...
Click to collapse
Yes I have has similar like that happen as it goes, re installing the drivers normally fixed it
Anyway, glad you like it.. hopefully more will find the benifits of EZBase
TrOjAn

[GUIDE] How to Unroot Back to Completely Stock with No Root/Superuser!

For those of you who need to unroot your Epic 4G Touch back to "completely" stock with no root whatsoever, here's a step-by-step guide.
*note - if you are not on a rooted stock ROM, you will need to restore your phone to a rooted stock ROM first, you can get a copy of rooted stock ROM here if you forgot to make a backup.
Step by step tutorial for beginners:
Step 1. First, put your Epic 4G Touch into download mode by holding down both Power button and Volume Up button together. Then connect a USB cable from your phone to your computer.
{
"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"
}
Step 2. Open up ODIN. You should have this program already when you rooted your phone but if you don't download ODIN here:
Download ODIN v.1.85
Step 3. You should see a yellow COM: show up in ODIN, the number doesn't matter so long as it shows up like in above screenshot. If it's not showing, you need to install Samsung Kies. (Download Kies here)
Step 4. Download acs-eg30-stock-kernel-pulled.tar at ACS site under Downloads.
Choose "PDA" then choose this file you downloaded, acs-eg30-stock-kernel-pulled.tar.
Step 5. Hit Start and your phone should reboot with stock boot logo.
For Linux and Mac users, you can use Heimdall instead of ODIN, use the same tool but flash this stock recovery acs-eg30-stock-kernel-pulled.tar instead of rooted kernel.
Step 6. Now, you should have a fully stock rooted Epic 4G Touch. At this point, you should still have your apps/personal data. If you just want stock rooted Epic 4G Touch, you can stop here. Otherwise go to Step 7.
Step 7. If you want to completely unroot your Epic 4G Touch, you will need to erase root and Superuser app files. To do this, you can use ADB or Terminal Emulator app. If you are using Terminal Emulator app, skip to Step 10.
Download ADB.zip here if you don't have it already (works for Windows, Linux, and Mac):
Download ADB.zip
Unzip(uncompress) ADB.zip into your hard drive, I prefer C:\adb (for Windows).
Step 8. Browse to the directory of your ADB files by typing:
For Windows:
Code:
cd \adb
For Mac & Linux:
Code:
cd /adb
Step 9. Get into ADB shell, type:
For Windows:
Code:
adb shell
For Mac:
Code:
./adb-mac shell
For Linux:
Code:
./adb-linux shell
Step 10. Type the following commands to erase rooting and Superuser files:
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/xbin/su
rm/system/bin/su
rm /system/app/Superuser.apk
reboot
Step 11. Your Epic 4G Touch will reboot and you can double-check now that Superuser app is gone plus rooted apps are not working any more.
Step 12. Lastly, if you want to erase all your personal data and apps for returning to Sprint warranty, you can get into stock recovery by holding down both Volume up and Power button together for about 10 seconds.
Step 13. Choose wipe data/factory reset using Volume keys then hit Power button.
Step 14. Choose "Yes -- delete all user data" using Volume buttons and hit the Home button.
Step 15. Reboot your Epic 4G Touch and you should have the same exact phone you got the day you bought it.
Step 16. And also, make sure to connect your Epic 4G Touch as a disk drive and erase your personal files.
*****Credits*****
HUGE thanks to Bubby323 for pulling stock kernel! - hit up Bubby323's "Donate to me" button here

You are awesome and I love you
.: sent from my Samsung Galaxy S II Epic 4G Touch :.

When I go to stock recovery (step 12) to wipe data, I can use the volume to move up and down, but it won't actually let me select anything with my power button.
It also says:
E: update file is backed up: Reportedted
# MANUAL MODE #
-- Updating application...
Installing apks.
Successfully updated application
Click to expand...
Click to collapse
Also, I did everything else, and my about phone still reports Build number: StarBurst ROM v1.1
how do i fix this? I need to return the phone today

I have a custom Rom on here now.I do I get the original shipped Rom with this as well. The downloadable copies give me an error as if they are not signed

JoeBruin32 said:
When I go to stock recovery (step 12) to wipe data, I can use the volume to move up and down, but it won't actually let me select anything with my power button.
It also says:
Also, I did everything else, and my about phone still reports Build number: StarBurst ROM v1.1
how do i fix this? I need to return the phone today
Click to expand...
Click to collapse
This guide doesn't really show you how to go completely back to stock, it's really a restore stock kernel + remove super user and wipe data if necessary guide...

adma84 said:
This guide doesn't really show you how to go completely back to stock, it's really a restore stock kernel + remove super user and wipe data if necessary guide...
Click to expand...
Click to collapse
crap crap crap, I think the only way is if I have a nandroid backup before I installed a rom, but I don't think I have one anymore arhgajrhgajrh
is it possible to get someone else's nandroid and restore, also why won't stock recovery function for me? (see above)
nm stock recovery uses home button instead of power button

JoeBruin32 said:
crap crap crap, I think the only way is if I have a nandroid backup before I installed a rom, but I don't think I have one anymore arhgajrhgajrh
is it possible to get someone else's nandroid and restore, also why won't stock recovery function for me? (see above)
nm stock recovery uses home button instead of power button
Click to expand...
Click to collapse
See here:
http://forum.xda-developers.com/showthread.php?t=1272186

athlet1c said:
I have a custom Rom on here now.I do I get the original shipped Rom with this as well. The downloadable copies give me an error as if they are not signed
Click to expand...
Click to collapse
restore your rooted stock rom or this first in clockworkmod recovery: http://forum.xda-developers.com/showthread.php?t=1272186
then rest of instructions on this thread will get u back to stock day one.

zedomax said:
restore your rooted stock rom or this first in clockworkmod recovery: http://forum.xda-developers.com/showthread.php?t=1272186
then rest of instructions on this thread will get u back to stock day one.
Click to expand...
Click to collapse
THANK YOU!

I Appreciate that BRah

I only wish the download was faster! hah, I have like an hour to get this done today and the download is taking 25 minutes

I was thinking the same thing

I was never able to get the stock kernel to boot after flashing that backup. It would just sit on the splash screen, but not the shipped splash screen.

I can't get the stock rom zip zedo linked to to install. it says installing update, then installation aborted.. guess I'm stuck with this phone

Joe you have to unzip it, copy the Boot , cache and other files then place them in in the Clockwork/backup folder . Originally I did not have a folder , so i went in to there and made a backup and replaced teh contents with those from this one

JoeBruin32 said:
I can't get the stock rom zip zedo linked to to install. it says installing update, then installation aborted.. guess I'm stuck with this phone
Click to expand...
Click to collapse
Did you use the restore function? Not zip from sdcard!!!
You need to unzip the zip file then copy the folder into clockwork/backup folder in your internal storage then do this:

ZedoMax I would like to thank you for your contribution to the community. Your doing an excellent job , by the way. I Hope that other stuff blows over. Coming from the Evo community, this is a small venue. the Devs work well together

okay i put the folder in clockwork/backup (therefore clockwork/backup/zedomaxbackup) and now it says couldn't open directory, no files found. Tried also just putting the contents of the zip into the backup folder and same message. Now I'm creating a backup and seeing if that helps "set the stage" for me to insert this backup. Hope it works, got like 5 minutes to get to the store

That is what I did as well..... I used a stock kernel , but it put me in a loop

directory should be /clockworkmod/backup not clockwork/backup!
ugh, also in bootloop -- probably bc forgot to wipe dalvik and cache?

[Q] Wiped OS need help to sideload zip file

I just messed up big time.
I have been rooted for a couple of months now and played around with a couple of roms. I noticed my free storage shrinking when there apparently should have been nothing on my Nexus 7 except for the system files. What I did was delete my system,storage and cache with Clockworkmod Recovery leaving me with a blank tablet. Unfortunately now I can't install any zip from my sdcard as there is just emptiness on my tablet meaning I have no OS. I had initially thought I would be able to just install the OS from my usb stick but I couldn't find any way to mount my usb stick in recovery mode and I have reason to believe it just isn't possible.
As far as my research has taught me the only way to install a OS now is via sideloading it. I have spent like 2 hours reading through several threads and various other sites how to sideload a zip file onto my tablet but I'm having trouble with that. I downloaded ADB tools and I looked into this thread: http://forum.xda-developers.com/showthread.php?t=2380913
My current state is that I am in recovery mode and selected 'install zip from sideload' I have ADB tools and the OS but can't sideload it onto my tablet. When I use the command 'adb devices' my N7 is not listed. When I go to device manager the N7 is listed but there is also a warning sign displayed.
{
"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"
}
I desperately need help to resolve this issue, I love my Nexus 7 and can't bear the thought of having bricked it for good because of my own stupidity.
Much thanks in advance.
P.S. It is already late at night in Germany so I won't answer in the next few hours.

I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images here:
http://developers.google.com/android/nexus/images
Pick nakasi or nakasig depending on whether you have wifi or mobile version

You need to install this to use ADB while in recovery. You can use fastboot to flash the stock ROM.

sfhub said:
I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images
Click to expand...
Click to collapse
I'm sorry I wasn't aware of this being the wrong sub-forum.
Thanks for your submitted fix, it sounds very simple yet I don't know how to perform it. Do you mean I have to select 'Restart bootloader' on my N7?
How do I then get the factory image onto my tablet?

I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.

sfhub said:
I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery. He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.

sfhub said:
...
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
Username invalid said:
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery.
Click to expand...
Click to collapse
That's why I suggested he follow your post to install the naked drivers if he wanted to use adb sideload in recovery instead of using fastboot and the images.
Username invalid said:
He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.
Click to expand...
Click to collapse
According to the OP for naked drivers, he suggests removing old drivers. I just relayed what was in that post.
1wayjonny said:
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Click to expand...
Click to collapse

merchants oicedBri
Update:
Thanks for your helpful answers, I figured it out now.

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"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"
}
It has LINUX/UNIX and MAC support!
​
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: ​Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.1 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
​
Download links: ​Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
​
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.​
Known bugs/limitations: ​ - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)​
Changelog: ​
Check the changelog for each release here.
​
Tutorials/FAQ: ​
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload​
Sources: ​The official and original repository can be found here.​
Bug reports/Feature requests: ​If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.​
Licensing: ​Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.​
Tech and stuff: ​Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.​
Donations: ​Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
​
Disclaimer:​I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.​Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!

I tried to make a backup but it kept on giving an error; oups something went wrong, could not open *path to backup*.
I thought it may be a permission issue, so checked the app had full permissions and granted it admin access too, still didn't work sadly. This is all using Windows 10 x64.

Dodgexander said:
I tried to make a backup but it kept on giving an error; oups something went wrong, could not open *path to backup*.
I thought it may be a permission issue, so checked the app had full permissions and granted it admin access too, still didn't work sadly. This is all using Windows 10 x64.
Click to expand...
Click to collapse
It's a bug of the platform tools used in the package, the latest version of platform-tools should work. I will try to update it today.
Edit: Fixed in 1.3.1

New update with some fixes that should have been implemented a long time ago...
- Fixed Sideload flashing
- Enabled Recovery rebooting
- Fixed open folder for Stock menu

[TWRP] [CORRECTION] [NORA] 64 bit TWRP for Moto E5

{
"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"
}
Introduction
I'm not a developer. After 4 days of messing with files I made this using AIK (Android Image Kitchen). It include files from different TWRPs. The theme is not mine. I provided all credits below.
As you guys know, our 64 bit TWRP from this thread is usable, but has some major bugs. Specially the touchscreen doesn't work & it's too big to flash. Now, here is a fixed twrp, no need to hassle with OTG & adb anymore!
Installation
Command-
fastboot flash recovery <filename>.img
Booting into TWRP-
- Power off
- Volume down + Power
- Keep pressing volume down until Recovery mode option comes
- Press power
Or,
Command-
adb reboot recovery
Install magisk.zip to avoid twrp being replaced by the stock recovery
Decryption
- Format data
- Install Disable_Dm-Verity_ForceEncrypt.zip
My works
I didn't know these steps from the beginning. I had to discover these. After 30-40 attempts & making 7 versions, the final result came out. To make the thread "To the point" here is what I did for the final one-
Touchscreen Fix :
- Extracted the old TWRP and started modifying it.
- Extracted plus-linux kernel, took "kernel image" & "kernel offset" from there. Inside TWRP, replaced kernel image & kernel offset with these new files. Touchscreen got fixed.
Minimal size :
The TWRP file must be 16 MB or less to be flashable for moto e5. This is because the device has very low recovery partition size. Making a 64 bit TWRP v3.7 under 16 MB was almost an impossible task. Here is how I finally did it-
- Removed txt files.
- Replaced /ramdisk/sbin/ folder with the sbin folder of official TWRP for Asus Nexus 7 2012 3G. This greatly reduced the file size & also made the TWRP v3.7. This happened because that TWRP is 32 bit. Means I used sbin from a 32 bit recovery. But our TWRP didn't become 32 bit because "bit" depends on split_image folder (specially kernel image file inside it)- not sbin folder. After this step, the twrp became 15.1 MB !
- Because of the previous step, a bug came where the cursor was always showing on the middle of the screen even though I was not using mouse via OTG. So I replaced cursor.png with a completely transparent image. So now, the cursor is hidden. And also you won't see cursor while using mouse. But no one need that, as touchscreen is fixed.
- Replaced files inside /ramdisk/twres/ with the files I got by extracting flashable zip of SHADOW"S BLACK THEME. We had a useless font that took almost 4 MB in our old TWRP. After doing the step, got the same font in 100 kb. But the overall file size increased because of new images in /ramdisk/twres/images folder. These images makes the recovery look better. After all, the size became 15.4 mb.
The steps look pretty much easier. But I had to suffer 3 days to discover them. I can briefly say that I ported a 32 bit twrp, used sbin from 8 TWRPs, tried to port 64 bit, removed languages and fonts, removed files from sbin folder, repacked & booted image every time after making every single changes, compressed images using online tools and many more !
I shared all these in case anyone finds them useful.
Bugs
- Adb push / pull (Sideload works though)
- Terminal
NB. Use adb version (boot only) to use adb features like push/pull & inbuilt terminal.
- MTP (Read File Transfer part)
File Transfer
MTP works fine. If you aren't able to use mtp & adb (in adb version), the problem is related to drivers. Here is the fix for windows (Sorry for linux / mac)-
1. Download Drivers.zip.
2. While in twrp, connect it with computer.
3. Go to device manager & uninstall devices related to adb - mtp. Adb device can be under "universal serial bus devices".
4. Disconnect the mobile.
5. In Device Manager, click on view & select "show hidden devices".
6. Again, Uninstall all drivers/devices related to adb - mtp.
7. Re-connect the mobile.
If windows doesn't install the drivers / the installed driver doesn't work, uninstall those and install working drivers manually-
How to install the drivers?
Install automatically- Run the exe file
Install manually (Recommended) - Device manager > Right click on the device > Update driver > Browse my computer >Let me pick > Have disk > Browse > Select the appropiate .inf file provided in each folder.
If you can't see mtp device under portable devices, try running the mtp driver exe file & reconnecting. However, adb fix is guaranteed. Good luck for MTP!
Download
adb version (boot only) - Drive / Mega
v2.1- Drive / Mega
v2.1 (stock)- Drive / Mega
v2- Drive / Mega
v1- Drive / Mega
Drivers.zip- Drive / Mega
Disable dm verity force encrypt
Credits & Links
Theme
Old TWRP
Kernel
Porting Guide
Disable dm verity & force encrypt
TeamWin Official
Android Image Kitchen

Changelog
Version 2.1
- Removed "Install twrp app" screen
Version 2
- Fixed empty area in Advanced options
- Fixed stock theme version error
- Fixed override font error
- Fixed all string resource errors
- Removed all other languages rather than English (Other languages have font problems. And I can't add more fonts because of limited partition size)

Any plans for further updates?
If yes may I suggest the following:
1. Be able retain settings (ex. The prompt to install the twrp app, even if turned off, at next use it still prompts)
2. Use graphics resources of plain twrp, at least with keyboard and navbar, better with everything though.

kenshinta said:
Any plans for further updates?
If yes may I suggest the following:
1. Be able retain settings (ex. The prompt to install the twrp app, even if turned off, at next use it still prompts)
2. Use graphics resources of plain twrp, at least with keyboard and navbar, better with everything though.
Click to expand...
Click to collapse
Actually I had to reset my whole computer & lost all my works. I made a list of best working gsi builds for both stock & custom rom. The gsis over stock rom didn't have graphics issues. And I also created other recoveries such as orange fox, Pitch black which were large to flash though. But I lost all of these
I will try to remove that prompt.
And will make a stock theme variant as well. Thanks

Stock theme variant added.

can't boot 64bit lineage 16
https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img.xz/download

basiotte said:
can't boot 64bit lineage 16
https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img.xz/download
Click to expand...
Click to collapse
That's gsi rom bro. They are not guaranteed to work