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
Related
Hey everyone! Lately i've been trying to unlock my BL and never really got to a solution, me being the total idiot I am, I was messing around with fastboot to see if I could do something with the "hidden" menu while holding down the down volume while fast booting. I tried first, flashing ics xloader and u-boot on jellybean and without booting the phone I did the Jellybean xloader and u-boot. When I booted the phone the normal screen faintly had the same weird screen stripes fastboot has. I flashed v20f and the phone didn't boot, it hung at lg, I did a hard reset and it booted. I rooted and tried to use cwm restore to restore all my apps and I keep getting error while restoring \(system, data, cache). I can however create new backups and restore them.
When I use the phone as is, when I lock it sometimes, then try to unlock it, the phone stays black but responds to touch. I noticed if I managed to change the brightness the screen would go back to normal, but would eventually crash. Everytime I try flashing kdzs' I have to hard-reset. The phone also connects to the pc but only as the installer for drivers.
I actually don't know where to get my cwm logs, so if someone could tell me real quick that would also be appreciated.
P.S. I created the backup before everything, when the phone was fine.
AlbinoCookie said:
Hey everyone! Lately i've been trying to unlock my BL and never really got to a solution, me being the total idiot I am, I was messing around with fastboot to see if I could do something with the "hidden" menu while holding down the down volume while fast booting. I tried first, flashing ics xloader and u-boot on jellybean and without booting the phone I did the Jellybean xloader and u-boot. When I booted the phone the normal screen faintly had the same weird screen stripes fastboot has. I flashed v20f and the phone didn't boot, it hung at lg, I did a hard reset and it booted. I rooted and tried to use cwm restore to restore all my apps and I keep getting error while restoring \(system, data, cache). I can however create new backups and restore them.
When I use the phone as is, when I lock it sometimes, then try to unlock it, the phone stays black but responds to touch. I noticed if I managed to change the brightness the screen would go back to normal, but would eventually crash. Everytime I try flashing kdzs' I have to hard-reset. The phone also connects to the pc but only as the installer for drivers.
I actually don't know where to get my cwm logs, so if someone could tell me real quick that would also be appreciated.
P.S. I created the backup before everything, when the phone was fine.
Click to expand...
Click to collapse
There are save log to sd option in cwm advanced menu.
Try to format /data before restore backup. This may help you boot pass LG logo.
Sent from my LG-P768 using xda app-developers app
Recovery log
Heres the cwm log. From what I could tell, is there something wrong the eMMC?
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..
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
whitechameleon said:
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
Click to expand...
Click to collapse
i have now tried to flash the firmware while in download mode using a less than legitimately obtained lg R&D tool. however, i need V10F_00.kdz and i am facing a bit of censorship. any kind soul willing to host this file on dropbox or similar so i can download it?
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
J2270A said:
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
Click to expand...
Click to collapse
believe me i have. the only combo i can get to is download mode. there is a combo for a hard reset, but my touch buttons arent active during boot.
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.
I have a Umidigi Crystal (2/16) and it´s not booting anymore.
How that came is a long story.:crying:
I got the phone, wanted to root it and while I was enabling usb debugging in developer options, I noticed you can root it from there as well.
I have no idea whether thats a Umidigi special or if that was seen on other phones too, basically I had a slider option to enable root access.
After a reboot, SuperSU was installed automatically, root checker, file explorer and rom toolbox worked fine with it but I actually rooted to get Xposed Installer.
That worked very well too, only did I want to have a custom recovery to prepare my phone in case of a bootloop.
So I followed these instructions.
I hadn´t unlocked the bootloader by the time and since the instructions said I would have to unlock it I did that first using these instructions.
Everything worked as expected but from this point on, on the pre-bootanimation picture my screen would say
Code:
Orange State
Your device has been unlocked and can't be trusted
Booting in 5 sec...
As everything else was the same as before, I just ignored it.
Then I moved on to installing TWRP by, again, these instructions.
The process seemed to work but after finishing, I was unable to boot into recovery mode, my phone would just boot into the normal OS(which still worked by the time).
I wanted to get around that by using this app but because of the unlocked bootloader my phone was factory reset
and I had to root again.
I was going for the same way I already did it beforehands and I was asked to reboot again.
After that point, my phone was stuck in the pre-bootanimation screen saying it´s orange state thingy again and would just stay there forever.
I tried installing the stock rom from here ((2/16 - V1.0_20171026)) to get rid of the root setting I enabled.
Now I get the pre-bootanimation screen with the orange state text again and after 5 seconds it keeps the background image but the text disappears.
Thats where it´s stuck for like 3 hours now.
When I press the power key a couple of seconds, that loop starts again, I can´t turn the phone off.
Things I can still do:
•Reboot (holding the power button, still get stuck the same way though)
•Access a PC, the internet, an SD Card and electricity
•Charge the phone
•I still have all the drivers on my PC properly installed
Things I can´t do
•Keep the phone turned completely off
•Boot into fastboot, recovery or normal OS
•Get the PC to recognize my phone (not even the adb)
What I want (if possible in that order):
•Boot into literally any OS
•Use the current OS or any custom rom
•Have root access without the developer option method
•Have TWRP
•Unlocked Bootloader
I know, I ask for a lot but this is the only phone I have right now and I badly need it.
Getting it to boot again is really the primary goal here.
Thanks so much to everyone who tries to help me, it really means a lot