I've unfortunately soft-bricked my mobile phone (aforementioned model).
The cell is in constant bootloop. I've tried flashing many firmwares but to no avail as preloader restricts its formatting and re-downloading (shows s_bram error). Therefore, if any of you guys using the same version of "CUN-U29" with custom recovery image and rooted your cell phone, please send me a backup of your device with the custom recovery image file that you are using. Please can you help me fix this problem.
Related
Hi everyone,
I am having issues with this phone of mine. Here is a background of it:
My phone is rooted and is running rayglobe rom. I tried updating the update that it gave me and made me stuck in bootloop.
Now I downloaded another rom, which I don't remember since this happened december 2013. after flashing, it does not boot and does not make me go to TWRP anymore. Now I tried using download mode to restore my phone. but eveytime I try to flash (using the 2 methods I saw in the thread), either it hangs at 49% or the other one does not start flashing because it says I have inconsistent dll? I downloaded a D802 stock rom and tried flashing via download mode and it says that I have different model (F380K). Now I tried downloading a dll and F380K stock rom, but won't allow me because it says that my phone is D802. But when I go to download mode it is korean and it says F380K.
I think I have flashed a korean rom before which made this incident happen, but do you have any idea how I can restore this?
Thank you all in advance.
If this was me, I would do a factory reset.
sounds like you should go back to stock firmware.
http://forum.xda-developers.com/showthread.php?t=2432476
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=xxxxxxxxxxxxxxxxxx<YOUR IMEI NO.
First check what exactly phone model in Internet Browser. Then download TOT and flash back to stock.
xaneybert said:
Hi everyone,
I am having issues with this phone of mine. Here is a background of it:
My phone is rooted and is running rayglobe rom. I tried updating the update that it gave me and made me stuck in bootloop.
Now I downloaded another rom, which I don't remember since this happened december 2013. after flashing, it does not boot and does not make me go to TWRP anymore. Now I tried using download mode to restore my phone. but eveytime I try to flash (using the 2 methods I saw in the thread), either it hangs at 49% or the other one does not start flashing because it says I have inconsistent dll? I downloaded a D802 stock rom and tried flashing via download mode and it says that I have different model (F380K). Now I tried downloading a dll and F380K stock rom, but won't allow me because it says that my phone is D802. But when I go to download mode it is korean and it says F380K.
I think I have flashed a korean rom before which made this incident happen, but do you have any idea how I can restore this?
Thank you all in advance.
Click to expand...
Click to collapse
I faced similar problem with D800. I had the correct dll and the firmware but it failed saying my phone model was different (I think its because I tried the "upgrade recovery" option on the LG PC software by selecting a different model).
My phone was passing the LG screen and stuck at android boot screen.
What I did:
Pushed a kitkat based rom for D800 to sdcard using adb on Linux (on windows adb failed to recognise the device).
Then adb reboot recovery and flashed the rom.
Then I was able to flash the factory image.
Hi all, im really hoping someone can help, and that what ive done is reversible.
After rooting I tried installing the alliance rom (lollipop) on my n610f, i got a boot loop so restored the backup rom using CWM without any problems, i read on the alliance rom page that id need a different bootloader and modem, i got what i thought were the correct one and put them on using odin, did a wipe and tried again, same bootloop. Except this time when i restore the backup rom i still have the same boot loop.
If anyone has a fix for this id be eternally grateful.
Fixed it by flashing N910FXXU1B OB4 [Lollipop 5.0.1] bootloader and modem
What did you flash? Modem or bootloader..? I think the best solution is, flash stock firmware via odin, then try again.
I own a Canadian S 4. I used TWRP to try and flash CM 13 and followed instructions as to how to do it. I also made a backup with TWRP. After trying many things to eliminate the boot loop, I am still left with the boot loop as I cannot get the recovery to load or anything else. Help!. I have tried all the suggested methods to try and cure the boot loop. I have also tried flashing the original ROM, and that will not work either. Lost as to what to do at this point.
Do you get any Odin error messages when flashing the stock ROM? Where did you get the stock ROM? You have an i337m?
I understand @audit13 questions... and I've used Oden... but may I suggest Samsung Kies emergency firmware recovery from a computer which i have also used but can't remember the differences between Kies and Oden..
Depending on the firmware on the phone Kies may not be supported. Smartswitch replaced Kies.
Hello, so I have a Y625-U21 which had a bootloop issue, I couldn't boot it to recovery in order to wipe data, so I downloaded a random firmware, flashed it via Lenovo flasher, and now it's completly offline, but somehow it still has connection with the pc, i tried several others firmwares but they didn't work, I read an artical about OTA ( FullOTA-MF: Full OTA MF firmware is Full package of firmware and it can unbrick your phone model with any buid number.), is this possible? if so how can I do it, or at least how can install a costum rom on it in this state? or boot it in recovery? any help that this phone may has is much appreciated.
Ps: I can provide its imei or its S/N if that would help.
I have tried flashing it with different files but still no result. Flash is successful but still stuck. Tried installing twrp and custom rom but still no result. Apparently it didn't install anything on data folder or anywhere.
Can anyone help me?
hello, maybe you need to download the official firmware with the current binary of your phone, if you know it, and try to reflash