Related
Hey,
I recently became the owner of a bricked Iconia a500 tablet. Beyond that, I don't know much about it and I cannot contact the previous owner...
The situation:
It will boot the the Acer logo, but it doesn't go beyond that.
I've searched this forum (and others) for ways to bring it back to life. A factory reset doesn't seem to do anything at all.
I can boot into recovery mode to load a rom, but cannot find the proper rom. CWM does not seem to be installed. I've looked for stock roms but none seem to work.
When I try and load a rom I will inevitably get a white triangle with an orange exclamation mark inside of it. Next to this is the android man.
I've found a few threads that purpose links to a stock rom, but a lot of them have file shares linked to Megaupload... which is.. well non-existent now.
Again, I can not tell you the anything about the current software.... if you know how I can find out that alone would be a huge help! = )
Many thanks,
Robert
This might be your best luck..
This flashed thru your computer adb.. apx mode..
http://forum.xda-developers.com/showthread.php?p=20680452#post20680452
Hey Erica,
Thanks for you very speedy response!
Well, I read a lot of that thread... lol probably more than I should admit. I followed the procedure but was unable to get a good connection via USB.
I was finally able to get it to register a Factory Reset thanks to that post. Had tried it a few times before... must have not been pressing hard enough?
Either way, it is stuck on Erasing Userdata... and Erasing Cache...
I saw that it was suggested it could be a hardware issue... What is your opinion?
Thanks,
Robert
I still think its a rom issue..
You might could try to download the rom again. and try again.. there is also another thread in the DEV section that does the same thing but differently you could try that or maybe posting there where a TRUE Developer might be able to help you..
I just repeat what i have learned from my own mistakes and read from others..
Sorry im not more help ..
Trust me Erica, you have been a great help! If I find a solution, I will update this thread with it = )
Thanks!
Robert
big ol' noob here. i just flashed the Jelly-Bean_4.1.2_CM10-FLEX_v6supercharged_Aroma rom on my a500 which previously had lightspeed 4.8 on it. now when it boots it shows the android guy with gears for a second then just a blank black screen. the backlight is on so you can tell the tablet is still on. i can still get into recovery with no issues though("aman ra-iconia-3.17-ics" via "scrilax_CZ bootloader v8") i dont know what it could be though. installation of rom gave no errors. so please, I ask for assistance in resolving the issue. i was looking into (and learning about) fastboot fixes but i'm not sure if it applies to me nor have i tried it before. any help in fixing the darn thing would be much appreciated.
raotheconqueror said:
big ol' noob here. i just flashed the Jelly-Bean_4.1.2_CM10-FLEX_v6supercharged_Aroma rom on my a500 which previously had lightspeed 4.8 on it. now when it boots it shows the android guy with gears for a second then just a blank black screen. the backlight is on so you can tell the tablet is still on. i can still get into recovery with no issues though("aman ra-iconia-3.17-ics" via "scrilax_CZ bootloader v8") i dont know what it could be though. installation of rom gave no errors. so please, I ask for assistance in resolving the issue. i was looking into (and learning about) fastboot fixes but i'm not sure if it applies to me nor have i tried it before. any help in fixing the darn thing would be much appreciated.
Click to expand...
Click to collapse
You should change the title to "Stuck in APX Mode". Refine your search. I've never had the issue, however, I believe 1 or more partitions are messed up. Which means you will probably have to revert back using TimmyDeans V4 rollback tool at the worst.
Just a guess. But search the forum for those terms. You should be able to find some threads as I've seen several references to being stuck in APX mode.
One place you may want to post your issue, is Skrilax_CZ's bootloader thread. He may know some fastboot commands to wipe the data.
MD
cool. I'll do that. thanks man. I'm still learning the lingo so that sheds a bit of light for me and gives me some direction to start. thanks again.
raotheconqueror said:
cool. I'll do that. thanks man. I'm still learning the lingo so that sheds a bit of light for me and gives me some direction to start. thanks again.
Click to expand...
Click to collapse
Also remember, before you install a different rom, you must; in CWM
1. Wipe User Data/Factory Reset
2. Wipe Cache
3. Wipe Dalvik
Then go to Mounts and Storage and;
1. Format System
2. Format Flexrom
Then you can install the rom. If you haven't done this, you should try again.
MD
raotheconqueror said:
big ol' noob here. i just flashed the Jelly-Bean_4.1.2_CM10-FLEX_v6supercharged_Aroma rom on my a500 which previously had lightspeed 4.8 on it. now when it boots it shows the android guy with gears for a second then just a blank black screen. the backlight is on so you can tell the tablet is still on. i can still get into recovery with no issues though("aman ra-iconia-3.17-ics" via "scrilax_CZ bootloader v8") i dont know what it could be though. installation of rom gave no errors. so please, I ask for assistance in resolving the issue. i was looking into (and learning about) fastboot fixes but i'm not sure if it applies to me nor have i tried it before. any help in fixing the darn thing would be much appreciated.
Click to expand...
Click to collapse
Try the wipe commands suggested in post #4 and then reflash your JB ROM. A lot of time it helps with reflash the ROM after wipes.
thanks for the tips. i believe i've actually performed them like you guys told me but it seems i've made it worse. my ridiculousness is currently going on in this thread here
I'm having the same issue with this ROM. I'm using the same recovery you are.
if you have any progress let me know cause i'm still stuck in apx land...
final update
Back to stock HC 3.2.1 right now. my issue ended up being unable to format the /data directory causing all my newly flashed roms to not load properly. per JdgM3NT4L's guidance i used the tutorial and tools here which took me back to a working status. now my only problem lies with what delicious rom should i have next? an ICS or a jellybean? if any XDA tutorials or assistance help bring you tablet back, make sure to click those ":good: thanks" buttons guys.
***DISCLAIMER***
If done incorrectly, this can soft brick your device. I take no responsibility for this, and if you're unfamiliar with rooting android I suggest reading up before attempting. There are threads to fix your tablet if this goes sideways, but if this doesn't work I personally can't promise I can help you.
I used this method two days ago, and would like to thank jerbear294 for providing me with the information. I didn't come up with this, I just want to help others looking for root.
Hello guys
First, apologies if this is a redundant thread. All the root methods I've seen in individual topics seem outdated, and I just wanted to make this quick guide to help people from having to scan through pages of information to learn how to root these things. This method works on firmware WW_V12.10.1.33_20150917, which is the current release as of this post.
Lets get to it!
Download
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
(Navigate to page 1, for some reason it links to the last page)
Place it on your computer and unzip.
And the latest supersu .zip 2.46
https://download.chainfire.eu/696/supersu/
Which will be on your tablet.
Install the temp recovery to your computer, connect the tablet, make sure you enable adb (USB Debugging) on it in developer mode (Settings → about → software version → tap build number 7 times for developer mode). Once connected, run the exe in the .zip from the temp recovery.
Choose: TWRP HDPI portrait, T4.
Your device will boot into twrp recovery. Now navigate to the supersu.zip on your tablet, and install, and you should be good to go . Good luck, and happy rooting!
Thanks to everyone who developed these tools (especially Social_Design_Concepts), and XDA for providing a medium to relate them.
To run Xposed, go to http://forum.xda-developers.com/showthread.php?t=3034811
Choose 'xposed-v80-sdk21-x86', this is currently the only version I've had success with. Happy hunting folks!
404 page not found on the first link?
ThunderThighs said:
404 page not found on the first link?
Click to expand...
Click to collapse
Link fixed, thanks and my apologies
thank you a lot! you saved me a lot of browsing! :good:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
seamo123 said:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
Click to expand...
Click to collapse
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Opensystem said:
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Click to expand...
Click to collapse
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to create a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Then I placed all the files from the nandroid zip inside that (second) folder. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
I wonder should I have taken the recovery log from my own nandroid and replaced jerbear's recovery log with it? I'm starting to confuse myself at this point I think..
seamo123 said:
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to unzip the file into a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
Click to expand...
Click to collapse
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Opensystem said:
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Click to expand...
Click to collapse
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Yes the general for the memo 176 has a special working xposed, make sure you use that one. I'm a bit busy, but I'll link when I can glad you got it rooted
Joe_Bangles said:
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
Click to expand...
Click to collapse
Glad to help, xda is where it's at for community
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Delichi said:
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Click to expand...
Click to collapse
Hurray! Glad it worked out for you
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Hey sorry for the late response, work got crazy on me. I edited the original post to now include how to set up Xposed, for you or anyone else interested. Confirmed working on both .33 and .36
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
dareas said:
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
Click to expand...
Click to collapse
It's got less battery drain here, performance seems better too but that could just be a placebo
Opensystem said:
It's got less battery drain here, performance seems better too but that could just be a placebo
Click to expand...
Click to collapse
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
dareas said:
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
Click to expand...
Click to collapse
I'm not sure, we should be because of art runtime but I feel like our version is bootlegged to a degree
unable to mount /data, internal storage 0MB. How can I load the zip file?
It's probably because FDE. I used a external SD card instead
Hi all, i'm new to Android Phones, so i started a few days with this phone. But now i think i've done a big mistake, i tried to erase everything from the phone, in a hope to "restore" to the factory state. Instead, i think i've deleted everything from the phone, and now, it only says "Your device is booting now..." and it doesn't boot. It's unlocked and rooted, i've deleted it from the TWRP menu.
So, is there anything that i can do, to restore it back? The model i think it's the VNS-L31, i'm downloading a firmware from the L21, can it be replaced or something like that? Thankx in advance.
*Edit* I found stock rom for my phone here in the fórum, but it says i need to have stock recovery but i have the TWRP recovery. Is there any way that i can do it, with that recovery?
*Edit 2* In Erecovery, when i try to download it says "Getting package info failed"
First of all... Why don't you have a backup in TWRP? ALWAYS back up your stuff before doing ANYTHING in TWRP.
Second: there is an option for factory reset within the EMUI system itself. Absolutely no need to mess around in TWRP for something like that. Of course you can "factory reset" in TWRP but this can also wipe your system which then requires you to flash something.
To your problem:
Since I luckily was not forced to flash a stock firmware yet, some more information would be nice.
In which format does the firmware come (link to where you downloaded it)? TWRP can handle .zip files. So if it comes as a .zip file, you can try flashing it through TWRP (really depends on what you downloaded!)
If you only need stock recovery, try accessing TWRP with your phone plugged into a PC.
This way it normally fires up the stock eRecovery.
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
iDeadSmack said:
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
Click to expand...
Click to collapse
Hmm maybe best way is to send the user that made it work a PM and maybe he can provide you a guide on how to do it.
And maybe he or you can then provide a guide here on how to do it.
This device is rather new and the forum is building up so there is a lot of work to do and a lot of things have to be worked around.
Hope you can fix it, like I said, I cannot really help you properly since I never had the problem and therefore do not really understand what's happening on your device.
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
iDeadSmack said:
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
Click to expand...
Click to collapse
Could you help me with this problem i have the same problem on Huawei l-21 ??
Always have a backup of your fresh system on TWRP. Then whatever happen just restore it whenever you think you messed up your device and you should be fine ALWAYS.
Hi,
My Mediatek Micromax Canvas Knight A350 is totally dead. Not responding at all to any buttons. No lights or battery indicator is displayed. But some warmth can be felt on the phone.
When I connect the phone to the pc with a USB cable it is detected as MTK USB Port Comxxxx
But when I use SP flash tools to download the preloader...it does nothing. Please let me know what to do...Thanks and God bless you.
Frank Morris said:
Hi,
My Mediatek Micromax Canvas Knight A350 is totally dead. Not responding at all to any buttons. No lights or battery indicator is displayed. But some warmth can be felt on the phone.
When I connect the phone to the pc with a USB cable it is detected as MTK USB Port Comxxxx
But when I use SP flash tools to download the preloader...it does nothing. Please let me know what to do...Thanks and God bless you.
Click to expand...
Click to collapse
when connecting in sp tools, press volume down button and see if the preloader starts.....mine worked this way
harvir46 said:
when connecting in sp tools, press volume down button and see if the preloader starts.....mine worked this way
Click to expand...
Click to collapse
I tried it but did not worked. when i open device and printer, i can see DA USB VCOM PORT when battery is in and MTK USB PORT when battery is removed, i guess i should see preloader but that is not happening. when i connect karbonn without battery then i see preloader there and flashing get completed successfully.
Please help my phone is not charging, power buttons also not working, Tried to hard reset by pressing power button, volume up and down simultaneously but still phone does not respond.
I request members to help. i am trying from last 15 days.
raghubar said:
I tried it but did not worked. when i open device and printer, i can see DA USB VCOM PORT when battery is in and MTK USB PORT when battery is removed, i guess i should see preloader but that is not happening. when i connect karbonn without battery then i see preloader there and flashing get completed successfully.
Please help my phone is not charging, power buttons also not working, Tried to hard reset by pressing power button, volume up and down simultaneously but still phone does not respond.
I request members to help. i am trying from last 15 days.
Click to expand...
Click to collapse
Sorry but this thread limits to A350 only.
---------- Post added at 07:55 PM ---------- Previous post was at 07:50 PM ----------
Frank Morris said:
Hi,
My Mediatek Micromax Canvas Knight A350 is totally dead. Not responding at all to any buttons. No lights or battery indicator is displayed. But some warmth can be felt on the phone.
When I connect the phone to the pc with a USB cable it is detected as MTK USB Port Comxxxx
But when I use SP flash tools to download the preloader...it does nothing. Please let me know what to do...Thanks and God bless you.
Click to expand...
Click to collapse
Using SP Flash Tool, flash the preloader.bin first.Use meta mode if not detected,all three buttons together while connecting and keep pressed until flashing starts.
If flashing was successful then your phone should at least be able to vibrate when you press the power button or boot if the correct files are present on your phone; else, flash other necessary files to make the phone boot up and start working normally again.
P.s. writing again and again is painful as I'm lazy-ass.
I'm thinking of making a thread about this but again,I'm lazy-ass.
it worked...wow...thanks ...but now it gets into a boot loop
harvir46 said:
when connecting in sp tools, press volume down button and see if the preloader starts.....mine worked this way
Click to expand...
Click to collapse
Thanks buddy, the phone started but now it ends into a bootloop. Tried getting into custom recovery and doing a factory reset. It starts and goes all the way through and finally restarts and the same thing again...bootloop....Please suggest what should I do...Thanks and God bless.
In the meanwhile i tried flashing a new custom ROM from xdafirmware.com. But the SP flash tools downloads upto 9.86MB and then the download stops...What could be the reason? Also please let me know if Miracle Box is any kind of solution for these kind of problems! Thanks and God bless.
Mr.Ak said:
Sorry but this thread limits to A350 only.
---------- Post added at 07:55 PM ---------- Previous post was at 07:50 PM ----------
Using SP Flash Tool, flash the preloader.bin first.Use meta mode if not detected,all three buttons together while connecting and keep pressed until flashing starts.
If flashing was successful then your phone should at least be able to vibrate when you press the power button or boot if the correct files are present on your phone; else, flash other necessary files to make the phone boot up and start working normally again.
P.s. writing again and again is painful as I'm lazy-ass.
I'm thinking of making a thread about this but again,I'm lazy-ass.
Click to expand...
Click to collapse
I am also talking about Micromax A350 and i am facing same problem
as written by thread creator.Please help me, all things mentioned in this thread i tried but none worked.
Please tell whether i should do all these step with battery or without battery.
Frank Morris said:
Thanks buddy, the phone started but now it ends into a bootloop. Tried getting into custom recovery and doing a factory reset. It starts and goes all the way through and finally restarts and the same thing again...bootloop....Please suggest what should I do...Thanks and God bless.
In the meanwhile i tried flashing a new custom ROM from xdafirmware.com. But the SP flash tools downloads upto 9.86MB and then the download stops...What could be the reason? Also please let me know if Miracle Box is any kind of solution for these kind of problems! Thanks and God bless.
Click to expand...
Click to collapse
What did you actually do?
What caused bootloop if full v3 rom was actually flashed?
Also,there's no custom roms on xdafrimware.com,it's only stock roms and make sure whatever you flash is for A350 only!
You can find everything on our blog:
www.canvasknightroms.blogspot.in
Good luck!
---------- Post added at 03:34 PM ---------- Previous post was at 03:32 PM ----------
raghubar said:
I am also talking about Micromax A350 and i am facing same problem
as written by thread creator.Please help me, all things mentioned in this thread i tried but none worked.
Please tell whether i should do all these step with battery or without battery.
Click to expand...
Click to collapse
Do you even know A350's battery is non-removable?
The only way you can remove it is by disassembling the device but doing that will compromise with your battery life.It should only be used in worst case scenario and everything else fails to work!
Mr.Ak said:
What did you actually do?
What caused bootloop if full v3 rom was actually flashed?
Also,there's no custom roms on xdafrimware.com,it's only stock roms and make sure whatever you flash is for A350 only!
You can find everything on our blog:
Good luck!
First of all, I apologize for my mistake. It was not a custom ROM but a Canvas Knight Stock ROM... The file name is this...Micromax_A350_V2_040614_KitKat_(by_xdafirmware.com). It's a version 2 (unmerged storage). However, earlier I had flashed a version 3 (merged storage) ROM and since it was constantly giving me trouble I tried to reflash version 2 ROM...But unable to do so...it gets stuck at 9.6MB or 0% in the SP Flash tool.
I tried the format+download option too. But in vain. Guess I am doing something wrong! What could it be? Thanks and God bless.
Btw, I have been through your blog in the past and benefited from the same. Thanks
Click to expand...
Click to collapse
Frank Morris said:
Mr.Ak said:
What did you actually do?
What caused bootloop if full v3 rom was actually flashed?
Also,there's no custom roms on xdafrimware.com,it's only stock roms and make sure whatever you flash is for A350 only!
You can find everything on our blog:
Good luck!
First of all, I apologize for my mistake. It was not a custom ROM but a Canvas Knight Stock ROM... The file name is this...Micromax_A350_V2_040614_KitKat_(by_xdafirmware.com). It's a version 2 (unmerged storage). However, earlier I had flashed a version 3 (merged storage) ROM and since it was constantly giving me trouble I tried to reflash version 2 ROM...But unable to do so...it gets stuck at 9.6MB or 0% in the SP Flash tool.
I tried the format+download option too. But in vain. Guess I am doing something wrong! What could it be? Thanks and God bless.
Btw, I have been through your blog in the past and benefited from the same. Thanks
Click to expand...
Click to collapse
What was the problem with v3?
Click to expand...
Click to collapse
Version 3 problem...
Mr.Ak said:
What was the problem with v3?
Click to expand...
Click to collapse
Version 3 booted well the first time...it went all the way...i was setting it up nicely...and it hung and just stopped. Ever since then I tried to reboot it would not load...the Canvas Knight logo with the sound would come on and then restart or get hung at that point. In short, it would not fully boot anymore except for that once!
So I decided to do away with version 3 and thought version 2 would be fine because that's what was originally on my phone...but now this is the problem...i mean the SPFT gets hung at 0%.
Thanks and God bless you.
On a different note, I would still love to have version 3 if possible since I plan to install a custom ROM...most likely Cyanogenmod....
Latest update...
Latest Update…
I finally managed to successfully flash a Kitakat 4.4.2 vs. 2 (unmerged storage) stock rom…I downloaded the file again from xdafirmware.com and flashed it. There was no problem. The phone has started and its up since the last one hour or so.
Before booting I entered into stock recovery and did a wipe data/factory reset and also wipe cache partition. So far no problem. I have not yet switched on my wifi coz I am worried it might go off again and enter a bootloop.
Battery was 95% when booted...its now 94% since one hour...I have not used the phone at all though...
Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock rom. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the bootloader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the bootloader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3
Sorry for the trouble. But I have messed up many times in the last one month with innumerable flashing of the ROM’s and zip files. Now, once bitten twice shy I want to play safe.
So please let me know your thoughts if they are fail proof and time tested. Thanks for all your help. God bless.
Frank Morris said:
Latest Update…
I finally managed to successfully flash a Kitakat 4.4.2 vs. 2 (unmerged storage) stock rom…I downloaded the file again from xdafirmware.com and flashed it. There was no problem. The phone has started and its up since the last one hour or so.
Before booting I entered into stock recovery and did a wipe data/factory reset and also wipe cache partition. So far no problem. I have not yet switched on my wifi coz I am worried it might go off again and enter a bootloop.
Battery was 95% when booted...its now 94% since one hour...I have not used the phone at all though...
Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock rom. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the bootloader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the bootloader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3
Sorry for the trouble. But I have messed up many times in the last one month with innumerable flashing of the ROM’s and zip files. Now, once bitten twice shy I want to play safe.
So please let me know your thoughts if they are fail proof and time tested. Thanks for all your help. God bless.
Click to expand...
Click to collapse
Well I hate giving bad news to people but I might know what causing all this.
As you say,the phone booted fine now but you'll likely see random hangs and sudden reboots in using it,to be sure,use it for atleast 2 hrs constantly and then we can proceed further with your questions.
In mean time,check this post:
https://forum.xda-developers.com/showpost.php?p=69482562&postcount=697
Mr.Ak said:
Well I hate giving bad news to people but I might know what causing all this.
As you say,the phone booted fine now but you'll likely see random hangs and sudden reboots in using it,to be sure,use it for atleast 2 hrs constantly and then we can proceed further with your questions.
In mean time,check this post:
https://forum.xda-developers.com/showpost.php?p=69482562&postcount=697
Click to expand...
Click to collapse
Well I tried using it for a while...no internet...just going through settings and checking...then I enabled Developers options and connected USB. Tried to check if the phone was listed on ADB etc....but then it went into a bootloop and kept shutting down after periodic bootloops...now its totally down...not responding at all.
Anyway, I think I know how to get it back when everything else fail. Until then stay blessed and don't give up.
God bless.
Frank Morris said:
Well I tried using it for a while...no internet...just going through settings and checking...then I enabled Developers options and connected USB. Tried to check if the phone was listed on ADB etc....but then it went into a bootloop and kept shutting down after periodic bootloops...now its totally down...not responding at all.
Anyway, I think I know how to get it back when everything else fail. Until then stay blessed and don't give up.
God bless.
Click to expand...
Click to collapse
How?
The Phone has been up and about for the last 6 hours now...
Mr.Ak said:
How?
Click to expand...
Click to collapse
Hi, Sorry for the sudden disappearance. I really didn't know how to reply to your "HOW"? But I knew there was a CERTAIN possibility of getting the phone back...I call it faith in God. And I have plenty of faith and I believe in the impossible coz I have seen some of the most impossible things happen in my life and around me over the years. So plain hope and faith in God was what I banked on. But I have no logical explanation to give on the phone starting again smoothly. I have been struggling with this phone for the last 45 days. And this is the first time the phone has really stayed put and it got booted in just one go!
Also your signature line was a source of continued inspiration to hit out against all the odds and doubts.
I would now kindly appreciate any help in restoring the phone to full functionality...I mean would love to hear answers for my questions from the previous post.
In the meanwhile, I did a bit of study on the Miracle Box and a tool called ALL-IN-ONE-TOOL_V2.1...
But, I don't want to jump the gun and get going...Will wait for expert advice. Until then God bless us all. Stay blessed. And yes, thanks for all the help. Shalom.
Frank Morris said:
Hi, Sorry for the sudden disappearance. I really didn't know how to reply to your "HOW"? But I knew there was a CERTAIN possibility of getting the phone back...I call it faith in God. And I have plenty of faith and I believe in the impossible coz I have seen some of the most impossible things happen in my life and around me over the years. So plain hope and faith in God was what I banked on. But I have no logical explanation to give on the phone starting again smoothly. I have been struggling with this phone for the last 45 days. And this is the first time the phone has really stayed put and it got booted in just one go!
Also your signature line was a source of continued inspiration to hit out against all the odds and doubts.
I would now kindly appreciate any help in restoring the phone to full functionality...I mean would love to hear answers for my questions from the previous post.
In the meanwhile, I did a bit of study on the Miracle Box and a tool called ALL-IN-ONE-TOOL_V2.1...
But, I don't want to jump the gun and get going...Will wait for expert advice. Until then God bless us all. Stay blessed. And yes, thanks for all the help. Shalom.
Click to expand...
Click to collapse
You don't need all those tool box.
Sp flash tools is enough to give life to your device.
Help required to set up the device fully...now that it is working!
Mr.Ak said:
You don't need all those tool box.
Sp flash tools is enough to give life to your device.
Click to expand...
Click to collapse
Hi Ak,
Thanks for your reply. My device is up and about since the last hmmm...to be exact...26 hours. I didn't have any reboots or bootloops or anything for that matter.
However, I need to set it up complete...customization I mean...and these are some of the problems I am facing... Quoting a part of the previous post to save typing...
Quote "Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock ROM. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the boot-loader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the boot-loader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3" Unquote.
In the meanwhile, I have done a little bit of study and RnD of the miracle box/MTK Droid Tools/S&N Writer tool etc. on my old Canvas HD 116. And I realized that the Miracle Box is one good tool. The IMEI No. can be changed in a jiffy. Rooting is extremely easy using this box. I did via adb.
In short, a bit too confused with too much knowledge on hand. Looking for wisdom to apply this knowledge correctly. There could be many simpler ways too!!! Any help in this regard is much appreciated.
Thanks and God bless us all. Shalom.
Frank Morris said:
Hi Ak,
Thanks for your reply. My device is up and about since the last hmmm...to be exact...26 hours. I didn't have any reboots or bootloops or anything for that matter.
However, I need to set it up complete...customization I mean...and these are some of the problems I am facing... Quoting a part of the previous post to save typing...
Quote "Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock ROM. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the boot-loader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the boot-loader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3" Unquote.
In the meanwhile, I have done a little bit of study and RnD of the miracle box/MTK Droid Tools/S&N Writer tool etc. on my old Canvas HD 116. And I realized that the Miracle Box is one good tool. The IMEI No. can be changed in a jiffy. Rooting is extremely easy using this box. I did via adb.
In short, a bit too confused with too much knowledge on hand. Looking for wisdom to apply this knowledge correctly. There could be many simpler ways too!!! Any help in this regard is much appreciated.
Thanks and God bless us all. Shalom.
Click to expand...
Click to collapse
Okay don't panic!
Clearly your device is fine by hardware stuff so let's fix some myths and problem of yours.
Firstly,this is mt6592 so you don't have to unlock any boot loader stuff.You can just root your device using kingroot or kingoroot(google it).
For more please read out this whole section,
https://canvasknightroms.blogspot.com/2015/10/rooting-canvas-knight.html?m=1
Now I believe you have root by now. Now all you need to do is get a recovery and as you're on v2 you can find it here,
https://drive.google.com/file/d/0B5W6R0DsDjWTU1o3TEpfWGFsMEE/view
This is philz recovery with OTG support.As you've root just download the IMG file and flash it though flashify,you can find it on Play store.So you've recovery!
Again,these are just suggested methods,you can do all that with other methods too.Also please stop wasting time on stuffs like miracle boxes and etc etc.
Secondly to get your imei back it would be very easy as you've recovery.
https://drive.google.com/file/d/0B6-QF5uchBNhbFlfVk1wOEthbms/view
Just flash this file in recovery and everything shld be fine.
Now to fix Nvram error,just extract the folder from this backup zip,
https://drive.google.com/file/d/0ByuIKfMkBBxBaXBZRHJnNHVRMVk/view
And using any root explorer(I prefer es file manager) go to /data root and replace nvram folder with the folder in this zip
Now the best recovery would be philz recovery for v2 but I greatly suggest you to flash v3 for a variety of reasons and custom ROMs.Yes,you need to shift to v3 to get LP or MM and new updated ROMs though you can still flash available ROMs for v2 which you can find here,
https://canvasknightroms.blogspot.in/2015/10/all-roms-link-for-v2.html?m=1
Very less isn't it? That's because storage barrier in v2.
You can find various mods here,
https://canvasknightroms.blogspot.in/2015/10/mods.html?m=1
You can find correct stock ROMs here,
https://canvasknightroms.blogspot.in/2015/10/stock-rom.html?m=1
Flashing the sim fix above will eventually fix SN too.
And yes many custom ROMs are bundled with SuperSU so you should use that.
To convert from kingroot user to super su use this guide,
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
And lastly mtkdroidtools is a good tool and you should definitely have it just in case for backing up stuff and tinkering with ADB.
With all that said,you should join our Whatsapp group for more faster help and updates by messaging me on my Whatsapp No. +919468519959
Enjoy!
Edit: writing all this is a pain in ass,at least one thanks is deserved
Thank you so much...
Mr.Ak said:
Okay don't panic!
Clearly your device is fine by hardware stuff so let's fix some myths and problem of yours.
Firstly,this is mt6592 so you don't have to unlock any boot loader stuff.You can just root your device using kingroot or kingoroot(google it).
For more please read out this whole section,
https://canvasknightroms.blogspot.com/2015/10/rooting-canvas-knight.html?m=1
Now I believe you have root by now. Now all you need to do is get a recovery and as you're on v2 you can find it here,
https://drive.google.com/file/d/0B5W6R0DsDjWTU1o3TEpfWGFsMEE/view
This is philz recovery with OTG support.As you've root just download the IMG file and flash it though flashify,you can find it on Play store.So you've recovery!
Again,these are just suggested methods,you can do all that with other methods too.Also please stop wasting time on stuffs like miracle boxes and etc etc.
Secondly to get your imei back it would be very easy as you've recovery.
https://drive.google.com/file/d/0B6-QF5uchBNhbFlfVk1wOEthbms/view
Just flash this file in recovery and everything shld be fine.
Now to fix Nvram error,just extract the folder from this backup zip,
https://drive.google.com/file/d/0ByuIKfMkBBxBaXBZRHJnNHVRMVk/view
And using any root explorer(I prefer es file manager) go to /data root and replace nvram folder with the folder in this zip
Now the best recovery would be philz recovery for v2 but I greatly suggest you to flash v3 for a variety of reasons and custom ROMs.Yes,you need to shift to v3 to get LP or MM and new updated ROMs though you can still flash available ROMs for v2 which you can find here,
https://canvasknightroms.blogspot.in/2015/10/all-roms-link-for-v2.html?m=1
Very less isn't it? That's because storage barrier in v2.
You can find various mods here,
https://canvasknightroms.blogspot.in/2015/10/mods.html?m=1
You can find correct stock ROMs here,
https://canvasknightroms.blogspot.in/2015/10/stock-rom.html?m=1
Flashing the sim fix above will eventually fix SN too.
And yes many custom ROMs are bundled with SuperSU so you should use that.
To convert from kingroot user to super su use this guide,
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
And lastly mtkdroidtools is a good tool and you should definitely have it just in case for backing up stuff and tinkering with ADB.
With all that said,you should join our Whatsapp group for more faster help and updates by messaging me on my Whatsapp No. +919468519959
Enjoy!
Edit: writing all this is a pain in ass,at least one thanks is deserved
Click to expand...
Click to collapse
Hi Ak,
I went through your entire post and more or less got most of the useful and helpful information. I have not gone through all the links and will do so in due course.
I have been on your website and have read quite a bit and was happy to see the dedication and commitment to help people like us.
I am sure the phone like you said is stable and away from hardware issues. I will consider flashing vs. 3 soon. Yes, i agree with you there are more choices for vs. 3. I did peep into the website last week to see the big list of custom ROM's for vs. 3.
Last but not the least, God bless you. Shalom.
Frank Morris said:
Hi Ak,
I went through your entire post and more or less got most of the useful and helpful information. I have not gone through all the links and will do so in due course.
I have been on your website and have read quite a bit and was happy to see the dedication and commitment to help people like us.
I am sure the phone like you said is stable and away from hardware issues. I will consider flashing vs. 3 soon. Yes, i agree with you there are more choices for vs. 3. I did peep into the website last week to see the big list of custom ROM's for vs. 3.
Last but not the least, God bless you. Shalom.
Click to expand...
Click to collapse
What about joining our whatsapp group?