Hello!
I have an Atrix 4G (MB860 Bell) who is rooted but I DO NOT unlocked the bootloader. Bootloader is locked. I'm with the original Motorola Android, version 2.3.6.
Using "Rom Toolbox" app first time, I tried to change the battery icon. When I clicked on install, appeared several error messages with warnings that applications were being terminated. I decided to restart the Atrix but he never passed the initial startup screen, getting stopped in the image of the Motorola logo and says "Dual Core".
I've tried taking the battery several times.
I've tried starting in "Android Recovery", but I get the message: "Failed to boot 2".
How can I solve this problem?
I have no recent backup of my data, because I have no SD installed. Can I recover my data before "rescuing" the phone?
Thank you!
Did you purchase this phone new or used? You might try unlocking the bootloader anyway if you can get to RSD protocol. Once unlocked you may be able to recover it.
I'm not sure of what other options you might have.
I bought this new phone for less than 1 month. So I do not want to unlock the bootloader, not to run the risk of voiding the warranty.
Anyone else can help, please?
I need to resolve without unlocking the bootloader.
Wonderful!
I could access the files using the "Early USB Enumeration" and Commander Android app (http://forum.xda-developers.com/showthread.php?t=1587717)
Taioba said:
Wonderful!
I could access the files using the "Early USB Enumeration" and Commander Android app (http://forum.xda-developers.com/showthread.php?t=1587717)
Click to expand...
Click to collapse
UPDATE: :crying:
But I was unable to access user data.
How do I fix?
Now, using the QtADB.
I have found that you need the "Shell Root" in SuperOneClick to get access the files from /system
ops! i posted in the wrong place...
Related
Hi, I have been trying to root and unlock my prime TF201 (JB 10.4.2.17 - stock) which I bought a few months ago. I am at my wits end. I have searched through most of the guides here and walked through most of them (thanks to everyone for their hard work, because they are all well written!) and I keep running into these roadblocks...
When trying to run the Asus Unlock Tool V6, I get an error message "unknown error, this may be caused by a network connection or contact your administrator". When using any of the other methods from the guides here on XDA, I get various errors (i.e. "adbd cannot run as root in production builds" or "permission denied" or "file not found" - apparently su and root do not exist either).
I can't boot into recovery, I get the "dead android with an exclamation point" and then it cold boots. I can get to the fastboot screen, but then I can't access my device. I installed a terminal program (better terminal emu) on the tablet, but I still can't get root access to copy the files where they need to be.
Any advice would be greatly appreciated!
Thank you in advance!
Error on ASUS Unlock Tool may be caused by network problem or their servers being overloaded - it happens. You can wait or check if server is up by pinging it (better if from your Prime, but from another computer in same network will be fine). Address is mdm.asus.com
About "dead android with an exclamation point" - it may be there becouse of update.zip on SD card - recovery tries automatically update system. You should delete it if any.
This may not be solution but full wipe helps sometimes
weavejenn said:
Hi, I have been trying to root and unlock my prime TF201 (JB 10.4.2.17 - stock) which I bought a few months ago. I am at my wits end. I have searched through most of the guides here and walked through most of them (thanks to everyone for their hard work, because they are all well written!) and I keep running into these roadblocks...
When trying to run the Asus Unlock Tool V6, I get an error message "unknown error, this may be caused by a network connection or contact your administrator". When using any of the other methods from the guides here on XDA, I get various errors (i.e. "adbd cannot run as root in production builds" or "permission denied" or "file not found" - apparently su and root do not exist either).
I can't boot into recovery, I get the "dead android with an exclamation point" and then it cold boots. I can get to the fastboot screen, but then I can't access my device. I installed a terminal program (better terminal emu) on the tablet, but I still can't get root access to copy the files where they need to be.
Any advice would be greatly appreciated!
Thank you in advance!
Click to expand...
Click to collapse
Many people are having issues with the Unlock tool. Did you ever have to send it in for RMA service? ASUS isn't really doing what they can to support this tool, so unfortunately it sounds like you may be out of luck until they do something about it. It is certainly worth a shot to try it every so often and see if it works...
There is not a known exploit in our current JB OTA to allow rooting without unlocking. You would have needed to root on ICS and used voodoo or supersu to protect your root for the update. The issue here is there just aren't many devs working on our platform any longer. From my understanding the ADB restore exploit should in all reality work with our tabs... with some tweaking.
Thank you both for responding so quickly! Unfortunately, this tablet came with the latest update applied so I guess I will have to deal with it until Asus decides to update their bootloader unlocker. In the meantime, I will most likely search for a work around or another exploit to get the bootloader unlocked because I happen to be impatient If I find anything (that works) I will be sure to post it here in the forum.
Have a good day!
weavejenn said:
Thank you both for responding so quickly! Unfortunately, this tablet came with the latest update applied so I guess I will have to deal with it until Asus decides to update their bootloader unlocker. In the meantime, I will most likely search for a work around or another exploit to get the bootloader unlocked because I happen to be impatient If I find anything (that works) I will be sure to post it here in the forum.
Have a good day!
Click to expand...
Click to collapse
I downloaded the bootloader unlocker today and i kept receiving the network error. After several hours, suddenly it asked me for my Google password and then it unlocked my TF201!!!
The Problem:
Phone stuck on LG logo screen with "Security Error" written underneath.
How I Got Here:
Rooted and installed recovery using apks found in these forums. I successfully restored a CWM backup zip found on these forums. Next, I decided to try flashing a ROM. SuperLuminal gave me a "Status 7" error, but when I checked over the thread, I realized that the P769 was not specifically mentioned as a compatible device. So, I decided to give PACman ROM a try, but got the same error.
I googled "status 7 error" and found a guide for fixing this (removing "assert" line in updater-script line). I was aware of the danger in doing this, but since PACman ROM stated "P769" right there in the title, I gave it a shot. Now I'm stuck with the "security error" screen.
What I tried:
I could no longer get into recovery, so I thought restoring it might be a good idea. I tried to use fastboot using the method described in this thread (http://forum.xda-developers.com/showthread.php?t=2310569). However, I quickly realized that I didn't know how to put the phone into a "download mode" like most other phones I've worked with.
I then tried B2CAPP, but phone couldn't be detected. Went and learned how to get into s/w upgrade mode, ran recovery and got an error message saying "updating is not possible any longer due to a fatal error..."
Next, I tried uninstalling all LG software and rebooting PC. Installed LG PC Suite found here (http://en.kioskea.net/download/download-19186-lg-pc-suite), allowed the program to update to latest version. Then tried to run Emergency Firmware Recovery, which opened a window asking if I want to run LG Mobile Support Tool. I clicked OK and was taken to an app that looked exactly like B2CAPP and gave me the same error as above.
So in conclusion, I can only access two screens: the LG logo security error screen and the s/w upgrade screen. Neither appears to give me access to fastboot/adb nor to LG's recovery tools. Am I permanently bricked or is there a way out of this mess? I've been searching these forums extensively and have tried every method I could find. I'm out of options, so I'm kinda freakin out here. Can anyone please help me figure out what else to try?
You did some studying for sure, but you needed to do some more before jumping in.
1. http://forum.xda-developers.com/showthread.php?p=41768774
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sent from my LGMS769 using xda app-developers app
Kuma82, I can't thank you enough for your helpful response.
Here's a shortened version of what I did, in case someone out there finds themselves in a tough spot like I was in:
1. Installed OMAP drivers using method described in link above (right-click on device in Device Manager, manually install driver, etc.). Fastboot worked after this
2. Using Lelus' Fastboot, flashed option 6 (load JB xloader and uboot). This gave me an inverted purple LG logo that still said "security error"
3. I think tried to use fastboot to flash the p4_769.img recovery file. No change. Loading up s/w upgrade mode and the LG Mobile support tool (B2CAPP) was no use (stuck at 15%, no connection to phone).
4. Once again, using one of the links above, I downloaded 3 .img files and proceeded to erase uboot, boot and recovery and flashed those .img files instead. When I rebooted the phone, I got the regular LG logo for a second, then a white flash and then a smaller LG logo with "security error"
5. Now, I installed the LG United mobile driver, went into s/w upgrade mode again and ran the Mobile tool. Got the "updating is not possible..." error again
6. Searched for the offline flash fix method and followed it step-by-step, word-for-word. Phone works again!
I'm pretty sure I could have just done steps 1, 4 and 6 and achieved the same result.
Hope this helps someone, and thanks again Kuma82!
I've had this happen to me twice and was able to get out of it really easily. Basically, I just have my desktop set up for offline flashing and my laptop for online. Just popped into S/W update mode and plugged it into the laptop, started the b2c app, clicked on the "recovery phone" option, and went for a snack. Fixed when I came back.
No problem, glad I could help.
Now that you know how to use fastboot, you are pretty much ready for everything.
It took me a couple of tries to get it running.
Use the new root method, http://forum.xda-developers.com/showthread.php?t=2338816
If you plan on staying on stock, get the cwm for locked bootloader, but first get this busy box http://forum.xda-developers.com/showpost.php?p=43395803&postcount=260
Then this cwm
http://forum.xda-developers.com/showpost.php?p=41613095&postcount=220
Sent from my LG-P769 using xda app-developers app
kuma82 said:
You did some studying for sure, but you needed to do some more before jumping in.
1. http://forum.xda-developers.com/showthread.php?p=41768774
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
Dear, Kuma82!
Thank you very much fot your instruction! It really saves my LGP768 from "security error"! I follow 3 steps and it works, GREAT!
Thank you again and this forum too!
Please help! Bricked LGMS769 (P769)
Solved. The LGMobile Support Tool needed to run on a different computer. It worked when I put the phone into SW Update Mode (press up volume key and plug in USB) and then ran the LGMobile Support Tool.
By the way, this is how I got the phone recovered after it was booting to the small LG logo with the "security error" message as mentioned in Step 4 above.
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.
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.
Hello,
Forgive my lack of experience in this forum. My daughters Pixel 6 has the following message:
Problems updating this device.
This device can't receive any future system updates.
Contact your devices manufacturer for support.
She got this message after she got an alert saying her phone has not updated in the last 21 days.
Is there anything she can do to get rid of this error and update the phone?
Her phone is completely stock and running Android 13.
Would need detailed instructions if anything can be done.
We tried using the pixel software updater tool here https://pixelrepair.withgoogle.com/ but get an error about 15% into the software install. No info on the error. just the word "error"
We tried a factory reset using the boot rescue mode, but it says the phone could not be erased.
The phone is currently working, it just has the message when updates are attempted.
Thank you for any help and suggestions.
Anikir said:
Hello,
Forgive my lack of experience in this forum. My daughters Pixel 6 has the following message:
Problems updating this device.
This device can't receive any future system updates.
Contact your devices manufacturer for support.
She got this message after she got an alert saying her phone has not updated in the last 21 days.
Is there anything she can do to get rid of this error and update the phone?
Her phone is completely stock and running Android 13.
Would need detailed instructions if anything can be done.
We tried using the pixel software updater tool here https://pixelrepair.withgoogle.com/ but get an error about 15% into the software install. No info on the error. just the word "error"
We tried a factory reset using the boot rescue mode, but it says the phone could not be erased.
The phone is currently working, it just has the message when updates are attempted.
Thank you for any help and suggestions.
Click to expand...
Click to collapse
Try clearing storage on the Google Play Services app.
Lughnasadh said:
Try clearing storage on the Google Play Services app.
Click to expand...
Click to collapse
We already tried that several times as well. Thanks.
Anikir said:
We already tried that several times as well. Thanks.
Click to expand...
Click to collapse
Maybe try Android Flash Tool to update to the latest build. You will need to have OEM unlocking enabled in Developer Options. The directions in there are pretty straight forward. Would probably want to tick "Wipe Device" and "Force Flash Partitions". If you go this route, make sure you have the latest Platform Tools and USB drivers. Also suggest using an A to C USB 2.0 cable.