Related
*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Thank you for the info! Does sound like an awful lot of work though
jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.
shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Does sound like an awful lot of work though
greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...
With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.
sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!
I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.
jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.
I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?
Hi, I need the ROM for this phone, more specifically, the boot.img file, as the current kernel is for the older, Indian revision of the On5, and my revision, the USA version SM-G550T1, seems not to have any copies of its firmware floating around. I'm running an OS for the SM-G550FY, which has no audio or camera support. Even if the version isn't an exact match, if you bought this phone in the USA, new, in 2016, your boot.img will probably work. I need this kernel guys. Please, if someone has an On5 in the USA, can I please get a copy of your boot.img and possibly system.img? I really care about the boot.img.
Thanks guys
-Subsentient
Firstly, did you try the updated ones at these locations:
http://www.theandroidsoul.com/galaxy-on5-stock-firmware-2-86761/
http://firmwarefile.com/samsung-sm-g550fy
Secondly, why exactly do you need the boot.img, what problem do you think it'll solve? Is there any specific issue with your current ROM that you are trying to solve?
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Subsentient said:
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Click to expand...
Click to collapse
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
prahladyeri said:
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Subsentient said:
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Click to expand...
Click to collapse
There you are! I just cannot emphasize enough that why don't you guys backup your existing ROMs before flashing a new one? It hardly takes five minutes with CWM/TWRP recovery.
In any case, what happens when you flash the Indian ROM (5.1.1)? I guess that could be your only option.
Otherwise, you can put a request on the CyanogenMod thread for your particular Samsung model.
For future reference, perform device backups and all the research before flashing a custom ROM, not after the fact.
EDIT
If you can contact Samsung support, see if you can manage to get a stock ROM from them that you can flash using ODIN or something.
I contacted them already, they basically told me to go **** myself. The missing ROM is a result of bad parameters I accidentally put in to Heimdall/ODIN flasher. I wanted to back up, but ironically, my first attempt at installing TWRP is what destroyed my ROM.
I've downloaded the kernel source code from Samsung and I'll try compiling it myself. If I create a working boot.img, I'll post it here.
prahladyeri said:
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
boot.img is where the kernel is stored. I know, I decompressed it.
Subsentient said:
boot.img is where the kernel is stored. I know, I decompressed it.
Click to expand...
Click to collapse
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
prahladyeri said:
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
Click to expand...
Click to collapse
The kernel on this device does not have loadable module support. It's entirely monolithic. And, I'm having one hell of a time building a kernel this thing is willing to boot.
I really would love just to get a ROM from someone else's SM-G550T or SM-G550T1.
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
bandtab said:
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
Click to expand...
Click to collapse
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Subsentient said:
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Click to expand...
Click to collapse
thank you!
however, i can't install twrp to my recovery partition anymore because i got FRP locked, and i can't go into my settings to disable it now. so i think my only option really is via odin. i'll see what i can do with this though, thank you very much. i did have twrp on there before but after i got frp locked i can't go into recovery mode at all.
I've been losing my mind trying to make this work.
I think if I installed the stock recovery.img it may work, but I can't find it in the files you sent. Would you or anyone else be able to make a copy of it for me? I would be eternally indebted to whoever could.
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
holydude92 said:
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
Click to expand...
Click to collapse
unfortunately smart switch is incompatible with this model phone for the time being.
I got four of these from T-Mobile when we switched from Verizon ($120 for 4 lines). Three of our Verizon phones worked well on T-Mobile (after a few APN tweaks), but my dad's old Galaxy S3 barely worked at all, and when it did, only got Edge for data. So I set one of the On5 phones up for him.
Everything was going great. I put the TWRP recovery on it, rooted it, froze all the bloatware, and backed up/restored his apps from the old S3. However, he wanted me to see if I could restore all his SMS/MMS. I tried restoring that, and the stock Messaging app started FC'ing. I installed Textra, which worked (and saw the old messages), but he never received new texts (even though he could send). So I tried removing Messaging and Textra, as well as the SMS cache (which seemed to be in "Dialer Storage (Phone SMS/MMS). I removed it, but now I'm getting an error every five seconds about "com.android.phone" and can't seem to get rid of it. I tried to restore the dialer storage backup again, but it just seems to sit forever without installing.
I've looked far and wide for a stock ROM... hoping I could just put this mess behind me, but I'm surprised to find it is nowhere to be found.
My other alternative would be to fix the com.android.phone error, but nothing seems to fix it.
Which cynogenmod or any custom os suits for Samsung Galaxy on 5.......please tell me guys.....I am bored with this official os
I was really hoping to come back to this forum and finally see stock ODIN files for this phone. I really, really want to get rid of the MetroPCS ROM I used to fix it.
Has anyone been able to find it?
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?
Hello to all,
first of all sorry for my English, i'm using google translate, I do not know if you can help me here.
I bought this jewel from Gearbest and arrived yesterday.
I would like to unlock the bootloader and root it following this wonderful guide , but I can not get into developer options, I get the error "the settings application crashed abnormally"
I wanted to do this via the toolkit, but in EDL mode the phone is not recognized, maybe because in developer options I have to select the OEM UNLOCK.
The only good thing is that it recognizes usb debugging mode (at least I think) because I see the debug notification icon.
I can not understand where it came from, I went into bootloader mode but did not release me information.
From the onscreen screen I can only provide these info:
model number zte a2017g
version android 6.0.1
kernel version 3.18.20
build number zte a2017gv1.0.0b11
baseband version th.2.0.c1.9-00050-m8996faaaanazm
The MiFlavor version is 4.0
The smartphone does not receive OTA updates. I downloaded the global version (b05) of Nougat, the update with Android started I did not find it (I renamed the rom file in update.zip and put in the root of the SD CARD). I tried through recovery mode but it does not do anything to me, it's as if the smartphone was locked in everything and for everything.
I'm doing well ? How do I update when I download the rom? Can you please help me? Is there any system to interact with this smartphone and unlock it? I do not want to keep a phone that I can not update and root it.
Thanks in advance to who will help.
UPDATE:
I tried to manually install the downloaded ROM, but in recovery mode it does not flash the new rom ... the phone does not even try it !!!
It's as if the phone was locked in everything and I only have to keep the installed rom.
Some idea ?
SuDGLaD said:
UPDATE:
I tried to manually install the downloaded ROM, but in recovery mode it does not flash the new rom ... the phone does not even try it !!!
It's as if the phone was locked in everything and I only have to keep the installed rom.
Some idea ?
Click to expand...
Click to collapse
Hey I would recommend clearing the data for settings if you can. To do this go to your launcher, find the settings icon and either drag or hold down or do whatever it takes to get to the app info. I haven't used stock in a long time so idk. But then go into storage and clear data. Then go and try again.
I do have one question though. How did you get usb adb debugging enabled if you didn't get into developer options at all?
For the second half of your question you won't be able to flash anything without first unlocking the bootloader and flashing TWRP onto the device. For the devices recovery idk which one you meant, but it needs to be TWRP. Good luck!
JTruj1ll0923 said:
Hey I would recommend clearing the data for settings if you can. To do this go to your launcher, find the settings icon and either drag or hold down or do whatever it takes to get to the app info. I haven't used stock in a long time so idk. But then go into storage and clear data. Then go and try again.
I do have one question though. How did you get usb adb debugging enabled if you didn't get into developer options at all?
For the second half of your question you won't be able to flash anything without first unlocking the bootloader and flashing TWRP onto the device. For the devices recovery idk which one you meant, but it needs to be TWRP. Good luck!
Click to expand...
Click to collapse
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
SuDGLaD said:
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
Click to expand...
Click to collapse
What rom are you trying to install? Usually you will be absolutely fine.
SuDGLaD said:
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
Click to expand...
Click to collapse
JTruj1ll0923 said:
What rom are you trying to install? Usually you will be absolutely fine.
Click to expand...
Click to collapse
You can't flash an official zip through TWRP, it will just fail. No brick.
Edit: didn't read OP lol. If you want to update, you have to flash the stock recovery (there are stock recovery flashable zips on the Download Center) then install the update, then get TWRP again. Or you can install a custom ROM (I recommend one based on stock MiFavor 5.0, I think that the best one is ADM Team V3 (the one that's not based on B13), this way you can simply download, flash in TWRP, and you'll be done
JTruj1ll0923 said:
What rom are you trying to install? Usually you will be absolutely fine.
Click to expand...
Click to collapse
Thanks :good:
Choose an username... said:
You can't flash an official zip through TWRP, it will just fail. No brick.
Edit: didn't read OP lol. If you want to update, you have to flash the stock recovery (there are stock recovery flashable zips on the Download Center) then install the update, then get TWRP again. Or you can install a custom ROM (I recommend one based on stock MiFavor 5.0, I think that the best one is ADM Team V3 (the one that's not based on B13), this way you can simply download, flash in TWRP, and you'll be done
Click to expand...
Click to collapse
Thanks mate !!
I installed the rom that you suggested to me, I find it very good, but this phone has very poor support (MiFavor).
SuDGLaD said:
Thanks :good:
Thanks mate !!
I installed the rom that you suggested to me, I find it very good, but this phone has very poor support (MiFavor).
Click to expand...
Click to collapse
Very poor support? It's going to get Android O, and it's got at least 1 update per month (officially). It's unclear whether that ROM you installed will be updated since it's based on an older version, but the latest (B13) breaks a bunch of stuff like Google Play Games, Maps, the GPS works awfully...
Choose an username... said:
Very poor support? It's going to get Android O, and it's got at least 1 update per month (officially). It's unclear whether that ROM you installed will be updated since it's based on an older version, but the latest (B13) breaks a bunch of stuff like Google Play Games, Maps, the GPS works awfully...
Click to expand...
Click to collapse
No no ... do not get me wrong.
My reference is to rom, MiFlavor is really bad. I come from 3 Xiaomi smartphones and I can assure you is another world.
The smartphone is really nice and well balanced (apart from the just enough battery) and I would replenish it a thousand times. :fingers-crossed::good:
I'll put the long story below..but spare those that don't want to read. The short is, I'm not able to ADB Sideload the OTA images as it always fails to verifiy signature at about 40-47%. I've searched many places and not found a fix. So I'm hoping the genuises here at XDA which I frequent can help.
The long story. I've flashed roms for many years. My current device was the Nexus 6p. Running XE Rom I think it was. Flashed an update all was well, but my sim card would not show up. I was on MetroPCS and remembered needing a different radio. Flashed that,still no sim. Decided I'd go back to Stock since those had been updated to 8 by now. Flashed the OTA and followed some steps by another thread on XDA, one of the last was locking the bootloader. I had not booted up so I didn't know if my system was working. My big mistake! I locked my bootloader and don't have a system to boot into so I can enable OEM Unlocking. So now I only have adb sideload, can't flash individual images through fastboot! I think it can be recovered but for some reason the signature verification issue keeps coming up no matter what cable or PC I use.
If anyone has any thoughts I'd love to hear them. I have since moved to a Hauwei Mate SE and am pretty pleased but will not be a flashing phone I don't think. I loved my 6p and it still had lot's of life for me. I hate to sell it for parts at this point.... Thanks for anyone willing to chime in.
tcoursey said:
I'll put the long story below..but spare those that don't want to read. The short is, I'm not able to ADB Sideload the OTA images as it always fails to verifiy signature at about 40-47%. I've searched many places and not found a fix. So I'm hoping the genuises here at XDA which I frequent can help.
The long story. I've flashed roms for many years. My current device was the Nexus 6p. Running XE Rom I think it was. Flashed an update all was well, but my sim card would not show up. I was on MetroPCS and remembered needing a different radio. Flashed that,still no sim. Decided I'd go back to Stock since those had been updated to 8 by now. Flashed the OTA and followed some steps by another thread on XDA, one of the last was locking the bootloader. I had not booted up so I didn't know if my system was working. My big mistake! I locked my bootloader and don't have a system to boot into so I can enable OEM Unlocking. So now I only have adb sideload, can't flash individual images through fastboot! I think it can be recovered but for some reason the signature verification issue keeps coming up no matter what cable or PC I use.
If anyone has any thoughts I'd love to hear them. I have since moved to a Hauwei Mate SE and am pretty pleased but will not be a flashing phone I don't think. I loved my 6p and it still had lot's of life for me. I hate to sell it for parts at this point.... Thanks for anyone willing to chime in.
Click to expand...
Click to collapse
First, if i understand right you tried to flash OTA over custom rom to return to stock?? To go to stock you must flash full system image, not OTA.
And second, why the hell did you lock the bootloader??...you dont lock the BL unless you are 100% stock..
I know i didnt help you much, but if your BL is locked, dont know how to help...maybe someone else know how to unlock it again
Meanwhile read this guide,it will help you to understand some things:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
scrin378 said:
First, if i understand right you tried to flash OTA over custom rom to return to stock?? To go to stock you must flash full system image, not OTA.
And second, why the hell did you lock the bootloader??...you dont lock the BL unless you are 100% stock..
I know i didnt help you much, but if your BL is locked, dont know how to help...maybe someone else know how to unlock it again
Meanwhile read this guide,it will help you to understand some things:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Oh believe me my head hit the wall for sure! I got careless and wasn't thinking straight. No reason to lock the boot loader except it was on a list of steps to get back to stock..and I guess it was late! doh.
There are lot's of posts/videos I've seen that should allow what I'm trying to do with sideload adb but mine keeps getting a signature verification error. Each new full version of a release 7.0 8.0 etc..has the entire rom, images etc. So your suppose to be able to flash those even though they are OTA updates... *shrug*
It's a blur what I did exactly in some areas. I at one point may have tried to flash the set of Stock IMG files as well. But for sure now all I'm left with is a locked phone with who knows what on it! Stock recovery...some form of 7.0.0 that has NYC as letters...that I can find NOWHERE! on any official releases...
Prob trash, I really want that night back..lol.