I initially bricked my phone when I took an OTA update by accident while the phone was rooted. When I got the new phone I decided to let it update first and then try to root it but now the Gingerbreak/ZergRush method doesn't seem to work. It never reports that it failed but doesn't say success either, just the "Blue Hellions" thing. The script fails at the "adb remount" saying that the operation isn't permitted.
I've tried a few other methods but have had zero luck with them but most of them used ZR so I didn't expect a lot.
Since they don't seem to have a recovery image for this phone, there's not a lot I can do.
I'll take any ideas and upload logcat, etc.to help out (if I can...it seems to be about 100k which was double the allowed size for the last forum I asked this on)
Any and all help appreciated.
Kyocera Milano Root?
ehrichweiss said:
I initially bricked my phone when I took an OTA update by accident while the phone was rooted. When I got the new phone I decided to let it update first and then try to root it but now the Gingerbreak/ZergRush method doesn't seem to work. It never reports that it failed but doesn't say success either, just the "Blue Hellions" thing. The script fails at the "adb remount" saying that the operation isn't permitted.
I've tried a few other methods but have had zero luck with them but most of them used ZR so I didn't expect a lot.
Since they don't seem to have a recovery image for this phone, there's not a lot I can do.
I'll take any ideas and upload logcat, etc.to help out (if I can...it seems to be about 100k which was double the allowed size for the last forum I asked this on)
Any and all help appreciated.
Click to expand...
Click to collapse
My wife has same phone and I also have tried many diff ways to root this phone with no luck. If someone out there has a suggestion...plz offer... tired of sleeping on couch while Milano is acting up.:crying:
Root Milano patched 2.3.4 Gingerbread
hawkeyez731 said:
My wife has same phone and I also have tried many diff ways to root this phone with no luck. If someone out there has a suggestion...plz offer... tired of sleeping on couch while Milano is acting up.:crying:
Click to expand...
Click to collapse
I just got my phone from Ting a couple weeks ago and rooted it yesterday.
Unfortunately I can't directly post Outside links (Not at 10 posts yet, and have no idea what else to post about other than this at the moment, which requires a link (For Credit Due Purposes) and I know it will be helpful to people that were as desperate as me for something that was starting to seem rather impossible and no one was paying that much attention to it.), but this is important enough that I'll try to just chop it up - You'll just have to put it back together to go to that site.
This works:
androidforums
.com/milano-all-things
-root/709963-no
-pc-root-method
.html
Not sure why the guide says "Enable usb debugging in Settings, Applications, Development" since you never use the PC, I enabled it anyway, and also enabled to install third party apps, or else Poot won't install, not sure why that isn't on the guide. (Maybe they got mixed up?)
A few things you might want to know:
After hours I finally found the solution. But the terminal still doesn't work for uninstalling ("pm uninstall com.google.android.books.apk" = Failure), you have to do everything though your phone (I'm using the app "RootAppDelete"). The phone roots itself with a third party app called "Poot" using libraries from "Ministro 2"
Before doing this you're gonna need something like 25MBs of storage or so (Can delete everything afterwards with the exception of SuperUser (Can't delete that) to get the space back (Also, you need a app to actually use root actions). - The "Ministro 2" packages are huge for this phone's tiny internal storage! 11MB around)
Make sure to install anything small first and anything big right before the phone gets over 15MB full, because at that time you can't install anything else, with low memory errors.
Another thing that might have helped me when I did this is - back when I couldn't root I made all apps default install to the phone with the android sdk platform-tools (I didn't want to risk anything so I moved Poot, Ministro 2 and SuperUser back to the phone before running Poot. since they default installed to the SD)
"adb shell"
"pm SetInstallLocation 2"
Know its been said elsewhere, but this works with the Milano. Wanted to say that in case you needed the space to use Poot.
And the last problem is after I did all this, now my headphone jack wants to think it has headphones plugged in all the time, If I move the phone around it starts playing on the phone's speaker. It seems like something is lose. Not sure if that was caused by the root (since it wasn't doing it before, and I've never used the headphone jack before) or because there was lose hardware, not sure. Still working on a solution to that, which I found
something similar here, almost looks like a common problem: http://forum.xda-developers.com/showthread.php?t=817872
I would put my proof of doing this have a screen shot of root checker, but alas its an outside link. Understand though.
And as I've read a million times before this, here's a disclaimer: I'm not responsible and use at your own risk.
The 4.0.4 OTA update was waiting for me when I woke up this morning. I started the install but when it went to reboot it hung up with a picture of the Android man on his back with a red error/warning triangle.
I haven't done anything with it, hoping someone might be able to help me out.
The phone is rooted but running 4.0.2 stock rom. the battery was a little low when i started the install, but i plugged it in before starting.
Thanks in advance for help,
jvoosh
the reason is that your phone is rooted ,so ... if you want OTA ,you had better unroot you rom or ruu
so can I hard reset the phone (pull the battery) without screwing anything up and then figure out how to unroot the phone?
thanks for your help,
j
Ditto
I'm in exactly the same boat, and hope someone answers this before I try a battery pull.
EDIT: I read around and found some people describing our situation, and mentioning that they did battery pulls to no avail. So I did, and nothing broke. However, the update didn't go through, and now I'm trying to figure out why this happened.
Same issue
I'm having the same issue. Phone got the IMM76k update, and after downloaded, was prompted to restart and install. So i did, gets through part of the install, and then goes to the android man on his back with a red exclamation mark. Have tried multiple times, all to no avail. Now, when I click check for update, it says system up to date, but still on 4.0.2.
Non-rooted, bootloader unlocked...anyone have any luck fixing this?
After downloading update, get Android man on back with red exclamation point
I'm having some difficulty getting the update to install, along the lines of some of the comments posted before mine:
I was able to force download the OTA update (IMM76K) according to the instructions on this original post. (It took a few tries, but eventually worked.)
I select the "Restart & Install" option (which is the only option available to me), and it restarts.
I get the relatively familiar Android man with his blue-green glowing polyhedron wireframe guts spinning, and a progress bar beneath him. After getting through what looks like about 20%, it slows down significantly, and I get the Android man on his back with a red exclamation point above him where the polyhedron used to be. I don't recall seeing any specific error message any of the three times that I tried this. (The first time, I did a battery pull; the second and third times, I just waited, and it eventually restarted on its own.) Needless to say, I'm still on 4.0.2.
I'm afraid I'm not very familiar with different version names and so forth (e.g,. I don't know what yakju is), but this was a phone that Verizon sent me in December 2011 here in the US.
Here's the information from my "About phone" page:
Model number: Galaxy Nexus
Android version: 4.0.2
Baseband version: I515.09 V.EK05 / I515.EK02
Kernel version: 3.0.8-gaaa2611 [email protected] #1
Build number: ICL53F
When I first got the phone, I immediately unlocked the bootloader and rooted it. I did NOT install a custom recovery, nor did I install any custom ROM.
It sounds like there might be some kind of validation error, but I do not recall doing anything that would make my OS non-stock, except perhaps side-loading Google Wallet, but since that doesn't even require root, I can't imagine that it would have any effect. My Superuser app shows only the following apps to have ever used root permissions: BusyBox Free, Secure Settings, Superuser, Terminal Emulator, and Titanium Backup. I've only used BusyBox and Secure Settings with Tasker to automate certain tasks, but nothing crazy! Mostly, I just need root for Titanium Backup. (I cannot recall exactly what I restored from my stock Gingerbread Droid X, but I was very careful to only restore apps and their corresponding app data--and I avoided restoring any Google-provided apps.) Even my tethering is done through an app not requiring root (SVTP).
Any advice (not requiring that I do a factory reset or flash a custom recovery or ROM) would be greatly appreciated! I'd also like to hear about people who have similar circumstances, but didn't have problems updating (so that I can rule out various factors).
Thank you in advance!
same exact issue here.
A "solution", albeit less than ideal
The OTA update eventually came to my phone naturally, and it still didn't work. (No surprise there.)
I called up Verizon tech support, and they had me do the Google Services Framework workaround to try to force the update again. Of course, it didn't work.
They said "We're going to need you to reset your device." (i.e., to factory default).
I told them that was wholly unacceptable, since I want to make sure that all my settings are preserved. (I'm kind of obsessive compulsive about things being set the way I like them, and Titanium Backup, as great a program as it is, has sometimes caused some trouble for me when restoring system settings, and especially since I'd be doing a restore after upgrading the OS, I was nervous about that option.)
Verizon got Samsung on the phone. They had no advice except "We're going to need you to reset your device." Both the Verizon rep and I told him that wasn't acceptable.
So Verizon's "solution" was to send me a new device, allow me five days to get everything transferred over, and then have me return the old device.
Up side: In case there was something wrong with my hardware or something else got messed up, I get a new device that I can get set up with the exact same settings as the old one.
Down side: The "new device" is refurbished, so there could potentially be some kind of baggage.
The "new device" came with 4.0.2. I booted it up without the SIM card, skipped all the logging in to Google, and immediately started going through the steps to unlock the bootloader and root the device. (I used the Galaxy Nexus Root Toolkit, which worked like a charm on a 64-bit Windows 7 machine I had lying around.) After unlocking and rooting, I logged into the device with my Google credentials and let it restore my settings and apps that I had downloaded from Google Play.
Then, it notified me that the 4.0.4 (IMM76K) update was available, so I installed that, and it worked without a problem.
Then, I installed the SIM card and got the new device activated through Verizon's website for activation.
Then, with both devices side by side, I went through every phone setting and made sure it's what I wanted, I made sure every app was installed (and if it was a non-Google Play app, I restored it through Titanium Backup), and I restored data for apps that don't store their data in the cloud (e.g., various games) through Titanium Backup. (I made a backup of my old device with Titanium Backup and transferred it over to the new device after getting the new one up and running.)
Everything seems to be working just fine, and the "new device" runs a bit faster and smoother than the old device, and that's with both devices rebooting and then going through the exact same "click paths", side by side.
So it's a bit of a hassle, but everyone who has a Galaxy Nexus should still be under warranty, so if you're polite with your Verizon tech support representative, they may be willing to help you out.
Verizon can sometimes be infuriating with their update release schedule and keeping their customers informed, but they sure do a good job accommodating their customers in other ways.
I realize this isn't really a "solution" to the Android man on his back problem, but this seemed to be the path of least resistance for me, and I'm pretty happy with the outcome so far. (It's been less than 24 hours since I got the "new device" set up!)
Other things I realized I should have tried (and still may, before I wipe my phone and send it back):
- uninstalling BusyBox (through the app itself, since it makes modifications to the system) and Secure Settings
- unrooting
Good luck!
My friend who has a nexus has his bootloader unlocked and CWM on it. He got the OTA today on his way into work and like you guys, he has a broken android when he boots up. We can get into CMW but we are unable to mount his internal SD storage onto our computer and he has no ROM zips on his phone. Any advice as to how to get his phone up and running?
Will wiping the system/data fix it? Is there a way to get a ROM like AOKP onto the device outside of CWM?
Edit: After several reboots it decided to just boot into the stock ROM. Really strange. Anyhow, flashed AOKP and all is well now.
Hey guys, let me just start off by saying I have spent almost 8 hours straight today trying to figure this out and dig myself out of a hole I've created for myself, that being said, I'm going to try and be as detailed as possible so you guys know EXACTLY where I am and what I've tried. This post looks long but that's because it is. It's pretty much my entire day's worth of trouble typed out. So just bare with me and see if you guys can help me out here!
I have a T-Mobile Galaxy S4 model: SGH-M919 it has Android 4.4.2. Now on to the problem: I've had this phone for almost a year now and a few months ago I rooted it. Did a simple Youtube tutorial and used Odin to do the work and everything worked out fine. A couple months down the road (yesterday), after using the phone like a teenager, downloading apps and cluttering it up it started to slow down and not run some apps. After thinking about it I decided to factory reset it. All of my contacts, photos, and videos were backed up on Google so I thought "why not?" Well, this is where $#!% hit the fan.. being rooted then factory reset, right before the phone came online it had me answer two questions about the root. Something to the effect of "Do you want to keep root? (This option is not reversible)" I thought since I wasn't using the features I originally rooted the phone for I figured nah just get rid of the root. So the phone did its T-Mobile boot up and started the Initial setup.
Everything up to to this point was fine until I wanted to log in to my Google account during the setup. Please understand that where I am I have full 4G LTE coverage and have access to a pretty fast and sturdy wifi connection. Well, when it came to the google sign in I entered my email and password and it came up with a message reading "Can't Sign in - Can't establish a reliable connection to the server" (believe me i wish that was the only issue) so after reading that, I thought I'd try with my wifi.. nope. Same thing. Since neither my 4g or wifi worked I thought it was Google's servers so I tried again this morning, same thing. (keep in mind at this point i think my phone isn't rooted anymore.) I call the t mobile store and they give me a technical support number, so I call it and I tell them i cant sign into Google. The gentleman told me he cant do anything because he can tell my phones been rooted. Only thing he suggests is to contact Google, well, the customer care number just tells you go to google.com/support and there's nothing there about my problem.
This is where I dig my hole even deeper. I tried another factory reset and up in the top left corner i still see that root text. Even the rooted android symbol pops up before the Samsung logo or t mobile. Since I saw that I thought "ohh it just didn't get unrooted all the way." I look up ways to completely remove a root and a lot of them require plugin your phone into the computer and using Odin to flash a stock firmware on to the device. I went to plug my phone into the usb port but my computer didn't recognize the usb device, having experienced this a long time ago I searched around for the latest Samsung usb drivers and I installed those. Device still isn't recognized. Let me just note before people tell me to use MTP mode or Developer tools> usb debugging or connection mode.. The only thing that happens when plugging my phone via usb is the phone starts charging and my computer makes the trumpet noise like something is plugged in. Other than that, there is NO notification of it being plugged in. The reason i stress this is because I called Samsung technical support at this point and the guy (not gentleman) treated me like a 5 year old and ran me through all of these options after i told him I already did everything he was suggesting, including downloading Samsung Kies 3 and having it install the drivers. It does not pick up the device either.. at this point I looked up ways to remove the root without the computer. I found out you can just go into the root app "SU" or something and theres a remove root option. I jumped on that opportunity and had it removed. I restarted the phone and all the problems still persist, it even still has the root text on the top left when you factory reset it again. However now, even if you factory reset and select the option "keep root," thinking it would bring back the"SU" app it does NOT.
So lets recap. I have a phone that thinks its rooted and even appears rooted to t mobile but doesn't have any of the root apps or privileges or capabilities to fix my Google log in issue (like the host file in filemanager). And I can't re-root to get that app back because none of my 3 usb ports, 3 different usb cables (one being the cord that came with the phone), or any of the ports/cables on someone else's computer will recognize the darn thing to work on that way! I have all these issues that are supposed to fix each other but I can't do any fixing because they cancel each other out too... I'm at a dead end.
In case this isn't the right forum/website/thread/post area etc.. I have this whole message saved in Microsoft Word document so I can repost it anywhere you guys might suggest better results. Any help/advice will be much appreciated.
Hi everyone this my first post here so I'm not sure if it's in the right place. I just made an account on this site because I couldn't find any information on my question.
When I was trying to root my phone I was following a youtube tutorial, so I put my phone into download mode and transferred the root file onto my phone. The program said it was successful each time I ran the program but the phone would not restart like in a video. I transferred the file 5 times before I switched to a different tutorial and successfully rooted my phone without issue.
But now I'm wondering if there are any side effects that can happen to my phone (like battery drain or slowing it down) because of all those files I attempted to root my phone with.
Galaxy s7 android 6.0.1
Any comments are greatly appreciated!
No, don't worry, flashing always replaces all existing files in the file system with new ones.
Sent from my SM-G930F using XDA-Developers mobile app
Thanks for the reply! Is this still true when the successful root DIDNT actually erase any of my phones data? (apps, pictures, settings, and layout)
Re-reading your original question, it now appears to me that you may have installed and executed one or more apps on your phone according to directions in the YouTube tutorial.
Any app can install code that drains the battery or slow down the phone (or do whatever you gave permission to). So if those apps weren't useful, I'd just uninstall them. This would also remove any such code.
If you suspect they do interfere with battery or performance, you may check the battery usage in the settings to verify this before uninstalling.
Basically I bought Samsung Galaxy A5 2017, which was branded. Whilst I was using it the phone had all the operators’ apps and themes which I didn’t want. Also the whole phone was even crashing sometimes and was slow. I found a YouTube video showing how to de-brand my phone, and I’ve managed to de-brand it following some steps, after I have successfully de-branded my phone it automatically installed 7.0 Nougat and it got rid of all the crap inside, and then the phone was faster and smoother. Keep in mind I only de-brand it I did NOT root my phone, I also checked whether it is rooted or not from the root checker.
However as I was playing around with it and I found that I can’t access two apps ‘S Health’ and ‘Secure Folder’, for both of these there is some error message coming up, it says this:
S Health: Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices (0x100030522830)
Secure Folder: Secure Folder cannot be set up because unauthorised software was installed on the device.
I know this is the result of my phone being de-branded and maybe the current software is not compatible, I don’t really know, I have check all around the internet to find if someone has this problem and a lot of people have this issue but the way how to fix it is not clear, I couldn’t find a video which would explain clearly how to fix it and there isn’t much on forums either.
Please if anyone could help me solve this problem, my phone is new and I haven’t got much stuff there so if this problem would be fixed by erasing data like a factory reset then I don’t’ have problem with it, I also don’t mind rooting my phone, but I would prefer to have it unroot at least for now but if there is no other way then I’m fine to root it, it’s just that I need to know how to root it and I have to be sure it’s going to work, because I’ve seen that there are several roots and ways you can do it. Therefore I need to know which one is the most appropriate for this matter. And can I go back to the unroot state after I've rooted my phone?
And also can someone tell me. What if I wait for software update for example new Nougat 7.2 maybe it will fix this problem, or is it better just to fix it now whether or not it has to be rooted and don’t bother waiting. If the new software update can get it fixed and it’s guaranteed that it will. I can wait a bit, it’s not a big deal, but I would like to really use those two apps really soon.
If you have any questions or something wasn’t mentioned please ask.
Thank you for your time