Database Develop

[Q] Odd issue with root disappearing?

Hi,
I've just upgraded the OS of my HTC One to 4.4 with Sense 5.5 and rooted the handset.
I took the majority of information and downloads from here:
http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/
while the rooting stuff I grabbed from here:
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
So ok this is my 3rd OS upgrade with root so in a basic sense I did this:
- Updated TWRP to version 2.7.x
- Used TWRP recovery WIPE option to format / (root)
- Installed the 4.4 stock ROM from above link
- TWRP then asked me if I would like to root the device and so I said ok to that
- Booting into the OS everything was fine and I had the SU-Root icon in the Apps menu
I'm not sure what happened if the battery got drained or so but in anycase after a restart the handset was no longer rooted??
As I have the 2.65 SU-ROOT Zip file on my storage partition I went back to TWRP and Install then clicked on the Zip file and re-rooted the device; then wiped the cache and booted back into the OS.
For some reason now the phone isn't able to be rooted at all? I am pretty sure I had similar behavior with Android 4.3, though the initial stock build was absolutely fine.... I think I managed to get from 4.1 to 4.2 successfully.
Will I need to format the handset again then re-install the ROM and re-root or is something else going on which I'm unaware of??
I've also noticed that the device becomes un-rooted each time the battery goes low or dies for some reason... a persistent root would be nice as I have many apps needing full root access; not to mention being able to work with the full Android system too.
Would anyone be able to suggest anything? Thanks!

JohnnySSH said:
Hi,
I've just upgraded the OS of my HTC One to 4.4 with Sense 5.5 and rooted the handset.
I took the majority of information and downloads from here:
http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/
while the rooting stuff I grabbed from here:
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
So ok this is my 3rd OS upgrade with root so in a basic sense I did this:
- Updated TWRP to version 2.7.x
- Used TWRP recovery WIPE option to format / (root)
- Installed the 4.4 stock ROM from above link
- TWRP then asked me if I would like to root the device and so I said ok to that
- Booting into the OS everything was fine and I had the SU-Root icon in the Apps menu
I'm not sure what happened if the battery got drained or so but in anycase after a restart the handset was no longer rooted??
As I have the 2.65 SU-ROOT Zip file on my storage partition I went back to TWRP and Install then clicked on the Zip file and re-rooted the device; then wiped the cache and booted back into the OS.
For some reason now the phone isn't able to be rooted at all? I am pretty sure I had similar behavior with Android 4.3, though the initial stock build was absolutely fine.... I think I managed to get from 4.1 to 4.2 successfully.
Will I need to format the handset again then re-install the ROM and re-root or is something else going on which I'm unaware of??
I've also noticed that the device becomes un-rooted each time the battery goes low or dies for some reason... a persistent root would be nice as I have many apps needing full root access; not to mention being able to work with the full Android system too.
Would anyone be able to suggest anything? Thanks!
Click to expand...
Click to collapse
I think there is an update for supersu
please google it
if yes than move it to your phone and flash it in the recovery

Thanks I managed to find version 1.94 which worked fine:
http://download.chainfire.eu/396/

Android 7.0 Call Problem

Hi
I have installed many of the Android 7.0 ROMS for Shamu and all of them have this annoying problem:
When I dial out I cannot hear the ring or the other person.
When I receive a call I don't often hear the other person but they may hear me.
Yes I've installed the N6 boot loader and radio and do not load any other mods, custom kernels.
I just can't figure this out. Any ideas? Is there a Android 7.0 firmware that I need to install to prepare my Shamu for Android 7?
Thanks
Aussie

I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it

Flashing Stock 7.0
aroy97 said:
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Click to expand...
Click to collapse
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie

aussie1234 said:
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
Click to expand...
Click to collapse
Flashing stock does not relock the bootloader.

Didn't work
Ok I flashed stock 7.0 using Wugfresh's tool.
But still when I use the phone I can't hear who is on the other end.
Really odd!
Anyone have any suggestions?
Thanks
Aussie

I'm having the same issue on a stock Nougat phone as well. The problem appeared a few days ago out of the blue. The only band aid fix I've found is the sound about app and force assigned the mic and earpiece functions.
Sadly, this doesn't address the main issue in the first place.

none
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
---------- Post added at 07:53 AM ---------- Previous post was at 07:50 AM ----------
USMC retired said:
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
Click to expand...
Click to collapse
If you need anything else you can PM me

I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.

stevew84 said:
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
Click to expand...
Click to collapse
have you tried reflashing your radio? Maybe try flashing a MM radio as well

Just wanted to chime in, I think this is actually more of a VoLTE/HD issue. It happens to my N6 that's still on MM. Sometimes the dialtone/ring is there, other times it's not. Would love to know of there's a fix!

Found a fix..
Hello all.
I found a fix to Shamu+Nougat ROM problem when I am called I do not hear the other person and vice versa.
To install Factory Nougat from Google: https://developers.google.com/android/nexus/images
FIRST backup your phone (contacts, files, pics, movies etc) as this will totally erase EVERYTHING!
When you are on the Factory Images for Nexus Devices page click "backed up to your Google Account" then go click 'back' on your browser and click on 'Acknowledge' to see the list of Factory Nougat ROMS for Shamu come up on the right.
Download the Android 7.0 Factory ROM for Shamu/Nexus 6.
Do not flash this stock ROM using Wugfresh's tool. Instead follow precisely the 'Flashing Instructions' on the page https://developers.google.com/android/nexus/images. Allow the phone to reboot and fully set up. Restart the phone again.
Then use Wugfresh to Root the phone and also to install custom recovery (I already have unlocked bootloader).
Now, nothing against Wugfresh Tool (I do not know why the flashing method above works better) as Wugfresh has saved my phone many times.. Its just that Googles recommended flashing instructions worked best.
Now I use the phone and not only do I hear the caller and they hear me I have much better reception (Australia). Yes I did previously flash latest radio but the above method seemed to improve my Shamu 100%.
What I have not done yet is flash a custom ROM in case the problem re-appears. But my phone is rooted and unlocked so I can install other mods that work with Nougat.
Hope this works for you.
Cheers
Aussie

Another Fix Part 2
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie

aussie1234 said:
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
Click to expand...
Click to collapse
Has there been a listed fix for people who haven't rooted their nexus?

System Update with Bootloader unlocked via Sunshine

Hello out there I looked for a thread on this subject and I didn't see one so I apologize to the mods if this has been covered.. Anyways today I received a notification for a System update on my Turbo. I haven't tried to install it yet. Right now my bootloader is unlocked via the Sunshine apk I have TWRP installled as my custom recovery and I have root. Basically I'm running stock but rooted. What is the upgrade procedure. I'm pretty sure the update will fail with twrp installed. Is there a set procedure everyone is using... Thanks in advance

tombaldwin6 said:
Hello out there I looked for a thread on this subject and I didn't see one so I apologize to the mods if this has been covered.. Anyways today I received a notification for a System update on my Turbo. I haven't tried to install it yet. Right now my bootloader is unlocked via the Sunshine apk I have TWRP installled as my custom recovery and I have root. Basically I'm running stock but rooted. What is the upgrade procedure. I'm pretty sure the update will fail with twrp installed. Is there a set procedure everyone is using... Thanks in advance
Click to expand...
Click to collapse
Backup apps via titanium backup, and save off the phone. Backup all personal files, pics etc, off the phone. Flash a stock ROM in TWRP, wipe dalvik & cache. Then flash stock '49' recovery using ADB. Power up normally & take update. It should execute flawlessly. You could also flash the stock firmware for marshmallow via RSDlite, but that will wipe your data off the phone. Bootloader will still remain unlocked so you can Flash TWRP back on afterwards. Root can only be restored by flashing a particular beta version in TWRP. Better details and download links in the XDA forum thread for droid turbo.

USE THE TWRP-FLASHABLE VERSION OF UPDATE
tombaldwin6 said:
today I received a notification for a System update on my Turbo. Right now my bootloader is unlocked via the Sunshine apk I have TWRP installed as my custom recovery and I have root. Basically I'm running stock but rooted. What is the upgrade procedure.
I'm pretty sure the update will fail with twrp installed. Is there a set procedure everyone is using... Thanks in advance
Click to expand...
Click to collapse
Congratulations on having an unlocked bootloader! No need to do all that above, unless you really want. There's also a TWRP-flashable version on that update already posted in this forum. Just flash it in TWRP. It's the full update, minus stock recovery so you can keep TWRP and also flash it in TWRP!
@TheSt33v, who wrote the guide in this forum about unlocking the Droid Turbo bootloader is who posted it, so you can trust it.
[ROM] MCG24.251-5 100% Stock
https://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
All updates like that will ALWAYS be posted here in various formats. Never any need to take an OTA. That's one of the great things about XDA.
____________
Also, there's a TWRP-flashable stock-based Verizon Marshmallow ROM by @computerfreek274. It's basically this Verizon Marshmallow update but tweaked, optimized, debloated.
Computerfreek274_MM_1.0.4 Marshmallow 6.0.1 Stock rooted VOLte Debloated
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
1.0.4 Change Log
Native Tether. (Tested and Working)
Audio Boost In call volume. "Fixed in 1.0.4 Lowed down from 94 to 90 Stock is 84 to avoid echo when volume was up to full."
Audio Boost Media Audio.
De-Bloated.
Removed Some Google apps like YouTube ,books,games,videos,Google Photos, Slacker radio, NFL Game,Verizon Cloud, Google pay and and some Verizon apps. Plus the demo stuff and mp4's also removed all amazon junk.
init.d Support.
Tweaks for speed.
Tweaks For battery life
.
Click to expand...
Click to collapse

Root OnePlus 3T running 7.1.1 Android Nougat and Oxygen 4.1.1.

Hello all.,,
I checked and read many thread slowly and steadily ,but couldn't find a good solution to root this phone 3T.
I just bought this Beautiful Device runing so smooth but with Hands tied too hard unable to run many apps and many ads and Bloatwares..
Thought to Root this device ,but all are mostly either Oxygen 3 or Marshmallow or 7.0. Version of ANdroid..and DW Error,is also a major concern to look out..
So Please help me to root this device running O2 4.1.1 (I literally dont want to change the stock,as of now) and Android 7.1.1 ,some simple steps...
Thanks and Regards
Awaiting for replies!!

I'm about to get this phone so I've been doing a lot of research myself. It looks like you can follow the steps in this thread and you can flash supersu through TWRP once you've unlocked the bootloader.

Unlock bootloader.
Flash TWRP.
Flash your preferred root zip in TWRP (SuperSU or Magisk are two good choices, I prefer Magisk).
That's about it...

i too tried the above method,,But I got struck with Logo of TWRP and got enabled only after 6 Hours.. But to my fate,,i'm still running on Stock recovery.. Not on TWRP !!

Use the latest official TWRP (currently 3.1.0-1). Works just fine.

i can relate to your question.
however, i discovered how to root the 3t and flash the usual zips files the finally the freedom rom, on my own.
it was a thrill.
i advise you to just take the blue pill.

I installed Blusparks Version of TWRP ,,but still no use,,SuperSU or Magisk both says My phone is not rooted!!!!

I want to live the Stock ROM and just to root the device,,But the steps are not futile for me!

What I would do if i was you.
Unlock bootloader
Flash TWRP
Flash latest Magisk 13.2 zip

Hey,
Is this method still valid for rooting the 3T?
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/

Yes, that is still valid, more or less. Might be a more current version of blue_spark's TWRP (official TWRP is on 3.1.1.2) although the link only says 3.1.1-x, so I don't know what that means. But probably won't make a huge difference.
Can't see what version Magisk is linked (my office network is blocking the link). If you choose Magisk, flash latest version 13.3, especially if you want to hide root (from Snapchat, banking apps, etc.). Older versions of Magisk will fail to hide, due to recent changes Google made to SafetyNet.

And what if we want to flash this beta to a brand new device?
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_12/
Should we first unlock the device, then install the TWRP recovery, then flash this beta rom and then root?

[ROM] [7.1.1] Google Pixel 2 Experience J320A/J320AZ/J320AG

This is an early release, but just like the other it's fully functional as a daily driver.
Note:
Still no root method for our device on Nougat
Features:
Pixel 2 emoji
Pixel 2 fonts
Pixel 2 wallpapers (live and still)
Pixel 2 sounds and notifications
Google Assistant
Google Lens
Unlimited Google photo storage (Pixel feature)
Round icons (uses apps native icons, not masks)
Daydreams enabled on battery power (screensaver can be used like always on display, until 15% battery)
360° rotation, everywhere
Power menu from sleep
All quick settings enabled (including mobile data toggle)
Hotspot activation bypass
System menu translated into every language
To do:
Lower the 15% screensaver limit
Add Pixel 2 logo and startup animation
Lockscreen background
Lockscreen default widgets (phone & camera)
What else do you want?
Bugs:
Selfie video doesn't record (prolly not fixable until we get an updated app)
Anything else?
Installation:
From 6.0.1:
Flash with Flashfire and do full wipe
From 7.1.1:
*Must use PC*
Method A
1. Unzip ROM.
2. Flash the included eng_root kernel with Odin.
3. Double click the included "Install.bat"
The script will wipe your data for you (and not touch the internal sd)
Method B
Use Odin to downgrade to 6.0.1 then flash zip with flashfire.
Download

I'll add more screenshots tomorrow

As of right now, even with the custom ROM, there is no root, correct?

I installed it, and every time I boot, I get a System UI has stopped error.

@NateDogg1232
Did you wipe?
... Correct no root yet, until we get a permissive kernel

DamienMc said:
@NateDogg1232
Did you wipe?
... Correct no root yet, until we get a permissive kernel
Click to expand...
Click to collapse
Yes, I did wipe.
I even did it again using the default recovery just to make sure.

More screenshots
Please, upload more screenshots, I would like to install this rom but I do not know if I really have any problems when using it, as it is in terms of speed, can it really be used now?

@RaghebAlama
Sorry I am having problems uploading more screenshots (used all my data this month)
I'll be sure to do it this evening when I'm on wifi.
I've been running this for a week now and haven't had any issues yet
But after the above comment you might want to grab full Odin updates as well, just in case you need to recover
@NateDogg1232
What method did you use to install?
What device do you have?
I would recommend going back to stock and giving it another try.
I apologise tho, I tried to get a few testers this time but never find any. It's hard to test every scenario with just one device

I used FlashFire from actually your first GPE ROM.
I have the J320A
I will reset from stock and try again as soon as I can and try again.
Whether it works or not, though. Thank you for your work on this phone

I bet that's it, I'm not sure I tried to install from v1.
Can't think of why it would fail except maybe if goodlock has files on your sd and this systemui is trying to use them... If you want to test that just pull your sd, because wipe already did your internal sd
I'll test it later this evening
[EDIT]
Nah wasn't that, it was a mistake by me. Two actually.
Testing a quick fix now. And I'll upload a full fixed Rom while I sleep
[/EDIT]

DamienMc said:
@RaghebAlama
Sorry I am having problems uploading more screenshots (used all my data this month)
I'll be sure to do it this evening when I'm on wifi.
try to explain in detail the installation process since 7.1.1 the eng_root does not detect it ODIN if it is not in .tar format, after installing the Eng_root, you have to start the normal cell phone and then the second.pass with the Install.bat ?
Click to expand...
Click to collapse

I fixed the systemui error and another popped up, sigh... ill let you know when it's fixed.
The only way to install this currently is from 7.1.1
@RaghebAlama
Eng_root is a tar. Flash it with Odin.
Your phone will stay on the logo the entire time.
Then just run the bat...The script waits for your phone, copies the required files, then it flashes the original kernel back and reboots.
easy peasy
... and it really does work installing this way

Sorry for the delay. Uploaded fixed version, OP updated

Alright, this looks AWESOME. Will try it when I get time. But about the root problem: I don't know if nobody's thought of this, or if I don't know something you do, but to get root for this, couldn't you add Magisk-14.zip (or another root method) to the queue in Flashfire, or include it in the install.bat? Flash the ROM then root, then reboot to system? I've tried to install Magisk before on stock Nougat with its new way of installing, which is flashing a boot.img that Magisk Manager patched, but Odin always failed on Operation: Write. I was going to go back to Marshmallow to try flashing a ROM and Magisk with Flashfire.

Hello. Can I get permission to make a version for j320fn/f/g

DJJosephJumper said:
Alright, this looks AWESOME. Will try it when I get time. But about the root problem: I don't know if nobody's thought of this, or if I don't know something you do, but to get root for this, couldn't you add Magisk-14.zip (or another root method) to the queue in Flashfire, or include it in the install.bat? Flash the ROM then root, then reboot to system? I've tried to install Magisk before on stock Nougat with its new way of installing, which is flashing a boot.img that Magisk Manager patched, but Odin always failed on Operation: Write. I was going to go back to Marshmallow to try flashing a ROM and Magisk with Flashfire.
Click to expand...
Click to collapse
Odin will not install a custom boot image on our device.
There are other ways to install the custom kernel, but our bootloader will not allow it to boot.
I can install SuperSU, but our selinux policy will not let the system load. The way I know it's rooted tho is that I can get a root shell thru adb, but that's useless since the system will not fully load... We need a new permissive boot image (engboot)
borksek said:
Hello. Can I get permission to make a version for j320fn/f/g
Click to expand...
Click to collapse
All yours bud

DamienMc said:
Odin will not install a custom boot image on our device.
There are other ways to install the custom kernel, but our bootloader will not allow it to boot.
I can install SuperSU, but our selinux policy will not let the system load. The way I know it's rooted tho is that I can get a root shell thru adb, but that's useless since the system will not fully load... We need a new permissive boot image (engboot)
Click to expand...
Click to collapse
Got it. Again, I was without the experience. Thanks for clearing it up.

Can i use this rom on my j320f

Does it work on the SM-J320m?

@aR_aNiK & @lithoy
Sorry guys, no.