Jump to content

ZTE Open C £39.99 sim free, unlocked etc etc

Guest hecatae

By Guest hecatae
in ZTE General Discussion

 Share

Recommended Posts

Guest hecatae

Guest hecatae

Posted
Posted

Specifications:

 

Fiefox1.3 OS with 1.2GHz Qualcomm Snapdragon 200 MSM8210, Dual core processor
Size: 126×64.7×10.7mm
Display: 4.0”WVGA (480x800Pixel)
Camera: 3 megapixel camera
Network: GSM 900/1800/1900 MHz | WCDMA 900/2100 MHz
Battery: 1400 mAh
Memory: 512MB LPDDR2/3 + 4GB eMMC | MicroSD (Up to 32GB)
Other: GPS with AGPS, WiFi 802.11 b/g/n, Bluetooth 4.0
Can update to Android 4.4 OS. If you are not accustomed to using Firefox OS.

 

£39.99 at Amazon UK http://www.amazon.co.uk/gp/product/B00KIKDNWO/

 

£39.99 at Ebay http://www.ebay.co.uk/itm/351077440090

 

£54.99 from ZTE UK Ebay store boo http://www.ebay.co.uk/itm/171301269724

 

 

Guest t-bon3

Guest t-bon3

Posted
Posted

Nice rip of my HUKD thread.  :P

 

Will get my hands on my new Open C next week, looking forward to trying out a new mobile OS after 5 years of Android  :rolleyes:

Guest hecatae

Guest hecatae

Posted
Posted

Nice rip of my HUKD thread.  :P

 

Will get my hands on my new Open C next week, looking forward to trying out a new mobile OS after 5 years of Android  :rolleyes:

 

 

:P  :rolleyes:  :P  Mine arrives this week

Guest KonstaT

Guest KonstaT

Posted
Posted
None of these ship to Finland. :( Also the prices on the official ZTE UK and German ebay accounts seem to change every week. Last week it was £44.99 (now back to £54.99) on the official ZTE UK account. And a while ago you could get one from the German account without postages.
 
I'm still yet to purchase mine. Bootloader status still concerns me. It's completely f*cked up if you really can't even flash a custom recovery image to the device's recovery partition without 'bricking' it. Always fastboot booting a recovery image is really not a proper option. I'm not even sure if 'unlocking' the bootloader is really necessary. It will provide a key combination to cold boot to bootloader though but booting to bootloader with the 'locked' bootloader should also be possible with 'adb reboot bootloader'. I wonder if converting this device into a Kis 3 will make any difference in this regard. There's also a similar windows flash tool available to flash Android firmware that is used to flash the unlocked/rooted Firefox OS.
 
I opened a thread with all the available Kis 3 / Open C stock firmware.
Guest KonstaT

Guest KonstaT

Posted
Posted

 

Can Kis 3 android ROMS be flashed to the Open C directly? And vice versa?

 
Asda has the Kis 3 (unlocked?) at £40 
 
 
Fairly sure the description of a MSM7225A chipset is wrong.

 

Open C and Kis 3 are the same device what comes to hardware. There's tools available to go back and forth between Firefox OS and Android. It still doesn't mean that you could directly flash any Open C firmware to a Kis 3 and vice versa. E.g. you still need to use matching stock recovery image to flash official ZTE update.zip's or repack them for a custom recovery. Everything should be possible if you know what you're doing. ;)
 
Yeah, those specs are wrong. ZTE already had a device called Kis 3 previously (or maybe it was only a marketing name in some areas). I think those specs are for the older device, picture is right though. :P
Guest hecatae

Guest hecatae

Posted
Posted

both of mine arrived today, ordered from oxford street on amazon

Guest KonstaT

Guest KonstaT

Posted
Posted

None of these ship to Finland. :( Also the prices on the official ZTE UK and German ebay accounts seem to change every week. Last week it was £44.99 (now back to £54.99) on the official ZTE UK account. And a while ago you could get one from the German account without postages.

Now available for £39.99 also on the ZTE authorized ebay account with international shipping.

 

both of mine arrived today, ordered from oxford street on amazon

Can you confirm that bootloader is inaccessible without unlocking the device? Can you fastboot flash a recovery image after unlocking the device?

Guest hecatae

Guest hecatae

Posted
Posted

 

Now available for £39.99 also on the ZTE authorized ebay account with international shipping.

 

Can you confirm that bootloader is inaccessible without unlocking the device? Can you fastboot flash a recovery image after unlocking the device?

 

 



philip@hecatae:~$ adb devices


* daemon not running. starting it now on port 5037 *


* daemon started successfully *


List of devices attached 


3a11bef device


 


philip@hecatae:~$ adb reboot-bootloader


philip@hecatae:~$ fastboot devices


3a11bef fastboot


philip@hecatae:~$ fastboot oem unlock


...


OKAY [  0.004s]


finished. total time: 0.005s


philip@hecatae:~$ 




philip@hecatae:~/Downloads/Open_c_root/EU_Android+to+FFOS$ fastboot flash recovery recovery.img


target reported max download size of 1073741824 bytes


sending 'recovery' (8334 KB)...


OKAY [  0.334s]


writing 'recovery'...


OKAY [  0.626s]


finished. total time: 0.960s


 




 


 





			
		


		

		
	


	
    


	



					
					
					
				

					

					
					







	

	

	

		

			

				

	
		Guest KonstaT
	

				
				
			

		

		

			

				


Guest KonstaT
			

			

			    Posted 
				
			

		

	

	
	

		




	

		

			

				
    
					
					
					
					
					
				

			

			
		


		

		   
		   Posted 
		   
			
			
				
				
			
		

	


	

    

	

		
		

			

Was that with the untouched 'locked' bootloader? Or why you needed to 'fastboot oem unlock'? Did you try flashing a custom recovery (there's a CWM image available at XDA)?


 


I bought one today as well but it's going to take a week or two to arrive so I don't get to play yet. :P



			
		


		

		
	


	
    


	



					
					
					
				

					

					
					







	

	

	

		

			

				

	
		Guest hecatae
	

				
				
			

		

		

			

				


Guest hecatae
			

			

			    Posted 
				
			

		

	

	
	

		




	

		

			

				
    
					
					
					
					
					
				

			

			
		


		

		   
		   Posted 
		   
			
			
				
				
			
		

	


	

    

	

		
		

			





 


Was that with the untouched 'locked' bootloader? Or why you needed to 'fastboot oem unlock'? Did you try flashing a custom recovery (there's a CWM image available at XDA)?


 


I bought one today as well but it's going to take a week or two to arrive so I don't get to play yet. :P


 






 


 


that was with the ul.to zte kis 3 firmware which is an interesting find, as the ffos recovery image does not allow me to fastboot flash or fastboot oem unlock.


 


so yes out of the box the bootloader is locked, but that 4.4.2 firmware allows you to unlock the bootloader with fastboot oem unlock, no root required.



			
		


		

		
	


	
    


	



					
						
    
							
							
								
  • 
									2 weeks later...
								
    • 
							
						

					
					
					
				

					

					
					







	

	

	

		

			

				

	
		Guest KonstaT
	

				
				
			

		

		

			

				


Guest KonstaT
			

			

			    Posted 
				
			

		

	

	
	

		




	

		

			

				
    
					
					
					
					
					
				

			

			
		


		

		   
		   Posted 
		   
			
			
				
				
			
		

	


	

    

	

		
		

			





that was with the ul.to zte kis 3 firmware which is an interesting find, as the ffos recovery image does not allow me to fastboot flash or fastboot oem unlock.


 


so yes out of the box the bootloader is locked, but that 4.4.2 firmware allows you to unlock the bootloader with fastboot oem unlock, no root required.






Are you absolutely sure about that?


 


My device is completely unlocked out-of-the-box. No need to use any windows flashers or 'fastboot oem unlock'. Just booted with power down pressed to bootloader and fastboot flashed my CWM build to the recovery partition.


 




Edit. Can you post output of following commands in shell after using the Windows flasher to convert to Kis 3?




cat /proc/partitions
ls -l /dev/block/platform/msm_sdcc.1/by-name




I tried flashing GEN_EU_P821E10V1.0.0B10 update after EU_FFOS+to+Android and it didn't fit the /system partition. Luckily I had CWM installed and only fastboot booted the stock recovery image. Otherwise I'd probably already have a brick. :P





			
		


		

		
	


	
    


	



					
					
					
				

					

					
					







	

	

	

		

			

				

	
		Guest hecatae
	

				
				
			

		

		

			

				


Guest hecatae
			

			

			    Posted 
				
			

		

	

	
	

		




	

		

			

				
    
					
					
					
					
					
				

			

			
		


		

		   
		   Posted 
		   
			
			
				
				
			
		

	


	

    

	

		
		

			

Are you absolutely sure about that?
 
My device is completely unlocked out-of-the-box. No need to use any windows flashers or 'fastboot oem unlock'. Just booted with power down pressed to bootloader and fastboot flashed my CWM build to the recovery partition.
 
Edit. Can you post output of following commands in shell after using the Windows flasher to convert to Kis 3?
cat /proc/partitions
ls -l /dev/block/platform/msm_sdcc.1/by-name
I tried flashing GEN_EU_P821E10V1.0.0B10 update after EU_FFOS+to+Android and it didn't fit the /system partition. Luckily I had CWM installed and only fastboot booted the stock recovery image. Otherwise I'd probably already have a brick. :P
I can downgrade from GEN_EU to FFOS to EU_FFOS+to+Android but not the other way
shell@ZTE-P821E10:/ $ cat /proc/partitions
major minor  #blocks  name

 253        0     196608 zram0
 179        0    3817472 mmcblk0
 179        1      65536 mmcblk0p1
 179        2        512 mmcblk0p2
 179        3        128 mmcblk0p3
 179        4         32 mmcblk0p4
 179        5        512 mmcblk0p5
 179        6        500 mmcblk0p6
 179        7      10240 mmcblk0p7
 179        8        500 mmcblk0p8
 179        9       1024 mmcblk0p9
 179       10       1536 mmcblk0p10
 179       11       1536 mmcblk0p11
 179       12     917504 mmcblk0p12
 179       13    1900527 mmcblk0p13
 179       14      32768 mmcblk0p14
 179       15     262144 mmcblk0p15
 179       16      10240 mmcblk0p16
 179       17       1024 mmcblk0p17
 179       18       1536 mmcblk0p18
 179       19          1 mmcblk0p19
 179       20          8 mmcblk0p20
 179       21          4 mmcblk0p21
 179       22      10240 mmcblk0p22
 179       23       6127 mmcblk0p23
 179       32       4096 mmcblk0rpmb
 179       64    1927168 mmcblk1
 179       65    1926144 mmcblk1p1


shell@ZTE-P821E10:/ $ ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root     root              1970-01-11 19:04 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              1970-01-11 19:04 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              1970-01-11 19:04 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              1970-01-11 19:04 cache -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              1970-01-11 19:04 factory -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              1970-01-11 19:04 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              1970-01-11 19:04 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              1970-01-11 19:04 misc -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              1970-01-11 19:04 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              1970-01-11 19:04 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              1970-01-11 19:04 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              1970-01-11 19:04 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              1970-01-11 19:04 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              1970-01-11 19:04 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              1970-01-11 19:04 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              1970-01-11 19:04 safeKeybox -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              1970-01-11 19:04 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              1970-01-11 19:04 sdi -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              1970-01-11 19:04 splash -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              1970-01-11 19:04 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              1970-01-11 19:04 system -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              1970-01-11 19:04 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              1970-01-11 19:04 userdata -> /dev/block/mmcblk0p13





			
		


		

		
	


	
    


	



					
					
					
				

					

					
					







	

	

	

		

			

				

	
		Guest KonstaT
	

				
				
			

		

		

			

				


Guest KonstaT
			

			

			    Posted 
				
			

		

	

	
	

		




	

		

			

				
    
					
					
					
					
					
				

			

			
		


		

		   
		   Posted 
		   
			
			
				
				
			
		

	


	

    

	

		
		

			





I can downgrade from GEN_EU to FFOS to EU_FFOS+to+Android but not the other way






Thanks, partition layout is completely different than on Firefox OS. /system is slightly larger, /data is a lot larger and they've dropped the separate partition for internal sdcard (using emulated sdcard on /data/media). Not sure what would be the best way forward. :/ I'll probably end up dropping the internal sdcard all together again.


 


I also liked the ability to cold boot to bootloader with volume down pressed with Firefox OS, that's now gone with Android. Ideal would be probably some combination from both firmwares.



			
		


		

		
	


	
    


	



					
					
					
				

					

					
					







	

	

	

		

			

				

	
		Guest hecatae
	

				
				
			

		

		

			

				


Guest hecatae
			

			

			    Posted 
				
			

		

	

	
	

		




	

		

			

				
    
					
					
					
					
					
				

			

			
		


		

		   
		   Posted 
		   
			
			
				
				
			
		

	


	

    

	

		
		

			

Thanks, partition layout is completely different than on Firefox OS. /system is slightly larger, /data is a lot larger and they've dropped the separate partition for internal sdcard (using emulated sdcard on /data/media). Not sure what would be the best way forward. :/ I'll probably end up dropping the internal sdcard all together again.
 
I also liked the ability to cold boot to bootloader with volume down pressed with Firefox OS, that's now gone with Android. Ideal would be probably some combination from both firmwares.
This is the 4.2 Virgin UK Rom, my automatic brightness works.



			
		


		

		
	


	
    


	



					
					
					
				

					

					
					







	

	

	

		

			

				

	
		Guest KonstaT
	

				
				
			

		

		

			

				


Guest KonstaT
			

			

			    Posted 
				
			

		

	

	
	

		




	

		

			

				
    
					
					
					
					
					
				

			

			
		


		

		   
		   Posted 
		   
			
			
				
				
			
		

	


	

    

	

		
		

			





This is the 4.2 Virgin UK Rom, my automatic brightness works.






I highly doubt that. And if you had ALS, you'd also have proximity. Screenshot of CPU-Z sensors screen or no way I'm going to believe you. :P Where is this sensor physically located? I can only see one hole on the front of my device and that's where notification LED is.



			
		


		

		
	


	
    


	



					
					
					
				

					

					
					







	

	

	

		

			

				

	
		Guest hecatae
	

				
				
			

		

		

			

				


Guest hecatae
			

			

			    Posted 
				
			

		

	

	
	

		




	

		

			

				
    
					
					
					
					
					
				

			

			
		


		

		   
		   Posted 
		   
			
			
				
				
			
		

	


	

    

	

		
		

			





I highly doubt that. And if you had ALS, you'd also have proximity. Screenshot of CPU-Z sensors screen or no way I'm going to believe you. :P Where is this sensor physically located? I can only see one hole on the front of my device and that's where notification LED is.






 


gallery_19680_3_11466.png



			
		


		

		
	


	
    


	



					
					
					
				

					

					
					







	

	

	

		

			

				

	
		Guest KonstaT
	

				
				
			

		

		

			

				


Guest KonstaT
			

			

			    Posted 
				
			

		

	

	
	

		




	

		

			

				
    
					
					
					
					
					
				

			

			
		


		

		   
		   Posted 
		   
			
			
				
				
			
		

	


	

    

	

		
		

			

But you don't get any reading from those sensors so they don't actually work either? At least not on my device! Virgin UK kernel has TAOS sensor driver built in and using sensor HAL from that build on my CM11 gets it recognized. Maybe some Kis 3 variant has that sensor hardware but not Open C.


 


Where is the sensor supposed to be located? Can you see it?



			
		


		

		
	


	
    


	



					
					
					
				

					

					
					







	

	

	

		

			

				

	
		Guest hecatae
	

				
				
			

		

		

			

				


Guest hecatae
			

			

			    Posted 
				
			

		

	

	
	

		




	

		

			

				
    
					
					
					
					
					
				

			

			
		


		

		   
		   Posted 
		   
			
			
				
				
			
		

	


	

    

	

		
		

			





But you don't get any reading from those sensors so they don't actually work either? At least not on my device! Virgin UK kernel has TAOS sensor driver built in and using sensor HAL from that build on my CM11 gets it recognized. Maybe some Kis 3 variant has that sensor hardware but not Open C.


 


Where is the sensor supposed to be located? Can you see it?






kis_3_zoom_front.png


notification on is top left, proximity light sensor is top right, taken from here http://store.virginmedia.com/virgin-media-mobile/pay-as-you-go-phones/zte-kis-iii/zte-kis-iii-tariffs.html


 


if I hold my thunmb over it's rough location i do see some gradual dimming, though that may be the notification bar trying to respond



			
		


		

		
	


	
    


	



					
					
					
				
			
			



		

	


	
	
	
	
	
		
	

			
				
				



	
	
		

			
Please sign in to comment

			
You will be able to leave a comment after signing in

			

			

			Sign In Now
		

	


			
		

	

	
		

			

				
					


    
          Share
    

    

				
				
                

                


				
			

		

	







	

		
			
				Go to topic listing
			
		
	

	




						


					

					


					

				

			

			
		

		
		


	

		×
		

			
				

					
				

			

			

			

			
		

	






	

		×
		

			
    
				
  • Create New...
    • 
				
			

		

	



		






















	

		

			
Important Information

			
By using this site, you agree to our Terms of Use.

		

		

			
			  I accept