Related
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?
Hi y'all, i recently within the last month 2 months taken up a very unsual craving for delving deeper into my technology, with that being said. my tab 4 7.0 sm-t230 i Downloaded an app called "lucky patcher" was messing with it, been reading about deoxe(ing) my tablet,it gave me the option to do it for me (usually i enjoy the challange of using a emulated terminal and what not) but every file etc would take too long, and it worked, my daughter ot well over 150 million score on subway surfers etc. i notice my phone sluggish even bein over clocked, I/Os that i did myself, running max cpu and performance i could blabber forever since my 3 kids arnt interested in my newly found hobbie and my husbands a truck driver, i'm getting it out here (i'm sorry but i do need help) so anywyas i decided to kick her into recovery and begin to just manually delete all the dex copied files through TWRP went good till i wetn to reboot after staring at my screen for 3 hours and got threw up on twice from sick babies and i was boot looped. i decide to restore a previous freshly flashed rom/root backup. well they were deleted too. and all i could do was a master re format i think is what i read it was called, and excited to get back and re download everything i notice i now have no OS and no recoveries and TWRP fulll of emptiness. i can play through TWRP i've changed file permissions i've tried everything ive read and tried everything i learned and experianced to fix this issue, and yet stillno idea how to fix this issue..
Now the fun part is my set up. the only pc i have means and access too is my samsung Chromebook, and my tablet, that's it, no phone because my tablet handles everything my little heart can desire.
needless to say, i need some kinda recovery tool kit i can use via my chromebook, that'll allow me to use ADB for chrome (which another question i have is how do i enable my tablets USB debugging if i can't get into the phone?) so toolkit for chromebook for a ADB side load if possible. or some way to do it through my emulated terminal in TWRP,. my minds rushing, i'm confused and my over emotionally stressed female head is killing me without my tablet. (drive to any town where i could use anything but my chrome book. 3.5 hours.
sorry i pray this post doesnt get deleted. I need help because my tablet is my main source of income being in real estate when i'm back in town once a month. never made a page or a forum or anything like this usally google magic does it. but 3 days and countless mind numbing forums i've given in.. please help me! i'll donate pay something idc at this point. -a pissed off irish southen woman on the verge of pms and a meltdown thanks in advance i'll try to reply as fast as humanly possible, ill be up for awhile tonight going through more posts.
0well with a little more tinking around, i think i have found the issue as too why no matter what i do i'm unable to boot a rom/os. mt EXT3 wil not mount my system i'm clueless as to how to fix that at all threw TWRP, anyone have an idea of any kind please? i'm for anything, even if after more attempts and countless hours, i'll record me skipping it across my lake, and we'll all take guesses as too how many skips it'll do. hopefully my dog will fetch it if i throw at the wrong angle. (completely dumb jokes are the only thing keeping me from returning Sain.) we all cant be too serious. please very interested on how to fix this issue tho.
s,
you need to get a custom rom zip onto an sdcard, check development section.
in twrp, flash the rom,
if the rom still doesn't boot, then reboot to twrp again and use the format data option, then reflash rom and try again.
twrp terminal sucks, you can try flashing aromafm https://www.androidfilehost.com/?fid=95916177934547314
this is for the marvell variant, it may work for the msm/qcom variant.
stop using lucky patcher.
m
moonbutt74 said:
s,
you need to get a custom rom zip onto an sdcard, check development section.
in twrp, flash the rom,
if the rom still doesn't boot, then reboot to twrp again and use the format data option, then reflash rom and try again.
twrp terminal sucks, you can try flashing aromafm https://www.androidfilehost.com/?fid=95916177934547314
this is for the marvell variant, it may work for the msm/qcom variant.
stop using lucky patcher.
m
Click to expand...
Click to collapse
Hi, that's where another problem lies within, I have no way of communicating with the phone or being able to do much, considering the only pc/laptop i have access too is my chromebook, and this thing is a ssteaming pile of regurgitated dog bile. if theres one regret in life.. buying this thing.. even dual booted i still can't process the zips or compile them properly, maybe i need to find out how to build a zip file from scratch and comepile the corresponding stuff myself in small hopes it'll work on this chromebook
and yes, never again will I use that. it worked don't get me wrong. but then it decided to deodex my system to oblivion.
s,
hey that rhymed !
your alternative is to use a usb thumbdrive and an otg cable , else nada.
m
moonbutt74 said:
s,
hey that rhymed !
your alternative is to use a usb thumbdrive and an otg cable , else nada.
m
Click to expand...
Click to collapse
I'm gla you have a sense of humor, thank you hun. looks like i'm tabletless until i go back into town in two weeks ): i suppose till then i will tinker with it some more and unlock the universe, or find a way to convert zips that are made for windows or mac and be able to convert it to be able to be used and transfered unto the phone. Chromium os or chrome now has ADB for chrome as an extension but very iffy, has 3 options to screen record/screenshot and terminal. i was able to use vitural box for about 2 hours and force odin to pretend i was on a widnows enough to orignally root, then it crashed my chromebook. Maybe i've gotta achieve 88 mph first to get this thing to work? lol my chromebook "overclocked" 810 mghz.... maxx.... frequency says it can go to 2100... i think if i even try that i'd recreate the "hydrogen bomb"
Hello guys,
Here is a long story, interesting to read maybe for some.
I had android 4.3.2 on my Note 3 N9005, for 2 and a half years now. I rooted the phone as soon as it came out. Had many applications which ran smoothly on it, schreenshots/screenrecorders, xposed installer with a lot of mods.. etc.. everything worked fine. Until the last few months, where suddenly "some application" stopped working. I began to have that message, more and more often, and on different applications. I thought, it was time to run a factory reset. BUT I remembered that I ran into some applications on Play Store, which couldn't be installed, since I had an old android version.
So, now, I thought, maybe it was time to try a custom rom. So I installed LiquidSmooth, (android 5.1.1). Nice jump, I must say, many things different, than 4.3.2. Some problems though, the sound was with interference, and some apps just froze. Some games I was playing, just froze.
Then I thought I try another ROM. Found a page with best ROMs, for 5.1.1 and saw that LiquidSmooth only had like 4.8% of the votes, while Nightly had like 40% of the votes and was much more stable (well, according to that site). So I thought I change. BUT, then I saw, that I could actually update to 6.0.1 with Ressurection Remix. So I thought, wow, lemme try that !
So I did. I installed Ressurection Remix, and I must admit, it looks damn good. Even bought the swift dark theme, and it is beautifull. It is candy for the eye. God damn, almost like the 3D cube I played with in Linux a few years back. But some of my games, still freeze. - And as you can guess, I do not like that.. I also got the message on boot: Kernel is not seandroid enforcing.. and I know it's normal, but still I do not like it. (I want everything to be perfect). And with some games, not being able to run, I got tired of RR.
So now, I was thinking, what if I could switch back to 4.3.2? I should have run maybe a factory reset on 4.3.2 instead of trying ROMs, at least my stuff was working. So I thought I get the original stock firmware, and just flash it with ODIN. So, it should be good.
Now I know that on a lot of threads here on the site, people mention that you can't downgrade android. Well, at least not from 6.0.1 to 4.3.2. Because ODIN is not working in 6.0.1 and other stuff.
BUT, I think this: I have a backup, with CWM, for 4.3.2, which I know works, (since I used it a few times).
So, what if I run that backup and get my phone back to 4.3.2.? (again, some ppl here on site, that they accidentally downgraded from 4.4 to 4.3, then they could't upgrade back to 4.4).
So my question is: I use CWM to restore the 4.3.2 backup, THEN in the phone with ODIN I run the original full stock firmware?
Then later, I could unlock bootloader and root my phone again if I want to try something. Would this be possible?
A second question, which I have is: Before I upgraded to lolipop and marshmallow, i ran of course a factory reset, reset cache and dalvik from CWM. But still, now, where I am on 6.0.1 I still saw some folders of some programs I had on 4.3.2. How is that possible? The programs are not in the menu, but the folders are on phones memory. Shouldn't they have been deleted on those 3 resets from CWM? (factory, cache and dalvik?). This is also a reason, for why I would want to return to original stock firmware. Cos I could root my phone right away again, and then upgrade to some rom, so those programs do not come along, and I would have a clean rom. Or with other words, the phones "user" memory, /storage/emulated/sdcard0 - could I just delete it all? I mean the operating system is on root, this directory /storage/emulated/sdcard0 is usually what the user installs on the phone, am I right?
And last question, cos I am greedy for answers. The samsung pen, is of course not working, and I miss it. Any app to install or flash to get the pen alive again?
Thank for your time ro read this Hope u can help ))
Please somebody help. I am also interested.
Wao, boy it was a real long story. And I read it all.
LordTicut said:
Hello guys,
Here is a long story, interesting to read maybe for some.
I had android 4.3.2 on my Note 3 N9005, for 2 and a half years now. I rooted the phone as soon as it came out. Had many applications which ran smoothly on it, schreenshots/screenrecorders, xposed installer with a lot of mods.. etc.. everything worked fine. Until the last few months, where suddenly "some application" stopped working. I began to have that message, more and more often, and on different applications. I thought, it was time to run a factory reset. BUT I remembered that I ran into some applications on Play Store, which couldn't be installed, since I had an old android version.
So, now, I thought, maybe it was time to try a custom rom. So I installed LiquidSmooth, (android 5.1.1). Nice jump, I must say, many things different, than 4.3.2. Some problems though, the sound was with interference, and some apps just froze. Some games I was playing, just froze.
Then I thought I try another ROM. Found a page with best ROMs, for 5.1.1 and saw that LiquidSmooth only had like 4.8% of the votes, while Nightly had like 40% of the votes and was much more stable (well, according to that site). So I thought I change. BUT, then I saw, that I could actually update to 6.0.1 with Ressurection Remix. So I thought, wow, lemme try that !
So I did. I installed Ressurection Remix, and I must admit, it looks damn good. Even bought the swift dark theme, and it is beautifull. It is candy for the eye. God damn, almost like the 3D cube I played with in Linux a few years back. But some of my games, still freeze. - And as you can guess, I do not like that.. I also got the message on boot: Kernel is not seandroid enforcing.. and I know it's normal, but still I do not like it. (I want everything to be perfect). And with some games, not being able to run, I got tired of RR.
So now, I was thinking, what if I could switch back to 4.3.2? I should have run maybe a factory reset on 4.3.2 instead of trying ROMs, at least my stuff was working. So I thought I get the original stock firmware, and just flash it with ODIN. So, it should be good.
Now I know that on a lot of threads here on the site, people mention that you can't downgrade android. Well, at least not from 6.0.1 to 4.3.2. Because ODIN is not working in 6.0.1 and other stuff.
BUT, I think this: I have a backup, with CWM, for 4.3.2, which I know works, (since I used it a few times).
So, what if I run that backup and get my phone back to 4.3.2.? (again, some ppl here on site, that they accidentally downgraded from 4.4 to 4.3, then they could't upgrade back to 4.4).
So my question is: I use CWM to restore the 4.3.2 backup, THEN in the phone with ODIN I run the original full stock firmware?
Then later, I could unlock bootloader and root my phone again if I want to try something. Would this be possible?
A second question, which I have is: Before I upgraded to lolipop and marshmallow, i ran of course a factory reset, reset cache and dalvik from CWM. But still, now, where I am on 6.0.1 I still saw some folders of some programs I had on 4.3.2. How is that possible? The programs are not in the menu, but the folders are on phones memory. Shouldn't they have been deleted on those 3 resets from CWM? (factory, cache and dalvik?). This is also a reason, for why I would want to return to original stock firmware. Cos I could root my phone right away again, and then upgrade to some rom, so those programs do not come along, and I would have a clean rom. Or with other words, the phones "user" memory, /storage/emulated/sdcard0 - could I just delete it all? I mean the operating system is on root, this directory /storage/emulated/sdcard0 is usually what the user installs on the phone, am I right?
And last question, cos I am greedy for answers. The samsung pen, is of course not working, and I miss it. Any app to install or flash to get the pen alive again?
Thank for your time ro read this Hope u can help ))
Click to expand...
Click to collapse
Hi friend.
I think you asking: I installed Android MM and It's possible to downgrade 4.3 via Odin tar.md5 flash installation?
I answer: Yes, i think i like you (or you like me). I love use all rom as possible as quickly, but i tired from "system" process not respond and sound quality issue.
I say you ITS POSSIBLE. because i flash via odin anytime (my stock firmware .tar.md5). Even from android mm to 4.3, lollipop > kitkat, v5.1.1 port rom > v5.0.
You can try, first time i'm newbie on XDA, there said something like bootloader. I now said, its necessary (important), just not too for Flashing Stock ROM.
I hope this little helps to you...
Good luck, i'm now Android MM!
Now i searching for backing knox to 0x0.
Via CWM not ODIN
Thanks dalisoft for answering.
My question was actually if I could restore my backup I made with ClockWorkMod a few years ago.
dalisoft said:
Hi friend.
I think you asking: I installed Android MM and It's possible to downgrade 4.3 via Odin tar.md5 flash installation?
I answer: Yes, i think i like you (or you like me). I love use all rom as possible as quickly, but i tired from "system" process not respond and sound quality issue.
I say you ITS POSSIBLE. because i flash via odin anytime (my stock firmware .tar.md5). Even from android mm to 4.3, lollipop > kitkat, v5.1.1 port rom > v5.0.
You can try, first time i'm newbie on XDA, there said something like bootloader. I now said, its necessary (important), just not too for Flashing Stock ROM.
I hope this little helps to you...
Good luck, i'm now Android MM!
Now i searching for backing knox to 0x0.
Click to expand...
Click to collapse
LordTicut said:
Thanks dalisoft for answering.
My question was actually if I could restore my backup I made with ClockWorkMod a few years ago.
Click to expand...
Click to collapse
Yes, you can restore nandroid backup if you have CWM.
But, remember, before restoring you should to do some steps:
1. Wipe data/factory reset
2. Wipe cache
3. Advanced > Wipe dalvik cache
4. Mounts > Format /system
5. Mounts > Format /data
Allright, thanks Dalisoft.
Do you know by the way, if CWM also takes a copy of EFS? I mean EFS is a system directory, so is it included in the nandroidbackup by CWM, right? So if I restore that backup, I will have my EFS exactly as it was, just after I rooted my phone. (not because something is wrong with it, but in case sometyhing is altered, it will be back to normal, right?).
I mean, there are 2 partitions on the phone, the ROM and the recovery. And CWM does an exact image of the ROM partition, so I would assume that the EFS folder is there too. But I am not sure, that's why I am asking.
Guess I am happy and lucky I made a backup with CWM right after root..
CWM also takes a copy of EFS?
Answer = NO .
http://forum.xda-developers.com/showthread.php?t=2698639
http://forum.xda-developers.com/showthread.php?t=2481255
JJEgan said:
CWM also takes a copy of EFS?
Answer = NO .
http://forum.xda-developers.com/showthread.php?t=2698639
http://forum.xda-developers.com/showthread.php?t=2481255
Click to expand...
Click to collapse
JJEgan
You are right, I posted this thread in the wrong forum. I am deeply sorry for that. I just wanted quickly an answer. It won't happen again. ( I saw in the meantime it has been moved, so I guess everything is good)
Cheers !
Note: Moved thread
Hey guys,
Sorry to be one of those d**ks who registers and first post is asking for help >_<
Take a seat and join me on this epic quest of failure, which has been my life for the last 12 hours.
Had this phone since release, over the years it has got more and more bogged-down with crap, even from the word go it had tonnes of bloatware installed, but I always avoided the temptation to root, just because I didn't want the hassle if something went wrong... lol.
Yesterday decided to finally take the plunge and root it, whatstheworstthatcouldhappen.jpeg
Here's how it went down....
1. Kingoroot via PC (first tried the apk but it wouldn't work).
2. Hated all the additional stuff that had been added to the phone (new wakeup screen with ads etc)
3. Used a guide to remove and replace kingoroot (kinguser, kingroot, kingmaster) with superuser. zidroid dot com/how-to-get-ride-and-replace-kinguser-with-supersu-app/ <<Here's the guide
4. Stuck on "Installing, please wait" (just after step 8 in the guide)... as the guide explains, if this happens then reboot. So I did...
5. Phone now won't get past the samsung logo (I die a little inside).
6. Google crap for a few hours (Boot into recovery mode etc) I clear cache, remove data.
7. Try loading a stock rom I downloaded and opening it from the sd card... no joy
8. Try Kies... no joy
9. Try Odin... no joy
10. During all of this frantic messing around I loose the option of booting into recovery mode, now I can only get to download mode.
11. Basically spent about 6 hours last night and a few hours this morning trying to get this fixed from all info I could find online... STILL NO JOY.
So now I'm biting the bullet and having to own up to the public, that's you guys.
Anyone here got a clue as to what may have gone wrong/what I can do to resolve this?
Not even fussed about keeping the phone stock, just need it running something!
As I'm sure you can tell I'm new to messing around with android, but I'm not entirely tech-naive so hopefully with some help I might be able to get this back to more than just a paperweight?
Cheers!
Altum said:
Note: Moved thread
Hey guys,
Sorry to be one of those d**ks who registers and first post is asking for help >_<
Take a seat and join me on this epic quest of failure, which has been my life for the last 12 hours.
Had this phone since release, over the years it has got more and more bogged-down with crap, even from the word go it had tonnes of bloatware installed, but I always avoided the temptation to root, just because I didn't want the hassle if something went wrong... lol.
Yesterday decided to finally take the plunge and root it, whatstheworstthatcouldhappen.jpeg
Here's how it went down....
1. Kingoroot via PC (first tried the apk but it wouldn't work).
2. Hated all the additional stuff that had been added to the phone (new wakeup screen with ads etc)
3. Used a guide to remove and replace kingoroot (kinguser, kingroot, kingmaster) with superuser. zidroid dot com/how-to-get-ride-and-replace-kinguser-with-supersu-app/ <<Here's the guide
4. Stuck on "Installing, please wait" (just after step 8 in the guide)... as the guide explains, if this happens then reboot. So I did...
5. Phone now won't get past the samsung logo (I die a little inside).
6. Google crap for a few hours (Boot into recovery mode etc) I clear cache, remove data.
7. Try loading a stock rom I downloaded and opening it from the sd card... no joy
8. Try Kies... no joy
9. Try Odin... no joy
10. During all of this frantic messing around I loose the option of booting into recovery mode, now I can only get to download mode.
11. Basically spent about 6 hours last night and a few hours this morning trying to get this fixed from all info I could find online... STILL NO JOY.
So now I'm biting the bullet and having to own up to the public, that's you guys.
Anyone here got a clue as to what may have gone wrong/what I can do to resolve this?
Not even fussed about keeping the phone stock, just need it running something!
As I'm sure you can tell I'm new to messing around with android, but I'm not entirely tech-naive so hopefully with some help I might be able to get this back to more than just a paperweight?
Cheers!
Click to expand...
Click to collapse
Your mistake was using Kingroot.
Use CF-Auto-Root next time.
And what does "Try Odin... No joy" mean?
Did it fail or did it successfully flash and still didn't boot?
The procedure to flash with Odin is something like:
Download a stock ROM (should have the .tar extension)
Get a good USB cable (preferably the original one) and connect it to a back USB port (any other ports can cause problems) and to the phone.
If flashing fails, try a gain.
You could have avoided this had you just downloaded the correct cf-auto root file and flashed it via Odin..