Related
Hey guys, so I searched and search, using the search function as described in the forum rules, and couldn't come across anything with this nature, so if anyone has an urge to help out a noob I would really appreciate it!
So I downloaded the new Android Desire V4 rom, someone told me there were instructions in the download, which there were...they read as follows...
set mtype 2524
set ramaddr 0x20000000
set ramsize 0x0fc00000
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline ""
boot
So my question is, again, um how do I do any of that! LOL Those look like a list of things I am supposed to do as opposed to actual instructions on how to do them LOL
If I run HaRet, it boots, but from my understanding I need to do the above list to make it functioning to it's (current) fullest potential?
Thanks for any assists!
i haven't tried android, not interested in kids play things, but that to me lookslike a list of setup commands, , sure they aren't supposed to go in an initialization file of some kind?
thats the startup txt details, and all you hav to do is copy it all to ur sd root and thats it its honestly not worth it at the min unless u just gonna play about for a bit
hmm
samsamuel said:
i haven't tried android, not interested in kids play things, but that to me lookslike a list of setup commands, , sure they aren't supposed to go in an initialization file of some kind?
Click to expand...
Click to collapse
Probably, but I don't even know what that means! LOL
I am like a super noob..haha.
I guess I am asking specifically what you would do, every step, to do the list of setup commands.
1. How do I change to those values, like which part of the phone I go into.
2. If they need to be installed, how exactly, specifically do I install them.
I am basically looking for full instructions. For example if I were teaching someone to watch a DVD who has never used a DVD/movie playing device before, I wouldn't just say "put it in and watch it." I would say. "This is the power button. Click that to turn the device on. This is the open tray button, click this, and place the DVD shiny/mirror side down flat. Click the open tray button again to close the tray. Once closed it should automatically play, if not click the button with the sideways triangle on it to start the movie."
Like that is how nooby I am with this stuff LOL..but not stupid enough to change something I shouldn't, screw something up. If the instructions are there, I got it.
Demon_man said:
thats the startup txt details, and all you hav to do is copy it all to ur sd root and thats it its honestly not worth it at the min unless u just gonna play about for a bit
Click to expand...
Click to collapse
So I don't have to do anything? I have booted Android Desire V4 rom about 22 times so far, and every single time it is stuck in fast forward mode, does not give me the sim option like in the instructions on the website to download the file, and is generally the exact opposite of what everyone is claiming it is/doing.
So I would assume I am missing some key crucial steps no? Also My radio rom is fine, I reformatted my SD Card, it's fresh and all files are on the root of the card. From the sounds of it, you have to do something with the zImage (from what I have read), and something else... this is why I am confused.
as far as i'm aware there are still a few issues where certain models cant run it properly? and isn't there something about there being a few different digitizers, and it only works on some? (that might not be an issue anymore, i've not been keeping up)
i tried android quite a few times on my previous device (htc kaiser). i believe nearly the same concepts apply to the HD2 at the current stage of android development for the HD2.
facts:
1. you should know that android's files are to be kept on the sd card according to the instructions (more details here: http://forum.xda-developers.com/showthread.php?t=719646)
2. you should know that your windows and any settings made under windows will remain INTACT. this is because android, being in the storage card, is like an independent operating system.
3. point 2 above implies that any settings specific to windows or specifically made in the windows system settings (etc) have NO IMPACT on android. so no need to ask:
1. How do I change to those values, like which part of the phone I go into.
Click to expand...
Click to collapse
4. the only things important to android are the radio ROM version and MAYBE the (Hard)SPL version.
5. android is spun into action using "haret". haret is a little program that is started from windows but it essentially kicks out windows (temporarily) and tricks the phone into booting android from the sd card.
so from all of the above points, we can conclude that any and all configurations for android must be made in some text files. this text file must be placed according to the instructions somewhere along side haret and the rest of the android files on the sd card. this should answer:
2. If they need to be installed, how exactly, specifically do I install them.
Click to expand...
Click to collapse
this text file, as suggested by demon_man in post 3 in this thread is the "startup.txt". another name for startup.txt is "default.txt". these files are the same, except that haret pre-selects "default.txt" as your startup script when you launch haret. this saves you the step of manually selecting a particular startup file (you can have a bunch of startup files with different settings in each to experiment and you can name them ANYTHING). so after experimenting, you should arrive at a startup file containing configurations that work well for you. you can then name this file as "default.txt" and you can also optionally delete all the other startup files you created while you were experimenting.
i hope the above gives you some idea of what to do. if i had tried android on the HD2 for myself and if i had personally done more research of android on the HD2, i would have certainly given you some links of material that i am CERTAIN already exists, if you fancy searching just a little bit. being a noob is no excuse, because "search" is the FIRST forum rule. and just saying that you searched without posting some example keywords of what you searched for sounds "fishy", so not sure you searched well
i have written the above to help you build your concept, but we would all applaud for you (yay!) if you post in the appropriate threads for android and android tutorials from now on. i doubt you will need to post more because what i have tried to detail for you above should be a very solid foundation for you to understand how the wonderful people here at xda have gotten android to work on devices it was never released for.
Not too sure if this belongs in Q and A... But I have a Titanium Backup folder copy on my PC. Well, when I try to delete the folder it causes the program to "not respond". So I bring up task manager and "end task". It then closes everything on my PC, and all the desktop icons disappear. There's nothing other then the wallpaper. Only thing that still works is task manager. Restart PC, try again. Same thing. Happens when I put the folder in recycle bin, or by deleting just some of the folder contents. I did some spring cleaning on the PC today, and this is the only problem I've had and its consistant, and specific to this folder. Any ideas on how to delete it?
Use Astro/file explorer/Root broswer to delete it from your device.
That would probably work to get it off my phone, but the problem is on my PC. when I was in newb stages I had a backup of a backup on my PC. It's just this one TB Backup file on my PC that is causing problems and wont delete.
You could move all the files to a folder except the TB Backup and just format the sd card. that could help.
Virus scan your pc, if you haven't already. Or boot into safe mode and that should allow you to delete the file. Or you could do a system restore.
Root-Hack_Mod*Always\
laie1472 said:
Virus scan your pc, if you haven't already. Or boot into safe mode and that should allow you to delete the file. Or you could do a system restore.
Click to expand...
Click to collapse
Yeah, did a scan and it didn't pick anything up. But I had a hell of a trojan about a month ago and I was thinking it could possibly have to do with that. Although I did a very deep clean. I will give safe mode a shot. I got the PC from my parents with a bunch of virus/trojan issues only a few months ago, and because of all the cleaning and the other trojan I got....I'm not too positive a system restore will be good. I was going to create a new restore today since all has been great....until this.
Ok sounds like some spyware or malware. As said before boot into SAFE MODE, but select the SAFE MODE WITH NETWORKING. Go to http://www.superantispyware.com/ download the free version. Install it, then run superanti spyware. Select to do a COMPLETE SCAN not quick scan. On the next screen select HIGH BOOST and scan inside of ZIP files, which will use most of your cpu it will run about 80% just let it run because it will slow down anything else you try to do. After it is done get rid of the bad files, tracking cookies and/or any trojans left. Reboot the computer, but into safe mode with networking again. Then go to http://www.malwarebytes.org/ and download the free version and install. Run the complete scan in malwarebytes. Let that run and when it finishes is will ask for a reboot. Reboot, again and you should be good to go. I have seen this on teachers computers at least weekly, because of the stupid Ransom WARE. If that doesn't work than my last suggestion would be download combofix from bleepingcomputer and run that. Hope this helps a lil
gokart2 said:
Yeah, did a scan and it didn't pick anything up. But I had a hell of a trojan about a month ago and I was thinking it could possibly have to do with that. Although I did a very deep clean. I will give safe mode a shot. I got the PC from my parents with a bunch of virus/trojan issues only a few months ago, and because of all the cleaning and the other trojan I got....I'm not too positive a system restore will be good. I was going to create a new restore today since all has been great....until this.
Click to expand...
Click to collapse
Let me know if the safe mode works.
Root-Hack_Mod*Always\
dont forget to check the permissions of the folder itself tooif windows doesnt let you find them and you have two new choices so keep us all posted
mikejones13 said:
Ok sounds like some spyware or malware. As said before boot into SAFE MODE, but select the SAFE MODE WITH NETWORKING. Go to http://www.superantispyware.com/ download the free version. Install it, then run superanti spyware. Select to do a COMPLETE SCAN not quick scan. On the next screen select HIGH BOOST and scan inside of ZIP files, which will use most of your cpu it will run about 80% just let it run because it will slow down anything else you try to do. After it is done get rid of the bad files, tracking cookies and/or any trojans left. Reboot the computer, but into safe mode with networking again. Then go to http://www.malwarebytes.org/ and download the free version and install. Run the complete scan in malwarebytes. Let that run and when it finishes is will ask for a reboot. Reboot, again and you should be good to go. I have seen this on teachers computers at least weekly, because of the stupid Ransom WARE. If that doesn't work than my last suggestion would be download combofix from bleepingcomputer and run that. Hope this helps a lil
Click to expand...
Click to collapse
Yeah, I did something like this in order to get the last trojan off. I tried/have a million virus/anti-malware programs, of course only one active now which is the malwarebytes one. The trojan I had was a Win32/Sirefef one, can't remember specifically which one. But I did have to do a combo fix and I continued to check for about a week after....all was good.
laie1472 said:
Let me know if the safe mode works.
Click to expand...
Click to collapse
Will do.
wloftus said:
dont forget to check the permissions of the folder itself too if windows doesnt let you find them and you have two new choices so keep us all posted
Click to expand...
Click to collapse
I didn't check the actual permissions, will do that too.
Thank you all for the ideas/help. Much appreciated! Won't be back to the PC until tomorrow, will let you know what I find.
Update... Ran multiple virus scans and nothing showed up on any of them. Tried deleting folder in safe mode, but it still froze up without any icons. Still did the same if I tried erasing only one of the files in the TB folder itself. Permissions were set normal, as other files that I erased with no issues. Ended up erasing all my other phone backups (twrp, etc...) that were in the "BACKUPS" folder, the same folder the TB folder was in. Then I erased the "BACKUPS" folder itself with the TB one in it, and that seemed to do it. Definetly weird, but at least I got it deleted.
Your asking I. The wrong place buddy. This is for EVO 3d questions.
Have you tried to even search about it.
Sent from my PG86100 using Tapatalk
gokart2 said:
Update... Ran multiple virus scans and nothing showed up on any of them. Tried deleting folder in safe mode, but it still froze up without any icons. Still did the same if I tried erasing only one of the files in the TB folder itself. Permissions were set normal, as other files that I erased with no issues. Ended up erasing all my other phone backups (twrp, etc...) that were in the "BACKUPS" folder, the same folder the TB folder was in. Then I erased the "BACKUPS" folder itself with the TB one in it, and that seemed to do it. Definetly weird, but at least I got it deleted.
Click to expand...
Click to collapse
what you need to do to avoid all this is just download any linux live version... i personally use hirens boot cd 15... once downloaded take the image and either burn it do a cd or use a linux installer... i use pendrivelinux load that up and let it install your boot cd to your usb thumb drive....once that is completed reboot your computer and as it reboots have it load the usb drive first once that loads up you then can boot into partition magic and use linux's permissions and rights to over take windows permissions does that all automatically.... from there you right click and delete....need help or info feel free to pm me
iTzLOLtrain said:
Your asking I. The wrong place buddy. This is for EVO 3d questions.
Have you tried to even search about it.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I'm asking in the wrong place...is that what u meant? Read from the original post. If it was that far out of the wrong place, it would more then likely have been moved by now. I always search, and search for awhile before posting. It seemed somewhat relative to me do to the fact the file came from my evo3d, and is a file made by an android app everyone rooted uses. I was also aked yo give an update on the problem.
wloftus said:
what you need to do to avoid all this is just download any linux live version... i personally use hirens boot cd 15... once downloaded take the image and either burn it do a cd or use a linux installer... i use pendrivelinux load that up and let it install your boot cd to your usb thumb drive....once that is completed reboot your computer and as it reboots have it load the usb drive first once that loads up you then can boot into partition magic and use linux's permissions and rights to over take windows permissions does that all automatically.... from there you right click and delete....need help or info feel free to pm me
Click to expand...
Click to collapse
Thanks, this was originally what I was after...but in a windows software program. BUT....I will more then likely do this anyway. Slowly working the noob out...but there's SOOOOOOOOO much to learn (still), I feel overloaded sometimes. I'm in the process of downgrading hboot on the 3d, and downgrading iOS and performing a jailbreak on my old 3g so the boss and kids stop whining at how slow it is and why there's still a phone button on it...lol.
gokart2 said:
I'm asking in the wrong place...is that what u meant? Read from the original post. If it was that far out of the wrong place, it would more then likely have been moved by now. I always search, and search for awhile before posting. It seemed somewhat relative to me do to the fact the file came from my evo3d, and is a file made by an android app everyone rooted uses. I was also aked yo give an update on the problem.
Click to expand...
Click to collapse
Have you even tried formating the sdcard?
Sent from my PG86100 using Tapatalk
Ohhhhh boy.
gokart2 said:
Ohhhhh boy.
Click to expand...
Click to collapse
is this a good ohhhhh boy?
I take no credit for any of this, I have just put together things I have found on various threads.
As you all know the touch screen calibration that runs at boot does not work with any of the newer kernels as you cannot see some of the cross hairs to tap. I have personally NEVER been able to produce my own accurate ts-calibration file and have been using an ancient one that I downloaded back in the early days of FRX (thank you arrrghhh). Hopefully you have a somewhat functional ts-calibration file as you need to carry out this procedure from within Android. Here we go... (it's easy)
1. Download HtcCalibrate_WVGA.apk, thanks to lukas.pce, attached to first post here http://forum.xda-developers.com/showthread.php?t=1457343 to your device.
2. Install HtcCalibrate_WVGA.apk
3. Run HTC Calibrate and follow the instructions, tapping all the points (I used a toothpick for added accuracy)
4. When complete the app will report 'Calibration complete', tap 'Done'. Your screen should now be accurately calibrated for this session. Test to make sure it is working correctly before proceding to next step.
5. Now to get the calibration data to stick after reboot: Open your file explorer (MUST HAVE ROOT ACCESS; I use ES File Explorer with Menu>Settings>'Up to Root' checked) and navigate to /sys/devices/virtual/input/input3/ there you should see a file named calibration_points.
**It seems that in some builds (perhaps depending on kernel version?) that the devices get defined differently and I have found the file calibration_points in /sys/devices/virtual/input/input2/.
**So if you can't find it in input3/ then check input2/ (I haven't seen it anywhere else, but it probably could be in input1/, 4/, or 5/ as well, if not in the first two).6. Finally copy calibration_points to /sdcard/ (the root of your SD card), delete your existing ts-calibration file (or backup somewhere if you want) and rename calibration_points to ts-calibration.
**Nand users see this (thanks wizardnight!):
wizardknight said:
BTW on the nand version (GBX0* + 3.3.x kernel) it needs to be placed in /data/
Click to expand...
Click to collapse
Done. Your phone should now boot with the calibration data you created.
So that is where it sticks the file. I have been trying to find that out forever. Cool beans.
I had been using an old version of GBX0B on an sd card to make a decent ts-calibration file. Kind of a pain as you have to load up WM, then GBX0B to make the file at boot time (and it wasn't as accurate as the HTC one), copy it , and then reload the GBX and paste it.
BTW on the nand version (GBX0* + 3.3.x kernel) it needs to be placed in /data/
Why couldn't you have posted this sooner When I was using GBX0C I couldn't find the file anywhere
Ha! Sorry, I just found it today. Your problem was prbably that you looked virtually everywhere! It does seem an odd place for the file to be.
Would it work to bind-mount that file to /data/ts-calibration in the boot script, so that running HTC Calibrate will automatically write it?
That I do not know. I have never looked at the boot script or bind mounted anything. But automating this does sound like a great idea!
It would be amazing if a dev could do a reverse compile on this app, and put in an option to select the save location. One can dream.
I was taking a look at the data and time stamps on calibration_points, and it seems that there is a script somewhere that takes ts-calibration and overwrites calibration_points at boot time. If that is correct disabling that overwrite would mean the app could work fine as-is.
Unfortunately just renaming the ts-calibration is not enough. During the boot process it creates a new one with a set of values.
I found this bit of code that might explain why we are seeing this overwriting.
http://gitorious.org/xdandroid/rootfs/merge_requests/4
Part 1 locates the touch screen manager directory
Part 2 looks for ts-calibration in /data/ and if it finds it overwrites calibration_points
otherwise it creates a new ts-calibration using a default set of values and then overwrites calibration_points
So what we want to do is have it overwrite /data/ts-calibration with $touchscreendir/calibration_points as long as calibration has been completed previously within android.
Now I haven't really written code/scripts in a decade and am not yet too familiar with linux but something like:
(tiad8's commit, edited poorly by me)
## Ts Calibration
for i in /sys/class/input/input* ; do
if [ "`cat $i/name`" = "tssc-manager" ] ; then
touchscreendir=$i
echo "Touchscreen device directory is $i"
fi
done
if [ -f /data/ts-calibration ] ; then
echo "Using Saved Touchscreen Calibration"
echo 128,128,1903,128,128,1907,1903,1907,1024,1024 > $touchscreendir/calibration_screen
cat /data/ts-calibration > $touchscreendir/calibration_points
else
if [ -f "$touchscreendir/calibration_points"="0,0,0,0,0,0,0,0,0,0" ] ; then
echo "Using Default Calibration Values"
echo 821,860,197,868,500,517,829,172,191,171 > /data/ts-calibration
cat /data/ts-calibration > $touchscreendir/calibration_points
else
echo "Using Last Calibration Values"
echo 128,128,1903,128,128,1907,1903,1907,1024,1024 > $touchscreendir/calibration_screen
cat $touchscreendir/calibration_points > /data/ts-calibration
fifi
I am sure that my commands and syntax above are wrong, it's the concept that I am trying to convey.
I want to look to see if there is a ts-calibration and if not then look to see if there is valid calibration data in calibration_screen and if there is then write that value to ts-calibration. Thus to update calibration all you need to do is run HTC Calibration, and delete ts-calibration.
I guess you could also compare calibration_screen to ts-calibration and if there are differences (and calibration_screen is valid) have ts-calibration overwritten, removing the need to delete it!
I am assuming that before calibration or having ts-calibration written to it that calibration_screen has the value 0,0,0,0,0,0,0,0,0,0 but it could also be 0 or empty i don't know really and am probably wrong!
Also for GBX0C /data/ would have to be /sdcard/
One major problem with that plan:
/sys/ isn't a real filesystem.
It's a virtual file system, like /proc/, created programmatically by kernel drivers. It's not stored anywhere.
That boot script is writing the node because that's the only way to get the data into the kernel. If you don't do that, the calibration gets purged (or more accurately, not initialized) every boot.
That's why I proposed a bind-mount: make an access to one place in the filesystem affect another place. Though I realize another problem with that... The driver doesn't read from the filesystem! You have to actually write to the node to get the data into the driver. So that busts that plan.
It might be theoretically possible to modify the kernel driver to signal a userspace process to copy that data out, but... I don't know what would go into that, or even if it's ideal.
I have been using the latest kernel, 3.4 with a new build of GBX0C and decided to re-calibrate my screen:
Strange.... When I went looking for calibration_points in /sys/devices/virtual/input/input3/ it wasn't there, it had moved to /sys/devices/virtual/input/input2/
Before I edit the first post can anyone who is using the 3.4 linux kernel confirm this, please?
I can confirm that with the 3.3 kernel, mine is in input2, not input3
where to copy? does not have memory card
karelkopp said:
where to copy? does not have memory card
Click to expand...
Click to collapse
What does not have a memory card? The RHOD certainly has a slot for one...
Edit - I just realized why your question is so poorly worded. You're running NAND, and this thread assumes you're on a SD build.
I responded to you here.
I recently started working on a Android based Car solution and decided to buy the MK802 units. My car used to have a Windows based PC, so I already have VGA touchscreens installed. I didnt want to replace the screens, so I bought a HDMI to VGA converter and the MK802.
I plugged the touchscreen into the MK802, assuming it wouldnt do anything. But sure enough, it works. Problem is the calibration is off and up and down are reversed. So say I tap the bottom of the screen, the mouse pointer appears on the top of the screen and vis versa. My understanding (Im very new to this) is that you have to be rooted, which is the way these devices come.
So my question is, will this calibration tool work? I know most Androids use a multi-touch screen. Mine are 4-wire touch panels. Also, what do I have to look for and edit to get Up to Up and Down to Down?
Thanks in advance!
hijackzx1 said:
I recently started working on a Android based Car solution and decided to buy the MK802 units. My car used to have a Windows based PC, so I already have VGA touchscreens installed. I didnt want to replace the screens, so I bought a HDMI to VGA converter and the MK802.
I plugged the touchscreen into the MK802, assuming it wouldnt do anything. But sure enough, it works. Problem is the calibration is off and up and down are reversed. So say I tap the bottom of the screen, the mouse pointer appears on the top of the screen and vis versa. My understanding (Im very new to this) is that you have to be rooted, which is the way these devices come.
So my question is, will this calibration tool work? I know most Androids use a multi-touch screen. Mine are 4-wire touch panels. Also, what do I have to look for and edit to get Up to Up and Down to Down?
Thanks in advance!
Click to expand...
Click to collapse
This tool was made for HTC phones. You will need to find the group for your device to get support for it.
Calibration problem
Hello,
I am not able to calibrate screen on htc touch pro2 sprint modem (T7380) PocketPC
there is a software problem due to which i had to reset factory restore button inside handset ,and restarted device
but it stuck on calibrate option ,continuous prompt to press all 4 side and centre ,even though i had done multiple time
but no further progress ,would like to know how to come out from this problem
now the handset is completely not starting ...i am on calibrate mode screen.
please suggest any solution .
syedwasi said:
Hello,
I am not able to calibrate screen on htc touch pro2 sprint modem (T7380) PocketPC
there is a software problem due to which i had to reset factory restore button inside handset ,and restarted device
but it stuck on calibrate option ,continuous prompt to press all 4 side and centre ,even though i had done multiple time
but no further progress ,would like to know how to come out from this problem
now the handset is completely not starting ...i am on calibrate mode screen.
please suggest any solution .
Click to expand...
Click to collapse
It sounds like you are having this issue with a Windows Mobile ROM and this thread is dedicated to Android on the Touch Pro2. However...
OFF TOPIC:
I had a similar problem with my old Acer M900 and the solution was to put an empty text file in the root (no folders) of your SD card and rename it welcome.not and this will bypass the screen calibration on your first boot. I was then able to successfully run the calibration afterwards from the settings menu. Here, to make it easy I attached the file here:View attachment welcome.zip. Simply unzip the file and place the file welcome.not on your storage card.
Caldair said:
I take no credit for any of this, I have just put together things I have found on various threads.
As you all know the touch screen calibration that runs at boot does not work with any of the newer kernels as you cannot see some of the cross hairs to tap. I have personally NEVER been able to produce my own accurate ts-calibration file and have been using an ancient one that I downloaded back in the early days of FRX (thank you arrrghhh). Hopefully you have a somewhat functional ts-calibration file as you need to carry out this procedure from within Android. Here we go... (it's easy)
1. Download HtcCalibrate_WVGA.apk, thanks to lukas.pce, attached to first post here http://forum.xda-developers.com/showthread.php?t=1457343 to your device.
2. Install HtcCalibrate_WVGA.apk
3. Run HTC Calibrate and follow the instructions, tapping all the points (I used a toothpick for added accuracy)
4. When complete the app will report 'Calibration complete', tap 'Done'. Your screen should now be accurately calibrated for this session. Test to make sure it is working correctly before proceding to next step.
5. Now to get the calibration data to stick after reboot: Open your file explorer (MUST HAVE ROOT ACCESS; I use ES File Explorer with Menu>Settings>'Up to Root' checked) and navigate to /sys/devices/virtual/input/input3/ there you should see a file named calibration_points.
...
..
**Nand users see this (thanks wizardnight!):
Done. Your phone should now boot with the calibration data you created.
Click to expand...
Click to collapse
I have had a little bit of an alingment problem with my screen on my TP2. The NAND GBX works great so far. The only small but nevertheless important issue is finding a way to calibrate the screen and all Google searches lead back to the same forum post here , which has many files in the zip but NO apk inside.
Anyway, if anybody has any information of where to find an apk that will work, or maybe information on how to use the included files in the above mentioned link would be much appreciated.
My sincere thanks to all the developers that make all this modding possible, thank you all.
isruco said:
I have had a little bit of an alingment problem with my screen on my TP2. The NAND GBX works great so far. The only small but nevertheless important issue is finding a way to calibrate the screen and all Google searches lead back to the same forum post here , which has many files in the zip but NO apk inside.
Anyway, if anybody has any information of where to find an apk that will work, or maybe information on how to use the included files in the above mentioned link would be much appreciated.
My sincere thanks to all the developers that make all this modding possible, thank you all.
Click to expand...
Click to collapse
I just redownloaded the WVGA calibration from the link you refered to here:
[URL="http://forum.xda-developers.com/showthread.php?t=1457343"]http://forum.xda-developers.com/showthread.php?t=1457343
And the file seems to be intact and unchanged.
Those attached files on said thread ARE apk's already, they don't need to be extracted, just installed on your TP2.:good: Hope that helps!
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
BornReady_ said:
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
Click to expand...
Click to collapse
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
nmyshkin said:
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
Click to expand...
Click to collapse
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
BornReady_ said:
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
Click to expand...
Click to collapse
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
nmyshkin said:
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
Click to expand...
Click to collapse
Yes, I booted with the power cable connected, I tried on being connected to the laptop and power wall as well. I also held down the N button, which is why I got to the Boot Menu.
Bear with me
Are you sure you got the SD card version of TWRP?
Yes, 100% sure.
BornReady_ said:
Yes, 100% sure.
Click to expand...
Click to collapse
Well that was interesting! We're "live" apparently
I want to help but I'm not digixmax... I'll bet he has an idea. Wait for him to get back to you while I rummage around.
Lol, thanks for the help anyways though. I will have to wait for digixmax.
Wow, everytime you mention digixmax, he replies. He just privated messaged me in return.
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
I'm sorry, I should have been more precise. I don't know if it will help, but this is the TWRP recovery image I used successfully when I tried this process. That's v. 2.8.6.0
digixmax said:
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
Click to expand...
Click to collapse
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
nmyshkin said:
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
Click to expand...
Click to collapse
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
BornReady_ said:
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
Click to expand...
Click to collapse
I've already shut down my computer for the night. I'll have a look at the size that an image of the card would be. Maybe that's the easiest way if there's room in my dropbox. If you've read through the CM11/12 thread you know I ran into problems and if you were to look at the CM10 thread you'd find me floundering around there also, so I know how frustrating it can be. And then suddenly it just works.
I'll let you know tomorrow.
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
digixmax said:
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
Click to expand...
Click to collapse
You are totally correct. I enabled Windows Explorer to display file-name extension and the TWRP recovery file turned out as "recovery.img.img" I am going to try it out now and reply with if it works or not.
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
BornReady_ said:
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
Click to expand...
Click to collapse
Is flashing_boot file on your SD card correctly named "flashing_boot.img", and not "flashing_boot.img.img"?