I am on firmware 4.3 that I rooted a while ago. I would like to unroot 4.3 however I cannot figure out how. I thought I could flash stock 4.3 via Odin but there are no .tar versions of 4.3. Help?
albo23 said:
I am on firmware 4.3 that I rooted a while ago. I would like to unroot 4.3 however I cannot figure out how. I thought I could flash stock 4.3 via Odin but there are no .tar versions of 4.3. Help?
Click to expand...
Click to collapse
Do you have the full stock version of 4.3 or the modified (unrooted) version? You can check your phone's settings and build number to see if it's MJB or MJ2. You can try unrooting from the SuperSU app. The definitive solution to unrooting is indeed to flash a complete stock image. An Odin flashable *.tar file was recently developed. There have, however, been reports on outcome. You can flash custom recovery to your phone (either of CWM or TWRP) and use the instructions in the thread below to download and flash a complete stock restore.
http://forum.xda-developers.com/showthread.php?t=2658486
Hello, I recently just updated my Rogers SGH-i317M to 4.3, which then downloaded a system update which put it at 4.4. I was running Jedi X20, which is based on 4.1.2, when I first tried updating, I flashed the "4.3param_tz" file in odin, and was left with an error screen saying I need to recover using Kies, so I downloaded the official release, flashed via odin, and thats how I got to where I am now. I want to try the "Ditto Note 3" rom, "Sky Note Air 4.3", "Mean Bean" and "Beanstalk". My main question is, can I just start flashing these roms like I was before on 4.1.2, or do I need to use the specific kernel listed on their page? Before you needed a specific kernel to run a touchwiz rom or an aosp rom, so is it still the same? Or can I use my stock 4.4 kernel and try both aosp and tw roms now? If so could you point out the kernels I would need? And educate me on anything else I should know about before flashing 4.3 and 4.4 roms, (I'm not worried about warranty), this would be greatly appreciated. Thanks for your time in reading this and helping me out, much appreciated!!
Regardless of where u are, I'd Odin to Rogers stock KK 4.4.2. Then Odin Twrp recovery, boot into twrp recovery and flash SU v.1.99. Finally choose your rom and flash away. This way you are on the lastest KK 4.4.2 Bootloader and KK Modem/Baseband.
just_visiting said:
Regardless of where u are, I'd Odin to Rogers stock KK 4.4.2. Then Odin Twrp recovery, boot into twrp recovery and flash SU v.1.99. Finally choose your rom and flash away. This way you are on the lastest KK 4.4.2 Bootloader and KK Modem/Baseband.
Click to expand...
Click to collapse
I did all that except flash SU 1.99, so I tried flashing SKynote Air and it didnt work, upon restarting my phone it said no os is available. So I tried restoring from the backup I made of the official 4.4.2 Samsung rom in twrp, didn't work. Tried Odin, didn't work. Then I tried flashing the Skynote rom again and it worked. So I'm afraid of flashing any other roms now.
I have an AT&T I747, and tried to install the OTA update to 4.4.2. After completing & rebooting, the phone got stuck on the white AT&T screen. I flashed stock 4.3 back onto the device, but now have no phone/mobile networks, and the IMEI & Baseband show as "Unknown". I do have Wifi. I've seen some similar issues on the forums but nothing exact - tried flashing the MJB modem (flashed fine, but no change), and tried flashing the MJB modem & bootloader (get "assert failed" followed by several getprop commands). After a couple of days chasing this, thought I should ask rather than keep stumbling & possibly making things worse. Anyone have any advice?
I was rooted but otherwise stock when I tried to do the OTA update.
I'm using TWRP 2.6.3.1 to flash, ODIN 3.07, and the files I flashed were (from links found in this forum):
4.3: I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5
MJB modem: d2att_I747UCUEMJB_modem.zip
MJB modem & bootloader: d2att_I747UCUEMJB_modem.zip
Any help greatly appreciated.
Try flashing a 4.4.2 touchwiz rom and factory resetting.
DO NOT try to flash the 4.3 bootloader or firmware! You are lucky it didn't flash or you'd now be hard bricked! The MJB modem may not work on the NE4 firmware, so make sure you have that modem.
DocHoliday77 said:
Try flashing a 4.4.2 touchwiz rom and factory resetting.
DO NOT try to flash the 4.3 bootloader or firmware! You are lucky it didn't flash or you'd now be hard bricked! The MJB modem may not work on the NE4 firmware, so make sure you have that modem.
Click to expand...
Click to collapse
Thanks for the advice! So would you recommend flashing 4.4.2 first, and then an NE4 modem if I don't have it, or reverse that order?
Gaussfan said:
Thanks for the advice! So would you recommend flashing 4.4.2 first, and then an NE4 modem if I don't have it, or reverse that order?
Click to expand...
Click to collapse
OK, I went ahead and flashed 4.4.2 and I'm back up & running - thank you!
Gaussfan said:
OK, I went ahead and flashed 4.4.2 and I'm back up & running - thank you!
Click to expand...
Click to collapse
which ROM and files did you flash? in what order? I'm in the same boat. It works in 4.3 with "Baseband Unknown". However, If I try to update to 4.4.2 , the phone will freeze after "Samsung" logo.
What firmware are you on?
Install terminal emulator and enter this:
getprop ro.bootloader
If it returns NE4, that's the modem you need. If it returns MJB or MJ2, do not flash the NE4 modem or it'll hard brick. Basically, you should use whatever modem matches the firmware/bootloader version you currently are running.
DocHoliday77 said:
What firmware are you on?
Install terminal emulator and enter this:
getprop ro.bootloader
If it returns NE4, that's the modem you need. If it returns MJB or MJ2, do not flash the NE4 modem or it'll hard brick. Basically, you should use whatever modem matches the firmware/bootloader version you currently are running.
Click to expand...
Click to collapse
Was at stock 4.3 . Received OTA update and froze in the middle of updating.
I used this to get back to stock 4.3 I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5
Everything works , but Baseband Unknown. If flashed NE4 modem, Baseband is back and phone working again, but can't turn on Wifi.
[email protected]:/ # getprop ro.bootloader
getprop ro.bootloader
I747UCUFNE4
- install TWRP and flashed 4.4.2 stock zip -> freeze after Samsung logo after reboot
- restored to stock 4.3 again, install TWRP and flashed 4.4.2 OTA zip -> freeze after Samsung logo after reboot
- restored to stock 4.3 again, used stock recovery and flashed 4.4.2 OTA zip -> freeze after Samsung logo after reboot
Ok, this is what happens with wifi....
4.3 firmware with 4.4.2 rom = no wifi
4.4.2 firmware with a 4.3 rom = no wifi
In both cases you need a custom kernel. Since you are updated to 4.4.2 firmware, if you want to use a 4.3 rom, you will have to flash either the MJ2 or kt747 kernel for wifi to work. The NE4 modem is the only modem you can use now.
Your boot hangs will be solved by factory resetting. I doubt there's any way around this at this point.
I suggest flashing the NE4 stock rom from enewman17. Then factory reset. It should reboot and work fine now.
---------- Post added at 02:44 AM ---------- Previous post was at 02:42 AM ----------
Oh, and do not try to use the ota again.
DocHoliday77 said:
Ok, this is what happens with wifi....
4.3 firmware with 4.4.2 rom = no wifi
4.4.2 firmware with a 4.3 rom = no wifi
In both cases you need a custom kernel. Since you are updated to 4.4.2 firmware, if you want to use a 4.3 rom, you will have to flash either the MJ2 or kt747 kernel for wifi to work. The NE4 modem is the only modem you can use now.
Your boot hangs will be solved by factory resetting. I doubt there's any way around this at this point.
I suggest flashing the NE4 stock rom from enewman17. Then factory reset. It should reboot and work fine now.
---------- Post added at 02:44 AM ---------- Previous post was at 02:42 AM ----------
Oh, and do not try to use the ota again.
Click to expand...
Click to collapse
Thx for the tips. Will try soon.
However, once the phone froze after Samsung logo, I could not access custom recovery anymore. In the case of stock recovery, I could get back to it but there were no point. Phone still froze after Wipe.
Try refreshing your recovery with Odin. Try rebooting recovery again. Then try to factory reset before flashing the rom, and again afterwards.
Good luck and let me know how it goes!
DocHoliday77 said:
Try refreshing your recovery with Odin. Try rebooting recovery again. Then try to factory reset before flashing the rom, and again afterwards.
Good luck and let me know how it goes!
Click to expand...
Click to collapse
After 5 hours working on this phone, I think I'm happy which what I have now.
1- Restored back to stock 4.3
2- Flash custom recovery
3- Flash NE4 modem
4- Flash ktoonsez kernel Touchwiz JELLYBEAN 4.3 VERSIONS
Everything is working now. I will not update this to 4.4.2 b/c no matter which ways I used to go to 4.4.2 either through custom or stock recovery, phone would freeze after Samsung logo ( already did factory reset before and after flashing ROM/update)
Thx for your help.
Hi first of all I want to ask that I had stock 4.1.2 when I bought the phone, rooted it, flashed mj5 bootloader and successfully flashed the xperia z-ized rom based on 4.3 on my N7100. Then I wished to switch to dn3 rom but I still did not like it so I reverted back to stock 4.1.2 and updated to stock 4.4.2 via OTA updates. My question is, while updating via OTA to stock 4.4.2, can it be possible that I lost my mj5 bootloader and it was replaced by samsung's proprietary bootloader?
After using stock 4.4.2 I thought to check out the LS rom so I rooted, flashed philz recovery but the ROM does not boot at all and while trying to revert back to stock 4.1.2, ODIN displays the fail message. What did I do wrong and what should I do to overcome this? Thanks.
You've locked your bootloader because you upgraded to latest official which also comes with Knoxx.
hey can anyone help me? i've recently reverted my note 2 back to stock via odin and everything seemed fine. When the phone booted and i went through the setup process it always hangs. No matter what i do it always hangs. I've tried reflashing it and rebooting it over and over again but it always hangs. anyone know why this keeps happening?
Are you flashing the latest stock ROM? You're performing a factory reset before booting the ROM for the first time?
audit13 said:
Are you flashing the latest stock ROM? You're performing a factory reset before booting the ROM for the first time?
Click to expand...
Click to collapse
Yup latest stock rom, and before i flashed via odin i deleted my previous rom via twrp and formatted internal storage so its 100% clean
I've downgraded a Note 2 sgh-i317m to 4.1.1 from 4.4.2 by flashing a stock 4.1.1 ROM from sammobile.com in order to network unlock the phone. Flashing the stock 4.1.1 ROM tripped knox and could be installed via Odin because the 4.1.1 ROM from sammobile.com did not contain a 4.1.1 bootloader so I wound up with a stock 4.1.1 ROM on a 4.4.2 bootloader. After unlocking, I flashed the stock 4.4.2 ROM again and the the phone worked as it should.
I'm not sure which phone you have and I'm not sure downgrading and upgrading will work in your case but it's something you may want to look into.
audit13 said:
I've downgraded a Note 2 sgh-i317m to 4.1.1 from 4.4.2 by flashing a stock 4.1.1 ROM from sammobile.com in order to network unlock the phone. Flashing the stock 4.1.1 ROM tripped knox and could be installed via Odin because the 4.1.1 ROM from sammobile.com did not contain a 4.1.1 bootloader so I wound up with a stock 4.1.1 ROM on a 4.4.2 bootloader. After unlocking, I flashed the stock 4.4.2 ROM again and the the phone worked as it should.
I'm not sure which phone you have and I'm not sure downgrading and upgrading will work in your case but it's something you may want to look into.
Click to expand...
Click to collapse
I've managed to get the phone working (N7100) and it seems to run fine on Nougat. I did some testing and indeed it would always crash on setup with kitkat roms. I wonder why this is the case....
It is strange that kit kat causes a problem.
Have you tried using a different version of twrp to wipe the system before flashing with Odin? Can't think of anything else that may solve the problem.