I kept getting a pop up message on my phone saying a new software update is available for my device. It appears to be an Android update MB860 v4.5.141. So I downloaded the update with no problems but the update won't install.
When I clicked Install the phone shut down as it's supposed too. But the update fails and I keep getting a black screen with Android & an exclamation point inside a Triangle. I have to pull the battery and restart but once the phone boots up it shuts down again to attempt to Install the update and again I get the black screen with the Android and exclamation point. The phone is unusable at this point. Any ideas?
My Atrix is NOT rooted.
I just tried the manual update and it won't work because the phone can't start up long enough, it shuts down before I can do anything. How can perform a factory reset if the phone shuts off before I can get into the menu to select factory reset? Will a factory reset even fix this problem?
Hi,
check this:
http://forum.xda-developers.com/showpost.php?p=22636544&postcount=5
Good luck
Thank you for the help. The problem is I'm new to Android so I don't really understand what that post is telling me and I'm a new member here so the forum won't let me post a question there. I don't understand how to boot into CWM or how to format the /cache partition once I get there. Any help would be greatly appreciated.
NY Yankee Pride said:
Thank you for the help. The problem is I'm new to Android so I don't really understand what that post is telling me and I'm a new member here so the forum won't let me post a question there. I don't understand how to boot into CWM or how to format the /cache partition once I get there. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you flashed a custom recovery? If you have, boot into it by holding volume down after turning the device on. Then hit volume down until you have selected recovery. Then hit volume up to boot into recovery. From there, wipe the cache partition and reboot.
If you haven't flashed custom recovery... I dunno what to tell you. It's strange that the OTA update isn't working on a non-rooted, non-unlocked phone.
I don't even know what flashed recovery is. Is that what the post above is about where it explains to boot into CWM and format the /cache partition? Sorry for the newb questions but I'm really lost here and kind desperate because now I'm without a phone.
NY Yankee Pride said:
I don't even know what flashed recovery is. Is that what the post above is about where it explains to boot into CWM and format the /cache partition? Sorry for the newb questions but I'm really lost here and kind desperate because now I'm without a phone.
Click to expand...
Click to collapse
Make sure phone is off.
Press and hold the volume down button, then press the power button.
When text appears on the screen, release the down volume button. Then press the down volume button again and watch the text change... keep going until text reads "Android Recovery". Press up volume button. IF YOU go to far (too many down presses) keep pressing down and it will cycle back...don't press the up volume expecting to go back.
You are now in recovery...if you have a screen with a big triangle and an exclamation point, press both volume buttons at the same time. A menu will appear. Use volume buttons to move to the option you want and the power button to select it. Most likely, you'll want "factory reset". do that.
If you end up with any other screen (not the triangle) then you have a custom recovery and you knew everything I just told you...
Yeah it looks like a factory reset is my only option at this point, I was hoping to avoid that. Thanks for all the help and tips.
I got it working!! I spent about an hour searching google with different search phrases and I found a post where someone had a similar problem about a year ago with a different phone. This is what I did:
-I pulled the battery then booted up the phone by pressing the power button & the volume down button at the same time until "Fastboot" showed at the top of the screen.
-Then I scrolled through & selected "Android Recovery"
-I then selected "Wipe Cache Partition"
-Then I selected "Yes-Wipe Cache"
The phone then restarted and I got a message that the update failed but the phone stayed up and running and has been working fine since. I've since restarted it several times.
So the update did not install but I'm not going to attempt the update again at this point because I'm sure I'll just have the same problem.
I know I said the phone was not rooted but I failed to mention that I did buy the phone used so I don't know what the previous owner did to it. But I did a Factory Reset on the phone when I bought it so wouldn't that remove any previous rooting on the phone if there was any?
NY Yankee Pride said:
I got it working!! I spent about an hour searching google with different search phrases and I found a post where someone had a similar problem about a year ago with a different phone. This is what I did:
-I pulled the battery then booted up the phone by pressing the power button & the volume down button at the same time until "Fastboot" showed at the top of the screen.
-Then I scrolled through & selected "Android Recovery"
-I then selected "Wipe Cache Partition"
-Then I selected "Yes-Wipe Cache"
The phone then restarted and I got a message that the update failed but the phone stayed up and running and has been working fine since. I've since restarted it several times.
So the update did not install but I'm not going to attempt the update again at this point because I'm sure I'll just have the same problem.
I know I said the phone was not rooted but I failed to mention that I did buy the phone used so I don't know what the previous owner did to it. But I did a Factory Reset on the phone when I bought it so wouldn't that remove any previous rooting on the phone if there was any?
Click to expand...
Click to collapse
No. Factory reset does not clear out rooting, unlocking, or any modifications to the bootloader or recovery.
for root: There's a root checker app in marketplace to test root access. If you do have root access you need to unroot before applying the update.
for unlocked: the only way I know to tell is when you power on the phone the word "unlocked" will appear at the top of the screen.
bootloader and recovery: if you have a locked bootloader than you should have stock bootloader and recovery = ok to apply OTA update. If you're unlocked, do NOT apply the OTA update. A few people have succeeded somehow, many do not.
Thanks Gnac. I just noticed when I turn the phone on it does say "unlocked" at the top left of the screen, I never noticed that before. I know for sure the previous owner was using it on AT&T so I don't know why he would have unlocked it. I think I'll just skip the update to avoid any further problems.
I know it's been a couple of months since my last post but I never got the update to work even with the manual update from Motorola's site. I followed the exact directions more than once but I just can't get it to work. At this point I don't really care about the update but the nagging pop up every hour on my phone reminding me to update is getting annoying. Is there an easy way to stop the nagging update pop up that give the option to download now or download later? I always choose later but it nags me probably 20 times a day.
NY Yankee Pride said:
I know it's been a couple of months since my last post but I never got the update to work even with the manual update from Motorola's site. I followed the exact directions more than once but I just can't get it to work. At this point I don't really care about the update but the nagging pop up every hour on my phone reminding me to update is getting annoying. Is there an easy way to stop the nagging update pop up that give the option to download now or download later? I always choose later but it nags me probably 20 times a day.
Click to expand...
Click to collapse
titanium backup's freeze function (you need to buy the paid version) can fix this. Just freeze Updater to stop the pop up.
Thanks for the suggestion but that won't really work for me since I have no experience in rooting and I'm way too worried about bricking it to even try that.
You say you bought your phone used, and haven't rooted or modified it. Are you on AT&T? If so, and were it my phone, I'd be taking it to an AT&T store and having them check it out.
We are great at looking for alternate routes to fix our own stuff and using "official routes" as a last resort (as it requires putting it all back to stock first), but to me, this is a clear case of their own update screwing up for some arbitrary reason -- totally not your fault.
I don't think that will work because the bootloader is unlocked so I have to assume the previous owner rooted the phone. When I start up the phone it says "unlocked" in the top left corner during start up.
Wait for the update but I know that come in 2013 when android world will be jelly bean
Inviato dal mio MB860 usando Tapatalk
Ok I'm sorry to be a pest but I can't take this darn nagging pop up 20+ times a day. Obviously I don't have a clue about rooting but a guy a work with said he could probably unroot this phone for me so I can install the update. My question is if I take the SIM card out & sign into blur will he be able to do whatever needs to be done without a SIM card in the phone? That way I can put my SIM card in an older phone I have so I won't be without a phone if it takes him a few days.
NY Yankee Pride said:
Ok I'm sorry to be a pest but I can't take this darn nagging pop up 20+ times a day. Obviously I don't have a clue about rooting but a guy a work with said he could probably unroot this phone for me so I can install the update. My question is if I take the SIM card out & sign into blur will he be able to do whatever needs to be done without a SIM card in the phone? That way I can put my SIM card in an older phone I have so I won't be without a phone if it takes him a few days.
Click to expand...
Click to collapse
Actually you could probably do this yourself.. search for "Petes Motorola root" then download and follow instructions in how to "unroot"..
Sent from my MB860 using XDA
Thank you for that suggestion. Since I don't have any experience in rooting I'm a little nervous but it seems pretty straight forward. How do I verify steps 1 & 2?
1. Make sure the Motorola drivers are still installed.
2. Make sure USB Debugging is still selected.
3. Connect your Bionic to your computer.
4. Run the Pete's Motorola Root Tools.exe.
5. Select UnRoot My Phone at the bottom.
6. Your phone will reboot 3-4 times as the program goes through all 4 steps in the process.
Related
tl;dr: Interrupted update. cant do jack. tried acer tech support. failed
I grew bored with waiting the two minutes for my tablet to install the new update. so i stood up and hit the power button to put it to sleep like a boss. then i cam back later, the lock screen was unresponsive
i figured out be double tapping the pwr button i was able to unlock the tablet to see the powering down screen (see attachment). I can get to the setting menu, but evrytime i try to mess around in it, the window closes itself.
an interesting note is that the time is wrong, and the battery suddenly went from 100% to 15%
I called acer tech support, and with ther guidance...
pressed the reset button to no effect
powered on holding the pwr & vol- buttons down to get an error (see attachment). then the tablet turns off.
Ive dled some "update.zip" files i found online that are supposedly used to unbrick the tab... but i just got the same error picture(see attachment)
one other thing i tried was to hold the power and vol+ buttons. this cleared a chache, but had no other effect.
I am a noob at droid, but not to tech. i would like to avoid perma bricking, and im unsure about mailing this in. waiting is gay. I would like to restore it to factory settings w/o rooting it etc. as ive never done that before. but im not opposed to installing a CFW if it somes to that...
Im looking for ideas guys here guys. wtf is wrong with this thing?
Haha
Lmao "hit the power button to put it to sleep like a boss", funny ****.
Can't help you though sorry
ive been around he web, and have seen this exact series of symptoms happen to a handful of other guys... i haven figured out a solution yet, and it is looking more and more like ill be sending it in via warranty
my best guess at this point is i have corrupted a crucial system file. as to why i can do jack in the factorys recovery mode... idk. but then again, idk what the factorys recovery mode should look like or how it would function. youtube only shows CWR... which i dont have
if i believed i could anything reasonably withing my abilities, i would... but voiding the warranty on a long shot seems dumb.
still ANY ideas would be great
I too faced exactly the same problem today.. Dunno why this is happening... I am too worried now... Kindly post the solution as you find them...
Am sure calling tech-support is just waste of time..
Thanks in advance..
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
stuck on same screen also!
My friend and i who both purchased this Acer Iconia tab are both having the same problem. We both received a message on the tablets to do the update. We both got stuck and have gone thru tech line and there is no remedy. She was able to return hers within the 15 day period; I on the other hand am a week over that so have to mail it to Acer for repair. I'm thinking this is more than a cooincidence and there is a problem more spread... Acer would neither verify or confirm....
buntzmehta said:
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
Click to expand...
Click to collapse
He said the root of his SDCARD. You can take out the sdcard and put it in a sd cardreader on a computer and copy the file to it then put it back in the tablet. The file worked for him so it might be worth trying. Just have patience while it is loading as some of these updates take a while to load and sometimes you may not see anything happening but it is. The more patches and roms you load on Android the more you'll learn to just leave it alone and let the updates finish. Its pretty rare for updates to be messed up. Its usually people getting anxious and clicking on stuff.
Good luck
Sent from my A501 using Tapatalk
still stuck on shutdown screen any updates?
Anyone had any luck with a fix? If not --sending it to Acer for warranty repair after the hurricane hits..Sure hope this isn't a wide spreasd Acer issue do to the new download. Wish I could just return the thing all together. Worked well while I had it a whole 3 weeks...... Thanks in advance for any information.
npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
Thanks a lot dear npena.. you are simply great.. i was very anxious initially to try your method as no other member here who face the same problem thanked or recommended your suggestion...
I tried it and it worked... I am really very thankful to you...
Cheers..
you are my hero indeed.. thank once again..
BuntZ
Friends, who face this problem you must try it... it just takes few mins b4 you can get your acer tab to work again beautifully without loosing any settings or installed apps... they remain intact...
Yay!
Glad you got it running again - had a similar problem when doing a ota update myself, was so worried I bricked the tab, went thru about 7 update.zip files until I found one that magically worked, letting me get back into the system and flash the correct rom for my region
hi! i have the same problem with my a500. I write a guide to solve this problem. Problem in firmware. here is the gude http://forum.xda-developers.com/showthread.php?t=1572622
Ill start this saying, yes, im a noob. I rarely post or visit unless i have problems.
But i do have experience rooting this specific phone before. But this time around its giving me a LOT of problems...
Ill start with:
Samsung Epic 4g (D700.0.5)
FM 2.3.6 (GB)
BB EL30
K 2.6.35.7
Now i will attempt to explain all the problems as well as what i have done to try to fix them and i will give as many links to the pages that i used for guidance as i can.
As i said, i have experience rooting this specific phone in the past. I ran a stock rooted ROM and everything was fine other then some glitches that i just learned to live with. But about 3 months ago i got a few more problems that have been driving me crazy so i desired to reroot.
When i power down the device, it will not turn back on just by pressing/holding the power button. Removing the battery, reinserting it, and holding the power also dose not work. I finally figured out that i have to remove the battery, replace the battery, then quickly (before the on-screen battery disappears) insert a charging cable thats connected to a power source. Then when the battery turns green (even with minimal power or full power) i can then power it on, but only when the on screen battery shows green. If i wait too long and it disappears it will not work and i have to start over from the beginning. (Removing Battery...) That was the 1st problem.
Soon after this happened (maybe 1-2 weeks) my phone started doing random shutdowns and not powering back on (i assume because it didnt have a power source connected). This would happen at anytime of the day or night, even when it was connected to a charger and actively charging. Yesterday i finally had the last of it and started researching this problem. I found that apparently some/all of the epics have this problem in time. From what i read the micro(or mini im not sure) USB port dosnt fit 100% snugly. So it causes heat. This heat causes corrosion and eventually leads to this problem. (I have never got this phone wet in the 1.5 years i have had it, i take very good care of my electronics.) Around the time this started my phone also would drain its self in about 2-3 hours, this was due to it constantly thinking i was plugging and unplugging it from a computer and requesting that i choose from the 3 options of mass storage.... Eventually the whole screen turning black with the android and the 3 buttons went away but the pop up on the notification bar continued, and as already said, it will drain the battery quickly.
NOW on to the rooting problems.
I dont remember what rom i was running originally, but following a few videos from QBKing77.
I odin'd back to EC05. This went fine no problems. (Useing odin 1.85)
I then tried to use the e4gtauto.zip file and running the "RUNFIRST.bat"
Used option A (install Root not EL13/newer)
Everything went though like it was suppose to. No errors or problems. Phone rebooted into recovery rather then to the lock screen.
Not remembering how to use recovery, i did some research, apparently the camera button is SUPPOSED to be the select button, but this did not work for me at all. After several manual reboots (pulling battery) this was the only thing i could get to (not even download mode to try to flash back to EC05 again). I did some research and found a post that said the "home" button on the front of the screen was his selector for some strange reason. This worked for me. I selected "reboot now" or something like that (the 1st option) and it rebooted into what i was thinking was a rooted rom, checked and there was no SU, or BusyBox (as said would happen in the e4gtauto).
I downloaded an su.zip and figured i would flash it with CWM (last time i installed CWM it was "purple" or 3.1.0.1)
Well it seems that my CWM is gone... i did the ever famous "3 finger salute" of Vol Down + Camera + Power and nothing except that i had to select "reboot phone" again from what i believe is stock recovery. Which booted me back into EC05.
By this time it was late at nite (2am or so) so i went to bed, over night apparently it updated and is now EL30. Thinking this was a good thing (and deff proving im not rooted) so today i tried rooting it as EL30.
Still do not have CWM seemingly.
Also would like to note, inorder for me to get to download mode, i have to take out my SD card, take out my battery, plug in the phone, and hold 1+power when the green power indicator comes on as stated above. This is the only way i can get into DownloadMode (if that helps at all)
If i could get any information on how to root from EL30 i would appreciate it greatly!!!
I will answer any questions as fast as possible, and i will provide as much information as you request when as soon as possible.
Thank you all in advance.
LATE:
Im not able to post links... so i cant give all the steps ive followed so far, I have attempted to take out all infomration already stated related to a link or video... Sorry.
I can do this for you remotely via teamviewer 7 google it and install it pm me the id and password and ill do it all for you
Oh and you used the epic touch one click root... not ours.. and el30 doesn't work on one click root.
Sent from my SPH-D700 using xda premium
As i was writing the above i thought of something. What if i do the same thing i have to do in order to get into download mode to boot into CWM.
No, this dosnt work, it brings me back into the what i believe is stock recovery. I decided to mess with the "install from sdcard" option. I tried the various .zips i have on there and they all fail a signature check.
YourLordAndMaster said:
As i was writing the above i thought of something. What if i do the same thing i have to do in order to get into download mode to boot into CWM.
No, this dosnt work, it brings me back into the what i believe is stock recovery. I decided to mess with the "install from sdcard" option. I tried the various .zips i have on there and they all fail a signature check.
Click to expand...
Click to collapse
You have the wrong recovery installed... you used the epic touch one click root... ... just go get teamviewer and ill fix it for you.
oh but now your on stock recovery because samsung has a script in the kernel to restore the stock recovery upon boot.
The rooting has been fixed.
I didnt install a CWM file apparently
and i also did a lot of bad things
Big thanks to "Big Goron" for the help he provided
I have an Acer 500a I just bought off carigslist. Initially I thought it would be fine but then I realized I was inheriting someone elses problems. I hope someone may be able to help.
Within the first few hours I was noticing google Play crashed a number of times and struggled to update from Market. Somehow the update went through but now there is a system update that won't go through. I'm able to down load it and when i restart the computer to complete installation the screen goes black and says: booting recovery kernel in the corner. I then see a picture of an android and a load bar which after 2-4 seconds the android is on his back and an exclaimation mark is coming out of his belly.
My android version is 3.2
Kernel version
2.6.36.3+
Build number
Acer_a500_7.006.01_COM_GEN2
I'm pretty sure its rooted and i think that might be why its not playing nice with google market and system updates. I called the old owner and explained the problem and he just said he had it rooted and he thought he unrooted it. There is an ap called superuser in aps. (although if it were rooted would'nt I be able to uninstal some of thecrap software it comes with like GOLF HD? -- it won't let me).
The system update is for Acer_a500_7.014.01_COM_GEN2 8.88mb
My problem is all of the force closes I'm getting and the inability to update the system. Any thoughts? I don't have a usb cord to connect it to a desktop either =(
I am a bit out of practice, but...
Should be pretty simple to fix. From what I am seeing, you are running a stock rom. Just because the superuser.apk is installed on the system does not mean it is rooted, but it probably is.
Hit the market, grab "Root Checker" - simple tiny program to let you know for sure if your tab is rooted or not.
https://play.google.com/store/apps/details?id=burrows.apps.rootchecker&hl=en
From what I understand - automatic system updates will fail when trying to apply them to a rooted or modded system. Probably why you cannot auto-update.
My advice at this point would be to:
1) Since you just bought it, just do a factory wipe on it. That will remove all the stuff the prior owner had running on it and will result in a unrooted tab that should be able to get auto updates without a problem.
2) Un-Root it. Once the tablet is unrooted, the system should update without any issue.
As for your Play Store issues - I have never heard of or personally seen any issues caused with installing apps from the store on a rooted device. I have seen a few apps that will refuse to run on a rooted device - but that does not sound like your problem.
I would go with option 1 - just factory wipe the thing. Prior owner may have made tons of changes to the OS that we will never know about, and may have handed you a unstable system. Start fresh. Wipe it out.
Hope this helps you out! Let me know if I can answer any questions.
k thank you so much for the quick reply! I downloaded the root checker and it Is rooted. I did a factory wipe as found in the settings privacy tab when I bought it. That factory reset did not unroot and only cleaned out some of the aps on the device. Is there a better or more surefire way to unroot it? If I reset with the volume down key will it hard reset it?
Thank you for you help!
Draight
Okay.
I am about a year out of practice with my a500 - but from what I am think, if a factory reset still results in a rooted device - the prior user installed a stock ROM that comes pre-rooted.
I highly doubt being rooted is causing the issues you are running into.
At this point if you just want to get back to stock you can probably just install the Acer Recovery Manager from the market and use it to reflash a stock unrooted ROM. Or I see a few guides about how to manually restore back to stock over in the dev section for the a500.
Others will correct me if I am wrong, but I think Acer Recovery Manager should take care of your problem.
Hope this helps!
(Edit: Or you can just download the official stock 4.x rom (ICS) from the dev section and flash that. 3.2 is pretty slow and wonky in my experience, you should be able to just download a 4.x ROM and flash, since you are rooted. Again, I am way out of practice. Don't do anything before reading up!)
(Edit again: I think I was making this harder then needs be. Just flash any stock 3.2 unrooted ROM, done. After you do that the automatic on the air update should kick in for you and update you to ICS)
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
draight said:
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
Click to expand...
Click to collapse
Hmmm..
Try the thread I linked two in my second edit of my last post. You just need to grab the stock and unrooted 3.2 - put it on a MicroSD card as update.zip - then reboot with vol rocker and power switch to get the system to flash the update.
That *should* work just fine.
(Edit: Forgot the link! http://forum.xda-developers.com/showthread.php?t=1839313 - there you go)
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
draight said:
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
Click to expand...
Click to collapse
Nope. Just snag the stock unrooted 3.2 ROM - place it in the root of the MicroSD card as update.zip
Power down.
Power up with VOL + and POWER key held at the same time (you can let the vol rocker go when you see text appear in the upper left corner)
Should be all you need to do. Worst case; it does not work and returns you back to where you are now. Worth a shot.
If that does not work, let me know so I can do a few mins of homework and help you further. Been a long time since I have changed ROMS or had any issues with my a500.
I have bricked it twice by not following directions all the way or just making simple mistakes, but from what I have found there is always a way to recover.
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
draight said:
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
Click to expand...
Click to collapse
Hmmm. Odd.
Like I said, I am rather out of practice.
Someone more experienced them me: please help me point Draight in the right direction here?
Thanks for trying to help. =(
I wish that my tablet wasn't having such issues. I;m going to try to scramble around the forums and see if I can find some advice...If anyone has a suggestion please let me know.
Thanks again entropy,
Draight
Update:
So I've been tinkering around with it a bit more and I found a usb cord that plugs it into my computer. I keep finding boken links on this site so Im struggling to find an update I can use to flash to. I downloaded a different super user program which allowed me to temporarily unroot my device. I then restarted it and no root checker says its no rooted and I cannot find the superuser program. I think I have somewhat unrooted it -- but I think the real issue now is the recovery tool. I keep reseting it - hard reset, or factory reset and it wipes everything away but when i try to update it gets about 1/3 of the way up the bar then it stops with an '!' Mark above the droid. Im kind of annoyed at this point and hoping for some new links or some ideas on how to repair the recovery piece.
Draight
Go to the Dev section, and grad a couple of the ICS Update roms. You will see them listed for the a500. Make sure they are the FULL update roms. Should be about 3-400mb. These contain a FULL ICS Update Rom, and not a patch file.
http://forum.xda-developers.com/showthread.php?t=1816560
Then, go to the Themes and apps forum. You'll see a sticky that has the Acer Update Decrypter.
http://forum.xda-developers.com/showthread.php?t=1869505
Now, unpack the decrypter, and select one of the ICS Updates. Then hit Start. Take a couple minutes, but you will have a duplicate file with the word "decrypted" added to it.
Wait, you are not done yet.
Using a program like 7zip, or even Winzip, open the decrypted file. DO NOT EXTRACT, just open it and pull the update.zip to your PC's desktop.
Copy that update.zip file to your Ext SD Card of the tablet. Don't be putting it in any folder, just copy it to the root of the card.
Now, you still ain't done.
With the tablet off. Press and hold Vol+ and then PWR. Hold them both untill you start to see text about installing blah blah blah, then release the buttons.
If it completes, and you can reboot into ICS, then you are good to go.
If something fails during installation, then decrypt the other update Rom file you downloaded, and do the same procedure. Usually one of the 2 or three should work for you.
Note these are for the a500, and not the a501.
One more thing. It's advisable you get your UID number before doing these things. You probably won't need it, but it's nice to have written down in case you need it in the future. Inf to get it is at;
http://forum.xda-developers.com/showthread.php?t=1624645
MD
Thanks! I am downloading a few of the FULL ICS roms:
*Acer_A500_1.031.00_WW_GEN1 : http://d-h.st/uAy
Acer_A500_1.031.00_PA_CUS1: http://d-h.st/idO
Acer_A500_1.041.00_WW_CUS1: http://d-h.st/Yt5
*Acer_AV041_1.054.00_WW_GEN1: http://www.theandroidcollective.org/...00_WW_GEN1.zip
*Acer_A500_7.014.16_041.206.01_COM_GEN1: https://docs.google.com/file/d/0B_bk...hVc1RVcHc/edit
The I downloaded the ones ending with Gen1. Once they are downloaded I will continue with the instructions. Thank you so much for your help! I will post how it goes later tonight.
Draight
I just decrypted both:
*Acer_AV041_1.054.00_WW_GEN1:
*Acer_A500_1.031.00_WW_GEN1
Both get get to the third bullet quickly and the bottom says DONE! It takes like 4 seconds. I don't think the Decryption key of $12 is working
[*] Opening file: Acer_A500_1.031.00_WW_GEN1.zip
[*] Decrypting using key $12
[*] Writing decrypted file: Acer_A500_1.031.00_WW_GEN1_decrypted.zip
I try to extract something from the decrypted file and it says the file was not downloaded properly and I should try redownload it...it says its not a proper archive
wahoo!
So that worked! I down loaded the file Acer_AV041_A500_1.033.00_PA_CUS1 and extracted the update. I palced the update on the sd card and booted with the power and sound volume pressed down. it went through the installation procedure and restarted twice before saying it was upgrading my aps and BOOM its got ICS and everything looks great. Thank you so much for your help and I hope that this paper trail is able to help someone in the future
My problem is that I'm on ICS and I'm rooted, but I just can't download a custom recovery. I've tried, and I haven't gotten anywhere
Sent from my SPH-L710 using Tapatalk 2
*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Thank you for the info! Does sound like an awful lot of work though
jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.
shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Does sound like an awful lot of work though
greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...
With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.
sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!
I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.
jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.
I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html . From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight. From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight.
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
bryantjb said:
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
Click to expand...
Click to collapse
I don't want to give you useless information, but make sure you're using the right steps to get into download mode.
1) Power off your device
2) Remove battery for 10 seconds
3) Replace battery
4) Hold POWER + HOME + VOLUME DOWN until you see the "Warning" Screen
5) Quickly hit the VOLUME UP button.
Then you can connect to ODIN, and go from there.