Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Let's begin with tutorial you will need
Samsung USB Driver
Odin3 (if you don't have DOWNLOAD HERE)
Latest twrp (if you don't have DOWNLOAD HERE)
if you have all this things we can continue
Run Odin3_v3.14.4.exe
You should see that window
{
"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"
}
Now click Options.
Output box should now change to this
Untick "F.ResetTime" and "Auto Reboot"
Now look at this
click the AP Button and select twrp-x.x.x_9-0-herolte.img.tar
after selecting twrp image boot into Download Mode using button combination
Vol down + home + power and hold until you will see
click Vol up to confirm
now plug in your phone to computer and on odin click "Start" button and wait until flashing will end
now hold Vol down + home + power and hold until phone will exit from download mode. now start holding
Vol up + home + power and hold until you will see twrp. now you should see
tick "Never show this screen during boot again" and swipe "swipe to allow modifications"
after that you will get twrp home screen this is time to put your rom to emmc/sdcard
i recommend this roms
[ROM][12L] [OTA Updates] crDroid v8.4 for Samsung Galaxy S7 (THREAD)
Havoc OS 3.x for Samsung Galaxy S7 (THREAD)
[ROM][12L][UNOFFICIAL][OTA Suppported][herolte] PixelExperience/ Plus Edition [AOSP] (THREAD)
[ROM][UNOFFICIAL] Pixel Extended ROM V4.0 Android 12 [herolte] (THREAD)
ROM[R][Unofficial] DotOS v5.2 for Samsung Galaxy S7 (THREAD)
but if you want you have on xda many roms for herolte (ALL ROMS)
after puting your rom to emmc/sdcard go to Wipe>>Advanced Wipe. Tick "Dalvik/ ART", Data, System And swipe now get back to twrp home and click "Install" now locate your rom zip and click on it(if you have ROM on sdcard click Select Stoarge>>Micro SD card and click ok)
now you should get screen like this
now swipe to confirm flash and wait until flashing will end
After flashing you should get output smillar to this
(Optional) Flash Gapps, root or xposed
Now Reboot System
Congratulations! you successfully flashed your first custom rom
if I made a mistake here. you can correct me in comments​
Zordon,
Please consider changing the title of this thread to SM-G930F instead of Samsung S7.
Related
I only started a new thread on this because I figure the post I made in the other thread with the file might end up getting lost.
This OTA is interesting. Though it includes no firmware update (i.e. radio, PRI, NV, WiMax), it does include Sprint's new "Connections Optimizer" which is supposed to help with battery.
Something else it includes (which I found unexpectedly) is the patent-abiding new App Associations screen (anyone that pre-ordered an EVO 4G LTE knows all about this). So it does appear that HTC is rolling out an update to all devices to "correct" this issue.
First off, keep in mind this is the straight OTA file - it has not been rooted or otherwise touched. If you're running stock, unrooted, and want to apply it, you can save it to the root of your SD card, and rename it "update.zip". Then boot into Recovery from the bootloader (disable "Fast boot" under "Applications", power device all the way off, and then hold volume down button while powering on until HBOOT appears. then choose "RECOVERY" option). When you see the phone with the red triangle & exclamation point, press both volume buttons and the power button at the same time. Some yellow error text should appear first (ignore that), and wait a few seconds until the menu appears. Use the volume buttons to select the apply update zip option, and then navigate to the file. Press the Power button to apply.
NOTE: I've only been using this OTA for a few minutes, and my phone keeps hot rebooting. I wonder what's up with that?
EDIT: If you want the full ROM, stock & rooted, based on this OTA, get it here.
EDIT 2: If you want the new kernel from this OTA, get it here.
DOWNLOAD (Dev-host)
Screenshots:
{
"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"
}
Thank You x1000.
OTA Installation failed. Tried this from revolutionary recovery. Bada Bing/Boom. upon reboot system tells u to do the update since i guess it didn't detect the installation.
EVO 4G(not really) Rooted with 5.07.651.1
click.mine said:
OTA Installation failed. Tried this from revolutionary recovery. Bada Bing/Boom. upon reboot system tells u to do the update since i guess it didn't detect the installation.
EVO 4G(not really) Rooted with 5.07.651.1
Click to expand...
Click to collapse
Revolutionary is a Clockwork Mod recovery. You need to be using a RA-based recovery (otherwise the firmware won't flash). And this will only work if you're running an unmodified stock ROM based on the 4.67 OTA (the release keys and /system content must match).
Is there any advantage in using this over y5 battery saver?
sent from my Supersonic on Digital Karma v7.7 w/ Tapatalk 2
Hey there,
I got my Galaxy S4 and I wanted to install CWM and custom Roms. Because the phone is fresh there is no custom recovery to install zips with and I don't want to use strange rooting methods. I put the phone into download mode, started Odin, selected a CWM_<...>.tar as PDA and pressed Start. The flashing seemingly went well but I can't enter the recovery with power + home + volume up. The phone tries to launch it but then just shows the battery icon you see when charging it while its off.
I went back into download mode and noticed there was a message saying "Write Protection: Enable". Whats this supposed to mean? Can't I use Odin? Do I need to unlock the bootloader or something like that? Thats what I had to do on my HTC Desire but when I installed a custom recovery on my brothers Galaxy S3 I could just use Odin.
Here's a screenshot of the download mode.
At least my Knox is still on... yeah...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you only try to flash the recovery:
Then uncheck auto-reboot before flashing.
Saenic said:
Hey there,
I got my Galaxy S4 and I wanted to install CWM and custom Roms. Because the phone is fresh there is no custom recovery to install zips with and I don't want to use strange rooting methods. I put the phone into download mode, started Odin, selected a CWM_<...>.tar as PDA and pressed Start. The flashing seemingly went well but I can't enter the recovery with power + home + volume up. The phone tries to launch it but then just shows the battery icon you see when charging it while its off.
I went back into download mode and noticed there was a message saying "Write Protection: Enable". Whats this supposed to mean? Can't I use Odin? Do I need to unlock the bootloader or something like that? Thats what I had to do on my HTC Desire but when I installed a custom recovery on my brothers Galaxy S3 I could just use Odin.
Here's a screenshot of the download mode.
At least my Knox is still on... yeah...
Click to expand...
Click to collapse
turn off your phone, pull out the charger before enter recovery mode or you need to press power + home + volume up key for 8 second then it reboot to recovery
Hello everyone,
First of all, I apologize if this post is in the wrong section. Also I'd like to say how awesome it is everyone that is involved in these projects.
My Issue is I can't get ANYTHING to work, I have tried so many roms that apparently work for my phone and I always, foot errors, signature errors though the adb. I have tried every program to unlock bootloader but apparently does not work unless you are running V2 551 2.40.*.* so I went and downloaded this, and wants again can't flash the ROM. The unlock bootloader was weird, I went through all the installation and I don't even know if it worked to be honest. I can boot into the phone via power and volume down, and get a menu that includes, apply apps from ADB, wipe/restore phone, fastboot mode * which goes as far as my phone saying *FASTBOOT !!!* then thats it will not continue. The power and volume up does the same thing. So basically I'm starting to think this piece of crap phone will never have a decent operating system on it. The phone is in developer mode and USB debugging is on also. * Basically have done every single tutorial I can find and nothing works*. Also the twrp doesn't even work. I have even tried flashing back to an older version on the phone and get the same ADB errors. I have installed all the ADB and also minimal adb and fastboot and all drivers for the phone as well. * TRYING NOT TO MISS ANYTHING*
My phone specs:
Model: ASUS_z00LD
Android: 5.0.2
Baseband Version: 202c10_10.0.0_160120
Kernel: 3.10.49-gec27b65
Build: LRX22G.WW_user_1.17.40.1106_20160202044030520_2015052101030010000300001
IMAGES:
{
"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"
}
Hope it works
Did you try to unlock bootloader the official way? I myself unlocked the ZE550kl following this thread http://forum.xda-developers.com/zenfone-2-laser/general/ze600kl-official-bootloader-unlock-t3273263
You can check if bootloader is lock or not from fastboot by entering "adb>fastboot oem device-info" should show up somewhere between the lines "Device unlocked: true"
After unlock only then you can install Official recovery TWRP 3.0.0-0 from here http://forum.xda-developers.com/zen...recovery-twrp-3-0-0-0-touch-recovery-t3317513 .
If needed TWRP will also help you root your phone once is installed.
Good luck!
I wanted to install a custom ROM, resurrection remix.
[ROM][9.0.0_r46][A2017X][OFFICIAL] Resurrection Remix 7.0.2
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included...
forum.xda-developers.com
I gathered a whole bunch of information on this and decided first I needed to unlock the boot loader, maybe get fast-boot to work? (which is removed?) and install a custom recovery first. For this I was using the Axon7Toolkit-v1.2.1.
Thing is I tried to flash the recovery with the Axon7Tool and now I am stuck on this green ZTE logo loading screen, the device is already formatted.
https://github.com/bennykor/Axon7Toolkit/releases
I have previously installed ROM's on other phone's but not sure what is going on with this one?
I can't really seem to get it to boot up into anything else or connect it to ADB to see what is going on and it is also not detected anymore by the tool. Not much of what I have previously done seems to work on this thing...
Can you get into the bootloader?
Turn phone off, hold 'vol +' and 'vol -' and 'power' buttons, once phone turns on release 'power' button.
shpitz461 said:
Can you get into the bootloader?
Turn phone off, hold 'vol +' and 'vol -' and 'power' buttons, once phone turns on release 'power' button.
Click to expand...
Click to collapse
Hey yeah that did work actually, althought when I selected the recovery mode option it restarted to the logo again and I have to wait until the battery drains now because I can't seem to turn it off.
EDIT - Doesn't seem to detect it in adb though, not sure where to go from here.
oops -delete-?
Bootloader/download modes are not related to adb, you need to use 'fastboot' tool instead of 'adb' tool.
Did you try to boot into bootloader and then run an RUU from a pc while the phone is connected via cable?
shpitz461 said:
Bootloader/download modes are not related to adb, you need to use 'fastboot' tool instead of 'adb' tool.
Did you try to boot into bootloader and then run an RUU from a pc while the phone is connected via cable?
Click to expand...
Click to collapse
Ah I didn't realize this. I am trying to flash with fastboot now but I get an error and also with the axon7tool (on github) I get this error:
{
"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"
}
Thing is I read use fasboot clear cache but this also yields the same error.
fastboot doesn't work in bootloader for flashing, you need to boot into download mode and then use fastboot commands to flash partitions.
Flashing usually fails the 1st time so just run the same command again and it will go through (it prompts you that on the screen).
shpitz461 said:
fastboot doesn't work in bootloader for flashing, you need to boot into download mode and then use fastboot commands to flash partitions.
Flashing usually fails the 1st time so just run the same command again and it will go through (it prompts you that on the screen).
Click to expand...
Click to collapse
Ok but but the only two options I appear to have left here is to hold "volume up/down power" for fastboot mode or go into FFBM mode? (Also gives some message about devices cannot be checked for corruption when bootloader is not unlocked)
Do i need to go into download mode from android?
Download Mode ZTE Axon, how to - HardReset.info
The whole list of secret codes for your device. Check out how to get access to hidden mode, advanced features and secret options.
www.hardreset.info
Because I doesn't appear to be working for me with this button combination.
So I can't really get any of this fastboot flashing to work it keeps either giving the error "To many links" or "FAILED (Write to device failed (Unknown error))" ?
Fixed here: https://android.stackexchange.com/q...e-failed-no-link-unknown-error-too-many-links
Hi,
first of all: I'm a noob and I've got no idea what I did. I appreciate all of your help to get my phone back alive!
My phone (Samsung Galaxy S8, SM-G950F, stock ROM, Android 9.0, not rooted or anything else) is stuck in recovery mode. It doesn't react to any buttons (e.g. very-long-press power button) or connecting a USB cable, also my PC and Odin with all drivers installed won't recognise the device.
What I did: I went into download mode to check if I could find my RMM status (I didn't) and navigated to "view recovery logs". I entered /cache/recovery/last_log and scrolled through it until I reached "back". I confirmed with the power button and - then I can't really remember what was there on the screen - I got into a similar log screen. It took a while and I pressed the Vol-down key quickly numerous times.
Then it happened: there was a screen with some options to choose from (written in blue) but spamming the button I probably entered something. Another log (or whatever) showed up --> see photos. It took about 20-30 minutes to reach 100% and then went back to the Android recovery screen, where it's been stuck for about an hour now. I tried cancelling it numerous times times with long-pressing power button, but nothing happened.
{
"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"
}
(log) (log) (log at 100%) (the screen where it's stuck now, detailed pictures attached)
PLEASE help, is there anything I can do besides waiting for the battery to die and reboot?
Big thanks in advance!
---
Note: the device has been factory reset recently with no data on it, OEM unlocking and USB debugging were checked in developer options as I was about to flash TWRP.
1)Download stock firmware from sammobile or else (exact your device and model)
2) Download Odin
3)See video on youtube if noob(obviously ) to flash stock by going to download mode
After successful installation u will have your cell back
Cheers......
Thanks for the advice, but I found that pressing Power + Volume Down for 20+ sec. could eventually shut down the phone. After that it rebooted into recovery mode, even though it took ages.
Now I'm a happy owner of a LineageOS S8 btw
Entering download mode wouldn't have been possible at the stage I described in my first post, as the device didn't react to anything at all.