So, basically, i rooted my phone(WYNN SK S150) a month ago and flashed a custom ROM onto it. All was well, until yesterday, when i factory reset my phone normally(using the factory reset option in settings and not the clockworkmod way). When the phone restarted, it was stuck into a loop of the boot animation(the animation of the custom ROM logo and not the default ROM) and is practically unusable. I cant access it through my computer(Computer doesnt identify it, just says its an unknown device) and i cant access recovery mode.
NOTE: i have a backup of the default ROM.
Can anyone help?
Hope my phone isn't "bricked"...
Related
well
i got an alcatel ot908 3 days ago, i installed clockworldmod recovery and after rooting it, i backed up so i can flash a rom but this didn't worked, rom wasn't working as thephone stucked on the boot screen saying "alcatel one touch" and nothing was happening... so i restrored the backup i had made and everything was fine, yesterday i installed a lot of stuff and i wanted to reset factorysetting so i shutted down the phone and went into recovery screen, i wiped everything but since then the phone stucksagain on the boot screen, tried reseting again to factory settings but nothing, i also wiped cache and other stuff but still won't boot. I tried to restore the backup i already had, the same that i used to restore when i had problem with the rom but it didn't worked. Now for some reason it doesn't even reach the alcatel boot screen, it just shows the android icon and then stucks with a black sccreen and the buttonsenlightened
what do i have to do to get it work again?
Can anyone please help me
Before my phone got bootlooped, I used to change the build.prop in
root/system/build.prop to add a navigation bar to my Samsung Galaxy S DUOS GT-S7562.
I added qemu.hw.mainkeys=0 at the end of the texts.
And do a reboot and now my device is bootlooping
I only had a stock recovery, and do the factory reset but still no luck.
It only boots to the Samsung boot animation.
I tried to enter the Download Mode to use Odin but it surprised me that
I can't even go to USB state so it's impossible for me to do it also.
And lastly, I don't have a backup also.
But I found a firmware exactly for my device.
Can anyone please help me
ICS
Found this old thread while looking for the same symptoms. I added just this line to my Android box (KM8P) and the next time it rebooted it was forever stuck at the MBOX logo. Cache clear and factory reset did not fix it. I had to flash the stock ROM back on, then TWRP and magisk and set everything back up again.
The soft keys appeared after the build.prop mod so it seemed to be working.
So I have a droid razr that has (Safestrap 3.73 with TWRP 2.7.0.0)
I flashed a custom rom onto it; a 4.4.4 version and it was working fine for a few days. The phone died overnight, and I charged it to full battery yesterday. After doing so it will no longer boot to the operating system.
The phone can boot to recovery, and the options can be fiddled with there, however I cannot get the phone to get past the blue logo with the spinning arrows. It will stay there indefinitely...
I do not have an external SD card for the phone, and my pc will not recognize the phone in spite of having the drivers for the phone installed before hand. I have tried to wipe/factory reset multiple times and yet it will always get stuck at the blue logo. The option for the stock rom is greyed out in the boot section, and I really need my phone to get some functionality back to it.
I do not have any other image for recovery installed on the phone, only the current rom and gapps are on the install section. I have wiped and tried to reflash but I always get the same result.
Where do I proceed from here? I am very confused and could use some help as to what to do to restore functionality... personally id prefer to go back to stock image but am having a hard time locating the us verizon factory image online, not that I can even get it onto the phone.
Hi, I hope you can help me as I am clueless about my phone...
I had the stock 4.1.2 firmware on my phone and wanted to update to Slimkat 4.2, so I first flashed the Siyah-s2-v6.0b5 kernel, check if the device is rooted and booted into recovery.
In recovery I did the factory reset, wiped the cache and formated the system partition.
Then the mistake happened and instead of flashing the Slimrom firmware I kept my finger to long on the swipe enabled recovery and selected "Reboot now" by mistake...
Basically since then my phone can only enter the Download mode (at least). I cannot enter recovery and I cannot boot it.
I flashed the Stock 4.1.2 firmware again but the problem remains. Directly after flashing the firmware when the phone gets rebooted I can see the white Samsung logo (where the yellow triangle would appear with a rooted kernel), then instead of showing to boot animation it switches to the charging screen but it does not charge (battery is and keeps grey).
I also put in another battery just for the case but that didn't change anything of course...
I hope you can help me, else I have the first brick for my wall of shame...
P.S. The stock firmware I use is "I9100XWLSD_I9100DBTLS7_DBT" from sammobile.
Can you still boot to download mode? If not, then look for a USB JIG.
Ok so, a bit of background, I'm on a Vodafone speed tab 6 (vf-1397) running on a root using kingoroot converted to super sume using the app, everything was running fine as such I decided to start looking for apps to use when rooted and ended up coming across jrummyapps boot animations As such I thought, "oh that looks cool let's get that" being naïve and not having any recovery boot loaders installed because I only found out about them after I got into a boot loop. So I proceeded to test a few and they all worked till I got to the third, it proceeded to lock it into a boot loop and now I have no clue what to do, is there anything that I can do, I've tried everything in the recovery menu and nothing. Any help would be highly appreciated I did do a factory reset so it's not currently rooted it's just stock with a custom boot animation that I can't seem to get rid of. Thank you. If all else fails I'll take it to a local Vodafone store when I get back from my holiday.
Another thing I should add currently from my device I can
-reboot system now
-wipe data/factory reset
-wipe cache partition
-power down
-enable adb
Update on current status.
I've found a stock rom for the device and now have the files however, i didn't have usb debugger turned on before it got stuck in a boot loop so, are there any alternative ways of saving it or have i completely messed up?
I know its grave digging at this point but ........
load in recovery and select start adb
then select restart
the device will now load with an unsecured adb connection active