Database Info

I've bricked my phone? I am unable to go to recovery mode! It is in reset loop! :v

I had installed xposed with some popular modules like Android L theme, Greenify, Gravity Box and ifont.
Today I wanted to unroot my phone (due to some reasons) so I just unchecked all modules from XPOSED modules list and restarted the mobile. After restarting I wanted to reset my phone so I went to reset my phone and then the **** happened.
Now it goes to reset screen (for 2 seconds) then in logo screen (for 3 seconds), then again in reset screen (for 2 seconds) and again logo (for 3 seconds) and again reset screen..... it is in boot loop!!! but this boot loop is extra ordinary :v
So after waiting for some time I realized that I have done something wrong so I decided to remove the battery and then turn on the phone but still same problem.
I have backup of my phone so when I wanted to go to recovery mode I couldn't.
Whenever I press volume up/down (both) keys with power button it again goes to that reset screen loop (instead of opening recovery mode). So please tell me a way to fix this problem.
Any help will be appreciated!
My mobile is "Qmobile Noir i9".
*Its specs are: "click here to see the specs"
**I was using stock rom.
***I have cwm backup in my computer.

ToXiC said:
I had installed xposed with some popular modules like Android L theme, Greenify, Gravity Box and ifont.
Today I wanted to unroot my phone (due to some reasons) so I just unchecked all modules from XPOSED modules list and restarted the mobile. After restarting I wanted to reset my phone so I went to reset my phone and then the **** happened.
Now it goes to reset screen (for 2 seconds) then in logo screen (for 3 seconds), then again in reset screen (for 2 seconds) and again logo (for 3 seconds) and again reset screen..... it is in boot loop!!! but this boot loop is extra ordinary :v
So after waiting for some time I realized that I have done something wrong so I decided to remove the battery and then turn on the phone but still same problem.
I have backup of my phone so when I wanted to go to recovery mode I couldn't.
Whenever I press volume up/down (both) keys with power button it again goes to that reset screen loop (instead of opening recovery mode). So please tell me a way to fix this problem.
Any help will be appreciated!
My mobile is "Qmobile Noir i9".
*Its specs are: "click here to see the specs"
**I was using stock rom.
***I have cwm backup in my computer.
Click to expand...
Click to collapse
I Think This Will Solve your Problem
Flash this Rom Via Flash Tool
Rom Link : click Here
How To Use Flash Tool : Click Here
Cheers

ok I fixed the problem.
I turned off the device for two hours (the battery was removed too). After two hours I removed sd card and sim card and then turned on the device. The device turned on successfully!!!
The only problem I am facing now is xposed modules are still installed. The phone is reset successfully but modules are not uninstalled. My phone still have new font (which i changed with xposed), new boot animation!
I will now install the modules again and then uninstall them. I hope it'll work!

And the scatter file link is not working in the blog (the link you gave above)....

Qmobilei9 bricked
My qmobile i9 stucked at start screnn i tried to flash the same rom already installed ...but it stucked in the meddle and flashtool shows error Memory not found any help??/ the phone is totally dead now it does not respond to any key ....but it connects to my pc and the after a few seconds disconnects and so on ...:crying

Bricked!

After installing blisspop (or I don't really remember), I realized that WiFi wasn't working and neither was bluetooth so I decided to flash Extended Stock Kernel kernel, first with flashing the boot, then flashing the zip from recovery mode and even after that, the result was the same. It didn't work. Later on I went to the Phantom kernel's page and flashed that without checking that the kernel was meant for 4.4 and it bricked my device. Now, whenever the phone starts, it shows the Phantom kernel boot at start with its logo without any led light appearing below and due to that I'm unable to go into either flashmode or fastboot. It keeps restarting the Phantom boot at start and doesn't go any further. Please help!
EDIT: A more detailed version that I wrote a few months ago to the kernel's developer.
-
Previously I had my Xperia L reset on stock ftp then flashed the Extended Stock Kernel on it. Since the wifi wasn't working, I tried to download R17 and flashed it through CWM and now the phone keeps restarting on the Phantom Logo. It shows the logo, waits for about 10 seconds then restarts and the same keeps repeating. I saw it was for Kitkat but then too I insisted on installing. I can't access neither bootloader nor recovery mode. The light which comes when the Phantom Logo pops doesn't appear either. Can you help me please? Anything would be greatly appreciated. I know I did a stupid thing but I really don't want to give up on this device.
-

Xephor_EX said:
After installing blisspop (or I don't really remember), I realized that WiFi wasn't working and neither was bluetooth so I decided to flash Extended Stock Kernel kernel, first with flashing the boot, then flashing the zip from recovery mode and even after that, the result was the same. It didn't work. Later on I went to the Phantom kernel's page and flashed that without checking that the kernel was meant for 4.4 and it bricked my device. Now, whenever the phone starts, it shows the Phantom kernel boot at start with its logo without any led light appearing below and due to that I'm unable to go into either flashmode or fastboot. It keeps restarting the Phantom boot at start and doesn't go any further. Please help!
EDIT: A more detailed version that I wrote a few months ago to the kernel's developer.
-
Previously I had my Xperia L reset on stock ftp then flashed the Extended Stock Kernel on it. Since the wifi wasn't working, I tried to download R17 and flashed it through CWM and now the phone keeps restarting on the Phantom Logo. It shows the logo, waits for about 10 seconds then restarts and the same keeps repeating. I saw it was for Kitkat but then too I insisted on installing. I can't access neither bootloader nor recovery mode. The light which comes when the Phantom Logo pops doesn't appear either. Can you help me please? Anything would be greatly appreciated. I know I did a stupid thing but I really don't want to give up on this device.
-
Click to expand...
Click to collapse
yea.... output battery... reinput it.... DONT TOUCH POWERBUTTON.... holf vol - and connevt to pc
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
yea.... output battery... reinput it.... DONT TOUCH POWERBUTTON.... holf vol - and connevt to pc
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
-
It worked, I flashed the generic ftf and everything's okay. Thank you so much!
-

My Xperia E3 doesn't start !

Hello,
This morning turning my phone on, everything worked, until the error messages like "com.snapchat.android process suddenly stopped" (I have received several of this) including one which bugged my phone: "the prossessus Xperia ™ 11 has stopped working" (the two "1" appeared like the™).
There I received messages that appeared and stood out immediately: I could not use my phone: I reboot. And here's the problem:
My phone is on and stays blocked on the first boot screen (Sony).
My phone is rooted since 8 months, and when it starts, it does not even reach the violet LED: so i'm unable to access the Recovery Mode.
When it charges it's the same: it remains stuck at the boot screen plus a red LED usual for chargings, and when I unplug the screen is still on with red LED indefinitely.
To turn it off (for not stay on all the time), I push with a pencil lead into the notch "off" (at the back of the phone on the left of the SD card)
The worst: When I try to connect my phone into fastboot mode or flashmode, the LED (blue or green) lights, but Flashtool doesn't recognize the device. When I unplug the device, the LED (blue or green) is still lighting. So I cannot flash (which I wanted to do) with Flashtool.
So I think it's a problem because the phone hangs at the beginning of the boot, maybe it's a bootloop, or a hardbrick (?).
This problem appeared like that, I think having done anything weird lately. The phone is one year and a half.
It's very difficult for me because I can not do anything that is in my possession and I greatly needed.
Anyone have a solution for this? Its very important.
Thank you so much !
PS : Very sorry for my english

Same problem i have facing more than 10-15 work stopped i try to install new rom but keel facing this problem but my phone enter in recovery mod but hangs on boot animation

hey there,, i m experiencing the same problem...flashtool doesnt detects my xperia too....but there is a fix for your phone..if u have not unlocked the bootloader then download sony pc companion and then try repairing your phone with it..**THIS WILL DELETE ALL DATA...or if u want to use flashtool then check and install the drivers for your xperia...!!HOPE THIS WORKS....
hit th thx button if it worked..

Z3 Bootloop

Hello there. I own a Z3 model D6603. It is unlocked bootloader and Before it had got the bootloop i had Lineage OS 16 custom rom installed on it (Android 9). I was watching some videos on chrome and then the phone heated a little and then restarted. I thouhgt it was maybe some sort of instability but then it started just bootlooping.
Current Status right now is :
Once connected to pc goes to flash mode.
I can get it to fastboot.
When connected to charger just goes into endless bootloop where only SONY logo appears and then quickly restarts
In attempt to fix it I flashed stock FTF using multiple versions of Flashtool which was fruitless. I also Tried with EMMA but nothing helped still. And then after looking I think it might be damaged TA and I've seen so many say that if that's the case then the phone is bricked forever unless you have had a backup from a previous working state which I actually do. The problem is that I don't know how to flash this TA back since the phone doesn't boot to restore it through ADB. I saw that S1tool works with older devices and doesn't work with Z3 models so I wonder if there is a way to fix this. Thank you for your time.
PS : My power button doesn't work I used to use fastboot to boot it when necessary

Issues of that kind may be a hint for a dead battery, this should be ruled out first. Note: In that case your phone might not boot even if connected to a charger!
After that is ruled out, one should try to install LineageOS 16 or later following the official installation routine from scratch.

J700F Black Screen

Hello, what could be the cause of the black screen? I can manage to boot it up to recovery mode(TWRP) but after a few seconds it goes into black screen. Same goes after seeing the samsung logo. I can't seem to boot into odin mode as I tried multiple times it only shows the samsung logo and then boots into samsung logo again. I also tried connecting it into the computer but the device won't show up even though I unlocked the oem. When charging it shows the battery indicator fine. It shows error on the upper left: Custom Binary blocked by frp lock. what can I possibly do to make it work again? Thanks! It's on custom rom: onkiller-os v2.0 final and custom recovery: twrp 3.4.0.

The oem Unlocking gets enabled sometimes if your battery runs out.
try flashing the stock rom again, it can help sometimes. it happened once to me as well. My phone died once bcuz the battery ran out and somehow oem unlocking got reenabled

Ahmed9193 said:
The oem Unlocking gets enabled sometimes if your battery runs out.
try flashing the stock rom again, it can help sometimes. it happened once to me as well. My phone died once bcuz the battery ran out and somehow oem unlocking got reenabled
Click to expand...
Click to collapse
Thanks for the reply. ah, But the oem is enabled and can I flash the stock rom without accessing odin mode? I can't seem to boot into it.

Boot into download mode, by pressing power, home and volume down button
Try that