This morning I was able to update my rooted phone to OK4 from OD3 keeping root and my Knox counter at 0 using metalfan78's [ROM]OK4 Stock Rooted Zip, and stock partitions from the full tar. I was able to use Flashfire to create the stok partitions tar and flash them via Odin. I did this based on another thread I followed to update to OD3 to keep root and Knox at 0 a while back. So far everything seems to be working good for me, I dirty flashed and everything seems to have gone like taking an OTA update.
I got the ROM here and used the odexed version:
http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692
Stock partitions file is save to my google drive here, it contains everything from the full tar except the system and cache (not sure how well sharing like this will work):
https://drive.google.com/file/d/0Bw7_CzqViQzSSGZHSE1TS3loN1E/view?usp=sharing
Followed the instructions for the update to OD3 here:
http://forum.xda-developers.com/spr...w-to-update-to-g900pod3-5-0-keeproot-t3136932
Hopefully this will help someone get updated, or just provide stock partitions for other use.
If Knox is already tripped this probably isn't worth the effort
You MUST be rooted already for this to work.
Edit:
1. After a couple hours S Health stopped working about every 5 seconds, making it difficult to do anything. Clearing the data and signing back in seems to have fixed it.
2. Play store continuously fails to download app updates on WiFi or Mobil data.
3. Wiped and reinstalled the ROM with Flashfire on Jan 1. I have not had any issues since.
Thank ya for this post, it has actually been a while since I have updated my phone. I haven't had any issues with any of the apps thus far. It's been a little over 24 hours since I've updated. Also, I think my phone runs a lot smoother with the update than it use to. Also, I don't have any issues with the play store updating. I'll post issues if any occurs.
dave011182 said:
This morning I was able to update my rooted phone to OK4 from OD3 keeping root and my Knox counter at 0 using metalfan78's [ROM]OK4 Stock Rooted Zip, and stock partitions from the full tar. I was able to use Flashfire to create the stok partitions tar and flash them via Odin. I did this based on another thread I followed to update to OD3 to keep root and Knox at 0 a while back. So far everything seems to be working good for me, I dirty flashed and everything seems to have gone like taking an OTA update.
I got the ROM here and used the odexed version:
http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692
Stock partitions file is save to my google drive here, it contains everything from the full tar except the system and cache (not sure how well sharing like this will work):
https://drive.google.com/file/d/0Bw7_CzqViQzSSGZHSE1TS3loN1E/view?usp=sharing
Followed the instructions for the update to OD3 here:
http://forum.xda-developers.com/spr...w-to-update-to-g900pod3-5-0-keeproot-t3136932
Hopefully this will help someone get updated, or just provide stock partitions for other use.
If Knox is already tripped this probably isn't worth the effort
You MUST be rooted already for this to work.
Edit:
1. After a couple hours S Health stopped working about every 5 seconds, making it difficult to do anything. Clearing the data and signing back in seems to have fixed it.
2. Play store continuously fails to download app updates on WiFi or Mobil data.
3. Wiped and reinstalled the ROM with Flashfire on Jan 1. I have not had any issues since.
Click to expand...
Click to collapse
I followed your instructions and everything went smoothly, but at least once a day I get a message saying: "Device must restart. Device will restart in 25 seconds.". Do you get this? Any suggestions on how to stop it from happening?
IMBigWillie said:
I followed your instructions and everything went smoothly, but at least once a day I get a message saying: "Device must restart. Device will restart in 25 seconds.". Do you get this? Any suggestions on how to stop it from happening?
Click to expand...
Click to collapse
Sorry for my delayed response.
I was having a random system reboot, and assumed it was from my bad habit of dirty flashing. I think what ultimately fixed it for me was using flashfire to flash the stock tar(as far as it recommended) and inject root. Metalfan recommend flashing via Oden and rooting before installing his rom, but that would have tripped kmix for sure. After flashing the stock tar via flashfire I had no data even on WiFi. I flashed Metalfan's rom to get me working again quickly and haven't had any random reboot issues recently. My knox counter is still at 0.
I'm sure I should recommend wiping data in this process but that's up to you. I can't say for sure that I did, then restored backed up data or not. I was pressed for time that morning, and needed my phone working.
dave011182 said:
Sorry for my delayed response.
I was having a random system reboot, and assumed it was from my bad habit of dirty flashing. I think what ultimately fixed it for me was using flashfire to flash the stock tar(as far as it recommended) and inject root. Metalfan recommend flashing via Oden and rooting before installing his rom, but that would have tripped kmix for sure. After flashing the stock tar via flashfire I had no data even on WiFi. I flashed Metalfan's rom to get me working again quickly and haven't had any random reboot issues recently. My knox counter is still at 0.
I'm sure I should recommend wiping data in this process but that's up to you. I can't say for sure that I did, then restored backed up data or not. I was pressed for time that morning, and needed my phone working.
Click to expand...
Click to collapse
Thanks for getting back so soon! I actually did a clean flash and still am having the issue ... I will definitely try your method tonight!
IMBigWillie said:
Thanks for getting back so soon! I actually did a clean flash and still am having the issue ... I will definitely try your method tonight!
Click to expand...
Click to collapse
You may also want to try using flashfire to create your own stock partitions tar to flash in this process to be sure my file on drive isn't somehow corrupted. If you used it in the first place. Use the flash firmware package option, wait for it to read the file partitions, then the download icon to create your partitions file. Use what's highlighted by default, create your file, and transfer it to your computer. Flash what is selected by default from the tar and reboot into download mode to flash the partitions file just created.
If all you want is stock root and your data works you shouldn't need to flash anything else at that point.
Related
Hey guys, I am having some issues flashing roms through CWM as well as rerooting.
A bit of backround info
Device: GT-P7510
Started with latest OTA stock rom. I was wanting to use titanium backup to uninstall some bloatware.
Rooted successfully following the wifi only version forum post on how to root.
Did what i wanted, but now i wanted more.
Decided to try to get Jellybean on my device. Loaded into CWM - flashed - successful.
Now i ran into the issue of no flash support - needed for school work i do on my tablet. Tried to follow guide on installing flash.. did not work, tried the titanium backup method as well with no prevail.
Decided to flash back to ICS. I chose the CM9 ROM.
Loaded into CWM - wiped data / cache/ dalvik / Installed rom from SD card - flashed successfully
I noticed that my home button was not working. so after another data wipe etc. and re flash of the rom it did.
I then could not get googleplay to function just kept getting server error no matter what i tried. I tried installing apk from the web. did not work. and tried loading gapps.zip through odin. Installed other google apps that did work, just not google play..
So i was like holy hell. what to do now. Tried installing another ICS ROM ( the one that mimics jellybean)... It fails instantly after unloading package or something of that nature. I tried about 3 different roms and get the same issue.
So i then followed the guide to unroot - it required flashing the stock ROM through CWM . I tried this but got a status 7 error. Not really sure what that was so i found another guide.
The alternative guide had me load the original ROM for the device via odin. Worked great!!! I thought i was in clear sailing. Updated to the OTA ICS ROM. And then went to follow the root guide again. It acted as if it was rooted, but upon reboot option in CWM it says root access might have been lost.. do you want to fix. I tried both no and yes. Reguardless i do not gain root.
I tried flashing other roms through CWM - they all fail instantly ( not with any specific error messages ) just says aborted.
Any idea on what i may be doing wrong?
What version of cwm u using ?
5.5.0.4 works best for our tabs coz he has not got some verification for unsigned zips something like that .
Hmm i think the problem is when u updated ota it took your root away so i would suggest flashing cf-root again via odin
Just guessing though really strange, perhaps back up data on sd card and format it too i know its a pain but could help aswell
;/
Sent from my GT-P7500 using xda app-developers app
I was on 6. something. So that may be my issue.
I did try an older version v4.0.0.4 which was included in the guide i used but that did not seem to work either. I will download that version and see what happens.
As far as flashing cf-root. I am going to do a forum search but the method i used used the file Samsung_galaxy_tab_10.1_root.zip through CWM.
it is always risk to Odin back to stock and update OTA I have bricked 2 android devices by doing this .......once you install custom roms it is always better not to install official update ..... ur device is not rooted properly just go to unrooted stock rom if possible and later get root.zip then try rooting ur tab using it .......and this might help ...... forum.xda-developers.com/showthread.php?t=1474971..........
CHEERS
HIT THANKS BUTTON IF I HAVE HELPED
Hi, I have a Nexus 7 2012 wifi nakasi & my 5.1.1 OTA just landed. As my Nexus is rooted using CF-auto-root & had a TWRP 2.8.5.1 recovery flashed, I fastboot flashed the recovery.img from the 5.1.0 archive & then clicked the button to install the OTA.
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Thanks
Had the same issue.... Just flashed the update without wiping the use info, so far seems to have worked... Not yet noticing much improvement though so don't get to excited.... Will keep watching it to see if it still crashes in sleep mode whilst sitting in the desk doc/charger...
Sent from my Nexus 7 using XDA Free mobile app
---------- Post added at 07:40 AM ---------- Previous post was at 07:32 AM ----------
Update: loads of system & none system apps still hanging and force closing some without the usual report/wait/OK option
So far:
- Google map
- Android System
- Facebook
- BBC iPlayer
- Chrome
Probably worth a full wipe and re flash to remove any gremlins.....
Sent from my Nexus 7 using XDA Free mobile app
FIXED
JustinSB said:
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Click to expand...
Click to collapse
I just flashed the system.img from my 5.1.0 archive (the recovery had already been flashed from the first time I tried it), waited half an hour for the OTA to flag up again & it all worked perfectly & upgraded exactly as it should. I haven't tried to root it again yet, as I want to see if it makes a difference.
So that's it, if your Nexus 7 2012 wifi won't let you install the 5.1.1 OTA, flash system.img & recovery.img from the 5.1.0 archive & you will be good to go, with all of your existing software, settings & data still intact. Naturally, you will need to re-root it though.
I flashed the 5.1.1 recovery, boot, and system images and then did a full wipe in recovery. Upon booting into the system, I was offered to restore my previous apps and data which all worked well but took a while to download and install the apps. I had to spend some time setting up the screens but 5.1.1 is running very well (better than 5.1) and I've since flashed twrp to get root. I do believe the wipe is important to get the best performance from the update.
I agree with the poster above me. Not wiping the device, cobbling together some unapproved update scheme pulled out of your ass, then complaining the performance sucks is just plain stupid. Do it right, and it will run butter smooth. But hey, I'm perfectly OK with snapping up several N7's DIRT CHEAP when all the idiots who can't follow instructions start dumping them on eBay and Craigslist thinking they're "broken". I have two cars that could use an in-dash install.
JustinSB said:
Hi, I have a Nexus 7 2012 wifi nakasi & my 5.1.1 OTA just landed. As my Nexus is rooted using CF-auto-root & had a TWRP 2.8.5.1 recovery flashed, I fastboot flashed the recovery.img from the 5.1.0 archive & then clicked the button to install the OTA.
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Thanks
Click to expand...
Click to collapse
JustinSB,
Since you've already flashed your ROM's stock recovery, I *think* the problem you're encountering is the same one I had when I moved from 5.0.1 to 5.1: The rooting procedure you're using installs a non-stock kernel, which resides in the boot.img partition and is detected in the pre-flash checking phase of things in the OTA update.
If it were me, and I wanted to save a significant amount of time on the update (i.e. keep my userdata and bootloader partitions the same), I'd download the 5.1.1 image archive, uncompress/untar/unzip all the archives, and do the steps outlined here. They involve wiping the cache, recovery, boot, and system partitions and flashing the latter three with the updated images. Definitely do not fail to do any of those steps. Fwiw, and as I note later in that thread, I didn't re-flash the bootloader as it's the same in both ROMs.
All I did to finalize things was to boot to twrp via fastboot and generate a Nandroid back up, and then re-root using the CF-Auto-Root procedure. Afterwards I was set and experienced no particular system slowdowns. The whole process took about 15 minutes, including waiting for the dalvik-cache to reinitialize. I typically do not flash twrp, I just boot to it from fastboot as needed.
As a poster has pointed out in his non-diplomatic way, this is not the recommended path to updating, so if you encounter problems going this route, you can always do the full reset thing and re-load all of your userdata from a back up as a second option.
Which ever path you decide to follow, I wish you good luck.
cheers,
john
Well, I guess I'm going to do the unthinkable and reply to my own post to say that I've just followed the procedure I described above, this time to update from 5.1 to 5.1.1. It also took a total of 15 minutes with the longest portion of that time taken by the dalvik-cache reinitializing during the first reboot.
Good luck to you, OP. I hope that you upgrade goes as smoothly.
cheers,
john
I found only one way to root the galaxy s7 edge but it includes erasing everything and thats just too much trouble for me since i don't trust backup apps with my apps data and all
my model is sm-935FD
this the method i found :
https://youtu.be/nlj76YvxGYo
thank u
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
You only need to erase everything if you want to flash custom roms in twrp. Otherwise you can just root with cf autoroot and you're all set
As the others said, flashing cf autoroot in odin won't erase anything, will leave your phone as is and will add supersu.
You should be aware that by rooting you will trip the knox flag, which permanently breaks samsung pay, and will break the following stuff on the stock rom: private mode, secret mode in the browser with fingerprint authentication (which can later be fixed by flashing a custom Rom).
If you want a properly working twrp recovery, you will have to erase everything, including the internal storage of the phone, there is no way around it.
If you absolutely must have root and you're into custom roms then I say do it now, if you're OK with the stock firmware I would advise not to root. This phone doesn't have too much development and you should not expect too many custom ROMs. I personally regret rooting.
I'm erase mi data because I want to do twrp backups, if you don't want to use a custom recovery for flash Roms and use a nandroid only flash supersu.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
Glad I came across this thread, as I was having the same thoughts. How easy is it to just flash recovery back to stock? or do you need to flash the complete firmware package?
TwinCalibre said:
Glad I came across this thread, as I was having the same thoughts. How easy is it to just flash recovery back to stock? or do you need to flash the complete firmware package?
Click to expand...
Click to collapse
Flashing the whole fw of course 1 of the way. Maybe if we can extract stock recovery from the fw then just odin it?.
Sent from my SM-N920C
if your on nougat and try to flash TWRP, your device wont boot....they dont have a decrypt solution to 7.0 right now.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
Have anyone tried and successfully done it?
there are many ways to root
I recommend use TWRP to root with SU apk file
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
In nougat it will disable access to data folder and force you to format, but if you flash stock firmware nougat the same it was in and reboot it everything was like before.
Basically backup everything using non root apps and adb then format then restore.
Today I accidentally did oem unlock to OFF then rebooted and then it said custom binary blocked by frp. I then flashed many nougat versions but they all caused force close of 2 things ims service and srbg? I ended up flashing nougat from January 2017 dqlc. I got everything back and working. Next I did twrp and supersu etc but data encryption failed. Then I flashed stock dqlc and got everything back. Use home csc or otherwise it will erase everything. Now I have to backup everything.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
Click to expand...
Click to collapse
That's not horse**** at all. If your storage is encrypted (most of them are by default) then it will force you to format once you flash TWRP. I took ages of trial and error of flashing stock firmwares and bootloaders etc via Odin to get it all back as I couldn't afford wiping (even if I had backed up).
Anyone reading this thread and wanting to try it should be careful.
I also found no way to backup ALL apps and ALL their data & settings reliably without root (Helium gets only part of the job done) so I could not risk wiping and restoring. I have too many apps configured and fined tuned that I use regularly.
Sorry for necro, but I found out the hard way after being badly advised ...
mastabog said:
That's not horse**** at all. If your storage is encrypted (most of them are by default) then it will force you to format once you flash TWRP. I took ages of trial and error of flashing stock firmwares and bootloaders etc via Odin to get it all back as I couldn't afford wiping (even if I had backed up).
Anyone reading this thread and wanting to try it should be careful.
I also found no way to backup ALL apps and ALL their data & settings reliably without root (Helium gets only part of the job done) so I could not risk wiping and restoring. I have too many apps configured and fined tuned that I use regularly.
Sorry for necro, but I found out the hard way after being badly advised ...
Click to expand...
Click to collapse
And finaly do you find a way to restore your data after installing TWRP ?
By now I would hope your important data is 100% redundantly backed up.
Of all the things that can and do go wrong with rooting, data lose shouldn't even enter into the equation unless you really goofed up bad.
Only two types of data users, those who have lost data and those that will...
I consider any data on internal memory 100% expendable. A complete reload/restore takes me about 2 hours and that's without the luxury of rooting.
At any moment I'm (and you should be too) ready to do a factory reset regardless of the cause without critical data lose.
After two forced back to back forced reloads on my 10+ I learned my lesson.
Thanks Blackhawk for your explication
I am on the second part of user which have lost his data but only the configuration not the contact, photo, etc...
But without root they are plenty of data (configuration, autorisation, widget) which take very long time to "reinstall" and those data are not saved if you are not root. And sometime with root also. They are not important but the time to restore them is very long and use a phone without his custumization is very anoying.
That's why I'm loocking for a way to save it without root or root without loosing those data.
jameslevalaisan said:
Thanks Blackhawk for your explication
I am on the second part of user which have lost his data but only the configuration not the contact, photo, etc...
But without root they are plenty of data (configuration, autorisation, widget) which take very long time to "reinstall" and those data are not saved if you are not root. And sometime with root also. They are not important but the time to restore them is very long and use a phone without his custumization is very anoying.
That's why I'm loocking for a way to save it without root or root without loosing those data.
Click to expand...
Click to collapse
A clean wipe of all settings data means no misconfigurations or malware will survive.
Nuke em.
I'll see how well SmartSwitch does saving the home page next reload. If it screws up it will cost another reload... of course.
Only shortcuts/folders, Good Lock, One Handed Operation plus etc kill me with setup time but it's no big deal. I've gotten pretty adapt at it
Poweramp is completely, redundantly, backed up as that would take weeks to sort of recreate, a true nightmare... as it is now, it only takes a few minutes to do.
My music database has existed for over 15 years. I've lost count of the number of backup copies I have for it... plus the source CD/HDCDs.
Currently have 3 up to date copies to be expanded soon to 4.
Overkill for data backup is a good thing.
Be cautious with the latest N910TUVS2EPG2.
You might not be able to downgrade the bootloader once its updated.
If you look back at the history of builds for the N910T you will see the following:
N910TUV U2 EPE3 = 6.0.1
N910TUV U2 DOK2 = 5.1.1
N910TUV U1 COG2 = 5.0.2
Pay attention to the U1 & U2 numbers.
Notice that you can upgrade and downgrade between 6.0.1 and 5.1.1 but cannot downgrade to 5.0.1
Both 6.0.1 and 5.1.1 have U2 in their build. In the past (at least on some devices) once these numbers change is when you cannot downgrade to a different number.
So whats my point? Look at the latest build. N910TUV S2 EPG2.
"S2" This very well could mean you can not downgrade to 5.1.1 and or PE3 6.0.1.
It also could mean that there have been some other bootloader changes.
There have been some reports that some on the latest N910TUVS2EPG2 have had trouble flashing TWRP.
Disclaimer: This info is not to be taken as golden fact. I'm just providing it so people can look out and be aware this has been the case in the past.
Since a lot of this information has not been confirmed and will not be confirmed by Samsung we can only go by past situations.
This has been indeed the case on both the Note 4 and the Galaxy Tab S2
To everyone that has indeed updated to this new Firmware version (N910TUVS2EPG2) please post any experiences from it.
Any problems? Any confirmed known changes. Anything.
Thanks!
I updated, and I was able to install twrp, root, and xposed. However, I have heard reports that twrp doesn't work for some people.
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
ayeitschris said:
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Chocu1a said:
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
Click to expand...
Click to collapse
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
DeeXii said:
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
Click to expand...
Click to collapse
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
wilsonmd said:
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
Click to expand...
Click to collapse
Any update to this?
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
Odined stock EPG2 tar, SuperSu systemmode, Xposed alt 86 wanam, TWRP 3.0.2-0, no issues. Great battery, runs smoother, no hiccups. :good:
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
via Odin and i could not let me try flashing the LP bootloader and flash any room ......
How Downgrade your T-Mobile Note 4 (N910t) from MM (any version) to DOK2 Lollipop!
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
IM NOT RESPONSABLE IF A HEART ATTACK OCCUR OR YOUR PHONE BLOW UP WITH ALL THE ROOF :silly:
IF YOU HAVE YOUR PHONE IN MM PG2 STOCK rooted with super SU systemless and last TWRP instaled (like me) YOU CAN DOWNGRADE TO D0K2 LOLLIPOP :
******REMEMBER Disable Reactivation lock (see picture below) and activate USB debuggin, Before DO this procedure!!*******
1-Download the DOK2 BOOTLOADER HERE https://www.androidfilehost.com/?fid=24269982087008410 and the D0K2 modem here: https://www.androidfilehost.com/?fid=24269982087008409 ( i did use 3.0.9 Odin) >>>>>>>>>thanks to @xoxo_xdagirl91 for post the links!
2- Download The 5.1.1 rom here: http://forum.xda-developers.com/note-4-tmobile/development/rom-maximum-ovrdrive-v15-1-1-t3196653 its an awsome rom by @OvrDriVE and so Thanks for that!
3-Put the ovrDrive 5.1.1 rom into the external sd card together with the upgrade. (because need erase all in the internal memory, remember, make a back up of your data in the phone or in the internal memory if you want).
4-now GO to your TWRP and wipe cache-dalvik-system-data-INTERNALmemory x3 ..........DONT TOUCH YOUR EXTERNAL SD, REMEMBER THE OVRDRIVE 5.1.1 ROM IS THERE!
******REMEMBER WHEN YOU ERASE YOUR INTERNAL MEMORY JUST REBOOT AGAIN IN RECOVERY, each time you erase yor internal memory, when reboot in TWRP you see the warning and said that you need to click in "never show this screen during boot again" just click there and swipe to allow Modifications or the stock recovery will rewrite again. TURN OF YOUR PHONE!
5-GO TO DOWNLOAD MODE TO USE Odin and flash the 5.1.1 bootloader FIRST, WHEN FINISH, Flash the modem ..... REMEMBER: put the bootloader in the BL section FIRST AND FLASH & FOLLOWING THE modem in the CP section of odin
6- When finish the step 5, go to your recovery TWRP>install>go to ext sd>flash the ROM first, when finish, wipe dalvik, cache and reboot again in TWRP
7- Just flash the othe part of the rom........the upgrade zip file, when finish just reboot the system aaaaaaaand
WALAAAAAHHHHHH!!!!!!
I DID IT EXACTLY AS DIRECTED AND I HAVE A CLEAN OVRdrive
rooted rom in 5.1.1. Now you can flash via ODIN the original firmware on 5.1.1:good::good:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
mykos said:
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
Click to expand...
Click to collapse
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
kiikez said:
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
Click to expand...
Click to collapse
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Conflicting reports on here. I haven't tried this myself yet but THIS post states a successful downgrade. YMMV.
mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
how did you flashed the super su systemless?
Cannot root or odin twrp after latest (pg2) update. Odin to pe2 and everything is back to normal.
xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
krishelnino said:
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
Click to expand...
Click to collapse
Sure bud.
1) Download the M6 ROM from Dev-Host or from MediaFire.
Put this file in your external SD card.
2) Download the BeastMode kernel.
Put this file in your external SD card.
3) Download the Data Fix - MM_DataFixs7rebootmenu.zip.
Put this file in your external SD card.
4) Boot into recovery. Make a backup of your current ROM just in case. :fingers-crossed:
5) Go into Advanced Wipe (if you're using TWRP) and wipe dalvik, system, data, cache, internal storage (or whichever options are available in the recovery you are using).
6) Flash M6 Rom from Step 1. Do not restart.
7) Flash kernel from Step 2. Do not restart.
8) Flash data fix from Step 3.
9) Now wipe cache and dalvik cahe. Restart.
Once you restart, it will look like your phone crashed or is stuck in a bootloop, it's not. Let it sit there for about 10-15 minutes and it will boot into the setup screen. Good luck. :good:
Hello all,
Been a LONG while since I've actively played around with rooting and unlocking an android device. I finally "upgraded" from my very aged Galaxy S4 to the Moto E4 XT1768. I have successfully unlocked the bootloader, got TWRP installed, rooted with Magisk, and gotten Xposed installed with my favorite modules.
This morning, I got a prompt that a new security update is available, and like a noob, I tried to take the update. This resulted in me getting stuck in a loop where the phone only wanted to boot into TWRP. I got that fixed thanks to XDA, got the pending and failing update completely cleared and am booted back into the device normally, and have frozen the moto update service.... but now...
Is there a way without completely flashing back to stock rom? I know how to take titanium or nand/twrp backups, but I feel like this would still be hours of work to go back to stock, flash, re-root restore all apps blah blah. what are the chances of there being a dirty-flashable zip put out at this point?
The way I normally do these type of upgrades is to download the firmware (from here), use fastboot commands to wipe (erase) and flash the needed partitions (everything but data and recovery), boot to TWRP - flash the no-verity-opt-encrypt.zip & root, and then reboot to system - done. It's easy enough for me, but I know some prefer to being able to use a flashable zip in TWRP.
Also, I have to ask - did you get your e4 cheap? It's was replaced by the e5, some other phones seem to be getting replaced like the G6 series (it's gone on clearance at some places), so they can be had cheap.
bast525 said:
Hello all,
Been a LONG while since I've actively played around with rooting and unlocking an android device. I finally "upgraded" from my very aged Galaxy S4 to the Moto E4 XT1768. I have successfully unlocked the bootloader, got TWRP installed, rooted with Magisk, and gotten Xposed installed with my favorite modules.
This morning, I got a prompt that a new security update is available, and like a noob, I tried to take the update. This resulted in me getting stuck in a loop where the phone only wanted to boot into TWRP. I got that fixed thanks to XDA, got the pending and failing update completely cleared and am booted back into the device normally, and have frozen the moto update service.... but now...
Is there a way without completely flashing back to stock rom? I know how to take titanium or nand/twrp backups, but I feel like this would still be hours of work to go back to stock, flash, re-root restore all apps blah blah. what are the chances of there being a dirty-flashable zip put out at this point?
Click to expand...
Click to collapse
Flashing back to stock and taking the updates is really the best way. Unless you can find a complete firmware package of the new update which of course takes back to stock as well. Really the only way to do it. @MotoJunkie01 makes some TWRP flashable stock roms. And he also creates the partition updater which updates your oem partition and other important things that can't be done in the Twrp flashable stock ROM.
madbat99 said:
Flashing back to stock and taking me updates is really the best way. Unless you can find a complete firmware package of the new update which of course takes back to stock as well. Really the only way to do it. @MotoJunkie01 makes some TWRP flashable stock roms. And he also creates the partition updater which updates your oem partition and other important things that can't be done in the Twrp flashable stock ROM.
Click to expand...
Click to collapse
Speaking of that, @ALI12 just posted a stock firmware package for the NCQS26.69-64-10 build. He gave me approval to use it to update my firmware thread to the latest build, so I'll be updating that OP shortly.
MotoJunkie01 said:
Speaking of that, @ALI12 just posted a stock firmware package for the NCQS26.69-64-10 build. He gave me approval to use it to update my firmware thread to the latest build, so I'll be updating that OP shortly.
Click to expand...
Click to collapse
This will be for the XT1766, correct? Or will same build work for XT1768 (me thinks not)?
So what would the easiest/quickest way be to get updated with all of my apps and data intact? Twrp backup of data partition? Or would there be any way to do this without wiping data at all?
bast525 said:
So what would the easiest/quickest way be to get updated with all of my apps and data intact? Twrp backup of data partition? Or would there be any way to do this without wiping data at all?
Click to expand...
Click to collapse
If you're going to slash a firmware package you'll want to wipe everything. Especially data. Make a backup of your data first of course. After you flash TWR P you can try restoring your data and see if everything comes back. but everything in your downloads folder and all of that will be gone once you format data to remove encryption again.