I installed TWRP 3.3.0 sucessfully on my Redmi 2 prime which was lagging a lot to install a custom rom. I wiped out all the previous data using twrp recovery mode. I had my rom zip file on my sd card. So to mount that ( had to remove battery) I reboted my phone without an OS. now I am unable to go into recovery mode. When I try power + Volume up button, my phone keeps getting rebooted in a loop. Using volume down + power button I am able to go into fastboot only. How can I get into recovery mode. Please help!!!!
I have a backup of stock firmware (excluding data) on a sd card.
PS: I read a similar thread here for a samsung device. The guy solved his problem using odin. what should I do.
Related
I installed the ICS update manually and used it for around 2 days and suddenly my power key stops working, and my bootloader is unclocked but the phone was not rooted.
The phone works Fine, everything is working...
then i pulled out the battery to goto recovery mode, and bam, the phone entres recovery mode but the volume kes does nothing, power key does nothing, and the phone is not even detected in recovery mode by my PC at all...
i can't do anything......
please help me out what do i do????
i can still pull out the battery and the phone automatically restarts, without pressing any key and boots normally and as everything works fine...
but i am stuck, i can't use recovery mode nor my power key
Very similar to my problem in this thread here
http://forum.xda-developers.com/showthread.php?p=26578138#post26578138
Your phone is compatible with the clockwork recovery touch?
Edit
Excuse is the nexus s forum, so it is compatible xD
Make the root of your phone with any application in the market and install the recovery ClockworkMod touch with Rom manager premium or Rom toolbox Pro. Restart recovery using Rom manager or Rom toolbox and do a full cleaning on the phone. Wipe only data and cache.
Now, select from mount and storage mount USB storage and copy over to your i9020 storage any rom ( try using the cm9 ). If the installation is successful restart, if not try some other roms. More than that I do not know how to help.
P.s.: In theory it should go smoothly, otherwise I do not assume any liability for further damage to the phone ... Good luck!
Hey
So I have a Samsung Galaxy Tab 2 7.0" GT-P3110.
I followed this guide to flash my tab with a 4.2.2 ROM.
Everything went fine, all downloaded and everything, I wiped the memory, and formatted the device, and then when I pressed choose zip from external sd, it said it wasn't mounted. I then pressed back, and the device rebooted. Now it just shows the samsung boot logo, and shuts down.
I can't get back into recovery mode now!
I tried pressing power on and volume up + down at the same time, doesn't work.
What do I do D:
There is a backup of the OS on the actual device itself, I made one before, so I figured that if I can get back into clockwork recovery, i can install the backup, and then copy over the ROM to the internal storage where I can install it from there.
But i can't get back into clockwork recovery mod D: Help, please!!
Update
CommanderZT said:
Hey
So I have a Samsung Galaxy Tab 2 7.0" GT-P3110.
I followed this guide to flash my tab with a 4.2.2 ROM.
Everything went fine, all downloaded and everything, I wiped the memory, and formatted the device, and then when I pressed choose zip from external sd, it said it wasn't mounted. I then pressed back, and the device rebooted. Now it just shows the samsung boot logo, and shuts down.
I can't get back into recovery mode now!
I tried pressing power on and volume up + down at the same time, doesn't work.
What do I do D:
There is a backup of the OS on the actual device itself, I made one before, so I figured that if I can get back into clockwork recovery, i can install the backup, and then copy over the ROM to the internal storage where I can install it from there.
But i can't get back into clockwork recovery mod D: Help, please!!
Click to expand...
Click to collapse
I can boot into download mode though, if that helps.....
CommanderZT said:
I can boot into download mode though, if that helps.....
Click to expand...
Click to collapse
If its the same procedure like my Galaxy S, you have to search for a firmware, most likely 3part
and restore trough Odin...
CommanderZT said:
I can boot into download mode though, if that helps.....
Click to expand...
Click to collapse
Flash stock rom using odin pc, choose rom for p3110 I suggest
Make sure your using odin 1.85, it's never let me down.
HI, I'm using a Samsung Galaxy S3 Neo for the past 2 months.. Went for an upgrade to Kitkat OS. All steps were done including the zip files download, odin (latest version). Flashing was successful using odin, entered recovery mode, cleared data/cache, mounted SD card and selected the specific custom ROM zip file. But phone got stucked in "download mode" after rebooting, without pressing any keys other than the power button. I'm not able to enter the recovery mode either after this. Please help me to resolve this. Is this due to soft brick or any firmware issues?
Okay so I'm not new to rooting, flashing custom roms, or using custom recoveries, but this one has stumped me.
After reading and researching several poorly written/translated guides I set out to flash the Miui6_5.3.20_r827_b3wok custom rom on my Oppo Find 5 Mini. I copied the CWM for the R827 into the sd card, using Mobile Uncle MTK tools to install it. I successfully rebooted into CWM, selected the factory reset option (wiping data and cache) and then format /system and wiped the dalvik cache. I then installed the zip of the custom rom, with no errors. However, the custom rom needed a patch, specifically the "VPN-Fix by Louise - AICP v10 - R827" which acc. to the instructions were supposed to be patches BEFORE gapps.
Now the problem is that at the end of flashing that patch, it automatically reboots the phone, so I held the power button while the Oppo logo was there and booted into CWM again. I then flashed gapps, and rebooted the device.
However, I am no longer able to get into CWM, nor does the Oppo logo move/progress. Pressing Volume Down + Power to get into recovery mode turns on the phone with the text =>Recovery Mode in the bottom left, but instead of going into CWM it now just turns off the screen, vibrates, and proceeds to boot as if I never attempted to go into recovery mode in the first place.
Is this phone well and truly bricked? Fastboot mode (Volume Up + Power) just vibrates the phone and turns it off, so theres no way I can do a adb reboot or sideload. I can however copy files to and fro the microSD card via a separate card reader, if it helps.
Thanks for helping , and sorry for the long read...This really is my last hope. :crying:
Update: Okay so I went to the Oppo store and after about 40 minutes they somehow both fixed it and updated to the ColorOS with Kitkat.
OP resolved.
Thread closed.
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.