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

Root Trouble Installing New Rom

L

LittleRedDot

Android Enthusiast
Ok I was running Deck 1.3 stable and heard that the beta "d" version was actually better, and since I'm a flashaholic I decided to flash it. So I did my back up of apps, and a nandroid, wiped thoroughly.... Installed the new rom, then gapps, then kernel (tiamat 3.3.7).... Went to reboot and got stuck at splash screen.... Pulled the battery and went into hboot, then recovery, wiped dalvik & cache and rebooted.... Got past splash but stuck on boot screen...

So I restored the nand, deleted everything I downloaded, re-downloaded everything, and repeated the process with the exact same results.

Any suggestions?
 
I am trying out a Deck rom, Liking it too.

I did like you the other day and had the same problem.

I re wiped thoroughly and then just flashed the rom and gapps and booted. then I went back and flashed the kernel after I had it set up.

Been working perfectly since then. don't know if that will help you but you can try it.
 
LittlrRedDot said:
Ok I was running Deck 1.3 stable and heard that the beta "d" version was actually better, and since I'm a flashaholic I decided to flash it. So I did my back up of apps, and a nandroid, wiped thoroughly.... Installed the new rom, then gapps, then kernel (tiamat 3.3.7).... Went to reboot and got stuck at splash screen.... Pulled the battery and went into hboot, then recovery, wiped dalvik & cache and rebooted.... Got past splash but stuck on boot screen...

So I restored the nand, deleted everything I downloaded, re-downloaded everything, and repeated the process with the exact same results.

Any suggestions?
Click to expand...

Odd. Never had that problem
 
My "issue" was almost similar I didn't realize I needed to flash dt before reinstalling my apps got low disk space and when into recovery wiped cache and dalvic rebooted and the Setup Wizard was there again Asking me if I had a google account. I rebooted and wiped again reboot same thing I skipped out of it. And phone was a big laggish until I was able to get terminal open and type the a2sd install command. Now that progs are on ext, It's working fine. I'm going to flash tiamat 3.3.7 maybe tomorrow I generally want to give the ROM time to settle.

actually didnt state the start right. I didnt realize that dt was not baked in. or if it is hmmmm anyway it seems to be fine now.
 
Ok I encountered another issue.... I can install the rom and gapps with no issue, and restore via TB with no issue. From there I have a smooth sailing rom ready to go. But as soon as I flash the kernel (Tiamat 3.3.7) it's like when I first installed the rom, no restore from TB. Ok so I open my app drawer, TB is gone. So I click on the market, and it tells me that it's not installed on my phone. So I wiped and nand back to Deck 1.3 stable... That was last night. This morning I started athe whole process again. Same results after flashing ROM and gapps. So I tried flashing kernel and DT, but now I'm back to no TB recovery done and market not installed.

What's going wrong here?

Oh and I wiped dalvik and cache before tring to flash kernel or DT.
 
I have not had that problem. Here are my thoughts though. l didn't need to flash dt or run any commands with this version of 1.3. It just did everything itself. Are you sure you have to? Look at it in TB before you do or flash kernel. Got the a2sd line there? If so, don't flash dt.
are you sure your kernel dl is good?
 
LittlrRedDot said:
Ok I was running Deck 1.3 stable and heard that the beta "d" version was actually better, and since I'm a flashaholic I decided to flash it. So I did my back up of apps, and a nandroid, wiped thoroughly.... Installed the new rom, then gapps, then kernel (tiamat 3.3.7).... Went to reboot and got stuck at splash screen.... Pulled the battery and went into hboot, then recovery, wiped dalvik & cache and rebooted.... Got past splash but stuck on boot screen...

So I restored the nand, deleted everything I downloaded, re-downloaded everything, and repeated the process with the exact same results.

Any suggestions?
Click to expand...

I'm running 1.3 now. This hasn't happened to me. One thing I did notice was that after you freshly installed the rom you didn't reboot your phone before installing the kernel. I was told that was a no no some time ago. After a fresh install, reboot to where you can use the phone, then go back to recovery and install the kernel
 
MusicJunkie said:
I'm running 1.3 now. This hasn't happened to me. One thing I did notice was that after you freshly installed the rom you didn't reboot your phone before installing the kernel. I was told that was a no no some time ago. After a fresh install, reboot to where you can use the phone, then go back to recovery and install the kernel
Click to expand...

Thats more for troubleshooting purposes than anything. NOT rebooting in between flashing your ROM and kernel wont cause problems. It just allows you to narrow it down to either the ROM or the kernel in case you have problems.


I always flash in the same recovery session unless theres issues. If there are any, I go back and reboot in between to see which one caused the problem.
 
Rxpert83 said:
Thats more for troubleshooting purposes than anything. NOT rebooting in between flashing your ROM and kernel wont cause problems. It just allows you to narrow it down to either the ROM or the kernel in case you have problems.


I always flash in the same recovery session unless theres issues. If there are any, I go back and reboot in between to see which one caused the problem.
Click to expand...

So accoding to your logic I've narrowed it down to the kernel...and since I'm using the same kernel on the stable build I know the download is good. I'm gonna try flashing a different version of tiamat when I get home tonight.

Also something else I noticed this morning was that its not letting me flash a known good band of mik3.0. I install the nand and it's like flashing the Tom with no customization, so I hit the home button to switch launchers and nothing is installed. Never had any of these issues before.
 
Almost sounds like you didn't check to backup sd extension when ever you backed up or restored.
Which recovery are you using? Could it be corrupt? I guess the partition could be hosed. Argedion could tell you how to check it.
Hope you get it straight soon. Let us know! Good hunting.
 
LittlrRedDot said:
Ok I encountered another issue.... I can install the rom and gapps with no issue, and restore via TB with no issue. From there I have a smooth sailing rom ready to go. But as soon as I flash the kernel (Tiamat 3.3.7) it's like when I first installed the rom, no restore from TB. Ok so I open my app drawer, TB is gone. So I click on the market, and it tells me that it's not installed on my phone. So I wiped and nand back to Deck 1.3 stable... That was last night. This morning I started athe whole process again. Same results after flashing ROM and gapps. So I tried flashing kernel and DT, but now I'm back to no TB recovery done and market not installed.

What's going wrong here?

Oh and I wiped dalvik and cache before tring to flash kernel or DT.
Click to expand...
If you're seeing an issue with an app disappearing after you know it's installed, I would go into terminal and type

su
a2sd reinstall

and let it do its thing. Also, which DTa2sd script did you flash? I have seen issues at times with the Beta 04 version. Just use the stable one if you have problems. It's ok to flash the stable version if you have already flashed the beta version. The a2sd reinstall command has helped me a couple different times.

I flashed the updated CM7 nightly build that has been compiled and posted on XDA and noticed titanium disappeared on me as well. ran the reinstall command and poof, everything is back.
 
dustwun77 said:
Almost sounds like you didn't check to backup sd extension when ever you backed up or restored.
Which recovery are you using? Could it be corrupt? I guess the partition could be hosed. Argedion could tell you how to check it.
Hope you get it straight soon. Let us know! Good hunting.
Click to expand...

If its a known good nand then everything should have been fine. It is possible the partition has gotten corrupted but I not thinking that is the issue. Try out Mizzou's suggestion first and it if gives your partition errors then we can progress from there. Best to leave the partition alone unless we have to mess with it. When you get a chance backup your sdcard to your computer.
 
argedion said:
If its a known good nand then everything should have been fine. It is possible the partition has gotten corrupted but I not thinking that is the issue. Try out Mizzou's suggestion first and it if gives your partition errors then we can progress from there. Best to leave the partition alone unless we have to mess with it. When you get a chance backup your sdcard to your computer.
Click to expand...

In the Amon Ra Style recovery, which I have now, you have to check what you want to restore, you can omit stuff. That is why I asked what recovery he has.

Still seems like a possibility to me. Awaiting his answer.
 
dustwun77 said:
In the Amon Ra Style recovery, which I have now, you have to check what you want to restore, you can omit stuff. That is why I asked what recovery he has.

Still seems like a possibility to me. Awaiting his answer.
Click to expand...

Yes Its still a possibility however the kernel and rom were on the same partition the apps are stored in the ext partition yes but if there was a problem with that partition he shouldn't have any apps coming up and notice so very serious lag on the phone. and more than likely some serious FC'ing going on.

Yes I have amon ra syle 3.11 on and I know what you mean I have to always make sure I have it checked.
 
Haha I know how frustrating it is when you give out all this advice and the OP up and disappears and never tells you how it worked out!

Ok the known good nand DID work once I remembered to check the sd ext, but I still havent got deck1.3d to work right, gonna try again right now.
 
Ok I flashed the ROM, gapps, kernel, then DT... It went into boot loop for a few cycles then finally loaded... I went through the setup, then it shut off and botlooped for a few more cycles...then it booted, I went through setup again and made it to my home screen...

Then I hit the market and dl'd TB, but when I opened it it said I wasn't rooted and didn't have busy box... so I dl'd BB and installed v1.8.2 and re-opened TB... Still said I wasn't rooted, so I rebooted in recovery and fixed permission and wiped dalvik and cache... Now I got TB to recognize root and am running the batch restore.

Will keep you posted...
 
LittlrRedDot said:
Haha I know how frustrating it is when you give out all this advice and the OP up and disappears and never tells you how it worked out!

Ok the known good nand DID work once I remembered to check the sd ext, but I still havent got deck1.3d to work right, gonna try again right now.
Click to expand...



Yeah, almost as if he had a life or something. Lol.
Glad that part worked out.
I am on that very same rom. I did not have to flash any stripe or flavor of dt to get a2sd to work. It just did it's thing out of the box.
 
I think it is possible. Try without it? Think there is an a2sd repair command. Not sure. Or if it would apply

TB doesn't backup SMS and calendar and contacts should be hooked to your Google account.
 
You must log in or register to reply here.
Back
Top Bottom