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
Related
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
I have purchased a galaxy nexus on the cheap to hold me over until the nexus 6 is out but if I can fix my note, I would like to.
I know there were other threads about this same issue but it seems that they are all on a different version of the note, or on a s3 or something. Not to mention, I don't see anything that I could try without asking for some help on here. Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Thanks guys!!!
amberkalvin said:
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
Click to expand...
Click to collapse
Before you tried to flash a custom ROM and things went wonky...were you on Verizon's factory stock 4.3 MJ9 firmware, or on Beanstown106’s modified 4.3 MJ9 with TWRP installed?
Does the phone still boot into stock recovery? If so, you may be able to fix the phone by doing a factory reset.
amberkalvin said:
Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Click to expand...
Click to collapse
If you were on Verizon's factory stock 4.3 MJ9, then you won't be able to Odin flash back to 4.1.2 or any earlier Android version because the bootloader has been locked down tight on 4.3 (and 4.4.2) with no current do it yourself method to unlock for those newer versions. You would want to restore the phone back to factory stock 4.3 though, if that's what version you were on before your phone got messed up. You can root the phone on 4.3 with saferoot, then use safestrap recovery to flash some custom Touchwiz ROM's.
If you were on the 4.1.2 based bootloader, (but running Beanstown106’s MJ9 firmware and TWRP), then you would want to restore your phone back to factory stock 4.1.2 and then root and unlock the bootloader again with CASUAL. This would give you the most flexibility with flashing custom kernels, ROM's, etc...
Check out Section 1b in Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. The guide has download links for the files you'll need to restore the phone back to the correct build version.
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.
Hi,
I've been fiddling around with Lollipop for the Z2 device today and I've got a question.
Are 5.1.1 based custom ROMs root-possible? I've first managed to make a stock pre-rooted 5.1.1 .ftf and everything was fine, both root and recovery, but my phone was overheating like crazy on it so I decided to try a custom ROM, Paranoid Android to be exact. I got the latest stable from their site and almost successfully installed it using the TWRP. Almost, because I forgot to re-flash the recovery. Then it turned out I can't root it and couldn't find a way to do so. I've since gone back to 4.4.2 using Flashtool, rooted it and installed the XZDualRecovery.
So, my question(s) is/are, what did I do wrong? Would flashing the flashable XZDualRecovery after the custom ROM and gapps sufficied? Or maybe flashing the SuperSU package? Or maybe, is it impossible to have a rooted custom ROM on 5.1.1? And if isn't, I'd be really grateful if someone supplied me with a hint or something, because I don't want to go through all the trouble only to downgrade again.
I'm using this for recovery : http://forum.xda-developers.com/showthread.php?t=2785598
And used this guide for the prerooted .ftf, though I guess it's not related at all to my questions, except the SuperSU package I'm thinking of using: http://forum.xda-developers.com/xperia-z2/general/4-4-4-creating-rooted-update-package-t2933155
Thanks in advance.
EDIT: OK, I've tried my own advice and flashed SuperSU and flashable XZDualRecovery after flashing the custom ROM and Gapps. Now the phone is rooted, but the custom recovery doesn't stick. I tried installing again using the installer version, which soft rebooted into the custom recovery, but after the manual boot the recovery was gone and the garbled screens were back.
My question has changed then, what is the way to having a custom recovery on a custom ROM on lollipop 5.1.1?
EDIT2: Nvm fixed it... , I went to NUT's website and made recovery using his kernel creator.
Sorry for wasting space then and I hope my post helps someone eventually.
You can flash superSU via recovery on any rom
Worst that can happen is it bootloops.
Hello everyone,
I own a samsung galaxy s2 gt-i9100 I've been using it for a long time. A few days ago i installed cynogenmod 13 marshmallow on it but faced some severe issues like dialler problems,battery drain,google play services not working. So, i switched it back to my previous rom i.e. cm 12.1 lollipop but my old twrp recovery got replaced by cynogenmod default recovery. Now some people who may have used it know that its very basic and does not has backup,restore, has bugs,does not flashes some zips or files that i wanted so i tried to replace it with twrp/cwm through rashr,flashify,rom manager,etc. But none of it worked, whenever I'd boot after flashing the twrp/cwm recovery it'll go back to the default cynogenmod recovery. Now, me not knowing what im doing stupidly downloaded mobile odin lite app then i downloaded the cwm kernel recovery kitkat compatible and installed via mobile odin lite. After that it got screwed, it won't just startup it'll just start and go into recovery i mean continuously! It was annoying, then i read an article on a forum to download any cm nightly or stable mod and flash it but i did a little bit of tweak of removing the recovery boot img file with twrp to get preinstalled twrp recovery but i gotta admit it was the last mistake possible. Now i sit here, with a bricked phone in my hand which is looping continuously only on the samsung logo. If anyone out there can assist me correctly it'll be a life saver for me. Thanks for reading this and please reply with a solution asap. Please! Im in danger!
can you get into download mode?
if yes you can download a stock firmware and flash but you will have to hope it will work, otherwise you will get stuck on nand write start which means the nand is stuffed/corrupted and then basically only a motherboard replacement will do the job, or you can try using another computer, reinstall usb drivers..
can you get into recovery mode?
if you can, you can flash a rom
The 'nand stuffed' assumption is a last resort, tried everything and nothing works assumption. There is *plenty* to try before assuming that the nand is 'stuffed'......
It sounds like (from your description) that you may have rendered recovery useless and inaccessible.
I've a feeling what you need to do is to go into download mode and Odin flash a firmware.
Even if it doesn't boot, you should have a recovery that you can flash PhilZ recovery from and then use that to flash a custom rom. Initially, I'd stay away from the MM builds and instead flash something KK or LP based as they're less 'volatile' and have a higher degree of stability than the MM roms.
http://i.imgur.com/rVnFwJM.jpg