Can't update from rooted 4.0.3 to 4.0.3R1A - Sony Tablet S

Hi guys!
I've tried to upgrade my tablet from 4.0.3 to 4.0.3R1A as I did from 3.2.1 to 4.0.3, but I stuck on the first step menu 3-1. When I tried to start _hack_recovery.zip in recovery mode nothing happen in console of S.onyTablet.S tool and because of that I can't move forward
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

olegtord said:
Hi guys!
I've tried to upgrade my tablet from 4.0.3 to 4.0.3R1A as I did from 3.2.1 to 4.0.3, but I stuck on the first step menu 3-1. When I tried to start _hack_recovery.zip in recovery mode nothing happen in console of S.onyTablet.S tool and because of that I can't move forward
View attachment 1254796
Click to expand...
Click to collapse
Always be careful when updating a rooted device with any OTA updates. You are probably not likely to be able to update to 4.0.3R1A unless one of the developers on this forum mods the update package.
Spunky168
"Condi for president in 2012!!"

olegtord said:
Hi guys!
I've tried to upgrade my tablet from 4.0.3 to 4.0.3R1A as I did from 3.2.1 to 4.0.3, but I stuck on the first step menu 3-1. When I tried to start _hack_recovery.zip in recovery mode nothing happen in console of S.onyTablet.S tool and because of that I can't move forward
View attachment 1254796
Click to expand...
Click to collapse
This is the exact same position I'm in at the moment. I'm going to try using updated ADB drivers

blackadder666 said:
This is the exact same position I'm in at the moment. I'm going to try using updated ADB drivers
Click to expand...
Click to collapse
Adb 1.0.29.zip extracted from Android SDK attached here to post #1
http://forum.xda-developers.com/showthread.php?t=1828107
Stifilz

olegtord said:
Hi guys!
I've tried to upgrade my tablet from 4.0.3 to 4.0.3R1A as I did from 3.2.1 to 4.0.3, but I stuck on the first step menu 3-1. When I tried to start _hack_recovery.zip in recovery mode nothing happen in console of S.onyTablet.S tool and because of that I can't move forward
View attachment 1254796
Click to expand...
Click to collapse
At this point, reboot tablet s into recovery mode, choose 2) update, and choose "INSTALL.ZIP". Note the file name is not "_hack_recovery.zip", which is the most confusing part.
After running "install.zip" AiO will talk again.
@stifilz, my problem with the adb files was far before reaching this point. Now I'm wondering that was only me having the problem. Maybe I shouldn't update my installed SDK tools. A simple way to test is to run "5-reboot device" in AiO to check if the adb drivers/files work correctly.

jessicaat said:
At this point, reboot tablet s into recovery mode, choose 2) update, and choose "INSTALL.ZIP". Note the file name is not "_hack_recovery.zip", which is the most confusing part.
After running "install.zip" AiO will talk again.
@stifilz, my problem with the adb files was far before reaching this point. Now I'm wondering that was only me having the problem. Maybe I shouldn't update my installed SDK tools. A simple way to test is to run "5-reboot device" in AiO to check if the adb drivers/files work correctly.
Click to expand...
Click to collapse
Thanks for clearing that up jessiccat, remember i am doing this from memory as i cant root lol
Stifilz
Sent from my GT-S5830 using xda app-developers app

jessicaat said:
At this point, reboot tablet s into recovery mode, choose 2) update, and choose "INSTALL.ZIP". Note the file name is not "_hack_recovery.zip", which is the most confusing part.
After running "install.zip" AiO will talk again.
@stifilz, my problem with the adb files was far before reaching this point. Now I'm wondering that was only me having the problem. Maybe I shouldn't update my installed SDK tools. A simple way to test is to run "5-reboot device" in AiO to check if the adb drivers/files work correctly.
Click to expand...
Click to collapse
Strange that AiO can reboot my device and it does when i choose menu 3-1 but then it stopped. It looks like AiO is waiting for some response from device after launching install.zip (I've noticed that install.zip is launched automatically after reboot (AiO v4.1)).
When I updated device from 3.2.1 to 4.0.3 after choosing _hack_recovery.zip (aka install.zip) on AiO console (in Windows) was some movement and then you should choose signed-nbx03_042...zip.
I've replaced files from Adb 1.0.29.zip but have the same unlucky result

olegtord said:
Strange that AiO can reboot my device and it does when i choose menu 3-1 but then it stopped. It looks like AiO is waiting for some response from device after launching install.zip (I've noticed that install.zip is launched automatically after reboot (AiO v4.1)).
When I updated device from 3.2.1 to 4.0.3 after choosing _hack_recovery.zip (aka install.zip) on AiO console (in Windows) was some movement and then you should choose signed-nbx03_042...zip.
I've replaced files from Adb 1.0.29.zip but have the same unlucky result
Click to expand...
Click to collapse
I have the same problem. I updated my device also from 3.2.1 (german device) to 4.0.3 (us device). Then changed the region back to german with contis tool. Maybe it is a device problem?

my problem is that after i choose 3-1 the tab goes off (as it is supposed to do) but also does aio. is that normal? shall i just flash install.zip in the recovery and then what? aio can't take over because it is closed...
and: i changed my region to the us. shall i download the 4.0.3R1A for germany or for the us? shall i use these links? http://forum.xda-developers.com/showpost.php?p=26882207&postcount=1

k.bergmann2 said:
my problem is that after i choose 3-1 the tab goes off (as it is supposed to do) but also does aio. is that normal? shall i just flash install.zip in the recovery and then what? aio can't take over because it is closed...
and: i changed my region to the us. shall i download the 4.0.3R1A for germany or for the us? shall i use these links? http://forum.xda-developers.com/showpost.php?p=26882207&postcount=1
Click to expand...
Click to collapse
AiO 4.1 a little bit buggy, replace file in file folder by View attachment _submenu_custom_rom.7z it should help.
Concerning the second question: I upgraded without region changing and used 4.0.3 for my region.

k.bergmann2 said:
my problem is that after i choose 3-1 the tab goes off (as it is supposed to do) but also does aio. is that normal? shall i just flash install.zip in the recovery and then what? aio can't take over because it is closed...
and: i changed my region to the us. shall i download the 4.0.3R1A for germany or for the us? shall i use these links? http://forum.xda-developers.com/showpost.php?p=26882207&postcount=1
Click to expand...
Click to collapse
Is adb recoginizing tablet in recovery??
Check out FAQ thread in my signature link.
I have added some house keeping adb stuff.
Good luck
Stifilz

I'm still unable to install the latest update, having tried various things
I attach my build.prop file (hopefully attached correctly), not sure if it gives any clues as it means nothing to me
Thanks

blackadder666 said:
I'm still unable to install the latest update, having tried various things
I attach my build.prop file (hopefully attached correctly), not sure if it gives any clues as it means nothing to me
Thanks
Click to expand...
Click to collapse
Would be able to get more info from vendor.prop under vendor folder. You can save prop files as txt and upload that way. Prob easier.
Chur
Stifilz

stifilz said:
Would be able to get more info from vendor.prop under vendor folder. You can save prop files as txt and upload that way. Prob easier.
Chur
Stifilz
Click to expand...
Click to collapse
Thanks for taking the time to help
Vendor.prop file contains:
ro.sony.update.service_id=nbx03_003
ro.sony.sku.base=nbx03_003
ro.sony.build.id=TISU0017700
ro.sony.build.incremental=111104048

blackadder666 said:
Thanks for taking the time to help
Vendor.prop file contains:
ro.sony.update.service_id=nbx03_003
ro.sony.sku.base=nbx03_003
ro.sony.build.id=TISU0017700
ro.sony.build.incremental=111104048
Click to expand...
Click to collapse
This is link for r1a for UK
http://info.update.sony.net/ST003/nbx03_003/contents/0013/signed-nbx03_003-ota-120803004.zip
Are you planning on rooting?
I guess from your incremental you have root?
Chur
Stifilz

stifilz said:
This is link for r1a for UK
http://info.update.sony.net/ST003/nbx03_003/contents/0013/signed-nbx03_003-ota-120803004.zip
Are you planning on rooting?
I guess from your incremental you have root?
Chur
Stifilz
Click to expand...
Click to collapse
Already rooted with ICS, I just can't update to the new update r1a. AiO tool (v4) stops after telling me to reboot into recovery, updated ADB drivers, looked through this forum, in recovery I opt for install.zip then try the signed-nbx.zip, but still AiO tools stops. So posted my build.prop (and vendor.prop) to see if they showed up anything.
Must be doing something wrong but no idea what

blackadder666 said:
Already rooted with ICS, I just can't update to the new update r1a. AiO tool (v4) stops after telling me to reboot into recovery, updated ADB drivers, looked through this forum, in recovery I opt for install.zip then try the signed-nbx.zip, but still AiO tools stops. So posted my build.prop (and vendor.prop) to see if they showed up anything.
Must be doing something wrong but no idea what
Click to expand...
Click to collapse
Hmmm not too sure. All I can sugest is cat mcgowans tuit. You can find it post 2 of my faq link in signature. Follow to the letter and hopefully it will work, but thats all ive got
Good luck
Stifilz

blackadder666 said:
Already rooted with ICS, I just can't update to the new update r1a. AiO tool (v4) stops after telling me to reboot into recovery, updated ADB drivers, looked through this forum, in recovery I opt for install.zip then try the signed-nbx.zip, but still AiO tools stops. So posted my build.prop (and vendor.prop) to see if they showed up anything. Must be doing something wrong but no idea what
Click to expand...
Click to collapse
Condi's AiO v4.0 tool stalls at two points in the rooting process where it asks you to NOW ENTER RECOVERY MODE (at least it did for me). At both points, you just need to first update the system from the SD card using the install.zip file, then update the system from the SD card using the signed-nbx03.zip file during the first NOW ENTER RECOVERY MODE point, or the custom_update_signed.zip file during the second NOW ENTER RECOVERY MODE point. After starting the signed-nbx03.zip or custom_update_signed.zip update, WAIT! It may appear that the AiO tool has failed because it's not giving you any feedback, but it really has not failed. It takes several minutes (approximately 5) for the update to complete. Once the update has completed, AiO will spring back to life with additional prompts. I described my experience with what you are attempting HERE. The point you would be interested in reading is about half way through the post. Good luck.

olegtord said:
AiO 4.1 a little bit buggy, replace file in file folder by View attachment 1276079 it should help.
Concerning the second question: I upgraded without region changing and used 4.0.3 for my region.
Click to expand...
Click to collapse
that helped me. but now, when i am obliged to install the install.zip in the recovery, the tab tells me that the update was prohibitted as a result of checking version or base sku.
any clues?

Cat McGowan said:
Condi's AiO v4.0 tool stalls at two points in the rooting process where it asks you to NOW ENTER RECOVERY MODE (at least it did for me). At both points, you just need to first update the system from the SD card using the install.zip file, then update the system from the SD card using the signed-nbx03.zip file during the first NOW ENTER RECOVERY MODE point, or the custom_update_signed.zip file during the second NOW ENTER RECOVERY MODE point. After starting the signed-nbx03.zip or custom_update_signed.zip update, WAIT! It may appear that the AiO tool has failed because it's not giving you any feedback, but it really has not failed. It takes several minutes (approximately 5) for the update to complete. Once the update has completed, AiO will spring back to life with additional prompts. I described my experience with what you are attempting HERE. The point you would be interested in reading is about half way through the post. Good luck.
Click to expand...
Click to collapse
Finally got round to trying the above, still doesn't work. One thing however, when in recovery mode the tablet no longer comes up as an android device, it now shows as an unknown device. So looks like to loses the ADB driver. When I reboot the tablet normally it appears as an ADB device
Could that be the problem?
Thanks

Related

Pre root?

I rooted my UK tablet using the AiO tool, with the US version of ICS.
Now we have this update I'm unsure how to proceed. I'd like to update using the UK version.
So can someone point me in the right direction, I don't want to lose root.
blackadder666 said:
I rooted my UK tablet using the AiO tool, with the US version of ICS.
Now we have this update I'm unsure how to proceed. I'd like to update using the UK version.
So can someone point me in the right direction, I don't want to lose root.
Click to expand...
Click to collapse
Ok so you are currently US ICS???
Use region changer in AIO to change back to UK.
Then use AIO to preroot this:
UK
4.0.3 R1A WIFI ONLY
http://info.update.sony.net/ST003/nbx03_003/contents/0013/signed-nbx03_003-ota-120803004.zip
OR This
4.0.3 R1A WIFI + 3G
http://info.update.sony.net/ST003/nbx03_004/contents/0012/signed-nbx03_004-ota-120803061.zip
And install following instructions from AIO thread. If you do it right you will have new UK 4.0.3 R1A with root access.
Chur
Stifilz
stifilz said:
Ok so you are currently US ICS???
Use region changer in AIO to change back to UK.
Then use AIO to preroot this:
UK
And install following instructions from AIO thread. If you do it right you will have new UK 4.0.3 R1A with root access.
Chur
Stifilz
Click to expand...
Click to collapse
Right, having a problem with this. Changed the region to UK, seemed to work fine, tablet rebooted
Put the zip file (wifi only version) onto the SD card and ran the AiO tool. It went through some processes, it did say that the region needed to be changed. The tablet then shut down (didn't reboot) and the AiO tool closed. And that was that.
So what am I missing out here. Any help much appreciated
blackadder666 said:
Right, having a problem with this. Changed the region to UK, seemed to work fine, tablet rebooted
Put the zip file (wifi only version) onto the SD card and ran the AiO tool. It went through some processes, it did say that the region needed to be changed. The tablet then shut down (didn't reboot) and the AiO tool closed. And that was that.
So what am I missing out here. Any help much appreciated
Click to expand...
Click to collapse
Oh yeh v4.1 bit buggy like that. Try using v4.0 or even v3.4. You will need to turn updates off. It tells you when you open AIO so open v4.1 to read how to disable updates.
Good luck
Stifilz
Me again
Tried v3.4 and 4.0. First figured out how to stop it wanting to update.
V3.4 didn't seem to work, but v4.0 did at first. Went into menu 3 and chose option 1. This went through some processes and then to reboot into recovery mode. So far okay. Then installation failed (as it says on the AiO tool) but then the tool stops with 3 dots at the bottom. It offers no further instructions. The tablet asks whether to cancel and reboot or install from SD card.
So stuck again.
I tried watching the videos but for some reason I don't get any sound
Any other assistance would be appreciated and thanks so far.
An update if anyone can still help
When the tool creates the hack recovery file it seems to report some errors, something about not being able to verify googlegroups.com certificate but carries on. It then says it's pushing this file to the SD card and ask for the tablet to be rebooted into recovery mode. At this point the tools stops and goes no further.
I reboot into recovery it tries to install something but fails, so I go for the install from SD card but no hack recovery file there only an install.zip file. Reading the main discussion I see now that you install from this file. But it fails and I can go no further.
The main problem at this point is the AiO tool stop and hangs.
Currently trying v4, any ideas
Try using a newer adb version. It has helped others. Click faq link in signature adb 1.0.29.zip is attached there.
Stifilz
Sent from my GT-S5830 using xda app-developers app
blackadder666 said:
An update if anyone can still help
When the tool creates the hack recovery file it seems to report some errors, something about not being able to verify googlegroups.com certificate but carries on. It then says it's pushing this file to the SD card and ask for the tablet to be rebooted into recovery mode. At this point the tools stops and goes no further.
I reboot into recovery it tries to install something but fails, so I go for the install from SD card but no hack recovery file there only an install.zip file. Reading the main discussion I see now that you install from this file. But it fails and I can go no further.
The main problem at this point is the AiO tool stop and hangs.
Currently trying v4, any ideas
Click to expand...
Click to collapse
In decrypting the update file:
1-When asked to run _hack_recovery, run "install.zip". I guess there has been name confusions in all those updates.
2-"install.zip" will fail and then AiO will give you new directions. Now choose the firmware (signed-nbx03_001-ota-120803002.zip) or anything you have. You should copy it to SD card before the whole process.
Follow the instructions.
Another confusion in finally flashing the decrypted and signed update file:
When in recovery mode and AiO stops again,
1-run install.zip [it wouldn't fail], after this, AiO will simply tell you everything is done, delete or rename install.zip, and will exit. BUT NO ICS YET, and you're still in the recovery mode, on your own without further directions from AiO.
2-run _hack_recovery.zip [this one failed!!]
3-run the new install.zip [it was the old custom_updated_signed.zip]
Hope this helps.
jessicaat said:
In decrypting the update file:
1-When asked to run _hack_recovery, run "install.zip". I guess there has been name confusions in all those updates.
2-"install.zip" will fail and then AiO will give you new directions. Now choose the firmware (signed-nbx03_001-ota-120803002.zip) or anything you have. You should copy it to SD card before the whole process.
Follow the instructions.
Another confusion in finally flashing the decrypted and signed update file:
When in recovery mode and AiO stops again,
1-run install.zip [it wouldn't fail], after this, AiO will simply tell you everything is done, delete or rename install.zip, and will exit. BUT NO ICS YET, and you're still in the recovery mode, on your own without further directions from AiO.
2-run _hack_recovery.zip [this one failed!!]
3-run the new install.zip [it was the old custom_updated_signed.zip]
Hope this helps.
Click to expand...
Click to collapse
Thanks for taking the time to reply.
First I installed some new ADB files into the AiO tool 'files' folder and tried again
When the AiO tool asks to reboot into recovery mode I do that but the tool stops. I then ran the install.zip file and this fails (tablet stays in recovery) and the AiO tool does nothing further, just stops at the point telling me to reboot into recovery.
On your step 2 at the top, I run install.zip but get no new instructions from AiO
blackadder666 said:
Thanks for taking the time to reply.
First I installed some new ADB files into the AiO tool 'files' folder and tried again
When the AiO tool asks to reboot into recovery mode I do that but the tool stops. I then ran the install.zip file and this fails (tablet stays in recovery) and the AiO tool does nothing further, just stops at the point telling me to reboot into recovery.
On your step 2 at the top, I run install.zip but get no new instructions from AiO
Click to expand...
Click to collapse
hmmm... I vaguely remember in my case AiO said something like: now run the update, it is surely 100% safe, AiO won't allow anything to flash on your device, blah blah, and this was shown on the command window (not 100% sure here though). I used AiO v4.0, btw. Did you check other threads? I saw successful cases with different steps from what I went through. Good luck, anyway!

[Q] How to root N8000+(e1908_v77_jbl1)?

As title.pls. help.
yes.
tailangon2 said:
As title.pls. help.
Click to expand...
Click to collapse
Download boot pacthed from her *****http://yadi.sk/d/ZcZUWbkTirEO****. After download flashed it using flashtool. For root use UNLOCKROOT download from unlockroot.com
problem solved.tq.
i still unable to root the phone. and still cannot get the boot file patched.
how you do it?
could you share here step by step?
imanhunter said:
i still unable to root the phone. and still cannot get the boot file patched.
how you do it?
could you share here step by step?
Click to expand...
Click to collapse
Flash tool tutorial
http://colonelzap.blogspot.co.uk/search?q=n9770
fadhil3536 said:
Download boot pacthed from her *****[]//yadi.sk/d/ZcZUWbkTirEO****[l]. After download flashed it using flashtool. For root use UNLOCKROOT download from unlockroot.com
Click to expand...
Click to collapse
Help. downloaded the boot patch file..It is an img file. Flashtool only recognizes FTF file. Help newbie here.
afwong said:
Help. downloaded the boot patch file..It is an img file. Flashtool only recognizes FTF file. Help newbie here.
Click to expand...
Click to collapse
Managed to get it rooted with both SuperOneClick and UNLOCKROOT. Well, at least these 2 apps reported that the phone is successfully ROOTED. However, when check with RootChecker and Root Checker Basic from Google Play, both apps said the phone not rooted.
So which is which? Superuser is in the phone and Terminal Emulator accepted the "SU" command...
My N8000+ has JB 4.1
Hi,
I've just received Star N8000+ , and it seems it has JB 4.1 installed in it.
How can I root the device ?
Thks
texwiller said:
Hi,
I've just received Star N8000+ , and it seems it has JB 4.1 installed in it.
How can I root the device ?
Thks
Click to expand...
Click to collapse
Appreciate if you could do a ROM dump and share
mdashraf said:
Appreciate if you could do a ROM dump and share
Click to expand...
Click to collapse
If you can tell me how to dumb ...
I need info about rooting jb, anyone can help?
plz share
texwiller said:
Hi,
I've just received Star N8000+ , and it seems it has JB 4.1 installed in it.
How can I root the device ?
Thks
Click to expand...
Click to collapse
plz share the JB 4.1 rom ... :angel:
want to update my star n8000+
N8000+ with JB 4.1
texwiller said:
Hi,
I've just received Star N8000+ , and it seems it has JB 4.1 installed in it.
How can I root the device ?
Thks
Click to expand...
Click to collapse
Hi Textwiller,
Did you managed to root your N8000+ JB 4.1? Just curious.
I managed to root my N8000+ JB 4.0 set but not the set with JB 4.1.....
Have a very tough time to get the Star N8000 4.1.1 rootted
Can anyone help, please?
I have tried everything, from OneClickRoot, UnlockRoot, Root with Restore (V25) - and they all fail.
It seems like the filesystems cannot get remounted - even after busybox has been copied to the /data/.... directory.
Any ideas?
I want this rooted and install a "better recovery" - The one that is currently on the phone is in Chinese....
My current ROM is: e1908_v77_jbl1_9p017_6628 build date: 20121220
Thanks
bert269 said:
Can anyone help, please?
I have tried everything, from OneClickRoot, UnlockRoot, Root with Restore (V25) - and they all fail.
It seems like the filesystems cannot get remounted - even after busybox has been copied to the /data/.... directory.
Any ideas?
I want this rooted and install a "better recovery" - The one that is currently on the phone is in Chinese....
My current ROM is: e1908_v77_jbl1_9p017_6628 build date: 20121220
Thanks
Click to expand...
Click to collapse
Try this, http://forum.xda-developers.com/showpost.php?p=31126124&postcount=107
Mine is still on 4.0.1. I tried it on my second set on 4.1.1. It seems to be rooted. but some apps couldn't run reported it requires root....so.puzzled!
I also need to root my N8000+, i tried rooting it before but my ignorance of these chinese phones ended me up a few days of getting things back to normal, i do believe i need to flash patched boot file, then use rooting tool. correct? I have 4.1.1 please let me know if someone can successfully root this phone. also, what do you guys use for a front camera driver? thanks
i also have been looking to root the star n8000 mdk 6577 rom build i beleave is e1908_v77_jbl1_9p017_6628 i have been serching for a few moths now and nothing i cant get nowhere i cant read german nor chinse can we get some help with this phone please someone somewhere
So I guess we're not getting any help on this I have been surching hi and low and found nothing there so much for the mtk 6575 but nothing for the 77 so I'm not sure what's up with that I know some of the root programs I have tried says that it won't mout as read write so I don't know its kinda agervating but when u buy a phone u get what u pay for I mean it is a great phone fast but crappy reception I just wanna see if a u.s ROM would help the reception and speed if I new how to make a root program it do it or if someone made one it test it same with the Roms I have two phones Samsung s2 and the star note n8000+
Sent from my SGH-I777 using xda app-developers app
Use superone click
Finally got it rooted - here's how.
Hi all, my first post on xda-developers
I was really annoyed by the fact that no procedure seemed to work on my Star N8000+ (JB 4.1.1) e1908_v77_jbl1_9p017_6628 ORIGINAL STOCK ROM. I tried everything, from SuperOneClick to chinese rooting software... Nothing seemed to work. And since I have an untouched stock rom, and I had no wish to reflash the phone, I was left in the dark.
But, after lots of searching, experimenting and tons of trial-and-error with trying to understand scatter files and partitioning stuff, I finally managed to root my device with no need to use adb or to reflash the phone.
I'm posting a step-by-step guide for complete noobs like me. So here's the method I used (hope it works for all of you who aren't getting any luck with other methods, just like I was):
Download this file N8000+e1908_v77_jbl1_9p017_6628-Root.zip and copy it to your phone's sdcard;
Enter the phone's system recovery menu:
Turn phone OFF;
Hold Volume + key and turn phone ON. Keep holding Volume + until the below robot picture shows on your device. When it appears you can release the Volume + key;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Press the menu touch key (on the left of the phone's home button). A list of options will appear.
Using the Volume + or - key, highlight the "apply update from sdcard" option and press the phone's home button;
Using the Volume + or - key, find and highlight the N8000+e1908_v77_jbl1_9p017_6628-Root.zip file you've already saved on your sdcard (step 1). Once highlighted, press the phone's home button. Update will start;
When the update finishes, reboot your phone by using the Volume + or - key to select the "reboot system now" option and then press the phone's home button. Phone will reboot normally.
After all this, you should have root access to your phone
Files included on zip:
su v. 1.27
SuperSU v. 1.30
BusyBox v. 1.20.2
As always people mention when posting such procedures (and I think they are right), do it at your own risk. Although I feel and think that the above method is pretty safe and harmless, I will take no responsibility for any damages your phone may suffer. If you feel insecure about anything, just browse the sources on the zip package to check that the contents do not intend to harm your phone. I can assure you that I did all this just to try to help everybody who's out there, lost with rooting this wonderful device.
The above procedure worked flawlessly on my Star N8000+ (JB 4.1.1) e1908_v77_jbl1_9p017_6628 ORIGINAL STOCK ROM. If your phone version is different, it may or may not work. I think no harm could be done by trying (I guess the worst thing that could happen was the update to be refused to be applied due to certification incompatibility or wrong scatter/partition info). Once again, do it at your own risk.
Bonus: un-Root.
If you managed to successfully root your device using the above procedure, then you can undo it (unroot) by following the same above steps again, but instead of using the original zip file posted on step 1 use this one: N8000+e1908_v77_jbl1_9p017_6628-Root-UNINSTALL.zip

[Q] Bricked my Tablet S trying to force Jelly Bean, is there a fix?

I apologize if this is a redundant question, but I've got my Tablet S stuck at the SONY screen and can't seem to do much else. I'm looking for a) instructions to make it functional again, or b) instructions to confirm that it is totally bricked as I've seen in some forum posts that some situations are only repairable by sending in to Sony.
Story:
I finally decided to upgrade my Sony Tablet S to Jelly Bean (which in retrospect may not actually be possible ... ) and rooted it with AiO v6.4, after working around Windows 8 unsigned driver restrictions. That seemed to work fine, and so I moved on to Flasher v3.0. I admit I was of the understanding that the first menu was to choose the current version of the Tablet to update to JB, so I chose the WiFi only version r5a. It downloaded all of the parts and ran to near completion and then asked which hidden.img file I wanted to use. I was confused as I expected it to just continue through (one click, after all) and restart the tablet under jelly bean. Anyways, I chose option 1, it restarted, and was the same as it had been. I tried it again and when I was asked the question I chose the r1a option instead. Still, no noticeable change to the tablet. Then I had the bright idea that, "maybe I'm not choosing the present version but the final version to install". So, I started it again this time choosing option 1d (I believe, whichever one had the "JB!" next to it. It worked it's way through the downloads and flashing, but it erred when mounting a directory to /system, but it continued. Then it threw an error about not enough space. Eventually, it rebooted and got stuck on the SONY screen.
Considering my options, I worked my way into the recovery and tried to flash the various system, datapp, and hidden .img files with no success and then made the fatal decision (I'm guessing) to "Reset to factory settings". I tried flashing signed-nbx03_001-ota-120803002.zip and signed-nbx03_016-ota-120803071.zip and was hopeful each time that something was happening, but they ultimately failed with "Erohibit update as a result of checking version or base sku".
So, my thoughts are several fold: 1) while it was rooted, I de-rooted it by reseting it, 2) there is a regional mismatch of some sort, 3) I don't have the proper drivers to run ADB in recovery mode (if they exist), 4) it's toast. My understanding of how to get useful information off of the tablet is limited.
Long story short: Is there anything I can flash to get it back to a workable status? :fingers-crossed: Or have I done something horrible to my beloved tablet? :crying:
Tablet s doesn't have jelly bean.
Sent from my GT-S5830 using xda app-developers app
jumper62 said:
Tablet s doesn't have jelly bean.
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I think I realize that now. Posts like this across the internets are very misleading:
eandroidhowto.com/update-sony-tablet-s-to-android-jelly-bean-4-1-2-using-one-click-tool.html
android.gs/update-sony-tablet-s-jelly-bean-4-1-2-one-click-tool/
au.ibtimes.com/ articles/457545/20130416/upgrade-sony-tablet-s-android-4-1.htm#.UcgkxvnU-Hg
droidgator.com/update-sony-tablet-s-android-jelly-bean-412-one-click-tool/
Why would people post about something they haven't done themselves?
+1
I'm in the same situation.
viochemist said:
Why would people post about something they haven't done themselves?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hmm well this is unfortunate did you try the flasher by Condi? Should be able to flash both system partitions.
Sent from my LT28i using xda app-developers app
psxpetey said:
Hmm well this is unfortunate did you try the flasher by Condi? Should be able to flash both system partitions.
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
Doesn't it need tablet to boot properly to be able to work?
umutgultekin said:
Doesn't it need tablet to boot properly to be able to work?
Click to expand...
Click to collapse
I don't remember but mine was bricked well bootlooped like yours and I flashed using flasher. As long as it will connect to adb it should work dude
Sent from my LT28i using xda app-developers app
psxpetey said:
I don't remember but mine was bricked well bootlooped like yours and I flashed using flasher. As long as it will connect to adb it should work dude
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
ADB cannot connect on Sony logo Computer says it's a MTP USB Device and it can't install the drivers for it. I tried to force insall the "Composite ADB Android Interface" driver but it says it is not compatible with the device.
umutgultekin said:
ADB cannot connect on Sony logo Computer says it's a MTP USB Device and it can't install the drivers for it. I tried to force insall the "Composite ADB Android Interface" driver but it says it is not compatible with the device.
Click to expand...
Click to collapse
Hmm this is a pickle! I'm pretty sure Condi is the only one who can help you if you can't get adb connected in any way.
Sent from my LT28i using xda app-developers app
Success!
So, I've managed to regain functionality. I ultimately just had to go here:
forum.xda-developers.com/showthread.php?t=1687429
and grab the appropriate ROM for the region I purchased my tablet (in my case, the Canada R5a worked). I put that on an SD card, booted into Recovery, and "restored from SD card" or some such thing (option 2). I did lose root in the whole process, so I'll just do that again and leave it at that.
So, since there are apparently no custom ROMs for the Tablet S, what are some recommended tools that require root? Has anyone overclocked this thing?
viochemist said:
Success!
So, I've managed to regain functionality. I ultimately just had to go here:
forum.xda-developers.com/showthread.php?t=1687429
and grab the appropriate ROM for the region I purchased my tablet (in my case, the Canada R5a worked). I put that on an SD card, booted into Recovery, and "restored from SD card" or some such thing (option 2). I did lose root in the whole process, so I'll just do that again and leave it at that.
So, since there are apparently no custom ROMs for the Tablet S, what are some recommended tools that require root? Has anyone overclocked this thing?
Click to expand...
Click to collapse
I'm not that lucky, I tried every single file in that list, no luck.
viochemist said:
I apologize if this is a redundant question, but I've got my Tablet S stuck at the SONY screen and can't seem to do much else. I'm looking for a) instructions to make it functional again, or b) instructions to confirm that it is totally bricked as I've seen in some forum posts that some situations are only repairable by sending in to Sony.
Story:
I finally decided to upgrade my Sony Tablet S to Jelly Bean (which in retrospect may not actually be possible ... ) and rooted it with AiO v6.4, after working around Windows 8 unsigned driver restrictions. That seemed to work fine, and so I moved on to Flasher v3.0. I admit I was of the understanding that the first menu was to choose the current version of the Tablet to update to JB, so I chose the WiFi only version r5a. It downloaded all of the parts and ran to near completion and then asked which hidden.img file I wanted to use. I was confused as I expected it to just continue through (one click, after all) and restart the tablet under jelly bean. Anyways, I chose option 1, it restarted, and was the same as it had been. I tried it again and when I was asked the question I chose the r1a option instead. Still, no noticeable change to the tablet. Then I had the bright idea that, "maybe I'm not choosing the present version but the final version to install". So, I started it again this time choosing option 1d (I believe, whichever one had the "JB!" next to it. It worked it's way through the downloads and flashing, but it erred when mounting a directory to /system, but it continued. Then it threw an error about not enough space. Eventually, it rebooted and got stuck on the SONY screen.
Considering my options, I worked my way into the recovery and tried to flash the various system, datapp, and hidden .img files with no success and then made the fatal decision (I'm guessing) to "Reset to factory settings". I tried flashing signed-nbx03_001-ota-120803002.zip and signed-nbx03_016-ota-120803071.zip and was hopeful each time that something was happening, but they ultimately failed with "Erohibit update as a result of checking version or base sku".
So, my thoughts are several fold: 1) while it was rooted, I de-rooted it by reseting it, 2) there is a regional mismatch of some sort, 3) I don't have the proper drivers to run ADB in recovery mode (if they exist), 4) it's toast. My understanding of how to get useful information off of the tablet is limited.
Long story short: Is there anything I can flash to get it back to a workable status? :fingers-crossed: Or have I done something horrible to my beloved tablet? :crying:
Click to expand...
Click to collapse
Good to see you fixed it. A lot aren't as luck as you.
SHI* like this wouldn't happen if Sony just unlocked the bootloader for this!!! But we all know the VAIO team suck
stifilz said:
Good to see you fixed it. A lot aren't as luck as you.
SHI* like this wouldn't happen if Sony just unlocked the bootloader for this!!! But we all know the VAIO team suck
Click to expand...
Click to collapse
I think what probably saved me was that I had flashed the rooted R5A version using Flasher prior to the JB Xperia version. In so doing it loaded the bootloop recovery that allowed me to get it back to normal. That's my guess anyways. Afterwards, I restored root and added the other tweaks in AiO to the device. AiO can't seem to reboot properly, though. It tries, but it gets stuck at SONY each time. But it always restarts with a manual shutdown.
Personally, I love how Sony puts out a device the the Tablet S and stops supporting it less than a year after its release. Certainly not the kinda love they give Playstation.
viochemist said:
I think what probably saved me was that I had flashed the rooted R5A version using Flasher prior to the JB Xperia version. In so doing it loaded the bootloop recovery that allowed me to get it back to normal. That's my guess anyways. Afterwards, I restored root and added the other tweaks in AiO to the device. AiO can't seem to reboot properly, though. It tries, but it gets stuck at SONY each time. But it always restarts with a manual shutdown.
Personally, I love how Sony puts out a device the the Tablet S and stops supporting it less than a year after its release. Certainly not the kinda love they give Playstation.
Click to expand...
Click to collapse
Yeah sounds like flasher saved it with the rescue back-door. I'm guessing because the other partition was the proper one it allowed you to install again. What is happening is it is trying to boot JB and crashing and when you reboot it boot the other system being R5A. Mine does this.... after any install it crashes and then manual shutdown and it powers up into R5A. But mine is only after trying to flash so it is no that bad.
Hi, I have the same error message when trying to flash one of this firmware files.
My problem is that after boot I get the message "startmenu was closed" or similar.I was stupid and removed the "vendor" folder (because even with root apps deleted with titanum backup where restored after reboot). The missing vendor folder is probably the reason for all this trouble.
The tablet is a swiss 3g one.
I can connect and root/unroot with the aio tool.
Would be nice if somebody could help.
Thank you.

[Q&A] [ROOT] Root with Locked Bootloader for SGP621 using giefroot

Q&A for [ROOT] Root with Locked Bootloader for SGP621 using giefroot
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] Root with Locked Bootloader for SGP621 using giefroot. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Deleted
I'm at (24).
I requested the link to get an unlock code at developer.sonymobile.com. It's now been over 24 hours and i haven't get an email yet. Tried ist with a differnet email adress too.
How long does it take usally?
WiFi isssue after flashing D6603 rom
Hi,
I liked the idea of flashing D6603 rom on my SGP621 and rooting it..
I like my tablet now even more..
But the WiFi is not working for me now, only LTE/3G..
Also the camera not working, but I don't care because I'm using my mobile phone for taking pictures..
Is there any way to make WiFi working with D6603 rom?
Thanks...
russse said:
I'm at (24).
I requested the link to get an unlock code at developer.sonymobile.com. It's now been over 24 hours and i haven't get an email yet. Tried ist with a differnet email adress too.
How long does it take usally?
Click to expand...
Click to collapse
Normaly it takes not more than a few minutes. You can resend it at any time by requesting it again on sonymobile. If it still does not work you may need to get in touch with developer support on their website.
---------- Post added at 03:38 PM ---------- Previous post was at 03:33 PM ----------
kamal3383 said:
Hi,
I liked the idea of flashing D6603 rom on my SGP621 and rooting it..
I like my tablet now even more..
But the WiFi is not working for me now, only LTE/3G..
Also the camera not working, but I don't care because I'm using my mobile phone for taking pictures..
Is there any way to make WiFi working with D6603 rom?
Thanks...
Click to expand...
Click to collapse
No, you cannot. As there are other drivers used. If you want root and WiFi you need to follow the tutorial to the end and in the process unlock your bootloader and return to the SGP621 stock rom.
Hi lowtraxx
Thanks a lot for your great work!
I have the SGP611 version and have successfully followed rurie's guide to root the unit. Now i'm installing the rooted stock, but I'm stuck at your step 30. In step 28 I booted into fastboot and used Flashtool to execute the Z3TC-stock-twrp.img by pressing the button "Select system to Flash" and selecting the img-file, see pic.
I have tried to reboot by pressing "Reboot into fastboot mode (via Fastboot) to press volume down on purple light. However, the light never goes purple. It is blue, then swishes to red for an instance/glimpse. I have tried to hold down "volume down" and to press it many times but nothing works. Can you explain step 30 to 32 in detail, e.g. by using the buttons on the Flashtool - Fastboot toolbox (see pic)?
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I hope you did not flash the SGP621_23.0.1.A.0.167_CE.ftf onto your device but the one that is for the SGP611, because from your description it sounds like you are in a bootloop. I haven't used Flashtool to flash a kernel before, I am only using the command line. But my best guess would be that you need to click on Select Kernel to flash, select the Z3TC-stock-twrp.img and click on flash. Once that is done, you should reboot the device and wait until the Xperia logo shows up and the LED goes purple. If you now press volume down you get into recovery where you need to flash the RICDefeat.zip file you downloaded. If that does not work, download flashtool binary for windows, open a cmd prompt as Administrator, boot into fastboot mode and execute 'fastboot flash boot /path/to/the/Z3TC-stock-twrp.img' and then continue as outlined above.
lowtraxx said:
Hi,
I hope you did not flash the SGP621_23.0.1.A.0.167_CE.ftf onto your device but the one that is for the SGP611, because from your description it sounds like you are in a bootloop. I haven't used Flashtool to flash a kernel before, I am only using the command line. But my best guess would be that you need to click on Select Kernel to flash, select the Z3TC-stock-twrp.img and click on flash. Once that is done, you should reboot the device and wait until the Xperia logo shows up and the LED goes purple. If you now press volume down you get into recovery where you need to flash the RICDefeat.zip file you downloaded. If that does not work, download flashtool binary for windows, open a cmd prompt as Administrator, boot into fastboot mode and execute 'fastboot flash boot /path/to/the/Z3TC-stock-twrp.img' and then continue as outlined above.
Click to expand...
Click to collapse
Thanks for your reply. I have used the SGP611 firmware, so no problem.
I have flashed Z3TC-stock-twrp.img unto the unit using the button Select Kernal, but when I reboot the LED never goes purple - only blue and for a quick glimpe (~1-3 ms) red. If I boot the unit in normal mode (without fastboot mode or flash mode) it gets stuck at the Sony logo and cannot be shut down without pressing the small force-shut-down button next to the SD card. (It booted as SPG611 just fine before I flashed Z3TC-stock-twrp.img unto it - using the button Select Kernal.)
EDIT. Tried to download Z3TC-stock-twrp.img again and flash it using CMD in windows. Now I can access Recovery.
I'm progressing, but only slowly.
I'm at step 32 in the guide but every time I try to load/install RICDefeat it fails. Nothing happens when I try to issue 'adb sideload /path/to/RICDefeat.zip', so I have put the file on my external SD card. But when I press "install" - "external_sd" - "RICDefeat.zip" in the twrp Recovery it fails and an error comes: "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
How can I progress? Why do I have to install RICDefeat?
Without RICDefeat you are not able to mount the system partition writeable, so you have no real root. The error is odd though. Have you tried downloading the RICDefeat.zip again, maybe it was corrupted too (like the TWRP img)
lowtraxx said:
Without RICDefeat you are not able to mount the system partition writeable, so you have no real root. The error is odd though. Have you tried downloading the RICDefeat.zip again, maybe it was corrupted too (like the TWRP img)
Click to expand...
Click to collapse
Yes, I have tried downloading it again by clicking "View Raw". I have copied both to the SDcard, but both fails with same error.
Trying to use ADB Sideload and writing "adb devices" in Windows CMD from the folder C:\Users\USERNAME\AppData\Local\Android\sdk\platfo rm-tools just returns an empty list, and installing from SD fails with "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
Is it possible to go back some steps and try again - without bricking the device? E.g. to step 26? Is there an other place to down the advanced stock kernel?
centric dk said:
Yes, I have tried downloading it again by clicking "View Raw". I have copied both to the SDcard, but both fails with same error.
Trying to use ADB Sideload and writing "adb devices" in Windows CMD from the folder C:\Users\USERNAME\AppData\Local\Android\sdk\platfo rm-tools just returns an empty list, and installing from SD fails with "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
Is it possible to go back some steps and try again - without bricking the device? E.g. to step 26? Is there an other place to down the advanced stock kernel?
Click to expand...
Click to collapse
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
centric dk said:
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
Click to expand...
Click to collapse
Hi,
you will most likely be notified about OTA updates, but you should not take them, because they will not apply properly and most likely remove root again. Just wait for recovery flashable updates or build your own flashable update once the ftfs for the lollipop versions get available. If you want a clean installation without unlocking the bootloader again, just build a flashable zip of a clean ftf and flash that. If you want to send it in for repairs and the like, you can always flash a clean ftf with flashtool, but if you want to root it afterwards you need to unlock the bootloader again.
centric dk said:
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
Click to expand...
Click to collapse
I'm currently trying to flash RICDefeat from recovery and am getting the exact same error you reported. Do you know what exactly changed that allowed you to flash it successfully? Did you use the RAW version? Where did you put it, internal memory or SD?
Thanks!
Amplifiction said:
I'm currently trying to flash RICDefeat from recovery and am getting the exact same error you reported. Do you know what exactly changed that allowed you to flash it successfully? Did you use the RAW version? Where did you put it, internal memory or SD?
Thanks!
Click to expand...
Click to collapse
I did not change anything. The second time just went a lot faster as I had tried it before. I put RICdefeat on the SD card.
I also have a Z3 Compact (phone). That it a lot simpler to root and RICdefeat is not needed in that guide. Maybe you can get inspiration there?
centric dk said:
I did not change anything. The second time just went a lot faster as I had tried it before. I put RICdefeat on the SD card.
I also have a Z3 Compact (phone). That it a lot simpler to root and RICdefeat is not needed in that guide. Maybe you can get inspiration there?
Click to expand...
Click to collapse
I actually have been following a guide in the Z3C forums but ended up with partial root. RICD should be able to solve it, but gave me an arror. When I read you've been having similar problems, I thought I'd give it a go. Thanks anyway.
Amplifiction said:
I actually have been following a guide in the Z3C forums but ended up with partial root. RICD should be able to solve it, but gave me an arror. When I read you've been having similar problems, I thought I'd give it a go. Thanks anyway.
Click to expand...
Click to collapse
I followed this guide for Z3C (phone): http://forum.xda-developers.com/showpost.php?p=59627168&postcount=120
centric dk said:
I followed this guide for Z3C (phone): http://forum.xda-developers.com/showpost.php?p=59627168&postcount=120
Click to expand...
Click to collapse
Try this one;
http://forum.xda-developers.com/z3-...to-rooted-lollipop-locked-bootloader-t3083980
All works fine.
Hey,
today I got my Xperia X3CT and I followed this Guide to Root my Tablet: http://forum.xda-developers.com/z3-t...gp621-t3013534
(I rooted my LG G2 so I thought I should be able to Root my Tablet without any problems )
At Point 6 I started my Tablet, but somehow it is Stuck in a Bootloop. I am sure I did everything the way the Guide told me to, but somehow my Tablet is still in a Bootloop. How do I get out of it? I can turn the Device of by pressing the Power Button und the Volume Up Button.
Can someone please help?
EDIT: Got out of the Bootloop by flashing back to SGP621_23.0.1.A.0.167_CE.ftf. That was quite a shocker
I think the Problem was that I was at 23.1.A.0.690. Now that I am at 23.0.1.A.0.167 it should make any problems? Or could there be another Problem? Would be thankful for help
Emildeon said:
I think the Problem was that I was at 23.1.A.0.690.
Click to expand...
Click to collapse
That was the problem , you must follow the manual from kitkat (23.0.1.A.0.167) . I advise to use http://forum.xda-developers.com/z3-...to-rooted-lollipop-locked-bootloader-t3083980 ( No need to open the bootloader ). I made a guide in Spanish

[Updated] OTA update bricked your Nexus 9? -- Google Now Provide OTA images

Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Instructions for sideloading the OTA images.
Use the latest OTA image from the above link instead of using Android N OTA.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Posting this in a new thread so more people see it.
Get the Android N Preview OTA from here.
Google has updated the OTA zips again for nexus 9.
We've updated the OTA packages on https://developer.android.com/preview/download-ota.html. This should fix the issue with adb sideload failing at 47%. Please try again with the new packages.
Click to expand...
Click to collapse
Quote taken from here
Note: Removed Marshmallow from the tittle because it has been report to work for lollipop brick as well.
Try this if sideloading a marshmallow OTA doesn't work. See here. (Also see this link for instructions on sideloading.)
My Nexus 9 that I purchased when the device was originally put up for sale, got an OTA to 6.0.1 a few weeks back. I had not activated OEM Unlock in settings, no developer mode so I also hadn't activated USB Debugging. Well, that legit OTA ended up soft bricking my device. From that moment on, all it would ever do was show the booting screen until the battery died.
I tried manually sideloading Google's official update to 6.0.1 to the device, no go. It kept failing during the process.
I tried (knowing it likely wouldn't work) playing around with Nexus Root Toolkit to see if maybe there was some magic in there that would work, no go.
After two straight weeks of trying, I could not get an update pushed to the device and last night had resigned myself to sending it into HTC for repair... something that they weren't sure yet whether or not would incur a cost FOR ME to repair, even though in a completely stock and pristine device, the OTA update is what hosed it.
This morning, I heard that Google released sideloadable Android N images for all supported Nexus devices that some were saying would work in this scenario. (https://plus.google.com/u/0/+ArtemRussakovskii/posts/K4oUnQymMqG)
And what do you know, that totally worked. It sideloaded to my Nexus 9 and its working again.
tl;dr If you got an OTA for your Nexus and it ruined the device, and nothing else works, try to update it to N. Worked for me.
Thanks to Artem and Lenny Fudenna for the heads up.
Click to expand...
Click to collapse
dweissinger said:
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
Click to expand...
Click to collapse
Thanks pal. You saved my Nexus 9 LTE after 4 months of soft brick.
This is because the N OTA is a full-block/full image OTA zip that doesn't check the system partition of it's current state. It will just blindly flash. This kind of OTA image is perfect for recovering locked bootloader devices because it is signed by Google, unlike their factory images which are not signed and gets flashed like any other custom ROM.
I hope Google will provide full-block OTAs for major version releases in the future to resolve instances like this. With the requirement of enabling OEM unlocking in the new Nexus devices, full-image OTAs like these would be required to recover from failed standard OTA updates. I imagine this can happen with the monthly security update OTAs like it did with you. For those who never had an OTA fail, they never knew they were dodging bullets all those times.
For those concerned that stolen devices can be re-purposed this way, fear not. Even with a factory reset (no more user data), after flashing this OTA to get my Nexus 9 working again, it asked me to authenticate with the last owner's credentials before letting me in. So this should still deter thieves if they get a hold of a full-image-OTA thinking they can just flash a factory image with a locked bootloader. Much safer than leaving the bootloader unlocked or keeping OEM unlocking enabled.
Another reason why it's a good idea vs the old Full Factory Image method: will not delete user data.
I seriously hope the Google Android team consider releasing full-image OTAs in the future as standard practice - at least for major Android releases (no need to do this for all the minor updates - kind of like reinstalling Windows and getting all the security updates).
Creating a full-image OTA shouldn't add much to their workflow. The OTA for Lollipop to Marshmallow, for example, would have to be a full-image OTA anyways. The only thing the Android team needs to do is to disable version checking so it can be side loaded no matter what state the system partition is in.
Also, if a user wants to keep their data partition intact, a full-image OTA for the major release is important. If Google only released a single full-image OTA for the original OS the device released with (example: Lollipop), and someone needs to recover from a bad OTA update when they're already in Marshmallow, the original Lollipop build may not work with the new data partition schema.
Of course you'd be thinking "I'll just be happy the device is not bricked", but if you can also solve the "I'm glad I didn't lose any data" dilemma without much effort, why wouldn't you?
Well, I have discovered an exception to this solution .
Yesterday I set my Nexus 9 to update to the Android N Preview but when I returned I had the robot with the exclamation mark and my machine would not boot . I went through all the processes to try and get a factory image of 6.0.1 installed but had not preset my bootloader to allow an unlock.
I eventually found this article and duly downloaded the Android N developer preview factory image and then tried to ADB sideload but the process failed.
And I knew why it failed. It failed because it told me that the factory image I had downloaded from the correct URL was older than the version that had failed the OTA process.
Google does not give a version date for their Android N developer images so I had concluded that they must be up-to-date.
I now realise that their image was not up-to-date so I will now have to wait for Google to publish a newer version of their Developer N factory image that is the same age or newer than the failed OTA update from yesterday so that I can successfully ADB sideload the image without getting this error .
Just as well that I have some technical knowledge or I'd be sending my Nexus 9 back to HTC for something that was not my fault.
Overall - not impressed.
Herbiv4 said:
I eventually found this article and duly downloaded the Android N developer preview factory image and then tried to ADB sideload but the process failed.
Click to expand...
Click to collapse
You don't sideload a factory image, you sideload an "OTA zip" linked in the OP or again here
corkiejp said:
You don't sideload a factory image, you sideload an "OTA.zip" linked in the OP or again here
Click to expand...
Click to collapse
Just to clarify - I was up until 3:30am this morning having been through factory images, OTA zip files, the SDK for Android, the Wugfresh Nexus Root Kit, installing Linux Mint to try and get fastboot working when my Windows PC didn't seem to want to recognise my Nexus 9. I eventually sorted out the drivers included with the SDK because the Wugfresh drivers did not play nicely with my Nexus 9. Then I realised that as my bootloader was locked I could get nowhere with restoring 6.0.1. MMB29R.
After more googling I found this webpage and the link to the OTA .zip file plus the instructions of how to force the upgrade to the developer preview of Android N. Fantastic I thought.
I did in fact download the OTA .zip file from the right URL posted above and tried to sideload that file but it failed because the download was older than the files that Google sent to my Nexus 9 OTA earlier the previous afternoon.
So, as I said before, I now have to wait until Google to update their OTA .zip file to a version equal to or newer than the failed OTA file from yesterday.
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
So apologies for using the wrong phrase - it wasn't a factory image - it was an OTA .zip file and my tablet did try to send over the .zip file but it failed owing to it's age relative to the files already on my Nexus 9.
Hope that this clarifies everything.
The bottom line is - sideloading an OTA.zip file isn't as simple as it has been made out to be.
Herbiv4 said:
I did in fact download the OTA .zip file from the right URL and tried to sideload that file but it failed because the download was older than the files that Google sent to my Nexus 9 OTA.
Click to expand...
Click to collapse
Thanks for clarifying, Google must have sent you an Android N OTA which included the latest patch. Hopefully they will provide new OTA zips with Preview 2 in April. Which should hopefully resolve your problem. As i haven't seen a link for the latest patch OTA yet.
Herbiv4 said:
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
Click to expand...
Click to collapse
You could setup a change detection on that page. I use it on the factory images page all the time.
Herbiv4 said:
The bottom line is - sideloading an OTA.zip file isn't as simple as it has been made out to be.
Click to expand...
Click to collapse
I remind you of the title of this thread "Marshmallow OTA update bricked ..." which should make this process still valid for those devices. Your findings are worth posting on the Android N thread.
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
ignaciouy said:
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
Click to expand...
Click to collapse
MPA44I is Marshmallow Developer Preview. Is your device bricked that long? You should have RMA'd that while in Warranty.
Please check stock recovery to see if your device reports a different build version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
corkiejp said:
MPA44I is Marshmallow Developer Preview. Is your device bricked that long? You should have RMA'd that while in Warranty.
Please check stock recovery to see if your device reports a different build version.
Click to expand...
Click to collapse
You mean this?
That long because I tried everything, and nothing worked
I can't RMA because this was a gift in USA, and I live in Uruguay. So I can't send it to usa and get another back, I think I can't do that. + I can't afford it :/
ignaciouy said:
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
Click to expand...
Click to collapse
ignaciouy said:
That long because I tried everything, and nothing worked
I can't RMA because this was a gift in USA, and I live in Uruguay. So I can't send it to usa and get another back, I think I can't do that. + I can't afford it :/
Click to expand...
Click to collapse
What error did you get when trying to sideload the Android N zip?
corkiejp said:
What error did you get when trying to sideload the Android N zip?
Click to expand...
Click to collapse
First of all, thanks for replying, this is what I get
I checked the md5 of the file and it's the same of the google download page
ignaciouy said:
First of all, thanks for replying, this is what I get
I checked the md5 of the file and it's the same of the google download page
Click to expand...
Click to collapse
You maybe looking to perform a miracle here.
Other things to check: -
Your Cable
Versions of adb and fastboot on your PC (have you got the latest).
People have reported errors when using a faulty cable.
The stock recovery on your device maybe to old to apply the Android N OTA.
I tried 3 cables, and the same with all of them.
192:volantis-npc56x ignacio$ adb version
Android Debug Bridge version 1.0.32
Revision 09a0d98bebce-android
192:volantis-npc56x ignacio$
Isn't that the last one?
The stock recovery on your device maybe to old to apply the Android N OTA.
Click to expand...
Click to collapse
And what can I do? :-|||
Herbiv4 said:
So, as I said before, I now have to wait until Google to update their OTA .zip file to a version equal to or newer than the failed OTA file from yesterday.
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
Click to expand...
Click to collapse
corkiejp said:
You could setup a change detection on that page. I use it on the factory images page all the time.
Click to expand...
Click to collapse
I setup a change detection on the page and google has update the OTA zip for Nexus 9.
Nexus 9
"volantis" volantis-ota-NPC56X-2785955f.zip
MD5: 36d813350fd660ab751a434782f5523f
SHA-1: 2785955fd77310106d2fa9f02f93b595d77b8e72
Nexus 9G
"volantisg" volantisg-ota-NPC56X-d93e161c.zip
MD5: 1fb7d83cd065a962dbed49e72db97dc4
SHA-1: d93e161c15503dc641b654f6ef4c1611222bc9fd
Click to expand...
Click to collapse
corkiejp said:
I setup a change detection on the page and google has update the OTA zip for Nexus 9.
Click to expand...
Click to collapse
Hello there Corkiejp, thanks very much for doing this. I downloaded this new OTA .zip file last night and used adb sideload as instructed. The transfer got to 47% on the PC side and on the Nexus 9 side the installation started briefly before suddenly rebooting so the install fails. When booting to recovery it shows the very latest version has registered but as the install has failed it cannot boot. I have done a factory reset and tried the process again but got the same result.
I'll have to wait for the next update and I'll try process again.
Otherwise, I'll have to ask HTC to fix this for me.
Herbiv4 said:
Hello there Corkiejp, thanks very much for doing this. I downloaded this new OTA .zip file last night and used adb sideload as instructed. The transfer got to 47% on the PC side and on the Nexus 9 side the installation started briefly before suddenly rebooting so the install fails. When booting to recovery it shows the very latest version has registered but as the install has failed it cannot boot. I have done a factory reset and tried the process again but got the same result.
I'll have to wait for the next update and I'll try process again.
Otherwise, I'll have to ask HTC to fix this for me.
Click to expand...
Click to collapse
Get the recovery logs to see where it failed and post the results in this thread.
Hello, good evening I'm having the same Issue that herbiV4; it gets till 47% then reboot and shows the android in its back and *ningun comando" (No commands) if I try to reboot, it send me once again to the recovery menu like... It doesn't have a OS? Even when it "updated" the recovery menu I really REALLY need help, I already contacted with HTC and the told me to send it but I'm from Venezuela so that's absolutely impossible for me, the Nexus has been bricked for 4 months ;---;
This is what the ADB shows me in the pc.
And this is what the tablet shows exactly after it reboot post "No error" from adb
This is the Last log, I truly dont get the "error" thingy :/
Help :crying:
If your getting error's from this process, it maybe helpful to google, to report your recovery logs to this thread.
If your device is in this state we would really appreciate logs from more devices.
1) Power off your tablet.
2) Press and hold the Volume Down button. Then, while holding Volume Down, also press and hold the Power button until the tablet turns on. (Fastboot mode)
3) Press the Volume Down button once to highlight "Recovery." Press the Power button to start in recovery mode. You'll see an image of an Android robot with a red exclamation mark. (Recover mode)
4) Press and hold down the Power button. Then, while holding Power, press and release the Volume Up button once.
5) Use the Volume Up and Volume Down buttons to navigate to "View recovery logs", and press the Power button to select.
6) There might be multiple log files. Start from "/cache/recovery/last_log" to view the log contents. Look for lines like "Finding update package...", "Opening update package...", etc. These lines indicate that the log file is for the OTA.
7) Navigate towards the end of the log using the volume buttons and look for any errors.
We are specifically interested in knowing if the bricked devices show "fsync failed: I/O error". We are exploring options to recover devices with locked bootloaders that are bricked. We'll post an update here.
Click to expand...
Click to collapse
This process has been reported to work on a bricked lollipop device.
This process has been reported to work on a bricked lollipop device.
defmetal96 said:
Hi I know this is a long shot but do you know how to fix this ^^ abort error?
Currently stuck on LRX22L but it is not booting as the OTA update to LRX22L failed for no apparent reason, foolishly my bootloader is still locked and the OEM unlock option is not checked.
is there any salvation?
Click to expand...
Click to collapse
defmetal96 said:
Sideloaded the N preview and that finally did the trick.
For anyone else with this issue I think the N preview is the only escape at present if your tablet is locked and refusing OTA updates
Click to expand...
Click to collapse

Categories

Resources