{
"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
So how does this handle the different partition layouts?
I am curious myself...
This tool has been posted in numerous threads for different devices. I don't have my laptop a few days. Does nobody have any feedback on weather this was successful?
Sent from my Galaxy Nexus using xda premium
Go to the principal thread (link in the OP) and read comments
I searched his original thread there is no mention about devices having different partition layout. I don't think the OP realizes that we have two different partition layouts for the Dell Streak 7.
I'm working on it.
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
Hello,
I posted this on cyanogenMod forum few days ago, but no one was able to help me so far, so maybe I will have more luck here...
Recently I found my old dev phone 1 with stock image and decided to make it more useful by installing cyanogenMod on it. I tried to follow instructions on http://wiki.cyanogenmod.com/index.php?title=Android_Dev_Phone_1:_Full_Update_Guide page. I downloaded Amon_Ra's Recovery, adb and fastboot tools, added all-htc udev rules and followed instructions on fastboot page http://wiki.cyanogenmod.com/index.php?title=Fastboot#Access_bootloader to access the bootloader.
Unfortunately fastboot devices returned empty list of devices even more, lsusb did not list any new device.
When connecting the phone in debug mode adb sees my phone without problems and lsusb shows my phone as well so it's not connectivity problem.
I found this section about SPL S-OFF on fastboot page http://wiki.cyanogenmod.com/index.php?title=Fastboot#Verify_SPL_S-OFF and it seems it applies to my case as my fastboot screen looks like this:
{
"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"
}
The section continues that in such case I have to use different SPL, so I went to http://wiki.cyanogenmod.com/index.php?title=HTC_Dream:_DangerSPL page to install DangerSPL, but it requires Amon_Ra recovery which again requires fastboot to install so there's a cycle here
I would be grateful for any hints what I should do in this situation
Thanks!
ok, never mind: I used standard dream procedure with rooting and it worked ok, I'm on cyanogenMod now
Cheers
Morg
UltimateAndroidBox is a toolbox that it is aimed to help many people to handle their android devices via ADB and in the future not only ADB.
It will feature, backup systems, file manager systems, apk installation, camera backup and many more features to come.
With the passing of time i will be adding more features to the App and add a
{
"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"
}
whether features are working.
Features: (the first ones will always be the ones that work)
Smartphone detection
Adb Reboot
Adb Recovery
Adb Bootloader
Install .apk (space in name error solved)
Install Multiple .apk (space in name error solved)
LogCat Viewer
LogCat Downloader
BackUp Whatsapp
BackUp Camera
Updated 12/14/2013
XDA:DevDB Information
UltimateAndroidBox, a Tool/Utility for the Samsung Galaxy S III I9300
Contributors
monose1
Version Information
Status: Testing
Created 2013-12-15
Last Updated 2013-12-14
First one ☺
tapatalked with Nexus S3
romskii said:
First one ☺
tapatalked with Nexus S3
Click to expand...
Click to collapse
No link anymore, is this discontinued?
Is this supported for S3 lte as well?
Sent from my GT-I9305N using Tapatalk
It is a global phone tool. It was paused due to studies but i will continue to develop it, thaks for the support.
Well, few days ago I was bored, so I decided to develop this very simple app which can be an altenative to that "Hardware information" section under "About device" you can find in stock rom.
There also is an option ("Dump all the properties!") which makes a file called "getprop.txt" which lists device's properties; useful to developers when they have to bring up a device tree for building custom roms for a new device or when they have to add the support for a new variant of that device. You can find this file under /sdcard/Android/data/org.alberto97.motoinfo/files/getprop.txt (I have choosen this path because it doesn't need root access and it is always availaible).
This app should work on every Moto/Motorola device (It works well on my 1st and 3rd Moto g).
N.B.: "Manufacture Date" field is available only on those roms which include this commit. Else if you have root access, you can see it from /proc/config/date/ascii. Still not sure why Motorola took another longer (and not working) way in stock rom.
A couple of screenshots:
{
"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"
}
great job, as usual
I like it! THX
unable to scan this APK !! what is this error?
i downloaded this on my MotoG3, when i wanted to install it , it showed me this error !!
can anyone help regarding this
nandakis4 said:
unable to scan this APK !! what is this error?
i downloaded this on my MotoG3, when i wanted to install it , it showed me this error !!
can anyone help regarding this
Click to expand...
Click to collapse
I simply got a blank page.
This is the Nexus 5'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.
Nice tool man
Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly
i WANT TO UNLOCK MY NEXUS5S
Hello everyone!
I made a script here to package the current system into a firmware that will be recognized and run by twrp or orangefox.
What is build_now_system?
It can help you package the currently running system into a zip archive that can be recovered and executed by a third party.
It saves you the step of image conversion and reduces the burden of finding tools, it's already built in.
It can automatically generate the flashing scripts required by each image
Although it is not flashing according to the standard, it also has its own unique set of flashing specifications.
You don't have to care how it works, you just need to provide error logs and problems.
Its running log is stored in /sdcard/build_now_system.log by default, it will not be cleared unless you delete it manually
What conditions are required to run it?
Just need your device to be rooted.
But ideally you also need to meet the following:
1. Have root privileges
2. Has a third-party recovery mode
3. Sufficient space (about 30GB)
4. Have at least 30% power
[DOWNLOAD]
passcode：wak0
GoogleDrive
SCREENSHOT:
{
"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"
}
AND MY FORUM ARTICLE
@MrZZZ123 Thread closed as duplicate of
[SCRIPT] BUILD NOW SYSTEM TO ROM.ZIP
Hello everyone! I made a script here to package the current system into a firmware that will be recognized and run by twrp or orangefox. What is build_now_system? It can help you package the currently running system into a zip archive that can...
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator