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

Root [ROM] Deck's ReLoaded | LOTK | Ver 500 RLS

Mikestony said:
Well, the only terminal emulator that I have is the one included in the rom.
I type su and I get nothing
Right now I'm in recovery....didnt do anything yet ...sitting at recovery.

Edit: the only good thing I got going for me is I made a nandroid backup before I did this
Click to expand...

That's odd. If you have super user and terminal emulator on your app list then that should work.
 
MizzouBrent said:
That's odd. If you have super user and terminal emulator on your app list then that should work.
Click to expand...
I know right? Let me nand back to my backup....
When I originally flashed this rom, I noticed, after I restored my user apps (no data, just apps) I had 2 Terminal Emulators...one worked , one didnt
 
O.k...while in recovery, instead of going back to a nand, I decided to fix uid permissions....did that and rebooted
got back apps so far, went into terminal emulator...typed su, the a2sd repair...at the bottom is says
WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.
Do you want to continue? y/n
 
Mikestony said:
O.k...while in recovery, instead of going back to a nand, I decided to fix uid permissions....did that and rebooted
got back apps so far, went into terminal emulator...typed su, the a2sd repair...at the bottom is says
WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.
Do you want to continue? y/n
Click to expand...

Wow I have no clue what that means.
 
Mikestony said:
Well, the only terminal emulator that I have is the one included in the rom.
I type su and I get nothing
Right now I'm in recovery....didnt do anything yet ...sitting at recovery.

Edit: the only good thing I got going for me is I made a nandroid backup before I did this
Click to expand...

It happens with larger sd cards with some. It's a known issued with dta2sd not picking up the mount in time. It doesn't happen if you don't transfer the cache over to the sdext partition. Also are you using the firerat mod in conjunction? If so they both mount the/system partition and conflict with each other. This isn't a rom issue. Finally it sounds like you lost your su which would happen in reboot if you changed your system busy box to 1.18-4. A2sd works properly with reloaded such that it is. Move your cache back to the internal first.
su
a2sd nochache

Then

su (enter)
a2sd repair
a2sd reinstall

If you can't do this then your mount can't be reestablished because you changed your system busybox to 1.18-4.

If you can't achieve su or if you can't remount you're ext partition in order to run a repair/reinstall then flash vipermod which will force busybox 1.16 back on your phone. Reboot and see if you can get su back. If not go back to recovery and install su. If you insist on running it from the sd which I do, I have a workaround that achieves both without breaking your mount.

ropodope
 
Mikestony said:
O.k...while in recovery, instead of going back to a nand, I decided to fix uid permissions....did that and rebooted
got back apps so far, went into terminal emulator...typed su, the a2sd repair...at the bottom is says
WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.
Do you want to continue? y/n
Click to expand...
is your sdcard usb mounted right.now?

ropodope
 
ropodope said:
http://db.tt/aq8pzT4j

ropodope
Click to expand...
Thanks, flashed vipermod..while I'm waiting for it to boot up, do I need to start over in TE with the su, a2sdnocache, blah blah blah....or do I need to run vipermod somehow?

###!!! Ran in TE
su
a2sd nocache
Gave me that big warning and severe file damage message....
ok., I thought...ran a2sd repair.....brief message at bottom about couldnt mount system and phone rebooted before I could read it.
I KNOW I have bb 1.16...checked it with busybox installer pro.

Edit: I see you're having other issues over at xda....sorry about my issue here...
I'll nand back or I will reflash the rom....no biggie...Thanks for your help
 
o.k. all..update (if you've been following my issue)
1--nandroids are a root users BEST friend.
2. I really dont know the cause of all this but I surmise it was because when I originally flashed this rom I upgraded busybox to 1.20...and that was before I knew I shouldn't have but I was not having any issues until I ran the a2sd cachesd....
3. Wierd stuff happened, tried to fix it, (BIG sorry to ropodope for not following the install instructions, namely the busybox thing), and couldn't fix it. He's not an "a2sd tech support to the world". So, again, Sorry sorry rope.
4. I really love this rom, I will not go back to sense in foreseeable future.
I will gladly flash his next update to a "T".
5. Thank you Mizzou for helping me and your advise.
6. I will not touch or try to move cache/dalvik to sd again, nor will I attempt to upgrade my ext 3 to ext 4....and why should I? The rom is perfect for me (even tho I have bb 1.20....who knows...I will leave it be until next update.

THANK YOU ROPE AND MIZZOU
G'nite ladies and gentlemen, thank you for coming:D
 
Mikestony said:
Thanks, flashed vipermod..while I'm waiting for it to boot up, do I need to start over in TE with the su, a2sdnocache, blah blah blah....or do I need to run vipermod somehow?

F###!!! Ran in TE
su
a2sd nocache
Gave me that big warning and severe file damage message....
ok., I thought...ran a2sd repair.....brief message at bottom about couldnt mount system and phone rebooted before I could read it.
I KNOW I have bb 1.16...checked it with busybox installer pro.

Edit: I see you're having other issues over at xda....sorry about my issue here...
I'll nand back or I will reflash the rom....no biggie...Thanks for your help
Click to expand...
his issue was unique to a2sd running with firerat mod which he fixed.

ropodope
 
Mikestony said:
o.k. all..update (if you've been following my issue)
1--nandroids are a root users BEST friend.
2. I really dont know the cause of all this but I surmise it was because when I originally flashed this rom I upgraded busybox to 1.20...and that was before I knew I shouldn't have but I was not having any issues until I ran the a2sd cachesd....
3. Wierd stuff happened, tried to fix it, (BIG sorry to ropodope for not following the install instructions, namely the busybox thing), and couldn't fix it. He's not an "a2sd tech support to the world". So, again, Sorry sorry rope.
4. I really love this rom, I will not go back to sense in foreseeable future.
I will gladly flash his next update to a "T".
5. Thank you Mizzou for helping me and your advise.
6. I will not touch or try to move cache/dalvik to sd again, nor will I attempt to upgrade my ext 3 to ext 4....and why should I? The rom is perfect for me (even tho I have bb 1.20....who knows...I will leave it be until next update.

THANK YOU ROPE AND MIZZOU
G'nite ladies and gentlemen, thank you for coming:D
Click to expand...
cool, now pm me and I can show you how to move the dalvik without breaking mount. And upgrading from ext 3 to ext 4 is effortless.

ropodope
 
I have ext. 4 and data and dalvik on SD, should I have done something special because sometimes it seems like my phone iant reading data for certain things and my Baltic feedback comes in and out.
 
brianvillage5 said:
I have ext. 4 and data and dalvik on SD, should I have done something special because sometimes it seems like my phone iant reading data for certain things and my Baltic feedback comes in and out.
Click to expand...
That's what I was shooting for....ext 4 and dalvik on sd but I fudged it up somehow....I don't know if you should do anything special.....I'll find out...
 
Right on thanks, I just realized haptic was turned off for some reason, and I did a2sd repair. All seems good here, I run every option I can from my SD partition. I did nothing different Coming off cm7.
 
You must log in or register to reply here.
Back
Top Bottom