Related
I am not very much familiar with all intricacies of Android system but i have played around rooting and putting customer firmwares on few devices.
I have AT&T Galaxy S3 with following detals:
Baseband: I747UCUEMJB
Version: 4.3
I had the device rooted in the past but recently un-rooted it and reset the flash counter as well and did factory reset. Did all that since i wanted to use ISIS and couldn't make it work on a rooted S3. Seems it used to work before till they updated ISIS app to patch it.
Now AT&T got 4.4 update and my phone detects it, downloads it but while installing fails at 32%. I have seen many threads where people faced similar issues due to their phones being rooted. Seems something on my phone didn't reset to default.
I found one post which mentions that i can download UCUEMJB_to_UCUFNE4_Firmware_update.zip and load it to phone using TWRP. As i understand, this will update the baseband but android version still remains at 4.3 (?). Is that the path i should be looking for or i am shooting in wrong direction? I want to stay on default firmware since i like to use ISIS till they keep running those cashback promos
Would appreciate some feedback.
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
DocHoliday77 said:
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
Click to expand...
Click to collapse
Thanks for the reply.
Just to confirm so that i don't mess up, i will apply the following(is modem same as firmware?) and then try OTA.
I747UCUEMJB: modem_CWM_I747UCUEMJB.zip
No. The modem is only one part of the firmware. Firmware includes bootloaders, kernel, system, modem and more.
Hello,
I just bought my first Galaxy device (had a CDMA LG for a while, and I have a Nexus Tablet), and I am looking at how to get this new phone set up right. I bought my i747 retail, so I was unable to unlock it. However, now I'm struggling with finding the right method for upgrading, rooting, etc. I know nothing about knox or any of these Samsung intricacies. Could someone please give me a little guidance on how to go about getting to the OS and status that I'm looking for? This is what I've done so far:
Came unrooted with 4.1.2 stock rom
Unlocked using legit unlock code
Tried OTA updates, but none were available (must be because of unlock)
Rooted w/ ODIN using 4.1.1 file based of MrRobinson method. (http://forum.xda-developers.com/showthread.php?t=1739426)
Now I keep getting popups like process. ... .acore,media, etc. stopped.
I'm looking to ideally get a custom recovery (either CWM or TWRP, whichever is better) and either kitkat Touchwiz or possibly kitkat nexus stock (I read somewhere that it was possible). Also, i just bought it, and have the code still, so I don't mind deleting everything if needed. Regardless, I'd like the ability to get it back to pure stock with no flash counter (I have a manufacturer's warranty I want to use if need be).
Could someone please just give me a little guidance? I'm pretty capable with rooting, etc., so you'd only need to lead me to other threads, etc. that will take me where I want to go. Thank you very much.
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
audit13 said:
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
Click to expand...
Click to collapse
Well, the bad news is I already flashed using MrRobinson's instructions, and now my phone is barely workable, as things like process.android.media and Touchwiz keep crashing. I was able to install the info app though, and my bootloader is listed as I747UCDLK3. Thanks again though, and let me know what else you need from me.
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
audit13 said:
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
Click to expand...
Click to collapse
Thank you, but wouldn't OTA updates install Knox, which would basically void my warranty if I tried to flash anything after that? And, I've checked for OTA updates twice, once on 4.1.2 and on 4.1.1, and both times it said my software was up to date.
I spoke with StoneyJSG about my situation, and he suggested that I go to stock 4.1, root w/ saferoot, then flash a kitkat custom rom without Knox through TWRP. That way, I could use triangle away and flash stock unrooted if I needed to send it in.
Although, I'm not sure if I should do that, as I thought I read that you need to update the radio and bootloader first before you can install a custom kitkat rom from jelly bean, but I'm still not entirely sure how that works.
The most recent release of many custom ROMs will not work but you may not have a signal without an updated modem and you should not be running updated modems on an older bootloader. Doing this could brick your phone.
With a rooted system, OTA updates will not work.
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
jateed said:
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
Click to expand...
Click to collapse
What is your cell service? If not AT&T, you will never get OTA.
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
audit13 said:
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
Click to expand...
Click to collapse
Well, I have an AT&T model which I unlocked and will be putting on Cricket at the end of the week (when my plan month is set to end). Right now there's no SIM in it, and I've been doing everything over wifi. I looked up whether the carrier had something to do with the OTAs, and I was told that Samsung sent the updates out, not AT&T, so I figured that the carrier info was irrelevant. I now wonder what my options are.
Can I manually flash 4.3 stock without tripping the knox warranty void?
Does Towelroot/Xposed framework trip the Knox void flag?
If I can update to 4.3/4.4 and root without tripping the knox flag, I might just manually update and just run towelroot and xposed to modify my OS the best I can until my warranty runs out.
If I can't root it at all once I'm on 4.3+, then I'll just sit on 4.1.1 for a few months until I can't stand it anymore and just void the warranty anyway.
Thanks again everyone. This whole knox/binary counter thing is not something I dealt with on my CDMA LG or Nexus, so I was totally in the dark about how it all worked. This is also my first GSM phone, so all those intricacies are new to me too. Once I know about manually flashing stock and running towelroot/xposed, I think I'll be in good shape.
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
audit13 said:
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
Click to expand...
Click to collapse
Excellent. If I did flash stock, i would just use ODIN, then factory reset to wipe the caches. And that's good to know about the KK rom, as I would probably update straight to 4.4 if at all (I've read a lot of bad things about 4.3 on the S3), but not if it means I cannot root safely and cleanly.
I'll check out the custom roms for 4.1.1. I know that flashing the rom and/or a custom recovery will trip the binary counter, but I can just use triangle away to clean that up. Do you know if there is a list of custom 4.1.1/4.1.2 roms somewhere, or do I need to scour the older threads here?
Thank you very much audit13 (thanks to StoneyJSG and pre4speed as well). You have been immensely helpful and really brought me up to speed on everything surrounding S3 customization. Needless to say it's way more complicated than what I've dealt with from LG and Google/Asus. (I mean, i could root my nexus with a single click using Wugfresh's toolkit)
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
audit13 said:
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
Click to expand...
Click to collapse
Oh, so what other way can you flash a stock rom, if not through ODIN or a custom recovery? Regardless, it seems as though I really should not dive into 4.3+ until I'm ready to concede that my warranty is over. There are just too many potential pitfalls and headaches.
On the lighter side, I've found a few 4.1.2 based custom roms that have some promise. I'm going to post them here in case anyone has opinions on them, or if someone else in my situation sees this thread and wants to go custom 4.1 too:
Hyperdrive RLS16
http://forum.xda-developers.com/showthread.php?t=2176793
Slim Bean-d2
http://forum.xda-developers.com/showthread.php?t=1865262
Jedi Academy
http://www.teamandroid.com/2013/12/...oid-412-jedi-academy-jelly-bean-custom-rom/2/
Jelly ‘Beans’
http://www.teamandroid.com/2013/04/...ndroid-412-att-galaxy-s3-sgh-i747-custom-rom/
I was also torn when I got my s3 that was running 4.1.2. I downgraded to 4.1.1, sim unlocked the phone, used it on stock 4.1.2 for about a week to make sure everything was working, hardware wise, upgraded to stock 4.4.2, installed a custom recovery and a custom ROM. I wasn't too concerned about the warranty since I got the phone as a free upgrade and had no intention of using the s3 as my daily phone. I kept it as a backup until my niece needed and phone and then it went to her. It's been over a year and there are still no problems with the phone.
Hello all
I've been watching the forum for years now and I admit there are plenty of nice guides ( I even rooted my z3 dual first try using the guides)
Now I have purchased Z5 premium dual e6883 model and it's been sitting in the box for almost 2 months now, waiting on a root guide
Most of the guides are either for different models like e6853 or for experts who are into testing and experiencing options
I know there are successful attempt to root this model so I ask if there is any comprehensive (complete) guide on how to get the root for this device?
I would appreciate if anyone can refer to a post or even a guide that I can follow
Model 6883
Android 5.1.1
Build 332.0.A.6.170
Karnel 3.10.49-perf-g9a3c9a8-04532-g75e6207
Many thanks for all the support
Any help please?
I think the first thing that you want to know is, currently you can't root without your bootloader unlocked.
(Please Google search for more details regarding the "side effects" of the unlocked bootloader Sony smartphones, though tobias.waldvogel has created the DRM functions restoration mod.)
My advice, why don't you wait until Android 6 rolls out? Maybe more developers would focus on the latest ROM and bring out various ROOT methods (for unlocked bootloader and locked bootloader maybe?)
I wanted to ROOT my Z5 premium dual since the first day I bought it, but it is a sad thing to lose the DRM keys (my opinion), and unless the DRM functions restoration mod becomes "better", I will not unlock my bootloader just yet...
Novioo said:
Hello all
I've been watching the forum for years now and I admit there are plenty of nice guides ( I even rooted my z3 dual first try using the guides)
Now I have purchased Z5 premium dual e6883 model and it's been sitting in the box for almost 2 months now, waiting on a root guide
Most of the guides are either for different models like e6853 or for experts who are into testing and experiencing options
I know there are successful attempt to root this model so I ask if there is any comprehensive (complete) guide on how to get the root for this device?
I would appreciate if anyone can refer to a post or even a guide that I can follow
Model 6883
Android 5.1.1
Build 332.0.A.6.170
Karnel 3.10.49-perf-g9a3c9a8-04532-g75e6207
Many thanks for all the support
Click to expand...
Click to collapse
keep waiting.. I received 6.0.1 ota on an amazon z5p e6883. The phone worked famously.. .loved it.
Some compulsive and sick part of me wanted to root the phone.. no good reason.. the phone worked perfectly.
I didn't research enough to know that unlocking the bootloader wipes drm keys.. (my hastiness there, no one to blam)
I unlocked the bootloader -
Followed a few guides on this site (full of some knowledgeable folks, but most are tards.. including the site designer who decided to fill the site with shockwave flash ads..WTF)
I can safely say, NONE of the guides worked on this model.
So I've got no rooted phone, but lost DRM keys, so lost phone functionality.
Here's my understanding of the procedure, asuming the obvious.. you have fastboot, flashtool and adb all working
1. unlock bootloader
2. get modified 'premissive' kernel (there are a couple flying around.. I tried both Z5PDual_AndroPlusKernel_v5b.zip, and E6883_MM_ROOTABLE_PERMISSIVE_boot.img during different attempts..
3. get twrp (I tried both twrp-2.8.7.0-E6883-20151130_material.img and twrp-3.0.2-0-E6653-20160504.img. on different runs)
4. flash boot with permissive or andro plus
6. flash recovery with 2.8 or 3.0 twrps
7 reboot and watch You'll see the sony banner then yellow led... Press and hold vol down during yellow led)..
8. Blam. you're in twrp.. All good right.. time to install su.zip or su and drm repair zip...
gravy right..
not for me..
my phone doesn't boot at any point after this point. The OS starts, but I get either a continuous animated 'sony waves' banner OR Android is Starting.. starting apps. (I've waited a long time for this to progress but did not make it to OS..
My recovery..
Flash tool 9.0.22
Sony Xperia Z5 Premium(E6883). FW release : 32.2.A.0.224_R6C. Customization : India Generic_1299-6238
After this, I'm back in business, but without unlocked bootloader and no DRM keys or patch..
during debugging I tried several combinations and found that the OS will not boot after these two modified kernels are pushed
AND twrp won't install without the modified kernel
Would be appreciate if someone could guide me through this, without saying "did you unlock your boot loader..?"
Otherwise, I'd suggest taking that phone out of the box and using it stock.. it's a great phone.
giz
I'm going to side with Giz on this one. Take the phone out of the box and use it without trying to unlock the bootloader. It is a nice phone and the camera is pretty awesome as long as your DRM keys are intact. I'd love to unlock my bootloader too so I could root the phone but I'm not willing to loose some functionality to do so. One thing that really annoys me is those 2 worthless SIM card icons in the tray. They are worthless. All we need are the signal icons. Anyway that's my .02.
foopy said:
I'm going to side with Giz on this one. Take the phone out of the box and use it without trying to unlock the bootloader. It is a nice phone and the camera is pretty awesome as long as your DRM keys are intact. I'd love to unlock my bootloader too so I could root the phone but I'm not willing to loose some functionality to do so. One thing that really annoys me is those 2 worthless SIM card icons in the tray. They are worthless. All we need are the signal icons. Anyway that's my .02.
Click to expand...
Click to collapse
Pardon the pun, but I think I found the "root" of the problem ... at least for myself anyway..
this is for those who *HAVE* unlocked the boot loader.
I couldn't get my 6.0.1 phone (32.2.A.0.224) rooted. I've got the E6883 Dual Sim.
To recap:
I've Unlocked
I've downloaded E6883 MM Permissive Kernel
I've Downloaded E6533 TWRP
What happens after this is that my phone will not ever boot. It just hangs on the animated xperia waves screen.
My Fix is to reflash with flashtool
During Flash AFTER installing the permissive kernel I noticed that the flash tool detected a .163 build number. I thought this was odd because I just flashed to .224
I believe the issue is that the 6883MM permissive boot loader (required to install twrp) was built from a 163 kernel AND the boot loader is not compatible with the system flash that loads up.
I believe all that is required for root on 6.0.1 is a new 6883MM permissive (built using a .224 parent).
Does any of this theory hold any water?
This thread has helped me for E6853 http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
The procedure supports E6833/E6853/E6883 models.
try to downgrade to backup TA, with firm .209 5.1.1 china and had problems,i not to wipe downgrade .. I used xperi firm for download.the cell begins with many errors , xperia z5 premium e6883, i found firm .209 Malaysian but flashtools show firm Z5 normal to flash, I downloaded and blog xperia same name e6886
@Novioo , i have E6833, on 6.0.1 ,,,, build .224
when you were on 5.02 and 5.1.1, KINGROOT can root it EASILY,
however 6.0 , 6.0.1 onwards there is no known xploit (yet)
so i rooted via replacing stock kernal with MODIFIED KERNAL
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
if you are ready to UNLOCK you BOOTLOADER then download your modified kernal from
https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!ngpAhbSL
---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------
danilo_scala said:
try to downgrade to backup TA, with firm .209 5.1.1 china and had problems,i not to wipe downgrade .. I used xperi firm for download.the cell begins with many errors , xperia z5 premium e6883, i found firm .209 Malaysian but flashtools show firm Z5 normal to flash, I downloaded and blog xperia same name e6886
Click to expand...
Click to collapse
downgrading did not work with me also,,,,, malaysian version keeps crashing
YasuHamed said:
@Novioo , i have E6833, on 6.0.1 ,,,, build .224
when you were on 5.02 and 5.1.1, KINGROOT can root it EASILY,
however 6.0 , 6.0.1 onwards there is no known xploit (yet)
so i rooted via replacing stock kernal with MODIFIED KERNAL
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
if you are ready to UNLOCK you BOOTLOADER then download your modified kernal from
https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!ngpAhbSL
---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------
downgrading did not work with me also,,,,, malaysian version keeps crashing
Click to expand...
Click to collapse
@YasuHamed you downgrade wipe all?, i no and have problem with firm china .209, malaysian i found to my xperia premium e6883 but in flashtools show to z5 normal, strange I was afraid to flash, i dont no if bug flashtools
giz02 said:
Pardon the pun, but I think I found the "root" of the problem ... at least for myself anyway..
this is for those who *HAVE* unlocked the boot loader.
I couldn't get my 6.0.1 phone (32.2.A.0.224) rooted. I've got the E6883 Dual Sim.
To recap:
I've Unlocked
I've downloaded E6883 MM Permissive Kernel
I've Downloaded E6533 TWRP
What happens after this is that my phone will not ever boot. It just hangs on the animated xperia waves screen.
My Fix is to reflash with flashtool
During Flash AFTER installing the permissive kernel I noticed that the flash tool detected a .163 build number. I thought this was odd because I just flashed to .224
I believe the issue is that the 6883MM permissive boot loader (required to install twrp) was built from a 163 kernel AND the boot loader is not compatible with the system flash that loads up.
I believe all that is required for root on 6.0.1 is a new 6883MM permissive (built using a .224 parent).
Does any of this theory hold any water?
Click to expand...
Click to collapse
I haven't unlocked my bootloader or attempted to root the phone so I don't have any experience to go on for this particular phone. I do know that sometimes you have to do a factory reset even though you have just flashed a new kernel and/or system image. If you haven't done so you might try that. Also keep in mind after a factory data reset the phone usually takes considerably longer to boot up than normal the first time so be patient. There is a thread that contains a modified .224 kernel so make sure you are using that one and not the .163. After flashing everything and BEFORE first boot perform a factory data reset in recovery and see if that makes a difference.
danilo_scala said:
@YasuHamed you downgrade wipe all?, i no and have problem with firm china .209, malaysian i found to my xperia premium e6883 but in flashtools show to z5 normal, strange I was afraid to flash, i dont no if bug flashtools
Click to expand...
Click to collapse
@Novioo i tried downgrading but could not find right version for E6833. Malaysian version kept crashing.
later i found stock modified roms for E6833 so i made deal with the devil and gave up my DRM KEYS by unlocking the boot loader,,,, but since the stock modified kernal has DRM Stimulation it works fine...
in my views, sooner or later, with or without DRM KEYS restored, you will be unlocking your boot loader anyway!
Z5 deserve to be FREED
i found this firm but in flashtools show to z5 and no premium, i dont no if bug http://www.xperiablog.net/forum/res...dual_e6883_32-0-a-6-209_malaysia_generic.519/
foopy said:
I haven't unlocked my bootloader or attempted to root the phone so I don't have any experience to go on for this particular phone. I do know that sometimes you have to do a factory reset even though you have just flashed a new kernel and/or system image. If you haven't done so you might try that. Also keep in mind after a factory data reset the phone usually takes considerably longer to boot up than normal the first time so be patient. There is a thread that contains a modified .224 kernel so make sure you are using that one and not the .163. After flashing everything and BEFORE first boot perform a factory data reset in recovery and see if that makes a difference.
Click to expand...
Click to collapse
Just wanted to say thanks for taking the time for the response.
I did try the factory reset, then let the phone sit overnight on one occasion, but to no avail.
It turns out that there was a parallel thread using the modified 224 kernel that got me much futher along, but I had other issues with is, so I ended up rolling back to the 163 build on 6.0.0 with root and drmfix. I'll look again once in a few weeks I think. I took the time to get my phone set up again, at least this time I have root and the luxury of running titanium.. such a pain to get everything manually installed and configured.
Hello guys,
For some reason, my phone shows that my SIM is locked ( I was on RR 6.0). I need to flash the 4.1.1 firmware for Koodo to unlock the SIM.
Can anyone send me a link for this firmware?
Thank you!
You don't need Koodo to unlock the sim. Just flash the stock LJ2 firmware with Odin and use the dialler menu to permanently network unlock the phone.
https://forum.xda-developers.com/showthread.php?t=2014982
Maybe this will work: http://rapidgator.net/file/0207e341...yos.com/samsung-galaxy-note-2-stock-firmware/
I know it's been a long time, but did this procedure actually WORK? AFAIK, Koodo Note 2s never came with less than KitKat, and we all know that Samsung has blocked downgrading though its bootloader starting then.
The reason I ask is I'm looking for a spare phone for mine as a backup and can't seem to find one on which I can load my Jellybean 4.1.2 CM based phone image.
Well this an interesting post, I have a similar problem, I have 2 exact Note 2 phones one with custom firmware (4.1.1) one without, I would like to copy/clone the stock firmware to my other (as I somehow managed to delete the stock firmware on it)
Now I have made a backup with TWRP and copied it to the other phone but TWRP refuses to install it, it tries to install and gets most of the way but at the very end I get the 255 error "install failed"
Why can't I copy/ install this backup?
Do I need to to use some other recovery software or make a backup some other way.
Thanks
Old faithful said:
I know it's been a long time, but did this procedure actually WORK? AFAIK, Koodo Note 2s never came with less than KitKat, and we all know that Samsung has blocked downgrading though its bootloader starting then.
The reason I ask is I'm looking for a spare phone for mine as a backup and can't seem to find one on which I can load my Jellybean 4.1.2 CM based phone image.
Click to expand...
Click to collapse
The note 2 sgh-i317m was used by Telus, Rogers, and Bell.
This downgrade method works. I've used it to network unlock four note 2 models.
The stock 4.1.1 firmware from sammobile.com did not contain a bootloader file which allowed me to flash it using Odin on a phone running a stock 4.4.2 rom.
audit13 said:
The note 2 sgh-i317m was used by Telus, Rogers, and Bell.
This downgrade method works. I've used it to network unlock four note 2 models.
The stock 4.1.1 firmware from sammobile.com did not contain a bootloader file which allowed me to flash it using Odin on a phone running a stock 4.4.2 rom.
Click to expand...
Click to collapse
Man, if this really works it's going to solve all my problems. Are you saying you can flash the 4.1.x ROM on top of the the 4.4.2 bootloader (presumably one could deselect the bootloader from the 4.1.x ROM if it was included - sorry I'm quite rusty at this, haven't used Odin in years), so that the phone may be running ICS or JB despite having a 4.4.2 encrypted (locked) bootloader?
The idea is being able to load Clockworkmod recovery and from it, the rooted 4.1.2 backup on my external sd card...
Sorry if it's been asked before and if I may be confused - Thing is, I haven't done this type of tweaking in 5 years
I could flash a stock 4.1.1 ROM from sammobile.com on top of a stock 4.4.2 ROM because the stock 4.1.1 ROM didn't contain a bootloader. I did this to use the menu method to network unlock the sgh-i317m; however, the phone cannot stay on a stock 4.1.1 ROM with a 4.4.2 bootloader because the phone cannot connect to a cellular network with this 4.1.1 ROM/4.4.2 bootloader combination. After I unlocked the phone, I either re-flashed a stock 4.4.2 ROM or a new custom ROM.
The bootloader on the Canadian Note 2 was never locked the way it was with some USA carriers.
audit13 said:
The bootloader on the Canadian Note 2 was never locked the way it was with some USA carriers.
Click to expand...
Click to collapse
Are you saying the Koodo/Rogers.... 4.4.2 Note 2 bootloader is NOT locked on our phones, ergo, that I could downgrade to 4.1.1 including its bootloader successfully?! If so I'm set, I could purchase a used one on kijiji and simply reload my old Bell based ROM backup on it I simply look for a way to load my 5 year old Rooted ROM onto a newer version of the phone. I have on it apps that won't run on 4.4.2 that I sorely miss on my tablet (which runs 4.4.4)
The bootloader is not locked which allows for the installation of TWRP and cwm but it cannot be downgraded.
audit13 said:
The bootloader is not locked which allows for the installation of TWRP and cwm but it cannot be downgraded.
Click to expand...
Click to collapse
In other words it does allow for installing the 4.1.1 ROM for unlocking the phone, but it can't can't actually be used with the 4.1.1 ROM... What if I simply reinstalled the 4.4.2 modem, wouldn't that work?
I now I'm asking quite a lot - but in my case if I haven't been able to find a used phone that hadn't been at some point 'upgraded' and consequently became shackled (I've been looking for over a year now) in which case I might as well mourn it and move on to a new phone and start the fight for freedom all over again Honestly, I've grown tired of having to fight for the basic right of ownership against the relentless push for slavery that is the general trend in technology, to force people away from freedom of using the software they prefer and force them into a system where they must follow the dictates of corporate giants so perfectly exemplified by the cell phone, computer and browser based service industry.
Like Frederick Douglass famously said "Power concedes nothing without a demand. It never had and never will"... In other words if you want freedom and true control, you MUST FIGHT the providers and the manufacturers whose prime interest is to keep you enslaved
Installing the 4.4.2 modem will install but the stock 4.1.1 dialer doesn't work with a 4.4.2 modem and 4.4.2 bootloader from what I recall. It's been a long time since I had a note 2.
Hello I'm currently running 4.4.2 with root and I've been thinking about upgrading to marshmallow. I just wanted to know whats the best way going about it. I'm assuming that I'm going to have to re-enable the software updating app that I disabled for I didn't get OEM updates then upgrade to marshmallow and re-root using one of the guides or would a root keeping app or Survival mode on superSU possibly work? I also believe I have TWRP installed from when I rooted my phone before, I'm not sure if that's important info. Also side note, would their be a way to keep the 4.4.2 touch buttons on the bottom of the screen? They make more sense to me then the new ones. Device info below
AT&T
android 4.4.2
software version D85010d
Model number LG-D850
You can't root on marshmallow so if you want root DO NOT update with that app. the easiest way is to just flash a rom. i have the verizon version (vs985) and all i have to do to flash a custom stock rom, is to flash the right modem before flashing the rom, then flashing modem again after the rom and bam, i just flashed a marshmallow rom from kitkat 4.4.2. you can also downgrade that way just flashing the appropriate modem before and after and bam.! but i dont know about your version, you should definitely check the att&t G3 subforum. you need to be careful and read thoroughly so you don't brick. the thing with vs985 is that there are modems out there that can hardbrick the device, however, it may not be the same for others but, just in case you should read.
Thank you I'll look into that. So far I found this https://forum.xda-developers.com/att-lg-g3/development/rom-stock-bumped-marshmallow-v30a-t3661194 but I still got more research to do since I'm unfamiliar with flashing modems and whatever "bumped" is exactly. Hopefully this weekend I'll have more time to look into this.