Droid RAZR Forum - Motorola Droid RAZR Community - Droid Razr HD Development
http://www.razrforums.com/forum/
All development for the Razr HD can be found in here!enWed, 01 May 2013 10:55:39 GMTvBulletin60http://www.razrforums.com/forum/images/styles/DarkCore/misc/rss.pngDroid RAZR Forum - Motorola Droid RAZR Community - Droid Razr HD Development
http://www.razrforums.com/forum/
<![CDATA[[ROOT] Motochopper: 4.1.2 by djrbliss]]>
http://www.razrforums.com/forum/droid-razr-hd-development/3370-root-motochopper-4-1-2-djrbliss.html
Wed, 24 Apr 2013 21:20:57 GMTALL credit for this goes to the amazing djrbliss
"After publishing yesterday's Motorola bootloader unlock tool, I feel bad that some people are running the unrooted 4.1.2 build for Razr HD. Let's fix that.
This exploit will root the Razr HD, Razr Maxx HD, Atrix HD, Photon Q, and Razr M, regardless of what build they're running. While these are the only supported Motorola devices, it will also root lots of other non-Motorola devices...feel free to try it and see. ;-)
But first, I thought I'd reflect a bit on the state of the rooting/modding community and my involvement in it. I published my first Android root exploit almost two years ago for the Droid 3 (it also re-rooted a number of other earlier devices). Since then, I've rooted every major Motorola device that's been released, including the Bionic, Razr (multiple times), Droid 4, Xoom 2, Atrix HD (multiple times), Razr HD, and Razr M. With the release of this exploit, every major Motorola device in existence has a viable public root method, and the most recent models now have an unlocked bootloader.
I see this as the end of an era for Motorola rooting and modding. At this point, it is significantly more difficult to find vulnerabilities that may be used to root Motorola devices than when I started two years ago, due to fixes for the all the bugs used in previous exploits. It has gotten to the point where there may not be a "next time" for publishing a Motorola root exploit. Of course vulnerabilities still exist, but as the pool of bugs shrinks, the number of people capable of finding them grows smaller and the time investment required increases. As a result, I have no plans to continue publishing Motorola root exploits after this release.
I have hopes that the acquisition of Motorola by Google will gradually lead to changes in policy allowing more open devices. If it doesn't, I encourage everyone to speak with your wallets when purchasing your devices: if an unlocked device is important to you, buy an unlocked device instead of expecting someone to accomplish a difficult hack.
The Motochopper exploit is attached to this thread. It may be used as follows:
Extract the entire contents of the zip file.
If you are using Windows, ensure you have installed the latest Motorola USB drivers available for your phone.
Ensure USB Debugging mode is enabled on your device.
If you are using Windows, navigate to the extracted directory and execute "run.bat". If you are using Linux or OS X, navigate to the extracted directory in a terminal and execute "./run.sh".
As always, future OTA updates may remove the ability to regain root access, so proceed with caution when updating. Enjoy!"
Changelog:
Updated 4/8/13 20:17 EDT: For those who were having trouble or just want to try out the reloaded version. Download Version 2. It should get rid of the install-recovery.sh problem for those having issues with the recovery sticking. Please report errors so I can fix. Thank you
Updated 4/8/13 21:17 EDT: Updated TWRP to 2.5.0.0 for both flash methods
Updated 4/9/13 9:42 EDT: rewrote and consolidated. Thanks to Hashcode for locating a pretty big bug.
Updated 4/16/13 16:56 EDT: added more code to help with recovery's that won't stick through reboot, removed uneeded code for flashing back to stock. Updated tutorial to reflect changes
If you do not want to one click this. I will now explain to you how it works and you can try it on your own. I want to help teach you guys how to do this as well as not give you...er bad help.
For the sake of saving time, I will provide you with a copy of ADB (Android Debugging Bridge) so you do not have to go through the time of downloading the entire Android SDK, Download that first here, Place it on your desktop and UNZIP it. However, should you wish to learn how to properly install and set up the Android SDK, please see tucstwo's thread HERE
Also, on the quest to save time. I (tucstwo) have zipped up and will include all 3 recoveries for you. Download here, Unzip those and place all 3 into the ADB folder you just unzipped.
Next, I would like you to press and hold Shift and RIGHT click on the ADB folder. Select from the contextual menu "Open Command window here". This will open a command line for you, already browsed to the folder on your desktop. Now, the easy part.
Ensure you're phone is plugged into your computer, that you have all the necessary drivers installed and that USB debugging mode it ticked in Settings>Developer Options>USB Debugging.
Now we will run some commands and I will tell you what they do. So let's start with killing an previously running ADB deamon that may already be running:
adb kill-server
Next, we will connect to your device:
adb wait-for-device
If it hangs at this point, then you are having communication issues with your PC. Check your drivers, your wire, or untick and then retick Usb debugging. If we want to be doubly sure you can run
adb devices
If you are given what looks like a serial number, then we are indeed connected. If it just says "List of Devices" but no serial number, you are not connected, go back a step.
Now, we need to start communicating with the shell on your phone. And we are going to want to be running as root so we can complete the process. So next we will type
adb shell
su
You may be prompted with a Superuser prompt on your phone, Grant it permission. You will now be met with a new prompt something like [email protected]:/# We will then move on and mount /system, remember, no ADB prefix to these commands:
mount -o rw,remount -t ext4 /dev/block/system /system
Now, depending on what ROM you are on, some people had trouble with the recovery removing a script that motorola puts in place to over write any custom recoveries you may flash. So we are going to get rid of this file before we move forward.
rm /system/ect/install-recovery.sh
Also, the "Patch" that is stored on your phone that the aforementioned script would have flashed to erase your custom recovery
Ok, now that that's gone we need to back out of shell and get back to your windows CMD line. (Note, depending on your set up, you may need to run the exit code twice. Once to get out of SU and again to completely exit shell. If you are back to your original C:\user\me\desktop\ADB prompt then there is no need to exit again or you will close you Windows CMD. So:
exit
Ok, We are going to put the recovery of your choosing into a temporary location until we're ready to flash it. Keep in mind, you will need to use the name of the recovery you intend to flash. So if its CWM you're pushing cwmrecovery, if it's Team Win, then it's twrprecovery and if it's stock Motorola then it will be motorecovery. I will use CWM in my example, you just need to change the name so it reflects the recovery you are trying to flash.
It will proceed to tell you how long it took. Tip, if it says no such file or command, this means that the recovery of your choosing is not in the ADB folder that we put on your desktop. So now, we will flash it. but first back into shell
If you're really feeling brazen and are only using a Moto, Nexus, or HTC device. You could use fastboot to achieve the same deal. I find it to be a lot more work. But others for some reason find it to be easier. IDK? Anyway download the same set of recoveries here: Dev-Host - Razr HD Recoveries.zip - The Ultimate Free File Hosting / File Sharing Service, Only this time you will need an additional package that includes not only ADB files but also the Fastboot binary. Downloat that here Dev-Host - - The Ultimate Free File Hosting / File Sharing Service, UNZIP this to your desktop and place the recovery images into this folder!
Next, I would like you to press and hold Shift and RIGHT click on the ADB-Fastboot folder. Select from the contextual menu "Open Command window here". This will open a command line for you, already browsed to the folder on your desktop. Now, the easy part.
Ensure you're phone is plugged into your computer, that you have all the necessary drivers installed and that USB debugging mode it ticked in Settings>Developer Options>USB Debugging.
adb kill-server
Next, we will connect to your device:
adb wait-for-device
If it hangs at this point, then you are having communication issues with your PC. Check your drivers, your wire, or untick and then retick Usb debugging. If we want to be doubly sure you can run
adb devices
If you are given what looks like a serial number, then we are indeed connected. If it just says "List of Devices" but no serial number, you are not connected, go back a step.
Now, we need to start communicating with the shell on your phone. And we are going to want to be running as root so we can complete the process. So next we will type
adb shell
su
You may be prompted with a Superuser prompt on your phone, Grant it permission. You will now be met with a new prompt something like [email protected]:/# We will then move on and mount /system, remember, no ADB prefix to these commands:
mount -o rw,remount -t ext4 /dev/block/system /system
Now, depending on what ROM you are on, some people had trouble with the recovery removing a script that motorola puts in place to over write any custom recoveries you may flash. So we are going to get rid of this file before we move forward.
rm /system/ect/install-recovery.sh
Also, the "Patch" that is stored on your phone that the aforementioned script would have flashed to erase your custom recovery
Ok, now that that's gone we need to back out of shell and get back to your windows CMD line. (Note, depending on your set up, you may need to run the exit code twice. Once to get out of SU and again to completely exit shell. If you are back to your original C:\user\me\desktop\ADB prompt then there is no need to exit again or you will close you Windows CMD. So:
exit
From this point on, we need to be sure that the recovery of our choice is in our " C:\Users\me\desktop\ADB-Fastboot\ " folder. It's now time to reboot into our bootloader.
adb reboot bootloader
We will now issue 2 commands, one after the other to flash the new recovery. Again, I will use Clockworkmod as my example, but you will need to replace the commands with the recovery of your choosing.
fastboot erase recovery
fastboot flash recovery cwmrecovery.img
Next we will reboot our bootloader
fastboot reboot-bootloader
When this is finished, power down your device.
Next press and hold, Power & VOL- to boot ur phone up to the bootloader selection menu. From here, use Vol - to highlight "Recovery" and Vol + to select it. It is vital that you go into your new recovery BEFORE you boot up your device fully again.
Once you get booted up to your recovery of choice, you may now boot back into Android. You're done!
Again ALL credit to tucstwo, He, RAZRForums nor I, are responsible for what you do with your device. If you are not comfortable doing it manually, simple use the download at the top of this thread and run the auto installer.
]]>Droid Razr HD DevelopmentGoCliffGo05http://www.razrforums.com/forum/droid-razr-hd-development/3369-utility-flash-cwm-twrp-recovery-1-click.html<![CDATA[[ROM][Unlocked Bootloader] AOKP Unofficial XT925/XT926]]>
http://www.razrforums.com/forum/droid-razr-hd-development/3368-rom-unlocked-bootloader-aokp-unofficial-xt925-xt926.html
Wed, 24 Apr 2013 20:44:59 GMTALL credit to mikeyinid for this. Original thread here: [ROM] Unofficial AOKP 4.2.2 xt925/926 - xda-developers
TMC363 has successfully ported Carbon ROM to the HD/Maxx HD! Here is what he has to say about it:
This is a port of Team Carbons Rom for the VZW Razr/Maxx Hd. All credit for the creation of the rom is team carbons which is listed at the bottom of the page.
Thanks
Dhacker for fixing, creating, upating, and correcting and redoing my screw ups and making the changes to cause this beast to work even when his give-a-crap meter was at -60% and much more.
DroidTh3ory for spending 2 straight days setting the stuff up, trouble shooting with me, teaching me github step by step and much more.
WITHOUT THESE 2 GUYS THIS PORT WOULD BE NON-EXISTENT.
Bkjolly for helping with many different things both related to this and android in general.
CarbonRom is an aftermarket firmware based on the Android Open Source Project. The team is composed of former members of Team Liquid who have forked the code in an attempt to bring greater speed, better coding, and full authorship to code. We are in no way affiliated with Liquid0624. The rom was forked at Liquid beta 3.2.1 and has since undergone major code changes and modifications. Please note that on some devices the kernel is not yet linaro compiled.
Please feel free to look at, build, and use our code on CarbonDev GitHub
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Xposed Framework (May cause stability or performance issues - use at your own risk!)
Comprehensive speed enhancements, including Linaro -O3 and processor-specific optimizations
Unofficial Voodoo Sound support on Note 2 and i9300 devices.
Option to hide lockscreen hints
Carousel lockscreen
Customizable lockscreen buttons and sliders
Chronus clock widget
Customizable hardware and software keys
Transparent navbar and status bar
Customizable navbar ring
Navbar arrow keys
Navigation bar widgets
Customizable power menu
Notification power widget
Notification brightness adjustment
Customizable quicksettings panel
Statusbar mods including center clock and color
LCD Density
Theme engine
Quiet hours
Volume rocker music controls
Full Rotation
Customizable battery and notification light
More that haven't even been mentioned, and more to come!
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users!
For the best support please ask questions in the original thread!
Bugs:
Anything that the official carbon/cm roms currently have
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
ToxicThunder
winner0
RAZRForums is not responsible for what you do with your device
]]>Droid Razr HD DevelopmentGoCliffGo05http://www.razrforums.com/forum/droid-razr-hd-development/3360-rom-unlocked-bootloader-carbon-4-2-2-a.html<![CDATA[[ROM][Unlocked Bootloader] Pac Man Rom 4.2.2]]>
http://www.razrforums.com/forum/droid-razr-hd-development/3351-rom-unlocked-bootloader-pac-man-rom-4-2-2-a.html
Thu, 18 Apr 2013 02:45:10 GMTbkjolly has successfully ported pac man ROM from the Nexus to the HD! Here is what he has to say about it:
Warning this is an alpha build!!!
...bkjolly has successfully ported pac man ROM from the Nexus to the HD! Here is what he has to say about it:
Warning this is an alpha build!!!
This is a port bkjolly has been doing from the PACMan ROM, he in no way developed this ROM, he ported it to work with this specific device with the help of Dhacker and Hashcode. All credit for the ROM goes to the PACMan devs alone. As well as this thread, if you look at the bottom of the page you will find the OP that was created at xda and this was copied from.
Description:
After months of work, the long awaited PACman 4.2 ROM is ready for public released. This is still a work in progress (WIP) and there are many missing parts. Though the ROM is rock stable for average users, we are working on it daily to fill the missing parts.
Now what is PACman? The idea was to remove the need for a hunt for a ROM and cure flasholicsm by providing everything xda has in ROM development in a single bloat free rock stable ROM. This is the FIRST ROM of its kind with a hybrid framework consisting on cm10.1, AOKP and AOSPA. What makes PACman unique is this perfect blend of all of these. Be informed PACman is not a "git cherry-pick blahblah yeee i am a dev donatezzz me" ROM. It took a LOT of work and thinking behind it to merge the frameworks in the right order.
Features
Working Camera
Hybrid FrameworkCM10.1AOKP MR1AOSPA
3.00Per App DPIPer App
ColorPie Controls
Open Source
Camera HALcLock
Hardware Key Control
Any Widget on lockscreen
CM Profiles
Lock Screen Shortcuts
Lock Screen ring target
Fresh compiled CM10.1 kernel
Init.d Support
Everything cant be listed here go check it out
A LOT more to come
IF you get a force close when trying to make phone calls then follow these steps to fix them. THANKS to ducats.
"This is a sync issue. Here's how to fix it... keep in mind I've done this twice, so don't flip your lid if it doesn't take the first time.
1. Disable all sync. Easiest way is to just add the power control widget to one of your screens and turn off sync.
2. Go to Settings>Apps>All... Find contacts and contacts storage... clear data and cache for both. Then find phone and phone storage clear data and cache for both of those as well.
3. Reboot into recovery, clear dalvik and cache. Reboot.
4. Make or receive a couple calls just to confirm that Phone is not FC'ing.
5. Enable sync.
Again, you may have to do this more than once. And you MAY need to do this every time you reboot.
That exact process has completely cleared the issued for me, hopefully it works for you as well."
]]>Droid Razr HD DevelopmentGoCliffGo05http://www.razrforums.com/forum/droid-razr-hd-development/3351-rom-unlocked-bootloader-pac-man-rom-4-2-2-a.html<![CDATA[[ROM] [Unlocked Bootloader] Unofficial CM 10.1]]>
http://www.razrforums.com/forum/droid-razr-hd-development/3344-rom-unlocked-bootloader-unofficial-cm-10-1-a.html
Sun, 14 Apr 2013 18:54:35 GMT** ALL credit to Hashcode **
DEVELOPERS:
- E. Pinter - Kernel Development, Build Setup, XT925 Support
- D. Hacker - Kernel Development, Build Setup, XT907 Support
- Hashcode - XT926 Support / Setup for CDMA
FEATURES:
Updated 3.0.31 Linux Kernel heavily modified to be more AOSP compatible
Jellybean 4.2 Adreno drivers
WHAT'S WORKING:
Call
Audio
Rotation and sensors
GPS
USB
Data/4G
HW acceleration
Torch
Headphone plug detection
Microphone
Bluetooth
WiFi
WiFi Tethering
NFC (appears to be working, communication untested yet)
WHAT'S NOT WORKING:
Camera / Video Recording
Voice Dialer
HOW DO I INSTALL?
1.) Download the .zip and place it on your SD card
2.) Reboot into recovery (you are unlocked right!?)
3.) Wipe data. cache, dalvik and system
4.) Install ROM and GApps.
5.) Enjoy
** RAZRForums is not responsible for what you choose to do with your device **
]]>Droid Razr HD DevelopmentGoCliffGo05http://www.razrforums.com/forum/droid-razr-hd-development/3344-rom-unlocked-bootloader-unofficial-cm-10-1-a.htmlUnlock the bootloader on your XT926 RAZR HD + Maxx HD
http://www.razrforums.com/forum/droid-razr-hd-development/3334-unlock-bootloader-your-xt926-razr-hd-maxx-hd.html
Tue, 09 Apr 2013 00:01:06 GMTEverything you'll need can be found here Security Research by Dan Rosenberg
ALL credit to Dan Rosenberg.
This will work on the XT926 RAZR HD, RAZR MAXX HD, Atrix HD and the RAZR M.
This WILL NOT work on OMAP devices such as the OG RAZR, Bionic, Droid 4 etc.
**Dan Rosenberg, RAZRForums, Nor I, take any responsibility for what you choose to do with your device**
]]>Droid Razr HD DevelopmentGoCliffGo05http://www.razrforums.com/forum/droid-razr-hd-development/3334-unlock-bootloader-your-xt926-razr-hd-maxx-hd.html
