Related
I turned on my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected. This occurred after using Odin for something I downloaded from http://forum.xda-developers.com/showthread.php?t=1739426.
asodiu said:
I was messing around with my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected.
Click to expand...
Click to collapse
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Larry2999 said:
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Click to expand...
Click to collapse
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
After flashing, did you boot to recovery and wipe data and cache?
audit13 said:
After flashing, did you boot to recovery and wipe data and cache?
Click to expand...
Click to collapse
As I have said, I am unable to boot to recovery or boot to download mode. I did not wipe data and cache.
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
asodiu said:
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
Click to expand...
Click to collapse
I recommend getting your hands on the Android SDK and using adb to boot into download and recovery modes. I got a water damaged d2att from friend a few months ago and the old volume down key doesn't work and using the command prompt and adb, you can get it to boot to whichever mode you want.
Sent from my SPH-L710 using Tapatalk
asodiu said:
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
Click to expand...
Click to collapse
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Larry2999 said:
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Click to expand...
Click to collapse
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
asodiu said:
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
Click to expand...
Click to collapse
Glad to know it's working fine now. Unless the firmware for the 2 phone models have identical build numbers, I'd be surprised the post suggested that cross-flashing may be OK.
Can't flash unbranded Oreo ROM and "e: failed to find /misc partition" message after
Hi guys, here's the deal.
I've bought this phone from an Argentina company called Claro, it has all typical bloatware from the carrier, apps, logo boot, ringtones, etc. So I've decided to flash my brand new Samsung Galaxy A5 2017 (SM-A520M) with the unbranded OREO ROM version from SamMobile, with the 4 files through Odin. Well, the thing's that I didn't know that because of the new security patchs (and for what I know), the OEM unlocked option was disabled it was impossible to flash. I mean Odin recognized it but the steps didn't even appear like always did. I've investigated a bit and I saw that OEM was disabled and because of that, I'll have to wait a week or so to unlock the feature. I've read that setting the date a week back I was able to activate it. And so I did, and it worked, so I thought... I've plugged the phone with Odin in Download Mode and I was determined to finally flash the new ROM. Long story short, it got stuck on SET PARTITION, which I think is the first message that pop-ups on Odin when flashing. So, I waited and waited but nothing happened, I saw that the whole process got stuck. The only thing I remember to read was NAND START WRITTING and nothing else.
After several minutes with no response I've unplugged my phone, and I press the power button. I saw the Samsung logo on loop, I almost died. I've read some forums about the issue but nothing certain, I guess this problem is kinda new. My concern was that when I went to Recovery Mode I saw the message below the options "e:/ failed to find misc/partition" that's when I really thought that it was a real problem and probably my phone was bricked forever. Luckily I made the factory reset and then it booted again. The phone is working great but, I'm very concerned about that message that appears on Recovery Mode, there's something wrong with that partition and for what I read and know about it there could be something missing from my phone that could be essential.
Thoughts? What can I do? I also downloaded Samsung Smart Switch to try to recover the firmware and install it to begin again but the option won't appear. My phone is detected, but I can't use the Emergency Recover with the original Firmware on Smart Switch. One more detail, the phone was bought from a company and it has the logo, ringtones and app from that company. Reason why there's no Oreo update yet with the company, so I have to wait but I really want the unbranded Oreo ROM.
What can I do? I really want Oreo unbranded but I don't know how to procced without screwing my phone. Thanks for reading, this is my first post in the forum.
Which Odin version have you used?
Ok i tell you u have to do to recover your phone and get oreo ?
1-u have to use new version of odin V13.3.1 (with LZ4 support )
2-Download any stock firmware oreo 8.0 from sammobile and flash it
Thats it
I case that not work with u so downlad combinition rom (factory binary rom ) and flash it
Wipe your phone then reflash stock rom oreo
It was very helpful for me
Reeii said:
Which Odin version have you used?
Click to expand...
Click to collapse
the latest version 3.13.1
ayman16 said:
Ok i tell you u have to do to recover your phone and get oreo
1-u have to use new version of odin V13.3.1 (with LZ4 support )
2-Download any stock firmware oreo 8.0 from sammobile and flash it
Thats it
I case that not work with u so downlad combinition rom (factory binary rom ) and flash it
Wipe your phone then reflash stock rom oreo
It was very helpful for me
Click to expand...
Click to collapse
No man, if it were that easy I wouldn't post anything. There's something that won't allow me to do it. It seems that because my phone is in "Pre-Normal" status on downlaod mode there's no chance to flash until it changes to "Normal," and for what I've read I have to wait one week. My question has to do with if is something serious the message "e: failed to find /misc partition" in download mode. What do I have to do from now on? Please read the whole post so you can understand my query. Thank you for your reply and intention to help. :good:
I have simmilar message, but i am not even rooted. "Failed to clear BCB message : failed to find misc partition."
There is nothing to worry about.
Hi!
I have a problem with my new Sony Xperia XA2. When I got my new phone I decided to flash LineageOS 16.0 (the unofficial build from LuK1337), however the Lineage-build is not the problem. I got the problem when I tried to flash TWRP and Magisk, and I've realised that I did it too quick.
Here's what I did:
0. Unlocked bootloader
1. Booted TWRP
2. Flashed LineageOS
3. Flashed GAPPS.
4. Flashed Magisk.
So far, so good. This worked.
5. Decided to flash TWRP to get rid of the standard recovery.
6. Now both the standard recovery and TWRP seems to be gone.
Is there a way to revert to the standard recovery? I've tried to download FlashTool and XperiFirm, and I've downloaded the correct stock image for my Xperia XA2 Dual (H4113), but I cannot get it to only flash the bootloader.
My understanding is that the recovery and bootloader resides on the same partition. Is this correct?
When I try to flash the bootloader with FlashTool, I get an error stating that the device is identifying as H3113, which is the single-sim-version.
Thank you for the help!
I managed to get my phone working again by using Emma, as I had managed to soft-brick my phone. The bootloader said that the phone was corrupt, and turned off after 5 seconds. Using Emma and the bundled USB-C-USB-A-cable did the trick for me.
Now I'm going to install TWRP once more, and hopefully I'll manage it correctly this time.
My understanding is that we cannot install TWRP as a replacement recovery on this device because there is no true recovery partition. It's part of the boot partition. Hopefully someone will come along and correct me if I'm wrong.
You can install twrp on a/b devices. However, it installs to /boot. Thus every upgrade kills it. Which really sucks as lineage recovery sucks bad.
hjahre said:
Hi!
I have a problem with my new Sony Xperia XA2. When I got my new phone I decided to flash LineageOS 16.0 (the unofficial build from LuK1337), however the Lineage-build is not the problem. I got the problem when I tried to flash TWRP and Magisk, and I've realised that I did it too quick.
Thank you for the help!
Click to expand...
Click to collapse
Hello,
sorry for the delay.
You can use EMMA to flash back the stock firmware, however if you don't want your data lost, use flashtool ( http://flashtool.net ) and make sure your userdata is Wipe Excluded
what is the trick of USB-C-USB-A
Hello friend, what is the trick of USB-C-USB-A, can you explain it, because I can not get flashtools to work on my sony xa2, explain me the trick please
cristianrb said:
Hello friend, what is the trick of USB-C-USB-A, can you explain it, because I can not get flashtools to work on my sony xa2, explain me the trick please
Click to expand...
Click to collapse
There's really no trick to it. Just plug the cable bundled with the phone and plug it into your PC.
My problem was that I've got a Macbook Pro that only have USB-C ports. When I tried a cable with USB-C connectors in both ends, my phone would not let me flash from my computer. When I used the bundled cable and a USB-hub it worked as it should
hello guys,
i have bricked my phone i earlier downgraded my phone and then i updated the phone to the last update of nougat and then i locked the bootloader(my biggest mistake) as i was not reciving oreo updates and i thought that it was due to the unlocked bootloader (earlier i rooted my phone but after unrooting i was unable to update when in stock and though i flashed stock rom no updates and i had to take it through service centre ) then i was unable to flash the stock rom using sp flash tool it was showing(BROMCODE_CMD_SEND_FAIL) i tried changing the download agent but no help then i read somewhere that is the usb is inserted and the battery is pluged in at the same time it would flash and somehow i managed to flash oreo
But due to lack of any custom rom and any update in the stock rom on xda i was forced to downgrade it to nougat (as oreo gave me onscreen time of 2-4 hr at max) so i thought i wouldn't do any **** after this but as i knew that even after flashing I was not able to flash rom using sp flash tool ( i even tooked phone to service centre they asked to change the motherboard as they were even not able to flash it ) but now 7-9 days ago it got updated and it stopped working yesterday then i tried hard to flash it but all in vein it was getting on sometimes but in bootloop)
somehow i managed to get it into fastboot and i used flashall.bat to downgrade and it showed
WAITING FOR ENUMERATION (with administrative privilege )
but normally it stared flashing and gave error (FAILED TO MAKE PGPT SOMETHING SOMETHING )
then i tried to flash twrp manually to wipe and use TWRP flashable oreo but then it showed flash write error
then i saw in xda to clear cache
I USED THIS COMMAND
PS D:\adb> .\fastboot erase cache
then my friend told me as it was unable to get into recovery it may be error with that then i used
PS D:\adb> .\fastboot erase recovery
PS D:\adb> .\fastboot erase userdata
then i was tried to flash oreo recovery and showed flash write error
but then i saw a post he guy told to use
PS D:\adb> .\fastboot boot TWRP.img
to boot into TWRP and use adb shell to flash recovery and rom
and now its not getting into fastboot but showing charge and led is glowing
and while using sp flash tool am getting STATUS_DEVICE_CTRL_EXCEPTION
pls help :crying:
so screwed i am now heeeelllllllllpppppppppppp!!
THANKS IN ADVANCE AND PLS IGNORE ANY TYPING MISTAKES
I recently found a moto g5 in one of my fellow "old tech" drawers and decided to turn it on, it was on the
1. May 2018
Security patch on nougat, I decided to use the inbuilt system updater to go to Oreo, and now....it crashes during flashing process after about 25-30% completion,
Now im guessing boot or System is not properly installed due to the zip file having aborted mid-flash
Recovery doesn't properly boot as that is used to install the update and thus imidiately goes to doing that
Also, it hang up during installation on random times, it basically has a record of 2mins of not crashing whilst still being stuck on 30%
I got it to "boot" when trying factory mode, yeah it crashed mid boot animation...not a help
Any suggestions? EDL mode maybe?
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
TheFixItMan said:
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
Click to expand...
Click to collapse
SOMEHOW it just decided to boot, I have never seen such behaviour, even on my g5s which I had for a while, (and am currently daily driving to school if it wasn't closed....NEVER
Maybe I'll unlock it and try somehow recreating it? Well it's in physically rough shape but all components inside are fine...so that can't be the reason....?
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
anonymous724 said:
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
Click to expand...
Click to collapse
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
riyan65 said:
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
Click to expand...
Click to collapse
no luck on this front, gets to the passcode screen, write in passcode then motorola logo shows and screen keeps on turning off and on.
Thanks for the effort though, much appreciated
Mine is similar to yours. Initially was on permanent loop of the following:
1. Boot to moto g splash screen... Repeat
2. Boot to lock screen then usually a few loops of 1. (after entering the patter or left Idle)
The phone initially didnt have any developer options enabled.
I wiped cache using recovery mode. Restarted and pretty much the same thing except that it would on rare occasions actually fully boot up usually only last a few minutes before cycling between steps 1 and 2 above.
I used those rare boot ups to backup all files and enable any USB debugging /oem unlock (incase I need to use a solution dependent on these being enabled.)
Factory resetted it and its still the same with the random successful boot amongst the numerous failed ones.
I managed to hook it up to Lenovo's Lmsa and flash the latest ROM. Now I get a lot more successful boots but still loops every so often. The downside is that I can no longer do any functions that make use of the audio/ mic/ video (can take pictures). If I do then it will crash and loop.
The hardware test on the LMSA passed for every component before flashing to the latest version. Post update it predictably fails on the audio/ mic components.
I guess I'll have to go back to the old version to see I get the audio back.