Related
I need help guys,
I used Odin to root the phone and did my first custom rom which is the clean rom...it went through the process and when it was about to reboot i got the system software not approved by verizon and take phone to store
I have been told to odin back to stock but it wont let me. The stock image on odin wont work it says fail
I tried the first method and used odin in download mode to flash the stock image
Failed:
This is what I get
added
Odin V3 engine
File Analysis
all threads completed (succeed 0 / Fail 1)
In the Odin Download mode on the phone the top left reads as follow
Odin Mode (Red Letters)
Product Name (SCH-I535)
Custom Binary Download : Yes (1 counts )
Current Binary Custom
System Status Custom
Qualcomm Secureboot: Enable
One thing I gotta mention is that when I got the phone last week it had an OTA update from Verizon which I did install and then a few days later I rooted the phone and when I tried to use Clean Rom it gave me the dreaded Verizon message
Sounds like you didn't unlock the bootloader.
Ya your bootloader is locked again ... unlock it and redo the steps everything should be fine after that
Guys I know that the bootloader is locked but i cannot get back to stock to unroot phone and then unlock the bootloader
Odin recognizes phone but the stock image goes into fail mode right away
I cannot get into recovery and the only thing I can do is go to download mode and Odin but nothing else
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Stranger_84 said:
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Click to expand...
Click to collapse
You are aware he can Odin flashed the latest OTA instead of that you have provided. Here it is :http://forum.xda-developers.com/showthread.php?t=2046439. This will also help fix his phone being that it is recent. Forgot this link to get him back on track: http://forum.xda-developers.com/showthread.php?t=1974114.
i thought thats what he already tried? but yes you can odin any ota file being that an unlocked bootloader isnt needed.
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
I'm not sure being ive never had that issues ... im sorry and good luck
try flashing odin stock ROM, not bootchain
NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
Did you put the file in PDA in Odin they only work if you checked PDA.
NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
I had a similar issue once. This helpful post by h3llsdr0id eventually got me up and running. Took a total of like 4 hours though lol.
http://forum.xda-developers.com/showpost.php?p=30569324&postcount=26
Make sure you have the correct files. This is for the original root66 so it's ICS. Once I booted up and activated I took the Verizon OTAs all the way to JB and then rooted/unlocked bootloader.
edit: I actually had to go back to ICS to reprovision my SIM so not sure you have to go through all of this. Try to odin stock JB ROM like mentioned above.
Thank YOU so much guys you have made my day.
After trying all last night and today I got it back to stock with the OTA file through ODIN. That is all I needed and it went right back to brand new stock phone using 4.1.1
WOW.
I thought I was going to have a dead phone.
Thank you all
Glad you got it up and working!!!!!
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
I'm having the same problem and can't get into download mode
Gatanater said:
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
You have to get into download mode to use Odin. It will go into download mode, if you will search, there are ways to pull battery along with button combo to get it there. After rooting, use EZ Unlock 1.2 and that will unlock your bootloader without then unauthorized message from Verizon. Make sure you use only that version, the others don't work.
Re: I'm having the same problem and can't get into download mode
mj76 said:
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
Click to expand...
Click to collapse
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
flammablepez said:
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
Click to expand...
Click to collapse
Thank you for your response. I tried pulling the battery out and holding volume down, home and power keys at the same time while putting battery in, even as i plugged it into my phone, but nothing but the unauthorized error screen comes up. I should note that my phone is note 2 not s3. I apologize for posting it here, but this thread seemed to be just like the problem i was having.
This is a very noob thing to do.
I have a Verizon S3 with a broken screen. So I was fooling around with it without reading the forum.
I have a fresh MF1 installed, then rooted and also installed ROM Manager. The foolish thing is that I used ROM manager to boot into recovery.
The boot failed. Now the stock recovery is gone. The worst thing is that, now I can't even get into Odin. The phone kept vibrating and give the yellow triangle, saying, System software not authorized by Verison wireless has been found on your phone.....
I do not know what to do now. I think the first thing I have to do is to get rid of the CWM recovery, which never worked in this case. Then I can get the Odin back.
I tried the download button combo. I got to Odin just once. And the Odin session did not complete stating that it could not find a COM port. So Odin is no go now.
Do I have to get on adb or bootloader level? How?
deleted.
Well, I think I made a fool of myself.
After repeated failures to boot into Odin, I put the phone to some rest. Then I just tried it one more time and my lovely Odin has returned. So I flash the phone with the stock ROM and the phone is back to normal.
I was thinking I have another hard bricked phone. I think by pulling the battery and put the phone to rest, it changed something.
BaSingSe said:
Well, I think I made a fool of myself.
After repeated failures to boot into Odin, I put the phone to some rest. Then I just tried it one more time and my lovely Odin has returned. So I flash the phone with the stock ROM and the phone is back to normal.
I was thinking I have another hard bricked phone. I think by pulling the battery and put the phone to rest, it changed something.
Click to expand...
Click to collapse
You got that warning message at boot because you didn't unlock your bootloader.
Sent from my SCH-I535 using Tapatalk
Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.
I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:
heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img
However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.
Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.
I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?
Thanks for any help you can advise on ....
vax1170 said:
Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.
I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:
heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img
However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.
Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.
I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?
Thanks for any help you can advise on ....
Click to expand...
Click to collapse
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
buhohitr said:
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
Click to expand...
Click to collapse
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:
ODIN MODE
product name: SCH-I535
custom binary download: no
current binary: Samsung official
System status: Official
QUALCOMM secureboot ENABLE
And nothing else after that (just the green antroid graphic and 'downlaoding....')
Thank you for the fast response
vax1170 said:
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:
ODIN MODE
product name: SCH-I535
custom binary download: no
current binary: Samsung official
System status: Official
QUALCOMM secureboot ENABLE
And nothing else after that (just the green antroid graphic and 'downlaoding....')
Thank you for the fast response
Click to expand...
Click to collapse
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.
buhohitr said:
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.
Click to expand...
Click to collapse
Sorry I wasn't clear ....
I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.
It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.
After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.
If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.
Let me know what you think .... thanks!
vax1170 said:
Sorry I wasn't clear ....
I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.
It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.
After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.
If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.
Let me know what you think .... thanks!
Click to expand...
Click to collapse
It's possible that the 4.3 bootloader already flashed and it's in the process of flashing the rom when you pulled the battery. In any case, if the software is half done you phone won't boot, and if you attempt to flash the old rom, you will brick your phone if the bootloader already locked. So you need to turn it on to see where you at or you can take a chance and try to Odin old stock rom, again if the bootloader already locked you will brick your phone and if not then you will be back to the older version. I would turn it on and see.
Thanks.
Is there anyway to tell for sure if the bootloader is the new one?
Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.
Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there? I already did a print-pit on all 3 phones, but from what little I know it seems like the only differences are likely due to the memory sizes. 32 vs 16.
If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,
vax1170 said:
Thanks.
Is there anyway to tell for sure if the bootloader is the new one?
Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.
Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there?
If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,
Click to expand...
Click to collapse
If you don't see the last 2 lines like I mentioned above, it should be the old bootloader...since the timing you pull the battery, no one really know what state it's in unless you boot it up.
Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?
The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.
Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....
vax1170 said:
Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?
The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.
Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....
Click to expand...
Click to collapse
Yes, you can boot up now and see what's going on...
So it looks like it is bricked to some degree. What might you advise to undo this?
When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.
If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.
If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.
What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.
Thanks
vax1170 said:
So it looks like it is bricked to some degree. What might you advise to undo this?
When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.
If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.
If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.
What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.
Thanks
Click to expand...
Click to collapse
I would try to use Odin and flash MF1 full firmware here http://www.androidfilehost.com/?fid=23134718111254196
Thanks for confirming ... I was poking around the forums and figured I should probably try the procedure to completely reflash my device back to stock. I'll try that later tonight. Thanks again ... crossing my fingers
[RESOLVED]
Looks like flashing the 4.1.2 stock image worked, device boots now!
There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.
On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.
Some summary details to anyone who is interested:
- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.
- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.
- On reboot, the phone has pulsing blue LED; bricked
- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.
If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.
Thanks for the help!
vax1170 said:
Looks like flashing the 4.1.2 stock image worked, device boots now!
There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.
On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.
Some summary details to anyone who is interested:
- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.
- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.
- On reboot, the phone has pulsing blue LED; bricked
- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.
If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.
Thanks for the help!
Click to expand...
Click to collapse
You're a lucky son of .....lol.
My Galaxy S7 (SM-G930R4) has decided to not want to boot. I can't boot normally or into recovery. I can only boot into Odin mode.
I've tried to flash stock rom, but it doesn't seem to work. I've heard that I should use the ROM from samsmobile, so I'll try that next.
This all started to happen after I accidentally turned on the phone right before I took the battery out. I put that battery back in and it booted fine, but after a few minutes it rebooted and started to reboot over and over again. It won't even show the charging screen when it is turned off and plugged in.
OK, I tried to flash the stock rom with Odin, but it still is in a boot loop. I've flashed it 3 times. I've firmware files from different sites. It seems that this S7 is dead. Please help!
Try to flash another rom and keep in mind that it sometimes takes up to 10-15 minutes at the first boot.
You could also just flash TWRP...
ATP-Flo said:
Try to flash another rom and keep in mind that it sometimes takes up to 10-15 minutes at the first boot.
You could also just flash TWRP...
Click to expand...
Click to collapse
TWRP for the Samsung Galaxy S7 (SM-G930R4)???
Also, now I've been greeted with the screen that says "An error has occurred while updating the device software." It says to use the Samsung Smart Switch PC software to fix it. Hopefully that works.
Where are you?
What firmware are you using? Branded or unbranded?
Have you looked on Sammobile for the correct firmware?
Are you able to boot into system recovery? Home+VOLUME UP+Power (Not Download)?
Oh you have got the G930R4. I thought G930F.
Then I don't know if there is a TWRP you could flash.
But if there is one you could just flash it and enter recovery mode and install a new ROM from within the TWRP environment.
Check this out.
https://dl.twrp.me/herolte/
Sounds like your device is currently bricked anyways, so just give it a try.
Maybe you can get a working TWRP recovery mode again.
Also check these links:
http://www.techzai.com/root-galaxy-s7-s7-edge-android-8-0/
and
https://twrp.me/samsung/samsunggalaxys7.html
cooltt said:
Where are you?
What firmware are you using? Branded or unbranded?
Have you looked on Sammobile for the correct firmware?
Are you able to boot into system recovery? Home+VOLUME UP+Power (Not Download)?
Click to expand...
Click to collapse
I am in the US.
I'm on Android 8.0 (Oreo)
I have a US Cellular Branded phone.
As soon as the phone is turned on, it tries to boot into recovery, but it can't so it keeps on trying over and over again. I've tried the firmware from SamMobile, but nothing seems to work.
When I flash to Stock ROM, and I turn the phone on, it stays in a bootloop of the "Recovery Booting..." screen.
When I flash the rooted Engineering rom, and I turn the phone on, it stays in a bootloop of the Samsung S7 logo. I can't boot into safe mode.
I tried to use Samsung Kies... didn't work... I tried to use Samsung Smart Switch... didn't work... I've tried 3 or 4 different ROMs from different websites.... didn't work.
i have the same problem. was able to enter download mode several times, but at some point it died completely (not charging anymore). how do you manage to take the battery out? does the SM-G930R4 the possibility to easily remove it?
Cloud2F said:
i have the same problem. was able to enter download mode several times, but at some point it died completely (not charging anymore). how do you manage to take the battery out? does the SM-G930R4 the possibility to easily remove it?
Click to expand...
Click to collapse
The glass panel on the back is glued onto the phone. If you remove the glass, there are screws and from there, it's easy. I broke the glass in the process... so yay me.
Mine won't charge either. It is completely dead, but it will still turn on when I plug it into my computer.
Really strange. Mine is not turning on, even tried several locations, charger, etc. Once I had download mode while having a black screen. Keep an eye on odin and instantly flash firmware if it got recognized. I press all three buttons while plugging in; that's how it worked the first time for me....
Hi all,
I have a Samsung A8 that I have been given to me to sort out.
Its currently boot looping at the initial Samsung Logo.
I can get into this recovery mode section shown in attached picture.
The person tells me they went into this mode and pressed Wipe Data/Factory reset as well as Wipe Case Partition.
Since they did this, its been boot looping, it was working perfectly fine before hand.
Im not sure if this has already been rooted or if this is a custom recovery rom?
Not had to deal with rooting or anything for quite some years!
Could anyone help?
Is this rooted, and could I just flash a custom ROM to get it back up and working.
Or is their a stock ROM I can just flash to get this working?
Any help would be really appreciated!
Cheers
keef01 said:
Hi all,
I have a Samsung A8 that I have been given to me to sort out.
Its currently boot looping at the initial Samsung Logo.
I can get into this recovery mode section shown in attached picture.
The person tells me they went into this mode and pressed Wipe Data/Factory reset as well as Wipe Case Partition.
Since they did this, its been boot looping, it was working perfectly fine before hand.
Im not sure if this has already been rooted or if this is a custom recovery rom?
Not had to deal with rooting or anything for quite some years!
Could anyone help?
Is this rooted, and could I just flash a custom ROM to get it back up and working.
Or is their a stock ROM I can just flash to get this working?
Any help would be really appreciated!
Cheers
Click to expand...
Click to collapse
so, that screen is the stock recovery where, yes, you can wipe everything that was on the phone, which is actually a good thing. Turn the phone off completely, let it sit for a couple seconds once youre certsin that its completely off. Press and hold both volume buttons and then simultaneously press and hold the power button until it buzzes. When it buzzes, release the power button but continue holding the volume buttons until a screen comes up that asks you to press up to continue or down to reboot. Press volume up, take a pic of that screen and post it up on here. Thats "download mode" aka "Odin mode" From there you can flash the stock firmware and rid yourself of the insidious bootloop. Youll need the firmware from sammobile.com/firmwares tho. Anyways, get to that screen and post the pic up so we can further assist! Have a good day!
keef01 said:
Hi all,
I have a Samsung A8 that I have been given to me to sort out.
Its currently boot looping at the initial Samsung Logo.
I can get into this recovery mode section shown in attached picture.
The person tells me they went into this mode and pressed Wipe Data/Factory reset as well as Wipe Case Partition.
Since they did this, its been boot looping, it was working perfectly fine before hand.
Im not sure if this has already been rooted or if this is a custom recovery rom?
Not had to deal with rooting or anything for quite some years!
Could anyone help?
Is this rooted, and could I just flash a custom ROM to get it back up and working.
Or is their a stock ROM I can just flash to get this working?
Any help would be really appreciated!
Cheers
Click to expand...
Click to collapse
Flash Firmware using Odin and also tick Nand erase
was your problem sorted out