hi,
i have my lg d620r stuck in fastboot mode, i found some guides that reflash via fastboot a dump of all the partitions(imei excluded, obv), and i'm here if someone knows where I could find them, or if someone would be so nice to provide me these files
link to the guide(in italian):https://www.tuttoandroid.net/forum/threads/fix-brick-no-recovery-mode-no-download-mode.37272
https://forum.xda-developers.com/g2-mini/development/bootstack-kk-l-unknown-baseband-imei-t3142805
How did you get stuck in fastboot mode?
DrAcula04 said:
How did you get stuck in fastboot mode?
Click to expand...
Click to collapse
it did it by itself, very strange situation
Vagelis1608 said:
https://forum.xda-developers.com/g2-mini/development/bootstack-kk-l-unknown-baseband-imei-t3142805
Click to expand...
Click to collapse
this does work with a modified aboot and a modified recovery
i'm on stock aboot and with no recovery, that's why i need the dumps
mg95tux said:
this does work with a modified aboot and a modified recovery
i'm on stock aboot and with no recovery, that's why i need the dumps
Click to expand...
Click to collapse
I thought you would figure out that you can extract the contents and flash them via fastboot.
If I was you, I would find the laf partition to get download mode working and flash a kdz.
Vagelis1608 said:
I thought you would figure out that you can extract the contents and flash them via fastboot.
If I was you, I would find the laf partition to get download mode working and flash a kdz.
Click to expand...
Click to collapse
i noticed that the guide I found uses .img files, while files in the link you sent me uses .bin
i can use them anyway or i risk a full brick?
mg95tux said:
i noticed that the guide I found uses .img files, while files in the link you sent me uses .bin
i can use them anyway or i risk a full brick?
Click to expand...
Click to collapse
Just find the laf partition to fix download mode and flash a kdz.
Partition backups (usually taken with dd) are the same no natter the extension (img, bin, or even no extension).
Vagelis1608 said:
Just find the laf partition to fix download mode and flash a kdz.
Partition backups (usually taken with dd) are the same no natter the extension (img, bin, or even no extension).
Click to expand...
Click to collapse
tried with these, but fastboot seems useless, it says
Code:
sudo fastboot erase laf
erasing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.002s
and
Code:
sudo fastboot flash laf laf.bin
target reported max download size of 536870912 bytes
sending 'laf' (16896 KB)...
OKAY [ 0.678s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.680s
do you have some suggestion for me how to flash these?
Are you sure you cant get in download mode?
Pull out the battery for a few seconds, put it back in, hold the Vol+ , then insert a USB cable to your PC and the other end to your phone (while holding Vol+)
Make sure that the USB is capable of data transfer, not just charging.
Vagelis1608 said:
Are you sure you cant get in download mode?
Pull out the battery for a few seconds, put it back in, hold the Vol+ , then insert a USB cable to your PC and the other end to your phone (while holding Vol+)
Make sure that the USB is capable of data transfer, not just charging.
Click to expand...
Click to collapse
this is the result
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mg95tux said:
this is the result
Click to expand...
Click to collapse
Try to follow this, but instead of flashing the partitions it says, flash the laf partition.
https://forum.xda-developers.com/showthread.php?t=2582142
Vagelis1608 said:
Try to follow this, but instead of flashing the partitions it says, flash the laf partition.
https://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
doesn't work, i'll try to find a qhsbulk how-to short the processor, and this will be the last chance
mg95tux said:
doesn't work, i'll try to find a qhsbulk how-to short the processor, and this will be the last chance
Click to expand...
Click to collapse
Good luck
Vagelis1608 said:
Good luck
Click to expand...
Click to collapse
In the end, It was the Memory
It's completely gone, so rip g2mini
Thanks for your help!
mg95tux said:
In the end, It was the Memory
It's completely gone, so rip g2mini
Thanks for your help!
Click to expand...
Click to collapse
Do you mean that the NAND chip was wiped?
It can't be, because if it was then the device wouldn't turn on at all.
Vagelis1608 said:
Do you mean that the NAND chip was wiped?
It can't be, because if it was then the device wouldn't turn on at all.
Click to expand...
Click to collapse
If nand chip is wiped/destroyed, the phone will boot a stub fastboot from the chipset, like a "last resource"
And i'm sure nand is gone, since when i put the phone in qhs loader and i checked the nand, It said " dimension 2TB".... Which is the max value that a nand chip could ever have... And It is for sure really too big for this phone
mg95tux said:
If nand chip is wiped/destroyed, the phone will boot a stub fastboot from the chipset, like a "last resource"
And i'm sure nand is gone, since when i put the phone in qhs loader and i checked the nand, It said " dimension 2TB".... Which is the max value that a nand chip could ever have... And It is for sure really too big for this phone
Click to expand...
Click to collapse
If it was destroyed, then it wouldn't start at all.
There are probably more reasons to it, but the first one I can think of is that the aboot partition (secondary bootloader) would be gone and it would only show an empty battery warning, if anything.
When this broken fastboot 'mode' shows up, it means that the dtb of the partition you are trying to boot is faulty, possibly along with the rest of the partition.
dtb holds the device drivers, I believe.
So, the NAND chip is probably good.
Related
I hate to be a newbie but I really read through the entire troubleshooting guide and didn't really understand how to proceed.
I have a rooted Evo 4G LTE with latest stock ROM and TWRP recovery installed (2.5).
This morning my device was pissing me off so I thought it would be a good idea to flash it with CyanogenMod. I went into TWRP, wiped EVERYTHING. loaded the CYanogen Zip on the SD Card, and flashed. Device went right into soft brick.
Tried to flash a couple of other ROMS, also didn't work. in the mean time I discovered BeanStalk which I think is the ROM I want to use.
I have ADB / Fastboot / Latest drivers installed on my computer but when I try to do anything it acts like the device is not connected.
Any advice how to proceed?
From the troubleshooting guide I think my problem might be:
Missing ROM Due to a misunderstanding, you have already wiped all ROM data from phone (cache, dalvik, and system) and fastboot flashed the kernel. Now phone hangs on HTC boot screen and will not load Android. Only the kernel has been flashed, the screen hangs because there is no OS to load. Fear not, return to recovery and flash the ROM package that your boot.image originated from. Now select reboot to system and wait for your phone to restart. The kernel will boot, your OS will load, and all will be right with the world.
Click to expand...
Click to collapse
But I already tried to flash the rom package ( I think).
Help would be much appreciated! thank you!
yoerz said:
I hate to be a newbie but I really read through the entire troubleshooting guide and didn't really understand how to proceed.
I have a rooted Evo 4G LTE with latest stock ROM and TWRP recovery installed (2.5).
This morning my device was pissing me off so I thought it would be a good idea to flash it with CyanogenMod. I went into TWRP, wiped EVERYTHING. loaded the CYanogen Zip on the SD Card, and flashed. Device went right into soft brick.
Tried to flash a couple of other ROMS, also didn't work. in the mean time I discovered BeanStalk which I think is the ROM I want to use.
I have ADB / Fastboot / Latest drivers installed on my computer but when I try to do anything it acts like the device is not connected.
Any advice how to proceed?
From the troubleshooting guide I think my problem might be:
But I already tried to flash the rom package ( I think).
Help would be much appreciated! thank you!
Click to expand...
Click to collapse
If you are s-on you have to fastboot flash or use Flash Image GUI to flash the boot.img/kernel first then flash the rom from twrp
bigdaddy619 said:
If you are s-on you have to fastboot flash or use Flash Image GUI to flash the boot.img/kernel first then flash the rom from twrp
Click to expand...
Click to collapse
Thanks for the help man, I'm just not sure HOW to flash the boot.img/kernel first then flash the rom from twrp
1. Where do I get the Boot.img/kernel? is it just a file I download?
2. What's the command to flash it to the device?
THANK U
You can get a copy of Flash Image GUI here to flash the kernel or pull the boot.img from the rom zip and put it in the folder you have adb and fastboot in and fastboot flash from there.
Here is a guide you can look at to show you how to do the whole process
http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
bigdaddy619 said:
You can get a copy of Flash Image GUI here to flash the kernel or pull the boot.img from the rom zip and put it in the folder you have adb and fastboot in and fastboot flash from there.
Here is a guide you can look at to show you how to do the whole process
http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
Click to expand...
Click to collapse
Well, clearly "Flash Image GUI" isn't going to help me because as I stated before, my device is in boot loop.
I've placed boot.img in my C:\ROOT folder where I keep all my root related files (like ADB and FASTBOOT) but when I run the command:
fastboot flash boot.img
I get the error: unknown partition 'boot.img' error cannot determine image filename for boot.img
Should be
fastboot flash boot boot.img
at this point it just goes < WAITING FOR DEVICE >
I think this is part of the problem. Even though I installed the latest HTC Drivers it seems the computer isn't recognizing the device. When I'm in TWRP and I mount it - it DOES show up in My computer. But not when I'm at that first boot menu.
yoerz said:
at this point it just goes < WAITING FOR DEVICE >
I think this is part of the problem. Even though I installed the latest HTC Drivers it seems the computer isn't recognizing the device. When I'm in TWRP and I mount it - it DOES show up in My computer. But not when I'm at that first boot menu.
Click to expand...
Click to collapse
Try this
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Whats next
OK! turns out I just needed a restart. I ran the command:
C:\ROOT>fastboot flash boot boot.img
sending 'boot' (5770 KB)...
OKAY [ 0.899s]
writing 'boot'...
OKAY [ 1.461s]
finished. total time: 2.360s
Now what? what's the next command? do I flash the rom? the recovery?
yoerz said:
OK! turns out I just needed a restart. I ran the command:
C:\ROOT>fastboot flash boot boot.img
sending 'boot' (5770 KB)...
OKAY [ 0.899s]
writing 'boot'...
OKAY [ 1.461s]
finished. total time: 2.360s
Now what? what's the next command? do I flash the rom? the recovery?
Click to expand...
Click to collapse
Choose recovery from the bootloader then flash the rom like you normally would
ALL GOOD
NEVER MIND! That totally did it! Wonderful! Thank you so much for your help man!
I REALLY appreciate it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This was compiled by me from Sony's AOSP branch for the Z3 Compact. My bootloader is not unlocked so these have not been tested yet. Why no flashable zip? Before I go through the trouble of making one I want to make sure it at least boots. There has been no modifications what so ever.
If it boots then we can make it into a flashable zip.
instructions:
Have an unlocked bootloader
do a full back up or have a way to get back to stock in case something goes wrong
boot into recovery and do a factory reset
boot into fastboot
flash the images in fastboot
fastboot flash boot boot.img
fastboot flash system system.img
flash Gapps (search xda for them)
reboot
pray it boots...
What works?
It boots...
no idea.. you tell me
What's broken?
No idea.. you tell me..
Images can be downloaded on my website:
http://graffixnyc.com/z3compact.php
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. Again, I am not responsible.... It was the other guy... I swear....
I'll take this one...
one more for good luck
The system.img seems corrupt?
C:\adt\sdk\platform-tools>fastb..
sending 'system' (264722 KB)...
OKAY [ 8.289s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 27.345s
NisseGurra said:
The system.img seems corrupt?
C:\adt\sdk\platform-tools>fastb..
sending 'system' (264722 KB)...
OKAY [ 8.289s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 27.345s
Click to expand...
Click to collapse
Did you check the md5? It seems like yours didn't fully download. it should be like 394MB. I created and uploaded it from my linux machine and got the md5 from that file. Uploaded to my ftp server then downloaded it from a windows machine and checked the md5 and it matched (just to make sure the upload went ok)
graffixnyc said:
Did you check the md5? It seems like yours didn't fully download. it should be like 394MB. I created and uploaded it from my linux machine and got the md5 from that file. Uploaded to my ftp server then downloaded it from a windows machine and checked the md5 and it matched (just to make sure the upload went ok)
Click to expand...
Click to collapse
Yes, u correct, download was cut somehow, trying again
Edit: Booting
Booted up nicely, no wifi, network tho
Edit2: Needed to back to old kernel to be able to wipe data. (no recovery in lolipop kernel?)
Edit 3: some reboots, no usb storage, no external sd, no sound or camera
But its very snappy, looking forward to a functional aosp
NisseGurra said:
Yes, u correct, download was cut somehow, trying again
Edit: Booting
Click to expand...
Click to collapse
Anxious to know if it boots and what does and doesn't work
NisseGurra said:
Yes, u correct, download was cut somehow, trying again
Booted up nicely, no wifi, network tho
Edit2: Needed to back to old kernel to be able to wipe data. (no recovery in lolipop kernel?)
Edit 3: some reboots, no usb storage, no external sd, no sound or camera
But its very snappy,
Click to expand...
Click to collapse
good to hear. im going to try it later
Wow,thanksss
I hope someone can find root for locked-bl cos I want aospppp.
Damn this sh!TTY DRM malarky.
If anyone flashes it, can they take a video of the device running it?
I did not install the system.img, but I installed the launcher
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could you maybe make a zip of it?
If so we could then copy the vendor folder from the phone into the zip and check if that fixes any of the bugs.
Here are all the folders being in system.img
Ah sorry I meant as a flashable zip
It's a quick and dirty way to test for problems with the binaries but it works quite well.
I would need the file Meta.inf to realize the zip flashable
Edit: Could use me to build Meta.inf?
@_MutantX_ can you please share the wonderful wallpaper?
thanks
moly82 said:
@_MutantX_ can you please share the wonderful wallpaper?
thanks
Click to expand...
Click to collapse
Hello,
If you speak about the wallpaper of my screenshots, you can find him in the theme : Тема eXPERIAnZ - Azuro
_MutantX_ said:
Hello,
If you speak about the wallpaper of my screenshots, you can find him in the theme : Тема eXPERIAnZ - Azuro
Click to expand...
Click to collapse
thanks my friend. unfortunately I can't download it as it says my device is not compatible (don't have a sony phone).. maybe you could share only the wallpaper? otherwise, never mind and thanks in any case! (and sorry for ot!)
moly82 said:
thanks my friend. unfortunately I can't download it
Click to expand...
Click to collapse
http://goo.gl/rQHnx9
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
64875585 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.490s
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance for your help!
dimxr said:
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
Thanks in advance for your help!
Click to expand...
Click to collapse
I had same problem once all I could do was reboot fastboot but since the bootloader was locked but luckily I found this thread https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/ on oneplus forums this really helped hope this will help you
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number: 64875585
Checking bootloader state..
Device bootloader state is: Locked
Do you want to unlock the bootloader? Type y[yes] or n[no]:y
When prompted, Press the Volume Up/Down button to select Yes on the screen, then
press the Power button to Unlock the Bootloader. If it is already unlocked this
will just be skipped and your device will not be wiped.
Sending oem unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
dimxr said:
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Click to expand...
Click to collapse
Being in the same situation right now. Did you manage to come out of it?
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Kéno40 said:
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Click to expand...
Click to collapse
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
MrEasy666 said:
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
Click to expand...
Click to collapse
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Kéno40 said:
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Click to expand...
Click to collapse
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
MrEasy666 said:
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
Click to expand...
Click to collapse
Lucky you. There was no way for me to get to recovery. Something was wrong there.
The only thing that really worked in the end was the Mega Unbrick Guide. I've got my phone back on track and working.
Glad you managed.
Hi, so I successfully installed TWRP from here, everything went well until this point. I flashed a more stable EU rom and then tried to flash Magisk, but when I rebooted it just went to fastboot mode.
Now everytime I try to turn it off or go back into TWRP it just goes to fastboot mode.
I have tried to flash using MiFlash but I can't seem to get the right thing to flash apparently.
When trying to reinstall TWRP
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.498s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.503s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Zelyric said:
View attachment 5448807
Click to expand...
Click to collapse
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
akins0405 said:
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
Click to expand...
Click to collapse
Reading on that post I saw that there are issues with Ryzen powered computers, and I indeed have a Ryzen CPU. Really hopes this helps, thanks for showing me regardless - ill keep you updated!
@akins0405
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try flashing you stock boot img
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
Where do I find that?
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
You have it in fastboot stock rom
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
Try to transfer the rom to the system partition
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
adb doesn't show my device under adb devices but fastboot devices does show it..
MTP also is disabled
Zelyric said:
adb doesn't show my device under adb devices but fastboot devices does show it..
Click to expand...
Click to collapse
Flash in fastboot stock boot img, can you do it
akins0405 said:
Flash in fastboot stock boot img, can you do it
Click to expand...
Click to collapse
fastboot flash b boot.img
Sending 'b' (196608 KB) OKAY [ 4.817s]
Writing 'b' FAILED (remote: '(b_a) No such partition')
fastboot: error: Command failed
nevermind, i understood the partition wrong.
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.558s]
Writing 'boot_a' OKAY [ 0.707s]
Finished. Total time: 6.103s
what now?
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try firstly erasing your recovery partition with fastboot erase recovery
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Zelyric said:
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Click to expand...
Click to collapse
I'm glad you made it, hello
I have a XT1941-4 that is stuck in the Bootloader. Whenever I press 'START' it says that the device can't be verified and will boot in 5 seconds, but it never actually boots. Is there anything I can do as a noob to get this phone to work again?
you could flash motorola's stock rom to the phone using fastboot on your pc or using motorola rescue and smart assistant. https://www.getdroidtips.com/motorola-rescue-and-smart-assistand-tool/
applesucksLmao said:
you could flash motorola's stock rom to the phone using fastboot on your pc or using motorola rescue and smart assistant. https://www.getdroidtips.com/motorola-rescue-and-smart-assistand-tool/
Click to expand...
Click to collapse
I have tried to go ahead with this tool. It recognises my device but failed at around 50% at step Fastboot Flash before. I just ran it again and its stuck at that step now. Any way to fix this?
ogruendel said:
I have tried to go ahead with this tool. It recognises my device but failed at around 50% at step Fastboot Flash before. I just ran it again and its stuck at that step now. Any way to fix this?
Click to expand...
Click to collapse
Failed after 6 minutes at ~70%
send pictures of the "fail" and the phone screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
applesucksLmao said:
send pictures of the "fail" and the phone screen
Click to expand...
Click to collapse
Just added them to the thread
delete the first photo, as it contains your IMEI number. Have you tried to manually flash the image, and also, are you using the original oem cable?
applesucksLmao said:
delete the first photo, as it contains your IMEI number. Have you tried to manually flash the image, and also, are you using the original oem cable?
Click to expand...
Click to collapse
Deleted the first image. I don't know how to manually flash an image or where to get this image to begin with. I am also not using the cable that came with the phone. I will try to find it and see if that works
Edit: Come to think of it I believe this cable broke a while ago
Ok, so, to help u i gotta get some info first. What country was the phone purchased at/where do u live and use it? Is it updated to android 10? What did u do to that happen?
applesucksLmao said:
Ok, so, to help u i gotta get some info first. What country was the phone purchased at/where do u live and use it? Is it updated to android 10? What did u do to that happen?
Click to expand...
Click to collapse
I bought the phone here in Germany where I live. I believe it was a display unit. I think it had Android 10 on it. I rooted it but when a message popped up saying there was an update available, that wouldn't go away I tried to unroot it and now we're here.
ogruendel said:
I bought the phone here in Germany where I live. I believe it was a display unit. I think it had Android 10 on it. I rooted it but when a message popped up saying there was an update available, that wouldn't go away I tried to unroot it and now we're here.
Click to expand...
Click to collapse
how did you try to unroot it?
applesucksLmao said:
how did you try to unroot it?
Click to expand...
Click to collapse
That was a year ago. I can't remember a lot.
ogruendel said:
That was a year ago. I can't remember a lot.
Click to expand...
Click to collapse
I am able to boot into TWRP. When I'm in TWRP only adb works, when I'm not in TWRP only fastboot works
ogruendel said:
That was a year ago. I can't remember a lot.
Click to expand...
Click to collapse
so you tried to unroot it a year ago and it just happened or its dead for 1 year?
enter fastboot then type this command in cmd
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot reboot
then try to use Rescue and Smart Assistant
best of luck
Hucin44 said:
enter fastboot then type this command in cmd
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot reboot
then try to use Rescue and Smart Assistant
best of luck
Click to expand...
Click to collapse
When running fastboot erase userdata I get (bootloader) Permission denied
ogruendel said:
When running fastboot erase userdata I get (bootloader) Permission denied
Click to expand...
Click to collapse
go to twrp and format data from the wipe section
applesucksLmao said:
go to twrp and format data from the wipe section
Click to expand...
Click to collapse
i mean the slider
applesucksLmao said:
i mean the slider
Click to expand...
Click to collapse
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Wiping data without wiping /data/media ...
Done.
Updating partition details...
...done