Related
Hi All,
I have a Note Edge 915FY. Tried to upgrade it to stock 5.0.1 via sammobile.com
It is now stuck. It just shows the Samsung Galaxy Note Edge screen and then flashes to "Recovery Booting" and just stays stuck there! For hours!
I have also tried to download 4.4.4 from sammobile.com and flash that but same thing happens. I cannot go into recovery, only into download mode.
I also tried to root it using CF-Autoroot but that failed.
Furthermore, I have tried flashing CWM and TWRP but both do nothing.
I am absolutely stuck! And I really need help!
PS: The phone has no warranty now, so I have no fallback! Please HELP!!!!!
I didn't have any luck flashing CF-AutoRoot when I was on Lollipop, I used CWM and it worked fine.
If your'e stuck go into ODIN mode (Power, Home + Down Vol) and then click up when prompted,
make sure your pc has samsung drivers installed
Download the stock 5.0.1 BOC2 ROM from this XDA page
http://forum.xda-developers.com/note-edge/development/rom-stock-tw-lollipop-t3019721
(You can easily up to BOC6 or a hacked rom later)
Make sure to set Odin as shown in the picture from that same url above
http://dl-1.va.us.xda-developers.com/3/1/4/6/2/6/9/odin.PNG?key=DHp6BTdAsBVpoENIbV4DMw&ts=1431888807
This should work without any issues, I spent some cycles getting bootloops via cf-auto root and some funny ROM behaviour, I was always able to
use this to get me back to stock, root using cwm method then deploy whichever debloated rom you like !
G
iqsoft said:
Hi All,
I have a Note Edge 915FY. Tried to upgrade it to stock 5.0.1 via sammobile.com
It is now stuck. It just shows the Samsung Galaxy Note Edge screen and then flashes to "Recovery Booting" and just stays stuck there! For hours!
I have also tried to download 4.4.4 from sammobile.com and flash that but same thing happens. I cannot go into recovery, only into download mode.
I also tried to root it using CF-Autoroot but that failed.
Furthermore, I have tried flashing CWM and TWRP but both do nothing.
I am absolutely stuck! And I really need help!
PS: The phone has no warranty now, so I have no fallback! Please HELP!!!!!
Click to expand...
Click to collapse
iqsoft said:
Hi All,
I have a Note Edge 915FY. Tried to upgrade it to stock 5.0.1 via sammobile.com
It is now stuck. It just shows the Samsung Galaxy Note Edge screen and then flashes to "Recovery Booting" and just stays stuck there! For hours!
I have also tried to download 4.4.4 from sammobile.com and flash that but same thing happens. I cannot go into recovery, only into download mode.
I also tried to root it using CF-Autoroot but that failed.
Furthermore, I have tried flashing CWM and TWRP but both do nothing.
I am absolutely stuck! And I really need help!
PS: The phone has no warranty now, so I have no fallback! Please HELP!!!!!
Click to expand...
Click to collapse
Did you solve?
Try this (It works for me when my Note Edge was bricked):
On samsung kies 3 select "Tools --> Firmware Upgrade and Initialization" and follow the instructions.
It will ask for phone model (SM-N915FY or other) and for Serial Number S/N, this number is indicated under the battery (make attention to insert the number near S/N not near SSN).
After this It will ask to connect the phone in Download Mode and after it will start to download the firmware (more than 1GB) and will start the installation.
Boot into recovery , power + button + sound UP and clear cache and all reset.
Re do lollipop and you should be fine.
Happened to me but i worked it out after the panic stage....
lucarp78 said:
Did you solve?
Try this (It works for me when my Note Edge was bricked):
On samsung kies 3 select "Tools --> Firmware Upgrade and Initialization" and follow the instructions.
It will ask for phone model (SM-N915FY or other) and for Serial Number S/N, this number is indicated under the battery (make attention to insert the number near S/N not near SSN).
After this It will ask to connect the phone in Download Mode and after it will start to download the firmware (more than 1GB) and will start the installation.
Click to expand...
Click to collapse
I have tried this but weird enough for me, after I input the model number followed by the S/N number in Kies, I got a message "Initialization is not supported for SM-N915FY"
Its kind of fishy since the S/N input only appears after I gave Kies the Model number. If N915FY was not supported, why would they make me open up the back cover and look up for the S/N, make me type it letter by letter and then tell me 'Ok, no luck for you!'.
Any explanation and/or solution for me please? I only have 14 days of extensive researching experience, still left with a 'baseband unknown and null imei" note edge with no prior efs backup .
I think we got the same problems bro, i was very proud note edge user till two days a go, when sudden problems start to happen like restart, slowdown, loop, freeze and shoot of, later no more reboot from system menu that it just shoots of, and then latter hard to start, i had to take out battery and push start + home + volume down buttons about one minute and put back battery just to bring in to download mode and then volume down to start the in to system, and after screen is off it shots down again and again, and last time i put in to freeze to start it to see any missed calls or messages, but sens last night no way i can start any more!
I used to update apps from google and samsung store, and i em curious at this latest update, overnight was lot of data use, even in settings it was setup not to sync any data and not to use any data in background, only Viber app, so i assume there most have been sent to our phones some malware update to brick our old lovely phones, it is very possible.
Now, all i can do is to go to market to find broken screen note edge to purchase and replace motherboard, and i hope i find one not sim-locked.
So try to use Odin v3.07, and download the firmware from here https://www.sammobile.com/samsung/galaxy-note-edge/firmware/#SM-N915FY ans flash it, hope you get back your phone, and if you need to root it, use TWRP v3.02.tar flash with odin to...so the rest of procedure i guess you know!
Today i found on local phone shop+ service one note edge with a bit broken screen, but it did start and stack on kind of "recovery booting", i realized the service or the owner did try to flash sort of room on it but not completed, i bought the phone sm-n915FY model for 30.euro, and now i just transferred the motherboard to my own phone and flashed the TWRP v3.02.tar successfully and let it charge first, bcz there was only 05% battery, and later i will see if i can restore the twrp backup, and i will be careful with this update apps from google and Samsung store the gmail, androidwebsecurity**, maps and browser.
Well, my phone works now, it's just the TWRP backup is not working correct, even i modified folder of the backup, i had pssword in backup and now when i restore seek pasword, i type correct, but the phone did encrypt it. so i have to start with new room setup.
I have one H60-L02, its chinese model and its not rooted or anything like that.
I was in EMUI 3.1 and I try to update to EMUI 4.0, but I make a mistake because I charge one update of 100MB. I did it by local way, with "dload" in SD.
When Honor 6 restarts he didnt charge android anymore and now:
1) if I restart with 3 buttons he stops in the first "honor powered by android"
2) if I restart with power button + vol up he charge recovery but in chinese and I can only restart cache and hard reset but that doesnt works.
3) if I turn off he restarts again, I cant turn off, he always restart.
I try to put some Original FULL ROMs in SD but they dont charge and dont reinstall anything.
Only when I try to charge this rollback "mega:///#F!uopFUBJa!jp6hkjmftAKjQ8LrriwOTA!ukZzVDIY" to EMUI 3.1 something changes. Now when I starts says "4GLTE" screen and then an "android" screen, but the same 3 steps before and anything else.
PLEASE HELP ME
Any help?
Hi potey10,
there is a recoverymode in HiSuite. Idk what it does but I guess (!) it installs the last working firmware and can make your phone work again.
Here is a guide for ascend mate 7
http://www.gizok.com/blog/huawei-asc...very-tutorial/
Pls report if you tried it!
borg17a said:
Hi potey10,
there is a recoverymode in HiSuite. Idk what it does but I guess (!) it installs the last working firmware and can make your phone work again.
Here is a guide for ascend mate 7
Pls report if you tried it!
Click to expand...
Click to collapse
I think the link dont works
I send the phone to Huawei Support in Spain, and they told me they cannot fix it because is a chinese version. WTF?
I hope the link work this time:
http://www.gizok.com/blog/huawei-ascend-mate7-upgrade-recovery-tutorial/
Here it does.
So you have nothing to loose, if you try it.
Install HiSuite on your Computer, start your Smartphone in Fastbood-Mode (Power-Button + Vol. down), select recovery on HiSuite.
The link says "HiSuite will download a suitable version from the official web, the speed of the downloading will be connected to the network speed of the user. As this is a large version, it will take a long time to download, commonly for 1~2 hours, so please wait patiently."
Good luck!
borg17a said:
I hope the link work this time:
http://www.gizok.com/blog/huawei-ascend-mate7-upgrade-recovery-tutorial/
Here it does.
So you have nothing to loose, if you try it.
Install HiSuite on your Computer, start your Smartphone in Fastbood-Mode (Power-Button + Vol. down), select recovery on HiSuite.
The link says "HiSuite will download a suitable version from the official web, the speed of the downloading will be connected to the network speed of the user. As this is a large version, it will take a long time to download, commonly for 1~2 hours, so please wait patiently."
Good luck!
Click to expand...
Click to collapse
I must try. But I dont know waht kind of version of HiSuite is that.
Thats what you means?? "2.2 One-key Recovery Operating Steps"
What version of HiSuite is that?
I think the version isn't important. There is a recovery option in the newest version.
I tried it. Recovery mode isn't supported on my European L04
Hello everyone,
I just installed lineage os on my huawei p20. But i like to return to emui8.1. Where can i download the original firmwares?
Greets
I would suggest "Firmware Finder" by TeamMT.
Google it, there is a PC Version and a mobile one for Android. Make sure to EXACTLY enter your device type ( in my case EML-L29C432) If you dont know your model take a look at the phone box.
You need to download three files. If you still have TWRP you can use HuRupdater. Place the three files in a folder together with the hurupdater.zip, then flash the hurupdater zip. I may seem stuck but it just takes a few minutes so be patient and do NOT REBOOT MANUALLY DURING INSTALLATION (=Brick)
sackgnom said:
I would suggest "Firmware Finder" by TeamMT.
Google it, there is a PC Version and a mobile one for Android. Make sure to EXACTLY enter your device type ( in my case EML-L29C432) If you dont know your model take a look at the phone box.
You need to download three files. If you still have TWRP you can use HuRupdater. Place the three files in a folder together with the hurupdater.zip, then flash the hurupdater zip. I may seem stuck but it just takes a few minutes so be patient and do NOT REBOOT MANUALLY DURING INSTALLATION (=Brick)
Click to expand...
Click to collapse
Will give that a go. Thanks for the help.
If I upgrade to EMUI 9.0 and don’t like it. Can I not just do a simple factory reset on the p20 to revert back to EMUI 8.1. My phone is EM L09.
mixdupkid2002 said:
If I upgrade to EMUI 9.0 and don’t like it. Can I not just do a simple factory reset on the p20 to revert back to EMUI 8.1. My phone is EM L09.
Click to expand...
Click to collapse
[GUIDE] How to rollback from EMUI 9 beta / Back to Android 8
https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-rollback-emui-9-beta-to-t3841687
dauw said:
Will give that a go. Thanks for the help.
Click to expand...
Click to collapse
you're welcome. have you flashed stock rom successfully?
curtricias said:
[GUIDE] How to rollback from EMUI 9 beta / Back to Android 8
https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-rollback-emui-9-beta-to-t3841687
Click to expand...
Click to collapse
Thanks I have read this guide but I don’t want to root my phone. Is there not a way to just factory reset without rooting?
mixdupkid2002 said:
Thanks I have read this guide but I don’t want to root my phone. Is there not a way to just factory reset without rooting?
Click to expand...
Click to collapse
Yes, you can use eRecovery.
No Root or Flashing Stuff needed.
1. Power Off your Phone
2. Press the Powerbutton shortly and wait till you see the Huawei Logo.
3. As soon as you can see the huawei logo press and hold the volume up button. This will take you to erecovery.
You will see a Screen with different options
4. Touch the "Download latest Version and Recovery" Button at the bottom of the screen. Your Phone will activate Wifi.
5. Choose your Wifi Network and enter your Wifi Key.
6. When the phone is successfully connected it will search for the latest official firmware. Follow the instructions
sackgnom said:
Yes, you can use eRecovery.
No Root or Flashing Stuff needed.
1. Power Off your Phone
2. Press the Powerbutton shortly and wait till you see the Huawei Logo.
3. As soon as you can see the huawei logo press and hold the volume up button. This will take you to erecovery.
You will see a Screen with different options
4. Touch the "Download latest Version and Recovery" Button at the bottom of the screen. Your Phone will activate Wifi.
5. Choose your Wifi Network and enter your Wifi Key.
6. When the phone is successfully connected it will search for the latest official firmware. Follow the instructions
Click to expand...
Click to collapse
Thanks sackgnom. I will try this but I am worried that if Huawei makes emui 9 as the official firmware from this point on then doing the above steps will not allow me to reset to 8.1. I will keep it posted.
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)
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
philipp-h said:
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
Click to expand...
Click to collapse
Philip, it helps if you let us know what country your in.
Anyway the solution to your problem is pretty straight forward, you just need to flash the latest firmware for your region with Odin. No need to mess about with TWRP at this point.
Official firmware will contain a copy of the stock kernal which will also be installed when you flash with Odin 99% of the time. If for some reason the kernal is not flashed (it happens) and you continue to get the reboot issue then you will need to flash the kernal seperately first with Odin then the firmware afterwards.
The issue with the FRP lock will remain after this but should allow you to unlock with google email and password.
So we're talking, downlaod mode, flash official fimrware and go from there.
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
philipp-h said:
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
Click to expand...
Click to collapse
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
cooltt said:
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
Click to expand...
Click to collapse
Hi cooltt and thanks for your help!
Unfortunately the BTU-ROM did not solve the freeze-reboot-problem but led to another: After flashing the phone gets stuck with a blue screen "Erasing". After several hours I force rebooted and now it is showing a similar screen with "Error!" and a percentage which is increasing to a random number from 0% to 12% on each boot. On first boot it shows the boot screen ("Galaxy S7"), then "Installing system update" shortly and then "Erasing". After force-reboot it shows boot screen, "Erasing" then "Installing system update", both for a very short time (sometimes misses "Installing...")
As suggested I used SamFirm to download the newest BTU-ROM (SM-G930F_1_20191218140415_dgobhw6g3v_fac; G930FXXS7ESL5/G930FOXA7ESL5/G930FXXS7ESL5/G930FXXS7ESL5). I just ticked F. Reset Time and Reboot. Re-Partitioning did not change anything. Using Odin v3.13.1 does not make a difference. The other ROMs, like SM-G930F_1_20191226131628_8ds2p6kf0v (G930FXXS7ESL9/G930FDBT7ESL9/G930FXXS7ESLA/G930FXXS7ESL9) which I downloaded with Frija (should do the same: download enc4-files from Samsung and decrypt) make the phone going to the initial setup fine, but with the reboot-problem. Tried also with Odin 3B patched.
At this point I was going to write, that I could not access the recovery mode with the BTU-ROM but just now I started it unintentionally when looking for the sequence of screens showed on boot. So I used my chance, made a full wipe and screenshot. After this the phone booted until the glowing "Samsung"-logo appeared. Then rebooted and went to initial setup (after "Androi"Installing applications") in German. The freeze-reboot-issue appears as with all the other ROMs.
The phone is certainly an original SM-930F as it was bought directly from a big, trustworthy dealer and then just used by my aunt. The only one touching it when problems appeared was me. There is SM-G930F printed on the backside and showed in download mode.
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
philipp-h said:
Hi cooltt and thanks for your help!
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
Click to expand...
Click to collapse
Hi Phill
The only options checked in Odin should be F-Reset and Auto reboot. Don't check any others.
The blue screen erasing and updating is normal after a flash with Odin, the phone will restart a couple of times, just leave it do it's thing for a bout 10 minutes or so. If it's any longer than that as you have mentioned then it's stuck as you've said.
So we're going to start from the begining again but do something slightly different.
1. Place the phone into download mode
2. Run Odin but uncheck "Auto Reboot" so the only option checked is F-Reset Time.
3. Use whatever firmware you want, BTU or DBT the latest version. Make sure files are in the correct boxes.
4. Connect phone and flash with Odin, wait until Odin says "succeed 1" and "dissconnected" . It may even say "pass" in green, not important but "succeed 1" is important.
5. Your phone will show the bar and do not disconnect. So....disconnect from laptop / PC. The screen should remain "do not disconnect".
6. Hold volume down+home+power (in that sequence).
7. As soon as the screen goes black move your finger to volume up, while still holding down home + power. You are trying to get the phone into Recovery mode as you said earlier.
8. The option to choose in the recovery menu is "wipe cache partition" NOT "wipe/factory reset". I can see from your pictures that this option has failed because the FRP lock is still on!!
9. When you've chosen "wipe cache partition" then choose "reboot system now"
The phone should go through it's normal set up routine, erasing, update, installing apps etc, just leave it do this and hopefully the phone will boot then ask for the Google email and password which was used on the phone.
There are very few reasons for the phone to get stuck on boot....
1. Incorrect firmware,
2. Water damage
3. The phone has been Rooted with FRP lock on. It is very rare to be a hardware issue.
You should always turn FRP lock off and enable OEM unlock in settings before flashing to a phone. I know it's a little late for that but something to remember.
To check for water damage.
1. Remove SIM card and holder
2. Shine a light in the hole, you will see a WHITE sticker which turns PINK if water has ever got inside the phone.
Thanks a lot again for your great efforts!
I tried as you wrote but did not manage to start recovery immediately after flashing (tried >10 times). But after some while the BTU-ROM started and now keeps doing so even after new flash without wiping cache afterwards. Wiping data worked for me in past when I sometimes had enough time to enter Wi-Fi-password. It was saved even after reboot and away when I did data wipe in recovery. With the newest ROMs I never got beyond typing Wi-Fi credentials.
I cannot see a water damage. A root was never tried before (and OEM-lock and FRP were always on because stock, which is very bad now ). Would be absolutely no problem if this !#@*#% stock ROMs would work... TWRP installation was directly blocked when I tried my luck as last resort. I did not try other images.
Thanks nevertheless for your time and patience!