Related
Hi All -
New to this phone obviously (RAZR MAXX). Trying to get a grasp on it, as it's way more complicated than HTC and Samsung phones. I've rooted and installed 100s of custom ROMs with those brands before. This is my 1st Motorola since the Motorola V120c if anyone is old enough to remember that dinosaur. On nTelos' network nonetheless.
I have some questions that I would like answered and I hope someone will do me the honor as the content is really sporadic.
What is Fastboot for this device, what does it do?
Safestrap & Bootstrap? What's the difference? Which is better?
Can I flash ROMS through CWM like I have in the past?
What purpose does RSD Lite serve other than to flash Fasboot files?
Why would I want to flash fastboot? (Redundant question I think)
Thanks to anyone that takes the time to help me out.
I rooted and flash the crap out of my last phone which was Samsung. This phone seems really complex. I'm really on my toes, don't want to brick my phone. But I do want to root to get rid of the bloatware and test out some roms. The stock OS is laggy at times.
Honestly I really like the Stock OS as is. It does seem laggy at times, but nothing worse than I've run into on HTC or Samsung phones.
HTC Sense UI was/is terrible since it's so bloated and Samsung couldn't make a GPS radio capable of locating a mall let alone provide directions to anywhere. Terrible phones.
So far this phone is awesome, really bought it for the battery life honestly.
I too would like to DELETE the garbage that Verizon has installed on this thing. In terms of bloat, Verizon takes it to a whole new level. Just wow.
I'm in the same boat. Only had the phone for 2 days so far. I've already rooted it, but haven't gone any farther. But in some of my reading, I thought I saw that removing the bloatware can cause OTA updates to not happen. Hopefully someone can shed some more light on that issue.
midas69 said:
I'm in the same boat. Only had the phone for 2 days so far. I've already rooted it, but haven't gone any farther. But in some of my reading, I thought I saw that removing the bloatware can cause OTA updates to not happen. Hopefully someone can shed some more light on that issue.
Click to expand...
Click to collapse
I rooted mine 5 mins after activating it haha. As far a bloat, just use titanium pro and freeze it. Very simple. I froze around 35 apps and haven't had any issues associated w it. Should an ota come I should be prompted still. Just unfreeze all apps. Accept ota, reroot. If it breaks root completly then eventually it will get root again. I actually Ind, e system to run very well but honestly have no idea how just stock runs as I froze these apps instantly. I did not safe strap or bootstrap but I had previous knowledge of things I should be able to freeze and not and I figured it out myself
I find this phone so easy. There YouTube videos on everything.
To Get bootstrap, all you need to do is press one button, this phone has to be the easiest I've been on. The only people that struggle are the desperate ones that cba to search the forums And YouTube
Ask us any Android Related Question @FeraLabsDevs on Twitter
IdowhatIwant said:
Hi All -
What is Fastboot for this device, what does it do?
Safestrap & Bootstrap? What's the difference? Which is better?
Can I flash ROMS through CWM like I have in the past?
What purpose does RSD Lite serve other than to flash Fasboot files?
Why would I want to flash fastboot? (Redundant question I think)
Thanks to anyone that takes the time to help me out.
Click to expand...
Click to collapse
- Fastboot: its just the stock bootloader, can flash moto updates/factory reset/wipe cache. it also lets you into AP fastboot, which is where u recover stock with rsd.
- Safestrap/bootstrap: bootstrap is currently our only way of CWM on the gsm phones, i understand safestrap is pretty much like dualbooting except its not(only its not completely compatible with gsm)
- can you flash with cwm: YES!
- another purpose for rsd: i have only used it for recovering after ics, so idk.
- why flash a fastboot image?: if you mess up badly or get a bootloop you can recover back to stock
midas69 said:
I'm in the same boat. Only had the phone for 2 days so far. I've already rooted it, but haven't gone any farther. But in some of my reading, I thought I saw that removing the bloatware can cause OTA updates to not happen. Hopefully someone can shed some more light on that issue.
Click to expand...
Click to collapse
removing bloatware will cause you to be unable to get ota's (freezing and then unfreezing with TiB before ota update works fine, as long as you don't uninstall).
but i think its enough to just flash a fastboot with rsd (fully return to stock), then you can get the ota
Look here:
aashrey99razr.wordpress.com
Helped me out a lot!
Gesendet von meinem XT910 mit Tapatalk
Addictd said:
removing bloatware will cause you to be unable to get ota's (freezing and then unfreezing with TiB before ota update works fine, as long as you don't uninstall).
but i think its enough to just flash a fastboot with rsd (fully return to stock), then you can get the ota
Click to expand...
Click to collapse
I'm afraid I deleted one app before I was aware of this. TiB shows that I made a backup of it, but doesn't give me the option to restore it. Guess I'm screwed.
hehe, probably not
did you make a cwm backup prior to uninstalling the app(s)?
then you could just restore that
if not the titanium backup file should be on your internal sdcard in /mnt/sdcard/TitaniumBackup as a gzipped .apk with a kinda cryptic filename
you could try ungzipping it and installing with a file explorer.
or you could just backup with cwm and flash the correct fastbootimage for your phone from here: http://forum.xda-developers.com/showthread.php?t=1362956
usind rsd lite
and that should do it
but why not just flash a fastboot and isntall arctic 3.0.5?
Addictd said:
hehe, probably not
did you make a cwm backup prior to uninstalling the app(s)?
then you could just restore that
Click to expand...
Click to collapse
Of course not, that would be too easy
if not the titanium backup file should be on your internal sdcard in /mnt/sdcard/TitaniumBackup as a gzipped .apk with a kinda cryptic filename
you could try ungzipping it and installing with a file explorer.
Click to expand...
Click to collapse
There is a file there, but it doesn't have an .apk. There's a gzip file, inside that is a tar file. In there are imbedded data directories, but no actual files.
or you could just backup with cwm and flash the correct fastbootimage for your phone from here: http://forum.xda-developers.com/showthread.php?t=1362956
usind rsd lite
and that should do it
Click to expand...
Click to collapse
Might take that route when the next update is ready.
But why not just flash a fastboot and isntall arctic 3.0.5?
Click to expand...
Click to collapse
Well, as I said, I only got the phone Saturday, and I work weekends.
But I've got an issue hooking up to my work email account. I was unable to get it working on my Touchpad using CM7 or CM9. I originally bought a Galaxy Nexus and had no luck with that either, thus I bought the Razr. I still can't get the native apps to work, but at least Touchdown semi-works (no Activesync). So I'm actually a little gun shy about trying new things.
Addictd said:
- Safestrap/bootstrap: bootstrap is currently our only way of CWM on the gsm phones, i understand safestrap is pretty much like dualbooting except its not(only its not completely compatible with gsm)
Click to expand...
Click to collapse
Does that mean that we can't use ROM Manager or do we just need to use Bootstrap to install CWM and than use ROM Manager like we otherwise would? I got used to that app on my old phone.
I got a GSM RAZR and I have just rooted, the root script pushed in my phone some app called Bionic Bootstrapper, which gives me options Bootstrap Recovery and Reboot Recovery, what does each of them do? I don't plan on changing ROMs for now, but I definitely need to be able to recover the system.
It appears there isn't any real root on this device since the bootloader is locked. Samsung and HTC devices have their BLs unlocked so it's easier to make a permanent Recovery that will persist on reboot. I'm speculating of course, so someone correct me if I'm wrong.
Reboot recovery should reboot the phone to a ClockworkMod style "DOS" menu that allows you to preform functions like Back up, install zip files or even a new ROM.
When I did it, it rebooted a triangle and exclamation point, with an android guy on it. I was worried at that point. I hit the power button and the Recovery loaded instantly. Not sure if that's normal, but it's quite shakey compared to other devices out there.
I love this phone, so don't me wrong. It's just going to take some getting used to.
i dont think all of rom managers functions will work :/
bootstrap recovery: installs recovery (you only have to do this once)
reboot recovery: reboots your phone into cwm
the thing is the bootloader is locked, so we cant put cwm into the stock fastboot.
there is however a little workaround made by J.Y.Daddy that starts cwm everytime you boot, but this is installed in your rom, not in the stock fastboot, so you have to reinstall it when you flash a new rom :/
onboot cwm link: http://forum.xda-developers.com/showthread.php?t=1385283
Addictd said:
i dont think all of rom managers functions will work :/
bootstrap recovery: installs recovery (you only have to do this once)
reboot recovery: reboots your phone into cwm
the thing is the bootloader is locked, so we cant put cwm into the stock fastboot.
there is however a little workaround made by J.Y.Daddy that starts cwm everytime you boot, but this is installed in your rom, not in the stock fastboot, so you have to reinstall it when you flash a new rom :/
onboot cwm link: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Is there some way to otherwise boot into CWM enviroment, some combination of keys or something like on other phones? Not much use for CWM if you brick your phone and can't boot into it. Also, is installed CWM not going to cause a problem for regular OTA updates and do we need to reinstall it afterwards?
From what I understood, Motorola has put some sort of recovery environment on this phone already, but I don't know what it can be used for.
And I have GSM version, bootloader is not locked, so I don't have to worry about that.
laserburn said:
Is there some way to otherwise boot into CWM enviroment, some combination of keys or something like on other phones?
Click to expand...
Click to collapse
there's a workaround by J.Y.Darry that makes it boot into cwm on every boot.
there is no keycombo for cwm booting. but you can boot into fastboot with both volumekeys + power
where you can go into stock "recovery" and AP fastboot
you will use AP fastboot in combination with RSD lite to flash back to stock if u mess up, there are also more options in fastboot, but i have never used them.
laserburn said:
Not much use for CWM if you brick your phone and can't boot into it. Also, is installed CWM not going to cause a problem for regular OTA updates and do we need to reinstall it afterwards?
Click to expand...
Click to collapse
you will use cwm to flash custom roms and make backups
then if you mess up and want to recover a backup you have to
- set phone in ap fastboot mode
- connect razr to computer
- use rsd lite(or an alternative flashtool) to flash the fastbootfile for your phone
- root and install bootstrapper
- reboot into cwm and restore backup
i dont think cwm in itself will cause any problems for OTA's. but if you install a custom rom its a different story
as long as you have the bootstrapper app installed on your phone, you should be able to bootstrap recovery and boot into cwm
laserburn said:
From what I understood, Motorola has put some sort of recovery environment on this phone already, but I don't know what it can be used for.
Click to expand...
Click to collapse
yes they have put a rudimentary recovery in it. but you can only use it to apply updates from sdcard (to manually download ota and install), wipe and factory reset. (someone correct me if i'm wrong here)
laserburn said:
And I have GSM version, bootloader is not locked, so I don't have to worry about that.
Click to expand...
Click to collapse
sorry to be the bringer of bad news. but i have gsm too. mine is locked, so i'm pretty solid your bl is too
troollolotorola -.-
Damn, how I miss my old phone where rooting was 1 click on the app and you could swap ROMs as easy as swapping socks.
How could I check if the bootloader is locked and what consequences does it have?
laserburn said:
Damn, how I miss my old phone where rooting was 1 click on the app and you could swap ROMs as easy as swapping socks.
How could I check if the bootloader is locked and what consequences does it have?
Click to expand...
Click to collapse
Yeah I agree with you. Rooting, flashing, CWM all 100 times easier on HTC and Samsung phones.
Don't get wrong though, I Love my RAZR Maxx, and the default OS is actually OK. Which is good because it seems that there is little to zero developement for the CDMA version of the droid RAZR/MAXX at the moment, if at all.
they're all over on the HTC/Sammy forums =D
laserburn said:
Damn, how I miss my old phone where rooting was 1 click on the app and you could swap ROMs as easy as swapping socks.
How could I check if the bootloader is locked and what consequences does it have?
Click to expand...
Click to collapse
if/when we get the BL unlocked this phone will be a dream
there is this utility made by mattlgrof u can use to check bl lock
http://forum.xda-developers.com/showthread.php?t=1486718
IdowhatIwant said:
Yeah I agree with you. Rooting, flashing, CWM all 100 times easier on HTC and Samsung phones.
Don't get wrong though, I Love my RAZR Maxx, and the default OS is actually OK. Which is good because it seems that there is little to zero developement for the CDMA version of the droid RAZR/MAXX at the moment, if at all.
they're all over on the HTC/Sammy forums =D
Click to expand...
Click to collapse
Ain't no agruing with that, but they don't make as sweet looking and solid phones i hope motorola pull their head out of their ass soon...
Development for the cdma version is found mostly on droidrzr.com (plenty of beta/alpha ICS and some GB roms) but they are missing some parts, so we have to wait till motorola release ics be4 they will be complete.
http://www.droidrzr.com/index.php/index
for all you non-cdma users out there, u should check out the cdma to gsm patch
http://www.droidrzr.com/index.php/topic/1233-cdma-port-cm9aokp-givesomelovetogsm/
Hi All,
I have been using qbking videos to get root/unlock/cwm my photon. I had to revert to stock for some problems while running CM9.
Now I am willing to take a plunge into CM9 again but I am unable to find a file needed to root (system.img). So I just had an idea to work around that. I wanted to get the opinion from some of the much wiser and experienced flash-root folk out here.
Here goes the plan:
1. I have my photon unlocked.
2. By observation, the root process needs to flash a system.img onto photon through fastboot. My guess is this is a image (2.3.x), from a rooted photon, that is(was) being circulated.
3. As joker now has a fastboot image for flashing which is coincidentally called system.img and it very clearly is rooted, can I flash this using fastboot instead. This way I seem to be doing sth similar to step 2 but using a 4.0.x image. Behold! I am rooted.
4. Install CWM according to the steps detailed by qbking.
It all sounds good to me. But as this is not a very popular option for many people I am guessing there is something that I am missing, which comes with experience.
Thanks a ton
- Harakiri
If you are unlocked, you need to install a recovery, cwm or jokers. Then flash what ever rom you want. They are pre rooted. As far as the rest of it, I don't know
Sent from my MB855 using Tapatalk 2
If you install a cwm try romracer's 5.0.2.7-photon3.zip. It works across many roms.
I'm an ICS craving MoPho-er!
UPDATE: The latest update still is safe. I just installed it and I am still s-off.
UPDATE: The update to Jellybean does not write the secure flag and this method is safe to apply the OTA update with this method and still maintain root access afterwards.
First and foremost, a couple disclaimers.
FIRST, YOU MUST BE S-OFF FOR THIS TO WORK. PLEASE DO NOT TRY THIS IF YOU ARE NOT ALREADY S-OFF.
SECOND, FOR THE OTA UPDATE 1.22.651.3 YOU WILL FOR SURE RETAIN S-OFF. ALTHOUGH HIGHLY UNLIKELY, HTC COULD POTENTIALLY MAKE YOU S-ON IN FUTURE OTA UPDATES. SEE HERE FOR MORE INFORMATION.
To obtain s-off please see this thread: http://unlimited.io/jewel.htm
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out. I don't really theme, mod, or do crazy things with my phone but still want root access. So, I decided since I was s-off, I would give this method a whirl. I am happy to report that I am s-off, with TWRP, fully rooted, and with installing the OTA update. I had a little hiccup but was able to solve that.
So, here is the process. This is kind of a hodge podge of different threads, ideas, devices, and versions of android so if I didn't give you credit, please let me know and I will put you in this thread.
Process for installing a stock recovery. I have already created some stock recovery files so see at the bottom of this post for the zip file that includes the stock recovery. If you wish to use these files, just start with step #10.
IF YOU CHOOSE TO JUST DOWNLOAD THE STOCK RECOVERY AT THE BOTTOM OF THIS POST, SKIP TO STEP #10.
Creating Stock Recovery File Manually
1. Install a stock recovery if you don't already have one.
2. To do so, get the RUU for the version you are running.
3. Run the RUU (don't connect to your phone at all)
4. Navigate to your temp directory on your computer (on windows 7 it is C:\Users\your_user_name\AppData\Local\Temp)
5. Find a folder that looks like it is in the following format "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}" It might help to sort by date modified. The folder should have the current date
6. Inside the folder might be a couple other folders. Navigate through the folder to find a zip that says "firmware" or "rom" (mine said rom)
7. Extract the content to a folder in the same directory called rom
8. Navigate into the rom folder and find two files android-info.txt and recovery_signed.img. Copy those to a directory of your choice.
9. Send those files to a zip folder and name the file "PJ75IMG.zip" without the quotes. Make sure zip is only listed once. If you have file extensions hidden in windows yours will only say "PJ75IMG".
Installing the stock recovery, OTA, and regaining root
10. Place the stock recovery file on the root of your sd card
11. On your phone, head into settings and power and make sure the fastboot option is unchecked
12. Power down phone
13. Once phone is completely shut down, hold the volume down button and press the power on button while keeping the volume down button pressed.
14. It will boot into your hboot (verify it says s-off at the top or don't proceed) and find the file you placed on your sd card and ask you if you want to update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
15. Go to settings>check for updates and check to see if there is an update. Download the update. Once it verifies, click install now. It should install just fine.
16. Once you are up and running, download one of the dirty racun hboots. I used hboot 2.09 img found here. Follow the instructions on the unlimited.io website how to flash the hboot by using fastboot (flashing the zip doesn't seem to be working.
update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
17. Make sure usb debugging is checked under settings>developer options
18. Go download a su zip file. I used this one here and place it on the root of your sd card.
19. Go grab a custom recovery flashable zip (could not find the latest twrp zip) or img (I used TWRP found here. Take the image and place it in your platform tools folder for ADB.
20. Plug in phone while powered on and type in adb devices to make sure you are connected.
21. If you see a device type in
Code:
adb reboot bootloader
22. Your device will boot into your bootloader and you will see fastboot usb (make sure usb debugging was checked if you don't see that).
23. Then type fastboot flash recovery [filename] of the recovery img you downloaded. Once flashed, toggle with the volume up buttons to bootloader and then select recovery. This should boot you into TWRP
24. Once in recovery, install the su zip you downloaded in step 18.
25. Reboot and Enjoy!!!!
You are now rooted with the most current OTA update and all the goodies (radios, PRI, etc.)
This process should hopefully hold true for any future OTA updates if you are S-OFF. The only thing you will have to find is the current RUU to create the stock recovery. If this helped, feel free to thank! Go XDA!
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I don't know. So you don't have to wait at all? Or for the people that aren't accustomed to flashing ROMs or don't care to. I prefer this method for whatever reason and it seems just easier. Personal preference though. The beauty of android and their strong developer network is that it gives the users choices. I can take the OTA update as soon as it comes out and don't have to worry about waiting for anything. Just another method I guess.
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
msimindlessmsi2 said:
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
Click to expand...
Click to collapse
The update firmware is the part that hangs me up. I believe when it was back in the original EVO days that some people were having problems updating their PRI version and it screwed up some things with wimax. That is when I decided I would just accept the OTA to get everything they included in the update and then gain root access through this method.
Again, to each their own. Please try not to clutter up the thread with off topic items. Thanks.
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
im coming from the rezound, i just want the updated firmware! on my rez being s-off i could run ANY firmware ICS, or GB and then go back to whatever rom i was running. im wondering if im s-off, i should b able to do the same thing right.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
The devs state that so that they don't have to spend their valuable time troubleshooting because you didn't flash right. Its always best to do a full wipe, but not always required when flashing an updated version of the same ROM.
1) Nandroid.
2)Wipe Dalvik cache & cache
3) Flash
You retain all data.
If you have issues, then you nand restore and do a full wipe before bugging the devs
bpdamas said:
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out.
Click to expand...
Click to collapse
Lmao! You find that whole process "easier" than waiting for a day? I think it might take the better part of a day to do all that.
Sent from my EVO using xda premium
Thanks for taking the time to do a write-up OP!
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
Agreed.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Definitely agreed.
greyopaque said:
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
Click to expand...
Click to collapse
I know. This is exactly why I root and I can't believe there are so many people against this method. It seems very simple to me and I can have a stock recovery waiting to flash as soon as an OTA update comes out. Oh well.
Thanks for this info. I think I'm like you and not only like the stock experience and its benefits but also prefer diy when possible.
Of course I never seem to stay stock like you but I like doing the steps my self. To each their own is the beauty of android.
Go android!
Sent from my EVO
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
zounduser said:
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Click to expand...
Click to collapse
Very curious on this. Nothing in this method should affect this.
Robbie_G said:
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
Click to expand...
Click to collapse
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Rxpert said:
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Click to expand...
Click to collapse
That's fair, rooting and s-off could also inject malicious code. But so can ROM makers.
I think there's a difference between trying to be safe and being paranoid. If there is a way for someone to make money off of you/steal your identity, eventually they will try. I'm not suspicious of any of the current devs, but it's something we should maybe be more aware of. Look at all the warez Windows out there with malware built in to steal your information.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Totally agree. Its a good thing to learn in my opinion. I broke my Evo 4G, fixed it then rerooted it. Now on the 4G LTE got it rooted with custom rom. Love learning new things plus some of the good things that come with rooting and custom roms are worth it for me.
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
upndwn4par said:
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
Click to expand...
Click to collapse
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
I just sold mine but will look in PC history. My matrix was stock 4.5.145 and I rooted it. I remember failing a few methods till I found one that worked. If I figure out what I did I will post it for you. If not fruitcake is best way
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
upndwn4par said:
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
Understood, thanks for the explanation.
UnlockRoot couldnt gain root access
I will attempt your suggestions Thanks very much for the guidance, its invaluable
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
KetoSoi said:
Unless some one figures out what motorola/att did with 145 to completely screw root ...
Click to expand...
Click to collapse
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
upndwn4par said:
Let me know how things go with the above before you even consider this.
Click to expand...
Click to collapse
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
ravilov said:
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
Click to expand...
Click to collapse
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
KetoSoi said:
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
Click to expand...
Click to collapse
Wow, that's just bizarre. Not sure what to think here.
I meant something like
Code:
moto-fastboot erase preinstall
KetoSoi said:
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
Click to expand...
Click to collapse
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
upndwn4par said:
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
Click to expand...
Click to collapse
Very odd some cannot root. I was on permalocked bootloader and still rooted after soak
Its sad, because the 145 update seemed like it made the phone a little snappier, and the screen was a pinch smoother.
What do you guys think about applying the CWM Zip for update 4.5.145 in my situation? Would that be safer?
Uh oh.... you guys ran away! LOL
I was able to flash the 145 update via CWM from NYG-SBXLII's handy zip file
No real problems, 145 running fine WITH root intact. Awesome
Had to blow away the recovery-from-boot.p file afterwards, and re-flash CWM Recovery, but it was all good.
Updated SU and bin's, good to go.
affiatic said:
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
Click to expand...
Click to collapse
This worked for me too with 4.5.145, followed it exactly and had no problems. Thanks!
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
How did you unlock the bootloader for firmware 4.5.145? I've been looking everywhere on how to do it safely!
upndwn4par said:
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
hello, ive been using 4.5.145 and was unable to root it, the problem with mine is that when I try to use the preinstall method it chokes when i type the "cp /preinstall/su /system/bin/... there was a message cp write error: no space left on device.. I have tried everything (almost) to root it but was unlucky.. then i saw this thread http://forum.xda-developers.com/showthread.php?t=2153422 ... i wanna try your suggestion but cant find the zip file in suggestion 1 and the 141 fruitcake you made on suggestion 2 and cant find file on option 3.. please do help me.. I have unlocked bootloader and have rom racers cwm.. thank you and more power..
So guys, I'm new to this and thought I would jump in at the deep end.
I unlocked my HTC One X+ easily and set about rooting.
I've got TWRP installed but it keeps telling me it needs to install superuser before it can root.
I have totally wiped the phone, how come if Im not rooted?
How do I get an OS and indeed the kernel or ROM onto the phone?
Its and International OX+, I've got the right kernel... what do I need to do?
It was locked to O2 if that makes a difference
I followed the instruction in Hasson but then wiped the OS
I know its a simple procedure but can someone walk me through it please
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
eskimosound said:
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
Click to expand...
Click to collapse
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
dan_alexandre said:
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
Click to expand...
Click to collapse
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
eskimosound said:
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
Click to expand...
Click to collapse
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
dan_alexandre said:
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
Click to expand...
Click to collapse
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
eskimosound said:
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
Click to expand...
Click to collapse
I see, the easiest ways would be to use a custom rom now. For example, the one you already got the kernel from(android revolution hd)
To root you dont need to install a kernel... just to flash the supersu zip. Using a custom rom's kernel with stock rom might not be a good idea.
Another simple way would be to restore stock rom back to start and try rooting again, this time reading everything carefully
So the two easiest ways i think:
1) flash a custom rom following the instructions they provide in the initial posts for that rom
2) run the o2 correspondent RUU to restore stock rom (you'd need to relock the bootloader), also reading carefully posts in the forum about restoring to stock
Without getting into too much detail, these are the simplest options.
All the info required to do these are on these forums
Aaarrghhh, its driving me insane as I knew it would, just like XP, Vista Seven and Eight!!!
So Im back to being up all night learning..
Well have installed SDK correctly but device is not seen, no serial, nothing.
I can get it to fastboot though, however I don't know any commands so I cant get it to work
Windows 7 keeps moaning about an mpt file which I downloaded and dont know where to extract it to
All I need to do is copy a few files to the phones sd card and install them right?
Whys that so difficult?
I don't know the difference between a rom an ruu and a boot image, in that I don't know where they should all be placed.
Why cant twrp copy and paste from pc...
So Hassooon works sort of but still none the wiser.
Am following tutorial but fastboot commands are not working
Still cant find right driver.....
So CMD lines not working 100%
So am downloading drivers in sdk manager
And how do I flash the supersu zip?
Still no luck with driver, im on windows 7 32bit
OK I cant push using adb it cant find the file or directory,
Hassooon cant detect the phone as cant windroid universal
I dont think the phone is rooted even though i have twrp on it.
Thus can I have wiped the os?
If not can i restore it?
No I didnt make a backup rom..
mmm a zip on the phone doesnt load in bootloader, count that be my os?
Guys, im stranded in the water here...
On boot im getting...
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
Whats PM35IMG.zip?
Is that the OS?
Am I saved?
Is it easy to get that file to unzip and load?
Can anyone help?
So now I need the right RUU.....
2.17.206.3
Is there anyone out there that can help please?
So have managed to install superuser and root my phone, all instructions for doing this were wrong including Hassoon, had to have the phone in System screen to do it, not bootloader or recovery.
Now cant get adb to push file to sdcard...
Man alive, how to make something very easy, sound very difficult.
Would any of you experts care to help?
Just trying to install a ROM.zip to Root and place the boot img in right place.
Well, the instructions are dire but after 10 days of persistance have installed Android Revolution HD 8, finally my phone is up and running better than the bloated os that came with the phone so, you can call this thread resolved.