Related
Simple Question about WP Easy Backup
If I made a Full backup with this tool I Will get a Folder at Windows Phone Update with the name of Mobile ID like:
YYYYYYYY - YYYYYYYY - YYYYYYYY - YYYYYYYY
At properties folder theres a file with a .xml with a line like this:
<DeviceUrlId>zune-tuner://windowsphone/YYYYYYYY%20-%20YYYYYYYY%20-%20YYYYYYYY%20-%20YYYYYYYY</DeviceUrlId>
At restorpoint folder we got an active id.dat with a ID like:
{11111111-1111-1111-1111-111111111111}
and a folder with the same name:
11111111-1111-1111-1111-111111111111
In that folder there is a sub-folder called Data and there is a lot of files .dat and .hash
and a another .xml. The .xml got a line like this:
<DeviceId>YYYYYYYY - YYYYYYYY - YYYYYYYY - YYYYYYYY</DeviceId>
Now if I share my Backup with someone with the same device and change the information like:
YYYYYYYY - YYYYYYYY - YYYYYYYY - YYYYYYYY to:
XXXXXXXX - XXXXXXXX - XXXXXXXX - XXXXXXXX
<DeviceUrlId>zune-tuner://windowsphone/YYYYYYYY%20-%20YYYYYYYY%20-%20YYYYYYYY%20-%20YYYYYYYY</DeviceUrlId> to:
<DeviceUrlId>zune-tuner://windowsphone/XXXXXXXX%20-%20XXXXXXXX%20-%20XXXXXXXX%20-%20XXXXXXXX</DeviceUrlId>
{11111111-1111-1111-1111-111111111111} to:
{22222222-2222-2222-2222-222222222222}
11111111-1111-1111-1111-111111111111 to:
22222222-2222-2222-2222-222222222222
When the other person try to restore using the WP7 Easy Backup
The phone will recognize the mobile ID and install my Backup on the other device?
I'm Just courious.
i have tried it but with no luck, every device has its own "serial" i dont know how they name it, but we cant see it, and we cant manipulate it. and this serial wont allow you to do that. i even tried to backup 7720 on a custom ROM, and restore on a other ROM, that also dont work. its like the backup dont realize that this is the same device. and what i seen so far, every backup has its own code in the windows backup folder, try the same device after a update and the name changes also...
Backups are, so far as we know, encrypted with device-specific keys. I think these keys are in the hardware or at least the bootloader; they persist even across hard-reset.
Thanks
Just wanted to express my gratitude since I'm too young to post in the dev forums. Full Backup and restore worked perfectly for me. Got the error message after my phone rebooted due to the fake update, restored, and everything was picture perfect.
HTC HD2 (Back to the Future ROM, xmb Rom 8107.79) = HTC HD7 T9292
When I first bought my HD2 two years ago I was miserable until the official stock rom update helped smoothed out several issues, but even then it felt like a lot was missing in comparison to WM7. Now two years late after applying the Back to the Future ROM with the Mango update, added with this perfect backup solution, I'm really in love with my HD2/HD7 and can afford to hold out til atleast 2013 for the new Cortex-A15 superphones to drop. And even then I'll still hold on to my HD2/HD7 as an extra PMP.
Just a quick one on this. Is it possable to strip the device ID from the backup and create a Rom out of it and maybe modify it somehow for Root, etc ?
I would love to be able to create a rom with alll my Paid apps, then make it have root, then have my own custom rom that if something breaks I dont spend 2 hours installing like 60 apps...
... as I posted *just* a few responses further up:
"Backups are, so far as we know, encrypted with device-specific keys."
Unless you can figure out the decryption key - it's possible, probably without even disassembling the phone, but if you managed it you'd be the first success in a significant list of people to try - you can't even read the backup, much less modify it or flash it as a ROM image.
I made a clean ROM based on the factory ROM for the Lenovo A789, A660 and P700i
Cleaned up ROMs:
- A789_S227_cybermaus_V2 (below)
- A789_S228_cybermaus_V2.1 (further below)
Ported ROMs (ported from P700i):
- A789_ROW_S105_cybermaus_ICS_V3 (further below)
- A789_ROW_S106_cybermaus_ICS_V3.1 (Further below)(also for A660 and P700i)
- A789_ROW_S107_cybermaus_ICS_V3.2 (Further below)(also for A660 and P700i)
The current and advised rom to use is A789_ROW_S106_cybermaus_ICS_V3.21
Based on factory ROM A789_S227_120827, and located in my Dev-Host. It is as close to factory as possible, which I hope will be good for stability. It is a flash-utility ROM, because it also holds the latest preloader, uboot and recovery. Assuming those are OK, followup fixes will be update.zip style.
Summery of changes:
- Rooted the phone with Chainfire SuperSu
- Set to boot in US-english, changed name of ROM
- Added MoreLocale for extra languages in 3rd party apps
- Removed Chinese apps, incl Chinese keyboard, removed SmsReg.apk
- Left Lenovo Security (anti-malware) and Lenovo (Go) Launcher intact
- Added Google GAPPS, Play Store, Maps, etc
- Added MobileUncle toolbox, SManager (root explorer). Titanium backup (free version)
- Added fix for location services
- Added CWMT recovery image (modded from 593cn.com)
- Added Skype, Whatsapp, and some others, as auto-install into userdata upon wipe
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Replaced bootup animation with clean Lenovo butterfly
- Replaced all some audio files with english named ones (thanks mabuc)
- Caller ID bug still present, sorry
- Just as a reminder, these ROMS have English and Chinese only.
Instructions:
By default, the ROM will not overwrite USERDATA or FAT. If you want a clean slate, first extract empty.userdata.rar and/or empty.fat.rar
- Read bgcngm flash tutorial.
- Read it again
- Start Flash Tool (v3.1222, in my Dev-Host)
- Load scatter file
- Take out USB cable and replace battery
- Press the download button in the flash tool
- Connect the USB cable
- Wait for the flashing to complete
A789_S228_cybermaus_V2.1 (no longer current, Use V3 instead)
Based on factory ROM A789_S228_120913, and located in my Dev-Host. Similar to V2, but newer, and a few extra fixes. It should be noted that the S228 is listed to solve unexpected crashes, so an important update in itself.
I do not have a A789, so it is a blind build. Until I get positive feedback, consider untested. Don't be the first to try if you are not experienced.
Summery of changes:
- Same as on V2, and additional
- Removed 2 more chinese apps that I forgot last time
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Added a tweak so USB-Debug notification is no longer shown
- Added a tweak so Wifi works on all 14 international channels (rather than only the 11 US ones, may be undone if you set a different locale)
Instructions:
This is a update.zip type ROM. So you need the custom recovery, see post #3,
A789_ROW_S105_cybermaus_ICS_v3.03
Based on P700i_ROW_S105_120920, see this separate post.
A789_ROW_S106_cybermaus_ICS_v3.11
Based on P700i_ROW_S106_121001, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
A789_ROW_S107_cybermaus_ICS_v3.2
Based on P700i_ROW_S107_121221, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
Below:
Post #2: Small review and fix of location services
Post #3: Custom recovery image
Post #4: Root your phone / install GAPPS
Also, many issues for the A789 are similar to those of the A750, so if you have questions, do search that Lenovo A750 thread to.
Thanks
Also thanks to bgcngm for his help, and to jazzor for his help
=================
BTW: Due to new forum rules, resulting in a large number of people that cannot post into developer threads and that subsequently PM me, I open op a new Q&A thread.
I am not going to be policing, so you can post where you like, but I invite everyone to use this new thread for any Q&A, and this thread for ROM releases and deep development talk only.
Consequently, if you PM'ed me, look for your reply in this new thread
Thanks
====================
PS: do drop me a reply if you use or tried it! Or press the 'thanks' button.
So, I got my first glimps at the A789. So to speak. My colleague was holding it while we were audio-skype, so I did not actually see it.
His A789 came with a Etotalk ROM by Dean, which I now suspect is a reworked Smileyvvv ROM with Sony Experia interface. Not bad, but as you know, I am a 'factory ROM' guy. My colleague may also be, because he had already replaced the the SE launcher with GO Launcher, which is the default Lenovo one. Also my colleague said it jammed a few times, which it still has not done on my factory A750 ROM.
Most of the phone worked, but a few tips for others out there:
- The phone still has the Called-ID bug. Even though it is newer 4.0,4. I know some of you claim this is solved on ICS Mediatek, but I still claim it is solved in *some* of the cases, not all, it also depends on how your provider sends the caller ID info. Anyway, you can work around it with the prefixer app as reported before.
- It did not come with the MobileUncle tool, but with the Etotalk tool. Which was not updated for the new MT6577 chip, so it had no Engineer Mode. Install the latest MU tool (version 20120813v2.2.0 its in my Dev-Host), so you get one with MT6577 Engineer mode.
- Recovery Mode was hard to get into. Like the newest A750 preloader, you have to press the power putton *just before* you press both volume buttons. But it did came with the CWMR Touch, though its Touch function was broken, so buttons only. They probably simply tried recovery images of other models, and did not properly build one with the A789 kernel, but it does not matter, it works well enough.
- Location services did not work. Update the phone with the ICS_locationfix_v1.3 update using recovery mode. While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Lenovo A789 Recovery
I created a recovery image for the Lenovo A789 based on ClockWorkMod Touch 5.5.0.4. However, I do not own a A789, so until I have reports of it working, consider it untested. You can download it from my Dev-Host: File A789_S22x_recovery_cybermaus.rar
NOTE: It has come to my attention this recovery works well, except the nandroid backup function, which is broken. If you value nandroid backup, install the APKHOT one below.
While doing this, I also found a full APKHOT distro which had what seems to be a CLockWorkMod (non-Touch) recovery in it, so I extracted that and also uploaded it. That too you can download from my Dev-Host: File A789_S22x_recovery_apkhot.rar
Both of them you will have to flash using the flash tool, using bgcngm's excellent manual, and the V3.1222 of the flash utilities and drivers, also in my Dev-Host. If you flashed my V2 ROM, you do not need to do this, as the recovery is already part of that.
Once you have the recovery installed, you can enter it by pressing both VolumeUp/Down while booting the phone. Due to an issue with the preloader, it may be needed to press the power button slightly before both volume buttons. If the phone seems stuck, it means the preloader messed up, remove battery and try again.
Inside the recovery (the Touch variant) you can navigate not only by its physical buttons, but also by screen buttons, and by gestures: swipe up/down for up/down, left for back and right for enter.
The first few people using this, please report your findings, good or bad.
PS: As alwasy, thanks to bgcngm for his unpack utilities, which I used to modify the recovery.img
Lenovo A789 Root; GAPPS, Location DIY
Its been mentioned before, but if you have a working recovery (like above, hopefully), you can always yourself root your phone. Simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red requires root warning)
The file you need is labeled "CWM installable ZIP" at the bottom.
Direct link to the file you need to install via recovery update.zip
And while you are at it: You probably also want to install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9:
Explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip and can be found here
You probably also want to wipe your cache partition after doing this.
To complete this DIY of fixing factory ROM: On Chine phone typically the location services do not work. Update the phone with my A750 V1.3 update using recovery mode. (it works on the A789 because it is a minor update, but *DO NOT* any of the other A750 updates on the A789. I repeat, do *NOT* flash A750 on A789). While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Good luck
PS: If either update.zip refuses to install, remember to turn off the checksum and assert checks in the recovery.
And thanks to Chainfire for his work, and the team at CyanogenMod for theirs.
cybermaus said:
Before I can help, please provide some info:
Can you tell me what ROM you have?
Which flash tools did you use to root?
Also, do you have a working recovery?
Click to expand...
Click to collapse
hwonggc said:
I fix the proximity thingy. it's caused by my lousy screen protector. But i've got another bigger problem now. I've accidentally uninstalled the default system home screen. I cant assess anything now. I tried flashing a recovery inside but it still doesn't work as factory. I use SP flash tool v3.1.222.00
---------- Post added at 06:32 AM ---------- Previous post was at 06:18 AM ----------
dont think my recovery is working. Could you please provide me with a working recovery? =(
Click to expand...
Click to collapse
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my Dev-Host. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
EDIT: @ hwonggc : Please test recovery in post#3. Just update your post below with results, or PM me. I would like to avoid too many new posts on this while we are testing.
cybermaus said:
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my 4Shared. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
Click to expand...
Click to collapse
Yes yes. I had the factory rom. I got the phone just yesterday evening and this afternoon it's half dead already. I use smart phone flash tool to root using a file i got from http://www.fight.org.ua/publications...novo_A789.html. Everything was fine until I deleted the original home UI and the apex launcher also. So there isn't anything I can do. I'm downloading the S223 from some russian site and try, hopefully I can find some luck there. Downloading slowly~ sighhhh.
---------- Post added at 07:49 AM ---------- Previous post was at 07:40 AM ----------
BTW~ i'm willing to test out your rom too! I wouldn't want to sound too demanding, put please please put in the play store will ya?
I posted the custom build, see first post. It may take a while before I can get it uploaded, I am on a bad link.
Also, there have been 20 downloads on the recovery image. Come on guys, someone must be able to provide feedback about it working or not!
A789_S227_cybermaus_V2 ROM is working
Hello
Thanks for Your work.
Your A789_S227_cybermaus_V2 ROM is working.
Simple Flashing and start without problems. Now I must check some functions.
Thx again
basell
Edit:
The 3g connections don't work at first run. After restore they start but in My opinion with less sensitivity (compare to stock rom). It's look like A789 loose some frequency on witch can work.
Edit2:
And they have some strange behavior - After couple min of data connection (on 3G) they disconnect with information - "Restricted access changed" and the same is when I try to choose network manually. After that sometimes they login to 3G sometimes they change to EDGE.
In Stock version (S221) was not this kind of problems.
Edit3:
In place with good 3G signal I have no problem with data transfer.
How Can I check on witch frequency (2100,900,850) I have connected My data transfer?
Thanks for testing
Well, I definitely did not mess with any of the 3G stuff. So if it is true that 3G is less sensitive, then I would claim it is true for the factory S227 vs factory S221, and not directly related to my cleanup of it.
But (sorry to say so) I have learned to take claims of improved or degraded radio sensitivity with a grain of salt, even for the factory ones.
Having said that: Restoring S221 radio into S227 firmware is easy. The radio is separate firmware file, and I can extract the S221, S223 and S227 firmware in a separate file, so you can test. Were you actually using factory S221, or some other?
As to whether it is using 2100, 900 or 850: I can probably figure out how to get that info, *BUT* reality is that your provider most likely has only one frequency anyway. Most, pretty much all, EU providers are on 2100. The phone could not get to 900, simply because your provider does not have that frequency in the air (not for 3G anyway). And 850 is not supported at all on this phone.
Anyway, inside MU utility, engineer mode, bandmode, you can check/set the frequencies that are supported.
But please run a proper test if 3G is really degraded. As stated. it is so often a empty claim, I am somewhat careful to follow it. You want me to extract the 3 versions of firmware files in update.zip files?
Also, what country/vendor are you? please list the MMC and MNC from inside the APN settings.
Hi
If You will prepare this files I can test it tomorrow.
I'm from Poland and I have two frequency on data transfer - 2100 and 900. But I don't know if A789 use only one or change them. The place I'm test the signal is poor and I don't see if I work on 2100 or 900.
If You can, pleas tell me what kind of tests I can do to do that properly
Ok, here they are. update.zip type.
I only have S221 and S227, but the firmware files were indeed different, in more than just their timestamps. Of course, normally I would assume newer is better. So to make it clear: below files only replace the radio&dsp firmware, not the phone firmware.
Try to test honestly for yourself. Same conditions, same place, same time (because network load can make a difference)
It is possible that 3G really is degraded in S227, but as mentioned, I learned to not jump to conclusions just because the network is having a bad day.
WARNING: I retracted the two attachment, because I made a typo in the installer script. While the firmware is for the A789 (MT6577), the installer script is for the A750 (MT6575). Sorry. I will upload the correct ones in a moment.... Anyone that took a copy of these files before Oct 14, delete them!!!
I suspect the install would simply have failed, no harm done, but best to get rid of all copies anyway
BTW: basell, is that why you asked how to install? Really, if you ask for help, you should provide a bit more info. Anyway, I attached newer scripts, if you still want to try.
sorry for My question but :
How to install this firmware?
Like any update.zip on android. Go into recovery (see post #3) and apply the update.zip
i have the problem that the netlocation doesn't work with google maps, i flashed the cyber update 1.3, nothing changed, what should I do now?
And this is on what phone and ROM?
Anyway, to quote myself: "While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work."
many thanks, Cybermaus, netlocation works again after your instruction
Hi,
Thank you very much for building the ROM !!
I am using it for 3 days now and I am happy to report no problems with it. Everything works and most important: no more freezes !!!
my A789 came with the Etotalk by Dean ROM which was mostly OK, but was freezing from time to time (some days not at all, other days several times a day - most of the times when hanging up a call or, when trying to do wake it from standby: I was pressing the power button, but the screen would not light up).
Other things I like about this ROM:
- all phone functions work great
- Google Play works perfectly
- is rooted
- it has the Lenovo battery app, which is great! I am not 100% sure if this is the reason, but the battery life went from 1 day to 2 days
- I had no issues flashing it
- CWMT recovery works
Also, so far, I did not experience any 3G issues
I have written a small review of the Lenovo Security app, which you guys may want to put back on your phone if it was cooked out of it.
jman0 said:
Thinking it twice, I've remembered another reason. One of the things I like most about the apkhot rom I'm using is that the external sdcard is mounted on /sdcard and not /mnt/sdcard2, which avoids problems with many apps. I tried one of the newest apkhot roms, based on s227, and none of the tricks to exchange /sdcard and /mnt/sdcard2 worked with it.
Click to expand...
Click to collapse
Well, that is actually an easy change to perform, just change the /etc/fstab.vold
However, if you go into settings->storage, the first option is default write disk. Change it from USB storage(the internal SD) to SD (the external SD)
So no hacking is needed at all.....
I've been running your rom for around 6 hours now. Everything runs fine. The 3G connection worked without much trouble. The only thing I haven't been able to do is performing a backup with the CWM Touch Recovery. So, I've just flashed the recovery I had on the apkhot rom I was using, using Mobileuncle tools, and now I've been able to create a backup.
So far, so good, and I've noticed a slight performance increase, too.
GUIDE SGS4 GSM vs CDMA, Unlocking, Rooting,Info on XDA, Flashing,4 noobs & beginners
First off: if you find this useful, please hit the THANKS button, instead of posting thank you in the comments
Over the course of the past three months (and more specifically, over the past week), I'd like to think I've gone from complete noob to proficient android ROM flasher/ phone dude. However, it took many, many hours of searching for info scattered across this site and others, so I figured I'd give compiling all I've learned a shot, into one comprehensive thread that really covers all the stuff you need to learn from the ground up.
Will do so in the next couple 10 posts, topics being:
*Step (-1): What type of network/ phone technology does your phone use?
*Step (0): is your phone networked locked?
*Step (0.5): DECIDING YOU WANT TO ROOT YOUR DEVICE!/ Put a custom operating system on that thaaaang
*Step1: figure out what your device is- specific phone and model
*Step2: figure out how to root (gain root access to) your device looking at XDA forums
*Step3: Follow instructions, root device
*Step4: backup all your apps and app data
*Step5: Install a custom recovery either ClockWorkRecovery (CWR) or Team Win Recovery Project (TWRP), and do a nandroid backup!
*Step6: Choose which ROM or multiple ROMS you want to try out, and download the zipfile to your phone's internal memory or
*Step7: Step 7: flash the ROM and restore your apps!
NOTE: YOU TWEEK YOUR PHONE/ FOLLOW MY ADVICE AT YOUR OWN RISK
I just learned this stuff myself, so I thought now would be a good time to explain it, while I can still remember what if feels like to have no idea what I'm doing haha.
Before I go further, there are similar intro threads to this...for example, this one does a decent job of explaining that by modding your phone, you may void the warranty (although there are ways to restore your device to a state such that you can't tell you ever modded, it, like triangle away, etc.) http://forum.xda-developers.com/showthread.php?t=1118120
I posted this here because a couple of these steps use the Galaxy S4 i9500 as an example...so if you have that phone this thread should be particularly helpful.
Step(-1): What type of network/ phone technology does your phone use?
If you are OUTSIDE the USA, 99% chance the answer to this question is GSM, meaning your phone number is attached to a little plastic sim card that you can put into/ out of your phone...you should check anyways though to be sure.
If you are in the US, you may have a phone which uses CDMA, a technology that does not use Sim cards (true if your carrier is Verizon or Sprint). Phones that JUST use CDMA are sort of "Hardwired" to their networks, making it much more of a hassle to switch carriers; plus, basically everywhere else in the world uses GSM, so if you plan on traveling outside the USA, you probably won't be able to use your phone abroad. If you have a fancy new smart phone, it may have the hardware to use both CDMA and GSM networks, (for example, all Iphones models 4s and above), so check your phone specs.
In the US, the major carriers that use GSM are ATT and Tmobile. I prefer getting phones from these guys, because I know I'll be able to relatively easily use my phone anywhere in the world, and easily switch between cheap, prepaid, contract free plans (like straight talk or ultramobile), which rent out the networks of major carriers like ATT and Tmobile.
Step(0): is your phone networked locked?
ans: This is mostly a non-issue to folks outside the US, or if you don't plan on switching your carrier, but if you plan on travelling abroad or switching your carrier, and have a CDMA phone, you have a tough road ahead that I cannot advise you on . I would suggest checking out this site and buying a slightly used android gsm phone (att or tmobile branded) http://swappa.com/ .
However, if you have a GSM phone you got in the US, your phone may be configured so that putting sim cards from different carriers in it won't give you any service (aka "locked" or "network locked"). Check by taking a friend's Sim card using a different network than you and popping it into your phone; if you have service/ can make and receive calls, the phone is NOT locked. There are probably more sophisticated ways of checking if your phone is network locked, but above is probably the most straightforward.
There are some methods of unlocking your phone for free, but if you have a newer phone it may not work. Plenty of online sites that sell you unlock codes for between $7-$25, and send the code over email either instantly or a day at most after you buy it. Definitely worth it in my opinion; one site I've used a bunch is http://www.cellunlocker.net/
NOTE: if you have your phone on a contract, you are still obligated to pay your carrier throughout the time of your contract, else you pay some cancellation fee. So be aware of that.
Step 0.5 DECIDING YOU WANT TO ROOT YOUR DEVICE!/ Put a custom operating system (ROM)
SO, now let's say you've network unlocked your awesome GSM android smartphone, and you want to travel with it to another country, like for example, India. Because you unlocked it, you can buy a cheap local Sim card and use it in your phone, fully enjoying mobile 4g data (well, more like 3.5G, using HSPA+, not so much 4G LTE in India yet, but I digress). OR, you can use a $45 a month prepaid plan where you get unlimted everything and have no contract, instead of paying $80 a month or some garbage. AWESOME!
However, let's say you got a Tmobile phone and want to use the phone's capability of being a portable wifi hotspot, broadcasting the mobile data it's getting to your computer...turns out you can't do that in India (or on cheap prepaid plans in US, for that matter). I discovered that since I was using a Tmobile branded phone, the Tmobile "stock" operating system of the phone won't let you use the wifi hotspot unless you have Tmobile's special "hotspot plan"...it also hard codes a bunch of shi**y bloatware apps on your phone that suck. Some BULLS**T, eh?
Luckily, there are plenty of free and easy ways to "root" (gain root acccess) to your phone (and plenty of resources telling you how to do so!), and install custom android operating systems on your phone, which
1.) don't have any stupid bloatware apps
2.) let you use all the hardware features of your phone regardless of carrier
The result is a more powerful phone that runs faster, uses less battery life, and is generally just way more badass. Probably the best resource for how to do all of this is the xda-developers forums (http://forum.xda-developers.com/ ) Very vibrant community, and lots of people will help...just follow the rules though, explained tongue and cheeck in the following video ( http://www.youtube.com/watch?v=JmvCpR45LKA ). The main site for xda-developers is www.xda-developers.com, they also do cool vides and stuff on what's up with phone stuff. HOWEVER, if you are not careful you can mess up your phone, so that it's about as good as a paperweight (called "bricking" your phone). So just read all the instructions before you do stuff, yeah?
The following is more or less the beginning steps I did to root and install a custom ROM on a friend's Galaxy S4, which is an international model and so not network locked. The same general process could be applied to your phone as well, but again--this is only a general guide--your phone can (and probably will) have it's own exceptions to the general process. LOOK THEM UP!
Steps 1,2,3: find device model, research how to gain root, ROOT!
Step1: figure out what your device is- specific phone and model
ans: for example, my friend's phone I am setting up for him is the Samsung Galaxy S4 model i9500
**************************************************
Step2: figure out how to root (gain root access to) your device
ans: Off all the devices on xda forums (http://forum.xda-developers.com/index.php?tab=top), found my device ( http://forum.xda-developers.com/galaxy-s4) , found the proper forum (http://forum.xda-developers.com/galaxy-s4/help) , then searched in that specific forum to find the proper thread http://forum.xda-developers.com/showthread.php?t=2419762 , see Q4
**************************************************
Step3: Follow instructions, root device
ans: Instructions are at http://forum.xda-developers.com/showthread.php?t=2292615
NOTE: You must have the proper USB drivers installed, meaning either installing the sdk (software developer kit) from google and getting adb (android debugging bridge) set up (this is the best way to do it, really, especially if you want to mess around with phones more...tutorial on how to setup adb here http://androidcentral.us/2013/08/how-to-install-android-adb-and-fastboot-on-windows/ ) . If you can already transfer music and stuff from your computer, it may work without adb. Be sure your USB cable is not too beat up, and if possible, is the one that came with the device.
adb is very useful for communicating between pretty much any android phone and your computer. You can use it to push files on the computer through the terminal interface, even if the phone's file system doesn't show up for whatever reason on the computer when you connect it via USB ( more on that here http://log.amitshah.net/2012/05/using-adb-to-copy-files-to-from-your-android-device/ ), and a cool little program to send files from your computer to the device in a slightly more straightforward way, if you already have adb installed (http://www.xda-developers.com/android/push-files-to-your-device-with-quick-adb-pusher/)
Also, make sure you have USB debugging enabled. It should be in the Develpors options, which you may have to "activate" to see...see here http://gs4.wonderhowto.com/how-to/enable-hidden-developer-options-your-samsung-galaxy-s4-0146687/
If you are rooting a samsung device, you will probably have to use a program called ODIN. Other android devices allow you to do root through a method called flashboot. In general there are tons of ways to root devices, just make sure the one you are using has been tested and you follow the instructions exactly.
CONGRATS! you are rooted. That's half the battle. Rooting the phone will add a "Super User" app of some kind, which will basically controll which apps have access to the internal files of the phone (located on the "root" of the phone's flash drive). Some apps that are very useful for flashing custom ROMS (like ROM manager) and backing up your apps and their associated data (like Titanium backup) require root access, so you'll need to have rooted your phone first, and then when you open those apps for the first time, tap "allow" when it asks about granting root access.
some cool apps can only be downloaded if your phone has Root, like this gameboy emulator: https://play.google.com/store/apps/details?id=eu.codlab.src.game&hl=en
and here are some good Root apps to have, apparently
http://www.youtube.com/watch?v=jX4ir9r84YA
Step4: backup all your apps and app data
When you do eventually install a custom ROM on onto your phone, it will start out with little to no apps. The best way to get up and running again as quick as possible is to back up all your apps and data with Titanium Backup (mentioned above), which requires root access. Here's a great video on How to use the free version: http://www.youtube.com/watch?v=gQWoWfTA88k ....the video makes a good point in that if you are backing up your apps for a new ROM you are about to flash, you should only backup the User apps. Backing up and restoring the system data as well might cause some problems in the new ROM
While you don't need to to buy the pro version, I would recommend it--7 bucks, but it allows you to restore all the apps you've backed up much faster by letting you back them up into a zip file that you'll later be able to flash on your phone. Very useful, more on that in a bit...video talking about that here: http://www.youtube.com/watch?v=dRR5FONGJUA
Step5: Install a custom recovery either ClockWorkRecovery (CWR) or Team Win Recovery
By "custom recovery", i mean a custom version of the boot/ recovery interface, which lets you do a lot more with your device besides just restore it to factory settings. These custom recoveries will let you do a full backup of your device (often called a "nandroid backup"--this should be the first thing you do after you root your device!), as well as flash custom phone operating systems (ROMS) onto your phone; useful if you want to fully use all the hardware features of your phone, and not have the bloatware apps from the manufacurers hard-coded into your phone.
It's worth noting here that it's VERY important to install the correct version of CWR or TWRP. Usually to download CWR for your device, you can just download an app called ROM manager (again, after you've rooted your phone), which will recognize your device and then install the proper CWR version on it.
NOTE: If you have a more esoteric model of phone (like I do--the Samsung Galaxy S3 T999L, an LTE version of the S3 that came out in 2013, a while after the initial S3 launch), you may have to flash a custom recovery of a similar and more popular phone model to flash some custom ROMS (in my case, I had to flash the the Galaxy S3 model T999 version of CWR). For weird esoteric cases like this, it may be worth it to buy a useful app, ROMToolbox pro, which will let you flash a custom recovery for a userdefined device onto your phone in the paid version (it's like $5). Most times you shouldn't have to worry about this stuff, but just make sure you read any instrutions on XDA forums carefully before doing stuff.
As mentioned before, before messing around with your phone anymore, do a nandroid backup--super easy and essential if you make a mistake installing the wrong ROM or Recovery. Doing a nandroid backup will create a .zip file that contains a full "image" of your phone--all your data, apps, settings, a snapshot of your phone exactly the way it was when you took it. In creating this backup you can save it to your phone's micro SD card, or the phones internal memory. Regardless, always a good idea to save a copy on your computer too when you are done.
For the Samsung galaxy S4 i9500, looks like TWRP is the recovery to flash: http://forum.xda-developers.com/showthread.php?t=2361122
Step6: Choose which ROM or multiple ROMS you want to try out, and dl zipfile to phone
Now comes the fun part. Do some research on what custom ROM you'll want to try out. Some basic principles about ROMS:
Roms based on the Stock OS: These ROMS are based on the manufacturer firmware/ OS that the phone shipped with. So for Samsung devices, for example, these types of ROMS are Touchwiz based (because "TouchWiz" is the name Samsung has given to it's proprietary software that is responsible for a lot of the bell and whistle tricks you see in Galaxy S4 commercials, for example) These Roms are usually about 700 MB in size, and may still have some of the samsung apps installed if you do like to use them.
AOSP or AOKP ROMS:
AOSP (Android Open Source Project) ROMS are those that ship with "vanilla" android, meaning they don't have any manufacturer bloatware--they come with more or less the bare bones apps required to run the system. These ROMS will be much smaller, around 100-150 MB in size. The most popular of these is CyanogenMod, which is often referred to as just CM (for example, CM11.0.1 stands for CyanogenMod version 11.0.1). The guy who made clockworkrecovery, Koush (a legendary android developer of sorts, it seems), now works for the CyanogenMod development team ( think)
AOKP is the name of another popular AOSP based ROM. AOKP stands for Android Open Kang Project, Kanging being some jargon for stealing code and messing with it or something. Apparently it was used as a joke and then stuck, in the same sense that their mascot being a unicorn stuck (which I think is awesome haha).
IMPORTANT POINT ABOUT AOSP ROMS:
If you flash an AOSP Rom, the google play store will NOT be installed by default. In order to fix that, you'll need to flash another zip file containing the play store app as well as other basic google apps (gapps for short) as soon as you flash the Rom itself. You can find the proper gapps zips that go with the proper AOSP roms here: http://goo.im/gapps
There are couple apps that will let you download the ROM files directly to your interal storage from the app itself, like Rom Manager. However, to make sure you have the most up to date version of the ROM, you should visit the ROM's website directly.
Custom ROMS will often have a most recent stable build, and a most recent "nightly" build. The nightly builds may have some new experimental features, but may be a little buggy.
Step 7: flash the ROM and restore your apps!
So here's a pretty good short video walking through how to flash a ROM, although uses a different recovery interface besides CWR or TWRP : http://www.youtube.com/watch?v=nxTwGwtUBbk ....this does a good job of explaining the basic idea, however--
A.)you get the zip file of the ROM you want to flash on your internal or removable SD card
B.) reboot into recovery mode (often by holding down the volume down key and power button at the same time when your power is off, but you should look up what it is for your specific device)
C.) do a Wipe or Factory Reset. THis should not wipe the data on your SD card or phone's Internal SD card
D.) Wipe the Cache or the Dalvik Cache, whatever it is called (though on TWRP, the wipe feature does both a factory reset and cache wipe at once)
E.) install from SD card the zip file containing the ROM you are going to flash
F.) If the Rom is an AOSP based ROM, install the zip file containing the proper package of google apps
G.) reboot system
Again, the above are just general steps. If you want to see someone flashing a ROM with the recovery you are using (and I would recommend CWR or TWRP), just search for it on Youtube.
Now, if you plan on restoring your apps by flashing a Titanium Backup zip file, you first want to reboot into the new ROM, and skip the part when it asks you if you want to restore your phone using your google account (you can do that later). Then reboot into recovery and flash the Titanium backup zip file. got this info here: http://www.s3forums.com/forum/galax...backup-pros-update-zip-restore-your-apps.html
And that's about it! let me know if I got anything wrong. If you do have questions, I'll try my best to answer them, but again, I've just learned all this stuff as well, so I may not know.
AS ALWAYS: I take no responsibility - DO THIS AT YOUR OWN RISK!!!! BE CAREFUL!!!!! I guarantee nothing.
1 Mar 2020 9:50PM GMT: changed - PE10 doesn't work with this - need backup of EFS. Persist, fsg.
8 Mar 2020 2:42AM GMT: I doubt the premise of removing the 2 erases of t1 and t2 so that has been removed. The crux of this guide is simply take backups of EFS and a few other files before making any mod.
Why this post: it seems many folks can't get back to working stock (no wifi or mobile).
- - for folks who have re-locked their phones, I have no solution for unlocking it if you can't go to the motorola site and unlock it. Sorry. - -
- - for folks who are on a custom ROM with working wifi and mobile, and don't have backups of EFS etc from stock, DO THAT as described below. - -
EDIT: Pixel Experience 10 coming back to stock wipes mobile, even though it worked on PE10. Have to have twrp backup of EFS, Persist, fsg. Worked fine for Lineage 16, Superior OS. So clearly, have a backup!
Prep: if you are thinking of trying a custom ROM, or simply as a good safety aid, back up some of the small files:
Grab both the .img and .zip files of the latest TWRP.
Temporarily boot to twrp:
1) boot your phone to bootloader screen (power off, then hold vol-dn while hold power - takes 6 secs or so.
2) plug your phone to PC and do "fastboot boot twrp.img" (latest is 3.3.1-0)
- at the twrp screen, if you have 9 dots 3x3, press "cancel" just below that.
- choose Backup and select only the ones you want - I used EFS, Persist, fsg, Vendor.
- make sure it is stored to your SD card. It will be in /twrp/backup/..... Probably best to put a copy on your PC as well.
I use google's backup - in settings/system/backup to backup and restore my apps and settings. I uncheck "contacts" when restoring. your choice.
3) go to backup and tell it to backup now.
4) do 1 and 2 above.
5) now, flash twrp permanently: (since you previously put the latest twrp.zip on your SDcard, choose "install" and flash it. Hit back arrow until you get back to the regular menu and chose reboot, and choose recovery - this will reboot your newly flashed twrp and lock it in. (this method correctly puts twrp in both slots - -a and -b. -> https://twrp.me/motorola/motorolamotox4.html
Now, using the instructions in the thread for the ROM you want to flash, install it.
---------
Okay, you want to get back to stock: I grab the latest-minus-one for my phone from lolinet. At the time of this writing, I use -4 even though -5 is out - this way I will get an immediate update for -5 as the first boot is progressing. ie immediate proof that build is good as far as OTA is concerned.
Expand that zip, and add platform-tools to it. Also add whatever bat files to it that you wish. Attached to this post is the one I just used to get back from Lineage (modified slightly from the one I used to get back from PE 10).
EDIT: I do not know for sure that the bat file without the 2 erases is helpful/necessary so have removed it.
This bat is special! It was made from the xml from XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-6-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip , so if you are using a different zip, you will need to check that the command set is the same - particularly check the number of sparsechunks.
This bat is also very special because it intentionally does not include the two erase modemst1 and t2 commands. This is because I found that these 2 will render your new build as not having mobile, or possibly wifi.
okay, now you are ready to flash stock. Put your phone in fastboot mode (bootloader screen as per #1 at top of post). In windows you can right click on the folder that contains all this junk and choose open command window. Then just type the name of the bat file. I put lots of pauses near the beginning as I assumed I would make mistakes. ymmv
This gave me a perfect result. I will test with superior OS tomorrow.
EDIT: Superior OS back to stock works fine but Pixel Experience 10 (and probably others) required a twrp restore of a previously backed up EFS, Persist, fsg.
-----------
Thanks to @redwoodie and @akillenb .
The bat file is renamed txt to be allowed. You will need to change it back to bat.
EDIT: I do not know for sure that the bat file without the 2 erases is helpful/necessary so have removed it.
This bat is from XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-6-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip - check the xml file in the stock zip you are using to assure this bat is correct for your zip.
future
future2
Wow, you actually did all that? Thought you were risk-adverse on your X4. What an adventurer!
So, your .bat omits the erase modems t1/t2....yet that is what I had to do to get them back after I lost radios. Weird.
Should one leave those commands out if re-flashing stock when one has never flashed a custom ROM?
Thanks for the excellent how-to.
"Superior OS"--meaning 39-6-5?
redwoodie said:
Wow, you actually did all that? Thought you were risk-adverse on your X4. What an adventurer!
So, your .bat omits the erase modems t1/t2....yet that is what I had to do to get them back after I lost radios. Weird.
Should one leave those commands out if re-flashing stock when one has never flashed a custom ROM?
Thanks for the excellent how-to.
"Superior OS"--meaning 39-6-5?
Click to expand...
Click to collapse
Superior OS - custom - SuperiorOS-Phoenix-payton-UNOFFICIALwgapps-20200216-1735.zip
I'm only going to do 3 and I picked those based on views.
It's all your fault! Then akillenb seems to have success so I jumped in. Key is taking backup of all those little partitions. If I hadn't done that I would have been immediately sc***ed.
I discovered the prob with the erases when I was trying to fix PE 10. I would restore EFS, erase t1,t2, and EFS was zero again. So DUH! So I made that bat file and tried it with Lineage and it worked perfectly. The only thing that takes time with this is waiting for all my apps to get put back on, but at least that is automatic. It also makes it easy to build a custom ROM.
Now everybody gets to shoot holes in it!!!
If people going back to stock flash proper firmware retin =retin only ,retail=retail firmware , after sept patch (retin user) moto modify retin modem this leads to no wifi and no network ,this happen when people flash different firmware for fun ,it can be fixed by restoring efs,persist
For retin users I already made script and firmware for this
I already explain this on telegram
---------- Post added at 04:42 PM ---------- Previous post was at 04:37 PM ----------
For twrp there is modified version of twrp made by syberhexen ,it can decrypt data
OP changed: EDIT: Superior OS back to stock works fine (as does Lineage 16) but Pixel Experience 10 (and probably others) required a twrp restore of a previously backed up EFS, Persist, fsg.
I doubt the premise of removing the 2 erases of t1 and t2 so that has been removed. The crux of this guide is simply take backups of EFS and a few other files before making any mod.
Hi all,
Just wanted to give a background story as to why I formatted the Flash by accident on my device. I received the phone not too long ago and was excited to venture into the possibilities of testing and trying out different images. Unfortunately without backing up the device I kind of jump the gun and formatted the drive after I ran into some issues thinking I could restore it with the Stock ROM files. To my horror I found out that not all ROMs were included when reimaging the Stock Roms.
So, here I am. The device is working ok, but these are the issues I'm facing below:
- Partially lost of cellular signals - (Flashing "Modem.bin could resolve this, but don't know where to flash it or what folder structure)
- Wifi working inconsistently - (Stock Roms, does include a "Modem_bin" folder with the files, but again don't know where to flash it)
- Don't have all the calibrations files (Maybe I do, but don't have the correct partition or where it would be placed)
- The Databases were also included, but again don't know where to flash it
- Lost IMEI/BaseBand - (Fixed by flashing IMEI numbers through SN Writer Tool)
- Lost Google Device certification - (Fixed by flashing Attestation files with SN writer tool)
Few things I need help with:
- Does anyone have the full structure of their Doogee V20 phone that does not mind pointing me in the right direction of where to flash the Modem.bin files to?
- Also, if IMEI and SN is corrected, does it means now that the NvRam and NvData info is all there or partially there?
Thanks in advance and hope my insights or issues helps other to avoid my mistakes.
I have attached the scatter files and stock roms if you have any way of extracting what I need from them I would highly appreciated it.
Scatter files : attached
Stock rom : Here