I am a new Android convert and purchased the Photon 4G last week. I successfully rooted, though I have not unlocked the bootloader. I flashed the Photon Laser 1.1 ROM, and then the Alien 1.1 Rom and theme. After noticing that I had no 3G/4G, I decided to revert to stock and avoid the Alien 1.1 for now. I went into Clockworkmod and wiped the dalvik cache, which I think was my major mistake, then in android recovery mode I wiped the cache 3 times, and did a factory restore. From this point forward I can not boot the phone successfully. Once it comes up to the tap the android to begin screen, I receive multiple error messages requesting the calander, phone, and other apps be force closed. I am unable to get into the phone at all. Additionally, if I tap the android icon, I can see the icon flex indicating my tap, but nothing happens. I've spent the last 6 hours attempting to use RSD Lite to reflash the stock image, but I receive an error each time stating "Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected." I need some direction from anyone that can help. Thank you in advance.
WEC2011 said:
I am a new Android convert and purchased the Photon 4G last week. I successfully rooted, though I have not unlocked the bootloader. I flashed the Photon Laser 1.1 ROM, and then the Alien 1.1 Rom and theme. After noticing that I had no 3G/4G, I decided to revert to stock and avoid the Alien 1.1 for now. I went into Clockworkmod and wiped the dalvik cache, which I think was my major mistake, then in android recovery mode I wiped the cache 3 times, and did a factory restore. From this point forward I can not boot the phone successfully. Once it comes up to the tap the android to begin screen, I receive multiple error messages requesting the calander, phone, and other apps be force closed. I am unable to get into the phone at all. Additionally, if I tap the android icon, I can see the icon flex indicating my tap, but nothing happens. I've spent the last 6 hours attempting to use RSD Lite to reflash the stock image, but I receive an error each time stating "Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected." I need some direction from anyone that can help. Thank you in advance.
Click to expand...
Click to collapse
Hey, I just wanted to confirm that you used RSDlite to flash the Final SBF release...45.2.5? And that didn't work? I've had issues with RSDlite attempting flash and then fail on me too. In that case, my phone would turn on into the Moto-boot logo, and then get stuck. I took the battery out and put it back in and it seemed to get me back into the phone after booting. Maybe you can try to reflash the final 45.2.5 update again?? Try using the cmd terminal to reboot or push files onto the phone? Sorry I don't know too much..I'm still really new to android.
I have followed the exact steps from this page: (http://forum.xda-developers.com/showthread.php?p=16328237), but every time RSD Lite fails with the error message I listed in the original post. I have pulled the battery several times, but am unable to get past the "tap the Android" screen. Tapping it leads to no change at all. I have no access to CWM anymore, and can only access recovery from Android recovery now, which I have used to reboot a few times at this point. When I reboot, I am greeted with errors that include "The process com.android.phone has stopped unexpectedly. Please try again." and "The application Suggestions Poll Scheduler Service (process com.motorola..suggestions.scheduler) has stopped unexpectedly. Please try again." and "The application Calander Storage (process com.android.calendar has stopped unexpectedly. Please try again."
WEC2011 said:
I have followed the exact steps from this page: (http://forum.xda-developers.com/showthread.php?p=16328237), but every time RSD Lite fails with the error message I listed in the original post. I have pulled the battery several times, but am unable to get past the "tap the Android" screen. Tapping it leads to no change at all. I have no access to CWM anymore, and can only access recovery from Android recovery now, which I have used to reboot a few times at this point. When I reboot, I am greeted with errors that include "The process com.android.phone has stopped unexpectedly. Please try again." and "The application Suggestions Poll Scheduler Service (process com.motorola..suggestions.scheduler) has stopped unexpectedly. Please try again." and "The application Calander Storage (process com.android.calendar has stopped unexpectedly. Please try again."
Click to expand...
Click to collapse
I know it's somewhere in this forum, but if you brick your phone and render it useless, you can try and reflash the original SBF...not the update. Give it a shot. Just let the force closes go, but see if you can connect to your computer. Best of luck!
Thanks, but I think that's what I was doing. Maybe it was the update. Can anyone point me to the original sbf? Thanks again for the replies.
http://www.multiupload.com/FNZKNV0T3G
thats the link, u need to unzip and then mount it on RSDlite
Thank you so much. I will download now and run it. Let you know if it finally works. Thank you for the link and help.
So nothing under the sun worked at all. I ended up having to take the phone back to the retailer and received a new one. I am happy now because after two days I have a functioning phone. I still believe that my error was clearing the dalvik cache before the factory reset, but I wouldn't have done that had the Alien ROM, which I mostly liked, hadn't killed my non-wifi data reception, as in I had none. Thank you the those of you who took time out to read and post a reply to help me. I am very grateful.
Help
Hey guys:
Yesterday I made mega mistake, I've flashed CM7 but... I didn't notice that I had to unlock the bootloader, obviously didn't work , but now, the phone is stuck on "unable to boot 2 entering RSD mode" with the Moto logo, so I tough, I will flash it again with the official Sprint update and fix the whole thing, but RSD gets to 100% restarts the phone and then phone shows just garbage! just like a blurry image, can't describe correctly but doesn't go any further. I've removed the battery start the phone again and then I get the same message "unable to boot 2 entering RSD mode". I'm on a loop right now, any advise will very appreciated, thanks'
Try flashing the 154_5 sbf...when in rsd mode...ive always had luck,with it as a starting point.
Sent from my MB855 using xda premium
KTT16 said:
Try flashing the 154_5 sbf...when in rsd mode...ive always had luck,with it as a starting point.
I will certainly give it a shot. I don't remember right now which file is the one that i got, I'm at work, but took me about 2 days in a row to download the file on my 128 kbps connection... third world connection.. I know.
Something that I would like to know is, when I turn the phone on takes directly to the error, if I press power + volume up then takes me to fast boot and stays there and if I do power + volume down gives a messages for about 1 second goes away and the phone goes like dead... I have to remove the battery to get it going again. Is there anything else that I need to know?.
thanks'
Click to expand...
Click to collapse
you need to get into rsd mode by powering up + volume up but use rsd verion 5.5 when connecting to the computer. Then after run the sbf and wait till it asks to manually power up the phone..pull battery and ur golden.
Make sure youre fully charged and have allege drivers installed properly.
Sent from my MB855 using xda premium
KTT16 said:
you need to get into rsd mode by powering up + volume up but use rsd verion 5.5 when connecting to the computer. Then after run the sbf and wait till it asks to manually power up the phone..pull battery and ur golden.
Make sure youre fully charged and have allege drivers installed properly.
You're the man!!!, I've dowloaded the file you told me and RSD 5.5 and I'm back in bussiness. I just unlocked the bootloader... ready to try CM7, yay!.
Thank you for your support, best regards.
Click to expand...
Click to collapse
Related
Just got my workphone, Droid 2 Global. No stranger to flashing droid phones (my personal phone is a Captivate) I just had to flash it. I mucked it up once or twice flashing Droid 2 Roms on it and needed to get it back to stock. I know a few people have asked about recovering the Droid 2 Global but I haven't seen any instructions to that effect, so here goes:
Droid 2 Global Return to Stock
1. Download RSD Lite 4.9 - http://www.mediafire.com/?ufxs9lft9q2xwnu
2. Download DROID2WE_X6_2.4.29_FULL SBF - http://www.megaupload.com/?d=MD5K1YY8
3. Download Motorla Drivers - http://www.motorola.com/staticfiles...al_Drivers/MotoHelper_2.0.40_Driver_4.9.0.exe
4. Install RSD Lite 4.9 and the Motorla Driver software. Unzip DROID2WE_X6_2.4.29_FULL to a convenient location, i.e. Desktop.
5. Shut off your Droid 2 Global, unhook it from USB or the AC adapter charger.
6. With the phone off, slide open the keyboard, hold the UP ARROW key on the keyboard and hold the power button. This puts the phone in Recovery mode. The screen will display white text and say something to this effect: "Bootloader D0.11, Battery OK, OK to Program, Connect USB Data Cable."
7. Start RSD Lite by clicking on the desktop icon, this brings up the GUI. Click the ellipse (...) next to the Filename dialogue box. If you put the DROID2WE_X6_2.4.29_FULL SBF file on the desktop, scroll down and select it and click Open. The File Properties box should populate with information about the SBF file.
8. Hook your USB cable to your phone, the text on the display will change. Click the Start button and have patience, this takes a while. RSD Lite will extract files to your desktop and begin flashing your phone. Do not interrupt the flash at any point or you will most likely have as nice paperweight.It takes roughly 5 minutes to flash the default rom and RSD Lite will reboot your phone.
9. If the Reboot fails and your phone loops through the starting animation. Pull the battery and put it back in.
10. Slide open the keyboard on the phone, hold down X on the keyboard and push the power button. This puts the phone in Recovery mode. You know you're in recovery mode when you see a triangle with a yellow exclamation and the green android logo.
11. Hit the Search magnifying glass key, this brings you in to the actual menu. You use the Volume Up and Down to navigate here and the Camera button for enter. Power button exits. Use Volume down until you get to the entry which reads Wipe Data/Factory Reset, push the Camera button. This will wipe your data and cache, I had to tap the OK button (The four little square button on the touchscreen) While it was running because the progress bar would stop. Your milage may vary. After it finishes, select the first menu option to reboot and push the Camera button.
That's it in a nutshell pretty much, let me know if I missed anything.
I've been trying to do this all day. My husband installed Liberty on my phone last night and forgot that it was a D2G, so of course it's all kinds of buggy. I'm trying to revert back to stock to try to properly install Liberty on the phone, but I can't get past the RSD Lite section. It keeps telling me "Failed Flashing Process 0x7100."
I've read a few forums about this issue and tried everything I could find. I'm running Windows 7, have run RSD lite as administrator, changed compatibility to Windows XP, moved the sbf file to every folder mentioned, moved RSD lite to the desktop, etc etc. I've also rebooted, uninstalled, reinstalled, in every fashion I could think of.
This is what I get when I check the error log:
17:01:30, May 03, 2011
Line: 868
ERROR: \\?\c:\users\user\downloads\droid2we_x6_2.4.29_full.sbfuèá contains an invalid path.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashFileIO.cpp
17:01:30, May 03, 2011
Line: 552
ERROR: The superfile specified does not exist
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse
I'm not sure what it means because most of the errors I've seen for RSD lite have been "was not found."
Any suggestions?
Also, I don't know if this is connected (I think it probably is), but for some reason when I plug in the phone it tells me MTP USB driver installation has failed. Each and every time.
Should I try to flash Fission over top of Liberty?
Thanks.
At first glance, i'd say to check the filename. There looks to be a space in what you copied from the errorlog, in the word full. Secondly, i'd redownload the SBF file, it's possible your download is corrupt. You can also try uninstalling and reinstalling the Moto software, it should install the drivers properly in recovery mode. I have windows 7 64bit and did not have to do anything other than what's in my directions.
Shorten the name of the SBF. Like - d2g.sbf for example. Put the SBF in c:\ and let RSDLite look for it there. It is known not handle well long paths or spaces in file name.
Is this supposed to put the phone back at original stock settings with no apps and everything? I can't find any videos of this, but the Droid X sbf guid it leads you back to the touch the android new out of the box screen. I followed this guide and when my phone rebooted, it had all my apps and widgets and stuff still, the only thing that was different was the firmware version had gone back down.
Nevermind, I somehow skipped the last few steps, I must be really out of it, ignore me.
i flashed it twice now and updated it. both times while flashing it told me to restart the device manually and when i did no change, so i closed the rsd and hit ok when it warns me of damaging my phone. phone was already on and running at the time.
Now i cant get my wifi to connect, it authenticates, then goes straight ot disconnected and then trys again.....any ideas of why this is happenning?
Did you follow steps 9-11?
What terrigan said. If you didn't do the last steps, then your phone will maintain all of its settings, but it will revert to the old firmware, 2.4.29 which is what I initially did. I believe that firmware has buggy wifi to say the least which might be the cause of your problem. You should do steps 9-11 and then after that go to settings, about phone, and system updates, and update to 2.4.330
Awesome!
Thank you for the post! You are awesome. Like a noob, I messed up my phone wile rooting/bootstrapping it and couldn't download from the marketplace, get updates installed etc. This fixed it all and I'm back up and running!
No prob, Wish there were more ROMs for the D2G though.
Worked like a champ, thanks!
Thanks muchly! Now that D2G Gingerbread is available, I'm reverting in the hopes to get the OTA update. Just waiting for the stock SBF to finish atm, will let you know how it goes..
Were not going to get the update until a couple more weeks...
Sent from my DROID2 GLOBAL using XDA App
Does anyone know if this works for the Droid 2 (NOT GLOBAL)...?
Chenoaem said:
Does anyone know if this works for the Droid 2 (NOT GLOBAL)...?
Click to expand...
Click to collapse
The steps and the RSDLite software will, you will need to find an SBF for your phone.
Droid 2 (Non Global) SBF: http://www.multiupload.com/R6VS5FFISB
I take no responsibility if this bricks your phone.
failed flashing process?
Hey, I was trying to revert my phone back, and while running RSD Lite, it got to 100% then it said that the flashing process failed?
the status came out as:
"Failed flashing process: Failed flashing process: Phone[0000]: Error switching phone to BP Pass through mode (0x70BE); phone disconnected"
help please?
Is there a reason why this would work on one phone but not another? I keep getting a failed on one phone with RSD lite I get code error FEBE 0047. I search and says not compatible software, doesn't make sense. Phone stays in boot loop.
thanks for any help.
Hey guys,
Here's my story:
Just bought a brand new D2G from a friend who likes to waste money...he tried to root it using a D2 rom, and gets the bootloader error. I bought it off of him for $50.
Flashed back to the SBF file in the first post, and then I got a message saying a new update was available. It downloaded on the phone, installs, the phone reboots and I saw the android green robot logo with a box, and a status bar. Once it hit 100%, the phone rebooted again, and to the bootload error said "code corrupt, insert data cable"
Tried holding X and power button to go into recovery mode like I did before, but it just boots to this screen....
Battery just died too, so I had to take it to a verizon store where they are awfully kind to recharge it for free.
Any help is appreciated, otherwise I'm just re flashing back to the rom in the first post again, and never updating the phone!
Jon
Find the .330 D2G SBF file and that should solve your problem I think....
Sounds like the update corrupted during install or download.. theres a .330 sbf try it like the above post stated make sure its fully charged low battery can cause major issues
i did the new gb update now i get a sorry the application contacts storage (process com.motorola.contacts) has stopped unexpectedly. please try again. it keeps coming up and i got to force close it comes back cant do anything on the phone. its stuck in airplane mode. cant get in to files to change anything? anyone able to help?
only 2 things to do:
if you're unlocked ur bootloader go to the developers forum and flash a stock rom using tenfars recovery.
else: http://forum.xda-developers.com/showthread.php?t=1181932
get the sbf and flash with RSDLite, YOU CANNOT GO BACK TO 1.83, IT WILL BRICK UR DEVICE.
grncivic2001 said:
i did the new gb update now i get a sorry the application contacts storage (process com.motorola.contacts) has stopped unexpectedly. please try again. it keeps coming up and i got to force close it comes back cant do anything on the phone. its stuck in airplane mode. cant get in to files to change anything? anyone able to help?
Click to expand...
Click to collapse
I had a similar issue yesterday after trying a mod. I pulled the battery, put it back in, and booted up. The error had stopped, (although the issue remained). I then put the original zip file on my phone, booted into CWM and flashed the original.
In essence, pulling the battery may allow you to do what p0xer said because you will be able to get any files you need onto your phone for flashing. (May actually fix the problem also).
If you can reboot to a useable state, maybe try clearing Dalvik, cache, and factory reset to get rid of the problem.
Hi,
On My atrix I download latest update sent by ATT for Gingerbread, Atrix was rebooted after that and Now I am stuck at error message "Failed To Boot 2" and "Startup RSD Mode". I cannot do anything at this screen. I took out the battery and phone was started but after starting up, immediately will show message "Power off, shutting down" and it will shut down and start in boot mode with the same error messaage "Failed to boot 2". Please help what should I do to come out.
I beleive I can use Motorola PC method to update my phone but since I cannot come out from boot mode, I am not able to even us PC mode.
I had GingerBlur installed, rooted phone before updating the latest ATT update.
I had the same problem. I used rsd to flash froyo with pudding and the problem was solved. I too had tried to unlock the bootloader while on gingerblur. Hope this helps.
Sent from my MB860 using XDA App
lordofthering said:
Hi,
On My atrix I download latest update sent by ATT for Gingerbread, Atrix was rebooted after that and Now I am stuck at error message "Failed To Boot 2" and "Startup RSD Mode". I cannot do anything at this screen. I took out the battery and phone was started but after starting up, immediately will show message "Power off, shutting down" and it will shut down and start in boot mode with the same error messaage "Failed to boot 2". Please help what should I do to come out.
I beleive I can use Motorola PC method to update my phone but since I cannot come out from boot mode, I am not able to even us PC mode.
I had GingerBlur installed, rooted phone before updating the latest ATT update.
Click to expand...
Click to collapse
I used RSD to load the factory SBF ("beta" 5.9.1") and it got me working again. I was running on a stock ROM, though, only rooted.
I have the same problem as the op but wanted to ask a real quick question in regards to this topic. How did you manage to flash back to the orginal sbf? When the phone is plugged in and powered up at this screen, RSD (5.3.1) is unable to detect the phone making it impossible to flash it.
I'm not trying to hijack this post but looking to shed a little insight in case the op is having the same issue.
Thanks!
mikedaman34 said:
I have the same problem as the op but wanted to ask a real quick question in regards to this topic. How did you manage to flash back to the orginal sbf? When the phone is plugged in and powered up at this screen, RSD (5.3.1) is unable to detect the phone making it impossible to flash it.
I'm not trying to hijack this post but looking to shed a little insight in case the op is having the same issue.
Thanks!
Click to expand...
Click to collapse
I thought it wasnt connected either when looking in the upper left pane of RDS. However, the status section under the 2 upper windows showed connected, so I went forward from that. Progress was indicated in the same lower section entry.
Sent from my android!
psyop1 said:
I thought it wasnt connected either when looking in the upper left pane of RDS. However, the status section under the 2 upper windows showed connected, so I went forward from that. Progress was indicated in the same lower section entry.
Sent from my android!
Click to expand...
Click to collapse
Thanks for the follow-up. I will give it a shot tonight and let you know how it goes. I think it was Rom Manager that screwed it up. When it forced the recovery software install, i'm pretty sure that is what caused it. I did have gingerblur installed so might not have been compatible. Just an FYI.
mikedaman34 said:
Thanks for the follow-up. I will give it a shot tonight and let you know how it goes. I think it was Rom Manager that screwed it up. When it forced the recovery software install, i'm pretty sure that is what caused it. I did have gingerblur installed so might not have been compatible. Just an FYI.
Click to expand...
Click to collapse
I had overwritten my stock recovery image as well, which is what caused me to do it this way. Should work for you.
Sent from my android!
psyop1 said:
I had overwritten my stock recovery image as well, which is what caused me to do it this way. Should work for you.
Sent from my android!
Click to expand...
Click to collapse
So I came home tonight and tried it once more on my PC and nothing showed connected. I figured I would give it one more try by installing a fresh copy of RSD Lite and the Moto drivers on my laptop. I plugged in the phone with the error on the screen and it did detect it!
It's currently installing the image (1.8.3 SBF) and at about 6% the error is now gone. Going to cross my fingers and hope for the best. Thanks for all the info and Ill make one final post with the results.
interesting im in the same boat lol
so how does one find a sbf file for the atrix i have the same issue
There are links in the forum to the "prerelease" version which turned out to be the same as the released version.
Sent from my Transformer TF101 using Tapatalk
I had the same problem using 01.97.00R SBF and installing the AT(HoneyComb)RIX with ClockWorkMod.
I solved with the file "ATT 2.3.4 pudding+root" and RSD 5.3.1, it installed Gingerbread plus 01.77.30P SBF
very good
FENZ-IT said:
I had the same problem using 01.97.00R SBF and installing the AT(HoneyComb)RIX with ClockWorkMod.
I solved with the file "ATT 2.3.4 pudding+root" and RSD 5.3.1, it installed Gingerbread plus 01.77.30P SBF
very good
Click to expand...
Click to collapse
Could you explain how to do that?
I run Install update and then it's show "Failed to boot 2.. " everytime
I'm Android newbie and have no experience to fix this.
nuboat said:
Could you explain how to do that?
I run Install update and then it's show "Failed to boot 2.. " everytime
I'm Android newbie and have no experience to fix this.
Click to expand...
Click to collapse
Is your phone unlocked?
Do you have a recovery (CWM) installed?
Edit: I see it has to be...Please give more information about what you´re doing.
If so, just download another rom and follow the flash-instructions using CWM.
As long as you can access the Recovery/Fastboot etc., you can fix things.
DO NOT BLINDLY USE RSDlite and SBF!!! It can turn your phone into a very expensive letter-weight.
I do not know what to do anymore ...
My phone is Hard Brick, AT & T, have no guarantee of any account, and live in the EU.
Jel is worth it in the United States sent in for repair and how much will we charge??
Atrix, or to throw against the wall and forget it ....
OK I know there are a ton of boot loop threads, but I can't find anything close to my problem after hours of searching, so here it goes:
My Atrix:
-2.3.6 Stock with 4.5.141
-Rooted
-(Side notes - because I'm not sure if they will be helpful:
--It had an unlocked bootloader before 2.3.6, but after the update it was locked again, I believe, as it doesn't say Unlocked in the top left corner when booting up. It's worked fine for months since the update.
--The internal SD was almost full - it only has about 30MB free, and it kept telling me it was pretty much full.)
A few days ago my Atrix just shut down while I was playing "Where's My Water?". Titanium Backup was updating itself automatically while I was playing, and when it finished was when the problem happened. A message popped up while I was playing that said "The process com.motorola.service.main has stopped unexpectedly. Please Try Again --> 'Force Close' or 'Cancel'". I pressed Force Close, and the phone shut down and started boot looping.
After searching I found that com.motorola.service.main may have something to do with e-mail, but I only use Gmail and I only have 1 account.
It won't boot into safe mode, and I don't have any recovery on it that I can remember, or it won't boot into that.
The thing is that I haven't done any modding in months - since rooting after the update, so it seems extremely random.
I don't care if I lose any data, as anything I need is backed up or useless.
I just want the thing working again or having NottachTrix on it. Really I just want it to work again.
If there is any more info I can provide, I will try my best to do so. Any help is greatly appreciated!
Same
I got the same problem. Please Help!
Eric162 said:
OK I know there are a ton of boot loop threads, but I can't find anything close to my problem after hours of searching, so here it goes:
My Atrix:
-2.3.6 Stock with 4.5.141
-Rooted
-(Side notes - because I'm not sure if they will be helpful:
--It had an unlocked bootloader before 2.3.6, but after the update it was locked again, I believe, as it doesn't say Unlocked in the top left corner when booting up. It's worked fine for months since the update.
--The internal SD was almost full - it only has about 30MB free, and it kept telling me it was pretty much full.)
A few days ago my Atrix just shut down while I was playing "Where's My Water?". Titanium Backup was updating itself automatically while I was playing, and when it finished was when the problem happened. A message popped up while I was playing that said "The process com.motorola.service.main has stopped unexpectedly. Please Try Again --> 'Force Close' or 'Cancel'". I pressed Force Close, and the phone shut down and started boot looping.
After searching I found that com.motorola.service.main may have something to do with e-mail, but I only use Gmail and I only have 1 account.
It won't boot into safe mode, and I don't have any recovery on it that I can remember, or it won't boot into that.
The thing is that I haven't done any modding in months - since rooting after the update, so it seems extremely random.
I don't care if I lose any data, as anything I need is backed up or useless.
I just want the thing working again or having NottachTrix on it. Really I just want it to work again.
If there is any more info I can provide, I will try my best to do so. Any help is greatly appreciated!
Click to expand...
Click to collapse
OK if you don't care about losing data, you can wipe the phone and factory reset it like this:
1.Turn off the phone and boot into recovery
2. If you didn't have a recovery or thought you didn't, like me, when you see the triangle, exclamation point, and android dude press (and possibly hold) both volume buttons at once. (I got this tip from a Motorola guy when I called thank goodness because I thought there was no recovery...)
3. Find the option for factory reset, and them it'll delete everything.
**Do this for me first though - when you get to recovery try wiping the cache and dalvik cache and see if that doesn't fix it. Otherwise do the full reset because that worked for me. Good luck and if you have any questions hopefully I can help!
And then I put a romracer's recovery and NottachTrix 4G on, and I love it!
Sent from my MB860 using XDA
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
deathbenotproud said:
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
Click to expand...
Click to collapse
Howdy, DBNP,
The Exhibit II is pretty much unbrickable...you won't need to resort to esoterica like jtag
The guide in the Exhibit II Wiki usually works out well. I'd try booting into stock recovery, doing a data wipe, then install stock with Odin. The Wiki has the links to the files you need. BTW, I didn't write the Odin portion @ the wiki; I just hosted required files when the links went stale.
Easy way to start recovery
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Once you're back up and running first thing you should do is install Clockworkmod. HTH, & good luck.
I cannot get my phone to get into recovery mode, though. if I press volume+up, the phone simply displays the firmware error message. thus, I cannot do a data wipe.
deathbenotproud said:
I cannot get my phone to get into recovery mode, though. if I press volume+up, the phone simply displays the firmware error message. thus, I cannot do a data wipe.
Click to expand...
Click to collapse
Sorry if this is redundant, but this was with:
Easy way to start recovery
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
This has never failed for me. IDK, Perhaps your earlier Odin try wiped the recover partition. Can you get into Download mode? (hold Power-on Vol-Down)
I can enter download mode, but I cannot enter recovery mode. volume down gets me into download, while up gets me the error message. I cannot get to that menu anymore.
deathbenotproud said:
I can enter download mode, but I cannot enter recovery mode. volume down gets me into download, while up gets me the error message. I cannot get to that menu anymore.
Click to expand...
Click to collapse
Are you saying that you get an error when you press Vol-Up at the initial "Warning!" "A custom OS can cause..." screen, the initial download mode screen?
when I press and hold the vol-up sequence, it takes me to the initial error of "firmware upgrade has encountered an issue..."
when I press and hold the vol-up sequence, it takes me to the menu where it says custom OS etc., press up to continue, down to cancel (restart phone).
deathbenotproud said:
when I press and hold the vol-up sequence, it takes me to the menu where it says custom OS etc., press up to continue, down to cancel (restart phone).
Click to expand...
Click to collapse
And when you press Vol-Up at this screen what happens?
it takes me to odin mode/download mode.
deathbenotproud said:
it takes me to odin mode/download mode.
Click to expand...
Click to collapse
OK, that's good. That tells us that your exhibit2's /dev/block/mmcblk0p5 partition is undamaged. AFAIK Odin when properly used, can flash a new rom to your phone. Please try again, following the instructions in the wiki, reading carefully, downloading any files that you need, if you don't have them. Please walk through the wiki procedure to reflash stock from Odin, this procedure has worked for many,many people. Keep careful notes, you may be an edge case for some reason.
I'm posting links to this thread in the discussion threads that we use, since we're not allowed a forum. These threads get the most attention.
Exhibit II 4g discussion HERE
Exhibit II 4g dev thread HERE
yeah, I have tried doing that myself, as well as my friend who is rather skilled with android devices. he tried that all himself today, as well as attempting add. nothing worked.
deathbenotproud said:
yeah, I have tried doing that myself, as well as my friend who is rather skilled with android devices. he tried that all himself today, as well as attempting add. nothing worked.
Click to expand...
Click to collapse
I think you and your friend did it wrong. You should try again, following the wiki carefully.
we re-did it this morning step-by-step with no new results. we tried three times.
odin does its thing successfully, then when it goes to reboot, instead of going into recovery mod, it just goes to the firmware upgrade issue message.
deathbenotproud said:
we re-did it this morning step-by-step with no new results. we tried three times.
odin does its thing successfully, then when it goes to reboot, instead of going into recovery mod, it just goes to the firmware upgrade issue message.
Click to expand...
Click to collapse
Sorry to hear it. If Odin won't fix your phone and you've only had it a few weeks, I'd return it. I've linked your thread to our discussion threads, perhaps someone else has an idea.
that's the issue. because I have tried to flash it via odin, they're saying they won't take it because of the firmware upgrade error that keeps coming up. :/
because they won't take it, and the normal flashing to stock method isn't working, what do you think I should do next?
deathbenotproud said:
because they won't take it, and the normal flashing to stock method isn't working, what do you think I should do next?
Click to expand...
Click to collapse
I don't know who "they" are, but the chances of anyone at a T-Mob store or a Walmart knowing you touched your phone with Odin or even what Odin is are practically nil. "It's three weeks old, I turned it on and it doesn't work. Gimmie my replacement."
Or seek out a repair service to reflash your phone.
all right, i'll take it back and get a different rep. thanks for your help, though
deathbenotproud said:
all right, i'll take it back and get a different rep. thanks for your help, though
Click to expand...
Click to collapse
I'm sorry we didn't resolve the problem. Better luck next time!
deathbenotproud said:
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
Click to expand...
Click to collapse
go into recovery and do a factory reset then reboot from recovery.