yashsingh1/xdaforums huggingface dataset:
[Sony Tablet S] pajn:
Okey new test.

Sorry for not responding earlier, I have been busy IRL.

Seems like my Busybox build where stupid. Have corrected

some config problems but did also have to rename the binary.

I'm a bit tiered now so something may still point to the old one.

If it does work, be careful and make sure to do all checks I wrote

here http://xdaforums.com/showpost.php?p=43228217&postcount=15

to make sure it isn't touching your stock system when it shouldn't.

We can't boot another kernel with this (this is the only limitation however). For that we need the last bit working: kexec and that is much harder work than this.

However CM should probably be able to boot on our current kernel if I get time I will try to make it work on the XTS however that is unknown ground for me so yeah... If someone knows more about this stuff that would be real good. Also someone with an STS would need to fix that device. But when both devices have been fixed I guess most development should be doable on both.

Yes, if you are only using the rom-slots your stock system should be good (however this is still beta, bad things may happen even if everything I publish on the Play store have been tested)
[Sony Tablet S] smgdev:
Oops, Am I doing wrong something?
[Sony Tablet S] stifilz:
+1 Same result :(
[Sony Tablet S] pajn:
No, I did, as usual...

I really need to create a checklist for what to do when releasing a version.

Hope you haven’t got completely tiered of me yet.
[Sony Tablet S] smgdev:
1st try - Bootloop

2nd try - Stuck at black screen
[Sony Tablet S] pajn:
For this stage you'll have to use adb shell and not an in Android terminal as the killall script will kill the android framework, surface flinger, dalvik and other stuff needed to run a terminal app.
[Sony Tablet S] smgdev:
I just tried it and it stuck at black screen. Sometimes stuck at boot animation. Animation freezes.
[Sony Tablet S] pajn:
I find it a bit strang that you end up in a boot animation. Didn't thought that would be possible.

However I looked through the source and found one thing that might stop it from booting

so a new try :)
[Sony Tablet S] CoolApps:
Nothing?
[Sony Tablet S] smgdev:
Sorry but didn't work. This time i don't know the problem but i will try again and report it.
[Sony Tablet S] CoolApps:
What files does this modify/add/replace/remove?

---------- Post added at 11:30 AM ---------- Previous post was at 11:14 AM ----------

Well I can see why, it modifies the system partition so while it executes the first init it will hit that boot and lead it to the recovery but because there is no where for the init to lead it to since the information is invalid it becomes null so it is just going to loop and then freeze has it has timed out.
[Sony Tablet S] smgdev:
[MENTION=1958616]pajn[/MENTION], are you there? lol
[Sony Tablet S] pajn:
Sorry, I read the email on the phone but hadn't time to answer. Forgot to answer when I came home.

>What files does this modify/add/replace/remove?

On the STS:

Add: /system/bin/reboot-recovery This is the script that unpacks the temporary files for booting recovery (overwriting you current rootfs)

and also kills everything and tells 2nd-init to "boot".

Add: /system/etc/bms and everything in it This are files needed, example is 2nd-init, recovery, busybox and such.

Nothing is modified/replaced or removed. (On the XTS logwrapper is replaced for hijacking).

Do you get bootloop on normal boots or just when running reboot-recovery?

Normal boots shouldn't be affected as everything it overwrites to boot to recovery is on a write-protected storage and is therefore gone on a true reboot.

reboot-recovery shouldn't be affected as the init.rc is overwritten to boot the recovery instead of boot Android. Thus it shall never launch the boot-animation.

Well this is the idea anyway. Something obviously goes wrong.

Can someone post the output of

ls -al /

as root?
[Sony Tablet S] smgdev:
Here you are.
[Sony Tablet S] rohit choudhary:
So much long will it take to hijack the bootloader or to get jb custom Rom for tablet s
[Sony Tablet S] smgdev:
Maybe but I think we are gonna make soon.
[Sony Tablet S] Ziain:
Is this really looking like a possibility then?
[Sony Tablet S] smgdev:
Yep.
[Sony Tablet S] pajn:
This surly is possible, however it's very hard for me when I don't have any device to test with.

If someone have reasonable knowledge about Linux and Android I would be very happy to

cooperate because right now it starts to feel too hard to do this my self. And not having

both devices on would be very sad as our community already is quite small.
[Sony Tablet S] dmt-300:
I can be that guy :D:thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:

HOX+Viperx+Alex(V) = ^o^
[Sony Tablet S] smgdev:
I don't know so much about linux but i can help as much as i can.
[Sony Tablet S] dmt-300:
The silence before the storm :mad:

HOX+Viperx+Alex-V=^o^
[Sony Tablet S] smgdev:
Yeah :D, [MENTION=1958616]pajn[/MENTION] where are you man, something wrong with reboot-recovery script.:o
[Sony Tablet S] Fallon9111:
Linux Android

Hey, I'm very confident using linux (two years of use with no ms windows), I have a fair knowledge of bash/sh programming. I also do a few other coding languages :) (I have very limited experience at writing android apps and programming java though :( )

I just found this thread today, to the best of my knowledge, we have no source code for the xperia tablet s, so cannot build ROM's? I have compiled CM/PA/AOSP/AOKP before, but have never ported for a devices which don't already have a working build for the version of android compiled with.

If there is anything you would like help with, I would be happy to help. Nice to see the posibility of custom ROMs on the XTS!

If somehow someone manages to create a source for AOSP XTS rom, I would be happy to maintain a Pa/CM/AOSP or other ROM :laugh:

Edit: Also, I would love to maintain and/or port an Ubuntu Touch rom if someone is able to get a CM10.1 / AOSP 4.2 working!
[Sony Tablet S] Cat McGowan:
Sony Global - Source Code Distribution Service
[Sony Tablet S] CoolApps:
The problem is that when you use such reboot commands the bootloader will only reboot and that's it.
[Sony Tablet S] smgdev:
It practicaly doesn't reboot, it just stops system processes and starts the custom recovery.
[Sony Tablet S] CoolApps:
True but if you do reboot recovery ADB or not the device will not go into it and will just enter the system without giving input to the bootloader.
[Sony Tablet S] databoy2k:
For what it's worth, I use a modified build.prop on my tab S to hide the debug icon. If I reboot using a system superuser command (like the one in Power Toggles), the modified build.prop file is ignored. The only time that it is read is when powering off with the switch and rebooting.

Could this be a STS related behavior leading to the above problem?
[Sony Tablet S] pajn:
I post the cm 10.1 devices I have created for this.

These are not usable right now for CM but may be a good start.

I'm not integrated in the whole CM thing but just contact me

if there is anything, I may be able to answer.

I will also try to be more active on these forums again.
[Sony Tablet S] smgdev:
Glad you back pajn. As I said, reboot-recovery script is throwing errors (Will post later.). And thanks for device trees. And I think we should get kexec working for custom kernels.(Hashcode said it is can be tricky.) Have you got knowledge for getting kexec working?

Thanks sir ;)
[Sony Tablet S] Fallon9111:
I'm very busy ATM, but I'll see what I can do when I have a bit less work, thanks :D
[Sony Tablet S] pajn:
Yeah, having kexec working would be a dream.

With kexec there are nothing that we cant do that a "open" device can.

The only minor problem is that boot time increases a bit as it needs to

load stock kernel and a bit of stock Android first, but how often do you

reboot?

Unfortunately I don't have any experience with porting kexec, I were

planning on trying to do that when BMS got working but then things

changed and time disappeared :/

[MENTION=4716681]Fallon9111[/MENTION]

Great! Just take your time.
[Sony Tablet S] smgdev:
[MENTION=1958616]pajn[/MENTION], can you describe how should rebooting to recovery work? I can contribute to this project as I can ;)
[Sony Tablet S] pajn:
The first thing that needs to be understood and mad work is 2nd-init.

2nd-init is a very complex thing and I redirect to the explanation at

http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works

So what this basically means is that by running 2nd-init we can do a

new start-up. But before we do a new start-up we need to make sure that

the it now starts up whatever we want to start up.

This is (in reboot-recovery) done by extracting recovery.zip which holds

the ramdisk for the recovery. After that we need to kill everything (in a

reboot you first need to shut down) this is (in reboot-recovery) done by

hijack.killall

After that the last three lines in reboot-recovery loads 2nd-init which

basically just makes the kernel start up the system again.

Do you get what is basically happens up to this point?
[Sony Tablet S] psxpetey:
Looks like good progress is being made
[Sony Tablet S] Dillenger:
would it be possible to install CM 10 or a kitkat rom using something like this?

http://www.xda-developers.com/android/locked-bootloader-xperia-s-and-want-cm10-no-problem/

This was just recently posted and I am hoping that someone with more expertise will be able to bring new life to our tablets using a method like this. Please let us know when you can. It seems like using this method we would not have to bypass or unlock the bootloader. This seems very hopeful to me. I wanted to let you all know, incase it was missed or overlooked by those with the proper expertise.

Best regards

Dillenger
[Sony Tablet S] CoolApps:
Nice find, would be really interesting to look at...
[Sony Tablet S] wan5xp:
http://xdaforums.com/showthread.php?p=09

It is about kexec on Z1. And he also said this tool maybe can be used on any xperia. I think it is currently work in progress
[Sony Tablet S] dmt-300:
I can't promise anything guys, but I'm working on it. I have a spare tap :D
[Sony Tablet S] CoolApps:
Spare tap? Lol
[Sony Tablet S] Casey Walt:
did anybody find anything out? right now I am working on backing up my device then tweaking the back up to see what i can do...
[Motorola Droid RAZR] RedJack117:
hey guys im having a problem with my Razr...I tried installing CWM and when i booted the phone back up it said Encryption Unsuccessful...I hit factory reset then it tries to reset my phone but then fails and it gives me the option to reset again...any way I can fix this?
[Motorola Droid RAZR] anurag.dj2u:
Yeah resetting phone again and again cant unbrick ya phone . We get this error when we try to flash any mod or .zip from cwm and that zip ain't compatible for our RAZR and stuck on this ****.

So the solution is ya need to flash fastboot

Please hit the thanks :thumbup: if i ever helped ya !! :D:D

---------- Post added at 07:09 AM ---------- Previous post was at 07:06 AM ----------

And so many thread related to this problem tripping over xda . No need to make another thread sir :D:D:D

Read this i hope this would work for ya

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

Please hit the thanks :thumbup: if i ever helped ya !! :D:D
[LG Optimus G (International)] Miniricho:
Yep. Me again I know.

But with a bigger problem , recently I flashed the beanstalk ROM, and everything went swimmingly. Until I realise that my SD card had been erased. Photos, music everything!

Way to get it back without restore? :(

Edit: it says they're in a folder called 'shell' but I can't access it through gallery or music player !

Edit: I restored stock backup because I couldn't be bothered moving stuff around.

Moderator please delete.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
This is a story from my friend - he does not speak english at all, so he totally killed his XDA III.

He tried to flash VPA III German from Vodafone to English language.

Here is Device Data.

PH20B2 B 2 GER R VODAP102 1.22.01 0 1 1.22.163 1.06.00 06.00

Then he downloaded Qtek WWE update and began to flash after preparing with following bat file.

xda3nbftool -x ms_.nbf ms_.nba 0x20040522

xda3nbftool -x nk.nbf nk.nba 0x20040521

xda3nbftool -x radio_.nbf radio_.nba 0x20040523

xda3nbftool -sd PH20B2 -sl GER -so VODAP102 ms_.nba

xda3nbftool -sd PH20B2 -sl GER -so VODAP102 nk.nba

xda3nbftool -sd PH20B2 -sl GER -so VODAP102 radio_.nba

xda3nbftool -c -u NK.nba

xda3nbftool -c -u ms_.nba

xda3nbftool -c -u Radio_.nba

xda3nbftool -x ms_.nba ms_.nbf 0x20040522

xda3nbftool -x nk.nba nk.nbf 0x20040521

xda3nbftool -x radio_.nba radio_.nbf 0x20040523

del *.nba

But the update hang on 10 percent of radio and did not continue. All his ideas to restart and continue had no success.

So he decided to delete radio file from update folder and restart the update process, because VPA simply hand in bootloader mode.

After update the device ran crazy, because he showed WWE version during the load but all error messages ran out in German.

Radio Worked!!! He tried to make a telephone call.

Then he decided to restart the whole update, but radio update began and stopped at 10 percent again.

So he flashed the device again without radio and then put in the folder a radio file from german T-Mob update. This time he flashed the device successfully, but during the load it shows NO GSM and D 1.22.00 WWE

Now we are in total sh... because GSM not working and still no effect in flashing.

The bootloader version is 2.07 and we only have working Qtek with 2.06 version, so SD backup will not help. Please help! Please!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
Can you get the Device data TXT

PH20B2 B 2 GER R VODAP102 1.22.01 0 1 1.22.163 1.06.00 06.00

From an original Russian phone.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
It was not original Russian Phone. It was VPA III form Vodaphone, but without Sim-lock
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
Then you have the info you should need.

Read :

http://wiki.xda-developers.com/index.php?pagename=BA_GettingStarted

Just REMEMBER to be aware that if you get any warnings in the DOS window When running the xda3nbftool you must delete that ROM and try on a new copy. Running the xda3nbftool twice on the same ROM can produce errors without warnings!!

When you understand the consept descriped on that page, move on to getting the newest rom avalible that also works with the xda3nbftool

http://wiki.xda-developers.com/index.php?pagename=BA_RomKitchen
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
Thinking about extended ROM is not very actual now. I'll try to read all materials on Wiki, but the problem is that during this updates device data could change and I can not get the new version of this file now.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
One of the headlines say "Based on I-Mate 1.22.162 WWE and I-Mate Arabic 1.31.112 WWE"

I werent thinking Ext. Rom. you have no need for that right now
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
I wanna say that I really appreciate your help.

Now I can describe situation in following points.

1. Device is after strange flashing of widely discussed Qtek ROM

2. I can't get devicedata.txt, because now I have strange mix of English and German langeages in system. (Something like German version with English interface - it is even hard to explain).

3. No GSM during booting.

I really have no ideas except trying to guess the combination of model, country code and operator.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
Do you have the DeviceData.txt from befor you starting messing with it?

Otherwise try looking looking at this page http://wiki.xda-developers.com/index.php?pagename=BA_Versions
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
Well, I have such file before all upgrades. It is listed in the first post. But now I have kind of WWE Rom installed (I think so, because it is showed in red during the boot).
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
Ok, so if you try to make a new DeviceData.txt, what does it say ?

I suppose this is the original deviceDate :

PH20B2 B 2 GER R VODAP102 1.22.01 0 1 1.22.163 1.06.00 06.00

Correct?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
I can not put GetDevicedata.exe to device, because I can not connect via ActiveSync, can not access File Explorer or Storage card because of this awful mix of languages. The only think I can do - launch applications from Today screen. They launch in German though.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
You really ****ed this one up. Well i can only hope that the device data on it is still the same.

Now i'm absolutly no expert on this ROM switching, just did it once for kicks, but hang on a sek. and ill try and look at the 131.Base version to se if we can get that installed on your device.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
In my humble opinion it was changed... I can suppose this, because fix.bat listed does not work now. And I can not even imagine the "radio" section of such file because of "NO GSM" presented.

p.s. Are there some "Flashers" devices in maintanance centers? Maybe they can help me... Of course it will not be easy to find such centers in Russia, so I hope that we can manage this situation at home.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
Im have uploadet a file you should be able to use.

Unpack and run the BaUpgradeUt.exe file.

If your device data hassent change in your friends desperate attempt to update it, it should work.

There is no Radio incluced cause i keep getting Password errors on all those i find.

You can try and run the the upgrade i made, edit and delete the files you dont need in the ext. rom after installation, hard reset it, and you should be running, without radio that is.

Now i dont have all that much time, but look through the wiki and find a radio you can flash onto it. Same procces as everything else, just without the nk and ms files.

ftp://xda:xda@xda-developers.com/emergency

As far as i know this is a WWE Rom, and all the Arabic customation is in the ext. rom.

Please note that you install this on your own request and risk, and that i take no responsobility on the outcoming result!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
Thank you so much in advance. I'll try to flash it today.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
I get the same country ID error.

No-No-45-45-N

It means that devicedata changed. But can yous guess the new data?

I think that new device ID shoud correspond to flashed ROM, because it was flashed twice. Maybe WWE language and BRIGH001 are the new country identificators. What about the model?

And I want to return to the idea of SD dump. Is it possible to do such trick?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
Well, I tride to decode this files to following combinations

PH20B WWE BRIGH001 and PH20B2 WWE BRIGH001

Only country ID error
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
Tried all the combination of identificators

PH20B and PH20B2

VODAP102 and BRIGH001

WWE and GER

country id all the way.

I am beginning to loose my last hope. I feel even pain to look at it. It is alive, bootloader is alive and no way to save it...
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
It sounds like the first atempt succesfully wiped the DeviceData, and the second attempt wrote new DeviceData.

I heard someone in here have a similar senario, he just succeded installing the faulty DeviceData ROM.

Well first pull of the battery and look at at the silver sticker, in the upper left corner is the device Model/Number PH...... check that number against the number you gave me as the original number.

Which ROM was it he tried to install, The excact name as it's found on the ftp server.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
Oh, and do remember to only use the xda3nbftool.exe once on the same ROM. If it dont work, erase that ROM and try on a new copy!!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] HDuser:
Boy we are having fun.

Ok I feel you need to first clean you device.

Remove battery and push the slide of the battery cover back into the locked postion. Keep it that way for about an hour to insure that the back up battery is dead.

Now I have know idea what the SHIPPED DEVICE DATA was.

Was it?

PH20B2 B 2 GER R VODAP102 1.22.01 0 1 1.22.163 1.06.00 06.00

The owner should know what Language the phone was shiiped in, That was what he read when he turned it on. The Model number is at the back. The only problem is the SHIIPED Carrier info.

The country code error is from the language code. WWE is english but so is ENG, try that.

On all these you need to use the I-mate from Wiki getting started, this is the only one that we all know it works with as well as that update tool. Any other rom could give you encription errors that we the reader are unaware of.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
Hmmmmm i succesfully flashed my device with that rom, just without the Radio, for that i used the lates update from Dangaard Norway, the complete one, just erased the ms and nk files.

Whent like a charm 8)

Deleted it again though, wanted to read some more about the stability on it first. Was just bored, so what else to do than try to make a brick :lol:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] HDuser:
Well for you its fine the 167 as you are doing a same carrier upgrade and thus don't need to fix it. (based on your sig that is)

Rest of us well we are stuck untill the new tool comes out.

Its going to be realy cool, as you can extract from any ndf, might even be able to get player 10 out of the siemens rom, (if its true that it is in there).
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
Guys, thank you for not forgetting me. I'll give you some comments about the situation.

1. Hm. It is written PH20B on the sticker.

2. Always using xda3nbftool on fresh ROM.

3. PH20B2 B 2 GER R VODAP102 1.22.01 0 1 1.22.163 1.06.00 06.00 - this is original data before all this upgrading.

4. I can try decoding ROM provided in Emergency to ENG language, but original language was GER and flashed ROM was WWE (ENG will be too strange, but who knows).

5. For flashing he used http://www.qtek.nu/files/BA_WWE_BP_12200_126_10600.zip

this update.

6. Now I am killing backup battery... Waiting for your comments. You are my only hope. Thanks.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] HDuser:
Well that does explain a lot of things.

The 126 has not been tested with the tools that I know of so thus I dont know if it works or if it comes up with an error.

He needs to use the 162 and follow the explanation in wiki, the format of the fix bat looks correct based on your 1 post.

http://www.clubimate.com/Support/PDA2k_WWE_12200_162_10600_SHIP.exe
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] commentator:
Well, disconnecting of battery gave no result - I'll give it second chance - I have no time now for new attemps. Maybe some hours later. I also have to download this imate ROM and try to flash again. The problem is in new device data. The first fix.bat was good for original device, but now I am sure that all identificators changed someway.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] HDuser:
The way I read you is that you are STILL using the qtek rom. Just Don't.

Your fix bat gave you an error on the orriginal install, somebody ignored it or did not see it, that is why you are were you are today, and we still are trying to help you even though you have been told what you needed to do on *Sun Mar 06, 2005 19:27*.

Last time from me anyway, use the imate, follow the instructions in wiki or just keep a brick.