PPCGeeks

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   HTC Apache (http://forum.ppcgeeks.com/forumdisplay.php?f=14)
-   -   6700 Has Blank model # After Flashing. (http://forum.ppcgeeks.com/showthread.php?t=10641)

KidGixxer 10-29-2007 01:42 AM

6700 Has Blank model # After Flashing. Fixed!!!
 
1 Attachment(s)
Tested. Fixed. Windows live works fine now.
0. Download mtty.zip
1. Put phone in bootloader (power, notes and soft reset)
2. Disable activeSync (right-click on activeSync, select connections, and uncheck USB)
3. Connect phone to computer and run mtty1[1].42.exe
4. select "USB" in com ports and click 'ok'.
5. Press the "enter" key on your keyboard and you will get "USB>"
6. type "task 28 55aa" (do not copy and paste, it wont work.) without the quotes and press "enter"
7. Close mtty1[1].42.exe
8. soft reset phone. (It wont turn on)
9. Put phone back into bootloader mode.
10. Make your custom rom the way you want it and flash your phone. (Do not over stuff it)
11. Check the device name. Tada Its magic...


If you need help p.m me. I doubt you will though.

Disclaimer!!!!!
READ THE FIRST POST OF THIS TOPIC BEFORE YOU DO ANYTHING.
http://forum.ppcgeeks.com/showthread.php?t=7820



Quote:

Originally Posted by mbial (Post 110530)
For anyone running Vista who is having trouble getting mtty working properly, be sure to check out how to make it work here:
http://forum.xda-developers.com/showthread.php?t=291723
MJB


varaff 10-29-2007 10:03 AM

Yeah, I have this problem with the Model ID. It seems to have affected Live Search. (it no longer downloads the maps and traffic)

Drewidian 10-29-2007 12:28 PM

I also had this problem and ended up having to use the #2 option when I reflashed. If anyone has any clues as how to resolve this and get back to the original settings let me know.

Thanks in advance.

gilesmartin 10-29-2007 12:34 PM

i have this issue

mbial 10-29-2007 02:45 PM

Obviously I have this problem...still no clear answer...

KidGixxer 10-29-2007 03:34 PM

well i tried going through the ## numbers and found nothing. I had
"APAC_VZW_20720_200_11000_Ship.exe" with the same bootloader i had hoping it would reinstall the bootloader. That didn't help. Im thinking maybe going to a newer bootloader might do the trick.

I have v1.00 in my phone. anyone have v1.02?

P.S
Maybe the "APAC_VZW_20720_200_11000_Ship.exe" rom didn't update my bootloader. Any have v1.00 also?

Perhaps theres a firmware for the phone?

mbial 10-29-2007 03:56 PM

I also have bootloader 1.00 - what bootloaders are people with this problem using?

MJB

varaff 10-29-2007 04:01 PM

Quote:

Originally Posted by mbial (Post 109591)
I also have bootloader 1.00 - what bootloaders are people with this problem using?

MJB

I have 2.02 but it's not specific to the bootloader.

mbial 10-29-2007 08:09 PM

Per VerizonGuy:
"Flash back to your carrier's stock rom, possibly using the noid ruu, then update to wm6."

Anyone have success with this method?

MJB

varaff 10-29-2007 08:31 PM

Quote:

Originally Posted by mbial (Post 109741)
Per VerizonGuy:
"Flash back to your carrier's stock rom, possibly using the noid ruu, then update to wm6."

Anyone have success with this method?

MJB

Nope this will not work, I have tried it with sprint's and others have tried with Verizon's Rom and still no luck.

KidGixxer 10-29-2007 09:26 PM

Quote:

Originally Posted by mbial (Post 109741)
Per VerizonGuy:
"Flash back to your carrier's stock rom, possibly using the noid ruu, then update to wm6."

Anyone have success with this method?

MJB

I tried this will several different official roms and different wm6 roms


Quote:

Originally Posted by varaff (Post 109599)
I have 2.02 but it's not specific to the bootloader.

I Think it does have something to do with the bootloader.
Since the problem occurred to the phone when stuck at 99% while flashing the phone. This might have damaged certain data that is hard coded into the phone.

varaff 10-29-2007 09:30 PM

Quote:

Originally Posted by KidGixxer (Post 109784)
I tried this will several different official roms and different wm6 roms




I Think it does have something to do with the bootloader.
Since the problem occurred to the phone when stuck at 99% while flashing the phone. This might have damaged certain data that is hard coded into the phone.


The Model Id is stored in the nk.nbf
If you look at the HTC64_Extended_ROM_Tool.exe when doing the encoding, that is where
the Model ID is put in and not on the bootloader. But if you do upgrade to bootloader 2.04 Please let us know if it works for you.

KidGixxer 10-29-2007 09:51 PM

I FIXED IT!!!!!!!!

Simple fix to. Stay tuned for the fix and files.

Quick question. Everyone having this problem is on verizon?

jarmenti 10-30-2007 12:13 AM

OMG KidGixxer you are my hero if you fixed it, does windows live work again ?

KidGixxer 10-30-2007 12:26 AM

I haven't gotten that far yet. I'm still running some tests. Look for an update in the first post soon.

KidGixxer 10-30-2007 12:57 AM

Fix posted in first post.

jarmenti 10-30-2007 01:24 AM

so do you make the small rom with the wm6 kitchen using the verizonVG PRJ?, or just the verizon prj

KidGixxer 10-30-2007 01:39 AM

Quote:

Originally Posted by jarmenti (Post 109957)
so do you make the small rom with the wm6 kitchen using the verizonVG PRJ?, or just the verizon prj

verizonVG PRJ is the original prj file (Use this when you make your custom rom)

Verizon.prj is the new one. (Use this to make the small one)

jarmenti 10-30-2007 01:54 AM

i've tryed a few times and still no model No. i've flashed with the wm6 kitchen small rom encoding it with verizon.prj, still nothing, i wonder what is going on

KidGixxer 10-30-2007 02:24 AM

First post.

jarmenti 10-30-2007 02:58 AM

tried the steps you had there , still no go on the model id, it still remains blank

jarmenti 10-30-2007 09:02 AM

I alsotried the 2 roms you posted, but still nothing. you may have to recreate the error and try fixing again, as i've tried everything from the 1st post with no luck

mbial 10-30-2007 02:01 PM

Users on Sprint are having this problem also, NOT JUST VERIZON!

MJB

KidGixxer 10-30-2007 02:13 PM

Quote:

Originally Posted by mbial (Post 110203)
Users on Sprint are having this problem also, NOT JUST VERIZON!

MJB

No need to the caps there guy.
I'm just trying to help.
I posted the instructions in the first post of how i fixed it.
And i am trying to recreate the error so i can document the way i fixed it.

bmtbandit 10-30-2007 02:17 PM

Mine happened by packing way to much shite into a 5 pound bag. Load the hell out of a Kitchen flash that rom, and poof mine was broke. It stuck at 99% on the flash utility.

KidGixxer 10-30-2007 02:22 PM

Quote:

Originally Posted by bmtbandit (Post 110219)
Mine happened by packing way to much shite into a 5 pound bag. Load the hell out of a Kitchen flash that rom, and poof mine was broke. It stuck at 99% on the flash utility.

Yeah but new kitchen will crash when making the nbf file now to let you know its over packed.

I think 0.3 will let you over pack it.

bmtbandit 10-30-2007 02:24 PM

I did mine on .4

KidGixxer 10-30-2007 05:02 PM

Ok i recreated the error and figured out how i fixed.
Then i repeated the error and fix to double check it. It worked.
Look in the first post first files and instructions.

varaff 10-30-2007 05:49 PM

Hey this looks promissing, but now I get the Error 120: country ID :-(
any ideas?

Sprint

KidGixxer 10-30-2007 05:54 PM

1 Attachment(s)
What are you flashing? the rom i uploaded to the first post or your own custom rom?

Extract the zip.
Move the .nbf file to the No_ID_RUU folder

mbial 10-30-2007 11:25 PM

First off, thanks for your efforts KidGixxer, I'm trying your latest fix now. For anyone running Vista who is having trouble getting mtty working properly, be sure to check out how to make it work here:

http://forum.xda-developers.com/showthread.php?t=291723


MJB

RussMuscle 10-30-2007 11:26 PM

Confirming that skipping to step 10a works just fine. Mine now has a model number.

KidGixxer 10-30-2007 11:27 PM

Quote:

Originally Posted by RussMuscle (Post 110531)
Confirming that skipping to step 10a works just fine. Mine now has a model number.

Cool thanks. I will update the first post.

mbial 10-30-2007 11:43 PM

YAY KIDGIXXER!!! You are the man. Worked like a charm, thanks so much!!

MJB

varaff 10-31-2007 05:02 AM

OOh you are the man!!! it freaking worked!!!
We all owe you one.. thanks a lot.

jarmenti 10-31-2007 08:54 AM

also confirming that the mtty fix worked, thanks sooo much for fixing this one, we deffinetly owe ya a few. haha

hefman 10-31-2007 12:38 PM

Excellent!!!
 
Awesome! Thanks KG!!!!!

I simply did the wrtt fix, reflashed with the same ROM I had been using and restored from SPB Backup. Worked like a charm. I'm wondering if a simple hard reset will suffice though...

Drewidian 11-01-2007 01:58 AM

Your kung-fu is most impressive KidGixxer! Thanks for solving this one. FYI I followed your steps in your first post and it worked flawlessly. Three Cheers!!!

PaulFix 11-05-2007 08:47 PM

Thanks, worked for me, as per instructions in post1


All times are GMT -4. The time now is 07:44 AM.

Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0