Related
OUT OF DATE USE THE ONE CLICK 1.85 ROOT TOOL IN THE FORUMS
As the ROM chefs go to work, we want to be sure that we are ready to flash the ROMs when they come to be available! This guide will help you set up your phone so that you can flash custom ROMs.
After this process you will have a phone on the latest firmware (1.85 at the moment) with bootloader unlock, rooted, and busybox installed.
This guide assumes you are on a root friendly firmware (as of now, it is firmwares 1.82.502.3 and below).
This is really going to be done in a four step process. First we need to root the device in order to access the place where the CID is stored so that we can change it and get unlocked. After changing the CID, we can unlock via htcdev.com. Then we can go on to installing a custom recovery and finally rooting!
From there I will give you some tips on installing ROMs.
NOTE: THIS PROCESS IS EXTREMELY DANGEROUS. IT MAY BE A BIT CONFUSING. READ OVER THE STEPS BEFORE STARTING. IF YOU DO NOT THINK YOU WANT TO RISK YOUR DEVICE BECOMING A BRICK THEN DO NOT ATTEMPT THIS. THIS VERY EASILY COULD RUIN YOUR DEVICE.
BACKUP EVERYTHING BEFORE STARTING AS EVERYTHING ON YOUR DEVICE WILL PROBABLY BE WIPED.
I, XDA, AND THE ORIGINAL TOOL CREATORS DO NOT TAKE RESPONSIBILITY FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. IT IS SOLELY YOUR RESPONSIBILITY FOR WHAT YOU DO TO YOUR DEVICE.
Click to expand...
Click to collapse
Your warranty will be void if you unlock the bootloader. If you just root though then you can return to 100% stock by running the RUU.
This guide is for Windows only at the moment though I will try to post Mac and Linux guides at some point.
ORIGINAL TOOL THREADS:
One Click Root for 1.82 and below: http://forum.xda-developers.com/showthread.php?t=1644167
Spoof CID Script: http://forum.xda-developers.com/showthread.php?t=1672284
I will try to keep this as up to date as possible! Taking a visit to the index of the development forums (http://forum.xda-developers.com/showthread.php?t=1671237) is also a good idea!
Last Updated: 5/28/12
0. Getting the prerequisites:
Download the package at the bottom of the first post to get started.
Extract the package somewhere you will remember (like on your desktop).
Connect your device via USB and make sure you have USB Debugging enabled under settings.
Click to expand...
Click to collapse
1. Root your device
1. Open the folder you downloaded and navigate to the "root" directory.
2. Double click on the root-windows.bat file
3. Let the root run and do not touch your device. It will reboot several times- do not touch it or you may brick your device. Just let it do its thing and eventually after around 3 minutes you will have a rooted device in your hand.
Click to expand...
Click to collapse
2. Get the unlock token
In order to unlock the bootloader we will need to change a value called the CID. This will allow the htcdev.com site to unlock our phones.
1. Go to the downloaded folder and go to the "change_cid" folder.
2. Click on the "Spoof-CID.bat" file. Follow the instructions. Your CID will change from CWS__001 (stock AT&T CID) to 11111111 (called "SuperCID," will allow you to flash anything)
3. Log in to htcdev and go here: http://www.htcdev.com/bootloader/unlock-instructions (NOTE: This skips the agreements you need to click through as some of the buttons on their website are wonky. Doing this assumes you agree to their policies that are listed there)
4. Follow the instructions very carefully (they are written very well) untill the point where you get the file "Unlock_code.bin" via email. Stop there.
5. You should now have the file for bootloader unlock. MAKE SURE TO SAVE THAT FILE "Unlock_code.bin" TO THE "generic" FOLDER IN THE PACKAGE YOU DOWNLOADED! YOU WILL NEED IT LATER.
Click to expand...
Click to collapse
3. Run the RUU to update to latest firmware
1. Download the latest RUU from the xda forums (should be an .exe file)
Currently it is version 1.85.502.3 and you can download it here:
http://briefmobile.com/download-htc-one-x-att-1-85-update
2. Follow its instructions very carefully. It will take approximately 20 minutes to complete. BE PATIENT. IF YOU UNPLUG YOUR PHONE HERE YOU WILL GET A BRICK.
3. Let your phone reboot and go through initial setup again
Click to expand...
Click to collapse
4. Unlock your bootloader using Unlock Token
1. Navigate to the "generic" folder in cmd (you should have added the Unlock_code.bin file to this folder already) and plug your phone in in fastboot mode. To do this, first shut off your phone. Wait for it to turn off. Then hold the volume down button. Press the power button for 3 seconds while still holding the volume down key. Let go of the power button but keep holding the volume down button untill you see a white screen with a bunch of small text on it. Use the volume up and down keys and the power button to select the FASTBOOT option. Plug your phone into your computer. Then wait for the FASTBOOT text to turn into FASTBOOT USB.
2. Type the following into cmd on your computer:
fastboot flash unlocktoken Unlock_code.bin
NOTE: This step might take quite a few tries. For some it works on the first time. For others, it may take around 20 times. Just keep typing in the command until you get a sucessful flash. We aren't sure why it does this at the moment but just keep trying and don't give up.
3. Use the volume keys to say that you do want to unlock your bootloader and wait for reboot
4. Bootloader should be unlocked! Congrats, most of the grunt work is done! Go to Settings - Developer Options - Enable USB Debugging. This will allow us to continue
5. Re-set up phone and enable USB debugging again
Click to expand...
Click to collapse
5. Install a custom recovery so that we can gain root access
1. Currently there are two recovery options: ClockWorkMod Touch and TWRP (TeamWinRecoveryProject). Both are pretty much the same as they both use touch input but TWRP does have some other nice features like a built in file browser and more. It is also more touch optimized. ClockWorkMod is more "old school" and I personally feel more comfortable using it, but using TWRP is fine as well. It doesn't really matter which recovery your choose, both are good choices. Download whichever one you want below:
CWM Touch: http://forum.xda-developers.com/showthread.php?t=1677304
TWRP: http://forum.xda-developers.com/showthread.php?t=1677447
2. Drag the .img recovery file you just downloaded into the "generic" folder
3. Connect your phone via fastboot
4. Type the following:
fastboot flash recovery <insert name of recovery .img file here>
Replace the stuff between the <> with the name of the file you just downloaded
5. Wait for your device to reboot. Then type into cmd which is cd'ed to the "generic" folder:
adb reboot recovery
6. Make sure your recovery works as soon as it is done loading and then press "reboot system"
7. Follow its instructions
Click to expand...
Click to collapse
6. Root your system
1. Connect your phone as a "Disk Drive" and drag the "root.zip" file in the "root" folder to your phone's memory
2. Reboot into recovery with the adb command (adb reboot recovery)
3. Go to install zip from sdcard and navigate to the zip file you downloaded. Say "yes" and watch it flash
4. Reboot system now
5. Go to the play store and download any app that has "Busybox installer" in its name (the one by JRummy16 works good I believe)
Click to expand...
Click to collapse
If all goes well, you should be sitting at an AT&T HTC One X which is on the latest RUU leaked firmware (1.85.502.3 at this moment), rooted, busyboxed, and unlocked.
Congrats!
If you want to flash any ROMs, download the .zip file of the ROM, place it on your phones memory, and then install the zip like you did to the root.zip file.
Enjoy your AT&T HTC One X!
CREDITS:
kennethpenn: For initial root, getting all the RUUs from the "source" and for giving the HTC One X's situation prime press appearance on his website, BriefMobile.com
grankin01: For finding out how to edit the CID originally
designgears: For creating the One Click Super CID tool for bootloader unlock
paulobrien: For porting CWM Touch to our device
sk08: For leading the way in terms of MODs and organizing an S-OFF thread to get this thing fully ours
JSLEnterprises: For initially being there to help organize a bootloader unlock
Team Nocturnal: For their awesome ROM
Click to expand...
Click to collapse
If you want to thank or donate to someone, please do not do so to me. The people above are the ones that deserve the thanks and the donations to encourage them to keep doing the fantastic work they have been doing! I'm just a high school student
Some common terminology:
Deoxdexed: OEMs package their apps with .odex files because they are more optimized for your device. However, this makes the file uneditable by developers and things like mods cannot be used with odexed ROMs. A ROM with "deodexed" as a feature means it is easier to use mods with that ROM
Busybox: A collection of linux tools that are helpful for flashing ROMs and doing other basic Android tasks
RUU: ROM Update Utility, made by HTC, completely reflashes device firmware, useful if you get bricks. Only for Windows.
Root: Allows you to edit system level files
S-OFF: (currently unattainable) Security-OFF, it is a "feature" in HTC phones that allows us to modify almost any part of your system.
Unlocked Bootloader: Allows us to flash custom images to the device.
Click to expand...
Click to collapse
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
Wasnt sure, there are still a few people asking how to do it since it is a bit complicated with the 1.85 update breaking root so I just compiled everything into a master one.
And yeah, I use a lot of the scripts in the package I put for download.
Anyway, mods do what you think with this thread! And this might be in the wrong section, wasnt sure if it goes in general or development.
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
As I agree with you, a "one stop shop" that can be pointed out to for the noobs who got their mommy's to buy them their cool phone should at least keep the redundant questions to a minimum.
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Locked boot loader yes.
Root for cwm no.
Sent from my HTC One X using xda premium
squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
rohan32 said:
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
Click to expand...
Click to collapse
He put his foot in his mouth, apology should be coming oh and Good job man, Good job. Thanks for the work, this should be a sticky.
This is a great write up and would have been extremely helpful last night. I will admit I have done a lot of reading before I unlocked the bootloader and updated to 1.85, but it was still very confusing at some points. The htcdev site actually gave me the most trouble because I didn't realize most of the steps were completed and I could skip all the way to entering the token and the site was simply used for entering the token and getting the unlock file.
And yes, I almost said the same thing about the relock step. I had to read it twice to realize you didn't unlock yet. That's another thing that confused me last night was unlocking/relocking immediately.
I think this should be a sticky and all the other tutorials and such should be deleted. This is a perfect summary IMO and will use it when I unlock my friends one x
Sent from my HTC One X
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
designgears said:
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
Click to expand...
Click to collapse
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Red5 said:
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Click to expand...
Click to collapse
Sure thing, I will add to the original post for the links.
Also I will try to keep this updated, but yeah I might not catch all the updates
Thank you so much Rohan! Really appreciate it! Took me about 4 hours to get this done but it was worth it. Now to install cleanrom. Thanks again. This is my first time doing something like this.
Duse ijuat saw this and I'm going to do this and flash clean from when I get home and I read through this I honestly love you for doing this it helps more than you think thanks a lot
Deffinitlet should be stickied
Sent from my HTC One X using XDA
These are the best instructions! Wish i had them when all this shenanigans started. Thx
ethantarheels123 said:
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
Click to expand...
Click to collapse
I agree. This guide is very helpful for me. I consider myself to be fairly computer literate and have flashed ROMs on previous phones, but I am a complete n00b to android and linux. Looking around some of the other threads -- it appears to me that there are many people who could have much confusion resolved by reading this. Thanks for the thread.
-- Jon
Not quite sure what's going on with my update...
I'm using the exe that updates the RUU and it gets stuck on the "sending to phone" step. Reboots the bootloader once, gets stuck again (as far as I can tell , nothing is ever sent) and then gives me an error telling me "The ROM Update Utility cannot update your Android Phone. Please get the correct ROM Update Utility and try again"
i've got the correct drivers installed (was having some trouble related to that a couple days ago but have since figured it all out ) would it be better to just do the update manually? (On my evo you just change the update file to Update.zip and it automatically installs it for you when you boot into bootloader)
maybe I'll have to look into it further, but just curious if anyone's run into this issue or figured out how to get past it as of yet...
Edit: Just an update- I'm betting its because I forgot to relock my bootloader before updating. So anyone who's already completed SOME of the steps in the second post here, make sure you relock your bootloader if you haven't already done so.
Edit1.5: This assumption was correct and the bootloader is now unlocked.
Edit 2- Almost done here... Busybox wont install. Tried two different apps, neither one worked. No indication as to why (got very vague error messages to the effect of "busybox was not installed")
Edit 3- FIXED- Ok, figured it out. As far as I can tell, the process should be Root first, THEN install busybox. It doesn't work without root privelages (at least that was my experience here)
Hey guys this is my first post here on the forums so go easy on me
So I bought this phone a couple weeks ago off of eBay. The phone was already rooted when I bought it and it is my first experience with a rooted android. I've been doing my best to learn everything I can about all the different things I can do with a rooted phone and I've learned a lot so far.
One thing that's stumping me though is that my phone will randomly just not turn back on after I lock the screen. This happens very randomly and happened to me last night which meant that my alarm didn't go off and I was late to work.
I've tried searching the forum but I can't seem to find a cause or a fix for this problem. If there is any information that I neglected to include, I apologize and will be happy to include that in another post.
Anything that y'all could do to help me would be greatly appreciated!
Sent from my Nexus S using xda app-developers app
it's happen for me too. JB 4.1 stock rom
Maybe try another kernel. I use AIR and.have heard great things bout MATR1X and Marmite as far as stability.
I would back up your apps and do a wipe and reinstall your ROM. For back ups and system tweakage I.use Android Tuner.
I guess we should know your current set up to help you the best. Please tell us what ROM Kernel combo you ate running.and I will do my best to offer suggestions as I'm sure the test.of the community.here will.
Sent from my phone using my thumbs and a keyboard
happen to me twice in the same day on stock unrooted JB. since then, nothing
Nexism said:
Maybe try another kernel. I use AIR and.have heard great things bout MATR1X and Marmite as far as stability.
I would back up your apps and do a wipe and reinstall your ROM. For back ups and system tweakage I.use Android Tuner.
I guess we should know your current set up to help you the best. Please tell us what ROM Kernel combo you ate running.and I will do my best to offer suggestions as I'm sure the test.of the community.here will.
Sent from my phone using my thumbs and a keyboard
Click to expand...
Click to collapse
Ok I think that the screenshot I attached is what you are asking for. If it isn't please let me know what else you need to know. Like I said earlier, I bought the phone pre-rooted so I'm not very sure how use another kernel or flash a different ROM. The whole process seems a little intimidating to me but I would be willing to try it out. I just really don't want to brick my phone because I don't know what I'm doing haha.
You're running a build based of the SDK.
Simply put. Get that crap off of your phone. Flash official stock , a custom ROM or whatever but that needs to go
albundy2010 said:
You're running a build based of the SDK.
Simply put. Get that crap off of your phone. Flash official stock , a custom ROM or whatever but that needs to go
Click to expand...
Click to collapse
Oh, well that makes me feel great about my purchase
Would you mind telling me what the best way to do this is, or directing me to instructions how to do it? I'm really new to this and I would hate to ruin my phone because of my inexperience.
I really appreciate the help.
NikoStone said:
Ok I think that the screenshot I attached is what you are asking for. If it isn't please let me know what else you need to know. Like I said earlier, I bought the phone pre-rooted so I'm not very sure how use another kernel or flash a different ROM. The whole process seems a little intimidating to me but I would be willing to try it out. I just really don't want to brick my phone because I don't know what I'm doing haha.
Click to expand...
Click to collapse
follow this thread to update to the official stock jellybean
http://forum.xda-developers.com/showthread.php?t=1736645
Cascabreu said:
follow this thread to update to the official stock jellybean
http://forum.xda-developers.com/showthread.php?t=1736645
Click to expand...
Click to collapse
Ok, thanks. Is this the latest update? Please forgive me for the complete noob questions that follow:
1. I've downloaded the file, but how do I open it and perform the update?
2. Will updating it this way cause me to lose root?
Well first off you should be posting in the Q&A section.
Use fastboot to install factory images. You can download fastboot and the driver for it from the links in my signature.
1. Download the factory image for your device and extract all the image files in it, put them in the folder where fastboot.exe is located.
2. Hold shift + right click on the folder where fastboot.exe is located, choose "Open command window here" (if you're using Windows 7)
3. Boot the phone into bootloader/fastboot mode and connect it to the computer. (While the phone is off, hold VOL+ and POWER).
4. The computer should now ask for the driver, point it to the location of the drivers you downloaded.
5. Open up the file "flash-all.sh" that you extracted along with the factory images with a text editor, it will tell you the commands you'll need to type to install the images:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jro03l.zip
I can't remember if this process will wipe your entire internal storage or not.
Now if you want to root, try this: http://forum.xda-developers.com/showthread.php?t=1479831, although there are other ways to root.
Or you can follow these instructions to install Clockworkmod and using it to flash root: http://dottech.org/25412/how-to-root-nexus-s/.
eksasol said:
Well first off you should be posting in the Q&A section.
Use fastboot to install factory images. You can download fastboot and the driver for it from the links in my signature.
1. Download the factory image for your device and extract all the image files in it, put them in the folder where fastboot.exe is located.
2. Hold shift + right click on the folder where fastboot.exe is located, choose "Open command window here" (if you're using Windows 7)
3. Boot the phone into bootloader/fastboot mode and connect it to the computer. (While the phone is off, hold VOL+ and POWER).
4. The computer should now ask for the driver, point it to the location of the drivers you downloaded.
5. Open up the file "flash-all.sh" that you extracted along with the factory images with a text editor, it will tell you the commands you'll need to type to install the images:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jro03l.zip
I can't remember if this process will wipe your entire internal storage or not.
Now if you want to root, try this: http://forum.xda-developers.com/showthread.php?t=1479831, although there are other ways to root.
Or you can follow these instructions to install Clockworkmod and using it to flash root: http://dottech.org/25412/how-to-root-nexus-s/.
Click to expand...
Click to collapse
I appreciate the extensive list of instructions you provided. I tried my best to follow them but I couldn't quite figure out what I was doing wrong. I decided to try to install a custom ROM instead and was able to install cm9 pretty easily. Will this be sufficient to remove the aforementioned problem I was having?
If your already rooted then you don't need to go through a lot of that even.though it was a good walkthrough. If you flashed a new ROM then.you have.some sort of recovery in place. As long as you do a full wipe to get the previous owners garbage off of there and then flash a new ROM like CM9 then you should be golden the new ROM will come with it's own kernel so you don't need to start learning about those until you want to.
If I may make a suggestion, give AOKP Build 4 a try the ROM you chose is good but is using old code (ICS) If you just got a new phone why not put the latest on it.
Keep me (us) posted as we the reason a lot of us belong to this forum is to offer any help we can....AOKP4 you won't regret it.
Sent from my phone using my thumbs and a keyboard
That works too, you can flash the stock roms here (using CWM) or stay with the custom rom: http://forum.xda-developers.com/showthread.php?t=1843301
Nexism said:
If your already rooted then you don't need to go through a lot of that even.though it was a good walkthrough. If you flashed a new ROM then.you have.some sort of recovery in place. As long as you do a full wipe to get the previous owners garbage off of there and then flash a new ROM like CM9 then you should be golden the new ROM will come with it's own kernel so you don't need to start learning about those until you want to.
If I may make a suggestion, give AOKP Build 4 a try the ROM you chose is good but is using old code (ICS) If you just got a new phone why not put the latest on it.
Keep me (us) posted as we the reason a lot of us belong to this forum is to offer any help we can....AOKP4 you won't regret it.
Sent from my phone using my thumbs and a keyboard
Click to expand...
Click to collapse
First I want to say thank you to everybody for all the help so far. :highfive: I'm still learning but I am slowly figuring all of this out.
Nexism, I would be interested in trying AOKP build 4 if you wouldn't mind explaining the easiest way to do it or point me somewhere that can explain it to me. I don't know what all goes into flashing a new ROM and I don't want to forget something that will mess up my data or my battery life.
Here is the AOKP thread. Its located in the general section.
http://forum.xda-developers.com/showthread.php?t=1645400
As far as flashing goes...
Download the ROM from the above thread
Download a good app backup app (I use Android Tuner, it seems like everyone else uses Titanium Backup or ROMToolbox all have free versions only thing you'll miss is batch restore)
Back up your $hit
Boot I recovery (phone off, hold vol up while powering phone on) then scroll to recovery
(At this point opinions differ a bit) I go to mounts and storage and format the following data, cache, system, then boot then back out to the main menu and wipe all factory reset (I'm kind of a neat freak just.like to make sure I'm always starting with a clean slate)
Then install your.ROM and Gapps after a few min main recovery menu will come up
Select reboot
Go through the norm set up
Re-install backup app
Restore your apps
Then play around with all.the new features on your Nexus
Sorry if this is too basic of a walkthrough no offense if so. You can PM me if you need more detail. Good luck, happy flashing.
Sent from my phone using my thumbs and a keyboard
Nexism said:
Here is the AOKP thread. Its located in the general section.
http://forum.xda-developers.com/showthread.php?t=1645400
As far as flashing goes...
Download the ROM from the above thread
Download a good app backup app (I use Android Tuner, it seems like everyone else uses Titanium Backup or ROMToolbox all have free versions only thing you'll miss is batch restore)
Back up your $hit
Boot I recovery (phone off, hold vol up while powering phone on) then scroll to recovery
(At this point opinions differ a bit) I go to mounts and storage and format the following data, cache, system, then boot then back out to the main menu and wipe all factory reset (I'm kind of a neat freak just.like to make sure I'm always starting with a clean slate)
Then install your.ROM and Gapps after a few min main recovery menu will come up
Select reboot
Go through the norm set up
Re-install backup app
Restore your apps
Then play around with all.the new features on your Nexus
Sorry if this is too basic of a walkthrough no offense if so. You can PM me if you need more detail. Good luck, happy flashing.
Sent from my phone using my thumbs and a keyboard
Click to expand...
Click to collapse
Awesome, thanks man.
It was exactly what I needed to know - not too basic. I flashed it and now I'm checking it out. Is there any reason I would need to use a custom kernel for anything?
No, only i u find it slow as it is now. If u want a custom kernel go for matr1x one
Sent from my Nexus S using xda app-developers app
Glad to here your Nexus is doing well.
Now that you have a good build make a backup (in recovery) so you will always have a working configuration to go back to then experiment all you want. I may get corrected on this but as long as I have a backup and access to recovery mode I know that the chances of me bricking my phone is slim to none. So I am a flash happy fool. I try everything new when it comes out.
Get comfortable with your new ROM and flashing in general and as you see a need try different stuff out.
I use a custom kernel because I use the on screen navbar and I like to turn off the hardware key backlight. You also have control over CPU min/max Frequency,governors, and I/o schedulers as well as some extra tweak options. If you're like me the more you learn the more you'll flash.
Check out NSTools it is one of the must have apps for our phones.
Again, I am available for anymore help I can.offer.
Sent from my phone using my thumbs and a keyboard
Hi guys.
I posted a thread the other day asking for help with superoneclick, I have since taken on board the advice given, and scrapped the superoneclick route. Instead I followed this guide http://forum.xda-developers.com/showthread.php?t=1525100 , which was going really well, up to the point where I go into recovery, and try to install from sd card. I tried the method with the reaper v2.1, and now also with blind roms pacman rom, and neither show up when I go to install from the sd card. I downloaded the roms, and unzipped them in the sd card, not in a file, just into the card itself, they then show up, but only as "boot" and not as "boot.img" as I'm sure it should say, they also still say they are a "winzip file", which surely if they were unzipped, they wouldn't say this?
Seemingly everything else I did is working as it should, I have an unlocked bootloader, I have enabled adb and fastboot, it's just the putting the rom on the sd card and then locating it when I go into EXT4.
Can anyone please shed some light on to what I may be doing wrong?
4) Open the rom (.zip file) you downloaded in step 1 and put the ''boot.img'' file in ''C:\android-tools'' seems to be the part where it all goes wrong?
Thanks for now.
Geez, so many things done wrong.
I hope someone will have patience to explain all of them to you, I'll just tell you 2 things:
1) Guides assume that people can tell file names from file extensions, and know how to see both.
2) I highly suggest you leave your phone alone. You don't have enough knowledge to safely proceed, and definitely don't have enough knowledge to pull yourself out of trouble, which you'll eventually get into.
Jack_R1 said:
Geez, so many things done wrong.
I hope someone will have patience to explain all of them to you, I'll just tell you 2 things:
1) Guides assume that people can tell file names from file extensions, and know how to see both.
2) I highly suggest you leave your phone alone. You don't have enough knowledge to safely proceed, and definitely don't have enough knowledge to pull yourself out of trouble, which you'll eventually get into.
Click to expand...
Click to collapse
I appreciate any feedback or criticism, as long as the end result is me figuring out how to root my phone.
I THOUGHT I'd followed the guide pretty closely. I'm inexperienced,yes, buy so is everyone when they try doing something for the first time. I've been reading all I can to help give myself some much needed knowledge.
But guess I'm doing something not right, I'd very much appreciate someone being uber patient with me,and showing/telling me what it is I'm doing wrong.
Thank you.
What needs to be on the sd card is the zip file of the rom, not unzipped or anything. Then you can install the rom from recovery, assuming you did all the other steps right.
teadrinker said:
What needs to be on the sd card is the zip file of the rom, not unzipped or anything. Then you can install the rom from recovery, assuming you did all the other steps right.
Click to expand...
Click to collapse
He has unlocked bootloader, which means - telling him how to install it without explaining what to do after (flashing boot.img) is a great idea - if you want to get his phone not to boot anymore.
Jack_R1 said:
He has unlocked bootloader, which means - telling him how to install it without explaining what to do after (flashing boot.img) is a great idea - if you want to get his phone not to boot anymore.
Click to expand...
Click to collapse
^^^^ Which will be why my phone now wont go past the white screen displaying HTC.
But I can still boot into 4EXT recovery, but when I do the backup/restore, it does nothing, just comes back to 4ext, or if I reboot, the white htc screen.
As it will go into 4EXT, it's not bricked, I guess it cant find the stock rom in the system to restore back to.
Not sure where to go now....Ebay for a replacement perhaps :silly:
nixon. said:
^^^^ Which will be why my phone now wont go past the white screen displaying HTC.
But I can still boot into 4EXT recovery, but when I do the backup/restore, it does nothing, just comes back to 4ext, or if I reboot, the white htc screen.
As it will go into 4EXT, it's not bricked, I guess it cant find the stock rom in the system to restore back to.
Not sure where to go now....Ebay for a replacement perhaps :silly:
Click to expand...
Click to collapse
Sounds like if your tire goes flat to trash the whole car for parts lol
Jack_R1 said:
He has unlocked bootloader, which means - telling him how to install it without explaining what to do after (flashing boot.img) is a great idea - if you want to get his phone not to boot anymore.
Click to expand...
Click to collapse
He was following a guide which included flashing boot.img, so I (perhaps over optimistic) assumed the right boot.img had been flashed.
---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------
nixon. said:
^^^^ Which will be why my phone now wont go past the white screen displaying HTC.
But I can still boot into 4EXT recovery, but when I do the backup/restore, it does nothing, just comes back to 4ext, or if I reboot, the white htc screen.
As it will go into 4EXT, it's not bricked, I guess it cant find the stock rom in the system to restore back to.
Not sure where to go now....Ebay for a replacement perhaps :silly:
Click to expand...
Click to collapse
Yes your problem now is that you haven't flashed the boot.img from the rom you've installed.
deleted
nixon. said:
Hi guys.
I posted a thread the other day asking for help with superoneclick, I have since taken on board the advice given, and scrapped the superoneclick route. Instead I followed this guide http://forum.xda-developers.com/showthread.php?t=1525100 , which was going really well, up to the point where I go into recovery, and try to install from sd card. I tried the method with the reaper v2.1, and now also with blind roms pacman rom, and neither show up when I go to install from the sd card. I downloaded the roms, and unzipped them in the sd card, not in a file, just into the card itself, they then show up, but only as "boot" and not as "boot.img" as I'm sure it should say, they also still say they are a "winzip file", which surely if they were unzipped, they wouldn't say this?
Seemingly everything else I did is working as it should, I have an unlocked bootloader, I have enabled adb and fastboot, it's just the putting the rom on the sd card and then locating it when I go into EXT4.
Can anyone please shed some light on to what I may be doing wrong?
4) Open the rom (.zip file) you downloaded in step 1 and put the ''boot.img'' file in ''C:\android-tools'' seems to be the part where it all goes wrong?
Thanks for now.
Click to expand...
Click to collapse
In step 1 you copied the ROM zip file from your PC to your phone.
In step 4, you should open the PC zip file, not the file on the phone's sdcard. X(
That's the only thing you did incorrectly!
Sent from my Nexus 7
BillGoss said:
In step 1 you copied the ROM zip file from your PC to your phone.
In step 4, you should open the PC zip file, not the file on the phone's sdcard. X(
That's the only thing you did incorrectly!
Sent from my Nexus 7
Click to expand...
Click to collapse
^^^ thanked
Thank you for pointing out my mistake, now at least I realise what I was doing wrong, although now my phone is beyond my own repair, I shall have to see if I can send it off somewhere to get fixed.
Thanks again
nixon. said:
^^^ thanked
Thank you for pointing out my mistake, now at least I realise what I was doing wrong, although now my phone is beyond my own repair, I shall have to see if I can send it off somewhere to get fixed.
Thanks again
Click to expand...
Click to collapse
Why is it beyond your repair? Have you flashed the boot.img from the ROM?
Exactly, just flash the boot.img from the rom you flashed and it should work fine.
And if "flashing boot.img" sounds too complicated, try googling "fastboot flash boot boot.img", and going to Youtube for tutorials.
Your mistakes that I referenced earlier weren't only unpacking the ROM - this wasn't the problematic part - but when you did unpack the ROM and didn't understand anything from the boot.img file you saw, it meant that you have no idea about files and extensions, which usually means that it would be a bad idea to expect you to be able to freely use command prompt without detailed directions (and the guides always assume some level of knowledge - some more, some less). If you were to follow a better guide, the one that gets you S-OFF, it wouldn't matter - but since you've unlocked the bootloader and forced yourself to have to flash boot.img by fastboot, I didn't count on a happy ending should you proceed. I hate to be right in these cases.
You need to learn several things:
1. What are file extensions and what do they mean (mostly for yourself, but also for further understanding of the issue).
2. How to enable your OS to show file extensions to you, so you can see them and understand what file you're looking at.
3. How to open command prompt (you already did that - when you unlocked. now you need to do it to communicate with the phone in the same way).
4. How to use fastboot to flash boot.img (kernel) from command prompt.
Not too complicated, but it would have been better to learn that in your free time while having a functional phone, rather than in a rush to bring a non-working phone back to life.
Good luck.
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
twtoned said:
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
Click to expand...
Click to collapse
Looking for one as well. I have not found one.
Recovery is actually preinstalled
I found this just tooling around. Use your favorite file browser, I used
Total commander. /system/vender/itson
The zip file is there. Hope this helps. (Rooted LG ls620)
Could you explain in a little better detail on what you mean Enigmatic177... I'm pulling my hair out Hehe
If anyone makes or finds a working recovery please post it.
Itson is a zip file that was installed after last update it has the basics to unlock the boot loader. I unpacked it used Rom toolbox pro rebooted to RECOVERY did regular reboot system upgraded.
A couple if bit mapp errors 11111. Then I basically flashed CWM.
Before you do this the partitions change from ext2-ext4. I'd advise
Backing them up.
LG Realm & exceed 2 TWRP recovery/fastboot files
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
TWRP recovery help L620 LG Realm
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
I think i know what seems to be the problem. I think i might have accidentally replaced the boot img with the twrp recovery img. i did not make a backup before this happened. is there anything i can do to make my phone boot up to its normal image? thanks
Nope. It is officially a paperweight and no one I know of has access to the stock ROM either.
Sent from my LGLS620 using XDA Premium 4 mobile app
Hey
Has anybody found a custom rom?
Finally. Easy as pie
Ok, I downloaded an image (w5c_twrp_bumped.img)
put that img on the root of my sd card
downloaded Rashr from the google play store
opened rashr and tapped 'recovery from storage', navigated to external sd and tapped the image and tapped
ýes please'
flashed it. after the flash the phone rebooted into the twrp recovery.
then just rebooted back into the system
worked perfectly.
im new here im not allowed to post outside links yet, just google "w5c_twrp_bumped.img" should take you to a link for a download of that recovery
i got twrp now as a custom recovery. on my lg realm.
That_One_Person760 said:
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
Click to expand...
Click to collapse
You have the bumped recovery so all i can say if u messed up is to flash a stock rom u can find on google i had to re flash mine a few times messing with root
right on, thanks for the info. I had no problems at all. it all fell in place like i was hoping. The Realm is the easiest device Iv ever rooted, flashed, and messed with. Well, as far as rooting and flashing a custom recovery. dunno bout roms though. Im sure its simple?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
OK, I grabbed and extracted this. I used Flashify to simply flash the recovery (w5c_twrp_bumped.img) and it works like a dream on my LG Realm.
OTOH, trying the same on an Exceed 2 gets me TWRP, but it cannot mount much of anything and the backup fails. After failing, it tells me "No OS found, continue?" I continue and get the message "Appears your device has no Root, install now?' I am absolutely certain I have root, or wouldn't even be able to run Flashify, so I continue and it simply boots into the OS just fine. Perhaps the readme isn't complete, as I see the following file in the extracted folder (resources.zip) with no explanation of why it's there. It "appears" to be a flash-able zip that installs "itson" (whatever THAT is). Note that the Realm has this in the /system/vendor/itson, yet the Exceed 2 doesn't.
Have you actually used this on an Exceed 2? And if so, what am I missing here?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
petermg said:
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
Click to expand...
Click to collapse
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
fathergweedo said:
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
Click to expand...
Click to collapse
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
petermg said:
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
Click to expand...
Click to collapse
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
fathergweedo said:
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
Click to expand...
Click to collapse
THANKS!!!! I'll make it a point to flash that to my mom's phone next time I get the chance!
I updated my rooted 32 gb nexus 5 to the latest 5.1.1. It was not easy and I ran into all sorts of hiccups that left me phoneless for a couple of days. ?
My wife also has a rooted 32 gb nexus 5 and needs to upgrade. I don't want to go through all the headaches I had with mine, so, can I safely transfer my nandroid to her sdcard and just restore it on hers? Will that work? Or is there something that is unique in each nexus 5 phone and nandroid?
Thanks.
No it won't work, certain parts will. The folders need to be the same name too. You'll probably have more issues trying to do it to be fair, What's not easy about just fastboot'ing img files? What android version is her phone currently on?
Sent from my Nexus 5 using Tapatalk
maybeme2 said:
I updated my rooted 32 gb nexus 5 to the latest 5.1.1. It was not easy and I ran into all sorts of hiccups that left me phoneless for a couple of days.
My wife also has a rooted 32 gb nexus 5 and needs to upgrade. I don't want to go through all the headaches I had with mine, so, can I safely transfer my nandroid to her sdcard and just restore it on hers? Will that work? Or is there something that is unique in each nexus 5 phone and nandroid?
Thanks.
Click to expand...
Click to collapse
I don't have 2 of the same model phone so I've never tried it but I don't see an issue other than attempting to restore a backed up EFS. Do not restore the EFS to a different phone.
What u need to do is grab urself a copy of the latest factory images from here https://developers.google.com/android/nexus/images?hl=en download it to ur PC, connect ur device, make sure u have ADB and Fastboot installed on ur PC first, then open a command promt and type
adb reboot bootloader
When the device reboots run the "flash_all.bat" command inside the downloaded stock image file and ur device should flash the image. If this process is too difficult, as it may be for some ppl, you can download Wugz Nexus Toolkit from XDA, follow all the steps it tells u too, and upgrade with that, as it has a step by step walkthrough, that should be it, if u need any further help just let me kno
Sent from my Nexus 6 using Tapatalk
The way to do it is simple enough. Problem is it doesn't always "work" as expected for everyone.
Example: I started by doing exactly what you said, but the flash-all command just stayed stuck on waiting for device no matter what I did to the phone.
So, I decided to go the step-by-step longer way. That gave me problems too. I don't remember what exactly but it included being stuck in a forever boot where the balls revolved forever, and some other problems I chose to forget. (boot loops, loss of sdcard space, etc.)
I did succeed in the end but it was more complicated than just running flash-all and left a bad taste in my mouth. Fortunately, re rooting went smoothly.
When I have the time I'll try again with my wife's phone and it probably will go smoothly and I'll feel stupid but I was just trying to avoid going through something similar again.
Looks like I was not the only one with problems. See http://forum.xda-developers.com/showthread.php?t=3185165
http://forum.xda-developers.com/showthread.php?t=3190103
and others on the web.
soupysoup said:
What u need to do is grab urself a copy of the latest factory images from here https://developers.google.com/android/nexus/images?hl=en download it to ur PC, connect ur device, make sure u have ADB and Fastboot installed on ur PC first, then open a command promt and type
adb reboot bootloader
When the device reboots run the "flash_all.bat" command inside the downloaded stock image file and ur device should flash the image. If this process is too difficult, as it may be for some ppl, you can download Wugz Nexus Toolkit from XDA, follow all the steps it tells u too, and upgrade with that, as it has a step by step walkthrough, that should be it, if u need any further help just let me kno
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
maybeme2 said:
The way to do it is simple enough. Problem is it doesn't always "work" as expected for everyone.
Example: I started by doing exactly what you said, but the flash-all command just stayed stuck on waiting for device no matter what I did to the phone.
So, I decided to go the step-by-step longer way. That gave me problems too. I don't remember what exactly but it included being stuck in a forever boot where the balls revolved forever, and some other problems I chose to forget. (boot loops, loss of sdcard space, etc.)
I did succeed in the end but it was more complicated than just running flash-all and left a bad taste in my mouth. Fortunately, re rooting went smoothly.
When I have the time I'll try again with my wife's phone and it probably will go smoothly and I'll feel stupid but I was just trying to avoid going through something similar again.
Looks like I was not the only one with problems. See http://forum.xda-developers.com/showthread.php?t=3185165
http://forum.xda-developers.com/showthread.php?t=3190103
and others on the web.
Click to expand...
Click to collapse
The flash all file will wipe everything from your phone which I'd assume you don't want to do. Just extract further to get the img files. Fastboot flash the bootloader, boot, system and radio. Then on your phone tell it to boot to recovery (i assume being rooted you have twrp etc) tell recovery to wipe cache and dvalik then boot the phone back up
Then make sure you have superuser zip ready to flash, your choice of kernel to allow root. Reboot to recovery and flash em both
Sent from my Nexus 5 using Tapatalk
I know. Thanks.
A nandroid can be used across phones, but limit what is put on. The problem you had upgrading was probably the userdata issue. Just skip the data wipe and flash just the things noted. You can also do this from a nandroid if your wife has twrp (I think bootloader needs to be manually updated though). Do a nandroid of her device first of course. Always good to have somewhere to fall back too.
It is probably best to just wipe the whole thing though. With your previous experience it should be fine. You can find the fix for userdata issues on the forum.
Thanks. Which userdata issue? I searched for userdata on this forum and nothing came up.