Database Users

[Q] CM10.1 and Locked Bootloader

I stupidly accepted the latest 78 update and am now stuck with a locked bootloader. I'm working on rooting my phone now (thanks to the guys @ http://forum.xda-developers.com/showthread.php?t=2379833) but am left with a question... can I load a custom ROM, say CM10.1, with just root?
Is there any utility out there to unlock the bootloader, or a way for me to downgrade from the current baseband I'm at now?
Thanks.

No. You need to be unlocked so you can install a custom recovery. That being said, you may be able to unlock the bootloader if you can root it.
Sent from my Nexus 7 using Tapatalk 4 Beta

http://forum.xda-developers.com/showthread.php?t=2379833

I did get the phone eventually rooted. I found an old thread that showed how you can use SafeStrap (basically a wrapper around the original stock ROM) to install other custom ROMs with... is this a safe bet? I still have a locked bootloader as I took the new update... tried motopocalypse and it came up with the error code -11.

sheppardzwc said:
I did get the phone eventually rooted. I found an old thread that showed how you can use SafeStrap (basically a wrapper around the original stock ROM) to install other custom ROMs with... is this a safe bet? I still have a locked bootloader as I took the new update... tried motopocalypse and it came up with the error code -11.
Click to expand...
Click to collapse
The thing about Safestrap is it don't flash the kernel when you try to flash a 4.2.2 rom so when you try to flash it keeps your stock kernel with a custom rom and it don't work out well
Flashing stock based ROMs with ss is fine though it's how we used to do it haha
Sent from my XT907 using Tapatalk 2

[Q] MB525 flashed to MB526, rooted but cant install cm9, 10, kitkat or any other ROM

Hi
I had a Motorola Defy mb525.
Bricked the phone while trying to install CM9
Got it alive somehow by Flashing it with .sbf
Now my phone shows as mb526 and I was able to root it again.
System Version - 45.0.231.mb526.AsiaRetail.en.03
Version - 2.3.6
Kernel - 2.6.32.9-ge281b6e [email protected] #1
The problem now is I am not able to flash any of the Custom ROM's.
Tried CM10, Cm9 and also the latest kitkat
Downloaded different ones for each ROM's.
I get the message when i try to update from SDcard "Signature verification failed"
If someone could help me in Upgrading to JellyBean or Kitkat

rahulpillai said:
Hi
I had a Motorola Defy mb525.
Bricked the phone while trying to install CM9
Got it alive somehow by Flashing it with .sbf
Now my phone shows as mb526 and I was able to root it again.
System Version - 45.0.231.mb526.AsiaRetail.en.03
Version - 2.3.6
Kernel - 2.6.32.9-ge281b6e [email protected] #1
The problem now is I am not able to flash any of the Custom ROM's.
Tried CM10, Cm9 and also the latest kitkat
Downloaded different ones for each ROM's.
I get the message when i try to update from SDcard "Signature verification failed"
If someone could help me in Upgrading to JellyBean or Kitkat
Click to expand...
Click to collapse
Are you sure you are using custom recovery?
Sent from my Nexus 7 using Tapatalk

Feel like a real dumb person now, I did not install Sndinit
hotdog125 said:
Are you sure you are using custom recovery?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Feel like a real dumb person now, I did not install Sndinit
Now I am in the Custom Recovery menu
Backing up my current ROM
Will try to flash Kit Kat and update

Still no Luck
rahulpillai said:
Feel like a real dumb person now, I did not install Sndinit
Now I am in the Custom Recovery menu
Backing up my current ROM
Will try to flash Kit Kat and update
Click to expand...
Click to collapse
Tried Kit Kat, still same
Tried CM10 twice, installs but when I reboot it gets Stuck on startup "Startup has encoutered an error" something like that
No matter what language I select still same
Any Inputs

For KitKat you need to flash an updated recovery. Check the thread.
Sent from my Nexus 7 using Tapatalk

CM10.2 works but Kit Kat Still not installing
hotdog125 said:
For KitKat you need to flash an updated recovery. Check the thread.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
CM10.2 works after installing gapps but Kit Kat Still not installing
I updated the recovery as well
My phone was bricked when I was installing Kit Kat
It stopped at Step 7
I had to flash the stock SBF to get it alive again
Will wait for updates to the kit kat mod
CM10.2 works but really slow

safestrap rom problem

i have a droid razr m
running 98.30.1
root only
i am trying to use safestrap 3.11 to flash a custom rom and every attempt has failed stating unable to open zip file i have tried multiple download links and roms and still nothing. also tried internal and external storage...other attempts were done on older versions of safestrap and still nothing
the only rom i was successful with was the rage m rom

Musiv said:
i have a droid razr m
running 98.30.1
root only
i am trying to use safestrap 3.11 to flash a custom rom and every attempt has failed stating unable to open zip file i have tried multiple download links and roms and still nothing. also tried internal and external storage...other attempts were done on older versions of safestrap and still nothing
the only rom i was successful with was the rage m rom
Click to expand...
Click to collapse
you are going to get deleted!! post this in QnA section. And BTW change your recovery to TWRP.

Musiv said:
i have a droid razr m
running 98.30.1
root only
i am trying to use safestrap 3.11 to flash a custom rom and every attempt has failed stating unable to open zip file i have tried multiple download links and roms and still nothing. also tried internal and external storage...other attempts were done on older versions of safestrap and still nothing
the only rom i was successful with was the rage m rom
Click to expand...
Click to collapse
Man!!! READ forum before posting!!

I did not realize you were boot locked.

Before this thread gets moved or deleted: you must tell us that whether you have unlocked your bootloader. If you haven't unlocked it, then you're stuck with SafeStrap and you should give up on ANY AND ALL custom ROMs beyond Android 4.2. Otherwise, if you have an unlocked BL, just fastboot flash a custom recovery and flash any ROM from there.
And stop posting the same question everywhere!
Sent from Google Nexus 4 @ CM11

Sounds like you tried to flash some ROMs that aren't compatible with SS.

AndyYan said:
Before this thread gets moved or deleted: you must tell us that whether you have unlocked your bootloader. If you haven't unlocked it, then you're stuck with SafeStrap and you should give up on ANY AND ALL custom ROMs beyond Android 4.2. Otherwise, if you have an unlocked BL, just fastboot flash a custom recovery and flash any ROM from there.
And stop posting the same question everywhere!
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
You're telling me I can run 4.2 roms in safestrap with a 4.1.2 base?

The only 4.2 ROM that worked was a CM10 port. It's running around in this forum somewhere.

You mean CM10.1(4.2)? or CM10 (4.1.2)

Playb3yond said:
You mean CM10.1(4.2)? or CM10 (4.1.2)
Click to expand...
Click to collapse
I think it was 10, so yeah 4.1.2.

Playb3yond said:
You're telling me I can run 4.2 roms in safestrap with a 4.1.2 base?
Click to expand...
Click to collapse
No, I mean everything Android 4.2+ will not run, including 4.2, 4.2.1, 4.2.2 and so on. I should've been clearer when describing. Just try that CM10 (Android 4.1.x).
Sent from Google Nexus 4 @ CM11

AndyYan said:
No, I mean everything Android 4.2+ will not run, including 4.2, 4.2.1, 4.2.2 and so on. I should've been clearer when describing. Just try that CM10 (Android 4.1.x).
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
There was a 10.1 in development for SS, but the BL unlock came out and they shifted focus away from SS.

Musiv said:
i have a droid razr m
running 98.30.1
root only
i am trying to use safestrap 3.11 to flash a custom rom and every attempt has failed stating unable to open zip file i have tried multiple download links and roms and still nothing. also tried internal and external storage...other attempts were done on older versions of safestrap and still nothing
the only rom i was successful with was the rage m rom
Click to expand...
Click to collapse
Only SS compatible rom i know of is this
http://forum.xda-developers.com/showthread.php?t=2609263/
Updated 3/22/2014

Help sought: Screwed up my S4 and seeking a fix

Note: Relevant device info will be provided below.
Dear techwizards,
I've been trying to root my phone for a while, I've done it before: both my S II and S III were international variants, and rooting those devices was very simple. But after getting an S IV from America and consensually downloading a samsung issued update -- I had yet to read up on the disadvantages of knox -- my rooting and android experience took a turn for the worse.
Long story short -- I know developers are a proud bunch who value their time -- I tried rooting my phone yesterday after almost smashing my phone on a coffee table. They say it's a well known side effect of Touchwiz, but I'll leave that to you.
I used a towelroot.com root -- a wonderful tool, if I may say so. After that, I visited the CM website and picked out the compatible CM11. I never got to flashing it though, as my problems arose while installing a recovery.
I had downloaded an app, a something recovery or another. They had an option to flash recoveries on there--it would download your recovery for you and do all the work, which seemed plausible as most video tutorials demonstrated. To my astonishment, doing so bricked my phone.
I tracked back, looked for the samsung stock rom, downloaded all 2.2 gb's of it and flashed it. It worked. My phone was functional but I suspect something within it stinks. My device, apparently for security reasons, wont let my wifi or 4g to establish a connection. It's making it impossible for me to fix this problem as I can't root my device or flash a custom rom.
About Device:
Pre problem I was running a:
SGH-I337UCUFNC1 baseband. Build Number ending with: NC1.
Android version: 4.2.2
Post problem:
Baseband: I337UCUFNC1
Build Number: JSS15J.I337UCUEMK2
Android version 4.3.
If I could find my original stock 4.2.2 NC1 version and get simple instructions on how to re-install it back to stock version, I'd be very grateful.
If you know how I could fix the internet issue on the MK2 one, and provide some simple instructions of how to root it, I'd be grateful too.
If you think neither would work, and have something else in mind, Im open to your suggestions.
Much Regards,
Y

You can only use safestrap for the recovery. See in the general forum index, all things at&t....
You can't flash cm, only touch wiz based roms
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You can only use safestrap for the recovery. See in the general forum index, all things at&t....
You can't flash cm, only touch wiz based roms
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I never got to installing or attempting to install CM.
Things took a turn for the unexpected after I tried installing CMW recovery.
Please reread my post

I've read it. You can't install cwm. That's what had messed up your device. The only recovery you can use is safestrap
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app

jd1639 said:
I've read it. You can't install cwm. That's what had messed up your device. The only recovery you can use is safestrap
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
Click to expand...
Click to collapse
I see. Thanks for the info. Do you know what could be done to restore my device to stock? As of now I'm running a MK2 Android 4.3 on a NC1 4.2.2 device and the wifi/4g connection aren't working.

androidshmandroid said:
I see. Thanks for the info. Do you know what could be done to restore my device to stock? As of now I'm running a MK2 Android 4.3 on a NC1 4.2.2 device and the wifi/4g connection aren't working.
Click to expand...
Click to collapse
Did you look for the thread I pointed you to? In the general forum index, all things at&t... You're going to want to start there. That'll link you to this
http://forum.xda-developers.com/showthread.php?p=49687770
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app

Since your bootloader is already locked, you might as well Odin to stock. Odin to NB1 then use stock recovery to flash the NC1 update from a zip file on a microSD.
Part of the problem is that the NC1 is not 4.2.2 like you listed, but 4.4.2. That's the update you applied that started the sordid tale. When you were on 4.2.2, with bootloader MD<something>, you could have flashed CM or whatever, because you would be able to have TWRP or CWM recovery. When Samsung pushed out a 4.3 update (MK2 I believe) all the unlocked bootloader fun was over, probably permanently for this phone.
When you flashed MK2 firmware (4.3) onto the phone, parts of it don't work with the NC1 baseband, causing the problems you've seen. If you Odin NB1, then do the quick zip update from stock recovery to get all the way to NC1, you'll be back to stock and everything should work.
Once that's done, you can go through this process:
1. Root with Towelroot.
2. Install SuperSU to manage root access. (You might have to reboot, it's a 50%/50% shot... sometimes it hangs trying to disable Knox... no worries just reboot)
3. Install SafeStrap... it will create the safestrap recovery. You might need to install SELinux Mode Changer app (from play store) and set to permissive, to get Safestrap installed.
4. Boot to the SafeStrap recovery. Install any touchwiz rom. Only touchwiz compatible roms will work. I liked GoldenEye.
When installing touchwiz ROMs, typically one flashes the ROM, then SuperSU, then the NC1 modules, then the ATT BuildProp/APN file. Sounds complex but goes quickly. Some roms have some of these things built in.
Good luck! I eventually decided I didn't like the ATT Samsung restrictions of the locked boot loader, and bought a T-Mobile M919 variant of the S4. Unlocked boot loader. Woo hoo. And works fine on ATT.
Marc

[Q] questions re razor m / kitkat

ok I just got a razor m on ebay.
it was on JB
I rooted it with towelroot3
unlocked the boot loader with motopocolypse
but the recoveries I see are for kitkat.
i did a check for software updates and it found one and down loaded it successfully
updated is successfully and i am not on
system version 98.18.78.xt907.verizon.us
android version 4.1.2
kernel 3.0.31-g101ca72
build 9.8.1q-78
your device is up to date!
all the recoveries are i find kikat
my goal is to get this to cm12 or at least cm11
so I think I need to get to kitkat should I just get cm11 and flash the whole thing. is that right.

Wrong. You can't get CM11 installed without a proper recovery, and since you don't know where to get a JB recovery, I advise simply going for KitKat.
Use RSD Lite to flash this thing up to stock KitKat (you've unlocked your BL already so don't worry), then do the recovery stuff as you know. More guides are available in the General sticky post.
Remember, once you get to stock KitKat, any ROM you flash from then on should be for "moto_msm8960" instead of "moto_msm8960_jbbl". Especially for CM11 and CM12.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]

AndyYan said:
Wrong. You can't get CM11 installed without a proper recovery, and since you don't know where to get a JB recovery, I advise simply going for KitKat.
Use RSD Lite to flash this thing up to stock KitKat (you've unlocked your BL already so don't worry), then do the recovery stuff as you know. More guides are available in the General sticky post.
Remember, once you get to stock KitKat, any ROM you flash from then on should be for "moto_msm8960" instead of "moto_msm8960_jbbl". Especially for CM11 and CM12.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
before you posted I had already installed the latest cm 11 for the razr M (not the unified one) and it seems to work fine for the 12 hours I had it.
but I followed your recommendation anyway.
i couldn't get rsd lite to work but I just extracted the images from the zip and used the xml to create a proper bat script to mfastboot them manually
that got me to kitkat while still being unlocked bootloader just like i expected. (its nice not to be a total noob)
then i found out the speaker on the back (behind the broken glass which i planned to replace) didn't work.
headphone and earpeice work fine vibration work fine.
it will go up on ebay, or i will keep it for some other use.