• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Newbie here again...Guess what?? :) :) :)

nardo89

Member
Remember me from yesterday when I started FREAKING OUT cuz my screen had gotten stuck & I thought I had "bricked" my phone???? Well not only have I recovered from that mental meltdown, but since this morning (following dangerously close to all the GREAT info I've found around this forum) I've been able to perform the S-Off on my V, and I've also been able to flash my very 1st custom ROM :) *Mobster ROM HD 012813*

I'm now ready to start playing around with this new ROM & see how cool it actually is!!!!!!!! THANKS TO EVERYBODY THAT HAS CONTRIBUTED IN ANY WAY TO MAKING THIS MOMENT HAPPEN :)
 
:rock:

I've found that it takes a bit of reading and research before I am willing to try something new. I like to run through what-if scenarios and try to ask questions about stuff that may happen in the future before I begin something.

About the only thing left for you to do that could brick your phone is to change your bootloader. But PLEASE do NOT do this right now. Give yourself some time to enjoy Mobster HD before you change bootloaders.

The only reason to change bootloaders is to run some of the ROMs that don't support your current bootloader which I assume is 1.57 Juopunutbear. I am on 1.50 Juopunutbear which will run almost any ROM for the EVO V. It doesn't run the stock ROM, or JMZ, but that's about it.

Again, read a lot and research before you decide to go down the path of changing your bootloader. You don't need it for a lot of the ROMs, but if you ever want to try a Jellybean ROM, I think you may have to unless there are some that will run off 1.57. The method I recommend is using SDK-Tools rather than flashing from recovery as that requires you to remove the battery, and SD card after the initial flash...then you gotta erase a file on the SD, then insert it again, and go from there. If you do it with your PC, it's very easy. Again, research this until you KNOW WHAT you are doing. Do not jump into it.

Mobster HD is my go to ROM, and I haven't found another one compelling enough for me to switch. That being said, I have only scratched the surface...I've tried maybe 6 or 7 ROMs for this phone...and I keep coming back to Mobster HD.
 
Yes we were all noobs once. The problem that I have with a few newbies is that some don't bother to even read or appreciate people. In other words they don't help them self and act like screaming babies. That's the only thing that annoys me.

Congrats. :D
 
wait how did you fix it ? im in it right now please help[/QUOTE

ROM / Data Recovery:

There are three ways to recover your ROM. Try each one in until you succeed:

Open the cmd prompt that is located in your ControlBear folder where you unzipped all of the files. Type the following cmds into the cmd prompt.

1. ControlBear -r (This is run with the phone at the JuopunutBear/Arrow screen) If this succeeds recovery is complete otherwise continue to Step 2.

2. ControlBear -f (This is run with the phone at the fastboot screen). If this succeeds you're done otherwise continue to Step 3.

3. fastboot flash boot boot_backup.img

4. fastboot flash recovery recovery_backup.img (This is done with the phone in fastboot mode) If this succeeds continue to Step 5.

5. Boot the phone to android and install busybox from the market if not already installed.

6. adb push sdcard.img /data/local/tmp/

7. adb shell

8. $ su

9. # busybox dd if=/data/local/tmp/sdcard.img of=/dev/block/mmcblk1 conv=notrunc

10. Reboot the phone.
 
Do you know what bothers me about some noobs? When they are guided step by step with a problem and they make it seem more complicated than what it really is. That comes from not paying attention.

I also agree that it pays to read and do your research to know what you're getting yourself into. Nobody wants a brick in their hands that they paid so much money for.

BTW, congratulations to the OP for getting S-OFF. You've just opened up a lot more possibilities for your phone. :)
 
Ah, but I see it as the best way to learn is asking questions. The steps for laid out for one may not make sense for another. I'd rather have someone stop when they are uncomfortable and ask a question, no matter how clear the instructions, and get a different explanation of the next step, than try and help them fix a brick, no.;)
 
it said found device...Please wait, then couple of minutes later it said ,Device should be in normal boot mode now , it say press enter to exit what do i do ?
 
Ah, but I see it as the best way to learn is asking questions. The steps for laid out for one may not make sense for another. I'd rather have someone stop when they are uncomfortable and ask a question, no matter how clear the instructions, and get a different explanation of the next step, than try and help them fix a brick, no.;)

Yeah you got a point. I just find it frustrating when a noob goes off on their own to find their own "solution" when you can't explain it anymore clearly to them.
 
it said found device...Please wait, then couple of minutes later it said ,Device should be in normal boot mode now , it say press enter to exit what do i do ?
It's good that the device was found.

Did you get requests for superuser access on the screen and respond to them?

ramjet73
 
Yeah you got a point. I just find it frustrating when a noob goes off on their own to find their own "solution" when you can't explain it anymore clearly to them.

Clearly to one new member may not be so clear to another. I lurked here for 18 months, I had one post until January of last year (you can look it up). I rooted and rom'd my OG Droid a thousand times and managed to do the same with my D2. All that was done by reading, so I see your point. That's me and you.

Others aren't like that, sometimes the solution to the particular question they have is in the 487th post in a thread and they are crosseyed by the time they make it that far into the thread. This place is nice in that we help folks one way or another.
 
Clearly to one new member may not be so clear to another. I lurked here for 18 months, I had one post until January of last year (you can look it up). I rooted and rom'd my OG Droid a thousand times and managed to do the same with my D2. All that was done by reading, so I see your point. That's me and you.

Others aren't like that, sometimes the solution to the particular question they have is in the 487th post in a thread and they are crosseyed by the time they make it that far into the thread. This place is nice in that we help folks one way or another.

Well, that's one of the main reasons why I stick around this place. Wouldn't change it for the world. :)
 
it said found device...Please wait, then couple of minutes later it said ,Device should be in normal boot mode now , it say press enter to exit what do i do ?
Are you still with us?

It would really help to know exactly where you are in the wire trick procedure and whether or not you have responded to the superuser prompts.

ramjet73
 
Since it's been over two hours now and there is still no status update, I'll mention for the benefit of new users a few rules to follow if you need help:

1. Don't create or post in multiple threads for the same problem.

2. If you are given advice or instructions follow them exactly and ask for clarification if you don't understand them.

3. After requesting urgent assistance don't disappear while other users are trying to help you. If you need to do something else and come back later, just say that before leaving.

We are here to support you but need some help from you too.

ramjet73
 
im so sorry for not replying but its because i went desperate and had to get my mind off things to think better ... so what i tryed was to linux since my windows 7 is 64 bit, but it didn't work because my processor doesn't support pae... now i'm restoring nandroid backups.

will update when the nandroid is done.
 
nandroid restore was successful, and an original boot image was restored so he is back to the pre s-off stage of the game now. Without a processor that supports PAE he's not in luck on the current Ubuntu or Mint, and his only option is to use a 32-bit copy of Windows 7 "at a friend's house".
 
nandroid restore was successful, and an original boot image was restored so he is back to the pre s-off stage of the game now. Without a processor that supports PAE he's not in luck on the current Ubuntu or Mint, and his only option is to use a 32-bit copy of Windows 7 "at a friend's house".
Sounds like you were helping him in PM, and will continue to do so until his issues are resolved?

ramjet73
 
I used my girlfriends Windows 7 64-bit to S-Off my phone. The bit doesn't matter for this procedure honestly. It's correct driver setups, and whether or not you are unlocked and on the actual stock ROM. It works better if you just use your original unrooted ROM, and flash a Superuser.zip. this is the one I used and I confirm that it worked perfectly fine. After you flash it with recovery you should be rooted on your actual stock ROM not a downloaded stock ROM. http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip

I also didn't use a wire. I used a small paper clip that has the colored rubber around it. I spent 3 hours with the wire and it failed Everytime. When I used the rubber paperclip it worked on my 3rd try of running controlbear.
 
Sounds like you were helping him in PM, and will continue to do so until his issues are resolved?

ramjet73

Yes sir... sorry for the late reply, I crashed out after I submitted my last message in this thread.

The best policy is definitely to follow the prerequisites given by the developer. If you don't do that, you're essentially treading into uncharted waters, and no guarantees are made to you at that point.
 
Back
Top Bottom