Related
Im sorry if i posted this in the wrong section; I have no clue where im suppose to post this ;\. Anyway, i followed this tutorial trying to jailbreak my g1 http://www.youtube.com/watch?v=xOo2V9qCauc. I downloaded the RC29(From the youtube tut) and put it into my sdcard and turned it off and on by holding the power and camera button. So i got to the part where it asked me to update my image but when i finished i got a update terminated msg instead of complete\successful. Then it kicked me to the colorful\rainbow screen with red green blue and white. I have no clue what i did wrong and no idea what im suppose to do now, can't turn off the phone or anything. Can somebody please help ;x! Thanks
I desperately wanted to post and say to say it failed bc you think your phone is an iphone (jailbreak). However, after reading your post i would say abandon a video and follow the root guide that is a sticky on here... look at the information thread above your post and look in there for the root guide.
When it says to get a recovery.img get cyans in the development thread. When it says get a rom, get cyans 4.0.2 stable cupcake... when you are all done i rec the community hero theme.
I typed all of that and this thread was right below yours
http://forum.xda-developers.com/showthread.php?t=548924
I believe jailbreak is another word for rooting @[email protected];
And i really want to know is how do i get outta this rainbow\color screen. Do i have to take out my battery? Want to make sure before i do so ;\
Snailrawring said:
I believe jailbreak is another word for rooting @[email protected];
And i really want to know is how do i get outta this rainbow\color screen. Do i have to take out my battery? Want to make sure before i do so ;\
Click to expand...
Click to collapse
That works, give it a try!
shaolinx said:
That works, give it a try!
Click to expand...
Click to collapse
What you mean that works?
Dang i took out the battery and turn the phone back on but i went back to the update image part >_>; . No matter which choice i choose i end up at the colorful screen....(Choices are either update or not)
is your rc-29 named DREAIMG.nbh exactly named that caps and all. also is your sdcard formatted to fat32.
Snail....
I went to bed last night thinking you were fine. Could you post exactly what steps you have done? If you press red (power) + menu + green (call) your phone will reboot (no need to pull the battery).
Did you remove (delete using your computer) the .nbh file when you put the image and update.zip file on your SD? Did you get the files from the site you visited for the video?
I strongly suggest following my first post.
Just like everyone else said, follow our guides instead of some video on youtube. Make sure your card is formatted to fat32 and try to update again. If that still doesn't work it might have been a bad download. So download DREAIMG.nbh (RC29) again. You can check the MD5sum to make sure its a good download and update again. And by the way jailbreaking ain't the same as rooting.
s15274n said:
Snail....
I went to bed last night thinking you were fine. Could you post exactly what steps you have done? If you press red (power) + menu + green (call) your phone will reboot (no need to pull the battery).
Did you remove (delete using your computer) the .nbh file when you put the image and update.zip file on your SD? Did you get the files from the site you visited for the video?
I strongly suggest following my first post.
Click to expand...
Click to collapse
These are the steps i've done
1.Copy and Paste all the files within my sd card to my pc.
2.Changed my sdcard into fat32
3.Dragged the dream.nbh or w\e that i got from the video tut into my sd card.
4.Turned off my phone by holding the power button.
5.On by holding power and camera.
6.Then i got to the update image part and pressed power to update, buy failed to update and now end up stuck at the color screen.
I've tried to reboot and everything but everytime i turn it back on it always goes back to the color screen T___T
Snailrawring said:
These are the steps i've done
1.Copy and Paste all the files within my sd card to my pc.
2.Changed my sdcard into fat32
3.Dragged the dream.nbh or w\e that i got from the video tut into my sd card.
4.Turned off my phone by holding the power button.
5.On by holding power and camera.
6.Then i got to the update image part and pressed power to update, buy failed to update and now end up stuck at the color screen.
I've tried to reboot and everything but everytime i turn it back on it always goes back to the color screen T___T
Click to expand...
Click to collapse
Have you redownloaded the DREAIMG.nbh file. It was prolly just a bad download. Happens all the time, thats why you wanna check the MD5sum.
your new best friend
as mentioned before sub in Cyans recovery image version 1.4 *you will thank me* and Cyans 4.0.2 rom *you will thank me*
supremeteam256 said:
Have you redownloaded the DREAIMG.nbh file. It was prolly just a bad download. Happens all the time, thats why you wanna check the MD5sum.
Click to expand...
Click to collapse
Yea i would love to do that too but im stuck at the color screen D:< how do i get outta there T___T
Snailrawring said:
Yea i would love to do that too but im stuck at the color screen D:< how do i get outta there T___T
Click to expand...
Click to collapse
Just pull the battery. Redownload DREAIMG.nbh put it on your sd card and try to update again. Get the file from this site now instead of youtube.
supremeteam256 said:
Just pull the battery. Redownload DREAIMG.nbh put it on your sd card and try to update again. Get the file from this site now instead of youtube.
Click to expand...
Click to collapse
Tried that when i take out my battery and turn it back on it goes back to the update image part and nothing happens when i plug in the usb
Oh and supreme do you have aim, msn or something? I hate this forum posting takes forever xD.
Snailrawring said:
Tried that when i take out my battery and turn it back on it goes back to the update image part and nothing happens when i plug in the usb
Oh and supreme do you have aim, msn or something? I hate this forum posting takes forever xD.
Click to expand...
Click to collapse
Yea I do its supremeteam256 on aim. I'm at work now so I can't do it on my computer and my phone signal might be hit or miss, but I'll still log on just deal with me if it shows me cuttin in and out. But what your going to have to do is either put the new DREAIMG.nbh on your sd card either by a card reader or another electronic device that you can transfer files over to the sd card. And the last option will be to mount your card using ADB and just push the file to your sd card. But as of right now it sounds like you can't access your phone because of the bad file. So once you get that file on your card then you would be able to boot holding camera + power and apply RC29. You'll be straight after that.
Yay got through with the image update part and now im stuck at the setup wizard part. Somehow my phone has problem with communicating with google servers when i type in my google account. And yes i don't have internet. I canceled it because i got this when it first came out and for the first 1-2months nothing worked on it such. None of the messengers work D:< so i had no use of internet so i end up cutting it xD.
Register w/o data plan
Uhh thanks but sorry im a newbie D:<. I did downloaded it from here
http://developer.android.com/sdk/download.html?v=android-sdk-windows-1.5_r3.zip
But when i try to open adb in the tool folder a command window pops out and disappear nothing happens ;\
Snailrawring said:
Uhh thanks but sorry im a newbie D:<. I did downloaded it from here
http://developer.android.com/sdk/download.html?v=android-sdk-windows-1.5_r3.zip
But when i try to open adb in the tool folder a command window pops out and disappear nothing happens ;\
Click to expand...
Click to collapse
You don't open it... it's utility
open command prompt (window key +R, type cmd) from there you can run adb commands (adb shell, adb pull, adb push or whatever else you need)
adb is your friend, learn how to use it. It will save you when your in trouble... trust me
Hello, i'm new to this forum, i would like to thank you for taking your time to help me out.
First, i had a clean Starhub 2.1 android running milestone with update1, i flashed the G.O.T open recovery's of STAR_36_GOT_SERVICE.sbf to my phone, follow up by, opening the recovery mode and open the G.O.T open recovery's thru the updates.zip as instructed. After that i rooted the phone with the options there. after rebooting my phone and ensure that superuser is already there. i when back to the recovery menu and flashed the fastlightrom v2a, after indicating that it is done, i reboot the system and check the free space in setting it was 164mb or somewhere near there. With this and i went back to the recovery menu and went to the app2sd hack menu and split my sd card, i chosen the 8gb one, which create 1gb ext2 if i am not wrong, after the process is done, i went to install app2sd symlik edition, everything went smoothly and i reboot the phone and check the space again, it had 194mb ( Oh yeah ! ) Does this mean that app2sd had sucessfully installed to my phone?
To ensure that it is, i went ahead and install program like launcherpro, msntalk , and so on. i found out that , my memory had began to drop to 189mb, nevertheless so had sdcard. My Sdcard display a maximum of 6.9xgb of space, which means the sd card split was a sucess right? My worried start here, am i safe to say that the others programs that i am going to install from now on would be install to my sd instead?
I also found out that my current cpu freq was 1000mhz , by using android system info found in the market, i went to download the overclocking widget, i manage to tweak here and there and revert it back to 550mhz, so am i on the safe track that i did not hurt my phone in any way or other?
- Went to the recovery menu and clock it to 650mhz instead. solved?
Any kind soul could enlighten me with some good advices or config? i was temp to install the app2sd provided by dsixda's post when i post my enquire there.
And also, it seem that all my .apk that require root installation when i download them from the internet, i found out that it had become a zip file instead, with this i am unable to install it thru adb install right?
Thanks for taking your time to read this message, please give your advises, Sorry for my bad english.
Solved my doubts thanks.
I have searched a lot, spent time trying to figure everything out.
I have Hero that I am trying to make BA for my little bro. I have the evo now. Rooted and tethering. Not much else I need to mess with on it. Fast enough for me. But my old hero is now rooted and has the app to tether. I can't figure out how the heck to over clock it. It is slow and I want to kick it up a couple notches for him.
I have searched and all the codes that you guys use at the top throw the searches off, or maybe I am searching for the wrong thing.
Any links to other threads would be great. That way when someone else searches just over clocking like I did it will come to this thread and then link to the useful threads.
Thanks in advanced.
I see you are rooted already, is the phone running a stock rom? If so think about installing [ROM] cyanogenMod 6.1 stable (<<<<search). Then you flash a [Kernel] [GPL] DecaFuct [2.6.29.6] (<<<<search) and install a app called OverClock Widget, it is easier to use than the other one you can use called SetCPU. Thats pretty much it, somebody may chime in that can put a few links up but I am on my phone right now so I cant.
DecaFuct Max 768Mhz Kernel
DecaFyct Max 698Mhz Kernel
Decad3nce's Kernel OP Thread
These are JayBob's CM6.2 ROM Downloads.
Okay, so I need to back up my phone? Can I use the app on the android market MyBackup by Rerwarre, LLC? Then I need to download the files you linked me to in this thread? And then what?
Okay. I am sure you are all tired of hearing from me. But I am going to flash a ROM that has a over clock on it. I have a question tho. When I download the files. It unzips them. By that I mean I can open the folder and explore all of the files. Does this make it impossible to load that ROM? Thanks for your quick responses in advanced.
You dont want the file unzipped. Leave it zipped and put it on the root of SD card, that means just on the SD card, not in another file. Then reboot into recovery by powering phone off, then hold down the power button and the home button at the same time, keep them down until recovery comes on. If a white page comes up instead of recovery that says clear storage, pull battery and try again. Once in recovery you should see a few options. Nandroid, select this by clicking track ball while highlighted, this will back up your current system. After that choose install zip from SD card, then select the rom you loaded on SD card. After is says done, choose reboot system now. Then find Gapps 12-18-2010, I think those are the latest ones. Put them on root of SD like you did the rom and reboot into recovery the same way, choose the install zip from SD and select the Gapp file. Then reboot system amd you will set phone up with google like you did when it was new. You can then install one of the kernels linked for you, I recommend the 768 one, download OverClock Widget from the market and set it to 748, if your phone reboots for no reason lower that to 729, 710, wherever it becomes stable for you.
Okay, I did nandroid, I cleared everything, and I loaded the zip'd file ( I was trying to say earlier it is my mac's default action to un zip the file when it downloads. So I re compressed it. This might be attributing to my later problems) ANd then I rebooted. And it looks and behaves exactly the same as before.
Any pointers or ideas why it did this?
oefootball_70 said:
Okay, I did nandroid, I cleared everything, and I loaded the zip'd file ( I was trying to say earlier it is my mac's default action to un zip the file when it downloads. So I re compressed it. This might be attributing to my later problems) ANd then I rebooted. And it looks and behaves exactly the same as before.
Any pointers or ideas why it did this?
Click to expand...
Click to collapse
Since you re compressed it, it may need to be resigned before flashing. I could be wrong though
What does resigned mean?
ANybody have any idea why my ROMS arent loading at all?
Not quite sure if this will work on mac, you may need to find a XP pc to do this from. Here is a link to a zip signer though, http://forum.xda-developers.com/showthread.php?t=805766&highlight=zip+signer
Another thought...
Can you download the rom using the phone, then move file from download folder to root of SD card, using a file manager such as Astro or even better E Strongs File Explorer? I have read where some members have rooted, installed roms, kernels, theme, with no PC at all.
awesome idea on doing it from my phone. I didn't know it was a Mac problem. I can just run boot camp and boot up my mac with windows OS and try it on that. Thanks again.
Okay, i am trying to do it all from the phone. But the file is too large for the phones memory. And I can't figure out how to download righto the SD card. Any pointers here?
oefootball_70 said:
Okay, i am trying to do it all from the phone. But the file is too large for the phones memory. And I can't figure out how to download righto the SD card. Any pointers here?
Click to expand...
Click to collapse
That's weird it should. I have my applications checked to be installed to external memory but I don't know if that makes a difference or not. Mine go to sd
How would I click that option.
oefootball_70 said:
How would I click that option.
Click to expand...
Click to collapse
Ok what rom are you running again?
I just go to settings then cyanogenmod settings then application settings & it will let you choose
The factory ROM trying to get the first custom one loaded.
use the xda app and navigate to the thread that has the rom you want to install. from there click the link of the rom and it will go to SD card in a file called downloads. after completed plug phone into PC/mac and move that file/rom to root of SD card. Then reboot recovery and flash, done. There are literally 100+ threads on installing a rom, search, read, learn. What recovery do you have installed?
Okay downloading it to my Windows 7 bootcamp worked like a charm. I did the red dawn ROM. Isn't that one already over clocked?
oefootball_70 said:
Okay downloading it to my Windows 7 bootcamp worked like a charm. I did the red dawn ROM. Isn't that one already over clocked?
Click to expand...
Click to collapse
I believe it is, 710 maybe not to sure I have never ran it. There are faster smoother roms to run, why that one when we have Froyo for the Hero
i made an nandroid backup with amon ra 2.2.1 with sd-ext included and when i reboot, everything was gone, as if the data got wiped....
i see some broken apps so i geuss something happended with the ext partition
my sd-ext map is empty and i have this ext.tar in my nandroid map
wtf happened!?
shiyou,
You are having too many problems from the beginning. I posted some tips on your first thread, but never heard back. Also, a member recommended doing more research before going forward. The N1 is different from other phones as far as flashing roms.
I would recommend you do this assuming you have a working rom or working backup and sdcard backup. Depending what you have or don't have the below order may vary. Maybe someone can help us there:
1. Take your sd card out of phone--believe you said you have a backup--format it with sdformatter: http://panasonic.jp/support/global/cs/sd/download/sd_formatter20.html
You can dl manual also--mainly select full erase on and size adj on as format options.
Put your backup back on sdcard while still outside phone. Put card back in phone and boot into Amon recovery. Go thru the partition steps to get 1gb ext3 and 0swap.
At this point you need to have a working rom to boot into. If not other steps may be needed.
I use Titanium Backup to manage apps, the paid version. After I flash a new rom, I open TB, or get it from Market if not part of rom. Then I restore all apps with data. NOT system data. Then I delete any old rom apps and do a refresh and then backup all apps and data.
At some point you need to get rid of Rom manager and Clockwork and flash a fresh Amon_Ra 2.2.1 from his site: http://forum.xda-developers.com/showthread.php?t=611829 Before flashing make sure the install recovery file from old revovery is deleted thru Root Explorer, see this link: http://forum.xda-developers.com/showthread.php?p=9414097#post9414097. You don't have to use adb, just Root Explorer. Change permission first to R/W.
You can push the 2.2.1 .img after, downloading to root of sdcard, with Terminal Emulator using these commands:
Open TE and type:
SU
at # type flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img then hit enter. I usually check md5's with a file explorer. The recovery-RA-passion-v2.2.1.img part above should be the exact name of the img file you downloaded.
2. Before flashing an update to a rom wipe dalvik cache and cache in recovery
3. If flashing a new rom wipe Phone's System with Temasek's System Wipe zip 3X by flashing from recovery. It should be in your download folder.
http://forum.xda-developers.com/showthread.php?t=723844&page=1767
Then wipe Dalvik Cache and anything else that wasn't wiped with System Wipe zip 5X
4. You probably already know, but you can't restore a CWMod backup using Amon_RA or vice versa.
5. Read all the OP pages on the links I posted carefully
This is the way I been doing this for a long time--and rarely need any help or have problems. The system wipe is critical as old files can be left on phone even after a phone data wipe and flashing new rom.
Hope this helps and I haven't left anything out. Not a good typer. If I did--someone will correct me and some things are personal preference. But these have worked well for me.
BTW: If you have no good rom, you may want to dl the latest CM7 RC or nightly to pc and put it on sdcard after you format and put your sdcard backup from pc to phone. Then it is there to flash after card is ready and good recovery installed. You can always put the 2.2.1 on I mentioned after you get rest worked out. But, you gotta get off CWMod 3.0.
You should not use the beta Dark Tremor either, Would dl the the latest non beta.
Also, want the correct gapps for CM7 from OP page, and flashing order is rom/gapps/DT
Ken
I guess I was the member who recommended doing more research. So let me repeat:
I suggest leaving your phone alone and reading A LOT before you start doing something with it.
Yea, Sorry Jack
I was too lazy to go back and look--been a busy day and Fits is giving me a hard time on another thread
rugmankc said:
Yea, Sorry Jack
Click to expand...
Click to collapse
Nothing to be sorry for But indeed, I agreed with your point - someone who's looking for help rooting the phone and doing basic stuff for several days in a row, encountering a lot of problems, is most probably not ready for it, or not willing to read the guides.
You were right Jack on last thread. OP has now abandoned two threads he/she started and again asking for help on a CM7 thread.
No return to either with thanks and still looking for one magical answer, wondering why his phone don't work.
I gave enough advice for a dozen new users and over a year of flashing/backup expertise all in one post.
If he had done it right to begin with and followed some advice, he'd be running smooth. Card could be bad too, don't know.
I am done--
Ken
I love how you two are having this random conversation hahaha. Although I don't understand how the op did a nandroid backup and his phone wiped.. he mustve clicked wipe and confirmed it instead of nand backup. It's nearly impossible. I also decided (out of boredom) to look at his other thread.. Jack you said "Flash a new ROM, wipe your data, and try.
Repeat.
If the problems will still persist - they're in HW and you can't do anything about them." and what HE did: "i tried factory reset but didnt work..." lmfao you sir, are too nice jack! I'll give you two a thanks for the entertianment!
Well, rom development is slowing
Gotta do something
can't tell the same. 2 times i saved by nandroid due to bad flashing issue...
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