Database Develop

SD cleanup questions

Hello all,
When I first rooted my phone a week or so ago, I literally had no clue what I was doing. I knew it worked, I was happy, and I haven't touched the original files since.
Now that I'm a tad more familiar with the inner workings of the OS, flashing images, etc., I have a couple questions in regards to files from the original process.
First, am I correct in assuming:
- DREAIMG.nbh is the original RC29 image with root access and I need to keep it as a fall back if I ever brick my phone
- recovery.img allows me (via Power + camera button) to boot into recovery mode and apply the .nbh
- recovery_testkeys.img and boot_nosecure.img are vital to reimaging the .nbh as well
Lastly, I have four files (signapk.jar, testkey.x509.pem, testkey.pk and a README) in a directory called SignApk. Should I keep these around as well?
If this has been covered elsewhere on the forum, please point me in the right direction and have the Mods delete this thread.
Again, thanks for the help!

you can save all those files as backup in your pc.. if that what u are consern removing them fron your sdcard and having them backup in your pc.. they are already copied on to the phone.

Sorry, I should have searched better. I came across a thread (http://forum.xda-developers.com/showthread.php?t=491821) where someone thought they "bricked" their phone, but were able to get back to RC29 by going into recovery mode and restarting.
It appears as though the only reason they were able to save their phone was because DREAIMG.nbh was here. Maybe I'm wrong.
I'm worried that if f I find myself in the same situation and the nbh isn't there, I'm SOL.
Although I appreciate your help, I think I'll just leave these files alone and stop being OCD about files laying around in the root of my SD card.
Thanks for replying though!

ryan75 said:
I'm worried that if f I find myself in the same situation and the nbh isn't there, I'm SOL.
Click to expand...
Click to collapse
That is what an SD card adapter or a USB adapter is for.

seeking help....flashing new recovery img

ok so im currently running theoriginal donut tmo US with the stock 1gig sd card wat imt trying to do is set up apps2sd but y probem is i cant get ext2(or 3 whichever s suggested) set up now before im burned at the stake and told to use the search or have someone redirect me google.com rest assured i hav tried both routes and i have even went as far as messaging users for help but still not working.... i tried this http://forum.xda-developers.com/showthread.php?t=535232 didnt work and so nephron suggested i flash RA recovery but i get a message saying recovery image not found when i try to do the commands in the terminal...now i dont try to act like one of the elite around here but i can follow simple instructions or for that matter copy a command off the computer screen to the g1 terminal with out errors and just to make sure i didnt fudge something in the process i tried the command several time and now i come to the community for for advice and guidance ....
sorry for the long winded post...

bladepbc said:
ok so im currently running theoriginal donut tmo US with the stock 1gig sd card wat imt trying to do is set up apps2sd but y probem is i cant get ext2(or 3 whichever s suggested) set up now before im burned at the stake and told to use the search or have someone redirect me google.com rest assured i hav tried both routes and i have even went as far as messaging users for help but still not working.... i tried this http://forum.xda-developers.com/showthread.php?t=535232 didnt work and so nephron suggested i flash RA recovery but i get a message saying recovery image not found when i try to do the commands in the terminal...now i dont try to act like one of the elite around here but i can follow simple instructions or for that matter copy a command off the computer screen to the g1 terminal with out errors and just to make sure i didnt fudge something in the process i tried the command several time and now i come to the community for for advice and guidance ....
sorry for the long winded post...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=534714
well thats for editing your partitions.

You can look up a guide or try the root guide in my sig.

message saying recovery image not found when i try to do the commands in the terminal
Click to expand...
Click to collapse
Are you sure you typed in right? make sure you use recovery-RA-dream-v1.3.2
and not recovery.img unless you renamed the file when flashing. also, it must be on the root of the sd card

B-man007 said:
Are you sure you typed in right? make sure you use recovery-RA-dream-v1.3.2
and not recovery.img unless you renamed the file when flashing. also, it must be on the root of the sd card
Click to expand...
Click to collapse
Yea I'm pretty postive I typed it all in right I tried several times to make sure I wasn't makeing a stupid mistake like putting v1.2.3. (Did that once) I copied it letter by letter and still said recov_img not found
And ace I tried a few other guide and I'm hitting the same wall. But thanks for ur guys help and thanks for not telling me to search first( idid and got a bunch of posts telling people to search) ok well I'm gonna continue u looking for my answers but if someone happens to kno what I'm doing wrong by any chance throw a dog a bone here...lol alright well thanks again guys

bladepbc said:
Yea I'm pretty postive I typed it all in right I tried several times to make sure I wasn't makeing a stupid mistake like putting v1.2.3. (Did that once) I copied it letter by letter and still said recov_img not found
And ace I tried a few other guide and I'm hitting the same wall. But thanks for ur guys help and thanks for not telling me to search first( idid and got a bunch of posts telling people to search) ok well I'm gonna continue u looking for my answers but if someone happens to kno what I'm doing wrong by any chance throw a dog a bone here...lol alright well thanks again guys
Click to expand...
Click to collapse
Just to rule out any typos, plug your phone into your PC. Mount the phone. Navigate to the SD card and rename the recovery file to "recovery.img". Now unmount the phone. Then go to Terminal and type the following, hitting Enter after each line:
su (if prompted for super user access, just tap "Always Allow")
mount -o rw,remount /system
flash_image recovery /sdcard/recovery.img
Tell us if you get the same error message.

Help please, I rooted my g1 a while back and forgot everything

phillyblunt said:
I have JF 1.5 installed still and think its about time to upgrade. I have the latest radio but I think I need to update my spl which is the latest version I need to use this rom. Also I have partition magic so I can use that to format the sd card for apps 2 sd right? , I just do a ext2 on one half and ext3 on the other then cops all the files from the zip of 1.7 to the root of the sd card or do I have to put the app folder on ext3 and everything else on ext2 then just flash into recovery and update with the img? sorry for the questions I rooted my phone like 9 months ago and pretty much forgot everything I read and learned.
also I do have root access because I can use wifi teather and other root things but when I went to install cyanogen recovery Image and I go to terminal and type in mount /sdcard it tells me SDcard not found in /etc/fstab and If i type create a dir it says permission denied, can anyone help with that?
Click to expand...
Click to collapse
uansari1 said:
Jesus f-ing Christ! Just to shut you up, I'll give you an answer... but know that I'm doing so halfway hoping you brick your phone due to the stupidity of your question.
This isn't the right place to ask questions about SPLs and partitioning cards. However, I'd suggest you look in my sig for info regarding the SPL. Most people that use Partition Magic, Paragon, etc. to partition end up with problems. If you upgrade to Amon_RA's latest Recovery, he's included an automatic partitioning script where you can even select the sizes of the partitions.
As for the files.. You FLASH the zip file via Recovery.
Click to expand...
Click to collapse
phillyblunt said:
the link you have for Flashing the Haykuro SPL? Follow directions in post #3 HERE. does not work if you try to download the spl. Like I said I have the latest radio so once I do that spl all I will need to do pretty much is install amons latest recovery and have it partition the sd card as well has have a recovery option. Then do a nandroid backup and install the new 1.17.1 of dwangs script and I should be good to go right.
Click to expand...
Click to collapse
phillyblunt said:
do you have a working link for that spl, again sorry for pissing you off. Just I was in a bad car accident in april been out of work and out of commission haven't really messed with my phone. Last question I promise. I got Amon_RA's latest Recovery and I renamed it to recovery.img but when i try to copy it to the data folder on system it gives me a permission denied error. Is there a file browser on the market that will let me copy it over or is their a way to browser the system files thru the pc and copy it that way. Thanks again.. merry xmas
scratch that sorry, They got me on good meds, found the spl now I just need to get the file to copy to the data folder
Click to expand...
Click to collapse
phillyblunt said:
hmm I think I might of messed up my root access a while back. I installed what I thought was a modded cupcake firmware but Maybe I did google's. My build number says htc_dream-eng.15 cupcake eng.benji.20090609.153832 test keys and my kernel version is 2.6.27.24-cm [email protected] firmware 1.5. Do I need to go backwards or do I still have root access cause Like I said wifi tether still works. btw I am going to copy all of this and move the whole thread to the right forum board and stop posting in this one.
Click to expand...
Click to collapse
So do I or do I not have root, also if anyone can help me to copy that recovery.img to the system folder so I can do a nandroid backup and partition it the right way that way I can get apps 2 sd working and that new rom I want.

Sorry can you go back and quote properly, I lost all interest when it said you logged in and yeah. Might help if things were quoted

Sorry about that there you go

phillyblunt said:
Sorry about that there you go
Click to expand...
Click to collapse
Thanks, here let me go and read it now I'll try and help

1.Press cam+power-should say this if you have haykuro spl
DREA 100 PVT 32B HBOOT-0.95.0000. CPLD-4. Radio 0-2.22.19.26I Sep 2 2008
2.Goto recovery mode= power+hme
if you have jf or cyan recovery root is still one with you
Also if you have 3 skateboard droids in fastboot then you def got root.

Nah I still have the rainbow boot screen. if I update the spl will it give me root again and let me modify the system files

Make sure you updated your radio before you flash your SPL!!!!

G1 rooting problems

Hello everybody,
I try to root my 1.6 G1 for many days now. Followed many more tutorials. TheUnlockr, YouTube, XDA-Dev and other Android-Forums.
The problem is an error message when I try to flash the 1.5 Update. Everytime it says "00028002 Not allow". Tried the flashing process with so many DREAIMG.nbh's from different websites. Tried the US and the UK Version but nothing, really nothing worked.
And now, after Google and all these tutorials didn't work, I ask you for help. I hope that i won't get stupid posts =)
Thanks in advance!

did you format to FAT32?

I really don't know. I normally use Mac OS X 10.6.2 and don't know how to format there. Under Windows 7 which I use with BootCamp I right-clicked the SD-Card and selected "format..." but then there is an error message too like "not found". I don't have an adapter for the microSD. Do you have any Tips for me?

i'm not sure about other ways to format (anyone, lend a hand please?) but i think you need it to be FAT32.
EDIT: disk utility. i think you can get it there. just backup beforehand.

I Googled for formatting under Macintosh. FAT works, but there's no option for FAT32... Really need help.
Could anyone post me the "best" files/tutorial for downgrading a german G1, please?

19SK91 said:
I Googled for formatting under Macintosh. FAT works, but there's no option for FAT32... Really need help.
Could anyone post me the "best" files/tutorial for downgrading a german G1, please?
Click to expand...
Click to collapse
Well read the edit in my post. Some say Disk Utility works for FAT32, some say it doesn't. Hmm, i don't have macintosh so i can't really try it ATM.

Disk Utility was what I tried. But I just have these options:
4 times "Mac OS X Extended" and "MS-DOS Dateisystem (FAT)". Don't think that this is right.
But do you have a link to a tutorial for rooting a german G1 at 1.6? Because the files I downloaded always had different sizes and I don't know which the right one is/was?

19SK91 said:
Disk Utility was what I tried. But I just have these options:
4 times "Mac OS X Extended" and "MS-DOS Dateisystem (FAT)". Don't think that this is right.
But do you have a link to a tutorial for rooting a german G1 at 1.6? Because the files I downloaded always had different sizes and I don't know which the right one is/was?
Click to expand...
Click to collapse
Fat32 might be a windows only format just like EXT is a linux only format, so you will need to find a program that can do it like paragon or have a friend format it on their computer.

I do have Windows but it always says that the SD card can't be found. Don't know why.
I connect the G1 to my MacBook and run Windows 7. I mount USB and choose the SD card in Windows. Then I right-click on it and say "format...". After that it seems that the G1 automatically dismounts the SD card so that Windows can't find it...
Edit: How does the G1 itself format the SD card?
Edit 2: After formatting G1 in Mac (MS-DOS (FAT)) it said that something's wrong with the SD card and Android wanted me to format it again. I did it but Windows doesn't find the SD card anymore -.-'
Edit 3: G1 also doesn't find the SD card anymore xD

Formatted the SD card to FAT32 but the problem doesn't disappear...
Will try it now with RC7 instead of RC29. Don't think that it'll work because I already tried this before but who cares...
Edit: RC7 also doensn't work. I tried to install the "signed-kila-ota-148830.de6a94ca" update too. But after a while it says "Installation aborted"... I really need help!!

19SK91 said:
Formatted the SD card to FAT32 but the problem doesn't disappear...
Will try it now with RC7 instead of RC29. Don't think that it'll work because I already tried this before but who cares...
Edit: RC7 also doensn't work. I tried to install the "signed-kila-ota-148830.de6a94ca" update too. But after a while it says "Installation aborted"... I really need help!!
Click to expand...
Click to collapse
Alright put your sd card back into your g1. Unmount it in settings, then format it from there. When it's done, plug your g1 back into your computer or use and sd card reader (Personally, I prefer the card reader.) I use a mac based laptop as well, but i put windows on it as a partition. (I needa play my games ) See if your computer detects it now. And what do you mean that the problem doesn't disappear? Wasn't your problem the fact that the card didn't format?

No, the original problem is/was, that I can't get back to 1.5. No matter what file I choose, this damn "00028... Not Allow" problem appears everytime.

19SK91 said:
Formatted the SD card to FAT32 but the problem doesn't disappear...
Will try it now with RC7 instead of RC29. Don't think that it'll work because I already tried this before but who cares...
Edit: RC7 also doensn't work. I tried to install the "signed-kila-ota-148830.de6a94ca" update too. But after a while it says "Installation aborted"... I really need help!!
Click to expand...
Click to collapse
Na bra... go ahead an try one more thing..
Macs by default automatically unzip files when downloaded from the internet.
So if this is the case, the file your downloading isn't in the correct format (atleast for the phone). You can even try re-zipping the file but its not gonna work. This happened to me, the only way to fix it is to change the Mac preferences to not automatically unzip/open/handle files downloaded. Its been so long I cant remember the right steps in order to do this. But Im pretty sure thats why you're getting hung up. If you have a Windows availible to you, try downloading it again on the PC and moving it to your SD and see if it works Oo. Or just change your Mac settings and redownload. This MIGHT be your problem.
On second though, this might not be your problem. But maybe worth a try.

19SK91 said:
Hello everybody,
I try to root my 1.6 G1 for many days now. Followed many more tutorials. TheUnlockr, YouTube, XDA-Dev and other Android-Forums.
The problem is an error message when I try to flash the 1.5 Update. Everytime it says "00028002 Not allow". Tried the flashing process with so many DREAIMG.nbh's from different websites. Tried the US and the UK Version but nothing, really nothing worked.
And now, after Google and all these tutorials didn't work, I ask you for help. I hope that i won't get stupid posts =)
Thanks in advance!
Click to expand...
Click to collapse
Looking at your info, I'm assuming you're using a German G1
If that's the case I'm pretty sure you have to use the goldcard method to downgrade your G1 then root.
I'm not 100% sure on this, but based on what you've already tried and the flag below your location and post count, it might be a good idea to read up on it and try another method.
Check this thread out for a little more detail
http://forum.xda-developers.com/showthread.php?t=485364

@nopotential: So, could you tell me how to change this in the settings? 'Cause I right-clicked on a .zip, chose "open with..." and said "The unarchiver". Then i said "always open with" but it doesn't work...
@jackslim: I do have Windows 7 and the MacBook Pro does have a SD card reader but I do not have an adapter... Is there any chance to do this without a WM Device (If this is also Windows 7 ^^)?!
@all: Does anybody have a good downgrading tutorial für GERMAN/EUROPEAN G1s that worked for him/her too? That would be really nice.
By the way: What time is it in the US now? Is it in the morning?!

I'm just piecing together bits of other information I've found on various posts, so this may or may not work. Since you'll be using a macbook you should be able to dd to the sdcard
The first thing you need to do is get the CID of your SD Card
You can do this with adb, if you need help setting up adb see here
After ADB is setup
*Make sure on your phone you go to settings -> applications -> development and make sure USB Debugging is checked
check that it is working by opening a terminal and using
Code:
adb devices (enter)
If you see a serial number it's working, if not refer back to the adb setup guide and check for what you may have missed. If you seen a serial number do the next step
Code:
adb shell (enter)
cat /sys/class/mmc_host/mmc1/mmc1:*/cid (enter)
Now you should have the CID of your SD Card (write it down exactly). If you know an easier way to get this info directly from your macbook, feel free to try it that way.
Once you have your CID, go to this website scroll to the bottom, enter your email and cid as directed to, then wait for the email with your goldcard img
Once you recieve your goldcard.img, on your mac open a terminal, go to the directory you saved the goldcard.img to and
Code:
dd if=goldcard.img of=/path/to/your/sdcard bs=384 (enter)
*Note: Change /path/to/your/sdcard to what it actually is
Now add DREAIMG.nbh to the SD Card, and reboot your phone into the bootloader Camera + Power **Cross Fingers While You Wait*** And hopefully it will work
I don't have a Mac, never even used a Mac. I'm just piecing bits of information from different posts in an attempt to assist you downgrade. Although none of these steps should cause any damage to your Macbook/PC/Phone/House/Leg/Car or grandchildren. Try these steps at your own risk
And inresponse to the current time in the US, it's approximately 11:10 am on the eastern coast

Whoa, thanks for this. I don't know how to show you how thankful I am in english ^^
At the moment I'm not able to try this 'cause I'm busy but I'll post the result of it =)
Thanks again.

Also see this post
It specifically says for a Dutch phone, but I think most continental G1's that are having the downgrade problem require the same method to fix it

Samsung site link affects S7

Here's a odd one!
I was using my S7 to research an issue with my Samsung LED Smart TV. I found a How To, noticed a file path at the top of the page and backed up one page. It had several links, one of which was "How to Power Cycle a Customers Network". That sounded interesting so I clicked on it.
As soon as I clicked on the link my S7 turned OFF. I turned it back ON and it was stuck on the Dell logo. I pinned holed and tried again. It stuck again.
I booted into the recovery menu and tried to boot from there but it again got stuck. I had to do a factory reset. I use My BackUp Pro with a external SD card, it wasn't that painful and other than my email to setup, I'm back up.
Anyone see anything like this before?
Here a link to the nasty page for the brave to try: http://support-us.samsung.com/cyber/popup/iframe/pop_troubleshooting_fr.jsp?idx=151038&modelname=&modelcode=&session_id=P7mLwJcB60VpLrLWp3vgvhhXtfh2XSS3p78q2QlvhT3McsST29T1%21-1964052360%211228160092%211329276619709

Went to all the links on that page with no ill effects. You're Streak was just ready for a clean install

cdzo72 said:
Went to all the links on that page with no ill effects. You're Streak was just ready for a clean install
Click to expand...
Click to collapse
I just did a full factory reset around 1/7/12. Is the Android OS so fragile that it requires frequent resets? Your not running a stock S7 as I am, are you?
I suppose it was that it just shut off instead of a normal power off sequence that did the damage.

wptski said:
I just did a full factory reset around 1/7/12. Is the Android OS so fragile that it requires frequent resets? Your not running a stock S7 as I am, are you?
I suppose it was that it just shut off instead of a normal power off sequence that did the damage.
Click to expand...
Click to collapse
It's not fragile at all, it's about maintenance, just like a PC... you regularly need to wipe your app and dalvik caches just like you do disk cleanups and defrags on a PC.
You should clean up obsolete databases on your internal and external sd cards.... all those types of things. Many of us don't know what it is to have one single install of a ROM running for that long on our devices as we are constantly flashing updates and fixes, and a after a couple of those come around you naturally combine those into a package and flash clean from a factory reset.
But to answer your other question is no, I have never had stock ROM on any of my devices for no longer than it took me to go in and just have a peek at it to compare it to what I would be about to flash.

cdzo72 said:
It's not fragile at all, it's about maintenance, just like a PC... you regularly need to wipe your app and dalvik caches just like you do disk cleanups and defrags on a PC.
You should clean up obsolete databases on your internal and external sd cards.... all those types of things. Many of us don't know what it is to have one single install of a ROM running for that long on our devices as we are constantly flashing updates and fixes, and a after a couple of those come around you naturally combine those into a package and flash clean from a factory reset.
But to answer your other question is no, I have never had stock ROM on any of my devices for no longer than it took me to go in and just have a peek at it to compare it to what I would be about to flash.
Click to expand...
Click to collapse
I'm sure that a reset must wipe everything out, true? A reset barely a month ago. Your saying that monthly maintenance is needed?
I don't reinstall Windows monthly as that's a last resort at any time.

NOt a montly factory reset, but every week or so I wipe app caches and dalvik caches and let them rebuild themselves from use.... On Froyo for the S7 this is easily done through Clockwork Mod, but in Honeycomb and ICS I use SD Maid to clean app caches and another app called DroidTeaker to wipe the dalvik cache.

cdzo72 said:
NOt a montly factory reset, but every week or so I wipe app caches and dalvik caches and let them rebuild themselves from use.... On Froyo for the S7 this is easily done through Clockwork Mod, but in Honeycomb and ICS I use SD Maid to clean app caches and another app called DroidTeaker to wipe the dalvik cache.
Click to expand...
Click to collapse
Both for rooted devices and no good for me.

wptski said:
Both for rooted devices and no good for me.
Click to expand...
Click to collapse
1) well I have to tell ya, an android device that aint rooted just about isn't much more than a paperweight, so I have to ask why haven't you rooted?
2) I can't remember what version you're running on your S7, freshen my memory please

cdzo72 said:
1) well I have to tell ya, an android device that aint rooted just about isn't much more than a paperweight, so I have to ask why haven't you rooted?
2) I can't remember what version you're running on your S7, freshen my memory please
Click to expand...
Click to collapse
I've read, read and read then I read about some that appeared to have bricked theirs! They ask questions, get answers that are maybe too techy for the average user. Never hear that they solved the issue and I have to "assume" that they had to sent it back for service.
I've never read to date a real "Whatever for Dummies". Anyone can create a post full of links to other posts. What may seem simple to one isn't simple to another. Some have forgotten when they knew nothing.
There are probably more non-rooted S7's out there than rooted ones with perfectly happy users. Of course, there are the ones that get rooted, etc. right out of the box and a few that don't work after that too.
Like my signature states, I have a stock HC 3.2 with build 21700.
Getting back to the Android OS not being fragile. I had a misunderstanding of sdcard meant as in doing an update from sdcard which really means sdcard2 or external. I put the 514 update.pkg in the S7's internal memory. It errored and got stuck on the Dell logo. That was one factory reset because it couldn't handle that error or recover from it properly. Get a SD card and put update.pkg on the SD card. Get a file name mismatch error this time but it does reboot. Read up a bit and find something to rename to Update.pkg. Worked like a charm. Why was it case sensitive for me but maybe not for others??

wptski said:
I've read, read and read then I read about some that appeared to have bricked theirs! They ask questions, get answers that are maybe too techy for the average user. Never hear that they solved the issue and I have to "assume" that they had to sent it back for service.
I've never read to date a real "Whatever for Dummies". Anyone can create a post full of links to other posts. What may seem simple to one isn't simple to another. Some have forgotten when they knew nothing.
There are probably more non-rooted S7's out there than rooted ones with perfectly happy users. Of course, there are the ones that get rooted, etc. right out of the box and a few that don't work after that too.
Like my signature states, I have a stock HC 3.2 with build 21700.
Getting back to the Android OS not being fragile. I had a misunderstanding of sdcard meant as in doing an update from sdcard which really means sdcard2 or external. I put the 514 update.pkg in the S7's internal memory. It errored and got stuck on the Dell logo. That was one factory reset because it couldn't handle that error or recover from it properly. Get a SD card and put update.pkg on the SD card. Get a file name mismatch error this time but it does reboot. Read up a bit and find something to rename to Update.pkg. Worked like a charm. Why was it case sensitive for me but maybe not for others??
Click to expand...
Click to collapse
1) rooting any android device WILL NOT brick it... what the user does AFTER rooting may render it useless and them have to start all over
2) rooting the S7 is as easy as putting the Superuser7.zip file on the external sd, flashing it through Clockwork Mod and that's that, takes about 2 minutes
3) have no idea why for some their recoveries are case sensitive, but the general consensus is that the update.pkg was corrupt to begin with more than likely. I have had problems downloading zip files and update.pkg files in Chrome and Internet Explorer, Firefox consistently gives me a clean file and checksum so I have never experiences the problem. The other issue is not using the correct stock recovery for the package being flashed.
4) when you tried to flash the 514 package and it got stuck on the Dell logo, then it sounds to me you have a glitch in your inner sd, it should not have flashed anything that would make it stick at the Dell logo if there was a problem with the file, thus that may be your entire problem, you have a problem internally that just hasn't truly reared it's ugly head...
5) my personal suggestion would be to flash DJ Steve's Honeycomb R2 ROM via NVFlash, that will wipe clean the innerSD and it's partitions, so any problem there may have been would get cleared up by the process. Then if you still want to remain stock you can flash the factory recovery and flash the 514 package again after your innerSd has been reformatted by the NVFlash
6) all that sounds like a lot, I understand your point, but all in all it all takes about 30 minutes

cdzo72 said:
1) rooting any android device WILL NOT brick it... what the user does AFTER rooting may render it useless and them have to start all over
2) rooting the S7 is as easy as putting the Superuser7.zip file on the external sd, flashing it through Clockwork Mod and that's that, takes about 2 minutes
3) have no idea why for some their recoveries are case sensitive, but the general consensus is that the update.pkg was corrupt to begin with more than likely. I have had problems downloading zip files and update.pkg files in Chrome and Internet Explorer, Firefox consistently gives me a clean file and checksum so I have never experiences the problem. The other issue is not using the correct stock recovery for the package being flashed.
4) when you tried to flash the 514 package and it got stuck on the Dell logo, then it sounds to me you have a glitch in your inner sd, it should not have flashed anything that would make it stick at the Dell logo if there was a problem with the file, thus that may be your entire problem, you have a problem internally that just hasn't truly reared it's ugly head...
5) my personal suggestion would be to flash DJ Steve's Honeycomb R2 ROM via NVFlash, that will wipe clean the innerSD and it's partitions, so any problem there may have been would get cleared up by the process. Then if you still want to remain stock you can flash the factory recovery and flash the 514 package again after your innerSd has been reformatted by the NVFlash
6) all that sounds like a lot, I understand your point, but all in all it all takes about 30 minutes
Click to expand...
Click to collapse
The same PKG file was used both times. I'll throw another oddity at you. I was unable to edit update.pkg to Update.pkg either using File Expert with the S7 or while connected to my PC. I'd edit, hit return and it always reverted back. I actually deleted it from the S7, changed the name from Windows then connected and copied it back. Later on while trying this from ES File Explorer a thing popped up, something about try different name or other. Sure enough, it doesn't allow just case changes. You have to rename it different and back again if you just wanted a case change.
I'm going to save your suggestions.

wptski said:
The same PKG file was used both times. I'll throw another oddity at you. I was unable to edit update.pkg to Update.pkg either using File Expert with the S7 or while connected to my PC. I'd edit, hit return and it always reverted back. I actually deleted it from the S7, changed the name from Windows then connected and copied it back. Later on while trying this from ES File Explorer a thing popped up, something about try different name or other. Sure enough, it doesn't allow just case changes. You have to rename it different and back again if you just wanted a case change.
I'm going to save your suggestions.
Click to expand...
Click to collapse
Then you definitely had/have a corrupt package and the renaming is a sign of a read only problem trying to surface sounds like to me