I got a used Motorola Photon that has Android 2.3.5 (build 254_12) and it has an unlocked bootloader. After going through numerous posts in XDA I came to know that 2.3.5 doesn't support bootloader unlocking. I asked the guy I bought it from and he said that initially it had MoPho 2.3.4 - he unlocked it, upgraded it to CM10 JB rom and then downgraded it back to 2.3.5 (as JB was unstable). I confirmed my MoPho has an unlocked bootloader from here ( http://forum.xda-developers.com/showthread.php?t=1650520 ). It's also rooted.
So I just wanted to know, are there any risks in installing a custom kernel/rom since my MoPho's OS ver is 2.3.5 ? Are there any internal conflicts that might occur since my OS version/build is different - one that doesn't allow unlocking of bootloader and root access?
No there aren't any major risks. Just make sure the kernel corresponds to the system you are using. For instance, if your using cm7 and want to overclock, make sure to use a kernel built for it.
Most ROMs are flashed with the kernel it needs to boot. Version 2.3.5 could be thought of as just another ROM. To flash something different, make a backup with your recovery then wipe and install the ROM of your choice.
Just be sure to us common sense and not to accept any ota update because it could lock your bootloader and brick your phone. Be sure to look at the stickies for a ton more information
Sent from my MB855 using xda premium
mystaku said:
I got a used Motorola Photon that has Android 2.3.5 (build 254_12) and it has an unlocked bootloader. After going through numerous posts in XDA I came to know that 2.3.5 doesn't support bootloader unlocking. I asked the guy I bought it from and he said that initially it had MoPho 2.3.4 - he unlocked it, upgraded it to CM10 JB rom and then downgraded it back to 2.3.5 (as JB was unstable). I confirmed my MoPho has an unlocked bootloader from here ( http://forum.xda-developers.com/showthread.php?t=1650520 ). It's also rooted.
So I just wanted to know, are there any risks in installing a custom kernel/rom since my MoPho's OS ver is 2.3.5 ? Are there any internal conflicts that might occur since my OS version/build is different - one that doesn't allow unlocking of bootloader and root access?
Click to expand...
Click to collapse
do as you please no risks with anything really. only phones that took the 2.3.5 OTA update are locked. or new factory restored ones. the previous user put the 2.3.5 update on their in a safe manor that doesn't lock the phone. :silly:
na7q said:
do as you please no risks with anything really. only phones that took the 2.3.5 OTA update are locked. or new factory restored ones. the previous user put the 2.3.5 update on their in a safe manor that doesn't lock the phone. :silly:
Click to expand...
Click to collapse
I've the 254_12 build. And (I think, I'm not sure) the OTA update is probably the only way to update your system to 254_12.
What I'm not able to understand is how he could have downgraded from a CM10 JB rom to 2.3.5(254_12) without locking the bootloader. Is there anyway to do so?
All the root/unlock guides in XDA and other forums warn us, before proceeding to unlock, to ensure that our MoPho has 2.3.5 (198_7)or below to unlock/root. Shouldn't I be worried about it?
Here's a screenshot of my system specs.
No. You're unlocked. That's just your system build information. It will change when you flash a different ROM.
The ota update is the only way to update your stock and locked phone without any sort of modification. Since you're unlocked and rooted you shouldn't have an issue flashing a custom recovery and ROM
Sent from my MB855 using xda premium
mystaku said:
I've the 254_12 build. And (I think, I'm not sure) the OTA update is probably the only way to update your system to 254_12.
What I'm not able to understand is how he could have downgraded from a CM10 JB rom to 2.3.5(254_12) without locking the bootloader. Is there anyway to do so?
All the root/unlock guides in XDA and other forums warn us, before proceeding to unlock, to ensure that our MoPho has 2.3.5 (198_7)or below to unlock/root. Shouldn't I be worried about it?
Here's a screenshot of my system specs.
Click to expand...
Click to collapse
My friend, as I mentioned, the previous user had downgraded or "upgraded" the stock firmware in a SAFE manner that does NOT lock the bootloader. It's done the same way custom ROMs work. It just another ROM basically. Pretty simple. Don't take everything so literal in terms of 2.3.5 only OTA updated or factory restored phones are locked. Which you don't have
Sent from my MB853 using XDA
na7q said:
My friend, as I mentioned, the previous user had downgraded or "upgraded" the stock firmware in a SAFE manner that does NOT lock the bootloader. It's done the same way custom ROMs work. It just another ROM basically. Pretty simple. Don't take everything so literal in terms of 2.3.5 only OTA updated or factory restored phones are locked. Which you don't have
Sent from my MB853 using XDA
Click to expand...
Click to collapse
Thank you, it's clear to me now
mystaku said:
Thank you, it's clear to me now
Click to expand...
Click to collapse
Great! I hope you have fun trying out ROMs!! It's always a blast!
Sent from my MB853 using XDA
Related
I've been away on holiday for a short time and boy....development has sure moved fast
quick few questions:
1. I'm on gingerblur, do I need to SBF back to stock to flash new custom ROMs?
2. Regarding above question....I need to unlock the bootloader first using the unlocking package on briefmobile or the pudding thread if I can find it right?
3. Which Gingerbread based ROM seems to run the most bug free/useable as a daily driver right now?
thanks!
I like KennethPenn's ROM. Running smoothly, so far. I haven't had it on long enough to make a definitive comment, but it is stable and fast.
carlharsch said:
I like KennethPenn's ROM. Running smoothly, so far. I haven't had it on long enough to make a definitive comment, but it is stable and fast.
Click to expand...
Click to collapse
I have had it since he released and I think its a great build quick and seems like moto has fixed some things that needed to be fixed.I like the gui.
Sent from my MB860 using XDA Premium App
Xenocyde said:
I have had it since he released and I think its a great build quick and seems like moto has fixed some things that needed to be fixed.I like the gui.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Is it already rooted if I may ask?
Sent from my semi de-blurred atrix using telepathy and Tapatalk
droid_does said:
Is it already rooted if I may ask?
Sent from my semi de-blurred atrix using telepathy and Tapatalk
Click to expand...
Click to collapse
its not rooted, you are going to have to flash back to 1.8.3, make sure you use the full build and not just the OTA update, unlock the bootloader, flash 2.3.4 then root. make sure you flash this build from ken theres reports of hard bricking if you use other sources.
neotekz said:
its not rooted, you are going to have to flash back to 1.8.3, make sure you use the full build and not just the OTA update, unlock the bootloader, flash 2.3.4 then root. make sure you flash this build from ken theres reports of hard bricking if you use other sources.
Click to expand...
Click to collapse
so first I SBF back to 1.8.3
root
unlock BL
flash 2.3.4 (which one? HKTW? or the one linked above?)
The new build is fully rooted thanks to kenneth. Everything seems to work.
Sent from my MB860 using XDA Premium App
droid_does said:
so first I SBF back to 1.8.3
root
unlock BL
flash 2.3.4 (which one? HKTW? or the one linked above?)
Click to expand...
Click to collapse
Flash the one in the link above by Kennethpenn. The HKTW one will give you battery life issues and a non-working fingerprint scanner, while other sources could result in a hard brick if you ever want to downgrade. You'll need the unlocked bootloader version of CWM to flash it, not the existing charge mode one. You dont need root to install it, and I believe that particular version of 2.3.4 is already rooted. So,
unlock BL
flash cwm
flash Kennethpenn's 2.3.4.
If i flashed the ota. And u have unlocked bl and cwm, can I flash custom roms from 2.3.4?
Sent from my MB860 using XDA App
Javi97100 said:
If i flashed the ota. And u have unlocked bl and cwm, can I flash custom roms from 2.3.4?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yes you can
K thanks
Sent from my MB860 using XDA App
I too flashed the OTA( 2.3.4), I wasn't rooted or unlocked when i did it. will there be a way to get the official version when released on my device?
(didn't know if i had to start another thread since OP already started it)
velvetmxo said:
I too flashed the OTA( 2.3.4), I wasn't rooted or unlocked when i did it. will there be a way to get the official version when released on my device?
(didn't know if i had to start another thread since OP already started it)
Click to expand...
Click to collapse
Since it hasn't come out yet, no one knows if ota 2.34 we flashed will accept official updates properly. But if that's the case devs will definitely figure out ways to extract the files needed to install them either through fastboot or cwm most likely. You'll want to be unlocked and rooted.
mysticdrew said:
Since it hasn't come out yet, no one knows if ota 2.34 we flashed will accept official updates properly. But if that's the case devs will definitely figure out ways to extract the files needed to install them either through fastboot or cwm most likely. You'll want to be unlocked and rooted.
Click to expand...
Click to collapse
looks like i'm out of luck with the unlocking and rooting since it requires me to RSD flash to a different rom prior to updateing to 2.34 when they are saying it causes bricks. guess i'll wait for the official att and see if we can do the same update setup over the beta..love it though..just hate the fact my signal keeps going white then blue...any way thanks
I may have to return my ATRIX due to Let'sTalk horrible customer service, but I was wondering if there is anyway to re-lock the Bootloader, or to hide the fact that it says, Unlocked. Thank you in advanced
Also, I'm sorry if this is in the wrong section, as this is urgent to me and I have yet to see any otherpost relating this topic.
There is another topic like this.
No you can't re-lock and no you can't "hide" the unlock wording. Sorry.
Sent from my AWESOME Atrix
Assume you installed 2.3 using CWM, if that is the case, you can flash the stock 1.8.3. Because the bootloader is not compatible with the unlocked phones, it won't show the "unlocked" text when you turn on the phone. I have tried it when I was trying to get rid if the unlocked text.
The down side is, you won't be able to flash custom ROM until you flash a compatible bootloader.
Sent from my Motorola Atrix 4G MB860 using XDA App
But downgrading will hard brick the phone.be very very carefully.
Reflash To Stock
Unfortunately, there is no way to relock a bootloader. Hence all of the warnings when you committed
but, if you use 4.5.91 the software at the address below should reinstall the newest stock software...
direct.motorola.com/hellomoto/motosupport/source/SoftwareUpdateSelect.asp?country=USA&language=ENS
be careful because Im not sure how motorola update will react to an unlocked bootloader. Ask around...do so at your own risk.
If you want to try a harder, albeit, safer method, and you are sure that you do not have a phone running 4.1.5.91, you can restore your phone to a factory SBF with this process:
briefmobile.com/motorola-atrix-4g-system-boot-file-sbf-leaked
DO NOT UNDER ANY CIRCUMSTANCES TRY TO RESTORE A 4.5.91 system to stock with RSD LITE.
To go to any of the blue webaddresses above, copy-paste them into your browser. Sorry, but I am not allowed to post links yet.
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
drpratik said:
But downgrading will hard brick the phone.be very very carefully.
Click to expand...
Click to collapse
The downgrading and hard brick problem stems from using the OTA update, so you won't hard brick if for example you upgraded with KP's 4.5.91.
You also should be able to flash the 4.5.91 SBF. You just can't downgrade. There are other threads about this.
Sent from my Alienated Atrix
maledyris said:
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
Click to expand...
Click to collapse
The reason the fruitcakes were created and deemed safe by the devs were because it didn't touch the BL, which people believe to be the culprit behind the hard bricks. NFhimself was brave enough to testing flashing the BL via cwm in his gobstopper on international phones, but I don't think any other devs are willing to risk hard bricking their phones by testing that theory on US phones.
There also isn't enough "reward" for doing so because if people want to downgrade they can use a fruitcake. The only gain is to get rid of the "unlock" text. But if you were really that concerned about it despite reading all the warnings of this will void you warranty, you shouldn't have unlocked in the first place.
maledyris said:
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
Click to expand...
Click to collapse
Hi,
One of the reasons I did up a default CWM of 2.2.2 is to have a means of doing a reset after trying all ATT/ORANGE/TELSTRA/MOVIESTAR/etc firmwares out there which may have side effects or accumulated side effects. Hence the inclusion of the stock bootloader and radio and a write of the extra partitions to clean up whatever mix and match leftovers are in there from the various carriers. The other big one is just to be able to get a Bell OTA applied when it comes out, it will probably be similar to the leak, but best to be safe.
This is more of a Bell/Intl issue as ATT folks tend to run just ATT firmware or flash just boot and system via CWM/fastboot and don't have the same issues as flashing a sbf file.
Both the stock 2.2.2 and leaked ap20 OTA bootloaders from Bell are safe to flash after IHOP, this is not the case with ATT bootloaders and may be the case for any included in a sbf file. Finding out the hard way is not an option.
Cheers!
ken218 said:
Assume you installed 2.3 using CWM, if that is the case, you can flash the stock 1.8.3. Because the bootloader is not compatible with the unlocked phones, it won't show the "unlocked" text when you turn on the phone. I have tried it when I was trying to get rid if the unlocked text.
The down side is, you won't be able to flash custom ROM until you flash a compatible bootloader.
Sent from my Motorola Atrix 4G MB860 using XDA App
Click to expand...
Click to collapse
Say I unlocked it at 1.8.3 should I go down to 1.5.7? Is that safe?
moto helper update relocked mine flashed it to 4.5.91 and i had to reunlock and root agin i thought i was getting a driver update not ota.I was on rom homebase + extras but my win 7 64 bit wasent seeing my phone so i reinstalled drivers and updated drivers and updated moto helper and in the process flashed my phone to stock that pissed me off had to start over..I rebooted the phone several times and never seen unlocked on boot tried to fastboot into android recovery and got the triangle im all good now back on homebase ext4 just thought id share that you realy can relock at least it dont say unlocked i beleve its locked
defnow said:
and no you can't "hide" the unlock wording. Sorry.
Click to expand...
Click to collapse
Err...............yes you can!
care to share how?
Scolis said:
care to share how?
Click to expand...
Click to collapse
Read the thread from the start. It's already been said!
CaelanT said:
Read the thread from the start. It's already been said!
Click to expand...
Click to collapse
Trying this today. Seems like my vibrator motor quit working. Phone is 6 months old I should be under the year warranty or so right?
leperkuan said:
Trying this today. Seems like my vibrator motor quit working. Phone is 6 months old I should be under the year warranty or so right?
Click to expand...
Click to collapse
When I was at school 6 months < 1 year so yes!
This is where you need to look:
http://forum.xda-developers.com/showthread.php?t=1163009
CaelanT said:
When I was at school 6 months < 1 year so yes!
This is where you need to look:
http://forum.xda-developers.com/showthread.php?t=1163009
Click to expand...
Click to collapse
Lol well I wasn't sure it had a one year warranty. Found out my vibrator does work. Just sometimes doesn't on cm7. Weird. Well I may try this anyways. Tired of custom Roms.
Sent from my MB860 using Tapatalk
leperkuan said:
Found out my vibrator does work.
Click to expand...
Click to collapse
Think you should go to another site other than XDA with this. Something in the XXX domain should work for you. Too much information for me! LOL................
assuming it is still in warranty
hard brick the phone and return it
just tell them you was doing a software update and your kid unplugged the phone while doing so
I relocked, will this allow me to get the ota?
If not will i have to download and flash the official build in ph98 form?
fenguepay said:
I relocked, will this allow me to get the ota?
If not will i have to download and flash the official build in ph98 form?
Click to expand...
Click to collapse
what ota? in case you didn't notice it never came.
I mean the future one
Sent from my ADR6425LVW using xda premium
anyone?
Sent from my ADR6425LVW using xda premium
if there is ever a ota ... as long as u are relocked u should be able to get the ota
yojoe600 said:
if there is ever a ota ... as long as u are relocked u should be able to get the ota
Click to expand...
Click to collapse
Not if he's not on stock though right?
Sent from my ADR6425LVW using XDA
werdna87 said:
Not if he's not on stock though right?
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
right. need to be re-locked and stock non rooted.
I do not understand why you would want to unroot and unlock to get the OTA "when released". In about a day after it is released I am sure a Dev will have a flash-able version posted.
Maybe but since we don't have s-off don't we have to relock to flash the new firmware and radios? Hopefully we have s-off before official update comes.
sent from my Rezound
qudwis said:
right. need to be re-locked and stock non rooted.
Click to expand...
Click to collapse
I didn't think it mattered if you were rooted or not. I thought the things required to get an OTA update from Verizon were:
1. LOCKED or RELOCKED
2. Stock Recovery
3. Close to Stock ROM
Somebody please correct me if I am wrong...
guyd said:
I didn't think it mattered if you were rooted or not. I thought the things required to get an OTA update from Verizon were:
1. LOCKED or RELOCKED
2. Stock Recovery
3. Close to Stock ROM
Somebody please correct me if I am wrong...
Click to expand...
Click to collapse
Yea like I think I read you couldn't be debloated or anything
Sent from my ADR6425LVW using XDA
werdna87 said:
Yea like I think I read you couldn't be debloated or anything
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
You will not get the ota on a custom Rom
Sent from my ADR6425LVW using Tapatalk 2
No need to relock. Just unfreeze or restore bloat. Radio and such flashed fine while unlocked
esheesle said:
No need to relock. Just unfreeze or restore bloat. Radio and such flashed fine while unlocked
Click to expand...
Click to collapse
Wierd, I read a few posts in another topic that said you had to be locked or relocked in order for the new radio to flash...
What about me?
Well my bootloader screen at the top says ***tampered with*** and then under it says ***re-locked*** and rom is a "clean rom" (ICS based). I purchased (expecting a stock device) and it turned out to be rooted/flashed. What I'm wondering is when Verizon HTC releases the "official" ICS update, will it come to my phone? If so, this would be the quickest fix for me to get stock again. I'm not concerned with "bloatware" etc, I just want things Verizon/HTC stock. I don't download enough apps to be concerned about bloatware and internal space etc. So from what I'm reading here, being "re-locked" and having a flashed rom that's close to being stock should allow me to still get the update, am I correct?
In short, what I mean is, will the update come to my phone like it has done previous android devices (that weren't flashed)? Or will I have to flash another OTA based cooked rom AFTER the official one comes out and someone "cooks" it?
You will not get the OTA if you are rooted, that's for sure. If it's the stock ROM, you'll get the option to update, but it'll fail during the installation. I've seen it happen on a few HTC devices and even my rooted Xyboard tablet lol. But, just to be safe if you DO want the OTA, install the stock ROM (If you're on an ICS ROM, you're going to have a tough time getting back to stock. It's bricked a lot of people's phones. You have to restore the firmware yourself, I think.) and relock your bootloader. Don't be worried if it says **Security Warning** this simply means that your bootloader has been unlocked at one point in time.
Just make sure your phone is on a stock, non-rooted ROM with your phone locked to make sure you have no issues. Better safe than sorry.
lol?
refuse2bstopped said:
Well my bootloader screen at the top says ***tampered with*** and then under it says ***re-locked*** and rom is a "clean rom" (ICS based). I purchased (expecting a stock device) and it turned out to be rooted/flashed. What I'm wondering is when Verizon HTC releases the "official" ICS update, will it come to my phone? If so, this would be the quickest fix for me to get stock again. I'm not concerned with "bloatware" etc, I just want things Verizon/HTC stock. I don't download enough apps to be concerned about bloatware and internal space etc. So from what I'm reading here, being "re-locked" and having a flashed rom that's close to being stock should allow me to still get the update, am I correct?
In short, what I mean is, will the update come to my phone like it has done previous android devices (that weren't flashed)? Or will I have to flash another OTA based cooked rom AFTER the official one comes out and someone "cooks" it?
Click to expand...
Click to collapse
I returned a rezound with cleanrom in it.... XD. probably not urs but jsut a question.... is the menu button dim compared to the others?
relock/unlock
You do not need s-off to relock. I unlocked and installed scotts cleanrom. I then a month later relocked installed the leaked OTA ICS update so i could have the new radios. Then unlocked again and installed the cleanrom DE senseless yesterday and i am loving it btw! I get decent battery too (13+ hours with moderate use)!
Hello.
I just got my hands on a Photon 4G.
I'm looking for alternative rom to stock.
However, I noticed that all roms have no 4G wimax. Is that correct? Or, I'm not looking hard enough.
Thank you.
To flash most ROMs you need to unlock your bootloader, flashing a new bootloader breaks 4G.
But you might not have to worry about that, what's your android version number 2.3.4 or 2.3.5?
If you updated your phone to 2.3.5 OTA, that'll lock the bootloader permanently.
I did the 2.3.5 OTA.
So, therefore, no custom roms for me?
And, apparently, Sprint/Motorola will not be updating phone to ICS.
Pretty much, I'm out of luck?
Bock Abrams said:
To flash most ROMs you need to unlock your bootloader, flashing a new bootloader breaks 4G.
But you might not have to worry about that, what's your android version number 2.3.4 or 2.3.5?
If you updated your phone to 2.3.5 OTA, that'll lock the bootloader permanently.
Click to expand...
Click to collapse
knite75 said:
I did the 2.3.5 OTA.
So, therefore, no custom roms for me?
And, apparently, Sprint/Motorola will not be updating phone to ICS.
Pretty much, I'm out of luck?
Click to expand...
Click to collapse
Pretty much. I know there's locked ROMs but I'm not sure if there are 2.3.5 compatible
Sent from my MB855 using xda app-developers app
Jaemostoriginal said:
Pretty much. I know there's locked ROMs but I'm not sure if there are 2.3.5 compatible
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
I got tired of the OTA bugging me constantly, and was pretty sure I wasn't going to root again, because 1) I had Foxfi for WiFi tether and 2) none of the ROMS that DON'T break 4g were that interesting. So I downloaded it. But, I also fully expected to get ICS from Google, because they promised, on the official ICS upgrade list, that the Photon would be there. BUT, YET AGAIN, THEY LIED!
SO... I have an app that let me re-image my device back to pre-root before, and it was 2.3.4. Can I root, then re-image back to 2.3.4, then apply a ROM?
ALSO, I have heard of unlocking and re-locking the bootloader. Can I root, unlock the bootloader, ROM, then re-lock and restore 4g? If so, how?
And, with ALL the 4g WiMax out there, and so, little 3g even functioning these days, why can't anyone seem to not break WiMax when ROMing? I'm just asking, because I really don't know.
Thanks!
Re-locking your bootloader won't restore 4g. I don't have 4g in my area so haven't ever connected to it so not sure if its much faster. If you want to try custom a ROM then unlock and try it. Can always undo it. That's if you can actually get off 2.3.5