Database Info

[Q] Bricked P5100? Help please!

My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!

dwl99 said:
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
Click to expand...
Click to collapse
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM

DigitalMD said:
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
Click to expand...
Click to collapse
Thanks but Odin cannot see the tablet to re-flash the recovery.

Downlods mode
Then flash new firmware

sembre said:
Downlods mode
Then flash new firmware
Click to expand...
Click to collapse
That's the problem - I cannot access download mode
UPDATE - it just started in download mode! I can manage from here!!

Just for the record you can install adb on the pc and run the command 'adb reboot recovery'. This will force the tablet to reboot in recovery mode.
Sent from my GT-I9300 using xda app-developers app

Jeez, this has taken up most of the day to fix. I came across many problems I have not previously experienced:
1. When the tablet was stuck at the boot animation and I tried to turn it off by long-pressing the power button it immediately restarted. The only way I could get it to turn off was by long-pressing the power button whilst it was connected to my PC.
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
3. Flashing CWM with Odin caused the tablet to reboot into the stock ROM which would not load, in the end I had to untick the "reboot" button in Odin, power it off then manually restart with the Vol- & power buttons.
4. The only way I could get a bootable ROM was by flashing CM10 with CWM. I tried to restore 2 previous CWM backups but on each occasion there was an error restoring the Data partition and I got stuck at the scenario at (1). The backups were made to the external SD card with CWM Touch - is the Touch version unreliable?
I would be really interested if anyone could shed any light on any of this stuff!

For how long did you let it install during the first reboot? It happened to me too, and it took about 10 minutes, maybe even more...
Also, did you try in the "Mount and storage" cwm menu the options "format system", "format data", "format cache" and "format preload" options, prior to re-flashing a ROM? I have read somewhere that for a clean install it's better to do this, as it really clears everything that could mess up the system between two different bases ROMs (like CM and stock).
What I do everytime is using in CWM these 4 "format" options, plus "wipe" system, cache and dalvik, then immediately after this I flash with cwm the new "zip" copied on the card. Then the first reboot is much longer than usual, as at this stage it installs the files, rebuild the dalvik cache etc.
Good luck
dwl99 said:
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
Click to expand...
Click to collapse

I think I gave it a good 20 mins to boot. When I got up this morning there was an error message saying that there was no room to install any more apps even though I had very few installed. Settings -> Storage would not calculate the space available so I figured that the partitions had become corrupted. I did the step by step format you described and reflashed & it all seems to be OK now.

[Q] How can I boot back into my OS?

I have a Samsung Galaxy Mini 2 GT-S6500. Its rooted and have CWM based recovery installed via ODIN-PDA.
It does not have terminal installed. Yesterday I downloaded a software name Quick Boot (root) from google play market and its icon is purple in colour. i downloaded such software because i wanted some apps like that to ease me in booting to other mode. So after installing i tried using it. So i tried the recovery mode button. it asked for SU permission and after i allowed it, it boot into CWM based recovery and i was very happy as i though it was a working app. But now, i restarted the phone millions of time but it just keep booting into the recovery mode again instead of booting back into the samsung android os. :'( i read and tried so called cold-boot but no hope, tried wipe factory data and wipe cache and wiped delvik cache from the recovery but still no hope. anyone can please help me? :''''''(

[Stock] Boot loop, wipe doesn't help

I've got a T-Mobile phone with stock updated to the last version, with TWRP 2.6.3.0 and root. Everything worked fine for a couple of months.
A month ago the phone started to boot loop with no apparent reason. I've wiped everything, re installed stock, rooted and used the phone again. I've thought it might be an app updated that screwed something.
Anyway, I've only got the basic apps on the phone and today it happened again. I've read that I need to boot into bootloader and selecr "CLEAR STORAGE", I've tried that but it goes into recovery and there I can only wipe the data. I've did that and rebooted and it didn't help.
Any other ways to fix this without re installing the rom?

I think that if you use the clear storage option, you will have to reinstall the rom. I believe it wipes the system partition as well.
If you want to do this, you should flash the stock recovery (get it here)
Go into the bootloader and select the clear storage option.
Then you can flash CWM or TWRP recovery again and install the ROM.

[HELP] Problems just after official lollipop update.

Let me start form the beginning.:-
My bootloader was locked and I was on stock 4.4.4 . I faced no problems at that time. I saw OTA notification for lollipop 5.0.2 update, downloaded it, installed it, device gets restarted, I saw new bootlogo and then bootanimation. Just after the bootanimation, the screen goes blank(back-light is still on). I waited for about 40-50 minutes, but the screen is still blank with backlight on. Tried rebooting 3-4 times but stuck after bootanimation. 1 time it booted successfully and I was presented with the lockscreen. I swiped unlock the screen but suddenly services was stopping one by one and various applications also getting force closes, even the launcher also got force closed. So I rebooted again, and again got stuck after bootanimation, getting only a blank screen with backlight on.
Now I booted my phone into recovery, factory reset it(also wiped cache manually) and then booted into system, still no good. I was getting the same blank screen after bootanimation. I tried rebooting 4-5 times and at one time, it got past the bootanimation. There I saw that the device didn't get factory reset(wallpaper, home screen icons were at that place only where it was before). Now again service got stopped and apps got force closed.
Now, I downloaded stock firmware images from here on xda and flashed it from bootloader. I was still getting blank sceen after bootanimation and occasionally it got booted and everything force closes again.
After trying everything, I unlocked my bootloader and tried flashing a custom recovery (so that i can try installing custom roms). But after successfully flashing custom recovery, I booted into recovery and find that it didn't got flashed (I was still on stock recovery). I tried flashing different custom recoveries 7-8 times, but the stock recovery persists!.
So, now the bootloader is unlocked, stock recovery is persisting after flashing any custom recovery, even the user data is persisting after factory reset, and I am unable to boot to system properly. I don't know what to do after this. Please let me know if this all means that some part of the hardware is failing in my moto g or if it can ever be come back to life.
Edit:- I have just booted into twrp Recovery(not flashed, only booted) and found that I am unable to wipe internal storage. Everything else like, dalvik cache, data, cache and system do not give error on wiping. Also, I am unable to delete any file or folder using twrp file manager
Thank you.

[Help] Flashed Franco Kernel over CM13 Stock and ended in bootloop

Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please

First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?

leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.

Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.