Need some guidance on this one. Went through trying to root my Note 4. Upgraded from 4.4.4 to 5.1.1 after all this time waiting. From there, continually hitting soft bricks (referring to endless boot loop in regards to soft brick) and a lot of the issue I believe to be my battery. However, was originally able to flash the 5.1.1 FW (N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5) and the brick would be remedied. At this point however, the note just goes into a endless boot loop where only thing it displays is the "Samsung Galaxy Note 4 Powered by Android" splashscreen (Never displays the oval samsung or verizon splashscreens) and vibrates twice as the screen display goes off for about 3 secs and pops back up with the same screen over again. At this point, the only thing I have found to remedy this is the Verizon Software Update program, which instantly updates to 6.0.1 (newest FW). This wouldn't be an issue, with the exception that the 5.1.1 FW still puts the phone into the soft brick state. Anyone have an idea why the FW is now putting into a brick and how to fix the issue so I can downgrade successfully?
In case it matters, to get the Verizon program to work, I would flash "N910VVRU2BPA1_StockRestore.tar.md5" via Odin and from there, download mode would then populate a screen stating update failed and to utilize the program. Seems to be the only way to get it to be able to connect.
Also, with all that said, the one thing I have thought about doing, but haven't is re-partitioning with a PIT file. However, I have not come across any threads on re-partitioning the Note 4 and those that refer state not to. With that said, I wouldn't mind attempting it if someone else feels like it may work. If so, please lead me to a thread with instructions along with a correct PIT file in order to run through the process please.
hey man I'm actually running into a similar issue. Ran into it while attempting to Root via Kingroot on 5.0.1 I was following a guide, the phone rebooted on it's own during the process and didn't have any issues rebooting, but at one point I wanted to reboot and instead of pulling the battery like normal, I decided to press the reboot option in the power menu, bad idea, now I'm bricked and Odining PA1 is not allowing a proper boot... have you found a solution to your problem? maybe it would help me with mine
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
well after a really long battery pull, its booting up for me, I hope you were able to resolve this issue
Related
So, at the risk of posting too much info (instead of not enough) I'm going to start at the beginning:
I rooted my wife's S3 and loaded TWRP and Paranoid Android. It ran fine, but there was a camera issue, so she wanted me to restore it to the stock ROM. I did this (to 4.1, I believe, whatever was out in August). Again, it ran fine and I was planning to restore the root access, but did not.
Later, it was dropped in Hibachi sauce (not sure this is relevant, but in case) and we put it immediately in rice. It worked fine, other than the touch screen intermittently ceasing to receive touch commands.
When the updated ROM came from Samsung, my wife installed the update and the phone continued to work fine, other than the screen issue.
She was tired of the issue and decided to sell it to buy an iPhone (shudder) so she did a factory reset. This is where the issues began (I included the previous steps as I'm not sure which may have caused the current issue).
Upon the factory reset, the phone would only boot to the beginning of the AT&T logo loading. I thought it may be something she could fix through Kies and suggested she try that, so she did. The phone would then boot to a screen in Odin mode that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." We did this and there was no help.
I can get it to boot into recovery (the default one now) and have tried to reflash that and the stock ROM that I did previously and only can get two actions: either the freeze at the AT&T logo (if I use Odin to flash the ROM) or the above message in Odin mode (after trying to fix from Kies).
I'm not sure what to do at this point and would appreciate any and all help you guys can provide. I've lurked around and learned quite a bit to flash my ROM and my wife's from you guys, so I'm really hoping I can learn more from this.
Thanks in advance!
Fearborn said:
So, at the risk of posting too much info (instead of not enough) I'm going to start at the beginning:
I rooted my wife's S3 and loaded TWRP and Paranoid Android. It ran fine, but there was a camera issue, so she wanted me to restore it to the stock ROM. I did this (to 4.1, I believe, whatever was out in August). Again, it ran fine and I was planning to restore the root access, but did not.
Later, it was dropped in Hibachi sauce (not sure this is relevant, but in case) and we put it immediately in rice. It worked fine, other than the touch screen intermittently ceasing to receive touch commands.
When the updated ROM came from Samsung, my wife installed the update and the phone continued to work fine, other than the screen issue.
She was tired of the issue and decided to sell it to buy an iPhone (shudder) so she did a factory reset. This is where the issues began (I included the previous steps as I'm not sure which may have caused the current issue).
Upon the factory reset, the phone would only boot to the beginning of the AT&T logo loading. I thought it may be something she could fix through Kies and suggested she try that, so she did. The phone would then boot to a screen in Odin mode that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." We did this and there was no help.
I can get it to boot into recovery (the default one now) and have tried to reflash that and the stock ROM that I did previously and only can get two actions: either the freeze at the AT&T logo (if I use Odin to flash the ROM) or the above message in Odin mode (after trying to fix from Kies).
I'm not sure what to do at this point and would appreciate any and all help you guys can provide. I've lurked around and learned quite a bit to flash my ROM and my wife's from you guys, so I'm really hoping I can learn more from this.
Thanks in advance!
Click to expand...
Click to collapse
So is it stuck on the AT&T Logo? Or Samsung Logo?
UnknownTroll1 said:
So is it stuck on the AT&T Logo? Or Samsung Logo?
Click to expand...
Click to collapse
It was the AT&T logo, it's currently the Odin. If I flash it again with the stock ROM, it'll be the AT&T logo again, but it doesn't completely load the AT&T logo. The Samsung one loads and then the AT&T starts to load, but doesn't finish playing.
Anyone?
Yes, Odin to stock unrooted, then go ahead and factory reset by holding volume up + home button on first boot. Done.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jblparisi said:
Yes, Odin to stock unrooted, then go ahead and factory reset by holding volume up + home button on first boot. Done.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
If this works (I'll try it when I get home) I will be so grateful! BTW, do you happen to have a decent link to a stock ROM? If not, I'll Google it tonight.
I am currently having trouble with my phone, it works fine as long as i do not turn my phone off. If I turn my phone off it seems to go into a hard brick, and I cannot get back into my phone unless I use a homemade jig to get into download mode and there for getting back to my phone rebooting. I noticed this problem right after I downloaded the teamwin app to update my recovery, but I accidentally choose the "I9300" recovery instead of my phone "I747". That initially put my phone into the first hard brick that I encountered, then with the help with www youtube com/watch?v=y5_yoJilLe0, I was able to get my phone and flash the correct recovery as well as a new rom. So my question is, how can I fix this problem of not turning off my phone and making it go into a hard brick? Any help will be much appreciated, and I am sorry if this is in the wrong place, this is my first post.
I do have a nandroid backup that I have tried and it still has this problem
Further testing I have figured out that I have to have my SD card that has the software to unbrick(using the method in the youtube video) in my phone for it to turn on. With my SD card out it acts just like a hard brick.
Sounds like a bootloader problem...
You probably flashed over sbl1. Its not included in firmware updates so the odin flash will not help.
Thats just a guess though. It depends on what partition the i9300 stores its recovery. It may be a different one from sbl1.
---------- Post added at 04:36 AM ---------- Previous post was at 04:28 AM ----------
Ok, I just checked and you wrote over the rpm partition (mmcblk0p6). This is included in the firmware package so flashing with odin should have fixed it. Did you not flash the firmware? You said you followed a video, but you should use the instructions we have in this forum.
It also helps to know what build your current firmware is.
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
GoonReb0rn said:
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
Click to expand...
Click to collapse
Update: I spent the past two days trying to solve this and I'm at a standstill in progress. It seems that my phone was one that suffered SDS with a corrupt eMMC chip so I've lost both my firmware and recovery but I can still get into Download mode. It also seems like I have lost my PIT table and I am just completely unable to flash the PIT file back to the phone for some reason. Does anyone have any ideas on how I could just factory reset my phone or reinstall my partition table so that i can get a simple recovery installed? Please help
Exact same issue!
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
dkinniburgh said:
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
Click to expand...
Click to collapse
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
GoonReb0rn said:
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
Click to expand...
Click to collapse
I was lucky having most of my info already backed up. I also had just upgraded another line, so I had a new phone to work with. It just sucks having to switch everything over to a new phone, reloading all the apps etc.
I have what's probably a unique situation, though I hope not. For background info, I bought two I747s, one white and one blue, each with issues, but I intended to put parts together to end up with one good one.
When I did a factory reset on the blue one via the recovery menu, it returned a bunch of errors along the lines of "failed to mount /data." Then when it rebooted it would hang on the Samsung logo. Back in recovery mode it returns more of the same errors just booting into recovery mode, and factory reset still returns more of the same errors and doesn't fix anything. I flashed 4.3 with Odin in an attempt to fix it, but I got the boards mixed up, and that one had 4.4 on it, not 4.1 like I thought. I'm pretty sure it's hard bricked now (that whole can't downgrade thing) because it's unresponsive to everything. Though my computer does recognize that it's plugged in, more on that later.
So I figured, fine, I screwed up, I'll just use the other board with 4.1 on it from the white phone. Except when I did a factory reset on that one, it did the exact same thing! Same errors, same problem stuck at the Samsung logo. Except this time I'm not flashing sh*t until I know exactly what I need to do to fix it. In another post where the guy had the same issue with 4.1.1, it was solved by flashing 4.3 with Odin. And another post where the guy had no idea what version he had, he just knew it was lower than 4.3, his problem was also solved by flashing 4.3, But since my last efforts failed miserably, I'm very reluctant to try it until I get some knowledgeable input. I don't remember exactly which version is on there, it's 4.1.something. I'd also prefer not to upgrade beyond 4.1 because I'd like to unlock it and from what I'm reading you can only do it for free if you're on 4.1. So I guess I need a link to an Odin flashable 4.1 package?
As for the poor blue phone that used to have 4.4.something, and was mistakenly flashed with 4.3, I've heard about JTAG but I don't quite understand it, and I'm not sure it would work in my case since a lot of what I'm reading says that bricking which occurs from downgrading is often unfixable. However, Windows recognizes that a device is plugged in when I attach it via USB. It shows up in the Device Manager as QHSUSB_DLOAD. I am currently researching more on this and the method of booting from an SD card, except I don't have an SD card reader at the moment.
Any assistance, advice, links, information, and plain ole encouragement are always welcome and appreciated.
For the phone running 4.1, flash any stock rom in Odin. After flashing, boot into recovery and perform a factory reset, then boot the phone and use the free method to sim unlock. The important thing is to have the stock 4.1.1 dialler in order to access the hidden menu options?
For home hard bricked phone, you will have to try the debrick image method. If it doesn't work, a jtag service should be able to force flash a rom to the phone.
Wow, that was like a crazy fast reply!
What if the phone is 4.1.2? Can I still flash 4.1.1? I'm on the hunt for a 4.1.1 stock rom now.
Yes, you can flash 4.1.1 from 4.1.2.
audit13 said:
Yes, you can flash 4.1.1 from 4.1.2.
Click to expand...
Click to collapse
Apparently not always. I downloaded and flashed 4.1.1 with Oden 3.07, it rebooted, showed the android image like it was updating, progress bar finished, and then it just went blank. Now both phones are in the same condition of being hard bricked and showing QHSUSB_DLOAD in the device manager.
This is strange. I have downgraded approximately 10 i747m phones from 4.1.2 to 4.1.1, unlocked using the free method, and re-flashed back to 4.1.2 after unlocking.
http://forum.xda-developers.com/showthread.php?t=2371897
What options did you check in Odin? Where did you get the 4.1.1 ROM? I ask because the stock ATT 4.1.1 rom was apparently removed from sammobile.com.
How did you confirm that the phone was running 4.1.2?
I checked only auto reboot in Odin.
I found this link sammobile.com/firmwares/database/SGH-I747/ in this thread http://forum.xda-developers.com/galaxy-s3-att/help/downgrade-att-running-stock-4-4-2-rom-t3170938 , 7th post
The download was going absurdly slow, so I googled the exact file name being downloaded which was, I747UCDLK3_I747ATTDLK3_ATT, and found a google drive link at https://drive.google.com/file/d/0B_UTWXKFnZoNVFdSVjJEZlMwZjA/edit which was the first result after searching for the file name if that link doesn't work. I'm downloading the slow one now to compare it to the one I got from google drive.
I'm unsure if the phone was 4.1.1 or 4.1.2, that's why I asked if it's possible to flash 4.1.1 on top of 4.1.2. I was only trying to do a factory reset originally and had no intentions of flashing anything. I just wanted to wipe out all the crap on it from the previous user so I had only glanced at the version out of curiosity to see if it was unlockable via the free method. I remember it was 4.1.something.
I have an SD card reader on order. Hopefully I'll be able to unbrick one of them.
Do you, or anyone else, have any idea why a simple factory reset would cause errors like I described and then hang on reboot? At that point both phones were 100% factory and I hadn't done anything to them except put a battery in them to power them on. I've done a factory reset on four other S3s and this didn't happen.
It is definitely possible to flash 4.1.1 over 4.1.2 because the bootloader could not be downgraded until the mjb version.
That's what I've been reading. So where did I go wrong? Any idea why a factory reset would screw up like that?
Did you confirm the bootloader before flashing?
audit13 said:
Did you confirm the bootloader before flashing?
Click to expand...
Click to collapse
No, because I had no intentions of flashing it when I tried to do a factory reset. Then after that went bad it wouldn't boot, and I don't know how to check the boatloader when a phone will only go into recovery mode.
Where did you see reference to 4.1? It's possible that the modem or baseband was 4.1 but the bootloader was 4.3.
Under about device and then Android version. The one where if you tap it a lot you get the jellybean android that pops up. It wasn't the baseband version because that's a much longer number with the model number in it.
That screen doesn't tell you the bootloader.
As I said, I didn't check for the bootloader version before I ran into trouble because I only wanted to do a factory reset and I didn't intend to flash anything. I wouldn't imagine that it would have a different bootloader than the OS version unless that can happen without any user intervention because the previous owner was only concerned with selfies and games. She certainly didn't modify anything.
I cant explain what happened. This has never happened to me after flashing about 10 phones.
I believe it has something to do with the errors that were produced while trying to do a factory reset. What bothers me is that both phones did the exact same thing. Normally I'd say it was something I did, except that I didn't do anything but put a battery in them, boot up, find lots of junk installed, and then attempt a factory reset. On the first phone, I rebooted into recovery and tried it from there. On the second phone I tried it from inside the OS. Same results on both. The phones ran fine before that.
Any advice on how to do the boot from an SD card, or how to do the JTAG thing? I've been reading a lot but the information jumps around a lot. I'm comfortable with soldering and have an IT background if that helps.
It's possible that the recovery was corrupt or the partitions were corrupt.
Whenever I factory reset a phone, I always boot into recovery to do that, not from within the ROM.
Sounds to me like you did nothing wrong.
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
audit13 said:
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
Click to expand...
Click to collapse
I don't know for sure if she had it from new. Yes, for both phones Odin said pass in the window and then it rebooted. I had walked away when Odin finished with the first phone. I came back and it was dead. The second one I watched and it showed the android with the wireframe in his guts and the progress bar which moved across, and then it just went blank.
There were error messages about the partitions when I did the factory reset IIRC. Perhaps the recovery or the partition was corrupted like you said. It's just odd that both had the exact same identical problem with the exact same results. That's why I think that it must have been something I did, except that I didn't DO anything other than initiate a factory reset.
I took an i747m and reflashed stock the Telus 4.4.2 ROM.
In download mode, you should see the green Android guy with the words "Downloading...Do not turn off target" and a blue progress bar moving from left to right.
I did not check reset in Odin. Once it finished flashing the ROM, I removed the USB cable, removed the battery, replaced the battery, and booted the phone. I the Android guy with the wire frame for a few seconds, the screen went blank, and the phone started up with the Samsung logo.
Since you were getting errors with mounting the different partitions, you may have needed to flash the PIT and PDA files but I can't really say for sure as I have never encountered this problem.
I normally verify everything before I use Odin because phones that I have been given to fix have had all sorts of weird configurations.
You'll have to try the debrick guide. of use a jtag service. You could also do what I did and that is to look for people with phones that have a damaged screen and buy they at a steep discount.
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.