Related
All right... GOOD NEWS story for today!!!
There is no doubt, that our gods are helping us...
Here's what happened to me yesterday.
Yesterday I was dreaming about editing the ROM of Universal/Exec but as you may know, 'd2s' command doesn't work. It just quits with "Not allow operation".
But suddenly, my china god of wisdom whispered to me:
GOD: "hey buzz, you wanna dump the thing? why do you use that old fashioned 'd2s' command to dump it?"
me: "well, that always worked... so what else should i use?"
GOD: "OK, here's a little present for you ) just try 'task 32' )) "
Code:
USB>task 32
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SD:Detected one card
SD:ready for transfer OK
d.total_lba=1DC00
d.block_size=200
d.RCA=EC7E
d.drv_type=40000000
d.busWidth=1
Total card size=3B80000
So here it is !!!!
... and LET THE FUN BEGIN!!!
The above story is 100% true, i've made up maybe two words myself...
BTW, this might also work on other "password protected" devices.
THANX
buzz
Buzz, that's great, where the heck did you find that command?
But now that bal666 has that decrypt/encrypt utility of the original NBK files, what would be the benefit of dumping the ROM to the SD card?
Can you restore back to the device from the SD card?
Going by the way of the SD card to dump, extract, modify, write back, then flash may be safer than the Upgrade Utility that keeps my device stuck in Bootloader mode until I go through the whole NK/MS, then Radio upgrade.
So, what's the opposite of 'task 32?'
Thanks!
i'm dumping at the moment, but i would say, that it would be enough to insert the SD card back into the slot and reboot into bootloader mode.
Then you have to wait few seconds till "press power to flash" message appears.
But so far i didn't test it, yet...
Testing right now...
))
buzz
buzz_lightyear said:
i'm dumping at the moment, but i would say, that it would be enough to insert the SD card back into the slot and reboot into bootloader mode.
Then you have to wait few seconds till "press power to flash" message appears.
But so far i didn't test it, yet...
Testing right now...
))
buzz
Click to expand...
Click to collapse
Buzz, it is really good news. At this moment some of Universal (e.g. T-mobile) providers have not released an update yet. So if people can dump their roms on a SD, we at least have a fall back. In case of repairs the Universal will need to be updated again with a rom from the provider.
That is really a fantastic news!
If the restore test is successful, please just let all of us know.
Oh, and look forward to a complete dump backup/restore guide. :wink:
BeyondtheTech said:
But now that bal666 has that decrypt/encrypt utility of the original NBK files, what would be the benefit of dumping the ROM to the SD card?
Click to expand...
Click to collapse
From what I've seen his tool incorrectly decrypts NBF, some blocks are mixed.
hmmm.....
i think that the "task 32' commande needs a little bit more tweaking...
Till now it was just saying OK... ready.. etc., but actually did not the dump... (
Code:
USB>task 32
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SD:Detected one card
SD:ready for transfer OK
d.total_lba=F1F00
d.block_size=200
d.RCA=80CA
d.drv_type=40000000
d.busWidth=1
Total card size=1E3E0000
Level = FF
USB>
Well, "Level = FF" sounds like an error to me....
hmmm....
buzz
Another very interesting command and it's output:
Code:
USB>info 2
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SD:Detected one card
SD:ready for transfer OK
d.total_lba=F1F00
d.block_size=200
d.RCA=80CA
d.drv_type=40000000
d.busWidth=1
Total card size=1E3E0000
HTCSDOPOD601 «Jú½HTCE
USB>
Code:
USB>info 7
HTC Integrated Re-Flash Utility for bootloader Version : 1.40h, UNIVERSAL HW Version : 1.00
Built at: Sep 2 2005 15:14:29
Copyright (c) 1998-2005 High Tech Computer Corporation
Turbo=312, Run=208
Memory Frequency = 208 MHz
SDRAM Frequency = 104 MHz
Board ID is: 5
USB>
buzz
buzz_lightyear said:
Code:
Board ID is: 5
Click to expand...
Click to collapse
Hi Buzz,
is it possible to make memory dumps
in the bootloader without entering a password ?
cr2 said:
buzz_lightyear said:
Code:
Board ID is: 5
Click to expand...
Click to collapse
Hi Buzz,
is it possible to make memory dumps
in the bootloader without entering a password ?
Click to expand...
Click to collapse
not in bootloader...
but i'm able to dump DOC and memory using RapiEnabler and itsutils.
buzz
buzz_lightyear said:
but i'm able to dump DOC and memory using RapiEnabler and itsutils.
Click to expand...
Click to collapse
Hmm. What part of the DoC ? All 128 MB ?
There is also OTP and other stuff.
As you can guess, i'd like to dump the whole 64MB RAM (or as much as possible) while the bootloader is running, not
in wince.
Maybe you should try 'r2sd' ?
mamaich said:
BeyondtheTech said:
But now that bal666 has that decrypt/encrypt utility of the original NBK files, what would be the benefit of dumping the ROM to the SD card?
Click to expand...
Click to collapse
From what I've seen his tool incorrectly decrypts NBF, some blocks are mixed.
Click to expand...
Click to collapse
He stated that as long as you don't change the header information, it will encrypt and decrypt properly.
As a precaution, I took the NK.NBF, decrypted it to NK.FAT, then reencrypted it and did a successful byte-comparison.
I did the same with my modified NK.FAT file with my injected custom splash image and it encrypted and decrypted properly.
The biggest test was flashing it, and man, I was sweating buckets during the process. But, the flash came through successful for me and now I have the first custom splash screen on the Universal.
It's fun to break news or be the first guinea pig to try it out, just as long as it comes out successful! :lol:
The password doesn't seem do do anything.
The level of access is determined by your CID.
If your CID is 11111111 you have a SuperCID, which enables all the operations. I'm trying to track down where the CID is stored.
Bye,
Ricardo
go beyoundthetech !!!!
now only if you could post a step by step for all us goofs out here...
also im wondering with your genius if you could use the recently posted tools here to make custom universal rom (minus the ie explorer, file explorer etc) and teach us how to do that aswell!!!!
buzz_lightyear said:
i'm dumping at the moment, but i would say, that it would be enough to insert the SD card back into the slot and reboot into bootloader mode.
Then you have to wait few seconds till "press power to flash" message appears.
But so far i didn't test it, yet...
Testing right now...
))
buzz
Click to expand...
Click to collapse
My 9000 has a SuperCID. I managed to dump and flash the rom using these techniques.
Bye,
Ricardo
BeyondtheTech said:
He stated that as long as you don't change the header information, it will encrypt and decrypt properly.
As a precaution, I took the NK.NBF, decrypted it to NK.FAT, then reencrypted it and did a successful byte-comparison.
I did the same with my modified NK.FAT file with my injected custom splash image and it encrypted and decrypted properly.
Click to expand...
Click to collapse
I decrypted nk.nbf to nba with his tool, and decrypted the same file with alpinenbfdecode.pl script. Files are different after some offset. So there should be a bug in his util, because alpinenbfdecode.pl is known to produce working files. I had no time for more tests.
buzz_lightyear said:
Another very interesting command and it's output:
Click to expand...
Click to collapse
Hi buzz,
i can run "rbmc", but don't get where is this c:\test\mem.nb located.
Is it used by the mtty download protocol ?
I can't test it because mtty is not working
for me in windowz
cr2 said:
buzz_lightyear said:
Another very interesting command and it's output:
Click to expand...
Click to collapse
Hi buzz,
i can run "rbmc", but don't get where is this c:\test\mem.nb located.
Is it used by the mtty download protocol ?
I can't test it because mtty is not working
for me in windowz
Click to expand...
Click to collapse
looks like rbmc is running up to the point, where it should start saving the dump (
same as task 32
(
buzz
OK, so here is, how it should be:
Dump Bootloader:
Code:
USB>task 32
USB>d2s 70000000 80000
OS ROM + splash:
Code:
USB>d2s 70100000 3FA0000
XtendedROM:
Code:
USB>d2s 74100000 A00000
Radio ROM:
Code:
USB>d2s 60000000 a24200
If you want to have them all on single SD card, you must add "sd a" at the end of each command except the first one.
Example to dump/backup OS + XtendedROM + Radio:
Code:
USB>d2s 70100000 3FA0000
USB>d2s 74100000 A00000 sd a
USB>d2s 60000000 a24200 sd a
buzz
Help Please.
I'm using the OSImageTool.exe to save my current ROM so I can try to SIM unlock my phone. This is what I have done:
Double click osinagetool.exe
source: Device Memory (current rom)
Destination: d:\rom
Error message:
unsupported target filetype
don't know how to write destinationfile d:\rom
Any help would be great.
Thanks.
maybe you can try to make in d:\rom.nb1 (i thought that was the extention)
Hi,
Apologies in advance if I'm covering old ground.
I'm trying to re-flash a WM6 rom after my previous attempt just left me with the 4 colour screen permanently and as the links to mtty1.42.rar seem to be broken at the moment I decided to re-flash with a different rom.
the problem is that even though I can get the unit into boot-loader mode and the update software appears to see the BA when it checks versions etc. as soon as I hit the upgrade button the BA screen blanks and I get Error 112: CE ROM UPDATE ERROR.
I've tried different roms, different usb ports and different versions of activesync all with the same result.
Any help on this would be great and hopefully I haven't 'bricked' the unit.
Cheers
Duncan
Do you have PH20A2 or PH20B device?
mtty utility can be found using search button
It's a PH20B.
I've now found mtty after a fair bit of searching on other forums..now to see if I can make some sense of it's commands.
A further update: it seems that I've managed to corrupt just the OS part of the ROM. I managed a radio update successfully which means all the USB connection is fine for updating. It just can't access the OS part of the ROM.
Is there anyway to manually format that area of ROM so I can in effect install over clean unit? Infortunately I can't make sense of the mtty commands and don't know what memory address and for how log I should perform the format.
Cheers Duncan
try reflashing
You should know how to use search - however here is the link
http://forum.xda-developers.com/showthread.php?t=348030&highlight=mtty
(Is that hard to put "mtty" in the search field and set BA section only? )
Further update:
Now I don't even get the 4 colour screen. After soft and hard reset I get a dead device. I can put the device into bootloader mode (serial/usb) but as soon as the update software attempts to copy the rom across the screen blanks and I get the ROM Update Error.
Now my thought is to try and flash with the original rom for the device as I have another unit available but using the link from the BA wiki for dumping the ROM doesn't work. I have also tried searching for 'ROM Dump' within the BA section of the forum but there don't seem to be any definitive instructions for this, everyone just keeps asking why not use the wiki or search funtion....
I have used the wiki and the search funstion and I seem to be the first with this situation.
Soft Reset - Nothing
Hard Reset - Nothing
Bootloader - Able to flash the radio rom but as sson as i try to flash the OS rom the screen blanks and I get Error 112: CE ROM Update Error. When I take the device out of the cradle the screen comes back on with the Serial 2.xx screen and I'm back to square one.
I've tried to use the wiki to dump an exisiting working rom but the link on the wiki is broken. I have also searched the BA forum for these intructions but they're not covered as they're already in the wiki..... or not as the case is.
I appreciate you regular users get fed up with noobs coming on and expexting you to do all the work for them but so far I've spent 3 days searching both this site and others to try and resurect my device. I'm not dumb or lazy and would love to be able to do all this myself but without instructions I'm flying somewhat blind.
Any help would be great..... please??
[off topic]
no need for apologies...
we started once like you... some are far worse...
knowing one part and boasting with air on their heads...
since you managed to explain yourself on your first post.
knowing what to search (E.G. MTTY 1.42.rar)
you definitely searched the forum before you posted AND
you stated that the links are not working... that proves it.
we are the one who is sorry because some others think
that they are high and mighty, it sometimes blurs the opinion making.
i dont like opinionated people because i admit that am one too... sometimes...
but that doesnt mean i hate them...
[on-topic]
you never told us what happened when you tried the mtty procedure.
is your last post the result of your mtty experience?
please elaborate how did you end up with that... what did you do before you soft-reset and hard-reset?
SilverSamurai,
Thanks for the quick response.
After my last 'apparently' successful re-flash with Helmi's latest WM6 rom when I hard reset the device I had nothing but a blank black screen, no power LED or anything. Soft-reset was the same. I can reset into bootloader and the PC detects the device when I place it in the cradle. The first part of the update seems to work although it never detects the current OS installed, it always says upgrade from ' ' to 'ver 6.0.0' which is wierd because it always used to say the previous OS version. When I then hit next the progress bar shows on the PC but the BA screen immediately blanks and eventually the PC gives the ROM update error.
I have managed to re-flash the radio rom in this state which proved that I still have access tho the device from the PC.
Using mtty I can run through all the commands to recover from the 4 colour lines screen (even though I'm beyond that point).
USB>set 14 0
HTCST ÚÈÒHTCEUSB>task 28
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>task 0
USB>
It's almost as if the last flash didn't complete and has left the area for the OS 'dirty' with what ever it did manage to flash. What I was hoping to try was to re-format the entire OS section of memory and then try to re-flash again. Using mtty it says you can format sections of memory by stating a start address and the length you want to format but I don't have clue what these should be.
I've tried flashing with WM6, WM5 and a compatible version of 2003 with the same result every time. I would like to dump a rom from another BA I have and try with that but as mentioned earlier the link for that is down at the moment.
I think that's about it. If you need any more info let me know.
Many thanks
Duncan.
let's relist the things you did.
USB>set 14 0
Click to expand...
Click to collapse
1. start OS after a reset
result:
HTCST ÚÈÒHTCE
USB>task 28
Click to expand...
Click to collapse
2. format doc (Disc-On-Chip)
result:
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>task 0
Click to expand...
Click to collapse
3. do hardware clear boot.
Click to expand...
Click to collapse
since i dont want to experiment with my sole BA...
i tried to search for solution...
and with some of my computer instincts i came up with this suggestion...
try this command before "task 28"
"task 7 0" <-- this is the "Do flash ROM lock/unlock" command
"task 2a" <-- fix bad blocks on MFG bootloader and Storage
then try to reflash your BA.
my sources one | two
although it's not BA but i think mtty commands are generic.
it's worth a try.
SS,
Still no joy, it's exactly as it was before.
Just reading through some more posts for bootloader ant it seems at least one other person has the same problem - http://forum.xda-developers.com/showthread.php?t=345181&highlight=bootloader and no resolution posted for that either.
I think I may have got it beyond the point of return.
I've just tried to flash from the blank screen I end up with from the initial attempt and it still detects the device but fails in exactly the same way.
awww... im sorry to hear that.
but dont lose hope.
i'll try to read some more and search for solutions.
and i hope someone with the same problem as
yours that had their BA fixed comes to the foreground.
[off topic]
hmm... come to think of it... we're both Marvel SuperVillains
SilverSamurai said:
awww... im sorry to hear that.
but dont lose hope.
i'll try to read some more and search for solutions.
and i hope someone with the same problem as
yours that had their BA fixed comes to the foreground.
[off topic]
hmm... come to think of it... we're both Marvel SuperVillains
Click to expand...
Click to collapse
These steps are from my notes. Follow these steps. It worked for me last time i tried (3 months back)
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.
4. Run mtty (from downloaded) Choose WCEUSBSH001
5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.
6. type "task 28" to get your device formatted
7. type "task 0" to ask your device reboot
8. take the device out of the cradle, and manually reset it if it does not do that already.
i think he did all of those already,
that's why i posted this in response to his mtty experience.
wouldnt hurt to try it again though.
A bit more info:
I tried the mtty solution again but still the same result.
I finally managed to find the instructions for dumping and exisiting rom to SD card and pulled one from a working unit. I put the card into the faulty BA and booted into bootloader. Pressed 'Power Button' to flash from card and it appeared it was going to work........ until it got to 12% then it failed with the message 'Download Fail'. So still no better off.
What I'm going to try now as it seems anything is worth a try is use the address ranges used to dump the rom to try and format all 3 sections. See if that will give me a clean base to try and re-flash from the sd card. My only worry is if it will format the section of ROM used to store the bootloader info.
I'll post my results shortly.
Now I need to know how to get the bootloader password to enable me to use the 'erase' command through mtty.
The hunt coninues....
Yet more developments.
As the update from SD failed I thought I'd see if it was possible to dump the current contents of the rom to SD using the following
“d2s 80000000 02000000“
“d2s 60000000 00300000 sd a“
“d2s 70000000 01080000 sd a“
The first 2 commands completed fine and checksum was OK. On the 3r command 'd2s 70000000 01080000 sd a' it errored with the following result
USB>d2s 70000000 01080000 sd a
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SDetected one card
SD:ready for transfer OK
pc->drive.total_lba=1E8000
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=B368
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=3D000000
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
DOC_ReadBinary is fail: dwStartAddress=0,dwReadSize=40000.
DOC_ReadBinary is fail: dwStartAddress=0,dwTempReadLength=40000.
*DOC_ReadBinary is fail: dwStartAddress=40000,dwTempReadLength=40000.
*****************************************************************dwCheckSum of Storage=95609D16
cSectionNum=2
psImageSectionInfo[cSectionNum].dwCheckSum=0
psImageSectionInfo[cSectionNum].dwLength=1080000
Stored image of SD/MMC card checksum error!
Now my guess is the Doc_Read_Fail bits are the corrupt part of the rom. If I can find a way to repair these I could then try re-flashing the rom.
what was "task 2a"'s result?
i think that's the chkdsk option of mtty.
we're dissecting the innards of the bootloader.
little by little as we go along the way...
im learning something, i hope you can find the fix for your problem.
SilverSamurai,
Thanks for the help you gave but the unit has finally had enough and totally locked. No power or anything no matter how I try to reset it. I've tried charging for hours, discharging for hours, left the battery out for hours but to no avail. It seemed to take exception to me dumping the rom contents to the SD card. Maybe there was a hardware problem ?? Not sure.
I'll have to see if I can wangle another unit from the company I work for as we're currently selling a bunch that were purchased for a failed IT project on ebay.
it was sad to hear/read that.
anyways. at least we tried to revive it. but dont throw it away.
maybe someday there will be ways how to ressurect your BA.
Happy Computing! err... Mobile Computing!
Hi everyone, if you are having trouble with upgrading the ROM on the US TG01, then this is your topic! Here are the few things you must do the update the ROM:
-Fully charge your battery
-Format your MicroSD card to FAT32, then create a folder called "prg" (don't type the speech marks), and place your ROM in there, and don't forget to change it's extension to .enc from .tsw
-Remove the black tab under the SIM slot, beware, pull it upward, not forward
-Can you see the three "yellow circles" on the SIM slot? The first and third one are what we wanted the connet together. Link/connect them with a wire
-Push the power button for 10 seconds
-Wait a little bit
Done!
Don't thank me, thank leeston for all his continous support, hey, thank you again man!
El Diablo said:
Hi everyone, I've just tried with the mirolg's Sense included English ROM to upgrade the software version on my TG01, but it's just restarting, so nothing changes, any ideas?
Click to expand...
Click to collapse
Not enough detail for me to help you. Please reply to the following.
1. Which method did you use, short pin or sddl+?
2."just restarting", do you mean that the sd downloader doesn't start and goes straight to Toshiba screen or it starts then resets the device making no changes?
3.If the sd downloader starts, does it say 'Variant Invalid' briefly before it restarts?
If you dont know what shortpin or sddl+ means then look HERE.
Sorry, I did not informed you very well,
I've used the sddl+ method. Clicking on the sddl+ restarts the device, just like a soft reset. If I click on the SD downloader, then it says "Invalid filename".
Thanks for the reply.
Now the SD Downloader says "Error occurred during system reset" when I click Download.
Err?
I'm wondering, is that too difficult to help a mate who is having a problem? PLEASE???
El Diablo said:
I'm wondering, is that too difficult to help a mate who is having a problem? PLEASE???
Click to expand...
Click to collapse
I assume you've read the sticky about rom flashing and are still having problems, follow the guide below and let me know how it went.
Download my ROM from HERE.
Download 7Zip from HERE.
Download sddl+ from HERE.
1.Install 7Zip
2.Right click "TG01WP_StonromR7.7z" and choose "7Zip -> Extract to "TG01WP_StonromR7.7z\"" (This will create a folder called "TG01WP_StonromR7" in the same place as the downloaded file)
3.UnRAR sddl+
4.On your storage card create a folder named "prg" (no speech marks)
5.Copy "TG01WP_Stonrom.tsw" to the "prg" folder on your storage card.
6.Copy sddl+ to the root of your storage card. (root = not in a folder, just straight on the card)
7.Open file explorer and go to your storage card and open sddl+
8.You will now have a white screen, with the text "sd downloader - do not remove battery or storage card" (it may not say exactly this, i can't remember just now)
9.Wait
10.Wait a bit more
11. The phone should restart after a bit of waiting, the first boot can take a long time. Be patient.
I only say use my rom because i know it flashes and boots on my 2 devices.
If this doesn't work, pay attention to the on screen messages during flashing and post them here word for word, along with which rom you tried and any other info that you can provide.
Thanks again for your help, downloading right now, I'll inform you about the process.
It doesn't work, only says "Invalid filename" if I click on the TG01_SDDL.
If I click on the tg01_sddl+, the device just restarts, no further changes, still the same problem.
???
BTW, I changed the ROM's name to TG01WP_00.tsw, now the SD Downloader says "Error occurred during system reset".
El Diablo said:
It doesn't work, only says "Invalid filename" if I click on the TG01_SDDL.
If I click on the tg01_sddl+, the device just restarts, no further changes, still the same problem.
???
BTW, I changed the ROM's name to TG01WP_00.tsw, now the SD Downloader says "Error occurred during system reset".
Click to expand...
Click to collapse
Only thing i can think of is to rename the .tsw to .enc.
I tried that too. It doesn't work neither.
BUT,
Thank you very, very much for your afford.
Post edited, detailed informations added.
Have you tried updating you TG with the manufacturer update instead of a cooked ROM? Just to prove that flashing is possible on your device.
I would suggest using the official update and SD Downloader from Toshiba.
Please post back with your experiences.
Yes, actually I've tried with the TG01WP-WM6.5-UK file. Result: Same
El Diablo said:
Yes, actually I've tried with the TG01WP-WM6.5-UK file. Result: Same
Click to expand...
Click to collapse
Where did you get the file? The correct file name should be "TG01WP_5005000176.tsw" or "TG01WP_5005000167.tsw" not "TG01WP-WM6.5-UK"
Just to clarify, is it an Orange UK TG01? Did you buy it from a shop or second hand?
I got the file from Toshiba's official web site (Europe).
Err, I don't know where my device is from, but I can assume you it's a TG01, not the "A" one.
Here, the file is included on the file I've downloaded:
TG01WP_5005000176.enc
Ok, the phone is from USA, I guess it has a different software version updater.
El Diablo said:
Ok, the phone is from USA, I guess it has a different software version updater.
Click to expand...
Click to collapse
The only thing i can see that is left now is to use the short pin method. Details are in the guide to flashing tut in the sickies. You will need to make sure the radio versions are the same first though.
Start\settings\system\about\version info. Where it says radio version is what you need to know. Mine is "5005.1600.05" so would be referred to as 1600 here. If you let me know what radio you have i will upload a ROM with the correct radio for you.
This may take me a little while though.
Radio version is 5001.0000.5319
Very different, heh?
El Diablo said:
Radio version is 5001.0000.5319
Very different, heh?
Click to expand...
Click to collapse
I'll try and find a rom with that radio, for now though try renaming the tsw to .enc and try short pin.
I think some phones released to America have different radio hardware than UK phones. I'm not sure if this is the case for the TG01 though. I think we have a few American forum users. Maybe they could help if they are reading this?
Anyway, I really appreciate your help and support.
Hi everyone, I've read every topic related but couldn't find any proper solution and couldn't post in development forum also I use linux on desktop but could be counted as a dummie for this stuff.
Here's the sory; Got new fresh nook, without reading any instruction backed up my Nook files via its usb connection as an img file. Then like an idiot, I've writed the nookie image to the NOOK's memory as it seems and got an error. After rebooting my Nook it became unstable in screen and started an error pop-up says:
"Your Nook encountered an error that need to restart
If this problem persists, please contact our Costumer Service."
Since not any core files deleted from my failed root try, just tried to format the drive as it seems 223MB; Nothing changed. What I did for recover is trying to boot up with an SDcard installed nookie devs. Nothing changed. Tried to recover from the back-up file which gave me the error of "Error#0 occured while writing to disk at sector 465792". I've tried to format it via partition wizard but still the same error. Also tried the solution of rosa87 introductions from his topic as it fail as everything else and decided to open a fresh new topic as the problem source is different. Also I'm out of U.S to contact any official technical service.
Any reccomendations?
P.S: I'm on windows machine runs 7.
Sphixxx said:
Since not any core files deleted from my failed root try
Click to expand...
Click to collapse
If you wrote the Noogie image onto your NST, then you did in fact overwrite core files.
You're also not the first one to do this mistake.
- At this point your NST could have been easily fixed by booting the n2T-Recovery v0.2 image.
Sphixxx said:
, just tried to format the drive as it seems 223MB;
Click to expand...
Click to collapse
Why on earth would you do that?
If you don't know what is going on, it sure aren't gonna help formatting parts of the internal flash.
- At this point your NST is much harder to repair, but maybe not entirely impossible.
Sphixxx said:
Nothing changed. What I did for recover is trying to boot up with an SDcard installed nookie devs.
Click to expand...
Click to collapse
This part I do not understand.
Sphixxx said:
Nothing changed. Tried to recover from the back-up file which gave me the error of "Error#0 occured while writing to disk at sector 465792".
Click to expand...
Click to collapse
How did you try to write it back? What tools? How big is your backup file?
Sphixxx said:
I've tried to format it via partition wizard but still the same error.
Click to expand...
Click to collapse
Again with the formatting? why?
Sphixxx said:
Also tried the solution of ros87 introductions from his topic as it fail as everything else..
Click to expand...
Click to collapse
Yes it would fail because you've deleted all the critical files needed to recover your NST.
Forgive me if I sound a bit harsh, I do no intend to, but you made things so much worse by starting to format things and I hope others who read this post and get into trouble later on remembers this and ask us for help before trying to fix it themselves
Check your PM in a few mins.
Restart Required Error
I too have this problem, but my NOOK's memory was corrupted.
I don't know what to do... n2T-Recovery 1 and 2 was failed.
Yes it would fail because you've deleted all the critical files needed to recover your NST. Forgive me if I sound a bit harsh, I do no intend to, but you made things so much worse by starting to format things and I hope others who read this post and get into trouble later on remembers this and ask us for help before trying to fix it themselves Check your PM in a few mins.
Click to expand...
Click to collapse
I was deleted the files, but I made a backup.
Help please!