Hello, I have been a member of the forums for a while and read up on the posts, but I haven't been doing any modding for YEARS. I was on an OG EVO rooted with MIUI rom and I have been running that. So I recently saw a photon on Ebay for peanuts, and they said that it kept rebooting. Thinking myself clever I bought it saying they probably just screwed up trying to flash it.
I got it 4 days ago and I have been making the situation WORSE since I got it!! When I first got it, it booted to the sprint homepage. I got a "no signal" red indicator. I tried to activate it, but couldn't. called sprint, they couldn't and said it's probably because of the no signal. I read a few hundred posts and decided to try to flash. I DL'd RSD lite and flashed the electrify USC file. Now it boots up as US CELLULAR, and I still have no signal. Anytime I insert an sd card it reboots. It reboots randomly often. (5-10 times per hour) WIFI works though, (I can use it as an Ipad Micro.) I have downloaded files, tried a lot of fixes, with no luck. I think it's safe to say I bit off more than I could chew being out of practice and pretty noobish, but any tips would be greatly appreciated... The last thing I tried was moto fastboot to flash the boot img and recovery img. I keep getting an error (windows could not find moto fast boot). I can go into recovery by holding power and vol down, and RSD by holding power and vol up...And here I am...
I also get the flash failed error (phone failed to re-enumerate) ever since flashing the electrify file
what version of GB does it have on it?
if you mean by GB android (just a guess, I have no idea what you mean!) It's 2.3.5
There were certain photons that would randomly reboot for no reason. I had one and exchanged it for another one and have been fine since.
Unfortunately there was a hardware issue that caused the rebooting. Nothing software related can fix it.
Could try a sprint store.
gizmatic said:
if you mean by GB android (just a guess, I have no idea what you mean!) It's 2.3.5
Click to expand...
Click to collapse
2.35 is gingerbread
gizmatic said:
Hello, I have been a member of the forums for a while and read up on the posts, but I haven't been doing any modding for YEARS. I was on an OG EVO rooted with MIUI rom and I have been running that. So I recently saw a photon on Ebay for peanuts, and they said that it kept rebooting. Thinking myself clever I bought it saying they probably just screwed up trying to flash it.
I got it 4 days ago and I have been making the situation WORSE since I got it!! When I first got it, it booted to the sprint homepage. I got a "no signal" red indicator. I tried to activate it, but couldn't. called sprint, they couldn't and said it's probably because of the no signal. I read a few hundred posts and decided to try to flash. I DL'd RSD lite and flashed the electrify USC file. Now it boots up as US CELLULAR, and I still have no signal. Anytime I insert an sd card it reboots. It reboots randomly often. (5-10 times per hour) WIFI works though, (I can use it as an Ipad Micro.) I have downloaded files, tried a lot of fixes, with no luck. I think it's safe to say I bit off more than I could chew being out of practice and pretty noobish, but any tips would be greatly appreciated... The last thing I tried was moto fastboot to flash the boot img and recovery img. I keep getting an error (windows could not find moto fast boot). I can go into recovery by holding power and vol down, and RSD by holding power and vol up...And here I am...
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/showthread.php?t=1798145
You flashed a sbf and now you have US Cellular, but there are more files to flash to get back Sprint service. It's outlined in the thread. I soft-bricked my phone (bootloop that I couldn't get out of) followed the directions and I'm back up. You'll need to know how to root (http://forum.xda-developers.com/showthread.php?t=1819660) and install Bootstrap (can't find the link but it's probably in here http://forum.xda-developers.com/showthread.php?t=1393519)
thanks a lot!! but am not out of the woods yet. I followed the instructions from the link and using bootstrap I was able to flash back to Sprint, so I am back where I started. The phone boots up, I have a sprint startup and home screen, I flashed the 2.3.5 modules through bootstrap But I still have the no signal red icon.
##786# shows me I have a wimax mac id, Wimax chipset version, Wimax Channel Plan, but mobile number is blank, MSID is blank, SW Version Version.45.4.13.MB855.Sprint.en.us, OS version 2.3.5, Radio is Blank, HW Version unavailable, PRL Blank, PRI Version 1.3, life timer 2233, life calls 1237, Recondition Status unavailable, ESN Unavailable, MEID Unavailable, Activation Date Unavailable
Have you tried fast boot -w command?
Edit: It will wipe your data, might be able to activate afterwards
Sent from my sunfire using xda premium
have you flashed the 2.3.5 ota unbrick sbf? and if youve flashed all the files and are on the stock sprint rom you could try ##epst# and do a data reset which will take you to reactivate the phone
Related
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Have you tried to reinstall the motorola driver?
Yes, when I first "lost" RSD support and since the current "Failed to boot 2" message.
It has the flash interface when I plug it in, but the motorola software dosent see it, same with RSD. just like nothing is plugged in.
Why not put it into fastboot mode when it reboots and then flash a different file?
phobos512 said:
Why not put it into fastboot mode when it reboots and then flash a different file?
Click to expand...
Click to collapse
It won't boot into any other mode, upon putting the battery in, it shows the dual core logo for about 1.5-2 seconds that pops up the "Failed to boot 2" message and starting RSD mode.
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Phalanx7621 said:
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ya, from what I can tell its Motorola locking me out for using an modified rom. But I think that I should be able to return to a stock firmware using RSD lite or the Motorola software restore from thier site, but neither see my phone connected. This leads me to belive that somewhere in the process the RSD protocol got messed up. Now I really don't know much, just enough to be dangerous. So if theres anyone that can tell me if I'm even looking the right direction.
And if I am right is there anything I could possibly do?
gjRabbit said:
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Click to expand...
Click to collapse
Hey man, I have the same problem with you.. have you some progress for that..
I find some infor from forum that this kind of hard brick can be solved by using the developping cable to reflash the sbk file, this method is pending at the SBK file is unavailable which is not released out by MOtorola.. I find a one of my friend who is working in MOTO (Tianjing, CHINA) to see my device, I hope he can help me to unbrick my phone.. when i have good news, I'll update it.
Hello guys. I bought a used dell streak which worked before I flashed streakdroid 2.4.4. I flashed the amss and dsp1 and everything matches when I check the phone information. I tried searching for mobile networks and AT&T appears but when I select it, it says "unable to connect to network please try again later" or "unable to register". Whats confusing is that I get a voicemail notification letting me know I have voicemail but when I click on it, I get "mobile network unavailable"
I rarely ask questions because when I'm stuck on something it is usually a simple fix. I've flashed every custom rom and matching baseband on the front page of the android development section and the Official PKG (351, 353, 206). I've done multiple system wipes etc. Im not sure what else I need to do. I've never worked on a phone for more than 4 hours and Im currently on my 11th on this damn dell streak
So is there a way to find out what region this dell streak came from to make this process easier, I dont want to have to try flashing every single update.pkg and baseband.
Or is there a general solution to this issue hidden in the archives of the internet?
Im soooo confused so any help would be greatly appreciated
liquidburns said:
Hello guys. I bought a used dell streak which worked before I flashed streakdroid 2.4.4. I flashed the amss and dsp1 and everything matches when I check the phone information. I tried searching for mobile networks and AT&T appears but when I select it, it says "unable to connect to network please try again later" or "unable to register". Whats confusing is that I get a voicemail notification letting me know I have voicemail but when I click on it, I get "mobile network unavailable"
I rarely ask questions because when I'm stuck on something it is usually a simple fix. I've flashed every custom rom and matching baseband on the front page of the android development section and the Official PKG (351, 353, 206). I've done multiple system wipes etc. Im not sure what else I need to do. I've never worked on a phone for more than 4 hours and Im currently on my 11th on this damn dell streak
So is there a way to find out what region this dell streak came from to make this process easier, I dont want to have to try flashing every single update.pkg and baseband.
Or is there a general solution to this issue hidden in the archives of the internet?
Im soooo confused so any help would be greatly appreciated
Click to expand...
Click to collapse
Do a cache wipe
dalvik cache wipe,
"DELL" factory reset
Re-Flash gs244, then straight away do the first 3 steps again.
This time, flash without the simcard inserted.
When it first boots up after the factory reset, turn it off, put your sim in and power on.
I had the same prob as you with a uk network sim, after doing the above, it worked fine, im pretty sure it will sort your issue.
graemeg said:
Do a cache wipe
dalvik cache wipe,
"DELL" factory reset
Re-Flash gs244, then straight away do the first 3 steps again.
This time, flash without the simcard inserted.
When it first boots up after the factory reset, turn it off, put your sim in and power on.
I had the same prob as you with a uk network sim, after doing the above, it worked fine, im pretty sure it will sort your issue.
Click to expand...
Click to collapse
I have tried this step 3 times to no avail. When I go into settings>Wireless & Network Settings>Mobile Networks >Network Operators then select Search Networks two networks appear related to my phone company. When I select one option it says
Your sim will not register to this network
The second options gives me this response
Unable to connect to the network at this time. Please try again later.
Isnt the error code for a bad radio blinking lights? So why am I getting this particular error code.....
Is there a deeper menu within the dell streak to access more radio settings?
Is there a way to find out what region this phone is from so I can flash the original update.pkg?
Will the packers win the superbowl.......
Thanks for the help so far, this seems to be a common problem. I searched through several pages of Google, I even resorted to using bing and yahoo but I haven't found one consistent solution. Lets make one guys.
Also after dell factory reset I get this error Default NV checked #2 which doesnt allow me to go straight into the update.zip streakdroid menu then it resets the phone.
Do yourself a favor and don't install GingerStreak. Development has essentially stalled on that ROM, leaving it in a very buggy state compared to other ROMs. I recommend DSC, but with the GKernel that's available in Android Development instead of the kernel that comes with the ROM. The combination has been rock solid stable on my device, without any screens of death or problems with WiFi.
Ive flashed every single update.pkg from this list and have my Dell Streak 5 currently on 1.6 At&t retail 106 rom
http://mirror2.streakdroid.com/manii/
None of the packages work. On the Rodgers I would get a
Emergency Calls only status
Other than that I just have 4 bars with an x over them
I even erased all user data via fastboot
Ive used QDL at least 8 times
Does anyone else have any suggestions?
Is there a key code via fastboot menu to get further into the mobile network settings?
Any help would be greatly appreciated
Does your Streak still boot after using fastboot -erase? That's a big no-no. Usually results in a brick that only can be cured by disassembling the Streak and flashing an image of the internal MicroSD onto the card.
I am assuming that you flashed the recovery for the ROM you wanted to put on the Streak before trying to flash the ROM? You likely will have to search for some ancient posts, but if flashing the desired ROM's recovery image and then flashing the ROM doesn't work, you have to prepare the Streak to accept newer ROMs. Those ancient posts I mentioned detail the method to get units like yours to run newer versions of Android.
Strephon Alkhalikoi said:
Does your Streak still boot after using fastboot -erase? That's a big no-no. Usually results in a brick that only can be cured by disassembling the Streak and flashing an image of the internal MicroSD onto the card.
I am assuming that you flashed the recovery for the ROM you wanted to put on the Streak before trying to flash the ROM? You likely will have to search for some ancient posts, but if flashing the desired ROM's recovery image and then flashing the ROM doesn't work, you have to prepare the Streak to accept newer ROMs. Those ancient posts I mentioned detail the method to get units like yours to run newer versions of Android.
Click to expand...
Click to collapse
I know fastboot erase is a bad idea but at this point not having a mobile signal makes this device useless to me anyways. I did that twice actually.
I am currently running official rom update package 360 or Android 2.2.2 the latest from retail. I am still having the same issue.
I have spend a good portion of my day for the past 4 days reading archives of discussions both here and on madaco. No on seems to have a consistent solution to this problem. Ive read that sticking a business card under the battery works, the order of flashing should fix it, I mean the solutions are all over the place and I tried all of them but I still have the same problems.
I haven't read every single Q&A post but I have read almost everything under the Dell Streak 5 XDA board pertaining to this issue. I've also flashed every single available update package with match recovery and baseband with no results.
I feel like I've failed at this project and I am never going to get the time or the effort I put into this device back unless I can get it to work so this is just beyond frustrating.
Any other suggestions would be greatly appreciated.
Have you tried using a different sim card? Every now and then there's a sim that wont work on it but will work on a different device.
TheManii said:
Have you tried using a different sim card? Every now and then there's a sim that wont work on it but will work on a different device.
Click to expand...
Click to collapse
I've used a good variety of sim cards, none of which work.
Any other suggestions?
sim
Sorry your still having this issue.
Ive googled and found nothing consistent apart from the obvious that already been mentioned.
Daft question i know but, are you absolutley 100% certain that this phone has not been blocked by your network via IMEI?
Sounds daft i know but people using phone / Tablets are reporting on consisten problems with networks and IMEI.
I would not attempt QDL anymore, if it didnt fix it the first time then that wont help your cause.
I think going back to ground zero is the place to sart, can you gain access to internal memory card, mine i can, i cut away the piece of plastic in the guide to allow easy access, i replaced the internal 2gig card with an 8gig class 10, just to note, the 2gig card was shot and was nothing more than a standard generic unbranded card, i do still have it sat around.
That would be my next step, wipe the phone, stick a diff card in and start again with STOCK 360 and matching recovery, i agree with the quote of avoiding gs, too damn buggy and problematic.
Let me know how youre getting on with it.
graemeg said:
Sorry your still having this issue.
Ive googled and found nothing consistent apart from the obvious that already been mentioned.
Daft question i know but, are you absolutley 100% certain that this phone has not been blocked by your network via IMEI?
Sounds daft i know but people using phone / Tablets are reporting on consisten problems with networks and IMEI.
I would not attempt QDL anymore, if it didnt fix it the first time then that wont help your cause.
I think going back to ground zero is the place to sart, can you gain access to internal memory card, mine i can, i cut away the piece of plastic in the guide to allow easy access, i replaced the internal 2gig card with an 8gig class 10, just to note, the 2gig card was shot and was nothing more than a standard generic unbranded card, i do still have it sat around.
That would be my next step, wipe the phone, stick a diff card in and start again with STOCK 360 and matching recovery, i agree with the quote of avoiding gs, too damn buggy and problematic.
Let me know how youre getting on with it.
Click to expand...
Click to collapse
I ended up just liquidating the phone and cutting my losses. I dont think it was blocked from the network because I tried several SIM cards from different networks. For all I know it it could have been a bent SIM connection or something wacky. I am leaning towards the idea of it being hardware related but I gave it my best shot
Friends, I am also in the same state now. I bought the dell streak from one of our members, and it worked for few weeks. After that, I am getting that signal bar with X mark on it. I have tried all the options, but of no luck.
I spent almost my 6 months savings on this phone and it's really making me sleepless. Request your kind suggestions to address this.
hi
i had same problem about a month ago, i just kept restarting phoning, pulling battery out and i gave up, then after leaving it for a couple of hours it was working......
^^ Thanks friend for your reply. I have been doing the same, doing the factory resetting and trying the various options. But, of no luck.
Any concrete solution for this problem? I appreciate all your inputs.
What I would suggest for all of you is to go back to Froyo by flashing stock Dell update packages for your respective regions and see if you regain signal
Sent from my cm_tenderloin using Tapatalk 2
^ Thanks for the suggestion. I did that try that, but didn't work
tech4pk said:
^ Thanks for the suggestion. I did that try that, but didn't work
Click to expand...
Click to collapse
If you flashed a stock Froyo ROM for YOUR SPECIFIC region, did a factory reset and still can't get a signal then your problem is hardware related...
Sent from my cm_tenderloin using Tapatalk 2
^^ Yeah, that's my big worry!! It seems to be a hardware related. I got this phone from one of the our members, and it has already having some hw issues like the buttons are gone inside, right side bezel is very loose, and all (unfortunately, the seller has not mentioned all these issues in his post)
Can the dell warranty applies internationally?
tech4pk said:
^^ Yeah, that's my big worry!! It seems to be a hardware related. I got this phone from one of the our members, and it has already having some hw issues like the buttons are gone inside, right side bezel is very loose, and all (unfortunately, the seller has not mentioned all these issues in his post)
Can the dell warranty applies internationally?
Click to expand...
Click to collapse
It applies only in the country it was purchased if it hasn't expired and with a valod letter of release from the original owner
Sent from my cm_tenderloin using Tapatalk 2
^^ yeah, checked my local dell service guys and they are not supporting this. I think that this is now turning into an expensive brick!
Hey all,
I did my searching for the last several hours, and am feeling pretty weak. I know there are several other posts with this error - but please let me explain my situation.
Phone was running 2.3.6. I am unsure how it was originally unlocked (carrier unlocked) and bought it used. To my knowledge it did not have root access... (though the advert said it did - running SU in Terminal to show if it had access failed)
I tried doing a factory reset on the phone because it kept acting weird. Just rebooting 10 times a day, and wifi not working either.
Since the reset the phone has not made it past the M Dual Core screen.
Edit as I type: As I type this, I FINALLY got into recovery mode. It took a long time... is that normal? I mean.. loongggg. Now i see other posts state I just need to click the bottom right corner above the search key and I should be on the way to recovering the device...
This however is not working...
I will keep the phone plugged in over night and see if it just needed more time I suppose. Can you guys recommend anything?
I am on win7 - should have the device drivers installed (though, Windows doesn't seem to recognize this with a notification bubble). I know the phone was not on USB Debug Mode when I clicked 'factory reset'.. would it have retained this?
I will update as i have more information.. otherwise if I am missing something please let me know.
Thanks again,
-k
Try booting into recovery mode by holding volume down while turning on. When the menu appears keep pressing volume down until it says android recovery and then press volume up to select it. If an android Guy with a warning sign shows up, press volume down and up. A menu should appear soon. Try to do a data wipe and factory reset from there.
Sent from my MB860 using XDA App
Hi ar31791, thank you for the reply.
That worked to put me into a recovery mode - very nice. Is the button combo different depending on the version of android your'e running, or just phone dependent? I appreciate that.
Couple follow up questions if you guys don't mind and can help
- after the factory reset - my boot time is incredibly slow.... like 30 minutes to boot kinda thing. I tried to factory reset several times since, and its the same issue.
- my data is not working on the phone. I used the apn suggestions from all sites I've found, rebooted (took a while) tried data roaming, etc, but it just doesn't work. I have a decent idea that the apn's are correct because the mms apn worked fine with a test picture message.
My main concern is the incredible lengthy boot time and the data no longer working. The issue with wifi still showing 'error' when enabling it was not resolved by the reset (I didn't think it would - I was reading other posts where it is suspected as a hardware issue).
Thanks again for the reads, and replies. I appreciate the help!
-kenny
You need romracers or cwm. Unless yer going to stay stock.
Sent from my MB860 using xda premium
Is this an att or a rogers/international phone? Best bet would be to flash pudding and than cwm + custom roms
hey again- thank you for the replies.. seriously. much appreciated.
phalanx, i dont mind staying stock but would that not allow the data connection to work correctly? i found a few posts based on the romracer. i lack the hands on experience, but it looks like i just need to follow the steps for an adb push and then install eh?
you mention staying stock, is that an option? info on my setup below
crnkoj, i am running a bell phone on a fido network in canada. bought on ebay pre unlocked. i do not bekieve it is rooted. phone, mms and text work fine, it seems to be a problem finding a data network at this moment.
thanks again guys, ill be taking a look into the tutorials for romracer and cwm, and giver a shot. lemme know if you have any further ideas, questions or anything you think i might need to know.
edit.. also, whats the deal with the crazyyyyy long boot up time?
kenny
(send from a mobile.. please excuse any typos or punctuation errors)
No its just that with an unlocked bootloader you can flash a new.recovery and that makes it easier to flash roms and also kernels and radios. Kernels and radios can affect your ability to connect with data and can even affect the speeds.
Sent from my MB860 using xda premium
I had a similar situation. So, i did a full wipe installed the rom did another full wipe then installed the appropriate kernel and booted it up. I believe you nedd to install the right kernel per the instructions. It will mot boot if the kernel is not correct.
Sent from my MB860 using xda premium
Thanks again guys,
Man it's a funny issue. I am always able to get in and factory wipe the device, but it seems that sometimes that damn M screen will sit forever. I left it over the course of a movie and a half (probably 3 hours) and that screen was still just sitting there.
I get into the fastboot menu easy enough before that screen hangs, and sometimes i can get into the Boot Android (without BP) (I believe it's called) and sometimes it hangs, and sometimes it works.
Other times, like right now, it boots just fine and kinda fast.
I am having an issue with the RSDLite application recognizing my phone. It did once - then hung at 94% flash of the pudding tutorial. I didn't realize the tutorial says to keep the phone plugged in for 10 minutes even after a fail to see if it actually completes. I havent been able to have the software recognize the phone since- I've installed and reinstalled the motorola drivers, set the phone to usb debugging, and was able to try 2 computers, and 2 different cables. I'll giver another shot though.
I am pretty sure my boot loader was unlocked (as I said I had this all done from an ebay purchase) so I think I can just proceed to the flashing, but if there is a way to confirm that it is indeed locked, I'll take the advice.
The more I read though, it looks like I might just need to send this beast in for a service call with Motorola, because of that damn wifi "error" error. I'd hate to go through all this and realize it still will not work.
Thanks for the replies, I'll always take more suggestions, and if you guys think I'm on the wrong path, let me know. I'll keep searchin dem' forums
If your bootloader is unlocked it will say unlocked in white letters on that M boot logo screen. Did you run "fastboot oem unlock" after the rsd flash?
Sent from my MB860 using XDA App
Good afternoon folks,
I had a "situation" where I found myself missing some apparently critical "bloatware" on my phone. Came up with lots of errors and a lot of functions no longer, well, functioned. Got too carried away I guess.
I had done a system backup with Titanium Backup. I initially tried just restoring some of the apps. Problem was, it just sat there saying restore. Just stuck. So I thought, hey, I have it backed up, I will do a factory reset. I did this, only then to find out that my backup was located on the INTERNAL sdcard not sdcard-ext, so all of a sudden I have no backups.
I do have access to another Electrify, if it would help. What I then decided to do was try downloading a factory rom for my phone. I downloaded "1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.rar" off of the teamuscellular.com page. I booted the phone in RSD mode, restored it (three times now actually), and every step seemed to go fine (RSD even says it finished fine). But on the last step when RSD says it is rebooting the phone, at the very end, it comes up with an error :
"Failed to boot 4
starting in rsd mode"
I have read elsewhere where people say it is related to the battery. I had a 60% charge for the first two times I did this process, the last time I used the battery from the other phone which was at 95% plus. So far I have not been able to get past this.
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
In case this might help figure out the issue, here are some details from the phone :
System version - 45.1.190.MB853.USC.en.US
Model number - Motorola Electrify
Android version - 2.3.5
Also worth noting, I did not see anything on the screen ever indicating I was "unlocked".
What I want when this is done and over with is to get the phone back and working stock, root, and make barnicle wifi work. Any advice would be most helpful, I am really kind of freaking out here.
H-E-L-P!
Thanks,
ledoktre said:
Good afternoon folks,
I had a "situation" where I found myself missing some apparently critical "bloatware" on my phone. Came up with lots of errors and a lot of functions no longer, well, functioned. Got too carried away I guess.
I had done a system backup with Titanium Backup. I initially tried just restoring some of the apps. Problem was, it just sat there saying restore. Just stuck. So I thought, hey, I have it backed up, I will do a factory reset. I did this, only then to find out that my backup was located on the INTERNAL sdcard not sdcard-ext, so all of a sudden I have no backups.
I do have access to another Electrify, if it would help. What I then decided to do was try downloading a factory rom for my phone. I downloaded "1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.rar" off of the teamuscellular.com page. I booted the phone in RSD mode, restored it (three times now actually), and every step seemed to go fine (RSD even says it finished fine). But on the last step when RSD says it is rebooting the phone, at the very end, it comes up with an error :
"Failed to boot 4
starting in rsd mode"
I have read elsewhere where people say it is related to the battery. I had a 60% charge for the first two times I did this process, the last time I used the battery from the other phone which was at 95% plus. So far I have not been able to get past this.
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
In case this might help figure out the issue, here are some details from the phone :
System version - 45.1.190.MB853.USC.en.US
Model number - Motorola Electrify
Android version - 2.3.5
Also worth noting, I did not see anything on the screen ever indicating I was "unlocked".
What I want when this is done and over with is to get the phone back and working stock, root, and make barnicle wifi work. Any advice would be most helpful, I am really kind of freaking out here.
H-E-L-P!
Thanks,
Click to expand...
Click to collapse
did you install the moto drivers? if you're unlocked be sure to flash 2.3.4 not 2.3.5
Good afternoon,
I have installed the moto drivers. I am on Windows 7 64 bit (dual boot with Linux Mint Debian 64). I installed "MotoHelper_2.1.40_Driver_5.5.0.exe", and was using RSDLite5.6.
As far as I know, the phone was locked. Rooted, but locked. Some say it will actually say on the screen 'unlocked', mine does not say anything like that.
Thanks,
Just to make sure it's not a battery issue, there is free battery swap if you can run by a USCC store. But I think you're right, it's probably not that. Wish I could help you more, but it stumps me.
ledoktre said:
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
Click to expand...
Click to collapse
From the phone completely off, hold vol-down and power. When the screen lights up, release power ONLY. Keep holding vol-down until some text shows up then release. Click vol-down to scroll through options until Recovery shows up. Click vol-up to select. Once recovery starts, navigate using vol-up/vol-down and power to select. /data will be wiped if you do a factory reset.
Hope this helps.
Hello,
I'm a little bit at a dead end after trying so much things.
My phone already was in repair for three times. The first time the replaced the mainboard because of a defective earspeaker. Before sending it in I was on the latest available Stock OTA update for my ROM (2.3.4, Retail DACH).
After I got it back after the first repair, I started to get trouble with GPS. Then also the touchscreen started to get a dead area and I send it in for repair the second time. I mentioned the GPS problems aswell, but they just changed the screen.
Then I send it in for the third time and now I have the third mainboard in my phone.
Unfortunately GPS still didn't work. Shows satelites, even sometimes gets a fix for some seconds, but the GPS Test App never reported a value for Accuracy.
Since I didn't want to send it in a again I started to search and found that this seems to be related to libnmea.so.
So I rooted the phone, exchanged the file, checked the permissions and tested it after reboot. Phone showed satelites, but the values for the satelites never went above 30 and it didn't get a GPS-fix within the 20 minutes I was testing it outside in the cold
So I followed another advice to flash a newer radio (N_01.77.36P) just to see if that helps. This required me to unlock the bootloader and install CWM Recovery, since this Radio I found was a fruit cake.
GPS isn't still much better now though... I drove a distance of 350 km (from work back to my home office) with always getting some satelites (approx. max. 7 at a time) displayed but only on the last 40 km I got my first fix, which then also displayed accuracy, so it might have helped a bit, I thought, but GPS fix only worked until I rebooted the phone the next time, since then it seems I didn't drive far enough to get a fix again...
Then I discovered the next problem...
Since unlocking killed my settings I had to make them again. My Exchange ActiveSync at work requires DeviceEncryption, and when the phone rebooted to enable encryption CWM Recovery came up with an error, that it doesn't recognize the parameter, and the phone didn't get encrypted and so I was without my contacts, calender and mails...
I couldn't find a way in the forums to restore the stock recovery, so I decided to reflash the stock-image with SBF.
Followed the guidance to delete cache, davlik cache and factory reset via cwm, and to erase different partitions using fastboot before using RSD Lite.
RSD Lite was 5.7 and the Motodrivers are 5.5.0, running on Win8 64bit.
RSD Lite flashed until 99% and then failed when trying to restart the phone in BP Bypass mode (0x70BE), and the phone was stuck with Error "Failed to boot 1".
I tried the ROM 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-rtdach.sbf
Then I found hints, that others were in the same boat and were able to recover from this error flashing this image
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf
But this didn't help me either, even after more retries. I also tried flashing on three computers and even tried to flash under linux using a Knoppix Live CD. Flash was always performed until the end, but after the last reboot I had the failed to boot 1 again.
Since I didn't find any more usefull guidance of things I could try, I thought "give it another try with the bootloader from the unlock (intl-fix-try1.sbf), can't get really worser now" and so did I and voila device is back and running.
Tried it again to flash a full sbf and came back to the same error, flashed the bootloader.sbf and it's working again...
After that I rooted it again and replaced the libnmea.so file again. But didn't have chance to test it yet, if this helped in any way...
I don't have much hope and think, that I 'll need to send it back to repair again, so again my question, is there any way, to get rid of the "Unlocked" of the bootscreen?
I can think of two possibilities, maybe there is a patched version of this intl-fix-try1.sbf available, that doesn't display this word or there is a way to really get back to the stock bootloader...
Best Regards
Mario
Exactly whats ur problem?????can u be more specific !!!
Sent from my MB860 using Tapatalk
Currently my problem is having the word "unlocked" during boot. Guess they'll refuse or charge for service, when they see it, when I send it in for repair once again...
GPS is still not working as it used to before the first repair. It sees some satelites (max. observed signal strength in GPS Test app yesterday was 23), but doesn't get a fix, even after 30 minutes.
Mario1976 said:
Currently my problem is having the word "unlocked" during boot. Guess they'll refuse or charge for service, when they see it, when I send it in for repair once again...
GPS is still not working as it used to before the first repair. It sees some satelites (max. observed signal strength in GPS Test app yesterday was 23), but doesn't get a fix, even after 30 minutes.
Click to expand...
Click to collapse
Mario1976,
I am encountering a similar problem with my AT&T Atrix 4G running Fruit Cake 4.5.141 with BL unlocked.
I cannot get the Data Encryption to work with CWM Recovery 5.8.1.8.
I'm beginning to think that I'll need to restore the stock Android Recovery to be able to get the Data Encrytion to work.
So far, my previous attempts at flashing the stock 4.5.141 SBF using RSDLite has met with the sec_exception: febe, 35, 35 error.
I also tried to use another set of instruction for restoring stock recovery onto another device on my Atrix but to no avail:adb push install-recovery.sh /data/local
adb shell
su
mount -o rw,remount /system
cat /data/local/install-recovery.sh > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1Konker
Update:
I finally figured out that the sec_exception: febe, 35, 35 error meant that the SBF was not intended for the device. That led me to suspect that the system board is not an original AT&T US board. I gave an Asian stock SBF a try & viola! The phone was successfully restored to factory stock ROM with stock bootloader & the Unlocked words removed from the boot screen. Device encryption is also working without any issues.