Develop Bugs

[Q] Installing Custom Roms on unlocked and rooted phone

So here is my given situation in hand.
1) I Unlocked and rooted my phone and upgraded to jelly bean from ICS.
2) Then later on installed Cyanogenmod rom (team shogun rufdroid)
3) While trying to upgrade. i screwed up and wiped and reinstalling the rom again and for some reason soft keys were missing so i had to wipe complete data and roll back to jelly bean 4.1.1.
4) Now how do i install custom roms now, coz if i use a g nex tool kit v9.1.it says my phone is already rooted and there seems to be a problem loading a bootloader.
I d appreciate if somebody can help me out with this..im still a novice ..trying to learn.

Damn it, don't use a toolkit.
Sent from my i9250

maddyreddy said:
So here is my given situation in hand.
1) I Unlocked and rooted my phone and upgraded to jelly bean from ICS.
2) Then later on installed Cyanogenmod rom (team shogun rufdroid)
3) While trying to upgrade. i screwed up and wiped and reinstalling the rom again and for some reason soft keys were missing so i had to wipe complete data and roll back to jelly bean 4.1.1.
4) Now how do i install custom roms now, coz if i use a g nex tool kit v9.1.it says my phone is already rooted and there seems to be a problem loading a bootloader.
I d appreciate if somebody can help me out with this..im still a novice ..trying to learn.
Click to expand...
Click to collapse
bk201doesntexist said:
Damn it, don't use a toolkit.
Sent from my i9250
Click to expand...
Click to collapse
QFT.
Use This
|
|
|
v​

OP read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my i9250

why step 3? if you had an issue with the rom you flashed, why not just wipe data and redownload that rom and flash it again from your recovery. or wipe data and flash a different rom. wiping data doesnt remove your rom, and doesnt take you back to stock, and doesnt remove root access. it just removes user data.
root toolkits are the absolute worst things to use on nexus devices. they prevent you from learning the very easiest basic procedures. without knowing the basic procedures, you should not even consider modifying your device in any way. learn about what you are doing/what you want to do, then root your device.

maddyreddy said:
So here is my given situation in hand.
1) I Unlocked and rooted my phone and upgraded to jelly bean from ICS.
2) Then later on installed Cyanogenmod rom (team shogun rufdroid)
3) While trying to upgrade. i screwed up and wiped and reinstalling the rom again and for some reason soft keys were missing so i had to wipe complete data and roll back to jelly bean 4.1.1.
4) Now how do i install custom roms now, coz if i use a g nex tool kit v9.1.it says my phone is already rooted and there seems to be a problem loading a bootloader.
I d appreciate if somebody can help me out with this..im still a novice ..trying to learn.
Click to expand...
Click to collapse
Don't use a toolkit....download the ROM and GApps onto your phone directly....download a file explorer like Astro or ES and make a folder where you want to keep your stuff or just keep them in the downloads folder.....I prefer twrp but you can use CWM or w/e custom recovery you want...now it depends if your upgrading your current ROM with a newer version of your ROM or not....let's start with a complete clean flash....reboot into recovery and make sure you have a backup of at least your current data....if you do do a factory reset wipe system wipe cache wipe dalvik cache (this is all done in recovery mode)....go to previous menu and then go to install....install the ROM FIRST!!!!!!! then the GApps....(newer ROMs have GApps included so make sure you read everything before you install anything). Once you install the ROM and GApps you can go to restore and restore data only....clear the cache and dalvik again then go to advanced and then fix permissions....hit reboot and then reboot system.....now this is my process others might do it differently and you may as well once you get a little better at it.....now a dirty flash would be something like if you are just upgrading to a newer version of the same ROM..... You would download the ROM and GApps reboot recovery wipe cache and dalvik install newer version of ROM and GApps (if applicable on the GApps portion).....once installed clear cache and dalvik again then advanced and then fix permissions then reboot....for kernels you just have to clear the cache and the dalvik cache and then install the kernel unless otherwise indicated..... Good luck let me know what happens and if you have any problems let me know

Seriously, there's no need to wipe caches, when flashing kernels or roms!
Factory reset, or factory reset+format /system at best. Most roms will wipe /system on their own.
Sent from my i9250

No issues,my device is working fine now..I'm on rufdroid v0.92.
But I still had to use a tool kit to install recovery..I tried doing it on command prompt and it was confusing ..next time I'll try doing it with out these tools ....anyways thanks everybody.
Sent from my Galaxy Nexus using xda app-developers app

Updating to 4.4.4 Sickness

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

[Q] Re-root after omni lollipop install

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!

Rooted OTA?

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.

Root / SuperSU Failing to complete? ( Help)

When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.

savvymatthew said:
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
Click to expand...
Click to collapse
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.

LS.xD said:
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
Click to expand...
Click to collapse
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.

savvymatthew said:
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
Click to expand...
Click to collapse
OnePlus.net offers the rom files as download:
OOS 3.2.6 (capable for OTA 3.2.8)
Open Beta 7
I'm using the Open Beta at the moment and it runs without any issues
OOS roms can be flashed with custom TWRP
For a clean installation just wipe partitions (System; Data; Cache; Int. Storage) with TWRP before flashing the new rom

Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.

Hw4ng3r said:
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Click to expand...
Click to collapse
Thank you for pointing on that I backup all my stuff on my computer once a week but others may not.
By never wiping your internal or manually deleting folders you will collect garbage over time when you change android installations.

I have a back up from when i first set it up, so its very old. After i Flash and set everything up again think im gonna start making weekly back ups, with all the roms and stuff for this phone probably be smart.
Thanks guys