Maybe the problem is intractable to Sony Tablet S, because of its 3E recovery.
My S(China 3G model) was repaired, and the version of system backed to factory(3.2.1). I tried to root it with AIO 5.2, but failed. So, I updated it to 4.0.3 R1 with SD, everything is OK.
Then, I rooted it by AIO 5.2, and changed the region to JP. I tried to update it to JP 4.0.3 R1 with SD, everything is going so well, but it stopped in "SONY" interface, unable to go.
A long time later(10 mins), I forced to reboot, system data still, never changed. So I tried it again, and wipe data, the problem still.
There is no way to OTA update, and it was failed, "error code: 7". I tried to OTA it again, it displayed the system is newest, but my system is CH 4.0.3 R1 still!
Who can help me?!
How can I make it to normal?!
Is the BUG of AIO 5.2?!
Thanks for your reply!
Sorry for my poor English!
All I know is that it's not a bug of v 5.2, cause I have the same error. Cannot solve it.
Maybe factory formatting could help... not just a reset. But do not know if it works on Sony Tablet S...
I get the same error code on my other android device.
Maybe it is the partition sizes.
The device?
The file is too large on one side?
OR maybe the build.prop is gone for good
Bootloops mean that there is a chance that there is a corruption o.o
Sent from my Sony Tablet S using xda premium
mikajo said:
All I know is that it's not a bug of v 5.2, cause I have the same error. Cannot solve it.
Maybe factory formatting could help... not just a reset. But do not know if it works on Sony Tablet S...
Click to expand...
Click to collapse
Thanks, but reset so many times.
andyabc said:
I get the same error code on my other android device.
Maybe it is the partition sizes.
The device?
The file is too large on one side?
OR maybe the build.prop is gone for good
Bootloops mean that there is a chance that there is a corruption o.o
Sent from my Sony Tablet S using xda premium
Click to expand...
Click to collapse
But I restored the build.prop(factory version), and tried it again, rebooting in "SONY" stopped.
Topery Chiang said:
But I restored the build.prop(factory version), and tried it again, rebooting in "SONY" stopped.
Click to expand...
Click to collapse
What do you mean 'Stopped'?
It is stuck on the Sony screen?
Sent from my Sony Tablet S using xda premium
andyabc said:
What do you mean 'Stopped'?
It is stuck on the Sony screen?
Sent from my Sony Tablet S using xda premium
Click to expand...
Click to collapse
Yes, yes, yes.
It is stuck on the "SONY" interface during the third rebooting.
Can you help me to solve this problem?
Thanks!
Topery Chiang said:
Yes, yes, yes.
It is stuck on the "SONY" interface during the third rebooting.
Can you help me to solve this problem?
Thanks!
Click to expand...
Click to collapse
Can you access the recovery partition?
Sent from my Sony Tablet S using xda premium
Topery Chiang said:
Yes, yes, yes.
It is stuck on the "SONY" interface during the third rebooting.
Can you help me to solve this problem?
Thanks!
Click to expand...
Click to collapse
OK Do you have adb debugging enabled??
DO NOT FACTORY RESET!!!!!
Try to flash a rom and use adb pull /tmp/recovery.log
Then post here
Stifilz
andyabc said:
Can you access the recovery partition?
Sent from my Sony Tablet S using xda premium
Click to expand...
Click to collapse
Yes.
I learned that this is not just a Sony Tablet S problem but can happen on every device.
Furthermore I learned that the Update is not getting the correct device name from the build.prop.
This is very interesting as I can't remember that I would have changed the name of the tablet in the build.prop. However, maybe it's helpful for someone of you
Topery Chiang said:
Maybe the problem is intractable to Sony Tablet S, because of its 3E recovery.
My S(China 3G model) was repaired, and the version of system backed to factory(3.2.1). I tried to root it with AIO 5.2, but failed. So, I updated it to 4.0.3 R1 with SD, everything is OK.
Then, I rooted it by AIO 5.2, and changed the region to JP. I tried to update it to JP 4.0.3 R1 with SD, everything is going so well, but it stopped in "SONY" interface, unable to go.
A long time later(10 mins), I forced to reboot, system data still, never changed. So I tried it again, and wipe data, the problem still.
There is no way to OTA update, and it was failed, "error code: 7". I tried to OTA it again, it displayed the system is newest, but my system is CH 4.0.3 R1 still!
Who can help me?!
How can I make it to normal?!
Is the BUG of AIO 5.2?!
Thanks for your reply!
Sorry for my poor English!
Click to expand...
Click to collapse
ok, lets try to solve the problem.
try to flash any update zip, after error 7 wait a minute, and get log from device:
Code:
adb pull /tmp/recovery.log
attach it here, let me see.
condi said:
ok, lets try to solve the problem.
try to flash any update zip, after error 7 wait a minute, and get log from device:
Code:
adb pull /tmp/recovery.log
attach it here, let me see.
Click to expand...
Click to collapse
Mine is JP, I was flashed the JP.
Hello, what the recovery.log(similar) is……
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/_hack_recovery.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 111104048 -> 111201009
Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst
Erohibit update as a result of checking version or base sku
Installation aborted.
Topery Chiang said:
Mine is JP, I was flashed the JP.
Hello, what the recovery.log(similar) is……
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/_hack_recovery.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 111104048 -> 111201009
Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst
Erohibit update as a result of checking version or base sku
Installation aborted.
Click to expand...
Click to collapse
similar? so thats not your log?
condi said:
similar? so thats not your log?
Click to expand...
Click to collapse
This isn't mine, but my log is similar to that(I checked some days ago).
I can't provide mine for you these days, my friend borrowed it.
Mine is similar, the words of "Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst" specially!
Please!
Topery Chiang said:
This isn't mine, but my log is similar to that(I checked some days ago).
I can't provide mine for you these days, my friend borrowed it.
Mine is similar, the words of "Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst" specially!
Please!
Click to expand...
Click to collapse
try this fw.
condi said:
try this fw.
Click to expand...
Click to collapse
nbx03_016?
What the region is?
condi said:
try this fw.
Click to expand...
Click to collapse
Like UK version, if the wifi only and wifi+3G can flash mutually without rescue-backdoor?
Topery Chiang said:
nbx03_016?
What the region is?
Click to expand...
Click to collapse
Have a look and see for yourself. Click Update Links in my signature then search for nbx03_016 on that page.
Stifilz
Topery Chiang said:
This isn't mine, but my log is similar to that(I checked some days ago).
I can't provide mine for you these days, my friend borrowed it.
Mine is similar, the words of "Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst" specially!
Please!
Click to expand...
Click to collapse
ok now try to flash this fw, and post results - if error, post recovery.log just after flashing try.
Related
EDIT: New problem I am using this root method:http://forum.xda-developers.com/showthread.php?t=1046855 However, no matter how many times I attempt to perform step 9, it keeps giving me the exclamation point. Any ideas?
The only way I could get root was to use super one click. Version 1.7 worked for me on two fascinates.
Sent from my SCH-I500 using XDA App
Were those two running 2.2.1? ED01?
I am pretty sure that with the latest kernals from stock you won't be able to get a root to stick.
No matter what after running any root method, you'd have reboot back to recovery and flash some kind of kernal in order for it to stick.
If you plan on putting a rom on your phone, just follow my stickied guide in this forum and flash that rom in place of the kangbang community rom I linked to... or just flash your kernal of choice to keep the stock experience with root.
Well, the problem that I'm having is that when I attempt to apply the "update.zip" file, I get a progress bar for a fraction of a second and then the exclamation point with the droid guy next to it.
I get this:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification failed
Installation aborted.
EDIT: Just realized the "update.zip" file was missing. But now I get this:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Looks like I wont figure it out today (too tired to think straight)
spartan.062 said:
Well, the problem that I'm having is that when I attempt to apply the "update.zip" file, I get a progress bar for a fraction of a second and then the exclamation point with the droid guy next to it.
I get this:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification failed
Installation aborted.
EDIT: Just realized the "update.zip" file was missing. But now I get this:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Looks like I wont figure it out today (too tired to think straight)
Click to expand...
Click to collapse
Sometimes I download multiple files at one time. For instance, to get the ED01 modem I downloaded the 2 update.zip's from adrynalyne's thread. The second update.zip had a "(2)" at the end of it. Erase that. On your PC the files needs to only say "update", not "update.zip". The phone adds a ".zip" to each file. Make sure you are doing that.
Sent from a depraved XDA junkie and flashaholic
superchunkwii said:
I am pretty sure that with the latest kernals from stock you won't be able to get a root to stick.
No matter what after running any root method, you'd have reboot back to recovery and flash some kind of kernal in order for it to stick.
If you plan on putting a rom on your phone, just follow my stickied guide in this forum and flash that rom in place of the kangbang community rom I linked to... or just flash your kernal of choice to keep the stock experience with root.
Click to expand...
Click to collapse
This isn't true. You are thinking about installing CWM recovery, that gets overwritten with the stock recovery by the stock kernels. I've used this method on many of the stock builds including ED01: http://forum.androidcentral.com/ver...d-post-1-before-posting-forum.html#post699944
I know of a VERY simple root method. If you want to know it, hit me back. It seems to me that no one is using it but it is posted in these forums.
Sent from a depraved XDA junkie and flashaholic
What method is that kidserious?
spartan.062 said:
Ok... Every time that I attempt the adb root, I get this in the command prompt:
'adb' is not recognized as an internal or external command, operable program or batch file
Click to expand...
Click to collapse
Are you on stock 2.2?
spartan.062 said:
What method is that kidserious?
Click to expand...
Click to collapse
Click on this and then once you are there download linked file. Then place it on your SD card. Let me know when you have done that.
http://forum.xda-developers.com/showthread.php?t=1045048
Yep. And I am still somewhat confused when it comes to flashing a kernel. And I already have the su file, however, when I try to apply the update to get to CWM, It won't take the update. I'll try adding .zip to the end of the name.
spartan.062 said:
Yep. And what was that method you were mentioning?
Click to expand...
Click to collapse
Yes, but I see you have had problems with this method already. Are you able to get odin properly set up on your PC? I mean have you been able to flash anything via odin? Did you see my link in my above post? And don't worry about a kernel just yet. Lets get this taken care of first.
Yeah, it said that it was successful. But the update.zip WILL NOT apply no matter what I do.
spartan.062 said:
Yeah, it said that it was successful. But the update.zip WILL NOT apply no matter what I do.
Click to expand...
Click to collapse
Did you see a Green "Pass" when it finished in odin? And when you put the battery back in were you unplugged first? You may know this but you cannot allow the phone to boot normally before booting into recovery. Try using this recovery instead: http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5
Flash that the same way in Odin?
spartan.062 said:
Flash that the same way in Odin?
Click to expand...
Click to collapse
Yes, but boot into recovery FIRST before the phone turns on normally. Not trying to sound condescending but do you understand what I am saying about booting into recovery first?
Yeah I understand. Ok I got the voodoo lady's voice. Now I have the red CWM menu.
spartan.062 said:
Yeah I understand.
Click to expand...
Click to collapse
The way it always works for me is I don't even boot into the blue recovery, it boots straight into red. Let me know what happens.
spartan.062 said:
Yeah I understand. Ok I got the voodoo lady's voice. Now I have the red CWM menu.
Click to expand...
Click to collapse
GOOD! With that menu find the superuser root package from nemesis2all on your SD card and install it. Let me know what happens.
So im rooted and running a stock rom i havent unlocked my boot loader but i cant update from mr1 my phone downloads the update but when it goes to reboot and apply it the status bar goes about have way and reboots and when it restarts is says update failed anyone have a solution
Sent from my MB855 using XDA Premium App
I have the same issue...
Sent from my MB855 using XDA Premium App
I was having the same issue. I was on stock and rooted. I had removed a ton of bloat from /system/app. I had to put all of my files I removed back into /system/app and voila the update went through.
Ughhhhh ......forget that i guess im waiting for a flashable zip thats to much work
Sent from my MB855 using XDA Premium App
smoothone said:
I was having the same issue. I was on stock and rooted. I had removed a ton of bloat from /system/app. I had to put all of my files I removed back into /system/app and voila the update went through.
Click to expand...
Click to collapse
I had renamed sprint_worldwide, sprint wallet and the stock news app to ".bak". When I made them ".apk" again the OTA went through.
I am rooted with a locked bootloader with all the sprint bloatware removed and the updated went flawless for me......Still have not made a call yet to see if the "muted call" issue is resolved. But I just wanted to speak up and let others know to at least try to run the update, it could work.
I am in the same situation. I am rooted with a locked boot loader and using the stock rom and cannot apply the ota update. Here is what I gather from the recovery log:
Finding update package...
I:Update location: /cache/
Blur_Version.45.2.1.MB855.Sprint.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1469 bytes; signature 1446 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing Etna updater extensions
installing NV updater extensions
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed:
apply_patch_check("/system/build.prop", "8250ac16a9fab966853d763e7e02db69fd1499df", "85bbed34360609e4bbf50f01b6f0519c02fccfcc")
assert failed: apply_patch_check("/system/build.prop",
"8250ac16a9fab966853d763e7e02db69fd1499df", "85bbed34360609e4bbf50f01b6f0519c02fccfcc")
E:Error in /cache/Blur_Version.45.2.1.MB855.Sprint.en.US.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I could be wrong, but it seems like there is something wrong with either my build.prop or the patch itself.
Im not to sure but i think this may be the ota ..........has anyone tried and know ............http://forum.xda-developers.com/showthread.php?t=1202666
Final build courtesy of the fine folks at MOTOROLA 8/11/11
Sent from my MB855 using XDA Premium App
ajoerivera said:
Im not to sure but i think this may be the ota ..........has anyone tried and know ............http://forum.xda-developers.com/showthread.php?t=1202666
Final build courtesy of the fine folks at MOTOROLA 8/11/11
Sent from my MB855 using XDA Premium App
Click to expand...
Click to collapse
For me, the problem with the manual update is RSD lite will not show my device when I plug it in. I have tried 2 different computers and multiple USB ports. Both computers install the drivers but that’s as far as it will go.
NextEQ said:
For me, the problem with the manual update is RSD lite will not show my device when I plug it in. I have tried 2 different computers and multiple USB ports. Both computers install the drivers but that’s as far as it will go.
Click to expand...
Click to collapse
Make sure you installed the drivers i had the same issue worked for me
Sent from my MB855 using xda premium
I've tried the official OTA 3 times with no success. Anyone have any suggestions as to what might correct the issue?
Photon is rooted but otherwise stock w/alternate launcher. Battery level is around 65. Have only deleted one stock app but can't remember what it was and don't have a backup of it.
I would rather not do the manual *leaked* update. Seems like too much work with having to actually re-activate.
NextEQ said:
For me, the problem with the manual update is RSD lite will not show my device when I plug it in. I have tried 2 different computers and multiple USB ports. Both computers install the drivers but that’s as far as it will go.
Click to expand...
Click to collapse
I had the same issue...you have to go into device manager and click on android usb devices and manually reinstall the driver.....atleast thats how I ended up getting my rsd working and connecting to my photon
unsane said:
I had the same issue...you have to go into device manager and click on android usb devices and manually reinstall the driver.....atleast thats how I ended up getting my rsd working and connecting to my photon
Click to expand...
Click to collapse
Thanks, I will try that next time. I ended up trying my luck to manually update the full SBF on my wife’s netbook while she was away. The stupid thing worked with no problems! Nearly pulled my hair out trying to get my main PC to recognize the phone.
OTA update error problem fixed
sigabrt said:
I had renamed sprint_worldwide, sprint wallet and the stock news app to ".bak". When I made them ".apk" again the OTA went through.
Click to expand...
Click to collapse
I tried installing the OTA update 3 or 4 times and received the same error each time. After reading this I realized that I had renamed 4 apps (news.widget, swype, vtt-sprint, and weatherwidget) to .bak. I went in and changed them back to .apk and the OTA went through on the first try. Not sure what would have happened if the apk's were deleted, but I'm guessing just about any apk that gets modified in the system folder will throw off the OTA update. Unless of course it was entirely coincidence that on my 5th try the OTA suddenly started working (did all of these within about an hour).
Hi everyone,
I`m tryign to install criskelo rom (http://forum.xda-developers.com/show....php?t=1714091) and I followed every step, but when trying to install the rom I get the error bellow:
Installing: /emmc/Criskelo_6.0.1_Stock_XXBLG9_oat.zip
Finding update package....
Opening update package....
E: Can't open /emmc/Criskelo_6.0.1+Stock_XXBLG9_ota.zip
(bad)
Installation aborted
Anyone knows what I did wrong?
Thanks.
Ryudo0 said:
Hi everyone,
I`m tryign to install criskelo rom (http://forum.xda-developers.com/show....php?t=1714091) and I followed every step, but when trying to install the rom I get the error bellow:
Installing: /emmc/Criskelo_6.0.1_Stock_XXBLG9_oat.zip
Finding update package....
Opening update package....
E: Can't open /emmc/Criskelo_6.0.1+Stock_XXBLG9_ota.zip
(bad)
Installation aborted
Anyone knows what I did wrong?
Thanks.
Click to expand...
Click to collapse
Check the download again..compare the md5...probably a bad download..
Sent from my GT-I9300 using xda app-developers app
zoot1 said:
Check the download again..compare the md5...probably a bad download..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I've already tried to download the rom about 4-5 times and still not working. =/
Ryudo0 said:
Hi everyone,
I`m tryign to install criskelo rom (http://forum.xda-developers.com/show....php?t=1714091) and I followed every step, but when trying to install the rom I get the error bellow:
Installing: /emmc/Criskelo_6.0.1_Stock_XXBLG9_oat.zip
Finding update package....
Opening update package....
E: Can't open /emmc/Criskelo_6.0.1+Stock_XXBLG9_ota.zip
(bad)
Installation aborted
Anyone knows what I did wrong?
Thanks.
Click to expand...
Click to collapse
Have you tried flashing any other custom-rom??
I hope ur rooted and this has also happened to me few times and always the culprit was bad download
Sent from my GT-I9300 using xda premium
zoot1 said:
Check the download again..compare the md5...probably a bad download..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
There is nothing else which can go wrong here...check the md5 of the downloaded file...which recovery are you using?
zoot1 said:
There is nothing else which can go wrong here...check the md5 of the downloaded file...which recovery are you using?
Click to expand...
Click to collapse
I was using CWM.
I got it to work.... Everytime I downloaded the file it was from the first link I tried the sencond one and it worked.
Thanks everyone.
Off topic question: My kies is not working anymore this normal?
Ryudo0 said:
I was using CWM.
I got it to work.... Everytime I downloaded the file it was from the first link I tried the sencond one and it worked.
Thanks everyone.
Off topic question: My kies is not working anymore this normal?
Click to expand...
Click to collapse
Kies won't work with custom Rom......in fact forget kies ever existed, it is widely recognized as an unreliable POS!
Put the Update ZIP onto your SDCARD and try the install and also check the size of the zip file
I had a similar issue, my download didn't throw an error in CWM, but when I flashed it and rebooted I was greeted with constant force closes (so much, so quickly that I couldn't finish pressing ok). Went back into CWM and did a complete wipe and flashed again. No boot. I only got my s3 on Saturday so I was scared sh**less. After a quick trip to the bathroom to calm down I figured out the zip was corrupt and restored to a CWM backup then restored a TiBp. Flashed WanamLite with the theme linked in the OP instead. I wasn't really emotionally stable enough to try flashing criskelo again...
On another note, I always check MD5's but I couldn't find any for v6.0.1 of criskelo's ROM? Can anyone point me in the right direction? I just wanna confirm that the zips were corrupt..
slaphead20 said:
Kies won't work with custom Rom......in fact forget kies ever existed, it is widely recognized as an unreliable POS!
Click to expand...
Click to collapse
Yea... but I made contacts backup using the Kies any ideias on how to retrieve them without having to install the original rom again?
Thanks
Ryudo0 said:
Yea... but I made contacts backup using the Kies any ideias on how to retrieve them without having to install the original rom again?
Thanks
Click to expand...
Click to collapse
Use Google for your contacts in future! Then they are safe in the cloud! Only way I know is flash back to stock
flash back to stock, restore contacts using kies to your phone then either backup to google a/c or memory card
i chose the memory card option as restoring from google always gives me duplicate contacts. its the only way i think
Guess I will have to go back to the old rom and flash again. Thanks everyone for the tips.
I`ve been lazy to look into cloud stuff for like a year now =P... really stressing year... guess I can`t run from it now lolz.
Why wont the device update to .18? I downloaded the firmware from their site and get error 22 every time I try to update my device. This is bullcrap, first I couldn't OTA now I can't even manually update.
Says this exactly:
The system update failed. (22)
The application is not compatible with the device ROM.
The system is restored to previous configuration.
Click to expand...
Click to collapse
And before some jackass says I have the wrong ROM(US,WW,etc). I have US the correct one I have used for every single update.
Anyone?
Did you modify /system with anything? Edited build.prop, deleted crapware, etc?
Did you unzip it? There is a zip inside of a zip. You need to unzip it once.
giant25 said:
Did you unzip it? There is a zip inside of a zip. You need to unzip it once.
Click to expand...
Click to collapse
I've the same problem, yes it's just unzipped.
Same problem
Same problem here... WW version. Cannot get OTAs, try to update manually and still no luck.. appears a android with a red signal....
**** asus!!
I cannot do unlock ... and cannot get OTAs... Very frustrating.
Anyone know how to fix this?
Well if I ran the update it is obviously unzipped
abcorp said:
Same problem here... WW version. Cannot get OTAs, try to update manually and still no luck.. appears a android with a red signal....
**** asus!!
I cannot do unlock ... and cannot get OTAs... Very frustrating.
Anyone know how to fix this?
Click to expand...
Click to collapse
Snap!
Same problem here.
Can't unlock bootloader, Lost root several updates ago, can't restore root. Never even seen an OTA, always had to apply updates manually in the past (after a wipe) but fails with latest update (system update failed. 22).
My motherboard was swapped out after a previous RMA but my serial number is correct in system settings.
WEAK!
richardmlea said:
Snap!
Same problem here.
Can't unlock bootloader, Lost root several updates ago, can't restore root. Never even seen an OTA, always had to apply updates manually in the past (after a wipe) but fails with latest update (system update failed. 22).
My motherboard was swapped out after a previous RMA but my serial number is correct in system settings.
WEAK!
Click to expand...
Click to collapse
Same problem: after a RMA, my tablet returned re-locked, unrooted and now with error 22 trying the update via zip file.
I'm very angry
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
Has anyone fixed this issue?
mccahon said:
Anyone?
Click to expand...
Click to collapse
mine too :crying::crying::crying:
Hmmm. Just noticed the US and WW version downloads have been pulled from the site. Perhaps faulty file has been the source of our problems?
Restorer said:
Hmmm. Just noticed the US and WW version downloads have been pulled from the site. Perhaps faulty file has been the source of our problems?
Click to expand...
Click to collapse
maybe..
DarkMenTH said:
maybe..
Click to expand...
Click to collapse
The updates are back up - but still no go for me :crying:.
Wow ASUS fix the issue. You screw us out of OTA and Unlocking now manual updating. How is this legal let alone a way to treat customers.
Just tried the ones they just uploaded and still error 22. This makes no sense.
mccahon said:
Just tried the ones they just uploaded and still error 22. This makes no sense.
Click to expand...
Click to collapse
Me too
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
colostro said:
Me too
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
Click to expand...
Click to collapse
Can you guys all check your logs and see if we all fail with the same problem (in my case it says SKU size error, though I don't understand how come). Look in \cache\recovery\last_log
Code:
I:dec_rule: 10 4 2 18 0
I:dec_version: 10 4 2 17 0
I:check SKU & version pass
Installing update...
Check : blob size = 818942949
[COLOR="Red"]512MB ROM device but update 768MB images[/COLOR]
Installation SKU size error.
I:result_code: 80000016
Check and format /storage to vfat if needed...
Done.
I:timed out waiting for key input; rebooting.
Success!!!
OK guys, I got it sorted - at least for the US version. The b$£@%ds still haven't got the correct downloads on all of the ftp sites!!! Only the smaller one (319,948KB extracted) from the Global site (that's the one you don't use the akmai downloader) will work.
Looks like they realised this yesterday, pulled the wrong files but some drongo uploaded the wrong ones again!
Hope this helps at least some of you to get updated.
Thanks Asus for wasting all my time.
EDIT: Be careful guys. In all the excitement I didn't realise I have lost root. Voodoo Rootkeeper backup folders seem to have been wiped . Pretty sure I did everything right but it's all been wiped :crying:.
Hi!
Can somebody flash following ZIP in the FACTORY recovery?
https://docs.google.com/file/d/0Bwt_FvteRPD7WkN1YlVXYlFwbmM/edit?usp=sharing
I just want to know whether it works.
Maybe I can create a "Root.zip" package using this but first I need to know the thing above.
Information:
This ZIP was extracted from an original GT-I8190 firmware, namely from the I8190XXAMA2_I8190OXXAMA2_XEO.
Package contains multi CSC definitions, you can check the country codes in the package's /system/csc folder.
Flashing this will not brick your device just refreshes the CSC.
Would you like to elaborate a bit more people like to know a bit more about these things before they flash and test..
Sent from my GT-I8190 using xda premium
Whats in it? 55mb?
Info
First post updated.
CSC carrier codes and no it will not work in a stock recovery.
Benzonat0r said:
CSC carrier codes and no it will not work in a stock recovery.
Click to expand...
Click to collapse
Have you tried or you just simple wrote here a response?
Do we even need root zip now? We can just flash cwm in odin and reset counter
tys0n said:
Do we even need root zip now? We can just flash cwm in odin and reset counter
Click to expand...
Click to collapse
No, of course we don't. But what about alternative, working, and easier methods?
ladislav.heller said:
Have you tried or you just simple wrote here a response?
Click to expand...
Click to collapse
No I haven't tried cause I simply know it will not work.
But this script will.
Code:
show_progress(0.100000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
package_extract_dir("system", "/system");
show_progress(0.500000, 0);
unmount("/system");
Benzonat0r said:
No I haven't tried cause I simply know it will not work.
Click to expand...
Click to collapse
OK, so please explain a little bit deeper why then Samsung puts a flashable package (sec_csc.zip) into its own firmware? I extracted it from an original firmware! Who will then execute the script inside the package?
ladislav.heller said:
No, of course we don't. But what about alternative, working, and easier methods?
Click to expand...
Click to collapse
I agree. It was more like a joke, just because I was happy about it
ladislav.heller said:
OK, so please explain a little bit deeper why then Samsung puts a flashable package (sec_csc.zip) into its own firmware? I extracted it from an original firmware! Who will then execute the script inside the package?
Click to expand...
Click to collapse
I've been thinking bout that csc.zip also, as it installs upon boot right after flash...
tys0n said:
I agree. It was more like a joke, just because I was happy about it
I've been thinking bout that csc.zip also, as it installs upon boot right after flash...
Click to expand...
Click to collapse
Exactly. Right after flashing the whole firmware. Like on other Samsung devices (Galaxy Ace for example).
Finding update package...
Opening update package...
Verifying update package...
Installing update...
The install meter moves about a cm, then stops.
Dont know if it installs right, but no errors
tys0n said:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
The install meter moves about a cm, then stops.
Dont know if it installs right, but no errors
Click to expand...
Click to collapse
What do you mean by "then stops" ? What happened? The progressbar stopped?
Whatever, it seems that this package's signature is correct and maybe we can use it for some tricks.
ladislav.heller said:
What do you mean by "then stops" ? What happened? The progressbar stopped?
Whatever, it seems that this package's signature is correct and maybe we can use it for some tricks.
Click to expand...
Click to collapse
Yes the progressbar stopped.
When looking at the file-dates in csc-folder, they're all from yesterday, so no updates done in there as far as I can see.
However, there is no errors on screen..so you are probably right about signature.
tys0n said:
Yes the progressbar stopped.
When looking at the file-dates in csc-folder, they're all from yesterday, so no updates done in there as far as I can see.
However, there is no errors on screen..so you are probably right about signature.
Click to expand...
Click to collapse
Thanks for your help, dude! The most important, that we have a package with correct signature and it works from factory recovery!
ladislav.heller said:
Thanks for your help, dude! The most important, that we have a package with correct signature and it works from factory recovery!
Click to expand...
Click to collapse
No problems. Just load it with some porn and give it to me, and we'll se how funny things get
tys0n said:
No problems. Just load it with some porn and give it to me, and we'll se how funny things get
Click to expand...
Click to collapse
Tried to modify original package (sec_csc.zip) following way:
- Removed system folder
- Replaced script to my own, which only prints some info about device
- Everything other untouched
Result in recovery:
"Signature verification failed"
What did I say?
Hmm, maybe it's not only a signature but also some checksum implementation