This is my new tutorial/program for unlocking/rooting/backing up/flashing recovery on the Rezound.
V
V
V
Thanks to hasoon2000 for all of your help. You helped me improve many parts of this from start to now !!!!
^
^
^
Thanks for this! http://www.xda-developers.com/android/htc-rezound-auto-unlocker-makes-unlocking-faster-and-easier/
For quick contact, Skype me, im "Fenguepay"
It is only v1.x so it is sure to have some errors.
If you find any, post them here If i don't respond to them then PM me.
I will try to find and fix as fast as possible.
This comes with all of the files that you will need.
Windows only.
You *may* need to install ADB here:
http://developer.android.com/sdk/index.html
You will need to download most of the stuff and install it once you get it.
For anyone who doesn't get any devices found before or after the reboot into fastboot. Make sure you have the HTC drivers installed. Get HTC sync from their site then simply open and run the installer then close the HTC sync process. It tends to interfere with your connection and you want the drivers not the program.
My program is now likely to brick your device. It hasn't bricked anyone's yet and probably won't ever. It's 99% noob proof.
DO NOT CHANGE THIS PROGRAM AND CALL IT YOUR OWN!!!!!!!!
SCAN FOR VIRUSES IF YOU WANT TO. THERE ARE NONE.
v1.0 Initial Release DONT USE EXE FILE DOESNT WORK. WONT EXECUTE THE ADB AND FASTBOOT CMDS
http://www.mediafire.com/?74332s36tjs335q
v1.2 Fixed many issues, tested with new device
http://www.mediafire.com/?hs2aurm5e81b1ke
v1.3 Added input options and a new menu. DO NOT USE. CRASHING ERROR!!!!
http://www.mediafire.com/?mty2n39u2ctkew7
v1.4 Fixed stability, did a few tweaks.
http://www.mediafire.com/?g32bzcf8g1eke9z
v1.5 Very refined, 99% working.
http://www.mediafire.com/?h11mllw3e67zvsq
v1.7 Added a utility and custom command menu, cleaned up menu. BIG DIFFERENCE!
http://www.mediafire.com/?5keazk7z6ew3cpl
Added custom command line. Use cust then command will be entered from the unlocker folder. Experimental*
v1.8 Fixed color issues, cleaned up root folder.
http://www.mediafire.com/?g4tpzr4b2smvpnb
Need help making gui.
v1.9 Fixed a missing "." on one line of code
http://www.mediafire.com/?zf7c0cd4cou7tqx
v2.0 Now redirects you to HTCdev.com/bootloader
http://www.mediafire.com/?ky6ezfk48v0y6l1
Future:
Executable file. No
Fancy GUI. Future
Walkthrough and Individual steps. Yes
Kernels, Recoverys and more.... Somewhat
*need help*
*side note* I want to make a gui version but I can only code bat. Would appreciate help :/
For quick contact, Skype me, im "Fenguepay"
EDIT---
Apparently this was not as easy to use as I intended. Here are some quick instructions to get you started.
1. Who is responsible for damage? You are. The answer to the question is "me"
2. You should now be on the menu. From here, if you are a noob/trying to unlock, do 1 and follow the whole process. It should explain it well, and i know it works i rooted a new device in around 5 minutes.
3. If you wan to flash another recovery, use the "util" option at the menu, select recovery and drop your recovery into the recoveries folder. From here you just type its name.
4. If you want to use a custom command that is launched from the root folder, use "cust" this makes it so you do not have to use "cd c:/Android". For ease of use.
5. If the process does not work, i know for sure there are other tutorials on xda and other sites. I am not a 100% pro at this.
http://www.youtube.com/watch?v=l1hhwplNVMQ
Any feedback anyone?
I get my laptop back today and since I skipped school I'll give this a shot, I'll be able to try it around 11 or 12
Sent from my ADR6425LVW using XDA
I would try it out but I'm already unlocked and rooted.
Sent from my rooted HRC Rezound
Can anyone give me some feedback?
Feedback...was gonna give this a go but nae.
Sent from my ADR6425LVW using XDA
anyone?
I'm sure your script will run. I'll probably end up running it when I need to. Just don't feel like going through the process right now. We do appreciate the tool though.
I did a few changes, this program works perfectly now
Good Job on the program. Choices are always good
I don't want to sound like a total noob but I was hoping for some instructions. I have rooted the D1 and the Charge but I am kind of lost here. Do I need to do the HTC Unlock first?
Thanks,
Brad
Originally, when I was going to make a toolkit, I was going to make one like yours but I opted out and believed the GUI style is easier to use and understand. Never-the-less, there are more choices for people and I give you props! Great job!
if you start with one, it does a full guide, read the notes. It does the commands for you but you need to go to the website
Becuaswe of how its set up, you will need to use internet explorere with htcdev idk y but once you are there amde an account, select the rezound, SKIP THE FIRST 2 PAGES,MY PROGRAM DID THAT FOR YOU. And just follow the text selection on the 3rd page. From there you will get the email unlock_code fiel and put it in the folder.
Hope this works for you
hasoon2000 said:
Originally, when I was going to make a toolkit, I was going to make one like yours but I opted out and believed the GUI style is easier to use and understand. Never-the-less, there are more choices for people and I give you props! Great job!
Click to expand...
Click to collapse
Thanksfor the good feedback, i was expecting hate, thats what i got whne i made a text guide. I tried to amke it noob friendly with a brief explanation. Also, i only know how to code bat, I could do a project with you if you taught me c++ of java. I would love to know how. But bat is my only option. I actually looked into c++ for a project like this with a cool gui.
We could make a beta/2.x version with a gui.
Thats if you know hwo to code.
fenguepay said:
Thanksfor the good feedback, i was expecting hate, thats what i got whne i made a text guide. I tried to amke it noob friendly with a brief explanation. Also, i only know how to code bat, I could do a project with you if you taught me c++ of java. I would love to know how. But bat is my only option. I actually looked into c++ for a project like this with a cool gui.
We could make a beta/2.x version with a gui.
Thats if you know hwo to code.
Click to expand...
Click to collapse
I don't know how to code with either lol. Look at my signature. I made a GUI toolkit. Took me forever to learn lol
Sent From My HTC Amaze 4G via Someone's Room
hasoon2000 said:
I don't know how to code with either lol. Look at my signature. I made a GUI toolkit. Took me forever to learn lol
Sent From My HTC Amaze 4G via Someone's Room
Click to expand...
Click to collapse
Thats very good!
What coding lanugage?
Is there a mode where it does a walkthrough or not. And is it all compiled or is there a folder?
soooo many questions. And finally, would you mind sending me the kernels, i dont want to fish them out. Ya but i want to make a program that is a walkthrough but has options to do only one step. The walkthrough is what i think makes mine different.
I worked a lot to get from 1 to 1.5 hope you like
Sent from my ADR6425LVW using xda premium
Thanks for thanking me
Sent from my ADR6425LVW using xda premium
Working hard to make this more functionable, next step, custom kernels.
I need to know the command for flashing kernels and need some recomendations for kernels, i dont have much knowledge for this
Related
MOD EDIT : As requested by OP, I'm closing this thread.
Everyone can continue the rooting related discussions on the other thread linked here. Full root for Nook Tablet. [11/20/11] [Yes this is a permanent root!].
All,
Here is a "one click" script to root your Nook Tablet AND install gapps (Market) all in one shot. It also includes the latest superuser binary and apk (automatically installed). MAD PROPS to Indirect for being the first to get root on the NT. This script builds off of his (and others) work to make it a bit easier.
I need people to test this. That being said, RUN THIS AT YOUR OWN RISK. It may work perfectly, or it may explode your Nook. You've been warned!
1. Download and extract the zip file located at https://rapidshare.com/files/3156164791/NT-One-Click-Root-by-anlog.zip (PLEASE MIRROR THE FILE FOR ME SO YOU DON'T KILL MY DROPBOX ACCOUNT).
2. Factory reset your Nook Tablet (just do it).
3. Run Windows 7 (32-bit or 64-bit). Sorry Mac and Linux, but that's not my arena.
4. Enable USB debugging and sideloading on your Nook (download an APK and try to install it with package manager. Hit settings and set the options). YOU MUST uncheck "auto mount USB" or debugging won't activate. There are also two checkboxes for debugging and staying awake - make sure both are set. DO NOT REBOOT your Nook once you enable these settings.
5. Plug in your Nook and point Windows to search for the drivers in the usb_drivers directory from the etracted file. The driver has been modified to work with the Nook Tablet and you don't need to mess with any adb.ini stuff. It's ready to go.
6. Once the driver loads, make sure you have a device called "ADB Composite Device" (or something similar) in Device Manager. As long as you don't have an item called "Nook Tablet" with an exclamation point, you're good. Once you are plugged in, check the status bar on your Nook and make sure USB debugging is enabled (there will be a little robot indicator).
7. This step is optional, since it is run at the beginning of the script, but you can open a command prompt AS ADMINISTRATOR and go to the folder where you extracted your files and run "adb devices". It should list your Nook serial number. If it doesn't, start over.
8. Run a command prompt as Administrator and then run the NookTabRoot.bat file to root your tablet and install gapps. Your tablet will automatically restart once the script finishes.
This script is ALPHA and probably won't work, but that's why I need people to test. If anyone finds a way to make it better, please feel free to modify it (as long as you credit me and Indirect).
Good luck!
MIRROR 1 - http://dl.dropbox.com/u/7364988/NT-One-Click-Root-by-anlog.zip
Thanks a lot, this is going to be quite helpful.
anlog, can you please remove the rooting script from yours as it will make it harder for me to provide support if they are in your thread as well. Im happy the gapps is there but I really don't want aanyone to be missed when they need help.
Note: Seriously not trying to be a **** but this is the early stages of rooting and I would HATE for someones system to be completely screwed and I don't know they need help.
P.S.: Just link to the original root thread saying you must have rooted before you proceed with this script.
After that, I'll happily help you work on this script and offer support for this as well.
Indirect said:
anlog, can you please remove the rooting script from yours as it will make it harder for me to provide support if they are in your thread as well. Im happy the gapps is there but I really don't want aanyone to be missed when they need help.
Note: Seriously not trying to be a **** but this is the early stages of rooting and I would HATE for someones system to be completely screwed and I don't know they need help.
P.S.: Just link to the original root thread saying you must have rooted before you proceed with this script.
After that, I'll happily help you work on this script and offer support for this as well.
Click to expand...
Click to collapse
Your root method is not easy enough for the average user, which is why I've posted this.
I'm not removing anything. It's up to the community to decide if they want to try my script or not. I will host it and setup my own mirrors if I have to.
conundrum768 said:
Thanks a lot, this is going to be quite helpful.
[Mirror removed in light of Indirect's post below]
Click to expand...
Click to collapse
Sorry to see you cave in so easily...
I'm not being disrespectful but my script really isn't too complicated. I was working on rewriting the thread anyway I just haven't gotten the time yet until now. I've been out all day.
This early in the process, it is great having multiple ways to achieve root.
Can't you each add a disclaimer in your package "If you use this method to root, don't use any other method without doing a full factory reset first" or whatever words would be appropriate?
Mostly - don't get ticked at each other.
It's not a multiple way, it's verbatim my script with his added to it.
This is not a glory or recognition thing. This is something that I think will greatly help the community of average users with little to no experience with things like ADB or Unix commands.
Many every day users are discovering XDA and it can be very difficult for them to navigate through the forums and find what they are looking for. My goal is to make it really easy.
The script will not blow up your Nook. The worst thing that can happen is that it just doesn't work.
Not sure what else to say, but this "only one user is allowed to help people root" nonsense doesn't work for me, nor the rest of the community. Sorry Indirect. If it helps, I've credited you at the beginning of my script.
OK - then I would say don't include an early version of a root script except by reference... Let the original author handle the bugs and enhancements.
I dont see a problem with useing each others method as long as the appropriate credit is given when you use someone else's work in your own.
Indirect said:
It's not a multiple way, it's verbatim my script with his added to it.
Click to expand...
Click to collapse
You mean your script with a bunch of STANDARD adb commands in it? Not exactly rocket science. Did you write zergrush? No, but you used it (and credited them accordingly).
"Your script" <-- I atleast want people to ask permission before blindly taking my work in the first place. I didn't say this is released under public domain for anyone to use, I would like you to ask before. Use it, whatever but seriously, It kind of upsets me that you didn't bother checking with me if it was alright to atleast use my script. If anyone wants support, come to this thread if you use it. I am not able to help you as I did not develop the addition to this.
Indirect said:
"Your script" <-- I atleast want people to ask permission before blindly taking my work in the first place. I didn't say this is released under public domain for anyone to use, I would like you to ask before. Use it, whatever but seriously, It kind of upsets me that you didn't bother checking with me if it was alright to atleast use my script. If anyone wants support, come to this thread if you use it. I am not able to help you as I did not develop the addition to this.
Click to expand...
Click to collapse
YOUR SCRIPT IS A BUNCH OF STANDARD ADB COMMANDS. That means that 100% of all other ADB scripts out there use elements from the script you pieced together from other scripts.
Get over it. You obivously only care about recognition. My only goal is to help other people.
anlog, you have clearly not seen any of my other work. I'm not in it for recognition, I need to know if something goes wrong at all and if so, what caused it. That's it.
Indirect said:
I'm not in it for recognition
Click to expand...
Click to collapse
Then stop telling people to remove their work and instead write a better/faster/easier version.
Enjoy this script anlog, I appreciate your help finding the driver fix and be sure to reference me in your thread as well for proper credits. Enjoy your evening, I'm no longer debating about this as it's stupid. I think we can both agree on that.
And before you think I'm just being a ****, I wrote a script for the evo shift that was ridiculously advanced for the job JUST to make it so people can't screw it up.
http://forum.xda-developers.com/showthread.php?t=1277793 <-- read about it there.
okay, so not to get in the middle of anything, I will say I've successfully rooted my nook tablet with the original method. didn't have any luck installing the android market (and getting it running).
as such, I've done a factory restore and have downloaded the script here.
as someone who is fairly computer literate, but is VERY new to rooting (short of 1 click root), I will take the shortest path possible. no loss of credit to indirect. please guys, all your work is recognized.
will report back shortly.
Indirect said:
Enjoy this script anlog, I appreciate your help finding the driver fix and be sure to reference me in your thread as well for proper credits. Enjoy your evening, I'm no longer debating about this as it's stupid. I think we can both agree on that.
And before you think I'm just being a ****, I wrote a script for the evo shift that was ridiculously advanced for the job JUST to make it so people can't screw it up.
http://forum.xda-developers.com/showthread.php?t=1277793 <-- read about it there.
Click to expand...
Click to collapse
Dude we need people like you to build off other's work. We both agree that if there is a super easy way to root and get Market, more people will buy the NT. From the second I started this thread you were credited in the first line of my script. I will also credit you in the beginning of this thread. I am NOT about stealing other people's work. Your work here is GREATLY appreciated!
anlog said:
Dude we need people like you to build off other's work. We both agree that if there is a super easy way to root and get Market, more people will buy the NT. From the second I started this thread you were credited in the first line of my script. I will also credit you in the beginning of this thread. I am NOT about stealing other people's work. Your work here is GREATLY appreciated!
Click to expand...
Click to collapse
Sorry for getting annoyed and worked up but I already had to play "Dueling Batch Scripts" in the evo shift section when mine was CLEARLY superior to the other ones by far because I was still developing it. :| So again, my apologies for losing my head but don't wait too long for my REAL script to be thrown together sometime tonight and blow yours out of the water.
Update 1-21-12
Ok, 1KDS ran into a small, well maybe not small, issue. The way the whole process works would require a large amount of RAM for the process to run properly. It's in the order of 6+ gigs because the scripts set up and run the operation in RAM. Since most people don't have that much RAM the project is on hold until a solution presents itself. I would like to thank 1KDS for looking into this. If anyone has ideas, feel free to post up.
Previous Info:
Ok, guys here's the deal. The dev is aware of what I'm asking and is looking into possibly doing this for us. Remember these simple requests:
1) Don't ask for ETA's. Enough said.
2) If a question is asked that needs your answers/input, please give it.
3) If he is successful, and I have to stress "IF', he will need testers. Please do, I know I definitely will.
And Finally
4) If you can, donate/support, he's doing this for YOU!
Previous Post:
Ok Here's an update. I pm'd the creator over at DXF and he has said it's pretty involved. He has said:
" It's pretty involved, it may be easier to make one myself. If you can link me the SBF file, instructions to get into the bootloader or wherever you flash from, instructions to factory reset afterward, and what root method is used for the MoPho I can work on one."
So I'm going to provide the info. My question to my fellow MoPho users is "Would you be willing to support and/or donate to him for his work on this?" If he's going to be nice enough to do this we should be nice enough to support him for his efforts. I'll update this as I find more info.
Mike
Original Post:
Have a question, how would one go about creating an automated Linux bootable CD with all the scripts and files to make it easier to SBF a MoPho?
I came from the Droid X and there was a file I downloaded that was in a word - awesome. Insert CD, boot from it, plug in phone, choose option 1, and viola!!! In a few minutes your device was flashed back to stock, no fuss no mess.
I'm a MoPho-er
I wish I could help, but IDK how to do that bub, try making a post in the Droid X Forums, ask for a dev to remake the files to boot on a CD and use this SBF file ---- use this link to download it.
See if that helps, someone may be able to make that CD.
Just thought I'd ask. It's been a few years since I dabbled with linux, Red-Hat was my last venture (10-12 years ago). I'll look at how the cd and the scripts are set up. I can probably figure it out.
I'm a MoPho-er
Let me know if you or someone can get it to work, I'd be very interested.
I think I can get it to work, just have to get the scripts right. Gonna take a fews days. I'm gonna post over at DXF and ask the person who creates them for some input.
I'm a MoPho-er
I'm linking this thread here as it has all the tools and info needed (hopefully) to create a bootable SBF CD.
http://forum.xda-developers.com/showthread.php?t=1393519
I'm a MoPho-er
Alright guys, I'll be working on a new image for the MoPho (I like that name!)
One question, anyone use the ZergRush root method on the MoPho? I have a nice script for that already as well as the Droid 3 method.
1KDS to the rescue!!!!!!!!
Thanks, your work is awesome!!!!!!
I'm a MoPho-er
I used Shabby's one click
I'm a MoPho-er
I looked at Shabby's script, looks pretty much like the Droid 3 method, I can use his script though, there may be a piece I'm not seeing that affects the MoPho. Does it work on the newest SBF/firmware?
I used it to root mine. Took it out of the box and it updated to the latest as soon as I activated it. I rooted about three days later and had success on the first try.
Edit: I don't know about the latest SBF, but (uneducated guess here) I would imagine it should.
I'm a MoPho-er
Alright guys, been busy but I'm ready to start on this new image, couple questions...
There was an SBF file posted on page 1, is that one preferred? I see there is a newer one out there.
Can someone post some clear instructions on getting into the bootloader or RSD mode and instructions for stock recovery to factory reset?
Is there a preferred bootstrap/clockwork? If one is preferred and offered free from the dev I can add a script to install it for you after rooting.
I hope I can give good info here, no one else is stepping up and I'm not fully "up to speed" on my MoPho yet. There's much I haven't tried because I'm "RSD skiddish". When I had my Droid X RSD and I just wouldn't "get along", so I'm not familiar with it. Hence the reason I loved the bootable CD.
For SBF files I think 198_6 is the latest official release. From what I understand 198_7 is out, but it's a leaked package as Sprint never released it.
As for CWM, there is one available, a thread is devoted to it. I think the version is 5.. dot something and it was made specifically for the Photon. It requires the bootloader to be unlocked as well, I believe. Thread here:
http://forum.xda-developers.com/showthread.php?t=1218417
For all the other steps there is a thread by qbking77 that has videos instructing how to root, flash, unlock, install CWM, etc. here:
http://forum.xda-developers.com/showthread.php?t=1250697
Hope this helps.
I'm a MoPho-er
Keep me posted. Can someone PM me the link to this thread when this is done, for some reason, I'm not getting updates on this thread...
Sent from my Motorola Photon 4G (MoPho) on Sprint, the Now Network using XDA Premium.
I had a couple bad downloads of the SBF file, I've got a good one now and unzipped it, the file (uncompressed) is 2.44GB! SliTaz (the Linux distro I use for these images) boots into RAM and my machine simply doesn't have enough RAM to unzip the file and stay stable, if I had more RAM I could make the iso but very few people would be able to use it as they would need 6+ gigs of RAM to run it. For now I'm putting this project on hold until I think of something else or a smaller SBF file is released. Sorry guys.
Ouch!!!!
Bummer 1KDS
Thanks for looking into it, though. I was curious why one didn't exist yet. I guess that would be a good reason why. I guess I'm just gonna have to break down and make RSD and me get along so I can do some modding to my MoPho.
I'm a MoPho-er
Question. Would a "virtual" environment work or is something like that just way to involved to work?
Edit:
Don't know if "virtual" is the right thought or not. I may have been thinking "RAM Disk" setup.
I'm a MoPho-er
Yeah, I use VirtualBox to build the images, my laptop has 4 gigs of RAM and I allocate around 2.5GB to the virtual machine so the machine stays stable and I can't even unzip it within that amount of memory. Like I said, even if I can build the image only a few people would be able to use it since it is so massive.
This is my new tutorial/program for unlocking/rooting/backing up/flashing recovery on the Rezound.
V
V
V
Thanks to hasoon2000 for all of your help. You helped me improve many parts of this from start to now !!!!
^
^
^
Thanks for this! http://www.xda-developers.com/androi...er-and-easier/
For quick contact, Skype me, im "Fenguepay"
It is only v1.x so it is sure to have some errors.
If you find any, post them here If i don't respond to them then PM me.
I will try to find and fix as fast as possible.
This comes with all of the files that you will need.
Windows only.
You *may* need to install ADB here:
http://developer.android.com/sdk/index.html
You will need to download most of the stuff and install it once you get it.
For anyone who doesn't get any devices found before or after the reboot into fastboot. Make sure you have the HTC drivers installed. Get HTC sync from their site then simply open and run the installer then close the HTC sync process. It tends to interfere with your connection and you want the drivers not the program.
My program is now likely to brick your device. It hasn't bricked anyone's yet and probably won't ever. It's 99% noob proof.
DO NOT CHANGE THIS PROGRAM AND CALL IT YOUR OWN!!!!!!!!
SCAN FOR VIRUSES IF YOU WANT TO. THERE ARE NONE.
v1.0 Initial Release DONT USE EXE FILE DOESNT WORK. WONT EXECUTE THE ADB AND FASTBOOT CMDS
http://www.mediafire.com/?74332s36tjs335q
v1.2 Fixed many issues, tested with new device
http://www.mediafire.com/?hs2aurm5e81b1ke
v1.3 Added input options and a new menu. DO NOT USE. CRASHING ERROR!!!!
http://www.mediafire.com/?mty2n39u2ctkew7
v1.4 Fixed stability, did a few tweaks.
http://www.mediafire.com/?g32bzcf8g1eke9z
v1.5 Very refined, 99% working.
http://www.mediafire.com/?h11mllw3e67zvsq
v1.7 Added a utility and custom command menu, cleaned up menu. BIG DIFFERENCE!
http://www.mediafire.com/?5keazk7z6ew3cpl
Added custom command line. Use cust then command will be entered from the unlocker folder. Experimental*
v1.8 Fixed color issues, cleaned up root folder.
http://www.mediafire.com/?g4tpzr4b2smvpnb
Need help making gui.
v1.9 Fixed a missing "." on one line of code
http://www.mediafire.com/?zf7c0cd4cou7tqx
v2.0 Now redirects you to HTCdev.com/bootloader
http://www.mediafire.com/?ky6ezfk48v0y6l1
Future:
Executable file. No
Fancy GUI. Future
Walkthrough and Individual steps. Yes
Kernels, Recoverys and more.... Somewhat
*need help*
*side note* I want to make a gui version but I can only code bat. Would appreciate help :/
For quick contact, Skype me, im "Fenguepay"
EDIT---
Apparently this was not as easy to use as I intended. Here are some quick instructions to get you started.
1. Who is responsible for damage? You are. The answer to the question is "me"
2. You should now be on the menu. From here, if you are a noob/trying to unlock, do 1 and follow the whole process. It should explain it well, and i know it works i rooted a new device in around 5 minutes.
3. If you wan to flash another recovery, use the "util" option at the menu, select recovery and drop your recovery into the recoveries folder. From here you just type its name.
4. If you want to use a custom command that is launched from the root folder, use "cust" this makes it so you do not have to use "cd c:/Android". For ease of use.
5. If the process does not work, i know for sure there are other tutorials on xda and other sites. I am not a 100% pro at this.
Didn't u already have a thread with this ?
Sent from my Dinc... I mean Rezound
Just wanted to repost in development section
Sent from my ADR6425LVW using xda premium
fenguepay said:
Just wanted to repost in development section
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Ahh ok I see now ... Hopefully this will help some noobs
Sent from my Dinc... I mean Rezound
Note: more content is coming regularly, so check back regularly! Also, post your input so this thread does not become buried.
As an initiative to kickstart development for the Galaxy Player 4.0, I have decided to put up this guide to try and attract more users to rom development. This, although, does not mean you can willy-nilly post up a rom including one mod, or a quick tweak. Making a rom involves a lot more than that.
The Developer's Code:
1. Your rom MUST be unique from the other roms.
This means you have to have a careful, well thought out rom. It must have several things differing it from other roms, something that makes it stand out. The last thing we need are 200 "me too" roms cluttering up development. Takes Klin's rom and mine, for example. We both have ICS themes, we both have tweaked our roms for performance, but they are both completely unique. Why? Because we didn't copy one another. We saw what the other had, and left it alone. I have an ICS theme, he has an ICS theme, but they are based on completely different themes. The biggest boo-boo in rom devving is copying someone else's rom/features/work. You will get kicked out unbelievably fast if you DO NOT follow this rule. To reiterate, the last thing we need is 200 identical roms. Make sure yours is unique from the others, and has a defining feature.
2. You must be willing to provide regular, consistent updates.
Maintaining a rom can be a full time job. You have bugs to deal with, features to add, and hours of work in which you only accomplish a small amount of work, due to some catastrophic failure. Last night it took me over 3 hours to fix a battery icon issue. Why? because I had almost space left in which to apply my fix, and if I did even one step wrong I had to reflash to correct the issue.
You should NOT release your rom once, and never look at it again. You should be willing to update it at least twice a month, if not sooner. I update mine several times a week, but that's because I have a lot of free time. Your mileage may vary, but try to hit for that mark. Too long wihtout an update and users will get bored/tired of your rom without anything new to spice things up.
3. You must be willing to provide helpful, friendly support.
At times, monitoring your thread can be frustrating. you may have someone complaining about an issue that was fixed several releases back, or someone who wants a new feature and keeps bugging you about it. It can be frustrating at times, but make sure you calmly answer everyone's questions in a fair manner. It can be extremely frustrating for a rom user to post up a question, and have it answered days later because the dev was "too busy" to monitor their thread. This, if anything, is almost more important than rom updates. Users love devs who actually converse and answer them, so be friendly, and keep your thread going!
4. ALWAYS ALWAYS ALWAYS give someone the apppropriate credit for their work.
It is the bane of the dev's existence: spending days/weeks/months of xyz feature/theme/rom, and have someone come along and snatch their work from them without as much as a "thank you". First of all, it will get you banned faster than any other offense out there. Secondly, it is one of the largest insults you can give someone. Our community is one that is supposed to share work, and most people do that freely, but you MUST give credit where credit is due. It is best if you ask someone's permission before you use their work, especially if it is something major (a huge theme for example). But even if you don't (and you should), at the very least list their username and what they did in your rom SOMEWHERE in your description.
5.You do not know everything.
After creating a rom, many people feel that they know much more then the "average" community, and that they are always right when it pertains the their rom. This could not be more wrong. The best way to improve your rom, is to listen to xyz person who knows more about a certain area than you do, and attempt to learn from that person. Everyone is skilled in a different area, so if you listen to your community, and assume they know best, you can learn and accomplish a lot evry quickly.
6. Google is your friend.
Do not assume that dev's know everything, and that they pull these features out of their heads. When in doubt, go to google. Always. There is normally a guide, or someone with your issue to help you out. As usual, make sure you give that person credit if you use their work.
So, to sum it up, Make your rom unique, be dedicated to your work, be ready to handle unexpected situations, ALWAYS give someone appropriate credit, listen to your community, and google a lot!
Not intimidated yet? ready to bring your amazing idea to the limelight? head on down to the section below to get started!
The Easy Way to Dev: Odin flashable packages.
Most people don't want to edit their rom on their computer. As a matter of fact, you can create a killer rom without even touching a computer to mod it. Up until I started theming, I working on my rom 100% on my device. This is the most tried-and-true method out there, and the one most likely to create the least drama. All you have to do is Pull the /system partition from your Player, and create a tarfile out of ti.
Prerequisites:
Samsung Device (system partition location may change with device type. This should be the same for US/INTL players)
PC running Ubuntu/form of linux (ubuntu is recommended for beginners)
ADB installed (actually not needed, but speeds up the process) (look below in resources for a guide)
appx. 300mb free on /sdcard
about 1 GB free on the Linux box
1. Apply whatever mods you want too
2. Open up a terminal emulator
3. type this in: dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
4. wait for it to complete (may take up to 10 minutes)
5. You now have a file called factoryfs.rfs on your internal sdcard
6. Hook it up to a computer and activate usb storage
7. copy factoryfs.rfs to whatever directory you want (home is recommended for simplicity)
8. Open up a terminal
9. cd to the directory of your file (if you placed it in home skip this step)
10. Type in "tar -H ustar -c factoryfs.rfs >packagename.tar"
11. Now you have a odin-flashable rom!
ADB users, simply run adb shell and type in the first command, then adb pull the file to the computer.
If you want to save space for a file sharing website (eg. mediafire, which has an upload cap of 200mb), simply Zip the file using 7-zip (set on ultra). You may have to do this on a windows machine.
Now this is even easier! simply flash the stock image in the link below with all the essentials included, and you can apply all the mods you want without having to ever go through dsidxa kitchen! Klin even fixed busybox for you! this way you can easily start from stock and work your way up to more advanced hacks.
http://forum.xda-developers.com/showthread.php?p=27973753#post27973753
The Advanced Users Guide: CWM packages.
Maybe you want more flexibility. Maybe you need to deodex your rom to mod some stock files, or zipalign to speed things up. This guide is for you people who need the more advanced options. It is harder, and you have a greater chance of messing things up, but you get to completely control your rom, even easily edit it on the computer! This guide is for advanced users only, or someone who is willing to spend a lot of time on trial and error.
Prerequisites:
ADB installed (Extremely helpful, and may to required)
Samsung device
Ubuntu/linux box
A bit of caution
Patience
1. Install Dsidxa Kitchen
2. Put your factoryfs.rfs in the necessary folder
3. cd to the directory you installed the kitchen
4. Type "sudo su"
5. enter your password
6. Type "chmod +x menu"
7. run "./menu"
8. you are now in the main menu of the kitchen.
9. There are many options, choode the one that you need!
Note: stay away from installing busybox using the kitchen. It installs a bad version of busybox which can make rom development a big headache for you!
10. There is a working folder in the kithcne directory, in there mod all the files you need.
11. When you are done, head into option 99 (create rom)
12. Run the interactive option
13.When you get to the update-script type, type "y" to install the newer type, which is required to flash a cwm zip in the Galaxy Player.
14. If you want to flash your rom using stock recovery, sign it. Else, leave it alone.
15. You can keep the normal name, or change it to what you want. If you are going to be flashing using stock recovery, make sure it is named "update.zip"
That is it! If you want to create a odin package out of it, simply flash the cwm zip, then follow the instructions above!
I will be adding on to this guide as time goes on, so make sure you ask pertinent questions below!
Resources/Additional Guides:
Install ADB:
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Install dsidxa kitchen:
http://forum.xda-developers.com/showthread.php?t=1303311
4.0 base (essentials installed, just apply your hacks and you are good to go! thanks klin):
http://forum.xda-developers.com/showthread.php?p=27973753#post27973753
Easy theming guide:
http://androidforums.com/optimus-m-...guide-theme-guide-noobs-adding-lots-more.html
APK multi-tool (needed to theme):
http://apkmultitool.com/?q=node/5
Recommended hosting sites:
www.mediafire.com
Good Rom practices:
1. If you retheme, include screenshots! people love screenshots.
2. Make a logo if you can, it makes it easy for people to support your rom by adding it into their signature.
3. If you mod, make sure you can easily explain it to someone if need be. Messy hacks are not good in the long run!
4. Focus evenly on all parts of your rom. Some people love speed, others love features. You can focus on one or the other but try and keep it balanced.
5. If you create a custom script/init,d script/documentable file make sure you include comments in your mod so people can try and fix it if need be!
6. Make sure all the bugs are ironed out before release. People love fast releases, but if it is really buggy they may switch to another rom.
7. if you have exhausted all other methods of fixing an issue, or cannot work on it a lot in the opcoming days/weeks, release a beta version stating the bugs clearly. That way while you are gone, more experienced people can help you iron out the bugs.
8.Make sure it is easy for the person to obtain your rom. If they have to download another utlity or click through 30 ads, they may just want to use another rom than go through the hassle. Worse, they may mess it up, forcing you to help them troubleshoot.
9. Make sure you update utilities on your rom as soon as an update becomes availible. That way you get the fewest bugs, and as I said before, users love updates!
10. Even if someone's issue seems isolated, at least spend some time with them figuring out what happened so they can fix it. You never know, it may be the harbinger of a HUGE outbreak of issues.
11. Base your rom on an intl version. There is a fortunate "bug" that klin discovered that allows US users to use any intl rom without their home button breaking. Of course, that has a lot of asterisks, but if you will look below, I have developed a fix for that issue, which allows anyone with a "broken" home button to use it with the problematic rom!
12. Practice good rom devving. If there is a major issue that could be a pain, don't take the easy way/fix out. That always comes back to bite you later, as I have figured out. I once had a corrupt journal on my system partition, and did not want to go through the hassle of recreating my rom on a clean partition. So, I simply added a flag to have /system mount as rw if there are any issues. Sure enough, about 3 days later, I started having some filesystem issues, and had to completely rebase, because I did not have any backups.
13. ALWAYS keep backups. Just do it. Not just one, either. Keep at least three days worth of backups, just in case there is an issue in backup 1 and two, but it not in no. 3. This would have been hugely helpful to me in many cases, but I didn't want to "waste" the space. Guess what I did a few days later: spent a nice evening with linux fully recreating my rom from scratch. Just do it.
Fix home button issues. (useful if you use a rom seperate than a flasher's region) (developed by me)
I have finally, after a bit of luck and some know-how, determined a fix for the home button issue! This will work on ALL roms, not just this one, and will probably work for the 5.0 as well. This also means you can fully wipe data if you want, and simply apply my fix.
1. Navigate to /dbdata/databases/com.android.providers.settings
2.Optionally copy to a computer (easier that way)
3.Open it up in a sqlite editor (if you are doing this on the device, copy it to /sdcard and and then copy it back
4.Navigate to the locale/first section (there should only be one string in there
5.It should look like en_US if you have a US player, or en_GB if you have a UK/intl player
6.Change the string to the language/locale you use (if you are INTL you can merely change it to xx_GB, where xx is your language. If you are US, just perform the same steps, but change the last part to US)
7. commit/save the file and copy it over the old one
8. Reboot, and your home button *should* be fixed!
NOTE: I have not personally tested this. It has a 99% change of working, but I have yet to completely verify it.
NOTE: after you replace the file, android may go a little haywire (wifi disconnects, forgets password, advanced reboot option unavailable, etc.). THIS IS OKAY. Simply reboot, and it will all be back. Do not change any settings after copying until it reboots, as it may possibly break the fix
NOTE: I cannot provide a downloadable file, as that file contains all of your system settings, and if you use mine, my settings will be applied, which could be pretty bad in some cases.
NOTE: this has no chance of bootlooping or bricking your device. At absolute worst, you have to set up a few settings/restore from a /dbdata backup. There is almost no risk involved.
Potential fixes for potential issues:
1.Bluetooth breaks. The main cause of this is if you install supercharger and nullify. Simply unullify and verify it is remove from build.prop, and you are good to go!
2. Home button breaks. (see above )
3. Root/busybox breaks. It's kinda messy, but if you absolutely HAVE to, simply reroot. That should fix it in a pinch. This is a classic case of keeping good backups. I have had to spend an entire afternoon redoing my entire rom because of my lack of recent backups. If you have the space, keep them. I have more than once managed to create a stopgap solution in my rom just to have some weird issue pop up again, and again. Just do it.
I LOVE you, man.!!
Hanthesolo,
Very good achievement, we all have to learn from your good sharing.
Congratulations man
rgds
I am really happy you guys like this! I will continue to add to it as time goes on, so expect even more content!
Sent from my EtherealPlayer.
New content up! also notice the link to the stock rom klin made so that you never need to go through a kitchen to get your rom started!
Has anyone used this yet? successes/failures? make sure you give me feedback so I can make this better!
Yet mre content up! Could this be possibly stickied? I know it's a little rough right now, but noone replies to this thread as there really is nothing to reply TO. I have worked hard on this and would hate to see this information go the way of the dead threads.
Thanks for this info man, making roms for my old evo and just stacking up on guides and any kind of reading material that I can utilize for my advantage. So, this will be helpful lol. I'll be checking back every so often on anything new added, but thanks again bro. Thanks given! Feel Encouraged!! lol
iAMsalm said:
Thanks for this info man, making roms for my old evo and just stacking up on guides and any kind of reading material that I can utilize for my advantage. So, this will be helpful lol. I'll be checking back every so often on anything new added, but thanks again bro. Thanks given! Feel Encouraged!! lol
Click to expand...
Click to collapse
Glad you enjoy it, this forum is the abandoned, dusty wasteland of xda, so I wrote this guide to (hopefully) stimulate development a bit.
hanthesolo said:
Glad you enjoy it, this forum is the abandoned, dusty wasteland of xda, so I wrote this guide to (hopefully) stimulate development a bit.
Click to expand...
Click to collapse
I know it definitely feels like that from time to time, but that's a byproduct of the nature of our devices. There's ridiculous money in selling someone a shiny new crippled phone with a horrific contract that will never get updated. You won't see a jawdropping ad on TV featuring a Galaxy Player because there's just no money in it. I'd love to have the T-Mobile girl holding my phone while wearing a pink leather riding suit(her, not me). That ain't happening.
I'm pleased and more than a little shocked that some new roms have come out in the past month thanks to this guide. I wanted a Android powered phone without the contract. I wanted an iPod Touch without all the bull**** that comes from being tied to Apple. Thanks to XDA my device fast, sexy as Hell, and does everything I want.
The only thing that makes me sad is that a year from now I probably won't be able to buy a Galaxy Player 4.0 v2 because there's just too much money to be made from contract only devices.
Thanks for this guide. It help me for begin android development.
GalaxySWifi4 said:
Thanks for this guide. It help me for begin android development.
Click to expand...
Click to collapse
I hope you have fun beginning development! It really is a lot of fun once you et past the basics.
Gswifi, I never replied to you, but your speech was so awesome, that I want to put it in the OP .
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
hanthesolo said:
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
Click to expand...
Click to collapse
@hanthesolo
do you have some knowledge about kernel compiling, so you could hel me?
hanthesolo said:
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
Click to expand...
Click to collapse
please do
I understand early nothing about this advanced stuff of making ROMs, even more about make Kernels XD. But I want to experiment some little things to learn by myself step at step. But... I cannot start... I'm in CM10.1 with Koala's Kernel and I can't make the factoryfs.rfs file doing this: dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096 in Terminal Emulator because /dev/block/stl9 doesn't exists. With ADB I have the same error.
Is this due to this ROM is not stock or something like this? Or only I have to create this folder or change it by other...
---------- Post added at 02:55 AM ---------- Previous post was at 02:37 AM ----------
I'm trying to do this but without if=/dev/block/stl9. I don't know if I'm doing well...
How about some info on modifying or tweaking already compiled roms?
Say you want to remove some of the apps included with CoolDevXYZ's rom or modify some of the settings pre-install (e.g. build.prop tweaks, etc.). How do you tell the kernel these changes are intentional, not the result file corruption, infection or something?
This is a simple tool/script used to:
1. convert .jpg .png and .bmp files into the format used for the splash screen on your device.
2. Make a full backup/restore of your device.
3. Flash the new image to your device.
I have only tested this on the HTC Droid DNA, if anyone wants to test it for another device and post results that would be great.
This script is based on the work done by TrueBlue_Drew, but since I am on a Mac, I got tired of booting a virtual machine every time that I wanted to make a new splash screen. So I decided to "convert" his script to a bash script to make my life easier. After testing several boot screens and all of the functions myself to make sure they all work, I decided to share the script with everyone here on XDA. I have been using this site since I got my first Android phone just a few years ago (and it was a Motorola Citrus...one of the worst "smart" phones ever created!), and have learned a ton - I figured it is time that I start giving back to the community.
If you like my work, don't be afraid to click the "Thanks" button. If you see any way to improve the script or have suggestions for other functions, leave a comment. If you have a question about bash scripting or using adb, leave a comment (I may or may not be able to help, but I will try...and there are many others here that can help).
Thanks again to TrueBlue_Drew for writing a nice little batch file that got me started on the path to creating this tool for myself.
The flash/backup splash option should work for any HTC devices that use a 1080x1920 splash screen but has ONLY been confirmed working with the HTC Droid DNA (I will add others to the list if anyone else confirms they work. I am already thinking about a way to select an option for the boot screen size you want to convert in order for this to work on more devices. :fingers-crossed:
REQUIREMENTS
1. Written on Mac running OSX 10.9.1 (Mavericks), but should work on any OSX Mac
2. Rooted HTC device with S=OFF and Eng Hboot
3. 1080x1920 png, jpg or bmp image
INSTRUCTIONS
1. Download the attached zip and unzip it somewhere on your Mac.
2. Create or find the 1080x1920 image you want for your splash screen.
3. Go into the "Splash Flasher Mac" folder you unzipped and place your image
in the "place-image-here" folder.
4. Run the file "splash_flasher.sh" file in the terminal and follow the on screen instructions.
NOTE: At this time this does not support having more than one of the same image type in the "place-image-here" folder when converting and flashing. A fix for that is already being worked on, but didn't see it as a major issue right now since you can only flash one splash screen anyway.
NEW NOTE: I was finally able to get the multiple images in one folder working and have implemented it only for .png images (other file types coming with next version). So now you can dump multiple .png files in the folder and the program will create the boot images, name them using the original filename and move them to the "images" folder. The next part of this to figure out is how to select your screen size and create a boot image of that size. Stay tuned...not that it seems many people are tuned, but that's OK.
NOTE: VERSION 1.2 - Removed support for .jpg and .bmp files. Didn't see the need to support multiple file types. There is now a Photoshop template file included with the script. Just open in photoshop and add your image to the top layer (labeled as "Team Logo" because I am using that as my template for my sports teams splash screens). If your image is large and covers the HTC and Beats logos (and you want them in your splash screen), just move the layers around how you want them. The colors of the HTC letters can also be changed however you want.
RESERVED
Has anyone used this to create their own custom boot screen? I am just trying to figure out if I should continue working on this or not. If you have made your own boot screens, feel free to share.
I am also working on a port of this script to Linux and improving on the original for Windows that TrueBlueDrew created and I based my script on. Would there be any interest in that?
drakemata said:
Has anyone used this to create their own custom boot screen? I am just trying to figure out if I should continue working on this or not. If you have made your own boot screens, feel free to share.
I am also working on a port of this script to Linux and improving on the original for Windows that TrueBlueDrew created and I based my script on. Would there be any interest in that?
Click to expand...
Click to collapse
I have forgotten about this. I'm going to look at it today sometime. A Linux version would be AWESOME. Mac and Ubuntu is all I work on. I'm really surprised that more things aren't for the Linux os.
Sent from my HTC6435LVW using Tapatalk
I don't typically work with Windows, either...but I know there us still a large demand for making things easier for Windows users since a great majority of them are not as inclined to do stuff at the command line.
As long as there is one person interested, I will continue to work on this. Thanks for your reply.
Mav3rick40 said:
I have forgotten about this. I'm going to look at it today sometime. A Linux version would be AWESOME. Mac and Ubuntu is all I work on. I'm really surprised that more things aren't for the Linux os.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Mav3rick40, have you had a chance to check out the script on your Mac? Just wondering if you have any issues or recommendations for improvements. I have just completed a revision to the script to remove support for .jpg and .bmp images. I figured I would keep it simple with support for .png images since I feel they have the best quality of the three file types.
I am also hoping to finish the Linux version and post it tonight. If you would be willing to test, that would be great. I will probably start a new thread for that.
drakemata said:
Mav3rick40, have you had a chance to check out the script on your Mac? Just wondering if you have any issues or recommendations for improvements. I have just completed a revision to the script to remove support for .jpg and .bmp images. I figured I would keep it simple with support for .png images since I feel they have the best quality of the three file types.
I am also hoping to finish the Linux version and post it tonight. If you would be willing to test, that would be great. I will probably start a new thread for that.
Click to expand...
Click to collapse
Not yet hopefully tonight. I got busy with school work.
Sent from my HTC6435LVW using Tapatalk
Mav3rick40 said:
Not yet hopefully tonight. I got busy with school work.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
drakemata said:
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
Click to expand...
Click to collapse
Ok cool. Yeah I'm going to school for programming.
Sent from my HTC6435LVW using Tapatalk
drakemata said:
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
Click to expand...
Click to collapse
is there anything special I need to do to make this run? every time I try to open splash_flasher.sh it opens up in Xcode.
Mav3rick40 said:
is there anything special I need to do to make this run? every time I try to open splash_flasher.sh it opens up in Xcode.
Click to expand...
Click to collapse
You need to navigate to it from the terminal and do ./splash_flasher.sh
Sent from my Droid DNA using Tapatalk
I figured it out after playing around with it for a couple of hours.
Sent from my HTC6435LVW using Tapatalk
Glad to see you figured it out. I am trying to convert this over to an Applescript app as well as working on my Linux version and making new splash screens for all sports teams (which was a much bigger undertaking than I thought it would be).
If you have any suggestions for improving the script or for additional tools that should be added, I would appreciate the feedback.