Related
right
i am going to have send my a100 back. the touchscreen issue is driving me nuts and i cant keep it in its crrent state. i am shipping it back to the retailer for a full refund rather than pay to ship it back to acer. at the end of the day i cant be doing with the hassle. so i need to know how i go about unrooting it and locking the boot loader back up and basically restoring it to stock.
i will have a read of the forums but with work being all rather busy and a deadline for return i am a little pushed for time so if anyone out there knows and would be kind enough to link me to a thread or simply tell me that would be appreciated.
cheers
You could flash stock boot loader and flash an official ota
sent from your future.
das_webos_transformer said:
You could flash stock boot loader and flash an official ota
sent from your future.
Click to expand...
Click to collapse
If hes just rooted just run the ota it'll do boot loader too. He didn't mention a custom rom or recovery, but if he does then doing it in that order will lock it up. Stock recovery then stock rom then bootloader last. Basically stock recovery > ota then you're fine.
Tapatalked from my Galaxy S II.
hey guys thanks for the replies.
ok sorry i should have said i have unlocked the boot loader rooted it and instaled twrp recovery. i never got round to putting a rom on it (i have only had it about 6 or 7 days), i removed root by accident when i wiped it but obviously the unlocked bootloader and recovery remained. so with this in mind then exactly what would i do?
flash stock rom>flash stock bootloader?
would that also remove recovery?
edit sorry i didnt remove root when i wiped it i merely lost the superuser app so i am actually still rooted.
rockmonkey1973 said:
hey guys thanks for the replies.
ok sorry i should have said i have unlocked the boot loader rooted it and instaled twrp recovery. i never got round to putting a rom on it (i have only had it about 6 or 7 days), i removed root by accident when i wiped it but obviously the unlocked bootloader and recovery remained. so with this in mind then exactly what would i do?
flash stock rom>flash stock bootloader?
would that also remove recovery?
edit sorry i didnt remove root when i wiped it i merely lost the superuser app so i am actually still rooted.
Click to expand...
Click to collapse
Root occurs in system, which isn't affected by wipes, so yeah SU is still there, just the app to control it is gone, which you discovered already.
As you have twrp, unlocked a200 bootloader but stock rom, the process is pretty simple.
Get the ics ota, name it update.zip place it on the root of the external sd card, no folders.
Power on holding volume - (closes to lock switch) and press power for 3 seconds, once the text starts up in the upper left corner, let everything go.
Should install stock rom, which will do the following:
1 wipe cache
2 flash new rom system
3 "flash" a100 bootloader
4 reboot into android
5 flash over twrp and place stock recovery in place
This will all occur on it's own once you get it loading up update.zip
5 only happens if it boots and is completely stock with /system/etc/install-recovery.sh intact.
3 can happen as long as it uses the update.zip
2 can fail, if it does but proceeds to flash bootloader twrp will be locked out, however a stock rooted rom as you have will still boot, and we can cover replacing the recovery with stock at that point if needed.
1 always happens, regardless of any other steps being met or finished.
mate thanks for helping here. i had to fix my phone which died after a bad flash of a back up in cwm... long story wont go into it... but it did eat up a good one or two days. so i havent gotten round to sorting anything out here with the tablet.
now i am going to try to flash the build prop and install one or two roms. flex reapers and cm10 all look good and i am hoping that that combination with maybe with over clocked kernal will be enough to fix the screen problem.
now i know it is unlikely if it is a hardware fault but i need to try because i would like to keep this tablet and the place i got it from havent got any more. it was pretty inexpensive at 127 pounds and i will be unlikely to find any other store that has stock at that price so if it goes back it goes back for good. hence me wanting to try to keep it.
so i am gonna flash the roms and the build prop now. if it doesnt fix it then i will be back for a little help in reverting it back to stock. by the way where can i find the ota ics release?
i will have a look on the forum i am sure it has to be here somewhere but just in case!!!
edit: got them edit no i havent i cant download them? the site is offline... anywhere else they can be gotten from? maybe acers website? will check now. just realised i have the stock rom installed! will make a back up now.
http://forum.xda-developers.com/showthread.php?t=1307046
so you reckon it could be as simple as simply flashing the official rom to take the tablet all the way back to stock including the locking of the bootloader and removing the recovery? that would be nice and simple and easy which will be a real welcome change from the norm. fingers crossed that is all that is needed.
To go stock that is all that's needed. In vaches thread there is one decrypted on a drop box, that's our only one unless vache brings his stuff back online.
Well there is the service ROM which will be stock, but not what is supposed to be there. At first glance its stock though. Wouldn't suggest it for a return.
Tapatalked from my Galaxy S II.
ok this post was confusing. i am running stock ics at the moment. the bootlaoder is unlocked i have root and the recovery is twrp.
so i have downloaded the update found in the drop box folder here.
http://forum.xda-developers.com/showthread.php?t=1307046
it was already called update and it has a zip extension. so it is update.zip.
i have put it in both mnt/external_sd/ and also /sdcard/ none of them work.
all i get when i hold the volume and power button is taken into twrp recovery.
i thought it flashed automatically? can i flash it through recovery? bit worried about doing that because if it removes recovery while it is flashing i will be screwed.
will wait here now until someone can confirm what i am doing wrong because i cant afford to brick it.
i can be a bit to smart for my own good at times.
could the problem be that i am already running the latest ics official release? should i flash a custom rom? just throwing out some ideas here because i aint got a clue why it hasnt worked.
anyone know? i need to ship this back to the retaler tomorrow and i would prefer not to do it with an unlocked bootloader and custom recovery.
things is i am stumped because i thought i had done all that should be needed to flash the update and the only thing i can think of is because the firmware is up to date (possibly even newer than the update.zip) it wont update.
rockmonkey1973 said:
anyone know? i need to ship this back to the retaler tomorrow and i would prefer not to do it with an unlocked bootloader and custom recovery.
things is i am stumped because i thought i had done all that should be needed to flash the update and the only thing i can think of is because the firmware is up to date (possibly even newer than the update.zip) it wont update.
Click to expand...
Click to collapse
In that case flash the stock recovery and run the bootloader for a100 that came in the unlock boot loader zip. Run the a100 script instead of the a200 script, that will lock it. Do this after stock recovery flashing.
Or, put back install-recovery.sh and reboot, that will replace the stock recovery then run the a100 boot loader script. You'll still be rooted but try update.zip again after stock recovery and boot loader are done.
Tapatalked from my Galaxy S II.
pio_masaki said:
In that case flash the stock recovery and run the bootloader for a100 that came in the unlock boot loader zip. Run the a100 script instead of the a200 script, that will lock it. Do this after stock recovery flashing.
Or, put back install-recovery.sh and reboot, that will replace the stock recovery then run the a100 boot loader script. You'll still be rooted but try update.zip again after stock recovery and boot loader are done.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
mate you have been incredibly helpful. i mean seriously.
i will do as you suggest however i have a question how am i supposed to flash these files? do i do it through recovery? please dont say adb because i have never used that program dont know why i just tended to stay away from it zips and nandroids always seemed so much easier.
i have edited this post due to being slightly confused and thought it best to save the gushing praise until after the tab is stock! sorry mate i hate being a pain and i am reading all i can on locking the bootloader but there doesnt seem to be any guide i can follow. most of the threads i have found are for bricks and my tab is certainly not beicked... and i want it to stay that way.
rockmonkey1973 said:
mate you have been incredibly helpful. i mean seriously.
i will do as you suggest however i have a question how am i supposed to flash these files? do i do it through recovery? please dont say adb because i have never used that program dont know why i just tended to stay away from it zips and nandroids always seemed so much easier.
i have edited this post due to being slightly confused and thought it best to save the gushing praise until after the tab is stock! sorry mate i hate being a pain and i am reading all i can on locking the bootloader but there doesnt seem to be any guide i can follow. most of the threads i have found are for bricks and my tab is certainly not beicked... and i want it to stay that way.
Click to expand...
Click to collapse
Well....adb. You used it before with the scripts to unlock the boot loader.
http://forum.xda-developers.com/showthread.php?p=23868002
Right above the download it mentions running the a100 script to revert to locked a100 boot loader.
Only do this with a stock ROM installed!
After that it'll be manually installing the recovery with fast boot or replace the stock /system/etc/install-recovry.sh
If it was just renamed, then name it back. If it was deleted it'll need replaced, it will revert to stock recovery on its own after booting with it in place.
Tapatalked from my Kindle Fire - Jellytime AOSP
thanks again my friend. funny i never realised i was flashing stuff with adb when i was doing things like that!
i always thought adb was a command line interface like say ssh and that you needed to use some sort of software like putty.
anyways just to bring this to a close. i never got time to flash it back to stock. i simply left the official ota on and reset it. have already received the refund so all is good. shame i am unlucky with tablets. i had a faulty archos 80 g9 and then this. guess i will hold off for a while maybe until i feel my luck has changed for the better.
cheers again mate.
I'm posting this just because it might be helpful for others, as well as providing some warning for anyone else who might one day get into the same situation.
I was rooted and had installed TWRP on my new Gpad 7.0 V410 and everything was running just fine. I've been modding Android devices for years and thought I knew what I was doing. I didn't like the AT&T boot animation and thought I'd replace it. I found the stock animation in system/media, and replaced it (with a Nexus 7 ani) just like I'd done on previous devices.
When I rebooted, the animation started and ran. But then it hung, and rebooted. It was now stuck in a bootloop. Well, no problem, I thought, I'll just get back into recovery and restore the stock ani.
That was when I discovered how locked down the firmware is on this device. No fastboot. No standard Android bootloader. Not even, as far as I could tell, anyway of rebooting into recovery using the hardware buttons.
I could get to the factory reset screen and download mode, but neither have any way to get to recovery. ADB could not connect. The LG support tool found it, but did nothing but tell me the firmware was up to date. Lots of searching and reading turned up similar tales of woe. I began to worry that there was no way out.
Having no other ideas, I tried doing a factory reset. It ran, and lo and behold, kicked me into TWRP. From here, I confirmed that the device was wiped.
However! I had had the foresight to create a TWRP backup on my external sdcard, and that was still there. Restoring it got everything back in working order.
The moral: If you're up and running now, make an external backup. It could save your butt just as it did mine.
Amen
I'd just like to add that you can enable fastboot on this tablet for anyone who might read this thread. If you follow the method described here you'll lose download mode, but the tablet will fall back to fastboot when download mode fails. :good:
Without a kdz file released for the V410 the download mode isn't really good for anything, but fastboot gives you a fighting chance of being able to flash your way out of trouble if you brick your V410. Probably advisable to keep a backup of the laf partition just in case you need it someday.
Aha, thanks, I had seen that referenced several times, but wasn't sure where to go with it, and wanted to try less extreme methods before attempting something like that.
I've been spoiled by modding HTC and Nexus devices up to now, so this is a bit of a culture shock over here.
Edit: Decided to bite the bullet in case of future problems and nuked laf. Ah, sweet fastboot. :highfive:
My G3 randomly decided to get the green screen of death after I plugged it into my pc to charge it. Now it cycles to the TZ Crash! Green screen no matter what I do.
The only way for me to get the phone to boot up for approximately 10 seconds is to put it in the freezer for about hour or so and for some reason it will boot up and crash after that time.
I could care less about the phone but would really like to recover my information and pictures from the device but as soon as I try and transfer them it crashes and Green Screens again.
Is there ANY way to temporarily get it to work or a way to pull my info off from it?
I am rooted on Cloudy G3 Kitkat at the moment. Maybe I can get into a recovery?
Any help is appreciated, thanks!
I would suggest you to switch to latest Marshmallow firmware.
I've read about many KitKat users that got the green death screen, so upgrade may be resolutive.
Look for latest firmware: go to http://devtester.ro/projects/lg-firmwares/download.php#imei, you simply have to type your IMEI code and proceed to download the proper Kdz file.
Then flash it with LGUP (http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3) and remember to do a full wipe (procedure should be explained in the thread).
Now install and run KingRoot (http://forum.xda-developers.com/devdb/project/?id=9793#downloads), then run Autorec (https://www.androidfilehost.com/?fid=24352994023705527) and finally uninstall the same KingRoot app (it's no longer needed).
Since CloudyG3 is no longer supported, you have to reboot in recovery and flash latest Fulmics Rom (v5.3, http://www.fulmics.com/rom-g3/).
After doing that, tell me if you solve
If you have a custom recovery installed, data backup will be easy. For instance, while in TWRP, simply plug in your phone to your computer and you have access to the files on the internal and SD Card storages. If you want more than that, simply mount the desired partitions.
If you do not have a custom recovery installed, you could use ADB but that could be difficult/tedious if you are not familiar with linux commands... or ADB for that matter.
As for the crashing, just flash a different ROM. Make sure you do a semi-clean flash and wipe only the System partition before doing so. That may also solve any data backing up probs you may have. If flashing a diff ROM doesn't work, you may have to resort to using the LG flash tool to go back to stock. But, of course, that would wipe everything on the phone.
Good luck!
Thanks for the replies guys. I flashed it to stock kdz and it appears to still be broken. My thoughts are that the logic board is toast. Only short term resolution was placing it in the freezer for a few hours. This gave me about 5 minutes of use before it crashed again. Just enough time to transfer my pictures off from the internal sd card. Hopefully this helps others with the green screen crash issues in recovering some of their data.
So while i was browsing around with Firefox on my 1 year old Nexus 5X, it suddenly froze and after about 20 secs automatically reboots.
After it shows the google boot logo for about 10 seconds it reboots again in a loop.
Bootloader is unlocked, its rooted and Cyanogenmod is installed. This worked fine for about 1 year. I havent done any updates since this CM install 1 year ago.
I can get into fastboot by pressing power and volume down. I can stay there forever but if I choose anything else from there, it goes into the reboot cycle again.
So I can not get into recovery mode from fastboot because it reboots before it gets there.
I can sometimes get into download mode by pressing power and volume up but after a few seconds it again reboots from there.
Is there any way to at least save my data? I do have some very important account data on it.
I assume from fastboot mode alone you cant save anything or is there a trick?
Thanks for any help!
sounds very similar to my situation, bought mine about a year ago as well, except I was running stock 7.1.2
It should be easy to save the phone, but for the data - that's going to be trickier.
As long as you have fastboot you can always just flash it back to stock but that will wipe your data.
So you could try to to:
fastboot erase cache and fastboot erase recovery and then reflash recovery and see if you can get into it now.
Once in recovery you should have adb access if you have the correct drivers installed and you can flash a full OTA image in ADB which will reflash every partition, but not wipe your data.
For both methods read this: https://developers.google.com/android/images
Once you have adb you could also just pull the entire content of your data partition. The question is if and how that account data is stored and if you could get it back that way.
If you really need that app data I would try to get the OS working by flashing the OTA image in adb, then reinstall the app and hope your account data is still there...
And then look into backup options. It's pretty risky to have important data not backed up or duplicated somewhere else on a mobile device that could be lost or stolen any second...
It sounds like the bootloop problem, its a problem that many people are facing
berndblb said:
It should be easy to save the phone, but for the data - that's going to be trickier.
As long as you have fastboot you can always just flash it back to stock but that will wipe your data.
So you could try to to:
fastboot erase cache and fastboot erase recovery and then reflash recovery and see if you can get into it now.
Once in recovery you should have adb access if you have the correct drivers installed and you can flash a full OTA image in ADB which will reflash every partition, but not wipe your data.
For both methods read this: https://developers.google.com/android/images
Once you have adb you could also just pull the entire content of your data partition. The question is if and how that account data is stored and if you could get it back that way.
If you really need that app data I would try to get the OS working by flashing the OTA image in adb, then reinstall the app and hope your account data is still there...
And then look into backup options. It's pretty risky to have important data not backed up or duplicated somewhere else on a mobile device that could be lost or stolen any second...
Click to expand...
Click to collapse
I dont know about the OP, but my 5X will not get into fastboot, no matter what option I pick, I see the Google screen then it goes black and back to the Google screen and then is unresponsive for hours
I'm having the same issue as of this morning. I find it a little suspicious that it happened on the same day that my billing restarted and they had just updated the app a few days ago...
But I am unable to get to recovery mode either. Just shows the Google logo and reboots.
It's happening to me right now, the exact same thing, guys, this is not a coincidence
Another one here, started Friday night 3 days ago. Really weird that all of a sudden so many 5X users are experiencing the same problem.
mine just started this today, but after about ten reboots it finally started. Its almost like someone took control of the phone to install something remotely... weird
Sent from my Nexus 5X using Tapatalk
I'm having the exact same issue. Was watching a youtube video and suddenly the screen froze and my phone rebooted. When i tried to get into the recovery i still only got the google logo and a reboot. Fortunately i have my bootloader unlocked. I was able to reflash android and it worked again. After an hour or two the same started to happen again. Extremely frustrating.
Best thing you can do is flash just the recovery and try to get your files out that way.
so even until now many Nexus 5x still got bootloop? nothing to fix it still?
planning to get an used Nexus 5x and afraid also got this bootloop problem, should I or shoudn't I get it?
after reading so much bootloop stories, seems the timing to bootloop is just matter of time? on how much the phone is used? heavy use got bootloop first and lighter use got bootloop last but still get it sooner or later?
I will not buy it
DON2003 said:
so even until now many Nexus 5x still got bootloop? nothing to fix it still?
planning to get an used Nexus 5x and afraid also got this bootloop problem, should I or shoudn't I get it?
after reading so much bootloop stories, seems the timing to bootloop is just matter of time? on how much the phone is used? heavy use got bootloop first and lighter use got bootloop last but still get it sooner or later?
Click to expand...
Click to collapse
Two days ago I was facing the same problem, I managed to reload the stock rom and relock the bootloader so I can claim the warranty. But even though they replace me the phone I am pretty sure that sooner or later you will face this problem. This is an amazing phone and for the time I buy it, I believe was a smart choice, now I believe you can find something at same range price with even better specs.
I am facing the exact same issue. I was watching a Youtube video when the phone suddenly froze and shutdown itself. Then impossible to boot again. Sometimes I can boot to fastboot (after few hours without touching the phone or 20 min in the freezer). I tried to flash factory images (https://developers.google.com/android/images) but it does not fix it.
Has anyone been able to fix this? I don't think it's a hardware issue as I replaced the screen (the last one had a small crack on it) as well as the battery...
Look in the general subfourm for BLOD. https://forum.xda-developers.com/showthread.php?t=3683926
Sent from my [device_name] using XDA-Developers Legacy app
Where to begin...
Okay, so I ended up flashing an incorrect .zip which caused my Nexus 5X to go into a boot loop. Usually, the fix is to go into TWRP and fix what I broke. Unfortunately, TWRP or Custom Recovery does not exist. The endless boot isn't booting far enough for ADB or Fastboot commands. Additionally, my volume down button my device is also broken so therefore I can not manually go into Custom Recovery. Also, I know I have the right drivers needed in my windows 10 machine to read the device. The device is not able to be seen by the computer currently either.
My question is, I am currently at the Firmware Update screen. This is the only screen I can currently go into manually. What is it that I can do from the Firmware Update screen ( Download Mode ) to restore my device?
There is a temporary fix or two so you can get back your data, but not permanent fix. The chipset will keep falling and the phone gonna die.
KarimKh said:
There is a temporary fix or two so you can get back your data, but not permanent fix. The chipset will keep falling and the phone gonna die.
Click to expand...
Click to collapse
That explains a lot...Lol!
Luckily, there is hope for you!
should work
Can't test it since my device is in a deeper bootloop that requires Qualcomm files that nobody wants to build.