Related
Hi guys,
I was trying to root my phone(EMUI 4.0, Marsh mellow), first i unlocked bootloader, then installed twrp, everything was right till then, when i installed SU, and rebooted the phone got stuck at logo screen.
Then I installed another rom, which changed phone model to HI6210SFT, but wifi and bluetooth was not working.
So, I installed another rom, this time indian version, bluetooth, wifi, sim were working fine, but still Model remained HI6210SFT.
Then i got another rom, this time the pak version, after flashing that, the phone is now stuck at boot screen, nothing works.
I can go into Fastboot, TWRP, but not into UPDATE mode.
I tried flashing multiple roms, still phone is stuck.
Xaadi Xhahid said:
Hi guys,
I was trying to root my phone(EMUI 4.0, Marsh mellow), first i unlocked bootloader, then installed twrp, everything was right till then, when i installed SU, and rebooted the phone got stuck at logo screen.
Then I installed another rom, which changed phone model to HI6210SFT, but wifi and bluetooth was not working.
So, I installed another rom, this time indian version, bluetooth, wifi, sim were working fine, but still Model remained HI6210SFT.
Then i got another rom, this time the pak version, after flashing that, the phone is now stuck at boot screen, nothing works.
I can go into Fastboot, TWRP, but not into UPDATE mode.
I tried flashing multiple roms, still phone is stuck.
Click to expand...
Click to collapse
You nerd to flash stock ROM...
hassanjavaid8181 said:
You nerd to flash stock ROM...
Click to expand...
Click to collapse
How, can you explain please?I tried flashing at least 4 different roms, the only one booted the phone but the problem was the phone had no connectivity, i cannot go into UPDATE mode, so tried flashing via fastboot. but still no luck, its stuck on the first screen...
any help will be appreciated, thanks in advance
hassanjavaid8181 said:
You nerd to flash stock ROM...
Click to expand...
Click to collapse
all those 4 roms were stock.
Xaadi Xhahid said:
all those 4 roms were stock.
Click to expand...
Click to collapse
Flashed it via dload method?
hassanjavaid8181 said:
Flashed it via dload method?
Click to expand...
Click to collapse
no, via FASTBOOT method, System.img, recovery.img, boot.img
I tried the dload method, but the phone doesnt go into UPDATE mode, instead it goes to twrp on pressing Vol +, Vol - and power button
Xaadi Xhahid said:
no, via FASTBOOT method, System.img, recovery.img, boot.img
I tried the dload method, but the phone doesnt go into UPDATE mode, instead it goes to twrp on pressing Vol +, Vol - and power button
Click to expand...
Click to collapse
You will have to flash stock recovery then use dload method
Dload will not work on twrp..
hassanjavaid8181 said:
You will have to flash stock recovery then use dload method
Dload will not work on twrp..
Click to expand...
Click to collapse
It should work, dload method doesn't use normal recovery. I think it uses eRecovery.
Thanks, I will try your methods, and will update if i get lucky.
Xaadi Xhahid said:
Thanks, I will try your methods, and will update if i get lucky.
Click to expand...
Click to collapse
First of all install TWRP from Here
https://forum.xda-developers.com/p8lite/orig-development/twrp-t3583180
Now Download the MM Rom From Here
http://www.carbontesla.com/2016/07/download-honor-4c-b530-marshmallow-update-india/
Now wipe all partitions from TWRP
and flash the MMRom.zip through twrp it will boot your device normally.
For more info go to this link
https://forum.xda-developers.com/honor-4c/how-to/installing-p8lite-roms-honor-4c-t3617942
try using adb
Xaadi Xhahid said:
Hi guys,
I was trying to root my phone(EMUI 4.0, Marsh mellow), first i unlocked bootloader, then installed twrp, everything was right till then, when i installed SU, and rebooted the phone got stuck at logo screen.
Then I installed another rom, which changed phone model to HI6210SFT, but wifi and bluetooth was not working.
So, I installed another rom, this time indian version, bluetooth, wifi, sim were working fine, but still Model remained HI6210SFT.
Then i got another rom, this time the pak version, after flashing that, the phone is now stuck at boot screen, nothing works.
I can go into Fastboot, TWRP, but not into UPDATE mode.
I tried flashing multiple roms, still phone is stuck.
Click to expand...
Click to collapse
you can use adb if your custom recovery is working, the do a sideload
brianjb_jbbrian said:
you can use adb if your custom recovery is working, the do a sideload
Click to expand...
Click to collapse
What about if the recovery is not working?
arczangel said:
What about if the recovery is not working?
Click to expand...
Click to collapse
You can flash stock recovery via adb fastboot..
arczangel said:
What about if the recovery is not working?
Click to expand...
Click to collapse
Extract ur exact stock rom using Huawei extractor and then flash the system.img and cust.img
Hi
Was having trouble with phone and then did a restore back to saved version
However now the phone is stuck on Fast boot mode It gives the options to start in below
Bootloader
Recovery Mode
Power Off
START
However whatever I choose it keeps going into FastBoot mode with menu below
Product name
Variant
Bootloader version
Baseband Version
Serial Number
Secure Boot - Yes
Device State unlocked
I have tried power off an then press power and volume up and down and keeps booting into fastboot mode
I have connected it to PC and PC not picking it up
Tried rebooting with power cable plugged in and same issue stuck in fastboot
Has anyone got any solutions otherwise I have to send it to OP7 for repair
I guess if you can boot twrp and flash Magisk it will boot.
Or use msmtool to restore your phone to oos9 or oos10 formating data and erase your stuff
I don't know how you restored your phone into a "stable" version maybe you used the twrp for Android 11?
You need to provide more information about the state of your phone
RokCruz said:
I guess if you can boot twrp and flash Magisk it will boot.
Or use msmtool to restore your phone to oos9 or oos10 formating data and erase your stuff
I don't know how you restored your phone into a "stable" version maybe you used the twrp for Android 11?
You need to provide more information about the state of your phone
Click to expand...
Click to collapse
Thats the problem I cannot boot to anything except Fastboot. Gives option to boot to recovery but when I select it boots back into Fastboot
I was on Android 10 and having issues with phone connected to PC not picking it up etc and cables, drivers etc was working ok as have OP5 and could pick up that
Tried everything and nothing worked and also was not getting push notifications so could not purchase online
So last resort was to revert back to back up over 1 month old. Did that and for what ever reason phone booted back to fastboot and PC still wont pick it up so cannot even connect via adb
I restored it using TWRP and now everything I try just not working and looking at sending it back to OP to get it to factory reset as I cannot even do that
funkyirishman said:
Thats the problem I cannot boot to anything except Fastboot. Gives option to boot to recovery but when I select it boots back into Fastboot
I was on Android 10 and having issues with phone connected to PC not picking it up etc and cables, drivers etc was working ok as have OP5 and could pick up that
Tried everything and nothing worked and also was not getting push notifications so could not purchase online
So last resort was to revert back to back up over 1 month old. Did that and for what ever reason phone booted back to fastboot and PC still wont pick it up so cannot even connect via adb
I restored it using TWRP and now everything I try just not working and looking at sending it back to OP to get it to factory reset as I cannot even do that
Click to expand...
Click to collapse
That backup was from an older version of OOS?
In this point if you can't boot twrp the only safe way is using msmtool
RokCruz said:
That backup was from an older version of OOS?
In this point if you can't boot twrp the only safe way is using msmtool
Click to expand...
Click to collapse
No it was Android 10 pretty sure
Ok downloaded MSM tool just trying to figure out how to use it so checking that
Otherwise its going back to OP as under Guarantee and nothing I need on it Pics backed up but will come back with Android 11 if they can fix it
Android 10 but which version? It's not recommended to downgrade.
In msmtool are the instructions, download the correct msmtool for your device.
Not sure what version think it was the last one ???
Have msm tool and installed cert but now getting Package image not exist when I run the MSM download tool?
What was the file size of the MSM tool. Does it have the .ops file included over 2gb
justencase6 said:
What was the file size of the MSM tool. Does it have the .ops file included over 2gb
Click to expand...
Click to collapse
It was the zipped file and has Guacamole_21_O.07_190512.ops which is over 2kb
Installed the drivers but could not get it working
Phone on its way to one plus repair shop in Poland to get checked and repaired hopefully and will come back non rooted and with Android 11 installed
Now hopefully they can fix it but think I will leave it as is with Android 11 until possible TWRP and new roms come on board for Android 11 dont want to feck it up more
Thanks for the help
Hi, I badly needed help on my phone it is having bootloop, I just can't find any reliable source on how to fix it. It's a Realme C12, the phone keeps rebooting it cant access recovery I think its software is corrupted or deleted. It cant perform the Volume down+power button combination
lupin98 said:
Hi, I badly needed help on my phone it is having bootloop, I just can't find any reliable source on how to fix it. It's a Realme C12, the phone keeps rebooting it cant access recovery I think its software is corrupted or deleted. It cant perform the Volume down+power button combination
Click to expand...
Click to collapse
Since your device is in boot looping without ability to enter recovery, try if you can boot into fastboot mode by hard-keys. If it is, then just flash the stock boot image ( from which build ur device is currently on ). If it's not, then u must use SP Flash Tool to force flash the factory images into your device to fix bootloop. Try and inform back the situation!
LinhBT said:
Since your device is in boot looping without ability to enter recovery, try if you can boot into fastboot mode by hard-keys. If it is, then just flash the stock boot image ( from which build ur device is currently on ). If it's not, then u must use SP Flash Tool to force flash the factory images into your device to fix bootloop. Try and inform back the situation!
Click to expand...
Click to collapse
hello sir, I've tried using SP flash tool yet my laptop doesn't detect the phone, its been rebooting for a while now but the download process is still not starting.
I can only see the realme logo, and the phrase which says Orange State, then after that the phone will reboot again and shows that it is in > RECOVERY MODE, then it loops again.
LinhBT said:
Since your device is in boot looping without ability to enter recovery, try if you can boot into fastboot mode by hard-keys. If it is, then just flash the stock boot image ( from which build ur device is currently on ). If it's not, then u must use SP Flash Tool to force flash the factory images into your device to fix bootloop. Try and inform back the situation!
Click to expand...
Click to collapse
Can you help me sir? It's my only phone right now can't afford to buy a new one, I'm still a student.
lupin98 said:
Can you help me sir? It's my only phone right now can't afford to buy a new one, I'm still a student.
Click to expand...
Click to collapse
Inbox me
lupin98 said:
Can you help me sir? It's my only phone right now can't afford to buy a new one, I'm still a student.
Click to expand...
Click to collapse
Can you help me I have the same promblem
undersnde32 said:
Can you help me I have the same promblem
Click to expand...
Click to collapse
I guess you bad quoted the guy that had troubles, we don´t know if he found a fix though.
Better describe your exact issue, but also note that there are many posts/threads in Realme forum giving some solutions for bricked devices.
My oneplus 6 after the latest android 11 update recently crashed it reboots automatically without entering to the OS and shows QUALCOMM DumpCrash Mode there are still some data i didn't backup yet. is there any way to back up my data
-usb debugging not turned on
Did you ever manage to boot after applying the update? Or did it go straight into crash dump mode?
agent_07 said:
My oneplus 6 after the latest android 11 update recently crashed it reboots automatically without entering to the OS and shows QUALCOMM DumpCrash Mode there are still some data i didn't backup yet. is there any way to back up my data
-usb debugging not turned on
Click to expand...
Click to collapse
Flash stock recovery first from Fastboot . And do not wipe anything. Just reinstall OOS and boot. That should help.
[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates
As OnePlus doesn't always provide download links for all of for their Oxygen OS ROMs & OTA update zips, we mirrored them on AndroidFileHost and put the links in one post so that they're easy to find. This is not a support thread for issues you...
forum.xda-developers.com
facing the same issue yesterday updated to android 11 , after boot went into crash dump mode , tried n number of msm tools . not able to boot it up, i can boot to fastboot mode though
MoresM said:
Did you ever manage to boot after applying the update? Or did it go straight into crash dump mode?
Click to expand...
Click to collapse
yes after update it was fine for a week
MITHUN7888 said:
facing the same issue yesterday updated to android 11 , after boot went into crash dump mode , tried n number of msm tools . not able to boot it up, i can boot to fastboot mode though
Click to expand...
Click to collapse
if you found any was pls inform me
MITHUN7888 said:
facing the same issue yesterday updated to android 11 , after boot went into crash dump mode , tried n number of msm tools . not able to boot it up, i can boot to fastboot mode though
Click to expand...
Click to collapse
If you flash old TWRP on Android 11 it will go to Crash Dump Mode. Suggest doing a clean install of Android 11 or use Nebrassy TWRP and reinstall OOS11. Other TWRP's have already been repacked to latest version to carter Android 11.
agent_07 said:
if you found any was pls inform me
Click to expand...
Click to collapse
i tried nearly 10-15 msm tools all were success but when booted up same message " Qualcomm crash dump mode" the thing is my bootloader was locked . i couldn't flash twrp or flash fastboot rom's to revive my phone...gave my device to oneplus authorized service center they said i need to get my motherboard replaced which costs 24,050 for 256gb variant.. currently i have asked them to replace the motherboard , as motherboard for my variant was not available i need to wait 10 more days to get it fixed .
UPDATE: if u have ur bootloader unlocked search for how to get out of qualcomm crash dump mode using fastboot roms.
if not look out for a local mobile repair center which does chip level repairs and ask them to reball ur phone ram and cpu, theres a 50/50 chance ur device might boot up.
mm_rajesh said:
If you flash old TWRP on Android 11 it will go to Crash Dump Mode. Suggest doing a clean install of Android 11 or use Nebrassy TWRP and reinstall OOS11. Other TWRP's have already been repacked to latest version to carter Android 11.
Click to expand...
Click to collapse
my device bootloader was locked , had no twrp installed , after updating to os11 directly went into crash dump mode .
MITHUN7888 said:
my device bootloader was locked , had no twrp installed , after updating to os11 directly went into crash dump mode .
Click to expand...
Click to collapse
I don't know who is that Mahaaan who said it's a Motherboard fault. Crash Dump Mode is an error while loading with the Firmware. This can be fixed with MSM tools. Try this step if you cannot fix with MSM tool.
Safe Mode Procedure :
Hold the Power Button Until Android Starts to Boot Up.
As Soon as Android Starts Booting Up, Let Go of the Power Button.
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons.
Continue Holding Both Volume Buttons Until Android is Fully Booted.
If successful, backup your phone, and do a full factory Erase All Data reset of Android.
See if that helps.
like many even i too ugraged my op6 to oo11.1.1.1, rooted was running well for a week till i encountred face crash dump mode error
Stupid thing i did was instead of flashing fastboot oos 10.3.8 i tried to flash msm 10.3.8 which didnt solve crash dum and also locked my BL.
now nonof the msm could solve crash dump nor we can unlock BL bz we cant toggle OEM in Dev option,
i discussed with @L0ND0NB0Y regarding this, his suggestion would be to take a backup of oos10.3.8 config partation of a working rom, then use edl to flash it on affected op6, by that way we can unlock bootloader and flash fastboot rom.
we need to fide a working op6 and back config which @L0ND0NB0Y can guide us. if it works he ll creat a post to solve crashbump and BL locked issue.
if this wont work, we may need to wait for msm oos11 file.
update : managed to solve crash dump by flashing msm international 5.1.5 but ended up getting black screen with white notification light, if my op6 had BL unlocked all i had to do is to boot stock/twrp recovery and factory wipe.
How to resolve the issue . I got the same issue 1 week after SW upgrade . Nothing is fixing the issue
Jagadish-ravi said:
update : managed to solve crash dump by flashing msm international 5.1.5 but ended up getting black screen with white notification light, if my op6 had BL unlocked all i had to do is to boot stock/twrp recovery and factory wipe.
Click to expand...
Click to collapse
exactly describes what I have encountered the last few days. MSMDownloadTool works fine for 5.1.5, 5.1.11, 9.0.8, 10.3.0 and 10.3.8 (10.3.0 and 10.3.8 with new driver, ends in crash dump where I startet). Currently no solution in sight?
I have the strong feeling this error is correlated with the update to android 11. Going back to a previous recovery.img might initiate the qualcomm crashdump mode error on boot.
Seems to be worth a try to restore android 11 via MSMDownloadTool. Did not find a file for that. Anyone?
Another way out of the horror seems to be getting get unlock ability to 1.
https://forum.xda-developers.com/t/...stuck-in-fastboot-mode.4135563/#post-83153239
Last case is to modify the devcfg binary and flip the lock bit and reflash through EDL
Click to expand...
Click to collapse
I've got no idea on how to do that. Anyone?
I've contacted OP support. They answered i should send the phone in for repair.
Currently I am issuing a repair order.
My oneplus went to crashdump mode on Oct 21st... Really shocked to see many users reporting this issue.. Tried to revive it using msm tool , but ended up with crashdump mode even after successful flashing
I also got the same issue , the funny thing is i was still on android 10 , i havent even updated to android 11 .
cpr437 said:
I also got the same issue , the funny thing is i was still on android 10 , i havent even updated to android 11 .
Click to expand...
Click to collapse
That is some terrible news. I thought I'd be able to keep safe from this nonsense by staying on 10.
even in bootloader unlocked state its same
I brought op6 motherboard which had OOS 11 running.
I tried to downgrade to oos10 via fast boot, gave crash dump.
flashing other versions fastboot rom gave same error again n again
can't boot twrp, stock recovery non works,
flashing recovery stock or twrp gave "no such partation error"
next I would try reballing ram my old MB try n see if it works.
or should wait for OOS11 MSM flash file.
Update: OnePlus charges 307,67€ for the repair of their own fault. Game over for the phone and OnePlus. We will both change the manufacturer.
cpr437 said:
I also got the same issue , the funny thing is i was still on android 10 , i havent even updated to android 11 .
Click to expand...
Click to collapse
Same here bro.. My phone was on stock android 10...
Hello everyone,
I'm in a loop, I've been trying to solve it for five days, any help will be apreciate.
I have an SM-g930F in boot loop and I need to save the data that I have on it.
I'm trying to install TWRP through Odin, but when I try to do it, the Blocked by FAP message appears. (On the S7 screen)
I don't have access to developer options, because the phone is in a boot loop, I can only enter in Download Mode (Odin Mode), Recovery doesn't work either.
All this happened after uninstalling the secure folder, the phone freeze and it didn't start up correctly again, it stayed in a boot loop trying to start up in recovery. (#fail to open recovery_cause)
I tried to flash the latest firmware with ODIN but it gave me FAIL with hidden.img
After that, the mobile only started in Emergency recovery and in Download Mode (Odin Mode). Also after this, the phone was discharged and the battery stopped charging. I can only use it if it is connected to the wall or via USB.
At this moment I have found the solution to the FAIL of the hidden.img in firmware (it seems to be the .lz4 format) but I am afraid of flashing in Odin without having a battery.
I have also tried with a wireless charger and it still does not charge.
Could I install the firmware via USB while charging with the wireless charger? Or is it very risky?
My idea was to restore the recovery with TWRP through Odin, to be able to charge the battery and then install all the firmware again with Odin, but as I have mentioned the problem is that in the development options I do not have the OEM enabled (Also I have looked for how to enable it through ADB, but I think it is not possible because the device needs to be running).
Another possibility, although it doesn't make me very happy, would be to change the battery, and try to install the firmware in Odin. (But sometimes the new ones also come with little charge)
Finally there is the possibility to use Smart Switch PC to restore it to factory, but that would erase all the data.
Does anyone know what I can do to fix this? Any help would be appreciated.
Thank you
I think the problem with the hidden.img is that some files are corrupted.
Use the following tool do Download the firmware straight from Samsung Servers :
Releases · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Than go to download mode and let the phone plugged. Flash the files with odin.
Try at first with the home csc and see if you can boot to safe your data.
If not you have to use normal csc which will erase your data and bring the phone to factory state. Unfortunately i see no other solution for you.
Thats why you should always do a backup of your files. I had to learn it the hard way too.
USB power should be enough to run and flash the firmware through odin. Just dont disconnect the phone while flashing.
Edit: make sure to use always the latest version of odin which is if remember correctly 13.14.1:
Samsung Odin - Root Android download page for one click root
Samsung odin download - Root android and oneclickroot for flash / install custom ROM with one click root method
odindownload.com
Thank you very much for your answer.
Is it really safe to do the flashing without any battery? I have always read somewhere that you have to have a minimum of 50%. I'm afraid that later I won't be able to flash again.
On the other hand, I had an idea, but I don't know if it's possible or if it's safe to do it. Could I just install the straight firmware recovery.img from Samsung Servers? That is, extract the recovery.img from AP and then flash only the recovery.img in Odin on AP? (I don't know if it could be a problem to flash a stock recovery from another different stock firmware)
In recovery mode the phone should charge and I imagine that installing recovery.img will be faster in Odin.
Thanks again
Logeate said:
Thank you very much for your answer.
Is it really safe to do the flashing without any battery? I have always read somewhere that you have to have a minimum of 50%. I'm afraid that later I won't be able to flash again.
On the other hand, I had an idea, but I don't know if it's possible or if it's safe to do it. Could I just install the straight firmware recovery.img from Samsung Servers? That is, extract the recovery.img from AP and then flash only the recovery.img in Odin on AP? (I don't know if it could be a problem to flash a stock recovery from another different stock firmware)
In recovery mode the phone should charge and I imagine that installing recovery.img will be faster in Odin.
Thanks again
Click to expand...
Click to collapse
It is risky but unless you diconnect the phone during odin flash it should not turn off normally.
You need a .tar file to install a recovery through odin.
All right.
But from what I've read it would be possible to unzip the AP (and in this case remove the rest of the files leaving only the recovery.img), then compress again with 7zip and flash with Odin. It is right?
Although what scares me the most is that there is a problem flashing only the recovery.img of two different firmwares, could that create a conflict?
Thank you very much.
Logeate said:
All right.
But from what I've read it would be possible to unzip the AP (and in this case remove the rest of the files leaving only the recovery.img), then compress again with 7zip and flash with Odin. It is right?
Although what scares me the most is that there is a problem flashing only the recovery.img of two different firmwares, could that create a conflict?
Thank you very much.
Click to expand...
Click to collapse
I did not try it and cant tell you if it will work. Guess you have too try and see what happens.
All right, I'll see what i do.
Thank you very much.
Well, here's the update.
I managed to solve it, the mobile already works.
I share the solution in case someone else can use it as a reference.
It has worked for me, that does not mean that it will work for you, because using Odin with low battery is risky.
The solution was reinstall the recovery.img that I had previously extracted from the stock firmware.
After that, the device has restarted and automatically started charging the battery, which was effectively completely discharged.
All the problem came for a failure in the recovery.
So, installing the recovery.img needs 4 seconds, so although it is risky to flash with zero battery, it is very fast and so it is a good solution.
After the phone updated Android (also the applications) started keeping all the applications and data, which was what I wanted.
In brief:
Download the official firmware from Samsung of your device, from Sammobile, Frija, etc. (Make sure it is the exact version of your phone)
Unzip the AP with Winrar
Open the folder and copy recovery.img
Compress the recovery.img file in .tar format with the 7-Zip compressor
Download the latest version of Odin.
Connect the phone via USB and put it in Odin mode. Make sure the phone is stable and can last for a long time with the USB cable.
Flash recovery.tar in the AP tab
It only takes 4 seconds.
That's all, the phone recharges the battery in recovery mode. When turned on, it updates and restarts itself.
In my case it was not necessary to do anything else, the phone worked fine. You can also (of course after charging the battery) flash all firmware (or install TWRP) in Odin as usual.
That's all, thanks for your help aarem, Regards.