Database Info

stuck on Google logo

After updating around 20 apps (altogether ), I noticed the phone was not functioning normally so I tried to reboot it but now it is stuck on Google logo. I've never unlocked the phone nor used any custom roms. I'm on the latest stock rom 2.3.4
I tried removing the battery and putting it back but didn't work. Vol. up + power and then Recovery didn't work either. It gives me a triangle with ! in it and stops right there.
I also tried the USB Jig that forces the phone into downloading mode but it gave me a screen that asks (Unlock bootloader?) with some warnings but I don't know how to accept that. Niether Vol buttons nor Power button worked there
I didn't want to mess up with the phone until I hear from you guys. Please help

up.......

You might have to actually root it or use the Samsung exe back to factory. That is if you don't want to mess with it because if I ware in your position I'd be going back for a new phone. You did nothing wrong and you have 1 year warranty on it.

FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.

matt2053 said:
FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.
Click to expand...
Click to collapse
Thanks man, I didn't know about that
Is wiping the data (factory reset) going to delete my stuff stored on my SD card? like pic., music, vid. etc?
and do I need to actually wipe the data or will wiping the chache only work?

Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz

frutelaken said:
Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz
Click to expand...
Click to collapse
Thanks a lot. I already tried wiping the Cache but it didn't work. I guess I'm going with the factory reset now
Thanks again

the factory reset didn't work !
still stuck on Google logo
any advice?

farisallil said:
the factory reset didn't work !
still stuck on Google logo
any advice?
Click to expand...
Click to collapse
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?

Try doing a hard reset.

GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help

farisallil said:
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help
Click to expand...
Click to collapse
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App

matt2053 said:
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I would if I was in the States

just unlock it and flash a nice CM7 with Trinity on top
Here's a rooting guide: http://forum.xda-developers.com/showthread.php?t=895545
There's another guide out there for the i9023 (European version).

GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
No. The device doesn't even show up when I type "adp devices"
Is there anything else I should try?

Thanks
I can perform things with Fastboot
I don't want to root or unlock the phone. Is there anything else I can do?
I tried typing Fastboot update update.zip after downloading the stock rom update 2.3.4 and putting it in the SDK tools directory but it gave me the msg "faild to upload update.zip"

Try to reset with Odin.

[Q] RAZR HD bricked?

After my Fido XT925 received OTA update, it installed succesfully. Some days ago phone working slow down, and i did the factory reset from settings. After that it bootloped (M logo the black screen than green android guy). and when i select "normal booting" through the boot selector menu but it stuck on the Fido logo. after many attempts to boot with other options it booted once from the "Factory" option, but it soo slooow working and i've tryed to do factory reset from the recovery. After that it wan't boot anyway with any options, always stucks on the Fido logo or bootloop. Only after that i've try to unlock the bootloader to full flash. On the last step (when i send command with unique key) it said "failed (too many links)", but when phone reboot it show the warning logo about unlocked bootloader, and in AP Fastboot Mode string with device status is "device is UNLOCKED status code 3".
1) Now it can't be flashed through RSD Lite (it looks like flashing, RSD and fastboot.exe show all steps, no error but on the phone nothing changes)
2) It boot but stuck on the FIdo logo
3) I can access to the ADB Interface from the BP Tools (boot option) after manually edit & install usb driver
4) Bootloader Unlocked
4) i've made logcat boot process (in the attachments)
5) No motorola service in Russia (no way to use hardware programmer)
6) Battery no problem - i charge it using BP Tools
Now there is the question - is there any way to get it work?

mine had strange behaviour 'out-of-the-box' like reboots, bootloops, unwanted factory resets, until from recovery menu I wiped every partition twice.
give it a try :good:

bgumble said:
mine had strange behaviour 'out-of-the-box' like reboots, bootloops, unwanted factory resets, until from recovery menu I wiped every partition twice.
give it a try :good:
Click to expand...
Click to collapse
thanks, but it no success. (still stuck on the Fido Logo)
from adb shell, looks like there is no access to /data, /cache, /tmp partitions (also in log similar errors). when i try any commands said there is no permissions. For /sdcard also no access but there is another failure - i/o error.
Also, from adb shell i've found binary "restore_userdata" in /system/bin when i've tried to did it it cannot be done, cause no permissions.
I can't install any apk's through the adb cause data partition non accessable and i don't have root for install it in the system partition =( If i had that i can install custom recovery (Safestrap maybe) and then flash custom...

maks.xt925 said:
thanks, but it no success. (still stuck on the Fido Logo)
from adb shell, looks like there is no access to /data, /cache, /tmp partitions (also in log similar errors). when i try any commands said there is no permissions. For /sdcard also no access but there is another failure - i/o error.
Also, from adb shell i've found binary "restore_userdata" in /system/bin when i've tried to did it it cannot be done, cause no permissions.
I can't install any apk's through the adb cause data partition non accessable and i don't have root for install it in the system partition =( If i had that i can install custom recovery (Safestrap maybe) and then flash custom...
Click to expand...
Click to collapse
Try to boot in recovery mode and do a factory reset. See what happens then. Booting in factory mode is different than doing a factory reset, maybe your data partition is full
Sent from my XT925 using Tapatalk 2

danifunker said:
Try to boot in recovery mode and do a factory reset. See what happens then. Booting in factory mode is different than doing a factory reset, maybe your data partition is full
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
Already tried, it wrote wiping data, wiping cache, then prepairing for BP masterclear and no one error.

maks.xt925 said:
Already tried, it wrote wiping data, wiping cache, then prepairing for BP masterclear and no one error.
Click to expand...
Click to collapse
Try jelly bean fastboot, let me know.
Sent from my XT925 using Tapatalk 2

danifunker said:
Try jelly bean fastboot, let me know.
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
Tryed to flash new xml 9.8.2Q-8-XT925_VQL-12.2 FULL through the fatsboot.exe (unzip and manually flash step by step) and RSD, nothing changes. Already tried to flash many other xml fw with no success. Also tryed flashing backup Rogers Jelly Bean FullXML-Feb.11-21.06.41

remove sdcard
it looks like a broken hardware.
last idea I have: remove sdcard and start wiping again

bgumble said:
it looks like a broken hardware.
last idea I have: remove sdcard and start wiping again
Click to expand...
Click to collapse
there is no sdcard installed. also nosim card. (but i've already tried with installed)
UPD: Now, dont't worry about buggy-phone, sell it for parts...

Looks like I am having same issue with my Fido Motorola RAZR HD, after receiving JB update, I couldn't do a security wipe within the OS, so power cycled the phone and did factory reset via Android boot screen, but now my phone can't boot into the OS. keeps rebooting over and over again, the green android guy with blue bar beneath it.

All Rogers/Fido have a bug after JB ota update ... if you security wipe by the setting menu or via recovery... you stuck on Motorola Logo ... you can't enter in recovery mode too ... I just imagine all return... There are two ways to recover your phone ... send in repair center ... or flash the JB rom via RSD ...
in the two case ... you loose the root forever ! and you can't get back to ics to root again ;( ( until you unlock the bootloader and void your moto warranty )
This is a basic bug .. why motorola don't update their ota package to fix this bug !

o2qc418 said:
All Rogers/Fido have a bug after JB ota update ... if you security wipe by the setting menu or via recovery... you stuck on Motorola Logo ... you can't enter in recovery mode too ... I just imagine all return... There are two ways to recover your phone ... send in repair center ... or flash the JB rom via RSD ...
in the two case ... you loose the root forever ! and you can't get back to ics to root again ;( ( until you unlock the bootloader and void your moto warranty )
This is a basic bug .. why motorola don't update their ota package to fix this bug !
Click to expand...
Click to collapse
Look, I was just passing by and thought that maybe the firmwares from Brazil could help you. The firmwares from brazilian ICS never gave any problem to the users. Try to download retail brazilian ICS. I have my moto with unlocked bootloader and have flashed the brazilian firmware more than 10 times and never had problems. (After flash, phone will reboot and load itself but you will have bootloop. Then, you reboot cellphone (power + vol - for 10 seconds), enter recovery and wipe everything.)
=)

The problem is when the consumer don't have the bootloader unlocked ...
and the retail brazil don't have all languages .... i need french ;p !

If your problem sounds anything like this, please let me know..I'll post the solution.
"So you did a factory reset.then phone tried to reset but couldn't and goes into a boot loop. The Motorola symbol comes then the green android guy..then it dies after a few seconds..then the cycle goes on and on " ..
Is this what you're experiencing?? I'm on the Fido RAZR HD too.Let me know
Sent from my XT925 using xda premium

slickfing said:
If your problem sounds anything like this, please let me know..I'll post the solution.
"So you did a factory reset.then phone tried to reset but couldn't and goes into a boot loop. The Motorola symbol comes then the green android guy..then it dies after a few seconds..then the cycle goes on and on " ..
Is this what you're experiencing?? I'm on the Fido RAZR HD too.Let me know
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
I have this exact problem after the Rogers OTA update!
Any solution would be most appreciated.

like i say ... in up : All Rogers/Fido have a bug after JB ota update ... if you security wipe by the setting menu or via recovery... you stuck on Motorola Logo ... you can't enter in recovery mode too ... I just imagine all return... There are two ways to recover your phone ... send in repair center ... or flash the JB rom via RSD ...
in the two case ... you loose the root forever ! and you can't get back to ics to root again ;( ( until you unlock the bootloader and void your moto warranty )
This is a basic bug .. why motorola don't update their ota package to fix this bug !
THE ONLY SOLUTION :
... Download the rogers jelly bean roms and flash with rsd lite ... FLASH ! ( you dont need to unlock the bootloader ) all work great after ! ...

slickfing said:
If your problem sounds anything like this, please let me know..I'll post the solution.
"So you did a factory reset.then phone tried to reset but couldn't and goes into a boot loop. The Motorola symbol comes then the green android guy..then it dies after a few seconds..then the cycle goes on and on " ..
Is this what you're experiencing?? I'm on the Fido RAZR HD too.Let me know
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
This is exactly what happened to mine, I managed to fix mine (not really sure how) via getting into menu and selecting factory reset but I had to do it about 10 times for it to finally get past the bootloop and stick. The first few times I tried I could get past the bootloop and into the OS but when I powered the phone off and then back on it would bootloop again, persistance paid off though.The phone has been faultless since and that was about 2 months ago.
What is the solution you used to fix as I would be grateful for future reference?
Cheers

XRCIST said:
This is exactly what happened to mine, I managed to fix mine (not really sure how) via getting into menu and selecting factory reset but I had to do it about 10 times for it to finally get past the bootloop and stick. The first few times I tried I could get past the bootloop and into the OS but when I powered the phone off and then back on it would bootloop again, persistance paid off though.The phone has been faultless since and that was about 2 months ago.
What is the solution you used to fix as I would be grateful for future reference?
Cheers
Click to expand...
Click to collapse
I'd just like to announce that this fix has worked for me.
Even better, I did not have to do it 10 times like you said. It was fixed after the first try. No problems getting into the OS after power off/boot or after a forced reboot. :highfive:
For others' reference, to get into the menu you have to press the "middle of the volume rocker" (basically to get both buttons pressed, some have tried it by doing vol down first then vol up), which will send it into a data wipe procedure. Once it gets to the recovery menu, go back to factory reset and do the data wipe again. Then, reboot. After X number of tries (for poster above it required 10, for me it required 1) the problem should have gone away.

Thanx for this thread it worked for me as well

[Q] Bricked?

Hi,
Someone gave me a Tf700t. On bootup it says unlocked, shows the Asus screen and then keeps rebooting. If I reboot and hold down the volume down arrow I get the menu with four choice ROC, Android, USB, Wipe.
When I press ROC I get the red triangle.
I've read many threads and I think this indicates its bricked and can't be recovered. I just want to confirm before I sell it for parts.
Thanks in advance for the help.
Mark

mmanis said:
Hi,
Someone gave me a Tf700t. On bootup it says unlocked, shows the Asus screen and then keeps rebooting. If I reboot and hold down the volume down arrow I get the menu with four choice ROC, Android, USB, Wipe.
When I press ROC I get the red triangle.
I've read many threads and I think this indicates its bricked and can't be recovered. I just want to confirm before I sell it for parts.
Thanks in advance for the help.
Mark
Click to expand...
Click to collapse
Actually, since you do have access to the bootloader this may be recoverable.
You have 4 icons in the BL menu, so it's a ICS bootloader. The dead Droid on his back when you select RCK is normal - it's the stock recovery not finding a valid update file.
The easiest way to try to get your tablet back to life would be to download the full Asus firmware from here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad Infinity TF700T&p=28&s=1
Select "Android" as the OS. From the resulting list, choose the firmware for your SKU: US if you are in the USA.
If you are considering running a custom rom do yourself a favor and go for the 10.6.1.14.8 version, NOT the latest firmware 10.6.1.14.10. The .8 version can be rooted, the .10 not.
Download the .zip file, extract it ONCE, getting another zip and rename that file to: EP201_768_SDUPDATE.zip
Copy that file to a FAT32 formatted microSD (that's the factory default) and insert it into the tablet.
Boot into recovery (Power and Volume Down, then Volume Up to select RCK) and hopefully the recovery will recognize the file and start to flash it. Be patient - it'll take a while. Wait for it to reboot.

berndblb said:
Actually, since you do have access to the bootloader this may be recoverable.
You have 4 icons in the BL menu, so it's a ICS bootloader. The dead Droid on his back when you select RCK is normal - it's the stock recovery not finding a valid update file.
The easiest way to try to get your tablet back to life would be to download the full Asus firmware from here:
Select "Android" as the OS. From the resulting list, choose the firmware for your SKU: US if you are in the USA.
If you are considering running a custom rom do yourself a favor and go for the 10.6.1.14.8 version, NOT the latest firmware 10.6.1.14.10. The .8 version can be rooted, the .10 not.
Download the .zip file, extract it ONCE, getting another zip and rename that file to: EP201_768_SDUPDATE.zip
Copy that file to a FAT32 formatted microSD (that's the factory default) and insert it into the tablet.
Boot into recovery (Power and Volume Down, then Volume Up to select RCK) and hopefully the recovery will recognize the file and start to flash it. Be patient - it'll take a while. Wait for it to reboot.
Click to expand...
Click to collapse
Well that partially worked. Thanks so much!!!
It was able to flash the firmware. It rebooted 5 times before the os came up. I then shut it down. When I turned it on it goes to the Asus screen and then keeps on rebooting indefinitely. I then hit the volume up and power button to reset and then it rebooted 5 times before the OS came up. BTW I flash with 10.6.1.14.10.
Any ideas?
Thanks again,
Mark

mmanis said:
Well that partially worked. Thanks so much!!!
It was able to flash the firmware. It rebooted 5 times before the os came up. I then shut it down. When I turned it on it goes to the Asus screen and then keeps on rebooting indefinitely. I then hit the volume up and power button to reset and then it rebooted 5 times before the OS came up. BTW I flash with 10.6.1.14.10.
Any ideas?
Thanks again,
Mark
Click to expand...
Click to collapse
Hmm, still bootlooping.
Next thing I would try is to boot into the bootloader, select 'Wipe Data' with the Volume Down button, hit Volume Up execute.
And actually, before even booting back to system (that would be choosing the Android), I would reflash the firmware - just for good measure after the data wipe.
Can't wait to hear if that solves it!

So I downgraded to .8. Rooted. Was able to install TWRP. Reflashed, wiped and it still reboots multiple time before coming up. I tried to flash CyanogenMod but all I get is the spinning Cyanogen wheel. I was able to restore .8. Its not bricked anymore. Its just weird that it keeps rebooting before coming up. But at least its now consistent and will come up every time whether from power on or reset.
Thanks,
Mark

mmanis said:
So I downgraded to .8. Rooted. Was able to install TWRP. Reflashed, wiped and it still reboots multiple time before coming up. I tried to flash CyanogenMod but all I get is the spinning Cyanogen wheel. I was able to restore .8. Its not bricked anymore. Its just weird that it keeps rebooting before coming up. But at least its now consistent and will come up every time whether from power on or reset.
Thanks,
Mark
Click to expand...
Click to collapse
Great job so far! That you got TWRP installed is very good and gives you many more options. It's version 3.6.1? Have you tried to capture a logcat of the boot process?
The logcat may reveal the cause of this and then you could target the problem easier.
If you can't get a logcat my next step would be to format the data partition. Since you probably do not have that much data on it yet, this is the perfect time for that. Always a good idea when you move to a different rom and major framework change.
Go for a Wipe > Advanced > Format Data. It could be that there's something left behind from a former installation that causes the bootloop.
After the format you have to reflash the rom - or restore your .8 nandroid. Although I would go for CROMi-X 5.0.4. Love that rom. Excellent support too.
sbdags, creator of this rom, also provides a bootloader and several kernels.
I mean, if you flash a new bootloader and kernel, format data, clean install the rom and you still get bootloops, it's got to be hardware related. At least I would be out of ideas at that point.

berndblb said:
Great job so far! That you got TWRP installed is very good and gives you many more options. It's version 3.6.1? Have you tried to capture a logcat of the boot process?
The logcat may reveal the cause of this and then you could target the problem easier.
If you can't get a logcat my next step would be to format the data partition. Since you probably do not have that much data on it yet, this is the perfect time for that. Always a good idea when you move to a different rom and major framework change.
Go for a Wipe > Advanced > Format Data. It could be that there's something left behind from a former installation that causes the bootloop.
After the format you have to reflash the rom - or restore your .8 nandroid. Although I would go for CROMi-X 5.0.4. Love that rom. Excellent support too.
sbdags, creator of this rom, also provides a bootloader and several kernels.
I mean, if you flash a new bootloader and kernel, format data, clean install the rom and you still get bootloops, it's got to be hardware related. At least I would be out of ideas at that point.
Click to expand...
Click to collapse
Hi, how do you capture a logcat. FYI, I flashed with CROMi. It kept hanging on reboot. Finally it booted and worked. I shut it down and now I'm back into the endless looping boot cycle. One thing I didn't mention before when the unit is off the only way it will turn on is if I hold the power button down for 10 seconds.
Thanks,
Mark

mmanis said:
Hi, how do you capture a logcat. FYI, I flashed with CROMi. It kept hanging on reboot. Finally it booted and worked. I shut it down and now I'm back into the endless looping boot cycle. One thing I didn't mention before when the unit is off the only way it will turn on is if I hold the power button down for 10 seconds.
Thanks,
Mark
Click to expand...
Click to collapse
Did you format data?
http://forum.xda-developers.com/showthread.php?t=1378491

berndblb said:
Did you format data?
http://forum.xda-developers.com/showthread.php?t=1378491
Click to expand...
Click to collapse
Yes I formatted data. Its very weird it only will boot correctly after I re-flash or about once every 10 times.
Thanks again.
Mark

mmanis said:
Hi, how do you capture a logcat
Click to expand...
Click to collapse
This was at the top of the xda portal http://forum.xda-developers.com/showthread.php?t=2274119
best bookmark it for future reference its a really good tutorial

mmanis said:
Yes I formatted data. Its very weird it only will boot correctly after I re-flash or about once every 10 times.
Thanks again.
Mark
Click to expand...
Click to collapse
At this point only a bootloop logcat can shed light on this. Check the tutorial JTR recommended. It's truly good - thanks for the link!

Hi,
I've attached the logcat. What I did first was do a total wipe, system, data, cache and then reinstalled the rom.
Still having trouble booting once I shutdown and turn it back on.
All the help is greatly appreciated.
Thanks,
Mark

mmanis said:
Hi,
I've attached the logcat. What I did first was do a total wipe, system, data, cache and then reinstalled the rom.
Still having trouble booting once I shutdown and turn it back on.
All the help is greatly appreciated.
Thanks,
Mark
Click to expand...
Click to collapse
Great! Now we need to try to get someone's attention who can actually read and interpret the logcat - that is where my usefulness ends...
@sbdags, @_that, @JoinTheRealms to the rescue???
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

berndblb said:
Great! Now we need to try to get someone's attention who can actually read and interpret the logcat - that is where my usefulness ends...
@sbdags, @_that, @JoinTheRealms to the rescue???
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Right try booting without the microsd card in. Something is wrong with it. Also turn off the Bluetooth, what ever it is trying to connect to is adding lots of entries to the log.

Your device software can't be checked for corruption. Please...

Hi,
I just followed the steps on these two web pages to get my device modded:
https://android.gadgethacks.com/how-to/root-your-google-pixel-pixel-xl-0174670/
https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/
On step 10 of the second link I followed the steps to root my Pixel phone but at the end I saw an option on my TWRP that said you can install TWRP app as a system app to get latest updates. I said okay and done that. Then my device started restarting approximately 2 times followed by this message: "Your device software can't be checked for corruption. Please lock the bootloader. Press power to continue." I can't turn off the phone because it will lock the bootloader.
What should I do to fix this problem?
Here's a Google's response to this issue: https://support.google.com/nexus/answer/6185381?hl=en-GB

Update: I decided to hold power button to turn off the phone. The phone restarted automatically and this time I get "pause boot" then "continue". Then it goes in a boot loop.
Update 2: I managed to get to the bootloader mode via power + vol down.

That screen is standard during boot up when your device is not locked and it is nothing to worry about. If your device is boot looping and you can't get it sorted out you can download stock images from google and run the flash-all command to flash everything again.

ohioa6driver said:
That screen is standard during boot up when your device is not locked and it is nothing to worry about. If your device is boot looping and you can't get it sorted out you can download stock images from google and run the flash-all command to flash everything again.
Click to expand...
Click to collapse
Hi and thanks for the response. You mean something like this or exactly this: https://www.youtube.com/watch?v=5Ewo1ou_53o

Yep just like that video. Be aware that it will wipe all of your user data too unless you remove the -w flag from inside flash-all.bat.

ohioa6driver said:
Yep just like that video. Be aware that it will wipe all of your user data too unless you remove the -w flag from inside flash-all.bat.
Click to expand...
Click to collapse
I just tried that tutorial but it didn't work. :/

Should I follow the steps @death2all110 gave on here: https://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140
Power and Vol Up got me to recover mode and I managed to wipe data and factory reset but my phone is still in a loop + that orange message.

My phone is fixed now. I downloaded 7.1.2 (N2G47O) from the official Google website and followed the steps of @death2all110 . Then I followed the tutorials again and this time I didn't install TWRP as a system app and my phone is successfully rooted.

Xperia L does not turn on.

So i wanted to try out this custom android 5.1.1 i folowed every step but i didnt do one *clear the old system cache* i didnt found it in the recovery so i thought deleting delvik cache will be enough,
The only thing the mobile does, when i press power button it vibrates once and still black screen, cannot entry recovery or anything.
I ve read somewhere this is not a bricked phone so it should be fixable but i have no idea how, somebody told me the old system is still in the phone and it causes errors so it does not boot up.

Strataios said:
So i wanted to try out this custom android 5.1.1 i folowed every step but i didnt do one *clear the old system cache* i didnt found it in the recovery so i thought deleting delvik cache will be enough,
The only thing the mobile does, when i press power button it vibrates once and still black screen, cannot entry recovery or anything.
I ve read somewhere this is not a bricked phone so it should be fixable but i have no idea how, somebody told me the old system is still in the phone and it causes errors so it does not boot up.
Click to expand...
Click to collapse
Try going into fastboot mode.
Then flash a custom recovery and this time clear everything

Nikhil kuttu said:
Try going into fastboot mode.
Then flash a custom recovery and this time clear everything
Click to expand...
Click to collapse
Was wondering about the same but it wont let me to get in haha,