Database Info

Newbie, please help, nandroid problems...

Hi,
I hope this is in the right section....
I have recently put the QTEK 1.6 Hero ROM on my Sapphire (UK MAGIC), and its ok but I preferred the stock ROM.
I have obviously done a nandroid backup using the RAV1.2.1G recovery image, using the one-click method (http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/).
I want to revert back to the stock ROM using my nandroid backup. I have follwed the instructions on these forums on how to do it, but I keep getting a problem.
I use the flashboot flash system system.img, it says sending, then writing, but when it comes to verifying info something or other, it says failed, something and something about unable to verify signature (happens on data and boot imgs too).
Is this something to do with SPL, do I need to update my SPL to restore, I have downloaded HARDSPL (version?) but have not gone any further as I dont want a brick....
Any help would be much appreciated.....
Thank you

If you were able to make a nandroid backup with your current SPL, then i assume thats not the problem.
Are you sure the files of your backup is still on your SD-card, and its (foldername "nandroid") location is root on SD-card..?

Hi,
Thanks for your reply.
Yes the nandroid folder is on the root of the sdcard, i've managed to get it working. Very strange??
What I did was to ignore the windows way of restoring, I just booted into recovery and selected nandroid restore, pressed green and hey presto, it worked? Now I tried that before and it said use adb in windows... maybe i missed a file or didnt press something correctly, at least I have my stock and apps back now...
Will try tinkering again though...got to be done... QTEKs rom has a few bugs, want to try Cyanogens, but i cant find his rom anywhere (i realise the issues with google)

Then i guess your SD-card wasnt ready mounted the moment you tried to recover.

He didn't recover via recovery, but via SPL.
so, do 1clickroot again, but instead of flashing a rom in recovery, select: restore nandroid recovery.

What if
What if we never created a Nandroid backup of the OEM ROM from our phone?
Will we still be able to return to the original ROM if we'd like for warranty purposes? I have flashed a Hero ROM and the OEM Tmo for Root Users and AmonRA Recovery. I haven't flashed any Radios or SPLs or anything though.
Just curious, thanks.
I downloaded the Unroot IMage which is exactly the release I used to have, COC10, is this the ROM I need for warranty purposes?

Samsung vibrant help needed.

I flashed back to stock 2.1 on my samsung vibrant.
the phone boots up fine at first, then all of a sudden i get a wierd screen and the phone reboots automatically. i dont know what the problem is. can anyone please help me with this problem.
the phone is continuously rebooting for the past half and hour. and i have no idea what to do now.
PLEASE HELP ME WITH THIS.
im posting a photo of the "wierd" screen below. the quality is crappy, but i cant help it.

Were you coming from a GB rom? Be sure your not mixing bootloaders...Not sure what that is but if you flash just the stock kernel in ODIN, with the phone off (pull the battery)and using the button combo try and get into DOWNLOAD mode. you might recover it....or flash the Bali kernel and then try going back to stock again.

erad1 said:
Were you coming from a GB rom? Be sure your not mixing bootloaders...Not sure what that is but if you flash just the stock kernel in ODIN, with the phone off (pull the battery)and using the button combo try and get into DOWNLOAD mode. you might recover it....or flash the Bali kernel and then try going back to stock again.
Click to expand...
Click to collapse
yes i did try flashing a 2.3 ROM,but it didnt work properly, so i tried flashing the stock 2.1 again using ODIN...it got installed, but later all these things started happening.
i even flashed the 512 PIT file that came along with the stock 2.1, but still no use.
can u please post the link to the kernel you are talking about and also how should i flash the kernel?
thanks for your reply.

hey the problem is solved. i installed eugene's 2.2 leaked build and my phone is back to normal now...!!!!
thanks for all your help. i really appreciate it...!!!

Glad to hear you got it...just be careful to know which bootloaders you are on, GB or FROYO... unless you have alot of problems with a ROM its not really necessary to ever flash back to stock...I flash rom to rom without any issue as long as you:
1. wipe cache partition,
2. then wipe dalvik cache and then
3. factory reset all from CWM...
4.then flash whatever .zip ROM you like.
Flashing back to stock FROYO/ECLAIR from GB with an odin rom you must be sure the stock rom either includes both PBL and SBL or no bootloaders at all and then your good.

Gb Stock Rom Recooked

Im working on recooking the stock gb rom with root support. Thank you white for the deodexed version without the sbl and boot support.
The reason for this recook as sammyfirmware gave us the leaked gm rom with a messed up sbl file which is why we lost recovery support as the boot loader seems to be from the international verson and the sbl file seems to be from one of the i9000 that had a borked sbl that didnt allow for the the recovery boot.
those of you that went from KD or anything pre gb that went to whitehawks rom you are ok as you didn't loose support and still have your non borked sbl file.
this is for those of us that did the stock gb rom and added root access after.
so if you used dsextons method off that rom which at the time we had no idea had a borked sbl please use odin and flash this rom as it will re add back a fixed sbl file ..
Also note if u dont reflash there is a possibility when the gb rom actually drops u wont get back recovery without doing this becuase it may not fix the borked sbl file.
if u have issues getting the rom to work let me know if u brick your phone i take no responsability for any damages gb may cause ...
Update
Updated install instructions
download and flash coocked gb rom in odin
once flashed data wipe cache wipe reboot phone go back into download mode
reflash kd1 or kb one onto your phone so the boot loaders stick
factory reset and cache wipe to pervent bootloops
reflash cooked gb rom back to system
cache and fs system wipe again
this will cause the gb cracked bootloaders to stick and give u a fully booting gb rom
Ginger snacks cooked adding to rom Made a nice ginger theme to go with this Dev build of the rom.
Things in progress deodexed
adding busy box and root support out of the box
bug fixes to prevent fc's
notification bar Bluetooth
notification WI-Fi fixes
Going to fix the premisson issues with the damn call log permanently...
ps i attached a working wi fi calling that isnt in the rom that will work on gb for those of you that would like wi fi calling feature back
update i removed the link do to to many people having issues im going to upload a full dump that u can odin using pit repartiton and flash back which wipes all of gingerbread off the device after that flash the flavor of your choice... Some got it to work via flashing then flashing back to kb 1 then kd 1 and back to cause it to stiick. WHy its not working for the rest of everyone i need to do more testing with..
but for now
http://sourceforge.net/projects/kc1cleanup/files/hawk.zip/download
updated link
that will get you out of it and restore your boot and sbl files back to kc one

RaverX3X said:
Im working on recooking the stock gb rom with root support. Thank you white for the detoxed version without the sbl and boot support.
The reason for this recook as sammyfirmware gave us the leaked gm rom with a messed up sbl file which is why we lost recovery support as the boot loader seems to be from the international verson and the sbl file seems to be from one of the i9000 that had a borked sbl that didnt allow for the the recovery boot.
those of you that went from KD or anything pre gb that went to whitehawks rom you are ok as you didn't loose support and still have your non borked sbl file.
this is for those of us that did the stock gb rom and added root access after.
so if you used dsextons method off that rom which at the time we had no idea had a borked sbl please use odin and flash this rom as it will re add back a fixed sbl file ..
Click to expand...
Click to collapse
yea guys this has been a real pain in the ass,
lets just say im going to tmobile right now... LOL
stupid i9000 bootloader

no **** lol thanks for hardbricking ur phone so we could figure it out ya he needs a donate he took one for the team...

tired i couldnt get it to root from a stock flash without doing the origonal methood so im uploading the stock with fixed sbl and bins as always flash at your own risk..
been trying to upload with media fire umm it uploads then the page says i didnt upload anything so will keep posted

RaverX3X said:
Im working on recooking the stock gb rom with root support. Thank you white for the detoxed version without the sbl and boot support.
The reason for this recook as sammyfirmware gave us the leaked gm rom with a messed up sbl file which is why we lost recovery support as the boot loader seems to be from the international verson and the sbl file seems to be from one of the i9000 that had a borked sbl that didnt allow for the the recovery boot.
those of you that went from KD or anything pre gb that went to whitehawks rom you are ok as you didn't loose support and still have your non borked sbl file.
this is for those of us that did the stock gb rom and added root access after.
so if you used dsextons method off that rom which at the time we had no idea had a borked sbl please use odin and flash this rom as it will re add back a fixed sbl file ..
Also note if u dont reflash there is a possibility when the gb rom actually drops u wont get back recovery without doing this becuase it may not fix the borked sbl file.
Rom to come later as to make sure that it works 100 percent and no more issues with it borking back to not letting us have recovery support.
Click to expand...
Click to collapse
I knew someone would do this..I've been waiting

Downloading now. Do I need any of the CWM files on my sd card?

this right now should fix the problem that people had that flashed the initial... Where u could GET INTO download mode BUT COULD NOT get to recovery..
We still need Krylon to get a working recovery for us... This will just get you back recovery mode support.
all i did was fix the sbl and boot files..
The boot to download and recovery keys after u flash should revert back to pre GB which is
Vol up Vol down stick in usb for download mode
and then vol up and down and power for recovery..
When and if i can get a root Busy box + clockwork flashable ill upload that in its place and update the origonal post to reflect it Me and dsexton702 spent 2 days trying to get this back to where it should work proper and we bricked his phone in the process to bad he didnt live closer i could have unbricked it for him..

Just sitting at the galaxy s 4g logo right now. Was I supposed to flash all 4 files? I just did pda and phone

de1packers said:
I knew someone would do this..I've been waiting
Click to expand...
Click to collapse
yep i hardbricked for the sake of the community
just ordered my new sgs4g but samsung is out of stock at the moment, so wont get my new phone for about a week or so
ill still be helping you guys out though

Ichibahn SLC said:
Just sitting at the galaxy s 4g logo right now. Was I supposed to flash all 4 files? I just did pda and phone
Click to expand...
Click to collapse
i included all files to be safe reflash it with odin with pit phone pda csc
if your at the galaxy s 4 logo give it a bit it does take a bit for the inital boot its not that fast

Got it into download mode with the two vol button pressed and then the cable plugged in. Will try again.

how long did u wait at the galaxy screen cause it does take a min if it doesn't work after that let me know i may have included the wrong boot file but that's differently the right sbl file

RaverX3X said:
Im working on recooking the stock gb rom with root support. Thank you white for the detoxed version without the sbl and boot support.
The reason for this recook as sammyfirmware gave us the leaked gm rom with a messed up sbl file which is why we lost recovery support as the boot loader seems to be from the international verson and the sbl file seems to be from one of the i9000 that had a borked sbl that didnt allow for the the recovery boot.
those of you that went from KD or anything pre gb that went to whitehawks rom you are ok as you didn't loose support and still have your non borked sbl file.
this is for those of us that did the stock gb rom and added root access after.
so if you used dsextons method off that rom which at the time we had no idea had a borked sbl please use odin and flash this rom as it will re add back a fixed sbl file ..
Also note if u dont reflash there is a possibility when the gb rom actually drops u wont get back recovery without doing this becuase it may not fix the borked sbl file.
Rom to come later as to make sure that it works 100 percent and no more issues with it borking back to not letting us have recovery support.
http://www.mediafire.com/file/hr6ir56xd6z6jkc/T595VUVKF1-fixed.7z
if u have issues getting the rom to work let me know if u brick your phone i take no responsability for any damages gb may cause ...
Click to expand...
Click to collapse
Or you could use quickboot. Just download from the market.
Sent from my SGH-T959V using XDA Premium App

Mine boots into recovery fine using quick boot, am I missing something? I was stock gb then rooted
Sent from my SGH-T959V using XDA App

ya ur missing the point without quickboot u couldnt boot directly into recovery from the volume up down and power button to get into cwm at all as the sbl file that was included in the package was messed up.
also remaped the keys pre ginger flash so u could get into download mode the old way with the 2 button insert usb..
well im going to work more on gettin root support out the box custom shut down and startup animations and deodexing the rom and then adding back stuff so the rom doesnt fc at the notifcaton screen when u turn on bluetooth also will look into fixing the call log also.

kkoshko1 said:
Mine boots into recovery fine using quick boot, am I missing something? I was stock gb then rooted
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Me too, quick boot is fine. I believe this ROM was unfinished, hence the lack of recovery. At this point in our game, recovery is insignificant. Even CWM isn't working right. I'm still trying to understand the issue with recovery.
Sent from my SGH-T959V using XDA Premium App

re read origional post if you dont understand it please re read cause i dont know how else to tell you that you have a flashed file on your phone that broke some of the key press sequences on your phone in short if you did the inital gb rom and didnt wait for whitehawks you now have a broken sbl file on your phone... Thats the point.

ADVANTAGES OVER QUICKBOOT
Someday, we will be flashing a CM7 on our phone. If we use quickboot and we are in recovery, we flash, flash fails, we have to ODIN all the way.
With a fixed sbl, just restore.

airfluip1 said:
ADVANTAGES OVER QUICKBOOT
Someday, we will be flashing a CM7 on our phone. If we use quickboot and we are in recovery, we flash, flash fails, we have to ODIN all the way.
With a fixed sbl, just restore.
Click to expand...
Click to collapse
Thanks that's all i have to say...

pjim said:
Me too, quick boot is fine. I believe this ROM was unfinished, hence the lack of recovery. At this point in our game, recovery is insignificant. Even CWM isn't working right. I'm still trying to understand the issue with recovery.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
more plane and simple even if you flashed a finalized ginger rom there was no 100 percent chance they would have included fixed files along with it so you may have well never been able to reboot back into recovery without quickboot which like another poster put eventually we will get cm7 and you would have still had the borked files.

No .androidsecure?

Ok so i backed up my tf using cwm and everything worked perfectly. When i try restoring the back up it first restores the system apps but then there is an error saying the is no .androidsecure file. And my tf wont boot up after. I then have to flash an old tf version for it start working again.
If anyone has a solution that would be great

mafo5000 said:
Ok so i backed up my tf using cwm and everything worked perfectly. When i try restoring the back up it first restores the system apps but then there is an error saying the is no .androidsecure file. And my tf wont boot up after. I then have to flash an old tf version for it start working again.
If anyone has a solution that would be great
Click to expand...
Click to collapse
It might not have anything to do with the 'error' which is maybe not an error, just an informational message from the "Froyo" days. This is all guesswork, but I seem to recall that .android_secure was for apps that were movable and moved to the sdcard. That just doesn't really make sense on the TF101 using Honeycomb, so if you don't have that folder (.android_secure), that that's cool.
Does the restore complete entirely aside from the message about .and* ?
Another thing I wonder about with cwm restores is the kernel. Did you have a working kernel in your tf101 before you got started with this restore? I'm not really seeing how it restores the kernel (boot.img/zImage/whatever) in this version of cwm. All I see saved is system.img, the md5sum, data.img and cache.img. My guess is that you might benefit by picking a kernel, like either the latest stock one or say, Prime's kernel, and burning that in afterward, clearing dalvik and rebooting again.
Note: It might be that everything needed is somehow in system.img and that cwm has the smarts to burn what it needs to the right places, but in every other version of cwm I've seen, there is a boot.img file in the cwm backup that contains the kernel.
If anyone knows how cwm is burning a blob for the kernel, I'd be curious to know how since I'm not looking at the code. Thanks.
Good luck

the restore doesnt completely restore.
It goes something like this....
System apps restore
I think another restore
Then the error
Restore cache
And then its done. It boots me up to an Asus image and wont go past.
These are the files in my cwm restore
Cache.img
Data.img
Nandroid.md5
System.img
Also i have stock kernel

mafo5000 said:
the restore doesnt completely restore.
It goes something like this....
System apps restore
I think another restore
Then the error
Restore cache
And then its done. It boots me up to an Asus image and wont go past.
These are the files in my cwm restore
Cache.img
Data.img
Nandroid.md5
System.img
Also i have stock kernel
Click to expand...
Click to collapse
So it sounds like the restore is completing with the message about the secure folder then dropping dead during the kernel load. If I understand you right, it sounds like you "had" a stock kernel when it was working, but I wonder if you've got any viable kernel right now?
Since your tf101 isn't working and is basically useless, you could try to boot back to cwm and burn some known working current kernel in there. I don't have the links right now to the stock one, but you could try a nearly stock one from the Prime ROM http://roach.qap.la/Roms/Prime_v2.0/OCKernel_Prime_v2.0.6.zip .
I don't know what his zip file looks like but at least it'll force the issue of burning a blob into the boot partition and you can tell if the kernel was the problem.
If that doesn't work, then your backup was possibly corrupted and I don't have a good answer other than to install either a stock image or one of the ROMs people use like Prime or Revolution and see how they do.
I'm also guessing that blowing a new image on there is a last resort because you had stuff setup the way you wanted it, but it's for you to decide that. You could search the forums for something that does some sort of integrity check on the cwm backups, or better yet, get in touch with Solarnz or Daoist via messages and ask their advice. They're experts here in cwm and I'm not.

hachamacha said:
So it sounds like the restore is completing with the message about the secure folder then dropping dead during the kernel load. If I understand you right, it sounds like you "had" a stock kernel when it was working, but I wonder if you've got any viable kernel right now?
Since your tf101 isn't working and is basically useless, you could try to boot back to cwm and burn some known working current kernel in there. I don't have the links right now to the stock one, but you could try a nearly stock one from the Prime ROM http://roach.qap.la/Roms/Prime_v2.0/OCKernel_Prime_v2.0.6.zip .
I don't know what his zip file looks like but at least it'll force the issue of burning a blob into the boot partition and you can tell if the kernel was the problem.
If that doesn't work, then your backup was possibly corrupted and I don't have a good answer other than to install either a stock image or one of the ROMs people use like Prime or Revolution and see how they do.
I'm also guessing that blowing a new image on there is a last resort because you had stuff setup the way you wanted it, but it's for you to decide that. You could search the forums for something that does some sort of integrity check on the cwm backups, or better yet, get in touch with Solarnz or Daoist via messages and ask their advice. They're experts here in cwm and I'm not.
Click to expand...
Click to collapse
I flashed another kernel but I still get the error when trying to restore. I've been searching around and I guess I'm missing the .android_secure file in the data.img. I just dont know how to fix it.
Btw my tf is usable and all I am just not able to restore all my apps and such. So its basically like new..

mafo5000 said:
Btw my tf is usable and all I am just not able to restore all my apps and such. So its basically like new..
Click to expand...
Click to collapse
Couldn't you extract data.img and then make a CWM zip out of that?
Sent from my X10a using The Force

AyDee said:
Couldn't you extract data.img and then make a CWM zip out of that?
Sent from my X10a using The Force
Click to expand...
Click to collapse
I dont know if that would work because, i think, the error is in the data.img.
I could try that though, how would i change it to a cwm zip?

Google "extract data.img android" and "make cwm zip" or search here.

AyDee said:
Google "extract data.img android" and "make cwm zip" or search here.
Click to expand...
Click to collapse
I found this app called app extractor and it can extract apps from old nandroid backups. It works when trying to restore the system apps but when i try to restore user apps it is unable to. If been searching around on how to extract the data.img and what ive found is that i need to use something call unyaffs. If you can point me in a way of a great tutorial that would be great because i can not find one...

[Q] cm10 unintall method for htc one v (india-gsm)

i have installed cm10 on htc one v primo-u (india gsm ) and i wish to revert to the original image.
i tried to flash India_1567201recovery_signed.img file but no success.
can someone help me with a procedure how to revert to either 1.56.720 or 2.09.720 image of the phone

romah1 said:
i have installed cm10 on htc one v primo-u (india gsm ) and i wish to revert to the original image.
i tried to flash India_1567201recovery_signed.img file but no success.
can someone help me with a procedure how to revert to either 1.56.720 or 2.09.720 image of the phone
Click to expand...
Click to collapse
How did you try to flash the RUU? You can not flash it like a normal ROM
Also if you are looking for the RUU try HERE
I see what you're trying to do, that won't work...you can't flash a recovery to get to stock because stock phone won't flash from recovery, which is why once you get root the first thing you do is flash a custom recovery. Use the RUU to flash it back to shipped state stock, or if you are trying to keep root and just want to use a different ROM. More clarification on what you are trying to accomplish would be nice.
If you did a Nandroid prior to flashing CM10 I would wipe all partitions except SD and restore the Nandroid, if all you want to do is get CM10 off your phone. Remember Nandroid Backups are your friend do them before flashing anything and save them to your PC if you don't want the SD space taken. Doing this has made flashing pain free and hassle free. If I don't like how my phone is running after a flash I can always get it right back to how it was when I was happy with it. Lastly there was a time when I had a Nandroid backup of a Sense ROM and was on AOSP and wanted to flash back to Sense, well my Backup wouldn't flash. After spending hours raising hell I did a clean install of the ROM booted once, then rebooted into recovery and flashed the Nandroid backup that had the settings I was using (when I was on Sense, it won't restore data and apps used on AOSP)...sorry if its not much help but more details are needed. But you have a starting point.

ItzCrooK2UxD said:
How did you try to flash the RUU? You can not flash it like a normal ROM
Also if you are looking for the RUU try HERE
I see what you're trying to do, that won't work...you can't flash a recovery to get to stock because stock phone won't flash from recovery, which is why once you get root the first thing you do is flash a custom recovery. Use the RUU to flash it back to shipped state stock, or if you are trying to keep root and just want to use a different ROM. More clarification on what you are trying to accomplish would be nice.
If you did a Nandroid prior to flashing CM10 I would wipe all partitions except SD and restore the Nandroid, if all you want to do is get CM10 off your phone. Remember Nandroid Backups are your friend do them before flashing anything and save them to your PC if you don't want the SD space taken. Doing this has made flashing pain free and hassle free. If I don't like how my phone is running after a flash I can always get it right back to how it was when I was happy with it. Lastly there was a time when I had a Nandroid backup of a Sense ROM and was on AOSP and wanted to flash back to Sense, well my Backup wouldn't flash. After spending hours raising hell I did a clean install of the ROM booted once, then rebooted into recovery and flashed the Nandroid backup that had the settings I was using (when I was on Sense, it won't restore data and apps used on AOSP)...sorry if its not much help but more details are needed. But you have a starting point.
Click to expand...
Click to collapse
i have installed CM10 without backing up any image, therefore i cannot restore the orifginal vendor's rom. Nandroid back would have prevented this situation. the second problem is that I couldnt find any RUU for this phone. indeed the link you attached seems to have it bu unfortunately it is in chineese and after pushing all the buttons i couldn't download the file. so my options are
1- to pray that someone will be kind enough to publish it in a manner that it is accessible
2- I have a friend with a simillar phone , can i somehow back up hus rom and restore it in mine ????
thank
romah1