{
"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
Java was a better solution I think it's cross platform
Yes but java is very complex and I don't like the design (don't blame me lol). And QtSdk is also cross platform but my program needs specifics windows libraries.
hey man i have a question! i have a galaxy nexus gsm with root, but i rooted without unlocking the bootloader..but then i decided to unlock the bootloader but using an app call bootunlock..can i use this tool to install cmw touch recovery on my nexus? or do i need to unlock my bootloader, let's say the way it has to be", and root my phone using the gnex toolkit?.. im gonna wait for your replay before i install the recovery
seleu said:
hey man i have a question! i have a galaxy nexus gsm with root, but i rooted without unlocking the bootloader..but then i decided to unlock the bootloader but using an app call bootunlock..can i use this tool to install cmw touch recovery on my nexus? or do i need to unlock my bootloader, let's say the way it has to be", and root my phone using the gnex toolkit?.. im gonna wait for your replay before i install the recovery
Click to expand...
Click to collapse
you can root without unlocking bootloader but you need to unlock it to flash recovery..
k786 said:
you can root without unlocking bootloader but you need to unlock it to flash recovery..
Click to expand...
Click to collapse
so you're telling me that i don't really have the bootloader unlock? even if i used that app, bootunlocker? because it says i have the bootloader unlock, and when i turn on my phone, under the google logo now shows up an open padlock, and i think that means i have the bootloader unlocked
seleu said:
so you're telling me that i don't really have the bootloader unlock? even if i used that app, bootunlocker? because it says i have the bootloader unlock, and when i turn on my phone, under the google logo now shows up an open padlock, and i think that means i have the bootloader unlocked
Click to expand...
Click to collapse
i thought you decided to use the app now but...if you unlocked your gnex using that app an dif you have the open padlock under the google logo then you are unlocked and can use this tool to flash recovery on your device
k786 said:
i thought you decided to use the app now but...if you unlocked your gnex using that app an dif you have the open padlock under the google logo then you are unlocked and can use this tool to flash recovery on your device
Click to expand...
Click to collapse
so everythings cool? i can install the recovery without any problem?
seleu said:
so everythings cool? i can install the recovery without any problem?
Click to expand...
Click to collapse
yes
k786 said:
yes
Click to expand...
Click to collapse
well it doesn't work at all, the tool says it has been installed correctly, but when i try to enter recovery mode (first entering fastboot mode, then selecting recovery mode) it doesn't do anything, it shows up and android with open chest and a red error sign..what did i did wrong? does that means i don't really have the bootloader unlocked?
seleu said:
well it doesn't work at all, the tool says it has been installed correctly, but when i try to enter recovery mode (first entering fastboot mode, then selecting recovery mode) it doesn't do anything, it shows up and android with open chest and a red error sign..what did i did wrong? does that means i don't really have the bootloader unlocked?
Click to expand...
Click to collapse
the red chest android is stock recovery, looks like the recovery-from-boot.p file is still there which overrides your cwm and brings it back to stock..to make cwm permanent, you need to delete or rename recovery-from-boot.p file located in /system folder using a file manager and then re-flash recovery
k786 said:
the red chest android is stock recovery, looks like the recovery-from-boot.p file is still there which overrides your cwm and brings it back to stock..to make cwm permanent, you need to delete or rename recovery-from-boot.p file located in /system folder using a file manager and then re-flash recovery
Click to expand...
Click to collapse
and what you recommend? delete or rename?..i allways wonder why that android with red errors always shows up everytime i try to enter recovery, because i flash the regular recovery via rom manager, and it works fine, but everytime i have to flash it to enter recovery because it give me that error, and i didn'd know why until now, so thank you
seleu said:
and what you recommend? delete or rename?..i allways wonder why that android with red errors always shows up everytime i try to enter recovery, because i flash the regular recovery via rom manager, and it works fine, but everytime i have to flash it to enter recovery because it give me that error, and i didn'd know why until now, so thank you
Click to expand...
Click to collapse
your choice..
k786 said:
your choice..
Click to expand...
Click to collapse
now it works thanks!..but one last question..when i enter recovery and i hit the button reboot system now, to turn on my device, it shows some kind of warning thats says "ROM may flash stock recovery on boot. fix? THIS CAN NOT BE UNDONE." and i can choose "no, yes, disable recovery flash, and o back"..wich option do i have to choose?
seleu said:
now it works thanks!..but one last question..when i enter recovery and i hit the button reboot system now, to turn on my device, it shows some kind of warning thats says "ROM may flash stock recovery on boot. fix? THIS CAN NOT BE UNDONE." and i can choose "no, yes, disable recovery flash, and o back"..wich option do i have to choose?
Click to expand...
Click to collapse
just click yes..
Are you sure you have fastboot drivers for your device correctly installed on your PC ??? Because 80 % of people who said that the tool doesn't work didn't have installed these drivers.
If it is not the case, please, use the Gnex Toolkit to install the drivers on your PC then, try to install the recovery.
LEDelete said:
Are you sure you have fastboot drivers for your device correctly installed on your PC ??? Because 80 % of people who said that the tool doesn't work didn't have installed these drivers.
If it is not the case, please, use the Gnex Toolkit to install the drivers on your PC then, try to install the recovery.
Click to expand...
Click to collapse
it worked for him..
If it worked, the problem is solved
This thread has been closed as it is a clone of the original which is against xda rules (spam).
If you wish to post please use the following thread:
http://forum.xda-developers.com/showthread.php?t=1773227
Mark.
Related
View attachment primoc_boot_unsecure.imgPlease excuse my absence. I will not be watching this thread for the time being. Hopefully if you have any questions, they can be answered by using the search option or someone else with this device that happens to check this thread will be kind enough to help.
!#I'M BACK#!
soon enough we won't need this thread, because we will all be able to RUU lol-Dec 6, 2013
beaups said:
posted on rumrunner.us. should work for both primou and primoc. Note, it is highly recommended (mandatory?) to be on a normal sense-based ICS rom and using an unsecure (preferably stock based) kernel. If you get poor results with other configurations, don't bother asking for help please!
Click to expand...
Click to collapse
S-OFF is here rumrunner.us
Huge thanks to beaups
This rom is probably most compatible with rumrunner
The boot.img inside is unsecure so flash away and GO GET S-OFFED!!!
Here's the unsecure boot.img that I used to achieve s-off.
View attachment primoc_boot_unsecure.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"
}
Added init.d support
Added Root Permissions with Chainfire's SuperSu
This ROM was cooked with dsixda's Android Kitchen
Thank you and credit goes out to the both of them.
CLICK HERE TO DOWNLOAD
I have posted this ROM for safetynet/fall-back purposes.
I've noticed fellas posting please help, I forgot/didn't make a backup.
This is for you. Worried and maybe even a little scared that your phone is now a beautiful paper weight.
This ROM is completely stock with added init.d support and root.
It is still odexed, and with stock kernel.( I'm still learning/attempting to build one with extra governors and over clocking abilities ).
Instructions below....
1. Unlock your Bootloader by following the instructions at htcdev
1a. If you've succesfully unlocked your Bootloader, that means you have your fastboot files on your PC and know in general how to use them.
2. Download an openrecovery of your choice. I personally use TeamWinRecoveryProject 2.2.0 without any issues at all. (See the attached File)
3. Place the recovery.img that you have chosen into your fastboot folder.
3a. Change the name of the .img to recovery.img (just easier that way when sending the flash command)
4. Now open a terminal while in the fastboot folder.
4a. On Windows- hold shift+right click the mouse then click open command terminal here.
4b. On Ubuntu- CTRL+ALT+T to open a terninal then cd fastboot.
5.fastboot flash recovery recovery.img
5a. ^^^^^ Type this into the terminal. ^^^^^
5b. You now have a custom/openrecovery.
6. After the recovery.img is flashed, reboot your Bootloader.
6a. fastboot reboot-bootloader
7. After booted back into bootloader, use your volume-down button to highlight Recovery.
Now press your Power button to select it.
7a. Now your are in Recovery!
8. Click Wipe, then Cashe, then Dalvick, then Factory Rest, then System.
8a. This will wipe all of your phone nice and clean for a fresh install.
9. Click Home, then Install, and find the ROM.zip, click it, then install. Let it finish installing the click Wipe Cashe/Dalvick.
10. Navigate back to the Home screen and click Reboot, then Bootloader
10a. I hope you have a copy of the ROM.zip on your PC.
11. Open the ROM.zip and copy/extract the boot.img from inside it and place it in your fastboot folder.
12. Open a terminal once again.
13.fastboot flash boot boot.img
13a. Let it finish.
14. fastboot reboot
15. Enjoy.
These instructions are for use with TWRP (TeamWinRecoveryProject) They may be different using CWMrecovery (ClockWorkMod).
I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here
lostboybinns said:
I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here
Click to expand...
Click to collapse
u flashed shpongle? that means u are GSM not CDMA so this ROM just simply won't work
as for returning to stock, u can always flash a sense kernel duh
This is for primoc CDMA Virgin Mobile
I just downloaded and flashed to test, everything is working....Just like stock
This should allow me to update my PRL, right?
YUP!
Turns out it was a network fluke?
wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...
russellvone said:
Turns out it was a network fluke?
Click to expand...
Click to collapse
What was a network fluke?
I'll cross reference the updater-script to another one I've used on a different Rom I cooked and have been running for over two weeks..... See if there are any differences between the two.
lilrob1213 said:
What was a network fluke?
Click to expand...
Click to collapse
I was replying to zombiegirl's question about updating her/his PRL
Matt_the_Geek said:
wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...
Click to expand...
Click to collapse
Ok I found a difference in the updater-script, the update binaries are identical so that shouldn't be the issue. Problem I have is that I don't have a working computer to fix the updater-script. It won't be until June 26th that I can apply it. Sorry for the inconvenience.
P.S. are you flashing with TWRP?
Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.
Matt_the_Geek said:
Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.
Click to expand...
Click to collapse
If you downgrade TWRP to 2.3 you should be fine.
Sent from my One V using xda premium
ah, I'm on 2.5, so I'll look into that...
did the downgrade to TWRP 2.3.0.0, still the only thing i can install is Rhythimc Rom, everything else fails to install... unless i just got some really crappy downloads, so i'm off to try to dl the roms again...
Actually, instead I swapped out recoveries for CWM. aaaand it worked.
Link To Main Thread
{
"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"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
Reserved.
Reserved.
Thank you so much.
Just used this tool to unlock bootloader (I had my token from before so didn't use your tool to gain token) and root my phone. It was very simple indeed.
Keep up the good work.
Major update to version 2.0! Check it out and give some feedback on the new design! :highfive:
Is it support Windows 8?
Sent from my HTC One X Viper x 3.8.0 Final using XDA Premium app
sifatrhmn said:
Is it support Windows 8?
Sent from my HTC One X Viper x 3.8.0 Final using XDA Premium app
Click to expand...
Click to collapse
It's designed to look like Windows 8, and was built on a computer running Windows 8, so it better support Windows 8!
Version 2.1 Now Out!
The toolkit has now been updated to Version 2.1! Lots of new features and fixed bugs, so check it out let me know what you think! :highfive:
EDIT: Aaaaand, something major came up. I may have to redesign a function, so the update may be a few more days. Sorry everyone!
Looks great, will try next time :thumbup:
Sent from my HTC One X using xda premium
Version 2.1 is back online now! I had to redesign a few functions on the Setup page, and took some of that extra time to add even more features to it as well! Hope you all enjoy it! :laugh::good::highfive:
hi! it might confuse to others. maybe you should edit the numbering in the next update. if you can see no.3 is flash kernel and rom while no.4 is gain root.
robchongke said:
hi! it might confuse to others. maybe you should edit the numbering in the next update. if you can see no.3 is flash kernel and rom while no.4 is gain root.
Click to expand...
Click to collapse
I believe the numbering is correct, as you need to flash a working ROM and Kernel before you can gain root on your phone.
WindyCityRockr said:
I believe the numbering is correct, as you need to flash a working ROM and Kernel before you can gain root on your phone.
Click to expand...
Click to collapse
yes. what i'm trying to say is for example, if a first timer follow the numbering and after he/she flashed custom recovery and want to flash a custom rom or custom kernel it wont flash because the phone is not yet rooted. well that's just me.
A bit of help please
I have used this tool kit this morning. flashed custom recovery. CWM. Done a back up. Loaded Viper ROM to SD card. Loaded ROM ok.
I am stuck on the HTC screen.
I erased cache, flashed boot img, erased cache again. wiped all data, reloaded ROM, and I am trying it again.
But in your all in one tool kit it says at the top
error; device not recongised, but it still says it has flashed the boot img and erased the cache.
Any help greatly appreciated.
Thanks
melhookv12 said:
I have used this tool kit this morning. flashed custom recovery. CWM. Done a back up. Loaded Viper ROM to SD card. Loaded ROM ok.
I am stuck on the HTC screen.
I erased cache, flashed boot img, erased cache again. wiped all data, reloaded ROM, and I am trying it again.
But in your all in one tool kit it says at the top
error; device not recongised, but it still says it has flashed the boot img and erased the cache.
Any help greatly appreciated.
Thanks
Click to expand...
Click to collapse
You have to make sure your phone is in Fastboot mode. To do that, go to the GroupBox on the right side labeled "Reboot" and choose the "Bootloader" button. Once your phone has rebooted successfully, you should be able to correctly flash the boot.img and erase the cache.
WindyCityRockr said:
You have to make sure your phone is in Fastboot mode. To do that, go to the GroupBox on the right side labeled "Reboot" and choose the "Bootloader" button. Once your phone has rebooted successfully, you should be able to correctly flash the boot.img and erase the cache.
Click to expand...
Click to collapse
I've done at and this is the message I get ...
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.155s
melhookv12 said:
I've done at and this is the message I get ...
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.155s
Click to expand...
Click to collapse
What command are you using that gives you that message?
WindyCityRockr said:
What command are you using that gives you that message?
Click to expand...
Click to collapse
I tried flashing the boot image by selecting 'Flash System ' then selected boot.img from my fastboot folder.
I cannot see a direct ' flash boot.img ' command in the tool kit
Thankyou for your help so far
I have come from a stock ruu, do I need to root the phone first ?
melhookv12 said:
I tried flashing the boot image by selecting 'Flash System ' then selected boot.img from my fastboot folder.
I cannot see a direct ' flash boot.img ' command in the tool kit
Thankyou for your help so far
I have come from a stock ruu, do I need to root the phone first ?
Click to expand...
Click to collapse
You are using the wrong command. A boot.img can also be known as a Kernel. On the Setup tab, in the bottom left, there is button named Flash Kernel. Use that with the boot.img instead.
WindyCityRockr said:
You are using the wrong command. A boot.img can also be known as a Kernel. On the Setup tab, in the bottom left, there is button named Flash Kernel. Use that with the boot.img instead.
Click to expand...
Click to collapse
Thanks windycity, I have got it to work and have my custom Rom. Thanks again.
This toolkit (2.1) does not appear to work on Windows XP. Any that runs on older Windows?
TWRP recovery 3.0 zenwatch
How to install Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
update
Twrp 3.0.2 For android wear 1.4
NOT INSTALL ON ANDROID WEAR 1.3 !
Download twrp 3.0.2
installation
Code:
fastboot flash recovery twrp-3.0.2_anthias.img
Photos
{
"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"
}
Stock Recovery for Android Wear 1.4
installation stock recovery
Download stock recovery
Code:
fastboot flash recovery recovery_MEC23S.img
OLD VERSION FOR ANDROID WEAR 1.5 / TWRP 3.0 /TWRP 3.0.1
Download twrp 3.0.1-0 Zenwtach AW 1.4
Download twrp 3.0
OLD VERSION FOR ANDROID WEAR 1.3 / TWRP 2.8.7.0
old version (for android wear 1.3) download twrp mega.nz
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
source https://github.com/asyan4ik/asus_anthias/tree/master
acbka said:
Twrp recovery 2.8.7.0 zenwatch
How to install
Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
download twrp basketbuild.com
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
Click to expand...
Click to collapse
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
btonetbone said:
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
Click to expand...
Click to collapse
Same. Thanks.
Ups , i fix this today ...
Sorry
hecksagon said:
Same. Thanks.
Click to expand...
Click to collapse
reload to mega . sorry
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
CSX321 said:
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
Click to expand...
Click to collapse
Yes, I pulled a system image and another user modified to successfully pass the checks that occur during updates (the original pull didn't pass). Check out this thread: http://forum.xda-developers.com/zenwatch/development/root-t3163248
Makes sure you read up on it, though, as it sounds like you'd need to do some legwork to get the system image to work. Relevant posts in that thread are 32, 52, and 54.
Hopefully, though, having TWRP means that someone smarter-than-I-am may develop even more elegant solutions!
Cheers!
Now that we have twrp we can do a system pull from an unrooted device. The system image posted in the other thread will only work on the previous version of Android Wear. Do not flash if you are up to date.
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
itechnoguy said:
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
Click to expand...
Click to collapse
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
hecksagon said:
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
Click to expand...
Click to collapse
Make sure you're using this zip file to install SuperSU (it seems to be the same binary as Chainfire's) since the app itself doesn't work, and this one doesn't require authorizations (not completely safe, but it works).
(also, don't forget to unroot from the KingRoot app first; the unroot seems to be clean enough to use Wear SuperSU)
itechnoguy said:
Make sure you're using this zip file to install SuperSU
Click to expand...
Click to collapse
That's the one I used, and it works. (Though there's no authorization popups, as you said.)
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Talysdaddy said:
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Click to expand...
Click to collapse
It'll probably remove KingRoot successfully, but the Zenwatch can't launch the SuperSU app, so root authorization dialogs never show up (the su binary still gets installed, but it can't do anything without permission from the app first).
Boooooo moto 360. It's sooo damn big.
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
itechnoguy said:
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
Click to expand...
Click to collapse
hi . i update first message .
add my github
Message for all you zenwatch 2 people.. Don't try to flash this recovery. You will have a soft brick. And with no resources at this time. There is no fix.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
Has anyone pulled the stock system partition? I, stupidly, didn't do it before I installed SuperSU. I'd like to be able to go back to stock, if there's another firmware update.
I need a link to the stock recovery.IMG file
This is the LeEco Le Pro 3's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN 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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
mauronofrio said:
Someone have tried my Tool All In One for Leeco Le Pro 3?
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Click to expand...
Click to collapse
I didn't try it yet
But Thank you for your work,
mauronofrio said:
Someone have tried my Tool All In One for Leeco Le Pro 3?
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Click to expand...
Click to collapse
It is compatible for the lepro3? I used it before for oneplus2.
meuhmeuh51 said:
It is compatible for the lepro3? I used it before for oneplus2.
Click to expand...
Click to collapse
Yes, it's completely compatible, i have tested it on my leeco le pro 3
mauronofrio said:
Yes, it's completely compatible, i have tested it on my leeco le pro 3
Click to expand...
Click to collapse
ok I will try
Can I go back to completely stock with this tool kit? I have the 727 model with a custom ROM currently
Sent from my SM-P600 using XDA-Developers Legacy app
mauronofrio said:
Someone have tried my Tool All In One for Leeco Le Pro 3?
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Click to expand...
Click to collapse
Can I go back to completely stock with this tool kit? I have the 727 model with a custom ROM currently<br />
<br />
Sent from my SM-P600 using XDA-Developers Legacy app
Sent from my LEX727 using XDA-Developers Legacy app
toanau said:
Can I go back to completely stock with this tool kit? I have the 727 model with a custom ROM currently<br />
<br />
Sent from my SM-P600 using XDA-Developers Legacy app
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
no
Think I just bricked my Le Eco Pro 3. Dragged the ROM into the root system of my X727 I was going to flash, Lineage 13
Enabled USB Debug
Unlocked Bootloader
Flashed GS Custom Recovery
Wiped Everything
Went to Flash the ROM, and nothing showed up...
I rebooted, and now I think the stock recovery re-installed itself, and there is no ROM present because I wiped everything.
Help
I just get a flicker of the Le Eco Boot Screen, then it shuts off. Can't get into ADB or Recovery.
kaivorth said:
Think I just bricked my Le Eco Pro 3. Dragged the ROM into the root system of my X727 I was going to flash, Lineage 13
Enabled USB Debug
Unlocked Bootloader
Flashed GS Custom Recovery
Wiped Everything
Went to Flash the ROM, and nothing showed up...
I rebooted, and now I think the stock recovery re-installed itself, and there is no ROM present because I wiped everything.
Help
I just get a flicker of the Le Eco Boot Screen, then it shuts off. Can't get into ADB or Recovery.
Click to expand...
Click to collapse
Can you get to fastboot? Power button + vol up? If you can you can probably flash a chinese bootloader and then try booting again
Sent from my LEX727 using Tapatalk
coolmaster121 said:
Can you get to fastboot? Power button + vol up? If you can you can probably flash a chinese bootloader and then try booting again
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
Thankfully I fixed it.
Flashed an aboot file, and all a sudden, Lineage 13 started up. You cannot believe how psyched I was. I was on eBay looking at my next phone, and all angry that I messed up my perfectly good phone.
I don't think this tool had anything to do with it. I was unforunate enough to wipe my phone before I went to install the ROM, and it wiped the ROM too. When it restarted, it had nothing to boot too. Just used Fastboot to flash the aboot file, and sideloaded the ROM and flashed away
kaivorth said:
Thankfully I fixed it.
Flashed an aboot file, and all a sudden, Lineage 13 started up. You cannot believe how psyched I was. I was on eBay looking at my next phone, and all angry that I messed up my perfectly good phone.
I don't think this tool had anything to do with it. I was unforunate enough to wipe my phone before I went to install the ROM, and it wiped the ROM too. When it restarted, it had nothing to boot too. Just used Fastboot to flash the aboot file, and sideloaded the ROM and flashed away
Click to expand...
Click to collapse
Had the same issue and same fix for my attempt into unlocking bootloader and installing custom recovery and rom.
Did you also flash the 5.8.0.19 aboot file? I'm wondering if flashing a newer one is a good idea...
Sent from my LEX727 using Tapatalk
Very good tool thank you very much Mauro
Thanks Mauro, it helped me install Omni ROM.
Question, I had two TWRP versions to choose from, I installed the latest 3.02. Is it useful to update the TWRP with e.g. the 3.1.0 from Darkobas?
Wortelstok said:
Thanks Mauro, it helped me install Omni ROM.
Question, I had two TWRP versions to choose from, I installed the latest 3.02. Is it useful to update the TWRP with e.g. the 3.1.0 from Darkobas?
Click to expand...
Click to collapse
The twrp 3.1.0 is better no matter the dev
Wortelstok said:
Thanks Mauro, it helped me install Omni ROM.
Question, I had two TWRP versions to choose from, I installed the latest 3.02. Is it useful to update the TWRP with e.g. the 3.1.0 from Darkobas?
Click to expand...
Click to collapse
Maybe yes, in the next Tool update i will update all recovery available, for now you can flash it through Manual Mode
mauronofrio said:
Maybe yes, in the next Tool update i will update all recovery available, for now you can flash it through Manual Mode
Click to expand...
Click to collapse
Thank you for all your effort for our Le Pro 3 :good:
Does this unlock bootloader with the current us version 21s?
I try using this Tool ALL in One on the Le Pro 3 but unable to unlock the bootloader as it displayed
"FAILED <remote: oem unlock is not allowed).
I already checked "ON under the OEM UNLOCKING" and "USB debugging" is "ON" also under the Developer Option before turning off the phone and boot it (volume down + Power) into Fastboot Mode.
Please help. Any advise is appreciated.
coolmaster121 said:
Can you get to fastboot? Power button + vol up? If you can you can probably flash a chinese bootloader and then try booting again
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
fastboot should be vol down
- WARNING -
This Guide is not failproof, if you do anything wrong with your device while following this guide, i won't be held responsible if you brick or hard damage your device. I insist about that but you must extract all of your data (Photos, Videos, Music, Apps, Accounts, Messages, ETC) Before proceeding or else you will end up with a loss of data, again i'm still not responsible if you lose all of your data without backing up. I WARNED YOU.
Well, you have a Galaxy S6 edge+ lying around and you want to get back to Lolipop? You want to downgrade? Well then you're in the right place!
So......downgrading to lolipop...... some people claimed it can be done by deleting some file in the odin .tar but that never worked for me.
If you have the sw rev check fail error upon downgrading....this is the guide for you!
This will wipe all your data including internal storage (depending on how you do it)
Confirmed working on my Galaxy S6 edge+ SM-G928F [It should work on Note5 but no promises from now on]
Advantages :
Downgrade procedure is safe, simple.
Your phone should boot faster
battery life should last longer [i said it should]
You can get the animated lock screen animations back.
Get old touchwiz back. [i like the 5.1.1 version]
disadvantages:
1. You cannot boot TWRP while on the downgraded bootloader
2. You will only have system-wide root. DO NOT flash systemless or it will not boot (but nobody cares)
3. Fingerprint is not working (still working on that)
4. You can only flash stock nougat from odin. You cannot flash lolipop, marshmallow tar,twrp tar,cf auto root tar or anything else [except if you have a combination firmware]
Ok, let's get started.
Requirements :
A laptop or home PC : At least running Windows 8/8.1 or Windows 10
Your device
Genuine Samsung charging cable [NOT SPONSERED]
Stable internet connection.
Files :
The lastest SAMSUNG Drivers which can be found here : https://developer.samsung.com/android-usb-driver
Odin3 : https://www.samsungodindownload.com/fr/download-for-windows
The firmware you want to downgrade to : I will link my ROM so u can install it.
TWRP [Newest version] : https://twrp.me/samsung/samsunggalaxys6edgeplus.html
Classy Kitchen [for bulding your rom] : https://forum.xda-developers.com/t/...kitchen-for-android-roms-development.3862584/
Now let's get started!
Let's start first by cooking the ROM! Open Classy Kitchen, and then open the ROM you want to use :
{
"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"
}
Normally the first time you open the program, there shouldn't be any project [except if you used this app before]
Next click "Create new project", "From PC (Browse for one)"
And then chose the path where you saved your firmware. After chosing your firmware, Classy Kitchen will open the firmware automaticly.
After the ROM is now open, click on "ROM utils" and then click on "Deodex ROM" After you Deodex the ROM, we will have to de-bloat it.
On Classy Kitchen, click on "Debloat / Re-Bloat ROM" to Debloat your ROM.
Last step [optional] We will have to De-Knox our ROM. (again optional) But De-Knoxing our ROM can save a lot of space in our phone storage. So i recommend you do.
After De-Knoxing our ROM, we will have to disable DM-Verity Force Encryption in order to Boot into the ROM [Otherwise if you don't your phone will never boot]
Click on "Remove DM-Verity / Force Encryption"
Next that we disabled DM-Verity, We will have to remove the "meta-inf installer"
Click on "Re-Build META-INF installer" and click on remove.
Finally once we have done the modifications on our ROM, we just have to save.
Click on "Build (system.new.dat) ROM (for recovery)"
and then we are done cooking our ROM!
But the guide is not done yet. We will have to install TWRP in the phone.
HOW-TO-PROCEED?
Step-1 Press and hold the power button on your device
Step-2 Chose "Power Off"
Wait for your device to completly Shut-Off.
Step-3 Re-Boot in download mode "odin mode"
Step-4 connect the phone to your computer
Step-5 open Odin3
In Odin, we will have to install TWRP, click on the AP box and chose your TWRP file [the one that you downloaded]
Don't forget to disable "Auto-Reboot" after installation, otherwise your phone will re-boot normal into Android.
At this point, Knox is tripped in your device meaning that your warranty is now expired. Also the Knox features are no longer usable.
On TWRP, click on wipe, "Format Data". A keyboard will pop-up, type "yes"
Type "yes"
Once Data Format is completed, hit home, reboot, recovery.
your phone will reboot into recovery again, hit wipe again, this time we won't format data. Instead we're going to wipe the phone's partitions
Chose in TWRP,
Then swipe to wipe. Then hit home again. Next hit "Install"
Install the ROM you just made with Classy Kitchen. It can be found in "Documents" - "Output" - "Your-ROM"
Transfert it to your phone
Click on the ROM / ZIP file and "swipe to confirm flash"
After the flashing procedure is complete, you will have to wipe the "cache" / Dalvik.
Hit "wipe dalvik/cache"
Then "swipe to wipe"
After you wiped the cache, hit "Reboot System" and hit "Do Not Install"
One last step before you get back to Lolipop. You will need a custom Bootloader in order to boot.
Just download my "custom Bootloader" https://drive.google.com/file/d/1207Guvk8J_L9FSJv2C9BpkeLpWkXtViQ/view?usp=drive_link
After you downloaded my "custom bootloader" you will have to install it.
so get Odin3 and install my bootloader!
After the Bootloader installation is complete, you just have to reboot your device, cross your fingers and hope it boots!
Congratuations! You are back on Lolipop! Enjoy!
1 : If you want to flash a mod in TWRP, you will have to put your phone in download mode, install the stock bootloader in BL tab, install TWRP in AP tab and then click on "start"
2 : If you want to get back into marshmallow / Nougat, you just have to flash stock firmware in Odin3
If you have any issues or any questions, you can DM me but it isn't guaranteed that i will reply.
Here are some screenshots of Lolipop :
Here the device i used.
what about system sound because on 6.1.1 (sorry 6.0.1) sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Nevermind. This comment is deleted
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Actually
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Try download downloading my bootloader again. I made it public
TheWiiGuy said:
Actually
Try download downloading my bootloader again. I made it public
Click to expand...
Click to collapse
Why sound coming like creepy from buzzer only on 6.1.1 interesting..
iskender4444 said:
Why sound coming like creepy from buzzer only on 6.1.1 interesting..
Click to expand...
Click to collapse
Have you downgraded to Lollipop yet?
TheWiiGuy said:
Have you downgraded to Lollipop yet?
Click to expand...
Click to collapse
i had bootloop on samsung galaxy s6 edge plus here the photo:
and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"
iskender4444 said:
and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"
Click to expand...
Click to collapse
Yes. This is The Good TWRP. Are you trying to get into recovery? If not then there is a problem with my bootloader
Mind if i upload the New bootloader tomorrow?
iskender4444 said:
i had bootloop on samsung galaxy s6 edge plus here the photo:
Click to expand...
Click to collapse
It looks like the phone is trying to get into stock recovery.
TheWiiGuy said:
It looks like the phone is trying to get into stock recovery.
Click to expand...
Click to collapse
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.
iskender4444 said:
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.
Click to expand...
Click to collapse
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.
TheWiiGuy said:
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.
Click to expand...
Click to collapse
Oh yes. Have you backed up all of your partitions on TWRP?
TheWiiGuy said:
Oh yes. Have you backed up all of your partitions on TWRP?
Click to expand...
Click to collapse
i solved twrp but can't boot same as issue on picture
iskender4444 said:
i solved twrp but can't boot same as issue on picture
Click to expand...
Click to collapse
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery
TheWiiGuy said:
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery
Click to expand...
Click to collapse
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.
iskender4444 said:
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.
Click to expand...
Click to collapse
Nevermind this comment is deleted
TheWiiGuy said:
What is your phone model number? I see you are installing firmware for a sm-g780f.
Click to expand...
Click to collapse
no this is for example man mine was g928c