I have a vankyo matrixbox x95 plus that I turned into a retro gaming center. Anyway, I asked how to make emulators close when I pressed the home button and was told Tasker and supersu. I installed supersu and it said that I needed to update. Did that and have been stuck in boot loop since. For the last 3 hours I have been trying to get it to boot. Tried resetting to factory 1000 times, didn't work. Tried flashing another supersu zip file, read about it in another group, didn't work. Instead it just said "bad recovery detected no unzip". Hunted down, what I hope is, the original rom and tried to flash and it says the same thing "bad recovery detected no unzip". Please someone shed some light on this I'm going crazy
Keep trying different freshly formatted usb thumb drives until it works properly again.
Days later and still in boot loop hell. So glad I installed supersu and turned my box into a paperweight. Got firmware from here and followed the directions for burning tool, doesn't work just errors out after 1 percent. Then I tried a bootable USB, can't get it to boot. Ahh the joy
Related
I recently installed a gingerbread rom Lidroid. it was working ok till i realized i could not stand some bugs. I decided to try cyanogen that was released today. It looked like it installed fine but the phone is stuck trying to install clockwork recovey. it keeps going on and looping at the same screen. the last message it shows before it reboots off is "Replacing stock recovery with Clockworkmod" it just keeps looping doing the same thing. I have tried to get into download mode without success. I have been able to put my phone in download mode the past couple times i have run into trouble. Now i simply cant be able to do it. Any help?
I dont know how it happened but after trying for the past 5 hours, i have been able to get it to work. I took the battery out inserted it back in. I held the volume down button and the power button together. i immediately plugged the phone into USB cable while still holding Vol down and power button. After 10-15 seconds, it brought up the clockworkrecovery. I Wiped everything and the cache. I then tried to reinstall cyanogen(the one that brought all this in the first place) because it was the only one on my sd card. It installed and booted up and now i have CM 7. I can also successfully get into Download Mode
Am not sure what i did, but if anyone can run into such a problem you might try this.
Hello everyone!
I have a Lenovo a820 with Lambda rom 2.4v.
I'm using it for a couple of weeks now with this last version, and everything was fine, until suddenly it froze for a while, I unplugged the battery and plugged it again, and what I notice was that the phone restored itself to when after I installed the rom (meaning all of the apps were gone).
So I tried going into Google play, installing some apps back, and I get this error -24 telling me its unable to install the app, happened with any app I tried. so after trying a few suggestions from the internet about this error, I decided to format it and install the rom all over again.
I go back to recovery mode with CWM, try to install the lambda rom like I did before, and in the middle of the installation it reboots and gets stuck in the "lenovo" screen like when you boot it. so after waiting for a long time I unplugged and plugged the battery again, went through the procedure again this time it installed it 100% rebooted so it would boot with the mod, and again, it freezes at "lenovo" start screen unable to boot.
went on recovery mode, formatted system, data, emmc, everything... I think that's the issue here. but im not sure.
After that, tried to install again with the same problem.
The problem now is. it won't even start I press the on/off button to start it normally, and I dont even get the "lenovo" screen, I tried going into recovery mode and no luck.
It's like the phone is dead! Although I have another Lenovo A820 and I tried the battery, and its 60% so that's not the battery.
Do you guys know any tricks? or any tools that I could use to get my phone running again?
I would appreciate it very much, any help you can give.
Matt.
MatWho said:
Hello everyone!
I have a Lenovo a820 with Lambda rom 2.4v.
I'm using it for a couple of weeks now with this last version, and everything was fine, until suddenly it froze for a while, I unplugged the battery and plugged it again, and what I notice was that the phone restored itself to when after I installed the rom (meaning all of the apps were gone).
So I tried going into Google play, installing some apps back, and I get this error -24 telling me its unable to install the app, happened with any app I tried. so after trying a few suggestions from the internet about this error, I decided to format it and install the rom all over again.
I go back to recovery mode with CWM, try to install the lambda rom like I did before, and in the middle of the installation it reboots and gets stuck in the "lenovo" screen like when you boot it. so after waiting for a long time I unplugged and plugged the battery again, went through the procedure again this time it installed it 100% rebooted so it would boot with the mod, and again, it freezes at "lenovo" start screen unable to boot.
went on recovery mode, formatted system, data, emmc, everything... I think that's the issue here. but im not sure.
After that, tried to install again with the same problem.
The problem now is. it won't even start I press the on/off button to start it normally, and I dont even get the "lenovo" screen, I tried going into recovery mode and no luck.
It's like the phone is dead! Although I have another Lenovo A820 and I tried the battery, and its 60% so that's not the battery.
Do you guys know any tricks? or any tools that I could use to get my phone running again?
I would appreciate it very much, any help you can give.
Matt.
Click to expand...
Click to collapse
The boot.img must be wrong try rom for your phone.
Sent from my Moto G
I tried updating my ROM (to CM11) and came across so many issues. For some reason, it kept rebooting and then at one point just got stuck at the animation screen. So I decided to just start everything from scratch again.
I tried to get into download mode to install CWM, but the phone kept shutting off as soon as I got in. After MANY tries, I finally got in and got it installed. When it finally worked, I tried to get into recovery mode and the same thing happened. Finally after many tries I was able to get in there too. I then installed my ROM and then when it finally loaded, the phone then shut off and tried rebooting but wouldn't get passed the animation screen again.
I did a lot of research and found that some people had their internal power button either get stuck or become defective. Mine clicks so I don't know if that's the problem, but the symptoms that others have mentioned have all happened to me.
Does this in fact sound like a button issue to anyone? Any help is appreciated.
moraha1287 said:
I tried updating my ROM (to CM11) and came across so many issues. For some reason, it kept rebooting and then at one point just got stuck at the animation screen. So I decided to just start everything from scratch again.
I tried to get into download mode to install CWM, but the phone kept shutting off as soon as I got in. After MANY tries, I finally got in and got it installed. When it finally worked, I tried to get into recovery mode and the same thing happened. Finally after many tries I was able to get in there too. I then installed my ROM and then when it finally loaded, the phone then shut off and tried rebooting but wouldn't get passed the animation screen again.
I did a lot of research and found that some people had their internal power button either get stuck or become defective. Mine clicks so I don't know if that's the problem, but the symptoms that others have mentioned have all happened to me.
Does this in fact sound like a button issue to anyone? Any help is appreciated.
Click to expand...
Click to collapse
Seems like your hardware button could be broken, I would all do in this order:
Download Philz Touch Recovery from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/
Official Firmware from here: http://www.sammobile.com/firmwares/3/?download=28378
Flash Philz touch through Odin
Reboot to Recovery, selct "Clean to install a new rom"
Wipe cache and dalvik cache
Go to downoad mode and flash the md5.tar file through odin
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
yoda254 said:
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
Click to expand...
Click to collapse
My guess is that when you rooted with CASUAL, it changed the Samsung device driver on your computer and you need to reinstall the Samsung driver to get the computer to recognize the phone again in download mode.
Underneath step 7 of section 1b on Droidstyle's restore guide, he discusses issue with CASUAL replacing the Samsung driver... and he gives a link to Jeremy Loper's fix... "If odin no longer recognizes your device, most likely Casual killed the driver for odin!! follow this tutorial for restoring the driver: http://www.youtube.com/watch?v=zzghcV8HVVk"
Once the computer recognizes the phone again, you should be able to use ODIN to restore back to 4.1.2 so you can root/unlock again with CASUAL. After you get the phone restored with Odin, I would recommend booting into Stock Recovery and wiping cache/doing factory reset before running Casual again... this would enure you are starting over with a totally clean slate.
If the above doesn't work, then here's a thread where I tried to help someone else who couldn't get their computer to recognize the phone.... maybe some of those ideas will help - http://forum.xda-developers.com/showthread.php?p=55833998
Good luck!!
1 step forward two steps back. I got my pc /odin to recognizes my note 2(changed usb cords). Then tried to odin back to stock 4.1.2. At first odin kept saying (odin not responding) and would ask to close the program,after several attemps i final got it to flash the 4.1.2 file. When i flashed the file and was at the point where it reboots, it would not get past the samsung note 2 logo and continued to flicker and not boot up even when i tried to put it into download mode like it said to in this thread. http://forum.xda-developers.com/showthread.php?t=2024207. When i tried to reflash the file it failed. when i attempted again it just hangs at setupconnection. Tried again and it failed. Btw thanks for the help mattnmag.
Got it working! i simply forgot to place the sch-i605 pit. into the pit section of odin when i flashed the 4.1.2 rom.
Similar problems
I was running AllianceROM 26. My phone had been spontaneously rebooting for a bit recently. Today, it started to spontaneously reboot again, but this time, it never got past the Galaxy Note 2 screen. After pulling the battery, I tried to boot into TWRP. It just hangs on the twrp boot screen for a few minutes but never goes into twrp.
I figured I would try taking it back to stock. So, I used ODIN to try and put 4.1.2 on it and a new PIT file. That appeared to work fine. I got no errors in ODIN. However, I still cannot get this thing to get past these boot screens, either the Galaxy Note 2 one or TWRP when I try that there. I have tried this twice now, once with re-partition checked and another time with re-partition unchecked (saw conflicting instructions on that so I figured I would try it both ways). I still am not getting past the boot screen.
Any help or ideas are appreciated as right now, my phone appears to be bricked and I am out of ideas.
so what was the solution to the teamwin flashing on and off after a factory reset? this is certainly not a solution, having to reflash the phone...
Hi
Rooted my S6, and threw TWRP recovery on, put a "sixperience S7" rom on it, at first it worked flawlessly, but since I didnt make a factory reset i pulled one later, thats when my problems started.
Installs fine, reboots and the initial start and setup goes fine, but when the screen turns off and i wake it up again, the screen looked like a pc screen with no gfx driver, funky colors and very dark - tried two times to make a clean install, same happened
Tried to install stock rom with Odin, failed, tried 3-4 times, fails
Then i went into TWRP and deleted all......but seriously all......coudnt boot into anything then, not even download mode, got the message on the screen that "something went wrong in updating the firmware, try the emergency recovery with Samsung Smart Switch" That of course couldnt connect to the phone, when i finally got it to be recognized by the computer, my phone wasn't supported by the program (because it is rooted i read somewhere)
After an hour with a lot of swearing and crying almost, I tried to connect it to Odin and i got connected, installed a new TWRP and i got it into recovery where i could install a new rom, and the phone booted again
Heres my question, when i put it into download mode (tried to install stock rom with Odin once more) then I cannot boot it again, I have to install TWRP and a new rom before I can get it up and running again, is there any possibility to get a stock rom installed ever again?