Hello all!
I need help saving my Sony Tablet P US model.
First off I did manage to root the device at 3.2.1 with S.onytablet.S v6.4. All was well. It worked properly, superuser was installed etc.
Since I have the us version, there is no official ICS 4.0.3 update so that was the next step.
I changed the region with the same program to a Tablet S UK region (I wasn't looking closely, stupid of me).
I then used the S.onytablet.S Flasher v3.0 to flash the device with what I believe was (signed-nbx02_002-ota-121121007.zip).
The Flasher spent a hour on the flashing hidden.img step. I figured something was wrong so I X'ed out of the program and restarted the Tablet P with the intent of starting over. Bad Move.
Now my screen looks just like this fellow's:
http://forum.xda-developers.com/showthread.php?t=2131779
I tried everything in that thread and in many others, always ending with the tablet spitting out this message in recovery mode:
Erohibit update as a result of checking version or base sku
Installation aborted.
I've tried the following firmwares:
signed-nbx03_016-ota-120803071
signed-nbx02_001-installer-01202.009
signed-nbx02_002-ota-120612037
custom_prerooted_R1A-nbx02_002-ota-120612037
signed-nbx02_003-ota-120510003
Even with the hacked_recovery.zip. Same message.
I'm attaching my recovery.log in the hopes that someone can point me in the right direction or at least confirm that I there isn't any hope.
By the way, this is a att&t model, if that matters.
Related
[how-to] another advenure: From German "unrootable" 3.2 build10 to rooted 4.0.3R5a
Hi there,
after about 5 nights, this "morning" at 4am, I won over Sony and M$ :highfive:
So i want to write this little tutorial for the ones, who might still be stuck on 3.2 build10.
I bought my tablet S 114DE/S, German with 3G, right before Xmas. Thought, it would be an easy task ... ha-ha.
First thing I read was, that build 10 is unrootable. F#?!
Started reading everyhing on XDA and other forums. Also read Cat McGowan's "adventure". Tried to do it like him... but as my tablet is German region an region changer only works with rooted devices, I could not flash his US files. But the idea was born.
Found the thread: XDA Developers > Sony Tablet S > Tablet S General > NEW Update Links Inc Tablet S/P R5A & Xperia S R6b
The "oldest" downloadable German original Sony FW was ICS R2a. I was not sure if this was still rootable, i would have liked to find a R1a, but what the heck, worst case is a not rooted ICS, which is still better than an unrooted 3.2!!
Downloaded, put on SD an flashed with recovery mode. Went fine.
So all you need to get away from "unrootable" build10 is a rootable original FW for YOUR tablet's country code!!! Hope you find one. There are many in the above mentioned thread.
Installed ADB automatic installer, no probs. i have Windows 7 pro 64bit.
Would be really NICE to add a clearly visible advice to also install the ADB driver (most likely MANUALLY on some systems) before using any special tools... I did not see any advice, maybe I was blind...
At least tell everybody to check, if the driver is working, by booting in recovery and looking at Windows device manager.
Problem is to find the right driver...if you simply choose the INF like for the "normal boot" ADB device, W7/64 does not install properly, you can get an error... really badly misleading message comes from Windows: It's telling something about MTP device ... well, actually you need the ADB driver!! Took me some hours... but as I found that problem only later, it took me 2 nights before, trying Condi's flasher and AIO 5.3 tool, without success...
OK, ADB drivers were installed (I only had the normal boot drivers at that time).
Downloaded Condi's AIO 5.3 tool, used the "root device" option, everything went OK, I was really happy! Rooted ICS R2a. First big step. 3.2 build10 unrootable? Not really... you only need a rootable original Sony firmware, flash it the normal way.
Then, I wanted to upgrade to R5a of course!
Condi's flasher 2.2. did not work. Maybe also because of the missing ADB driver for recovery mode?? Dunno. It always ended with: System.zip and all the other zips "not found", although I also tried pushing them manually to the internal SD before... when checking later, they disappeared.
Tried AIO 5.3 and custom signed zip. Always stuck in recovery mode with "Status 7" Error, like described in post #72 in this post:
XDA Developers > Sony Tablet S > Tablet S Android Development > [FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery!
Also here, it would be nice to bring the advice (install ADB drivers for recovery mode) BEFORE! It does NOT appear in the tool's window IF you are stuck!
After finding the right driver, it was no problem installing the prerooted double-flash zip with the AIO tool... Also here, do not panic when the "Status7" Error appears... it's normal, it disappears after a few seconds and at the same time, the hint about the driver comes up in the command window...
Btw I had no problems with missing google market or apps or any Sony applications. Google play is working, also Sony remote etc.
OK, that's it!
Waiting for 4.2
Have fun with your rooted Sonys!
Many thanks to Condi and the other devs for the tools, videos, tutorials... they may not be perfect, but without, it would be impossible for guys like me :angel:
Daniel
I’ve been following this forum for quite some time but never had anything smart to say or ask before today. So this is my first post and call for help in the same time!
I have Sony Tablet S32GB Wi-Fi only, purchased in UAE (Model: SGPT112AE/S).
Used S.onyTablet.S v2.4 [FLASHER] to upgrade from Honeycombto R5A and now I’m stuck with device showing SONY logo and not booting further! The only (at least for me) unexpected moment during the flashing process was several force close dialogs that popped-up on the tablet while flashing current sys and a message “Cleaning up...” (after “Finished!”) that took more than 20 minutes so I’ve restarted tablet manually.
During the process I’ve picked “FLASH hidden.img from thisstock fw version” option.
Now when power-on device, boot process stops at SONY logo. I can use adb shell in both, normal and recovery mode (device status is recovery and shell commands are very limited) - device is recognized. Using S.onyTablet.S [ALLinONE] v5.3 or FLASHER again, reports the same: ‘su’ binary not found. You need ROOT to use this function.
In recovery mode it states “Android system recovery (Rev.10)<3e>”and I can run option “Update system from SD card”. I downloaded updates from condi’s Google Drive and for both, encrypted and decrypted fws, error is the same: “E: Prohibit update as a result of checking version or base sku/Installation aborted.”; for custom prerooted fws error is “E: failed to verify whole-file signature/E: signature verification failed/Installation aborted.”.
I would be more than grateful for any help or suggestion how to proceed and recover my dear Tablet!
Br,
Boki
boki71 said:
I’ve been following this forum for quite some time but never had anything smart to say or ask before today. So this is my first post and call for help in the same time!
I have Sony Tablet S32GB Wi-Fi only, purchased in UAE (Model: SGPT112AE/S).
Used S.onyTablet.S v2.4 [FLASHER] to upgrade from Honeycombto R5A and now I’m stuck with device showing SONY logo and not booting further! The only (at least for me) unexpected moment during the flashing process was several force close dialogs that popped-up on the tablet while flashing current sys and a message “Cleaning up...” (after “Finished!”) that took more than 20 minutes so I’ve restarted tablet manually.
During the process I’ve picked “FLASH hidden.img from thisstock fw version” option.
Now when power-on device, boot process stops at SONY logo. I can use adb shell in both, normal and recovery mode (device status is recovery and shell commands are very limited) - device is recognized. Using S.onyTablet.S [ALLinONE] v5.3 or FLASHER again, reports the same: ‘su’ binary not found. You need ROOT to use this function.
In recovery mode it states “Android system recovery (Rev.10)<3e>”and I can run option “Update system from SD card”. I downloaded updates from condi’s Google Drive and for both, encrypted and decrypted fws, error is the same: “E: Prohibit update as a result of checking version or base sku/Installation aborted.”; for custom prerooted fws error is “E: failed to verify whole-file signature/E: signature verification failed/Installation aborted.”.
I would be more than grateful for any help or suggestion how to proceed and recover my dear Tablet!
Br,
Boki
Click to expand...
Click to collapse
UH OH . Nah not really.
You are meant to have ICS before using flasher!!! Hence your issues. easy fix though.
Click on the first link in my signature. Search for Saudi Aribia? AE model???
Copy to SD
You will need to boot into recovery and select the file from recovery to install.
Then root using AiO, then use flasher to get R5a
Happy travels
Stifilz
Stifilz, thank you very much!
I did exactly what you said and now Tablet is on R5A and rooted! :highfive:
Saudi Arabia fw worked like a charm for my AE model; there were some problems with ADB drivers and when I solved that – AiO and Flasher finished job perfectly! :victory:
Once again, THANK you and I wish you great and fruitful year!
Boki
Hi all I've updated my G9 80 many times and tried all the available ROM's with a few hiccups but have always managed to recover the tab with the info on this forum. On my latest update the tablet appears to refuse to load a ROM from the SDE menu? If I boot the tab normally it halts at the ARCHOS boot screen but I can see the tab in device manager/Disc drives as ARCHOS_A80S but not in the explorer window and the USB is shown as an unknown device. If I boot up into the SDE/Archos A80S Recovery menu and then select (Update Firmware) it opens up a drive on my win7 system labeled A80S_REC as per normal and I can transfer the (fimware_archos_it4.aos) update file across to the tab but when I select (OK to disconnect) the tab starts the update in progress which fails after about 20 seconds with a Update failed (221) message. This is the method that has always solved any problems in my previous operating excursions but after a few days of trying to solve this problem I'm now at an impasse has anybody any ideas or is it time to upgrade to the Gen 10 and retire this tab as bricked
Thanks for any info
Ken.
I made the basic mistake of trying to update with an older ROM (kicks own backside for making such a basic mistake) aaaaa well back to trying to brick it again but I happy as the screen of my old backup Hannspad is doing my eys in
The 221 error usually means that you have tried to install an older official Archos firmware than the last official Archos firmware you had installed.
If you know exactly which one that was, then you can find a link to download it hidden in-between all of the other rooted and custom ROMs in this list.
Go into Recovery / SDE and do a full Reformat. Do not try to install anything, just go thru the steps (without connecting to your computer) and let it fail the firmware upgrade process. Then exit out so your tablet turns off. Then start back up in Recovery / SDE and do another full Reformat. Then connect to your computer and copy over the Archos .aos file.
If it still shows a 221 error after that, then you may have at some point installed a higher official Archos firmware. Start all over with the above steps, but with the next higher Archos firmware download.
I really do not know just what might happen if say you had the official Archos 4.0.7 firmware installed and then installed a 'rooted' 4.0.25 or 4.0.26 firmware. That could possibly somehow make the tablet only allow you to install that specific official Archos firmware afterwards also.
Let us know what luck you have?
Now OK
Hi I came to the same conclusion myself and solved the problem 5 min after starting the thread but thanks for the info, it's much appreciated. I cannot understand how I missed this for so long as I've loaded the majority of the roms on this site. I solved it by downloading the latest rooted Firmware 4.0.26 from surdu_petru (GENIUS ROM MAKER )
Thanks again
Ken.
55mls said:
The 221 error usually means that you have tried to install an older official Archos firmware than the last official Archos firmware you had installed.
If you know exactly which one that was, then you can find a link to download it hidden in-between all of the other rooted and custom ROMs in this list.
Go into Recovery / SDE and do a full Reformat. Do not try to install anything, just go thru the steps (without connecting to your computer) and let it fail the firmware upgrade process. Then exit out so your tablet turns off. Then start back up in Recovery / SDE and do another full Reformat. Then connect to your computer and copy over the Archos .aos file.
If it still shows a 221 error after that, then you may have at some point installed a higher official Archos firmware. Start all over with the above steps, but with the next higher Archos firmware download.
I really do not know just what might happen if say you had the official Archos 4.0.7 firmware installed and then installed a 'rooted' 4.0.25 or 4.0.26 firmware. That could possibly somehow make the tablet only allow you to install that specific official Archos firmware afterwards also.
Let us know what luck you have?
Click to expand...
Click to collapse
I recently got a Xperia X10a, and I noticed that it has the android 1.6 on it. I know that the newest version of Android is 4.2 so I started searching the internet for an update to android 4.0.4 at least. I discovered that the android 4 for the X10 isn't completed so I went to android 2.3 and found the site freexperia, there you can download the CM7 for X10. I'm a noob, I don't know what a kernel is and what I can cause to the phone by changing it so I need help, because every tutorial explains how to update from 2.1/2.3 to 2.3.3 or something like that. I also tried to update the phone throug SE Pc companion and update service, but I can't pass through the step of pressing back and plugging the phone in again, I do what is said to do but nothing happens and the phone just turns back on. Also i saw something about the baseband and changing it to most recent one, but I don't know how to do it, and I discovered that you can put multitoutch in the X10. How can I update from android 1.6 to 2.3? I need to update the baseband? If yes how and to what version(i'm from brazil, and I don't know if this change from country to country) What are the main differences between CM7 and the official SE 2.3 updates? Through these updates the multitouch will be automatically installed in my device? I also would like to install clock work mod on my device, how can I do that?
PS.: I read the thread about using the flashtool to do many thing to my device, and the tutorial was very clear, so if I can do what I want using tha tutorial as a foundation the process will be much more easy.
Well, I've been trying to update for a while now and I think I discovered the problem. As I need at least the Android 2.1 to start doing what I want with my phone I have to update via PC companion, but when I reach the end of the preparing step I get an error on my PC, after I turning off the device I plug it in holding down the back key and a pop up apears saying that the device had a malfunctionig and is not conect so I get stuck in this step, as the device is not recognized. Can anyone help me?
What i did with mine is rooted the phone while on 1.6 then changed the region code. After connecting via pc comp i got the update to 2.3.
Guys,
Been struggling with my Vertu for a long time and thought of bringing it here.
Basically, im trying to reinstate the Firmware on my Vertu and looked at this link.
Rooted the phone successfully via KingoRoot
I am able to get to the point where I have the drivers and the flashtool ready.
1. Consistently I found an error while I tried to mount the "scatter file" but then I saw a video where someone opened it and added ## in the first line and mine loaded correctly.
2. Now when I try to run the update, it gives me a BROM error S_INVALID_BBCHIP_TYPE(0x3EB)
OR Failed to get PMT Info
Any idea how I can get the Firmware loaded ?
Can someone please try and help this guy get his very expensive phone working.
https://www.google.com/search?q=BRO...nt=ms-unknown&sourceid=chrome-mobile&ie=UTF-8