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/
My Droid Razr MAXX is Bricked and I really need my phone! Any ideas out there?
Ill start from the beginning, list every single Mod I have done to my phone, where it failed, and why it failed, and see if there is a possible solution. This was my FIRST EVER SMARTPHONE. I had had a samsung basic flip phone for nearly 8 years but I am a huge computer nerd (Windows Specifically) and thought I could learn how to modify an Android. This Bricking and Erroring of my Razr MAXX all had to do with me downloading and installing the wrong ClockWorkMod .zip file, it was CWM_on_boot_REMOVE.zip instead of the correct install file. I wasnt paying attention to the attachments here: http://forum.xda-developers.com/showthread.php?t=1385283. If you look at the bottom you will notice only the remove file is there, because I did not see the other link in the post ITSELF to the CWM_on_boot real package download site. So here, in great detail, is what happened:
Early October 2012 - Recieve Droid Razr MAXX from Verizon. Comes with Android ICS 4.0.4
Mid October 2012 - Razr MAXX rooted using easy ICS root, works fine
Early November 2012 - Bought Motomizer Expert Edition to make overclocking easy, works fine
Late January 2013 - Cought wind of official Jelly Bean OTA and was deciding whether or not to start doing research and get it done
Early February 2013 - Cought wind of Jelly Bean OTA ROOT now possible and so I decide to make the push that night
Early February 2013 - Noticed that on Jelly Bean, many apps run slow/lag quite a bit. Games that are normally so easy to run (i.e. Fruit Ninja)
Early February 2013 - Get fed up with my lagging apps and decide its time for a custom ROM
Just Yesterday - (See Below...)
So what happened Yesterday was I installed Razr Bootstrap.apk and downloaded (or so I thought) CWM_on_boot (ClockWorkMod Recovery - N BOOT) package from http://forum.xda-developers.com/showthread.php?t=1385283. I hit "Bootstrap" in Razr Bootstrap, it said "successful", I hit "Reboot Recovery" and it reboots into ClockWorkMod Recovery. Well, Turns out it was the CWM_on_boot_REMOVE package instead and not paying attention in ClockWork Mod Recovery, I hit "Install from SD" (NOT "Install Update from SD"). Here I am thinking everything went fine and dandy, then the phone rebooted after the "Removal"... Now it gives me this screen on boot:
ENCRYPTION UNSUCCESSFUL
Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account. (Below appears a small square button, it says "Restore Phone"
I have tried the reset button, it goes to the reset screen and appears to work, just to reboot to the "ENCRYPTION UNSUCCESSFUL" screen yet again, and does this over and over no matter how many times I try. I have a Micro-SD adapter and so I re-loaded the Jelly Bean OTA .zip file as well as the real CWM_on_boot package but cannot install them from the stock recovery mode screen. AP Fastboot goes to a screen where it says my phone is "Locked".
That is all the information as far as I can remember, if you need specifics feel free to ask. I was wondering if there was a way to reverse my CWM-on_boot_REMOVE error and simply remove all of the tweaks I have ever performed (i.e. get rid of modified kernel and JB and install original ICS and factory Kernel) and restore the phone to the day I pulled it out of the box back in October. After this mix up, I dont ever plan to use custom ROMs or OTA leaks ever again. Just a simple root on stock phone with some overclocking will do for me.
wallacengineering said:
My Droid Razr MAXX is Bricked and I really need my phone! Any ideas out there?
Ill start from the beginning, list every single Mod I have done to my phone, where it failed, and why it failed, and see if there is a possible solution. This was my FIRST EVER SMARTPHONE. I had had a samsung basic flip phone for nearly 8 years but I am a huge computer nerd (Windows Specifically) and thought I could learn how to modify an Android. This Bricking and Erroring of my Razr MAXX all had to do with me downloading and installing the wrong ClockWorkMod .zip file, it was CWM_on_boot_REMOVE.zip instead of the correct install file. I wasnt paying attention to the attachments here: http://forum.xda-developers.com/showthread.php?t=1385283. If you look at the bottom you will notice only the remove file is there, because I did not see the other link in the post ITSELF to the CWM_on_boot real package download site. So here, in great detail, is what happened:
Early October 2012 - Recieve Droid Razr MAXX from Verizon. Comes with Android ICS 4.0.4
Mid October 2012 - Razr MAXX rooted using easy ICS root, works fine
Early November 2012 - Bought Motomizer Expert Edition to make overclocking easy, works fine
Late January 2013 - Cought wind of official Jelly Bean OTA and was deciding whether or not to start doing research and get it done
Early February 2013 - Cought wind of Jelly Bean OTA ROOT now possible and so I decide to make the push that night
Early February 2013 - Noticed that on Jelly Bean, many apps run slow/lag quite a bit. Games that are normally so easy to run (i.e. Fruit Ninja)
Early February 2013 - Get fed up with my lagging apps and decide its time for a custom ROM
Just Yesterday - (See Below...)
So what happened Yesterday was I installed Razr Bootstrap.apk and downloaded (or so I thought) CWM_on_boot (ClockWorkMod Recovery - N BOOT) package from http://forum.xda-developers.com/showthread.php?t=1385283. I hit "Bootstrap" in Razr Bootstrap, it said "successful", I hit "Reboot Recovery" and it reboots into ClockWorkMod Recovery. Well, Turns out it was the CWM_on_boot_REMOVE package instead and not paying attention in ClockWork Mod Recovery, I hit "Install from SD" (NOT "Install Update from SD"). Here I am thinking everything went fine and dandy, then the phone rebooted after the "Removal"... Now it gives me this screen on boot:
ENCRYPTION UNSUCCESSFUL
Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account. (Below appears a small square button, it says "Restore Phone"
I have tried the reset button, it goes to the reset screen and appears to work, just to reboot to the "ENCRYPTION UNSUCCESSFUL" screen yet again, and does this over and over no matter how many times I try. I have a Micro-SD adapter and so I re-loaded the Jelly Bean OTA .zip file as well as the real CWM_on_boot package but cannot install them from the stock recovery mode screen. AP Fastboot goes to a screen where it says my phone is "Locked".
That is all the information as far as I can remember, if you need specifics feel free to ask. I was wondering if there was a way to reverse my CWM-on_boot_REMOVE error and simply remove all of the tweaks I have ever performed (i.e. get rid of modified kernel and JB and install original ICS and factory Kernel) and restore the phone to the day I pulled it out of the box back in October. After this mix up, I dont ever plan to use custom ROMs or OTA leaks ever again. Just a simple root on stock phone with some overclocking will do for me.
Click to expand...
Click to collapse
Well, did you tried to reboot the phone in AP Fastboot?! Turn off the phone and hold down "Vol Up + Down, then power" the AP Fastboot screen will appear.
If you can access the AP Fastboot screen, then your phone can be restored. Download the RSD Lite 6.1.4 and flash a Stock ROM to your phone.
I bricked my Razr Maxx trying to upgrade my ICS 4.0.4 to the JB leak, but the process failed. My phone was booting directly to the AP Fastboot screen.
It will restore your phone, but you will lost all your data.
MichelBFR said:
Well, did you tried to reboot the phone in AP Fastboot?! Turn off the phone and hold down "Vol Up + Down, then power" the AP Fastboot screen will appear.
If you can access the AP Fastboot screen, then your phone can be restored. Download the RSD Lite 6.1.4 and flash a Stock ROM to your phone.
I bricked my Razr Maxx trying to upgrade my ICS 4.0.4 to the JB leak, but the process failed. My phone was booting directly to the AP Fastboot screen.
It will restore your phone, but you will lost all your data.
Click to expand...
Click to collapse
I tried to find RSD 6.1.4 but only found version 5.7 but it said it was compatable with the Motorola Droid Razr MAXX so I downloaded and installed it onto my laptop. I located the official stock rom here: http://forum.xda-developers.com/showthread.php?t=1767255. I tried flashing this ROM and it failed at step 12/16: "boot.img". So I tried Droid Razr Utility 1.8.2 and again everything wen well except for 'boot' but on this utility it gave me the error:
writing 'boot'... INFOPreflash validation failure
FAILED <remote: >
wallacengineering said:
I tried to find RSD 6.1.4 but only found version 5.7 but it said it was compatable with the Motorola Droid Razr MAXX so I downloaded and installed it onto my laptop. I located the official stock rom here: http://forum.xda-developers.com/showthread.php?t=1767255. I tried flashing this ROM and it failed at step 12/16: "boot.img". So I tried Droid Razr Utility 1.8.2 and again everything wen well except for 'boot' but on this utility it gave me the error:
writing 'boot'... INFOPreflash validation failure
FAILED <remote: >
Click to expand...
Click to collapse
I couldn't use the Razr Utility 1.8.2.
Always having failures when "writing files".
Believe me. Search for a Stock rom which is compatible with your phone (Maxx XT910) and correspond to your country. I'm from Brazil and all of the roms I tested couldn't be installed with RSD Lite (fails on step 6th). I found a brazilian stock rom (no carrier logo or apps) of ICS and installed it.
I can't post any links here (newbie yet), but the RSD Lite 5.7 works too. But you need to find a compatible rom.
___________
Another important hint. Be careful with it. I don't know if the phone can be charged when is bricked. Try to not keep it turned ON unnecessary.
MichelBFR said:
Well, did you tried to reboot the phone in AP Fastboot?! Turn off the phone and hold down "Vol Up + Down, then power" the AP Fastboot screen will appear.
If you can access the AP Fastboot screen, then your phone can be restored. Download the RSD Lite 6.1.4 and flash a Stock ROM to your phone.
I bricked my Razr Maxx trying to upgrade my ICS 4.0.4 to the JB leak, but the process failed. My phone was booting directly to the AP Fastboot screen.
It will restore your phone, but you will lost all your data.
Click to expand...
Click to collapse
MichelBFR said:
I couldn't use the Razr Utility 1.8.2.
Always having failures when "writing files".
Believe me. Search for a Stock rom which is compatible with your phone (Maxx XT910) and correspond to your country. I'm from Brazil and all of the roms I tested couldn't be installed with RSD Lite (fails on step 6th). I found a brazilian stock rom (no carrier logo or apps) of ICS and installed it.
I can't post any links here (newbie yet), but the RSD Lite 5.7 works too. But you need to find a compatible rom.
___________
Another important hint. Be careful with it. I don't know if the phone can be charged when is bricked. Try to not keep it turned ON unnecessary.
Click to expand...
Click to collapse
Hey there guys. Thank you all so much for the help. After a few days of intense stress and toying, I finally got it online. A couple of great guys over at the AndroidForums helped me through every step. Pay special attention to the last tread but pay attention to them all it has important info that WILL help others. Here is the thread (below). How would it be possible to spread this information to allow others who needed help like me, to gain access to its information?
Link: ht + tp://androidforums + .co + m/razr-razr-ma + xx-all-things-root/689043-user-error-mo + to-droid-razr-maxx-xt912-now-bric + ked-any-solut + ions.ht + ml#post55 + 50465 (Sorry drastic measure there apparently I am not allowed to post links since I am new)
My Droid Razr MAXX is Bricked and I really need my phone! Any ideas out there?
Ill start from the beginning, list every single Mod I have done to my phone, where it failed, and why it failed, and see if there is a possible solution. This was my FIRST EVER SMARTPHONE. I had had a samsung basic flip phone for nearly 8 years but I am a huge computer nerd (Windows Specifically) and thought I could learn how to modify an Android. This Bricking and Erroring of my Razr MAXX all had to do with me downloading and installing the wrong ClockWorkMod .zip file, it was CWM_on_boot_REMOVE.zip instead of the correct install file. I wasnt paying attention to the attachments here: http://forum.xda-developers.com/show....php?t=1385283. If you look at the bottom you will notice only the remove file is there, because I did not see the other link in the post ITSELF to the CWM_on_boot real package download site. So here, in great detail, is what happened:
Early October 2012 - Recieve Droid Razr MAXX from Verizon. Comes with Android ICS 4.0.4
Mid October 2012 - Razr MAXX rooted using easy ICS root, works fine
Early November 2012 - Bought Motomizer Expert Edition to make overclocking easy, works fine
Late January 2013 - Cought wind of official Jelly Bean OTA and was deciding whether or not to start doing research and get it done
Early February 2013 - Cought wind of Jelly Bean OTA ROOT now possible and so I decide to make the push that night
Early February 2013 - Noticed that on Jelly Bean, many apps run slow/lag quite a bit. Games that are normally so easy to run (i.e. Fruit Ninja)
Early February 2013 - Get fed up with my lagging apps and decide its time for a custom ROM
Just Yesterday - (See Below...)
So what happened Yesterday was I installed Razr Bootstrap.apk and downloaded (or so I thought) CWM_on_boot (ClockWorkMod Recovery - N BOOT) package from http://forum.xda-developers.com/show....php?t=1385283. I hit "Bootstrap" in Razr Bootstrap, it said "successful", I hit "Reboot Recovery" and it reboots into ClockWorkMod Recovery. Well, Turns out it was the CWM_on_boot_REMOVE package instead and not paying attention in ClockWork Mod Recovery, I hit "Install from SD" (NOT "Install Update from SD"). Here I am thinking everything went fine and dandy, then the phone rebooted after the "Removal"... Now it gives me this screen on boot:
ENCRYPTION UNSUCCESSFUL
Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account. (Below appears a small square button, it says "Restore Phone"
I have tried the reset button, it goes to the reset screen and appears to work, just to reboot to the "ENCRYPTION UNSUCCESSFUL" screen yet again, and does this over and over no matter how many times I try. I have a Micro-SD adapter and so I re-loaded the Jelly Bean OTA .zip file as well as the real CWM_on_boot package but cannot install them from the stock recovery mode screen. AP Fastboot goes to a screen where it says my phone is "Locked".
That is all the information as far as I can remember, if you need specifics feel free to ask. I was wondering if there was a way to reverse my CWM-on_boot_REMOVE error and simply remove all of the tweaks I have ever performed (i.e. get rid of modified kernel and JB and install original ICS and factory Kernel) and restore the phone to the day I pulled it out of the box back in October. After this mix up, I dont ever plan to use custom ROMs or OTA leaks ever again. Just a simple root on stock phone with some overclocking will do for me.
I think you need to get the original jellybean rom from http://sbf.droid-developers.org/pho...SDLite) then u're phone is fully operational.
I think you need to get the original jellybean firmware then flash the xml file using RSDLite(assuming you have RSDLite) then u're phone is fully operational.
I am having the same problem
LaserCrafter said:
I think you need to get the original jellybean firmware then flash the xml file using RSDLite(assuming you have RSDLite) then u're phone is fully operational.
Click to expand...
Click to collapse
I am also facing the same problem. Thanks for the replies. Can you please tell me what is the name of the xml file that i need to flash (after extraction)?
I am currently downloading the complete zip file from the link http://sbf.droid-developers.org/phone.php?device=9
Tried it but it failed
nishanchi said:
I am also facing the same problem. Thanks for the replies. Can you please tell me what is the name of the xml file that i need to flash (after extraction)?
I am currently downloading the complete zip file from the link http://sbf.droid-developers.org/phone.php?device=9
Click to expand...
Click to collapse
I tried flashing the zip but the process failed. I was using RSD Lite and it now reads an error on the RSD Lite: 'Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Okay I have similar problem,I think. I can enter fastboot on phone, But all of a sudden my computer can't install the fastboot. So I can't use rsdlite or any other utility out there. Any suggestions??? Or is this phone completely bricked now?
Sent from my XT1080 using XDA Premium 4 mobile app
nishanchi said:
I am also facing the same problem. Thanks for the replies. Can you please tell me what is the name of the xml file that i need to flash (after extraction)?
Click to expand...
Click to collapse
Are you on Jelly Bean, Ice Cream Sandwich, or Gingerbread?
nishanchi said:
I am also facing the same problem. Thanks for the replies. Can you please tell me what is the name of the xml file that i need to flash (after extraction)?
I am currently downloading the complete zip file from the link http://sbf.droid-developers.org/phone.php?device=9
Click to expand...
Click to collapse
Download the one that says 98.72.165 if u're on jelly bean
nishanchi said:
I tried flashing the zip but the process failed. I was using RSD Lite and it now reads an error on the RSD Lite: 'Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Click to expand...
Click to collapse
Are you using the ics image or the gingerbread image?
jemf1982 said:
Okay I have similar problem,I think. I can enter fastboot on phone, But all of a sudden my computer can't install the fastboot. So I can't use rsdlite or any other utility out there. Any suggestions??? Or is this phone completely bricked now?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had that same problem before. Just try using PDANET if your computer can't read the driver. Then try flashing the image for your phone again
Sent from my XT912 using XDA Premium 4 mobile app
unbricking xt912
PLEASE any help will be very much appreciated.
my xt912 got bricked some time ago... i recently saw a way to unbrick it using RSD LITE and i thought i might as well work on it myself..
long story cut short,rsd lite keeps giving failed when it get to the 12/16 step
kept reporting failed:boot flash failed...
now i've seen some people reporting failed but not at this stage so the solutions like "delete get var lines"" dont apply
i really hope someone has got the answer....
appreciate any consideration by yáll...
thomasopeyemi said:
PLEASE any help will be very much appreciated.
my xt912 got bricked some time ago... i recently saw a way to unbrick it using RSD LITE and i thought i might as well work on it myself..
long story cut short,rsd lite keeps giving failed when it get to the 12/16 step
kept reporting failed:boot flash failed...
now i've seen some people reporting failed but not at this stage so the solutions like "delete get var lines"" dont apply
i really hope someone has got the answer....
appreciate any consideration by yáll...
Click to expand...
Click to collapse
What does it say on AP Fastboot screen?
Filenames?
Sent from my XT907 using Tapatalk
jemf1982 said:
Okay I have similar problem,I think. I can enter fastboot on phone, But all of a sudden my computer can't install the fastboot. So I can't use rsdlite or any other utility out there. Any suggestions??? Or is this phone completely bricked now?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try to install the motorola drivers from @mattlgroff's Razr Jelly bean Utility
LaserCrafter said:
Try to install the motorola drivers from @mattlgroff's Razr Jelly bean Utility
Click to expand...
Click to collapse
You know that post is a year old? (14th June 2014, 01:51 AM )
sd_shadow said:
You know that post is a year old? (14th June 2014, 01:51 AM )
Click to expand...
Click to collapse
Wow, it I only took a year!! Somebody cares. Lol. I appreciate it though. I did do exactly that though.
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please! You need to backup everything on your internal storage before you install this in case you need to restore back. If using the Safestrap version this rom needs to be flashed to the STOCK SLOT and the 4.4.2 KitKat Kernel and Baseband need to be flashed for it to work. If your Unlocked you either need to be on 4.4.2 prior to install or flash the 4.4.2 Baseband after the install. YOU'VE BEEN WARNED!
Okay this is a stock unmodified rooted rom of the Republic Wireless and C-Spire 4.4.2 KitKat OTA with full Safestrap functionality, except for restoring back to 4.2.2. To go back to 4.2.2 you will have to restore back using RSD or Fastboot. You will need to have the phone's drivers installed to get this working, so click the link below to download them and install them before you start. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
I don't own a XT1049 I threw this together for some users that asked for it, y'all will be my testers to confirm it's working.
Instructions to install this rom for Safestrap Users, read every step before you start...
1. You need to be rooted on 4.2.2 or 4.4 with Safestrap installed
2. You also need to have disabled write protection via MotoWpNoMo
3. Boot into Safestrap Recovery
4. Factory Reset the STOCK Slot in Safestrap DO NOT wipe the /system it can cause issues
5. Flash the Rom zip to the STOCK Slot (this can take up 10 minutes just walk away and let it finish)
6. Once the Rom has finished flashing, reboot to the Bootloader from within Safestrap
7. Plug your Moto X via usb cable into your computer the Bootloader screen should say usb connected now
8. Unzip the "RW & C-Spire Moto X Kernel and Radio Flasher.zip"
9. Open the extracted folder and find the FlashMyMotoX.bat and run it
10. For RW choose option 2 and for C-Spire option 4 within the FlashMyMotoX utility to flash the 4.4.2 KitKat Kernel
11. Once it finishes get back to the options and for RW choose option 3 and for C-Spire option 5 this will flash the 4.4.2 KitKat Baseband
12. Once it finishes successfully unplug your usb cable and reboot the phone
13. Enjoy 4.4.2 KitKat!
For Unlocked Users
1. Boot into TWRP 2.7 factory reset then install the rom.
2. If you were on 4.4.2 already then reboot and enjoy if you weren't on 4.4.2 then continue to step 3.
3. Once done installing reboot to the bootloader from within TWRP.
4. Once on the bootloader screen plug your usb cable into your Moto X the screen should say usb connected.
5. Extract and run my utility for RW choose option 3 and for C-Spire option 5 to flash the 4.4.2 Baseband.
6. Reboot and Enjoy 4.4.2!
Downloads: DO NOT repost links on other forums, link them to this thread!
Republic Wireless Versions
Safestrap Version
Unlocked Version
C-Spire Versions
Safestrap Version
Unlocked Version
Utility
RW & C-Spire Flashing Utility
Thanks to Google for Android and their Search engine, Hashcode for Safestrap, jcase for root, beaups and fuses for MotoWpNoMo, dhacker29 for TWRP 2.7, and the Chinese middle man for my bootloader unlock without them this wouldn't be possible!
great work
Stuck at "Formatting System...."
I followed your guide and at the point where I am attempting to flash the update, it is hung up. The last message the console printed was "formatting system...."
What should I do? It has been 5 minutes now... If the update is corrupt somehow, is there any way to push another version to the device from recovery?
* UPDATE * the flash finally completed. For those of you that are unsure, let it sit. It takes quite some time to flash (more than a couple minutes)!
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
slgooding said:
I followed your guide and at the point where I am attempting to flash the update, it is hung up. The last message the console printed was "formatting system...."
What should I do? It has been 5 minutes now... If the update is corrupt somehow, is there any way to push another version to the device from recovery?
* UPDATE * the flash finally completed. For those of you that are unsure, let it sit. It takes quite some time to flash (more than a couple minutes)!
Click to expand...
Click to collapse
slgooding said:
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
Click to expand...
Click to collapse
Yeah the install for Safestrap takes forever for some reason it doesn't for custom recoveries though. You need to run MotoWpNoMo to remove Write Protection, because you can't flash the 4.4.2 boot.img to the recovery partition, Moto signed them with different keys. It says that in the OP!
slgooding said:
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
Click to expand...
Click to collapse
did you run MotoWpNoMo when you were still on 4.2.2 ? thats the only way to retain write protection on 4.4.2
jbrukardt said:
did you run MotoWpNoMo when you were still on 4.2.2 ? thats the only way to retain write protection on 4.4.2
Click to expand...
Click to collapse
Well crap. I can't believe I missed that step... Is it safe for me to flash back to 4.2.2 (using safestrap recovery), remove WP and then upgrade again? I'm guessing I'm stuck...
slgooding said:
Well crap. I can't believe I missed that step... Is it safe for me to flash back to 4.2.2 (using safestrap recovery), remove WP and then upgrade again? I'm guessing I'm stuck...
Click to expand...
Click to collapse
I'm pretty sure you can run MotoWpNoMo while on 4.4.2, I might be wrong but I think someone did it in my Verizon 4.4.2 thread. I will check the comments later.
iKrYpToNiTe said:
I'm pretty sure you can run MotoWpNoMo while on 4.4.2, I might be wrong but I think someone did it in my Verizon 4.4.2 thread. I will check the comments later.
Click to expand...
Click to collapse
I just ran it MotoWpNoMo within 4.4.2. It WORKED. I verified with the following command: adb shell getprop ro.boot.write_protect
This means that for anyone that didn't remove write protection before updating (but had rooted prior to update) you can still disable WP.
slgooding said:
I just ran it MotoWpNoMo within 4.4.2. It WORKED. I verified with the following command: adb shell getprop ro.boot.write_protect
This means that for anyone that didn't remove write protection before updating (but had rooted prior to update) you can still disable WP.
Click to expand...
Click to collapse
Nah it still works because you're not on the 4.4.2 bootloader!
I was succesfully able to update to 4.4.2 with this update.zip. It is working great and I still have root! I did forget to wipe before updating, but so far I haven't noticed any problems. If I do, I just do a wipe and reflash. Thanks!
RobertsDF said:
I was succesfully able to update to 4.4.2 with this update.zip. It is working great and I still have root! I did forget to wipe before updating, but so far I haven't noticed any problems. If I do, I just do a wipe and reflash. Thanks!
Click to expand...
Click to collapse
Glad to hear, Enjoy!
Just updated my wife's moto x as well. Once again, it's working great.
Sent from my XT1049 using Tapatalk
settings are force closing when I try to access it.
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
If you happen to be a Dev if this bug is either confirmed or absolved, I have a bug report I can share if needed.
-------------------------------------------------------
Sent via my Republic Wireless XT1049 Moto X with Tapatalk Pro.
-------------------------------------------------------
PM or e-mail me if you want to as well starting @ $5/month!
-------------------------------------------------------
Hello guys,
Just curious - Is anyone that successfully unlocked their bootloader (on Republic Wireless Moto X) with China code interested in selling their unlocked moto X?
I'm disappointed that I missed the bandwagon, so this may be my only opportunity to obtain an unlocked unit.
Thanks,
samwathegreat
EDIT: Offer withdrawn. Got BL unlocked. Thanks anyways.
EeyoreSyndrome said:
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
Click to expand...
Click to collapse
I used Malcolmputer's exploit instructions and packages so that may be the difference but you are the first one to report this issue in either this thread or his.
Try booting into Safe Mode. That will tell you if it is an app conflict. Android Device Manager, and probably others too, can tell you what order your apps were installed in so that you can trace back to find the rogue app if Settings no longer does an f.c. in Safe Mode.
If it still crashes in Safe Mode then remember: The first rule of the Force Close club is -- don't let your cache talk to Android! The SafeStrap ROM was a bit of a learning curve for me (or I just worry too much) but if you go into it and Select WIPE there are 4 checkboxes. Start with just the cache. If you have already done that then ...
The next step is to wipe cache and Dalvik cache. Your phone will take much longer to boot up after that as it needs to rebuild the Dalvik cache. It will show you app by app until it finishes.
Malcolmputer has said that his idea was that if things went wrong that you could:
I did it. I now have an update.zip that you can flash from SafeStrap, keeping your recovery where it is at already.
This means that if you f- something up, you can just sbf back to stock 4.2.2, root, safestrap, my update.zip, and then be back at rooted 4.4.2, with WP off.
Click to expand...
Click to collapse
I sure hope it doesn't come to that.
I also haven't seen any reports of anyone trying it either, so ...
EeyoreSyndrome said:
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
If you happen to be a Dev if this bug is either confirmed or absolved, I have a bug report I can share if needed.
-------------------------------------------------------
Sent via my Republic Wireless XT1049 Moto X with Tapatalk Pro.
-------------------------------------------------------
PM or e-mail me if you want to as well starting @ $5/month!
-------------------------------------------------------
Click to expand...
Click to collapse
Did you flash the new 4.4.2 baseband? There was issues with 4.4 if you didn't flash the baseband you would have FC's in the security settings.
iKrYpToNiTe said:
Did you flash the new 4.4.2 baseband? There was issues with 4.4 if you didn't flash the baseband you would have FC's in the security settings.
Click to expand...
Click to collapse
Maybe I was impatient in flashing the last two things
OBV if I didn't flash the kernal, it would simply not boot right?
On the kernal / baseband flasher, I get to "flashing modem" then done on my fastboot screen.
But the program seems to stick at "writing modem".
After unplugging the usb cord and then back in, it then finished erasing partition modems 1+2 and then flashed the fsg.
Okay, seems that I didn't properly flash the baseband on the first go, thanks for helping me troubleshoot! At least I can confirm that not having that updated baseband = force closing in settings app.
EeyoreSyndrome said:
Maybe I was impatient in flashing the last two things
OBV if I didn't flash the kernal, it would simply not boot right?
On the kernal / baseband flasher, I get to "flashing modem" then done on my fastboot screen.
But the program seems to stick at "writing modem".
After unplugging the usb cord and then back in, it then finished erasing partition modems 1+2 and then flashed the fsg.
Click to expand...
Click to collapse
I had this issue one time while trying to flash a kernel using my new usb 3.0 ports it ended up borking my phone pretty bad had to rsd several times to 4.2.2 to fix. I only use my usb 2.0 ports for flashing now. When do you get FC, is it as soon as you open the security settings or is it when you check unknown sources?
Hmm I used my USB 3.0 as well, didn't stop to think about it.
As for what your Bork was, what happened?
The FC happened as soon as I clicked on security, couldn't make it futhur then that.
As it is, things seem fine now, tho If you feel I should reflash em on USB 2.0, let me know.
Sent from my XT1049 using Tapatalk
Since there seems to be no way of installing current (and future) patches from stock recovery when the device is rooted, it'd be good to know if someone has information about whether it's possible or not to develop a custom recovery. The old method using 5.02 droidboot won't work because the updates mess up the whole system if you use them. So since we have unlockable bootloaders in 5.1, could there be the possibility of compiling a permanent CWM?
since there seems no one to be working on it at the moment, i'll start a few tries myself and document the progress in this thread. Feel free to help or comment.
For now, i', stuck at unlocking the bootloader and still don't know why. "OEM unlock" was set in the developer options, rebooted to fastboot and tried "fastboot oem unlock". Results as attached. :\
I'll google a bit around and see if i can get it working....
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
He's asking about a recovery that can be installed to the recovery partition, not just tethered.
It's possible, but we'd need somebody to build one. I tried one a while back from the Zenfone 2, but it didn't want to boot.
jumpup said:
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
Click to expand...
Click to collapse
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
toxic_garden said:
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
Click to expand...
Click to collapse
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
@xBIGREDDx made some instructions on this. Let me find it.
http://forum.xda-developers.com/showpost.php?p=64391058&postcount=16
This is not straightforward, but you *can* get to tethered CWM and root your 5.1 system. I did exactly this.
jumpup said:
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
Click to expand...
Click to collapse
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
toxic_garden said:
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
Click to expand...
Click to collapse
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
jumpup said:
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
Click to expand...
Click to collapse
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
However, I have always used a multi-tiered backup system:
* Titanium Backup (FULL on Sunday, INCREMENTAL every other day)
* Online NAndroid Backup (One per week using CWM format)
Each app's backup data syncs to the home NAS and Dropbox once a week.
I thought I had the Stagefright fix already in place. That's why I wanted to compare build/version details with a device that has the fix installed.
jumpup said:
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
Click to expand...
Click to collapse
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
toxic_garden said:
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
Click to expand...
Click to collapse
D'oh. I should have remembered about the data encryption. Need more caffeine
If you need anything tested or confirmed in the field, I'd be glad to help.
Sent from my Venue 8 7840 using Tapatalk
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
jumpup said:
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
Click to expand...
Click to collapse
oops you're right. Didn't even notice.
First steps forward: it seems like it's not possible to unlock the bootloader with installed sf-patch. No matter which version of fastboot i tried, i always got "FAILED: (some text i can't remember)". After downgrading to 5.1 stock firmware, unlock was possible. So as i now at least have the possibility to boot another recovery, i'll try setting up the build env. The Recovery Builder from CWM seems to be out of order at the moment.
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
I now have the Stagefright patch installed. Used the 5.02 droidboot temporarily to engage tethered CWM and install SuperSU. Reflashed 5.10 droidboot and firmware before proceeding. All is well. As you mentioned, it makes for a mixed 5.1 boot system, but I simply cannot live without root.
Here are the new build/version details:
After taking your advice and flashing the sg droidboot, my IWFI version is in line. I'll see if any system issues occur.
Is anyone still working on the 7840? Would be nice to have TWRP or CWM
I've been poking around on my 7840 on and off for a few weeks now. I seem to have verified that, after unlocking the bootloader, you can modify the boot and recovery partitions to your heart's content. However, any time I rebuild the kernel myself, I end up back at the "Dell" screen, frozen. Any other files are free game.
Assuming that the kernel needs to be signed using some tool I haven't figured out yet, I'm going to see if I can get a version of CWM working w/ the stock kernel. I tried dumping the version from the tethered recovery onto the recovery.img, but running it results in a black screen. I'll keep poking around though.
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Anyone? Even a, "Yeah, that's weird man! Sounds like you did everything right!" Would make me feel better...
Yes I've tried it and it worked make sure u have the unofficial safestrap the one for your phone and do the busy box and terminal emulator thing and it works if you try to install safestrap without the other things you will brick I did it twice but it very easy to unbrick so download busybox terminal emulator and the correct safestrap for you device and also I'm on 4.4.2 also and there is only one rom i have found that works and its called superliter there ya go hope I help would provide download links but I'm not home
Also I forgot to mention your bootloader won't be unlocked it'll be bypassed and you will have a custom recovery
androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/page-2[/url]
forum.xda-developers.com/showthread.php?t=2605648
device specific safestrap recovery and image
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
schmitey said:
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Click to expand...
Click to collapse
Verizon spends a pretty penny when it comes to making sure their devices................. stay theirs i guess you can say when it comes to the boot-loader! To my knowledge their isn't a way of getting around that with a permanent recovery flash that completely replaces Verizon's stock recovery. I can almost guaranteeing you that your problem is Verizon locked boot loader. Stock recoveries are solely only their for their technicians, so unless someone somehow has leaked a program that they use to get around that stuff without screwing it up, we the general public will never be able to flash anything permanent with any phones stock recovery unless we have their "secret" software! Every once in a while you do find a leaked one. I got lucky and found one for the T-mobile galaxy S6 Edge. As far as Odin I've noticed that the new versions seem to be very particular. Meaning if a dot or a space is misplaced anywhere in the zip or what not it will always fail. With my t-mobile S6 I spent two days figuring out I had to take a letter out of the name of the file i was trying to Odin. One letter that was it and once I did that it went flawlessly. Otherwise man i really don't know what to tell you, seems like ya followed the lines as described. Just remember its a Samsung Galaxy in my opinion Galaxies are unbrickable. Ive even pulled the cord in the middle of a Odin flash to see if i could brick it for good and was still able to go right into download mode and flash stock back onto it and everything working. So don't be afraid of bricking it. It will be way easier (sorry to say) for you to re-flash stock right now! Good luck bro wish you the best!
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
schmitey said:
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
Click to expand...
Click to collapse
Are you able to disable Signature verification in the recovery?
Are you able to disable Signature verification in the recovery?
You can once I flash to say clockworkmod recovery. Stock I don't know of a way to...hence the Catch 22 there's no going forward and no going back...you're stuck with stock ROM/recovery but at least its rooted.
Well ****. Take my word for it you CAN brick a galaxy s3.
I used KIES to restore back to factory stock recovery etc etc.
I then used towelroot to root phone and install supersu. I then installed safestrap which totally worked! I was able to bypass the stock recovery and everything was running smoothly...I got overzealous and tried to install the cyanogenmod vrale6 bootloader zip through safestrap. I currently have a brick. It won't boot, no led's, no screen, no vibrate. I have another galaxy s3 charging batteries and swapped it out...removed sim and micro sd. I should have just installed the cyanogenmod app and done it that way...
So close and now I bricked it...
OK got my brick back by writing image to microSD card...pretty happy about that little trick. And that's utter nonsense about needing the same size card as your internal memory! I used a 32gig card on a 16gig phone...
Still trying but this locked 4.4.2 bootloader is BULL****. Going to try to downgrade but I'm not sure I'm going to end up with anything but a rooted stock rom...
So does anyone know of a way to downgrade or change recovery on Verizon 4.4.2?
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
slimcyril said:
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
Click to expand...
Click to collapse
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
schmitey said:
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
Click to expand...
Click to collapse
Well no zip has ever failed on my end using safestrap, does your device have init.d support?
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
schmitey said:
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
Click to expand...
Click to collapse
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
slimcyril said:
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
Click to expand...
Click to collapse
system partition is NOT checked within safestrap. Installed universal init.d but I'm out of my league on it... Init.d says stock kernel does not have support...