Today Morning My phone restarted automatically,then it not boot stuck at Google logo.
After some times Google logo turned into Graphic Glitches and restart.
Same thing happening again and again.
I can't able to go to recovery mode,when i tried to go,it stops at TeamWin logo and restart.
I can able to go to Fastboot mode.I tired to flash a Kernel(boot.img),same graphics glitches happen and stopped.
Fastboot error msg:
Code:
sending 'boot' (6014 KB)...
OKAY [ 0.766s]
writing 'boot'...
FAILED (status read failed (Too many links))
finished. total time: 0.797s
Any way to recover my phone?:crying:
Is it possible to reset my mobile via fastboot?
Any help please?:crying:
Graphics Glitches See Attachment.
{
"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"
}
I tried to flash a bootloader to from Nexus Images(Official).
Same error was showed.
"error out of memory"
Now i can't able go to fastboot mode
Is my mobile bricked?
Omap flash?
But it seems like your MMC died.
Beamed from my Maguro.
I tried to factory reset my mobile by flash stock image.
First i started with bootloader.img,it was stopped.
Now fastboot was not working.
Do i need to take to service center?
Read this thread http://forum.xda-developers.com/showthread.php?t=478820&page=4 and all of its posts.
Sent from my Nexus
I flashed OMAP and got fastboot.
Then i tired to flash radio,system etc..
Same error:
sending 'recovery' (4900 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.571s
D:\Android\android-sdk\platform-tools>fastboot
tory-b2ebb5f3\image-yakju-jdq39\recovery.img
error: out of memory
i tired it on my Laptop and pc with different cable.
Hello? Did you read the ENTIRE, AND CLOSELY, the thread i linked you? That was only the first hit on Google-xda search.
Sent from my Nexus
Yeah i read that completely.
He has write error.
i have read error only.
Then also i tried many ports.But not succeeded.
I think it was a internal memory problem.
I can able to erase,format a system.
Only when i try to flash,problem occur.
Can any one tell me how to replace the internal memory?
Related
So i tried to flash new ROM. got inte bootloader, chose option "recovery" but seems like it freezes at HTC splash screen. So i connected device to computer and tried to flash two new recoveries, CWM and...some other i can't name of the top of my head. Using fastboot flash recovery command. they resulted:
sending 'recovery' (4182 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
What should I do?`
Device S-OFF with alpharev
Amphor said:
So i tried to flash new ROM. got inte bootloader, chose option "recovery" but seems like it freezes at HTC splash screen. So i connected device to computer and tried to flash two new recoveries, CWM and...some other i can't name of the top of my head. Using fastboot flash recovery command. they resulted:
sending 'recovery' (4182 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
What should I do?`
Device S-OFF with alpharev
Click to expand...
Click to collapse
try this:
first:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery [URL="http://www.mediafire.com/?5xrndbh5obumfz7"]recovery.img[/URL]
MD5: 6CBF5C129739F3DE0948EA6F3D274CEA
erasing 'recovery'...
FAILED (status malformed (1 bytes))
finished. total time: 0.002s
try different cable/pc
fastboot devices working?
Amphor said:
erasing 'recovery'...
FAILED (status malformed (1 bytes))
finished. total time: 0.002s
Click to expand...
Click to collapse
Put the attached file in the root of your sd-card, and boot into HBOOT (not fastboot).
You may need a goldcard for it to work.
I was always in hboot, not in fastboot, so flashing didn't work(but devices did)
My bad
Amphor said:
I was always in hboot, not in fastboot, so flashing didn't work(but devices did)
My bad
Click to expand...
Click to collapse
{
"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"
}
Hello
Today I tried to flash TWRP on my Moto G5S because I wanted to use a custom ROM. While trying to flash TWRP on the phone, I got this error:
Code:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15850 KB) OKAY [ 0.696s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.387s]
Finished. Total time: 1.191s
I have USB Debugging enabled, the bootloader is unlocked, and I'm using the latest version of TWRP (3.3.1.0) made for this phone.
I have never installed TWRP or anything similar before, so I don't know how to fix this. I have searched on Google, but no results are about this same problem. If anyone knows how to fix this issue, please tell me how.
Thanks.
Lekrkoekj said:
Hello
Today I tried to flash TWRP on my Moto G5S because I wanted to use a custom ROM. While trying to flash TWRP on the phone, I got this error:
Code:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15850 KB) OKAY [ 0.696s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.387s]
Finished. Total time: 1.191s
I have USB Debugging enabled, the bootloader is unlocked, and I'm using the latest version of TWRP (3.3.1.0) made for this phone.
I have never installed TWRP or anything similar before, so I don't know how to fix this. I have searched on Google, but no results are about this same problem. If anyone knows how to fix this issue, please tell me how.
Thanks.
Click to expand...
Click to collapse
DId this ever get fixed? I have been going through the same process on my moto x4 - twrp - flashing lineageOS but I am having hang ups and I think they are bootloader related
Lekrkoekj said:
Hello
Today I tried to flash TWRP on my Moto G5S because I wanted to use a custom ROM. While trying to flash TWRP on the phone, I got this error:
Code:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15850 KB) OKAY [ 0.696s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.387s]
Finished. Total time: 1.191s
I have USB Debugging enabled, the bootloader is unlocked, and I'm using the latest version of TWRP (3.3.1.0) made for this phone.
I have never installed TWRP or anything similar before, so I don't know how to fix this. I have searched on Google, but no results are about this same problem. If anyone knows how to fix this issue, please tell me how.
Thanks.
Click to expand...
Click to collapse
its says image not signed or corrupt, did you make sure that flashing=unlocked at the bootom of the screen on bootloader menu (fastboot)?????????
Rush said:
its says image not signed or corrupt, did you make sure that flashing=unlocked at the bootom of the screen on bootloader menu (fastboot)?????????
Click to expand...
Click to collapse
Yes
I want this to get fixed because LineageOS 17.1 is taking a lot of space on my Moto X4. I wanna flash PixelExperience... You can see the screenshot I have attached.
{
"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"
}
Maybe its too late but I solved it by activating USB Debugging
Hi guys, i really need help here.
i wanted to flash and install TWRP.img on my redmi note 8 today, but i accidentally used the cmd command fastboot flash boot TWRP.img .
my phone then only boots to TWRP instead of my usual MIUI. so i tried flashing the whole note 8 rom using MiFlashTool. However, there is a error (error:Mismatching image and device), and now my phone only shows me that "the system has been destroyed".
when i tried to flash another boot.img to the phone, it shows "FAILED (command write failed (unknown error))"
{
"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"
}
anyone know what i should do to fix this phone? will really appreciate any help... :crying:
I don't know if you can enter to fastboot mode (power + vol down button). If you can, you can try fastboot flash recovery TWRP.img and search for boot.img at Google I think....
---------- Post added at 23:41 ---------- Previous post was at 23:36 ----------
I think this may helps: https://c.mi.com/thread-2542493-1-0.html
I think that the key is to get boot.img (miui or custom rom) from installation zip and flash it again to the phone via fastboot
If you could boot into twrp, then try to flash the boot image of your firmware from twrp. First extract the boot image and place it in your SD card, then in twrp select flash image and flash it to the boot partition, might work.
I got the same message even when trying to boot into recovery, even flashing the recovery again didn't work, so I downloaded The stock rom uncompressed and flashed each img manually with fastboot
Leeban Joseph said:
If you could boot into twrp, then try to flash the boot image of your firmware from twrp. First extract the boot image and place it in your SD card, then in twrp select flash image and flash it to the boot partition, might work.
Click to expand...
Click to collapse
This is the right solution
Dont worry you phone isnot destroyed ,just fellow these instructions
Hello Community!
I unlocked my 7 days old REDMI NOTE 8 with MI UNLOCK. All fine.
Then I Boot into Fastboot-mode and flashed TWRP.IMG (twrp-3.3.1-0-ginkgo.img) and started into TWRP (Recovery). On internal drive i copied new XIAOMI.EU, deleted all data. Take a reboot into Recovery, too.
But now I get "Message THE SYSTEM hat been destroyed".
MI UNLOCK SAYs UNLOCK no Nessesary. Is unlocked.
I COULD NOT BOOT INTO TWRP after Flashing TWRP.IMG
Devicecheck:
d:\platform-toolsfastboot devices
130fd5f2 fastboot
Writing TWRP is possible:
d:\platform-toolsfastboot flash recovery twrp.imgSending 'recovery' (65536 KB) OKAY [ 1.673s]
Writing 'recovery' OKAY [ 0.287s]
Finished. Total time: 1.980s
Command CONTINUE:
d:\platform-toolsfastboot continue
resuming boot FAILED (status read failed (Too many links))
Finished. Total time: 30.073s
Can Someone help me, please?
Many Thanks!
I tried to flash with MI Flash (Fastboot.rom)
ginkgo_global_images_V11.0.3.0.PCOMIXM_20191119.0000.00_9.0_global_a8923e1765.tgz
Now I am back to Stock!
Thank you!
Hi all,
when installing Lineage 18.1 on my Nexus 7 (2013) flo, i keep getting this ERROR: 1
i figured i must be missing something, so i wiped everything and re-uploaded the image to the internal storage over usb.
unfortunatly this keeps happening
any help would be much appreciated
{
"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"
}
basdejongg said:
Hi all,
when installing Lineage 18.1 on my Nexus 7 (2013) flo, i keep getting this ERROR: 1
i figured i must be missing something, so i wiped everything and re-uploaded the image to the internal storage over usb.
unfortunatly this keeps happening
any help would be much appreciated
Click to expand...
Click to collapse
Hi, let's see...
Code:
Transferring: 449987627/449987627 (100%)
3263 KB/s (449987627 bytes in 134.671s)
Wait...
Installing zip file '/tmp/lineage-18.1-20210306-UNOFFICIAL-flo.zip'
Checking for Digest file...
Unmounting System...
Target: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
Error installing zip file '/tmp/lineage-18.1-20210306-UNOFFICIAL-flo.zip'
Done processing script file
You're right. Let's remedy this situation with sysrepart-ultimate.zip...
Code:
Transferring: 174140/174140 (100%)
3627 KB/s (174140 bytes in 0.046s)
Wait...
Installing zip file '/tmp/sysrepart-ultimate.zip
Checking for Digest file...
Unmounting System...
##########################################
# k23m Nexus 7'13 Repartition [ultimate] #
##########################################
Creating log
Removing partitions
Creating new partitions
Formatting new partitions
#######################
# Operation completed #
# REBOOT NOW! #
#######################
Done processing script file
...and re-try...
Code:
Transferring: 449987627/449987627 (100%)
3168 KB/s (449987627 bytes in 138.671s)
Wait...
Installing zip file '/tmp/lineage-18.1-20210306-UNOFFICIAL-flo.zip'
Checking for Digest file...
Unmounting System...
Target: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keys
Patching system image unconditionally...
script succeeded: result was [1.000000]
Done processing script file
All OK
Thanks @k23m for the sysrepart, i used TWRG to run that and it did work fine.
now the nexus keep booting in fastboot mode and i cannot install TWRG again to install the lineage.zip
fastboot flash recovery .\twrp-3.5.2_9-0-flo.img
sending 'recovery' (10060 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.026s
basdejongg said:
fastboot flash recovery .\twrp-3.5.2_9-0-flo.img
sending 'recovery' (10060 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.026s
Click to expand...
Click to collapse
"FAILED (data transfer failure (Unknown error))" is actually a known error of bad USB cables as you can read eg here.
Incidentally, you could install everything automatically in one go with CROSS.
thanks! now i get the message that the file size is to big
Code:
.\twrp-3.5.2_9-0-flo.img
sending 'recovery' (10060 KB)...
OKAY [ 0.337s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 0.378s
any idea @k23m ?
basdejongg said:
any idea @k23m ?
Click to expand...
Click to collapse
Yes, already suggested in CROSS...
"If direct sysrepart installation is impossible due to TWRP or GPT issues, run the repartition.bat script."
"If you see errors, copy and report them. Run getlog.bat and include "getlog.log" in your post. If possible, also run relog.bat and attach "relog-xxxxxx.zip" to your post."
"CROSS works on PC with Windows, or WinPE if you do not have Windows installed." (or in VirtualBox)
I have a Lenovo P2, unrooted, on stock Android, with a 256mb micro SD card. It hasn't been unlocked/flashed/rooted in any way apart from Developer Options to allow ADB.
A couple of days ago the phone started to lag and lock up, and then rebooted into "AP Fastboot Flash Mode (Secure)" menu. The only options are Start/Barcodes/Power Off.
The Start and Power Off/On options simply reboot back to the same screen after a couple of seconds. It won't boot back into Android with any combination of volume up/down/power buttons, or offer me any other options such as recovery or clear cache etc.
I've tried rebooting with/without the SD card - it makes no difference.
The phone still appears to be recognised by ADB when I connect it to a laptop - it appears in 'fastboot devices' - but I still can't get it to exit fastboot and boot back into Android with any ADB command.
I've tried downloading Reiboot and "15 second adb" toolkits which claim to exit fastboot mode, but without success.
I'm assuming the bootloader is corrupted.
Can anyone please point me towards any possible action for fixing it, or is it bricked?
Many thanks.
{
"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"
}
The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?
If your rom is not booting you might need to reinstall it.
Keno_I said:
The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?
Click to expand...
Click to collapse
Here's what I've tried with ADB - the phone seems to be connected as evidenced by "fastboot devices", but I don't know what to do now. "Fastboot reboot" just brings me back to the same Fastboot screen in my original post, as does holding down vol+/vol-/power for several seconds.
I successfully unlocked/flashed a ZTE San Francisco Blade back in the day, so I don't mind trying to flash this P2 if that's the answer and you can point me towards a noob-friendly guide, please.
Reinstall the stock rom from fastboot
@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.
bigajm said:
@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.
Click to expand...
Click to collapse
You have to find and flash a valid flash image, try with the same version you were installed on
Can someone provide me with a twrp restore file? I tried to flash the stock rom but the bat file that came with it tampered with some files and I can't even boot into the stock rom