Related
This thread is dedicated to hacking and development of the Sharp SH7218u. This is an Android phone with a somewhat unique clamshell form-factor.
Before proceeding, please note that all of the usual warnings apply. The software and techniques described here have the potential to break your device and make it unusable. By using the software and following these techniques you run the risk of bricking your phone. I take no responsibility if this happens - proceed at your own risk.
First, some credits for the work of others:
Z4root:
Developed by xda member RyanZA.
http://forum.xda-developers.com/showthread.php?t=833953
SH7218u Clockworkmod Recovery:
Clockworkmod original developer is Koushik Dutta:
www.clockworkmod.com
Dialer2:
Original developer of now open source dialer is dnaq Productions:
http://dnaq.tumblr.com/
Initial hacking and development work:
Gigi Tse is credited for early and ongoing work for the SH7218u:
http://gigitse.com/
http://www.msharp.cn/forum/t390991/page1/
Now on the instructions....
-------------------
Rooting Your Phone, Installing Clockworkmod Recovery, and Installing Google Apps
Gather the Required Files:
1. Go to the z4root xda thread, login in and download z4root.1.3.0.apk:
http://forum.xda-developers.com/showthread.php?t=833953
2. Download SH7218u_recovery.apk:
(attached below)
3. Download the Clockworkmod recovery flashable Google Apps file from the following site:
http://goo-inside.me/gapps
In the table, you want to select the HDPI, CyanogenMod 6 version. The file that you download should be
called 'gapps-hdpi-20101114-signed.zip'
4. Place these three files on your micro-SD card and insert the card into your phone.
Root Your Phone
1. Boot up your phone and skip the system setup wizard. Go to the app drawer and run 'Settings'.
2. Select 'Applications', and enable 'Unknown sources'.
3. Select 'Development', and enable 'USB debugging'.
4. Exit back out to your home screen launcher, then go to the app drawer and run 'ES File Explorer'.
5. The file explorer should show you the contents of your sd card. Tap on the file 'z4root.1.3.0.apk'.
6. Confirm installation of z4root, and when this is complete select 'Open' to run the app.
7. From within z4root, press the 'Permanent Root' button.
8. Wait until this process is complete, and the phone will reboot by itself. It can take 30 seconds or so for this to happen, so be patient. You are now rooted.
Flash Clockworkmod Recovery Image
You must be rooted for this to work. Do this after you have successfully completed the rooting process above. Also please note that this is not the CWM recovery image developed by Gigi Tse. Her image contains CWM version 3.0.2.4. This is my recovery image and contains CWM version 5.0.2.8.
1. Open the app drawer and run 'ES File Explorer'.
2. Tap on the file 'SH7218u_recovery.apk'.
3. Confirm installation and run the application by selecting 'Open' once installation is complete.
4. On startup, the application will request Superuser privleges - press 'Accept' to allow this.
5. Press the 'Flash Clockworkmod Recovery' button.
6. Wait a few seconds until you see the confirmation message 'Recovery Flash Complete'.
7. Exit out of the application. You now have Clockworkmod as your recovery. You can uninstall the SH7218u_recovery app if you wish as you have no further use of it.
Note for users of Link2SD: This version of Clockworkmod recovery will perform backup and restore operations on the secondary SD card partition used by Link2SD. However, that partition must be formatted in the ext3 filesystem for this to work. Formatting the partition in any other filesystem (e.g. ext2, fat32, ext4, etc.), will result in failure to mount and backup the partition. An SD card can be prepared for use with Link2SD from within this version of Clockworkmod recovery by using the 'Partition SD Card' feature within the 'Advanced' menu.
Install Google Apps
1. Boot into Clockworkmod Recovery. This is done by powering down your phone, then turning it back on by pressing and holding down the number 3 and 6 buttons together, then pressing and releasing the power button. Continue to hold the number 3 and 6 buttons until you see the Clockworkmod screen.
2. Select 'install zip from sdcard' from the menu.
3. Select 'choose zip from sdcard' from the next menu.
4. The next menu will be the contents of your sdcard. Select the Google Apps file - 'gapps-hdpi-20101114-signed.zip'.
5. Confirm the installation and wait until it is complete.
6. Press the back button once to get back to the main screen and select 'reboot system now'. You now have Google Apps installed.
When you reboot the device, you will be taken through the Google account setup. Please note that in order for contacts applications to work with Google synchronization, you will need to install a modified contact editor. The stock firmware on this phone is not intended to sync with the Google servers as it was intended for Chinese users. The modified contact editor fixes this issue. It is free and available from the Market. Look for 'Contact Editor Free' by a developer named 'dmfs'.
Deleted
Deleted
Thank you! Very good job!
No ideas how to get the phone to answer a call when you open?
TabletGuru said:
Thank you! Very good job!
No ideas how to get the phone to answer a call when you open?
Click to expand...
Click to collapse
Hey someone read my thread!!
Sorry, no posts on this thread yet and it has been up for a while. I think most people who have this phone stick to Howard forums or other such sites that cater to the phone type and its region of origin.
As for your question, no...but I have tried. That would require a modification of the phone app or a change to the OS itself as the phone app is the active app when the phone is ringing and the device is opened. If I had the source code for the stock phone app, this would be a fairly easy thing to do. Unfortunately, I have been unable to find the source for the stock device firmware anywhere. I tried compiling a generic Froyo phone app from the Google source, but of course this did not work. This is a somewhat special app that needs to interface with several parts of the device's hardware, so a generic version just doesn't work. Unless Sharp releases the full source code for the stock firmware, I don't think this is going to be possible....at least not from someone with my somewhat limited development abilities.
Sent from my MB855 using xda premium
Google Play
Hey xdajunkman, amazing work you are doing here.
Have you considered adding Google Play to the mix? I was able to get the latest version working just fine on my SH7218u.
How hard would it be to hack the light notifications area of the phone, to make some of the notifications last for 1-2 seconds longer?
I should also add that my phone is giving some really flaky GPS information. It is putting me somewhere in the ocean near China unless I use wifi only. Do you have any experience with this?
EDIT: I don't know why, but the dialer is not working for me with regard to the long-press of the delete key and silent (#) key. No idea why...
EDIT2: It is because I had another keyboard installed; which must do something funky... switching back to a default keyboard and then trying seemed to work!
Thanks for your guide! Do you have got new version Rom? 2.3 or 2.3.5?
johnny8384 said:
Thanks for your guide! Do you have got new version Rom? 2.3 or 2.3.5?
Click to expand...
Click to collapse
Not likely to come. This would mean building something like CM7 for a new device from scratch. This kind of task takes dozens of man-hours for an expert developer, and that assumes that they have access to the original source for the release build. We do not have the original source, and there is no such developer working on this device. We will be stuck with Froyo.
Thank you so much for taking the time to write a guide xdajunkman!
I received my SH7218u today and did everything. The instructions were clear and the whole process took no more than 30 minutes.
Surprisingly, my SH7218u accepts 64 microsd card (after you format it).
Is it ok to have 2 partitions?
One is a ext2, and the other I just created using clockwork mod ext3...
I'm wanting to use that custom rom..
EDIT: clockwork mod Repartitioned my ext2 to ext3 now ಠ_ಠ
and all my apps are "installed"
Going to make a backup rom now.. and then Install xdajunkman's custom rom >__<
EDIT: Ok succesfully installed the Custom rom It looks great I might say awesome work xdajunkman
Ok the question is now.. how to I get back all my previous apps and stuff?
I followed the guide and made a backup already
My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps ( don't remember exactly) what i've to do now? plz help me
P/S: My english sucks, sorry for that
delpan said:
My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps ( don't remember exactly) what i've to do now? plz help me
P/S: My english sucks, sorry for that
Click to expand...
Click to collapse
Boot into clockwork mod by pressing 3and 6 and the power on button, (assuming you have that installed)
Reinstall the rom.. http://forum.xda-developers.com/showthread.php?p=22106340#post22106340
sirjoe1 said:
EDIT: Ok succesfully installed the Custom rom It looks great I might say awesome work xdajunkman
Ok the question is now.. how to I get back all my previous apps and stuff?
I followed the guide and made a backup already
Click to expand...
Click to collapse
It is usually just easier if you wait until you have the new ROM installed before you try and install your apps. There is no reliable way from within CWM to restore your installed apps.
However, because the new ROM is just a modified version of the stock ROM, it should be possible to flash the new ROM without wiping the existing user data and keeping your installed apps. Restore your backup that has all of your apps installed. Then, flash the modified ROM but skip the step in the instructions that tells you to wipe existing user data. Instead of wiping the user data, do the following:
1. In the 'mounts and storage' menu of CWM recovery, select to format both '/system' and '/cache'
2. In the 'advanced' menu of CWM, select 'Wipe Dalvik cache'
Now proceed with installing the ROM as per the instructions. This should result in the modified ROM being installed, but all of your installed apps should be protected.
If this does not work, then you will just have to re-installed the modified ROM according to the instructions (including wiping the existing user data), then re-install all of your apps. For future reference, a great app called Titanium Backup will allow you to backup your apps and restore them after changing the ROM.
sirjoe1 said:
-->My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps
-->( don't remember exactly) what i've to do now? plz help me
Boot into clockwork mod by pressing 3and 6 and the power on button, (assuming you have that installed)
Reinstall the rom.. http://forum.xda-developers.com/showthread.php?p=22106340#post22106340
Click to expand...
Click to collapse
Agree with sirjoe1. Hopefully you flashed CWM as your recovery before you did this. However, if not then booting into recovery mode as described above should trigger a factory reset from the stock recovery partition. I have not attempted this myself with the stock recovery, but usually what this will do is simply return your device to it's stock state. You can then start over using the instructions in the OP....but without deleting critical system apps this time.
Hello again, I've a question, has anyone successfully Overclocked the cpu frequency on this phone using setcpu or similar apps?
Overclocking not possible without either a custom kernel or a kernel module of some sort. As the source for the stock kernel was never released, such a thing would be a HUGE undertaking. Very unlikely to ever happen.
xdajunkman said:
Overclocking not possible without either a custom kernel or a kernel module of some sort. As the source for the stock kernel was never released, such a thing would be a HUGE undertaking. Very unlikely to ever happen.
Click to expand...
Click to collapse
Oh darn, that's such a downer..
These sh7218u threads are so dead nowadays :/
I might have messed up my phone -_- (again)
I went into the /data/sdext2/dalvik-cache and deleted everything and now a few apps have gone missing, and some won't work, they just give me a force close error >___<
I also lost my go launcher ex settings..
and to make things worse.... my internal memory went to 0% free... deleted a few things to clear up 8mb..
Any Ideas how to fix this ? @[email protected]
[Can you guys play 480p videos?
I can't.. 360p runs fine though..]
I am hoping to get this device this week.
Thanks for your tutorial, and I will let you know if it runs out just fine
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
theonyxphoenix said:
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
Click to expand...
Click to collapse
Go into the settings of ES file explorer and check everything under root settings. The only folder you want to get rid of is the Apps in the vendor folder. Anything else can harm the system. I just used the cut feature on the apps folder and pasted it to my sd card to make sure it worked first. Good Luck!
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
theonyxphoenix said:
. then switch to boot in parent mode, .
Click to expand...
Click to collapse
how ?
theonyxphoenix said:
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
Click to expand...
Click to collapse
Guess I missed something and should've read better, how did you set it to boot only into parent mode.
Sent from my SAMSUNG-SGH-I957 using xda premium
theonyxphoenix said:
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
Click to expand...
Click to collapse
How do you set it to boot into parent mode?
byohaserd said:
How do you set it to boot into parent mode?
Click to expand...
Click to collapse
Did you try going to settings -Security - put a TIC in " Set Parent Mode as default mode " ?
---------- Post added at 07:15 AM ---------- Previous post was at 07:07 AM ----------
ALSO
I found no need to delete the vender/apps folder as it can be used to help get rid of "Android is upgrading ' message after each boot up that seem to come when you install apps from play store
---------- Post added at 07:28 AM ---------- Previous post was at 07:15 AM ----------
theonyxphoenix said:
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
Click to expand...
Click to collapse
I used TWRP to do anything - rooted or unrooted you can make change as you wish .
when you are in TWRP mount system then use advanced and file manager
hope this helps
I did not see that until you mentioned it...thanks
I was able to get it to work by going into a startup manager and freezing kidsmode2 and nabimode. I erased the apps folder though cause I wanted the space freed up.
Sent from my NABI2-NV7A using xda app-developers app
I deleted some files I shouldn't have. My nabi 2 keeps rebooting. It goes from the start up screen to "Android is upgrading..." Then back to the start up screen, then again. When I try to go to "Recovery Kernel" I get the Android laying down with the Red triangle over his chest..any suggestions?
Rest to Factory setting
mikewhit001 said:
I deleted some files I shouldn't have. My nabi 2 keeps rebooting. It goes from the start up screen to "Android is upgrading..." Then back to the start up screen, then again. When I try to go to "Recovery Kernel" I get the Android laying down with the Red triangle over his chest..any suggestions?
Click to expand...
Click to collapse
1-switch off.
2-press power button & vol + together.
3-press vol - to go to recovery kernel and press vol + to select it.
3-android model should come lying down with red triangle!.
4-press vol - & vol + together.
5-select the system reset and press power button.
6-after that switch off and on with all new factory settings.
Best Regards.
Eric Karz said:
ALSO
I found no need to delete the vender/apps folder as it can be used to help get rid of "Android is upgrading ' message after each boot up that seem to come when you install apps from play store
Click to expand...
Click to collapse
I created a new gapps package that does away with the upgrading message on every boot.
http://forum.xda-developers.com/showpost.php?p=35887804&postcount=1
Nabi 2 Charge/Reboot problem
t499user said:
I created a new gapps package that does away with the upgrading message on every boot.
http://forum.xda-developers.com/showpost.php?p=35887804&postcount=1
Click to expand...
Click to collapse
Completed the OTA to 1.9.37, root, and gapps install - had the upgrading message on every boot but fixed that with the new gapps package (thanks a lot to all the great developers on this forum!)
However I still have a problem since the root process that I haven't seen addressed so far after searching the forums.
After my putting the Nabi 2 to sleep and plugging in the charger, it will fully charge and turn the battery light green as it should, shortly after that the device then powers off and requires a reboot/cold start vs. just a quick click of the power button to return from sleep mode. It does reboot fine and has a full charge - all other operations are normal.
Any suggestions on how to eliminate this power down/reboot after charging?
Thanks!
I flashed your package but the android upgrading still shows up for me,only for a few secs and it seems as if no programs get upgraded...what are your thoughts on this? How can I find the stray files that are causeing this?
Sent from my NABI2-NV7A using xda app-developers app
stuck in TWRP
My tablet only boots in TWRP v2.2.2.1
I've flashed at least 5 different images in fastboot using at least 5 different methods. Every time I think I make any progress, I reboot my nabi2 and it reboots directly to TWRP. Any advice would be greatly appreciated.
mikewhit001 said:
My tablet only boots in TWRP v2.2.2.1
I've flashed at least 5 different images in fastboot using at least 5 different methods. Every time I think I make any progress, I reboot my nabi2 and it reboots directly to TWRP. Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to flash a backup of 1.9.37 or just a program thru install? I know that if you wipe system and then flash another backup, if the backup is no good, twrp will not boot system but go right back to twrp. That is a safety setting, cause if it booted with no system installed you would most likely have a bricked device. That happened in the early days of Twrp, so they added the safety setting. If you flashed a backup, how long did it take, a good backup or image will take 10+ minutes, a bad 1 will say done in 1-2 minutes or less.
Might help if we had a little information about what you where doing.
ALD3 said:
Are you trying to flash a backup of 1.9.37 or just a program thru install? I know that if you wipe system and then flash another backup, if the backup is no good, twrp will not boot system but go right back to twrp. That is a safety setting, cause if it booted with no system installed you would most likely have a bricked device. That happened in the early days of Twrp, so they added the safety setting. If you flashed a backup, how long did it take, a good backup or image will take 10+ minutes, a bad 1 will say done in 1-2 minutes or less.
Might help if we had a little information about what you where doing.
Click to expand...
Click to collapse
I tried flashing multiple backups and they all go to twrp. The backups only took a minute or 2.
mikewhit001 said:
I tried flashing multiple backups and they all go to twrp. The backups only took a minute or 2.
Click to expand...
Click to collapse
Ok your backups are all bad, that's why it finishes so quick and won't boot out of TWRP recovery. You will have to download a image file and get it into the TWRP folder on your sdcard. You will have to download it on your computer unrar it and name the folder something like unrooted 1.9.37 and transfer it to your micro sdcard. Then put micro sdcard back in tablet. In TWRP recovery, you will have to go into Advanced>File Manager. In file Manager, you will have to click on external sdcard and copy the file from there back to sdcard>TWRP>backups>serial#>unrooted 1.9.37 it doesn't matter what the folder name is that you put in the serial# folder but the all the others are as named and your new folder HAS TO BE IN THE SERIAL# FOLDER, or Restore will not see it. When that is done go back to main menu and Restore, you should see your new folder, choose it and swipe to restore. This should take 10+ minutes. You should be able to reboot to system then.
Unrooted1.9.37 file to download
https://www.box.com/shared/ew0jcmch2ohvr43ubjqe
This thread can help you a lot quicker.
http://forum.xda-developers.com/showthread.php?t=1905674
If you have problems, PM me and I will send you my email so we can work quicker and won't trash up this thread.
I'm having the same issue since the gapps update, where the Nabi shuts itself down while charging. Sometimes it can be a real pain to reboot after it does this.
Funhog51 said:
Completed the OTA to 1.9.37, root, and gapps install - had the upgrading message on every boot but fixed that with the new gapps package (thanks a lot to all the great developers on this forum!)
However I still have a problem since the root process that I haven't seen addressed so far after searching the forums.
After my putting the Nabi 2 to sleep and plugging in the charger, it will fully charge and turn the battery light green as it should, shortly after that the device then powers off and requires a reboot/cold start vs. just a quick click of the power button to return from sleep mode. It does reboot fine and has a full charge - all other operations are normal.
Any suggestions on how to eliminate this power down/reboot after charging?
Thanks!
Click to expand...
Click to collapse
i cant delete /vendor/apps always tells me (app can not be deleted) thats in es file explorer the others say its deleted but its still there???
streetglide13 said:
i cant delete /vendor/apps always tells me (app can not be deleted) thats in es file explorer the others say its deleted but its still there???
Click to expand...
Click to collapse
In es go to the menu where you turn on root explorer and tap the words 'root explorer' then a menu will pop up, tap mount r/w and then set /system to rw. You then should be able to delete the files. After you're done deleting set system back to read-only.
Hi all,
Obviously you need the Carbon ROM for the P6200 first. Here is the link http://forum.xda-developers.com/showthread.php?t=2723566
Step One: Unlock Your Bootloader and Flash a Custom Recovery
How to Flash a ROM to Your Android Phone
First, let's clear up some confusion: Contrary to popular belief, you do not actually need to root your phone to flash a ROM—you just need to unlock your bootloader and flash a custom recovery. However, this process usually goes hand-in-hand with rooting—and most custom ROMs come with root access—so what you think of as "rooting your phone" is probably what you're going to have to do first.
Unfortunately, we can't go through this step in detail here, because it's different for every phone! So, I highly recommend checking out our everything root guide to learn a bit more about what's involved, what all the different terms mean, and what to watch out for. Then, search around sites like XDA Developers for instructions on how to unlock the bootloader of your specific phone, which recovery you should use (usually TWRP or ClockworkMod), and how to flash it.
I also recommend rooting your phone during step one, since it'll make the backup process in step two easier—and save you some hassle along the way. A lot of methods and one-click apps will root your phone anyways, so it might be included in the process. Again, this can vary from phone to phone. (If the instructions require you to flash SuperSU.zip, you can refer to step three of this guide for info on how to do that—ironically, it's just like flashing a ROM).
NOTE: Unlocking your bootloader will most likely wipe your phone, and without root access, you won't be able to back up very much. So, save anything you want to keep on your computer—you will have to set up your phone from scratch just this once before continuing.
When you're done, return here and continue to step two for the rest of the ROMming process.
Step Two: Make a Backup of Your System, Apps, and Data
Now that you've got a custom recovery on your phone, the first thing you should do—before you ever make a big change to your system—is back it up. First, we'll make a Nandroid backup, which is basically a image of your current system. That way, if something goes wrong, you can restore your phone to exactly the way it was before you started tweaking. This will save you a lot of hassle if something goes wonky (which, let's be honest, can happen often). To do this:
Reboot your phone and enter recovery mode. This is a bit different on every phone, but usually involves some permutation of pressing the power and volume buttons at the same time.
Head to the "Backup" or "Nandroid" section of your recovery mode. The default settings should be fine. If given the option, give your backup a name that helps you remember what it is (like "Pre-CyanogenMod Backup 01-17-14"). Confirm your backup and let it run.
Wait for the backup to finish. This may take awhile.
I also recommend making a second type of backup: your apps and settings. If you just unlocked your bootloader and wiped your phone, you can skip this step, but any time you flash a ROM in the future, you'll want to back up your apps first, since you may have to wipe your phone before you flash. With a backup, you can easily restore those apps and data after flashing, making the process a lot simpler. We recommend using Titanium Backup.
How to Set Up a Fully Automated App and Settings Backup on Android
In an ideal world, your Android's apps, their settings, and your system settings would…
Read more
How to Flash a ROM to Your Android Phone
This is different from a Nandroid backup because it just backs up the apps themselves, which you can then restore on any ROM you want. Nandroid backups take your entire system as it is, ROM included.
Note that you'll need to be rooted to use Titanium Backup (which is why I recommend you root in step one). To perform a backup in Titanium:
Open Titanium Backup and grant it root permissions if it asks for them. If it experiences any problems with root, it'll tell you right now.
Tap the "Batch" button in the upper right-hand corner (the one that looks like a little checkbox). Scroll down to the "Backup" section and find "Backup All User Apps." Tap the "Run" button. This will back up any apps you've downloaded from the Play Store, and their data. (You can try backing up your system data as well, but I find this usually doesn't work very well).
Wait for it to finish. If you like, you can also sync these to Dropbox as described here, but you don't have to for this process.
This may seem like a lot of unnecessary backups, but trust me: it's going to save you a lot of time in the long run. Now if something goes wrong, you have a nandroid backup to fall back on and don't have to start from scratch. And, when your ROM flashes successfully, you don't have to start re-downloading and setting up all your apps yourself because you can restore them with Titanium.
Step Three: Download and Flash the ROM of Your Choice
How to Flash a ROM to Your Android Phone
Now comes the fun part: flashing your ROM. First, obviously, you need to find the ROM you want. Again, this chart is a good place to start, as is our list of the five most popular. You may also want to poke around sites like the XDA Developers forums to see what's available for your particular phone.
When you've found a ROM you want to try, download it and save it to your phone. It should come in the form of a fairly large ZIP file, so you'll probably want to be on Wi-Fi to download it. You can either download it directly from your phone, or download it on your computer and transfer it over via USB.
To flash your ROM:
Reboot your phone into Recovery mode, just like we did back when we made our Nandroid backup.
Head to the "Install" or "Install ZIP from SD Card" section of your recovery.
Navigate to the ZIP file you downloaded earlier, and select it from the list to flash it.
Wait for the process to complete; it may take a few minutes.
Depending on your situation (see below), you may also need to wipe your data and/or cache. In TWRP, you'll find this under the "Wipe" section, and in ClockworkMod, you'll need to either choose the "Wipe Data/Factory Reset" option or the "Wipe Cache Partition" option. When you're done, you're free to reboot into your new ROM.
So, when should you wipe your data and cache? Here are a few general guidelines:
If you're flashing a ROM different than the one you're currently running, you should wipe data and cache. Essentially, this performs a factory reset on your phone, and you will lose all your data.
If you're flashing a new version of a ROM you're already running, we recommend wiping your data and cache—but you should be able to get away with just wiping the cache, meaning you get to keep all your apps and settings.
Remember, if you backed everything up with Titanium, then doing a factory reset isn't all that bad, since you can just restore most of it. Keep in mind that even if you're just upgrading your existing ROM, factory resets can be helpful. If you only wipe your cache, note that a few apps may run into issues, but reinstalling them or wiping that app's data usually fixes the problem.
When you reboot, you should be in your shiny new ROM, ready to play! But what? There's no Play Store? Read on for the last step of the process...
Step Four: Download and Flash Google Apps
How to Flash a ROM to Your Android Phone
Because Google's apps are not open source, custom ROMs can't bundle Google's apps—like Gmail, Hangouts, or the Play Store—with their ROMs. That means you'll need to download and flash them separately. Luckily, this is pretty easy to do: just head to this page on RootzWiki to find out which ZIP file you need, download it to your phone, and flash it just like you did the ROM in step three. Gapps Manager is also a great app that'll help you find the right package if you're stuck, and you can download the APK from XDA Developers.
Gapps Manager Gets You the Right Google Apps for Your Rooted Phone
Android (Rooted): If you root your phone and install a new ROM, the first thing you may notice is…
Read more
Once you've flashed the latest Google Apps package, you should be all set! You'll have a new ROM with tons of settings to play with, the Play Store to download new apps, and—if you made a backup with Titanium—you can now head into Titanium Backup and restore all your apps and their settings. Enjoy!
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
b217260 said:
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
Click to expand...
Click to collapse
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Thank you for making the time writing this, it is relief to hear that you figure this out. Will try this first in the morning.
I did a bad mistake running the flash-all.bat thinking it will only flash the partitions of the system.
Well it is all gone now...Dam if only I wait until the morning I might not made this mistake.
tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
This guide can also be used to restore from other roms;
b217260 said:
I did a bad mistake running the flash-all.bat thinking it will only flash the partitions of the system.
Well it is all gone now...Dam if only I wait until the morning I might not made this mistake.
Click to expand...
Click to collapse
What did you do?
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
petran07 said:
This guide can also be used to restore from other roms;
Click to expand...
Click to collapse
I guess so. I never had to use a backup to restore on a custom ROM yet.
tabletalker7 said:
What did you do?
Click to expand...
Click to collapse
After extracting the stock zip flasher, there is file "flash-all.bat" on the root of the folder. (Guess I needed to use the "flash-all-partitions-fastboot.bat)
Thinking it will only flash the android system partitions I've run it and realize that my internal stoarge was formatted.
Really stupid mistake from my part, sorry for couldn't verify your guide.
Hoping that someone who read this in the future won't do my mistake.
b217260 said:
After extracting the stock zip flasher, there is file "flash-all.bat" on the root of the folder. (Guess I needed to use the "flash-all-partitions-fastboot.bat)
Thinking it will only flash the android system partitions I've run it and realize that my internal stoarge was formatted.
Really stupid mistake from my part, sorry for couldn't verify your guide.
Hoping that someone who read this in the future won't do my mistake.
Click to expand...
Click to collapse
It's my bad. I always store my backups on an SD card with my OTG card reader. I forget others don't think like I do sometimes
tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
tabletalker7, can you please explain a little technical detail? If i follow your procedure, what is the difference from me just restoring boot, system and data from a Nandroid backup of a system that used to boot? What causes the restored system to no longer boot?
Because you seem to be suggesting a solution for the the problem I had. I normally do plenty of backups and play around with the system quite a lot, but Op6 burned me: I was unable to restore from a backup like I always did on other phones. I tried suggestions from other posters to no avail. So I set up a clean system from a fastboot rom and reinstalled everything from Titanium. I wonder, after I set pretty much identically, should I just risk and to once more try to restore from that Nandroid that was failing to restore (that only had system and data btw)? I'd greatly appreciate if you can enlighten.
b217260 said:
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
Click to expand...
Click to collapse
Had faced this many times. ...after trying diff options and failed Qualcome MSM method works perfectly.
Yep, You cant restore data i think as it being already formated as per knowd based on your steps above on diff posts
ahacker said:
tabletalker7, can you please explain a little technical detail? If i follow your procedure, what is the difference from me just restoring boot, system and data from a Nandroid backup of a system that used to boot? What causes the restored system to no longer boot?
Because you seem to be suggesting a solution for the the problem I had. I normally do plenty of backups and play around with the system quite a lot, but Op6 burned me: I was unable to restore from a backup like I always did on other phones. I tried suggestions from other posters to no avail. So I set up a clean system from a fastboot rom and reinstalled everything from Titanium. I wonder, after I set pretty much identically, should I just risk and to once more try to restore from that Nandroid that was failing to restore (that only had system and data btw)? I'd greatly appreciate if you can enlighten.
Click to expand...
Click to collapse
1. Changing Android security updates makes changes to phone encryption. It will make the data itself on the backup unreadable to the operating system. That is why people playing with many different custom ROMs had problems with data stored on their phones.
2. By using the fastboot rom you ensure that both partitions have the same operating system. A/B partitioning seems like a great idea on paper but it seems to be executed in the most horrible way possible.
tabletalker7 said:
1. Changing Android security updates makes changes to phone encryption. It will make the data itself on the backup unreadable to the operating system. That is why people playing with many different custom ROMs had problems with data stored on their phones.
2. By using the fastboot rom you ensure that both partitions have the same operating system. A/B partitioning seems like a great idea on paper but it seems to be executed in the most horrible way possible.
Click to expand...
Click to collapse
Thanks a lot. It is plausible and I remeber seeing folder names to which random hex strings were appended (I did not see file contents though). But after last restores I verified that the folder names in /data/data folder were looking allright. Twrp apparently could decrypt the data partition, but the system would still not boot. If I were to encypr the data partition I'd use the whole partition as one encrypted block and not bother doing it on file or folder basis, which is more error-prone. Another sourse of doubt is that I never played with OS version upgrades nor with installing other roms.
Can you also please answer the following? Do you think I can try to restore my boot+system to a different slot and then come back to my original slot if my playing there is unsuccesfull? Being scared that restoring a previous state can fail is a major problem.
ahacker said:
Thanks a lot. It is plausible and I remeber seeing folder names to which random hex strings were appended (I did not see file contents though). But after last restores I verified that the folder names in /data/data folder were looking allright. Twrp apparently could decrypt the data partition, but the system would still not boot. If I were to encypr the data partition I'd use the whole partition as one encrypted block and not bother doing it on file or folder basis, which is more error-prone. Another sourse of doubt is that I never played with OS version upgrades nor with installing other roms.
Can you also please answer the following? Do you think I can try to restore my boot+system to a different slot and then come back to my original slot if my playing there is unsuccesfull? Being scared that restoring a previous state can fail is a major problem.
Click to expand...
Click to collapse
I would not recommend doing that. While you may have different roms on different partitions you only have one data partition. That is asking for trouble
tabletalker7 said:
I would not recommend doing that. While you may have different roms on different partitions you only have one data partition. That is asking for trouble
Click to expand...
Click to collapse
I would have data backed up, sure.
What bothers me is that an essential property of a digital automaton is that if you start it from the same state it will continue the same. Nandroid used to capture all that mattered for identical runs. It no longer does, something is missing, such as some encryption keys for data partition, as you seem to suggest. This bothers me.
ahacker said:
I would have data backed up, sure.
What bothers me is that an essential property of a digital automaton is that if you start it from the same state it will continue the same. Nandroid used to capture all that mattered for identical runs. It no longer does, something is missing, such as some encryption keys for data partition, as you seem to suggest. This bothers me.
Click to expand...
Click to collapse
What bothers you here are things I call "security". If the nandroid backup has the encryption keys to decrypt it, then the data is not secure.
tabletalker7 said:
What bothers you here are things I call "security". If the nandroid backup has the encryption keys to decrypt it, then the data is not secure.
Click to expand...
Click to collapse
Nandroid backups should be encrypted when created with a user supplied key. Twrp allowed this since ages ago. Not allowing the user to restore a backup is not a right substitution for this.
ahacker said:
Nandroid backups should be encrypted when created with a user supplied key. Twrp allowed this since ages ago. Not allowing the user to restore a backup is not a right substitution for this.
Click to expand...
Click to collapse
TWRP didn't do this. Android didn't do this. Ya know, if this is anywhere near as horrible for you as you are making it sound, my advise for you would be to buy Apple products. Bottom line is a new feature was added to Android, and your backup does work.
tabletalker7 said:
TWRP didn't do this. Android didn't do this. Ya know, if this is anywhere near as horrible for you as you are making it sound, my advise for you would be to buy Apple products. Bottom line is a new feature was added to Android, and your backup does work.
Click to expand...
Click to collapse
-It is as horrible as not being able to restore a full backup. No more, no less.
-Twrp has an ability to encrypt your backups, with your experience you must know this.
-You are suggesting someone to switch to iphone only because they point out that the things are wrong or dont add up.
-It is quite a common knowlege that you get good security out of encryption if you make things explicit and clear. And not how you may think it is. Cause you don't seem to know where the keys are stored for the data partition. Obviousely, because the phone eventually decrypts your data, the keys must be stored somewhere or derived from you swipe pattern.
tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
Following these instructions seems to be the only way of restoring a nandroid backup (at least for my Op6 bought on AliExpress from China). Important: step 1 wipes your sdcard, so the backup you want to restore must be on otg usb stick.
After spending many hours I managed to restore a backup at least once. Fortunately for me I have no plans of upgarding Android and will likely forever stick with the following set:
1) 5.1.11-OREO-OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT.zip (found here)
2) twrp-3.2.3-x_blu_spark_v9.85_op6.img + twrp-3.2.3-x_blu_spark_v9.85_op6.zip (found here)
3) Magisk-v18.1.zip (found here)
My plan is to fully debloat the phone and then I will keep everything unchanged for years, because nowadays updates are more about twisting your arms than giving you usefull features. I almost got to that state, but one little glitch forced me to roll back and the whole hell with the Nandoid backups on Op6 started.
PS: It's very interesting what is really going on with this A/B system. There must be a storage where the encryption keys are stored (if it is the encryption that does prevent the phone from restoring. Which I doubt because Twrp sees the files fine). There also probbaly stored what slot is used. That information does not get captured by the Nandroid backup.
(Btw, It seems that blu_spark Twrp is really NOT encrypting your backups with the passwod you supply. Official Twrp does. I have plenty of old encypted backups, from wich I could not extract any personal data (/data/data folder) but yesterday I could extract my private information from a backup done by blu_spark Twrp. This is serious iussue. I'll double check and will post if confirmed.)
Not confirmed, I was looking at unencrypoted file.
Hi, I have my phone rooted, magisk'd, xposed etc etc and with a lot of apps and tweaks done to it.
Is there any way at all I could make a flashable image of it instead of having to make a backup of it in TWRP and then restoring it from there? (The TWRP method has never failed me but I was just curious about whether the question below could be done)
I'd like to be able to have a copy of the entire phone as a backup on the PC so I could then flash the phone back to its current state (if I mess anything up) using SP Flash Tool?
Forgive me if this is a stupid question or a task so complicated that it would just be easier to continue using TWRP.
The reason I ask is if the TWRP backup on the phone gets corrupted somehow then I'd like a copy of the phone so I could restore using that.
MrGRiMv2 said:
Hi, I have my phone rooted, magisk'd, xposed etc etc and with a lot of apps and tweaks done to it.
Is there any way at all I could make a flashable image of it instead of having to make a backup of it in TWRP and then restoring it from there? (The TWRP method has never failed me but I was just curious about whether the question below could be done)
I'd like to be able to have a copy of the entire phone as a backup on the PC so I could then flash the phone back to its current state (if I mess anything up) using SP Flash Tool?
Forgive me if this is a stupid question or a task so complicated that it would just be easier to continue using TWRP.
The reason I ask is if the TWRP backup on the phone gets corrupted somehow then I'd like a copy of the phone so I could restore using that.
Click to expand...
Click to collapse
You can store a copy of your TWRP backup on PC, then, if the backup that is stored on the device gets corrupted, you can use the copy that is stored on PC.
Sent from my SM-S767VL using Tapatalk
I have a copy of it on PC just in case, I thought I remembered reading a thread on here quite a few years back about creating a custom ROM from your existing installation with SPFlashtool or a similar program but it was so long ago that I might have mistaken it for another backup method.
Either way the TWRP backup is still quick enough to recover from and was thinking about the SPFlashtool way as an experiment. Thanks for replying.
You should be able to make partition image backups in TWRP. System, data and boot. Then you can Fastboot flash those partitions back.
I am not familiar with the MTK devices but it must be similar.
You can also use SuperR's kitchen to easily build a ROM from the images.
MrGRiMv2 said:
Hi, I have my phone rooted, magisk'd, xposed etc etc and with a lot of apps and tweaks done to it.
Is there any way at all I could make a flashable image of it instead of having to make a backup of it in TWRP and then restoring it from there? (The TWRP method has never failed me but I was just curious about whether the question below could be done)
I'd like to be able to have a copy of the entire phone as a backup on the PC so I could then flash the phone back to its current state (if I mess anything up) using SP Flash Tool?
Forgive me if this is a stupid question or a task so complicated that it would just be easier to continue using TWRP.
The reason I ask is if the TWRP backup on the phone gets corrupted somehow then I'd like a copy of the phone so I could restore using that.
Click to expand...
Click to collapse
Please check if this will help you out, I know it can save app, app data and roms. I used it on my device. Though some apps have problem using the app data which was backed up, most apps worked
https://play.google.com/store/apps/details?id=balti.migrate&hl=en_US
https://forum.xda-developers.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763
gopikrishnanrmg said:
Please check if this will help you out, I know it can save app, app data and roms. I used it on my device. Though some apps have problem using the app data which was backed up, most apps worked
https://play.google.com/store/apps/details?id=balti.migrate&hl=en_US
https://forum.xda-developers.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763
Click to expand...
Click to collapse
That is useless for what they are trying to do. That only backs up and restores user apps and user data, it helps you keep your data when switching ROMs. That doesn't help restore the system if the device gets corrupted.
Sent from my SM-S767VL using Tapatalk
Can't believe nobody on XDA told you about dd in 361 days!
Abstract:
Twrp have constant problem with encrypted data. The goal to achieve is make full backup of encrypted phone, when is unlocked, and be able copy on another same model of phone, and again encrypt it.
Same question here.
Im currently working on this.
Will update soon...
-`chiron` -> lineage-18.1-20210722
1. First try:
Code:
a) adb shell
b) su
c) dd if=/dev/block/by-name/system of=/mnt/sdcard/system.img
d) copied /mnt/sdcard/system.img to windows file system
e) dd if=/dev/zero of=/dev/block/by-name/system (after that phone restarted and automaticly went into fastboot)
(adb exited)
f) fastboot flash system system.img
g) Flashed with success, system animation showing, but after longer time phone turning off.
Data looks to dumped correctly, but now question is how to restore it correctly? (i didnt check it well: todo)
Copy full disk image from Android to computer
I have a smartphone without the possibility to insert an SD-card. I would like to make a dump of the biggest partition (cause I lost files and I'd like to use a dump to recover them). The partition...
stackoverflow.com
How to stream an encrypted backup of the entire device to remote host?
I have an Android device that has no free space and no SD-card that I can replace (thanks to OnePlus policy). I also have no free space on PC to accommodate the backup so I wanted to upload it to the
android.stackexchange.com