I updated to ZVC, rooted my phone and flashed TWRP 2.7.0.0. I would like to flash a more vanilla AOSP rom like Pacman but I would like to be sure I can do this without any other steps involved other than backup stock rom in TWRP (done) download zip, copy to phone, boot to TWRP flash and reboot? I've owned many many android devices and this one is by far the most complicated one to install roms on that I've owned yet.
Artifesto said:
I updated to ZVC, rooted my phone and flashed TWRP 2.7.0.0. I would like to flash a more vanilla AOSP rom like Pacman but I would like to be sure I can do this without any other steps involved other than backup stock rom in TWRP (done) download zip, copy to phone, boot to TWRP flash and reboot? I've owned many many android devices and this one is by far the most complicated one to install roms on that I've owned yet.
Click to expand...
Click to collapse
if your on stock kitkat zvc (kitkat) and have a recovery like twwrp 2.7.0.0 then all you need to do is flash like you normally would download a rom wipe everything but internal storage then flash rom gapps etc.
so people are getting a no sound bug meaning no sound at all comes from the speakers this happens because the rom you downlloaded still uses the zva radio. flash a rom cheack if sound plays though if not then just flash the zva radio then re-boot
hope this helps alot
Thanks, I appreciate the help greatly
Sent from my LG-LS980 using Tapatalk
thelgog said:
if your on stock kitkat zvc (kitkat) and have a recovery like twwrp 2.7.0.0 then all you need to do is flash like you normally would download a rom wipe everything but internal storage then flash rom gapps etc.
so people are getting a no sound bug meaning no sound at all comes from the speakers this happens because the rom you downlloaded still uses the zva radio. flash a rom cheack if sound plays though if not then just flash the zva radio then re-boot
hope this helps alot
Click to expand...
Click to collapse
Autorec flashes a version older than 2.7.0.0 I believe (not sure, didn't look at version number honestly, but it didn't vibrate every time I touched an option), is it safe to flash 2.7.0.0 over the version installed by autorec on stock ZVC?
Nevermind. Must just be the first time booting to recovery that doesn't vibrate. It's 2.7.0.0
So I rooted and then flashed TWRP using autorec. I have tried to flash several roms and 80% of them result in a boot loop. On the ones that actually boot up, The mobile data network wont activate so I have no internet at all. What am I doing wrong? Do I just need to find a zva radio download and flash it after flashing the rom?
Related
im sorry if this has been asked before. i was very hesitant to post but ive been trying to resolve this issue for 2 days and browsing and reading as much as i can with minimal results. i am trying to update to 4.4 from 4.2.2. i initially had a hard brick but was able to restore life with the img file but am stuck there. it boots into paranoidkangdroid sometimes (which is the rom i used before it hard bricked but not the one on the img file i created...weird i think). i think the more reading i do the more confused i get. im not sure if i have to flash to stock to get the ota, or whether i can just flash a 4.4 rom. im not sure what other information i should provide. thanks for any help and again, sorry if this is inappropriate.
Does your phone boot into download mode? If it does, flash a custom recovery and custom ROM to at least get your phone into a working state.
audit13 said:
Does your phone boot into download mode? If it does, flash a custom recovery and custom ROM to at least get your phone into a working state.
Click to expand...
Click to collapse
i am able to boot into twrp no problem
audit13 said:
Does your phone boot into download mode? If it does, flash a custom recovery and custom ROM to at least get your phone into a working state.
Click to expand...
Click to collapse
i was finally able to get some where!
i used this method to restore my phone to 4.3
http://forum.xda-developers.com/showthread.php?t=2658486
what steps do i have to take now to update to 4.4 and flash a custom rom?
do i first need to flash a 4.4 bootloader?
Personally, I prefer cwm over twrp.
Just copy a custom ROM to your external SD card, boot into recovery, wipe cache, dalvik, data, system, install ROM, reboot.
Depending on the ROM you install, you may have to update your bootloader and modem.
Hello, a friend of mine installed a custom rom at my lg g3 android phone. The rom is ressurrection remix. I accidently dirty flashed an older version of the same rom, I had 5.1.1 r6 and I flashed 5.0.3, and now neither adb works nor download mode due to killswitch. The only thing it does is show the old rr boot image. It's on a bootloop and since it doesn't open I don't know how to fix it. Can someone tell me what should I do?
Can you use the button combo to boot into TWRP? If you can get into TWRP then just flash the ROM you want and be sure to follow the rom threads instructions before flashing of course.
I just noticed a few things. The stock based roms are using the Dual Recovery in their rom, but CM based roms, like Resurrection Remix, uses Cyanogen Recovery.
So when I flash RR, it automatically replaces my recoveries with the Cyanogen Recovery.
Is there any way to avoid that? Or is there any way I can flash my Duel Recovery back after installing RR?
SethPDA said:
I just noticed a few things. The stock based roms are using the Dual Recovery in their rom, but CM based roms, like Resurrection Remix, uses Cyanogen Recovery.
So when I flash RR, it automatically replaces my recoveries with the Cyanogen Recovery.
Is there any way to avoid that? Or is there any way I can flash my Duel Recovery back after installing RR?
Click to expand...
Click to collapse
It's not all cm-based ROMs that use cm recovery. Each ROM is different. It's discussed in the RR thread, and it's in the 2nd post that cm recovery is built in to that ROM. There's links there for other recovery options. I like to always have Rashr on hand to easily flash IMGs, so I can access my backups from other recoveries. Dual recovery is just not going to work on every ROM.
levone1 said:
It's not all cm-based ROMs that use cm recovery. Each ROM is different. It's discussed in the RR thread, and it's in the 2nd post that cm recovery is built in to that ROM. There's links there for other recovery options. I like to always have Rashr on hand to easily flash IMGs, so I can access my backups from other recoveries. Dual recovery is just not going to work on every ROM.
Click to expand...
Click to collapse
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.
SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.[/QUOTE
I haven't used RR since 1st build, but I know it's been addressed in the thread. I would be glad to try it out to help. Meanwhile, I would try to flash twrp with fastboot, (you said you used Flashtool - maybe the same, but worth a try), and also try flashing M5, (which you need recovery to do, but you could use a temp. boot.img to get into recovery, then flash M5), which may work better with recovery. There's also Nut's PC installer. And search the RR thread.
I'll attach a copy of twrp 2.8.7.0 to try. Hope this helps.
(File too big to attach. Let me know if you want it and I'll send a link)
Click to expand...
Click to collapse
levone1 said:
SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.[/QUOTE
I haven't used RR since 1st build, but I know it's been addressed in the thread. I would be glad to try it out to help. Meanwhile, I would try to flash twrp with fastboot, (you said you used Flashtool - maybe the same, but worth a try), and also try flashing M5, (which you need recovery to do, but you could use a temp. boot.img to get into recovery, then flash M5), which may work better with recovery. There's also Nut's PC installer. And search the RR thread.
I'll attach a copy of twrp 2.8.7.0 to try. Hope this helps.
(File too big to attach. Let me know if you want it and I'll send a link)
Click to expand...
Click to collapse
You can't because CyanogenMod uses its own Recovery based of CWM ( I think? ). You could try however, using a custom kernel that has its own Dual recovery ( for e.g. PhilzTouch and TWRP )
Click to expand...
Click to collapse
SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.
Click to expand...
Click to collapse
I just remembered something else. See my post here- http://forum.xda-developers.com/showpost.php?p=62114382&postcount=534 - latest version of Rashr doesn't seem to work on some ROMs. Try this one...
Edit - I just successfully flashed twrp 2.8.7.0 on latest RR using Rashr. Make sure to use this version, not the latest Play Store.
Okay so I tried what @levone1 said. I installed that Rashr which you uploaded. I tried flashing the recovery with this, and it worked! Thank you very much guys for your help!
hey thanks to levone1 i got twrp running on crDroid rom.:good::good::good:
i did it like he said: Use his Version of rashr and flash his twrp. done!
Hi all,
I am new here and I am having trouble with my Galaxy 3 SGH-I747 from at&t
I rooted the phone using KingoRoot and everything was fine.
I used the phone for about a week and decided to update from kitkat 4.4.2 to lolipop 5.0.
I have a micromax phone that is rooted and I didnt have any trouble updating it while it was rooted, so i figured it wouldnt be a problem but when I updated the s3 it said update failed at 94% and started rebooting and got stuck in an update loop.
I searched and searched and tried finding recovery options using odin but I cant find a 4.4.2 stock firmware, and cant find much information on recovering my device.
I am unable to boot in to recovery. I cant find a link for the SGH-I747 to philz recovery, the links all seem to be dead.
I can boot in to download mode.
I want to install a custom recovery via ODIN but i cant find one for my phone.
After I install the custom recovery, how will i know which stock OS my phone is currently at
I appreciate any advice you can give me, thanks.
Use TWRP for custom recovery. CWM and Philz haven't been updated in quite a while. You can get odin flashable tars from here.
Flashing TWRP should get you to working recovery, and you can find the rom zips you need to get back up and running in the development section here.
Unrooted stock will overwrite TWRP with stock recovery upon boot. Depending on how far your phone is getting into the booting process that might happen if you let odin auto-reboot. Your best bet is to uncheck auto-reboot in odin, so it won't restart on you automatically. Upon success remove the USB cable and pull battery. Replace battery and boot straight to recovery by holding home+vol up+power until you see tiny blue text in the upper left corner then releasing.
Thankyou! i was able to install the recovery by TWRP.
I just need to figure out what firmware to install and where I can get it... I was on kitkat, I tried to update to lollipop but it didnt work. My phone is bricked so I dont know how i would see the firmware version on it.
I really just want any kind of stable firmware that is rooted. Any ideas where I could find one? I'm trying to sift through the forums
Lots of ROMs are available here: http://forum.xda-developers.com/galaxy-s3-att/development
audit13 said:
Lots of ROMs are available here: http://forum.xda-developers.com/galaxy-s3-att/development
Click to expand...
Click to collapse
I appreciate all the help - It seemed really hard because I was finding roms and flashing with ODIN but it always failed TWRP is giving me results. I flashed slimkat and got my phone working again! the only problem is my sound is a bit junky, idk why.
I plan on trying out Octos - M, because I heard marshmallow OS has a lot better battery life among other things
If i upgrade to a custom marshmallow OS, is there any coming back to a former custom OS like 4.4.2? or is it a permanent upgrade?
Do you guys recommend any custom OS? I need something stable, that uses the resources efficiently.
Before flashing additional ROMs, make sure the phone is running the latest bootloader and modem.
To verify the installed bootloader and modem, install the Samsung Phone Info app from the Play store.
With a custom ROM, you can flash from one to another, usually without any issues as long as you perform a complete wipe (system, data, cache) before flashing a new ROM. If you are upgrading an existing custom ROM with a newer custom ROM (e.g. CM12.1 2016-01-01 nightly to CM12.1 2016-01-02 nightly), you can just flash the updated ROM over the existing ROM.
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Sent from my [device_name] using XDA-Developers Legacy app
androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list out what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I know it's a typo but condom kernel cracked me up. Does it automatically boot you to safe mode?
Sent from my Pixel 2 XL using XDA Labs
androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Vinnipinni said:
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Click to expand...
Click to collapse
What I' did to flash the rom was separate from rooting procedures . The phone been unlocked for months.
I did both separate times
I fastboot booted twrp.img then I installed magisk zip. I did not permanent flash twrp zip after . I only flashed the perm twrp zip after I wiped and flsahed the RR Rom . So another words I was on twrp temp boot only when I flashed the rom then I flashed twrp zip per the rom Dev instructions . But I can't make sense why you have to flash twrp after you flash a rom install .
I'm assuming it goes like this
Install latest magisk apk.
Fastboot boot twrp .img
Then perm flash twrp .zip
Then flash magisk .zip
Reboot into the O.S and check for root
Reboot into (permanent Twrp) swipe to allow modifications .
wipe stock rom with the swipe only method??
Install Rom of choice and reboot !
Or is it install Rom /flash twrp.zip for a second time then reboot
Sent from my [device_name] using XDA-Developers Legacy app
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I want to flash a rom but I'm not understanding how the pixel 2 xl works with twrp vs other devices .
If I reboot without first flashing a kernel then maybe that's the dilemma?
I just don't get why you need to flash permanent twrp .zip after you install Rom If you already had twrp permanent installed to begin with .
I' went over what I did in this thread and what I'm guessing I did wrong. So do I need special kernel for each and every rom listed . I never had to flash a kernel to get a rom to boot on any device and I've been flashing for years with T-Mobile phones on Galaxy devices and unlocked Google based phones.
Sent from my [device_name] using XDA-Developers Legacy app
I don't get why you would need to flash magisk before.
0. Make Backups and turn off security settings. Also make sure you're on the newest OTA
1. Boot into TWRP
2. Do a factory reset in Wipe settings.
3. Flash ROM
4. Flash TWRP of you want, not required but recommended
5. Reboot and set it up
6. Install magisk Manager and reboot to TWRP
7. Flash magisk and reboot
That's it.
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
nein7three said:
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
Click to expand...
Click to collapse
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Badger50 said:
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Click to expand...
Click to collapse
Thanks a lot. Does changing kernels remove magisk?
nein7three said:
Thanks a lot. Does changing kernels remove magisk?
Click to expand...
Click to collapse
Some do, some don't. That's why you flash magisk after the kernel. But that's changing as well :good: