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.
Related
Hi everyone
This is my second post about the same problem. My sony tablet s has a strange problem, all the applicaitons, even the main window application crashes constantly and i can not use the tablet. I have tried to boot the tablet with "ADB" drivers installed and Sony Tablet S all in one V6.5 by Konrad.
When i install the adb drivers as described in the video, the adb devices command can successfully recognizes the tablet. However when I try to boot the tablet with the SonyTabletS program, it says it has successfully bootet it and after it restarts the tablet everything seem just as before, no "Terminal" application present and when I try to unboot the device with the same program it says "the device needed to be bootet first".
So I have checked the everything in the tablet and the problem as I have observed is the tablet always restores an unknown backup whenever it restarts. So whether I boot it or not when the tablet restarts all the programs, everything is restored to a previous state where boot is not applied.
I have also downloaded and saved the latest rom to sd card and tried to install this rom form sd however I always receive the same error message while it is verifying the update package. it says "erohibit update as a result of checking version or base sku"
I have get in touch with sony service here and they demanded to much money to reinstall the software although the device is under warranty. In fact the technician in the service recommended me to install to software bymeyself if I could.
So I need a solution and would appreciate any help you would provide.
Thanks.
Aktemur said:
Hi everyone
This is my second post about the same problem. My sony tablet s has a strange problem, all the applicaitons, even the main window application crashes constantly and i can not use the tablet. I have tried to boot the tablet with "ADB" drivers installed and Sony Tablet S all in one V6.5 by Konrad.
When i install the adb drivers as described in the video, the adb devices command can successfully recognizes the tablet. However when I try to boot the tablet with the SonyTabletS program, it says it has successfully bootet it and after it restarts the tablet everything seem just as before, no "Terminal" application present and when I try to unboot the device with the same program it says "the device needed to be bootet first".
So I have checked the everything in the tablet and the problem as I have observed is the tablet always restores an unknown backup whenever it restarts. So whether I boot it or not when the tablet restarts all the programs, everything is restored to a previous state where boot is not applied.
I have also downloaded and saved the latest rom to sd card and tried to install this rom form sd however I always receive the same error message while it is verifying the update package. it says "erohibit update as a result of checking version or base sku"
I have get in touch with sony service here and they demanded to much money to reinstall the software although the device is under warranty. In fact the technician in the service recommended me to install to software bymeyself if I could.
So I need a solution and would appreciate any help you would provide.
Thanks.
Click to expand...
Click to collapse
Is your device rooted? If yes, you can apply the backdoor patch from aio and flash a signed ota zip from sdcard.
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
I have tried to root the device by using ADB drivers and all in one sony tablet s program provided somewhere in this forum however although the program says the tablet is rooted, when the tablet restarts I see that all the programs and everything restored to some previous backup. So the root is also removed. I have checked the programs in the tablet there seems to be no "TERMINAL" application visible. and when I try to unboot the machine the program says the tablet is no booted.
Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.
I'll try to get as straight tot he point as possible.
Been using my Mobile one touch pix 7 for a little over a year and always installed Ota updates. Well I rooted the tablet not too long ago, forgot which method I used, but was working fine.
an Ota update came through and totally forgot it was rooted, and tried to install it, at which point the whole tablet got bricked.
It ended up in recovery, and I selected due to failure, to format and wipe the data.
Anyhow, The unit will stay at the boot screen for a while then show command error and then show the recovery screen, my only options are:
reboot
update from sd card
update via adb
update via memory
reboot Bootloader
power off
Well I've tried updating by downloading system images via adb, they return a verification error.
I've tried using adb side load to try to install an Ota update file I found for it, returns a verification error.
I cannot get into download mode, fast boot mode I think does not work as windows reports 3 android devices, but the mobile update software cannot see anything, and fast boot gets stuck at waiting for devices.
I suspect the tablet is for lack of a better description totally bricked and just a paperweight.
I am at a loss of what to try from this point. I'm sure wiping the data after the failed update killed it completely but not sure.
Anyone have any guidance here? I've downloaded a few images from the web I found that say they are for this tablet model, but still getting verification error.
Is there any flashing software I can get that may be able to access the tablet or can I copy a file to the scared and have it try to run an update from there. I don't care if it is rooted or not, just want to get it usable again.
I can run Mac OS, windows 10, windows 7, windows xp, or even have no issue getting a linux version going, whatever will work best for this I can use it. windows 10 I was able to manually add the drivers but windows 7 is not letting me do it the same way. I can connect via adb sideload only, no other adb functions seem to work.
I'm not a total news when it comes to custom rooms, as I have done it with another tablet, and an android car radio, but those were pretty straight forward and bootable so never ran into a brick issue yet.
I have a feeling this is toast and I hope that is not the case.
If anyone here can help out, I would appreciate it.
Thanks again....
Need help here to. Been searching with no luck. Any my issue is.
Rooted kingroot, flashed twrp with flashify and now I'm stuck on twrp. Been searching for any custom stock rom. I forgot to unlock the bootloader but I did enable usb debugging (i didn't see any oem options).
Any k 28532Jonsunf of help would be greatly appreciated.
This sorta happen to me. I rooted pixi 7 with kingroot, and was able to delete a lot of bloatware. However, when I was using lucky patcher it pretty much messed up the play store. But it was fine. I could download stuff through the Internet. But sooner or later I needed to fix it. Tryed a lot of ways but it didn't help. So I factory reset the tabletand now im stuck at the Setup Wizard. It just won't let me let me through. I thought its was over, but then I get a message saying there is an update available. So I download it and installed it. But all I get at the end is error. So now I need to flash it with stock. I tried the img. too, but it doesnt show up in the recover menu. If you found a solution please tell me
Can anyoonneee help me find a good Custom Rom for the alcatel one touch pixi 7 (9006W)? Sucks that there's not much info for this device (probably cause the device sucks lol) I'm running on lollipop 5.0.2 and am not able to get OTA update due to rooting. Unrooting didn't help. It seems only answer is custom rom but don't want to risk bricking it as I don't have a computer at home. Also, I am new to this so if anyone can share some insight, I'd be eternally grateful
P.s
It's a t mobile device but I only use it on wifi.
Am using kingroot.
Have never installed a custom rom
****ing device is 8 gigs. 1 gig Ram.
Is it possible to get Nougat?
Help meeee lol
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.
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!