Related
My Trinity device is not recognized by any of my 3 pc's using any of USB ports. The problem started when I wanted to try a different ROM. I currently have 20070418_RUU_Trinity_LVSW_WWE_1.25.0.8 installed. I wanted to install img-32424-mUn_1_25_AKU3_5 but during the reboot after the ROM transfer the connection failed for the USB connection, after which I gave up and thought well let's try again and soft resetted the device. However I was never able to get a Active Sync session going again. The OS is still booting fine so I feel I am trying to fix something which is not entirely broken. I also tried the suggestion for flashing from SD card, but that did load the TRINIMG.nbh file as I hoped (and read) it would be loading. So I have a IR connection and possibly a bluetooth connection (I left my bluetooth module at work so I cant test this) Will this be my free ticket out of jail? Thanks for your input
You might want to ask this on the upgrading subforum, where all the people who flash their trinity are. This isnt the place for this discussion.
Though personally I'd say no, IR is slow and unreliable, given the length of time it would take to flash a 50mb ROM file, the chances of it breaking halfway through are pretty high, which would brick your device totally.
Try finding a mate's PC that works and doing it from that?
You can't flash using IR or BT because the drivers for those are removed during the flash process.
Post a query in the Upgrading section for info on how to set the device into Bootloader mode, to avoid the need for activesync.
OK will post it in the correct group. Thanks I wont flash it with IR. I already had a suspicion it would not be a happy ending.
Hello
I have a Yotaphone 2 running android 5.0. I have a huge problem with the device which is, that the phone reboots automatically all by itself after the screen turns off. The screen timeout is set at 1 minute and once the screen goes off, the phone reboots! I don't know what the problem is but its making me crazy!
Note: The phone does not reboot if the screen doesn't turn off. So I changed the screen timeout to 30minutes. Also note that Wi-Fi doesn't start immediately. It doesn't even start most of the time and is stuck at "turning on"! And also, the phone isn't detecting my SIM Card!
Hope someone can solve my problem.
Wow, seems a lot of problems here. However you provided very few info about your phone.
1) Where did you buy it?
2) What have you done after you opened it, OTA? Which firmware was installed?
3) Have you tried factory reset by wiping data in the stock recovery? (Accessible with Vol+ and Power)
4) Have you tried to flash from scratch the RU .124 firmware with YotaFlasher?
5) The phone was behaving normally before or it's doing this as soon as you started using it?
I got the phone as a gift
TheArt. said:
Wow, seems a lot of problems here. However you provided very few info about your phone.
1) Where did you buy it?
2) What have you done after you opened it, OTA? Which firmware was installed?
3) Have you tried factory reset by wiping data in the stock recovery? (Accessible with Vol+ and Power)
4) Have you tried to flash from scratch the RU .124 firmware with YotaFlasher?
5) The phone was behaving normally before or it's doing this as soon as you started using it?
Click to expand...
Click to collapse
-The phone was a gift from "Aramex Company".
-Yes, I have factory reset it! Note: It wasn't possible to reset it from settings because it would always get stuck in "Shutting Down" phase and nothing would happen. So I hard reset it.
-I found something strange going on though. Whenever I reset it, It would restart (after the reset is over) and say that "ANDROID IS UPGRADED TO 5.0".
I think it is upgrading by itself to 5.0.
-No, I haven't tried any flashing.
-Yes, the phone was working fine for a while and then started behaving like this!
Cheers!
(Thank You for your support and attention by the way)
Video
Hello!
I have made a video showing what the problems are! Please give me your e-mail so that I can send you the "Dropbox" link to the video.
Thank You!
I think the first thing to do here is to flash a clean firmware (RU or EU) on your phone via YotaFlasher, search here on xda how, and then report back if it's happen again! Seems that the firmware it was shipped with wansn't so stable.
Flashed it!
TheArt. said:
I think the first thing to do here is to flash a clean firmware (RU or EU) on your phone via YotaFlasher, search here on xda how, and then report back if it's happen again! Seems that the firmware it was shipped with wansn't so stable.
Click to expand...
Click to collapse
Hey!
As you had prescribed, I flashed it! First I flashed it with Android 5.0.0-ME1.1.60 and after opening the phone I used it for a while and the phone was same as before flashing! There was no difference at all! The phone was restarting on turning screen off as usual, the WiFi wasn't turning on, and the SIM wasn't being recognized!
But then I flashed it with Android 4.4.3-S01-003-ME1.0.3.61a and the phone is still rebooting by itself upon switching the screen off and the WiFi problem still persists! The WiFi just simply won't turn on. It's stuck at "turning on"! The SIM isn't recognized either! Also, the phone is restarting from the inside now (It wasn't restarting before. I had to keep the power button pressed every time I wanted to restart)! But NOTE that the phone still cannot be just shut down, it can only be restarted!
I don't know what to do!
Cheers
can you please help me find 4.4.3-S01-003-ME1.0.3.61a firmware. i tried yotaflasher and i cant make the program work. it exits close itself. i couldnt find any firmware folder in yotadevices ftp too. can you help me found the spesific firmware please?
Why are you unable to make yotaflasher work
lgk350tr said:
can you please help me find 4.4.3-S01-003-ME1.0.3.61a firmware. i tried yotaflasher and i cant make the program work. it exits close itself. i couldnt find any firmware folder in yotadevices ftp too. can you help me found the spesific firmware please?
Click to expand...
Click to collapse
Hi lgk350tr,
Why are you unable to make yotaflasher work, it is a pretty simple application. Have you tried to see instruction videos on YouTube on how to use it? Instructions are also available on XDA Developers' website. ( https://forum.xda-developers.com/yotaphone-one/general/yota-flasher-download-t3480922 )
Don't hesitate to contact, for any problem!
Cheerio
Please help..................I spent 800 USD on this phone and I can't use it
Can someone freaking help me with my phone's problem, I have spent 800 US Dollars buying that phone, and I can't even use it! It has been 6 months since I opened this thread and no one has helped me yet!
PLEASE HELP..............................................................:crying::crying::crying:
akahomeacc said:
Can someone freaking help me with my phone's problem, I have spent 800 US Dollars buying that phone, and I can't even use it! It has been 6 months since I opened this thread and no one has helped me yet!
PLEASE HELP..............................................................:crying::crying::crying:
Click to expand...
Click to collapse
Try flashing the hybrid modem mentioned in the general guide (Part 2).
Try flashing 2 times before rebooting.
If nothing helps, you could try lineageos, @angelll123 made a lengthy guide how to that in the post quoted here , also check my comment.
Is this what you mean?
tomgaga said:
Try flashing the hybrid modem mentioned in the general guide (Part 2).
Try flashing 2 times before rebooting.
If nothing helps, you could try lineageos, @angelll123 made a lengthy guide how to that in the post quoted here , also check my comment.
Click to expand...
Click to collapse
I have attached a screenshot of the Yotaphone 2 General guide page, I want to know if you are referring to the text that I highlighted in the screenshot!
Thank You
I do experience similar issue, but only recently. I haven't done anything like flashing or upgrading my phone, it started by itself .
I am experiencing reboots whenever battery drops below about two thirds of its capacity. Also, charging and handling some load prevents this.
Note that my Yotaphone has both displays damaged. Still working though.
Successful Recovery Note7 from last Samsung "Death Update" Disabled Battery Charging!
Ok, so here it goes, Im getting one more piece of Note7, addictive, I know... this piece has latest samsung's "Death Update" installed, thus its reportedly only working while plugged in with usb cable or charger but otherwise does not charge battery anywhere beyond 0%... so thats that.
My goal is to root this unit, and install custom rom (like hydra rom) and after probably reflash with ODIN with earlier version that did not have battery charging @ 0% cap , then again root the phone, install root package blocking program and just run stock rooted rom with updates disabled, thus having battery charging feature enabled. Ultimately my options of course are to attempt retrofit another battery to it like one discussed here in this thread:
https://forum.xda-developers.com/note-7/themes/note7-battery-swap-mod-note5-s6-s7e-t3545371
, since the model Im receiving has no warranty and it is already refunded unit to the original owner but was "written off" by samsung or whatever you call it, I dont care as long as I get it, I know me trading it in for S7e even aint an option so its going to be my test-unit for DIY and such.
Im wondering would charging features still be disabled if phone was powered via Download / Recovery modes? Anybody had first hand experience? Otherwise, is there anything else in place after the latest death update that prevents phone from being rooted and alternatively flashed with custom recovery/rom to enable charging?
Mega curious...
Hope ya'll having great weekend people
Mr.Ultimate said:
Ok, so here it goes, Im getting one more piece of Note7, addictive, I know... this piece has latest samsung's "Death Update" installed, thus its reportedly only working while plugged in with usb cable or charger but otherwise does not charge battery anywhere beyond 0%... so thats that.
My goal is to root this unit, and install custom rom (like hydra rom) and after probably reflash with ODIN with earlier version that did not have battery charging @ 0% cap , then again root the phone, install root package blocking program and just run stock rooted rom with updates disabled, thus having battery charging feature enabled. Ultimately my options of course are to attempt retrofit another battery to it like one discussed here in this thread:
https://forum.xda-developers.com/note-7/themes/note7-battery-swap-mod-note5-s6-s7e-t3545371
, since the model Im receiving has no warranty and it is already refunded unit to the original owner but was "written off" by samsung or whatever you call it, I dont care as long as I get it, I know me trading it in for S7e even aint an option so its going to be my test-unit for DIY and such.
Im wondering would charging features still be disabled if phone was powered via Download / Recovery modes? Anybody had first hand experience? Otherwise, is there anything else in place after the latest death update that prevents phone from being rooted and alternatively flashed with custom recovery/rom to enable charging?
Mega curious...
Hope ya'll having great weekend people
Click to expand...
Click to collapse
Not sure why you think that retrofitting a battery would allow the device to charge. The update on your device is what is preventing the charge cycle and also is stopping the device from using any radios.
You need to try to flash via Odin a complete rom, probably the last version that had the battery limited.
If you can manage this then you should be disable oem unlock under developer options and then install hydra by following the detailed instructions.
clearbox said:
Not sure why you think that retrofitting a battery would allow the device to charge. The update on your device is what is preventing the charge cycle and also is stopping the device from using any radios.
You need to try to flash via Odin a complete rom, probably the last version that had the battery limited.
If you can manage this then you should be disable oem unlock under developer options and then install hydra by following the detailed instructions.
Click to expand...
Click to collapse
Battery retrofitting mod is not to get battery charging - is to keep note7 fail-proof, and with this specific unit that Im talking about it is especially the case only after getting it back to firmware that did not have it bricked.
I know about "OEM unlock" feature in dev mode is a must before any software tampering, so thats not an issue. I am aware phone works while on cable, so I should be able to navigate and activate OEM Unlock from dev menu, also I should be able to do straight ODIN flash with firmware that is of an earlier version without any battery cap's , so my question still remains - is there anything in this latest deadly update from samsung that prevents ODIN from flashing anything to the phone, or is it just charging orientated?
we shall all see once it comes across, should be following week, Im actually eager to start working with it. May as well just go ahead and order myself a S7 battery too so less time to waste waiting
I have a Note 7 that's on the "Death update".
1) Phone cannot be charge in normal mode or download mode.
2) I did not check on whether it could still function with a cable plug in.
3) Attempting to flash older Samsung firmware from ODIN will not work. It will give some errors and stop there.
4) Could not flash anything through ODIN. BL, CSC, CP, AP could not be flash into the phone.
5) Could not flash recovery from ODIN either.
6) Enabling OEM unlock doesn't help in anything. See point 3 and 4 above.
Hope the above helps.
teslapolaris said:
I have a Note 7 that's on the "Death update".
1) Phone cannot be charge in normal mode or download mode.
2) I did not check on whether it could still function with a cable plug in.
3) Attempting to flash older Samsung firmware from ODIN will not work. It will give some errors and stop there.
4) Could not flash anything through ODIN. BL, CSC, CP, AP could not be flash into the phone.
5) Could not flash recovery from ODIN either.
6) Enabling OEM unlock doesn't help in anything. See point 3 and 4 above.
Hope the above helps.
Click to expand...
Click to collapse
Vey well, I have some extra ideas too, we shall see
Besides, what are your current plans for your note7?
are you willing to sell it by any chance?
Mr.Ultimate said:
Besides, what are your current plans for your note7?
are you willing to sell it by any chance?
Click to expand...
Click to collapse
I'm hoping to revive the Note 7 and use it if this is possible at all.
Won't mind selling if there are no other option.
Ok, so got my disabled charging note7, it has about 24% battery remaining and it stays this way if I keep it plugged in on USB or on wireless charger.
I tried flashing TWRP both versions available, both had flashed OK with ODIN however, it still has standard recovery...? wtf...
I remember my S7edge did have very similar behavior, odin would flash TWRP just perfectly fine but when going in to recovery on the phone it still starts in standard recovery, and this would continue until I flashed CF-Autoroot IMG.TAR file , but this time I cannot find it anywhere for note7....
Im thinking trying KingoRoot or OneClickRoot tools but I wanna hold back a little before I launch on those.
Ok good news (so far) , flashed custom kernel via ODIN, worked, but now I figured phone takes charge again while phone is off just on USB, so charge disable mode is within latest kernel update only.
I can still enter my standard recovery and do all I want there (havent tried factory reset yet!)
When powered off from recovery, phone began charging! now I have noticed it went from 23% to 24% and it is showing it is charging, where as before it would vibrate for second when plugged in and then show battery symbol which soon after would go offline and phone would be unresponsive like it is not plugged in - in not charging state. So for now 1:0 me vs note7
EDIT!
YESSS! IT IS CHARGING! NOW @ 26%!!!
Now @ 30% ... ok I should let it charge to 50% and then try perform more firmware DIY
ok, I will confess, I could not wait any longer, thought screw this sh*t, went in to recovery and wiped cache/factory reset, rebooted phone, then witness phone startup OK, welcome wizard started OK with 30% on battery and indicator on shows On-charge thought "yess!!!" , then I get this notification about battery is gonna run out and no longer recharge blah blah blah, but hey , it still charges and now Im at 33%
Yes, latest firmware and custom kernel and VIOLA , note7 is back in the game!
Also got this notification from device security thing asking me to reboot phone to try undo the changes... I guess I will not try just yet out of curiosity will try again to do TWRP reflash, this time it should work
Confirmed, now TWRP flash via ODIN worked liek a charm, so I should root via TWRP now and see if I can disable something in current latest software to disable these notifications playing around now
ok now rooted and lots knox stuff disabled with package disabler and etc, still getting this one notification about discharging battery warning when plugged in, anyone could advice me which file to edit in system root to bypass this?
Thanks
Wow, that's great. I've been trying for weeks but unable to get through to anything. Will it be possible to share on how you get to flash TWRP successfully? Thanks
---------- Post added at 12:36 AM ---------- Previous post was at 12:32 AM ----------
Mr.Ultimate said:
ok now rooted and lots knox stuff disabled with package disabler and etc, still getting this one notification about discharging battery warning when plugged in, anyone could advice me which file to edit in system root to bypass this?
Thanks
Click to expand...
Click to collapse
I'm don't know about the editing stuff but if you could get TWRP to work, wouldn't it be simpler to flash custom ROM that already have KNOX etc disabled?
I was disabling all kind of random packages just to see what results will I get from doing it all , was expecting to somehow find package that relates to USB/wireless pad power circuit monitoring so I could work on it while maintaining the latest patched firmware but no nagging popups every time phone is powered on or plugged in to USB/wireles pad. Otherwise I observe phone is 99.99% perfect aside from the notification that I have described and security centre prompts warning time to time that device has been modified , click restart to undo-modification, which I actually tried and it undone-nothing, so it is permanently patched this way regardless what you try to do within the phone now.
I am in favor of keeping stock rom and stock appearance of note7 as much as possible.... dont know if it makes much sense but I love the way note7 is... with all functions working as much as possible as close to standard as much as possible, so thats why my reasoning trying to make this latest rom work.
I have few firmwares which were the original ones V.1 and V.2 but not V.3, which is what I have, so even if I install custom rom now, there is no way going back to factory firmware since V.3 full factory rom is nowhere to be found.
I am going to look in to ways on how to extract entire current firmware so I can go and learn a bit and maybe do few ROM builds myself, this is actually exciting now once I got this far.
Able to link me to the custom Kernel that you use?
teslapolaris said:
Able to link me to the custom Kernel that you use?
Click to expand...
Click to collapse
do it on your own risk folks, I mean - enjoy...
https://www.androidfilehost.com/?w=files&flid=98347
Mr.Ultimate said:
do it on your own risk folks, I mean - enjoy...
https://www.androidfilehost.com/?w=files&flid=98347
Click to expand...
Click to collapse
Thanks. It works!!!. Thank you so much.
I managed to flash TWRP and Hydra ROM onto it. Everything works except mobile network. Somehow it is unable to detect the SIM card.
Will fiddle with it further. Hopefully I could get it up and running.
Thanks again.
only downside I see so far with current latest kill firmware and this patched kernel are those nagging notifications regardless battery charging to 100% ok, security center notification about modifications and about restart with attempt undoing them, which obviously will fail anyway anytime, and just now noticed it takes a little more time to activate wifi to show available networks, usually its instant, like 0.1second, and now its like 3-5 second delay once switch is toggled to ON position. Also, found out that when network sim card inserted, now phone prompts for network customization and asks to restart now or later to apply settings changes, and I tried restarting but this keeps coming on anyway, so finding the service package and disabling it solves this issue.
Besides no any network issues here, signal comes on every time I change sim cards around and all connectivity is there with data and all is OK, maybe try different kernel? I tried one with APO ,mine is European exynos SM-N930F model
I tried out Hydra kernel but it didn't work. Then I found this https://forum.xda-developers.com/note-7/how-to/spacex7-rom-kernel-kill-galaxy-note7-t3536693. I flash it and my SIM card works again.
This may help someone
Hi.
As I've read that there are people in the forum with problems after the last update from samsung, I decided to write my experience.
My first Note 7 was the Hong Kong version. It was amazing, because it had an fm radio built in, but of corse I couldn't flsh a costum rom on it, as there as none in the forum. In time, a gave up and send it to samsung, and I am glad for, since by now, I would have a death phone.
Anyway, after 2 months with a s7 edge, I found a person selling is international note 7, cause he would go to Brasil, and was afraid to had it apprehended at the aeroport. So I bought it, even with the limited charge at 60% problem.
First, I tried the Dr. Keatan rom, but the limited battery charge still persisted.
So I tried the TEKXodus rom, and I say its amazing.
My phone now as the batery charging to 100%, and even the shealth works fine, if you don't update it.
If it as an automatic update by google, just downgrad it and is fine.
When I received the samsung notification for the last update, I just needed to be sure that the update function was turn off, that the processes in the background were off too, and, with titanium backup, to freeze 2 "urgent update" apks.
Everything works fine.
So, for those who have problems, I recommend the TEKXodus rom.
Best regards
Hello,
Few months ago, when the battery was low (just below 20%) my P9 lite started acting crazy: opening/closing apps, pressing buttons, taking pictures, ... Everything so fast that the battery drained in few seconds. After searching the internet I tried changing the battery with an original one. It didn't change anything.
Recently the situation worsened: it seems that the phone fails to detect the real power of the battery. So even if the battery is 50-60%, it can happen that it starts acting crazy or, more recently, restarting all of a sudden. Then it still works, but after a bit it restarts again and the battery now is drained.
Both before changing the battery and now the problem can be easily solved by charging the phone. Connecting the cable stops immediately the phone both acting crazy and restarting.
Anyway, as you can guess, this is quite a problem if you are outside, even with a powerbank. But these restarst are becoming very frustrating even at home.
Beside this, the phone does work well so I think it's a pity to throw it off...
I've tried a hard reset just few days ago but it didn't change anything.
Is it possible to do anything to solve the problem?
Thank you
papersing said:
Hello,
Few months ago, when the battery was low (just below 20%) my P9 lite started acting crazy: opening/closing apps, pressing buttons, taking pictures, ... Everything so fast that the battery drained in few seconds. After searching the internet I tried changing the battery with an original one. It didn't change anything.
Recently the situation worsened: it seems that the phone fails to detect the real power of the battery. So even if the battery is 50-60%, it can happen that it starts acting crazy or, more recently, restarting all of a sudden. Then it still works, but after a bit it restarts again and the battery now is drained.
Both before changing the battery and now the problem can be easily solved by charging the phone. Connecting the cable stops immediately the phone both acting crazy and restarting.
Anyway, as you can guess, this is quite a problem if you are outside, even with a powerbank. But these restarst are becoming very frustrating even at home.
Beside this, the phone does work well so I think it's a pity to throw it off...
I've tried a hard reset just few days ago but it didn't change anything.
Is it possible to do anything to solve the problem?
Thank you
Click to expand...
Click to collapse
Hello,
sometimes weird things happens....
maybe it wont solve but
you can try this :
clear all recent apps,
reboot into e-recovery (keeping vol- & power)
then clear the cache and reboot system..
Test how it work...
Cheers
Dadditz said:
Hello,
sometimes weird things happens....
maybe it wont solve but
you can try this :
clear all recent apps,
reboot into e-recovery (keeping vol- & power)
then clear the cache and reboot system..
Test how it work...
Cheers
Click to expand...
Click to collapse
Thank you for your suggestion! I tried but unfortunately it didn't work, nothing changed...
papersing said:
Thank you for your suggestion! I tried but unfortunately it didn't work, nothing changed...
Click to expand...
Click to collapse
Yes, the behaviour is more similar to a malware.
It could be an app you recently installed....
A good change is to re-install your same firmware
or possibly to update it to the latest...
You can use Firmware Finder app to do this,
but beware what you do, a wrong firmware
may brick your device.
It's your choice doing this...
Good luck dude.
Cheers
Dadditz said:
Yes, the behaviour is more similar to a malware.
It could be an app you recently installed....
A good change is to re-install your same firmware
or possibly to update it to the latest...
You can use Firmware Finder app to do this,
but beware what you do, a wrong firmware
may brick your device.
It's your choice doing this...
Good luck dude.
Cheers
Click to expand...
Click to collapse
Hello! Excuse me I'm not sure I've understood correclty. I've searched for the Firmware Finder in Play Store, but looking at the comments it seems not working in my country. I've tried to search for the original firmwares in google but it appears I can find only modded versions which requires flashing and other stuff I don't know how to do. I couldn't find a guide for real beginners, is there?
Anyway I've recently done the hard reset on my phone so it shouldn't be an app, is it? Is it possible the firmware is damaged even if I never unlocked or done anything special on my phone?
Thank you!
papersing said:
Hello! Excuse me I'm not sure I've understood correclty. I've searched for the Firmware Finder in Play Store, but looking at the comments it seems not working in my country. I've tried to search for the original firmwares in google but it appears I can find only modded versions which requires flashing and other stuff I don't know how to do. I couldn't find a guide for real beginners, is there?
Anyway I've recently done the hard reset on my phone so it shouldn't be an app, is it? Is it possible the firmware is damaged even if I never unlocked or done anything special on my phone?
Thank you!
Click to expand...
Click to collapse
Ok dude, you don't have to worry.
There are many guides on the web in various forum,
especially here on XDA. What is your current firmware ?
I mean the whole firmware ex. VNS-L21C432B504 / VNS-L23C605B393;
You can try doing this in two ways:
1 - using FF and pointing to your current firmware or updating it to latest if possible;
2 - using HuRUpdater.
This method let you flash whatever version of firmwares,
but you need to unlock the bootloader and use a custom recovery (TWRP)(it cost 4€).
Using FF will not cost money, you should try it first.
Cheers
Dadditz said:
Ok dude, you don't have to worry.
There are many guides on the web in various forum,
especially here on XDA. What is your current firmware ?
I mean the whole firmware ex. VNS-L21C432B504 / VNS-L23C605B393;
You can try doing this in two ways:
1 - using FF and pointing to your current firmware or updating it to latest if possible;
2 - using HuRUpdater.
This method let you flash whatever version of firmwares,
but you need to unlock the bootloader and use a custom recovery (TWRP)(it cost 4€).
Using FF will not cost money, you should try it first.
Cheers
Click to expand...
Click to collapse
Hello! Thank you for your help.
I tried to follow your instructions but something went wrong.
My firmware is VNS-L31C432B417, so in FF I've searched VNS-L31C432:
I then pushed the button with the "play" symbol and FF searched for all the six tasks, but it couldn't find any firmware
Did I do something wrong?
Strange fact: searching in the internet for VNS-L31C432B417 I found that, since already 3 months, it is available in my country a new firmware VNS-L31C432B418, but, if I search for updates in the settings section of the phone, this update doesn't show up, saying that my phone is already up to date. Is it normal?
papersing said:
Hello! Thank you for your help.
I tried to follow your instructions but something went wrong.
My firmware is VNS-L31C432B417, so in FF I've searched VNS-L31C432:
I then pushed the button with the "play" symbol and FF searched for all the six tasks, but it couldn't find any firmware
Did I do something wrong?
Strange fact: searching in the internet for VNS-L31C432B417 I found that, since already 3 months, it is available in my country a new firmware VNS-L31C432B418, but, if I search for updates in the settings section of the phone, this update doesn't show up, saying that my phone is already up to date. Is it normal?
Click to expand...
Click to collapse
Dude you have the same device i owned.
Don't worry about FF, you simply searched the wrong place...
Tap "Common Base" TAB, write VNS-L31C432 and press on the lens to search ...
You'll see all the firmwares for your variant...
Beware dude, you have B417, it's the latest (for single sim)
and cannot update to B418 (it's for dual sim).
You have to point to your current same firmware.
First thing, delete all the safties (fingerprints/pin/pattern)
and do a backup of all your stuff, just to stay safe...
Make sure you have access to the network and use "Firmware Finder app",
choose B417 FULLOTA-MF, follow the inbuild guide (register the IMEI,
use dns/vpn method). Then go into settings/updates and tap "search for updates"
you should find your update. Tap to download it and when it reaches 5%,
tap pause and disconnect the vpn.
Reactivate the download and complete the reinstallation of the firmware.
Quite similar to THIS GUIDE, just change the firmware with yours...
Edit: I replaced the image because it could not be viewed.
Edit2: re-replaced again the image, still it couldn't be viewed...
Dadditz said:
Dude you have the same device i owned.
Don't worry about FF, you simply searched the wrong place...
Tap "Common Base" TAB, write VNS-L31C432 and press on the lens to search ...
You'll see all the firmwares for your variant...
Beware dude, you have B417, it's the latest (for single sim)
and cannot update to B418 (it's for dual sim).
You have to point to your current same firmware.
First thing, delete all the safties (fingerprints/pin/pattern)
and do a backup of all your stuff, just to stay safe...
Make sure you have access to the network and use "Firmware Finder app",
choose B417 FULLOTA-MF, follow the inbuild guide (register the IMEI,
use dns/vpn method). Then go into settings/updates and tap "search for updates"
you should find your update. Tap to download it and when it reaches 5%,
tap pause and disconnect the vpn.
Reactivate the download and complete the reinstallation of the firmware.
Quite similar to THIS GUIDE, just change the firmware with yours...
Edit: I replaced the image because it could not be viewed.
Edit2: re-replaced again the image, still it couldn't be viewed...
Click to expand...
Click to collapse
Hello!
Sorry I took some time to reply, recently I had to move a lot so I didn't want to take the risk to mess things with the smartphone. Anyway, yesterday I did the reinstallation of the firmware, choosing the VNS-L31C432B417 FullOTA-MF dated 2020.01.13 (I didn't get the difference with the other one dated 2020.01.08, so I choose the most recent).
I followed your guide (thanks!), the only thing I changed is the method: the dns method didn't work so I used the e-recovery mode and it seems that all went well... Except nothing changed. Now, even when the battery is full charged, if I listen to a podcast via speakerphone after a while the phone restarts suddenly.
Is it possible there is something wrong in the hardware?
It's so frustrating because aside from that it works flawless.
Thank you for your help!
papersing said:
Hello!
Sorry I took some time to reply, recently I had to move a lot so I didn't want to take the risk to mess things with the smartphone. Anyway, yesterday I did the reinstallation of the firmware, choosing the VNS-L31C432B417 FullOTA-MF dated 2020.01.13 (I didn't get the difference with the other one dated 2020.01.08, so I choose the most recent).
I followed your guide (thanks!), the only thing I changed is the method: the dns method didn't work so I used the e-recovery mode and it seems that all went well... Except nothing changed. Now, even when the battery is full charged, if I listen to a podcast via speakerphone after a while the phone restarts suddenly.
Is it possible there is something wrong in the hardware?
It's so frustrating because aside from that it works flawless.
Thank you for your help!
Click to expand...
Click to collapse
Ah yes, the e-recovery mode ... :cyclops:
I had assumed you had already tried it, hence the suggestion for using FF ...
So if after re-installing the software nothing has substantially changed,
then it would be something related to the hardware, honestly I can't tell you.
You could try to bring it to this service point or to a trusted person,
maybe a friend who deals with mobile devices.
Or maybe the time has simply come to replace it with another,
anyway I wish you good luck ...
Cheers
Hi all
As the title says. I've run into problems trying to flash a new ROM.
I used TWRP to flash a custom ROM but didn't like it so wanted to go back to stock. I'm not sure/can't remember what happened (been up till 4am for 2 nights trying to fix it), but it's now stuck. I can get into DL mode (pale blue/turqoise screen) and have tried flashing various stock ROMS but am running into problems that may be driver related.
I don't/have nevwer has Kise installed. I have tried various Samsung USB drivers. Some seem to have been invisible, but the one I'm using now (can't remember version but it's a few vesions old) is visible in Windows 7 device manager as Samsung modem which says it's working (for what that's worth). When I plugged the device in, the taskbar popped up to say the driver was installing.
I've tried a few versions of Odin. They all say <added> in the dialogue box, and 0:[com4] is added to the little box above and changes colour. I'm assuming that means that Odin can see the device ok?
After browsing for the stock ROM BL, AP, and CSC files, they get checked for MD5 which all seems ok, and then when I start Odin, nothing much happens, a few lines of text - file analysis, setup connection, and if I'm lucky it gets to NAND write start... and then nothing. I left it in that state last night and 10 hours later nothing had happened.
I'm hoping that this is something simple but I've exhausted my knowledge and need some help.
Most important question: Is this device recoverable? If not, there's no point in banging my head against the wall.
Secondly, am I on the right track or do I need to be doing something else? (if so, please point me in the right direction)
Is this as simple as the drivers not working right and should I continue to try different driver versions along with different USB sockets and cables? (tried a few cables including what I think is the unused OEM one). Is there a way to check that the driver is actually working or is its presence in device manager the only indication?
I've tried several Odin versions also.
Nothing I've tried has got past the NAND write, and I only managed to get that far last night.
How long approx should it take to flash and is there any progress indication on either Odin or device? (There's no point in waiting an hour if I should see something happening within 2 minutes, I may as well cancel and try something else)
I'm sorry for having to ask because I know to some of you, this may seem a simple problem and you may roll your eyes, but I really have tried everything I know and need to know if there is a chance what I've been doing will suddenly work or if I need to do something else or give up entirely. I never ask for help on a forum without trying my best to research and solve the problem.
TIA
Edit
I tried again, and left it showing at NAND writing, and after annhour or two, it completed, but failed. I don't know if this is a time out thing or whether it tried and failed. Without knowing if I'm on the right track there' s no point in repeating the same actions that are going to fail.
Must admit, expected some kind of response by now.
You may not have all the answers but if you may have part of one answer. I don't have anything to lose because the device will be going into landfill unless something happens.
cecr said:
Must admit, expected some kind of response by now.
You may not have all the answers but if you may have part of one answer. I don't have anything to lose because the device will be going into landfill unless something happens.
Click to expand...
Click to collapse
Boot into recovery and factory reset. Then, with the latest stock ROM available, flash only the AP and BL modules. If Odin shows "added" when you plug in the cable, then the driver is working. Have you tried a different USB cable?
Did you try using the latest patched Odin? If it says added then the driver is working so it can't be a driver problem. It usually doesnt take more than 10 minutes to flash stock rom so don't wait an hour. As @lewmur said try flashing just the BL and AP files and try different USB cables and sockets also avoid using a USB hub.