Database Users

Need help getting recovery option

I got a Google IO 10.1 Tab. I am trying to get the recovery option on my tab other then your basic download option and USB which I get. Can someone direct me to the right place ?

The IO tab's bootloader doesn't allow direct access to recovery like the retail version. You have to boot to it using fastboot. Put your tab in USB mode, and using fastboot: fastboot boot recovery.img.
Recovery.img can be the CWM version or the standard version. It doesn't matter. You just need the respective image to boot from. Look here for the stock image: http://droidbasement.com/galaxy/sys-backup/
I'm assuming you have the fastboot drivers installed. If not, you'll have to download the Android SDK and install them from that. The fastboot USB driver has to be force installed in windows for the Galaxy Tab 10.1. See here for basic instructions:http://scratchpad.wikia.com/wiki/How_I_rooted_my_Samsung_Galaxy_Tab_10.1_(Google_IO_edition)#Files
Or...if your already rooted, flash CWM via RomManager and boot to recovery from the options in RomManager.

FourCrows said:
The IO tab's bootloader doesn't allow direct access to recovery like the retail version. You have to boot to it using fastboot. Put your tab in USB mode, and using fastboot: fastboot boot recovery.img.
Recovery.img can be the CWM version or the standard version. It doesn't matter. You just need the respective image to boot from. Look here for the stock image: http://droidbasement.com/galaxy/sys-backup/
I'm assuming you have the fastboot drivers installed. If not, you'll have to download the Android SDK and install them from that. The fastboot USB driver has to be force installed in windows for the Galaxy Tab 10.1. See here for basic instructions:http://scratchpad.wikia.com/wiki/How_I_rooted_my_Samsung_Galaxy_Tab_10.1_(Google_IO_edition)#Files
Or...if your already rooted, flash CWM via RomManager and boot to recovery from the options in RomManager.
Click to expand...
Click to collapse
What if my Tab is just on the boot screen..... I can't even get in it. Normally I would adb reboot recovery but now I can't even do that. Is there a way to use Odin where it would erase everything and install retail software ?

Simultaneously hold volume down and the power button when you power on. This brings you to a two choice menu, usb on the left and download mode on the right. You choose by pressing volume down again and then volume up to enter the mode. To get out of either mode, press and hold power...eventually the tab reboots.
Flash the file in the first post via odin to turn your tab into a retail version with HC 3.2/Touchwiz etc:http://forum.xda-developers.com/showthread.php?t=1345995
It's completely stock and works well.
Be warned though, it replaces your bootloader with a locked, encrypted, retail version. You can still root by installing CWM recovery through odin and then flashing the root exploit via CWM recovery.

Problems While Rooting Lenovo K50a40 (K3 Note)

Many noobs New Users are experiencing Problems rooting Lenovo K3 Note on Marshmallow Rom. So this tutorial will help them Root Lenovo k3 Note and install Custom recovery.:good::good::good:
This is not a cookbook, You need to know what are you doing. Neither I nor XDA is responsible for BRICKED Devices.
Downloads:
Boot.img
SP Flash Tool
(optional)Lenovo K3 Note Stock ROM
Recovery
ADB AND FASTBOOT
Patience
Now to Root Your phone Follow These Steps:
(OPTIONAL) Flash Your Phone with Stock Rom, To do this follow these steps :
Install All the required Drivers.
Download the LENOVO K3 NOTE FIRMWARE from Above.
Now Extract SP Flash Tool And extract FIRMWARE Folder inside it.
Now Run flash_tool.exe as Administrator.
Go to Options>Download> And check both the checkbox(s).
Now Click On Scatter-Loading and navigate to Firmware>target_bin>and select MT6752_Android_scatter.txt .
and click on DOWNLOAD.
NOW connect your Device Powered OFF to your computer and Wait Till a Box Appears Saying "Download OK".
Turn ON your Mobile and complete the initialization.
Now Download the Recovery, Extract it, and load its scatter file in the SP FLASH TOOL with the same config.
And again connect the phone Powered OFF after clicking Download Button.
When it completes. Try to Boot into recovery (by holding VOL+, VOL- and Power button simultaneously).
IF TWRP boots You are good to Go. :good::good::good:
Now Reboot into system and open Settings>DEVELOPER Options and click on USB DEBUGGING and ALLOW OEM UNLOCK.
Now Extract ADB and FASTOOT tools (and PLACE boot.img in the folder) and shift+right-click in the folder and select open command window here.
and type
Code:
adb devices
allow ADB to connect on your phone and then type
Code:
adb reboot-bootloader
Now your phone will reboot in FASTBOOT MODE type
Code:
fastboot devices
if it shows your device then type
Code:
fastboot flash boot boot.img
then type
Code:
fastboot reboot
After that switch off your Phone and boot into recovery.
Now install the SuperSU zip.
Hurray Your Phone is ROOTED.
If you Have Any Problems please Reply :crying::crying:

What's the encryption key of recovery file

Rishi.Nerd said:
What's the encryption key of recovery file
Click to expand...
Click to collapse
I have Updates the Links They should now be working fine.

Albert
Anunay.j said:
I have Updates the Links They should now be working fine.
Click to expand...
Click to collapse
..... i finish to root but my device wont start anymore

custom rom installation without rooting
I have s433 firmware android 6.0,
1. if I just want to install twrp ( without rooting), do I need to flash boot.img
2. if want to install custom ROM and still don’t want to root, do I need to flash boot.img
3. after a litte bit googling i found i need to have an unlocked bootloader and custom recovery for flashing custom rom ,
how do i unlock bootloader ( is boot.img fot that )

Flashing custom ROM on my S5 Neo G903W

I feel like I am doing something wrong here and can't figure out
I have a Samsung Galaxy S5 Neo (Virgin Mobile, Canada) G903W
I have been looking at this thread to flash LineAge OS
I can't post link but its title is
Lineage OS 14.1 for Galaxy S5 Neo (G903F, s5neoltexx) Nougat ROM
on cyanogenmod website
First off is unlocking bootloader and install TWRP, which looks simple but it isn't
Pre note: OEM unlock is enabled, rooted with chainfire/odin, USB debugging is on
I have installed ADB Fastboot on my Windows 10 PC
Got the correct TWRP image (twrp-3.1.1-2-s5neolte.img)
Then I used the instruction to download TWRP with adb
typing adb reboot bootloader just reboots the phone normally. I can still get to download mode by using combination of home+power+volume down
fastboot oem unlock just sits at <waiting for device>
same thing with fastboot flash recovery twrp-3.1.1-2-s5neolte.img
I seem to be able to flash it with Odin by pressing AP and choose the tar file but upon rebooting to download mode it just shows normal download mode screen, not TWRP.
This is my first post here, if I made any mistake or needed any more information please let me know.

deXterlab97 said:
I feel like I am doing something wrong here and can't figure out
I have a Samsung Galaxy S5 Neo (Virgin Mobile, Canada) G903W
I have been looking at this thread to flash LineAge OS
I can't post link but its title is
Lineage OS 14.1 for Galaxy S5 Neo (G903F, s5neoltexx) Nougat ROM
on cyanogenmod website
First off is unlocking bootloader and install TWRP, which looks simple but it isn't
Pre note: OEM unlock is enabled, rooted with chainfire/odin, USB debugging is on
I have installed ADB Fastboot on my Windows 10 PC
Got the correct TWRP image (twrp-3.1.1-2-s5neolte.img)
Then I used the instruction to download TWRP with adb
typing adb reboot bootloader just reboots the phone normally. I can still get to download mode by using combination of home+power+volume down
fastboot oem unlock just sits at <waiting for device>
same thing with fastboot flash recovery twrp-3.1.1-2-s5neolte.img
I seem to be able to flash it with Odin by pressing AP and choose the tar file but upon rebooting to download mode it just shows normal download mode screen, not TWRP.
This is my first post here, if I made any mistake or needed any more information please let me know.
Click to expand...
Click to collapse
just dl twrp for ur device as .tar file and flash with odin, same procedure with CF-root
here's the link https://dl.twrp.me/s5neolte/

By default Odin will reset after flashing, you need to disable this and try again. Go to the options tab and disable "Auto-Reboot".
You must boot directly to recovery mode on the first boot, otherwise it will automatically override everything and go back to the stock bootloader. TWRP warns you about this in the instructions.

Fastboot is not an option for the s5 neo. Because theree doesnt seem to be a bootloader option. Odin. Adb only will work with adbd insecure app. Or modding sbin file
---------- Post added at 05:53 AM ---------- Previous post was at 05:46 AM ----------
Make sure you have developer mode open on your phone. Select allow oem. Or set to unlock. Make sure usb debugging is enabled.
Turn the phone off.
Volume down+home button+power to open the download mode on your phone.
Open odin on your PC. Select AP
Make sure your phone is detected. You make need usb drivers..
When you see you phone on odin and the file you selected is checked by odin.
Click start. Done. Of course you must know this if youre rooted. Oops. Otherwise do that first. Same process but with the autoroot file

I'm pretty sure the problem is flashing a ROM for G903(F) on a G903(W) device

JeffG79 said:
I'm pretty sure the problem is flashing a ROM for G903(F) on a G903(W) device
Click to expand...
Click to collapse
thats not a problem at all
the differences between all s5 neo models (G903F, G903M and G903W) are so minimal that you can ignore them safely
the main differences are that they are made for different countries to meat their mobile standards (eq. support the lte bands that are used in that country)
i havent found a single critical difference between these devices based on their specs

neokronic said:
Fastboot is not an option for the s5 neo. Because theree doesnt seem to be a bootloader option. Odin. Adb only will work with adbd insecure app. Or modding sbin file
Click to expand...
Click to collapse
Is this true? I'm actually facing the same situation as the OP with a SM-G903F here. Just asking out of curiousity, not actually trying to flash the device.

Phone doesn't get recognised in Download mode (bootloader)

Hi Guys
So my current goal is to root my galaxy S10+ (SM-G975F) running exynos with android 11. I've seen many methods that are supposed to work for android 11, some more complicated than the others.
The method I chose to stick with, is to enter bootloader through adb using cmd on my computer and to flash twrp that way. (Bootloader is unlocked already)
After that I should be able to install magisk via twrp to complete the root access.
My inital thought was to flash twrp via odin, because odin did recognize my phone after entering bootloader. The problem was that after flashing twrp with odin and performing vol down + power then bixby + vol up + power which normally makes you enter twrp, I got stuck in a bootloop. After that I had to flash the stock ROM via Odin to "repair" my phone.
From what I've read this is due to the vbmeta protection mechanism, that you need to deactivate to avoid bootlooping.
So I heard that you can extract the boot.img file from the official firmware and edit the file with HxD Binary editor to replace a bitcode's value with a series of 0's. Unfortunately I couldn't find that specific code in boot.img.
So the remaining option was to manually flash vbmeta.img and to disable verity verification via cmd.
This is where the big problem lies, my PC does not recognize the device as soon as I enter Download mode. I tried every possible fix I could find online, they all revolve around installing certain drivers and applying them to the device in the device manager. Apparently the device needs to appear in the device manager under "other devices" with a yellow triangle then you can manually select a driver to install. Unfortunately as soon as I enter Download mode (Via cmd command or manually) my device totally disappears from the pc. Only Odin still recognises it somehow.
I installed official android device drivers, specific drivers for bootloader etc.
Every online guide about solving this problem needs you to locate the device and to apply certain drivers to it, but nothing appears for me.
I hope somebody can help me

Format data?

What your twrp version ? your twrp version must be version support 11.

You cant flash Magisk via TWRP. It doesn't work, Install the magisk App

Wrong place to ask this stuff

Problems installing a custom ROM on Grand Prime Duos (SM-G530H)

I have a Grand Prime Duos (SM-G530H), currently running an Android version 4.4.4 and I wanted to install a custom ROM to have a higher version of Android. (Tried installing LineageOS 17.1 from itexpert.120, but any custom ROM with a higher version of Android would do)
Problem 1: No custom recovery seems to work.
I installed the TWRP app and tried to flash 4 different versions of their recovery images (from twrp-3.7.0_9-0-fortuna3g.img to twrp-3.4.0-0-fortuna3g.img) and all of them resulted in a unless glitched gray recovery screen.
I also tried the CWM app but it fails to download a recovery image for the device, tried looking online for a image file but didn't find one either.
In the end I reverted the recovery to the default one that I had backed up.
Problem 2: ADB works but fastboot doesn't.
I downloaded the ADB tools to try and flash the ROM from my computer instead. The ADB commands work, but when the device enters recovery mode the fastboot commands don't work. ("fastboot devices" doesn't even list the device)
Went to check the drivers. Most tutorials say to open the device manager and look for the phone device with an exclamation mark and update the driver with ones downloaded from the official site. To my surprise the device doesn't show up at all in the device manager (not even with an exclamation mark). Trying to install the drivers anyway says it's already installed.
The Odin software showed the same problems, detects the device when it's on, but doesn't detect it when in recovery mode.
Problem 3: Error when installing directly through the recovery mode options.
This probably wouldn't work for technical reason I'm not aware of, but I went and tried anyway. On the default recovery mode there are 2 options, apply update from ADB and apply update from external storage. Tried both, the first using the command "adb sideload <lineage rom file>" and the second using the ROM file in a SD card. Both begin to unpack and install the file but after a while throw an error "E: failed to verify whole-file signature", then the device boots to the usual OS.
So, is there anything else I can try? any other recovery images or hacks that won't give me the glitched recovery that TWRP had? Or another method to install a ROM without fastboot? Maybe using another file format in problem 3?
OBS: the device is rooted and has no "OEM unlock" options in its settings

delete the samsung usb drivers and install an older version. only way you can flash custom recovery is with odin. only way to flash custom rom is with custom recovery. fastboot and sideload wont work, this isnt a nexus

You think the reason why the custom recovery was glitched is because it was flashed through the TWRP app and not Odin? Seems unlikely. Is there any non-TWRP recovery image for my model you can point me to?