So, as we all must know by now, the Note 4 Retail version got the CID conversion, and now we have access to root.
But I have no such thing, because when I was messing with TWRP I couldn't flash SuperSu or Emotion r21. This resulted in a bootloop, and since I couldn't find a working way to get out of the bootloop, I decided to wipe the phone. The only issue is that I somehow accidently uninstalled android itself, leaving my phone without a system.
And now, I have used some files from http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
To be more specific, I tried to flash the "Stock restore" file, as that seemed to be the best option. I got about 98% of the way through it with Odin before I got a write-denied error.
And that's strange because I have my phone in developer mode.
And now, if I plug my phone in, it gives me a screen telling me that I must use the Verizon repair assistant application on my computer, although it doesn't recognize my phone unless its normally booted up.
Hitting the power button brings me to a download mode like screen, with the text in the top left, but a picture in the middle that tells me to use Verizons repair assistant.
The screen says "Software Update Failed ... Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update."
Booting into recovery mode doesn't work
Booting into download mode does work, however it doesn't allow me to flash anything through Odin.
I have a Verizon Note 4 N910V Retail (w/ CID change), on 5.1.1 and latest bootloader
EDIT: Also, Odin doesn't recognize when the phone is plugged in, but the pc does. The pc doesn't know what it is though.
Odin has recognized my phone after I left it off over night
Does anybody have any idea on how to fix this? There has to be a way, since its not a bricked phone
Any help is greatly appreciated
Did you try to use verizon repair assistant?
Sent from my SM-N910V using XDA-Developers mobile app
PapaDocta said:
Did you try to use verizon repair assistant?
Click to expand...
Click to collapse
Yes,but it refuses to recognize that my phone is plugged in
UPDATE: I flashed TWRP and i forgot to uncheck auto-boot, but it did get me out of Verizons restrictive boot. Also, Android is now present , just needing repairs
EDIT: Android is starting! Hopefully is someone else does this incredibly stupid and reckless use of TWRP like I did, they'll know how to fix it (to an extent). Sorry if this thread was more of a waste of space since I just fixed it myself (miraculously).
Related
Does anyone else get an error with Kies 3? when I connect my Edge Kies gives me an error! I want to perform a device recovery via Kies that's my last hope. I tried to root my Edge and now I'm stuck with a bricked phone and yes I have tried Odin 3.10.6 and regular s6 Auto Root from Chainfire as well. nothing works for me, I've looked everywhere to find the G925t firmware but no luck again. I'm really screwed.:crying:
Same
I'm guessing kies wont recognize it til after 4/10 since technically nobody is supposed to have it yet. Just a guess though.
dcmtnbkr said:
I'm guessing kies wont recognize it til after 4/10 since technically nobody is supposed to have it yet. Just a guess though.
Click to expand...
Click to collapse
same issue here. Had to use smart switch which is not as efficient from my old galaxy to the new one. Transfer stopped and had to restart 2nd time which did seem to complete.
Helium is much better for transferring data to new phone..
Same issue here. New Galaxy S6 and Kies 3 won't allow it: Unsupported device alert. WFT?
acana79 said:
Same issue here. New Galaxy S6 and Kies 3 won't allow it: Unsupported device alert. WFT?
Click to expand...
Click to collapse
Do the following: open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
Use Samsung Smart Switch instead. It has replaced Kies for the newer phones.
Here is my video showing it being used to flash Stock Firmware to the Edge.
http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176
Supersport, I have a SM-G900A (Galaxy S5 ATT) and Kies 3 and Smart Switch says it is an unsupported device. I got to the part to enter the model and serial and it comes up unsupported again. I tried a different USB cable and also tried Smart Switch on a Mac. The white USB3 Samsung cable does not allow the phone to be recognized by the Mac so I used an old USB2 cable and it hangs on "connecting to your device".
I tried downgrading to Android 4.4.2 so I could root it and it is in the "firmware encountered an issue" screen with the yellow triangle. Ack!
Boysterload said:
Supersport, I have a SM-G900A (Galaxy S5 ATT) and Kies 3 and Smart Switch says it is an unsupported device. I got to the part to enter the model and serial and it comes up unsupported again. I tried a different USB cable and also tried Smart Switch on a Mac. The white USB3 Samsung cable does not allow the phone to be recognized by the Mac so I used an old USB2 cable and it hangs on "connecting to your device".
I tried downgrading to Android 4.4.2 so I could root it and it is in the "firmware encountered an issue" screen with the yellow triangle. Ack!
Click to expand...
Click to collapse
It sounds like the MAC had issues with installing the driver. I'm not positive if your model is supported by Smart Switch yet, but I would suggest using Smart Switch as KIES has stopped official support for most of the newer models. If it's not supported yet, it should be soon. They keep adding devices. When I got my S6 Edge, it took about a week for it to be supported, but that's when Smart Switch had just come out too. Wish I was more help.
Anyone else have success getting this model to flash???
Bootloop
I initially used odin to flash OI1 update, after a rom I was using caused problems and I got bootloop. It changed bootloader value to b:3 and I'm unable to downgrade now so I used smart switch which didn't recognize device so used emergency recovery and still bootloop. I have factory reset and wipe cache multiple times along with adb side load and individual flashes of bootloader, modem, kernel, flashed custom kernel and twrp to access fix permissions and to mount partitions with advanced wipe etc and still wont boot past logo. Also during one fix attempt phone said can't mount system.. Idk I'm not understanding where the problem is .everything says successful but I'm still in bootloop. Please help. I've spent hours everyday for the past week searching & trying different things that seem might help so open to any suggestions.
I seem to be having the same issue. Tried to manually update my phone via Odin but nothing has worked so far.... Now I just get an error on my phone that says
"An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
What am I missing here?? It's a Samsung phone, and it's been around for over a year (S6 Edge T-Mobile)...
ieatcalcium said:
I seem to be having the same issue. Tried to manually update my phone via Odin but nothing has worked so far.... Now I just get an error on my phone that says
"An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
What am I missing here?? It's a Samsung phone, and it's been around for over a year (S6 Edge T-Mobile)...
Click to expand...
Click to collapse
If nothing else is working, you can try this for the T-Mobile S6 Edge. ONLY the T-Mobile S6 Edge is supported, so PLEASE verify it's the correct one.
https://mega.nz/#!H0hz2AQJ!iDzw_SwCL7qpJnZ8Y_8EDSrSgvAHK_hT93igXHOlm3A
It's a known working version of Odin, the Samsung Driver Package, and Firmware. Place your phone into Download Mode before using.
If any issues, let me know and we'll work through them.
SuperSport said:
If nothing else is working, you can try this for the T-Mobile S6 Edge. ONLY the T-Mobile S6 Edge is supported, so PLEASE verify it's the correct one.
It's a known working version of Odin, the Samsung Driver Package, and Firmware. Place your phone into Download Mode before using.
If any issues, let me know and we'll work through them.
Click to expand...
Click to collapse
No worries, I got it working! Thank you!
SOLUTION FOR ANYONE HAVING ISSUES STILL
1. Make sure you have Samsung Smart Switch Downloaded
2. Make sure Smart Switch is updated.
3. Click "more" across the top
4. Click "Emergency software recovery and initialization"
5. Click "Device initialization" across the top
6. In the model name box, type in exactly your model number. It is case sensitive. (for me, it was located on the back of my phone on the bottom named "SM-G925T)
7. It will then ask you for your serial number which can be found by holding POWER, HOME, and VOLUME DOWN
8. PROFIT$$$$$$$
Will this wipe the data like recorded audio and video files? This phone belongs to a friend with cancer and I'm trying to unload message he recorded for his family. I need to recover the data first and foremost and then getting the phone operation is secondary. I've got conflicting reports of what a firmware flash will do to recorded media files. I'm hoping the SDcard area will be unaffected but I need to know beyond a shadow of a doubt before I do anything.
Yes it will, it will behave like a factory reset. It will ask you to backup your storage content if it recognizes your phone you may be able to fix it.
Pp.
samanbabah said:
Do the following: open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
Click to expand...
Click to collapse
Thank you so f much!! I avoided waiting 8+ hours to download just the firmware. This method took less than half an hour!
*I dont know if doing something against the rules for replying to this really old thread but I am just thankful for this easy, simple method; I miss using the spen
hi,
so i just got my s6 edge for sprint shipped to me (it wasn't activated to any service when i got it). here is the order of events i took:
1) tried to activate my service, but there was a delay in porting the #
2) while waiting for them to port it, i rooted it, installed twrp and a rom (this was when it was on 5.0.2)
3) they called and said they were ready to port, but the new rom didn't have the activation software in it. so i stalled them and said i would call back. i then reverted back to stock using odin.
4) got the number ported and was fine using the phone at that point.
5) this is where the day turned bad...... i didn't realize that coincidentally today, a new firmware was released to 5.1.1 and the phone auto-updated to it while i wasn't looking
6) i went to go re-root it using the same 5.02 root and now my phone is stuck. it's sitting on the "Samsung Galaxy S6 Edge, Powered by Android" screen and in the top left in red it says "RECOVERY IS NOT SEANDROID ENFORCING"
7) i tried to restore it back to the stock using odin, but it errored in the download mode (i don't remember the error off hand)
i can get into download mode, and that's about it. i had to let the phone's battery die on it's own to turn it off (this phone gets super hot, btw)
so i guess what i need to know is how to restore back to factory default again, now that it thinks it's on 5.1.1. is there any hope?
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
bbacon said:
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
Click to expand...
Click to collapse
check this post, download the tar and flash it in odin. it worked for my phone!
http://forum.xda-developers.com/showpost.php?p=61650724&postcount=142
it got me into a recovery image that worked and i was able to factory reset in there. my phone is booting properly now. (after it reboots when done, it took a bit on the first title screen to do anything, just be patient)
Thanks man, that worked great. Although I found out in the process of trying to fix it the past few days, I must have flashed a non-compatible kernel because once it boots the touch screen is unresponsive. I guess I'll have to wait until the firmware download is available after all. Thanks again for the help though
I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Sparkinman said:
I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Click to expand...
Click to collapse
+1 on that, I'm stuck in an exact same situation. No help from Samsung either. After rooting with Kingroot my tab started acting like crazy with flickering screen and random reboots, did exactly like you did.
There are many with similar issue and as per my research most of them have given up. Getting a system image dump from a rooted tab running 4.4.2 might be the only way out. Unless of course Samsung/AT&T decides to release full odin flashable image.
I was in a similar situation from trying to fix a eff problem and took my sgh-i467 to a Samsung Experience Center located in many Best Buys and they fixed it free of charge. They were not able to fix my issue with a corrupted EFF file that is keeping my 4G from working though as I had hoped. If you have a Best Buy around with the Samsung Kiosk in it I would give it a try. I ended up trying a few different ones to fix the eff issue and some of the employees at the Samsung centers were about as smart as a head of cabbage (they laughed at me when I said my Note 8 was the issue and said "you can't have a Note 8 the Note 5 just came out") but some were at least helpful and listened when I told them they have the tools to fix my tab (reflash it back to life) and they did. Hopefully they can help you.
man Im in the same exact situation.. And I cant seem to find any help anywhere. I cant locate a stock 4.4.2 kit kat odin flashable file anywhere for the n5120
Sparkinman said:
I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Click to expand...
Click to collapse
please help me i need de 4 files repair from this tablet
Try the forum thread started by djjiz, https://forum.xda-developers.com/galaxy-note-8-0/help/i467-4-4-2-t3537302... He posted the files and yes I was able to bring back my previously bricked AT&T Note 8.
Hello, I managed to soft brick my phone while overseas and am writing this message at 2:00am in the morning (at least in this time zone) after two days of trying to fix it. Some background info--I'm usually based in the U.S., have a Samsung Galaxy S6 edge+ with service from T-mobile. Have never rooted or modified the phone in any way. I'm using a macbook pro laptop (running a windows virtual machine/vmware, on the mac) on this trip.
While on this current trip to Asia (currently in the Philippines) (much to my surprise it seems like the phone was getting 4G data here), I accidentally bumped the "yes" button on t-mobile's persistent OTA upgrade request box and the phone started a OTA upgrade, I assume to Android 6.0.1. I kept an eye on the phone as it went through various stages of progress in the upgrade. didn't see any error messages. It eventually restarted, got to the T-mobile screen, and got stuck there. That was two days ago. I've done quite a bit since that time to try to figure out what went wrong, searched all over online to find potential solutions. it goes without saying if there is any way possible i need to recover many important files on the device, so a reset is the option of last resort.
Long story short, seems like the farthest I can get on the phone is to Android Recovery mode, or the download screen. I installed the android tools and have "adb" working from the mac command line. Bad news is, it looks like I didn't have USB debugging mode activated on the phone, now I can't see any possible way to activate usb debug mode because the phone just won't boot past the t-mobile screen. I can get adb to detect the phone for a moment if I select "apply update from adb" on the recovery mode screen but that's about it, haven't been able to issue any other commands to the phone through adb other than detect and sideload.
tried to reload the android image...via command line adb sideload G928TUVU2DPD1 but get error messages about failure to verify (i think), anyways adb sideload wasn't happening. I installed Odin on my windows VM, attached the usb bridge from the mac to the windows vm and Odin was able to see the device. I was able to successfully push G928TUVU2DPD1 to the phone's download mode, both Odin and phone seemed happy about the file transfer, the phone went through a install process, restarted, with the exact same result as when the OTA update finished - phone stuck at the t-mobile screen after reboot.
I tried to load TWRP to the phone with hopes to run backups, and was actually able to transfer TWRP to the phone using Odin, yet TWRP wouldn't install -- the phone complained of the unauthorized binary. i guess the phone has to be rooted first or something else needs to be flashed to defeat the binary check, haven't tried that yet.
So I'm stuck with a soft bricked phone for now, yet instinct tells me with Odin working and talking to the phone, I should be able to install -something- that will get me back in business...that's why I'm posting this message, to ask for help as it seems like this group is the go to place for this type of specific info.
i am not at all familiar with custom android work yet have been active with tech stuff for the greater part of my life, plenty of coding and experience dating back years and have done dev work in most of the popular languages, very comfortable with command lines, log files and so forth...just never had a reason to mess around at a low level with my android phone until the past 48 hours, so i'm not really familiar. does anyone have any ideas? as a next step i'm thinking of trying to push a downgrade to the phone through Odin which I suppose would be Android 5.1.1 , although I haven't yet located binaries that feel exactly right for t-mobile and s6 edge+ ... sigh, this has been quite a time consuming way of learning the bricked phone recovery process..
:good:
thanks in advance for any ideas or help on this...it's quite disturbing to be on a business trip with no phone, and the past 6+ months worth of not backed up (gulp) data still sitting on the device (hopefully)..
here's some data from the Android Recovery screen:
6.0.1/MMB29K.G928TUVU2DPD1
samsung/zenltetmo/zenltetmo
was flipping through the recovery logs and i notice quite a few log entries about "couldn't find any tzdata when looking for localtime!" , I notice entries like "Starting recovery on Fri Jan 2 03:55:29 2015" -- i'm wondering if the phone is having trouble setting internal time and date which might be preventing it from booting...just a theory.
sorry for the long message, wanted to completely describe this fun scenario, just in case anyone has any ideas..thanks again
keep trying to load TWRP from the download screen on my phone...but get the "custom binary blocked by FTP lock" message. There's no way to change any settings on the phone as it still won't boot past the t-mobile screen..
platinum5 said:
keep trying to load TWRP from the download screen on my phone...but get the "custom binary blocked by FTP lock" message. There's no way to change any settings on the phone as it still won't boot past the t-mobile screen..
Click to expand...
Click to collapse
Can you download Odin?
Sent from my SM-N910T using Tapatalk
yes i have installed Odin and it's working fine...I can push files to the phone in download mode and it works fine, but the Android images i have loaded so far all seem to result in the phone getting stuck at the t-mobile screen...it won't go past there
Did you ever get this figured out? My guess is it has something to do with not being connected to t-mobile home network. The fact you can get to download mode & Odin sees your phone should mean all hope is not lost yet on recovering your files and getting it working again.
Twrp isn't going to work unless you had root installed with the USB debugging & oem unlock option turned on in developer mode.
Maybe try asking in some of the other s6 forums. There's a lot of knowledgeable people here & I'm sure someone knows how to fix this.
Goodluck, I hope you get it figured out, I know how frustrating it can be.
Long story short, my phone came from China and did not have Google Apps installed. I tried to root it with some youtube method and the boot.img file got changed, not knowing what to do next I gave it to repair shop.
They somehow managed to restore the stock rom and gave me the stock rom.zip file as well but the IMEI was removed, so after trying a few methods I realized my phone doesn't get detected in META Mode but somehow gets detected if it's turned off and connected directly. I thought should install the stock firmware again by myself.
I first tried it with Download mode only, it loaded a few files but gave some error like IMGHDR_TYPE_MISMATCHED. After that it got stuck on boot screen.
So instead of the download option in SP tool I chose Format All + Download.
The thing is my phone does not get detected in META Mode so I thought it wouldn't change anything but now the phone doesn't turn on. The screen is blank, nothing happens with phone is connected to charger.
If I connect the phone to PC, it detects a Preloader Port Android (COM 7) on device manager for a few seconds then goes off, then keeps going on and off like it's trying to boot but doesn't boot.
Please help. This phone can't be sent back to china because the warranty is possibly void as this phone has been used about 6 months and also been tried for rooting.
It still gets connected via SP Tool but gives the same error after loading a few files. Image Attached.
https://preview.ibb.co/kyJvZn/xt1662bricked.png
Any help in this regard would be much appreciated.
Thank you.
I had the same initial issue, so I did the "Format All + Download" on the SP Tool with a ROM I downloaded and it flashed successfully and everything works fine now, it even auto updated to the Android 7.0 and the latest security patches (05/08/18).
I cannot remember from where I got the ROM I used but I can upload it for you, if you want/need it.
The only issue is that I lost my IMEI. When I find a way to fix it I will let you know.
https://www.youtube.com/watch?v=jgTSbGBk1bI
I followed that and I successfully restored my lost IMEI, everything works fine now.
Hope it helps.
Tiki Thorsen said:
I had the same initial issue, so I did the "Format All + Download" on the SP Tool with a ROM I downloaded and it flashed successfully and everything works fine now, it even auto updated to the Android 7.0 and the latest security patches (05/08/18).
I cannot remember from where I got the ROM I used but I can upload it for you, if you want/need it.
The only issue is that I lost my IMEI. When I find a way to fix it I will let you know.
Click to expand...
Click to collapse
when i m trying this i m getting error of
verified boot is enabled please download signed image (md1img-verified.img) or disable verified boot
earthworm82 said:
when i m trying this i m getting error of
verified boot is enabled please download signed image (md1img-verified.img) or disable verified boot
Click to expand...
Click to collapse
Sadly I cannot help you since I no longer have that phone available, sorry.