TWRP manager boot is blinking while switching the phone
after installing cyanogen i found that my phone's internal memory was full. So i decided to format my phone's internal memory. i formatted it from settings page from "Back up and reset" i erase internal storage then after it was rebooting. After that teamwin label is now blinking and nothing is happening. The phone is now like dead. idk how to install a new rom while there isn't any way to open TWRP recovery mode or stock recovery mode. I really appreciate that you replied my text but i need a solution and please bro can you make a tutorial or something that can bring my phone back to working condition?..
Ketan Arora said:
after installing cyanogen i found that my phone's internal memory was full. So i decided to format my phone's internal memory. i formatted it from settings page from "Back up and reset" i erase internal storage then after it was rebooting. After that teamwin label is now blinking and nothing is happening. The phone is now like dead. idk how to install a new rom while there isn't any way to open TWRP recovery mode or stock recovery mode. I really appreciate that you replied my text but i need a solution and please bro can you make a tutorial or something that can bring my phone back to working condition?..
Click to expand...
Click to collapse
Reflash the recovery via fastboot, while in bootloader.
Related
I successfully rooted my G2 and then decided to install Miui. I did so by downloading Rom Manager. I selected to install zip file from SD card in Rom Manager, but did not back up my current ROM, because it did not work when I did ask to back up. When the phone restarted it goes to the Miui main boot up screen with the orange and purple lines and it just stays there flashing every 30 seconds or so. I then tried to restore to factory settings and no matter what option I chose from the main screen, my phone just sits on the icon with the top hat and orange arrow for hours doing nothing. Hopefully this is not irreparable. Please help me in anyway you can.
Try re-flashing. If you can get to the clockwork mod screen do a factory reset, then go advanced menu and toggle on usb mode and connect to your PC. This will give access to the sd card via windows. Then you can transfer a doable ROM zip file to it, or retry the downloaded file, but make sure you factory reset clearing all data, cache, dalvik cache etc. first. Let me know how it goes
i fixed it by installing a the factory ROM on the root of my SD card.
I have a updated g2x (gingerbread via Lg updater) installed NVflasher was able to boot into recovery performed a nandroid back up did a full wipe and was going to flash Xbroarders rom until i relized i put it on my internal instead of external so i then tried to flash my back up and got "no file found"did a reboot and all im getting is a black screen wit flashing keys. plz help
Try reflashing Clockwork Mod Recovery.
Sent from my LG G2X using XDA Premium for Android
Do that, and if you have the means, try to check out the external sd on some other device to see what's going on. I'd start with pulling the battery for a bit and try flashing the backup again.
Also, correct me if I'm wrong but if you didn't flash anything because of misfiling xboarder's rom, there was no reason to use the backup in the first place.
dachinaman said:
I have a updated g2x (gingerbread via Lg updater) installed NVflasher was able to boot into recovery performed a nandroid back up did a full wipe and was going to flash Xbroarders rom until i realized i put it on my internal instead of external so i then tried to flash my back up and got "no file found"did a reboot and all im getting is a black screen wit flashing keys. plz help
Click to expand...
Click to collapse
Where did you put your nandroid - internal or external SD? They would have been determined by the recovery option you chose - Internal or External SD. Your stock ROM would download the Xboarder ROM to internal in any case, but your nandroid location depends on the choice above.
Since you did a total wipe, you do not have a ROM installed, so you will not be able to boot up, but you DO NOT have a brick.
You could flash the Recovery again with the Oneclick Recovery tool and choose internal, and then you could flash the Xboarder ROM. After that, see if you can find your backup (in the clockworkmod folder).
gaww said:
Since you did a total wipe, you do not have a ROM installed, so you will not be able to boot up, but you DO NOT have a brick.
Click to expand...
Click to collapse
I didn't know that a wipe from cwm clears out the rom. I only ever wiped before flashing something else so I assumed it was more like a factory reset.
heysharon said:
I didn't know that a wipe from cwm clears out the rom. I only ever wiped before flashing something else so I assumed it was more like a factory reset.
Click to expand...
Click to collapse
As far as I know, the wipe data/factory reset is exactly that.
There's also a wipe system function, which wipes the entire ROM also. It seems he did that also.
As for fixing the phone, what gaww said haha. If xboarder's mod isn't there, then in recovery while the phone is plugged in, mount the sd card, and put a rom on there using windows explorer or whatever, then disconnect and you should be able to flash it.
dachinaman said:
I have a updated g2x (gingerbread via Lg updater) installed NVflasher was able to boot into recovery performed a nandroid back up did a full wipe and was going to flash Xbroarders rom until i relized i put it on my internal instead of external so i then tried to flash my back up and got "no file found"did a reboot and all im getting is a black screen wit flashing keys. plz help
Click to expand...
Click to collapse
Boot into recovery, go down to mount, and mount usb. Then find the file on your internal sd and move it over to the external sdcard. I have had to do that a few times when I forgot to move the file.
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
dwl99 said:
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
Click to expand...
Click to collapse
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
DigitalMD said:
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
Click to expand...
Click to collapse
Thanks but Odin cannot see the tablet to re-flash the recovery.
Downlods mode
Then flash new firmware
sembre said:
Downlods mode
Then flash new firmware
Click to expand...
Click to collapse
That's the problem - I cannot access download mode
UPDATE - it just started in download mode! I can manage from here!!
Just for the record you can install adb on the pc and run the command 'adb reboot recovery'. This will force the tablet to reboot in recovery mode.
Sent from my GT-I9300 using xda app-developers app
Jeez, this has taken up most of the day to fix. I came across many problems I have not previously experienced:
1. When the tablet was stuck at the boot animation and I tried to turn it off by long-pressing the power button it immediately restarted. The only way I could get it to turn off was by long-pressing the power button whilst it was connected to my PC.
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
3. Flashing CWM with Odin caused the tablet to reboot into the stock ROM which would not load, in the end I had to untick the "reboot" button in Odin, power it off then manually restart with the Vol- & power buttons.
4. The only way I could get a bootable ROM was by flashing CM10 with CWM. I tried to restore 2 previous CWM backups but on each occasion there was an error restoring the Data partition and I got stuck at the scenario at (1). The backups were made to the external SD card with CWM Touch - is the Touch version unreliable?
I would be really interested if anyone could shed any light on any of this stuff!
For how long did you let it install during the first reboot? It happened to me too, and it took about 10 minutes, maybe even more...
Also, did you try in the "Mount and storage" cwm menu the options "format system", "format data", "format cache" and "format preload" options, prior to re-flashing a ROM? I have read somewhere that for a clean install it's better to do this, as it really clears everything that could mess up the system between two different bases ROMs (like CM and stock).
What I do everytime is using in CWM these 4 "format" options, plus "wipe" system, cache and dalvik, then immediately after this I flash with cwm the new "zip" copied on the card. Then the first reboot is much longer than usual, as at this stage it installs the files, rebuild the dalvik cache etc.
Good luck
dwl99 said:
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
Click to expand...
Click to collapse
I think I gave it a good 20 mins to boot. When I got up this morning there was an error message saying that there was no room to install any more apps even though I had very few installed. Settings -> Storage would not calculate the space available so I figured that the partitions had become corrupted. I did the step by step format you described and reflashed & it all seems to be OK now.
I have rooted my gt i9105 and also by fluke I changed the kernel. now whenever I reboot in recovery mode phone get stuck at samsung screen. I did factory reset. But if I try to restore by cwm it again get stuck at rebooting.
the major problem is even after doing factory reset my device shows internal memory as 0.00B. and sdcard folder is also empty. when I try to download something from web it says please enter memory card....
rizwan92 said:
I have rooted my gt i9105 and also by fluke I changed the kernel. now whenever I reboot in recovery mode phone get stuck at samsung screen. I did factory reset. But if I try to restore by cwm it again get stuck at rebooting.
the major problem is even after doing factory reset my device shows internal memory as 0.00B. and sdcard folder is also empty. when I try to download something from web it says please enter memory card....
Click to expand...
Click to collapse
Flash full stock firmware for ur device via Odin and reset settings in recovery. Then it should work normal.
After doing this will I be able to restore backup which I have taken using cwm ...
About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.