Related
Ok im an admitted "noob" to the whole android/linux op but not technically challenged at all.. and i researched ALL the info availible before rooting my alltel samsung repp (sch-r680) supposedly its an american clone of an another "galaxy gio", think its an asian model or something... anyway, i made a very careless mistake and erased my backup and system files and now am stuck in a bootloop... i can still access download mode and clockwork recovery but ive tries to flash stock roms with odin, install zips and restore backups(that i copied to my device via usb)... but nothing works, all the nandroid.md5 files respond with mismatch errors, and when i try to flash with odin, either the file passes and is useless to fix the problem or it gives an error something like "odin multidownloader has developed an error and closing"... ive been looking into flashing with fastboot or adb, i have all the neccessary files just havent figured out how to successfully execute... oh, and im having problems running some executable files (.exe), even at the comand prompt,(which im not alll that fluent in command prompt syntax). i know this is not a very popular model, and my carrier store (alltel) is like the last one standing i think but the same model is marketed by us cellular... anyway, sorry for the extremely long message, but i wanted to provide as much info as possible, so if anyone can help id greatly appreciate it... ive been without my andoid for like a week now and seperation anxiety is starting to set in.. pls help!!!
Also, i cant mount my system in cwm or through adb... Dont know if thatll help find a solution but i know its a problem within itself...
First, I am not an expert. I cannot code, I do not produce ROMS in a kitchen. I can use google and I am determined and have learned bits. I offer what worked for me in the hope of helping others.
So, here’s the thing. Like others I went for the release version of KitKat for n8000 and by missing out the modem bit flashed it via Odin. Now the proper KitKat for n8010 comes out but it won’t update via odin, KIES is not happy either. I blame no one but me for this.
I figure it is the sboot that is the problem so I look for a way to flash without it. When I say “I figure” I mean I have put two and two together from many hours of google reading. I may be wrong but in the end I managed it.
Long story a little shorter I find Heimdall and I extracted the components from the n8010 kitkat update (I used winrar on the BTU version) and flashed them leaving out the sboot.img and tz.img bits as either would lead to failed flash. I now have a working n8010 with KitKat which under device, under settings, gives the n8010 build number and is recognised as an n8010 by kies.
It still says n8000 under download mode (due to locked sboot) but if I may get future updates via kies, as it recognises it as an n8010 and says it is up to date for now, then that works well enough for me.
Detailed instructions:
1. Download and unzip your update file of choice and extract the tar.md5 file to separate files. I used winrar but suspect 7-zip would work equally.
2. Download Heimdall (just Google it!).
3. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe.
4. Run zadig.exe from the Drivers folder of the Heimdall Suite.
5. If you get an error as follows:
The program can't start because MSVCP100.dll is missing from your computer.
This means that you haven't installed the Microsoft Visual C++ 2010 runtimes. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. Use the x86 even if you are running 64 bit Windows.
6. Put you tab into Download mode (while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC.
7. Once you’ve started Zadig.exe and connected to PC choose Options » List All Devices from the menu.
8. Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu. (If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Kies).
9. Click Replace Driver (having selected "Install Driver" from the drop down list built into the button).
10. If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this driver anyway. You may receive two more prompts about security. Select the options that allow you to carry on.
11. You will need to re-install the Samsung drivers later if you want to run kies.
12. Run Heimdall-Frontend.exe.
13. Hit the utilities tab then detect button.
14. If it doesn’t say detected in the output box it will not work. Try to repeat the above steps. Use a different usb port or a different pc.
15. Now you need to create a pit file. Hit save as and give it a name. Then hit download and it will create a pit file for you.
16. Go to Flash tab and hit browse and find the pit file you created earlier.
17. Then hit the add button. You will notice a drop down menu has appeared next to partition name. Then if you look below under Partition ID in brackets it says what sort of file it needs. So for example MD5HDR in the drop down requires md5.img. Use browse to find the relevant file from the files you extracted in step 1 and select then hit add again. Then repeat this until you have selected all the extracted files EXCEPT sboot.img and tz.img.
18. Hit start.
19. Bask in your new updated n8010 without needing kies or odin.
If you want to repeat this on another tab you can create a heimdall install package using the partitions and pit file you’ve created using the create package tab.
Now comes the question...
I've found places that offer an app for testing whether the sboot is locked (not sure how useful that is?) but several also offer a method for replacing a locked sboot. Such as this batch file:
@ECHO Restore OLD BOOTLOADER N7100!
@pause
@ECHO --- STARTING ----
@ECHO --- WAITING FOR DEVICE
@files1\adb wait-for-device
@ECHO --- Restore BOOTLOADER ---
@files1\adb push sboot.bin /sdcard/sboot.bin
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1"
@files1\adb shell rm /sdcard/sboot.bin
@files1\adb reboot fota_bl
@pause
There are others for different Samsung devices but all have the same block/mmcblk0p1 as the block to replace the sboot. And I also found a common block for the tz.img; mmcblk0p2. My question is whether this would work for the n8010, could we edit this batch slightly, grab the relevant files from a n8010 kitkat update and then have a n8010 sboot again?
Just hoping someone is either expert enough to know or brave enough to try?
I was thinking on a different aproache.
Using the leaked firmware as a guide and UK firmware. Change the sboot.bin and the tz.img on UK firm to that one on the leaked. And try to flash trough Odin.
Enviado do meu OT-995 através de Tapatalk
That may also work.
What do you think of my suggested method to replace the sboot?
jika23 said:
I was thinking on a different aproache.
Using the leaked firmware as a guide and UK firmware. Change the sboot.bin and the tz.img on UK firm to that one on the leaked. And try to flash trough Odin.
Enviado do meu OT-995 através de Tapatalk
Click to expand...
Click to collapse
azureus139 said:
That may also work.
What do you think of my suggested method to replace the sboot?
Click to expand...
Click to collapse
Your method works very well for me. However, we need to find someone willing on XDA to find a solution to revert the bootloaders to N8010 from N8000.
I am downloading the gtn7100 kitkat and will extract to check whether they are the same size. That should get us one step closer. I am still not brave enough to use adb to replace the sboot until someone more expert can comment on whether it is likley to be same address on the n8010.
YOSEFE said:
Your method works very well for me. However, we need to find someone willing on XDA to find a solution to revert the bootloaders to N8010 from N8000.
Click to expand...
Click to collapse
In a tar file isn't something like the updater script like in a flashable zip. Cause if there is we should know with that where the sboot is flashed.
that batch file won't do it
Decided to give it a try after further research.
I learned what the different commands did and I made an edit of the batch file. All seemed to go well replacing the sboot and tz but it didn't work, still showing as n8000 in download mode.
azureus139 said:
Decided to give it a try after further research.
I learned what the different commands did and I made an edit of the batch file. All seemed to go well replacing the sboot and tz but it didn't work, still showing as n8000 in download mode.
Click to expand...
Click to collapse
perhaps that can help
http://forum.xda-developers.com/showthread.php?t=1944858
Sadly that will not help. I have discovered it is because the leaked n8000 kitkat rom has a knox bootloader which cannot, as far as I can discover, be replaced. Thank you for the suggestion.
ivica81 said:
perhaps that can help
http://forum.xda-developers.com/showthread.php?t=1944858
Click to expand...
Click to collapse
secure boot key is what your looking for
From past devices with SECURE.. NOT LOCKED boot loader.
This new knox boot loader is locked.. And im assuming.. that its locked with a SBK.. Secure boot key.. We had this issue back with the acer a 500. Where we could sign and flash a custom rom. If rom / android version was same or newer then the Versions set in the Secure boot key.
EVENTUALLY Someone found a way to Turn off that sbk . but this was only to those who had not yet flashed the sbk secure boot loader. So if today someone finds a fix for this.. It will ONLY Help those not in your situation . I think PEOPLE Should start screaming at and Protesting samsung that you DO not want there sbk boot loader as default on all devices and you should be able to remove it. But i can tell you. its a waster cause. and this device is not popular enough for someone to break up a the boot loader to get the sbk algorithms . LOok up the old threads ON THE ACER A500 Tablet.. you will see its Quite similar .
SO you are Likely STUCK...
Sorry . this is why i have NOT Flashed one of these roms on my n8013.. I will NOT Be in this situation..
Well I was already out of warranty so that isn't an issue and I have it working with the proper kitkat for my device so tbh I don't know what difference it really makes. It shows n8000 in download mode and I will have to do something tricky via heimdall for any future updates, is that the only difference? Does it mean no access to custom roms as so far I've been happy to use stock and remove all bloat so that won't be too bad for me personally although it would be a real pain for some.
erica_renee said:
From past devices with SECURE.. NOT LOCKED boot loader.
This new knox boot loader is locked.. And im assuming.. that its locked with a SBK.. Secure boot key.. We had this issue back with the acer a 500. Where we could sign and flash a custom rom. If rom / android version was same or newer then the Versions set in the Secure boot key.
EVENTUALLY Someone found a way to Turn off that sbk . but this was only to those who had not yet flashed the sbk secure boot loader. So if today someone finds a fix for this.. It will ONLY Help those not in your situation . I think PEOPLE Should start screaming at and Protesting samsung that you DO not want there sbk boot loader as default on all devices and you should be able to remove it. But i can tell you. its a waster cause. and this device is not popular enough for someone to break up a the boot loader to get the sbk algorithms . LOok up the old threads ON THE ACER A500 Tablet.. you will see its Quite similar .
SO you are Likely STUCK...
Sorry . this is why i have NOT Flashed one of these roms on my n8013.. I will NOT Be in this situation..
Click to expand...
Click to collapse
As i said i never flashed that on my device. I am thinking all the issues/ benefits quarks of having the n 8000 boot loader on a non n 8000 device.. There may be NO Disadvantage unless Samsung Chooses to change how they sign there roms and so on.I just think Samsung Should Give us a way to avoid this .
so would we be best to wipe data before doing this? just still have all the n8000 icons in the top corner like data icon etc.
I did no wipes and just flashed over the top. All apps and data as before but no phone icon.
JamesEsh said:
so would we be best to wipe data before doing this? just still have all the n8000 icons in the top corner like data icon etc.
Click to expand...
Click to collapse
Any news on restoring the n8010 bootloader? Would a jtag service be able to restore it?
raducux said:
Any news on restoring the n8010 bootloader? Would a jtag service be able to restore it?
Click to expand...
Click to collapse
Nothing from me. Everything I found says no way to unlock or replace the kitkat sboot. The n7100 apparently has a way but none for the 8xxx that I have found. Don't know what a jtag is?
fail to finish
azureus139 said:
Firstly, great guide
Extremely happy you made this guide.
I'm getting stuck though at the download on Heimdall
Either getting: Initialising connection... Detecting device... Claiming interface... Setting up interface... Initialising protocol... ERROR: Protocol initialisation failed! Releasing device interface...
OR
ERROR: Failed to send data!
really wanting to get my tablet back up and running as I only had it for a few days before i tried to update it/brick it with n8000
Just wondering if you can create a package in Heimdall or upload pit files as i'm struggling to make to get through.
thanks heaps!
Click to expand...
Click to collapse
If you can't get heimdall to detect your tablet then it isn't going to flash to it either so a pit file wouldn't help you. It looks like a driver problem. I'd try uninstalling any samsung drivers and / or kies then reinstalling the heimdall ones.
keevo2481 said:
azureus139 said:
Firstly, great guide
Extremely happy you made this guide.
I'm getting stuck though at the download on Heimdall
Either getting: Initialising connection... Detecting device... Claiming interface... Setting up interface... Initialising protocol... ERROR: Protocol initialisation failed! Releasing device interface...
OR
ERROR: Failed to send data!
really wanting to get my tablet back up and running as I only had it for a few days before i tried to update it/brick it with n8000
Just wondering if you can create a package in Heimdall or upload pit files as i'm struggling to make to get through.
thanks heaps!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This driver is too tired
Thought that could be the issue as it changes every time I reinstall the usb driver. Currently too tired. Going to do a fresh windows or Linux install on my spare computer so it's fresh to go and hopefully doesn't have driver issues. Will confirm how it goes either way. Computer needed an upgrade from 7->8.1 anyway.
wifi problem
hy guys i just did that the guide said everything is working very well i m on 4.4.2 stock samsung. But the WIFI is not working. :crying: can you help me how to fix?
Hey Guys,
When I try to boot in Odin mode the tablet just boots with RECOVERY BOOTING....then hangs...
Samsung
Galaxy Note Pro
Unlocked Pic
Custom
Android
I was rooted then i wanted to flash stock and it went downhill from there. It flashed last night but wifi wasnt working. I really dont want to take it to verizon. I have revived but the three button salute doesnt let me get into download mode. Please help Its insuranced but will they cover it since it has Custom on it?
Edit: Screen is not faint and the device is working.
So reading some other threads where people encountered this problem. Two main solutions
1. bad recovery flash, it needs to be flashed again.
2. Can you still plug in the tablet and charge it? If you can do that the other recommended solution was burning the battery out until dead, basically forcing a full on restart of everything, then plugging in the device letting it recharge then trying to boot into download mode again. They say pull the battery, but since you can't do that you need to burn it down to 0. As long as you can charge your tablet you aren't lost. If you can get into download mode after trying that flash stock firmware from odin. Then start the process from step 1, clean start.
Either way, I wouldn't panic yet. Well don't panic at all. Panicking just makes mistakes and you aren't anywhere near the hopeless stage where you have to bring it back to verizon yet. I'm sure other people here will have other ideas as well and some people may have had the same problem. Just breathe. Burning the battery will give you some relaxing time lol. Pretty confident it can be fixed.
biggiesmalls657 said:
Hey Guys,
When I try to boot in Odin mode the tablet just boots with RECOVERY BOOTING....then hangs...
Samsung
Galaxy Note Pro
Unlocked Pic
Custom
Android
I was rooted then i wanted to flash stock and it went downhill from there. It flashed last night but wifi wasnt working. I really dont want to take it to verizon. I have revived but the three button salute doesnt let me get into download mode. Please help Its insuranced but will they cover it since it has Custom on it?
Click to expand...
Click to collapse
Gatsrom said:
So reading some other threads where people encountered this problem. Two main solutions
1. bad recovery flash, it needs to be flashed again.
2. Can you still plug in the tablet and charge it? If you can do that the other recommended solution was burning the battery out until dead, basically forcing a full on restart of everything, then plugging in the device letting it recharge then trying to boot into download mode again. They say pull the battery, but since you can't do that you need to burn it down to 0. As long as you can charge your tablet you aren't lost. If you can get into download mode after trying that flash stock firmware from odin. Then start the process from step 1, clean start.
Either way, I wouldn't panic yet. Well don't panic at all. Panicking just makes mistakes and you aren't anywhere near the hopeless stage where you have to bring it back to verizon yet. I'm sure other people here will have other ideas as well and some people may have had the same problem. Just breathe. Burning the battery will give you some relaxing time lol. Pretty confident it can be fixed.
Click to expand...
Click to collapse
Thats why ^^^^^^^ i love this great community because people help each other and positive feedback rather than negativity. I have modified dozens of device over the years and this device is my first big fail as of now but I will let it die. What gets me is Verizon and ATT know that locking their device makes people mad and yet they continue to do whats best for business. I someday would love to reach dev status. How would I flash the recovery without download mode?
Debrick IMG
I also have the Stock Rom decompiled and am trying to make a Debrick IMG to get the tablet to boot from SDext to get to download mode then im out of the woods but i need to find out what imgs to use. I have Win32 Disk Imager ready and this is how I saved my S3 verizon last year. I don't have download mode yet or ADB (i think) so im running out of ideas. There are a lot of awesomesauce devs out there (including you) that do amazing things for our devices. Mattlgroff saved my RAZR Maxx and Trident made the ally a great phone for its time. It might not seem sometimes especially how people act by bickering but we really do appreciate the hard work of development across the board of devices. End Story
just boots with RECOVERY BOOTING....then hangs...
--- wanted to flash stock and it went downhill from there. It flashed last night but wifi wasnt working.
Click to expand...
Click to collapse
the first one sounds so, that the recovery Image was/is the wrong one. This matched also the 2nd one : Stock, but Wifi is not working. If you flash e.g. on P905 the H3 Imagage and after that the C3 kernel, Wifi doesn't work in this status also anymore. I'll believe, you've flashed a wrong image.
To change anything / or the repair the Tab, you must have the possibility to have an access to the Tablet.
What does you've try?
Fastboot / Recovery-Menu? [This one failed -if I've understood you right]
Download-Menu?
Up to which point does your Tab start's up ? Doers you've any access?
biggiesmalls657 said:
I also have the Stock Rom decompiled and am trying to make a Debrick IMG to get the tablet to boot from SDext to get to download mode then im out of the woods but i need to find out what imgs to use. I have Win32 Disk Imager ready and this is how I saved my S3 verizon last year. I don't have download mode yet or ADB (i think) so im running out of ideas. There are a lot of awesomesauce devs out there (including you) that do amazing things for our devices. Mattlgroff saved my RAZR Maxx and Trident made the ally a great phone for its time. It might not seem sometimes especially how people act by bickering but we really do appreciate the hard work of development across the board of devices. End Story
Click to expand...
Click to collapse
Hmmm we definitely need someone with a 905 to post the partition info if you're going to try to build a debrick.img. Have you used search to see if anyone maybe already has? I only have the 900 and I was pretty sure they were different. Just glancing at this program I'm guessing you'd need boot.img since it's going to basically provide a bootloader as the phone hops from internal to external looking for a way to boot. I've never used it though so I don't want to tell you the wrong thing :x
Gatsrom said:
Hmmm we definitely need someone with a 905 to post the partition info if you're going to try to build a debrick.img. Have you used search to see if anyone maybe already has? I only have the 900 and I was pretty sure they were different. Just glancing at this program I'm guessing you'd need boot.img since it's going to basically provide a bootloader as the phone hops from internal to external looking for a way to boot. I've never used it though so I don't want to tell you the wrong thing :x
Click to expand...
Click to collapse
Now the software wont flash and there seems to be a hardware issue (my screen flickers) and it didnt last night.
Update: This device is fixed except for wifi wont initialize but this can help other users. Please lock this thread and hope it helps other people in unbricking! I love XDA and its community!
Update: This device is fixed except for wifi wont initialize but this can help other users
Click to expand...
Click to collapse
What does you'Ve done? Maybe other users have teh same issue and there are happy, if they can found a way to reanimate the Tab?
Mad07 said:
What does you'Ve done? Maybe other users have teh same issue and there are happy, if they can found a way to reanimate the Tab?
Click to expand...
Click to collapse
The Tablet has to be completely dead and then you can charge it to odin cause of the recovery booting ...... but draining the battery clears RAM and then i can get into download mode. Its still better than a 750 dollar paperweight just need to fix wifi. Its almost set up this way and takes longer to fix the device if you are kind of in a hurry. I was rooted but unfortunately have no safestrap so i could not back up my image It was in a bricked state and was corrected by troubleshooting android related problems and flashing in Odin. The only question besides the wifi problem is even though i flashed Stock firmware, my device shows up as Custom????? Any Ideas its not tripped i know that much.
biggiesmalls657 said:
The Tablet has to be completely dead and then you can charge it to odin cause of the recovery booting ...... but draining the battery clears RAM and then i can get into download mode. Its still better than a 750 dollar paperweight just need to fix wifi. Its almost set up this way and takes longer to fix the device if you are kind of in a hurry. I was rooted but unfortunately have no safestrap so i could not back up my image It was in a bricked state and was corrected by troubleshooting android related problems and flashing in Odin. The only question besides the wifi problem is even though i flashed Stock firmware, my device shows up as Custom????? Any Ideas its not tripped i know that much.
Click to expand...
Click to collapse
So the battery trick did reset it? Score! lol. I've actually had two friends have to do something similar with other android devices. So you flashed stock onto it (thank god) and now the only problem remaining is no wifi? I know we had a thread about no wifi for our specific device in the forums. Search for that. It seemed like people were able to fix it in that thread.
Gatsrom said:
So the battery trick did reset it? Score! lol. I've actually had two friends have to do something similar with other android devices. So you flashed stock onto it (thank god) and now the only problem remaining is no wifi? I know we had a thread about no wifi for our specific device in the forums. Search for that. It seemed like people were able to fix it in that thread.
Click to expand...
Click to collapse
Wifi and bluetooth and system status is custom and updating bricks and puts me back to letting it die.
Wifi and bluetooth and system status is custom and updating bricks
Click to expand...
Click to collapse
Where you can see, that Wifi and BT is custom ?
System status is also Custom on my tab ( TWRP was flashed )
At which point the update bricks? Near at the end > hiddenfile ext4 wrong ?
Which this error ( I've select the GBT - file, but the Tab was buyed in Austria > so I need the ATO ) I've triggered KNOX After download the correct FW-File, odin could flash successfully.
If you change temporary the Kernel for root, Wifi is no working , too...
updating bricks
Click to expand...
Click to collapse
If odin failed during flashing, press one time Reset in odin, dis-/ connect the USB cable from the TAB and you can continue with odin. During next flash, you received a lot of red text lines, that the progressbar indicator is not correct, but this one you can ignore. Urgent is, that odin said : PASSED at the end.
In you case, I would make direct after successfull flash -> boot into the EM Menu and initiate a factory reset
Mad07 said:
Where you can see, that Wifi and BT is custom ?
System status is also Custom on my tab ( TWRP was flashed )
At which point the update bricks? Near at the end > hiddenfile ext4 wrong ?
Which this error ( I've select the GBT - file, but the Tab was buyed in Austria > so I need the ATO ) I've triggered KNOX After download the correct FW-File, odin could flash successfully.
If you change temporary the Kernel for root, Wifi is no working , too...
If odin failed during flashing, press one time Reset in odin, dis-/ connect the USB cable from the TAB and you can continue with odin. During next flash, you received a lot of red text lines, that the progressbar indicator is not correct, but this one you can ignore. Urgent is, that odin said : PASSED at the end.
In you case, I would make direct after successfull flash -> boot into the EM Menu and initiate a factory reset
Click to expand...
Click to collapse
I had NB1 installed and it was working then i used Repair Assistant and it has recovery booting and the boot logo with Custom android. They wont cover it for insurance, i might as well just damage and pay the deductible. I have tried everything and it results in a brick.
From where is this image ND repair assistant ? The bootlogo is changed via root very easy. For that nobody needs a total ROM flash. It's only 1 zipfile.... Hopefully the repair assistant does not has make a recreate partitions....
let go out from the best case Which stock rom does you try to flash? The latest one?
Model: SM-P905V
Model name: GALAXY NotePRO 12.2 LTE
Country: USA (Verizon)
Version: Android 4.4.2
Changelist: 1810991
Build date: Mon, 10 Nov 2014 07:03:29 +0000
Product Code: VZW
PDA: P905VVRUANK1
CSC: P905VVZWANK1
MODEM: P905VVRUANK1
I didn't still know at which area Odin failed to flash
Mad07 said:
From where is this image ND repair assistant ? The bootlogo is changed via root very easy. For that nobody needs a total ROM flash. It's only 1 zipfile.... Hopefully the repair assistant does not has make a recreate partitions....
let go out from the best case Which stock rom does you try to flash? The latest one?
Model: SM-P905V
Model name: GALAXY NotePRO 12.2 LTE
Country: USA (Verizon)
Version: Android 4.4.2
Changelist: 1810991
Build date: Mon, 10 Nov 2014 07:03:29 +0000
Product Code: VZW
PDA: P905VVRUANK1
CSC: P905VVZWANK1
MODEM: P905VVRUANK1
I didn't still know at which area Odin failed to flash
Click to expand...
Click to collapse
Yes the latest build is what I flashed. I wonder if the kernel changed but right now NB1 makes it usable with no WiFi or bluetooth.
Which Rom does you mean exactly with NB1 ?
the only one, which I've found - which contains NB1 at the end is:
Model: SM-P905V
Model name: GALAXY NotePRO 12.2 LTE
Country: USA (Verizon)
Version: Android 4.4.2
Changelist: 617169
Build date: Thu, 06 Feb 2014 12:19:18 +0000
Product Code: VZW
PDA: P905VVRUANB1
CSC: P905VVZWANB1
MODEM: P905VVRUANB1
Click to expand...
Click to collapse
Why you don't try to flash the K1 Rom? [See above].
If I think about my Galaxy S3 LTE : I have the old Bootloader ( without Knox ) on the device -> if I flash the new System / Kernel without the new Bootloader, I'll have also a problem with a nonworking Wifi ...
Gatsrom said:
So the battery trick did reset it? Score! lol. I've actually had two friends have to do something similar with other android devices. So you flashed stock onto it (thank god) and now the only problem remaining is no wifi? I know we had a thread about no wifi for our specific device in the forums. Search for that. It seemed like people were able to fix it in that thread.
Click to expand...
Click to collapse
The software is flashed and notice the system sleeps and screen wont turn back on until i three finger salute. Boot Logo has no unlocked symbol but About phone displays Custom. Also Wifi/Bluetooth issue which I could not find. If i can fix the wifi and bluetooth i wont send into verizon. They should cover it, Odin mode displays 0x0.
Edit: Odin mode still displays SYSTEM STATUS: Custom even though I flashed the NB1 build. Wifi/Bluetooth still do not work. I have wiped data/ cache and rebooted the device. Towelroot didnt work previously but I will try with this build.
ok, first of all, go into the settings, developer and enable USB system debugging. Shut down the Tab, Hold The home key, volume down and Power. After that, the tab starts into the download mode, press volume + to continue. The screen changed. Connect the Tab with you running Odin ( check the task manager, that nothing from Kids is still running in the background. Select as PDA the K1 Firmware which was in the zip. Ending is tar.md5.
Check is Only Autogreboot and the F fuse(?) >>default settings are selected. Press Start and wait... In Odin you can following which Parton is now flashed. Hopefully Odin stopped with Passed and the Tab rebooted. If you've the wrong region rom, Odin failed at the hidden file ext4.
Mad07 said:
ok, first of all, go into the settings, developer and enable USB system debugging. Shut down the Tab, Hold The home key, volume down and Power. After that, the tab starts into the download mode, press volume + to continue. The screen changed. Connect the Tab with you running Odin ( check the task manager, that nothing from Kids is still running in the background. Select as PDA the K1 Firmware which was in the zip. Ending is tar.md5.
Check is Only Autogreboot and the F fuse(?) >>default settings are selected. Press Start and wait... In Odin you can following which Parton is now flashed. Hopefully Odin stopped with Passed and the Tab rebooted. If you've the wrong region rom, Odin failed at the hidden file ext4.
Click to expand...
Click to collapse
I have flashed it that way several times. The software flashing isn't the problem, its WiFi and Bluetooth jam and wiping data cache do not fix it. I have re downloaded the software and its a no go.
biggiesmalls657 said:
I have flashed it that way several times. The software flashing isn't the problem, its WiFi and Bluetooth jam and wiping data cache do not fix it. I have re downloaded the software and its a no go.
Click to expand...
Click to collapse
If Knox still triggered? Ill believe so. K1 is now the current FW?
Try after install TWRP , wipe normal and go into the adv. wipe settings to format / System and / Data / Cache etc..
Reflash K1 again.
How does it looks like Jam of Wifi / BT ? does you received a FC? only Interruption ?
Complettly Remove FRP , ie return YOUR fone to original state ie as if just bought and unregistered, without triping KNOX or any other signs Tamper switches etc being Shown!! , Current binary, official, system status = official, Secure download = enabled, Warranty Void = 0 (0x0000), AP SWREV b:1 k:0 s:0, this last bit i don't know what it is but this is the same numbers it outputted to my download screen when I first Factory Reset the fone after setting up google , making sure adb was off as OEM etc in settings, setting up a fingerprint and a 4 digit pin, and set it to activate before the fone boots.. I tried to make it as hard as i could to break, but ends up it doesnt matter anyway as all the info is in the PERSISTENCE partition, and if wiped, it thinks its never been registered, Again this comes down to security by obscurity hiding a txt file with your google details on it on a partition or anywhere just hoping no one will look there as its buried quite, well kinda deepish, is not security it laziness i forgot to dd the partition to my pc and looked to see if the info was even encrypted and what else was there in that partition as google thought it was impenetrable, just like apple does with "find my iphone" & icloud, but they are getting better am struggling with there new version, but anyway this is android here and
THIS IS HOW I DONE IT!
First Hold [Power} [HOME] and [VOLUME DOWN] all at once until a blue screen appears with stuff about non stock images et, then press [volume up], next Use ODIN.exe, which ive provided as well as every thing else needed, and flash your model version of the .tar file (included) by clicking the [BL} button on ODIN then make sure its has a tick next to it, if not click the box to tick it, then run the RUN_ME.bat file and that's that. Next just flash the STOCK version of your boot file in the way as before in the [BL] tab, sometimes a full new flash is needed via odin, but only rarely, then thats it phones like new, As in never owned before, as the script wipes the partition (PERSISTENT) that holds the username lock files.
this can be done manually as i found the files that lock the fone to the google account are in the PERSISTENCE Partition, it can be in different places per fone or model but usually in /dev/block/PERSISTENCE, or /dev/sda11 or somewhere in the /by-name/PERSISTENCE, just ls /dev/ and worm your way down till you see a PERSISTENCE then dd it by dd if=/dev/zero of=/dev/block/PERSISTENCE or wherever the partition is, simple,
if this works for youn hit hit thanks, or buy me a beer via paypal, cheers, sonnettie
Any Questions Ill answer you, Im very busy with a lot of projects just now and i just had brain surgery after been hit by a bus on a dual carriageway last year, and was in 3 hospitals in surgery for 70 hours, then a comma for six weeks,
PS, This will NOT trigger KNOX as its done at the lowest level below KNOX and before any services or apps start om the phone,
The BOOT loader you flash, all that does is start the system at its lowest level so we can run basic commands from the LINUX base of the fone, like ls, dd, df, mount, , basically like busybox when linux fails to load correctly, This is what the boot file does, first it start adb from its end then it loads only so far, not even to the point where the android flashes, it halts at the Galaxy S7, logo before the loading screen, so nothing loads at all.
The files can be downloaded from here... Files For Removing FRP, Knox Trip=NO, FRP=OFF, ALL Official!!
THIS IS PoC and some files and info to proof it, this was just to show how i was the first person do do this and not charge you for it, yes it need alterations for alternative fones if you cant figure how to do that dont just plug your fone into your pc and start pressing random buttons switches command etc again its PoC for this fone with info on "How to" with other android 6/7 fones thats all if you need a push one button flashy tool im not here for that only to help some one else do that ive done the technical part a app coder can make you a a plug and unlock tool, that was not my intention just to help and stop someone else finding this first and charging every one for it as this can be done remotely if you understand how it works using an apk but whatever........
sonnettie said:
Use ODIN.exe which ive provided as well as every thing else needed to flash your model version of the .tar file (included) the run the RUN_ME.bat file , that's it FRP=OFF , Then just flash the STOCK version of your boot file in the [BL] tab, sometimes a full new flash is needed via odin, but only rarely, then thats it phones like new, As in never owned before, as the script wipes the partition (PERSISTENT) that holds the username lock files.
this can be done manually as i found the files that lock the fone to the google account are in the PERSISTENCE Partition, it can be in different places per fone or model but usually in /dev/block/PERSISTENCE, or /dev/sda11 or somewhere in the /by-name/ folder just ls /dev/ and worm your way in till you see a PERSISTENCE and dd it by dd if=/dev/zero of=/dev/block/PERSISTENCE or wherever the files are, simple,
if this work hit thanks, cheers, sonnettie
PS this is for people that bought a fone and reset it and cant contact the owner or setup a google account on the spot and cant remember any of it, IT IS NOT to be used for STOLEN fones or ILLEGAL USES, and you should never have had to pay for this!!!!
The files can be downloaded from here... https://drive.google.com/open?id=0ByZUWMZ-VMvtMVJ1TE5memt5c0U
Click to expand...
Click to collapse
Hi
Unfortunately this will be use for illegal purposes........
You say to flash the boot file of the phone before running the bat file , why ? what boot file is that?
Do i need to be root?
If not root , will this trigger knox 0x 1 ?
mistake sorry.....
MAX 404 said:
Hi
Unfortunately this will be use for illegal purposes........
You say to flash the boot file of the phone before running the bat file , why ? what boot file is that?
Do i need to be root?
If not root , will this trigger knox 0x 1 ?
Click to expand...
Click to collapse
No no need for root to do this, and no it triggers nothing as the fone doesn't get a chance to boot while its done, hope this helps
and yes, just as the factory reset salute before FRP was, and the screwdriver, knife, car, printer, computer, even fones can be used for illegal purposes, but that NOT US, and we discourage that were helping people that as i see happening a very lot people buy a new fone set up google with anything that comes to mind cos the got a yahoo, or hotmail email, or maybe don't even use them so the just type any random sh!t into the fone thinking they will never use it, then some thing like this happens, before all you had to do was the three finger salute (factory reset) for them and try to warn them use memorable email passwords etc or even write them down in a book somewher, bad sec, but if it a 75 yr old woman coming to you every day coz she cant access here play store to get facebook, or whatever, then its better this way don't you think, with the obvious exception tell them not to use internet banking or there credit card online.
sonnettie said:
No no need for root to do this, and no it triggers nothing as the fone doesn't get a chance to boot while its done, hope this helps
and yes, just as the factory reset salute before FRP was, and the screwdriver, knife, car, printer, computer, even fones can be used for illegal purposes, but that NOT US, and we discourage that were helping people that as i see happening a very lot people buy a new fone set up google with anything that comes to mind cos the got a yahoo, or hotmail email, or maybe don't even use them so the just type any random sh!t into the fone thinking they will never use it, then some thing like this happens, before all you had to do was the three finger salute (factory reset) for them and try to warn them use memorable email passwords etc or even write them down in a book somewher, bad sec, but if it a 75 yr old woman coming to you every day coz she cant access here play store to get facebook, or whatever, then its better this way don't you think, with the obvious exception tell them not to use internet banking or there credit card online.
Click to expand...
Click to collapse
Hi Mate
why we need to flash another boot loader?
the bootloader activates ADB and only boot so far into the system before the Android Virtual Machine starts so we are running on pure linux so no KNOX or any other checkers are running and never know whats going on or happened as its as if they where in a comma at the time lol,
any other questions please ask, sonnettie
Does the latest security patch fix this flaw?
Nope still works
From what i read and what i understood, with this can you restore Knox to 0x0 from 0x1?
Thanks for posting this fix- i literally spent the last day trying to remove the frp lock off a legitimate purchase from ebay. Google has managed to close all the exploits out there on ****-tube and nothing other than paying some other programmer to do this (probably exact thing for a profit) This is why I keep coming back to xda developers. I'm not here for profit or nefarious reasons. I want my phone to work the way it's supposed to without all the bloatware and bull****. You rock and I appreciate it!
Hello,
I think no one has try this unlock method.
Because i think it cant work.
I have seen in the runme.bat there is script error at the end,
where it should be
dd if=/dev/zero of=/dev/block/...
Anyways, it is maybe just a fake when frp unlock methods was fixed?
FLash the boot file then run bat, then while running bat flash the recovery file?
First flash the recovery or the boot? Then run the bat, while running the bat flash the recovery? Please explaina little as I am having trouble with g935usa.
the boot file included in the file i left here
andrei1412 said:
From what i read and what i understood, with this can you restore Knox to 0x0 from 0x1?
Click to expand...
Click to collapse
yes u can, makes it a new fone electronically
XDALies said:
This is a complete load of bull****! The OP claims to have given all the files needed to get around the FRP, but ironically there are no files for the AT&T S7 or the SM-G930A ! If you're too stupid to bypass FRP on the AT&T Variant, just admit it!
Click to expand...
Click to collapse
look at the amount of people how have followed my instructions including ME! and it works on any android frp locked or ox1 fone , Muppet
AMAZING!!!
Finally a slution!! Thanks a lot mate! Feel better!
sonnettie said:
t FRP=OFF ,
First Hold [Power} [HOME] and [VOLUME DOWN] all at once until a blue screen appears with stuff about non stock images et, then press [volume up], next Use ODIN.exe, which ive provided as well as every thing else needed, and flash your model version of the .tar file (included) by clicking the [BL} button on ODIN then make sure its has a tick next to it, if not click the box to tick it, then run the RUN_ME.bat file and that's that. Next just flash the STOCK version of your boot file in the way as before in the [BL] tab, sometimes a full new flash is needed via odin, but only rarely, then thats it phones like new, As in never owned before, as the script wipes the partition (PERSISTENT) that holds the username lock files.
Click to expand...
Click to collapse
I just used Odin with the 930 Boot.tar file. And my phone is now in a permanent restart loop. What did I do wrong? And what do I do now to get it out of loop?
~~Fixed that problem. Still don't know what happened, but I didn't bypass FRP. My phone is sm-g930p. And I used the "G930_USA_(QUALCOMM)_BOOT" file first. Instructions were very unclear.
how to I do this to a SM-G930W8 model as i cannot get them files to work with it.
Since i am a newbie in flashing phones ...
What Zip do i need to select in Odin for the SM-930F (there are two versions of it in there both marked with "stock")
Does this work on the G930A? I assume latest update (7.1 possibly?).
Hi, I'm having a lot of troubles. My old Samsung S6 was accidentally factory reset and I did not have photo backup through google enabled. My mother died last April and this phone has many photos of her that I have not backed up anywhere else. I've been trying for days to figure out what to do, but I can't make heads or tails of a lot of the information. Some places say the phone can be rooted, some say not, and there are a lot of dubious websites offering the tools needed to root them. I don't know what to do, my phone model is SM-G920V, hardware version is G920V.07, and the build number is MMB29K.G920VVRU4CPF4.
I saw one tool, CF-Autoroot that generated a file set for me to root the phone, but it also said that the bootloader being locked could result in the phone being flashed. Can anyone please help me understand what my options are? If it's complicated, I will learn how to do it, I just need a definite direction to move in. Otherwise, I think I will keep the phone turned off and hope that someday the data can be recovered. I'm very distraught, I used this phone for a long time and a great period of memories will be lost if I cannot restore it. Photorec will not recognize the phone in either Windows or Linux, I assume because I do not have root.
EDIT: Android Version 6.0.1, security patch level June 1st, 2016, Kernel Version 3.10.61
EDIT 2: I've seen some threads talking about downgrading from 6.0.1 to 5.1.1 and then getting root with Odin and TWRP recovery. What's the likelihood any of the photos would be recoverable after all that using Photorec? I'm just looking for any way to get any of the photos. I definitely need root to get Photorec to recognize the phone at least, right? Or is there another program that would work better maybe? I've had good luck with a scrambled flash drive and Photorec in the past so I feel like that's my best option.
I think it only needed adb access if it OEM Unlocked
I have restored using only ADB from Linux
Edit: I don't know about factory reset would have permanently erase the files, I don't know..
But if you erase phone from Odin it is permanent. That is what I know