What's new

Solved RGH update issue?

D

ddsdavey

Newbie
Messages
5
Reaction score
0
Points
35
Hi guys,my issue is almost identical to to another thread on this forum.
Ok,ive restored about 8 consoles ive had stored using reset glitch,i foolishly decided to change the osig of one of the consoles as i had a few Samsung drives and the consoles osig was liteon and i new this would be an issue with lt2.0.
I glitched the console approx a week ago and since then i have updated it,like a fool i am i patched the original 9199 image i dumped and wrote that back,obviously the console should be on 13955 having updated midweek so coughs up 0022. I have a 13955 image and imported my kv/config and cpu corresponds correctly,Ive tried adjusting the ldv values but i cant seem to source any info on what these should be,it went directly from 9199 to 13955 and its values at 9199 were (from top) 0,7,6,what should they be? should i change my pairing data also?
I would appreciate your input guys.
 
Brother Jordan

Brother Jordan

מספר אחד
VIP
Retired
Sinner Hardened Veteran MotM
Messages
16,615
Reaction score
11,285
Points
1,800
13599, not 13955. You shouldn't have imported your KV and config to a new image, simply change your OSIG and re-flash the NAND.
 
D

ddsdavey

Newbie
Messages
5
Reaction score
0
Points
35
I do need to import them because i need to build a 13599 image.
I know i can change osig and reflash. But i dont have a 13599 dump of my nand and i updated to 13599,so i need to make a 13599 image with my 9199 dump as you cant simply write back original 9199 image if its been updated to 13599.
Sorry about the kernel number mix up,ive dont hundreds of jtags but it dont stop me being foolish lol!
This is all about getting a retail 13599 built from my 9199 dump,i usually wouldnt need help with these matters,its purely because its rgh,if it was pre 7371 then i would not be asking.
Sorry if i was a bit unclear at first.
Seems your the guy to ask on these matters bud.
 
Brother Jordan

Brother Jordan

מספר אחד
VIP
Retired
Sinner Hardened Veteran MotM
Messages
16,615
Reaction score
11,285
Points
1,800
I do need to import them because i need to build a 13599 image.
I know i can change osig and reflash. But i dont have a 13599 dump of my nand and i updated to 13599,so i need to make a 13599 image with my 9199 dump as you cant simply write back original 9199 image if its been updated to 13599.
Sorry about the kernel number mix up,ive dont hundreds of jtags but it dont stop me being foolish lol!
This is all about getting a retail 13599 built from my 9199 dump,i usually wouldnt need help with these matters,its purely because its rgh,if it was pre 7371 then i would not be asking.
Sorry if i was a bit unclear at first.
Seems your the guy to ask on these matters bud.

I'm confused. If you already RGH'd it, what is stopping you from getting a dump of your new 13599 image.. or did you try and re-flash and not have a backup of the 13599?
 
D

ddsdavey

Newbie
Messages
5
Reaction score
0
Points
35
or did you try and re-flash and not have a backup of the 13599?
Yes,i updated midweek,decided at end of week to change osig,having an abundance of samsung drives,lt2.0 wont boot xgd3 unless osig so made sendse to change osigs.So obviously being a dumb *** i patch the osig of my 9199 image and write it to nand.So now im left with 0022,ive tried everything i can think of just thought id reach out.
 

Similar threads

Oblivion
Replies
30
Views
942
HuskerHeaven
HuskerHeaven
XBL Zeus
Replies
28
Views
1K
XBL Zeus
XBL Zeus
Tupac Shakur
Replies
2
Views
276
Tupac Shakur
Tupac Shakur
Tupac Shakur
Replies
8
Views
469
Tupac Shakur
Tupac Shakur
Chips 98
Replies
4
Views
425
TeddeRz
T
Top Bottom
Login
Register