Database Info

[I9020A] Nexus S, Master Clear?

Hi everyone... I've tried searching and seen references to this kind of thing, but no download links or guides...
So I've got my Nexus S (bootloader unlocked, rooted, stock 2.3.4 until attempting the following, I have no Sim card in this phone), and I tried to flash 2.3.6, and while the update appeared to run just fine, the wifi won't turn on, just gives "error". So I attempted several things, reflashing the update, flashing the 4.04 update (which was the original point), etc, but they all give the following; installation aborted, assert failed, error in xxx.zip, "status 7".
Anyways... I'm a bit at a loss, I've never had this problem, or any problems flashing ROMs on other phones or updates. It seems no update.zip, or any .zip, will install. Back in my captivate days, there was a very handy program called Odin, and it had a master clear functionality that brought you back to the stockest of stock. Ideally... is there a tool like this for the Nexus S? I don't care about whether or not it re-locks the bootloader, I can unlock it again in just a couple minutes... but I need help.
I've read guides about "return to stock" but they all involve flashing a .zip. I need a way to push past that, and get back to 2.3.4, or alternatively, a way to completely reinstall 2.3.6.
I know an Odin exists for the Nexus S, but is there a way to use that to reset to stock?
Thank you so much anyone who can help...

Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
And as always, make sure you backup properly before flashing -anything-.
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.

Harbb said:
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
Click to expand...
Click to collapse
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Harbb said:
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Click to expand...
Click to collapse
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?

Dareoth said:
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
Click to expand...
Click to collapse
Some people supposedly had troubles with the ICS update and keeping all data as-is, though i've not experienced it myself, but it is definitely possible and with such a big update, if it's in your power to start fresh it is always the best option. It was more of a general statement, not directed at your situation - something to keep in mind
Dareoth said:
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Click to expand...
Click to collapse
You can flash the latest CWM through fastboot from your PC or Mac, you can grab the latest file from here. Name it whatever you like and put it in a known folder (preferrably current folder) and : fastboot flash recovery recovery.img
Dareoth said:
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Click to expand...
Click to collapse
Of course i do

Great, I'm all set now. Thanks so much.
(Also for linking to that ref guide again, I had read it three times, but I didn't get how to use it until I went in going, I just need the fastboot commands, which is all that guide gives.)

Your welcome mate. All you need for that is setting up the android SDK or essentially downloading platform-tools seperately. There are guides all over the place describing how to do this for Windows, Mac and Linux as it is no different from getting oem unlock to work, they're just mostly disguised as rooting guides.
Once you do it the first time it's quite simple, but it can definitely be confusing before that

problem flashing roms on moto g xt1032

Hi, I'm new to flashing roms and after installing CWM 6.0.4.7 on my xt1032 and rooting whenever i try to flash a rom it gets stuck in the boot animation. I have tried CM 11 Carbon rom and paranoid android. I don't know if I'm using the wrong GAPPS or what. Please help.

Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app

skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
Ok thanks, I will try that when i have some free time. And how do you revert back to 4.3
never mind i found a post on how to testing now

Brick?
skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help

Go back to Stock and start from Scratch.
As long as you can enter fastboot you should be fine.

I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa

A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.

Worked
quizmaniac said:
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.
Click to expand...
Click to collapse
Yes thank you so much I'm back on 4.4.2 You guys are great

hello everyone
I have a question about PaulOBrien superboot root method (look in modaco forum the moto g root method 1).
I have a 16GB Moto G and updated to Kitkat via OTA.
yesterday I used the method 1 (superboot) on windows 7, to root my phone, and run it for the first time and ended on a black screen with green bars (supposedly normal). I power off the phone and turned on and load kitkat normally and noted that the phone was not rooted.
y tried the method for a second time and have the same results (ended on a black screen with green bars), but when kirkat launched, on the initial screen i saw a message "System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable." and the system didn't respond.
I performed a factory reset via stock recobey and kitkat showed the same message but let me in the "i´m feeling lucky button" worked this time. there I noticed that my device was now rooted but non app was able to access the internal memory due to some r/w permissions as I think, because when I try to copy files to the phone via USB cable, I get have the same denial, even whit ADB push i get the same message of permissions denial.
I need a way to solve this because in this actual stage the phone works but the apps have like no access to the memory making them unusable,
for example i cannot take a picture, or download a file, for some reason all google apps not work or force close every time.
I need a way to upload a .img file to the phone in order to perform a recobery or to make a fresh install via fastboot, donn't know how to make the phone let me wrhite files on it. :crying:
(note: sorry for my bad English)

A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
As long as you can enter the bootloader you haven't bricked anything!!! so don't you worry!
I have two questions: when did you download the stock rom, did you check the MD5 ??? Are you sure that it wasn't a bad download ?
Additionally: are you sure that you have downloaded the appropriate ROM? Did you try to flash any other ROM?

will8578 said:
I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa
Click to expand...
Click to collapse
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032

dreezz said:
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032
Click to expand...
Click to collapse
I am having the same issue. I got this xt1032 after it was OTA upgraded to Lollipop 5.0.2 and I downgraded it to KitKat 4.4.4 Stock. Now I'm also getting stuck on the boot animations on every Custom ROM I try to flash on it.
Does anyone know if having the bootloader upgraded due to the Lollipop update has anything to do with this? mine is at Ver. 41.18.
EDIT: I was finally able to flash after Formatting Data from Recovery. Keep in mind this will basically delete everything from the internal storage and you need to put everything back there manually. Always make sure you backup your info/apps/music/fotos before Formatting Data.

ROM installation problems

I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk

A lot of users report issues not being able to flash rom's on 4.4.2 kitkat.
A fix is to downgrade to 4.3, then flash roms.
I dont know why. I bought my device upgraded to 4.4.2 already, and i can flash roms with no issues.
Search the forum for the topic and you will find the info you need.

Roshi69 said:
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It wont backup saying what error?

Twrp just said 'failed' in red writing after the data backup I think. And philz touch said something along the lines of Not being able to write a file into the \clockworkmod folder.
I bought the device with 4.4.2 on it and followed the guides after reading up about the problems etc but TWRP 2.7.0.0 had a lot of reports that everything was working on it so went ahead with it
Sent from my Nexus 5 using Tapatalk

Ya that's strange because philz works great for me. Do you have a USB otg to try an external backup?
Sent from my XT1032 using Tapatalk

I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.

Roshi69 said:
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Click to expand...
Click to collapse
Why dont you use Clockwork mod recovery for flashing Rom. I have flashed 10 Roms with that and all are backed up with out any problems. TWRP has no official support for moto g, and instead of all that why don't you try Cyanogenmod ?

(sorry if my english is not perfect)
Hello,
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
I never had such problems on my Nexus..
Please help me, I don't know what's going on

TheSkweed said:
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
Click to expand...
Click to collapse
Same here. It may be possible to downgrade to 4.3 (see here), but would it then be possible to flash a 4.4.2-based custom ROM ? I'm not sure.

Heres the steps I took.
*******Before device was stuck at bootloop*******
1. Bought phone (XT1032)
2. unlocked boot loader
3. Rooted
4. Flashed Philz Recovery (wouldn't backup rom)
5. Flashed TWRP and CWM with same issue.
6. Flashed 2 ROMs to try it (TweakyOne + C-Rom, Both wouldn't boot. and tried on all recoveries.
********Steps after being stuck at bootloop*******
1. Followed this amazing guide here (https://www.youtube.com/watch?v=laU6NQ0LxR0)
2. Set up the stock ROM again
3. Flashed TWRP 2.7.0.0 via Fastboot
4. Backup worked successfully
5. installed CM11 and setup successfully
6. installed Lego rom just to assure myself (currently running this ROM)
I know this is no solution at all but just wanted to share my steps to see what maybe fixed my phone. possibly the stock 4.2.2 rom I flashed was the solution. Maybe the original factory ROM that came on the phone was the issue?

[Completed] Installing CM over encrypted data = Locked Out!

I've had an LG E970 running the stock ROM for about a year and decided to try out CM. I'm new to this, but I did some research and went ahead and rooted the phone, and then installed ClockworkMod. That went smoothly, so I tried to install CM through CWM and it appeared to work until it finished booting up and led me to the encryption PIN screen. My PIN from the stock ROM won't open it. CWM can't mount the encrypted data partition to wipe it.
I can boot to CWM or the CM encryption screen. I tried doing a restore on CWM but keeping getting MD5 errors. I haven't had any luck finding the stock ROM anywhere online, I tried an LG tool to get the kdz but it kept giving me error messages when I entered the serial number. I used Titanium to backup everything beforehand, but I can't figure out how to use the files to restore the old ROM. I can put files onto the SD card with my computer, but don't know if that'll be any help. I tried using the ADK to connect to the phone in fastboot, but the phone doesn't show up when I enter the fastboot devices command. Will an older version of CM thats based on the same version of Android the phone was encrypted with be able to open the data? I've tried researching this but everything I've found suggests going about it in different ways and nothing I've tried has worked.
If anybody could give me any help I'd appreciate it.

You may wish to refer to [GUIDE][E970]Using LG Flash Tool To Flash .tot Files {Alternate To LGNPST}[WIP]
Of note to you is Post #8 If you still have issues, you can post on that thread as well.

I followed that guide, but got stuck because the LG Flashtool is identifying my phone as a Nexus 4 and not allowing me to install the E970 files. I think the phone ID changed because the CM version I downloaded was converted from the Nexus ROM. I was able to flash an earlier version, but it had the same problem. Do you have any suggestings for a ROM with the correct phone ID? Is there any other ROM that might be able to decrypt the stock Android encrypted data?
Thanks!

I fixed it!
By plugging my SD card into the computer, I was able to add new ROMs to it and flash them in CWM. I was trying out different ROMs, hoping one would show up as the right phone model in LG Flashtool, and I found one for LG Official Kitkat 4.4.2 Stock. It was able to decrypt the data and now my phone is usable again. I'll revert to the stock recovery, wipe the phone (including encryption) and then start over with CM.
Here's a link to the ROM in case anybody else has this problem later:
http://forum.xda-developers.com/showthread.php?t=2771440 - Thread
http://level99.nighthorsemedia.com/geeb/LG-KK-4.4.2-Fixed.zip - Download Link
Thanks!

[Q] recovery partition not found

Hello,
First off, I am a total noob and probably should not have been messing with my phone before knowing exactly what I was doing. I have a Nexus 5 that I rooted with towelroot. I had xposed framework installed with some other cool tweaks. I should have stopped there. I followed the tutorial on PhoneArena yesterday titled How to download and install the Android L beta update on your Nexus 5. I downloaded and flashed the modified kernel, the SuperSU mode, and the new radio.
I had a backup kernal and recovery set up through Flashify/TWRP. The flash and installation worked. When I tried to flash the N5_L_PREV_LPV79.zip to the newer N5_L_PREV_LPV81C.zip my phone said "your recovery partition couldn't be found. You won't be able to flash recovery images. You can still flash images. It said the same thing about my boot partition. Is there anything I can do to get these partitions back? I know I shouldn't have been jacking with everything without proper knowledge. I appreciate any help you can give me.
Thank you,
Patrick