This is an ancient tutorial. Stop frying me with PM's about it.
Outdated
Outdated
Thanks for this helpful guide!
Kudos!
I can get into flashboot mode but can't get into fastboot mode. I do it many times but it only charges my phone
I was never sure about using the fastboot toolbox until i read thru this. I would usually use the cmd window. I'll be flashing another of doom's test kernels later so i'll try it then. Thanks for going thru it
Sent from my R800i
I tried flashing my Xperia R800x back to stock with flashtool. The drivers installed fine but where I connect the phone flashtool says "ERROR FLASHING: Aborted"
thanks mate...help me alot
Thanks, great tutorial! Much appreciated.
Logseman said:
And now that we've covered flashing ROMs, we'll give our attention to the Fastboot Toolbox. Fastboot is a tool which can only be used normally through the command-line interface. This toolbox is basically a (quite raw) graphical shortcut to the relevant commands for our purposes.
We can activate it if we run Flashtool, click on the Flash icon, and select the Fastboot Mode.
{
"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'll comment the buttons' functions and the equivalent fastboot command if it exists . That is for the benefit of the people who use Fastboot in non-Windows desktops.
Check current device status: this checks the status of your device, to see if it's on, off, in Flash mode or Fastboot mode.
Reboot into fastboot mode (via ADB) (adb reboot bootloader): with your device switched on, it will try to reboot directly into Fastboot mode. I'm not sure if it works...
Reboot into fastboot mode (via Fastboot) (fastboot reboot-bootloader): with your device on Fastboot mode, it will reboot in Fastboot mode again. It's mostly useful for testing purposes, but the common user won't need that too much.
Select kernel to HotBoot (fastboot boot X.img): this command will prompt you to select a certain kernel in order to boot it (NOT install it). This is helpful mostly again for testing purposes, but there are cases when it might come handy.
Select kernel to Flash (fastboot flash boot X.img): This is the command you'll be using most likely. You'll be prompted to choose a kernel, exactly like before, but in this case the kernel you choose will be INSTALLED. Unless you're a tester, make sure to flash kernels which are safe to install.
Here comes an example of flashing a kernel (DoomKernel v08):
Get Ver Info (fastboot getvar version): this is a pretty pointless command by itself as it will give you the Fastboot version installed, but the "fastboot getvar" command is pretty powerful, giving you information about a lot of the internals of the phone. Of course, those informations make sense to developers, while common users can largely ignore them.
Get Device info (fastboot devices): this command will output the Fastboot ID of your phone.
Reboot device into system (fastboot reboot): this command will reboot your phone.
With all these bases covered, you can happily operate with your Xperia Play. Have fun!
Click to expand...
Click to collapse
i unable to boot unlocker using bootflash
pls advice
Screw yourself.
Logseman said:
Screw yourself.
Click to expand...
Click to collapse
If you are referring to the last post on page 1 dated Sept. 23rd of this year, you could have said something nicer then that.
priteshc:
Easiest method is to got to Wotan Server and download their Xperia PLAY Drivers:
http://www.wotanserver.com/en/page/download
Download the X-Unlock Client and install first, it will install the fastboot and S1 drivers. Then install the Xperia PLAY Flash Driver file and install. After that you should be golden to flash away.
Good luck.
I could. And he could have not undug a thread 2 years old quoting a full post to post unintelligible crock. How does one even come here? I wrote this when we were in an ancient version of FlashTool...
Logseman said:
I could. And he could have not undug a thread 2 years old quoting a full post to post unintelligible crock. How does one even come here? I wrote this when we were in an ancient version of FlashTool...
Click to expand...
Click to collapse
True, not trying to argue or anything. And I am too a bit curious to see a thread revived after all this time. I would venture that said member did a search online and it pulled this thread up so he left a reply.
Anyways, lets consider this thread done as the information while helpful is dated. Still though despite its age thank you for posting this tutorial out 2+ years ago. I know it helped me 2+ years ago when i got my first PLAY (R800x), now R800at.
Thanks!!
Thank you with all my heart, for unraveling this blessing unto me and guiding me! :good:
I might just add that for unbricking/flashing, as these links are old, i founded out new ones:
flashtool: mediafire.com/u8i5kui5b8lg/5cz5nda84565ahb/flashtool-0.5.3.0-windows.exe
tft file for xperia play: htaaatp://download2141.mediafire.com/jbnc50uejxsg/pbh253qd2dv355b/R800i_4.0.1.A.0.283_%281247-6212%29.zip (remove "a")
You sir, are a ****ing disgrace!
I jsut followed your guide from this link
Then you forward me to this page, to download Android..
The funny thing is, the first guide is for Linux, but you end up, on a download site, where you need to install a ****ing iLivid.. And that's for Windows only.
Logseman said:
Why-and-how-to use Flashtool
Flashtool is your warranty, basically. Whereas PC Companion and SEUS are fairly limited about the kinds of reparations they can do ("no can do" with modified firmwares of any kind), Flashtool is your unbricking tool of choice. And if you have unlocked your bootloaders, it's the only 100% safe way to upgrade to new builds, as OTA and PC Companion updates can bring trouble.
In order to use Flashtool, we need FTF files with entire builds to flash. No problem: here they are, all of them. Once we have downloaded the one we want, we must put it in the "firmwares" folder of Flashtool so that it can be flashed.
Now we can fire up Flashtool, click on the left icon (the lightning bolt):
Choose Flash mode:
Select the firmware we wish (note that you have a couple of options for newer builds such as keeping your user data, but you better know what you're doing or you'll probably screw up the firmware):
Wait until the files are prepared...
And connect our device in Flash mode as specified before.
Once AND ONLY ONCE the process is finished, we can disconnect the USB cable and restart our phones.
Click to expand...
Click to collapse
This tutorial is three years old. I have not maintained it since I made it. How am I to know what's been of the links?
Related
A WARNING: IN THE EVENT OF A BRICKED DEVICE, I AM NOT RESPONSIBLE! YOU DO THIS AT YOUR OWN RISK. KDZ UPDATER WILL BRICK YOUR PHONE IF NOT USED PROPERLY. SO FOLLOW THESE INSTRUCTIONS CAREFULLY!!!
So, you want to install custom recovery and custom ROMs? Well, you're in the right place. Follow this guide to it's exact instructions, and you will be fine.
You will need:
A computer running Windows (Sorry Mac & Linux users!)
Your phones USB cable. (If you don't have one, you can see a list of them here on Amazon)
We will need a couple of downloads first, so download these files:
V20C Orange France Fastboot ROM (It doesn't matter that it's Orange France, we are replacing the software anyway, I recommend this one as it fixes some calling issues by flashing a new baseband (or Radio).
KDZ Updater
Also, make sure you have your drivers installed. If you don't, get the .zip from here and install all 3 .exe files that are in the zip.
Now to install the Fastboot ROM!
First of all, extract KDZ Updater to the desktop. Then run the msxml.msi file to install the MSXML Parser that is needed to run KDZ. A window should then pop up that 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"
}
^^Select install now.
But if this comes up:
It is already installed, and you can close the window.
Once that is sorted, open up KDZ_FW_UPD.exe (Windows Vista/7 users, make sure to right click and select RUN AS ADMINISTRATOR!)
Change the type of flash by selecting the 'Type' dropdown box and select 3GQCT (SUPER IMPORTANT!)
And make sure PhoneMode is set to DIAG.
Click the
icon and select the KDZ file you downloaded earlier.
Prepare the phone by enabling USB Debugging by going to Settings>Applications>Development>Enable USB Debugging, also go into Settings>SDCard & Phone Storage and make sure 'Mass storage only' is unticked. Then connect the phone to the computer via USB cable and let Windows install any drivers it needs.
Click 'Launch software update' and do not use your computer until the update is complete. The update will take roughly 10-20 mins to complete. Your phone should reboot automatically.
Installing recovery:
You have multiple choices to choose from.
ClockworkMod Recovery 2.5.1.8 (Recommended)
ClockworkMod Recovery 4.x (Recommended but you may run into incompatible .zip files, download the recovery_clockwork_x.x.x.x_swift.zip file)
Amon RA 2.2.1 (Recommended)
Amon RA 1.7.0.1 (Not recommended due to incompatibility with zip files and recovery backups. Also .zips must be signed)
Download the recovery image of your choice (I strongly recommend Clockwork 2.5.1.8)
Next put your phone in Fastboot mode by rebooting then holding Camera+Power, make sure USB Cable is plugged in. Also let Windows search Windows Update for drivers.
Download fastboot.exe from here: http://adf.ly/2M8Hi and extract it to the desktop. Also put the recovery image you downloaded onto the desktop too.
Be sure to have your fastboot drivers installed, if you use Vista/Windows 7 then the driver should be auto-downloaded from Windows Update, if you use XP or the drivers won't install from Windows Update, then look at this.
Open a command prompt and type the following:
Code:
cd Desktop
fastboot devices (if you see ? fastboot then your device is recognized)
fastboot flash recovery name_of_recovery.img
fastboot reboot
When fastboot says rebooting, hold down HOME and wait. You should see clockwork pop up. Recovery is now on your phone. You can delete the fastboot, kdz and recovery file from your pc because we won't be needing them again. Unless you need to use fastboot.exe again, but just download the fastboot.zip again if you need it) The other files, we don't need.
(NOTE: If your phone reboots with no boot logos (LG logo and animation), or when you flash recovery and it doesn't come up, follow the steps found here. Thanks to fishears for the post!)
Now, installing custom ROMs. Pick any ROM you'd like from the ROM Development section, if you can, get the recovery version, it is much easier to install. Determine if it is a recovery backup, or update.zip
Recovery backups usually contain some .img files and a nandroid.md5 file. The folder containing these files will need to go in the sdcard\clockworkmod\backup folder. Flash them by going to Backup/Restore>Restore>Then pick the backup folder.
Recovery update.zips contain three (or four) files/folders:
boot.img (file)
install-busybox.sh (file, only appears in SOME ROMs)
system (folder)
META-INF (folder)
DO NOT EXTRACT THESE, just put the .zip file on your sdcard, then go into recovery and go to install .zip from sdcard>choose .zip>pick the .zip you downloaded. (NOTE FOR SWIFTDROID: You MUST put the update-cm-xxxxx.zip file found in the SwiftDroid_x.x.x.x_Recovery.zip on your sdcard for it to install!!!)
If you need any help, PM me or reply to this thread.
Don't forget to say
if I helped!
Enjoy!
Want to go 'advanced'? Check out this guide resizing your partitions so you can have more app space!
(Also, if a mod could sticky this thread I would be very thankful. Cheers!)
great work man.. only regret you did not post this earlier for me,as i took about 2 days to flash my phone for first time.. lol
found that helped me using recovery.
scribbclubber said:
great work man.. only regret you did not post this earlier for me,as i took about 2 days to flash my phone for first time.. lol
found that helped me using recovery.
Click to expand...
Click to collapse
lol, I was going to post it for a while because most of it was a reply to another post, but only just got round to doing it and it only took about 1 hour to re-write, but hopefully it will save some time by not having to explain it again and again to first time flashers (when they appear lol) Also might do a boot logo and recovery repair one too so users can sort that out too as there isn't a clear guide with pics on XDA. Also, i'm going to contact Decad3nce and see if we can get this stuck.
effortless. said:
...
V20C Orange France Fastboot ROM (It doesn't matter that it's Orange France, we are replacing the software anyway, I recommend this one as it fixes some calling issues by flashing a new baseband (or Radio)....
Click to expand...
Click to collapse
I have a few theoretical questions about this. Firstly, what calling issues does this fix? My current configuration is based off a v20d Baltic fastboot kdz, and has no problems. What difference would it make if I were to flash this v20c Orange, and restored a backup of my current software, if any(difference)? Lastly, is there any way to chech what baseband/radio a kdz flashes, if possible, without flashing it? I would be glad if I learned something new today, thanks.
nutterbg said:
I have a few theoretical questions about this. Firstly, what calling issues does this fix? My current configuration is based off a v20d Baltic fastboot kdz, and has no problems. What difference would it make if I were to flash this v20c Orange, and restored a backup of my current software, if any(difference)? Lastly, is there any way to chech what baseband/radio a kdz flashes, if possible, without flashing it? I would be glad if I learned something new today, thanks.
Click to expand...
Click to collapse
It is meant to include a fix for calling while connected to 3G. Me and many other users encountered a problem where we could not recieve calls on 3G. I flashed this and my problem was gone. Also, i'm unsure how to check the baseband firmware, in 2.2 ROMs, this is visible, but I looked in the build.prop, and it was a set text (under ro.ril.baseband I think) but yes, you could flash this KDZ, restore backup and all would be well. But if you needed the modified partitions, just use the tutorial that is in my signature, then flash backup.
Good idea
effortless. said:
lol, I was going to post it for a while because most of it was a reply to another post, but only just got round to doing it and it only took about 1 hour to re-write, but hopefully it will save some time by not having to explain it again and again to first time flashers (when they appear lol) Also might do a boot logo and recovery repair one too so users can sort that out too as there isn't a clear guide with pics on XDA. Also, i'm going to contact Decad3nce and see if we can get this stuck.
Click to expand...
Click to collapse
yep well said, when they appear and post without using search bar...lol think that i've did it myself but i used to save improtant notes and like that no need to search again and again, the thread should be stuck for noobs..
the guides are already here but posted on different threads and not at start, so agree that pics alongside instruction is a good idea.
Do I need recovery_clockwork_4.0.1.4_swift, that is on Mur4ik's site, to install SwiftDroid_v2.0_RC4, or I can use recovery clockwork 2.5.1.8 that I already have on my phone?
EDIT:Nvm, fixed it.
Added info on making sure 'Mass storage only' is unchecked before using KDZ to solve some peoples issues with the phone not being detected.
Noob friendly? hardly.
THis has no information on rooting. does the phone need to be rooted? is this flash pre rooted? how to root?
Lack of information everywhere, sorry.
DamDSx said:
Noob friendly? hardly.
THis has no information on rooting. does the phone need to be rooted? is this flash pre rooted? how to root?
Lack of information everywhere, sorry.
Click to expand...
Click to collapse
Obviously if you needed to root then I would have included the steps. Also around 99% of custom ROMs are rooted anyway.
I have a rooted and already updated to 2.1.
Would this still work?
KenifJambo said:
I have a rooted and already updated to 2.1.
Would this still work?
Click to expand...
Click to collapse
Of course, you would have to do this anyway if you want to install custom ROMs
This should be added to mygt540.com
Sent from my GT540 RSpec using XDA App
Danzano said:
This should be added to mygt540.com
Sent from my GT540 RSpec using XDA App
Click to expand...
Click to collapse
It already has been lol
In 2.1, you can check baseband in hidden menu.
Sent from my GT540 using Tapatalk
Will this also work with the GO version of the GT540?
As my girlfriend have this i she want to run Cyanogenmod because the phone is terrible slowly.
Aktivehate said:
Will this also work with the GO version of the GT540?
As my girlfriend have this i she want to run Cyanogenmod because the phone is terrible slowly.
Click to expand...
Click to collapse
As far as I am aware, it works perfect, GO is just some branding from some providers.
^^ Could someone back me up on this,
Thanks
Well that's good to know, i had one with 1.6 but made some things go wrong with the drivers, and the usb settings in android, but know i have this guide so i am gone try it.
When I tried it i had some trouble with the kdz flasher, but i did'nt knew of the msxml stuff and it was with windows 7.
Could someone upload another fastboot rom,preferably a version v20a or v20b
Sent from my GT540 using XDA App
The first part of this story is a little convoluted, so I'll start with my current situation and then start from the beginning.
I have a Nexus 7 WiFi tablet. I wanted a completely clean, back to factory reset. I followed the instructions here:
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
When I get to step 7 I get FAILED (command write failed (Invalid argument))
When I try to carry on past step 7 I continue to get FAILED messages. Screenshot below. Please note that I renamed bootloader-grouper-4.18.img to recovery.img for this attempt.
{
"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 have been Googling all afternoon to try to get past this but have not found a solution.
The longer, messy story. After I installed the 4.2.2 update everything seemed fine until one app, I think it was SD Maid, complained that it was lacking permissions. A bit of poking around revealed that SuperSU didn't seem to have permissions either and was giving the dreaded binaries error. Apparently 4.2.2 had removed the rooting. I waited until Nexus Root Toolkit v1.6.3 was released so it would have the right goodies for dealing with 4.2.2. Today I downloaded it and went to work.
Before I began anything with the toolkit the tablet was already showing as Unlocked. I applied the Root through the Toolkit and for some reason it would not apply. I installed Root Checker from the Play store and it confirmed that the tablet was not Rooted. I wasn't getting error messages during the procedure. I tried Googling this but didn't find anything that appeared to match my problem.
I next did a Factory Reset. When the tablet was done reloading it recovered all of my apps from backups saved to the Google servers. Still no root, still unrootable. So I do a Factory Reset but instruct it to not recover the backups. Still can't root the tablet.
At this point I'm thinking it's time to go back to a clean start instead of trying to fight the software. I'm picturing this as being like dealing with my desktop pc - no matter how bad things get I can always wipe the drive and reinstall Windows.
I next try Flash Stock + Unroot from the Nexus Root Toolkit. It appears to go smoothly and doesn't throw any errors, EXCEPT when the Toolkit says the tablet is rebooting out of fastboot mode and that the tablet may behave like it's stuck in a bootloop, the tablet just sits in fastboot mode.
So I next try the Android Central Forums link that I posted above. Maybe if I do it myself instead of using automation I'll be able to see what the problems are. As mentioned, everything goes fine until Step 7.
Other info...
This is the information that is currently displayed in the bootloader:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.18
BASEBAND VERSION - N/A
SERIAL NUMBER - something tells me I should post this here
SIGNING - not defined yet
LOCK STATE - UNLOCKED
Since product name, varient and bootloader version all seem to stem from the bootloader-grouper-4.18.img file, does this mean that the attempt to apply the image through fastboot actually succeeded despite the FAILED message?
Also, while in the bootloader, if I try to select Recovery Mode I get, "Booting failed" up where the notification bar would be. I'm interpreting that as meaning that I have in fact wiped (or at least rendered unusable) the OS.
At the bottom of the image above you can see where I tried Step 8. It is followed by the messages that the archive does not contain boot.sig, recovery.sig and system.sig. When I open image-nakasi-jdq39.zip using WinRAR I find this:
The files seem to be there but with .img extensions. What is going on?
I'm putting my efforts on hold while waiting for some feedback in this thread. To be clear; I am 100% fine and happy to wipe the tablet and install 4.2.0 or 4.2.1 or whatever else and then upgrade through the Play store. I just want my Nexus 7 working again, rooted and unlocked and I'll be smiling and back to business as usual.
success on short fastboot commands (those that send only a command) and failures on those that send files (large amounts of data) suggest data corruption - marginal cabling or a damaged USB port.
Try a different USB port on the same PC and/or a different cable and repeat the same commands. You should prefer the OEM cable instead of aftermarket cables unless it is damaged. Also, I would avoid flashing the bootloader while you are having communications difficulties. If you can do the full ROM install successfully, you can follow that up with a bootloader flash (the factory ROM is 50x larger; if you can get it to work, then the bootloader flash should also go off without a hitch)
good luck
just from looking at the text file with in system images from google, your missed step looks to be this
fastboot flash bootloader bootloader-grouper-4.18.img
your line in the command prompt just has flash bootloader recovery.img
try that then do the
fastboot reboot-bootloader
fastboot -w update image-nakasi-jdq39.zip
just leaving this here for some searchable info, there is a file called flash-all.sh inside of the zip you download the system images from google, in there has all the commands you need todo word for word. not really viewable from notepad on windows but notepad++ is able to open them and view them
bftb0 said:
success on short fastboot commands (those that send only a command) and failures on those that send files (large amounts of data) suggest data corruption - marginal cabling or a damaged USB port.
Try a different USB port on the same PC and/or a different cable and repeat the same commands. You should prefer the OEM cable instead of aftermarket cables unless it is damaged. Also, I would avoid flashing the bootloader while you are having communications difficulties. If you can do the full ROM install successfully, you can follow that up with a bootloader flash (the factory ROM is 50x larger; if you can get it to work, then the bootloader flash should also go off without a hitch)
Click to expand...
Click to collapse
I went from the tower's front usb ports to the back and it wasn't until I used a '3x USB Power" port that it worked. The cable was brand new with the tablet and hasn't even left this room since I unboxed it; I was confident it wasn't damaged.
It gave the "archive does not contain 'boot.sig' series of messages again but that didn't seem to hinder it. Following the update it booted into the OS on its own. Android 4.2.2. I went through the setups and first installed Root Checker. Device is not rooted. Next we'll find out if it roots this time. Perhaps my staying with this powered USB port will let the root operation complete properly this time.
[edit] Root success! Root Checker reports the device is now rooted. Also, during Toolkits procedures the Nexus 7's screen displayed the installation of TWRP, something it didn't show previously.
BrianDigital said:
just from looking at the text file with in system images from google, your missed step looks to be this
fastboot flash bootloader bootloader-grouper-4.18.img
your line in the command prompt just has flash bootloader recovery.img
Click to expand...
Click to collapse
Actually, if you look again you'll see it's there. I looked back and forth between the cmd window and the guide about half a dozen times to make sure I had it correct. I did *not* want to create a whole new headache due to a typo.
just leaving this here for some searchable info, there is a file called flash-all.sh inside of the zip you download the system images from google, in there has all the commands you need todo word for word. not really viewable from notepad on windows but notepad++ is able to open them and view them
Click to expand...
Click to collapse
It would appear I won't be needing this.
Thank you both very much for your replies. :good:
This is the Pixel'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.
Amazing work! EVERY ONE OF US NEEDS TO LEARN command line, but it's always excellent to see amazing devs make an all in one like this for the guys that refuse to learn the hard (right) way, and for vets that aren't quite smart enough to make a tool like this themselves, like me, but appreciate the **** out of this little gem making my first custom Oreo ROM from stock rooted a breeze! Perhaps a little bold, but im still calling it, OG PIXEL XL NOT DEAD just when I was losing faith! Bravo!
PS:. Donation incoming once my current "being a broke ass" sit-e-ation ends here in a few weeks.
awareunlikeu said:
Amazing work! EVERY ONE OF US NEEDS TO LEARN command line, but it's always excellent to see amazing devs make an all in one like this for the guys that refuse to learn the hard (right) way, and for vets that aren't quite smart enough to make a tool like this themselves, like me, but appreciate the **** out of this little gem making my first custom Oreo ROM from stock rooted a breeze! Perhaps a little bold, but im still calling it, OG PIXEL XL NOT DEAD just when I was losing faith! Bravo!
Click to expand...
Click to collapse
Thanks, all need to learn command line, but this tool help a lot, the advanced options are really good too, see it when you have some time
mauronofrio said:
Thanks, all need to learn command line, but this tool help a lot, the advanced options are really good too, see it when you have some time
Click to expand...
Click to collapse
Just peeped them briefly,. Mad props!
Damn dude, this is amazing. Will definitely give it a shot in the next few days!
Question about the install/uninstall apks feature: how does this work? Is it batch or one at a time?
EDIT: Also, to flash TWRP, do I need to be in bootloader mode and do I need to disable security on my phone before flashing? Will I lose root when flashing it? I'm using the latest Magisk.
Sent from my Google Pixel XL using XDA Labs
Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly
Thank. I've been using the Unified Android Toolkit from Skipsoft for a while now, but a lot of functions are blocked. I'll give this a go.
tutusinghsohi said:
Thank. I've been using the Unified Android Toolkit from Skipsoft for a while now, but a lot of functions are blocked. I'll give this a go.
Click to expand...
Click to collapse
Thanks, remember to give me a feedback
I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works
I'm running purenexus 7.1 ROM and would like to go to Oreo stock but retain root. Is this the right tool for me?
l2yangop said:
I'm running purenexus 7.1 ROM and would like to go to Oreo stock but retain root. Is this the right tool for me?
Click to expand...
Click to collapse
You can't retain root after flashing a factory image. You can root the oreo factory image after you have flashed it
I take it this is for windows only?
Thanks
Thanks for this toolkit
My phone was loop in no command screen . And you save me
I have questions about this toolkit
- can I use it to flash any custom rom or just original image
- can I root my phone with toolkit
- there is another virgin of toolkit can be use in a pixel book
Best wishes,
Ahmad Alsaeed said:
Thanks for this toolkit
My phone was loop in no command screen . And you save me
I have questions about this toolkit
- can I use it to flash any custom rom or just original image
- can I root my phone with toolkit
- there is another virgin of toolkit can be use in a pixel book
Best wishes,
Click to expand...
Click to collapse
You can't directly flash a custom rom with this tool, you need a TWRP already flashed on your phone and you can use "Recovery Zip Flasher" ( I do not recommend it ), i think is better to put the rom on your phone and flash it from your phone.
This tool can't root directly your phone, but gives all you need to root it (Bootloader Unlock and the flash of a TWRP).
Pixel book? This tool is only available for Windows, maybe you can use it on pixelbook with a virtual machine, but i don't know how pixel book works
With the new update a i make a new recovery flasher option for devices with project treble. Test it and told me if it works
Deleted
does this still work?
eightieskhild said:
does this still work?
Click to expand...
Click to collapse
Yes
This is a virus... how is this on XDA?
Trojan:Win32/Spursint.F!cl
revamper said:
This is a virus... how is this on XDA?
Trojan:Win32/Spursint.F!cl
Click to expand...
Click to collapse
This is not a virus, it's a false positive
https://www.virustotal.com/#/file/8...596c988acd17efa83f70e691c3d1ad7d2ff/detection
as usual, you need to breath your mouth without knowing what you're talking about
This is the Xiaomi Redmi Note 4'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.
Is there any source code available? I don't see many people using something like this when there are device-specific alternatives that are open source as well.
JosVermeulen said:
Is there any source code available? I don't see many people using something like this when there are device-specific alternatives that are open source as well.
Click to expand...
Click to collapse
This tool is not open source and it is device-specific for all Official supported devices.
I don't know others alternatives and I'm not interested in knowing them.
If you want to use it, ok, if you don't want to use it, it's always ok just don't bother others users
Good Job
It will make things easier for our device
v1da said:
Good Job
It will make things easier for our device
Click to expand...
Click to collapse
I want to specify that this tool can't bypass Xiaomi Bootloader Unlock procedure but all others function are working
mauronofrio said:
I want to specify that this tool can't bypass Xiaomi Bootloader Unlock procedure but all others function are working
Click to expand...
Click to collapse
Then this app is mostly useless...
Don't write all in one, including boooader unlock if it does not unlock bootloader. The only way to unlock a Xiaomi Bootloader is via the official app. So either remove bootloader unlock or all in one from the title because it is misleading.
greenys' said:
Then this app is mostly useless...
Don't write all in one, including boooader unlock if it does not unlock bootloader. The only way to unlock a Xiaomi Bootloader is via the official app. So either remove bootloader unlock or all in one from the title because it is misleading.
Click to expand...
Click to collapse
The name is that and will not be changed, this tool is not written only for xiaomi devices but also for others devices. Unfortunately Xiaomi devices needs to be unlocked through official method and this is why they have not been added until now. In all cases clicking on unlock you will be redirected to a good guide to unlock xiaomi devices.
mauronofrio said:
The name is that and will not be changed, this tool is not written only for xiaomi devices but also for others devices. Unfortunately Xiaomi devices needs to be unlocked through official method and this is why they have not been added until now. In all cases clicking on unlock you will be redirected to a good guide to unlock xiaomi devices.
Click to expand...
Click to collapse
Whatever it was designed for it does not work as intended with Xiaomi devices. So you should not have shared it with that title because it is not true. Without bootloader unlock you cannot do mainly anything and this app is not designed to unlock MI devices. It is my opinion that you shouldn't have shared it here under that name because it's very misleading. I've told you what you should do to make it not misunderstandable but you refuse to take my advice. See, whatever. You told your own opinion and I've told mine. Topic closed.
greenys' said:
Whatever it was designed for it does not work as intended with Xiaomi devices. So you should not have shared it with that title because it is not true. Without bootloader unlock you cannot do mainly anything and this app is not designed to unlock MI devices. It is my opinion that you shouldn't have shared it here under that name because it's very misleading. I've told you what you should do to make it not misunderstandable but you refuse to take my advice. See, whatever. You told your own opinion and I've told mine. Topic closed.
Click to expand...
Click to collapse
He'll just say "If you want to use it, ok, if you don't want to use it, it's always ok just don't bother others users." and ignore any valid remarks.
JosVermeulen said:
He'll just say "If you want to use it, ok, if you don't want to use it, it's always ok just don't bother others users." and ignore any valid remarks.
Click to expand...
Click to collapse
Again, i don't say what he said it's not true, i said that this is the name of the tool and that is the name of dedicated support threads. Unlock option is not available for xiaomi devices (except for Xiaomi Mi A1), in its place you will find the link to a guide to unlock the bootloader. Now if you want to tell me that a recovery on the tool is not working, or you want i add a new recovery to the list or you have problem with the tool, comment and i will try to help you, but do not keep saying unnecessary things.
Thanks and have a good day
mauronofrio said:
Again, i don't say what he said it's not true, i said that this is the name of the tool and that is the name of dedicated support threads. Unlock option is not available for xiaomi devices (except for Xiaomi Mi A1), in its place you will find the link to a guide to unlock the bootloader. Now if you want to tell me that a recovery on the tool is not working, or you want i add a new recovery to the list or you have problem with the tool, comment and i will try to help you, but do not keep saying unnecessary things.
Thanks and have a good day
Click to expand...
Click to collapse
Whatever floats your boat. You too have a good day.
ouch, i was here to unlock my 2nd mido in the fast way, well the app cant unlock bl
Very promising tool! Many thanks for your work Dev.
Can this tool flash stock images on the device with locked bootloader, or do I have to use edl?
mauronofrio said:
This is the Xiaomi Redmi Note 4's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
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.
Click to expand...
Click to collapse
where is the download ?
miaoudak said:
where is the download ?
Click to expand...
Click to collapse
Are you kidding, right? Don't be a write-only user.. Read the post you've replied to and follow the links.. literally the first line of the quoted #1 post points to the original thread where the download links are available (one main and 3 alternatives)..
its execute from fastboot mode or edl sir...
has someone tried it and is it still working today?
Just DL this morning to test
Hello all!
I have a question concerning a device, I have a Cricket Dream 5G and the device is completely bootloader unlocked. However, I'm trying to figure out how I can obtain a firmware file for the device seeing as the Carrier or manufacturer hasn't released one. It is a MediaTek device running the MT6833 and efforts to make a scatter file in order to read with SP Flash tools have been unsuccessful,
I've also attempted to download an OTA update and see if it saved the file locally, as well as packet dump the update process via Wireshark. No Cigar.. it appears to be in the Cache partition which isn't accessible without root (which cannot be obtained without running TWRP with the device being Android 11). does anyone have any suggestions on how I might be able to get a copy of the system image or boot images for the use of making a working TWRP?
Thanks a lot!
Josephdbrewer25 said:
Hello all!
I have a question concerning a device, I have a Cricket Dream 5G and the device is completely bootloader unlocked. However, I'm trying to figure out how I can obtain a firmware file for the device seeing as the Carrier or manufacturer hasn't released one. It is a MediaTek device running the MT6833 and efforts to make a scatter file in order to read with SP Flash tools have been unsuccessful,
I've also attempted to download an OTA update and see if it saved the file locally, as well as packet dump the update process via Wireshark. No Cigar.. it appears to be in the Cache partition which isn't accessible without root (which cannot be obtained without running TWRP with the device being Android 11). does anyone have any suggestions on how I might be able to get a copy of the system image or boot images for the use of making a working TWRP?
Thanks a lot!
Click to expand...
Click to collapse
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.
SubwayChamp said:
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.
Click to expand...
Click to collapse
I've successfully backed up the device and gained root access. Thank you so much for recommending this tool. It worked, just voided my warranty lol. Had to disconnect the battery which requires taking apart the device
SubwayChamp said:
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.
Click to expand...
Click to collapse
Also do you know where the stock recovery is located. I can't seem to find it anywhere, like it doesn't even exist.
Josephdbrewer25 said:
I've successfully backed up the device and gained root access. Thank you so much for recommending this tool. It worked, just voided my warranty lol. Had to disconnect the battery which requires taking apart the device
Click to expand...
Click to collapse
Usually when a device's software had been modified, it may lose the warranty, or not, depending on what the "small" letters on a contract says, anyway, you could restore to its original state at any time, as you see in the need to claim it.
Normally, this tool works only installing the USDK64 drivers, and connecting device when power off, pressing the two volume buttons, I never need to open the back cover as MediaTek devices have the preloader mode, that it used by this tool to bypass the DA/SLAA protection, it does in the first stage the same thing that this tool does https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/ but without the need to use SP Flash tool but reading/writing directly onto the device.
Josephdbrewer25 said:
Also do you know where the stock recovery is located. I can't seem to find it anywhere, like it doesn't even exist.
Click to expand...
Click to collapse
Newer devices doesn't have a dedicated recovery partition.
SubwayChamp said:
Usually when a device's software had been modified, it may lose the warranty, or not, depending on what the "small" letters on a contract says, anyway, you could restore to its original state at any time, as you see in the need to claim it.
Normally, this tool works only installing the USDK64 drivers, and connecting device when power off, pressing the two volume buttons, I never need to open the back cover as MediaTek devices have the preloader mode, that it used by this tool to bypass the DA/SLAA protection, it does in the first stage the same thing that this tool does https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/ but without the need to use SP Flash tool but reading/writing directly onto the device.
Newer devices doesn't have a dedicated recovery partition.
Click to expand...
Click to collapse
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.
Josephdbrewer25 said:
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.
Click to expand...
Click to collapse
My device is the Cricket Dream 5G EC211001. It's weird
Josephdbrewer25 said:
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.
Click to expand...
Click to collapse
It doesn't really need to stay in preloader, this is the whole purpose of this tool, preloader is, actually, useless for flashing, when you press the two volume buttons, the device enters to preloader mode
{
"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"
}
if you installed correctly the drivers, then, mtkclient detects the device, in the short time, and make it return to BROM mode through a handshake, to bypass the DA/SLAA authorization,
BROM mode is disabled by OEMs, similarly to EDL point, without this kind of tool, no more remedy that opening the back cover.
Moto 1st gen, it's a long time ago. It is placed in a tiny portion of the ramdisk, but you don't need to find where’s located.
If you think to port it, actually is not as easy due to newer implementations, A/B slots, virtual slots, a way to fix it permanently, etc., but basically what you need is in the boot image