yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] idexample:
I don't have this phone, I even never tried on my Galaxy S1 but I suggest this idea that may works:

I founded in Chinese online stores a USB otg (on the go) that let you connect to the phone USB whatever and often they have a micro SD card reader inside that may let you copy or directly use your zip file to flash back your desired rom.

Wish you luck and if works, let me know.
[Moto G Q&A, Help & Troubleshooting] kolega28:
Thank you sooo much, you saved my life, I literally just got my moto g today so if it got bricked that would suck, thanks!

Thread may be locked.
[Galaxy Ace II Q&A, Help & Troubleshooting] ockhamsrazor:
I'm interested in removing the network lock from my SGA2 GT-I8610 (Samsung codename "Codina"), and while I'm a total noob regarding Android development, I do have some clue about coding and tried a bit of Googling and searching these forums here.

First of all, two useful threads as linked from this post (which was erroneously posted in a similar thread about unlocking the Ace II X GT-S7560M):

Good starting point: Backing up NV data

Partition table

My personal findings:

My serial number -- without the trailing X -- is found 4 times in cspsa.bin, as produced by following the instructions found in the first Backing up NV data post.

I stumbled across this -- especially the parameters on line 59 -- and wondered if this was any helpful. Curiously, I haven't been able to find that very same file in GitHub repos (most are forks of https://github.com/dh-harald/android_kernel_samsung_codina) based on Samsung's open source released i8610 "Codina" kernel.

There is a mention of "pff2cspsa 0.0.2 Thu Apr 12 10:19:02 2012" in cspsa.bin. Googling "pff2cspsa" yields, among few other results, http://pastebin.com/ku0WHZ1B (posted only yesterday!), which seems to be some file related to the NovaThor U8500 chipset, upon which the Ace 2 is based. That file also seems to list a couple of other cspsa related tools, such as cspsalist etc. I wonder if those tools and/or their source code can be found somewhere.

Another good starting point might be investigating if SIM unlock techniques have been found for any other NovaThor U8500 SoC-based phones, e.g. the SGS3mini. I haven't done that thoroughly yet.

Few people have reported success unlocking their SGS3minis using the Service Mode menu, where they were able to disable a network lock option called "Perso SHA256", so maybe this means that the CSPSA is somehow SHA-256 hashed or encrypted.

Feel free to comment your thoughts and/or if any of this might be worth further investigation.

One thing I haven't really found through searching: are you guys using just a hex editor to analyze cspsa.bin or are there any better tools? (E.g. is it possible to mount that thing as a loopback device on Linux?)

(Sorry for posting this to the user section -- as this is my first post, I'm not yet allowed to post to the dev section.)
[Galaxy Ace II Q&A, Help & Troubleshooting] weblordpepe:
discovered aswell

I found your post when I did a keyword search for 'pff2cspsa'. I'm trying to goof with my RIL at the moment.

I've found it in my CSPSA partition.

There's also 'nwm2gdf' mentioned aswell which looks like a utility.

Googling that found me some XML dump of someones packages in what seems like a Gentoo distro. It looks like theres a package called 'cspsa-tools', because the 'cspsa-tools-debuginfo' package contains nwm2gdf.

That package looks interesting & i'm going to see if I can find it now.

This is also my first post. SIgned up just to reply :P

The SHA-256 clue is very interesting thanks I'm gonna investigate further.

---------- Post added at 07:45 AM ---------- Previous post was at 07:11 AM ----------

Okay I've found some info:

Turns out Ericsson (ie the company that once joined up with Sony to be SonyEricsson) once upon a time released packages to manage CSPSA things. They make the chipset that the galaxy s2/3 is built on (one of them anyway).

Now because I'm a new user I can't post external links. The captcha is F---ing me off so I'm going to obfuscate the link below:

http colon slash slash download.meego.com/live/home:/imppa/Trunk/i586/

Download all the files which mention CSPSA (theres a few down below, libcspsa ones so page down).

Also, they are rpm. If you are using a debian based system, use the 'alien' tool to convert to .deb packages with the -d switch.

Also, roll 32-bit ONLY. Forget about it if you're running 64-bit linux.

There's a bunch of handy tools there. I'm yet to goof with them but we'll see how we go.

edit: doesn't seem to work. All I'm getting is 'ERROR: CSPSA area could not be opened. Binary file not valid' when I try em on the image files I made of my CSPSA partitions.

---------- Post added at 08:08 AM ---------- Previous post was at 07:45 AM ----------

Okay what you need to do is figure out which partition is your CSPSA partition. lets say its mmcblk009.

Install all those CSPA packages

check /etc/cspsa.conf. it will point to a file under /dev. copy your binary partition into /dev and edit the file to match the filename of your partition image.

then run: cspsa-server. It will say something like 'CSPSA0 started'.

then type cspa-cmd and you'll get a prompt

type 'help' to see stuff. but you'll want to type 'open CSPSA0'

then you can type 'ls' to see the key/value pairs for things stored in your CSPSA image file.
[Galaxy Ace II Q&A, Help & Troubleshooting] ockhamsrazor:
Bought an unlock today

I bought a network unlock today, did another NV backup, and compared the before and after states of cspsa.bin.

Some of it has changed; but around the first occurrence of the serial number, the file is surprisingly almost identical to its previous state. Now what has changed is the range from offset 0x457 (after "FF 24 00") to (excluding) 0x477. I'll take a closer look soon if anything else looks suspicious, but this might be our SIM lock...
[Galaxy Ace II Q&A, Help & Troubleshooting] ockhamsrazor:
A couple of short notes

A couple of short notes on the CSPSA tools you found:

There are not only binary RPMs, but also two RPM source packages from which they're built (which contain a spec file and an upstream tarball) -- they're at download.meego.com/live/home:/imppa/Trunk/src/ . I successfully built the upstream sources on Ubuntu 13.10 (amd64), but I had to remove the -Werror parameter from the Makefiles first. I didn't have to install any of those tools to my system (i.e. no sudo required), but I have to admit that I haven't yet built the binaries from cspsa-tools that require cspsa.h.

You don't need to copy cspsa.bin to /dev -- you can specify its location in cspsa.conf

You don't need to move cspsa.conf to /etc -- you can specify its location as a parameter to cspsa-server

The readme files provided with the sources also provide some information on the tools.

A bit of a glossary:

CSPSA -- crash safe parameter storage area

NWM -- Nokia Wireless Modem; cspsa-tools' readme.txt says

PFF -- Parameter File Format; cspsa-tools' pff_readme.txt says

GDF -- ?

The packages contain various tools to convert between those formats.

As you noted, cspa-cmd can be used to list the CSPSA's contents, and to store them to individual files, as well as exporting to a gdf file. That file can then be viewed by gdflist. That latter tool reveals that apparently my CSPSA's contents were created by nwm2gdf, and that apparently most its contents are supposed to be copied to /modem/RFHAL -- I wonder if that's really the sole purpose of the CSPSA, and if (on a functional phone) everything is also identically contained in that /modemfs/RFHAL. I'll need to do a diff of that file and that (possibly) corresponding record showing up in the gdflist output.

One more (near-trivial) note: the part of CSPSA that I had noticed in a hex editor to have changed after network unlocking is 0x477-0x457=0x20=32 bytes long. So that *could* be a SHA-256, as that would be 256 bits = 32 bytes long.
[Galaxy Ace II Q&A, Help & Troubleshooting] rockeetman:
Hey, you must have done a mistake in last calculations. Actually, 32 bytes is 32 x 8 = 256 bits.

Wysłane z mojego GT-I8160 przy użyciu Tapatalka
[Galaxy Ace II Q&A, Help & Troubleshooting] ЯazoR:
This might be a mega necro, but is anyone by any chance even remotely interested in unlocking a phone this ancient?

I happened to have one at home which I use now as a replacement since I broke the touchscreen of my original device. In some of my free time I peeked around a bit, and managed to properly export the CSPSA entries. Sadly all this just results in a more human readable representation of hex values stored in the CSPSA, which means that without actually knowing what was stored there one must try a different approach :(
[General Topics] cr1t1c4l:
I love my palm desktop software. I hate to use Outlook. Is there any way to sync PPC to Palm Desktop?

Specifically I'm using the Cingular 8125 aka HTC Wizard with WM5 (...and posted same question in the Wizard Forum).

Thanks for any help.
[Galaxy S II Q&A, Help & Troubleshooting] FPSUsername:
I have a dual boot now, but I can't use my phone at the moment.

Does each rom has an own data path for apps you installed?

Like, I got real racing 3 (about 2GB) on rom 1.

If I install it on Rom 2 also, will it also download 2GB and store that data on a different place? Or will it use the same place and only install the apk?

Same for whatsapp, can I use whatsapp on both roms with only 1 phone number?

(like 1 account).

If it uses an other path, is there a trick to let rom 2 use the app data path from rom 1?
[Galaxy S II Q&A, Help & Troubleshooting] Paul_Kolanjian:
in case you already downloaded the required files to run Real Racing 3, all you need to do on your 2nd ROM is to just install the .apk file of the game. As for WhatsApp, I don't think you can use one phone number since i once tried it and I got some weird error saying an account with same phone number already exists, but it will probably work on 2 ROMs since maybe the issue was on my side only. I recommend you try and install the app to see whether it might give you a problem or not, but it should work on 2 ROMs with the same account.
[Galaxy S II Q&A, Help & Troubleshooting] pargas:
Backup your working whatsapp with titanium bu. on the other rom, dl whatsapp from play and restore just data with tb. Works for me.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] androidrocks23:
Sorry for asking silly questions but i don't know anything about gravitybox !!!

And how can i install it on my galaxy y(GT-S5360)???

Is it safe to install or i should stay with my busybox???

Thanks in advance for all user who are willing to help me:thumbup:

Sorry for my bad english :(
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] TheFixItMan:
google is your frien - you could of just typed gravity box in google!!

anyway

http://xdaforums.com/showthread.php?t=2316070

and no you cant use it in galaxy y 5360
[One (M7) Q&A, Help & Troubleshooting] jeffers95:
hello I recently tried to install arhd rom it finished then I went to boot it and it just turned off then rebooted to recovery so there is no os installed and anytime i try to adb push files seems to take hours and running the ruu it just gets stuck on sending any help would be appreciated thanks
[One (M7) Q&A, Help & Troubleshooting] mb_guy:
Please post your fastboot getvar all and recovery version currently installed
[One (M7) Q&A, Help & Troubleshooting] jeffers95:
(bootloader) version: 0.5

(bootloader) version-bootloader: 1.43.0000

(bootloader) version-baseband: 4A.21.3263.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.401.12

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3856mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too m

finished. total time: 0.670s

and twrp 2.6.33
[One (M7) Q&A, Help & Troubleshooting] mb_guy:
Have you tried usb OTG? Which arhd rom?
[One (M7) Q&A, Help & Troubleshooting] jeffers95:
I don't know how to use usb otg and it was Please post your 52.0
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
What custom recovery and what version of it do you have?

What rom and what version did you install?
[One (M7) Q&A, Help & Troubleshooting] jeffers95:
i was using twrp 2.6.3.3

and arhd 52.0 4.19.401.9 (WWE)

how do i go about returning it to stock
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
If the issues you listed in the first post are true, then you are toast.

However, I hope you were exaggerating only.

So, you need to either use a RUU or ADB Push/Sideload.

You said you installed ARHD 52, but now you have no OS.. That doesn't add up.

Can you still ADB PUSH?
[One (M7) Q&A, Help & Troubleshooting] jeffers95:
can still do it but it takes hours and when ever i try to install anything says cant load and i wiped the whole phone trying to run the ruu
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Change the computer, or USB port, or USB cable. Thats NOT normal. Or your phone is on the last legs.
[General Questions and Answers] ferdyvw12:
Hi,

I am quite new to this but have done everything i can to solve this problem. I have a HTC One S (s4 version).

- i have unlocked my HTC via HTC dev.

- i have installed Clockworkmod recovery.

- i have sent a Cyanogen 11 zip file via ADB push command.

- i tried to install the rom but i had status 7 error, didnt work.

- i flashed TWRP2 recovery instead of Clockworkmod, via fastboot on my pc.

And now; i reboot to TWRP recovery, ADB push my Rom again to /sdcard/, this works. I go to install, i can select the zip file, it asks me wether i'm sure i want to install it, i proceed and then get the error "E: Unable to mount '/internal_sd' " "E: unable to mount stoarage".

So i have root acces, ADB works. Fastboot works. But installing a rom doesn't work with either Clockwork or TWRP2.

Versions used are TWRP 2.7.0.0 and Cyanogenmod 11, a snapshot version.

How to solve this?

Thanks
[General Questions and Answers] Trozzul:
if your device has a forum for itself please use the Q&A there, you would get better help from professionals that own your device, there's lots of devices on xda and its possible this problem only exists on your device. if you ask these questions on the general Q&A you will most likely get answers from people who didnt read your OP and will give you something stupid. http://xdaforums.com/htc-one-s/help hope you fix your problem!:D
[Galaxy S III Mini Original Android Development] New Macław:
Hello!

This is development thread of TWRP Recovery v2.8.0.0 by NovaFusion.

Credits:

marcin1147

Macław

Huge thanks to TWRP team.

You can get it from http://novafusion.pl/.

Download is directly provided from our servers - it's fast, stable and fully resumable!

If you appreciate our work, please, use thanks button!

XDA:DevDB Information

TWRP v2.8.0.0, Kernel for the Samsung Galaxy S III Mini

Contributors

New Macław, marcin1147

Kernel Special Features: Only one recovery with full KitKat support!

Version Information

Status: Stable

Current Stable Version: 20140911

Stable Release Date: 2014-09-11

Created 2014-03-11

Last Updated 2014-09-11
[Galaxy S III Mini Original Android Development] New Macław:
Changelog

20140911 (v2.8.0.0)

Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy

Add command line capabilities – you can now execute various TWRP features via adb instead of the touchscreen

Add support for color in the console and give error, warning, and highlight lines different colors

Track backup and restore progress based on file sizes to provide a much more accurate indication of progress

Improve handling of /misc thanks to mdmower

Improve setting of time on Qualcomm devices thanks to [NUT]

Allow using images on slidervalue GUI objects thanks to Tassadar

Allow using variables and addition and subtraction in variables for easier theming

Add support for 1440×2560, 280×280, and 320×320 resolutions and update 240×240

Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain

Other minor fixes and improvements

What's new in 2.7.1.1 from 20140720?

upstream changes in TWRP

updated kernel

device updates

What new in 2.7.1.0 from 20140612?

full f2fs support for S3 Mini!

What's new in 2.7.1.0?

Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don’t have it in TWRP, please contact me via PM to arrange for it to be added.

Various bugfixes to backup and restore

Improvements to USB storage handling

Added a class to search for files to make finding the correct brightness file automatic in most cases

Various other bugfixes and tweaks

What's new in 2.7.0.0?

Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar

Allow sideloading from /tmp on encrypted devices

Check for a crypto footer before asking for a password to prevent user confusion

Additional checks for validity to auto generated backup names

Text wrap in the console output

Proper caps lock support in the keyboard

Mouse support via USB OTG for devices with a broken digitizer

Improve scanning of storage locations for OpenRecoveryScript

Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions

Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)

Update SuperSU to 1.93 and improve installation process

Added selinux contexts restoration to fix permissions

Load RTC offset on Qualcomm devices to fix the date/time in recovery

USB Mass Storage fixes Add SELinux support checking

Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)

Add 4.4 decrypt support

Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)

Various SELinux fixes and bug fixes
[Galaxy S III Mini Original Android Development] New Macław:
Downloads

All releases are available for download from:

http://novafusion.pl

Download is directly provided from our servers - it's fast, stable and fully resumable!

Sources: http://github.com/NovaFusion
[Galaxy S III Mini Original Android Development] oldmen:
Thanks
[Galaxy S III Mini Original Android Development] HirogenX:
:thumbup::D:thumbup::D:thumbup::D

Great, Thanks!
[Galaxy S III Mini Original Android Development] mauam:
Awesome work. Thanks a lot Mac & Marcin, you guys rock:cool::good:
[Galaxy S III Mini Original Android Development] calvooo:
Does it work properly? Because some people cant acess to SDcard.. or its just another user fail? :)
[Galaxy S III Mini Original Android Development] New Macław:
Will check right now ;) Of course if it's true, we will fix it as soon as possible.
[Galaxy S III Mini Original Android Development] mauam:
Just make a backup (stored on the sd card) & works flawless, so...;):cool::good:
[Galaxy S III Mini Original Android Development] +BOB+:
TWRP Backup and restore from and to sdcard works. Also apps like helium works with my 32gb sdcard.
[Galaxy S III Mini Original Android Development] New Macław:
Also ok for me. Thanks for fast reply guys!
[Galaxy S III Mini Original Android Development] calvooo:
Ok, i flash recovery and works fine. What about SElinux, is still disabled?
[Galaxy S III Mini Original Android Development] HirogenX:
Backup to and restore from extSd is working without any issue for me. Good work!

Btw : I like the Panda in recovery :thumbup::D
[Galaxy S III Mini Original Android Development] giociampa:
Silly question maybe...

Why use this one when the official TWRP (now at 2.7.0.1) is available? Is there a subtle difference that means this works when theirs doesn't?

(Edt: having asked the dumb question - I discover that the "official" download appears to be a 10 KB empty tar file! *laughs*)
[Galaxy S III Mini Original Android Development] mauam:
TWRP team doesn't support s3 mini anymore, so, Marcin made his magic, just for us;)
[Galaxy S III Mini Original Android Development] giociampa:
So I've just discovered (see edit above)
[Galaxy S III Mini Original Android Development] HirogenX:
Are you sure?

http://teamw.in/project/twrp2

Not even for the N7² it has a newer version.
[Galaxy S III Mini Original Android Development] mahdik.m:
Hi. i flashed previous version from cwm so i have twrp . for update flash new version with twrp or odin ?
[Galaxy S III Mini Original Android Development] Axaion:
Thanks.
[Galaxy S III Mini Original Android Development] piskor:
With TWRP
[Transformer TF300T Q&A, Help & Troubleshooting] ganggreen777:
My question is this....I have some notions based on having a 64g micro SanDisk. I wanted to get smart people's feedback lol.

I am rooted .(obviously)..pretty much use philz recovery for note2 and twrp for tf300. I have used others (recoveries). They all do not "read" the sd card. I had to format my 64 to a fat32. I know there is limitations to that but what else is there to do. And that is why I ask you smart people ....Perhaps you have a better insight than I....

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FuTuRisTiC Zo3:
I need help recovering my GS3, i tried using CF auto root to root my phone and i guess it didnt work because my phone doesnt boot past the samsung screen. I didnt have any custom recovery installed so i dont believe and thing was backed up. I am able to get into download mode and recovery mode. I tried flashing stock firmware using kies but it encounters a error saying its a problem with my phone, I tried using odin but it also gives me an error when flashing firmware saying

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> aboot.mbn

<ID:0/003> NAND Write Start!!

<ID:0/003> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1

What do I do to fix my phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FuTuRisTiC Zo3:
Ok I Installed Insecure Boot img via odin3 and my phone rebooted but now instead of it booting at the 1 second samsung screen it goes past it to the galaxy s 3 screen and just sits there. i also installed twrp, it let me mount everything but i cant u adb to push anything and it says i have no os installed. i dont know what moves to make anymore someone please help me out!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
What version of Android did you have on your phone when it last worked, stock or custom ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FuTuRisTiC Zo3:
its was a stock android rom i believe im not sure what version though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lemngo02:
Are you still able to get it into download mode?

Press and hold volume down + home + power at the same time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FuTuRisTiC Zo3:
yes im able to go into download and recovery mode
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lemngo02:
oops didnt fully read your 1st post :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FuTuRisTiC Zo3:
thats koo but the problem is i dont think my phone is rooted, i cant adb push using twrp cause my device wont show up when i adb devices