Database Users

Nexus 7 Root Problem

Im having a bit of a funny one with the Nex, a few days ago I unlocked bootloader, rooted and left it, but as we all know the temptation to try a custom ROM niggles away at the back of your mind and eventually I gave in and installed smoothRom 4.3.
However apps cannot gain root access anymore, the SuperSu popup doesnt, well popup any more...
I have booted into recovery mode and the bootloader is still unlocked,
any advice anyone?

Have you tried removing SuperSu, Wipe Cache/Dalvik
Reboot
Find the LATEST SuperSU
Reboot Recovery
Flash
Reboot.
Try that let me know how you go
---------- Post added at 01:50 PM ---------- Previous post was at 01:49 PM ----------
http://forum.xda-developers.com/showthread.php?t=1538053
^^
Newest SU

Wilks3y said:
Have you tried removing SuperSu,
Try that let me know how you go
Click to expand...
Click to collapse
Assuming you remove it the normal way you would remove any other app? If so, when I hold to drag to uninstall it just shows app info, could this be because SuperSU is built into the ROM itself?

Yeah my bad.
Reboot Recovery
Un-install, Wipe Cache/Dalvik
Reboot (Into actual System)
Reboot (Recovery)
Download new SuperSU (From link I've provided)
Flash it in recovery
Wipe Cache/Dalvik
Reboot
Test
Enjoy

Wilks3y said:
Un-install,
Click to expand...
Click to collapse
What exactly am I uninstalling at this stage?

Super SU?

Right, I think I've worked out where and when my device is unrooting itself.
> I went back to stock unrooted with a locked bootloader, factory settings on everything.
> Then unlocked, and rooted, checked and confirmed to be rooted with rootchecker basic application.
> Then installed Smoothrom 4.3 again, did the whole cache wipe etc, booted first time, no problems.
> Checked rootchecker basic again, AT THIS STAGE STILL ROOTED.
> Rebooted nexus, checked again, and it lost its root.
Ideas are very welcome, im pulling my hair out

I had the same problem today when i install smoothrom. What i discover is that when i go back to cwm, and try to reflash, i cannot even find my sdcard. When i choose "choose zip from sdcard", i can't see my sdcard. After some fumbling, i realised it's renamed as 0. Dunno why this happened, but anyway, i went in there, found the zip file, reflash, then everything is ok. Maybe you can try check. Hope this helps.
Sent from my Nexus 7 using Tapatalk 2
---------- Post added at 02:12 AM ---------- Previous post was at 01:32 AM ----------
Just found this solution.... under settings of super su, uncheck "respect cm root setting". So far it works for me
Sent from my Nexus 7 using Tapatalk 2

I'll give it a go, thanks for the info
Sent from my Nexus 7 using XDA Premium HD app

Same issue as above - Fixed
Neurosis said:
[/COLOR]Just found this solution.... under settings of super su, uncheck "respect cm root setting". So far it works for me
Click to expand...
Click to collapse
This worked for me thanks! :good:
I was having the same issue after flashing SmoothRom 4.3 with successful root. I didn't even realise I lost root privileges until I opened Titanium backup recently. All of the Following steps may not be necessary and are only precautionary as I was also updating to SmoothRom 4.4.
Anyway;
Remove SuperSU updates and clear the data for superSu (As mentioned previously, SuperSu is built in to SmoothRom and Broken Root so can't Uninstall with TiBackup)
Reboot Into Recovery
Wipe Cache/Dalvik
Flashed SmoothRom zip from sdcard
Flash SuperSu latest zip from sd card
Reboot (with patience...)
*Uncheck Respect CM Root Setting in SuperSu
Enjoy!

Can't get passed boot logo..

This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.

Try flashing a different compatible kernel.

ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.

Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app

Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr

ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide

Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/

Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app

I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!

Glad it's working out for you.

If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?

Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.

Guys I need you (flashing sac)

Okay Idk what's going on exactly but I've tried downloading sacs custom 7.2 several times md5s all check out and when I go to flash it in twrp 2.6.3 it fails same with twrp 2.5.2.zip they both keep failing. However I was recently able to flash miuiv5 after a download so the recovery is still working (also it restores backups fine)... So. I'm wondering what's going on here they aren't bad files and it just won't flash! Does this rom have that aroma installer? Am I missing something that allows that?
Currently running trifforce 3.1 with agat kernel and twrp 2.63
Sent from my SPH-L720 using XDA Premium 4 mobile app

coke32 said:
Okay Idk what's going on exactly but I've tried downloading sacs custom 7.2 several times md5s all check out and when I go to flash it in twrp 2.6.3 it fails same with twrp 2.5.2.zip they both keep failing. However I was recently able to flash miuiv5 after a download so the recovery is still working (also it restores backups fine)... So. I'm wondering what's going on here they aren't bad files and it just won't flash! Does this rom have that aroma installer? Am I missing something that allows that?
Currently running trifforce 3.1 with agat kernel and twrp 2.63
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It could be a product assert. If the TWRP is not made for t0ltespr (Sprint Note II) or ROM isn't made for that the two could be trying to verify the wrong model against each other and failing. You can remove this from the zip by looking for the assert in update-script.
Another option if you're open to it is to try my unofficial CWM and see if that avoids your issue.
Good luck!

rom help
In order for it to work, you need to flash sach's custom rom version 7.0. Let it do a full install and setup, then boot back into recovery. Then flash the 7.1 or 7.2 update. Hope this helps.
---------- Post added at 09:50 AM ---------- Previous post was at 09:45 AM ----------
Do Not, I repeat DO NOT do a system wipe in TWRP after installing 7.0 or 7.1. Let the aroma installer do the wipe. I learned the hard way, I wiped it myself and went to update to 7.2 and got nothing but failure notices. Once I re-flashed 7.1 and let the aroma installer do the wipe, it installed with no problem

ive always done a system wipe with no problems. be sure you are downloading the full rom and not the update. and make sure your downloading from a pc over a good wifi conection, then i make sure the file size is about the same size before transferring and flashing. hope this helps

coke32 said:
Okay Idk what's going on exactly but I've tried downloading sacs custom 7.2 several times md5s all check out and when I go to flash it in twrp 2.6.3 it fails same with twrp 2.5.2.zip they both keep failing. However I was recently able to flash miuiv5 after a download so the recovery is still working (also it restores backups fine)... So. I'm wondering what's going on here they aren't bad files and it just won't flash! Does this rom have that aroma installer? Am I missing something that allows that?
Currently running trifforce 3.1 with agat kernel and twrp 2.63
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After wiping system,caches,data in Twrp advanced wiped are you getting the fail? if so just reboot recovery and try to install again without wiping. I have had the flash fail for me too and a recovery reboot solved the issue for me. Also in aroma don't factory reset wipe just wipe cache and dalvik. Also I am on TWRP 2.6.3.1
Sent from my SPH-L720 using Tapatalk 2

[Q] Need Help With Bootfreeze/Bootloop

I recently installed a mod to add functionality to the restart menu from the phone's power down menu. It was supposed to add four additional functions involved in rebooting to recovery mode, download mode, etc. After copying the zip file for this mod to my sdcard via USB storage on my computer and installing it via Clockworkmod recovery, the phone will not go past the "Samsung Galaxy S4" logo on reboot. I have tried multiple things:
1. Removing the battery and rebooting
2. Reflashing stock rom via ODIN (fails repeatedly). I have used the stock roms on this website and a couple others. They all appear relatively the same and fail in every version of ODIN
3. Reflashing Root and CWM
4. Flashing a different ROM from the developers here (particularly the MK2 Stock Modem ROM)
It was working fine on root before adding the 4-in-1 restart menu mod. I was able to somehow remove CWM and attempt to factory reset via the stock recovery menu to no avail. I wiped system, data, cache, and the davig cache or whatever it's called multiple times. I obviously can't flash anything else with CWM since I can't get my phone to finish booting and thus can't connect it to my PC to access files or storage. This is further compounded by the fact that the "Mount USB Storage" function in CWM does not mount it to the PC. The PC is running Windows 7.
Obviously, I'm at my wits' end and would love some help on this. Can't really afford a brand new phone w/o upgrade discount at the moment.
Any and all help would be appreciated! Thank you!

Sounds like you flashed the wrong file. Maybe the mod wasn't meant for Mk2 or NAE. Which ever you are on. And Odin seems to be failing because you are using an outdated tar. Example if you were on MK2 you must be trying to Odin mja or mf9. Which is impossible. You have to dowblaod The latest one that you were on.
Sent from my SPH-L720 using Tapatalk
---------- Post added at 10:45 AM ---------- Previous post was at 10:41 AM ----------
And when you tried to install the other ROM were you factory resetting and deleting data?
Sent from my SPH-L720 using Tapatalk

daniel4653 said:
Sounds like you flashed the wrong file. Maybe the mod wasn't meant for Mk2 or NAE. Which ever you are on. And Odin seems to be failing because you are using an outdated tar. Example if you were on MK2 you must be trying to Odin mja or mf9. Which is impossible. You have to dowblaod The latest one that you were on.
Sent from my SPH-L720 using Tapatalk
---------- Post added at 10:45 AM ---------- Previous post was at 10:41 AM ----------
And when you tried to install the other ROM were you factory resetting and deleting data?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I'll be honest, I don't really know how to tell if the TARs are outdated or not. Earlier in the evening, I managed to flash a factory ROM with Odin 3.07 in an effort to actually factory reset the phone due to 4.4.2 killing wifi functionality. The factory reset went well and I rerooted with Odin just fine afterwards. I used the same stock ROM that I had flashed earlier in my troubleshooting efforts with the bootloop.
And yes, kind of. When I installed the custom ROM, I did the clear data, clear cache drill beforehand to get it ready. It was my mistake obviously to not make a backup of my current one. Big noob fail there. When I went to once again flash the stock ROM, I did the same with the clear data/clear cache drill.

[Q] SGH-I337m soft bricked with faulty usb

A few days ago my USB port on my Telus SGH-I337m gave out, leaving me with no data connectivity and extremely limited charging capabilities.
I rooted the phone using ODIN and TWRP when I originally got it last summer, but i forgot all about that and brought it over to best buy for an exchange. We did a factory reset before the guy noticed it was rooted and told me to un root and come back. However, after the factory reset, I'm now stuck on the samsung galaxy s4 splash logo, but I do still have access to recovery booting. I've tried downloading stock and custom roms and flashing those to no avail. I switched my recovery manager from TWRP 2.5.0.0 to CWM 6.0.4.4, but still nothing. ODIN flashing is impossible because the USB port isn't working. Any suggestions?

Are you using super SU? There's an unroot option in it
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
jd1639 said:
Are you using super SU? There's an unroot option in it
Can you flash a rom in recovery using adb side load or pushing a rom to it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Free mobile app

I don't have access to super SU at the moment. The phone hangs during boot at the Samsung galaxy s4 splash logo

SgtBuzzkilll said:
I don't have access to super SU at the moment. The phone hangs during boot at the Samsung galaxy s4 splash logo
Click to expand...
Click to collapse
You said you flashed cwm over twrp, if you did so you must be able to flash a rom too.
The bright side, if it's not booting you could take it to a best buy and they couldn't tell it's rooted
Edit, when you boot into recovery is it the stock recovery now, or cwm?
Sent from my Nexus 5 using XDA Free mobile app

Any custom roms I've tried to flash have still left me stuck at the splash logo. Any chance you could point me to a stock ROM download? None of the stock roms i've found will install. And since it does still boot into recovery mode the guys at bestbuy will still know i have it rooted though right? worst case i might just drain the battery and bring it in since it takes about 20 mins to charge 1%.
edit: it recovery boots into CWM 6.0.4.4 only, hangs on normal startup with any rom

SgtBuzzkilll said:
Any custom roms I've tried to flash have still left me stuck at the splash logo. Any chance you could point me to a stock ROM download? None of the stock roms i've found will install. And since it does still boot into recovery mode the guys at bestbuy will still know i have it rooted though right? worst case i might just drain the battery and bring it in since it takes about 20 mins to charge 1%.
Click to expand...
Click to collapse
If it boots into a custom recovery, twrp or cwm, yes they're going to know you modified the device. But you're not going to be able to get rid of that without Odin.
Sent from my Nexus 5 using XDA Free mobile app

If I'm able to fix the boot error, would I be able to use mobile odin or super SU to unroot it?
Either way any other suggestions for getting past the splash screen?
What I've tried exactly is:
-boot into CWM recovery
-wipe data/factory reset
-wipe cache partition
-wipe dalvik cache
-install ROM from zip
-reboot
custom ROMS install ok but give me the boot error
stock roms don't install at all
And thanks for the help i do appreciate it

SgtBuzzkilll said:
If I'm able to fix the boot error, would I be able to use mobile odin or super SU to unroot it?
Either way any other suggestions for getting past the splash screen?
What I've tried exactly is:
-boot into CWM recovery
-wipe data/factory reset
-wipe cache partition
-wipe dalvik cache
-install ROM from zip
-reboot
custom ROMS install ok but give me the boot error
stock roms don't install at all
And thanks for the help i do appreciate it
Click to expand...
Click to collapse
I'm not sure what to tell you. First, you're flashing the custom roms correctly and I'm not sure why they're not booting. I don't know what stock rom you're trying to flash.
Having the custom recovery is going to kill you at best buy. They'll try to boot into recovery to do a factory reset and they'll see you modified the device.
I don't know if mobile Odin works on the s4, I don't think so, but you'd have to boot into something first. And that's a problem right now.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
@SgtBuzzkill I'm not at a pc tonight but tomorrow I'll make you a stock recovery zip that you can flash in cwm. That will take care of the custom recovery issue
Sent from my Nexus 5 using XDA Free mobile app

I managed to get past the splash logo. Turn out i needed to format all the partitions as well as clear them before installing a rom.
The stock roms i was (mistakenly) trying were the odin tar.md5 files. But now I've got mobile odin running and I found a couple videos with mobile odin and the gs4 so im going to give it a shot. The procedure recommends >50% battery though so I'm going to have to let it charge overnight.
We'll see if it works in the morning

Reflash lastest 4.4.2 (Colombia) Firmware from Sammobile, Tick "NAND Erase All", "Re-partition" & "Phone EFS Clear", also put the unziped attached file on the PIT section.
This will completely wipe your NAND, this means a complete Full wipe of the whole phone, I also have a i337M from Telus & deleted all the remains of previus modifications that normal recoveries can't wipe. thus reformatting Boot, Cache, System, EFS & all other partitions to their correct state.
Make sure your Odin window looks as the attached image.
It will stuck at samsung logo after flashing, boot to recovery & perform a factory reset, and you are good to go.
King regards.

Starnel said:
Reflash lastest 4.4.2 (Colombia) Firmware from Sammobile, Tick "NAND Erase All", "Re-partition" & "Phone EFS Clear", also put the unziped attached file on the PIT section.
This will completely wipe your NAND, this means a complete Full wipe of the whole phone, I also have a i337M from Telus & deleted all the remains of previus modifications that normal recoveries can't wipe. thus reformatting Boot, Cache, System, EFS & all other partitions to their correct state.
Make sure your Odin window looks as the attached image.
Click to expand...
Click to collapse
Read the op. His usb port doesn't work. No Odin
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Read the op. His usb port doesn't work. No Odin
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Boot partition most likely to be damaged, Only Odin can repair it afaik.

Starnel said:
Boot partition most likely to be damaged, Only Odin can repair it afaik.
Click to expand...
Click to collapse
It's a broken usb port. It's hardware, not software.
Sent from my Nexus 5 using XDA Free mobile app