Related
n00b, but not an idiot here. been playing with handhelds for many years, new to android though.
I've been watching this forum (CDMA Hero sect.) since I got my Hero, been learning quite a bit. Held off on rooting until there was a official 2.1 release for the device that a ROM could be built around (I wanted full function of the phone and software), did the stupid thing of running the RUU (leaked official), and had to wait until Regaw (thanx!) gave us root...
It would seem the tone of this forum has changed fundamentally since the release of the EVO and an official 2.1 for our Heros. I can understand that perhaps the "thrill" is gone, and since we can all get 2.1 now without rooting, I guess it's "why bother"? (see questions below)
Aaaaanyway...
just did my first root, my first nandroid BU, my first rom flash (hated the rom), and then my first nandroid recover ;-) (what an amazing function, what a relief!) About to try out a 2nd ROM, see if I like it better...
(as an aside to the point of this post, the ROM i tried was DamageR, found it too "messy" for my tastes, and while I can appreciate the work put into it, the options it offers... not my style. was thinking on Damageless, waiting for a "rerelease" of his final. Or perhaps the Aloysius...)
Now that I have my caveats and excuses out of the way, I had a few n00b questions?
1) while I think I have figured out what JIT is, why is it "enabled" in many new ROMs? Is it not an included part of Sense 2.1 from HTC on the Hero?
2) When I was wiping before flash, I was unable to wipe davlik (sp?), insisted I had to do through adb. Is this "normal"?
3) could someone explain what "push" an APK is? Since I have rooted, will I be unable to use the application installer in the HTCsync? (haven't actually tried yet...) And how to "flash" a file? (Example: Dammageless' LWP fix...) I am sure it's something very simple that I am just not getting dues to being unfamiliar with the jargon here.
4) I would really like to use the A2SD feature, and in the recovery screen (where one does the nandroid BUs) it gives me the option to create partitions. I was of course clever enough to BU all data on the card before doing Anything re: root/flashing/etc, but I would like to know if this was needed? Will it just use empty space already present on the card? And in general, I would love to know what I am doing re: A2SD in general, I know "search is my friend", but would someone point me to a quick and succinct link to the "instructions" of doing this? And the different kinds of partitions (ext2? ext3?ext4? huh? why?) I need to know about?
5) And, so why bother rooting now? I know this sounds like a dense question, but really since I don't know enough about it, I guess I am looking for a list of "the obvious reasons" that would not occur to me, or other Android nooblets. LWP will be nice i guess, other launchers, A2SD, bootscreens, OCing... what else?
5) Personally, I am hoping people will rise to the Froyo challenge. While being ignorant of most things involving "programing", or compiling (cooking?), my understanding is that 2.2 runs several times faster due to (a new?) JIT (admitted ignorance again), so does this mean "more efficient"? Would something like a Hero be able to take advantage of that? I realize that we (due to CPU) will never have the highend features (OpenGL, gaming, LWPs being sluggish), so please correct me if I am grossly missing something, besides it not being written for this HW, I see that many other versions written for other devices have been ported to this device.... is this being actively worked on, seen a worthy challenge? Or even a possible one? One that has any benefits?
7) And the n00best question of them all: ROM suggestions? I happen to like Sense, or thought I did because of the 7 screens and other neato features in the UI, but it seems from further reading I can get most features and function out of just about any of them... As an example, what will I gain from flashing Damageless as opposed to the stock RUU? (While Damageless' ROM seems to be the most popular, it is also the least described in his post re: features added/removed, and it's benifits. It would seem like his ROM was "da bomb" when we didnt have 2.1 officially, but since we do now... do I bother with his? Or move to something "more exciting"?
Thank you for your patience.
/n00b-rant
1) JIT just speeds up the phone a bit, although, it's incompatible with Sense :\
2) Don't worry about the dalvik cache unless you're getting problems with booting up a new ROM
3) Push = copying a file to the device (usually when you're putting an .apk in the /system/app/ directory) And about HTCsync? I've never used it before, but it probably wouldn't hurt to try.
4) A2SD? I suggest you back up the files on your sd card before trying anything with it, also, make sure it's a fast card.
5) Rooting? To get rid of annoying sprint bloatware, overclocking, Wi-Fi Tether, etc.
5b) It'll be a little while before we get a stable FroYo (when they release the source, the work will begin)
7) I was about to suggest DarchDroid, but seeing as you like sense.....
(although, 7 homescreens? That's available in just about every homescreen app on the market, my favorite being LauncherPro Beta)
1. The JIT leak we have is buggy at best, and Force close city at worst, but is supposed to be fully featured in 2.2
2. What version of recovery are you running?
3. You can still use the HTCSync installer, but to push system files, you need to use ADB (Google "Android SDK"). You flash a file the same way you flash a ROM, always nandroid backup.
4. A2SD is only really helpful if you have a Class 6 SDcard, and can be hurtful otherwise. A2SD requires a portion of the SDCard to be formated as EXT, so say you have a 1GB SDcard.
256MB EXT (Space for apps)
0MB Swap (basically, "RAM" on your SDCard)
The rest as FAT. In a file manager and you phone, your SDcard will only appear to be ~760MB, as 256 is taken up by EXT.
5. Being able to completly customize everything, getting day by day support to fix bugs instead of waiting on Sprint/HTC, Basically, rooting is what makes your phone YOUR phone.
6. 2.2 is currently available in a very basic install, and will be developed further when the source code is released. Yes, the new JIT is supposedly 450% faster, by being more efficient with how it handles everything, and theorhetically with it, we can expect to see performance increases in everything.
7. I'm a personal fan of DarchDroid, it lacks Sense but he's incorporating ADWLauncher into his next release (Google it, it's amazing.) Damageless is also no longer developing his ROM as the Evo is out. Same thing with Flipz.
Anything else?
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
A Noobs Guide to Getting Started with a Custom Rom on the Nook Color
So you heard about the nook color. How it's a cheap e-reader that can be pushed to the limit and you are wondering how you can enable this power for yourself. Well you came to the right place!
Table of Contents
1. Why you should NOT use Honeycomb
2. SD or Internal instal
a. SD install
b. internal install
3. Restoring to Stock
4. Other Cool Stuff
5.Issues
6. Conclusion
7. Changelog (Last update 1/10/12)
1. Why you should NOT use Honeycomb
So you've heard about how the Nook Color can run Honeycomb and you are thinking that you want to try it. I mean why not? It's a tablet OS and the Nook is supposed to be turned into a tablet right? Well here's how it is. Honeycomb unlike other versions of Android is not an open source release. That means that developers cannot see how it works and have to reverse engineer basically the entire thing. This leaves you will something that barley runt because of countless missing drivers and many bugs from the SDK simulator. Honeycomb is a very painful and unstable experience. Do not use it. Wait for the next version of Android codename Ice Cream Sandwich to come out. For now use CM7. To check on the progress of CM9 (AKA ICS) check out this thread where you can find the first alpha builds.
2. SD or Internal install
The first decision you need to make is if you want to install CM7 (Android) over your current stock firmware or to run from an SD card.
a. SD Install
The benefit of running from an SD card is that you get to keep your Nook's current stock rom along side your Android install. The downside is that Android will run terribly if you do not use the correct SD card.
When running from an SD card use ONLY a SANDISK CLASS 2 or 4!
Take a look at this thread here for why you need to use a Sandisk:
Instructions for installing to an SD card
b. Internal Install
I recommend you do an internal install just because it is more stable and a lot easier to troubleshoot and upgrade to a newer CM version. If you ever need to return to stock it is very easy (see part 3).
To install to your internal memory follow this guide
Remember if you have a newer Nook that came with stock version 1.2 or above you may want to follow the repartitioning instructions here to have more space available to save files.
3. Restoring to Stock
So something happened and you need to return to stock. You need to make a warranty claim, register you device with BN, or whatever.
Here is what you need to do
When you are done you will have a complete stock Nook to do whatever you want with.
4. Other Cool Stuff
Watch Hulu with a hacked flash app
Make your Nook more Honeycomb like with TransformerBread
5. Issues
Help Facebook keeps force closing!!!!!
Solutions:
1. Use Facebook 1.6 or lower
2. Use tetherGPS lite
3. Use a third party app
Use this thread for help
N64oid won't work!!!!
Starting with N64oid 2.0 and above the new .32 Nook kernel used in CM7 does not work with N64oid.
Solutions:
Use a version of N64oid before 2.0
Use an older version of CM7 without the .32 kernel
Use this thread for help:
6. Conclusion
I hope this guide helped you out. If you think there is anything I should add or you have any questions feel free to comment.
7. Changelog
1/14/11
Restoring to stock guide updated for 1.4.1 zip that will work for people with new touchscreens.
1/10/12
New Guide for restoring to Stock that uses 1.3 and the new clockwork to work on the newer blue dot Nooks.
Removed 1.2 zip as it is no longer needed
Removed "Guide" from Changelog
Changed "Guide Changes" to Changelog in Table of Contents
Added link to CM9 dev thread
12/23/11
Added 1.2 restore zip link
Added Conclusion to table of contents
Good work, kookid,
Comment on 2.b. about re-partition. It is an option, not a must so saying "you need to follow ...." might confuse others.
votinh said:
Good work, kookid,
Comment on 2.b. about re-partition. It is an option, not a must so saying "you need to follow ...." might confuse others.
Click to expand...
Click to collapse
Oh good point. Will change.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Good overview for newcomers.
Will return here when I get my NC in November.
Two thumbs up, maybe this should get stickied.
What about overclocking/undervolting kernels?
OrganizedFellow said:
What about overclocking/undervolting kernels?
Click to expand...
Click to collapse
Overclock/undervolt is included in the CM7.1 kernel.
Overclocking is built in to the CM settings. To undervolt you need to use the Nook Tweaks app.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
BASIC! said:
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
Click to expand...
Click to collapse
Could you at least post the name of the thread? I'm always looking for better ways to do things.
---------------------------------
Sent from my LG Optimus V using Tapatalk
BASIC! said:
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
Click to expand...
Click to collapse
Link provided by koolkid was for 1.0.1 but I think it was the standard procedure for any other version.
I'm eager to learn a new, better way.
I just substitute the full 1.3 .zip for the CM7 and gaaps .zips when booting with the original install image and it works fine. I recommend everyone who installs CM7 to the eMMC save their original install SD card for future needs and buy a 2nd one for use with CM7. The 1.3 .zip now seems to be missing from the drop box site though so someone will need to repost it. It was linked in this thread: http://forum.xda-developers.com/showthread.php?t=914690&page=29
Thanks for a very useful thread ... even though I already have mine running on CM7 since last month, really grateful for the info regarding the Facebook FC.
I'm still very much a noob at this.
One suggestion for more info regarding an issue which many noobs like me may have: How to expand the partition to use the rest of the SD card. On my 16Gb card, it now has four partitions: Boot, 2x unallocated, and Storage. Using EASUS PartitionMaster, how do I expand the fourth partition ? Do I have to delete the two unallocated ? Any further info regarding this would be very much appreciated !!
If I use App2SD, which partition would those programs go to ? Seeing that I already booted from SD, the Apps are already on the SD, right ? No need to "move to SD" ?
Thanks ahead for the schooling !!
vn33 said:
Thanks for a very useful thread ... even though I already have mine running on CM7 since last month, really grateful for the info regarding the Facebook FC.
I'm still very much a noob at this.
One suggestion for more info regarding an issue which many noobs like me may have: How to expand the partition to use the rest of the SD card. On my 16Gb card, it now has four partitions: Boot, 2x unallocated, and Storage. Using EASUS PartitionMaster, how do I expand the fourth partition ? Do I have to delete the two unallocated ? Any further info regarding this would be very much appreciated !!
If I use App2SD, which partition would those programs go to ? Seeing that I already booted from SD, the Apps are already on the SD, right ? No need to "move to SD" ?
Thanks ahead for the schooling !!
Click to expand...
Click to collapse
For your first question: just right click the 4th partition, select resize and then make sure everything is selected.
For your 2nd question: I'm not exactly sure as I do not use an SD install. Maybe someone else with more SD booting experience can help but what I am thinking is that all of your apps are on the 2nd or 3rd partition but when you use app2SD they get moved to the 4th partition.
---------------------------------
Sent from my LG Optimus V using Tapatalk
votinh said:
Link provided by koolkid was for 1.0.1 but I think it was the standard procedure for any other version.
I'm eager to learn a new, better way.
Click to expand...
Click to collapse
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
BASIC! said:
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
Click to expand...
Click to collapse
Unfortunately you cannot use the 8 failed boot method if you replace the stock recovery which most do when installing CM. That is why I used the method I did with this guide. It works no matter what is on your internal memory.
---------------------------------
Sent from my LG Optimus V using Tapatalk
BASIC! said:
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
Click to expand...
Click to collapse
I'm probably slow but your provided link is for rooting the 1.2/1.3 NC using ManualNooter. It has nothing to do with reverse back to stock ROM.
And, the complete wipe near the bottom of the first post, again, has nothing to do with reversing if currently running custom ROM on eMMC.
A mod should definitely sticky this...most helpful thread I've read in the general forum yet.
Thank you so much
I just got a refurbished Nook Color and after hours of searching and reading I came across your post. This guide is a like a mother-load of good links and clear instructions. Thank you for taking the time to put it together. It has really helped me understand what was needed to get my NC up and running.
This is a really helpful guide for beginner.
I want to ask some thing about the whole workflow. I've used other Android phones to play with rooting and flashing new roms, but NC is quite new to me. So still need to make sure about something.
In this guide, there is nothing about rooting. And when I use CM7 from a SD card, I don't have to do that and already got the su in terminal. So I suppose if I just flash CM onto the eMMC, I'll get root access anyway. I don't have to root it right now in its stock system, right?
-Updated the Restoring to stock guide to use a 1.3 and the newest clockwork it's on Android Central for now but I might move it over here if I get some time.
zhourj said:
This is a really helpful guide for beginner.
I want to ask some thing about the whole workflow. I've used other Android phones to play with rooting and flashing new roms, but NC is quite new to me. So still need to make sure about something.
In this guide, there is nothing about rooting. And when I use CM7 from a SD card, I don't have to do that and already got the su in terminal. So I suppose if I just flash CM onto the eMMC, I'll get root access anyway. I don't have to root it right now in its stock system, right?
Click to expand...
Click to collapse
Nope, no need to root if you are going to flash CM7 because of the ability to boot a custom recovery from an SD card.
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
Hi everybody,
hopefully someone here can answer a few questions for me.
I have a Samsung Galaxy 3 mini.
android version 4.4.2
kernel version 3.4.0-1670137
baseband version g730aucubng4
my service provider is AT&T
what I want to do is pretty simple, or so I thought.
I read this article ( https://www.androidpit.com/galaxy-s3-note2-memory-bump) about swapping your phone's internal and external storage so the thing doesn't get so full of apps etc. it runs like crap.
I thought "hey, I haven't rooted my phone yet for fear of loosing stuff, but it's old and slow and if it's that easy, why not"
I rooted it using kingo-root, but decided to use o-nandroid backup to create a backup before I did anything. I fallowed these instructions (http://forum.xda-developers.com/showthread.php?t=1620255/) but during the process of flashing the zip file I got a failure message and managed to wipe my memory loosing everything that wasn't on the external sd card.
anyway, to make a long story short, after 4 days of messing with different apps and trying, unsuccessfully, to do various tasks (mainly dealing with creating backups. using twrp, cwm, titanium backup) I think I've discovered the problem.
contrary to what I had read, my android device's boot-loader was not unlocked, or in fact unlockable.
I finally managed to create a backup using Safestrap. but now to my question.
with my bootloader locked, and working through Safestrap, is it possible to use something like the 11extsd2internalsd file from that first article to swap my two hard drives? or am I stuck, since I can't install new kirnels?
--now, someone is bound to say "hey, you should have searched xyz, there is a thread there about this exact thing". I thought I'd respond to that now and save them the trouble. I have spent the past 5 hours searching, googleing, and reading articles about this. so far, I have learned a lot, but I'm tired and quite frustrated with the whole endeavor.
so I thought I would try asking the experts if it's even possible to do what I originally wanted to do, or if I should just delete all these apps, unroot my phone and go back to deleting my pictures and text messages every other day to save space.
Thanks for having the patiance to read through my tale of woes, hopefully someone will be able to help me out and answer my question.
JM
You can swap internal storage with external SD by editing fstab.<device_name>.
Look, here is this file for my phone (yours will be little different) https://github.com/TeamCanjica/andr...dina/blob/cm-11.0/rootdir/fstab.samsungcodina
Just swap in places this code "voldmanaged=sdcard0"/"voldmanaged=sdcard1"
This file you can edit only after unpacking and repacking boot.img (you need to get ramdisk filesystem, more info and how to http://forum.xda-developers.com/showthread.php?t=2036528).
For flashing boot.img (kernel) after making changes, your device must be rooted (minimum this) or have custom recovery which will let you flash zip package.
As I know, last step is to edit from /system/etc/permissions/platform.xml one line (more info http://trendblog.net/fix-kitkat-sd-card-write-restriction/ )