Is there any working custom recovery for SGP612 witch 5.0.2 on board?
TWRP
Managed to get this installed but only booted into it once - gives me the BSOD every time I try now. Takes a couple of goes to get back into the tablet.
Related
Hi so after updating from the stock zv6 to lollipop update my phone won't install a custom ROM. Every time I try to turn it on it goes straight to TWRP and went I install a ROM or try to load a backup as soon as I hit reboot it goes back to the TWRP page. Amy ideas?
You must flash back, using Flashtool, to zv4, then reroot, then flash newest TWRP. OTA software not included, because they flash every partition of the phone, including the boot loader. Stock roms like zv6 and zv8(lollipop)or AOSP, must be flashed from xda from here on out, because they've been modified to work correctly on zv4 boot loader. TWRP and root access only work correctly with zv4 boot loader.
sent from my LG G3
It sounds like there is no OS installed or it is stuck a reboot-loop. Try pulling the battery out for 10 seconds and if it still goes into twrp you know that it isn't a reboot-loop. When you go to restore a rom and it has the bar that shows the amount of storage does it say "0 MB"? If it does it means that twrp can't mount the storage on the phone thus causing it to not install/reboot. Have you tried side loading a rom via adb? Are you trying to install a rom off of a sdcard? I have seen many issues in the past sdcard related.
If you can please answer the following:
1) What is the message you are getting from twrp (if there is any)?
2) Have you installed a custom kernel and if so witch one?
3) What twrp are you running (the bumped one from xda or from the official twrp site) and what version is it?
4) Have you tried adb and pulling the battery?
If you answer these questions they should be able to tell us all that we need to know in order to help you out.
All -
I have a Xperia Z Ultra GPe, bootloader unlocked.
I have been experimenting flashing with different builds of Cyanogenmod.
I was able to get into the Cyanogen Recovery AND Stock Recovery.
Then I was getting random "Process.acore" errors from time to time, and only resetting the phone would resolve which prompted me to flash another Kernel. After a failed flash, now I do not seem to be able to get into stock recovery anymore.
Currently the phone is on Cyanogenmod Build CM12 20150401 which I found is relatively more stable than others.
I can get into the bootloader, then when I switch to 'Recovery Mode", the led will flash once and the phone will just shut down.
I can still get into Cyanogen Recovery without any issues.
Questions are:
1. How do I fix the stock recovery? Do I need to flash another Kernel?
2. When I tried to go back to stock rom, it complained about "Signature verification failed" and would not continue. What caused that?
3. The Cyanogen Recovery functionalities are very limited. Can I flash CWM or TWRP while still using Cyanogenmod ROM?
4. I was getting "Process.Acore" error very often (about every 3-4 weeks). Does anyone who is on the stock 5.0 LP have this issue? Is that the best solution for a reliable ZU at this point? Please advise.
Thank you in advance!
Hello all,
It was unwise of me to use ALL IN ONE TOOL (http://forum.xda-developers.com/showthread.php?t=2301720) to install a custom recovery on my i545vrugoc1 running lollipop.
As a brief record:
- I updated from kitkat to stock lollipop using stock recovery (was my only option since I live in Uzbekistan) which consisted of two packages
- I got it rooted using KingRoot (from 3d try)
- I flashed stang5litre ROM following the instructions via Flash Fire
Was more or less happy but not quite since wanted a ROM which is customizable (personally hate Samsung stock notification bar). To that end ignored all warnings and tried installing custom recovery using ALL IN ONE TOOL.
As a result my phone was unable to boot normally. Searching XDA forum I came across a solution to boot the phone from download mode.
So now I kindly ask to answer the following:
1. Can anyone provide me with i545vrugoc1 stock recovery wich I could flash via odin? I want to do so in order to be able to install the future OTA updates the same way I updated from kitkat to stock lollipop using stock recovery.
2. If first is not possible then second question is: will I be able to flash future stock updates via odin? My worry is that my stock recovery is messed up and I have no idea whatsover if it is going to affect the process.
Thank you in advance
After moving SU to the phone memory the device got stuck on Samsung boot logo and refused to boot up however much long I waited
Booting problem solved thanks to http://forum.xda-developers.com/gal...pment/odin-i545vrugoc1-factory-image-t3160125
Hi I need a custom recovery for a blu life x8. If any one has one that would be great. Also for some reason it won't boot into the factory recovery. I've tried every thing it will only boot into factory mode or android os. Its rooted and on 4.4.2. I would like to try and update to 5.0 it tells me i have an update but it downloads reboots and does nothing still on 4.4.2. Any help would be great.
hello,
I downloaded Flashify and I install with it TWRP (image), but I think, I downloaded a bad version, because when I restart my phone, It can't load boot screen..
- in 4.4 android I get error message: "error: can not load invalid boot image"
- in 5.0 android I dont get any info, it stops in boot screen..
I tried to change ROM (with full wipe), but it doesn't works (5.0 --> 5.0 --> 4.4 --> 5.0, etc.)
So I cant use my phone... Have you any idea? How I solve this problem? :/
thanks!
(sorry for my bad english..)
When you get into recovery does it look stock with the android there or does it show twrp.
If its not twrp you could use fastboot to try flashing a new recovery and then boot recovery after.
Then you could just reflash the fw you have before.
That could mean that you might have flashed the recovery img under boot.
Because you only restarted your phone and it just came up like black screen.
But what confuses me is you have went to 5.0 to 4.4 somehow and the problem still exists. Im wondering how you did that exactly, is it from backups or fw files from Asus.
If its the asus fw and the problem persists It might be the recovery and you might want to flash a different one.
The 4.4fw to 5.0fw should have flashed stock recovery again and the problem would have been solved. Only if you have used the downgrade fw and bootloader gets relocked
Overall its a weird problem
You could also try to flash cm 12.1 or 13.0 using custom recovery too if the bootloader is unlocked. And it should work just fine then you could go back to stock. You just might want to back up the data partition on stock then restore it after you get back to stock