Database Users

Un-rooting a rooted N1?

So I bought a N1 yesterday, cant wait till it gets here, The phone is rooted and has 2.2 on it, Is there anyway I can un root it and just be at the latest stock android? I just prefer to be at the normal stock updates, never really been big into rooting and ROMS etc unless I have too, anyway so yea thats my question and is it difficult?
Thanks in advance!

Take a look in the Development board, there is a sticky that shows you how to restore stock 2.1. Then it will prompt you to upgrade to Froyo.

solidkevin said:
So I bought a N1 yesterday, cant wait till it gets here, The phone is rooted and has 2.2 on it, Is there anyway I can un root it and just be at the latest stock android? I just prefer to be at the normal stock updates, never really been big into rooting and ROMS etc unless I have too, anyway so yea thats my question and is it difficult?
Thanks in advance!
Click to expand...
Click to collapse
Yeah, you can't re-lock the bootloader, but you can load up the stock ROM as the post above says. But since it's all already done, you might consider looking into a ROM which fits you. There are several which are "almost stock" but have nice enhancements, like the Enom rom.
I too am an unrooted stock ROM kinda guy, I don't have the time or patience to deal with fiddly stuff on my phone anymore, as I need to pull it out, see where my next meeting is, and get there. Not pull it out and realize it's in a Standby of Death or some other random problem. There are pluses and minuses to using a non-stock ROM, weigh them.. I'm starting to myself... I want a black notification bar and a handful of other small things, but to get them it requires a lot of work (unlock, flash new rom, set up all of my apps again, figure out new stuff in ROM, etc..)

Yeah you could also use modaco ROM. Those are stock ROMs with a few extras like super user access, which is a must have. Etc.

Is rooting similar or at least easy like the HD2? I had one of those and putting Custom ROMS was so simple!

Should be fairly simple if cyanogen is on it.
Sent from my Nexus One using XDA App at 35000 feet

uberamd said:
Take a look in the Development board, there is a sticky that shows you how to restore stock 2.1. Then it will prompt you to upgrade to Froyo.
Click to expand...
Click to collapse
Can you please link the thread, Ive looked and looked and I cant find a unrooting tutorial.

Nexus One Android Development -> Original Shipping - Tutotrial
The thread is stuck right at the top of the forum -_-

GldRush98 said:
Nexus One Android Development -> Original Shipping - Tutotrial
The thread is stuck right at the top of the forum -_-
Click to expand...
Click to collapse
WOW....I feel dumb....thanks lol

I am assuming you know how to use ADB and Fastboot
Hmm, Is there a thread explaining those 2 things?

solidkevin said:
I am assuming you know how to use ADB and Fastboot
Hmm, Is there a thread explaining those 2 things?
Click to expand...
Click to collapse
If all you want to do is flash stock rom, you don't even need to know what those two are. The stickied tutorials are dead simple.

Can somoene confirm Im gonna be doing this correctly.
Step 1. Disable backup my settings under privacy settings.
Step 2. unzip the original shipping ROM and put it somewhere you can find.
Step 3. Plug in Nexus One with USB to computer (enable usb and debug modes)
Step 4. adb reboot bootloader (which will boot into the bootloader)
Step 5. Confirm fastboot connection fastboot devices
Step 6*. fastboot erase userdata
Step 7*. fastboot erase cache
*If step 6 and 7 does not work, and if you have Amon_RA's recovery installed, you can do a factory data wipe from there.
Alternately, you can also do a factory data wipe within Android. Settings => Privacy Settings => Factory Data Reset.
Thanks to Brian and setzer715.
Step 8. Go to the directory that you stored your unzipped files.
Step 9. fastboot flash userdata userdata.img
Step 10. fastboot flash boot boot.img
Step 11. fastboot flash system system.img
Step 12. Skip to step 13 if you want to keep recovery (assuming you have a modified recovery such as Amon_RA's recovery). If not fastboot flash recovery recovery.img
Step 13. fastboot reboot
Step 14. After the system boots up and while setting up skip setting up with the google account and you can setup accounts later. This will prevent the phone from pulling down the previous settings (downloaded apps, wallpaper etc) from google.
Step 15. You are done. Enjoy.
Ok so I downloaded, installed and updated Android SDK, it seems to be all set, now when I follow those steps, I connect the phone first then for instance step 4 I should start "adb" then type in reboot bootloader, and for step 5 I should start up "fastboot" then type devices, etc etc? Is that correct?
thanks in advance.

Anyone? Please.

solidkevin said:
Anyone? Please.
Click to expand...
Click to collapse
look here to learn how to setup adb
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/

Anyone know how to downgrade roms?

I have the updates installed but the unlock and selection sounds don't work. They were for a bit but then stopped. I tried to rename the rom update.zip but the phone stated it was an older version and could not flash it. It then forced me to reboot, end of story.
I want to reboot back to OG rom and then apply the updates over it.
Can anyone help me out.

Do it with paulobrian's method.

~~Tito~~ said:
Do it with paulobrian's method.
Click to expand...
Click to collapse
Assuming he knows what that is. OP, were you doing the fastboot flash method using the command prompt on Windows?

~~Tito~~ said:
Do it with paulobrian's method.
Click to expand...
Click to collapse
Now if i only knew what this really meant.
* Download the 1.19 stock ROM from here
* Download fastboot from here
* Extract the fastboot zip to the same directory as the ROM
* Turn your G2 on with the action button held (fastboot mode) I've never heard of an action button
* Type 'fastboot-windows oem rebootRUU' (case sensitive, replace windows with mac or linux as required) No where does it give me the option to type anything in.
* Type 'fastboot-windows flash zip PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459
signed.zip'
* Let this finish, then type 'fastboot reboot' and apply the OTA
P

EfemaN said:
Assuming he knows what that is. OP, were you doing the fastboot flash method using the command prompt on Windows?
Click to expand...
Click to collapse
I used this method to revert back to stock cuz i deleted the goggles. But, the click sounds only worked for an hours then stopped.
-------------------------------------------------------
Download PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b _26.02.01.15_M2_release_149459_signed
(the link is somewere in this thread)
*then read name it to PC10IMG.zip
*Put it on the root of your sd card.
*Power down phone
*Power up phone holding Vol Down and Power button.
*Phone will boot into fastboot i believe and then it will look for PC10IMG
*It will ask to flash it you use the vol key and power buttons to do that.
*Once it done it will reboot the phone and all your data will be gone and your be back at factory setting.
Then just rename the ota to update.zip and flash via recovery.
*remover the PC10IMG.zip from root of sd card
* Get back into the fastboot on the phone (setups up there^)
*this time use the vol button to go down to recovery.
*Once at recovery hold vol up and hit the power button.
*then vol down to flash update.zip

ddgarcia05 said:
I have the updates installed but the unlock and selection sounds don't work. They were for a bit but then stopped. I tried to rename the rom update.zip but the phone stated it was an older version and could not flash it. It then forced me to reboot, end of story.
I want to reboot back to OG rom and then apply the updates over it.
Can anyone help me out.
Click to expand...
Click to collapse
First make sure you media vol is on and up. If its not then u wont be able to hear it. And second you can downgrade the phone. All andiords are downgrade block unless we have custom bootloader. And the steps poste above are mines I orignaly posted them so I know it wont work after u applyed the ota
Sent from my T-Mobile G2 using XDA App

You cannot downgrade using either of the fastboot methods (fastboot-windows or fastboot on your phone) listed above after you have applied the OTA. It checks the version and then tells you that the downgrade version is old.
So far, I have not seen a solution to downgrade.

cparekh said:
You cannot downgrade using either of the fastboot methods (fastboot-windows or fastboot on your phone) listed above after you have applied the OTA. It checks the version and then tells you that the downgrade version is old.
So far, I have not seen a solution to downgrade.
Click to expand...
Click to collapse
This is correct, verified live in IRC by people in #g2root

Just call tmob and tell them your hinge is loose! Exchange phone, don't apply OTA.

All the sounds stopped working on my phone a day ago, had to do a hard reboot to get them working again.
OTA was applied.

Well, I called tmobile and told them my issue. I also told them I had already tried to reset my phone in attempts to fix the sound issue to no avail. I've got a new or like new G2 on it's way.
I'm going to be kinda bummed if it's a like new (refurbished) model, but then again it can't be older than the one I got now.

[Guide] {Arc/Arc S} All-in-one: bootloader, rooting, kernel, ROM (4.0.3 firmware)

DELETED!
Don't want to risk anyone getting bricked, because of me giving you the wrong info.

Thanks for this topic, but I've a few questions:
- If I unlock the bootloader, can I still use TrackID or is it completly over?
- Which other Sony apps are effected (except WisePilot)?
- Can I re-lock the bootloader with FlashTool as written in the forums here to use TrackID again?
- Can I flash a new bootloader with FlashTool, too? I didn't read anything about it and I don't want to use any sony page.
- Currently I'm using Xperia CWM (from Google Play) with a stock kernel and different ROMs. It works so far. Is CWM included with every kernel?

1) Download TrackID from the market. That's a better and newer version than the one supplied with the ROM, plus it works even with an unlocked bootloader.
2) FB Like won't work if you've got the bootloader unlocked. But I hardly think that's a deal breaker.
3) Yes, you can relock the bootloader but the original TrackID still wouldn't work as you would have erased the DRM keys. (The newer version still works).
4) You can't flash a bootloader. You can flash kernels and ROMs.
5) Most custom kernels have CWM recovery within.
Cheers! Hope that answered your questions.
Swyped from my SE Xperia arc (LT15i) using Tapatalk 2

xtacy! said:
4) You can't flash a bootloader. You can flash kernels and ROMs.
Click to expand...
Click to collapse
This was a typo...
Did I mention that I'll flash a new kernel soon? I'll try it with FlashTool.

1. Can I unlock & root after official ICS update?
2. Can I install custom ROM using this(http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Arc:_Full_Update_Guide) method?

Just to be sure: I can only unlock the bootloader of my Arc S with the Sony-method? Is there another free way to do it?
In FlashTool I've to select "Flash" -> "Fastboot Mode" -> "Reboot into fastboot mode (via ADB)" -> "Select kernel to Flash" and flash the kernel file?
edit: All my questions were answered in the last hours.

hi, can i root my arc s with ICS with DoomLor method?

Hi,
I did steps 1& 2 (unlocking & rooting) but nothing seems to have happened. How can I tell if it worked? I followed everything to the T and got no errors.

Ive just checked and my bootloader is unlocked butthe pphone does not appear to have been rooted (I checked using a root checker app). Can you think of any reason for this? Should I just try again or could that cause me problems?
Thanks
edit:
Do I need to do step 3 & 4 before it is fully rooted? I assumed I could stop after step 2...

anybody? please help. im not sure if i should try to flash the rom if it isn't rooted yet, or is that what i need to do to complete the process?
soooo confused

twelveways said:
anybody? please help. im not sure if i should try to flash the rom if it isn't rooted yet, or is that what i need to do to complete the process?
soooo confused
Click to expand...
Click to collapse
The root method posted doesn't work with the latest ICS (431) update.

I'm running Android 2.3.4 and the build number is 4.0.2.A.0.62.

thanks for that
i have arc s and when i tried the way you say
it says already unlocked
is that normal ??
or there is a problem ??

This has only been tested on Arc S with 4.0.3 firmware.
THIS WILL NOT WORK ON THE LATEST FIRMWARE (4.0.4)
Sorry for not answering guys, thought my thread was dead.
Will bookmark.

Oscar-Mark said:
THIS WILL NOT WORK ON THE LATEST FIRMWARE (4.0.4)
Click to expand...
Click to collapse
Worked for me.

Update: Thread edited a bit.
If anyone has got this working on the latest (4.0.4) firmware please tell, (reply, no PM)

please can you reup the part of kernel flashing? i thought this thread is still existing, i deleted the hole system to prepare it for new rom and kernel flashing and no its deleted?! please help me my phone doen't boot i need a tutorial to flash the kernel, this tut herer was extreme good and noob friendly, please reuppload it :C

Google fetishist said:
please can you reup the part of kernel flashing? i thought this thread is still existing, i deleted the hole system to prepare it for new rom and kernel flashing and no its deleted?! please help me my phone doen't boot i need a tutorial to flash the kernel, this tut herer was extreme good and noob friendly, please reuppload it :C
Click to expand...
Click to collapse
To flash a kernel:
This will wipe all your data
Turn off your device, make sure you have atleast one ROM on your SD card in case anything goes wrong.
Put the kernel boot.img in /fastboot/fastboot_with_Android_USB_file/fastboot folder.
Press and hold SHIFT button while right clicking at an empty space in the /fastboot/fastboot_with_Android_USB_file/fastboot folder, and select "open command window here". (you can now release the SHIFT button )
Now plug your phone's USB cable to your computer.
Press and hold the MENU button on your phone, while connecting the MicroUSB connector to your phone.
When the LED turns blue you can release the button, your phone is now in fastboot mode.
Open the command window and insert the text you got in the Kernel thread, most certainly fastboot flash boot FILENAME.img, and press ENTER.
When the Command Window is finished close it and unplug your phone.
Turn on the phone, and when the button backlights turn on quickly press any button. Your phone will now boot into CWM Recovery.
RECOMMENDED: do a full wipe and flash your ROM.
If you want to keep your ROM and data just wipe cache and dalvik.
(If you're coming from a kernel with WiFi modules (ArcNight, DoomKernel) DO NOT do this, it will only mess up your phone.)

[Q] Fastboot Reason: Sticky bit factory_fastboot?

I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.

Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app

skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.

OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app

You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y

skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.

cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?

Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!

More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.

Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.

Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful

Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!

Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:

Edit : Sorry I asked stupid question!

Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.

Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick

ZTE OPEN C 1.4 Rom and Recovery

This is 1.4 rom for ZTE Open C, this needs to be installed on a ZTE Open C ruining an unlocked firefox, if you haven't unlocked your bootloader you can't use this rom.
connect phone to pc via usb cord.
Download rom and recovery
open terminal
adb reboot bootloader
fastboot devices
fastboot boot cw_recovery_dp.img
Once in recovery, screen will be black
in terminal
adb shell /sbin/black_screen_fix.sh
now kill this terminal
open another terminal
adb shell /sbin/cw_recovery.sh
at this point I recommend making a back up.
install rom via adb sideload
reboot.
Download below.
http://www.mediafire.com/download/dyad9ryol1tr9va/cw_recovery_dp.img
http://www.mediafire.com/download/5t303349en3wwv3/signed_1.4_fixed.zip
my roms use stock kernel, comes from Open_C_upgrade_Tool:
http://alturl.com/2bpns

vampirefo said:
This is 1.4 rom for ZTE Open C, this needs to be installed on a ZTE Open C ruining an unlocked firefox, if you haven't unlocked your bootloader you can't use this rom.
connect phone to pc via usb cord.
Download rom and recovery
open terminal
adb reboot bootloader
fastboot devices
fastboot boot cw_recovery_dp.img
Once in recovery, screen will be black
in terminal
adb shell /sbin/black_screen_fix.sh
now kill this terminal
open another terminal
adb shell /sbin/cw_recovery.sh
at this point I recommend making a back up.
install rom via adb sideload
reboot.
Download below.
http://www.mediafire.com/download/dyad9ryol1tr9va/cw_recovery_dp.img
http://www.mediafire.com/download/5t303349en3wwv3/signed_1.4_fixed.zip
Click to expand...
Click to collapse
Thank you I am currently running your build and it is working very well for me! I am just wondering if you can/will provide any updates? I'm going to use this until 1.4 is officially released

KUPOinyourWINDOW said:
Thank you I am currently running your build and it is working very well for me! I am just wondering if you can/will provide any updates? I'm going to use this until 1.4 is officially released
Click to expand...
Click to collapse
Once I feel 2.1 has matured enough, I will release it as well, right now I think 2.1 needs a little more time to mature, updates are still be turned out almost daily for 2.1, so 2.1 is not ready for daily use. 1.4 is good to go as a daily OS.
Glad 1.4 is working well for you, works well for me as well, I use it daily.

vampirefo said:
Once I feel 2.1 has matured enough, I will release it as well, right now I think 2.1 needs a little more time to mature, updates are still be turned out almost daily for 2.1, so 2.1 is not ready for daily use. 1.4 is good to go as a daily OS.
Glad 1.4 is working well for you, works well for me as well, I use it daily.
Click to expand...
Click to collapse
Just for the record, I installed the recovery via OS X's Terminal, then I just put the ZIP of 1.4 on my phone and installed it as if it was a normal update. I'm also using an EU ZTE Open C but it still works completely fine for me

.50 recovery is available no need for adb boot scripts recovery no longer has black screen.
This recovery should support any zip files including kitkat.
http://www.mediafire.com/download/s1a8jbb5zn2yfcp/cw_recovery_50.img

vampirefo said:
.50 recovery is available no need for adb boot scripts recovery no longer has black screen.
This recovery should support any zip files including kitkat.
http://www.mediafire.com/download/s1a8jbb5zn2yfcp/cw_recovery_50.img
Click to expand...
Click to collapse
Hi vampirefo
Nice work.
Would you mind telling me how you were able to fix your black screen issue
I am working on a similar phone, ZTE Concord 2, and any recovery I try to use either gets black screen or just displays the flash screen
The recovery binary is seg faulting, I am able to use adb and stuff. The only recovery binaries that do not seg fault are my stock binary and the stock binary from the Open C, but the binary from Open C has black screen
I think ZTE put some code in the kernel source that prevents some binaries from loading or something, unfortunately ZTE did not release the source code for this phone
Sorry for going off topic in your thread, any info you can provide is much appreciated.
hK

hroark13 said:
Hi vampirefo
Nice work.
Would you mind telling me how you were able to fix your black screen issue
I am working on a similar phone, ZTE Concord 2, and any recovery I try to use either gets black screen or just displays the flash screen
The recovery binary is seg faulting, I am able to use adb and stuff. The only recovery binaries that do not seg fault are my stock binary and the stock binary from the Open C, but the binary from Open C has black screen
I think ZTE put some code in the kernel source that prevents some binaries from loading or something, unfortunately ZTE did not release the source code for this phone
Sorry for going off topic in your thread, any info you can provide is much appreciated.
hK
Click to expand...
Click to collapse
Well I will give you the entire process I used, you can just jump to the end if you want, or read through how I was able to fix black screen.
First I packed the recovery.img with two recovery binaries, one stock other cwm, I used cwm ramdisk, rename stock recovery binary to recovery1.
next I made two scripts, which I put in /sbin black_screen_fix.sh and cw_recovery.sh
black_screen_fix.sh
Code:
#!/sbin/sh
/sbin/recovery1
cw_recovery.sh
Code:
#!/sbin/sh
kill $(busybox ps | busybox grep /sbin/recovery)
Using adb I was able to load and unload stock recovery binary, this actions turned on backlight, also created a log in my backups
Code:
I:Enabling backlightCommand: "/sbin/recovery1"
set default update to fota
So from this info I knew the stock recovery binary was turning on backlight, to figure out how I opened stock recovery binary in a hex editor, and searched for backlight, that gave me .
Code:
/sys/class/leds/lcd-backlight/brightness
which I then added
Code:
write /sys/class/leds/lcd-backlight/brightness 100
to init.rc in recovery ramdisk just below
Code:
write /sys/class/android_usb/android0/enable 1
looks like this.
Code:
# setup_adbd will start adb once it has checked the keys
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
write /sys/class/leds/lcd-backlight/brightness 100
I then removed scripts and stock recovery binary as I don't need them anymore.

vampirefo said:
Well I will give you the entire process I used, you can just jump to the end if you want, or read through how I was
Click to expand...
Click to collapse
thank you for your reply, i think I may have a different issue, but I do appreciate your time

Phone doesn't start after sideload flash. It's stuck on the boot screen (blue background with fox).
Flashing from external_sd doesn't work either because it 'can't mount /external_sd'.
Only way it works when I push the zip into sdcard folder. Flashing takes only a few seconds (suspicous!) - no error message. Then once again I'm stuck on the boot screen.
Any suggestrions?

happyass**** said:
Phone doesn't start after sideload flash. It's stuck on the boot screen (blue background with fox).
Flashing from external_sd doesn't work either because it 'can't mount /external_sd'.
Only way it works when I push the zip into sdcard folder. Flashing takes only a few seconds (suspicous!) - no error message. Then once again I'm stuck on the boot screen.
Any suggestrions?
Click to expand...
Click to collapse
sounds like you didn't unlock your bootloader and tried to flash my rom on a locked bootloader which will cause exactly as you described, the bootloader being locked wont let the boot.img flash, causing phone to boot loop or soft brick.
You need to restore your phone, and this time unlock the bootloader, before trying to flash anything.

hey guys, i cant find tutorial in this forum how to unlock bootloader or rooting for zte open c , would someone give me a link to do it? i am eager to try 1.4 , because zte open c with 1.3 is not smooth enough and has some bugs which i dont like

vampirefo said:
sounds like you didn't unlock your bootloader and tried to flash my rom on a locked bootloader which will cause exactly as you described, the bootloader being locked wont let the boot.img flash, causing phone to boot loop or soft brick.
You need to restore your phone, and this time unlock the bootloader, before trying to flash anything.
Click to expand...
Click to collapse
I used the Open C Upgrade tool to flash that image provided on that site. Thought that's the way to unlock.
How do I solve the soft brick? Open C Upgrade tool doesn't recognize the phone anymore..

Use .50 recovery flash stock kitkat reboot use unlocking tool, then flash 1.4

It's unbricked thanks to this: https://github.com/martensms/zte-openc-rootkit
Sorry I'm a little confused, I didn't get it.
Did you mean?:
1) use .50 recovery
2) flash stock kitkat (via sideload)
3)use 'Open C Upgrade Tool' with the image provided on that site
4) flash 1.4 with the instructions on the first page

Now I got it work (1.4). Don't ask me how.
Basically I used that Open Update Tool with it's image, flashed Kitkat and the installed Firefox OS 1.4.
Always tried to flash via 50_recovery otherwise I got verification errors.

happyass**** said:
Now I got it work (1.4). Don't ask me how.
Basically I used that Open Update Tool with it's image, flashed Kitkat and the installed Firefox OS 1.4.
Always tried to flash via 50_recovery otherwise I got verification errors.
Click to expand...
Click to collapse
Glad you got 1.4 installed, as of right now 1.4 is the best Firefox OS version, 2.1 is very nice and will be better than 1.4 in time.

Hi vampirefo,
I just used your cw recovery to update my Open C. I installed the KitKat rom you also provided and it works great.
Thanks for that
I only had one small issue, the phone says No Service on the lock screen as well as the notification drop down.
It has full bars and can make and receive calls. I have a US ATT sim card in it. In the about phone in settings it
also shows the baseband as unknown.
Aside from that everything works except for the Gallery app.
Thanks Again for the great rom.
Snorkel.
PS
I unlocked the phone with the ZTE update tool for windows and just followed your directions. It's also important to not say yes to the two questions when you reboot from recovery.

snorkel01 said:
Hi vampirefo,
I just used your cw recovery to update my Open C. I installed the KitKat rom you also provided and it works great.
Thanks for that
I only had one small issue, the phone says No Service on the lock screen as well as the notification drop down.
It has full bars and can make and receive calls. I have a US ATT sim card in it. In the about phone in settings it
also shows the baseband as unknown.
Aside from that everything works except for the Gallery app.
Thanks Again for the great rom.
Snorkel.
PS
I unlocked the phone with the ZTE update tool for windows and just followed your directions. It's also important to not say yes to the two questions when you reboot from recovery.
Click to expand...
Click to collapse
Yes it says no service but service works just fine, ZTE adds that info to bootloader, to get service to display one has to run the locked bootloader, which means no root no google playstore.
My baseband shows P821E10B01, I pretty sure that comes from modem, you can flash the modem and then check about phone and see if you have a baseband, which isn't really important.

vampirefo said:
Yes it says no service but service works just fine, ZTE adds that info to bootloader, to get service to display one has to run the locked bootloader, which means no root no google playstore.
My baseband shows P821E10B01, I pretty sure that comes from modem, you can flash the modem and then check about phone and see if you have a baseband, which isn't really important.
Click to expand...
Click to collapse
Thanks for the info. I did flash the modem and it still didn't show the baseband, but most everything works. Only thing that does not work is the gallery app which causes the camera to fail as well. I just downloaded a new camera and gallery app which resolves it for the most part.
Thanks again for the rom, great work.

vampirefo said:
Glad you got 1.4 installed, as of right now 1.4 is the best Firefox OS version, 2.1 is very nice and will be better than 1.4 in time.
Click to expand...
Click to collapse
Sounds great. How good is it (working) so far? Long way to go before it's ready for a daily driver?