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

Root think I am screwed, root went fine then POW

vincentp said:
Usually baseband updates don't require a wipe of any kind though. Because it's not actually modifying the /system, /data or /cache partitions, it should have no effect on the ROM itself whether or not these are wiped. I think something else funny went wrong there, but I have no idea what.
Click to expand...

digdug1 said:
it isn't nessecary to wipe data and cache for flashing basebands or kernals. i do wipe when i flash rom though.
Click to expand...

well it asked and I denied... so that was my 1 guess as it seemed the one thing that finally worked when I accepted that option.

I would love to know just what it was, but I also kind of want to move on. start to consider a 2.2 ROM and some over clocking (advice if any wanted)

I do recall that in that baseband download, it had to download 2 things I recall. I thought that was odd, did not expect it, but it was all fine after I did it and I even rebooted and did *228 and went about my way.

In retrospect, the thing that set this all off was that I went to MyBackup Pro and tried to open it, it asked for SuperUser access - as several other root specific apps did - and I gave it and then it FC. I tried again, FC. Well, then I went to SuperUser and it also FC so I was like WTF. I knew there was a mention in ROM Manager that if apps give issues, use ROM Manager to reset permissions, but then ROM Manger FC like 5 times. So I was like WTF and I just figured I would reboot and try again and that is when the thing stuck in the M screen and this all started.. Maybe someone smarter will read all of this, put it together and know just what happened or it will help someone else out.
 
digdug1 said:
just make sure you keep a back up
Click to expand...

keep a backup of what exactly? the update.zip file or backup my seemingly stable system again with Titanium before I delete update.zip? that update.zip file is available for download here, so not sure why I would keep a backup, not that big of a deal to do so, just curious what you mean.

and when I delete, can I just use Astro to delete it?
 
Backup your apps and data with Titanium. Also make a Nandroid backup in recovery before installing anything else - every time. This way if something goes wrong you should be able to restore the old image.
 
vincentp said:
Backup your apps and data with Titanium. Also make a Nandroid backup in recovery before installing anything else - every time. This way if something goes wrong you should be able to restore the old image.
Click to expand...

okay, I can backup with Titanium. I plan to do this before I make any future changes for sure. for sure as having it was a life saver. Even though I have had the paid MyBackup Pro and I think it does the same thing as it opened new root options once I rooted I did not have before. Any thoughts on it being as good?

But how does 1 make a "Nandroid backup in recovery"? is this reboot holding x and go into backup/restore option and doing a backup there?

you do BOTH of these regularly?
 
Lock-N-Load said:
okay, I can backup with Titanium. I plan to do this before I make any future changes for sure. for sure as having it was a life saver. Even though I have had the paid MyBackup Pro and I think it does the same thing as it opened new root options once I rooted I did not have before. Any thoughts on it being as good?

But how does 1 make a "Nandroid backup in recovery"? is this reboot holding x and go into backup/restore option and doing a backup there?

you do BOTH of these regularly?
Click to expand...


to make a nandrooid backup go to rom manager/backup and restore/backup current rom. this keeps an exact copy of your phone as it is. also what baseband are you currently running and which one did you try before it messed up? there are basebands in rom manager that require you to flash one before you flash another in kind of a progression.

the reason i ask which one you are running is once you flash a basebnd, you keep it until you flash a different one. meaning that you are probably still using the last one you flashed before you had your problem
 
okay.....

yesterday, when I first rooted, I did this backup method in ROM Manager via that cockworkMD - did not know it was called "Nandroid backup" since your in cockworkMD. I kind of have been reading so so things about this cockworkMD - and it might have been part of my issue - so I kind of want to go a different route. Isn't there another option than cockworkMD to make a "Nandroid backup"? I am stable right now, so I kind of want to make one now. As it stands, I do not have cockworkMD installed in ROM Manager right now, should I again as it seems I cannot do anything in ROM Manager without it?

EDIT: I went ahead and installed the clockworkMD as it seems you have no choice if you want to use ROM Manager. I went into the restore/backup and there was my backup from yesterday just after rooting with Easy Root. I kind of want to make one right now as it seems better and stable and just delete that old one. If I make one, then I technically have a ""Nandroid backup" despite it was made using clockworkMD in ROM Manager?

My current baseband is C_01.3E.01P. yesterday before updated I noted I had c_01.36.03p and the one I tried - which did not have a notice that you needed another first, but when I did it it showed 2 things downloading - was "verizon Droid 2.0.1 stock", which I believe you advised me was C_01.3E.01P so in fact, it looks like I do have the one I updated to yesterday as you suspected.
 
you can use the x button to make a back up under nandroid but this still uses clockwork. its just the long way around to get the same thing. i dont know really of another way to make such a backup withoud nandroid. i do think you need to flash clockwork but an older version. this is what i had to do awhile back when i had your exact problem. i flashed a rom that freaked out my phone once. someone here
(chief i think) helped me through it and told me to flash an older version. in fact im still using it now.
 
I understand now about making a nanodroid backup via clockworkMD.. either way, same results is achieved.

I think I also read, amongst the 200 things I read in the last 24 hours, about going to an older clockworkMD version than what is now downloaded... so how do I (1) get the older version and (2) flash it over. I kind of do not want to proceed until I get this clockworkMD issue addressed.

EDIT: I see at the bottom of ROM Manager "flash older and experimental versions of clockworkMD recovery"... is that what you did? do you know what version your using as they show 20 versions :eek:
 
Lock-N-Load said:
I understand now about making a nanodroid backup via clockworkMD.. either way, same results is achieved.

I think I also read, amongst the 200 things I read in the last 24 hours, about going to an older clockworkMD version than what is now downloaded... so how do I (1) get the older version and (2) flash it over. I kind of do not want to proceed until I get this clockworkMD issue addressed.
Click to expand...


i wouldnt either you need clockwork to enjoy rooting. even since i have had to go to older versions to get it to work sometimes usually after it gets updated lol!


Go into ROM Manager and select Flash Alternate Recovery. It will flash SPRecovery for you.

THEN flash the CWMod Recovery again. That shoud fix it. CWMod is VERY finicky!


i copied his exact text from my prior thread. i followed his steps and it fixed my problem. my problem wasnt the theme but my cwmod. i think it fits your situation as well.
 
wait, don't I have SPRecovery already? isn't that what I used RSD Lite to put onto my phone to even get back to where I was? I put on "SPRecovery_ESE81.sbf"... so are we sure I would want to do this? or am I doing this to clear off clockworkMD so I can reinstall it?

also, IF I do this and I understand correctly why your suggesting it, you say "THEN flash the CWMod Recovery again".. but which one? The one it self installs for you or one from the "older and experimental versions of clockworkMD recovery" and if from here, which one?


from the other guy who had the same issue

"Update: If any of you rooted your phone using the Easy Root program from the market or DMupdater (the beta posted at Droid Life) and are having problems with Clockworkmod, you need to reflash SPRecovery console using the tried and true method in all the root guides. You don't have to go all the way through the guide, you just need to get to the point where you use RSD Lite to flash SPRecovery onto the phone. From there, you can then use Rom Manager to flash Clockworkmod back onto the phone and it will "stick" from now on once you have used RSD Lite to flash SPRecovery onto the phone.

I was having an issue where the first time after flashing Clockworkmod using Rom Manager, it would boot just fine into Clockworkmod. Subsequent attempts would bring me back to the exclamation point inside a triangle meaning no Clockworkmod was detected.

Seems to be the only fix for this is to use RSD Lite to flash SPRecovery onto the phone. From there, you can then use Rom Manager as normal."

well it seems I already did the "you need to reflash SPRecovery console using the tried and true method in all the root guides" and thus the clockworkMD I just installled should "stick" (as he said) and I should then "use Rom Manager as normal".

seem like a fair assessment?
 
seems fair to me! but to answer your question, flashing sp recovery just clears cw allowing you to reinstall it. flash cw at the top of rom manager and make a back up. good to know if you have trouble in the future with it because, i used the old method of rooting and still had problems with it.
 
digdug1 said:
seems fair to me! but to answer your question, flashing sp recovery just clears cw allowing you to reinstall it. flash cw at the top of rom manager and make a back up. good to know if you have trouble in the future with it.
Click to expand...

fair enough.... only thing, what does "flash cw at the top of rom manager" mean? you mean use the first one listed in the "flash older and experimental versions of clockworkMD recovery" list? 2.5.0.1? is that what you saying?
 
well after reading your other post about the new way to root and problems with sp recovery, i would flash the newest version of cw. this should get you up and going. but if you have trouble with cw in the future remember the steps i gave you above:)


yes 2.5.0.1 is what i am currently using without any problems. just look at the top of rommanager under recovery and click flash clockworkmod recovery
 
then I have the newest right now.

as you know, you have to install clockworkMD to even really use ROM Manager, and as you recall it just installs one for you and so, I installed that so I could even use RM and will thus assume it is the newest version.
 
quite right, i missed your edit above saying you went ahead and installed cw. you should be good to go! make your nandroid backup. enjoy!
 
wow, well backup failed via ROM Manager!

CWMD v2.5.0.1
rom manager v2.0.1.5

I was watching the screen and it said

no /sdcard/.android_secure_found skipping backup of applications
no sd-exit skipping backup of sd-exit

what the hell?

Google tells me

"The no /sdcard/.android_secure found error is because you do not have the folder .android_secure on your sdcard. This folder is used for App2SD capability in 2.2.

The no sd-ext error is because you don't have the sd-ext partition on your sdcard (also used in App2SD).

Neither is an error really, they are just notifications that those items aren't located on your sdcard."

why are these 2.2 references when I am on 2.1?
 
Go into ROM Manager and select Flash Alternate Recovery. It will flash SPRecovery for you.

THEN flash the CWMod Recovery again. That shoud fix it. CWMod is VERY finicky!

try it
 
I did Flash Alternate Recovery to SPRecovery right into newest CWMod Recovery and no dice, same errors. ugh, this darn thing

yesterday BEFORE all of the issues it worked, now no joy.
 
did it back up anything? check rommanager under back up and restore/ manage and restore backups. mine also says no sd exit apps to sd or something like that. if not try flashing an older version perhaps 2.0.1.3 its the one i had to use once
 
well, on another site I read...

"what will have happened is that you are backing up a system that has no A2SD at all.

.android_secure is Froyo's A2SD, if you are backing up something other than Froyo, e.g. Eclair (perhaps R3 or some rooted native ROM) then there is no .android_secure so it will throw the error
sd-ext is used by A2SD or A2SD+ as is available to put in ROMs such as Paul's via the online kitchen; if you haven't specifically formatted your SD card to allow A2SD then there will be none and so you get this error.

Basically, to interpret, nandroid is trying to back up facilities that might be used, and if your current rom doesn't use them then it just skips it. I.e. you can safely ignore it, in the knowledge that the backup has worked."

so, I used Astro to look into sdcard/clockworkmod/backup and I see the 4 backups I did, 1 yesterday that showed success and 3 today I tried right now. When I go into those, the file size of the 6 files are nearly the same as the one we know worked from yesterday. So, I think this dude might be correct. but what is odd is.. what is some 2.2 froyo specifics doing here?
 
check my post above if its there it worked i get the same error because if this guy is right, i have never formatted my sd card because i am on bbv0.4 and pete has a script to store apps on the sd card without formatting it. i think you are ok
 
Those errors are fine. The recovery does not know what os version you have so it attempts to backup everything. If there is nothing there it skips it. That's all that happened
 
digdug1 said:
check my post above if its there it worked i get the same error because if this guy is right, i have never formatted my sd card because i am on bbv0.4 and pete has a script to store apps on the sd card without formatting it. i think you are ok
Click to expand...

it certainly "seems" it did its thing despite saying it did not. Plus, you see the progress bars come up but with no progress... but the #'s on file sizes kind of implies it did in fact BU.

did you just try it?

still, the more curious thing is this seems to be a 2.2 related issue and yet here it is in a 2.1 ROM??
 
OMJ said:
Those errors are fine. The recovery does not know what os version you have so it attempts to backup everything. If there is nothing there it skips it. That's all that happened
Click to expand...

wheww:D man hes had a rough day lol!
 
You must log in or register to reply here.
Back
Top Bottom