Related
So I'm really into Android developing, I'm always flashing and installing etc, but I got a problem now.
Phone information
LG G2 D802
Rooted
TWRP Recovery 2.7.0.0
Was running 4.4.2, found a kdz file on the internet and flashed it (no regular update from my phone)
What happenedI actually did something stupid, I received an application update from the LG Download Center (or whatever it's called) on my phone and clicked on it. I was planning on flashing Android 4.4.2 again because my firmware was not stable, and I thought this update could help me.
But no, after it finished downloading, I automatically booted into recovery.
What I didSo I tried to reboot and enter my OS, but unfortunately, I was stuck in recovery.
I did everything I could, wiping (Dalvik) cache, factory reset, flashed a new rom, restored Nandroid backup, but no, every time I booted, I got back into recovery again.
I only saw 1 option left, booting into download mode and flashing a new firmware.
I found the Netherlands 16GB kdz file for Android 4.4.2 (because I had a French one first), the one I was looking for.
Looked all over the internet, and all guides pointed me to this guide.
Tried it, but I got multiple errors, one of them was that my phone was not connected while I was at 15% of the flash process.
What happenedAfter that first flashing process, I booted up, but got a Security Error. After the Security Error was showing for 5 seconds, my phone shut down. This is happening every time I try to boot up.
I couldn't access my recovery anymore, nothing. Edit: I can access my recovery right now, and I tried this, but when I boot up I get the Security Error again.
The big problem right now is the Security Error! How do I bypass that?
So can someone please help me out!
Several phones/tablets of mine bricked and I always found a way to get out of it, but not this time, unfortunately...
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
XxZombiePikachu said:
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
Yes, I actually have. Didn't mention it, but after I did that I booted and got an LG logo and below it was a text that said 'Security Error' After like 5 seconds the security error goes away and my phone shuts down. I can only enter download mode right now.
I'll edit my first post with this info.
Thanks for the help though!
Edit: I find a way to access my recovery again because at first I couldn't but I figured out that the code in the thread you linked was a bit different than the code I entered at first.
So I used the code you gave me, but now I get the Security Error again!
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
evilruck said:
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
Click to expand...
Click to collapse
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Ibrahim9999 said:
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Click to expand...
Click to collapse
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
evilruck said:
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
Click to expand...
Click to collapse
Thanks man! I'm probably going to save money because of you, awesome!
Ibrahim9999 said:
Thanks man! I'm probably going to save money because of you, awesome!
Click to expand...
Click to collapse
I hope so!
Let me know if you fix the thing :laugh:
evilruck said:
I hope so!
Let me know if you fix the thing :laugh:
Click to expand...
Click to collapse
I just managed to fix it! Thank you so much man!
Can someone help me plz I got flashily got CWM instead of the TWRP and got and lg update it updated and now it's stuck in recovery mode it won't go into download mode it only goes to recovery mode and my computer won't recognize my phone so if any one knows how to fix it can you plz help me out
my pc don't recognize the lg g2 in download mode!
i installed the drivers and the USB is connected but the pc don;t even say that the device is connected . and nothing in device manager at all
Perhaps you might consider sending it in to lg if you still have warranty. But I'd you don't, there are services on eBay/ Craigslist that can help you.
Sent from my LG-D800 using XDA Free mobile app
Hi guys,
I have a T-Mobile Note 3 running 4.4.2 and I'm having the hardest time installing a custom recovery such as CWM or even TWRP. I was having problems the last few days with my older phone and decided to get a free replacement because I thought it was the phone. Anyways I open my phone, boot it up, install latest software, and restart to download mode. I root it with ODIN and restart. Then I restart it again and install CWM recovery. Everything goes smoothly, everything is in the green. Then I hold volume UP, menu, and power keys and it says "Could not do normal boot. What is this? It was happening on my older Note 3 and now this one.
Everything works fine when I try to boot it normally and I can use the phone but cannot seem to install a custom recovery. Instead of booting to the recovery screen, it goes to Odin/downloading mode with a message above 'Odin Mode' that reads 'Could not do normal boot'.
I am not new to this. I have done this before many times but for some reason it is not working for me anymore. Is it the new firmware and/or the updated software that is preventing me from doing this? I have researched this night and day last 72 hours but can't find a solution.
Please help, and thanks in advance!!
Figured I'd give it a bump. Any thoughts guys?
the_real_vlad said:
Figured I'd give it a bump. Any thoughts guys?
Click to expand...
Click to collapse
Which bootloader is the phone on, and which CWM/TWRP versions are you using? You sure you downloaded the right ones for your model?
jisoo said:
Which bootloader is the phone on, and which CWM/TWRP versions are you using? You sure you downloaded the right ones for your model?
Click to expand...
Click to collapse
Hi,
Firmware on my phone: N900TUVUENK3
Recovery: n900s-cwm-recovery-6.0.4.4(1011).tar, openrecovery-twrp-2.6.3.2-hltetmo.tar
As for the bootloader, I have no idea. It is stock however, I know that.
Solved!
What I did was download the VERY LATEST twrp from the official website and flash with odin. Then I wiped EVERYTHING and reinstalled the firmware. Last, reinstalled TWRP.
All is well
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Did you try flashing custom ROM?
thickymcthick said:
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Click to expand...
Click to collapse
androidtweaker1 said:
Did you try flashing custom ROM?
Click to expand...
Click to collapse
No, I did download a CyanogenMod one, but I can't install it from recovery, as I can't get into any recovery now.
Are there any custom ROMs that can be flashed from Odin?
did you try to remove and format your extSD (possibly partly corrupted) and reinsert and flash again? Or change to other extSD?
Perru said:
did you try to remove and format your extSD (possibly partly corrupted) and reinsert and flash again? Or change to other extSD?
Click to expand...
Click to collapse
Well, I removed the card completely and reflashed with Odin. No difference.
I can't flash from a ROM on the SD card because I can't successfully boot into recovery.
I suppose, you already tried to flash twrp-2.8.7.0-klte directly from here: https://dl.twrp.me/klte
and latest stock rom for G900F and your country directly from here: http://www.sammobile.com/firmwares/database/SM-G900F/
via ODIN 3.10.7 from here: http://forum.xda-developers.com/showthread.php?t=2711451?
Perru said:
I suppose, you already tried to flash twrp-2.8.7.0-klte directly from here: https://dl.twrp.me/klte
and latest stock rom for G900F and your country directly from here: http://www.sammobile.com/firmwares/database/SM-G900F/
via ODIN 3.10.7 from here: http://forum.xda-developers.com/showthread.php?t=2711451?
Click to expand...
Click to collapse
I have, yes.
And earlier stock ROMs, and with earlier ODINs too, in various combinations.
Every time, the flash appears to work but it then hangs, booting into recovery. I get the blue 'recovery booting' line at the top, on the Samsung initial boot screen.
thickymcthick said:
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Click to expand...
Click to collapse
What s u model number
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
R u now able go to download mode.
tharik816 said:
What s u model number
Click to expand...
Click to collapse
SM-G900F, as in the thread title. Is this what you meant?
R u now able go to download mode.
Click to expand...
Click to collapse
No, nothing's changed since I last tried.
https://youtu.be/m1eRM-kSNNs
---------- Post added at 11:30 PM ---------- Previous post was at 11:22 PM ----------
Try this ...http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
tharik816 said:
https://youtu.be/m1eRM-kSNNs
Click to expand...
Click to collapse
This video just shows starting up in download mode. Not sure how this helps. I can do this, flash a stock rom or recovery with ODIN, which appears to work (get PASS at the end).
Then on reboot to recovery, it just hangs at the Recovery booting message.
http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
thickymcthick said:
This video just shows starting up in download mode. Not sure how this helps. I can do this, flash a stock rom or recovery with ODIN, which appears to work (get PASS at the end).
Then on reboot to recovery, it just hangs at the Recovery booting message.
Click to expand...
Click to collapse
download mode working or not
tharik816 said:
http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
download mode working or not
Click to expand...
Click to collapse
Appears to be, as I've said. It's the reboot to recovery after flashing that hangs.
I don't have access to a working G900F, unfortunately.
Well, it turned out to be hardware. Needed a replacement board, seems fine now. Thanks for the various suggestions, but none of them worked.
thickymcthick said:
Well, it turned out to be hardware. Needed a replacement board, seems fine now. Thanks for the various suggestions, but none of them worked.
Click to expand...
Click to collapse
wow you have an identical problem with my device. Did you go to samsung service center or a unofficial service center? and may i know how much you spend to fix that? i'm afraid it'd be expensive for a student. thanks before.
firareza said:
wow you have an identical problem with my device. Did you go to samsung service center or a unofficial service center? and may i know how much you spend to fix that? i'm afraid it'd be expensive for a student. thanks before.
Click to expand...
Click to collapse
I took it to a local (I live near London, England) Samsung authorised service centre and they replaced the board.
It cost me GBP 169... :crying:
Worse still, it turned out that it had a 2-year warranty, not the one year one that I thought it had. If I hadn't tried to reinstall Android, thereby tripping the Knox counter, it would have cost me precisely nothing...
An expensive mistake there - check your warranty carefully.
thickymcthick said:
I took it to a local (I live near London, England) Samsung authorised service centre and they replaced the board.
It cost me GBP 169... :crying:
Worse still, it turned out that it had a 2-year warranty, not the one year one that I thought it had. If I hadn't tried to reinstall Android, thereby tripping the Knox counter, it would have cost me precisely nothing...
An expensive mistake there - check your warranty carefully.
Click to expand...
Click to collapse
My warranty isn't valid since i bought a mint condition second-handed G900F from SG. I'm Indonesian. My knox is 0x1 today when i tried to fix that using boot.tar (i didn't know if it'd make my knox avoid! desperately tried every possibilities. Ended up sobbing to see that 0x1).
I thought the problem is on the software, not the hardware. So i'm bit shocked reading your statement that you replace the board. Hope the local service center near the city helps. Thanks for the info!
firareza said:
...So i'm bit shocked reading your statement that you replace the board.
Click to expand...
Click to collapse
Well the thing is, flashing a new Recovery and booting into recovery mode isn't difficult - I've done it several times with other phones, and it's a straightforward procedure.
So the fact that the phone wouldn't boot to Recovery was (in retrospect at least) a bit of an indication that all wasn't well with the hardware. I wasn't messing with the phone when it failed initially, either - I was just using it.
Booting to the stock recovery was the first test I did on the repaired phone, and it worked fine. I'll be leaving the ROM as stock, though, till the warranty runs out.
A bit strange for the board to just stop working though - I've looked after the phone very carefully since new.
Is it common with the S5, does anyone know?
thickymcthick said:
Well the thing is, flashing a new Recovery and booting into recovery mode isn't difficult - I've done it several times with other phones, and it's a straightforward procedure.
So the fact that the phone wouldn't boot to Recovery was (in retrospect at least) a bit of an indication that all wasn't well with the hardware. I wasn't messing with the phone when it failed initially, either - I was just using it.
Booting to the stock recovery was the first test I did on the repaired phone, and it worked fine. I'll be leaving the ROM as stock, though, till the warranty runs out.
A bit strange for the board to just stop working though - I've looked after the phone very carefully since new.
Is it common with the S5, does anyone know?
Click to expand...
Click to collapse
Were you able to resolve the issue?
@mike_sausage said:
Were you able to resolve the issue?
Click to expand...
Click to collapse
Er, did you read my earlier posts? #14 and later.
Hello everyone, hope all is well.
I was trying to install a factory ROM for my Galaxy S7 Edge and during the process, I believe I went and flashed a wrong ROM file (I think it was Galaxy S6 Edge's).
Anyways, due to that, my phone is completely bricked (softbricked? because I can turn it on?).
The problem I'm having is that when I turn on the device normally, it will show the GALAXY S7 EDGE logo but then it'd go straight into recovery mode.
In the recovery mode, it'd say "dm-verity verification failed.. " , "E: failed to mount /system (Invalid argument)". Then when I press Apply update from ADB/SD Card, it gives an error saying "Update from external storage is disabled".
I am able to get into the download mode also and downloaded correct factory ROM and flashed it but it gives me an error saying "Odin protocol version error" in the phone, and in Odin, it stops at "Initializing..." and the program crashes after 5 minutes or so.
I there anything I can do to unbrick this dude? I've been searching all over the place yesterday and could't find a right solution for me so I decided to write one myself.
Thanks in advance and I'll appreciate any help.
Model: G935A. AT&T.
schoolbus11 said:
Hello everyone, hope all is well.
I was trying to install a factory ROM for my Galaxy S7 Edge and during the process, I believe I went and flashed a wrong ROM file (I think it was Galaxy S6 Edge's).
Anyways, due to that, my phone is completely bricked (softbricked? because I can turn it on?).
The problem I'm having is that when I turn on the device normally, it will show the GALAXY S7 EDGE logo but then it'd go straight into recovery mode.
In the recovery mode, it'd say "dm-verity verification failed.. " , "E: failed to mount /system (Invalid argument)". Then when I press Apply update from ADB/SD Card, it gives an error saying "Update from external storage is disabled".
I am able to get into the download mode also and downloaded correct factory ROM and flashed it but it gives me an error saying "Odin protocol version error" in the phone, and in Odin, it stops at "Initializing..." and the program crashes after 5 minutes or so.
I there anything I can do to unbrick this dude? I've been searching all over the place yesterday and could't find a right solution for me so I decided to write one myself.
Thanks in advance and I'll appreciate any help.
Model: G935A. AT&T.
Click to expand...
Click to collapse
what firmware was you running and what firmware are you trying to flash ?
schoolbus11 said:
Hello everyone, hope all is well.
I was trying to install a factory ROM for my Galaxy S7 Edge and during the process, I believe I went and flashed a wrong ROM file (I think it was Galaxy S6 Edge's).
Anyways, due to that, my phone is completely bricked (softbricked? because I can turn it on?).
The problem I'm having is that when I turn on the device normally, it will show the GALAXY S7 EDGE logo but then it'd go straight into recovery mode.
In the recovery mode, it'd say "dm-verity verification failed.. " , "E: failed to mount /system (Invalid argument)". Then when I press Apply update from ADB/SD Card, it gives an error saying "Update from external storage is disabled".
I am able to get into the download mode also and downloaded correct factory ROM and flashed it but it gives me an error saying "Odin protocol version error" in the phone, and in Odin, it stops at "Initializing..." and the program crashes after 5 minutes or so.
I there anything I can do to unbrick this dude? I've been searching all over the place yesterday and could't find a right solution for me so I decided to write one myself.
Thanks in advance and I'll appreciate any help.
Model: G935A. AT&T.
Click to expand...
Click to collapse
First of all why were you trying to flash a stock Rom? Next its a piece of cake take it to your local warranty store and ask them to flash your stock ROM as long as you didn't try to root it they should fash it for you. I've done it many times. Just tell them you were charging it overnight and had it turned off and when you booted up the next morning it was going crazy.
As I said if you weren't trying to root they should do it for you.
"All we know is...He's called the Stig!"
Sent from my Echoe driven G935F
strikerdj2011 said:
what firmware was you running and what firmware are you trying to flash ?
Click to expand...
Click to collapse
I was on a rooted Galaxy S7 firmware for development purpose but I wanted to take it back to factory setting and un-root the device by installing a fresh new one.
s7freak said:
First of all why were you trying to flash a stock Rom? Next its a piece of cake take it to your local warranty store and ask them to flash your stock ROM as long as you didn't try to root it they should fash it for you. I've done it many times. Just tell them you were charging it overnight and had it turned off and when you booted up the next morning it was going crazy.
As I said if you weren't trying to root they should do it for you.
"All we know is...He's called the Stig!"
Sent from my Echoe driven G935F
Click to expand...
Click to collapse
That sounds like a clever idea but if there's any way I could try to do it by myself before I take it to them, I wanted to try.
schoolbus11 said:
I was on a rooted Galaxy S7 firmware for development purpose but I wanted to take it back to factory setting and un-root the device by installing a fresh new one.
Click to expand...
Click to collapse
if your rooted who dont you just flash a custom rom boot up then flash stock ? and i thought you cant root the american model as of the locked bootloader just you said 935a thought that was usa model ?
strikerdj2011 said:
if your rooted who dont you just flash a custom rom boot up then flash stock ? and i thought you cant root the american model as of the locked bootloader just you said 935a thought that was usa model ?
Click to expand...
Click to collapse
Well now I couldn't flash any of the firmwares out there that I found. I kept on getting the same error stated above. It is usa at&t model.
Perhaps, is there a custom ROM and/or other steps you'd recommend me to try?
Thanks for your replies though, I appreciate it very much.
schoolbus11 said:
Well now I couldn't flash any of the firmwares out there that I found. I kept on getting the same error stated above. It is usa at&t model.
Perhaps, is there a custom ROM and/or other steps you'd recommend me to try?
Thanks for your replies though, I appreciate it very much.
Click to expand...
Click to collapse
just a massive shot in the dark here dm-verity verification failed when we flash a custom rom on our international 935f in twrp we have to format data in twrp to be able to flash any thing how about if there is a twrp for the qualacom version how about you flash the twrp format data then flash stock via twrp i know its a shot in the dark but best i can think of at the moment
strikerdj2011 said:
just a massive shot in the dark here dm-verity verification failed when we flash a custom rom on our international 935f in twrp we have to format data in twrp to be able to flash any thing how about if there is a twrp for the qualacom version how about you flash the twrp format data then flash stock via twrp i know its a shot in the dark but best i can think of at the moment
Click to expand...
Click to collapse
I will try what you have suggested. But isn't twrp only install-able when the phone is actually turned on to OS? As far as I've researched, I saw that it needs to have developer mode on.
schoolbus11 said:
I will try what you have suggested. But isn't twrp only install-able when the phone is actually turned on to OS? As far as I've researched, I saw that it needs to have developer mode on.
Click to expand...
Click to collapse
no odin flash twrp in download mode make sure there is a twrp for you device i know there is for the flat s7
Try smart switch emergancy mode
strikerdj2011 said:
no odin flash twrp in download mode make sure there is a twrp for you device i know there is for the flat s7
Click to expand...
Click to collapse
I tried to download one here http://androiding.how/galaxy-s7-edge-twrp-recovery/ and tried to flash it but I get the same error => "Odin protocol version error!", and stuck at "Initialization..".
Do you think you could verify if that link could be the one I'm looking for?
MATRIKS said:
Try smart switch emergancy mode
Click to expand...
Click to collapse
I tried it but unfortunately, I don't understand why but it doesn't recognize my S/N.
schoolbus11 said:
I tried to download one here http://androiding.how/galaxy-s7-edge-twrp-recovery/ and tried to flash it but I get the same error => "Odin protocol version error!", and stuck at "Initialization..".
Do you think you could verify if that link could be the one I'm looking for?
I tried it but unfortunately, I don't understand why but it doesn't recognize my S/N.
Click to expand...
Click to collapse
thats for the international version which is exynos and not qualacom
strikerdj2011 said:
thats for the international version which is exynos and not qualacom
Click to expand...
Click to collapse
Right.. Then that means I should wait for Qualcomm version to be released?
there doesnt seem to be one yet for the usa version of the edge you did turn on thre allow oem unlock in developer options on the device before you started playing with the firmwares didnt you ?
strikerdj2011 said:
there doesnt seem to be one yet for the usa version of the edge you did turn on thre allow oem unlock in developer options on the device before you started playing with the firmwares didnt you ?
Click to expand...
Click to collapse
Allow oem unlock.. I didn't allow it.. I regretted so much after I flashed everything and realized i didnt turn it on. -_- Probably not fixable?
schoolbus11 said:
Allow oem unlock.. I didn't allow it.. I regretted so much after I flashed everything and realized i didnt turn it on. -_- Probably not fixable?
Click to expand...
Click to collapse
i am not a dev mate just learn from observation lol but from other devices i have seen them bricked if thats not been allowed in dev options but i am not 100% sure on this one service center is probs you best bet as some one said earlier as am sure if thats not checked nothing can be flashed as that command allows it its like the bootloader is still locked kind of thing
I would take it a service repair center before messing it up anymore, just to be on the safe side, you never know with these things, yeah it might be fixable but if knox isn't voided then you can just have it repaired properly for free.
strikerdj2011 said:
i am not a dev mate just learn from observation lol but from other devices i have seen them bricked if thats not been allowed in dev options but i am not 100% sure on this one service center is probs you best bet as some one said earlier as am sure if thats not checked nothing can be flashed as that command allows it its like the bootloader is still locked kind of thing
Click to expand...
Click to collapse
samuel2706 said:
I would take it a service repair center before messing it up anymore, just to be on the safe side, you never know with these things, yeah it might be fixable but if knox isn't voided then you can just have it repaired properly for free.
Click to expand...
Click to collapse
I figured... Thanks for your help and suggestions anyways. Have a good one.
schoolbus11 said:
I figured... Thanks for your help and suggestions anyways. Have a good one.
Click to expand...
Click to collapse
Did you manage to get this sorted?
I'm having same issue
bump
Hi so first of all im kind of a noob when it comes to this so please explain any technical jargon
It all started a few days ago when my note 4 started rebooting on its own, it did occasionally get stuck in bootloop but a battery pull fixed every time, I hadn't rooted it or did anything that could break it that way just normal media consumption. About 2 days later it started to get stuck on bootloop more than half the times it rebooted (again all without a reason) Currently it doesnt even show the boot animation and i can't access recovery mode, I can access odin mode tho but i flashing it twice didn't help
I have the uk O2 version (SM-N910F) with a powerbear battery that doesn't show any signs of wear down
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience
Did you flash stock rom(latest) successfully through odin? Did odin show 'success' message after finishing flashing?
Mufrad said:
Did you flash stock rom(latest) successfully through odin? Did odin show 'success' message after finishing flashing?
Click to expand...
Click to collapse
yes and yes, I used the latest stock rom from sammobile and it did successfully flash but when it tries to go to recovery mode after that it just goes to bootloop again (it shows the "recovery booting..." in blue at the top)
Altrath said:
yes and yes, I used the latest stock rom from sammobile and it did successfully flash but when it tries to go to recovery mode after that it just goes to bootloop again (it shows the "recovery booting..." in blue at the top)
Click to expand...
Click to collapse
I am not sure what's wrong, but I would install a custom recovery and try and install a custom rom to check if everything works right, if it does then maybe try and flash stock through odin again.
Altrath said:
Hi so first of all im kind of a noob when it comes to this so please explain any technical jargon
It all started a few days ago when my note 4 started rebooting on its own, it did occasionally get stuck in bootloop but a battery pull fixed every time, I hadn't rooted it or did anything that could break it that way just normal media consumption. About 2 days later it started to get stuck on bootloop more than half the times it rebooted (again all without a reason) Currently it doesnt even show the boot animation and i can't access recovery mode, I can access odin mode tho but i flashing it twice didn't help
I have the uk O2 version (SM-N910F) with a powerbear battery that doesn't show any signs of wear down
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience
Click to expand...
Click to collapse
Mate, the 910F is a Snapdragon - famous for it's eMMc problem. You may search about this and get more info.
In short, there's a big chance it's not going to get to work again.
Sorry for your loss.
The problem seems to be caused by the eMMc chip
Is there a way to fix or replace it without expensive equiepement?
Mufrad said:
I am not sure what's wrong, but I would install a custom recovery and try and install a custom rom to check if everything works right, if it does then maybe try and flash stock through odin again.
Click to expand...
Click to collapse
btw flashing TWRP or any recovery doesn't work so i'm pretty sure it's the eMMc chip
If it really is your eMMC chip, you are better off trying to get a new device. The eMMC chip isn't removable without a lot of time, effort and risks. Also you'll need a head Gun or something and a new identical chip that will cost you a new device worth.
Altrath said:
The problem seems to be caused by the eMMc chip
Is there a way to fix or replace it without expensive equiepement?
Click to expand...
Click to collapse
try
https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448