Quantcast
Channel: ZTE Blade / Libra ROMs & ROM customisation Latest Topics
Viewing all 33 articles
Browse latest View live

[maybe solved] Touchscreen does not react after flashing an new ROM

$
0
0

Hi,

i have an B05 OLED SF. Running fine with Seb404s r6 ROM. Now i have tried to flash a newer Version like Seb404s R8 or R9. After flashing the phone boots in the normal way, but the touchscreen does not react. Unlock the screen or SIM input is not possible. The notification-LED is flashing red.

Same issue with FLB-Froyo G2 ROM.

Flashed with Clockwork 2.5.1.8 and both partitions wiped. MD5 sums are correct.

further information:

going back to Seb404s R6 by clockwork the touchscreen function is fine.

Can sombody help?

Thanks Seb.


[ROM] [CM10.1+AOKP+PA3] Root Box for ZTE Blade (Updated 17/9/13)

$
0
0

RootBox.jpg


Based on Android 4.2.2

This is a combination of these three popular ROMs

Description

The struggle to find the rom you need is over. Some people like CyanogenMod, Some prefer AOKP, Some like the advantages of Paranoid Android

We have picked the best features from CM10, Aokp and PA and combined them in a single rom so you get the experience you deserve



INSTALLATION INSTRUCTIONS:

Download ROM, GAPPS on your SDCARD

LATEST ROMDOWNLOAD

GAPPS 4.2http://d-h.st/opz Thanks to KonstaT

 


Boot into CWM Recovery
Optionally, but HIGHLY RECOMMENDED: BACKUP YOUR CURRENT ROM
Wipe Data/Factory Reset (Mandatory if you're coming from any other ROM!)
Wipe Cache
Mounts/Storage > Format System (Mandatory if you're coming from any other ROM!)
Advanced > Wipe Dalvik Cache
Install from zip > Select downloaded ROM
Install from zip > Select download GAPPS
Reboot (might take a while,pls be patient!)


> Minimum System Partition: 160MB <

CREDITS:
KonstaT - without him, this wouldn't be possible. BIG Thanks!

Daemond

Ganster
ParanoidAndroid Team
CM Team

AOKP Team

RootBox Team

KNOWN ISSUES:

Bluetooth sometimes might not initialize (workaround: toggle BT off/on until it starts searching)

ROM Control: Navigation ring incorrect scaling (workaround disable pie from appearing at bottom)

ROM Control: LockScreen targets scaling (warkaround select targets by tapping lower part of lockscreen image)

ParanoidPreferences: Backup not functioning

As any of my other work, this ROM has been compiled from sources.

SOURCES: Device / Kernel / Proprietaries / Base / Legacymod

paying 5$ to whom ever can help me.. [ZTE BLADE]

$
0
0

Hello there Modaco Hackers! :)
I really ADMIRE your work you've done in the past few years for our antique ZTE BLADE little fellow :).

I've got a slight problem i'm afraid. My touchscreen does not react after flashing Eco CM7 or Eco CM9 ROM's. (it only works for 0.5sec after i turn on/off the lock button) it is NOT a hardware issue, as my phone works dandy with standard Cyanogen cm7 Nightly, or Swedish snow RLS7. (i havent tried newer generation ROM's such as Zeelog's)
I too wish to have a stable fast snappy build, with low battery drainage, such as any of these two mentioned!
I have spent countless hours trying to get these to work on my machine (touchscreen that is) but in vain. I'm afraid only jventura himself, or someone with knowledge of editing kernels can help me :(.

I shall quote a guy who managed to somehow fix this issue, but he doesn't replies to my PM, nor does anyone on forum topics seems to read my cries. His forum name is leromarinvit.
Here it goes:

Quote


I finally figured out what the problem is (on my device, at least): for some reason, the touchscreen controller is in the wrong mode (bootloader mode, due to configuration CRC failure) when booting. A reset fixes it for me.
BUT: This is not an exact copy of what the ZTE kernel does, since I haven't been able to find their changes. It's possible that they actually configure something and my kernel doesn't work for everybody. So please test it and report whether or not it works for you!

Note: The initramfs is from Swedish Spring RLS4b and I haven't tried it with anything else. But if it does indeed fix the problem reliably, the same kernel changes will work for every custom ROM....

 

As far as i understood he somehow edited kernel to not have dual AMOLED / TFT but only one type of touchscreen enabled. Maybe you can understand what he did there, coz i sure as hell cant :(.

i'm looking forward for any kind of help or reply here, and i'm even willing to reward a brave soul who invests some of their time in fixing my issue!
ivanGrozni

::Source material::
topic where they fixed it:
http://www.modaco.com/forums/topic/331696-maybe-solved-touchscreen-does-not-react-after-flashing-an-new-rom/?page=7
Eco CM9 ROM: http://www.mediafire.com/download/8ze7wtt27c6wxt8/Eco-CM9-20130723-stable-blade.zip

Eco CM7 ROM: https://www.dropbox.com/s/kfcgg3izlp1cjks/Eco-CM7-20130722-stable-blade.zip
 

QUESTION goes: Can anyone help me editing Eco's Kernel (either cm7 or cm9), so that my touchscreen starts working after flashing it?

Creating new rom help

$
0
0

Right thought I would start fo simple and just try editing around with one of the pro-built ones, in this case flb. At first just deleted the touchpal.apk. I did this by unzipping the flb-froyo-blade-r6.zip, then deleting the said .apk. I then zipped it back up under the same name.

However when I go into clockwork to flash I get this error:

Opening update package...

E:opening /res/keys No such file or directory

E:Failed to load keys

Installation aborted

Can someone be so kind as to tell me why?

[DEV][ROM][24.7.] CyanogenMod 10.1 (Android 4.2.2)

$
0
0

This is my port of CyanogenMod 10.1 for ZTE Blade. It is unofficial and unsupported by the CyanogenMod team. This ROM is mainly for developers/testers/advanced users. I'm really not interested in hearing whining about non-working things (and questions when they will be fixed), actually I couldn't care less if you have issues with this ROM. ;) There's instructions/sources in the third post to build CM10.1 yourself. If you must have something fixed right now - you better do it yourself.

post-834050-0-58159400-1356078847_thumb.post-834050-0-46040400-1356078867_thumb.post-834050-0-69493600-1356078903_thumb.post-834050-0-59053500-1356078887_thumb.

cm-10.1-20130724-KonstaKANG-blade.zip
http://d-h.st/4bw
md5:3bc42f767f9a85462ad76895f00f0b4f

gapps-jb42-20130805-KonstaKANG.zip
http://d-h.st/opz
md5:680e41c4744c4b300aac52683acd05d2

You'll need at least 160mb system partition for the ROM and gapps to fit. Both gen1->gen2 and G2 TPTs are available at Amphoras' site. Gen3 patch for CM7/9/10/10.1 available at my CM9 thread.

Working:

  • Wifi
  • RIL (mobile network & data)
  • GPS
  • Bluetooth (& bt-tethering)
  • Audio (playback/input/routing/headphones/etc)
  • Camera (photos, camcorder & panorama)
  • Hardware acceleration and OpenGL rendering
  • Hardware video decoding & encoding
  • SD card
  • USB-storage & adb
  • USB-tethering
  • Wifi-tethering
  • Touchscreen/multi-touch
  • Sensors
  • LEDs
  • FM radio

Not working:

  • ???

Sources:

Thanks:

  • CyanogenMod team & everyone who's been working on CM10.1

ZTE Blade s6 freez pls help me

$
0
0

hello every one

pls help me to fix my smartphone i just try to recovery it by useing frimware by sd card and i think i put the wrong update frimware 

when i start it this beganing work good and after than the phone torned off and won't turn on againe

when i put it in charger its give me blue led shown allways

pls who can help me fix it

thanks a lot and sorry about my english language

Recovery for ZTE T-U880

$
0
0

Hi everyone

Note: Don't flash any thing from this thread on your ZTE Blade GEN1/GEN2/x880/v880).

If you want to try/test, flash it only on ZTE T-U880, for more details about ZTE T-U880, visit Link.

Clockwork version working on ZTE T-U880

Found it on some chinese website, ClockWork_ZTE_T_U880

- GEN1/GEN2 clockwork recovery is not working on this device.

- Extracted the latest version of clockwork 4.0.0.5 GEN2 by Sebastian404, after some modifications it's working on the device.

Modifications to Sebastian404 Clockwork V4.0.0.5 (attached)

- Extracted the ramdisk.img contents from the clockwork version 2.0.5.9 found working on the device.

- Extracted the ramdisk.img contents from the clockwork version 4.0.0.5.

- Replaced the initialization files of clockwork version 4.0.0.5 with the files of clockwork version 2.0.5.9.

- Deleted the kernel.img from clockwork version 4.0.0.5

- Repacked the stuff.

- Rebooted into recovery mode, no more blank screen.

Problems

- Still can't do nandroid, got an error "Error while backing up boot image!"

- Clockwork displays upside down.

- Up/down volume keys are swapped.

Please help me in removing these problems.

Thanks in advance.

Rec_ZTE_T_U880_v1.img

[GEN2] Proper Gen2 TPT Generator/Extractor

$
0
0

FOR EXPERIENCED USERS ONLY!

With a lot of help from my friend CodeNeos and based on cpg's research, I present you, the easy-to-use, informative, Gen2 TPT extractor/generator!

This simple tool makes life easy - not just extract and repack on the blind, see all the information you need!

Everything ordered on a nice UI, easy to use, yet effective, fast, and powerful!

Features:

- Extract any BIN file

- Create a BIN file from MBN and IMG files (partition and partition_zte mbn's are required, tool checks for that)

- See a content of a BIN TPT update without extracting it

- Extract only selected files

Coming:

- Partition editor for Gen2 firmwares

- YAFFS2 browser to go deeper!

- A nice all-in-one GUI

To work, these tools require .Net4!

post-742765-1305421723_thumb.png

post-742765-1305421715_thumb.png

Your look may differ from the seen - although should be almost the same as on the pictures.

Changelog:

2011.05.15 - V1.1

- Extractor: Extract selected function

2011.05.15 - V1.0

- Initial release

WARNING

This tool is NOT for beginners, or intermediates. This is to help the life of the developers, so, if you DON'T KNOW what you're doing, STOP NOW. Do NOT even download it.

Also, do NOT mix Gen1 and Gen2 TPT files, only if you know what you're doing! It is EXTREMELY DANGEROUS!

I do not take any warranty if your phone bricks, burns, explodes, barkes from using this tool. You've been warned.

Gen2_TPT.zip -- MD5: 1e4bd2d4e1bec3cc144c8e32943ef34c


[APP] Ask Mr Pigfish

$
0
0

As discussed here there are now two kinds for ZTE Blades on the Market and ROMs for one cannot be used on the other and so on.

So far all Blades that have been sold with Android 2.1 uses the same memory base address while all known Blades sold with Android 2.2 uses a different one.

Phones sold with Android 2.1, from now on called Gen1 phones, loads it's kernel to 0x02a00000 while phones sold with Android 2.2, from now on called Gen2 phones loads it to 0x02600000.

If you are in doubt on what type you have you can use this app and it'll tell you.

https://market.android.com/details?id=com.apedroid.pigfish

post-750537-1300708658_thumb.png

Screenshot from a phone sold with Android 2.1 (Gen1):

post-750537-1300708663_thumb.png

Frequently asked questions

Q: Does it matter?

A: Yes, flashing a ROM for one type on the other type will end up with a non-booting phone.

Q: Can I brick my phone if I flash the wrong version?

A: Propably not, flashing the correct ROM should bring it back to life.

Q: What if I do a TPT install, can I brick it then?

A: No one have tried asfaik, you either end up with a fully working Gen1 phone or an expensive paperweight. Either way there will be no way back unless we get our hands on a TPT install for Gen2 phones.

Q: WTF is a "pigfish"?

A: It's the evil cousin of the crocoduck.

Pigfish.rar

Gen1 to Gen2 TPT upgrade

$
0
0

Post removed. I didn't realise that I was expected to give one to one support to everybody on the internet because I released something for free. I've been told by the forum admins to post elsewhere.

[Update] Save ur Bricked V880 and also the IMEI

$
0
0

WARNING : PLEASE BEWARE THAT YOU MAY LOSE THE IMEI AND BRICK YOUR PHONE IF OPERATE IMPROPERLY.

AND PLEASE DO BACKUP CURRENT IMEI INFO BEFORE ANY ACTION."

edit : For those who flashed their firmware with hacatae's or hedgepigdaniel's . please keep a backup the channel1.nvm found in the program folder after a sucess run.

for those who bricked ur v880 due to upgrade failure. this guide might help.

some fellas in China already revived the phone by doing this.

Revive a bricked Phone

1. To check whether ur phone could use this method

This guide works only if the phone could run in the DFU mode in Windows: )

To do so, pls turn off the power and unplug the battery.

then press (and hold) both volume + and - buttons and connect ur phone to PC with an USB cable. (no need to put back the battery and pls install the ZTE driver package first)

if everything okay, u will hear the notification sound only that your phone should be remain in a plain black screen.

then u will see " ZTE Handset Diagnostic Interface (DFU) is connect with (COM XX)" inside Windows' device manager in control panel

1.jpg

If the phone cannot boot into DFU mode, then it is really bricked. U need a replacement.

2. If the phone is detected , continue to download this ZTE universal downloader toolset with several firmware packages.

http://hotfile.com/dl/115367515/af3e2a7/v8...covery.zip.html

unzip the program to desktop then replace the .cfg file inside with this :

http://hotfile.com/dl/115438650/db0c6ba/WC...etting.cfg.html

3. Double click to launch USDL_P726CV1.00.00.exe inside

4. login in as Administrator (press the "!" mark to change the ID). then Input the PW: ZTEsmt123

a.jpg

5. enter the main window then u need to setup the communication port number ( the port connected in DFU mode )

press ok and it brings you back the main window.

setup the com port in DFU mode (menu bar > option >port config)

4.jpg

After that, u will see the message that ur phone is running in download mode in Line 1.

If u see the word in red : "Fail". It means something wrong with ur phone motherboard. And u need to contact for replacement

c.jpg

6. then pickup the proper firmware u want to upload to the phone by browsing the path of "SW Directory" at the lower left hand corner

(u need to scroll down in the main window to see this thread)

c1.jpg

there are 3 firmware sets inside the zip u download.

A. GEN 1 Orange Sanfranciso with a partition layout of 136 mb system 15 cache and 289mb data

B. GEN 2 Orange Sanfranciso with a partition layout of 136 mb system 15 cache and 289mb data

C. Unicom Chinese retail version of blade(U X880) , running with 256 mb system ram.

Select pack B. then press start all and wait for it.

[edit@10 July 2011]: thanks for hedgepigdaniel's reminder, to save time, u may flash with a matching partition layout (about 160MB for system partition) to current CM7. with the custom firmware found in his thread(wbaw's V7) : http://www.mediafire.com/?fczy3y0el3zaw6s , extract the file and then replace the firmware set with thoses files from the extracted content(firmware files are located inside the "files" folder).

(if u want to downgrade to gen 1, u better work it out with the Patch Version downloader (provided by hacatae's ). Use this downloader to do so will struck yout phone with Airplane Mode. )

7. then setup the config like this :

Snap-2011-04-23-01-40-44-1.jpg

when everything is ready, press start all to launch the program,

yr phone should be okay when it finish.

************************************************************************

Backup the Original IMEI

For those who wanna perform NV backup or restore should know that,

u can't make a nvm backup or restore unless FTM mode of stock recovery has been launch,

for this action need to be done with the FTM protocol instead of DFU mode.

so just flash back the stock recovery and boot it to FTM mode before running this official downloader.

select both RF/BT/IMEI/ulock info and nv backup option , u will get a proper working nvm for future use. )

Snap-2011-04-24-06-28-04.jpg

*********************************************************************

Restoring AN IMEI

As mention, to get the NV option works , ur have to flash back the stock recovery and get your machne boot into FTM mode.

For person who messed up with their imei ,they can revive it by editing the nvm file and flash it back.

make a backup with ZTE downloader . edit the channel1.nvm with any hex editor

go to offset 0x1105 (Backup by Windows version downloader patch by Ramdir, used fpr wbaw's or hacatae custom firmware)or

0x1215 (Backup by the ZTE universal downloader)

Snap-2011-04-23-03-53-05.jpg

the current imei is store in dec format , an imei : 3 45 67 89 10 12 13 14

will be reordered as 3A 54 76 98 01 21 31 41

first digit settle in this way: (0)3>>3(0), and A=0

get ur self the orignial imei with the sticker on the back of ur phone

reorder it with the above proper format.

save the changes and then restore it with the official downloader

login as administrator, this time change the settings by

enabling the "NV RESTORE" and "RF /BT /IMEI" Option.

and u will have yr IMEI back.

**********************************************************

for those who lose their IMEI with a downgraded GEN1 machine and without a proper backup.

Here is a NVM file (Complete NV iems backup, I just made up a fake imei.):

http://hotfile.com/dl/115553882/d8d599f/Channel1.nvm.html (GEN 1 nvm BACKUP)

IMEI address start from offset 1215, edit it with a hexeditor with proper order.

Restore steps are same as the Gen2 Machine .

Youtube app: "This action isn't allowed", anyone else getting this?

$
0
0

I'm using konstat's android 4.2.2 rom and i get this message when playing videos, opening the app etc. Videos do work but i always get this message. When i try and sign into my account i get the message again and i can't log into my youtube account. Does anyone else have this problem, not sure if it is a problem with the rom or not.

[REQUEST] Android GO for ZTE Blade / Libra / V880 / San Francisco

$
0
0

Yes this old phone maybe called dead...

...but call me nostalgic...

I like this small piece of 2011s crap ;)

Will someone resurrect the ZTE Blade with android GO?
maybe  konstaT is a littl' bit nostalgic, too 3:)  // or just for a POC (Proof Of Concept)...

cheers,

acidophil

Viewing all 33 articles
Browse latest View live