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
Related
i get the error "Recording Failed" when i pressed the record button.... my sd card and phone memory still have like 10gb empty... and im using Phronesis Rom v3.0. Any solution?
what do logs say
what logs do you mean?
the logs that tell you what the error is
DSA said:
the logs that tell you what the error is
Click to expand...
Click to collapse
im not sure where to find it...i just saw the pop out error when i press the record camera icon..
aronron33 said:
im not sure where to find it...i just saw the pop out error when i press the record camera icon..
Click to expand...
Click to collapse
XDA is a developers forum/site. Not an end-user forum/site.
People are expected to search for the info the need first.
So google your issue, if that not works google howto get the right logs.
If that also doesn't succeed, write down what you have done to avoid the error.
Don't forget to put in all the needed specs, software versions and so on.
And do that in a proper post, preferably with good spelling, grammar and punctuation.
If done all that, help will be more helpful, plentiful and faster.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i cant switch to the video camera mode...
I'm out
@aronron33 Yeah you dug your own grave on this one.
You will get NO HELP, if you dont read others comments and at least try.
So bubye and goodluck finding out the problem yourself!!!
HanZie82 said:
@aronron33 Yeah you dug your own grave on this one.
You will get NO HELP, if you dont read others comments and at least try.
So bubye and goodluck finding out the problem yourself!!!
Click to expand...
Click to collapse
wow you are so helpful........i google -ed and i cant find anything about extract the logs... so i have no idea what the problem is and i cant even switch to the video camera mode so how could i get an error logs?
aronron33 said:
wow you are so helpful........i google -ed and i cant find anything about extract the logs... so i have no idea what the problem is and i cant even switch to the video camera mode so how could i get an error logs?
Click to expand...
Click to collapse
I have the same problem on my N900W8, probably you can fix it installing a 5.0 bootloader.
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian
[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.
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!
Hi. During the update to Android 10 the phone turned off and after switching on it goes into recovery mode.
The phone is not mine and this description was provided to me by the owner of the phone. I was unable to see the phone directly because of the quarantine, so as a first solution I thought about a restore via odin. Has anyone had this problem? And is there a less drastic way than Odin to solve? Because the owner has some data that he would prefer not to lose.
{
"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"
}
How did you get android 10 on j530f?
I get the same messages when I enter recovery but I'm able to get out. You could use odin to reflash the firmware but keep all the data.
You won't be able to do a thing with Odin if the device doesn't have an unlocked bootloader and USB debugging enabled which I doubt it has seeing as it's a stock update that was attempted.
What happens to the device once plugged into a PC? Is the data corrupt or is the device recognized and files can be seen?
I have the same problem with almost the same recovery messsges. It also says dm verity failed. Odin and samsung 300k tool both dont work.
myusernamesucks said:
I have the same problem with almost the same recovery messsges. It also says dm verity failed. Odin and samsung 300k tool both dont work.
Click to expand...
Click to collapse
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...
Emelin.2004 said:
How did you get android 10 on j530f?
I get the same messages when I enter recovery but I'm able to get out. You could use odin to reflash the firmware but keep all the data.
Click to expand...
Click to collapse
I don't know how the phone has Android 10, as I said "The phone is not mine and this description was provided to me by the owner of the phone", sorry.
garylawwd said:
You won't be able to do a thing with Odin if the device doesn't have an unlocked bootloader and USB debugging enabled which I doubt it has seeing as it's a stock update that was attempted.
What happens to the device once plugged into a PC? Is the data corrupt or is the device recognized and files can be seen?
Click to expand...
Click to collapse
Not even to flash a stock firmware? It seems strange to me, in the past I have often used odin on my S2 also for the stock ROM.
The device always reboot in recovery, I don't think the PC can see it.
jaggedN said:
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...
Click to expand...
Click to collapse
Hi, the details were given to me by another person, the only thing that I (and this person knows) is that the phone during an update has turned off and reboots in the attached image window.
Thanks for the tips, I will report it to the person concerned, hoping that he can install the twrp.
TheNightmare97 said:
I don't know how the phone has Android 10, as I said "The phone is not mine and this description was provided to me by the owner of the phone", sorry.
Not even to flash a stock firmware? It seems strange to me, in the past I have often used odin on my S2 also for the stock ROM.
The device always reboot in recovery, I don't think the PC can see it.
Hi, the details were given to me by another person, the only thing that I (and this person knows) is that the phone during an update has turned off and reboots in the attached image window.
Thanks for the tips, I will report it to the person concerned, hoping that he can install the twrp.
Click to expand...
Click to collapse
Put the j5ylte update onto sd card.
Get the update from updato or sammobile or somewhere.
Then reboot stock recovery and apply update from sd card. Or sideload it using adb on a computer. Not very complicated at all
Install the stock rom like i described here: https://forum.xda-developers.com/galaxy-j5/help/to-stock-rom-t4099857
jaggedN said:
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...
Click to expand...
Click to collapse
I cant even access download mode neither can I apply an update from SD card. It says dm-verity failed. System is completely stock. I didn't modify anything.
Hi there. About a year or so ago I went about flashing my Tab but it went wrong and now all I can do is get it to boot to TWRP. Would someone be so kind as to tell me step by step what to do to get it back working? I'd prefer it to go back to stock ROM without TWRP or other 3rd party flash programs but I'll take what I can get. Help appreciated.
This is what I get when it boots:
{
"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"
}
Bump.
fuzzyreets said:
I'd prefer it to go back to stock ROM without TWRP
Click to expand...
Click to collapse
Did you try booting to DL-mode (via adb reboot for example) and flash a stock ROM with ODIN?
DHGE said:
Did you try booting to DL-mode (via adb reboot for example) and flash a stock ROM with ODIN?
Click to expand...
Click to collapse
I got a reply! Thank you!
No I didn't try that. To be honest I used to flash android stuff all the time but kind of having been doing much of that stuff the last few years so I don't remember how to do any of that. If you were so kind to provide me a link or walkthrough on what to do that would be HUGELY appreciated. Thanks for the reply.
fuzzyreets said:
No I didn't try that. To be honest I used to flash android stuff all the time but kind of having been doing much of that stuff the last few years so I don't remember how to do any of that. If you were so kind to provide me a link or walkthrough on what to do that would be HUGELY appreciated. Thanks for the reply.
Click to expand...
Click to collapse
What was the goal when you started down the path of installing TWRP? It seems like you might have been part way there if you got that far?
There are Lineage install instructions here. <-- More importantly Odin Download if you don't already have it.
If you decide to try Lineage, the latest builds require new firmware found here. It can also be obtained by returning to stock and updating.
Anyways If you are in TWRP, in the restart menu there is an option to restart to download. If will reboot to a black screen, just hit the power button once when the screen goes off. Before you do this, you need to obtain stock firmware, from somewhere. (Sammobile or something like that) You will also need Odin, link above.
As with anything proceed at your own risk.
Once you have those files, you can extract the firmware. They will be labeled and go into those spots in Odin, AP, BL, CSC, then you should be able to hit start. I'm going from memory, as I haven't had to restore mine since I got it (and looking at the files in stock firmware file).
Idk how relevant this is anymore but I had this same issue after I install lineage 18, there's a multi-disabler zip I got awhile ago that fixes all my flashing problems related recovery loop. Just Google that zip, flash it then format and restart. That what I've done easy fix, this assumes you followed the basic steps to properly flash whatever it is you're trying to.