Just letting you know, ill start porting TWRP tonight. I need to sync the entire cm9 repo first so it will take a while.
Dunno IF and when it will be finished. Il integegrate it with my kernel. But I will also release it to the public so they can include it in their own kernels. At least thats the plan.
Try putting it in jb kernel. It may fix recovery glitch
Sent from my Ray with the FORCE
MrTapa said:
Try putting it in jb kernel. It may fix recovery glitch
Sent from my Ray with the FORCE
Click to expand...
Click to collapse
what's the significant difference between this one and CWM? what about the update script?
thetrisatria said:
what's the significant difference between this one and CWM? what about the update script?
Click to expand...
Click to collapse
u can read about here:
some info:http://www.xda-developers.com/androi...pdated-to-2-2/
main thread: http://forum.xda-developers.com/show....php?t=1416118
teamwin site: http://www.teamw.in/project/twrp2
@thomas1991_12 - will support u in near future
Good luck man! Hope it works...I tried with ChampionSwimmer's JB AOKP build, but I stopped because the TWRP Tut says it won't work with a userdebug build and that is the only version that is currently compiling for the ray.
mericon has it working on xperia S....http://forum.xda-developers.com/showthread.php?t=1858283
justmpm said:
mericon has it working on xperia S....http://forum.xda-developers.com/showthread.php?t=1858283
Click to expand...
Click to collapse
Hmm didnt know that. thanks. CM9 is syncing now, takes forever.
stuff is not progressing too well. Ive compiled twrp with cm9, integrated in flykernel ramdisk tried to boot in recovery. Got a purple led behind home then black scree n for 10 seconds then phone shuts down..
thomas1991_12 said:
stuff is not progressing too well. Ive compiled twrp with cm9, integrated in flykernel ramdisk tried to boot in recovery. Got a purple led behind home then black scree n for 10 seconds then phone shuts down..
Click to expand...
Click to collapse
I tried to compile with aokp and I am facing a mountain of compile errors.....looks like it cant find somethings, so maybe an easy fix....will try tommorrow after some sleep
justmpm said:
I tried to compile with aokp and I am facing a mountain of compile errors.....looks like it cant find somethings, so maybe an easy fix....will try tommorrow after some sleep
Click to expand...
Click to collapse
I only had one compile error. with the images it trys to pull frorm res. starting with firmware_error png or something. But that can easily be resolved removing the #PRODUCT_COPY_FILES from recovery resources in msm7x30.mk (msm7x30-common folder).
thomas1991_12 said:
I only had one compile error. with the images it trys to pull frorm res. starting with firmware_error png or something. But that can easily be resolved removing the #PRODUCT_COPY_FILES from recovery resources in msm7x30.mk (msm7x30-common folder).
Click to expand...
Click to collapse
Thanks, I will try again tonight...I had a lot of those png errors...mine started off with two files that couldn't be found in bin (or maybe sbin), I don't really remember...but will be easy to track down. Did you edit init.rc? I hunted around for it last night but since there wasn't a call for it Boardconfig.mk I didn't worry about it too much then...but now I am wondering if it still needs to be edited in order for the dynamic linking to work.
justmpm said:
Thanks, I will try again tonight...I had a lot of those png errors...mine started off with two files that couldn't be found in bin (or maybe sbin), I don't really remember...but will be easy to track down. Did you edit init.rc? I hunted around for it last night but since there wasn't a call for it Boardconfig.mk I didn't worry about it too much then...but now I am wondering if it still needs to be edited in order for the dynamic linking to work.
Click to expand...
Click to collapse
Im struggling with init.rc too.
Positive point is, i got it booting using all the files from the twrp ramdisk in stead of my own (so init.rc from twrp ramdisk too). But it had major graphical problems, unusable. So im trying a bit more right now..
Graphical problems fixed. Its not responding to any touch now..
I cant get touch to work. I just generates random touches. I think twrp has some issues recognizing the touch screen and is using something else as touch, dont know what.. Maybe ALS. Anyway here is the default ramdisk, latest TWRP compiled. So other devs can try to integrate it in their ramdisks. Ask you favorite kernel developer to try to integrate it.
Please report back if anyone got it working, i can compile a version without logging then.
Also a experimental boot.img with flykernel, for you who want to see what i mean. it DOESNT work. Only boots to twrp recovery. Testing purposes
You can press and hold the middle log button to see whats going on.
thomas1991_12 said:
I cant get touch to work. I just generates random touches. I think twrp has some issues recognizing the touch screen and is using something else as touch, dont know what.. Maybe ALS. Anyway here is the default ramdisk, latest TWRP compiled. So other devs can try to integrate it in their ramdisks. Ask you favorite kernel developer to try to integrate it.
Please report back if anyone got it working, i can compile a version without logging then.
Also a experimental boot.img with flykernel, for you who want to see what i mean. it DOESNT work. Only boots to twrp recovery. Testing purposes
You can press and hold the middle log button to see whats going on.
Click to expand...
Click to collapse
I was able to compile it tonight from CM10. I probably won't pack it into a kernel tonight....what did you decide to do about init.rc. I checked the ramdisk and it doesn't contain the code for dynamic linking....drats...
justmpm said:
I was able to compile it tonight from CM10. I probably won't pack it into a kernel tonight....what did you decide to do about init.rc. I checked the ramdisk and it doesn't contain the code for dynamic linking....drats...
Click to expand...
Click to collapse
I tried it with different combinations. Original init.rc TWRP wouldnt even boot. init.rc CM9 created with TWRP upon compilation booted, and i tried to combine my own with the one compiled by cm9, that booted too. But as I said, touch isnt working properly...
Btw you will need these build flags to avoid graphics problem:
DEVICE_RESOLUTION := 480x854
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
thomas1991_12 said:
I tried it with different combinations. Original init.rc TWRP wouldnt even boot. init.rc CM9 created with TWRP upon compilation booted, and i tried to combine my own with the one compiled by cm9, that booted too. But as I said, touch isnt working properly...
Btw you will need these build flags to avoid graphics problem:
DEVICE_RESOLUTION := 480x854
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
Click to expand...
Click to collapse
Crap....I had two out of three....I left the last one out because the CM10 thread in the Xperia S section was saying that this pixel format
wasn't properly supported so it defaults to RGB565..... Anyway...not that big of a deal...as long as it compiles...
Thanks a lot!
justmpm said:
Crap....I had two out of three....I left the last one out because the CM10 thread in the Xperia S section was saying that this pixel format
wasn't properly supported so it defaults to RGB565..... Anyway...not that big of a deal...as long as it compiles...
Thanks a lot!
Click to expand...
Click to collapse
I didnt use a pixel format flag myself neither in the beginning but colors and graphics were incorrect after adding those two it showed up the way it should.. Let me know what problems you have after compiling.
thomas1991_12 said:
I didnt use a pixel format flag myself neither in the beginning but colors and graphics were incorrect after adding those two it showed up the way it should.. Let me know what problems you have after compiling.
Click to expand...
Click to collapse
I have gotten to the point where I can get a frozen black screen....I will play around with it some more tonight....so far I have learned a lot which
makes it worth the "failed" effort....thanks for your help!
justmpm said:
I have gotten to the point where I can get a frozen black screen....I will play around with it some more tonight....so far I have learned a lot which
makes it worth the "failed" effort....thanks for your help!
Click to expand...
Click to collapse
Yeah been there too. Thats a init.rc problem most likely. Try to use the entire ramdisk of TWRP with all it files, it should then boot in twrp.
thomas1991_12 said:
I cant get touch to work. I just generates random touches. I think twrp has some issues recognizing the touch screen and is using something else as touch, dont know what.. Maybe ALS. Anyway here is the default ramdisk, latest TWRP compiled. So other devs can try to integrate it in their ramdisks. Ask you favorite kernel developer to try to integrate it.
Please report back if anyone got it working, i can compile a version without logging then.
Also a experimental boot.img with flykernel, for you who want to see what i mean. it DOESNT work. Only boots to twrp recovery. Testing purposes
You can press and hold the middle log button to see whats going on.
Click to expand...
Click to collapse
@thomas1991_12: I think that the problem with the screen might be the screen calibration....over the week end I tried a new version of the aroma installer and it was a complete mess. The new version isn't supposed to need screen calibration, but it still does on the Ray....anyway, it turns out that amarullz got the code for the "universal" calibration from TWRP (https://github.com/amarullz/AROMA-Installer/commit/ea100b05c16ac0deaba42a4cc744d5a6b04ce9c8).....so maybe your wonky twrp recovery can be fixed by calibrating the screen. Iriijo also reported some touchscreen issues with twrp and I am not sure how far he took it.
Wechy77 found a fix for the problem with aroma: http://forum.xda-developers.com/showpost.php?p=33269911&postcount=1128
If you want to see if the screen issues are the same you can get aroma installer from here: http://forum.xda-developers.com/showpost.php?p=21755937&postcount=2
Related
This is a sort of continuation of the work in this thread: http://forum.xda-developers.com/showthread.php?t=1798750
I only started this because I could not get the files located in that thread to work on Epinters CM10 build. With help from quetzalcoatl2435, we have a successful .zip with the modified files to work in this ROM.
The "Atrix-softbutton...cm10.zip" will activate the vitural soft keys and turn off the lights for the capacitive keys. With this file the capacitive keys still work.
"DisableAllCapacitiveKeys.zip" does just that, disables the capacitive keys all together.
"AtrixSoftKeys...zip" combines the two together into one file so the virtual soft keys are enabled and the capacitive keys are disabled completely.
The last file will return you to stock without soft keys and working capacitive keys!
Flash at your own risk, I have only tested this on Epinters ROM (personally), it may work for others.
Copy the file to your sdcard, Nandroid, flash, and enjoy your new mod!
Tested and working on Epinters 8/22 build.
Happy flashing!
try changing the false to true in this line of bools:
<bool name="config_forceDisableHardwareKeyboard">false</bool>
i did my own .zip with the tutorial posted on the thread you linked when leo stopped updating it
but my atrix's hardbuttons are dead, so i don't have how to test if worked or not
PS: i know, my english sucks
lstat said:
First I would like to say that I know this has been posted in the Dev. Section but I have reasoning for posting it again, secondly I have my fingers crossed this section will work, I see the buttons as a Dev. mod AND themeing. Mods, feel free to move if I am in the wrong! :good:
I am currently running Epinters CM10 build and love it, I really wanted the virtual soft keys, though. Losing a small amount of screen space wasn't to big a deal, its not really THAT much real-estate. I pulled the idea for doing this from this thread: http://forum.xda-developers.com/showthread.php?t=1798750 . All credit goes to the OP and any others mentioned before, I only created this for myself.
I was ecstatic when I found that thread, but every file the OP posted sent my phone into a boot loop and I was determined to make it work. Through a ton of searching I finally figured out what to do and what files needed to be edited. I have successfully gotten the virtual soft keys on CM10 and they work great! I know that I am not the only person who has had issues with adding these so I thought I would post it here for others relief!
Unfortunately this .zip file only turns on the soft keys and shuts off the capacitive lights for the hardware buttons, the capacitive buttons still work but I am going to look into that once I find the correct files that need to be edited. I have only tested this on Epinters CM10 build from 8/15. I cannot promise it will work on any other ROM although I would assume JB ROMS should be alright with this.
Remember to make a Nandroid, if this doesnt work for you, you need to have a backup so you arent reflashing your entire phone!
Simply add this to your SD card, flash, and reboot!
If this messes your device up in anyway I take no responsibility, but feel free to let me know what files I need to edit for the capacitive buttons functions!
Otherwise, cheers!
Click to expand...
Click to collapse
Errrm... I made a keymap that killed all 4 capacitive keys. It's on the first post of the thread you referred to...
Edit - Here's the link: https://dl.dropbox.com/u/19567156/DisableAllCapacitiveKeys.zip. It's flashable.
I will check that out, thanks for the heads up.
Currently I am trying to create an update.zip that contains the /usr/keylayout files that need replaced. I have all the needed files but the file always 1) aborts installation, 2) fails with (status 0)
At the moment I am trying to figure this out but I am going to checkout that line.
quetzalcoatl2435 said:
Errrm... I made a keymap that killed all 4 capacitive keys. It's on the first post of the thread you referred to...
Click to expand...
Click to collapse
I tried flashing it and it sent my Atrix into a boot loop, also. If it didnt then I wouldnt be trying to build one on my own....
lstat said:
I tried flashing it and it sent my Atrix into a boot loop, also. If it didnt then I wouldnt be trying to build one on my own....
Click to expand...
Click to collapse
K. Lemme check it. Last time I used it, it worked fine. It shouldn't do a bootloop since it only changes the keymap files, not the framework.
Thanks, I just tried again and got a boot loop once more. As I said, the modded framework I edited works fine on epinters CM10 and the one from that thread did not; I figure I will try the keymap files, also. I know I am not the only one that has had these problems which is why I started this in the first place.
Any help I can get is greatly appreciated.
update: Just did a fresh backup and flashed your linked file one more time; it actually worked this time. I finally have the cap. keys disabled with soft keys enabled. Thanks for the help! Hopefully a few more people can benefit from this now!
Yep, I just tested my keymaps with your framework. Works fine.
Edit: I made a unified framework + keymap flashable zip in case anyone's interested.
And one to restore things back to stock.
Using this. It''s working great!
quetzalcoatl2435 said:
Yep, I just tested my keymaps with your framework. Works fine.
Edit: I made a unified framework + keymap flashable zip in case anyone's interested.
And one to restore things back to stock.
Click to expand...
Click to collapse
Files attached to OP.
Is there any advantage to having soft keys over capacitive keys? Or is it purely cosmetic?
nh777 said:
Is there any advantage to having soft keys over capacitive keys? Or is it purely cosmetic?
Click to expand...
Click to collapse
Soft keys are cool. Nah, it's mostly cosmetic, but it gives you a Nexus "feel". Plus you get to see the actionbar in action (see what I did there?) with this mod.
BTW, I haven't seen this thread updated for the latest (22/8) version yet, so I updated these myself.
Soft keys + disabled cap keys.
Restore stuff back to normal.
I hope lstat doesn't mind. I don't intend to hijack his thread, though, so I will remove these links if he asks me to.
Remember, these are only tested on epinter's 22/8 version. Use at your own risk.
quetzalcoatl2435 said:
Soft keys are cool. Nah, it's mostly cosmetic, but it gives you a Nexus "feel". Plus you get to see the actionbar in action (see what I did there?) with this mod.
BTW, I haven't seen this thread updated for the latest (22/8) version yet, so I updated these myself.
Soft keys + disabled cap keys.
Restore stuff back to normal.
I hope lstat doesn't mind. I don't intend to hijack his thread, though, so I will remove these links if he asks me to.
Remember, these are only tested on epinter's 22/8 version. Use at your own risk.
Click to expand...
Click to collapse
Im not worried about hijacking, go ahead and keep it coming! I will link back to the OP once more!
update: Files are up on OP.
lstat said:
Im not worried about hijacking, go ahead and keep it coming! I will link back to the OP once more!
update: Files are up on OP.
Click to expand...
Click to collapse
Do the 8/22 files work for 8/23 build?
rmkilc said:
Do the 8/22 files work for 8/23 build?
Click to expand...
Click to collapse
I'm still downloading the 23/8 version, so I can't really tell yet, but you can check if there are changes in the framework-res yourself by comparing the file from the 22/8 version with the 23/8 version. If the contents are the same, then it's safe to assume they will work without problems. If they are different, then it *might* work, but it's not recommended.
Well now there is 8/23B.
Been busy with other stuff today, didnt realize there was another update! Downloading now to test, I will report back shortly.
rmkilc said:
Well now there is 8/23B.
Click to expand...
Click to collapse
That's what I'm currently downloading. Dev-host is slow as molasses...
Edit: Download finally finished. There are framework changes, don't flash the 22/8 mod on 23b/8.
7 tries later, I finally got it. :banghead:
Sent from my Xoom using Tapatalk 2
Still waiting for the download to finish, grr.
rmkilc said:
7 tries later, I finally got it. :banghead:
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
got it as in installed the current files over the new 8/23b?
Hi guys,
Download links for ClockWorkMod Recovery both touch and non touch.
Now moved here
Bugs : You tell me.
Thanks,
Dark Passenger
Credits : People who made this possible.
Lloir(base tree).
Claudy(bug fixes).
Cobje(bug fixes and major porting).
neXus PRIME(major porting and finishing touches).
Dark Passenger(finishing touches and final bug fixes).
Gweedo767(clockworkmod maintainer and the person to make us official).
Note:This thread shall be moved to development forum once rom manager integration is complete
How to install.
prerequisites
unlocked bootloader.
fastboot
a usable brain.
>reboot to bootloader/fastboot mode
>open a fastboot terminal and type
>fastboot flash recovery <recovery_name>.img
>fastboot reboot-bootloader
>fastboot erase cache(precaution)
Thanks guys.
I have tested flash, wipes and it works (I tried flashing AromaFM and it worked, not an entire ROM) but if I select mount storage it doesn't work!
Also, I'm in ICS (1.14) ROM not JB
pfff.....why is that...?
this recovery : http://forum.xda-developers.com/showthread.php?t=2076245
has the same bug... i cant mount sd :S
gbueno6 said:
I have tested flash, wipes and it works (I tried flashing AromaFM and it worked, not an entire ROM) but if I select mount storage it doesn't work!
Also, I'm in ICS (1.14) ROM not JB
Click to expand...
Click to collapse
mhb92 said:
pfff.....why is that...?
this recovery : http://forum.xda-developers.com/showthread.php?t=2076245
has the same bug... i cant mount sd :S
Click to expand...
Click to collapse
same tree.
so except ums no other bugs ? graphics okay ...
also adb and adb sideloading.
Can some one give me a log for the ums behaviour.
Thanks.
Dark Passenger said:
Can some one give me a log for the ums behaviour.
Thanks.
Click to expand...
Click to collapse
I can't because I don't know how to :crying:
All I can do is confirm you that all wipes are working and that no graphic glitches were found!
I'm sorry
gbueno6 said:
I can't because I don't know how to :crying:
All I can do is confirm you that all wipes are working and that no graphic glitches were found!
I'm sorry
Click to expand...
Click to collapse
Advanced-Copy Log to SD.
xpirt
gbueno6 said:
I can't because I don't know how to :crying:
All I can do is confirm you that all wipes are working and that no graphic glitches were found!
I'm sorry
Click to expand...
Click to collapse
alternative to what @xpirt told
Code:
adb pull /cache/recovery/last_log
EDIT do this after you try UMS(if on windows wait for sometime for the drivers to install like atleast 10 min) and boot into the rom.
xpirt said:
Advanced-Copy Log to SD.
xpirt
Click to expand...
Click to collapse
I can't "copy log to sd" it just says "show log".
Dark Passenger said:
alternative to what @xpirt told
Code:
adb pull /cache/recovery/last_log
EDIT do this after you try UMS(if on windows wait for sometime for the drivers to install like atleast 10 min) and boot into the rom.
Click to expand...
Click to collapse
Ok, I have copied the last_log file (i tried usb mass storage and waited for some minutes before copying the file). I'm unrooted so I picked up the file with AromaFM.
I hope it helps!
PD: There's also something weird that happened to me with the other CWM recovery: when I switched off the phone to charge it, the orange light blinks for 15 seconds and the phone starts again! It doesn't happen with TWRP recovery (the "starting process", not the blinking). EDIT: The restart issue does NOT happen with this recovery. Yeyyyy!!
@OP, why panicking? ums will work just fine
you need to add proper lines in BoardCOnfig.mk and ramdisk. You should have waited for me to fix it as i gave you my tree. Anyways Try uncommenting the line for UMS_LUNFILE which is commented, and delete the next two lines after it. Compile it with that and tell me.
neXus PRIME said:
@OP, why panicking? ums will work just fine
Click to expand...
Click to collapse
I'm a generally panicky sort of person...
neXus PRIME said:
you need to add proper lines in BoardCOnfig.mk and ramdisk. You should have waited for me to fix it as i gave you my tree. Anyways Try uncommenting the line for UMS_LUNFILE which is commented, and delete the next two lines after it. Compile it with that and tell me.
Click to expand...
Click to collapse
Yes its your tree and actually the fix became apparent with the log.
Thank you for everything you have done for this devices recovery and I have no plans of changing that.The recovery is now fully functional and bugfree as soon as Gweedo767 is free he will be doing an official build(dont hold your breadth may take a while).
Post that official builds shall be available on clockworkmod.com and this thread will cease to exist(at least it will be locked).
And @neXus PRIME will you be updating your thread with this info since you will be the main maintainer.
Thank you ,
Dark Passenger.
Thanks for all your work making CWM official.:good::good:
btw, i said the "panic" thing in a light-hearted way.
The recovery tree is originally LLOIR's, later on modified by cobje(therbom), Clauddy, and then final fixed tree by neXusPRIME (me). Please give credits to all of them.
Secondly, i like TWRP far more than CWM, so i invite you to be the official CWM maintainer if you are willing. We can work on recoveries together.
I currently have JB and ICS TWRP 2.5.0.0 ready to be released but only do it when i receive JB OTA.
Lastly, NOTE that the tree you are using for OFFICIAL CWM is only ICS COMPATIBLE. You will need to modify the recovery.fstab for JB compatible recovery by changing the mount points for SYSTEM,DATA,CACHE as they are in JB ROM proc/emmc. Then you will rebuild and CWM will be able to flash ROMs for people with hboot 1.25.0.0
Regards
Yasir
neXus PRIME said:
Thanks for all your work making CWM official.:good::good:
btw, i said the "panic" thing in a light-hearted way.
The recovery tree is originally LLOIR's, later on modified by cobje(therbom), Clauddy, and then final fixed tree by neXusPRIME (me). Please give credits to all of them.
Secondly, i like TWRP far more than CWM, so i invite you to be the official CWM maintainer if you are willing. We can work on recoveries together.
I currently have JB and ICS TWRP 2.5.0.0 ready to be released but only do it when i receive JB OTA.
Lastly, NOTE that the tree you are using for OFFICIAL CWM is only ICS COMPATIBLE. You will need to modify the recovery.fstab for JB compatible recovery by changing the mount points for SYSTEM,DATA,CACHE as they are in JB ROM proc/emmc. Then you will rebuild and CWM will be able to flash ROMs for people with hboot 1.25.0.0
Regards
Yasir
Click to expand...
Click to collapse
1. Its my pleasure.
btw so was mine
2.all credits will be present once official builds are online and I open a thread for it.(maybe you could make your thread jb version so there are both versions present for those who want it).
3.wat a coincidence I like cwm better than TWRP. no offence seem to work.Also the recovery tree as always is open for anyone with a github account to modify.
4.Same here the tree submited is for ics and will be updated only when i get the jb update(knew about the mount points from the various thread actually from your post I think).
PS do you know whats needed and/or where I can get the sources for touch recovery.
PPS in your recovery.fstab(cwm version) the internal sdcard(emmc) is mounted as vfat where as in cm its emmc.
gbueno6 said:
Ok, I have copied the last_log file (i tried usb mass storage and waited for some minutes before copying the file). I'm unrooted so I picked up the file with AromaFM.
I hope it helps!
PD: There's also something weird that happened to me with the other CWM recovery: when I switched off the phone to charge it, the orange light blinks for 15 seconds and the phone starts again! It doesn't happen with TWRP recovery (the "starting process", not the blinking). EDIT: The restart issue does NOT happen with this recovery. Yeyyyy!!
Click to expand...
Click to collapse
so there are no problems other than UMS.
can you please confirm.
thanks.
Dark Passenger said:
so there are no problems other than UMS.
can you please confirm.
thanks.
Click to expand...
Click to collapse
Yes, other than UMS, no more issues!
PD: I won't be able to test it again because I upgraded to JB!! ^^
Thank you very much for your work!
gbueno6 said:
Yes, other than UMS, no more issues!
PD: I won't be able to test it again because I upgraded to JB!! ^^
Thank you very much for your work!
Click to expand...
Click to collapse
cool :jealous: i might have to wait a tad bit longer for that
also if possible can you hold out on the update for a few more days might be the first to try out official builds.
Dark Passenger said:
cool :jealous: i might have to wait a tad bit longer for that
also if possible can you hold out on the update for a few more days might be the first to try out official builds.
Click to expand...
Click to collapse
I'm afraid I can't! I was very excited watching that my operator updated to JB (they never updated our ROM before) that I made it and now I'm in JB.
I'm sorry!
Also, if you want me to test it in JB, let me know it and I'll be very happy to help!
Have a great day
gbueno6 said:
I'm afraid I can't! I was very excited watching that my operator updated to JB (they never updated our ROM before) that I made it and now I'm in JB.
I'm sorry!
Also, if you want me to test it in JB, let me know it and I'll be very happy to help!
Have a great day
Click to expand...
Click to collapse
aye aye aye I just got an official build hot off jenkins.
Any one willing to test and let me know if ums is good and alls well.
latest built
@gbueno6 cab you test ums (yes in JB) it should work fine don't try anything else wont work.
Download
Mega
Installing
You can't flash this yet (I'm working on that, I promise) but you can boot from it!
NOTE: THIS IS A WIP. Not a lot has been really tested yet and this is posted merely for your enjoyment atm.
I don't suggest flashing anything yet, not that there is anything to flash heh.
Also, I take no responsibility if you break your watch, yada, yada.
To do this, make sure you have Android's tools (for fastboot), an unlocked bootloader, and the watch connected to your computer in Debug mode.
> adb reboot bootloader
<wait for the reboot to happen>
> fastboot boot /path/to/recovery.img
Click to expand...
Click to collapse
Enjoy!
Did u push the tree to github?
1st built for me was a no go
wouldn't twrp make more sense since its touch based?
D-FUSE said:
Did u push the tree to github?
1st built for me was a no go
Click to expand...
Click to collapse
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
ptesmoke said:
wouldn't twrp make more sense since its touch based?
Click to expand...
Click to collapse
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
ptesmoke said:
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
Click to expand...
Click to collapse
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
dude1981 said:
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
jamcar said:
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Click to expand...
Click to collapse
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Click to expand...
Click to collapse
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Click to expand...
Click to collapse
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
PlayfulGod said:
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Click to expand...
Click to collapse
It's only booting because it doesn't work when flashed to recovery. The file size is around 8 mb whereas the legitimate recovery is 23 mb, which I'm sure is an issue. Is it possible that I'm only creating a ramdisk that gets paired with the watch's kernel and I need to make an image with both of them? Sorry, this whole uBoot stuff confuses me a bit.
PlayfulGod said:
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Click to expand...
Click to collapse
Heh, I'm not actually afraid of git, I guess, I'm afraid of the whole "making a device-specific git repo that can be easily pulled while building CM." I guess I just don't have the time atm to set it up properly, but dw, I'll get to it this weekend! :fingers-crossed:
dude1981 said:
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, the iOS mod is something I downloaded awhile ago for my N5. I'm afraid I don't have the link anymore. Sorry, man.
Pepski said:
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
Click to expand...
Click to collapse
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Smith7018 said:
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Click to expand...
Click to collapse
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Pepski said:
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Click to expand...
Click to collapse
Weird... I don't even think you need root to push to /sdcard/ but I could be wrong. I'd suggest trying /sdcard/emoji.zip so it knows where to resolve. Also, I don't use Windows, but does the backslash work on adb as a file separator?
what happened to development on this?
Hi all! I just finished porting Paranoid Android Beta 5 (Oct 22, 2014) to our beloved Vibrant. My only problem is my Vibrant is my daily driver. Can any kind soul whose Vibrant is not your daily driver (or if you just like to live on the bleeding edge) please test this out for me?
ROM *EDIT: Wi-Fi not working yet. Wi-Fi working now, but took down link to wait for original dev's permission. I have permission now, but I keep getting "No SD card" error
PA Gapps
Official PA5 xda link of the Rom I ported (i9000/galaxysmtd)
Permission from the official Rom maintainer is still pending, hopefully I'll get it soon.
Thank you so much!
Edit: I suppose I should include these steps (copied from xda thread above):
Installation Instructions
Coming other ROM
1. You must be rooted!
2. You must have a custom recovery installed.
3. Wipe your device if you are not coming from PA 4.+ already.
4. Flash the ROM zip, it could appear a warning (all data will be wiped due different partition table)
5. Reflash the ROM zip, it will continue now.
6. Flash the GAPPS.
7. Reboot. (It can take up to 5 min.)
8. Enjoy
Coming from AOSPA 4.0+
NOTE: I'm not responsible of crashes due kernel changes.
1. Flash the ROM zip.
2. Reboot.
3. Wait the upgrading android dialog.
4. Enjoy!
Click to expand...
Click to collapse
I don't know why I was hesitating - I could just take a Nandroid backup before flashing. I just did this, and I'm happy to report that everything went just fine! The only snag I had was a Wi-Fi problem - it says "Turning Wi-Fi on", but just stays like that. I remember seeing this problem somewhere before, maybe the kernel. Will investigate and report back
------
Edit (4.41pm cst):
SIGH... Been researching and trying out solutions all this time, and nothing's working Tried NeatKernel, Semaphore kernel, neither worked. Will keep at it and report back.
raddatt said:
I don't know why I was hesitating - I could just take a Nandroid backup before flashing. I just did this, and I'm happy to report that everything went just fine! The only snag I had was a Wi-Fi problem - it says "Turning Wi-Fi on", but just stays like that. I remember seeing this problem somewhere before, maybe the kernel. Will investigate and report back
------
Edit (4.41pm cst):
SIGH... Been researching and trying out solutions all this time, and nothing's working Tried NeatKernel, Semaphore kernel, neither worked. Will keep at it and report back.
Click to expand...
Click to collapse
you need to copy over system/lib/modules from base to port or from custom kernel if that what you're using, in order to get wifi working. I could of sworn PA was patched a certain way and would only run with its provided kernel or maybe something has changed since i last tried to port it for personal use. Also not a great idea posting ones work with out getting full permission yet may cause you trouble later on down the road...
dzee206 said:
you need to copy over system/lib/modules from base to port or from custom kernel if that what you're using, in order to get wifi working. I could of sworn PA was patched a certain way and would only run with its provided kernel or maybe something has changed since i last tried to port it for personal use. Also not a great idea posting ones work with out getting full permission yet may cause you trouble later on down the road...
Click to expand...
Click to collapse
Omg, that worked beautifully! Thank you so much, kind sir! I've also taken down the Rom download link and will put it back up again once I have full permission. Thanks for prompting me to do it. This is my first time at porting a Rom, so I'm not fully caught up on the etiquette yet. I've asked him for permission, and thought I could put it up only for testing purposes in the meantime, and then post it fully in our development forum once I have his full permission. He has been pretty great so far with granting a few people permission on that thread, so hopefully I can become one of them soon Thanks again so much!
Okay, it seems like I'm having another problem/bug. My phone's not detecting its SD card. When I tried to download a file it said, "No SD card". When I went to Settings/Storage, there are 2 areas of storage as usual, but it only lasts for about 3 seconds, then all the rows collapse and all I'm left with is "Internal Storage" and a couple of rows - no sight of an SD card. Is this something you've come across?
raddatt said:
Okay, it seems like I'm having another problem/bug. My phone's not detecting its SD card. When I tried to download a file it said, "No SD card. When I went to Settings/Storage, there are 2 areas of storage as usual, but it only lasts for about 3 seconds, then all the rows collapse and all I'm left with is "Internal Storage" and a couple of rows - no sight of an SD card. Is this something you've come across?
Click to expand...
Click to collapse
Try flashing one of the custom kernels we have and see if that works, if it doesn't help solve the issues it may just be kernel related. If all else fails give this a shot http://forum.xda-developers.com/showpost.php?p=51293597&postcount=151<br /> and if that doesn't help try porting a previous version of PA and see if the SD will mount properly.
For some reason whenever I flash a kernel, everything goes well until the "Android is upgrading" point. All apps are updated, then it says "starting apps" or something and it doesn't go anywhere after that, just stuck on that stage Then when I tried to reboot into recovery, it would be really difficult for some reason (like holding the buttons down would cause boot looping, very finicky). When I finally did get into recovery, it turned out to be Twrp, and not the Cwm I was used to. I have no idea where it came from, esp since I believe both port and base were cwm! I got really scared for a few minutes because twrp didn't have my backups. Finally, after a few more reboots, I got back the familiar cwm. I've never been so relieved in my life lol. I'm back to my old state, and will try again tomorrow morning. That's what I get for trying to play hero haha
Sent from my Vibrant using ugly ass xda app.
raddatt said:
For some reason whenever I flash a kernel, everything goes well until the "Android is upgrading" point. All apps are updated, then it says "starting apps" or something and it doesn't go anywhere after that, just stuck on that stage Then when I tried to reboot into recovery, it would be really difficult for some reason (like holding the buttons down would cause boot looping, very finicky). When I finally did get into recovery, it turned out to be Twrp, and not the Cwm I was used to. I have no idea where it came from, esp since I believe both port and base were cwm! I got really scared for a few minutes because twrp didn't have my backups. Finally, after a few more reboots, I got back the familiar cwm. I've never been so relieved in my life lol. I'm back to my old state, and will try again tomorrow morning. That's what I get for trying to play hero haha
Sent from my Vibrant using ugly ass xda app.
Click to expand...
Click to collapse
Its fine you ended up with twrp that happens when you flash a kernel that comes with twrp, see our device recovery image is within the kernel. I actually prefer twrp over cwm due to it being touch screen and putting less stress/abuse on the volume and power button/s. I checked the i9000 thread of PA and didn't see any users with the SD not mounting so I'm guessing it could be kernel related. If i can get my hands on my wife's vibrant I'll do a personal port and let you know of the results.
dzee206 said:
Its fine you ended up with twrp that happens when you flash a kernel that comes with twrp, see our device recovery image is within the kernel. I actually prefer twrp over cwm due to it being touch screen and putting less stress/abuse on the volume and power button/s. I checked the i9000 thread of PA and didn't see any users with the SD not mounting so I'm guessing it could be kernel related. If i can get my hands on my wife's vibrant I'll do a personal port and let you know of the results.
Click to expand...
Click to collapse
Ah, yes, from the kernel, that makes sense. Yeah, I'm glad more people are switching to Twrp because I like the touchscreen too instead of hurting the physical buttons. There's also a kernel (Semaphore?) that uses touchscreen scrolling in Cwm, which is cool too. Thank you, I'd really appreciate that!
Also, can you please show me how to properly bring an outside kernel into a Rom? I have been following this guide. It says to replace:
bml_over_mtd
bml_over_mtd.sh
erase_image
file_contexts
flash_image
make_ext4fs
boot.img
Plus system/lib/modules per your suggestion. However, I was about to try Iyahman's kernel, but it doesn't have:
file_contexts
flash_image
make_ext4fs
system/lib/modules
How would that work?
Btw, I just tried pulling the kernel resources of the kernel used by SlimKat into PA5 rom, but I still get the No SD card error
Our SlimKat rom uses the "samsung kernel aries", which is also used by the i9000 PA rom, so I thought it would work this time, but nope.
@dzee206 - Sorry for the spamming, man, but I just wanted to clarify the SD card problem I'm having, because I'm a bit confused as to what exactly it is. So when I try to download an .apk off of an xda thread using Browser, I get the error:
"No SD Card
An SD card is required to download ...apk"
But I am able to successfully download an app from the Play Store and use it well.
When I open Gallery, I get this error:
"No Storage
No external storage available"
Sorry I'm a big noob, but is the phone saying I don't have an external card or an internal card? I've never had these problems on this phone before, and I've never used an external SD on it. Thanks.
raddatt said:
Also, can you please show me how to properly bring an outside kernel into a Rom? I have been following this guide. It says to replace:
bml_over_mtd
bml_over_mtd.sh
erase_image
file_contexts
flash_image
make_ext4fs
boot.img
Plus system/lib/modules per your suggestion. However, I was about to try Iyahman's kernel, but it doesn't have:
file_contexts
flash_image
make_ext4fs
system/lib/modules
How would that work?
Click to expand...
Click to collapse
You only need the files in the root of the kernel (zip) not the folders though, don't worry about the modules with semaphore that's just how it is. Just leave file_contexts, flash_image, make_ext4fs that came with PA while porting they should suffice. Sorry man I ported PA yesterday while at my in-laws but didn't get a chance to transfer it over. I'd do it while at home but my PC exhaust fan crapped out on me and I won't have time to replace it till the beginning of next week. For now the best I can do is give advice base on my experience porting. May wanna give a different ROM a shot at porting such as DU or Mackay.
Sent from my SGH-I717 using XDA Premium 4 mobile app
dzee206 said:
You only need the files in the root of the kernel (zip) not the folders though, don't worry about the modules with semaphore that's just how it is. Just leave file_contexts, flash_image, make_ext4fs that came with PA while porting they should suffice. Sorry man I ported PA yesterday while at my in-laws but didn't get a chance to transfer it over. I'd do it while at home but my PC exhaust fan crapped out on me and I won't have time to replace it till the beginning of next week. For now the best I can do is give advice base on my experience porting. May wanna give a different ROM a shot at porting such as DU or Mackay.
Sent from my SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man, I really appreciate your advice and efforts. Will try a couple more things and report back.
I tried putting Iyahman's Semaphore kernel stuff into PA5 and using SlimKat as base, but it didn't work I got the error 7, that the ROM was for i9000 and not for T959. I don't get why it happened... I deleted the i9000 lines from updater-script and everything, just like previous attempts (the rom had actually loaded properly in previous attempts, so the difference here must lie in the using of the kernel or SlimKat as base).
raddatt said:
I tried putting Iyahman's Semaphore kernel stuff into PA5 and using SlimKat as base, but it didn't work I got the error 7, that the ROM was for i9000 and not for T959. I don't get why it happened... I deleted the i9000 lines from updater-script and everything, just like previous attempts (the rom had actually loaded properly in previous attempts, so the difference here must lie in the using of the kernel or SlimKat as base).
Click to expand...
Click to collapse
Never use a ported ROM as base it be best to use the unofficial cm11 or spirit ROM, since those are the only ROMs we have that's built from source. Honestly if it was me I'd give up on PA and look for something else to run there's plenty of i9000 ROMs that have yet to be ported over or hasn't been updated I a while.
Sent from my SGH-I717 using XDA Premium 4 mobile app
dzee206 said:
Never use a ported ROM as base it be best to use the unofficial cm11 or spirit ROM, since those are the only ROMs we have that's built from source. Honestly if it was me I'd give up on PA and look for something else to run there's plenty of i9000 ROMs that have yet to be ported over or hasn't been updated I a while.
Sent from my SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ahh, thanks! I read somewhere that both base and port should both be either CM-based or AOSP-based, so I guess I started looking for AOSP-based roms and decided to try SlimKat. But I'll make sure not to use ported roms anymore. I tried the cm11 one, I might try Spirit as a last ditch effort, then see what else is on i9000. When Paranoid updated their website this week, I had checked it out, and when I saw galaxymtd as one of the legacy devices, I had gotten excited at the prospect of a new-ish rom. But lemme see what else is on i9000 after I try a couple more things here. Thanks again!
raddatt said:
Ahh, thanks! I read somewhere that both base and port should both be either CM-based or AOSP-based, so I guess I started looking for AOSP-based roms and decided to try SlimKat. But I'll make sure not to use ported roms anymore. I tried the cm11 one, I might try Spirit as a last ditch effort, then see what else is on i9000. When Paranoid updated their website this week, I had checked it out, and when I saw galaxymtd as one of the legacy devices, I had gotten excited at the prospect of a new-ish rom. But lemme see what else is on i9000 after I try a couple more things here. Thanks again!
Click to expand...
Click to collapse
It's some what true about using the same type of based ROMs when it comes to porting but pickings are slim. Myself and a bunch of other porters have been using cm as base and haven't had any issues porting different type ROMs.
Sent from my SGH-I717 using XDA Premium 4 mobile app
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Features:
-touchwiz ui with near stock functionality
-based on Tab A and Tab S frameworks
-Tab S2 apps
-Tab S3 UI Sounds
-SPen features
-theme support
-pre-rooted (magisk)
-deodexed
-debloated
-knox removed
-all apps support multiwindow
-some minor changes like removing safe volume warning, overlay fix etc
-ported IronKernel from @Tkkg1994 (read more about kernel features here: https://forum.xda-developers.com/galaxy-tab-s/orig-development/kernel-ironstock-kernel-v3-2-t3531295 )
Notes:
full wipe required!
First boot takes 10 minutes
For some features root required
Device encryption doesn't support here
If you don't want to install root, remove magisk folder from install zip
If you don't have working spen, flash stock rom before this one.
If you want to make custom rom based on my rom, you're welcome.
Thanks to @Miron24 for testing rom
Download:
02feb
gdrive: https://drive.google.com/open?id=1sAiyxBEkEDEWtOiuMvOM53DKWmAVWHQx
Thanks to @Tkkg1994 for the kernel
Kernel sources:
https://github.com/bonuzzz/IronKernel
I'll download and give this a shot. I really need all apps in multi windows.
How works SPEN?
write me please your feedback, what working or not working in hardware part
won't work on p600,
@maxximboy black screen after bootloader without any reboots?
@bonuzzz
Do your roms (P900, P600, T900) work on 3G devices(P901, etc.)? I want to test your rom on my P601. Do you plan to port Tab A 10.1 with S Pen apps to your roms?
Miron24 said:
@bonuzzz
Do your roms (P900, P600, T900) work on 3G devices(P901, etc.)? I want to test your rom on my P601. Do you plan to port Tab A 10.1 with S Pen apps to your roms?
Click to expand...
Click to collapse
if you dont need 3g support, so it should working. but current version doesn't boot on p600. trying to find, where is problem in kernel. wait for fix.
do you want exact app from tab A ?
Hi there, good to see this kind of development. I tried flashing, but install was unsuccessful.
Previous ROM is Resurrection Remix for P600
Went to recovery, did factory reset on TWRP, then wiped System partition
Flashed your zip, and out comes on the terminal:
This package is for "v1awifi, v2awifi, n1awifi, n2awifi, klimtwifi, chagallwifi" devices, this is a "lt03wifiue"
Updater process ended with ERROR: 7
So I assume the problem lies somewhere with the device name/code, but I'm not sure how to change this. From what I've searched it's in build.prop, but that doesn't exist one /system is wiped. After wiping everything I tried flashing AICP Rom, but still the same error code comes out when I tried flashing your .zip. Have any other tips? I assume you also have a P600 no? How did you get it to boot?
EDIT: Thanks for correcting noob mistake @mosimchah
Pact said:
Previous ROM is Resurrection Remix for P600 ie AOSP based
Click to expand...
Click to collapse
Resurrection Remix is lineage based, and lineage is caf based (not AOSP)
Sent from my LEX727 using XDA Labs
---------- Post added at 06:07 PM ---------- Previous post was at 06:00 PM ----------
bonuzzz said:
if you dont need 3g support, so it should working. but current version doesn't boot on p600. trying to find, where is problem in kernel. wait for fix.
do you want exact app from tab A ?
Click to expand...
Click to collapse
Check out the unofficial Lineage 13.0 kernel, it's based on the tab s mm source and works on the p600
https://github.com/exynos5420/andro...configs/cyanogenmod_deathly_n1awifi_defconfig
https://github.com/exynos5420/andro...tree/091b5954799bbfbb38bced4ac6342c5939900348
Sent from my LEX727 using XDA Labs
ok, lt03wifiue is also p600. I didn't know that. you could remove assert in updater-script to disable check device.
@Pact I have P900
OK, I removed the assert lines as per this guide:
https://forum.xda-developers.com/showpost.php?p=31519426&postcount=186
Used 7zip, edited the file mentioned above, deleted the lines, 7zip recompiles that, moved it to SD card and started flashing. Of course I did a factory reset beforehand, and wiped /system too. The usual stuff appears:
Checking config . . .
Formatting system . . .
Extracting system . . .
The flash was successful, then the Magisk installation lines appear and that was good too.
Once that's done, I flashed the kernel provided above, and that complete, I rebooted the tablet, no other warnings or anything like that appearing during installation. The Galaxy Note screen appeared, then the screen went black (lights on, nothing else displayed). I thought this was normal for a new flash, then I waited till 20 minutes and it's still like that. So I forced a reboot (long press power button) and the Galaxy Note screen appeared again, this time I've waited 5 minutes and nothing else happens - still lighted screen with nothing else. The backside is hot during both reboots, so something is definitely happening using CPU cycles, but I'm not sure what. Should I dirty reflash next?
bonuzzz said:
ok, lt03wifiue is also p600. I didn't know that. you could remove assert in updater-script to disable check device.
Test please this kernel
https://yadi.sk/d/WGxcpVrn3K6G7R
@Pact I have P900
Click to expand...
Click to collapse
Make sure you're using the proper vendor blobs
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/n1awifi
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/nx-common
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/exynos5420-common
Using the tab s blobs could cause it to not boot
Pact said:
OK, I removed the assert lines as per this guide:
https://forum.xda-developers.com/showpost.php?p=31519426&postcount=186
Used 7zip, edited the file mentioned above, deleted the lines, 7zip recompiles that, moved it to SD card and started flashing. Of course I did a factory reset beforehand, and wiped /system too. The usual stuff appears:
Checking config . . .
Formatting system . . .
Extracting system . . .
The flash was successful, then the Magisk installation lines appear and that was good too.
Once that's done, I flashed the kernel provided above, and that complete, I rebooted the tablet, no other warnings or anything like that appearing during installation. The Galaxy Note screen appeared, then the screen went black (lights on, nothing else displayed). I thought this was normal for a new flash, then I waited till 20 minutes and it's still like that. So I forced a reboot (long press power button) and the Galaxy Note screen appeared again, this time I've waited 5 minutes and nothing else happens - still lighted screen with nothing else. The backside is hot during both reboots, so something is definitely happening using CPU cycles, but I'm not sure what. Should I dirty reflash next?
Click to expand...
Click to collapse
Sent from my LEX727 using XDA Labs
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
bonuzzz said:
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
Click to expand...
Click to collapse
I'm not using this ROM, just happened to see the thread
Sent from my LEX727 using XDA Labs
bonuzzz said:
@maxximboy black screen after bootloader without any reboots?
Click to expand...
Click to collapse
no no black or blank screen, it wont flash the rom, message was something like, my p600 is not compatible.
View attachment tombstones.zip
View attachment last_kmsg.txt
bonuzzz said:
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
Click to expand...
Click to collapse
Hre's those files. After the second black blank screen that I mentioned in my previous post, I rebooted to recovery and grabbed these from the file manager. There's 10 tombstone files in the folder so I zipped it up. Hope it helps.
I am really excited about this rom, and cant wait to flash it on my p600..... i am not techies as you guys, so my question is, what do i need to do to make it work?
thanks all
maxximboy said:
I am really excited about this rom, and cant wait to flash it on my p600..... i am not techies as you guys, so my question is, what do i need to do to make it work?
thanks all
Click to expand...
Click to collapse
It need proper kernel ...patience
I need a tester, who will spend some time to flash couple of builds. write in pm
thanks in advance