I recently sidelined my Galaxy Note 2 for a Galaxy S4 and I'm running into a stability issue with the TWRP and CWM recoveries. It seems no matter what rom I use, Stock or Custom, AOSP or TouchWiz, once I flash a custom recovery and then install any custom rom - I can no longer access the custom recovery unless I reinstall it. In short every new rom I flash requires me to reflash, or install, the custom recovery again in order to access it. "Now I didn't go to math school, so I'm not going to do the math," but this wasn't an issue on the Galaxy Note 2 - so I 'm wondering if I may have missed something when I initially rooted the S4, or if there is some other issue I've overlooked. If anyone has any suggestions please speak up - I would be forever grateful for the help!
This is really weird. I haven't heard of someone having this issue on the gs4.
I'm curious as to why it does this.
BTW have you tried philz touch recovery, and see if it still does this.
Sent from my SPH-L720 using Tapatalk 4
Here mabye:beer:
http://forums.androidcentral.com/sp...61-how-unlock-install-su-custom-recovery.html
Sent from my SPH-L720 using xda app-developers app
Related
hi to all. is anyone having issus with latest DLL7?
what i mean is that i made a clean install of LL7. after rooting with autoroot i installed TWRP 2.3.2.3 cause latest gave me only black screen.
but if i want to update from 2.3.2.3 to 2.3.3.1 it does never boot to recovery bur instead it gives broken Samsung n7100 screen.
it is the same if installing any CWM recovery. so Sammy has made some really weird changes with this update.
any other info. maybe bootloader downgrade just as in S3 thread. Advices
This is a little bit like my problems but I have random reboots instead. They occur almost immediately on a clean XLL7 install flashed from Odin without any root or apps installed.
Everything works perfectly in 4.1.1.
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
mariosraptor said:
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
Click to expand...
Click to collapse
I will try that and see what will happen.
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Click to expand...
Click to collapse
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
JCVD_ said:
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
Click to expand...
Click to collapse
do not worry. he means with stock rom.
in ARHD and other custom roms bootloader is left ou of flash.
anyway. i think that sammy has changed the some partitions. twrp works but only 2.3.2.3
No the roms who are based on dll7 are safe.
The recovery imao needs to be updated.
Sent from my GT-N7100 using xda app-developers app
Do you mean that it is dangerous to flash the CWM recovery to the device when it runs XXDLL7?
I flashed the root and CWM package after flashing XXDLL7 and it seems to work (my random reboot problem is unrelated I guess since it happened even with just stock recovery in place).
Now, I have the new bootloader and radio and flashed BatteryPlus 0.2 from CWM without any problems. I flashed the CWM-root-package through Odin after flashing XXDLL7, also from Odin.
So the question is: is there a problem with CWM and other custom recoveries and the XXDLL7?
Or are we talking about flashing mods?
No it can be an issue. It's not recommended at this stage.
Sent from my GT-N7100 using xda app-developers app
If there is a problem with CWM and XXDLL7, that could perhaps explain my reboot problem in that case.
If so, I will hold off for a while and stay on my current configuration.
I have the new bootloader and radio already.
i have noticed that 4.1.2 isnt so friendly with custom recovery. I had cwm recovery and going into it, took a lot of time with 4.1.2 firmware. Maybe samsung is trying to make some higher security in 4.1.2 against custom recoveries and etc.
If they wanted they could have made it absolutely protected. No I don't think they actually wanted to increase security.
I just think the new bootloader isn't friendly with the old recovery.
Sent from my GT-N7100 using xda app-developers app
Ok... I have been reading way to much today, to the point i did something rather noobish.
Was in the dev section TWRP thread specifically looking to downgrade fron 2.6 to 2.5, saw the last post where someone posted a dropbox link of 2.5. Thought "how convenient" and flashed. But the zip was for another model number, now i cant get into my recovery.
Odin flash of the stock image is always an option. But one that I would prefer to avoid it if at all possible. I was hoping that someone else out there was well... as stupid as I am, and maybe had some advice?
Is there any possibility that goo manager will simply over right the wrong recovery image with the proper?
Or is it by any chance possible to simply flash the TWRP ZIP with Odin?
Any thoughts would be greatly appreciated, and I already know that I'm a burnout lol.
Sent from my SGH-I337M using Tapatalk 2
Just flash the 2.5 twrp zip in twrp. It'll down grade
Goo should over write it, and just to make sure ..you have the i337m -Non att variant. Youll have to see if anybody has a non loki version if twrp 2.5
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
jd1639 said:
Just flash the 2.5 twrp zip in twrp. It'll down grade
Click to expand...
Click to collapse
That's the problem... Cant get into recovery anymore.
Sent from my SGH-I337M using Tapatalk 2
mg2195 said:
Goo should over write it, and just to make sure ..you have the i337m -Non att variant. Youll have to see if anybody has a non loki version if twrp 2.5
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, was hoping someone would say that. My thoughts were the same. But after that last bout of stupidity, i guess I wanted to hear it from someone else...
Sent from my SGH-I337M using Tapatalk 2
celkin said:
Yeah, was hoping someone would say that. My thoughts were the same. But after that last bout of stupidity, i guess I wanted to hear it from someone else...
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
Can you get goomanager to install it?
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Can you use odin to flash the correct twrp with a .tar file?
Tylorw1 said:
Can you get goomanager to install it?
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, just finished a backup/restore after goo re installed 2.6.
Everything seems fine. Just with so many "brick" threads on here wanted to be careful.
The bricks revolve mostly around the newest update that locks the boot loader on the at&t s4. On the m non at&ti believe you just need a non Loki kernel but I am not positive.
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
The bricks revolve mostly around the newest update that locks the boot loader on the at&t s4. On the m non at&ti believe you just need a non Loki kernel but I am not positive.
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
If it's I337m or M919, Loki or not, it doesn't matter...
My phone is bootloader unlocked from the start from what i understand its the Canadian Rogers varient.
Im just now after reading countless threads wraping my head round this device. Its way more complex of a situation then the note 2 (previous phone).
My understanding is that we stay away from anything loki'd.
2 days in and im still not comfortable flashing any rom 4.2 or 4.3 lol. Another day or two of reading :-\
Sent from my SGH-I337M using Tapatalk 2
celkin said:
My phone is bootloader unlocked from the start from what i understand its the Canadian Rogers varient.
Im just now after reading countless threads wraping my head round this device. Its way more complex of a situation then the note 2 (previous phone).
My understanding is that we stay away from anything loki'd.
2 days in and im still not comfortable flashing any rom 4.2 or 4.3 lol. Another day or two of reading :-\
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
Ponder that, a canuck is less subject to tyranny? Your bootloader isn't locked? NICE! AT&T has degenerated from American Telephone and Telegraph into a globalized melting pot of greed and required upgrade costs and technical support that uses broken English spoken by people in India. You Canadians luck out this time!
I jumped in with motochopper to get root back in May and had the AT&T Software update service frozen with Titanium Backup back in June, I was so lucky to be "on top of it" by reading this forum. I used "Casual" to obtain TWRP 2.5.0.2 a custom recovery. I've never seen it so easy. After burning an image 3.56 GB of my stock firmware, I have since deleted it from my handset and replaced it with a nandroid of my daily driver here because GoldenEye is flawless. I saved a copy of the stock firmware on my desktop computer just in case, but I doubt I'll ever flash it and all of it's horrendous bloatware.
So I'm a happy camper, that only suffers the jone'sen for a fix as a "flash junkie". I will try CyanogenMod on this S4 after they iron the kinks out.
Looks like you're ok now?
FYI for anyone else in similar situation, ROM Toolbox Pro can download and install recoveries as well. It can access TWRP as well as CWM recoveries. A bonus for TWRP, it detects 2.5.0.2 as latest (avoid the occasional Teamwin splash screen hang with 2.6)!
I used this method to downgrade from 2.6 to 2.5.0.2. :good:
Word of warning, why upgrade from a working twrp 2.5.0.2, when it works flawless? Sometimes upgrading to a newer, is not always the best...look at the XDA app....yikes...
bo8 said:
Looks like you're ok now?
FYI for anyone else in similar situation, ROM Toolbox Pro can download and install recoveries as well. It can access TWRP as well as CWM recoveries. A bonus for TWRP, it detects 2.5.0.2 as latest (avoid the occasional Teamwin splash screen hang with 2.6)!
I used this method to downgrade from 2.6 to 2.5.02. :good:
Click to expand...
Click to collapse
All good thanks
Will Rom toolbox screw anything up if i install TWRP 2.5 over goo's install of 2.6?
I dont trust 2.6... Too many glitches for me and not having faith in your recovery is a scary thing...
Sent from my Nexus 7 using Tapatalk 2
celkin said:
All good thanks
Will Rom toolbox screw anything up if i install TWRP 2.5 over goo's install of 2.6?
I dont trust 2.6... Too many glitches for me and not having faith in your recovery is a scary thing...
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You're very welcome! I initially had TWRP 2.6 installed via rooting procedure (one-click method) and recently had ROM Toolbox flash TWRP 2.5.0.2 over it. No probs. Did full nandroid after it.
Sent from my SGH-I337M using xda app-developers app
Wrong twrp flashed
Dear friend wrong twrp for my device I'm not able to go to the boot menu, how can i get rid of this, help me please. I've my stack memory and kernel already backup in my device memory.
The phone is an att i337? If it is, I assume the bootloader is unlocked since you were able like to flash a custom recovery.
i have no twrp AND I am stuck in boot loop...............................what will I do
Boot into download mode and confirm the phone's model number. Then flash a stock ROM from sammobile.com with Odin to get the phone back to stock.
I haven't used an Android device for over a year now and i'm back to square one.
I'm just wondering if the only possible way of bricking your galaxy s4 is basically installing the incorrect ROM for your device. What is some other ways? I just want to try and avoid those ways before I actually root my S4.
I might be installing CM10 Nightly onto my S4 but if I wanted to go back to stock TW could I just use Kies to install the stock firmware? Instead of Odin because I heard it triggers some kind of binary counter?
Thanks!
EDIT: Does it matter if I'm on MF3 firmware on my S4?
Nevermind just figured out there is no custom recovery.
There is no custom recoveries on MF3.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
So i just bought my Lg G2 a few days ago, i instantely rooted it and installed Vanir, things have been great minus a few small bugs...but being i am a crack flasher i tried a few other roms such as Omni, Beanstalk and more but when i try these other roms i have no issues except that they always boot themselves on when you charge them..you can turn the rom off, plug it in and surely enough it automatically boots itself up, i've tried plugging it in then turning it off and the results are the same. the only rom that will charge while off and remain off is Vanir but i have experienced a few small bugs on then
ANYWAY the main resaon I started this thread is because every and any kernel i try to flash doesnt flash, they all fail...can anyone shed some light as to why all the kenels are failing on me?
Which kernels are you flashing? Which variant are they for? Erich variant do you have?
Sent from my LG-D800 using Tapatalk
If you are using TWRP, flash Philz touch recovery (see android original development). It may be a recovery issue.
Sent from my LG-D802 using XDA Premium 4 mobile app
tdevaughn said:
Which kernels are you flashing? Which variant are they for? Erich variant do you have?
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
The Kernels in the Lg G2 Verizon section and a couple other, the names escape me at the moment but they are for the vzw G2 which is what I have/
Life Engineer said:
If you are using TWRP, flash Philz touch recovery (see android original development). It may be a recovery issue.
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i was on the latest twrp and tried flashing and it didnt work, i now am on philz touch cwm recover and i still get the fail.
there is also one rom that fails to flash to which is odd because a mass of people swear they flash it no issue
Deleted
Sent from my LG-D800 using Tapatalk
Bump
Does anyone have any idea why I can flash majority of the roms available but I cannot flash one single custom kernel?
I've tried the latest TWRP. an earlier version and i've tried Philz touch...none of which will allow me to flash any of these custom kernels available for my VS980....and yes the kernels are meant for said device. There is also maybe one or two roms that won't flash either
sorry to bump this again but i still cannot get any kernels to flash
I am certainly rooted as i have flashed multiple roms but are there any other steps or processes i need to do in order to flash a kernel on this phone? i've owned about 9 android phones and every time i've rooted and unlocked the bootloader, installed a custom recovery i was able to flash roms and kernels with ease...as i've mentioned i've tried different versions of recoveries and everythng and no mattter what every kernel i try to flash fails...its not the end of the world but i would really like to try some of these custom kernels out and dunno how to do it...
am i missing something?
Hello, I have a new note 3 n900tmobile. I love it but, i cant live with touchwiz, i am rooted with twrp... i tried to flash cwm.tar through the lovely odin. But with the 4.4 bootloader i have learned that changes are permanent and cwm just throws me through a bootloop. I also get a bootloop through twrp flashing cm11 plz help! I also cant flash to 4.3 due to the bootloader? i think thats why.
I also flashed phillz cwm and tried flashing same issue I thought it might change due to not flashing on twrp with some devices namely the optimus , I'm gonna see if the latest nightly will flash correctly. If not the release candidate.
Sent from my SM-N900T using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2614461
This is what you need to know. For now wait and flash the latest nightlies and it will be fixed I have faith in cyanogenmod.
PS. I should have looked done some more research before starting a new thread thanks.
Sent from my SM-N900T using Tapatalk