Hi there!
I own an Acer Iconia A500. Originally came with HC3x, updated it all the way to ICS. Rooted it at ICS with this method:
http://forum.xda-developers.com/showthread.php?t=1546593
Worked fine. The only issue is accessing Recovery at boot. (Just in case I plan on restoring the Stock version of Android, for warranty).
I first used the Acer Recovery Tool app at the Play Store. I tried one of the Recovery options listed. CWM for start. Backed up as asked, then rebooted into recovery. I was told "recovery verified failed". Did a restore, tried another method, same crap, with a time the bot with the (!) appears. Did some research on the issue, and came up to this thread:
http://forum.xda-developers.com/showthread.php?t=1622425
I did option 1 (Afterota v1.09). And flashed Recovery Twp 2.1.3/Bootloader.
I reseted back to bootloader, it didn't show "Recovery verified failed", but instead I got the bot with the (!) again. Went back to Acer Recovery tool. Bottom shows that its unable to identify the installed recovery. So I tried TWRP 2.1.3, didn't work.
My question is, how can I get this to fix? This is my first time trying to install a bootloader. Please help me step by step to get this situation fixed. I appreciate the help by any!!
i am having the same issue and have tried several different fixes without success... any suggestions would be greatly appreciated!
(the only one I haven't tried yet is 'manual flashing' outline here http://forum.xda-developers.com/showthread.php?t=1622425... will give this a shot when I get a chance and report back... from all the 'automated' or gui methods it always seems to get stuck at the flashing/copying stage...)
thanks!
Same issue...
Glad I'm not the only one with this issue... Used the exact methods you did, same results. Amazing!
i think part of the problem may be that the bootloader was not unlocked when the initial recovery was flashed? when i rooted i thought I had properly unlocked the bootloader as well, but perhaps not....? (... i thought i read somewhere that if the bootloader has not been unlocked when you flash recovery these are the results.. so i am assuming that this might have something to do with the issue?)
the question is, is there a fix?
i have been playing and experimenting more on the tf101 side... all the stuff i'm doing with this is for my wife's a500 because she liked some of the features on my tablet... i'm not all that familiar with the A500 (didn't have to deal with bootloaders separately on the tf101) so any help is greatly appreciated!
thanks!
Alright. I seem to have got it all fixed. What I did was, went back to this page:
http://forum.xda-developers.com/showthread.php?t=1622425
Went to the "Automated flashing tool" / "USING blackthund3r ATX flash tool , It makes it all a little easier !" Method (below Option 2, in the middle). Downloaded V8-TWRP_2.1.3_ICS_recovery.a500apx and APX-FLASH-Tool & Manager, and followed the instructions.
It didn't work with Windows 8 RTM, (driver issue with APX), but Windows 7, worked perfectly, after downloading the Acer driver from a link in the app when prompted. All worked well.
hope u guys got sorted....
for others reading this
to install recovery from ICS you must first flash the unlocked boot loader, after that u can use Acer recovery installer, although once unlocked most of us use fast boot or the auto tools to do it
Hello, so I am having a bit of a crisis. LEt me start by giving a brief description of what has been done to the phone...
LG G2 ATT (d800) running 4.4.2 OTA.
Was rooted AFTER the OTA update.
I tried to install a custom recovery first by using ROM Manager to install from the phone itself. The stock recovery was intact as of this point, as ROM manager just flat didn't work. My next move was to follow the thread found here...http://theunlockr.com/2013/11/03/fla...ersions-video/
That is were I started seeing issues. The phone no longer was able to boot into recovery at all. I received the "secure boot error". So I took another approach.
I followed the post found here... http://forum.xda-developers.com/show....php?t=2582142
This is where I am now. The phone is stuck on the LG boot screen. I suspect my problem began when I used the files found on that post for the d802 instead of my d800. However, ubuntu will not recognize my phone now. Download mode will not help, it appears.
I think the solution may lie in the post found here... http://forum.xda-developers.com/show....php?t=2432476
The issue I am seeing with this is that I cannot see the COM ports within device manager to set the correct port. I will post in that thread as well, just to reach as many people as I possibly can.
WHAT DO I DO.
Thank you for your future help.
I've recently found away to fix a Galaxy S5 Active stuck in a boot loop. (This method only works if your device is on lollipop 5.0! )
Note: This method only works on the OC5 update.
More firmware support coming soon.
What happened: I accidentally made my Galaxy S5 Active get stuck in a boot loop. I couldn't find a solution for the longest time because the bootloader is locked. Time passed and I eventually found away to fix the boot loop if your devices is running Lollipop 5.0!
Solution:
1. You should always try to fix the boot loop by booting into recovery mode by holding down the Home+Volume-Up Key+Power button. Once the phone logo pops up on the screen releases the power button only, but continue to hold the Home+Volume-Up Key. If it worked is should say "Booting into recovery." or something along those lines in blue letters.
Once you're into recovery use the volume keys to navigate Up and Down. Find wipedata/factory reset. Select it with the power key and navigate down to Yes. Wait till it finishes. Then see if that fixed the problem. If not proceed to next step
2. Since the boot loader is locked it's really difficult to flash any kind of Recovery, ROM, or Stock Rom unless your phone accepts it as a valid file. So here's what you do!: (Method 1)
Download this file and save it to your desktop: https://drive.google.com/open?id=0B3UBRFq3BojVQnBSc3lCSzloYUU
Download ODIN v(3.09): http://odindownload.com/Samsung-Odin/#.VgiJ_8tViko - Extract it to your desktop.
Put your phone in download mode. (Note: Before you do this, install the correct drivers for your phone to your computer.)Make sure your phone is completely off and Hold the Home+Volume Down+Power. You will get a warning message just press the volume up key to continue.
Go to desktop and launch ODIN. After ODIN pops up, plug in your device. (Make sure you have the correct phone drivers installed)
You should see a dialog box in ODIN that say 0:[COM6] in blue. Note: It might be different for everyone, just make sure it says COM.
After that, Under "File [Download]" click "AP" Then navigate to the file you downloaded earlier called "boot.tar"
MAKE SURE RE-PARTITION IS UNCHECKED!
Leave everything else alone then click start. Wait till it says PASS! in green letters in ODIN!
(Method 2):
Go to this link download it to your desktop and follow the instructions: https://drive.google.com/file/d/0B3UBRFq3BojVdXlSUE43VzJPbEU/view?usp=sharing
Done! Your device shouldn't be in a boot loop anymore! If you have any questions let me know!
Note: Once this process is complete, your phone will permanently show a warning in your notifications saying "Unknown action detected." This happens because your phone will detect that your kernel was modified so if you don't want this to happen, then I suggest you wait for a official lollipop OS release.
UPDATE!: You should now be able to download the "Boot.tar" file. Sorry about that!
UPDATE!: New files and instructions added if the first method didn't work!
Having some major issues
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.
Ghujii said:
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.
Click to expand...
Click to collapse
New method for you...
irontaco1 said:
New method for you...
Click to expand...
Click to collapse
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?
Ghujii said:
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?
Click to expand...
Click to collapse
I'm glad you got past your Bootloop! If you need anymore help let me know.
Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active
I'd say hold off for a while I did that exact 5 Hong with the s5 active and it bootlocks it. You need to, if you're going to do this install and use safestrap to di so and BACK UP EVERYTHING with safe strap to SD. As long as you follow those method you SHOULD be able to even soft brick it and come back from it.
shadavis08 said:
Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active
Click to expand...
Click to collapse
I haven't found any successful way to to go back to Kit Kat or 4.4.2 for this phone. In fact that's why this thread exist is because people who have tried to flash back to 4.4.2 have failed and got stuck in a Bootloop. So if you plan on trying to find away make sure you back everything up and if you fail you can use this tutorial to get your phone working again.
Make sure you have "USB Debugging" on
Make sure you have the drivers for your phone installed on your PC before you start the process of looking for a root.
Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
shadavis08 said:
Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
There should not be anything attempting to download when you boot into ''download mode'' if there is, its highly likely there are still particulates of the last bad flash. I would as he said above, enable USB debugging and the like, and install safe strap to be safe. After safe strap is done and youve followed the tutorial which you can find in another thread on this site, boot your phone down and then power it back on, safe strap should come up first, when it does so push the ''recovery'' option to enter safe strap( someone correct me if thats wrong, my phone is currently dead/charging so i cant check) From there you can back up to an SD card, make sure you enable compression when you do.
Once thats done, WIPE YOUR PHONE, and Cache,( maybe dalvik as well if you cant find it dont worry.)and its all on SD CARD, then attempt to dirty flash( I dont recommend), or clean flash your device WITH safe strap. This typically entails downloading a .zip file and opening it THROUGH safestrap, which is done the same way as backing up your data, only via another option in the menu. Simply put; Back up data with safe strap, after thats done push back and choose FLASH, it should show you all available items it can flash from/to, pick and pray. I didnt go this route when I tried, I attempted to brute force the Bootlocked S5A, and it caused some errors that I now have reversed after much pain. If I HAD safe strapped, It may have went smoother for me, and may for you. Safestrap for us Samsung users is the same as Clockwork Mod for the rest if you weren't aware.
I'll edit this when my phone charges and I can walk you through appropriately, if need be MSG me and Ill do it as soon as I receive the message via this thread if I have not already.
hi guys! good day! i have tried the new method twice! and odin fails everytime! the problem is with the modem.bin! is there any way to fix this?
Make sure you're running lollipop and not Kit Kat and make sure you have the correct phone model. If you don't meet both those requirements then it won't work.
it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1
abatoir said:
it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1
Click to expand...
Click to collapse
Yeah that information is correct. You might want to download the latest version of ODIN and try again. (Make sure you're putting the modem.bin file in the correct spot in Odin.)
I think I have the latest odin.. And modem can only fit in the cp field I think. Its just not working for me. I tried doing each part separately. And the modem flash always fail.
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
I used odin 3.10 and also tried with odin 3.7
Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.
abatoir said:
Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.
Click to expand...
Click to collapse
You might want to boot into recovery mode and try to factory reset it normally. If his phone is rooted you could also flash a custom rom to it and get it out of Bootloop.
I also forgot to mention you can't get ahold of the system.img because it's not released to the public.
Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?
abatoir said:
Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?
Click to expand...
Click to collapse
If you flash the Kit Kat system.img you might have to downgrade the kernel also. I would give it a try and see if it works.
(I CAN GET INTO TWRP AND DOWNLOAD MODE) T-Mobile D801 (This was my previous phone that i had rooted before) My dads LG G2 was having issues with the touchscreen on CM so i decided to flash the stock ROM but i guess i might have skipped a few steps and after flashing i got :boot certification verify, secure booting error! and cause: boot certification verify. after that i tried flashing a backup but i got the same thing. My friend told me to wipe all the files so i did and that's what point i am on now. I can still boot into recovery but have no idea what to do further, i tried to following one of the guides on here (forgot link sorryz) but once i got to one of the steps where i plug my phone in my PC would recognize it as a bunch of drives (tried this on a different PC as well) WILL REALLY APPRECIATE THE HELP GUYS!
Gandek said:
(I CAN GET INTO TWRP AND DOWNLOAD MODE) T-Mobile D801 (This was my previous phone that i had rooted before) My dads LG G2 was having issues with the touchscreen on CM so i decided to flash the stock ROM but i guess i might have skipped a few steps and after flashing i got :boot certification verify, secure booting error! and cause: boot certification verify. after that i tried flashing a backup but i got the same thing. My friend told me to wipe all the files so i did and that's what point i am on now. I can still boot into recovery but have no idea what to do further, i tried to following one of the guides on here (forgot link sorryz) but once i got to one of the steps where i plug my phone in my PC would recognize it as a bunch of drives (tried this on a different PC as well) WILL REALLY APPRECIATE THE HELP GUYS!
Click to expand...
Click to collapse
if you can enter download mode then just flash stock friemware. using TOT or KDZ. thatll fix it. the boot error is when you mess with the bootloader. like you instal wrong bootloader for rom..
try it again.. i had same all i did was go back to stock.
i cant flash anything though since any PC will recognize my phone as a bunch of drives so i cant get the stock firmware
Gandek said:
(I CAN GET INTO TWRP AND DOWNLOAD MODE) T-Mobile D801 (This was my previous phone that i had rooted before) My dads LG G2 was having issues with the touchscreen on CM so i decided to flash the stock ROM but i guess i might have skipped a few steps and after flashing i got :boot certification verify, secure booting error! and cause: boot certification verify. after that i tried flashing a backup but i got the same thing. My friend told me to wipe all the files so i did and that's what point i am on now. I can still boot into recovery but have no idea what to do further, i tried to following one of the guides on here (forgot link sorryz) but once i got to one of the steps where i plug my phone in my PC would recognize it as a bunch of drives (tried this on a different PC as well) WILL REALLY APPRECIATE THE HELP GUYS!
Click to expand...
Click to collapse
you can flash again right rom for your model.(first confirm its not refurbished) or install bootloader changer through twrp(zip can be found on forum throug search). flash zip witb the help of OTG cable and usb drive. if you need help email me.. aslam. jarh @ gmail. com
Gandek said:
i cant flash anything though since any PC will recognize my phone as a bunch of drives so i cant get the stock firmware
Click to expand...
Click to collapse
Had the exact same issue, I believe it's caused by corrupting the internal memory (multiple causes for this).
Don't freak just follow http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 (there's a video guide at the bottom, but it's pretty straight forward).
After that follow http://forum.xda-developers.com/show....php?t=2432476 to get it back to stock and work from there.
I should have left well enough alone.
I was updating things so... I used twrp to install a new rom, magisk etc...
Then just though why not update twrp while I am at it.
I tried installing twrp-3.6.2_9-0-h910.img while inside my old version of twrp (not sure what version...)
Anyway - chose to install the .img file to recovery partition
Went to boot straight away back into my new recovery and got a kernel panic screen.
Booting to recovery gives me kernel panic every time
Regular boot gives me the LG symbol forever - more than 10 minutes
Now seems I am completely ____________'d
Seems I should know what to try next - but it's been a while since I have been doing this...
Thanks in advance.
wantpizza said:
I should have left well enough alone.
I was updating things so... I used twrp to install a new rom, magisk etc...
Then just though why not update twrp while I am at it.
I tried installing twrp-3.6.2_9-0-h910.img while inside my old version of twrp (not sure what version...)
Anyway - chose to install the .img file to recovery partition
Went to boot straight away back into my new recovery and got a kernel panic screen.
Booting to recovery gives me kernel panic every time
Regular boot gives me the LG symbol forever - more than 10 minutes
Now seems I am completely ____________'d
Seems I should know what to try next - but it's been a while since I have been doing this...
Thanks in advance.
Click to expand...
Click to collapse
I think you may need to root your phone again.
h910_root_pkg.zip "DirtySanta root package"
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
Thanks @Darnrain1 . It's been a while. Thanks for the reminder links.
I changed laptops since I did this... Plus I am 99% Linux now but a struggle I am used to.
I also found my initial LGUP before I rooted last time so the nerves have calmed and the tremors have stopped. HaHa. It was too late last night and I SOOOO should not have been flashing in TWRP.
wantpizza said:
Thanks @Darnrain1 . It's been a while. Thanks for the reminder links.
I changed laptops since I did this... Plus I am 99% Linux now but a struggle I am used to.
I also found my initial LGUP before I rooted last time so the nerves have calmed and the tremors have stopped. HaHa. It was too late last night and I SOOOO should not have been flashing in TWRP.
Click to expand...
Click to collapse
No problem.
Another thing you could try and do is flash twrp via fastboot and see what happens.
Update twrp. twrp-3.6.2_9-0-h910.img
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h910.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset.
Thanks a ton @Darnrain1 !!
Yep - that was all I had to do to get TWRP back was fastboot flash it in and now I restored an old backup and have my phone back.
I appreciate it. Happy New Year and all the best.