Related
Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz
Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...
Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz
Bootloader 70.13
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.
Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz
Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz
Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz
You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen
Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz
This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!
How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.
When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium
Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz
I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help
Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.
ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.
I originally followed this:
http://www.modaco.com/topic/341011-ultimate-guide-to-the-huawei-u8800/
and rooted the phone
Then I followed this:
http://forum.xda-developers.com/showthread.php?t=1420728
and I read this:
http://forum.xda-developers.com/showthread.php?t=1492957
I thought that the phone had 2.3.5 on, and then after a while (After I flashed the new zip file), I realised that it only had 2.3.3 on and it won't get past the Huawei screen ie: it's stuck
I backed up the current ROM, but I've no idea on what to do now that it's bricked. I've tried fixing permissions, connected via USB and using the "adb logcat" command when I got the reply
/sbin/sh: exec: line 1: logcat: not found
And it's just stuck at the boot screen. Just wondering if any one can help?
Re-flash firmware.
Sent from my U8800 using Tapatalk 2
Qqqxxxzzz said:
Re-flash firmware.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
I haven't the foggiest as to why my last post didn't go through. Any way, I did do that and I tried to restore my current ROM as well - remember it hasn't had the 2.3.5 update
On another note, my post also serves as a "hello" post considering that I didn't realise that I had an account here with zero posts until recently. I must have made it a while ago so hello
Hi, I didn't notice it because I use tapatalk.
Sent from my U8800 using Tapatalk 2
That's not a bricked people. A bricked phone is one that does not turn on no matter what, does't react in any shape or form, no screen, no vibration, no sound, no led when plugging usb or charger, no pink mode, no pc access to the phone, no nothing.
Your phone goes to huawei loading screen! How is that a bricked phone? Just reflash The ROM and do triple wipes. Search the forum for that.
flash stock rom. 2.3 or 2.2
not bricked
i can trustly say that it's not bricked, a brick phone means "unusable hardware tools"
the implementation that you explained can not cause a brick operation, you only have to teach your phone to work - that its possible to install the original stock rom.
original stock rom images also contains hubbable hardware working scripts and images.
so you can get your system back and also imei.
fjsferreira said:
That's not a bricked people. A bricked phone is one that does not turn on no matter what, does't react in any shape or form, no screen, no vibration, no sound, no led when plugging usb or charger, no pink mode, no pc access to the phone, no nothing.
Your phone goes to huawei loading screen! How is that a bricked phone? Just reflash The ROM and do triple wipes. Search the forum for that.
Click to expand...
Click to collapse
Thanks for that. I'll go off to search for a stock ROM
EDIT: Which stock ROM do I use?
http://coraldrive.net/users/androidz/583/u8800 stock roms
Once I've got the correct ROM, then I'll probably follow this:
http://forum.xda-developers.com/showthread.php?t=1011527
I'm putting that link in, to help others and in case I can't find it. I'm from the UK if that helps
So today, I loaded the general overseas version stock ROM and formatted the Micro SD card to FAT32 and it loaded with android 2.2 on it (yay)
However, I can't download the official 2.3 ROM because the Huawei site is having problems with it's server, and every file sharing site I've seen has deleted it for "copyright infringement" Why the hell Huawei even requested for it's removal, when it doesn't even work from their own site, I have no idea
So, just wondering if there's any kind people out there that can send us the official 2.3 ROM either by email or a public dropbox link, which can then be deleted?
Thanks
EDIT: I may have found something:
huaweidevice.com/worldwide/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDQzNTg=
Just an update to show what I've now done, in case any one else has the same problem. Go here:
huaweidevice.com/worldwide/downloadCenter.do?method=toDownloadFile&flay=softw are&softid=NDQzNTg=
(XDA forums won't allow me to insert external live links just yet)
Download the file from there. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1011527
Follow step 12 and onwards from here:
http://forum.xda-developers.com/showthread.php?p=22682229#post22682229
I also deleted the dload folder, in case I accidentally revert it to stock ROM. I also had to run SuperOneBoot again because it was unrooted after I flashed the official ROM
To get clockword mod, go here:
http://forum.xda-developers.com/showthread.php?t=1420728
Once you've got clockword mod, a rooted phone etc... and if you follow the guide posted above, then you can also install custom ROM's on to your Huawei device
Thanks to the XDA people for providing these guides
This thread is for users who have a 2017g model that is stuck in DFU mode.
If you would like to assist in the investigation, please reply here. I'll be sending links to test programs to try to diagnose and repair devices.
With any luck, we can get the devices back to normal within a few days.
Reserved
I had this problem, but luckily I could send it back and get a new one on warranty. I was very careful when unlocking the new one ?
Skickat från min ZTE A2017G via Tapatalk
Can more people who are stuck in DFU mode PLEASE contact tennear? I worked with him before and he really knows what he is doing. He's the only one who I think could be able to help you restore your device to working state.
Please help him, so A2017g users like me know they have a trick up their sleeve in the case the BL unlock goes awfully wrong
Thank you.
@tennear keep us updated. I'm planning to give up root in order to get this week's B08 update and i'm not sure if flashing the system with twrp will go smoothly.
Thank you for you work and dedication to help other people.
I have two people that are able to help now. But more is always better. If you have a G model and you can access DFU (regardless if you are bricked or not), you can help test. Linux is my preferred OS, but I can also build for Win64 if needed.
razorsbk said:
@tennear keep us updated. I'm planning to give up root in order to get this week's B08 update and i'm not sure if flashing the system with twrp will go smoothly.
Thank you for you work and dedication to help other people.
Click to expand...
Click to collapse
If you are Lock bootloader and have TWRP you CAN flash B08 , just need to mod. The updater_script in other for the B08 to be install, but YOU WON'T BE ABLE TO ROOT unless you unlock bootloader and I'll be posting something about that later today or coming days.
DrakenFX said:
If you are Lock bootloader and have TWRP you CAN flash B08 , just need to mod. The updater_script in other for the B08 to be install, but YOU WON'T BE ABLE TO ROOT unless you unlock bootloader and I'll be posting something about that later today or coming days.
Click to expand...
Click to collapse
I'm rooted without unlocking bootloader (tenfar's method).
So you are saying I can flash the upcoming update safely from TWRP by editing updater script and removing getprop & assertprop lines from it?
I also have system modifications.
Sent from my ZTE A2017G using Tapatalk
razorsbk said:
I'm rooted without unlocking bootloader (tenfar's method).
So you are saying I can flash the upcoming update safely from TWRP by editing updater script and removing getprop & assertprop lines from it?
I also have system modifications.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
Ok, I don't want to go off topic here, but YES you'll need to edit updater_script and look and bookmark if possible my thread about Updates ,I'll be posting B08 as soon the full update hits ZTE site. If you want to talk about Updates post there , so we can keep this thread on topic.
I agree. See you there.
Sent from my ZTE A2017G using Tapatalk
tennear said:
I have two people that are able to help now. But more is always better. If you have a G model and you can access DFU (regardless if you are bricked or not), you can help test. Linux is my preferred OS, but I can also build for Win64 if needed.
Click to expand...
Click to collapse
I have a G model and I am using Linux (based on ArchLinux). I can use Windows 10 if needed, so OS should not be a problem.
So if you need some testing, I can help
Hi, I would love to help,
I have a G model and I have TWRP and unlocked bootloader but u can access DFU mode
I am using windows
I'm afraid that I have not been successful getting out of DFU mode. I have tried several things, but the device refuses to switch into EDL mode.
According to the user who has a bricked device, he got bricked by running "axon7backup -d" without any image files present. The tool wrote something to both boot and recovery partitions. I don't know what that something is -- zeros, random data, ... who knows.
So it seems that if you are careful and only flash recovery properly, the device should not brick. But I cannot test -- someone else will need to confirm.
Now that this investigation is concluded, I will be posting my own tool shortly.
Always remember: to avoid bricking your device, never flash both boot and recovery at the same time.
^^Is there even a reason to flash the boot/kernel? The main reason why most of us would use the axonbackup tool is to flash twrp.
gpz1100 said:
^^Is there even a reason to flash the boot/kernel? The main reason why most of us would use the axonbackup tool is to flash twrp.
Click to expand...
Click to collapse
The only reason why tenfar had the tool to Flash boot is because he had the boot sign and pre-rooted for Lock bootloader units.
^^Got it. I thought about keeping the BL locked, but decided unlocking it would cause fewer headaches and be less restrictive.
That is correct, there is no real reason to flash your boot partition now that the images provided by tenfar are not compatible with the latest updates from ZTE.
However, the real danger remains: if you run "axon7backup -d" with no files to write, it is reported to write bad data over both boot and recovery and brick your device.
I highly recommend using my tool instead. I can guarantee that it will never write both boot and recovery in the same session.
tennear said:
That is correct, there is no real reason to flash your boot partition now that the images provided by tenfar are not compatible with the latest updates from ZTE.
However, the real danger remains: if you run "axon7backup -d" with no files to write, it is reported to write bad data over both boot and recovery and brick your device.
I highly recommend using my tool instead. I can guarantee that it will never write both boot and recovery in the same session.
Click to expand...
Click to collapse
The command help indicates -d is to dump only. My understanding is nothing is written to the phone when reading from it? Are you saying that's not the case?
gpz1100 said:
The command help indicates -d is to dump only. My understanding is nothing is written to the phone when reading from it? Are you saying that's not the case?
Click to expand...
Click to collapse
Yes, that is what I am saying. According to a PM that I received, the user ran "axon7backup -d" without any other files in the directory. The tool flashed something to both boot and recovery partitions. No idea what it flashed. But then the device was bricked. And because 2017g cannot enter EDL mode directly, there is no way to unbrick.
hi i have china version of axon 7 A2017 and have the same problem with my device (stuck in dfu mode after Flashing SuperSU).Will there ever be a way to fix this problem? I am depered :crying:.
Hey,
I just wanted to inform you about an issue that happens in TWRP. I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B. I think TWRP should inform the user that rebooting will brick the device. What are your thought on that? It could be done similar to how TWRP informs the user to install supersu if the phone isnt rooted.
This would be really helpful as it would prevent many people like myself from bricking their phones.
Now if I connect my pixel it only shows Qualcomm HS-USB Diagnostics 900E (COM3). No bootloader, fastboot, or recovery is present.
Here are a coupe of links of other people that did the same thing:
https://productforums.google.com/forum/#!topic/phone-by-google/sXjCoQ8glac
http://forum.xda-developers.com/pixel-xl/help/pixelxl-bricked-t3517310
Thanks!
Edit
I contacted the devolper of TWRP and he says that it should have boot loader regardless.
Here is the history: At work 3pm, froze Android system apk and some other telephone apps to troubleshoot something, I know I shouldn't do this. Resulted into boot loop. Go into twrp recovery and wipe data. It boots up fine and I see it downloading updates but it never goes through, I attempt to go back to recovery and apparently it's back to the stock recovery even though I originally had TWRP rc1.
I get home at 7 pm, I want to install TWRP rc1 so I send the command to boot into TWRP and then I install the zip, then I install sr5 SuperSU. I change to slot b and it's been bricked since.
It arrived November patch and it stayed like that since I was rooted. It attempted to install 7.1.1 but it returns installation problem. I think the bootloader was removed because of the failed update.
Your in download mode. I had this happen once on my Nexus 7. I held power for 90 seconds and it went back to bootloader. However I dont know about the pixel. Its still a new and uncharted device.
You also have to realize TWRP is in an unstable stage. You really should not flash anything until its in final release mode. I know I know... Hindsight is 20/20.
If you have insurance you could get it replaced.
Good luck.
sorry to hear dude..
bahehs said:
I think TWRP should inform the user that rebooting will brick the device. What are your thought on that?
Click to expand...
Click to collapse
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
bahehs said:
I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B.
Click to expand...
Click to collapse
Does anyone have an understanding about how something like this could potentially happen? Do these phones ship without information on the second slot? After my phone OTA updated, I switched slots without issue back to the previous version by following the information from Android Police. I'm not clear on what exactly would need to happen for the noted situation, and how someone could potentially get into a similar situation, unless the phone ships without information on the second slot. Switching slots worked without issue the times I tried it, but my phone had been through a typical OTA update before switching slots, so there was definitely information on both slots when I tried it.
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Scott said:
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Click to expand...
Click to collapse
Same, mine is on slot B. Dunno if it came that way, but it is only two days old. I let it take the OTA then flashed Francos kernel and then booted the root su image.
I really regret not watching more closely how all of impacted which slot it was on.
Sent from my Pixel XL using XDA Labs
Everytime you get OTA update you will switch slots. If you update via flashall it will say on the same slot.
This mode can't be a complete brick but it doesn't look like anyone has a solution yet. Maybe we will need some HTC tool?
Also when you root or modify you take responsibility for anything that happens. There is always a chance of a brick. At least Google will still probably warranty these devices.
Sent from my Pixel using Tapatalk
CZ Eddie said:
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
Click to expand...
Click to collapse
This comment is unnecessary and serves no purpose in this thread.
Sent from my Pixel XL using XDA-Developers mobile app
I'm okay with that.
Updated op with more info
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
reb1995 said:
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
Click to expand...
Click to collapse
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Sent from my Pixel XL using Tapatalk
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
Sorry for the long delay. No I was not rooted.
yearn2burn said:
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Click to expand...
Click to collapse
Bump
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
You are right a failed OTA could brick a pixel phone
DR3W5K1 said:
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
You are right a failed OTA could brick a pixel phone
Click to expand...
Click to collapse
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
aholeinthewor1d said:
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
Click to expand...
Click to collapse
Failed bootloader flash? The Google .IMG files contain bootloader's.
EDIT I do believe the flash_all.sh flashes the bootloader
So you cant even run ADB commands ( a.k.a Bootloader / Recovery mode ), its a hard brick or soft ?
Does your PC detect the device when its on and connected via USB ?
Why did you switch slots in the first place ? if your taking an OTA on a rooted device with SU an OTA wont even apply via TWRP, you have to manually flash with the flash-all.bat script or part by part and the A / B boot slots are handles by the updates so you don't accidentally boot with a slot with no bootloader.
There is no need to swap A / B manually and if your going to flash and want to play with the A / B slots you should at least flash the partitions first but hindsight is a wonderful thing.
Aboot here might be your friend, but as this device is still quite new to many devs and or the tools might not be publicly available . . .
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?