Hi,
I'm having some trouble entering the default Android Recovery on my S5830i, as it appears to not have it on my model. I've tried holding the Home + Volume up + Power buttons and a combination of others, though nothing works. Holding the Volume up + Volume down + Power buttons enters into download mode, so there's always that.
Can anyone explain how I would factory reset my device without the recovery mode? Is this something that can be done via Odin?
Thanks for your help!
just few quick questions though,, Did you root your device? You are on some custom kernels? home and volume buttons don't function or you have difficulty grasping the right time intervals procedure ? Are you in boot loop/freezing Samsung splash screen state, or you have access to your device?
press and hold the Volume Up + Home keys and then long press the Power key till the start up screen with “Samsung Galaxy Ace GT-S5830i″ logo blinks for two times and you see your desired recovery screen.
if you want to achieve factory data reset,open your settings and follow this path>>
Settings → Privacy → Factory data reset → Reset phone → Erase everything.
Are you familiar with ADB? you can activate debugging mode,assuming you have access to your phone settings and connected to your PC ( follow this topic for getting to know the command line and how to use it with given tools )
By typing the following command you can merely reboot the phone:
Code:
adb reboot
want to go to recovery:
Code:
adb reboot recovery
I haven't rooted my device and it's running stock firmware which is bootable to the lock screen, but I have no access to the settings due to this and unfortunately haven't enabled USB debugging. The volume/home buttons function normally however the combination press when turning it on does not show the recovery mode (been trying all day!). I've just tried the buttons you've mentioned though this boots the device normally. Doing the same on my Galaxy S2 does boot into the recovery mode, so this is very strange!
If there was a way to flash (and factory reset) the device again using Odin that would be great, but I haven't yet found a way to do this. I flashed the firmware using one found on sammobile.com, though as I guessed this doesn't factory reset the device. If possible, perhaps flashing clockworkmod recovery might help? Thanks again.
got your correct stock firmware, have access to your Download mode, follow this post step-by-step instructions .
Thanks ehsanotaku, just tried that and still boots to the lock screen so appears to not been factory reset. The firmware flashes okay in Odin and when the phone restarts the install screen appears, but then it just boots into Android as normal.
Still no luck with getting the recovery screen to show. Thanks.
@BradDodi, I am a bit confused mate The lock screen that comes with your Android device has a Pattern/Pin/Password protection being activated, which refuses to let you inside your OS UI environment !
Are you absolutely sure you are on GT-s5830i (cooperve) not (cooper) ? lets remove your battery and read the fine print on the back of your battery please,, might help shed some light on this odd combo behavior.
On side note though ,if you have your PDA;PHONE(MODEM);CSC information, really can help us find some wipe Multiple .tar.md5 file package for your problem mate( a reference links to what you have found on sammobile.com firmware database also would give me more clues, your preference country/region would help).
This is the sammobile.com firmware which I downloaded and flashed previously. I'm in the UK, so I downloaded the firmware which has the region code BTU (which I believe is correct, though might be wrong). I've tried searching around for any Cyanogenmod firmware for my device which I can flash using Odin, but most are in .zip's not .tar.md5.
Here's the info under the battery:
SSN: S5830iGSMH
FCC ID: A3LGTS5830I
Thanks again for your help with this!
@BradDodi, You didn't answer the password protected part( you can recover it easily through Gmail account with ease, if you already established your account through settings ).
We are going to devise some plan to wipe your data through Multi wipe package mate.
Be advise your modem might be incompatible with these European division Multi packages and render your sim card totally useless >>
Code:
http://d-h.st/1mr
or
Topic compatible with 2.3.6 s5830i
Another solution: if you are up to little challenge I can create some modified Walk through step-by-step instructions to split your confirmed working flash into 3 part wipe flash -able package .
Technique I am going to discuss was originated by Doky73 and involved some propriety tools ( Splitfus2) , Linux terminal emulator for windows ( Cygwin), good internet connection for updating kitchen inside Cygwin , latest Java SE Development Kit from oracle (x86 based or x64 based structure ) .
Read this topic thoroughly, but don't act on it ,, we need some adjustment to make it work .
Let me know if this is not too much technical stuff for your taste
How To install Cygwin/Splitfus2 To Split Stock Firmware
"marcussmith2626" was credited for this tutorials, "Doky73" credited for discontinued project "Splitfus2" , few modification and adjustment need to be made for Further improvements > Tested on Windows 7 (32-BIt) Machine>> wipe package produced for s5830i successfully .
marcussmith2626 said:
How to install Cygwin Properly
uninstall any version of Cygwin you currently have installed
now install Java SE Development Kit 7u51 from here
Click to expand...
Click to collapse
jdk-7u71-windows is the tested/updated installer, please download and install the appropriate (x86) 32-Bit or (x64) 64-Bit installer from oracle ( tick the agreement links for download)
marcussmith2626 said:
now download Cygwin from here
extract the fille
you should have a package folder and a setup.exe
run the setup
when it asks how you want to install select I have the packages already on my harddrive
select the package folder
in the next window click the arrow at the top that changes everything from default to install all
make sure you have selected the root of your harddrive to install it in Cygwin folder for eg c:\cygwin
now you can install cygwin
Click to expand...
Click to collapse
Package/libraries/Dependencies failed on 32-BIt Windows 7. Missing Dll was reported.
To get your Cygwin working on your designated Machine Please follow these instructions>>
1. Visit this official Website , get either of the New installer available : setup-x86.exe (32-bit installation) or setup-x86_64.exe (64-bit installation).
2. Run your installer, choose "Install from Internet"
Note: To keep the installation small while saving bandwidth for you and Cygwin, the default installer will download only the files you need from the internet.
3. Do as he says, leave the "C:\Cygwin" as your Root Directory.
Note: Don’t like to have programs installed on the root of your C: drive you can change the path or make a (Hard/Soft) symbolic link from C:\Cygwin to your desired location.
4.Caution Advised as some of these mirrors are linked to gigabytes of dependencies and occasionally some vital files are missing .
Recommended mirror ( contains only 100 something megabyte of database/tools, which is needed for basic simulations of Linux command line>>
Code:
http://mirrors.koehn.com
Process will take 5 ~ 15 Minutes;
5. Now Run the shortcut on your Desktop, you must be directed to your root directory
Code:
i.e: [email protected] ~
$
we need to check if "zip utilities" is available, otherwise we have to run the installer to get the missing tools from our preference mirror.
Type the following after the "$" character please :
Code:
$ cygcheck -vf /usr/bin/zip
/usr/bin/zip: found in package zip-3.0-12
if you don't have this tools, Go back and run installer, do all of the previous procedure .
Now in the search box on top of the mirrors section, type "zip" to filter all of the packages already installed or suggested. In this picture(in archive sub part), marked for me as Reinstalled ; for you is marked as skipped;marked it and proceed . (picture will be found in attachment)
Run the command again, you must have the tool by now .
Note: Make the acquaintance of zip utilities and relevant parameters by typing the following command after "$" character, if you are curious though.
Code:
$ /usr/bin/zip
marcussmith2626 said:
How To Install Splitfus2 And Run It
Download Splitfus2 from here
Click to expand...
Click to collapse
Or in case of file corruption, get the latest version from my attachment.
marcussmith2626 said:
now navigate to C:\cygwin\home\your username
create a folder called splitfus
{
"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"
}
unzip the Splitfus2 zip and place the containing splitfus2.exe and _base folder in the splitfus folder
place the stock firmware you want to split also in the splitfus folder
run Cygwin
type cd splitfus
now type ls
type ./splitfus2.exe -w S5360nameofyour firmware (note to make it easier just type S5360 then press the tab key and it will auto compleate - also note it is case sensitive and it starts dot then a forward slash)
now your firmware will be split and output in a zip file to your splitfus folder
unzip and use in odin
Supported Models
B5510
S3300
S5360
S5360B
S5360L
S5360T
S5363
S5369
S5570I
S5830i
S6102
Click to expand...
Click to collapse
Do the following instruction. Proof of wipe zip package and more info about this tools will be found in attachment.
Unofficial Odin firmware package for Samsung GT-S5830i Sliced from the Kies package using SplitFUS2 v2.11.120625GA by Doky
Based on: "myxxx"_HOME.tar.md5
MODEL: S5830i
PDA: -###
CSC: ###
MODEM: ###
WIPE package - will erase your user data!!! Use at your own risk only! Do not use pit file, and do not tick repartition!
You can also try this re-built installer file for other models ( failed on "i" model, only regular parts was produced) >>
Code:
https://drive.google.com/file/d/0B7aETFlknMd7UTFNbmcydExFSGc/view?usp=sharing
ehsanotaku said:
"marcussmith2626" was credited for this tutorials
, "Doky73" credited for discontinued project "Splitfus2" , few modification and adjustment need to be made for Further improvements > Tested on Windows 7 (32-BIt) Machine>> wipe package produced for s5830i successfully .
jdk-7u71-windows is the tested/updated installer, please download and install the appropriate (x86) 32-Bit or (x64) 64-Bit installer from oracle ( tick the agreement links for download)
Package/libraries/Dependencies failed on 32-BIt Windows 7. Missing Dll was reported.
To get your Cygwin working on your designated Machine Please follow these instructions>>
1. Visit this official Website , get either of the New installer available : setup-x86.exe (32-bit installation) or setup-x86_64.exe (64-bit installation).
2. Run your installer, choose "Install from Internet"
Note: To keep the installation small while saving bandwidth for you and Cygwin, the default installer will download only the files you need from the internet.
3. Do as he says, leave the "C:\Cygwin" as your Root Directory.
Note: Don’t like to have programs installed on the root of your C: drive you can change the path or make a (Hard/Soft) symbolic link from C:\Cygwin to your desired location.
4.Caution Advised as some of these mirrors are linked to gigabytes of dependencies and occasionally some vital files are missing .
Recommended mirror ( contains only 100 something megabyte of database/tools, which is needed for basic simulations of Linux command line>>
Code:
http://mirrors.koehn.com
Process will take 5 ~ 15 Minutes;
5. Now Run the shortcut on your Desktop, you must be directed to your root directory
Code:
i.e: [email protected] ~
$
we need to check if "zip utilities" is available, otherwise we have to run the installer to get the missing tools from our preference mirror.
Type the following after the "$" character please :
Code:
$ cygcheck -vf /usr/bin/zip
/usr/bin/zip: found in package zip-3.0-12
if you don't have this tools, Go back and run installer, do all of the previous procedure .
Now in the search box on top of the mirrors section, type "zip" to filter all of the packages already installed or suggested. In this picture(in archive sub part), marked for me as Reinstalled ; for you is marked as skipped;marked it and proceed . (picture will be found in attachment)
Run the command again, you must have the tool by now .
Note: Make the acquaintance of zip utilities and relevant parameters by typing the following command after "$" character, if you are curious though.
Code:
$ /usr/bin/zip
Or in case of file corruption, get the latest version from my attachment.
Do the following instruction. Proof of wipe zip package and more info about this tools will be found in attachment.
Unofficial Odin firmware package for Samsung GT-S5830i Sliced from the Kies package using SplitFUS2 v2.11.120625GA by Doky
Based on: "myxxx"_HOME.tar.md5
MODEL: S5830i
PDA: -###
CSC: ###
MODEM: ###
WIPE package - will erase your user data!!! Use at your own risk only! Do not use pit file, and do not tick repartition!
You can also try this re-built installer file for other models ( failed on "i" model, only regular parts was produced) >>
Code:
https://drive.google.com/file/d/0B7aETFlknMd7UTFNbmcydExFSGc/view?usp=sharing
Click to expand...
Click to collapse
I have already split one 5830i firmware
You can download it
S5830i_XXMJ2_OXEMC2_XXMJ1_wipe_by_SplitFUS2
http://d-h.st/1mr
marcussmith2626 said:
I have already split one 5830i firmware
You can download it
S5830i_XXMJ2_OXEMC2_XXMJ1_wipe_by_SplitFUS2
http://d-h.st/1mr
Click to expand...
Click to collapse
we already new that master marcussmith2626 :good: all respect and credit was given in advance mate.However some individual with very different base band ( not compatible ) with your work requested it through our private channel, so I did some modification upon failure of your kitchen dependencies on Linux simulator.
ehsanotaku said:
we already new that master marcussmith2626 :good: all respect and credit was given in advance mate.However some individual with very different base band ( not compatible ) with your work requested it through our private channel, so I did some modification upon failure of your kitchen dependencies on Linux simulator.
Click to expand...
Click to collapse
what firmware did they want?
if you give me the link to it on sammobile i'll see if it can be simply split
Related
Method outdated and risky.
Improved method: http://forum.xda-developers.com/show...5#post17148825
Hi Everybody, Im Jcmaster and im Kind of new in this forum, i have been following this forum for some time ind i think its time to give something to this comunity, i have been searched for a while and found nothing like this, i'dont know if this is ilegal (i dont think so) or if it is in the wrong section but i will continue any ways.
Ok this is to all the people who had they phones bricked while doing this, First of all, i succesfully Bricked my phone and bring it back to life by doing the following.
I was reading all the messages from people who bricked their phones by doing this tutorial and i did not understand how they did it so i tried to brick my phone to see how to fix it, but the only way i could do this was by skiping the last step, umount /efs, when i did not make this and restarted my phone, the phone get bricked, it onli lighted up the screen and do nothing.
Once i managed to brick my phone i just downloaded the KPN gingerbread rom, and the brazilian rom, y followed this tutorial to unbrick my phone: This is The Tutorial
I Installed the KPN with the OPS and the Modem files of the brazilian rom, once i got the rom running my phone was kinda messy, some random error messages and many more, so i did a wipe of the chache and dalvik and restarted the phone an it was ok, and the i installed the Fla.sh rom via odin and thats the rom im runing now and i dont have any problem, well thats how i bricked/unbricked my phone on purpose, and dont forget the last step, umount/efs. i hope it works for somebody because i worked with me.
Firts Things First, I'm not responsible for a, Brick or semibrick that may come with this tutorial i have succesfully unlocked 15 Phones and by the thime they dont have any problem, so i suggest to read the entire post as many times is needed to understand the entire procedure & clarify all the doubts that you may have.
If you have a cuestion, please ask it, its better to wait some time until you have an answer that brick your phone, and also your cuestions are usefull for other people.
Once this is understood lets proceed.
Ok ill start with the Requirements.
You Will Need:
Your Samsung Galaxy Ace (obviously)
The original Usb Cable that comes with the phone.
Your Computer (I will use Windows XP for the demonstration, because i dont know how to do it with other O.S)
Your Phone has to be Rooted
Samsung Kies Installed Wich can be found HERE
ADB wich comes with Android SDK and can be found HERE
Ok Once you have all that stuff we can continue.
I will not teach how to Root your device because custom roms are already rooted and if you have a stock rom there are plenty tutorialn on hou to root it, and also i will not teach you how to install Kies because its realle easy and anyone can do it, i will only teach you how to install Andoid SDK and the specific ADB Package OK lets start.
Once you have downloaded the Android SDK Run the Installer trough all the steps to install it, I recomend to Install it in "C:" disk so it makes easier to make al the further steps, if it ask for the Java SDK just download and install, restart the Android SDK Installer and continue, Once its Fully Installed open it and do this next steps:
1-Go to the "Available Packages" Option on your left Menu
2-Click on the "Refresh" Button ond the bottom Right and wait until it finish
3-From Items select the "Andoid SDK platform-tools, revision 6" Item
4-Click the "Install Selected" button on the botton right and wait until it finish
5-Now you can either close the SDK or leave it open.
Image:
{
"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"
}
Now that you installed the SDK and the ADB its time to set the Path so the cmd.exe recognizes the ADB, there are two methods, One With cmd.exe (console) and one with the My PC Properties, i will explain bot of them.
Cmd.exe (console) Method.
Click on your start button and select "Run" from the Start Menu, type cmd.exe on the box and press enter.
Once the CMD its open write the next Text: set PATH=%PATH%;C:\android\android-sdk-windows\platform-tools
The text Write in Bold means your SDK Installation Directory, thats why i told you to Installa the sdk In C: Disk, just check that your Installation Directory is the same as mine or modify the line according to your needs.
My PC Properties Method.
Open My PC, and Right click on a blank space,
Select "Properties" from the just opened contextual menu,
On My PC Properties select the "Advanced Options" Tab
On the "Advanced Options" tab click on the "Environment Variables" button.
Now Mark the "Path" Variable and click the "Edit" Button.
At the end of the line add this text:
;C:\android\android-sdk-windows\platform-tools
Remember that The text Write in Bold means your SDK Installation Directory, thats why i told you to Install the SDK In C: Disk, just check that your Installation Directory is the same as mine or modify the line according to your needs.
Ok now you have completly installed the android SDK and the ADB (Android Debugging Bridge) and you can now do the final steps to Unlock or Get the Unlock Code for Your Samsung Galaxy Ace.
Ok now that you have Installed all the necessary programs:
Connect your SGA to your Computer via the included USB Cable. (the drivers should be installed by now, Kies installs them automaticaly)
Click on you start button and open the "Run" option, on Run type cmd.exe and press enter.
Now on Cmd.exe type the next text to acces the ADB Shell:
cd C:\android\android-sdk-windows\platform-tools
Remember that this means your Android SDK Installation directory, so if you get an error, check that the route is well writed and if you installed it in a diferent directory just modify the line so it fits to your needs, just remeber to pur - instead of spaces and \ (not / ) to indicate folders.
Image:
Now that you are in "C:\android\android-sdk-windows\platform-tools" type: adb shell
Image:
Now That you are in adb shell type the next command: su
At this point you have to give root premission to adb shell on you Phone
Image:
Ok now that adb shell has root premission and its inside you phone, type the next line:
cd /
Now be carefull and notice that there are spaces in the line and that we are using / instead of \
Image:
Ok now that you typed cd / type the next line: mount -o remount rw /
Image:
Ok Now type: mkdir /efs
Image:
And now type: mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
Image:
And now type: cat /efs/mits/perso.txt
And you will get some strange characters on the screen and a 8 digit number, thats your unlock code, copy it in paper or in a Notepad file, but check it twice so you get the correct number, also the number provided is unique so dont try to use your number with other phones or use my number with yours.
Image:
Ok Now that you Have your Code just type: umount /efs
And disconnect your phone from your computer, turn off your Phone and insert a SIM from another company, it will ask for the Unlock Code, just type the code that you just get and you are done, your phone is now unlocked and without brick risk.
Image:
Now you can check that your cellphone is unlocked by typing the next code on your numeric keyboard, like if you where doing a call: *#7465625#
Image:
And thats it, its really easy, and its really safe if you read everything, and clear your doubts.
All the images are mine and i learned this from a friend of my, but its tested in 15 Samsung Galaxy Ace Phones an none get hurt XD,
Well thats it, remember to comment and ask as many times you need, im glad to answer all of your questions, se you later
great tutorial. very detailed and easy to understand.lucky for me my phone is already unlocked out of the box
Sent from my GT-S5830 using XDA Premium App
Thank you Im gonna try it
This works with every android? or every samsung android?
Or its just ACE?
once again GREAT TUTORIAL
Gh0s7_Hun73r said:
Thank you Im gonna try it
This works with every android? or every samsung android?
Or its just ACE?
once again GREAT TUTORIAL
Click to expand...
Click to collapse
I havent tried, but maybe it can work i just tried with galaxy ace because one friend of my bought several of them to sell and i unlocked them all, well its just matter of trying
Just tried on mine. Works perfect!!!!!!!! Thank youuuuu
Sent from my GT-S5830 using XDA App
Thanks for ur contribution......... Luckily we dont have network lock in our country
Now thanks to you, I dont have it either
hehehehehe .... This may encourage other to buy ACE..... More Aces Strong community
ThanKS! i got the code.
I was denied access trying to go to into SU because I made a mistake in Cmd.exe (console) Method.
I then tried My PC Properties and it worked.
umount /efs did not do anything so i just used exit.
Deserves to be in development thread.
Did you follow the steps with the SIM installed and registered, or without SIM?
Even i use preunlocked ace, i have to admit that this tutorial is well writen. Straighforward and easy to understand. Good one will click that thanks button once i get on my pc later
Sent from your phone
I did it with my SIM on the phone lol. Then when i got the code, i switched the sim for another provider and after i put the pin it asked for the code. Put it and "phone not restricted" message apear
Sent from my GT-S5830 using XDA App
Very nice and easy to understand tutorial...thanks
rjtd said:
Did you follow the steps with the SIM installed and registered, or without SIM?
Click to expand...
Click to collapse
The first time i tried this i had the original telcel sim on the phone, then when i finished i restarted the phone with other company (movistar) sim, and for the tutorial my phone was already unlocked and the original telcel sim on
Sent from my GT-S5830 using XDA App
wow, just tryed it 5 min ago, and it WORKED
Thank you so muhc, you save me some euros
terminal
could i do this from terminal on my phone instead of thru ADB?
wow! it really worked
hats off to you my friend
dg1598 said:
could i do this from terminal on my phone instead of thru ADB?
Click to expand...
Click to collapse
I havent tried but you can give it a try, butt i dont thin it will work.
I have done the proces but after I type SU I receive a message permision dennied, I have updated my phone with the new Telcel Ginger version and rooted with the acegingeroot file, wht can I do??
thanks
Hi.
This is the stock ROM I have flashed: French stock: G1XXKPQ
http://forum.xda-developers.com/showthread.php?t=1531850
I flashed the 2.3.6 stock ROM with Odin 1.85. And used Odin again to flash the TerraSilent 1.3.5 custom kernel. Then I have CWM custom recovery. And for the 2.3 GB ROM, I can see I have root (adb shell, su is okay).
Now I can't find out what to do as next step. I have looked at several AOSP ROMS' threads in the development forum, and still got no clue.
I tried the following:
1.
Download the following ROM: [ROM][YPG1][4.2.2] Paranoid-Android 3.60 - With HALO - 6/26/13
http://forum.xda-developers.com/showthread.php?t=2340544
And put it to the SDCARD. BTW, I have no external SDCARD installed.
In the CWM recovery, I chose to install this .ZIP file, the process is failed as follows:
{
"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 on screen text is OCR'ed by human flesh as follows:
Code:
ClockWork Mod Recovery v5.0.2.7
-- Installing: /sdcard/ROM/pa_ypg1-3.60-26JUN2013-201457.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "ypg1" || getprop("ro.build.product") == "ypg1"
E:Error in /sdcard/ROM/pa_ypg1-3.60-26JUN2013-201457.zip
(Status 7)
Installation aborted.
As the message hints, I run similar commands in "adb shell" within the stock 2.3.6 ROM:
# getprop ro.product.device
getprop ro.product.device
YP-G1
# getprop ro.build.product
getprop ro.build.product
YP-G1
Click to expand...
Click to collapse
("adb shell" on Windows will have all commands echoed back, hence the stupid repeated command lines)
I don't know if this result is related to that assert performed in recovery. Just for the record. And I believe "YP-G1" is definitely "not equal" to "ypg1". But this is a safe assert. If this failed, probably there is something not expected by the ROM installer, so I understand cancelling installation is the correct thing. But how to pass the test and enable installation anyway?
2.
Then I downloaded this "preflash" zImage as mentioned in this most recent CM10.1 ROM thread:
http://forum.xda-developers.com/showthread.php?t=2333769
I have found several threads linking to this "preflash" zImage. It is somewhat quite mysterious. I don't know what does this "preflash" indicate: under what condition indeed does this "preflash" procedure to be performed?
I have come across the "MTD based ROM" jargon while searching everywhere. I have no idea of that. But I just want to get the AOSP likes to be installed onto the device. This "preflash" kernel seems to be just for such task.
Any way, I flashed it using TerraSilent's CWM recovery. The device is stuck at the samsung logo. So I reboot to Ubuntu to use heimdall to flash the zImage raw file.
By the way, can I pack zImage into .tar file and flash using Odin? heimdall tends to get messed up, and install its driver in Windows tends to mess even more, this tool definitely is not recommended to casual user).
So after flashing using heimdall, the device enters boot loop, the "samsung" logo did apear for three times, then the recovery screen just flashed away, even too fast to peek for the on screen message, I have to capture it by recording a video, and here is the frame extracted from the video:
Again the on screen text is OCR'ed by human flesh as follows:
Code:
CWM-based Recovery v6.0.1.2
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
Checking Internal SD Card marker...
Internal SD Card marker not found... continuing anyways.
-- Installing:
Finding update package...
E:unknown volume for path []
E:Can't mount
Installation aborted.
At last I'm still with that French stock 2.3.6... Any help would be appreciated and sorry for the lengthy gossips I have put here.
Well I figured out... It turns out after flashing the "preflash" zip, you MUST NOT reboot, but instead go on to flash the ROM itself.
And another important thing: you must restore /efs after flashing back to stock using Odin.
Initially I just can't get such hints from all those ROM threads in the development forum. Maybe it's too obvious. But it certainly is not so obvious for we Chinese people, as I searched in Chinese, I can find many have done exactly the same I did (lol). Anyway from the Chinese forums I finally get to it.
I have made a record of all the flashing procedures and put it here, hope it will help some avoid searching all over the world to get started from scratch.
Samsung Galaxy S Player WLAN 4.0, YP-G1 International (Intl.) version flashing notes
====================================================================================
I use Windows 7 X64 to perform the following operations.
Part 0: Backup /efs (to your computer)
I don't know what this really means, but it is REQUIRED for later flashing, so don't rush to the flashing.
I use adb shell to make backup:
# tar cf /sdcard/efs.tar /efs
And pull it to your PC and keep it safe:
C:\> adb pull /sdcard/efs.tar .
(This is just an example, your backup and restore approach can be different)
Part 1: Revert to stock Android 2.3 (Gingerbread)
I believe this can be performed as long as you have download mode available, and this should be a good start if you think you have totally messed up with your device.
Files you need:
a. Samsung mobile driver: http://forum.xda-developers.com/showthread.php?t=2038555
For the 1.5.25.0 driver installation, the install wizard says it some error occurred at the end. But it seems no harm.
b. Odin flashing tool: (download link is the same as a.) I use Odin 1.85 for the YP-G1 device.
c. The 2.3.6 stock ROM: http://forum.xda-developers.com/showthread.php?t=1531850
I picked G1XXKPQ, version 2.3.6. Since my device is bought from China, it is compatible.
Also download the "Pit" file, again for my YP-G1 from China, I choose the "Intl" version.
Steps:
1. Put your device into download mode:
a. Shutdown deivce entirely, and pull battery and re-install to be sure
b. Key combinations: PRESS and HOLD: HOME button and Volume Down button. Then additionally, press and hold POWER until "Download mode" appears on device screen.
2. Connect your device to PC, let the system recognize new devices and install drivers.
3. To further make sure, you can disconnect the device, pull out its battery. And enter download mode, then connect to PC again.
4. Open Odin tool, this needs Administrator privilege, if Odin detects your device, it will display some message like "<ID:0/008> Added!!", and there is a blank text field under the "ID:COM" label turning to yellow color and showing a COM port number.
Then on the Odin GUI, select two files:
a. Click "PIT" button, locate your downloaded ".pit" file. This will cause the "Re-Partition" option to be selected automatically.
b. Click "PDA" button, locate your ROM, which is a .tar.md5 file, like: YP-G1FullRestoreIntl2.3.6.tar.md5
c. Click "Start" and wait until the device reboots.
Sometimes Odin is stuck at "SetupConnection", then retry: find a better cable (should not be too long), find a better USB port on your PC (USB 2.0 possibly can be preferred over USB 3.0). Retry by restarting from Step 1.
5. After device reboots, it enters the Android recovery automatically, and you can see some RED text saying "mount failed" alike. Just choose "wipe data/factory reset" and then reboot.
Now you are stock.
Part 2: The TerraSilent custom kernel (with custom recovery ClockWork Mode, CWM)
The stock Android recovery cannot be used to flash custom stuff, so you need to flash a custom recovery first.
Steps:
1. Download TerraSilent custom kernel: http://forum.xda-developers.com/showthread.php?t=1643384
I choose 1.3.5, which comes with CWM v5.0.2.7
The odin flashable kernel file is: TerraSilent_intl-1.3.5.tar
2. Shutdown device, and enter download mode again, and connect it to the PC, open up Odin, DO NOT touch the "PIT" button, only the PDA button, and choose custom kernel file. Then punch "Start".
3. This should be quick, and device reboots automatically, but you will find nothing new in your stock Gingerbread ROM.
Part 3: Restore your /efs folder
Like part 0:
C:\> adb push efs.tar /sdcard/
Then "adb shell" to the device, and "su" if necessary:
# tar xf /sdcard/efs.tar -C /
(Again your restore approach can be different)
Part 4: Get 4.x AOSP ROM and flash:
This is the time you transform your Android 2.3 player into an AOSP based Android 4.x ROM, so it's a little tricky (in fact the tricky stuff includes above /efs backup & restore thing)
I'm taking this CM9 as an example: http://forum.xda-developers.com/showthread.php?t=2213152
Because in this thread it mentions you MUST restore /efs for this ROM install to succeed, otherwise it will fail. (I have attached a photo of the failed install for reference.)
1. From this thread, download two files:
a. cm-9-20130402-kernel-preflash.zip
b. cm-9-20130408-UNOFFICIAL-ypg1.zip
Put both to device's /sdcard. And REMOVE your external Micro SD card if any.
2. Shutdown your device. Addtionally pull and re-install the battery for sure. Then you need to enter the recovery.
The key combinatoins for entering recovery:
PRESS and HOLD: HOME button and VOLUME UP button.
Additionally, press and hold power button. When the screen lights up, release POWER button, but keep HOME and VOLUME UP pressed.
As you are in the CWM recovery, this is from the TerraSilent custom kernel, version is v5.0.2.7.
a. Perform some wiping:
- wipe data/factory reset
- wipe cache partition
- advanced, - Wipe Dalvik Cache
b. Then install:
- install zip from sdcard, - choose zip from sdcard, --> select the .zip ROM file and confirm.
Sometimes the /sdcard won't mount, i.e., after choosing "- choose zip from sdcard", nothing can be found there.
Then I pull the battery and repeat it. Probably the files will show up.
Flash in the following order, don't reboot after the first .zip is flashed:
a. cm-9-20130402-kernel-preflash.zip
b. cm-9-20130408-UNOFFICIAL-ypg1.zip
When flashing the second one, the device will reboot automatically. Wait patiently until the device stays at a "new" custom recovery, which shows its version as "CWM-based recovery v6.0.1.2". Then you have completed all. Here you can flash the GAPPS package, if you have put it at your /sdcard before.
PS. "GAPPS" packges download: http://goo.im/gapps/
Please match the version, e.g., CM10.1 is "Jelly Bean" 4.2 (JB), CM9 is "Ice Cream Sandwich" (ICS).
Part 5: Other AOSP based ROMS.
From now on, you don't need that "cm-9-20130402-kernel-preflash.zip" file when flashing other AOSP based ROMS.
Just put the .zip ROM file at /sdcard, and reboot into custom recovery, wipe as needed, and install.
Attached is a photo showing how it fails to install the CM9 ROM if /efs was not restored:
Wow this is a full fledged guide on how to flash cm9, cm10 and cm10.1. I will add this to the all-in-one when I'll get some time.
Envoyé depuis mon Nexus 7 avec Tapatalk
How To Root Galaxy Win or Galaxy Grand Quattro (GT-I8552)
Best viewed in a Web browser. The pictures won't appear as intended in the XDA app.
One of the bit.ly/shortened URLs linked in this guide which directly leads to the download page of the file may be blocked by a security feature. They're all safe. Once you click a link you may be warned by your browser for accessing the URLs, but fortunately, the Warning page has a part where there's an option to proceed with accessing the page, just proceed and click the link. See example below.
bitly suggests that you
Change the original link, and re-shorten with bitly
Close your browser window
Notify the sender of the URL
Or, continue at your own risk to: http://download.clockworkmod.com/drivers/SAMSUNG_USB_Driver_for_Mobile_Phones.exe[/COLOR]
If you get no warnings, much better. Let's proceed.
The Preparation : Before you start, make sure that . . .1) You have a PC / Laptop running Windows Platform
2) Samsung USB Driver for Mobile Phones (click to DL from clockworkmod.com) is installed
3) Phone battery power is at least 70%. That's good enough to not run out of power during this whole process.
4) Its USB Debugging is enabled (Settings > Developer Options > USB Debugging)
5) You have a USB Cable to establish a connection between the phone & your computer
6) You have the files needed. Keep three files in one folder.
- twrp_2.8_material - 9185 KB (click to DL directly from its dev's (Gody) MediaFire drive)
- Odin3-v3.09.zip - 972 KB (click to DL from sammobile.com's MEGA shared cloud storage) This software runs only on Windows platform.
- SuperSU_v1.94.zip - 1,703 KB (click to DL direclty from chainfire website)7) A copy of that flashable zip file "SuperSU" must be saved in your phone's memory, internal or external .
1st Step : Flashing TWRP Recovery Via OdinWhat is Recovery? | The Two Android Recovery Agents (CWM & TWRP)
Here, we will use TWRP Recovery. We will install it on the device using the Odin software.
Required: your phone, Windows PC, USB cable, Odin, and TWRP (.tar file)
1) Boot phone to "Odin Mode, a.k.a. Download Mode" by pressing the buttons at the same time: Volume Down, Power, & Home. When the device vibrates, immediately release the Power button while still pressing the other two until the Download Mode's warning screen appears.
{
"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"
}
2) Press the "Volume Up" button to continue to Odin Mode
3) In your computer, using WinRar or 7-zip, extract the Odin zip file, then run Odin3 v3.09.exe as Administrator
4) Connect your phone to your PC via USB. It should say "Added" on Odin.
5) On Odin, click the "AP" button, find and select the "twrp_2.8_material.tar"
6) Click "Start" to proceed in flashing the TWRP Recovery. *This takes about a minute.
7) It's partially finished when it says RESET! with these three lines in the message box.
RQT_CLOSE !!
RES OK !!
Removed!!
Then, phone will reboot automatically to OS.
8) Sometimes it takes a few more seconds after the phone has rebooted for you to be able to completely close Odin. Just wait for Odin to change its status from RESET! to PASS! and say All threads completed. (succeed 1 / failed 0), as shown in the picture below.
Then, you may click Exit and disconnect cable.
TWRP 2.8.5.0 Recovery is now installed.
And this is how to boot to "Recovery Mode". Press the buttons at the same time: Volume Up, Power, & Home. When the device vibrates, immediately release the Power button while still pressing the other two until the SAMSUNG boot-screen appears. See photo instructions below.
By the way, see the pictures below for the difference between the Galaxy Win's stock recovery and TWRP's recovery.
Important : NANDroid Backup
At this point, with TWRP Recovery installed, you can now create a NANDroid backup. It's a backup of literally everything in your phone - System, Cache, Data, EFS, and Boot. It is considered to be the top priority of things to do before messing with your phone i.e. flashing ROMs, kernels, or apps. After you create a backup, the backup file would be located in "sdcard0/TWRP/BACKUPS/" for internally saved backup, and "extSdCard/TWRP/BACKUPS/" if it's saved to the external memory. This file can also be transferred to a different storage, say a hard-disk, if you need to have more space on your phone for something else. You may skip to the actual rooting part. But, in case you do want to create a backup just follow the simple steps below. 1) Boot phone to Recovery Mode
2) Select Backup
3) This part lets you name the backup file with whatever name you want, choose whether to save it internally or externally, and pick which stuff you'd like to backup. And when you're ready, swipe to backup.
*This may take 5-10 minutes depending on how big your whole current installation is.
4) Once done, you may proceed with the 2nd part of this rooting guide.
2nd & Final Step: Flashing SuperSUSuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root.
Required: your phone, and SuperSU (.zip file)
1) Boot phone to Recovery Mode
2) Select Install
2) Locate the zip file SuperSU
3) Go ahead and swipe to install SuperSU *This takes just 5-10 seconds.
4) Reboot System
You now have root access. Good luck!
Important Reads After Rooting An Android Device:
What Is A Nandroid Backup and How Exactly Does It Work?
TriangleAway – Reset Flash Counter Tool
11 Things To Do After Rooting Your Android Smartphone | RootMyAndroid.Org
Suggested ROM:
COSMIC 2.0 ROM (released 4/27/15) (CM10). Rated to be the most stable custom ROM for the device.
Originally developed for Galaxy Core Duos by dev abhi922, then ported by dev gody420 to work on Grand Quattro.
Hey mate, thanks a lot! Your guide is very clean and objective. Links shown properly. You did a good job!
But I'm still facing a problem on my I-8552B. Whichever Recovery I try to flash, I keep getting a black screen.
I tried the one you posted and the 6.0.3.7 version, but nothing different. :/
Thanks! I'm as glad that this guide is helpful to us who need it.
When does this black screen appear?
What have you done so far?
Sent from my GT-I8552
The phone is working properly, I can boot into the system normally. But after I flash any custom recovery via Odin (all I tried, so far), and boot into recovery (phone off, VOL +, Home and PWR boot), I get a black screen.
I've read that people are getting this issue on devices bought after July/14...
Please refer to this thread for more ideas.
http://forum.xda-developers.com/showthread.php?t=2977978
Best of luck!
Sent from my GT-I8552
Hi. .when my galaxy win was rooted, the task manager was deleted. Is there a way to recover it plz. .tnx
Sent from my GT-I8552 using XDA Free mobile app
[Root ,Easy ,Fast No Pc! ]
:angel:Visit the link: http://forum.xda-developers.com/grand-quattro/general/root-grand-quattro-win-duos-t3091676
Good Share
Thanks for clear share;
1- Odin3-v3.09.zip link dead
2- I download the v3.07 and It works only AP = PDA
3-I like the TWRP screen
Thanks again
i'm too having the same problem..after flashing custom recovery, the screen goes black when i try to enter recovery mode
Samsung Galaxy Win GT-I8552B
Excellent tutorial, but I could not install SuperSU, my phone model is
Samsung Galaxy Win GT-I8552B
Version: 4.1.2
Can you help me?
Best regards
Roosevelt Paz Garcia
I am stuck at 'starting adb sideload features' in adb sideload. Please suggest what to do?
I am not getting the install option on the recovery boot
someone help plz
No need to unlock bootloader for samsung ???
Is it??
NEXUS 6 - SUPPORTS ALL VERSIONS UP TO LATEST ANDROID BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus, Google, OnePlus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down', 'Volume Up' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
** Updates **
** Videos **
** FAQ**
Hell yeah! Been waiting for a long time.
edit: how do I upgrade to 1.3.3 from 1.3.2?
edit1: nvm, figured it out
Sent from my Nexus 5 using Tapatalk
AutoUpdate available for Nexus 6 Pro Version
+Added FULL support [including root] for Android 5.0.1 LRX22C
+Download and Flash stock 5.0.1 LRX22C stock image directly from Toolkit
Mark.
Hi Mark.
Really looking forward to trying the toolkit for the first time.
Thanks a bunch, Shaun
Is it just me or is your site down?
Any alternative links?
nexus6 drivers
I have ran the drivers page cant find them im starting to wonder if they wrote a windows 7 64 bit driver set it only connects in camera mode i got as far as unlocking the boot loader then flashing twrp but it seems twrp isnt even Installed now i went to boot loader mode and It had stock recovery it kept giving the error cannot find recovery any ideas? Ive downloaded the new sdk updated my adb.exe and fastboot.exe to no avail cf autoroot cant even find it abd the boot loaders unlocked
Would be nice to have unencrypted boot image file in the toolkit for newbies
aalupatti said:
Would be nice to have unencrypted boot image file in the toolkit for newbies
Click to expand...
Click to collapse
Disabling Forced Encryption is included in the Toolkit in the Rooting section (option 4,8 from the main menu).
Mark.
mskip said:
Disabling Forced Encryption is included in the Toolkit in the Rooting section (option 4,8 from the main menu).
Mark.
Click to expand...
Click to collapse
Great.. missed that
Also FYI : when I activated the motorola nexus 6 module , the application shows the name as HTC nexus 6 V 1.0.2
aalupatti said:
Great.. missed that
Also FYI : when I activated the motorola nexus 6 module , the application shows the name as HTC nexus 6 V 1.0.2
Click to expand...
Click to collapse
Same here, guess just a typo[emoji1]
Sent from my Nexus 6 using Tapatalk
aalupatti said:
Great.. missed that
Also FYI : when I activated the motorola nexus 6 module , the application shows the name as HTC nexus 6 V 1.0.2
Click to expand...
Click to collapse
My stupid mistake lol I made this at the same time as the HTC Nexus 9 module and must have pasted HTC in the wrong place.. Its just a bit of text at the top and nothing is affected by it. Will upload the fixed text in the next update. Thanks for pointing it out
Mark.
How would i going about reverting totally to stock?
Using the toolkit i have:
flashed the stock 5.0 ROM
re-locked the bootloader
I still cannot update to 5.0.1
How to achieve fully to stock?
i keep getting recovery not found when i try to root it.
i've tried root alone, install recovery and all-in-one.
i've never had this problem with my nexus 4 and 5
I'm getting the same thing.
Everything works until I try and root it. It boots into my twrp then just hangs and says it can't find my recovery. Any ideas
Could I have a download link?
That does not work in the home
m.ilbello said:
Could I have a download link?
That does not work in the home
Click to expand...
Click to collapse
looks like the website is down for the moment
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It has LINUX/UNIX and MAC support!
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.1 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations: - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here.
Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources: The official and original repository can be found here.
Bug reports/Feature requests: If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.
Licensing: Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
Disclaimer:I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
warfenix said:
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This tool has support only for 4 nexus devices, some features might work, some not, it's all down if the commands that are used by the tool are supported by the other device.
For example all fastboot flashing commands use the command:
Code:
fastboot flash <partition> <file_to_flash>
The same goes for the rest of the commads, I will try to investigate more and see if it's worth it to create a Sam Note 3 package for the tool.
The adb features should work though.
That would be awesome as i run only linux. And cant seem to get odin or heindall to work. Tried multiple times. So if there is something you could cook up. Amazing sauce. Its a att note 3. Either way. This will work great for my n6
Sent from my Nexus 6 using Tapatalk
New update with some fixes that should have been implemented a long time ago...
- Fixed Sideload flashing
- Enabled Recovery rebooting
- Fixed open folder for Stock menu
Wow - Great work on this. Love the fact that it supports mac/nix as well.
Nice! Keep up the good work.
Thank you!
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
bL33d said:
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
Click to expand...
Click to collapse
Yes, you can unlock the bootloader and flash TWRP recovery with it.
Support to Nougat?
ipan gulopuan said:
Support to Nougat?
Click to expand...
Click to collapse
Nougat should work with no problems, I personally used it to flash bootloader, radio and vendor images for Nougat update.