Develop Bugs

[TOOL] RecoverX - Recovery installer for almost all android devices

{
"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"
}
Hello world !!!
I've created a project of a new kind : The RecoverX Project
The goal of this project is to gather ALL the recoveries for ALL android devices in ONE tool which install them on the devices. RecoverX is coded in C++ thanks to QtSDK and allow to install a recovery on more than 150 different devices !!!
You just have to select your device and the recovery, click "Install" and RecoverX does the rest !!! It's that simple
This program require different prerequesties, depending of your device
- Wether you need an unlocked bootloader to flash the recovery partition (and fastboot drivers on your PC)
- Wether you need root access and usb debugging activated (if busybox is not installed, RecoverX will ask you the permission to install it).
This program have been published on XDA News : Here
Here is the list of supported devices :
Finally, a small preview
Awesome !!! Where is the download link ???
Here : http://forum.xda-developers.com/showthread.php?t=1773227​

Wow! Nice! Its original CWM or a based CWM recovery?

It's a based CWM Recovery !!! But still have some minor bugs, that's why it's written "Beta".

How can I acces CWM after installation?

Just tap the screen several time when the SE logo appear.

LEDelete said:
Just tap the screen several time when the SE logo appear.
Click to expand...
Click to collapse
I did, but doesn't work :[

Do you have "charger", "chargemon" & "recovery.tar" files into /system/bin ???

LEDelete said:
Do you have "charger", "chargemon" & "recovery.tar" files into /system/bin ???
Click to expand...
Click to collapse
no... do you have a link/tutorial for that?

Go to "settings" > "log" and click on Log. Then, plug your device and run the log and send me a PM with the log.txt file.
Thanks

Nevermind. I had root but lost it again when reflashing ICS. I'm gonna sell this phone. It is the worst phone I ever bought for hacking such a dissapointment. Thanks for your tool anyways.

turkification said:
Nevermind. I had root but lost it again when reflashing ICS. I'm gonna sell this phone. It is the worst phone I ever bought for hacking such a dissapointment. Thanks for your tool anyways.
Click to expand...
Click to collapse
Omg, how smart are you? Why didn't I think of that!
Don't use tools, use the proper hacking.
And if you were as good as hacker as you claim you are,
you'd know that's not true what you said. But it's ok.
Sell it. I hope the next owner will appreicate your loss as his/her gain.

Hey if we install CWM as this method just install in our system file. Some ROM cannot accept install with CWM like this . because it will format system partition . we have to use kernel integrated CWM

This tool is just for stock rom for people who can't or who doesn't want to unloc their bootloader.

working on XperiaS lock BL MIUI 2.7.20

Yes, it work on Xperia S but only on stock rom and not on stock rom
EDIT : stock rom

but MIUI is a custom rom

Sorry, I'm tired, the tool is only compatible with stock rom

MIUI is a custom rom but your recovery working on it, testet by me and it is workin great. Offcourse im using stock kernel.

Ok, thanks a lot !!! I prefered to said no because I was not sure about this...

LEDelete said:
Hello everyone !!!
I've created a new GUI tool for all Xperia devices (included Xperia S as BETA) to install a recovery automatically such as CWM Recovery (as BETA).
Let me present you RecoverX !!!
Here is the list of supported devices for the moment :
Xperia P (beta) (unlocked bootloader) [NEW]
You need to be rooted, busybox installed on your phone and USB Debugging activated. Finally, you need to be on 2.3 Stock ROM
Click to expand...
Click to collapse
On Xperia P is not working.
unlocked bootloader, rooted, busybox installed, USB Debugging activated - That's all there is.
Stock kernel

Lg L Manager [Win] [Unix] [L3] [L3 II] [L5] [L7]

{
"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"
}
LG L Manager​
With Crazy Mode too​
Lg L Manager is your new Pc suite for your Lg L3, L3 II, L5 and L7!!​
Features
Code:
#Supported Os:
--> Windows (Xp, Vista, 7, 8.x)
--> Unix based os (Os X too)
--> Linux distros (Ubuntu, Debian, Suse, Fedora, Linux Mint, etc..)
#Common Fetures:
-->Backup & Restore
-->Adb Shell
-->Install roms (Not fully automatized due to wipe /data)
-->Install Gapps or any mod (automatizated)
-->Install apk
-->Import Camera photos
-->Push and Pull files
-->Crazy mode
#Device Specific
-->Full Unlock (Bootloader+Recovery+Root) [L5] [L7] [L3II -> WIP]
-->Full Unlock (Recovery+Root)

Sources
Sources: https://github.com/ionolinuxnoparty/Lg-L-Manager
Branches :
Master > Windows
Master-unix > Unix and Linux
Click to expand...
Click to collapse
Download
Windows
Unix / Linux
Click to expand...
Click to collapse
Bugs
-Windows > dunno what's working and what not cuz I own no windows PCs and I wrote it with no test
-Unix > Crazy mode will make you crazy [cannot fix this]
Check commits to see if I've fixed something
Click to expand...
Click to collapse
How to run
Unix / Linux : browse into the folder where you have to place files ( ~/Lg-LManager), and run
./Start.sh 0 [Select device manually]
./Start.sh 1 [Lg L3]
./Start.sh 2 [Lg L5]
./Start.sh 3 [Lg L7]
./Start.sh 4 [Lg L3 2]
Click to expand...
Click to collapse
Windows: execute start.bat

Dev notes
Full Unlock,
it was pretty easy, everyone used stupids toolkit that may work or not. Adb and fastboot are the most useful and powerful tools.
I've changed the order to unlock device that everyone used. Why first root, then recovery and then bootloader?? Do you need the keys to change a car engine? Nope, so it's the same thing for an android device. Fist I boot a recovery to get adb root (stock kernel doesn't allow it, but a recovery automatically give adb root acces even if phone is not rooted), then I'll push file to unlock bootloader to sdcard and then unlock it. After this I flash recovery, then flash any root package. Done! And it works with any rom.
Click to expand...
Click to collapse
About Lg L3 II,
apparently this device has no bootloader to imput fastboot commands needed for the full unlock, read notes inside bat file
Click to expand...
Click to collapse
About Lg L3,
this is the only device I own of the four I support... Now there's no recovery that allow both adb shell and sideload so I've to push every file to sdcard. When there will be a recovery where both adb shell and sideload are working I'll change a few lines of code and it will be OK.
Click to expand...
Click to collapse
About Crazy Mode,
it's made for crazy users that may brik their devices and make strange things with their pc. When crazy mode is enabled there's no way to quit it and it may lag your pc like hell (until reboot) so you won't be able to do anything because you're crazy and you may destroy something.
Click to expand...
Click to collapse

Seems so good!
Well I guess I need to run su before i execute it on unix because of the permission errors I get , it will work fine I guess
If you need any help or testing for Unix , message me on Hangouts

[info] Linux on SM-T585 Samsung Galaxy TAB A6 10.1 (2016)

Hi,
Currently i am porting Linux "Ubuntu phablet" to my device Samsung Galaxy TAB A6 10.1 (2016), i have a little progress here.
Currently i was able to do following
- Recompile the kernel and enable video frame buffer
- Build init scripts and create boot.img
- Installed Ubuntu touch on system partition
- Boot to Ubuntu and enable adbd server to be able to continue.
Here you can find a video with my progress h**p://ms.serdit.ro/files/linux-boot-t585.mp4
Best regards,
Marc

Added kernel linux logo
Hi,
For days i was stuck in why those nice penguins are not shown at startup, and voila, i did it....
Here is a nice one
{
"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"
}
Best regards,
M

Hi,
Just to let you know that I have another breakthrough, an init boot menu which can,
- boot installed Linux from system partition
- Reboot in recovery
- reboot
- mount .iso or .img from sdcard and boot from them if contain any OS
Here is a demo
Best regards,
M

I have modified the kernel's fonts to have bigger fonts on text console. This gif is loading very slow....

Help Needed
Hi. I am one of the few who is interested in having linux installd on android devices (Galaxy Tab A 10.1 2016), but there is little forums about this.
I am therefore asking for your help in trying to get this to work. I am trying to install any linux distribution thats available.
As i saw in your video you had something similar to grub bootloader. Can you share it please. B ut most importantly I'd like to know how to get linux installed.
Any necessary information will be greatly accepted.
Thank you in advance and look forward to hearing from you soon.

Hi pops,
Unfortunately there is no complete linux version yet which works on this tablet, i didn't had enough time to complete my port so currently the only thing which works is the boot process of a bare linux with only command line without wifi or mobile data.
The above boot menu is actually a simple program, built by me, which loads an init scripts from desired partition based on an exit code from a loop in the initial init script. It is programmed in C and you need to know how to cross-compile on other platform apps in order to be usable, or to use it as is with precompiled menu.
Basically my linux does not have graphical interface and no peripherals yet and does not have an installable image, with a little progress on android LXC container which is up and running, but nothing tested yet.
Best regards,
Marc

Thank you very mu ch for your quick reply. I understand totally what you said. :good::good:
I believe that this is something that shouldnt be done by only one developer as it may be lots of work.
I know lots about android but not about porting or making custom roms, custom recoveries, or custom kernels. I
If you come up with anything let me know(and who ever it may concern).
Thanks so much again for your reply. :good::good:
Pops

Unfortunately I will not update any of my threads on XDA-Developers websites.
I asked them to remove all my posts and delete my account, but is seems that they did't did that yet.
I will continue to work on my projects but publish the result elsewhere.

Okay but I'd really appreciate if I can stay in the know aboit this so i will leave my contact in order for you to update me. And if you may require any help from my end that wouldn't be. problem.
Email: [email protected]
Website: http://bitly.com/popscommunications
https://popsproductions.wixsite.com/popscommunications
Pops

I will update the http://ms.serdit.ro page with any news i will have, you can check that page regularly if you want, or you can use that to ask anything.

Hi..any new updates

download linl broken

I am terribly sorry, i do not have that device anymore and discontinued the work on it long time ago.

ok, i want test it
pls give link

lentas said:
ok, i want test it
Click to expand...
Click to collapse
I don't think i have the source code of my work for this device anymore, as I changed quite a few computers since then and a lot of hard disks. However, i will have a look for them and if I will have them i will upload all of them on my GitHub repos.

ok

lentas said:
ok
Click to expand...
Click to collapse
Meanwhile you may want to review the PostmarketOS pages, it seems to have been ported to this tablet, there is a kernel source link as well

wifi is broken from that device on pmos

lentas said:
wifi is broken from that device on pmos
Click to expand...
Click to collapse
Even so, is more than i achieved, you can try to fix that.

im not a c++ coder

[ROM][8.1][TREBLE][VENDOR][ZUK_Z2_PLUS] SmartisanOS_6.6.5.4_Oreo_by_Jacques

I bring some work that I put together for my personal use but decided to make friends, credits to Art_chen and the Gsi developer so let's go.
{
"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"
}
Have installed Factory2vendor and TWRP Kuber 3.2.2 on the Google drive
Whoever is using the TWRP Who is using TWRP 3.3.0 or 3.3.1 will have to pass the TWRP 3.2.2
via FastBoot
Whoever is using the TWRP 3.2.3 Can pass the TWRP 3.2.2 via TWRP
Installation tutorial Twrp
Note Remembering if using 3.3.1 will have to pass 3.2.2 via fastboot, because via twrp it will
give problem in the partition
Have zuk z2 drivers installed correctly
Enable usb debugging, connect the device to the note or pc open the command prompt or shell and type:
adb devices
adb reboot bootloader
fastboot flash recovery -i 0x2b4c twrp-3.2.2.img
restart in recovery mode and proceed with the installation of the build
Wipe system
Wipe data
Wipe Cache
Wipe Davilk Cache
Wipe Vendor
Install the ROM's zip and wait for the restart
Note If TWRP hangs when restarting hold the Power button until forced restart
Configure the ROM until it arrives at the home
Wait for the device to cool and update Google apps
Go to settings / screen & fonts / system fonts Size / small
Go to Settings/Go to Settings/ about this Phone / system version and enable developer options
Go to Settings / advanced settings / Option Developers/disable edge error detection
This step 2 above fix the bug on the keyboard due to the invisible notch
To receive notifications in apps go to Settings / notifications center / Click on the desired
application and enable everything
Go to Phone Manager Go to Phone Manager / Permissions Manager / auto launching Permissions
manager and enable the desired application
Go to Phone Manager/Power optimization / APP battery Use Optimization / Disable the app you
want notifications to arrive
Update
Removed all Chinese and unnecessary applications from ROM
Kernel Nameless 3.18.120 R18 ( VoLte )
Thermal updated
Magisk 17.1
Added Gapps
Morecale
Geek camera
Via Browser
Link rom: https://drive.google.com/folderview?id=165NLW3bprGnwOm6Sk6mCY3xntUMU1FRZ
To all the friends who have supported me in this work
Credits
@xzr467706992
 @kubersharma
 @IMCHenxy
 @DD3Boh
 @davidevinavil

Reserved

Excelente Rom.
Another great job brother. Fluid and beautiful rom. Running smooth and unblocked Pubg. Congratulations : D:Boa:

I was tested this ROM about 3 days and I must say it's great work by @jackjt3, thanx:good:. ROM is very smooth and almost bugless, expect Bluetooth headphones issue (can't connect to device) and Nighttime mode. I hope you could fix this unpleasent moments in the next build of SmartisanOS

mellowmaniak said:
I was tested this ROM about 3 days and I must say it's great work by @jackjt3, thanx:good:. ROM is very smooth and almost bugless, expect Bluetooth headphones issue (can't connect to device) and Nighttime mode. I hope you could fix this unpleasent moments in the next build of SmartisanOS
Click to expand...
Click to collapse
Can u confirm some points
1. Is jio video call work
2. Call recoding
3. Long screenshot
4. Dual app

ershibbu said:
Can u confirm some points
1. Is jio video call work
2. Call recoding
3. Long screenshot
4. Dual app
Click to expand...
Click to collapse
1. Don't know, I don't use Jio
2. This option is exist in ROM, but I didn't check it
3. No
4. App cloner is available, in my case it offers me to clone only Telegram and it works

After flashing 3.2.2 getting fladh error and in pc mode i cant flash

Still have some Chinese apps which i don't like and this rom have future??

Wileyfox Swift adb fastboot flash failed // adb sideload failed

I purchased a nice Willeyfox Swift in very good condition with Android 7.1.2. , wanted to install LineageOS + MicroG via ADB.
OEM unlocked and USB Debugging Mode enabled, drivers installed, the device was perfectly recognized, but then problems started:
When I wanted to flash TWRP via platform-tools, „< waiting for any device >“ occured. This happened using Windows 10 as well as Mac OS (so I guess, drivers aren’t the problem).
TWRP -package is: „twrp-3.5.0_9-0-crackling,img“
{
"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"
}
Then I tried to send packages via adb sideload either directly to get a ROM started or to install Magisk in order to root the devices to install TWRP via TWRP-App.
As Android Recovery („Android Recovery
Wileyfox/Swift/crackling 7.1.2/N2G48B/eeea277114“) just offers the option „Apply update from ADB“, I tried to send LineageOS 17, CM 13.0 , CM 13.1 (both signed) and even the MoKee packages MK7.1.2 and MK8.1.0
ADB & Fastboot Version: platform-tools_r30.0.5-darwin.zip
Packages were: lineage-17.1-20210126-microG-crackling.zip
cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip
cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip
MK71.2-crackling-190228-HISTORY.zip
MK81.0-crackling-200215-HISTORY.zip
Magisk-v21.2.zip
But I always got the the same result:„E: footer is wrong"/ "E: failed to verify whole-file signature" -> "E: error 21" -> Installation aborted"
Has anybody any idea how to get TWRP into recovery in order to choose a custom ROM?
Thanks a lot for any help!

Hello,
i cannot explain why, but there is a problem installing LineageOS from Android.
You have to install Cyanogen before.
https://forum.xda-developers.com/t/...r-wileyfox-swift.4119901/page-3#post-83720397 #60

wowi63 said:
Hello,
i cannot explain why, but there is a problem installing LineageOS from Android.
You have to install Cyanogen before.
https://forum.xda-developers.com/t/...r-wileyfox-swift.4119901/page-3#post-83720397 #60
Click to expand...
Click to collapse
Hello,
thank you for your answer & tipp.
I tried
SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip
and
cm-13.0-ZNH0EAS2NH-crackling-signed-9c92ed2cde_recovery.zip
now it says:
"Warning: No file_contextsThis package is for device: crackling; this device is .
E: Error in / sideload/package.zip"
I think, that leads me at least one step further in order to look only for recovery-files.
But I don't understand the Warning - it seems, the system doesn't recognizes the device as crackling, although it's even written in the Android Recovery version?
Also, since the option is ADB update and the actual Version is Android 7.1.2, shouldn't I look for CM/ Lineage 14... instead of CM 13...? - I guess there isn't CM 14 and it says, Lineage 14 isn't supported for crackling.
How did you get the Lineage 17.1. on your Wileyfox Swift?
Thanks in advance for your answer!

Are you sure it is a Swift? There had been Swift 2 and Swift 2 Plus.
What says "About the phone"?

wowi63 said:
Are you sure it is a Swift? There had been Swift 2 and Swift 2 Plus.
What says "About the phone"?
Click to expand...
Click to collapse
It's a Swift indeed:
Model: Wileyfox Swift
Android Version 7.1.2
Kernel version: 3.10.49-g6016b4d
[email protected] #1
Strange thing is that it's printed "powerded by Cyanogen" on the box it came with, but apparently it's not:
Android Recovery
Wileyfox/Swift/crackling
7.1.2/N2G48B/eeea277114
Bootloader shows "device locked" although OEM is unlocked

The predecessor of LineageOS was CyanogenMod. Some people founded 2013 CyanogenMod Inc. and made a commercial fork named CyanogenOS. Some cellphone manufacturer like Wileyfox, BQ and OnePlus bought the OS for their phones. CyanogenMod Inc. made some weird decisions and ran out of money around 2016. Wileyfox took Android to give the customers an up to date OS (better read more in the net).
I think your fastboot attributes "device state - locked" and "secure boot - enabled" means that unlocking bootloader failed.
Attached you see the fastboot of our Swift: "OEM unlocked: true" and "security fuse: false".

This is how cyanogen fastboot should look like...
I'll be going on trying - let's see

I managed to open bootloader, now it says:
DEVICE STATE - unlocked
But still, wanting to operate adb flash: <waiting for any device>

Congratulations unlocking the bootloader!
Your next step is installing the recovery?
You do not flash it using adb but fastboot.
In general there seems to be an unstable USB-Connection. To unlock the bootloader, you needed fastboot. In the beginning, you reported: ".fastboot oem unlock: < waiting for any device >".
Maybe you try several cable and port combinations?
It is always a good idea to use " fastboot devices" and "adb devices" to see wheather the device is recognized.
I never had problems using the USB-Ports for the Swift (I had with the Poco F1).
Can you use another PC or a USB-Hub?
You use MacOS? I do not know it, i use LinuxMint. But these should be familiar.
In LinuxMint i have to be root, before using adb or fastboot.
After opening the terminal, i type " sudo sh".

After all, I managed it:
Thanks to Senior Member jwoegerbauer who reminded me not to forget the command <adb reboot bootloader> before operating fastboot flashing - that was the reason for >waiting for any device> ;-)
Thanks to you, I first installed Cyanogen after installing lineageOS.
So thank you for your help!

I'd like to close this thread