Database Users

i9505 doens´t boot after flashing stock firmware

Hello
I was trying to update my friend´s i9505 to the latest AntaresOne CM12 build, but forgot to flash gapps, and since i coulnd´t for some reason enter CWM (the phone just reboots), i had to flash stock firmware over again so i could start over.
But now the phone isn´t booting even on stock firmware. That usually did the trick.
The wierd thing is that Phils Touch Recovery was working before, but ever since i used Triangle Away to reset binary counter, the recovery won´t boot up anymore.
The only way that i could get into Phils Recovery was to install the TWRP recovery installer, and throught the app i would tell it to flash, and it would reboot into Phils Recovery
Now since system isn´t booting, i can´t install and use the TWRP installer to reboot into recovery mode for me.
Tried to flash stock recovery, the same thing happens: the phone just black screens, vibrates and reboots.
Any ideas of why this might be happening?

Go to stock recovery if you can and wipe data/factory reset. Install stock ROM then.

@guguts
As clearly wrote in 1st post of my thread, you need to do "format /system" before installing ROM's builds starting from 26/11 one and latest ones, including 3/12 and the ones that will come in the future.
I strongly suggest you to take a look again at installation instructions, but this time carefully.
If you need anything else, write directly in its Q&A thread (you can find it in this section) where surely you can be helped more and better
Inviato dal mio GT-I9505

Flash a custom recovery with Odin. Uncheck auto-reboot before flashing.
Then boot into the recovery using the botton combo. Keep holding it as long as it takes to enter recovery.

Hey guys, i managed to work it out.
It was probably a loose vol up or home button, because i didn´t do anything but a few moments later i tried to enter stock recovery and it went fine.
The issue was not with the custom rom (which by the way is great, my friend says its running smooth).
The issue happened because i forgot to do i data wipe after installing the rom and prior to installing the stock rom.
So the stock ROM was trying to load using lollipop data and cache, and thats why it got stuck in the samsung logo.
As soon as i managed to enter stock recovery again, and made a data wipe, the stock room booted fine.
So i tried again, but this time didn´t forget to flash gapps, and even better, now Phils Recovery is booting up normally (go figure...)
So i formated /system and /data, flashed AntaresOne ROM and gapps, and everything went fine.
Just posting here in case anyone in the future goes througyht the same hassle.
Thank you so much for your work Antares.
Its people like you, quarx and pawtip (and many others top developers) that makes this community great.

S4 I9505 - Ressurection Remix - Can't Access TWRP 3.0.0

I'm running ResurrectionRemix-M-v5.6.5-20160316 with the latest TWRP recovery and Xposed.
The last time I used the recovery was on 22/03 to make a backup of my ROM (I've entered the recovery more than a dozen times before this backup with no issues).
Today I wanted to switch from Ressurrection Remix to crDroid (Ressurrection for some reason becomes laggy after use and only a reboot resolves this issue).
I downloaded all of the zips I required (ROM, GAPPS, SU etc.)
I selected to reboot to recovery using the advanced reboot option.
The phone rebooted and displayed recovery booting in blue as per the norm.
The TWRP splash screen showed for around 10 sec or so then the phone rebooted (this never happened before).
Thinking that this was a bug with the recovery, I tried turned off the phone via the power menu once my I got into MM and then removed the battery and used the power + up button combo to enter recovery however still no go.
Next I tried flashing the TWRP 3.0.0.tar file via odin, still no luck.
The question I have is how do I resolve the issue?

Try flashing a different version of TWRP.
Or flash an twrp.img file via the app Flashify.

Ok to downgrade?
GDReaper said:
Try flashing a different version of TWRP.
Or flash an twrp.img file via the app Flashify.
Click to expand...
Click to collapse
So it's ok to downgrade to say 2.8.60 with F2FS support?

Fixed!!!
jdhot2 said:
So it's ok to downgrade to say 2.8.60 with F2FS support?
Click to expand...
Click to collapse
I found a custom version of the recovery made by the JDC team http://forum.xda-developers.com/gal.../jdcteam-twrp-touch-recovery-3-0-0-0-t3312115.
I flashed the recovery using flashify.
All fixed now

OP2 Hybrid Recovery Problem

I have searched everywhere and end up with the same problem every time I try to install a custom recovery. I try many different recoveries and only old TWRP recoveries will boot but will not allow me to flash roms. I was using a modified custom recovery for the longest and was the only one I've managed to use, it was 3.0.1 IIRC by kinglilrowrow. Using this recovery I could flash roms. Now I can't find this recovery anywhere. Currently I can only boot into recovery using First Aid from the forum but have not been able to flash any roms.

Finally was able to flash TWRP 3.0.2-2 not sure how it worked. Went back to stock recovery and oxygen rom then followed the same guide but it worked this time. All the info and files from XDA so big thanks to the site and developers.

Sounds like you where stuck on the old bootloader, which would explain why newer recoverys didn't want to boot. Should have been solved by updating to OxygenOS 3. ?

How do I install any other ROM on Redmi 2 Prime currently running MIUI 8?

I am currently using MIUI 8 and i hate it.
I want to go back to Resurrection Rom. But the problem is when installing, i think i used wrong command and flashed the boot image (fastboot flash boot).
Now if i install any ROM other than MIUI 8, it does not work. Goes into bootloop. I can boot into TWRP recovery using fastboot. But after successfully flashing my Resurrection Rom, the phone starts, MI logo appears and it reboots again after a screen flicker.
Please advise on how i can install Resurrection Rom again. Also i can only boot into recovery using TWRP 3.0.0, any other recovery like Stock, Philz (CWM) are not working. I can only boot into recovery using fastboot boot twrp3.0.0.img command.
Thanks

kishorer747 said:
I am currently using MIUI 8 and i hate it.
I want to go back to Resurrection Rom. But the problem is when installing, i think i used wrong command and flashed the boot image (fastboot flash boot).
Now if i install any ROM other than MIUI 8, it does not work. Goes into bootloop. I can boot into TWRP recovery using fastboot. But after successfully flashing my Resurrection Rom, the phone starts, MI logo appears and it reboots again after a screen flicker.
Please advise on how i can install Resurrection Rom again
Thanks
Click to expand...
Click to collapse
try to install with t.w.r.p 3.0.2.0

i-AM-BoReD said:
try to install with t.w.r.p 3.0.2.0
Click to expand...
Click to collapse
I edited the question. I can only boot into twrp 3.0.0, all other versions, other recoveries are not working.

kishorer747 said:
I edited the question. I can only boot into twrp 3.0.0, all other versions, other recoveries are not working.
Click to expand...
Click to collapse
If fastboot method is not working for 3.0.2.0 version then ,Just try to flash t.w.r.p 3.0.2.0.img (download from here)by flashify or rashr app.Then reboot in to recovery and flash any custom rom.
u can also flash recovery image file by your existing recovery.
And why using only fast boot command?U can boot to recovery by updater app or button combo.

Soft-Bricked, no access to recovery.... HELP!

Hey everyone.
I'm really hoping someone can help me. I just got my Redmi 2 Prime today, and before even properly setting it up I had rooted it. It wasn't long before I decided to try a different ROM. I decided on Resurrection Remix and TWRP recovery, both of which I flashed an ran flawlessly. RR booted up, everything was great.
I then tried flashing SuperSU again, after installing RR. Flashing the .zip file resulted in a boot loop, with no access to recovery, only fastboot.
What I've tried (with no success):
- Re-flashing TWRP (through Fastboot).
- Flashing CWM instead (through Fastboot).
- Flashing stock recovery (through Fastboot).
None of these have proven successful..... Can anyone give any advice on how to get out of this mess? I hardly feel up for having to take my phone into a shop without even having had it for 24 hours.....
TIA!

Fastboot flash Redmi 2 ROM. Download ROM file from MIUI forums and read the instructions there. Go to this link http://en.miui.com/a-234.html

i dont know if this comes at the right time,since fastboot is accesbile ,boot into fastboot, and flash recovery into boot(this may sound foolish but you can do it)
fastboot flash boot recovery_twrp.img
reboot,you will be taken into twrp
you can take a backup here,
now wipe all and flash the ROM.zip
anfd it should all work fine

I had the same problem when I switched from MIUI 8 4.4Kitkat to CM13 6.0
But I was able to solve it without fastboot.
RessurectionRemix and most roms esepecially CM based have "built-in" superSU manager.You just have simply to re-enable it on the developer settings.No need to flash supersu.zip,it would just make things worse.Download Flashify to boot in TWRP manually since flashing different ROMs will temporarily remove the TWRP(doing the button combination wouldn't boot into recovery,instead bootloop like you mentioned).
Then I was able to perform a restore on stock MIUI 8.
You have to download Flashify in order to manually force the phone to boot in recovery mode,since doing to volume up+power wouldn't let you.
I don't know if this is because my TWRP version only supports KitKat....or switching from 4.4-6.0 is a big gap.

Thanks for the responses!
I ended up solving the issue, though there wasn't really an issue to begin with. Turns out the button combination to enter recovery is different than stock (both volume buttons and power), though I did re-flash to the latest version of TWRP.
I'm now running Resurrection Remix without flaws!
But yeah, I realize now that CM based ROMs have a baked-in SU manager, it was foolish of me to flash the file without doing proper reading up beforehand!