I was just wondering if there is any active development or effort going towards getting a custom Recovery for D800s that are rooted with kitkat. I know that you can go back to stock jellybean and then re root and put back the old recovery and then flash away, but I've been holding off on attempting this assuming some talented developer would create a new custom Recovery sooner or later. If nobody is working on it then that's fine and I can use the former method, I would just like to know if me waiting is pointless or not.
Thank you
Sent from my LG-D800
sropedia said:
I was just wondering if there is any active development or effort going towards getting a custom Recovery for D800s that are rooted with kitkat. I know that you can go back to stock jellybean and then re root and put back the old recovery and then flash away, but I've been holding off on attempting this assuming some talented developer would create a new custom Recovery sooner or later. If nobody is working on it then that's fine and I can use the former method, I would just like to know if me waiting is pointless or not.
Thank you
Sent from my LG-D800
Click to expand...
Click to collapse
AutoRec the only ting to keep in mind is that if you are going to flash an aosp/4.2 rom you also got to flash a kk baseband ported for aosp or the jb baseband
Thank you! How would I go about finding one of those basbands?
Edit: when looking at the Mahdi ROM thread I noticed there is a device specific "patch" file that I'm supposed to flash a long with the ROM, is that what you were referring to?
Sent from my LG-D800
sropedia said:
Thank you! How would I go about finding one of those basbands?
Edit: when looking at the Mahdi ROM thread I noticed there is a device specific "patch" file that I'm supposed to flash a long with the ROM, is that what you were referring to?
Sent from my LG-D800
Click to expand...
Click to collapse
No the patches for some roms are because they support multiple devices and the patches are usually modified kernels to boot the different devices the baseband is for touch/gps/radio/rotation/etc there is a the w ad which has most of the jellybean basebands and cloudy has the stock kk basebands in most of his roms thread
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Related
Hey every1, I was wondering if there was a working stable way to root the VZW s3... I know a lot of devs have been working on it and I hear there coming out with an update to fix it, but for right now is there a way? I have sprint but the service isn't good where I live so I'd like to get Vrzn and be able to flash cm10, any input much appreciated
Thanks
Sent from my SPH-L710 using xda app-developers app
irish.iolar said:
Hey every1, I was wondering if there was a working stable way to root the VZW s3... I know a lot of devs have been working on it and I hear there coming out with an update to fix it, but for right now is there a way? I have sprint but the service isn't good where I live so I'd like to get Vrzn and be able to flash cm10, any input much appreciated
Thanks
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Rooting and the bootloader issue have virtually nothing to do with one another. Here's a copy/paste of something I wrote:
ExodusC said:
The Verizon (and pretty much every) Galaxy S3 has had root since virtually their release date.
The Verizon version does have a locked bootloader (see #3), and there is going to be a "Developer Edition" released directly from Samsung with pretty much no warranty, and it will be completely unsubsidized.
The bootloader lock has not stopped us from flashing custom ROMs or custom kernels. See below.
Here's some source links for you, in rough chronological order:
The "Root66" method for easily obtaining root
Original proof-of-concept showing custom kernels can be booted
Standard install of CyanogenMod 9 via kexec demonstrated
Functioning 3G/4G data on CyanogenMod 9 demonstrated
Unofficial guide to installing CyanogenMod 9
CVPCS states locked bootloader is a non-issue
Ongoing research & development on the locked bootloader
I could go on and on, but as you can see, development of custom ROMs (both TouchWiz and AOSP based) has not been hindered by the locked bootloader.
The community has pulled together on this, and developers from non-Verizon carriers have been tons of help in all the progress that has been made so far.
Many people, including myself, do not support the idea of the Developer Edition SGS3, and I personally doubt it will have even a tiny fraction of the community the consumer version has.
Click to expand...
Click to collapse
Thanks for the info, but what can't you do with the Verizon version?
Sent from my SPH-L710 using xda app-developers app
And if you can still root and flash roms from Verizon s3, why does it say like cyanogenmod is coming out for everything but Verizon bc it has a locked bootloader?
Sent from my SPH-L710 using xda app-developers app
Look at the development forms it will answer yourquestions and show you where the VZW development is going.
Sent from my SCH-I535 using xda app-developers app
In short a locked bootloader will prevent flashing custom kernel, hence why CM10 is not officially supported for VZW yet. It is possible to flash other ROMs and there are already a few different versions of the stock rom that have been stripped or debloated. Some people have also reported a workaround for flashing custom kernels but its a little more tedious. As far as rooting goes, you can do everything else that rooting entails (TB, tethering, etc.) just fine.
kthung said:
In short a locked bootloader will prevent flashing custom kernel, hence why CM10 is not officially supported for VZW yet. It is possible to flash other ROMs and there are already a few different versions of the stock rom that have been stripped or debloated. Some people have also reported a workaround for flashing custom kernels but its a little more tedious. As far as rooting goes, you can do everything else that rooting entails (TB, tethering, etc.) just fine.
Click to expand...
Click to collapse
What do you mean "reported?" Read my above post- we have an effective workaround for flashing custom kernels and ROMs.
All it requires is flashing a custom recovery (just like you'd do with any phone) and then simply flashing the custom ROM (just like you'd do with any phone).
The auto-kexec and custom kernel are built right into the .zip package.
Yes, it's not perfect, but assuming the CyanogenMod team is okay with the workaround, I don't see why we wouldn't get official support.
ExodusC said:
What do you mean "reported?" Read my above post- we have an effective workaround for flashing custom kernels and ROMs.
All it requires is flashing a custom recovery (just like you'd do with any phone) and then simply flashing the custom ROM (just like you'd do with any phone).
The auto-kexec and custom kernel are built right into the .zip package.
Yes, it's not perfect, but assuming the CyanogenMod team is okay with the workaround, I don't see why we wouldn't get official support.
Click to expand...
Click to collapse
thats right im even running CM10 (dealing with the regular issues before that rom hit RC status, but i love cyanogen so i can live with that, official could hit us soon
Hey XDA, I am not entirely new to this but not close to knowledgeable. Anyways, my simple question is, do I need to have 4.1.2 installed in order to flash the newest ROMs. I have 4.1.1 rooted but am afraid to flash any of these ROMs as they all say they are designed for 4.1.2. I avoided posting a thread but it seems I cannot find the answer ANYWHERE.
Well.. thanks in advanced! :laugh:
The 4.1.2 ROMs are built from the update, so they'll already have whatever is in it. You don't have to flash it separately. However, you may want to flash the 4.1.2 modem and rpm (may not be in the rom), which can be found in post 2 of the CleanROM 6 thread in Android Development.
SempaiMatt said:
The 4.1.2 ROMs are built from the update, so they'll already have whatever is in it. You don't have to flash it separately. However, you may want to flash the 4.1.2 modem and rpm (may not be in the rom), which can be found in post 2 of the CleanROM 6 thread in Android Development.
Click to expand...
Click to collapse
Sorry for my newbie self but are you suggesting I go ahead and flash whatever ROM I want ? I really just don't want to increase the risk of bricking my device. Again, my device is 4.1.1 and do not plan to update the firmware to 4.1.2. To be more specific, I am looking to flash SynergyROM VZW S3. All I need is the green light. Thanks again!
dannyboy951 said:
Sorry for my newbie self but are you suggesting I go ahead and flash whatever ROM I want ? I really just don't want to increase the risk of bricking my device. Again, my device is 4.1.1 and do not plan to update the firmware to 4.1.2. To be more specific, I am looking to flash SynergyROM VZW S3. All I need is the green light. Thanks again!
Click to expand...
Click to collapse
You will be fine flashing SynergyRom. You can downgrade, upgrade, stay in the same version. You won't brick you phone.
Watanuki-Kun said:
You will be fine flashing SynergyRom. You can downgrade, upgrade, stay in the same version. You won't brick you phone.
Click to expand...
Click to collapse
Sounds good! :good: I am finally going to go ahead and do what I've been hesitating to do for about a week now lol
There's always a chance for a brick. I have never bricked one of the three phones I have rooted. Just make sure you are flashing a rom made for the Verizon gs3, your bootloader is unlocked and you have backed up your imei. Those three things will greatly reduce your chances of a hard brick.
Sent from my SCH-I535 using xda app-developers app
Make sure you wipe your phone before flashing rims and such. It is NOT okay to just flash without wiping, and always backup your apps first with titanium backup. Just thought I'd let you know since you wanted to flash away for your first time.
Sent from my SCH-I535 using xda app-developers app
Im trying to update my TF300T to a jellybean rom and im a bit confused. im currently an AOSP ICS rom from when i first rooted this tablet but since i havent messed with it since them im a bit lost. i updated TWRP to the latest ics one and i tried installing Paranoid android and it just bootlooped. Luckily i backuped my rom. So can anyone point me in the right direction please? any help would be appreciated
First of all, since you're apparently both unlocked and still on the ICS bootloader, take some time to go through the NVFlash process here: http://forum.xda-developers.com/showthread.php?t=1894867
That will come in handy if you accidentally flash the wrong recovery later on (or do anything else that could brick your tablet). I'm sure you've seen the many "I bricked my TF300T" threads, so do yourself a favor, and do the NVFlash backup.
Now, once you've gotten the NVFlash out of the way (it's extremely important that you do the NVFlash backups first, because you can't go back and do them later), we can upgrade you to Jellybean. The easiest way, IMO, is to boot your tablet into fastboot, and flash the stock ASUS firmware (specifically, the first version of 10.x) that way. If you search the forum for "fastboot stock firmware", you should find at least a couple good guides on how to do that.
Once you're on the stock firmware, you can just update via the OTA method. Download the firmware you need (I suggest doing this incrementally, so get each individual update), unzip it, and put the resulting zip file on the root of either your external SD card or the internal storage (doesn't matter). If the tablet doesn't notify you of an update, just reboot. When you get the update notification, accept it, and it'll flash like a normal OTA. Just do this until you're up to date.
Keep in mind, if you go up to the 10.6.x.x firmware (Android 4.2), your only AOSP option will be a mostly-but-not-completely functional CM10.1. So, you may want to stay on the newest 4.1 firmware (10.4.2.20, I believe) until all the issues are ironed out.
Bloodykiller86 said:
Im trying to update my TF300T to a jellybean rom and im a bit confused. im currently an AOSP ICS rom from when i first rooted this tablet but since i havent messed with it since them im a bit lost. i updated TWRP to the latest ics one and i tried installing Paranoid android and it just bootlooped. Luckily i backuped my rom. So can anyone point me in the right direction please? any help would be appreciated
Click to expand...
Click to collapse
Can you access fastboot?
Alright awesome thanks that answered a bunch of my questions. And one more thing so since youre saying if I go to the latest update if be limited to just cm10, what about paranoid android rom in saw in dev section. Would that work on the 4.1 update? Or do I have to go to 4.2 to use that rom? I know it's not really a help question per she but just wanna make sure I don't waste any time lol
Sent from my Nexus 4 using xda app-developers app
Bloodykiller86 said:
Alright awesome thanks that answered a bunch of my questions. And one more thing so since youre saying if I go to the latest update if be limited to just cm10, what about paranoid android rom in saw in dev section. Would that work on the 4.1 update? Or do I have to go to 4.2 to use that rom? I know it's not really a help question per she but just wanna make sure I don't waste any time lol
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Almost every AOSP ROM, including the official CM10.1, requires the 4.1 bootloader. They are stable. The CM for the 4.2 bootloader is in testing stages still, but I believe that the only thing that's broken now is the camera. Regardless, stick to the 4.1 OTA for now if you want a wide selection of AOSP ROMs.
EndlessDissent said:
Almost every AOSP ROM, including the official CM10.1, requires the 4.1 bootloader. They are stable. The CM for the 4.2 bootloader is in testing stages still, but I believe that the only thing that's broken now is the camera. Regardless, stick to the 4.1 OTA for now if you want a wide selection of AOSP ROMs.
Click to expand...
Click to collapse
Okay awesome thanks guys you helped me out a lot. Now to make this tablet run awesome cuz on ics it sucks especially with the rotation bug lol
Sent from my Nexus 4 using xda app-developers app
So I'm trying to do the nvflash but when I do the first fast boot command it just sits at waiting for device ugh -_-
Sent from my Nexus 4 using xda app-developers app
And it sees the fast boot driver in device manager so its not like its not seeing it but ugh.....any ideas? Should I update to the latest ICS update from Asus?
Sent from my Nexus 4 using xda app-developers app
It wouldn't hurt. Also make sure you're using the newest version of fastboot.
Where can I get it? Just update the one from android SDK?
Edit: nvm duh from SDK lol and I upgraded to latest ICS image and it worked! Thanks again
Sent from my Nexus 4 using xda app-developers app
Hi all, been reading the threads and have 'info overload' :silly: from so many different options. Just looking to get stock OS with root, and the latest update (mf1 I believe) so I can have stable 4g and the latest OS updates. Locked or unlocked BL does not matter. I do have Triangle away just in case it is needed.
In the past I went straight to mf1 and then did the 1 click Casual root. All was good except I had no 4g, even when everyone around me did. So I'm thinking of going to COMBINATION_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship.tar.zip and starting over.
Should I do ota's to get to mf1, or root first, install a root keeper app, and then upgrade.
Thank you all in advance for any advice you can provide. I tried searching on my own first but there is so much info out there.
-Ry
ryokox3 said:
Hi all, been reading the threads and have 'info overload' :silly: from so many different options. Just looking to get stock OS with root, and the latest update (mf1 I believe) so I can have stable 4g and the latest OS updates. Locked or unlocked BL does not matter. I do have Triangle away just in case it is needed.
In the past I went straight to mf1 and then did the 1 click Casual root. All was good except I had no 4g, even when everyone around me did. So I'm thinking of going to COMBINATION_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship.tar.zip and starting over.
Should I do ota's to get to mf1, or root first, install a root keeper app, and then upgrade.
Thank you all in advance for any advice you can provide. I tried searching on my own first but there is so much info out there.
-Ry
Click to expand...
Click to collapse
You can just update then root as it requires less steps.
Root first. Then from the development section download the new ROM and modem which is separate and flash away. That's what I've been running with the KT747 kernel but others like the LK 3 kernel, so it's up to you whichever you prefer
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
Root first. Then from the development section download the new ROM and modem which is separate and flash away. That's what I've been running with the KT747 kernel but others like the LK 3 kernel, so it's up to you whichever you prefer
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Honestly not familiar with the kernels. Like I said Just want stock os with root and an actually working LTE this time.
jmxc23, I do like your solution but last time I lost 4g lte doing that. Maybe another try will do it
ryokox3 said:
Honestly not familiar with the kernels. Like I said Just want stock os with root and an actually working LTE this time.
jmxc23, I do like your solution but last time I lost 4g lte doing that. Maybe another try will do it
Click to expand...
Click to collapse
To fix the lost LTE flash the rooted ota rom here: http://forum.xda-developers.com/showthread.php?t=2332840
jmxc23 said:
To fix the lost LTE flash the rooted ota rom here: http://forum.xda-developers.com/showthread.php?t=2332840
Click to expand...
Click to collapse
Thank you Jmxf23.
ryokox3 said:
Thank you Jmxf23.
Click to expand...
Click to collapse
No problem.
I used the method in this thread to gain root:
http://forum.xda-developers.com/showthread.php?t=1984436
It flashes a rooted stock rom (MB1) via Odin. Then used Voodoo OTA Rootkeeper and took the OTA to MF1. Then restore root. 100% stock Rom + Root. I've had zero issues so far. Don't have to mess with flashing kernel, modem, and it doesn't trip the flash counter.
Sent from my SCH-I535 using xda app-developers app
Ok, so I'm no stranger to modding and XDA but every phone I've always had I always flashed custom Roms immediately so I'm not sure how it works on stocks. I'm rooted with unlocked bootloader on the stock ROM with Franco's kernel. Can I install system updates or is it best to do that on stock kernel and does being rooted with unlocked boot loader affect it? Thanks for any help.
Sent from my One using xda premium
The OTA should contain the stock kernel, so you would just need to flash the custom one afterwards. I'm not 100% sure, but I don't see why it should be different from what I said...
bradipovsky said:
The OTA should contain the stock kernel, so you would just need to flash the custom one afterwards. I'm not 100% sure, but I don't see why it should be different from what I said...
Click to expand...
Click to collapse
I'm on a custom kernel now, wasn't sure if I can do an ota on a custom kernel or not.
Sent from my One using xda premium
C-4Nati said:
I'm on a custom kernel now, wasn't sure if I can do an ota on a custom kernel or not.
Sent from my One using xda premium
Click to expand...
Click to collapse
Sorry, I wasn't clear: most likely the OTA itself contains the stock kernel, therefore it installs it instead of whatever you already have. After the OTA you should just have to (re-)flash your custom one back and be good to go.
C-4Nati said:
I'm on a custom kernel now, wasn't sure if I can do an ota on a custom kernel or not.
Sent from my One using xda premium
Click to expand...
Click to collapse
worse case scenario you can flash an update zip but like previously mentioned the kernel is not what generally causes the issue but the recovery. I do not think you will have an issue but hey there are some nice custom roms out there with options give one a shot. Just nandroid you current setup
Remember custom roms are running 4.4.4
playya said:
worse case scenario you can flash an update zip but like previously mentioned the kernel is not what generally causes the issue but the recovery. I do not think you will have an issue but hey there are some nice custom roms out there with options give one a shot. Just nandroid you current setup
Remember custom roms are running 4.4.4
Click to expand...
Click to collapse
Yeah I know, I always use custom Roms cause I generally have phones that have some OEM ui plastered on so since this is already close to stock I'm going to ride it out and see how CM does updating for a bit. Especially since they promised L within 3 months after it's release.
Sent from my One using xda premium
C-4Nati said:
Yeah I know, I always use custom Roms cause I generally have phones that have some OEM ui plastered on so since this is already close to stock I'm going to ride it out and see how CM does updating for a bit. Especially since they promised L within 3 months after it's release.
Sent from my One using xda premium
Click to expand...
Click to collapse
I hear ya but they working on a Android L rom in development now just so you know... I ran the version for my N4 and it is a lovely OS :good: