Hey all, had this guy running fine for a while, ticked the wrong setting in twrp and deleted everything. Previously used Casual with no issues. This is an i605 (Verizon Note 2)
Can use ODIN3 (1.85) to get it back to stock 4.2.2. VZWAMC3. Loads, fine.
Want to unlock so I am going the route of casual.
Tried on 3 diff comps, 2 windows 1 linux. Same errors each time,
Output from the linux box is here
pastebin dot com / RhAM2YPk (sorry I can't link since new user)
It's bootlooping afterwards, gotta jig it and odin it back to stock to be useable, blah, no fun
Note also tried the root66 ROM, Odin no likey. (maybe versioning or something else?)
I have a nandroid on my sdcard if I can get this rooted/twrp installed to go back to. I was doing them daily since I had been running cyanogen nightlies.
and ypeaxp
Ran it again @ work, linux mint box. Diff cable. Same result
pastebin dot com /VnGsjTE2 (sorry still cant post url's yet)
key lines seem to be
ERROR: Failed to confirm end of file transfer sequence!
ERROR: recovery upload failed!
Ending session...
ERROR: Failed to send end session packet!
Back to Odin and reflashing stock I suppose for now. Really curious to why this won't work... is there another method I can take to this?
In my own stupidity, panic, and lack of sleep over the past day, I realized my issue.
WRONG VERSION of CASUAL for current stock rom.
I hate when it's the small oversights, but then also at the same time am happy that I was able to fix it.
CASUAL is awesome, and I owe Adam some props and likely donations. Works beautifully in linux and windows.
Last time, windows, flawless,
This time, linux, and flawless.
How is it that XDA devs can make something cross platform that WORKS and most corp coders cant...
Just updating this thread in case anyone runs into it. Don't be dumb and miss the small stuff. Saves time and frustration.
Related
Hello, I have tried everything I can find (many times) ....I had a working gtab with 1.1, have not touched it in years, wanted to load one of the new roms as apparently they are much faster now. Did a few things, 1.1 to 1.2, stock, etc....not really sure of the order or where I messed up, but now I am stuck with APX only, no recovery menu, no birds, yet I can always get to APX. No matter what script I run it always ends with a bad data error of some type: "sending file: system.img \ 18743296/125207808 bytes sentdata send failed NvError 0x120002 command failure: create failed (bad data)". I have tried 250mb, 300mb.
I feel I have messed up the partitions somewhere related to the bct? Tried format, comes up with magic mismatch.
Any ideas on what I can do next, besides use the wife's Ipad?
Fixed....
Well I finally figured out I cannot possibly be the only person in the world with this issue.....(right, I can't be)..so took a deep breath after 2 days of messing with this, found another cable, system resolved! Don't think your usb cable is good just because its new.......now on to install a rom!
gmcnitt said:
Hello, I have tried everything I can find (many times) ....I had a working gtab with 1.1, have not touched it in years, wanted to load one of the new roms as apparently they are much faster now. Did a few things, 1.1 to 1.2, stock, etc....not really sure of the order or where I messed up, but now I am stuck with APX only, no recovery menu, no birds, yet I can always get to APX. No matter what script I run it always ends with a bad data error of some type: "sending file: system.img \ 18743296/125207808 bytes sentdata send failed NvError 0x120002 command failure: create failed (bad data)". I have tried 250mb, 300mb.
I feel I have messed up the partitions somewhere related to the bct? Tried format, comes up with magic mismatch.
Any ideas on what I can do next, besides use the wife's Ipad?
Click to expand...
Click to collapse
Sound like you might have a bad download. Try this link http://teamdrh.com/DRH-Downloads/Full_Stock_NVFlash_CWM_5504_Touch.zip.
That one is already modified to expand the system partition to 250m and prep everything else. Also includes the recovery image 5504 beta 15. With this setup you should still be able to run any of the ROMs I post and later ROMs like HC all the way to Froyo. If wanting to run any of the other JB firmware you will have to use a system prep setup to expand the system to a 350m. That can be found here http://teamdrh.com/DRH-Downloads/TeamDRH_350M_Prep.zip. I would start with the first one and update your drivers and use a USB connection on your PC that is connected to the mother board and not a hub. Both packages have the updated drivers included in the package. Just guide your wizard to load them from the folder they are in.
So I'm trying to get my device back to stock so I can ship my device to someone I sold it too but somehow I'm running into issues.
I installed Terrasilent kernal and custom rom on my US 4.0 way back last spring and never had to connect my device to a computer since. Well now obviously I have to and am trying to do it off a new laptop I recently purchased.
My steps so have gone like this.
1. Downloaded and installed Samsung Drivers
2. Downloaded and installed C++ Redistrubiutable from: http://www.microsoft.com/en-au/download/details.aspx?id=30679
(I only got the bottom one. Did I need all 3?
3. Downloaded Latest Heimdall
4. Ran zadig and updated the one Samsung device that showed up
5. Ran Heimdall and loaded the pit and recovery files from this thread http://forum.xda-developers.com/showthread.php?t=1531850
But every time I get some sort of error.
The latest error being
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
After trying reinstalling drivers and such I've also ran into this error
error: failed to access device. libusb error: -12
Am I missing a very simple step? Somehow even though Heimdall won't flash anything I've also managed to get my device soft bricked.
Sadly I don't remember having such issues when I originally rooted my device and flashed it. Any ideas? I'd really love to get this device shipped out to the person it was sold to.
mewrius said:
So I'm trying to get my device back to stock so I can ship my device to someone I sold it too but somehow I'm running into issues.
I installed Terrasilent kernal and custom rom on my US 4.0 way back last spring and never had to connect my device to a computer since. Well now obviously I have to and am trying to do it off a new laptop I recently purchased.
My steps so have gone like this.
1. Downloaded and installed Samsung Drivers
2. Downloaded and installed C++ Redistrubiutable from: http://www.microsoft.com/en-au/download/details.aspx?id=30679
(I only got the bottom one. Did I need all 3?
3. Downloaded Latest Heimdall
4. Ran zadig and updated the one Samsung device that showed up
5. Ran Heimdall and loaded the pit and recovery files from this thread http://forum.xda-developers.com/showthread.php?t=1531850
But every time I get some sort of error.
The latest error being
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
After trying reinstalling drivers and such I've also ran into this error
error: failed to access device. libusb error: -12
Am I missing a very simple step? Somehow even though Heimdall won't flash anything I've also managed to get my device soft bricked.
Sadly I don't remember having such issues when I originally rooted my device and flashed it. Any ideas? I'd really love to get this device shipped out to the person it was sold to.
Click to expand...
Click to collapse
Did you installed the drivers while you were in download mode? Maybe this would solve your actual issues. Also if you used a different port, you need to reinstall the drivers once again AFAIK.
I'm writing this post to give back to the community...
I spent about collectively 9 hours trying to get my D803 to work. Was on 4.2 rooted, then went factory fresh using the LG Support Tool. Then updated to 4.4.2 using the same. Great, things work except in the stupid Bell D803 ROM the "I-won't-remember-your-wifi-settings" bug still exists (!!). I went to great lengths to try and edit the build.prop and finally was able to push.
Reboot, then all heck broke loose. Apparently it didn't like my modified build.prop.
TOP TIP: when you have a stable phone, install a custom recovery and do a backup (yes, requires root)
The phone would boot past the LG logo then a black screen with blinking green and blue. I tried many, many things like factory reset, flashing this and that. If you're reading this you'll probably be familiar... load the HTTP fake server, modify HOSTS file, run window enabler... etc. Ultimately these things either lead to a 4% fail or the usual 49% fail.
After 9 hours of futzing around I gave it to my buddy as he said "it can't be that stupid, the stock consumer tools should work". He spent about 3 hours messing about and gave up. In the meantime, I built a physical Windows XP 32-bit machine just in case the fault lies in my trying to use a VMware Fusion XP box on my Mac to do this.
Fast forward...
I'm only going to list the tools/items I used, not link them as I have no idea where they came from now. I'm sure you can Google each and see where and what they are required for.
Setup_LGFlashTool_1.5.10.1120.exe
MegaLock.dll (to, uh, "unlock" the tool above)
BIN_LGD803AT-00-V10c-RGS-CA-SEP-04-2013-32G.zip (this file is SPECIFIC for the D803 variant !!)
BELL_D803B10D_00.kdz (this file is SPECIFIC for my Bell D803 variant !!)
LGUP_8974.dll (this is EXTRACTED from the KDZ file)
General steps:
1. Install the LG Flash Tool
2. Overwrite megalock.dll
3. Download YOUR correct TOT (zipped up) file from (remove spaces): downloads. codefi.re/autoprime/LG/LG_G2
4. Unzip the TOT file from the zip and put it someplace you remember
5. Download YOUR correct KDZ file. There are various places but the EASIEST is to get it DIRECTLY from LG. There is a way to use your IMEI and plug it into a csmg.lgmobile.com URL in order to download it. Please search it.
6. EXTRACT the DZ and DLL file from the KDZ you downloaded. Please search this. I believe it was using a Python script.
7. Install the LG G2 drivers, I used: LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1-2.exe
8. Boot the phone into factory reset mode and wipe it. Search this.
9. Boot the phone into DOWNLOAD (or UPDATE FIRMWARE) mode. Search this.
10. In DEVICE MANAGER, change the LG device (under PORTS) to use port 41, then unplug and plug the phone back in.
The good part...
11. Launch the LG Flash Tool, click MANUAL, then put in the location of the DLL and TOT file from above in the right places.
12. The upper left corner box labelled COM41 should now say "READY!!".
13. Unplug the phone, wait 5 seconds, it should say waiting for connection
14. Plug it back in.
15. Should be flashing now, just wait.
Why am I writing this? It took far too long for me to figure this out. Unknowns or stumbles:
1. No one clearly said when to plug in the phone at the FlashTool screen. I tried having it plugged in to launch the tool, I tried waiting for READY!! then plugging it in then. It always just sat a 0%. I HAD to have it plugged in, get to READY!!, then replug. Maybe you need to do this as well.
2. Skip using the LG Mobile Support Tool doing the HTTP hacks etc. Just use the LG FlashTool and cut to the chase. Wasted SO much time trying different KDZ, support tools, etc.
3. MAYBE it was the VMware guest causing issues but unlikely because I got to the same stages as the physical machine... all I did different was replug it in.
4. Only ONE KDZ file got to 49%, all the others dumped me at 4% (probably citing incompatibility?). You MIGHT need to extract the DLL file from a known KDZ that works for you OR maybe the DLL file is the same across the identical hardware models (ie. Bell D803)? I don't know.
I think those are the only lessons learned but if there are any more, I'll drop them in later. I have to go install a custom recovery and find out how to modify that build.prop properly on 4.4.2...
tip dont ota on custom recovery if you do there is a fix already posted somewhere.
some fixed 49% by clearing system/data prior to flashing. Not sure, never encountered it myself.
bachera said:
tip dont ota on custom recovery if you do there is a fix already posted somewhere.
some fixed 49% by clearing system/data prior to flashing. Not sure, never encountered it myself.
Click to expand...
Click to collapse
Oh yeah. I encountered that and had to LiveCD a Ubuntu virtual machine and push the partitions... that one is straightforward to fix The PRO TIP on that one from me is to disable the notification of removable drives in Ubuntu or it will drive you nuts.
bachera said:
tip dont ota on custom recovery if you do there is a fix already posted somewhere.
some fixed 49% by clearing system/data prior to flashing. Not sure, never encountered it myself.
Click to expand...
Click to collapse
That dont fix it. Ive tried every trick and suggestion on the net and I cant find the answer . Im about to give up on having Kitkat
EDIT: I just found this . Maybe its the answer I havnt tried it yet http://forum.xda-developers.com/showpost.php?p=49724825&postcount=1747
TheAndroidGeek said:
I'm writing this post to give back to the community...
I spent about collectively 9 hours trying to get my D803 to work. Was on 4.2 rooted, then went factory fresh using the LG Support Tool. Then updated to 4.4.2 using the same. Great, things work except in the stupid Bell D803 ROM the "I-won't-remember-your-wifi-settings" bug still exists (!!). I went to great lengths to try and edit the build.prop and finally was able to push.
Reboot, then all heck broke loose. Apparently it didn't like my modified build.prop.
TOP TIP: when you have a stable phone, install a custom recovery and do a backup (yes, requires root)
The phone would boot past the LG logo then a black screen with blinking green and blue. I tried many, many things like factory reset, flashing this and that. If you're reading this you'll probably be familiar... load the HTTP fake server, modify HOSTS file, run window enabler... etc. Ultimately these things either lead to a 4% fail or the usual 49% fail.
After 9 hours of futzing around I gave it to my buddy as he said "it can't be that stupid, the stock consumer tools should work". He spent about 3 hours messing about and gave up. In the meantime, I built a physical Windows XP 32-bit machine just in case the fault lies in my trying to use a VMware Fusion XP box on my Mac to do this.
Fast forward...
Click to expand...
Click to collapse
THANK YOU!!!! I did exactly the same thing as you by improperly editing the build.prop file trying to solve the WiFi password issue. I spent the last few days with futile attempts at the KDZ method. Your method worked first time. I am now able to boot into 4.2.2.
Were you able to solve the WiFi issue at all?
Hi All, New to this forum and have not found a resolve reading the threads so if someone could correct me that would be awsome.
I am trying to un-hard brick our samsung galaxy player 5.0 intl. It attempted to boot with a flat battery along time ago and has been a brick since. i have periodically kept it charged in case one day i find a resolve.
I have been attempting to use Unbrickable Ressurector but cannot even get it to load.
Initial process:
I have installed ubuntu on a spare laptop.
Installed Java through command line and verified the install.
Downloaded Unbrickable Ressurector from: (github) downloaded as a zip file. 'hummingbird-hibl-master.zip'
changed the zip file permissions to allow executable.
Right clicked an run with Java. But nothing happens. A little bit of hard drive noise but nothing comes up.
In the threads there is mention of running the .jar file but there is no .jar file in this package. I have unzipped and searched the folders to no avail.
I have even tried renaming the zip file to .jar which yeilds the same result as above.
I think it may be that i'm simply stupid or am i missing something?
Any help greatly appreciated.
I have just tried installing java 6 instead of java 8 in case there was a compatibility issue. Set default application to Java 6 runtime. Icon pops up in side bar after double click on 'hummingbird-hibl-master.zip'
then after 14 seconds icon disappears.
Not sure what else to try. I must be missing something obvious?
SymondoR said:
Hi All, New to this forum and have not found a resolve reading the threads so if someone could correct me that would be awsome.
I am trying to un-hard brick our samsung galaxy player 5.0 intl. It attempted to boot with a flat battery along time ago and has been a brick since. i have periodically kept it charged in case one day i find a resolve.
I have been attempting to use Unbrickable Ressurector but cannot even get it to load.
Initial process:
I have installed ubuntu on a spare laptop.
Installed Java through command line and verified the install.
Downloaded Unbrickable Ressurector from: (github) downloaded as a zip file. 'hummingbird-hibl-master.zip'
changed the zip file permissions to allow executable.
Right clicked an run with Java. But nothing happens. A little bit of hard drive noise but nothing comes up.
In the threads there is mention of running the .jar file but there is no .jar file in this package. I have unzipped and searched the folders to no avail.
I have even tried renaming the zip file to .jar which yeilds the same result as above.
I think it may be that i'm simply stupid or am i missing something?
Any help greatly appreciated.
I have just tried installing java 6 instead of java 8 in case there was a compatibility issue. Set default application to Java 6 runtime. Icon pops up in side bar after double click on 'hummingbird-hibl-master.zip'
then after 14 seconds icon disappears.
Not sure what else to try. I must be missing something obvious?
Click to expand...
Click to collapse
Did you miss something? Yes, You missed the date on the OP which was DEC 2011!. The links are out of date and so are the instructions.
1. In 2011 I think maybe ubuntu 11.04/12.04 was current. So you might have trouble getting 14.04 or 16.04 to work.
2. The link for the download of Unbrickable Resurrector is not right. You are looking for a file called "UnBrickableResurrectorR36.jar" which is apparently been expunged from the internet. The current link, that is redirected to github.com, leads to the source code that will "compile" UnBrickableResurrectorR40.jar"( or whatever the lasted version was). So unless you've got some java 6 skills...
EDIT: I managed to find 1 copy of the file here:
https://www.4shared.com/file/1Gx6ZSXjei/UnBrickableResurrectorR40.html
Thanks meticulus for taking the time to reply. That got me out of a sticking point. Greatly appreciated. I know i'm trying to revive old tech but i also don't like being wasteful by just throwing it away. I hope to revive it so my daughter can use it as a ipod alternative. Here's hoping.
Hopefully i don't need any further help and this thread will help any other late comers to fixing the old galaxy player 5.0.
Thanks again.
Hi Meticulus. Progress update: Unbrickable Resurrector R40 now functional.
Connect SGP 5.0 intl.
Device recognised.
S5PC110 Detected.
Clicked : Perform Resurrection - Download Mode
Begin Resurrection Sequence
Requesting Permission to access device
Please wait......Uploading...
This is far as the process goes. Device does not go into download mode. Could i be missing something simple again?
SymondoR said:
Hi Meticulus. Progress update: Unbrickable Resurrector R40 now functional.
Connect SGP 5.0 intl.
Device recognised.
S5PC110 Detected.
Clicked : Perform Resurrection - Download Mode
Begin Resurrection Sequence
Requesting Permission to access device
Please wait......Uploading...
This is far as the process goes. Device does not go into download mode. Could i be missing something simple again?
Click to expand...
Click to collapse
1. It's been quite awhile since I used this but I believe that I used it with ubuntu 12.04 LTS. So first make sure you use that version.
2. Make sure you are NOT using virtualization software such as virtualbox or vmware. Either use a thumbdrive, dualboot, or just install ubuntu natively.
3. You man need to set permission on the USB device in udev. Sort of like this: http://ptspts.blogspot.co.il/2011/10/how-to-fix-adb-no-permissions-error-on.html
Use lsusb to find the exact IdVendor
4. Launch the file in the terminal like this: java -jar UnbrickableRessurectorR40.jar . This may* give you more output to tell what is going on.
Hi Again Meticulus. thanks for you instruction. I have managed to make some more headway from your help.
I performed a new native install of ubuntu 12.04 LTS and Java 6
Now Unbrickable Ressurector appears to work. It recognises the device and after password prompt brings up the now in download mode screen on the GUI window. Although the samsung player screen stays black.
I have now also installed Heimdall Frontend in ubuntu and in the process of learning how to use it and acquiring the correct pit file and firmware. It appears to recognise the player at this stage.
Just to refresh it is a Samsung Galaxy Player 5.0 International 16GB. Made in Korea.
I have pit file: GB70-GalaxyPlayer-16gb.pit
also G70intl.pit
I am thinking the first is a safer bet.
Firmware: G70XXKPL_CL1105219_REV01_user_low_ship_HOME.tar.md5
and: CODE_GB70KRKPG_CL762569_REV01_user_low_ship_HOME.tar
Although heimdall expects tar.gz file extensions. so i'm doing something wrong again.
I'm going to sleep on it and re approach in the morning. (I'm on the other side of the planet in good old New Zealand)
If you have any further advise to offer on correct firmware for this device any help is most appreciated.
SymondoR said:
Hi Again Meticulus. thanks for you instruction. I have managed to make some more headway from your help.
I performed a new native install of ubuntu 12.04 LTS and Java 6
Now Unbrickable Ressurector appears to work. It recognises the device and after password prompt brings up the now in download mode screen on the GUI window. Although the samsung player screen stays black.
I have now also installed Heimdall Frontend in ubuntu and in the process of learning how to use it and acquiring the correct pit file and firmware. It appears to recognise the player at this stage.
Just to refresh it is a Samsung Galaxy Player 5.0 International 16GB. Made in Korea.
I have pit file: GB70-GalaxyPlayer-16gb.pit
also G70intl.pit
I am thinking the first is a safer bet.
Firmware: G70XXKPL_CL1105219_REV01_user_low_ship_HOME.tar.md5
and: CODE_GB70KRKPG_CL762569_REV01_user_low_ship_HOME.tar
Although heimdall expects tar.gz file extensions. so i'm doing something wrong again.
I'm going to sleep on it and re approach in the morning. (I'm on the other side of the planet in good old New Zealand)
If you have any further advise to offer on correct firmware for this device any help is most appreciated.
Click to expand...
Click to collapse
".tar.md5" or ".tar" file must be flashed with Odin in Windows but those files are archives that can be opened via the Archive Manager in Ubuntu and the files extracted. As I said it's been awhile and I'm just talking from memory so do your homework but, basically each file in the archive is a raw dump of the partition. So system.img is the system partition, cache is cache and so on (zImage is kernel) and can be flash via heimdall. I am not very familiar with heimdall front end but from the Terminal, the command is something like:
"heimdall flash --system system.img" ( <---real iffy on exact syntax, something close to that.)
DO NOT FLASH PIT FILES!!! ( I have bricked my device many times and have never had to do this and you shouldn't do it unless you are sure that you have muffed up your partition table!)
Odin is available here and the drivers for windows too but the last time I used them Windows 7 was the thing so...
Techically if you can use Heimdall or Odin with any success, you are already in "Download Mode" and you do not need the Resurrector.
The Terminal command "heimdall --print-pit is a good test. If it can connect to the device and print the pit file with out error then Download mode is working and you can flash a stock ROM with ODIN and as long as it's the right one, your golden...
Hi Meticulus, Here's a quick result of a pit print:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
So I may have a bigger problem. Would that indicate a muffed partition? from what i have read elsewhere i may have a hardware failure which means RIP samsung player.
What originally bricked the device was an attempted boot with a dead flat battery. the device has never had any custom firmware flashed. Purely stock.
Will do some more research in the meantime.
SymondoR said:
Hi Meticulus, Here's a quick result of a pit print:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
So I may have a bigger problem. Would that indicate a muffed partition? from what i have read elsewhere i may have a hardware failure which means RIP samsung player.
What originally bricked the device was an attempted boot with a dead flat battery. the device has never had any custom firmware flashed. Purely stock.
Will do some more research in the meantime.
Click to expand...
Click to collapse
I can be sure but i would say yes, that does point to a partition. The only way to repair you partition table is if you can get into a custom recovery.
Your only hope is if you can flash a custom kernel:
http://www.meticulus.co.vu/p/galaxy-player-5-beanstalk-install-from.html
You can also extract the zImage from the .tar or .tar.md5 file and flash the zImage (kernel) with heimdall sort of like this:
heimdall flash --KERNEL zImage .
The kernel has custom recovery in it and if you can boot into it, you can use the partition tools to straiten yours out.
You might need this:
https://www.youtube.com/watch?v=Uzu4uDTDL5k
and you might want to read through this entire thread:
https://forum.xda-developers.com/showthread.php?t=2398120
Meticulus said:
I can be sure but i would say yes, that does point to a partition. The only way to repair you partition table is if you can get into a custom recovery.
Your only hope is if you can flash a custom kernel:
http://www.meticulus.co.vu/p/galaxy-player-5-beanstalk-install-from.html
You can also extract the zImage from the .tar or .tar.md5 file and flash the zImage (kernel) with heimdall sort of like this:
heimdall flash --KERNEL zImage .
The kernel has custom recovery in it and if you can boot into it, you can use the partition tools to straiten yours out.
You might need this:
https://www.youtube.com/watch?v=Uzu4uDTDL5k
and you might want to read through this entire thread:
https://forum.xda-developers.com/showthread.php?t=2398120
Click to expand...
Click to collapse
Thanks again Maticulus. I have been through all of the above to no avail. The last thread was interesting and tried to repeat the process there to see it the partitions were messed up.
Used adb-shell. (On Windows terminal)after installing Android devalopment suite. but Shows no connected devices. The player shows as SEC S5PC110 test B/D in device manager requiring drivers. Even though I have installed the samsung drivers.
I've also tried to use the zImage previously. Heimdall front end will only allow me to add the extracted file after adding the pit file. But in the end fails to upload the pit file.
Sorry for the low detail as I have decided to give up on this one. I appreciate your input to get me this far. You certainly went above and beyond to help and for that I thank you.
hopefully there is something in here to help someone else in a similar situation.
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!