This question was originally posted here but didn't seem to get much traction. Hoping putting it on its own thread will help me get the answers I'm looking for.
I recently un-rooted my Moto X 2014 to take an OTA update and then re-rooted it again. (Ref: http://forum.xda-developers.com/moto...phone-t3179350). I was really surprised by how smoothly everything went, and it got me thinking that I'd kind of like to update my old Nexus 4 that I keep around to use as a WiFi only device for music and such. I downloaded the factory image (Ref: https://developers.google.com/androi...s/images?hl=en), so my question is: will the process be as simple? Do I just boot into fastboot and flash system.img? As in the first post I linked, I don't want to lose any of my data or settings, nor do I want to lose root.
Current Status:
Android version: 4.2.2
Kernel version: 3.4.0-perf...CyanogenMod
CyanogenMod version: 10.1.3-mako
What I'd like to do is get my phone back as close to stock as possible (from a UX perspective, probably want to keep custom recovery), while maintaining root and without losing any data or settings. Any references for the best way to go about this?
Thanks in advance!
Click to expand...
Click to collapse
If you will flash a factory image you will loose all the data on the phone. Backup the data on a PC or wherever you want and then flash.
You will loose your root too.
---------- Post added at 10:03 AM ---------- Previous post was at 10:01 AM ----------
It is better using Nexus Root Toolkit. Easy and fast. No hassle.
Being that you are on 4.2.2, you are going to need to flash more than just the system.img file. I know there was a change to the radio, and am rather sure there was a change to the bootloader.img as well (not certain). So yes, while you can flash the images directly, you will need to flash bootloader.img, boot.img, radio.img, and system.img at minimum, or, you can just flash the 4.2.2 system.img file from https://developers.google.com/android/nexus/images and then just keep using the OTA updates to move up to the latest LMY48I release. Once you get there, you can then just re-root and install a custom recovery at the same time.
So, I actually followed the steps in your original response (just flashing boot.img and system.img) and that seemed to work great. I'm now running 5.1. I had a little trouble getting TWRP to stick. I kept flashing it, rebooting to system and rebooting to recovery...only to find stock recovery. The trick was to flash TWRP, boot *directly* into recovery (TWRP now), flash SuperSU. I think I'm all set...much thanks!
Okay, so I am noticing some rather odd behavior:
* I can access quick settings once after reboot, then I cannot access it
* when I set the lock screen setting to "Swipe" I still have no lock screen
* the home button doesn't seem to work
Any idea how I might resolve issues like this? I've tried wiping the cache.
Ended up doing a factory reset. It resolved all the issues I describe above.
Cool, yeah, I figured it would work, but you are operating with the old 4.2.2 radio. There is no reason why it would not work, however, usually the new radio versions incorporate fixes, so you might think about flashing those images. (or take the, if it ain't broke, don't fix it approach)
Yep, definitely a taking a, "if it's not broke, don't fix it approach" Just out of curiosity, though, what do you mean when you say "radio"? The radio for the wireless signal? As I said in the original post, this is now a WiFi only device. Not sure if you're talking about the WiFi radio, but it seems to be working great.
I am referring to the radio.img file, which hosts the Baseband for the phone, it affects Wifi and Cellular/SMS/MMS processes. Usually, changes are more to the mobile side than the Wifi side however, but Wifi side fixes sometimes address disconnects from the AP, etc. If Wifi is working well for you, then no need to mess with it.
Related
Edit: Solution found look below!!!
As I posted in a different thread:
I managed to do it, but it was hackish
How I did it:
Used a terminal directly on the tablet, no adb.
I installed the acer chinese update. I 'dd'ed my old system and flexrom and rebooted. After that I checked for updates, and as luck had it, there was one. I tried it, but it failed half way through the procedure.
I rebooted again, then I 'dd'ed a boot.img on mmcblk0p2 from a 1.016 that matched my original system.img and flexrom.img. WITHOUT REBOOTING (I tried that before, it gives a bad kernel checksum and stops, but I assumed on update it would just patch if the file corresponds and re-sign), I then proceeded to do the update. It rebooted, entered recovery, and lo and behold, IT WORKED! So I'm 100% back to stock.
I would imagine that the same procedure would work when manually updating through recovery (using an extracted update.zip).
I used the kernel from here:
http://forum.xda-developers.com/showpost.php?p=14033507&postcount=27
EDIT: The kernel is stock for ACER_A500_1.016.05_COM_GEN1
Take a look at the thread linked below, get the 1.016.05_COM_GEN1 files (system, flexrom, and boot). If you are not offered an online update (System>About>Check for updates), you need the official update.zip from Acer. Extract the update.zip from the official Acer update THAT MATCHES YOUR FLEX VERSION using the XOR 12 method (see here - http://forum.xda-developers.com/showthread.php?t=1065360&page=20 - note in that post the link is for 03_COM_GEN1, NOT 05_COM_GEN1. For 04_COM_GEN1 and 05_COM_GEN1 see here - http://forum.xda-developers.com/showpost.php?p=14052165&postcount=184. For 03 and 04 you will need to find system.img, flexrom.img and boot.img, for 05 they are linked in the thread below).
EDIT: The thread with the images for ACER_A500_1.016.05_COM_GEN1 is here:
http://forum.xda-developers.com/showthread.php?t=1086785
EDIT: You might pull this off for other flex versions as well, but you would need all the files (system.img, flexrom.img, boot.img AND update.zip) from those versions.
PLEASE NOTE THAT THIS ONLY WORKS IF YOU HAVE THE OFFICIAL UPDATE.ZIP FOR YOUR SPECIFIC FLEX VERSION
Wow, I was about to try that!!!
I'll do that now and see how it goes.
Thanks mate!
EDIT: Worked!
I would expect that the reason an update fails on the Chinese one is that it tries to patch the kernel (which is different from the one expected). The update is a bunch of diffs and patches, and almost no full files, so it cannot be applied over anything but the right files.
Yes that is true. The old kermel checksum check was failing.
huxflux2003 said:
EDIT: Worked!
Click to expand...
Click to collapse
Glad to hear it Take that, you sneaky Acer bastards!
adancau said:
As I posted in a different thread:
I managed to do it though, but it was hackish
How I did it:
Used a terminal directly on the tablet, no adb.
I installed the acer chinese update. I 'dd'ed my old system and flexrom and rebooted. After that I checked for updates, and as luck had it, there was one. I tried it, but it failed half way through the procedure.
I rebooted again, then I 'dd'ed a boot.img on mmcblk0p2 from a 1.016 that matched my original system.img and flexrom.img. WITHOUT REBOOTING (I tried that before, it gives a bad kernel checksum and stops, but I assumed on update it would just patch if the file corresponds and re-sign), I then proceeded to do the update. It rebooted, entered recovery, and lo and behold, IT WORKED! So I'm 100% back to stock.
I would imagine that the same procedure would work when manually updating through recovery (using an extracted update.zip).
I used the kernel from here:
http://forum.xda-developers.com/showpost.php?p=14033507&postcount=27
Take a look at the thread, get the 1.016 files, system, flexrom, and boot, and try it.
Click to expand...
Click to collapse
Ahhhh a true milestone, well done.........
Nice work! Two questions:
Does the update work in the US?
I assume gingerbreak still works after the OTA update?
Thx
gingerbreak works
_motley said:
Does the update work in the US?
I assume gingerbreak still works after the OTA update?
Click to expand...
Click to collapse
A warning first: You DO NOT need to do this if you haven't installed the chinese update.zip (update.acer.zip) before, as that is the only one that changes kernels. Also, if you have anything other than ACER_A500_1.016.05_COM_GEN1, it's debatable if you want to do this (if you do read below), it might be better to wait for an official update.
The kernel above is stock for ACER_A500_1.016.05_COM_GEN1
So it works if you have ACER_A500_1.016.05_COM_GEN1 images, or are ok with changing your flex to that (in which case you would need to flash a system.img and a flexrom.img for ACER_A500_1.016.05_COM_GEN1, reboot, and then flash the kernel from the post above before heading off to recovery and updating - HOWEVER as far as I know no one has tried this, though IN THEORY it should work).
Gingerbreak still works, you can get root back after updating.
Just so I'm clear...
I'm at version 1.139.05 but I got here via the Chinese update.zip.
What do I need to do to get back to stock? Do I need to go back to my old system image and flexrom plus a new kernel?
Could someone post clearer instructions?
Thanks
adancau said:
A warning first: You DO NOT need to do this if you haven't installed the chinese update.zip (update.acer.zip) before, as that is the only one that changes kernels. Also, if you have anything other than ACER_A500_1.016.05_COM_GEN1, it's debatable if you want to do this (if you do read below), it might be better to wait for an official update.
The kernel above is stock for ACER_A500_1.016.05_COM_GEN1
So it works if you have ACER_A500_1.016.05_COM_GEN1 images, or are ok with changing your flex to that (in which case you would need to flash a system.img and a flexrom.img for ACER_A500_1.016.05_COM_GEN1, reboot, and then flash the kernel from the post above before heading off to recovery and updating - HOWEVER as far as I know no one has tried this, though IN THEORY it should work).
Gingerbreak still works, you can get root back after updating.
Click to expand...
Click to collapse
Thanks guys, I did restore using the Chinese update.zip last week and I am currently sitting at kernel 2.6.36.3 with flashed system img=Acer_A500_1.104.05_COM_GEN1, but with recovered Chinese kernel modules for wifi etc. I also flashed a flexrom.img from this build as well. I didn't flash the boot.img from this build, but was thinking about it until huxflux2003 reported the check-sum failure.
So, I am trying to decide what I am going to do. It sounds easy enough to get back to stock now, but I may wait for the official update next month that has 3.1. At this point, I suppose we are assuming that it will be a full update.zip that will work on any tablet (god I hope so). It's about time they gave us a full recovery image...I will be beyond disappointed if they don't. Let's also just hope we can still gain root easily after this.
One more question, if I use all the images from ACER_A500_1.016.05_COM_GEN1 that were posted, does this have to match what I had originally had in any shape or form? It sounds like since all the pieces are from the same build, everything will be fine regardless of what you had to begin with. Is this right?
Thx
To your last question - Theoretically yes, it should work, and I guess you don't need to match what you originally had. I can only speculate, logically though it would makes sense. You definitely need all the images to be from the same build (system+flexrom+boot.img). You also need the official update for that build.
heyoh said:
Just so I'm clear...
I'm at version 1.139.05 but I got here via the Chinese update.zip.
What do I need to do to get back to stock? Do I need to go back to my old system image and flexrom plus a new kernel?
Could someone post clearer instructions?
Thanks
Click to expand...
Click to collapse
To get back to stock you need the three images for your build - system, flexrom, and boot. If there is no online update available, you also need the update.zip for that build (extracted from an official acer update using the XOR 12 method - do a search).
Alternatively, I suppose you could switch to a new build for which you could find all the necessary files (but it hasn't been tried).
Flash system.img using dd. You might need to re-root. Reboot, flash flexrom.img. Reboot once more. Make sure your wifi works (you might need different kernel modules).
Look to see if there is an online update (Settings > About > Check for updates). If there is, cancel it. Flash boot.img on mmcblk0p2. DO NOT REBOOT.
If there was an online update available, now it's the time to perform it. After it's done you will get you back to stock 1.139.05.
If there isn't any update, make sure you have the update.zip on the root of your microSD. Turn off the tablet, then turn it back on holding the volume key closest to the power button. Do not let go of that button until you see some text in the corner. At that moment the update would begin. Once rebooted you will be back to stock.
Hope I've explained it better this time, and it works ok for you. If not, you need to go through the chinese update again. Good luck.
adancau said:
To your last question - Theoretically yes, it should work, and I guess you don't need to match what you originally had. I can only speculate, logically though it would makes sense. You definitely need all the images to be from the same build (system+flexrom+boot.img). You also need the official update for that build.
Click to expand...
Click to collapse
It worked for me too! Thanks again for the tip. I am now at the latest build and ahead of the US update schedule from what I can gather
It asked me to update after I flashed the ACER_A500_1.016.05_COM_GEN1 build system.img and flexrom.img. Even from the US it prompted just fine since I was on ACER_A500_1.016.05_COM_GEN1 build and not ACER_A500_1.104.05_COM_GEN1 as the former is what the differential patch targets.
I cancelled the update once I saw it presented and then blew on the boot.img from the ACER_A500_1.016.05_COM_GEN1 build. Then, without rebooting, I downloaded and applied the update (but with a little hiccup, see below). Now I am at Acer_A500_1.139.05_COM_GEN1 and didn't lose any user apps or settings etc.
Had a scary point though that I will share as it may help others. The first time I tried, the zip wouldn't downloadload and I was getting an HTTP 403 error. I cleared the systemupdater app and FWUpdateService data. I also killed the services and then I was stuck. Instead of conceding to reflashing the Chinese update.zip and starting over, I unzipped the Chinese update.zip and grabbed the boot.img from it. I then dd'ed that image back to the boot partition and rebooted again. It came back up and I this time I was able to do the system update successfully. Whew!
Followed instructions by OP and it worked perfectly! Back to stock and updated.
I think I'll be keeping these system images for next time I brick and have to flash the Chinese update.
Any chance of someone uploading the extracted update.zip for the new Acer_A500_1.139.05_COM_GEN1 so I can update manually using this method.
Thanks in advance
I used the above method to update to 1.139.04 from 1.016.04.
However my kernel is still 2.6.36.3-00001-gf991e5d instead of the 2.6.36.3 everyone else is reporting?
tianqi said:
I used the above method to update to 1.139.04 from 1.016.04.
However my kernel is still 2.6.36.3-00001-gf991e5d instead of the 2.6.36.3 everyone else is reporting?
Click to expand...
Click to collapse
If you directly flashed a 1.139.04 image your kernel has not been updated. You had to flash a 1.016.04 image, flexrom and boot, and then run the update.
You MIGHT have some luck regardless by running the update.zip now (I used it on mine one time when I updated like you did, and it seemed to work, but I have not noticed the kernel number). Be prepared to have to reflash if something goes wrong though.
I did reflash system, flexrom, and boot from 1.016.04...
Second time is still the same...
Kernel is still 2.6.36.3-00001-gf991e5d...
I've been trying to update from 4.1.2 to 4.2.2, but I deleted some stock apps and now the update is failing. I've tried flashing it manually and OTA, and various other things, but nothing has helped so far. Has anyone else had this problem?
The OTAs are for use with [size=+2]unmodified[/size] factory ROMs.
bftb0 said:
The OTAs are for use with [size=+2]unmodified[/size] factory ROMs.
Click to expand...
Click to collapse
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.
wipeout4wh said:
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.
Click to expand...
Click to collapse
My post tells you that you have the wrong expectation about what OTAs are capable of... and that you are probably the 200'th dude to come in here and say
"Wahhh! The OTA doesn't work on my heavily modified stock ROM!".
If you want it to work without exerting any mental effort, return the /system, boot, and recovery partitions back to 100% pure stock corresponding to whatever release your original ROM was based upon, and run the update. Then re-flash your recovery and re-perform all your /system mods, starting with a flash of the same root kit you started with.
Note that the the update you are contemplating also includes a bootloader update - performed the safest way possible (signature checking performed by the existing boot loader). Doing it the manual way (via fastboot) is quite dangerous, even for experts. If you have a 3g version there is also a radio update which also should not be attempted in any other way than via a pure stock OTA install including use of a stock recovery.
Make a full Nandroid backup before you begin anything - and get a copy of that backup off of the tablet as well as a failsafe measure. If you screw things up moving forward, at least you will be able to start over from where you are right now.
If you have been operating using best practices, you should already have a nandroid backup of the pure-stock /system & boot images. TWRP allows you selectively restore individual partitions. Few users seem to know how to actually make a backup of stock recovery partitions, but you can get that out of oldblue910's archive site - find the link in the OTA thread.
good luck
wipeout4wh said:
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.
Click to expand...
Click to collapse
He's telling you the plain and simple truth. Want the OTA- as it stands, you're out of luck. Either return to stock and then flash the OTA, or flash the 4.2.2 factory image. That's it. Nothing more. That anyone even bothered to answer this uselessly redundant thread is a miracle in and of itself.
Sent from my Nexus 7 using Tapatalk HD
Be very careful doing this, you could brick your phone if you aren't - you have been warned.
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware - it is also the same as your device ID if you type 'adb devices' with your phone hooked up with USB debugging enabled for adb commands.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!
To save you some pain you can more thank likely flash the system image and boot without wiping your /data.....if for some reason you ran into issues you'd still be able to go into factory recovery and do a reset which deletes data.
Also to anyone who actually uses AVG the pro version is free on amazon appstore today only.
Also you don't have to INSTALL twrp...you can opt to only boot into it using the instructions in the system image thread if you prefer to keep stock recovery.
If I had to bet I'd say you'll get the USA notifications but we will find out on next update.
famewolf said:
To save you some pain you can more thank likely flash the system image and boot without wiping your /data.....if for some reason you ran into issues you'd still be able to go into factory recovery and do a reset which deletes data.
...
Also you don't have to INSTALL twrp...you can opt to only boot into it using the instructions in the system image thread if you prefer to keep stock recovery.
Click to expand...
Click to collapse
Totally correct on the TWRP thing, though I prefer it to stock recovery, and updates work just fine with TWRP as well.
As for the not wiping - again, correct, I just come from the 'do a total wipe' school of flashing things, to avoid any possible weirdness
purple.epod said:
Be very careful doing this, you could brick your phone if you aren't - you have been warned.
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!
Click to expand...
Click to collapse
When restoring the UE40 firmware the first time you go into system update checker you need to delete the existing UE40 update as it kept it around...you should then be able to check updates as normal.
Manually update
At the end of your post, you say that you update manually.. where do you get your update ?
Manually update
At the end of your post, you say that you update manually.. where do you get your update ?
Click to expand...
Click to collapse
I mean that when the next update comes out, if I can't use the OTA update, I'll wait for someone to upload it here, and then I'll manually apply it. If you follow the directions in my post, you'll be totally up-to-date as of August 15th, 2015 - I'm referring to the next update, whenever that may be.
Thanks for the guide!
Was able to update my Canadian idol 3 without installing twrp
Just fastbooted into it and did a backup of my old CDN setup and restored with the file above the whole update process took about 15min
If **** hits the fan I can still restore back to the original CDN ROM with twrp and my backup.
Dt2w works every time now and chrome scrolling is vastly improved definately worth updating. I may flash back to Canadian system image when they finally release it
To anyone on stock Canadian firmware please post once an OTA is available (and what carrier you are on)
anyone else have lost LTE and get bad network speeds after converting? I had 60mbps with canadian firmware and now i get around 5mbps and lots of network drops.
jpfk said:
anyone else have lost LTE and get bad network speeds after converting? I had 60mbps with canadian firmware and now i get around 5mbps and lots of network drops.
Click to expand...
Click to collapse
I'm not in canada but I would think if more folks were experiencing issues like that they would have mentioned them here already. Did you do a factory reset and start clean or did you keep your previous data around after changing firmware? In this case I'd really recommend starting clean with the exception of using tools like Titanium Backup to backup all your user apps+ their data (or you can use Helium if you don't have root).
famewolf said:
I'm not in canada but I would think if more folks were experiencing issues like that they would have mentioned them here already. Did you do a factory reset and start clean or did you keep your previous data around after changing firmware? In this case I'd really recommend starting clean with the exception of using tools like Titanium Backup to backup all your user apps+ their data (or you can use Helium if you don't have root).
Click to expand...
Click to collapse
I had cleared the cache and did a factory reset only after i confirmed the flash of the US firmware was ok. (i have a really bad SD card which keeps unmounting and didnt want to risk being stuck with a non-functional device). In addition to the network problems i also still had the performance issues everyone mentionned was fixed in latest update. I just did a complete wipe and flashed the US again, now the performance is much much better but i still get only H+ with about 7mbps instead of LTE. But the good thing is the drops seems to have stopped.
jpfk said:
I had cleared the cache and did a factory reset only after i confirmed the flash of the US firmware was ok. (i have a really bad SD card which keeps unmounting and didnt want to risk being stuck with a non-functional device). In addition to the network problems i also still had the performance issues everyone mentionned was fixed in latest update. I just did a complete wipe and flashed the US again, now the performance is much much better but i still get only H+ with about 7mbps instead of LTE. But the good thing is the drops seems to have stopped.
Click to expand...
Click to collapse
you probably tried this but... check that the APN didn't get changed/reset from when lte was working.
That was actually the problem, i did not realize it was a different APN for LTE so it looked normal when I first checked. Thank you very much
Has anyone gotten the Canadian stagefright update pushed to their phone yet?
doesn't work for me!
purple.epod said:
Be very careful doing this, you could brick your phone if you aren't - you have been warned.
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware - it is also the same as your device ID if you type 'adb devices' with your phone hooked up with USB debugging enabled for adb commands.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!
Click to expand...
Click to collapse
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread http://forum.xda-developers.com/idol...dates-t3163745
I also have the twrp-2.8.7.0-idol3 installed on my phone.
I also followed this thread
to find the way to install that ROM, without success. i also installed the root from the zip file in the twrp, but again without success!! but when i open from the twrp the directory TWRP/Backups/XXXXX/ and i copy the .win and the .win.md5 files the phone doesn't see the when i click restore
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread
Click to expand...
Click to collapse
This guide is for converting a Canadian 6045i to a US 6045i - both are identical models with simply slightly different software. It won't work with a European 'Y' model like you said you have.
punkal said:
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread http://forum.xda-developers.com/idol...dates-t3163745
I also have the twrp-2.8.7.0-idol3 installed on my phone.
I also followed this thread
to find the way to install that ROM, without success. i also installed the root from the zip file in the twrp, but again without success!! but when i open from the twrp the directory TWRP/Backups/XXXXX/ and i copy the .win and the .win.md5 files the phone doesn't see the when i click restore
Click to expand...
Click to collapse
Step 1) Make a backup on the device so it creates the directory path you need.
Step 2) Take the time datestamp folder from the backup you have and put it in the folder that has the other time datestamp folders. It's not a complicated process. Installing the "root" from the zip file does you no good because the time datestamp folders need to be under a folder with your device id (ie what shows up when you do adb devices).
While the restore process IS the same your questions should be asked in the system image thread if you don't have a 6045i.
According to @petrov.0 it's better for you to install the official 10 06 update (or his modified one in the system image thread) as it updates files in SEVERAL partitions other than system and boot. Again discussion needs to be there.
Apologies to @purple.epod. This will hopefully redirect folks back to the system image thread. I have a line that states to follow your restore tutorial but use their own backup but did not intend for them to be asking questions HERE.
purple.epod said:
This guide is for converting a Canadian 6045i to a US 6045i - both are identical models with simply slightly different software. It won't work with a European 'Y' model like you said you have.
Click to expand...
Click to collapse
Now i understand why it doesn't work. And where can i find the rom for my as i have everything wiped? do you know i only found ROM Arde-Dev-Team-v1_5.0.2 but it doesn't work!
---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------
famewolf said:
Step 1) Make a backup on the device so it creates the directory path you need.
Apologies to @purple.epod. This will hopefully redirect folks back to the system image thread. I have a line that states to follow your restore tutorial but use their own backup but did not intend for them to be asking questions HERE.
Click to expand...
Click to collapse
Unfortunately i can bakup anything as i have wiped everything on the phone!:crying:
I know i'm really stupid, but i do that as it was a step as a process of installing a new ROM as mine was corrupted!:crying:
punkal said:
Now i understand why it doesn't work. And where can i find the rom for my as i have everything wiped? do you know i only found ROM Arde-Dev-Team-v1_5.0.2 but it doesn't work!
---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------
Unfortunately i can bakup anything as i have wiped everything on the phone!:crying:
I know i'm really stupid, but i do that as it was a step as a process of installing a new ROM as mine was corrupted!:crying:
Click to expand...
Click to collapse
Why are you posting this HERE when even the message you quoted states questions should be asked in the system image thread?
famewolf said:
Why are you posting this HERE when even the message you quoted states questions should be asked in the system image thread?
Click to expand...
Click to collapse
Really sorry!
i've been taken by terror and panic.!
Hi, everyone. First post here so I'm coming up to speed on a lot of things.
I bought a brand new Moto X pure yesterday and was excited to get to work on rooting. The whole process went smooth. I currently have an entirely rooted device on Marshmellow. There was a hitch at the end of it, though. Everytime I flip my wifi to 'on' it goes off on its own the very next second.
The logical conclusion was to search this forum and try the widely suggested tip of flashing NON-HLOS.bin in fastboot. Well I did...and I'm still having the same problem. I've searched through a whole bunch of wifi related threads and there doesn't seem to be much lack of success after flashing the bin in fastboot.
Do any of you fine folks have any tips or will I have to flash a nandroid back to the 'stock' Marshmellow I had made right after flashing TWRP?
I know when flashing original firmware you have to flash the non hlos file then follow with commands that erase modemst1 and modemst2. This might be worth investigating???
I am not sure if this would help?
Note: Problem & solution is for lollipop but the cmds I think are for MM and LP.
Problem:http://forum.xda-developers.com/showpost.php?p=64582653&postcount=146
Solution for the guys wifi problem.
http://forum.xda-developers.com/showpost.php?p=64584506&postcount=149
If not, my bad.
You must reflash the Modem again. I have the same issus and after reflashing Wifi working fine.
OneCoconutTwoCoconut said:
Hi, everyone. First post here so I'm coming up to speed on a lot of things.
I bought a brand new Moto X pure yesterday and was excited to get to work on rooting. The whole process went smooth. I currently have an entirely rooted device on Marshmellow. There was a hitch at the end of it, though. Everytime I flip my wifi to 'on' it goes off on its own the very next second.
The logical conclusion was to search this forum and try the widely suggested tip of flashing NON-HLOS.bin in fastboot. Well I did...and I'm still having the same problem. I've searched through a whole bunch of wifi related threads and there doesn't seem to be much lack of success after flashing the bin in fastboot.
Do any of you fine folks have any tips or will I have to flash a nandroid back to the 'stock' Marshmellow I had made right after flashing TWRP?
Click to expand...
Click to collapse
Reflash the modem again and it will work. If not then just restore your backup and re root
jlbuck6212 said:
Reflash the modem again and it will work. If not then just restore your backup and re root
Click to expand...
Click to collapse
Reflashing the MM modem does not work. I've got the same problem.
I had the same problem also and it worked for me. If it's not working then you may want to do everything again step by step to make sure you are not missing anything. Go back into twrp, wipe cache and dalvic and reboot before you do anything. If it is turning off then it is your modem and it is faulty so you may want to re download the modem and try again. Make sure you aren't flashing the lollipop non hlos with mm.
Thanks for the help, everyone. In the end, reflashing did not do the trick (I wonder if I was doing something wrong), but I managed to get my wifi back after restoring my nand. This was the thread I used to help gain root. Could I have missed a step in there during the process?
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?