[GUIDE] Firmware (5.1.1) + Root + TWRP (SM-G925F + Others) - Galaxy S6 Edge Q&A, Help & Troubleshooting

Welcome.
After two days of sweating trying to understand all the guides and tricks as a complete newbie, I realized that some things are easier than they seem but requires certain knowledge to pull off.
I softbricked my device after my first attempt of rooting but after two days total, I managed to get everything working. The point of this guide is to be as thorough as possible because a lot of the guides out there, no matter how well they were made, some things still did not make sense to me as a newbie and I intend to make it a lot clearer in this guide.
Please understand that my knowledge is very limited, but I am going to explain very thoroughly step-by-step how I managed to update my firmware using Odin, Uni root and TWRP. I will also do a brief explanation of how to use TWRP to install a ROM as that was my goal from the beginning.
Note: I can only assure you that this worked for me with the firmware version, root and TWRP that I used. I cannot guarantee that this will work for you at all, and you should make sure to read and understand the risks about flashing and rooting your device. I take no responsibility if you brick your device, please continue at your own risk. Also note that you may or may not lose your data depending on what you do so I suggest you backup all your files somewhere else if you want to save your data. YOU WILL VOID YOUR WARRANTY USING THIS METHOD.
Firmware
It is important that you have a supported firmware for whatever root you are chosing. I have a SM-G925F and here is the link to all the newest firmwares.
http://www.sammobile.com/firmwares/database/SM-G925F/
If you have a different model, you can change the last section of the link "SM-G925F" to whatever model you have, for example ".../database/SM-G925T/".
For this guide I am using 5.1.1 G925FXXU3COI9 (Sweden).
{
"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"
}
Drivers & Odin
Download and install the necessary drivers for your Samsung Galaxy S6 Edge provided in the link below.
https://www.dropbox.com/s/jze4q58cspwnjwh/SAMSUNG_USB_Driver_for_Mobile_Phones.zip?dl=1
Download latest version of Odin provided in the link below.
http://odindownload.com/download/Odin3_v3.10.7.zip
Testing your connection/Debug mode (MANDATORY)
Enter settings on your device, scroll to the bottom and chose "About device".
Then tap on Build number until you have unlocked "Developer options".
Go back a step and you should now be able to see "Developer options". Enter it and find "USB Debugging". Activate it.
Connect your device to your PC. If this is your first time doing it you will get prompted on your device to allow your PC access. Please tick the box and allow it. Now start Odin and make sure you have a COM connection.
We now know that your device has a connection with your PC and can start the firmware flash.
Unlocking Bootloader
If your bootloader is locked, you should be able to see a setting in "Developer options" that can be called "OEM Unlocked", "Unlock OEM" and so forth. You will want to make sure that your OEM is unlocked, otherwise you will most certainly fail. The most common question for bootloaders are the ones who can't find this setting and what that means. If you can't find the OEM Unlock setting, then your bootloader is probably already unlocked. And I can confirm this as I did not have this setting and have a perfectly working 5.1.1 rooted with custom ROM.
Flashing firmware
Make sure you have enough battery, I usually keep my phone around at least 80% when flashing.
Turn off your device completely, "Power off". Now hold Volume Down + Home button + Power button until you get a screen with "Warning". Click 'Volume Up' to enter "Download mode". Make sure Odin finds your device while in "Download mode" by checking the COM connection.
Now unpack the firmware you downloaded. You should now have a "FIRMWAREVERSION".tar.md5 file.
Open Odin, click the "AP" button and navigate to the "FIRMWAREVERSION".tar.md5 file you just unpacked. Please allow Odin to load the file and wait until the log says "<OSM> Leave CS..".
You can now click "Start" and let Odin write all the files. Do now touch anything during this process. When it is done, if you have done everything correctly, it should become green and say "PASS!". At this point you have successfully flashed the firmware to your device.
Rooting
Make sure you have a supported firmware before attempting to root. If you have flashed your device accordingly, this root should work perfectly. Make sure your device is supported and then download the Unikernel "ODIN FLASHABLE".
http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
We are now going to do the exact same process as above, but this time using a different file. Put your phone in "Download mode", connect it to your PC and make sure you can see the connection in Odin. Click the button "AP" in Odin and navigate to the Unikernel.tar file.
Click start and wait for Odin to complete the process. It should become green and say "PASS!".
Your device will reboot and you should now be rooted if you have done everything correctly.
TWRP
TWRP is a custom type of recovery that can be used to do a lot of things. Please read about TWRP here: https://twrp.me/about/
To install TWRP with Odin, your device needs to be rooted. Here is how you do it.
First, make sure you download the supported version for your device from the link provided below.
http://galaxys6root.highonandroid.com/cwmtwrp-recovery/
I have a SM-G925F and I downloaded the .tar file shown on the picture below.
Again, repeating the steps from above. Put your device in "Download mode", connect it to your PC and check the connection in Odin.
Click "Start" and wait for the process to "PASS!". You should now have TWRP Recovery installed properly.
To access TWRP enter your phone into "Recovery mode". You do this by turning off your device completely and starting it through Volume Up + Home button + Power button. From here, you can do a lot of things but most importantly you can install custom ROMs. Always make sure to check the installation guide for the ROM you want to install but basically you copy the ROM to your phone memory, chose "Install" in TWRP and navigate to the ROM.
I hope this helps people who are impatient to learn all the details and just want to be a user. The problem with this is that if something goes wrong, you might not have the knowledge to fix your problem instantly and might have to wait for responses on the forums. Usually if your phone is Softbricked or stuck in a bootloop, you can enter "Download mode" and flash a suitable firmware from the links provided. Please let me know if you still have questions and/or don't understand some of the steps and I will adjust accordingly. Good luck!

Related

[GUIDE] HOW TO FIX your unflashable or soft bricked GSII

Hello everyone!
I thought that this forum is more appropriate to post this, to avoid any new "lulz i r borked" threads. Plus, I had good feedback on the other flrum section
This is a guide dedicated to noobs, so if you're not one, I would advise to stop reading now! (altough feedback would be great! )
Yes, there have been quite a few threads about fixing a soft brick. But what I'm writting now is another solution to a different kind of problem : unflashable GSII (which also works with a soft brick of course ), which is a soft brick and a corrupted NAND rw (read/write) function.
Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, regarding NAND rw (NAND's read and write function being the corruption) it means that it is an issue deeper than a soft brick. It is obvious when you can flash a kernel, but you can't flash a ROM, because it can't properly read the NAND, but can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple", so when flashing, ODIN wkll say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.
Let's start with the basic files, downloads and requirements​
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary files : the Kernel, the Recovery Package and the Bootloader (it's the old one, which you can easily use a USB JIG to reset the counter and remove the yellow triangle when having a custom kernel or OS)
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
And that is it! Let's get down to business
If your GSII has the folowing symptoms :
Bootloop
Stuck on GSII logo, but already removed the battery to try to fix it
Enters Download mode and Recovery mode
It means that you are soft bricked and is easy to solve.
But if your symptoms are the mentioned above, PLUS the symptoms below
Enters Download mode but does NOT enter recovery mode (usually means a NAND rw corruption)
Doesn't flash
Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)
Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.
It's time to open up ODIN and start reviving your phone!
First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :
{
"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"
}
As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way.
ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
THAT THE FLASH WILL SUCCEED.
Which means that you CANNOT have a damaged USB, corrupted drivers and such.
​
When recovering from a soft brick, it is recommended, not mandatory, to have Re-partition ticked with a .PIT file. So you must be extra careful when you are using a .PIT and Re-Partition. And obviously, the red box is the one where you can't and don't want to mess with
But where are the files going, you say?
.PIT -> PIT
CODE -> PDA
MODEM -> PHONE
CSC -> CSC
There is only 1 way to recover a soft bricked phone. How to recover from a NAND corruption? We'll get on that later on
Recovering a soft bricked phone​
1) Grab the Recovery Package, and you'll see a bunch of .tar files. Take a look at the names. You'll see CODE, MODEM, CSC and .PIT. Put each one in its place, and tick re-partition.
2) Turn off your phone. Enter Download mode by presing Vol. Up + Home + Power button.
3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9)
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!​
You deserve some cake afterwards, and some rest
Now, if your problem is the NAND rw coruption, and wasn't fixed by the above fix, then follow these steps :
5) Download the Kernel. Flash it in PDA. Without ticking Re-Partitioning
6) Successful? Nice, hope is still present.
7) Flash the recovery package, following steps 1-4 This should fix your issue. If it does not, then :
WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
8) Download the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partitioning
9) Flash the Kernel, as in step 5
10) Flash the recovery package, like in steps 1-4 And that will fix any of your issues
I hope that this guide was helpful, and if it was, hit the thanks button!
Credits mainly go to Intratech, for his amazing gallery of ROMS and files
_______________________
Disclaimer
This is to be used as educational information. I am not liable of any damage that may occur to your phone.

3/4/15 NEW HOWTO ROOT & install TWRP on DL701Q/DigiLand 7" Tablet 4.4.2 KitKat

3/4/15 NEW HOWTO ROOT & install TWRP on DL701Q/DigiLand 7" Tablet 4.4.2 KitKat
Ok, So you got your new Super Cheapo MTK8127 quad core Tablet from BestBuy or some other overpriced electronics emporium and want to install root and a custom recovery So it won't suck nearly as bad
Feeling hungry but don't wanna feed yourself??? Open wide......Here comes the airplane requesting permission to land
The Following procedure may "BRICK" your tablet and wipe your porn....You do so at your own risk, Neither Kneee or his lawyer claim to know ANYTHING about android....or anything else for that matter
THIS GUIDE WILL WIPE YOUR PORN!!!
If you've ever seen THIS:http://forum.xda-developers.com/chef-central/android/root-dl701q-install-twrp-touch-recovery-t2980339thread, You know that "iRoot/vRoot no longer works since updating to kitkat. I've BUNGLED my way into a solution, Hope it helps you too.....
THIS GUIDE ASSUMES YOU KNOW HOW TO USE ADB AND FASTBOOT (ENABLE USB DEBUGGING)OR AT LEAST KNOW WHAT THEY ARE AND DON'T SUFFER FROM GOOGLEPHOBIA
#1 Making a backup of this crap software when ADB , FASTBOOT and SP flash tool are working correctly is pointless (IMHO) (inm
Here's Everything you should need:
Stock ROM COURTESY...THIS DUMBASS https://drive.google.com/file/d/0B9DmzLnUt5tuaUtJS1FHcjNyX1U/view?usp=sharing
ADB_&_FASTBOOT_executables, no need to install, just extract the .zip to the directory of your choice and execute openCMD.bat with a right click + run as administrator. it will open a terminal window, you can run all your ADVB & FASTBOOT commands from there:https://drive.google.com/file/d/0B9DmzLnUt5tuM29vOTNHNEZya2s/view?usp=sharing
Driver installer & MTK_SP_FLASH_TOOL for MT8127 use this to install the drivers and flash the stock rom + custom recovery.img https://drive.google.com/file/d/0B9DmzLnUt5tudVlrSEtzSE1tWHc/view?usp=sharing
UBIFS_Modified_CWM FOR FLASHING UPDATE-SuperSU-v2.46.zip COURTESY Vampirefo: https://drive.google.com/file/d/0B9DmzLnUt5tueC04RDFVX3plTVk/view?usp=sharing
UPDATE-SuperSu-v2.46.zipflash this with vampirefo's modified CWM recovery image UBIFSRecovery4SuperSu.img" https://drive.google.com/file/d/0B9DmzLnUt5tuZjlmVm1Wc2tFUTA/view?usp=sharing
TWRP Setup.exe...Used to install TWRP recovery after flashing Stock ROM + Custom recoveryCOURTESY TWRP team & Protocol 9https://drive.google.com/file/d/0B9DmzLnUt5tuTVVJS2d2RERpbVk/view?usp=sharing
STEP 1: INSTALL THE DRIVERS INSIDE THE MT8127 SP_FLASH_TOOL.zip" file you downloaded It will install the mtk usb vCOM driver we need for the mtk8127. if u have questions PM vampirefo. after that, turn your tablet upside down, FIND THE reset hole and jam the nearest tiny object in there until the screen does something different (like go black) release the reset button, hold VOLUME DOWN and plug in the USB cord and the tablet should be reconized as a preloader USB VCOM Port device under "Ports" in Device Manager
{
"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"
}
So, the necessary driver to save this POS is at hand. after it's done installing the tablet will probably reboot and the remaining drivers will install. (EVEN WITHOUT THE OTHER DRIVER YOU CAN ROOT AND FLASH NOW)
Fire up the MT8127 SP flash tool (run as administrator) you downloaded and you should see this:
Click "Scatter-Loading" and select the scatter file located in the stock rom folder you downloaded and unzipped (you DID unzip it right?) and click the "RECOVERY" FIELD LOCATED HERE:
and select the recovery image you downloaded called "UBIFSRecovery4SuperSu.img......yay, you should be all set up and ready to go!
Make sure youve already unplugged the USB cable AND hit the reset button. HIT THE DOWNLOAD BUTTON (the program is now waiting for your device...no rush) HOLD VOLUME DOWN AND PLUG IN THE USB CABLE, the computer will detect the device, the program will proceed to shove a bunch of ones and zeros down the the tablets throat and it will reboot (hopefully to a mediatek logo).
If so, youre not as stupid as everyone says when u leave the room
Toss "UPDATE-SuperSU-2.46.zip" on a microSD, Power off the device, shove the SD in his home and hold POWER + VOLUME UP until you get prompted to select either RECOVERY OR FASTBOOT, we want recovery so make sure it's selected and press VOLUME DOWN to boot into recovery & install your SuperSU.zip and reboot
once the OS is fully running, run TWRP.exe as ADMINISTRATOR in AUTO mode, TWRP recovery should be installed and u should still have root, if not, you'll need to go into advanced, then mount system before re-installing from zip.
NOW learn ADB and fastboot so I can save my breath next time:
PS, all your GAPPS are gone....quit *****ing, I've got em here: htpa_gapps-modular-micro-4.4.2-20140608-signed.zip(pa_gapps-modular-micro-4.4.2-20140608-signed.zip 85.3MB) & HERE: https://drive.google.com/file/d/0B9DmzLnUt5tuSl9lME9VZnFJTU0/view?usp=sharing(pa_gapps-stock-4.4.2-20140608-signed.zip 267MB))
I have requested this thread be removed, you are using my stuff without permission, and even crediting yourself with the firmware, I took the time to download, you yourself have done nothing but take others work including mine without permission.

How to root the LG G3 Sprint (LS990) {Out Dated}

So first of all I have no idea if anyone has ever made a post on how to root the G3 (LS990) so I decided to go ahead and make one (to be helpful). This post was made on 3/4/15 check the date and make sure that this isn't to outdated
Code:
[COLOR="Red"]IF YOU DO THIS, YOU ARE AT THE RISK OF BRICKING YOUR PHONE/ BREAKING IT I AM NOT RESPONSIBLE IF ANYTHING HAPPENS TO YOUR DEVICE(S) READ CAREFULLY!!!!!!!!![/COLOR]
1) Make sure that you are on ZV4 you can check this by going into settings>About phone>Software Info>Software version. If it is not on ZV4 then you should refer to the help post below on help down grading.
2) If you are in fact on ZV4 then you need to enable "Unknown sources". This will allow you to download/install the application needed to root our device. Go into Settings>Security>Unknown sources make sure to check this and agree (press "ok") to the pop up.
3) Once you have enabled that go to this xda link and install this app on your phone: http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906. Download the latest copy and pull down your status bar and tap on the notification. You will be brought to a install menu now press "install" a security pop up will show up. Just say ok to it and allow the app to keep installing once it has installed press the "open" button.
4) Once inside the app press "Grind" a pop up will come up telling about brute force. Just say ok the reason for this is that our model (LS990) isn't officially supported but brute forcing will work so just let it run. Then turn up your volume and listen to the music good. Once it is done it will tell you to reboot, go ahead and reboot. Once you have gotten back into your system download this app from the playstore: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en this app will give you root access/ mange it. Once it is open you might be prompted to update the binary go ahead and update it. You will have two options "normal" or twrp/cwm" press "normal" and then reboot once it is completed:
{
"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"
}
.
5) Go to this thread and download the latest bumped twrp: http://forum.xda-developers.com/spr...recovery-twrp-touch-recovery-2-8-2-0-t2966096 make sure to download the .img file this is needed so that you can flash recovery. The is two ways of doing this 1) running commands from your computer or 2) using a app from the playstore called flashify: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en to make things simple we will use flashify.
6) Make sure the .img is in your download(s) folder and open flashify agree to the disclaimer and then grant it root access. Then click "Recovery Image". Then click "Choose a file" and navigate to your .img and select it. It will come up with a pop up just press "Yup" and it will flash. Now you can go ahead and be done just press the option to reboot to recovery. Or below I will link some videos with a how to boot into recovery so you can watch that to find the hardware key method. Or you can use this app it will reboot you really easily: https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en.
(Thanks goes to the creators of all of the work I have listed above! Make sure to thank them (thumbs up:good and maybe buy pro's/donate.)
----------------------------------------------------------------------------
Lollipop ZV8 ROOT (MAYBE)
Here is the link for the new ZV8 lollipop root: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 I have no idea if it works so just read carefully. If someone can PM me and tell me if it works that would be great. Also since the thread has instructions I will likely not make a guide.
How to down grade:
If you want to root as of (3/12/15) then you have to be on ZV4 or ZV8(look above) Some phones may come updated on newer builds and you may have to down grade them use this thread to accomplish this: http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
How to boot into recovery via hardware keys (Do the same thing just press volume up rather then volume down):
https://www.youtube.com/watch?v=waFrzMQivaI
How do I unlock my bootloader?:
As of now bump is the bootloader unlock without it we would not have a bootloader unlock. So pretty much (for the most part) by just installing the bumped recovery your bootloader is unlocked.
Can I update my phone once it is rooted?:
No, You cannot download a system update and update the phone. This will likely break it or really mess it up . What you have to do is install a rom that is all ready rooted and on the build you want I.E: "BarePop it is rooted" ZV8 or "BarRin" rooted ZV6.
For ZVA Phones
For phones that are running ZVA instead of ZV4 or ZV8, this tutorial helped me finally get rooted:
http://forum.xda-developers.com/sprint-lg-g3/general/one-click-root-zva-t3141390
Check under About phone > Software info > Software version to see what you have. It will be the last 3 characters after LS990 for Sprint phones.

How to root the Homtom HT16

Hi there,
I recently got the Homtom HT16 for just 50 bucks. I've always rooted my phones with a one-click rooting app(kingoroot etc.), but it seems not to work. I did some reading and saw you need TWRP to root the device. Now there is no TWRP for the device, saw on xda there was for the HOMTOM HT7.
Anyone knows if I can use the TWRP for the HT7 or is there any other way to root my phone?
Sorry for late response. On Russian forum you may find way to install recovery with Flash tool, however that didn't worked for me. Their TWRP recovery is useful for rooting. This is 100% tested, I own HOMTOM HT 16.
1. Install adb-setup-1.4.3 to enable adb, fastboot and Google USB driver on computer..
https://www.dropbox.com/s/wvsyab1iakpsswu/adb-setup-1.4.3.exe?dl=0
2.Settings-Developer optons Enable USB Debugging and Allow OEM unlocking
3.Put on sd card SuperSU-v2.78-201609011115 (this version worked for me).
https://www.dropbox.com/s/84xm1m7rxerg6kt/SuperSU-v2.78-201609011115.zip?dl=0
4. Turn off the phone, press Power and Volume up. You'll see new menu. Move with Volume up, choose Fastboot and press Volume down. Connect computer and phone with USB cable.
5. Find the directory where adb and fastboot are installed and position itself there . Hold Shift, right-click and choose Open command window here. ( If you are not the administrator, Windows 10 Start, Command Prompt (Admin) and position yourself in directory where fastboot is installed with cd command).
Copy TWRP recovery (recovery.img) in that folder.
https://www.dropbox.com/sh/t26oax8n96izp60/AACq00Cgo1iMFOWPAT8leRXZa?dl=0
5.Type and execute commands:
fastboot devices (check if device if recognized, you'll see the serial number)
fastboot oem unlock (press Volume up to unlock bootloader)
fastboot flash recovery recovery.img (install new recovery on phone)
6.Pull out battery, push it back . Hold Power and Volume up. You'll see new menu. Move with Volume up, select Recovery and press Volume down.
7. Don't make attention to blinking and bad performance of Recovery. Select Install, find SuperSu on sd card and install. If everything is ok, you will see notification that superuser is successfully installed.
8. Reboot phone and check with Root checker application root rights.
(optional) If you need restore factory recovery and remove Superuser, to keep warranty valid.
https://www.dropbox.com/sh/s6dvqr8ge72otfu/AACgOQ7CgrVk94o0_K6ACXtIa?dl=0
Hi, all I received yesterday the z11 max. Install recovery with super your and comborom V6.2 all ok. Problem does not update ota, it tells me no updates. I have made to the wrong? Thank you.
Hi.
After step 6. I could not enter in the new recovery menu. I get some error messages (attached picture) then the phone is restarting. What could be the problem?
{
"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"
}
---------- Post added at 06:41 PM ---------- Previous post was at 06:34 PM ----------
The image not visible, these are the error message:
'Could not mount /data and unable to find crypto footer'
`Unable to mount storage`
and so one....
pecs72 said:
Hi.
After step 6. I could not enter in the new recovery menu. I get some error messages (attached picture) then the phone is restarting. What could be the problem?
...
and so one....
Click to expand...
Click to collapse
I downloaded the original fw from needrom, then I put back the original recovery.img, so now it's as original, but without root...
I don't know what is the problem, this procedure worked on my phone.
Look here:
https://forum.xda-developers.com/s7-edge/help/twrp-mount-data-unable-to-crypto-footer-t3360331
**** my phone factory resseted it self
No matter what I do, my phone doesn't allow to be found when I make "fastboot devices".
Can someone that have rooted the phone please do a readback of the entire rooted rom and upload for me?
I'm facing a lot of problem installing the recovery , so if someone can please post a rooted rom it'll be useful ...
Edit : can someone backup his nvram partition? I lost my imei and with this phone any trick wont work...
dani the hack said:
Can someone that have rooted the phone please do a readback of the entire rooted rom and upload for me?
I'm facing a lot of problem installing the recovery , so if someone can please post a rooted rom it'll be useful ...
Click to expand...
Click to collapse
Hi, for me the SuperSU from holocen (see above):
togeter with the TWRP image, flashtools v5 and the description from needrom worked for me (not every emailprovider can be used to create an account):
needrom.com/download/homtom-ht16-4/
Greetings Rikski
Solution found in here!!
Use TWRP for cyanogen after installing it with sp tools v5.
Put SuperSU v2.82 or above in the phone or sd memory card go to custom recovery and install the SuperSU v2.82.zip file. Reboot and that's it. It works like a charm. :good:
7. Don't make attention to blinking and bad performance of Recovery. Select Install, find SuperSu on sd card and install. If everything is ok, you will see notification that superuser is successfully installed.
How long does blinking take usually? It blinks all the time, I can't select Install ?!
This phone has now nearly 30 ROMs on needrom.com
Plus a non blinking custom TWRP recovery, go check it out:
needrom.com->Doogee->Homtom->ht16
I tryed to follow the guide of holocen (also used much of external information) but right now i'm stuck in a bootloop.
First of all i needed hours of reading and troubleshooting to get my adb "cmd" working proberly with the "bootloader mode" (cause of a driver problem).
After i was successful ("fastboot devices. fastboot oem bootloader) , i tryed serveral twrp recovery *.img's (officials first, holocen's later on), but i can't get the ht16 out of bootloop. Recovery flashing seems to be successfull though.
If i try "volume up + power" and start up the recovery manually, i got the twrp splashscreen, followed by a huge chunk of red "unable to mount xyz..." with a following bootloop (there are only seconds to see whats happening, an then the "HomTom" splashscreen reappears). I tryed "fastboot erase userdata" with no help. Was insecure about the "fastboot erase system" command though.
Maybe some of you guys are eager to help. I really tryed to read up as much information i could about this topic. I thank you in advance.
Target was to root the phone and to install some kind of lightwight custom rom (just to get rid of those frikk'n "trojans, bloatware-viruses, marketing horrors" which are messing with the stock rom. Hopefully everybodys know right now what i'm talking about).
I try to respond quickly, but i can't garuentee.
Thank you very much for reading.
Best regards
B4dLuck

The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer care to fix it.

Hello Everyone!
I need urgent help from you all because I am currently stuck in a very bad situation. Please please please!! Help me to get out of this. Let me start from the beginning of whatever I did. This is going to be a very long post so please bear with me.
Why did I try to root my device?
I have Realme 1 which works on Android 9 and does not support internal screen recording. So I thought rooting would help me and I would be able to create gaming videos.
1st Phase:
I researched about how to root my device.
I came to know that first I’ll have to unlock my bootloader.
I tried to unlock my bootloader and when I was running the necessary commands like fastboot reboot, it simply showed, “Waiting for device…..”
Now confused, I went to the Device Manager and uninstalled Android and its drivers from the category of other devices by mistake. Now, my problem was that, how to pass commands to my device?
Next, I deleted everything, and started from scratch. This time, I connected my device (via the same USB cable) and I did something (I don't exactly remember what I did, but ultimately it lead me to Windows Update, where I clicked on View Optional Updates and updated the driver. I am attaching a screenshot of what I had installed.
Next, I downloaded platform tools, extracted them and in the address bar typed cmd and did the following checks to ensure that my device can receive commands.
When device was powered on:
adb devices
Returned: _________ device
Next command:
adb fastboot (Something like that which took it to the fastboot mode)
Next Command:
fastboot devices
Returned: _________ fastboot
Satisfied that I was going on well, I unlocked the bootloader using the respective commands.
2nd Phase:
Now I knew, my bootloader was unlocked, so I did the next step.
I switched to fastboot mode.
Downloaded boot_patched.img for Realme 1 C.50
Next, I pasted it into the platform tools folder.
Next, booted my device into the fastboot mode, and gave the flashing command.
Confirmed it on my device using volume up key.
Gave fastboot reboot command to reboot my device.
Downloaded Magisk Manager and rooted my device successfully.
Downloaded RootChecker app to be sure and got the positive result.
I downloaded the apps I needed.
Problem Phase:
I had downloaded a banking app but it didn’t work because my device was rooted, so I searched, “How to hide root from banking apps?”
I came to know that the solution for this was on Magisk Manager itself. Magisk Hide
So, I opened the Magisk Manager and I was shown a prompt to download something (Or maybe I downloaded something from the settings? It was something like system host module or something like that) Now I don’t exactly remember whether my device rebooted or not, but let me continue.
So, I went to settings, enabled Magisk Hide, selected the app from which I had to hide root and opened the app. It didn’t work.
I searched the internet and saw that I had to reboot my device as well.
After I did that I faced a more serious problem. The app was still not working and my sim cards were disabled.
Now I panicked, I did the ultimate thing for which I had rooted my phone, I downloaded the game and the screen recorder. I chose the internal sound recording option, it told me to download some Magisk Module for it to work. So I did it.But it still didn’t work.
Now I was sad, I didn’t know what to do. Then ultimately I opened my RootChecker app and check the root status of my device and you guys won’t believe what I saw.
" No proper root access granted "
Super Problem Phase:
I decide that I’ll unroot my device. So, I set down to work.
I got to know that I had to uninstall the Magisk Manager completely. I did so and my device rebooted.
There came a wave of relief, my sim cards started to work.
I thought that my device was unrooted now, so I opened my banking app and it showed: “Your device is rooted! You can not proceed further.”
I was confused, I checked the rootChecker and it clearly said the same thing. No root access.
So, I searched the web again and I was told that if I remove some files like su and one more file (I don’t exactly remember the name) then my device will be unrooted. I donloaded the es file explorer but didn’t find those files.
I searched the internet again and found something new. If I reset my device, then the root will go away. I was very happy. I did a factory reset of my device and this time I didn’t check the banking app, I did one more thing which I was not supposed to.
Ultra problem phase:
I got to the fastboot mode using the same commands in the adb terminal and decided to lock the bootloader. I thought that the app had detected that my bootloader was locked so that may be the reason it was not working. I gave the command:
fastboot flash lock
(it was something like this, I don't quite remember)
I confirmed that I wanted to lock my bootloader.
And that led me to my doom.
I rebooted my device using the command.
My device never started.
After the logo, or to say while booting I was shown this error:
"The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer care to fix it."
Then I though maybe I could just download the original boot and recovery file again then it would be all fine. I have those files and everything, when now I try to give those commands, they just show "Waiting for device...." Moreover the computer doesn't detect my device. The only thing I can do is just go to recovery mode.
Guys, I told you all everything that I knew please give me a detailed solution to the problem. I am also attaching some images so that you can see what exactly has happened.
Thanks in advance.
{
"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"
}
Sorry to say, but ... flashing unofficial/custom firmware and rooting has risk of bricking your device. And locking the bootloader was not the right/, best option
Maybe you have a chance to get it working again by flashing a complete firmware to it. Hopefully it will be successful after locking the bootloader

Categories

Resources