I can't seem to get root now that I've installed Omni lollipop 5.0.2 for my ls 970. Free gee will not boot on both fresh install of rom and app. I tried rooting with newest philz touch in recovery. Also, no dice. Tried towelroot and framaroot hoping something would work...nothing. I had cm12 unofficial running and it had root somehow. Is there any way to re-root with Omni? Is it just a matter of changing kernels? Thanks in advance.
thejase said:
I can't seem to get root now that I've installed Omni lollipop 5.0.2 for my ls 970. Free gee will not boot on both fresh install of rom and app. I tried rooting with newest philz touch in recovery. Also, no dice. Tried towelroot and framaroot hoping something would work...nothing. I had cm12 unofficial running and it had root somehow. Is there any way to re-root with Omni? Is it just a matter of changing kernels? Thanks in advance.
Click to expand...
Click to collapse
I have root, no problem. Did you wipe everything before install? Wipe data, system, cache, dalvik cache. I am using the multi boot TWRP and have installed omni as primary (the same as any other recovery would be) and have no problems. I beleive root is built in. If you have problems, try flashing superSU from recovery. I have used 2.42 and 2.44 but there may be a newer one now...
here is 2.42. Follow the link, download the zip. Flash in recovery, wipe caches after install.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
dopy25 said:
I have root, no problem. Did you wipe everything before install? Wipe data, system, cache, dalvik cache. I am using the multi boot TWRP and have installed omni as primary (the same as any other recovery would be) and have no problems. I beleive root is built in. If you have problems, try flashing superSU from recovery. I have used 2.42 and 2.44 but there may be a newer one now...
here is 2.42. Follow the link, download the zip. Flash in recovery, wipe caches after install.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Thank you. The built in one didn't work but the newest beta is perfect!
Sent from my LGOG with much love to the xda community!
Related
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Edit: I have now also tried
1. Restoring to original stock touchwiz 4.1.1
2. Wiping cache from original recovery
3.Rerooting
4.Restoring a backup of 4.3
5.Attempted to update to C-Rom, Carbonrom, Resurrection Remix -- No Luck Fails
Corvetrims77 said:
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Click to expand...
Click to collapse
I'd like to know myself. I'm stuck too. I can flash a 4.3 rom and everything works, but when I reboot, it gets stuck. All was fine until I flashed Wicked rom and flashed " MJ2 bootloader MJB" Now every time I reboot it gets stuck. Also If I try a reflash, the only way to get it to bootup is to format before flashing.
Try using Philz Touch as your recovery program.
audit13 said:
Try using Philz Touch as your recovery program.
Click to expand...
Click to collapse
I had cwm when I originally started out, switched to twrp to see if the recovery was the issue.
I assume you were running the latest version of cwm before you switched to twrp so it can't be the recovery.
Are you doing a full wipe of the system, cache, data, and Dalvik before installing the ROM?
Yea every time I wiped data, cache, dalvik , I even reformatted once. I have managed to boot up into tasl650AOKP which is a d2lte build but no other ROMs. I mean at this point it looks like I should just wait a bit to see if it is something with the ROMs interacting with my phone(as per all phones are made different)
Sent from my d2lte using Tapatalk
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
audit13 said:
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
Click to expand...
Click to collapse
Yeah I gave it a shot still no dice. I keep seeing other people having similar issues, so I am still leaning it has to do with the differences in d2lte builds vs dtatt builds
Sent from my d2lte using Tapatalk
d2att ROMs are okay? Just not any d2lte?
audit13 said:
d2att ROMs are okay? Just not any d2lte?
Click to expand...
Click to collapse
As I stated before I am able to boot int Task650AOKP(Which is a d2lte build), any of the others that I have tried have not worked. There are some updates out today, I am going to attempt again and post back results.
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
audit13 said:
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
Click to expand...
Click to collapse
Thanks for the help, I actually was just able to boot into C-Rom by following the same steps except I am using TWRP. No idea really what caused the Roms to get stuck on boot. Quite annoying.
I had TWRP on my phone but I was having problems installing ROMs when I first got the phone in January.As soon as I switched to CWM or Philz, no problems at all except for ROMs based on a stock 4.3 ROM.
I can't update my N7100 from previous Omnirom to latest CM11. I wiped my phone, installing latest CM11 zip and phone is stuck at N7100 logo and restart to recovery. When I install Omni zip everything is working fine. I'm tried TWRP and Philz recovery but no results. Please help
did you wipe /system, /cache, /data and dalvik? (full wipe).
atmos929 said:
did you wipe /system, /cache, /data and dalvik? (full wipe).
Click to expand...
Click to collapse
Yes of course but I think CM isn't extracting to /system because when I leave recovery it shows there's no root and asks if I want to install it.
emlo16 said:
Yes of course but I think CM isn't extracting to /system because when I leave recovery it shows there's no root and asks if I want to install it.
Click to expand...
Click to collapse
Recoveries tend to do that... they do not detect superuser from any CM based ROM and offer you to install supersu after a ROM install and rebooting system.
I you do full wipes and you have tested latest Philz and TWRP recoveries... I can only suggest you to double check that the CM11 ROM is the correct one for your N7100.
It is strange that you encounter issues with CM based ROMs... these usually install without problems... I've encountered problems booting TW based ROMs, but not these. Sorry I can't be or more help. Good luck .
EDIT:: wait a second... according to your screenshot, you did a full wipe after installing the CM ROM... you are deleting your ROM that you just installed . The steps are:
1.- full wipe
2.- install ROM
3.- Install GAPPS
4.- wipe Dalvik <-- (some devs recommend this step, others don't... doesn't hurt to do it anyway)
Hi, I'm on the 4.4.2 version of the Sickness, with the MDL bootloader. I've updated the modem to NH7.
Do I need to go through the whole process of updating the firmware, re-rooting, etc., or can I just do a full wipe and update to the Sickness' 4.4.4 V3?
I tried a full wipe and installing it today, but I ran into bootloops/other failures.
its better to use the latest recovery like twrp becuz in twrp 2.8.0.1 which is the latest recovery you can choose wipe and then advance wipe and choose dalvik cache,system,data and cache then wipe and that normally takes care of the boot loops
rblckmnjr84 said:
its better to use the latest recovery like twrp becuz in twrp 2.8.0.1 which is the latest recovery you can choose wipe and then advance wipe and choose dalvik cache,system,data and cache then wipe and that normally takes care of the boot loops
Click to expand...
Click to collapse
CWM and Philz also allow you to wipe system, data, cache, and even the non-existent Dalvik cache partition.... Your post makes it sound like TWRP is the only recovery that does that Just saying..
jonnyboy2040 said:
Hi, I'm on the 4.4.2 version of the Sickness, with the MDL bootloader. I've updated the modem to NH7.
Do I need to go through the whole process of updating the firmware, re-rooting, etc., or can I just do a full wipe and update to the Sickness' 4.4.4 V3?
I tried a full wipe and installing it today, but I ran into bootloops/other failures.
Click to expand...
Click to collapse
As to your question; you should be able to do a full wipe (system/data/cache and even though it literally does nothing because the partition doesn't exist, dalvik) and then flash with no problems. I would say that since you're still one of us few lucky ones still with MDL bootloaders, try to keep an official update as a very last option!
Were you trying to flash a kernel or any other mods along with the ROM? If so, flash only the ROM itself and see how it works.
You say bootloops/other failures... that means you bootloop a lot, and when you don't bootloop something else happens. Could you be more specific on the "other failures?" Any error messages? Were you able to pull a logcat? Did you compare the MD5's? Doesn't sound like a bad download, but you never know...
i understand what you saying however i ran into the same problem using philz touch and got the latest twrp and havent got stuck in boot loops since i read a forum on this and using older recovery to flash kitkat roms has been having people phones stuck in a boot loop and throwing errors after flashing and they updated the recovery to fix it
Sh*t, I have TWRP 2.6 and never have a problem. IMO (and some others) newer versions don't seem to play well with others. That goes for all Recoveries.
As for your issue, you might have a bad DO. Try re downloading the ROM, full wipe and then flash.
well my phone didn't like philz touch it works better with the latest twrp recovery
I actually ran into this last night with philz.. I tried flashing insane 4.4.4 v3 and got stuck in a bootlooop I couldn't recover from. It flashed v1 just fine, but it just wasn't having any of v3. I had to use Odin to flash the latest TWRP and have had no problems.... :/
lordcheeto03 said:
I actually ran into this last night with philz.. I tried flashing insane 4.4.4 v3 and got stuck in a bootlooop I couldn't recover from. It flashed v1 just fine, but it just wasn't having any of v3. I had to use Odin to flash the latest TWRP and have had no problems.... :/
Click to expand...
Click to collapse
Sickness mentioned something about a script that was causing bootlegs when flashing
Hi,
hope I don't ask a repeat question: It's possibile to update the N7 2013 with root and custom recovery without lose data? (when I accept the update the device reboot in recovery mode and that's all)
Many thanks
cheers!
The OTA won't work with custom recovery. Search for scrosler's flashable 5.0.1 rooted ROM thread--at least a few of us have flashed that without losing anything. Update your bootloader, then flash the ROM and wipe cache and Dalvik.
I was on rooted 5.0 with TWRP. I think the easiest way to get the 5.0.1 update without losing apps or data is to download the stock, rooted rom from Scrosler found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , use Wugfresh's NRT 1.9.9 to update the bootloader listed in Scrosler's post, and then dirty flash (wipe Dalvik and cache if you want) the 5.0.1 rom using TWRP. Painless and fast with no loss of data or anything.
That's the one! Worked for me too, from rooted 4.4.4 w/TWRP--no data loss.
newkydawg said:
I was on rooted 5.0 with TWRP. I think the easiest way to get the 5.0.1 update without losing apps or data is to download the stock, rooted rom from Scrosler found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , use Wugfresh's NRT 1.9.9 to update the bootloader listed in Scrosler's post, and then dirty flash (wipe Dalvik and cache if you want) the 5.0.1 rom using TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
many thanks!! work!
Hi, is is possible after rooting to replace TWRP with the stock recovery, stay rooted and enjoy OTA updates.
Rooting is out of question, but besides the fact that 3.2.0 is still not available from the Oneplus website and it is hard to judge which unofficial source is trustworthy, I would prefer not to have to reroot and install xposed each time I flash a full image.
I am also interested in this.
Is this possible without wipe?
I guess root and xposed should be reinstalled even after OTA:
ErzlordCaron said:
Hi, is is possible after rooting to replace TWRP with the stock recovery, stay rooted and enjoy OTA updates.
Rooting is out of question, but besides the fact that 3.2.0 is still not available from the Oneplus website and it is hard to judge which unofficial source is trustworthy, I would prefer not to have to reroot and install xposed each time I flash a full image.
Click to expand...
Click to collapse
Download complete ROM from here: https://www.androidfilehost.com/?fid=24591020540823780
1. Booted into TWRP wiped Cache & Dalvik
2. Flashed Full ROM 3.2.0
3. Wiped Cache & Dalvik
4. Flashed systemless SU and systemless Xposed v85.7
5. Wiped Cache & Dalvik
6. Reboot
You will not lose data and be updated at the same time.
nidhish91 said:
Download complete ROM from here: https://www.androidfilehost.com/?fid=24591020540823780
1. Booted into TWRP wiped Cache & Dalvik
2. Flashed Full ROM 3.2.0
3. Wiped Cache & Dalvik
4. Flashed systemless SU and systemless Xposed v85.7
5. Wiped Cache & Dalvik
6. Reboot
You will not lose data and be updated at the same time.
Click to expand...
Click to collapse
Thanks, but I know how to do that - aside from the fact that I would like to get my ROM from Oneplus or at least a dedicated XDA-dev thread, instead of some link in some forum. The question was if I can flash the original recovery to be able to receive OTA updates.