Develop Bugs

[Q] [HELP] P350 stuck on LG logo 4 softkeys blinking

Hi, I've just registered in this forum, though I've been reading you guys for almost a year. I just want to say that you guys are awesome, i've learned too much about android because of you.
Introduction
Said that, I recently had a problem with my P350g, I'll try to be as clear as possible hoping you can help me out.
The problem came after i installed CM 9 [stable 8] on it, at first it worked perfectly (a very few panics or reboots but i'm used to it :laugh. The next day after taking a photograph the cellphone got stuck, it had done that several times before with some other ROMs so i didn't pay much attention to it, so i took the battery off and put it again, and when I tried to turn it on, there it was, the lg logo with the 4 softkeys blinking.
-- It doesn't enter to recovery (i had recovery installed at that time) pressing [- power send] at the same time, it just stays there with the lg logo blinking.
-- It does enter to the emergency mode (yellow background with "emergency mode" in black letters) pressing [+ - power] at the same time.
-- It does enter to the fastboot mode pressing [+ power send] at the same time.
what i've already tryed:
--- i've read the wiki about this phone and try everything there (and everything found on google which is pretty much the same)
http://forum.xda-developers.com/wiki/LG_Optimus_Me
--- i've tryed using the KDZ updater as somebody on this forum recommended:
http://multidroid2.feed.nu/2012/03/27/how-to-unbrickflash-your-optimus-melg-p350-2/
using firmware from here:
http://lg-phone-firmware.com/index.php?id_mod=5
and from somewhere else on the internet, the problem here is, that when it comes to "restart the phone", it doesn't start, it just keeps getting stuck on the lg logo with the 4 softkeys blinking, after some time the KDZ updater shows an error: Upgrade Error WParam: 100 LParam: 6
--- i've tryed flashing the recovery from fastboot mode as shown on this thread:
http://forum.xda-developers.com/showthread.php?t=2131247
it flashes well, everything "succeeded" but whe it comes to reboot (flashboot reboot) the cellphone says on the screen rebooting cellphone (or something like that) but it never reboots. if I take the battery off and put it on again, and then try to turn it on, the cellphone shows at the same problem, the lg logo with 4 softkeys blinking.
--- I've also tryed this tool:
http://forum.xda-developers.com/showthread.php?t=1948326
it hasn't solved my problem either.
Computers' info
I've tried this on 2 computers:
windows 7 x86
windows 8 x64
both of them have the drivers installed, I've disabled the modem on both of them, both of them have the latest android SDK tools
both computers give me the same problems, please i need your help, i'm desperate, I've been with this problem for several days and I can't solve it. I hope you can help me out

bump!
Anybody? please, i'm desperate

Hi,
Let's hope for the good
Try to flash the rom with fastboot.
and did you overclocked it too high? maybe your nand is burned?

kD said:
Hi,
Let's hope for the good
Try to flash the rom with fastboot.
and did you overclocked it too high? maybe your nand is burned?
Click to expand...
Click to collapse
thanks for answering, yes i did overclock it really high ~804MHz can't remember the exact number, but with other roms it had been working at that level of overclock without any problems (besides the casual panics and reboots) for more than half a year.
i'm going to try flashing the rom from flashboot and see what happens

I couldn't fash a rom via fastboot
IsraelMP said:
thanks for answering, yes i did overclock it really high ~804MHz can't remember the exact number, but with other roms it had been working at that level of overclock without any problems (besides the casual panics and reboots) for more than half a year.
i'm going to try flashing the rom from flashboot and see what happens
Click to expand...
Click to collapse
Hi everybody, i tried to flash a zip containing the rom on my p350, though i could not flash it. i used the command:
fastboot flash system rom.zip
but it says the file/rom size was smaller than expected. (honestly i can't remember the actual sentence) and then it says (x < y) where x is the suposed size of the rom and y is the expected size.
i tried with several roms, and a backup a user uploaded somewhere which was suposedly legitimate.
Is there something i can do?

download lg mobile support tool (lg mobile updater)
make sure that the driver is installed on the computer
open it
let it reconize the phone then
click recover phone from CS
the phone will be returned to latest stock rom for your country
then intsall recvoery again and root again

My Method
Well you need usb debugging enabled.Remove phone's batytery and connect it to pc via usb.It will boot up (horribly of course ignore it).Then fire up the kdz updater and start the flashing process.Once the phocess starts midway anywhere in the process insert the battery.The process will complete then KDZ will sat update complete...REBOOTING....and as battery is inserted it will reboot.Voila.Hope it works for you.This is my routine method.(Bricked more than 7 times lol).

Thanks for replying
MeeDa said:
download lg mobile support tool (lg mobile updater)
make sure that the driver is installed on the computer
open it
let it reconize the phone then
click recover phone from CS
the phone will be returned to latest stock rom for your country
then intsall recvoery again and root again
Click to expand...
Click to collapse
thanks for replying, i did that, when i just plug it without pressing any button the cellphone does not get recognized by the software, when i plug it in emergency mode it does get recognized but the software gives me an error.
blazecodester said:
Well you need usb debugging enabled.Remove phone's batytery and connect it to pc via usb.It will boot up (horribly of course ignore it).Then fire up the kdz updater and start the flashing process.Once the phocess starts midway anywhere in the process insert the battery.The process will complete then KDZ will sat update complete...REBOOTING....and as battery is inserted it will reboot.Voila.Hope it works for you.This is my routine method.(Bricked more than 7 times lol).
Click to expand...
Click to collapse
thanks for the answer, I tried that way, though it keeps getting stuck in the LG logo with the 4 blinking softkeys when it comes to reboot the cellphone.

Nexus X bootloop

Ok so here it is. I never post things on XDA because usually if you take the time to read and do some searching through google you can resolve your problems.
Anyways here's my problem. I traded my Blackberry Z10 (piece of sh**) for a Galaxy Nexus at a pawn shop. :highfive:
I was pretty happy to get my hands back to an android device and start flashing custom Roms and all that buzz.
It was instantly rooted when i got home, flashed a slimkat rom on there and had fun for a bit. :good:
Then my data connection was not working, so i flashed an AOKP Rom over top of the old rom without wiping anything previously. I did make a backup through TWRP but then i couldn't touch the screen in TWRP (power button still locked it though) so i gave up with that and tried CWM. NOTHING.
Now, 5 fuc***g days later, after searching, downloading, flashing stock images, following directions. I am still staring into this annoying as hell "X" boot loop.
I swear to you that i have tried absolutely everything I can possibly do to get it to stop.
-downloaded about 3 different google factory images
-tryed to un-root and re-root
-tryed to wipe the boot.img, system.img, userdata, bootloader, recovery, cache
-re-locked and un-locked bootloader (oem)
-I have tryed two different toolkits (Wugg's and Skipsoft) and i swear i have pushed every god damn button on both toolkits by now
-I even called google just to see what they would say, they just got me to go into the stock recovery and factory reset and clear the cache part.
-then google support told me to call samsung , just so they could tell me to do the exact same thing as google.
-the drivers are all installed correctly, but it will only recognize it in fastboot
-I cant even try an adb logcat command to see what is happening because USB Debugging is not on (not like i can turn it on)
Please if you think there is something that i have not tried go ahead and shoot at me with some kind of direction
***UPDATE**** to anyone who is reading this
I have fixed the bootloop. all thanks to legija (SEE- (http) forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-gt-i9100g-gt-i9300-1465412/)
it had somthing to do with Omap. - LINK for omapflash- (http) d-h.st/XNv
if you may have the same problem as me follow these steps
1. Download the zip file created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process. Once you see "Press any key to continue..." close the CMD window and proceed to step 9
9. Unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)

Hi,
I don't guaranteed if this works but maybe you could try Odin and reflash through your PC
Išsiųsta naudojantis Galaxy Nexus Tapatalk 4 Lt

xamxamas said:
Hi,
I don't guaranteed if this works but maybe you could try Odin and reflash through your PC
Išsiųsta naudojantis Galaxy Nexus Tapatalk 4 Lt
Click to expand...
Click to collapse
I can put into odin mode, but if i plug it into my computer the device inst recognized. It just stays at the "downloading... do not turn off target" screen. So im not to sure how i would go about re-flashing it.
But thank you for the reply. Sir:good:

Was your bootloader still unlocked when you tried to lock it?
Sent from my Galaxy Nexus using xda app-developers app

mrgnex said:
Was your bootloader still unlocked when you tried to lock it?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
yes it was. would it make a difference?
Honestly i have even tried the ODIN program 2 different ways (just as xamxamas suggested) and now im thinking that the kernal has something to do with it.

Well I think you have a fried eEMMC (your internal storage is dead). When you reboot everything was as it was before no matter what you did?
Sent from my Galaxy Nexus using xda app-developers app

Help needed: Blank screen. Can't get into recovery or start phone X9077

Hello.
I have an X9077 and was trying to flash the latest stable ROM coming back from Beta2.
I tried a few times with no luck and then I read that someone had had more luch by flashing 1.2 first and then the latest ROM.
I tried with that ROM and it caused a split screen image and when I tried again it just caused a blank screen. So no OPPO logo or noting but the backlight is on and the soft keys glow a bit.
If I try to enter recovery I have the same thing happening.
The computer sees the phone and the sd card and I can access it in fastbook mode but don't get any visuals in the screen to reload the beta2 Rom.
Please help. All I wanted was to get the GAPPS and to be able to make and receive calls without chinese characters popping out everywhere.
I downloaded the stock recovery from:
oppoforums . com / threads / stock-recovery-for-find-7-7a.17397 /
and then did a
fastboot erase cache
Which worked fine and then I did a
fastboot flash recovery recovery.img
Which worked but still can't access the recovery part. I get a blank black screen with glowing buttons underneath.
Everything went south before when I installed X9006_12_OTA_INT_001_all_svn5596_wipe.zip which I now know was not for my phone.

munecito said:
Hello.
I have an X9077 and was trying to flash the latest stable ROM coming back from Beta2.
I tried a few times with no luck and then I read that someone had had more luch by flashing 1.2 first and then the latest ROM.
I tried with that ROM and it caused a split screen image and when I tried again it just caused a blank screen. So no OPPO logo or noting but the backlight is on and the soft keys glow a bit.
If I try to enter recovery I have the same thing happening.
The computer sees the phone and the sd card and I can access it in fastbook mode but don't get any visuals in the screen to reload the beta2 Rom.
Please help. All I wanted was to get the GAPPS and to be able to make and receive calls without chinese characters popping out everywhere.
I downloaded the stock recovery from:
oppoforums . com / threads / stock-recovery-for-find-7-7a.17397 /
and then did a
fastboot erase cache
Which worked fine and then I did a
fastboot flash recovery recovery.img
Which worked but still can't access the recovery part. I get a blank black screen with glowing buttons underneath.
Everything went south before when I installed X9006_12_OTA_INT_001_all_svn5596_wipe.zip which I now know was not for my phone.
Click to expand...
Click to collapse
Hi, since you're also here, the link:
http://www.oppoforums.com/threads/find-7-x9077-soft-bricked.16918/
Good luck.:fingers-crossed:

tropical cactus said:
Hi, since you're also here, the link:
http://www.oppoforums.com/threads/find-7-x9077-soft-bricked.16918/
Good luck.:fingers-crossed:
Click to expand...
Click to collapse
Well I have installed the stock recovery but my phone still does all the things that Suyi's did.
I have written to Suyi and Coldbird to see if they can guide me on how to manually restore the partitions.
Thank you very much.

Coldbird and Suyi are legends!!! I have rescued my phone back from the darkness thanks to your amazing work.
The only thing is that there is an unnecessary line there which is 521. The syntax in it is wrong but it doesn't harm the procedure, but it can be a bit unnerving.
I did not use the ROM that they used but the latest stable 1.2.1
Instructions are here:
http://www.oppoforums.com/threads/find-7-x9077-soft-bricked.16918/page-2#post-218544

munecito said:
Coldbird and Suyi are legends!!! I have rescued my phone back from the darkness thanks to your amazing work.
The only thing is that there is an unnecessary line there which is 521. The syntax in it is wrong but it doesn't harm the procedure, but it can be a bit unnerving.
I did not use the ROM that they used but the latest stable 1.2.1
Instructions are here:
http://www.oppoforums.com/threads/find-7-x9077-soft-bricked.16918/page-2#post-218544
Click to expand...
Click to collapse
Well done. Oppo should at least have set the numbers of the models further apart e.g. 9008 for find 7 & 9007 for 7a. It seems 7 is feng shui for them. Launch date for find 7 in Malaysia is 7.7.14. 7+7=14.
Oppo. Symmetry. Should be opqo.

My phone's model number is X9076. I am facing this same issue. The only difference is that my phone is not even rooted. Whenever I try installing TWRP on my phone the screen goes black. When I try pressing the hardware buttons, it gives a haptic feedback but doesn't show anything on the screen. Because of that I am not able to root my device and also can't install any custom ROMs. Also my phone is in stock condition and I haven't done anything to it before. How can I fix this (please don't provide me with any links, please explain me the procedure so it becomes easy for me )

Devansh Bharatia said:
My phone's model number is X9076. I am facing this same issue. The only difference is that my phone is not even rooted. Whenever I try installing TWRP on my phone the screen goes black. When I try pressing the hardware buttons, it gives a haptic feedback but doesn't show anything on the screen. Because of that I am not able to root my device and also can't install any custom ROMs. Also my phone is in stock condition and I haven't done anything to it before. How can I fix this (please don't provide me with any links, please explain me the procedure so it becomes easy for me )
Click to expand...
Click to collapse
https://forum.xda-developers.com/find-7/help/how-to-debrick-unbricka-oppo-7-7a-t3717802/page1

knusto said:
https://forum.xda-developers.com/find-7/help/how-to-debrick-unbricka-oppo-7-7a-t3717802/page1
Click to expand...
Click to collapse
Thank you but my phone is not bricked.

Is this thread dead already? Because I need some serious help with my Find 7

Devansh Bharatia said:
Is this thread dead already? Because I need some serious help with my Find 7
Click to expand...
Click to collapse
Setup?
Skickat från min Find7 via Tapatalk

[Q] Bootloop, can't access Recovery Mode

Hi All!
I've checked all similar threads but I haven't found any solution to my problem, hence this post.
I was trying to root Samsung Note 2 and install Cyanogenmod but rooting failed
The current problem:
1. Samsung Note 2 has ended up in a bootloop after failed rooting
2. I can't boot the phone in the Recovery Mode
3. The USB Debugging Mode was not activated
4. I can't turn on the phone
Description:
I was trying to root my friend's Samsung Note 2 using the following method from this website http://forum.xda-developers.com/showthread.php?t=2291827
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
Click to expand...
Click to collapse
The problem is that by mistake I used a wrong CF-Auto-Root... file and instead of this file CF-Auto-Root-t03g-t03gxx-gtn7100.zip which was designed for Samsung Note 2 I used a file which I was using before for my own phone (Samsung Galaxy S4) CF-Auto-Root-jflte-jfltexx-gti9505.zip
Result 1: The rooting process got frozen and I had to disconnect the USB cable connecting the phone with the computer.
Result 2: Black screen, I couldn't boot the phone.
Next, I used the same rooting method but with the correct CF-Auto-Root... file.
Result 3: Bootloop. The phone boots up when I press the power button but when I see the first screen with a white "Samsung Note 2" on a black background, the phone reboots again and the process repeats itself for ever.
Result 4: I can't boot the phone in recovery mode. When I press the Volume Up+Power+Home buttons, the phone reboots and keeps rebooting instead of going into recovery mode.
Result 5: The USB Debugging Mode was not activated before rooting. Since I can't turn on the phone I can't activate the mode now. All solutions to my problem that I've seen require having USB Debugging Mode activated.
Could anyone help me and suggest what to do, please?
I don't know much about how mobile phone works but I can follow instructions if I know what to do.
I rooted my own mobile phone and installed Cyanogenmod successfully. I wanted to do the same with my friend's phone who was fed up with bloated and slow manufacturer's firmware.
I hope you can help me. Thank you.

I really don't know why so many users try to root before flashing a custom rom -> it is simply useless and as shown in this example dangerous, when a false root method or file is chosen.
You need:
1. Custom recovery, flash through ODIN, I think latest TWRP will do the job
2. Flash your desired custom rom through above recovery, (if needed: GApps also)
3. Flash SuperSu if needed (read in OP of that rom) done
If number 1 won't work, you got to flash firmware from sammobile first using ODIN
and then take steps 1, 2, 3

Androidwizzard said:
I really don't know why so many users try to root before flashing a custom rom -> it is simply useless and as shown in this example dangerous, when a false root method or file is chosen.
You need:
1. Custom recovery, flash through ODIN, I think latest TWRP will do the job
2. Flash your desired custom rom through above recovery, (if needed: GApps also)
3. Flash SuperSu if needed (read in OP of that rom) done
If number 1 won't work, you got to flash firmware from sammobile first using ODIN
and then take steps 1, 2, 3
Click to expand...
Click to collapse
Hi AndroidWizzard!
Thank you very much for your quick reply.
I've done everything as you advised me to and... it worked!
Firstly, I installed TWRP, I wiped all files on the phone, downloaded Cyanogenmod to external SD card, installed Cyanogenmod through TWRP and all done! I also installed the minimum version of Gapps and it's all I need.
Thank you SO much for your help. twdeim which
All the best!

britanix said:
Hi AndroidWizzard!
Thank you very much for your quick reply.
I've done everything as you advised me to and... it worked!
Firstly, I installed TWRP, I wiped all files on the phone, downloaded Cyanogenmod to external SD card, installed Cyanogenmod through TWRP and all done! I also installed the minimum version of Gapps and it's all I need.
Thank you SO much for your help.
All the best!
Click to expand...
Click to collapse
Never praise a ford till you get over.
Click to expand...
Click to collapse
As I said, everything I mentioned before went fine but there is one problem. The system doesn't detect the network as if the SIM card wasn't inserted. I double checked everything and I have no idea what that is.
I installed CyanogenMod version 11-20140715-NIGHTLY-n7100 with android version4.4.4.
I would be very grateful for any suggestions.
Many thanks!

Access Recovery Tool
RecoveryFix for Access data recovery software expediently recover inaccessible Access file. It recovers user data from damage Access files.

udansikka said:
RecoveryFix for Access data recovery software expediently recover inaccessible Access file. It recovers user data from damage Access files.
Click to expand...
Click to collapse
I am sorry but I don't understand how RecoveryFix relates to my problem. Could you write a bit more, please?
Thank you.

britanix said:
I am sorry but I don't understand how RecoveryFix relates to my problem. Could you write a bit more, please?
Thank you.
Click to expand...
Click to collapse
Hi All,
I've solved the problem. Thank you!

britanix said:
Hi All,
I've solved the problem. Thank you!
Click to expand...
Click to collapse
can you tell me how to solved your problem because i have something like your problem

suirs said:
can you tell me how to solved your problem because i have something like your problem
Click to expand...
Click to collapse
The problem originated from the fact that my IMEI got lost somewhere during failed rooting/flashing. I've flashed with the stock firmware which retrieved my IMEI and the phone connected to the network as usual. After the phone was brought back to the fully operational state, I used CyanogenMod installer for Mac and I successfully installed CM, and it works like a dream.
I hope it will help. Good luck!

britanix said:
The problem originated from the fact that my IMEI got lost somewhere during failed rooting/flashing. I've flashed with the stock firmware which retrieved my IMEI and the phone connected to the network as usual. After the phone was brought back to the fully operational state, I used CyanogenMod installer for Mac and I successfully installed CM, and it works like a dream.
I hope it will help. Good luck!
Click to expand...
Click to collapse
there is have a version worked on windows 7 ??

suirs said:
there is have a version worked on windows 7 ??
Click to expand...
Click to collapse
I understand that you are asking if there is a CyanogenMod installer for Windows. Yes, there is, particularly for Windows http://beta.download.cyanogenmod.org/install

Just copy of my posts in another thread as this one is more relevant to my problem I think:
Good afternoon gents and girls, I have a bit strange problem wonder if anyone can get a bit of light on it. My Mrs's GT-7100 one day was stuck on boot up screen. I thought is was corrupt tried to do factory reset. Didn't work out read about is decided to flash it with a different official ROM for that installed twrp-3.0.2-0-t03g.img.tar and was trying to do a lot of different things within TWRP mode. As I'm not familiar with flashing process I guess didn't do it properly BUT! While doing it all over sudden I realised that the phone is actually working while connected to external power it shows charge and goes upto 100% but as as soon as it disconnected from main power source it starts to reboot constantly again stuck at the same boot screen again, till reconnected to power source again, then goes in to fool boot and functions properly making and receiving phone calls. The charge shown on the battery drops from 100% to 4-7% in a matter of the boot up time which is say 5-10 seconds.
Tested by multimeter battery shows 4.32V. I can't test battery under load, but will endeavor to do so by a test light. I have a bit strange problem wonder if anyone can get a bit of light on it.
So any thoughts?
I suspect the battery is not the issue. I have 2 external banks which are holding the charge to keep running Galaxy 3 8.0 up to 2-3 hours in use. Both of them are 5.2V 1A and having GT-7100 connected to them doesn't help to boot up the phone. Olso 5V 0,5A charger of Bluebery either, only Samsung 2A charger gets the GT-7100 back to fanctioning mode. When phone is booted up it shows
The ROM Version it is N7100XXUFND3,
Kernel version 3.0.31-152758,
Build number
KOT49H.N7100XXSFQA1
SE for Android status
enforcing
SEPF_GT-7100_4.4.2_0016

{How To}[Root][Recovery] Everything For Micromax Canvas Fire 2 (A104) KitKat Based

""As my Dev brothers said earlier, "BOND comes with bang". So giving respect to all of my dev brothers and starting this new thread.""
Lets first start with the very known thing of MTK devices. So these things are common in all MTK:-
1)
Code:
[URL="http://www.mediafire.com/download/kmt3bjcga3pyymf/SP_Flash_Tool_exe_v3.1344.0.212.rar"]SP Flash Tool (For flashing any MTK Device)[/URL]
2)
Code:
[URL="http://www.mediafire.com/download/3q679a2jelhcumc/UPDATE-SuperSU-v1.94.zip"]Super-User Update (Rooting zip, flashable in custom recovery)[/URL]
3)
Code:
MTK Preloader USB VCom Driver (Search on google, there are many)
Brothers,
1) is basically used by us for flashing custom recovery, boot, or factory firmware, if anything goes wrong.
2) is used for rooting a ROM, may its Kitkat or Jellybean.
3) is used for flashing through sp flash tool
PRE-Requisite:-
1) Normal Human Brain. [Must, Don't even try without it]
2) Patience [Again a must have thing.]
3) MTK Preloader USB VCom driver installed on your PC.:good:
4) Recovery Utility for Canvas Fire 2 A104 [Download this]:good:
5) Stock Firmware of Canvas Fire 2 A104 [Download this as a precaution]:good:
6) Heart & Money. {If everything goes wrong and nothing works, then heart to bear the blame and money to buy a new phone.
Now Procedure for rooting MT6582M based Micromax Canvas Fire 2 A104:-
a) Download SP Flash tool and also download the recovery utility.
b) Extract both somewhere on your pc but not out side "C/" drive.
c) Open Flash tool and click on scatter loading.
d) Select scatter loading "MT6582_Android_scatter" from recovery utility folder.
e) Now De-select everything other than recovery and boot in the flashtool.
f) Make sure only recovery & boot is selected in flashtool then click Download button.
g) Now connect your fire 2 (without battery) to your pc.
h) Let the process complete. After this disconnect your phone and press Volume up(+) and Power Button for
booting in to recovery.
i) In recovery choose zip "Update SuperUser zip" and flash it and voila.
You have got root and one of the best custom recovery "Phillz Touch based recovery" on your fire 2. Now start firing and enjoy.
Screenshot Given for reference of "Phillz Recovery".
Disclaimer:-
If anything goes wrong, and nothing is there left to make your phone come back, then neither me nor XDA nor my dev brothers are responsible for this. You are the person who have chosen to do this to your device and so you're the responsible person for this. So please do responsibly and enjoy boldly.

"First of all a big THANKS to all my dev brothers who ported 4.2 to MT6577. You guys genuinely has made a history in MediaTek Device forums."
A Big Thanks to Master @yuweng, for his awesome services and threads for mediatek. Its been a light of guidance for devs.
A Special Thanks to Master @phillz, for devoting time and creating recovery modules for Meditek Devices. The Phillz recovery has been the most famous and wonderful custom recovery.
Special Thanks to "Micromax" for making so many devices with same specs but different boots and all.
Special Thanks to XDA & Droid-Devz for giving me platforms for presenting my works and XDA been my school where I learned Android.
Special Thanks to my wife for bearing my non-sense jokes and being my partner in everything I do or will do.
Special Thanks to all those brothers who trusted me and still using my MODs and my ROMs.

Thanks For This Dude
Hope you all will see a rom For this device by me

ICS_XD said:
Thanks For This Dude
Hope you all will see a rom For this device by me
Click to expand...
Click to collapse
Sir,
I will wait for your ROM, Still using Neat ROM on my S2. Will wait even longer if its going to be a series of Neat ROM for Micromax A104.

Welcome back stranger ...
Regards

SuperDroid-BOND said:
Sir,
I will wait for your ROM, Still using Neat ROM on my S2. Will wait even longer if its going to be a series of Neat ROM for Micromax A104.
Click to expand...
Click to collapse
Mate No It wont be Neat Rom
It will have a New name
Just wait for it

ICS_XD said:
Mate No It wont be Neat Rom
It will have a New name
Just wait for it
Click to expand...
Click to collapse
Sir,
If its not a series of Neat Rom then also its fine because the Dev for both will be same...
Still I'll wait for getting this on my phone.
Sent from my LG-F240L using Tapatalk

reply fast sir
SuperDroid-BOND said:
""As my Dev brothers said earlier, "BOND comes with bang". So giving respect to all of my dev brothers and starting this new thread.""
Lets first start with the very known thing of MTK devices. So these things are common in all MTK:-
1)
Code:
[URL="http://www.mediafire.com/download/kmt3bjcga3pyymf/SP_Flash_Tool_exe_v3.1344.0.212.rar"]SP Flash Tool (For flashing any MTK Device)[/URL]
2)
Code:
[URL="http://www.mediafire.com/download/3q679a2jelhcumc/UPDATE-SuperSU-v1.94.zip"]Super-User Update (Rooting zip, flashable in custom recovery)[/URL]
3)
Code:
MTK Preloader USB VCom Driver (Search on google, there are many)
Brothers,
1) is basically used by us for flashing custom recovery, boot, or factory firmware, if anything goes wrong.
2) is used for rooting a ROM, may its Kitkat or Jellybean.
3) is used for flashing through sp flash tool
PRE-Requisite:-
1) Normal Human Brain. [Must, Don't even try without it]
2) Patience [Again a must have thing.]
3) MTK Preloader USB VCom driver installed on your PC.:good:
4) Recovery Utility for Canvas Fire 2 A104 [Download this]:good:
5) Stock Firmware of Canvas Fire 2 A104 [Download this as a precaution]:good:
6) Heart & Money. {If everything goes wrong and nothing works, then heart to bear the blame and money to buy a new phone.
Now Procedure for rooting MT6582M based Micromax Canvas Fire 2 A104:-
a) Download SP Flash tool and also download the recovery utility.
b) Extract both somewhere on your pc but not out side "C/" drive.
c) Open Flash tool and click on scatter loading.
d) Select scatter loading "MT6582_Android_scatter" from recovery utility folder.
e) Now De-select everything other than recovery and boot in the flashtool.
f) Make sure only recovery & boot is selected in flashtool then click Download button.
g) Now connect your fire 2 (without battery) to your pc.
h) Let the process complete. After this disconnect your phone and press Volume up(+) and Power Button for
booting in to recovery.
i) In recovery choose zip "Update SuperUser zip" and flash it and voila.
You have got root and one of the best custom recovery "Phillz Touch based recovery" on your fire 2. Now start firing and enjoy.
Screenshot Given for reference of "Phillz Recovery".
Disclaimer:-
If anything goes wrong, and nothing is there left to make your phone come back, then neither me nor XDA nor my dev brothers are responsible for this. You are the person who have chosen to do this to your device and so you're the responsible person for this. So please do responsibly and enjoy boldly.
Click to expand...
Click to collapse
sir is it work on Micromax fire a093 ?? its worked on fire a104..

FROM_HEAVEN said:
sir is it work on Micromax fire a093 ?? its worked on fire a104..
Click to expand...
Click to collapse
Brother,
First thing first that please don't quote the whole OP, its very long and consume much space. Now brother I don't know that its working for A093 or not as I don't have the device and now I have also sold the A104. Try it but before trying download the whole stock firmware of A093, so that if it fails you can get back to its original position.
Regards
BOND

bro i tried it but its failed on a093 but thanks for stock rom suggestion i manage to get back my devive now bro create a method for Micromax fire a093 i am waiting for this too long

Guys thanks for this awesome recovery and root method but one thing my titanium app not restoring apps and can't take up backup and it shows interrupted error....this happens after root with super su but works well on kinguser app....why it happens guys any solution? Thanks
Sent from my Micromax A104 using XDA Free mobile app

SuperDroid-BOND said:
Sir,
I will wait for your ROM, Still using Neat ROM on my S2. Will wait even longer if its going to be a series of Neat ROM for Micromax A104.
Click to expand...
Click to collapse
Hi man,
I did the whole procedure properly and the top half of my phone screen is inverted.. Not the display, but the touch only.. I must touch the center of the screen to pull down the status bar.. (Know what I mean?) I can't seem to fix the issue.. I tried flashing stock recovery.img, didn't work. Tried stock rom, didn't work. Did a full wipe too.. I'm not blaming you, I just need your help.. Any idea why that happened or how to fix it?

branndonn1 said:
Hi man,
I did the whole procedure properly and the top half of my phone screen is inverted.. Not the display, but the touch only.. I must touch the center of the screen to pull down the status bar.. (Know what I mean?) I can't seem to fix the issue.. I tried flashing stock recovery.img, didn't work. Tried stock rom, didn't work. Did a full wipe too.. I'm not blaming you, I just need your help.. Any idea why that happened or how to fix it?
Click to expand...
Click to collapse
I got the same issue. Looks like the provided boot.img wasnt meant for the device we have. I am also trying to fix this. Will update if it gets fixed.
---------- Post added at 08:51 PM ---------- Previous post was at 08:02 PM ----------
branndonn1 said:
Hi man,
I did the whole procedure properly and the top half of my phone screen is inverted.. Not the display, but the touch only.. I must touch the center of the screen to pull down the status bar.. (Know what I mean?) I can't seem to fix the issue.. I tried flashing stock recovery.img, didn't work. Tried stock rom, didn't work. Did a full wipe too.. I'm not blaming you, I just need your help.. Any idea why that happened or how to fix it?
Click to expand...
Click to collapse
Hey, Just in case you are still having that issue. I figured out the cause. Its because of the boot.img we flashed. The new hardware components used in our phones are not compatible with the old boot.img we flashed, which is supposed to be of earlier Firmware version. Please download the package below and flash it.
http://clicknupload.com/xdpt8n2w3oho
I assume that you must had already flashed the complete old firmware, you need to flash this new firmware. I havnt flashed old FW so just flashed the new boot.img of this package and the problem is solved.
This is a request to the thread owner to please mention this in OP that the users with V8.1 (can be checked in Settings >> About Phone >> Build Number) should uncheck boot while flashing, however it will cause same inverted touch issue in recovery but it can be managed with the volume buttons anyways.

branndonn1 said:
Hi man,
I did the whole procedure properly and the top half of my phone screen is inverted.. Not the display, but the touch only.. I must touch the center of the screen to pull down the status bar.. (Know what I mean?) I can't seem to fix the issue.. I tried flashing stock recovery.img, didn't work. Tried stock rom, didn't work. Did a full wipe too.. I'm not blaming you, I just need your help.. Any idea why that happened or how to fix it?
Click to expand...
Click to collapse
EnDLessssS said:
I got the same issue. Looks like the provided boot.img wasnt meant for the device we have. I am also trying to fix this. Will update if it gets fixed.
---------- Post added at 08:51 PM ---------- Previous post was at 08:02 PM ----------
Hey, Just in case you are still having that issue. I figured out the cause. Its because of the boot.img we flashed. The new hardware components used in our phones are not compatible with the old boot.img we flashed, which is supposed to be of earlier Firmware version. Please download the package below and flash it.
http://clicknupload.com/xdpt8n2w3oho
I assume that you must had already flashed the complete old firmware, you need to flash this new firmware. I havnt flashed old FW so just flashed the new boot.img of this package and the problem is solved.
This is a request to the thread owner to please mention this in OP that the users with V8.1 (can be checked in Settings >> About Phone >> Build Number) should uncheck boot while flashing, however it will cause same inverted touch issue in recovery but it can be managed with the volume buttons anyways.
Click to expand...
Click to collapse
Brothers,
When I bought this device then I downloaded it and made the rooting n recovery guide after testing it for three times on my device. If later the oem has changed anything in firmware then I'm sorry but I cannot update it as now I don't have this device anymore. If you want recovery for this device then please uploaded your boot.img from latest firmware and I'll make a recovery for you but after 7 days from now. currently busy in funeral of my Grandma.
Thanks & Regards
BOND
Sent From:-
""The Little Beast of XIAOMI""

SuperDroid-BOND said:
Brothers,
When I bought this device then I downloaded it and made the rooting n recovery guide after testing it for three times on my device. If later the oem has changed anything in firmware then I'm sorry but I cannot update it as now I don't have this device anymore. If you want recovery for this device then please uploaded your boot.img from latest firmware and I'll make a recovery for you but after 7 days from now. currently busy in funeral of my Grandma.
Thanks & Regards
BOND
Sent From:-
""The Little Beast of XIAOMI""
Click to expand...
Click to collapse
Hi Bond,
Never mind it. You can just put this info in your opening post for now. Also, here i am attaching the new boot.img. As per the release notes, this version is backward compatible.
Thanks

After flashing the boot.img inverted touch fixed.all goes right.but in charging animation(switch off) are still inverted

SuperDroid-BOND said:
""As my Dev brothers said earlier, "BOND comes with bang". So giving respect to all of my dev brothers and starting this new thread.""
Lets first start with the very known thing of MTK devices. So these things are common in all MTK:-
1)
Code:
[URL="http://www.mediafire.com/download/kmt3bjcga3pyymf/SP_Flash_Tool_exe_v3.1344.0.212.rar"]SP Flash Tool (For flashing any MTK Device)[/URL]
2)
Code:
[URL="http://www.mediafire.com/download/3q679a2jelhcumc/UPDATE-SuperSU-v1.94.zip"]Super-User Update (Rooting zip, flashable in custom recovery)[/URL]
3)
Code:
MTK Preloader USB VCom Driver (Search on google, there are many)
Brothers,
1) is basically used by us for flashing custom recovery, boot, or factory firmware, if anything goes wrong.
2) is used for rooting a ROM, may its Kitkat or Jellybean.
3) is used for flashing through sp flash tool
PRE-Requisite:-
1) Normal Human Brain. [Must, Don't even try without it]
2) Patience [Again a must have thing.]
3) MTK Preloader USB VCom driver installed on your PC.:good:
4) Recovery Utility for Canvas Fire 2 A104 [Download this]:good:
5) Stock Firmware of Canvas Fire 2 A104 [Download this as a precaution]:good:
6) Heart & Money. {If everything goes wrong and nothing works, then heart to bear the blame and money to buy a new phone.
Now Procedure for rooting MT6582M based Micromax Canvas Fire 2 A104:-
a) Download SP Flash tool and also download the recovery utility.
b) Extract both somewhere on your pc but not out side "C/" drive.
c) Open Flash tool and click on scatter loading.
d) Select scatter loading "MT6582_Android_scatter" from recovery utility folder.
e) Now De-select everything other than recovery and boot in the flashtool.
f) Make sure only recovery & boot is selected in flashtool then click Download button.
g) Now connect your fire 2 (without battery) to your pc.
h) Let the process complete. After this disconnect your phone and press Volume up(+) and Power Button for
booting in to recovery.
i) In recovery choose zip "Update SuperUser zip" and flash it and voila.
You have got root and one of the best custom recovery "Phillz Touch based recovery" on your fire 2. Now start firing and enjoy.
Screenshot Given for reference of "Phillz Recovery".
Disclaimer:-
If anything goes wrong, and nothing is there left to make your phone come back, then neither me nor XDA nor my dev brothers are responsible for this. You are the person who have chosen to do this to your device and so you're the responsible person for this. So please do responsibly and enjoy boldly.
Click to expand...
Click to collapse
hey buddy after rooting when I open superuser it says "The SU binary needs to be updated" and it doest work, I reflashed superuser with recovery but did't get root access..

branndonn1 said:
Hi man,
I did the whole procedure properly and the top half of my phone screen is inverted.. Not the display, but the touch only.. I must touch the center of the screen to pull down the status bar.. (Know what I mean?) I can't seem to fix the issue.. I tried flashing stock recovery.img, didn't work. Tried stock rom, didn't work. Did a full wipe too.. I'm not blaming you, I just need your help.. Any idea why that happened or how to fix it?
Click to expand...
Click to collapse
same problem...
---------- Post added at 12:23 PM ---------- Previous post was at 11:48 AM ----------
MayankGupta said:
hey buddy after rooting when I open superuser it says "The SU binary needs to be updated" and it doest work, I reflashed superuser with recovery but did't get root access..
Click to expand...
Click to collapse
not working.........plzz help after hitting download button nothing is happening

Driver not installing in Windows 8. Says driver signature is not present in INF.

Hello brother, something's wrong with my phone (mmx a104). After flashing custom recovery (twrp, philz) when I boot into recovery, touchscreen starts behaving abnormal. It got inverted horizontally and vertically. And it doesn't touch the place where I touch the screen.
Any solution dude.
Sent from my Micromax E352 using XDA-Developers mobile app