Related
Can you let us know if your out there using tmobile UK atrix, please!
Swyped from 'mount' Olympus
Bump
Swyped from 'mount' Olympus
nitrox1 said:
Can you let us know if your out there using tmobile atrix, please!
Swyped from 'mount' Olympus
Click to expand...
Click to collapse
i just ordered a unlock code for my atrix from cellunlock.net. its been 2 days as of now. i have tmobile us, still tmobile though lol
stratax said:
i just ordered a unlock code for my atrix from cellunlock.net. its been 2 days as of now. i have tmobile us, still tmobile though lol
Click to expand...
Click to collapse
Thank you for your reply. But I'm really looking for the UK Tmobile, sbf, or understanding of it.
Ps check out our uk orange thread, for a much cheaper unlock, and within 10 min!
Swyped from 'mount' Olympus
Bump
Swyped from 'mount' Olympus
im using a t-mobile uk atrix, got it yesterday
karl0ss said:
im using a t-mobile uk atrix, got it yesterday
Click to expand...
Click to collapse
Have a look in the about phone part and post up if you can
system version
Baseband version
Build number
system version - Version.4.2.23.MB860.T-Mobile.en.GB
Baseband version - N_01.92.00R
Build number - OLYEM_U4_2.2.3
any idea how i can root it? side loading apps seems to work without any hacks, as I was able to install some apks I had laying around on my dropbox, and I have installed some using Android Commander...but I can't work out how to root it, does GingerBreak NEED a real sd card inserted to work?
karl0ss said:
system version - Version.4.2.23.MB860.T-Mobile.en.GB
Baseband version - N_01.92.00R
Build number - OLYEM_U4_2.2.3
any idea how i can root it? side loading apps seems to work without any hacks, as I was able to install some apks I had laying around on my dropbox, and I have installed some using Android Commander...but I can't work out how to root it, does GingerBreak NEED a real sd card inserted to work?
Click to expand...
Click to collapse
Yep, it's worked on all the orange roms, and devices. Give it a whirl.
But before you flash a new rom over your stock tmobile, could you help us get you original sbf up on the forum. You will need to be rooted to do it.
It will help you in the long run, so if you have a problem you can return to your stock
Swyped from 'mount' Olympus
nitrox1 said:
Yep, it's worked on all the orange roms, and devices. Give it a whirl.
But before you flash a new rom over your stock tmobile, could you help us get you original sbf up on the forum. You will need to be rooted to do it.
It will help you in the long run, so if you have a problem you can return to your stock
Swyped from 'mount' Olympus
Click to expand...
Click to collapse
I have no problem doing that atall, i'm glad to help as much as I can...
so just to confirm, GingerBreak will only work with a sd card inserted, as I have tried it and it doesn't seem to do anything, but I don't have a sd card inserted atm..
how would i go about backing up the sbf afterwards? also what does sbf stand for?
thanks.
edit - just redone GingerBreak with a sd card and i can confirm I am now rooted..
can i not do any of the hacks around at the moment? as they all report versions im not on? e.g.
1.42_deodex_OlympusCamera.zip
1.57_deodex_OlympusCamera.zip
1.83_deodex_OlympusCamera.zip
also, what is deodex?
Strange, it's running a newer rom than the orange atrix, being as both orange and t-mobile are one of the same now, you would have thought orange would have had a update to the 2.2.3?
SBF means system binary file. basically its a completely stock system image. Flashing it thru RSDlite (software flashing application from motorola), will completely return your phone to stock.
Deodex: Basically, Android uses a a java based virtual machine as the bases for running programs. This virtual machine is called Dalvik. A .dex file contains the cache used by the Dalvik VM (called Dalvik-cache) for a program and is stored inside the .apk. A .odex file is an optimized version of the .dex file which gets stored next to the .apk as opposed to inside the .apk. This process is done by default to system apps. Deodexing is the process of converting the .odex files back into .dex to be stored inside the .apk so that things can be more easily modified. So a deodexed rom is one that has been through the deodexing process. Deodex can just as easily be called Unodex or any other pre-fix you wish to use.
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
For rooting check here.
http://forum.xda-developers.com/showthread.php?t=1046626
should be very easy, but you must have a sd card.
We are then after a couple of files off your phone, and a little information? Are you game?
Do you have any knowledge of using ADB?
If not have a look here to start, but goggle will be your friend on this.
http://android-dls.com/wiki/index.php?title=ADB
We're after a request for a firmware, we need to submit the following files (using adb pull):
/system/default.prop
/system/build.prop
/system/etc/motorola/bp_nvm_default/File_GSM
about phone > weptop version
Then we can hopefully grab your sbf, so we can use it for restoring the phone, if there's mistakes made.
Have to say I don't know about modding your phone, you'll have to try.
But that's why sbf, is important.
As devs have got around bootloader, I would get used to your phone, while roms like vanilla android, miui, and cm7, get ported over.
lonegunman said:
Strange, it's running a newer rom than the orange atrix, being as both orange and t-mobile are one of the same now, you would have thought orange would have had a update to the 2.2.3?
Click to expand...
Click to collapse
True but have you seen how much more the phone is to TMO renewal customers, compared to Orange renewal.
But looks like it could be a very good sbf to grab.....
Bump
Swyped from 'mount' Olympus
This guy was able to get our orange sbf in minutes so take a look: http://modmymobile.com/forums/659-motorola-atrix-4g-general/562049-atrix-firmwares-superthread.html
Edit didnt see u already posted about pulling those files woops
Hey guys, attached is the build.prop and default.prop file, the third folder you listed doesn't exist, or at least I can't see it...
www(.)mediafire(.)com/?1ducdwtg246qz57
webtop version -OSHWT_U1_6.54.0
so once you guys help me make a SBF, I can somehow then put Clockwork recovery on there and flash one of the custom roms?
thanks
karl0ss said:
Hey guys, attached is the build.prop and default.prop file, the third folder you listed doesn't exist, or at least I can't see it...
www(.)mediafire(.)com/?1ducdwtg246qz57
webtop version -OSHWT_U1_6.54.0
so once you guys help me make a SBF, I can somehow then put Clockwork recovery on there and flash one of the custom roms?
thanks
Click to expand...
Click to collapse
Yep you should be clear to go forward, just remember no way to rerun to stock at the moment.
I've forwarded this information to daywalker04 who seems to be able to find these sbf's, and it could take a while, the web site he uses is a couple of posts up.
flashing at the moment is mainly themes at the moment rather than roms
Will post sbf on the orange uk thread in general.
Plus pm you a copy, if and when we get it.
Swyped from 'mount' Olympus
karl0ss said:
Hey guys, attached is the build.prop and default.prop file, the third folder you listed doesn't exist, or at least I can't see it...
www(.)mediafire(.)com/?1ducdwtg246qz57
webtop version -OSHWT_U1_6.54.0
so once you guys help me make a SBF, I can somehow then put Clockwork recovery on there and flash one of the custom roms?
thanks
Click to expand...
Click to collapse
I wish I had that flex version.
It doesn't appear to be on Motorola's system yet. Sometimes they take a while to catch up.
Here is an alternate method to find flex file.
Be sure to set Android USB debugging mode on your device to OFF. Then make sure you have the latest Moto drivers installed on your machine. If you can connect to Motorola Software Update using Windows OS and try to run a software update--- it will not succeed because there is no update for T-Mobile UK.
When it searches for an update it will store the necessary info in a file called MSU.txt (this is the file needed) in the Motorola Software Update program directory. Then you can find the flex version.
That file is on your computers directory, rather than your phone.
Swyped from 'mount' Olympus
nitrox1 said:
Thank you for your reply. But I'm really looking for the UK Tmobile, sbf, or understanding of it.
Ps check out our uk orange thread, for a much cheaper unlock, and within 10 min!
Swyped from 'mount' Olympus
Click to expand...
Click to collapse
oh haha sorry. just recived mine and it took 3 days for $20
I have not seen it posted here but wolf849 has put together a guide to downgrade so you can downgrade, root then upgrade to .21 all without the need for root access or unlocking.
I linked below
http://forum.xda-developers.com/showthread.php?t=1622628
Thanks! I stupidly updated to .21 right away when I first got my prime and regretted it ever since. Finally I can get some use out of this!
Man this is GREAT news.
Even a noob like me has down graded from .21 down to .15
Used Vipor Mod to reroot - Thank you Vipor Boy
Intalled OTA Rootkeeper and backed up my root
reinstalled the .21 updated
restored root!!!!
Thank You Wolf
Can a TF201 owner confirm?
Thanks.
-lukin- said:
Can a TF201 owner confirm?
Thanks.
Click to expand...
Click to collapse
Confirmed !!!!!
-lukin- said:
Can a TF201 owner confirm?
Thanks.
Click to expand...
Click to collapse
Confirmed, I just finished.
Wooooooooot!!!! This is awesome.
-lukin- said:
Can a TF201 owner confirm?
Thanks.
Click to expand...
Click to collapse
Confirmed also.
Useless post was useless. figured it out. plz delete this post.
It worked! Downgraded to .15 from .21 and have now managed to install SuperUser and SU binary. Waiting for OTA Rootkeeper to install before upgrading to .21 again.
Finally I can fix some of the bugs that I've had to put up with due to Asus' incompetence, such as the bad I/O performance and shocking web browser performance.
Awesome, I've been looking for a solution for a good while. I'm glad this is confirmed. Hopefully someone will update the reference guide to link it to wolf's guide!
pileot said:
im going to post here because the other thread is like 40 pages long and i dont want to get confused with other information there (dont wanna brick my tablet)
it says to put your blob file in a directory on your prime.... Which blob is relivent for us? do we use the blob for the version were using or what? I realize this guy's native language is not english, can someone whos done it write the instructions so its easier for a non geek to understand?
Click to expand...
Click to collapse
put the blob in the root directory of your internal sd.
I extrated the blob from the US version .15.
don't us .21 that is what you have installed now and that one can not be rooted
pileot said:
im going to post here because the other thread is like 40 pages long and i dont want to get confused with other information there (dont wanna brick my tablet)
it says to put your blob file in a directory on your prime.... Which blob is relivent for us? do we use the blob for the version were using or what? I realize this guy's native language is not english, can someone whos done it write the instructions so its easier for a non geek to understand?
Click to expand...
Click to collapse
Well, we want the following blob, as it has the exploit that allows us to gain root.
WW 9.4.2.15 - MD5: 55122257B30E9376DF463F3C1A8BA702 - (or zip)
That's the "world wide" version, I'm not sure which firmware locale you should have as you're Canadian? Check you "About tablet" section with your tab settings and see which firmware you have installed.
There's threads around which tell you how to extract blobs from the firmwares on Asus' website, so if you need a different version to the world wide blob, you could extract your own.
Just follow his method 2, I did and it was very easy as long as you have adb set-up.
Mekrel said:
Well, we want the following blob, as it has the exploit that allows us to gain root.
WW 9.4.2.15 - MD5: 55122257B30E9376DF463F3C1A8BA702 - (or zip)
That's the "world wide" version, I'm not sure which firmware locale you should have as you're Canadian? Check you "About tablet" section with your tab settings and see which firmware you have installed.
There's threads around which tell you how to extract blobs from the firmwares on Asus' website, so if you need a different version to the world wide blob, you could extract your own.
Just follow his method 2, I did and it was very easy as long as you have adb set-up.
Click to expand...
Click to collapse
So with wolf guide we are downgrading to .15 then rooted in any manner we want?
Replying to see where this goes, not going to be a beta tester for it though.
kageebe said:
So with wolf guide we are downgrading to .15 then rooted in any manner we want?
Click to expand...
Click to collapse
Yes, that's correct. However I would recommend ensuring you use the blob for your region. The one Wolf links to is the WW (world wide) version.
A little help for Android noob, please. I read that I need ADB enabled.
What is that? I looked on Google Play, and there is no app specifically named ADB.
Is that the checkmark "Allow USB Debugging" listed under Developer Options?
Do I also need to install something similar on my Win7 PC.
If I can figure out this ADB stuff, I think I'm good to go.
Thanks,
bob
Edit: Will we be able to use this same technique when they come out with their new update....or is it better to wait till that arrives?
Mekrel said:
Yes, that's correct. However I would recommend ensuring you use the blob for your region. The one Wolf links to is the WW (world wide) version.
Click to expand...
Click to collapse
Is there any way to check which region my blob is from? Also, where would 1 find the blob for their region?
robertg9 said:
A little help for Android noob, please. I read that I need ADB enabled.
What is that? I looked on Google Play, and there is no app specifically named ADB.
Is that the checkmark "Allow USB Debugging" listed under Developer Options?
Do I also need to install something similar on my Win7 PC.
If I can figure out this ADB stuff, I think I'm good to go.
Thanks,
bob
Edit: Will we be able to use this same technique when they come out with their new update....or is it better to wait till that arrives?
Click to expand...
Click to collapse
ADB is a tool that comes with the Android SDK, so you need to install the SDK onto your laptop and install the SDK Tools and Platform Tools. Then edit your path variable so that your command line know's where to find the adb executable. You might also have to install Java development kit, I'm not sure if the Android SDK manager moans if you don't have it installed.
There's easier ways of using ADB, by just downloading the .dll and .exe and referencing them via command line but I always recommend having a full SDK tool install and learning about ADB as it's a god send.
kageebe said:
Is there any way to check which region my blob is from? Also, where would 1 find the blob for their region?
Click to expand...
Click to collapse
Like I said, go to "About Tablet" in your tablet settings and there's something called a "Build Number". Mine says IML74K.WW_epad-9.4.2.21-20120323 - the initials stipulate which region firmware you have, in my case "WW" aka World Wide.
If anyone can locate a US blob please let me know, I've been searching on the forums for a .15 US blob to no avail and no luck at all.
Hello XDA-san
This is my first time working with cygwin and Android Kitchen and I wanted to make sure I didn't miss anything that will royally brick my s4. I have attached screenshots of my journey for reference.
I started with the stock ROM from you know where, version 4.4.2 (i337MOYAFNC1) and proceeded to remove the KNOX bootloader (using instructions from SilviuMik). I skipped the last step where it is re-md5, to continue on to the kitchen..
Using the de-knoxed tar file, I created a working folder for the ROM in the kitchen. It started unpacking, everthing went well. When i was prompted to choose if I wanted to extract the CSC, I said no.. because the DiskInternals Linux reader was giving me an error saying along the lines of cant read disk..
From my working folder, I proceeded to root & busybox, all went well. I then deodexed both the system apps and framework, all went well.
lastly, I made a build from the working folder. Selected all default options while doing so (see pictures) , signed the freshly minted rom and voila.
If the repacking was successful there is not much to fear about.
(You may want to lookup if there is any dependents (in the rom) by using the removed knox bootloader (atleast remove the knox apks I guess)
the CSC is really nothing important:
A common short code (CSC) is a short telephone number, usually consisting of five digits, that is used to address SMS and MMS messages from a cellular telephone. Common short codes may also be called mobile short codes or short numbers. Each common short code is designed to be unique to each operator.
Click to expand...
Click to collapse
Just include the one from the stockrom. btw, I have successfully manually unpacked the CSC file a year ago or so with simg2img, it only contained crap (samsung only files for altering behavior in TW rom and bloatware), the hidden partition or preload partition may also contain unwanted crap btw
So go ahead and flash it, your phone will not get bricked by this in any way.
broodplank1337 said:
If the repacking was successful there is not much to fear about.
(You may want to lookup if there is any dependents (in the rom) by using the removed knox bootloader (atleast remove the knox apks I guess)
the CSC is really nothing important:
Just include the one from the stockrom. btw, I have successfully manually unpacked the CSC file a year ago or so with simg2img, it only contained crap (samsung only files for altering behavior in TW rom and bloatware), the hidden partition or preload partition may also contain unwanted crap btw
So go ahead and flash it, your phone will not get bricked by this in any way.
Click to expand...
Click to collapse
Hi broodplank1337, thhank you for your reply
So would it be better to go into my newly minted zip file and hunt down the knox apks / dependencies? Or should I flash the ROM then use root browser to get rid of them?
I found this list "
Delete the files in the following files in this order.
/system/app/KNOXAgent.apk
/system/app/KNOXAgent.odex
/system/app/KLMSAgent.apk
/system/app/KLMSAgent.odex
/system/app/KnoxAttestationAgent.apk
/system/app/KnoxAttestationAgent.odex
/system/app/KNOXStore.apk
/system/app/KNOXStore.odex
/system/app/ContainerAgent.apk
/system/app/ContainerAgent.odex
/system/lib/libknoxdrawglfunction.so
/system/app/ContainerEventsRelayManager.apk
/system/app/ContainerEventsRelayManager.odex
/system/app/KNOXStub.apk <--- delete if you have, some will not
Delete the following folders
/system/containers
/system/preloadedkiosk
/system/preloadedsso
/system/etc/secure_storage/com.sec.knox.store
/data/data/com.sec.knox.seandroid
/data/data/com.sec.knox.store
/data/data/com.sec.knox.containeragent
/data/data/com.samsung.android.walletmanager
The French Tickl3r said:
Hi broodplank1337, thhank you for your reply
So would it be better to go into my newly minted zip file and hunt down the knox apks / dependencies? Or should I flash the ROM then use root browser to get rid of them?
I found this list "
Delete the files in the following files in this order.
/system/app/KNOXAgent.apk
/system/app/KNOXAgent.odex
/system/app/KLMSAgent.apk
/system/app/KLMSAgent.odex
/system/app/KnoxAttestationAgent.apk
/system/app/KnoxAttestationAgent.odex
/system/app/KNOXStore.apk
/system/app/KNOXStore.odex
/system/app/ContainerAgent.apk
/system/app/ContainerAgent.odex
/system/lib/libknoxdrawglfunction.so
/system/app/ContainerEventsRelayManager.apk
/system/app/ContainerEventsRelayManager.odex
/system/app/KNOXStub.apk <--- delete if you have, some will not
Delete the following folders
/system/containers
/system/preloadedkiosk
/system/preloadedsso
/system/etc/secure_storage/com.sec.knox.store
/data/data/com.sec.knox.seandroid
/data/data/com.sec.knox.store
/data/data/com.sec.knox.containeragent
/data/data/com.samsung.android.walletmanager
Click to expand...
Click to collapse
Oh I thought you were building an odin rom? zip you say?
Anyways, just remove em from the system folder and test it's result. You can always test roms without damaging your device at any time, read: it's impossible for a ROM to brick a phone, the thing that can brick it is the kernel, but only if using a kernel from an other device or so.
so don't be afraid to test it, if it doesn't work just continue your work. if it works, good joob
broodplank1337 said:
Oh I thought you were building an odin rom? zip you say?
Anyways, just remove em from the system folder and test it's result. You can always test roms without damaging your device at any time, read: it's impossible for a ROM to brick a phone, the thing that can brick it is the kernel, but only if using a kernel from an other device or so.
so don't be afraid to test it, if it doesn't work just continue your work. if it works, good joob
Click to expand...
Click to collapse
One caveat to this, and this mostly applies to Verizon and AT&T users, but if you have upgraded to KitKat and kept root using SuperSu's survival mode and your planning to test a rom using Safestrap, you better make sure that the su binary is in xbin and bin (.ext/.su) and that the Superuser.apk is in /system/app. Also make sure that the permissions are set correctly for su (chmod 06755 chown 0.0) and have busybox in the rom as well, or at least have busybox install in the updater-script and make sure everything symlinks correctly.
The best thing to do when testing roms to avoid having to worry about losing root is to download Chainfire's SuperSu zip and flash it after you flash your rom you're testing (but before it reboots into the rom for the first time) the reason I even mention all of this is because currently we (Verizon and AT&T users) have no way to root a device thats taken a complete 4.4.2 OTA.
Surge1223 said:
One caveat to this, and this mostly applies to Verizon and AT&T users, but if you have upgraded to KitKat and kept root using SuperSu's survival mode and your planning to test a rom using Safestrap, you better make sure that the su binary is in xbin and bin (.ext/.su) and that the Superuser.apk is in /system/app. Also make sure that the permissions are set correctly for su (chmod 06755 chown 0.0) and have busybox in the rom as well, or at least have busybox install in the updater-script and make sure everything symlinks correctly.
The best thing to do when testing roms to avoid having to worry about losing root is to download Chainfire's SuperSu zip and flash it after you flash your rom you're testing (but before it reboots into the rom for the first time) the reason I even mention all of this is because currently we (Verizon and AT&T users) have no way to root a device thats taken a complete 4.4.2 OTA.
Click to expand...
Click to collapse
Seriously? wow, thanks for mentioning, I can't believe what a pricks Verizon and AT&T are. Same count for Samsung that handles knox regulation in the USA (while not in other countries). In the USA you get pretty much screwed by the carriers and manufacturers the hard way.
In The Netherlands (where I live) it's even illegal to sell smartphones that are not unlocked by default. and the only thing a carrier may do is adding a CSC (Consumer Software Customization) package. This should be in the USA as well!
In the USA companies get to private / independent it seems. they should be regulated by national government rules. instead of making their own. (this keeps the crap like the problem you described away)
But Samsung should be regulated as well, there is no chance that will happen (south-korea), and their phones will contain more and more backdoors / suspicious daemons / methods of screwing you and so on, because who checks it, no one. Oh yes only someone, the NSA that adds even more of this stuff, like a VPN Interceptor, which no one is waiting for as well.
Anyways, life (or actually companies) is (are) a *****. Only strict regulation could solve this, but who still believes in regulation after seeing what the NSA all did, they broke like every single rule and forced companies to merge their crap (most likely, or a huge payment, but no single company actually likes that)
- NSA 'was allowed' to break in all PC's because that where outside the USA. that just ridiculous but true
- NSA applied their 'jizz' to all super famous apps like Facebook.
Even though it sounds like I say USA is the culprit thats not true, The netherlands have BREIN, which is the anti piracy company.
This asshole tim kuik has,
a. destroyed the piratebay for the whole world (even though it's recuping soon)
b. have done a million requests on removing uploaded movies (on newsgroups)
I really went OT all the way at this reply xd but you get my point :good:
The product gets made, then infected by the creator, then gets forced to merge nsa crap. after that it goes to the carrier which installs even more crap.
there is not a single bit of freedom left
Thank you both for these tips. Being a rather unexperienced cook, I would have never thought of these important details mentioned above.
it really is a shame how tightly service provider have our collective balls in a grasp..
broodplank1337 said:
Seriously? wow, thanks for mentioning, I can't believe what a pricks Verizon and AT&T are. Same count for Samsung that handles knox regulation in the USA (while not in other countries). In the USA you get pretty much screwed by the carriers and manufacturers the hard way.
In The Netherlands (where I live) it's even illegal to sell smartphones that are not unlocked by default. and the only thing a carrier may do is adding a CSC (Consumer Software Customization) package. This should be in the USA as well!
In the USA companies get to private / independent it seems. they should be regulated by national government rules. instead of making their own. (this keeps the crap like the problem you described away)
But Samsung should be regulated as well, there is no chance that will happen (south-korea), and their phones will contain more and more backdoors / suspicious daemons / methods of screwing you and so on, because who checks it, no one. Oh yes only someone, the NSA that adds even more of this stuff, like a VPN Interceptor, which no one is waiting for as well.
Anyways, life (or actually companies) is (are) a *****. Only strict regulation could solve this, but who still believes in regulation after seeing what the NSA all did, they broke like every single rule and forced companies to merge their crap (most likely, or a huge payment, but no single company actually likes that)
- NSA 'was allowed' to break in all PC's because that where outside the USA. that just ridiculous but true
- NSA applied their 'jizz' to all super famous apps like Facebook.
Even though it sounds like I say USA is the culprit thats not true, The netherlands have BREIN, which is the anti piracy company.
This asshole tim kuik has,
a. destroyed the piratebay for the whole world (even though it's recuping soon)
b. have done a million requests on removing uploaded movies (on newsgroups)
I really went OT all the way at this reply xd but you get my point :good:
The product gets made, then infected by the creator, then gets forced to merge nsa crap. after that it goes to the carrier which installs even more crap.
there is not a single bit of freedom left
Click to expand...
Click to collapse
The NSA can screw a cow. USA is Freedom? Like hell. I live here and am starting to become ashamed of my country. I hate the government, more directly this president. Anyway, whats a VPN Interceptor? Sounds scary..
But about the OP, can you build an Odin tar with the older Bootloaders in and newer system images to remove knox warranty and allow users to upgrade without screwing themselves? Last i checked, you needed a way to sign the tar file to match with the current bootloader checking.
broodplank1337 said:
the CSC is really nothing important:
Click to expand...
Click to collapse
CSC is "Country/Carrier Specific Config", not "common short code"
While it's not so important, skipping it may produce many side effects in normal work.
The common way to deal with CSC is extract it and pre-integrate into system - that's what stock recovery is doing upon first boot after flash.
sorg said:
CSC is "Country/Carrier Specific Config", not "common short code"
While it's not so important, skipping it may produce many side effects in normal work.
The common way to deal with CSC is extract it and pre-integrate into system - that's what stock recovery is doing upon first boot after flash.
Click to expand...
Click to collapse
This doesn't always work. I used to try this with rooted dump/repacks for S4, N2 and E4GT and we got mixed results not including Samsung's cache.img. In Sprint's case this defaulted the carrier to XAS, an internal use only code that doesn't fully enable everything for Sprint. I don't recall if this was on images with a blank data.img only or "nodata" cases as well.
garwynn said:
This doesn't always work. I used to try this with rooted dump/repacks for S4, N2 and E4GT and we got mixed results not including Samsung's cache.img. In Sprint's case this defaulted the carrier to XAS, an internal use only code that doesn't fully enable everything for Sprint. I don't recall if this was on images with a blank data.img only or "nodata" cases as well.
Click to expand...
Click to collapse
I've did it on GT-I9100, GT-I9300, SHV-E210K, GT-N7100, SHV-E330S. It worked always. Sometimes CSC is multi-CSC where you have to choose correct version.
I didn't use operator-specific models. So probably some additional steps required. But anyway, CSC from cache partition is simply copied to system by recovery. To be more precise, you can check command file in cache.img - this is where "magic" happens
Hi devs, i first time cooked prerooted deodexed rom from stock 4.4.2 rom using cygwin and andriod kitchen. every thing went well. my only question is can i remove modem from output zip as i don't want to use that modem.
Got status 7 error installation aborted.
navdeepavi said:
Got status 7 error installation aborted.
Click to expand...
Click to collapse
go to advanced > show log in recovery
As a follow up to the status 7 error, I spent quite a while figuring out what caused it and how to solve it. I posted this on another thread but ill quote myself here.
The status 7 failed to mount /preload error and why it happens:
Lets take a minute to go over why this happens and what it means. First what is /preload anyways? Well lets take a look at how it gets mounted, consider mount points below:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/hidden", "/preload");
We can infer from the point arguements that /preload is the mount point for the "hidden" partition. Well then what is this "hidden" partition then you ask? Well hidden contains some useless crap Samsung uses to verify integrity of the system partition when in recovery
So the idea is to wipe data/factory reset in recovery followed by making sure to flash hidden.img.ext4 prior to cache.img.ext4. I think my inclusion of cache.img.ext4 on accident in the first tar is the root of the cause so ive uploaded a new one that doesnt contain it so it wont fail at step 1.
So essentially you cant flash a a full-wipe or no-wipe Odin tar to go back. You have to use a custom made Odin tar. Also for people getting the status 7 error where /preload fails to mount after flashing cache the solution is to boot into stock recovery and factory data reset followed by flashing hidden.img.ext4 via Odin or Heimdall.
Click to expand...
Click to collapse
OK
So I managed to create a flashable
.zip of I337MVLUFNE1:
Rooted, Deodexed, Knox-Free,
Zipaligned, Debloated, KT Kernel!
Will post link here if you guys want!
Adizzzle said:
OK
So I managed to create a flashable
.zip of I337MVLUFNE1:
Rooted, Deodexed, Knox-Free,
Zipaligned, Debloated, KT
Will post link here if you guys want!
Click to expand...
Click to collapse
oh sweet, sure ill gladly test it out
ty!
go habs GO
The French Tickl3r said:
oh sweet, sure ill gladly test it out
ty!
go habs GO
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23501681358539374
It has a TMO KT kernel so you may need a
different kernel depending on your device.
It's debloated, but only lightly.
I have a heavily debloated version uploading.
Adizzzle said:
http://www.androidfilehost.com/?fid=23501681358539374
It has a TMO KT kernel so you may need a
different kernel depending on your device.
It's debloated, but only lightly.
I have a heavily debloated version uploading.
Click to expand...
Click to collapse
awesome ty
i have the i337m with telus, and if i remember correctly, I had to use the TMO kernel when I flashed the maple leaf ROM a while back
The French Tickl3r said:
awesome ty
i have the i337m with telus, and if i remember correctly, I had to use the TMO kernel when I flashed the maple leaf ROM a while back
Click to expand...
Click to collapse
Yeah it was made for a Telus I337M
The only thing missing is the APN.
Made with ArchiKitchen.
Root:
1. Enable Unknown Sources under Security
2. Unlock Developer Options
3. Enable Usb Debugging
4. Install Kingroot
http://www.kingroot.net
5. Run the app and follow instructions until root
6. Download mrw folder
http://www.4shared.com/zip/HucTEoJoba/mrw.html
then place it in the root of Device Storage using the Default app "MyFiles"
7. Install ROM Toolbox Pro
http://www.4shared.com/mobile/c87lgrS4ba/ROM_Toolbox_Pro_v6065.html
8. Run the app and Grant Root Permission
9. Open Terminal Emulator under Tools tab
Enter Commands as follow:
su
sh /sdcard/mrw/root.sh
10. Let it run
11. After is done it will open SuperSu
12. Update Binary as Normal
13. Reboot
14. Your done :good:
Enable Tethering
Using a root file explorer such as ES File Explorer or your preferred file manager, mount /system rw. Navigate to /system and find and open the build.prop file.
Find..
Code:
# Disable Tethering (Tracfone)
ro.tether.denied=true
Change to...
Code:
# Disable Tethering (Tracfone)
ro.tether.denied=false
Save the file, make sure its permissions are set to -rw-r--r--, reboot and Tethering will be available in the settings menu.
Excuse me, does this "Rooting" process allows me to use the micro Sim of any company?
Koenji said:
Excuse me, does this "Rooting" process allows me to use the micro Sim of any company?
Click to expand...
Click to collapse
Nope, any SIM other than a Verizon Wireless one will simply say Invalid SIM.
bfoos said:
Nope, any SIM other than a Verizon Wireless one will simply say Invalid SIM.
Click to expand...
Click to collapse
If you don't mind telling me, what process is the one required so that the phone recognizes SIMS from other companies? Flashing? Sorry for the amateur question.
I have no idea. There isn't anything to flash. No roms, no kernels, no recoveries no nothing. There appears to be zero interest in this variant by the dev community.
bfoos said:
I have no idea. There isn't anything to flash. No roms, no kernels, no recoveries no nothing. There appears to be zero interest in this variant by the dev community.
Click to expand...
Click to collapse
I guess i will wait a bit for those tools before i give up and try to sell this device since its no use to me, being unable to use SIMS for other companies.
Koenji said:
I guess i will wait a bit for those tools before i give up and try to sell this device since its no use to me, being unable to use SIMS for other companies.
Click to expand...
Click to collapse
You may use a verified online website to sim card unlock the phone to any company
Koenji said:
Excuse me, does this "Rooting" process allows me to use the micro Sim of any company?
Click to expand...
Click to collapse
No sir im sorry
ordinarykid23 said:
You may use a verified online website to sim card unlock the phone to any company
Click to expand...
Click to collapse
I can confirm that this does in fact not work. Invalid SIM. No unlock menu.
bfoos said:
I can confirm that this does in fact not work. Invalid SIM. No unlock menu.
Click to expand...
Click to collapse
Thanks for the information fellas. So basically we have to wait until someone with the knowledge can extract those files (Roms, kernels, recoveries).
By some of the comments i've seen here, i get the impression that only the high-end phones are the ones that the community gets behind? How unfortunate if true.
By the way i saw in a different post someone uploaded a Rom http://forum.xda-developers.com/grand-prime/development/rom-download-sm-s920l-straight-talk-usa-t3265004/page2
Yes, and that ROM will turn your Grand Prime into a Core Prime (Franken Prime) with lots of things not working. There are no stock roms available for this variant.
bfoos said:
Yes, and that ROM will turn your Grand Prime into a Core Prime (Franken Prime) with lots of things not working. There are no stock roms available for this variant.
Click to expand...
Click to collapse
Thanks for the warning.
i cant get the build.prop to save after editing the data tethering line... idk how to set the permisions on the file
Galaxy Grand Prime Value Edition 5.1.1
Hello guys can you help me. ? Android os is draining battery like hell .About 4-5% and it's the second after screen. Before this facebook messenger and facebook was sucking my battery . I uninstalled them.. but android os is still draining my battery.. what I should do ? It' draining about 10-15 % overnigh . I have installed greenfy and i just have only wifi opened.. but it's still draining. Please helpp
Spartacus first you have to be root, then es editor to edit the build.prop, close out and reboot...should see the the tether option enabled...worked flawless for me
NullByte04 said:
Spartacus first you have to be root, then es editor to edit the build.prop, close out and reboot...should see the the tether option enabled...worked flawless for me
Click to expand...
Click to collapse
i actually was able to do it, using the rom tools thing that the guy provides in his steps
Yea that works to both shouldn't have a issue with
Can someone pull all system files from a (preferably) completely stock or factory reset device via adb? Please! Thank you!
Sent from my HTCD200LVWPP using Tapatalk
bfoos said:
I have no idea. There isn't anything to flash. No roms, no kernels, no recoveries no nothing. There appears to be zero interest in this variant by the dev community.
Click to expand...
Click to collapse
yeah ik theres alot of interest but no ones developing for it id love to but i dont know much for baking android os id take a look into the s5 and s6 area since it uses a bit of the same software.
Hello.
I was forced to reinstall firmware due to phone issues.
Now I'm again with root and TWRP.
Firmware is on nougat, version c900b300 but many files are missing.
In particular, themes cannot be applied even if I can download them.
I followed a procedure suggested for the Mate 8 but with no results.
Is someone able to help me?
I think this is not a post for q&a section.
Otherwise please move it.
Thanks.
Ah, even the ringtones folder is empty, but this is not a big issue...
Try these 2 methods
1 - https://forum.xda-developers.com/honor-6x/help/solved-huawei-gr5-2017-honor-6x-problem-t3606037
2 - https://forum.xda-developers.com/honor-6x/help/theme-issue-5-0-upgrade-t3579812/page2
First method pushed FM spk in data folder, I rebooted but no FM radio app shows up.
Regarding second method, Google drive file doesn't exist.
I hope to be able to install Oreo when available through TWRP.
Now I don't have the updater and I'm not receiving ota update from Huawei. Unfortunately I'm stuck with March security updates
Dammit, I'm out of ideas at the moment. Plus, i didn't knew that even updater was missing... You wanna try with an apk of mine extracted?
of course mate.
Now I'm more relaxed, as I understand that is better just playing with this phone. I'm not gonna put job related files anymore in, so if something happens, I can recover easily.
Baaaaaaaaad phone...
Ah, sorry if I forgot to mention that I miss A LOT of file. Basically all the crapware like Health or Huawei related bullshits, updater, ringtones, themes are not installing. Cannot even load a different wallpaper.
But I have nougat base and patches till March.
Better than nothing!
Ringtones= thank you Zedge to exist!
Themes= amen, I can live with it
Diamantes said:
Ah, sorry if I forgot to mention that I miss A LOT of file. Basically all the crapware like Health or Huawei related bullshits, updater, ringtones, themes are not installing. Cannot even load a different wallpaper.
But I have nougat base and patches till March.
Better than nothing!
Ringtones= thank you Zedge to exist!
Themes= amen, I can live with it
Click to expand...
Click to collapse
For Huawei bloatware it's surely a positive thing if you don't care, since that those results "well" radicated into system and aren't easy to remove. For all the rest, looks like you are on a firmware build that was created to another build, and so causes various incompatibilities... But it's the worst case that i saw, except bricking related cases maybe a rebranding to an other variant, with the flash of another firmware could solve at least the missing apps issue. Anyway, i uploaded the updater apk; after all i don't think it'll works sincerely neither making it a system app with apps or modules like systemizer, if all those issues are present already... But in the worst case here, you'll just get an install failure due to an apk version that doesn't match your first, initial build. Try for fun, i would say.
Thank you for the tips.
Even if I read on this forum (honor in general) many different opinions regarding how to flash a Rom with twrp...and sometimes even with dload method.
I mean: it seems to me that with twrp is compulsory to flash the zip with "PV" only, even if many disagree
With dload, unzip the folder and better to put all the files, not only the .app one inside...
Am I right?
By the way, the updater apk should be put inside what folder? Of course it cannot be installed normally (file corrupted)
You can use apps like Link2SD, but if the file looks corrupt (had this problem too when i accidentally deleted compass app time ago) it means that doesn't matches your build number. You could try by installing a version that matches your actual build.
Diamantes said:
Thank you for the tips.
Even if I read on this forum (honor in general) many different opinions regarding how to flash a Rom with twrp...and sometimes even with dload method.
I mean: it seems to me that with twrp is compulsory to flash the zip with "PV" only, even if many disagree
With dload, unzip the folder and better to put all the files, not only the .app one inside...
Am I right?
By the way, the updater apk should be put inside what folder? Of course it cannot be installed normally (file corrupted)
Click to expand...
Click to collapse
Yes, with dload method, you need to flash all files available in zip to get everything working, i tries this and everything worked for me without anything missing.
For flashing zip, yes it is PV files that can be flashed via Twrp
The problem, as far as I know, is that now Huawei stopped releasing ROM files and even the .ru website now will have problems to collect files...
Diamantes said:
The problem, as far as I know, is that now Huawei stopped releasing ROM files and even the .ru website now will have problems to collect files...
Click to expand...
Click to collapse
They are still getting it. Not sure how
Solution
Hey, i have had the same Problem with the theme changer - found this solution which just take 1 minute
Themes:
- I downloaded the Huawei Tool from here:
https://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
- enable USB-Debugging connect your phone to the PC and start the tool
- choose "7" for utilities
- after that choose "12. Install /data/hw_init (Mate8,P9,P9 Plus)" and confirm
- after reboot the theme change will work again!
Will it work on honor 6x? The hw data is only for p9 ,isnt it?
starkeeper2018 said:
Hey, i have had the same Problem with the theme changer - found this solution which just take 1 minute
Themes:
- I downloaded the Huawei Tool from here:
https://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
- enable USB-Debugging connect your phone to the PC and start the tool
- choose "7" for utilities
- after that choose "12. Install /data/hw_init (Mate8,P9,P9 Plus)" and confirm
- after reboot the theme change will work again!
Click to expand...
Click to collapse
Will it work on honor 6x..the hw data is showing only for honor p9 ,etc but not 6x