Moto E4 bootloop, unable to enter fastboot mode - Moto E4 Questions & Answers

Hi, I have moto E4 XT1760, I tried to install custom rom on the phone but even after successful installation it didn't boot. After trying to reinstall it got stuck in a bootloop and now I am not even able to enter fastboot mode even after holding for 2 minutes. Help me and thanks !!

southwriter said:
Hi, I have moto E4 XT1760, I tried to install custom rom on the phone but even after successful installation it didn't boot. After trying to reinstall it got stuck in a bootloop and now I am not even able to enter fastboot mode even after holding for 2 minutes. Help me and thanks !!
Click to expand...
Click to collapse
A custom rom can't really do that to your phone. Maybe trying to flash the wrong firmware with fastboot can. And if you did that, there is no fix.

southwriter said:
Hi, I have moto E4 XT1760, I tried to install custom rom on the phone but even after successful installation it didn't boot. After trying to reinstall it got stuck in a bootloop and now I am not even able to enter fastboot mode even after holding for 2 minutes. Help me and thanks !!
Click to expand...
Click to collapse
Try connecting to wall charger
Sent from my PH-1 using Tapatalk

sd_shadow said:
Try connecting to wall charger
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
It continues looping. I think I installed wrong recovery. Is there any solution ?

southwriter said:
It continues looping. I think I installed wrong recovery. Is there any solution ?
Click to expand...
Click to collapse
What were the filename s and commands you used?
Sent from my PH-1 using Tapatalk

sd_shadow said:
What were the filename s and commands you used?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
it was TWRP recovery for perry. Whenever it has charge it starts looping so, is there an way to get into fastboot mode?

southwriter said:
it was TWRP recovery for perry. Whenever it has charge it starts looping so, is there an way to get into fastboot mode?
Click to expand...
Click to collapse
What command did you use?
Sent from my sailfish using XDA Labs

sd_shadow said:
What command did you use?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
fastboot flash recovery <recovery image>

southwriter said:
fastboot flash recovery <recovery image>
Click to expand...
Click to collapse
That should not have caused your issue.
---------- Post added at 09:34 PM ---------- Previous post was at 09:31 PM ----------
it started to bootloop right after that command?

southwriter said:
fastboot flash recovery <recovery image>
Click to expand...
Click to collapse
Did you finish all the other root steps? If you flashed twrp, what else did you do?
you should still have fastboot
So it seems you took some other steps as well. Flashing twrp wouldn't do that. Were you able to boot to twrp after flashing it?

madbat99 said:
Did you finish all the other root steps? If you flashed twrp, what else did you do?
you should still have fastboot
So it seems you took some other steps as well. Flashing twrp wouldn't do that. We're you able to boot to twrp after flashing it?
Click to expand...
Click to collapse
1. I flshed the lineage os 14 rom, for that I cleared dalvik cache, system, data, cache partitions but the os didn't start so I repeated the steps again
2. The data partition was not able to format so I changed the format to ext2
3. I also used ''fastboot flash boot <boot.img from lineage os rom>"

southwriter said:
2. The data partition was not able to format so I changed the format to ext2
3. I also used ''fastboot flash boot <boot.img from lineage os rom>"
Click to expand...
Click to collapse
Where were these steps advised? Ext4 is the normal internal format if not using f2fs but that in itself probably wouldn't have caused your current woes. Step #3 seems the likely culprit...either image not compatible or a flash gone bad.

southwriter said:
1. I flshed the lineage os 14 rom, for that I cleared dalvik cache, system, data, cache partitions but the os didn't start so I repeated the steps again
2. The data partition was not able to format so I changed the format to ext2
3. I also used ''fastboot flash boot <boot.img from lineage os rom>"
Click to expand...
Click to collapse
If it let you choose to format to ext2, you probably could have formatted to ext4.
But that aside, can you still boot to twrp?
Maybe pull the battery.

madbat99 said:
If it let you choose to format to ext2, you probably could have formatted to ext4.
But that aside, can you still boot to twrp?
Maybe pull the battery.
Click to expand...
Click to collapse
No, the phone powers off after pulling the battery out but when I press power off and volume down simultaneously it start looping. I also tried pressing power off and volume down for 2 minutes but it didn't work.

Hello
Have you find solution, I have the same problem with my E4 XT1762
bootloop with twrp and fastboot impossible.
After flashing by mistake twrp-perry-3.2.3-r1.img
Thank you

Darkmo said:
Hello
Have you find solution, I have the same problem with my E4 XT1762
bootloop with twrp and fastboot impossible.
After flashing by mistake twrp-perry-3.2.3-r1.img
Thank you
Click to expand...
Click to collapse
XT1762 is mediatek right and you flashed a Qualcomm twrp I assume? I would say try to find an sdcard unbrick method for a similar mediatek device if one exists like there is for some Qualcomm devices. I don't know much about mediatek devices but if you can get at least the bootloader written to an sdcard so it will boot to it when started, then pull the sdcard and flash twrp again (make sure it's the correct twrp). You just have to make sure you pull the sdcard or it will flash twrp to the card, not the phone. Probably your best bet. I've unbricked Qualcomm devices this way that were completely dead and wouldn't do anything.
Edit: you'll want to make sure the bootloader you write to an sdcard is the same or newer version as what you have now or it may not boot it.

Thank you, I was finally able to recover everything except my numbers imei which are virgin and my serial number which is zany to him. Would you have a solution? Thank you.

Darkmo said:
Thank you, I was finally able to recover everything except my numbers imei which are virgin and my serial number which is zany to him. Would you have a solution? Thank you.
Click to expand...
Click to collapse
Hey Darkmo, how exactly You did it?

Related

Installing TWRP after May update

Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
Code:
adb reboot-bootloader
fastboot flash recovery .\recovery\twrp-3.0.2-0-clark.img
fastboot reboot
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
user7743 said:
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
You have to immediately boot into TWRP after flashing or the system will overwrite it with the stock recovery.
Sent from my XT1575 using XDA Labs
Thanks for that. Exactly the hint I needed.
Question
Would you mind telling me what steps you took to get the May update? It's so small that I'm reluctant to do anything major to get it and I'm debating on whether to just flash the stock recovery to give that a try, or whether I'm going to have to flash the unrooted image I've saved using TWRP, then flash stock recovery, then get the OTA. Seems like a lot of work for a tiny update.
user7743 said:
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
Code:
adb reboot-bootloader
fastboot flash recovery .\recovery\twrp-3.0.2-0-clark.img
fastboot reboot
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
Marnina said:
Would you mind telling me what steps you took to get the May update? It's so small that I'm reluctant to do anything major to get it and I'm debating on whether to just flash the stock recovery to give that a try, or whether I'm going to have to flash the unrooted image I've saved using TWRP, then flash stock recovery, then get the OTA. Seems like a lot of work for a tiny update.
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
If you have modified the system in any form, such as using Xposed, then OTA will fail. If the system image is stock that has never been rooted, in theory you should have no issues with stock recovery installed. The OTA is the May security update. Whether you feel it is necessary or not is up to you.
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Sent from my XT1575 using XDA-Developers mobile app
Sherrillface said:
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Don't run the last command:
fastboot reboot
Select to reboot into recovery from the menu. If you're getting No command, you may need to flash the stock recovery then reboot the recovery. You should have the menu back. Flash TWRP and reboot into recovery to start TWRP.
HTH
Ooms
Sherrillface said:
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Click to expand...
Click to collapse
1. Periods, dude. Where are they?
2. Flash TWRP again.
3. In TWRP, mount /system (Advanced > Mount > system), and delete:
/system/etc/install-recovery.cfg
/system/etc/recovery-resource.dat
/system/recovery-from-boot.p
Click to expand...
Click to collapse
or add the .bak extension to the filenames.
/system/etc/install-recovery.cfg.bak
/system/etc/recovery-resource.dat.bak
/system/recovery-from-boot.p.bak
Click to expand...
Click to collapse
4. Reboot straight back into TWRP (Reboot > Recovery) to make sure TWRP sticks.
Can't get into twrp at all tried fastboot reboot and tried recovery mode directly after flash that's the whole issue just says no command upon trying to enter twrp directly after twrp.img flash.
Sent from my XT1575 using XDA-Developers mobile app
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
Says flash successful but I don't think it truly is
Sent from my XT1575 using XDA-Developers mobile app
Sherrillface said:
Can't get into twrp at all tried fastboot reboot and tried recovery mode directly after flash that's the whole issue just says no command upon trying to enter twrp directly after twrp.img flash.
Sent from my XT1575 using XDA-Developers mobile app
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
Says flash successful but I don't think it truly is
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Sounds like it's not flashing... what is your bootloader state? Try to start it with fastboot boot recovery.img command.
acejavelin said:
Sounds like it's not flashing... what is your bootloader state? Try to start it with fastboot boot recovery.img command.
Click to expand...
Click to collapse
Got it a while ago wrong windroid version.
Sherrillface said:
Got it a while ago wrong windroid version.
Click to expand...
Click to collapse
Umm... OK... No offense to @Rapscallion16 but why are you using a generic toolkit on the Moto X??? It has been mentioned many times that using one click tools and other toolkits is not safe with this and most newer Moto devices, doing it manually is pretty simple.
Anyway, glad you got it working. Enjoy...

please helpe me

i try instaling cortex 7.00( 7.1.2) after al is ok after the phone reboot evry time when i using i try wipe data with twrp
after reboot the phon don t rebot just bootloop i try unstaling stock image with toolkit evry think is ok but the same brob just bootloop i can enter in fastboot mode but not in stock recovery
samone know the solution ?or my fhone is dead
leroilion02 said:
i try instaling cortex 7.00( 7.1.2) after al is ok after the phone reboot evry time when i using i try wipe data with twrp
after reboot the phon don t rebot just bootloop i try unstaling stock image with toolkit evry think is ok but the same brob just bootloop i can enter in fastboot mode but not in stock recovery
samone know the solution ?or my fhone is dead
Click to expand...
Click to collapse
Since your phone is unlocked, I would try to flash a full Google image using the included flash-all.bat (instructions are on the same page as the image downloads). Not being able to access recovery mode may indicate a more serious problem.
v12xke said:
Since your phone is unlocked, I would try to flash a full Google image using the included flash-all.bat (instructions are on the same page as the image downloads). Not being able to access recovery mode may indicate a more serious problem.
Click to expand...
Click to collapse
do you think my phone still alive
leroilion02 said:
do you think my phone still alive
Click to expand...
Click to collapse
Too early to tell. Google intended the image files to be a foolproof way to "reset" the phone to factory stock. This is the first thing you have to try. Set up ADB/Fastboot on your PC and use it to communicate with, and send commands to your phone.
I've gotten myself into the same situation a few times and flashing the full stock image with flash-all.bat command has always gotten me out of it so far. After I'm back on stock I just start from scratch again and flash recovery, custom rom and root.
jhs39 said:
I've gotten myself into the same situation a few times and flashing the full stock image with flash-all.bat command has always gotten me out of it so far. After I'm back on stock I just start from scratch again and flash recovery, custom rom and root.
Click to expand...
Click to collapse
i flash the full factory image with fastboot all is ok after fishing just bootloop i don t know what is the probleme
leroilion02 said:
i flash the full factory image with fastboot all is ok after fishing just bootloop i don t know what is the probleme
Click to expand...
Click to collapse
fastboot FORMAT (not erase or wipe) userdata, cache and system capturing the screen (or text from each command). Try flash-all.bat again. Which image are you flashing?
v12xke said:
fastboot FORMAT (not erase or wipe) userdata, cache and system capturing the screen (or text from each command). Try flash-all.bat again. Which image are you flashing?
Click to expand...
Click to collapse
the last android 7.1.1
when i flash with flash-all.bat the note progresse he stop with message fichier not fond
leroilion02 said:
the last android 7.1.1
when i flash with flash-all.bat the note progresse he stop with message fichier not fond
Click to expand...
Click to collapse
do you think my phone can reboot
leroilion02 said:
do you think my phone can reboot
Click to expand...
Click to collapse
Can you enter recovery mode after all you have tried? Or do you only have access to fastboot in broader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Can you enter recovery mode after all you have tried? Or do you only have access to fastboot in broader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
just fastboot
leroilion02 said:
do you think my phone can reboot
Click to expand...
Click to collapse
I don't know, you're providing conflicting information. What happened when you fastboot formatted each of the 3 partitions?
v12xke said:
I don't know, you're providing conflicting information. What happened when you fastboot formatted each of the 3 partitions?
Click to expand...
Click to collapse
when i flash the phon on fastboot al is ok the bootloader after the radio after the system after vendor all ok the phon just bootloop
when i try flash with flash-all.bat the procedur don t progress just the radio and bootlaoder after just error message files don t exist
leroilion02 said:
when i flash the phon on fastboot al is ok the bootloader after the radio after the system after vendor all ok the phon just bootloop
when i try flash with flash-all.bat the procedur don t progress just the radio and bootlaoder after just error message files don t exist
Click to expand...
Click to collapse
No. Fastboot FORMAT the 3 partitions (for the 3rd time). Capture the response from each of these commands:
fastboot format userdata
fastboot format cache
fastboot format system
v12xke said:
No. Fastboot FORMAT the 3 partitions (for the 3rd time). Capture the response from each of these commands:
fastboot format userdata
fastboot format cache
fastboot format system
Click to expand...
Click to collapse
ok i try tomorow and i tell you the Result

bootloop after unlocking bootloader and flashing TWRP

Hello,
I have lenovo k4 note 32GB ROM, 2GB RAM with stock 6.0 MM. I've unlocked the bootloader with the command ''fastboot flashing unlock'', confirmed it by pressing volume down and returned to fastboot, then successfully flashed twrp from here https://forum.xda-developers.com/k4-note/development/recovery-twrp-3-0-2-0-touch-recovery-t3530374 , i used the latest version 3.2.1. Now the phone remains in bootloop. After pressing vol- with pwr it enters meta mode for a few seconds but then returns to bootloop again. Attempts to anything lead to bootloop. My computer does not recognise it. Is there anything I can do to revive it? Maybe SP flashtool? I have not tried that yet. Help me please, I would be very thankful for any help.
Thank you
bfbl said:
Hello,
I have lenovo k4 note 32GB ROM, 2GB RAM with stock 6.0 MM. I've unlocked the bootloader with the command ''fastboot flashing unlock'', confirmed it by pressing volume down and returned to fastboot, then successfully flashed twrp from here https://forum.xda-developers.com/k4-note/development/recovery-twrp-3-0-2-0-touch-recovery-t3530374 , i used the latest version 3.2.1. Now the phone remains in bootloop. After pressing vol- with pwr it enters meta mode for a few seconds but then returns to bootloop again. Attempts to anything lead to bootloop. My computer does not recognise it. Is there anything I can do to revive it? Maybe SP flashtool? I have not tried that yet. Help me please, I would be very thankful for any help.
Thank you
Click to expand...
Click to collapse
1. Flash stock version (This will lock you bootloader again).
2. Unlock bootloader and let it reboot (donot flash recovery now)
3. It will wipe the device and boots up.
4. After the boot is successful, go back to fastboot and flash recovery.
senthilvigneshkumar said:
1. Flash stock version (This will lock you bootloader again).
2. Unlock bootloader and let it reboot (donot flash recovery now)
3. It will wipe the device and boots up.
4. After the boot is successful, go back to fastboot and flash recovery.
Click to expand...
Click to collapse
I appreciate your reply, but could you please elaborate on the first step? How am I supposed to flash stock recovery when I cannot enter fastboot? The phone is in bootloop no matter what I try. I can't seem to find a way to communicate with the phone from computer.
bfbl said:
I appreciate your reply, but could you please elaborate on the first step? How am I supposed to flash stock recovery when I cannot enter fastboot? The phone is in bootloop no matter what I try. I can't seem to find a way to communicate with the phone from computer.
Click to expand...
Click to collapse
Flash full stock rom, not just recovery using flashtool. You can't flash recovery alone at this point.
For flashtool, you need to power off the mobile completely.
senthilvigneshkumar said:
Flash full stock rom, not just recovery using flashtool. You can't flash recovery alone at this point.
For flashtool, you need to power off the mobile completely.
Click to expand...
Click to collapse
Thank you soooo much, you helped me a lot. The phone is now running!
Btw, before I restored it, I got into TWRP once, I think i pressed some of the nav buttons to get there. But in mount partitions system was missing and data partition was showing 0B, so something was definitely wrong.
Gonna try flashing it again, this time I'll reboot after unlocking bootloader and only then flash. I hope this time I'll succeed
bfbl said:
Thank you soooo much, you helped me a lot. The phone is now running!
Btw, before I restored it, I got into TWRP once, I think i pressed some of the nav buttons to get there. But in mount partitions system was missing and data partition was showing 0B, so something was definitely wrong.
Gonna try flashing it again, this time I'll reboot after unlocking bootloader and only then flash. I hope this time I'll succeed
Click to expand...
Click to collapse
Good, might be problem with twrp. Flash the correct version of twrp provided for k4 note(2/3gb/
senthilvigneshkumar said:
Good, might be problem with twrp. Flash the correct version of twrp provided for k4 note(2/3gb/
Click to expand...
Click to collapse
It works now, successfully rooted!
I know it's OT, but could you recommend me a reliable custom AOSP ROM? I don't have time to spend trying to find one. You seem to have experience with the phone
thanks!
bfbl said:
It works now, successfully rooted!
I know it's OT, but could you recommend me a reliable custom AOSP ROM? I don't have time to spend trying to find one. You seem to have experience with the phone
thanks!
Click to expand...
Click to collapse
Try resurrection remix. More stable one as far as i know. Follow the install steps exactly as said in OP
Deleted

[SOLVED] Mi A1 restarting each few minutes after flash.

Hey,
After hard bricking my Mi A1 and flashing an official android 8.0 stock rom, it is restarting every few minutes. First goes the unlock boot loader warning screen, then the mi screen and android one screen. It then goes onto the setup menu. I am able to go only to the point to enter my name. Depending on my setup speed, it becomes unresponsive at about that point, just restarts and goes back onto the lock boot loader warning screen. I tried re-locking the boot loader, but it only went to the mi screen, and again the process repeats. Please note that I can't flash a boot.img partition, says partition table doesn't exist.
**********************************************************
SOLUTION:
Place persist.img into the root of phone(not in any folder), flash twrp.img INTO THE BOOT PARTITION, and then reboot to recovery. You will see the TWRP loading screen. Go to Advanced-->Terminal--> and execute the following:
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
And go back to Restart--> Reboot to system.
The persist should b back!
Now use Qualcomm IMEI write tool to restore your IMEI and MAC address!
Try flashing a custom ROM, then reflash Mi A1 stock OS
kvn95ss said:
Try flashing a custom ROM, then reflash Mi A1 stock OS
Click to expand...
Click to collapse
Where should I flash a custom rom from? Don't have TWRP since when I try installing TWRP, it says that recovery partition table doesn't exist.
CoolPlushBear said:
Hey,
After hard bricking my Mi A1 and flashing an official android 8.0 stock rom, it is restarting every few minutes. First goes the unlock boot loader warning screen, then the mi screen and android one screen. It then goes onto the setup menu. I am able to go only to the point to enter my name. Depending on my setup speed, it becomes unresponsive at about that point, just restarts and goes back onto the lock boot loader warning screen. I tried re-locking the boot loader, but it only went to the mi screen, and again the process repeats. Please note that I can't flash a boot.img partition, says partition table doesn't exist. Would be grateful if someone could help me!
Click to expand...
Click to collapse
seems you have corrupted the persist partition
you need to flash it again
go thru this thread maybe it can help you
https://forum.xda-developers.com/mi-a1/help/ruined-modem-partition-please-help-t3733909
Rawwr said:
seems you have corrupted the persist partition
you need to flash it again
go thru this thread maybe it can help you
https://forum.xda-developers.com/mi-a1/help/ruined-modem-partition-please-help-t3733909
Click to expand...
Click to collapse
Tried erasing and re-flashing persist.img , but get FAILED (remote: Error: This image isn't allow download
) Please help!
CoolPlushBear said:
Tried erasing and re-flashing persist.img , but get FAILED (remote: Error: This image isn't allow download
) Please help!
Click to expand...
Click to collapse
Service cente is your only hope now mate
Rawwr said:
Service cente is your only hope now mate
Click to expand...
Click to collapse
There has to be a way to manually make the persist partition writable, since the service center somehow knows how to do that...
CoolPlushBear said:
There has to be a way to manually make the persist partition writable, since the service center somehow knows how to do that...
Click to expand...
Click to collapse
nope there isnt, if you have flashed every rom available using mi flash tool hasnt solved your issue.
only hope you have is clean flash stock ROM with locked bootloader, go to service center and tell them it happened after you updated to the latest security patch.
first they will flash using EDL cable (deep flash) if that doesnt help they will replace the whole motherboard (that's how my issue was solved)
i recommend you to follow this procedure.
Rawwr said:
nope there isnt, if you have flashed every rom available using mi flash tool hasnt solved your issue.
only hope you have is clean flash stock ROM with locked bootloader, go to service center and tell them it happened after you updated to the latest security patch.
first they will flash using EDL cable (deep flash) if that doesnt help they will replace the whole motherboard (that's how my issue was solved)
i recommend you to follow this procedure.
Click to expand...
Click to collapse
Were you charged for it? I don't think they would have replaced it for free.
guy_infinity said:
Were you charged for it? I don't think they would have replaced it for free.
Click to expand...
Click to collapse
Nothing was charged not even a single penny, i just told them it started after i updated to oreo, even they said its happening because of oreo, but you gotta have a locked bootloader.
Rawwr said:
Nothing was charged not even a single penny, i just told them it started after i updated to oreo, even they said its happening because of oreo, but you gotta have a locked bootloader.
Click to expand...
Click to collapse
Oh. That's great!
Pretty sure I'm gonna try this once I corrupt my persist partition too.
guy_infinity said:
Oh. That's great!
Pretty sure I'm gonna try this once I corrupt my persist partition too.
Click to expand...
Click to collapse
Did you guys already try flashing persist thru ADB shell on pc:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
guy_infinity said:
Oh. That's great!
Pretty sure I'm gonna try this once I corrupt my persist partition too.
Click to expand...
Click to collapse
haha great xD
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
CoolPlushBear said:
Did you guys already try flashing persist thru ADB shell on pc:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
Click to expand...
Click to collapse
yeah i did, i said service center guys flashed the whole ROM but that couldnt help it.
Help
Hello friend, did you manage to solve it? At this moment I am in the same problem. I appreciate you if you can help me.

Bricked P10 Lite (Only fastboot works) WAS-LX3

Was trying to flash the SIRIUZ rom to my P10 Lite with TWRP, so i wiped Dalvik, cache, data, internal storage, system. Unsurprinsingly the rom didnt install, but for some dumb decision I rebooted the device, and now it doesnt even show any screen! Cant access twrp, nor fastboot(The phone is recognized when pluged in to Windows and type fastboot devices in cmd).
Tried flashing system.img and boot.img but still, rebooting and nothing shows up.
Has anybody exprienced this? If so, please reply!
I`m not the only one having this problem, thats sad
Try dload method.
TunesPequeno said:
Try dload method.
Click to expand...
Click to collapse
Just tried recently, and it seems it didnt do a thing
Somehow fastboot can flash most of thte things(recovery,boot,system) but when i reboot the phone, nothing happens
Care_99 said:
Just tried recently, and it seems it didnt do a thing
Somehow fastboot can flash most of thte things(recovery,boot,system) but when i reboot the phone, nothing happens
Click to expand...
Click to collapse
Just take a service ROM extract and flash userdata.img ! It has a size of about 724 MB flash it along with some critial partitions like recovery,recovery 2 and others. This should fix it.
Eurofighter_ty said:
Just take a service ROM extract and flash userdata.img ! It has a size of about 724 MB flash it along with some critial partitions like recovery,recovery 2 and others. This should fix it.
Click to expand...
Click to collapse
hello, it doesn't works me, someone have another idea?? I've my phone bricked after flash custom rom oreo based....:crying::crying::crying::crying:
shadowdark93 said:
hello, it doesn't works me, someone have another idea?? I've my phone bricked after flash custom rom oreo based....:crying::crying::crying::crying:
Click to expand...
Click to collapse
Can you boot phone in fastboot mode?
shadowdark93 said:
hello, it doesn't works me, someone have another idea?? I've my phone bricked after flash custom rom oreo based....:crying::crying::crying::crying:
Click to expand...
Click to collapse
If your bootloader is unlcoked try fladhing twrp and booting into there, then download the flashable stock formware and flash it via twrp
If it doesn't work you have to pay 15$ for DC Phoenix or try to get a warranty repair.. but completl brick it first so they can't proove it's your fault
nemanjsb said:
Can you boot phone in fastboot mode?
Click to expand...
Click to collapse
Yes, it only works un fastboot mode but I flahs recovery, system, cust Andrés another partitions Andrés doesnt works
shadowdark93 said:
Yes, it only works un fastboot mode but I flahs recovery, system, cust Andrés another partitions Andrés doesnt works
Click to expand...
Click to collapse
Try with HWota download stock rom from here.
You don't need sd card for installation.
nemanjsb said:
Can you boot phone in fastboot mode?
Click to expand...
Click to collapse
Yes muy phone works un fastboot mode, I flash a custom ROM based for dual SIM but it doesnt work
---------- Post added at 12:05 AM ---------- Previous post was at 12:04 AM ----------
nemanjsb said:
Try with HWota download stock rom from here.
You don't need sd card for installation.
Click to expand...
Click to collapse
Ok thanks I'll do it and tell you :laugh:
davidhozic said:
If your bootloader is unlcoked try fladhing twrp and booting into there, then download the flashable stock formware and flash it via twrp
If it doesn't work you have to pay 15$ for DC Phoenix or try to get a warranty repair.. but completl brick it first so they can't proove it's your fault
Click to expand...
Click to collapse
Hey frend, I only have black screen and fastboot mode, I was flash boot.img but it doesnt run, I can realive my phone?
shadowdark93 said:
Hey frend, I only have black screen and fastboot mode, I was flash boot.img but it doesnt run, I can realive my phone?
Click to expand...
Click to collapse
So your screen is black when your pc detects fastboot?
If that is the case then you won't solve anything by flashing the normal partition, use DC Phoenix.

Categories

Resources