Develop Bugs

TWRP 4.4 build on 5.1.1 ROM?

UPDATE: So, I couldn't really wait, went ahead and flashed TWRP. It installed just fine, as long as you get into recovery immediately, TWRP sticks. I flashed SuperSU and rebooted and got into a boot loop, so had to flash the stock firmware again and everything is fine again. No idea why the bootloop, so if some expert knows, please share
-------------------------------------------------------------
So, T-Mobile/Samsung FINALLY delivered 5.1.1 on the P607T and it looks quite awesome so far. My device was rooted and had twrp, so I had to flash with odin and now have neither twrp nor root. While I know that its only a matter of time before the community updates the tools to make it easy for us to root, I wonder if somebody could tell me if its okay to flash the existing twrp_2.8.7.0_4.4 build on this new ROM?
I vaguely recall reading somewhere that with Lollipop, Android moved to a new FS, but suspect this only applies to the system and boot partitions? That flashing recovery should be fine, and worst case, twrp will not stick? But, just in case, it would be great to know if this is true from someone with more experience ... If yes, then I can try to flash twrp and see if SuperSU still works through ODIN.
Thanks!
Karthik

I tried root/TWRP using the P605 NEE thread method and I get the bootloop. It takes the modified ROM but not the SuperSU. Anyone else get root on P607T 5.1.1 yet?

From what I gather so far, 5.1.1 is rootable, but a bit more complicated than other versions. There are instructions one can follow to 'manually' root (meaning no simple odin flash), but these have not been tested on the Note 10.1 firmware yet and so no guarantees. I am told its just a matter of somebody who knows picking it up and creating a flashable solution, but the device is old and the world has moved on to Android 6.0, so this is not very high priority and we may have to wait a bit more.
The manual instructions, I understand them enough to want to try, BUT am not a developer and am worried about bricking my device! If anybody is brave enough to try,
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
http://forum.xda-developers.com/showpost.php?p=63194536&postcount=2076
should get you started.

Bought Zenfone 2 Z00AD from AmazonUK... but OTA doesn't work

Right... so, I think I traced down why OTA doesn't work.
Namely, whenever I click on system update to search for update, it searches, but nothing happens.
Online I found that this is likely because a WW custom ROM was flashed... and so OTA doesn't work.
My phone is brand new (got it today actually), but 'stuck' on Android 5.0 (ugh).
So... I would like to ask for the recommended course of action so I can get either latest OTA, or just install a stable and up to date clean Android ROM (without all the Zen bloatware) that works.
Also, I'm relatively new with flashing this phone and there's tons of info on rooting, different CWM and TWRP's, etc.
Problem is, which ones to use?
How to determine if you're using the right one and avoid bricking the phone in the process?
My phone arrived with SuperSU... which would indicate it's been rooted (and I was able to install AdAway).
So bearing that in mind... what would you recommend?

Your phone should not be rooted when bought in a store. So it seems to be used before, and not correctly refurbished.
Anders
As there is no possibility to get evidence that you did not do that yourself, you can only hope to get a replacement from the vendor,or any warranty.
On the other side: the device is already rooted, so you can flash a 6.01 rom yourself.
Depending on the way the phone was rooted in the first place, OTA will not always work.
I did see an original rom surface recently. With that you can go original, Unrooted and locked, so the vendor will not be able to void your warranty claims.
Verstuurd vanaf mijn ASUS_Z00A met Tapatalk

Sorry for the late reply.
Was busy.
The phone was bought off Amazon UK, and no modifications to the device were done by me apart from installing my apps.
Trouble is, I don't know how to flash a new ROM onto this thing.
The forums are overflowing with information which is all over the place and it is extremely confusing.
Yes, I tried the search function and found some info, but it is all over the place.
I have to be able to figure out the original firmware apparently if I want to flash the CWM or TWRP... and in some cases, flashing TWRP can break the device it would seem (what's up with that?), and I cannot figure out the original firmware because the mobile was not delivered with one (a custom WW ROM was apparently flashed on top of I don't know which version), and I really do not know where to look for this.
So, I'm very confused.
There's too many threads to sift through and each seems to be giving its own unique information and a list of no no's which appear to contradict each other.
I could use some help in sorting through this 'mess' (well, 'mess' for me) so I could try at least flashing the original ROM and get OTA (for which I require concise instructions).
Also, something else seems to be happening... Asus Zentalk forums appear to refuse to load on my laptop for whatever reason.

Settings>About - will show you what rom you have.
I would recommend unlocking bootloader 1st as this seems to have helped me. If you have any recovery but stock or have a white splashscreen then this has already happened... I used the unofficial unlock tool to do this and thus my imei numbers stays off the "no warranty" list..
If you go to the pre-rooted rom thread you can download the newer stock roms. These also have the recovery, boot and droidboot.img files included with the .rar file of a system.img (unrar it of course)...
I believe it may also contain the flashtools, if not look at the CN to WW thread...
Using fastboot you can flash these onto your phone using commands -
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Make sure, if do this the commands are correct. Copy and paste can be your enemy because if you use the same command and just overwrite your boot/droidboot or recovery every time you flash, it may result in a brick...
Good luck and happy flashing...
I seem to get OTA's pushed now..

Tnx.
Now that I look back, it doesn't seem too complicated.
My bootloader seems to already be unlocked though.
One other thing... about flashing that system.img
I think I stumbled upon similar instructions before, however, I couldn't find system.img file (everything else was accounted for).
Also, does the the procedure for flashing new ROM's or possibly just OTA's require repetition of ALL those commands, or just some?
Oh and I was able to access the stock recovery (which the seller said he used to flash the custom WW rom). Could I use it to update OTA's manually? And would I need to first unroot the mobile?

Downgrade to MM then if desired, restore to Nougat

Good day guys!
I have an app that I need to use for my phone but it seems in android N that it consumes more battery, maybe because it is not optimized for it yet. Regardless, I would like to try MM again and see if it does indeed drain less, if not, I would like to go back to android N. Can I flash MM thru bootloader as described here (Restore for OTA part) > https://forum.xda-developers.com/moto-z-play/how-to/howto-moto-z-play-unlock-root-t3508547, obviously not flashing over bootloader.img or the modem. It is then my understanding I cannot take the OTA again to get back to android N because it will brick my device. With that, how would I get back to android N if and when I want? Could I just restore my backup that is made before my downgrade? Or do I have to flash custom stock ROMs provided here? Can I even do that?
I am rooted in android N, I am actually not sure how to unroot it to get another OTA. With the systemless root, I believe I just need to reflash boot.img, however, I didn't make a backup of that, and I am not sure where to get it. Maybe I get it thru the android N OTA? I found a file called boot.img.p. If I removed the p is this what I need?
Thanks, guys!
Cheers
Joshua

Just bumping this... No one has any thoughts or ideas here?

TWRP+SuperSU, TWRP+Magisk, or Custom ROM?

Last year, I bought my first ever Android - a Galaxy S7 Snapdragon. Unfortunately, I soon learned that without root & Titanium, Android provides no way to do a proper/complete backup (i.e. SmartSync doesn't backup any app data, & Helium backs up some but misses many - WhatsApp, LINE, Viber, etc). Thus I returned the S7, took a brief hiatus, & am now eagerly awaiting the arrival of a brand new Exynos S9
I wanted to ask for any quick advice as to the "suggested" approach for rooting, so I can hit the ground running as soon as this thing arrives. As I understand it, there are 3 main approaches:
1) Install TWRP, stick with the stock Samsung ROM & flash SuperSU
2) Install TWRP, stick with the stock Samsung ROM & flash Magisk
3) Install TWRP, flash a custom ROM that's already rooted
Between 1 & 2, my understanding is that Magisk is preferable to SuperSU as it essentially accomplishes the same thing but without necessarily blocking OTA updates or some financial applications from working. True? So is there even any reason to consider #1? If not, any insight as to choosing between #2 vs (any specific custom ROMs)?
My long-term priorities are simply for the phone to run as well as possible, with as little maintenance as possible (i.e. as far as ease of getting security updates goes). I'm not really into lots of customization, experimenting, etc - I'd prefer to just get something up & running, stable, & stick with it. I will be using T-Mobile though, so I guess in either case I'll need to install this to get WiFi calling & VoLTE working. Also, I want to make sure that whichever root solution I choose, it can coexist with Secure Startup (the S7 Snapdragon's root couldn't, which was a dealbreaker for me).
Any insight would be greatly appreciated. The phone arrives Tuesday, I can't wait to get started!

As soon as you flash twrp your not going to get OTA updates nevermind root.
sent from my Pixel 2 XL or Note FE

Unfortunately i made a silly mistake, i wiped the EFS partition of my G960FD once rooting the device while not having any backup for it
i tried flashing official rom, combined roms, cutoms roms; but always, i have the same problem "unknown IMEI and Baseband"
even, i tried to use ODIN Nand Erase All and installing new fresh official rom and also, have the same problem
is there any recommendations, please?

hanymedic said:
Unfortunately i made a silly mistake, i wiped the EFS partition of my G960FD once rooting the device while not having any backup for it
i tried flashing official rom, combined roms, cutoms roms; but always, i have the same problem "unknown IMEI and Baseband"
even, i tried to use ODIN Nand Erase All and installing new fresh official rom and also, have the same problem
is there any recommendations, please?
Click to expand...
Click to collapse
Samsung repair centre

*Detection* said:
Samsung repair centre
Click to expand...
Click to collapse
They asked me to pay 400$ for replacing the mother board
that's why i asked for having any solution

hanymedic said:
They asked me to pay 400$ for replacing the mother board
that's why i asked for having any solution
Click to expand...
Click to collapse
when you say combined roms do you mean the factory binary firmwares? because if flashing the combination firmware/factory binary followed by the usual rigmarole factory reset, nd reflash official fw doesnt work you could try rebuilding the partition using adb shell (root access needed for this though)
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965
this link isnt for the s9 smg960f but it did work for me when trying to solve the same issue on the sm-g950f,
anyway hope this helps in some way

Backing up everything or restoring partitions to original state

Hi I've always tinkered with my phones but with the One Plus 7t Pro nothing ever gave me a reason to root until now (quick step) but so far there has always been a reliable method to go back to full stock whether it's fastboot on nexus device with the official google images or Odin on Samsung devices. So I've been documenting myself and trying to understand the different partitions. My understanding is that one plus on it's website only offers system images so if I ever came to loose my other partitions what would I be able to do ? I've seen a tutorial with EDL mode but where does the firmware come from ? MSM tools only restore boot.img and system.img right ?
Also how could I go about backing up my persist partition.
So basically before I root I wanna be sure that I can go back to partitioning my phone exactly to how it was before with official firmware or if there is no official one, backing up mine before rooting.
Any clarification would be appreciated !
Thanks,