Hi, RomSwitcher has been nagging me to update since I installed it. So finally, I clicked Update.
Now my phone doesn't show the boot logo, it just boots into a blank screen. Adb seems to function:
C:\Unified_Android_ToolKit>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Anyways, if I ODIN any Perseus kernel, then my first ROM boots fine. But if I go into RomSwitcher and install the tools, then reboot boots into blackness again. I've tried to install the tools from the recovery, same thing happens.
I would post this in the Development thread, but I'm not allowed to post there yet. So as I understand it, RomSwitcher boots into it's own environment, changes some directories so one of several ROMS will boot. What seems to happen is that the RomSwitcher environment is just blank. I have no idea where to look, and I can't find the old version of RomSwitcher which worked anymore. I don't really want to reflash everything just to get RomSwitcher functionality back.
There's no information on the internet about how it works or how to fix it. It seems I've probably managed to wipe the configuration when updating it. If anyone can point me to a FAQ or Guide or something about how it works, or summarise it, I'll really appreciate it, as I don't really want to go and dig through the code to figure it out... that might take me several weeks with the little time I have available!
Questions:
What is in the configuration file?
Where is it stored?
Can I re-create it by hand?
What's the simplest way to get RomSwitcher working again, without starting from scratch with all my ROMs?
(I'm just dual booting Phoenix ROM and CM11, which worked fine until I updated RomSwitcher. New RomSwitcher looks good, but doesn't work!)
Thanks
Steps to repeat...
So, I've tried every Perseus kernel: 16, 18, 19
From the main TW based ROM that boots: Phoenix 10.1
RomSwitcher says to install Tools and Reboot before it does anything. Doing that reboots into a black screen, no matter what kernel. I've re-downloaded the main config and the tools several times.
Seems the only thing left to try is re-flash main ROM, re-install RomSwitcher... then it will probably work But that is a 3-4 hour operation I can't afford right now.
Trying to flash different Nougat ROM. I have tried several but something is preventing the process getting past the screen where you are asked if you want to use your old settings. It won't proceed. If I try to do a new install it still just stops. I can get back to recovery (TWRP) and restore the backup but I want to change to a different ROM as the one I am using has a few features I don't like.
Update: have tried again. Get to set up your XT 1562 and then after selecting, the message says Setup Wizard has stopped. Can get no further.
Help please.
Rick O said:
Update: have tried again. Get to set up your XT 1562 and then after selecting, the message says Setup Wizard has stopped. Can get no further.
Help please.
Click to expand...
Click to collapse
Keep touching in all four corner of your screen(fastly) it I'll skip the process and lead you to your home screen.
I face same problem twice and this method works for me
check your Gapps package, does it match with the rom version? try bean or open gapps and different packages
Wrong gapps! Many thanks.
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Maybe its realy screen problem... did the touch screen works on twrp
fire_onCA said:
Maybe its realy screen problem... did the touch screen works on twrp
Click to expand...
Click to collapse
Yes It Does. Its not the screen issue because on stock rom everything works properly.
Im guessing somethings interrupting with the OS, causing the apps to crash.
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
mfaisal98 said:
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
Click to expand...
Click to collapse
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
aymanabdulla said:
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
Click to expand...
Click to collapse
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Its not actually an error message but a small notice on the top left corner.
When I restore my official rom back the message is normally gone.
But I will try again with ur advice again because I always wipe system before flashing the rom so it could be causing the issue.
Thanks I'll let u know what happens
kaiserfakinaway said:
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
Click to expand...
Click to collapse
I did do that. I have the official stock rom running now since RR and cyanogenmod isn't responding.
aymanabdulla said:
I did do that. I have the official stock ROM running now since RR and CyanogenMod isn't responding.
Click to expand...
Click to collapse
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
kaiserfakinaway said:
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
Click to expand...
Click to collapse
Yes, thats what i did.
G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md5 this was the file name. it works fine i guess, had some issues with the sim as the phone keeps on asking to reboot but no other issues.
Subhashis said:
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
Click to expand...
Click to collapse
Yes i did. as well as the front cam + patch fix. i flashed both yet still the same issue.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
aymanabdulla said:
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
Click to expand...
Click to collapse
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Why Doesnt any one else have this problem?
oh is it? what about lineage os 13.1 running MM?
Fine i have put cm12.1 for download, will flash it and let u know what happened.
Fingers Crossed
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
kaiserfakinaway said:
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
Click to expand...
Click to collapse
Nope, all of them have camera issues too.
but im sure there will be a fix for this, since its running LOLLIPOP.
I'll let u know.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Might not be a kernel issue because I have also tried with this custom kernel [KERNEL][5.x/TW/6.x]Infected Kernel R4[15-05-2016] and still the same.
Hello there!
I recently came out on a post about Dual Boot your android device.
This seems really handy to me so i was willing to try it.
I rooted my S7 Edge, i have Magisk installed and the Dual Boot Patcher.
I tried tons of roms like: DOTOS, RR, LineageOS, Ice Projects and so on.
Everytime when i try to flash the zip i patched it gives me an error.
But every time another error.
For example with Dot.OS i got:
Failed to copy /raw/data/,system.img.tmp to /raw/system/multiboot/dual/system
But when i try for example LineageOS the app just stops working.
Also i tried some other roms which gave an error about the system check. If my device was compatbale with the ROM.
I saw alot of issues about that online so i tried all those fixes but nothing seems to help.
I tried to delete the Asserts line from the updater-script. How ever only 1 rom i downloaded got these lines in the file.
I am really stuck and have no idea what to do now.
Is this because of my phone? Do i need to install another APP or anything to fix this issue?
I really wanna install this Dual Boot. And i saw many people successfully flashing on S7 Edge. So its pretty strange it doesnt work for me...
If there is some one with a solution or maybe someone that wanna take a look with me to fix my issue woukd be highly apprecieted!
Also i dont mind to pay a few bucks to a dev or anyone with more knowledge to take a look and try to fix this issue with me if no one else can!
Thank you in advance! Please let me know if you need more information about these issues and please tell me which info.
As i had no idea what to all post here to make it easier to locate the issue.
Thank you all!
I have a T3 Mini-A S905 series SOC P281 with a Stectek MLC NAND Flash. The firmware is 20181210. The box keeps freezing and I have tried loading and changing various img file using Ricky's Android Customization tool V 7.1.0 and the Android USB Burning tool V 2.1.7.3.
I have tried the APTXperience img with no success. It boot fine but still freezes. I have tried everything I can think of. Anyway all this and nothing seems to help the freezing problem.
Now I am thinking of removing all the APK's that are not necessary and see if this helps. I have done many searches on what APKS are required to get the box up and working, with no success.I have tried removing the ones I throught may not be needed but the box wiil only stays at the android cycling screen, the one displayed before the android screen comes up.
Does anyone know what APKS are required in order to boot up the box. Any help on this would be great. Thanks.