Database Info

(Q) Odin 3 flashing kernel issue

What would start causing this to happen?
{
"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 am very familiar with the process. Rooted, sideloading for apps is all done. I have flashed my device with JM2, JH2, and the 1.2 OC. Now when I try to flash it doesn't work. I tried last night with no luck. I decided to master clear the device since I was having issues and wanted to start back with a fresh device. Now after trying to flash the JH3 from JF6 with Unleash the beast it wont work.
I also tried flashing with one click root, and superrooter from a fresh Odin one click. Usb debugging is enabled, Odin opened and then get into download mode. So my process from when it would work is now not working haha? So beyond my confusion of what I might be forgetting can anyone think of something that might help? I didn't want to put this in the dev section since there is nothing specifically made up for odin 3, only odin one click restore.

Your drivers are messed up... grab the ones from the odin thread and reinstall with the phone plugged in and in download mode.

designgears said:
Your drivers are messed up... grab the ones from the odin thread and reinstall with the phone plugged in and in download mode.
Click to expand...
Click to collapse
Reloaded the drivers and still get the message. Any other suggestions would be helpful.

Try un-selecting the other options? (auto reboot/time)
I had a similar error message when the "repartition" was selected. Just an idea...

Gave that a shot but no luck
I am almost resigned to the fact I might be stuck with JF6 until Froyo gets pushed out OTA (if/when that happens). I just can't believe it has me this stumped.
Can busybox, the older superuser, anything like that cause this issue? When I wiped back to stock I loaded Unleash the beast because I prefer the older superuser (ninja guy). When I first got my phone I did the adb code for sideloading after doing one click root. That process isn't different from what the guys that made the UTB and Superrooter update.zip files is it?
Well tried running Odin as an administrator and that didn't work haha. Worth a shot.

I dont really know if that could be the cause or not. Im actually having trouble wiping all the data from my phone (I have my own thread, but it could be related). I used Odin 1 click, I used the regular Odin and did everything manually, tried master reset, and also did a factory data reset. Tons of data still on my phone, though. I was contributing it to titanium backup, but it may be things installed from super rooter

Anyone else have an idea that I might try?
Now even Odin one click comes up with this message??? I am really baffled with this situation.
Update: Got Odin one click to work again, I wiped my user data through clockwork. After this reloads I am going to try and do sideloading via the adb codes rather then using UTB or superrooter to see if that makes a difference for me. Still could use any suggestion on what else people have tried in this situation, if you have been in this before.
Sweet life

Still stumped by this issue if anyone has any help for me. Also could this be moved to the new Q&A section. Thanks.

flashman2002 said:
Still stumped by this issue if anyone has any help for me. Also could this be moved to the new Q&A section. Thanks.
Click to expand...
Click to collapse
Do you use the Kies program and if so has it ran an update lately, I had it on my Win7 laptop and when it ran the software update it totally hosed up my drivers and I could not connect to my phone anymore... I had to uninstall Kies and remove all my drivers and then reboot my laptop then I only reinstalled the Samsung drivers and now I can connect again. I won't be using Kies anymore..Anyways I thought I would share my experience in case it might help you..

jhernand1102 said:
Do you use the Kies program and if so has it ran an update lately, I had it on my Win7 laptop and when it ran the software update it totally hosed up my drivers and I could not connect to my phone anymore... I had to uninstall Kies and remove all my drivers and then reboot my laptop then I only reinstalled the Samsung drivers and now I can connect again. I won't be using Kies anymore..Anyways I thought I would share my experience in case it might help you..
Click to expand...
Click to collapse
I haven't used kies since I first got the phone to put contacts in. But I just tried again to give it a whirl and got it to load the kernel. Hell if I know why it worked today compared to before hahaha.

[Q] HELP CWM recovery problem, infuse wont boot

Hi, i just bought a samsung infuse and i was looking for an ICS rom and i found the cm9 unofficial http://forum.xda-developers.com/showthread.php?t=1601844 this one
and i flashed like the thread says and everything went good, ics started like a charm but then i turned off my phone to get into the recovery but i found out to be in a huge problem
My phone wont boot, it goes directly to the recovery (cwm 5.5.0.4) and it looks like a broken screen (sort of, rainbows) its usable but it wont boot, i even tried to reflash it
Would somebody help please?

riikiiee said:
Hi, i just bought a samsung infuse and i was looking for an ICS rom and i found the cm9 unofficial http://forum.xda-developers.com/showthread.php?t=1601844 this one and i flashed like the thread says and everything went good, ics started like a charm but then i turned off my phone to get into the recovery but i found out to be in a huge problem My phone wont boot, it goes directly to the recovery (cwm 5.5.0.4) and it looks like a broken screen (sort of, rainbows) its usable but it wont boot, i even tried to reflash it Would somebody help please?
Click to expand...
Click to collapse
Well I guess you didn't read all the way til post 3 of the thread where you pulled the CM9 unofficial ROM...BTW your probable gonna get flamed since you also didn't make a run thru the the Q&A...since this has been address, well I ran out of fingers and toes to count how many times...but
Go back the op [Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G... go down to post 3, and do a little reading, maybe you should of did some more homework before jumping in, but hey good on you for just jumping and not looking where you might land...
If you require more reading (i suggest) see my links below...ok,
Good luck

yes i know i will get flamed, and i did read the 3rd post about the bootloaders
but i just wanted to know if there is another way to do it, and since English is not my native language, i don't understand everything very well, but thanks

riikiiee said:
yes i know i will get flamed, and i did read the 3rd post about the bootloaders but i just wanted to know if there is another way to do it, and since English is not my native language, i don't understand everything very well, but thanks
Click to expand...
Click to collapse
Ok understood, just relax and re read it again, and go thru the Q and A seciton.
What part are you having trouble understanding...?
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
What I suggest is start over:
Use the one click back to stock and then use the one click to install CWM...which is what you need to get CM9 ics ok,
so first one click back using qkster method:
http://forum.xda-developers.com/showthread.php?t=1524081
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: CONNECTED. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
Then use one click from same op, qkster method:
http://forum.xda-developers.com/showthread.php?t=1524081
post 2... After you have flashed the UCLB3, some of you may want to have Red ClockWorkMod (CWM) recovery to flash another ROM.
Put your phone back into DOWNLOAD mode after your phone has booted up.
Then reinstall the cm9 zip, once you reach this stage, you will have to flash it twice..ok this file...

Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.

timmetal6669 said:
Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.
Click to expand...
Click to collapse
Yes and No...
It is a step up for the infuse, well it will be...
The problem is people are not doing their homework, and have never flashed a ROM, much less know what the letter ICS or CM9 even are, and yes it has brought some challenges but for those of us that have installed and ran it on this phone and other phones, I don't mind assisting others, but they have to do the reading and homework for them self's...
Yes you have your opinion and I don't disagree or agree, but I do hope the ROM with be brought up fully functionally, and it will with the Developer we have working it and others who are "testing" it, the ones who are familiar with...

Alright thanks mate, right now im installing the driver for heimdall, I already read everything you said and the links you shared
Thanks again, you just saved another noob

When your up and running for good, let us know, and don't forget to thank the Dev that provided you with the tools you needed...not me...just pointed you there...

Yes I will

timmetal6669 said:
Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.
Click to expand...
Click to collapse
No one who actually FOLLOWED THE INSTRUCTIONS has had an issue.
I challenge you to find ONE person who has bricked an Infuse with CM9. The only time in the CM9 flashing process one might brick is when flashing the bootloaders to get rid of rainbows - and I have PLENTY of warning that flashing bootloaders is a dangerous and risky process.
Similarly, no one has bricked an I9100 flashing CM9 either, unless the recovery they were flashing away FROM was defective (such as the initial I777 UCLD3 recovery repacks) - but that same defective recovery caused hardbricks for people flashing even rooted stock with no CM9 involvement.
Task650 was right when he replied to you in the I777 thread - he contributed more to XDA when he took a dump this morning then when you spread your bull****.

Thank You "E"....well put...:thumbup: :thumbup:
I hate it when jokers like that guy pipes in, when trying to help others...the op admits to not to be good at his English...

hey, i downloaded everything that i needed
and even a little bit more
but i haven't been able to start OneClick
put my phone into download mode, install drivers for heimdall
I tried with heimdall frontend in the flash tab, just like the tutorial
add every partition, and then when i click Flash
this is what it says
"Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12"
any idea?

ok I am not trying to insult you just wanna ask a few question ok,
{
"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 sure your in Download mode...does it look like this your phone?
I go into download mode like this: I take out my battery, plug in the cable while holding both volume buttons i pop my battery in...bamm download mode...
you will see the pic above....
But once it does go into dl mode carefully place the phone down with still connected to the cable then...
if so then you click the one click to open it and you see the word "connects"..in green, click the button below it flash...
and then it should run thru you will see the blue line go across your phone will lots of remarks running thru on the screen in the one click window....ok

dont worry, but yes i know how to put it into download mode
but the thing is that i downloaded oneclick but i cant run it

riikiiee said:
dont worry, but yes i know how to put it into download mode but the thing is that i downloaded oneclick but i cant run it
Click to expand...
Click to collapse
1) ok, have you tried different usb port and or cable...
2)re-download the one click file again...here is a link
http://db.tt/Y2XEPwGv
3) And this the link to give you CWM, you run this after you have install above and you will have to put into download mode for this....and you will hear the lady voice talking that means it is installing cwm...ok but first do the above
http://db.tt/WEJyXywV

riikiiee.....status check my friend...

elostish venus.
Hey BigJoe
the problem was my computer, i used other one I have here, and now Im good and running GB I really appreciate your time and your help.
From now and on I will read everything I have to read
And thanks again mate, you really helped

riikiiee said:
Hey BigJoe
the problem was my computer, i used other one I have here, and now Im good and running GB I really appreciate your time and your help. From now and on I will read everything I have to read
And thanks again mate, you really helped
Click to expand...
Click to collapse
No problem....glad you found out what the real problem was...
Any time ...:thumbup:

goritat the
Yeah, now back to ICS again
the right way now

[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | Shield Tablet

Link To Main Thread
{
"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"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.

Reserved
Reserved.

Sorry for the question... but how is the process to root a Nvidia Shield Tablet? It supports update 2.2.1?
Thanks!!

tux_topo said:
Sorry for the question... but how is the process to root a Nvidia Shield Tablet? It supports update 2.2.1?
Thanks!!
Click to expand...
Click to collapse
I'm working on a step-by-step written guide, but the toolkit will guide you through the steps to root as well. The toolkit does support the 2.2.1 update. :good:

Noob question: The proccess reset the tablet? Will gone a loose any data?
Thanks!!

tux_topo said:
Noob question: The proccess reset the tablet? Will gone a loose any data?
Thanks!!
Click to expand...
Click to collapse
+1.
not looking to install custom recovery, just root. Looking forward to the progress of this toolkit. Thanks @WindyCityRockr
Sent from my 1+1

tux_topo said:
Noob question: The proccess reset the tablet? Will gone a loose any data?
Thanks!!
Click to expand...
Click to collapse
Mojar7070 said:
+1.
not looking to install custom recovery, just root. Looking forward to the progress of this toolkit. Thanks @WindyCityRockr
Sent from my 1+1
Click to expand...
Click to collapse
Unlocking the bootloader WILL erase all data. I don't know if you could achieve root without a custom recovery but if you plan to flash a custom recovery you will need to unlock the bootloader.

While this tool worked for me, it didn't work well with step 2. It did flash the recovery but I had to manually reboot to recovery for it to work. Selecting yes/next to reboot to recovery after flashing it through the tool only took me to fastboot. That was the only thing I noticed but other than that, everything else worked perfectly. For clarification as well, I did it on newest firmware available right now (2.2.1).

gqukyo said:
While this tool worked for me, it didn't work well with step 2. It did flash the recovery but I had to manually reboot to recovery for it to work. Selecting yes/next to reboot to recovery after flashing it through the tool only took me to fastboot. That was the only thing I noticed but other than that, everything else worked perfectly. For clarification as well, I did it on newest firmware available right now (2.2.1).
Click to expand...
Click to collapse
The reboot option after the recovery flash is supposed to reboot you back to Android because the next step in the toolkit is to push SuperSU, which requires ADB.

WindyCityRockr said:
The reboot option after the recovery flash is supposed to reboot you back to Android because the next step in the toolkit is to push SuperSU, which requires ADB.
Click to expand...
Click to collapse
Well in my case, it didn't do that either, mine ended up in fastboot. In any case it everything works as it should. thanks!

Worked flawless.
After flashing TWRP where it asks to reboot, it does reboot the tablet but the program seems to get stuck on "Rebooting......" even after the tablet have booted.
I tried waiting a min to see if it changed but I had to remove and attach the USB again before it realized it was connected and said "Move to step 3".
I'm happy though because anything that can be done smoother than ADB (even though it is really easy) is appreciated.

Wow, this looks super useful and easy. I was just thinking of rooting my shield again cause I'm sick of adds and just dropped in to see how things were progressing on the development side.
Glad I did now, might give this a whirl today

Edit: This is awesome! I was contemplating rooting my 2nd shield (after my first one blew up after 5 days) and have been putting it off for a while.
I'm used to rooting n'stuff so I don't find it to difficult but this just made things so much easier! I had it unlocked and rooted in a couple of minutes.
Big thank you for your effort and hard work.

I can't seem to get adb working. What do I need to do to get the program to recognize my shield tablet?
Sent from my Nexus 6 using Xparent Cyan Tapatalk 2

Ensure you have installed the drivers.

And don't forget to use an USB 2.0 port! USB 3.0 ports generally do not work.

Is there any way to do this with Ubuntu?

Thank you for this! It looks like an amazing tool, just what I was looking for. I had a Kindle Fire HD and it was a hell lot of trouble to install TWRP and flash roms, and when I saw my brand new shield had a hell of a process to get rooted in Lollipop the Kindle nightmare just flashed before my eyes (I had bricked it once so my heart practically stops every time an android device of mine reboots, in fear it won't turn on again). It's such a relief to see everything automated.
If you read what I had written there before (some questions about how to use the toolkit) never mind me, I found the instructions

i can't get this to work, it keeps saying OFFLINE. i installed everything it requested when I opened the .exe

Unlocked bootloader.
Installed Twrp.
But when i go to recovery mode on my lg watch r it STILL boots to the stock recovery???
Am i doing something wrong?

Really confusing softbrick (small reward offered for fix)

TLDR: LGUP will just straight up not recognize my G5 no matter what. I'll give you five bucks on Paypal for a solution, if that means anything.
{
"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"
}
Hi guys, I try to avoid posting, but I've searched high and low for an answer and I really can't find it.
I've got a T-Mobile LG G5 H830, that I have recently rooted and installed TWRP on it. Last night, I decided to try changing a value in build.prop, stupidly without making a backup first and after I changed the value and rebooted, stuck at T-Mobile bootscreen, go figure. All I did was change a value from false to true for adoptable storage..
Anyway-- I tried factory resetting, I tried flashing that FLUENCE rom I found somewhere here on XDA, I've tried just about every thing I could, before I gave up and decided it would be easier to just revert back to stock and unroot. I wasn't really utilizing root for more than Titanium Backup anyway.
To the point; I've got the LG UP program installed, I've got the DLL for it installed and inserted, and the appropriate .tot file to flash it back to factory default. No matter what I do, no matter how many different COM ports I try, different drivers I've tried etc, I cannot get it to read my phone in download mode. ADB mode works in TWRP still, but this is driving me insane. The only other phone I have is a busted up BlackBerry Priv, and I want this phone working again asap.
If someone can shed some light on whatever the hell I'm doing wrong, it would mean the world to me.
Please.
P.S: yes I've tried just about every USB port on my computer, and I've tried restarting Windows many times.

you have tried jiggling it?

You know what? Hell, if someone finds me a working solution to my problem, I will personally paypal them five dollars. I just want this fixed. I've had LG G3s brick on me obnoxiously and then never come back from it, I don't know what it is about LG phones.. Samsung phones, Nexus phones, and basically any other Android phones I've worked on aren't nearly this hard to restore and repair.

speedanderson said:
You know what? Hell, if someone finds me a working solution to my problem, I will personally paypal them five dollars. I just want this fixed. I've had LG G3s brick on me obnoxiously and then never come back from it, I don't know what it is about LG phones.. Samsung phones, Nexus phones, and basically any other Android phones I've worked on aren't nearly this hard to restore and repair.
Click to expand...
Click to collapse
Use the twrp restore file in the development thread it will revert your build prop back, and from there your phone will work again. Editing build prop is not advised on the H830 has been discussed on numerous threads even before root was established. At least it's only a soft brick .

Have you tried jiggling it perhaps?

so did @wolfu11 get the 5 bucks? his solution should have fixed it.

autoprime said:
so did @wolfu11 get the 5 bucks? his solution should have fixed it.
Click to expand...
Click to collapse
I don't know if he's been back on since his initial post.

wolfu11 said:
I don't know if he's been back on since his initial post.
Click to expand...
Click to collapse
Last Activity: Today 12:52 AM
good luck :fingers-crossed:

autoprime said:
Last Activity: Today 12:52 AM
good luck :fingers-crossed:
Click to expand...
Click to collapse
Not holding my breath lol. That's why I declined any of the root bounty.

Try manually pointing to either the lg drivers, or adb drivers had that same problem when trying to root H830.
Sent from my LG-H830 using XDA-Developers mobile app

IDK if u fixed it or not, but i have a simular issue where LGUP does not recognize my phone. i'm guessing it could be the buildprop could have broken it. i have factory reset my phone, but upon turning on wifi, the phone crashes and i need to factory reset. i am rooted and retain root. My guess is that changing the buildprop causes the phone to be unrecognized. I did backup my buildprop but its stuck in an encrypted backup. Thanks alot gooogle...

Same problem here
I am having the same problem but I never touched my build prop. I rooted and decided to install cm14. When i flashed, none of my partitions are mounting and phone would not boot. I put stock back on and flashed tot and tried mounting partitions and nothing. Now computer doesn't recognize it as well as it will not boot into recovery or android.

I have seen this and I think I fixed it by disabling one of the two, in device manager. 1st listed, iirc.

Barsky said:
I have seen this and I think I fixed it by disabling one of the two, in device manager. 1st listed, iirc.
Click to expand...
Click to collapse
ill give it a shot, thanks

Please help, Samsung A11 - TRWP problem

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.