Hi guys,
I'm with my OP 5 black screen and blue led (can't boot) since 5 days and I tried everything I saw on the forum, I tried to flash the recovery, to flash the Oxygen OS, to use MSMDownloadTool but nothing helped.
I'm now with my OP5 soft brick but since I used MSMDownloadTool it locked itself (bootloader) and I can't flash again with fastboot or adb, I tried fastboot oem unlock but I got an error :
Code:
FAILED (remote: Flashing Unlock is not allowed)
If it gets you some info I did :
Code:
./fastboot oem device-info
and got that result :
Code:
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
OKAY [ 0.001s]
Finished. Total time: 0.002s
Could someone help me I'm stuck and sad
Is there any solution to be sure to write again everything on the OP5 ? (it seems that the MSMDownloadTool and fastboot won't erase everything as the OP5 finish properly new installation but bootloop everytime).
Present state of the OP5 : bootloader locked, official recovery working, official rom installed but won't boot.
I'm on mac and windows btw. I followed numerous tutorials like this one :
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Thx in advance.
Have you tried adb sideload the stock rom from recovery? or adb push the zip to internal storage and flash from stock recovery?
tsuttie99 said:
Have you tried adb sideload the stock Rom from recovery? or adb push the zip to internal storage and flash from stock recovery?
Click to expand...
Click to collapse
As i said :
I tried to flash the recovery, to flash the Oxygen OS, to use MSMDownloadTool but nothing helped.
Click to expand...
Click to collapse
I have already done adb sideload etc... the problem is not the way to flash the Rom (as it seems), I can flash a stock Rom but not the others due to the bootloader being locked, the result stays the same after the flash: phone not booting, black screen with blue led.
If you have other ideas ?
Thx for your answer, you're the first answer I finally got on the forum (i tried on other posts about soft brick but no answer).
Shauny ItIsMe said:
As i said :
I have already done adb sideload etc... the problem is not the way to flash the Rom (as it seems), I can flash a stock Rom but not the others due to the bootloader being locked, the result stays the same after the flash: phone not booting, black screen with blue led.
If you have other ideas ?
Thx for your answer, you're the first answer I finally got on the forum (i tried on other posts about soft brick but no answer).
Click to expand...
Click to collapse
No worries, just trying to help.
I am a bit confused by "I can flash a stock Rom but not the others due to the bootloader being locked"
But my understanding of the bootloader and kernel is if you are locked you must only run full stock. A locked bootloader should still allow you to flash stock roms. theroetically you should be able to boot the stock rom, and get into android, at which point i would immediately unlock the bootloader.
Have you tried a factory reset from recovery? or fastboot?
dunjamon said:
Have you tried a factory reset from recovery? or fastboot?
Click to expand...
Click to collapse
Yes from recovery it doesn't change anything and fastboot also, no success.
tsuttie99 said:
No worries, just trying to help.
I am a bit confused by "I can flash a stock Rom but not the others due to the bootloader being locked"
But my understanding of the bootloader and kernel is if you are locked you must only run full stock. A locked bootloader should still allow you to flash stock roms. theroetically you should be able to boot the stock rom, and get into android, at which point i would immediately unlock the bootloader.
Click to expand...
Click to collapse
I tried to flash multiple roms (stock) and none worked, I always got the red screen and the blue led after the boot.
Are you able to format data in the stock recovery? Sorry I run TWRP so cannot test this. You lose all data including sdcard but might be worth a try to get your phone back. Back in the nexus 6p days this happened a lot, and the community eventually figured out that formatting data would often resolve these bootloops/soft bricks. You'd want to reflash your rom afterwards as well. Goes without saying try at your own risk, can't be responsible for data loss, etc, etc...
tsuttie99 said:
Are you able to format data in the stock recovery? Sorry I run TWRP so cannot test this. You lose all data including sdcard but might be worth a try to get your phone back. Back in the nexus 6p days this happened a lot, and the community eventually figured out that formatting data would often resolve these bootloops/soft bricks. You'd want to reflash your rom afterwards as well. Goes without saying try at your own risk, can't be responsible for data loss, etc, etc...
Click to expand...
Click to collapse
I already tried that, I did every wipe possible (factory reset, wipe cache, wipe data, ...) but nothing changed.
Shauny ItIsMe said:
I already tried that, I did every wipe possible (factory reset, wipe cache, wipe data, ...) but nothing changed.
Click to expand...
Click to collapse
Confirm you did a format though? Wipe and format are completely different things. Just want to make sure we are talking about the same thing. In TWRP when you do a format you have to validate by typing "yes". Wiping is completely different.
tsuttie99 said:
Confirm you did a format though? Wipe and format are completely different things. Just want to make sure we are talking about the same thing. In TWRP when you do a format you have to validate by typing "yes". Wiping is completely different.
Click to expand...
Click to collapse
Yes, I've done a format on TWRP before the bootloader locked itself and also the option to erase everything (from the original recovery).
But I did not use the fastboot command for that, I don't know if it changes anything. Furthermore, now that I have the bootloader lock I can't use these commands.
Up
any error came out when u flashed with unbrick tool or any key didn't go back after u pressed it
billsz said:
any error came out when u flashed with unbrick tool or any key didn't go back after u pressed it
Click to expand...
Click to collapse
Sometimes I get an error but, most of the time it gets through everything and shows the green "success".
Shauny ItIsMe said:
Sometimes I get an error but, most of the time it gets through everything and shows the green "success".
Click to expand...
Click to collapse
when unbrick success,start booting system ,it shows oxygen logo or nothing?
billsz said:
when unbrick success,start booting system ,it shows oxygen logo or nothing?
Click to expand...
Click to collapse
It always goes on, can't boot into the logo and restart. After that, the phone goes black screen and blue led.
Shauny ItIsMe said:
It always goes on, can't boot into the logo and restart. After that, the phone goes black screen and blue led.
Click to expand...
Click to collapse
so u could boot into recovery or fastboot even edl,but normal booting, u got black with blue led.
usually edl will unbrick any situation back to factory status,if not,it should be broken somewhere.
some clue showed, after battery drained,u could try some reset
billsz said:
so u could boot into recovery or fastboot even edl,but normal booting, u got black with blue led.
usually edl will unbrick any situation back to factory status,if not,it should be broken somewhere.
some clue showed, after battery drained,u could try some reset
Click to expand...
Click to collapse
Ok, so if I understand correctly I should try to put my phone on edl and try to push the full rom and try this after draining the battery?
How should I do so ?
(Thank you for helping me )
hey shauny.. I have the same situation with my oneplus 5 .. did you fix it by any chance?
@Shauny ItIsMe
hello
Related
I seem to have got myself into a bit of a pickle here.
I had a rooted N7 on 4.2.2. Tried to unroot (in lieu of going up to 4.3). Disaster struck! It wouldn't boot. It would just get stuck at the bootloader and go "Booting failed" or something similar.
So bother, I could get into the bootloader. So I tried to fastboot flash a stock image using this (http://forum.xda-developers.com/showthread.php?t=1907796) guide.
I got a bit further now, it would get the X loading screen but then no amount of waiting would have it boot.
So I tried factory reset from the recovery menu (the one with the Android and the red triangle).
No good, still did the same thing.
So I tried using Nexus Root Toolkit to flash stock + unroot from a soft-bricked/bootloop state. Nope! No good. Still does the same thing.
I've been through every combination of flashing, clearing, resetting but to no avail!
I've tried flashing CWM and TWRP but when I try to get into recovery mode, I just get the Google logo forever. This is a nightmare!
What's going on Have I managed to brick this thing...
evenstevens said:
I seem to have got myself into a bit of a pickle here.
I had a rooted N7 on 4.2.2. Tried to unroot (in lieu of going up to 4.3). Disaster struck! It wouldn't boot. It would just get stuck at the bootloader and go "Booting failed" or something similar.
So bother, I could get into the bootloader. So I tried to fastboot flash a stock image using this (http://forum.xda-developers.com/showthread.php?t=1907796) guide.
I got a bit further now, it would get the X loading screen but then no amount of waiting would have it boot.
So I tried factory reset from the recovery menu (the one with the Android and the red triangle).
No good, still did the same thing.
So I tried using Nexus Root Toolkit to flash stock + unroot from a soft-bricked/bootloop state. Nope! No good. Still does the same thing.
I've been through every combination of flashing, clearing, resetting but to no avail!
I've tried flashing CWM and TWRP but when I try to get into recovery mode, I just get the Google logo forever. This is a nightmare!
What's going on Have I managed to brick this thing...
Click to expand...
Click to collapse
Hey,
did you try doing all these manually :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot -w update image.zip
PS : Edit these according to images you are trying to flash.
You mentioned you tried the guide but try this once again.
Unlock your bootloader / keep your bootloader unlocked while doing this.
If you want to you can even try running the .bat files and / or .sh files while in the bootloader.
If it still doesnt work , download the latest custom recovery and just try flashing it through
Code:
fastboot flash recovery recovery.img
Please mention the errors you have a bit more in detail during these steps !
Red Devil said:
Hey,
did you try doing all these manually :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot -w update image.zip
PS : Edit these according to images you are trying to flash.
You mentioned you tried the guide but try this once again.
Unlock your bootloader / keep your bootloader unlocked while doing this.
If you want to you can even try running the .bat files and / or .sh files while in the bootloader.
If it still doesnt work , download the latest custom recovery and just try flashing it through
Code:
fastboot flash recovery recovery.img
Please mention the errors you have a bit more in detail during these steps !
Click to expand...
Click to collapse
Okay, I've managed to get TWRP up and running.
Now... how do I get a ROM onto there to try to flash? >_<
PS. I did all those commands manually many many times. It's got to a stage now where the X logo never actually comes up... Just the Google logo and the little padlock
evenstevens said:
Okay, I've managed to get TWRP up and running.
Now... how do I get a ROM onto there to try to flash? >_<
PS. I did all those commands manually many many times. It's got to a stage now where the X logo never actually comes up... Just the Google logo and the little padlock
Click to expand...
Click to collapse
Code:
adb sideload ROM.zip
in advance options > adb sideload
And about the ROM getting stuck at the Nexus boot animation , try getting a logcat.. maybe that will help. !
Red Devil said:
Code:
adb sideload ROM.zip
in advance options > adb sideload
And about the ROM getting stuck at the Nexus boot animation , try getting a logcat.. maybe that will help. !
Click to expand...
Click to collapse
Amazing. I actually managed to flash a copy of Cyanogen on there and it all booted perfectly.
Now I wonder if I can get it back to stock from here easily..
Thanks
evenstevens said:
Amazing. I actually managed to flash a copy of Cyanogen on there and it all booted perfectly.
Now I wonder if I can get it back to stock from here easily..
Thanks
Click to expand...
Click to collapse
You can ... just make sure you have downloaded the right factory images and flash the use the .bat / .sh to flash the images .. keep in mind that you will lose all your data including that on the internal sd. All the best
Red Devil said:
You can ... just make sure you have downloaded the right factory images and flash the use the .bat / .sh to flash the images .. keep in mind that you will lose all your data including that on the internal sd. All the best
Click to expand...
Click to collapse
So I tried to reflash a stock image... same issue again! Just freezing at the Google logo screen :/
Properly stumped as to why it's doing that. Maybe I'm stuck with Cyanogen...
evenstevens said:
So I tried to reflash a stock image... same issue again! Just freezing at the Google logo screen :/
Properly stumped as to why it's doing that. Maybe I'm stuck with Cyanogen...
Click to expand...
Click to collapse
So close...
Downloaded the new SDKs from Google and managed to actually flash and get into a stock version of Android... but it's constantly saying "Google keyboard has stopped working! Launcher has stopped working! etc" and it's practically useless
Gaaaaaaaaah
evenstevens said:
So close...
Downloaded the new SDKs from Google and managed to actually flash and get into a stock version of Android... but it's constantly saying "Google keyboard has stopped working! Launcher has stopped working! etc" and it's practically useless
Gaaaaaaaaah
Click to expand...
Click to collapse
Okay my solution to this:
Just keep flashing it with the flash-all.bat command until it just... worked.
Must've done it about 15 times.
Well that's that ordeal over.
I need some major help
My N7 2012 was stock, never rooted. I had only installed OTA updates. Yesterday, the OTA update for Lollipop appeared, and I installed it.
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
I've also tried getting it into fastboot, and I can issue fastboot commands. However, I've never unlocked the bootloader. And when I try to unlock it now, I get the screen that says "This will void your warranty are you sure?" But when I select Yes, fastboot's console says "Failed", and it remains locked.
If I go into Recovery, it just says "No commmand"
I need some help from the geniuses on this forum. To me it seems like an app running at startup is causing the crash, so if I could just get it to Safe Mode, I could figure it out and uninstall it. Hell, I'd be fine w/ a total wipe at this point. Just something to get it working again!
Thanks in advance!
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Didn't work
bubba949 said:
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Click to expand...
Click to collapse
I tried using the Nexus toolkit, using Flash to Stock/Unroot in Bootloop mode, and it didn't work. A few sections succeeded, but most of the sections said "FAILED". Even after performing this, it still wants to boot to my normal desktop, so I know it's not re-flashing a thing.
I wish I knew more about this. I can get into fastboot by going to Power+VOL- but because it won't stay on the desktop, adb commands are a no-go. Is there something in the Advanced section of the Nexus Toolkit that will let me do a reflash? I'm afraid of just poking and trying things for fear of truly bricking it.
Thanks.
Sorry just re-read your last reply didn't realise you can't do adb commands, if you get to a point when you can then below may help...
I had a similiar issue caused differently what i did was to go to this link
http://forum.xda-developers.com/showthread.php?t=1907796
Downloaded the bootloader from JWR66V the guy mentions in his thread he mentions the same issue that i had which is when i tried to flash a stock or custom rom i kept getting messages about invalidstate on bootloader then the system and userdata images would fail when i tried to install...
In the end i downloaded the stock JWR66Y rom, replaced the bootloader image with the one mentioned above, i had to flash the seperate parts of the rom as the Nexus Root Toolkit wouldn't accept the MD5 after i replaced the bootloader so make sure the recovery, the modified bootloader, system and userdata are in your SDK tools folder then i did the following in cmd...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
Fastboot reboot
And voila it booted up and then upgraded its self and is now stock running 5.0 but its working for 2days it wasn't lol
alastria1 said:
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
Click to expand...
Click to collapse
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
bftb0 said:
[size=+1]Safe Mode Boot[/size]
From a cold start boot (press & release Power button), wait 2 seconds after the B&W Google (bootloader) splash screen appears, then press and hold Vol-Down button until the normal OS boot is fully completed (lock screen or home screen appears)
Click to expand...
Click to collapse
Sounds like something is draining the RAM. Try using the stock launcher as default.
Still crashed
dtg7 said:
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
Sounds like something is draining the RAM. Try using the stock launcher as default.
Click to expand...
Click to collapse
I didn't know that. I tried it, and I was able to boot it into safe mode doing this ... and then it crashed in 15 seconds and rebooted...
At this point, I'm considering just emailing Google, since its their update that did this.
They'll probably tell you to wipe cache partition. And by the way,
alastria1 said:
If I go into Recovery, it just says "No commmand"
Click to expand...
Click to collapse
that is a normal operation, it's supposed to say that. What you need to do to get the actual recovery menu is, with screen saying No Command, hold the power button, then click the volume Up button, them let go of power.
This will get you the recovery options, where you should scroll down to wipe Cache partition (last one I think) and select it by hitting power. Reboot into Android and see if that helped.
If not in the same recovery menu there's an option to wipe everything, factory reset. that might cure your device but it will wipe your data.
There is an adb command to pull your sdcard data off your device, but I've never tried it in stock recovery. it might work, but of course it will probably require you had turned On USB debugging.
adb pull /storage/sdcard0/ yourcomputerfolder
yourcomputerfolder being a location on your laptop, like a folder on the desktop.
try this command when in recovery, I don't think it works in bootloader. also, if it works it will only backup your regular files, not your installed apps.
if not then just do the wipe from recovery.
good luck.
Still a no go...
So, I got into the recovery menu, and did a full factory reset. After it rebooted, it went right back to Nova Launcher (with my usual wallpaper on there), and crashed as before. Getting into safe mode confirmed that it no apps were wiped. Factory reset didn't reset a thing.
Its almost like the flash memory is stuck on read-only mode. No matter what I do, nothing changes the contents of memory.
That is weird. And I suppose you can't do what 'wakers' suggested and flash the individual partitions since it probably requires an unlocked bootloader, which you already tried to unlock unsuccessfully. I'd say you were up sh-- creek without a paddle, but... Google searching, maybe there's still a tiny bit of hope:
See this discussion: http://android.stackexchange.com/qu...p-after-lollipop-flash-no-adb-and-no-fastboot
to summarize the suggestions:
- try holding the power button for over ten seconds to kind of reset... something
- try sending the command: fastboot oem lock
yes I know you never unlocked but try it anyway, it might go thru where unlock failed.
speaking of fastboot oem unlock, I know it failed but maybe you can just keep sending the command a few times, one of them might go thru.
I'd add another suggestion: carefully remove the back and carefully unplug the battery and let it sit for a while. then put it back together and try booting up.
may the force be with you.
Finally resolved
Thanks to the posters for the help. I contacted Google customer support and they're overnighting a refurb replacement for free.
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding
Alright so where i'm at now is basically the aftermath of a failed attempt to install a cyanogen unofficial rom for my phone.
I have a p9 lite VNS-L23 dual sim and well basically, i unlocked the bootloader and i rooted it with twrp and installed superuser using the srk tool. Everything worked fine up to this point until i booted into recovery, cleared cache and data etc to do a clean install and the install failed with an error code 7.
I thought doing a twrp backup before the flash was effective but because it didnt take any length of time, i sort of thought it definitely wasnt a full backup but i didnt pay it any attention and tried to flash it anyway since iv'e never had probs flashing anything with other of the phones ive had before which was my main mistake.
Usb debugging was enabled before trying to flash. I thought it failed because i didnt change my file system but i had no idea how to do that so i avoided it and tried to install a newer version of twrp to see if the rom would work with the updated version instead. When flashing the twrp img file, it asked where i wanted to install and i think i selected bootloader instead of boot cause there were only 2 options.
After than finished and i chose to restart in recovery, recovery never loaded. I was getting erecovery but that couldnt help me either. I was just stuck with no os and a phone stuck on the bootscreen. I tried to unbrick my phone by installing the update file for the international version firmware which i downloaded which was the only one not to fail after trying 2 others before it before realizing the error i was making. I read online that it would restore my phone back to ofw and that was great considering i had no os installed. Now, after the update, i think i reached like 100% then it went blank. I tried to wait a couple seconds to see if it was rebooting but nothing happened. tried all button combinations with and without the charger for varying lengths of time but no luck. I hear a sound when its connected to my laptop tho so idk if that matters. Its a bit frustrating right now and i have no clue how to fix this problem and i havent even had the phone for a long time. If someone. anyone can help me, id more than appreciate it
So far, nothing is responding to anything. No lights, no vibrations and i dont see anything when it conencts to my laptop, my laptop just makes the connected sound. I see Fastboot 2.0 detected but the srk tool cannot detect any emulators or devices :/ im so depressed at this point. More or less just bought the ****.
Sounds bad, try using the dload method and if that doesn't work you are ******.
What is the output of "fastboot devices"
vidra said:
Sounds bad, try using the dload method and if that doesn't work you are ******.
What is the output of "fastboot devices"
Click to expand...
Click to collapse
its the dload method that has me in this mess. It didnt reboot from the upgrade and since then i think ive been in fastboot mode. I get a response with the fastboot devices cmd and i manage to flash the boot, recovery and system of the stock firmware but still no luck. Think my only option is to use dc phoenix but i cant buy credits for that
bessonster said:
its the dload method that has me in this mess. It didnt reboot from the upgrade and since then i think ive been in fastboot mode. I get a response with the fastboot devices cmd and i manage to flash the boot, recovery and system of the stock firmware but still no luck. Think my only option is to use dc phoenix but i cant buy credits for that
Click to expand...
Click to collapse
Have you tried flashing MM with dload?
vidra said:
Have you tried flashing MM with dload?
Click to expand...
Click to collapse
not getting to the upgrade screen with dload, the phone restarts but nothing on screen. I can use fastboot only to flash and unlock bootloader, check specifications but thats it. I flashed the stock image which is mm thru fastboot but no luck. I read that i might wait for my battery to drain since my battery isnt rly made to be removable. Can i still use dload without any on screen response?
Have you also tried flashing vendor, cust ... partitions ?
vidra said:
Have you also tried flashing vendor, cust ... partitions ?
Click to expand...
Click to collapse
Fastboot doesnt flash certain img's such as xloader etc, no vendor img included inside the update but i doubt i'd be able to flash it anyway, but i flashed everything i was allowed to incl. cust, boot, recovery, system, cache, . Everything else is giving error: command not allowed. I've hit a brick wall so far til my battery drains or i take it to a repair shop which is i guess, last resort. Can't seem to find help anywhere on the internet, nothing returns anything to the screen.
Looks like a hard brick, take it to an official repair shop. But remember: unlocking the bootlader does NOT void the warranty.
Hi, I've been using a Motorola Moto G6 Plus for quite a long time now. However, I can't figure out why it doesn't show any boot logo at startup, getting a black screen but a USB signal to my PC in fastboot mode (PC detects it at Fastboot evert S, which is good). Can anyone tell me or help me figure out why this phone isn't giving me boot logo's and fastboot?
First of all i wanna make clear that:
1. Can you reboot to system?
2. Can you reboot to recovery?
3. You have Root access in your phone?
Please consider answring.
ai.Sanaul said:
First of all i wanna make clear that:
1. Can you reboot to system?
2. Can you reboot to recovery?
3. You have Root access in your phone?
Please consider answring.
Click to expand...
Click to collapse
Yes, the system works as normal. It runs stock Android 9, not rooted. It doesn't have any recovery installed, and when I try to reboot to ADB, it gives the same black screen as the boot logo and bootloader. The screen is slightly lighting up, so I know it powers up, but it doesn't give the screen I want, the default bootloader screen.
DaHolyBlobfish said:
Yes, the system works as normal. It runs stock Android 9, not rooted. It doesn't have any recovery installed, and when I try to reboot to ADB, it gives the same black screen as the boot logo and bootloader. The screen is slightly lighting up, so I know it powers up, but it doesn't give the screen I want, the default bootloader screen.
Click to expand...
Click to collapse
OK, try flashing stock boot.img through Fastboot or TWRP, this should work.
ai.Sanaul said:
OK, try flashing stock boot.img through Fastboot or TWRP, this should work.
Click to expand...
Click to collapse
TWRP already isn't an option, and I don't know how to do it with fastboot. Could you guide me through that?
OK, so first of all i wanna make clear that you don't use this phone as primary phone because unlocking bootloader and Flashing have chances that your data might be erased, so BACK Up all of your DATA to a safe place before doing this.
If everything is set, Lets move ahead by unlocking your phone's bootloader and flashing. Watch this this tutorial:
Download boot.img file of your phone &
After that boot your phone in fastboot mode connect it to PC and, type this command in CMD fastboot flash boot (boot.img path)
Hope this helps!
ai.Sanaul said:
OK, so first of all i wanna make clear that you don't use this phone as primary phone because unlocking bootloader and Flashing have chances that your data might be erased, so BACK Up all of your DATA to a safe place before doing this.
If everything is set, Lets move ahead by unlocking your phone's bootloader and flashing. Watch this this tutorial:
Download boot.img file of your phone &
After that boot your phone in fastboot mode connect it to PC and, type this command in CMD fastboot flash boot (boot.img path)
Hope this helps!
Click to expand...
Click to collapse
I didn't read your message fully, so didn't back up my phone... Lucky me this isn't my primary phone and it didn't erase anything. It didn't help me though.
Edit: Now that I try booting into Android, it gives the same black screen as the bootloader and logo. I'm starting to think that it unfortunately erased my phone.
Maybe try flashing full stock?
Arealhooman said:
You said Orem unlocking isnt on? How about Adb debugging?
Click to expand...
Click to collapse
I unlocked the bootloader 2 years ago, and ADB is on, but idk if ADB works without android showing up on the screen
Arealhooman said:
Maybe try flashing full stock?
Click to expand...
Click to collapse
Let's try that. How do I flash that with fastboot or adb?
DaHolyBlobfish said:
I unlocked the bootloader 2 years ago, and ADB is on, but idk if ADB works without android showing up on the screen
Click to expand...
Click to collapse
It doesnt. You need a custom recovery or be booted or booting.
DaHolyBlobfish said:
Let's try that. How do I flash that with fastboot or adb?
Click to expand...
Click to collapse
watch this video tutorial (turn on auto translate captions)