Related
So many people have been wondering about this, so I thought I would try to bring it to life. I would like to get a port of CyanogenMod 7 going for the Atrix 2. I know it normally comes with a custom kernel, but is there any reason it won't run with our stock one? obviously we can't change it until we get our bootloader unlocked. I am not a super talented developer like some of you, but I am capable of doing a lot. Still I would greatly appreciate any help from others who would like to take part in this. As far as I am concerned, we should be able to get something working by taking a port for some device close to ours and modifying it slightly to work. we will have to replace the radio with our own, which we can do by just flashing the fxz files we have and we will not be able to use a custom kernel. Does this sound about right to people or am I missing something big. Will CM7 run on a stock kernel, or does it need something special? thanks for any help in advance, if you are interested in helping with this, please reply here or send me a PM, preferably post here so others can see what is going on, but if it is something you don't want to share, PM me. Also, what device(s) should We look at to try and port from? I would guess the Droid Bionic as it is very similar, the RAZR as I think it also has a locked bootloader, and the Droid 3 because cm9 ports from it will boot on our phone. Any others?
lkrasner said:
So many people have been wondering about this, so I thought I would try to bring it to life. I would like to get a port of CyanogenMod 7 going for the Atrix 2. I know it normally comes with a custom kernel, but is there any reason it won't run with our stock one? obviously we can't change it until we get our bootloader unlocked. I am not a super talented developer like some of you, but I am capable of doing a lot. Still I would greatly appreciate any help from others who would like to take part in this. As far as I am concerned, we should be able to get something working by taking a port for some device close to ours and modifying it slightly to work. we will have to replace the radio with our own, which we can do by just flashing the fxz files we have and we will not be able to use a custom kernel. Does this sound about right to people or am I missing something big. Will CM7 run on a stock kernel, or does it need something special? thanks for any help in advance, if you are interested in helping with this, please reply here or send me a PM, preferably post here so others can see what is going on, but if it is something you don't want to share, PM me. Also, what device(s) should We look at to try and port from? I would guess the Droid Bionic as it is very similar, the RAZR as I think it also has a locked bootloader, and the Droid 3 because cm9 ports from it will boot on our phone. Any others?
Click to expand...
Click to collapse
Last i knew jimbridgman was working on a port. I have a rough cm7 only running on one core and only using about 427mb of ram that was passed down to me from lfaber.he said its set on 2.3.5 so u need to have 2.3.5 before u install it however still doesnt seem to boot ..stays on moto logo for me.theres two different ports i have so maybe i just tried the wrong one but i last remember trying both and to no evail..stuck at boot. If i get the time and get to a wifi spot ill upload them so u can have a go at it if youd like. Right now i am busy with scv6 which is making progress btw. So ill let u know thru pm when i get them up for u to d/l.
Sent from my MB865 using XDA
rdavisct said:
Last i knew jimbridgman was working on a port. I have a rough cm7 only running on one core and only using about 427mb of ram that was passed down to me from lfaber.he said its set on 2.3.5 so u need to have 2.3.5 before u install it however still doesnt seem to boot ..stays on moto logo for me.theres two different ports i have so maybe i just tried the wrong one but i last remember trying both and to no evail..stuck at boot. If i get the time and get to a wifi spot ill upload them so u can have a go at it if youd like. Right now i am busy with scv6 which is making progress btw. So ill let u know thru pm when i get them up for u to d/l.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Thanks, I'm glad there is some work on this going. I did not really know what all the hype was about CM until I really used it for a bit in the last few days on a family members phone, which got me excited. Keep going with scv6, I can't wait to try that out as I was quite pleased with v5 as it got me started with roms for our phone (no pressure). why do you think it is not booting well? is it just because we have to optimize it for our kernel or something?
lkrasner said:
Thanks, I'm glad there is some work on this going. I did not really know what all the hype was about CM until I really used it for a bit in the last few days on a family members phone, which got me excited. Keep going with scv6, I can't wait to try that out as I was quite pleased with v5 as it got me started with roms for our phone (no pressure). why do you think it is not booting well? is it just because we have to optimize it for our kernel or something?
Click to expand...
Click to collapse
No.he said it boots. It just isnt for me. Maybe i wasnt supposed to wipe data.dont know ill find out tho.
Sent from my MB865 using XDA
rdavisct said:
No.he said it boots. It just isnt for me. Maybe i wasnt supposed to wipe data.dont know ill find out tho.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
No problem, I will PM him and see if I can get some info. I just tried to flash one of the droid 3 ports I found for the hell of it. Naturally it did not work. would not even get past the boot logo to the animation, so I guess simple modification is out of the question for now! anyways, restoring back to normal for now until I can get some more info.
Im talkin with him now.ill let u know
Sent from my MB865 using XDA
rdavisct said:
Im talkin with him now.ill let u know
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Alright, thanks.
I don't know a thing of developing roms but i do know this, my fist phone was a nexus one, and the first custom rom i installed was the CM6 and if i remember well it was under the stock kernel, so i guess it should work with us too. It's my humble opinion
Not for nothing but isn't a CM7 port a waste of time when CM9 is only a few tweaks away from working? Why not focus completely on CM9 so we can get ICS on our phone?
Sent from my MB865 using Tapatalk
jfrank1485 said:
I don't know a thing of developing roms but i do know this, my fist phone was a nexus one, and the first custom rom i installed was the CM6 and if i remember well it was under the stock kernel, so i guess it should work with us too. It's my humble opinion
Click to expand...
Click to collapse
It will work without a custom kernel. You will have to strip it though... as all builds of CM7 come with a custom kernel. It's really just a matter of having everything in place and tweaking it to work with the stock Motorola kernel.
StrizzMatik said:
Not for nothing but isn't a CM7 port a waste of time when CM9 is only a few tweaks away from working? Why not focus completely on CM9 so we can get ICS on our phone?
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
good point, but cm9 is more than a few tweaks from working. the radio may never work until the ota for ics comes out, or we can pull one with cheesecake. either way it will be a few months. plus many people like GB better anyways, i prefer ICS, but i know some do not. things we learn from developing this could of course help us with other roms as well.
Sorry guys, but I don't get as much of a chance to get on here as often anymore, and its been about 6 or so weeks since I have pulled up XDA, I just have a ton of things on my plate right now.
Yes I had a bootable CM7, but it really does not work, the big issue is that ALL of the CM7 apps are tied to the kernel, and there is no kernel that has been built that is close enough to our hardware to just stick in there.
The ONLY way I have had a successful build was to compile a custom kernel and bypass the bootloader with kexec. There was an update to kexec a few weeks ago and I have lost the ability to bypass the bootloader on our phone since then.
My plan all along has been once I can get kexec working to release this version of CM7, but the issue is that it is all based on 2.3.5, and can't go forward, since 2.3.6 does not work well with CM7, no matter what i have tried.
I have just sort of let the cm7 no-kernel port die, and I am focusing on just kexec at the moment.
I have to keep my efforts underground right now, because I have been given a cease and desist letter from Moto, about my bypassing the kernel with kexec. They (Moto) do read this board, so I do advise you to be very careful what you decide to post on this site.
P.S. I have PM'd lkranser with this information, and I will PM him the link to the last no-kernel CM7 build, but it is worthless without the kernel, which is why I started the work on kexec. I have been the one person on here really focusing on cracking the boot loader since day one that this phone was out, and I have done it 3 different ways, but it is only a temp situation, until kexec is fully working on our phone, and I am working to resolve that.
Jim
jimbridgman said:
Sorry guys, but I don't get as much of a chance to get on here as often anymore, and its been about 6 or so weeks since I have pulled up XDA, I just have a ton of things on my plate right now.
Yes I had a bootable CM7, but it really does not work, the big issue is that ALL of the CM7 apps are tied to the kernel, and there is no kernel that has been built that is close enough to our hardware to just stick in there.
The ONLY way I have had a successful build was to compile a custom kernel and bypass the bootloader with kexec. There was an update to kexec a few weeks ago and I have lost the ability to bypass the bootloader on our phone since then.
My plan all along has been once I can get kexec working to release this version of CM7, but the issue is that it is all based on 2.3.5, and can't go forward, since 2.3.6 does not work well with CM7, no matter what i have tried.
I have just sort of let the cm7 no-kernel port die, and I am focusing on just kexec at the moment.
I have to keep my efforts underground right now, because I have been given a cease and desist letter from Moto, about my bypassing the kernel with kexec. They (Moto) do read this board, so I do advise you to be very careful what you decide to post on this site.
P.S. I have PM'd lkranser with this information, and I will PM him the link to the last no-kernel CM7 build, but it is worthless without the kernel, which is why I started the work on kexec. I have been the one person on here really focusing on cracking the boot loader since day one that this phone was out, and I have done it 3 different ways, but it is only a temp situation, until kexec is fully working on our phone, and I am working to resolve that.
Jim
Click to expand...
Click to collapse
Thanks, I will take a look at all that and see if I can get anything done. I can't believe Moto actually did that! Keep up the good work though.... I mean you should stop right now of course....
jimbridgman said:
Sorry guys, but I don't get as much of a chance to get on here as often anymore, and its been about 6 or so weeks since I have pulled up XDA, I just have a ton of things on my plate right now.
Yes I had a bootable CM7, but it really does not work, the big issue is that ALL of the CM7 apps are tied to the kernel, and there is no kernel that has been built that is close enough to our hardware to just stick in there.
The ONLY way I have had a successful build was to compile a custom kernel and bypass the bootloader with kexec. There was an update to kexec a few weeks ago and I have lost the ability to bypass the bootloader on our phone since then.
My plan all along has been once I can get kexec working to release this version of CM7, but the issue is that it is all based on 2.3.5, and can't go forward, since 2.3.6 does not work well with CM7, no matter what i have tried.
I have just sort of let the cm7 no-kernel port die, and I am focusing on just kexec at the moment.
I have to keep my efforts underground right now, because I have been given a cease and desist letter from Moto, about my bypassing the kernel with kexec. They (Moto) do read this board, so I do advise you to be very careful what you decide to post on this site.
P.S. I have PM'd lkranser with this information, and I will PM him the link to the last no-kernel CM7 build, but it is worthless without the kernel, which is why I started the work on kexec. I have been the one person on here really focusing on cracking the boot loader since day one that this phone was out, and I have done it 3 different ways, but it is only a temp situation, until kexec is fully working on our phone, and I am working to resolve that.
Jim
Click to expand...
Click to collapse
How complex are the 3 different ways for temporary bypass?
Sent from my MB865 using XDA
jimbridgman said:
Sorry guys, but I don't get as much of a chance to get on here as often anymore, and its been about 6 or so weeks since I have pulled up XDA, I just have a ton of things on my plate right now.
Yes I had a bootable CM7, but it really does not work, the big issue is that ALL of the CM7 apps are tied to the kernel, and there is no kernel that has been built that is close enough to our hardware to just stick in there.
The ONLY way I have had a successful build was to compile a custom kernel and bypass the bootloader with kexec. There was an update to kexec a few weeks ago and I have lost the ability to bypass the bootloader on our phone since then.
My plan all along has been once I can get kexec working to release this version of CM7, but the issue is that it is all based on 2.3.5, and can't go forward, since 2.3.6 does not work well with CM7, no matter what i have tried.
I have just sort of let the cm7 no-kernel port die, and I am focusing on just kexec at the moment.
I have to keep my efforts underground right now, because I have been given a cease and desist letter from Moto, about my bypassing the kernel with kexec. They (Moto) do read this board, so I do advise you to be very careful what you decide to post on this site.
P.S. I have PM'd lkranser with this information, and I will PM him the link to the last no-kernel CM7 build, but it is worthless without the kernel, which is why I started the work on kexec. I have been the one person on here really focusing on cracking the boot loader since day one that this phone was out, and I have done it 3 different ways, but it is only a temp situation, until kexec is fully working on our phone, and I am working to resolve that.
Jim
Click to expand...
Click to collapse
This is THE man right here. Thanks for all the hard work Jim, we wouldn't have crap without this guy
Sent from my MB865 using Tapatalk
rdavisct said:
How complex are the 3 different ways for temporary bypass?
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Well the first two ended up bricking my phone after a reboot, but work until you reboot.... hence temporary.... They both involve compiling a HUGE kernel file that is over a GB in size, then while the bootloader tries to uncompress the tar.gz kernel file, you replace the kernel file with the one you want to boot, since the bootloader is busy. The second one is similar, but replaces the boot.img and the restore partition as well while the bootloader is busy. Again you get one successful boot and can run forever, unless you need to reboot, or drain the battery, then you are hard bricked.... that is how I bricked my first 3 A2s.
The third is kexec, that is how I had been running cm7 with a custom kernel for 2 months. Untill the last update that would allow ics kernel booting, but I have had trouble getting it working again with the newer version. It works like firmware in that you can't go to a lower version from a higher version, even after an fxz flash, so I am stuck, until I get it working. Oh and kexec has not caused a single brick yet, when I had it working.
Jim
Sent from my MB865 using xda premium
Oh by the way here is the link to kexec, for those who would like to give it a shot..... it is not hard.... it looks like kohlk has it for the razr, so that version "should" work for us too.
I will give this one a try hopefully tomorrow and report back. I was using my own compiled version before.
Kexec for the razr:
http://forum.xda-developers.com/showthread.php?t=1599648
Jim
Sent from my MB865 using xda premium
jimbridgman said:
Oh by the way here is the link to kexec, for those who would like to give it a shot..... it is not hard.... it looks like kohlk has it for the razr, so that version "should" work for us too.
I will give this one a try hopefully tomorrow and report back. I was using my own compiled version before.
Kexec for the razr:
http://forum.xda-developers.com/showthread.php?t=1599648
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Hm, I can't get it to work... Here's the output when I execute "unlockme.sh"
Code:
sh /system/bypassme/bypassme.sh
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444
Written 0x4444AAAA; readback 0x4444
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444AAAA
Written 0x44445555; readback 0x4444AAAA
I've recognized devtree argument! devtree3Adding OMAP Device Tree...
Adding initrd...
Then it hot reboots but the kernel stays the same:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cogeary said:
Hm, I can't get it to work... Here's the output when I execute "unlockme.sh"
Code:
sh /system/bypassme/bypassme.sh
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444
Written 0x4444AAAA; readback 0x4444
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444AAAA
Written 0x44445555; readback 0x4444AAAA
I've recognized devtree argument! devtree3Adding OMAP Device Tree...
Adding initrd...
Then it hot reboots but the kernel stays the same:
Click to expand...
Click to collapse
You need a kernel to boot for that to change. The kernel must be compiled for this device though. That is great news though, that means that you can boot other kernels with it. Check what kholk has to say on how to in the link I posted, there is a place you need to put the kernel...
This is HUGE!!!!
Jim
Sent from my MB865 using xda premium
jimbridgman said:
You need a kernel to boot for that to change. The kernel must be compiled for this device though. That is great news though, that means that you can boot other kernels with it. Check what kholk has to say on how to in the link I posted, there is a place you need to put the kernel...
This is HUGE!!!!
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
cogeary said:
Hm, I can't get it to work... Here's the output when I execute "unlockme.sh"
Code:
sh /system/bypassme/bypassme.sh
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444
Written 0x4444AAAA; readback 0x4444
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444AAAA
Written 0x44445555; readback 0x4444AAAA
I've recognized devtree argument! devtree3Adding OMAP Device Tree...
Adding initrd...
Then it hot reboots but the kernel stays the same:
Click to expand...
Click to collapse
This should probably be moved/quoted in the Bootloader thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
**[p999 G2X ONLY) PRE-ALPHA- NO SUPPORT - KNOWN BUGS (NO CALL AUDIO)**
AS ALWAYS 'A BIG THANKS' TO THE CYANOGENMOD TEAM FOR ALL THEY DO. WITHOUT THEM NONE OF THIS WOULD BE POSSIBLE.
There will be no support provided for this release as it is still undergoing development. Do not contact support regarding bugs as we are well aware of the current state of each Service.
This is in Pre-Alpha so expect things to not work. This is a barebones Jelly Bean 4.1 AOSP build. Not everything will be functional to its usual capacity.
==PROPRIETARY CODE: NO KANGING - NO COPYING OF CONTENT - LEGAL INFO HERE==
EAGLESBLOOD™ DEVELOPMENT PARTNERS:
[doniqcc | b0xer | cellsafemode]
..:::[ TEAM EB™]:::..
~THANK YOU TO EVERYONE WHO HAS DONATED AND SUPPORTED US~
Several Known Issues / Things Not Working:
Code:
*Audio doesn't work
*Data tends to cut off at times. A "hot-reboot" usually fixes it and this is due to audio not working.
*Phone will not enter 'Sleep Mode', again due to audio malfunctioning.
*Mobile Data Network: Data IS working, but you might need to cause the phone to hot-reboot (...easiest way is by connecting to non-encrypted network, which in turn usually fails.) It's due to a SIM-card thing...
*On cold-boot the SIM card status is not correct.
AGAIN, SOME STUFF NOT WORKING - THIS IS A SNEAK PEEK -> NO COMPLAINTS, or BUGS, or EMAILS OR ANYTHING SIMILAR THAT GIVES US THE FEELING YOU DONT LIKE IT. -
CHANGELOG:
====Build# Aa====
Pre-Alpha testing release.
Click to expand...
Click to collapse
=======================================
IMPORTANT NOTES:
=======================================
This distribution is still in development phase.
=======================================
SOURCE CODE:
=======================================
http://github.com/***
=======================================
KERNEL SOURCE REPO:
=======================================
http://kernel.eaglesblood.com
========================================
EAGLESBLOOD™ ROM INSTALL INSTRUCTIONS:
========================================
**IMPORTANT** MUST READ CAREFULLY AND FOLLOW COMPLETELY.
1. Make a full backup of your current ROM. Then copy it over to PC if you wish.
2. Reboot into ClockworkMod Recovery (CWM). *Note* You should always flash CWM using a USB Cable and NVflash; do not 'flash CWM from the ROM Manager app'.
3. To begin start by clicking "Wipe User Data/Factory Reset", this will wipe all data off of the phone's memory (not SD card though).
4. Now click "Wipe cache partition".
5. Then go down to "Advanced > Wipe Dalvik cache".
6. Choose Install zip from "External SD Card". Wait for that to complete and confirm you see an "Installation Complete" message.
7. Now, you must flash the correct Google Apps - GAPPS JB (gapps-2012xxxx.zip) ...link below.
Once the gapps are installed you can now click "Reboot System". Failing to complete all of these instructions precisely can potentially leave you stuck in CWM Recovery until you manage to build your way back out. This is not fun, trust us.
9. Done. Enjoy your new ROM!
Click to expand...
Click to collapse
DOWNLOAD ROM & GAPPS BELOW (then to Downloads tab.)
Like our ROM? Feel free to show your support by rockin' this free public forum signature! Just copy the code below and paste in your signature settings...
FREE FAN/USER SIGNATURE:
TO GET IT, COPY THIS CODE IN THE BOX:
HTML:
[URL=http://www.eaglesblood.com][IMG]http://img855.imageshack.us/img855/5981/ebusersig500x40.png[/IMG][URL]
________
TEAM EB™
FAST. STABLE. CLEAN.
--reserved for me later--
Thanks guys!!
much appreciated!
Hey a quick question... Does that mean that when we will have official ICS or drivers we might get a fully functional Jelly bean?
papa.khan123 said:
Thanks guys!!
much appreciated!
Hey a quick question... Does that mean that when we will have official ICS or drivers we might get a fully functional Jelly bean?
Click to expand...
Click to collapse
It should if a phone can operate ICS then it should. Galaxy nexus had ICS and now it has JB.
Sent from my LG-P999 using xda premium
LostInNorth805 said:
It should if a phone can operate ICS then it should. Galaxy nexus had ICS and now it has JB.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
But I think Nexus got the official update from Samsung.
In our case however, we can hardly expect ICS from LG let alone JB.
So I do hope once we have ICS (fingers crossed) the devs here would be able to make a fully functional JB out of it.
The reason I am asking it because the recently we saw the Google now app ported to ICS but they couldn't get the talk back to work, as I read somewhere it was JB kernel specific.
Possible audio fix
Hey EaglesBlood team,
This is great, and you guys are awesome. You might find this helpful for fixing audio
http://forum.xda-developers.com/showthread.php?t=1783993
According to the OP this is a universal fix, not device specific.
Thanks again, keep up the great work and good luck :good:
Or http://forum.xda-developers.com/showthread.php?p=29021522
for audio fix?
Edit: Oh wait that's based off CM10...
Sent from my LG-P999 using Tapatalk 2
I'm taking that you can use twrp as well to flash this
edit: Great work, very snappy, i dont really like the aroma installer. hard to press items. i noticed:
kineto.apk fcs [wifi calling],
camera doesn't work [i know its pre-alpha, just pointing it out],
Does not read external sd card
Two google music apps [music and google music]
Google Now/ Voice Search Fcs
Flashed back to paranoidandroid rom, will keep a eye out for this
Sent from my LG-P999 using Tapatalk 2
This is an exciting start! Thank you devs! Cant wait for it to be out of pre-alpha
Sent from my LG-P999 using xda app-developers app
Just a question, does project butter work on this? Thanks for the rom btw
Sent from my Galaxy Nexus using xda premium
papa.khan123 said:
Thanks guys!!
much appreciated!
Hey a quick question... Does that mean that when we will have official ICS or drivers we might get a fully functional Jelly bean?
Click to expand...
Click to collapse
if we get the drivers most likely
jj_z1 said:
Hey EaglesBlood team,
This is great, and you guys are awesome. You might find this helpful for fixing audio
http://forum.xda-developers.com/showthread.php?t=1783993
According to the OP this is a universal fix, not device specific.
Thanks again, keep up the great work and good luck :good:
Click to expand...
Click to collapse
It helped us to know that we weren't putting out media_codex_xml but audio still no go after pushing it to etc directory.
djvoleur said:
Or http://forum.xda-developers.com/showthread.php?p=29021522
for audio fix?
Edit: Oh wait that's based off CM10...
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
You guys are more then welcome to try em out and let us know.
ayysir said:
I'm taking that you can use twrp as well to flash this
edit: Great work, very snappy, i dont really like the aroma installer. hard to press items. i noticed:
kineto.apk fcs [wifi calling],
camera doesn't work [i know its pre-alpha, just pointing it out],
Does not read external sd card
Two google music apps [music and google music]
Google Now/ Voice Search Fcs
Flashed back to paranoidandroid rom, will keep a eye out for this
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Should be able to use Twrp
Kineto.apk not a priority at this point
Camera doesn't work cause of the SD card
There's 2 music apk cause 1 gets flashed with gapps
Google now/voice search audio related
We might consider removing aroma in the feature.
Thanks for the feedbacks
dexterb said:
Thank you...
Click to expand...
Click to collapse
huy_gm said:
Just want to thank u.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
AndroidKills said:
This is an exciting start! Thank you devs! Cant wait for it to be out of pre-alpha
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
You all welcome
I was getting scared about 4.1 Jelly Bean! With no word from Ricardo but ah you're doing well it looks great!
Do the camera's work? No mention of camera's and the HAL has had alot of work since 4.0.x just interested be good to know, since I'm not flashing until the other major bugs are gone.
Also I don't see why Wi-Fi calling isn't an extra flashable zip I always have to uninstall it as its no use to me.
BTW when you get to your releases that are for me at least very heavily skinned will there be a way to de-skin it cause that's what puts me off about eagles blood and Hellfire roms .....
Finally will I be able to use my internal storage as an SD card at some point since my SD card reader is physically broken so otherwise my phones crippled without that ability
Cheers sorry for the moaning just questions
Thank you EB. No camera no WiFi no audio no Google search and no SD card detection. Lightning fast
Sent from my LG-P999 using xda app-developers app
The OG optimus Has gotten a working JB port, interesting right?? But seriously, I got sound working to an a certain point using Cm10 sources and merging them in EB, I can hear ppl but they can't hear me only on speaker phone tho, weird, I got ringtones going for me also, but I doubt this well be interesting to EB as they build from source, So I don't think I can share
Sent from my Nexus 7 cus I'm sleeping with a Bear
Awesome work guys, I claimed an article on this thread, let's see if I can finally get you guys on the portal. Everyone else, it's been pretty clean and refreshing around here and lot of the trouble makers have died, or moved on. We don't need or want any replacement smart asses. Also, I talked to Ricardo earlier at length and he now says lg is having problems with Nvidia, what I mean by this is that lg is experiencing the same thing we are. They are ready and wanting to release ics and drivers, but Nvidia is being Nvidia. We might not get drivers after all. Thanks for the thread space guys, back on topic, I noticed reboots when trying to connect wifi.
[email protected]
mustangtim49 said:
Aw man, we're not gonna need me to step in are we? Jk. Awesome work guys, I claimed an article on this thread, let's see if I can finally get you guys on the portal. Everyone else, it's been pretty clean and refreshing around here and lot of the trouble makers have died, or moved on. We don't need or want any replacement smart asses. Also, I talked to Ricardo earlier at length and he now says lg is having problems with Nvidia, what I mean by this is that lg is experiencing the same thing we are. They are ready and wanting to release ics and drivers, but Nvidia is being Nvidia. We might not get drivers after all. Thanks for the thread space guys, back on topic, I noticed reboots when trying to connect wifi.
[email protected]
Click to expand...
Click to collapse
Wow sorry to hear that, looks like I'll be selling my G2x after all, there is no hope 4 the old lady now
Sent from my T-Mobile Galaxy SIII using Tapatalk 2 cause I'm out kidnapping Devs
Wow its been a while since i flashed anything on the old g2x(got the GS3) but I am glad to see Don still being Don, this should be fun. Keep up the great work Team EB, Talent is def. in your blood. lolz
Have you tried some of the ics fixes? On builds I've done from source I have audio working but have issues with launcher (stock) constantly fc. Also camera (pics only) fc.
Sent from my LG-P999 using xda premium
Android and licences, 101
Kernel: GPLv2 = must make source available on request when distributing a binary, on XDA we consider posting a rom a request for source code, you normally get a few days.
ROM/recovery/most other bits and bobs google wrote/used from elsewhere: Mostly under the apache or BSD licenses, this means that as long as you GIVE CREDIT to whoever's code you are using, you are free to use the code without giving out source.
This means they are within their rights to not give out source for the OS.
So now lets get back on topic and stop flaming, I had to spend another 15min cleaning up this mess rather than sleeping, so thanks for that.
veyka said:
Android and licences, 101
Kernel: GPLv2 = must make source available on request when distributing a binary, on XDA we consider posting a rom a request for source code, you normally get a few days.
ROM/recovery/most other bits and bobs google wrote/used from elsewhere: Mostly under the apache or BSD licenses, this means that as long as you GIVE CREDIT to whoever's code you are using, you are free to use the code without giving out source.
This means they are within their rights to not give out source for the OS.
So now lets get back on topic and stop flaming, I had to spend another 15min cleaning up this mess rather than sleeping, so thanks for that.
Click to expand...
Click to collapse
THANK YOU for this. So many users should learn about this...noobs I say...noobs...
Just a simple question. is this the update for the new radio and such? Or is it just a fake message? I'm rooted and read up on the new update but was just curious is all
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Apple pwner using xda premium
It's probably just for the ROM.
That is correct its Sense 3.0 update
Sent from my HTC PH39100 using xda premium
toxicpaulution said:
Just a simple question. is this the update for the new radio and such? Or is it just a fake message? I'm rooted and read up on the new update but was just curious is all
Sent from my Apple pwner using xda premium
Click to expand...
Click to collapse
It's legit. That's the message my wife got on her phone that updated her to the new Rom with sense 3.0. She's not s-off though so she was able to install it. I rooted it for myself to use and I must say it's probably the smoothest gingerbread experience for our phones since all the custom roms are built on dhd base or our buggy gingerbread update.
Okay I'm not a sense fan and still on absolution 3.7 imo its the best rom for our phones but I just was making sure... I think my phones being duped(hacked) so I can't really say if the texts I'm getting are correct or just fakes lol. XD I have traces set up and such in my phone to see if I'm getting mixed stuff xD but thanks guys
Sent from my Apple pwner using xda premium
What did you use to root and could you post instructions to root the new ROM from AT&
Gizmoe said:
It's legit. That's the message my wife got on her phone that updated her to the new Rom with sense 3.0. She's not s-off though so she was able to install it. I rooted it for myself to use and I must say it's probably the smoothest gingerbread experience for our phones since all the custom roms are built on dhd base or our buggy gingerbread update.
Click to expand...
Click to collapse
How did you root the update. I had rooted 2.3.3 and now I have 2.3.5 update from AT&T. Totoally removed everything back to square one. I used ACE kit before and it wanted to uninstall and take me back. I like the new ROM, better all around.
brett46373 said:
How did you root the update. I had rooted 2.3.3 and now I have 2.3.5 update from AT&T. Totoally removed everything back to square one. I used ACE kit before and it wanted to uninstall and take me back. I like the new ROM, better all around.
Click to expand...
Click to collapse
I use dsixda kitchen on ubuntu O.S. just look up dsixda's kitchen on xda if you are curious about how to develop roms.
Sent from my Inspire™ 4G using xda premium
Rooting new Inpire with 2.3.5
Gizmoe said:
I use dsixda kitchen on ubuntu O.S. just look up dsixda's kitchen on xda if you are curious about how to develop roms.
Sent from my Inspire™ 4G using xda premium
Click to expand...
Click to collapse
Thanks. I will be looking into your suggestion
I am a newbee no doubt to this world and an old man from Walla2 living in Chicago area now since 76. I will do as you have suggested....and check out the dsixda kitchen. I do develope, but it is on iSeries systems for back office. This has been fun as well as an eye opener what they do with smart phones.....wife has the iPhone 4s and hates it....but with 17mo left no doubt will convert her over to Android.
My wife got the notice for the update but the phone never connects to upgrade server. It's never been rooted.
Sent from my Galaxy S3 using xda app-developers app
Amon37 said:
My wife got the notice for the update but the phone never connects to upgrade server. It's never been rooted.
Sent from my Galaxy S3 using xda app-developers app
Click to expand...
Click to collapse
This happened a few times on my wifes phone before it actually updated. She never rooted either. Just keep trying once every 24 hours. It will start eventually.
Gizmoe said:
It's legit. That's the message my wife got on her phone that updated her to the new Rom with sense 3.0. She's not s-off though so she was able to install it. I rooted it for myself to use and I must say it's probably the smoothest gingerbread experience for our phones since all the custom roms are built on dhd base or our buggy gingerbread update.
Click to expand...
Click to collapse
I got that message this morning. I did the update. Now my phone won't stop resetting. Nothing works any longer. Please help if anyone can. I wish it was back to the way it was before the update.
mousepaws said:
I got that message this morning. I did the update. Now my phone won't stop resetting. Nothing works any longer. Please help if anyone can. I wish it was back to the way it was before the update.
Click to expand...
Click to collapse
It's normal to keep resetting a bunch during the upgrade. But if it finished and let you into Rom and is resetting then something went wrong. You aren't bricked though so I will tell you how to fix it. Just to be sure, I am assuming you are not s-off since the update actually ran. If you are s-off then just flash cwm through hack kit and install different Rom. If s-on do this. First from a pc download and install HTC sync and make sure it's running. Download the new ruu from HTC to your computer. Now take the battery out of phone. Put battery back making sure not to press the power on accident. Now with battery in hold volume down and tap power button while still holding volume down. You should enter hboot. Select fastboot and plug phone into pc. You will see fastboot USB on phone. Now from the pc run the ruu update and follow the prompts until finished. This will leave you at new stock with no data except what's on sd card.
mousepaws said:
I got that message this morning. I did the update. Now my phone won't stop resetting. Nothing works any longer. Please help if anyone can. I wish it was back to the way it was before the update.
Click to expand...
Click to collapse
It sounds like you have some app is conflicting. Figure out the exact app, and clear data for that.
ai6908 said:
It sounds like you have some app is conflicting. Figure out the exact app, and clear data for that.
Click to expand...
Click to collapse
An app doesn't cause the issues he is having. Apps force close themselves not the whole system. He can't even use the phone long enough to remove apps anyways.
Okay this is a fyi , i have been trying to do the AT&T update via WiFi all weekend, and got the the server busy message, so i tried again, same issue, then i turned on my data and WiFi , then i was able to download the update... it is down loading as we speak.
F2504x4 said:
Okay this is a fyi , i have been trying to do the AT&T update via WiFi all weekend, and got the the server busy message, so i tried again, same issue, then i turned on my data and WiFi , then i was able to download the update... it is down loading as we speak.
Click to expand...
Click to collapse
You have to be on WiFi for it to download. They took out the function of doing it over mobile network with the last Rom update. So if anyone else is having issues be sure WiFi is connected.
Gizmoe said:
You have to be on WiFi for it to download. They took out the function of doing it over mobile network with the last Rom update. So if anyone else is having issues be sure WiFi is connected.
Click to expand...
Click to collapse
Wow did you read what i stated ? The updated started after I also turned on my Data , I did have my WiFi on, but only got past the server busy notice after the DATA was turned on......
Gizmoe said:
With over 700 posts and only 20 thanks I think it speaks for itself. Your what I like to call a pseudo intellectual. Your really hung on your loosely based argument of what name calling means. Your a **** and I'm sure other people in your life think your a **** too. And yes I'll say it again, YOUR A ****! Now stop cluttering threads with your useless bull. No one thinks your cool and your mom hates you too. Lol.
Click to expand...
Click to collapse
oh hey there yeah this is my thread that I had posted. Ignorance was not what this was about, it was about a question with the update. It wasn't to be name calling or being ignorant. Also when you refer to someone its "you're" as in you are. Not your. So please take the ignorance and rude comments else where. You haven't answered the main question I had stated so you really shouldn't be posting your silly nonsense moderators you are allowed to close this I got my answer. Thank you in advance
Sent from my my device® using xda premium
Thread Closed
Thread closed at request of OP. Warning PM's forthcoming.
MD
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*If anyone in this thread helps you, please click their "thanks" button below!
Okay, so by my count we have at least fourteen (14!) threads about 'Did I brick my phone' or the like in our Q&A Section within the last few days, probably more in actuality. That's just ridiculous. Why we need a new thread every time someone thinks they have bricked their phone is just pointless, clutters up the forum, and isn't in line with the rules of this site. This is a prime example of members (mostly new ones) thinking it's proper protocol to start a new thread, regardless of having over a dozen others on the same topic. So, I'm opening this thread for some clarification on this, and for questions to be asked here if you have done something to your phone resulting in any kind of booting problem. If you feel like you have possibly bricked your phone (either hard bricked or soft bricked), it would be beneficial to start here for some definitive answers to your particular situation. Though we here on xda are willing to help others with their dilemmas, this site isn't necessarily for tech support to those who try to do something they have no clue as to what they're doing. Rooting/modding/upgrading/etc your phone won't help you woo the ladies, it won't win you any awards with your peers or co-workers, nor will it make your mother proud of you. Having an interest in this type of thing is great; but there are risks involved, and the potential to brick your device can always be present if you're not careful and do not follow the instructions exactly as they are given for what you are attempting.
Now then, allow me to give a run down of what is a soft bricked device:
If you're phone will not boot passed the Motorola splash screen = soft brick
If you your phone will only boot into AP Fastboot, and nothing else (AP Fastboot Flash Mode (S) (Flash Failure) 0A.68) = soft brick
If you can only manually boot into AP Fastboot (holding volume ↑ + ↓ + power buttons at the same time) = soft brick
Attempt to FXZ back to GB and get an error (step "_____" failed) and will not boot into Android, but only AP Fastboot = soft brick
If your phone will boot, but only as far as the Motorola splash screen, reboot, and continue = bootloop (super soft brick)
Okay, now on to what a hard bricked device is:
If your phone will not boot at all, no power, nothing but a white LED = hard brick
If your phone has none of the above = super hard brick
If your phone will not boot at all, and the battery gets very hot = hard brick
JTAG or RIFF boxes will not recognize the device if any of the above has been experienced -- please note this!
Now, if you have any of the above, please reply in this thread and we will try to see if we can pull you out of your "brickdom" -- assuming you are only soft bricked. If you are showing any of the above signs of being hard bricked, well, you're our of luck. You will need to try to contact Motorola for a warranty exchange (assuming your device is within the one [1] year warranty) or contact AT&T's 1-800 number (assuming this is your provider). Again, this thread is in hopes that we can keep all the "Plz Halp I Brickz My Fon" threads from popping up all over. You've either hard bricked your device or it's soft bricked/bootlooping, in the case of the latter we can help. If I've overlooked any of the above mentioned lists of "brick possibilities", please let me know and I will update the OP.
Great Post! Thanks for another great rundown!
I think this is sticky material.
I agree with Jim. This should definitely be stickied. Hopefully everyone will read this before posting the same questions repeatedly.
Great post Apex! Glad to see this.
Sent from my MB865 using xda premium
Might i suggest adding "ICS update failed","Can't fxz back to stock 2.3.x" (if it isn't much trouble) and links to already available solution threads,coz with the advent of the ICS OTA that is what has been cluttering up the forum lately.
Just a sincere thought...
But anyways great post...
Thanks Apex..
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
deveshmanish said:
Might i suggest adding "ICS update failed","Can't fxz back to stock 2.3.x" (if it isn't much trouble) coz with the advent of the ICS OTA that is what has been cluttering up the forum lately.
Just a sincere thought...
But anyways great thread idea...
Thanks Apex..
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
Click to expand...
Click to collapse
Good point, though I was thinking of keeping this one "brick only" and drawing up another for all the problems people are having updating to ICS. That to me seems like a whole other animal. But, this was something I just thought was somewhat overdue, and posted in an attempt to funnel all the bricked users here, rather than muddying up the forum. Thanks for the suggestion, I will put some thought into this. Oh, and I do have your PMs -- I've read them and will be getting back to you. My apologies for the delay thus far. I'll be on to address those things you brought up soon... :good:
Edit: We'll see how this all goes, and see who posts what. Perhaps it could encompass that problem as well. If it keeps the forum free of extraneous threads, I'd consider this successful!
Apex_Strider said:
Oh, and I do have your PMs -- I've read them and will be getting back to you. My apologies for the delay thus far. I'll be on to address those things you brought up soon... :good:
Click to expand...
Click to collapse
Lol well don't strain yourself too much see to them in your leisure time.Thanks
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
deveshmanish said:
Lol well don't strain yourself too much see to them in your leisure time.Thanks
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
Click to expand...
Click to collapse
I'm not neglecting you, just super busy after being away for the last week for work. I'll get back to you, I assure you of that!
Sent from my rooted Mayan Calendar running Mayanogenmod 10
Great work as always mate.
Some guys suggested stickying this. I understand the intent but unfortunately, stickying a thread seems to be the best way to ensure that the thread will not even be seen, let alone read. Regular and periodic bumping seems to work best.
PS: Apex, appreciate the work. See if you can add typical / common soft brick situations and the panacea, so that lot of people don't even have to post but may simply refer to this thread.
Bumping...
Sent from my rooted Mayan Calendar
I'd hoped that I would never need to post here but here I am. Actually, I'm posting on behalf of a friend.
My friend has the Indian A2 on stock gb and stock recovery - no bootstrap, etc. The phone was rooted and had busybox installed. My friend wanted to unroot and so tried to remove busybox using some busybox installation app from the market.
Now on rebooting, the phone doesn't get past the Motorola logo. The poor fellow is almost in tears
Hope the phone is not a paperweight. How can I set it right? Thanks in advance for the help.
athani said:
I'd hoped that I would never need to post here but here I am. Actually, I'm posting on behalf of a friend.
My friend has the Indian A2 on stock gb and stock recovery - no bootstrap, etc. The phone was rooted and had busybox installed. My friend wanted to unroot and so tried to remove busybox using some busybox installation app from the market.
Now on rebooting, the phone doesn't get past the Motorola logo. The poor fellow is almost in tears
Hope the phone is not a paperweight. How can I set it right? Thanks in advance for the help.
Click to expand...
Click to collapse
Man that should be updated in OP never uninstall busybox that way.I did the same thing and bootlooped from ICS Leak2.The return from where seems shady till now.
Anyhow since he was on gb just fxz back with the proper files and you should be fine.
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
deveshmanish said:
Man that should be updated in OP never uninstall busybox that way.I did the same thing and bootlooped from ICS Leak2.The return from where seems shady till now.
Anyhow since he was on gb just fxz back with the proper files and you should be fine.
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
Click to expand...
Click to collapse
Thanks. Good to know that I can resurrect the phone.
I've downloaded the file from the fxz thread. I've never used RSDLite before. Can someone please link me to some guide on how to use it.
athani said:
Thanks. Good to know that I can resurrect the phone.
I've downloaded the file from the fxz thread. I've never used RSDLite before. Can someone please link me to some guide on how to use it.
Click to expand...
Click to collapse
RSD Lite is fairly intuitive. But here's a guide I found that should help explain things fully: http://wiki.howardforums.com/index.php/How_to_flash_with_RSD_lite
Sent from my rooted Mayan Calendar
Apex_Strider said:
RSD Lite is fairly intuitive. But here's a guide I found that should help explain things fully: http://wiki.howardforums.com/index.php/How_to_flash_with_RSD_lite
Sent from my rooted Mayan Calendar
Click to expand...
Click to collapse
RSD lite 6.0 is out also. Thought I'd mention it since I haven't seen it posted anywhere.
RSD lite 6.0
https://hotfile.com/dl/174582400/60ad26d/RSDLite_6.0.rar.html
Mtk patch 20
https://hotfile.com/dl/174581768/b23cd63/MTK_Patch20_RSD_Lite_6.0).rar.html
Phew, got the phone up and running. I felt morally responsible as I'd rooted the phone for him just for fun
Thanks again to everyone who helped.
BTW, what's the correct way of removing busybox and unrooting?
mtnlion said:
RSD lite 6.0 is out also. Thought I'd mention it since I haven't seen it posted anywhere.
RSD lite 6.0
https://hotfile.com/dl/174582400/60ad26d/RSDLite_6.0.rar.html
Mtk patch 20
https://hotfile.com/dl/174581768/b23cd63/MTK_Patch20_RSD_Lite_6.0).rar.html
Click to expand...
Click to collapse
what is this Mtk patch??..what is it for???
devilhunter47 said:
what is this Mtk patch??..what is it for???
Click to expand...
Click to collapse
Nothing you need with phones like ours that use the ti omap family of processors. I really posted it more for devs.
athani said:
BTW, what's the correct way of removing busybox and unrooting?
Click to expand...
Click to collapse
Busybox is just a root privileged application, and can be uninstalled like any other: Settings>Apps>Mangage Apps> BusyBox Installer: Uninstall
I suppose un-rooting would depend on which rooting method you used. If it was the .bat file root method, you should have a 'click to unroot' .bat file that can be run to removed root...
apex_strider said:
busybox is just a root privileged application, and can be uninstalled like any other: Settings>apps>mangage apps> busybox installer: Uninstall
i suppose un-rooting would depend on which rooting method you used. If it was the .bat file root method, you should have a 'click to unroot' .bat file that can be run to removed root...
Click to expand...
Click to collapse
No, never ever ever uninstall busybox!!!! All you will remove by doing this is just remove the installer.apk. inside the apk you can actually uninstall busybox, but you will soft brick.
CONCERNING AT&T's Galaxy S4
So I looking thru the threads every ones frantic bout this bootloader stuff...
I'm Thinking what-de-do.
We playing smoke and mirrors here!
Dan the man has done the job, and if your already rooted, no problems....(Give him his props though)
ASK YOURSELF:
1. Are you rooted? If yes go to question #2
2. IS GooManager Installed? If yes go to Question #3
3. Can you find TWRP version 2.5.0.2 in GooManager for AT&T? If yes Install it! and Go to Question # 4
4. There is no question 4 your done!!!!
You have a custom Recovery bootloader!!!
Are you OK?
hair frizzing
akira02rex said:
Are you OK?
Click to expand...
Click to collapse
Look at my hair, do I look OK?
Bro...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:facepalm:
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
In before de lock
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Lol awesome
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
retard...sheeez
These are perfect instructions. Thanks for sharing.
iSaint said:
Bro...
Click to expand...
Click to collapse
OOPS....
TOO LATE!!!
Custom bootloader??? Nowhere in that process do you get a custom bootloader
But really though, Loki will suffice for now...and its incredible that Dan was able to find the exploit and utilize it...
But, we do still need to worry about bootloaders...for the sake of future s4 owners...sure we have something that works now, but what about the people who buy the phone a couple months from now? It's something that should always be looked into just for the Saks of future patches
I'm not bashing Dan here...take note I gave him a compliment...just trying to explain why some are still worrying about the bootloader - for us current owners nothing to worry about, its just the possibility that future owners may not be able to use this...
And yes, even future exploit may/will get patched...so its just a cat and mouse game were playing, hopefully att isn't going to get to into keeping the bootloader locked...and who knows, maybe they never will bother to patch Loki...only time will tell
Sent from my HTC PH39100 using Tapatalk 2
I have to say this thread was the most helpful thread for me
mg2195 said:
Custom bootloader??? Nowhere in that process do you get a custom bootloader
But really though, Loki will suffice for now...and its incredible that Dan was able to find the exploit and utilize it...
But, we do still need to worry about bootloaders...for the sake of future s4 owners...sure we have something that works now, but what about the people who buy the phone a couple months from now? It's something that should always be looked into just for the Saks of future patches
I'm not bashing Dan here...take note I gave him a compliment...just trying to explain why some are still worrying about the bootloader - for us current owners nothing to worry about, its just the possibility that future owners may not be able to use this...
And yes, even future exploit may/will get patched...so its just a cat and mouse game were playing, hopefully att isn't going to get to into keeping the bootloader locked...and who knows, maybe they never will bother to patch Loki...only time will tell
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Actually now that Dan has released the exploit and satisfied the masses, it seems like he is diving head first into a more solid bootloader solution. Along with the satisfying part, it seems to have stopped the idiots from posting in the R&D thread when they were not supposed to be, hindering development. Either way, as expected, development is taking off full force and a new exploit will be found in time. Hopefully before they patch the current one so when they do, we can just give carriers the bird and boot unlock the same day bwahahaha :laugh:
Well My Thoughts
mg2195 said:
Custom bootloader??? Nowhere in that process do you get a custom bootloader
But really though, Loki will suffice for now...and its incredible that Dan was able to find the exploit and utilize it...
But, we do still need to worry about bootloaders...for the sake of future s4 owners...sure we have something that works now, but what about the people who buy the phone a couple months from now? It's something that should always be looked into just for the Saks of future patches
I'm not bashing Dan here...take note I gave him a compliment...just trying to explain why some are still worrying about the bootloader - for us current owners nothing to worry about, its just the possibility that future owners may not be able to use this...
And yes, even future exploit may/will get patched...so its just a cat and mouse game were playing, hopefully att isn't going to get to into keeping the bootloader locked...and who knows, maybe they never will bother to patch Loki...only time will tell
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
The AT&T Guys as well as the Verizon Guys know that enough stuff goes wrong in the most normal times.. so in my humble opinion they can not lock these devices down where as the masses of company techs are unable to fix their own $hit such as resetting downgrading etc... The big companies have to fix their stock units, nuff said!! (remember thats just my opinion..)
Dude he's got a valid point. Thanks to Dan and numerous other devs who have Loki'd their work, I've got TWRP, a nandroid, and Faux's kernel. On a device with a locked bootloader. All in less than 24 hours since Dan released his exploit. That's incredible, and saying "thank you" just doesn't seem like enough.
As far as future S4 owners, the same badass peeps are working on a permanent unlock. People with lives besides XDA, and families too.
But in the meantime, if you've got an AT&T or Verizon S4 and you wanna flash stuff, you've got not a dang thing to complain about.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
TRUE DAT
Planktron said:
Dude he's got a valid point. Thanks to Dan and numerous other devs who have Loki'd their work, I've got TWRP, a nandroid, and Faux's kernel. On a device with a locked bootloader. All in less than 24 hours since Dan released his exploit. That's incredible, and saying "thank you" just doesn't seem like enough.
As far as future S4 owners, the same badass peeps are working on a permanent unlock. People with lives besides XDA, and families too.
But in the meantime, if you've got an AT&T or Verizon S4 and you wanna flash stuff, you've got not a dang thing to complain about.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Dan's the Man as in the first post... (you better believe, I've ponied up some funds)
:angel:
I'm just trying to understand.
I followed all the easy to follow instructions and had no issues.
What do I have now?
Is it that my bootloader is unlocked? I keep seeing "loki" mentioned everywhere.....
I'm coming from an s3. Once I had cmw I could flash roms.
Now on the s4 I have twrp. Can I flash roms at my leisure?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Tjisana said:
I'm just trying to understand.
I followed all the easy to follow instructions and had no issues.
What do I have now?
Is it that my bootloader is unlocked? I keep seeing "loki" mentioned everywhere.....
I'm coming from an s3. Once I had cmw I could flash roms.
Now on the s4 I have twrp. Can I flash roms at my leisure?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
If you have twrp, you can only flash roms with the loki patch. You may also flash a t-mobile rom without the loki patch as long as you also flash a loki patched kernel before rebooting.
I got approved for an upgrade from AT&T even though I got a Note 2 with an upgrade last November, they are even giving it to me for $174. However I will for sure be flashing AOSP on it, my concern is, once a new version of Android comes out, and new bootloaders are required(4.3, 5.0) what are we going to do then? If we want to run any future version of android that require new bootloaders we are kinda screwed. So not only are future buyers in jeopardy of not being able to run custom firmwares, the current user-base who can take advantage of Dan's exploit may not be able to update to future versions of Android unless they want to run stock Samsung TouchWiz.
Sent from my Tablet
Jonnyredcorn said:
I got approved for an upgrade from AT&T even though I got a Note 2 with an upgrade last November, they are even giving it to me for $174. However I will for sure be flashing AOSP on it, my concern is, once a new version of Android comes out, and new bootloaders are required(4.3, 5.0) what are we going to do then? If we want to run any future version of android that require new bootloaders we are kinda screwed. So not only are future buyers in jeopardy of not being able to run custom firmwares, the current user-base who can take advantage of Dan's exploit may not be able to update to future versions of Android unless they want to run stock Samsung TouchWiz.
Sent from my Tablet
Click to expand...
Click to collapse
Pretty sure we can odin back to factory firmware and apply MDL ota and then apply root/recovery and you're set :thumbup:
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2