Related
Hello All!
Relative noob here...but more seasoned all the time. Firstly my viewpad device info from FTM:
SWVer=3.410
Model: FM6-001
HWVer: 107
In a nutshell: My bluetooth wasn't turning on (would turn on..then off). So tried to fix by:
1) Rooting and install CWM 5.0.2.6 (awesome tool BTW) and various ROMs, all done with success.
2) No good, oh well now want to give up. Contacted Viewsonic got RMA to return unit..however now concerned they'll not honor warranty if I rooted the device (sigh). So thought I'd return to stock. I did backup..but was already rooted when I thought of it.
3) Trying to return to stock using many versions Sutl3 and Sutlr...and on different PCs none work..once it boots to CWM menu...just stalls with error eventually.
4) Tried to install Napster's CWM with Recovery Menu to be able to return to original state with stock recovery. My version of CWM won't install it...errors out (another great tool though by the sounds of it).
5) Can't use fastboot..never sees device...although ADB works OK. Believe that the Bluetooth issue may be a hardware problem and may be effecting devices ability to work in "download mode". Note that HS-USB device is never present in device manager in Windows even though driver is installed.
So...my question...how can I return my device to stock with one of the below .nb0 files without stock recovery, sutlr or sutl3?
Files I have:
FM6-3310-0-5029-A02.nb0
FM6-3350-0-1008-A01.nb0
Can I somehow use CMW? Can I somehow use adb and "flash_image"?
Will super appreciate any thoughts!
Many thanks in advance!
Johnster25
If I remember correctly, you use SUTL3 from Viewsonic on your PC with the *.nb0 file in the same sub/directory - and just run it to flash the stock ROM or return it to factory condition, you do NOT use CWM to flash or re-install the *.nb0 file ... Part of this process involved overwriting the CWM installed on your rooted device & reversing it to become unrooted, look under the Development subforum here in this section as there's a link/discussion about how to restore, please double check on the details written up.
Also, make sure you have a mSD card in the slot - and that the USB drivers are loaded & running (they should be installed already back then) - might want to power down & restart the PC and do the same to the Vpad7.
Let us know how it go & good luck !
Many thanks for your response.
Well, what has happened when I've used SUTL3 so far is that I select the .nbo image I wish to flash, then the program restarts teh VPAD7 into recovery mode.
From what I've read, after a few moments the phone is then supposed to enter some sort of "download mode" whereby the new image is pushed across the USB cable.
It's at this point with SUTL3 seems to error out, and the phone simply remains in CWM.
I've read a few posts that suggest that not using the correct image could produce a response like this, so I'll retry again this PM having tried re-downloaded the two .nbo files I've tried, and one I've not tried.
Will let you know how it goes!
J.
Hi Again,
OK I've retried it with a fresh copy of SUTL3, and new .nb0 files. Still no good.
Take a look at the enclosed pictures. The first time I try to run SUTL3 the device not configure error shows up. By this point CWM is showing on the VPAD7. I try to run SUTL3 again in this state and now the device not detect error shows up.
So all in all it seems to me that the device when in CWM mode is not exposing an interface to the computer...or the computer lacks the driver needed to utilize the interface.
I've also enclosed a picture of my windows devices when the VPAD7 is connected, as well a copy of the drives that show up when it's connected. The only time the drives change is when the VPAD7 is in CWM mode, at which time the H: drive (where the adb program are) is not present.
So am I missing a driver?
BTW: Have tried to copy down the synchronization program that is on the H: Drive and ran it while running SUTL3...thinking somehow it acted like a bridge to the VPAD7 (I've seen some posts that suggest this). Still no good.
J.
OK..one more piece to the puzzle...or maybe off the trail...but when trying on two differnt PCs when the VPAD7 is first plugged in I get one set of driver installs...and note that the HS-USB has an error.
Later when trying to run SUTL on it...another set of driver installs...again HS-USB error.
See enclosed.
try run sutl with viewpad in FTM mode that worked for me good luck
I have same problem before..n my solution is change back CWM with old ..mine to CWM 2.5.1..found that CWM 5.0.2.6 got problem with SUT L3..and everythind done successfully..as long u can still access ur Viewpad to change CWM its ok..
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Alleycatzero you're a genius! Running SUTL in FTM mode has done it!
THANK YOU!!!!!!!!!!!!!!!!!!!!!!
Johnster25 said:
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Click to expand...
Click to collapse
This is under the Development section - just d/l and unpack the zip file, copy to mSD card & follow the instructions. This verison should be the earlier one and I personally find it worked best together with ext3 and/or ext4 partitioning as needed.
http://forum.xda-developers.com/showthread.php?t=1015005
The issues with SUTL3 and other apps not working/running has to do with the usb drivers not auto-installing & running as they should, try to uninstall Vpad7 drivers, reboot the PC - turn off any firewall and anti-virus software, connect the Vpad7 and let it finish installing/rebooting both devices again. Then, turn back on antivirus & firewall so that you will have easier time flashing rom, connecting mSD card & copying/moving files, etc.
Hi everyone,
I have a Sony Tablet S with Android Version 4.0.3 release 5a and I am having problems with the Android Software, the programs such as browser, games even android base applications keep crashing. The device is still under warranty and I sent it for repair however the service here requested around 100$ for software installation as it is not under warranty. This is too much for me so I decided to do it myself however. I have searched this forum and many more to find a solution however even I have tried every step described in forums several time I could not be able to reinstall latest ROM from SD Card. I really desperately need some help here as this device is purchased solely for my daughter who loves android games alot.
I really appreciate any help you may provide.
Thanks.
Aktemur said:
Hi everyone,
I have a Sony Tablet S with Android Version 4.0.3 release 5a and I am having problems with the Android Software, the programs such as browser, games even android base applications keep crashing. The device is still under warranty and I sent it for repair however the service here requested around 100$ for software installation as it is not under warranty. This is too much for me so I decided to do it myself however. I have searched this forum and many more to find a solution however even I have tried every step described in forums several time I could not be able to reinstall latest ROM from SD Card. I really desperately need some help here as this device is purchased solely for my daughter who loves android games alot.
I really appreciate any help you may provide.
Thanks.
Click to expand...
Click to collapse
hello,
try a hard reset. hold VOL up + POWER and when you see the logo sony release the VOL up button. then choose a factory reset. do not have to install from sd card.
Already tried hard and soft reset. Doesn't work.
I will try to describe the problem in full detail. I have weird error messages like "Google Play Store stopped working" "browser stopped working" "clock stopped working" and such error messages and when I try to uninstall programs i can uninstall them however when the tablet restarts they are all there, I think machine resets it self. If i try to uninstall a program called "Ustream" the tablet immediately goes off, and restarts resetting it self again. Even the soft and hard reset can not solve the problem. I have tried to boot the device, it says it is booted (I have managed to run adb and flash tools) how ever when the tablet restarts it again resets it self having the exact same situation as before. I have downloaded the official R5A update from the Sony Website when ever i try to install update from SD, the machine stops saying the operation is aborted due to some error. There must be a way to reset this machine to what ever it was.
Aktemur said:
I will try to describe the problem in full detail. I have weird error messages like "Google Play Store stopped working" "browser stopped working" "clock stopped working" and such error messages and when I try to uninstall programs i can uninstall them however when the tablet restarts they are all there, I think machine resets it self. If i try to uninstall a program called "Ustream" the tablet immediately goes off, and restarts resetting it self again. Even the soft and hard reset can not solve the problem. I have tried to boot the device, it says it is booted (I have managed to run adb and flash tools) how ever when the tablet restarts it again resets it self having the exact same situation as before. I have downloaded the official R5A update from the Sony Website when ever i try to install update from SD, the machine stops saying the operation is aborted due to some error. There must be a way to reset this machine to what ever it was.
Click to expand...
Click to collapse
If you have adb, you can try to root tab and apply the backdoor patch.
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
smgdev said:
If you have adb, you can try to root tab and apply the backdoor patch.
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
I have already tried that. The adb, flasher and other tools that I have found in this site. All in one tool says it has succesfully rooted the device but whenever it boots it restores itself to a previous unknown backup with all the applications installed and I guess not rooted state. I have used the flasher yet it needs rooted device. I have tried to update the system from SD, it says the software is low version (5A). I can not do anything. There must be a solution for this.
Aktemur said:
I have already tried that. The adb, flasher and other tools that I have found in this site. All in one tool says it has succesfully rooted the device but whenever it boots it restores itself to a previous unknown backup with all the applications installed and I guess not rooted state. I have used the flasher yet it needs rooted device. I have tried to update the system from SD, it says the software is low version (5A). I can not do anything. There must be a solution for this.
Click to expand...
Click to collapse
After attempting root the tablet is rebooting into the other partition. (There are two system partitions). Can you try rooting again and on the last reboot boot into recovery and try to install R5a twice in a row without restarting from the recovery menu. Hopefully this will catch the system switch and install R5a on the other system
stifilz said:
After attempting root the tablet is rebooting into the other partition. (There are two system partitions). Can you try rooting again and on the last reboot boot into recovery and try to install R5a twice in a row without restarting from the recovery menu. Hopefully this will catch the system switch and install R5a on the other system
Click to expand...
Click to collapse
I think I have rooted the device asthere is a "device manager" in the security options. However adb programs fails to recognize the device. I have installed the driver several times, restarted the computer how ever it did not change. Last time I was able to see the device in the adb device list. But i do not know what I have done to achieve this as I have tired many options. Can you describe me how to do that step by setp?
Aktemur said:
I think I have rooted the device asthere is a "device manager" in the security options. However adb programs fails to recognize the device. I have installed the driver several times, restarted the computer how ever it did not change. Last time I was able to see the device in the adb device list. But i do not know what I have done to achieve this as I have tired many options. Can you describe me how to do that step by setp?
Click to expand...
Click to collapse
EDIT: I have AIO tools and flasher and ADB automatic driver instlaller. Now ADB Automatic installer worked just fine the adb devices i can see the device serial number. There is an "android device manager" option which I have enabled from security settings in my tablet. USB debugging mode is active however the S.onyTablet.S allinone v6.5 by konrad plasczykowski can not flash the tablet, it can not find the tablet. when i boot in to recover i have 3 options listed.
1. restart device
2 update sysstem from SD cARD
3 Reset to factory settings
when i choose update system from SD cart i see" Erohibit update as a result of checking versdion or base sku insallation aborted." message what does that mean?
there are no other options. how can i continue on...
Aktemur said:
EDIT: I have AIO tools and flasher and ADB automatic driver instlaller. Now ADB Automatic installer worked just fine the adb devices i can see the device serial number. There is an "android device manager" option which I have enabled from security settings in my tablet. USB debugging mode is active however the S.onyTablet.S allinone v6.5 by konrad plasczykowski can not flash the tablet, it can not find the tablet. when i boot in to recover i have 3 options listed.
1. restart device
2 update sysstem from SD cARD
3 Reset to factory settings
when i choose update system from SD cart i see" Erohibit update as a result of checking versdion or base sku insallation aborted." message what does that mean?
there are no other options. how can i continue on...
Click to expand...
Click to collapse
After the update fail. Use adb pull /tmp/recovery.log and post it here and I will see what is happening
The flashing operation fails as the system can not access to the specified directory. Whenever I run the flashing tool the command windows background turns to red and I see this error. ADB can list the device yet I can not flash it.
By the way I have to reinstall all the drivers everytime I connect the tablet to PC, if I remove the cable and re mount it adb fails to list the device.
Hi all,
I recently got a new Dell Venue 7 3740 (yeah, not my first choice, but it was free for buying a computer). Anyway, started reading up on how to root the thing. I have a couple of apps that require root.
I found this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
and also the main Dell page: http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/
Following Dell's guide to rooting appears to NOT root it. Installing Root Checker confirms I don't have root. Unbricked it and got it back up from 4.4.2 to 4.4.4. By reading the first guide for the 3840, my question is ...
Is the boot image linked there compatible with my 3740?
(yeah, I know this should be in the developer section ... unfortunately I don't have enough posts ... also, I am familiar with rooting/flashing/etc, my first device that I put CM7 on was the original Galaxy S1 ... and I have CM10 on my S3.)
Tried, failed
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
reaper-death said:
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
Click to expand...
Click to collapse
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
ProfM2 said:
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
Click to expand...
Click to collapse
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
Click to expand...
Click to collapse
You better redo the unbrick procces cause as you are now, you won't be able to update your tablet and 4.4.2 has some issues with the clock and browser. The best way to root is by thetered cwm, I did it and it's working great.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Click to expand...
Click to collapse
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
ProfM2 said:
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
Click to expand...
Click to collapse
http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
* For Wifi-only device on A150 and Wifi / LTE device on A195
I see it now, I think I was misinterpreting the above statement which means I've been flashing the A195 rom this whole time. Thank you all for your help! :good:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
ProfM2 said:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
Click to expand...
Click to collapse
It is mentioned somewhere that the 3740 and the 3840 use the same firmware. Assuming that, what you can do is download the latest SuperUser zip, copy it to the internal or external storage, then use THIS, or THIS to root through CWM.
graphdarnell said:
It is mentioned somewhere that the 3740 and the 3840 use the same firmware.
Click to expand...
Click to collapse
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
ProfM2 said:
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
Click to expand...
Click to collapse
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
graphdarnell said:
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
Click to expand...
Click to collapse
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
ProfM2 said:
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
Click to expand...
Click to collapse
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
reaper-death said:
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
Click to expand...
Click to collapse
I have finally settled down and got the tablet rooted. What's really odd, was Win8.1 kept losing the proper driver. I'm not sure exactly why ... but suffice it to say, I got it working. It did appear to be more stable when I hit the Vol+ and plugged in the USB, but then again it may have been a coincidence.
Open source dell
If you follow the link to dell open source, they do have a detailed PDF download for unlocking the boot loader etc. The file was too large for me to upload on XDA. I just found it today while I was researching how to root this tablet. I have not had a chance to try it yet.
http://opensource.dell.com/
That doesnt work for 3740 lte. I;ve done everything that was in PDF. OTA image should be with unlocker bootloader and root but its not. ;/
Its adb root not su big difference
Does anyone have any idea to root dell venue 7 3740 lte
The open source is for venue 7 3740 wifi
how can i hard reset this device please tell me.
Mahisasur said:
how can i hard reset this device please tell me.
Click to expand...
Click to collapse
Reset any android tbalet with ...
Setting >>>>> Backup & Reset >>>>> Factory Data Reset >>>>> Reset Tablet >>> Erase Everything
Hi, good day...
Recently, I rooted my phone successfully, installing xposed framework and modules, but I was messing around the system files then I rebooted my device and now it is currently stuck on boot. I have the exact rom downloaded from needrom.com but my problem is everytime start downloading using "SPD Factory Upgrade Download Toolkit", it appears that my phone is not detected, it's just nothing happens. I have already installed the drivers, uninstalling them and installed it again to make sure I have the right drivers, but nothing works. The drivers seems to be working though, since I rooted my phone successfully. I cannot also get into the recovery mode, I am not sure why. also, the usb debugging was not tick on does it matter? I found some posts online that it is not really necessary. By the way, my device name is Cloudfone Q305E. This device might not familiar, but I hope I can get some help just to install the working rom...
Hi, my rooted Sony Xperia E5 phone( F3311 ) has started to fail when I tried to download the PS4 Remote app with Magisk, I could see the app in Playstore but everytime that I downloaded it the app showed me an error, so I tried many things to pass through SafetyNet succesfully, and nothing. Finally, I thinked about it a while and I De-rooted my device, I noticed that it was a mistake when I couldn't root it again, so I wiped my device and re-installed the root. All was fine, but when I wiped the Cache it showed me an error, "the Cache is busy". Although, I decided not to care about it and reboot my phone, then many error messages appeared showing this: "Unfortunately X app has stopped". I restored the backup and configurated my device, but when I tried to go to Home Screen an error message appeared: "Unfortunately com.sonymobile.anondata has stopped" spamming infinitely on a black screen. I tried to restore my phone to default presets many times but all that messages cames up again when I boot for the first time. What can I do??
Help =(
Sound is low
The sound is low in xperia e5 and tried many methods to solve it but I couldn't make it
Hey there,
I can tell you've messed up your device.
Never wipe your device when you've removed system apps.
Also, don't use Magisk to root this device; it's better to not use it at all, cause it's known to have problems on the E5.
You will have to start all over and flash the stock firmware.
Download Flashtool on your PC and get the E5 drivers for fastboot+adb.
Open up Flashtool and connect your phone with us; it should give you some kind of indication that the connection has been established.
In Flashtool itself there's a button which, when clicked on, will load up an other program called Xperifirm.
In Xperifirm you'll have to search for the latest E5 F3311 firmware and download it.
When it's finished downloading exit the program, and if prompted, run the included script to extract and automatically flash the firmware.
After flashing you'll have an unrooted stock firmware, without any problems or error messages, which you can manually root again by following my guide here on xda.
If you want modules, just install Xposed Framework instead of Magisk.
Good luck.
Marvin.
mrmarvin_16 said:
Hey there,
I can tell you've messed up your device.
Never wipe your device when you've removed system apps.
Also, don't use Magisk to root this device; it's better to not use it at all, cause it's known to have problems on the E5.
You will have to start all over and flash the stock firmware.
Download Flashtool on your PC and get the E5 drivers for fastboot+adb.
Open up Flashtool and connect your phone with us; it should give you some kind of indication that the connection has been established.
In Flashtool itself there's a button which, when clicked on, will load up an other program called Xperifirm.
In Xperifirm you'll have to search for the latest E5 F3311 firmware and download it.
When it's finished downloading exit the program, and if prompted, run the included script to extract and automatically flash the firmware.
After flashing you'll have an unrooted stock firmware, without any problems or error messages, which you can manually root again by following my guide here on xda.
If you want modules, just install Xposed Framework instead of Magisk.
Good luck.
Marvin.
Click to expand...
Click to collapse
Hello, fortunately 1 day ago I did just that but without seeing your comment, but thanks a lot, you're by far a good user. I'm interested in your root guide for do it again but as it has to be made, again, thanks.