I suspect your mom will blister your butt for borking her tablet.
S.onyTablet.S v3.0 [FLASHER] - Tab S/P/Xperia fws! new: Xperia Tab JB 4.1.1 !!!!!!!
- Thread starter condi
- Start date
-
- Tags
- development thank you
@condi: Can this tool fix soft-bricked device ?
My tablet can't boot anymore, can go to recovery but can't mount anything.
I tried adb shell but it didn't regconize.
Do you know the way to fix that ?
Sony Service Center told to me that the problem is belong to mainboard.
But this happened because I tried to use restore to factory setting function in recovery.
My tablet can't boot anymore, can go to recovery but can't mount anything.
I tried adb shell but it didn't regconize.
Do you know the way to fix that ?
Sony Service Center told to me that the problem is belong to mainboard.
But this happened because I tried to use restore to factory setting function in recovery.
Out of warranty I assume?? My was sticking on the the boot animation after messing with it. Could get recovery but after not thinking about it I did a factory reset and lost usb debugging, therefore lost the ability to adb push and adb shell. So the only way to fix it was SONY.
Stifilz
Hello guys!
First of all, great stuff here, both AutoFlasher and AiO tool. Im completely new owner of Tablet S WiFi version, but old modder so i pretty much know what im doing.
Now, as i said, im Tab S WiFi owner and did AutoFlasher update from r1a to r5a. AutoFlasher naturally downloaded both Rom and "hidden.img" and process was undergoing well. I choosed to flash "last possible rootable hidden.img" (forgot correct number).
Everything was done well, i got my root, SD mount, permissions, everything.. except rom that was downloaded by AutoFlasher was for WiFi/3G version of Tab S, but i have just WiFi version.
Did i do anything wrong? I only choosed to update hidden.img to last possible rootable, everything else is done auto, so where did i do error?
Is there any way to fix this without reflashing it, or do i need to do it manually by creating custom firmware via AiO?
My current sys info:
First of all, great stuff here, both AutoFlasher and AiO tool. Im completely new owner of Tablet S WiFi version, but old modder so i pretty much know what im doing.
Now, as i said, im Tab S WiFi owner and did AutoFlasher update from r1a to r5a. AutoFlasher naturally downloaded both Rom and "hidden.img" and process was undergoing well. I choosed to flash "last possible rootable hidden.img" (forgot correct number).
Everything was done well, i got my root, SD mount, permissions, everything.. except rom that was downloaded by AutoFlasher was for WiFi/3G version of Tab S, but i have just WiFi version.
Did i do anything wrong? I only choosed to update hidden.img to last possible rootable, everything else is done auto, so where did i do error?
Is there any way to fix this without reflashing it, or do i need to do it manually by creating custom firmware via AiO?
My current sys info:
Code:
Model Number - GT - p7500 (done Galaxy TAB hax) (original is Sony Tablet S)
Android Version - 4.0.3 (release5a)
Baseband Version - unknown (naturally, since its not 3G)
Kernel version - 2.6.39.4 [email protected]#1
Build number - TISU0163410
Heh, it didn't break anything though. More like, nothing changed at all.I suspect your mom will blister your butt for borking her tablet.
No, you did not do anything wrong. Condi's S.onyTablet.S [FLASHER] v1.0 and v1.1 use firmware images based on 4.0.3r5a Poland WiFi+3G. Having WiFi+3G firmware on a WiFi Only tablet will not cause the tablet any problems; however, like you, I would prefer to have a WiFi Only firmware instead. Condi recently said he is "trying now to add next firmwares." I believe (with fingers crossed) Condi is working on adding US WiFi Only firmware. We will just have to wait to see what he does.Hello guys!
First of all, great stuff here, both AutoFlasher and AiO tool. Im completely new owner of Tablet S WiFi version, but old modder so i pretty much know what im doing.
Now, as i said, im Tab S WiFi owner and did AutoFlasher update from r1a to r5a. AutoFlasher naturally downloaded both Rom and "hidden.img" and process was undergoing well. I choosed to flash "last possible rootable hidden.img" (forgot correct number).
Everything was done well, i got my root, SD mount, permissions, everything.. except rom that was downloaded by AutoFlasher was for WiFi/3G version of Tab S, but i have just WiFi version.
Did i do anything wrong? I only choosed to update hidden.img to last possible rootable, everything else is done auto, so where did i do error?
Is there any way to fix this without reflashing it, or do i need to do it manually by creating custom firmware via AiO?
My current sys info:
Code:Model Number - GT - p7500 (done Galaxy TAB hax) (original is Sony Tablet S) Android Version - 4.0.3 (release5a) Baseband Version - unknown (naturally, since its not 3G) Kernel version - 2.6.39.4 [email protected]#1 Build number - TISU0163410
My tablet is rooted with release5, so used the flasher tool to (hopefully) replace it with release 5a.
It went through all the processes but remains on release5
Have I got it wrong to assume it will update to 5a using this method? Any help appreciated
It went through all the processes but remains on release5
Have I got it wrong to assume it will update to 5a using this method? Any help appreciated
Thanks bro for this tool,, hope you add option to go back to honeycomb soon.
Sent from my Sony Tablet S using Tapatalk 2
Sent from my Sony Tablet S using Tapatalk 2
Can I use Flasher tool to flash any firmware or I have to use the ones listed within the tool itself?
You have to use the ones listed in the tool. The tool downloads the firmware files from Condi's online storage location during its process.
Hello guys!
First of all, great stuff here, both AutoFlasher and AiO tool. Im completely new owner of Tablet S WiFi version, but old modder so i pretty much know what im doing.
Now, as i said, im Tab S WiFi owner and did AutoFlasher update from r1a to r5a. AutoFlasher naturally downloaded both Rom and "hidden.img" and process was undergoing well. I choosed to flash "last possible rootable hidden.img" (forgot correct number).
Everything was done well, i got my root, SD mount, permissions, everything.. except rom that was downloaded by AutoFlasher was for WiFi/3G version of Tab S, but i have just WiFi version.
Did i do anything wrong? I only choosed to update hidden.img to last possible rootable, everything else is done auto, so where did i do error?
Is there any way to fix this without reflashing it, or do i need to do it manually by creating custom firmware via AiO?
My current sys info:
Code:Model Number - GT - p7500 (done Galaxy TAB hax) (original is Sony Tablet S) Android Version - 4.0.3 (release5a) Baseband Version - unknown (naturally, since its not 3G) Kernel version - 2.6.39.4 [email protected]#1 Build number - TISU0163410
If you need it guys, then no problemo, i'm gonna add it to next ver
Thank you very much condi for your hard work.
Waiting for a Tablet P with 3G R5a Firmware pre-rooted.
Thank you again and happy holidays.
Waiting for a Tablet P with 3G R5a Firmware pre-rooted.
Thank you again and happy holidays.
dear condi thanks again for your works, i flashed firmware with your tool but nothing changed!!!
check if you have enough space on internal storage (~1gb+)
i have 8.4 GB free space on internal storage, i think downloaded file is damaged because just dataapp.zip can open and 2 other file cant open and in flasher tool say cant open zip!!! i dont why!!!
most probably you are right. you have uncomplete zips.
delete _firmwares directory, and run flasher again - it will redownload fw data.
------edit
PS. i've implemented size checks for downloaded data
so in next ver - no worries about that
Last edited:
dear condi thanks,thanks,thanks!!! i download required files manually with IDM software and move to flasher tool folder and start flashing process and my tab update to r5a and rooted!!! realy thanks but i have idea because i test 4 times with auto download required files with flasher tool but every time files damaged, my idea is:
I think it is better if you can download the required files individually. Because the fluctuations during the download connection may not download correctly.
I think it is better if you can download the required files individually. Because the fluctuations during the download connection may not download correctly.
I was stuck on standard 4.0.3 due to a conflict with my builprop/region during the update process. I have just flashed using this and now I have 4.0.3. (release5a) so I assume that this has cleared eveything up with a fresh image?
Thanks for your hard work condi, I will be donating some beer money :good:
Thanks for your hard work condi, I will be donating some beer money :good:
Condi, I think I found a weird bug.
I tried the flasher, the download clompeted, the the flasher stopped with the message "waiting for device".
So I tried the latest AiO5.3, also to no efford.
The AiO stopped, even at simple tasks like "run adb shell".
So I looked in the files/ folder of both tools and found, that the adb.exe located there is way smaller (159 vs. 796kb) than the last one delivered with android sdk.
After replacing your adb.exe with the one in the sdk, shell is possible in AiO, and now the flasher is pushing data.
Perhaps an update of the basic tools like adb could be useful for other to?
I tried the flasher, the download clompeted, the the flasher stopped with the message "waiting for device".
So I tried the latest AiO5.3, also to no efford.
The AiO stopped, even at simple tasks like "run adb shell".
So I looked in the files/ folder of both tools and found, that the adb.exe located there is way smaller (159 vs. 796kb) than the last one delivered with android sdk.
After replacing your adb.exe with the one in the sdk, shell is possible in AiO, and now the flasher is pushing data.
Perhaps an update of the basic tools like adb could be useful for other to?
you've got instable connection i think
but im glad that you've flashed it successfuly next ver will check if the data is correct, so it should be no problem any more
yes you are right, i had adb versions problems, i thought about it also.
got updated adb in next ver
thx for the info
!im glad
enjoy tab! about clear everything - /data parition is not modified in any way, so your installed apps should be still there.of course wipe is recommended after flash. thx for the beer! will drink for your health
I'm working now on next ver, gonna add some additional fw's.
br
condi
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone