Database Info

[HOWTO][TAR][BLAZE 4G] THE ODIN THREAD :: Return to stock, fix soft brick :: 4/9/12

k0nane presents...
Odin: Return to Stock, fix soft brick
Sponsored by k0nane.info. Have you tipped your devs today?
DO NOT CHECK REPARTITION! YOU HAVE BEEN WARNED!​
Why the big red warning? Far too many people have broken their devices by not following these instructions! Search the forums, or drop by IRC - you'll see plenty of examples.
These instructions should fix your soft-bricked or broken phone as long as you can get it into download mode. Make sure you have drivers already installed on your Windows computer before starting. Please read them all the way through and then begin.
Code:
#include <external/cyanogenmod/std_disclaimer.h>
/*
* 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.
*/
Instructions​
Download Odin 1.85 - see section below.
Download the stock TAR for your device - see section below.
Extract the contents of odin-185.zip and the 7zip archive.
Run Odin 1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Click PDA and select the TAR you downloaded. Click PIT and select the PIT your downloaded.
Put your device into Download Mode:
Connect the USB cable to your PC, but NOT your device.
Remove the battery.
Reinsert the battery.
Hold down Volume Up + Volume Down + Power.
You should now be at Download Mode. Make sure Odin looks similar to the following:
{
"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"
}
Click Start in Odin.
Wait! When complete, Odin should appear like the following:
That's it! Your device will autoreboot, and your phone should be working properly again. Be sure to wipe data in recovery after completing this process if you have further issues.
Downloads​
Download Odin 1.85
Download PIT
Download Stock TAR
Download Stock TAR (Mirror)
​
Credits:​
DrTaru: stock device, remote access, lots of testing, screenshots, patience
Shabbypenguin: Shabbypenguin (do I need to say more?)

P-O-S-T :: R-E-S-E-R-V-E-D
Original artwork by Pendulum via Gasolin3.
...for future use.
Follow me on Twitter @k0nane and @publik0!​

boom! once again

No 4G or Wifi Afterwards...
I just did the Factory Recovery on my phone 'cause I messed something up and now I can't get the 4G or Wifi to work... I'm connected to the Wifi Network and 4G icon is on my phone but there's no internet connection...any help please?

Hi
I need 2 folder app and framework to build some app then send to my friend because my friend don't know how to copy it from system. Please use root explore to copy it then upload for me .
Thanks

Desertstorm00 said:
I just did the Factory Recovery on my phone 'cause I messed something up and now I can't get the 4G or Wifi to work... I'm connected to the Wifi Network and 4G icon is on my phone but there's no internet connection...any help please?
Click to expand...
Click to collapse
Wipe cache and data in factory recovery.
doantri said:
Hi
I need 2 folder app and framework to build some app then send to my friend because my friend don't know how to copy it from system. Please use root explore to copy it then upload for me .
Thanks
Click to expand...
Click to collapse
Extract them from the system image yourself.

stuck at param.lfs
anyone else stuck at param.lfs when trying to restore to stock??

mayesmwhite said:
anyone else stuck at param.lfs when trying to restore to stock??
Click to expand...
Click to collapse
Use a non-stock USB cable, and switch ports on your PC. If you continue to have issues, redownload the TAR or use another computer.

Ok, yes this is my first post and yes, the "don't check Re-Partition!" is in red everywhere... and I am a relatively experienced at rooting devices (this is the second Blaze I was doing, first one rooted with zero problems... That being said: What are the recovery options if one does open a new tar using oden and forgets to un-check re-partition (like I did earlier today)?
I have since flashed both the recovery rom and CWM, however the phone still prompts me for a password and after I input the correct password it goes into a boot loop.
Steps taken:
1. Flashed the k0nane root kernel and forgot to uncheck re-partition. ( Yes I know... laugh it up... )
2. Dropped the F-bomb in front of the kids about 1 second after pressing "Start" once I realized what I had done...
3. Followed the "THE ODIN THREAD: Return to stock instructions, fix soft brick"
4. At the hard reset part where you go into recovery mode I received the green/red dot screen response
5. Successfully flashed the CWM, therefore fixing the green/red dot recovery mode issue
6. Performed a hard reset using CWM, however...
After all this I still am getting the prompt for password (I would have expected a factory reset would make this go away) and subsequent boot loop upon entering the correct password.
Would saving a CWM recovery rom to my sd card of my "good' Blaze and transferring/flashing it to my broken blaze fix the issue?
Edit:
- I tried it (flashing my other blaze's recovery rom) and no it does not fix the password prompt to boot loop issue... (It didn't make anything worse either... how is it I can flash a rom and still have a password prompt (my working droid is not password protected...)?

chlor3 said:
Ok, yes this is my first post and yes, the "don't check Re-Partition!" is in red everywhere... and I am a relatively experienced at rooting devices (this is the second Blaze I was doing, first one rooted with zero problems... That being said: What are the recovery options if one does open a new tar using oden and forgets to un-check re-partition (like I did earlier today)?
I have since flashed both the recovery rom and CWM, however the phone still prompts me for a password and after I input the correct password it goes into a boot loop.
Steps taken:
1. Flashed the k0nane root kernel and forgot to uncheck re-partition. ( Yes I know... laugh it up... )
2. Dropped the F-bomb in front of the kids about 1 second after pressing "Start" once I realized what I had done...
3. Followed the "THE ODIN THREAD: Return to stock instructions, fix soft brick"
4. At the hard reset part where you go into recovery mode I received the green/red dot screen response
5. Successfully flashed the CWM, therefore fixing the green/red dot recovery mode issue
6. Performed a hard reset using CWM, however...
After all this I still am getting the prompt for password (I would have expected a factory reset would make this go away) and subsequent boot loop upon entering the correct password.
Would saving a CWM recovery rom to my sd card of my "good' Blaze and transferring/flashing it to my broken blaze fix the issue?
Edit:
- I tried it (flashing my other blaze's recovery rom) and no it does not fix the password prompt to boot loop issue... (It didn't make anything worse either... how is it I can flash a rom and still have a password prompt (my working droid is not password protected...)?
Click to expand...
Click to collapse
This thread might help you out. Brick 2 Fix

I was hoping i had stumbled upon a new way to fix my "soft brick" since not everyone has access to two phones..
-chlor3

chlor3 said:
I was hoping i had stumbled upon a new way to fix my "soft brick" since not everyone has access to two phones. I am still considering installing dropbear to the good phone using CWM and flashing to the broken phone in an attempt to get shell.
-chlor3
Click to expand...
Click to collapse
Do you have a working Blaze? If so, I only need two partitions... Anyone? Our only Blaze owner on IRC returned his.

I'm thinking of returning mine too. Its really a let down coming from my vibrant

k0nane said:
Do you have a working Blaze? If so, I only need two partitions... Anyone? Our only Blaze owner on IRC returned his.
Click to expand...
Click to collapse
I can attempt to help you get what you need. I'm fairly new to this stuff but would be happy to help if I can.

So I tried out the CM7 alpha and it froze at the loading screen. I'm doing it wrong and can't figure out how to get a logcat.
I'm trying to get back to stock and it seems to work other that the 'market' app is greyed out and it says that it's not installed on my phone. I've tried re-rooting and cwm and still the market app is greyed and doesn't show up anywhere other than the app drawer.
When I flash back to stock via Odin, I'm already past the gmail login part.
Even after adding cwm, I can't figure out how to get to recovery via hardware buttons to wipe or whatever.
Anybody have any ideas?
Nevermind maybe. I added a Google Play apk and now things are syncing up. I'm not sure what happened though.

So it looks like I may be the only one messing this up...
I flashed the cm7 alpha a bit ago. It's making progress.
Now that I'm trying to get back to stock I'm getting a loop between the Samsung logo and the Android blasting off.
I flashed the cwm but can't for the life of me figure out how to boot into recovery using hardware keys.
Anybody have any ideas? I'm lost w/ a useless phone ha.

Try this
1. Turn off phone
2. Remove battery
3. Plug USB from computer to phone
4. Insert battery
5. Hold volume up + volume down
6. While still held push and hold the power button keeping all three pressed
7. Wait for Samsung logo to appear
8. When screen goes black wait half a second and release all buttons
9. In a second or 2 should be in recovery
If that doesn't work please leave outcome, I have another method if that fails
Sent from my SGH-T769 using xda premium

xArcane1x said:
Try this
1. Turn off phone
2. Remove battery
3. Plug USB from computer to phone
4. Insert battery
5. Hold volume up + volume down
6. While still held push and hold the power button keeping all three pressed
7. Wait for Samsung logo to appear
8. When screen goes black wait half a second and release all buttons
9. In a second or 2 should be in recovery
If that doesn't work please leave outcome, I have another method if that fails
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
im boot looping like in the above thread between the samsung logo and the android screen - ive tried 2 different cables/and downloads
im coming from root and cwm - but needed to go back to stock...
...im not a noob but im stuck and kinda shrugging - help? lol
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
of course im using odin - all succeeding - not failing as odin reports
getting to root and cwm were simple seems this should be but just looping
---------- Post added at 03:52 PM ---------- Previous post was at 02:57 PM ----------
well - nevermind my post although its apparently happening to some devices.
i found a nandroid backup on my SDCARD thankfully i hadnt deleted (as im going back to my g2x lol) - and after i ran it everythings fine; did a factory reset on it and it appears to be good; not sure if it's kept root and wont know until i install tb again on it - but thanks for now guys!

The stock tar file isn't being recognized by Odin b/c it's not a "tar" file. Can someone please advise how I can get Odin to recognize it? I really need to get back to stock.
Thanks

Did you unzip and extract the contents of the zip? Hopefully that will help you
Sent from my SGH-T769 using xda app-developers app

Galaxy S6 0mb TWRP / no OS! Help wanted, i do not want an brick

I have Galaxy S6 and when i tried to install new ROM via usb-otg stick something strange happened and now my whole phone is unusable.
TWRP just says 0mb for internal storage and i cannot install anything since i cannot mount anything. I have looked pretty much all the "fixes" but nothing has helped so far :\ I have tried to format, wipe, change partition type, install, etc. And nothing has helped me so far. So if there are any ideas left please help :]
I think i still have root and when entering TWRP it does not ask password since i have done dm-verify long time ago.
Here is video showing some of the things: https://youtu.be/wXVVRBmRROU

go to download mode and flash stock firmware with ODIN. than flash twrp, enter recovery (twrp) before system. and boot to stock.
than try again.

HowJesNo said:
go to download mode and flash stock firmware with ODIN. than flash twrp, enter recovery (twrp) before system. and boot to stock.
than try again.
Click to expand...
Click to collapse
Hi!
I got stock firmware from Updato and then began to flash with Odin and it seemed that it would work since it was actually doing something at first (while trying to flash ROM's Odin crashes) but then it gave an error and stopped :\ Here is an picture of Odin's log.
{
"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"
}

I guess you had better restore factory image, make sure the system comes back. then flash updated version OS.
You can trying to use ODIN to do that. or using fastboot flash .....
https://gs6.gadgethacks.com/how-to/unroot-restore-samsung-galaxy-s6-back-stock-0162155/
Hope to it is helpful.
DARKKi said:
I have Galaxy S6 and when i tried to install new ROM via usb-otg stick something strange happened and now my whole phone is unusable.
TWRP just says 0mb for internal storage and i cannot install anything since i cannot mount anything. I have looked pretty much all the "fixes" but nothing has helped so far :\ I have tried to format, wipe, change partition type, install, etc. And nothing has helped me so far. So if there are any ideas left please help :]
I think i still have root and when entering TWRP it does not ask password since i have done dm-verify long time ago.
Here is video showing some of the things: https://youtu.be/wXVVRBmRROU
Click to expand...
Click to collapse

Okay, i have new problem. After i tried to flash with odin now i got only one place i can boot into and it looks like this:
I downloaded Smart Switch and entered emergency recovery but i was met with this screen and i have no idea from where to get the code.

in smart switch emergency upgrade and initialization, if will ask model and S/N.
model is SM-G920F and S/N in on the back of the phone. all caps.

HowJesNo said:
in smart switch emergency upgrade and initialization, if will ask model and S/N.
model is SM-G920F and S/N in on the back of the phone. all caps.
Click to expand...
Click to collapse
Smart Switch did not even have that option but i tried it with Kies and got this

smart switch should have same option. I found googling that in never versions that option was not functional due to Samsung not wanting people to debrand their phone. so older version is needed.
just got mine in a similar bootloop.
can u get into download mode?
If phone can't turn off do this:
- hold volume down + power, (that is reboot)
- as the screen goes black move finger to volume up + home key.
that should get you to download mode. now use odin to flash stock firmware.

HowJesNo said:
smart switch should have same option. I found googling that in never versions that option was not functional due to Samsung not wanting people to debrand their phone. so older version is needed.
just got mine in a similar bootloop.
can u get into download mode?
If phone can't turn off do this:
- hold volume down + power, (that is reboot)
- as the screen goes black move finger to volume up + home key.
that should get you to download mode. now use odin to flash stock firmware.
Click to expand...
Click to collapse
I tried that before and i tried it now again and same result:

is that firmware higher version than one previously installed?? i had that issue once!
G920FXXE5EQJ1........ try with any other with higher number. UK (BTU) is G920FXXU6ERC9

The problem is hidden.img file.
Search in google "galaxy s6 hidden.img fail" and solved.

HowJesNo said:
is that firmware higher version than one previously installed?? i had that issue once!
G920FXXE5EQJ1........ try with any other with higher number. UK (BTU) is G920FXXU6ERC9
Click to expand...
Click to collapse
Hi! I got the Model name but for some reason i cannot find S/N in the box or anywhere else
vindau said:
The problem is hidden.img file.
Search in google "galaxy s6 hidden.img fail" and solved.
Click to expand...
Click to collapse
Thanks a lot for this! I was able to install stock rom.
---
But then trouble started again. Boot screen came up and then text and mount problems like "failed to mount efs (no such file or directory)" :crying:
Here is the video about it, anything i could do now? I installed TWRP and it still says internal storage 0mb and formatting has no effect.
Video - https://youtu.be/OBfhTRWUZeU

I got little progress. I found the S/N from back of the phone with torch which i could not see without (Thanks for Augustin @ XDA Discord for this!) and then i tried to use Smart Switch but it does not recognize the phone and only option is "Emergency Firmware Recovery" and it needs some recovery code.
Then i tried Kies and it does not detect the device either and i tried the option "Firmware Upgrade and Initialization" and typed out model and S/N and after that it said "SM-G920F" does not support initializing"
So anyone knows what i could do now? Seems like i am running out of options here
Augustin also said that i should try pit but i have never used that feature in Odin so help with that would be awesome if it can remedy this situation somehow

You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459

allensd.cordero said:
You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
Click to expand...
Click to collapse
Thanks a lot! I will begin investigating and learning!
Hopefully this would solve this damn problem
And thanks a lot for this info!

allensd.cordero said:
You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
Click to expand...
Click to collapse
Thanks a lot! Finally using pit got the partitions right and phone is working like a charm now! :]

This might be a bit late but I am also currently in the same situation with my S6. Somewhere in the thread it said something about pit files but I don't really understand what to do. For reference, my issue is the exact same as OP's with the unmountable partitions and unbootable system. Would someone be kind enough to help out? My device is a SM-G920F from Vodafone (UK)

How I downgraded from Pie to Oreo

This is how I downgraded from Pie to Oreo. I can't guarantee it works for everyone but it worked for me. It required an SD card and a computer.
This is not a guide for the android development savy users but for people who preferred oreo to pie. It works without an unlocked bootloader and an unrooted phone. You will have to wipe your data so backup everything beforehand!
STEP 0) Remove your google account from your phone so you can prevent it automatically updating to Pie on first boot. Go to Settings > Accounts and remove your google account from the phone.
1) First download the zips that include Oreo with the November security patch and the December security update. Put these in the root of the SD card and rename them so you remember which is which.
I have found November Oreo links for both TA1012 and TA1004 but reportedly they both work for all Nokia 8 phones as the main payload.bin file is the same. I used the TA1012 zip with my TA1012 phone.
THMSP said:
https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
Don't worry about the TA-1004 stuff, all Nokia 8 software is generic, only google makes a difference between the model IDs.
Click to expand...
Click to collapse
MD5: 07e5b0c46e86919a66d2e6279613047d
TeddyBeers said:
Rollback for TA-1012 from Pie Beta to Latest Oreo
Official link just captured a minute ago.
https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip
Click to expand...
Click to collapse
MD5: e00affc410525d63200c0c18bc8e0622
December Security update can be downloaded here (file is called NB1-488L-0-00WW-B01-488K-0-00WW-B01-update.zip):
https://tmsp.io/fs/xda/nb1/ota/
MD5: a8ed8cac0cf4dd7763f9dd0fb00971d5
2) Boot into recovery mode.
a) To do this on Pie, plug your phone into a computer and wait for the drivers to get installed. Windows 7 downloaded a few megabytes from windows update for this.
b) Unplug your phone and turn it off. Hold Volume up and plug your phone into your computer. Keeping holding volume up.
c) When the sad android appears with 'No command' showing, release Vol+. Hold the power button and press Vol+ to get into the recovery menu.
3) Use the Vol+ and Vol- to navigate down to 'Apply Update From SD card' click the power button to select it. In the next menu select the November Oreo zip file. It'll then verify the downloaded zip and install it. This takes a few minutes.
4) Select Wipe data/factory reset from the recovery menu. You need to do this cause data created on Pie doesn't work on Oreo.
6) Repeat steps 3 & 4 for the December security update. I don't know whether you need to factory reset both times but it shouldn't do any harm.
5) Finally select Reboot system now and it'll boot into Oreo. This takes a few minutes.
6) Don't connect to any wifi during setup. Go to settings > system > about phone. Tap the build number at the bottom until you unlock developer options. Go to settings > system > developer options and disable Automatic system Updates.
Hopefully this helps someone. Thanks to @THMSP, @TeddyBeers and @al mak for various posts that helped me downgrade and write this guide.

That's exactly the way to do it.
Actually works both ways as upgrade or downgrade, as Nokia kindly provides full rom oreo/pie instead of just incremental update.

Usb debug need to be enabled or not?

Setup updates from Android 8 back to Android 9 Again
Useful guide, thanks, but after downgrading from Pie to Oreo how do you avoid being forced to upgrade to Pie again in setup, after you Wipe data/factory reset the phone?
I downgraded back to Oreo from Pie, but when I restart in setup I get forced to search for updates and it finds, downloads and installs the Pie update again, and I dont seem to be able to avoid it?

Disable in Developer Options
nb111 said:
Useful guide, thanks, but after downgrading from Pie to Oreo how do you avoid being forced to upgrade to Pie again in setup, after you Wipe data/factory reset the phone?
I downgraded back to Oreo from Pie, but when I restart in setup I get forced to search for updates and it finds, downloads and installs the Pie update again, and I dont seem to be able to avoid it?
Click to expand...
Click to collapse
You have to enable Developer Options then disable Automatic system updates. You will always get the notification that a system update is available but it will not download automatically. Going further, you can even turn this notification off and forget about it.

The problem is that it happens before you get to a point where I know how to access the developer menu to do that.
It happens during the setup wizard, which I can't see how to complete without selecting a wifi network or mobile network, it then searches for downloads and installs the update before it sets up the phone and drops me at the home screen.

nb111 said:
The problem is that it happens before you get to a point where I know how to access the developer menu to do that.
It happens during the setup wizard, which I can't see how to complete without selecting a wifi network or mobile network, it then searches for downloads and installs the update before it sets up the phone and drops me at the home screen.
Click to expand...
Click to collapse
I've been having the same issue. I think it is new. I've done the process as early as January 9th with no forced update. As of yesterday it is forced. I've posted my experience in the thread for NOST. Pie may be life now because there are no custom ROMs and I expect all Oreo ROMs to have the force update thing inside them.

ululalbab said:
Usb debug need to be enabled or not?
Click to expand...
Click to collapse
Not as far as I am aware, though it might be needed if you are booting into recovery mode bia adb.

@nb111 @hodiedodie
Is it possible to either get through the entire setup without connecting to any network - you will have to forgo logging into a google account at first. Or only use mobile data in the hopes that google is smart enough to realise that people don't want to download 1.5GB on their data plans?

Optimus_Toaster said:
@nb111 @hodiedodie
Is it possible to either get through the entire setup without connecting to any network - you will have to forgo logging into a google account at first. Or only use mobile data in the hopes that google is smart enough to realise that people don't want to download 1.5GB on their data plans?
Click to expand...
Click to collapse
I doubt I'll do this myself but I would suggest doing a man in the middle attack on the phone with arpspoof in a Linux distro. Use Wireshark to see what servers it calls out to. Then I would go in my home WiFi router and block those IP addresses. Then reset the phone and connect to the WiFi network and see if that works.

Ok solved this one, had to Update to P remove the Google Account linked to the Device and downgrade again.
It's Part of the Factory Reset Protection that you cant skip the Wifi and Update Screens.

thanks a lot ，my ta1052 downgraded successfully use your 1004firmware

fushanhu said:
thanks a lot ，my ta1052 downgraded successfully use your 1004firmware
Click to expand...
Click to collapse
Do you still have dual sim support? All bands work as before downgrading with 1004 firmware?

jskamxmxm said:
Do you still have dual sim support? All bands work as before downgrading with 1004 firmware?
Click to expand...
Click to collapse
I didn't try out dua sim because i have only 1 sim and it works well . don't worry bro, any problem can be solved as long as you done downgrade，it's easy to unlock BootLoader under Oreo ，so you can flash your original official firmware use OST tool or NOST in case any issue . （i downloaded my TA 1052 firmware from google，but i didn't flash it because this 1004 so far no problem）
i downgraded because my battery drained very fast and phone became hot frequently ，but i cant find any other way to downgrade or unlock BootLoader under Pie ，the official unlocking method doesn't working with Pie. i unlock it successful after downgrading by flash this 1004 stuff .
There's a small surprise when flash 1004 firmware，it's showing failed:'version old ，not support downgrade' or something i dont remember，my phone off and stucked at starting log and can restart even holding power button 1 minute，so i thought it fu*ked and bricked，after some time i tried hold power and volume + button finally it switched off and in recovery mode i did factory reset and restart ，Oh sh*t ....... it's Oreo already ！！!
haha i wrote too much！

jskamxmxm said:
Do you still have dual sim support? All bands work as before downgrading with 1004 firmware?
Click to expand...
Click to collapse
thanks for reminding the dual sim，i think better to flash my 1052 firmware again，i'm not sure could there be any issue in future in case two sim in use

i have trouble please help me
My friend who hadn't elect Wipe data/factory when downgrade pie to oreo , so the phone can't open into system . Can't go through the Recovery too!
How can I do?

[email protected] said:
My friend who hadn't elect Wipe data/factory when downgrade pie to oreo , so the phone can't open into system . Can't go through the Recovery too!
How can I do?
Click to expand...
Click to collapse
Force shutdown the phone by keeping volume up, volume down and power pressed for some time (2 - 3 minutes). Then directly boot into recovery by holding down volume up while connecting the phone to the PC via. USB.

Optimus_Toaster said:
This is how I downgraded from Pie to Oreo. I can't guarantee it works for everyone but it worked for me. It required an SD card and a computer.
This is not a guide for the android development savy users but for people who preferred oreo to pie. It works without an unlocked bootloader and a rooted phone. You will have to wipe your data so backup everything beforehand!
1) First download the zip that includes Oreo with the November security patch and put it in the root of the SD card.
I have found links for both TA1012 and TA1004 but reportedly they both work for all Nokia 8 phones as the main payload.bin file is the same. I used the TA1012 zip with my TA1012 phone.
MD5: 07e5b0c46e86919a66d2e6279613047d
MD5: e00affc410525d63200c0c18bc8e0622
2) Boot into recovery mode.
a) To do this on Pie, plug your phone into a computer and wait for the drivers to get installed. Windows 7 downloaded a few megabytes from windows update for this.
b) Unplug your phone and turn it off. Hold Volume up and plug your phone into your computer. Keeping holding volume up.
c) When the sad android appears with 'No command' showing, release Vol+. Hold the power button and press Vol+ to get into the recovery menu.
3) Use the Vol+ and Vol- to navigate down to 'Apply Update From SD card' click the power button to select it. In the next menu select the downloaded zip file. It'll then verify the downloaded zip and install it. This takes a few minutes.
4) Select Wipe data/factory reset from the recovery menu. You need to do this cause data created on Pie doesn't work on Oreo.
5) Finally select Reboot system now and it'll boot into Oreo. This takes a few minutes.
Hopefully this helps someone. Thanks to @THMSP, @TeddyBeers and @al mak for various posts that helped me downgrade and write this guide.
Click to expand...
Click to collapse
hi everyone,
just now want to try downgrade Pie to Oreo, but struggling to entry the recovery mode.
i already 'success' to access "android sad - no command" but after that, when i press-hold vol up and power always going to home screen (android pie)
can you guys please advise what should i do?
should i unlockbootloader? i try with HMD unlock bootloader but error message "device not support"
fyi, i check on developer option, "OEM unlocking" still grey
also on my device manager, only appear "android composite adb interface"
{
"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"
}
thanks as so much for help

worked for me (downgraded from Pie, January 2019), thanks

I successfully rolled back to Oreo.
I wonder if removing the Google account before the rollback prevent you from rollback - install the forced updates - rollback again (I had to do it because I was forced to install the updates the first time, while the second one I had the possibility to skip the configuration)

Root newbie

Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.

Unfortuently there is no clear tutorial to root this phone but you car read here: [GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018

Snypie said:
Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.
Click to expand...
Click to collapse
1. Do i need custom rom?
no
2. Do i need custom kernel?
no
3. Will the android self update as now?
if you flashed TWRP, no

1. Do i need custom rom? No
2. Do i need custom kernel? No
3. Will the android self update as now? depend on your settings
1-to root it the first thing is to have OEM Unlock available and enabled in Dev Options
if not keep the device fully on and with data on dont restart, power off or reset for at least 7 days continuously (or a bit more) and you should have it
if it's not shown dot bother with the rest
2-to have Dev Menu available go to settings >> about phone >> software information >> on build number tape multiple times 10 times i guess, you will have a pop up confirmation
once back at settings menu you will find a new choice at the very bottom "Develper Options"
3-next step with to plug ur phone with PC with usb cable
after installing SAMSUNG DRIVERS & ODIN and downloading TWRP (custom recovery)
in ODIN 2nd tab, untick "AUTO REBOOT" VERY VERY IMPORTANT
chose the TWRP file using AP button/option in ODIN
put your phone in download MOD power off completely >> power back on while holding vol+ and vol- at the same time
flash the file using ODIN to your phone
4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so, after flashing TWRP, press vol- + power button to reboot the phone
AT THE VERY PRECISE MOMENT WHEN PHONE TURN OFF BEFORE POWERING BACK ON WHEN IT BLINK
RELEAS POWER BUTTON AND VOL+ and PRESS POWER BUTTON + VOL+ AGAIN VERY VERY QUICKLY
if successful you should boot into TWRP directly
5-once you are in TWRP wipe everything then format the device (ALL DATA WILL BE LOST)
of course you need to have the needed files already copied in the SD CARD
from twrp after the wipe and formatiing
go to install and flash in that order RMM_Bypass_v3_corsicanu or RMM-State_Bypass_Mesa_v2
then no-verity-opt-encrypt-6.0
then at the end flash Magisk-v19.3
once its done reboot the phone normally, you will have your phone working as normal
once you are in, install Magisk APK MagiskManager-v7.3.2
reboot again
and voilaaa, you should have root and everything shoul be functional for you
allthow of course I will not be responsible for any kind of software or hardware damage, and certainly not ressponsible for any data loss
as it is completely you responsibility
I would like to attach all the files mentioned above, to help better but dnt sems to find how
so you will have to download and gather them from previous posts

Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.

Snypie said:
Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.
Click to expand...
Click to collapse
its virtually impossible to brick samsung devices these days. Well, perma-brick that is. I have spent entire evenings after work bricking phones just so i could figure out what caused the brick and then fix it. the worst thing that would happen if the FRP lock gets enabled again is that youd have to go re-disable it.
i guess i didnt really explain that clearly after re-reading it. So, when he says "stuck" he means with TWRP installed and no method of rooting. The phone will boot normally in the situation described in point #4

Help rescuing a S7 in boot loop and no access to recovery

Hello guys
First of all, thanks to everyone who shares their knowledge and experiences here on XDA. I've been learning stuff here for years, and every time I made a mistake, I could find a solution, but I'm afraid this time the noob here has made too many mistakes.
My S7 G930F DBT stock is in a boot loop, with the "no command" screen, and the only thing I'm able to do is access download*mode. I would like your help to figure out if there's still something I can do on my own.
So, what happened was that I followed this tutorial about a year ago and converted*my S7 to dual sim. I encountered some issues, one of them being that I wasn't able to keep TWRP installed (the system removed it after the first boot), but in the end I was able to make the phone work again, dual sim. This week, I was having some issues with short battery life and wanted to boot into recovery to wipe cache. I tried that and the boot loop started, and when I tried to access recovery it said that there*was no recovery (I can't recall the exact*message). Since then I tried some things*and realized later I made things worse:
- I tried to flash the stock rom via Odin, but did so with the latest firmware (S8), not with the one on the phone (S4).
- Tried to flash all except the BL file on Odin- I tried to flash TWRP, but it failed because of FRP lock.
- I tried to flash a combination rom, but since I had flashed S8, I couldn't*because the latest combination available is U5
- I'm not sure if it's relevant or not, but when following the dual sim conversion tutorial last year and editing the cert file, the serial number was 00000. I kept it that way because I didn't realize it's written on the back of the phone (duh).
Nothing worked, the phone is still in boot loop, I can't access recovery (not even the "no recovery*message" shows up anymore) and I can only put it in download mode. I thought about maybe removing FRP Lock with the z3x 29.5 I used for the dual sim tutorial, flash TWRP and follow all the steps again, to put the serial number in the cert file, but I'm not sure it would be possible, since I flashed a newer firmware.
So, what do you think? Have I messed up beyond repair this time?
Thanks in advance

drlemmy said:
Hello guys
First of all, thanks to everyone who shares their knowledge and experiences here on XDA. I've been learning stuff here for years, and every time I made a mistake, I could find a solution, but I'm afraid this time the noob here has made too many mistakes.
My S7 G930F DBT stock is in a boot loop, with the "no command" screen, and the only thing I'm able to do is access download*mode. I would like your help to figure out if there's still something I can do on my own.
So, what happened was that I followed this tutorial about a year ago and converted*my S7 to dual sim. I encountered some issues, one of them being that I wasn't able to keep TWRP installed (the system removed it after the first boot), but in the end I was able to make the phone work again, dual sim. This week, I was having some issues with short battery life and wanted to boot into recovery to wipe cache. I tried that and the boot loop started, and when I tried to access recovery it said that there*was no recovery (I can't recall the exact*message). Since then I tried some things*and realized later I made things worse:
- I tried to flash the stock rom via Odin, but did so with the latest firmware (S8), not with the one on the phone (S4).
- Tried to flash all except the BL file on Odin- I tried to flash TWRP, but it failed because of FRP lock.
- I tried to flash a combination rom, but since I had flashed S8, I couldn't*because the latest combination available is U5
- I'm not sure if it's relevant or not, but when following the dual sim conversion tutorial last year and editing the cert file, the serial number was 00000. I kept it that way because I didn't realize it's written on the back of the phone (duh).
Nothing worked, the phone is still in boot loop, I can't access recovery (not even the "no recovery*message" shows up anymore) and I can only put it in download mode. I thought about maybe removing FRP Lock with the z3x 29.5 I used for the dual sim tutorial, flash TWRP and follow all the steps again, to put the serial number in the cert file, but I'm not sure it would be possible, since I flashed a newer firmware.
So, what do you think? Have I messed up beyond repair this time?
Thanks in advance
Click to expand...
Click to collapse
Hello, so if you've flashed a newer bootloader than the one in the tutorial then yes it's game over for dual SIM as there isn't a newer version of that bootloader and there isn't going to be. The S7 is getting on abit now.
The best you can now hope for is to install the latest German firmware and have your phone working as a single SIM again.
To exit no command press volume up + power.
When you install TWRP stock recovery is removed. When you uninstall TWRP stock recovery is still missing until you flash stock firmware, that's why you have No command.

cooltt said:
Hello, so if you've flashed a newer bootloader than the one in the tutorial then yes it's game over for dual SIM as there isn't a newer version of that bootloader and there isn't going to be. The S7 is getting on abit now.
The best you can now hope for is to install the latest German firmware and have your phone working as a single SIM again.
To exit no command press volume up + power.
When you install TWRP stock recovery is removed. When you uninstall TWRP stock recovery is still missing until you flash stock firmware, that's why you have No command.
Click to expand...
Click to collapse
Thanks for replying!
I have no problem loosing dual sim, as long as I can get it back up. When I press volume up + power, nothing happens, it only turns off completely. I flashed the the latest firmware again (G930FXXS8ETC6 - CSC file, not HOME_CSC). But the result was the same, "no command" screen and no access to recovery, I tried volume up + power and volume up + home button + power, at the same time and alternating.

I was able to get to were the recovery was supposed to be and this is the error it's showing:
{
"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"
}
I flashed the phone in Odin once again, this time with "nand erase" and "repartition" checked, and the pit file in the third tab. But it didn't work, afterwards the "no command" screen poped up and the same error showed up when trying to access recovery. Tried to flash TWRP again and got the FRP lock message. Nothing changed, basically.
I thought about finding a way to bypass FRP and install TWRP, but there's some shady stuff online on how to do it. The Z3x tool used in the dual sim tutorial has an option for that, but it shows "card error" when I try it and nothing happens.
So, I'm kinda lost here, any suggestion on the next steps would be much appreciated.

I tried to find a way to bypass FRP, tried many tools, like Z3X and Miracle, but it didn't work. The best I could get out of two of these softwares was a "Custom Binary(Userdata) Blocked by FRP Lock" line in download mode when the procedure was finished, not even a reboot. When I manually reboot the phone after getting this message, it shows something different, "An error has occurred while updating" blue screen saying to use SmartSwitch, but that obviously doesn't work either.

drlemmy said:
I tried to find a way to bypass FRP, tried many tools, like Z3X and Miracle, but it didn't work. The best I could get out of two of these softwares was a "Custom Binary(Userdata) Blocked by FRP Lock" line in download mode when the procedure was finished, not even a reboot. When I manually reboot the phone after getting this message, it shows something different, "An error has occurred while updating" blue screen saying to use SmartSwitch, but that obviously doesn't work either.
Click to expand...
Click to collapse
It's unlikely you'll be able to bypass FRP lock with any tool as most don't work anymore.
You just need to flash the latest firmware for your region with Odin. Boot into download mode to do this, can you still access download mode?
After a successful flash the FRP lock will still ask for the Google account and password used with the phone. Follow the steps and your phone should start normally.
It does not matter what modifications you have done prior, the default recovery is always flash latest firmware with Odin.
In future REMOVE Google account from phone BEFORE modification.

cooltt said:
It's unlikely you'll be able to bypass FRP lock with any tool as most don't work anymore.
You just need to flash the latest firmware for your region with Odin. Boot into download mode to do this, can you still access download mode?
After a successful flash the FRP lock will still ask for the Google account and password used with the phone. Follow the steps and your phone should start normally.
It does not matter what modifications you have done prior, the default recovery is always flash latest firmware with Odin.
In future REMOVE Google account from phone BEFORE modification.
Click to expand...
Click to collapse
It wasn't intentional, the phone was working fine and I was logged in my Google account, but the battery life was getting shorter. I just wanted to wipe cache to try and fix that. When I tried to boot to recovery, the boot loop started.
I think that happened because of the dual sim modification last year, I must have done something wrong and the phone lost the recovery mode or something. But the first thing I did was flashing the latest stock firmware, and after that I couldn't get into the system anymore. I probably should have flashed the same binary I had installed, at least it would give me the combination file option.
Download mode is the only thing working. The FRP lock bypass route was the best I could come up with, since it would allow to install TWRP, access to ADB, etc

drlemmy said:
It wasn't intentional, the phone was working fine and I was logged in my Google account, but the battery life was getting shorter. I just wanted to wipe cache to try and fix that. When I tried to boot to recovery, the boot loop started.
I think that happened because of the dual sim modification last year, I must have done something wrong and the phone lost the recovery mode or something. But the first thing I did was flashing the latest stock firmware, and after that I couldn't get into the system anymore. I probably should have flashed the same binary I had installed, at least it would give me the combination file option.
Download mode is the only thing working. The FRP lock bypass route was the best I could come up with, since it would allow to install TWRP, access to ADB, etc
Click to expand...
Click to collapse
I understand all that you've said the only solution is to install correct firmware with Odin via download mode then sign into Google account.