I need urgent help, I was using TWRP manager and tried to install that over the clockword mod recovery, now the phone is n a booting into recovery loop and wont boot at all.
I was using resurrection remix as a custom rom and that was 6.0.1. Is there anyway I can go back to 5.1.1 stock? I get SW REV Check Failed:Fused 2>Binary 1
Want to help
darksarken said:
I need urgent help, I was using TWRP manager and tried to install that over the clockword mod recovery, now the phone is n a booting into recovery loop and wont boot at all.
Click to expand...
Click to collapse
If you remember what version of android were you on?
Can you boot into download mode?
If you can answer those 2 questions then my best guess is you can ODIN back to stock with out an issue.
Just download ODIN 3.09 from some where shouldn't be to hard to find.
and download the top link from here: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
unzip the samsung firmware(only once), put your phone in download mode, plug it into your computer, open odin, click "AP" and find the file that you just unzipped
make sure you click no boxes but "AP" and hit start and let odin do its thing.If yu have any questions Id be glad to answer
Help
BoiBundy said:
If you remember what version of android were you on?
Can you boot into download mode?
If you can answer those 2 questions then my best guess is you can ODIN back to stock with out an issue.
Just download ODIN 3.09 from some where shouldn't be to hard to find.
and download the top link from here: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
unzip the samsung firmware(only once), put your phone in download mode, plug it into your computer, open odin, click "AP" and find the file that you just unzipped
make sure you click no boxes but "AP" and hit start and let odin do its thing.If yu have any questions Id be glad to answer
Click to expand...
Click to collapse
Okay after this passed my phone is still rebooting in a loop for some reason? Do you know why?
darksarken said:
Okay after this passed my phone is still rebooting in a loop for some reason? Do you know why?
Click to expand...
Click to collapse
Factory reset from recovery should fix it.
Sent from my SM-N910T using XDA Free mobile app
darksarken said:
Okay after this passed my phone is still rebooting in a loop for some reason? Do you know why?
Click to expand...
Click to collapse
Raptor is right, pull your battery for about 20 seconds replace it and hold volume+up and home while powering on. And you should be presented with a dead android. From there I believe you factory reset your phone.
Sorry, in literally always busy but here is the exact step by step method of resetting from recovery:
Turn off the phone. If the phone will not turn off, remove and re-insert the battery.
Press and hold the following three buttons at the same time:
Volume Up key
Home key
Power key.
When the phone vibrates, release the Power key.
When the Android System Recovery screen appears, release all keys.
Press the Volume down key several times key to highlight 'wipe data / factory reset.'
Press Power button to select.
Press the Volume down key until 'Yes -- delete all user data' is highlighted.
Press Power button to select and start the master reset.
When the master reset is complete, 'Reboot system now' is highlighted.
Press the Power key to restart the device
I'm actually having the same issue, but seems more complicated.
I was using resurrectionremix, and bluetooth/lte wasn't working so well so I decided to factory reset it and install the stock factory image.
But when I try to flash using Odin (3.07, 3.09 tried both) it gives me this error.
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> sbl1.mbn
<ID:0/015> rpm.mbn
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone
UDC START
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail : ABOOT
And teh firmwares I tried are
NIH, NK4, COD
MTP Isn't working, the phone isn't recognizing my microSD card either so there's no way for me to flash anything through zip TWRP.
Can somebody help me out? Thanks
Stiria said:
I'm actually having the same issue, but seems more complicated.
I was using resurrectionremix, and bluetooth/lte wasn't working so well so I decided to factory reset it and install the stock factory image.
But when I try to flash using Odin (3.07, 3.09 tried both) it gives me this error.
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> sbl1.mbn
<ID:0/015> rpm.mbn
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone
UDC START
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail : ABOOT
And teh firmwares I tried are
NIH, NK4, COD
MTP Isn't working, the phone isn't recognizing my microSD card either so there's no way for me to flash anything through zip TWRP.
Can somebody help me out? Thanks
Click to expand...
Click to collapse
By chance are you already on 5.1.1 firmware, if you are you can't downgrade back to those lower fws and the stock factory Odin is dok2. Try that 1 instead.
Sent from my SM-N920T using Tapatalk
Related
I was trying to root my galaxy note, I download the rooted stock rom (N7000DXLC2) from here http://forum.xda-developers.com/showthread.php?t=1535025
but the odin failed and showing this
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000DXLC2.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000OLBLC2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.img
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
then my phone can't boot anymore, it jus stuck at the samsung n7000 screen,
i tried to download stock rom and flash again, but it failed like above,
and when i go try to flash the kernel, it success to go to the recovery mode,
but it showing error like
E:Error in /cache/recovery/sec_csc.zip (status 7)
And i maybe forgot to enable usb debugging before i root, is this the cause? how i enable it now?
what can i do now? I tried to change port, change pc, uninstall kies, reinstall driver, close antivirus, and all doesn't work, please help...
To be sure, take out all unnecessary USB devices and use a USB port that's directly attached to your motherboard. Without your phone attached load Odin and load all files. Put the phone in Download mode and hook it up to your pc. When Odin recognizes it then try and flash again.
Make sure there's not a trace of Kies on the pc, just have the drivers installed.
USB debugging should not have to be enabled. There's no way of enabling it without booting up the phone and setting it in the options anyway.
bioweb said:
To be sure, take out all unnecessary USB devices and use a USB port that's directly attached to your motherboard. Without your phone attached load Odin and load all files. Put the phone in Download mode and hook it up to your pc. When Odin recognizes it then try and flash again.
Make sure there's not a trace of Kies on the pc, just have the drivers installed.
USB debugging should not have to be enabled. There's no way of enabling it without booting up the phone and set it in the options anyway.
Click to expand...
Click to collapse
I tried that, and I uninstalled the kies,
but the odin still showing the same error.
PROBLEM SOLVED
for who facing the same problem, just include a pit file in PIT,u can find it here
http://forum.xda-developers.com/showpost.php?p=23234683&postcount=10
solving this for whole day,thanks god it worked......
17n337 said:
PROBLEM SOLVED
for who facing the same problem, just include a pit file in PIT,u can find it here
http://forum.xda-developers.com/showpost.php?p=23234683&postcount=10
solving this for whole day,thanks god it worked......
Click to expand...
Click to collapse
CAUTION : Just dont go on blindly flashing the PIT file. Its a repartitioning file. To be used only when your partition is corrupted.
Galaxy Note stuck
hello,
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but operation failed showing:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> factoryfs.img
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010>
<ID:0/010> Receive Response form LOKE
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried many times but showing the same error everytime.
I am not able to go into the recovery mode......although i can go into the download mode.
When i reboot it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." There is no samsung logo or GT-N7000 logo when you reboot your phone. You only see this warning.
I have some imp data on my internal memory(Phone storage). I have to save that data. Please please please help me out. Is there any way to recover phone storage data???
Can anyone explain my current situation...???
vinay28761 said:
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
...
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but
...
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
...
Can anyone explain my current situation...???
Click to expand...
Click to collapse
First: this thread is marked as solved since april. Chances are very low for a reaction (but at least I did)
Second: Make a new one in Q&A
Third: What do you mean with "Took the TB"? Especially when you flash a new Stock Rom after
Fourth: Did you put the tar-file under "Phone"? Should be "PDA".
Fifth: Read a lot in the stickies here - good start for handling Odin is Dr. Ketan's thread
Sixth: your current situation might result from not reading enough. I hope you didn't brick your device and can restore a running Rom with the instructions from the stickies. Good Luck
how exactly did you reach this situation?
Did you resolve this ?
vinay28761 said:
hello,
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but operation failed showing:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> factoryfs.img
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010>
<ID:0/010> Receive Response form LOKE
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried many times but showing the same error everytime.
I am not able to go into the recovery mode......although i can go into the download mode.
When i reboot it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." There is no samsung logo or GT-N7000 logo when you reboot your phone. You only see this warning.
I have some imp data on my internal memory(Phone storage). I have to save that data. Please please please help me out. Is there any way to recover phone storage data???
Can anyone explain my current situation...???
Click to expand...
Click to collapse
@vinay28761
I have your exact problem. Phone came to me with problem of hanging on Samsung N7000 Logo.
After flash everything, it shows error, exactly like yours.
Were you able to fix it? How ?
dannyogolo said:
@vinay28761
I have your exact problem. Phone came to me with problem of hanging on Samsung N7000 Logo.
After flash everything, it shows error, exactly like yours.
Were you able to fix it? How ?
Click to expand...
Click to collapse
Yes, i resolved it. I just followed dr. ketan's guide to flash through ODIN properly and exactly as described. I would request you to do the same.
Hope it solves your error too. If not, please post your screenshots.
could you jst give me details about dis nand write fail problem?i m having same problem in my gt n7000
Does anyone know where i can download PIT file for samsung gts6802 and a bootloader?
It woulb be very helpful. Thank You
help please i got this unit stuck on upgrade screen
history:
the unit had too many pattern attempts then i tried hard resetting it by using the combination keys, but then after accessing the menu for hard resetting, when i press vol - to choose the reformat or factory reset (somthing like that i forgot) then it displayed forced uplaod mode by pressing keys. then i removed the battery and turned it on with just the power button, but it entered the hard reset menu again. i thought the volume keys were shorted so i removed them, but even if i have removed all the keys still stuck on the hard reset screen. then i tried connecting it to kies and one time it was detected, but it turned off then i showed that screen. it can be detected by my computer but not by kies or odin or any other flashers i have here.
up for this post can anybody help me pls?
Stuck on Upgrade Logo
chunkiebone said:
up for this post can anybody help me pls?
Click to expand...
Click to collapse
Mine got this problem too, any help guys?? thanks in advance
asukaragnaboy said:
Mine got this problem too, any help guys?? thanks in advance
Click to expand...
Click to collapse
if you are getting an "UPGRADE" screen, it means you have failed/unsusessfull flash and you are still in download mode, so just connect to fresh/reboot Odin and flash again recovery or flash WF07 ROM to recover
xsenman said:
if you are getting an "UPGRADE" screen, it means you have failed/unsusessfull flash and you are still in download mode, so just connect to fresh/reboot Odin and flash again recovery or flash WF07 ROM to recover
Click to expand...
Click to collapse
nope. my phone fully flashes whenever i flash it. odin always says completed. problem is that when the phone restarts, it's working ok until i remove it from cable. when i unplug it to cable, after a few minutes it turns off and goes to the never ending loop again (samsung logo, the first one with circle) or if i unplug it and charge it on a wall charger it turns off and guess what, it returns to the same loop again.
EDIT:
odin logs for reference
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL4_I9300H3GELL1_I9300NELK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> recovery.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/007> Added!!
Hay guys.Sorry to open new thread,but I really need help.I got galaxy note (N7000) and the problem is that is stuck ob samsung boot logo.I have tried every single solution I could find on the web,but with no luck.I dont even know on what rom is ATM because i got it in this condition.All I know is that it was bought in Austria
PLEASE HELP!!!!
Have you tried booting it into recovery mode or download mode?
Recovery: Press Home + Volume Up + Power On. Stay pressed until GT-N7000 logo comes up.
Download: Press Home + Volume Down + Power On. Stay pressed until GT-N7000 logo comes up.
Nibb31 said:
Have you tried booting it into recovery mode or download mode?
Recovery: Press Home + Volume Up + Power On. Stay pressed until GT-N7000 logo comes up.
Download: Press Home + Volume Down + Power On. Stay pressed until GT-N7000 logo comes up.
Click to expand...
Click to collapse
i can only get it in download mode.when i try to start recovery mode the phone stops at samsung logo and just hangs there all day
Go to the download mode, flash a stock ROM for your region using PC ODIN and go thru dr.ketan's thread in the original Android development forum. Flash a stock ROM and then flash a kernel like the PhilZ kernel that you'll find in the thread on how to root and this boot loop bug will be out forever.
thanks for your effort Varad,but still not luck.I guess I got a pretty expensive paper weight :crying:
bizzare187 said:
thanks for your effort Varad,but still not luck.I guess I got a pretty expensive paper weight :crying:
Click to expand...
Click to collapse
post the result or screenshot of pc odin or just mention where is it getting stuck while flashing.
flashing goes without problem,but when the phone reboots it stucks on samsung logo
bizzare187 said:
flashing goes without problem,but when the phone reboots it stucks on samsung logo
Click to expand...
Click to collapse
do you get message on pc oding saying success1/failed0?
yes i get that message and then phone reboots.and it stucks
bizzare187 said:
yes i get that message and then phone reboots.and it stucks
Click to expand...
Click to collapse
have you tried flashing again?
treacherous_hawk said:
have you tried flashing again?
Click to expand...
Click to collapse
yes i did.i will do it again now and post odin messages
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLQ3_N7000OXXLP7_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.img
<ID:0/008> NAND Write Start!!
<ID:0/008> hidden.img
<ID:0/008> factoryfs.img
<ID:0/008> zImage
<ID:0/008> modem.bin
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
And yet it is stuck on the boot logo? Well that thing about the paperweight seems to be right now
Varad297 said:
And yet it is stuck on the boot logo? Well that thing about the paperweight seems to be right now
Click to expand...
Click to collapse
friend told me to try a full wipe rom.is it a good idea?if it is,i just wanna know if it is flashable via odin.
Look haven't you wiped data before flashing ROMs? And yes any full wipe ROM with a .tar file is flashable via odin. But a full wipe ROM is of no use if you wipe data and cache before a flash, it's the same.
Varad297 said:
Look haven't you wiped data before flashing ROMs? And yes any full wipe ROM with a .tar file is flashable via odin. But a full wipe ROM is of no use if you wipe data and cache before a flash, it's the same.
Click to expand...
Click to collapse
no i havent wiped anything.i got the phone in this condition.i can only enter download mode.when i try to enter recovery mode the phone stucks at logo.same thing if i just try to turn it on.
Yes try a full wipe ROM then, no harm in trying...
tried the wipe ROM.still no luck
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXKL8_CL840182_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXKL8_REV_05_CL1089796.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXAKL8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> Sbl.bin
<ID:0/008> param.lfs
<ID:0/008> zImage
<ID:0/008> factoryfs.img
<ID:0/008> data.img
<ID:0/008> cache.img
<ID:0/008> hidden.img
<ID:0/008> modem.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response form LOKE
<ID:0/008> cache.img
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
still under warranty?
Get to the service center...that's the only way i see out of this...
treacherous_hawk said:
still under warranty?
Click to expand...
Click to collapse
no,warranty is expired
Varad297 said:
Get to the service center...that's the only way i see out of this...
Click to expand...
Click to collapse
thanks a lot everybody for trying
Hi together, before i try to use a "last exit" by buying me an "Unbrick - JTAG", i thought if one could may help me, it will be found here or nowhere.
I started with a new S3 Mini (Telekom Branding Android 4.1.2 Germany). Using the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, (mskip) i rooted it and flashed also the CMW Recovery. Within the CMW Recovery i made a Backup before i flashed a CUSTOM-ROM ( "enox reVenge one" ROM ).
Flashing went trough without Errors, afterwards i did a "wipe factory reset", a "wipe cache" and a "wipe dalvik cache". Then after a reboot the "disaster" was there with a permanent bootloop (Samsung starting Screen with model, etc.) and i couldn´t get into Recovery mode anymore. As i found out, the Download mode still worked and i could still flash using ODIN. So i studied some articles here and i followed procedures to re install a common Stock-Rom together with a PIT file for the I8190N (! found also her specific for the "N" option). The flashes went trough without errors, but unfortunately without positive effects to come over the bootloop. I read some articles about ADB, i downloaded the Android SDK, and tried to use some shell commands to get into recovery mode with no success, because i got allways the message "device not found". Within the SDK package also the USB Drivers were installed and when i connected the S3 via USB, Drivers were installed under "WXP" without any errors (I use WXP instead of W7 or W8 which i have also available). At a certain time i recognised that the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, give me an ADB environment just on a selectable menuelevel, which can be used more comfortable as the native ADB environment. I recognised that i could use there just a function like "reboot in recovery mode".
The problem just ist, that of coarse also there the "device not found" problem is just the same (same Environment on Laptop). I just have any idee anymore what to do, and either i can solve the problem finaly here with your support (maybe something else could be tried out using ODIN flashing), or i take the last exit "and buy me the mentioned Unbrick - JTAG.
Instead of this i would more like to buy you a beer or to donate for a beer for someone of you.
We will see what happens, anyway my best wishes to you.
reflash the firmware (make sure that it is the right firmware for your variant) with pit file.
if you stuck in bootloop, flash param file with odin http://forum.xda-developers.com/attachment.php?attachmentid=1937012&d=1367738404 (it works also for N)
Unfortunately no success
Did it as recommended with no success, files used within flashing:
First ODIN Flash,
I8190NXXAMD3_I8190NOXAAMD3_DBT.zip
i8190N_goldenxx.pit
Second ODIN Flash,
PARAM_I8190.tar.md5
The loop still remains. here the logs (copied in one file) from ODIN (two separate runs):
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190XXAMB3_I8190DTMAMB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.img
<ID:0/015> NAND Write Start!!
<ID:0/015> STE_boot1.img
<ID:0/015> STE_boot2.img
<ID:0/015> modem.bin
<ID:0/015> system.img
<ID:0/015> cache.img
<ID:0/015> hidden.img
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
New Start of ODIN as Admin
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PARAM_I8190.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> param.lfs
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
K.r. Heinz :crying:
samersh72 said:
reflash the firmware (make sure that it is the right firmware for your variant) with pit file.
if you stuck in bootloop, flash param file with odin http://forum.xda-developers.com/attachment.php?attachmentid=1937012&d=1367738404 (it works also for N)
Click to expand...
Click to collapse
htruempler said:
Did it as recommended with no success, files used within flashing:
First ODIN Flash,
I8190NXXAMD3_I8190NOXAAMD3_DBT.zip
i8190N_goldenxx.pit
Second ODIN Flash,
PARAM_I8190.tar.md5
The loop still remains. here the logs (copied in one file) from ODIN (two separate runs):
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190XXAMB3_I8190DTMAMB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.img
<ID:0/015> NAND Write Start!!
<ID:0/015> STE_boot1.img
<ID:0/015> STE_boot2.img
<ID:0/015> modem.bin
<ID:0/015> system.img
<ID:0/015> cache.img
<ID:0/015> hidden.img
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
New Start of ODIN as Admin
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PARAM_I8190.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> param.lfs
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
K.r. Heinz :crying:
Click to expand...
Click to collapse
Try reflashing param as .tar not .tar.md5
serophia said:
Try reflashing param as .tar not .tar.md5
Click to expand...
Click to collapse
md5 is valid so I don't think there would be any difference except from removed security from flashing bad files.
Try to first flash stock recovery then firmware.
Stock recovery
Still no change in Bootloop
Hi, thanks to all of you for your participation and supporting me :good:
Well, did it as recommended, unfortunately still no success.
Three flash runs, first, stock recovery, then Firmware. checking if successfull, bad result. Third flash again param, bad result.
Still bootloop, no opportunity to launch recovery.
First Flash Stock Recovery Log of ODIN:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190_stock-recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> recovery.img
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
<ID:0/015> Removed!!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Second Flash Firmware
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190XXAMB3_I8190DTMAMB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.img
<ID:0/015> NAND Write Start!!
<ID:0/015> STE_boot1.img
<ID:0/015> STE_boot2.img
<ID:0/015> modem.bin
<ID:0/015> system.img
<ID:0/015> cache.img
<ID:0/015> hidden.img
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
<ID:0/015> Removed!!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Third Flash PARAM
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PARAM_I8190.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Added!!
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> param.lfs
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
K.r. Heinz :crying::crying:
htruempler said:
Hi, thanks to all of you for your participation and supporting me :good:
Well, did it as recommended, unfortunately still no success.
Three flash runs, first, stock recovery, then Firmware. checking if successfull, bad result. Third flash again param, bad result.
Still bootloop, no opportunity to launch recovery.
K.r. Heinz :crying::crying:
Click to expand...
Click to collapse
if you can not boot into recovery to wipe, flash this .tar.md5 as pda (the same for I8190 and I8190N) http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346
No success, Bootloop remains
Many thanks, but no success. I have the impression it might have to do with the bootloader itself. K.r. Heinz :crying:
samersh72 said:
if you can not boot into recovery to wipe, flash this .tar.md5 as pda (the same for I8190 and I8190N) http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346
Click to expand...
Click to collapse
Did you try the 3 button combo for recovery: http://forum.xda-developers.com/showthread.php?t=2157105?
Start in recovery and do a factory reset after you flash a stock rom in Odin.
Still no success
Hi, i tried the I8190.tar.md5, unfortunately without success, because i´m not sure about the effect and the battery load, i decided not to try as well the I8190 серв. укр.rar package (might be i don´t have enough battery load and within the permanent bootloop, loading doesn´t seem to work). I think i will stop at that stage with this huge amount of attemps and buy me a jtag unbrick as mentioned when i started this thread. In case somebody would know how charge the battery in this stage, i would give the I8190 серв. укр.rar a final try out. Anyway i would like to say thanks to all of you because of your participation and support to me. Great community here!!!
deconectat said:
Did you try the 3 button combo for recovery: http://forum.xda-developers.com/showthread.php?t=2157105?
Start in recovery and do a factory reset after you flash a stock rom in Odin.
Click to expand...
Click to collapse
Doesn't the phone charge when it's off? Try to unplug the battery, plug it back in and connect the charger.
Same here! I have TWRP recovery and it shows TeamWin splash screen for 1 second and shuts off!
KoolKid98189 said:
Same here! I have TWRP recovery and it shows TeamWin splash screen for 1 second and shuts off!
Click to expand...
Click to collapse
go to download mode and flash param.tar (search in forum).
if this isn´t successful, download This ROM (LaFleur) and follow This Instructions.
After that you can flash every ROM you like
I flashed a wrong script one time - nothing worked. So i did it like i described and everything worked
JackoMJ said:
go to download mode and flash param.tar (search in forum).
if this isn´t successful, download This ROM (LaFleur) and follow This Instructions.
After that you can flash every ROM you like
I flashed a wrong script one time - nothing worked. So i did it like i described and everything worked
Click to expand...
Click to collapse
What's so special about the LaFleur ROM though?
I have the same problem and no way to make get it out of bootloop
htruempler said:
Hi together, before i try to use a "last exit" by buying me an "Unbrick - JTAG", i thought if one could may help me, it will be found here or nowhere.
I started with a new S3 Mini (Telekom Branding Android 4.1.2 Germany). Using the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, (mskip) i rooted it and flashed also the CMW Recovery. Within the CMW Recovery i made a Backup before i flashed a CUSTOM-ROM ( "enox reVenge one" ROM ).
Flashing went trough without Errors, afterwards i did a "wipe factory reset", a "wipe cache" and a "wipe dalvik cache". Then after a reboot the "disaster" was there with a permanent bootloop (Samsung starting Screen with model, etc.) and i couldn´t get into Recovery mode anymore. As i found out, the Download mode still worked and i could still flash using ODIN. So i studied some articles here and i followed procedures to re install a common Stock-Rom together with a PIT file for the I8190N (! found also her specific for the "N" option). The flashes went trough without errors, but unfortunately without positive effects to come over the bootloop. I read some articles about ADB, i downloaded the Android SDK, and tried to use some shell commands to get into recovery mode with no success, because i got allways the message "device not found". Within the SDK package also the USB Drivers were installed and when i connected the S3 via USB, Drivers were installed under "WXP" without any errors (I use WXP instead of W7 or W8 which i have also available). At a certain time i recognised that the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, give me an ADB environment just on a selectable menuelevel, which can be used more comfortable as the native ADB environment. I recognised that i could use there just a function like "reboot in recovery mode".
The problem just ist, that of coarse also there the "device not found" problem is just the same (same Environment on Laptop). I just have any idee anymore what to do, and either i can solve the problem finaly here with your support (maybe something else could be tried out using ODIN flashing), or i take the last exit "and buy me the mentioned Unbrick - JTAG.
Instead of this i would more like to buy you a beer or to donate for a beer for someone of you.
We will see what happens, anyway my best wishes to you.
Click to expand...
Click to collapse
Seems like a soft brick, nothing to worry about as of yet. Try using Unified Android Toolkit to flash stock firmware following the on screen instructions.
uvedovle said:
I have the same problem and no way to make get it out of bootloop
Click to expand...
Click to collapse
Discharge the battery and return it to the seller and get a replacement. This is last resort and that's what I did and got a free replacement in sacrifice of my data.
samersh72 said:
if you can not boot into recovery to wipe, flash this .tar.md5 as pda (the same for I8190 and I8190N) http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346
Click to expand...
Click to collapse
Thanks for the WIPE_I8190.zip
I was stuck in bootloop, and after i flashed this file in Odin as PDA, my phone works. Thanks ! :good:
resolve
hi mate got one for u to try worked on mine as had same problem dowload odim 3.07 then registure on samfirmware website then look for the uk o2 stock firmware list hope this helps and u get phone back on
let me nw how u get on
htruempler said:
Hi together, before i try to use a "last exit" by buying me an "Unbrick - JTAG", i thought if one could may help me, it will be found here or nowhere.
I started with a new S3 Mini (Telekom Branding Android 4.1.2 Germany). Using the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, (mskip) i rooted it and flashed also the CMW Recovery. Within the CMW Recovery i made a Backup before i flashed a CUSTOM-ROM ( "enox reVenge one" ROM ).
Flashing went trough without Errors, afterwards i did a "wipe factory reset", a "wipe cache" and a "wipe dalvik cache". Then after a reboot the "disaster" was there with a permanent bootloop (Samsung starting Screen with model, etc.) and i couldn´t get into Recovery mode anymore. As i found out, the Download mode still worked and i could still flash using ODIN. So i studied some articles here and i followed procedures to re install a common Stock-Rom together with a PIT file for the I8190N (! found also her specific for the "N" option). The flashes went trough without errors, but unfortunately without positive effects to come over the bootloop. I read some articles about ADB, i downloaded the Android SDK, and tried to use some shell commands to get into recovery mode with no success, because i got allways the message "device not found". Within the SDK package also the USB Drivers were installed and when i connected the S3 via USB, Drivers were installed under "WXP" without any errors (I use WXP instead of W7 or W8 which i have also available). At a certain time i recognised that the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, give me an ADB environment just on a selectable menuelevel, which can be used more comfortable as the native ADB environment. I recognised that i could use there just a function like "reboot in recovery mode".
The problem just ist, that of coarse also there the "device not found" problem is just the same (same Environment on Laptop). I just have any idee anymore what to do, and either i can solve the problem finaly here with your support (maybe something else could be tried out using ODIN flashing), or i take the last exit "and buy me the mentioned Unbrick - JTAG.
Instead of this i would more like to buy you a beer or to donate for a beer for someone of you.
We will see what happens, anyway my best wishes to you.
Click to expand...
Click to collapse
Hello everybody. Yesterday Im trying to upgrade to my s3 mini to kitkat 4.4.4. but then my phone is on bootloop. And then I try to boot to recovery mode and wipe dalvik cache. but it still not working, and then I tried to flash again with recovery tar md5. And now after samsung logo appear, its only black screen. Can you help me?
Hi I'm new to XDA. My Note 8 (N950U) won't boot past the Samsung Galaxy Note 8 powered by android screen.
I can access the download mode and have flashed the stock firmware. But as soon as it reboots it gets stuck on the same screen.
Any help regarding this is much appreciated
factory reset.
android-incredible said:
factory reset.
Click to expand...
Click to collapse
I cant enter the recovery to perform a factory reset
RPG-XDA said:
I cant enter the recovery to perform a factory reset
Click to expand...
Click to collapse
Flash all 4 files in Odin instead of using home-csc file use CSC file. This will erase phone. Also make sure your on the latest Odin and using the same bootloader version.
Sent from my SM-N950F using Tapatalk
BluePhnx said:
Flash all 4 files in Odin instead of using home-csc file use CSC file. This will erase phone. Also make sure your on the latest Odin and using the same bootloader version.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
I already tried flashing both the HOME_CSC and CSC separately, but it didn't work. I'm able to successfully flash the firmware, but the phone is still stuck at the powered by android screen.
Do you know what caused the issue in the first place? Was it just on stock and suddenly won't boot? Were you using Samfail or anything like that? Just trying to narrow down the issue, because flashing stock should usually work.
sefrcoko said:
Do you know what caused the issue in the first place? Was it just on stock and suddenly won't boot? Were you using Samfail or anything like that? Just trying to narrow down the issue, because flashing stock should usually work.
Click to expand...
Click to collapse
Yes, I was on stock Oreo. Haven't tried rooting it or installing custom recovery. I came across some posts on the S8 forum with the same issue, but the solution mentioned there isn't working for me.
https://forum.xda-developers.com/galaxy-s8/help/galaxy-s8-g950fd-stuck-logo-flash-t3647926
RPG-XDA said:
Yes, I was on stock Oreo. Haven't tried rooting it or installing custom recovery. I came across some posts on the S8 forum with the same issue, but the solution mentioned there isn't working for me.
https://forum.xda-developers.com/galaxy-s8/help/galaxy-s8-g950fd-stuck-logo-flash-t3647926
Click to expand...
Click to collapse
Which Odin version are you using?
sefrcoko said:
Which Odin version are you using?
Click to expand...
Click to collapse
Odin 3 v3.13.1
RPG-XDA said:
Odin 3 v3.13.1
Click to expand...
Click to collapse
Possible to show a screenshot of Odin after the flash? To see the log messages and firmware version being flashed?
sefrcoko said:
Possible to show a screenshot of Odin after the flash? To see the log messages and firmware version being flashed?
Click to expand...
Click to collapse
Firmware version: N950U1UES5CRF6_N950U1OYM5CRF6_ATT
Odin log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 6197 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> bksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> pmic.elf
<ID:0/003> rpm.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> keymaster.mbn
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> sec.dat
<ID:0/003> NON-HLOS.bin
<ID:0/003> storsec.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> dqmdbg.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> adspso.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Still stuck at the same boot screen. Still wondering why the Odin flash is successful, but the phone doesn't seem to even have a recovery to boot into.
RPG-XDA said:
Still stuck at the same boot screen. Still wondering why the Odin flash is successful, but the phone doesn't seem to even have a recovery to boot into.
Click to expand...
Click to collapse
Use USB 2.0,Also try unplugging it mid flash, Then reboot the phone, Does it boot to the screen where it tells you to connect with Smartswitch?
Samsunguser932 said:
Use USB 2.0,Also try unplugging it mid flash, Then reboot the phone, Does it boot to the screen where it tells you to connect with Smartswitch?
Click to expand...
Click to collapse
I tried your suggestion and I now get the screen which tells me to connect to smart switch. But when I run Smart Switch, it says the connected device cannot be recognized and Emergency recovery mode doesn't list the phone
RPG-XDA said:
I tried your suggestion and I now get the screen which tells me to connect to smart switch. But when I run Smart Switch, it says the connected device cannot be recognized and Emergency recovery mode doesn't list the phone
Click to expand...
Click to collapse
Okay, Just use ODIN then to try and restore it from that screen, Maybe that will work, Also try Smartswitch from Download mode, Make sure your drivers are installed.
Samsunguser932 said:
Okay, Just use ODIN then to try and restore it from that screen, Maybe that will work, Also try Smartswitch from Download mode, Make sure your drivers are installed.
Click to expand...
Click to collapse
I have installed all my drivers, but Smartswitch still won't detect my device. After flashing with Odin it goes back to being stuck on the Powered by android screen.
RPG-XDA said:
I have installed all my drivers, but Smartswitch still won't detect my device. After flashing with Odin it goes back to being stuck on the Powered by android screen.
Click to expand...
Click to collapse
When you flash with odin select Nand Erase from your options. then youll be able to boot if you flash WITH the AP,BL,CP and CSC
me2151 said:
When you flash with odin select Nand Erase from your options. then youll be able to boot if you flash WITH the AP,BL,CP and CSC
Click to expand...
Click to collapse
I tried using the Nand Erase option as you suggested, but it didn't change anything. I was just trying various button combinations and suddenly got the grey circle with the lightning bolt, but it wasn't charging. After some time the phone turned off and I haven't been able to get to that screen again. Any idea of what that could be?
Thats just the off mode charging(also known as low power mode)
me2151 said:
Thats just the off mode charging(also known as low power mode)
Click to expand...
Click to collapse
Oh. Didn't know that But even in that mode the phone just shows that symbol, even after I disconnect it from power.
Could this be a issue with the motherboard or is it just software, because I can still get into download mode and flash successfully?