Im new to rooting. And stupid enough to proceed in installing things i don't fully understand how to do... I installed MonsterUI 5.0 but when I later rebooted my phone. It says system ui not responding with no notification bar and can't boot into recovery. Safe mode does the same thing. I can boot into odin tho. What do I do? I don't care about losing any data.
Katia23 said:
Im new to rooting. And stupid enough to proceed in installing things i don't fully understand how to do... I installed MonsterUI 5.0 but when I later rebooted my phone. It says system ui not responding with no notification bar and can't boot into recovery. Safe mode does the same thing. I can boot into odin tho. What do I do? I don't care about losing any data.
Click to expand...
Click to collapse
Since you are in this forum, would it be safe to assume you are trying to root an i535, the Verizon version of the SGS3?
If you are working with the i535, what bootloader and modem were on your device before you installed MonsterUI?
Related
just use the one click root tool by kennethpenn, work perfectly thanks. use titanium back to do a backup of all the app and system then took out all the att bloatware. i have few questions at this point.
1.
will i be able to get OTA updates from att? what will happen to all the bloatware that i deleted? would they appear again?
2.
what happens if i do a factory reset on the phone? would i brick the phone? under normal condition that will erase all apps i installed and return it to factory setting, that means all the att bloatware will be back? will i lost root?
3.
what other things i can do after i root the phone at this point?
thank you for your help
no one can help me with those questions??? anyone???
i am sure a lot of people have the same question.
1.
will i be able to get OTA updates from att? what will happen to all the bloatware that i deleted? would they appear again?
I'm not 100% sure on this, but as long as you're running an actual AT&T ROM (not an Asian or Rogers ROM), you'll be notified of the OTA's. Now, if you're not using the stock Recovery image (that is, if you've installed CWM Recovery), you won't be able to apply the update. OTA updates get applied via the stock Recovery image.
2.
what happens if i do a factory reset on the phone? would i brick the phone? under normal condition that will erase all apps i installed and return it to factory setting, that means all the att bloatware will be back? will i lost root?
If you do a factory reset from CWM or within the phone's UI, you're fine. Root will remain in place, and you won't brick it. It just clears the user data from the phone, and should leave "sdcard" intact. However, I'm not 100% sure what happens if you do a factory reset from the bootloader. So just don't do it that way, unless someone else can confirm that it's okay.
3.
what other things i can do after i root the phone at this point?
You ca use apps like AutoKiller to change your memory management, for one. That's about all I'm doing with root right now. If we ever get custom kernels, you'll be able to overclock your CPU. If you search the Play Store for "root," you'd doubtlessly find some other root apps that you may be interested in.
Hope this helps!
Don't ever ever ever install an OTA on any rooted Android device. At the least, it won't work anyway, or you will lose root. At the worst, you will be stuck in a bootloop. Updated ROMs (based on the OTA's, but rooted, and safe to flash) usually get posted in Development soon after the OTA's go out. That is what you want to install.
craig0r said:
However, I'm not 100% sure what happens if you do a factory reset from the bootloader. So just don't do it that way, unless someone else can confirm that it's okay.
Click to expand...
Click to collapse
I can confirm that it's OK. My phone was rooted and stuck in a boot loop. I did a factory reset. It was reset and still rooted after the fact. So you can do it.
thank you all
redpoint73 said:
Don't ever ever ever install an OTA on any rooted Android device. At the least, it won't work anyway, or you will lose root. At the worst, you will be stuck in a bootloop. Updated ROMs (based on the OTA's, but rooted, and safe to flash) usually get posted in Development soon after the OTA's go out. That is what you want to install.
Click to expand...
Click to collapse
Just to clarify, pre-rooted versions of the official ROMs (which often get posted on XDA, as I mentioned) may need unlocked bootloader to install, so this will possibly not be an option for a while. Although there may be alternate safe ways to update (but not OTA). For instance, a leaked 1.83 firmware version is already available as an RUU in the Development subforum. Apparently, its okay to install via RUU, then re-root.
In general, the safe thing to do is to read up on here when updates are released, and see if there is a safe way to update on a rooted phone.
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Reciprocate said:
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2046439
Reciprocate said:
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Click to expand...
Click to collapse
hey guy my question is did u unlock ur bootloader before rebooting also remember if u can manually boot into cwm u can redo the rom its either the up volume or down plus multi function button and power button at same time to go right to cwm
wingtytn said:
hey guy my question is did u unlock ur bootloader before rebooting also remember if u can manually boot into cwm u can redo the rom its either the up volume or down plus multi function button and power button at same time to go right to cwm
Click to expand...
Click to collapse
I think i actually locked it after i finished the install. And then restarted, do softbricks occur when you re-lock your bootloader?
Also another question..is there any way to check the /system /data partitions from inside the phone (terminal app maybe?) are correctly set to r/w over r/o (i don't like unplanned installs )
Soft bricks always occur on a locked bootloader. There are file managers that can do that like solid explorer.
jmxc23 said:
Soft bricks always occur on a locked boot loader. There are file managers that can do that like solid explorer.
Click to expand...
Click to collapse
Ah dully noted in the future the boot loader will be left unlocked! and thanks for the app recommendation i downloaded it and checked all my permissions I'm slightly less terrified to restart my phone now
thanks for all you help
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
arsenaljordan said:
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
Click to expand...
Click to collapse
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
GUGUITOMTG4 said:
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
Click to expand...
Click to collapse
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
arsenaljordan said:
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
Click to expand...
Click to collapse
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
GUGUITOMTG4 said:
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
Click to expand...
Click to collapse
I have already flashed the stock recovery and ROM back to the device
Hey all, before I start I'd like to apologise for making the post here but I don't know what you guys would classify the state of my phone as, "bricked, soft-bricked, hard-bricked", I have no clue! As a result I have no idea what threads to start looking in so I've come here to make this, sorry again!
I'm here looking for help because I think I've completely destroyed my Moto G and really really would like to fix it.
Basically, I had been running an old version of CyanogenMod for months and was not able to update due to the fact my bootloader was not updated. After finally updating it through a tool on XDA, I installed the newest version of CyanogenMod onto the phone and it was all going well, except for the fact all of my Google apps were crashing and making it impossible to use.
Now, I'm not sure why, but without taking any precautionary measures or looking into it at all or what I needed to do, I then decided to try and flash a Paranoid Android rom onto the phone, which installed fine. I load the phone up and something comes up with a passcode saying I need to unlock it to use the phone. I put in some random things and eventually get it, but it says my data is corrupted and therefore I need to reset to factory settings and there's a button there to do it. I think "why not" and click.
So now, the phone did something weird and basically went into a bootloop of the PA logo, so I restarted the phone and went to the bootloader thing. When doing "Normal Startup" it loads the phone with the PA logo like before, comes up with a brief "Android is Upgrading" screen before showing me the passcode screen for half a second, before repeating this, thus having a bootloop. Every so often, I can put my code in and press the reset button again, but it does the same thing.
On the other hand, if I try to access my ClockworkMod recovery system, the screen repeatedly flashes with the CWM background of the Android Alien guy, as if to say it keeps trying to start but it cannot.
TLDR: I cannot access my phone through a normal powerup or through my recovery, have I screwed it completely?
I'd hugely appreciate any help here guys because I'm stressing like I never have before here, thanks!
EDIT: it is the X0123 version!
Spaciouz said:
TLDR: I cannot access my phone through a normal powerup or through my recovery, have I screwed it completely?
I'd hugely appreciate any help here guys because I'm stressing like I never have before here, thanks!
EDIT: it is the X0123 version!
Click to expand...
Click to collapse
Just a few questions before I start suggesting a full flash to stock.
Did you have any SIM passwords, boot passwords, CWM passwords before flashing?
Also In CWM does it flash before any options are selected and did you dirty flash the new ROM over the old ROM?
Anyway, your phone is not hardbricked as it can get to recovery so thats good news.
I would suggest flashing your phone back to factory stock using the tools here on XDA (http://forum.xda-developers.com/showthread.php?t=2542219). That should hopefully resolve most of the issues and then if you feel like it you can start flashing custom ROMs again.
Hello everyone well I just messed up big time with my phone, last night i was in a hurry to find a way to get a bypass for a app that didn't support root.
So I saw there was a way to do that with a module in xposed. I then precided to install the xposed apk and update xposed within the app. Then the trouble startet, when I rebooted my phone up it was stuck in a boot loop. I tried going in to recovery mode to factory reset the phone and delete the cache. I have been looking for a way to fix this all day but since I was to lazy to install twrp when I first rooted my phone I can't seem to find a way to fix it. I tried to flash a stock firmware using odin but I only get stuck with the the text saying NAND Write start!!.
Any suggestions on how I can fix it or is the phone dead?
Thanks for all help in advanse
Installing xposed Framework within the App doesn't work. This Option only works for non-Samsung device since Samsung made a lot of changes to ART. You have to flash the Framework manually in twrp.