So a friend recently bought this spanish voxter tab 97 IPS (16GB) and after a few days of usage and several attempt to install a custom ROM, the tablet stopped booting. According to him, he tried loading a "compatibility bla bla bla.zip" file with CMW which I really do not know what it is, and since he did the installation, the tab stopped booting into system. Every time it's turned on, it just stops at the boot screen and nothing more. Although before this, he had installed a custom recovery and had also done a Nandroid backup with the recovery. However, what baffles me is, CMW is no longer accessible through the normal "power + volume up" key combo and I'm quite unsure of how to boot into fastboot.
That aside, I tried booting into recovery with adb because apparently, adb recognizes the device whenever it's stuck at boot screen, this also failed, neither did rebooting into fastboot via adb work. All I need to know is if this device is totally bricked, or if there's still something I can do. If there's any, I really would appreciate every help offered. Thanks..
Related
My phone restarted one day and just wouldn't boot up. At first it was just stuck on the SAMSUNG logo, but after trying to boot into recovery, it now sits at the boot animation. When I try to boot into recovery, the CWM screen will come up, but no menu will show up, and then the phone will restart after a few minutes and go back to being stuck on the boot animation.
I can enter Download Mode, but USB Debugging must be disabled since ADB won't recognize the device and I can't send any commands (yes, drivers are installed).
First of all, is there any way I can recover the data on the phone? That is more important than getting the phone working, since I was just about ready to get a new phone anyway.
What can I do to get the phone working? Everything involving flashing a new kernel, or resetting the phone back to factory seem to require a working recovery or the ability to send commands through ADB, but I'm probably missing something, since there must something else that I can do.
Any help is greatly appreciated. Thanks.
**Not sure if this is related or not, but the reason why the phone restarted before this issue occurred is because the power button on the phone is a bit faulty. Over the past couple months I've been having issues with the power button; it seems overly sensitive so when I push it sometimes the screen will turn on and off and other times the phone will just restart as if I held the button down for too long. This is the main reason why I was ready to get a new phone.
Hello,
I own an Android tablet KO PARA1 FULL and experiencing a strange problem. This is a chinese atm7029 quadcore tablet (16gb, 1gb ram, without bluetooth, only wifi, bu supports 3g dongle), running android 4.1.1 nad 3.4.0+ kernel, which came prerooted. After some time I've decided to install backup programs on in to make a full backup of the device for the case something would go wrong, and after some trying I descovered, that there is something like recovery for that purposes which seemed a good solution for me. I decided to install CWM, which I managed to install without problems and made some backups on my device. Everything was fine, I did some factory resets through the time, some restoring processes from my previously backup states of the device, was always able to activate CWM recovery menu through Reboot to recovery or through combination of Volume down a Power button...
Until last saturday. I was normaly surfing the internet, reading mails and afterwords I powered my tablet off (it is draining battery in sleep mode, but its another story..). After a while wanted again to write a mail, so I powered it on. In that momet seemed the screen too dirty for me and I tried to cleen it little bit throug the bootup process. Unfortunately I obvious confused the system with it and after boot it was not responding properly. I did not wait enough and after a while powered it off with power key pressed for a long time, to make a new boot.
But when I powered it on again, it stayed stuck in boot logo and did not boot at all. I've tried a copple of times to boot it again with no cuccess, stayed stuck in boot logo for more then 10 min...
Afterwards I decided to make it boot up with the help of computer. I downloaded adb and drivers and somehow managed to make it boot up. I thing I was too excited to see it boot up again, that during boot up process I desconected my device from computer...
My worries were reliesed and I thought it would be a good idea to make a restore from backup to prevent some strange behaviour, so wanted to boot into recovery, but nothing had happened. After some repeated clicks on Boot into recovery button, as well as app called rebooter with nothing happening, I decided to try it out through button combination. It has not worked as well Next try was to reset to factory settings. But when I go through the menu, I can click on reset to factory settings button, seeing warning that I will lost ma data, then I can push the button to make it happen, but nothing is happening. I see only the screen with the button, can touch it 100 times and the tablet stays on, fully funcional. making no factory reset as it done before.
I did a lot of reading and searching, but have not find answer for my problem. I flashed recovery images from my backups (using flashify, flash gordon, adb shell, terminal emulator), from all previously functional states of the device. I refleshed the CWM recovery downloaded from the internet for my chipset, which previously did the job just perfect, with no success...
I am still not able to reach recovery menu. For me it seems like the bootloader would be locked, but I did not find the answer how to unlock it without to be able to start in some recovery state to use fastboot command to unlock it.
Otherwise, my device is functional, still rooted, i can use it without any other problems. But not be able to do recovery from my backups, even do a factory reset.
How can I restore my access to recovery mode? Is it somehow possible?
Hopfully it is not too much information (tryied to follow the intructions and wrote everything I thought would be important to know about) and you will not be bothered to read all my story and pull me out of my darkness with helpfull suggestion.
Thanks a lot in advance
Steve
So I flashed a new ROM by the Spanish guys at Team Force (great looking ROM), via CWM, and so naturally I got the boot loop problem.
Normally solvable by turning off the phone, booting into recovery and then performing a factory reset, right?
Here's the problem - this appears to be one of the only android cellphones in existence where you CAN'T boot into recovery using the normal power + volume key combinations.
Essentially, I've bricked the phone without actually REALLY bricking it.
Did I miss anything, or does it sound like a quick end of line for this phone?
Edit: Well, if I connect my phone via USB and have ADB running in the background, holding the volume up key during the boot loop does bring up recovery mode.
It seems to me that the installation of said ROM simply doesn't fully complete before it tries to reboot itself, which could be why this is happening.
I apologize if this is in the wrong place, and I've really tried searching around, but nothing seems to work/ is tailored to the m8.
So, I just got an M8 new out of the box, rooted it and successfully installed cyanogenmod. Problem is, I was playing around with it, trying to get the GApp store and somehow (did what i think was) deleted my roms completely. Now upon booting up the phone I just get the "This build is for dev..." screen, and with the volume down+Power button to access recovery mode I constantly get put back to the fastboot screen. I tried flashing a custom recovery as in "Phone arena CWM flash recovery" guide, but no luck because my computer is reading the device as offline. I honestly have no idea what to do, and if anyone could help me I would be so greatful...
TL;DR: Stuck on boot screen, can't enter recovery mode, think i deleted all my roms, help please
On a scale of 1 - bricked, how bricked is my phone?
HUGE DEVELOPMENTS, GUYS! I've been able to access recovery mode again by re-flashing ClockWorkMod.
ctran1 said:
On a scale of 1 - bricked, how bricked is my phone?
Click to expand...
Click to collapse
On that scale, you are zero. If the screen comes on, you aren't bricked.
Hi guys, I really need your help.
I'm new at this rooting stuffs and I tried to root my Oppo Neo 5.
I tried so many softwares like OneClickRoot, FramaRoot, and Kingroot but none seemed to work.
So I resorted to an app called oppo tools
It worked at first but I got really annoyed when my status bar suddenly colored to red when my phone discharges to 15% so I unrooted my phone and rooted back again. I really thought that was going to fix my problem but that's where the bootloop issue started.
I tried to flash some custom recovery zip but it failed since I only have a stock recovery.
But the thing is, I found a guide that says to rename the clockworkrecovery img to PG86IMG.zip.
So I did tried that and as soon as I flashed the zip from my stock recovery, my phone hanged.
I long-pressed the power button to restart and boot into recovery mode but nothing seems to happen.
I'll try to explain a bit more on how it looks when I boot my device.
When it boots normally (I mean not pressing the volume to enter recovery mode) it will only show the logo but when I try to go into recovery mode it will show the logo with a little text on the lower left portion "Recovery Mode"
Before I flashed the PG86IMG.zip, recovery mode was still working and the charging screen when off is working too.
but after I flashed the zip, every time I try to recovery mode the logo shows up with the little text but RECOVERY MODE isn't working. When I charge my phone it automatically boots up and shows the logo and text like it's trying to go recovery mode (I'm just trying to charge? It's going to recovery mode)
I tried using "adb devices" on cmd but it's not detecting any devices.
I'm really out of ideas guys, I know not all people use this model but what would be your suggestion?
A suggestion on how to fix this would really be appreciated :good:
I'm sorry I'm really new at this, please correct me if I did something wrong starting this thread. :angel:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Salman Al-Badgail said:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Click to expand...
Click to collapse
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
DeepBricked said:
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
Click to expand...
Click to collapse
You made a soft brick, not to worry flash it with correct stock firmware, if the phone is in warranty than ask them to do flash, this will take approx 10-30min. If it isn't in warranty than you should try it own or else pay some amount and the rest they will do.
Salman.
how about bootloop, cant enter recovery, reboot continiously when turn on even going to recovery, only fastboot isnt rebooting automaticaly but pc days drivers not succesfuly installed, and when off it qont detect by pc because of rebooting auto,
where can i find a rom for my oppo neo 5
pls help me pls