Hi everyone,
I have a Note 4 Exynos version and recently i decided to make the root procedure. My steps was first update to 5.1.1 then, root by flashing the su zip file, flashing TWRP recovery and then i did a full backup to make sure i can keep my files intact just in case. I tried installing CM 12.1 but i had the " Execute updating binary failed etc..." and after a lot of tries i decided to restore my backup. The problem is that after restoring my phone keeps rebooting in randomly.. Can i unroot without flashing stock firmware, so i can keep my backup as it is?
Any thoughts appreciated.
5.1.1 can't be root just yet.
Flash stock rom & setup your phone to fix it.
You can flash another rom after that
So that is the reason for the random rebooting? To be honest i followed the procedure from a known website that was talking about rooting this particular phone with version 5.1.1 ...
Thanks for the response
I'm expecting my 910c to arrive soon and I'm currently reading for root procedures.
So, if my phone arrives with 5.1.1, I won't be able to root? and if I root can I later flash 5.1.1 without problems?
Also, please direct me to a threat that is safe to follow in order to root.
Of course you can root 5.1.1
Just read the development section and follow the instructions there
sent from somewhere
Antreassy i have followed the procedure from a website i do not wish to quote since it might be against the forum rules. But the result was not the best since my phone keep rebooting. So the only thing that saved it is by flashing the stock 5.1.1 firmware using odin and everything came back to normal.
From my own research i believe that at the moment the most valuable custom firmware is CM 12.1 and that is the reason i tried to flash it at first but without any success.
Related
I've been poking around the forums trying to figure out an answer to this, but nothing so far has worked. My question is a simple one:
How do I root a stock ROM of Android 5.0?
First, the tech stuff:
Device: SM-N900A / AT&T
Android: build LRX21V.n900AUCUEOC1
I had Android 4.4.3 (rooted with Towelroot), which I was finally able to force to upgrade to 4.4.4 by using ODIN to flash a firmware update. In the process, root access disappeared, but my overriding concern was to get Android 5. I found a stock ROM of it here, which I downloaded and which did install perfectly.
Now, I've tried a bunch of different things to get it rooted--including trying to flash the pre-rooted Android that Walter.White posted in another thread (my phone kicks back an "invalid signature" error when I try, the install always fails and what I get is a device that's like it's fresh out of the box)--I also tried the CF-Auto-Root route, with ODIN says fails and which causes my phone to freeze. Towelroot doesn't work, and I can't get Safestrap to work either (it complains that there is no root access and there's no Safestrap option in the restart dialogue box).
I know that I'm missing something, and I know that it's probably something absurdly simple. I've got no doubt someone else has cracked this, any chance someone out there could help me figure out what I'm getting wrong?
You must go back to android 4.4.3 and root like you once did, then flash the pre-rooted version android 5.0 and you're all set. Sounds like you have everything you need, just need to do it in the right order.
I rooted my wife's N9008V which was running Android 5.0 with Kingoroot and afterwards removed Kingoroot with Super-Sume. After that I installed SuperSu.
I know that I'm missing something, and I know that it's probably something absurdly simple.
very simple .
Op you are in the wrong forum this is NOT Note 3 AT&T forum .
I rooted my note 3 by flashing TWRP through odin then flashing the SuperSU.Zip package through TWRP
The n900a can't be flashed with twrp if it has a locked bootloader.
I have a Moto X running the Stock 5.1.1 using whatever root method was out when the phone first became rooted.
I want to ugprade to this ROM http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242 using the "Rooted 60 Deodexed" I haven't flashed a phone since I got this one, so I have a few questions.
1) I'm encrypted but using the custom TWRP from this post http://forum.xda-developers.com/showpost.php?p=65045112&postcount=474. Will that cause any issues?
2) If I want to revert to a Nandroid of my 5.1.1 coming from the 6.0 ROM, do I just restore the Nandroid or are there additional steps to take?
3) Coming from what I assume is a classic system root, but flashing a new ROM, do I need to go back to unrooted stock first, or just flash the ROM for the new fancy systemless root?
4) What is the difference between Odexed and Deodexed?
4a) Will that affect Xposed/XPrivacy at all?
Thanks so much!
If I were you, I would first back everything up, then flash the stock 5.1.1 unrooted file in this thread: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 after doing a factory reset in TWRP. Do a full wipe (this should undo any encryption you've got going on as well). This would be the best way to avoid any issues along the way. (I always do a full wipe when flashing something new out of habit to avoid issues). You may be able to just skip this install if doing a full wipe as well. I'm not too familiar with having encryption on my phone.
After you're booted back up on stock unrooted, flash whichever 6.0 rom you want in TWRP after a factory reset. Systemless root as far as i know is only good if you want to use android pay. Xposed should be fine to use, generally speaking, but you can't use Xposed if you want to use android pay, it breaks it.
If you want to revert to your 5.1.1 nandroid, I would flash that stock file I linked to again and THEN restore your nandroid. I haven't heard of any issues downgrading to lollipop from marshmallow on the 2015 model like there were on the 2014 model between lollipop and kitkat, but to be safe, I'd make sure I was on 5.1.1 before restoring the nandroid.
The difference between odex/deodex is explained here: http://forum.xda-developers.com/showthread.php?t=2200349
Again, these are steps I would take if it were MY phone. Others in the forums may have better solutions or ideas.
@shkmkr Thanks! I'm going to do all that. My main goal is to make sure that at the end of the day, Skvalex's Call Recorder still works as I use that heavily for business calls. I don't really use Android Pay so I don't mind that breaking. I just want to avoid (soft/hard) bricking the phone by downgrading/upgrading around with an unofficial TWRP.
I would like to avoid wiping the encrypted data partition if possible since, encrypting is not the easiest with root. It tends to not encrypt on reboot except under special circumstances which I forget partially. Stock recovery is definitely one of them though and I don't know where to find the stock recovery for 6.0 on this phone as Motorola doesn't have the official 6.0 posted yet.
Could you let me know if this works for you? I made a THREAD a while back and didn't get any help on it. I would like to follow this if it works.
Also I messed up one time and I did infact downgrade back to lollipop and restored my nandroid with no problems. I want to do my 2nd attempt but I want to get it right.
you can get the stock recovery from that first link i mentioned under the 6.0 section.
This is too complicated for me to explain everything but here is my Cheat Sheet !
If you have been flashing you probably already have these files.
1. Odin SamMobile N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CPG2_N910VVZW2CPG2_N910VVRU2CPG2_HOME.tar
( ! System and Cache only ! )
SAME as the thread Safe System Updates_6.0.1 MM_FlashFire, dm-verity work around, SM-N910V
Except Now that SamMobile has posted 2CPG2 I was able to skip steps and go straight to Flashing the firmware package with FlashFire.
No need to do over the air updates.
-----------------------------------------------------------------------------------------------
Note: I was able to skip the recommended rooting of 5.1.1
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
I have been flashing and playing with roms on many devices and there is something I don't understand. Why can't someone inject root into the factory tar file and make the upgrade a much simpler process? If our devices once rooted are considered the same as a developer edition, why can't we simply flash whatever image we want?
PaulPizzRom is just as good......
tbtaf said:
I have been flashing and playing with roms on many devices and there is something I don't understand. Why can't someone inject root into the factory tar file and make the upgrade a much simpler process? If our devices once rooted are considered the same as a developer edition, why can't we simply flash whatever image we want?
Click to expand...
Click to collapse
OR BETTER!!!!!!
Think you could fix your 'HERE' links in your OP?
hsbadr's CPD1 is already rooted or something? I just re-went through the unlock process and i thought if you flashed a stock firmware it re-locked the bootloader?
azreark1 said:
Think you could fix your 'HERE' links in your OP?
hsbadr's CPD1 is already rooted or something? I just re-went through the unlock process and i thought if you flashed a stock firmware it re-locked the bootloader?
Click to expand...
Click to collapse
Chick on the link in OP
Safe System Updates_6.0.1 MM_FlashFire, dm-verity work around, SM-N910
That's all I got right now
I am in : [ROM] [5.1.1] Kyubi Note 5 Port Final [N910VVRU2BPA1] [2/23/16]
Can i flash stock rom 5.1.1 by flashfire?
Could someone please upload the ota zip file only
I'm on 5.1.1 PA1/PD1 with TWRP installed and would love to move to 6.0...would I have to start all over to accomplish this or could I begin in the middle of your guide where I am?
thanks!!
Nevermind..I'm on 6.0
Many thanks!
mistake
Posted too soon. Need to delete and repost later with more info
What happens if I have lineage 15.1 and I want to return to 7.0 stock can I do it?
should I do a back up? I read that I could lose the imei :crying: how can I avoid it?
I would use this tutorial
https://www.youtube.com/watch?v=F_6LQr01GhY
thank you all for the help and advice :good::fingers-crossed:
sorry for my bad English
I don't know about lineage 15.1, but I had the OTA 8.1 update on my XT1644, and it broke my speakerphone and made my phone run like crap, so I just rolled back to stock 7.0 and am VERY happy.
I DID lose IMEI (I had IMEI=0), but from what I understand, it was because I manually flashed 7.0 from adb. I think that had I used the TWRP file, it wouldn't have happened.
I got IMEI back by following the directions in this thread:
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
I also disabled OTA backups by doing this: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12
So that Motorola can't push an OTA on my phone and brick it.
You should make a complete backup following the directions of this thread:
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-complete-partition-t3875787
I know virtually nothing about messing with phones or Android. My motivation was that if I couldn't get rid of OTA 8.1, I was going to throw away my phone and get something different. And I didn't want to spend the money on a new phone. I figured I'd brick what I have, before I spent money on a new one.
I pretty much followed the directions on this thread:
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
Except that by loading 7.0 manually, it caused me to lose IMEI. Knowing what I know now, after flashing TWRP, I would have flashed 7.0 using TWRP. And I don't think I would have lost IMEI then.
Once I had 7.0 loaded, I flashed Magisk to get root.
Once I had root, I used a file explorer to go in and delete the app that pushes the OTA, so Motorola can't screw me. As far as I know, I am now permanently on 7.0.
Do this at your own risk. But you're already running Lineage, so I assume that you know way more about this than I do.
Edit: Just realized I kinda rambled here. So here's the condensed version of what I would do, I think... do at your own risk.
1. Use that thread I linked to back up your *everything*
2. Save stock 7.0 file, Elemental X file, and Magisk file on your SD card (all from XDA)
3. From TWRP, flash 7.0
4. Once you have 7.0, from TWRP flash Elemental X.
5. From TWRP, flash Magisk
6. From that link I posted, delete the file that stops OTA's.
I think you'll now be where I am, with rooted stock 7.0. But you should still have your IMEI. If you have IMEI=0, follow the directions in the link I posted.
slimbobaggins said:
I don't know about lineage 15.1, but I had the OTA 8.1 update on my XT1644, and it broke my speakerphone and made my phone run like crap, so I just rolled back to stock 7.0 and am VERY happy.
Click to expand...
Click to collapse
I am eternally grateful for your help and message!! :good::good::good:
but in the tutorial that you sent me: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
indicate that the installation should be done manually by adb... do you think I should do it for TWRP ??
---------------
[...]
Flashing Stock Firmware:
1) Download the correct firmware for your device from http://www.filefactory.com/folder/c6cdedc45a775d27
2) Download adb and fastboot from https://drive.google.com/file/d/0B5j...ew?usp=sharing
3) Extract the firmware into the folder containing abd and fastboot.
4) Reboot the phone into Bootloader (power off, then press the power and volume down buttons simultaneously).
5) Execute these commands and make sure you receive an 'OKAY' after each command.
[...]
-------------
thanks
That tutorial was written years ago. I think back then, the only way was to manually install.
If you manually install 7.0, you will wipe your IMEI and have to restore it like I did.
I suggested the TWRP install because I *think* it wont wipe the IMEI.
If it does, you should still be able to recover it... but again, I barely know what I'm talking about. So please follow the thread about backing up your entire phone and persist, first. I am merely sharing with you what I did to roll back mine to 7.0, your experience may vary.
And again, if you do roll back, make sure you follow the instructions to disable OTA, because if you accidentally take an OTA, it will brick your phone for sure.
I literally just figured out how to do all this, this weekend. Prior to that I knew *nothing* about this stuff. So please read everything you can to educate yourself... its all here on this very good forum, you just have to piece it together. I am 100% a newbie.
I have a Tab E 8 (SM-T377P) and I cannot get any version of TWRP new than 2.8.7.0 to flash, Magisk will not flash, and no custom roms will install.
I've tried both lineage 15.1 and 16, both the standard and GO versions.
It's on stock firmware, 5.1
I rooted with cfautoroot with Odin 3.10.7.
Hopefully someone has an idea on what I need to do.
:edit:
I was able to get magisk installed by rerooting with cfautoroot and then doing a full unroot and restoring bootimage with supersu. Still can't install any roms though
So I was able to update to Nougat using the rom posted in this thread. It was the ONLY place I was able to find the stock firmware. I was hoping that installing 7.1.1 would put me on a new bootloader/kernel that might allow me to install an Oreo rom.
Still, the only TWRP that I can get to boot is the one posted in this thread, which is 2.8.7. The dev posted links to 3.0.2-1 that do not work, but I've tried multiple different versions of TWRP, and they all boot loop and I have to reinstall 2.8.7 via Odin.
All roms say that they are intended for SM-T377P and cancel, although my device is exactly that.
So, after doing a total wipe and flash back to stock 7.1.1 using Odin, I was able to boot back into Download mode and install the latest version of the TWRP posted in this thread - https://forum.xda-developers.com/ga...official-lineageos-16-0-galaxy-tab-e-t3847488
Still won't let me install a custom rom though...
Alright got it up and running on Lineage 16.
I bought this off of eBay to use as a dashboard for my smart home. When I opened it and put it into download mode for the first time, I noticed that it said it was running a custom binary even though everything looked bone stock, it wasn't even rooted. I didn't pay it any mind and went about trying to root it and install TWRP as the dew guides stated. Nothing would work, so I decided to upgrade it to stock 7.1 since it was on 5.1. After I did this, I noticed that in download mode it stated that it was on stock binary and I was able to update to the most recent TWRP for this device. Then I was able to install Lineage and all is well now.
This thread doesn't appear to be getting any traction, but I figured I'd update it in case someone searches a similar issue in the future.
Krunk_Kracker said:
Alright got it up and running on Lineage 16.
I bought this off of eBay to use as a dashboard for my smart home. When I opened it and put it into download mode for the first time, I noticed that it said it was running a custom binary even though everything looked bone stock, it wasn't even rooted. I didn't pay it any mind and went about trying to root it and install TWRP as the dew guides stated. Nothing would work, so I decided to upgrade it to stock 7.1 since it was on 5.1. After I did this, I noticed that in download mode it stated that it was on stock binary and I was able to update to the most recent TWRP for this device. Then I was able to install Lineage and all is well now.
This thread doesn't appear to be getting any traction, but I figured I'd update it in case someone searches a similar issue in the future.
Click to expand...
Click to collapse
Thank you for documenting your progress.
I am in a similar situation.
I am the original owner of my t377p.
I'm going to try your steps to see if it will work for me.
UPDATE:
Flashing back to Stock and starting the process all over again, as you described above--fixed the problem. I am now running LineageOS16.
Thank you!
I'm glad it worked for you!
That's exactly why I updated the thread, I knew I wouldn't be the last one have this odd issue.
Do you have a copy of twrp the servers are down and I've been trying for week to download it