yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Q&A, Help & Troubleshooting] Soprono:
Hello There,

Being new to the site I often read, follow and apply and keep quiet but i really need help on this situation please. Iv seen that Omega has released a few new roms in short succession and im due for a rom upgrade (on omega v5 still). Anyways i was just wondering i see that Omega Pro is avaliable on play store and was wonder what is the quickest way to keep up to these rom updates without loosing my data all the time?

My typical process of getting updates is to:

1. Downlaod Rom

2. Clear Cache and Data

3. Install Rom

4. Install Titanium

5. Restore From Titanium All My Apps.

But i was wondering is there methods to shortcut the restoring if im staying on the same rom? I know people say you can just flash and not clean cache and data but i want to confirm this before as to how nightlies are delivered in the cynogen architecture OTA?

Regrads in advance, i have tried searching (maybe didnt use the correct terminologies) and thought id ask a question to get a specific answer i need .

Regards

Soprono
[Galaxy S 4 Q&A, Help & Troubleshooting] lohiyashubham12:
Thanks for posting this

I also have the same doubt and registered with xda just to ask this..

Let me elaborate..

I am using currently Omega rom v7..

now the v8 is launched..

Do i have to download whole of it again? (around 1.5 GB)
[Galaxy S 4 Q&A, Help & Troubleshooting] SevenD2:
I haven't had any problem with just flashing the new rom on top without clearing data or cache (I think the rom clears the cache for you)

And yes to update you need to download the entire rom again, though if you look at the change log, the changes aren't that much.

However I do want to know the change log for each Samsung update
[Galaxy S 4 Q&A, Help & Troubleshooting] lohiyashubham12:
Thanks

Thanks for answering.. :good:

I also was Using Adam Kernel Previously but now I use Perseus...

If you haven't tried yet,Try it..its much better :)
[JAM, MDA Compact, S100 General] inkdot:
Community, hey!

First of all I want to thank ITSME and all the other good contributers that has added value to the "scene".

I see that many with me needs to modify the HTC Magician ExtRom partition. In this message i want to discuss how this can be done, and eventually help implement the kind of solution needed.

I am quite new to the device, so please clearify on the bulletpoints. [ Sanitycheck / reject / comment ]

A) I see three different scenarios for changing ExtRom on Magician.

-a1- mount the extrom as disk, and modify directly on device.

-a2- modify .nb* file before flashing of the phone.

-a3- modify flashmem directly through bootloadermodus.

B) Extended ROM image for Magician has been decrypted by Itsme, so modifying .nb* file, apply encryption and flash will be a suitable way to modify Ext ROM ?

C) All that has to be done is to make a tool to modify and recrypt the .NB* file prior to flashing?

D) Is the format of the decrypted .NB* file well defined?

E) Any other "issues" i should think about?

I understand that many of these Q's probably is answerd through out the message board, but i wan't to have one focused tread that eventually ends up in someone (me?) implementing the solution in a public tool.

Regards InkDot
[JAM, MDA Compact, S100 General] inkdot:
Does the Ext Rom of Magician allso have the same structure as described by Itsme when decrypted? - If so we can mount it as Fat16 like Qtek 2020 early days modifications?? - Please comment..

--- from itsme XDA-II flashfile formats writeup---

ms_.nbf

this file is build up as follows: 00000000 00000040 NBF header

00000040 00000028 devtype, operator, language

00008040 00025800 first bitmap

00030040 00025800 second bitmap

00070040 01000000 FAT16 filesystem

01070040 end of image

the bootsplash image is there twice, at
[JAM, MDA Compact, S100 General] inkdot:
Short update!

It did mount as expected on linux...

now the problem is to encode it back to its original coded state..

Trying to understand doctor Itsme's perl - not easy for me.. no perl skills.. ;( If someone else has tried this, please reply with your findings..

What scares me is the "Checksum" in the header!

If it is an actual checksum of the Fat16 structure like Itsmes naming can indicate; we have a problem unless we find the checksum algo that is used.

I can allways encrypt it with the same "checksum"-variable and hope that the naming is "scam".

Please add comments.. i'm in pain
[JAM, MDA Compact, S100 General] tupisdin:
I'am using dumb method ;)

for example.... we have ms.nbf file (encrypted) you need decrypt it at first.....

after i'am split file for two parts .... ms.header - (first 128 bytes) and other ms.main part.(section starting from header)

After that i simply opening ms.main as disk image.... copying that i need... saving ...
[JAM, MDA Compact, S100 General] inkdot:
Yep that works!! The problem is to Encrypt it again!!

If the Magician uses a real checksum of the fat16 datapartition as the initial XOR encryption key, i must know the checksum algo used to calculate it to be able to encrypt it back... ;/
[JAM, MDA Compact, S100 General] tupisdin:
type ms.header > ms_.nba

type ms.main >> ms_.nba

xda3nbftool -c -u ms_.nba

try this ;)
[JAM, MDA Compact, S100 General] torsen:
tupisdin,

Are you using xda3nbftool.exe to calculate a checksum for the Magician extended ROM ?
[JAM, MDA Compact, S100 General] tupisdin:
yes
[JAM, MDA Compact, S100 General] inkdot:
Good for you ;)

1. First i split the original crypted file into two parts.

ms_.nbf ---> ms_header(172bytes) ms_fat(all the remaining bytes)

2. Then i decode the header with the modified UUEncoder routine found on the board. This gives me a good looking readable header. Now = 128bytes.

3. Now I have one "ms_header" file and one "ms_Fat16 part"

the ms_header is 128 bytes big and no longer "base64-like-encoded". It looks good!

4. Then i decode the ms_fat16 part with the new XOR routine from itsme.

5. To check that everything is ok.. i merge the files into one again, and recalculate the checksum with xda3nbftool.

Unfortunately the checksum differs from the original checksum. ;/

1 ) Where can i find the source for XDA3nbftool??

2 ) What is wrong with my procedure

3 ) Is the checksum calculated only from the Fat16 part or does it include other header data?

Regards,

InkDot
[JAM, MDA Compact, S100 General] tupisdin:
Checksum changed every time.
[JAM, MDA Compact, S100 General] inkdot:
Hemm, i understand that the checksum changes if data is changed! But i try to merge the SAME data as i decrypted and splitted 1 minute earlier..

That should give me the same checksum (!?)

Therefor i beleve that i got wrong version of XDA3nbf tool, or or something else is wrong..

How did you decrypt the header???
[JAM, MDA Compact, S100 General] tupisdin:
xda3nbftool recalculating checksum every time.

It is not an error.

for example.

xda3nbftool -x ms_.nbf ms_.nba 0x20040522

After that open ms_.nba with your favourite hex editor cut first 128 bytes and save them to another file(ms.header).

Save another part to another file(ms.main).

no you can delete original ms_.nba

Open main part(fat virtual disk) in winimage (for example)

Add, modify what you want....

After that in command promt:

"type ms.header > ms_.nba"

"type ms.main >> ms_.nba"

Then:

xda3nbftool -c -u ms_.nba

And at last

xda3nbftool -x ms_.nba ms_.nbf 0x20040522

No you can flash your new ms_.nbf file to your device(do not forget to change operator and language id)

That's dumb and simple method.
[JAM, MDA Compact, S100 General] inkdot:
Now i understand!

What i have learned from this is that there is ONE or more Magican operator roms that uses the old XOR technique that is decodable with Xda3nbf

And ONE or more Magican operator roms that uses the NEW encryption method.

You Tupisdin is one of the lucky ones to work with a Rom based on the old structure! Please correct me if i'm wrong.

I think that the rom you started with had an header that was not Base-64-like-encoded

Regards,

InkDot
[JAM, MDA Compact, S100 General] tupisdin:
Encryption method is changed in new ROM versions.
[JAM, MDA Compact, S100 General] tupisdin:
New NBF format described by mamaich here

http://xdaforums.com/viewtopic.php?t=14877&highlight=encryption
[JAM, MDA Compact, S100 General] inkdot:
Yes, and the only thing that remains is to calculate a correct checksum for the extended rom...

To solve that we have tried to find the algorithm / method used to get the same checksum as it was in the original decrypted rom..

InkDot..
[JAM, MDA Compact, S100 General] tupisdin:
Something goes wrong?

This method perfectly works for me.

Or you are trying to encode something with new method?
[JAM, MDA Compact, S100 General] tupisdin:
As i sad checksum will be change every time when you recalculate it.
[JAM, MDA Compact, S100 General] inkdot:
1. Ofcourse CRC changes if data changes! AND therefor i try to find the right CRC algorithm using a datasource i allready know the correct CRC of! Still i cannot get back to the correct CRC, that prooves my algorithm or method wrong.

2. I need to make the extendedrom into a mountable file. To do this I could have uses XDA3NBF.exe, but it does not work with the new encryption technique.

3. I therefore decrypt it manually with Itsme's method, and get a perfectly mountable datafile. I allso do the base64 transelation of the header into a classical readable format.

4. To build a file that i can FLASH to the device i need to put an uncrypted header, and an uncrypted FAT together, and apply the correct checksum.. And then xor the data with the checksum as initial XOR password! (if you have seen the new algorithm.)

5. Unfortunately i cannot get the same CRC as the file had initially. that means that the CRC check is not served the exact same data as before.

This is a problem because the CRC value is now used as encryption password!!

Conclusion: Either i have something accidentaly wrong in my rebuildt nbf file, OR the technique for calculating data differs from the technique used in XDA3NBFTOOL.

For you, tupisdin, it means that either you have an old rom using traditional XOR encryption from Password, not CRC, or you did not manipulate the extended rom. Did you use password? Ie. the password supplied by NightMarE? (That method does not work with newer roms..)

Regards

Inkdot
[JAM, MDA Compact, S100 General] tupisdin:
for new roms i use same method....

There is only one difference.

I'am decoding ms_.nba with new algo.

change in fat part what i need.... after i'am replacing header with old one..... and use xda3nbftool and old maupgrade to update extended rom in my device :)

Dumb and simple ;)
[JAM, MDA Compact, S100 General] inkdot:
Good, Then i will try with old header and with new FAT16 extrom partition.

Still looking for a way to make the Extended_Rom partition writable on the device like on the old XDAII and XDAIII.. but the new VDISK is a showstopper..

-Or is it just about applying finding the right password, and applying it with the EXTRomUnlocker tool?? If so we can bruteforce crack it!

Inkdot
[JAM, MDA Compact, S100 General] sergiojsilva:
Hello... this is my first post...

I would like to try your process but i cant find the tools you have. Where can i get the "UUEncoder routine" and "XOR routine from itsme"? I already searched in forum and didnt find anything...

Thanks in advance...
[JAM, MDA Compact, S100 General] Bebbo:
You are quite right about the CRC in the UUEncoded type roms not being calculated the same way using the old CRC routine.

I have written a little application which allows you to decode and encode roms as well as edit the splash screens, header and has a FAT16 filing system built in. It is based on the code in xda3nbftool amongst other code with thanks to itsme and maimach.

Using the old non-UUEncoded roms the crc calc routine I use works flawlessly (I check an incoming file with the CRC routine and it always matches to confirm valid decoded data) however the new roms don't match the stored CRC. I have tried using reverse CRC calc routines and different CRC base values all to no avail. This is presently stopping me from releasing a full application as I cannot completely re-encode the newer roms or check that they have successfully decoded.

(For info - the string CRC value in the header is used as the starting value to encode the very first byte of the rom data using the new XOR routine. This XOR routine uses the previous word to encode the next data word through the entire file)

If anyone has the skill to disassemble the RUU.dll to find out what has changed I would be very grateful!
[JAM, MDA Compact, S100 General] milklok:
Why not release the program first? So that people who have old ROM can customerize their machine easily? :)

I think if you do so there will be more people interested to help to make the new version of your program. Bacause now not many people know that it is possible to modify their Extended ROM.
[JAM, MDA Compact, S100 General] Bebbo:
It is still in my opinion only an alpha version (Slightly buggy and not fully tested). MDAIIIUser has a copy which he is testing and I recieve almost hourly reports on oddities from him. I do not want to release to everyone in this state or I will be innundated with 100 x same problem emails!

Give it a week or so and it should be ready for release.
[JAM, MDA Compact, S100 General] milklok:
Yeah then better fine tune the program before release it to public.

Thanks a lot for your effort. :wink:
[JAM, MDA Compact, S100 General] wilco_sg:
when's the release?

anxiously awaiting the release... :)

its been a week ... right?
[JAM, MDA Compact, S100 General] whdumg:
Could please let me know how the testing is going. Also what password did you use with the nbf file, 20040522 does not work on the 1.06 versions.

Regards
[LG Optimus L9 P760, P765, P768, P769] aarongotgame:
soooo i deleted build.prop from system on my optimus p769v20d

what do i do now.... detailed instructions
[LG Optimus L9 P760, P765, P768, P769] aarongotgame:
i flashed 10g.. i might stay on ics.. jb was cool and all but the volume sucks
[LG Optimus L9 P760, P765, P768, P769] ionuutzuu:
Try use power amp with max preamp and some custom setting at eq and the volume is rlly high :) i wasn't satisfied by its level too.
[One (M7) Themes and Apps] MaWline:
Hi,

is there a nice theme for the Car-App out there?

Greetz, MaW

Sent by my HTC One using tapatalk.
[One (M7) Themes and Apps] jonas2295:
Like this? :)

View attachment 2078250
[One (M7) Themes and Apps] MaWline:
Yes, more or less ;)

I'm more on that chrome / red - theme though.

But where do I find some like yours?

Greetz, MaW

Sent by my HTC One using tapatalk.
[One (M7) Themes and Apps] jonas2295:
Get renovate rom and choose renovate theme :)
[One (M7) Themes and Apps] MaWline:
Well, that's not really what I'm looking for. I'm fine with the viper-theme...

I just want the car-app to change..

Greetz, MaW

Sent by my HTC One using tapatalk.
[One (M7) Themes and Apps] jonas2295:
Well then you have to wait for viper.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] reddevilboyz:
i just got S view cover for my phone... i was irritated by the inability to shuffle songs through the cover... i just wonder is there a tweak that allow it to do so. any suggestion?
[Android Q&A, Help & Troubleshooting] M4nu3l1c4t4:
Hello forum ;)

it would be useful to have the Android OS on our psp? ? I do not intend to have a complete 100% system , but maybe run a browser and some small app with wifi. What do you think? Would it be possible?

Inviato dal mio MB860 con Tapatalk 2
[Android Q&A, Help & Troubleshooting] jglm4u:
Would be nice:cool:
[Android Q&A, Help & Troubleshooting] RoberGalarga:
333Mhz of CPU, 32Mb of RAM and a non-ARM CPU... An Android themed app is 100% possible, but a real Android environment I don't think so.
[Android Q&A, Help & Troubleshooting] M4nu3l1c4t4:
It's not possible? :/

Inviato dal mio MB860 con Tapatalk 2
[Android Q&A, Help & Troubleshooting] RoberGalarga:
The psp doesn't have enough power... sorry.

As I said, you can get (or develop) an app that looks like Android (and it's pretty easy, btw), but don't expect more than that.
[Android Q&A, Help & Troubleshooting] M4nu3l1c4t4:
Thank's for answear! ;)

Inviato dal mio MB860 con Tapatalk 2
[Android Q&A, Help & Troubleshooting] strawberry23:
yes , sorry about that.:(
[HTC Sensation] Zatorra:
Hey guys, after some flashing my device is stuck in a bootloop. It goes to htc logo, but it doesnt go on from that, it keeps rebooting all the time. I can reboot to bootloader but NOT TO RECOVERY.

Here I show you my sensation details:

-Firmware -3.33-

PYRAMID PVT SHIP S-OFF RL

HBOOT 1.27.1100

RADIO-11.24A.3504.31_M

OpenADSP-v05.6.0.2226.00.0418

eMMC-boot

Jan 13 2012, 17:33:34

I have the original HTC DRIVERS (HTCDriver3.0.0.007) and SUPERCID.

I tried many ways but cant seem to enter recovery, do u think my sensation is bricked? How can I repair it?

Things I've been told to do and

dont seem to make any change:

-Install 4Ext in every way possible.

-Install alternative recovery (I tried ClockWorkMod)

-Install last RUU ( I installed RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76

A.3504.00U_11.24A.3504.31_M_release_280871_signed)

-Install an old RUU (I installed RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007 .00P_10.11.9007.15_M_release_192608_signed)

Many thanks in advance
[HTC Sensation] ashkan-khatar:
hi,

unlocked/locked? s-off/s-on? ROM? kernel? what caused the bootloop?
[HTC Sensation] Zatorra:
It says locked now because I installed the 3.33.40 ruu, I think that's why. It is s-off. The brick was caused by flashing some roms. it was working quite good but sudenly it stopped working and entered the bootloop. Now after flashing this ruu it keeps in the loop.

Thanks for the fast reply btw :)
[HTC Sensation] Zatorra:
This is what it says now:

****LOCKED****

PYRAMID PVT SHIP S-OFF RL

HBOOT 1.27.0000

RADIO-11.24A.3504.31_M

OpenADSP-v05.6.0.2226.00.0418

eMMC-boot

Jan 13 2012, 17:33:34
[HTC Sensation] rzr86:
ok now flash again recovery and after that install a custom rom

---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------

you are missing the details:)

those in bold mean that he is on S-OFF and has(or had) a patched hboot(unlocked)
[HTC Sensation] Zatorra:
Ok, I installed 3.33 firmware again and now it installs 4ext from fastboot but when i hit recovery is stuck in the bootloop.
[HTC Sensation] rzr86:
try this

from bootloader(fastboot usb)

do this command

fastboot reboot recovery (open a cmd window from pc)
[HTC Sensation] Zatorra:
c:\adb>fastboot reboot recovery

usage: fastboot [ <option> ] <command>

commands:

update <filename> reflash device from update.zip

flashall flash boot + recovery + system

flash <partition> [ <filename> ] write a file to a flash partition

erase <partition> erase a flash partition

getvar <variable> display a bootloader variable

boot <kernel> [ <ramdisk> ] download and boot kernel

flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it

devices list all connected devices

reboot reboot device normally

reboot-bootloader reboot device into bootloader

options:

-w erase userdata and cache

-s <serial number> specify device serial number

-p <product> specify product name

-c <cmdline> override kernel commandline

-i <vendor id> specify a custom USB vendor id

-b <base_addr> specify a custom kernel base address

-n <page size> specify the nand page size. default:

2048
[HTC Sensation] Zatorra:
I did fastboot boot recovery.img and this is what it does:

downloading 'boot.img'.... OKAY [1.505 s]

booting... OKAY[1.505 s]

finished. total time: 1.509s

bootloop still is there
[HTC Sensation] rzr86:
hmm,

try to flash 4ext using this method

http://xdaforums.com/showthread.php?t=1631861 (only step 2)

otherwise use third option from here

http://xdaforums.com/showthread.php?t=1472298 (post #1 step 1)
[HTC Sensation] Zatorra:
I did first step, flashed allright, yet bootloop.

I didnt do second step because I did a couple mins ago and I have 3.33 firm now.
[HTC Sensation] rzr86:
do you mean the third option from the second link?

if yes use that pg58img.zip

it doesn't contain firmware only the recovery.img

flash it from bootloader
[HTC Sensation] Zatorra:
Oh sorry. I did install it now via bootloader using the pg58img. I hit recovery on bootloader, yet bootloop. I think it installs it ok, but it ccant reach it.
[HTC Sensation] rzr86:
do reboot bootloader and try to enter again to recovery

also try a different recovery
[HTC Sensation] Zatorra:
I will try CWM, could you please tell me the command to reboot exactly? The one you gave me before didnt work for me :/

Edit: managed to reboot bootloader but it makes no change
[HTC Sensation] Zatorra:
I tried with clockworkmod and it installs it ok, yet the loop is there. Starting to loose a bit of faith hahahah

You're a boss dude, many thanks for ur help!
[HTC Sensation] rzr86:
you also usd a ruu.exe and it didn't worked

now i am out of ideas:(

if i think something else i will tell you

or if somebody has something to suggest
[HTC Sensation] Zatorra:
Much thanks dude, do u think the unbrick project could help me?

Enviado desde mi GT-I9300 usando Tapatalk 4 Beta
[HTC Sensation] rzr86:
your device it is not bricked as long as you can enter to the bootloader

so i think it won't help
[HTC Sensation] onemanshow85:
a bricked device is when it doesn't do anything at all anymore. It won't boot and doesn't respond to anything, even when it's fully charged and wall plugged. the screen will stay permanent black. So there's no point in doing the unbricking project.

Bootloop is generally caused by ROM's that are incomaptible with FW. and as long as you can't enter recovery, the bootloop is not your first concern. once you get recovery up and running you can flash a working ROM

You still can't enter recovery? And where did you download the FW? If you still can't get into recovery I suggest fasboot flashing a 4EXT recovery with the following command in bootloader:

fastboot flash recovery recovery.img
[HTC Sensation] rzr86:
you mean fastboot flash recovery recovery.img :)
[HTC Sensation] onemanshow85:
yes, you're totally right. thanks for the notification. corrected it.
[HTC Sensation] Zatorra:
I have installed 4ext in every possible way and installation is OK, but still cant enter recovery.
[HTC Sensation] Zatorra:
by the way, it doesnt say "quietly brilliant" under HTC, just logo. In case it helps.
[HTC Sensation] onemanshow85:
the HTC screen is the boot screen, the 'quietly brilliant' screen is the splash screen. And it seems your ROM just won't boot and like said, it's mostly caused by imcompatible ROM/FW combination.

but are you still unable to enter recovery?
[Sony Xperia ZL] unmaskedfalesh:
:confused: i saw that xperia Z had the speed dialing option on dialer on.307 firmware and heard that it will be available for ZL also but i dont have the option on my ZL even after updating to JB 4.2.2 stock. Please anyone clear on this matter...if anyone has that option please let me know.
[Sony Xperia ZL] Lonzo_SGS2_506:
No man there is no speed dial on this update. I guess this is related to region... I've never had it at all. But you can have it on the small app of the dialer. And you can try also EX DIALER from Google Play bro...

Sent from my ZL monst@
[Sony Xperia ZL] sarobi:
I have speed dial option - ZL 6503 (german version)
[Sony Xperia ZL] unmaskedfalesh:
you are lucky mate my ZL 6502 India Variant dont have it...
[Sony Xperia ZL] stinky73:
I have speed dial on .253 firmware, android 4.1.2, C6503 model - cannot say for 4.2.2 as I'm not letting it anywhere near my currently fully functioning zl as I have never had it (4.2.2) work properly on any device :(
[Sony Xperia ZL] sarobi:
Only my opinion, if you stay on stock firmware there is nothing wrong with 4.2.2. My XZL 6503 works just the same as with 4.1.2, no problems and bugs at all. Everything that worked in 4.1.2 works also in 4.2.2.

But it is really interesting that ZL 6502 Indian doesn't have speed dial option. I thought only differences between 6502/6503/6506 are different network frequencies/bands:confused: