Annoyed with the volume bug on your Galaxy Nexus? Well, i'm very proud to present the forthcoming official fixed boot image which resolves this problem. In order to flash this boot image, you need your bootloader to be unlocked at this time (use './fastboot-windows oem unlock' (or the appropriate version for your machine, included in the download). Note that the OEM unlock sequence wipes your device.
APPLY THIS AT YOUR OWN RISK! This is still in a testing phase internally. Although it works great for us, well, you never know.
Volume Bug Fix r3 - DOWNLOAD - MD5: 292ba3630f475b2f779a19057649200a
How to use - Windows, Linux and OSX
- Download the zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'install-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-mac.sh' followed by './install-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-linux.sh' followed by './install-linux.sh'
Please don't rehost this zip file - if you want to link to the fix, please link to this topic. That's all I ask. Enjoy!
P
Thanks a lot for your effort!
Does OEM unlock touch my guarantee?
Thanks Paul, I get the phone tomorrow morning & thanks to you we already have our hands on the fix. Thanks a million!
You can reverse the unlock with lock when required;
./fastboot-windows oem lock
I'm very curious as to whether the volume bug is also fixed for the bootloader, and if it affects CPU load in any way, anyone tested something along those lines yet?
Rubu said:
I'm very curious as to whether the volume bug is also fixed for the bootloader, and if it affects CPU load in any way, anyone tested something along those lines yet?
Click to expand...
Click to collapse
Me too. Can anyone confirm?
Sent from my Sensation using XDA App
This doesn't fix the bootloader, doesn't seem to affect the device in any other way.
P
paulobrien said:
This doesn't fix the bootloader, doesn't seem to affect the device in any other way.
P
Click to expand...
Click to collapse
I'm pretty sure you have tested the fix. Have you been able to reproduce the bug with this version ? (Other than in the bootloader) One word from you and I might buy the Nexus ;-)
Paul if you dont mind i will repack it to zImage flashable mod because your stock boot.img will disable all tweaks in my ROM if people flash it.
Sent from my HTC Sensation Z710e using Tapatalk
mike1986. said:
Paul if you dont mind i will repack it to zImage flashable mod because your stock boot.img will disable all tweaks in my ROM if people flash it.
Sent from my HTC Sensation Z710e using Tapatalk
Click to expand...
Click to collapse
Sure, that's what i've done for MCR, as long as you give appropriate credit that's cool!
P
And what's new kernel version? Or what's the base number it came from?
i have just applied this patch.
will report back if this helps.
mike1986. said:
And what's new kernel version? Or what's the base number it came from?
Click to expand...
Click to collapse
Still 3.0.1.
P
Thanks in advance(Nexus on its way)
With all credits to paulobrien, who delivered this stock kernel to us, I made recovery flashable .zip with zImage file (kernel) instead of whole boot.img, because I do some changes to ramdisk (another part of boot.img) and by flashing default boot.img over my ROM you will loose all my tweaks. Also there are no changes to ramdisk, volume button fix in only zImage related. So you can grab it from here
Just flash it in recovery. You can flash it on any ROM, not only mine.
Hope we get the updated kernel source soon!
P
paulobrien said:
This doesn't fix the bootloader, doesn't seem to affect the device in any other way.
P
Click to expand...
Click to collapse
Thanks for all your hard work! Cant wait for my GN, i hope ill get it this week!
Can you pleas tell me whats wrong with the bootloader? I only know the bug with the volume but ive never read something about bootloader bug ...
Thanks in advance
lichti1901 said:
Thanks for all your hard work! Cant wait for my GN, i hope ill get it this week!
Can you pleas tell me whats wrong with the bootloader? I only know the bug with the volume but ive never read something about bootloader bug ...
Thanks in advance
Click to expand...
Click to collapse
The phone suffers from the volume bug even when it's in the bootloader. A lot of people think now it could be a hardware problem because there isn't much going on the software side in this state.
Which means if it is a hardware problem and you fix it with a software patch then it could still cause some problems under the hood. For example the phone doesn't sleep proberly while it is in a 2G area.
But according to Paul it doesn't cause any reaction on the phone. Which makes the bug really strange.
Edit: At least for me.
Paul,
The .bat file is "fastboot boot *.img", which i understand wouldn't be permanent, can we also "fastboot flash boot *.img"
Cheers
ande_uk said:
Paul,
The .bat file is "fastboot boot *.img", which i understand wouldn't be permanent, can we also "fastboot flash boot *.img"
Cheers
Click to expand...
Click to collapse
i have manually run fastboot flash boot <image> on mine, and it worked.(i also backup a copy of my boot.img before hand just incase).
i believe what paul is trying to do is just a temporary fix (running it once) untill google release a proper update.
Related
Universal Xoom Root
Thats right, this method will work for any xoom on any update - Including future updates!!!
Note: Unlike the similar method floating around on here, this also gives you an unsecured boot image.
-- Please Note: this thread is still a work in process and has been sped up by the arrival of the 4g Xooms --
Current requirements: adb & fastboot have been setup and you have an external sdcard for your xoom.
1. Setting up adb & fastboot
Coming Soon! (If you want to write this section for me and pm me it, thats fine !)
2. Downloading the rooting-update zip file.
Download the zip file from here.
Now place this on your external sdcard. - Sorry this is a requirement at the moment, like I said this is a bit rushed.
3. Flashing recovery
1. Download this Recovery image.
2. If your device is locked, now is a good time to unlock it.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
3. Flash recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
4. Flashing the Xoom-Universal-Root.zip file.
If you're in clockwork mod recovery you can continue (This recovery image will say it is clockwork mod) . If you're not looking at clockwork mod, then you need to repeat step 3 again.
In cwm, go into "install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Reboot your device and then welcome to your rooted device!
Downloads
Universal Xoom root - version 1.0
This was also tested on a 4G Xoom and is working 100%.
I'll take this one as well....
Came just in time, sol. My friends' Xoom needs a-rootin'.
solarnz said:
This was also tested on a 4G Xoom and is working 100%.
Click to expand...
Click to collapse
Will run this when I get home. After root would it be safe to reload tiamat hammerhead.
jsa11ey001 said:
Will run this when I get home. After root would it be safe to reload tiamat hammerhead.
Click to expand...
Click to collapse
Went smooth just ran home on lunch and ran adb. took like 10 min. you the man. Still wondering about Hammerhead.
By any Xoom... does that mean the country of the Xoom doesn't matter? Because I am currently still working on my Xoom Heaven stickied thread, and this would be an amazing addition to my thread. It will be much less confusing for all when it comes to rooting. I was working on adding Euro models rooting guides next, but an any Xoom and any model rooting method is awesome! And it would result in a lot less semi bricks.
Correct. As long as the xoom can be unlocked and cwm works, this tool should work!
solarnz said:
Correct. As long as the xoom can be unlocked and cwm works, this tool should work!
Click to expand...
Click to collapse
Awesome! Thank you. I just wanted to make sure of this before I linked it up on my thread. It's good to know this will work for future releases. Finally, a real rooting method that will always stay current. Team Tiamat wins!
Correct. As long as the xoom can be unlocked and cwm works, this tool should work!
Click to expand...
Click to collapse
Are all zooms unlockable or can some not be unlocked?
HTC wildfire cyanogenmod nightly
hboot -1.01 s-off xtc clip
banny7000 said:
Are all zooms unlockable or can some not be unlocked?
Click to expand...
Click to collapse
All XOOMs are unlockable, just need to get into fastboot, run fastboot oem unlock, press volume down then up, then press volume down then up again and now your XOOM is unlocked.
@solarnz - if no one did the adb setup and configuring yet, I won't mind typing it up and send it your way.
Nice. Worked perfectly. Cipe Niw.
I'm going to sound real noob here even though I've flashed and rooted a few times with various ROMs but...
If I root a stock ROM will it prevent the OTA updates from working?
Cheers
Works fine on a 3.1 Canadian Xoom thanks. I was looking at the script and was wondering does this patch the current boot partition on the fly, just curious.
WOW!!!
This is HUGE!
You've just obsoleted probably 15 - 20 percent of the entire Xoom development section!
Thanks so much for continuing to make it easier to get other Xoomers on board the Root Express train to Android Awesomeness!
scsa20 said:
All XOOMs are unlockable, just need to get into fastboot, run fastboot oem unlock, press volume down then up, then press volume down then up again and now your XOOM is unlocked.
@solarnz - if no one did the adb setup and configuring yet, I won't mind typing it up and send it your way.
Click to expand...
Click to collapse
Someone has already PM'd me text for this on xoomforums. I just haven't had a chance to copy it in yet.
Lakota said:
I'm going to sound real noob here even though I've flashed and rooted a few times with various ROMs but...
If I root a stock ROM will it prevent the OTA updates from working?
Cheers
Click to expand...
Click to collapse
Yes.
woolmonkey said:
Works fine on a 3.1 Canadian Xoom thanks. I was looking at the script and was wondering does this patch the current boot partition on the fly, just curious.
Click to expand...
Click to collapse
Yes, this does the modifications on the fly.
Wipes Xoom
I think the answer is yes, but I'll ask to make sure. Since this is changing the recovery/boot images, should I assume that it wipes the Xoom?
silvinoa said:
I think the answer is yes, but I'll ask to make sure. Since this is changing the recovery/boot images, should I assume that it wipes the Xoom?
Click to expand...
Click to collapse
Only if you haven't done fastboot oem unlock before.
Good, you make this work.
Are you inspired by my method, or you think of it all by yourself?
eddielo said:
Good, you make this work.
Are you inspired by my method, or you think of it all by yourself?
Click to expand...
Click to collapse
I had actually intended to write this since the release of Android 3.2 on the wifi Xooms.
Hi Friends
Now You can see your Black Screen Recovery!!
NO More tension of flashing Rom's With Black Screen Recovery.
But again a bad News This is only visual with PC Not in phone .
Days are gone with BLACK SCREEN RECOVERY
Here how it works!!
You need some files.
1.Download Adb Files form here
2.Download This [email protected] Tool,Thanks To RiboComments
3.Extract Adb "c:\ " on your pc Creating Folder Adb.
4.Copy [email protected] From your Downloaded folder to desktop.
5.Double click on [email protected] ,and locate the adb.exe form c:\ when asked.
6.Connect you phone using "Charge only mode" with usb debug on.
7.Follow The UI of [email protected] and when will you get your phone screen appearing.
8.Now restart your phone in Recovery mode.
And enjoy The Pleasure Of CWM.
REMEMBER: PLEASE DISABLE ANY FIREWALL (If Getting connecting error) IN YOUR PC AND INSTALL THE LATEST JAVA SDK TO MAKE WORKING THIS SOFTWARE.
Sometime if not working in CWM .
Do the following Troubleshoot .
1. Disconnect your phone.
2. Close [email protected] And
3. Delete all Files In temp Directory Of your PC. (Type " %temp% " Under search box of Start Menu or Under Run Command window) to navigate to Tempdirectory Directly .
4. Now connect Your phone With CWM recovery screen and START [email protected]
5.Click on Restart ADB . (More than once if needed)
This Tool Is Not Mine.
Original Thanks Goes to creator of this Tool RiboComments For his Great Work.
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
BigChillin said:
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
Click to expand...
Click to collapse
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.
And rajanand is the only one that provides a solution.
I'll try the solution of rajanand and I will post the results
Greetings.
Sorry for my bad English.
rajanand said:
Hi Friends
Now You can see your Black Screen Recovery!!
NO More tension of flashing Rom's With Black Screen Recovery.
But again a bad News This is only visual with PC Not in phone .
Click to expand...
Click to collapse
Works great ! Thanks again.
Works great ! You're the BOSS.:good::good:
Thanks a lot.
Aww yeah! Great job sir!
BigChillin said:
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
Click to expand...
Click to collapse
little knowledge it always dangerous to health, so tk care of ur health.
Thanks aunto for commenting on my useful post.
Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.
Sent from my Marvelc
Do not download! Maybe a VIRUS!
Never heard something about this iusses.
Why should I disable my FIREWALL?
Sounds like a virus.
matt5eo said:
Never heard something about this iusses.
Why should I disable my FIREWALL?
Sounds like a virus.
Click to expand...
Click to collapse
sometimes it disconnects itself due to continuous Data transfer in between adb and phone......so
To avoid interruption between ADB and Your phone.
i personally recommend it, rest is on your side.
BigChillin said:
Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.
Sent from my Marvelc
Click to expand...
Click to collapse
Go to market and purchase brand new Lot of WFS,you will surely find black screen problem in that.
Please Stop Arguing..further ,i am not here to entertain such comments.
rajanand: This works great!! thanks
To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help
Anto2 said:
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.
Click to expand...
Click to collapse
You are not the one with this problem I have blank CWM Recovery too.
Rajanand helped me many times.
ngoralph said:
rajanand: This works great!! thanks
To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help
Click to expand...
Click to collapse
Thanks for your support.
marchelius said:
You are not the one with this problem I have blank CWM Recovery too.
Rajanand helped me many times.
Click to expand...
Click to collapse
Thanks dear for support , hope you all be with me always .
rajanand said:
Thanks dear for support , hope you all be with me always
Click to expand...
Click to collapse
Of course I will
But, I have now another problem to solve: please look : http://forum.xda-developers.com/showthread.php?t=1785689
I have blank screen with older versions of CM 7 !!!
marchelius said:
Of course I will
But, I have now another problem to solve: please look : http://forum.xda-developers.com/showthread.php?t=1785689
I have blank screen with older versions of CM 7 !!!
Click to expand...
Click to collapse
try these steps and try to replace boot.img
(by copying boot.img file only inside the folder),from any other working roms
http://forum.xda-developers.com/showthread.php?t=1749212
older version of boot.img incompatible with black screen devices.
I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:
1. Why the blackscreen occurred
2. Fix it
3. Take preventative measures so that it would not occur again.
But that's just me. I wouldn't build a tool to propigate my device's bad behavior.
Rob
Sent from my HTC_A510c using Tapatalk 2
rajanand said:
try these steps and try to replace boot.img
(by copying boot.img file only inside the folder),from any other working roms
http://forum.xda-developers.com/showthread.php?t=1749212
older version of boot.img incompatible with black screen devices.
Click to expand...
Click to collapse
Not working, same sh*it
insink71 said:
I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:
1. Why the blackscreen occurred
2. Fix it
3. Take preventative measures so that it would not occur again.
But that's just me. I wouldn't build a tool to propigate my device's bad behavior.
Rob
Sent from my HTC_A510c using Tapatalk 2
Click to expand...
Click to collapse
its fully upon users ,weather they are using it on firewall on or off.(it will work on both the conditions if the "adb" have the access to the port)
its just a recommendation from my side. That's it
Its fully safe from my end and free from any type of virus.
as i have already said this tool is not mine.Please consult the owner of this tool linked on first page of this Thread For future reference.
i don't know why this "black screen recovery" Problem is there with all the newly manufactured WFS.
Why occurred?
1. I am rooting and reflashing CWM on old wfs without any problem.(even rooted for the first time)
2. the same above is not working with any newly manufactured devices.(all working well but With a black CWM recovery)
3. My doubts are pointing, its a fault of hardware,or any kind of display adapters Upgradation from HTC Side.(May be HTC is planning to give supports like ICS etc for future)
4.Also Some rooting errors can be the catch,(Again if HTC upgraded something)
4.CWM is fully working without any error.(Blindly)
5.only the four keys are lighting up,
6.This tool is The only option in that case to flash any custom ROMS.
This is just a recovery I compiled from the latest available code from the CM10 source. It does not offer any major upgrade in function from ACL's latest cwm recovery, but is slightly aesthetically different.
Installation:
Download from link below, flash with fastboot
Code:
fastboot flash recovery recovery.img
Bugs:
recovery.log may show these errors:
Code:
failed to open /sys/class/android_usb/android0/state: No such file or directory
but it does not affect usb or mass storage afaik.
Download:
recovery_cwr_6.0.1.3.img - 3.36 MB 9912
Credits: Everyone involved in Android development.
Feel free to report any bugs and enjoy.
works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?
Ranomez said:
works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?
Click to expand...
Click to collapse
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea
jianC said:
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea
Click to expand...
Click to collapse
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get
Ranomez said:
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get
Click to expand...
Click to collapse
In that case, just choose "no".
sorry to revive this old thread, but i just realised this recovery has a big problem and wanted to warn anyone who may want to try it: most blckups made by it have md5 mismatch, i meant i got that error at 14 out of 15 backups created.
EDIT1: i had a look at the backup folder and as far as i can see some .img files are not generated (i think cache and recovery) and also the nandroid.md5 is not generated, but that is easy to fix by generating it by urself throu adb.
Battery loading Led not working
The Led is not working with this recovery while charging.
I guess the Battery is not loading, too.
Edit - This is only, when phone is off. -
Hope this can be fixed.
regards
Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
https://github.com/jianC/android_device_htc_rhodium
jianC said:
Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
http://ge.tt/1gVK1FS/v/0?c
Click to expand...
Click to collapse
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.
wizardknight said:
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.
Click to expand...
Click to collapse
Thanks for the links, but I do not have a rhod for testing anymore.. maybe someone adventurous could take a stab at it .
Hi there!
I hope you guys can help me. The USB port of my GNEX seems to be broken and I would therefor like to get it repaired/ replaced.
The only problem is, that I'm using the Paranoid Android rom and now I've to get it to a factory image without being able to connect the phone to a pc. I've still a bit more then 50% battery, my plan was to download the image and then flash it. The bootloader doesn't need to be relocked, it already came locked.
So I know this is possible but apart from the official factory image, that I can't flash with recovery, I couldn't find any suitable image/rom/file.
So, does anybody have an idea on how to proceed here? Or a link to a recovery flashable factory image/rom?
Many thanks in advance!
Edit: I plugged in my phone turned off on the USB charger and strangly it is charging up... So seems to work with phone of but not when the phone is turned on
You can flash images via terminal there's a guide around here somewhere,
Sent from my Nexus 4 @1.72 GHz on Stock 4.2.2
Ok so I found somethnig...
I downloaded the latest official Google factory image and extraced all the images so now I have these images:
- boot
- bootloader-maguro-primelc03
- radio-maguro-i9250xxlj1
- recovery
- system
- userdata
So now I put these images in /sdcard/
The terminal command to flash something would be:
su
flash_image recovery /sdcard/name-of-recovery.img
Replacing "recovery" with the thing that I want to flash and the path with the respective path of the image
Is this right until now?
Is there a right order that I must follow when flashing or is that irrelevant?
lukasb9000 said:
Ok so I found somethnig...
I downloaded the latest official Google factory image and extraced all the images so now I have these images:
- boot
- bootloader-maguro-primelc03
- radio-maguro-i9250xxlj1
- recovery
- system
- userdata
So now I put these images in /sdcard/
The terminal command to flash something would be:
su
flash_image recovery /sdcard/name-of-recovery.img
Replacing "recovery" with the thing that I want to flash and the path with the respective path of the image
Is this right until now?
Is there a right order that I must follow when flashing or is that irrelevant?
Click to expand...
Click to collapse
it will not work for you, you need "flash_image" file in your phone.
use dd command (search for it)
Hey guys!
I fiddled around a bit on the usb port and got it to work...so I just reset everything with fastboot!
Thanks nevertheless for your help
Can be closed.
lukasb9000 said:
Hey guys!
I fiddled around a bit on the usb port and got it to work...so I just reset everything with fastboot!
Thanks nevertheless for your help
Can be closed.
Click to expand...
Click to collapse
edit : whoops no no wrong thread lol
phaze3131 said:
thanks for a wasted thread, no help to me
Click to expand...
Click to collapse
Yeah, shame on everyone that posted in this thread. How dare they not be clairvoyant enough to be able to predict that someone would come along 3 months later with the same problem and manage to find this thread, somehow missing others that likely would answer his/her question (including at least one thread stickied in this forum). Especially after the OP managed to solve his/her problem, so assistance wasn't necessary anymore.
[not sarcasm] Thanks for the wasted post. No help to meanyone. [/not sarcasm]
cupfulloflol said:
Yeah, shame on everyone that posted in this thread. How dare they not be clairvoyant enough to be able to predict that someone would come along 3 months later with the same problem and manage to find this thread, somehow missing others that likely would answer his/her question (including at least one thread stickied in this forum). Especially after the OP managed to solve his/her problem, so assistance wasn't necessary anymore.
[not sarcasm] Thanks for the wasted post. No help to meanyone. [/not sarcasm]
Click to expand...
Click to collapse
whoops wrong thread lol my bad
good info!
check this out for ppl who want to know how to do this!
http://forum.xda-developers.com/showthread.php?p=28238970#post28238970
The disclaimer is attached to the script file. When you open them, a disclaimer will show up with 2 choices: accept them or exit.
Hi guys
I'm here for give you a batch script (with repo) that works on all windows system without installing .net framework or other software!
The only thing that you need is WinRAR 5.30 or up! Otherwise you will aren't able to unpack all the folder.
I've made this because i see some people that wants to mod his One X, but they can't due to unknown errors with some tools.
This tool will do these functions:
*Bootloader Unlocker/Locker!
*Fastboot Recharger!
*Helps to root your device!
*Recovery Flasher! (New layout and Old layout, no need to download anything!)
*Guides to flash a custom rom!
*boot.img extractor and autoflasher!
*CID/MID Reader!
*Fastboot Emergency Recovery!
*Some accurates guides! (provided by @teemo)
*Integrated FAQ and How To!
*Fastboot&ADB status Connection Verifer!
*And much much more! Stay tuned!
Special contributors:
@teemo for providing all stuff needed like recoveries, guides and others.
Downloads and repo:
MEGA LINKS:
V1.0 Stable: https://mega.nz/#!NddVkTTb!aINZPwACwHgAYgpA4L8tR86dobJ9zGuGpY-5In3YE7E
Beta3: https://mega.nz/#!AFkEFJIL!jI3EJtJhbdiT_Q8I7tb3qnDINNj3os8CYNtB_htHGvA
Beta2: https://mega.nz/#!MUlSgZwI!SPaAKOkgt-xCHyzMwb6rJmzW0mQY66N8L87S5JbgZVs
Beta1: https://mega.nz/#!tRMDHDAZ!Cv09ijHB5WJrp5zNL4gzUyz3cv_1qy1X06Lx_e_t65k
Google Drive Links:
V1.0 Stable: https://drive.google.com/file/d/0BzLuAF-eWwH9VnIzNkxEbldsTjQ/view?usp=drivesdk
GitHub Repo: https://github.com/Giovix92/onex-modder.git
Tested OS:
*Windows 98 (Yeah, on VM )
*Windows XP (All SPs)
*Windows Vista (All SPs)
*Windows 7 (All SPs)
*Windows 8
*Windows 10
Download it and test if all works! If there is any bug, tell me! If anyone goes wrong, i'm happy to help you!
Please don't modify the batch code, or you can harm your device/pc.
Changelog:
V1.0 Stable: Added 5 more function. Check the new features pressing 11 on the menù!
V1.0b3: Added 7 more functions. Now there is 11 items + 2 hide on the menú. Check the new features pressing 11 on the menú!
V1.0b2: Added 2 new functions: Fastboot & Adb status connection verifer and Fastboot phone recharger
V1.0b1: Initial Release
Enjoy! )
How to use:
You don't need to setup anything.
You don't need .NET Framework. Simply install WinRAR 5.30 or up, download my rar package, decompress it and open the batch file. Make sure you have this tree:
|OneX_Modder (Folder)
|---OneX_Modder.bat
|---Resources
At first screen there is the disclaimer. After the disclaimer, there are some options:
If you want to unlock your bootloader, press 1. It will guides on how to. It includes an Unlock_code.bin auto flasher. )
If you want to flash a custom recovery, press 2. It will flash a custom recovery in the menú. Simply select a recovery, type Y (yes) and wait for the flashing. It's very easy. No more annoying manual-flashing
If you want to root your device, press 3. There is an explained how to.
If you want to flash a custom rom, press 4. There is an boot.img extractor and flasher and a guide provided by @teemo (thanks).
If you want to verify if the pc recognize the device, press 5, and the tool will show you the adb&fastboot status.
If you are desperatly in need to flash a rom but you haven't enough power, no more worries!! Reboot your phone in fastboot mode, connect to the pc, press 7 and your phone will be recharged!
If you want to read the about, press 9.
If you want to flash a new RUU, but you have the Bootloader unlocked and you need to flash a new RUU, press 8 and your bl will be relocked!
If you want to see the lasts changes, press 11.
If you want to flash a custom rom, but your hboot is older, press 0 and you will be guided. You need only to follow the first steps. The final process is automated!
FAQ:
Q: I have a problem with this tool! How can i do?
A: Don't worry! I will help you in any situation!
Q: Why some numbers aren't show?
A: They aren't shown because i'm working on their sections. I will add in new betas
Q: Really i need WinRAR? Why?
A: Yes, because the .rar archive is a RAR5 archive. Only WinRAR can open them.
Q: I really love it! How can i support you?
A: Simply press thanks button!
Q: How can i contact you if i have a problem with this tool?
A: Only this thread, because if a user has the same problem than you, he will find easily the solution without making a new post.
Added beta2! It has new functions: please check changelog (op post)
Thank you. Please place instructions of use/setup in op
nchc said:
Thank you. Please place instructions of use/setup in op
Click to expand...
Click to collapse
Yes, sure! There's no setup. I will add in 2nd post. Thanks for the tip.
Added an How to and FAQ. Enjoy! The beta3 is already ready for uploading! I will upload it the next week.
Guys, tell me your favourite colours for this little batch script and i will create 3 modded version with different colours! The beta3 will be published the next week due to much much work on it. It will has: HBOOT Upgrader, an how to and more more functions! The size is decreased of 30%. Sorry for this little problem
Some trouble.
Hello and thank you for your effort! I tried to flash twrp2853-endeavoru-NewLayout over the old one but while in recovery, the phone stays stuck at twrp hox welcome screen. Any idea of how can I pass this and access the twrp menu?
b12rtc said:
Hello and thank you for your effort! I tried to flash twrp2853-endeavoru-NewLayout over the old one but while in recovery, the phone stays stuck at twrp hox welcome screen. Any idea of how can I pass this and access the twrp menu?
Click to expand...
Click to collapse
Hmmm. Isn't passing at all TWRP welcome screen? The phone can boot up in fastboot? If yes, Try this: go on Resources-ADB_TOOLS. Right click on ADB_TOOLS and select command prompt. Then reboot your phone in bootloader mode and type: fastboot erase cache , press enter, type fastboot reboot bootloader or fastboot reboot-bootloader and try to access in recovery.
P.s. tomorrow i will publish beta3 with HBOOT Upgrader and much much more!
Giovix92 said:
Hmmm. Isn't passing at all TWRP welcome screen? The phone can boot up in fastboot? If yes, Try this: go on Resources-ADB_TOOLS. Right click on ADB_TOOLS and select command prompt. Then reboot your phone in bootloader mode and type: fastboot erase cache , press enter, type fastboot reboot bootloader or fastboot reboot-bootloader and try to access in recovery.
P.s. tomorrow i will publish beta3 with HBOOT Upgrader and much much more!
Click to expand...
Click to collapse
Thanks for reply! I've just tried what you suggested but in recovery I still can't pass the twrp ''hox teamwin big'' screen. If I put the old layout back everything is fine again but can't flash any newer rom.
I must tell you though, that I've tried to install it before using different ways but I had the same result There's no way to pass the twrp new layout's start scxreen. So I guess there's something wrong on my side... (I had cwmr before, it may be that?). If you have any other suggestion i'll be happy to try, If not I'll try to dig more.
Once again, thank you for your work and support.
b12rtc said:
Thanks for reply! I've just tried what you suggested but in recovery I still can't pass the twrp ''hox teamwin big'' screen. If I put the old layout back everything is fine again but can't flash any newer rom.
I must tell you though, that I've tried to install it before using different ways but I had the same result There's no way to pass the twrp new layout's start scxreen. So I guess there's something wrong on my side... (I had cwmr before, it may be that?). If you have any other suggestion i'll be happy to try, If not I'll try to dig more.
Once again, thank you for your work and support.
Click to expand...
Click to collapse
Hmmm... Probably the zip is damaged. The TWRP is flashed successfully or there are errors? No, the cwm doesn't make any problem. I will try to view if there is a problem on the code. Thanks for your test
Giovix92 said:
Hmmm... Probably the zip is damaged. The TWRP is flashed successfully or there are errors? No, the cwm doesn't make any problem. I will try to view if there is a problem on the code. Thanks for your test
Click to expand...
Click to collapse
I don't know for sure, but I rather think your zip file is ok. The flashing was ok, no errors. It's probably my phone. Of course, a double check on the code doesn't hurt, it just might be loosing time for nothing. Of course, if you will come back with something new tomorrow I will try my luck again
b12rtc said:
I don't know for sure, but I rather think your zip file is ok. The flashing was ok, no errors. It's probably my phone. Of course, a double check on the code doesn't hurt, it just might be loosing time for nothing. Of course, if you will come back with something new tomorrow I will try my luck again
Click to expand...
Click to collapse
I will check the code asap. In 10 minutes i will update you... No, if it's your phone other recoveries doesn't boot at all. Anyway, i will check. Retry and update me. Good luck!
Edit: I've checked all the code, of all recoveries.Now i will add stock HTC Recovery (if anyone wants the stock recovery). Anyway... I will add another TWRP with New Layout Support.
Edit2: Check the beta3!
Beta3 is out! Check the new version! It has 7 more functions. You can find them in OP post at Downloads section!
b12rtc said:
I don't know for sure, but I rather think your zip file is ok. The flashing was ok, no errors. It's probably my phone. Of course, a double check on the code doesn't hurt, it just might be loosing time for nothing. Of course, if you will come back with something new tomorrow I will try my luck again
Click to expand...
Click to collapse
Man, type fastboot getvar all into your cmd, and post here the result.
Guys, tell me any idea for the first stable. If you want any function on this script, tell me and i add them! (S-OFF is possible only on HTC One X+ and AT&T HTC One X)
Giovix92 said:
Guys, tell me any idea for the first stable. If you want any function on this script, tell me and i add them! (S-OFF is possible only on HTC One X+ and AT&T HTC One X)
Click to expand...
Click to collapse
Any chance of incorporating the ability to get Kali Nethunter on our One X(https://cyberkryption.wordpress.com/2014/10/13/the-quest-for-kali-nethunter-part1/)
pleomaxell said:
Any chance of incorporating the ability to get Kali Nethunter on our One X(https://cyberkryption.wordpress.com/2014/10/13/the-quest-for-kali-nethunter-part1/)
Click to expand...
Click to collapse
Hmmm... I've read all the steps... But i don't know kali nethunter. I know only Kali for pc. If you explain me because you want it i will add them in a separate batch that will be called by the main program. The main step is to build the cm... the 2nd is more difficult... The 3rd too... Please explain me. Thanks in advance.
Giovix92 said:
Hmmm... I've read all the steps... But i don't know kali nethunter. I know only Kali for pc. If you explain me because you want it i will add them in a separate batch that will be called by the main program. The main step is to build the cm... the 2nd is more difficult... The 3rd too... Please explain me. Thanks in advance.
Click to expand...
Click to collapse
I don't know how to explain it to you because I am not a programmer. I tried to follow that guide but got scared because it looked a bit complex.
pleomaxell said:
I don't know how to explain it to you because I am not a programmer. I tried to follow that guide but got scared because it looked a bit complex.
Click to expand...
Click to collapse
Okay, so... The process for me is a bit complicated because now i'm a win user, and not a linux user due to my bad pc (only 1gig of ram, single core 1.66GHz), but i can create an .sh script that can do this process automatically. Maybe if this work i will create some .sh script to build some custom rom . I need only to write the code that is in the guide (maybe with 2-3 sec of delay too and some echo) and optimizing them with some request. Anyway, stay tuned!