Database Info

dead bootloader what to do next

I've got a dead bootloader. My device doesn't upgrade thru SD and not with USB. can somebody please help me because i realy don't know what to do. My device is dead for almost 3 weeks now
[edit]
Even my backup on SD doesn't load. And this happend after i downgrade the radio version of the well know greek rom
[/edit]

nobody?
Is there a solution to flash only the bootloader?

I think you need to add some more info, if anyone should have a chance to help. For example what happened when it died - how and why? What happens if you remove the battery cover, replaces it and turns on the device? Text on screen, like USB or Serial? Have you tried uploading ROM from different PCs?
The more info you provide, the more likely it is that someone recognizes your situation from own experience and can provide some help.

HBK said:
I think you need to add some more info, if anyone should have a chance to help. For example what happened when it died - how and why? What happens if you remove the battery cover, replaces it and turns on the device? Text on screen, like USB or Serial? Have you tried uploading ROM from different PCs?
The more info you provide, the more likely it is that someone recognizes your situation from own experience and can provide some help.
Click to expand...
Click to collapse
You are totaly right.
I have update my frvice with the wrong greek rom and now i have the 15 sec reboot thing.
When I startup my device he ends up the bootloader and the only way to get the device booting to windows is remove the battery cover. But the her reboots again after the 15 seconds.
In the bootloader i tried to load my backup with the SD card but nothing happens. I also tried to load a ROM with MaUpgradeUt_NoID but nothing happens. I only get empty version thing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If i use the regular MaUpgradeUt and change the file change.bat for the xda3nbftool I get a error "error 201: get device data error".
I also tried to backup my device with the wrong ROM on it, to look at the header but nothing happens (romupdate.exe).
So my conclusion is that my bootloader is dead. Please correct me when i'm wrong but if this is the case how can i correct my bootloader.

When you unplug your Magician from the USB cable, what do you see?
If you see (with the backlight OFF) "Serial v1.00" or similar, thats a WORKING bootloader.
Make sure you have Active Sync DISABLED (right click the taskbar icon, click "Connection Settings..." the uncheck "Available by USB".
You should then plug in the USB cable and it should change to "USB v1.00" or similar.
Your PC may detect the connection as new hardware - that is a good sign that you have Active Sync disabled.
Let the New Hardware Wizard do it's thing, then re-run the upgrade setup and it should work.
If not, you've got BIG problems.

guess I'm in big trouble
The only thing i can do, is trying a different pc without ASync. On the current pc i'm working on, USB in activesync is disabled.
Are there any posibilties to reload (rebuilt, update) Bootloader.
Can somebody please help me.

The bootloader is built in as it's own ROM, and I've never seen a utility that can make it writeable. I doubt you've destroyed your bootloader, but that doesn't help you - sounds like you'll have to bite the bullet, act dumber than you are, and return it to the manufacturer for a repair - and probably pay for the privilege.

KevinL said:
The bootloader is built in as it's own ROM, and I've never seen a utility that can make it writeable. I doubt you've destroyed your bootloader, but that doesn't help you - sounds like you'll have to bite the bullet, act dumber than you are, and return it to the manufacturer for a repair - and probably pay for the privilege.
Click to expand...
Click to collapse
:shock:
But isn't it strange that if you can't destroy it, it doesn't work anymore? And isn't there somebody who had the same problem?

Before you give up, try this:
Try using another USB cable.
I have experimented many times to realise that the upgrading process does require matching with the right cable.

I noticed that in the screenshot you posted, there is no info on what the device will be upgrade to! I could be wrong, but this may well mean that your device is incompatible with the ROM you are trying to upload.
Try downloading another ROM and give it a go. The best thing would be, if you can find one made specifically for your brand, ie Qtek, I-mate or whatever, and DON'T patch it. Just let the original installer do the job...

Talents said:
Before you give up, try this:
Try using another USB cable.
I have experimented many times to realise that the upgrading process does require matching with the right cable.
Click to expand...
Click to collapse
I'm using the cable that came with my device so that can't be wrong. But i could give it a try.
HBK said:
I noticed that in the screenshot you posted, there is no info on what the device will be upgrade to! I could be wrong, but this may well mean that your device is incompatible with the ROM you are trying to upload.
Try downloading another ROM and give it a go. The best thing would be, if you can find one made specifically for your brand, ie Qtek, I-mate or whatever, and DON'T patch it. Just let the original installer do the job...
Click to expand...
Click to collapse
There isn't a orignal rom fot the dutch T-mobile MDA. And if you use a original installer, it uses ActiveSync. And i can't boot windows because it restarts after 15 seconds so I can't use ActiveSync.

Why can't you use an original ROM updater, if you have the Greek resetting ROM installed? I believe a lot of us has done so without any problems, including me. I don't remember precisely what I did, but it was no problem whatsoever. Most likely I just entered bootloader mode first, to keep the Magician from resetting...

HBK said:
Why can't you use an original ROM updater, if you have the Greek resetting ROM installed? I believe a lot of us has done so without any problems, including me. I don't remember precisely what I did, but it was no problem whatsoever. Most likely I just entered bootloader mode first, to keep the Magician from resetting...
Click to expand...
Click to collapse
I really tried everything but without any results. I realy don't know why i can't use the original ROM updater.

I have the similar problem, but mine one doesnt even start windows. It always go into the bootloader mode and stays there. I try upgrading it, but it gives me communication errors.

Do this
This is what you do.
Disconnect your JAm from USB
Go from your PC , ACTIVESYNC > FILE > CONNECTION SETTINGS > remove the check mark for ALLOW USB CONNECTION TO THIS DESKTOP COMPUTER
Now connect your JAM to your PC again via USB, this time active sync should not start since you have disabled USB
Now double click on the installer file of the original ROM and you should be good to go
After Reset , enable USB ,
Go from your PC , ACTIVESYNC > FILE > CONNECTION SETTINGS > Put a check mark for ALLOW USB CONNECTION TO THIS DESKTOP COMPUTER

MDA dead
I have tried.... it's not responsing as it should be.

[Q] Is my Galaxy S i9000 Bricked?

Okay so i had my phone rooted for fun and had no original purpose of installing CM7 on it before i read about a thread that displayed that it was a safe method to do according to what was wroten.
The phone (Galaxy S i9000) 2.2.1 Android was however, what i think is "bricked".
The phone starts with a simple picture showing me a phone with a dot-frame going to a triangle (warning sign) and further to a computer screen. Does this mean that the phone is bricked or is this something else?
The phone does not respond to:
Adb (android-sdk) throught CMD (windows 7 32 bit)
Kies
Odin
Droid Explorer
Android Control 1.3
The phone was originally modified with Odin 1.7 and failed after pushing the ROM into the phone. According to what i did, i did everything correct according to what was written in the explenation.
Please answer as quick as possible, otherwise i will try to get out the warranty which i doesn't even have anymore.

This screen means in fact that you are "nearly bricked" but some kind of emergency system is running what should act like the download mode (as I know it from my SGT). I had similar problem and after a bunch of work I found out that it was the USB driver from Samsung. A simple click in the Samsung Kies Software to re-install drivers helped me and I was able to normally flash a new Kernel, Rom, whatever. I guess you have a sync software as well (as well Kies?!), or try uninstalling drivers manually. Might work. May be worth a try.
Edit: Even with broken drivers it seemed that it was working with Kies... sync (with comlications, broke my calendar app after restarting tab after sync), storage mode, everything but no adb and such.
Sent from my GT-P1000 using XDA App

I know tried to:
Re-install Kies completelly
Removed drivers (manually)
Turned of the phone: ripped the battery out
Put it back in
Re-installed Kies (no phone connected)
Kies 2.0 Successfully installed
Re-install drivers throught kies
Checked that the phone was off and repeated step: 3
Put the usb cable in and begged to the god of nerds
Profit? No...
Kies didn't even find any device that it could try to connect to. Neither did any of above written softwares. The pc cant communicate with the phone.
Tried: 3-button-combo: lots of times!!
Adb prints: No device found
Odin: No device
Kies: No device
DroidExplorer: No device
Note that i live in Europe.

Guess you have a nice 450€ brick then... but as I am more a semi-noob than a semi-pro I am not qualified to tell you this as a shure fact... just an opinion...
send from my SGT with Overcome...

I contacted the company that sold my phone, got the number for Samsung Support, they redirected me to the company "Mobilbyrån" which will re-install and make sure my phone starts working as usual for 45 £. All thought i could done it with a jig on my own, but i rather trust a professional company to do this for me in exchange for my warranty (billing only guilty if warranty denied).
According to "Mobilbyrån" or translated "Phone Agency" this is a ordinary errand and that it's highly possible that this will go on my warranty that is still guilty for atleast 8 more months.
Solution for my problem would be to:
1. Build a Jig to hardware boot the phone into download mode
2. Enter Odin and push a new rom inside (preferebly a stock (android))
3. flash kernel (could be done before 2?)
4. Profit

I guess there is no way, even for Samsung, to find out if there was a third party Rom etc is installed as device refuses to do anything. You are only f*** up if they are still able to read out current data somehow... but 45£ is really a fair deal...
send from my SGT with Overcome...

Sucks to hear that about your phone. I have a similar model and I managed to CM7 working. I followed a tutorial on this website and I semi-bricked it too at first although I've never had the same problem as you regarding Odin not being able to locate the phone.
Can you tell me the steps you took in trying to flash CM7 on it?

Also, refer to this topic to see if it can be of any help: clicky

It was when i were to use Odin the second time.
I managed to flash the speedmod kernel into the original Android ROM (stock). I also managed to install one of the zips that were to be installed throught recovery. But after this (when connecting to Odin) and this was the step where only one of the checkboxes (F.Reset Time i think).
So i made this and the Odin 1.7 told me: "Failed" or such. And i then got paniced, i disconnected the phone since i was so frightened something had gone bad, the phone was turned of and i reset the battery (in and out) and started the phone to notice that image (as told above).
Now i thought: Yeah, lets just reset the phone throught recovery and were kind of happy by the thought of it. So i tried to access it with the 3-btn-combo but as i just remembered is that in Europe this is patched to be removed.
So i thought, lets send a adb shell to the phone throught Android-spk and i connected the phone and sent the command: Adb wait-for-device, nothing happened and the phone couldn't be found by above said softwares.
So i thought: "Hmm... this isn't good"... So i started googling for what reason this could be and i believe it's called "Semi-bricked", that is "Almost" bricked phone.
So i were sad, called Samsung Tech support and they told me to contact "Mobilbyrån Stockholm" who were a tech repair support, they wanted either 45 £ or my warranty insurance if i wanted the phone fixed. I thought... yeah right, so i sent my phone to the company and i am now waiting for what they are about to do with it.
I suppose a jig would work, thought no one i know got one and i have poor skills at constructing electrical or related components so i put up a thread (like this one) at Sweclockers.com and found a guy that had one which he could lend for me, super, just have to wait and see what happens.
I suppose this "Jig" method could work, but will the computer really notice my phone as a device? It doesn't do that now, thats why i am asking.
At all moments i used Terminal for Android phones (throught market: Android Terminal) by sending commands (since 3-btn-combo didnt work):
> "Su" <- needed for Superuser allowance for controlling the phone
> "Adb reboot recovery"
> "Adb reboot download"
And the phone starts with this picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, in that correct order.

[Q] ADB not recognizing phone on USB when its booted android, fine in recovery

Hey everyone, basically just what the title says. I plug it into the computer via USB, and ADB will not see the device when it's booted into Android. However when I boot it into recovery, it sees it fine.
I'm running Cyanogen 9 for a rom and TWRP for recovery.
Booted into android:
C:\Users\Michael>adb devices
List of devices attached
Booted into recovery:
C:\Users\Michael>adb devices
List of devices attached
b3fe68e1 recovery
I've tried installing drivers, deleting drivers, reinstalling drivers, rebooting, countless times now. Samsung's own software Kies won't even recognize the phone.
I am able to use ADB over wifi with ADB Wireless.
C:\Users\Michael>adb devices
List of devices attached
10.0.0.99:5555 device
Oh, and I can turn on USB Storage and access the filesystem with no problems.. so that works fine.
Am I going crazy or has someone else had this same problem? Thanks everyone.

Sorry for the silly question but have you enabled it in settings? That may or may not help you:thumbup:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I should have posted that in my original thread.. but yes I have it enabled. I tried having ADB over network enabled just to see if it would help.. but it did't.

Is "USB Debugging" in the phone (inside Android) checked ? check this option and see..
PS:sorry if it is enabled ... ROM problem ? did adb work on stock ROM ?

Yep it is enabled. It did not work with the stock rom either and the only reason I know that is because my wife just got the same phone yesterday and I noticed it wasn't working while trying to root it.

Start all over again ...
Uninstall all drivers for the device and kies..
Install adb and USB driver for the phone and try again ...
You seem to have a software problem (a driver issue) somewhere around your PC (are you on Mac or Windows ?)

mahanddeem said:
Start all over again ...
Uninstall all drivers for the device and kies..
Install adb and USB driver for the phone and try again ...
You seem to have a software problem (a driver issue) somewhere around your PC (are you on Mac or Windows ?)
Click to expand...
Click to collapse
+1
try on another comp and c what happens, 2 phones cant be both screwed up so it must b comp

Yeah I agree it must be something to do with Windows. I will try installing the drivers and such on a computer at work on Monday and see what gives.
In the mean time I uninstalled everything and rebooted. Then I downloaded the drivers from Samsung's website, from here:
http://downloadcenter.samsung.com/c...27_GS_II_Skyrocket_USB_Driver_v1_3_2200_0.exe
I also read this post:
http://forum.xda-developers.com/showthread.php?t=1415051
and the #2 article points to: ATT_i777_GS2_USB_Drivers.zip
So I tried installing that too. Still nothing.
I took a couple screenshots during the process, maybe it will raise a red flag to one of you guys because I certainly can't figure this out.
When I plug in my phone, the "Android" device is what comes and goes. I've tried updating the drivers for that and pointing them to the Samsung drivers directory, just says it can't find them.
I admit to still being new around the whole android development thing, but with Windows I'm pretty proficient, I just can't figure out what I'm missing.

Just out of curiosity, why do you need to access adb with the phone not in recovery? You can do push pull commands through adb even if phone is in recovery

yoft1 said:
Just out of curiosity, why do you need to access adb with the phone not in recovery? You can do push pull commands through adb even if phone is in recovery
Click to expand...
Click to collapse
If super user is installed yes you can pull or push even in Android...But if not rooted it's only done while in recovery...

y do u need to use adb, i have returned to stock many times, so i installed cwm many times, all the roms r rooted, so w/cwm and root explorer i have not needed to use adb myself

vincom said:
y do u need to use adb, i have returned to stock many times, so i installed cwm many times, all the roms r rooted, so w/cwm and root explorer i have not needed to use adb myself
Click to expand...
Click to collapse
Well if you ask me I wouldn't trust root and i would modify things using recovery and adb..but that's just me..

mahanddeem said:
Well if you ask me I wouldn't trust root and i would modify things using recovery and adb..but that's just me..
Click to expand...
Click to collapse
k, but r u not installing any custom roms, as far as i know they are all prerooted, or u just need root todo ur own stuff

Personally I just like being able to have access to use adb. I can still use it over wifi using "adb wireless" so it's not a complete loss -- but for some reason the fact that the usb isn't working is just bothering me.
I'm not going to spend much more time fighting with it.. I'm sure it has something to do with the windows and the drivers.

mmerlina said:
Personally I just like being able to have access to use adb. I can still use it over wifi using "adb wireless" so it's not a complete loss -- but for some reason the fact that the usb isn't working is just bothering me.
I'm not going to spend much more time fighting with it.. I'm sure it has something to do with the windows and the drivers.
Click to expand...
Click to collapse
i agree its win7 and drivers

Hey I know this thread is a week old or so, but I just wanted to let you know I found the problem. The problem was actually the Cyanogenmod ROM I had installed.
I was having a few other unrelated problems with that rom so I decided to try SkyICS, and low and behold.. I can now access adb via usb.
Just wanted to put the solution forward and maybe it will shine light on someone else's problem.
Thanks again to everyone for all their help.

mmerlina said:
Hey I know this thread is a week old or so, but I just wanted to let you know I found the problem. The problem was actually the Cyanogenmod ROM I had installed.
I was having a few other unrelated problems with that rom so I decided to try SkyICS, and low and behold.. I can now access adb via usb.
Just wanted to put the solution forward and maybe it will shine light on someone else's problem.
Thanks again to everyone for all their help.
Click to expand...
Click to collapse
Not exactly a solution though, in that Sky ICS is still a TW-based ROM (as in, based off the stock ROM) and not an AOSP-based ROM like CM9 or AOKP.
I also had this issue. The problem was in fact a Windows driver issue though, even though I had installed them already. When I went to Device Manager it would always show up as generic "Android" device with no driver under "other devices". I right-clicked it, Selected "Update device drivers" and then I believe there was an option to select drive from existing installed drivers. I'm on my linux partition right now so I forget what the precise option dialogue was, but it was a separate option from the "Browse my computer" option. From there it opened up a long list and I scrolled down and found one of the Samsung entries listed. I believe it was Samsung Electronics Co. Ltd. (there were others like SAMSUNG in all caps, etc.). I then selected the driver from the list within that Samsung group and ADB worked again.

[Moto G: 1st Gen. LTE - XT1045] Blank screen altought functional.

First of all, thank you for reading my post.
I'll try to point out what is going on right now iwith the phone (never saw it happen, ever).
Phone boots but shows a blank (black screen with faded light in the corners) after booting.
After several tries, found out that the 4G is on and receiving notifications (LED is blinking waiting for my response ) and I'm receiving calls nonetheless, so it is working but I can't use the screen.
The screen IS FINE, the boot shows up properly, the fastboot menu shows up properly, sometimes the icons and widgets shows up where they should be, the "Shut down" button shows up properly.
What seems to be the issue is that the upper tray with the time, data, and other things, and the down one with the "◁ ⭘ ▢" menu doesn't shows up AT ALL, so I just receive a blank screen.
Also, the computer isn't finding the phone even if it is connected through the USB cable.
I'm acessing the "Whatsapp" app in the computer right now, which requires the phone to be online and with a internet connection, meaning that the apps are functional and something really weird is happening.
The phone was working fine until last afternoon, just blanked moments after I got out of my house (when I first noticed the issue).
So... anyone willing to crack heads with me trying to figure out what the hell is happening here?
I'll provide pictures soon.
Thanks in advance!
:highfive:
EDIT1: seems to show this "Unfortunately System UI has Stopped" from time to time.
EDIT2: https://youtu.be/AS-wv0NB-g4 (recorded the issue) the 58s shows what i'm talking about.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Most likely a firmware issue
xtragen said:
First of all, thank you for reading my post.
I'll try to point out what is going on right now iwith the phone (never saw it happen, ever).
Phone boots but shows a blank (black screen with faded light in the corners) after booting.
After several tries, found out that the 4G is on and receiving notifications (LED is blinking waiting for my response ) and I'm receiving calls nonetheless, so it is working but I can't use the screen.
The screen IS FINE, the boot shows up properly, the fastboot menu shows up properly, sometimes the icons and widgets shows up where they should be, the "Shut down" button shows up properly.
...
Also, the computer isn't finding the phone even if it is connected through the USB cable.
...
EDIT1: seems to show this "Unfortunately System UI has Stopped" from time to time.
EDIT2: https://youtu.be/AS-wv0NB-g4 (recorded the issue) the 58s shows what i'm talking about.
Click to expand...
Click to collapse
Most likely a firmware issue - may be a corruption has developed or could be an incompatible app update (Google Play Services or your launcher?) . Are you rooted? You haven't indicated what ROM you have installed (Stock, custom ...?). Is the recovery stock or custom? Can you enter recovery? Does everything look as it should in recovery? If custom, do you have a recent backup and have you tried running it? The 1045 is the US version I believe - are you sure it's not a 1040 (Canada/Brazil)?
Your best bet may be to install/flash another ROM, either stock or custom. Check out lost101's or vpnair's threads for stock firmware for your phone - they've done an excellent service by providing these ROMS and they are great. I've used both at different times to overcome some issues - may be the best way to go at this stage.
Good luck --- S.

Something caused and error in your firmware, you have to do the following:
1.- Try to backup your files. See if you can connect it to the PC and explore the files from there.
2.- Once backup is done, you have 2 ways:
A) Unlock bootloader, then flashing TWRP recovery, then installing a custom ROM like CyanogenMOD or AOSP.
B) Search and download the stock firmware file, extract the files, and then flashing it to your phone using mfastboot excecutable.
You can find the files and the info here in XDA thread, just do it carefully and read instructions.
If you can't find something say it and I can help, but won't spoonfeed you.
Good luck.

sdembiske said:
Most likely a firmware issue - may be a corruption has developed or could be an incompatible app update (Google Play Services or your launcher?) . Are you rooted? You haven't indicated what ROM you have installed (Stock, custom ...?). Is the recovery stock or custom? Can you enter recovery? Does everything look as it should in recovery? If custom, do you have a recent backup and have you tried running it? The 1045 is the US version I believe - are you sure it's not a 1040 (Canada/Brazil)?
Your best bet may be to install/flash another ROM, either stock or custom. Check out lost101's or vpnair's threads for stock firmware for your phone - they've done an excellent service by providing these ROMS and they are great. I've used both at different times to overcome some issues - may be the best way to go at this stage.
Good luck --- S.
Click to expand...
Click to collapse
Stock and yes, 1045.
I've fixed the issue by restoring the phone through the fast boot (but lost all my data because I couldn't create a backup at all).
Case closed, thanks.

moralesnery said:
Something caused and error in your firmware, you have to do the following:
1.- Try to backup your files. See if you can connect it to the PC and explore the files from there.
2.- Once backup is done, you have 2 ways:
A) Unlock bootloader, then flashing TWRP recovery, then installing a custom ROM like CyanogenMOD or AOSP.
B) Search and download the stock firmware file, extract the files, and then flashing it to your phone using mfastboot excecutable.
You can find the files and the info here in XDA thread, just do it carefully and read instructions.
If you can't find something say it and I can help, but won't spoonfeed you.
Good luck.
Click to expand...
Click to collapse
I'll migrate to the Oneplus 3 soon, but just so you know, I'll root the phone later on, couldn't find the cause of the problem and had to wipe the phone in order for it to work, so that's it, case closes. Thanks.

Good to know ...
xtragen said:
Stock and yes, 1045.
I've fixed the issue by restoring the phone through the fast boot (but lost all my data because I couldn't create a backup at all).
Case closed, thanks.
Click to expand...
Click to collapse
If you run into the issue again at any point, your apps and some data can be backed up to your Google account. Additionally, it is worth rooting your phone and installing Titanium Backup (free) available on Play Store to back up all your data. Once rooted, make sure you backup your phone through recovery and copy the contents on your phone over to your computer from time to time, particularly the recovery backups and the Titanium backups. If you haven't created backups on your computer of all your phones folders in the internal and external divisions on your phone through a USB connection, another solution, in the event you lose USB, is to take out your SD card, insert it in a card reader and create matching folders for both internal and external (SD Card) on you computer and copy all the contents over directly from the card.
Takes a little time but backups can save your ass when needed.
S.

[update] Finalllly !!!!! Root Nougat S6 Verizon

Finally I Get Root On S6 Verizon with nougat :laugh: :laugh:
Edit For those didn't work with them use this
https://forum.xda-developers.com/ve...al/rom-offical-nougat-pre-rooted-rom-t3718155
There Is a Proof In Attachments
My Rom DQD1
*Do It AT YOUR OWN RISK!* I am not responsible for ANY damage to your device
Edit :
A Video Proof And How To Do
In Description Of Video I add link to my rom
To Root You Will Need The Following Files :
G920V_ENG_ROOT_B4_ 7.0 , Root Files and Odin In The Attachments
First Extract G920V_ENG_ROOT_B4_ 7.zip
Flash G920V_ENG_ROOT_B4_ 7.0.tar with odin in AP
After Reboot make Sure You enabled usb debugging go to Settings and tap on About Phone. Tab Software Info Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it
Plug Your Device To Pc
Now Extract S6Root_Unroot_SU_2_79.zip
Plug your phone into the computer
Enter The Folder S6Root_Unroot_SU_2_79 And Double Click On root.bat
If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wait for minute your phone will reboot automatically
Your Phone Will reboot 2 time on 3 will boot
Every Time You will reboot your device it will reboot 2 time on 3 will boot because we have loocked bootloader
Dont Forget To hit Thanks Button
sorry For My Bad English

where is the proofs?
Dude.... and, where is the proofs? Wich nougat version did you use? Some screenshot? I dont know but a root for this phone sounds really amazing and surprising.

NerdTronik said:
Dude.... and, where is the proofs? Wich nougat version did you use? Some screenshot? I dont know but a root for this phone sounds really amazing and surprising.
Click to expand...
Click to collapse
You Are Right I will Post ScreenShot

NerdTronik said:
Dude.... and, where is the proofs? Wich nougat version did you use? Some screenshot? I dont know but a root for this phone sounds really amazing and surprising.
Click to expand...
Click to collapse
I Added Proof In Attachments Check them

Ok, I have a problem with the adb, I tried many times but it still freezing and my cellphone screen too, I searched in the internet many ways to mount the system partition as read and write but all failed. Im thinking that the problem is the nougat version, I have the J1 and Im downloading the D1. Pst, the drivers and the cables are ok, I used another adb codes and they worked.

Seems like it only works on Qd1, so if have updated QI1 or QJ1, got to flash back to Qd1 to get it to work
...

I flashed DQD1 via Odin and after that, I flashed the .tar, but it still freezing my screen, I tried first without flashing the .tar because after flashing the firmware, the custom logo appeared. But again, the adb process failed, itsn freezed like the other but was unable to copy the su.img
---------- Post added at 07:06 PM ---------- Previous post was at 06:13 PM ----------
I did the same process that you made, so, I don't know why this happen, can you please assist this?? The phone doesn't matter, I just want to prove if this really work. I'll be amazed if this really do.

I´m facing the same problem on my device as @NerdTronik , just frezes when try to remount system as rewritable.. No succes as yet and I'm on Qd1 with the same kernel version.. Dont know How you Got to succesfully Remounted the system..

Another one stuck scratching my head with the phone locking when the batch script gets to the first adb shell mount command. The flash to DQD1 (from here, all 4 files) went fine. Flashed the new boot image without issue, reboot reflects custom image. Enabled debugging, connected with ADB, but that mount would be the final thing that would occur. Hoping this is just something we need clarified in the instructions.

Ok for all of your problem tonight i will make a youtube video learn how to root with the proof of it ☺?

Thanks for the root! Tell me, after I get the root of what custom firmware I can put? I understand you only need the development of verizon?

I did a Google for the the boot image file name and came across this link:
http://www.techzai.com/eng-root-file-samsung-android-7-nougat/
NOTE: I accessed this via Google's cache, and with NoScript plugin in Firefox. The firewall I was accessing through blocked the site for a reason... unsure if that could be that it isn't safe, work just didn't want me going there during business, etc. Go at your own risk.
But one thing that was noted in those instructions was to not only enable USB Debugging, but to also enable OEM Unlock in the developer options.
The thread for the S7 (which I think would apply but we just need to use the later released S6 boot image) mentions disabling secure startup. https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Might have time to play around with this more during the coming weekend, but maybe @faw_wal or another member will get additional info before then.

Don't work in my phone

So has any one else been able to confirm this as a working method?

DonaldAnderson said:
So has any one else been able to confirm this as a working method?
Click to expand...
Click to collapse
@DonaldAnderson
I was made a video about method but from begin when i flash the reactivation lock was on and now it's locked if you want a video with a proof i can post it for you and tomorrow i will post the full video do you want a proof video now ?

faw_wal said:
Finally I Get Root On S6 Verizon with nougat :laugh: :laugh:
There Is a Proof In Attachments
My Rom DQD1
*Do It AT YOUR OWN RISK!* I am not responsible for ANY damage to your device
To Root You Will Need The Following Files :
G920V_ENG_ROOT_B4_ 7.0 , Root Files and Odin In The Attachments
First Extract G920V_ENG_ROOT_B4_ 7.zip
Flash G920V_ENG_ROOT_B4_ 7.0.tar with odin in AP
After Reboot make Sure You enabled usb debugging go to Settings and tap on About Phone. Tab Software Info Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it
Plug Your Device To Pc
Now Extract S6Root_Unroot_SU_2_79.zip
Plug your phone into the computer
Enter The Folder S6Root_Unroot_SU_2_79 And Double Click On root.bat
If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
wait for minute your phone will reboot automatically
Your Phone Will reboot 2 time on 3 will boot
Every Time You will reboot your device it will reboot 2 time on 3 will boot because we have loocked bootloader
Dont Forget To hit Thanks Button
sorry For My Bad English
Click to expand...
Click to collapse
Don't you think your omitting a step??, we all follow each step you pointed in the instructions and got the same problem, devices just freezes when execute the root.bat

faw_wal said:
@DonaldAnderson
I was made a video about method but from begin when i flash the reactivation lock was on and now it's locked if you want a video with a proof i can post it for you and tomorrow i will post the full video do you want a proof video now ?
Click to expand...
Click to collapse
I think that it will be nice, I'll be waiting for it in a few hours. We just want to solve the errors, exactly the mounting system partition process.

can you tell me how to do that? when i double click root.bat my homegreen freezy?
can you tell me how to do that? when i double click root.bat my homegreen freezy
motorec said:
Thanks for the root! Tell me, after I get the root of what custom firmware I can put? I understand you only need the development of verizon?
Click to expand...
Click to collapse

I was doing a research and found this thread with the same problem as us ,seems like its knox that blocking the system remount.https://forum.xda-developers.com/att-galaxy-s6/general/root-att-samsung-g920a-s6-g925a-s7edge-t3564637

DDwhite said:
I was doing a research and found this thread with the same problem as us ,seems like its knox that blocking the system remount.https://forum.xda-developers.com/at...ot-att-samsung-g920a-s6-g925a-s7edge-t3564637
Click to expand...
Click to collapse
Oh nice, it's just seems impossible until somebody find the method to write in the system partition, in the thread you posted here, there was a man saying that we need to flash or do something before run root.bat, he didn't checked before but, sounds like a development.
http://rootjunkysdl.com/files/?dir=Gates/DeBloater