I bought a Motorola Photon and unlocked the boot loader, rooted, Clockwork Mod Recovery'd, tried the whole Sprint phone unlocked for all carriers, then flashed CM9.
I tried to sbf back to stock and somehow (assuming I downloaded the wrong file along the way) I now have a Motorola Electrify that tries to run on U.S.Cellular.
I have subsequently downloaded all three stock sbf files on ShabbyPenguin's website and none of them will flash. (Super mega thanks to Shabby!)
I apologize if this is a duplicate thread. I've been searching all over this forum and the general interweb since roughly 9:00pm last night. Does anyone know a way I can force my phone to allow the flash that keeps failing on "re-enumeration"?
I come from mostly Samsung devices and RSD seems to be the closest thing to "download mode" but in download mode you can pretty much flash anything. Sorry this is long and rambling.
jonas916 said:
I bought a Motorola Photon and unlocked the boot loader, rooted, Clockwork Mod Recovery'd, tried the whole Sprint phone unlocked for all carriers, then flashed CM9.
I tried to sbf back to stock and somehow (assuming I downloaded the wrong file along the way) I now have a Motorola Electrify that tries to run on U.S.Cellular.
I have subsequently downloaded all three stock sbf files on ShabbyPenguin's website and none of them will flash. (Super mega thanks to Shabby!)
I apologize if this is a duplicate thread. I've been searching all over this forum and the general interweb since roughly 9:00pm last night. Does anyone know a way I can force my phone to allow the flash that keeps failing on "re-enumeration"?
I come from mostly Samsung devices and RSD seems to be the closest thing to "download mode" but in download mode you can pretty much flash anything. Sorry this is long and rambling.
Click to expand...
Click to collapse
Yikes... I think once people flash that Electrify SBF by mistake, they are screwed.
Well, crap.
Take it to nearest Sprint store ask someone there to reprogram it you tried to do a system update and the battery died in the middle of it and how your phone is now is the end result if you have insurance it will be free to program it and if it fails to program should get new/ refurbished one for free or at the worst what ever the replacement fee is worth a shot worked for me once I tried to flash an sbf and my damn battery drained completely. Took it to Sprint store said the above and received the above. Gl
Sent from my MB855 using xda premium
I don't have insurance.
If you dont have the insurance it will cost you $35 for a replacement phone. I bricked mine without insurance and had to cough up the $35 for a new one. They tried reflashing my phone for free though but it didnt fix issue, so they should reflash it for you no problem without charging
Do you think they'll do it even though its booting up as an electrify on U.S.Cellular?
jonas916 said:
Do you think they'll do it even though its booting up as an electrify on U.S.Cellular?
Click to expand...
Click to collapse
Honestly, it depends on who you see. As a Sprint employee who works at a S&R store, and into rooting myself, I'd have no problem with it (Upstate NY btw). But technically, since it's unlocked, its broken the warantee, and if you go to a store thats very by the books, it's gonna be iffy. If you can, go to a serice and repair store that IS NOT corporate, and likely they'll do it for you. If they ask if you rooted it, just say yes, and one of two things will happen. Either they'll say "sorry, we can't help you" and then you go to a different store, because trust me, that **** doesn't get noted or anything, or since the guy knows what rooting is, he's probably into it himself and will sympathise and get you a new one.
Sprint service and repair store turned me down. Looks like I'm just gonna keep at it. I figure I'll get it at some point. If anyone has any other suggestions, I'll give it a try.
jonas916 said:
Sprint service and repair store turned me down. Looks like I'm just gonna keep at it. I figure I'll get it at some point. If anyone has any other suggestions, I'll give it a try.
Click to expand...
Click to collapse
Does you phone say unlocked ?
Currently, it does not say unlocked. It also gives me an error message if I try to execute any fastboot commands aside from:
moto-fastboot -w
&
moto-fastboot reboot
Motorola is saying all I can do is send it in to them. I can get into RSD mode but nothing will successfully flash. I'm starting to think they might be right. I'm just so used to having Samsung phones. They're relatively easy in comparison. If anyone has any ideas, I'm open to suggestions.
Try # moto-fastboot -w and then rds unlock then #moto-fastboot erase recovery #moto-fastboot flash recovery recovery-cyan-photon3.img (cwm) and you should be good! *cross fingers*
Sent from my MB855 using xda premium
Yeah, that is not going to work either.
That electrify ROM is a PITA when placed on the Photon.
I was able to exchange mine at the local store, but I luck out in the fact that they LOVE me there.
My exchange didn't cost me a dime either. However by that time the phone wouldn't charge either, so it wasn't booting, so they couldn't see the unlocked or the US Cellular boot animation.
Plus the fact the the owner and one of the techs were running Photons really helped.
Good luck.
I have the same problem I think the only way to solve this is to actually unlock it and use a custom rom. OR wait for Sprint to release a 2.3.5 rom to flash since you have a 2.3.5 bootloader I basically have a useless phone now
radrian92 said:
Try # moto-fastboot -w and then rds unlock then #moto-fastboot erase recovery #moto-fastboot flash recovery recovery-cyan-photon3.img (cwm) and you should be good! *cross fingers*
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Do I put the # in? I've never done that before.
Sent from my Nexus S 4G using Tapatalk
jonas916 said:
Do I put the # in? I've never done that before.
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
No without it
Sent from my MB855 using xda premium
Ok, I've tried that. Basically what I've found is that the 2.3.4 sbf for both the Photon 4G and the Electrify are unlockable, but the 2.3.5 which is available for the Electrify comes with a non unlockable bootloader. Somewhere along the line I must have accidentally flashed that and now I'm screwed. There is no way to downgrade without unlocking and no way to unlock that bootloader at this time. Sorry for the bad news to anyone else in this predicament. If anyone comes across a solution, please let me know.
jonas916 said:
Ok, I've tried that. Basically what I've found is that the 2.3.4 sbf for both the Photon 4G and the Electrify are unlockable, but the 2.3.5 which is available for the Electrify comes with a non unlockable bootloader. Somewhere along the line I must have accidentally flashed that and now I'm screwed. There is no way to downgrade without unlocking and no way to unlock that bootloader at this time. Sorry for the bad news to anyone else in this predicament. If anyone comes across a solution, please let me know.
Click to expand...
Click to collapse
try "frying" the phone phone/cpu so u can get it replaced without them seeing it unlocked ?
More or less that is what I did. By the time I brought my phone into the local store, it wouldn't even turn on.
Now when the tech put his charged battery into the phone, it showed whatever it did, but I was taken care of.
Related
I need to send my wife's phone back to verizon. I need to unroot it and get it back to stock before I return it. Is running the Verizon RUU all I need to do to get the phone back to legit? I didn't know if that wipes out the bootloader and everything?
Any input is appreciated.
Ryzor said:
I need to send my wife's phone back to verizon. I need to unroot it and get it back to stock before I return it. Is running the Verizon RUU all I need to do to get the phone back to legit? I didn't know if that wipes out the bootloader and everything?
Any input is appreciated.
Click to expand...
Click to collapse
Yes, it replaces the bootloader, the radio (with a slightly older version than the 7/17 OTA), and the /system, /data, recovery, and boot partitions. You might find that after you do this it will immediately inform you that an update is available (the 7/17 OTA).
That should be sufficient. Highly, highly unlikely that VZW is going to put a crack team of computer forensic scientists "on the case" to investigate your phone. There have been folks who reported (either here or over on AF, I can't remember) that they had returned multiple rooted phones, without making any effort whatsoever to clean them up - and not a peep out of Big Red.
bftb0
I'm getting a refurb phone because of a trackball issue. Ill be doing the ruu and ill let you know how it goes.
Sent from my Froyo Eris using XDA App
Thank you both for your input.
Her phone is the trackball too...I was really hoping they would come off a different model since this will be her third Eris. Maybe the inevitable next time
Ryzor said:
Thank you both for your input.
Her phone is the trackball too...I was really hoping they would come off a different model since this will be her third Eris. Maybe the inevitable next time
Click to expand...
Click to collapse
If it happens again I would start getting ugly with Verizon and say something like "if you guys can't send me an eris that will work properly then I want a different phone that works." Usually if you complain enough or threaten to go to a competitor they will do something for you.
Sent from my Froyo Eris using XDA App
I flashed the official 2.1 ruu and it flashed my phone to 100% stock. Bootloader, recovery, etc. Got the update notice for the Mr4 so I'm all good now.
Sent from my Eris using XDA App
My dad's Optimus T supposedly can't boot up after he took out the battery and the device has been never rooted or anything(stock). I can't take a look at the phone to see whats wrong, but I'm preparing for the worst and want to know how to flash stock rom with kdz to maybe get it back up and running. I found the KDZ file and I am wondering what else I would need besides that? I've never done this before and looking for advice. Also, my parents never bought warranty so do you think TMO will replace it because it was never rooted and it also has the dust problem. So would they replace it since it is defective product, but then again it's been a few months since we bought it.
Thanks.
Feeshie said:
My dad's Optimus T supposedly can't boot up after he took out the battery and the device has been never rooted or anything(stock). I can't take a look at the phone to see whats wrong, but I'm preparing for the worst and want to know how to flash stock rom with kdz to maybe get it back up and running. I found the KDZ file and I am wondering what else I would need besides that? I've never done this before and looking for advice. Also, my parents never bought warranty so do you think TMO will replace it because it was never rooted and it also has the dust problem. So would they replace it since it is defective product, but then again it's been a few months since we bought it.
Thanks.
Click to expand...
Click to collapse
well to be frankily honest with you, get yourself a job and start buying your own phones so that you can get warranties and insurance on your phone's also yes check with TMO about replacing the phone, no sense in using a utility like KDZ if you know nothing about it, I cant help you with KDZ, ive never had to use it and never will, but Im pretty sure there are tons of threads that can point you in the right direction
Jrhodes85 said:
well to be frankily honest with you, get yourself a job and start buying your own phones so that you can get warranties and insurance on your phone's also yes check with TMO about replacing the phone, no sense in using a utility like KDZ if you know nothing about it, I cant help you with KDZ, ive never had to use it and never will, but Im pretty sure there are tons of threads that can point you in the right direction
Click to expand...
Click to collapse
It wasn't my decision to buy warranty or not and this isn't my phone. I'm using KDZ as a last resort so I'm not 100% set on it. Going to see what TMO can do first, but I don't have any hopes that they will do anything.
Feeshie said:
It wasn't my decision to buy warranty or not and this isn't my phone. I'm using KDZ as a last resort so I'm not 100% set on it. Going to see what TMO can do first, but I don't have any hopes that they will do anything.
Click to expand...
Click to collapse
well good luck to you on that, if you need any help, let me know and Ill try to get some info for you on w/e you need, keep me updated as to how KDZ works for you, I have no need for it but Im to damn lazy to actually do the research for a tool I wont use, the only problem I had was one phone I "accidently" semi-bricked, but was under warranty so I got it replaced and now my second phone is rooted, customed recovery and CM7 rom on it
If you haven't had a chance to take a look at the phone yet, then maybe you can start with that and trying something simple like taking out the battery, putting it back in, connecting the charger, and trying to turn on the phone? Then you can see what's going on. Maybe you'll want to try holding Power + Vol. down + Home to go into recovery from a turned off state. Keep in mind that stock recovery immediately begins its restore which (I think - custom recoveries spoil us) wipes user content.
Jrhodes85 said:
well good luck to you on that, if you need any help, let me know and Ill try to get some info for you on w/e you need, keep me updated as to how KDZ works for you, I have no need for it but Im to damn lazy to actually do the research for a tool I wont use, the only problem I had was one phone I "accidently" semi-bricked, but was under warranty so I got it replaced and now my second phone is rooted, customed recovery and CM7 rom on it
Click to expand...
Click to collapse
Well, it's strange how it happened because this phone is completely stock and my dad or I never did anything to change anything to it. I really don't think it would get bricked just by removing the battery out.. I'll just have to wait until he gets back with the phone.
UPDATE: All phones have a 1 year warranty if something wrong with the phone so TMO took the phone in and sending a new one on the way.
Wait, so did you get a chance to look at it, or did someone else take it to TMO?
maip said:
Wait, so did you get a chance to look at it, or did someone else take it to TMO?
Click to expand...
Click to collapse
I tried to turn it on and it stays stuck at LG logo with the 4 buttons blinking. My dad took it to T-Mobile and gave him a replacement
Sent from my LG-P500 using XDA App
Hey guys... been checking around.. have a few quick questions. Just to give you an idea.. I've rooted and flashed my own Captivate, now my brother is looking for a new phone so we may get him an atrix.
1. How common is it to hardbrick the atrix? I know that on the captivate a hardbrick is an extremely rare happening, and you can almost always go back to stock via odin.
2. Is CM7 officially available? if so are the nightly releases fairly stable?
3. I know that flashing voids the warranty, and I wouldn't try to redeem a phone I ruined by overclocking or anything like that.. However, I prefer to have a way to completely remove anything I did to the phone. Is this possible?
1. Not very. Unless you try to downgrade from 4.5.91
2. I'm using cm7 now. No nightlies but 0 issues! VERY stable!
3. If you unlock bootloader its unlocked. No going back.
Sent from my MB860 using XDA App
Like joe said a hard brick is not very common, unless you don't follow directions. Cm7 is currently in beta for the atrix, but it is very very stable. No web top or finger scanner try though. Once you unlock the phone, during startup wroth the red M in thee upper left it will say unlocked. So nope, no way to undo it all.
Sent from my MB860 using XDA App
I'm going to agree with the the first two points earlier posters made, but as for relocking the bootloader, I think it can be done if you sbf(not recommended) back to the stock 3.4
Sent from my Unlocked Gingerblurred Atrix
Thanks guys, I know that on the Captivate if you go back to odin it returns it to stock.
I am hesitant to root something that can't be reverted.. not a good situation if something goes out.
I don't think he is too worried about the finger print scanner or webtop.
My friend wanted his Atrix rooted i took it home and did it under a hour, I had no experience with command prompts at the time
Sent from my VS910 4G using XDA App
There's an easy to follow guide if you only want root, not unlocked bootloader. Other than removing bloat its mildly pointless though
Sent from my MB860 using XDA App
krad54 said:
I'm going to agree with the the first two points earlier posters made, but as for relocking the bootloader, I think it can be done if you sbf(not recommended) back to the stock 3.4
Sent from my Unlocked Gingerblurred Atrix
Click to expand...
Click to collapse
I was under the impression that unlocking the bootloader cannot be undone, which is why the hardbrick occurs when flashing back to an earlier version after the GB OTA update.
I believe flashing a fruit cake should give you the stock Motorola bootlogo (no "Unlocked" at the top) image, but the bootloader will still be unlocked.
The biggest issue here is honestly this.
I don't want to get a phone with some sort of manufacturer defect, then not be able to claim the warranty because the phone was at some point in its life flashed. (Sometimes it takes a while for the defects to actually pop up..)
I don't believe in overclocking or anything like that.
If I softbrick a phone I can usually fix it on my own.
I just don't want say, the speaker to go out and it have nothing to do with what rom he is running..
And then for my brother to be out of a phone, just because the speaker went out.. despite it having nothing to do with the fact it was flashed..
As to the bootloader, yes you can flash earlier versions and the "unlocked" at the boot screen will disappear, however there will remain evidence that you had unlocked the bootloader before if they investigate it
That being said there's been quite a few people who have been able to get warrenty replacements and repairs sending back their phones after flashing back..I haven't heard of anyone who's phone has been investigated that deeply and rejected
That works.
I mean, I don't have any intention of overclocking or pushing the hardware out of spec or anything.
I figure as long as whatever goes wrong is reasonable and not related to doing something stupid with the device we will probably be ok.
You don't need to overclock that phone at all ... rooting it's simple as I posted before. There some bootloader blocking you from loading roms, can be taken off.
Sent from my VS910 4G using XDA App
While completely bricking the Atrix is hard to do, it's still possible if you don't carefully read all the instructions. I do miss the Captivate though, it's incredibly easy to flash and recover from any mistake. The CM7 beta build is very stable, I have been using it since the last update was release on the 13th of September and haven't experienced any big problems. If your brother is looking at the Atrix for the webtop or fingerprint scanning capabilities though, just know that the current CM7 build do not yet support them.
From what I've read so far, I haven't seen anyone trying to use their warranty have a problem with the unlocked bootloader. If you're going to buy it through AT&T, I'm pretty sure they're oblivious to it anyway. Last time I exchanged my phone at the repair center, they didn't even bother to see if it booted. They just took it and handed me another one on the spot.
UPDATED 3/25/2012
Talk Android, in the article below, mistakenly stated the update was for the X2 was live. Turns out not to be true.
http://www.talkandroid.com/99664-droid-x2-minor-update-1-3-418-is-now-live/#.T2HsKEGxFI4
I'm so avoiding this. Anyone else that decides to be brave and apply it, let us know the following:
Can you root with Zergrush
Can you SBF back to 2.3.4 without bricking your phone
Just for S and Gs, see if the bootloader is unlocked. I doubt it, but maybe a dev did something stupid? If so, save that update!
Thanks iBolski. (Or should I say Mr Ambassador )
If anyone has a phone info screen shot, that would be nice to see.
Also confirmation that VooDoo works?
Thats all the update brings? Why bother?
I am (just) thinking the kernel will be better for my Mx2 "Nandroid port".
jsgraphicart said:
Thats all the update brings? Why bother?
Click to expand...
Click to collapse
Exactly. I've tweeted to both Verizon and Motorola that I'm done with both of them. I'm looking for a new carrier and a new phone.
Verizon is reaching out right now asking why I'm so unhappy. Do I really have to answer that question? Give me a break!
iBolski said:
Per Talk Android, the X2 minor update is available.
http://www.talkandroid.com/99664-droid-x2-minor-update-1-3-418-is-now-live/#.T2HsKEGxFI4
I'm so avoiding this. Anyone else that decides to be brave and apply it, let us know the following:
Can you root with Zergrush
Can you SBF back to 2.3.4 without bricking your phone
Just for S and Gs, see if the bootloader is unlocked. I doubt it, but maybe a dev did something stupid? If so, save that update!
Click to expand...
Click to collapse
One question. DID ANYONE get the Soak???
If not, is this "really" what Moto was soak testing? What if it means... (gasp!)??
Edit: I don't think it is live yet, iBolski. Verizon's webpage still says "Coming Soon", like I'm supposed to be happy. I think the article is misguided... Did any brave soldier get the update and then apply it?
litetaker said:
One question. DID ANYONE get the Soak???
If not, is this "really" what Moto was soak testing? What if it means... (gasp!)??
Edit: I don't think it is live yet, iBolski. Verizon's webpage still says "Coming Soon", like I'm supposed to be happy. I think the article is misguided... Did any brave soldier get the update and then apply it?
Click to expand...
Click to collapse
I am signed up for the soak and I have not received it yet. I also tried to force the update to my phone just now and it is not pushing it.
I am going to be brave on this one because I have a back up phone I can fall on if anything does go wrong, but I am pretty much ready to just drop my DX2 like our Ambassador and just use something else until my upgrade....
I will let everyone know as soon as I get the email for the soak or if I can update to this at some point today...
Security update! I do not trust those bastards. I hope someone tries it so we know but I don't wish anyone to get stuck without root or able to sbf. Need a normal user that does not care about these things. I will not get close to it before we find out what it does.
gaad0701 said:
I am signed up for the soak and I have not received it yet. I also tried to force the update to my phone just now and it is not pushing it.
I am going to be brave on this one because I have a back up phone I can fall on if anything does go wrong, but I am pretty much ready to just drop my DX2 like our Ambassador and just use something else until my upgrade....
I will let everyone know as soon as I get the email for the soak or if I can update to this at some point today...
Click to expand...
Click to collapse
If/when you get it, check also just in case some dev made a "mistake" and left the kernel unlocked. Would be nice.
iBolski said:
If/when you get it, check also just in case some dev made a "mistake" and left the kernel unlocked. Would be nice.
Click to expand...
Click to collapse
I am no dev, can you walk me through how to do that? I am willing to try anything but I do not know how to do that off the top of my head.
gaad0701 said:
I am no dev, can you walk me through how to do that? I am willing to try anything but I do not know how to do that off the top of my head.
Click to expand...
Click to collapse
do you have the Android SDK on your computer? if you do just go into the folder where it's stored:
if windows C:/SDK (i believe)
if Linux /home/yourname/android-sdk-linux
it should have fastboot within there, but i'm bad at explanations, so iBolski'll walk you through it better than I can.
gaad0701 said:
I am no dev, can you walk me through how to do that? I am willing to try anything but I do not know how to do that off the top of my head.
Click to expand...
Click to collapse
From what I understand, you do the following, but back everything up to your external SD card first (do a nandroid) and you must have the Motorola USB drivers and Android SDK installed. Of course, since you've been flashing and SBFing, you definitely have those already installed:
Have your phone hooked up to your PC and type "ADB REBOOT BOOTLOADER"
The phone should reboot into the bootloader saying "Starting Fastboot Protocol Support"
When it's rebooted into the bootloader, type this in your DOS command window: "fastboot eom unlock"
Read the warnings. This WILL reformat your phone so be sure you've backed it up.
Tap Volume Down to switch to "Accept"
Now press Volume Up to actually "accept" the warning.
After that, you should be unlocked and formatted IF the bootloader and kernel were unlocked.
I could be wrong, but that's what I've read before.
http://forum.xda-developers.com/showthread.php?t=1136261
the thread w/ 1/3 of a mil hits!
IT'S all about the last 2 pics in the op.
skwoodwiva said:
http://forum.xda-developers.com/showthread.php?t=1136261
the thread w/ 1/3 of a mil hits!
IT'S all about the last 2 pics in the op.
Click to expand...
Click to collapse
iBolski said:
From what I understand, you do the following, but back everything up to your external SD card first (do a nandroid) and you must have the Motorola USB drivers and Android SDK installed. Of course, since you've been flashing and SBFing, you definitely have those already installed:
Have your phone hooked up to your PC and type "ADB REBOOT BOOTLOADER"
The phone should reboot into the bootloader saying "Starting Fastboot Protocol Support"
When it's rebooted into the bootloader, type this in your DOS command window: "fastboot eom unlock"
Read the warnings. This WILL reformat your phone so be sure you've backed it up.
Tap Volume Down to switch to "Accept"
Now press Volume Up to actually "accept" the warning.
After that, you should be unlocked and formatted IF the bootloader and kernel were unlocked.
I could be wrong, but that's what I've read before.
Click to expand...
Click to collapse
Good deal, I can do that for sure. I will make sure to update everyone as soon as anything comes through.
I won't be able to do any of the testing until I get home from work (roughly 6:30 central time) but I will keep trying to update throughout the day.
Thanks guys.
No updates have started to roll out yet....
Tapin' the Talk on the xSquared
gaad0701 said:
Good deal, I can do that for sure. I will make sure to update everyone as soon as anything comes through.
I won't be able to do any of the testing until I get home from work (roughly 6:30 central time) but I will keep trying to update throughout the day.
Thanks guys.
Click to expand...
Click to collapse
Still no update, nothing to report tonight probably. Hopefully I get something tomorrow so I have something to do at work...
Sent from my DROID X2
For those of you considering doing the update, you might want to take a look at these two threads on RootzWiki: rooted before update and important information regarding .621 update (I'm sure there are XDA equivalents of this by now, but these are two threads I'd been following previously for my brother's DX.)
Apparently using OTA rootkeeper (and ADB in some cases) it should be possible to keep root after the sbf *IF* you have SU backed up on /system/! SU cannot (CAN NOT) be restored from the SD card. Of course, any SBF/factory restore will lose SU and you'll be SOL until that gets sorted. Another problem (for us) is that we do not yet have an SBF file for this, so if anything goes awry, you could (potentially, not necessarily) be looking at a nice expensive paper weight until the SBF gets leaked.
This was also mentioned in the DX information thread, but if anyone is brave enough to update from rooted stock (using OTA Rootkeeper) and could get a nandroid, it could potentially be useful for anyone in the know (read: devs) to see what has changed in the update, so that we can examine alternative root methods. Unfortunately, most devs have moved onto newer/better phones so this may take a bit, but there is still a lot of dev for the DX (and the dx2 of course) so hopefully we can get something going (and presumably any exploit found on either phone should hopefully be useful for the other.)
Hey ibolski if VZW is reaching out it's a good thing.. Even if nothing is going to change in terms of their policy. Take the opportunity to reach out to them and let them know how we feel. Perhaps they can understand or at least listen to how HTC customers can feel better about unlocked bootloaders.
Sent from my MB870 using Tapatalk
coolpoete said:
Hey ibolski if VZW is reaching out it's a good thing.. Even if nothing is going to change in terms of their policy. Take the opportunity to reach out to them and let them know how we feel. Perhaps they can understand or at least listen to how HTC customers can feel better about unlocked bootloaders.
Sent from my MB870 using Tapatalk
Click to expand...
Click to collapse
I've tried. After I started doing that, the replies via twitter stopped. Figures.
listen I'm not saying anything, but just mentioning: I just tried to root my dad's Droid 2 Global and bricked it because the D2G got a "security update" around a week ago that kills root (Duh) and if you try to sbf back down it causes the phone to hard brick.
Now that may not be the case with this- who knows, that particular update went from 2.3.3 to to 2.3.4 and obv this one probably isn't going to update the kernel/bootloader/god knows but even still I find the closeness in time for these two OTAs suspicious, so be careful my flashaholic friends
Alright so new member here i have been using XDA to unlock and flash zip,kernals etc in android devices since 4 years.. i would like to thank this site :good:
Now straight to my point
Okay so I bought a Photon 4g 2 weeks ago and my bad luck its on 2.3.5 (I dont know if its factory 2.3.5 or OTA because i bought it from a friend who knows nothing about it) which means its bootlaoder is locked for good.. I did the ReservedOdm check and got "30000000000030003000100000000" which means =Electrify who performed OTA update to 2.3.5 and now stuck never unlocked) As the thread says.
Moreover I saw this thread http://forum.xda-developers.com/showthread.php?t=2072644 by @nickman529 and I was really shocked to see that a 45 pages thread with skilled people couldnt unlock the 2.3.5 version of MoPhon. (I did not read the whole thread but i guess you guys couldnt found a solution) So my question is still in 2014 there's no method to unlock this beastly phone? an updated android OS is a must for this phone. We should do something as there are hundreds of people still waiting for XDA guys to come up with a solution.
I am not a newbie in this developing thing nor I am a developer I know In's and outs of unlocking etc.
I would really appreciate if XDA skilled guys will work on this again atleast we can do something? unlocking a bootloader of a phone is not impossible right? just that we need to work again on this. I want to get this done. Thank You :good:
Some details of my phone:
I flashed superuser with "Photon Torpedo Direct" method so I have root enabled
Build: 4.5.1A-1 SUN254_13
2.3.5
Hope I will get some replies as this is my first thread on XDA
mopo
whizinc said:
Alright so new member here i have been using XDA to unlock and flash zip,kernals etc in android devices since 4 years.. i would like to thank this site :good:
Now straight to my point
Okay so I bought a Photon 4g 2 weeks ago and my bad luck its on 2.3.5 (I dont know if its factory 2.3.5 or OTA because i bought it from a friend who knows nothing about it) which means its bootlaoder is locked for good.. I did the ReservedOdm check and got "30000000000030003000100000000" which means =Electrify who performed OTA update to 2.3.5 and now stuck never unlocked) As the thread says.
Moreover I saw this thread http://forum.xda-developers.com/showthread.php?t=2072644 by @nickman529 and I was really shocked to see that a 45 pages thread with skilled people couldnt unlock the 2.3.5 version of MoPhon. (I did not read the whole thread but i guess you guys couldnt found a solution) So my question is still in 2014 there's no method to unlock this beastly phone? an updated android OS is a must for this phone. We should do something as there are hundreds of people still waiting for XDA guys to come up with a solution.
I am not a newbie in this developing thing nor I am a developer I know In's and outs of unlocking etc.
I would really appreciate if XDA skilled guys will work on this again atleast we can do something? unlocking a bootloader of a phone is not impossible right? just that we need to work again on this. I want to get this done. Thank You :good:
Some details of my phone:
I flashed superuser with "Photon Torpedo Direct" method so I have root enabled
Build: 4.5.1A-1 SUN254_13
2.3.5
Hope I will get some replies as this is my first thread on XDA
Click to expand...
Click to collapse
i've same problem and it will be good to resolve this issue by xda devs... this is really good phone and is sorrowful to see how this topic stayed inattentive
ultimo123 said:
i've same problem and it will be good to resolve this issue by xda devs... this is really good phone and is sorrowful to see how this topic stayed inattentive
Click to expand...
Click to collapse
yeah i think the Skilled XDA guys just gave up on this phone and its a shame that these skilled guys couldnt figure out a way to unlock this MoPhon atleast we can start work on this again COME ON Guys! the thread is being inactive please show some humanity.
Maybe it will be solved by developers sooon .. They could be working on it .. will be a way to get rid of this problem ..
kaleemhunter said:
Maybe it will be solved by developers sooon .. They could be working on it .. will be a way to get rid of this problem ..
Click to expand...
Click to collapse
i am afraid to tell you brother but there is no development under process of photon 4g the people on 2.3.5 are locked for good and its a misery for the developers too that they couldnt unlock it.. A replacement of another new model will be the only way to use new android versions lol :good:
check out Motorolla Moto G it has official upgrade of kitkat its affordable too :good:
photon
.. I've photon 2.3.5 and locked for sure.. hoping on dev to get a way out there..
come on guys I've got a few posts on here over the years about this lol I have a new account here since so I don't know where all those posts are.
sadly I have no clue what I did or how the heck I did it!
I bought the photon the day after it came out and used it for quite a while on sprint. I received the ota update to 2.3.5.
then when my contract expired I spent hours and hours and finally rooted and unlocked my phone and put it on straight talk. it was on the ota update so I was told I wouldn't be able to do it but somehow I did.
more recently I have a new issue with mine which is why I am back on here again but I am very disappointed I never had the chance to figure out how I did it.
-boxorandyos
<sent from my nexus4>
boxorandyos said:
come on guys I've got a few posts on here over the years about this lol I have a new account here since so I don't know where all those posts are.
sadly I have no clue what I did or how the heck I did it!
I bought the photon the day after it came out and used it for quite a while on sprint. I received the ota update to 2.3.5.
then when my contract expired I spent hours and hours and finally rooted and unlocked my phone and put it on straight talk. it was on the ota update so I was told I wouldn't be able to do it but somehow I did.
more recently I have a new issue with mine which is why I am back on here again but I am very disappointed I never had the chance to figure out how I did it.
-boxorandyos
<sent from my nexus4>
Click to expand...
Click to collapse
brother we are talking about the bootloader unlock of photon 4g devices on 2.3.5 please clear that did you unlocked the bootloader or just unlocked your phone?? and whats your the problem you are facing now? let me know. I can help
I can't guarantee but I figured what I did would be called unlocking the bootloader. I do know I received the ota update as I remember having trouble with the phone after doing it so I was on 2.3.5 for sure. I do not remember what I did when unlocking it but it was completely factory plus the ota when I started and by the time I was done I had root access and I was running cm7 and I could put in my straight talk sim card and I had talk, text, mms, and data. that would be an unlocked bootloader if I'm right?
what I'm facing now is I get a message saying something about the modem did not start when ever I try turning the phone on.
-boxorandyos
<sent from my nexus4>
boxorandyos said:
I can't guarantee but I figured what I did would be called unlocking the bootloader. I do know I received the ota update as I remember having trouble with the phone after doing it so I was on 2.3.5 for sure. I do not remember what I did when unlocking it but it was completely factory plus the ota when I started and by the time I was done I had root access and I was running cm7 and I could put in my straight talk sim card and I had talk, text, mms, and data. that would be an unlocked bootloader if I'm right?
what I'm facing now is I get a message saying something about the modem did not start when ever I try turning the phone on.
-boxorandyos
<sent from my nexus4>
Click to expand...
Click to collapse
if you have your photon with you right now then take a look at its bootloader open it and it must say UNLOCKED if not then your bootloader is still locked..
so the modem error comes and the mobile doesn't works?? I think its a hardware problem as far as i know
yea it does say unlocked in the corner of the bootloader screen.
I got the error when I tried flashing an update to my ROM. I don't know whether it flashed something that did that our if it was just coincidence that something went wrong with the hardware at the same time. I tried flashing it back to the old version and that did not fix the problem.
-boxorandyos
<sent from my nexus4>
boxorandyos said:
yea it does say unlocked in the corner of the bootloader screen.
I got the error when I tried flashing an update to my ROM. I don't know whether it flashed something that did that our if it was just coincidence that something went wrong with the hardware at the same time. I tried flashing it back to the old version and that did not fix the problem.
-boxorandyos
<sent from my nexus4>
Click to expand...
Click to collapse
what really? it says unlocked that it means the bootloader is unlocked how the hell did you unlocked your bootloader on 2.3.5? you have to remember it brother?
I honestly have no clue this was only like the third phone I ever unlocked and I've done dozens since. this was back right after the ota came out.
all I remember is I spent days and days trying to figure it out. if I had another phone I might work on it again as that's a really nice phone but I don't really expect to ever land on one of them again.
-boxorandyos
<sent from my nexus4>
boxorandyos said:
I honestly have no clue this was only like the third phone I ever unlocked and I've done dozens since. this was back right after the ota came out.
all I remember is I spent days and days trying to figure it out. if I had another phone I might work on it again as that's a really nice phone but I don't really expect to ever land on one of them again.
-boxorandyos
<sent from my nexus4>
Click to expand...
Click to collapse
I have an OTA-locked one that's fairly cosmetically beat up. New replacement battery. USB port cracked off just enough that normal USB cables work but car dock does not. Otherwise I *think* it's fine - I gave up on peetr's decrapped stock ROM, which is good I gotta say, and bought an unlocked one on eBay.
I'd give it to you free but I am literally sweating out my rent check. Would you be willing to part with $25 for it, includes shipping?
A friend brought me a photon of his he is wanting to use with straight talk Sim , It is on 2.3.5 ota I believe but don't know . Have tried to unlock the boot loader but keep getting (FAILED (remote: (00180001))) when I try to get the unlock key. It has root but does not register the straight talk Sim and I felt unlocking the boot loader would help me fix this issue but am finding I can't .can anyone help am open to any suggestions. Pls know though I am still learning how to use the adb, fastboot, and know little about rsd (can't get it to even pick up the phone)
Sent from my XT1080 using XDA Premium 4 mobile app
def2moto said:
I have an OTA-locked one that's fairly cosmetically beat up. New replacement battery. USB port cracked off just enough that normal USB cables work but car dock does not. Otherwise I *think* it's fine - I gave up on peetr's decrapped stock ROM, which is good I gotta say, and bought an unlocked one on eBay.
I'd give it to you free but I am literally sweating out my rent check. Would you be willing to part with $25 for it, includes shipping?
Click to expand...
Click to collapse
woops I must have missed this. I can do that as soon as I get some people to pay what they owe me. right now I am behind on some bills by quite a bit but I am hoping that will get taken care of shortly. do bug me about it and I'll do that.
-boxorandyos
<sent from my nexus4>
Hi guys, I'm new to ARM devices, but I have a lot linux experience and a fair amount of Android experience, as I've done some device porting work at android-x86.org.
I was recently given a photon 4G with a locked bootloader, 30000000000030003000100000000
My question is, what is so special about the bootloader that it can't be replaced by another bootloader. I was just looking at the thread to put Arch Linux on the Photon, but that thread seems to have stalled and I can not ask any questions there because I do not have 10 posts yet.
I am guessing the kernel image cannot be replaced with a locked bootloader? I read the post by peetr_ about SBF's & CG's & signatures, but when are the signatures checked, at flash time or every boot? I dd'd the boot partition to /tmp/boot.img and pulled it to my linux workstation but I've not been able to mount it. Mount thinks it's NTFS, is that what a .smg is? NTFS in some sort of container?
boxorandyos said:
woops I must have missed this. I can do that as soon as I get some people to pay what they owe me. right now I am behind on some bills by quite a bit but I am hoping that will get taken care of shortly. do bug me about it and I'll do that.
-boxorandyos
<sent from my nexus4>
Click to expand...
Click to collapse
Sure thing, I starred the notice of this in my email program and will get back on this thread next time I go thru my backlog if I haven't heard from you.
Funny how we're all in some way participating in all this work that manufacturers should've done, and a lot of us are broke.
---------- Post added at 01:20 PM ---------- Previous post was at 01:12 PM ----------
fuzzy7k said:
Hi guys, I'm new to ARM devices, but I have a lot linux experience and a fair amount of Android experience, as I've done some device porting work at android-x86.org.
I was recently given a photon 4G with a locked bootloader, 30000000000030003000100000000
My question is, what is so special about the bootloader that it can't be replaced by another bootloader. I was just looking at the thread to put Arch Linux on the Photon, but that thread seems to have stalled and I can not ask any questions there because I do not have 10 posts yet.
I am guessing the kernel image cannot be replaced with a locked bootloader? I read the post by peetr_ about SBF's & CG's & signatures, but when are the signatures checked, at flash time or every boot? I dd'd the boot partition to /tmp/boot.img and pulled it to my linux workstation but I've not been able to mount it. Mount thinks it's NTFS, is that what a .smg is? NTFS in some sort of container?
Click to expand...
Click to collapse
Forgive me if I'm telling you stuff you already know, but here are a few random tidbits of info:
The OTA update blew a hardware fuse which somehow prevents bootloader unlock by any known methods
The only ROMs that can be flashed with the bootloader locked are ones using the stock kernel as-is, like peetr's ROM, so I think your guess about the kernel image becoming set in stone is correct.
Don't know anything else but I also have an OTA-locked one which I could run stuff on and get you output, if you want it, and an unlocked one (pre OTA update) running CM9. As long as it doesn't mess up my devices I could provide you with debug info.
def2moto said:
Sure thing, I starred the notice of this in my email program and will get back on this thread next time I go thru my backlog if I haven't heard from you.
Funny how we're all in some way participating in all this work that manufacturers should've done, and a lot of us are broke.
[/LIST]
Click to expand...
Click to collapse
I will try an remember to get back to you
there is one thing I was just thinking about that I do remember thinking about afterwards. whatever I did that made it work may have stemmed from what I later discovered was a corrupted file. I remember downloading file after file and trying to flash dozens of different files. every time I was getting all sorts of errors. suddenly tho I got a different error and after that when I would try throwing commands at the phone I would get completely different responses. my memory is very limited of it all but I thought I was completely screwed.
somehow tho I suddenly had a phone with the pre ota software on it.
whatever exactly it was that I messed up I have no clue without trying to re create the story.
-boxorandyos
<sent from my nexus4>
Hey guys. Nickman529 here. Sorry I haven't ever updated anything on that thread. I don't have the MoPho anymore but I'd be willing to start up development if someone would wanna send me one or donate the PayPal funds for such. I hear your cries.