Related
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!
Well i am trying to flash a droid x to cricket for a friend of mine. I have talk and text. I wasn't able to do all the flashing process at once so i just got around to trying to get data to work. I was using this tutorial.
http://www.myrootedandroid.com/thre...-Droid-X-running-Android-2.2-Froyo-to-cricKet
Now the link is dead.. I haven't been able to find another decent one on the net.. I tried to follow the droid tutorial as it looked similar to the droidx one, but i know there are some steps missing.
Another weird thing is i have noticed that there is no data status in the taskbar at all. It doesn't even say 1x. I tried the prl recommended in the tutorial above and i cannot update over the air with the prl. i also tried another one and it was also a no go.
Anyone have some decent instructions and possibly know why there isn't a data status in the taskbar? It almost acts like data is turned off.. I've noticed that there is no data enabled box to check under network connections.
I'm on Sprint with the Evo so i'm not hugely familiar with the Droid x. Thanks!
Here is the link you need
http://www.howardforums.com/showthread.php/1643218-Motorola-Droid-Full-Solution-Updated
boredmug said:
Well i am trying to flash a droid x to cricket for a friend of mine. I have talk and text. I wasn't able to do all the flashing process at once so i just got around to trying to get data to work. I was using this tutorial.
http://www.myrootedandroid.com/thre...-Droid-X-running-Android-2.2-Froyo-to-cricKet
Now the link is dead.. I haven't been able to find another decent one on the net.. I tried to follow the droid tutorial as it looked similar to the droidx one, but i know there are some steps missing.
Another weird thing is i have noticed that there is no data status in the taskbar at all. It doesn't even say 1x. I tried the prl recommended in the tutorial above and i cannot update over the air with the prl. i also tried another one and it was also a no go.
Anyone have some decent instructions and possibly know why there isn't a data status in the taskbar? It almost acts like data is turned off.. I've noticed that there is no data enabled box to check under network connections.
I'm on Sprint with the Evo so i'm not hugely familiar with the Droid x. Thanks!
Click to expand...
Click to collapse
Im taking off the instructions. There was a dilemna with the instructions so I rather take them off. Sorry.
bigshotrob22 said:
I was able to save this part from "http://www.myrootedandroid.com/threads/40-How-to-flash-Motorola-Droid-X-running-Android-2.2-Froyo-to-cricKet"...so credit goes the the author of this.
Click to expand...
Click to collapse
Please, don’t copy and paste the first thing you search for in Google without researching it a little further (not trying to be rude). That webpage is not even available anymore. I made a nice long post regarding the guide on the last page of the thread and now it’s gone.
While this is a nice starter guide, it's outdated, has unnecessary steps and incorrect files and might cause a major nightmare, trust me, that’s what I started out with and then, some time later, I have my own reformed way of flashing Motorola Droids to Cricket which I can do faster then it took you to read this post lol.
I have yet to see a guide or webpage to date that has the correct flashing process, tools, files and procedures. If I have some time in the future, I will release a proper guide. If you have any other questions for now, just PM me.
Couple quick things to the OP. You can not OTA with a flashed Droid on Cricket, your data is not working because you do not have the correct 4 series PRL or, there was a user error while using CDMA. You will not be able to *228 ever with a flashed Droid, all accounts must be set up first with your HEX MEID # converted to an ESN # that Cricket must have on file first in your account. If you've gotten to the QPST part of things, your done flashing.
Ben's said:
Please, don’t copy and paste the first thing you search for in Google without researching it a little further. That webpage is not even available anymore. I made a nice long post regarding the guide on the last page of the thread and now it’s gone.
While this is a nice starter guide, it's outdated, has unnecessary steps and incorrect files and might cause a major nightmare, trust me, that’s what I started out with and then, some time later, I have my own reformed way of flashing Motorola Droids to Cricket which I can do faster then it took you to read this post lol.
I have yet to see a guide or webpage to date that has the correct flashing process, tools, files and procedures. If I have some time in the future, I will release a proper guide. If you have any other questions for now, just PM me.
Couple quick things to the OP. You can not OTA with a flashed Droid on Cricket, your data is not working becuase you do not have the correct 4 series PRL or, there was a user error while using CDMA. You will not be able to *228 ever with a flashed Droid, all accounts must be set up first with your HEX MEID # converted to an ESN # that Cricket must have on file first in your account. If you've gotten to the QPST part of things, your done flashing.
Click to expand...
Click to collapse
First off I didn't copy and paste the first thing I found and secondly I have used this tutorial with no issues...Your also wrong about never being able to OTA update with cricket...I am able to do the OTA with my Droid X flashed to cricket using that tutorial. I agree this tutorial is a little outdated but it still gets the job done..
Sent from my DROIDX using XDA App
bigshotrob22 said:
First off I didn't copy and paste the first thing I found and secondly I have used this tutorial with no issues...Your also wrong about never being able to OTA update with cricket...I am able to do the OTA with my Droid X flashed to cricket using that tutorial. I agree this tutorial is a little outdated but it still gets the job done..
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Which build where you on when you used it and what build did you OTA to?
If it's just 2.2 then it might have worked, however, it's been sometime since then and most Droid's have already been OTA'ed with VZW. Go ahead, use the tutorial, the only thing that it will get done is a non working Droid X with 1x data speeds only. I do this on the side... I don't need to use some web guide and one which is crap. This is for the OPs discretion and I am trying to do him a favor. I am trying to save him and anyone else wanting to use that guide without know-how a major headache lol.
Ben's said:
Which build where you on when you used it and what build did you OTA to?
If it's just 2.2 then it might have worked, however, it's been sometime since then and most Droid's have already been OTA'ed with VZW. Go ahead, use the tutorial, the only thing that it will get done is a non working Droid X with 1x data speeds only. I do this on the side... I don't need to use some web guide and one which is crap. This is for the OPs discretion and I am trying to do him a favor. I am trying to save him and anyone else wanting to use that guide without know-how a major headache lol.
Click to expand...
Click to collapse
I must of been lucky to get mine working flawelessy then, huh? (sigh) If he gets 1x data or OTA doesnt work all he has to do is load another PRL like 32500 to get 3G. Its not the end of the world. If your so concerned for him just write another tutorial. Were all here to help out not bash on someones response...Like I said I used that tutorial and had no issues. I was able to root (eventhough z4 wouldve been easier) and load the prl to successfully do the OTA. Im done bickering with you. All im here to do is help out not argue.
P.S.
I took off the instructions so you might want to edit your response and delete the quote that had the instructions. I decided to take them off. Thanks
bigshotrob22 said:
I must of been lucky to get mine working flawelessy then, huh? (sigh) If he gets 1x data or OTA doesnt work all he has to do is load another PRL like 32500 to get 3G. Its not the end of the world. If your so concerned for him just write another tutorial. Were all here to help out not bash on someones response...Like I said I used that tutorial and had no issues. I was able to root (eventhough z4 wouldve been easier) and load the prl to successfully do the OTA. Im done bickering with you. All im here to do is help out not argue.
P.S.
I took off the instructions so you might want to edit your response and delete the quote that had the instructions. I decided to take them off. Thanks
Click to expand...
Click to collapse
I'm not trying to argue or bicker with anyone; sorry I came across that way. I was just trying to aim for a more factual answer.
I recently tried that guide to a T and found it to be a complete headache. I'm not sure what happened between now and six months ago but things have changed since and the OP of that thread never bothered to update it.
You still can't get 3G data or OTA with a 3 series PRL. You now need PRL 49027 and even then no OTA.
Ben's said:
I'm not trying to argue or bicker with anyone; sorry I came across that way. I was just trying to aim for a more factual answer.
I recently tried that guide to a T and found it to be a complete headache. I'm not sure what happened between now and six months ago but things have changed since and the OP of that thread never bothered to update it.
You still can't get 3G data or OTA with a 3 series PRL. You now need PRL 49027 and even then no OTA.
Click to expand...
Click to collapse
Thats weird like I said I followed it to the T as well and I was able to do the OTA update with no problem. I even flashed my phone to cricket 3 times and each time was successful. I had to SBF beacuse I was on .15 and I was getting stuck at the "m" logo. I SBFed with the .15 two times before actually reading that I needed to upgrade .320 to fix the "M" error (lol). If you want I can help you write a good tutorial.
bigshotrob22 said:
Thats weird like I said I followed it to the T as well and I was able to do the OTA update with no problem. I even flashed my phone to cricket 3 times and each time was successful. I had to SBF beacuse I was on .15 and I was getting stuck at the "m" logo. I SBFed with the .15 two times before actually reading that I needed to upgrade .320 to fix the "M" error (lol). If you want I can help you write a good tutorial.
Click to expand...
Click to collapse
I've flashed my own phone more than I care to count let alone other's
When did you flash your X? I might be incorrect about the OTA part since I have not been able to do so accross three builds but doesn't mean someone else won't have luck?
Thanks for your help Ben. I think i got a pretty good plan of action here now. I spent a couple hours yesterday jackin' with the damn thing yesterday so i'll be happy to get it to work correctly for her.
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
I have done some reading and finally decided I will be using the Casual method to root my S 4, but I am stock with not wanting to end up with the custom lock pad permanently, and I have seen many people have not been able to get rid of it.
So here is my question... After using Casual, what would be the way to get back to stock? This method installs custom recovery, so I am not sure how to go back if indeed to....
Can some one point me in the right direction?
Appreciated!
Before we move forward here, have you updated? As it stands the update released yesterday effectively blocks root and more then likely also blocks Loki. O and it blocks Odin so you can't downgrade. This is like first and foremost if you even wanna run casual now.
no update on my phone yet...
Sent from my SAMSUNG-SGH-I337
http://forum.xda-developers.com/showthread.php?t=2314494
post #1 is about rooting/flashing. post #2 addresses returning to stock, which literally is about as simple as flashing stock firmware via odin and factory resetting. cheers
Awesome.. I read that post but forgot completely about it.. most appreciated!
Sent from my SAMSUNG-SGH-I337
genesiss said:
Awesome.. I read that post but forgot completely about it.. most appreciated!
Sent from my SAMSUNG-SGH-I337
Click to expand...
Click to collapse
as Thermalwolf stated, your firmware version is important. make sure you dont have the latest MF3
No.. MDL still
Sent from my SAMSUNG-SGH-I337
If you're still on MDL I recommend rooting now before your phone tries to force MF3 on you as it blocks root and possibly loki.
Thermalwolf said:
If you're still on MDL I recommend rooting now before your phone tries to force MF3 on you as it blocks root and possibly loki.
Click to expand...
Click to collapse
Yea, talk about making it just under the wire, your lucky you decided to root today and that your phone hadn't already updated.
I feel for those poor souls that updated, personally I think loki is patched and I remember sitting around for months and months while people tried and failed to unlock the rezound bootloader, locked bootloaders can be a b***h
Take care of your non MF3 Galaxy S4's everyone, they just became more valueable ...
movielover76 said:
Yea, talk about making it just under the wire, your lucky you decided to root today and that your phone hadn't already updated.
I feel for those poor souls that updated, personally I think loki is patched and I remember sitting around for months and months while people tried and failed to unlock the rezound bootloader, locked bootloaders can be a b***h
Take care of your non MF3 Galaxy S4's everyone, they just became more valueable ...
Click to expand...
Click to collapse
Right?! This guy could not have picked a better day too root. Also I'm damn sure Loki is patched, we can't Odin back to MDL so that should speak for itself.
OP, Root and block the OTA APKs immediately! If your phone starts downloading just rip the battery out lol
Thermalwolf said:
Right?! This guy could not have picked a better day too root. Also I'm damn sure Loki is patched, we can't Odin back to MDL so that should speak for itself.
OP, Root and block the OTA APKs immediately! If your phone starts downloading just rip the battery out lol
Click to expand...
Click to collapse
I just rooted last night. I keep postponing the update. I did some searching and found that I should rename wssyncmldm.apk and reboot to block the OTA update. Is this correct? Is there another file that should be renamed?
Thanks!
ok just did it.. had some issues with Windows drivers but it turns out MAC worked just fine.. i am currently doing nandroid back up..
thanks to all for replies..
ok everything works just fine.. now.. what would be my next step
. how can I avoid update? so far I am interested in staying stock. maybe remove some apps and add some.. but how can I assure I will not update?
Sent from my SAMSUNG-SGH-I337
genesiss said:
ok everything works just fine.. now.. what would be my next step
. how can I avoid update? so far I am interested in staying stock. maybe remove some apps and add some.. but how can I assure I will not update?
Sent from my SAMSUNG-SGH-I337
Click to expand...
Click to collapse
You need to read the existing threads. Go to the 'General" section read the stickies and then read the threads about the new OTA. ALL of your questions are answered in detail in those threads. Good luck.
Hopefully this works for me
I Bought my S4 yesterday and the sales rep at AT&T pressed the update button before handing it to me. I didn't think anything of it because as far as I knew android was designed to be open and easily rooted. Man was I mad when I got home. So today I went back and complained that the "phone was glitchy" and was handed another one. This time I told them not to touch it. Hand over the box and nobody gets hurt (keep in mind I paid full price for it too so i was extra mad). This one is on MDL. Now to root and block update. Hooray!
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)?