Related
Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance
I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that
Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload
Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.
Model: Asus Zenfone 2 ZE551ML
After updating to latest version i decided to wipe partition cache while on the process it showed erasing android bot then restarted and hung on asus logo for nearly an hour so i decided there is some problem and force switched off then after switching on it shows the blinking android error bot.........im unable to enter neither recovery mode nor fastboot mode(when entering it shows for a some seconds waiting fastboot cmd bt then comes again to the normal boot screen)....
Its been nearly a week i went thru various post and tried most of the methods like entering recovery mode thru adb(as im unable to enter fastboot mode it shows in cmd waiting for device) and pressing both buttons same for stock recovery(it shows some lines saying in last line can't mount recovery)
SO CAN SOMEBODY THROW LIGHT ON WHAT EXACTLY NEEDS TO BE DONE TO RECOVER MY PHONE FROM THIS ERROR.... would be grateful and thanks in advance.
Feel like you for the same worries as I did.
Try to flash bootdroid.img / boot.img / recovery.img with fastboot commands and that should do the trick.
For recovery I renamed twrp.img to recovery.img to get twrp right away
cuberio1 said:
Feel like you for the same worries as I did.
Try to flash bootdroid.img / boot.img / recovery.img with fastboot commands and that should do the trick.
For recovery I renamed twrp.img to recovery.img to get twrp right away
Click to expand...
Click to collapse
now i got some idea bt can u tell a bit elaborate what exactly i need to do..... (downloads and cmd commands)
Rockybala90 said:
Model: Asus Zenfone 2 ZE551ML
After updating to latest version i decided to wipe partition cache while on the process it showed erasing android bot then restarted and hung on asus logo for nearly an hour so i decided there is some problem and force switched off then after switching on it shows the blinking android error bot.........im unable to enter neither recovery mode nor fastboot mode(when entering it shows for a some seconds waiting fastboot cmd bt then comes again to the normal boot screen)....
Its been nearly a week i went thru various post and tried most of the methods like entering recovery mode thru adb(as im unable to enter fastboot mode it shows in cmd waiting for device) and pressing both buttons same for stock recovery(it shows some lines saying in last line can't mount recovery)
SO CAN SOMEBODY THROW LIGHT ON WHAT EXACTLY NEEDS TO BE DONE TO RECOVER MY PHONE FROM THIS ERROR.... would be grateful and thanks in advance.
Click to expand...
Click to collapse
maybe you have flashed wrong droidboot img for fastboot partition.. if you manage to enter fastboot mode, you may try to type
fastboot erase cache
but only if you able to enter fastboot..usually wiping cache from stock recovery may stuck but it can be cleared with that command.. but if you are unable to enter fastboot mode sorry then, hope that someone expert can help you..
I unlocked bootloader of my phone, flashed TWRP then installed new ROM and then tried to boot bt the only thing I get on my screen is "the current image(boot/recovery) have been destroyed and cannot boot"
This screen repeats and I cn't do anything, not able to find any good tool or something to flash stock rom again...Please help am alrady dead
Dude, you just should flashing original/stock boot.img and recovery.img. And your phone already fixed.
Jus flash vbmeta and than flash twrp again . It will work fine and you won't get erro
Flash vbmeta
where did you got the file?
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
orl4nd said:
where did you got the file?
Click to expand...
Click to collapse
I found one in the pixel rom thread, it worked fine for me when i had this issue flashing candy rom
Ragzone said:
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
Click to expand...
Click to collapse
You have to flash the boot.img via adb to boot into Fastboot or Recovery.
Stuck at same problem.
I am also facing same problem. I can't open fastboot and the phone reboots to stock recovery after some time. Please help.
same problem for me
Ragzone said:
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
Click to expand...
Click to collapse
i have the same problem exactly. no access to adb commands nor recovery. please let me know if you could find a solution.
reza14 said:
i have the same problem exactly. no access to adb commands nor recovery. please let me know if you could find a solution.
Click to expand...
Click to collapse
I will keep trying the different flashing tools. Also let me know if you are succesful.
RMX1901CH unbirick
RMX1901CH
I was in the same state but unbirick.
When the power is off Press the volume minus and the power simultaneously.
If you are in fastboot mode
1.adb flashing command // fastboot flash recovery twrp-3.3.1-24- RMX1901-mauronofrio.img
2. after starting TWRP - connected with otg usb memory (StockROM.ozip)
3. USBOTG to mount
4.wipe dalvik / ARTCache & cache & system & data
* 5. INSTALL StockROM
* RMX1901_11_OTA_0190_all_fSt4F56aQlqf.ozip (China) A19
I haven't tried with older versions
The international version will show an inappropriate error, and it may be possible with the same language model
* 6. reboot
Japanese who cannot speak English
I did this way
Is this problem Solve? i face the same problem. what can i do?
Hatzey said:
I unlocked bootloader of my phone, flashed TWRP then installed new ROM and then tried to boot bt the only thing I get on my screen is "the current image(boot/recovery) have been destroyed and cannot boot"
This screen repeats and I cn't do anything, not able to find any good tool or something to flash stock rom again...Please help am alrady dead
Click to expand...
Click to collapse
Please help me.
same issue , can't do anything
the only way I found is , to know this user and pass in this tool so that I could test the firmware and post this here
Такая же проблема, помогите!!!
Long press volume down and power button , the phone will boot into fastboot mode. Flash vbmeta with disable verity command . It worked for me. No need do anything else.
volume down and power button for 10 sec
then flash stock recovery
then wipe data from stock rocovery
then back to bootloader and flash twrp recovery
then transfer stock rom zip on device
install it
done
Man i have the same problem, did you find any solution?
I already downloaded the qualcomm flash image loader, the pc detects the phone only when i press volume + and volume - and connect it, so i know i can do something, im gonna try with the EDL mode, any advance i'll let you know
how to do Flash vbmeta with disable verity command ???
Hello i need help please.
I was trying to flash twrp using adb and fastboot when i accidentally flash aboot.img into system and now it wont boot into the system and it stuck on lg logo and it wont let me boot into recovery mode. When i do the Vol. down + power it directs me to factory data reset and I tried resetting it and gave me an error "Your device is corrupt. It can't be trusted and may not work properly."
Does anybody know how to fix this issue please?.
Hello everybody, I have a problems with unbricking Note 8 Pro - begonia - M1906G7G.
It stuck in boot loop. Bootloader is locked.
I have tried that python bypass and flashing firmware using SP Flash Tool. I get success / done message after a while, but when I power the phone, there are no changes. Phone is sitll in boot loop.
Is there anything, what can I do?
Thank you in advance!
EDIT:
Have just tried to flash TWRP, now I'm getting "system has been destroyed" error. So flashing probably works. Problem must be somewhere else.
If you dont care about data (I think you dont because you flashed by Sp flash tool), just unlock bootloader and flash by Sp Flash Tool again. Maybe you flash fastboot rom not same region with stock phone with locked bootloader. This is the way to unlock bootloader unofficial way you can try.
Kirasu2080 said:
If you dont care about data (I think you dont because you flashed by Sp flash tool), just unlock bootloader and flash by Sp Flash Tool again. Maybe you flash fastboot rom not same region with stock phone with locked bootloader. This is the way to unlock bootloader unofficial way you can try.
Click to expand...
Click to collapse
At first, I could not use that tool. Everytime I tried, I get this error: "mtk: error: argument cmd: invalid choice: 'xflash'".
I had to edit the mtkclient-gui.py with this two commands (from github)
subprocess.call(f"{runtime} mtkclient/mtk e metadata,userdata,md_udc")
subprocess.call(f"{runtime} mtkclient/mtk da seccfg unlock")
Now after running the commands I get this in log: "Failed to format all partitions." and after that: "
100.0% Write (Sector 0x1 of 0x1, ) 0.05 MB/s
xflashext - Successfully wrote seccfg."
After this process, when I turn on the phone I get errors:
"dm-verify error
Android system on your device is corrupted."
When I check with fastboot mode, phone have bootloader unlocked now.
So I have tried to flash firmware using SP Flash Tool, got 100% done success message, but on phone I still can see only:
"dm-verify error
Android system on your device is corrupted."
I have also tried fastboot rom and flashing using fastboot "flash_all.bat". Result was "OKAY" for every single file. Phone rebooted and again this error:
"dm-verify error
Android system on your device is corrupted.".
UPDATE:
Finally found firmware, which does not give me "dm-verify error. Android system on your device is corrupted.". But phone is still in a bootloop.
Growicek said:
At first, I could not use that tool. Everytime I tried, I get this error: "mtk: error: argument cmd: invalid choice: 'xflash'".
I had to edit the mtkclient-gui.py with this two commands (from github)
subprocess.call(f"{runtime} mtkclient/mtk e metadata,userdata,md_udc")
subprocess.call(f"{runtime} mtkclient/mtk da seccfg unlock")
Now after running the commands I get this in log: "Failed to format all partitions." and after that: "
100.0% Write (Sector 0x1 of 0x1, ) 0.05 MB/s
xflashext - Successfully wrote seccfg."
After this process, when I turn on the phone I get errors:
"dm-verify error
Android system on your device is corrupted."
When I check with fastboot mode, phone have bootloader unlocked now.
So I have tried to flash firmware using SP Flash Tool, got 100% done success message, but on phone I still can see only:
"dm-verify error
Android system on your device is corrupted."
I have also tried fastboot rom and flashing using fastboot "flash_all.bat". Result was "OKAY" for every single file. Phone rebooted and again this error:
"dm-verify error
Android system on your device is corrupted.".
UPDATE:
Finally found firmware, which does not give me "dm-verify error. Android system on your device is corrupted.". But phone is still in a bootloop.
Click to expand...
Click to collapse
Flash this TWRP if you using Miui 12.5.x: MOD EDIT: Link Removed
Try
- Advanced > Patch vbmeta
- Reboot > System and check
If you dont have twrp:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And vbmeta.img take from fastboot or recovery rom you flashed
If not work, try flash custom rom same as Miui Firmware based to check if phone still can work or not.
And if Custom roms work, just throw Miui away.
Kirasu2080 said:
Flash this TWRP if you using Miui 12.5.x: MOD EDIT: Link Removed
Try
- Advanced > Patch vbmeta
- Reboot > System and check
If you dont have twrp:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And vbmeta.img take from fastboot or recovery rom you flashed
If not work, try flash custom rom same as Miui Firmware based to check if phone still can work or not.
And if Custom roms work, just throw Miui away.
Click to expand...
Click to collapse
Have tried flashing that TWRP. After doing it, I have tried: fastboot reboot recovery. Recovery never loaded. Just pure bootloop. Have also tried flashing vbmeta.img from firmware I have flashed. Then I powered on the phone. Again bootloop. When I tried to flashing few others TWRP. Same result - bootloop. Recovery never boot.
Could not find any custom rom, which is flashable through SP Flash Tool (With working scatter etc..), so I have tried to flash img files from custom rom one by one using fastboot (probably did something wrong or maybe not, idk), phone still in bootloop.
Growicek said:
At first, I could not use that tool. Everytime I tried, I get this error: "mtk: error: argument cmd: invalid choice: 'xflash'".
I had to edit the mtkclient-gui.py with this two commands (from github)
subprocess.call(f"{runtime} mtkclient/mtk e metadata,userdata,md_udc")
subprocess.call(f"{runtime} mtkclient/mtk da seccfg unlock")
Now after running the commands I get this in log: "Failed to format all partitions." and after that: "
100.0% Write (Sector 0x1 of 0x1, ) 0.05 MB/s
xflashext - Successfully wrote seccfg."
After this process, when I turn on the phone I get errors:
"dm-verify error
Android system on your device is corrupted."
When I check with fastboot mode, phone have bootloader unlocked now.
So I have tried to flash firmware using SP Flash Tool, got 100% done success message, but on phone I still can see only:
"dm-verify error
Android system on your device is corrupted."
I have also tried fastboot rom and flashing using fastboot "flash_all.bat". Result was "OKAY" for every single file. Phone rebooted and again this error:
"dm-verify error
Android system on your device is corrupted.".
UPDATE:
Finally found firmware, which does not give me "dm-verify error. Android system on your device is corrupted.". But phone is still in a bootloop.
Click to expand...
Click to collapse
That dm-verity error is normal if you use mtkclient. You need to lock the phone in mtkclient and reunlock the phone in the normal way to get rid of that error
Also the link seems to got removed but i use Salih-Sonar's TWRP for MIUI 12.5 (search begonia-oss and download the MIUI 12.5 one)
You can just flash the full fastboot rom and it should work unless you corrupted properitary partitions (nvdata,persist,nvcfg etc)
Canny1913 said:
That dm-verity error is normal if you use mtkclient. You need to lock the phone in mtkclient and reunlock the phone in the normal way to get rid of that error
Also the link seems to got removed but i use Salih-Sonar's TWRP for MIUI 12.5 (search begonia-oss and download the MIUI 12.5 one)
You can just flash the full fastboot rom and it should work unless you corrupted properitary partitions (nvdata,persist,nvcfg etc)
Click to expand...
Click to collapse
I have finally after hours and hours of trying flashed firmware, which is not stuck in bootloop. Now the phone reboots after few seconds of running. I found out, that CPU is overheating, so probably hardware issue. Will try reball of the CPU chip and we will see, if it helps.
Growicek said:
I have finally after hours and hours of trying flashed firmware, which is not stuck in bootloop. Now the phone reboots after few seconds of running. I found out, that CPU is overheating, so probably hardware issue. Will try reball of the CPU chip and we will see, if it helps.
Click to expand...
Click to collapse
Well good luck then.
There is a super small chance that the overheat is be related to the firmware though. But the odds of that are really low if the phone is running normal.
Canny1913 said:
Well good luck then.
There is a super small chance that the overheat is be related to the firmware though. But the odds of that are really low if the phone is running normal.
Click to expand...
Click to collapse
Phone was in a bootloop, so I have unlocked bootloader, flashed latest firmware, phone was still in bootloop. So I have flashed very very old firmware and then phone booted successfuly. I was able to set language, region, connect to wifi and then freeze. After few seconds it rebooted. I have checked the temperature of CPU (with my finger) and it was quite hot.
Let's hope that reballing will help.