Database Info

[Q] Various Flashing Issues

I've searched and found a few different solutions for each of my problems. However, nothing has resolved the issue.
I tried to flash CM 11.0 to my Galaxy Tab 2 (GT-P3110) and now I can't get anywhere but my CWM Recovery screen.
When I try to install the ROM, I get a "Status 7" error. I've attempted the steps found here but they have not worked.
So, I decided to just recovery what I had before - easy enough. But then when I attempt to recover, I get an error of "MD5 Mismatch".
I've looked up ways to resolve this issue, but I can't complete the steps for 2 reasons. Firstly, I can't get to my File Explorer because my tablet won't completely boot. Secondly, my laptop has stopped recognizing my tablet for some reason. So, I'm unable to edit the file from there.
Lastly, when I just try to reboot system, I get an error explaining that I "may" have lost root access. If I select to "fix" this, it does nothing - just reboots back to recovery. If I choose no, same thing.
I've cleared dalvik, cleared cache partition, cleared data/factory reset, and formatted system - nothing makes a difference.
Any help is greatly appreciated. Thanks everyone.

IS there kitkat update for tab 2. Please inform about That}.

chandru andriod said:
IS there kitkat update for tab 2. Please inform about That}.
Click to expand...
Click to collapse
I believe so, yes.

@ohhello update your recovery. your recovery needs to be up-to-date to flash KitKat Roms. Link in my signature, all my latest recoverys can handle KitKat-Roms.

Android-Andi said:
@ohhello update your recovery. your recovery needs to be up-to-date to flash KitKat Roms. Link in my signature, all my latest recoverys can handle KitKat-Roms.
Click to expand...
Click to collapse
Okay - easy enough.
If I'm unable to get to ROM Manager, is there a way to update my Recovery within Recovery Mode?
I've zipped the .img file for the update.
Should I just install the zip from Recovery Mode?
THANKS!

download a flashable zip for your device from my thread and flash it in recovery. after that reboot the recovery to see the new recovery.

[Q] to root or not to root

Hello,
1st.: while starting this new thread, I looked through the automaticly generated similar threads and found non that was suiting my problem.
Last night I unlocked the bootloader of my wifes Xperia L (C2105) and got stuck into an boot loop. After this I had the need to flash an original rom (4.1.2). This results in an total wipe of the phone :crying:
Now the phone has an unlocked bootloader and an old Android Version. I want to install the pacman rom 4.4.4. I know i have to use cwm or twrp to do this, but do I need to root the device?
I'm a little bit confused. I thought installing the *.img-File from TWRP, with the folloing command, will get me the recovery option an with this option
Code:
c:\fastboot\Fastboot.exe flash boot C:\fastboot\openrecovery-twrp-2.8.4.0-taoshan.img
Can anyone help me out?
My wife is not upset, but with the boot loop from last night in my mind, I'm quit unsure what to do next.
many thanks in advanced
Felix

you need to root the device and use flashtool by androxyde(Easier and user friendly), first download the rom and put it in internal/external memory and then install thunderzap 4.12 by select bootkk.img and install it in fastboot mode in flashtool, now enter the recovery go into wipe and format options and choose clean to install a new ROM and then flash the pac rom and reboot

Root isn't necessary.
Download PAC ROM, Take boot.img inside the zip.
Flash boot.img via fastboot.
Boot into recovery, wipe data / factory reset.
Flash ROM and GApps.
That's it

NOP, you dont need to root to install a custom rom
felix leiter said:
Hello,
1st.: while starting this new thread, I looked through the automaticly generated similar threads and found non that was suiting my problem.
Last night I unlocked the bootloader of my wifes Xperia L (C2105) and got stuck into an boot loop. After this I had the need to flash an original rom (4.1.2). This results in an total wipe of the phone :crying:
Now the phone has an unlocked bootloader and an old Android Version. I want to install the pacman rom 4.4.4. I know i have to use cwm or twrp to do this, but do I need to root the device?
I'm a little bit confused. I thought installing the *.img-File from TWRP, with the folloing command, will get me the recovery option an with this option
Code:
c:\fastboot\Fastboot.exe flash boot C:\fastboot\openrecovery-twrp-2.8.4.0-taoshan.img
Can anyone help me out?
My wife is not upset, but with the boot loop from last night in my mind, I'm quit unsure what to do next.
many thanks in advanced
Felix
Click to expand...
Click to collapse
you can download the rom, extract it and keep, boot.img file, in fastboot folder, and also keep the downloaded rom zip file in sd card for later use.
than you can use use fastboot commands to flash those boot.img which will install the recovery into your phone, than .
use reboot command in fastboot, it will reboot your phone, take out your cable, using volume up key go to recovery,
there clear all the cache and delvik cache file, then, install your custom rom by selecting from your sd card, it will take a bit of time for first time, so don't worry,
than you are done,

Rooted Galaxy s5 (sm-g900p [5.0]) Stuck on Yellow Sprint Screen - Im finally Stumped!

Phone Info:
Samsung Galaxy s5 (sm-g900p) (Sprint)
Android Version 5.0
Build: LRX21T.G900PVPU1BOA6
Hi, Thank you ahead of time to anyone who might have a minute to help me out. I have been combing XDA and as well as some other sites trying to find a solution myself but given my limited experience in this area Im at the point where I thought it best to stop and ask for help rather than do the wrong thing and have my phone blow up in my hands TNT style
I rooted my s5 a few weeks ago using Odin with C-f--auto-root, which went perfectly and I had zero issues afterwards.. This was only my second rooted device so of course I was exploring all of my new options out there to customize my phone.
The problem occurred after installing the apps Layers Manager and Layers Showcase (BitSyko Development) from the Playstore. Both seem like great apps and were not to blame for this problem, I just happened to be using them when I jacked something up.
Basically, over a day or two I tried several Layers Themes and they applied just fine, but one did not. Shortly after applying the Layer, and rebooting my phone I ended up on the bright Yellow Sprint Spark startup screen and my phone wont budge past this point.
I am able to boot into Recovery Mode as well as Download mode. I tried wiping the cache Partition as i had read to do as well as doing a full data clear and reset ,but it still; wouldnt move past the yellow screen. Then I very carefully followed directions to flash the stock firmware using Odin, making sure i used the right one for this phone and Odin displayed PASS! at the end. From what i could tell, it all went fine... But it STILL wont move past that enraging yellow screen!!
I think I may have missed something in regards to flashing stock firmware but i dont know. Ive read some other suggestions and things to try but, like i said, at this point and with my limited experience, I thought it best to concede and ask the experts for some help.
I hope I included any information needed...

Are you waiting long enough to allow for loading? Did you try installing a stock rom that matches bootloader version?

gdrocks said:
Are you waiting long enough to allow for loading? Did you try installing a stock rom that matches bootloader version?
Click to expand...
Click to collapse
Hi, thank you for your reply. Yes, the stock rom i used matched the original rom on the device. I had taken some screen shots of the Device Info screen a while back for something else, so luckily i had a lot of general info right there shot the s5. And i waited a good amount of time. Odin took a few minutes and it read PASS at the end. From what i could tell, it was all done and i still waited just to be sure. But the more i think about it, the more i feel that i did do something wrong at this step. I'm just not certain what

Amandajbee86 said:
Hi, thank you for your reply. Yes, the stock rom i used matched the original rom on the device. I had taken some screen shots of the Device Info screen a while back for something else, so luckily i had a lot of general info right there shot the s5. And i waited a good amount of time. Odin took a few minutes and it read PASS at the end. From what i could tell, it was all done and i still waited just to be sure. But the more i think about it, the more i feel that i did do something wrong at this step. I'm just not certain what
Click to expand...
Click to collapse
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
DOWNLOADS
Odin 3.10.7
Stock Rom OG1
TWRP 2.8.7.0

daniel3x said:
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
Click to expand...
Click to collapse
Thank you so much! I am going to give this a try hopefully tonight, or in the morning if I cant make time tonight. I will report back once I do. Again, thank you so much for taking the time to help me out. It really means a lot! :fingers-crossed:

i had the same problem and tried over 10 other ways to fix it. i finally found this post and it worked! ty so much. was almost ready to throw the phone out

daniel3x said:
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
DOWNLOADS
Odin 3.10.7
Stock Rom OG1
TWRP 2.8.7.0
Click to expand...
Click to collapse
see, nw this is the type of post i like to see!! @daniel3x , for future reference, idoneapps.com has WAAAAAAY faster downloads then sammobile and the tar.md5 files are 100% legit! But youre reply is pretty much exactly what i would have said. I personally would have advised on OK4 vs OG1. OK4 is just easier to mess with on TWRP and stuff.

wait a while for first stock boot from yellow screen
I've read that flashing a stock firmware will take 10 to 20 or more minutes on your first boot. Let the heat sink from your body and give it time.
I want to flash to a stock as well. Can I just full system wipe in twrp and Odin og1 or ok4>what I'm currently on and would like to keep it? Should I take out my SIM? Should I take out my sd card? Will I need to re partition my ext2/4 on the sd? Does the stock image replace the bootloader? I have a twrp backup on my extsd, can I use it after attempting to flash stock? Flash stock tar/zip should stock be a tar?, Odin kltespr twrp in pda mode, leave everything alone, root method of choice, phh su so flash in twrp, should I update Odin? I have 3.07 and 3.10.6. Then wait out that initial boot. I don't want a backup of what I have now because I've done things I wantedd to revert and do differently this time as I'm not AS clueless

Amandajbee86 said:
Phone Info:
Samsung Galaxy s5 (sm-g900p) (Sprint)
Android Version 5.0
Build: LRX21T.G900PVPU1BOA6
--SNIP--
I hope I included any information needed...
Click to expand...
Click to collapse
Oh, some app permissions can cause a bootloop. Instead of flashing the whole stock rom, you can flash the recoveries through odin.
You can either:
-Flash stock recovery through Odin (BL slot) and perform a factory reset/cache wipe
-Go through TWRP and restore your backup
-Go through TWRP and wipe your cache partitions on ADVANCED WIPE
SAMSUNG S5 SPRINT STOCK RECOVERIES:
mega(DOT)nz/#!bRxE1QRD!1-mAR_T6tvb-83xohTD6Q8uNxW4TdpcqnDT3Uq6s5ms
mega(DOT)nz/#!mEwQCDrS!I8pGn8Wa4TSlCpsazD2_ZOh7t1r9sy5kJZ_ujk6viOY

Bl is the recovery? Odin can't flash a bootloader?

This salvaged my sprint phone
I had to flash back from LineageOS 14.1 to stock rom temporarily to "update profile" so I could make phone calls again after moving the phone to a new line. I tried several different versions of stock rom and flashed via ODIN, but all got stuck on the boot loop. It felt like I had searched endlessly for a solution until I came across this thread. I followed the process (Thank you @daniel3x & @youdoofus) using the stock rom ending in OK4; it worked flawlessly!
If possible, I would like to see this thread "stickied" for Sprint Galaxy S5. It will likely save other users a lot of time.
:good: :victory:

kentc said:
I had to flash back from LineageOS 14.1 to stock rom temporarily to "update profile" so I could make phone calls again after moving the phone to a new line. I tried several different versions of stock rom and flashed via ODIN, but all got stuck on the boot loop. It felt like I had searched endlessly for a solution until I came across this thread. I followed the process (Thank you @daniel3x & @youdoofus) using the stock rom ending in OK4; it worked flawlessly!
If possible, I would like to see this thread "stickied" for Sprint Galaxy S5. It will likely save other users a lot of time.
:good: :victory:
Click to expand...
Click to collapse
glad to help

Galaxy S6 only boots in TWRP

As the title already states my Galaxy S6 ( SM-G920F, 6.0.1, rooted) only boots in TWRP and I can't get out of that recovery boot loop. I already tried flashing the stock ROM but I get the SW REV CHECK FAIL DEVICE 4 BINARY 3 fail. Are there any ways to fix this, possibly without losing all my personal data(if not I'd like to know how anyways)?
I can access the download menu and I also tried wiping the Dalvik/ART Cache.
I tried this stock ROM: G920FXXU4DPIL, Switzerland(AUT)
Thanks for taking your time
EDIT: I haven't tried ADB since I'm not sure how to use it correctly and I don't want to screw up even further.

Hi mate that error means that the stock firmware you are triyng to install is a lower version than the one on the device, go online and find the most recent version, as for the data just boot to twrp make a backup of data partition, connect the phone to pc twrp as mtp turn on by default and copy the backup to pc, after the flash just reinstall twrp and restore.

Unable to install TWRP

Hi everyone,
I retrieved a Galaxy Tab 2 10.1 GT-P5110 which has a strange behavior: it boots up correctly, but always reboots after around one minute. In order to try being able to use it, I uninstalled a few apps before it rebooted, but after the reboot the uninstalled apps were still there. After that, I tried a more radical method: I booted into the stock recovery mode, and wiped data and cache. It doesn't seem to have any effect as the tablet boots with the same customized background and all the apps are still installed.
As these steps weren't successful, I wanted to wipe everything and install a new ROM: in order to do that, I need to install TWRP. I followed the instructions of the Lineage wiki to do it, but it doesn't work. Here are the steps I followed:
Boot into download mode
Flash the TWRP image with heimdall on Ubuntu:
Code:
heimdall flash --RECOVERY recovery.img --no-reboot
Wait for download success
Reboot into recovery mode
The stock recovery is still launched instead of TWRP
I have read a lot of possible issues and tried quite everything I've read and think of:
Use heimdall with different USB ports to download TWRP to be sure that it's not an USB issue
Use different images of TWRP (and even CWM) to be sure that the recovery image is not the cause of the recovery not being installed:
Code:
TWRP GT-P5110 3.0.0-0, TWRP espresso common 3.1.1-1, CWM 6.0.5.1
Disconnect the battery between the different steps described above, and particularly after downloading TWRP in order to avoid the tablet overwriting TWRP with the stock recovery at boot
Use Windows and different versions of Odin (3.10.6, 3.11.1, 3.12.2) with the No reboot option checked to download TWRP, instead of Ubuntu and heimdall
Even flash the kernel along TWRP with heimdall:
Code:
heimdall flash --KERNEL lineage/boot.img --RECOVERY recovery.img --no-reboot
It seems that whatever I try, the TWRP recovery image is overwritten by the stock recovery after I download it. Or that the tablet is protected in some way avoiding wiping data and downloading new images.
Any ideas of what I could do to be able to install TWRP on this tablet?

dohseven said:
Hi everyone,
I retrieved a Galaxy Tab 2 10.1 GT-P5110 which has a strange behavior: it boots up correctly, but always reboots after around one minute. In order to try being able to use it, I uninstalled a few apps before it rebooted, but after the reboot the uninstalled apps were still there. After that, I tried a more radical method: I booted into the stock recovery mode, and wiped data and cache. It doesn't seem to have any effect as the tablet boots with the same customized background and all the apps are still installed.
As these steps weren't successful, I wanted to wipe everything and install a new ROM: in order to do that, I need to install TWRP. I followed the instructions of the Lineage wiki to do it, but it doesn't work. Here are the steps I followed:
Boot into download mode
Flash the TWRP image with heimdall on Ubuntu:
Wait for download success
Reboot into recovery mode
The stock recovery is still launched instead of TWRP
I have read a lot of possible issues and tried quite everything I've read and think of:
Use heimdall with different USB ports to download TWRP to be sure that it's not an USB issue
Use different images of TWRP (and even CWM) to be sure that the recovery image is not the cause of the recovery not being installed:
Disconnect the battery between the different steps described above, and particularly after downloading TWRP in order to avoid the tablet overwriting TWRP with the stock recovery at boot
Use Windows and different versions of Odin (3.10.6, 3.11.1, 3.12.2) with the No reboot option checked to download TWRP, instead of Ubuntu and heimdall
Even flash the kernel along TWRP with heimdall:
It seems that whatever I try, the TWRP recovery image is overwritten by the stock recovery after I download it. Or that the tablet is protected in some way avoiding wiping data and downloading new images.
Any ideas of what I could do to be able to install TWRP on this tablet?
Click to expand...
Click to collapse
sounds like a broken emmc
http://andi34.github.io/faq.html (scroll to the bottom of the site)
the best solution for this problem is, buy a new motherboard on ebay.

smart-t78 said:
sounds like a broken emmc
http://andi34.github.io/faq.html (scroll to the bottom of the site)
the best solution for this problem is, buy a new motherboard on ebay.
Click to expand...
Click to collapse
Thanks, it seems to be exactly my problem. Guess I will try to find a new motherboard if it's not too expensive.