Related
Greetings all.
Firstly, thanks for such a great repository of info. I have successfully managed to root my phone using Chainfire's method. I'm supremely happy to have even accomplished that.
I'm not a tech noob, but I'm quite new to Androids.
The feeling of frustration at trying to learn new terms and make sense out of all this information is HUGE. I have seen various "noob" entitled threads, as well as threads (Like ChainFire's) that make it somewhat easier. However, there seems to be so many threads to look through, and different info/terms that at this point trying to add a battery percentage mod to the status bar (which I'm sure is an easy easy thing to some of you) has become quite the gargantuan task for me.
---to that topic i'm having trouble understanding what it means when people say "flash using CWM". I understand "flash" (i think) and i know what CWM is, but have no idea what steps to take to "flash the necessary apk" files.
Do i use CWM? I've seen mention of using a root explorer or just adding the files overtop.
Then I've read "backup first". Yes, i know i want to do that. I have Titanium Backup on my device. And I've backed it up> but then i read that i should be using Nandroid. Where the hell do i get that? lolz. I mean I've searched for it and found threads, but from HTC section. Is it even compatible? No D/L links...
arrrrgggggg!!!
I did find some resources from Villain rom. So at least I found some term definitions.
Speaking of Roms...
If I have KF3 on my phone, and i wanted to put Villain Rom v.2 on it, would i need to install KF2? Or is it recommended to put on KG1? Am I flashing that like I flashed the kernels when rooting (via odin)?
------------------------------------
Well if you made it through that - thanks. My head feels like it's going to explode. Too much info, too fast. I feel like I've had a ton of info my brain really doesn't comprehend. What was that movie...Johnny Mnemonic?
I wish we had a Rooting Rom'ing Guide for Noobs. One that explained what terms meant along with the instructions. Maybe a screenshot or two.
benivolent said:
Greetings all.
Firstly, thanks for such a great repository of info. I have successfully managed to root my phone using Chainfire's method. I'm supremely happy to have even accomplished that.
I'm not a tech noob, but I'm quite new to Androids.
The feeling of frustration at trying to learn new terms and make sense out of all this information is HUGE. I have seen various "noob" entitled threads, as well as threads (Like ChainFire's) that make it somewhat easier. However, there seems to be so many threads to look through, and different info/terms that at this point trying to add a battery percentage mod to the status bar (which I'm sure is an easy easy thing to some of you) has become quite the gargantuan task for me.
---to that topic i'm having trouble understanding what it means when people say "flash using CWM". I understand "flash" (i think) and i know what CWM is, but have no idea what steps to take to "flash the necessary apk" files.
Do i use CWM? I've seen mention of using a root explorer or just adding the files overtop. CWM comes with Chain Fires Rooted Kernel. If you have rooted your phone using Chaninfiire Kernel you should have an app called CWM. you need to put the apk in your internal storage using PC, then open CWM, theer is an option to install apk. select that and browse to the file.. all done
Then I've read "backup first". Yes, i know i want to do that. I have Titanium Backup on my device. And I've backed it up> but then i read that i should be using Nandroid. Where the hell do i get that? lolz. I mean I've searched for it and found threads, but from HTC section. Is it even compatible? No D/L links...
it means backing up ur phone using CWM.. open CWM and theer is a backup option select that or just boot to recovery power off then Power+home key+ volume Up) and select backup from there
arrrrgggggg!!!
I did find some resources from Villain rom. So at least I found some term definitions.
Speaking of Roms...
If I have KF3 on my phone, and i wanted to put Villain Rom v.2 on it, would i need to install KF2? Or is it recommended to put on KG1? Am I flashing that like I flashed the kernels when rooting (via odin)?
no ur not required to put KF2 first. flash the villain rom using CWM (install zip from sd card)
------------------------------------
Well if you made it through that - thanks. My head feels like it's going to explode. Too much info, too fast. I feel like I've had a ton of info my brain really doesn't comprehend. What was that movie...Johnny Mnemonic?
I wish we had a Rooting Rom'ing Guide for Noobs. One that explained what terms meant along with the instructions. Maybe a screenshot or two.
Click to expand...
Click to collapse
hope that helps
Thanks indeed!
I did have a problem with the CWM, I did pretty much exactly as you mentioned - prior to me making this thread - and I used cwm to browse to the location with the apk on my sd card. installed... nothing happened.
re: cwm and back up - again, did as you had mentioned, but when i go into cwm and press "backup" it give me option to name the file, and then resets into recovery mode (i think - as i've used the buttons method to get to the same screen) but there is no "back up" option listed. also there is some csc error message. see picture.
re: villain rom. so to confirm, I do not have to change from kf3 to another kernel to install VR2.0?
Have to agree, especially for people coming form the world of Ilockedinsideaboxfullofnothingtochangeordophone
What are the benefits of flashing a custom rom?
PM sent.
Sent from my GT-I9100 using XDA Premium App
benivolent said:
Thanks indeed!
I did have a problem with the CWM, I did pretty much exactly as you mentioned - prior to me making this thread - and I used cwm to browse to the location with the apk on my sd card. installed... nothing happened.
re: cwm and back up - again, did as you had mentioned, but when i go into cwm and press "backup" it give me option to name the file, and then resets into recovery mode (i think - as i've used the buttons method to get to the same screen) but there is no "back up" option listed. also there is some csc error message. see picture.
re: villain rom. so to confirm, I do not have to change from kf3 to another kernel to install VR2.0?
Click to expand...
Click to collapse
according to that pic..u dont have cwm installed properly.. that recovery screen is from the default recovery which comes from the phone..ur not flashing your rooted kernel properly.. ur recovery screen should be orange in colour and it will be stated there clockwork mod recovery
and you can safely ignore that csc error..
THUDUK said:
Have to agree, especially for people coming form the world of Ilockedinsideaboxfullofnothingtochangeordophone
What are the benefits of flashing a custom rom?
Click to expand...
Click to collapse
You mean like my Blackberry? heh. for sure.
I'm hoping with the Custom Rom it's got less bloatware, better battery life.
xinfinityoO said:
according to that pic..u dont have cwm installed properly.. that recovery screen is from the default recovery which comes from the phone..ur not flashing your rooted kernel properly.. ur recovery screen should be orange in colour and it will be stated there clockwork mod recovery
and you can safely ignore that csc error..
Click to expand...
Click to collapse
I never installed cwm as a separate action. Only used the "cwm" that came with chainfire's stuff. I've seen the orange colour you speak of in an faq I've found, but I'm not sure how to remedy this....
I am using the system as described for flashing kernels in Chainfire's thread.
1. debug mode on phone
2. phone into download mode (three buttons)
3. start Odin
4. plug phone into usb
5. browse to zip/tar file of unsecured
6. phone reboots
7. root phone
8. install secured kernel to sd card
9. use cwm to flash that kernel. (which did so successfully i believe)
Is there another step I should have done to install CWM? will reflashing the kernel via odin fix this?
thanks!
benivolent said:
I never installed cwm as a separate action. Only used the "cwm" that came with chainfire's stuff. I've seen the orange colour you speak of in an faq I've found, but I'm not sure how to remedy this....
I am using the system as described for flashing kernels in Chainfire's thread.
1. debug mode on phone
2. phone into download mode (three buttons)
3. start Odin
4. plug phone into usb
5. browse to zip/tar file of unsecured
6. phone reboots
7. root phone
8. install secured kernel to sd card
9. use cwm to flash that kernel. (which did so successfully i believe)
Is there another step I should have done to install CWM? will reflashing the kernel via odin fix this?
thanks!
Click to expand...
Click to collapse
ur puting the kernel in the PDA section ?? and it is the chainfire kernel ur flashing using ODIN??
boot to download mode
CF kernel >> PDA (Odin)
Flash
Reboot
You get yellow triangle
to remove triangle use a usb jig..its the best option ..u can get it from ebay for less then 10 bux
or
transfer zimage file from the CF kernel.tar file (extract) to internal storage
boot to download mode
stock kernel >> PDA (ODIN)
flash
reboot
open up CWM application(should be in your apps)
choose flash kernel
browse to the zimage file from earlier (from cf kernel)
all done
your step 8 looks wrong.. secured kernel would mean stock..u will not flash the stock kernel (secured)
benivolent said:
You mean like my Blackberry? heh. for sure.
I'm hoping with the Custom Rom it's got less bloatware, better battery life.
Click to expand...
Click to collapse
Not unless bloatware has been removed . Read the rom posts in dev section .
Villain lite rom would be one with less bloatware or use the remove bloatware script same section .
Battery life is more than just the rom much is down to user apps installed .
Villian full rom thread has some useful battery info over the last ten or so pages .
jje
xinfinityoO said:
ur puting the kernel in the PDA section ?? and it is the chainfire kernel ur flashing using ODIN??
Yes, browsing to the CF kernel in pda section of odin
boot to download mode
CF kernel >> PDA (Odin)yup
Flashyup
Rebootyup
You get yellow triangleyup
to remove triangle use a usb jig..its the best option ..u can get it from ebay for less then 10 bux don't have a jig... yet
or
transfer zimage file from the CF kernel.tar file (extract) to internal storage
boot to download modemight do this then
stock kernel >> PDA (ODIN)
flash
reboot
open up CWM application(should be in your apps)
choose flash kernel
browse to the zimage file from earlier (from cf kernel)
all done
your step 8 looks wrong.. secured kernel would mean stock..u will not flash the stock kernel (secured)I did flash the secured version of the kernel back onto it after rooting it. That might have been the issue. I just reflashed CF kernel and had the CWM work differently for the back up. still not orange, but at least it actually backed it up!!! yaaaahooooo!
Click to expand...
Click to collapse
initially i had rooted with the one click method, and then still didn't have root so changed and did the chainfire method. but still put a stock kernel on after flashing and getting root with super one click. I think I didn't realize that the CF kernel means I get root without having to use superone click. and still put a stock kernel back on afterwards.
JJEgan said:
Not unless bloatware has been removed . Read the rom posts in dev section .
Villain lite rom would be one with less bloatware or use the remove bloatware script same section .
Battery life is more than just the rom much is down to user apps installed .
Villian full rom thread has some useful battery info over the last ten or so pages .
jje
Click to expand...
Click to collapse
Ok, fantastic. Thanks I'll have a look at that. I may not have gotten to the end yet with all 700+ pages hehe
And thanks to all who've responded to my issues. Much appreciated.
Here's the reflashed CF kernel CWM doing the back up... this about right?
benivolent said:
And thanks to all who've responded to my issues. Much appreciated.
Here's the reflashed CF kernel CWM doing the back up... this about right?
Click to expand...
Click to collapse
yes
get a jig ..will save u a lot of work.. since i think u made an error while trying to remove the triangle
xinfinityoO said:
yes
get a jig ..will save u a lot of work.. since i think u made an error while trying to remove the triangle
Click to expand...
Click to collapse
I purchased one from somewhere in the UK (off ebay), just waiting for it to arrive.
So now I've gotten my CWM working and i've backed up my phone with titanium and cwm (no need for nand i guess?) Can i safely try to add the mods for the battery %?
benivolent said:
I purchased one from somewhere in the UK (off ebay), just waiting for it to arrive.
So now I've gotten my CWM working and i've backed up my phone with titanium and cwm (no need for nand i guess?) Can i safely try to add the mods for the battery %?
Click to expand...
Click to collapse
as far as i think..backup using cwm is nand backup..unless i am wrong
once you have cwm backup u can play around with mods
thanks again for your help.
Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this
wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day
You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.
Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now
I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?
Hey guys,
I searched the web already but I can't find a solution. My S5 won't turn bluetooth on anymore. It's rooted but after rootprocess, BT worked fine. I can't remember that I've done something around BT. I've deleted Data and Cache already and rebooted the phone afterwards but still no Bluetooth. I opened Quick Connect and a Toast appeared which said "Bluetooth activated" but there wasn't the logo in the status bar and the icon in the notification center was also grey. Hope that you can help me.
Pozdrav
Croatia1
Any solutions?
Hey mate..
Any solution yet..?
Mine wont turn on still.
Galaxy S5 LTE
Reinstall ROM
Maybe the cause of the problem is that you downloaded an invalid root and it did something to the bluetooth. I highly recommend reflashing a stock rom. See if anything changes. Thank you :victory:
la2o said:
Maybe the cause of the problem is that you downloaded an invalid root and it did something to the bluetooth. I highly recommend reflashing a stock rom. See if anything changes. Thank you :victory:
Click to expand...
Click to collapse
This can't be the reason, becausw after I rooted it, BT worked fine.
Pozdrav
Croatia1
Yes.. Mine worked for a while as well and then it dsnt now....
I have the stock rom.
Galaxy S5 LTE
For the gentleman with the stock rom - you can try rebooting into service mode (holding home+volume up and then pressing power) and wipe your cache there - and then try to switch on bluetooth. If that does not work - warranty claim.
As for the rooted phone - you cannot be sure how stable the implementation of bluetooth drivers etc on that rom is. It could have worked at first and later - due to any number of reasons - could stop. I'd really suggest flashing a stock rom and checking - that way you'll be sure the hardware is ok. If not ok - warranty claim.
rnrnrn said:
For the gentleman with the stock rom - you can try rebooting into service mode (holding home+volume up and then pressing power) and wipe your cache there - and then try to switch on bluetooth. If that does not work - warranty claim.
As for the rooted phone - you cannot be sure how stable the implementation of bluetooth drivers etc on that rom is. It could have worked at first and later - due to any number of reasons - could stop. I'd really suggest flashing a stock rom and checking - that way you'll be sure the hardware is ok. If not ok - warranty claim.
Click to expand...
Click to collapse
First, thanks for the tip, sadly it didn't work.
Second, I'm already on Stock Samsung Rom, it's only rooted, I didn't even flashed a custom recovery.
Pozdrav
Croatia1
Hold on, I remember that I've done something around BusyBox with the app from Steven Stericson. Could Busybox brake my bluetooth?
croatia1 said:
Hold on, I remember that I've done something around BusyBox with the app from Steven Stericson. Could Busybox brake my bluetooth?
Click to expand...
Click to collapse
Yes, it could although that wouldn't be a normal result. But yes, it's possible. Depends on what you did with the Busybox configuration.
.
fffft said:
Yes, it could although that wouldn't be a normal result. But yes, it's possible. Depends on what you did with the Busybox configuration.
.
Click to expand...
Click to collapse
Just installed the 1.22.1 version of Busybox with the pro app that's all. Maybe it killed some symlinks.
Well if you practice safe mods.. you'll have made a backup before installing Busybox. So temporarily restore your backup and see if the issue resolves?
If you don't make backups, then you have a lot more work as you have to look for a pattern and /or guess at the cause.
.
I usually always make Nandroid Backups but in this case not. I'm afraid that Busybox will kill my S5 if I deinstall it. What if I flash a Stock Custom rom via CWM? Of course with a full wipe
I doubt Busybox is the cause, but I cannot rule it out. Only because it was a recent change does it move up the suspect list.
Still way too many variables in my mind. I'd probably start by installing a 100% stock firmware temporarily, just for troubleshooting. Confirm that bluetooth works i.e. not a stock issue or hardware failure. Then install your core apps one by one.. see if you can narrow down the conflict fairly rapidly.
But that is hardly the only way to go about it. As you like.. you have to start somewhere and either cull a lot of possibilities or wait for a pattern to emerge. Search the forum too, just in case it's some issue affecting a larger number of people - which might offer more clues.
Good luck.
.
fffft said:
I doubt Busybox is the cause, but I cannot rule it out. Only because it was a recent change does it move up the suspect list.
Still way too many variables in my mind. I'd probably start by installing a 100% stock firmware temporarily, just for troubleshooting. Confirm that bluetooth works i.e. not a stock issue or hardware failure. Then install your core apps one by one.. see if you can narrow down the conflict fairly rapidly.
But that is hardly the only way to go about it. As you like.. you have to start somewhere and either cull a lot of possibilities or wait for a pattern to emerge. Search the forum too, just in case it's some issue affecting a larger number of people - which might offer more clues.
Good luck.
.
Click to expand...
Click to collapse
Thanks mate, I'll post if I have success.
Pozdrav
Croatia1
Good news!
Before I flashed a new firmware with Odin I decided to flash a Custom Rom. Flashed new bootloader + modem and performed a "Wipe for new Rom" in Philz CWM, flashed the rom, set up my apps and settings and, BT works again. Thanks for your help
Pozdrav
Croatia1
Great to hear that so it was just a bit of software acting up - good to know
Please do change the title of your thread to solved
Alright, so following some prodding, searching, and questioning, I flashed MIUI V6 to my BLU Vivo Air alongside TWRP.
I will update this post with a detailed, step-by-step guide including my own personal mirrors for your convenience and those of you without 4PDA accounts, which is the Russian equivalent of XDA.
Upon booting, I noticed apps force closing without being launched. Namely Hangouts and Newsstand. I'm sure reinstalling them will resolve the issue rather quickly.
Stay tuned for updates.
Update 1:
TWRP had difficulty mounting data and cache for me, and was unable to format them. This led to applications force closing, window mishaps, and accounts glitching out. I just flashed Carliv recovery, and flashed MIUI with it. Flashing gapps at the moment, and will update you on my progress.
Update 2:
Currently attempting to format data (success), cache (success), and dalvik (success).
Update 3:
Rebooting into MIUI V6, checking if I've entered a bootloop.
5 seconds - Boot animation reached, "MIUI Pro."
165 seconds - Still booting.
180 seconds - Setup screen reached, MIUI V6 flashed successfully.
Update 4:
Google apps flashed successfully, no redraws or force closes this time. Had an issue with the keyboard not registering as being selected, Google voice typing appeared as the default. Pull down notification shader and "choose input method" to select MIUI Smart Keyboard. Signed into Google successfully. Will run preliminary tests on video playback, camera, and multitasking.
Guide:
If you mess up your phone, it is on you, and I am not to be held liable for your actions. This is your responsibility. A lack of planning on your part does not constitute an emergency on mine. With that out of the way, if you encounter troubles, I am more than happy to help you.
Step 1:
Root your phone using one of the links provided. Click HERE for method 1, or HERE for method 2. I personally used method 1 because it was the first I saw. They both get the job done.
Step 2:
Install THIS application (Settings -> Security -> Unknown Sources), and install a recovery. I installed Carliv recovery, and had no problems with it. You can also install TWRP, however, it had issues mounting data and cache. This left it unable to factory reset when I flashed MIUI, which subsequently led to problems. I do not recommend flashing TWRP - You have been warned. Carliv recovery says it can't "mount" cache, although when formatting it does so without a problem. I believe Carliv is supposed to be touch-based, although the touches weren't responding for me. The controls are as follows: Volume +/- for navigating, Power for selecting, and the Back key for, you guessed it, going back.
Step 3:
Install MIUI V6, located HERE, and then install Google Apps, located HERE. After installing, factory reset the device from recovery and reboot into the system. I posted my timestamps at the top of the post, so you can get an idea of how long your flash/boot process should take.
Step 4:
Basic setup. Be ready to fix your keyboard if you had the same issue I did, which isn't even necessarily a problem. Choose WLAN network and sign into your accounts, then you're good to go.
To root the ROM, I recommend finding "iRoot" for your computer. Then boot to recovery and install the SuperSU zip, as it's better than the root app which comes with the iRoot method.
Enjoy your ROM, and be sure to thank our Ruski comrades over at 4PDA!
Special thanks to @DvDwx. (research), @itsJohnuno (answers), and @Milly7 (testing).
All download links are being hosted by me, and I recommend creating mirrors of your own as safety precautions in the event that the files are removed or become unavailable.
Have a phenomenal day or night, possibly even both. If you have any questions, I'll do my best to answer them.
Nice Guide ;D
DvDwx. said:
Nice Guide ;D
Click to expand...
Click to collapse
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
DvDwx. said:
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
Click to expand...
Click to collapse
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Ilxaot said:
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Click to expand...
Click to collapse
i understand that ;D
on my WonderMedia WM8880 Tablet project i share the projects from other developers... but i asked they to have permission to share that, and leave on post the credits with their names... maybe if you talk with developer on 4PDA for permission to do it or ask him if it is possible he share he ROM Project here is will be perfect... anyway Good Guide to Flash this ROM :highfive:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
dimasp6 said:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
Click to expand...
Click to collapse
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
DvDwx. said:
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
Click to expand...
Click to collapse
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
dimasp6 said:
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
Click to expand...
Click to collapse
You can also try iRoot. Install SuperSU and try using it as the root granter for the recoveries.
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
ron580 said:
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
Click to expand...
Click to collapse
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Ilxaot said:
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Click to expand...
Click to collapse
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
ron580 said:
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
Click to expand...
Click to collapse
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Ilxaot said:
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
request
Ilxaot said:
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
JesusEMC said:
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
Click to expand...
Click to collapse
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
on Captcha you need count the numbers and ignore the russian Letters Like for exemple -> ##22###16## -> 22+16= 38
to can finish the registration... and no, you don't need use VPN or Proxy to create the account :highfive:
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
itsJohnuno said:
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
Click to expand...
Click to collapse
Our Buddy @SSJGohon found the kernel source code and already shared on some topic(i Already re-shared that on Cyanogen Mod to Mediatek SoC's Development thread... but anyone there say nothing about it... and already shared on 4PDA to maybe the MiUi developer can Bring something to All...). i already downloaded and already start my research about what can be maked with that and for sure have a possibility to we have a custom Kernel and maybe Custom ROM like PURE AOSP, AOSPA... but Cyanogen Mod is more difficult because we don't have a updated Repo Source from MediaTek to work like Driver Blobs to GPU, Bluetooth, Wifi Drivers... etc
My real problem is i don't have all skills to make a custom kernel to Mediatek SoC because a lot of things change from Qualcomm to Mediatek.. but if anyone here want to try development that just search the topics with @SSJGohon comments replays :highfive:
Ilxaot said:
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
Click to expand...
Click to collapse
I've already installed the ROM, it runs smoothly! You were right, I really like it! I had an issue trying to format /data, it took like 15 minutes, and did a hard reset (pressed power button for a few seconds) and tried to format again and it worked. Im a little bit worry cause I've had 2 radom reboots so far.. Any idea of what has happened to me?
Disclaimer
**** All flashing is done at your own risk! ****
**** While this recovery should not break your device, don't come back here blaming anyone if it does! ****
This is a TWRP 3.2.3 build based on Android 7.1.2 source kernel for the Galaxy Tab Active 2 (codename: gtactive2lte) - Exynos. The "tar" file should be installed using Odin (tested on Odin 3.12.3).
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.(DO NOT GET FOOLED.)
Installation process:
1. Flash Stock ROM.
2. Flash recovery using Odin (AP = recovery.tar).
3. Load recovery immediately after flashing.
4. Format data (Will erase /data partition).
5. Reboot to recovery.
6. ADB push SuperSU to internal storage / insert SD-Card with SuperSU.zip.
7. Flash SuperSU using TWRP install option.
8. Reboot to system (May bootloop several times. Wait untill system loads).
Bugs:
1. ADB sometimes doesn't work in MTP mode. Need to manually change to PTP in order to get adb usage.
2. Bad label in ADB shell + bad characters appearing while writing through AD. Works well out of recovery and on recovery's terminal.
Sources:
Device tree - Device tree
Kernel - Kernel
TWRP sources - platform_manifest_twrp_omni
SuperSU - SuperSU-2.82-SR5
Recovery download:
Recovery
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 08/19/2018 (DD/MM/YYYY)
Contributors:
Many thanks to TWRP's developers for the support on building this recovery.
Special thanks to CaptainThrowback, Bigbiff and Dees_Troy on TWRP-freenode and Ashyx on xda-developers.
Please post any bugs you encounter. I will try to fix any issues that come up.
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
slomo2 said:
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
Click to expand...
Click to collapse
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Shedaim said:
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Click to expand...
Click to collapse
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
slomo2 said:
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
Click to expand...
Click to collapse
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Shedaim said:
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Click to expand...
Click to collapse
This will be great, let me know if I can help, perhaps document.
slomo2 said:
This will be great, let me know if I can help, perhaps document.
Click to expand...
Click to collapse
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Shedaim said:
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Click to expand...
Click to collapse
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
Click to expand...
Click to collapse
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
7.1.1 is what The T397U should have already been on before you started. Mine is and I have not installed this recovery as of yet. Just wanted to let you know it's where it should be.
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
Click to expand...
Click to collapse
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Shedaim said:
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Click to expand...
Click to collapse
Sorry for delay. I've done the following tests all with the expected results. The only thing I noticed compared to previous installations of TWRP that I've performed ( some years ago ) is that the load time of recovery seems long at 1:15. Also a message about "RECOVERY NOT SEANDROID ENFORCING" which I suspect is normal. Tablet has been working without incident. Thanks again.
Blocking checks
- Correct screen/recovery size
- Working Touch, screen
- Backup to internal/microSD
- Restore from internal/microSD
- reboot to system
-ADB ( yes, if this means being able to access from ADB while in recovery )
Medium checks
- Screen goes off (and on )
- F2FS/EXT4 Support, exFAT/NTFS where supported
- all important partitions listed in mount/backup lists
===> define important ? - depends on the device, i guess
= Assume we can still boot a recovery (aboot/lk is still there for fastboot), can restore everything left ?
- backup/restore to/from external (USB-OTG) storage
- Correct date
Minor checks
- MTP export
- reboot to bootloader
- reboot to recovery
- poweroff
- battery level
- USB mass storage export
- set brightness
- vibrate
Security Policy Updates should not be applied to this system ?
Since this is stock Samsung OS that is rooted I'm guessing this system is still SELinux "enforcing" so does this mean that I can/should say yes to Security Enhancements automatic updates from Samsung ? Any explanation or link on this matter appreciated.
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
maddada said:
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
Click to expand...
Click to collapse
Hey, sorry for the very late answer.
I'm currently not working on Android and I've never tried on OREO, so my politically correct answer would be: "Right now there is no plan to work the same magic on OREO, but whoever wants, can try to use the device tree I created with a new official OREO kernel (didn't know they have one already)".
Anyway, keep checking the forum from time to time, I may have found the time to work on it
Links to the device tree and other tools used are in the main page of this thread.
Thank you,
Shedaim
I Pay 100$ for making my Galaxy Tab Active 2 booting when its charging
Hey guys,
i hope somebody can help me.
Im trying since 2 Weeks to make my Galaxy Tab Active 2 booting when its charging.
I try all the ways i found (fastboot, LPM change and Autoboot App) and nothing was successful.
So i hope to find with this way somebody who would help me to get the feature.
I need it because i installed the Active 2 on my Harley Davidson as my navigation.
And the problem is that i make a Novalauncher thats looking like the original Harley Davidson one and starts without a code.
So when i put the Tablet in the Mask i dont get a method to press to power button and when i make a method (hole trough the mask or something) then everybody can start up my tablet and use it.
So if somebody can help me with that i will pay them 100$ for helping!
you can contact me at [email protected].
thanks alot
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
sCOTTN916 said:
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
Click to expand...
Click to collapse
I used the methods and recovery here for my tablet which is a T397U...works flawlessly. The same should work for the wifi T390 you have aswell.
Flash process
I am new to the rooting process. This will be my first time. What is the actual flash process? How do I flash the rom on my tablet?
All the links are dead can anyone please post this recovery
i can Flash this twrp-3.2.3-0-gtactive2lte-7.1.2.tar, Odin says pass, but there is no TWRP. it boots into System. when i stop and boot to recovery, there is stll custom recovery from T395XXU5CSH2.
Any hints?