Bricked Note 2 (N7100)? - Galaxy Note II Q&A, Help & Troubleshooting

I think I might have totally broken my Note 2 and I've got no idea what to do next for the best.
Long story short, I can boot my phone into TWRP but apart from that I believe the phone is wiped. TWRP for some reason won't mount an SD Card so I cannot install a new Rom from there (which is what I would normally do). TWRP is also reporting that my phone is no longer rooted. It asks if I want to install SuperSU but this fails also.
I cant mount anything via USB-OTG either and cannot get my PC (windows 8) to see the phone either, even though I am sure it is detecting it.
Anyone got any ideas on what I should try next?

kristianity77 said:
I think I might have totally broken my Note 2 and I've got no idea what to do next for the best.
Long story short, I can boot my phone into TWRP but apart from that I believe the phone is wiped. TWRP for some reason won't mount an SD Card so I cannot install a new Rom from there (which is what I would normally do). TWRP is also reporting that my phone is no longer rooted. It asks if I want to install SuperSU but this fails also.
I cant mount anything via USB-OTG either and cannot get my PC (windows 8) to see the phone either, even though I am sure it is detecting it.
Anyone got any ideas on what I should try next?
Click to expand...
Click to collapse
if you can enter download mode, then flash rom using Odin.
See in settings of recovery what you have mounted.
You can also reflash recovery, root and flash rom to make sure it's well set up

Related

Stuck in a boot-loop

Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Atraeh said:
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Click to expand...
Click to collapse
The latest Clockwork jobby will allow you to mount the sdcard as USB drive.
Other than that, you seem to be on the right track.
^ he's right
What you want to do is first download the 5.8.4.0 version of the endeavoru CWM recovery.
reboot to your bootloader, make sure you're in fastboot and flash the new recovery img.
After you have successfully flashed the new recovery, well... go to the recovery
On the recovery, tap mounts and storage, then tap Mount USB. VOILA!!!!!
Yeah, I forgot to mention that I've already tried mounting the SD Card via Clockwork Recovery - I get an error saying "Unable to open ums lunfile (No such file or directory exists). So that doesn't seem to be an option either, unless you have an idea on how to counter this?
EDIT: Ah, I see - he's using an older version. I'll get the latest one on board and give it a go. Will have to wait a bit for the phone to charge up first it seems though. Not enough battery to do it right now .
Thanks!
And voila! The phone is operational.
Thanks a lot for the help and, I just hope I never manage to half-brick my own HOX .

Note 2 softbricked, TWRP recovery says (system/data/EFS/usb/data etc...) cant mount!

Hi guys,
New to XDA, I have a Note 2 which was getting a bit sluggish but worked fine, I rooted and custom flashed TWRP and saved a NANDROID BACKUP using TWRP to SDCARD and kept that on the desktop for safe keeping.
The phone worked fine after that for some time, Now spontaneously I woke up in the morning with the phone stuck on the samsung logo screen, so i knew it was softbricked but i cant understand how that happened.
First thing i tried apart from multiple restarts, removing battery etc, was then boot into custom recovery TWRP and try and restore from SDCARD nandroid backup. But it says EVERYTHING CAN'T be mounted!
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/modem'
E: Primary block device '/dev/block/mmcb1k0p16' for mount point '/data' is not present!
unable to mount '/data', EFS, System, cache and so forth.....
The phone was sincerely working fine and this happened seemingly randomly while asleep. Phone hadnt dropped and was connected to charger, and prior to this was restarted several times with no issues.
I have been looking at endless articles, I changed to CWM, TWRP, Philz and Stock Recovery and ALL OF THEM are unable to mount. So this does NOT seem to be a problem in the recovery. I used TWRP 2.8.0.1 for my Note 2 as well as 2.7.0.1. So I have a perfect NANDROID RESTORE on my SDCARD and DESKTOP to fix this but no way of mounting it to recovery?
Odin works fine and each time i flashed the recovery it would work fine. Is there some way of fixing it with ODIN?
Any input here would be greatly appreciated, and hopefully this helps someone else with the exact same issue.
Cheers.
the9kill said:
Hi guys,
New to XDA, I have a Note 2 which was getting a bit sluggish but worked fine, I rooted and custom flashed TWRP and saved a NANDROID BACKUP using TWRP to SDCARD and kept that on the desktop for safe keeping.
The phone worked fine after that for some time, Now spontaneously I woke up in the morning with the phone stuck on the samsung logo screen, so i knew it was softbricked but i cant understand how that happened.
First thing i tried apart from multiple restarts, removing battery etc, was then boot into custom recovery TWRP and try and restore from SDCARD nandroid backup. But it says EVERYTHING CAN'T be mounted!
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/modem'
E: Primary block device '/dev/block/mmcb1k0p16' for mount point '/data' is not present!
unable to mount '/data', EFS, System, cache and so forth.....
The phone was sincerely working fine and this happened seemingly randomly while asleep. Phone hadnt dropped and was connected to charger, and prior to this was restarted several times with no issues.
I have been looking at endless articles, I changed to CWM, TWRP, Philz and Stock Recovery and ALL OF THEM are unable to mount. So this does NOT seem to be a problem in the recovery. I used TWRP 2.8.0.1 for my Note 2 as well as 2.7.0.1. So I have a perfect NANDROID RESTORE on my SDCARD and DESKTOP to fix this but no way of mounting it to recovery?
Odin works fine and each time i flashed the recovery it would work fine. Is there some way of fixing it with ODIN?
Any input here would be greatly appreciated, and hopefully this helps someone else with the exact same issue.
Cheers.
Click to expand...
Click to collapse
It is possible that your Nandroid Backup is corrupt. It happens. Also, as you tried everything, I think you should flash fresh stock rom via odin.
Press thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
It is possible that your Nandroid Backup is corrupt. It happens. Also, as you tried everything, I think you should flash fresh stock rom via odin.
Press thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi ceomaverick,
Thanks for replying so fast, I may have not explained clearly but, the NANDROID BACKUP should be fine, its on the SD but cant be seen by any of the Recoverys (TWRP,CWM,stock,Philz) because nothing is able to MOUNT. So whether or not the nandroid backup is corrupt doesnt matter because we cant use it yet, as first problem is mounting to use the custom recovery restore.
Thanks for the suggestion about the Stock ROM , I have been downloading that for the past few hours! (XME-N7100XXUFNI4-20141020155451.zip) haha! That is what I will try next via Odin, just not sure how to do it safely. I will try and google and article for re-flashing stock rom via odin to make sure i tick all the correct boxes. If anything works will be back to update.
Cheers
P.s If anyone is interested in looking for this phones Stock ROM I found it here:
samsung-updates.com/device/?id=GT-N7100 (Select the one for your country/region)
the9kill said:
Hi ceomaverick,
Thanks for replying so fast, I may have not explained clearly but, the NANDROID BACKUP should be fine, its on the SD but cant be seen by any of the Recoverys (TWRP,CWM,stock,Philz) because nothing is able to MOUNT. So whether or not the nandroid backup is corrupt doesnt matter because we cant use it yet, as first problem is mounting to use the custom recovery restore.
Thanks for the suggestion about the Stock ROM , I have been downloading that for the past few hours! (XME-N7100XXUFNI4-20141020155451.zip) haha! That is what I will try next via Odin, just not sure how to do it safely. I will try and google and article for re-flashing stock rom via odin to make sure i tick all the correct boxes. If anything works will be back to update.
Cheers
Click to expand...
Click to collapse
Well, no hassle really. ODIN 3.09 does a great job. Just dump your file in AP tab and start after MD5 is verified. You should be fine. Welcome.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Well, no hassle really. ODIN 3.09 does a great job. Just dump your file in AP tab and start after MD5 is verified. You should be fine. Welcome.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Bad news, Odin failed halfway through. Was able to boot back into download mode thankfully. But after rebooting again, seems the phone is now HardBricked. Meaning it wont even turn on.
Not sure what options are left now (if any). Anyone know what to do with a Note 2 hardbrick (apart from use it as an expensive door wedge).
Cheers
the9kill said:
Bad news, Odin failed halfway through. Was able to boot back into download mode thankfully. But after rebooting again, seems the phone is now HardBricked. Meaning it wont even turn on.
Not sure what options are left now (if any). Anyone know what to do with a Note 2 hardbrick (apart from use it as an expensive door wedge).
Cheers
Click to expand...
Click to collapse
This should not happen unless the cable or the usb ports are faulty. ( or if u have not followed the instructions correctly )
Anyway,
Can u still go to download mode? If yes, try a different cable and flash.
If no, use a USB jig to revive your phone. Ebay has them in plenty. With this you might get into download mode.
Also, are u flashing the correct firmware?
I have flashed custom ROMs n number of times without a single instance of failure.
Best of luck.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
This should not happen unless the cable or the usb ports are faulty. ( or if u have not followed the instructions correctly )
Anyway,
Can u still go to download mode? If yes, try a different cable and flash.
If no, use a USB jig to revive your phone. Ebay has them in plenty. With this you might get into download mode.
Also, are u flashing the correct firmware?
I have flashed custom ROMs n number of times without a single instance of failure.
Best of luck.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi again,
Yes, I can fully appreciate why you would say that, from what I see ODIN is very straight forward and unless you do something totally (silly), like jiggle the cable or do something midway it should not hardbrick. Therefore it makes sense you suggesting the cable is faulty, but it seemed to copy over 32GB of data seemlessly in one go. Although i will change the cable as a precaution as there is a slight cut.
When I say hardbricked, I mean hardbricked as in no recovery and no download mode, and no display whatsoever no matter what you do.
[UPDATE] Okay, the strangest thing happened. After a whole day of charging the phone, sometimes trying it on for luck, hoping something would happen. I went to the doctors and came back, and oddly enough the screen had life!!! Yes, this gets bizarre, I repeat a clearly hardbricked phone resurrected back to life with a screen showing ("A firmware upgrade encountered an error, please retry with kies") or something like that, so overjoyed with this sign of life I carefully put it into download mode and its now waiting.... But before I try Odin again, I think I will take a leaf from Ceomavericks suggestion and get a brand new cable from another samsung phone and use that this time.
By the way Ceomaverick, last time i just tried to flash to stock rom using AP, and kept autorebook and Ftime checked.
This time I am seeing on a thread to do the following, please advise (given that my TWRP doesnt mount anything at all).
It says do this: from: http://forum.xda-developers.com/showpost.php?p=43760271&postcount=22
Open ODIN, and check Re-Partition, Nand Erase All, Auto Reboot and F. Reset Time. Uncheck all other boxes. Click the PIT button and select the PIT file appropriate for your device (16GB or 32GB). Click the PDA file and choose the Stock Rom you downloaded. Press start and wait.
File Type: rar PIT_t03g_0907_16GB.rar - [Click for QR Code] (899 Bytes, 84 views)
File Type: zip BOOTLOADER_N7100.zip - [Click for QR Code] (1.03 MB, 75 views)
click start.
If everything goes well, the process should succeed and the phone should reboot. Don't wait for the phone to boot into android. Immediatly boot into recovery, factory reset the phone and wipe cache. Reboot to Android.
Now, if everything worked well, your phone should boot into Android. And then sort out the sleep of death issue.
I think I will wait for some feedback before doing this and just enjoy that my phone is mysteriously back in download mode, perhaps a hardware issue......
Another thread reading http://www.theandroidsoul.com/unbrick-restore-samsung-galaxy-note-2-gt-n7100/
Cheers
UPDATE:
Now that we are back to softbrick, I tried download mode and ODIN again, this time it fails right near the end. Last time it failed somewhere in the middle. So it seems to randomly fail and this is with the brand new USB Sony PS4 Cable. I ditched the worn out samsung cable because of the first fail. So twice its failed, but at different points. If it doesnt hardbrick again this time I suppose I will keep repeating till it passes.
For now just a straight rom flash, not sure if i should repartition with the before mentioned PIT Files and bootloader etc. Wont do that unless im told.
Thanks
Attached (Fail Image)
the9kill said:
UPDATE:
Now that we are back to softbrick, I tried download mode and ODIN again, this time it fails right near the end. Last time it failed somewhere in the middle. So it seems to randomly fail and this is with the brand new USB Sony PS4 Cable. I ditched the worn out samsung cable because of the first fail. So twice its failed, but at different points. If it doesnt hardbrick again this time I suppose I will keep repeating till it passes.
For now just a straight rom flash, not sure if i should repartition with the before mentioned PIT Files and bootloader etc. Wont do that unless im told.
Thanks
Attached (Fail Image)
Click to expand...
Click to collapse
Good news is you can visit download mode.
Ok. Alternative.
Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom
If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )
Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick.
If all above fails, it has to b a hardware issue.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Good news is you can visit download mode.
Ok. Alternative.
Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom
If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )
Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick.
If all above fails, it has to b a hardware issue.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi ceomaverick!
Just going to highlight what you said with a few questions please.
"Good news is you can visit download mode. " - Yes, and once I tried to flash it for the second time it got hardbricked round 2. So somehow me flashing it gives it a seemingly temporary hardbrick. That was some hours ago and still no way to turn it on or get any sign of life, just like yesterday before it miraculously came to life again. Which since it has happened once I am guessing it will come back to life again as i followed the exact same procedure as before but Odin failed much later on into the process rather than halfway through.
"Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom" - Okay I had Philz before I will reflash it when it comes up and i suppose search for a note 2 touchwiz rom. Philz as before wont be able to mount anything though, even sim card. As i did this prior none of them, TWRP, Philz or CWM can mount anything. So even if i have the ROM file i wont be able to use it on SD if the SD doesnt mount, but i can try it through Odin?
"If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )" - I suspect this is the case hence not mounting, so do I use that PIT file and select Re-Partition in Odin to resolve that?
"Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick." - Good idea, while the hardbrick is waiting to resurrect (LOL), I will start a download.
"If all above fails, it has to b a hardware issue. " - Again something I suspect, from forum could be this dreaded eMMC "insane samsung chip" problem which is as far as i know a 16gb internal SD? If so, perhaps there is a way to put in a 16gb SD and edit boot to mount from there as internal instead from the eMMC? Sorry if thats way out there, but i read something like this once.
Appreciate the help, waiting for it to spring back into life
the9kill said:
Hi ceomaverick!
Just going to highlight what you said with a few questions please.
"Good news is you can visit download mode. " - Yes, and once I tried to flash it for the second time it got hardbricked round 2. So somehow me flashing it gives it a seemingly temporary hardbrick. That was some hours ago and still no way to turn it on or get any sign of life, just like yesterday before it miraculously came to life again. Which since it has happened once I am guessing it will come back to life again as i followed the exact same procedure as before but Odin failed much later on into the process rather than halfway through.
"Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom" - Okay I had Philz before I will reflash it when it comes up and i suppose search for a note 2 touchwiz rom. Philz as before wont be able to mount anything though, even sim card. As i did this prior none of them, TWRP, Philz or CWM can mount anything. So even if i have the ROM file i wont be able to use it on SD if the SD doesnt mount, but i can try it through Odin?
"If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )" - I suspect this is the case hence not mounting, so do I use that PIT file and select Re-Partition in Odin to resolve that?
"Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick." - Good idea, while the hardbrick is waiting to resurrect (LOL), I will start a download.
"If all above fails, it has to b a hardware issue. " - Again something I suspect, from forum could be this dreaded eMMC "insane samsung chip" problem which is as far as i know a 16gb internal SD? If so, perhaps there is a way to put in a 16gb SD and edit boot to mount from there as internal instead from the eMMC? Sorry if thats way out there, but i read something like this once.
Appreciate the help, waiting for it to spring back into life
Click to expand...
Click to collapse
If the firmware from other region fails, then find pit file for 16gb to flash. If that too fails, I think your phone needs hardware repair.
Sent from my GT-N7100 using Tapatalk

Note 2 OS not installed error

Hi, I'm trying to erase my old note ll to pass it along to a friend who's in need of an upgrade but have a problem, turn it on and it just forever stays stuck in the note 2. Have twrp 2.8.1.0 on it and when I tried to do a wipe of any kind or factory reset, I get fails of it being able to mount anything, tried doing a kies emergency firmware recovery and doesn't detect the phone, tried though Skipsoft unifide toolkit and same, cant get it to detect the phone to redo it. Tried though twrp with a rom but it can't see the 16gb card at all. Any help with possibly getting to work would be greatly appriciated, thanks!
So any updates if anyone might possibly know?
there are several solutions.
1.use odin to install a rom.
2.reinstall the recovery. i think there is something wrong with it.
952599993 said:
there are several solutions.
1.use odin to install a rom.
2.reinstall the recovery. i think there is something wrong with it.
Click to expand...
Click to collapse
Hard to use odin when it wont pick the phone up or windows wont pick it up so I can do anything to it via odin or twrp wont see a micro sd card so kinda screwed to do such sadly :/

n910v unlocked boot, twrp, twrp reboots on any rom install

so i followed the recent bootloader unlock, i have the retail in developer mode, i got twrp installed, this i where it gets messy, it went into a bootloop, so i did a wipe on the cache and davk cach, didn't work. even pulled the battery, so i tried the format. same problem, did work, so i did a wipe again which i think i really broke it when i wiped all but the sdcard, so now, NO OS. so i'm trying to get files to reflash stock roms, i found downloads to the stock files btw, currently downloading.
so, i have twrp
no backup (i'ma idiot lol)
no OS installed
bootloader is confirmed to be in developer mode
can't get phone to access fastboot. via adb
only recovery and download avaible
[edit, i can move files onto my sd card by using another phone to move files]
so do i continue with trying to use idon to flash stock rom onto the phone? will twrp still be installed? and will i keep my developer unlocked booloader?
twrp is v2.8.5.0
(been working on this for about 14 hours now)
FIXED!!
ok, so i found a stock recovery file, md5.tar, i'll post a link below.
i used odin, put phone into download mode, connected with odin running as administrator.
selected the file i used in the AP button, (had to wait awhile for it to check md5, doesn't respond during that time)
it failed. so i pulled phone in battery and tried to turn on recovery, it sent me to the download screen and said the verizon update failed. tried to reinstall rom again. pulled battery. said same thing.
i reflashed the TWRP i was using with odin, doing the AP button with it too.
[[It will say failed on deviced and in odin]]
phone now boots up.
[btw the temp root i did was kingroot]
http://forum.xda-developers.com/devdb/project/dl/?id=12450
here is the original post for what i was doing
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
the two walk throughs i found
1. http://forum.xda-developers.com/note-4-verizon/general/howto-converting-retail-note-4-to-t3358957
2. http://www.techtimes.com/articles/152037/20160421/modder-unlocks-verizon-galaxy-note-4-bootloader-heres-how-to-do-it.htm
the stock recovery( reason for old version is because a few can update from this one)
http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_146187538272120&key=f0a7f91912ae2b52e0700f73990eb321&libId=inkoi1eq01000n4o000DLb61t4tis&loc=http%3A%2F%2Fforum.xda-developers.com%2Fnote-4-verizon%2Fdevelopment%2Ffirmware-firmware-kernel-modem-recovery-t2942937&v=1&out=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292&ref=https%3A%2F%2Fwww.google.com%2F&title=%5BFirmware%5D%20%5BOfficial%5D%20Firmware%20%2F%20Kernel%20%2F%20Mo%E2%80%A6%20%7C%20Verizon%20Samsung%20Galaxy%20Note%204&txt=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292
this is the main page to find the stock roms
http://forum.xda-developers.com/note-4-verizon/development/firmware-firmware-kernel-modem-recovery-t2942937
i may have put the wrong title
dragont4 said:
i may have put the wrong title
Click to expand...
Click to collapse
Try adb push worked for me
axeldiks1 said:
Try adb push worked for me
Click to expand...
Click to collapse
for moving files right?
fixed!!
dragont4 said:
for moving files right?
Click to expand...
Click to collapse
Yes just download a rom and flash it after you push it to your storage
dragont4 said:
so i followed the recent bootloader unlock, i have the retail in developer mode, i got twrp installed, this i where it gets messy, it went into a bootloop, so i did a wipe on the cache and davk cach, didn't work. even pulled the battery, so i tried the format. same problem, did work, so i did a wipe again which i think i really broke it when i wiped all but the sdcard, so now, NO OS. so i'm trying to get files to reflash stock roms, i found downloads to the stock files btw, currently downloading.
so, i have twrp
no backup (i'ma idiot lol)
no OS installed
bootloader is confirmed to be in developer mode
can't get phone to access fastboot. via adb
only recovery and download avaible
[edit, i can move files onto my sd card by using another phone to move files]
so do i continue with trying to use idon to flash stock rom onto the phone? will twrp still be installed? and will i keep my developer unlocked booloader?
twrp is v2.8.5.0
(been working on this for about 14 hours now)
FIXED!!
ok, so i found a stock recovery file, md5.tar, i'll post a link below.
i used odin, put phone into download mode, connected with odin running as administrator.
selected the file i used in the AP button, (had to wait awhile for it to check md5, doesn't respond during that time)
it failed. so i pulled phone in battery and tried to turn on recovery, it sent me to the download screen and said the verizon update failed. tried to reinstall rom again. pulled battery. said same thing.
i reflashed the TWRP i was using with odin, doing the AP button with it too.
[[It will say failed on deviced and in odin]]
phone now boots up.
[btw the temp root i did was kingroot]
http://forum.xda-developers.com/devdb/project/dl/?id=12450
here is the original post for what i was doing
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
the two walk throughs i found
1. http://forum.xda-developers.com/note-4-verizon/general/howto-converting-retail-note-4-to-t3358957
2. http://www.techtimes.com/articles/152037/20160421/modder-unlocks-verizon-galaxy-note-4-bootloader-heres-how-to-do-it.htm
the stock recovery( reason for old version is because a few can update from this one)
http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_146187538272120&key=f0a7f91912ae2b52e0700f73990eb321&libId=inkoi1eq01000n4o000DLb61t4tis&loc=http%3A%2F%2Fforum.xda-developers.com%2Fnote-4-verizon%2Fdevelopment%2Ffirmware-firmware-kernel-modem-recovery-t2942937&v=1&out=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292&ref=https%3A%2F%2Fwww.google.com%2F&title=%5BFirmware%5D%20%5BOfficial%5D%20Firmware%20%2F%20Kernel%20%2F%20Mo%E2%80%A6%20%7C%20Verizon%20Samsung%20Galaxy%20Note%204&txt=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292
this is the main page to find the stock roms
http://forum.xda-developers.com/note-4-verizon/development/firmware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
I'm glad that you fixed it, but I just wanted to say what I think your problem was so that other people can fix it with a little less pain.
The bootloader unlock writes files to your sd card during the process. That's why the instructions state to use an SD card that you can set aside later. If you leave that SD card in the phone when you boot, you will bootloop. Simply removing the SD card and putting in another one will work. You can also remove the SD card, format it, and put it back in.
ssj4gogeta2003 said:
I'm glad that you fixed it, but I just wanted to say what I think your problem was so that other people can fix it with a little less pain.
The bootloader unlock writes files to your sd card during the process. That's why the instructions state to use an SD card that you can set aside later. If you leave that SD card in the phone when you boot, you will bootloop. Simply removing the SD card and putting in another one will work. You can also remove the SD card, format it, and put it back in.
Click to expand...
Click to collapse
Yeah I was thinkong about that. I had pulled the sd card right after due to boot loop. Think it had to do with the sd card. I messed a step up I believe there at the end.
Sorry for the late reply guys

[Resolved] Almost bricked: N5120 & USB Issues

Expert advice needed please. This is a puzzle that someone might enjoy solving.
Although I have a fair bit of experience with flashing, I tried to flash my 8.0 for the first time and it has dramatically failed. It was probably my fault - not an uncommon story.
What is less common is that I am struggling to figure out how to undo the damage I've done. What's really making this difficult is that no computer recognises the device as USB any more so I can't use Odin, Kies, etc to repair or return to stock. I have tried everything I can think of to deal with the USB issue, the usual cable, driver, port nonsense. I don't think the USB problem is Windows now.
I suspect one of these things may have happened:
The USB port just went bad coincidentally during this flash process (charge, no data). I have ordered a new port but it will take weeks to arrive.
Has the device come out of Developer/USB debugging mode somehow? I can't tell because I can't boot to an OS.
I wonder if the ROM flash has corrupted the firmware the deals with USB - is that possible? Where is the devices USB drivers located? Is it in the bootloader, something like BIOS?
I'm suspicious of the bootloader, as the screen is weirdly corrupted now when I turn on or reboot the device - fuzzy white lines rather than a logo - but that disappears when OS tries to load, or I go into Recovery/Download.
I actually did do a backup of the original ROM to the SD card; but restoring it doesn't work, just produces an endless Samsung boot, even if I then wipe and reset.
I can get into Download mode, and a Recovery (Philz for N5120) but since I can't connect to the devise with USB in any way, it's very hard to get the Recovery to flash anything new and useful. I did put my SD Card in another phone and copied over the stock ROM zip from Samsung, but it refuses to flash - I think because it doesn't like Philz Recovery? I can't think how to replace Philz Recovery with another by flashing, without USB.
I may have to wait to replace the USB port, but I fear that won't fix it. Until then, I can only think of one other thing to try, and that is to copy a ROM onto the SD Card through another phone, and try to flash it. Lineage doesn't flash, and nor does the stock zip I got from Samsung. Would anything else work?
Can I flash an alternative recovery from within the recovery? Philz only lets me flash zips, not img or tars.
So it's quite a mess, but if anyone has a brilliant idea of how to get out of this, I'd love to hear it.
THANK YOU if you have a genius idea.
So after a few days of working on this, I did manage to resolve it, and I thought I'd just add a note about how I escaped this obscure problem.
The device went bad because I stupidly flashed an incompatible Recovery to the device and somewhere between doing this, backup and restoring and flashing, it corrupted mostly everything including something in the bootloader.
Oddly enough, the solution seemed to be to mess up the Recovery even more by flashing something even more random - it seems this provoked the device into restoring its own basic Recovery. Using this to wipe and reset the device somehow enabled Download mode's USB interface to start working again so I was able to use Kies to return to stock, which repaired everything including the bootloader.
Finally, I flashed the correct Recovery for this device, and then managed to flash the ROM I wanted. A happy ending to a stressful story; the device now works better than it ever has done before.

Categories

Resources