Related
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.
Hello, I have several questions about rooting and backing up my Android tablet but I'm not really sure where to begin.
My (current) goal is to back up the firmware that's currently on the tablet so that I can later restore to it in the event that something goes wrong. The only problem is I seem to have a newer version than the latest-offered version that was posted on the manufacturer's website, but the latest-offered version doesn't work. To make matters worse, the manufacturer's website is no longer online so there's no chance that the firmware I have will ever be uploaded. In other words, I need to root my tablet so that I can make a backup of the stock firmware to revert to if necessary.
The tablet in question is a Panimage Media Tablet R79RT2W5 that I picked up for $20. Before you tell me not to bother or that it's a piece of crap, don't worry; I'm VERY aware. The entire reason I bought this to begin with was BECAUSE it was a piece of crap. I was hoping that at the very least I could screw around with it and use it as a testbench to learn Android programming on with hardware I don't care about possibly bricking. (In other words, I wanted a cheap tablet to play around with so I wouldn't risk bricking my phone.)
I'll try to give you all the possible information I have on it. If you need any more information, pictures, screenshots, uploaded files, etc. I'll try to get what I can for you.
Panimage Media Tablet
Model Number R79RT2W5 (according to the physical sticker on back)
Model Number R79RTW5 (according to the 'About Device' page; note the lack of the 2 in the model number there.)
256MB of RAM
Firmware Version 1.6 (Donut, apparently?)
Kernel Version 2.6.29
Build Number WMT2.1.7_PD
2GB Internal Flash Memory (according to the box)
- Apparently it's a Gome Flytouch clone?
- It has a whole bunch of software made by WonderMedia Technlogies. (Which makes sense considering that it has a WMT-based processor.)
- It has "App Market" com.wonderappstore instead of Google Market. In other words, I basically have to sideload apks to get anything worth using.
Click to expand...
Click to collapse
Things to take note of:
- It has no USB port so I can't hook it directly to a computer (meaning regular ADB won't work), but it does take microSD cards.
- I can sideload applications, but they need to be able to work on 1.6, obviously.
- I have FTPServer installed so I can send files to/from my computer, but I can't access protected directories.
- I have run BOTH Universal Androot and z4root. Neither program rooted the tablet. z4root DID install SuperUser (which I'm assuming only worked because USB debugging was turned on), but SuperUser doesn't work.
- I'm willing to work with terminals or command prompts so long as I have someone able to walk me through the process.
Is rooting this thing a possibility?
Alternatively, the way that the firmware update process works is that you put a folder named "script.zip" on the root of the microSD card and then boot the tablet with the card inserted. The tablet will then proceed to automatically install the firmware on it.
Would it be possible to take advantage of this function to allow me to run a script that will back up the firmware to the microSD card before it boots that I would then later be able to restore onto the tablet as necessary?
I can upload a copy of the latest script.zip I have so that you can take a look at it if you'd like.
What do you mean by their isn't a USB port what do you use to charge.
Sent from my HTC Velocity 4G using Tapatalk 4 beta
WildfireDEV said:
What do you mean by their isn't a USB port what do you use to charge.
Click to expand...
Click to collapse
It has a generic electrical plug; one of the round ones with a single prong in the middle.
It doesn't charge through USB like most other phones/tablets, because there's no USB port on it.
you can possibly back up your phone's firmware even without a usb port...
using the stock recovery, you can flash a custom recovery like clockworkmod which gives you a back-up option... and you can also root it with that...
WisdomSky said:
you can possibly back up your phone's firmware even without a usb port...
using the stock recovery, you can flash a custom recovery like clockworkmod which gives you a back-up option... and you can also root it with that...
Click to expand...
Click to collapse
That's a bit of a problem... the tablet doesn't appear to have a stock recovery available.
I've tried as many button combinations upon boot as I can think of (Power + Vol. Down among many other things) and none of them boot into any sort of recovery mode.
I've even gone as far as trying to force my way in using the SysRq trick that someone got to work for the Ouya:
http://forum.xda-developers.com/showpost.php?p=42516267&postcount=6
...but unfortunately that doesn't work either. No mater what Alt + SysRq combination I use (out of the ones that actually work, that is), the tablet automatically restarts. Every time.
However, as I said in my OP, I think that there may be a small bit of hope.
Alternatively, the way that the firmware update process works is that you put a folder named "script.zip" on the root of the microSD card and then boot the tablet with the card inserted. The tablet will then proceed to automatically install the firmware on it.
Would it be possible to take advantage of this function to allow me to run a script that will back up the firmware to the microSD card before it boots that I would then later be able to restore onto the tablet as necessary?
I can upload a copy of the latest script.zip I have so that you can take a look at it if you'd like.
Click to expand...
Click to collapse
After a bit of messing around, I've found that the firmware update process looks for a file named "prepare.bin" and then loads it, which starts the automatic firmware update process.
While I'd rather try doing some sort of manual root on the tablet if possible, I'd be willing to try to make my own version of "prepare.bin" that will allow me to essentially hijack the firmware update process before it begins, which should essentially give me system-level control over the tablet.
...In theory, that is.
Do you think this would be a possibility?
I'd post pictures and screenshots and links and other information I've found, but I don't seem to have enough posts to do that yet...
edit- To be more direct, I'm willing to try to hijack the boot process to run my own code if possible, but I'd much rather do some sort of manual root or something if possible so I don't risk screwing up my tablet. As I said before, neither z4root nor Universal Androot work for my tablet, so I was wondering if there's some sort of manual exploit I can use to get in from within Android. If that's possible, I'd much rather take that approach as opposed to basically brute forcing my way into system-level access and risk bricking something.
Hello there,
I just registered on this forum to hopefully resolve my problem with the Kobo Arc tablet. I apologize if any similar issue regarding this was posted. So basically, my Uncle bought me a Kobo Arc tablet about 2 months ago and I know quite alot of things about it. Due to my stupidity I couldn't play a game I really wanted to and so I edited my build.prop to make my tablet compatible with the game. In build.prop I changed the product model to: "GT-I9100", product brand to: "Samsung" and product manufacture to: "unknown". After this I restarted my device. As I did, the kobo arc logo appeared and then a never ending start-up boot. I restarted my device many times but still couldn't get my device to fully on. I entered recovery mode by holding the up volume and power button together and tried to reset to factory, but my Kobo Arc just still won't go pass the never ending start-up screen. I even tried to connect it to my computer but it doesn't recognize it. I'm assuming it's bricked, is there any possible fix for this? if so I need to know asap.
Someone please help me, it would be so kind, and I'll appreciate it soo much.
Thanks in advance
SmootZ
Please, I'm in urgent need of help. I really want to go on my tablet again..
Any help to get my kobo arc to its original state and working properly again, I would be sooo grateful.
Do you have a nandroid backup? If so, restore it.
Otherwise, do you still have access to your SD card (probably using an adapter and connecting it to your PC)? Try using AROMA FM to edit build.prop to the original values.
If not, I'd suggest installing ADB (GIYF) and using that to edit build.prop.
For the last two solutions, you'll need to use the shell, and use a text editor such as nano, pico or vi (depending on what's available). BTW, how did you edit build.prop?
You can also flash back stock/any ROM. Restoring to factory settings doesn't restore build.prop AFAIK.
EDIT: Just noticed your PC doesn't recognize your phone. That rules out solution #3. Are you sure the required drivers installed on your PC?
Yes, I'm sure. But when I plug my tablet into my PC through my usb cable it makes a noise connoting its connected but it won't appear.
Could you possibly give me instructions on how to do a nandroid back-up or something that will get my device back with the following condition:
-My device not able to be recognized on my computer
EDIT: When I connect my device to my computer it charges, but it won't appear on my computer or anything, if this helps.
It's too late to make a nandroid backup now. Try using AROMA FM.
GermainZ said:
It's too late to make a nandroid backup now. Try using AROMA FM.
Click to expand...
Click to collapse
Could you possible give any instructions, I'm kinda new to this stuff.
SmootZ said:
Could you possible give any instructions, I'm kinda new to this stuff.
Click to expand...
Click to collapse
Click the link I posted.
Read the first few posts in full.
Ask about the specific part you don't understand.
I cannot even access my device apart from putting it in recovery mode since my device gets stuck at the start-up and loops, In addition I don't know how to access my sd card since my computer doesn't recognize my device as I said. Will this be a problem?and can I still do it?How do I access my sd card?
Sorry if this question seems stupid
Is your device still not detected in recovery mode?
To access your SD card directly from your PC you'll need a special reader/adapter.
Nope, it doesn't recognize it even in recovery mode. What is this "special" reader/adapter and where can I get it? Could you provide me a link or something?
Well, I'm out of ideas. Just Google "SD card adapter".
Actually my device does not offer any external memory card slot. Meaning There is no support for MicroSD or SD cards on my Kobo Arc.
What shall I do now?
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
SmootZ said:
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
Click to expand...
Click to collapse
I'm out of ideas you could try yourself. I'd try triple checking the drivers on your PC and see if you can get ADB to work.
Is sending your tablet to repair an option?
EDIT: Can't you update to the latest update using fastboot?
Hey.
First of all, messing with build.prop without backup wasn't the brightest idea in your life, but crap happens, like Forrest Gump used to say.
What is the exact model of your tablet? Kobo Arc? Kobo Arc 10 HD? Maybe Kobo released an update and you can update it directly by fastboot.
If not try to use Linux as it handles ADB much better than Windows, go to system and edit you build.prop back and wipe cache and dalvik cache. You need to have a working ADB to even think about reversing your changes.
Good luck.
Well thanks for the help.
Can I try taking this adb method without my device giving permissions for USB debugging? Since I haven't enabled this in my developer options as far as I know, in addition I cannot really check since my device is bricked but I'm 100% sure it's NOT enabled. Will this stop me from carrying an ADB method?
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...
Hello and thanks for reading / helping if you can.
In brief, I have a Samsung Tab 2 GT-P3110 tablet which was running android 4.2.2. It's main use was as a controller for my sonos sound system which no longer supports my device. I thought I'd try and update it rather than simply chuck it into landfill for no good reason other than it was old like me! I know almost nothing about what I am doing, sorry!
So far I have I think 'rooted' the device using something called odin, and installed the clockwork recovery mod. I have also installed the Samsung drivers onto my PC and I have on my pc a zipped file which I believe will install a newer version of android (perhaps some guidance might be required for best file to go for). Unfortunately I am unable to see my tablet's sd card (or anything to do with the tablet) when connected to my pc via USB in order to copy it. Moreover I have copied the same file to a micro sd card but when I put this directly into the tablet and try and boot off the external card I get an access error and the card is not read.
I am out of ideas now and wonder if one of you clever people might be able to help me? I think I read somewhere about having to switch on USB debugging and USB sharing or the like BEFORE rooting. The instructions I used only mentioned the former and so that's all I did. Maybe I've locked myself out for good.
Thanks again, Pezos
Blimey, I really must have killed it! Surely someone out there can help me fix it?