Database Users

Read BEFORE flashing!!

Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.
Terminology, the differences in my opinion.
Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.
Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.
Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.
1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.
3 Methods.
Method 1: (ADB - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold Volume Up + Volume Down + Power
Method 3: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons (from i9000 just down, don't touch the power button)
Plug in the USB cable and continue holding both Volume buttons
If not, use designgears fix. http://forum.xda-developers.com/showthread.php?t=812434
2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.
Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:
Then open a command prompt and type,
C:
CD tools
Then issue adb commands.
adb reboot, adb reboot download or whatever command you need.
Of course make sure your phone is connected via USB and debugging is enabled.
Here's another method for using adb.
1) start-> run-> sysdm.cpl
this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.
2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.
http://wtfokc.com/sef****/sysdm-1.gif
3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:
http://wtfokc.com/sef****/sysdm-2.gif
4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.
http://wtfokc.com/sef****/sysdm-3.gif
5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.
3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.
Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.
NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.
http://forum.xda-developers.com/showthread.php?t=841512
Here's another thread about the USB Jig method.
http://forum.xda-developers.com/showthread.php?t=819551&highlight=USB+jig
If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.
****Disclaimer****
This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.
I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.
This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.
Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.
Just my 2 cents, take it or leave it.
Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.

+sticky
excellent write up. a must-read for anyone even thinking about flashing

Original Post updated to add my information

bobbylx said:
ADB reboot download is nice, but if you are stuck at ATT logo
Click to expand...
Click to collapse
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.
If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.
Steps
1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.
Mileage may vary but should work.
This has saved me a few times.

STICKY
Sent from my SAMSUNG-SGH-I897 using XDA App

Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.
I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.

bulletproof1013 said:
STICKY
Click to expand...
Click to collapse
+1
This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
Sent from my SAMSUNG-SGH-I897 using XDA App

This thing is getting buried in the BS posts....BACK TO THE TOP!
definitely sticky

Bump Bump Bump
Great Info

Updated original post with extra info.

Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.

Thanks, great info.

FWIW........
I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.
One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.
Thanks for the post, my vote for sticky as well.

+1 sticky
Sent from my SAMSUNG-SGH-I897 using XDA App

Moving this to the top. More questions in QA that can be helped by reading these tips first.

I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.
The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.
Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).
This will ensure your USB connection is stable enough for long, error free transfers to the phone.
Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.

Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.

Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!

thanks for the reminder
there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!
another good reason flashing stock with odin before flashing new rom

I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.

Problem root galaxy s 2

I m trying to root my new galaxy s 2 i9100 with this way.http://forum.xda-developers.com/show....php?t=1075278
i follow all the steps but i have a serious problem.
in step 8. "Click root and wait for it to finish. Install Busybox and all that good stuff." the SuperOneClick bugs.
this is all tha i get in my screen:
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
2820 KB/s (585731 bytes in 0.202s)
OK
chmod psneuter...
OK
Running psneuter...
please help!!

Do it again and follow the instructions .
- Make sure your device is in USB debugging mode: Settings -> Applications -> Development -> USB debugging
- Reboot your device into download mode: Turn the device off, then power it on again by pressing and holding VolumeDown + Home + Power simultaneously. You will know when you are in download mode, it is really obvious
- Start ODIN
- Connect the device to your computer using USB
- Wait a few seconds, the ODIN screen should show you that a device is now connected
- Make sure that in ODIN NOTHING is checked, except the "Auto reboot" and "F. Reset Time" checkboxes. Press the "PDA" button, and select the "XWKDD_insecure.tar" file.
- Press "Start". ODIN you should now be flashing the kernel, and the device should reboot.
- Wait until the device is rebooted, and while still being connected over USB, start SuperOneClick, and press ROOT.
- Reboot the device
- Done !
jje

JJEgan said:
Do it again and follow the instructions .
- Make sure your device is in USB debugging mode: Settings -> Applications -> Development -> USB debugging
- Reboot your device into download mode: Turn the device off, then power it on again by pressing and holding VolumeDown + Home + Power simultaneously. You will know when you are in download mode, it is really obvious
- Start ODIN
- Connect the device to your computer using USB
- Wait a few seconds, the ODIN screen should show you that a device is now connected
- Make sure that in ODIN NOTHING is checked, except the "Auto reboot" and "F. Reset Time" checkboxes. Press the "PDA" button, and select the "XWKDD_insecure.tar" file.
- Press "Start". ODIN you should now be flashing the kernel, and the device should reboot.
- Wait until the device is rebooted, and while still being connected over USB, start SuperOneClick, and press ROOT.
- Reboot the device
- Done !
jje
Click to expand...
Click to collapse
I ve done all this but in the step 8 is the problem.
it's the second time that i done it.

Try closing Odin before running superoneclick.

Is debugging mode on or off .
jje

JJEgan said:
Is debugging mode on or off .
jje
Click to expand...
Click to collapse
is on here is two images.
The one when i run SuperOneClick and the second from the phone.

Can you post the steps you are taking to root .
Like install xxxx via Odin
Phone set at XX
steps 1 , 2, 3 , 4 etc from the beginning .
jje

JJEgan said:
Can you post the steps you are taking to root .
Like install xxxx via Odin
Phone set at XX
steps 1 , 2, 3 , 4 etc from the beginning .
jje
Click to expand...
Click to collapse
Finally i found the problem.
The kernel that was with the same name wasn't the same.
ouffff!!!
Thank you very much man!!

im having this problem too, maybies ive flashed a wrong version of the kernal tho this is the link to it.
http://forum.xda-developers.com/attachment.php?attachmentid=581915&d=1304094698
im running a new from the box yesterday s2 gingerbread 2.3.3 uk 3network
gt-I9100 Baseband I9100NEKD5
It says kernal version [email protected] #2 (tho i have flashed the above file)
I have followed all tuts to the tee
Help would be appreciated

warrent2 said:
im having this problem too, maybies ive flashed a wrong version of the kernal tho this is the link to it.
http://forum.xda-developers.com/attachment.php?attachmentid=581915&d=1304094698
im running a new from the box yesterday s2 gingerbread 2.3.3 uk 3network
gt-I9100 Baseband I9100NEKD5
It says kernal version [email protected] #2 (tho i have flashed the above file)
I have followed all tuts to the tee
Help would be appreciated
Click to expand...
Click to collapse
Maybe is wrong kernel.
The name is the same but i don't know something goes wrong.
Flash with this kernel and you will be allright.
http://forum.xda-developers.com/showthread.php?t=1056334

Thanks for the quick reply,
thats the same file i flashed. I re-downloaded the file from the link you posted and flashed again in Odin. Same result I can confirm the phone is in usb de-bug, the phone was turned off and started in the download mode (black screen) I got pass ok in Odin. The phone restarted afterwards but i get the same. When the program gets to this stage it locks up and has to be ended by task manager. Im running windows 7 x64 pc with i7850 processor ddr3 ram..
on the tut the file is called XWKDD_insecure.tar inside the rar file on the post its called zimage with no extension, i had to manually add the .tar to get odin to view it.
([email protected]) Running psneuter...
Any suggestions?

warrent2 said:
Thanks for the quick reply,
t
on the tut the file is called XWKDD_insecure.tar inside the rar file on the post its called zimage with no extension, i had to manually add the .tar to get odin to view it.
Any suggestions?
Click to expand...
Click to collapse
Why did you extract a tar file to make a tar file the instructions are to Flash XWKDD insecure .tar . as PDA through Odin
Long guide (for beginners)
- Download the attached ODIN file and extract the .zip file
- Download the attached XWKDD, but do NOT extract the .tar file
jje

cheers m8 ure a star, the file was associated with winrar and i didnt realise that had a .tar ext, jumped the gun a lil. Thanks to the lad who posted earlier it worked first time leats this post go tme registered on here great forum!

warrent2 said:
cheers m8 ure a star, the file was associated with winrar and i didnt realise that had a .tar ext, jumped the gun a lil. Thanks to the lad who posted earlier it worked first time leats this post go tme registered on here great forum!
Click to expand...
Click to collapse
You were very instructive!!!

warrent2 said:
cheers m8 ure a star, the file was associated with winrar and i didnt realise that had a .tar ext, jumped the gun a lil. Thanks to the lad who posted earlier it worked first time leats this post go tme registered on here great forum!
Click to expand...
Click to collapse
so no problem at all!!

Hey guys , I rooted my SGS2 with XWKDD_insecure.tar and superoneclick.
Everthing worked fine.
But after a while I found out, that I couldn´t make any videos with the device´s camera. All new recorded vids couldn´t be played. Message "unrecognised file type".
So, I decided to get some other ROM. I wanded to flash the litening 2.0 Rom and flashed it with odin.
But no flash changed my device. Yesterday I had thousands of konversations with experts from a german android forum. noone could held me.
Every odin flash seemed to finish correctly with PASS. But after reboot, my device always has the same state, the same kernel version, all installed apps after my rooting were gone, messages, images... all were gone, except these I had on my device before the rooting I did.
If I install e.g. CWM Manager and select the action "boot into recovery mode", I only can see the Options "reboot now", "install update from sd", "wipe data" and "wipe partition".
All data saved by my device, doesn´t stay on it, after i rebooted it.
It looks like after every boot, my device loads a special recovery point, like system recovery on e.g. Win XP.
Anybody an idea?

Nobody here who can help me with this problem? ...

Hello Humphrey,
when you boot into recovery, you can see ' update.zip' , usually that is cwm. Rom manager installs update-zip before you can use rom manager. Install update.zip via rom manager just incase that update-zip is not cwm, unless you know it is. When you install update-zip, via recovery and it comes back as unable to verify zip, then you are not rooted.
The cwm will allow you to format the caches and system, delvik and battery and then allow you to install a complete rom with a rooted kernel.To be quite honest, Oden could brick your phone because you are using 2 hardwares, computer and phone. I have found it easier to download a zipped rom to your sd card and use cwm to flash it. Remember to format everything I said but not usb or sd. I have found Designgears Cognition 1.13 rom, not 1.15, to be ideal. I also use Zeam desktop, which I find ideal. Cognition is already rooted. Rom manager has glitches, so I don't use it to reboot into recovery or anything else but to look at roms, which I don't download via rommanger. Also, I'm fed-up with downloading stock roms and then having to find a rooted rom and using Odin.
I hope you find this useful.
Adrian
Sent from my GT-I9100 using XDA Premium App

[Tutorial] Rooting the Vibrant with KB5 Update

Okay, first and foremost, by posting this tutorial I am not taking any responsibility if you brick your phone. This worked for me, and it should work for all US based Vibrant (3G) T959 models with the latest 2.2 update (KB5).
NOTE: Rooting and/or installing another recovery WILL void the warranty.
What you will need...
1. SuperOneClick v2.1.1
2. Cmenards's OverStock Kernel with ClockworkMod Recovery
3. Heimdall Suite (Go To CyanogenMod Wiki for Vibrant to download as it is over 8MB in size and won't upload here)
Please get all of these first.
Now, first step in the actual process... Thanks to Cyanogen for the tutorial on this part.
Windows ONLY:
1. Power off the Samsung Vibrant and connect the microUSB to the computer but not the Samsung Vibrant.
2. Boot the Samsung Vibrant into download mode by holding down Volume Up & Volume Down while connecting the USB to it.
3. Run the included zadig.exe in the drivers folder of the Heimdall Suite.
4. From the menu, choose Options » List All Devices.
5. From the drop down, select Samsung USB Composite Device or Gadget Serial.
6. Click Install Driver.
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."​
7. Heimdall can now be used safely on the Windows computer.
8. Create the following folder on the root of the internal SD card, Voodoo/disable-lagfix (case-sensitive).
9. Unzip Cmenard's Overstock Kernel.
10. Launch the Heimdall Frontend.
11. Select the extracted zImage in the Kernel (zImage) section.
12. Power off the Samsung Vibrant and connect the microUSB to the computer but not the Samsung Vibrant.
13. Boot the Samsung Vibrant into download mode by holding down Volume Up & Volume Down while connecting the microUSB to it.
14. Click Start on the Heimdall Frontend. A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.
The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section.
Part two of the procedure...
1. Extract the SuperOneClick file.
2. Open the SuperOneClick executable in that extracted folder.
3. Put your phone in Debug mode. (Settings --> Applications)
4. Connect your USB to the computer and the device.
5. Click Root and Wait (The phone will not restart).
6. Turn the phone off.
7. Boot into the recovery (hold the volume up+down while pressing the power button. let go of the power button when you see the samsung vibrant boot screen)
8. Scroll the list with the volume up or down buttons. The power button selects the item.
9. Select "advanced".
10. Select "fix permissions"
11. When it says finished, select "+++++Go Back+++++"
12. Select "reboot system now".
13. Open Android Market -> Search for Superuser -> Update
14. Search for "File Explorer" -> choose eStrongs (free and has root) -> Install
15. Open ES File Explorer -> Menu -> Settings -> Scroll to the bottom and check Root Explorer -> Check Mount File System
16. Press back button -> click the SD Card icon in the top left of the app
17. That will put you in the root. Go to system-->app and remove ONLY the bloatware you don't want (ie.. Slacker Radio, Avatar player, GoGo)
18. Exit the File Explorer and open the Market
19. Get the BusyBox installer from Stephen and install
20. Open the BusyBox installer you downloaded and follow the instructions.
After all is done, the annoying system apps you didn't want will be gone. The phone will be rooted. It will have the clockwork recovery and still be the official ROM.

NOTE: The only reason to remove the bloatware is because you must have at least 1600KB of free space in the /system folder of the device. If running the official KB5 rom, there is only about 560KB free. This frees up the space needed for the BusyBox installer to install BusyBox.

I am all for new guides/information and helping... curious though...
do you feel this is easier than just using odin to get back to jfd
moving the update.zip and rom to the internal sd
getting in stock recovery, pressing reinstall
flashing a rom
EDIT, emphasis, I am honestly not trying to sound like a ****... REALLY happy to see others taking the time to write out such good detail.

stock kb5 recovery will not open the update.zip. it gives an error every time i have tried.

^ needs the modified 3E. Another reason I like to ODIN to JFD.

s15274n said:
I am all for new guides/information and helping... curious though...
do you feel this is easier than just using odin to get back to jfd
moving the update.zip and rom to the internal sd
getting in stock recovery, pressing reinstall
flashing a rom
EDIT, emphasis, I am honestly not trying to sound like a ****... REALLY happy to see others taking the time to write out such good detail.
Click to expand...
Click to collapse
The main reason for the tutorial is because it is very difficult to find working links to the original 2.1 vibrant which allowed SuperOneClick to work out of box. I did find that it was easier than hunting down many different applications/files and most of this can be done from the PC.
This was also for those that wanted to keep the actual official 2.2 (KB5) rom on the vibrant, but have root access. I have tried using the update.zip method with the modified 3e only to find that a lot of the permissions get messed up. The only way that I was able to get the update.zip to work in establishing root was to actually use Odin to downgrade to the 2.1 rom. As soon as I used Keis to update to the new 2.2 rom (KB5) it would loose root and the ClockworkMod recovery.
After much trial and error, I found out this solution is a lot more stable (for me) to achieve root on the KB5 official rom.
If there is a better way, then I was not able to find an actual tutorial from here that stated how to perform root on the KB5 rom without it having permissions problem.
Don't worry about sounding like a ****. I didn't take it that way.

s15274n said:
^ needs the modified 3E. Another reason I like to ODIN to JFD.
Click to expand...
Click to collapse
I understand your affinity for Odin and JFD, but this tutorial is about having a rooted KB5. Sorry to sound like an ass here... regardless of your affinity for Odin/JFD, this is not the topic to shout that affinity.
This is for rooting the KB5 rom. If others wish to downgrade to the JFD, awesome. That is not what this thread is about. It is about a rooted KB5.
Not sure if I made that clear or not in the main tutorial, but this will give you a rooted KB5.

^ wow. Just letting that person know what their issue was while pointing out that if they went to JFD and had the 2E recovery it would not be an issue... pointing out how to fix something and giving an alternative.
I don't consider JFD a downgrade, because nobody stays on it... it's to root and flash a custom ROM... most of which are now going to gingerbread, CM7 and MIUI builds... an upgrade from KB5.
Someone could just as easily root 2.1 and flash a deodexed stock kb5 with root. There are MANY ways to do things.. I applauded you and have only offered other suggestions. I'll regress if you just don't want people to post here.

s15274n said:
^ wow. Just letting that person know what their issue was while pointing out that if they went to JFD and had the 2E recovery it would not be an issue... pointing out how to fix something and giving an alternative.
I don't consider JFD a downgrade, because nobody stays on it... it's to root and flash a custom ROM... most of which are now going to gingerbread, CM7 and MIUI builds... an upgrade from KB5.
Someone could just as easily root 2.1 and flash a deodexed stock kb5 with root. There are MANY ways to do things.. I applauded you and have only offered other suggestions. I'll regress if you just don't want people to post here.
Click to expand...
Click to collapse
I apologize if I did come off as an ass. Bad couple of days here, but that is no excuse. Again, I apologize.
The reason I consider it to be a downgrade is because the 2.2 based rom is the first to offer the ability to do certain things in regards to media. Netflix, HBO Go and the like wasn't working on the 2.1 based rom. The official reason why was because it didn't support the protection they needed to utilize.
I offer this for those that wanted to stick with the rom they got from Kies, but get rid of certain things and add root for installation of other tools.
Now that Samsung has changed their statement regarding a 2.3 release from "we are not sure when" to "we are not sure if", then I am a strong supporter of running custom roms.
I just know that I was looking for a way to do this at one point. Because of my OCD, when I get an idea in my mind... I can't stop until I either find a way to get it done or know for a fact it can't.
Again, I do apologize for coming off as a total ass. Thank you for trying to offer alternatives and posting here. I love being challenged on my ideas, but I shouldn't have gotten nasty in response.

5. From the drop down, select Samsung USB Composite Device or Gadget Serial.
I'm currently stuck on this step, since my system doesn't indicate what kind of usb device is on the current usb port. Nor do I see "Samsung USB Composite Device or Gadget Serial. I believe it's not picking up the device after I did step 1-4. Any insights on what is happening or what I'm doing incorrectly?

Tamborine said:
5. From the drop down, select Samsung USB Composite Device or Gadget Serial.
I'm currently stuck on this step, since my system doesn't indicate what kind of usb device is on the current usb port. Nor do I see "Samsung USB Composite Device or Gadget Serial. I believe it's not picking up the device after I did step 1-4. Any insights on what is happening or what I'm doing incorrectly?
Click to expand...
Click to collapse
I had this same issue, but it was because I was running the app in an Avast sandbox. When I re-ran it in normal mode, it worked as the OP described.
Many thanks for this tutorial, by the way. Very helpful.

plase update procedure.
GayBooSC said:
Okay, first and foremost, by posting this tutorial I am not taking any responsibility if you brick your phone. This worked for me, and it should work for all US based Vibrant (3G) T959 models with the latest 2.2 update (KB5).
NOTE: Rooting and/or installing another recovery WILL void the warranty.
What you will need...
1. SuperOneClick v2.1.1
2. Cmenards's OverStock Kernel with ClockworkMod Recovery
3. Heimdall Suite (Go To CyanogenMod Wiki for Vibrant to download as it is over 8MB in size and won't upload here)
Please get all of these first.
Now, first step in the actual process... Thanks to Cyanogen for the tutorial on this part.
Windows ONLY:
1. Power off the Samsung Vibrant and connect the microUSB to the computer but not the Samsung Vibrant.
2. Boot the Samsung Vibrant into download mode by holding down Volume Up & Volume Down while connecting the USB to it.
3. Run the included zadig.exe in the drivers folder of the Heimdall Suite.
4. From the menu, choose Options » List All Devices.
5. From the drop down, select Samsung USB Composite Device or Gadget Serial.
6. Click Install Driver.
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."​
7. Heimdall can now be used safely on the Windows computer.
8. Create the following folder on the root of the internal SD card, Voodoo/disable-lagfix (case-sensitive).
9. Unzip Cmenard's Overstock Kernel.
10. Launch the Heimdall Frontend.
11. Select the extracted zImage in the Kernel (zImage) section.
12. Power off the Samsung Vibrant and connect the microUSB to the computer but not the Samsung Vibrant.
13. Boot the Samsung Vibrant into download mode by holding down Volume Up & Volume Down while connecting the microUSB to it.
14. Click Start on the Heimdall Frontend. A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.
The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section.
Part two of the procedure...
1. Extract the SuperOneClick file.
2. Open the SuperOneClick executable in that extracted folder.
3. Put your phone in Debug mode. (Settings --> Applications)
4. Connect your USB to the computer and the device.
5. Click Root and Wait (The phone will not restart).
6. Turn the phone off.
7. Boot into the recovery (hold the volume up+down while pressing the power button. let go of the power button when you see the samsung vibrant boot screen)
8. Scroll the list with the volume up or down buttons. The power button selects the item.
9. Select "advanced".
10. Select "fix permissions"
11. When it says finished, select "+++++Go Back+++++"
12. Select "reboot system now".
13. Open Android Market -> Search for Superuser -> Update
14. Search for "File Explorer" -> choose eStrongs (free and has root) -> Install
15. Open ES File Explorer -> Menu -> Settings -> Scroll to the bottom and check Root Explorer -> Check Mount File System
16. Press back button -> click the SD Card icon in the top left of the app
17. That will put you in the root. Go to system-->app and remove ONLY the bloatware you don't want (ie.. Slacker Radio, Avatar player, GoGo)
18. Exit the File Explorer and open the Market
19. Get the BusyBox installer from Stephen and install
20. Open the BusyBox installer you downloaded and follow the instructions.
After all is done, the annoying system apps you didn't want will be gone. The phone will be rooted. It will have the clockwork recovery and still be the official ROM.
Click to expand...
Click to collapse
part 1 procedure after # 7, please indicate if disconnect cable or let cable stay. same as part 2 procedure after # 14 part 1, what happend next. let the cable stay until fully boot?thanks

step 1 procedure #14
After carefully followed the step 1 after procedure # 14 reboot and stuck at vibrant logo.

[Q] Brand new Iconia A500, want to get JB on it but wanna be on the safe road

Hey guys
I'm a happy owner of a new Iconia A500 bought from Amazon . It isn't brand-new but new-enough-for-me lol. It seems it was updated by OTA or something because it has Android ICS 4.0.3 on it.
Tech info:
Model: A500
Android version: 4.0.3
Kernel version: 2.6.39.4+
Image version: Acer_AV041_A500_RV05RC01_PA_CUS1
Compilation version: Acer_AV041_A500_1.033.00_PA_CUS1
Image part number: FM.S14A0.00Y
I read a lot and noticed there's a lot of info but it isn't very organized. I see there is CWM and TWRP, there are stock ROMs, ICS and JB and maybe a linux or two out there, but the instructions on using them aren't very clear.
I know I have to back up my SBK because it's something important. Thing is, how to?
Actually, in the case of a brand new Iconia which I want to get JB/any-other-custom-rom on it and have the possibility to go back to stock in case I screw up (or in other words, how to avoid a brick or how to recover from one if possible), what would I have to do?
In other words, what would be the steps I'll have to follow in order to play safe and backup my current state so I can start flashing custom ROMs like custom JB/ICS and kernels? what do I have to read and in what order? I already have experience in flashing & cooking ROMs, recoveries & bootloaders for HTC Magic, Motorola Defy and MT6577 devices, but this whole nvidia environment is new to me.
Thanks in advance!
- DARKGuy

DARKGuy,
I just recently took the plunge and experimented with various ROMs. The link below pretty much details all the required steps and links to files:
http://forum.xda-developers.com/showthread.php?t=1622425
Remember proceed at your own risk !!. Before doing anything, backup any items (docs, mp3, books, pics, etc) you want saved.
DOWNLOAD ALL FILES BEFORE STARTING !
Practice placing the A500 into Recovery Mode ( PWR + (-) Vol key) and APX Mode (PWR + Reset button (paper clip needed)). You need a micro SD card installed to perform the upgrade.
Download the latest USB drivers from ACER (1.00.0524) and install into PC. Verify they work in both USB drive mode and APX mode. Make sure tablet has USB Debugging enabled (Settings). Verify the drivers work. Boot tablet normal and connect to PC, you should see Acer Tablet with SD drive and External SD drive (if micro SD installed). Files\folders should be viewable. Turn table off, then restart into APX mode. You should see new hardware found, ADB driver. You shouldn't see any errors in device manager. If everything is working fine, you're ready to proceed.
Basic Steps:
1) Get CPU ID. I used File Explores ES app. Folder Local\Sys\Firmware\Fuse and the file is acer_cpu_id. Text file. Remember to add a zero in the beggining. ie mine started 33c20c.... My CPU ID is 033c20c....etc, Write it down.
2) Download the tool and generate your SBK with the CPU ID. Write it down. It's 4 sets of numbers, ie 0x520A1300 0x78498901 etc.
3) Root device. Here' the link: http://forum.xda-developers.com/showthread.php?t=1546593.
4) Install bootloader and recovery rom. I used Blackthund3r APX tool. Option 17, ShirlaxCZ V8 Bootloader and Thors 1.7.3 recovery tool.
Once this have been completed, successfully. You can download any JB\ICS you'd like to load. Just boot into recovery and load from SD card.
I would also download a stock image in case you want to go back.
Acer Stock w/Root Images:
http://forum.xda-developers.com/showthread.php?t=1633907
I'm being brief, please read the various links thoroughly.

da_maxx said:
DARKGuy,
I just recently took the plunge and experimented with various ROMs. The link below pretty much details all the required steps and links to files:
http://forum.xda-developers.com/showthread.php?t=1622425
Remember proceed at your own risk !!. Before doing anything, backup any items (docs, mp3, books, pics, etc) you want saved.
DOWNLOAD ALL FILES BEFORE STARTING !
Practice placing the A500 into Recovery Mode ( PWR + (-) Vol key) and APX Mode (PWR + Reset button (paper clip needed)). You need a micro SD card installed to perform the upgrade.
Download the latest USB drivers from ACER (1.00.0524) and install into PC. Verify they work in both USB drive mode and APX mode. Make sure tablet has USB Debugging enabled (Settings). Verify the drivers work. Boot tablet normal and connect to PC, you should see Acer Tablet with SD drive and External SD drive (if micro SD installed). Files\folders should be viewable. Turn table off, then restart into APX mode. You should see new hardware found, ADB driver. You shouldn't see any errors in device manager. If everything is working fine, you're ready to proceed.
Basic Steps:
1) Get CPU ID. I used File Explores ES app. Folder Local\Sys\Firmware\Fuse and the file is acer_cpu_id. Text file. Remember to add a zero in the beggining. ie mine started 33c20c.... My CPU ID is 033c20c....etc, Write it down.
2) Download the tool and generate your SBK with the CPU ID. Write it down. It's 4 sets of numbers, ie 0x520A1300 0x78498901 etc.
3) Root device. Here' the link: http://forum.xda-developers.com/showthread.php?t=1546593.
4) Install bootloader and recovery rom. I used Blackthund3r APX tool. Option 17, ShirlaxCZ V8 Bootloader and Thors 1.7.3 recovery tool.
Once this have been completed, successfully. You can download any JB\ICS you'd like to load. Just boot into recovery and load from SD card.
I would also download a stock image in case you want to go back.
Acer Stock w/Root Images:
http://forum.xda-developers.com/showthread.php?t=1633907
I'm being brief, please read the various links thoroughly.
Click to expand...
Click to collapse
Hey sorry for the late reply, I must say that was a very elaborate yet useful answer and I was able to backup my important data aswell as installing ROMs like crazy. You rock man! big thanks for the help and guidance!

root
get bootloader + thors recovery 1.7.3 cwm base(only cwm i found to work with aroma installer. which some of the newer roms is a must)
backup your files before u wipe.
flash away.
trying to find a rom that will let us a500 users use multiwindow manager, this would be superb!
will post back i find that golden ticket.

Newbie corner: How to unlock, install some OS on Galaxy S6

Hello there,
I am a very, very, very newbie in mobile and android, event the vocabulary is new, so please be indulgent. Moreover, I am old school and running Linux (opensuse Leap 15.2) and I hate GAFAM stuff.
I got an old Galaxy S6 SM-G920F. I don't have access to it, no SIM card, I'd guess no data. I want to learn how to change the OS (I think the good word is mod) to something like Lineage.
I have read a lot but there has been evolution in methods and I can't find the easy way to do it.
As it seems WINDOWS OS is needed to success, I installed WIN 10 in a laptop (what a chit!). BUT if you have a way to go with Linux, please I'd prefer.
First I wand to know the main part of the process. I think the first on is to unlock the bootloader.
I tried the following in the phone: Press and hold three physical keys of Home, Power and Volume Down. Release them when the screen is lightning, and then press the Volume Up key. I got on the screen:
Code:
ODIN MODE
PRODUCT NAME: SM-G620F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download : Enabled
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: B:5 K:2 S:2
I'd guess the bootloader is unlocked, could you confirm?
Now, what to do? Could you
- Explain the main steps without detail then
- Point me on a good recent HowTo or write it here.
Many thanks for your help
Edit: BTW what does mean debloat and deknox?

MrNice said:
Hello there,
I am a very, very, very newbie in mobile and android, event the vocabulary is new, so please be indulgent. Moreover, I am old school and running Linux (opensuse Leap 15.2) and I hate GAFAM stuff.
I got an old Galaxy S6 SM-G920F. I don't have access to it, no SIM card, I'd guess no data. I want to learn how to change the OS (I think the good word is mod) to something like Lineage.
I have read a lot but there has been evolution in methods and I can't find the easy way to do it.
As it seems WINDOWS OS is needed to success, I installed WIN 10 in a laptop (what a chit!). BUT if you have a way to go with Linux, please I'd prefer.
First I wand to know the main part of the process. I think the first on is to unlock the bootloader.
I tried the following in the phone: Press and hold three physical keys of Home, Power and Volume Down. Release them when the screen is lightning, and then press the Volume Up key. I got on the screen:
Code:
ODIN MODE
PRODUCT NAME: SM-G620F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download : Enabled
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: B:5 K:2 S:2
I'd guess the bootloader is unlocked, could you confirm?
Now, what to do? Could you
- Explain the main steps without detail then
- Point me on a good recent HowTo or write it here.
Many thanks for your help
Edit: BTW what does mean debloat and deknox?
Click to expand...
Click to collapse
Hello,
as I have installed a custom ROM myself on my S6 G920f only a few weeks ago, I can help you out as far as my knowledge goes and as far as I haven't forgotten it. Bear in mind though that I am not an expert and had to look up a lot of stuff myself.
First, after trying many different up-to-date ROMs and after becoming very frustrated, I kind of accepted that there is currently no up-to-date ROM for the S6 that does not have one or the other big flaw. Some didn't even Boot and instead did load for 5 minutes and rebooted into twrp. The critical flaws on the others were random shutdowns, microphone issues ranging from my voice not being transmitted at all to constant feedback where the other person was hearing her or his voice. The feedback issue I experienced on all the ROMs. Also, with the ROM that I thought I could arrange with I noticed that sometimes, randomly, the calls coming in were just blocked/didn't come through for whatever reason. Also, fast charging is an issue and the camera is bad since you won't have Samsung's camera app and the necessary framework that optimizes it. Google safety net was a big issue with the Android 10 ROMs too, but magiskhide props solved that for me.
I'm sure many people have different reasons to use ROMs but for me it was just not worth it at this time. Maybe this will change later. Just wanting to let you know since you asked for it. I found my current happy place with the Marduk Stock Rom which you can find in the S6 Development section. It is based on the stock ROM which is Android 7, I find it to be fast, it has a good battery life and for me it is very stable. Also no microphone or connectivity issues, fast charging works only with screen off, camera is good since it's the original camera app. No google safety net issue.
Now to your questions.
Debloat means the pre-installed apps that you cannot uninstall and that clutter your phone are removed. Deknoxed as far as I know refers to Samsungs knox which is a safety plus as long as you use your phone unrooted but (tries to) restrict rooting and installing custom ROMs etc. Don't know much more than that tho.
Yes, your bootloader seems to be unlocked.
Now install twrp first. Go to twrp website and download the version you need for your phone. To flash TWRP recovery, you don't need odin. I have used heimdall myself and found it to be very easy.
- Install heimdall. You can also install samsung usb driver for linux if you have issues connecting your phone to your pc.
- Boot into Download Mode (For me volume down + home button + power button)
- Have phone plugged in to pc and at least 60% charge
- Start Terminal, Cd into folder with your recovery.img and use this command to install your recovery (of course replace "recovery.img" with your recovery):
heimdall flash --RECOVERY recovery.img --no-reboot
- Now turn your phone off, and since my phone automatically rebooted at this point, try to stop this by instantly using your key combo as soon as the screen turns black to boot into recovery mode (volume up+home button + power). I had issues here. If you don't manage to do this and get stuck in bootloop just boot into download mode again and install recovery once more to try again.
- Now you can download your preferred rom, boot your phone into twrp recovery and connect to your pc to copy, wipe everything in twrp (obviously save any file you'd like to keep) and install your Custom ROM.
- Most ROMs (but not all! read ROM description!) come without GAPPS installed so you will have to download and install it manually after you have installed your ROM (I recommend GAPPS pico for your custom ROM version). You don't have to do this if you don't want to use google applications.
- Before leaving twrp and booting into your OS install Magisk in TWRP(Download latest version and install in twrp after GAPPs).
- Wipe Cache/Dalvik
- Now reboot into System (and don't install TWRP manager system app)
- Install Magisk Manager after after restart
ROMs:
The best LineageOS ROM I have found to be this: https://lineageos.wickenberg.nu/zerofltexx
It seemed to have the least amount of flaws. The bugs for me were no fast charging unless you reboot plugged in. So no fast charging when you plugin and dont reboot and stay plugged in after reboot. Random connectivity issues. Microphone feedback. Camera crashes and camera issues whilst videocalling etc. Google safety net failure by default, but you can fix this with MagiskHide Props.
Haven't tried the Pixel one here but it seems to have the same microphone issue where nobody can hear your voice.
The Marduk Debloated Stock ROM, also here on XDA, is based on the older Android 7.0 but works very well. Lacks the extended settings and features you find on LineageOS, but least buggy and fast and battery efficient.
Have fun

waffelschnitten said:
Hello,
as I have installed a custom ROM myself on my S6 G920f only a few weeks ago, I can help you out as far as my knowledge goes and as far as I haven't forgotten it. Bear in mind though that I am not an expert and had to look up a lot of stuff myself.
First, after trying many different up-to-date ROMs and after becoming very frustrated, I kind of accepted that there is currently no up-to-date ROM for the S6 that does not have one or the other big flaw. Some didn't even Boot and instead did load for 5 minutes and rebooted into twrp. The critical flaws on the others were random shutdowns, microphone issues ranging from my voice not being transmitted at all to constant feedback where the other person was hearing her or his voice. The feedback issue I experienced on all the ROMs. Also, with the ROM that I thought I could arrange with I noticed that sometimes, randomly, the calls coming in were just blocked/didn't come through for whatever reason. Also, fast charging is an issue and the camera is bad since you won't have Samsung's camera app and the necessary framework that optimizes it. Google safety net was a big issue with the Android 10 ROMs too, but magiskhide props solved that for me.
I'm sure many people have different reasons to use ROMs but for me it was just not worth it at this time. Maybe this will change later. Just wanting to let you know since you asked for it. I found my current happy place with the Marduk Stock Rom which you can find in the S6 Development section. It is based on the stock ROM which is Android 7, I find it to be fast, it has a good battery life and for me it is very stable. Also no microphone or connectivity issues, fast charging works only with screen off, camera is good since it's the original camera app. No google safety net issue.
Now to your questions.
Debloat means the pre-installed apps that you cannot uninstall and that clutter your phone are removed. Deknoxed as far as I know refers to Samsungs knox which is a safety plus as long as you use your phone unrooted but (tries to) restrict rooting and installing custom ROMs etc. Don't know much more than that tho.
Yes, your bootloader seems to be unlocked.
Now install twrp first. Go to twrp website and download the version you need for your phone. To flash TWRP recovery, you don't need odin. I have used heimdall myself and found it to be very easy.
- Install heimdall. You can also install samsung usb driver for linux if you have issues connecting your phone to your pc.
- Boot into Download Mode (For me volume down + home button + power button)
- Have phone plugged in to pc and at least 60% charge
- Start Terminal, Cd into folder with your recovery.img and use this command to install your recovery (of course replace "recovery.img" with your recovery):
heimdall flash --RECOVERY recovery.img --no-reboot
- Now turn your phone off, and since my phone automatically rebooted at this point, try to stop this by instantly using your key combo as soon as the screen turns black to boot into recovery mode (volume up+home button + power). I had issues here. If you don't manage to do this and get stuck in bootloop just boot into download mode again and install recovery once more to try again.
- Now you can download your preferred rom, boot your phone into twrp recovery and connect to your pc to copy, wipe everything in twrp (obviously save any file you'd like to keep) and install your Custom ROM.
- Most ROMs (but not all! read ROM description!) come without GAPPS installed so you will have to download and install it manually after you have installed your ROM (I recommend GAPPS pico for your custom ROM version). You don't have to do this if you don't want to use google applications.
- Before leaving twrp and booting into your OS install Magisk in TWRP(Download latest version and install in twrp after GAPPs).
- Wipe Cache/Dalvik
- Now reboot into System (and don't install TWRP manager system app)
- Install Magisk Manager after after restart
ROMs:
The best LineageOS ROM I have found to be this: https://lineageos.wickenberg.nu/zerofltexx
It seemed to have the least amount of flaws. The bugs for me were no fast charging unless you reboot plugged in. So no fast charging when you plugin and dont reboot and stay plugged in after reboot. Random connectivity issues. Microphone feedback. Camera crashes and camera issues whilst videocalling etc. Google safety net failure by default, but you can fix this with MagiskHide Props.
Haven't tried the Pixel one here but it seems to have the same microphone issue where nobody can hear your voice.
The Marduk Debloated Stock ROM, also here on XDA, is based on the older Android 7.0 but works very well. Lacks the extended settings and features you find on LineageOS, but least buggy and fast and battery efficient.
Have fun
Click to expand...
Click to collapse
Thank you waffelschnitten (no waffel icon) for your extensive answer.
I've learn a lot yet.
As this phone is for experiment, I'll try your Howto.
Forgive my ignorance but the first step is not clear for me. TWRP looks to be an Android app. So I have to install it on the phone, but as I mentioned in my previous post I can't access in it, I don't have the code.
Is it possible to bypass the code? Maybe this device is only good for the recycling? Could you be more accurate in the process?

No worries. No your device should be fine.
TWRP stands for Team Win Recovery Project. It is a Custom Recovery System, it's not an app. You don't need to boot into your System OS to install it. You have to flash it onto your phone by using the Samsung Download Mode. Only with a Custom Recovery System such as TWRP you can easily install new ROMs, Root your phone etc.
To install TWRP, you first need to download TWRP for the S6 onto your PC: https://eu.dl.twrp.me/zeroflte/. Download the .img file version.
Now you have to boot into the S6 Download Mode. To do this, make sure your phone is turned off. Then boot it up by pressing and holding Volume Down Button+Home Button+Power Button at the same time for a few seconds. This should get you into Download Mode.
When in Download Mode, connect your phone to your Linux PC via USB.
Make sure you have installed heimdall on Linux. Start Linux Terminal. Remember, your phone should be connected to your PC and in Download Mode. Now check if heimdall detects your phone with this command:
heimdall detect
If it is not detected, try and install Samsung USB drivers for Linux.
If it is detected, navigate to the folder with the TWRP file in your Linux Terminal with the Cd command.
Then, flash your twrp.img file on your phone with this command:
heimdall flash --RECOVERY recovery.img --no-reboot
Replace recovery.img with your twrp.img file. For the latest one it should be twrp-3.3.1-0-zeroflte.img
So this would be the command:
heimdall flash --RECOVERY twrp-3.3.1-0-zeroflte.img --no-reboot
Just to make sure, do you know how to navigate/use the linux terminal?
If you have followed these steps, you should have installed your Custom Recovery. With this you have access to your File System etc. Continue as described in my first reply. As already said, to boot into your newly installed TWRP recovery, you have to press Volume up+Home Button+Power Button at the same time and hold for a few seconds, even after the S6 logo appears.

Many, many thanks,
I am not too bad with Linux, user for around 10 years, only newbie with mobile devices and Android.
I had to wait long time for the battery be empty and the phone power off. I can't find other way with buttons.
I did a download mode restart and connected to my Linux box. Then detect OK, then flash the phone.
Code:
heimdall flash --RECOVERY twrp-3.3.1-0-zeroflte.img --no-reboot
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
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...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Releasing device interface...
After that I power off with Vol-, Vol+, Home, Power together long time but had no time to restart in TWRP mode.
I wait again to discharge the battery and try again.
See you

MrNice said:
Many, many thanks,
I am not too bad with Linux, user for around 10 years, only newbie with mobile devices and Android.
I had to wait long time for the battery be empty and the phone power off. I can't find other way with buttons.
I did a download mode restart and connected to my Linux box. Then detect OK, then flash the phone.
Code:
heimdall flash --RECOVERY twrp-3.3.1-0-zeroflte.img --no-reboot
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
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...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Releasing device interface...
After that I power off with Vol-, Vol+, Home, Power together long time but had no time to restart in TWRP mode.
I wait again to discharge the battery and try again.
See you
Click to expand...
Click to collapse
You can force your phone to turn off by pressing Vol- and Power Button together and holding it until it turns off, maybe this helps. Good luck!

Very good, now I am in TWRP and I have a lot of questions.
I did WIPE, Format Data, "yes" and Back.
Should I reboot now? What will be the OS/ROM at self reboot? Should I reboot with Vol up, Home, Power instead?
I connected the phone to my linux computer but no connection.
How (with detail as you did perfectly) to upload the new ROM image to the phone?
As you are happy with Marduk Stock Rom, I'll try it.
Could you provide the link to the thread and the download to this rom?
Thanks a lot again
Edit:
In Marduk Stock Rom, is there any GAFAM app/link/account needed?
Is the version v4.5 (12/10/2019) the last one?
Is it the good link to the thread?
Edit 2:
After disconnect and reconnect, I got the phone in my file manager in Linux (Internal Storage). I can transfer the rom file. What should be the extension of the file? .img or .zip or other? Waiting to your confirmation for the version.

MrNice said:
Very good, now I am in TWRP and I have a lot of questions.
I did WIPE, Format Data, "yes" and Back.
Should I reboot now? What will be the OS/ROM at self reboot? Should I reboot with Vol up, Home, Power instead?
I connected the phone to my linux computer but no connection.
How (with detail as you did perfectly) to upload the new ROM image to the phone?
Asyou are happy with Marduk Stock Rom, I'll try it.
Could you provide the link to the thread and the download to this rom?
Thanks a lot again
Click to expand...
Click to collapse
Advanced Wipe everything (but USB)
If you reboot without going into TWRP you will probably face bootloop. But that's no issue since you can always boot down and up into recovery. In TWRP, you can also go to Menu -> Reboot -> Recovery
If you connect your phone via USB to your PC in TWRP it should be detected, so that is weird. You can try to use different usb cables and USB ports on your PC, you can also try to install Samsung USB Drivers and ADB if nothing helps and try again.
Marduk ROM you can find here:
[ROM][ESE3][MAY PATCH] Galaxy S6 Marduk Stock ROM v4.1 [04/07/2019][G920/5/I/F]
WELCOME TO MY S6 MARDUK STOCK ROM No one is allowed to modify or use anything from ROM without first contacting me. READ INSTALLATION INSTRUCTIONS TO AVOID ANSWERED QUESTIONS INSTALLATION INSTRUCTIONS: - Do full wipe and factory reset -...
forum.xda-developers.com
See his/her instructions for your model:
- Do full wipe and factory reset
- Flash ROM using latest TWRP recovery
- Flash latest Magisk Manager
- Reboot
- First boot will take a while
Click to expand...
Click to collapse
You don't need GApps for this, but you need additional Magisk. magiskmanager.com
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip
When you have finished and installed your OS install the magisk manager app as an App.
Downloading Magisk App... | Magisk Manager
The download will automatically start in 5 seconds, please click here to access the download URL directly. If you are confused and want to know how to install the Magisk Manager on your phone you can click here.
magiskmanager.com

MrNice said:
Very good, now I am in TWRP and I have a lot of questions.
I did WIPE, Format Data, "yes" and Back.
Should I reboot now? What will be the OS/ROM at self reboot? Should I reboot with Vol up, Home, Power instead?
I connected the phone to my linux computer but no connection.
How (with detail as you did perfectly) to upload the new ROM image to the phone?
As you are happy with Marduk Stock Rom, I'll try it.
Could you provide the link to the thread and the download to this rom?
Thanks a lot again
Edit:
In Marduk Stock Rom, is there any GAFAM app/link/account needed?
Is the version v4.5 (12/10/2019) the last one?
Is it the good link to the thread?
Edit 2:
After disconnect and reconnect, I got the phone in my file manager in Linux (Internal Storage). I can transfer the rom file. What should be the extension of the file? .img or .zip or other? Waiting to your confirmation for the version.
Click to expand...
Click to collapse
Extension should be zip. Version 4.5 is the right one. Dont forget to flash Magisk after installing the ROM and wiping Cache/Dalvik right after flashing Magisk. Then reboot into OS and wait

Ahrrr...
After Wipe, Advanced Wipe, select all but not USB Storage, Wipe then reboot, Recovery, when I connect to PC, I get SAMSUNG Android device and Internal Storage. If I open this directory I get error:
Code:
The forlder contents could not be displayed.
Sorry, could not display all the contents of "Internal Storage". The connection is closed
I tried to reboot with 3 buttons, same issue.
In Linux dmesg says:
Code:
[23088.108086] usb 2-4: new high-speed USB device number 13 using ehci-pci
[23088.265639] usb 2-4: New USB device found, idVendor=04e8, idProduct=6860
[23088.265647] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[23088.265652] usb 2-4: Product: SAMSUNG_Android
[23088.265656] usb 2-4: Manufacturer: SAMSUNG
[23088.265661] usb 2-4: SerialNumber: 0815f83172eb2d01
[23088.267224] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[23096.897800] pool[17212]: segfault at 54b62d50 ip 00007feb702ed9d6 sp 00007feb65ffab68 error 4 in libc-2.26.so[7feb70252000+1b1000]
[23383.203939] pool[17338]: segfault at 54b62d50 ip 00007f4154ef69d6 sp 00007f4142ffcb68 error 4 in libc-2.26.so[7f4154e5b000+1b1000]
I'll try more
Any idea?

MrNice said:
Ahrrr...
After Wipe, Advanced Wipe, select all but not USB Storage, Wipe then reboot, Recovery, when I connect to PC, I get SAMSUNG Android device and Internal Storage. If I open this directory I get error:
Code:
The forlder contents could not be displayed.
Sorry, could not display all the contents of "Internal Storage". The connection is closed
I tried to reboot with 3 buttons, same issue.
In Linux dmesg says:
Code:
[23088.108086] usb 2-4: new high-speed USB device number 13 using ehci-pci
[23088.265639] usb 2-4: New USB device found, idVendor=04e8, idProduct=6860
[23088.265647] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[23088.265652] usb 2-4: Product: SAMSUNG_Android
[23088.265656] usb 2-4: Manufacturer: SAMSUNG
[23088.265661] usb 2-4: SerialNumber: 0815f83172eb2d01
[23088.267224] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[23096.897800] pool[17212]: segfault at 54b62d50 ip 00007feb702ed9d6 sp 00007feb65ffab68 error 4 in libc-2.26.so[7feb70252000+1b1000]
[23383.203939] pool[17338]: segfault at 54b62d50 ip 00007f4154ef69d6 sp 00007f4142ffcb68 error 4 in libc-2.26.so[7f4154e5b000+1b1000]
I'll try more
Any idea?
Click to expand...
Click to collapse
Maybe install Samsung USB drivers

More and more I think the issue is in the phone.
When I wiped with: Wipe, Advanced wipe, select all but USB Storage, this selection included "Internal Storage".
Now in this window, I can "Repair or Change File System" directories. When I select System or Data or Cache or USB Storage, and press "Repair or Change File System" button, I get info on the selected item and I could do more. When I select "Internal Storage" instead, I get error: "Invalid partition selection".
As I can;t find it with the file manager, my question is
This directory has issue, is it a real dir or a soft link to a real dir?
How to restore as previous?
Edit 1:
In phone, Wipe page I can read on top:
Wipes Data, Cache and Dalvik
(not including internal storage)
Click to expand...
Click to collapse
What does mean "not including internal storage"?
Should I not wipe it?

MrNice said:
More and more I think the issue is in the phone.
When I wiped with: Wipe, Advanced wipe, select all but USB Storage, this selection included "Internal Storage".
Now in this window, I can "Repair or Change File System" directories. When I select System or Data or Cache or USB Storage, and press "Repair or Change File System" button, I get info on the selected item and I could do more. When I select "Internal Storage" instead, I get error: "Invalid partition selection".
As I can;t find it with the file manager, my question is
This directory has issue, is it a real dir or a soft link to a real dir?
How to restore as previous?
Edit 1:
In phone, Wipe page I can read on top:What does mean "not including internal storage"?
Should I not wipe it?
Click to expand...
Click to collapse
Did you allow modifications here?
https://www.android-hilfe.de/attachments/default-twrp-welcome-screen-jpg.643125/
You can try to mount partitions in TWRP mount option.
I dont know about the Repair options. I didn't have to do that. Also, I dont think your issue is with corrupted file directories.
I would first try to reboot into DOwnload Mode and try and see if USB works in Download Mode. Maybe ADB sideload is possible in Download mode? I don't know about this, though.
If I were you, I would try to connect it to the PC, install Samsung USB and ADB drivers. If it still doesnt work, connect to a different PC, maybe your Windows 10 OS. If that doesn't work, Flash TWRP again and try again.
Wipe/Cache Dalvik does not include internal storage. That is just to make clear that you can wipe it without losing your os or phone data. You should still wipe it, and it will not block wipe of internal storage.

Following this howto I succeeded to transfer and install the new ROM.
I didn't reboot so far as I have to install Magisk.
I downloaded Magisk-v21-4.zip but I don't know how to transfer and install it as I still can't access to "Internal Storage"
I am in the good way, any help?

Nice. So you used ADB sideload to transfer your ROM onto your device? Do the same with the Magisk.zip and flash it just like you have flashed the ROM. Then wipe Cache/Dalvik and reboot into OS.

I did the same process with Magisk, OK then wipe and reboot without TWRP install.
I had to wait at least 5mn then got the new screen.
It seems to work fine and I started to follow setting.... but I got a Google account to create and other thing like that I don't like at all...
I see this ROM is not what I want but I will try a bit
Thank a lot for your help
See you

MrNice said:
I did the same process with Magisk, OK then wipe and reboot without TWRP install.
I had to wait at least 5mn then got the new screen.
It seems to work fine and I started to follow setting.... but I got a Google account to create and other thing like that I don't like at all...
I see this ROM is not what I want but I will try a bit
Thank a lot for your help
See you
Click to expand...
Click to collapse
Hey, yes this ROM is not de-googled. Sorry for that. Go ahead and try other ROMs. Good job installing the Marduk ROM though and have fun

I spend some time to test some features.
So far I found that the fingerprint is not working.
I removed the Google icon but can't remove the apps in Settings > Apps. Is it possible?
How I could install alternative apps store like Apkpure, Aptoide? There are a lot of them but I don't know if I can trust them.
Do you know trusted app shop, good one?
Later if needed, I'll change the ROM. Just to be sure, should I use the same process as previously: Boot to TWRP > ADB sideload > Install the ROM > Install again Magisk.zip (?) > Wipe Cache/Dalvik and reboot into OS.
Question about Magisk.
If fact I don't understand the usage. I have read it's usefull to root devices. My device is rooted, so why I need it? What is the difference between Magisk.zip and Magisk Manager that I have in the apps?
When I start Magisk Manager, at the top page, there are 2 links "Install" to update Magisk and Manager, both look up-to-date. Strange, as the apps are up-to-date why I see these links? Have you the same?
Thank you for your patience.
Edit:
Just to say I don't have any browser where I could display and download apps. Maybe I should start first to install one. BTW what do you advise as browser outside GAFAM?

MrNice said:
I spend some time to test some features.
So far I found that the fingerprint is not working.
I removed the Google icon but can't remove the apps in Settings > Apps. Is it possible?
How I could install alternative apps store like Apkpure, Aptoide? There are a lot of them but I don't know if I can trust them.
Do you know trusted app shop, good one?
Later if needed, I'll change the ROM. Just to be sure, should I use the same process as previously: Boot to TWRP > ADB sideload > Install the ROM > Install again Magisk.zip (?) > Wipe Cache/Dalvik and reboot into OS.
Question about Magisk.
If fact I don't understand the usage. I have read it's usefull to root devices. My device is rooted, so why I need it? What is the difference between Magisk.zip and Magisk Manager that I have in the apps?
When I start Magisk Manager, at the top page, there are 2 links "Install" to update Magisk and Manager, both look up-to-date. Strange, as the apps are up-to-date why I see these links? Have you the same?
Thank you for your patience.
Edit:
Just to say I don't have any browser where I could display and download apps. Maybe I should start first to install one. BTW what do you advise as browser outside GAFAM?
Click to expand...
Click to collapse
You can manually degoogle your phone I am sure, but I would advise you to just install a (stable) ROM that is already de-googled.
You can try lineageOS 17.1 if you want (best version I have found was this: https://lineageos.wickenberg.nu/zerofltexx), or look for older official lineageOS builds in this forum, or just any other ROMs.
My fingerprint sensor works, so I dont know about yours. But it won't work without Google apps, I think. At least not on this ROM I guess.
Yes, if you want to change your ROM later, that is what you would do. IF you want Google Apps and it is not included in the chosen ROM, you would have to install GApps additionally. But since you dont want google, you only need to Root and flash Magisk.
Most people use FDroid for a free App Store I think.
About your Question regarding Magisk:
Magisk.zip is the thing you root your phone with. Usually you have to root your phone again every time you install a new ROM.
Magisk Manager is an App that helps you manage your root permissions, so you can grant root access to apps or deny them. It is also there to hide your root from the google system and from apps that require un-rooted devices. I guess you can't run them without Google safety net etc anyways. Furthermore, there is a repository in the magisk manager app from which you can download various tweaks and scripts etc for your phone and flash it directly onto it, without needing to boot into recovery first.
Yes, I see the same installation buttons even though it is up to date. Maybe it is there to give you the option to re-install things to fix issues.
I would advise using Firefox as your browser.

Thank you again waffelschnitten I learn a lot with you.
So far I installed
F-Droid, APKPure
Firefox, Opera, Brave
Signal but I can't start it because I need to update Google Play Services. I had reading about it and understand it is very difficult to avoid as it is a layer between hardware and software (?).
As you know I don't like GAFAM stuff but I'll be pragmatic and use it unless you know another way.
The issue now is when I start Signal, it ask to update Google PS and I am back to the previous window when I click update button. I checked that it is installed version 11.9.75 and the 2 buttons Disable and Force Stop are grey out.
Any idea how to get ride of this issue?
BTW what Instant Messaging app do you advice/use?