Related
Ok been running 4.04 for a sometime now. I got it as it first came out.
Some issues that u have noted outside of the bricking issue. **disclaimer I am running my own built version of this ROM deoxeded zipaligned bla bla bla plenty of tweaks etc and the ROM is faultless(not really it has its faults and I am about to list them) with exception of a few things that may or may not be kernel related. IT DID NOT flash the new .pit file. I have built the ROM as according to 4.03 builds and used Siyah kernel.
1. initial boot and dalvik cache build takes an extremely long time. Easily mistaken for bootloops and possibly another reason people prematurely ejected this ROM
2. Android is upgrading/updating splash does not exist. Further adds to the concern that phone has enternal bootloops...it doesn't it just doesn't warn you. It goes back to the gingerbread days where you wore a big question mark ? on your head "What is my device doing?"
3. Bluetooth enablement does not work. We go from 4.03 that had wifi issues much similar to fixed wifi and issues with bluetooth. Sux. Guess you cant win eh?
My guess is that this is specifically related to the kernel and framework. Ihave the framework decompiled now and I will be looking into maybe making some adjustments to allow for the bluetooth drivers in 4.03 kernels to interact with 4.04, rather than a whole new re-reslease of kernels just to combat this issue.
4. USB not detectable in Windows 7? Hmmm I am not sure what happened here? It worked flawlessly for 2 days and then all of a sudden not recognised? USB speeds were perfect when it did work, reflashing the ROM did not fix this? My guess is that this is also kernel<->framework related. Also to note here that within the siyah recovery you can mount USB no issues and transfere, so no eMMC corruptions before you freak out.
5. Vol down + power button for screen capture does not work? This again maybe because of the kernel used?
Can anyone give any reason for me not running the new pit and flashing stock kernel? Does the stock kernel require that there is a repartition or is this an assumption?
Additional notes: Further testing my eMMC with Gotbrickbug *MASSIVE thanks to chainfire for this support* personal thanks from me. Thanks Chainfire you're a legend! After testing it revealed oddly enough that my eMMC was inconclusive, so not that it helped me much, but I have flashed this firmware now several times and have not had any issues. Everything working smoothly and 100% except for the above mentioned.
I am tempted to flash the standard kernel now (again no repartition) and then do CFroot for the stock kernel image on this firmware to see if these issues are alleviated in 4.04?
Additional to this is that I have the 15 toggles mod by Jkay translated and compiled with exception of the last file on systemUI for 4.04. I would REALLY love to have this ROM running for everyone.
Any input suggestions warnings (besides the brick scare - I am not scared cause I doubt my phone will brick considering I have flashed it so many times now with the phone acting the same every single time)are welcomed. Please use your head when you respond and not your bricked phone, I would like intelligent answers and discussions. Preferrably not from n00bs or those that are only rehashing all that has spilled out across the petition thread already.
My understanding is that it is a repartition issue with bricking not a kernel or ROM issue its self. My understanding is that I can flash any kernel I like I can flash the stock one and I should be able to flash a rooted one after it to get back if I want?
Proceedure now:
Flash ROM
Flash kernel
Flash CFroot
Flash Modded recovery
Happy days?
I think most of those issues are due to Siyah, because I've tried the same builds running the stock kernel, and I didn't encounter most of them. Bluetooth fine, USB fine, etc. Nothing major. Still went back to LGP because the 4.0.4 implementations are quite ugly at this point.
Again flashed this ROM no problems.
I also attempted to run 4.04 czech republic version of this ROM to which it did not boot or run. Just to let those know that were considering doing this. I had 3 apks from that 4.04 build that refused to deodex? Also the sizes of all apks in this version of 4.04 (which does not come with a supplied .pit file) are vastly different to those in the Euro 4.04 supplied with .pit?
Yet to download and try 4.04 Chinese version? I figured someone else has probably already done this....the chinese are fast lil buggers. They don't much around! haha. If anyone has feel free (and please I would like you to contribute) to comment in this thread on your findings?
James
PS: Just about to flash standard kernel on unpartitioned GS2 if all goes well I will implement CF-Root. Cheers
donalgodon said:
I think most of those issues are due to Siyah, because I've tried the same builds running the stock kernel, and I didn't encounter most of them. Bluetooth fine, USB fine, etc. Nothing major. Still went back to LGP because the 4.0.4 implementations are quite ugly at this point.
Click to expand...
Click to collapse
Did you re-partition when you flashed stock kernel? I like the sounds of this. I have the 4.04 working nicely.....if i can achieve the above I will create a ROM and upload. Thank you for your valuable input
I may even test with the czec 4.04 kernel and see what happens there? Hmmm
Kernels are identicle sizes but not the same?
czec zimage: MD5 2A4AE1B758D934E2AD1791E318F94424
europe zimage: MD5 FCB26E67AE9E7F701793B6014E4AF7D2
see attached for additional size details? I am wondoering if czec might be better for no repartition was/is used in this 4.04 build?
James
WOW! I flashed standard kernel and I now have bluetooth enabled and I STILL kept root access. yeeeeeeeew! stoked!
Jarmezrocks said:
WOW! I flashed standard kernel and I now have bluetooth enabled and I STILL kept root access. yeeeeeeeew! stoked!
Click to expand...
Click to collapse
No fix for USB enablement? I have switched the customboot.sh for the MTP application. I however don't have MTP.apk in system? I may place this apk and then re-try to see if I might be able to get the thing to be recognised by my PC.
USB Mass storage is now working via the old method. I need to have the MTP client in system/app for this to work. No longer getting the USB device not recognised which is great.
Any kernel devs want to share with me how to embed the correct components in the kernel to allow for customboot.sh to work? I am certain then that USB mass storage will work when that script can be run and enabled at boot. I dare say that boot animations should work then also.
4.04 is starting to shape up nicely now
Disclaimer:
I am not to be held responsible for any actions that you take by following this guide that result in harm to your device. Sony devices are almost impossible to brick.
pre-requirements:
You're going to need the following things:
Flashtool
CWM Xperia SP Package
.266 4.3 kernel
.257 firmware
DooMLoRD easy rooting toolkit
CyanogenMod 10.2 Package & gapps
Step 1:
extract Flashtool, place the .257 firmware file in the firmwares folder and then run flashtool, flash the .257 firmware. This process could take 5-10 minutes.
To do this, click the electric bolt symbol in FlashTool, and select Flashmode, select .257 and then when the prompt says to connect your device in flashmode, power off your phone and holding volume down, plug your phone into the computer. This will then flash the files.
Turn your phone back on and enable USB debugging in android development settings.
Step 2:
Extract DooMLoRD's easy rooting toolkit and make sure that you have your phone connected and adb is enabled, while the phone is powered on run the script and this will then root your phone, do this by double clicking runme_win.bat, your phone will reboot in this process and it will be rooted.
Step 3:
Time to install a custom recovery, unpack the CWM Xperia SP package listed above. Make sure your phone is still turned on and in adb mode (USB debugging enabled) and then run install.bat from the package. You will need to accept a superuser request prompt on your phone meaning that you will need your phone screen on. Recovery is now installed.
Step 4:
Copy the CyanogenMod 10.2 package & google apps package to your phone, reboot into clockwork recovery by pressing the volume UP button once when you see the blue LED light up and feel a short vibration while your phone is booting. In CWM choose factory reset, and then install the two files we put on your phone using install zip from sd card option. Use volume rockers to navigate and power button to select options. Make sure you install CM zip then Google apps zip
Step 5:
After installing the ROM, power off your device in CWM and then connect your device in FlashMode again (hold vol down while plugging into computer) and then flash the .266 kernel only file. Reboot your phone.
Step 6:
Enjoy! You now have CyanogenMod and CWM installed on your phone, even with a locked bootloader. Recovery is now accessed with volume down.
I appreciate thanks greatly, and any issues I can help with and you can discuss them in this thread. I hope I have helped.
KeiranFTW
awesome
That. It's one good guide that anybody can follow. Just one question. Will this rom be as stable as normal cm, will it be full cm or just a stripped down version
Sent from my C5303 using Tapatalk
can this rom be flashed on ROOTED device running 4.3
zolaisugly said:
That. It's one good guide that anybody can follow. Just one question. Will this rom be as stable as normal cm, will it be full cm or just a stripped down version
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
I don't see why it can't be as stable as normal CM.. The only thing that isn't working at the moment is GPS, everything else to be honest it runs smoother than stock.
I'm going to work on getting AOKP to work if they have a compilable 4.3 branch. I'm also going to try and encourage ROM devs to add locked bootloader support and I shall show them how
pchetan2 said:
can this rom be flashed on ROOTED device running 4.3
Click to expand...
Click to collapse
Just follow the steps, if you have CWM installed on your XSP with 4.3 already all you need to do is flash the ROM in CWM nothing else..
I posted method for 4.1.2 because I'm presuming the user does not have root, and this is only rootable firmware.
Sent from my C5303 using Tapatalk
Awesome job to able get this rom on my lock xperia sp bro. And also am looking forward from you ,that you will bring other roms on my lock xperia sp which is the best phone ever.:good:
To have root on CM I need to flash SuFix as in existenz?
I have never used cm roms before...when the gps. Is fixed I will try rhis out,sadly I use gps alot due to work and driving into towns I don't know etc...
(Q) Due to limited space on sp can we use apps like link2sd and foldermount.
Or does the scripts not run.
Sent from my C5303 using Tapatalk
radeon6002 said:
To have root on CM I need to flash SuFix as in existenz?
Click to expand...
Click to collapse
Nope, su binary is included and root is already in the ROM.
CyanogenMod also features its own root permissions app (Settings -> Superuser) so you dont even need to install supersu or any equivalent, it works out the box.
zolaisugly said:
I have never used cm roms before...when the gps. Is fixed I will try rhis out,sadly I use gps alot due to work and driving into towns I don't know etc...
(Q) Due to limited space on sp can we use apps like link2sd and foldermount.
Or does the scripts not run.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Theoretically yeah, these scripts should run. I will look into it soon
Sent from my C5303 using Tapatalk
I had just posted a thank-you in another thread for the same - outstanding work. A big thank-you from one who prefer not to touch the BL
And thanks for the lucid instructions. Will download the stuff when I am off work.:good:
yeah i did it succesfully ..need to wipe data and factory reset .then install the rom and gapps....... thank you a lot
Note: the link to the 257 firmware is dead.
[not applicable to those who already rooted their phones ]
EDIT:
Just installed the rom. Also 'upgrage' kernel to 266 (had preferred 254 as it was faster, but with this new rom...)
Question:
a. could one just live with 254 kernel instead of flashing 266 at the end?
b. Now that I have flashed 266, could I re-flash to downgrade (just the kernel) to 254 later on?
Fun time - rom is working on my device.
Thanks a million!
headache59 said:
Note: the link to the 257 firmware is dead.
[not applicable to those who already rooted their phones ]
EDIT:
Just installed the rom. Also 'upgrage' kernel to 266 (had preferred 254 as it was faster, but with this new rom...)
Question:
a. could one just live with 254 kernel instead of flashing 266 at the end?
b. Now that I have flashed 266, could I re-flash to downgrade (just the kernel) to 254 later on?
Fun time - rom is working on my device.
Thanks a million!
Click to expand...
Click to collapse
If you flashed the .254 kernel your Phone won't boot...you just get a bootloop. You need. 266
don't downgrade kernel without downgrading rom as well.
Sent from my C5303 using Tapatalk
Great work by @bagyusz and @KeiranFTW for the initial spark idea. I thot all was lost when i got vendorlocked sp.
I would love to have MIUI (4.3 based) using cm10.2 as base. @OP, if you have any experience of using MIUI patchrom, please help me.
The steps i have already done are:
1. make workspace
2. Make firstpatch
3. Make fullota
now i have to diff and patch the smalis, but not sure exactly how many smalis need to be patched for boot, and how do i know when to stop.
Having LB means to test my port, i have to go thru all the hassle of flash ftf, rooting and then check for every failed attempt.
THanks in advance
Yasir
I know there is an MIUI thread already there, but the OP states its for UBL only, plus he uses 4.2.2 as base. so thot this might be the right place.
---------- Post added at 09:01 PM ---------- Previous post was at 08:56 PM ----------
btw, @ keiran...
I once thot about this... can u confirm im true....
what if we dont format /system partition in updater script of cm.zip... every time, we flash, system wont be formatted so recovery will stay, and if there was something wrong with cm.zip, we can try to fix and flash the new cm.zip and it will overwrite the previous versions of every file hence we know it boots or not.
If it boots, we can do a clean install.
Correct me if im wrong here. Thanks
neXus PRIME said:
Great work by @bagyusz and @KeiranFTW for the initial spark idea. I thot all was lost when i got vendorlocked sp.
I would love to have MIUI (4.3 based) using cm10.2 as base. @OP, if you have any experience of using MIUI patchrom, please help me.
The steps i have already done are:
1. make workspace
2. Make firstpatch
3. Make fullota
now i have to diff and patch the smalis, but not sure exactly how many smalis need to be patched for boot, and how do i know when to stop.
Having LB means to test my port, i have to go thru all the hassle of flash ftf, rooting and then check for every failed attempt.
THanks in advance
Yasir
I know there is an MIUI thread already there, but the OP states its for UBL only, plus he uses 4.2.2 as base. so thot this might be the right place.
---------- Post added at 09:01 PM ---------- Previous post was at 08:56 PM ----------
btw, @ keiran...
I once thot about this... can u confirm im true....
what if we dont format /system partition in updater script of cm.zip... every time, we flash, system wont be formatted so recovery will stay, and if there was something wrong with cm.zip, we can try to fix and flash the new cm.zip and it will overwrite the previous versions of every file hence we know it boots or not.
If it boots, we can do a clean install.
Correct me if im wrong here. Thanks
Click to expand...
Click to collapse
No need to, I am creating build repository that will be able to build CyanogenMod using the cyanogenmod build system, basically I just add the files that are needed for the hack into the repository and then I will be able to build CM and flash it straight off - I'll do this so when the ROM is built it includes recovery and hijack in the /system partition and so when you flash it, it will still be there.
As soon as I get access to a build server I will build AOKP for locked bootloader (jb-mr2)
All work except my wifi. It's grayed out. I got data though...
Just to note: that I was on 4.1.2 (254) rooted when I flashed this rom and GAPPS. After which I flashed the 266 kernel.
Edit:
I did a factory reset under recovery (CWM) and now my wifi has turned on (blue). Unfortunately I am away from my wifi (home) point, so can't test it out fully.
Back to reinstalling of data...
babicsbalu said:
Well done, nice job! :highfive:
Click to expand...
Click to collapse
Don't quote the whole post.
Just preparing for this, I downloaded the kernel from the main thread not the one linked by KeiranFTW do we only need to flash the kernel.sin or do we need other files like fotakernel.sin like when flashing existenz?
Oblox said:
Just preparing for this, I downloaded the kernel from the main thread not the one linked by KeiranFTW do we only need to flash the kernel.sin or do we need other files like fotakernel.sin like when flashing existenz?
Click to expand...
Click to collapse
The link on both threads only feature the .266 kernel - for use after installing cyanogenmod.
The .257 is the full firmware for rooting purposes.
I have already rooted my SP previously therefore, I merely installed CM and flashed the .266 kernel at the end of the process (actually I used my country's version, unchecked all but kernel only) - worked for me.
headache59 said:
The link on both threads only feature the .266 kernel.
I flashed the kernel at the end of the process (actually I used my country's version, unchecked all but kernel only) - and it worked for me.
Click to expand...
Click to collapse
Ahh ok, does the countries kernel make any difference whatsoever?
I never did any software changes to my phone, because of this whole warranty talking, but today my warranty is over, so this finally the time for some upgrade . Currently I have B138 ROM and I want something with android 4.0+ for google hangouts, and much more apps that are based on API level 14. So my first question: is CM11 stable enough for every day use? I don't have second phone, and I have to be on line most of the time.
Assuming that it is, I did prepare a little todo list:
Install stock rom through dload (Second question: will B518 be good enough, becouse if anything goes wrong I will still have pink screen; Third question: Should I wipe data and/or cache? It would be wiped anyway, or not?)
Root the phone using [U8800] [How To] Root, Install ClockworkMod + Remove Bundled Apps from Official 2.3.5 (link to SuperOneClick inside this thread is dead, but I found it elsewhere)
I'm rooted so I can backup my IMEI thanks to [Helpful][Tutorial][Caution] IMEI backup & Flash your IMEI
I still have stock recovery, [RECOVERY] ClockworkMod Recovery [v6.0.4.6]
If answer for second question will be “You should use latest official, B528”, I will have to get my PINK screen back (in this tut Blefish recommended 5.5.0.4 recovery, 6.0.4.6 installs on top of it, so I will rather stay with 5.5.0.4)
If CM11 is stable enough partitioning is required: [PARTITION] BlePart [v2.x].
[ROM][07.09.2014] Unofficial Cyanogenmod 11.0 [4.4.4]. This ROM is rooted out-of-the-box, isn't it?
[GAPPS][4.4.x] OFFICIAL Up-to-Date PA-GOOGLE APPS (All ROM's). And here it goes a little messy. A lot of different packages, replacement of stock apps, Titanium Backup required (?), I don't know how to install, update, remove them...
Anyway, see guys how much have you done for anyone who has u8800, it's everything right here and only thanks to you I was able to make above list .
Is everything in right order? Is there anything important that I didn't found and read before posting this?
EDIT: If anyone will need this in the future:
Second step didn't worked, SuperOneClick freezed in "Step 7", I found [URL="http://forum.xda-developers.com/showthread.php?p=23565074]this[/URL] tutorial and it rooted my phone (I had to use included adb drivers).
CWM 5.5.0.4 wasn't able to install CM11, with error "E:Error in /sdcard/cm-11-... .zip (Status 7) Installation aborted", with CWM 6.0.4.6 I had no problems.
/system partition from BlePart allows only for micro PA-gapps
It's good decision to Flash Custom ROMs as there is no good original FW for this good phone. It's a "Do It Yourself" phone! :fingers-crossed:
But there are more than one CM11 versions like there are more than one CM10 versions, etc. You should better read their forum pages and then decive yourself which one to use...
ROMs which need re-partitioning is one step further than classic Custom ROMs. For this case you should better try firstly some ROMs which don't need partition. For e.g. Aurora will be a perfect option for that.
You can get Aurora v5 Update 20 and 21 (which I have used very long time) from its topic:
http://forum.xda-developers.com/showthread.php?t=1492957
Then you can do partitioning. I personnally suggest Forumber's partition file.
After partitioning you can try Aurora SP+ Update 2 which I am currently using. You can get from here:
http://forum.xda-developers.com/showthread.php?t=2295318
Next step is Blefish currently developping ROM. After trying Aurora SP+ you can go one step further and flash Blefish. You can even participate to the topic with the issues you may face in this still developping ROM. Get it here:
http://forum.xda-developers.com/showthread.php?p=49579659
Thanks for reply, I'm using CM two days from now and I'm amazed what this phone is capable of To be honest I didn't choose Aurora ROM because of 800 pages topic to read . I wasn't shure from where start reading, so I read the whole topic about 4.4.4. And I didn't even thought about leaving stock partition schema. In 2.2 I had problems with lack of space for applications.
But you advise in just one answer to try 3 different ROMs. And I belive many people do so - they change ROMs weekly, monthly to find the best one for their needs. My question is: how to restore everything, everytime when new soft is flashed? Google can restore phonebook. Titanium Backup SMS, and apps. But app data? Saved games? Saved progress in books? And we talking here about jumping between two kernels (.32 and .35), and many API levels. How do you do it?
14 November 2014
There are several great lollipop builds out there currently with a lot of work being done to give us all a great product. So far multirom is working perfectly in Primary slot as well as secondary slots in multirom with @scrosler AOSP builds 5-7, Build 7 here as well as @scrosler Factory Stock Rooted ROM LRX21P which can be found here
If your favorite dev is making a Lollipop build for the Nexus 7 and you have successfully used it with multirom, please let us know so we can tag it and place a link for future users to this thread.
06 November 2014 (ORIGINAL POST)
Ever since I mentioned this in an email, I have received a few requests on how I got @scrosler Pure AOSP 5.0 Build to work with MultiROM on my Nexus 7 flo.
First off, I have only done this with the build by @scrosler which can be found HERE, but I would guess that it can work with similar builds.
Secondly, this worked perfectly on my device. If you mess up your device, I am not responsible.
Thirdly, and most importantly thank you to:
@scrosler for the lollipop build and all the extras
@Chainfire for SuperSU
@sykopompos for the permissive boot image
@flar2 for the ElementalX Kernel
@Tasssadar for MultiROM
if I forgot to mention someone, please holler at me
Okay, on to the easy stuff...
This has been tested and is successful on Nexus 7 flo (2013). For information on Deb procedures, please refer to this post by @drewski_1 but at the request of @scrosler, please bring all multirom questions back to this thread. Also for Nexus 7 deb, @darkobas has given us a modified boot image to use which can be found here
This ROM (this particular build I've been working with) cannot go into a secondary slot of MultiROM, I have tried everything. If you found a way, please share it.
1. go HERE and read the OP, download necessary files, (latest build, latest gapps, busybox flashable, etc), update bootloader if needed, and goto step 2.
2. go HERE to get ElementalX Kernel for Lollipop
3. go HERE to get a very permissive boot image that works perfectly with this setup.
4. go HERE to get the latest SuperSU
After you have everything in order, reboot into recovery...
1. Move your primary ROM into a secondary slot in TWRP recovery.
2. Go back out to the main TWRP page (outside of Advanced/MultiROM)
3. Install Scotts Pure AOSP build 5.0
4. Install Recovery Saver
5. Reboot Recovery (just to make sure your recovery is still intact)
6. Install GAPPs
7. Install Permissive boot image
8. Install SuperSU
9. Install ElementalX Kernel
10. Reboot and Enjoy
When you get into your ROM, check to verify that your SuperSU is functioning properly and set your ROM up to your likings. :good:
appreciated clarification
OP said:
I've gotten a few requests about multirom with this build since I posted something earlier. If you need to know how to do it (you should already if you're using multiROM), you can check it out HERE.
I didn't want to post the info in here and muddy up the dev thread.
http://forum.xda-developers.com/showpost.php?p=56558107&postcount=802
Click to expand...
Click to collapse
I know but tend to forget details over time - THANKS. I like to verify procedures before committing anyway - saves me from bricks soft or hard. With the file structure changes, etc I like to know what I'm getting into and how best to do it safely.
I'm in the process of moving roms and should have this latest L in slot #1 before dusk, heh.
Heads up, the modified boot image does not stick after booting into secondary ROM (IE KitKat or other earlier based ROM), so if this happens just reflash modified boot image. You will be good to go and back to root. :good:
Also, @darkobas has created updated boot images for both FLO and DEB. Would be great if OP could be modified as such. The new images can be found in @scrosler 's thread.
Make sure to have MultiROM zip and recovery installed when trying this method, as the MultiROM code must be injected for it to work well.
hhairplane said:
Heads up, the modified boot image does not stick after booting into secondary ROM (IE KitKat or other earlier based ROM), so if this happens just reflash modified boot image. You will be good to go and back to root. :good:
Also, @darkobas has created updated boot images for both FLO and DEB. Would be great if OP could be modified as such. The new images can be found in @scrosler 's thread.
Make sure to have MultiROM zip and recovery installed when trying this method, as the MultiROM code must be injected for it to work well.
Click to expand...
Click to collapse
I had no issues with the modified boot image sticking after booting into either of my secondary Roms.
I will look at the modified boot images in a few. I'm reading through scrosler's thread now.
Megaflop666 said:
I had no issues with the modified boot image sticking after booting into either of my secondary Roms.
I will look at the modified boot images in a few. I'm reading through scrosler's thread now.
Click to expand...
Click to collapse
It might just be with Deb, then...
hhairplane said:
It might just be with Deb, then...
Click to expand...
Click to collapse
Would be my guess. I am currently reading through the section in scrosler's thread that you mentioned. Is the new boot image you mentioned for deb only?
Megaflop666 said:
Would be my guess. I am currently reading through the section in scrosler's thread that you mentioned. Is the new boot image you mentioned for deb only?
Click to expand...
Click to collapse
Yes, but I think there is a different boot image in scrosler's thread (not for Lollipop preview, but for AOSP scrosler build). It is attached in OP and made by darkobas. Not sure what is different than older boot image.
Also, my secondary are KitKat and earlier ROM's, not Lollipop-should be a different boot image. Not sure if that's the same for you? Perhaps, flashing a KitKat boot may solve the problem, since it seems that MultiROM has to mod Lollipop's for KitKat to work?
hhairplane said:
Yes, but I think there is a different boot image in scrosler's thread (not for Lollipop preview, but for AOSP scrosler build). It is attached in OP and made by darkobas. Not sure what is different than older boot image.
Also, my secondary are KitKat and earlier ROM's, not Lollipop-should be a different boot image. Not sure if that's the same for you? Perhaps, flashing a KitKat boot may solve the problem, since it seems that MultiROM has to mod Lollipop's for KitKat to work?
Click to expand...
Click to collapse
OP has been updated, I think I found all the pertinent info you mentioned regarding making deb part of this thread. If I missed something, please let me know. Thanks
Megaflop666 said:
OP has been updated, I think I found all the pertinent info you mentioned regarding making deb part of this thread. If I missed something, please let me know. Thanks
Click to expand...
Click to collapse
This one is the better Deb Modified Boot.img http://forum.xda-developers.com/showpost.php?p=56564714&postcount=856 Sorry, I should have more clearly laid it out myself.
hhairplane said:
This one is the better Deb Modified Boot.img http://forum.xda-developers.com/showpost.php?p=56564714&postcount=856 Sorry, I should have more clearly laid it out myself.
Click to expand...
Click to collapse
Its all good. There's been conversation scattered everywhere, that's one of the biggest reasons I wanted to start this thread.
Edit: Link has been updated to the correct post.
I followed the OP instructions very closely (twice) and can get the primary L rom installed, rooted and running smooth - very smooth, in fact. Nice rom scrosler! But the rest of my multirom roms won't load even the boot ani - I get only to the Google screen and loop there on any rom - I have a jellybean, a couple of kitkats and one of the dev releases of L and they all do the same. I've not yet tried to install a secondary rom but will.
Anyone with a suggestion? I have the new primary backed up and have some nandroids of a couple of the secondarys. I'm not that worried about losing them and have considered starting from scratch if nec.. tia!
dadeo1111 said:
I followed the OP instructions very closely (twice) and can get the primary L rom installed, rooted and running smooth - very smooth, in fact. Nice rom scrosler! But the rest of my multirom roms won't load even the boot ani - I get only to the Google screen and loop there on any rom - I have a jellybean, a couple of kitkats and one of the dev releases of L and they all do the same. I've not yet tried to install a secondary rom but will.
Anyone with a suggestion? I have the new primary backed up and have some nandroids of a couple of the secondarys. I'm not that worried about losing them and have considered starting from scratch if nec.. tia!
Click to expand...
Click to collapse
Try going into twrp into one of the secondary ROMs and fixing it's boot? Something must've gotten missed in the setup or something happened because this issue is new.
Megaflop666 said:
Try going into twrp into one of the secondary ROMs and fixing it's boot sector?
Click to expand...
Click to collapse
I should use the remove/add boot.img function? I've never done this but will look into how. If you have a link to some specifics it would be much appreciated.
Thanks! :good:
edit to add:
I am able to install/add roms, btw. I successfully re-added a jellybean rom from nandroid backup just fine. I'll probably throw them out except one anyway. I'm not sure what happened or when but I followed your steps verbatim. thanks again.
dadeo1111 said:
I should use the remove/add boot.img function? I've never done this but will look into how. If you have a link to some specifics it would be much appreciated.
Thanks! :good:
Click to expand...
Click to collapse
All the multiform specifics can be found in that thread here.
I would try restoring your backup first and see if that fixes the secondary ROMs. Especially since you don't have much time in the lollipop ROM yet. If you restore and it works, let me know.
@scrosler has build 4 up, please see his thread which can easily be found in the OP, second paragraph.
OP will be updated shortly if necessary.
Okay, I've gone through this a few times now. @scrosler work is perfect unless we want to use it on multirom. Continue the same steps listed in the OP or you will lose root, as well as the ability to boot multiple Roms.
Build 6 is out from @scrosler. Follow the same installation process listed in the OP. Only add on would be that scrosler added a flashable busy box zip on his threads OP that you can flash in twrp around the same time you flash SuperSU. :thumbup:
Megaflop666 said:
Build 5 is out from @scrosler. Follow the same installation process listed in the OP. Only add on would be that scrosler added a flashable busy box zip on his threads OP that you can flash in twrp around the same time you flash SuperSU. :thumbup:
Click to expand...
Click to collapse
I have successfully installed @scrosler's latest (build 6) as a secondary rom and in the usual fashion - Flash ROM, Flash GAPPS. I then booted into the new install and allowed Google to update me (successfully). Everything worked but root apps, of course. I then rebooted to TWRP, flashed the beta superuser zip - rebooted and checked and have root. All per usual and as expected.
Titanium bup didn't work after accepting root permissions but it was from the play store so this is also per usual. I'll try the one I got from twitter and expect that to work too - as usual. If not I'll post so here.
This is going to be my daily driver now. :good:
I'll add a custom kernel later. ElementalX 3.x has been solid for me on all lollypop roms so probably that one.
dadeo1111 said:
I have successfully installed @scrosler's latest (build 6) as a secondary rom and in the usual fashion - Flash ROM, Flash GAPPS. I then booted into the new install and allowed Google to update me (successfully). Everything worked but root apps, of course. I then rebooted to TWRP, flashed the beta superuser zip - rebooted and checked and have root. All per usual and as expected.
Titanium bup didn't work after accepting root permissions but it was from the play store so this is also per usual. I'll try the one I got from twitter and expect that to work - as usual. If not I'll post so here.
This is going to be my daily driver now. :good: I'll add a custom kernel later. ElementalX 3.x has been solid for me on all lollypop roms so probably that one.
Click to expand...
Click to collapse
Awesome. I was going to try it with the latest build later when I had some time but you saved me the work. :thumbup:
Besides checking tibu, also check es file explorer. I have both working on this build in the primary slot but I know a lot of people are struggling with es.
Megaflop666 said:
Awesome. I was going to try it with the latest build later when I had some time but you saved me the work. :thumbup:
Besides checking tibu, also check es file explorer. I have both working on this build in the primary slot but I know a lot of people are struggling with es.
Click to expand...
Click to collapse
ES seems fine - even sees my lan. Also sees and navigates sd card but am unable to do root tasks in system folder (rename, copy, delete). When I do a root action it requests root and I accept then the task fails.
dadeo1111 said:
ES seems fine - even sees my lan. Also sees and navigates sd card but am unable to do root tasks in system folder (rename, copy, delete). When I do a root action it requests root and I accept then the task fails.
Click to expand...
Click to collapse
Are you using the permissive boot image from the OP and elementalX kernel 3.01? Just curious why I have full function with ES and other people don't.
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?