my logAdb pull /tmp/recovery.log
try THIS FW via recovery, post results - if error - copy new recovery.log again and post.my log
I tried but didn't get that to work. I didn't pay attention to the other thread, so I hesitated and didn't flash hidden. (b/c someone posted "he thinks he can save the recovery and accidentally chose flashing hidden" and I took it as that it would work w/o. Plus it says R5+ doesn't need, so I thought both pointing it is not required, no other warnings). Too late.Hi,
I've got fix for P users who updated from 3.2 fw without hidden (kernel etc.),
and used FLASHER.
Download:
_hack_recovery.zip
custom_prerooted_R1A-nbx02_002.zip
How-To:
1. Put that two files on SD.
2. Run AiO - choose 'Custom ROM and Flashing', and 'Flash signed zip [straight from recovery]'.
3. Be sure to have installed correctly adb driver in recovery mode.
4. Follow AiO instructions and flash fw.
5. After successfull fix, you can switch to R5A - just reflash via FLASHER like before,
now it will work for sure
Post results.
br
condi
I forgot to update this on this thread (but I did on other threads already earlier on at the time) that I had eventually rooted it by being persistence (i.e., run the rooting process a few times and last time it worked). So it was rooted and now ok.I tried but didn't get that to work. I didn't pay attention to the other thread, so I hesitated and didn't flash hidden. (b/c someone posted "he thinks he can save the recovery and accidentally chose flashing hidden" and I took it as that it would work w/o. Plus it says R5+ doesn't need, so I thought both pointing it is not required, no other warnings). Too late.
So I have lost root for good now, as I had flashed install version of 3.2 on P, and that's it. I tried your method here but it iddn't go, I know why, it's because I also made a 2nd mistake: I did a factory reset in standard recovery (later read from another expert here said it is a big no-no).
Anyway, I am not a novice but no expert here, had flashed many devices over the time. I just wasn't patient enough this time and this Sony is more challenging than others. I already almost bricked it once long time ago, but I can't leave it at HC so I wanted ICS at least and came back to try. Oh well, you guys are great and not your fault of course.
Your recovery log is empty per se. Please try to flash the only tab p file we have hc3.2 installer file twice and then pull the recovery again. ThanksI forgot to update this on this thread (but I did on other threads already earlier on at the time) that I had eventually rooted it by being persistence (i.e., run the rooting process a few times and last time it worked). So it was rooted and now ok.
3G also works as well too. So all is good.
I can use adb command but cannot use fastboot command, I try with adb command for fastboot but nothing it writes "waiting".Your recovery log is empty per se. Please try to flash the only tab p file we have hc3.2 installer file twice and then pull the recovery again. Thanks
My email alerted to my post being quoted, so here I am back here to see what's going on as I don't understand your post (and thus quoted my post). You probably clicked on the wrong space in replying to someone else.Your recovery log is empty per se. Please try to flash the only tab p file we have hc3.2 installer file twice and then pull the recovery again. Thanks
Sorry about that was ment to be the post below yours. I was using the XDA mobile app. It seems to be a bit buggy atmMy email alerted to my post being quoted, so here I am back here to see what's going on as I don't understand your post (and thus quoted my post). You probably clicked on the wrong space in replying to someone else.
BTW, now I am on ICS on the Tablet P, it seems better but it still has that mysterious freeze from time to time though, didn't behave as stable as many other Android devices I own (and I have many). But psychologically I am more satisfied w/ being able to catch up to ICS and not get left behind at 3.2.
I think this is the most I could have done on my Tablet P: upgraded to ICS while AT&T version doesn't have official update; replaced locked modem card while AT&T and Sony both would not give out unlock code (regardless if I have an AT&T account, I got a very clear answer from 2 reps at diff AT&T dept); rooted it (of course), and got tethering working (that was a convoluted one) by using an xda method (thanks again to WiFi Tether by TrevE Mod); so that is maxed out of what this baby can do. Boy, did that take a long exercise. The just as long hacking was on my first Android device: Nook Color, playing w/ diff custom ROMs.
Anyway, best of luck to all of you.
By 'flash' I mean install from sd card. Can you try to 'flash' any update twice in a row without reboot i.e the one for US tab P and then use adb pull /tmp/recovery.log without reboot. I can then see why the update is failingI can use adb command but cannot use fastboot command, I try with adb command for fastboot but nothing it writes "waiting".
I can use adb only on recovery, the story is: standar 4.03 (not 5A) I rooted with Sony AllinOne, and after I flashed 4.03 5A prerooted with flasher, after I flashed 4.11P), I tought I could return to 4.03 using rom and stock recovery but nothing.
I know I was an idiot, but do you thing I can save this poor tablet or GAME IS OVER ^_^
Thank you
PS: Attach 2 image, one with rom on sd card and another with error I receive every timeI try to flash everything.
The first attempt is failing due to the zip being older than the incremental. The second is due to messed up vendor. Can you a 3.2.1 for the region you changed to on the first attempt and get a log. This may be your only hopeThank you for your time :crying:
This was a little mees tablet, I took used and seller told me he changed region to USA, I downloaded 3.2.1 US, and here the log, (my last chance).The first attempt is failing due to the zip being older than the incremental. The second is due to messed up vendor. Can you a 3.2.1 for the region you changed to on the first attempt and get a log. This may be your only hope![]()
Ok. So 3.2.1 (0035) is too old. Please try 3.2.1R2 (0042) for USAThis was a little mees tablet, I took used and seller told me he changed region to USA, I downloaded 3.2.1 US, and here the log, (my last chance).
Thank you :cyclops:
Again failure, but always thank you.Ok. So 3.2.1 (0035) is too old. Please try 3.2.1R2 (0042) for USA
Ok we are getting somewhere first failed as 27550171 is not in SKU list. Second one fails due to vendor files etc. 27550171 is JAPAN region for TABLET S. So you will probably need a 3.2.1R2 for JAPAN. You can try the ICS files but will possibly fail.Again failure, but always thank you.
Correct I received error also with japanese ICS and 3.21 japanese is offline and I'm able to find one (do you have jpn rom?You can try the ICS files but will possibly fail.