Database Info

[Q] Acer Iconia Tab A700 Bootloop HELP!!

Ok so today CyanogenMod released the m10 snapshot version for the A700 and before installing it, i decided to factory reset my tablet from CWM and then install the new version.
My tablet did run the cyanogenmod intro start up like all new devices but I found out that my music, videos, pictures, etc were still there even though I formatted from recovery. SO, I decided to factory reset from the settings, tablet reboots, won't start up! I've come to the conclusion that I might have reset my tablet to stock firmware even though there isn't any installed. I can open recovery but can't do anything other than scroll through the menus. Whenever I confirm an action the tablet bootloops. I think I can solve this by re-flashing the new rom but whenever I go to install zip the tablet reboots into a bootloop. Is there anyway to install the rom without recovery? Like using command prompt? And if that's not the case then could you help me solve this issue?
Many thanks to anyone who can help me out
SOLVED: After spending 7 non-stop hours on command prompt typing in fastboot and adb commands, managed to somehow luckily figure it out. I can't really explain how I did it but I did it

AusomBabs said:
Ok so today CyanogenMod released the m10 snapshot version for the A700 and before installing it, i decided to factory reset my tablet from CWM and then install the new version.
My tablet did run the cyanogenmod intro start up like all new devices but I found out that my music, videos, pictures, etc were still there even though I formatted from recovery. SO, I decided to factory reset from the settings, tablet reboots, won't start up! I've come to the conclusion that I might have reset my tablet to stock firmware even though there isn't any installed. I can open recovery but can't do anything other than scroll through the menus. Whenever I confirm an action the tablet bootloops. I think I can solve this by re-flashing the new rom but whenever I go to install zip the tablet reboots into a bootloop. Is there anyway to install the rom without recovery? Like using command prompt? And if that's not the case then could you help me solve this issue?
Many thanks to anyone who can help me out
SOLVED: After spending 7 non-stop hours on command prompt typing in fastboot and adb commands, managed to somehow luckily figure it out. I can't really explain how I did it but I did it
Click to expand...
Click to collapse
Good Job if You Could Explain For Latest Problem Solved. I Think this is the problem from cwm or maybe the latest rom of cwm snapshot, need to investigate for problem occured. before this update we never have this problem. "When Reset Factory Default within Setting than it will always bootlop". My a701 have this problem too. looks like @Flupkes Problem too, the different is i Reset it From Snapshot M7 this my old thread and could make the adb working because the usb slot problem.

[Q] Boot freezes/crashes after flashing images

Hello, I'm having some problems with my Nexus 5 LG-D820 32GB
Here is everything I did in order:
1 - Was using stock 4.4.4
2 - Tried to install OTA lollipop following this:
1) Install Minimal ADB and Fastboot.. This will allow you to run commands on your phone.
2) Install Android USB Drivers. This will add the proper driver to recognize your device.
3) Install Universal Android USB Driver. This will automatically add the driver when you go into recovery mode. It's a different driver than the one above.
4) Open Minimal ADB and Fastboot (your phone should be plugged into your USB now)
5) Make sure your phone is recognized (enter 'adb devices'. A long number plus the word "device" should show up).
6) enter "adb reboot bootloader"
7) Use the volume rockers on your phone until it says "recovery mode," then hit the power button.
8) When you get the android with the exclamation, hold power and tap volume up. Don't hold, just tap it.
9) Use the volume rocker to choose "apply update from adb."
10) Go back to the minimal adb and fastbook command prompt, and enter "adb sideload filename.zip". Filename should be the path and the name of the zip file. You can rename the zip file so it's easier to type in. You can also type in "adb sideload" then just drag and drop the zip file into the command prompt if you'd prefer.
11) It should now sideload. Once it finishes on your screen, it will go back to the bootloader and you should reset your system once it's finished.
12) Watch in anticipation as your apps get optimized.
13) Play with your phone.
Click to expand...
Click to collapse
3 - It apparently worked, no errors or anything. But, when the phone tried to boot, it got to the upgrading android screen, with the optimizing apps list (1 of 82), it kept freezing, crashing, showing graphical glitches, and rebooting.
4 - I went into recovery and did a full reset/wipe, thinking it might have been because of an app it was trying to optimize. It still did the same thing.
5 - I thought it might have been happening because I was trying to upgrade OTA instead of a clean full install, so I got the factory image from the google page and tried to flash it following this:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
Click to expand...
Click to collapse
6 - Apparently it went ok, no errors or anything. But the same thing kept happening, it got to the optimizing app screen and would glitch up
7 - I got scared and tried to flash 4.4.4 back with the method in number 5. It worked, the phone was finally usable again. Thinking I had a way to always reset, I decided to keep trying to flash 5.0
8 - Tried again method number 5 with android 5.0, still glitched at optimizing apps
9 - Tried using Nexus Root Toolkit v1.9.4 to flash android 5.0, no apparent error, but got the same results at the optimizing apps screen
10 - Tried using Nexus Root Toolkit v1.9.4 to flash back to 4.4.4, and this time it froze at the twirling balls loading screen
11 - Tried using the method in number 5 to flash back to 4.4.4, and this time it froze at the twirling balls loading screen
12 - ??? I don't know what to do now. I was thinking of trying to flash 4.4.3 using the method in number 5 to see what happens >_>
Any help is appreciated, does anyone know why it kept freezing and showing graphical glitches at the optimizing app screen? Am I doing something wrong? The thing that bugs me is that every attempt went nicely, it isn't like I couldn't flash the images. I did flash them with no apparent error but they didn't work..
Thanks for any help

Hi,
I still have not been able to successfully boot into any usable version of android, they keep freezing and restarting the phone, but no errors appear during the flashing process. Can anyone shed some light?
Thanks

Are you seeing the same boot animation after trying to flash 4.4.4 & 5.0?
Since you used fastboot to flash the factory images, it should have worked. Only thing I can think of is your eMMC died.
This happened to me once on my old Galaxy Nexus. Basically no matter what ROM I would try to flash it would boot to Paranoid Android. Even after flashing factory images with fastboot (encountering no errors) I'd be greeted with the old JellyBean PA boot animation. Never got any errors, but nothing actually worked.
That's why I asked if you're seeing the different boot animation between KK & LP. To me it kind of sounds like your eMMC fried.

RoyJ said:
Are you seeing the same boot animation after trying to flash 4.4.4 & 5.0?
Since you used fastboot to flash the factory images, it should have worked. Only thing I can think of is your eMMC died.
This happened to me once on my old Galaxy Nexus. Basically no matter what ROM I would try to flash it would boot to Paranoid Android. Even after flashing factory images with fastboot (encountering no errors) I'd be greeted with the old JellyBean PA boot animation. Never got any errors, but nothing actually worked.
That's why I asked if you're seeing the different boot animation between KK & LP. To me it kind of sounds like your eMMC fried.
Click to expand...
Click to collapse
The animation is different, twirling pseudo 3D balls for 5.0 and 4 2D balls meeting in the centre for 4.4.4
And every time it stops at a different point. Right after I flash is when it goes the furthest, and then it goes less and less each subsequent boot
I really don't know I think I'll try flashing using the LG Flashtool to see if anything changes

It didn't work... I'm basically out of ideas
Guess I'll try the same things I've already done but with another computer, in the off chance the pc was corrupting something

I'm having the exact same issue. I received the OTA and it failed on install. I tried to install the update through toolkit and it installed fine, but it kept freezing on the initial phone setup. I went back to 4.4.4 through the toolkit and again received the OTA. This time the OTA installed without issue, and I was able to actually get the phone set up, but it kept having graphical glitches, would freeze and requiring a reboot. Went back to 4.4.4 and then followed the procedures on the Google factory images page and installed the update without issue. Again, it won't get through the initial setup without the graphics issues and freezing. I wiped the cache, did a factory reset, and installed the factory image again, with no change. 4.4.4 is working without an issue. I have a friend that is also experiencing similar issues. I'm out of ideas how to get the update to work.

mr2620 said:
I'm having the exact same issue. I received the OTA and it failed on install. I tried to install the update through toolkit and it installed fine, but it kept freezing on the initial phone setup. I went back to 4.4.4 through the toolkit and again received the OTA. This time the OTA installed without issue, and I was able to actually get the phone set up, but it kept having graphical glitches, would freeze and requiring a reboot. Went back to 4.4.4 and then followed the procedures on the Google factory images page and installed the update without issue. Again, it won't get through the initial setup without the graphics issues and freezing. I wiped the cache, did a factory reset, and installed the factory image again, with no change. 4.4.4 is working without an issue. I have a friend that is also experiencing similar issues. I'm out of ideas how to get the update to work.
Click to expand...
Click to collapse
At least you can revert to 4.4.4, mine freezes on the balls/once it did on the initial screen
Using another PC just made things worse, it froze while writing the system image and now the usb recognition is flimsy, sometimes it says the pc can't recognize the device when plugged in and sometimes it works, but now I can't flash things anymore
Welp. It's a less than a month old phone too, and I really think it's gone

Mine has froze a couple of times at that screen as well. I was able to force it into recovery mode with the power and volume down buttons and I was able to use the soft brick function in the toolkit to get it back to 4.4.4.
Sent from my Nexus 5 using XDA Free mobile app

Well I was able to flash 4.4.4 again ( I guess it's really hard to get it completely bricked, always when I thought it was gone it was able to get to fastboot mode)
But it still freezes on the balls / starter config screens

I'm at a loss as to how to fix this and I'm not seeing much online about others having this issue.
Sent from my Nexus 5 using XDA Free mobile app

You said you tried LG Flashtool and that didn't solve the problem either?

I haven't tried the LG flash tool. I'll have to try that tomorrow.
Sent from my Nexus 5 using XDA Free mobile app

mr2620 said:
I'm at a loss as to how to fix this and I'm not seeing much online about others having this issue.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, most problems are people receiving errors/not being able to complete flashing the images. What's crazy about this is that we follow the correct procedure, get no errors or anything, but it doesn't work

I'm still unable to boot. Will try contacting Google soon.

I still have been unsuccessful as well. I'm getting a replacement phone from Google. Should have it next week.
Sent from my Nexus 5 using XDA Free mobile app

Another TF300T brick ? need advice !

Hello all,
I think my TF300T is definitely bricked, but I'd rather have your opinion before trying to switch motherboards....
What are the symptoms :
When I power on the tablet, I have for a few seconds the Asus screen (with "tablet unlocked" on the top), then this Asus screen blinks and the tablet launches twrp automatically (without showing the bootloader (recovery,android,wipe) screen, it goes directly to twrp).
But TWRP won't launch properly, it is stuck in twrp start screen for 30 seconds, then the tablets restarts automatically and the loop I described starts from the beginning.
I cannot event switch off the tablet holding the power button, can only restart it.
I started many combinations described in several posts here to obtain the bootloader screen (I've seen a post with a least seven methods, the only one I did not try yet is to open the tablet and unplug the battery ), none succeeded !
I previously (before the problems) had good adb/fastboot connection with my computer, none of it is working now ! (I've seen a post of someone saying that he had a proper connection for only a few seconds during boot, I tried the steps he described but it did not work either, If I constantly launch "adb devices" or "fastboot devices" commands , I never obtain a response from the tablet. ( I also did the drivers replacements )
How did I get there :
I wanted to install katkiss , before that I installed twrp and formatted /data in f2fs.
After installing twrp I saw that it could not launch properly (it could launch only after flashing it , the next boot it was not working anymore, stuck in launch screen), and that the filesystem was not accessible in twrp any more .
That's where I guess I did the biggest mistake, I used the wipe option in the bootloader (I know now that it was A VERY BAD IDEA ... ) .
I seemed to me that , to perform this wipe, the tablet launched twrp and freezed , but I can be wrong.
I suspect that the tablet saved somewhere that is has to launch twrp on boot to perform the wipe, but as twrp is not launching correctly, the tablets restarts, sees that it has to launch twrp... , then loop again ...
Am I right ? could it be possible that the tablets stored somewhere to automatically start twrp on boot ?
and now ?
Every ways to fix it I read implies having adb or fastboot (I read about nvflash but never used it before, so it seems too late), butI can't use it at the moment !
Any Suggestions / advice ?
Thanks in advance,

hardballer83 said:
Hello all,
I think my TF300T is definitely bricked, but I'd rather have your opinion before trying to switch motherboards....
What are the symptoms :
When I power on the tablet, I have for a few seconds the Asus screen (with "tablet unlocked" on the top), then this Asus screen blinks and the tablet launches twrp automatically (without showing the bootloader (recovery,android,wipe) screen, it goes directly to twrp).
But TWRP won't launch properly, it is stuck in twrp start screen for 30 seconds, then the tablets restarts automatically and the loop I described starts from the beginning.
I cannot event switch off the tablet holding the power button, can only restart it.
I started many combinations described in several posts here to obtain the bootloader screen (I've seen a post with a least seven methods, the only one I did not try yet is to open the tablet and unplug the battery ), none succeeded !
I previously (before the problems) had good adb/fastboot connection with my computer, none of it is working now ! (I've seen a post of someone saying that he had a proper connection for only a few seconds during boot, I tried the steps he described but it did not work either, If I constantly launch "adb devices" or "fastboot devices" commands , I never obtain a response from the tablet. ( I also did the drivers replacements )
How did I get there :
I wanted to install katkiss , before that I installed twrp and formatted /data in f2fs.
After installing twrp I saw that it could not launch properly (it could launch only after flashing it , the next boot it was not working anymore, stuck in launch screen), and that the filesystem was not accessible in twrp any more .
That's where I guess I did the biggest mistake, I used the wipe option in the bootloader (I know now that it was A VERY BAD IDEA ... ) .
I seemed to me that , to perform this wipe, the tablet launched twrp and freezed , but I can be wrong.
I suspect that the tablet saved somewhere that is has to launch twrp on boot to perform the wipe, but as twrp is not launching correctly, the tablets restarts, sees that it has to launch twrp... , then loop again ...
Am I right ? could it be possible that the tablets stored somewhere to automatically start twrp on boot ?
and now ?
Every ways to fix it I read implies having adb or fastboot (I read about nvflash but never used it before, so it seems too late), butI can't use it at the moment !
Any Suggestions / advice ?
Thanks in advance,
Click to expand...
Click to collapse
I guess you've tried this, but power on by holding power+down vol. Should get you to bootloader. Keep holding it until bootloader screen appears. Holding power for 10-20 seconds should power down tablet.
Sent from my HTC One M8 using XDA Free mobile app

Hi
Thanks for your answer.
Yup I tried it, I tried all the ways I found on the internet (there's a post somewhere in this forum where 7 or 8 different methods are explained) none of it worked.

So, did you have TWRP loaded on the regular flash partition vs. the Recovery partition?
Is it possible you were running TWRP as the Operating System, and when you wiped the partition, you destroyed the OS?

TF300T bricked?
Hi,​
hardballer83 said:
Hello all,
I think my TF300T is definitely bricked, but I'd rather have your opinion before trying to switch motherboards....
What are the symptoms :
When I power on the tablet, I have for a few seconds the Asus screen (with "tablet unlocked" on the top), then this Asus screen blinks and the tablet launches twrp automatically (without showing the bootloader (recovery,android,wipe) screen, it goes directly to twrp).
But TWRP won't launch properly, it is stuck in twrp start screen for 30 seconds, then the tablets restarts automatically and the loop I described starts from the beginning.
I cannot event switch off the tablet holding the power button, can only restart it.
I started many combinations described in several posts here to obtain the bootloader screen (I've seen a post with a least seven methods, the only one I did not try yet is to open the tablet and unplug the battery ), none succeeded !
I previously (before the problems) had good adb/fastboot connection with my computer, none of it is working now ! (I've seen a post of someone saying that he had a proper connection for only a few seconds during boot, I tried the steps he described but it did not work either, If I constantly launch "adb devices" or "fastboot devices" commands , I never obtain a response from the tablet. ( I also did the drivers replacements )
How did I get there :
I wanted to install katkiss , before that I installed twrp and formatted /data in f2fs.
After installing twrp I saw that it could not launch properly (it could launch only after flashing it , the next boot it was not working anymore, stuck in launch screen), and that the filesystem was not accessible in twrp any more .
That's where I guess I did the biggest mistake, I used the wipe option in the bootloader (I know now that it was A VERY BAD IDEA ... ) .
I seemed to me that , to perform this wipe, the tablet launched twrp and freezed , but I can be wrong.
I suspect that the tablet saved somewhere that is has to launch twrp on boot to perform the wipe, but as twrp is not launching correctly, the tablets restarts, sees that it has to launch twrp... , then loop again ...
Am I right ? could it be possible that the tablets stored somewhere to automatically start twrp on boot ?
and now ?
Every ways to fix it I read implies having adb or fastboot (I read about nvflash but never used it before, so it seems too late), butI can't use it at the moment !
Any Suggestions / advice ?
Thanks in advance,
Click to expand...
Click to collapse
Hi, Had the same thing happen to mine. Hold own power to force shutdown then hold volume down and recovery screen should come up. Worked for me.!

@hardballer83
Unfortunately a bad situation caused by yourself!
If you don't have any fastboot or ADB-access to your tablet now, only a new MB can bring your device back to life again.

Recovery Mode "REMOVED"

The title says it all, but I explain calmly how it happened.
I was trying to want to install the official version of LineageOS for my Zenfone 2 and after downloading all the necessary files, have formatted and clean everything (except the SD), trying to install the new custom rom and then have the same "error 7". Then I realized immediately that lacked the Bootloader for Marshmellow, so I tried to look for a ZIP file for this, being able to find it right for my smartphone. The folder was known as "M_BL_upgrade_for_zf2_ze551ml_6.0" and once I had entered the USB cable to my PC and started the "Upgrade.bat" program, after the strangely reboot bootloader returned closed (it was understood from the screen, which instead to be white background with black writing was black with white lettering), then I tried to go back in recovery mode, realizing that every time I tried to get in, it was as if I were locked in a deadly circle and then kept restart and then return to where we started ... you have any idea how to do it, maybe re-add the Recovery Mode standard via CMD?

Primux Sirico 2 issues

Hello everyone, I have lots of issues with this tablet since I bought it. It works painfully slow, yet resetting it doesn't change anything, still the same problem. I also tried to root it via Kingroot and it werk, however it took me lot of time due to the system being unresponsive / unstable and almost useless. It comes with android 4.0.3 and I also tried looking up for any possibilites to reinstall the firmware since I'm extremely sure it could be caused from the firmware it also got installed from the factory. I also tried searching for custom roms and other ways around for TWRP or any custom recovery, but no result. I also tried up with the Flashify app to try extracting / backing up / dumping the recovery and the kernel but the app freezes up. I also tried a possibility to update the firmware from their official page, hence it failed to do so since it gives an error in their flashing software that dosen't tell me nor it logs it what it could be caused up from the connecting part.
primux.es/producto/tablets/tablet-primux-siroco-2-101/189
(not sure if anyone understands spanish thought but I can translate if needed)
This is the page from where I tried to download and install their software and their firmware down below on the page. primuxcomputers.es/primux/siroco2upgrade.pdf
There are the instructions where I tried to follow but at the "Imagen 9: Icono" part got me stuck in there. It requests me to insert the cable in the tablet holding the "Home" button and while holding it, plugging in the USB cable throught PC, and tap quickly the "Power" button 3 times. However it gives me a red X icon and yet nothing shows up in the devices: No ID, no other kind of detection no logs no nothing. After it showed up the X on the status, it disconnects itself and it changes to ready / green icon and plugs itself in again but nothing really happens to detect it again thought.
I also tried to boot in recovery mode but nothing happens menawhile Flashify keeps on the rebooting in recovery mode in loop doing nothing else... I'm seriously in pain with this tablet. And if you ask me to return it, not gonna even bother doing that..
I seriously hope any answer very soon and don't get dissapointed by the ignorance of this topic..