Related
Hi guys,,, just bought myself a X10i to play with,,, figured I,ve flash the thing with a rom from the developers forum,
This is where I came unstuck,,,, cant for the life of me get it into flash mode.
Instructions were as follows
1 With fone OFF. Hold down back button and insert usb cable, green light comes on and hit enter. What bloody enter, on the fone or on your keyboard. I,ve tried both, fone just keeps on booting into the main screen, nothing even resembles a flash mode screen. Tried this untill my thumb nearly bled.
Someone help please.
Read the tuts in the dev forum. P.S. no custom roms yet but there is root.
TrevvyD said:
Hi guys,,, just bought myself a X10i to play with,,, figured I,ve flash the thing with a rom from the developers forum,
This is where I came unstuck,,,, cant for the life of me get it into flash mode.
Instructions were as follows
1 With fone OFF. Hold down back button and insert usb cable, green light comes on and hit enter. What bloody enter, on the fone or on your keyboard. I,ve tried both, fone just keeps on booting into the main screen, nothing even resembles a flash mode screen. Tried this untill my thumb nearly bled.
Someone help please.
Click to expand...
Click to collapse
Try hold down "back button" without battery then insert USB cable and then insert battery.
When it says to hit enter, that is to continue from the screen (on the PC) that says "press any key to continue" when you are doing the steps for rooting. If you don't have that window ready the phone will only stay in flash mode for about 5 seconds and then it will continue to boot. So, just make sure you are ready with the PC before entering flash mode.
Dr_Wolodya said:
Try hold down "back button" without battery then insert USB cable and then insert battery.
Click to expand...
Click to collapse
thanks!!
this really helps!
My phone is also x10i.I have trouble to enter in flash mode.It shows up the green LED but flash tool says it occurs error and plug your phone in flash mode.
What should I do?Help me , plz.
johnmin said:
My phone is also x10i.I have trouble to enter in flash mode.It shows up the green LED but flash tool says it occurs error and plug your phone in flash mode.
What should I do?Help me , plz.
Click to expand...
Click to collapse
check drivers (install SE PC suite and let it atleast detect the phone once in FLASH mode)...
also it might help to disable any antivirus (worked for me)
cannot enter the flash mode
Hi,
I know this post is pretty old, but still I'm struglig the second day now to get into flash mode and still no luck despite trying every method there is on the web.
I've got Xperia X10i mini pro, reinstalled standard ROM with PC companion just to make sure it's nothing with the software or any modifications I made to it.
I'm guiding myself with instruction given here:
wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Mini_Pro:_Full_Update_Guide
in order to get my bootloader unlocked
what I've done so far:
-installed Android SDK incl. SDK Tools, SDK Platform-tools, Google USB driver package. Not installed any API from SDK.
-put android_winusb.inf (18 KB size) in C:\android-sdk-windows\extras\google\usb_driver
-in general- everyting given here: wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK#Windows
command
Code:
adb devices
rerurns
Code:
List of devices attached
43423531315537465737 device
in my opinion meaning it works as it should.
So I turn the phone off, unplug the cable both from computer and the phone, take the abttery out, plug both end of USB cable where these should be, hold the Back button (tried with Volume up too) and put the battery in.
The result is it only goes into flash mode for several seconds (confirmed by SuperOneClisk log) and then goes into charging mode. nothing gets displayed on the screen. Only when PC Companion is on it detects it, than looses it and pops up with a window on how to properly connect the device... :/
So can someone please tell me what I do wrong?
Why it doesn't stay in flash mode?
PS. when I enter *#*#7378423#*#* to access the service menu, after pressing the last * the numbers just disappear and nothing happens...
Pls help
Edit:
I somehow got around that with s1tool and Flashtool. But eventually I could not go along the way given at cyanogenmod.com and unlocked with the help of this: http://forum.xda-developers.com/showthread.php?t=1254225
Hi!
I've just got my gt540 .
I decided to install CM7[swift-droid] but fastboot or recovery was needed, so I downloaded rom with fastbood [.kdz] , installed all drivers and started update with kdz updater .
[phone was 2.1 already]
Installation stopped on 140 [booted to download mode]
I disconnected phone ...
And now it is not able to boot .
I tried VOL- + USB - nothing happen
I tried Hard-reset - same
KDZ Updater cant find my phone,
I can't even hear the "BUMP" sound when I connect the divice via USB .
Simply phone is fully dead .
Is there possiblity to make my gt540 working again ? //no warranty ;/
[HOW-TO] Repair your device if it feels like dead | When you click power button nothing happens (Note that this may or may not work)
Make sure you use USB ports that are in back of youre PC, dont use front ones.
Disable LGE Virtual Modem. In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.
Try to boot your phone into Emergency/Download mode (VOL DOWN + POWER).
If the phone booted into Emergency/Download mode, launch KDZ Updater.
In TYPE dropdown menu, choose EMERGENCY.
Load KDZ(ROM) and flash your phone.
If the phone failed to boot into Emergency/Download mode (VOL DOWN + POWER), launch KDZ Updater.
In TYPE dropdown menu, choose CS_EMERGENCY.
Load KDZ(ROM) and flash your phone.
____________________________________________
THANKS TO fishears FROM XDA!
[HOW-TO] Repair your device if you don't see LG logo, boot animation | Recovery doesn't show up
Download the French v20A and the out.kdz
Take out your battery, SIM and SD card
Plug USB into PC (but not phone yet)
Hold (VOL DOWN) button and plug USB into phone | *Phone goes into Download Mode
Run KDZ Updater
In TYPE dropdown menu, choose CS_Emergency mode
Load French V20A ROM and flash it
When it's finished pull out USB again and hold (VOL DOWN) and reinsert USB to put phone back in Download Mode
Launch KDZ Updater (still in CS_Emergency mode)
Load out.kdz and flash it
You should now have your boot animations back and you can flash whatever ROM you want to use.
taken form the great guide from here
http://forum.xda-developers.com/showpost.php?p=13205397&postcount=26
Thanks but my phone is not able to go into Download mode and KDZ Upadter says "Phone not found" when I use "cs_emergency" .
Any other ideas ?
I think that repairing boot with jtag is inevitable
You have to send it to LG. Basically, they will replace the motherboard
post to delete
@up not so fast others with this prob might see this thread and fix their phone this way
Hmm, as I said warranty has ended .
I found auction where I can repair this for 20USD, probably I will try ... ;/
hmm connect to pc and try to power the phone with Power + Camera (2 clicks) for 30 seconds or more. (no matter if no logo appears)
then try to flash with kdz
I have some problem what to do!?
bs828 said:
@up not so fast others with this prob might see this thread and fix their phone this way
Click to expand...
Click to collapse
Well I just repetead a part of what you posted because I didnt read entirely your post. Doubt that anyone will find that helpful.
EDIT: SOLUTION (Not a fix)
For those who are stuck at "50% saying current account is different from the a/c info of device"
It is due to the database miss-match in their server ,the possible sollution are :
Remember: for MediaTek devices you will have to first flash a China Dev ROM onlu then you can get the unlock successful.
But this is not a recommendation for Qualcomm Devices.
1. Go to i.mi.com and look weather your device shows up in the find device (this is required only to be sure as to your device is connected to their server and they have updated the info on your Device too).
2. Reset your Phone sign in and turn on find device. turn on usb debug and oem unlock connect to pc allow whatever is asked on your phone also check always trust, then open adb folder and open cmd there and type adb devices your phone will ask for authorisation allow it and check always trust.
3. Mail your concern with user ID and also the snapshot of the error as they will ask for it,to your regional service (I am an indian so i had to mail it at [email protected])(just google contact xiaomi) wait for their reply.
You can PM these persons on MIUI forum regarding the 50% stuck issue.
{ EDIT 2:
You may contact these person in MIUI forum:
1) vincent_khoo
2) PatrickXi
( @bravonova gave me these names you may try I haven't cross checked as mailing will most probably solve) }
The last method should Work for everyone as it's a db miss-match which should be fixed after this.
PS: This a solution and not a fix so it will take time.
PPS: Don't blame me for all the trouble Blame Xiaomi.
ilvmyname said:
Ok, so I have been trying to move to miui 8 global beta version now for a long time and haven't succeeded, the updater app says could not verify update package.
I have a pretty good net connection so that's not an issue.
Also If I try download latest rom it says "Can't download update, wait a minute or two" and this it has been saying for about a week now (ironic).
So, I requested for unlocking the bootloader got the confirmation messages after 3 days tried to unlock now stuck at 50% saying "account is different from the account in the phone info"
I don't want to use the fast boot edl method of flashing rom as my lappy keeps getting sudden shutdown, so I don't want it to shutdown in between and get hard bricked.
I have tried MiPc suit but since it cannot do a backup(again app bug) so cannot flash through it.
I have looked in to the mi cloud and my phone does gets located.(possible solution given for unlock bootloader but even that didn't work).
Can anyone please help me on this or will I have to be on this ****ty unrooted Rom forever.
Currently on miui 7.5.3.0 global stable rom.
Any suggestions will be appreciated ty
Click to expand...
Click to collapse
I unlocked it just today!make sure all drivers are installed..boot into fastboot mode :- power off then hold vol down + power button.w8 for the drivers to get installed
Now boot into recovery mode :- turn off device and hold volume up + power button.w8 for the drivers to get installed.
I was stuck at the same 50% error..one of d xda member told me to boot into recovery mode and let the drivers get installed and taddaa...bootloader unlocked
Make sure u r logged in to the same account in ur phone u r using to unlock the bootloader
I fixed this by updating to latest version in miui app in fastboot mode.
Same problem for me. I tried using the MIUI PC Suite, it tells me my phone isnt up to date even though it is. Recovery mode drivers fail. Requested unlock over 2 weeks ago and got the SMS 9 day ago... still stuck at 50% error. Its driving me nuts.
Warrimonk said:
Same problem for me. I tried using the MIUI PC Suite, it tells me my phone isnt up to date even though it is. Recovery mode drivers fail. Requested unlock over 2 weeks ago and got the SMS 9 day ago... still stuck at 50% error. Its driving me nuts.
Click to expand...
Click to collapse
i today unlocked my bootloader...try doing this go into recovery mode by pressing power+volumeup button. You will see a picture telling you to connect ur phone to pc using usb cable..connect your phone to your pc now w8 and let the drivers get installed and try again..i did dis and unlocked it today before that i was getting the same error even today got the same error before doing this.
hitesh1792 said:
i today unlocked my bootloader...try doing this go into recovery mode by pressing power+volumeup button. You will see a picture telling you to connect ur phone to pc using usb cable..connect your phone to your pc now w8 and let the drivers get installed and try again..i did dis and unlocked it today before that i was getting the same error even today got the same error before doing this.
Click to expand...
Click to collapse
First of all thanks for the reply sir but
I tried entering to recovery mode and then connect to pc but nothing happens, I mean it does not show connected even after say 5 minutes.
Although when trying to enter into the fastboot mode and then connecting to pc the drivers do get install and it shows connected and stucks at 50%
I do have adb drivers RN3 USB drivers installed on my pc
But all things in vain.
Garyj881 said:
I fixed this by updating to latest version in miui app in fastboot mode.
Click to expand...
Click to collapse
I am sorry sir but I didn't get you, you updated to latest version of miui through the updater app right? And then entered to fastboot mode to unlock right?
My updater app also doesn't work It says cannot verify update package and so I am stuck like from all corners.
ilvmyname said:
First of all thanks for the reply sir but
I tried entering to recovery mode and then connect to pc but nothing happens, I mean it does not show connected even after say 5 minutes.
Although when trying to enter into the fastboot mode and then connecting to pc the drivers do get install and it shows connected and stucks at 50%
I do have adb drivers RN3 USB drivers installed on my pc
But all things in vain.
Click to expand...
Click to collapse
Are you able to see this pic on your device when you enter recovery mode??
hitesh1792 said:
Are you able to see this pic on your device when you enter recovery mode??
Click to expand...
Click to collapse
Yes
ilvmyname said:
Yes
Click to expand...
Click to collapse
connect your device to your pc and let the drivers get installed...and if u are using a desktop pc do not use the usb port which is at the front of the cpu..use the one which are at the back of the cpu...the image i am attaching shows which drivers get installed.
after drivers get installed remove usb cable and again boot into fastboot mode (power + volume down ) and try again to unlock bootloader
hitesh1792 said:
connect your device to your pc and let the drivers get installed...and if u are using a desktop pc do not use the usb port which is at the front of the cpu..use the one which are at the back of the cpu...the image i am attaching shows which drivers get installed.
after drivers get installed remove usb cable and again boot into fastboot mode (power + volume down ) and try again to unlock bootloader
Click to expand...
Click to collapse
Okay, so i am missing drivers i guess.
Have you pre installed any drivers if so can you provide me a link?
as when i connect into recovery mode only the bootloader interface driver get install and nothing else and hence it still doesn't show connected in the recovery mode.
ilvmyname said:
Okay, so i am missing drivers i guess.
Have you pre installed any drivers if so can you provide me a link?
as when i connect into recovery mode only the bootloader interface driver get install and nothing else and hence it still doesn't show connected in the recovery mode.
Click to expand...
Click to collapse
strange!bootloader interface driver gets installed when connected in fastboot mode..uninstall that driver connect your phone in recovery mode and see if dese drivers get installled..nope i do not have any link because as soon as i connected my phone into recovery mode the drivers automatically got installed!
ps :- i was able to unlock bootloader after flashing kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global_f5889c1549
i too have the same problem !! if you got the solution please tell me !!
T/[email protected]$ said:
i too have the same problem !! if you got the solution please tell me !!
Click to expand...
Click to collapse
i was able to unlock the bootloader after flashing kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549...
i was not able to unlock it before i connected my phone into recovery mode and installed the drivers on my pc..as soon i did it the bootloader got unlocked .before that i was getting the same error even after flashing the V7.3.7.0.LHOMIDD firmware
hitesh1792 said:
i was able to unlock the bootloader after flashing kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549...
i was not able to unlock it before i connected my phone into recovery mode and installed the drivers on my pc..as soon i did it the bootloader got unlocked .before that i was getting the same error even after flashing the V7.3.7.0.LHOMIDD firmware
Click to expand...
Click to collapse
how to flash kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549.?
when i connect my device in recovery mode nothing happens
For Kenzo / SD / Snapdragon only.
1. Install Mi PC Suite, plug your phone in and install the app on the phone when it prompts (then close mi pc suite) - this provides all the drivers needed for the next step
http://en.miui.com/thread-92720-1-1.html < Mi PC Suite
2. reboot the phone to recovery mode ( Vol UP + Power ), let drivers install on pc - wait, then reboot again to fastboot mode (VOL Down + Power) let drivers install on pc - wait - it might take a few minutes to install the drivers don't unplug the phone during this time.
3. download and install the unlock tool - log into your account, after it checks you have permission press unlock
http://en.miui.com/unlock/ < unlock tool
----------------------------
(if it still fails proceed to next step)
4. use xiao mi flash beta and install the latest kenzo global fast boot image (I have heard some people needed to use the Chinese dev firmware- the global stable worked for me though), use the clean all option selected at the bottom of mi flash. (this will erase ALL data on the phone)- backup before doing this.
http://en.miui.com/thread-281979-1-1.html <- xiao mi flash beta
5. let phone boot up first time, log into the mi account on the phone with your email / password, if your phone number doesn't work then select option to log in with email / password.
6. reboot to fastboot again and press unlock it should proceed now
Do at own risk I am not responsible for bricked devices.
T/[email protected]$ said:
how to flash kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549.?
when i connect my device in recovery mode nothing happens
Click to expand...
Click to collapse
it must install the drivers...please do check out the steps mentioned above by the xda member "otyj" he helped me to unlock my bootloader
I had the same problem and believe me I did everything possible as you are also advised in this forum.
But it had nothing to do with this.
Just wait and watch.. try everyday once and I think you will get in 7-10 more days.
I was also frustated at that time but now I can unlock everysingle time I want when it gets locked.
otyg said:
For Kenzo / SD / Snapdragon only.
1. Install Mi PC Suite, plug your phone in and install the app on the phone when it prompts (then close mi pc suite) - this provides all the drivers needed for the next step
http://en.miui.com/thread-92720-1-1.html < Mi PC Suite
2. reboot the phone to recovery mode ( Vol UP + Power ), let drivers install on pc - wait, then reboot again to fastboot mode (VOL Down + Power) let drivers install on pc - wait - it might take a few minutes to install the drivers don't unplug the phone during this time.
3. download and install the unlock tool - log into your account, after it checks you have permission press unlock
http://en.miui.com/unlock/ < unlock tool
----------------------------
(if it still fails proceed to next step)
4. use xiao mi flash beta and install the latest kenzo global fast boot image (I have heard some people needed to use the Chinese dev firmware- the global stable worked for me though), use the clean all option selected at the bottom of mi flash. (this will erase ALL data on the phone)- backup before doing this.
http://en.miui.com/thread-281979-1-1.html <- xiao mi flash beta
5. let phone boot up first time, log into the mi account on the phone with your email / password, if your phone number doesn't work then select option to log in with email / password.
6. reboot to fastboot again and press unlock it should proceed now
Do at own risk I am not responsible for bricked devices.
Click to expand...
Click to collapse
where can i find fastboot images ?
and when i plugin in recovery mode nothing happens !!
and your were telling that app will be installed in phone when we connect wiith mi pc suit, can you clearly explain it ?
otyg said:
For Kenzo / SD / Snapdragon only.
1. Install Mi PC Suite, plug your phone in and install the app on the phone when it prompts (then close mi pc suite) - this provides all the drivers needed for the next step
http://en.miui.com/thread-92720-1-1.html < Mi PC Suite
2. reboot the phone to recovery mode ( Vol UP + Power ), let drivers install on pc - wait, then reboot again to fastboot mode (VOL Down + Power) let drivers install on pc - wait - it might take a few minutes to install the drivers don't unplug the phone during this time.
3. download and install the unlock tool - log into your account, after it checks you have permission press unlock
http://en.miui.com/unlock/ < unlock tool
----------------------------
(if it still fails proceed to next step)
4. use xiao mi flash beta and install the latest kenzo global fast boot image (I have heard some people needed to use the Chinese dev firmware- the global stable worked for me though), use the clean all option selected at the bottom of mi flash. (this will erase ALL data on the phone)- backup before doing this.
http://en.miui.com/thread-281979-1-1.html <- xiao mi flash beta
5. let phone boot up first time, log into the mi account on the phone with your email / password, if your phone number doesn't work then select option to log in with email / password.
6. reboot to fastboot again and press unlock it should proceed now
Do at own risk I am not responsible for bricked devices.
Click to expand...
Click to collapse
Okay I will try flashing a rom through MiFlash toll b'coz the above methods didn't work and will quote if that's how it gets fixed
I have meizu m2 note. Its now bricked. I was using sp flash tool to unlock the bootloader and install twrp recovery.
i was following the guide giving on youtube. I can't attach an outside link here.
So i did everything this guide said, but on the last step when i switched off my phone and connected to the usb port. The sp flash tool stopped working i waited for 5-10 mins. Finally it crashed. Now when i try to connect my phone it says usb device not recognised (the last device you connected to this computer malfunctioned). I cannot start my phone. I tried pressing the power button for 10 secs, tried pressing volume + with power button, nothing happens.
Anybody have any idea how to solve this.
Go to download old version Flyme os 4+ any but original rom you have must install,
And dow load any latest sp tool,
And also downlaod latest all mtk devices drivers,
If you have system knoledge you can install all of these pc softwares,
Test it once again your phone connecting to computer,
Just detected only nothing. Can do that its just detected your will be alive soon but its very easy if you know a little bit mobile knowledge,
Lets go to process
Step 1 check best and good branded usb connecting cable, test to connect usb cable to your phone,
Step 2 extract Flyme stock rom, and extract mtk sp tool,
Step 3 open sp tool showing error there is no any scatter. Or download file dont worry, da file availble at sptools folder you can go and select, and scatter. File availble at flyme stock rom folder lets check it then select firmware all formate and install that you have to select that option, then you select download and now connect your phone just leave ituntill done then your phone is will alive feel happy like me if you need any more information any other problem connect. To. Me
Can you speak more clearly?I don't understand.Because my English is not very good.
zzx3731 said:
Can you speak more clearly?I don't understand.Because my English is not very good.
Click to expand...
Click to collapse
What problem with your phone?
Hi ! I have the same problem right now, when I plug it, it says device not recognised, what could I do now ?
Thank you very much，This is my mobile phone. It's done.Thank you for your kindness.
：○
Hagadou said:
What problem with your phone?
Click to expand...
Click to collapse
I been able to install LineageOS, I fixed it by pressing home and menu button, it disconnect and reconnect and i been able to Re-flash it with the recovery and when i tried to install Lineage, my error was gone (error 7)
Hi all !
I have a Samsung A8 (model SM-A800F) which was working great. I ran Kingo Root to try to install Youtube ad free. The next time I restarted it, it didn't load, and restarted in an endless loop to where "Samsung" logo appears (then restarted again). I booted into System Recovery and chose to reset to factory, but it didn't help. Then I tried flash it using Odin in Download mode. I installed the Windows drivers, downloaded the 6.0.1 firmware for Vietnam (where it was purchased), loaded the file into the AP field, and once verified clicked Start. The progress was frozen when reaching mid-way every time I tried, until it said "an error occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software"...
I downloaded Smart Switch and installed in Windows, but the drivers were not able to install correctly, and failed on the component referring to the ID or something... while Modem driver was installed correctly and the phone appeared in Device Manager. Smart Switch didn't recognize my phone and said "unsupported device".
Now I cannot get the phone stay constantly ON, and the screen shuts down and loads in an endless loop, to the "Error occured" screen... When trying to boot to the ODIN Download page, it loads, I press UP for Continue, and then it again shuts down and loads to "Error Occured".
I tried to charge over night but it didn't help. It does the same thing when the phone is connected to the charger...
However it seems that by IMEI it is sill under warranty. I'm not sure if I voided it :/
Here's what the Download mode page says:
ODIN MODE
PRODUCT NAME: SM-A800F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 0
AP_SWREV: 1
Would appreciate any help, this phone is almost new but now it's dead :/
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Paradoxxx said:
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Click to expand...
Click to collapse
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
wurlitzer99 said:
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
Click to expand...
Click to collapse
No worries, your phone is not dead.
Try to find a firmware that correspond to the one you got :
http://updato.com/firmware-archive-select-model?exact=1&q=SM-A800F
and use ODIN : http://dl.sammobile.com/Odin3-v3.12.7.zip
You should be good to go.
EDIT : Also for that error occurred thing, try to be faster than it by starting odin flash before it appears.
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
wurlitzer99 said:
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
Click to expand...
Click to collapse
Could you take a picture of that error ? I've never heard/seen such thing
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
wurlitzer99 said:
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
Click to expand...
Click to collapse
Hmmm, the thing is, the battery charging process is actually held on some kind of "mini-boot" OS on Samsung I believe, where the phone boots into a certain state, with that said mini-os to display the battery charging info and this kind of things.
My guess is that you *might* have, or more likely your phone did corrupt the flash at some point for x or y reason.
What I'd do is :
Let the phone on a charger a whole night doing its bootlooping thing. And see from there if the battery would charge.
I'd try another computer with Odin just to be sure something is not triggering the reboot process at some point.
And if all the above fails, you still have the warranty, so beside time, you would not be losing any money..
I'm going to write a long post. But I believe it will help a lot of people having a similar problem.
Long story short - problem solved! but it took much of my nerves (and time).
I'll start with the "warranty". The so-called Samsung "warranty" which basically worths nothing!
Calling Samsung international service center, they "informed" me that I must contact Samsung Vietnam, where I bought the device, although I am not there anymore... Needless to say the local dealer in my country refused to take care of this situation, saying Samsung's warranty is regional based, rather than international... which means, only Samsung in the original country where the device was sold in, are responsible for the warranty (and therefore repair!). I had a chat with a Samsung Vietnam representative, who just kept saying "I'm sorry", and refused to let me sent the device out to them for repair! asking me to "bring it to them", although I noted him a few times that I bought it as a tourist and I am not in Vietnam anymore.... Thank you Samsung !! From now on every traveler in the world will know they basically have NO WARRANTY if they buy any Samsung device in a "foreign" country while traveling abroad!
Now for the solution:
I started by letting the device staying connected to the charger overnight, which didn't help. With the OS now installed, I realize that the battery was NOT CHARGED ! it was completely drained, although connected to a charger for long hours... So, know from now on that if your boot data is corrupted, it may cause the device NOT TO CHARGE THE BATTERY at all. Luckily, my desktop PC could use the device while connected to it although the battery was empty, until the problem was sorted out. I did get a crash on my MAC tough (Log said it was USB related), while using Smart Switch, so one option is that it could not supply enough power to the device to keep it keep working at all, or working correctly... So my suggestion is to use a desktop Windows PC in this case, which can potentially provide more power to a device with 0% battery power.
After scratching my head, and considering removing the front panel for replacing the battery (a very risky procedure) I decided to keep on investigating....
I followed a youtube video who suggests that you should install Smart Switch on a PC, choose "reinstall driver" from the menu, restart the PC, then use Emergency Recovery and Initialization, enter the phone model number in the search box (as appearing on the back of the device) , and once it recognizes the model, also to enter its serial number. Here's the video:
https://www.youtube.com/watch?v=1yXQUFrEWg4
This basically brings up a popup message saying Smart Switch detects a compatible firmware for this device, and is about to download and install it. It then asks the user to do the Power+Vol Up+Home push combination trick + pushing UP once the page is loaded in order to "Continue" and bring up the ODIN Download screen, which worked for me if did that as soon as the device shuts down (in the middle of the bootloop). As I couldn't make it load at all with no charger connected, I had it connected to the charger, and once I saw the Smart Switch message asking to do the push combination, I quickly connected it to the computer using another cable which was already connected to the PC USB port on its other end.
Somehow, I could at last make Smart Switch finally start downloading the firmware from the web, and the device again disconnected (bootlooped), but luckily Smart Switch didn't care about it disconnecting, and kept on downloading the firmware. At about 85% of the progress bar state, I could find the downloaded firmware on the temp folders, which are described in this thread:
http://forum.gsmhosting.com/vbb/f777/samsung-firmware-download-belongs-his-serial-number-2038404/
I had to make sure it wasn't still downloading, and watched the "last modified" state of the file to make sure they are not being downloaded anymore. CAUTION: although the AP was not downloading anymore, I know it was probably not good as ODIN couldn't verify it when I tested it. USE ONLY SMART SWITCH !
I quickly copied the folder to which the app extracted the BL and AP files it downloaded, and finally had an officialy bootloader (BL) image, which I could use in ODIN in order to reupload a correct, "official" bootloader to the device....
I hoped the device won't bootloop in the middle, but luckily ODIN was fast enough to send the image successfully, with a "PASSED" status, and the device booted with a nice "Samsung" logo directly to a System Recovery page!
What I exactly did, was loading ODIN, then loading ONLY the BL file into the BL field in ODIN, having it verifying it, and once verified I connected the device, and as soon as ODIN recognized it, pushed START. It managed to upload the image into the device in a few seconds! It seems then, that the bootloop was not caused by a bad battery, but as a result of a corrupt upload of an AP image through ODIN - or because I possibly was using an incorrect version when I tried to upload an AP files to the device on my first attempt to flash it.
Note that I did search for the correct, compatible AP file, by country and model (on Sammobile) but it didn't' work (stuck at 50% in ODIN) ! so I really suggest everyone TO ONLY USE SMART SWITCH if they want to be sure that the correct firmware is being used, and avoid similar situations...
I then deleted the temp files from the PC (the actual ones which were in the temp folder), reinstalled the drivers from inside Smart Switch (just in case), booted the device to Download mode (WHICH DIDN'T BOOTLOOP this time), let Windows installing the drivers (checked in Device Manager), then restarted the PC, and ran Smart Switch again. I repeated the procedure of loading Emergency and Initialization, entering the model and serial number, having it fully downloading the firmware (again) from the web, and installing the firmware into the device. This time it completed the process, and I finally had the device installing and booting into a fresh version 6.0.1 of Android!
Hope it helps!