Related
Hello community
I am able to get as far as unlocking the bootloader but I'm not sure as what to do next. I am on a fresh clean 4.3 stock upgrade Can some one suggest the best rooting method and possibly a very good ROM and kernel for this device please...
jgentry151 said:
Hello community
I am able to get as far as unlocking the bootloader but I'm not sure as what to do next. I am on a fresh clean 4.3 stock upgrade Can some one suggest the best rooting method and possibly a very good ROM and kernel for this device please...
Click to expand...
Click to collapse
I recommend backing up your data before making any changes then follow the Nexus 4 Root Guide at http://forum.xda-developers.com/showthread.php?t=2266654 to install your preferred recovery utility, either Clockworkmod or TWRP.
If you plan to install a custom ROM and kernel anyway, there really isn't much point in gaining root on the stock 4.3 ROM. If you must gain root on the stock 4.3 ROM, you will need to download Chainfire's experimental SuperSU v1.41 (available at http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip) and transfer the file to the root folder of the Nexus internal storage. Start your phone's bootloader by powering down the Nexus and simultaneously holding the volume down and power buttons approximately 5 seconds until the bootloader screen appears. Next use the volume up/volume down buttons to highlight Recovery and press the power button to start the custom recovery. In recovery press Install, then highlight the file SuperSU-JWR66N-S005-130625-1.41.zip and move the button slider to the right to install root. Reboot the phone and update SuperSU from the Play Store.
There is a wide selection of custom ROMs and kernels available in Nexus 4 Android Development and Nexus 4 Original Android Development. Every custom ROM already includes a kernel, so you only need to download and flash a kernel if you need specific features inlcuded in the custom kernel. I recommend taking some time to review the ROMs listed in these two forums, look at the screen shots, and read some of the user comments regarding the ROMs that look appealing to you. Once you identify the ROM(s) you would like to try, download the ROM(s) and tranfer the zip file to the root folder of the Nexus internal storage.
Before flashing any ROM make sure your battery is charged at least 50%, then boot into recovery and make a nandroid backup of your existing setup. Next wipe data, cache, and Dalvik cache and install the custom ROM from the associated zip file. Bear in mind that the first boot after flashing a new ROM will take a few (5 to 10) minutes. After booting the phone configure your Google account, update your Play Store apps, and configure the phone settings to suit your preference then reboot your phone. Be patient: Try out the new ROM for a couple of days before making a decision to move to a different ROM.
IT CAN BE DONE
Here's how I did it. (And don't blame me if you brick the phone, etc., etc....)
PLEASE DO NOT ATTEMPT IF YOU DO NOT UNDERSTAND THESE NOTES! Read them thoroughly!
1. Install stock NC2 (Instructions are all over)
2. Root with towelroot.
3. Install latest SU from the play store and update binary (you know the drill, right?)
4. See Chainfire's site here. http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 Get FlashFire
5. Place the AT&T stock lollipop .tar file on your SD card. It is available in the note 3 forum.
6. Run FlashFire. Once it has done its thing, click on the + sign.
7. Click on flash firmware package and navigate to the stock .tar file.
8. FlashFire will analyze the file and you will see a screen with partitions checked. These are the partitions that FlashFire can write (AND ROOT)
9. Click the download sign at the top on the red bar.
10. Click on the check mark to Create New Archive (FlashFire will create a .tar.md5 file take note of where it is saved and COPY TO YOUR PC BEFORE you run FlashFire! You will need it!
11. Next you will see the screen with ACTIONS on a red bar. Scroll to the bottom and touch FLASH
12. FlashFire will now write the partitions that are checked. When it reboots the phone, IMMEDIATELY hold the volume down, home, and power button to enter download.
13. Go to your PC where you copied the archive (that .tar.md5 fike). Right click on the file and choose rename. Remove the .md5 from the file name or odin will likely give you an error.
14. Open odin and connect your phone. Place the .tar archive FlashFire created in the AP section and flash. It will write the partitions that FlashFire could not.
15. Reboot and enjoy rooted lollipop on your phone.
Hate that I still have to wipe data to get it to boot at all, but a minor gripe I suppose. Just hate having to reinstall my apps and set them back up. Thanks for sharing this, been waiting for something like this for a while!
Yeah but if you're already on rooted nc2, why not just flash the stock rooted lollipop rom?
Doesn't that process require using SafeStrap, where this process does not?
netracerx said:
Doesn't that process require using SafeStrap, where this process does not?
Click to expand...
Click to collapse
You can use flashfire...
Plus why go through all this hassle to reach the same result?
That's absolutely true. but think it is a matter of preference. I had some issues with Safestrap, but were it still supported for lollipop, I would probably still be there. I also had a soft brick when I attempted to do a backup, which supposedly still works by booting from the power screen. SO for those who would prefer a cleaner option, this might suit them better. Flashfire also has the potential to install other custom roms. I am still looking at that option.
swapavi said:
You can use flashfire...
Plus why go through all this hassle to reach the same result?
Click to expand...
Click to collapse
this is the first post i've seen for the N900A that advised using Flashfire, all other posts required using Safestrap (which i personally did not like the idea of using just because it wasn't actually updating the OS on the phone, but essentially tricking the phone into loading a different set of files much like multi-booting). if it were possible to use Flashfire with the rooted lollipop roms, i'm surprised none of the thread OPs updated their posts to reflect that.
FlashFire has only been out since April. It is Chainfire's successor for Mobile Odin. It takes a while for all of the phones to be tested. There are a couple of other users that have tested it. Just search the FlashFire forum for Note 3 and you can read the comments. At least one other has used it on the AT&T variant.
reboot into download mode
I just finished your method successfully. Thank you. I would like to add that there was an option to reboot into download mode after flashing with FlashFire. I didn't have to worry
about immediately holding vol. down . I think the version of FlashFire I used is a little newer. Anyway thanks again!
I will keep trying
Hi all,
I was able to go through all the steps but keep getting stuck on step 14. Odin fails at the very very end and never finishes. I have done the whole process 3 times over.
Questions:
1. When picking the .tar in step 7, I am selecting the largest file of lollipop. I believe it is an AP file about 2.2 Gigabytes. This is the right one to select in step 7??
2. On step 10 when it ask you to Create New Archive, do i check ALL the boxes?? Nothing is checked by default when i press the download sign in step 9.
Other than these two things, everything else seems to work nicely. I did also notice that when Flash Fire runs and writes the system, wipe is set to OFF. I figured it was like that on purpose but just saying.
Thanks in advance,
John :good:
Sorry for the delay. I have moved on to the S6, so been busy with it.
For step 7, choose whichever ROM you wish to use. The one you have should be fine.
With regards to the second question, Flashfire should check the files in step 8 that are needed for the archive. Are you using a stock rom for step 7? If not, it might be able to flash without a separate tar file.
Ok,
Yes it was stock and thanks for the tip i will give this a shot as soon as i can and see how it goes.
So this will work to Root the Note III on Lollipop?
What exactly does Flashfire do in this case? Is it unlocking the bootlader, allowing for flashing a custom rom? Or is it only rooting Lollipop? I was looking at safestrap for running a custom rom on the AT&T Note 3, and someone mentioned in another thread that Flashfire was a better option for doing so, with no need for the multi-boot workaround. Thanks to anyone who can straighten me out on this, and if Flashfire doesn't allow for flashing a custom rom on the AT&T note 3, is there anything else out there that does?
I'm under the impression that the AT&T note 3 has a locked bootloader, which is my point of confusion.
fitzly said:
What exactly does Flashfire do in this case? Is it unlocking the bootlader, allowing for flashing a custom rom? Or is it only rooting Lollipop? I was looking at safestrap for running a custom rom on the AT&T Note 3, and someone mentioned in another thread that Flashfire was a better option for doing so, with no need for the multi-boot workaround. Thanks to anyone who can straighten me out on this, and if Flashfire doesn't allow for flashing a custom rom on the AT&T note 3, is there anything else out there that does?
I'm under the impression that the AT&T note 3 has a locked bootloader, which is my point of confusion.
Click to expand...
Click to collapse
Great Guide and find.
Flashfire has the power to bypass the security that would provent Odin from installing , for example a custom kernel, so be carefull with Flashfire, it installed a custom kernel on my phone and flagged Knox to a 1
Followed the steps in the 1st post...worked flawless! May I add its good to clear cache & delvic cache as well
Sent from my SAMSUNG-SM-N900A using Tapatalk
Excellent. I don't like Safestrap, so this was perfect... I didn't have to wipe my phone, and everything went perfectly the first time. One note, I did have to put my phone in Download Mode (as stated in the OP) after the reboot from Flashfire. Thanks so much to all who worked on this!
Update: The OC2 update happened pretty much immediately after I booted. The OTA update actually managed to complete, and I still have root.
I am currently on 4.3 MI9 version..
i rooted it with chainfire method root de la vega.
Now can i flash NC2 with odin and continue the thing ?
Can someone point me to the stock lollipop tar? I cannot for the life of me find it in any of these forums. Please & thank you.
Chocu1a said:
Can someone point me to the stock lollipop tar? I cannot for the life of me find it in any of these forums. Please & thank you.
Click to expand...
Click to collapse
look here, if you still have issues let me know
http://forum.xda-developers.com/showthread.php?t=2703006
I've read pretty much every source I can find on getting a custom ROM up on my LG G2, which I haven't even rooted in the past 2 and a half years. My warranty ran out a while back and I'm getting a bit bored with stock now, and I want to start flashing, but the last time I did this was with my old HTC Desire HD.
As you can see I'm on 20d on my LG G2. It's a Hong Kong version for some reason, lol. What I considered doing was the following: update to the latest Lollipop official ROM using the LG Flash Tool (it gives me an available update to 30d); root using the rooting app, install a recovery with AutoRec Lollipop, flash a thermal recovery from the installed recovery (very scared of my phone overheating, I'm even considering putting it on a large, fast-running fan while doing anything, read too much about the phone overheating and making the screen yellow); back up my phone's IMEI data; use the recovery to install a brand new (I'm hoping a Marshmallow) ROM. I also understood that I need to flash a bootstack to change my bootloader to a KitKat, because it can be "fooled" using the BUMP thing. Is that correct? Do I even have to update my phone to Lollipop in this case? Also, how likely is it to overheat while doing all of these procedures?
Thanks in advance!
Sorry for the necroing my old thread, but I have yet to do anything with my phone. I am also still on KK. I saw that I can start rooting and install TWRP from it straight away. After that I need to flash a bootstack, right? How likely is it that I can brick myself? By that I mean what could get mixed up to get a brick while flashing. Also, has anyone had overheating issues while doing root, recovery installation and flashing things (newer TWRP, bootstacks, new ROM)?
Hi, i can understand your situation as i was in same till today, g2 with stock kitkat.
i finally installed cm13 after rooting it and the phone feels fresh.
you have understood most things right and ready now.
you dont need to upgrade to lollipop if youdont want to, you can start from kitkat itself.
few things i can tell you to begin here,
Root your G2,
for kitkat i found few good methods. Either do it via ioRoot using pc. or you can use towelroot or kingoroot apps to do it from phone itself. I used kingoroot since i didnt have a system with me. You can find these apps by searching at google, jst tyoe kingoroot. At first i was skeptical but it worked nice.
after root, you download autorec app, this is to install a custom recovery(twrp) for kitkat. you just have to install the app and run it and press install recovery/twrp and it'll do the rest.
after you have twrp installed, you need to upgrade it to latest version. For that download blastgator's twrp for your model and flash it through your recovery.
oh and dont forget to learn, how to enter into recovery yourself, since each G2 model has different method.
once you have these things you can start flahing roms. Most of the instructions on how to flash certain rom with what bootloader and bootstack etc. is written in its own thread, so you can learn that from that rom's thread that you will flash.
but basically, you need kk bootloader and lp bootstack for cm13 and above. usually both these things come in one zip. (if not you check for hybrid bootstacks)
Just make sure you are downloading things For your Model, if you try to flash different models stuff into yours, itll brick.
The autorec app, blastgator's twrp and ioroot can be found in a sticky thread in G2 general section, along with many other files and guides in that thread, theres complete index in that thread of all thing for all g2 models .
here : http://forum.xda-developers.com/lg-g2/general/05-10-index-guides-fixes-roots-t3218178
also usually the phone doesnt heat up while flashing, just make sure your battery is more than 80% before you start and itll be ok. Even if it does a little, after a custom rom itll be fixed. I suggest you try cm13 for starters as your first custom rom.
hope this helps you :good:
Good Luck ::highfive:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
hitmancho said:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
Click to expand...
Click to collapse
to upgrade from kitkat you need lp or hybrid bootstacks. they have images (. img files) that are needed for your phone to function properly., like aboot, modem, radios etc. Hybrid bootstack contains aboot from kk and everyhing else from Lp. So when youll flash a bootstack, youll need to wipe everything, except internal storage(or external if you have one) , before you can flash it. that wipe will include, cache, dalvik cache, system, data. so basically all the old system stuff will be gone before you can flash this bootstack. i hope after reading that youll know that you cant access your old kk installation since itll be wiped, therell be nothing to boot to. if youll try, it will give you errors on lg logo.
understand it like this, to install new 21 inches tyres to your car, you need to upgrade the rims to hold a 21 inch tyre right? what will happen if you just put the 21' tyres on old 15' rim or old 15' tyres on new 21' rims?
the cm 13 devs dont recommend you to flash bootstacks because most of the models took the official lollipop update, which put everything in their phone to lolipop level. since there is no official marshmallow(MM) bootstack for our phone (because no official update), everyone developed ways to utilize lollipop bootstack to function on a custom MM Rom. Since most models are already on lollipop, theres no need to flash lollipop bootstack while flashing custom rom. That step is mostly for those who are still on stock or custom kitkat based rom. So they say to get official lollipop through kdz method, instead of flashing Lp bootstack before gettig their rom. But remember if a rom developer asks to install a bootstack for their rom, you should consider it if you dont have much knowledge about it, cause if you dont follow instructions, you can soft brick, in that case youll need hybrid bootstack.
see if you are using everyhing proper for your phone then your phone wont brick. only thing that can go wrong with that condition is your execution, your steps. As long as you dont make a mistake in these steps everything will go fine.
ill explain it what you should do.
1. first root your phone.
2. when done rooting, install "root checker" from google play. itll confirm if you have root or not.
3.Then you come back here and find autorec app from the link i gave you in my previous reply. download that, install the autorec app. and follow on screen instructions and itll install twrp recovery for you.
4. then come back here again, and find blastgator's twrp, from the same link in previous post. itll be the one whih says "twrp with f2fs". download it and remember where you put it.
5. turn off phone, boot into recovery (i hope you've learned by now how to get into recovery of your g2 model). Now youll be in recovery, hit install button there and find where you put that file, flash it, then reboot recovery, youll have new recovery after that. then you reboot into system.
now upto this point, you can play along in your kk, have fun with features, say last goodbyes and all lol. Because everything stock kk related will be gone, past this point, including all the apps you have installed.
[IMPORTANT] : after rooting and installing recovery, get bootstack zip, rom zip and gapps zip files downloaded and placed together in a folder on your phone, before you start with flashing bootstack. Because you wont be able to boot back into system after flashing just bootstack.
now you prepare for MM, boot into recovery, now since you are in kk, you need to install LP bootstack, and for that you need to wipe everything using your recovery's wipe feature.
6. in recovery, hit wipe, hit advanced, select cache, dalvik cache, system, data. [ Dont select internal storage otherwise all flashing files will be gone and youll be left with a brick.] and wipe.
7. Now hit the back button to go back to main recovery screen once wiping is finished. hit install, flash the bootstack zip.
8. now your phone has new bootloader but its still empty, like you got a body but no soul . so hit back button, hit install and flash the rom zip you downloaded.
9. now flash gApps same way.
10. once its done, just hit reboot system. no other steps needed.
11. be patient, first boot takes longer than normal boot.
12.enjoy MM :highfive:
you probably know these steps from all the reading but its for your reference, so you dont screw up at all and be safe from bricking.
you can get google apps from opengapps website. you need to get ARM-> 6.0 -> (your prefered ones) pico/nano/micro/etc.. pico has the least amount of gapps, all important ones are there in pico, then extra will increase as you go up from pico to stock. stock has all the gapps. size will also increase as you go up. so choose as you prefer.
now once you have a cm13 /MM based rom, you wont need to flash bootstacks for other roms from next time unless the developer instructs to do so.
good luck
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
andrew2432 said:
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
Click to expand...
Click to collapse
cwm is clockworkmod, its a custom recovery. i think you meant CM 13, mm rom.
yes, the Cyanogenmod team have placed root access into the rom, so once youll be finished wih installing cm 13 rom, you can just go to settings, Tap build number repeatedly until a message will show "congrats you are a developer now". that'll open developer options in main setting screen Go into that and youll see root access. turn it on. youll have root.
you can check in root checker app to confirm root access for confirmation. you wont need super su app in any of these roms anymore.
your steps :
stock
1. root
2.autorec (for installing twrp on your phone) for kitkat its on forums, for lollipop its in google play. just get the one for your model, search for autorec in google play.
- blastgator's twrp requires you to have any version of twrp beforehand in order to install his version.
3. download and save blastgator's latest twrp, when youll go to download his twrp, itll be written there which one's is the latest version, just download that one and flash it through recovery.
4. Yes place all files in your phone, you can get gapps from opengapps.org/
select arm- 6.0- whatever size you like(, pico is lightest contains all essential gapps, stock contains every gapps)
5. wipe yes.
6. flash bootstack
7. flash rom
8. flash gapps
9. once gapps done, just hit reboot system.
10. enjoy
yes go for it when you have more than 80% battery, this is to ensure that all flashing steps go through without any issue, you dont want your phone to run out of juice while flashing rom do you that could cause soft bricks. so always keep battery more before flashing.
[IMPORTANT] : remember to read instructions of the rom you're installing and adjust the steps as instructed in there.
Goodluck :highfive:
Awesome, I forgot to.flash gapps prior to something I just did, not sure if it will cause increased global warming or thermonuclear war...update soon
@MarshisnotMellow
Gapps installed!! No Internet connection on the d800 and something sinister has happened to my unlocked WiFi Hotspot so I'll have to check for play store capabilities later!! Thanks for the help!!
I decided to go with the latest 29.10.2016 nightly of CM13 for my first run on this phone. Everything went through, no one died, lol. I'm going to start installing and restoring stuff now, get Xposed on, like I have on my TF701T tablet and trick out my phone's appearance. Just a note - after you install new bootstacks your phone's MAC address will change, so if you have a WiFi network with a MAC filter you might want to add your new address.
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
I apologize as I feel this must be asked all the time, and I looked around on the forums for stickies and what not, but I didn't have any luck. Here is where I'm at, I want to flash Reserrection Remix, or another 64 bit ROM so I can try out the new google camera on my Moto G5 Plus. I miss the portrait mode from my old iPhone 7 Plus (long story on the move), and was looking to try this out. Given the nature of what I am doing I wanted to be careful as not to brick my phone.
Is there a good tutorial on everything I need to do to get a custom rom on the phone? Ideally with the ability to get back to stock if things go sideways? I would appreciate any help that isn't "google it" because I have tried that too and I am not sure the best place to start. I know XDA is a great resource from my experience, and hopefully someone can get me some steps, but even a link to a good post about the process would be helpful, I understand that.
Thanks for the help so much, I appreciate it.
Well, first time fashing can be overwhelming. I'll try to be brief and point you into right directions.
In short, flashing a custom ROM follows these steps:
1. Unlock your bootloader.
2. Flash a custom recovery (TWRP)
3. Get your desired ROM
4. Get the compatible gApps.
5. Flash ROM through recovery.
6. Flash gApps through recovery.
7. Reboot.
However, any of those step could go wrong and brick your debice. Not trying to scare you but just to understand that this is a risky process which will void your warranty (most probably) as soon as you successfully execute the first step.
I'll post the relevant links, just need to get to my laptop.
Commandersouth said:
I apologize as I feel this must be asked all the time, and I looked around on the forums for stickies and what not, but I didn't have any luck.
...
Thanks for the help so much, I appreciate it.
Click to expand...
Click to collapse
The following steps and guides assume you're familir with things as adb, fastboot, custom recovery etc. Even if not in depth but what they are and what they mean. If you have no idea about any of these. Stop. Read about it and then come back else you might end up bricking your phone.
So as to begin,
Step 1: Unlock your bootloader.
Step 2: Flash a Custom Recovery(TWRP). since you plan to flash RR which is 64 bit ROM, you will need 64 bit TWRP . Offical TWRP is here.
Step 3. By now you should have TWRP and booted into it at least once. Next step is to download the ROM and GApps. Head to the ROM thread and download the latest version. Get the GApps as well from Open GApps (ARM 64, 8.1). Copy the zips to your device (External SD card preferably. Internal memory might not be accessible by TWRP).
Step 4: Boot into recovery. Select Backup and take a Nandroid backup (Extremely Important. You would be able to go back if something goes wrong). Copy this backup to a safe location.
Step 5: Wipe -> Advanced -> wipe system,cache,dalvik,data.
Step 6: Install -> Select ROM.zip file. Flash it.
Step 7: Install -> Select GApps.zip file. Flash it.
Step 8: Wipe -> Advanced -> cache and dalvik only.
Setp 9: Reboot.
First boot might take a while.
You should boot into RR.
These are the standard steps for flashing. However, I've omitted some details that you will find in the respective threads. Be careful. Read before you do anything. At any point if something doesn't make sense, stop and ask.
I want to flash Reserrection Remix, or another 64 bit ROM so I can try out the new google camera on my Moto G5 Plus. I miss the portrait mode from my old iPhone 7 Plus (long story on the move), and was looking to try this out.
Click to expand...
Click to collapse
If you want it only for camera purposes, It's a lot of hassle for such a small thing IMO. (Not trying to discourage you). Moreover, Camera is buggy in most of the LineageOS based Roms (including ResurrectionRemix). Check out the thread.
Just an add on to the above post:
Backup /system as img, it backs it up as a bit perfect copy.
Back up everything in TWRP, you can scroll down and select more partitions, the most important is EFS. I'm saying this because I missed them when I started off. You might need this later on as it stores your IMEI.