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

Root Installed KaosGingerbread V6 ROM, BAD IDEA!!!

I just did what scotty suggested. I formatted my phone to FAT32, renamed the file exactly how it said. I loaded my phone in HBoot and i got a blue progress bar on the top right. It did a few things then brought up a screen that says Main Version is Older! Update Fail! Do you want to reboot device?
 
slikrider20 said:
This in bold. However my screen doesn't have all that stuff that the screenshot before Scenario 4 does. It simply just says stderr: Permission denied. SU box is checked.
Click to expand...

Yeah, I'm a little puzzled...sounds like you have a custom (rooted?) ROM without the su program and/or the SuperUser whitelist app.

Can you use Astro File Manager and navigate to the /system/bin directory to look for the su program? You can also check in the /system/app directory for the SuperUser.apk. This should give us a little more information about your current root status.

You might be able to use Z4root ([APP] z4root - xda-developers) if you can grab the .apk file from XDA and run it, you should be able to give yourself temporary root (I think I've tried temporary and permanent on my Eris and only temporary worked). If you do try this, be sure to do it after a fresh reboot--it seems to help.

After you get temporary root, it should install the su program, the SuperUser whitelist app, busybox, etc. This should allow you to re-run the Gscript Lite script (this is assuming that your problems stems from the lack of the root programs).

Good luck!
 
scary alien said:
Yeah, I'm a little puzzled...sounds like you have a custom (rooted?) ROM without the su program and/or the SuperUser whitelist app.

Can you use Astro File Manager and navigate to the /system/bin directory to look for the su program? You can also check in the /system/app directory for the SuperUser.apk. This should give us a little more information about your current root status.

You might be able to use Z4root ([APP] z4root - xda-developers) if you can grab the .apk file from XDA and run it, you should be able to give yourself temporary root (I think I've tried temporary and permanent on my Eris and only temporary worked). If you do try this, be sure to do it after a fresh reboot--it seems to help.

After you get temporary root, it should install the su program, the SuperUser whitelist app, busybox, etc. This should allow you to re-run the Gscript Lite script (this is assuming that your problems stems from the lack of the root programs).

Good luck!
Click to expand...

THIS WORKED! Holy shit i had Superuser.apk but it wasn't installed. As soon as i installed this, all of my programs which weren't responding now work!
 
I really appreciate the help guys. I feel kinda stupid now, everything always seems obvious AFTER you figure it out. Now i'm going to flash GSB and hope i don't screw up anything again :)
 
slikrider20 said:
I really appreciate the help guys. I feel kinda stupid now, everything always seems obvious AFTER you figure it out. Now i'm going to flash GSB and hope i don't screw up anything again :)
Click to expand...

Glad to see it's worked out. Remember that GSB also requires that you download and flash a google apps package after you flash GSB and before you restart the ROM (though it shouldn't give you as much trouble as this did.)

I am sorely tempted to throw up a thread warning new rooters not to install KGB. Or KF at this point, either. I think that the Kaos name is well known enough that people find it on searches, but these are clearly not being maintained well by punk.kaos at this point.
 
Looks like one of those "Big Dogs" pulled you thru.:D Congrats!! Let us know how GSB works for you. Remember to flash Gapps after flashing GSB and before rebooting.:)
 
Just one more problem. My dumbass set SETCPU too high and enabled the check box for set on reboot. Now it crashes everytime before i can access Setcpu. Keep in mind my recovery doesn't work. Wow, i am an idiot.

Edit: Saved myself by making a profile With 710 as the max plugged in :)))))))
 
I'm sorry my idea dint pan out. I thot I had flashed it overtop of kaos froyo once,so I'm not really sure wat hat main vesrion error means. :confused:

At any rate,I'm glad Mr scary had the answer for you(he usually does :D)

Doogald,I think a warning thread is an excellent idea. He isn't the first person to get stuck in KGB :eek:

If someone knows kaos,maybe even politely ask that he put a warning thread up on the 1st post in the KGB thread.

Whenever I look at a rom, I always look to see wen it was last updated. Then ill skim thru the last couple pages of replies to see what he current issues are :)
 
slikrider20 said:
Just one more problem. My dumbass set SETCPU too high and enabled the check box for set on reboot. Now it crashes everytime before i can access Setcpu. Keep in mind my recovery doesn't work. Wow, i am an idiot.

Edit: Saved myself by making a profile With 710 as the max plugged in :)))))))
Click to expand...

Do yourself a favor and make a Nandroid backup of what you have right now. This way you'll have something to go back to easily from Recovery if anything goes bad.
 
slikrider20 said:
Just one more problem. My dumbass set SETCPU too high and enabled the check box for set on reboot. Now it crashes everytime before i can access Setcpu. Keep in mind my recovery doesn't work. Wow, i am an idiot.

Edit: Saved myself by making a profile With 710 as the max plugged in :)))))))
Click to expand...

Might I suggest now that you're in a functioning rom that getting the tracball optional recovery working be one of the first orders of business ;) :D
 
scotty85 said:
Might I suggest now that you're in a functioning rom that getting the tracball optional recovery working be one of the first orders of business ;) :D
Click to expand...

For sure. I flashed the Clockwork Mod Recovery and my tracball works in this recovery. Is there any disadvantage to having this recovery as opposed to Amons?
 
slikrider20 said:
For sure. I flashed the Clockwork Mod Recovery and my tracball works in this recovery. Is there any disadvantage to having this recovery as opposed to Amons?
Click to expand...

Well, there have been reports of phones that were bricked or near-bricked (resurrected by erisuser1 / bftb0) with virtually all of them having ClockworkMod used on them, usually by novice users.

Its unclear as to what behavior or sequence of events that transpired that led up to or precipitated the brickings. It seems that there is something that led to memory pages being marked as bad which ultimately led to the inability to successfully flash or boot subsequent ROMs.

There are many folks that successfully use ClockworkMod on the Eris and have not reported brickings, but these seem to be users that know the proper sequence of events for loading / wiping / flashing a new ROM and are careful and diligent about making sure they have a full charge on their phones, etc. when doing recovery-related activities.

Your mileage may vary (:D) of course, but that's the "word on the street" re. CWM.

Cheers!
 
i personally would not use clockwork or rom manager(:eek:) lots of people may in fact use both,with no issue,but being active,here,on the d1,the inc,and now the thunderbolt forum,i see alot of scenarios like yours where the use of rom manager has led to disaster.

my advice would be to not use either. at the very least,id strongly reccomend getting the tracball optional recovery working,and becoming comfortable using it. then keep a couple nand backups from it,and a rom that you could flash in an emergency.

once youre comfortable with Amon_Ra,if you still feel the need to use rom manager or clockwork,go ahead. but at least youll have the tools and knowledge to fix a resulting bootloop or a semi-functioning rom with no rom manager and no market :)
 
scotty85 said:
i personally would not use clockwork or rom manager(:eek:) lots of people may in fact use both,with no issue,but being active,here,on the d1,the inc,and now the thunderbolt forum,i see alot of scenarios like yours where the use of rom manager has led to disaster.

my advice would be to not use either. at the very least,id strongly reccomend getting the tracball optional recovery working,and becoming comfortable using it. then keep a couple nand backups from it,and a rom that you could flash in an emergency.

once youre comfortable with Amon_Ra,if you still feel the need to use rom manager or clockwork,go ahead. but at least youll have the tools and knowledge to fix a resulting bootloop or a semi-functioning rom with no rom manager and no market :)
Click to expand...

I just did the Optional Tracball script thing and now my recovery works. I can now scroll down using the Send button....Genious.... Doing a Nandroid Backup now. Wow i never thought i would figure this stuff out. Thanks again for the help anyone who posted anything.
 
You must log in or register to reply here.
Back
Top Bottom