Related
Hey guys i've a problem with my x10
So one night i was playing with it than the other day the phone would start
so i thought yeah right might be the battery or something. i took it to my friends x10 it was with 87% charged so i exclude this
Than i tried to flash with flashtool a new kernel and i get stuck at 9% or 15% depending on the kernel i use.
With SEUS it starts to repair but it says. No new updates avaiable after a few moments.
Some information regarding my phone
Unlocked Bootloader
FXP KERNEL
MM TEAM MIUI V4
The phone vibrate but doesn't start or load the kernel.
What do i do?!
Srry for my bad english
Thx in advance
Usrle flashtool to reflash kernel or firmware.
already did but i get stuck at 9% or 15% flashing the kernel
I'm downloading a full generic rom x10a
having similar problem
Hi, I had similar problem as well
X10i running FXP CM7 suddenly just wont boot n charge after I turn off the phone
it wont boot after flashing anything (firm or kernel) except the official firm
now that I end up with a cap R bootloader but flashtool claim that bootloader is rooted
do I still keep the bootloader unlock?
i guess you have a locked bootloader since the original firmware is loading just fine even tho rooting has nothing to do with the bootloader it self. i'm only guessing.
I'm stuck at. Flashing Loader
I bricked my phone last week and it got stuck in a boot loop.
I downloaded the x10a generic Stock ROM and flashed it via Flashtool and it worked like a charm.
Hope this helps.
[XBOCT]™ said:
I bricked my phone last week and it got stuck in a boot loop.
I downloaded the x10a generic Stock ROM and flashed it via Flashtool and it worked like a charm.
Hope this helps.
Click to expand...
Click to collapse
But that way you weren't at a brick point.
You get brick when u get those 3 blink red LED and the phone doesn't do anything
By the fact that your phone were able to load the kernel. i guess
same problem repeat
Hi, just confirm that the bootloader remain unlock as long as the flashtool claim its ROOTED
had you try other than official 2.3.3 ftf?
because I just got the same unable to boot problem repeated again
this time cant get boot on even stock 2.3.3 firm
but I was able to boot up and charge on 2.1, then get root, recovery and kernel (w/o unlock bootloader again) and go straight to custom ROM with no problem
mooving said:
Hi, just confirm that the bootloader remain unlock as long as the flashtool claim its ROOTED
had you try other than official 2.3.3 ftf?
because I just got the same unable to boot problem repeated again
this time cant get boot on even stock 2.3.3 firm
but I was able to boot up and charge on 2.1, then get root, recovery and kernel (w/o unlock bootloader again) and go straight to custom ROM with no problem
Click to expand...
Click to collapse
i'm using
X10a_2.1update1_r2.1.A.0.435_Generic.ftf
And it get stuck at Flashing loader
Idk but i can "read" the kernel when i dump the propriets but i can't "right" when i try to flash something
Anyone?
guys?
you said your phone is "bricked"
I'm not sure if you know what that means.
If you say you've bricked your phone then no one can help you.
A brick is a brick. It doesn't matter if it weighs a few kgs or a few hundred grams. A brick can't receive phone calls.
And your phone isn't even a normal brick... You wrote that it's "really bricked"
Are you building a house anytime soon?
LJE said:
you said your phone is "bricked"
I'm not sure if you know what that means.
If you say you've bricked your phone then no one can help you.
A brick is a brick. It doesn't matter if it weighs a few kgs or a few hundred grams. A brick can't receive phone calls.
And your phone isn't even a normal brick... You wrote that it's "really bricked"
Are you building a house anytime soon?
Click to expand...
Click to collapse
maybe i'm wrong idk maybe is a soft brick. thats why i'm asking for some help.
almomdegal said:
But that way you weren't at a brick point.
You get brick when u get those 3 blink red LED and the phone doesn't do anything
By the fact that your phone were able to load the kernel. i guess
Click to expand...
Click to collapse
The red led blinking rapidly three times means the battery is "out of juice".
I've said it earlier: Several X10 devices have reached an age, where battery failures are fairly common due to charge cycles and/or age. Specially if one got it just after the launch.
Anyhow, what you can do, is let the device charge "blindly" for a while, and a while I mean for half an hour to a few hours. Then it should, out of the blue, jump into "active" charging (With the battery screen showing offline charging)
If this doesn't happen you might have to charge the battery externally.
...or even replace the battery.
-"Why?", one might ask.
Reason is that the flash mode only works with a charged battery.
If it empty, it won't engage the flash mode at all. Stupid design, yes, but that is how it is.
Worst thing is, that the battery does deplete/discharge while in flashing mode. That is why it's so important it's fully charged and fully working, before one engages in flashing activities.
See this post for more information about this: http://forum.xda-developers.com/showthread.php?t=1642154
Try wotanserver's flashtool...
http://www.wotanserver.com/en/
Good luck
SysGhost said:
The red led blinking rapidly three times means the battery is "out of juice".
I've said it earlier: Several X10 devices have reached an age, where battery failures are fairly common due to charge cycles and/or age. Specially if one got it just after the launch.
Anyhow, what you can do, is let the device charge "blindly" for a while, and a while I mean for half an hour to a few hours. Then it should, out of the blue, jump into "active" charging (With the battery screen showing offline charging)
If this doesn't happen you might have to charge the battery externally.
...or even replace the battery.
-"Why?", one might ask.
Reason is that the flash mode only works with a charged battery.
If it empty, it won't engage the flash mode at all. Stupid design, yes, but that is how it is.
Worst thing is, that the battery does deplete/discharge while in flashing mode. That is why it's so important it's fully charged and fully working, before one engages in flashing activities.
See this post for more information about this: http://forum.xda-developers.com/showthread.php?t=1642154
Click to expand...
Click to collapse
Didn't work, i even use my friends battery to flash it and it didn't work
almomdegal said:
Didn't work, i even use my friends battery to flash it and it didn't work
Click to expand...
Click to collapse
Well, if the battery issue was fixed, and you're sure the battery is fully charged, then try this: (Quoting from my other post)
I've charged/replaced the battery, and are having trouble with starting up. Earlier flash failed. Now what?
Don't worry. It's pretty darn hard to truly brick this device. Even if the screen remains black, there's still hope.
Once that the battery issue has been dealt with, you can move on:
Download the latest Flashtool and the proper global firmware (FTF-file) for your device from here:
http://forum.xda-developers.com/show...ight=flashtool
1: Extract/Install the Flashtool to a folder of your liking.
2: Copy the ftf-file to the "firmware" folder in the Flashtool folder you just created above.
3: Start Flashtool. Click the Bolt icon (flash). A Window appear. There, choose "flashmode". Cllick OK.
4: A new window appears. In the list on the left, choose the Generic firmware you downloaded and copied into the "firmware" folder. Should have a similar name as the file itself. (Or manually open the ftf-file from the "..." icon on the top right.)
5: Hit "OK. Follow the instructions you get on the screen:
1 - Unplug the device.
2 - Power off the device. (Unplug and replug the battery to be sure it really off, and not stuck in black screen)
3 - Press the "back" putton, and hold it down while performing the next task.
4 - Plug the device into the computers USB.
Click to expand...
Click to collapse
Forced flashing should now start.
Click to expand...
Click to collapse
time to accept the fact that it is really brick
Hi @almomdegal,
if you try flash using another full charge batt n its not work, I think this forum is no longer works for u anymore.
I own a faulty X10 as well, random shut down (no warning at all) then wont boot n charge
reflash it, revive for few days and dead again, and reflash....
now it is really dead, no problem appears and it show flash successful and it just wont boot or charge but vibrate non stop
I just send the phone to service center and the board need to be replace
so its time to send to the real professional to solve it, coz this problem ain't software downloaded from internet can solve anymore
mooving said:
Hi @almomdegal,
if you try flash using another full charge batt n its not work, I think this forum is no longer works for u anymore.
I own a faulty X10 as well, random shut down (no warning at all) then wont boot n charge
reflash it, revive for few days and dead again, and reflash....
now it is really dead, no problem appears and it show flash successful and it just wont boot or charge but vibrate non stop
I just send the phone to service center and the board need to be replace
so its time to send to the real professional to solve it, coz this problem ain't software downloaded from internet can solve anymore
Click to expand...
Click to collapse
yeah i guess so.
I just needed this closure i'll send it to service today
Hey guys!
Today I flashed an early build of CM11 on my I9100 (http://forum.xda-developers.com/showthread.php?t=2523604).
Basically everything went fine, just a few smaller bugs.
But then my phone froze for 2 times so I had to hold down the power button until it shut down. At the first freeze it worked and I could restart my phone but at the second freeze I couldn't restart the phone anymore!
No matter what buttons I hold (power, up-power-home, down-power-home) it just stays black, not even the Samsung logo shows up. When I connect it to the charger the battery icon with the small circle inside appears for some seconds, then goes away, then comes back up and so on...
I really have no idea on what to do so I ask you guys if you have any suggestions
SOLVED: battery was broken
That doesn't look good Did it just froze on its own? Did you do something? Focus on getting to the download mode and flashing stock with odin, if you can't get in the download mode read some instructions for recovering a bricked I9100, you can probably find them at the development sections.
Dakura said:
That doesn't look good Did it just froze on its own? Did you do something? Focus on getting to the download mode and flashing stock with odin, if you can't get in the download mode read some instructions for recovering a bricked I9100, you can probably find them at the development sections.
Click to expand...
Click to collapse
I was just setting everything back up, as i wiped the data before flashing. Unfortunately I can't get in any mode But thank you for your answer, I'll search for bricked S2s
No problem, you can also put the battery out and wait for some time, sometimes it magically works
Dakura said:
No problem, you can also put the battery out and wait for some time, sometimes it magically works
Click to expand...
Click to collapse
Already tried that :/ No luck
But I don't think it's related to CM11 directly as it doesn't even get close to booting it.
Yep, you probably got a faulty bootloader or something, this is definitely above the ROM, but i think flashing with odin will solve it, so just try to get in download mode right now.
Just solved my problem
Seems like my battery was broken or something (I had the 2002mAh extended battery inside). I put back the original battery and the phone booted normally!
So my phone started restarting randomly. It will only show the Samsung logo turn off and do the same thing again. Its not rooted and I am pretty sure that its not from something I installed recently (Everything was from the play store and no immediate problems after any of them). When I did the hold volume up,down and power it would only keep on restarting still. But when I just hold volume down it comes to something else that asks if I want to install a new rom. So I was wondering what I should do. Install a new ROM and then revert back ? or will that not work? Also I have a extra I717 with a broken screen I could swap the insides and see if that would help. Also I don't know much about rooting and stuffs. Lemme know what I should do guys! :highfive:
Klmnnoooooo said:
So my phone started restarting randomly. It will only show the Samsung logo turn off and do the same thing again. Its not rooted and I am pretty sure that its not from something I installed recently (Everything was from the play store and no immediate problems after any of them). When I did the hold volume up,down and power it would only keep on restarting still. But when I just hold volume down it comes to something else that asks if I want to install a new rom. So I was wondering what I should do. Install a new ROM and then revert back ? or will that not work? Also I have a extra I717 with a broken screen I could swap the insides and see if that would help. Also I don't know much about rooting and stuffs. Lemme know what I should do guys! :highfive:
Click to expand...
Click to collapse
Could be stuck power button. I know, I know, " but its clicking just fine". That doesnt mean anything. Flick the back of your phone a few times.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Thats not it
Yeah I read that It might be the problem but Its still happening with the case removed.
Klmnnoooooo said:
Yeah I read that It might be the problem but Its still happening with the case removed.
Click to expand...
Click to collapse
Take out the battery. Insert the battery without touching anything else. Does it just power on itself or does it stay off? If it does turn on, you might have a stuck power button. Let us know what happens
did that too :/
I did that too. It would turn off and on again but only show the Samsung logo then restart again. Also I have the case removed so It cant be the power button being stuck and I have tried the battery thing still nothing.
Whatcha mean? It would turn on by itself once the battery is inserted or you would have to press the power button. Once the battery is out and then inserted back in, it is not supposed to be powered on by itstelf. If it does turn on by itself, then the power button is most likely pressed in.
Yayodroid said:
Whatcha mean? It would turn on by itself once the battery is inserted or you would have to press the power button. Once the battery is out and then inserted back in, it is not supposed to be powered on by itstelf. If it does turn on by itself, then the power button is most likely pressed in.
Click to expand...
Click to collapse
I have a I717 doing the same thing. (Eg. device boots and seems to function for a about 2 minutes locks up and reboots. )
As the device was stock when it started having this issue I figured it might be an OS issue Factory reset to it would leave the device booting to optimize applications then reboot. Checked power button checked it was clean.
Also staied on when in recovery without issue.
As I figured this was an OS issue I installed CWM
Downloaded and installed SlimBeam
Device booted and completed instlation and operated for about 2 minutes and rebooted.
Device will does not have any issues with in CWM or Odin. I
I read alsowhere that the internal SD-Card filesystem might have become corrupted and need to be reformated however I have yet to find instruction or confirmantion.
Anyone have some ideas?
.
to Tal Star.
1. When you were in CWM and were about to flash, did you wipe data/factory reset, wipe cache and dalvik cache then do the flash? Or just flash?
2. So either os it would do the same? Stay on for about two minutes, then reboot? Would it reboot back into the os and do the same?
Yayodroid said:
to Tal Star.
1. When you were in CWM and were about to flash, did you wipe data/factory reset, wipe cache and dalvik cache then do the flash? Or just flash?
2. So either os it would do the same? Stay on for about two minutes, then reboot? Would it reboot back into the os and do the same?
Click to expand...
Click to collapse
Full Wipes every time tried a few diffirent roms no diffirnace.Stock, SlimBean & a couple CM ports.
Tal_Star said:
Full Wipes every time tried a few diffirent roms no diffirnace.Stock, SlimBean & a couple CM ports.
Click to expand...
Click to collapse
So right now you can boot up into the os and it will turn off in 2 minutes? or just given enough time? Will it boot into the os each time? I dont think ill have an answer for it, but i bet someone that does will want to know the same things to possibly narrow it down
Yayodroid said:
So right now you can boot up into the os and it will turn off in 2 minutes? or just given enough time? Will it boot into the os each time? I dont think ill have an answer for it, but i bet someone that does will want to know the same things to possibly narrow it down
Click to expand...
Click to collapse
Naw it starts optimzing the Applications and lasts a few minutes reboots locks up and starts again. SlimBean completes the process and makes it all the way to the launcher but after a same amount of time it reboots. back to the launcher. (Slim bean has a resonable number less Apps and that's why it completes or is my best guess)
Tal_Star said:
Naw it starts optimzing the Applications and lasts a few minutes reboots locks up and starts again. SlimBean completes the process and makes it all the way to the launcher but after a same amount of time it reboots. back to the launcher. (Slim bean has a resonable number less Apps and that's why it completes or is my best guess)
Click to expand...
Click to collapse
I really wouldnt know about that. Hopefully someone will come by and help you out. I wonder being on the latest recovery would help if youre not already and then doing it all over? Hopefully someone more experienced will chime in.
Could be a corrupt download.
Again, I always flash rom 2 times. You can get different reactions from 2 seperate flashes. 2 time seems to get a more solid installation.
Wait your 10 and reboot.
Still think its a power button issue. It can act normal but still be the problem. Hows you battery?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
HAAAAA I hope some one finds this trouble... having the same issue Here... Does your phone starts up correctly when sim card removed? Mine does when sim card removed and pluged into coputer or wall plug.... Did the same steps you did with no effect either... could it be a power management problem ??? :silly: This is getting me nuts...
captemo said:
Could be a corrupt download.
Again, I always flash rom 2 times. You can get different reactions from 2 seperate flashes. 2 time seems to get a more solid installation.
Wait your 10 and reboot.
Still think its a power button issue. It can act normal but still be the problem. Hows you battery?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
I dobut it's a download. I use CWM to flash from an external SD card. However I did try reflashing like you suggest with no change. The battery is fine as far as I can tell, like I said it will stay online in recovery on battery for what seems like forever.
daversv09 said:
HAAAAA I hope some one finds this trouble... having the same issue Here... Does your phone starts up correctly when sim card removed? Mine does when sim card removed and pluged into coputer or wall plug.... Did the same steps you did with no effect either... could it be a power management problem ??? :silly: This is getting me nuts...
Click to expand...
Click to collapse
Nope I am working on the one I have with the SIM Card out & SD card out.
happens
So what I done so far is taken out the sim and sd card. Took out the battery put it back in and when I power to turn it on It vibrates (like it normaly would when it starts) then shows Samsung logo turns off and loops. I tried doing the hold volume up down power thing and it does not work. But what does work is when I hold volume down it takes me to a custom OS thing. I don't know what that is but I cant get there. So maybe put a custom OS in and then revert it back?
So I used Odin and put 4.1.2 Jelly Bean Official Firmware but its still doing what it was doing before.Used 3.07 and it said it passed fine. Should I try a different rom or something else? Also the first time it starts up after installing the rom it goes past the logo to the ATT ball animation logo freeze there and turns of then when I turn it on from there it will loop at the samsung logo again.
You can try the firmware upgrade and initialization feature in kies. It will return your device to the original factory firmware, software, and settings. If it still loops after that you have hardware issues.
Ok so I guess im making progress now. After I put the stock rom (Different one from befor) It DIDNT BOOT LOOP well it did but only looped 3 times then stoped. Also there are 2 Samsung logos. the frist one was just normal logo ( same one I was having befor ) then the screen turns off and shows the same logo but this time its a little bigger its white with a blue glow! ( Made it further this time but still crashes afterwards) BUT now I can actualy get into the Manual mode. I did a wipe data/factory reset in that mode which didnt help i wiped the cache too. Still didnt help.
Now in manual mode my computer does recognize that something is connected to it now but it tries to configure it and keeps on failing. And so samsun kies cant connect to it either.
But from where I started at its a improvement
My Note is doing the same thing too now, but I know the reason why. I was trying to install clockworkmodrecovery so I would be able to upgrade to jellybean and I think I flashed a kernel that was meant for rooted phones (pretty dumb of me I guess). So now the phone is stuck and I'm going to try to install the original jellybean 4.1.2 for rogers and hopefully that will fix it.
As long as you can get into Odin download mode, your phone can be fixed.
So, I already had some issues with this device and they've been pretty similar, in a way that the problem always starts with random reboots when the power button is pressed. About two weeks ago I took it to a technician, because all sorts of connectivity (3G/Wi-fi/Bluetooth) simply stopped working, after yet another reboot. About 3 days ago I got it back and it was working fine except for the fact that the initial boot Motorola logo (The green one before the other logo animations) wasn't showing up. He told me it was fine because it was only an aesthetic problem because he couldn't find that image for my device's resolution.
This morning when i was going to work i picked up my XT1025 Moto E to check for messages and it suddenly restarted. So when I turn it back on, not only the animations did not pop up, but after some time all i get is a black screen, no UI whatsover, all I can do is turn off/restart the phone. At random times when I turn on the screen, it's content shows up but I can't click anything, and then an error message pops up saying that ''system has stopped responding''. I've tried many things to fix it, but nothing has worked so far.
What i've tried:
-Wiping cache partition did not work
-Factory resetting did not work either
-Unlocking bootloader (but apparently it was unlocked already)
-Flashing a custom recovery did not work for some reason...
These last two were on the ''All-In-One Guide'' by neo.ank and honestly I have no idea what i should do to fix this problem - I was thinking about reinstalling the stock ROM but i'd rather ask here first for you guys suggestions... (like i said, complete newb here).
Sorry for the long post and bad english, hopefully someone can help me out on this.
Kaio Oliveira said:
So, I already had some issues with this device and they've been pretty similar, in a way that the problem always starts with random reboots when the power button is pressed. About two weeks ago I took it to a technician, because all sorts of connectivity (3G/Wi-fi/Bluetooth) simply stopped working, after yet another reboot. About 3 days ago I got it back and it was working fine except for the fact that the initial boot Motorola logo (The green one before the other logo animations) wasn't showing up. He told me it was fine because it was only an aesthetic problem because he couldn't find that image for my device's resolution.
This morning when i was going to work i picked up my XT1025 Moto E to check for messages and it suddenly restarted. So when I turn it back on, not only the animations did not pop up, but after some time all i get is a black screen, no UI whatsover, all I can do is turn off/restart the phone. At random times when I turn on the screen, it's content shows up but I can't click anything, and then an error message pops up saying that ''system has stopped responding''. I've tried many things to fix it, but nothing has worked so far.
What i've tried:
-Wiping cache partition did not work
-Factory resetting did not work either
-Unlocking bootloader (but apparently it was unlocked already)
-Flashing a custom recovery did not work for some reason...
These last two were on the ''All-In-One Guide'' by neo.ank and honestly I have no idea what i should do to fix this problem - I was thinking about reinstalling the stock ROM but i'd rather ask here first for you guys suggestions... (like i said, complete newb here).
Sorry for the long post and bad english, hopefully someone can help me out on this.
Click to expand...
Click to collapse
You Should Flash Custom Roms.....
shyvam said:
You Should Flash Custom Roms.....
Click to expand...
Click to collapse
Hey man, thanks for the reply. How would this solve the problem, exactly? (I don't want o sound like a douche , i'd just like an explanation for information purposes - i'd be very thankful for some links ).
Are U on stock rom?
GNVM said:
Are U on stock rom?
Click to expand...
Click to collapse
I think it's currently using lollipop 5.1.
If u want to get back to stock 5.1 then flash stock rom. Then download the firmware from below link .
http://www.androidfilehost.com/?fid=24052804347783250
and download the batch file
https://www.androidfilehost.com/?fid=24269982087018369
1. Boot ur phone in fastboot mode then.
2. Extract the firmware and batch file on same folder and click on the batch file.
3. Click on the Fashtool batch file.
GNVM said:
If u want to get back to stock 5.1 then flash stock rom. Then download the firmware from below link .
http://www.androidfilehost.com/?fid=24052804347783250
and download the batch file
https://www.androidfilehost.com/?fid=24269982087018369
1. Boot ur phone in fastboot mode then.
2. Extract the firmware and batch file on same folder and click on the batch file.
3. Click on the Fashtool batch file.
Click to expand...
Click to collapse
Worked like a charm. Thanks a lot, man. ^_^
Hello, everyone!
As you might guess I don't know if my device is hard bricked.
It began when I rooted my Moto E, installed a ROM and then the battery started to discharge way too fast than normal.
I tried to calibrate the battery but it didn't work, at some point the battery only lasted a couple of hours until one day my device turned off and it didn't turn on again.
When I plug the original charger or any other, only the white led blinks, I have already changed the battery for a new one, but the same thing is happenning, only white led blinks.
It is possible to "suddenly" hard brick a device? Because the only thing I did was to unlock the bootloader and install a ROM (Cardinal AOSP 1st and then cm-13.0-20161108-NIGHTLY-condor)
(Sorry for the mistakes, not native english)
WAIFWAIF said:
Hello, everyone!
As you might guess I don't know if my device is hard bricked.
It began when I rooted my Moto E, installed a ROM and then the battery started to discharge way too fast than normal.
I tried to calibrate the battery but it didn't work, at some point the battery only lasted a couple of hours until one day my device turned off and it didn't turn on again.
When I plug the original charger or any other, only the white led blinks, I have already changed the battery for a new one, but the same thing is happenning, only white led blinks.
It is possible to "suddenly" hard brick a device? Because the only thing I did was to unlock the bootloader and install a ROM (Cardinal AOSP 1st and then cm-13.0-20161108-NIGHTLY-condor)
(Sorry for the mistakes, not native english)
Click to expand...
Click to collapse
Press and hold power button for 30 seconds, then release power button
Then connect your mobile with pc/laptop
Let it be charged for an hour
Then reboot it into fastboot and flash stock lollipop
WAIFWAIF said:
Hello, everyone!
As you might guess I don't know if my device is hard bricked.
It began when I rooted my Moto E, installed a ROM and then the battery started to discharge way too fast than normal.
I tried to calibrate the battery but it didn't work, at some point the battery only lasted a couple of hours until one day my device turned off and it didn't turn on again.
When I plug the original charger or any other, only the white led blinks, I have already changed the battery for a new one, but the same thing is happenning, only white led blinks.
It is possible to "suddenly" hard brick a device? Because the only thing I did was to unlock the bootloader and install a ROM (Cardinal AOSP 1st and then cm-13.0-20161108-NIGHTLY-condor)
(Sorry for the mistakes, not native english)
Click to expand...
Click to collapse
don't worry i'm here to help you, once i was also a noob
firstly i need to know your knowledge level do you know how to reboot you phone into fastboot mode
have you installed any custom recovery to you device if yes it'll be so easy to resolve your problem
so give me those info :good:
mklkumar4 said:
don't worry i'm here to help you, once i was also a noob
firstly i need to know your knowledge level do you know how to reboot you phone into fastboot mode
have you installed any custom recovery to you device if yes it'll be so easy to resolve your problem
so give me those info :good:
Click to expand...
Click to collapse
Hey, thanks for your help.
I know how to enter into fastboot mode and all that stuff... but when I try to turn on my device, nothing happen, and if I connect my Moto E to the PC the device manager detects it as: qhsusb_bulk
It appears that the boatloder corrupted itself for some reason, a lot of people have the same issue.
I think it is hardbricked, but if you have some info that could help me, I'd be grateful
1st try to unlock bootloader if you are not able to do that, try to flash stock firmware this may help you
And please send screenshots of all the stuff that you can access in ur bricked device...! It will be helpful for me to understand