Related
When I try to reinstall the firmware it will not work. I get a message update failed: (1). This is done in the recovery section. I have put the latest firmware in, but nothing happens other then the error message. When I turn on the Archos it just goes straight to the Archos A70S Recovery screen. I have totally reformatted the device several times. Any thoughts on this board? Thanks.
Aaron
Try to format the device and then install the firmware, also, make sure to have the right firmware so the archos stock .aos file and not the SDE firmware .aos file
have you tried redownloading the archos firmware again? maybe the download got corrupted?
Also try running the repair tools under recovery: specifically Check Disk?
do you have a (1) at the end of the aos file? "sdqsqdfkqsdomij(1).aos" like Firefox do, i had the same error like that
Thanks...but I think I have tried it all...no luck
Try using a different browser, like IE to download it.
I've got the same thing going on. Was trying to re-partition the app space and something didn't work for the 4th time. So I removed Android and the SDE and now I can't get it to boot. My problem is that I was running windows, not sure what you were using, and I changed the recovery location's format. So every time I go to load the file the archos will format the partition then windows says it will not read and formats the partition... I move the file and try to start the reload only to fail.
I'm going to run ADB hopefully tomorrow. I hardly know what I'm doing, but don't really care if I break it! Just playing around but if anyone has any ideas let me know!
If you removed sde and android, there is nothing to boot from.
You then have to go into the recovery, format the device from there and then restore the orginal Android by transfering the aos file from arcos.
Yeah, I might have done that 10 times. That is when the archos reformats itself to something and then windows can't read the drive.
After you have transfered the AOS File to the device and it installs the Archos Android
it reformats the device to something?
I think that the archos is formatting to ext3 but windows can't read it, so windows then formats to whatever and I move the file, then hit ok on archos and you get failed message.
I know that AOS files work because I have already used them once.
If any of you guys give up on trying to get life into your bricked gen8 devices, then shoot me a message... I might be interested in buying the device from you.
Have you tried tried to fully charge it before installing? I had that same problem and it got fixed by fully charging the device first.
Full charge and plugged in as we speak.
You now have 133 posts on xda and still are not able to post a complete detailed description of what you are doing and what is happening?
How should we help?
My suggestion if you get an Error, tell us what error exactly, as my crystal ball is on repair atm.
Ha! 393 posts and your only kind of a ****? Thanks!
All kidding aside It's not easy to describe whats going on, and I wasn't trying to hijack this thread but I think the original poster is way gone. I was only trying to say I had the same problem and was going to try a few things to get it working again, but this was only yesterday and I have not had luck. I never really even asked for help but appreciate everyones input.
So... Let me start again!
Archos 101.
Long ago I had Urik Droid 1.0 installed but it had since been removed. Before I messed everything up i had the latest Archos update and rooted. I was trying to create a large partition for apps and had just edited the init.rc and rebooted. Somewhere here I messed up! Boot loops start and I'm into recovery.
Recovery shows everything normal, but I'm unable to update archos via AOS file. So I totally reformat and remove SDE in an attempt to just start fresh. This is not the case and I figured it wouldn't be.
As I described before, using windows, in archos recovery this is what is displayed.
Archos A101IT Recovery
Would you like to recover system?
NO
REBOOT
UPDATE FIRMWARE
REPAIR SYSTEM
FORMAT SYSTEM
If you select updated firmware the archos will reformat to ext3. It then says USB connection: Press OK to disconnect. Windows then says that it is unable to use the disk and asks to re-format. I did, because I don't think I can do anything else, moved the AOS file over and hit ok. Update failed (1).
So today I installed linux in an attempt to move ext3 to ext3. I did get the file transfered and my archos even said plug into dc power. I did and waited... Update Failed (206). Not sure what this one is!
And that's really all I know. I can't even get the last thing I described to come up again. But I have all week on vacation.
And lastly I would like to thank you for the help
And I just got the AOS to install! Formated repair to Vfat, used repair option and moved AOS into archos. For whatever reason this time it worked. Rebooted and android just started up. Don't know if everything works yet but we will see!
Funny, you do the mistake and call others names.
fzelle said:
You now have 133 posts on xda and still are not able to post a complete detailed description of what you are doing and what is happening?
How should we help?
My suggestion if you get an Error, tell us what error exactly, as my crystal ball is on repair atm.
Click to expand...
Click to collapse
Let me make this clear...
I was kidding. Take a deep breath, relax and please try to help someone else if that is what you are on here to do.
I'm pretty sure what you said to me was worst then my little joke. It was hardly clever and I'm ok with it as it did make me laugh a little.
I didn't ask for your help.
I didn't need your help
You didn't help.
And I'm ok with it even if you are not.
I'm going fishing now. Good day everyone.
No, it was exactly what you needed, as before my message you didn't tell us what was happening on your side.
Please read what you have posted before and check yourself if you would be able to get any sence from that.
It is funny how some people handle kritik.
Hi all,
First off, just want to say thanks to all of the hardworking devs out there that put a lot of time and effort into these projects. You guys are really awesome!
Secondly, I tried to post this as a reply in the developer's forum, but didn't have enough posts to qualify.
That all being said, I followed all of the instructions in Indirect's post here, but can't get the Nook Tablet to bring up recovery mode when I reboot. It just continues to load the standard B&N image. I even tried a factory reset to see if that would work, but same problem. I verified that the files on the micro-SD card match those as shown in Albert's excellent video here. The device is still running 1.4.0.
Any assistance is greatly appreciated!
No luck here either...I tried the root while watching Albert's You Tube video at the same time. I think the significant thing is that my screen displays something like:
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
Installation Complete!
Install from sdcard complete.
Whereas the screen in the video shows:
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
Installing GApps 29110878
For Android 2.3.5 Customized for the nook tablet
Mounting data...
Extracting files to data...
Unmounting data...
Install complete. Enjoy!
Installation Complete!
So clearly my install seems to silently abort somewhere in the middle...
Any insight or advice would be appreciated!
Removed...
~ Veronica
Sent from XDA premium using my Nook Tablet
Beatbox,
Just re-reading your post I think I got farther than you, but also got stuck on your issue earlier. If you keep the Nook plugged into the PC via the USB cable during the power on, the Nook will boot into the recovery mode - that at least was what got me past your issue.
It's not about Rooting OR recovery. It's about the fact that this method is still being worked on. Indirect has been making modifications to the various files and it is my opinion that the file used in Albert's video is NOT the same file that would be downloaded if you went and obtained it right now.
I would wait this out until Indirect writes an updated post explaining that the method is finalized.
If this is not an option the original root method works perfectly.
Land - when you say "original root method" are you talking about something that predates Albert's solution?
jearley9 said:
Land - when you say "original root method" are you talking about something that predates Albert's solution?
Click to expand...
Click to collapse
See this Thread
If you are running 1.4.1 you will need to downgrade first.
See Here
jearley9 said:
Beatbox,
Just re-reading your post I think I got farther than you, but also got stuck on your issue earlier. If you keep the Nook plugged into the PC via the USB cable during the power on, the Nook will boot into the recovery mode - that at least was what got me past your issue.
Click to expand...
Click to collapse
Cool jearley9, this did indeed work for me and I was able to load the image. Problem now is that I always end up at the normal B&N Setup screen. Were you able to get past that part?
And thanks to all the other thread participants. I know it takes time to work these things out, so no biggie. We all get a little too excited and impatient with things like these sometimes.
Thanks - looking it over now...
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
Beat,
Does your screen match my screen or the one in Albert's video? If it matches then you and I have the same problem. If not then you have something different going on...
jearley9 said:
Thanks - looking it over now...
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
Beat,
Does your screen match my screen or the one in Albert's video? If it matches then you and I have the same problem. If not then you have something different going on...
Click to expand...
Click to collapse
Definitely matches yours. Just didn't know if you got further than I did after rebooting.
Land Master said:
See this Thread
If you are running 1.4.1 you will need to downgrade first.
See Here
Click to expand...
Click to collapse
Just wanted to provide an update. I attempted the instructions from the original rooting thread (my nook tablet doesn't have 1.4.1 yet, so didn't need to downgrade). When I ran the batch file to root, it detected that the device was already rooted - which I quote from the script, "Is bothersome."
Okay, so i think my device is half-rooted somehow. Just can't get the new home screen that I'm seeing on all the videos. I'll keep you guys updated with my further troubleshooting attempts.
Beat, you and I are at least synchronized - I too tried the original root method, and I had the same exact problem as you describe... a message saying "already rooted". I did a system reset right before I tried the root, so I don't see how it could be "already rooted".
I just purchased my Nook yesterday. I am wondering if there are newer units (mine included) that are more resistant to being rooted?
I'm having the same issue, but I can use the search function to determine that apps WERE installed (and will execute properly). I believe that Indirect has removed ADW launcher and Homecatcher from the zip we're suppossed to drop onto the SD Card. My guess is that we're waiting for him to come up with a solution to the "Market not showing up in launcher" issue.
Can someone confirm this?
Well any other tactics I've tried have been to no avail, so I'll just be patient and wait for Indirect to address it. I'm sure he has enough on his plate without us bugging him.
Many thanks to him again for even working on something like this.
Edit:
Okay, for some reason I missed Albert Wertz's helpful Youtube comment:
Please Vote this comment up so everyone else can read it among all the others. Indirect is making some changes to the script, if you dont get adw to launch right after the first reboot from root, you may have to download it manually from the market. You can use the N button menu search function to pull up market by typing M in the search. You can launcher it from here. Until the bugs are worked out, you may only be able to install from market, sideloading may still be an issue. Indirect is fixin
Click to expand...
Click to collapse
I did this and have no problem bringing up the Android Market now. Just installed an app successfully. Not sure where it lives though. I could only seem to launch it from the Recently Downloaded icon at the bottom bar.
Edit 2:
Okay, just restarted after installing the ADW and now it prompted me to start with it. Only issue I have now is if I hit the N button, it reverts back to the original Barnes & Noble homescreen and I have to reboot to launch ADW again.
I got pretty much to the same place - I downloaded HomeCatcher but that seems to be non-functional - Looks like the Nook home screen is winning this round...
jearley9 said:
Beat, you and I are at least synchronized - I too tried the original root method, and I had the same exact problem as you describe... a message saying "already rooted". I did a system reset right before I tried the root, so I don't see how it could be "already rooted".
I just purchased my Nook yesterday. I am wondering if there are newer units (mine included) that are more resistant to being rooted?
Click to expand...
Click to collapse
To truly "reset" the system run the downgrade I linked previously EVEN IF you are on 1.4.0. After that it will be just like you took the NT out of the box. Then run the Indirect Root Batch and the "you are already rooted" should be gone. I would hope so anyway
Land,
I did the press and hold 9 times and got back to factory state.
Also, I tried Brianf21's files and I got the same problem as you. If I try to open Update.Zip from Windows it gives me "Please insert last disk of a multi-volume set...". I would guess that the zip file is malformed or incomplete, but that's just a guess...
-jearley
jearley9 said:
Land,
I did the press and hold 9 times and got back to factory state.
Also, I tried Brianf21's files and I got the same problem as you. If I try to open Update.Zip from Windows it gives me "Please insert last disk of a multi-volume set...". I would guess that the zip file is malformed or incomplete, but that's just a guess...
-jearley
Click to expand...
Click to collapse
I copied this post to the Development Thread in my recent reply to Brianf21. It is conceivable at this point that you and I are the only ones that have tried this. lol
Please put information regarding future attempts in that thread to help him troubleshoot.
Glad to see that you were able to reset. I don't believe it will be necessary again if Brian fixes the issue. To my knowledge simply entering CWM using his image had NO affect on my NT.
Land,
Sorry I can't comply with your request - the forum software won't let me post in the development area due to my "newness" - I am 53 years old and have 30 years of software/firmware development experience, but to this forum I am a "newbie"
jearley
jearley9 said:
Land,
Sorry I can't comply with your request - the forum software won't let me post in the development area due to my "newness" - I am 53 years old and have 30 years of software/firmware development experience, but to this forum I am a "newbie"
jearley
Click to expand...
Click to collapse
Alrighty then.... I don't know if I should laugh or cry. You can't even "post" in the Dev section? I wonder how many posts you need. Seems a little extreme to me but you will get there soon enough I guess.
In the meantime I'll make sure that your comments are known. Thanks!
Can anyone help me get my TABLET S (non-XPERIA) back to the pre-Revision 5 release of 4.0.3?
I HATE, HATE, HATE R5. Took away so many things that I was using, and I want to go back.
I already called SONY and was told I can't go back. I told the guy...I will find a way - and hung up.
I am sure it can be done....just need to find the software and the steps to do it.
bearhntr
bearhntr said:
Can anyone help me get my TABLET S (non-XPERIA) back to the pre-Revision 5 release of 4.0.3?
I HATE, HATE, HATE R5. Took away so many things that I was using, and I want to go back.
I already called SONY and was told I can't go back. I told the guy...I will find a way - and hung up.
I am sure it can be done....just need to find the software and the steps to do it.
bearhntr
Click to expand...
Click to collapse
Simple as. Change vendor/vendor.prop incremental to a lower number and flash an older update.zip
Or use AIO and install rescue back door, boot loop protection.
Manually flash either 120803002 or 120410004.zip
Done
stifilz said:
Simple as. Change vendor/vendor.prop incremental to a lower number and flash an older update.zip
Or use AIO and install rescue back door, boot loop protection.
Manually flash either 120803002 or 120410004.zip
Done
Click to expand...
Click to collapse
While I appreciate the reply, which gives you credit for a post (yes - I know how these forums work), I asked for the steps and software. I know it can be done, as I did it to my DroidX phone and had someone give me step by step instructions (rather directed me to a post he had done a year before with had everything I needed in one place).
I am talking real steps 1)...2)...3)... and links to the files. Not just some partial filenname which sends me on a goose chase.
Someone in another forum directed me to download signed-nbx03_001-ota-120410004.zip but then gave me nothing more - like do I put it on an SD CARD and do something with it. How do I get into BootLoader mode so that I can apply it, etc. I have already paid for a couple of apps that I used when I did my phone - I am sure that they might work for my tablet as well.
I am no idiot, do not need Crayola drawings, but at least 6th grade steps and locations on how to do this.
I cannot believe that for $350.00 that I just paid for the table SONY would tell me you can't do it - nor do they offer a manner to go back to the previous level (1 step) if you do not like the ROM that got installed.
4.0.3 (r5) is for the birds....takes away some of the best features of the reason I bought the SONY Tablet S over something else.
While I do appreciate, and do thank/reward those that help me - I think I need a little more than a simple 3 line response.
Curtis
bearhntr said:
While I appreciate the reply, which gives you credit for a post (yes - I know how these forums work), I asked for the steps and software. I know it can be done, as I did it to my DroidX phone and had someone give me step by step instructions (rather directed me to a post he had done a year before with had everything I needed in one place).
I am talking real steps 1)...2)...3)... and links to the files. Not just some partial filenname which sends me on a goose chase.
Someone in another forum directed me to download signed-nbx03_001-ota-120410004.zip but then gave me nothing more - like do I put it on an SD CARD and do something with it. How do I get into BootLoader mode so that I can apply it, etc. I have already paid for a couple of apps that I used when I did my phone - I am sure that they might work for my tablet as well.
I am no idiot, do not need Crayola drawings, but at least 6th grade steps and locations on how to do this.
I cannot believe that for $350.00 that I just paid for the table SONY would tell me you can't do it - nor do they offer a manner to go back to the previous level (1 step) if you do not like the ROM that got installed.
4.0.3 (r5) is for the birds....takes away some of the best features of the reason I bought the SONY Tablet S over something else.
While I do appreciate, and do thank/reward those that help me - I think I need a little more than a simple 3 line response.
Curtis
Click to expand...
Click to collapse
If you KNEW these forums you would know that we do not take kindly to those who do not use the SEARCH function. It is there so we don't have to repeat ourselves over and over again.
None the less.
If you can't manage this then take it in to Sony saying that you are having issues with the camera (they will restore it to original 3.2 software)
Step One
Root your device.
See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step Two
Use AIO to 'Install "rescue-backdoor" [anti-bootloop protection].'
First you want to download, then extract to a folder, then double-click on S.onyTablet.S.bat, this will open a menu, enter '4' then press enter then enter '1' and press enter again. MAGIC, you have now decreased your incremental, well done.
Step 3
See my Update Links NOTE: ALSO IN MY SIGNATURE AND HAS BEEN FOR A LONG TIME, others had no problem with it
Find the update you require to flash, you want signed-nbx03_001-ota-120803002.zip or for you highness LINK
Step 4
Copy signed-nbx03_001-ota-120803002.zip to your SD card. Google how to if you don't know
Step 5
Put SD card back into tablet and boot into recovery. See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step 6
Leave tablet to boot into R1A
Step 7
Be happy and click the fricken Thanks button.
P.S this is not hard stuff
Stifilz,
Thank you so very much for the long post. I was going cross-eyed looking for something like that...surprised that no-one has STICKY'd that one.
So I checked out #1 - followed the directions in FAQ to put the ADB path into the my DOS PATH statement (ahhhhh. the good old days - DOS). I can go to the DOS prompt and type 'adb' from any directory and it will bring up the ADB menu - hence it is working.
So I went to the task manager and verified that ADB.EXE was not listed. I typed ADB DEVICES (lower case) and it gave me the following:
C:\Windows\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Windows\system32>:
I made sure that the SONY TABLET is seen - I unplugged from the computer and re-plugged, Windows bonks and wants to know if I want to browse the device. I have made sure the USB DEBUGGING is enabled on the device (before I connect it - had that problem with my DROIDX). Still the ADB 0.29 is not seeing the SONY TABLET S.
Any Ideas why?
When I try running the RUNME.BAT file I get the following:
D:\ROOT_W_RESTORE>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (02.10.2012) v13 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 2
Special mode:
1) Root
2) Rollback
Make a choice: 1
Tablet S mode enabled!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and it just sits there...left it for 20 minutes while I was making dinner. Should I have the power plugged in at the same time? Do I need to enable the STAY AWAKE setting?
Your guidance is again requested.
Please ignore my previous response. I really am not an ass - I was getting frustrated during my 2+ hours search not finding a message such as yours with the steps laid out like that - without making you bounce from one post to another - to another, it was like a scavenger hunt.
Again accept my thanks and my apologies.
Have you installed the drivers http://forum.xda-developers.com/showthread.php?t=1488822
Sent from my Desire S using xda app-developers app
gordo79 said:
Have you installed the drivers http://forum.xda-developers.com/showthread.php?t=1488822
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Hey...THANKS. not sure why I did not catch that the tablet did not show as adb device, as I had to do the same thing when I rooted my DroidX...I guess I assumed that it would do it from that install.
Again thanks...now lets see if I can get the 4.0.3 (pre-R5) back on the tablet.
SO FAR SO GOOD. Weird that the SD card does not show from the tablet with it in the SD slot on the tablet like it does on my DROIDX. You can copy files to and from the SD Card in the phone without taking it out.
See...you can teach an old bear new tricks.
Stifilz,
On last step of your instructions...have one question.
What is the difference between this signed-nbx03_001-ota-120803002.zip that you mention and the signed-nbx03_001-ota-120410004.zip that I also downloaded from another forum message I was reading?
Thanks
bearhntr said:
Stifilz,
On last step of your instructions...have one question.
What is the difference between this signed-nbx03_001-ota-120803002.zip that you mention and the signed-nbx03_001-ota-120410004.zip that I also downloaded from another forum message I was reading?
Thanks
Click to expand...
Click to collapse
120803 is 2012-Aug-03 which is ICS R1A
120410 is 2012-Apr-10 which is ICS original. R1A is suposedly better
Stifilz
stifilz said:
120803 is 2012-Aug-03 which is ICS R1A
120410 is 2012-Apr-10 which is ICS original. R1A is suposedly better
Stifilz
Click to expand...
Click to collapse
stifilz,
Well I was successful...but it killed my ROOT. I got to playing with the new load, and it looks to have kept a bunch of my apps and some settings, but some of the apps do not work well.
I take it that if I go though the process again and choose to NOT RESTORE, it will put it back to OUT OF BOX configuration?
I do not have a lot of customizations that I will have a problem re-doing to get it back to O-O-B configuration. All of my apps can be pulled back off GOOGLE PLAY. Learning that is advantageous to have a GOOGLE PLAY account for each device (he he).
There are a lot of apps that I have noticed on GOOGLE PLAY that say not compatible with my device. Any known reason why? I figured that open source was open source.
I saw in the AIO that you can change the device type of your tablet to something else. Have you ever tried that? Does it seem to work?
I have also read that the UK models have a slot for a SIM card. Do you know if the US models have it to - just maybe inside and inaccessible?
I am loving the tablet....but find that now that I am back on the 4.0.3 my media files on my HTPC will not play. I find this wierd. The 4.0.3 update - according to the SONY site, says it improves the H.264 file playing...and nothing is mentioned about any changes in the R5 update.
Also one thing I noticed about the R5 load was it would sometimes just turn OFF the tablet. No reason or rhyme to it. Ever hear of that?
I may wind up going back up - if I cannot get them to play...have yet to try copying one to the SD card and playing it. But all of them used to play before I went back down.
Been looking into codecs too - but most of the processing of streamed DLNA stuff is done on the host machine [ putting on the Sherlock Holmes outfit again ]
Thank again for all your insight.
bearhntr said:
stifilz,
Well I was successful...but it killed my ROOT. I got to playing with the new load, and it looks to have kept a bunch of my apps and some settings, but some of the apps do not work well.
I take it that if I go though the process again and choose to NOT RESTORE, it will put it back to OUT OF BOX configuration?
I do not have a lot of customizations that I will have a problem re-doing to get it back to O-O-B configuration. All of my apps can be pulled back off GOOGLE PLAY. Learning that is advantageous to have a GOOGLE PLAY account for each device (he he).
There are a lot of apps that I have noticed on GOOGLE PLAY that say not compatible with my device. Any known reason why? I figured that open source was open source.
I saw in the AIO that you can change the device type of your tablet to something else. Have you ever tried that? Does it seem to work?
I have also read that the UK models have a slot for a SIM card. Do you know if the US models have it to - just maybe inside and inaccessible?
I am loving the tablet....but find that now that I am back on the 4.0.3 my media files on my HTPC will not play. I find this wierd. The 4.0.3 update - according to the SONY site, says it improves the H.264 file playing...and nothing is mentioned about any changes in the R5 update.
Also one thing I noticed about the R5 load was it would sometimes just turn OFF the tablet. No reason or rhyme to it. Ever hear of that?
I may wind up going back up - if I cannot get them to play...have yet to try copying one to the SD card and playing it. But all of them used to play before I went back down.
Been looking into codecs too - but most of the processing of streamed DLNA stuff is done on the host machine [ putting on the Sherlock Holmes outfit again ]
Thank again for all your insight.
Click to expand...
Click to collapse
If you use MX player it will play most files. Regarding the apps have you checked the unknown sources in the settings?
Sent from my Desire S using xda app-developers app
bearhntr said:
Hey...THANKS. not sure why I did not catch that the tablet did not show as adb device, as I had to do the same thing when I rooted my DroidX...I guess I assumed that it would do it from that install.
Again thanks...now lets see if I can get the 4.0.3 (pre-R5) back on the tablet.
Click to expand...
Click to collapse
bearhntr, I have been struggling trying to get my tablet to show up when I type in adb devices. I was having the same problem you had before you wrote this post. I followed the directions in Bluechips post for the ADB installer (very huge thanks for all those who develop these things to make it easier) and even did step by step with the video. I have also tried other methods to get ADB to work.
Long story short, did you do anything different than listed in Bluechips post to achieve success in getting your computer to see your tablet as an ADB device?
Thanks!
esonnen said:
bearhntr, I have been struggling trying to get my tablet to show up when I type in adb devices. I was having the same problem you had before you wrote this post. I followed the directions in Bluechips post for the ADB installer (very huge thanks for all those who develop these things to make it easier) and even did step by step with the video. I have also tried other methods to get ADB to work.
Long story short, did you do anything different than listed in Bluechips post to achieve success in getting your computer to see your tablet as an ADB device?
Thanks!
Click to expand...
Click to collapse
Esonnen,
I followed the steps from BLUECHIPS direction step by step. Are you seeing the tablet at all in the Windows Device manager? Mine was showing up in the device manager - but not correctly until I installed the drivers.
I right mouse button clicked on the SONY TABLET S entry in the device manager in Windows and chose UPDATE DRIVER...then pointed it to the extracted AdbWinUsbApi.dll file. Followed the prompts and after that the SONY TABLET was listed in an new CATEGORY called ANDROID PHONE, as ANDROID COMPOSITE ADB INTERFACE.
I found that if I did not get it to show as this in the DEVICE MANAGER, nothing I tried with ADB or other tools that used that software would work. This was the same problem I had when I was working with my DROIDX. I had thought that by getting the DROIDX to work properly in the rooting process - that the tablet would as well. It was the simple act of changing the driver to the AdbWinUsbApi.dll that fixed it.
gordo79 said:
If you use MX player it will play most files. Regarding the apps have you checked the unknown sources in the settings?
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
I had already tried that player and it also downloaded the ARMv7 CODEC set to the tablet.
This player may work fine...but it wants the files to be LOCAL to the device or streamed from a WEBPAGE type arena.
I want something that will stream DLNA (the tablet sees all three of my Windows DLNA device and my Sony STR-DN1020 receiver) using the DLNA services that are in 4.0.3. It even shows me the folders on my HTPC. I can also list the movies on it. Where the 4.0.3(r5) showed an actual thumbnail of the first frame of the .M4V files - the 4.0.3 shows what appears to be a set of hotair balloons.
Touching one of the files yields the following error: "INVALID MEDIA - PLAYBACK NOT SUPPORTED" These files play fine on the HTPC and my D-LINK DSM-750 Media Center Extender (and in 5.1 audio). Generally with DLNA the decoding is handled at the source PC, not the playback device. I find this weird too.
Maybe I will try copying one of these files to the device and try playing it from there....try and narrow it down.
GORDO79,
Not sure what has happened, but my Tablet S is now playing the videos from my HTPC. The details of all the videos hows VIDEO CODEC: UNKNOWN and AUDIO CODEC: UNKNOWN, but all of them seem to be playing.
I searched the GOOGLE PLAY STORE, but do not find any codecs listed there other than the ones for various players.
I am so happy now that I can play my videos and I think I will be able to THROW them to my DSM-750 (Media Center Extended) until I can get a BRAVIA TV (hint hint Santa).
Much thanks for everyone's help.
stifilz said:
If you KNEW these forums you would know that we do not take kindly to those who do not use the SEARCH function. It is there so we don't have to repeat ourselves over and over again.
None the less.
If you can't manage this then take it in to Sony saying that you are having issues with the camera (they will restore it to original 3.2 software)
Step One
Root your device.
See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step Two
Use AIO to 'Install "rescue-backdoor" [anti-bootloop protection].'
First you want to download, then extract to a folder, then double-click on S.onyTablet.S.bat, this will open a menu, enter '4' then press enter then enter '1' and press enter again. MAGIC, you have now decreased your incremental, well done.
Step 3
See my Update Links NOTE: ALSO IN MY SIGNATURE AND HAS BEEN FOR A LONG TIME, others had no problem with it
Find the update you require to flash, you want signed-nbx03_001-ota-120803002.zip or for you highness LINK
Step 4
Copy signed-nbx03_001-ota-120803002.zip to your SD card. Google how to if you don't know
Step 5
Put SD card back into tablet and boot into recovery. See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step 6
Leave tablet to boot into R1A
Step 7
Be happy and click the fricken Thanks button.
P.S this is not hard stuff
Click to expand...
Click to collapse
stifilz,
Again many thanks for your help with this. Not sure why the ROOT broke when I did the deed (and I was successful), but I tried to get my root back following your steps again (other than flashing with the .ZIP from the SD card), and I cannot seem to get my ROOT back. Neither the AIO or the ROOT W/RESTORE works.
I wanted to use the AIO to turn off the OTA prompt and run a few of the tweaks, but each time I run it - the screen goes red and tells me I have to ROOT.
Any ideas where I am going wrong?
Much Thanks
can anyone tell me the main differences between the first ics release and the r1a?
sony tablet s 4.0.3 r5?
Personally I know that many people come to know about looking for it and I've spent hours and hours looking for a way to rooted my tablet and still nothing ...
Really there is still no way to update the sony tablet s 4.0.3 r5?
Nor has the downgrade to another rom?
I've looked almost everywhere but to no avail. help me.
I own a rooted Asus Transformer Prime TF201 table with JB 4.1.1 (original), and have probably done something stupid... please help this Noob, as I've read so much when looking for answers the last 2 days -- now I'm thoroughly confused! (To tell the truth, wasn't that great of a root user before...)
My tablet won't get beyond "Launcher has stopped" error when booting.
I rooted several months ago, installed a custom bootloader graphic (still works), SuperSU, ROM Manager and some other rooted apps. I had flashed cyanogen rom "9" (I think) -- the stable one for Asus -- and was running fine. I thought I had done a nandroid backup (file on SD card).
Then I created my problem: I had messed around with the LED settings via ROM Manager, and then I think I changed the build.prop file value for VM heap stack from 256 to 512 ("governor" settings?). (I know, I know -- used to mess around a little with PCs and I should have known better what I was doing!)
Now I can't get homescreens or launch apps, or anything. "Launcher has stopped"
I can power off and power on (using power + volume buttons). My custom bootloader image comes into view after the ASUS logo -- but next I get the "Asus Keyboard is not installed" message with the "Unfortunately, Launcher has stopped" message on top of that. Pressing the OK buttom just blinks and back to the errors.
I *can* get get to the settings, though.
Is a new tablet in my future?
Can anyone help me undo this mess I've made?? Help for the Noobs! Oh, and THANK YOU in advance for the trouble!
Hey!
Can you access the recovery mode? If yes:
1. Download the zip file attached to this post;
2. Put the holo.zip file in your sdcard;
3. Enter in recovery mode and flash the zip;
4. Reboot system;
5. Now you get Holo Launcher in your tablet!
Can't See Asus tablet from PC
Thanks for confirming that I am going about trying to fix this in the 'right' way!
I had never installed the SDK / android bridge to my Windows Vista 32-bit PC -- and I did that a couple days ago.
But I am not able to get root connected to the Asus. It shows as MTP device and I can see the sd card (also via Explorer in Windows)
I feel so dumb but I think the tablet can be rescued, if only I knew what to do!
Can you help me -- start from the beginning and help me get my Asus tablet working again??
Ellie92 said:
Thanks for confirming that I am going about trying to fix this in the 'right' way!
I had never installed the SDK / android bridge to my Windows Vista 32-bit PC -- and I did that a couple days ago.
But I am not able to get root connected to the Asus. It shows as MTP device and I can see the sd card (also via Explorer in Windows)
I feel so dumb but I think the tablet can be rescued, if only I knew what to do!
Can you help me -- start from the beginning and help me get my Asus tablet working again??
Click to expand...
Click to collapse
Sorry, I didn't see your post before.
Why don't you flash the ROM again?
I mean the custom one.
Sent from my mind using super powers.
I WANT TO START OFF BY SAYING THAT THIS IS THE FIRST TIME I HAVE MADE A THREAD ON THIS SITE.
I FEEL MY ISSUE IS UNIQUE AND ALL HELP WILL BE MUCH APPRECIATED. THANK YOU
Click to expand...
Click to collapse
The tablet that I am dealing with is a "Cruz Velocity Mini Tablet" running android 2.0 and no means of installing apk's.
Currently this is the situation:
A friend of mine lent me her Chinese reader tablet.
I told her that I could probably flash a newer version of Android on it, thinking that I could finally try my hand at making a ROM because I know for a fact that there aren't many ROMs if any at all out there for a chinese off brand reader like this.
After rooting the tablet I deleted the pre installed bloatware via ADB commands (shell) including a file manager (Astro) that I believe was the only way that you could browse files on the tablet, as well as some other pre installed applications that must have been necessary in retrospect. There is no existing vending capability or market application.
I am looking to make a custom ROM (Using android Kitchen and Cywign) through following this tutorial by lokeshsaini94 yet I feel like following that tutorial won't even get me where I need to be.
Click to expand...
Click to collapse
Things that I have tried at this point include:
Attempting to connect the tablet to my computer with the SD inserted (with and without debugging turned on) [Failed to show up on my computer as a device or anything]
Downloading the APK that I need from a file sharing website [Downloads fail]
Uploading the APK that I need to my Google drive and downloading it from the tablet [Says waiting for data connection and doesn't download even though connected to our WiFi]
Inserting the SD card into my computer, copying the APK I need over to it, then inserting the SD card back into the tablet, going into the browser and typing "File:///sdcard/<name here>.apk" to install an APK but getting an error in the installer after pushing 'install' -> 'Application not installed'
Trying to perform a factory reset; this simply makes the tablet reboot with everything the same as it was before.
Essentially guys and gals, my tablet here is running Android 2.0, I want to update it by making my own rom for it to something at least >4.0, and it seems that I've made things worse and have no way out of this mess. I think I've essentially bricked it even though it still works. :silly:
What do I need to do to make a custom ROM let alone flash/wipe this tablet?
All help will be incredibly valuable
There should be plenty of info here http://www.slatedroid.com/forum/93-velocity-micro-cruz-reader/ to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Still no paddles
es0tericcha0s said:
There should be plenty of info here < > to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Click to expand...
Click to collapse
Thank you very much for your response. It looks like on that website I've already found multiple useful roms!
In fact I already downloaded one and put it onto the SD card. Apparently for these tablets you're supposed to, while powered off, turn it back on by holding the power button and the volume up button but all this seems to do as a whole load of nothing.
I fear that what I've done to it by deleting potentially sensitive programs previously, I have somehow managed to make this process impossible.
Is there some kind of way that I can plug this tablet into my computer and be able to completely wipe it so I can, at the very least, have a functional tablet that will work at all? I've done approximately 5 factory data resets yet the background image that my friend has on the tablet as well as seemingly every single setting and application is remaining untouched..
Try the ones here that also install a custom recovery: http://www.slatedroid.com/topic/33586-a-clockworkmod-rom-compendium-for-the-cruz-reader/
You'll want to make sure and rename the file exactly as mentioned there on the OP. Install instructions are included too. I don't think there is a way to reload via the PC. The right zip should get everything working properly.