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

Root [HOW-TO] Simplified Root + Recovery + Custom ROM

I am stuck at step 7 under Flash Custom Rom. When I try I end up with a blue screen with "Fastboot mode started udc_start()" and then nothing. I can pull the battery and boot into my existing stock system but am unable to proceed with the custom ROM.

Any help would be greatly appreciated!


Edit: Got it, please ignore the above post. :)
 
Okay, so since my last post, I downloaded Gingerbreak, and after a few days, I rooted it successfully--thanks, guys! Haven't done much since then, though. Here's my question--I see where I'm supposed to download Busybox from the market and run it. Is this necessary if Titanium Backup already has Busybox? I can see Busybox with TiBac open, and there's a green check by it, but do I need a version outside of TiBac? Sorry if I get annoying, but I really want to get this stuff right. Can't wait to get this bloatware off of my phone, sick of endless updates! I also want more available storage. I guess Link2SD would be next, yes? Thanks for any help.
 
Titanium has a busy box built in, but other apps can't use it. If you install it from the market, it will be available system wide. You'll find that you need that for other apps.

And, link2sd would be a good next step. That way you'll have plenty of room for the other apps you wind up installing along the way.
 
A lot new users are running into this problem right now, AndyOpie150 and I have noticed. Are you comfortable with typing in commands? We're working on a workaround/fix, but it may have you playing in the terminal emulator.
 
thanks so much for this guide.. I think there's a few details that could be added for complete dummies like me, but overall it got me through the process smoothly.

the phone is so much more usable now.
 
brotherswing said:
A lot new users are running into this problem right now, AndyOpie150 and I have noticed. Are you comfortable with typing in commands? We're working on a workaround/fix, but it may have you playing in the terminal emulator.
Click to expand...

sounds like a linux shell script might be the way to go.
could be run with terminal, gscript, or sl4a.
 
bigsupersquid said:
sounds like a linux shell script might be the way to go.
could be run with terminal, gscript, or sl4a.
Click to expand...
Damn good idea! You feel like writing it, or shall I? My scripting skills are more than a little rusty, but I'm wiz with research, so I'm sure I could come up with something usable. Eventually....
 
heh, you do it :D since you asked.
need any info, let me know.
one useful bit:
android shell scripts should start with the line (i believe)
Code: 
#!/system/bin/sh
so the terminal or whatever can identify what to run em with.
 
Good to know (I probably would have nerfed that, I default to bash.) I'll get started on it tonight, but like I said I haven't written scripts in more years than I care to admit. It will take a little while between having to look up things in my old text books, and the wife's doctor appointments, but I should have something workable in a few days. When I'm done, would you be so kind as double check my work, Squid?

Edit:: Either I'm more out of it than I thought, or it was much easier than I thought. I'm reinstalling the Android SDK right now to test, I really don't want to test this on my phone! Could it possibly be as simple as five lines of code!? Or does it sound like I'm way off base here?
 
brotherswing said:
What refinements do you suggest? More input and feedback will only make it better.
Click to expand...

4. Download and copy the recovery image VM670NH_recovery.img (works with new & old OV screens) onto your /sdcard.
Click to expand...

I had some trouble figuring out what to do with this.. I think it needed to be flashed or something.. There was also something about "bumblebox" or whatever that I think was edited out, but I had trouble figuring out what to do with that.

9. Wipe Data/Factory Reset, wipe cache partition, & under Advanced Settings, Wipe dalvik-cache, then format all partitions EXCEPT /sdcard.
Click to expand...

And I think I had just had trouble finding where "format partitions" was located.. I think most of this can be figured out with simple intuition though.
 
singbluesilver said:
I downloaded BusyBox from the market, but it won't install. I tried 1.19.3 and 1.19.2, but each fail. Any help is appreciated, thanks.
Click to expand...

brotherswing said:
A lot new users are running into this problem right now, AndyOpie150 and I have noticed. Are you comfortable with typing in commands? We're working on a workaround/fix, but it may have you playing in the terminal emulator.
Click to expand...

Idun Box said:
I had some trouble figuring out what to do with this.. I think it needed to be flashed or something.. There was also something about "bumblebox" or whatever that I think was edited out, but I had trouble figuring out what to do with that.
Click to expand...

I removed the step that requires installing busybox since I updated the link to Flash Image GUI app, which is the app that uses the .img file from the step before.

And I think I had just had trouble finding where "format partitions" was located.. I think most of this can be figured out with simple intuition though.
Click to expand...

I updated OP to make this clearer, it's under Advanced menu.
 
That's good news for all new rooters!

Edit:: Good news for me too, my script wasn't quite...well, it didn't work. Never found my old text books, (I think my ex-wife did something with them.) Had to try from memory, and I haven't done anything like that in eight years. I may get back into it though, it's tickling parts of my brain long dormant! ;)
 
Hey Whyzor, I have a question. If the flash_image GUI allows you to flash the recovery, then you don't need Busybox. Right?
By not having Busybox installed what can't you do/change? This is my question.
 
without busybox, shell commands default to toolbox.
wimpy, commands barely there, horrid permissions... won't cp across partition boundaries... ugh.
busybox is like mini-Linux at the command line. you can actually build a working Linux install in a reasonable amount of space (MB instead of GB) with busybox replacing most of /bin.
 
AndyOpie150 said:
Hey Whyzor, I have a question. If the flash_image GUI allows you to flash the recovery, then you don't need Busybox. Right?
By not having Busybox installed what can't you do/change? This is my question.
Click to expand...

I'm trying to keep this guide easy & simple for the beginner, since busybox isn't required to flash another ROM anymore, I removed it. CM7 based ROMs have it installed anyway (may not be the latest bleeding edge release), but I never really had to install busybox separately.
 
Whyzor said:
I'm trying to keep this guide easy & simple for the beginner, since busybox isn't required to flash another ROM anymore, I removed it. CM7 based ROMs have it installed anyway (may not be the latest bleeding edge release), but I never really had to install busybox separately.
Click to expand...
yeah, really, installing busybox is only neccesary if you want to stick with your stock rom but amp up the scripting/terminal functionality. You can get around a lot of the toolbox limitations if you go more old-school with your commands (like cat /path/to/source.file > /path/to/destination.file instead of cp)
I've noticed that even with busybox installed, stock-based roms seem to be less responsive in the terminal than the cm-based roms.
 
Ok, so if the CM-7 based ROM's have it installed then when someone has problems with getting Busybox installed, and wants CM-7 installed, then I can just have them try the flash_image GUI app.
They wont be missing anything if later they want to make some changes to the ROM. Right?
 
You must log in or register to reply here.
Back
Top Bottom