Hi everyone,
Recently I purchased and Samsung A11. I wanted to root it and unlocked the bootloader first. Than I used Odin to install TRWP recovery. Odin showed "PASS" and I was supposed to press certain buttons which didn't work. Phone kept coming back to "Download Mode" although I pressed those buttons. So I was stuck. The only option was to cancel the download mode, so I pressed volume down + power button for more than 7 seconds. That was the end Now the phone turns on until I see the Samsung logo, there's a small vibration but it can't go forward. It resets back and now stuck in a loop. None of the buttons work including Volume Down+Power combination. Don't know what I am supposed to do now. Can anybody help?
Thanks...
1. Add Samsung A11 to this thread's title thus mainly owners of such a phone get addressed
2. My recommendation: Re-flash STOCK ROM to get rid off of all mods you applied.
jwoegerbauer said:
Re-flash STOCK ROM to get rid off of all mods you applied.
Click to expand...
Click to collapse
Thanks but how can I do that? Phone doesn't turn on, so PC cannot recognise...
gokund said:
Thanks but how can I do that? Phone doesn't turn on, so PC cannot recognise...
Click to expand...
Click to collapse
As I can see you are proud owner of a softbricked phone.
Take it to authorized service center and let them fix it.
jwoegerbauer said:
As I can see you are proud owner of a softbricked phone.
Take it to authorized service center and let them fix it.
Click to expand...
Click to collapse
Yeah, veeeery proud
I plan to let it die on battery and will try to see if I can turn on "Download Mode" after recharging. Do you think it may work?
gokund said:
Yeah, veeeery proud
I plan to let it die on battery and will try to see if I can turn on "Download Mode" after recharging. Do you think it may work?
Click to expand...
Click to collapse
it wouldn't ... usually the cause of bootloop is certain corrupted partition and as long as that partition is corrupted it would keep bootlooping.
if you doesn't know what your doing your best bet is Take it to authorized service center and let them fix it. like what @jwoubeir said
I don't have the A11 model but have used this on other A models that were in the same loop.
Press the volume up and down at the sametime and plug in the usb cable.
This has to be done within a second or two after it vibrates and before it reboots and will likely take a few tries. Good Luck
sammiev said:
I don't have the A11 model but have used this on other A models that were in the same loop.
Press the volume up and down at the sametime and plug in the usb cable.
This has to be done within a second or two after it vibrates and before it reboots and will likely take a few tries. Good Luck
Click to expand...
Click to collapse
great tip work on ADB too anyway OP is provably using sp flashtool since his phone is samsung so this method would be rather tricky
Yayy, I managed to get into the "Download mode" doing exactly how @sammiev told and I tried flashing another TRWP file thinking that might have caused the problem but nothing has changed. Same loop again ! So I flashed the original ROM back using Odin and it's back live again Thanks for the help guys. But to be honest, I am still curious. What might be the problem in not getting TRWP flashing going right?
gokund said:
Yayy, I managed to get into the "Download mode" doing exactly how @sammiev told
Click to expand...
Click to collapse
Used that method of a few peoples Samsung phones. Worked for me every time. It's just to get the timing right.
Sure you have the correct TWRP?
sammiev said:
Used that method of a few peoples Samsung phones. Worked for me every time. It's just to get the timing right.
Sure you have the correct TWRP?
Click to expand...
Click to collapse
I tried again from scratch with a new TRWP file and the result is the same. Odin shows "PASS" but the "Download Mode" screen gives the error as in the photo:
{
"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"
}
My phone model is A115F and I downloaded the TRWP file from this link:
Downloads for : Samsung Galaxy A11 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
The version I used is "twrp-3.5.0_10-3_afaneh92-a11q.tar"
I also tried rooting with Magisk without the need of TRWP installation. That was also unsuccesfull. Odin was PASS but I got bootloader screen saying Secure Check Fail : vbmeta
Here's the screenshot of Magisk fail in "Download Mode"
Can't figure out what's wrong ...
Have you flashed the latest stock rom to this device?
Was there other TWRP files for this model?
Is other people having trouble with this model?
I never worked on A11 Samsung yet
I would hate to give you bad info and have you brick your phone.
Deleted
sammiev said:
Have you flashed the latest stock rom to this device?
Was there other TWRP files for this model?
Is other people having trouble with this model?
I never worked on A11 Samsung yet
I would hate to give you bad info and have you brick your phone.
Click to expand...
Click to collapse
Following your advice, I managed to get into the Download Mode and I flashed the original rom. So phone is up and running now but not rooted. So I've been trying to root again first with Magisk to bypass the need of TRWP installation and with others which need TRWP installation first. There seems to be something blocking the flashing of anything other than the original rom !! On the link I shared above, there are other (older version) TRWP files. Shall I try them?
gokund said:
Following your advice, I managed to get into the Download Mode and I flashed the original rom. So phone is up and running now but not rooted. So I've been trying to root again first with Magisk to bypass the need of TRWP installation and with others which need TRWP installation first. There seems to be something blocking the flashing of anything other than the original rom !! On the link I shared above, there are other (older version) TRWP files. Shall I try them?
Click to expand...
Click to collapse
Usually the latest TWRP with the latest firmware.
Check my profile, your KG stated is ****ed. There is nothing you can do about it, there is abosulutly no way to fix this without unsoldering the eMMC and resetting it entirely. Some people on 4PDA had the same problem and found no fix. I was hopping to develop a custom rom but I cant as my kg state is prenormal. This mexican dude on youtube fixes devices with KG and FRP issues, but yeah this aint something that you can do at home. At least I learned not to buy any samsung devices in the future https://www.youtube.com/c/TeamOcmineMMCBootRepair
edit: nvm your oem is unlocked, you can just flash the vbmeta reset script via odia and everything should flash fine.
Related
Unofficial release -TWRP recovery for the TAB E, both Qualcom and Spreadtrum models
Update: TWRP now version 3.0.2-1
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Put your device in DOWNLOAD mode.
Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Qualcomm models SM-T377P/SM-T377R4 / SM-T560NU:
twrp_2.8.7.0_sm-t377p/sm-377r4
twrp_2.8.7.0_sm-t560nu
twrp_3.0.2-1_sm-t560nu
Spreadtrum models SM-T560 / SM-T561(Y/M):
twrp_2.8.7.0_sm-t560
twrp_2.8.7.0_sm-t561
twrp_3.0.2-1_sm-t560
To Root:
Flash the latest Supersu version below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
STOCK TWRP IMAGE FOR SM-T377P
This is a link to the stock system, boot, modem image for the T377P in case anyone needs it. Needs to be restored with twrp.
Thanks to @shawn1976 for providing this.
https://www.dropbox.com/s/skuwsbzm2zigd83/sm-T377PVPU1AOJ5-boot-system-modem-only.zip?dl=0
Credits: Teamwin and my testers - Phrozen99 and nates730 wizzhard and Siarl
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
NOTE ON ROOTING WITH TWRP:
If you have kingroot installed remove this before rooting with SuperSU above or you will have issues.
Kingroot attempts to block Supersu so must be removed first by using the uninstaller in the Kingroot superuser app.
Absolutely NO feedback
Out of literally hundreds of people that have downloaded and benefitted from the files I've posted NOT ONE person has left ANY feedback whatsoever and only 5 have hit the thanks button and 2 very generous people have offered donations to whom I am very thankful.
As developers we need encouragement and ALL we ask is a quick click on the thanks button and a little feedback.
It's not too much to ask is it for hours of work on a device we don't even own?
XDA is a 2 way community, it's GIVE and TAKE not just TAKE.
Due to this I have decided I am not going to update the builds to the new TWRP v3.0.0-0.
Thank you.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
ashyx said:
Out of literally hundreds of people that have downloaded and benefitted from the files I've posted NOT ONE person has left ANY feedback whatsoever and only 5 have hit the thanks button and 2 very generous people have offered donations to whom I am very thankful.
As developers we need encouragement and ALL we ask is a quick click on the thanks button and a little feedback.
It's not too much to ask is it for hours of work on a device we don't even own?
XDA is a 2 way community, it's GIVE and TAKE not just TAKE.
Due to this I have decided I am not going to update the builds to the new TWRP v3.0.0-0.
Thank you.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Click to expand...
Click to collapse
Come on people. It is not asking to much to thank someone for giving us what we need to make our tablets much better. Over in the T-Mobile S6 thread we have the same issues. These devs do this for us in their spare time for free, so showing a little appreciation is not asking a lot.
Hi, sorry for the late reaction. I succesfully installed your custom recovery but than i had trouble with SD card, it wouldn't get locked in the slot so i couldn't try the backup and restore funtions.
Now SD problem is fixed but when i boot into recovery i get stock, TWRP is gone so first chance i get i'll try to flash it again (don't have a PC available right now).
It would be a shame if you would stop working on our device, you gave us a very important tool for witch i would like to thank you.
You don't need a pc. Extract the recovery.img from the .tar file and then flash with flashify.
ashyx said:
You don't need a pc. Extract the recovery.img from the .tar file and then flash with flashify.
Click to expand...
Click to collapse
I've not rooted yet and i'd like to have a backup before i do, so i guess i'll just wait a bit and flash with Odin.
I want to thank @ashyx for getting Root &TWRP for the Tab E. I bought my SM-T560NU one week ago today. The first thing I did when I got home was to search for Root & Recovery and I found this thread. Everything flashed fine for me. Without devs like @ashyx on XDA we would be stuck with ordinary Tablets & Phones. So make sure to hit the thanks button and post feedback to let them know if things are working or not. It's not that hard to do.
bigtom624 said:
I want to thank @ashyx for getting Root &TWRP for the Tab E. I bought my SM-T560NU one week ago today. The first thing I did when I got home was to search for Root & Recovery and I found this thread. Everything flashed fine for me. Without devs like @ashyx on XDA we would be stuck with ordinary Tablets & Phones. So make sure to hit the thanks button and post feedback to let them know if things are working or not. It's not that hard to do.
Click to expand...
Click to collapse
+1, I haven't tried it yet on my wife's SM-T560NU 'coz my wife always have the tablet with her. She wouldn't even let me get close to it since I screwed up her phone. I will report ASAP when I get a chance to steal the tablet and root it (hopefully successful).
Thanks to @ashyx in advance and to guys reporting back on their experience. Please keep the thread alive.
Thanks for the feedback guys.
Botsok said:
+1, I haven't tried it yet on my wife's SM-T560NU 'coz my wife always have the tablet with her. She wouldn't even let me get close to it since I screwed up her phone. I will report ASAP when I get a chance to steal the tablet and root it (hopefully successful).
Thanks to @ashyx in advance and to guys reporting back on their experience. Please keep the thread alive.
Click to expand...
Click to collapse
If you follow the steps in the OP you should not have any problems. Good luck.
It s work! Thanks man !
{
"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"
}
Smt560nu rom
Was anyone able to find the stock ROM for SM-T560NU on SAMMOBILE?
** EDIT ** I've tried two different computers, reinstalling samsung drivers and different ports. Can't seem to get past the setup connection step in ODIN. Does anyone have any suggestions?
** EDIT 2** Got it working! Thanks ashyx!
Mount Problem
When i tried to install a rom, it says 'Could not mount...blabla'. So I did go to the mount-tab and checked it for the second time and it still fails. Help me please
Hello! I have just finished reading through this thread and wanted to say thank you for all your hard work and dedication ashyx and the testers! I am about to purchase this tablet and wanted to know if model number SM-T560NZKUXAR is compatible with the files you created?
**edit** I just purchased the tablet and it is a SM-T560NU when I get home from work I will test this out and leave feed back
ROM-mer said:
When i tried to install a rom, it says 'Could not mount...blabla'. So I did go to the mount-tab and checked it for the second time and it still fails. Help me please
Click to expand...
Click to collapse
Are you attempting to flash the stock rom with twrp? As far as Im aware there is no custom rom for this device?
I apologize for the stupid question here, but if I am just wanting to do root do i have to flash twrp_2.8.7.0_sm-t560nu.tar first? Or can I just flash the root file
blaineg85 said:
I apologize for the stupid question here, but if I am just wanting to do root do i have to flash twrp_2.8.7.0_sm-t560nu.tar first? Or can I just flash the root file
Click to expand...
Click to collapse
If you're talking about this http://forum.xda-developers.com/showthread.php?t=3300291
Then you don't need to install twrp.
However installing custom recovery and making a backup is one of the best mods you can do to your device.
blaineg85 said:
I apologize for the stupid question here, but if I am just wanting to do root do i have to flash twrp_2.8.7.0_sm-t560nu.tar first? Or can I just flash the root file
Click to expand...
Click to collapse
When I got my Sm-t560nu last week the first thing I did was flash the TWRP 2.8.7.0 tar in ODIN, then I flashed the chainfire su file in ODIN to root it and everything went fine for me. After that I made a backup just like @ashyx suggested.
Ok thank you so much for all your help!! I did the root part successfully which is what I wanted. I don't understand the purpose of doing the twrp
I got an Alcatel OneTouch A462C and I need a root method and a bootloader unlock method. There is no way it could be that hard, its a ****ty tracfone, what security measures could it have?
{
"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"
}
^Heres the phone in question.
[email protected] said:
I got an Alcatel OneTouch A462C and I need a root method and a bootloader unlock method. There is no way it could be that hard, its a ****ty tracfone, what security measures could it have?
^Heres the phone in question.
Click to expand...
Click to collapse
Locked peloader for one, no flashing via SPFT. I heard someone say to get to stock recovery you need to use the button combination same as Samsung phones. Volume up + home button + power. Try this and let me know if it works.
To unlock bootloader, use fastboot to do so. Do some research before unlocking. I made a custom recovery for this device but I couldn't test it.
kirito9 said:
Locked peloader for one, no flashing via SPFT. I heard someone say to get to stock recovery you need to use the button combination same as Samsung phones. Volume up + home button + power. Try this and let me know if it works.
To unlock bootloader, use fastboot to do so. Do some research before unlocking. I made a custom recovery for this device but I couldn't test it.
Click to expand...
Click to collapse
I did the button combo and the phone should be on stock. Now how do I use fastboot to unlock the bootloader? Do you use any IM service?(Skype,ICQ,AIM)
[email protected] said:
I did the button combo and the phone should be on stock. Now how do I use fastboot to unlock the bootloader? Do you use any IM service?(Skype,ICQ,AIM)
Click to expand...
Click to collapse
I use telegram/facebook. You can find me on telegram @kirito9 and on facebook @nickron Davis.
kirito9 said:
Locked peloader for one, no flashing via SPFT. I heard someone say to get to stock recovery you need to use the button combination same as Samsung phones. Volume up + home button + power. Try this and let me know if it works.
To unlock bootloader, use fastboot to do so. Do some research before unlocking. I made a custom recovery for this device but I couldn't test it.
Click to expand...
Click to collapse
kirito9 said:
I use telegram/facebook. You can find me on telegram @kirito9 and on facebook @nickron Davis.
Click to expand...
Click to collapse
I messaged you on telegram. You havent been on since august 31st
Lol!
AdamOutler said:
Lol!
Click to expand...
Click to collapse
Care to share the joke? . Is it TracFone?
kirito9 said:
Locked peloader for one, no flashing via SPFT. I heard someone say to get to stock recovery you need to use the button combination same as Samsung phones. Volume up + home button + power. Try this and let me know if it works.
To unlock bootloader, use fastboot to do so. Do some research before unlocking. I made a custom recovery for this device but I couldn't test it.
Click to expand...
Click to collapse
Care to share said custom recovery? might help get it tested if people could get hands on it.
would also help if you shared what tools would be needed to flash it, and what tools are needed to back up beforehand,
possibly even a small step by step guide like you did for the other alcatel phones?
naemr said:
Care to share said custom recovery? might help get it tested if people could get hands on it.
would also help if you shared what tools would be needed to flash it, and what tools are needed to back up beforehand,
possibly even a small step by step guide like you did for the other alcatel phones?
Click to expand...
Click to collapse
The recovery.img I compiled was a bit lacking, I'll have to fix build and probably make a guide, if I do have time that it.
Yea, I have been trying to root this phone for a while. I have probably tried everything besides Saferoot and nothing has worked.
Hi AdamOutler,
Beginners Clarification: your post 15th October 2016, 05:51 AM |#6 "Lol! Flash with Odin on Windows, Linux and Mac. Use JOdin3," Googled and found your "[Release] JOdin3 CASUAL Cross Platform and Web-Based Flashing For Samsung Phones" http://forum.xda-developers.com/showthread.php?t=2598203
Does this mean you were able to root the Alcatel OneTouch A462C using JOdin3? (Also please do no Flame as had wanted to ask this by PM but was unable)
Thanks
Ken
I know this is a pretty big bump but I to need help with this phone any updates?
This Phone is a Qualcom Technologies, Inc "Proccessor MSM8609" Model TCL A462C Acatel Onetouch runing Android version 4.4.4 and Yes I have tried King root It reports Rooted but only temporarly and I cant even remove system apps with the temp root and yes I have tried third party apps for this process they claim root granted and even claimed they removed said apps but as soon as reboot root is gone and the apps are back please help.
Further more I havent been able to find a reliable way to transfer my root over to super su eaither
By the way I can go into factory recovery but cannot go into fastboot or download mode the only other mod I can go into is Safemode.
Also It Takes A while of running with the temp root but eventually although it takes a while kingroot will also eventually tell me that this phone restricts root authorization and by the time this happens Apps also start reporting that the su binary is not installed with the exception of super su which tells me su binary ocuipied This happens later after those same apps previously told me root granted. And yes I have checked and made sure there is not kingroot imposed restrictions. I dont know why this happens.
It doesn't appear anybody knows what to do with this http://forum.xda-developers.com/general/xda-assist/incoming-calls-answered-vener-make-to-t3500914 and I now have to go back to full factory stuff with no custom recovery and stock os to find out if this is a hardware issue. I did a TWRP restore from several months ago when the phone worked fine and it still has the incoming call issue from the link above. Did a factory wipe in Teamwin, same thing.
Rooted Sprint Galaxy S6 on Lollipop 5.1.1 with Teamwin recovery
http://tiribulus.net/pix/Phone/1.png
http://tiribulus.net/pix/Phone/2.png
Please pretend than I am a not particularly precocious ten year old who needs to make this phone as if I just took it outta the box. I have searched here and around the web. All I find elsewhere are paid download sites or 3 hour downloads and here I can't make heads nor tails out of the volumes of impressive information in these forums.
I do have PC skills, and this is my first smart phone and getting it rooted and the recovery installed and all that wasn't too tough back when I got it 15 months ago. It appears restoring it back to stock is quite a bit tougher.
I have to see if incoming calls still don't work when the machine is totally stock. Is there a way to do this without a 3 hour download and a masters in computer science? I sure would be most grateful for any help with this.
Thank you.
You can simply do "Rescue firmware" via Smart Switch.
forumber2 said:
You can simply do "Rescue firmware" via Smart Switch.
Click to expand...
Click to collapse
Thank you sir! I will have a look at this a bit later tonight when possible.
This won't work with Teamwin recovery right?
I have none of the boot options in this video. Not that I don't appreciate it.
I have none of the boot options in this video (TeamWin). I also have totally different options in SmartSwitch. Not that I don't appreciate it. It doesn't have an option to search like the video says and already has an upgrade in there. I deleted my google accounts like it said and now I have this:
http://tiribulus.net/pix/Phone/smartswitch.jpg
Root will mess up the mobile phone, but the whole point is getting rid of root and fixing the mobile phone. . Again, it's not that I don't appreciate the help, but this is what I've been going through. None of the instructions I find match what I have,.
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
brenner650 said:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
Click to expand...
Click to collapse
I appreciate that sir, but like I say, I never get step 4. It doesn't exist for me. As soon as I click the device initialization tab I get this:
{
"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"
}
If I proceed, I get this:
It tells me the update may fail if it's rooted and being unrooted is one of the goals of this. It also says that the mobile phone function may not work, but it's exactly the mobile phone function that's not working now and I've been trying to fix. That's what started this whole thing:
http://forum.xda-developers.com/spr...er-make-to-t3500914/post69641921#post69641921
Tiribulus said:
I have none of the boot options in this video (TeamWin). I also have totally different options in SmartSwitch. Not that I don't appreciate it. It doesn't have an option to search like the video says and already has an upgrade in there. I deleted my google accounts like it said and now I have this:
http://tiribulus.net/pix/Phone/smartswitch.jpg
Root will mess up the mobile phone, but the whole point is getting rid of root and fixing the mobile phone. . Again, it's not that I don't appreciate the help, but this is what I've been going through. None of the instructions I find match what I have,.
Click to expand...
Click to collapse
You won't do anything on TeamWin.
1. Open Smart Switch on PC.
2. Turn Off the phone. Press Volume down (not up) & Home button & power button. When you see the warning screen, just press volume up once. If you see "Downloading" screen, plug into PC
3. Do "Rescue Firmware" via Smart Switch.
Thats it.
Tiribulus said:
It tells me the update may fail if it's rooted and being unrooted is one of the goals of this. It also says that the mobile phone function may not work, but it's exactly the mobile phone function that's not working now and I've been trying to fix.
Click to expand...
Click to collapse
Well they had to write that, because if something happens during flashing it is not their fault, and you have been warned.
You can also uninstal supersu, and download that same fw Smart Switch would install from another internet source, and it will probably be a painfully slow download, but that is up to you.
I cannot guaratee you that Smart Switch emergency initialization would solve your phone issues, but it is the way to unroot and for the phone to become officially stock, offcourse knox will stay tripped if it was tripped during rooting (and probably is, unless you are on 5.0.2. and were using ping pong root).
I used Smart Switch emergency a lot, and it was always succesfull, just follow instructions, connect your phone in dowload mode when it asks for it, and there should be no problems getting to stock.
...I saw just now, in your other topic that you have fixed it /thumbs up!
I've had an MT6577 phone sitting around for a few years now that's been stuck in a boot loop. My phone karked it today and this is the only device lying around, hoping it can be revived some how to save a few dollars.
It all happened one time when I tried to use an app to install a new font just to see what it looks like.
Seems to be the most obscure thing ever made as it has many names and models all with 0 firmware available. Typically SoSoon X8 Elite 3 shows up as the most common make but I recall the original box having Senq X8 Elite on it.
The bad?:
USB Debugging is almost certainly off because ADB can't find a device no matter if I just plug it in off, in bootloop (shows 2 drives on my PC that are not ready to be used in this stage), fastboot mode, recovery (install update from ADB)
Questionable root, one of those generic one click apps.
No stock or custom roms available any where that I have found from searches here and there over the last few years
I tried to follow a tutorial to port an MT6577 rom but I would need the kernel off the phone, which can't be done to my limited knowledge.
No custom recoveries available, running Android System Recovery 3e. Can't use TWRP MTK 1 click install on my PC because the device needs to be fully booted to work.
The good?:
Fastboot seems to work as it does show the device in the command prompt "fastboot devices"
I think the bootloader was unlocked at some point, no idea on the relevance of that.
Any information on if/how to sort it out is greatly appreciated.
Last ditch effort to try revive it because it was decently usable for what it is, hoping that someone on here has one lying around somewhere.
Will add more information as I remember and reply to any responses asap
Thanks for your time
Hello have you tried a hard reset so far ?
-Hope- said:
Hello have you tried a hard reset so far ?
Click to expand...
Click to collapse
I have, through the recovery "Wipe cache partition" and "Wipe data/factory reset" have been done a few times as I've tried different ways to try and fix it
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
-Hope- said:
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
Click to expand...
Click to collapse
Good news: Tired it
Bad news: Nothing happened
{
"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"
}
Also tried "getvar all" which according to a post on a xiaomi forum, is an MTK specific command, returned nothing anyway.
Just showed the "..." until I pulled the USB cable out.
Thanks for the suggestion, guess that's a pretty significant strike against any kind of fix for it.
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
-Hope- said:
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
Click to expand...
Click to collapse
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the whole system.img unless you have TWRP or can sideload apps in the recovery that you have.
Sent from my SM-S903VL using Tapatalk
-Hope- said:
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
Click to expand...
Click to collapse
Thank you for finding this, much closer than anything I've ever found. From what I can see on it, it's really close spec wise. I'll download it and have a look through the files before trying it.
Droidriven said:
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the while system.img.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did try that. I have all kinds of zips that could supposedly be flashed with the stock roboto font as well as the file itself ofcourse but I could never get fast boot to so anything with it. Based solely off the assumption that all android devices use it as the default, and assuming that the app was just renaming custom fonts to Roboto or something along those lines.
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
FlooferLand said:
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
Click to expand...
Click to collapse
Can you send a screenshot of the bootloader screen?
Kenora_I said:
Can you send a screenshot of the bootloader screen?
Click to expand...
Click to collapse
I'm guessing you mean the Download screen..?
Here's the Download screen if so:
https://imgur.com/pxu0hsS
FlooferLand said:
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
Click to expand...
Click to collapse
You did run fastboot OEM unlock?
or
fastboot flashing unlock
Kenora_I said:
You did run fastboot OEM unlock?
or
fastboot flashing unlock
Click to expand...
Click to collapse
I don't think my phone even has fastboot
I tried booting it into recovery and selecting to apply an update with ADB, I've also tried it at the "Waiting for update" screen.
Fastboot just gets stuck saying < waiting for any device >
The OEM unlock checkbox is already checked in Developer Options.
I don't think the S8+ needs another way to enable OEM unlock other than the checkbox in Developer Options.
EDIT: Here's the output of adb logcat --regex rmm after booting into Android if that's helpful(?) (I have no idea how to use Logcat):
{
"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 did install fastboot drivers? Sometimes if you connect with a usb 3.0 port it dosent work properly
Kenora_I said:
you did install fastboot drivers? Sometimes if you connect with a usb 3.0 port it dosent work properly
Click to expand...
Click to collapse
I've seen a lot of people say the S8+ doesn't have fastboot, there's also no "Reboot to fastboot" option in the recovery menu
Apparently Samsung's RMM server (https://rmm.samsung.com/) appears to be dead (SSL certificate expired and the entire server seems to not work)
So i'm wondering if there's a way to actually spoof the data the server sends, basically blocking Samsung's server and making my own DNS that resolves to my own server sending it's own data.
My problem then is, how would i even know what data my server is supposed to send? And would that even be possible?
I'm very much out of ideas XD
I also found this post (and i have a continuation file for my own phone so in theory it should work?) but it requires the use of iRoot and some proprietary sketchy Windows program. And iRoot and all of these one-click root apps have been known for injecting malware system-level into devices.
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Nice work! tbh I'd never think of that lol,
FlooferLand said:
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Click to expand...
Click to collapse
FlooferLand said:
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Click to expand...
Click to collapse
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
JuanMat97 said:
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
Click to expand...
Click to collapse
The same goes. I have tried everything, and it seems that the post here suggests that we now entirely depend on Samsung to get the site certificate sorted out
Link pasted here for those who don't trust shortened links: https://forum.xda-developers.com/t/...d-expired-certificate-whats-next-lol.4403393/
JuanMat97 said:
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
Click to expand...
Click to collapse
I very much have no clue how it worked for me XD
It's very much possible, you just have to continously try.
I've heard rumors that if you have a Snapdragon chip instead of an Exynos, the RMM is doomed to lock until Samsung resolves their issue. But idk anything about that so i can't really confirm it XD.
I would recommend upgrading to Android 9 and doing the thing i said tho, that worked for me.
Also make sure that your ROM is from the country your SIM card is from, very important.
My phone was originally from Spain, and having a ROM that was made in Spain seemed to caused the RMM to continuously trip out since my SIM wasn't from Spain, so it essentially detected my phone as stolen or smth. You can find official ROMs on something like SamFW.
If this still doesn't work, try waiting 7 days again, then doing the thing i said.
FlooferLand said:
I very much have no clue how it worked for me XD
It's very much possible, you just have to continously try.
I've heard rumors that if you have a Snapdragon chip instead of an Exynos, the RMM is doomed to lock until Samsung resolves their issue. But idk anything about that so i can't really confirm it XD.
I would recommend upgrading to Android 9 and doing the thing i said tho, that worked for me.
Also make sure that your ROM is from the country your SIM card is from, very important.
My phone was originally from Spain, and having a ROM that was made in Spain seemed to caused the RMM to continuously trip out since my SIM wasn't from Spain, so it essentially detected my phone as stolen or smth. You can find official ROMs on something like SamFW.
If this still doesn't work, try waiting 7 days again, then doing the thing i said.
Click to expand...
Click to collapse
friend please, could you say, step by step and in an orderly manner what you did? for example when you said "The time trick actually worked.
All i had to do was turn back the time by like a year" 1-¿have you done that after a flash, a hard reset, or just rebooted without deleting anything?, and also when you said "reboot, enter recovery mode" 2-¿what you did was restart directly to recovery, or restart the system and then restart it again to recovery? and lastly in the part where you said "re-enable OEM unlock, spam the update phone button" 3-¿"re-enable", if you said "re" it means that before reactivating it you already had it activated, right? 4-¿"spam button" by that you mean pressing many times, but, did you have the automatic updates box enabled or not, and... how many times did you touch the update button? thanks in advance, I would appreciate if you answer the 4 questions
which ROM were you using when you did theses steps to unlock? I've tried the 168hs+ method almost now and it didn't worked, then I found your post and tried doing this method changing the date and rebooting cleaning the partition but until now I couldn't achieve it, can you help me pleass
which ROM were you using when you did theses steps to unlock? I've tried the 168hs+ method almost now and it didn't worked, then I found your post and tried doing this method changing the date and rebooting cleaning the partition but until now I couldn't achieve it, can you help me pleass