Downgrade Ml1 to Stock Rooted Mj2 Links Updated - Samsung Galaxy Mega

Downgrade Ml1 to Mj2 Rooted Stock
***Please Do Not Use My Links Or Work Except For Your Personal Use Without Asking Permission
***Please Do Not Repost My Links Without Asking Permission
I9205 ONLY***
***CWM MOD ONLY: DO NOT ATTEMPT THIS WITH TWRP***
***DO NOT ATTEMPT TO FLASH
Follow these instructions exactly
***Make a backup of current Rom before attempting
** I suggest you have the stock tar file on hand just in case
File Size is 2gb
1. Download all the files from link below: 11 total
2. Open CWM Backups Folder
3. Place the Downloaded Files in a single Folder
4. Place Folder in your CWM backups folder on sd
5. Reboot into CWM Recovery
6. Wipe Data Factory Reset
7. Wipe Dalvik Cache in Advanced Menu
8. Go to Backup and Restore
9. Restore from Sd Card
10. Choose the Folder that you put all the file in
11. Restore
12. Reboot once restore is completed
***If CWM has trouble reading the folder with all the files
1. Download files from post 2
2. Add the 2 android.secure files to the folder with the other 11
3. Reboot into CWM
4. Restore with Above Instructions
***If you get an md5 checksum error do this:
1. Reboot
2. Go To My Files
3. Go To Downloaded Folder and Open It
4. Delete nandroid.md5 file from Downloaded Restore Folder
5. Make a New Folder Inside the Restore Folder
6. Rename New Folder EXACTLY WITH ALL LOWER CASE: nandroid.md5
7. Leave the nandroid.md5 folder EMPTY
***Should have Boot.img, data.ext4.tar, system.ext4.tar ect AND nandroid.md5 Folder all together INSIDE SAME FOLDER
8. Reboot To CWM and follow instructions above
***If you run into any issues doing a regular restore follow below
****Re wipe Data and Dalvik
13. Choose Advanced Restore from Sd Card
14. Choose Restore Boot
15. Click Yes and let Boot Restore
16. Go back to Advance Restore
17. Choose Restore Recovery
18. Click Yes and Restore Recovery
19. Go Back to Advanced Restore
20. Choose Restore System
21. Confirm Yes to Begin System Restore
22. Reboot System
Once the process completes you will be back on Stock Rooted Mj2. This process has been verified several times to work on Ml2 but should also work on any of the newer updates with Knox and new Bootloader with the Knox Kernel Fuse.
Google Drive Link Updated With all Files included:
https://drive.google.com/folderview?id=0B3T9bHro9RUveFlQa2JxQ3RaLWc&usp=sharing
I am not responsible over what you do to your device...If you choose to download and restore these system files it is your choice and yours alone...I have no responsibility if you brick your mega or it blows the roof off your house.
Enjoy being back on a normal stock rooted system without all the bootloader, root issues, and selinux garbage.
You are free to flash rom and mods once again without fear of bricking your Mega.
Mega

Download these 2 files if you have trouble reading the restore folder from ext sd containing all 11 downloaded restore file
Add these 2 into the folder with the rest of the downloaded files, and possibly the empty nandroid.md5 folder making it 13 total in the folder
Then try the restore again
https://drive.google.com/file/d/0B3T9bHro9RUveXl1dFhZMmpsX00/edit?usp=sharing
https://drive.google.com/file/d/0B3T9bHro9RUvS0xuNEZlcG9rTTA/edit?usp=sharing
Mega

Looks interesting.
But what we will have at the end? Full rooted stock ROM MJ2 with MJ2 bootloader and without KNOX? And what about counter?

cheyenne said:
Looks interesting.
But what we will have at the end? Full rooted stock ROM MJ2 with MJ2 bootloader and without KNOX? And what about counter?
Click to expand...
Click to collapse
What you have at the end is Mj2 fully rooted, no selinux, no knox bootloader...gives you back the ability to flash roms and kernels which on the kernel for ml1 and up, you cannot do without getting a semi-hard brick due to knox bootloader kernel fuse. Plus, Ml1 and Ml4 are identical to Mj2, no new features, speed improvements, or ram management have been added, it was simply to add in the knox selinux and kernel fuse which is the worst part. I just finished my mh2 rom and v2 update for it, and was looking thru the code for the ml1 and ml4 to possibly make a rom, and make sure the custom kernel i'm building was compatible and realized these weren't updates or improvements, just junk forced on us by samsung that severly cripple our ability to customize our mega. I'm working on the selinux and knox apps are easily removed from in the rom itself, but there is no way around the 1024 bit kernel fuse. As for the warranty counter, it somehow made a partition untouchable even thru a decompile of the rom and kernel, at least at this point I've yet to even find this partition, and stays permenantly once tripped, even after removing the entire kernel and bootloader from the device. Its been 4 months and the note 3 still has no way around this either, so I merely put this out for those who want to get back to an open system to flash as they wish without the worry of bricking their mega and arent in depth at coding enough to pull themselves out. At least now theres an alternative that you can downgrade safely and relatively easily with. Take it easy,
Mega

Google drive files
From what you said I expected to find one packed file. Instead on your GD there are several files. It is not clear for me what to do - download them one by one and put in new folder (named i.e "Mj2&rootNObootloader") in /clockworkmod/backup on SD card? Be more specific in this point. Why don't you post whole folder to avoid misunderstanding?
And one more question - what REALLY is the kernel in system after flashing update with KNOX and then proceeding your fix?

trurl3 said:
From what you said I expected to find one packed file. Instead on your GD there are several files. It is not clear for me what to do - download them one by one and put in new folder (named i.e "Mj2&rootNObootloader") in /clockworkmod/backup on SD card? Be more specific in this point. Why don't you post whole folder to avoid misunderstanding?
And one more question - what REALLY is the kernel in system after flashing update with KNOX and then proceeding your
Unfortunately you cannot download the entire folder at once like how I uploaded it so...
Download every file that's in the link...There's 11 total
Place them all in 1 folder together...All are tiny files except 2 system files
Put this folder called whatever sure mj2 restore in CWM backups folder
Restore in cwm
Follow the directions exactly as depicted in op
I don't know what you're REALLY asking lol? Are you trying to ask...what kernel is in the system after you update to ml1? Or after my restore? If ml1 you have a new kernel with Knox fuse and warranty counter..The 2 lines of 00 01 ect
After my restore you have mj2 kernel...sorry from your wording I'm just trying to guess and fill in what I think you mean
Mega
Click to expand...
Click to collapse

megalomanic14 said:
trurl3 said:
-cut-
I don't know what you're REALLY asking lol? Are you trying to ask...what kernel is in the system after you update to ml1? Or after my restore? If ml1 you have a new kernel with Knox fuse and warranty counter..The 2 lines of 00 01 ect
After my restore you have mj2 kernel...sorry from your wording I'm just trying to guess and fill in what I think you mean
Mega
Click to expand...
Click to collapse
Thank you. Now I understand what you mean about kernel. The problem with Counter is made because of efuse in new ROM and counter is ticked during rooting attempt and getting CWM to system. After that you can remove ALL, but efuse is broken and counter is set... that I understand it... am I right in general?
Click to expand...
Click to collapse

trurl3 said:
megalomanic14 said:
Thank you. Now I understand what you mean about kernel. The problem with Counter is made because of efuse in new ROM and counter is ticked during rooting attempt to get CWM< to system. After that you can remowe ALL, but efuse is broken and counter is set... that I undesrtand it... am I right in general?
Click to expand...
Click to collapse
Kinda...The efuse is what blocks us from flashing a kernel over top of the ml1 kernel and will literally brick your device...I did it just to test it...it wouldn't boot past this kernel lockout code...The warranty counter is different...it writes a one time write code somewhere in your system...In a partition hidden away that I cannot even find in my decompile, that basically goes from 00 to 01. I believe it's hidden as a partition in a boot cache or something as I removed everything entirely...had no system to even boot and it showed up 01 warranty.
While reverting back to mj2 with these files will remove the kernel fuse and new bootloader from ml1...that warranty flash 01 stays hidden somehow in a cache partition that can never be undone. Not really a big deal, it has zero effect just simply voids your warranty. The kernel fuse was the nasty beast that could do some serious damage.
Mega
Click to expand...
Click to collapse

After reverting back to your ROM, what'll be system status and what'll be showed in download mode?

cheyenne said:
After reverting back to your ROM, what'll be system status and what'll be showed in download mode?
Click to expand...
Click to collapse
It goes back to rooted stock mj2, custom status since rooted and keep cwm on there...then here's download mode...01 because once that's flashed there's no way to ever get back to 00...just to be clear this isn't my MegaFire rom...it's completely stock mj2 rooted...I should note also this is after I used these exact files to restore back after intentionally tripping the kernel fuse to 01 bricking my mega just to test my files and method before posting.
Mega

cheyenne said:
After reverting back to your ROM, what'll be system status and what'll be showed in download mode?
Click to expand...
Click to collapse
I literally did this 5 times yesterday just double checking it before I posted the method lol. I have sent about 20 people these in PM over these last few weeks and have restored them back to mj2 and several are now running my custom rom. If done right you'll be back to 100% stock rooted mj2 with custom status like always and 01 warranty.
Mega

megalomanic14 said:
...no knox bootloader...
Mega
Click to expand...
Click to collapse
Sorry but this is a backup Rom made by Custom Recovery on "backup and restore". I have it also.
One backup not have modem nor bootloader backup's, then the Knox Bootloader continue there on aboot.mbn. And the modem continue ML1.
Can You make a Mod Modem MJ2 to People flash after Restore this backup please?
Thank You

ValenteL said:
Sorry but this is a backup Rom made by Custom Recovery on "backup and restore". I have it also.
One backup not have modem nor bootloader backup's, then the Knox Bootloader continue there on aboot.mbn. And the modem continue ML1.
Can You make a Mod Modem MJ2 to People flash after Restore this backup please?
Thank You
Click to expand...
Click to collapse
Sorry I'm confused...yes it's a backup stock rooted mj2 to be restored in cwm. ..it replaces the ml1 kernel and rom allowing for flashing custom kernels and roms...yes its made for those who don't have an mj2 backup or who want an mj2 stock pre rooted...A backup restore is the only way back to mj2 as odin gives kernel fuse brick...no it does not get rid of new boot but since it restores old kernel the kernel fuse does not function so it doesn't matter...and sure I could throw a mj2 modem together but I kept ml1 modem since it was better... Hope that covers what you're asking? Take it easy
Mega

megalomanic14 said:
Hope that covers what you're asking? Take it easy
Mega
Click to expand...
Click to collapse
Thank You
I don't ask anything. I made a try from downgrade by Odin, but its all, a try.
I have also a MJ2 backup for security only. I prefer made upgrades. I'm now whit NA2, new Knox bootloader flashed.
Good luck on Your work.

ValenteL said:
Thank You
I don't ask anything. I made a try from downgrade by Odin, but its all, a try.
I have also a MJ2 backup for security only. I prefer made upgrades. I'm now whit NA2, new Knox bootloader flashed.
Good luck on Your work.
Click to expand...
Click to collapse
I got you...The new rom updates didn't bring any improvements only added the boot and Knox, warranty flash, kernel fuse, and selinux so its not really an update as the rest of the build are idnetical to mj2 with no improvements or new festures...but if you run stock it doesn't really make any difference I guess. But for anyone wanting to flash custom roms or kernels you can't on the new updates. But yea you can easily restore mj2 if you have a backup...I've had like 20 or 25 people ask me for the files before is why I did the post. Thanks Take it easy
Mega

If anyone has any issues or questions please read thru the op and other posts... especially between Valente and myself as I want be around tonight till middle of the night... got a gig to do... will get back to you later if needed.
Mega

megalomanic14 said:
If anyone has any issues or questions please read thru the op and other posts... especially between Valente and myself as I want be around tonight till middle of the night... got a gig to do... will get back to you later if needed.
Mega
Click to expand...
Click to collapse
Thank you. I still have the red alers at the boot but works root and wifi. For me in ML1 with root no wifi.

megalomanic14 said:
Sorry I'm confused...yes it's a backup stock rooted mj2 to be restored in cwm. ..it replaces the ml1 kernel and rom allowing for flashing custom kernels and roms...yes its made for those who don't have an mj2 backup or who want an mj2 stock pre rooted...A backup restore is the only way back to mj2 as odin gives kernel fuse brick...no it does not get rid of new boot but since it restores old kernel the kernel fuse does not function so it doesn't matter...and sure I could throw a mj2 modem together but I kept ml1 modem since it was better... Hope that covers what you're asking? Take it easy
Mega
Click to expand...
Click to collapse
There are some suspicions so Warranty Counter is placed in EMMC partition. Is it possible to check it?

trurl3 said:
There are some suspicions so Warranty Counter is placed in EMMC partition. Is it possible to check it?
Click to expand...
Click to collapse
Yea I'll double check that....I had a similar thought, but cannot even find a trace or any code that would link instructions to the warranty flash. It's like ghost code...but I just starting building a new rom last night based on ml1 so I'll be going over it again and again....As I won't upload it until I'm positive I broke the efuse which is the bad boy in this kernel,I already disabled selinux and Knox, but that kernel fuse and warranty counter are so well hidden it's insane...plus I'm putting together my own root kit for ml1 since vcore break wifi and most other methods are only partial root that you lose on reboot or granting root access...will let you know as things progress what I find. Take it easy
Mega

I do not know what's going on, but after downloading all 11 files in one folder, I see them only 8 Then after download 2 files from the second post, I have a total of 9 files But again as I want to download files, which do not see, it shows me that already have them. And now I do not know what to do.

Related

[Q] Is this even possible?? (custom rom build, stock recovery and unrooting)

Hi guys,
I've been asked to look into the possibility of flashing some Android tablets so that they have some extra apps included.
We all know that you can build a rom from a stock one, add the apk files to /data/apps or /system/apps, sign, package it up and then flash. However I'm looking for a more complete solution.
I need to get these tablets to a point where once I'm done, when you turn in on you get the out of the box experience, all counters have been reset, device in NOT rooted, the recovery partition restored so that the device will pass a warranty inspection.
in my mind the to do list looks something like this;
root device
flash recovery
backup device (just in case...)
dump rom (as i might have a new model that a stock rom download doesn't exist for yet!)
edit rom to include the 2 extra apps i need to install
flash the new rom
revert recovery to stock
reset all counters
un-root device
anyone know of any reason why this wont work?
I'll be honest I have been playing for a day and I can root, flash recovery, (can't dump yet so used stock rom from dl), add apps to /data/apps but I keep failing on the flash.
I also know i can revert the recovery and unroot.
Anyone got any tips? or any nugget of information that proofs I can't do this so I'm wasting my time?
thanks in advance guys.

[Q] Updating firmware when already using link2sd and foldermount?

Hi, i'm on 4.1.2 and rooted using link2sd and foldermount so I can store apps on the external sd card. If I upgrade to 4.2.2 do I need to unroot first and then root again after flashing the new firmware?
Also i'm assuming i'm going to lose all my game saves etc as I will lose my link2sd and foldermount setups?
My phone is unlocked from the 3 network but still has the 3 network logo on boot up and so I thought if i'm going to have to start afresh I might as well get the stock unbranded S3 rom and get rid of the 3 network branding. I used Galaxsim unlock to unlock the network so i'm assuming I won't lose my network unlock by doing any of the above?
Thanks in advance for any help given.
Sp0oner said:
Hi, i'm on 4.1.2 and rooted using link2sd and foldermount so I can store apps on the external sd card. If I upgrade to 4.2.2 do I need to unroot first and then root again after flashing the new firmware?
Also i'm assuming i'm going to lose all my game saves etc as I will lose my link2sd and foldermount setups?
My phone is unlocked from the 3 network but still has the 3 network logo on boot up and so I thought if i'm going to have to start afresh I might as well get the stock unbranded S3 rom and get rid of the 3 network branding. I used Galaxsim unlock to unlock the network so i'm assuming I won't lose my network unlock by doing any of the above?
Thanks in advance for any help given.
Click to expand...
Click to collapse
Just flash any rooted 4.2.2 ROM via custom recovery. You should take a titanium backup and a nandroid backup first. If it flashes without a wipe, you've lost nothing. If you do have to wipe, you can restore using Titanium. The Nandroid is a full system restore incase nothing works.
rootSU said:
Just flash any rooted 4.2.2 ROM via custom recovery. You should take a titanium backup and a nandroid backup first. If it flashes without a wipe, you've lost nothing. If you do have to wipe, you can restore using Titanium. The Nandroid is a full system restore incase nothing works.
Click to expand...
Click to collapse
Thanks. As you can tell i'm not up to speed on android rooting as i'm an ex iphone devotee that was good with jailbreaking but i'm new to android rooting really.
If I take an already rooted rom that surely still overwrites my current data as a rom replaces what is already there doesn't it? Can titanium and nandroid backup to pc via usb cable as my 32gb sd card won't have enough room to backup onto as it's heavily used for foldermount and link2sd.
If I wanted a pre rooted 4.2.2 stock rom for the I9300 is that something I can find on this forum to safely download and try? And if for any reasom i'm not happy with it the nandroid backup will restore the phone back to my original rom and setup as if I hadn't changed roms?
Rom and data are different. Please read the link in my signature "read before reading". It should contain everything you need to know (i'm not just saying this because I wrote it, but its really essential).
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
Rom and data are different. Please read the link in my signature "read before reading". It should contain everything you need to know (i'm not just saying this because I wrote it, but its really essential).
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you, again. I have read all that this morning and I am in no rush to change anything as one thing i've learnt from jailbreaking when I first got into it was rushing = ending up in a big mess and panicking you've bricked your device.
I rooted my S3 earlier this year and so I expect I still have all the files and the url of the guide I followed so I can check exactly what it was I did. My flash counter won't reset to zero which really bugged me and again another lesson learnt from doing something without fully checking the consequences.
I'm an IT engineer but all windows based so when it comes to android/linux what I think would be logical pretty much seems to go out the window!
Its always good to hold off and understand before moving forward. Read the thread through a few times.
I'm also a wintel IT engineer but I wanted to get into android development so I've been using Linux at home as my daily driver for 2 years.
If there's ever anything in that thread you want me to put into windows analogies or similes,,just ask in that thread. It will help me expand the thread also
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
Its always good to hold off and understand before moving forward. Read the thread through a few times.
I'm also a wintel IT engineer but I wanted to get into android development so I've been using Linux at home as my daily driver for 2 years.
If there's ever anything in that thread you want me to put into windows analogies or similes,,just ask in that thread. It will help me expand the thread also
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks again. I've been having a play about today and firstly got a titanium backup done for everything and then copied to my laptop. Then got the online version of nandroid backup so no reboot required to take the backup and did a full one of those and copied to my laptop too.
I've checked what root process I followed and it was one posted on the s3 forums using GalaxyS3root which uses a file via odin called CF-Root-SGS3-v6.1.tar. I won't post the link in case it breaks any rules etc. After reading your other post as advised I get the impression i'm not going to be able to reset my flash counter to zero. I have tried triangle away but it doesn't succeed.
As Android 4.3 is out/due out i'm now thinking pointless moving to 4.2.2 and I should wait and got straight to 4.3. Now what I wanted to ask was the following...
If I took titanium backup and then undid all my link2sd and foldermount links and then unrooted would I be able to flash the stock 4.3 rom when available, root it then reset up link2sd and foldermount and restore the titanium backup and have all my apps back to how they were?
I want to get an unmodified samsung rom that is unbranded so I can get rid of my 3 network branding I currently have on boot up. I also want to know if it is possible in anyway to reset the flash counter so I could in theory if unrooted get ota updates.
First question...
If you wipe and manually set up link2sd - when you then restore via titanium everything should be as it was.
You can reset the counter before unrooting. Theres a return-to-stock guide stuck in the "sticky roll-up thread" that covers it. The counter goes up to 1 on boot so the trick is to prevent the boot...
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
First question...
If you wipe and manually set up link2sd - when you then restore via titanium everything should be as it was.
You can reset the counter before unrooting. Theres a return-to-stock guide stuck in the "sticky roll-up thread" that covers it. The counter goes up to 1 on boot so the trick is to prevent the boot...
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks, so the counter can't be cleared permanently for warranty purposes as a reboot will just put it back to 1. So as I have a custom recovery on the phone that went on with the root will that cause issues if I tried to update via official updates?
It can be prevented with an ics bootloader.
Imho its best to stay away from official updates when rooted
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
It can be prevented with an ics bootloader.
Imho its best to stay away from official updates when rooted
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks. An ics bootloader however will just further invalidate the warranty and also prevent stock updates? What I had been getting at with wanting to do stock updates was to unroot first. However now i've got the custom recovery there that in itself makes stock updates an unwise move even with rooting removed?
So with my current setup what is the best method to go to 4.2.2 without using a custom rom?
They check warranty by looking at the information provided in the bootloader. Your warranty is either void or not void. There is no such thing as further invalidation. Its 0 or 1. There is no 2.
There is no "best way" without using a "custom rom". If you want to flash a stock rom, do it. Theres only one way.
By the way, 4.2.2 hasn't been officially released, so you wont be getting stock updates. You'll have to manually keep flashing release via odin until you get one that is official. Then if your csc is wrong, you have to change it (which requires factory reset) and then you will still only get updates over USB if you're rooted.
Don't get me wrong, but that sounds ridiculous to me. I just don't understand any rooted user wanting to do that
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
They check warranty by looking at the information provided in the bootloader. Your warranty is either void or not void. There is no such thing as further invalidation. Its 0 or 1. There is no 2.
There is no "best way" without using a "custom rom". If you want to flash a stock rom, do it. Theres only one way.
Sent from my GT-I9300 using Tapatalk 4 Beta
---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------
By the way, 4.2.2 hasn't been officially released
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the quick reply. I've just read through the link on your thread for returning to stock and unless i've misread it you can actually return to stock even if you have installed a custom recovery/used the auto cf root method of rooting? That's step 16?
Sorry on the invalidating warranty thing, what I meant was that if you use the ics bootloader you fix the triangleaway issue but you are then left with the ics bootloader so your warranty is still invalid.
My mistake on 4.2.2, what's the latest official version as if I plug into kies it tells me there is an update available which i'd wrongly assumed was 4.2.2?
4.1.2 is the latest.
They don't check bootloader version for warranty. They only check download mode.
You can return to stock so long as phone fully boots and usb works. If phone only partially boots, you can't return to stock or reset counter. This is why IMHO its better to have an ics bootloader where counter is always in the reset state
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
You can return to stock so long as phone fully boots and usb works. If phone only partially boots, you can't return to stock or reset counter. This is why IMHO its better to have an ics bootloader where counter is always in the reset state
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK this has totally lost me now, I need to do some more reading! Also i'm on 4.1.2 yet if I plug into Kies ittells me there is an update available.
Sp0oner said:
OK this has totally lost me now, I need to do some more reading! Also i'm on 4.1.2 yet if I plug into Kies ittells me there is an update available.
Click to expand...
Click to collapse
An update won't necessarily update the android version. It will update the Samsung build version. Samsung have probably close to 100 updates on 4.1.2 (globally).
Android is just the base OS. It has Samsung GUI on top of that (and frameworks to support Samsung proprietary features). So Samsung take the android code for 4.1.2 and add all their stuff to it. But they will improve on that over a number of builds. Fixing bugs, addressing performance issues etc.
However, Samsung tend to release new features in line with android base updates too. so if Samsung are working on 4.1.2 and decide, "hey this feature would be cool", they would usually wait for the next android version to release it.
Hope that makes sense
Did that address your confusion?
Or is your confusion about returning to stock?
You return to stock by flashing a full ROM (which includes a bootloader, Android ROM, Recovery, baseband etc) over USB connection to a computer. The phone is put into download mode and flashed. if your USB is faulty, this wont work (obviously).
Before returning to stock, you need to ensure your download mode doesnt show how many times you flashed custom things. You can reset it then flash stock and warranty is fine. However, to reset it, android needs to boot, so if android doesnt boot and counter says more than "0", you've lost warranty, With ICS bootloader, you reset it once and it always says "0", so you are protected if phone doesnt boot.
rootSU said:
An update won't necessarily update the android version. It will update the Samsung build version. Samsung have probably close to 100 updates on 4.1.2 (globally).
Android is just the base OS. It has Samsung GUI on top of that (and frameworks to support Samsung proprietary features). So Samsung take the android code for 4.1.2 and add all their stuff to it. But they will improve on that over a number of builds. Fixing bugs, addressing performance issues etc.
However, Samsung tend to release new features in line with android base updates too. so if Samsung are working on 4.1.2 and decide, "hey this feature would be cool", they would usually wait for the next android version to release it.
Hope that makes sense
Did that address your confusion?
Or is your confusion about returning to stock?
You return to stock by flashing a full ROM (which includes a bootloader, Android ROM, Recovery, baseband etc) over USB connection to a computer. The phone is put into download mode and flashed. if your USB is faulty, this wont work (obviously).
Before returning to stock, you need to ensure your download mode doesnt show how many times you flashed custom things. You can reset it then flash stock and warranty is fine. However, to reset it, android needs to boot, so if android doesnt boot and counter says more than "0", you've lost warranty, With ICS bootloader, you reset it once and it always says "0", so you are protected if phone doesnt boot.
Click to expand...
Click to collapse
Thanks for both explanations :good: It was the ics bootloader I was really confused about. I'm in two minds as to change anything, the techy part of me says play with it and learn and understand more about what you've explained but the other side says i've got everything setup perfectly at the moment now I have link2sd and foldermount working and not to risk ruining that setup. I think the only thing i'd notice from 4.2.2 is the access camera from the lock screen feature.
Sp0oner said:
Thanks for both explanations :good: It was the ics bootloader I was really confused about. I'm in two minds as to change anything, the techy part of me says play with it and learn and understand more about what you've explained but the other side says i've got everything setup perfectly at the moment now I have link2sd and foldermount working and not to risk ruining that setup. I think the only thing i'd notice from 4.2.2 is the access camera from the lock screen feature.
Click to expand...
Click to collapse
If you want to continue to use stock.....
1) Backup all your app data with titanium backup (as a precaution)
2) Copy all internal /sdcard data to PC
3) Flash whatever "official" ROM you want via Odin
4) If it doesn't boot, perform factory reset#
5) re root using either cf auto root or framaroot (both do not give custom recovery)
6) Install Titanium backup and restore data.
Its worth noting a factory reset from custom recovery only wipes data and settings. A reset from stock recovery wipes internal /sdcard storage too.
rootSU said:
If you want to continue to use stock.....
1) Backup all your app data with titanium backup (as a precaution)
2) Copy all internal /sdcard data to PC
3) Flash whatever "official" ROM you want via Odin
4) If it doesn't boot, perform factory reset#
5) re root using either cf auto root or framaroot (both do not give custom recovery)
6) Install Titanium backup and restore data.
Its worth noting a factory reset from custom recovery only wipes data and settings. A reset from stock recovery wipes internal /sdcard storage too.
Click to expand...
Click to collapse
Thanks again :good: I have CWM installed and when I open CWM Manager I get a message "this version of CWM Manager should be used with CF-CWM v1.1 or newer. It appears you are running a different recovery. Various features have been disabled."
If I boot into recovery at the top it says "CWM-based recovery v5.5.04 :: CF-v1.3"
What effect does any of that have on the above steps?
Sp0oner said:
Thanks again :good: I have CWM installed and when I open CWM Manager I get a message "this version of CWM Manager should be used with CF-CWM v1.1 or newer. It appears you are running a different recovery. Various features have been disabled."
If I boot into recovery at the top it says "CWM-based recovery v5.5.04 :: CF-v1.3"
What effect does any of that have on the above steps?
Click to expand...
Click to collapse
CWM manager is an app to manage CWM. Its pretty pointless. I dont think it works on JB ROMs though.
CWM 5 is old and should be replaced by users who want to continue using a custom recovery.
The flashing stock from Odin process will overwrite any bootloader, recovery, ROM and Baseband. Nothing you have can prevent that.

safestrap problem

hallo guy
(first, my english is bad because i am from germany)
i have installed safestrap and the rom slot 1. i installed/flashed at the rom slot 1 thor gapps rom. after starting the system it came in a bootloop. so safestraped asked me to stop and format it. i thought it means only the rom slot 1. after that on safestrap is the stock rom empty and the other slots too. when i try to make a new rom slot it say there is no space. at the stock rom is only 1230mb space at the system partition. but there is no os. when i try to conect it on my laptop. the laptop dont recognize the kindle. so what can i do ?
kasem71 said:
hallo guy
(first, my english is bad because i am from germany)
i have installed safestrap and the rom slot 1. i installed/flashed at the rom slot 1 thor gapps rom. after starting the system it came in a bootloop. so safestraped asked me to stop and format it. i thought it means only the rom slot 1. after that on safestrap is the stock rom empty and the other slots too. when i try to make a new rom slot it say there is no space. at the stock rom is only 1230mb space at the system partition. but there is no os. when i try to conect it on my laptop. the laptop dont recognize the kindle. so what can i do ?
Click to expand...
Click to collapse
If I remember correctly you have to do these steps after installing the safe trap.
1. create back up from stock rom
2. Create romslot 1
3. restore the back up on romslot 1
4. install the thor gapps rom on rom slot 1.
thor gapps need the stock rom first. that why you create back up and restore it somewhere else. thor gapps is NOT a AOSP room, it removes and modifies the stock rom.
I don't think you can format your stock rom but if you did, you have to wait for a AOSP rom.
Arashkage said:
If I remember correctly you have to do these steps after installing the safe trap.
1. create back up from stock rom
2. Create romslot 1
3. restore the back up on romslot 1
4. install the thor gapps rom on rom slot 1.
thor gapps need the stock rom first. that why you create back up and restore it somewhere else. thor gapps is NOT a AOSP room, it removes and modifies the stock rom.
I don't think you can format your stock rom but if you did, you have to wait for a AOSP rom.
Click to expand...
Click to collapse
the problem is that i cant put anything on my kindle. the laptop dont recognize the tablet. so if a rom come out i cant put it on my kindle. the stock rom is there but its empty !
if
kasem71 said:
the problem is that i cant put anything on my kindle. the laptop dont recognize the tablet. so if a rom come out i cant put it on my kindle. the stock rom is there but its empty !
Click to expand...
Click to collapse
If you could if you can get somebody to send you a backup of some type you can ADB push it to your Sd card in backup directory and restore it . What is your base firmware originally? If you can score a flashable copy of your base that would work also. Four instance the base Hasscode has over in the safestrap thread. (Old firmware) But to get ADB you need to uninstall the Microsoft USB drivers for your device and install the ADB drivers from the utility .94
jimyv said:
If you could if you can get somebody to send you a backup of some type you can ADB push it to your Sd card in backup directory and restore it . What is your base firmware originally? If you can score a flashable copy of your base that would work also. Four instance the base Hasscode has over in the safestrap thread. (Old firmware) But to get ADB you need to uninstall the Microsoft USB drivers for your device and install the ADB drivers from the utility .94
Click to expand...
Click to collapse
thanks for you help. the firmware was the newest. 13.3.2.4. and can you give a step by step tutorial for the ADB ? i wont make it wrong, again
sorry
kasem71 said:
thanks for you help. the firmware was the newest. 13.3.2.4. and can you give a step by step tutorial for the ADB ? i wont make it wrong, again
Click to expand...
Click to collapse
You dont already have the toolkit from development?it has adb drivers try that first .does your device show at all? Maybe with like an explanation point on it and the yellow triangle? If it does open that device in your device manager in and uninstall the drivers. Then run the driver install part of the utility toolkit .94. I'm sorry but no I cannot give you step-by-step or I will not considering it is in these forums at least a dozon times but I'll give you a link to a thread that explains it over and over again but you must be able to comprehend what you are reading and follow directions explicitly it does work it has worked for people but sometimes it takes several attempts . http://forum.xda-developers.com/showthread.php?t=2588608 remember but not just the first post has good information this is discussed all the way through these threads . And often pertain to different subjects . And if you don't think that you find what you need in this thread there are several several other threads in the general section and the troubleshooting section titled brick! Or please help! Or yada yada yada etc. and most will have to do with trying to get ADB back on a device.. For whatever reason. What ever you do do not go to factory recovery attempt a factory reset it will totally screw you. As long as you still have safestrap booting you have hope now you need to do what you did not do to begin with,and educate yourself thoroughly before moving forward with anything . All it will take is one more mistake on your part of the inability to completely read everything and understand everything and you will be calling Amazon for a replacement.. good luck why can't you restore a backup?
hallo
my english is bad, so its diffcult to understand everything. because this i ask for a step by step tutorial. this was my fault.
and is there a difference between the 13.3.2.4.X.X.X versions ? can i take any 13.3.2.4 back up ?
kasem71 said:
hallo
my english is bad, so its diffcult to understand everything. because this i ask for a step by step tutorial. this was my fault.
and is there a difference between the 13.3.2.4.X.X.X versions ? can i take any 13.3.2.4 back up ?
Click to expand...
Click to collapse
Yes. As long as long is it is of a stock system of the same firmware you are on. I am aware of how to do it how to give you a clean backup that would allow you to set it up but I am not on that firmware on any of my three HDX devices And then another idea you may go over to the safestrap thread and inquire about a ABD sideload procedure I did see that option and safestrap recovery but I do not know how it works. Oh and another idea I also know works because I advised it to another person and he did it it worked well for him in a similar situation. Download the original bin file for your firmware to your PC rename the .bin to .zip and download the newest flashable superSU ADB push to SD card then flash to stock slot. Firmware then supersu reboot, reinstall safestrap and redo OTA blocker. It also sounds like you really need to read through the safestrap thread and understand it more thoroughly I do not believe this would've happened if you had more of an understanding on how safestrap is to be used.
jimyv said:
Yes. As long as long is it is of a stock system of the same firmware you are on. I am aware of how to do it how to give you a clean backup that would allow you to set it up but I am not on that firmware on any of my three HDX devices And then another idea you may go over to the safestrap thread and inquire about a ABD sideload procedure I did see that option and safestrap recovery but I do not know how it works. Oh and another idea I also know works because I advised it to another person and he did it it worked well for him in a similar situation. Download the original bin file for your firmware to your PC rename the .bin to .zip and download the newest flashable superSU ADB push to SD card then flash to stock slot. Firmware then supersu reboot, reinstall safestrap and redo OTA blocker. It also sounds like you really need to read through the safestrap thread and understand it more thoroughly I do not believe this would've happened if you had more of an understanding on how safestrap is to be used.
Click to expand...
Click to collapse
when i do this, can i install updates from amazon ?
i cant post anything on the development topic. when i do this, is the device like after a factory reset ?
No!
kasem71 said:
i cant post anything on the development topic. when i do this, is the device like after a factory reset ?
Click to expand...
Click to collapse
Didn't you read in a previous post a couple of post up do not factory reset at least until after you get a working OS and yes you can flash and Amazon bin file BUT safestrap does not flash kernel or bootloader so it will only flash the system partition and data partition and that is what you need. But you have to rename it from .bin to .zip and somehow get it on your device AND YES IT will overwrite any system modifications and root access that's why you must flash the super SU after you flash the firmware zip if you want root right away..that is
jimyv said:
Didn't you read in a previous post a couple of post up do not factory reset at least until after you get a working OS and yes you can flash and Amazon bin file that safestrap does not flash kernel or bootloader so it will only flash the system partition and data partition and that is what you need. But you have to rename it from .bin to .zip and somehow get it on your device
Click to expand...
Click to collapse
ok thanks
If you are still having trouble, go to the developer thread, and rather than posting, try reading and getting the HDX TOOLKIT .94 to work on your computer. That should get adb set up for you. Once that happens, the commands are easy.
$adb push [file location] /sdcard
It doesn't matter
lekofraggle said:
If you are still having trouble, go to the developer thread, and rather than posting, try reading and getting the HDX TOOLKIT .94 to work on your computer. That should get adb set up for you. Once that happens, the commands are easy.
$adb push [file location] /sdcard
Click to expand...
Click to collapse
He didn't listen he chose to do in ADB sideload through safestrap and completely screwed it up now. As far as I know he still has not recovered this device

[TW] Stock-UltraStock-Ultrapure-Deodexed/Debloated- T330NU-T330NUXAR1BOG1_XAR] 5.5.1

Finally a Deodexed and Debloated Stock Touchwiz ROM for our T330NU
You will have to flash root since I have not injected a preroot, I wanted to keep UltraStock and Ultrapure to be as close to stock as possible and could not be done without
the Kernel that made this all possible from @moonbutt74​
Instructions:
Download the ROM here:
Use Phil's Touch custom recovery found here: https://www.androidfilehost.com/?fid=95887005526787123
Flashable with both TWRP and Philz Touch
UltraStock-Deodexed: https://www.androidfilehost.com/?fid=24052804347803436
Ultrapure--For the Ultrapure experience almost completely Untouched: https://www.androidfilehost.com/?fid=24052804347812624
UltraStock-DeKnoxed-DebloatedV4, for those who want a debloated experience: https://www.androidfilehost.com/?fid=24052804347809297
Now reboot.. Allow 10 minutes to boot, it will seem like it will take FOREVER, but be patient it will work..
All Lollipop/ART ROMs take forever to boot, so just be patient
There are no bugs that I am aware of, however in the debloating process I incidentally removed the system fonts, you can readd them in the Display/Fonts Menu
Any issues please comment in the thread..
I will release 3 versions:
1) 100 percent stock Deodexed
2) Deodexed and Debloated
3) Deodexed, Debloated, and Desamsunged
This will be an ongoing project where mods and changes will be made over time as the they become available.
XDA:DevDB Information
[TW] Stock-UltraStock-Ultrapure-Deodexed/Debloated- T330NU-T330NUXAR1BOG1_XAR, ROM for the Samsung Galaxy Tab 4
Contributors
Zaphodspeaks, Zaphodspeaks, Moonbutt74
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: Have your device running the Stock T330NUXAR1BOG1_XAR 5.1.1 [TW]
Version Information
Status: Stable
Created 2015-08-27
Last Updated 2015-11-14
Ultrastock/Ultralite UPDATE 9-6-2015​
T330NU-LP_DeKnoxed-DebloatedV4, Released! See OP
"T330NU-LP_UltraliteV5d Removed due to complaints of boot loops
Please give up to 7 mins, "I tested this myself, it takes anywhere between 4-7 mins tops, if it takes longer, your doing something wrong..
I have been sitting at this screen with my Galaxy Tab on a stand, testing builds over and over and over again.. Nothing I put up goes untested..
I will work on the extras, and maybe a popular app or 2
If you wish to COMPLETELY remove all Samsung content, try this script from: http://forum.xda-developers.com/showthread.php?t=2507931 I attached the script needed from that page.. All Credit for the script goes to @Kaito95
UPDATE!!!
For those who use TWRP, since I don't use it, I did make an install method that can be used in Recovery..
I created a dump/back up of my device in TWRP with out the Data partition.. Flash it in TWRP and it should give you what your looking for
Since its a dump, its already rooted and ready to go.. Just be sure to clear Dalvik and Cache.. before rebooting
https://www.androidfilehost.com/?fid=24052804347805056
Just be sure your already on Lollipop before attempting, or you will end up in a bootloop
Its in zip format, do not flash the zip.. Unzip it, and just copy it to your SD card..
Install and enjoy..
Zaphodspeaks said:
Mine!
Click to expand...
Click to collapse
Is this deknoxed?
zach61797 said:
Is this deknoxed?
Click to expand...
Click to collapse
Read the title..
Yes it is..
Before you comment, please take the time to read..
It may save you a few headaches..
In fact it's stated 3 times that its Deodexed and debloated
Zaphodspeaks said:
Read the title..
Yes it is..
Before you comment, please take the time to read..
It may save you a few headaches..
In fact it's stated 3 times that its Deodexed and debloated
Click to expand...
Click to collapse
It says deodexed and debloated doesnt say deknoxed thats why i wasnt sure if you did it yet. Thank you very much for the rom
zach61797 said:
It says deodexed and debloated doesnt say deknoxed thats why i wasnt sure if you did it yet. Thank you very much for the rom
Click to expand...
Click to collapse
Debloated meant deKnoxed..
I'll be updating the page soon..
zach61797 said:
It says deodexed and debloated doesnt say deknoxed thats why i wasnt sure if you did it yet. Thank you very much for the rom
Click to expand...
Click to collapse
You should of looked at the what was removed:
Removing KNOX...
Removing com.sec.knox.store
Removing container
Removing preloadedsso
Removing Bridge
Removing KLMSAgent
Removing KnoxAttestationAgent
Removing KnoxMigrationAgent
Removing KnoxSetupWizardClient
Removing KNOXStore
Removing RCPComponents
Removing SPDClient
Removing UniversalMDMClient
Zaphodspeaks said:
You should of looked at the what was removed:
Removing KNOX...
Removing com.sec.knox.store
Removing container
Removing preloadedsso
Removing Bridge
Removing KLMSAgent
Removing KnoxAttestationAgent
Removing KnoxMigrationAgent
Removing KnoxSetupWizardClient
Removing KNOXStore
Removing RCPComponents
Removing SPDClient
Removing UniversalMDMClient
Click to expand...
Click to collapse
Ok thanks
Are there any tuts out there for upgrading from rooted 4.4.2 to Lollipop (or something newer than what I have)? I got my SM-T330NU last year and rooted it right away using Towelroot. I'd like to update the Android version and keep root. I know how to update using the Samsung firmware and Odin but I won't want to lose root. My apologies if this should be asked or redirected to a different thread. I'm pretty decent with managning the ROMS on my GS3 and GS4 but can't find a ton of info on the T330NU and I don't want to brick it.
Cheers
hpsguy10 said:
Are there any tuts out there for upgrading from rooted 4.4.2 to Lollipop (or something newer than what I have)? I got my SM-T330NU last year and rooted it right away using Towelroot. I'd like to update the Android version and keep root. I know how to update using the Samsung firmware and Odin but I won't want to lose root. My apologies if this should be asked or redirected to a different thread. I'm pretty decent with managning the ROMS on my GS3 and GS4 but can't find a ton of info on the T330NU and I don't want to brick it.
Cheers
Click to expand...
Click to collapse
In about an hour I will post a tutorial on how to flash from 4.4.2 to 5.1.1, I am uploading a custom Stock 5.1.1 image with a custom recovery to help with your upgrade..
Go to google play and download Titanium backup https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup It's my go to tool for backing up apps and restoring them. I suggest paying for the Pro version because it permits batch Jobs, instead of one app at a time.. You can for go this, and when you flash the image to which I will provide a complete tutorial, when 5.1.1 first boots, and it hang for about 6-10 mins, every device does this. Once the welcome screen comes up it will give you the chance to restore your device..
I'm uploading the Install Image now.. When it's done I'll let you know.. An hour.. its super slow uploading..
Once you have it, Ill walk you through it..
Awesome, thanks! I already have Titanium Backup Pro with all of my apps backed up ( I don't have a ton of apps on this device). I'm hoping the upgrade in software will help improve the performance of this as it's incredibly slow and laggy compared to my wifes Tab Pro (a MUCH better device). I got this one for free though so I'll take what I can get.
To be honest, I havent noticed much other than a Smoother Interface... Created a Deodexed version so I could Install Xposed, but there are no Xposed installs that work for this device yet due to lack of interest.. The Image is still uploading, you should know how to use the Custom Recovery... Work from there.. I'll post a full tutorial when its done..
1) If you are rooted, first things first.. Download Titanium backup from the Google Play, use it to backup all your apps, DO NOT BACKUP system apps, if you restore system apps from 4.4.2 you will brick your device.. So backup User Apps only..
2) Then Download the Samsung Stock 5.1.1 https://www.androidfilehost.com/?fid=95887005526787215 Save to your Desktop.
3) Download ODIN, which I attached below..
4) While in ODIN, Check AP, then select the ROM Image: T330NUUEU1BOG1_T330NUXAR1BOG1_HOME.tar that you downloaded. (Remember where you downloaded it to "Desktop") flash the ROM Image... It will reboot. It will take 6-10 mins at first boot, this is normal. You will not need to install a Custom Recovery because I included "Phil's Touch" in the Stock Image.
5) Once your booted up and ready to go and set up, Android will give you the opportunity to download all your previously installed Apps, wait for it to finish, then use Titanium Backup to restore your setting inside those restored apps, OR.. Just cancel the automatic restore and use Titanium back up..
I'll try this in the morning and let you know how I make out. Thanks.
Zaphodspeaks said:
1) If you are rooted, first things first.. Download Titanium backup from the Google Play, use it to backup all your apps, DO NOT BACKUP system apps, if you restore system apps from 4.4.2 you will brick your device.. So backup User Apps only..
2) Then Download the Samsung Stock 5.1.1 Save to your Desktop.
3) Download ODIN, which I attached below..
4) While in ODIN, Check AP, then select the ROM Image: T330NUUEU1BOG1_T330NUXAR1BOG1_HOME_Custom_Recovery.tar that you downloaded. (Remember where you downloaded it to "Desktop") flash the ROM Image... It will reboot. It will take 6-10 mins at first boot, this is normal. You will not need to install a Custom Recovery because I included "Phil's Touch" in the Stock Image.
5) Once your booted up and ready to go and set up, Android will give you the opportunity to download all your previously installed Apps, wait for it to finish, then use Titanium Backup to restore your setting inside those restored apps, OR.. Just cancel the automatic restore and use Titanium back up..
Click to expand...
Click to collapse
No dice so far. I get into Odin mode, start the flash then it fails almost immediately when it starts the "aboot" part.
hpsguy10 said:
No dice so far. I get into Odin mode, start the flash then it fails almost immediately when it starts the "aboot" part.
Click to expand...
Click to collapse
Ok, I probably didn't compile that correctly..
Try the 100 percent stock, but you will have to flash a Custom recovery "Phils touch"
https://www.androidfilehost.com/?fid=95887005526787215
That will work 100 percent
Zaphodspeaks said:
Ok, I probably didn't compile that correctly..
Try the 100 percent stock, but you will have to flash a Custom recovery "Phils touch"
https://www.androidfilehost.com/?fid=95887005526787215
That will work 100 percent
Click to expand...
Click to collapse
Pardon the ignorance but how do I flash a custom recovery on to the device?
Also, will I lose root with this update?
hpsguy10 said:
Pardon the ignorance but how do I flash a custom recovery on to the device?
Also, will I lose root with this update?
Click to expand...
Click to collapse
No Prob
Download Phil's touch https://www.androidfilehost.com/?fid=95887005526787122
Install via ODIN the same as the ROM, check AP....
You can't flash them both at once, only one at a time just to let u know..
Zaphodspeaks said:
No Prob
Download Phil's touch https://www.androidfilehost.com/?fid=95887005526787122
Install via ODIN the same as the ROM, check AP....
You can't flash them both at once, only one at a time just to let u know..
Click to expand...
Click to collapse
I keep getting this
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> sm-t330nu-Philz-6_58_9-recovery-final.img.tar.md5 is invalid.
<OSM> End...

[ROM][TW5.0]mostly stock N900VVRUEOF1[debloated/deodexed/wifi fixed]

I didn't think this warranted a development thread at this point, Mods may disagree and move it. Since a few people, myself included, need some TouchWiz features and want something closer to a stock rom than Jasmine but debloated, deodexed with the Verizon wifi tether provisioning disabled, I threw this together. I'll try to answer any questions and fix any issues that pop up but I cant make any promises due to work and other projects. If I do move forward with anything I may try to port the stock Verizon Note 4/5, but that's getting ahead of myself.
Now the usual warning about your warranty being voided (as if any Note 3s are under warranty and you didn't void it rooting/flashing recovery) and me not being responsible for you bricking your device because I was stoned when I packaged this.
Download the rom here.
So far the only changes to the stock OF1 are:
Deodexed
Moderatly debloated
Wifi tether provisioning disabled
Start up sound disabled
Rooted*
Busybox added*
*SuperSu and Busybox packages are installed during rom installation.
A list of debloated files can be found here.
Coming soon
Some files were left because they are too integrated into TouchWiz. I don't want people confused by orphaned menu items or get FCs. Some stuff I left because people I know use them. If you want anything back you'll have to get it yourself for now, sorry. I'm open to suggestions on stuff to keep and stuff to remove, but I'll want a good description of their functions before I remove anything. I'm funny about not deleting stuff I don't know what it does.
For those looking for Xposed, I'm using the latest Snapdragon requestConcurrentGC version from here.
Flashing instructions are pretty simple. Boot to TWRP, make a backup, wipe system/data/dalvik/cache, flash the rom and reboot system.
All thanks go to the Yemen rooters and @beaups and @ryanbg for liberating our devices.
thanks i tried it out and its working great! however one of the apps i like is S-Note and you debloated it :/ along with galaxy store. which i cannot find a download source for either, and its needed to reinstall s-note. anyway its a crucial app for the S-pen launcher and s-pen features.
if you could share the apks or upload a full but deodexed superSu/busybox version of this Rom it'd be a real winner.
also im not sure if its just me but i noticed the task manager is a little strange and is missing the ram clear button. ill take a screen shot and upload later
doombuger said:
if you could share the apks or upload a full but deodexed superSu/busybox version of this Rom it'd be a real winner.
Click to expand...
Click to collapse
All of the stock apps are in the system.img files in the Stock Odin tar bundles (available from sammobile.com for instance)
The only trick to getting them out of there is that those (system.img) image files are "sparse" ext4 files. The Android development environment has a tool called "simg2img" which allows you to create an uncompressed image file, which can then be mounted as an ext4 filesytem (loopback mount), and you can browse through there and copy out anything you want.
All of this is more convenient to do in a Linux environment (get yourself VirtualBox and install Ubuntu), but there are workarounds using Windows too, and there are even tutorials here on XDA on how to do this both ways. (Use searches for "sparse image" or "simg2img")
An even easier way is to simply pull them out of TWRP backup files of your rooted-stock ROMs; those "system.ext4.win00x" are just tar files. Heck, you could probably even use 7-zip for that.
You do make backups, right?
Ask your devs to do things that are interesting for the dev and difficult for almost any anybody else to do; not the simple stuff like "go get me some freely available files".
as some people like the stock image, you should do a non-debloated version, like beans did for 4.4.2 NC2/4: http://forum.xda-developers.com/showthread.php?t=2787627 Its just a minor thing, and i can add those apps back in.
How would i enable the startup sound that you disabled?
I'm running the deodexed version of NC4 (with an NC2 bootloader) that i linked above, and finally want to upgrade. I'm assuming that safestrap (which is currently installed) isn't compatible, so do have a link for a version of TWRP that is compatible?
also, can i upgrade from NC4 (with an NC2 bootloader) directly? or is there a step in between that i should do first?
Morlok8k said:
as some people like the stock image, you should do a non-debloated version, like beans did for 4.4.2 NC2/4: http://forum.xda-developers.com/showthread.php?t=2787627 Its just a minor thing, and i can add those apps back in.
How would i enable the startup sound that you disabled?
I'm running the deodexed version of NC4 (with an NC2 bootloader) that i linked above, and finally want to upgrade. I'm assuming that safestrap (which is currently installed) isn't compatible, so do have a link for a version of TWRP that is compatible?
also, can i upgrade from NC4 (with an NC2 bootloader) directly? or is there a step in between that i should do first?
Click to expand...
Click to collapse
i updated to of1 then rooted and bootloader unlocked then used flashify to flash recovery (back up stock recovery if u like) then no more safe strap or worries. but to each their own.
Very cool, thank you!
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
njdan30 said:
i updated to of1 then rooted and bootloader unlocked then used flashify to flash recovery (back up stock recovery if u like) then no more safe strap or worries. but to each their own.
Click to expand...
Click to collapse
How did you bootloader unlock after rooted? Were you able to install custom recovery? If so, do you mind sharing how you did that as well?
Thank you!!
Neo3D said:
Very cool, thank you!
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
How did you bootloader unlock after rooted? Were you able to install custom recovery? If so, do you mind sharing how you did that as well?
Thank you!!
Click to expand...
Click to collapse
yes you need to root 1st in order to get bootloader unlocked then head to play store for flashify the take the 1st(newest recovery)and thats it.check the yemen root http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 for of1 use that then the retail to dev unlock and enjoy,for unlock i did the adb method but think theres a 1 click unlock now also http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Problems with data
I appreciate all of your hard work. I do have a question though. Every single 5.0 and newer rom I have tried I have problems getting my data to work reliably. I get 4G after reboot but as soon as I send/receive a SMS message it reverts to 3g until the next reboot. This was a clean install and I've also tried reinstalling sim, done factory reset, cleared all data, everything under the sun I can think of. Nobody else seems to have this problem. Any ideas? Other than that this is exactly what I'm looking for.
May I ask somebody create a .tar version to use with odin.
I has no custom recovery .
Tried peazip software to convert .zip to .tar but odin always hangs when i use file
Long time first boot. thoght i made a brick Thanks mate
Quick question. I have kit Kat 4.4.2 with safe strap on mine. How would I be able to upgrade to this?
nitroevo said:
Quick question. I have kit Kat 4.4.2 with safe strap on mine. How would I be able to upgrade to this?
Click to expand...
Click to collapse
I am also looking for advice. My Note 3 is in a similar position with NC2 and Baja ROM in the stock slot of safestrap.

Categories

Resources