Related
The boot ROM is different from the bootloader. It is immutable code etched into the silicon that initializes everything, including the first stage bootloaders. Locked bootloaders mean nothing if they are not signature checked by some sort of hardware-based process to block the use of patched bootloaders. What tablets or smartphones come without this hardware-based security enabled?
Anyone?
Sent from my DROID2 GLOBAL using XDA App
Anyone at all?
Sent from my DROID2 GLOBAL using XDA App
Really, anybody?
Sent from my DROID2 GLOBAL using XDA App
Is it true that CWM is not good for flashing roms? Im using CWM and was wondering how to switch?
Sent from my ST25a using xda app-developers app
It works perfectly fine. There are simply alternatives, if one was made for your device.
AFAIK, CWM's only problem is interface. TWRP is full touch but is not widely supported like CWM
Sent from my DROID2 using xda premium
Not widely supported means not many people uses it right ?
Sent from my ST25a using xda app-developers app
It means that some of the lesser known ROMs may not work on it.
I've always used CWM and never had a problem at all with it
KidCarter93 said:
It means that some of the lesser known ROMs may not work on it.
I've always used CWM and never had a problem at all with it
Click to expand...
Click to collapse
That's true too, although what I meant is that TWRP is not available for as many devices as CWM is (official and unofficial)
Sent from my DROID2 using xda premium
gagdude said:
That's true too, although what I meant is that TWRP is not available for as many devices as CWM is (official and unofficial)
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
I knew that
I see thanks! But if I want to change from CWM to twrp, how do I do it?
Sent from my ST25a using xda app-developers app
Tamaskan said:
I see thanks! But if I want to change from CWM to twrp, how do I do it?
Sent from my ST25a using xda app-developers app
Click to expand...
Click to collapse
Google "TWRP <device name>" and see if it is available. If it is, just follow the directions on the thread.
Flashing recoveries varies by device. The less supported overall it is, the harder it is to get a recovery on it.
Example: my Motorola Cliq, Droid, and LG Ally had official CWM, so I could just download the official app (rom manager) and tap flash recovery. My Flipside did not have official support, so I had to download a 3rd party app meant for the Flipout (which happen to have similar hardware so some stuff was interchangeable) and tap flash recovery. For my LG mytouch I had to use ADB, and later someone in the thread found a way to flash via terminal emulator commands (I ultimately ended up bricking my Mytouch, though... whatevs)
@kidcarter93 lol, OK (sorry I was too lazy to quote)
Sent from my DROID2 using xda premium
I've actually got the twrp recovery already, coz when i root my device i had 2options using twrp or cwm kinda choose cwm xD
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
So recently I've been trying to compile a 4.4 compatible TWRP for our device, but somehow, this time around, it turned into a CWM. I had all my TWRP flags in the right position, but I digress.
I am proud to present to you CWM 6.0.4.5 touch and non touch for the Samsung Galaxy S Blaze.
The following link contains both builds. The non touch was compiled from source while the touch recovery was compiled through Koushes Recovery Builder.
THIS IS FOR 4.4 ROMS ONLY. I CLAIM NO RESPONSIBILITY FOR ANY DAMAGES THAT MAY OCCUR IF YOU CHOOSE TO USE IT OTHERWISE.
http://www.mediafire.com/?cf3f5501425de
I'll perform some maintenance on the thread a little later, but until then...
ENJOI
(Hopefully one day I'll have the twrp for you guys.)
Sweet! I've been waiting for a touch version! Checking it out now!
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Let me know
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Excellent -- thanks for the efforts Sky!
If you want twrp you need to pull Omni's bootable_recovery, unzip it and replace it with the cm recovery in /bootable/recovery.
From there make the general builds.
I've been trying to get this working for weeks as the mounts don't seem to work right. That's why omni is being delayed.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Works great so far. Only minor issue is that the font is a little too big to display the full description in the "install zip" menu but it's no big deal since I already know the order they appear in (sdcard0 then sdcard1). Thanks Skywalker!
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Somcom3X said:
If you want twrp you need to pull Omni's bootable_recovery, unzip it and replace it with the cm recovery in /bootable/recovery.
From there make the general builds.
I've been trying to get this working for weeks as the mounts don't seem to work right. That's why omni is being delayed.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Is that what the problem is? Cause I replaced said file and no matter what I do... Yea.. Nothing mounts properly except for external SD and data. Other than that, nothing.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Skywalker.00 said:
Is that what the problem is? Cause I replaced said file and no matter what I do... Yea.. Nothing mounts properly except for external SD and data. Other than that, nothing.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I'm at the same place. Dunno why they aren't working. Changing the internal Mount breaks the external.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
A guy on the tab 2 forum got his working flawlessly. I pm'd him to see how he got his working, tried his fixes but it was a no go. Unfortunately it takes me two and a half hours to compile one recovery image on my work computer. Needless to say troubleshooting is a real pain in my arse.
Sent from my GT-P3110 using xda app-developers app
Skywalker.00 said:
A guy on the tab 2 forum got his working flawlessly. I pm'd him to see how he got his working, tried his fixes but it was a no go. Unfortunately it takes me two and a half hours to compile one recovery image on my work computer. Needless to say troubleshooting is a real pain in my arse.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
What kind of computer.
Make sure ccache is up it can shorten your build time dramatically.
I tripped my Odin counter 32 times trying to make it work.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
I'm at the same place. Dunno why they aren't working. Changing the internal Mount breaks the external.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Did you try this flag? It looked promising, but with my ridiculous build times I haven't gotten around to it yet.
ignoreblkid -- blkid is used to determine what file system is in use by TWRP, this flag will cause TWRP to skip/ignore the results of blkid and use the file system specified in the fstab only
Sent from my GT-P3110 using xda app-developers app
Somcom3X said:
What kind of computer.
Make sure ccache is up it can shorten your build time dramatically.
I tripped my Odin counter 32 times trying to make it work.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
I'm only at fifteen or so... Maybe 20... derp
Oracle virtual box, Ubuntu 12.04. I was only able to allocate 2 gigs of RAM, which I know is not nearly enough, but i gotta work with what ive got. For now. I've known about ccache and thought to set it up, but I never got around to it... Don't know why I never did..? Smh.
Sent from my GT-P3110 using xda app-developers app
I know how to use adb and I'm not too inexperienced with it. Is there a way that I could push files to the system partition without having root on the device? I'm on stock ROM and I do not want to unlock the boot loader or root it, I just need to push a file to the system partition.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I am pretty sure you can only push files to the SD card without root. Rooting/ unlocking doesn't hurt. Try helium for a backup.
I know it doesn't hurt, I just came back to the stock ROM after using my own compiled ROM. I just didn't want to mod it except that one file, thanks though
Sent from my Nexus 5 using XDA Premium 4 mobile app
You should be able to do it in custom recovery
Sent from my Nexus 5
Am I able to boot into one without flashing it while my bootloader is locked? I do not want to unlock my bootloader
Sent from my Nexus 5 using XDA Premium 4 mobile app
Not without unlocking your bootloader.
Sent from my Nexus 5 using Tapatalk
Okay, if I decide to unlock, I can use adb to backup my data partition before the unlock and then restore it after I unlock right?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hmmm. Not sure if you can access /data without root via adb. Helium backs everything up so maybe it can. Try it. Im never unrooted enough to know
Sent from my Nexus 5 using Tapatalk
Sparx639 said:
Okay, if I decide to unlock, I can use adb to backup my data partition before the unlock and then restore it after I unlock right?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here's a good guide to use when performing an adb backup. No you do not need root.
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Sent from my Nexus 7 using Tapatalk
El Daddy said:
Here's a good guide to use when performing an adb backup. No you do not need root.
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks! I was actually reading this not long ago, I plan do do it soon
Sent from my Nexus 5 using XDA Premium 4 mobile app
Nice. Here is the official link:
https://developers.google.com/android/images
Let's find what's new.
Sent from my crosshatch using XDA Labs
Here is the changelog
Sent from my crosshatch using XDA Labs
lollyjay said:
Here is the changelog
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
dope... hopefully this answers a lot of our concerns.
-w to flash.all without losing anything right?
And then twrp and re-root?
masri1987 said:
dope... hopefully this answers a lot of our concerns.
-w to flash.all without losing anything right?
And then twrp and re-root?
Click to expand...
Click to collapse
Yes to all.
Just fyi after I rebooted twrp I had no touch response. I was happy to learn that flashing custom kernel fixed the touch issue with TWRP
Sent from my crosshatch using XDA Labs
If I downloaded the ota and have full twrp installed, the proper way of installing is to sideload through twrp correct?
Drewski_1987 said:
If I downloaded the ota and have full twrp installed, the proper way of installing is to sideload through twrp correct?
Click to expand...
Click to collapse
I have not tested it with the OTA sorry
Sent from my crosshatch using XDA Labs
lollyjay said:
Here is the changelog
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
No fix for the bottom speaker.
swieder711 said:
No fix for the bottom speaker.
Click to expand...
Click to collapse
wasn't aware there was an issue for bottom speaker??
swieder711 said:
No fix for the bottom speaker.
Click to expand...
Click to collapse
I have no issues with the speakers after this update.
Sent from my crosshatch using XDA Labs
Drewski_1987 said:
If I downloaded the ota and have full twrp installed, the proper way of installing is to sideload through twrp correct?
Click to expand...
Click to collapse
No you need the stock recovery for sideloading the ota.
lollyjay said:
I have no issues with the speakers after this update.
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Did you have an issue with the speaker before this update?
swieder711 said:
Did you have an issue with the speaker before this update?
Click to expand...
Click to collapse
No. I think it is not firmware related. Perhaps a quality problem?
Sent from my crosshatch using XDA Labs
lollyjay said:
Yes to all.
Just fyi after I rebooted twrp I had no touch response. I was happy to learn that flashing custom kernel fixed the touch issue with TWRP
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
wait, i have to remove the -w to prevent the wipe correct?
masri1987 said:
wait, i have to remove the -w to prevent the wipe correct?
Click to expand...
Click to collapse
Ya tru dat ?
Sent from my crosshatch using XDA Labs
lollyjay said:
Yes to all.
Just fyi after I rebooted twrp I had no touch response. I was happy to learn that flashing custom kernel fixed the touch issue with TWRP
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Same. TWRP was unresponsive. Booted into TWRP using the boot image and fastboot command. Then flashed custom kernel + Magisk and now all is working as it should.
anyone notice any difference from Nov?
considering doing a full wipe after work, as i dont believe in dirty flashing
virtyx said:
anyone notice any difference from Nov?
considering doing a full wipe after work, as i dont believe in dirty flashing
Click to expand...
Click to collapse
Very minor differences.
Free memory is a little greater
Seems smoother
One disappointment is System theme still not working
Sent from my crosshatch using XDA Labs
Can someone please give the steps to update.
Sent from my Pixel 3 XL using Tapatalk
chakra said:
Can someone please give the steps to update.
Click to expand...
Click to collapse
Depends on so many things.
If you are stock, then you can just flash the OTA
If you have twrp and magisk, then you can fastboot flash
So many possibilities
Sent from my crosshatch using XDA Labs