Related
So I just tried to flash 4.4 on my P605 (file being P605XXUCNE2_P605OXACNE2_NEE.zip).
Sadly, I forgot to tick 'phone bootloader update' in Odin, soooo....now I'm stuck on the Samsung logo with 'Recovery booting' written in blue on the top left edge.
I've searched the Net for a solution, but all the ones I've found require me to remove my battery, which is kinda impossible on the P605 without hardware modifications.
I really need some help here, as I'm sure there is another way to get to Download Mode.
Ilman said:
So I just tried to flash 4.4 on my P605 (file being P605XXUCNE2_P605OXACNE2_NEE.zip).
Sadly, I forgot to tick 'phone bootloader update' in Odin, soooo....now I'm stuck on the Samsung logo with 'Recovery booting' written in blue on the top left edge.
I've searched the Net for a solution, but all the ones I've found require me to remove my battery, which is kinda impossible on the P605 without hardware modifications.
I really need some help here, as I'm sure there is another way to get to Download Mode.
Click to expand...
Click to collapse
Flash stock JB rom,let it reboot then Flash Kitkat rom after... Flash TWRP 2.7.0.1 and let reboot, go into recovery, now should be TWRP, flash latest supersu.zip file(1.99r3). Now Kitkat, rooted and custom recovery.
If you don't want root and TWRP, skip those steps...
Just be aware you will have difficulty accessing external sd card with any but stock file manager and not all 3rd party apps will be allowed to use it (unless rooted)...
ultramag69 said:
Flash stock JB rom,let it reboot then Flash Kitkat rom after... Flash TWRP 2.7.0.1 and let reboot, go into recovery, now should be TWRP, flash latest supersu.zip file(1.99r3). Now Kitkat, rooted and custom recovery.
If you don't want root and TWRP, skip those steps...
Just be aware you will have difficulty accessing external sd card with any but stock file manager and not all 3rd party apps will be allowed to use it (unless rooted)...
Click to expand...
Click to collapse
The problem I'm currently facing is that I can't get to d/l mode, recovery or w/e. It's just stuck in a bootloop...
Thanks for the reply, tho.
Ilman said:
The problem I'm currently facing is that I can't get to d/l mode, recovery or w/e. It's just stuck in a bootloop...
Thanks for the reply, tho.
Click to expand...
Click to collapse
I had the same problem, just hold down power and down vol and get to into download mode so you can tick that bootloader update and it will work.
Took me a few goes to get it to go there... but it did work for me.. Hope that helps
I also found the flash jig for the S2 works to get to download mode...
Don't know what I mean, here's a youtube video demonstrating, just forget the bit with the battery, you just need to insert and power down - https://www.youtube.com/watch?v=V8yqWf6JU3o
Worth around $3 on ebay... Look for S2 usb jig...
jbm76 said:
I had the same problem, just hold down power and down vol and get to into download mode so you can tick that bootloader update and it will work.
Took me a few goes to get it to go there... but it did work for me.. Hope that helps
Click to expand...
Click to collapse
You must do it at the right moment between screen cycles. Took me 1 minute, but for some people here on forum it took 30.
jbm76 said:
I had the same problem, just hold down power and down vol and get to into download mode so you can tick that bootloader update and it will work.
Took me a few goes to get it to go there... but it did work for me.. Hope that helps
Click to expand...
Click to collapse
I've been trying that since yesterday, no dice.
ultramag69 said:
I also found the flash jig for the S2 works to get to download mode...
Don't know what I mean, here's a youtube video demonstrating, just forget the bit with the battery, you just need to insert and power down - https://www.youtube.com/watch?v=V8yqWf6JU3o
Worth around $3 on ebay... Look for S2 usb jig...
Click to expand...
Click to collapse
That looks like a nifty thing, minght look into one if I can't fix it the next couple of days.
xda_user_p600 said:
You must do it at the right moment between screen cycles. Took me 1 minute, but for some people here on forum it took 30.
Click to expand...
Click to collapse
What does a screen cycle mean exactly? Sorry if the question is dumb.
Edit: Just got into d/l mode.
I did that by holding Vol- and power. It restarted a couple of times but in the end it got there. Thanks for all the help.
Try Power + Volume Down + Home instead of just Power + Volume Down, there is a different if you are stuck.
I have a unlocked bootloader EVR-AL00 that has been bricked for awhile now. TWRP is stuck on load screen on erecovery and recovery. I have tried everything to get it to work. I can get to the bootloader screen and flash from Hstool, Funkyhuawei, ADB and Hisuite but it always goes back to the TWRP load screen and stays there. TWRP crashed on me back then and now it seems EMUI is gone forever. Any new tricks out there that might work? Please help if you can! Thank you!
can flash stock recovery via adb?
Which Firmware version is on it?
letschky said:
can flash stock recovery via adb?
Which Firmware version is on it?
Click to expand...
Click to collapse
910120. I've tried that. It seems to flash without errors then boots to the TWRP load screen and freezes...
Steamer2499 said:
910120. I've tried that. It seems to flash without errors then boots to the TWRP load screen and freezes...
Click to expand...
Click to collapse
After flash Stock Recovery can boot into Erecovery?
Power off wait for 10 seconds
Press and hold Volume up and put in the usb cable.
Hold Volume up until you start the Erecovery
letschky said:
After flash Stock Recovery can boot into Erecovery?
Power off wait for 10 seconds
Press and hold Volume up and put in the usb cable.
Hold Volume up until you start the Erecovery
Click to expand...
Click to collapse
That doesn't work either
There is only one wat I came back from the TWRP cycle of death.
I followed the steps for the side load in the OP of this thread. The bottom of the first post.
https://forum.xda-developers.com/mate-20-x/how-to/fw-emui-9-1-0-123-evr-al00-t3935995
The update is listed and can be renamed (I used the 123 update_full_base.zip)
The nocheck.img was a challenge, but I found one in a TWRP backup I had done and save off. Doing a search of XDA later I see that there is also versions in the Mate 20 pro and Mate 10 forums.
Now I have a normal eRecovery, but I cannot obtain root and the recovery StockAL00, magiskAL00 amd newer images changed in bootloader don't seem to make a difference.
Rudolpht said:
There is only one wat I came back from the TWRP cycle of death.
I followed the steps for the side load in the OP of this thread. The bottom of the first post.
https://forum.xda-developers.com/mate-20-x/how-to/fw-emui-9-1-0-123-evr-al00-t3935995
The update is listed and can be renamed (I used the 123 update_full_base.zip)
The nocheck.img was a challenge, but I found one in a TWRP backup I had done and save off. Doing a search of XDA later I see that there is also versions in the Mate 20 pro and Mate 10 forums.
Now I have a normal eRecovery, but I cannot obtain root and the recovery StockAL00, magiskAL00 amd newer images changed in bootloader don't seem to make a difference.
Click to expand...
Click to collapse
I can't get into TWRP. It is frozen on load screen
Steamer2499 said:
I can't get into TWRP. It is frozen on load screen
Click to expand...
Click to collapse
Damn, that's worse than I had it. I don't know if there is a way to HStool or modified HiSuite take a ROM update, which would return you to regular eRecovery.
I'm hoping that can work if you can Fastboot from bootloader through those steps or HiSuite recovery.
With my crazy sideload I cannot root, I get prompted for updates constantly (with updates set off) and HStool & HiSuite didn't work. Since I don't have root cannot do ENMUI flasher.
Rudolpht said:
Damn, that's worse than I had it. I don't know if there is a way to HStool or modified HiSuite take a ROM update, which would return you to regular eRecovery.
I'm hoping that can work if you can Fastboot from bootloader through those steps or HiSuite recovery.
With my crazy sideload I cannot root, I get prompted for updates constantly (with updates set off) and HStool & HiSuite didn't work. Since I don't have root cannot do ENMUI flasher.
Click to expand...
Click to collapse
To bad there's not a patch for TWRP...
I know there are some smart people out there that could tell me how to un-brick my phone
@ajsmsg78 is the smartest one I know on here. He has flashed stock, RR, etc... I bought his phone so he doesn't have one anymore but maybe he knows how to help you.
CCJ22 said:
@ajsmsg78 is the smartest one I know on here. He has flashed stock, RR, etc... I bought his phone so he doesn't have one anymore but maybe he knows how to help you.
Click to expand...
Click to collapse
I spent some time in pm trying to help him but the phone still won't do what it's supposed to. I think he needs to do a data format but he can't get into twrp to do it and Huawei blocks a lot of adb commands.
ajsmsg78 said:
I spent some time in pm trying to help him but the phone still won't do what it's supposed to. I think he needs to do a data format but he can't get into twrp to do it and Huawei blocks a lot of adb commands.
Click to expand...
Click to collapse
Sh*t if you can't help him it's not looking good.
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Larzzzz82 said:
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Click to expand...
Click to collapse
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
simplepinoi177 said:
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
Click to expand...
Click to collapse
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
helpless_user said:
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
Click to expand...
Click to collapse
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
In fastboot you can boot to a recovery.img; fastboot boot twrp.img
Download TWRP .img here.
(that recovery menu allows adb mode also).
Here you can(re)flash zip/image etc.
Format /data to ensure it is not encrypted.
For example, flash the extracted images of the OTA images from Google.
simplepinoi177 said:
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
Click to expand...
Click to collapse
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Not able to figure out the exact fix
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
@OP, I am still stuck with the exact same issue. How did you exactly fix it? After running the solution given, I'm back at the infinite logo screen again.
Edit: It worked, thank you so much! This is a life saver.
simplepinoi177 said:
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Click to expand...
Click to collapse
Hi i have the same issue with different device lenovo tab m10 tbx605L and i cant boot the recovery.img it throws me this error.Can u give me any ideas?
helpless_user said:
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Click to expand...
Click to collapse
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
EDIT: Quoted the wrong poster. My reply is an answer to the quoted poster instead of the poster who revived a dead thread with a question for a totally different device.
Strephon Alkhalikoi said:
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
Click to expand...
Click to collapse
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
safaan0313 said:
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
Click to expand...
Click to collapse
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Strephon Alkhalikoi said:
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Click to expand...
Click to collapse
Hmm well thanks for your indirect F**k off
safaan0313 said:
Hmm well thanks for your indirect F**k off
Click to expand...
Click to collapse
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Strephon Alkhalikoi said:
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Click to expand...
Click to collapse
Right I knew that.I am sorry.I was so damn angry at my own mistake.I AM S O R R Y.But off the record I just repaired my tab
Rooting A10s with Magisk [Very Early Root]
Hello community. I wanted to post my progress on trying to root this device and maybe was hoping for some pointers.
Unfortunately the steps are somewhat complicated, especially since we don't have a custom recovery.
Would appreciate some of the more experienced developers if you could give me a hand, since my knowledge is very very limited (don't know how to compile my own custom recovery, have 0 knowledge on even using git hub lmao)
Thanks for reading, here's what I got so far
Things to know about the A10s
It is a System As Root device
It is an AB device (after Android 10 update)
It has no custom recovery as of yet
The process may also work for the F variant
The process I used to root with Magisk is here: https://topjohnwu.github.io/Magisk/install.html
Special thanks to @topjohnwu for his very detailed guide
Ok and now well, to explain where I'm currently stuck. The final step to finish installation off is to reboot to stock recovery and wipe data. I'm guessing that this will fix the signal problem I have, but can't know for sure until I try. The problem with that is that topjohnwu states as follows:
We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
Click to expand...
Click to collapse
The problem here is that no matter how hard I try, I can't boot to stock recovery
I can boot the device as follows
System+No magisk (signal works here)
System+Magisk (RIL broken)
However I simply can't boot to stock recovery. Apparently I need to leave the VOL + button pressed and keep it pressed but it's simply not doing anything. Even using adb to reboot to recovery and holding the VOL + button since it even shuts down is not doing anything.
I don't know where to go from here, I simply can't boot to stock recovery
Would really like to know suggestions
Thanks for reading!
Currently I am hosting a Telegram group for anybody that wants to follow development as it progresses. But for questions, please keep them here on XDA
Link: https://t.me/a107X
I managed to boot to stock recovery by pressing power vol down and plugging usb in at the same time I think.
Update: Well, I flashed stock recovery with Odin. Managed to boot directly to recovery, wiped data and immediately flashed the magisk patched recovery. However this still did not fix the broken signal problem, as I expected. The search for a fix is still on.
you should follow topjohnwu's instructions for samsung devices..
edit: maybe you are, they are included in the link you posted but youre not specific in the steps youre taking for others to help you.
you could also im sure follow same steps as F variant id think but dont blame me for troubles lol
elliwigy said:
you should follow topjohnwu's instructions for samsung devices..
edit: maybe you are, they are included in the link you posted but youre not specific in the steps youre taking for others to help you.
you could also im sure follow same steps as F variant id think but dont blame me for troubles lol
Click to expand...
Click to collapse
Yeah I'll try that method in due time. But I'm really in no hurry since I've got root anyway and I just use it from time to time, so I just reboot to system+magisk only when I need to and just boot system normally every other time.
ShaDisNX255 said:
Yeah I'll try that method in due time. But I'm really in no hurry since I've got root anyway and I just use it from time to time, so I just reboot to system+magisk only when I need to and just boot system normally every other time.
Click to expand...
Click to collapse
Hey op, did you flash magisk with odin using patched file? if you did, could you share your patched file and the firmware version you used? Odin keeps failing when i try to patch.
MR2_Wei said:
Hey op, did you flash magisk with odin using patched file? if you did, could you share your patched file and the firmware version you used? Odin keeps failing when i try to patch.
Click to expand...
Click to collapse
I think I'll have some time this weekend, I'll try to put a in-depth tutorial with all the files required.
But, can you tell me the error you get on Odin and/or any error messages on your phone?
By the way, the signal problem has been reported on other occasions.
It seems to be a problem on this Mediatek SoC
https://github.com/topjohnwu/Magisk/issues/1801
topjohnwu seems to have just brushed it off so it doesn't seem like it's going to get fixed anytime soon
Sorry for butting in and my ignorance...I need HELP!
ShaDisNX255 said:
Rooting A10s with Magisk [Very Early Root]
Hello community. I wanted to post my progress on trying to root this device and maybe was hoping for some pointers.
Unfortunately the steps are somewhat complicated, especially since we don't have a custom recovery.
Would appreciate some of the more experienced developers if you could give me a hand, since my knowledge is very very limited (don't know how to compile my own custom recovery, have 0 knowledge on even using git hub lmao)
Thanks for reading, here's what I got so far
Things to know about the A10s
It is a System As Root device
It is an A-Only device
It has no custom recovery as of yet
The process may also work for the F variant
The process I used to root with Magisk is here: https://topjohnwu.github.io/Magisk/install.html
Special thanks to @topjohnwu for his very detailed guide
Ok and now well, to explain where I'm currently stuck. The final step to finish installation off is to reboot to stock recovery and wipe data. I'm guessing that this will fix the signal problem I have, but can't know for sure until I try. The problem with that is that topjohnwu states as follows:
The problem here is that no matter how hard I try, I can't boot to stock recovery
I can boot the device as follows
System+No magisk (signal works here)
System+Magisk (RIL broken)
However I simply can't boot to stock recovery. Apparently I need to leave the VOL + button pressed and keep it pressed but it's simply not doing anything. Even using adb to reboot to recovery and holding the VOL + button since it even shuts down is not doing anything.
I don't know where to go from here, I simply can't boot to stock recovery
Would really like to know suggestions
Thanks for reading!
Click to expand...
Click to collapse
I have a Samsung A10S (a107M) had it for a few days - I cannot get the bootloader unlocked. I can get it to the screen where it says long press vol up to unlock bootloader. When I do this it reboots, and starts 'normally' PLEASE if anyone can help I will happily buy you a beer!
SandsCayman said:
I have a Samsung A10S (a107M) had it for a few days - I cannot get the bootloader unlocked. I can get it to the screen where it says long press vol up to unlock bootloader. When I do this it reboots, and starts 'normally' PLEASE if anyone can help I will happily buy you a beer!
Click to expand...
Click to collapse
Just keep trying, and leave the VOL + button pressed even after it reboots. I remember last time I rooted, it took me approximately 4 or 5 attempts to finally get bootloader unlocked. Keep doing it until you can finally see the message that your bootloader is unlocked.
Hii there...
I've been trying to root my SM-107F(Samsung a10s) for months now with no luck,honestly speaking am very close to giving up even I wanted it so bad...And I've tried almost every top recommended methods out there,including using kingoroot,kingroot,irobot,magisk,supersu...But still no luck,the main problem is that I can't reboot successfully into bootloader and when I do so by clicking the vol up and power button simultaneously it just reboot...Plz anyone who has successfully rooted their Samsung a10s plz help me and I know all the side effects and disadvantages of rooting a mobile device including bricking and void warranty and am willing to take the risk...So if there is someone out there who can help,your help will be most appreciated.
Aaron_MK said:
Hii there...
I've been trying to root my SM-107F(Samsung a10s) for months now with no luck,honestly speaking am very close to giving up even I wanted it so bad...And I've tried almost every top recommended methods out there,including using kingoroot,kingroot,irobot,magisk,supersu...But still no luck,the main problem is that I can't reboot successfully into bootloader and when I do so by clicking the vol up and power button simultaneously it just reboot...Plz anyone who has successfully rooted their Samsung a10s plz help me and I know all the side effects and disadvantages of rooting a mobile device including bricking and void warranty and am willing to take the risk...So if there is someone out there who can help,your help will be most appreciated.
Click to expand...
Click to collapse
If you have Telegram, you can join our group and we can give you help in real time. TWRP will most likely be released soon so rooting is going to get a lot easier, if you can wait.
Aaron_MK said:
Hii there...
I've been trying to root my SM-107F(Samsung a10s) for months now with no luck,honestly speaking am very close to giving up even I wanted it so bad...And I've tried almost every top recommended methods out there,including using kingoroot,kingroot,irobot,magisk,supersu...But still no luck,the main problem is that I can't reboot successfully into bootloader and when I do so by clicking the vol up and power button simultaneously it just reboot...Plz anyone who has successfully rooted their Samsung a10s plz help me and I know all the side effects and disadvantages of rooting a mobile device including bricking and void warranty and am willing to take the risk...So if there is someone out there who can help,your help will be most appreciated.
Click to expand...
Click to collapse
i already done rooted my A10s (A107F) but now i want to know if there's someone in here can unroot this devices without flashing the stock rom...
i try flash the original boot.img and it didn't work for me cause it make my phone bootloop..
any suggest maybe...?
ShaDisNX255 said:
If you have Telegram, you can join our group and we can give you help in real time. TWRP will most likely be released soon so rooting is going to get a lot easier, if you can wait.
Click to expand...
Click to collapse
Telegram link please....?
jogijee said:
Telegram link please....?
Click to expand...
Click to collapse
It's on the seccond post
Can you help me I am trying to root a SM-A107M
i need some help here, couldn't find the solution anywhere else, after everything done the way it should be, in the last rooting step when i should get the magisk message: "requires additional setup" so the system reboots into root, i do not get that message at all, it does not appear in the screen, does somebody know what is wrong?
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.
PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image
DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.
Read this thread if you haven't...
blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.
lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.
rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.
PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked
If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.
Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.