So I tried flashing this autobot custom Lock ring and I have a custom theme and all that good stuff...so when I flashed the autobot custom Lock ring it didn't work and so i went back to my nandroid that I had made right before flashing it....so i was wondering could someone please tell or show me how to make it so when i actually flash this custom Lock ring my lock ring actually changes... Any help would be very much appreciated.
Sent from my calculator rooted with calctrix 2.0
it really depends on 2 things is it a custom lock screen for 2.3.3 or 2.3.4 and if it's the appropriate lock screen for your version sometimes it fails on the first flas and you need to reflash it a second time right then and their and it will take
I'm pretty sure its for 2.3.3 and I'm on viper rom for 2.3.3
Sent from my calculator rooted with calctrix 2.0
I'm having an issue when flashing new roms. I broke my original 3d and when I got my new one I rooted it the same way (hboot 1.3) as my original one that I got when the phone first came out. Flashing the rom goes fine but the first time I reboot my phone after it boots the rom all of the android apps on my home screen disappear (gmail, market, weather and clock widget) but my installed apps remain. Also, my lockscreen goes black except for the ring and the time. Weather and the shortcuts disappear. Only way I have found to fix it is wipe data, cache, and delvik cache and reflash, but again once I reboot it does the same thing. I can get some pictures of both later if necessary.
zaw11 said:
I'm having an issue when flashing new roms. I broke my original 3d and when I got my new one I rooted it the same way (hboot 1.3) as my original one that I got when the phone first came out. Flashing the rom goes fine but the first time I reboot my phone after it boots the rom all of the android apps on my home screen disappear (gmail, market, weather and clock widget) but my installed apps remain. Also, my lockscreen goes black except for the ring and the time. Weather and the shortcuts disappear. Only way I have found to fix it is wipe data, cache, and delvik cache and reflash, but again once I reboot it does the same thing. I can get some pictures of both later if necessary.
Click to expand...
Click to collapse
Try Flashing a Different ROM... See if that Helps? That's Weird man...
Yea tried that. Think I figured it out though. I was using the backup using TBU from my old phone. I flashed a new rom without restoring stuff and about to check it now.
Edit: That was it. Strange though, never had something like that happen, or any problem with TBU before.
Hi,
I have a Galaxy S3 i9300 currently running CM10.1. I just tried to flash Slim Bean 2.2 on my S3 as that's the only download available. However after flashing the ROM and G-Apps in CWM, when I boot the phone gets stuck at where the setup menu should be. Like when it should ask for Wi-Fi password etc, it just shows a black screen but the notification bar is there and working. At first nothing would work, but after a cache wipe, it said Android is upgrading (54 apps) but was still a black screen. However I could access settings and change anything I wanted, but the home button wouldn't take me to home screen. I print screened to try get to home through the gallery but the button still doesn't work. I booted without G-Apps to see if that was the cause and same problem. I have wiped everything and reflashed several times, still doesn't work. I have to flash through my external SD because when I put the .zip on my internal they don't show up in CWM. I am back on CM10.1 from a backup however I would much rather Slim Bean as I can tell from my "demo" access to it, it seems far far smoother. How can I fix the issue so I can use it?
Thanks
JesseBeckett said:
Hi,
I have a Galaxy S3 i9300 currently running CM10.1. I just tried to flash Slim Bean 2.2 on my S3 as that's the only download available. However after flashing the ROM and G-Apps in CWM, when I boot the phone gets stuck at where the setup menu should be. Like when it should ask for Wi-Fi password etc, it just shows a black screen but the notification bar is there and working. At first nothing would work, but after a cache wipe, it said Android is upgrading (54 apps) but was still a black screen. However I could access settings and change anything I wanted, but the home button wouldn't take me to home screen. I print screened to try get to home through the gallery but the button still doesn't work. I booted without G-Apps to see if that was the cause and same problem. I have wiped everything and reflashed several times, still doesn't work. I have to flash through my external SD because when I put the .zip on my internal they don't show up in CWM. I am back on CM10.1 from a backup however I would much rather Slim Bean as I can tell from my "demo" access to it, it seems far far smoother. How can I fix the issue so I can use it?
Thanks
Click to expand...
Click to collapse
Could be a long way off here, but are you sure the download wasn't corrupted, a statusbar and black screen sounds to me like the launcher wasn't opening, or wasn't flashed.
Also what version of CWM are you using? I would download rom manager and flash the latest version, then try flashing slim again.
JesseBeckett said:
Hi,
I have a Galaxy S3 i9300 currently running CM10.1. I just tried to flash Slim Bean 2.2 on my S3 as that's the only download available. However after flashing the ROM and G-Apps in CWM, when I boot the phone gets stuck at where the setup menu should be. Like when it should ask for Wi-Fi password etc, it just shows a black screen but the notification bar is there and working. At first nothing would work, but after a cache wipe, it said Android is upgrading (54 apps) but was still a black screen. However I could access settings and change anything I wanted, but the home button wouldn't take me to home screen. I print screened to try get to home through the gallery but the button still doesn't work. I booted without G-Apps to see if that was the cause and same problem. I have wiped everything and reflashed several times, still doesn't work. I have to flash through my external SD because when I put the .zip on my internal they don't show up in CWM. I am back on CM10.1 from a backup however I would much rather Slim Bean as I can tell from my "demo" access to it, it seems far far smoother. How can I fix the issue so I can use it?
Thanks
Click to expand...
Click to collapse
First of all, the newest version of Slim Bean available for the S3 is 3.1, which you can download here:
http://www.slimroms.net/index.php/downloads/all/viewcategory/152-i9300
I would suggest doing a full wipe and installing this (much newer) version... I'm using it and it's awesome. Hope this helps.
Wrong section, post in QA
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I just rooted my phone (Samsung S6 Edge [SM-G925P] running Android 6.0.1) this Friday and I have a couple of questions about using the CyanogenMod ROM and installing Xposed. To note, I am pretty, pretty new (I literally just rooted 2 days ago.
So my question about CyanogenMod is will it run on my rooted Samsung and is it dedoxed? I already have TWRP and SuperSU flashed and installed on my phone.
And my question about Xposed is will it run on my phone, as well with CyanogenMod, TWRP and SuperSU? I tried installing it with the original ROM on my phone, but that provided to be disasterous since it soft-bricked my phone, but I heard that was because my ROM was deodexed.
Hi NovaViper ! It depends. Cyanogenmod and other ROMS can come in two flavors: odexed or deodexed. The one on the official Cyanogenmod Website is deodexed. If you go on Cyanogemod's official website they don't have a ROM for Samsung Galaxy S6 / Edge. Check it out: http://download.cyanogenmod.org/ Look at the left to see supported devices. Unfortunately, it's not there. Some Galaxy S6 / Edge models do support Cyanogenmod but as for your model the SM-G925P there is still no official support for CM ROM. Check this link out: http://forum.xda-developers.com/gal...development/cyanogenmod-13-galaxy-s6-t3269984 Just out of curiosity, why do you want to install CM on your device?
I want to try CM because I heard it offers full customization.. I really would like to customize the lockscreen and colors of the UI especially and because it is deodexed, so I can also add Xposed. I have another ROM atm called Mostly Stock (its based on ROM but its deodexed and have a few changes to the stock UI, BUT it still has the parts I hate about the stock ROM). I specifically want CM because I haven't found any other ROM that offers full customization, deodxed for Xposed, and most importantly, is not like the stock ROM.
Oh, also with CM, I tried to install it but it said my device isn't support.. I tried the one from the link
If you want a full stable ROM for Samsung Galaxy S6 Edge and XPosed on it I would recommend this ROM: http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519. My friend has it on his ROOTED S6 Edge and it offers even more customization's then Cyanogenmod plus you can install XPosed on it. Give it a try.
Thanks I already flashed it but I notice that it isn't responsive to touch. I can interact with the buttons but no response to touch whatsoever. Seems like there isn't a ROM that works with my SM-G925P, the edge that rom works with is a G925F
Hmm, I thought it would work on your model. Try this: http://androidfreeroms.com/renegade-android-m-6-0-1-aroma-rom-sprint-samsung-s6-g925p/
I got the rom flashed and running.. but i cant seem to restore my messages from the samsung backup.. i can only get them from Textra (which doesnt export them). Also, i cant receieve text messages either.
Well, I finally got my messages backed up but.. I notice something else now. I had installed Xposed, which ended up giving me a bootloop and I had to factory and data reset, and reflash my stock rom. then I installed TWRP and then Renegade, but the mobile data isn't working anymore. Its just black the black bars.. I can't even find the Mobile Data enable button anywhere. (It works on stock rom though). To point out, mobile data WAS working before I installed Xposed. Right now, I'm reflashing my stock rom and seeing if it works.
--UPDATE 1--
Yeah, the stock mobile data works.. although I do have a theory on what could be going on
Theory 1: It could be I have to install my ROMS a certain way, initally, I had stock ROM, then I added the "Mostly Stock ROM" THEN I added Rengeade when you suggested it to me
Theory 2: Possibily signal strength/proxies (I'm doing this at on my school's wifi)
Theory 3: Something that Xposed has modified and its still there
--UPDATE 2--
I did the first theory and it worked successfully BUT.. I did remember that I had installed SuperSU soon after flashing twrp (which came after i flashed the stock rom).. Now I'm trying to see if that made a difference.
--UPDATE 3--
Ok, so it seems that it is a certain install order (tried with both superSU installed first and without). But I'm worried now about installing Xposed.. as I'm now nervous that it may end up messing up my phone again (It took a while for me to figure out how to get it back working.. as it ended up bricking with continuous looping and even factory resetting/clearing data off didn't work. I had to flash the stock rom for it to work again)
Interesting. My friends all have the International version which is G925F. Yours is Sprint ? Or some other cell phone provider ?
If your model goes haywire with simple custom rom installations and other apps than I wouldn't risk installing XPosed BUT if you do then try to follow these instructions... they work for your model:
https://xtremetricks.net/install-xposed-framework-android-6-0-6-0-1-marshmallow/
My phone is Sprint and I downloaded Xposed from the Magitsk app and it worked without bricking my phone.. I wonder why it was acting up
Strange thing, I seems I HAVE to install the 'Mostly Stock ROM' BEFORE I add Renegade.. the mobile data works to not work at all without installing Mostly Stock first.. How any idea how to fix this?
Well, I tried installing Magisk and it bricked my phone once again.. I'm really confused with whats going on. I have a backup of the stock ROM from SamMobile. What I want to do now is completely clear off ALL data from all of the roms and just start over, is that even possible? Also, if I delete the system files, do I HAVE to install the Stock ROM first, or can I just add the custom ROM and it will add the OS?
Well normally for rooted phones, you only add the custom ROM and it will automatically add the OS. I have no idea why you having so much problem with it. Did you unluck the bootloader ??
Yeah.. (I think), I made sure OEM Unlock is enabled and USB debugging is on.. Not sure what could be causing such problems with my phone.. I honestly wish I knew
What method did you use to root your phone and unlock the bootloader ?
I used the systemless method (installed TWRP, then installed the latest SuperSU which used the systemless method by itself) and I think I did.. there was an option where I had to enable (it was called OEM Unlocking, it was preventing me from flashing)
And I forgot to ask another question.. should I (and if such thing is possible) wipe the system/ folder and then install the custom ROM onto my phone without having to add the stock one at all?
What I would do if I were in your shoes is I would unroot and re-lock your bootloader again... see this article for unrooting: http://howunroot.com/unroot-supersu/samsung/galaxy+s6+edge+sm-g925p/5.0/ Now... once you unroot your phone... I don't think re-locking your bootloader will have any effect... but you can try to relock your bootloader and bring it to the original state meaning factory... once there just follow these instructions step by step: http://www.ibtimes.co.uk/skipsoft-toolkit-galaxy-s6-edge-root-unlock-restore-flash-stock-firmware-drivers-more-1517879 Once you root it and unlock your bootloader again, and after your install TWRP, go into TWPR, wipe dalvik cache, wipe system, wipe everything ... and then instlal the custom ROM that I gave you in the link, and it should be working find without problems. Try that and get back to me and update me... if you have any questions then just post it here and I will help you as much as i can.
I don't think I unlocked the bootloader because I looked up the instructions to how to unlock the bootloader and I didn't do that.. all I did was enable OEM unlock, is that the same thing as unlocking the bootloader? If not, how do I unlock the bootloader?
TL;DR: After flashing a new vendor image and LineageOS nightly, my phone is getting stuck on showing a notification at the lock screen. When I unlock the phone, it goes dark and relocks before showing the notification again. Any ideas of what is happening or what I should do to fix it?
Longer explanation:
Yesterday I downloaded the 9.6.27 vendor image and the latest OTA LineageOS nightly, I hadn't updated for a month or two so I assumed I would need to update my vendor image first but the OTA update sucessfully installed.
I decided to flash the vendor image and then reflash the latest LineageOS image again (e.g. dirty flash), but hit a problem where the phone would only show the background -- no lock screen, icons, menus etc.
So instead I downloaded the V10.2.5.0.PEJMIXM-9.0 venfor firmware and tried that instead. Everything worked, until I got a push notification -- my phone now gets stuck on showing a notification at the lock screen. When I unlock the phone, it goes dark and relocks before showing the notification again.
Any ideas of what is happening or what I should do to fix it? Should I cleanflash lineage again, restore an older nandroid backup and retry? What vendor image should I be using?
On a whim, I decided to flash the latest OTA update (1 day newer than the previous one) and this problem seems to have addressed itself.
I can't remember if the problem occurred straight away last time, so i'm still curious to know if anyone has experienced this before or knows anything about it?
xxbrentonxx said:
On a whim, I decided to flash the latest OTA update (1 day newer than the previous one) and this problem seems to have addressed itself.
I can't remember if the problem occurred straight away last time, so i'm still curious to know if anyone has experienced this before or knows anything about it?
Click to expand...
Click to collapse
With vendor-firmware from June forwards you new to flash that first before the new ROM otherwise you get the luvly Black Screen of Life. As you've now flashed a newer ROM, that's cured your black screen.