Any devs wanna help - Droid RAZR M Q&A, Help & Troubleshooting

Are there any devs that would be interested in a new challenge? The electrify m for us cellular is the sister to the RAZR m but with an unlocked boot loader. Its a great phone just need somebody to kick start the development on it. If you are interested here is the thread for the factory software image. I'm not begging just hoping somebody will.
http://teamuscellular.com/Forum/top...trify-m-stock-firmware-unlockable/#entry44454
Sent from my XT901 using xda premium

I am also hoping someone can assist us USC users with this. Our version is no longer rootable using the methods found here for the Razr m.
TIA!
Sent from my XT901 using Tapatalk 2

Meeeee toooooo!!!!
I'm not a developer, but I'm looking into a few things in regards to getting something going with this model. The biggest hurdle right now for me is figuring out how the partitions work on this thing and when they get mounted. Seems like they don't even exist until the damn thing is halfway booted up, so flashing from fastboot is a challenge. Once I figure out the right things to put into an updater script I think she'll be something we can work on. Again, I'm no developer, but I'm hoping I can gather enough peices of info that someone with more skills can take off with it.
In the meantime I'm cramming through the android sdk docs and java for dummies, smali stuff and xml. Hopefully I'll get to where I can start doing something before the phone is an antique.

dtrud0h said:
I'm not a developer, but I'm looking into a few things in regards to getting something going with this model. The biggest hurdle right now for me is figuring out how the partitions work on this thing and when they get mounted. Seems like they don't even exist until the damn thing is halfway booted up, so flashing from fastboot is a challenge. Once I figure out the right things to put into an updater script I think she'll be something we can work on. Again, I'm no developer, but I'm hoping I can gather enough peices of info that someone with more skills can take off with it.
In the meantime I'm cramming through the android sdk docs and java for dummies, smali stuff and xml. Hopefully I'll get to where I can start doing something before the phone is an antique.
Click to expand...
Click to collapse
Well as it is now, we can root using ADB commands with fastboot. You can either use CWM or TWRP, however CWM is a little more involved, so most people are just using TWRP.
Once rooted, CM10 can be flashed onto the M, but NFC and Wifi Direct don't work, which generally isn't a deal breaker for anyone on the Electrify M. However, it's a careful process since anyone flashing to CM10 will need to restore the APN settings.
Personally, I just kept it stock JB, but rooted. CM10 was too much of a headache to bother with after I screwed up the first time and had to flash stock in an emergency when on vacation. haha!
This is all being discussed on another website, and since I don't know the rules about posting external links, I'm not going to =)

Related

Problems with the root!

Hi, my phone now is working and all ( the is it bricked post) Thanks guys
Here is the new problem...I would like to go to 2.2.1 ( the passimg.zip is 2.2) is there a way to update without unlocking bootloader.
I tried Androot and superoneclick....Androot gives me the Fugu message and SuperOneClick says its Rooted...but when I go to rom manager or other apps that need superuser...
I get this message : An error occured while attemting to run privileged commands!
So basically Root isn't working.
Also, when trying to install Cyan cm6...Rom manager reboots...but I get the Triangle with the exclamation point with the green man next to it...
Is it still possible to have my cake and eat it? ( locked phone, with root access so I can install modded roms)
Again...can someone help me with this
Thanks!
You didn't have to make a duplicate post. I already answered one of your questions in the other thread.
Dont make another post next time...
I rooted FRG83D with superoneclick root, But if its not working for ya you will have to unlock the bootloader via fastboot. Then push a custom recovery. With the recovery you can install the su binaries.
Manual root:
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
Ok i'll only answer here now for this question:
I don't want to loose my warranty. Hence the softroot way.
I thought of something dunno if its possible:
is there a stock FRG83 image like the FRG33 I just installed....maybe 2.2.1 will be compatible with androot or superoneclick
Thanks
You need to do a few things before you go any further. There are key steps you are leaving out that are just a recipe for disaster. I'll detail them below, in the specific order you should follow them. There shall be no deviation from this list.
1 - Put your phone down. Seriously, stop messing with it. Just quit.
2 - Read the Wiki that you've been linked to, in both threads, several times.
2a - Now that you've read the Wiki, really read the Wiki. Yeah, you skimmed it the first time, I know you did.
2b - Now go read it again. I'm sure you'll notice something new this time.
2c - Now go read the links in the Wiki. Explore those threads.
2d - Those threads that the Wiki links to? They have links in them. Go read those.
3 - Rinse and repeat all steps from 2a to 2d for, oh, about 4 days. During this time you are allowed:
To post general chit chat on the forum. No technical stuff, no help threads, no questions. Just read. If you have questions, you need to read some more.
No more than 3 app installs per day, from the market. Thou shalt not download and install any APKs from any source that is not the Android Market.
To tweak settings on your phone, provided those settings are all done via the touchscreen on your phone. You shall forget the acronym "ADB".
Once you've done that, you'll root your phone in no time, and you won't be worried that you've bricked it. Then, and only then, can you start asking questions.
Why? Because all of your questions right now are answered. You're jumping the gun, and it's obvious you haven't done much research at all. Seriously, go read.
I hate to be mean, but if you want to understand stuff, you need to try and understand it on your own first. You're here looking for solutions (that are already spelled out) to problems that you created (because you didn't read anything). Quit looking for the easy way out. If you want to enjoy your phone and the features of what you're trying to accomplish...put some work in yourself, and stop expecting everyone else to fix everything and spell it out. People here are more than happy to help, but you gotta start helping yourself.
@Soberguy: Thumbs up to you. Couldn't have said it any better.
musashiken said:
@Soberguy: Thumbs up to you. Couldn't have said it any better.
Click to expand...
Click to collapse
Thanks, mate. Didn't mean to quote the guy above me, just noticed I did that. Fixed it.
I'm amazed at the patience some folks have. Maybe it was my rough 3 day weekend that's left me a bit short... Appreciate the thanks, all the same.
Ok, I do go a bit fast.
I'll read...it just that I tried the cm7 mod ( i know its experimental) and the phone
would'nt boot.
With the help of the great people on the board, I got my phone working again but on FRG33 (2.2)
My last question was if it was possible ( or someone knows of because Ive checked the net) to root without unlocking ( androot and superoneclick that i know of) if I have FRG33 ( Because Ive been getting permission errors)
Finally, I wanted to know if a FRG83 stock image was available so that I could recover to it without unlocking bootloader. (or any other stock that lets me root without unlock)
I'll unlock the phone as a last option...I'm sorry...And if anyone is pissed at my posts ...well sorry I just taught some of you experts could help.
pooky2010 said:
Ok, I do go a bit fast.
I'll unlock the phone as a last option...I'm sorry...And if anyone is pissed at my posts ...well sorry I just taught some of you experts could help.
Click to expand...
Click to collapse
See? Looking for the easy way out again.
It's not about anyone being pissed or short on patience. Look at how frustrated you are with the situation. You're frustrated. Why? Cause you did it wrong. Why? Cause you didn't read enough first. Even after several suggestions, you still want it done, with help, right now, or you'll sulk about someone pissed and how no one held your hand through it.
Is it possible to do what you want? Absolutely! Pretty easy, too. But if you read and help yourself, you'll better understand how to update in the future, as well as how to root the future update. Or, you'll learn how to root what you have, and flash a pre-rooted stock ROM (yes, those are here as well).
So call me an ass, cool. You did in your mind, that's fine. But really, I'm trying to let you know what will help you the most, and that's having a better understanding of how to prevent a boot loop in the future, or at least how to fix it if it happens. Best of luck, man.
Sent from my Sexy Nexy, courtesy of the fine developers of Tapatalk
Here's the deal.
I did a one click root without unlocking the bootloader. Then I installed rom manager and flashed clockwork recovery. Then I did a backup ( both done in rom manager) then I went back into rom manager and installed cyanogenmod 7 and my nexus is now haxored gingerbread. Make sure you do a full wipe before flashing new roms and it'll always work.
I didn't update my radio, my hboot or anything like that. And it all just works and is dead simple. I would suggest trying z4root or universal androot and then downloading rom manager from the market.
How you managed to **** up something so simple is pretty funny dude.
I'm using an at&t band n1 with an smiled. Not the one with super LCD. I heard a rumor that the super LCD n1s have problems with certain mods. You might want to figure out what type of screen you have too.
The cyanogenmod wiki at cyanogenmod.com might help you too.
Sent from my Nexus One using Tapatalk
OP, you have to learn the hard way. Stop using "newbie" as an excuse.
I was also a "newbie" when I first got my Nexus One in February. Everything about android was new and alien to me. It actually took me a couple of months of lurking in xda and reading up on tutorials before I took the plunge to rooting my phone. And I did not bother anyone on that. I made sure I understood the steps and triple checked every move I made in following instructions even though I did not understand them.
I also was worried about warranty and actually did the manual way of rooting my phone without unlocking the bootloader using some method that involved cutting a piece of plastic from my battery. That was nerve wrecking and no where as simple as the superoneclick thingy you have now. Yet I survived and I did it on my own.
I must admit that you have to be a little bit confident in using computers and have some basic knowledge of typing commands in cmd. But everyone has to start from somewhere.
Seriously if it's too much trouble or too complicated, maybe staying stock or going Iphone is a more comfortable alternative.
I'm actually pretty good with computers...
Also, I have bricked 4 phones (the provider took them back) fooling around...
I could brought this one back ( they didnt check). But I want to learn...I'm pretty impulsif...Anyway so far
With FRG33 z4root works (read thanks)
Now I trying to flash clockwork...( when I download cyan 6 +google apps) it reboots but I get the triangle thingy...I click power volume up ( read that thanks) I get a blue menu...I kinda scared to click an option so I rebooted...I'm trying to use rom manager for updates because its really simple ...anyway
Thats it for tonight All of you guys are nice dudes and I'll learn and will try to help im my own way...I know I'm a newbie that likes short cuts (hell I read all day at my day job...lol) This is fun ( playing with male toys)
Thanks guys!

[Q] Is the Droid X rootable

I am thinking about getting a Droid X this afternoon. With the OTA update is it rootable and if so with what? Thank!
floridatank said:
I am thinking about getting a Droid X this afternoon. With the OTA update is it rootable and if so with what? Thank!
Click to expand...
Click to collapse
Not the OTA. You will need to sbf back to froyo and then upgrade to the pre rooted GB
Sent from my DROIDX using XDA App
bigshotrob22 said:
Not the OTA. You will need to sbf back to froyo and then upgrade to the pre rooted GB
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I went ahead and got it. It has 2.3.3 on it, Will Gingerbreak work on that? Thanks!
floridatank said:
I went ahead and got it. It has 2.3.3 on it, Will Gingerbreak work on that? Thanks!
Click to expand...
Click to collapse
Nope! Like I said its unrootable
Sent from my DROIDX using XDA App
Unrootable...
But that doesn't mean you can't root.
SBF to froyo.
Flash the 2-part gingerbread .zips.
Flash a custom rom (Liberty?)
Or stay on the froyo kernel...
and try MIUI or Cyanogen.
Be careful and read as much as you possibly can before starting. Myself and at least one other on here with the latest iteration of the X have ended up with boot looping or totally non-responsive devices.
I have started a thread with my findings. I am by no means an expert but I do have much experience with rooting devices going all the way back to the PPC6700.
Good luck.
getting stuck in a bootloop is part of the exploration process IMHO.
At least once per new ROM I'll flash something 'just to see what happens' and end up SBF'ing back. Just make backups between steps if you aren't sure about what will happen next.
it would be nice if one of the devs or people who work on rooting or someone in the know would at least comment if we are going to get a real root with the OTA
i mean im running froyo with CM7 but i sure would like the new firmwares for all the radios flashed and then be running CM7
so if someone could give us some kind of update at least saying no one is even remotely working on trying to gain root on 4.5.596 Official OTA or that yea we are working on it but it is a ***** and taken longer then we expected
that lil bit of info goes a long ways
thanks
I am not aware of any dev working on this ATM.
I don't think rooting 596 ota is critical 2nd unit has opened up alot of new doors and the attention has shifted. However I have flashed all of drew gardens latest and ran cm4dx until nightly 47. Now I'm daily MIUI and loving it, despite locked bootloader the cdma_shadow still has alot of options.
Sent from my DROIDX using XDA Premium App
to my understanding .596 has better battery life and signals are better for wifi and cellular (at least more stable and less drops)
i do not know if this is true but i have read/heard alot of ppl saying the battery life is better on .596
after all there is a .596 for some reason and its not a lil bump from 2.2.340 its pretty big
anyhow someone really needs to figure this out as the baseband has changed....i mean there is the pre-rooted rom .596 that works great so we know it can be done.
whats the big deal...let us have it
m16-maniac said:
anyhow someone really needs to figure this out as the baseband has changed....i mean there is the pre-rooted rom .596 that works great so we know it can be done.
whats the big deal...let us have it
Click to expand...
Click to collapse
the big deal is that there isn't a readily found exploit for the ota, the pre-rooted was done with a diff. method (brute force? recompiled?) but the versions are the same regardless
no ones holding back a secret root method, there just isn't a dev interested in spending huge amounts of time to recreate what already exists
i think it would be interesting to create a batch script that sbf's a phone and installs the pre-rooted .596 but all hidden behind a random animation so the user doesn't see what's happening. if i call it a 'one click' root method lots of people who don't seem to want to take the readily available pre-rooted gb for whatever reason would likely be happy. yeah i understand that if it includes a sbf then data may get lost, but if i said in the instructions of my 'app' that it would happen and they should have backups, people would still likely use it
sorry, but i just don't understand why so many people who want root are seemingly against using the pre-rooted option, as most of them don't have the knowledge to find an exploit or a root method from scratch themselves, so they are still using the work of someone else...
<Disclaimer>I'm going out on a limb here with limited knowledge of the X. <End disclaimer>
From what I read and I don't remember where, the rooting of an X involves a 2nd init method by which it takes control of the initial init. I believe I read the original init isn't able to be exploited and this is the basis of some of the more complicated methods of rooting the X.
If someone knows more about this please correct me or chime in.
I had an Incredible prior. The rooting was more comprehensive and simple. I believe that is because the bootstrap and recovery were not as difficult to get into. That being said, personally, I may be going back to another HTC device if the folks light years smarter than me aren't interested in developing a root method like the other devices out there.

[i9003] Frustrated First Root

Starting off, I'm probably posting in the wrong section. Excuse my forum etiquette, but I need help with this because I'm insanely frustrated and in pain (Decided to learn how to exploit the android OS while recovering from my surgery).
So, if you've read past that first part and are still willing to help, thank you.
Moderators: If you absolutely need to move this post, please move it to a section where it will actually get attention and I can get an answer. Thanks.
Anyway, the breakdown of my problem is this;
I wanted to root my new day old Sprint CMDA Nexus S, I've never rooted anything android, and if anything the most I've done with a droid OS is installed it on my old iphone 2g.
So I did some googling and first thing to come up was this guide:
nexusshacks(dotcom)/nexus-s-hacks/how-to-root-nexus-s/
Now, usually I would do a bit more research, but because of the lack of blood in my body I'm doing dumb things, making bad decisions, whatever.
So obviously this guide doesn't work, even a quick skim of the comments shows that, I try to follow this guide-
I followed step "fastboot flash boot rootboot.img" then tried to reboot. It freezes at the google boot logo. This is where I start getting a bit nervous because I have absolutely no idea what I'm doing.
So I think "Well, if I jump over to someone elses tutorial and do that it should overwrite any "root"ing data I've tried to put into the device.
So I jump over to this:
androidadvices(dotcom)/root-sprint-nexus-gingerbread-235-update/3/
It has me install PDANet and it's frozen since on the installing PDAnet to your phone.
I just want to get my Nexus S back to original factory default so I can start fresh from there without a terrible guide.
Can someone please help me get there?
Thanks.
tl;dr:
Bad guide soft bricked my phone and I want to restore it to factory defaults
agnl said:
Starting off, I'm probably posting in the wrong section. Excuse my forum etiquette, but I need help with this because I'm insanely frustrated and in pain (Decided to learn how to exploit the android OS while recovering from my surgery).
So, if you've read past that first part and are still willing to help, thank you.
Moderators: If you absolutely need to move this post, please move it to a section where it will actually get attention and I can get an answer. Thanks.
Anyway, the breakdown of my problem is this;
I wanted to root my new day old Sprint CMDA Nexus S, I've never rooted anything android, and if anything the most I've done with a droid OS is installed it on my old iphone 2g.
So I did some googling and first thing to come up was this guide:
nexusshacks(dotcom)/nexus-s-hacks/how-to-root-nexus-s/
Now, usually I would do a bit more research, but because of the lack of blood in my body I'm doing dumb things, making bad decisions, whatever.
So obviously this guide doesn't work, even a quick skim of the comments shows that, I try to follow this guide-
I followed step "fastboot flash boot rootboot.img" then tried to reboot. It freezes at the google boot logo. This is where I start getting a bit nervous because I have absolutely no idea what I'm doing.
So I think "Well, if I jump over to someone elses tutorial and do that it should overwrite any "root"ing data I've tried to put into the device.
So I jump over to this:
androidadvices(dotcom)/root-sprint-nexus-gingerbread-235-update/3/
It has me install PDANet and it's frozen since on the installing PDAnet to your phone.
I just want to get my Nexus S back to original factory default so I can start fresh from there without a terrible guide.
Can someone please help me get there?
Thanks.
tl;dr:
Bad guide soft bricked my phone and I want to restore it to factory defaults
Click to expand...
Click to collapse
Ok I can see you need help but I am inclined to warn you instead. Stop. If you cannot figure out how to root the easiest phone to root then you shouldn't be messing around with your phone. You will end up screwing something up, won't know how to fix it, and come crying here for help. Do yourself some research before you go and ruin your phone.
Yes you posted in the wrong place.
There is a thread in this forum on how to root the nexus s 4g. Rooting is model specific. The T-Mobile Nexus s is different from the sprint, att, Rodgers, o2 etc.
Please please do some more research!
Sent from my PC36100 using XDA Premium App
Thanks for a reply, and I understand I dug a hole.
Now I need to get out of said hole, so if you had any directions of how to dig myself out, that'd be great.
if you can get into fastboot then you are still cool, if not you're gonna have to odin it. I dont actually know where the tar files are, Micheal posted it up but i think they deleted the thread. You should have came to xda first,we have one clicks.
actually rooting is the same across the board. same steps same everything... in fact the one click root version 1 would work on any and all of them, version 2 branches out a bit further due to that it installs cwm.
anyways boot into fastboot, download stock fastboot images from petes thread found here http://wonderly.com/bb/CRESPO4G/OEM/GRJ22IMAGES.zip and flash them all in fastboot.
youll be back on stock grj22 but youll at least be booting.. from there follow a guide for rooting this phone that has you flash cwm (not a prerooted kernel). or be lazy and use my one click root
You sir are a class act. We need a ton more guys like you here at XDA
shabbypenguin said:
actually rooting is the same across the board. same steps same everything... in fact the one click root version 1 would work on any and all of them, version 2 branches out a bit further due to that it installs cwm.
anyways boot into fastboot, download stock fastboot images from petes thread found here http://wonderly.com/bb/CRESPO4G/OEM/GRJ22IMAGES.zip and flash them all in fastboot.
youll be back on stock grj22 but youll at least be booting.. from there follow a guide for rooting this phone that has you flash cwm (not a prerooted kernel). or be lazy and use my one click root
Click to expand...
Click to collapse
mikeyinid said:
You sir are a class act. We need a ton more guys like you here at XDA
Click to expand...
Click to collapse
+1
Sent from my Nexus S 4G using XDA Premium App
mikeyinid said:
You sir are a class act. We need a ton more guys like you here at XDA
Click to expand...
Click to collapse
lol you give me way too much credit mikey but thanks for teh vote of confidence

[Q] Root for US OTA 2.0

So I'm going to go out on a limb and say that there is no solution to root a TP that's already applied the 2.0 update?
I've tried the root methods already obtainable on here and they don't work. I'm guessing (more hoping) that someone is working on finding a solution.
Makes me sad. A co-worker updated it for me because "it said it needed to update it so I did it for you"... *sigh*
OTA2 removed the exploit unless you were already rooted and used Voodoo Rootkeeper to maintain root during the update. I haven't heard the outcome with regards to 2.5. I don't want to risk root so won't be updating unless it's safe.
2.5 is out ? which your version of tablet ?
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Either people like us find a way to downgrade or wait until a new exploit is found. The former seems easier but my knowledge of these things isn't very high...
Yeah, I'm not sure how to either. I'm good at following directions but when a "friend" upgrades your device for you...
As for downgrading, I don't think that'll be an option until someone finds a Lenovo rom flash utility.
byersbw said:
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Click to expand...
Click to collapse
2. 5 was not available to US last week. How did you get it? Supposedly it's still going through certification. 0086_US is 2.0. What version are you?
Oh hell.... I've been reading too many posts on the Lenovo forums. My apologies, I am running OTA 2.0 NOT 2.5. I will correct my first post and title.
I'm running ThinkPadTablet_A310_02_0039_0086_US.
Okay. Thanks. No worries, but was scratching my head, looking puzzled.
Haha! I can understand. I have that look a lot sadly. I appreciate you telling me as I had no clue as to what exactly I was saying.
Now, if anyone knows someone on the inside at Lenovo that could get the flash utility...
LOL If only.
And now we wait. Did NOT expect CM9 to come out so fast and be working so didn't care much for root otherwise. Oh well, that was my fault and I knew I'd lose root for the time being. Now I wait patiently, since the primary work of the developers now is making CM9 to work properly so w/e.
Why isn't there a way to downgrade the rom to 075? The tab has a recovery boot. If it could be downgraded, it could then be rooted , then updated.
No way to downgrade, unless you know something the rest of us are unaware of. There's a bunch of folks that either can't root at all, or took OTA2 before getting root/without preserving root. We've been told that there's nothing to be done for the time being.
I don't know how to do it, but I know that's how other tabs got around the problem. I only say it in case someone does.
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Thanks. Noob enough that I couldn't explain it, just knew it doesn't work.
YassinTP said:
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Click to expand...
Click to collapse
I wonder what it takes to defeat the check? There must be an update script that performs that check. Editing elements of the update script has been the key to other "can't be done" situations.
http://forum.xda-developers.com/showthread.php?p=22918839[WIP][4.0.3]ICS CM9 ThinkPad Tablet PORT
I'm going to keep putting forth suggestions instead of claiming something can't be done. Afterall, the point of this entire forum is to work togther to overcome obstacles.
While I don't know a lot about these things, if it could be done, it would have been. This forum is overflowing with posts from owners of all kinds devices asking how to downgrade their respective device so they can take root. It's not an uncommon request, and one that I have researched for another device, only to find the same answer. Hey if you find out how to do it, you'll make a fortune.
Two other tablets, the Flyer and the View downgrade to gingerbread, then unlock bootloader, then root, then update to honeycomb, then custom roms are applied. They got the idea from another tab, the Iconia, who got it from the Transformer . . .
I'm just trying to push good and bad ideas to someone with the skills. It's about not taking 'no' as an answer.
Here's the thread for Flyer/View:
http://forum.xda-developers.com/showthread.php?p=21028879[Procedure]No HTC unlock downgrade HC-GB for official OTA

[Q] Challenge: I've messed up my new RAZR

Hey XDA! Just picked up new Droid RAZR M (XT907) and immediately messed it up on the first day. So here's the deal:
- I'm an idiot.
- Got it with 98.30.1 FW, so I used this method to root it: http://www.droidviews.com/root-verizon-droid-razr-m-razr-hd-maxx-hd-latest-firmware/
- Forgot to unlock the bootloader
- Installed ROM Manager and flashed CWM recovery
And this must have messed up something, because now I'm not able to:
- Unlock my bootloader
- Get into recovery, it returns this error: "failed to hab check for recovery 0x56"
I'm clueless now, since I have not much knowledge in this stuff...
I'd be so thankful if anyone could help me
Thanks!
Edit: Will this help me? http://www.phonearena.com/news/How-...-M-back-to-stock-ICS-from-the-JB-leak_id35580
Edit 2: Okay, so that didn't help, but I used "DROID RAZR M Utility 1.20" from mattlgroff and I was successful with bringing OG recovery back. However, I found out that the bootloader on my build just can't be unlocked. I also tried to install Safestrap and install CM on another slot, but it failed with status 6. Why is that? Or is there just any other way how to install any ROM?
krYshuT said:
Hey XDA! Just picked up new Droid RAZR M (XT907) and immediately messed it up on the first day. So here's the deal:
- I'm an idiot.
- Got it with 98.30.1 FW, so I used this method to root it: http://www.droidviews.com/root-verizon-droid-razr-m-razr-hd-maxx-hd-latest-firmware/
- Forgot to unlock the bootloader
- Installed ROM Manager and flashed CWM recovery
And this must have messed up something, because now I'm not able to:
- Unlock my bootloader
- Get into recovery, it returns this error: "failed to hab check for recovery 0x56"
I'm clueless now, since I have not much knowledge in this stuff...
I'd be so thankful if anyone could help me
Thanks!
Edit: Will this help me? http://www.phonearena.com/news/How-...-M-back-to-stock-ICS-from-the-JB-leak_id35580
Edit 2: Okay, so that didn't help, but I used "DROID RAZR M Utility 1.20" from mattlgroff and I was successful with bringing OG recovery back. However, I found out that the bootloader on my build just can't be unlocked. I also tried to install Safestrap and install CM on another slot, but it failed with status 6. Why is that? Or is there just any other way how to install any ROM?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3
Thanks, but I don't need that. I just expected a simple answer. So I'll just answer myself, sum up what I needed to know. Correct me if I'm wrong:
- There's no way I'm going to unlock my BL, I'm stuck with locked BL on my build
- There's no way I'm going to install CM (not even using SS)
- I can only wait on official Motorola KitKat update (coming in months???)
- I can also install some stock-based ROMs with SS
Yeah, I don't wanna Safestrap with custom stock-based ROMs if it can't be official CM. I'll rather keep my internal storage space with stock, disable bloat and wait for official 4.4.2 update...
krYshuT said:
Thanks, but I don't need that. I just expected a simple answer. So I'll just answer myself, sum up what I needed to know. Correct me if I'm wrong:
- There's no way I'm going to unlock my BL, I'm stuck with locked BL on my build
- There's no way I'm going to install CM (not even using SS)
- I can only wait on official Motorola KitKat update (coming in months???)
- I can also install some stock-based ROMs with SS
Yeah, IFon't wanna Safestrap with custom stock-based ROMs if it can't be official CM. I'll rather keep my internal storage space with stock, disable bloat and wait for official 4.4.2 update...
Click to expand...
Click to collapse
Simple answer.
Do you know how many times it has been summed up! For you to find if you just searched! Or just browsed the thread titles in the general forum!
That page is all YOU need.
We need it sticked.
There is an old ss cm btw. See dev section.
aviwdoowks said:
Simple answer.
That page is all YOU need.
We need it sticked.
There is an old ss cm btw. See dev section.
Click to expand...
Click to collapse
Yeah, that page is also A LOT of stuff I DO NOT need.
You didn't get that. Simple answer is something else than you may think and also best answer is something really distant.
I just wanted a direct response or confirmation of what I said, not this negativism. Yeah, but what could I expect, typical XDA attitude...
krYshuT said:
Yeah, that page is also A LOT of stuff I DO NOT need.
You didn't get that. Simple answer is something else than you may think and also best answer is something really distant.
I just wanted a direct response or confirmation of what I said, not this negativism. Yeah, but what could I expect, typical XDA attitude...
Click to expand...
Click to collapse
I wanted...
We do not need the likes of you!
krYshuT said:
Yeah, that page is also A LOT of stuff I DO NOT need.
You didn't get that. Simple answer is something else than you may think and also best answer is something really distant.
I just wanted a direct response or confirmation of what I said, not this negativism. Yeah, but what could I expect, typical XDA attitude...
Click to expand...
Click to collapse
I do apologize you fell this way about the members here at xda... Here at xda we help a lot of people, take time from our day away from our loved ones to assist those in need... Avi helps a lot members a lot of members... You have to understand that your issue your question has been answered and resolved several times prior to this post... I'm sure just scrolling through the topics reading the titles you would have found the answer/s to your question/s (probably answered by Avi)... I understand the search feature of xda may not result in what you are looking for but google will... We do get very tired of answering the same questions over and over again... So i apologize for the "negativism" but Why help those who won't help them selves... knowledge is power and reading is the key...
Sent from my XT907 using xda app-developers app
krYshuT said:
Thanks, but I don't need that. I just expected a simple answer. So I'll just answer myself, sum up what I needed to know. Correct me if I'm wrong:
- There's no way I'm going to unlock my BL, I'm stuck with locked BL on my build
- There's no way I'm going to install CM (not even using SS)
- I can only wait on official Motorola KitKat update (coming in months???)
- I can also install some stock-based ROMs with SS
Yeah, I don't wanna Safestrap with custom stock-based ROMs if it can't be official CM. I'll rather keep my internal storage space with stock, disable bloat and wait for official 4.4.2 update...
Click to expand...
Click to collapse
To answer your question, yes to all. And before you jump so quick as to label this typical xda attitude, keep in mind I can label you typical self entitled noob expects everything on a silver platter. People get tired of answering the same question a hundred times over... Guess your number in line. Anytime you're dealing with a locked BL it's a good idea to learn all the intricacies of your phone, which is precisely where you were referred to.... And precisely where I had to start too. That said, politeness and gratitude will get you farther in getting noob answers quicker, which none of your posts contained.
Thanks! I'm sorry if it sounded rude, I'm really grateful for any type of help. I've spent like 5h in all kinds of threads, but most of the time I just get "half-answers" from just reading and reading and reading. I'm not expecting any type of extremely thorough answer, just a direct answer with confirming of what I said. Sending me another link (which I already read) just makes me even more confused. I just found out for example, that Koush's Helium doesn't work on Motorola devices. Does that apply for root method, too? If so, are there any other alternatives to backup & restore on my RAZR M (without and with root)?

Categories

Resources