Related
Made a huge error.....didnt go through forums and read instructions before trying to Flash a German T-Mobile MDA Compact to a English ROM....
The device is completely dead....
Followed all the steps required to get it back up...It is refusing to do so though....
Used this thread:
http://forum.xda-developers.com/viewtopic.php?t=19500
One thing to note is that I am not using the AC charger, am using the USB cable to charge the phone.
Can someone please helpme...
Haven't got past the bootloader mode...
If you followed the instructions from the other thread, it should have started flashing.
Some things to check on:
1) Did you do a full d2s before you attempted the upgrade? It's always good to have something to fall back on.
2) If you can get to a bootloader screen, all is definitely not lost.
3) Sometimes, it takes 4 or 5 minutes for the "Press to flash" comes up on the screen so be patient with that.
4) Make sure you did exactly a 416 byte copy from the original rom file in to the new flash file.
5) You can only write an nb1 file from the pc AFTER it has been created from the pocket pc. If the SD card has been pc formatted, the nb1 file will write to it but the pocket pc won't recognize it and will just sit there at the bootloader screen.
HTH
I think I fired the MDA
Well I did not create the nbf file from the ppc, downloaded it from the the forum FTP. I do not have the backup of the nbf file. As I mentioned I did not read the forums before trying the update.
I just downloaded the T-Mobile ROM update and tried installing it. Obivousioly it didn't work, Game the dreaded the 112 error in the 3rd step.
Am not even getting the bootlader screen now..
Any ideas on how I can get this device up and running.?...
ok, need some clarification here. "What" are you trying to load (nbf files or nb1 files) and how are you trying to load them (SD flash or the standard USB based upgrade)?
Easy enough to check to see if your device can still get to bootload mode....hold the camera and power switches in at the same time and hit soft reset with your stylus. After letting go of those and you see either "Serial" or "USB" at the top of the screen, you should still be able to recover from this.
Tried with the nb1 files not nbf (sorry abt teh error)..
The bootloader screen was showing up ...unitll I tried the T-Mobile MDAcompact_vers11201
After the 112 error while updating...the device now refusing to get to the bootloader mode.
Have I fried the device and made it unusable....?
hey just got back the bootloader screen...
Take the SD card out, disconnect the USB and tell me what happens when you hold the power and camera buttons in at the same time, then hit the soft reset.
Also, has the unit been charged recently?
Its showing Serial v1.00...after the reset.
Its been on the USB chatge all along.....
Great. If you get Serial at the top, this can be recovered.
If you want a good T-Mobile 1.12 rom file, go here and use this one:
ftp://ftp.xda-developers.com/Uploads/Magician/tmobile-uk_wwe_ROM_1.12.00(thereapermanl).rar
Unpack it and follow all the procedures about copying the 416 bytes, rewriting the file, etc. from the other thread. I have tested this rom file and it installs ok.
Thanks for the encouraging words...
Will it work even if I do not have a backup of the original ROM on my machine?....I only have the tmobile.nb1 file which I got from the XDA forums.
Lemme try using that and editing it.
Thanks a ton for your help.
You might be a little stuck for an nb1 flash if you don't have an original flash back up but don't fear. You can go here and get this WWE1.12 file and just do a USB type upgrade:
ftp://ftp.xda-developers.com/Magician/Shipped_ROMS/WWE_11200_128_11210_ship.exe
I know this one works too. It's ROM 1.12, Radio 1.12 and Ext_ROM 1.12. When you try to run the upgrade program though, it might give you a Country ID error. If so, use the attached upgrade program instead. If this one gives you a Country ID error again, close the program and just run it again. I've been down all these roads already.
Lemme get this right this time: I will be doing the following
1. Install the ROM as you have mentioned. With the country id hack if necessary
2. Hopefully by now the device would be alive. If so will take a backup of the ROM on the SD card
3. From then on follow the instruction given in the doc.
Hope I get it righ this time else Its going to be a long night for me.
Lemme know if I have to do anything else.
Either ROM will work fine for you. It just depends on whether or not you want I-Mate stuff on it or T-Mobile stuff on it.
Doing the USB upgrade will put the I-Mate ROM on but after that, it should be working and you can then do an SD backup, follow the SD flashing procedures and get the T-Mobile ROM on.
Good Luck!
The masupgrateut is throwing up a ruu.dll error?...you seen that one before?
What sort of error? Not found?
yup...
I extracted the ROM exe and found teh file...copied it to the windows folder..and ran the no id program...no error this time round but the update is still giving a COuntry ID error...
Been looking at various posts...specially this one...
http://forum.xda-developers.com/viewtopic.php?t=14973
Thinks thats gonna help?
ok...two things.....just run it again. The no ID program sometimes does that on the first time 'round so just run it again.
Second, stick this at the end of the RUU.conf file:
[CHECKCEID_TYPE]=1
ran the program multiple times...still getting the COuntry ID error...
Are you running this program? MaUpgradeUt_noID.exe
...with the change in the RUU.conf file?
I just noticed something....did you extract all the files to a single directory and just run it from there or did you just pull a few out?
ALL the files have to be in the same directory. This is also where you need to execute the installer program.
I have installed the new iMate rom to my T-Mobile SDA(US) and have the following observations.
Push Email is working well.
Screen fonts not as crisp as original T-Mobile.
I believe the OS is overall slower.
Don't see A2DP.
Camera and Video work well.
I'll keep testing and keep this thread updated.
Do you know where I can find instruction on how to backup my original T-Mo rom? I'd like to load the sp5m rom but I want to make sure I have a backup. Also, which filename did you use, there seem to be sever roms for sp5, sp5m and two versions for the sp5m at that!
-Kap
kaplanfx said:
Do you know where I can find instruction on how to backup my original T-Mo rom? I'd like to load the sp5m rom but I want to make sure I have a backup. Also, which filename did you use, there seem to be sever roms for sp5, sp5m and two versions for the sp5m at that!
-Kap
Click to expand...
Click to collapse
Here is what I recall, I'm by no means an expert.
To start, you will need a 64MB mini SD card minimum.
I had to application and SIM unlock the phone. You can find good info at http://wiki.spv-developers.com/index.php/Main_Page
Disable ActiveSync under File/Connection Settings by unselecting "Allow USB connections".
With the phone off, press and hold down the camera button while attaching the USB cable from your computer. This should bring up the 3 color bootloader screen on your phone.
Use mtty.exe on your computer and select USB to connect. After connecting type:
r2sd all
This should back up your original rom to the mini SD card. This action will COMPLETELY REFORMAT AND ERASE YOUR SD CARD. I'd suggest copying everything off of it to your HDD in ActiveSync.
This is where it gets gray for me. There is supposedly a way copy the image from the SD card to your PC and back using itsutils utilities called psdpread.exe and psdwrite.exe. You have to know or figure out the size of the image on the SD card and the instructions were not intuitive to me. At this point I am leaving the card out of my phone until I decide whether or not to stay with the iMate rom. I did confirm that I can use the card to reload the T-Mo rom. With the card in the phone, load up the bootloader as described above. When it first comes up, it will ask you press the volume slider to load from the card. I worked for me.
I get Vendor ID error
What was required to load the ROM on your T-Mobile US branded SDA? I keep getting a Vendor ID error ( I assume the same as the old country code error on the XDAs). My phone is application and sim unlocked.
Thanks.
Panabax
Re: I get Vendor ID error
Panabax said:
What was required to load the ROM on your T-Mobile US branded SDA? I keep getting a Vendor ID error ( I assume the same as the old country code error on the XDAs). My phone is application and sim unlocked.
Thanks.
Panabax
Click to expand...
Click to collapse
I had to use what I believe is referred to as the Super CID unlock. It is one of the options in the SPV-Services app I got from the URL referenced in the first post. I was very leary to use it because I couldn't find any documentation about how to revert back if desired. I haven't had any issues since I set it to "11111111". I only hope that it won't prevent me from using the official T-Mo AKU2 release when it comes out.
Thanks
Thanks. In the time between our posts, I came to the same conclusion. The upgrade is proceeding as I type.
Panabax
Hmm sounds like something I would like to try. Thanks for all the good info, I have a 256 MB sd card on the way from New Egg to use exclusively to back up my rom (didn't want to waste my 2gigger .
-Kap
artiemon said:
Use mtty.exe on your computer and select USB to connect. After connecting type:
r2sd all
Click to expand...
Click to collapse
Can you explain where to get mtty.exe and how its used?
Thanks
-Kap
kaplanfx said:
artiemon said:
Use mtty.exe on your computer and select USB to connect. After connecting type:
r2sd all
Click to expand...
Click to collapse
Can you explain where to get mtty.exe and how its used?
Thanks
-Kap
Click to expand...
Click to collapse
Here is where I got mtty.exe.
http://wiki.xda-developers.com/index.php?pagename=HimalayaHowtoCopyRom
The following thread has some info on backing up the rom. Scroll down to a post by Genesis3. He is referring to a different terminal emulator (terraterm), but it works the same as mtty. Both of these just open up a terminal session to your phone. Genesis3 is discussing a different platform, but you will get the idea.
http://forum.xda-developers.com/viewtopic.php?t=43399
thanks for the quick reply, im hoping to get the imate rom on my phone today.
-Kap
HI,
I downloaded the SPV-Services.zip. However, when I run it on my PC. It says
RAPI Init failed:RAPI init timeout
ROM editing tools will be unavailable
Anyone know what is the problem here?
Thanks
thx for your new ROM,
if i want to install chinese input software to input chinese word with
new rom, how can I?
thx again!
ronior said:
thx for your new ROM,
if i want to install chinese input software to input chinese word with
new rom, how can I?
thx again!
Click to expand...
Click to collapse
I dont think there is Chinese input program for Windows Mobile 5 SP.
thx for your rapid answer
but really has one!
your can find it almost in any chinese forum
ronior said:
thx for your rapid answer
but really has one!
your can find it almost in any chinese forum
Click to expand...
Click to collapse
Really?
well...then
did u application unlock the phone before installation? Just copy the cab file to your phone and run it....or use the setup if it has one
sixthday said:
HI,
I downloaded the SPV-Services.zip. However, when I run it on my PC. It says
RAPI Init failed:RAPI init timeout
ROM editing tools will be unavailable
Anyone know what is the problem here?
Thanks
Click to expand...
Click to collapse
You have to kill wcescomm.exe in the Windows Task Manager (ctl-alt-del keys brings it up), look for wcescomm.exe, stop the task. This will eliminate the error you are getting. Then Run the 'SPVServices.exe' file on your PC - it will communicate with your phone via activesync. Please note that this file connects to a remote server to do the unlocking calculations, so requires an internet connection. It's been reported that if you have IE7 (beta 2 in my case) installed, it might not work; I have IE7 B2 installed and all worked fine. On the SPVServices tool menu, click the CDI box, it will update your ID to 11111111 (now all is unlocked) then you can do the mtty.exe to backup up your ROM to a miniSD card. I have a word document I've written for myself that outlines some of these pieces and bits and parts I've read on various forums. Email me if you want the Word Doc file.
i have this problem:
r2sd all
***** user area size = 0x3CA0000 Bytes
R2SDBackup() - Download type = 6
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
You didn't get the proper security level to download a specific image
Cmd>
can you help me?
ciselko said:
i have this problem:
r2sd all
***** user area size = 0x3CA0000 Bytes
R2SDBackup() - Download type = 6
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
You didn't get the proper security level to download a specific image
Cmd>
can you help me?
Click to expand...
Click to collapse
I believe that message is displayed if you have not yet CID unlocked your phone. Did you use SPV Services to unlock it?
i have done these two procedures:
http://wiki.spv-developers.com/index.php/HTC_Application_Unlock_Guide
and
http://wiki.spv-developers.com/index.php/HTC_Smartphone_SIM_Unlock_Guide
than I tried mtty.exe but... :-(
have I forgot something?
There's an application called SPV-Services in one of the links above. It has an option for Super CID unlock.
A couple day ago I've installed a new ROM (Touch FLO Manila 2D) on my Herald using "FLASH CENTER". It has worked for some time, but after one rebooting the system didn't start any more - after turning on it appears a green screen for a pair seconds, then my Herald goes automatically down. And it repeats again and again... And it is not possible to restore the system though ActiveSync, because the Herald doesn't start at all.
I have looked through in this forum for possible rescue options. one of them seemed to be FLASHING FROM SD CARD. But this had no effect - a tricolor has appeared, but it happened nothing more. Probably there is possible to install a ROM this way on working WINDOWS MOBILE' s and not at broken.
I thought - may be it is possible to install a Windows Mobile on SD CARD (something like portable version) and so boot a system from SD Card ???
I hope you can help me.
Thanks.
radjapost said:
A couple day ago I've installed a new ROM (Touch FLO Manila 2D) on my Herald using "FLASH CENTER". It has worked for some time, but after one rebooting the system didn't start any more - after turning on it appears a green screen for a pair seconds, then my Herald goes automatically down. And it repeats again and again... And it is not possible to restore the system though ActiveSync, because the Herald doesn't start at all.
I have looked through in this forum for possible rescue options. one of them seemed to be FLASHING FROM SD CARD. But this had no effect - a tricolor has appeared, but it happened nothing more. Probably there is possible to install a ROM this way on working WINDOWS MOBILE' s and not at broken.
I thought - may be it is possible to install a Windows Mobile on SD CARD (something like portable version) and so boot a system from SD Card ???
I hope you can help me.
Thanks.
Click to expand...
Click to collapse
This is the wrong forum for this. I have written a few guides on how "unbrick" the Herald.
You can flash just fine from the tricolor screen. (That's where the phone takes you automatically when you flash "from" windows mobile.) So no worries, you aren't out of luck. Worse case scenario, you search for the GoldCard method if nothing else works.
Hello!
Thank you for your help.
You say, I am on right way with my "tricolor screen". But why doesn't happen anything? May be:
- should I just take another SD Card? My is 1 GB - is it OK, too big, too small?
- did I something wrong with "flashing" methods? I did it 2 ways:
- just with any ROM-File in NBH-Format, which was renamed to HERAIMG.NBH and placed alone to the formated SD Card
- in addition to HERAIMG.NBH also other files (like "EnterBootloader.exe"), which are often inclusive in ROM- ZIPs.
- I should be more patient and wait more than 1 hour with a hope that anything will change?
Could you give me the links for "unbricking" the Herald?
Thanks a lot.
You misunderstood me. You don't flash with the SD card through the tricolor screen. You flash through the regular flash center. If you're not hardSPL you have to flash the stock ROM.
As far as the flashing through SD goes, it should give you a countdown before the tricolor screen appears. If it doesn't, or if it's too fast to read, then your SD card is too slow.
As it loads this tricolor screen I see the following data:
IPL 1.08.0001
SPL 1.08.0001
Perhaps it means, that I indeed need a GOLDCARD method.
You don't flash with the SD card through the tricolor screen. You flash through the regular flash center.
Click to expand...
Click to collapse
But the FLASH CENTER works only on WINDOWS. So I can't use the regular flash center, because my Herald doesn't start up and ActiveSync doesn't see him.
If you're not hardSPL you have to flash the stock ROM.
Click to expand...
Click to collapse
Where do I get the original ROM, may be even WM5? In your FTP- server I have found some "ship.exe"- Files, but I can't extract ".nbh" files from them.
it should give you a countdown before the tricolor screen appears. If it doesn't, or if it's too fast to read, then your SD card is too slow.
Click to expand...
Click to collapse
May be that is the point!!! My SD is too slow. Will be in this case "GoldCard" an ideal solution for me?
Thanks.
radjapost said:
As it loads this tricolor screen I see the following data:
IPL 1.08.0001
SPL 1.08.0001
Perhaps it means, that I indeed need a GOLDCARD method.
Click to expand...
Click to collapse
This means that you attempted to flash a HardSPL or another SPL when your SPL did not meet the state requirements. You NEED to create a Goldcard.
radjapost said:
But the FLASH CENTER works only on WINDOWS. So I can't use the regular flash center, because my Herald doesn't start up and ActiveSync doesn't see him.
Click to expand...
Click to collapse
No, the flash center doesn't only work in Windows. It works on the bootloader mode. ActiveSync's icon turning green doesn't mean that activesync saw the phone, it means that it can synchronize your information with the computer.
radjapost said:
Where do I get the original ROM, may be even WM5? In your FTP- server I have found some "ship.exe"- Files, but I can't extract ".nbh" files from them.
Click to expand...
Click to collapse
If you broke your SPL like I mentioned above, you will have to use the Goldcard first then you will be able to flash any stock Herald/Tmobile Wing ROM.
radjapost said:
May be that is the point!!! My SD is too slow. Will be in this case "GoldCard" an ideal solution for me?
Thanks.
Click to expand...
Click to collapse
I don't know if it will be too slow for that, too. But if you broke your SPL, the goldcard is the ONLY way to fix it.
The problem is - for GOLD Card I need a working WINDOWS Mobile Handy... and I don't have such one at the moment.
Is it possible to become a standard GOLD Card, which would be suitable for most of Heralds?
Thanks
radjapost said:
The problem is - for GOLD Card I need a working WINDOWS Mobile Handy... and I don't have such one at the moment.
Is it possible to become a standard GOLD Card, which would be suitable for most of Heralds?
Thanks
Click to expand...
Click to collapse
You don't need a windows mobile phone. You can also create one using linux.
http://forum.xda-developers.com/showthread.php?t=485364
Obviously, make it for the Herald not the Dream.
Hi.
You don't need a windows mobile phone. You can also create one using Linux.
Click to expand...
Click to collapse
I've installed Linux on my computer, but i can't find a correct command to read a CID of my SD Card. My SD is located in Linux under "/media/disk-1" and I try to write something like "cat /media/disk-1:*/cid", but the Linux doesn't recognize CID command at all.
Actually, I hope, that after getting CID it will not be difficult to obtain a goldcard.img through QMAT. Am I right?
Thanks.
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
adam_4049 said:
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
Click to expand...
Click to collapse
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
C-Lang said:
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
Click to expand...
Click to collapse
i did do a search and nothing has been able to help me so far. i also did read that it is device specific but have also read it has worked for some people. unfortunatley in australia we do no have any microsoft stores so its not that easy to just take it somewhere.
I feel like there are files missing from c drive. Almost like it started to do a restore then stopped halfway. In which I have never been able to get it to that stage for that to be the case.
I did some reading and was able to find the recover partition and tried to run the install.wim file from which I understand to basically be the “OS”. When I try to run it it says “no such interface supported”
From what I understand there is just no way to do a fresh install on these things regardless of what the problem is which is disappointing on Microsoft’s behalf.
C-Lang said:
And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you.
Click to expand...
Click to collapse
No. Those recovery images are device-type specific. Not device-specific. You can safely take one WIM file from the recovery partition of your device and use it to recover a different device of the identical model.
adam_4049
I see that you were able to start a restore process and it fails in the middle.
You may try the following: boot into the command line mode and format the boot partition (probably drive C: ). This would fix the disk errors if they are present, but you'll lose everything. Use diskpart tool to find the disk letter. Be careful with diskpart - do not delete partitions or issue "clean" command.
Then assign the letter to recovery partition with diskpart (say, R: ), then expand WIM file from the recovery partition with the command like this:
Code:
Dism /apply-image /imagefile:R:\RecoveryImage\install.wim /index:1 /ApplyDir:c:\
R:\RecoveryImage\install.wim - a path to install.wim on the recovery partition.
More info: http://technet.microsoft.com/en-us/library/hh824910.aspx - you need only "Dism /apply-image" part, bcdboot is unnecessary. Lets hope that "apply-image" option is present on RT.
This would forcibly expand the WIM file to your disk C:. Or at least you'll be able to see why it fails.
This may help. Or may completely brick the device and you'll need to go to service. So use it on your own risk. And you should be familiar with the command line - so don't ask how to use diskpart.
I had a problem with the recovery process when I've played with BCD and added a boot from VHD option. Had to delete that extra boot setting - and then recovery went fine. But I assume that you have not played with BCD.
Yeah, looks like people dont use search, what you want is a nice useful soul that creates a USB recovery from his EN-UK Surface_RT and puts it up on Copy, or Dropbox or something like that...
Hi
I am new to hacking android. I have built linux distros in the past, and have worked with Linux for 15 years,
I have just rooted a ZTE V965. It doesn't come pre-installed with Play store, and has all sorts of ZTE-specific Chinese apps. It has a good baseband circuit, a good screen, reasonable camera and I think is a great value phone, apart from the awful UI.
It is an android phone, although heavily customised. It has an MTK6589 processor coupled with 4Gb ROM and 512Mb RAM.
I have other phones which operate a much more "Vanilla" android. For example, the Guophone 9105 which also uses an MTK6589. This has a troubling tendency to reboot every random interval. Approx 6 times a week.
I have had success in the past running Linux systems built for much earlier kernels on later kernels. This suggests the ABI (application binary interface) for the Linux kernel changes rather slowly.
I am wondering how well the userland apps are separated from the kernel and drivers on Android.
Specifically, is it feasible to dump all the UI stuff from one phone onto another then change the init to launch the other UI?
Would this risk bricking the phone, or would the shell commands and ADB infrastructure still likely operate?
I guess I should change the bootloader to one that supports fastboot first, right? Is ther a how-to on achieveing this from the root shell?
Thanks for any thoughts
Nick.
Nick Hill said:
Hi
I am new to hacking android. I have built linux distros in the past, and have worked with Linux for 15 years,
I have just rooted a ZTE V965. It doesn't come pre-installed with Play store, and has all sorts of ZTE-specific Chinese apps. It has a good baseband circuit, a good screen, reasonable camera and I think is a great value phone, apart from the awful UI.
It is an android phone, although heavily customised. It has an MTK6589 processor coupled with 4Gb ROM and 512Mb RAM.
I have other phones which operate a much more "Vanilla" android. For example, the Guophone 9105 which also uses an MTK6589. This has a troubling tendency to reboot every random interval. Approx 6 times a week.
I have had success in the past running Linux systems built for much earlier kernels on later kernels. This suggests the ABI (application binary interface) for the Linux kernel changes rather slowly.
I am wondering how well the userland apps are separated from the kernel and drivers on Android.
Specifically, is it feasible to dump all the UI stuff from one phone onto another then change the init to launch the other UI?
Would this risk bricking the phone, or would the shell commands and ADB infrastructure still likely operate?
I guess I should change the bootloader to one that supports fastboot first, right? Is ther a how-to on achieveing this from the root shell?
Thanks for any thoughts
Nick.
Click to expand...
Click to collapse
Hi Nick, I have the same phone. I'm also very new to android, last phone was iOS and before that windows. I managed to root the V965 using Vroot. I also managed to install SuperSU and CWM. However, the CWM is not fully functional, I can only do a factory reset, not install any packages or roms. Probably the phone has a locked bootloader. I can't check, because the USB driver with the phone doesnt support fastboot.
I really need to get google play working in this phone, read a lot of stuff, tried many things, but I havent succeeded yet. Please let me know if you make any progress.
In China they are flashing this phone, found some ROMs even, but I am not sure how they manage and google translate isn't much help there.
http://www.romjd.com/Device/zte-v965/hot/all/1
Hmmm my V965 is having some issues now
After a factory reset, the setup wizard keeps crashing. Even after another resest. So I can't get in the phone anymore.
Any chance you can send me the USB drivers that are on the phone? My phone isnt deteceted anymore, so I can't access the drivers, which I want to reinstall. And of course they are not on the ZTE website.
Byte_Me said:
Hmmm my V965 is having some issues now
After a factory reset, the setup wizard keeps crashing. Even after another resest. So I can't get in the phone anymore.
Any chance you can send me the USB drivers that are on the phone? My phone isnt deteceted anymore, so I can't access the drivers, which I want to reinstall. And of course they are not on the ZTE website.
Click to expand...
Click to collapse
Hi
You can temporarily download the ZTE v965 USB drivers from
www dot nickhill dot co dot uk forward slash ztev965usb dot zip
Byte_Me said:
Hi Nick, I have the same phone. I'm also very new to android, last phone was iOS and before that windows. I managed to root the V965 using Vroot. I also managed to install SuperSU and CWM. However, the CWM is not fully functional, I can only do a factory reset, not install any packages or roms. Probably the phone has a locked bootloader. I can't check, because the USB driver with the phone doesnt support fastboot.
Click to expand...
Click to collapse
Fastboot and ADB appear to be standard protocols, at least on my Ubuntu, which don't need special drivers. However, it does appear that the stock boot loaader on the v965 does fail to incorporate the fastboot option.
If you remove the battery, replace it then turn on holding the volume down, you will get a menu, but fastboot is not there.
I don't know for a fact, but I do suspect that if you have access to the running android system as root, then you could in principle change any of the internal flash data. Therefore, in principle, I guess you could replace the boot loader or anything else in the running android system. Anyone please correct me if I am wrong, or confirm if I am right.
The feature set of this phone seems to be the same as the feature set of my Guophone. MTK6589, dual SIM, etc. So this image may be a good place to start if considering a transplant.
If you have ROMs, then perhaps it is possible to flash the ROM from a root terminal. I'm thinking add the uncompressed ROM to the Micro SD card, then using the dd command, block copy it to the appropriate image area on the internal ROM, reboot, reset to factory defaults.
If anyone more experienced than me with the nuts and bolts of Android can confirm or deny this will work, or where it should be put, please let me know.
An important factor is that the NAND is not locked on the ZTE V965. So if you have a root shell on the phone, you can issue the following command:
mount -o remount,rw /[email protected] /system/
Once you have done this, you will have read/write access to the system partition.
The only thing I then need to know is what should I avoid changing that may break the ADB bridge/root console?
And is all the UI stuff kept together, if so, where?
Shuffle it around a bit, make a new ROM
Thanks for the driver!
Unfortuntely it doesn't help
I found out the culprit, I tried to install gapps (google apps package) to the system app folder. I thought these changes would be reversed with a factory reset, but they are not. Setupwizard.apk keeps crashing and is preventing me from accessing my phone, so I must find a way to remove it from the system app folder. However, since this error occurred, I am not able to contact the phone in any way from the PC. Adb toolkit does not detect it, even when I reinstalled your driver. It's quite puzzling, I dont understand why in recovery mode I cannot connect adb-toolkit anymore.
Got my V965 working again, but it was a lot of hassle with shell access. Still not fully functional, no drives detected when i connect to USB, which is quite annoying, but not more than that. If you ever make any progress with google apps or flashing, please keep me informed, that would make this phone much more useable. I'll also keep hacking away at it, but without a bootloader unlock (I still think this is the problem), I don't think it will be possible.
I'm convinced it's possible to flash the phone, it seems they do it a lot in China.
I found a website with a couple of custom ROMs specific for the V965:
http://www.romjd.com/Rom/Detail/17086
And what I suspect is a rooting & flashing tool. Rooting works, I haven't figured out flashing yet.
http://dl.vmall.com/c0xa12brvo
I've also tried flashing from the settings - update menu in the phone, but it never finds the ROM (update.zip)
I did find another problem, I can't be reached on my phone, it always goes to voicemail. Same SIM in another phone works fine. No idea what's causing this.
Byte_Me said:
Got my V965 working again, but it was a lot of hassle with shell access. Still not fully functional, no drives detected when i connect to USB, which is quite annoying, but not more than that. If you ever make any progress with google apps or flashing, please keep me informed, that would make this phone much more useable. I'll also keep hacking away at it, but without a bootloader unlock (I still think this is the problem), I don't think it will be possible.
Click to expand...
Click to collapse
Hi
I might be able to help you with the problem.
I have a mint, unused ZTE v965. I have used MTK Droid root and tools to extract a backup of the entire new phone. It is currently uploading to www dot nickhill dot co dot uk forward slash ZTE-V965_new_backup.zip
You should be able to write this back to your phone using flashtool.exe.
I don't know for sure if this will work, so entirely at your own risk! Just trying to help. If unsure, ask around.
I am new to this forum, so please remember to click the thanks button if you find anything I have done helpful!
Meanwhile, the MTK droid root and tools has a function to remove much of the chinese stuff (once the system has been installed) and there is always the cyanogenmod gapps package. This may be worth investigating.
Nick Hill said:
Hi
I might be able to help you with the problem.
I have a mint, unused ZTE v965. I have used MTK Droid root and tools to extract a backup of the entire new phone. It is currently uploading to www dot nickhill dot co dot uk forward slash ZTE-V965_new_backup.zip
Click to expand...
Click to collapse
The file size should be 635,972,093 bytes and should finish uploading at 04:00 GMT
md5sum 17ecfdd1040d5dbfab70a3adbc24e07a
Thanks for the ROM, i'll give it a go. I will try to install it using the update option in the settings, that seems the safest.
Be careful with gapps. setupwizard.apk + factory reset = a lot of problems (if you install in system app folder)
OMG that tool is awesome. created CWM boot, installed your ROM, then installed a clean ROM, then installed gapps, all working!!!
Byte_Me said:
OMG that tool is awesome. created CWM boot, installed your ROM, then installed a clean ROM, then installed gapps, all working!!!
Click to expand...
Click to collapse
Firstly, I'm glad it's working for you.
Secondly, which tools did you use? Did you unpack the zip, open flashtools, select the scatter file then program the phone, or did you use some other method?
Which clean ROM did you then install, and how did you install it?
Did you then use MobileUncle to install CWM then use the cyanogenmod 10.1 gapps, or did you do something different?
It is useful to remember that MTKdroidtools has a useful function to remove chinese stuff. I think if more people contributed to the list of Chinese files that are safe to remove, that would be blade.
A detailed step-by-step guide might be helpful for anyone else with the same problem. One of the general problems I find is that there are plenty of guides around referring to this program, or that program, but few are detailed enough for someone who doesn't already know about those programs to use.
I pretty much bricked a Lenovo A766 yesterday, and it took several hours to learn about the tools to eventually unbrick it.
I would have rather spent my time understanding what is really going on, rather than spending my time learning vaguely what tool achieves what end result. If I understood more about the Android system, and built that knowledge on my understanding of Linux, I reckon I could achieve much more.
One thing I notice is that tablets and smartphones are actually replacing desktops and laptops. February this year, windows machines were down 7% YOY. I use Ubuntu for my main computer. Using these tools on Windows led me to significant frustration! This has led me to understand why there is a move. Maybe the tools provided for windows need to eventually move to android. We could then potentially use USB OTG to service other android devices. MTKdroidtools and flashtools runnng as a host on a separate Android system would be cool.
Nick Hill said:
Firstly, I'm glad it's working for you.
Click to expand...
Click to collapse
Thanks, me too
Secondly, which tools did you use? Did you unpack the zip, open flashtools, select the scatter file then program the phone, or did you use some other method?
Click to expand...
Click to collapse
I used MTK tools as described in that topic, rooted, made backup, installed CWM
Which clean ROM did you then install, and how did you install it?
Click to expand...
Click to collapse
I used the update tool from CWM to flash this ROM:
http://www.romjd.com/Rom/Detail/17086
That ROM is not very clean though, You might as well clean your own ROM
Did you then use MobileUncle to install CWM then use the cyanogenmod 10.1 gapps, or did you do something different?
Click to expand...
Click to collapse
CWM is installed using MTK Droid Root and Tools:
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
This gapps version I installed: gapps-jb-20121011-signed
It's installed using CWM bootloader: install .zip package
It is useful to remember that MTKdroidtools has a useful function to remove chinese stuff. I think if more people contributed to the list of Chinese files that are safe to remove, that would be blade.
Click to expand...
Click to collapse
I used the delete China function, but it didnt catch very much. But with all the functions available now, it's quite easy to clean manually.
A detailed step-by-step guide might be helpful for anyone else with the same problem. One of the general problems I find is that there are plenty of guides around referring to this program, or that program, but few are detailed enough for someone who doesn't already know about those programs to use.
Click to expand...
Click to collapse
Yes, I plan to make a topic for this phone, but at the moment I am still testing many things.
I pretty much bricked a Lenovo A766 yesterday, and it took several hours to learn about the tools to eventually unbrick it. I would have rather spent my time understanding what is really going on, rather than spending my time learning vaguely what tool achieves what end result. If I understood more about the Android system, and built that knowledge on my understanding of Linux, I reckon I could achieve much more.
Click to expand...
Click to collapse
I know how you feel, I was ready to toss this phone in the trash
One thing I notice is that tablets and smartphones are actually replacing desktops and laptops. February this year, windows machines were down 7% YOY. I use Ubuntu for my main computer. Using these tools on Windows led me to significant frustration! This has led me to understand why there is a move. Maybe the tools provided for windows need to eventually move to android. We could then potentially use USB OTG to service other android devices. MTKdroidtools and flashtools runnng as a host on a separate Android system would be cool.
Click to expand...
Click to collapse
I have no idea about the possibilities there. I'm not a programmer, just someone who is good with computers and knows a little bit of everything.
PS. I could also use some thanks as well, maybe get some respect around here
Nick Hill said:
...
Click to expand...
Click to collapse
Did you give it a try yet? Another user did and google apps are working for him, so thats 2 for 2.
Are you still on your original ROM? If so, I have a question for you. Do you get notification badges on your icons, for instance, when you have a missed call, is there a red box with a 1 on the phone icon? Also, do your contacts get ID-ed when they call you? I have some problems with that, caused by the country code prefix. I am still running that ROM I downlaoded from the Chinese forum, but if your ROM doent have these issues, I will switch back ASAP.
Nick Hill said:
Firstly, I'm glad it's working for you.
Click to expand...
Click to collapse
as you are a Lenovo a766 owner, may you help me with this?
http://forum.xda-developers.com/showthread.php?p=49076877#post49076877
Where are configuration settings stored accross factory resets?
I have come to the (perhaps erroneous) conclusion that the user interface and what the user will experience is governed primarily from:
the APKs in
/system/app/
/system/vendor/operator/app/
and the configuration files pertaining to the installed apps, which is located at:
/data/user/0/
I guess that when the android device is factory reset, the /data partition is completely cleared, right?
Is there a set of standard configurations which are unpacked from somewhere into /data/user/0/ after a factory reset, or is it normal for all configurations to be stored in their respective APKs?