[GUIDE/FIX] {S4-MULTI} No Sound &/ WiFi &/ Bluetooth After Unbrick/Update? Read Me!
THIS GUIDE CAN APPLY TO ANY MODEL, PROVIDED YOU ENSURE TO GET THE PROPER FILES FOR YOUR VERSION!
I've had success myself flashing stock firmware from the M919V for Wind Mobile onto my I337M with no issue. This shouldn't be an issue. However, for the purpose of this guide, it is important that you get the firmware that was intended FOR YOUR DEVICE!
This was originally posted in the I337M forum as that's what I have, but here you go!
---
First head over here >> http://forum.xda-developers.com/showthread.php?t=2559693 >> and check out the original thread that helped me get to this resolution. Thank you to all the lovely people there!!
Before my softbrick occurred, I had flashed the NE1 modem through ODIN. I found that the same modem remained regarldess of the firmware I flashed. So I thought to match them up and give it another go. This worked great. This will work even if it was a regular S/W upgrade or install that caused the no sound and/or WiFi and/or Bluetooth issue.
Quick note before we begin: this guide assumes that you already went through a softbrick and have successfully come back from it, or went through a software update/firmware install which resulted in the same issue. Some of the steps in this guide may be able to be applied to some parts unbricking a phone, but this is NOT the intention. The intention is to help recover sound, WiFi and Bluetooth AFTER a successful unbrick or failed update/install otherwise.
DISCLAIMER: I am not responsible for your phone melting, imploding, turning into maple syrup or dying. Follow at your own will!
PRE-GAME CHECKLIST:
- Determine the ORIGINAL FIRMWARE that came on your device (this one was important for me, not sure how crucial it may be for others) - to be honest, I'm not 100% sure how to figure this out other than looking at the phone's box. It should notate which software version (SW-VER) it is. Before doing this, I was soft bricked, and had to use the very original 4.2.2 software for my carrier to recover from THAT. So maybe this part wasn't as important as I think, but I wanted to mention it anyway.
- The ORIGINAL USB cable for the phone - I suspect any high quality ones would work, but the one that came with the phone is a no-brainer
- ODIN 3.xx (I used 3.09)
- Samsung USB Drivers installed properly
- NO SD CARD (to be safe - this is optional as it should not be touched throughout the process)
- DO NOT, under any circumstance, use a USB hub for this procedure. Make sure it's direct into your computer with no extensions. I also recommend a cable that is 6ft or shorter if possible, but the quality of the cable is the most important
DO IT:
1) Download the ORIGINAL firmware that came with your phone (if you weren't able to determine this, I'd say the most recent one should be safe to flash, unless you softbricked while on 4.2.2 or 4.3 - in that case I would stick with the corresponding version, though I'm not sure how it would be affected since I didn't run into this)
2) Extract the file (I use 7Zip) and ensure there is one .tar.md5 file as a result - do not extract again
3) Boot up the phone into Download Mode (PWR off completely, then hold VOLDOWN + HOME + PWR together until the warning appears on the screen - click VOLUP to accept and proceed)
---PHONE WIPE---
This part is optional but I highly, highly recommend it.
4a) Flash Philz CWM (you can find the file and instructions on how to flash it through ODIN very easily)
4b) After flashing, it usually reboots into recovery. If it does not, do so manually: turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on.
4c) Make sure you close ODIN once confirmed the flash is done
4d) Tap factory reset and confirm it
4e) Once done, choose the clean ROM install option and confirm that as well
4f) Reboot the phone and continue on with the steps
NOTE: if there is anything to backup, now would be a good time to do this.
---
5) Open ODIN (IMPORTANT: In Windows, right-click and choose "Run as administrator" - this helped avoid an error for me)
6) Connect your phone directly to a USB on your PC and confirm that ODIN recognized it (it should highlight the first box and have "COM#" listed)
7) Click the second section (AP / PDA) and choose the .tar.md5 file you got in Step 1
***NOTE: ODIN may look like it's freezing or hanging here - IT IS NOT, BE PATIENT - it is a large file and it will take a bit of time to verify the MD5 for it
8) Click Start and sit back - it should take 8-10 mins or so (8:55 for me) with KitKat, and 5-7 mins or so with JB.
9) Your phone should have rebooted into a fresh Firmware. If you hear the Samsung boot sound, GREAT! You should be good (test WiFi and Bluetooth if possible) and you're done. Assuming that's not the case, which is why you're here, proceed to the next step
***If it's stuck in a bootloop, you need to force Recovery mode and do a factory reset. To do this, turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on. Use the VOL buttons to scroll to the factory reset option, and choose PWR to select. Then confirm on the next screen. Once that's done, wipe cache in the same way. Then, reboot, again in the same way. Now your phone should boot up
10) Go through setup and then go into Settings > More > About device. Observe the "Baseband version" section, and see if it matches the "Build number" section (starting from I337 and onwards). IF THEY MATCH, then repeat steps 5-10. IF THEY DO NOT MATCH, continue.
11) Download the matching modem file - ENSURE that the version of the modem you download MATCHES EXACTLY with the "Build number" in your phone's settings. Flash the file in ODIN in the AP / PDA section (if you need detailed instructions on this, it's a snap to find in XDA or Google)
12) Once done, reboot into the regular OS and verify that the "Baseband version" and "Build number" sections MATCH. If not, try to flash the modem again. After this has been verified, go ahead and follow steps 5-10 as many times as necessary until you hear that beautiful boot noise! It took me twice.
All the best and happy flashing guys! I'm not too much of an expert, just very good at explaining things, but I'll try to help as I can with any questions!
THANKS:
- All the great help thanks to input from around XDA in this thread (also listed in the beginning of this one): http://forum.xda-developers.com/showthread.php?t=2559693
- All the devs that work hard for us Canadian and AT&T guys over here
Related
Guide
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted. Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
Edit - pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
After that nothing is happening in odin and everything is grayed out. Error can be different (that was just my error), but the point is that phone is bricked (does not turn on). Causes can vary from you disconecting device during flash, computer crashing, ODIN crashing (my case), alien abductions and other very possible reasons =)
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon - screenshot, thanks to m3keni.
I looked at "Disable Driver Signature Enforcement" (thanks goes to blackerwater) advice and several recovery advices (up + menu + power; down + power; laptop does not recognize apd device).
Win 7 x64.
Solution
try odin on a different computer phone should be ok once you flash.. i flash multiple times on one then suddenly wouldnt flash anymore.. just hung.. re-did it on a laptop and it worked fine.
dupel said:
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted.
Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon.
I looked at "Disable Driver Signature Enforcement" advice and several recovery advices (up, menu, power; down, power; laptop does not recognize apd device), however, haven't found anything good. Including restarting (device, laptop), using different usb slots (eventually run out of), etc.
What are the other options for recovery? And any possible advice on such an error? Like how to do a complete wipe, hardreset, recovery, better flashing advice?
My first time bricking Android (god knows how much times I did it to my symbian )
Win 7 x64. Will add screenshots (if forums will allow me) tomorrow afternoon, now I need some sleep and have to wake up early.
Click to expand...
Click to collapse
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
m3keni said:
something like this???
Click to expand...
Click to collapse
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, do not turn off" step. Stuck there for some 5 min already.
dupel said:
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, not dot retn off" step. Stuck there for some 5 min already.
Click to expand...
Click to collapse
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
m3keni said:
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
Click to expand...
Click to collapse
Thats exactly what I have been doing (and tried flashing pit 513 + JG1, as it was my previous firmware), but once again am stuck at crashes in odin.
Will try, if everything fails today, to flash it from friends computer in the evening.
Have you tried downloading a fresh copy of odin? Odin should not need any compatibility modes so you should start looking for what you changed on your PC between the last working and the non-working flash. But rest (relatively) easy: The state your phone is in, is quite easily recovered (given you have a working PC)
Just reflashed my phone successfully. In case anyone has the same error in future what I did is:
1) Run ODIN with admin rights and in comparability mode.
2) Restart. I did about gazilion restarts, both windows and phone.
3) Every flash - restart of phone (remove battery), without SD card or SIM card, restart of Windows (7 x64) - during the boot process press F8 and Select "Disable Driver Signature Enforcement". (thanks to http://forum.xda-developers.com/showthread.php?t=723041 ).
Every restart - new USB port, not sure if it did affect anything.
4) While I have seen recommendations to close Kies and any other software that could use COM ports (I have OVI Suite and Nokia PC Suite installed for my old Nokia 5800) on last sucesful flash-reboot I left everything running.
5) Try re-downloading ODIN again, in case it is corrupted. Or re-downloading the firmware.
6) Very possible solution for my original problem (screenshots) - starting ODIN as soon as windows starts and to flash as soon as you can after windows start. Seems to fix my original issue.
7) Interesting solution by eizyark
The most sucessful combination proved to be:
a) Restart the PC using the Disable Driver Signature Enforcement.
b1) Optionally (if you already have bricked device) try leaving Kies on (tray icon).
b2) Run ODIN and select files you wish to flash (I used pit 512 and JG5 files - all 3, code-pda, modem-phone and csc).
b3) Usually it is recommended to select "Re-Partition" (in some cases might actually help you unbrick - experiment) - I did not.
c) Switch on the phone (insert the battery) and boot into download mode (Volume down + Menu + power)
d) Connect the cables (cable was disconnected from both the device and laptop). At this stage Odin should see your device, as described by flash tutorials (yellow + COM).
e) Flash.
Darkstriker said:
Have you tried downloading a fresh copy of odin?
Click to expand...
Click to collapse
Actually I did. Don't think it was actually a problem with ODIN as its just an executable file. Old-new file sizes were the same and it made no difference trying to flash.
All I can say - Im guite a geek, have been playing around with computers for more than decade and I still dont understand them. I really have no idea what was so different this time, but I actually did flash my phone again.
What is even funnier - just tried to flash the modified kernel for ext4 partition on sd card - same error (phone though reboots without any problems).
I think I found another way as well on how to save your phone. I had a similar problem. what I did was, when odin has detected the phone, press start without adding anything. after a few seconds the phone will boot up normally. well it worked for me, maybe this might help others as well.
Sent from my GT-I9000 using XDA App
Maybe we should pin this or any other topic for people to post if they have bricked their device?
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
m3keni said:
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
If you have this screen then just disconnect the USB lead, press and hold, power, vol. down and home until the 'Downloading' screen appears, start ODIN and then reconnect the USB and reflash.
Darkstriker said:
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
Click to expand...
Click to collapse
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
dupel said:
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
Click to expand...
Click to collapse
The problem is that (unlike your issue) 95% of those could be resolved simply by reading the FAQ properly.
ODIN
1st post
My phone was stuck in this infinite loop where try as I might I couldn't get it to re-flash I tried different computers and all and the only thing that worked was getting odin to flash without a rom.
it got my phone out of the loop
Helped heaps
m3keni said:
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
When I press the Volume Down + Home Key and then Power I get the Phone!PC screen instead of the download screen.
was bored at work and just kept pressing the Download mode combo over and over and it went to download mode from the dreaded cell!pc screen. got the stock rom to flash finally and all appears to be well.
Hi,
Sorry to interrupt but I've managed to brick mine completely...I was trying to update to Froyo without getting any far (not applied any firmware as yet) but I thought I could try the three button fix first so I downloaded the .zip file and stored in root directory of phone.
Before I could apply the fix...i was messing around and the three button worked without applying the fix. However, in recovery mode, first i deleted the data and did a factory reset followed by .zip update (three button fix file...what was i thinking!) which screwed up the phone useless.
It does not power up at all even after removing battery etc...the pc will not recognise it either!
Anything i can do without sending back to samsung/vodafone (the phone was rooted!)
Thanks in advance..ash
Trhow it in the water if you have insurance and hope they give you a new one
Sent from my GT-I9000 using XDA App
Hello!
I am hapy to share this link that I just found!!!
http://www.attdroids.com/forum/motorola-flipside-forum/3230-froyo-2-2-2-a.html
So, seems that the dream of having some custom rom could be more possible...
Personally I would like to thank the Moto people that take care to make approval for make this beta possible and for sure to the original poster in the ATTDroids forum, marvin and the others that are already testing it.
I will also copy a instructions resume of him (marvin) in order to get an idea of the process:
"For the best result from this upgrade I suggest:
Backup all your data from your various apps
use an app to backup your text messages if you want to restore them
make sure that you calendar and contacts are up to date on google so that they can be resynced
Make sure that you have all of your usernames/passwords handy
Factory reset your phone to clear everything out
install update
Do another factory reset (probably not needed, but it will not hurt)
set your phone up from scratch (setting up your WiFi connection first will speed up the initial setup)
Doing a reset first makes sure that you have enough space and that you don't run into issues with misbehaving apps after the upgrade. When the backflip was updated many users ended up doing a reset to clear various issues after they upgraded and you should at least be prepared with backups before you start the process.
The first thing that Moto support will advise you if you have issues after the upgrade is to do a reset.
Be prepared for some of your apps to not show up in the market after the upgrade. This is not just a Moto issue, but an issue for any phone that undergoes an upgrade because the market signature changes.
Waiting at least a week after the general release and reading the questions/problems that show up in the forums (especially the Moto support forum) is a good idea to prevent any gotchas.
MotoBlur will try to restore some of your settings when you enter your username/PW. If you want a true fresh start set up a new MotoBlur account."
I downloading by now and for sure will be try it asap. I use linux, so I will also check the SBFFLASH utility that I already used in my XT720 before and will test if would work fine in recognizes the FlipSide (I almost sure that it will do, but I will report if this may helps since I found more easy to use SBFFLASH since I didnt requires any installation of ABD or other stuff, only the litlle binary excutable and run also from a Live CD).
sbfflash download:
http://blog.opticaldelusion.org/2010/05/sbfflash.html
sbfflash instructions:
http://blog.opticaldelusion.org/2010/07/new-sbfflash-features.html
the main advantage of sbfflash is that it could be used with the original Moto Bootloader mode that loads sbf so it will help with flash with original Moto 2.1 ROM and then with flash of Froyo 2.2 ROM beta
Best regards!
Ok, some feedback...
Well did my test, and the phone works fine and found some quirks so I worte them at the en of this post.Also, I had to use the instructions at this link in order to get the update.zip menu option (because Moto page with instructions on update are down by now, so I may suspect that is something goes wrong with moto providing us with the final update at least we already have this beta working for possible future custom roms...), so I will try to post a collected list of steps for easy on another friends around...
Detailed Step list for update (copy and collected of other posts):
A) Backup Existing Data:
A-1) Backup all your data from your various apps
use an app to backup your text messages if you want to restore them
make sure that you calendar and contacts are up to date on google so that they can be resynced
A-2) Make sure that you have all of your usernames/passwords handy
A-3) Factory reset your phone to clear everything out
by using Menu->Settings->Privacy->Factory Data
A-4) Reboot, enter nomal and set the phone in USB debug mode.
by using Menu->Settings->Applications->Development
A-5) Turn Phone Off
A-6) B) Get Original 2.1 Eclair SBF file:
SAGE_U3_10.23.20_SIGNATT_USASAGE02B25ND0ATTNA02E.0 R_PDS001_SAGEATT_P033_HWp4_1FF.sbf
form this link:
http://www.mediafire.com/?l7i266ugb3pklxk
C) Install Original SBF file for get Full Stock Android 2.1 base
with Flipside Bootloader Mode - Restore with SBF File
C-1) Power Down Phone
C-2) Open the keyboard
C-3) Press and hold the up arrow key (to the left of the OK key)
C-4) Hold the power button down
and Release both buttons after about 4 seconds
You should see a display that says:
Bootloader
91.2B
Battery Ok
OK to Program
Connect to USB
Data Cable
This mode is for flashing an sbf file (ROM) to your phone using SBF_Flash in LINUX or RSDLite in window$.RSD Lite version 4.9 works with the Flipside
C-5) Let phone finish and reboot without disturb (flash process may take around 8-10min and reboot may take 4-5min first time)
C-6) Reboot, enter proper data keywords for gain acces to normal menu.
D) Get Froyo zip with name:Blur_Version.2.159.17.MB508.ATT.en.US.zip
D-1) Download from this link:
http://www.filesonic.com/file/1597204534/Blur_Version.2.159.17.MB508.ATT.en.US.zip
D-2) rename the zip file to update.zip and put in the sd card.
E) Install update.zip for Froyo 2.2.2
E-1) Power off your phone
E-2) Open the hardware keyboard
E-3) Hold the X key and then hold the power button
When you see the Moto symbol you can release the power key
Hold the X key until you see a triangle with an exclamation point
E-4) Press the key labeled Fn (lower left corner of the keyboard in landscape, upper left in portrait) and the T key at the same time
E-5) You will now see a menu on the screen
Use the hardware keyboard cursor keys (lower left in portrait mode) to move the blue highlight to the various selections. You want to highlight "wipe data/factory reset"
Press the return key (to the right of the OK key with the phone in portrait mode) on the hardware keyboard to select the option that is highlighted.
Use the cursor keys to highlight YES from the next menu.
Press the return key to complete the selection
The phone will begin to reset. WAIT until it says it is complete
E-6) Repeat previous steps for clean cache if You want (I did)
E-7) Repeat E-5 steps for option update.zip, and it will look for the file update.zip in the sd card and then start the upgrade. Let this to finish without disturb around 10-12min.
E-8) When it is complete you will see the the menu again, select "Reboot system now" with the cursor keys
Press the return key to reboot the phone, the phone will take around 12-15min first time after upgrade the update.zip
F-9) Reboot and start with registering process normal
DETAILS FOUND! PLEASE READ!
1) It could not by now to get access again to Fn+T recovery menu after update.zip install!!!!, please help if somebody could find if there another key combination after froyo update or if may be something else.
2) The update DETECTS Non-Original batteries!!! I have 2 batteries for my FlipSide and I just found that one of then that I bought by Ebay is NON-original and now the phone do not recognizes none charges it also (the battery was labled as original ,and in fcat WORKS AND LOADS FINE in 2.1 previously the update.zip).
Hope may helps, so please share your info & details about.
Best regards!
I found this info on Motorola sight for froyo recovery for flipside. Hope this helps.
Froyo
Power off your phone
Open the hardware keyboard
Hold the X key and then hold the power button
When you see the Moto symbol you can release the power key
Hold the X key until you see a triangle with an exclamation point
Press the Up and Down Volume keys at the same time
You will now see a menu on the screen
Use the hardware keyboard cursor keys (lower left in portrait mode) to move the blue highlight to the various selections. You want to highlight "wipe data/factory reset"
Press the return key (to the right of the OK key with the phone in portrait mode) on the hardware keyboard to select the option that is highlighted.
Use the cursor keys to highlight YES from the next menu.
Press the return key to complete the selection
The phone will begin to reset. WAIT until it says it is complete
When it is complete you will see the the menu again, select "Reboot system now" with the cursor keys
Press the return key to reboot the phone.
How does this open up the possibilities for custom roms? Does this unlock the kernel or something?
pre4speed said:
I found this info on Motorola sight for froyo recovery for flipside. Hope this helps.
Froyo
Power off your phone
Open the hardware keyboard
Hold the X key and then hold the power button
When you see the Moto symbol you can release the power key
Hold the X key until you see a triangle with an exclamation point
Press the Up and Down Volume keys at the same time
You will now see a menu on the screen
Use the hardware keyboard cursor keys (lower left in portrait mode) to move the blue highlight to the various selections. You want to highlight "wipe data/factory reset"
Press the return key (to the right of the OK key with the phone in portrait mode) on the hardware keyboard to select the option that is highlighted.
Use the cursor keys to highlight YES from the next menu.
Press the return key to complete the selection
The phone will begin to reset. WAIT until it says it is complete
When it is complete you will see the the menu again, select "Reboot system now" with the cursor keys
Press the return key to reboot the phone.
Click to expand...
Click to collapse
Hi!
Thanks for the info, tested and IT WORKS so, return back to 2.1 SBF is possible in case (I found previously the info about Fn+T keys combination and it works on 2.1 but no in 2.2, so glad that this VolumeUP+VolumeDOWN keys is working)
About custom roms from this, I previously was using an XT720 (but really need the hardware Keyboard and 850Mhz 3g Band in my country) so I goot my FlipSide for a solution, but, as far I remenber, one of the big troubles previously to tht XT720 got 2.2 was the fact that were no release, so the process that the Dexter dev had to use was a long Hack&Test Roms and codes from other model until got one working.
IMHO the fact of have a beta ROM that have tthe native harware support for the FlipSide may could make more easy to get a custom or at least "Enhanced" ROM (aka... crapware free, and with some useful touches like removing crapware & locking things as battery detection, overcloking, swap, more memory swap utils compatibilty, EXT filesystem supports, etc), but I am not a dev, so this is IMHO. And also I am happy that this beat at least reach the comunity, since is suspecting for me why Moto shut down the page about offcial FlipSide update and no more annoucements...
Thanks to all and best regards!
I have received info from a reliable source that downgrading the Flipside from the not-yet-released (or after it's release) Froyo upgrade using the available SBF files will brick your AT&T phone.
I do not have personal knowledge of this, but I trust my source.
Here is part of the communication I received:
Just so you know AT&T devices cannot be flashed back(downgraded). It will likely brick them. I would urge strong caution when flashing SBF files
Click to expand...
Click to collapse
marvin02 said:
I have received info from a reliable source that downgrading the Flipside from the not-yet-released (or after it's release) Froyo upgrade using the available SBF files will brick your AT&T phone.
I do not have personal knowledge of this, but I trust my source.
Here is part of the communication I received:
Click to expand...
Click to collapse
If your talking about essentially following this guide twice, it will not brick your phone. I followed this guide, flashing to fresh 2.1 then upgrading to 2.2. Then did my cousins phone for him. Without thinking it would cause problems I used my motoblur login on his phone on the 2.1 step to make things faster (not having to ask his info) and afterwards my phone as flagged unassociated with motoblur that i needed to contact tech help. To save myself the time on the phone I simply followed this guide again... flashing 2.1 on top of my 2.2, then upgrading to 2.2 again. All works fine. That was 2 or 3 days ago.
boazjuggalo said:
If your talking about essentially following this guide twice, it will not brick your phone. I followed this guide, flashing to fresh 2.1 then upgrading to 2.2. Then did my cousins phone for him. Without thinking it would cause problems I used my motoblur login on his phone on the 2.1 step to make things faster (not having to ask his info) and afterwards my phone as flagged unassociated with motoblur that i needed to contact tech help. To save myself the time on the phone I simply followed this guide again... flashing 2.1 on top of my 2.2, then upgrading to 2.2 again. All works fine. That was 2 or 3 days ago.
Click to expand...
Click to collapse
Ok, so I just tried the official upgrade to the full (nonbeta) 2.2 on moto site.
Running the beta it shows that I did not have an available upgrade. So I went to flash back to 2.1 using the RSD method. I think my phone is bricked... RSD finishes like it normally does with no errors, but when it finishes and reboots the phone, instead of opening into the android OS it opens into a black screen that says
Bootloader
91.7B
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
As I said before, I did successfully do this one time, so it is possible but for me it was a 50/50 chance. Good luck and wish me luck finding a way to unbrick it.
boazjuggalo said:
Ok, so I just tried the official upgrade to the full (nonbeta) 2.2 on moto site.
Running the beta it shows that I did not have an available upgrade. So I went to flash back to 2.1 using the RSD method. I think my phone is bricked... RSD finishes like it normally does with no errors, but when it finishes and reboots the phone, instead of opening into the android OS it opens into a black screen that says
Bootloader
91.7B
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
As I said before, I did successfully do this one time, so it is possible but for me it was a 50/50 chance. Good luck and wish me luck finding a way to unbrick it.
Click to expand...
Click to collapse
Yea I just did this and now my phone is doing the same thing...we are indeed BRICKED!! I'm working to try to solve this problem too. Let me know if you find anything as I can't figure it out! I really want this unbricked...I can't do ANYTHING!!
Well, finally I was able to return here after several very busy and hurry days.... too bad the issue of the bricked phones... really bad also that the info about the bricking risk was leaked several days after the beta sbf was leaked and that some of us use it on our phones.
However, I wonder about, if somebody may knows what could be the instructions of Moto Devs to the official beta Testers, that were on the beta testing process, for update their beta phones to the official Froyo after Moto ends their beta testing process... I suppose that tehir could be the official instructions to this beta testers so make their phones to normal froyos.
Anyway, I will ask the moderator of this forum to please change add the word OBSOLETE to the title of this thread in order to avoid more bricking issues, since is all that I could do by know since I am not a programmer that could help more about how to revert bricked phone.
Good Luck and best regards!
boazjuggalo said:
Ok, so I just tried the official upgrade to the full (nonbeta) 2.2 on moto site.
Running the beta it shows that I did not have an available upgrade. So I went to flash back to 2.1 using the RSD method. I think my phone is bricked... RSD finishes like it normally does with no errors, but when it finishes and reboots the phone, instead of opening into the android OS it opens into a black screen that says
Bootloader
91.7B
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
As I said before, I did successfully do this one time, so it is possible but for me it was a 50/50 chance. Good luck and wish me luck finding a way to unbrick it.
Click to expand...
Click to collapse
Ok Bud just discovered someone got the bootloader and sbf for us to unbrick! Here you go!
Froyo SBF and Bootloader for Flipside MB508 AT&T USA
Bootloader: BL_917B_4G_sageemu_Consumer_replacer.zip
Download BL_917B_4G_sageemu_Consumer_replacer.zip for free on Filesonic.com
SBF Flash :
Android 2.2.2 ------ Blur_Version.2.159.17.MB508.ATT.en.US
SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz
Download SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz for free on Filesonic.com
WARNING: ONCE YOU FLASH THE FROYO SBF ANY ATTEMPT TO DOWNGRADE TO ECLAIR MIGHT RESULT IN A HARD BRICK !!!!!
These files are made available as a general courtesy and I assume no responsibilty for your own actions.
Thanks for share, very usefull, and in fact, I could use it with success. Best regards
I've tried going through all the steps to encrypt my phone, however, it seems I get stuck on the black screen with green "lock" android / robot. It never goes any further than that screen (it never reboots as the directions state it would).
I've tried a couple different roms (Frosty JB, Wicked, Synergy) and none seem to let me complete the encryption process. I haven't tried going back to stock yet, since someone with an i9300 (international SG3) posted they had the same issue even when they went back to stock.
Has anyone had this issue? If so, how did you fix it? I've been looking all over the place for days and haven't found anything.
EDIT/ANSWER:
After doing a bit more digging, evidently, there's something called a PIT file that has to do with partitioning in our phones. You need to use Odin to install it. These are the directions I followed:
Pull out the battery and reinsert.
Press and Hold Volume Down + Home + Power Button until you see a warning!!
Press Volume Up button.
Your device will now enter the download mode.
Connect your phone to the PC.
Let it install some drivers.
Open Odin and click on PIT
Select that .PIT file you downloaded.
Check the box – Re-partition and Click Start.
After the successful attempt to re-partition the device, Flash with new firmware(which you downloaded from SamMobile)
Browse the downloaded firmware to the PDA section in Odin.
Don’t check the re-partition box this time.
Click Start and wait.
As soon as the process completes, your phone will boot. and it won’t stuck at welcome screen.
PIT files for US ONLY phones can be found here:
http://forum.xda-developers.com/showthread.php?t=1848267 - SEE THE FIRST POST
This finally worked for me, but use at your own risk.
I am writing this because I couldn't seem to find a guide to solve my issue of my Galaxy Nexus being completely bricked. It was literally dead, or so I thought. The first part of this guide will tell you how to recover from the following situation:
Before we begin, here are the names of the programs and files used:
Odin3
Android ADK
CF-Root-GGN_YAKJU_ICL53F-v5.1
Stock Galaxy Nexus ROM
OMAP
Situation 1:
The first situation is where your screen has gone completely black. You can't boot into anything and nothing is displayed on the screen. Your computer no longer recognises the device. It is literally a brick. If you are in this situation, please follow the solution 1 and 2 else skip to situation 2.
Solution to situation 1:
I was googling everywhere for a solution to this and it appeared that it was not a common problem and those who did face the problem simply returned their phone on warranty. It is now an old phone but I still like it (will be upgrading to nexus 5 in the next few weeks). I didn't want to waste such a good phone and just have it sit there so I researched.
My solution to this problem is omap. I would post a link but unfortunately I do not have the permissions (for the download link I will be uploading later).
Please note that I do not take any credit for any program used in this guide and I am simply putting together several other guides so that future users who have this problem can access them all in one place.
Here is the step by step guide:
1) Open OMAPFlash. Navigate to usb_drv_windows. *Right click on omap_winusb.inf and click install*.
2) Navigate to usb_drv_android. *Right click on android_winusb.inf and click install*.
*Note: On Windows 8 (8.1), you will have to allow all certificates to be installed.
3) Double click on the omap4460_tuna_hs_pro.bat and run it accordingly. You will have to disconnect the device and remove battery. Connect the device and then count to 5. Re-insert the battery.
4)Omap will now start doing its thing and you will be given situation 2.
Situation 2:
This situation is where you have a phone connected to a yellow exclamation mark which is connected to a computer. Mind my ASCII Art, but here is what it looks like: [] - - /_\ - - [ ]. You can't do anything with this either but ODIN (google it) will pick it up. This is a good thing. You won't be able to boot into recovery mode or download mode which makes it hard to flash a ROM to it or fastboot it. You will need CF-Root-GGN_YAKJU_ICL53F-v5.1 (Google it). Here is the step by step guide:
Solution To Situation 2
1) Open ODIN3. Select the CF-Root-GGN_YAKJU_ICL53F-v5.1 as the PDA file. If your phone is not being recognised (should say added! in the log), simply disconnect device, remove battery, reconnect device and then place battery back in and hold down the power + vol up + vol down buttons.
2) Press start. The log will start filling up and it should say DONE! You now have bootloader.
3) Now you will need to find the stock ROM for the galaxy nexus (google it). Now you will need to extract that the contents into your adb file (from the android sdk installation which hopefully you have,
4) Put your device into bootloader mode. Run the fastboot flash-all batch file that should be included with the custom ROM.
5) Your phone will now start doing stuff and constantly rebooting in and out of bootloader mode.
6) You should now have the stock ROM installed.
Again, I am sorry that I cannot post links but I do not have permissions due to lack of posts. I know this is an old phone but this guide may still be useful to someone. Also, feel free to ask any questions or point out any mistakes I have made.
no need that android adk. setup correctly adb & fastboot just enough. i think this type of threads already here..
* yeah.. but no sticky guide. maybe good to go. better make ' how to prevent gnex from bricks'
omap flash.exe ~
http://forum.xda-developers.com/galaxy-nexus/general/bricked-gnex-brought-to-life-t1760787
odin ~
http://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
I probably already know the answer to this but I want to make sure: can this procedure be applied to the Verizon Toro?
Update: Phone isn't responding to this fix... It was a long shot maybe in a week or two it'll turn on...
I'll write up a tutorial for us Toro kids... Thank you guys!
Sent from my VS980 4G using Tapatalk
First, I would like to thank @toastido for sharing the stock firmware, information and all his own
time he used to put all this together, He deserves all thanks.
My problem was really low signal and GPS not locking, sometimes it used to take at least 10 min. to
lock and constantly this message: SIGNAL LOST (using google maps).
I solved my problem, and here it is, step by step:
!!!!!VERY IMPORTANT- BY DOING THIS PROCESS, YOU ARE GOING TO TRIP "KNOX"!!!!!!
1. Go here: http://forum.xda-developers.com/note-3-tmobile/general/5-0-n900tuvufob6-extracted-stock-t3047672
2. Download: Full Stock Image N900TUVUFOB6: http://www.mediafire.com/download/cuoz62g1ca6id9t
3. Download: Modem + NON-HLOS (Combined): http://www.mediafire.com/download/yfxoxii8xxmzmtr
4. Download: Odin 3.07 (this is the version I used)
Once everything is downloaded You are ready to start.
A) Open odin(make sure auto reboot and F. Reset Time are checked) and load Full Stock Image N900TUVUFOB6
under PDA (and make sure PDA is ckecked as well).
B) Put Your T-Mobile Note 3 in DOWNLOAD MODE.
C) Connect your phone to your pc or laptop (Odin should reconize your phone)
D) Press Start (to start the flashing process) It should take aproximatly 15 Min., let the phone
reboot by itself and CLOSE ODIN.
E) Go through the phone set up (wifi,accounts, etc.)
F) Put Your T-Mobile Note 3 in DOWNLOAD MODE again.
G) Open odin(make sure auto reboot and F. Reset Time are checked) and load Modem + NON-HLOS (Combined).
under PHONE (and make sure PHONE is ckecked as well)
H) Connect your phone to your pc or laptop (Odin should reconize your phone)
I) Press Start (to start the flashing process). This process should take a couple of min. Let the phone
reboot by itself and CLOSE ODIN.
J) DONE, Your signal might be better and specially your GPS will lock within a minute.
"""""""ALL CREDITS GO TO @toastido""""""
"NOW YOU ARE READY TO ROOT YOUR PHONE"