Hi Everyone!
I need help a somewhat retro issue here. I have an old Galaxy J5 (J500FN) phone what i want to use as a secondary display on my simulator rig. Back in the days when i switch to a newer phone i used a custom rom on that, called Bootlegers ROM or something like that. I don't really remember it was an android 9 or 10, but that was bad, the phone was slow and often overheated.
I decided to switch back to a stock system, so i used Odin to do that. The process was a success as you see in the picture:
{
"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"
}
But after restart, the phone not boots. The samsung logo shows up, it's keep pulsating, so the device is not frozen but not starting. The only thing happens that approx every 20 seconds the phone shakes a short and this continues endlessly. I can boot to recovery, tried to swipe caches but it's not helping.
Can i do something with that, or the phone is bricked?
Thanks for every advice!
Chris
ChrisWinter said:
(...)
But after restart, the phone not boots. The samsung logo shows up, it's keep pulsating, so the device is not frozen but not starting. The only thing happens that approx every 20 seconds the phone shakes a short and this continues endlessly. I can boot to recovery, tried to swipe caches but it's not helping.
Can i do something with that, or the phone is bricked?
Thanks for every advice!
Chris
Click to expand...
Click to collapse
It could be, for example, a low-capacity battery or one that causes micro short-circuits when power consumption is higher during full system startup.
ze7zez said:
It could be, for example, a low-capacity battery or one that causes micro short-circuits when power consumption is higher during full system startup.
Click to expand...
Click to collapse
I think the battery is in good condition, i turned on the phone once in every month since i switch to another to charge up and apply updates to apps, never noticed any strange behavior.
Use 4-file firmware, it will renew all partitions. 1-file firmware does not do this.
ze7zez said:
Use 4-file firmware, it will renew all partitions. 1-file firmware does not do this.
Click to expand...
Click to collapse
I will try this, but need some help with that. On sammobile.com i find only 1 file firmwares. Where can i get 4 files?
ChrisWinter said:
(...) Where can i get 4 files?
Click to expand...
Click to collapse
Galaxy J5 firmware - Google Search
ze7zez said:
Galaxy J5 firmware - Google Search
Click to expand...
Click to collapse
Downloaded and flashed a 4 file firmware and it was a success, the phone works now like a charm. Thank you very much for the advice!
Related
Hi all,
I did a factory reset for the first time tonight. Everything seemed to work fine. I left it on the home screen, went out for a cigarette, came back five minutes later, and this was the screen I came back to:
{
"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"
}
Hitting Alt+W to do the factory reset again doesn't fix it, as it just reboots to the same screen again.
Is there anything I can do to fix this? Can I apply an update via SD? If so, which one should I use?
I was running RC29, and I would love to keep root access, but my first priority is to have a usable phone. Should I just apply the RC30 update from Google via SD, would that work, and are there any other options?
I will be forever grateful for any information!
alt-L =text mode
home + back button= reboot
cbrunner said:
Hi all,
I did a factory reset for the first time tonight. Everything seemed to work fine. I left it on the home screen, went out for a cigarette, came back five minutes later, and this was the screen I came back to:
Hitting Alt+W to do the factory reset again doesn't fix it, as it just reboots to the same screen again.
Is there anything I can do to fix this? Can I apply an update via SD? If so, which one should I use?
I was running RC29, and I would love to keep root access, but my first priority is to have a usable phone. Should I just apply the RC30 update from Google via SD, would that work, and are there any other options?
I will be forever grateful for any information!
Click to expand...
Click to collapse
satru said:
alt-L =text mode
home + back button= reboot
Click to expand...
Click to collapse
Of course I tried that before posting.
RC30 just patches a few files and isn't a complete ROM update like RC29, so I doubt it would resolve your issue.
I'd suggest you try to "update" to RC29 again from SD Card.
Regards,
Dave
foxmeister said:
RC30 just patches a few files and isn't a complete ROM update like RC29, so I doubt it would resolve your issue.
I'd suggest you try to "update" to RC29 again from SD Card.
Regards,
Dave
Click to expand...
Click to collapse
Dave,
Thank you so much for that invaluable information!
The RC29 update on google's site seems to be gone now:
https://android.clients.google.com/updates/signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip
Does anyone know where I could still find this?
UPDATE: I haven't attempted the update yet, but this looks like a working mirror:
http://rs305.rapidshare.com/files/159243313/signed-kila-ota-115247-prereq.TC4-RC19_RC28.zip
if that mirror no longer works i have the file and will upload for you if needed
That file worked, and my phone now works great!
Thank you all for the information I needed.
*##### EDIT #####*:
Who would have thought that running Windows with VMWare Fusion on Mac OS X could mean that Flashing tasks aren't always a possibility... Tried on a nearby Windows computer and it worked completely fine..! How disappointing, sorry the waste of post, could a Mod please delete this.
Cheers again.
_____________________
Hello all.
I have a Galaxy S4 GT I-9505 which, to date, has shown me that it seems to be impossible to revert it back to stock firmware, of any kind...
I have tried numerous different stock firmwares and every single one has failed. I came from a Rom called 'Foxhound' and was a newly released 4.4.2 at the time, so I'm guessing KNOX has done something to the bootloader which has deemed my device in limbo - to my knowledge.
The thing is, I've come across a leaked 5.0.1 firmware for this device, so I thought I'd download it, only to notice that the Odin flash file wasn't a single TAR file but a series of other files that correspond to the functions of Odin.
From this point on, I decided to try and flash the Bootloader file by itself, and that WORKED. Of course, the only progress I was getting from this was the basic boot logo at the beginning of powering on the device.
Seeing as I was unable to boot into recovery, I thought I'd try and download an Odin flashable CWM Recovery, and this also WORKED.
The thing is, whenever I attempt to flash a full Rom through Odin, it will go through the inevitable error that it does with all attempts.
Here are some images:
{
"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'm beyond frustrated by this as I can't deem the phone usable until I have it up and operational, and it is basically worth nothing in this state.
I would be endlessly grateful if someone would be able to point out what the possible issue may be, I would be beyond thankful!
Best regards,
Try to use Odin 3.09
[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.
My Tab A Sm-T355Y Is Rebooting Randomly While using.It has developed so it is unusable mostly.Please Develop a Custom ROM.Many other users are also facing the use issue.Downgrading does not solve the issue.
Reflashing the firmware up or down rarely solves crashing issues unless the system partition is corrupted.
Wiping the data partition should be you next call
ashyx said:
Reflashing the firmware up or down rarely solves crashing issues unless the system partition is corrupted.
Wiping the data partition should be you next call
Click to expand...
Click to collapse
I tried everything from formatting to downgradomg but nothing helps.
Balaji Sriram said:
I tried everything from formatting to downgradomg but nothing helps.
Click to expand...
Click to collapse
Then I guess it's hardware related.
ashyx said:
Then I guess it's hardware related.
Click to expand...
Click to collapse
Bro many members faced this issue.Developing a Custom ROM Would Fix This.We already have TWRP.It does not reboot in Recovery or in Safe Mode.
Balaji Sriram said:
Bro many members faced this issue.Developing a Custom ROM Would Fix This.We already have TWRP.It does not reboot in Recovery or in Safe Mode.
Click to expand...
Click to collapse
What do you mean it doesn't reboot in recovery?
ashyx said:
What do you mean it doesn't reboot in recovery?
Click to expand...
Click to collapse
If I Keep In recovery It does not reboot.Already you have developed Twrp for Sm-T355Y Model Of Tab A.Can you please release a Custom Rom.Even Nougat or Marshmallow would help.
Balaji Sriram said:
My Tab A Sm-T355Y Is Rebooting Randomly While using.It has developed so it is unusable mostly.Please Develop a Custom ROM.Many other users are also facing the use issue.Downgrading does not solve the issue.
Click to expand...
Click to collapse
This is the common issue of Samsung tablet: loose battery cables and no ROM can fix it.
You can use this glue to make it works better without loosing the connection. However, the glue is conductive, make sure wipe clean with alcohol. Otherwise, you will end with overheating due to trace between terminals. It should not have any residues between the top as well. A lousy job will cause overheating or shorted circuit.
{
"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"
}
You can buy it online from Ebay or Amazon
https://www.ebay.com/itm/Silver-Con...028785&hash=item4d622308f1:g:zFQAAOSwyXNZ5XVn
Or adjust it manually, like this. Squeeze as much as possible
This is not an opinion, I have done many times to fix this problem of rebooting or quick discharge, not only this tablet but others as well.
Unless the mainboard is defective, this solution should fix the reboot issue easily.
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