So I flashed a new ROM by the Spanish guys at Team Force (great looking ROM), via CWM, and so naturally I got the boot loop problem.
Normally solvable by turning off the phone, booting into recovery and then performing a factory reset, right?
Here's the problem - this appears to be one of the only android cellphones in existence where you CAN'T boot into recovery using the normal power + volume key combinations.
Essentially, I've bricked the phone without actually REALLY bricking it.
Did I miss anything, or does it sound like a quick end of line for this phone?
Edit: Well, if I connect my phone via USB and have ADB running in the background, holding the volume up key during the boot loop does bring up recovery mode.
It seems to me that the installation of said ROM simply doesn't fully complete before it tries to reboot itself, which could be why this is happening.
I think I have soft bricked my S2. Let me start by pointing out my home button does not work (not the best start!).
Any who I am able to get to download mode (Volume down and power) and flash an official firmware in Odin. However when the flash is complete and the phone reboots it enters a boot loop to the Samsung logo and round again. I am sure if I could get into recovery all I would need to do is wipe data and it would be fine however without a home button I am not sure how I can get to recovery.
Is there anyway I can get Odin to reboot the phone to recovery or at least get adb access from Odin? If I had adb I could "adb reboot recovery"
Any help welcome!
edit: Solved using guide from http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Hi. I'm new here, and I really need help!
It started today when I'm tired of a disaster lagging using android 5.1.1 rom on my Galaxy tab 10.1 (GT-P7500).
So, I decided to flash a stock rom to go back to honeycomb 3.2
And basically, a volume down button on my tablet is broken. so I won't be able to reboot in recovery mode.
I tried reboot in download mode by pressing power + volume up button but it won't work either.
Then I managed to reboot in download mode and use Odin to flash a rom by using adb cmd but I didn't boot to recovery mode and wipe data/factory reset first(I don't know if this has something to do with this problem.)
And that brought me to a dead end problem.. Stuck at the logo while booting up. :crying:
I don't really know what else to do or is there some hope with this situation. I plugged a usb to my pc while in logo screen and it showed up as SAMSUNG_Android so when I check by typing adb devices in command it's there but can't get it to work since adb required debugging mode.
I think I will probably end up order a new button for replacement but I feel like I should ask a professionals first.
PCruzio said:
Hi. I'm new here, and I really need help!
It started today when I'm tired of a disaster lagging using android 5.1.1 rom on my Galaxy tab 10.1 (GT-P7500).
So, I decided to flash a stock rom to go back to honeycomb 3.2
And basically, a volume down button on my tablet is broken. so I won't be able to reboot in recovery mode.
I tried reboot in download mode by pressing power + volume up button but it won't work either.
Then I managed to reboot in download mode and use Odin to flash a rom by using adb cmd but I didn't boot to recovery mode and wipe data/factory reset first(I don't know if this has something to do with this problem.)
And that brought me to a dead end problem.. Stuck at the logo while booting up. :crying:
I don't really know what else to do or is there some hope with this situation. I plugged a usb to my pc while in logo screen and it showed up as SAMSUNG_Android so when I check by typing adb devices in command it's there but can't get it to work since adb required debugging mode.
I think I will probably end up order a new button for replacement but I feel like I should ask a professionals first.
Click to expand...
Click to collapse
Can you flash a TWRP recovery with Odin now? TWRP can support touch screen.
987987ken said:
Can you flash a TWRP recovery with Odin now? TWRP can support touch screen.
Click to expand...
Click to collapse
Hi Ken,
I have the similar problem like him, and the recovery mode was lost, i've try to flash a TWRP with Odin (twrp3000-20160207-p4.tar.md5) with AP button, it was PASS and restart, but still stuck in logo Samsung Galaxy Tab 10.1.
I don't know what to do, this is the 1st time i get this problem.
Need someone helps, thank a lot.
I've been following the tutorial found at https://forum.xda-developers.com/general/device-reviews-and-information/blu-life-one-x-2016-t3287428 but since the rules say not to post questions in general I figured I'd make a thread here instead of asking in that thread.
I've gotten to the part where I'm flashing a custom recovery. I have no problems flashing it but after rebooting and then rebooting into recovery I'm shown the stock recovery page. I'm sure it's because my phone's rewriting CWM and TWRP with the stock recovery, but I've been unable to find a way around it. The steps I've done to try and reboot into CWM/TWRP (I've tried both):
Use the adb reboot recovery command. This results in booting into stock recovery.
Use the fastboot boot cwm.img command to boot directly into the recovery mode. This results in the phone booting normally.
Shutting down the device and holding VolUp, VolDown, and Power simultaneously at boot. This results in the phone being stuck/frozen with a "Meta mode" text found at the bottom left of the screen.
Shutting down the device and holding VolUp and Power simultaneously at boot. This results in showing "Boot into recovery, bootloader, or stock" menu. Selecting recovery results in the phone booting normally.
I would find/create a custom "stock" ROM that doesn't automatically rewrite custom recovery modes with the stock recovery but I need to be able to load a custom recovery in order to install .zips. Any help in getting my phone as far away from stock as possible after reading about how the dev sells my data would be greatly appreciate.
I am having the exact same issues...why has no one in the entirety of the internet addressed this ??? We can't be the only two...
if your botloader is locked the system will keep replacing twrp with stock
Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.