Phone "bricked"?? [CM7] - Defy General

So here is what happened...
I am on the 2.2.2 Nordic sbf and Installed CM7 5.1 on it...
I used it for now 1 week.
But when the phone was booting, the green LED appeared while the Red M was displayed (due to the 2nd-init)
But I accidentally removed the battery at this moment and now my phone don't want to boot anymore........
I tried to reboot again but it was in a boot loop....
Then I wiped data by stock recovery and when I reboot,
It stays on the Red M logo and nothing......
I tried everything!
Go to system recovery and wipe data
Went to Custom Recovery and Restore
Re-installed the fixed Nordic sbf...
STILL NO LUCK :"(((((((((((((((((((
Please help me guys.....
please....
I'm gonna cry if it's bricked...
EDIT: Flashed 3.4.3-11 it boots but stuck in a boot loop... :'(

WIIstpM said:
So here is what happened...
I am on the 2.2.2 Nordic sbf and Installed CM7 5.1 on it...
I used it for now 1 week.
But when the phone was booting, the green LED appeared while the Red M was displayed (due to the 2nd-init)
But I accidentally removed the battery at this moment and now my phone don't want to boot anymore........
I tried to reboot again but it was in a boot loop....
Then I wiped data by stock recovery and when I reboot,
It stays on the Red M logo and nothing......
I tried everything!
Go to system recovery and wipe data
Went to Custom Recovery and Restore
Re-installed the fixed Nordic sbf...
STILL NO LUCK :"(((((((((((((((((((
Please help me guys.....
please....
I'm gonna cry if it's bricked...
Click to expand...
Click to collapse
Did you reinstalled it with RSD Lite?

AkkiandDefy said:
Did you reinstalled it with RSD Lite?
Click to expand...
Click to collapse
Yes I reinstalled Nordic sbf with RSD Lite but didn't work....
Now I tried with the 3.4.3-11 One and it Boot with the Blur animation but it's STILL in a boot loop :'(( :\ ....

WIIstpM said:
Yes I reinstalled Nordic sbf with RSD Lite but didn't work....
Now I tried with the 3.4.3-11 One and it Boot with the Blur animation but it's STILL in a boot loop :'(( :\ ....
Click to expand...
Click to collapse
Sorry for off-topic but at this point I would cry, too

AkkiandDefy said:
Sorry for off-topic but at this point I would cry, too
Click to expand...
Click to collapse
what do you mean............
Is it bricked then?................

WIIstpM said:
what do you mean............
Is it bricked then?................
Click to expand...
Click to collapse
I would say, yes
but it could be that somebody has a way to make it functional again.
PS.: I would post this to the Defy Development topic, because the activity there is muuuch higher.

AkkiandDefy said:
I would say, yes
but it could be that somebody has a way to make it functional again.
PS.: I would post this to the Defy Development topic, because the activity there is muuuch higher.
Click to expand...
Click to collapse
Gosh it Booted FINALLY!!
I went to system recovery and wiped data again... Phew... I was about to commit suicide... lol
I wonder If I can still go to Nordic again and install CM7....

Did you wipe date/factory reset in stock recovery?
Edit: ok, glad to got it back
What did you do to make it work?
Just a question when you flashed as example the 3.43.11 Rom , did the M-Logo appear??

spryte said:
i had a similar problem, but i wasn't able to flash my device any more.
Try to wipe and afterwards install beta 5.0, for me it worked.
Otherwise try this rom and flash it. This is the one i use as base rom.
Finally, as long as you are still able to power up your phone with the charger it should be possible to find a solution for your problem.
Click to expand...
Click to collapse
What do you mean by flash?? a SBF or a ROM??
What happened when you tried to flash another??
Phew... I'm so relieved now... I'm now definitely more careful with my phone!!

WIIstpM said:
Gosh it Booted FINALLY!!
I went to system recovery and wiped data again... Phew... I was about to commit suicide... lol
I wonder If I can still go to Nordic again and install CM7....
Click to expand...
Click to collapse
When it boots and gets stuck in a bootloop the phone is not, and I repeat, NOT bricked. Apparently there was clearly a software problem but as long as the device turns on, the display works and you manage to get to the bootloader then there is very little need to worry. So you know for the next time: suppress your panic, breathe and just keep trying.
Even when the screen doesn't turn on it isn't necessarily a bricked phone. This happened to me a few months ago because I was so stupid to flash an older sbf. It turned out that the device actually still functioned up to the bootloader. RSD lite detected the phone and I managed to revive it completely by flashing the original sbf. The Defy really is almost unbrickable mostly thanks to the locked bootloader, a blessing in disguise.

AgentSmith said:
When it boots and gets stuck in a bootloop the phone is not, and I repeat, NOT bricked. Apparently there was clearly a software problem but as long as the device turns on, the display works and you manage to get to the bootloader then there is very little need to worry. So you know for the next time: suppress your panic, breathe and just keep trying.
Even when the screen doesn't turn on it isn't necessarily a bricked phone. This happened to me a few months ago because I was so stupid to flash an older sbf. It turned out that the device actually still functioned up to the bootloader. RSD lite detected the phone and I managed to revive it completely by flashing the original sbf. The Defy really is almost unbrickable mostly thanks to the locked bootloader, a blessing in disguise.
Click to expand...
Click to collapse
The same I asked, if he saw the M-Logo because then it's normal that it needs more time (5-10 minutes)

AkkiandDefy said:
Did you wipe date/factory reset in stock recovery?
Edit: ok, glad to got it back
What did you do to make it work?
Just a question when you flashed as example the 3.43.11 Rom , did the M-Logo appear??
Click to expand...
Click to collapse
Yes everything appeared as normal (white M-logo though)..
When I flashed 3.4.3-11 I got a boot loop then I went to system recovery and wipe Data and it works again..
Do you know if I still can flash other sbf or rom??
I want to go back to CM7... I also have a CWM backup but I'm afraid to restore this...

WIIstpM said:
Yes everything appeared as normal (white M-logo though)..
When I flashed 3.4.3-11 I got a boot loop then I went to system recovery and wipe Data and it works again..
Do you know if I still can flash other sbf or rom??
I want to go back to CM7... I also have a CWM backup but I'm afraid to restore this...
Click to expand...
Click to collapse
Then it maybe wasn't a bootloop, because if you flash a new sbf, its normal that it can take 10 minutes to boot

AgentSmith said:
When it boots and gets stuck in a bootloop the phone is not, and I repeat, NOT bricked. Apparently there was clearly a software problem but as long as the device turns on, the display works and you manage to get to the bootloader then there is very little need to worry. So you know for the next time: suppress your panic, breathe and just keep trying.
Even when the screen doesn't turn on it isn't necessarily a bricked phone. This happened to me a few months ago because I was so stupid to flash an older sbf. It turned out that the device actually still functioned up to the bootloader. RSD lite detected the phone and I managed to revive it completely by flashing the original sbf. The Defy really is almost unbrickable mostly thanks to the locked bootloader, a blessing in disguise.
Click to expand...
Click to collapse
lol I panicked because I tried almost everything!
weird bootloop (after M-logo, black screen)
bootloader -> didn't work
custom recovery -> didn't work
stock recovery -> didn't work
CWM Backup -> didn't work
Different sbf -> bootloop
Finally Stock recovery again -> worked!

hi, i have a similar problem to yours (i made my own thread about it and still no ideas) but RSD Lite doesn't discover my phone, it just doesn't appear there. How can i try to make it appear in RSD LitE? My prhone also doesnt load the system, just hangs in Motorola logo moment. I can go to recovery and boot menu etc...
please help me, i feel like crying as well.... (

AkkiandDefy said:
Then it maybe wasn't a bootloop, because if you flash a new sbf, its normal that it can take 10 minutes to boot
Click to expand...
Click to collapse
no it was, after some minutes the animations froze and it started all other again. the first few secs of booting are laggy as it used to, and it repeated..

your_login said:
hi, i have a similar problem to yours (i made my own thread about it and still no ideas) but RSD Lite doesn't discover my phone, it just doesn't appear there. How can i try to make it appear in RSD LitE? My prhone also doesnt load the system, just hangs in Motorola logo moment. I can go to recovery and boot menu etc...
please help me, i feel like crying as well.... (
Click to expand...
Click to collapse
Install the drivers
You will ask where to download them?
Google it
Click to expand...
Click to collapse

@AkkiandDefy
@spryte
@AgentSmith
THANK YOU FOR EVERYTHING!!
You were quick, helpful, and helped me to stay calm
Really I thank you!
:")
But could you please help @your_login too??
He got more severe problems than me apparently...

WIIstpM said:
@AkkiandDefy
@spryte
@AgentSmith
THANK YOU FOR EVERYTHING!!
You were quick, helpful, and helped me to stay calm
Really I thank you!
:")
But could you please help @your_login too??
He got more severe problems than me apparently...
Click to expand...
Click to collapse
He just need to install the Moto-Drivers, and RSD-Lite will recognize it

AkkiandDefy said:
He just need to install the Moto-Drivers, and RSD-Lite will recognize it
Click to expand...
Click to collapse
I have the drivers already installed, i managed to flash the nordic sbf a few days ago without any problem maybe its my computers fault that it fails to see the phone now..? i reainstalled them anyway and still no luck. However, i forgot to mention it earleier - when i connect a turned off phone via usb to my computer the phone itself turns on, hangs at motorola logo and on my computer i can hear 'device plugged' sound and MotoHelper windows appears on my computer, so it is being recognised to some extent. However, in RSD Lite there is still no device in the list and i can't try with flashing another sbf ((((

Related

[Q] CM7 upgrade help

Hi all.
I'm really sorry if this has been covered before - I've searched but found nothing specific, and I'm at work just to make it trickier.
I was on T-Mobile UK stock ROM until lunchtime today, at which point I followed the instructions from this thread to upgrade to CM7 RC0. Following the upgrade, I used Titanium backup to restore my apps and data. Everything looks okay, but I keep getting random force closes for android.process.media. Can somebody please help me with this - it seems to come up when I try to change any sound option, but also in the market when loading my apps.
Factory reset
something u restored from ur stock apps backup is messing with ur current settings .i recommend u to factory reset and then install apps carefully (only user apps) dont go and even try those system apps ...
I'm no advance user yet.. but hey we both got cm7 at same day day and same time ..
i'm just learning ..if u still need help i'll be glad to help
I might have made it very much worse
after reading a bit more, I opted for clearing my cache in recovery mode... that made it worse, leaving me stuck at the M logo. Other posts pointed me in the direction of reflashing the SBF file and starting again, but this left me with a looping MotoBlur animation after flashing the sbf. recovery mode is now not getting past the ! triangle.
My phone appears to be a brick, and I know I've just done something stupid. Is there anyone who can offer any advice? Please?
simon211175 said:
I might have made it very much worse
after reading a bit more, I opted for clearing my cache in recovery mode... that made it worse, leaving me stuck at the M logo. Other posts pointed me in the direction of reflashing the SBF file and starting again, but this left me with a looping MotoBlur animation after flashing the sbf. recovery mode is now not getting past the ! triangle.
My phone appears to be a brick, and I know I've just done something stupid. Is there anyone who can offer any advice? Please?
Click to expand...
Click to collapse
Flash sbf a clean stock sbf and if the phone works then reply here ..'ll guide u further
simon211175 said:
recovery mode is now not getting past the ! triangle.
Click to expand...
Click to collapse
OK when you see the ! triangle to get into the recovery menu you need to press the volume up button & volume down button at the same time (this is for froyo 2.2 - if still on eclair 2.1 then just touch the bottom right hand of the screen) then you will access the recovery menu.
From there you can do a factory reset & then hopefully it should boot up OK.
Just beware that your battery may be getting low on charge & this makes it a bit trickier but not impossible.
Thanks. I figured out the volume buttons to access the recovery menu, managed to re flash the sbf file, then left it to reload cm7 in the morning. Thanks for all your help, panic mode is neither my favourite, nor my best.
simon211175 said:
Thanks. I figured out the volume buttons to access the recovery menu, managed to re flash the sbf file, then left it to reload cm7 in the morning. Thanks for all your help, panic mode is neither my favourite, nor my best.
Click to expand...
Click to collapse
I had the *exact* same issue over the weekend. Was able to fix it by following the installation instructions again. Glad you got your phone working again too, I know I'll be very careful with TB in the future.
But... Does anyone know why a (simple?) cache wipe gets you stuck at the M logo (2ndInit still works, but nothing after that)

[Q] Ramdump and Boot loop error > Pls help !

Hello,
Yesterday, I buy my new i8150 Galaxy Wonder and i root my phone
I install the rom Black Notes Chapter 2 with ClockworkMod.
I used V6 Supercharger with scrip manager.
After the restart everything worked normally and I just installed Viber app.
Being tired, I have not verified if the scrip was properly installed
I go to bed and getting up several hours later, my i8150 galaxy displays a black screen with
RAMDUMP mode
<null>
I will restart my phone and there's only the Samsung logo that flashes every second.
No more access to Clockwormod, the logo flashes too.
The only thing I know to do is put it into Download Mode or RAMDUMP Mode > cause: force upload
So I try flashed an original rom (W I8150XXKK1 Galaxy (EUR)) into Download Mode with Odin Multi Downloader v4.43.
Every step is going well, but when it restarts automatically at the end of the process, the Samsung logo blinking again.
I also tried to reinstall ClockworkMod with Odin Multi Downloader, but still the stage proceeds successfully, always the same problem of flashing samsung logo on startup and no access to ClockworkMod
Help me please, it's been over 5 hours I'm looking for a solution.
THANK YOU
I'm not completely new to android, I trained for over a year with my ZTE Blade with different Rom (CyanogenMod)
(My text is translated with google, my maternal language is French. I understand English, but do not know much to write)
Please post in appropiatte section
Thread moved
Sent from my GT-P1000 using Tapatalk
Oh2.. This is interesting r u sure no access to CWM ? If possible best to wipe all system folder making the phone fully wiped.
Have you tried to flash stock recovery ?
Sent from my GT-I8150 using xda premium
I tried so many different ways to repair my Galaxy W, that I totally bricked ...
Thank you anyway, I tried the after sale service, but I have hopes that I can exchange :-(
johndfl said:
I tried so many different ways to repair my Galaxy W, that I totally bricked ...
Thank you anyway, I tried the after sale service, but I have hopes that I can exchange :-(
Click to expand...
Click to collapse
Just doing independent research
From 1:10 wonder has this problem...
No kidding, but the characteristic for the phone that possible have a boot loop are always have FORCE CLOSE app and doing RESTART itself
It can fixed but only if we get stock firmware with wipe and boot loader to fix this issue
I will bring this issue to new tread
Im having this problem too. Any solutions for it.
Used perfectly for a day and 2nd day when i woke up the samsung logo keeps flashing..
Rio Saputro said:
Just doing independent research
From 1:10 wonder has this problem...
No kidding, but the characteristic for the phone that possible have a boot loop are always have FORCE CLOSE app and doing RESTART itself
It can fixed but only if we get stock firmware with wipe and boot loader to fix this issue
I will bring this issue to new tread
Click to expand...
Click to collapse
This is EXACTLY what happened yesterday..and just now I wiped everything in the phone and turned it on. It worked first, but there was a FC on the start or something..and the screen goes black. But I notice that I'm still in the custom ROM I was using (GingerICE). Then I turned it off and and went to CWM. I tried reboot system now, but I was stuck in the samsung logo. Can someone help?
I have the backup of the stock ROM. Is it safe to make the backup?
needya said:
This is EXACTLY what happened yesterday..and just now I wiped everything in the phone and turned it on. It worked first, but there was a FC on the start or something..and the screen goes black. But I notice that I'm still in the custom ROM I was using (GingerICE). Then I turned it off and and went to CWM. I tried reboot system now, but I was stuck in the samsung logo. Can someone help?
I have the backup of the stock ROM. Is it safe to make the backup?
Click to expand...
Click to collapse
if you could boot into Recovery screen, you could try:
wipe factory/system, wipe cache, advanced > wipe dalvik.
[careful] i usually format my /system if i get bootloops.
then reflash the ROM. reboot.. in my cases, those steps always worked.
edit: you should checkout the GingerICE with non OC version, the OC may work on some device and some don't, IMO if you're using your droid for daily use, i recommend using the non OC
im facing same issue too here... but i couldn't even access to download mode... tried many times, still failed... help plss...
Same thing happen to me ...today. I can get into download mode, but after flash the with odin it is still the same, boot loop on samsung logo.... help !!!
can you get to recovery mode?
follow my steps 3 post before this post
Hi..
If you can't go to recovery mode
Go to this tread..
http://forum.xda-developers.com/showthread.php?t=1506765
It not discuss about fixing but i want the user be aware of this issue
Regards
Twiq said:
can you get to recovery mode?
follow my steps 3 post before this post
Click to expand...
Click to collapse
No.. I can't.... only download mode
sgilmans said:
No.. I can't.... only download mode
Click to expand...
Click to collapse
Most probably it won't work but try to flash only the stock recovery, than give it a try(recovery mode).
Instruction and files (Scroll down to Other)
greets
THE-E
Check out Rio's thread above!!!!
You nay need to return under warranty!!
Unfortunately!!
Sent from my SGW GT-I8150 using Tapatalk!!
sgilmans said:
No.. I can't.... only download mode
Click to expand...
Click to collapse
hi, im just try bringing the idea , search the thread usb jig solution .it might help to hard reset ... .peace

[Q] R800X Boot Loop ~ HELP!!

I have a R800X (Xperia Play) Rooted, without an unlocked bootloader. I had noticed that quite a few apps were crashing, so i tried opening ROM manager to run a permissions fix. However it crashed too, so i turned my phone off to reboot it. When i tried to turn it back on, it was stuck in a bootloop. Going from the " Sony" Screen to the "android" screen, going black, then repeating. I've tried flashing 2.3.3 back on using Flashtool, but i had no luck. I really need help ASAP!! Thanks
Bcaraway14 said:
I have a R800X (Xperia Play) Rooted, without an unlocked bootloader. I had noticed that quite a few apps were crashing, so i tried opening ROM manager to run a permissions fix. However it crashed too, so i turned my phone off to reboot it. When i tried to turn it back on, it was stuck in a bootloop. Going from the " Sony" Screen to the "android" screen, going black, then repeating. I've tried flashing 2.3.3 back on using Flashtool, but i had no luck. I really need help ASAP!! Thanks
Click to expand...
Click to collapse
Hope you've got CWM... in that case... restore from a NANDroid backup... it's a possible solution, to be honest I don't know any other... probably there some other solutions out there.
TheDjNeo said:
Hope you've got CWM... in that case... restore from a NANDroid backup... it's a possible solution, to be honest I don't know any other... probably there some other solutions out there.
Click to expand...
Click to collapse
I have a backup on my SD, But this phone is not able to boot into recovery, albeit it does not have one. What is Nandroid?
Uhhh
Nevermind! I tried flashing again, i wiped data this time, and after a few boots it worked!
except argraG (lol, recaptcha string)
Bcaraway14 said:
I have a backup on my SD, But this phone is not able to boot into recovery, albeit it does not have one. What is Nandroid?
Click to expand...
Click to collapse
1.- CWM (Clock Work Mod) is a recovery menu for doing lots of things...
2.- One of those things are FULL Bakcups called NANDriod backups
3.- With a NANDroid you can fully restore your phone... It's equivalnt to flashing a fresh firmware + titanium (for apps and data)
you should try to install CWM... if your phone don't boot up you can try on booting time... but could be dangerous... your phone is not bricked... so try flashing fresh firm again. If fails again... tell me the whole output of flashtools (or whatever you use to flash).
EDIT: -_-' Just posted... when noticed your answer... It took me some time to write this...
EDIT2: LOL put reCaptcha string... on title XD
TheDjNeo said:
1.- CWM (Clock Work Mod) is a recovery menu for doing lots of things...
Click to expand...
Click to collapse
As far as I know, there is not a compatible version for the R800X, instead you have to use the general version. Since my phone can unlock its bootloader for some reason, the recovery for it wont work. Unless im Confused on which clockwork we're talking about here.
Bcaraway14 said:
As far as I know, there is not a compatible version for the R800X, instead you have to use the general version. Since my phone can unlock its bootloader for some reason, the recovery for it wont work. Unless im Confused on which clockwork we're talking about here.
Click to expand...
Click to collapse
Install CWM.
After a restart continually press the volume down button to enter recovery

Xperia arc S Ultimate HD 3.0.1 HARD BRICK WON'T BOOT WON'T CONNECT

Hello everyone. I know that before I should create a thread I should search the site more to see if there are similar threads. I have but unfortunately I've only found a few with no solutions.
This is about my phone which I flashed Ultimate HD 3.0.2 last June(mid). Everything was going well. I didn't have to restart my phone as much as when I had cyanogenmod. Last Sunday while trying to take a photo my phone died because of low battery. When I got home I charged it but would only get stuck at the Sony logo. To sum it up.
- When turned on/charged, the arc s would only get stuck at the Sony logo(no red LED light). The screen would get brighter, then dimmer, then blank, then go back to the Sony logo. I 'd gladly boot to CWM but nothing happens no matter what button I press. (Maybe I'm doing it wrong? No one clearly knows how to boot into bloody CWM. Almost everyone seems to say, errrr keep pressing back/menu/volume down/power after the Sony logo appears. If someone could clear it up on how to really boot into CWM, that would be great thanks)
- Tried Flashtool, PC companion, SEUS, but the phone also seems to have connectivity problems with the pc. It would slightly detect it then disconnect again. I try to flash a different kernel using Flashtool, the phone's LED turns blue(clearly indicating that it's in fastboot mode), but when I select a kernel, flashtool claims that I have to be in fastboot mode even when my phone's LED is blue.
I can't use any of the 3 tools(SEUS, PC, Flashtool) because it can't even be detected by the pc.(BTW I've fully charged the battery using an independent charger)
I fear this is a hardware problem but I hope it can be fixed. I'd really appreciate help. I've missed college to fix my phone just like I have before but this one won't budge. Thanks.
Flash the stock firmware manually
nrupareliya said:
Flash the stock firmware manually
Click to expand...
Click to collapse
How would he do that, if he clearly said
I can't use any of the 3 tools(SEUS, PC, Flashtool) because it can't even be detected by the pc.(BTW I've fully charged the battery using an independent charger)
Click to expand...
Click to collapse
To OP: Does the phone go into flashmode or fastboot mode? Do you have the drivers installed properly?
bryangld27 said:
Almost everyone seems to say, errrr keep pressing back/menu/volume down/power after the Sony logo appears. If someone could clear it up on how to really boot into CWM, that would be great thanks
Click to expand...
Click to collapse
From my experience, if you install CWM on a rooted phone but with a locked bootloader it uninstalls as soon as you flash a new ROM and you have to reinstall CWM over again every time you do so.
skaveelicious said:
From my experience, if you install CWM on a rooted phone but with a locked bootloader it uninstalls as soon as you flash a new ROM and you have to reinstall CWM over again every time you do so.
Click to expand...
Click to collapse
Not exactly uninstall, the CWM for locked bootloader is installed on /system partition. This partition is wiped every time a new ROM is flashed, therefore removing CWM from your phone.
僕のLT18iから送られてきた
skaveelicious said:
From my experience, if you install CWM on a rooted phone but with a locked bootloader it uninstalls as soon as you flash a new ROM and you have to reinstall CWM over again every time you do so.
Click to expand...
Click to collapse
popthosegaskets said:
Not exactly uninstall, the CWM for locked bootloader is installed on /system partition. This partition is wiped every time a new ROM is flashed, therefore removing CWM from your phone.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Some (if not most) ROMs, which are available for locked bootloaders, also include recovery already on the /system partition. At least I have seen custom recovery files listed in AROMA installation files for locked bootloader options.
I have not tested it myself (the freedom of unlocked bootloader ), so I am not sure though

Probably hard bricked my K420n using service menu

So, like in the topic, I were using 'service menu'. Everything was good, until I found 'AAT' option. When I entered it, notification appered: Press ok to enter AAT. Phone will reboot. So I pressed ok, on down message appered: 'enter AAT' and phone have rebooted. From now, phone didn't want to boot, it was stuck at LG logo. I wasn't really worried, because I knew I had a backup of system and data in case something worng happened. I entered TWRP and restored everything BUT system still didn't want to boot. I tried to restore second backup (without Xposed) but same result. Now I started to worry that I killed my phone.
Also phone still goes into download mode but I think that PC doesn't detect it because I hear only characteristic Windows 10 plug in sound and nothing more. So what do I supose to do now?
Also what is AAT? And why it killed whole system
Krystiannnnnn said:
So, like in the topic, I were using 'service menu'. Everything was good, until I found 'AAT' option. When I entered it, notification appered: Press ok to enter AAT. Phone will reboot. So I pressed ok, on down message appered: 'enter AAT' and phone have rebooted. From now, phone didn't want to boot, it was stuck at LG logo. I wasn't really worried, because I knew I had a backup of system and data in case something worng happened. I entered TWRP and restored everything BUT system still didn't want to boot. I tried to restore second backup (without Xposed) but same result. Now I started to worry that I killed my phone.
Also phone still goes into download mode but I think that PC doesn't detect it because I hear only characteristic Windows 10 plug in sound and nothing more. So what do I supose to do now?
Also what is AAT? And why it killed whole system
Click to expand...
Click to collapse
It shouldn't happen though
Try to flash the firmware again in download mode.
Krystiannnnnn said:
So, like in the topic, I were using 'service menu'. Everything was good, until I found 'AAT' option. When I entered it, notification appered: Press ok to enter AAT. Phone will reboot. So I pressed ok, on down message appered: 'enter AAT' and phone have rebooted. From now, phone didn't want to boot, it was stuck at LG logo. I wasn't really worried, because I knew I had a backup of system and data in case something worng happened. I entered TWRP and restored everything BUT system still didn't want to boot. I tried to restore second backup (without Xposed) but same result. Now I started to worry that I killed my phone.
Also phone still goes into download mode but I think that PC doesn't detect it because I hear only characteristic Windows 10 plug in sound and nothing more. So what do I supose to do now?
Also what is AAT? And why it killed whole system
Click to expand...
Click to collapse
Are you sure LG Drivers well installed? They might not have been and that's why your device isn't recognized. If your device gets recognized while it's in download mode, you can try these guides:
LG Bridge: https://forum.xda-developers.com/lg-k10/how-to/guide-unbricking-flashing-firmware-due-t3380529
LG UP: https://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839
Finally, after 5 hour tough battle with my phone, I made it to boot up.
thx for help xd
Krystiannnnnn said:
Finally, after 5 hour tough battle with my phone, I made it to boot up.
thx for help xd
Click to expand...
Click to collapse
Ciao bro, how did you solved that, I did the same mistake and now have the same problem
dioariete said:
Ciao bro, how did you solved that, I did the same mistake and now have the same problem
Click to expand...
Click to collapse
Flash ROM 5.1.1 (for me (K420n), flashing ROM 6.0 didn't work - I had to update to 6.0 earlier) until phone boots up. I think that I used this ROM: https://forum.xda-developers.com/lg-k10/development/stock-versions-model-lg-k10-t3457319
You can also try to recover/flash via TWRP but this method didn't work for me.
Krystiannnnnn said:
Flash ROM 5.1.1 (for me (K420n), flashing ROM 6.0 didn't work - I had to update to 6.0 earlier) until phone boots up. I think that I used this ROM: https://forum.xda-developers.com/lg-k10/development/stock-versions-model-lg-k10-t3457319
You can also try to recover/flash via TWRP but this method didn't work for me.
Click to expand...
Click to collapse
Thank you bro, you helped me solve the problem :good: . Have a nice day !

Categories

Resources