Related
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
Hi all,
I see the android development section has a lot of goodies in there and i have had great experience with custom ROMs on my old Galaxy S1. But for the GN4. Is there any value addition to the stock ROM, in the custom builds so far?. Kindly share your feedback on the custom ROMs that you.
P.S: I haven't yet rooted the device (i know) ... can someone kindly send me the easiest way to do that as well.
Thanks a bunch for your time.
As far as rooting go just download the toolkit from the dev section follow the instructions on that thread.
And with the custom roms read the thread try them out every dev adds there own tweets. You can always go back to a backup
Sent from my E10i using Tapatalk 2
Personally, I read through the pinned threads and unlocked my bootloader, flashed touch CWM and rooted my phone right after getting it. As for custom ROMs - I don't feel the slightest urge as the rom is imho perfect; although I was a keen flasher before I sold my Galaxy S II.
Custom ROM for N4 are very stable and smooth like stock, maybe even more smoother. More feature like editing nav bar and so on. Happy flashing
Sent from my Nexus 4 using Tapatalk 2
Thanks guys. definitely gona root the device, gona make a nand and try a couple of customs out as well.
ChrisHRocks said:
As far as rooting go just download the toolkit from the dev section follow the instructions on that thread.
And with the custom roms read the thread try them out every dev adds there own tweets. You can always go back to a backup
Sent from my E10i using Tapatalk 2
Click to expand...
Click to collapse
Highly advise against doing this. Prefer yarox method do it manually as you'll need to do fast boot and adb commands eventually. Just take the 20-25 minutes and learn how to do it now. It's very easy and they are stickied for a reason.
Toolkits are very dangerous. The shortcut isn't worth it.
Sent from my Nexus 4 using xda premium
zephiK said:
Highly advise against doing this. Prefer yarox method do it manually as you'll need to do fast boot and adb commands eventually. Just take the 20-25 minutes and learn how to do it now. It's very easy and they are stickied for a reason.
Toolkits are very dangerous. The shortcut isn't worth it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Never liked them!! Besides you don't learn anything using toolkits...
yyz71 said:
Never liked them!! Besides you don't learn anything using toolkits...
Click to expand...
Click to collapse
Exactly. It's not like you're learning useless crap that you wouldn't use.
In fact for anyone flashing anything on their phone and not knowing a plan b if something goes wrong is scary, then they start panicking and out of no where make a forum thread. Bricked phone??? Uh no man. Anyone bricking a nexus device doesn't deserve one to be honest. It's so hard to brick one because of fast boot factory stock images.
A simple 20-25 minute step by step guide. It pretty much carries you through it and is more important than that lecture you attend every Tuesday that chances are you'd fall asleep because the professor isn't enthusiastic with his studies
Sent from my Nexus 4 using xda premium
May I suggest using wug's nexus root toolkit. Safe and easy with just clicking your mouse. You will be amaze!
Sent from my Nexus 4 using Tapatalk 2
droidmeup said:
May I suggest using wug's nexus root toolkit. Safe and easy with just clicking your mouse. You will be amaze!
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
No. Did you really just say that after what we just said?
It's easy using a toolkit but also very easy to screw up your phone because people using it are clueless and flash whatever links making their phone into a non boot able state.
http://forum.xda-developers.com/showthread.php?t=1469909 is a great read on this topic.
Sent from my Nexus 4 using xda premium
zephiK said:
No. Did you really just say that after what we just said?
It's easy using a toolkit but also very easy to screw up your phone because people using it are clueless and flash whatever links making their phone into a non boot able state.
http://forum.xda-developers.com/showthread.php?t=1469909 is a great read on this topic.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
But the thing is people can choose whatever method they want to root their phone. Old way using adb or the new step by step on screen instruction toolkit. I choose toolkit to root my n4 just to try it out. I was just amaze how wug's toolkit was so easy as it had on screen instructions every click. I don't see how newbies could brick using wug's toolkit. I don't really care what method people use.
Sent from my Nexus 4 using Tapatalk 2
droidmeup said:
But the thing is people can choose whatever method they want to root their phone. Old way using adb or the new step by step on screen instruction toolkit. I choose toolkit to root my n4 just to try it out. I was just amaze how wug's toolkit was so easy as it had on screen instructions every click. I don't see how newbies could brick using wug's toolkit. I don't really care what method people use.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
It's not the OLD way whatsoever. It's not newbies bricking their phones using the toolkit. It's what they do AFTERWARDS, go read the Q&A forums. Many of the problems coming out of threads are from users doing things that they don't understand because they lack the basic knowledge of the Android system with ADB & Fastboot (they mention toolkit in OP post). Some people rooted using the toolkit and they don't even know how to flash a flashable zip or even restore their phone back to stock because they want to send it in for a RMA.
Like I said in many threads, two methods,
1) Learn how to get from Point A to Point B by using a map and planning it out
2) Using a toolkit and have it get you from Point A to Point B without knowing how you got there.
Let's see what happens.
1) Since you planned it out and have a map beforehand using a step-by-step guide (its not hard) you can remap yourself on how to get there. What if you went to back half way because you forgot to pick up something at the store? You know how to get there
2) Toolkit... oh im at point B, i want to go to the supermarket at Point A.5, how do I get there? exactly. You don't know, you then proceed to ask questions on how to get there (in this case it would be Q&A forum on how to fix their phone because its not booting up).
By spending 20-25 minutes, people are aware of how fastboot works and how to restore their phone when its in a nonbootable state and not mistakenly say that their phone is bricked. This is XDA developers not XDA shortcuts
No one asked for your opinion on what method people used so I don't care that you don't care either?
Next time you should read the thread I posted before commenting. It has nothing to do with 'old ways' vs 'new ways.' If toolkit is the new way then oh man... we are in deep trouble.
Just like my two cases, he couldn't say it any better.
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Click to expand...
Click to collapse
I don't constantly post in threads about "OH DONT USE A TOOLKIT ITS TOO EASY. go old fashion with command prompt" for no reason. I do it with a good reason and no one should ever endorse toolkits for this very reason. Learn how to do it, it doesn't take a rocket scientist to know how to fastboot/adb when it's in a step-by-step tutorial. It's not hard to unlock a bootloader on a Nexus device. If it was a device with a difficult unlocking method through a exploit, then yes I would endorse a toolkit but for a Nexus its so easy to unlock.
1. set up ADB (do it once and you're SET for life on that computer.. dont have to do it again).
2. install ADB drivers http://forum.xda-developers.com/showthread.php?t=1514942
3. boot into bootloader using combo keys
4. command prompt into fastboot -> fastboot oem unlock
5. fastboot flash recovery <whateverthenametherecoveryis>.img
6. DONE.
@zephik
You've inspired me. I don't have my N4 yet but just got my 7 for Christmas. I'm going to pop it back to stock and redo the whole process manually.
I knew I was taking the lazy way out, you have guilted me into doing it properly as you said you learn nothing from a toolkit. Lol
Sent from my Nexus 7 using Tapatalk 2
ChrisHRocks said:
@zephik
You've inspired me. I don't have my N4 yet but just got my 7 for Christmas. I'm going to pop it back to stock and redo the whole process manually.
I knew I was taking the lazy way out, you have guilted me into doing it properly as you said you learn nothing from a toolkit. Lol
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Glad to know that I can do a kind of a change. If you need any further assistance or questions ahead of time, feel free to PM me.
Honestly, I'm not doing it to be a bad guy or to waste people's time. If it wasn't important, then I wouldn't stress how imperative ADB & Fastboot are to ANY device, but particularly towards Nexus devices. Fastboot isn't present in all devices, other devices such as Samsung Galaxy etc etc use Odin (Samsung's Firmware Flasher) which is the same thing but its more GUI friendly but it can still cause bricks and fastboot is easier in my opinion.
Just like what franco said,
Why would something happen? This kernel won't brick anything, a Nexus is pretty unbrickable unless someone is very dumb or simply a hardware bug ****s the device up. If anyone bricks this device or any Nexus I'll award him idiot of the year trophy.
Click to expand...
Click to collapse
It is REALLY REALLY difficult to brick a Nexus device, and I'm not surprised that it does happen to people because they use the toolkit and aren't aware of what they're doing. It's like solving a math problem, what's the point in getting spoon fed the answer? Just work it out. Except for Nexus devices, you don't even have to work it out!!! all you do is read a GUIDE that one person spent time on writing up. At least have the decency on reading it. You read it, and you do the step, then proceed until you're at the end. It's not difficult, and you get to know what you're doing it and why you are doing it.
People do things and their phone cant boot up but can access bootloader mode. They don't even know how to fastboot flash and then post a thread in Q&A forum saying their phone is bricked.
And you don't have to redo the 7 process lol. Manually unlocking bootloader is one thing and then knowing how to flash is the easy part.
Even the ghetto guide I posted a couple posts above works for any nexus device.
1. set up ADB environment (google sdk) basically get fastboot binary.. if you want ADB you'll need the adb.exe binary
2. install drivers http://forum.xda-developers.com/showthread.php?t=1514942
3. bootloader mode
4. fastboot oem unlock
5. unlock the phone on screen using vol keys
6. fastboot flash whatever.img [put in same folder as fastboot.exe]
7. done. you successfully flashed a 3rd-party recovery. now just put a zip file on the sdcard when android starts
8. receovery, wipe factory/dalvik/cache
9. flash rom,gapps(optional depending what rom), kernel (optional)
10. congrats you flashed a rom and kernel.
@zephiK. Thanks for the expert advice. I used Samsung S1 in the past and never used adb, was scared of it. I took your advice. Followed the guide and got rooted, the adb way. I have to admit. It was pretty satisfying to know what i was doing. Thanks again to everyone here.
thanks
zephiK said:
It's not the OLD way whatsoever. It's not newbies bricking their phones using the toolkit. It's what they do AFTERWARDS, go read the Q&A forums. Many of the problems coming out of threads are from users doing things that they don't understand because they lack the basic knowledge of the Android system with ADB & Fastboot (they mention toolkit in OP post). Some people rooted using the toolkit and they don't even know how to flash a flashable zip or even restore their phone back to stock because they want to send it in for a RMA.
Like I said in many threads, two methods,
1) Learn how to get from Point A to Point B by using a map and planning it out
2) Using a toolkit and have it get you from Point A to Point B without knowing how you got there.
Let's see what happens.
1) Since you planned it out and have a map beforehand using a step-by-step guide (its not hard) you can remap yourself on how to get there. What if you went to back half way because you forgot to pick up something at the store? You know how to get there
2) Toolkit... oh im at point B, i want to go to the supermarket at Point A.5, how do I get there? exactly. You don't know, you then proceed to ask questions on how to get there (in this case it would be Q&A forum on how to fix their phone because its not booting up).
By spending 20-25 minutes, people are aware of how fastboot works and how to restore their phone when its in a nonbootable state and not mistakenly say that their phone is bricked. This is XDA developers not XDA shortcuts
No one asked for your opinion on what method people used so I don't care that you don't care either?
Next time you should read the thread I posted before commenting. It has nothing to do with 'old ways' vs 'new ways.' If toolkit is the new way then oh man... we are in deep trouble.
Just like my two cases, he couldn't say it any better.
I don't constantly post in threads about "OH DONT USE A TOOLKIT ITS TOO EASY. go old fashion with command prompt" for no reason. I do it with a good reason and no one should ever endorse toolkits for this very reason. Learn how to do it, it doesn't take a rocket scientist to know how to fastboot/adb when it's in a step-by-step tutorial. It's not hard to unlock a bootloader on a Nexus device. If it was a device with a difficult unlocking method through a exploit, then yes I would endorse a toolkit but for a Nexus its so easy to unlock.
1. set up ADB (do it once and you're SET for life on that computer.. dont have to do it again).
2. install ADB drivers http://forum.xda-developers.com/showthread.php?t=1514942
3. boot into bootloader using combo keys
4. command prompt into fastboot -> fastboot oem unlock
5. fastboot flash recovery <whateverthenametherecoveryis>.img
6. DONE.
Click to expand...
Click to collapse
wow. good post. thanks a lot!
Is wallet working on all to Roms? Sorry to butt in this thread..
malikusmanrasheed said:
@zephiK. Thanks for the expert advice. I used Samsung S1 in the past and never used adb, was scared of it. I took your advice. Followed the guide and got rooted, the adb way. I have to admit. It was pretty satisfying to know what i was doing. Thanks again to everyone here.
Click to expand...
Click to collapse
Not a expert advice by any means. Just been around for a long time so I observe the commonalities between all users. I just really dislike it when people say or recommend things when really they don't know anything. Not saying I'm perfect by any means, but people need to stop being so cocky on the forums acting like they know everything. Instead of trying to defend themselves, ask questions on why I feel this way or whatever.
That's what forums are all about right? That's what XDA is all about. Spreading information. Not clicking a button that spoon feeds you something and you don't know how or why it's like that.
If someone gave you a car with one click (toolkit), what's the point in having a car if you can't drive it? (Toolkit) do you expect to click one button and the car drives you from home to where you need to be and back? What happens if it doesn't work? You ask questions on how to do this and th at.
You have to go through the procedure of learning how to use it. If you learn from the beginning (like I said, it's not hard, if it was then it's understandable about a toolkit) then it'll be a breeze. When I first got started, I was a lurker on XDA, I didn't post. All I did was read. I didn't have toolkits, I had to telnet my G1 to obtain root access through a exploit that took 40-55 minutes, one mess up and I would of bricked my phone and i had to do it with my hands, that's a scary thought knowing that you can't go back once you started. People nowadays should be grateful that unlocking bootloaders aren't as difficult anymore but yet people still feel the need to use a toolkit when it already is simple.
wow. good post. thanks a lot!
Click to expand...
Click to collapse
I didn't post it. That guy did. Definitely a great read and pretty much what I always believed in when I saw a toolkit. Should be banned from the forums but eh, who am I to call the shots
Is wallet working on all to Roms? Sorry to butt in this thread..
Click to expand...
Click to collapse
Yes Google Wallet works on any ROM as well as kernel. It says incompatible because you're rooted but it should work regardless of that text on the top of the app. Flash away!
Edit: May 5, 2009: http://androidandme.com/2009/05/beg...r-rooting-your-android-g1-to-install-cupcake/
August 17, 2009: http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
First guide one of the first rooting methods. August 17 is sort of one clickish but you still had to do a lot of things to get through it. So as you can see, it's not spoon fed to you, compare that to what you have to do now. Tell me that unlocking the Nexus bootloader is hard after reading all that ... it isn't.
@zephiK Can you link me to where it shows me how to root, and install CWM? Please
Sent from my Nexus 4 using xda premium
xxMAGICxx said:
@zephiK Can you link me to where it shows me how to root, and install CWM? Please
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2019273
I actually prefer TWRP over CWM. Your preference though.
Both can be found in Android Development Forum.
Sorry for dumb question but I am not able not excerpt the important steps of all these help and guide threads to install a Rom on my brand new nexus 7 without 3g. Hopefully someone can give me a guide
thanks in advance
SENSATION_XE said:
Sorry for dumb question but I am not able not excerpt the important steps of all these help and guide threads to install a Rom on my brand new nexus 7 without 3g. Hopefully someone can give me a guide
thanks in advance
Click to expand...
Click to collapse
You need to unlock boot loader, flash custom recovery and then flash roms.
Its best to search and learn for yourself to be honest. If you are fed the information on a plate, you will learn nothing whatsoever.
There are plenty of guides and help resources on Google.
This isn't me trying to be ignorant, it really is the best way as when or if you mess up, you will then need 1 to 1 help which ends up consuming massive amounts of peoples time.
I just released Loki, a set of tools for developers and users to flash custom kernels and recoveries on the AT&T and Verizon branded Samsung Galaxy S4.
The tool is available at:
https://github.com/djrbliss/loki
The technical details on how the exploit works are described at:
http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html
This is a support thread that I will check regularly until I decide to hand over support to the community. Feel free to ask any questions, and I may add the answers to this post. As a guideline, if it's a question that's already been answered in this thread or in the README for Loki, I will ignore it.
Does this make any permanent changes to the device?
No permanent changes are made to your device when using loki_flash. The bootloader itself is untouched. By restoring the original system, boot, and recovery images (via Odin or otherwise), the device will be in a stock state.
Can this be patched?
Absolutely. Any update that includes a new aboot will almost definitely cause your custom kernel or recovery to fail to boot without running it through loki_patch again, and if the update contains a fix for the vulnerability Loki exploits, it may permanently prevent using the tool. It's possible for Samsung to ship an update that prevents downgrading aboot to a vulnerable version, so I recommend avoiding installing any OTA updates without confirmation that it's safe.
What about the bounty?
As usual, I encourage anyone looking to donate (as part of the bounty or otherwise) to give their money to a reputable charity organization instead. If you insist on donating to me, I'm sure you can find my Paypal account somehow.
This all seems complicated. What about a step-by-step guide?
These tools are primarily intended for developers, who will be able to use them and provide ordinary users with easy ways to flash custom ROMs. Be patient, I'm sure your favorite ROM developer will come up with something for you.
I've installed a Loki-patched recovery. Can I just install regular custom ROMs now?
Any ROMs that include a replacement boot.img must be modified to include a Loki-patched boot.lok file instead. Otherwise, your phone will fail to boot until you restore a Samsung-signed boot.img or a custom boot.lok image via your custom recovery, or flash a stock image via Odin.
So this is just like kexec?
This is similar to kexec in that it works around a locked bootloader, but this approach is much more flexible and robust. Kernel and recovery developers can build their projects just as they would for an unlocked device, run the final result through Loki, and then it's ready to be flashed. No hackery and brokenness required.
Thanks!!
Sent from my SAMSUNG-SGH-I337 using xda premium
is this similar to htc dev which doesn't truly unlock "s-off" the device? i assume your method just circumvents the locked bootloader? the way i read what your tool accomplishes is for us to flash a recovery and kernels but doesn't actually touch the locked bootloader status?
thanks for your work. also let the games begin!
Thank you very much!!!!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Very much appreciated!
By the time I get back from work, I'm pretty sure there'll be at least two recoveries and three roms prepared
Wooooot!!! Thanks man.
Awesome! Finally devs can start releasing some ROMs!
hopefully someone can make a toolkit and make this a one-click unlock/root
Thanks so much! :good:
thanks dude.
RawisTheGameHhH said:
hopefully someone can make a toolkit and make this a one-click unlock/root
Click to expand...
Click to collapse
This or a step by step guide.
Theres already recovery available...
But thank you Dan, now all this bootloader madness can finally stop!
so we can flash a recovery and kernels with this tool but what about radios? can those be flashed with a locked bootloader? i swore they couldn't.
You are the MAN. A charity will be finding my donation per your recommendation.
Thanks again for all the great work.
Oh man, I'm dying here. I don't get off work for another ~6 hours! And I don't have admin access on my work computer, so no adb.
So, we have a patched recovery now, but custom kernels also have to be patched, correct? So it would be a bad idea to adb the recovery and then immediately try to use it to flash one of the roms that are already out there?
mattdm said:
Oh man, I'm dying here. I don't get off work for another ~6 hours!
So, we have a patched recovery now, but custom kernels also have to be patched, correct? So it would be a bad idea to adb the recovery and then immediately try to use it to flash one of the roms that are already out there?
Click to expand...
Click to collapse
i wouldn't try flashing any roms yet.
YES!YES!YES!
Dan, You are The Man!!! Thank you so much. May your thanks meter need a fire extinguisher before the day is done....lol.:good::good::good::highfive::highfive::highfive:
did a nadroid backup, and it is doing multiple archives, is there a setting I missed?
nevermind, I stand correct, nice, very nice, thanks goes out to everyone involved.
Solid.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
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)?