Develop Bugs

So I bricked my GNEX...Then brought it back to life!

So, this morning at 5am (yes, stupid time to be playing) I flashed a zip. I have stored on my phone zips for both this and my tablet, and guess what genius did? flashed the wrong friggin one! Very surprised it went through without fault, but hey, **** happens.
So, basically what happened, is my phone became a brick. Black screen, could not boot it up, couldn't et to bootloader or download mode or recovery, tried several things like pulling battery for 30 secs then putting back in, plugging into PC without battery and putting battery in, leaving without battery or SIM for 30 minutes and putting back in, NA friggin DA. Still a brick. Not even the vibration when it first kicks in. Nothing
Starting to think time to call tech support, but as I was trying to plug into PC, I noticed something trying to install, then disappearing real fast. That was my first clue. I opened device manager, plugged phone in, and watched what was happening. A device called OMAP4460 was trying to install for half a second before disappearing, failing, but still, it was something. Even though screen was still blank, and not even bootloader would come up, this was happening. So I googled.
I found this site/thread: http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/. Legija, is a friggin genius Downloaded and unzipped the package, ran the bat, and plugged in the phone. But alas, still no joy
Reread his post - install drivers first...So, putting on my tech hat, how to install drivers if device is not listed, I went into the Actions menu in Task Manager (Win 7), and selected to add legacy hardware. I then chose to install manually, then selected have disk, and browsed to the drivers in the zip package from Legija (all this without device plugged in BTW). I installed the OMAP flash driver successfully, and now showing in task manager with the nice yellow triangle/exclamation mark.
Ran the bat file again, plugged phone in **WITHOUT** battery in phone, and off it went scrolling through it's processes, ninja'n away my f'up. When it completed, put battery back in, held down power, and up she came! Woot! Got back into OS no issues, and I'm one very happy camper.
So I thought i'd share, not thinking anyone else may do the same bloody stupid thing, but maybe a variance, or just have the same symptom (black screen, attempt to install OMAP when plugged into USB), this may just help you! AS for me...deleted all files not for GNEX, i'll continue to stuff around before work, so this is safe
EDIT:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process. Once you see "Press any key to continue..." close the CMD window and proceed to step 9
9. Unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)

Thanks for sharing this find, I'm sure others will find this to be useful

No problem, true believer in sharing my stupid mistakes so other may not follow, or if they do, know how to fix
Oh, in my write up - one change now edited - run the bat with the phone connected to USB **WITHOUT** battery in, once it's finished insert and boot up

Next time I'll be more safe while flashing roms to my phone.
Great find.

wow, this is possible? i thought cwm will prevent you from flashing wrong zips and even if not, why would it kill the bootloader? i was under the impression gnex is close to unbrickable but this topic you linked opened a whole can of worms for me, whats with all these hundreds of people who hard(!)bricked their nexus ... did i miss something?

This was a custom zip I had created myself to do some things on my tab, it ran from install script an install.sh that then went and installed a recovery img. Pretty sure i've never seen this before from any install zip, it was the behaviour I put in mine that allowed it to go through, and I hadn't put into the script to stop if not correct device - lesson learned
BUT - that said, you can do things like this to your phone running scripts, very easy to actually if it's running from su... So never run scripts unless you trust he person whose created it (or have written it yourself and certain of it), know it's definitely for your device, and, most importantly - never miss this step - have had 3 cups of coffee first :good:

Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^

Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:

rekrapg said:
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:
Click to expand...
Click to collapse
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
If it's not permanent, it's not, and never was, a brick.
Click to expand...
Click to collapse
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed

Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
Well it happens my dude.....at least he took the time out to give a guide and explained how he fixed it just in case someone else does something similar
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
efrant said:
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
True....but most people would not know what to do in this situation and call it a day....at least he searched Google and fixed his problem. Wish more people were like him ya know
---------- Post added at 09:00 AM ---------- Previous post was at 08:56 AM ----------
rekrapg said:
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed
Click to expand...
Click to collapse
Exactly I said most people would have called it a day.....ZOMGZ MA FONEZ NO LITE UPZ IT HARDSOFT BRICKED!! .....lol all joking aside man your like me I wouldn't have stopped until I was absolutely sure I needed them JTAG boys
Persistence pays off...remember that

Yup. In most cases, there's a way around a problem, you just have to dig until you find it

Congratulations
Saludos desde Ecuador

Though I don't want to have chance to perform your provided method, it's really good to know, in case....
Congratulation and thanks!

rekrapg said:
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?

Chad_Petree said:
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?
Click to expand...
Click to collapse
Choose the one closest to what displays on the device manager. I started with the OMAP Flash Drive one and it worked for me, but you can always choose the 'update driver' option and install another if required. Turn off User Account Control in Control Panel/Users and make sure you're on an admin account, as it may by default block the ability to install unsigned drivers, to be honest not sure on that one as it's always been first port of call for me on Win 7 (and Vista).
I also found this that might help: http://www.techspot.com/community/t...signed-drivers-in-windows-vista-7-x64.127187/

Wish I would have found this a week ago! The exact same thing happened to me, except I had been running a working JB ROM for a day or so.
Went jogging, was listening to music, came home, music stopped, screen wouldn't turn on with power button or USB cable with a charger or a computer, but there was a notification LED flashing. No amount of pressing and holding the power button would bring it back to life, so I pulled the battery. After that it was in the exact state your GNEX was in. Not even the vibrate when trying to power it up. After a few hours of charging and trying all sorts of things to breathe life into it (including a battery swap) I ended up returning it to the brick and mortar VZW store and they replaced it because I was under 2 weeks with the phone.
Thanks for posting!

I ran the OMAPFLASH_tuna on my GNex and now, I seem to be stuck at "Sending Data"(SEE last line in the image attached)
The values of 131072 has been like that for over 20 minutes and have not changed. What data is it sending and to who or where?
to those who've used this too, What should happen after this?
thanks...
{
"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"
}

I would be lying if I said I knew exactly what this wonderful tool is doing mate With mine, it ran through in like 30 seconds to completion. I ran it 3 times to be sure! I have 2 suggestions,
1. Sign up to those forums and ask the expert
2. If your device is already 'bricked', it may be worth just disconnecting, closing the CMD window, reconnect and re-run it.
I'm no expert on this application though, I simply found it, it worked for me, so I shared. So option 1 may be your best shot. It's quite likely the bloke who created the tool will be able to let you know the proper path to go down.
EDIT: I am at work atm, so I can't 're-run' it on my device to show you the screen - but I recall it comes up with a 'press any key to continue' prompt after completion (pressing any key just re-runs it).

Funny because another person on GSMHosting is experiencing the same problem and says that his just stops downloading... Just like mines and at the same stop too... hummm...

Can't Encrypt - Tmo Galaxy S3

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.

[Q] Tab 3 10.1 GT-5210 stuck in Odin

This morning, before even started with rooting, my brand new Galaxy Tab 3 10.1 (GT-P5210) went into the Odin Download modus without any problem.
But, the Odin software isn't able to even see the Tab 3 itself. Just the Odin screen and nothing else.
I have tried to reset or power down the device, with all possible keys and key combinations. But no luck so far.
Does anyone else have a suggestion ?

is128ae said:
This morning, before even started with rooting, my brand new Galaxy Tab 3 10.1 (GT-P5210) went into the Odin Download modus without any problem.
But, the Odin software isn't able to even see the Tab 3 itself. Just the Odin screen and nothing else.
I have tried to reset or power down the device, with all possible keys and key combinations. But no luck so far.
Does anyone else have a suggestion ?
Click to expand...
Click to collapse
To manually exit Download mode, you have to hold the Power button for at least 10 seconds (or more). It should then reboot normally if you haven't changed anything.
To get your PC to recognize your Tab, you need to download and install the Samsung USB drivers (or just install KIES). Also go ahead and make sure USB debugging is turned on in Developer settings (to make troubleshooting easier in the future if necessary).

gr8nole said:
To manually exit Download mode, you have to hold the Power button for at least 10 seconds (or more). It should then reboot normally if you haven't changed anything.
To get your PC to recognize your Tab, you need to download and install the Samsung USB drivers (or just install KIES). Also go ahead and make sure USB debugging is turned on in Developer settings (to make troubleshooting easier in the future if necessary).
Click to expand...
Click to collapse
Thanks for your relply. Problem is, I can hold down the power button until my hand falls off.
It won't power down

..... After 8 hours the tablet went down, because of an empty battery.....
Now waiting for it to have power enough stored to boot again....

HELP! i have same problem.
is128ae said:
..... After 8 hours the tablet went down, because of an empty battery.....
Now waiting for it to have power enough stored to boot again....
Click to expand...
Click to collapse
Did it boot up again normally after you recharged? Is it all normal now? Im really worried please reply.
:crying:

FSN8iN said:
Did it boot up again normally after you recharged? Is it all normal now? Im really worried please reply.
:crying:
Click to expand...
Click to collapse
Yes it booted up without a problem.
It only took a time (long! > 8hrs !) for the battery to be fully charged.

I have the same issue, TAB3 10-1.
I entered Odin Download Mode and the device wont switch down when power button pressed. I disconnected the cable and the screen still remains.
So I have to wait hours and hours till the tablet will discharge.
By the way that file pre-rooted md5 did not download at all and I have to download manually - 30kbit/sec is hell of a speed = aprox 16 hours and errors during download are very likely, phew.
PS - jailbreaking iPhone is far more easy

Yep, the tab 3 GT-5210 with x86 processor wont reboot from odin mode. Ive tried the suggestions here and elsewhere and agree with the others in this thread. Ive held down the power button for minutes by hand, and now it has been about 20 mins and counting with tape holding it down. Odin 3.09 can see the device and talk to it, but it wont reboot it without a flash. Ive seen suggestions elsewhere that flashing a blank file will work around the issue and cause the auto reboot to happen, but it does not. Odin fails to load the file, then does nothing and does not auto reboot. When I disconnected the tab from the pc after playing with odin, the battery part of the tab was warm so it had been charging off the pc Ive been searching quite a while, it seems the only way to get out of odin mode is to wait for it to go flat as discussed here.
---------- Post added at 10:54 AM ---------- Previous post was at 10:29 AM ----------
Ok, I created a way to do this.
Firstly you need odin 3.09. My version contains "Odin3 v3.09.exe" which is 2290688 bytes with an MD5 sum of 46947de16219dcbec41c8290353ad50c
Open the exe in your favorite hex editor and at offset 712A change 75 to EB. This disables the "no bin file is selected" error message, so you can do nothing and cause the reboot.
This screen shot was taken after the reboot. Configure the app like this and click start. It'll do nothing, reboot, and say PASS! :good:
due to being < 10 posts I cant post this link. But you can resassemble it. Mods, if you want to verify this link and fix my post, go ahead.
http: // i.imgur.com / X41Cq3s.png
If your not confident with odin and dont want to risk your tablet, your better of waiting for the battery to go flat. But if you understand the risks and what ive done here, maybe it'll save you the wait.

And when you did this were you able to install a new recovery w/o the old one being reinstalled?

Sorry, wrong message

antus said:
Yep, the tab 3 GT-5210 with x86 processor wont reboot from odin mode. Ive tried the suggestions here and elsewhere and agree with the others in this thread. Ive held down the power button for minutes by hand, and now it has been about 20 mins and counting with tape holding it down. Odin 3.09 can see the device and talk to it, but it wont reboot it without a flash. Ive seen suggestions elsewhere that flashing a blank file will work around the issue and cause the auto reboot to happen, but it does not. Odin fails to load the file, then does nothing and does not auto reboot. When I disconnected the tab from the pc after playing with odin, the battery part of the tab was warm so it had been charging off the pc Ive been searching quite a while, it seems the only way to get out of odin mode is to wait for it to go flat as discussed here.
---------- Post added at 10:54 AM ---------- Previous post was at 10:29 AM ----------
Ok, I created a way to do this.
Firstly you need odin 3.09. My version contains "Odin3 v3.09.exe" which is 2290688 bytes with an MD5 sum of 46947de16219dcbec41c8290353ad50c
Open the exe in your favorite hex editor and at offset 712A change 75 to EB. This disables the "no bin file is selected" error message, so you can do nothing and cause the reboot.
This screen shot was taken after the reboot. Configure the app like this and click start. It'll do nothing, reboot, and say PASS! :good:
due to being < 10 posts I cant post this link. But you can resassemble it. Mods, if you want to verify this link and fix my post, go ahead.
http: // i.imgur.com / X41Cq3s.png
If your not confident with odin and dont want to risk your tablet, your better of waiting for the battery to go flat. But if you understand the risks and what ive done here, maybe it'll save you the wait.
Click to expand...
Click to collapse
you're the man! Thank you!

could some one explain it in detail
Firstly you need odin 3.09. My version contains "Odin3 v3.09.exe" which is 2290688 bytes with an MD5 sum of 46947de16219dcbec41c8290353ad50c
Open the exe in your favorite hex editor and at offset 712A change 75 to EB. This disables the "no bin file is selected" error message, so you can do nothing and cause the reboot.
This screen shot was taken after the reboot. Configure the app like this and click start. It'll do nothing, reboot, and say PASS!
due to being < 10 posts I cant post this link. But you can resassemble it. Mods, if you want to verify this link and fix my post, go ahead.
http: // i.imgur.com / X41Cq3s.png
If your not confident with odin and dont want to risk your tablet, your better of waiting for the battery to go flat. But if you understand the risks and what ive done here, maybe it'll save you the wait.
Click to expand...
Click to collapse
nevermind I fixed it already

[GUIDE/FIX] {S4-MULTI} No Sound &/ WiFi &/ Bluetooth After Unbrick/Update? Read Me!

[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

Question Phone stuck in a boot loop please help :(

Hello everyone good day.
Sadly my phone Samsung galaxy A22 has stumbled into a boot loop been happening for couple days it started when I put the phone on charge and heard it vibrating to which It was constantly rebooting over and over as soon as the Home Screen loads after a second it just reboots I tried to do a reset using power + volume down and no luck also tried wipe cache partion in the recover menu and repair apps but no luck tried searching YouTube for fixes and also called a phone repair shop and said it’s a tough one as I want to keep my data meaning I can’t do a factory reset as I have a lot of stuff I need on the phone so I am reaching out here as a last resort it would make my day if someone could help thanks.
Note: after many restarts the phone managed to come on a couple of times to which after entering my pin a pop up would happen saying “ serious software issue detected check for update “ if i click check the message goes away then it says android starting but fails to start up after 30 seconds to a minute it just re boots again I had some hope as it happened a few times it allowed me to put my pin in but on the android starting screen it would never get past and eventually reboot again I haven’t updated the phone for a while so is it also possible to update from download mode without losing my data or do I need some room for that??

Read I could try safe mode unfortunately that didn’t work either

Try downloading your phones firmware on samfw and installing it with the HOME_CSC, not CSC without HOME!!!

HeroGamer007 said:
Try downloading your phones firmware on samfw and installing it with the HOME_CSC, not CSC without HOME!!!
Click to expand...
Click to collapse
Hey how can this be done? Never done this before any guides you could link me to?

ThePhoneGuyy1 said:
Hey how can this be done? Never done this before any guides you could link me to?
Click to expand...
Click to collapse
IF SOMETHING FAILS DO NOT PROCEED TO AVOID ANY FURTHER DAMAGES!!!
I AM NOT RESPONSIBLE FOR ANY DAMAGES DO TO YOUR PHONE!!!
1. Power off your Phone
2. Now hold the volume up + down button and while doing that plug in a usb cable that is connected to your pc
3. You should see some kind of blue screen, press volume up and it will show "Downloading..."
4. Now Download Odin3, unzip it and Open the EXE on your PC (Click OK on the Warning)
5. You should see COM0 (the 0 can be any other number) under the ID:COM label, if it doesnt appear check your USB connection
6. Download your Device's Firmware:
go to SamFW.com and search for your model on the big Search Bar, if you don't know if its the F or M variant check the packaging, it should be on there. then Click on the Country you're in (or the Country your phone is from) and scroll down until you see this section:
{
"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"
}
Click on the Most-Top Version and select "Download on Browser" (you might need to login with google).
7. after that you should have 5 files starting with AP_, BL_, CP_, CSC_ and HOME_CSC
8. go into Odin and click "BL", then select the "BL_" file, do that for BL, AP and CP
9. now select the "HOME_CSC_" file on the "CSC" button, make sure its the HOME_CSC File!!!
10. after you made 10 time sure its the HOME_CSC file click start and pray
11. after the whole process your device should reboot and work.

HeroGamer007 said:
IF SOMETHING FAILS DO NOT PROCEED TO AVOID ANY FURTHER DAMAGES!!!
I AM NOT RESPONSIBLE FOR ANY DAMAGES DO TO YOUR PHONE!!!
1. Power off your Phone
2. Now hold the volume up + down button and while doing that plug in a usb cable that is connected to your pc
3. You should see some kind of blue screen, press volume up and it will show "Downloading..."
4. Now Download Odin3, unzip it and Open the EXE on your PC (Click OK on the Warning)
5. You should see COM0 (the 0 can be any other number) under the ID:COM label, if it doesnt appear check your USB connection
6. Download your Device's Firmware:
go to SamFW.com and search for your model on the big Search Bar, if you don't know if its the F or M variant check the packaging, it should be on there. then Click on the Country you're in (or the Country your phone is from) and scroll down until you see this section: View attachment 5891443
Click on the Most-Top Version and select "Download on Browser" (you might need to login with google).
7. after that you should have 5 files starting with AP_, BL_, CP_, CSC_ and HOME_CSC
8. go into Odin and click "BL", then select the "BL_" file, do that for BL, AP and CP
9. now select the "HOME_CSC_" file on the "CSC" button, make sure its the HOME_CSC File!!!
10. after you made 10 time sure its the HOME_CSC file click start and pray
11. after the whole process your device should reboot and work.
Click to expand...
Click to collapse
I’ll make sure to give it a good read I appreciate that hopefully this can fix for good quick question before i proceed do I need enough storage for this to update because I remember it being almost full if that’s the case is this possible by inserting an SD card without losing data? Just wanted to check before I proceed as my storage was close to being full

ThePhoneGuyy1 said:
I’ll make sure to give it a good read I appreciate that hopefully this can fix for good quick question before i proceed do I need enough storage for this to update because I remember it being almost full if that’s the case is this possible by inserting an SD card without losing data? Just wanted to check before I proceed as my storage was close to being full
Click to expand...
Click to collapse
It shouldn't need storage, it rewrites the system files and does not just "adds" them, so it should be at max 1-5 hundred MB bigger

HeroGamer007 said:
It shouldn't need storage, it rewrites the system files and does not just "adds" them, so it should be at max 1-5 hundred MB bigger
Click to expand...
Click to collapse
Perfect thank you so much will give this a try soon will update you what happens really appreciate you taking the time

ThePhoneGuyy1 said:
Perfect thank you so much will give this a try soon will update you what happens really appreciate you taking the time
Click to expand...
Click to collapse
Oh also to check the Country from which your phone is (you need to select that when downloading firmware) you can apparently use recovery mode, go into recovery mode (volume up + power while being plugged into a pc) and check if it says something with CSC-Code on the bottom, the 3-digit code after that is the Country Code which you will need to download.

T0stbrot said:
Oh also to check the Country from which your phone is (you need to select that when downloading firmware) you can apparently use recovery mode, go into recovery mode (volume up + power while being plugged into a pc) and check if it says something with CSC-Code on the bottom, the 3-digit code after that is the Country Code which you will need to download.
Click to expand...
Click to collapse
Sadly I haven’t been able to get this to fix used Odin and downloaded correct version for my model and csc code Odin said pass but phone still in boot loop

ThePhoneGuyy1 said:
Sadly I haven’t been able to get this to fix used Odin and downloaded correct version for my model and csc code Odin said pass but phone still in boot loop
Click to expand...
Click to collapse
I seen a video of someone using Odin once done there phone rebooted and showed a pop up saying updating apps etc along those lines but for me it just rebooted after Odin showed pass then bootloop again and a menu saying phone couldn’t start properly and get the same message “ serious software issue check for update “

ThePhoneGuyy1 said:
I seen a video of someone using Odin once done there phone rebooted and showed a pop up saying updating apps etc along those lines but for me it just rebooted after Odin showed pass then bootloop again and a menu saying phone couldn’t start properly and get the same message “ serious software issue check for update “
Click to expand...
Click to collapse
Try going into recovery maybe and deleting the cache and repair apps

T0stbrot said:
Try going into recovery maybe and deleting the cache and repair apps
Click to expand...
Click to collapse
Is that wipe cache partion? If so sadly not work for me and repair apps no fix but upon some research I’ve read it’s possible the storage can cause a bootloop also? Not sure if true but my phone was literally almost full as unfortunately didn’t make some room in time it seems this is most likely the reason as before bootloop I never installed any updates or did anything just simply put the phone on charge then it bootloop I’ve read that because there is almost no storage the phone just can’t boot up properly? No idea tbh but seems most reasonable as of now :/

ThePhoneGuyy1 said:
Is that wipe cache partion? If so sadly not work for me and repair apps no fix but upon some research I’ve read it’s possible the storage can cause a bootloop also? Not sure if true but my phone was literally almost full as unfortunately didn’t make some room in time it seems this is most likely the reason as before bootloop I never installed any updates or did anything just simply put the phone on charge then it bootloop I’ve read that because there is almost no storage the phone just can’t boot up properly? No idea tbh but seems most reasonable as of now :/
Click to expand...
Click to collapse
Also whilst my phone was bootlooping I got a menu similar to recovery menu saying android failed and a few options I believe was
1) try again
2) wipe app data
3) power off
Also a message saying if you don’t want to lose any data then it should be taken to a technician however one of the places I called said there is not much they can do as I wanna keep my data :/

Does it say wipe all data or wipe app data?

T0stbrot said:
Does it say wipe all data or wipe app data?
Click to expand...
Click to collapse
Wipe app data if I remember right it said about wiping the data of apps and configuration so this has also lead me to thinking it could be an internal storage also no idea as phone says there is a serious software issue it’s been a nightmare hopefully fix eventually just worried about my data I believe wipe app data will keep photos and videos safe but it would log out all my emails and wipe all my apps also? :/

ThePhoneGuyy1 said:
Wipe app data if I remember right it said about wiping the data of apps and configuration so this has also lead me to thinking it could be an internal storage also no idea as phone says there is a serious software issue it’s been a nightmare hopefully fix eventually just worried about my data I believe wipe app data will keep photos and videos safe but it would log out all my emails and wipe all my apps also? :/
Click to expand...
Click to collapse
Yeah it will delete all app data, so for example your google login or email login, it should keep your photos tho as that is not app data

T0stbrot said:
Yeah it will delete all app data, so for example your google login or email login, it should keep your photos tho as that is not app data
Click to expand...
Click to collapse
Hmm do you think this is pretty much the last resort for me to try if I can keep pics and videos I guess that’s a bonus just would have to pray it does let me boot my phone up and that I can regain access to emails and other stuff via logins not all wrote down so I guess at this point with nothing I’ve tried working seems one of the last options unless there is other ways to extract data whilst phone is in bootloop but haven’t found many also

Did you setup any 2FA Authenticator apps that aren't synced with a cloud? That would be pretty dumb and you probably won't be able to login except you saved the backup codes. But otherwise if it really only deletes app data it should be fine, and as long as you have access to your email you should be able to reset all your passwords.

Do you can share your phone recovery mode picture with download mode