Notes
I just got a nexus 7 2013 and was using it for 3 weeks (after root + cyanogen 10.2 installation).
I tried to flash a kernel which I thought could solve an issue with cifs support, and after that trouble began:
After reboot, the device is only works in portrait mode - no matter what I did.
I tried to hard reset the device, formatting it completely, and installing the 2013 original rom which I downloaded from here (the wifi version):
htt ps://developers.google.com/android/nexus/images#razorjss15r
The device is starting (still - only portrait) but I got errors for google play and other apps.
At this point I tried to "adb restore" a full backup image which I did before all these troubles began - the image was restored successfully more or less, but I do not have the sdcard mounted (I can see a FILE named /sdcard on the root using root explorer but no folder).
I have no Idea what to do next - I cannot seem to make the device work with the SD mounted and therefore cannot copy files to the device at all (I always get read only filesystem/permission denied messages when I try to adb push). The portrait stays the same - no landscape and because no sd available, I am getting errors for almost every operation I do.
I cannot even make it back to the original factory state (boot works, but I cannot start google play or copy files to the device).
Any help will be appreciated.
-----
Some progress - I've managed to flash the recovery image, cyanogen 10.2 + google apps and after that latest SuperSU.
The device boots ok, but immediately I get the error of google play store - "unfortunetley, google play store has stopped". Trying to run the camera app gives "Unfortunately, Gallery has stopped". Gallery application gives "No external storage available".
I do not know if this is related, but when I am in recovery mode, I am able to use the file browser and see the content of /sdcard (which contains the files I pushed using "adb push" in order to flash the device), but if I boot into android, using adb to /sdcard (as root -> terminal + su) shows an empty folder.
liran corleone said:
Notes
I just got a nexus 7 2013 and was using it for 3 weeks (after root + cyanogen 10.2 installation).
I tried to flash a kernel which I thought could solve an issue with cifs support, and after that trouble began:
After reboot, the device is only works in portrait mode - no matter what I did.
I tried to hard reset the device, formatting it completely, and installing the 2013 original rom which I downloaded from here (the wifi version):
htt ps://developers.google.com/android/nexus/images#razorjss15r
The device is starting (still - only portrait) but I got errors for google play and other apps.
At this point I tried to "adb restore" a full backup image which I did before all these troubles began - the image was restored successfully more or less, but I do not have the sdcard mounted (I can see a FILE named /sdcard on the root using root explorer but no folder).
I have no Idea what to do next - I cannot seem to make the device work with the SD mounted and therefore cannot copy files to the device at all (I always get read only filesystem/permission denied messages when I try to adb push). The portrait stays the same - no landscape and because no sd available, I am getting errors for almost every operation I do.
I cannot even make it back to the original factory state (boot works, but I cannot start google play or copy files to the device).
Any help will be appreciated.
-----
Some progress - I've managed to flash the recovery image, cyanogen 10.2 + google apps and after that latest SuperSU.
The device boots ok, but immediately I get the error of google play store - "unfortunetley, google play store has stopped". Trying to run the camera app gives "Unfortunately, Gallery has stopped". Gallery application gives "No external storage available".
I do not know if this is related, but when I am in recovery mode, I am able to use the file browser and see the content of /sdcard (which contains the files I pushed using "adb push" in order to flash the device), but if I boot into android, using adb to /sdcard (as root -> terminal + su) shows an empty folder.
Click to expand...
Click to collapse
By factory state you mean...?
Well on a side note, I tried using a CM10.2 with both their kernel and glitch's and based on my 1 month experience, battery issues are big time with this ROM and not the kernel itself. That is why I avoid CM10.2 based roms. If you're, however, satisfied with their features despite the battery drain then I guess you're good there. The custom ROMs have great stuff to offer.
MartCLEANRFr said:
By factory state you mean...?
Well on a side note, I tried using a CM10.2 with both their kernel and glitch's and based on my 1 month experience, battery issues are big time with this ROM and not the kernel itself. That is why I avoid CM10.2 based roms. If you're, however, satisfied with their features despite the battery drain then I guess you're good there. The custom ROMs have great stuff to offer.
Click to expand...
Click to collapse
well, at this point - i just want to make the device work...
Hello,
In the process of rooting and trying to install CWM Recovery in preparation to flash Cyanogenmod, I seem to have denied myself access to the phone's internal storage. In the "File Manager" app, I get the following screen:
Local: /storage
No files
No search results
In addition, any app that requires access to internal memory will not work, instead showing messages such as "Try again after scanning media files" or "Not enough storage". If I plug in the USB cable and set it to "Media sync (MTP)" mode, Windows Explorer will show the device but list the internal storage as having "0 bytes" and no files.
I already tried the following:
- Factory reset
- Flashing the official ROM through the Windows Enabler / UpTestEX tools
In both tries the phone was "reset", as in it returned to the initial Android welcome screen where you set up your Google account, but in each case I still didn't have access to internal storage.
This is what I have in the "About phone -> Software information" option:
Android version: 4.1.2
Baseband version: APQ8064T/MDM9x15M
Kernel version: 3.4.0
Build number: JZO54K
Software version: E98810b
The phone does not have Wi-Fi access either, which is why I was tinkering around with custom ROMs in the first place, so I won't be able to download anything to it as part of the solution.
Is there anything else I can try?
I'm guessing you used FreeGee to install CWM? Perhaps try restoring?
If that didn't work... Id move the EFS backups to my computer. I'd make a NAND backup in CWM. Then I'd get CM and gapps on a micro SD. I'd do a format of system, data, and cache. Then I'd install CM and gapps. Then I'd cross my fingers.
Sent from my LG-E980 using Tapatalk
ackliph,
Since I didn't have Wi-Fi access on the phone, and at the time I didn't know how to reverse tether it to the computer, I was looking for a procedure to install CWM Recovery that didn't involve downloading files directly within the phone (only transfering via USB). Right now I can't find the exact instructions I used, but it was similar to what is described by hkfriends in this thread: http://forum.xda-developers.com/showthread.php?t=2361941, the only difference being that the image I downloaded was not that one.
I rooted the phone with Universal Root, then followed those instructions to install CWM Recovery. It seemed to have worked, but when I rebooted... nothing happened! The phone booted normally, and if I tried entering recovery mode all I got was the stock LG recovery.
I continued looking for another way to install a custom recovery, but instead came upon instructions to flash KDZ files with UpTestEx. Since the immediate problem I was trying to solve was the lack of Wi-Fi access (and not really the custom ROM), I thought it couldn't hurt to try updating the stock ROM. The procedure did update my ROM, but I ended up in my current predicament: no access to internal storage, and still no Wi-Fi access! It even managed to unroot the phone.
So your suggestion would be to try installing CM via a microSD card. OK, I can get a microSD and try that. However, I do believe I will need root access to do anything of the sort. I tried Universal Root again, and got the following messages:
Beginning Root Process
/system/bin/sh: can't create /sdcard/G_security: Permission denied
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
1955 KB/s (1085140 bytes in 0.542s)
mount: permission denied (are you root?)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chown /system/xbin/su: No such file or directory
You are now properly Rooted.
Click to expand...
Click to collapse
Evidently, that didn't work.
I guess I will need some other method of rooting it.
Q&A for [ROM]TN.kitkat.4.4.2.HTC.evo.supersonic(aosp)viper.mod. a2sd_updated4/26/14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I'm running supersonic, hboot 6.16 with S-OFF. Have TWRP 2.8 Installed and flashed the TN kitkat rom and gapps core together but play store and the other Gapps do not show up. Someone suggested that using TWRP 2.7.0.0 worked for them, however, flashing 2.7.0.0 through bootloader gives a Fail-PU Update Fail and trying to flash it via fastboot also fails. So far, 2.7.0.0 is the only version of TWRP that fails to install. Any suggestions for getting gapps to work on this rom? I've tried flashing several other kk gapp packs, but they all fail with a message about not being able to run the update script in the zip file.
paultyler82 said:
I'm running supersonic, hboot 6.16 with S-OFF. Have TWRP 2.8 Installed and flashed the TN kitkat rom and gapps core together but play store and the other Gapps do not show up. Someone suggested that using TWRP 2.7.0.0 worked for them, however, flashing 2.7.0.0 through bootloader gives a Fail-PU Update Fail and trying to flash it via fastboot also fails. So far, 2.7.0.0 is the only version of TWRP that fails to install. Any suggestions for getting gapps to work on this rom? I've tried flashing several other kk gapp packs, but they all fail with a message about not being able to run the update script in the zip file.
Click to expand...
Click to collapse
TWRP 2.8 is probably fine - the GApps packages are likely just too large and the flash is failing because your system partition is full.
What do I need to do to get gapps working then? The posted gapps core package doesn't fail on flash like other gapp packs, but the market and other apps never show up.
paultyler82 said:
What do I need to do to get gapps working then? The posted gapps core package doesn't fail on flash like other gapp packs, but the market and other apps never show up.
Click to expand...
Click to collapse
Have you tried downloading the latest core GApps through the EV Updater in the ROM?
(I assume this ROM has that)
Just tried that, flashed through recovery, EV Update only lets you flash gapps in conjunction with a nightly. Flash seemed to succeed, but no luck. Gapps not appearing, nowhere to enter google account in the UI.
paultyler82 said:
Just tried that, flashed through recovery, EV Update only lets you flash gapps in conjunction with a nightly. Flash seemed to succeed, but no luck. Gapps not appearing, nowhere to enter google account in the UI.
Click to expand...
Click to collapse
Can you use the File Manager in Recovery to navigate to /system/priv-app and look for the Google apps? Maybe try extracting them from the zip and manually copying them and setting permissions? There must be some explanation. I've never had a problem with GApps. Can you try fully wiping (including system) and flash the ROM and core GApps again, just to be sure?
Ok. Wiped and reflashed. Odd thing is, before rebooting, the gapps appear to be in /system, however, on restart, they don't show up and when browsing to /system in ES File Explorer, the gapps have disappeared. I have never seen anything like it before, but then, I haven't played with Evos much.
paultyler82 said:
Ok. Wiped and reflashed. Odd thing is, before rebooting, the gapps appear to be in /system, however, on restart, they don't show up and when browsing to /system in ES File Explorer, the gapps have disappeared. I have never seen anything like it before, but then, I haven't played with Evos much.
Click to expand...
Click to collapse
You are wiping system, right?
Ok, tried a few more times now, let me walk you through what I've done.
First, using TWRP, I go to Wipe>Advanced Wipe and select EVERYTHING except sdcard, do the wipe. No errors.
Next, Install. I've now tried both TN KitKat and gapps together, gapps seperately after KitKat, and gapps seperately before KitKat
Each time the result is the same, new boot into KitKat results in the first run demo and no gapps to be found.
Here is the odd part I've now noticed that makes me think either I'm not doing something right, or TWRP isn't treating system correctly. All references to TWRP's file manager means using Advanced>File Manager.
On a new wipe, TWRP's file manager shows usr and bin directories in /system.
After any of the above methods of flashing, TWRP's file manager shows usr and bin AND everything from the gapps package but nothing from the KitKat package.
After first boot, ES File Explorer shows everything expected from the KitKat package in /system and nothing from gapps.
After first boot, rebooting into TWRP and using it's file manager shows only usr and bin present in /system, none of the KitKat or gapps stuff, yet booting back into the system works fine and ES File Explorer continues to show the KitKat stuff in /system.
Attempting to flash the gapps package in again after first boot gives the same results as above.
Attempting to copy anything into /system via ES File Explorer fails on a Read Only error.
Attempting to copy gapps into /system via TWRP file manager gives the same results as flashing the package.
Some other info that may or may not help... Using the Repair or Change File System tool in the Advanced Wipe menu reports the following for System partition: Mount Point: /system, File System: yaffs2, Present: Yes, Removable: No, Size: 350MB, Used: 317MB, Free: 32MB, Backup Size: 317MB
I appreciate the help, I'm thinking that certainly I've missed something along the way, but I can't figure out what.
paultyler82 said:
Ok, tried a few more times now, let me walk you through what I've done.
First, using TWRP, I go to Wipe>Advanced Wipe and select EVERYTHING except sdcard, do the wipe. No errors.
Next, Install. I've now tried both TN KitKat and gapps together, gapps seperately after KitKat, and gapps seperately before KitKat
Each time the result is the same, new boot into KitKat results in the first run demo and no gapps to be found.
Here is the odd part I've now noticed that makes me think either I'm not doing something right, or TWRP isn't treating system correctly. All references to TWRP's file manager means using Advanced>File Manager.
On a new wipe, TWRP's file manager shows usr and bin directories in /system.
After any of the above methods of flashing, TWRP's file manager shows usr and bin AND everything from the gapps package but nothing from the KitKat package.
After first boot, ES File Explorer shows everything expected from the KitKat package in /system and nothing from gapps.
After first boot, rebooting into TWRP and using it's file manager shows only usr and bin present in /system, none of the KitKat or gapps stuff, yet booting back into the system works fine and ES File Explorer continues to show the KitKat stuff in /system.
Attempting to flash the gapps package in again after first boot gives the same results as above.
Attempting to copy anything into /system via ES File Explorer fails on a Read Only error.
Attempting to copy gapps into /system via TWRP file manager gives the same results as flashing the package.
Some other info that may or may not help... Using the Repair or Change File System tool in the Advanced Wipe menu reports the following for System partition: Mount Point: /system, File System: yaffs2, Present: Yes, Removable: No, Size: 350MB, Used: 317MB, Free: 32MB, Backup Size: 317MB
I appreciate the help, I'm thinking that certainly I've missed something along the way, but I can't figure out what.
Click to expand...
Click to collapse
That's because you have to mount system in TWRP to see the actual contents.
What is the exact GApps package you're flashing?
I tried using both the gapps-core-kk-2013-11-25.zip posted in the OP, as well as gapps-kk442-20131211-core.zip from the EVUpdater.
I think I may have just gotten this to work, Play store is showing up. My solution was to manually mount /dev/block/mtdblock4 to /system via ADB and THEN flash the gapps package. Does TWRP not automatically mount NAND to /system? I didn't see an option anywhere in TWRP to mount partitions, the only thing I saw was the Mount menu item that seemed to be related to USB Media Device mounting, not actually mounting partitions. Did I miss something, for future reference?
paultyler82 said:
I tried using both the gapps-core-kk-2013-11-25.zip posted in the OP, as well as gapps-kk442-20131211-core.zip from the EVUpdater.
I think I may have just gotten this to work, Play store is showing up. My solution was to manually mount /dev/block/mtdblock4 to /system via ADB and THEN flash the gapps package. Does TWRP not automatically mount NAND to /system? I didn't see an option anywhere in TWRP to mount partitions, the only thing I saw was the Mount menu item that seemed to be related to USB Media Device mounting, not actually mounting partitions. Did I miss something, for future reference?
Click to expand...
Click to collapse
In the Mount menu in TWRP, there is a list of partitions and check boxes next to them. If you're not seeing that, then perhaps you have a bad recovery flash.
A recovery log would tell us exactly what's happening when you flash.
Thanks, figured that out now, mount via ADB accomplished the same thing.
Problem solved. The original directions call for both packages to be flashed at the same time, however, at least with TWRP 2.8.0.0, system appears to unmount after KitKat is flashed and gapps is installed to null. On this version of TWRP, you must flash KitKat, then mount system again via the Mount menu or ADB before flashing gapps. It seems that the KitKat package's script causes system to dismount and/or gapps package's script does not properly mount system on it's own.
---------- Post added at 10:18 PM ---------- Previous post was at 10:11 PM ----------
Also, thank you Captain for helping to solve the issue. I was apparently suffering from a serious case of terminal stupidity. It didn't even occur to me to manually mount system until you made the statement about having to mount it.
paultyler82 said:
Thanks, figured that out now, mount via ADB accomplished the same thing.
Problem solved. The original directions call for both packages to be flashed at the same time, however, at least with TWRP 2.8.0.0, system appears to unmount after KitKat is flashed and gapps is installed to null. On this version of TWRP, you must flash KitKat, then mount system again via the Mount menu or ADB before flashing gapps. It seems that the KitKat package's script causes system to dismount and/or gapps package's script does not properly mount system on it's own.
---------- Post added at 10:18 PM ---------- Previous post was at 10:11 PM ----------
Also, thank you Captain for helping to solve the issue. I was apparently suffering from a serious case of terminal stupidity. It didn't even occur to me to manually mount system until you made the statement about having to mount it.
Click to expand...
Click to collapse
Well it's weird that the updater-scripts aren't doing it. Like I said, I've never had an issue with flashing the ROM and GApps in TWRP.
I thought it was a bit weird as well, gonna have a look at the recovery log.
Found it. Gapps update script tries to run /sbin/busybox mount /system. This line fails because busybox isn't there, this failure only shows up in the recovery log, the script messages do not indicate that /system has failed to mount and the update script proceeds to run, installing to null and indicating install was successful.
And then there were two.
I still check in to this forum every day. And as far as I can tell, Vin and Cap are the only reason we are able put our legendary device in our pocket every day and know our rom and recovery are bleeding edge. Lollipop would be huge for our small but dedicated community. But for now the gift of KitKat plus a number of Android 5.0 apps gives me what I like to call "LolliKat". This is the most reliable phone I have ever owned! I hope I get to use it for another four years.
htc supersonic TN 4.4.4 problems
I installed TN 4.4.4 a month or so ago and keep having to reinstall at least once a week. The following problems occur:
Home button softkey quits working, while the menu and back soft keys still work.
Browser is inop, when i click it, it seems like it wants to open because a white screen pops up but then it disappears and goes back to my home screen.
I get no notifications in the status bar for anything.
Calls don't ring, i only know i have missed a call if i check my call history.
Lost theme settings, lost all info i setup on phone. Almost like it reset, except it didn't give me a welcome screen.
I am s-on, but i followed the s-on workaround.
When i hit the home button, catlog shows a keyguard msg, a dropping event because of a non touchable area, and a dalvik VM msg too.
Any ideas or suggestions?
cody85 said:
I installed TN 4.4.4 a month or so ago and keep having to reinstall at least once a week. The following problems occur:
Home button softkey quits working, while the menu and back soft keys still work.
Browser is inop, when i click it, it seems like it wants to open because a white screen pops up but then it disappears and goes back to my home screen.
I get no notifications in the status bar for anything.
Calls don't ring, i only know i have missed a call if i check my call history.
Lost theme settings, lost all info i setup on phone. Almost like it reset, except it didn't give me a welcome screen.
I am s-on, but i followed the s-on workaround.
When i hit the home button, catlog shows a keyguard msg, a dropping event because of a non touchable area, and a dalvik VM msg too.
Any ideas or suggestions?
Click to expand...
Click to collapse
im going to install this today.
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
cryptickid715 said:
im going to install this today.
Click to expand...
Click to collapse
will there be a LP lol
So this phone is used by my close relative and I usually update their phone for them. It worked great, no complaints.
Just today I wanted to do something in Magisk, but I didn't have the bottom options like I didn't have root.
Interesting. I thought something broke it, so I decided to update to latest OS and then try again.
Since the phone was running a few months old update, I thought I'd update + root to make sure everything works.
I used flash-all.bat to update, it flashed fine, the phone loaded fine, it shows September security update.
so I went ahead and tried to root like I always did.
got the latest image, updated via flash-all.bat (without -w switch), then copied over the boot.IMG, patched it on phone, copied back to my PC from /sdcard/Downloads, then used "fastboot boot magisk...img" to boot the patched img.
now, this is how I rooted my 9R and this 3a XL a dozen times. but not now.
I open Magisk once it boots up and it just shows me the same Install option.
It same as nothing happened.
like root just doesn't exist. wtf?
did Google mess remotely with Pixels? or what's going on?
ps.: I even tried to "flash" the img into the active slot, both slots, nothing.
like the .img itself is not getting patched.
using Magisk stable, 23.0.
update 1: Interestingly enough, Root Checker says I have root. But Magisk only has Patch File option, no Direct Install. Tried Canary too, nothing. Reinstalled Magisk app, nothing. So weird... like Magisk lost root access? But why? How do I fix that? So weird...
You can open a terminal app and type 'su' to see if it prompts you for root access. If not you can try uninstalling magisk, then rename the magisk.apk to .zip and sideload from recovery.
SOLVED!
Sorry for not updating my thread, it was pretty late when I cracked this.
Here is how I fixed it. (I'll format it a bit later.)
I went Termux, root with su.
went into /data/adb/ and there is a magisk.db file.
I copied that to /sdcard/ and then to PC (you can do this on phone too using SQLite editor apps but whatever. On PC it's easier, more screen estate, etc.)
I used SQLite Browser (free) to open the file, then Browse Data and Policies
here I saw all the apps that had root granted...
So I added a new line.
I used adb shell on PC to find out the data I needed.
first, pm list packages | grep magisk to find magisk's name (it's "com.topjohnwu.magisk")
then, dumpsys package com.topjohnwu.magisk | grep userId to find out the user ID (uid) for it.
I added these into the database, it looked like this in the end:
uid package_name policy until logging notification
10386 com.topjohnwu.magisk 2 0 1 1
(^ your userId will NOT be the same!
and the first line is the column names)
saved the file, copied it back to my phone in Windows, then used Termux to copy the file from /sdcard/magisk.db to /data/adb/magisk.db
then I shut down the phone, used "fastboot boot magisk_.. patched.img" so I'd have a rooted boot image loaded up.
and boom, Magisk app works again.....
how to tell if Magisk app loses root?
well, for me the screen went dark briefly for like 2 times when I opened the app on clean boot.
and of course, Direct Install was missing.
to verify root in this case - you can only use apps that are present in the .db file.
ie.: apps that you granted beforehand.
so I'd really recommend opening Termux then doing a "su" at least after a root.
Why does it happen?!?!
I THINK this happens when you repackage Magisk. So I'd recommend changing it back before doing a system update. Because after the system update, you most often need to reinstall the .APK and then its under the original package + app name. Thus, it's not in the Policy file -> ie.: the Magisk app will not have root.