Good evening,
I waited 168 hours, installed twrp, and RMM State, all with a Stock ROM, then for a bug I had in the Cerberus app I had to reinstall the Stock and blocked the RMM again.
Is it always going to be like this? You still do not have a way to avoid this using ROM Stock, I'm not much of a MOD fan!
costafabiof said:
Good evening,
I waited 168 hours, installed twrp, and RMM State, all with a Stock ROM, then for a bug I had in the Cerberus app I had to reinstall the Stock and blocked the RMM again.
Is it always going to be like this? You still do not have a way to avoid this using ROM Stock, I'm not much of a MOD fan!
Click to expand...
Click to collapse
I suspect that anytime you have to flash the stock rom again, you will need to start all over. That seems a PITA!
well u should have installed a custom kernel before it can boot for the 1st time
since custom kernels has patched rmm state right...
but for now you should wait 7 days again and dont forget to install custom kernel after the 7 days...
if you plan to install a new rom again in twrp install custom kernel right after without rebooting and u should be fine then
good luck
JeffDC said:
I suspect that anytime you have to flash the stock rom again, you will need to start all over. That seems a PITA!
Click to expand...
Click to collapse
It's very difficult this way, we still have no way out about it? right?
SOGKush420 said:
well u should have installed a custom kernel before it can boot for the 1st time
since custom kernels has patched rmm state right...
but for now you should wait 7 days again and dont forget to install custom kernel after the 7 days...
if you plan to install a new rom again in twrp install custom kernel right after without rebooting and u should be fine then
good luck
Click to expand...
Click to collapse
Sorry, but I did not understand.
How should I have installed the kernel?
The steps I followed were:
1. I expected to release the OEM
2. I installed TWRP
3. Restart (I was in Download mode).
4. In TWRP I installed the RMM State
Then I had an error in the ROM caused by an app, and I had to reinstall. When I did that the RMM was there again.
costafabiof said:
Sorry, but I did not understand.
How should I have installed the kernel?
The steps I followed were:
1. I expected to release the OEM
2. I installed TWRP
3. Restart (I was in Download mode).
4. In TWRP I installed the RMM State
Then I had an error in the ROM caused by an app, and I had to reinstall. When I did that the RMM was there again.
Click to expand...
Click to collapse
I think what he is saying is that after you install your custom stuff, via TWRP, and before you reboot to system, flash the custom kernel.
JeffDC said:
I think what he is saying is that after you install your custom stuff, via TWRP, and before you reboot to system, flash the custom kernel.
Click to expand...
Click to collapse
so I will need a custom kernel?
Because my understanding is medio, I use only stock rom, and the default kernel.
In this case, if it is mandatory, is there a custom kernel indicated?
Just to quote, in the topic that has the link to the RMM State does not say about kernel!
Related
A while back, I always rooted and unrooted my Nexus S with no problems at all. Now whenever I try to root it, it just goes wrong. I've tried TWRP & CWM, CWM used to always work but now it just messes up. Both TWRP and CWM both give me an error that say Installation Aborted when I try to install a custom rom. I've redownloaded the rom from different browsers and even different PCs but nothing working, still that same error. Does anyone have a guide that is 100% to work without any errors during the process?
What guide are you using?
paul96 said:
What guide are you using?
Click to expand...
Click to collapse
I used this one: http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
albundy2010 said:
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
Click to expand...
Click to collapse
Alright, thanks Do you recommend that I root my Nexus S or should I wait for the Jelly Bean update? I've rooted before and I enjoyed it but now I don't see that many reasons to root, do you have any good reasons?
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
albundy2010 said:
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
Click to expand...
Click to collapse
What are your reasons for root? Please share?
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
albundy2010 said:
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
Click to expand...
Click to collapse
Oh cool. There is this project that some members from XDA are working on called Sense4All and they are porting Sense to many devices. Im probably going to wait until a fully functionable release is available for the Nexus S. I do like AOKP a lot, so that might be a reason for why I'll root.
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
albundy2010 said:
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
Click to expand...
Click to collapse
Oh, I never knew that, haha. Is it possible to flash a custom kernel with an unlocked bootloader or does that require root access?
m1l4droid said:
No you just need a custom recovery. But using that kernel's mods, like BLN, OC, UV, touchwake, etc, requires apps that need root, like NSTools, SetCPU, etc.
Click to expand...
Click to collapse
Oh alright. Now I really wanna root + install a custom rom. Do any of you have a full 100% fully working guide for rooting Nexus S and which rom should I flash first? I already know what kernel I want.
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
leap_ahead said:
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
Click to expand...
Click to collapse
Thank you so much! I rooted my phone with CWM recovery installed and Paranoid Android + gapps installed
Hello everyone !
I have some questions about the installaton of superman rom.
I've tried to change the bootloader and the modem but when i tried to install it via Odin it doesn't want to reboot and stay on samsung logo.. That's my only problem because i've successfully installed twrp.
I've heard that my actual rom (stock rom APB2) is encrypted.. how to unencrypt it.. (sorry for my english).
Thanks you !
Did you follow the install instructions on the first page?
They are very clear
suprememaster said:
Did you follow the install instructions on the first page?
They are very clear
Click to expand...
Click to collapse
Of course, i've followed everything but like i said when i want to install bootloader and modem that allow to install rom, it never boot
Try to flash the stock rom ape9 i think instead of the modem only. Can you still go to twrp even when you got a bootloop? If so. Flash the rom in twrp
suprememaster said:
Try to flash the stock rom ape9 i think instead of the modem only. Can you still go to twrp even when you got a bootloop? If so. Flash the rom in twrp
Click to expand...
Click to collapse
Can you give me the link to download the ape9 stock rom please i didn't found it :/
Yes when it booloops i can go to twrp and i've tried to install the rom but when the installation with aroma finished, it bootloop again
I think you might've skip a step in this thread:
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Namely step 9. that should answer you decrypting question.
It does a few minutes for boot up. How long were you in the bootloop??
But the rom is pre-rooted no ? It means that i don't have to root the phone before if i've right understand ?
If i let this 3 hours i think it have bootloop during 3 hours
@p0m-walt
Yes the Rom is prerooted but that was not what I was referring to. You asked how to decrypt the phone so I provided a link to the dm-verity zip file that you need to flash through twrp before installing a Rom. If you missed that step that's probably what's causing you problems.
3 hours in a bootloop is a little excessive. You should figured something was was wrong after 15-20 mins.
Format data
I installed the rom successfuly. I had to install an APE9 stock rom and after that, the installation via twrp was a success, Thanks for your help guys
Hi, I installed Thor v2 rom, nougat. However, i can't find a way to unroot it, whether using SuperSU unroot menu, or installing other kernel.
Upon boot, it shows samsung, but then back again to TWRP recovery, cannot go straight to OS.
Please help. I really need to unroot since i wanted to use several apps which detects root/
You need reinstall the OS via Odin
duke_dreadmoore said:
Hi, I installed Thor v2 rom, nougat. However, i can't find a way to unroot it, whether using SuperSU unroot menu, or installing other kernel.
Upon boot, it shows samsung, but then back again to TWRP recovery, cannot go straight to OS.
Please help. I really need to unroot since i wanted to use several apps which detects root/
Click to expand...
Click to collapse
Flash a ROM zip. Or flash the super user uninstaller zip
godkingofcanada said:
Flash a ROM zip. Or flash the super user uninstaller zip
Click to expand...
Click to collapse
Uninstaller not working. It looks like the ROM (thor v2) already modifies the boot, so it's not working without root. It's bootlooping to recovery screen. Is it?
duke_dreadmoore said:
Uninstaller not working. It looks like the ROM (thor v2) already modifies the boot, so it's not working without root. It's bootlooping to recovery screen. Is it?[/QUOToh I get it. Its pre rooted so there is no boot.IMG to revert to. I thought the su uninstaller would remove itself from the boot. Just use a different ROM bro
Click to expand...
Click to collapse
Ok so I figure I'll just ask since there is so much old information, and dead links or links that lead to no real answers. I'm already rooted and on a stock rom. Build number is LMY48C. I tried flashing a new TWRP version, 3.2.3.0 official version, but every time I try to reboot to recovery it just stays on the Nvidia logo. I can boot back to the tablet and flash my old version, 2.8.7.1 and everything works fine. But nothing remotely new will flash with that version lol. Any ideas of what I'm missing? Thanks in advance for anyone that can help, I'm sure it's something stupidly easy that I'm messing up lol.
I'd recommend flashing back to stock using the latest Nvidia image...then allow it to upgrade itself...they only have 5.2 available on their site...after it upgrades you'll have the newest bootloader...then in fastboot flash your recovery.
Make sure you're bootloader unlocked the whole time! And don't lock it...leave it unlocked.
You should be good to go after that.
Extra info...I'm on LOS 14.1 using opengapp (custom config so it only installs what I want)
I also flash a few other things but everything is working on my shield....even Nvidia Games
HaRdC0r3 said:
I'd recommend flashing back to stock using the latest Nvidia image...then allow it to upgrade itself...they only have 5.2 available on their site...after it upgrades you'll have the newest bootloader...then in fastboot flash your recovery.
Make sure you're bootloader unlocked the whole time! And don't lock it...leave it unlocked.
You should be good to go after that.
Extra info...I'm on LOS 14.1 using opengapp (custom config so it only installs what I want)
I also flash a few other things but everything is working on my shield....even Nvidia Games
Click to expand...
Click to collapse
Thanks for the reply. I was honestly just hoping there was a way to flash the newest bootloader without going to stock, but it looks like that's not an option. Ohh well, One more question, since you're actually on u custom ROM, does HDMI out work? I use that a lot with my TV haha.
If you want the easy quick way then you could pull the bootloader from the newest 15.1 zip as steel included it....flash the bootloader through fastboot and then proceed to flash twrp then wipe wipe wipe and install whatever rom you wanted...I still suggest 14.1 and yes the HDMI works.
HaRdC0r3 said:
If you want the easy quick way then you could pull the bootloader from the newest 15.1 zip as steel included it....flash the bootloader through fastboot and then proceed to flash twrp then wipe wipe wipe and install whatever rom you wanted...I still suggest 14.1 and yes the HDMI works.
Click to expand...
Click to collapse
Thanks for the reply, computer was messed up so couldn't see this sooner lol. Anyway, since I have no idea how to just pull the bootloader from a file, I'll have to do the whole thing it seems. Thanks for your reply ^_^
I have a galaxy s9+, and i wanted to get the best android experience by flashing a costume rom (TWRP) and rooting, i did it successfully with no issues, and working very well, downloaded some root apps and they worked fine one of the apps required me reboot my device to apply changes, once then...my phone stuck at a boot loop, i booted up to TWRP, did a factory reset, then format all data, still didn't work, i tried to repair/change system partitions and this time when tried to reboot TWRP shows a message: "os not installed" and now I'm still stuck the only thing I have now is TWRP...
I know how screwed up I am but I need a solution for this, it's my only phone i have ...
Reflash Stock ROM.
Ok I will try it then I will be able to install costum rom again ?
If you find a suitable Custom Recovery ( like TWRP ) and additionally a matching Custom ROM then the answer is YES.
jwoegerbauer said:
If you find a suitable Custom Recovery ( like TWRP ) and additionally a matching Custom ROM then the answer is YES.
Click to expand...
Click to collapse
The Actual rom I'm using TWRP it's the only thing I have now...
TWRP is a Custom Recovery, NOT a Custom ROM. Don't confuse things.
Just wipe everything from your phone and install custom ROM from TWRP.
dedq said:
Just wipe everything from your phone and install custom ROM from TWRP.
Click to expand...
Click to collapse
What's the difference between costume rom and costume recovery, is magisk a costume rom ? is android a stock rom? I need to understand things first...
jwoegerbauer said:
TWRP is a Custom Recovery, NOT a Custom ROM. Don't confuse things.
Click to expand...
Click to collapse
I need to understand things first, do you have time to explain pls ?
Bizzare user said:
What's the difference between costume rom and costume recovery, is magisk a costume rom ? is android a stock rom? I need to understand things first... of the custom recovery which you use to flash ROM.
Click to expand...
Click to collapse
Bizzare user said:
What's the difference between costume rom and costume recovery, is magisk a costume rom ? is android a stock rom? I need to understand things first...
Click to expand...
Click to collapse
TWRP recovery the custom recovery which you use the flash custom ROM.
Before you flash your ROM, you have stock Android and that means stock ROM.
Custom Android is the same as custom ROM. Stock Android is the same as stock ROM.
Magisk is a method you use to root your phone. It doesn't have to do anything with TWRP or recovery.
You have Magisk zip which you flash in TWRP recovery and your phone will become rooted.
dedq said:
TWRP recovery the custom recovery which you use the flash custom ROM.
Before you flash your ROM, you have stock Android and that means stock ROM.
Custom Android is the same as custom ROM. Stock Android is the same as stock ROM.
Magisk is a method you use to root your phone. It doesn't have to do anything with TWRP or recovery.
You have Magisk zip which you flash in TWRP recovery and your phone will become rooted.
Click to expand...
Click to collapse
That was really useful thank you now the thing that makes me worry is I'm not sure after I wiped the stock rom if the bootloader is unlocked and USB debugging is on, will i be able to flash the stock rom again ?
Bizzare user said:
That was really useful thank you now the thing that makes me worry is I'm not sure after I wiped the stock rom if the bootloader is unlocked and USB debugging is on, will i be able to flash the stock rom again ?
Click to expand...
Click to collapse
I have S9+.
I suggest you download Alexis ROM and just flash it. It's literally like stock ROM but it's custom.
Download it somewhere on your USB and then move it to your SD card so you can flash it. You can install it from the USB as well. You need an adapter for that.
dedq said:
I have S9+.
I suggest you download Alexis ROM and just flash it. It's literally like stock ROM but it's custom.
Download it somewhere on your USB and then move it to your SD card so you can flash it. You can install it from the USB as well. You need an adapter for that
Click to expand...
Click to collapse
dedq said:
I have S9+.
I suggest you download Alexis ROM and just flash it. It's literally like stock ROM but it's custom.
Download it somewhere on your USB and then move it to your SD card so you can flash it. You can install it from the USB as well. You need an adapter for that.
Click to expand...
Click to collapse
I've heard of Alexis ROM... is it stable ? What features i can profit from this rom ?
Bizzare user said:
I've heard of Alexis ROM... is it stable ? What features i can profit from this rom ?
Click to expand...
Click to collapse
It's literally like the stock ROM. I'm using Noble but the developer is the same. Noble is Android 11.