GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > RIFF Box Team > RIFFBOX

Reply
 
LinkBack Thread Tools Display Modes
Old 10-30-2012, 18:19   #481 (permalink)
No Life Poster
 
way2unlock's Avatar
 
Join Date: Sep 2007
Location: EARTH
Age: 42
Posts: 541
Member: 582682
Status: Offline
Sonork: 100.1607124
Thanks Meter: 136

Bro please put here step for usefully help HTC desire only vibrate


Quote:
Originally Posted by jagritisharma View Post
My htc desire repair done by me.........................
  Reply With Quote
Old 11-05-2012, 11:20   #482 (permalink)
Freak Poster
 
Elshad Ngage's Avatar
 
Join Date: Jun 2007
Location: Azerbaijan,Baku
Age: 39
Posts: 326
Member: 520916
Status: Offline
Sonork: 100.1605616
Thanks Meter: 53
Donate money to this user
Quote:
Originally Posted by Sethxp View Post
error:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.26, JTAG Manager Version: 1.35
Selected Resurrector: [HTC Desire]

Connecting to the dead body...OK
Detected dead body ID: 0x202400E1 - CORRECT!
Set I/O Voltage reads as 2.99V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected a Not Initialized FLASH1 Chip, ID: 0xAAAA/0xAAAA (256MB)
Detected a Not Initialized FLASH2 Chip, ID: 0xAAAA/0xAAAA (256MB)
ERROR: No Resurrection Data is available for the NAND Chip with Page size = 0B




Solved by rehoting Flash:


Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.26, JTAG Manager Version: 1.35
Selected Resurrector: [HTC Desire]

Connecting to the dead body...OK
Detected dead body ID: 0x202400E1 - CORRECT!
Set I/O Voltage reads as 3.00V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at 8 MHz]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x55BC (512MB)
Selected Resurrection Data for the NAND Chip with Page size = 2KB

Flashing the dead body...OK
Resurrection complete!


for me not solve this again same problem
Connecting to the dead body...OK
Detected dead body ID: 0x202400E1 - CORRECT!
Set I/O Voltage reads as 3.01V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at 800 kHz]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected a Not Initialized FLASH1 Chip, ID: 0xAAAA/0xAAAA (256MB)
Detected a Not Initialized FLASH2 Chip, ID: 0xAAAA/0xAAAA (256MB)
ERROR: No Resurrection Data is available for the NAND Chip with Page size = 0B
  Reply With Quote
Old 11-27-2012, 13:13   #483 (permalink)
Freak Poster
 
Join Date: Jan 2010
Location: romania
Age: 33
Posts: 234
Member: 1202098
Status: Offline
Sonork: none
Thanks Meter: 19
Donate money to this user
Any ways to repair radio bricked desire? cant install any rom in it... ruu say s image version 2.35.00 hboot is 1.02.0001.. originally it has orang001 cid but with riff we changed to universal 11111111 ... help please.
  Reply With Quote
Old 12-29-2012, 06:28   #484 (permalink)
Junior Member
 
Join Date: Dec 2012
Posts: 1
Member: 1859912
Status: Offline
Thanks Meter: 0
Riff-Box 'Tips & 'Tricks

Good day, and pleased to meet you --

I see many people here making the same mistake and going rage crazy on thier riff box. **Dont break it! that thing is gold!!!!** I'm so busy in my day to day mobile data device manufacturing / interfacing / programming / integration that I seldom get a chance to post and help people with problems or situations regarding the Joint Test Action Group system of interfacing.

First, Riff-box is like a super - duper mega big time advanced adb.exe. Escentially (Not literally) it works by providing you a window to transport information threw. Litterally, threw. I think about myself trying to fit a refrigerator threw a bathroom window. There is only so much I can fit threw a bathroom window.

Almost all comments/problems in this thread have to do with people trying to fit a refrigerator threw a bathroom window. RTCK is power up self test type system that regulates all the other signle feeds (ie, TDO, TDI, NRST ect ect) NOT all phones have this option, and this option is the equivelant of easily tossing the refrigerator right threw the bathroom window with no problem.

This demands bandwidth, lots of it, being pushed in the form of 100's 0f millions of computations surging threw those tiny serial cable wires, or pogo pins. Just because the Riff Box software is defaulting an option to show a device is RTCK ready, does not mean that it is true.

Try turning off RTCK, use a low transfer rate. Remember kh's are MUCH smaller than gh's experiment with the different speeds, you'll learn that every device has a specific "prefered" speed it will operate the most efficiently under. To low of a speed, and it will fail, to fast, same fail. You just have to test and play with it, make a game out of it.

When I have problems resurection a phone that includes its own DLL software, I will generally break into a combo of screen play jumps. I start with a resurrect attempt right off the bat, try different speeeds and hope I find something that sticks.

If this doesn't work, I'll go to the Jtag read/write pulldown and choose connect and get id. This will usually result in a failure, which is not a big deal.

Now, this is a good tip to remember, if the connect and get id, fails, click reset target, if you notice the phone vibrate, change in color indicator patterns, or an obvious boot up, this is a good sign to know your not so much at fault as you think.

Refrigerators threw bathroom windows ironically is a delicate proccess.

Dont get frustrated if you see the gaping wound red letters making up that horrible word.......... FAIL..... It is a Jtag commonality. You will fail, many times right before succeeding, whithout really changing anything.

Jtag and most software works on alot of reverse engineering dialog that the riff box and the computer play out with each other. This is by no means a finite assurance in collegic academics and the process has alot to do with trial and error.

Its like the old saying, "Lose a thousand times, oh well. Succeed once, your done."

Click connect and get id...... FAIL


Click connect and get id..... FAIL FAIL


Click copnnect and get id....

you get the message. Bounce around, go to DCC pulldown and try to read allocation units, and after a long mission threw the software underworld, try going back to resurrect and play with more TCK speeds...


Remember, dont get mad or curse the box - lack of knowledge and exploration is a big part of this davikish virtual machine we call android. We are all learning - and to learn, you must be wrong first.

Another tip to try, is keep RTCK on, but change the TCK speed under it.

If nothing more, this will will help learn the ins and outs of the softwares quirks and idioscyncracies.

Addressing a few other problems I noticed on this thread --

Red and green blinking light, no charge, still dead after res --

Most likely your resurrect has repartitioned the battery stats to your device. No matter what you do, you will not be able to initially charge a battery with that phone. Best bet is to charge a battery for 24 hours on an alternate device, or external charger. This will give you more time to play with any boot failure issues after resurrect.

Make sure you have the Java SDK (Jdk SE), and the proper HTC drivers and adb globals set, these are important.

Good luck guys, I probably will not be able to post again for a loooong time. Cheerio.
Attached Images
File Type: jpg IMAG0245.jpg (632.6 KB, 60 views)
File Type: jpg IMAG0246.jpg (831.7 KB, 62 views)
  Reply With Quote
Old 05-14-2013, 16:16   #485 (permalink)
No Life Poster
 
Join Date: Mar 2009
Location: Europe Wienna
Posts: 1,269
Member: 984046
Status: Offline
Thanks Meter: 255
Code:
[5/14/2013 2:05:28 PM] [START OPERATION_ID = DCC_ERASE_MEMORY]
[5/14/2013 2:06:47 PM] Open serial port...OK
[5/14/2013 2:06:47 PM] Connecting to the RIFF Box...OK
[5/14/2013 2:06:47 PM] Firmware Version: 1.34, JTAG Manager Version: 1.48
[5/14/2013 2:06:47 PM] Selected Resurrector: [HTC Desire V1.00]
[5/14/2013 2:06:47 PM] 
[5/14/2013 2:06:47 PM] Connecting to the dead body...OK
[5/14/2013 2:06:47 PM] Detected dead body ID: 0x202400E1 - CORRECT!
[5/14/2013 2:06:47 PM] Set I/O Voltage reads as 3.01V, TCK Frequency is RTCK
[5/14/2013 2:06:47 PM] Adaptive Clocking RTCK Sampling is: [Sample at MAX]
[5/14/2013 2:06:47 PM] Settings Code: 0x05010000000000000000000020000000
[5/14/2013 2:06:47 PM] 
[5/14/2013 2:06:47 PM] Resurrection sequence started.
[5/14/2013 2:06:47 PM] Establish communication with the phone...OK
[5/14/2013 2:06:47 PM] Initializing internal hardware configuration...OK
[5/14/2013 2:06:47 PM] Uploading resurrector data into memory...OK
[5/14/2013 2:06:47 PM] Starting communication with resurrector...OK
[5/14/2013 2:06:47 PM] 
[5/14/2013 2:06:47 PM] Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x55BC (512MB)
[5/14/2013 2:06:47 PM] 
[5/14/2013 2:06:47 PM] Erasing FLASH1 memory from 0x000000000000 to 0x00001FFFFFFF...OK
[5/14/2013 2:06:47 PM] WARNING: Erasing Error (0x24) at 0x000001140000. Attempt to Repeat again.
[5/14/2013 2:06:47 PM] WARNING: Erasing Error (0x24) at 0x000001140000. Attempt to Repeat again.
[5/14/2013 2:06:47 PM] WARNING: Erasing Error (0x24) at 0x000001140000. Attempt to Repeat again.
[5/14/2013 2:06:47 PM] WARNING: Erasing Error (0x24) at 0x000001140000. Attempt to Repeat again.
[5/14/2013 2:06:47 PM] WARNING: Erasing Error (0x24) at 0x000001140000 is Ignored. Erase continues.
[5/14/2013 2:06:47 PM] WARNING: Erasing Error (0x24) at 0x000001300000 is Ignored. Erase continues.
[5/14/2013 2:06:47 PM] WARNING: Erasing Error (0x24) at 0x00000BBC0000 is Ignored. Erase continues.
[5/14/2013 2:06:47 PM] WARNING: Erasing Error (0x24) at 0x00000C180000 is Ignored. Erase continues.
[5/14/2013 2:06:47 PM] WARNING: Erasing Error (0x24) at 0x000015720000 is Ignored. Erase continues.
[5/14/2013 2:06:47 PM] WARNING: Erasing Error (0x24) at 0x000019620000 is Ignored. Erase continues.
[5/14/2013 2:06:47 PM] Completed in 00:01:17.782 (Average Transfer Rate: 6740.48 kB/s)
[5/14/2013 2:06:47 PM] [FINISH OPERATION_ID = DCC_ERASE_MEMORY]

[5/14/2013 2:07:08 PM] [START OPERATION_ID = RESURRECT]
[5/14/2013 2:09:20 PM] Open serial port...OK
[5/14/2013 2:09:20 PM] Connecting to the RIFF Box...OK
[5/14/2013 2:09:20 PM] Firmware Version: 1.34, JTAG Manager Version: 1.48
[5/14/2013 2:09:20 PM] Selected Resurrector: [HTC Desire V1.00]
[5/14/2013 2:09:20 PM] 
[5/14/2013 2:09:20 PM] Connecting to the dead body...OK
[5/14/2013 2:09:20 PM] Detected dead body ID: 0x202400E1 - CORRECT!
[5/14/2013 2:09:20 PM] Set I/O Voltage reads as 3.01V, TCK Frequency is RTCK
[5/14/2013 2:09:20 PM] Adaptive Clocking RTCK Sampling is: [Sample at MAX]
[5/14/2013 2:09:20 PM] 
[5/14/2013 2:09:20 PM] Resurrection sequence started.
[5/14/2013 2:09:20 PM] Establish communication with the phone...OK
[5/14/2013 2:09:20 PM] Initializing internal hardware configuration...OK
[5/14/2013 2:09:20 PM] Uploading resurrector data into memory...OK
[5/14/2013 2:09:20 PM] Starting communication with resurrector...OK
[5/14/2013 2:09:20 PM] 
[5/14/2013 2:09:20 PM] Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x55BC (512MB)
[5/14/2013 2:09:20 PM] Selected Resurrection Data for the NAND Chip with Page size = 2KB
[5/14/2013 2:09:20 PM] 
[5/14/2013 2:09:20 PM] Flashing the dead body...OK
[5/14/2013 2:09:20 PM] Resurrection complete!
[5/14/2013 2:09:20 PM] [FINISH OPERATION_ID = RESURRECT]

And it looks that KA1000015M was allready replaced.

Phone goes to recovery, but radio timeout when diag is deployed, and with pb99img.zip can't be flashed - it just's hangs on checking pb99img.zip after progress bar came all the way up.


any thoughts?

New flash ic, or reflow?


No charging light whatsoever.


Br

Haltec
  Reply With Quote
Old 08-16-2013, 13:49   #486 (permalink)
Junior Member
 
Join Date: May 2013
Posts: 1
Member: 1932066
Status: Offline
Thanks Meter: 0
hey everybody
any one help to make my htc desire u dual mobile on....
its suddenly switchoff and not getting on
battery showing full charged
plz give solution to this
  Reply With Quote
Old 09-06-2013, 22:02   #487 (permalink)
No Life Poster
 
Join Date: May 2005
Age: 40
Posts: 9,814
Member: 146708
Status: Offline
Sonork: 100.108221
Thanks Meter: 1,601
Quote:
Originally Posted by Mobajer View Post
Hello, i have changed flash ic on htc desire. in ressurection process i set hboot 0.93, write correct imei, but dont know what cid should i write. ressurection is ok. when try flash phone throw RUU newest software version, it fully rewrites, but get error. and hboot meniu shows:
hi..


which flash ic did u use for htc desire..? i have the same pb.. and i need to change it..
  Reply With Quote
Old 09-06-2013, 22:03   #488 (permalink)
No Life Poster
 
Join Date: May 2005
Age: 40
Posts: 9,814
Member: 146708
Status: Offline
Sonork: 100.108221
Thanks Meter: 1,601
Quote:
Originally Posted by med_ion View Post
Hi
I want to order some HTC flash ic (ex. desire) can someone send me a webpage from here i can order? i didn't find on ****, or the sites i know.
did u find it..? desire nand flash ic.?
  Reply With Quote
Old 12-06-2013, 07:26   #489 (permalink)
Junior Member
 
Join Date: Jul 2011
Posts: 10
Member: 1609471
Status: Offline
Thanks Meter: 0
HTC T-Mobile G2
IMEI: 359116032394505
Unlock code please!
T.Y , more power!!!
  Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
thread Thread Starter Forum Replies Last Post
Unlocking 5190 Ryu Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 23 01-07-2018 17:14
$50 Reward for unlocking my 6150!!! TheDon Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 5 03-23-2015 14:21
FAQ about unlock n0kia man0n Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 6 11-29-2010 19:06

 



All times are GMT +1. The time now is 06:14.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.23265 seconds with 10 queries

SEO by vBSEO