Database Info

[Q] Tablet only boots in recovery mode P3110

I have a Galaxy Tab 2 7'' Wifi (P3110) with CM 10.1.3.
Thing is, I wanted to install the latest nightly, so I booted in Recovery mode, tried to install the zip file and I had a Status 7 error. So after that I decided to stay with my CM version, but when I try to boot the tablet it goes to recovery mode and doesn't boot! I tried to wipe everything and still. I can't flash anything else (not even the CM version I already have) because I keep getting the Status 7 error.
I am desperate, I don't know what to do!

Well, you attempted to flash CM11/Omni with the wrong recovery, that's why you got the "Error 7"
Anyway, the problem should be easy to rectify.
1. Install ODIN3 on your computer (don't forget to also install the Samsung USB drivers as well).
EDIT In case you are about to install the drivers by installing "Kies" ... make SURE that NONE of the Kies components are running in the background (on Windows) once you try to flash with ODIN3 - or it won't work. If you Google around for a bit, there are several Downloads for JUST the USB drivers - I can upload you the USB drivers installer I used for my P3110 (flashed back to Stock to sell it off)) /EDIT
2. Download the correct .tar.md5 recovery file for the ROM you're going to use from Android Andi's file repository.
For CyanogenMod 11 you want to grab either PhilZ Touch or CWM Swipe Edition, for OMNI you want to grab TWRP.
3. Start ODIN3 and select the <recovery>.tar.md5 as a PDA file (make sure that nasty checkmark at "Repartition" is NOT checked"!)
4. Power on the tablet and make sure you get it into Download Mode
If it boots into Download Mode itself, that fine. If not just press... was it Power + VOL Down?... until you see the screen telling you to pres VOL up to proceed into Download Mode.
5. Connect the tablet to the computer (wait a second in case Windows decides to install the driver)
6. Flash the recovery
7. Disconnect after flash, jump into the recovery, flash CM11 or OMNI
Of course you can also flash back to Stock ROM (given you have the ODIN flashable tar.md5 at hand), verify that it boots after flashing, get into download mode, flash the custom recovery, flash the custom ROM.

BoneWithABeagle said:
Well, you attempted to flash CM11/Omni with the wrong recovery, that's why you got the "Error 7"
Anyway, the problem should be easy to rectify.
1. Install ODIN3 on your computer (don't forget to also install the Samsung USB drivers as well).
EDIT In case you are about to install the drivers by installing "Kies" ... make SURE that NONE of the Kies components are running in the background (on Windows) once you try to flash with ODIN3 - or it won't work. If you Google around for a bit, there are several Downloads for JUST the USB drivers - I can upload you the USB drivers installer I used for my P3110 (flashed back to Stock to sell it off)) /EDIT
2. Download the correct .tar.md5 recovery file for the ROM you're going to use from Android Andi's file repository.
For CyanogenMod 11 you want to grab either PhilZ Touch or CWM Swipe Edition, for OMNI you want to grab TWRP.
3. Start ODIN3 and select the <recovery>.tar.md5 as a PDA file (make sure that nasty checkmark at "Repartition" is NOT checked"!)
4. Power on the tablet and make sure you get it into Download Mode
If it boots into Download Mode itself, that fine. If not just press... was it Power + VOL Down?... until you see the screen telling you to pres VOL up to proceed into Download Mode.
5. Connect the tablet to the computer (wait a second in case Windows decides to install the driver)
6. Flash the recovery
7. Disconnect after flash, jump into the recovery, flash CM11 or OMNI
Of course you can also flash back to Stock ROM (given you have the ODIN flashable tar.md5 at hand), verify that it boots after flashing, get into download mode, flash the custom recovery, flash the custom ROM.
Click to expand...
Click to collapse
Thanks! I didn't know that was a recovery problem!
Somehow I couldn't reboot into Download mode with the key combo so I used ADB for that, and flashed the new recovery with Heimdall (in the CMW official website the versions are old, maybe that was the problem...).
Then I installed CM.
Thanks again!

ultrachilled said:
Somehow I couldn't reboot into Download mode with the key combo so I used ADB for that
Click to expand...
Click to collapse
I am aware you managed to flash the ROM, but just as a hint about "this is a trap for young players":
IF your tablet is connected to the wall wart (power supply) or to the USB port of computer while trying to trigger the key-combo to hop into download mode or recovery it won't work! Your tablet needs to be _disconnected_!

Update Recovery!
hey you can try update your custom recovery to latest version by downlading the zip file here http://forum.xda-developers.com/showthread.php?t=2548257
and than try re-flash your current rom or any kitkat room for your device

Not able to install - always standard recovery menu

Hello guys.
Im struggeling to install a custom ROM at the stage of installing a CWM recovery. My S2 plus 9105p runs Android 4.2.2 and everytime I try to upload a recovery img via Odin everything works fine as expected but when I try to start (volume up, home, power) the recovery mode - it gets always into the standard Android one - not CWM recovery!!! It looks like Samsung has integrated some kind of security mechanism which keeps us from running custom ROMs...
I have realy tried maybe 5 different recovery images, but non of those worked for me.
Can you please help?
THX

try flashing the files used in this guide

karamancho said:
try flashing the files used in this guide
Click to expand...
Click to collapse
I tried exactly also this particular site and steps described on it, but didn't help... The same problem. Everything was OK, but recovery was not CWM but standard Android one.

When u have flashed ur recorvery, take ur battery out and then plug battery again. And now go to recorvery.

Now it is WORKING !
Hi guys.
I followed the step-by-step guide on this page:
http://forum.xda-developers.com/showthread.php?t=2560928
- used the CWM 6.0.4.5 and Odin3 0.7
- after successfull flash of the PDA with this recovery (manualy unset the auto-reboot option) I have pulled the battery out for a couple of seconds
- the battery came back in again and with home-volUP-Power I got directly to the new CWM recovery.
So thanx all for your support and you can lock this thread as everything is working now.
DETAILED STEPS FOR INSTALLING CWM RECOVERY IF THE PHONE AUTOMATICALLY RE_FLASHES IT:
Installation
WITH ODIN
1. Be sure, that your device is on 4.2.2 stock firmware and shut down the phone
2. Be sure that Samsung drivers are installed on your pc. Just install Kies or google for them
3. Download Odin 3.07(google it) and the CWM-Recovery image (in this case CWM 6.0.4.5 )
4. Open Odin as administrator
5. Start-up the phone by pressing Vol_DOWN + Home + Power so you get into the flash-menu.
6. After reading the disclaimer and warning stuff - simply press Vol_UP and plug the USB cable to the PC and Phone
7. In ODIN click on PDA and select the downloaded CWM-recovery (*filename*.tar.md5) . Check - "F. Reset Time" and UNCHECK!! -> "Auto Reboot"
8. Click start and wait until the blue progress bar in your device is graphicaly 100% (I also suggest to wait another minute to make things sure..)
9. Pull out the battery
10. Pull out the uSB cable from PC and phone
11. Wait abou 10-15 seconds and power up your phone to get into the recovery menu by pressing: Vol_UP + Home + Power
12. DONE

!SOLVED! S6 stuck in bootloop after TWRP-flash ( !SOLVED !)

SOLVED!
Hey there,
i just tried flashing TWRP (twrp-3.1.0-0-zeroflte.img.tar) via Odin (Odin3_v3.12.4_4) on my Samsung Galaxy S6 on nougat 7.0 and am stuck in bootloop (GALAXY S6-Bootscreen reappearing every 6 seconds). My device is not rooted, but i do have access on TWRP 3.1.1-0 and the Download Mode. I did not care about tripping knox as PingPongRoot doesn't support my Buildnumber (yet).
Is there any way to fix the bootloop without resetting my device to stock?
I tried wiping the caches, but nothing changes.
Any help is appreciated! :angel:
Download mode says:
Product name: SM-G920F
Current binary: Custom
System status: Official
Reactivation lock: Off
Secure download: enabled
Knox warranty void: 1 (0x030c)
Ap Swrev: B:5 K:2 S:2
Note:
I do have a root file (N920_Nougat_Root_SuperSU-No_kernel_included.zip) on my device that could be installed via TWRP, but that doesn't help at all, right?

Reflashing – Odin doesn't recognize S6
I tried reflashing, but Odin does not recognize the S6 at all.
No device is beeing 'added'.
Could i transfer my user data (pictures, music) via adb through twrp to my computer?
I didn't backup, stupid as i am

Problem solved!
I solved the problem by flashing the root file (N920_Nougat_Root_SuperSU-No_kernel_included.zip) via TWRP-Recovery.
After this step, the phone rebooted and all my user data remained. Root & TWRP working just fine. :good:

JoLien said:
I solved the problem by flashing the root file (N920_Nougat_Root_SuperSU-No_kernel_included.zip) via TWRP-Recovery.
After this step, the phone rebooted and all my user data remained. Root & TWRP working just fine. :good:
Click to expand...
Click to collapse
Can you tell the step you took to flash your S6 with TWRP. I have S6 G9200 dual sim. When i flash with TWPR my phone could not boot again. it kept repeating Samsung logo every 6 second.
Thank you

Baba Kay said:
Can you tell the step you took to flash your S6 with TWRP. I have S6 G9200 dual sim. When i flash with TWPR my phone could not boot again. it kept repeating Samsung logo every 6 second.
Thank you
Click to expand...
Click to collapse
1. Google or baidu the following twrp unofficial build "TWRP-3.1.0-G9200-G9208-G9209-G920D-G920P.tar" (Official TWRP builds will not work because they are for G9200 HK version)
2. Open Odin 3.1x.x and and uncheck the "Auto Reboot" option
3. Put the G9200 onto download mode and flash
4. Disconnect the usb cable
5. Hold "Volume Down + Power" (Hard restart) for 5 seconds and once screen goes black immediately release and hold "Volume up + Home + Power" (Launch Recovery)
6. You should see TWRP working If you did above steps correctly.
7. Now you got TWRP but OS is stuck in bootloop.
8. Flash latest Magisk or SuperSu with TWRP.
9. You're good!

KittyChampion said:
1. Google or baidu the following twrp unofficial build "TWRP-3.1.0-G9200-G9208-G9209-G920D-G920P.tar" (Official TWRP builds will not work because they are for G9200 HK version)
2. Open Odin 3.1x.x and and uncheck the "Auto Reboot" option
3. Put the G9200 onto download mode and flash
4. Disconnect the usb cable
5. Hold "Volume Down + Power" (Hard restart) for 5 seconds and once screen goes black immediately release and hold "Volume up + Home + Power" (Launch Recovery)
6. You should see TWRP working If you did above steps correctly.
7. Now you got TWRP but OS is stuck in bootloop.
8. Flash latest Magisk or SuperSu with TWRP.
9. You're good!
Click to expand...
Click to collapse
Thank you
Great job. it works for meeeee

Baba Kay said:
Thank you
Great job. it works for meeeee
Click to expand...
Click to collapse
Did you figure out a way to install Google Play?

KittyChampion said:
1. Google or baidu the following twrp unofficial build "TWRP-3.1.0-G9200-G9208-G9209-G920D-G920P.tar" (Official TWRP builds will not work because they are for G9200 HK version)
2. Open Odin 3.1x.x and and uncheck the "Auto Reboot" option
3. Put the G9200 onto download mode and flash
4. Disconnect the usb cable
5. Hold "Volume Down + Power" (Hard restart) for 5 seconds and once screen goes black immediately release and hold "Volume up + Home + Power" (Launch Recovery)
6. You should see TWRP working If you did above steps correctly.
7. Now you got TWRP but OS is stuck in bootloop.
8. Flash latest Magisk or SuperSu with TWRP.
9. You're good!
Click to expand...
Click to collapse
What version of Magisk should I flash? I read that v14 has problems...

alex27riva said:
What version of Magisk should I flash? I read that v14 has problems...
Click to expand...
Click to collapse
V14 worked fine for me

It checks MD5 than says please wait and stops responding (nvm it was a bad file)

Had same problem, but more intense - my phone did not react to pressing VolumeUp+Home+Power, just bootlooped even in this mode
I don know how much time I pressed VolumeDown+Power (like 2 minutes), but eventually it just powered down
After that I was able to boot into twrp
In TWRP I flashed Magisk16 and wiped dalvik cache
Now It works
Also e2fsck'ed /dev/block/sdaSOMETHING
P.S. sorry, English is not my language

Samsung S6, cannot flash
i have samsung s6 sm-g920i, which is stuck in bootloop mode, i can however go to download mode but i can't flash it using odin with any files (stock rom, custom rom, combination file, twrp )
can't see any increase in the bar of the phone when the flashing process starts ( the phone is just as it is before no line of process increase shown), the phone is recognized by odin ( it shows added with blue line on the com part) but the problem is i can't flash anything in it.
flashing always fails.
won't go to recovery mode as well.
current binary : custom
system status : custom
reactivation lock : off
secure download : enabled
knox warranty void : 1
ap swrev : 8:3 K:2 s:2
sw rev. check fail. device : 2 binary : 1
can anyone please help
thanks in advance

KittyChampion said:
1. Google or baidu the following twrp unofficial build "TWRP-3.1.0-G9200-G9208-G9209-G920D-G920P.tar" (Official TWRP builds will not work because they are for G9200 HK version)
2. Open Odin 3.1x.x and and uncheck the "Auto Reboot" option
3. Put the G9200 onto download mode and flash
4. Disconnect the usb cable
5. Hold "Volume Down + Power" (Hard restart) for 5 seconds and once screen goes black immediately release and hold "Volume up + Home + Power" (Launch Recovery)
6. You should see TWRP working If you did above steps correctly.
7. Now you got TWRP but OS is stuck in bootloop.
8. Flash latest Magisk or SuperSu with TWRP.
9. You're good!
Click to expand...
Click to collapse
You are genius! Thank you very much bro. You saved me! ❤

JoLien said:
Problem solved!
I solved the problem by flashing the root file (N920_Nougat_Root_SuperSU-No_kernel_included.zip) via TWRP-Recovery.
After this step, the phone rebooted and all my user data remained. Root & TWRP working just fine. :good:
Click to expand...
Click to collapse
thank you very for this, i kinda panicked a little after flashing twrp and it stucked at boot loop. i needed my stock rom before flashing different rom. luckily a quick search there i find similar issue
only one problem, i had to make a back up again with supersu after i booted the phone haha

[Solved]GT P3110 stuck in recovery mode, Not detected in ODIN, No APK recovery

I was trying a new ROM after installing mobile odin (pro) and superSu. However after failed installation the tab is restarting in recovery mode only ( screen shot attached). It is neither detected by odin nor can I install any apk as it is not booting further. I have wiped all data and caches and also have the recovery image (cwm and one supplied by mobile odin) but both are showing signature verification failed due to stock <3e>. So if somehow I can bypass the signature verification , I can load the backup. In short--
1. Tab not detected in PC ( via ODIN) , which was perfectly detected earlier. So no method via PC possible.
2. Tab not going beyond recovery mode, so no APK installation is possible.
3. It can read from SD card in recovery mode , but every image ( I know they are good, as used them earlier) is showing " Signature verification failed" and aborting.
4. I have a working CWM image but cannot install it due to reason 3 ( probably <3e> is the culprit).
I have searched the forum as far as I could but found all solutions are either PC based or APK based.

When you are in recovery, is the tab detected via adb from pc?

bukaida said:
I was trying a new ROM after installing mobile odin (pro) and superSu. However after failed installation the tab is restarting in recovery mode only ( screen shot attached). It is neither detected by odin nor can I install any apk as it is not booting further. I have wiped all data and caches and also have the recovery image (cwm and one supplied by mobile odin) but both are showing signature verification failed due to stock <3e>. So if somehow I can bypass the signature verification , I can load the backup. In short--
1. Tab not detected in PC ( via ODIN) , which was perfectly detected earlier. So no method via PC possible.
2. Tab not going beyond recovery mode, so no APK installation is possible.
3. It can read from SD card in recovery mode , but every image ( I know they are good, as used them earlier) is showing " Signature verification failed" and aborting.
4. I have a working CWM image but cannot install it due to reason 3 ( probably <3e> is the culprit).
I have searched the forum as far as I could but found all solutions are either PC based or APK based.
Click to expand...
Click to collapse
Signature verification fails because you are on stock recovery. Also have you tried booting in to download mode then plugging the USB cable to your tablet, then pressing volume up to start the download mode, then plugging the other end to your PC while odin is running? It should get detected

Power+ Vol up and Power + Vol down both are going to recovery mode. Plus getting an error 'logo_espresso7.jpg' draw failed at initial screen. Is there any <3e> compatable recovery without signature verification failed that can be run from sd card directly?
Ps: This happened when I tried to install "crdroid-5.1.1-20151103-p3110" via mobile ODIN pro.
The Tab is not detected in ADB server either.

bukaida said:
Ps: This happened when I tried to install "crdroid-5.1.1-20151103-p3110" via mobile ODIN pro.
Click to expand...
Click to collapse
The rom was meant to be installed with twrp or other custom recovery and not via mobile odin.

john99ap said:
The rom was meant to be installed with twrp or other custom recovery and not via mobile odin.
Click to expand...
Click to collapse
Yeah, the fault is mine, lack of knowledge. But what now? Can I recover my Tab ?
please help.

[Solved Problem]
The problem is solved. I finally could figure out that the culprit was the external volume down key ( not letting me go to download mode). So I opened the back cover as the last option and press the soft points corresponding to volume down and power together with two tooth-peaks. And voila , it issued the warning screen, and pressed up and it went to download mode. Connected with odin, flashed and load cwm recovery . Now that <3e> kernel is also gone.
Ps. It was weird about the Vol key behavior as it was working fine in both side in recovery mode during selection.

bukaida said:
The problem is solved. I finally could figure out that the culprit was the external volume down key ( not letting me go to download mode). So I opened the back cover as the last option and press the soft points corresponding to volume down and power together with two tooth-peaks. And voila , it issued the warning screen, and pressed up and it went to download mode. Connected with odin, flashed and load cwm recovery . Now that <3e> kernel is also gone.
Ps. It was weird about the Vol key behavior as it was working fine in both side in recovery mode during selection.
Click to expand...
Click to collapse
if you want to install the latest roms, you should update to the latest common twrp from android-andi http://andi34.github.io/recoveries_tab2.html
cwm recovery is outdated and causing issues with the latest roms

Is twrp safe to run from mobile odin? Will it automatically overwrite installed cwm?

bukaida said:
Is twrp safe to run from mobile odin? Will it automatically overwrite installed cwm?
Click to expand...
Click to collapse
install twrp as zip with your current cwm. its the easiest way. twrp will replace cwm, yes.

Samsung J400F stuck in loop after flashing custom recovery TWRP

Hello people!
I have a J400F phone model, I was working with android 9 rooted & working well, I updated to android 10 with a fresh install, the phone works well, and I wanted to use a custom recovery TWRP and root the phone, it stuck in boot loop, this is how I flashed:
- Used Odin with the latest stock firmware "J400FXXU6CTGO".
- restart the phone, and the bootloader is already unlocked "OEM Unlocked".
- Downloaded TWRP for J400F from halabtech, flashed it, then rebooted to recovery.
- In home screen, Wipe --> Format.
- With TWRP I flashed RMM_Bypass_v3_corsicanu.zip then no-verity-opt-encrypt-6.1.zip
After this I tried booting to system but then It kept rebooting after reaching the samsung logo.
Any help is appreciated guys.

I managed to access the download mode by taking out the battery, put it back in the phone, connect it to USB in the computer, press vol down and home button and you should be able to enter the download mode to flash the stock ROM (still reading on the second part).