Related
I've put together a rooted version of the stock 6.2.1 update if anyone wants to have at it. I flashed this on my own Fire with TWRP and it boots and runs fine, but I haven't done any other testing. Shouldn't need to wipe /data if you're coming from a 6.2 system, not sure about other ROMs like CM. Of course, I highly recommend you make a backup before flashing (good habit, and all that). To install just put it onto your Fire's /sdcard partition, boot into TWRP and install the zip. Note that TWRP will complain that it can't find the /misc or /sd-ext partitions. This is normal, those partitions don't exist on the Fire, but it won't affect the installation.
I downloaded the stock zip from the link in this post: http://forum.xda-developers.com/showpost.php?p=20509203&postcount=91 and then I changed the following from the stock zip file:
Removed the bootloader and recovery.img updates
Removed the backup_data.zip because it doesn't make sense, really (it looks like it just extracts to /backup/, but if you flash it it will wipe your /data partition?)
Added busybox, Superuser and the su binary. Should be properly symlinked and permissions set correctly.
Modified the updater-script for the above things.
Additionally, if you have the Market installed you may need to re-install it after updating since Amazon didn't do this as a patch - it just formats /system and replaces it. If you updated the Market manually then the newer version should survive in /data/app. Also, if you installed any custom frameworks or libraries (e.g. the maps framework to use Google Currents and whatnot) then you'll need to reinstall those. Basically, anything you added or modified on /system will be gone.
Edit: Thanks sadlius for pointing me to dsixda's kitchen! I've added a version with an unsecure boot image (so you get root by default on a shell). I'll leave the old one in case anyone would prefer the secure boot image. I've also uploaded the boot image itself for anyone who might have already flashed the secure 6.2.1 zip. I tried it with fastboot and it booted up fine, so you can test it first with:
Code:
fastboot boot 6_2_1rootboot.img
If it works, you can flash it (permanently overwrites your current boot partition) with:
Code:
fastboot flash boot 6_2_1rootboot.img
Downloads
MOD EDIT: Links no longer valid so removed.
Multiupload, courtesy sadlius:
update-6.2.1-rooted-secureboot.zip
Stock rooted update 6.2.1, secure boot image
update-6.2.1-rooted-unsecureboot.zip
Stock rooted update 6.2.1, unsecure boot image
Multiupload, courtesy intel352 (md5's should be the same):
update-6.2.1-rooted-secureboot.zip
Multiupload:
6_2_1rootboot.img Unsecure 6.2.1 boot image
Original Downloads:
Removed these so Dropbox won't yell at me anymore
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
But I think I know what the problem is. Will attempt again in a few minutes. Or as soon as TWRP relinquished control of my KF back to me.
You sir are a good Man....
sadalius said:
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
But I think I know what the problem is. Will attempt again in a few minutes. Or as soon as TWRP relinquished control of my KF back to me.
Click to expand...
Click to collapse
I got the "Cannot load volume /misc!" error, too, but it seems to be okay anyway. The KF simply doesn't have a /misc partition.
Curious that it can't open the zip, though, but I'll wait until after your second attempt to try troubleshooting.
sadalius said:
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
Click to expand...
Click to collapse
I have seen the same errors when I installed TWRP. It didn't seem to make a difference to it loading.
All but the last line.
E:Unable to open zip file.
Click to expand...
Click to collapse
I think that is the real error.
I got it figured out. Somehow, the file was corrupted when I transferred it to the KF. Deleted it and re-transferred, it took it that time. Will report any positives or negatives once I get back to the actual OS and play around with it.
Thanks a bunch!!
---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------
Yes. Everything I've tried so far works great!!
I do have one question though. I used to cook my own roms from OEM releases back when I had an HTC hero. May I ask what you used to root this with?
isn't 6.2 is latest ? where did 6.2.1 came from?
HI,
is there someway for me to flash this using fastboot? Because im stuck in fastboot and can't get out of it!
sadalius said:
I got it figured out. Somehow, the file was corrupted when I transferred it to the KF. Deleted it and re-transferred, it took it that time. Will report any positives or negatives once I get back to the actual OS and play around with it.
Thanks a bunch!!
---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------
Yes. Everything I've tried so far works great!!
I do have one question though. I used to cook my own roms from OEM releases back when I had an HTC hero. May I ask what you used to root this with?
Click to expand...
Click to collapse
I do it manually. The update had a .bin extension but it was really a .zip, so I renamed it, extracted it, and made the modifications I wanted (like adding su/Superuser). Then I just re-zipped it.
Don't know if it's the most "efficient" way to do it, but it's straightforward enough and it's how I've always done it...
Wonder if dsixda's android kitchen would work on it. If it would, it would automatically make the boot.img unsecured through the root process. Not sure if it will handle it though.
tes5884 said:
HI,
is there someway for me to flash this using fastboot? Because im stuck in fastboot and can't get out of it!
Click to expand...
Click to collapse
Edit: Pointed out in another post - the system image might be too big to flash via fastboot (like I said, I've never actually tried to use these). If you can get into fastboot you can try flashing a recovery, though, and then use that to try dd'ing the system image over or something.
Edit 2: Took down links since I exceeded my Dropbox bandwidth.
Can anyone verify this works? I mean the 6.2.1 pre rooted update zip
Sent from my Triumph using XDA App
dueltothedeath said:
Can anyone verify this works?
Sent from my Triumph using XDA App
Click to expand...
Click to collapse
Yes, I can. Works pretty well too. You'll get some error messages, but those shouldn't be an issue. When I installed it those error messages kind scared me, but once someone explained them, I felt a little better.
sadalius said:
Yes, I can. Works pretty well too. You'll get some error messages, but those shouldn't be an issue. When I installed it those error messages kind scared me, but once someone explained them, I felt a little better.
Click to expand...
Click to collapse
Anychance you could explain them to me? Working for me as well just curious what they mean.
sadalius said:
Wonder if dsixda's android kitchen would work on it. If it would, it would automatically make the boot.img unsecured through the root process. Not sure if it will handle it though.
Click to expand...
Click to collapse
Maybe I'll look into that tonight or tomorrow when I've got some time. I actually didn't know that the kitchen created an unsecured boot image for you. Thanks!
fbm111 said:
Anychance you could explain them to me? Working for me as well just curious what they mean.
Click to expand...
Click to collapse
When I first tried to install I got these error messages:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
since the kindle fire does not have a /misc volume or /sd-ext/ partition, it would give those errors. Those are nothing to worry about. The last error, Unable to open zip file was a real error, but it was cause when I transferred the file to flash to the KF, it got corrupted somehow. I just deleted it from the kindle using file expert and re-transferred it then tried flashing again. All was well at that point. I still got the cannot load volume /misc! and unable to stat '/sd-ext' but like I said, those do not exist on the kindle, thus the messages. But it still installs correctly.
---------- Post added at 05:05 PM ---------- Previous post was at 04:49 PM ----------
eldarerathis said:
Maybe I'll look into that tonight or tomorrow when I've got some time. I actually didn't know that the kitchen created an unsecured boot image for you. Thanks!
Click to expand...
Click to collapse
I took a quick look at it with your rom. It recognizes everything you've done to the ROM thus far. Have a look:
Android OS version : 2.3.4
Device : blaze
Model : Full Android on Blaze or SDP
ROM Name : L27.12.1-P1_QUANTA_20110422_quantaonly-1027-gefdcdf8
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : NO
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I don't have time to try it out with the stock rom, if I get time tomorrow I'll give it a go to see if it will work with it or not to make the boot.img unsecured. This maybe just what the doctor ordered to keep a stock rooted rom.
I flashed it and I don't really notice much of a difference, although my android market still works even tho this update obviously removed it as a system app but the update in /data/app still works.
sadalius said:
I took a quick look at it with your rom. It recognizes everything you've done to the ROM thus far. Have a look:
Android OS version : 2.3.4
Device : blaze
Model : Full Android on Blaze or SDP
ROM Name : L27.12.1-P1_QUANTA_20110422_quantaonly-1027-gefdcdf8
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : NO
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I don't have time to try it out with the stock rom, if I get time tomorrow I'll give it a go to see if it will work with it or not to make the boot.img unsecured. This maybe just what the doctor ordered to keep a stock rooted rom.
Click to expand...
Click to collapse
I just tried using dsixda's kitchen to modify the boot image and it looks like it worked. I can boot it in fastboot at least! I'm going to package it up and try flashing it for some testing. Thanks a lot!
neilrl79 said:
I flashed it and I don't really notice much of a difference, although my android market still works even tho this update obviously removed it as a system app but the update in /data/app still works.
Click to expand...
Click to collapse
It seems like a lot of little changes, so far. You can remove things from your carousel by long pressing them, and you can restrict certain access to your one-click and stuff. It also looks like the "Device" menu in settings got a little facelift because it lists "Application Storage" and "Internal Storage" separately (which I don't think it did before).
I flashed 6.2.1 unsecured .zip via twrp and received two E:Cannot load volume /misc! errors. I then wiped cache and dalvik, and booted up. Everything including Voodoo OTA root works fine. As you said though, google market was obliterated. I am about to put it back.
Edit: after sticking vending.apk back in /system/app and fixing permissions it appears everything is 100% back to order including market and running 6.2.1. I can't thank you enough. 6.2.1 feels much snappier, although it might be a placebo effect.
does this work if i am already on 6.2.1?
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
Q&A for [ROM][UNOFFICIAL] CyanogenMod 12 Nightlies
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Update your recovery to supported one. See the list below.
TWRP 2.8.1.2 ACE or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Where is my root?
A: http://www.cyanogenmod.org/blog/all-about-l-part-2 (Read under "Superuser where?")
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM12.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm12
cd cm12/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-12.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
Thanks..reserved?
Sent from my ATRIX HD using Tapatalk
Home button not working. Have to use back button
Camera Bug
Camera is in the Apps not listen and it dont work from Lockscreen.
Sorry for my English and a big Thanks from Germany / EinfachAleks
No sounds.
---------- Post added at 11:32 AM ---------- Previous post was at 11:14 AM ----------
I don't have camera at all
Sent from my Desire HD using Tapatalk
Great job Tested on my Inspire 4G with alpha gaps all - so all works good but one problem at startup setting after ten minutus of thinking it cant set up my GSM career and tell me to set up it next time I'll think okay wait when all google sutups done ..... go to setting /mobile wireless/operator settings ... and at this moment I have a crash. I hawe an Ukrainian operator maybe this thing cause such problem Thank you a lot for you futer job at this rom And WiFi works greate ))))
For me the Home Key just working fine...im waiting for the next Snapshot
I'm gonna download zip again and flash again. Maybe bad flash.
Doge2 and recovery
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
With TWRP 2.8.1.0 it installs but these TKruzze gapps (https://s.basketbuild.com/devs/TKruzze/Android 5.0 GApps/Micro-Modular GApps/) gives error
E: Error executing update binary zip "gapps location.zip"
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
Finnaly old bug for me.
Does anyone have same problem like I do? I can't make partitions with TWRP 2.8.1.0 partition editor! With 4ext recovey I can make partition but with TWRP I can't.
http://forum.xda-developers.com/htc-desire-hd/help/qa-twrp-2-8-1-0-cwm-6-0-5-1-unofficial-t2952947
first i want to thank you for this amazing rom
and i want to ask if i update from doge 1 to doge 2 should i flash boot.img again after installing the rom
marek287 said:
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
http://forum.xda-developers.com/htc-desire-hd/help/qa-twrp-2-8-1-0-cwm-6-0-5-1-unofficial-t2952947
Click to expand...
Click to collapse
I have the same error
marek287 said:
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Try to format your system partition manually. If that doesn't help, contact 4EXT dev. Generally I can't fix recovery related issues like this seems to be.
marek287 said:
With TWRP 2.8.1.0 it installs but these TKruzze gapps (https://s.basketbuild.com/devs/TKruzze/Android 5.0 GApps/Micro-Modular GApps/) gives error
E: Error executing update binary zip "gapps location.zip"
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
Click to expand...
Click to collapse
You'll probably need even smaller gapps. Our system partition is getting very small as the base system size has increased a lot since gingerbread. I haven't tried any gapps yet as they are irrelevant to our roadblocker issues so I can't give any recommendations.
desire hd user said:
first i want to thank you for this amazing rom
and i want to ask if i update from doge 1 to doge 2 should i flash boot.img again after installing the rom
Click to expand...
Click to collapse
Yes, if you are S-ON. There are some kernel related changes which are included in the boot.img so it needs to be updated too.
Mustaavalkosta said:
Try to format your system partition manually. If that doesn't help, contact 4EXT dev. Generally I can't fix recovery related issues like this seems to be.
Click to expand...
Click to collapse
That was mine second throught but main goal was to anounce others that problem. I posted it to 4EXT recovery Q/A threat
http://forum.xda-developers.com/showpost.php?p=57171180&postcount=2
and recontacted (PM) to jrior001 TWRP recovery partition bug.
rom not working
help me. Excuse, but apparently I'm the only one that failed to install the rom.
during installation sticking a message like warnig and then something about the sound and would not start more
I've already checked MD5
DOGE2 + PA GApps ALPHA1 flash succeeded
Thank you Musta and the team for great job!
http://forum.xda-developers.com/showthread.php?p=56560109
I flashed DOGE2 + PA GApps ALPHA1, and they work fine.
(cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip + pa_gapps-micro-5.0-ALPHA1-20141117a-signed.zip)
Before flashing, I made .gapps-config which containing the text "NanoGApps", and placed it in the same folder as the GApps zip.
Then, flashing has succeeded.
I didn't try "PicoGApps" option, but it will also succeed, I suppose.
matbeta said:
help me. Excuse, but apparently I'm the only one that failed to install the rom.
during installation sticking a message like warnig and then something about the sound and would not start more
I've already checked MD5
Click to expand...
Click to collapse
Install TWRP 2.8.1.0 then install the rom again. http://forum.xda-developers.com/showthread.php?t=2780164
After downloading writes: "sim card added restart your device".
bratmarat said:
After downloading writes: "sim card added restart your device".
Click to expand...
Click to collapse
Yeah, it's a bit wonky. Just hit back to skip it for now. Telephony code is still undergoing some changes.
Very good job. I wait for doge3
hello Mustaavalkosta, Great job, say thanks to you and all the dev team.
I am chinese user, i found doge 3 always crash when i install most common app.
such as baidunews, baidu market, zhihu
please check it, hope doge 4 coming as soon as possible.
Phone: Nexus Shamu 6
Current lineage: 14.1
I downloaded the lineage-15.1 nightly .zip and GAPPS, copied them to /sdcard, tried to install them in TWRP, and got:
E: error executing updater binary in zip /sdcard/lineage-15.1-20180416-nightly-shamu-signed.zip
Error flashing zip
I tried again without wiping, then while wiping cache/Dalvik, then after a Factory Reset. Same problem, same error. Changing file permissions for the .zip didn't help.
I have used this method to update .zips for at least a year, the last time with the most recent version of 14.1. This is the first time I've seen this error. Any troubleshooting steps will be appreciated.
Thimoteo said:
Phone: Nexus Shamu 6, Current lineage: 14.1. I downloaded the lineage-15.1 nightly .zip and GAPPS, copied them to /sdcard, tried to install them in TWRP, and got:...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS 15.1 thread for your device.
https://forum.xda-developers.com/showthread.php?t=3773143
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks, Ibuprophen. I hadn't seen that forum. I just took a look, and saw immediately that my version of TWRP is no longer supported. I'd better upgrade TWRP before taking other troubleshooting steps.
You can find latest radio on lineage 15.1 thread
aljoscha81 said:
So here i post new radios when the stock 8.1 will be updated feel free to test.It is maybe not the fact that something is changed in new radio but in changelog it is also point out that not every change from build to build is written in so testing testing testing.............. :fingers-crossed::highfive:
Ps. Sorry for my bad english
Radio v:5.42:https://mega.nz/#!iq5xgSZZ!J6uTZQ39enNcrWrCGIKofVEzxKti75Myb_VhJJVxl0s
Click to expand...
Click to collapse
Android 9? How you did it?
Deleted
Pie
Deleted
Deleted
It was released a new radio update 5.50
Deleted
aljoscha81 said:
Yes i am on latest build arrow os 9 treble rom i got nearly everything working only nfc don't work for me you must be on mokee 81 rooted with magisk 17.1 installed total commander delete with total commander in system/vendor/ lib and lib64 vndk-sp folder with all in it then create in system/vendor a folder called overlay in the overlay folder copy and past the apk from this thred :https://forum.xda-developers.com/pr.../overlay-enable-night-light-adaptive-t3741965
Then from terminal run this command first:
mount -o remount,rw /vendor
Then the command from the thread you got the apk. From
Restart
Then you flash twrp 3.2.3-3 in this forum you can find it
Wipe in advanced wipe everything format data make factory reset restart to twrp
Use otg device with extracted img. Of arrow os and choose img. Install choose system for where to install
After image is installed boot to system
Now you must install open gapps in twrp
The system will run crazy while you are not got a registred device but you can install device id apk. In device id apk tab google service framework tab copy tab on the message your device is not registred on custoum rom link log in with your gmail email and password in the row to put in you past what you before copyed in the id apk. And tab register a few reboots and the messaging will stop now in settings you see you can set up your phone and voila you on android p
Ps for camera is also a fix out there so face unlock also works
Click to expand...
Click to collapse
please share step by step
Deleted
Deleted
aljoscha81 said:
New update
Click to expand...
Click to collapse
Thanks
This should be the last update to come, right? Nubia themselves said they stop developing Android 8+ for Z17. Any luck with GPS tracking on last update (taking ~2 minutes until it can track you properely)?
Deleted
Deleted
Any radio more than 5.52?
Deleted
Deleted