So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
Related
Starting this thread again as my previous one was deleted during the board's transformation yesterday...but I think it's important to bring up the subject.
Coming from an older Android terminal (Htc Magic), I still don't understand how so few dev's out there are actually using ClockworkMod Recovery for their ROM. I know, a lot of you come from WM 6.5, where USB-Flash was the only way to go but now things have changed ! If you are fan enough of Android to be willing to flash it completely to the Nand, wiping WinMo6.5, then go with it and start flashing your ROMS the Android way. The CW way !
As a reminder, CW allows to :
- Flash your ROMS from the SD card. Imagine you want to flash a new ROM but have to leave for 2 days without a computer; it's not a problem ! Put it on the SD card and flash it later !
- Easily implement new kernels or updates. Doing so, dev's can propose completely clean build with the option to flash as many add-on's, updates, kernels or fixes you want. Look here : http://forum.xda-developers.com/showthread.php?t=810471. You can't make it easier.
- Partition your SD card with an ext partition the size you want without the need of a software or a linux-based iso. If you are a Windows user, that's a huge time saver !
- Back-up ans restore. That's a HUGE bonus. Want to flash a new ROM ? Back-up all your current ROM (5 minutes), then flash the new one. Don't like after all ? Restore your backup in 5 minutes...
- For me (and here, I'm not my saying it's always the case, just FOR ME), sd data transfer through CW is two times faster than through MAGLDR.
- Many more...
The same goes for EXT. Using data.img is outdated, it's another WinMo days leftover. Ext is actually mounted as an internal memory, allowing Sense Roms. And the apps installed there won't need to be reinstalled every updates...
It's tough for a Android user like myself to find a proper ROM/Zip with data2ext support these days. Pretty much MDJ, thank God for him. It seems that there a lot of ROMS to choose from but actually there isn't. Especially when the DAF to ZIP tool from the board doesn't work with all the DAF's releases (most of the time it's actually the releases that are not made right).
So please, be an Android user and make the step. It's like you found the door but are afraid to come in...
Just go and read the CW tutorial thread if you are unsure. I'll be willing to help also...
Hi,
This is my first time with android - that's why I'm trying SD.
All went ok for about 3 days - I tried many apps from the market & all of a sudden my phone rebooted!
When it booted again I saw the lock screen & can see the tiny icons on the status bar then it just reboot again!
After several attempts I got it booting but most of the apps now force close - my contacts are gone so as my SMS.
Any idea what might caused something like that? is Android so vulnerable that
installing some application can cause a total loss of the system?
- Do I need to re-install every thing again?
- will deleting data.img is enough to force a clean install?
- Is there a way to restore my old data from data.img?
- Is there a recommended book to upgrade from a noob to an educated user?
Thanks,
it's strange because when Americn android craches, it should bootloop.
here's a couple of suggestions:
backup the valuable contents of your SD card then search for file system errors, if your card has a corrupt file here and there it might be the one causing the problem, for the how to, it's in my troubleshooter, check my sig.
Usually a fresh data.img file is considered a clean install unless you've messed with root explorer (or any similar app) and did something wrong to your sytem files.
I'm not sure how to get the data back, I know you can access the data.img contents using a special tool, see here for info http://www.howtoforge.com/access-linux-partitions-from-windows
there's also a tool on softpedia to do so.
but you can try to look for the SMS data somewhere on your data.img, extract them to your harddrive, then copy them back using android explorer. I haven't tried it, and theoretically it might work, but I can not guarantee it.
My advice is that don't put too much pressure on the device, it's running Android from the SD which is not designed to work as NAND. let the device take a breath for a few seconds after each installation, it may say it finished, but it's still doing something in the background, I learned that the hard way. and always backup our data before you do something new.
and yes, if you use a fresh data.img you will have to install everything again.
So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
showlyshah said:
So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
Click to expand...
Click to collapse
good idea however there are SOOOO many variations of the files that would be needed, that basicaly it would be easier to consider what ever ROM you are using as the OMG_RECOVER.zip
Just my 2 cents.
Pvy
pvyParts said:
good idea however there are SOOOO many variations of the files that would be needed, that basicaly it would be easier to consider what ever ROM you are using as the OMG_RECOVER.zip
Just my 2 cents.
Pvy
Click to expand...
Click to collapse
mmmmm variables.... tasty
Before I get shut down for posting about a topic that has been posted before - I am doing this so others can access all the info in one place without having to scour the web/forum/posts.
Firstly let me point out a couple of important topics of discussion:
- You may just have a phone that has a hardware error. If you run through this post and options and you don't have any success, give some serious thought to getting it repaired because no matter how many new rom releases come out it isn't going to fix it.
- Full SELinux Support - If you use TWRP2 they have recently updated to 2.7.0.1 - It's worth reading through the 'Note' listed in the changelog. They talk about how Full SELinux Support is needed for installing Kit Kat roms and some of their older versions didn't support it. (http://teamw.in/project/twrp2)
- Rom and App settings - The Rom has several places to tick/untick screen rotation. Some apps also have screen rotation toggles. The important one is the Rom settings, make sure you have actually turned rotation on. It can be found in the notifications menu at the top of your screen (if you haven't removed it through customisation), also in Settings>Display> which is not to be confused with 'Smart rotation'.
- Smart Rotation - You do not need this turned on for screen rotation to work. In fact I would recommend leaving it turned off as it slows screen rotation down. I'll leave it up to you.
- Samsung Bloatware - There has been some talk on the forum about how removing Samsung apps has caused screen rotation to break. This is possible as several library files are shared. Since you are running a "custom" Rom it's hard to know whether any scripts have been included in the installation that haven't been specifically listed in a changelog.
- Model Vs Region Vs Solution - There are quite a few S4 models available at present. Most of these have hardware differences and the solution that worked for someone else may not work for you. It's good for you to start by learning what the differences are and what components were included in the version you purchased (this will save headaches later).
BACKUP YOUR DATA - I will not be held responsible for any actions you take with your device!
Ok, let's get started with the options/work arounds that you may wish to use and how they work (You will need to have root access):
1. ReInstall the Rom - This is the first place to start. You can usually install over the top of the initial installation without any issues. This would replace any data that may be corrupt from the installation. If you have installed a custom kernel it will install the one that comes with the Rom.
2. Clean install of the Rom - Sometimes we have to strip it all the way back to like-new. This means you would need to Factory Reset the phone (this will remove all apps and sign in data). If you wish to go all the way in cleaning off your device there is a Format option available in TWRP2 and PhilzTouch. Don't format unless you know what you're doing otherwise you could format the EFS data and then you're screwed. Don't say you haven't been warned.
3. a) Install a Library file (through recovery) - This is a script that has been built to replace a library file that is removed when you uninstall Samsung Hub. There is a discussion taking place in the Note3 forum where you can get the file. Be sure to follow their instructions exactly. http://forum.xda-developers.com/showthread.php?p=50099965
b) Install a Library file (through Android) - Using the same ScreenRotation.zip file you can download from the link above, open the zip and save 'libgnustl_shared.so'. You will need to put this file on your phone somewhere you can find it so you can copy it to the correct location and set some permissions. You need root access to even attempt this one, if you are unsure about what you're doing I would proceed with caution. It's not rocket science however you want to make sure that you don't alter any of the other files. You need to place libgnustl_shared.so into the \System\Lib folder. If the file is already there I would rename the old file rather than copying over the top. This just saves you in case anything else goes wrong and you need to go back a step. You need to change the permissions of the file before going anywhere. I used ES File Explorer to move the file and it allows simple change of the file permissions (through properties). It needs to be -rw-r--r-- or if you are using ES File Explorer then it should read Owner: Read & Write, Group: Read, Other: Read. You will then need to boot into recovery and wipe cache and davlik cache (don't confuse this with Wipe: Factory Reset).
4. Install a Stock Rom from YOUR phone provider - Telco's spend time and money ensuring their releases work with all the features of the phone, this is sometimes the reason why they take so long to update their software. Some of these features are Telco specific and others are region specific (hence my comment about being aware of what you have purchased). If you have installed a stock rom and you still have screen rotation issues it is likely (not guaranteed) that there is a hardware issue. In my experience installing a stock unmodified rom often addresses the issues that crop up on custom roms. It's worth testing it for a day or two on stock to ensure it's not intermittent. If you are willing to go to all the trouble you could try installing a custom rom again. I have has success in the past doing it this way. I can only assume that the installation of the stock rom addresses issues with internal components/firmware.
5. Kit Kat Roms - If you have loaded a bootloader that excludes you from installing your carriers stock rom (due to it being Jelly Bean or earlier), there are stock Kit Kat roms you can download in the forum. You won't have the added support of carrier addons and tweaks, however you will still get stock Samsung which is the next best thing.
What to do if none of the above work?
There are two options 1. Send it off for repair 2. Continue to work on it yourself with the help of others on the forum.
If you wish to continue working on it yourself or you have voided your warranty here are some tools to help. You need to take a look at whether your accelerometer is working - This is indicative only (an indicator) and will help you narrow the problem down.
1. In your dialer (phone) put in the following *#0*#
This will allow you to go in and see how the components are responding - You want to take a look at Sensors.
2. Accelerometer Monitor/Test Applications
There are quite a few for free on the market place - They will show you how the X, Y & Z axis are responding to the movement of the phone. Sometimes it is quite obvious when certain axis are not responding at all. Some of these applications will allow you to calibrate the sensors. I am not 100% sure whether these calibration options will work on Kit Kat. If you are speaking with a developer of a custom rom they will often query you for log data, this is code that will help them work out what is going wrong. This doesn't guarantee they will be able to fix it. Not all of the accelerometer apps provide a log but is necessary information you'll need if you decide to go down that path.
(AndroSensor is relatively good - https://play.google.com/store/apps/details?id=com.fivasim.androsensor)
Let me know how you go.
I feel like you could clean flash, boot and set the ROM up, then reboot to recovery and restore the data partition and be good to go. Could it really be that simple?
Not sure how I've been an Android user for so long and I don't know the answer to this question. Any flack I get is hella deserved with this one, lol.
They must be based on the same romlike aosp,cm,oxy and so on
And even when you're switching to another ROM with same base, risks are high that there's some incompatible data layout between the ROMs datastore which will create interesting bugs (different layouts in configuration files and folder structures and so on)
I tried that when started messing with my phone, It sometimes works but with errors and apps no starting in my case. There are some apps that create a zip flashable of your apps which is safer to do.