[Q] Bricked Iconia... - Acer Iconia A500

I guess I bricked my iconia...
I installed Recovery, etc. But when I rebooted my device it starts up, and shows my initial display screen. But it locks on the display (it is past the Android, and Acer screen).
So I tried to recover the device using the unbrick procedures described in this forum, and others. But it seems whenever it tries to process any update.zip file including the unbrick the little android man either stops turning or displays a sign indicating things did not work out as they should have.
I have clockwordmod backup from my system. How do I use that backup? When I use my phone the device automatically boots into xrecovery and allows me to restore. How do I get that with the Iconia?

first of all your device is not bricked as long as you can boot into any type of recovery.
second you obviously have cwm installed, but anyhow even if you don't have it i hope you have an external sd-card.
dl any of the stock rom's from the dev section, basically best is to choose the rom made for your country.
extract the update.zip and put it on your external sd-card.
then install it with cwm if you still have it, or with acer recovery (volume - and power simultaneously until the recovery text shows up).
and then take it from there.
also good idea is to clean dalvik cache and data cache before restarting if you use cwm.
then you can reinstall root and cwm.

zoubidou said:
first of all your device is not bricked as long as you can boot into any type of recovery.
second you obviously have cwm installed, but anyhow even if you don't have it i hope you have an external sd-card.
dl any of the stock rom's from the dev section, basically best is to choose the rom made for your country.
extract the update.zip and put it on your external sd-card.
then install it with cwm if you still have it, or with acer recovery (volume - and power simultaneously until the recovery text shows up).
and then take it from there.
also good idea is to clean dalvik cache and data cache before restarting if you use cwm.
then you can reinstall root and cwm.
Click to expand...
Click to collapse
Thanks... The problem is I can't boot into anything.
How do I boot into cwm? I can't boot into the operating system as once it hits the display screen with my picture the system freezes and tries to power down?
I have been playing around with acer recovery, but all of the updates I downloaded will not load onto the system. It tries to install, gets about 1/3 through and then gives me an error.
Hence why I was thinking that maybe my backup has something?

push volume - (left volume button) first and power and keep your fingers on it until it displays the recovery text message on top left of the screen

If you are getting into recovery. And flashing. A rom give you errors or does not complete. This issue is a bad d/load.or a bad currupt SD card.I would say format your SD card again.redownload the correct rom again.don't use a download manager.then decrypt. Unzip then put the update.zip on your SD card turn off your tab install SD card.
Reboot
Holding down volume up and power until you see the 4th line of txt. It should take you to cwr. Or flash your device
good luck

Yep.. use vol-down and power to boot into cwm. Keep holding vol-down until you see tiny white text in upper left corner.
Then do full restore. When it's done, if you don't see "Backup Succesfull!" message, you'll need to restore flexrom from the advanced restore menu. This is because it failed trying to restore .android_secure.img and caused cwm to restart before flextrom was restored.
Alternatively, you can delete the .android_secure.img file from your backup set before doing the full restore.
Good luck.
Sent from my A500 using Tapatalk

Thanks guys for all of your feedback.
However, when I hold down the buttons you mentioned I do get those text items you mention. The problem is that unlike my android phone it does not pop up the recovery menu. It goes straight into the Acer Recovery procedure (The android with turning gears).
Could it have been that upgrading to a specific ROM the recovery procedure is shortcircuited????
What I am trying to figure out is how to get the recovery menu.

Same deal!
I have the exact same issue. The Update.zip will not take and the Android Gears screen gets to 1/3 before the yellow triangle. Any further help would yield loud THANKS!

your update.zip should preferably be those 3.1 full. cos I believe it does not check anything for it to fail.

Thanks Kenny that does help and explain a few things.

Related

Root gone wrong

rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
If you have recovery, you should be fine. Just flash your favorite image and wipe your userdata.
DOD1 said:
rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
Click to expand...
Click to collapse
Holding Home + Power is supposed to take you into the recovery image.
At the bottom of your recovery image does it say Amon Ra 1.5.2 or 1.6.2 or something like that?
If your phones rooted then just wipe and reinstall you rom.
Like lets say your doing the new cyanmod
you apply zip
DR83
With out rebooting apply zip
Cyanmod-rom 1.4xxxx
If it boots back into Android System recovery Utility just hold home and back again.
Give it time to write its radio and its first time rebooting it says on the boot screen for a awhile some longer then others.
This site has always helped me its better to see the instructions rather then read them.
http://www.google.com/search?q=the+...s=org.mozilla:en-US:official&client=firefox-a

[Q] VISIONARY & Clockworkmod Couple Questions

I'm pretty sure I have these items in the correct order to "Permaroot" my MT4G and begin using Clockworkmod to load ROMs (and or/also want to be able to back up my default ROM)
My current attempts:
Downloaded and installed: VISIONary, from android.modaco.com, sorry I can't post actual links (VISIONary+, most recent version) was no longer avalible in the market so I had to install it from the URL)
Downloaded and installed "Clockwordmod" from the Market.
Put the phone into USB-Debugging mod, and disabled fast boot.
VISIONary+ question: I setup TEMPROOT, and "Root on Boot", assuming I would than be able to boot into "Recovery mode" via "Clockworkmod"
The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Going back to VISIONary+, I attempt to "Permaroot", the phone's homescreen goes blank and nothing happens. The phone eventually turns itself off but doesn't reboot, subsequently, I must restart it manually, again, I'm not sure if I've achieved anything?
Advice, suggestions? Would be very appreciated.
Questions that might explain what's wrong?
Even in USB-Debugging mode, should I be connected to a PC via USB-Cable during all of this?
Any thoughts on why the PERMAROOT fails, or the "Root on boot" fails to get me to "Recovery mode"?
Last thing, I get a complaint from "Clockworkmod" when loading, that my SD Card must be mounted (which I'm assuming it isn't due to USB-Debugging mode and/or being connected to the PC) So should I get a good charge and disconnect from the PC while attempting all this? Fixed, disconnected USB-Cable, and mounted SD card in settings, this stopped this error
Also, I'm interested in backing up my default ROM ASAP as a safety-net in-case I screw something up. Is this possible via recovery mode in "Clockworkmod"? Links to advice on doing this?
Thanks everyone! Great board!
you should follow this as it worked for me flawlessly
http://forum.xda-developers.com/showthread.php?p=9534017#post9534017
thanks! that post seems to answer a lot of the specifics I might have been missing! Guess I missed it in search! I'll report my results!
I followed it exactly but I still get the Red Exclamation Point. I have rooted my phone s-off and I have superuser and rom manager. I did the Flash Clockwork Recovery but when I reboot into recovery I get Red Exclamation Point then when I click vol up and power the next says " E:Can't open /cashe/recovery/command " What should I do??
[*]The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Click to expand...
Click to collapse
You can NOT flash clockwork without S-OFF and the red triangle is recovery. It is stock recovery if you press volup+power you will see the menu
S is off I rooted my phone using the terminal Emulator and that worked fine
When I press upvol and power I see
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cashe partition
E:Can't open /cashe/recovery/command
This is what my screen shows when I try to go into recovery and again my phone is rooted s-off and I use superuser
Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot
I found out the problem it was so easy but I never would of thought of checking but my wife said maybe my Rom Manager is a bad copy (because I get all my apps from a not so honest site) so I deleted my RM and downloaded the freebie on the market and it worked on the first try.....Now I have Glacier Rom running and I feel like a new man
slhpss said:
Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot
Click to expand...
Click to collapse
+1 on that, When I first flashed it, I was still getting the red triangle, after a quick google search I re flashed it an extra 2 times and it worked flawlessly

[Q] Problem installing gapps using cyanogenmod 7 on nook color sd card boot

If anyone can help I would appreciate it.
I followed this post about installing cyanogenmod 7 onto an SD card to boot my nook color off of the SD card.
http://forum.xda-developers.com/showthread.php?t=1000957
Everything worked great and it has been up and running for several days, very happy with the results.
Now I was trying to put gapps on the SD card and I followed the instructions shown below:
How to install market and gapps:
After you have booted into the CM7 on SD card for the first time and set up wifi access (important!)
Go to http://wiki.cyanogenmod.com/index.ph...Latest_Version and at the end there is a table with various google apps versions. Get the one suitable for your cyanogen version (CM7 is the latest for now). The file is named gapps-....zip
shutdown your nook and take the SD card out, insert it into your computer.
Copy the gapps-... file to the SD card on the first partition (titled boot) without changing the file name.
Insert the uSD card back into the NOOK and boot into "Recovery mode." To boot into recovery mode: Boot normally into Android, then from desktop hold power key until a poweroff menu appears, In the poweroff menu choose "reboot", in the next menu choose "recovery" and press "OK". The nook would reboot straight into recovery.​
So i have tried this several times and DL the file twice just to be sure but every time I reboot the system just comes up normally. I wonder if the gapps install package is named wrong? I don't know how to make this work.
Any suggestions?
Thank A LOT for your help!
Steveolio said:
So i have tried this several times and DL the file twice just to be sure but every time I reboot the system just comes up normally. I wonder if the gapps install package is named wrong? I don't know how to make this work.
Any suggestions?
Thank A LOT for your help!
Click to expand...
Click to collapse
That's the problem.
You want it boot into Recovery, not Normally.
Steveolio said:
If anyone can help I would appreciate it.
I followed this post about installing cyanogenmod 7 onto an SD card to boot my nook color off of the SD card.
http://forum.xda-developers.com/showthread.php?t=1000957
Everything worked great and it has been up and running for several days, very happy with the results.
Now I was trying to put gapps on the SD card and I followed the instructions shown below:
How to install market and gapps:
After you have booted into the CM7 on SD card for the first time and set up wifi access (important!)
Go to http://wiki.cyanogenmod.com/index.ph...Latest_Version and at the end there is a table with various google apps versions. Get the one suitable for your cyanogen version (CM7 is the latest for now). The file is named gapps-....zip
shutdown your nook and take the SD card out, insert it into your computer.
Copy the gapps-... file to the SD card on the first partition (titled boot) without changing the file name.
Insert the uSD card back into the NOOK and boot into "Recovery mode." To boot into recovery mode: Boot normally into Android, then from desktop hold power key until a poweroff menu appears, In the poweroff menu choose "reboot", in the next menu choose "recovery" and press "OK". The nook would reboot straight into recovery.​
So i have tried this several times and DL the file twice just to be sure but every time I reboot the system just comes up normally. I wonder if the gapps install package is named wrong? I don't know how to make this work.
Any suggestions?
Thank A LOT for your help!
Click to expand...
Click to collapse
turn on the NC, like normal, then power down, then you'll get option to reboot, reboot to recovery.
I'm sorry if my original post didn't make this clear, but I was trying to boot into recovery. I held down the power button until I got the shut down options and pressed restart then pressed recover mode. Every time I try this the nook just restarts in normal mode. I'm not sure if I've done something wrong or if this method doesn't work.
Just to give more information the file I used was:
gapps-gb-20110613-signed.zip
I didn't unzip the file I just copied it to the SD card BOOT partition.
Seems like you've done what eggnoodle suggested and if it didn't work, the only choice is using combination of N & power button. It needs some skills.
Try that, won't hurt.
I tried that several times, and it didn't work.
Is there a way to verify if I am in recovery mode? I'm not sure I am actually making it into recovery mode.
Further down in the instructions it says that to install other stuff anything with the name "update-***.zip" will install on recovery mode. So I will try renaming the gapps file to this and give it a try.
If you see the "Penguin" with scrolling text running horizontally on the NC screen, then it is in the Recovery mode.
If you see the Android guy or CM7 logo, you are in the normal booting mode.
Ok, so my problem is that I can never get the nook color in recovery mode. Perhaps the instructions on the forum are kinda flawed.
This is what I am doing:
Hold down Nook button.
Hold down power button
Loading screen appears then goes blank
Release power button for less than a second
Hold down power button again.
Wait for loading screen to appear
Release power button
Wait for screen to go blank
Release the Nook button
Then the NC just boots up like normal. Is this the correct process?
The NC boots up normal if I choose restart in recover mode from the shutdown menu also.
Any suggestions?
As I said, you need some skills.
Don't panic!
After a few tries and when you get it in, you will mumble "hmm, it's nothing like the instructions, it's much simply than that, wheewwww"
Steveolio said:
Ok, so my problem is that I can never get the nook color in recovery mode. Perhaps the instructions on the forum are kinda flawed.
This is what I am doing:
Hold down Nook button.
Hold down power button
Loading screen appears then goes blank
Release power button for less than a second
Hold down power button again.
Wait for loading screen to appear
Release power button
Wait for screen to go blank
Release the Nook button
Then the NC just boots up like normal. Is this the correct process?
The NC boots up normal if I choose restart in recover mode from the shutdown menu also.
Any suggestions?
Click to expand...
Click to collapse
Did you try going into recovery while in CM7 by powering it off and selecting reboot>reboot to recovery?
I did try that, just boots up in normal mode.
I cannot get this thing to work, I have also tried several different ways to boot up using the home button and power button I can find a combination that works.
so frustrating!
Maybe start over fresh with Cm7 and gapps install?
I intall CM7 and gapps at the same time...
Just to be clear I didn't try this because the instructions said do not do it.
Ok, so I reinstalled with gapps and cyanogenmod zip files both on the boot SD before it was installed and it took, but there were a few hang ups like it kept bringing in stuff from my phone when I linked to my google account. So I think I should be good.
Thanks for the suggestions.
That happen to me too. It installed a wallpaper that was on my phone that I no longer use. Strange? But as long as it worked, that what I cared about!
Yup same thing to me, it installed the wallpaper and some other apps.
Why won't it install angry birds, the market says it's not compatible? What the heck's up with that?
If you are having issues booting into recovery when booting onto the SD card. This post should help
http://forum.xda-developers.com/showthread.php?t=962708
The new market has issues with nook color. Market is looking for a 160 density level when the nook color is set to 161 to avoid panics.
Ive been using LCDDensity from the market and choosing Density 160 and changing the drop down to killall and click apply (reboot)
after it reboots go into manage applications and do a force stop on the market and clear the data/cache
it will reload and you will see all the options until the market resets itself. very annoying i know but its a temp fix until someone figures out how to fix this
Forget that stupid method with the buttons, it's a waste of time.
I tried it both ways and it doesn't work.
Use this instead, works like a charm.
http://forum.xda-developers.com/showthread.php?t=947698&highlight=boot
Sineira said:
Forget that stupid method with the buttons, it's a waste of time.
I tried it both ways and it doesn't work.
Use this instead, works like a charm.
http://forum.xda-developers.com/showthread.php?t=947698&highlight=boot
Click to expand...
Click to collapse
You mean you couldn't get it to work... works just fine.
Same problem as Steveolio - error message during recovery
Steveolio said:
Just to be clear I didn't try this because the instructions said do not do it.
Ok, so I reinstalled with gapps and cyanogenmod zip files both on the boot SD before it was installed and it took, but there were a few hang ups like it kept bringing in stuff from my phone when I linked to my google account. So I think I should be good.
Thanks for the suggestions.
Click to expand...
Click to collapse
I have the same problem as Steveolio and followed exactly the same procedures. Maybe these error messages from recovery boot help some experts with a good idea:
Penguin
""rcS!
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir(2.6.32.9): No such file or directory
Starting network...
Detected standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skiping format
Mounting /dev/mmcblklp1 as /boot
Looking for the install images....
Lets see if you have gapps installer too.
Gapps installer not found, skipping installation.
Flashing caches
Clearing recovery flag
1+0 records in
1+0 records out
All steps complete, flashing again
Preparing to shutdown
""
Does that possibly mean gapps file is not in the right location?
thank you
fatalfuryy said:
If you are having issues booting into recovery when booting onto the SD card. This post should help
http://forum.xda-developers.com/showthread.php?t=962708
Click to expand...
Click to collapse
There is no "Thanks" option so I just wanted to say Thank you! The button combo for booting into recovery has been kicking my butt and this was simple and worked flawlessly!

[Q] Custom ROM, stuck at boot animation...

I wanted to run a custom ROM on my A500 (first attempt at installing custom ROM), but i'm now stuck at the boot animation.
I downgraded my A500 to 3.0.1, rooted, installed clockwork mod, upgraded cwm to 1.5. So far so good.
Then i downloaded thor rom v12, copied it to the external sd card (by putting it on USB thumb drive, transfer to tablet, copy to external SD using file explorer - something tells me I'm going to need to pick up an sd card reader for my computer)
Rebooted into recovery, wiped everything (had nothing of value installed yet), and then chose to install zip file, chose thor_rom_v12.zip on external SD card, it started installing - looked like it succeeded.
Reboot tablet, and i've been staring at the boot animation (electric blue pulsating android with spinning gears on it) for about 45 minutes.
How should I proceed from here? Any idea what I did wrong?
Thanks
Hold the power button down and see if you can force it to shut down. I dont think itll turn off but its worth a try. You could also try the hard reset button (pin hole on the side of the tab) if the reset works than you should be able to boot back into recovery. If not than youll just have to wait till the battery dies.
Once you eventually get it turned off than try booting into recovery and do a full wipe and reflash the rom. I have a feeling the file you downloaded is corrupted though. if this is so than your tab probally wont boot up again.
At this point id redownload the thor or another rom and than try flashing that. You'd have to get an sd reader since you won't be able to transfer the files through your iconia again. If you can manage to get a clean download on your micro sd somehow than i'd skip straight to this step and start redownloading the rom right now.
BTW these are just the things i would try from knowing what I do about android. I haven't had any issues with my tab yet so I havent looked for solutions for this it, but ive dealt with other boot looped and soft bricked devices.
I'm sure if you do a search you'll find something.

Accidentally installed OTA update, now seeing many problems and can't find a fix

Yesterday I accidentally installed the OTA update. I got stuck in TWRP and flashed a new ROM. Phone booted up fine, but now I have no cellular signal, nothing that uses video or sound works. Camera doesn't work, flashlight doesn't work.
I tried several different ROMS and nothing changes. Even the system sounds, ringtones and so on do not work. Anyone have any idea what I can do? Thanks
boot into fastboot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase misc
fastboot erase fota
fastboot erase boot
then pull battery and reboot into twrp by holding power and vol down, when lg logo appears then click the power button and re-hold it down to get into twrp.
once in twrp, check and see if system is mounted, if it wont let you mount, go to wipe and wipe everything (not ur sd of course)
System, cache, dalvik, data, internal, everything... the fastboot should have already done this but let twrp do it too..
once done, use the format option and format data also, some of these may error thats okay, just keep going..
once done reflash the full rom that matches your device.. let it flash and reboot and do its thing. this should fix the issues...
once it boots you may need to let it activate, or re-activate.
Only other suggestion would be if you have a twrp backup and you backed up your efs, its time to restore it also and see if the NV files have been damaged.
I've tried installing several different roms available on xda but that didn't resolve the issue. My phone remains in a boot loop state. Is there a way I can return to stock without compromising my ability to use the current root exploits?
Might help to know what you've got currently, are you able to get to recovery at all, etc?
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
My Solution
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
lanyueng said:
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
Click to expand...
Click to collapse
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
jluca98 said:
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
Click to expand...
Click to collapse
This isn't working for me. Keeps rebooting to TWRP.
I get FAILED (remote: unknown command) with every adb command
Any ideas?
Drkphnxs2k said:
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
Click to expand...
Click to collapse
Don't use Easy Recowvery. Do it manually from the original thread. You can also google it for some sites that have cleaned the instructions up for easier reading.
I just did a H918 10d like this.

Categories

Resources