Database Users

Yoga 2 1050l efi fault after OTA. Only DNX mode left,no recovery/Fastboot. Hardbrick?

[SOLVED] I have rooted my 1050L to fix sharpness. After some weeks I received an OTA and installed. Stupid me. Tried to flash stock rom from temp TWRP, no luck.
Tried some suggestions from here and there, and now i have only DNX mode left. PhoneFlashTool says I'm in wrong mode.
HELP! Am I hardbricked?
{
"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"
}

SOLVED
daverob79 said:
I have rooted my 1050L to fix sharpness. After some weeks I received an OTA and installed. Stupid me. Tried to flash stock rom from temp TWRP, no luck.
Tried some suggestions from here and there, and no i have only DNX mode left. PhoneFlashTool says I'm in wrong mode.
HELP! Am I hardbricked?
Screenshot on imgur.com/gnUBeXS
Click to expand...
Click to collapse
Installed YT2-1050L_USR_S000225_1504220451_WW21_ROW.zip with PhoneFlashTool Lite 5.3.4.1
Then everything worked. Dont know what i did wrong, or if only this version vorked???

daverob79 said:
Installed YT2-1050L_USR_S000225_1504220451_WW21_ROW.zip with PhoneFlashTool Lite 5.3.4.1
Then everything worked. Dont know what i did wrong, or if only this version vorked???
Click to expand...
Click to collapse
Ok, so I was able to flash this rom and boot the tablet. But when i get the OTA the tablet crashes...

The OTA was YT2-1050L_USR_S100192_1511191319_WW52_ROW

Now trying YT2-1050L_USR_S100081_1507241439_WW52_ROW, will update with results

Can it be that the OTA did not have all the right files. Or did the root process do something so that I can only flash stock roms?

I am really not getting any wiser on this intel world. Only been playing with Samsung, Nexus(LG/ASUS) and HTC

Any thoughts? Anyone??

And I can't post images, sorry for that :c

forgot this,
Thanks ionioni
after you flash remember to set your region code before taking any ota's (on the first Android boot go to Contacts and in the search contacts box input ####59930# and if it shows a two letter country code then you're good to go, if it shows 'unknown' then you need to set a country code, input in the same box ####6020# and chose a country, yours or a close one, tablet will reboot)
Click to expand...
Click to collapse

After you flashed the from,did you go to contacts and enter your Country code, without this code it will not take updates.
Sorry missed your last post.

corasman said:
After you flashed the from,did you go to contacts and enter your Country code, without this code it will not take updates.
Sorry missed your last post.
Click to expand...
Click to collapse
I did
Now I have my tablet back!
Seems like there is a big difference between the ROM's (the YT2_1050L_USR* files)
Maybe we should have a tread with all the different ROM's?
I found this on Androidfilehost: Link to downloads for Lenovo Yoga Tablet 2 by ionioni
But how do you see the difference between different roms. Many are big files even if they are not stock roms (with radio, droidboot, bootloader, bios etc)

Now I have 1050L_S100255_160113
Is this the latest ROM?

I think the differences are in the file names...after YT2 it tells you which file is for which model.

S7 Edge (Sprint) stuck in boot loop after attempting to root using Odin

Welp, I'm pretty sure I messed this up. Found a YouTube video (not even sure which one at this point, sorry) that was recently uploaded detailing how to root a Galaxy S7 Edge. Downloaded the firmware, opened up Odin, put it into Download mode, selected the Qualcomm firmware version for the AP field, and click start. It flashed correctly (according to Odin) and the phone began restarting and didn't stop. Just show's the "Galaxy S7 Edge" screen, goes black, and starts over.
I tried downloading the stock firmware for Sprint, load the appropriate files into Odin, and click start, I then get this output:
{
"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"
}
And on the phone, I see:
My build number is NRD90M.G935PVPS5BRA1, kernel version 3.18.31-12623509
I'm fairly certain this is entirely something that could have been avoided had I read more guides or instructions. Unfortunately, here I am! I really appreciate any help anyone can give me. I've been Googling and reading all morning, and I'm sure the answer is there, but I'll be damned if I can see it.

While I don't think there's much important info here, I figure it's at least showing some more in terms of version and name:

Your binary boot is v5. It won't work and you can't downgrade at the moment. What are you trying to do with root? There are many non root alternatives. To fix your bootloops, odin the stock firmware again.
Make sure you have the special version of odin too.
Also, download the stock firmware again. Try updato.com or plug the firmware version into android file host

lvpre said:
plug the firmware version into android file host
Click to expand...
Click to collapse
I don't know why I did not put together the relevance of firmware and the build number, but that was the issue all along it seems! After a dozen different cables, ports, and firmware versions I finally realized I needed to plug in the whole build number to find the firmware for that build specifically. Once flashed, the phone rebooted, asked to restore the backup based on the Google account, and it can text and make calls! Thank you so much for the help, I really appreciate it. I'll be sure to read and research a lot more before the next attempt to root a phone.

reddeth said:
I don't know why I did not put together the relevance of firmware and the build number, but that was the issue all along it seems! After a dozen different cables, ports, and firmware versions I finally realized I needed to plug in the whole build number to find the firmware for that build specifically. Once flashed, the phone rebooted, asked to restore the backup based on the Google account, and it can text and make calls! Thank you so much for the help, I really appreciate it. I'll be sure to read and research a lot more before the next attempt to root a phone.
Click to expand...
Click to collapse
Glad it worked out...we all have been there at some point. Any reason you wanted to root? There may be some non-root alternatives available.

lvpre said:
Glad it worked out...we all have been there at some point. Any reason you wanted to root? There may be some non-root alternatives available.
Click to expand...
Click to collapse
Mainly I was just wanting to get rid of the stock Sprint bloatware that you can't uninstall by default. If you've got any other suggestions for it, they're very much appreciated!

Unable to flash stock rom via Odin from custom ROM (Renovate ICE)

Hello,
I have on my S8 (G950F) Renovate ROM for almost one year, I will switch to new phone soon and I want give my current phone to my sister, so I wanted flash stock firmware and unroot device. Unfortunatelly I am not able do it. I tried manage it on two laptops, I use originanal USB-C cable, I tried few different last firmware from https://www.sammobile.com/firmwares/, and this one as well- https://forum.xda-developers.com/galaxy-s8/development/rom-galaxy-s8-t3749171.
Odin software is 3.13.1 and drivers on my laptops should be okay because I am able flash TWRP. But when I tried flash stock firmware, I am getting some errors:
{
"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"
}
On screen on phone in Downlading mode after failed flash is showing:
sw rev. check fail device: 4. binary: 1
or
sw rev. check fail device 3 binary 2
Everything what I can do is flash custom ROMS from TWRP but I really want go back to Stock ROM so only Odin can do it I guess.
Thank you so much for your tips and help.
Veronika

Just a hint:
a had a similar behaviour on my Samsung tab S2.
The only thing that helped was flashing an really old stock ROM, specifically that one which was on the device at the time i bought it.
Maybe you could try it with an 7.0 Stock ROM.
You can get them from Here: https://updato.com/firmware-archive-select-model?q=SM-G950F&rpp=15&order=date&dir=asc&exact=1

Thank you.
I already tried flash custom Nougat ROM but I got same errors in Odin later.
https://forum.xda-developers.com/galaxy-s8/development/rom-batstock-rom-v1-0-t3598853.
So now I will try download first stock Nougat ROM from my carrier on sammobile site

VeronikaV said:
Thank you.
I already tried flash custom Nougat ROM but I got same errors in Odin later.
https://forum.xda-developers.com/galaxy-s8/development/rom-batstock-rom-v1-0-t3598853.
So now I will try download first stock Nougat ROM from my carrier on sammobile site
Click to expand...
Click to collapse
Your issue is you are trying to flash older firmware (bootloader) version than what is on your phone. You will need the latest version with boot loader version 4
The firmware version should look like this G950FXXU4CRI5.

Thanks!
So this one should help me?
https://forum.xda-developers.com/galaxy-s8/how-to/g950fxxu4cri5-oreo-super-slow-mo-ar-t3844015

VeronikaV said:
Thanks!
So this one should help me?
https://forum.xda-developers.com/galaxy-s8/how-to/g950fxxu4cri5-oreo-super-slow-mo-ar-t3844015
Click to expand...
Click to collapse
As long as it is for your region ( and carrier ). If not sure I would.use a program called samfirm. At the moment I am having issues pasting links so you will have to do a search or use sammobil or updato.

Done, firmware from link was correct and I was able flash it.
Thank you so much for your help.

There is a simple reason for this. If you came from TWRP as "reboot to download", this creates the problem. Turn off the phone. Go to download mode with Vol_Down+Bixby+Power and then press Vol_Up button. When I enter download mode like this, it flashes without any problems.

Galaxy J5 SM-J500FN stuck on boot screen after flashing custom ROMs

Hello to everyone,
I hope that someone can help me at this point where i'm stuck on bootscreen after i flashed an custom ROM.
So, let me tell you my story.
I have a little of experience with flashing custom ROMs. And on my personal phone (Galasy S5) i succesfully installed over and over again custom ROMs. I really like the ROMs from AOSP Extended. They are covering all of my needs. So today i have an Samsung Galaxy J5 SM-J500FN. It is having some problems with the capacitive buttons(Back and multitasking buttons); those are playing however they want, so you can realise that entering in some app and your phone exiting fro it by itself is very annoyng. So on my S5 i have an option that can disable those buttons for good. And i wanted to install the Android &.1 Nougat offered by AOSP Extended today. So i ve got the TWRP from the official website for the right model of the phone (J500FN) and put it succesfully on it. I downloaded the ROM from official AOSP website, and succesfully installed it on the phone whithout any error. Then i installed the GApps nano, again with 0 errors. And when i was relaxing a little bit hoping that everything it s allright, when i wanted to boot up the phone, it froze up at boot screen (At the moment with that logo with Samsung ... powerd by Android). Then in a couple of seconds it started to turn to an green screen and then to an white screen. At this point, everything is frozen. So i removed the battery and entered in recovery mode(TWRP). There was no problem (only with those capactive buttons that i want to block).. But anyway, i donloaded several ROMs and nothing so far. I tried with anoter TWRP version, samething, stuck on boot screen.
Until my first atempt to flash the custom ROM, the phone worked just fine, only that those buttons ware going crazy. But now, i can't start it up in every mode i can think of.
Can anyone help me with this, please?! Any ideea of how to slve it?
TWRP version 3.1.1-1 j5 nlte
Firmware version: AospExtended-v4.5-j5ltexx-20170816-2007-OFFICIAL
Phone version: SM-J500FN
Tried with various TWRP versions and ROMs. Installing with and without GApps. All the results were the same like in the pictures below:
1) Start up like a normal Android phone
{
"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"
}
2) The the big surprise
3) Getting colorfull
4) Advancing...
For now, i can flash with Odin any version of TWRP, i can flash from TWRP any firmware, but i cannot get it boot up normally.
I don't have any backups from stock firmware so, please don t ask me about that.
Thanks in advance...

Look at the aosp file you downloaded. It says j5LTE.
Your device is j5nlte not j5lte you tried to install the wrong file.
Simple as that.
And if that isnt your problem you may have the wrong bootloader and modem but changing that is easy just follow the guide here https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page15

garylawwd said:
Look at the aosp file you downloaded. It says j5LTE.
Your device is j5nlte not j5lte you tried to install the wrong file.
Simple as that.
And if that isnt your problem you may have the wrong bootloader and modem but changing that is easy just follow the guide here https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page15
Click to expand...
Click to collapse
I downloaded all the files i found out there to try see if anything is changing ))
I will try your solution later. Thank you for your reply

All done!
So, guys, my problem wasn-t from the firmware model, because i tryed many.
Thanks to
garylawwd
Click to expand...
Click to collapse
i flashed with Odin ''BootLoader version 5.1.1'' and everything after that was pretty simple.

I have some t350's with issues recovery/MDM/black screen and bootloops

I recently found at the dumps a box of t350's 6/18 didnt like combination flashing the mdm away/new firmware install. 3 failed the same way while putting on newest firmware with odin now they say mdm mode in odin again and i have no debug access. 1 black screens in bootloader and when booting no debug access mdm mode in odin again. BUT ! I have 1 with debug access and see it in ADB BUT it fails to install due to signature verifcation of the ROM's I've tried. I think the later is savable EZ just need a a little help getting TWRP onto it I guess and I'm good. I'll worry about the others later but any ideas ? my brain hurts from trying cables/roms/adb versions lol

Maybe the rom is incorrect have you checked the region and model number etc?

Kenora_I said:
Maybe the rom is incorrect have you checked the region and model number etc?
Click to expand...
Click to collapse
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time

TDIfrogman said:
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
Click to expand...
Click to collapse
no matter what i write to it twrp any firmware just fails like it did when it was mdm locked

Could you provide ODIN logs?

{
"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"
}

it shows mdm locked and the odin log reflects that BUT they where unlocked at some point im, afraid to try and flash the other and they'll end up like this one

TDIfrogman said:
View attachment 5364601
Click to expand...
Click to collapse
They might have NAND flash erros because they arent able to write to it.

Kenora_I said:
They might have NAND flash erros because they arent able to write to it.
Click to expand...
Click to collapse
hmmmm how can i fix it ?

It could be hardware issue, I'm not sure how to fix hardware issues. Thats probably the reason they were all together in a box.

no they where in a box because they came from a school and they didn't take knox off, there was 1000+ of them I just grabbed a tray full they have these crazy polycarbonate cases on them too with security screws. they all worked until i flashed knox away with varying results 12/18 working fine 18 worked prior but in knox

Oh that info is noted.
May I help you later. Its pretty late and I have to get off.
Ill help in the mornin