[Q] Could it be hacked to install another "recovery" partition and custom rom ?
I have bought a relatively cheap (not big brand) 1GHz due-core smartphone which runs Android 4.0.3. Recently, the SMS program crashes everytime I open it and I want to reflash the original Android 4.0.3 rom again. However, the manufacturer only flashes an Android 4.0 rom for my phone and serves me in a not-so-friendly way. They do not provide any information for the customers to reflash their Android roms themselves, and they also do not provide any information on rooting their phone. I have used the phone for just more than half a year and the phone's Android has crashed for 3 times.
I wonder is that any way that I could find out the hardware config of my smartphone and do some hacking to install some custom recovery and Android rom (e.g. Cyanogenmod) in the market. I do not want to depend on the manufacturer any more to accept their business manner.
Is there any suggestion or solution. Thanks a lot.
Lawrence
Related
my phone is running android 2.2.1. when i looked for cwm through rom manager it says there is official cwm for your device. is there any version of cwm which would work on all froyo devices?
This is by design not possible as we don't own iphones. Every android model is different by design, hardware and partitioning from each other.
Noteear sir/s,
First of all sorry to start this new thread as I don't know where and how to putup a question in the forums.(so as it is answered)
Second thing, i didn't get any resolution or satisfactory answer to some Qs previously asked.
Third one is that-- Every single person on this forum feels proud in calling a person noob.(May be he is a noob in this field but at his,
you are the one to be called an idiot<srry 4 using that word>)
Now to my problem..
I have a Fly F45Q handset running JB 4.2.1 Stock rom.
I'm a super user(rooted by motochopper method)
Removed bloatware from my smartphone
Titanium backup installed
Now the problem is that I want to make a full nandroid backup of my stock rom. Which is not possible(as I know till now) without custom recovery.
I installed rom toolbox pro and rom manager both of them doesn't support my device(I know it's hard for developers to come forward for each and every country specific device).
Neither CWM nor TWRP worked.
Now my Question is---
Is there any alternate for installing custom recovery on my smartphone
OR
Is there any other method for taking a full nandroid backup of my stock rom and flashing with it again as I play with my os files frequently..
NOTE:- I can provide every single information you require regarding my phone viz..kernel, build , cpu, gpu, hardware, display, etc..
Thanks...and waitin for early favorable replies..
Hi, is it possible to extract fully working installation of Android from one device and then install it to another? The devices are similar, but the another one is apparently having some issues because it cannot finish factory reset. No need to preserve data files (downloaded software, pictures etc.) but just restore the device to working condition.
Device has ATM7021 CPU, 512MB, 8GB, 10.1" display and Android 4.2.2. Model number is P706.
A device branded GD IPPO looks similar but these tablets I have are not branded.
Hi, I know that it's a post long time ago.
It's possible to do it by making a full nandroid backup of your device firmware if your device has a custom recovery installed.
Unfortunately, I haven't found any custom recovery for ATM7021a yet.
Anyone have any idea how to install CWM or TWRP on ATM7021A? Thanks In Advance.
Hi,
I'm new to ROMs with the Motorola Photon Q, but I have prior experience doing this with other Android devices. I'm also a longtime Linux guy, so "adb" and "adb shell" are both comfortable environments for me.
A few weeks ago my stock JB Photon Q reached a state where it would only reach the yellow "Sprint" screen during the boot process, and hang there. I fiddled a bit with the bootloader, but didn't get very far, and ordered a replacement used Photon Q. Unfortunately my newer phone came with ICS, and I when I attempt the builtin operating system JB update I encounter a message "Unfortunately, Motorola Services has stopped", followed by an indefinite "Checking for available update.* Please wait ..." So I've unlocked both phones, and began fiddling, while using the newer (ICS) one as my active phone for making phone calls, etc.
Fortunately on my older phone (the one that had the yellow screen) I've now been able to install the TWRP 2.7.1.2 Recovery, and I installed the September 26th version of the MoKee KitKat ROM, i.e. MK44.4-moto_msm8960_jbbl-140926-RELEASE.zip. In principle I'd rather use a blessed CyanogenMod version, but am concerned about some of the recent Wifi (and to a lesser extent, Bluetooth) problems that I've read about.
Overall, my primary goals are a stable environment and being able to store Amazon Prime DRM'd files on my SD card, symlink them from the primary storage, and be able to play them using the Amazon Music app. Thanks in advance for your recommendations regarding stable ROMs.
[ on my MoKee KitKat phone, the Amazon app is crashing on most of the DRM'd files that I downloaded from the Amazon Music app, even though I haven't moved them to the SD card or done anything tricky like that ]
My question now is: if I install the same TWRP recovery on my newer phone, will I then be able to install the stock JB image? I've researched to see whether TWRP 2.7 is backwards-compatible with JB ROMs, but haven't found the answer. It would be nice to use the same Recovery when trying out different ROMs, including both JB and KitKat.
Thanks ...
Yes, TWRP should be able to handle any appropriately formed .zip. Regardless of Android version.
Not sure if this really should be going to the noob friendly thread, but since it is a couple of questions covering various Android related issues, I figured that I will make it a separate thread after all.
1. Sometime updating an Android version would also end up updating the bootloader, at time rendering it impossible to downgrade again. Can this also happen in custom ROM (e.g. Lineage). I am asking this because I am thinking of custom ROM with newer Android version on my Galaxy S7, but may want to revert to a relatively old Android 7.0 after I am done testing.
2. Do file systems (the way application, application data are stored in the system and other information) etc. tend to stay the same as stock for a given Android version? For example between stock Android 7.1 and Lineage 14.1.
3. Same question as question 2., but between major Android versions (e.g. stock 7.1 and stock 8.0).
4. On rooted devices, can you usually update major version update without losing any data, and is it usually trouble free?
Feel free to skip reading this part, but for some background information, the reason I am asking all those questions is because one of the app I tried to restore via Titanium Backup and Swift Backup both failed. The application itself launches properly, but as soon as I restore the data, it would instantly crash and close. My guess is that this is probably caused by attempt to go from Android 6.0 to 11.0. Maybe it is the backup software or maybe something changed in the way files are stored, but whatever the reason, it just won't work.
So I am thinking that my best option is to try it to restore it on an Android 7.0 phone that I have (also on the way to be retired, and if it works, update to Android 8.0. Since Android 8.0 was the last officially released major version for that phone, and I was thinking that if it does work, perhaps I could alternatively go for an early Lineage ROM, then make gradual updates up to Android 11.0 and see if it helps the app remain unbroken. And then if it does work, perhaps I could then make a backup then restore it on the other new Android 11.0 phone that I have.
All in all, it is a silly amount of work to do just for one app.. but it is important to me, so I will exhaust every option that I can think of to find a solution.
Thanks!