Database Develop

[Q] Neeed Halp with rooting samsung galaxy s vibrant on bell

I was wondering if i was the only one who's a noob on this site because i have been trying (with no success) to root my using some good directions which i have posted below. The problem is... i only speak noob. I am so new to this stuff that i really dont know what to do. What i have already done is downloaded the update.zip and the SDK i dunno if i installed it properly but i know i have to go into my cmd and type something... from then on there i have no clue what to do. ANY HELP IS GREATLY APPRECIATED ^_^
Originally Posted by AllGamer View Post
Step 1. root your phone
Bell's I9000M is slightly different than the regular I9000
most of the root methods mentioned on other topics will not work.
Even the 3 button recovery mode has been disabled
After some experimentation this is the working method
download the update.zip from this topic (Thanks to jentech)
then you need to run adb devices to make sure your phone is listed
(ADB is part of Android SDK, download it from the source
if you get something like
Code:
adb.exe devices
List of devices attached
900098c722a9 device
(if you run adb.exe devices and comes back with an empty list, then make sure you have set the phone into debugging mode Application > Settings > Development > USB Debugging)
then you are can execute
adb.exe reboot recovery
this will take you to the recovery screen
now if your device works with the Power + Volume Up + Home button, then you can skip that, however in my case the 3 button mode didn't work
select the update.zip with the volumen up down button, then hit home screen, it should say installing in yellow, then you are done, it reboots back to normal, and now you can install Busy Box

Before you begin get some important info from the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series
just glance through it, and look at the pretty pictures.
then to Root you phone follow this topic, which is also linked on the Wiki
Self Unlock SGS tutorial
http://forum.xda-developers.com/showthread.php?t=747235
which starts from the basic, to root, all the way to unlocking the phone
post back if you have any question or get stuck at any point
just in case you missed it, make sure your 3 buttons Recovery Mode is working, else keeps all your finger crossed for good luck
{
"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 update.zip that you seek is attached to the link of the rooting/unlocking topic linked above

if the 3 button recovery mode doesn't work
using the Android SDK you installed run the ADB.EXE command
it is inside one of the folders after you unzip the Android SDK package

k so the 3 button thing was a no go :/ do you think you could walk me thru (slowly) how to do the whole abd thing properly? Also the link you reffered me to is exactly what is on this thread and i just dont have enough experience to understand each of the steps, if u can just give me the main pointers in noob talk then i think ill be albe to figure out the rest

yeap, you need to copy the update.zip into the phone internal SD card
you can do that by simply connecting the phone to the PC on the USB cable
instead of USB debugging mode, just choose USB Kies mode
make sure Kies is installed

AllGamer said:
yeap, you need to copy the update.zip into the phone internal SD card
you can do that by simply connecting the phone to the PC on the USB cable
instead of USB debugging mode, just choose USB Kies mode
make sure Kies is installed
Click to expand...
Click to collapse
Can i do that while im on recovery mode or will that eff evrything up?

So i now have no idea how to put the update.zip file onto my internal sd card there is nothing on the phone i checked all the settings and i disabled the debug...

does the windows explorer shows the drive letters?
just copy and paste the update.zip file into the Internal SD card of your phone
when you connect via Kies mode to your PC
the windows explorers automatically pops up too

Bell root is not possible!
i may try samsung keys however i dont see how that helps you put the update.zip on your internal memory card or allows you to access anything in adb.exe in command promp.....my main question is acctually how the heck do you root the samsung vibrant with bell??? I have tried the thread in xda developers forum for bell saying it is the only way to get it to work....well it willl not work along with the million other ways i have tried, except 1clickroot it bricks alot of phones. Has anyone successfully rooted vibrant with bell! If so how?! I have even tried Z4Root which is the preferable method, well maybe i will just have to wait until some figures out a way that works. Boot with 3 button method "up vulume +menu+power" then apply sdcard:update.zip
E:signature verification failed
Installation aborted.
It says this everytime no matter what way i try!!! please someone have a solution!

Here you go...
This worked well for me.
http://forum.xda-developers.com/showthread.php?t=803682
Read all instructions carefully!

Rooted!
Thanks worked like a charm good thing only way I had left to root my phone. Any ideas how to apply the lag fix? One click lag fix will not work "error installing device busy" I tried moving all Apps to external and still wont work? Is there another way?

aub_pro said:
Thanks worked like a charm good thing only way I had left to root my phone. Any ideas how to apply the lag fix? One click lag fix will not work "error installing device busy" I tried moving all Apps to external and still wont work? Is there another way?
Click to expand...
Click to collapse
For my first phone, I tried RyanZA's OCLF (search for oclf in the app market). I did have it installed and working pretty decent but ran into some issues in the beginning trying to apply the lagfix.
On my new phone, I applied Darky's ROM 9.2 with SpeedMod Kernel. You can enable or disable lagfix from recovery mode using CWM (ClockWorkMod) Personally, I just left the lagfix disabled and my phone now is performing way better then my first phone when I had lagfix enabled. (Mind you, my first phone was bricked).

I have downloaded darkys rom 9.2 and cwm recovery in rom manager also downloaded darky configurator from market for 9.2 and enabled speed work kernal in the configurator .do I flash rom with that app or use the flash rom from SD in rom manager? I will read more and try and figure this out....thanks a million for everything but if you could help me with this confusion that would be great lol

aub_pro said:
I have downloaded darkys rom 9.2 and cwm recovery in rom manager also downloaded darky configurator from market for 9.2 and enabled speed work kernal in the configurator .do I flash rom with that app or use the flash rom from SD in rom manager? I will read more and try and figure this out....thanks a million for everything but if you could help me with this confusion that would be great lol
Click to expand...
Click to collapse
Do you have a Bell phone?
- In any case, I had flashed my kernel using odin first.
- Copied the ROM(the entire zip file. don't extract it) over to the root folder of my phone.
- Boot into CWM and selected install zip from sdCard
- Select "choose zip from sdCard
- find the ROM that you downloaded to your phone and select it.
- let the phone do its thing and your good to go.
That was probably the long way but I now see that you can apply the ROM through Darky's Configurator...
- Open up Darky's Configurator
- Select Wipe the device if you want a clean install
- Select your Kernel preference
- Select Modem options (this is why I asked if you were Bell user. Apparently there has been an issue where you loose 850 band if your flashing a new ROM using JL2. So in this option, I selected "no modem")
- Check Alternative WiFi driver
- For the rest of the options you can see you can choose for yourself.
Once you are done with the selection process, press the menu key button on your phone, then choose "Select Zip and Flash".
Follow instructions on phone and you are good to go.

awesome those are much less confusing instructions then others....im stuck on the kernal part download it and extract it and there is no .tar file it is just zimage....file.....i have tried downloading it ten times same result....its the recommended odin 500 kernal
i have tried mounting that file in odin pda and it must not be a .tar cuz it doesnt even see the file....

aub_pro said:
awesome those are much less confusing instructions then others....im stuck on the kernal part download it and extract it and there is no .tar file it is just zimage....file.....i have tried downloading it ten times same result....its the recommended odin 500 kernal
i have tried mounting that file in odin pda and it must not be a .tar cuz it doesnt even see the file....
Click to expand...
Click to collapse
No need to extract that file. Once it is downloaded on to your PC, use Odin and navigate to where the file is downloaded.
I will have to verify the kernel I downloaded when I get home but I'm certain that I did not extract anything.

kernel installed
ok speedmod kernel is installed but when i load up darkys config the wipe all is greyed out and i cant click it.....im assuming that i use boot phone into recovery and whpe/factory data reset from there? wont i lose the darky 9.2 rom then being as it is on the root of the internal card?
the bold parts below are confusing me....so on the internal sd i should have the update.zip and darky rom 9.2 or is it just refurring to darky rom everytime it mentions zip?
Now turn off your phone, and wait for it to shutdown completely. Then, boot into Recovery Mode. Press and hold Volume-UP + Home + Power at the same time, and let go of the buttons when the screen turns on (and says Galaxy S GT-I9000/I9000M Samsung), to enter Recovery.
7. Then using the volume keys to navigate and the Power button to select, do the following:
Select 'wipe data/factory reset', and then select 'Yes'. Important!
Select ‘Install zip from sdcard’.
Then select ‘choose zip from sdcard’.
Now navigate to the ROM zip, then select it.
Then choose ‘Yes’.
8. The ROM will now be installed. After it says install complete, select ‘Go Back’ twice, then select 'Reboot System now'.
There you go, Darky's ROM is now installed!

k i figured it out im at the last step installing update.....been at this screen for about 10 mins but im sure thats normal.?

k it was hanging way to long on the installing updates screen and appeared to be frozen so i press menu + vol up + power and after a few time of it hanging at the galaxy s screen it finally brought me to clockwork recovery....so i rebooted normally and now i have the speed kernal still installed still rooted but the phone is original hardware? what do i do now?

Hey
....when you go to the menu settings about on your phone, what does the build number say?
Do you have Darkys Configurator app installed? Use that to flash the new rom. If you have nothing on your phone I would choose wipe. Choose the itmes that you want in the configurator. Select the menu button on your phone then select the option Save zip and exit... the second button in the bottom right.
Then choose Darkys rom where you saved it on your phone.
Sent from my GT-I9000 using XDA App

[GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root

{
"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"
}
Setup, Preparation and Prerequisites
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter the bootloader - Turn the phone off. Hold volume down + power. The bootloader is also known as fastboot mode.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Try this first, but if that doesn't work look here. Still having issues? Give this a try. None of these working? Hopefully this does the trick.
Downloads
Download a custom recovery of your choice and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP) or ClockworkMod (CWM)
Root:
SuperSU
Information
Rooting a nexus device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has. Using a toolkit will only make things worse in the long run...learn to do it properly. It has been proven that every time you use a toolkit, god kills a kitten. Save the kittens.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Plug the phone into your PC, then open a command prompt window window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.
After the above command has finished excuting, run the following (DO NOT skip this step, it is more important than you think):
Code:
fastboot reboot
The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.
Close the command prompt window.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock rom
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. Leave the phone at the home page of the custom recovery.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the Nexus 5 Android Development and Nexus 5 Original Android Development section) onto the phone (remember the location where you copy it to)
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. To install a custom rom the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the rom > select the rom > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the rom, and finally reboot the phone.
Keep in mind that the first boot after installing a custom rom & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted...Plus you saved a kitten. Enjoy

Troubleshooting & FAQ
Why am I seeing a red triangle with a dead android when booting into recovery even after I flashed a custom recovery?
What you are seeing is the stock recovery, meaning that the custom recovery that you flashed did not install correctly. Try the following suggestions:
Make sure you are using the USB cable that came with your phone. Only use other ones, if the stock one isn't working
Try using different USB ports. USB 2.0 ports (the ones that ARE NOT blue) are preferable. USB 3.0 ports (the blue ones) may cause problems with connectivity.
If you are on a desktop, use the ports on the back of the tower instead of the ones in the front. These ports are directly connected to the motherboard, rather than the ones in the front which are usually attached to a header cable which then indirectly connects to the motherboard.
My phone wont boot into android. I can only access the bootloader and custom recovery. What do I do?
Suggestion 1: Factory reset via recovery.
TWRP Instructions:
Boot into recovery
Wipe > Swipe to Factory Reset
Reboot
CWM Instructions:
Boot into recovery
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
Reboot
If that doesn't work continue onto Suggestion 2.
Suggestion 2: Push a ROM to your phone and flash it.
Download a ROM onto your computer. If you don't have time to look for a ROM, just download the stock ROM.
Move the downloaded ROM onto your desktop, and rename the file to "ROM.zip" (without the quotation marks)
Boot phone into recovery
Open command prompt and run the following commands:
Code:
cd Desktop
adb push ROM.zip /sdcard/
Wait for it to finish copying the file, then flash the ROM. If you need further details on how to flash a ROM take a look at the OP, section 3. Rooting, Option B)
If that doesn't work continue onto Suggestion 3.
Suggestion 3: Flash the factory images.
Flash the factory images
My phone wont boot into android. I can only access the bootloader. What do I do?
Flash the factory images
My phone exploded. What do I do?
Tape it back together then flash the factory images

Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk

dombera said:
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.

Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
Awesome, thx
Sent from my Nexus 4 using Tapatalk

This is awesome, will come in handy.
Sent from my HTC Desire using XDA Premium 4 mobile app

Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!

Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
---------- Post added at 01:43 AM ---------- Previous post was at 01:41 AM ----------
Xero258 said:
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Click to expand...
Click to collapse
If you unlock bootloader & root, and modify some system files, OTAs may not be able to pass some pre-install checks, at least this has happened to me on N4 before. I added one line to /etc/build.prop, also one of the older SuperSU versions had to be uninstalled for pre-install OTA checks to pass.

Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
Click to expand...
Click to collapse
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.

I see some Desire folks
Did u order one chromium?

Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.

talz13 said:
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
Click to expand...
Click to collapse
If you wipe cache exactly after you unlock the bootloader, without booting, no.

Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
Not yet. Hoping to eventually get it though.

Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful
Click to expand...
Click to collapse
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app

Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
I'm not a really famous desire user but yes I bought it. Did you buy it to? Happy to see some other desire users.
Sent from my HTC Desire using XDA Premium 4 mobile app

Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?

boysetsfire said:
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
Click to expand...
Click to collapse
It should work fine, but whats wrong with booting it up for the first time?

Chromium_ said:
It should work fine, but whats wrong with booting it up for the first time?
Click to expand...
Click to collapse
Nothing wrong, just the laziness of not wanting to do the initial setup two times

Chromium_ said:
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Click to expand...
Click to collapse
abaaaabbbb63 said:
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
Click to expand...
Click to collapse
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?

Whyzor said:
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Click to expand...
Click to collapse
Yes that is correct, they do not boot. I will update the OP now, sorry for the confusion.
Originally I had read the following threads and it seemed that they were somewhat functioning, but it is now confirmed that neither one boots.
TWRP
CWM

[GUIDE] Root/Flash for Xiaomi Redmi 2

AnandMore's How-To Guide For Beginners
Xiaomi Redmi 2
{
"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"
}
Intro:
This thread will serve as a location for basic how-to guides for the Xiaomi Redmi 2. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index:
Post #1 - Rooting your Redmi 2
Post #2 - Flashing Custom Recovery
Post #3 - Flashing Custom ROMs
Post #4 - Flashing Custom Kernels
Resources:
Everything you need for Xiaomi Redmi 2 is available in the below given thread -
[INDEX] Xiaomi Redmi 2

Rooting your Redmi 2:
This guide will root your device through Stock MI Recovery(Works with TWRP also), but this is not Native Root. A new app named SuperSU will be installed, which will give root Permission.
Note:
Rooting does not Void Warranty.
Caution:
This is a safe process, but I am not responsible for anything bad that happens to your phone.
In most cases this approach of rooting should not block OTA updates.
Steps to follow for rooting:
Download the Root.zip and Copy the file to the folder 'Internal storage' (root of internal storage).
(File at the end of thread)
Open the Updater app, Press the 3 dots at Right Top Corner, A menu will open. Tap on “Choose Update Package“ and select the Root.zip File.
Wait until device will reboot.
After reboot a new app SuperSu will be installed.
Open the app and Choose "Continue".
Choose "Normal", Don't Choose TWRP/CWM, device will go into Boot Loop.
Note - Don't Choose TWRP/CWM, it will brick your device.
After sucessful updation , press ok.
Your Phone has now Root Permission.
Open any app using Root permission and SuperSU will ask for Permission.
Enjoy your rooted Redmi 2.
Un Root The Device:
For Un Root , open the SuperSU app,tap on Settings, Choose Full Unroot.
Your Device is Un Rooted Sucessfully. The SuperSU app will be removed.

Flashing Custom Recovery:
From Mobile:
Install Flashify app from Playstore
Once installed, access the application through app drawer.
Allow root access now and get navigate to Flashify’s home screen.
First take a backup of your recovery in case something goes wrong. (RECOMMENDED)
Now tap on recovery image and by "Choose the file" menu locate the .img file you want to flash.
After successful flashing it will ask you to reboot your device.
Done! You have custom recovery on your phone.
From PC:
Enable USB debugging, go to settings>about phone and then tap on Android/MIUI version 5 times. Developer Options will be enabled. Now go back to settings>Developer options and enable USB debugging.
ADB and Fastboot Drivers installed on your PC. I can provide you the drivers but it would be a better option to install MiFlash to get all the necessary drivers and Miflash software with you for future use.
Install Miflash on your PC. Lets suppose we installed it in C:\Xiaomi folder.
You can see two folders, proceed to "adb' folder
Then proceed to "Google" folder.
Proceed to "Android" Folder.
We are at our destination.
Now Hold down "Shift" button on your computer keyboard and right click with mouse on an empty part of the window. You will see that in the menu that appears, you have an option - "open command window here". Click on that
To verify if ADB is working and installed correctly, type "adb version" in the command window that opened without the code. You should get the adb version which means its working fine.
Turn off your Phone. When its completely switched off, press and hold "Volume Down" and "Power" button together and then the phone will turn on in Fastboot mode.
Use the USB cable to connect Phone to PC.
Copy the Recovery.img in the Android folder where we are running the Command prompt. (C:\Xiaomi\adb\Google\Android in my case as i installed Mi flash in C:\Xiaomi folder)
Now go back to command promt and enter the following commands -
Code:
fastboot devices
Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command to flash recovery image -
Code:
fastboot flash recovery recovery.img
Once you enter this command, the recovery image will be flashed on your device. Once it is completed, enter the final command to reboot your phone -
Code:
fastboot reboot
Your phone will reboot.
You have have now completed flashing custom recovery replacing Stock Mi recovery on your Xiaomi Redmi 2.

Flashing custom ROMs:
Steps to Follow:
Download and transfer the custom ROM you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
Select “Wipe” from TWRP main menu and do a “Swipe to Factory Reset” on the bottom of screen.
Note: This will factory reset your device. If your custom ROM doesn’t require a factory reset, then simply skip this step.
Go back to TWRP main menu, tap on “Install” and select the custom ROMs .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom ROM installation process. This may take some time.
Once your ROM is successfully flashed, you’ll see “Wipe cache/dalvik” option, select it and then do “Swipe to wipe” on bottom of screen.
Once cache & dalvik wipe completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom ROM you just flashed. Since this will be the first reboot after flashing a new ROM, it might take some time to rebuild cache and finish boot, have patience.

Flashing Custom Kernels:
Steps to Follow:
Download and transfer the custom Kernel you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
In the TWRP main menu, tap on “Install” and select the custom Kernel .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom Kernel installation process. This may take some time.
Once flashing completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom Kernel you just flashed. Since this will be the first reboot after flashing a new Kernel, it might take some time to rebuild cache and finish boot, have patience.

For list of all available Roms visit this thread :
http://forum.xda-developers.com/redmi-2/how-to/available-custom-marshmallow-roms-redmi-t3278535
Click to expand...
Click to collapse
Better if you make lollipop ROMs thread too

Superb work bro thanks ...u

Isn't MIUI rooted out of the box already? [emoji52]

Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
Developer ROMs are. Global ROMs aren't.
Device comes with global ROM :3

noobpremium said:
Better if you make lollipop ROMs thread too
Click to expand...
Click to collapse
I made both lollipop and marshmallow roms in one thread. So you think i should make seperate one for lollipop.

Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
All roms(Beta,developer,stable) for Redmi 2 are not Pre rooted.

Added videos tutorials for better understanding.

Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?

my phone also rebooting. please help me. how to go to recovery?

srmohanrajan said:
my phone also rebooting. please help me. how to go to recovery?
Click to expand...
Click to collapse
1) Switch off the phone.
2) Press the Volume Down, Volume Up and the Power Button at the same time, about 2-3 seconds until the mi logo shows up.
3) Recovery mode menu will appear.

Fr3ak23 said:
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
Click to expand...
Click to collapse
Follow the same steps to boot into recovery and flash SuperSU v2.4.6 zip via recovery
(And remember you are responsible if anything happens to the device)

omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!

Fr3ak23 said:
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Click to expand...
Click to collapse
No problem bro !
✌

Great !

New CM 12.1 is awesome, finally the camera works
I am curious on why I keep on losing root access. I never had that issue with any other phones and custom ROMs.

[tutorial] root samsung galaxy a6 plus a605g

DISCLAIMER This is the method which worked personally for me after trying out a number of attempts. Try at your own risk. I am not responsible for any bricked devices.
First of all I would like to appreciate @topjohnwu for his amazing Magisk Project and being wonderful people around in XDA. It is because of the Magisk project that the A6 plus got root although having no stable twrp.
Directions
First of all you need to download the following files :
Latest version of ODIN
7Z Zstandard
Samsung USB Drivers
Stock Firmware of your model ( Use Sammobile or Updato)
Magisk Manager v6.0.0 apk ( https://******************/ or xda thread )
After downloading all of these tools, install 7zip Zstandard , Odin and Samsung USB driver in your Pc or Laptop. After that you need to extract your stock firmware if it's in compressed zip with 7zip. Now , there will be 5 files AP, BL, CSC, HOME CSC and CP. You need to extract AP file to get boot.img of your device . Select the AP file , right click > 7zip Zstandard > Extract Here.
Once decompressed you will find your boot.img.lz4 in there. again extract it using 7zip Zstandard and you will get your boot.img .Now transfer this boot.img to your android device.
Install Magisk Manager latest version (v6.0.0 as of now) in your phone and got to settinngs and select patched boot output format to img.tat . Return to the homepage of app and tap on install now. From the two options, select Patch boot image and browse to your boot.img. From here, a black terminal will appear and Magisk will download the root zip and patch your boot image to be ready for Magisk su. Once it is done with the process, it will show you the location if the patched image file. Now, Copy this patched image to your desktop and make sure you have both, the stock boot.img and the patched boot.img in case something goes wrong. In your device go to Settings > About Phone > Software Information and tap on the Build number for around 7 times until it shows “Developer settings has been turned on” . Now come again to the settings of your device and move to bottom. Below About Phone you will find Developer Settings. Go and tick on OEM Unlock there . It will ask for a reboot , allow it to perform that. Now follow the final steps given below:
1) Download Odin to your laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+Volume up buttons together and then connect the USB cable)
4)Press the Volume up button to continue.
5)Open Odin on your laptop/pc.
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the patched boot.img file you created.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the boot image flashed successfully.
11) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy A6 PLUS !!!
{
"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"
}

Thanks bro for the root method and detailed tutorial.. will i have to follow the same steps to root my sm-a605f device !!

kifayat83 said:
Thanks bro for the root method and detailed tutorial.. will i have to follow the same steps to root my sm-a605f device !!
Click to expand...
Click to collapse
Ys

kifayat83 said:
Thanks bro for the root method and detailed tutorial.. will i have to follow the same steps to root my sm-a605f device !!
Click to expand...
Click to collapse
Hello
Did you try this method?
Plz inform me if it worked for you

My OEM unlock option gone. try to reflash patched boot img but got an error iyhat only official binary can be flash

badagila said:
My OEM unlock option gone. try to reflash patched boot img but got an error iyhat only official binary can be flash
Click to expand...
Click to collapse
Hi
Does this method work for you?
pinoy here
thankz
---------- Post added at 13:36 ---------- Previous post was at 13:02 ----------
Dev-sahil (Devil) said:
DISCLAIMER This is the method which worked personally for me after trying out a number of attempts. Try at your own risk. I am not responsible for any bricked devices.
First of all I would like to appreciate @topjohnwu for his amazing Magisk Project and being wonderful people around in XDA. It is because of the Magisk project that the A6 plus got root although having no stable twrp.
Directions
First of all you need to download the following files :
Latest version of ODIN
7Z Zstandard
Samsung USB Drivers
Stock Firmware of your model ( Use Sammobile or Updato)
Magisk Manager v6.0.0 apk ( https://******************/ or xda thread )
After downloading all of these tools, install 7zip Zstandard , Odin and Samsung USB driver in your Pc or Laptop. After that you need to extract your stock firmware if it's in compressed zip with 7zip. Now , there will be 5 files AP, BL, CSC, HOME CSC and CP. You need to extract AP file to get boot.img of your device . Select the AP file , right click > 7zip Zstandard > Extract Here.
Once decompressed you will find your boot.img.lz4 in there. again extract it using 7zip Zstandard and you will get your boot.img .Now transfer this boot.img to your android device.
Install Magisk Manager latest version (v6.0.0 as of now) in your phone and got to settinngs and select patched boot output format to img.tat . Return to the homepage of app and tap on install now. From the two options, select Patch boot image and browse to your boot.img. From here, a black terminal will appear and Magisk will download the root zip and patch your boot image to be ready for Magisk su. Once it is done with the process, it will show you the location if the patched image file. Now, Copy this patched image to your desktop and make sure you have both, the stock boot.img and the patched boot.img in case something goes wrong. In your device go to Settings > About Phone > Software Information and tap on the Build number for around 7 times until it shows “Developer settings has been turned on” . Now come again to the settings of your device and move to bottom. Below About Phone you will find Developer Settings. Go and tick on OEM Unlock there . It will ask for a reboot , allow it to perform that. Now follow the final steps given below:
1) Download Odin to your laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+Volume up buttons together and then connect the USB cable)
4)Press the Volume up button to continue.
5)Open Odin on your laptop/pc.
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the patched boot.img file you created.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the boot image flashed successfully.
11) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy A6 PLUS !!!
Click to expand...
Click to collapse
Hi sir..
i want to try this method but the problem is when i try to unlock OEM...
its says that it will reset my phone to its factory settings
did this method still works if i do that?
before, unlocking oem will just restart your device but now it will reset to factory defaults..
Im using android security patch level (July 1,2018)

Not sure it worked
Hello,
Thank you for the tutorial.
I tried this method, and seems like it didn't work. I'm not really sure, beause I used one root checker app, and it says it's not rooted, and used another one that said it is :silly:
Anyway I installed titanium backup that said root is not granted, although on the bootup image of the phone the're's something written in yellow.
And more, I cannot log in to my samsung account anymore, seems I'm in to flash again.
Edit : My phone is an a605F, but I think it doesn't matter.

Dev-sahil (Devil) said:
DISCLAIMER This is the method which worked personally for me after trying out a number of attempts. Try at your own risk. I am not responsible for any bricked devices.
First of all I would like to appreciate @topjohnwu for his amazing Magisk Project and being wonderful people around in XDA. It is because of the Magisk project that the A6 plus got root although having no stable twrp.
Directions
First of all you need to download the following files :
Latest version of ODIN
7Z Zstandard
Samsung USB Drivers
Stock Firmware of your model ( Use Sammobile or Updato)
Magisk Manager v6.0.0 apk ( https://******************/ or xda thread )
After downloading all of these tools, install 7zip Zstandard , Odin and Samsung USB driver in your Pc or Laptop. After that you need to extract your stock firmware if it's in compressed zip with 7zip. Now , there will be 5 files AP, BL, CSC, HOME CSC and CP. You need to extract AP file to get boot.img of your device . Select the AP file , right click > 7zip Zstandard > Extract Here.
Once decompressed you will find your boot.img.lz4 in there. again extract it using 7zip Zstandard and you will get your boot.img .Now transfer this boot.img to your android device.
Install Magisk Manager latest version (v6.0.0 as of now) in your phone and got to settinngs and select patched boot output format to img.tat . Return to the homepage of app and tap on install now. From the two options, select Patch boot image and browse to your boot.img. From here, a black terminal will appear and Magisk will download the root zip and patch your boot image to be ready for Magisk su. Once it is done with the process, it will show you the location if the patched image file. Now, Copy this patched image to your desktop and make sure you have both, the stock boot.img and the patched boot.img in case something goes wrong. In your device go to Settings > About Phone > Software Information and tap on the Build number for around 7 times until it shows “Developer settings has been turned on” . Now come again to the settings of your device and move to bottom. Below About Phone you will find Developer Settings. Go and tick on OEM Unlock there . It will ask for a reboot , allow it to perform that. Now follow the final steps given below:
1) Download Odin to your laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+Volume up buttons together and then connect the USB cable)
4)Press the Volume up button to continue.
5)Open Odin on your laptop/pc.
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the patched boot.img file you created.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the boot image flashed successfully.
11) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy A6 PLUS !!!
Click to expand...
Click to collapse
done SM-A605GN, thank you and here is binary 8 patched file to help others

''''''Samsung a6 plus sm 605gn root''''''
The Directoins give are 100% correct
Should work with right firmware
Majisk works and updates itself corectly
Majisk patches firmware app file corectly
Odin works corectly
Every 100% ok
'''''THE STUPID QUESTION''''
The Samsung a6 plus sm 605gn was brought ''NEW boxed 2 days ago'12th ..Aug..2022 '''(2019 new and never used)
Phone was flat needed 12 hours charge
As as phone booted it came up as Android 9 with 2019 patch
As soon as it found interest it started to update itself
After a hour it finished update and after final reboot
the a6 plus is now Android 10/10q with 2021 patch
The Stupid question is what firmware do I root with Android 9 or Android 10

[Android 11] Unofficial Lineage OS 18.1 for A21s

WARNING + DISCLAIMER:
By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
Click to expand...
Click to collapse
I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.
Click to expand...
Click to collapse
After doing some research on this device, I was able to port LineageOS. The original sources are based on Galaxy Tab S6 Lite Wi-Fi version (gta4xlwifi), with some heavy modifications made for the A21s. In the process, I was able to fix some of the problems that were found on GSI (MTP, Fingerprint removal issues, NFC, Wi-Fi hotspot and direct), and added in some enhancements to the kernel.
Unfortunately, installation of this ROM requires Lineage Recovery, and since FBE (File-based-encryption) is enabled by default, it is incompatible with the TWRP.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOT WORKING:
- Cell Broadcast (Emergency Messages) is broken in South Korea. The phone shows notifications, but the messages appear broken. Not sure about other countries. FIXED in South Korea as of 2021/9/2. However, its functionality in other countries hasn't been tested.
- Samsung's Proprietary Apps
- In order to use Wi-Fi Direct, you need to install a Wi-Fi direct sharing app from Google Play, as LineageOS doesn't have a sharing app installed by default
- Auto Brightness (The phone doesn't have the sensors for it anyway)
- On very rare occasions(probably once in more than 20 boots), the device's RIL (Phone calls, Data) might start up late when booting. If you see "No service" after booting, please wait for 30-60 seconds.
- VoLTE & VoWifi(not tested) - Unfortunately, this is located deep within Samsung's framework. AOSP-based roms for other Samsung devices don't support it either. Someday, this might be fixed.....
WORKING:
- Everything Else
GITHUB:
Device Source Tree: android_device_samsung_a21s, android_device_samsung_universal3830-common
Kernel: android_kernel_samsung_universal3830-common
Instructions for Installation:
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate.
- ROM
- Recovery / Recovery(for U6)
- Google Apps
- ADB
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
4-1. As a test, type "adb devices". After typing it, the phone should show a screen that asks you to grant permissions for USB debugging. Select Yes.
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
11. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
12. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
13. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Apply update->Apply from ADB. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
14. After choosing Apply from ADB, type "adb sideload <the path where you saved the ROM file>" on the command prompt and press enter.
<CONTINUED ON THE NEXT POST>

15. If everything goes right, the device should show "script succeeded: result was [1.000000]" While ADB may show errors such as "Failed to read command" at 47%, this is no problem as long as the device says that the script succeeded.
16. Now it is time to install Google apps. On the phone, tap on Apply from ADB again, and on the computer, type "adb sideload <the path where you saved Google apps to>" and press enter.
17. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon shown below.
18. Choose Wipe data/factory reset, and reboot the device.
19. If everything went well, the phone should reboot into LineageOS. Set up the device and Enjoy!

ADDITIONAL TIP: HOW TO ROOT THE PHONE ON LINEAGE 18
On Lineage 18, I patched the kernel so that it would have no problem with the official Magisk app.
Therefore, you DON'T need to use a version that has been modified for A21s.
If you want to have root, you can get the Official Magisk App.
1. Download & Install Magisk from the official source.
2. Select Install. When it asks you to select the boot image, choose the boot image from the Lineage OS ROM file that you downloaded from the step above. After patching the boot image, move & rename it to something you can type easily (ex. /sdcard/rooting.img)
3. Enable developer settings (Settings->About phone->Tap on build number)
4. Go to developer settings and enable USB debugging & root permissions for usb debugging.
5. Connect the phone to the PC.
6. Open the command prompt, and type "cd <the folder where you installed adb>. After that, type "adb root". If the phone asks you for permissions for USB debugging, allow it.
7. After the adb shows "Restarting adbd as root", type "adb shell dd if=/sdcard/<the path to saved boot image>" of=/dev/block/by-name/boot". The output should be something like
" *** records in
*** records out
*** bytes (** M) copied, *** s, **M/s"
8. After seeing the output above, reboot the phone. After rebooting, it should be rooted.

Good news. Thank you very much

Then, my friends, write here how it works and thank you for your observations

Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc

Pharcanal40 said:
Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc
Click to expand...
Click to collapse
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..

Gxzllen said:
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..
Click to expand...
Click to collapse
A217F on U5

Pharcanal40 said:
A217F on U5
Click to expand...
Click to collapse
Can i download it on u6?i'm afraid my phone brick if i do it

Gxzllen said:
Can i download it on u6?i'm afraid my phone brick if i do it
Click to expand...
Click to collapse
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.

grccorps said:
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.
Click to expand...
Click to collapse
nice thankyou bro

Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin

Pharcanal40 said:
Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin
Click to expand...
Click to collapse
Ohh okay its easy this way

Can I use adb fastboot instead of Odin?

Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.

NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Thank you for your review. It's such a great news that it's working on U6.
Yes, PUBG is a hell of a game, Krafton has done such a great job with it The kernel has newer mali graphics driver (R26P0 -> R31P0), maybe that could've done the trick (or it may just be due to LineageOS being much, much lighter than One UI)
How is the battery? While I wasn't able to find any abnormal battery drains (both in standby and stress conditions), I'm concered about how it would perform in other devices.

NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exchange?

Phuc230204 said:
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exc(hange?
Click to expand...
Click to collapse
First look on A21s LineageOS 18.1

hi,so i get this message "only official released binaries are allowed''in download mode,after the vbmeta failed...
SM-A217F/DSN
and in frp hijacker i get ''check device connection or com ports''

Update:so i succeded to hijack my phone after the error but it wouldn't boot into recovery,and i got everytime a screen with a warning that my phone is not using samsung's official software,and when i press the power button to continue,like it shows,it boots automatically into android.
So what should i do?
And do i need root to do this?