Related
Hello..!!
I need some help here. I tried to flash a custom ROM (X-Note (build 6.0) for Galaxy S5 GM900F) and then flash a new bootloader, the problem is that my device will never pass the booting process. I was stuck with the logo and black screen. I have searched and tried tons of tutorials and fixes but have not solved it.
I even tried to wipe Dalvik cache, wipe data, format system. I even put out the battery and leave it for sometimes, then on but the problem is still there.
This link to bootloader that I downloaded and flashed using Odin (after successfully installing custom ROM) and also the instructions that I followed to install the custom ROM.
https://www.androidfilehost.com/?fid=23622183712475277
When I try to re-install stock Samsung via Odin, it shows a Fail message. I don't know where to go from here and I'm really worry that my phone will never come to work.
Please help me to solve it.
..
fffft said:
I'm too busy today to describe this in detail.. but here are a few comments that may help you.
First, it is fixable. Usually it's enough to boot to recovery mode (phone off, then press and hold home + volume up + power buttons). Then from the recovery mode menu, choose wipe system cache. Then reboot. If you still have an issue then try a system data format from the Settings menu (this will erase user files!).
And as a last resort, restore a backup (if you have one) or a full, stock firmware image with Odin or Heimdall. Odin is infamous for being a bit picky, so don't panic if you get a failed message. That happens to all of us. Look for a detailed Odin tutorial or how to flash back to stock firmware thread that has Odin tips e.g. use a different USB cable + USB port. Temporarily turn off anti virus on your PC.. If the Odin write fails, do not close the Odin window. Just pull the battery and USB cable from your phone again.. put the battery back.. go back to download mode (home + volume down + power), plug the USB cable back, then press the start button in Odin again. It's important that the Odin window was open the whole time.
It may take a few tries (Odin can be frustrating) but you'll succeed.
.
Click to expand...
Click to collapse
Thanks for your words, you give me some hope because I thought my phone is now useless. I'll try again as you said.
I flashed xposed framework. It booted a few times crashed and then I could still get to recovery twrp. I then flashed the original rom I was using it booted up and started completely but again crashed. So I booted recovery and flashed the original rapture 5.1.1 rom and it booted completely but after a few minutes it also crashed.
After that I was in a bootloop. In a weird way I'd have to take out the battery wait a few minutes then the power button would work (on battery). It'd try to boot vibrate, show the samsung note 4 letters and then shutdown.
Weird part is if I plug the wall charger in it just vibrates and tries to boot indefinitely. If I long hold the power button nothing happens. If I pull the usb cable out it cuts power even though I have a fully charged battery.
I've flashed twrp reovery via odin first, no luck. I've flashed the original cod6 firmware without luck. Then the original kernel and recovery. Nothing seems to work. Is my power button dead. My problems are similar to this also but it worked fine before I flashed xposed framework wanam.
http://forums.androidcentral.com/sa...battery-then-turns-off-after-two-seconds.html
The reason I think it might not be the power switch is if I take out the battery wait 15 and plug it back in the phone does not auto restart itself. I have to hold the power button to start it. After Odin flash of COD6 firmware I only get to recovery img message at the top and then it turns off.
Very similar to this problem
http://forums.androidcentral.com/sa...k-recovery-booting-screen-how-can-i-past.html
flash stock recovery, twrp, cwm recovery and still can't get to it. Only thing I haven't flashed it the modem.
Thanks for any replies
Sounds like a hardware r
Problem if odin is not flashing correctly and it has done correctly in the past. I had similar but could boot into download mode and flash nut it failed flashing . Had to reflash root, then reflash a stock rom which boot looped, then root, then flash recovery, then flashed a custom rom cmw2.1 which worked. Then to male sure I reflashed origianl 5.0 rom which then worked. Then started again rooting recovery and flash cm12.1 and all is fine. As long as u have download mode there should be a way to fix it try my method as I thought I had a paper weight for about 3 hours while I figured out the above.
Thanks
Steve
Digipro said:
Sounds like a hardware r
Problem if odin is not flashing correctly and it has done correctly in the past. I had similar but could boot into download mode and flash nut it failed flashing . Had to reflash root, then reflash a stock rom which boot looped, then root, then flash recovery, then flashed a custom rom cmw2.1 which worked. Then to male sure I reflashed origianl 5.0 rom which then worked. Then started again rooting recovery and flash cm12.1 and all is fine. As long as u have download mode there should be a way to fix it try my method as I thought I had a paper weight for about 3 hours while I figured out the above.
Thanks
Steve
Click to expand...
Click to collapse
Thanks I will try, I've tried everything odin cod6, cog2, bootloader, baseband, rom, kernel, flash reports good now but still bootloop, even tried Kies3, it completely said everything is good rebooted and just booted at the top left saying recovery... booting then shuts off.
Really weird part is as soon plug power to micro usb port it starts booting without me pressing any buttons?
First thing I do if it goes wrong is reflash original stock rom to create a clean sheet. I always find the simplest solution is usually the best, f
Aching modems, kernels, well u know what windows is like with registry errors cross link .dll files. Like with windows keep backups and reload and start afresh sometimes going too deep to fix something can make it worse :s
Yea it shouldn't boot just from inserting power cable it should goto charge screen.. If charge screen is corrupt then that could explain why It boots to go to charge screen but can't so hence the behavior. Makes sense to me .
Thanks
Steve
Mi A1 bricked, hard resetted it by opening the back cover and shorting two points.
It gets detected by mi flash tool but I cannot flash the stock room. It is giving me "cannot receive hello packet" and then it times out.
Any help will be appreciated.
Thank you.
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
foggs said:
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
Click to expand...
Click to collapse
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
foggs said:
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
Click to expand...
Click to collapse
Yup, I ruined one of my usb-C cable trying do do deep flash that way. I failed, so I went to one repair shop and open up the device and did the "two point short thing", which helped to be recognized by the flash tool. Then it showed me that "hello packet" thing.
Then I dug around the Internet for couple of hours and changed the USB port on laptop. I also restarted the laptop after I reinstalled the drivers. Then it actually flashed that ROM I mentioned above. But just that ROM. I tried the latest to oldest versions and all of those ROM would flash but then they will brick the phone again. Only that one worked, i.e. helped me to get to bootloader. But alas it is stuck there, no matter how many times I clean flashed it, it is refusing to boot to system. It gives me "Your SYSTEM HAS BEEN DESTROYED" message on every boot. It only goes to bootloader if I press Volume Up + Power button while booting. And it's a dead end for now. I don't know what else to do.
Also this phone was bought in Hong Kong and its warranty won't work where I am right now. I already took it to the authorized service center and those lazy people told me to change the motherboard and it will cost around $180. So I took it back. lol
Disable driver enforcment to get the hello packet.
TrueMS said:
Disable driver enforcment to get the hello packet.
Click to expand...
Click to collapse
still no hello packet
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
:victory: Held the power button, clicked flash.. Success :good: it's in the process of flashing now. Thank you
Edit: successful flash now to just let it charge up. Thanks again guys for the help/suggestions ?
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
foggs said:
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
Click to expand...
Click to collapse
Ur presist partition is damaged..thr are many guides here about recovering it
Do the "factory flash" mode in MiFlash under EDL mode as a last resort. May wipe your IMEI and MAC's, not sure.
Could not receive magic packet is solved by using USB2 port, Windows 7 x86 (32-bit) in a VM, or power-cycling the device and starting over, any or all of the above.
Deep flash cable is only for kicking the phone out of diagnostic mode and into QDFlash mode. Not necessary if using test point. I had to use testpoint method myself, couldn't get deepflash cable to work for getting out of diagnostic mode. I hope I can get it working next time though when I inevitably brick it from repartitioning; as I broke my screen when disassembling
apexashwin said:
Ur presist partition is damaged..thr are many guides here about recovering it
Click to expand...
Click to collapse
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Did you find the guide about fixing constant reboot? It's around somewhere, might be on MIUI forum.
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Please try presist resurrector from guides section
I think i've got it back to life.
first tried to flash 7.1.2 stock the earliest one (tissot_images_7.8.23_7.1), it hung on flashing it for nearly an hour with no success, closed the miflash application then tried another 7.1.2 (tissot_images_7.10.30_7.1)flash successful, then in stalled twrp did the persist command and reboot nearly got to the home screen just never getting over the line. then i flashed January 8.0 oreo (tissot_images_8.1.10_8.0) and was able to get on to the home screen/go into settings/enable developer options but it would eventually reboot itself, went back into twrp and did the persist command again and reboot.. success (fingers crossed) now downloading/applying April security update as i type this.
Boo installation problem with the update
looks like i lost my imei, https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190 this is going to be a pain.. i'll post back when i try this. need a break from this mess ive made lol
thanks for the help/suggestions appreciated big time.
edit: up to the latest update April 1 security patch.
all done, down to 7.8.23 rom, did the stuff to get the imei back then flashed latest oreo rom
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
Man, I was trying to fix my Redmi Note 4X for the past 6 hours and you were the ONLY guy to talk about this. Thank you so much. :victory:
THANK YOU
udaan said:
it was solved after i changed the usb port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then twrp. But after flashing aosp extended rom it gave me "the system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
man you just solved my problem and saved for me like 180 eur thank you you are a god !!!! Thanks for using this site !!!!!!!!!! <3 <3 <3
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I was unable to flash on MiFlash and after changing USB port I managed to do it!.
Many thanks!
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
I love you!
First it started right into Odin Mode. After holding Volume Down and Power to exit it, the screen went black (as expected). However, afterwards it won't boot up again. Tried normal boot, recovery and download. Removed the battery and put it again, didn't work. Also tried various cables and outlets. Tried the sequence for download mode (holding Power + Volume Down + Home, then pressing Volume Up - even if it didn't show anything on screen) and connected it to my PC. The computer played the sound as if a device was connected, then after some seconds Windows said that the USB device was not recognized. Odin did not recognize it either. Samsung 300K tool doesn't work as well. Do you have any suggestions, please? It's quite urgent.
Try installing official device drivers Inform us after that what's happening. Thank you
Rjt KD said:
Try installing official device drivers Inform us after that what's happening. Thank you
Click to expand...
Click to collapse
I can't. It's not booting at all. Never rooted it or changed its ROM.
You mean it doesn't even show download mood or recovery mood?
Rjt KD said:
You mean it doesn't even show download mood or recovery mood?
Click to expand...
Click to collapse
Yes, not even the charging battery logo when it is powered on. Tried using an USB Jig, fails as well.
Sent from my iPhone using Tapatalk
tomadimitrie3 said:
Yes, not even the charging battery logo when it is powered on. Tried using an USB Jig, fails as well.
Click to expand...
Click to collapse
I'm sorry to say that.. It's a hardware related issue... U need to take it to service center to repair Thank you
I've flashed marshmallow stock on stock lollipop via Odin but after completion J500H boots and immediately resets or off after first boot screen appears. so please help that why this problem is here???
Also please tell that custom ROM can be installed on the J500H or not ( bootloops and restart issue immediately)
Is it possible to flash again? If yes...
Then first wipe delvik cache then flash again, before flashing make sure to untick auto reboot on odin's log option... After flashing done don't reboot immediately first wipe delvik cache then restart...
If it doesn't allow you to flash then u need to take it to service center...
Yes it's possible to install custom rom using Odin but sometimes it fails if usb debugging is not enabled! You can search on Google for that or any thread here.
I was going along ok until I made the fatal error of transferring the Magisk patched file to PC via MTP instead of taking the time to re-learn adb, which must have corrupted it. Thus predictably Odin hung and I am in trouble.
Where I am stuck is being unable to turn the phone off to come back in download mode to start over with stock firmware. I have been unable to find any secret button presses, and the battery doesn't seem to want to die leaving me with an $800 paperweight.
I did search around for this first and didn't find any real answers. Has anyone found an effective solution to this problem? Thanks.
fastzombies said:
I was going along ok until I made the fatal error of transferring the Magisk patched file to PC via MTP instead of taking the time to re-learn adb, which must have corrupted it. Thus predictably Odin hung and I am in trouble.
Where I am stuck is being unable to turn the phone off to come back in download mode to start over with stock firmware. I have been unable to find any secret button presses, and the battery doesn't seem to want to die leaving me with an $800 paperweight.
I did search around for this first and didn't find any real answers. Has anyone found an effective solution to this problem? Thanks.
Click to expand...
Click to collapse
If Odin recognizes you device, you can flash firmware in emergency recovery.
Cindysmith0994 said:
If Odin recognizes you device, you can flash firmware in emergency recovery.
Click to expand...
Click to collapse
Thank you, but the PC won't recognize the device. What does happen is the emergency recorevy screen tries to come up. I tried starting in download mode with bixby+vol down then USB. I did get the battery low enough where I don't get the teal screen of death anymore, perhaps it is too low for USB to work? What I was hoping for was the charging animation but no luck. Surely this is just a software problem and there is a way out.
fastzombies said:
Thank you, but the PC won't recognize the device. What does happen is the emergency recorevy screen tries to come up. I tried starting in download mode with bixby+vol down then USB. I did get the battery low enough where I don't get the teal screen of death anymore, perhaps it is too low for USB to work? What I was hoping for was the charging animation but no luck. Surely this is just a software problem and there is a way out.
Click to expand...
Click to collapse
Did you try getting into recovery and perform a data factory reset and then see what happens?
Just load the stock firmware BL, Ap, cp and home csc into Odin if you see emergency teal screen. The emergency screen will start loading
Black screen ....Perhaps your battery is dead?
Thank you all for the replies. I had let the battery get low in a misguided attempt (based on advice elsewhere) to get it to shut off. I had to let it charge a while for it to wake up enough for PC to see it. Then I was able to flash in Emergency Recovery mode.
Thank you for the help.
fastzombies said:
Thank you all for the replies. I had let the battery get low in a misguided attempt (based on advice elsewhere) to get it to shut off. I had to let it charge a while for it to wake up enough for PC to see it. Then I was able to flash in Emergency Recovery mode.
Thank you for the help.
Click to expand...
Click to collapse
Glad you got your device up and running ?
Maybe someone can help me. I seemed to have borked my phone. I kept getting "Google is Stopping" with no way to fix it, so I tried reflashing my firmware in odin. After I loaded all the files and hit start, I realized I didn't untick auto reboot, so I tried aborting the installation and ended up with screen (I've had it before and got out of it by still flashing in Odin, but now, if I try to reflash firmware while in this screen, it's stuck on SYSTEM in odin.
Any help appreciated!
Try this
That is where I got stuck. Are you trying to flash stock or patched firmware? I had to start over with stock as I copied the patched via MTP instead of adb and it got corrupted.
I think what I did was unplug and reset Odin. Wait for screen to turn off, then make sure it is at least 80% charged. Then Bixby + Vol Down + plug in and you will go back to this screen. Then I was able to flash stock. I had to go so far as to re-lock bootloader and flash stock again since my "OEM Unlocking" was not just greyed out but missing. Since then I've had no time to try again, but at least I have a working phone.
This is my anecdotal procedure, can't say if it is the right or best one.
Hi All,
I was trying to flash the latest firmware for my device (G9750ZCU2ASG4) and during the odin process, my computer restarted which failed the update halfway through. I rebooted the computer, tried again, and it was trying to establish a connection for a really long time, so I disconnected my phone from the USB port on my computer, and held Power and Volume Down to try and force reboot the phone. I was going to try and go back into download mode to restart the process. My phone mentioned something about needing to do an emergency recovery, but I continued to hold down the power and volume down keys and then everything went black on the phone.
I've tried multiple USB cords, all of the button commands known for the device, and have even tried to perform the emergency mode recovery on my device, but it seems like it's in some sort of locked state; What I mean is the phone is stuck on a black screen. I can't "boot" into recovery or into download mode. The phone doesn't even vibrate when I hold the power button or power and down to try and force reboot it. Odin doesn't recognize the phone when I plug it into the computer nor does the device manager on my windows computer.
Does anyone have any experience with this sort of issue or any idea of what else I can do to try and get into download mode to flash my firmware again? All help, suggestions, or comments regarding this are much appreciated.
Sounds like the battery is dead
Hi Dude, I am struggling with the same problem, read this post and it came to me, had to come back and give you the solution.
Press bixby+volume down, IMMEDIATELY after the screen goes off, hold volume up and down while connecting the USB cable super fast.
You have got like 10ms to do it
Otherwise it just goes back to the AVB FAIL screen
Ran into this issue, none of the above worked for me.
This is how I resolved:
1) Placed phone on wireless charging mat and let it boot to emergency recovery screen
2) Load TWRP into AP slot of Odin and leave the window open on your computer ready to flash
3) Connect phone to computer whilst it's on the mat and press start in Odin as soon as your device appears
It may fail a few times but if your quick you can install TWRP.
4) Now boot into recovery and let your phone charge to a reasonable level (above 20%)
5) Boot into Download mode and flash your desired rim via Odin