Database Info

Weird question about emergeny mode

Hello to everyone and respect to all you developers for your hard work!
as you can see i'm noob but i'll try not to be too noobish.
here's the situation.. now, i have hephappy's CM9 bluepill rom installed in my lg p500 and it works just perfect (i mean it,just perfect),
and before that i have flashed custom rom's couple of times with success but once when i tried to boot into emergency mode (vol down+back+power) after that i couldn't get rid of that yellow message every time i restarted or turn on my phone till today.
so, now i'm living with that issue,but it bothers me,i can't understand why yellow emergency screen is showing EVERY time i reboot my mobile.
then i find out that the only way to avoid that is pulling battery out and wait for at least 5 minutes and then switch on (then it's ok - LG logo and blah blah).
but when i try to turn it on for less than 5 mins, emergeny mode will be showing everytime i switched mobile on.
so, i don't have a clue or answer what it could be. i tried to flash stock firmware through KDZ and actually everything seems ok and everything works just fine but that yellow screen still spy on me.
as i said, everything works perfect but when battery is drained or i wanna reboot my mobile i have emergency mode shown,so i must repeat above procedure with pulling out battery for 5 mins everytime.
i hope i didn't complicate this

Try to change RADIO (BASEBAND),maybe it might help you!
Sent from my LG-P500 using xda premium

totalka said:
Hello to everyone and respect to all you developers for your hard work!
as you can see i'm noob but i'll try not to be too noobish.
here's the situation.. now, i have hephappy's CM9 bluepill rom installed in my lg p500 and it works just perfect (i mean it,just perfect),
and before that i have flashed custom rom's couple of times with success but once when i tried to boot into emergency mode (vol down+back+power) after that i couldn't get rid of that yellow message every time i restarted or turn on my phone till today.
so, now i'm living with that issue,but it bothers me,i can't understand why yellow emergency screen is showing EVERY time i reboot my mobile.
then i find out that the only way to avoid that is pulling battery out and wait for at least 5 minutes and then switch on (then it's ok - LG logo and blah blah).
but when i try to turn it on for less than 5 mins, emergeny mode will be showing everytime i switched mobile on.
so, i don't have a clue or answer what it could be. i tried to flash stock firmware through KDZ and actually everything seems ok and everything works just fine but that yellow screen still spy on me.
as i said, everything works perfect but when battery is drained or i wanna reboot my mobile i have emergency mode shown,so i must repeat above procedure with pulling out battery for 5 mins everytime.
i hope i didn't complicate this
Click to expand...
Click to collapse
your not noobish. you post in the right place.
I have like no idea what you are expierencing. have you tried booting to recovery?

-DarkKnight- said:
your not noobish. you post in the right place.
I have like no idea what you are expierencing. have you tried booting to recovery?
Click to expand...
Click to collapse
yes pal. everything i can remember including booting into recovery with clockworkmod, wiping all data,cache,update with kdz,then root,flash new rom...and everytime everything goes like a glowe,everything is stable,with no errors.
i suppose i'm one of the luckiest lg p500 users when it's about good,stable device,which could be overclocked or tweaked without kernel panic,errors, etc (i heard that differences between same devices can vary).
BUT after all that i have that same issue with yellow emergency mode.
finally, i suppose that yellow screen is the price i must pay at the cost of good stability and great performance

did you try flashing gb stock rom by lgmdp?

totalka said:
yes pal. everything i can remember including booting into recovery with clockworkmod, wiping all data,cache,update with kdz,then root,flash new rom...and everytime everything goes like a glowe,everything is stable,with no errors.
i suppose i'm one of the luckiest lg p500 users when it's about good,stable device,which could be overclocked or tweaked without kernel panic,errors, etc (i heard that differences between same devices can vary).
BUT after all that i have that same issue with yellow emergency mode.
finally, i suppose that yellow screen is the price i must pay at the cost of good stability and great performance
Click to expand...
Click to collapse
If you can get into yellow screen your ok
Last resort use kdz just don't take out battery or disconnect and you should be fine
Sent from the My Little Pony Official App

@dhruv:
I heard about lgmdp,but i didn't found myself interested enough to try it
Because i actualy didn't had any issues excep that yellow screen.so you think it could be helpful?
@darkknight:
It is the only way i can avoid yellow screen by pulling out battery for 5 mins.
I know that my prob is unusal but now i have a lot of apps installed linked with link2sd,so i should find some way to safely backup all that stuff and try to do smtg.
Sent from my LG-P500 using xda app-developers app

totalka said:
yes pal. everything i can remember including booting into recovery with clockworkmod, wiping all data,cache,update with kdz,then root,flash new rom...and everytime everything goes like a glowe,everything is stable,with no errors.
i suppose i'm one of the luckiest lg p500 users when it's about good,stable device,which could be overclocked or tweaked without kernel panic,errors, etc (i heard that differences between same devices can vary).
BUT after all that i have that same issue with yellow emergency mode.
finally, i suppose that yellow screen is the price i must pay at the cost of good stability and great performance
Click to expand...
Click to collapse
I didnt get the method of flashing rom.. what you said above!!
You root again after updating from kdz.. you have gone wrong somewhere thats why you
get emergency mode everytime you restart.
I would suggest.. clear all the links.. make a nandroid backup. Dont use kdz as its not
required. Go into recovery.. clean everything (specially boot) and flash any rom and see if the problem persists.

which rom and which recovery maybe you can try and change the recovery. I wont reccomend kdz because i flashed it 10-12 times but after that i bricked my phone 2 times while flashing with kdz.

Here it is..
I had official gingerbread used when i found out that cm9 ics was out.then i have wait for stable cm9 rom,till hephappy's premature version.
So,i decided to flash premature,so here is a short procedure..
I don't have exact rooting/flashing guide link right now but i found it on xda forums for p500.
Downloaded short fuse,adb,etc and root via usb & command prompt..everything was ok,device sucesfully rooted,i got superuser.
Next step i installed rom manager from google play and follow flash instructions from xda including nandroid backup,booting to recovery,wiping data,dalvik,battery,everything that could be wiped..then installed premature,gapps,everything goes just fine.
I have been using premature till bluepill cames out.
just before flashing new rom i decided to hard reset via vol up+home+power, but i accidently entered into emergency mode by pressing vol down+back+power instead and after that yellow showing i have issue with it.
Downloaded then stock ginger rom from xda sites (20g),installed via kdz,everything flows fine,rooted againg with same procedure,flashed bluepill rom too with same procedure and still having that yellow emergency mode issue.
I think i made it much more clear
Sent from my LG-P500 using xda app-developers app

Weird Softbrick/Bootlooping!

Hey guys, I need your help.
My phone was all ok when I slept last night! (I have Purumod v3) I wake up in the morning and the phone was off. when I switched it on,it started bootlooping!(shows only samsung logo)
I tried reflashing it,but the bootlooping seems to persist EVEN when im trying to use the recovery(after the flash when I need to wipe data).If I go to recovery,just when Im about to reach the "wipe all data",it switches off and reboots. I thought its a hardware problem but there is one thing that goes against it ie., the phone does NOT show this behaviour when its in Download mode. when Im in download mode,it doesnt reboot or switch off or anything.
I tried going back to stock(a froyo rom without bootloader) but problem still remains. Tried flashing many different custom roms,still remains the same.
Any idea? Reinstalled Kies drivers and everything. Please help.

Have you tried flashing another kernel or reflashing your current one?
Since the kernel handles boot and recovery while download mode is on a lower level.

myozeus said:
Hey guys, I need your help.
My phone was all ok when I slept last night! (I have Purumod v3) I wake up in the morning and the phone was off. when I switched it on,it started bootlooping!(shows only samsung logo)
I tried reflashing it,but the bootlooping seems to persist EVEN when im trying to use the recovery(after the flash when I need to wipe data).If I go to recovery,just when Im about to reach the "wipe all data",it switches off and reboots. I thought its a hardware problem but there is one thing that goes against it ie., the phone does NOT show this behaviour when its in Download mode. when Im in download mode,it doesnt reboot or switch off or anything.
I tried going back to stock(a froyo rom without bootloader) but problem still remains. Tried flashing many different custom roms,still remains the same.
Any idea? Reinstalled Kies drivers and everything. Please help.
Click to expand...
Click to collapse
Try to find something called "zero fill tar" I think Hillbeast made? its like a deep cleanser, if it is a firmware issue, this should help. flash it then flash any rom over it.

Try flashing this tar file. It's saved my phone many times and here is the file that ava.tar is talking about. For the second file, you have to extract it and you get a .tar file that you flash through odin. :good:

I tried each of the things in your replies. I tried the 0kb file,did nothing,tried the zero fill followed by flashing Kyrillos Rom (froyo) still the same result(bootloop). Also flashed g3mod 2.4.1! this is just so annoying. Thanks so much for your help. I really hope my I could find a way.

Try flashing a rom with 'force upload mode' [vol up+home and power up]
Sent from my GT-I5800 using xda premium

myozeus said:
I tried each of the things in your replies. I tried the 0kb file,did nothing,tried the zero fill followed by flashing Kyrillos Rom (froyo) still the same result(bootloop). Also flashed g3mod 2.4.1! this is just so annoying. Thanks so much for your help. I really hope my I could find a way.
Click to expand...
Click to collapse
Try flashing the tar after flashing the rom, ie. flash it last

Hey guys,
I tried flashing in upload mode,doesnt make a difference.nor does flashing the zero fill tar AFTER flashing the rom!
Im sorry if Im being annoying but I'll try any options I can get!
Thanks again

myozeus said:
Hey guys,
I tried flashing in upload mode,doesnt make a difference.nor does flashing the zero fill tar AFTER flashing the rom!
Im sorry if Im being annoying but I'll try any options I can get!
Thanks again
Click to expand...
Click to collapse
Some more suggestions, which are not very likely (not in order of probability of success but in order of quickness), but it doesnt hurt to try
1. Try booting/ entering recivery while charging
2. Try removing sd card (and then sim card as well) then booting
3. Try flashing a stock rom (then try doing a factory reset from stock recovery)
4. If you know somebody with the same phone try using their battery and then booting.
(5. When you lose all hope try the russian/old school methdod, ie. beat it into complying to your wishes )

boot loop causes and hw to work around
hey
boot loops are a cause of ur kernal not working properly.....,try downloading a working kernal through odin........even i had boot loop problems with g3mod kernal.......but the ultra oc kernal 1260hr kernal works fine fr me........also try clearing the dalvik cache or cache partition..,..which usually solves stability problems nd its a must after flashing a kernal.......try flashing marcellusbe 7.2 rom.....which is very much stable u can also find a bunch of kêrnals try nt using the g3 mod kernal.... if all these dosent work take ur mob to the service center they wont flash it as u rooted ur mob bt they will suggest u to get new motherboard get it done and then u can start frm the beginning .......
HIT THE THANKS BUTTON IF HELPED DONT JUST SAU THANX

After flashing stock ics, phone dont boot, help please

first of all, sorry for my bad English, try to be as clear as possible
Accidentally i flash a rom in system 1 with bmm..... a warning appeared when I rebooted the phone
"bmm menu would not be available in the next reboot" then I went to the system keeper option and reinstall bmm ..... when i tried to reboot the phone the same message appeared on the screen again .... "bmm menu would not be ..."
then i decided to flash ics stock (as I always do when i have a problem) , i put the phone in ap FastBoot .. Select the firmware and started the rsd process
all ended well ... unplug the phone and restart
ohh surprise! ... The phone does not boot, i cant even see the motorola logo, the phone just stuck there
Additional detail: this is the first time i flash firmware after losing my cid
Can someone help me?
Thanks in advance

Boot by bp tool
Steps
1. Press power button ,vol+ & vol- simultaneously
2. Select bp tool here and it will boot.
Best of luck
Sent from my MB865 using XDA Premium 4 mobile app

Thanks mithun23, i will try that

I've tried that and it did not work ... now the phone reboots, shows the motorola logo and keeps restarting(bootlooping)
if i re flash the firmware with rsd, the procces finish well, but the phone do the boot loop again
i dont know what else i can do :crying:
I've been thinking about buying a nexus 4 ... maybe it's time to do it.

jualros said:
I've tried that and it did not work ... now the phone reboots, shows the motorola logo and keeps restarting(bootlooping)
if i re flash the firmware with rsd, the procces finish well, but the phone do the boot loop again
i dont know what else i can do :crying:
I've been thinking about buying a nexus 4 ... maybe it's time to do it.
Click to expand...
Click to collapse
Try Factory Reset and Clear Cache from Stock Recovery.

I've tried that too, but nothing happens ...
Again I clarify the symptoms:
Point 1 - When the phone starts, shows the motorola logo and the message "Error CustomerID Contact Dealer Boot to Suspend / MDCT mode: 0000:00000000:000000 cc.". Then the screen gets black and nothing happens
Point 2-If I turn on the phone by holding down the volume keys (+ / -) and the power button (boot mode selection menu) and select any of the options ... the screen goes black and nothing happens
Point 3 - If I turn on the phone by holding down the volume key (-) and the power button (ap fastboot flash mode) ... I can connect the phone, start and finish the flashing process correctly. When the process ends it happens again point 1 or point 2
It may be a hardware failure?

jualros said:
I've tried that too, but nothing happens ...
Again I clarify the symptoms:
Point 1 - When the phone starts, shows the motorola logo and the message "Error CustomerID Contact Dealer Boot to Suspend / MDCT mode: 0000:00000000:000000 cc.". Then the screen gets black and nothing happens
Point 2-If I turn on the phone by holding down the volume keys (+ / -) and the power button (boot mode selection menu) and select any of the options ... the screen goes black and nothing happens
Point 3 - If I turn on the phone by holding down the volume key (-) and the power button (ap fastboot flash mode) ... I can connect the phone, start and finish the flashing process correctly. When the process ends it happens again point 1 or point 2
It may be a hardware failure?
Click to expand...
Click to collapse
Last, but not the least, I hope you are using the correct FXZ file for your region?

EDIT
@mithun23
after flashing attempt number six:
I could enter the bp tools mode, the phone boot, and it works.What i can do in this mode?
Why I still can not boot normally?

XploitMachine said:
Last, but not the least, I hope you are using the correct FXZ file for your region?
Click to expand...
Click to collapse
I'm using the same FXZ file that I've always used (is not for my region, but always work for me with no issues)

jualros said:
EDIT
@mithun23
after flashing attempt number six:
I could enter the bp tools mode, the phone boot, and it works.What i can do in this mode?
Why I still can not boot normally?
Click to expand...
Click to collapse
Good man u booted...
Well since ur cid is lost u cannot boot normally..u can boot only using bp tool.
Install bmm from Google play..then u will be able to boot normally.
Sent from my MB865 using XDA Premium 4 mobile app

mithun23 said:
Good man u booted...
Well since ur cid is lost u cannot boot normally..u can boot only using bp tool.
Install bmm from Google play..then u will be able to boot normally.
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I installed bmm, but there is a problem ... boot menu manager requires root ...
when I try to root the phone, the process automatically restarts the phone and gets stuck on the motorola logo (since it no longer resets normally) ... then the root process can never be completed :crying:
I will continue doing more tests

when the phone starts normally, something similar to the root process of jelly bean leak happens ...
the method for jelly bean leak was something like this (the swapp method):
1 - the phone began in ap fastboot mode
2 - using a command line, the ics boot.img sends to the phone
3 - then the phone is unplugged from the usb cable and restarted
4 - the phone boots and gets a black screen
5 - plug the phone to the usb cable again and run the root tool for ics
5 - the phone restart 3 times (the root process is done)
6 - restart the phone in ap fast boot again
7 - using a command line, the jelly bean boot.img sends to the phone
8 - restart the phone and all is done
so....what is happening with my atrix 2 is something like step 4, is like boot.img is missing or corrupted

SOLVED : I boot using bp tools, then i found a root method that works , finally i get my phone rooted...so i've installed bmm and booted fine again....thx to those who takes the time to answer in this post
Sent from my MB865 using XDA Premium 4 mobile app

jualros said:
SOLVED : I boot using bp tools, then i found a root method that works , finally i get my phone rooted...so i've installed bmm and booted fine again....thx to those who takes the time to answer in this post
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which root method did u use ?
Sent from my MB865 using XDA Premium 4 mobile app

I download 2 scrips here in xda atrix 2 forum, 1 of those doesnt work (the process reboot the phone and get bootlooping), the other one works. I don't remember the post, but i can upload it and give you the link if you need it.
Sent from my MB865 using XDA Premium 4 mobile app

jualros said:
I download 2 scrips here in xda atrix 2 forum, 1 of those doesnt work (the process reboot the phone and get bootlooping), the other one works. I don't remember the post, but i can upload it and give you the link if you need it.
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
your phone att atrix 2 on 4.0.4, if so please post that link here so i can use it. im totally stucked with this 4.0.4

Golhaaboa said:
your phone att atrix 2 on 4.0.4, if so please post that link here so i can use it. im totally stucked with this 4.0.4
Click to expand...
Click to collapse
Were you asking him whether his device is att or not? I don't think so. Seems like he has been flashing jb leak on his. And were you asking for att ics fxz file? Sorry got confused for a while. Here you go. Be sure to choose the right one
http://sbf.droid-developers.org/phone.php?device=17

Heelpp..! BMM not appear, and the phone stayed restarting does nothing but nothing out of the motorola logo screen goes black for a minute and not start, should show BBM but no longer does, and prior to the reboot when installation is complete and I gave keeper system option "Install bmm to main system" not only told me BBM started after reboot and so did not know what to do now ..: S can not access the system 3 is where I have q my other system help please.. had stock 4.0.4 att in system 1 and LiquidSmooth v3.0 (4.4.2) in system 3 what can i do? I was trying to install on your system 1 LiquidSmooth 3.1 (4.4.3) step by step pls..

saga02 said:
Heelpp..! BMM not appear, and the phone stayed restarting does nothing but nothing out of the motorola logo screen goes black for a minute and not start, should show BBM but no longer does, and prior to the reboot when installation is complete and I gave keeper system option "Install bmm to main system" not only told me BBM started after reboot and so did not know what to do now ..: S can not access the system 3 is where I have q my other system help please.. had stock 4.0.4 att in system 1 and LiquidSmooth v3.0 (4.4.2) in system 3 what can i do? I was trying to install on your system 1 LiquidSmooth 3.1 (4.4.3) step by step pls..
Click to expand...
Click to collapse
If BMM is not appearing at startup, then FXZ is only option !!
FXZ (with your region)---->>root--->> install BMM---->> flash ROM.
Watch BMM video tutorial available in general section, for proper BMM usage

sameerm02 said:
If BMM is not appearing at startup, then FXZ is only option !!
FXZ (with your region)---->>root--->> install BMM---->> flash ROM.
Watch BMM video tutorial available in general section, for proper BMM usage
Click to expand...
Click to collapse
thank you ..! I resolved the problem already doing that

[100% WORKING] Un-Brick ANY ANDROID DEVICE EASILY !!!!!

100% Working method to UNBRICK ANY PHONE
PLEASE NOTE !!!!
THIS METHOD ONLY WORKS IF YOUR PHONE IS ABLE TO BOOT !!!!
IT SHOULD BE ABLE TO BOOT INTO RECOVERY !!!
ALSO NOTE- THIS ERASES ALL DATA ON PHONE.....
THIS WILL TEACH YOU TO BACKUP REGULARLY
THINGS REQUIRED !!!!
1) A BRICKED PHONE ABLE TO BOOT INTO RECOVERY....
2) {OBVIOUSLY} A BRAIN....
METHOD:
STEP-1: USING THE POWER BUTTON AND THE VOLUME-UP BUTTON, BOOT INTO RECOVERY...
(KEEP HOLDING VOLUME-UP UNTIL RECOVERY SHOWS UP)
STEP-2: WHEN YOU ARE IN THE STOCK RECOVERY, FAMILIARIZE YOURSELF WITH THE NAVIGATION AND SELECTION BUTTONS IN YOUR DEVICE.. (EITHER THE VOLUME-UP OR POWER BUTTON...)
STEP-3: SELECT DELETE CACHE OPTION AND CLICK YES....
STEP-4: SELECT THE FACTORY RESET OPTION AND CLICK YES IN THE OPTIONS....
STEP-5:CLICK THE "REBOOT-NOW" OPTION TO REBOOT INTO A BRAND NEW DEVICE WITH YOUR STOCK ROM !!!!!!
P.S IF YOUR DEVICE WAS STUCK DURING "UPDATING GAPPS" DURING ROOTING, YOUR PHONE WILL BE ROOTED WHEN YOU BOOT !!!!!
THIS IS A VERY EASY WAY TO UNBRICK ANY ANDROID DEVICE !!!!!
THIS MAY NOT WORK ON A FEW DEVICES ..... I REALLY DONT KNOW BUT IT PRACTICALLY SEEMS POSSIBLE TO UNBRICK ANY DEVICE...
EDIT
After a few people mentioned that this method can only be used while using a stock rom....
i kinda thought about it and realized it.....
Sorry for this, but this will work on devices running stock roms......
IF THIS WORKED PLZZZ HIT THE THANKS :good: BUTTON !!!!!!

Btw you are a kid if a person has made changes to rom or bricked while making changes while making changes to rom it gonna do nothing as factory reset only deletes all user data it gonna un brick if you bricked it while using xposed module or something like that so remove this non sense post
Sent from my Andi 3.5KKe+ using XDA Premium 4 mobile app

prashantdrew said:
Btw you are a kid if a person has made changes to rom or bricked while making changes while making changes to rom it gonna do nothing as factory reset only deletes all user data it gonna un brick if you bricked it while using xposed module or something like that so remove this non sense post
Sent from my Andi 3.5KKe+ using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And you have to have a working Stock Rom on your device

Phone isn't bricked if it works under the listed requirements though

Android phone stuck on installation / Android guy mode after factory reset.

My Micromax Canvas Spark q380 was stuck on logo screen after something bad happened during charging. So I did a factory reset from recovery screen but now it keeps showing some installation mode with that android guy. After 10 mins or so phone switches off automatically and on restarting that installation screen keeps coming up. I tried vol +/- but unable to go into even recovery.
Battery is nonremovable. Phone is not rooted.
I am not geek so plz explain in detailed.

no one?!

Biker Biker said:
My Micromax Canvas Spark q380 was stuck on logo screen after something bad happened during charging. So I did a factory reset from recovery screen but now it keeps showing some installation mode with that android guy. After 10 mins or so phone switches off automatically and on restarting that installation screen keeps coming up. I tried vol +/- but unable to go into even recovery.
Battery is nonremovable. Phone is not rooted.
I am not geek so plz explain in detailed.
Click to expand...
Click to collapse
Do a Google search for:
"Unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk

I found a couple links showing to flash stock rom on Micromax Canvas Spark but they looked fake so I went to service center and the guy there flashed the rom (not sure what he did) and reported that it did not worked and will have to change the hardware
Any suggestions?

Biker Biker said:
I found a couple links showing to flash stock rom on Micromax Canvas Spark but they looked fake so I went to service center and the guy there flashed the rom (not sure what he did) and reported that it did not worked and will have to change the hardware
Any suggestions?
Click to expand...
Click to collapse
Who knows, you didn't state the condition of the device after the service center flashed it.
Does the device have any signs of life, does it do anything, does it respond any kind of way, does it connect to PC, does it charge when connected, does the LED come on when connected? Anything at all?
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Who knows, you didn't state the condition of the device after the service center flashed it.
Does the device have any signs of life, does it do anything, does it respond any kind of way, does it connect to PC, does it charge when connected, does the LED come on when connected? Anything at all?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Oh sorry to forgot mention about it.
The mobile is still in same condition (see pic in 1st post) wherein that green android guy keeps moving its antenna relentlessly.
So after I came home from service centre I tried to flash is myself (I choose Download only mode in sp flash tool). After flash the mobile tried to start up and showed that mobile is encrypting but it got switched off soon after. So I charged it for some time and switched on. Than it showed that since the encrypting process was interrupted, the mobile needs to reset so I clicked on reset.
Next I got same screen (with that android guy running) but with "Erasing" written at bottom. And after some time stock recovery screen appeared. Then I selected Reboot from there and on start up the mobile again went into that screen with android guy.
Now I think I will flash again in "firmware upgrade" (will it make any difference?) mode. But waiting for battery to drain out. Another problem is my battery is non-removable. So maybe it switches on while flashing?
Any thoughts?

Biker Biker said:
Oh sorry to forgot mention about it.
The mobile is still in same condition (see pic in 1st post) wherein that green android guy keeps moving its antenna relentlessly.
So after I came home from service centre I tried to flash is myself (I choose Download only mode in sp flash tool). After flash the mobile tried to start up and showed that mobile is encrypting but it got switched off soon after. So I charged it for some time and switched on. Than it showed that since the encrypting process was interrupted, the mobile needs to reset so I clicked on reset.
Next I got same screen (with that android guy running) but with "Erasing" written at bottom. And after some time stock recovery screen appeared. Then I selected Reboot from there and on start up the mobile again went into that screen with android guy.
Now I think I will flash again in "firmware upgrade" (will it make any difference?) mode. But waiting for battery to drain out. Another problem is my battery is non-removable. So maybe it switches on while flashing?
Any thoughts?
Click to expand...
Click to collapse
Yikes, it's never good when a device powers down during flashing or during first boot after flashing.
Seems to me that you might have hardware issues now since the service center couldn't revive it. You might need to replace the motherboard. Trying to recover it with software tools is probably just gonna be a wild goose chase and will probably end with things being worse which will lead to replacing the motherboard anyway so just save yourself the headache and go straight for replacing it.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Yikes, it's never good when a device powers down during flashing or during first boot after flashing.
Seems to me that you might have hardware issues now since the service center couldn't revive it. You might need to replace the motherboard. Trying to recover it with software tools is probably just gonna be a wild goose chase and will probably end with things being worse which will lead to replacing the motherboard anyway so just save yourself the headache and go straight for replacing it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I think the service center guy was lazy. He did not even bother to remove my battery or let it die (since its unremovable). He flashed with mobile on.
I again tried flashing with sp flash with "download only" option and it showed download successful at the end of flash. Before starting the mobile, I charged the battery fully and then the mobile started with "Encyrpting mobile...." and it got stuck at 229% (how can something be more than 100%? .. anyways) for some time and then it company logo screen appeared. I let be like that for few hrs but then nothing happened.
Do you think I should flash again? Does appearance of company logo screen indicate any hope?
I am sorry if it's too much of trouble... but replacing hardware will cost too much to me and am trying my best if I could make my mobile work..

Biker Biker said:
I think the service center guy was lazy. He did not even bother to remove my battery or let it die (since its unremovable). He flashed with mobile on.
I again tried flashing with sp flash with "download only" option and it showed download successful at the end of flash. Before starting the mobile, I charged the battery fully and then the mobile started with "Encyrpting mobile...." and it got stuck at 229% (how can something be more than 100%? .. anyways) for some time and then it company logo screen appeared. I let be like that for few hrs but then nothing happened.
Do you think I should flash again? Does appearance of company logo screen indicate any hope?
I am sorry if it's too much of trouble... but replacing hardware will cost too much to me and am trying my best if I could make my mobile work..
Click to expand...
Click to collapse
If it powers on and tries to boot and can get to flash mode then yeah, you can probably fix it. But without knowing what got corrupted, it won't be easy. It's gonna take trial and error between adb/fastboot, flash mode and flash tool, etc.. you can try flashing or pushing the individual .imgs form your stock firmware one at a time until whatever is corrupted gets replaced.

Droidriven said:
If it powers on and tries to boot and can get to flash mode then yeah, you can probably fix it. But without knowing what got corrupted, it won't be easy. It's gonna take trial and error between adb/fastboot, flash mode and flash tool, etc.. you can try flashing or pushing the individual .imgs form your stock firmware one at a time until whatever is corrupted gets replaced.
Click to expand...
Click to collapse
Thanks @Droidriven for your leads.. I will check out what is adb, fastboot and .imgs