Appreciate anyone who can help! I was tooling around trying to unlock my AT&T locked SD1 but was basically unable to get it working. So I decided to undo everything with a factory reset and relock the bootloader...and that's when I bricked my device.
I am unable to go past the bootloader screen and unable to either Start the device or enter Recovery Mode.
Not sure how else to proceed.
So, is the bootloader currently locked?
Does fastboot flashing unlock work?
Renate said:
So, is the bootloader currently locked?
Does fastboot flashing unlock work?
Click to expand...
Click to collapse
Unfortunately, no. Adb is no longer recognising the device and I'm stuck in boot select screen unable to even Start or enter Recovery Mode.
Bootloader is currently locked.
Not that it does a lot of good, but you can see fastboot?
{
"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"
}
This is what I see.
I think you are out of luck until the firehose programer for the DUO out. I got the same device like this. Maybe boot.img is broken for the device, or recovery partition got messed up. Basically the device have to restore from the ground up.
Sadly MSFT does not provide a restore solution other than the recovery image which the device have to enter the recovery mode at least.
JimmyRespawn said:
I think you are out of luck until the firehose programer for the DUO out. I got the same device like this. Maybe boot.img is broken for the device, or recovery partition got messed up. Basically the device have to restore from the ground up.
Sadly MSFT does not provide a restore solution other than the recovery image which the device have to enter the recovery mode at least.
Click to expand...
Click to collapse
I was worried you'd say something like that. Down in the dumps.
May be this can help you?
https://www.reddit.com/r/surfaceduo/comments/wn5joi
Sharkam said:
May be this can help you?
https://www.reddit.com/r/surfaceduo/comments/wn5joi
Click to expand...
Click to collapse
What in the name of all things holy?! Man, I'm gonna have to look deep into this and figure it out. Problem is, I am not nearly as smart as that guy which is itself gonna be a huge challenge. That said, I do have all the patched imgs on my desktop...so perhaps there is a way back. IF I can figure out the process as laid out here.
Thanks for this pal at least it helps.
im here with you i need bootimg from 2022.823.41 ota went threw now stuck.. im on the duo 2
This is the duo 1 forum.
There is a duo 2 forum, but it is less active.
did u tryed
`fastboot reboot recovery`
yes .. it just falls back to bl .. I need the boot.img from 2022.823.41 update . I tried to capture the link but it flashed before I told it.
this is the duo2 btw
Me too I have the same issue. Did you found how to fix it ?
Related
Hey guys,
I've got a problem with my TF300. I have accidentally flashed the blob file from the TF201. Everything worked except the camera. Then i wanted to flash the TF300 Firmware back. I've tried to flash the TF300 bootloader back with following command : "fastboot -i 0x0B05 flash bootloader bootloader.bin" but there was an error and it stopped. I've tried to repeat this step, but without success.
My biggest mystake was to reboot the tablet, because its bricked now.
I've tried to go in the APX mode, in the beginnig it was not recognized. I've tried it several times and now its recognized.
Now I need the right commands for the NVFlasher to flash the TF300 bootloader back, because the NVFlasher was made for the TF201.
If I try to flash the bootloader this happens (see picture)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A friend of mine tries to repair my tablet with the following equipment: Riff JTAG Box,ORT JTAG Box.Flasher Boxen:MT Box,Z3X LG/Samsung,Setool3,JAF Box,Micro UFS3,Cyclone Box,XTC Clip.Infrarot-Rework Station Jovy RE-8500 u.v.m.
So what can i do? I am grateful for any help.
Thank you.
Hey
Nobody here really has an idea !?
I think we have to wait for nvflash specific to the tf300t
I may be out to lunch but.... flashing a boot.blob should not change the bootloader... did you try to flash the correct boot.blob? If you have twrp, you should be able to flash it from the terminal..... I don't see where you mention if you have access to recovery or not and as far as I am aware, the only way to get to apx is through nvflash... not sure how you managed that or are you calling fastboot mode apx? In apx all you see is a black screen on the tab......
Need more information to be able to help you out although I am pretty sure there is also a TF300 forum that may help...
Hi thanx
yes the only the only apx mode is: (
No fastboot not adb no recovery!
Screen is black
rudl1220 said:
yes the only the only apx mode is: (
No fastboot not adb no recovery!
Screen is black
Click to expand...
Click to collapse
You have surpassed my level of expertise wish I could help but don't know what to tell you with this one....
The device unknown is concerning.... I am guessing because nvflash hasn't been released for tf300 to my knowledge, the program probably doesn't know what to do with it... only thing I can suggest is posting in the nvflash thread and see if anyone can help there... you will mostly like get flamed by a few people but if someone can help it might be worth it.
I was really dumb and wanted to unroot so i decided to flash a stock_recovery.img to my Huawei LYO-L01. When prompted where to i selected boot without looking it up first :crying: Now when i open my phone i get a black screen that says
Android system recovery <3e>
LYO-L21C479B102
Reboot system now
apply update from ADB etc. etc.
I can still boot into TWRP and have a folder with some recovery files from when i rooted my phone.
How can i get my phone back into a bootable state?
I imagine i can just get a fresh boot img form extracting this update.app i see everyone taking about but i dont know where to get an update.app. Can someone point me towards a download?
{
"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"
}
Nafekop said:
I was really dumb and wanted to unroot so i decided to flash a stock_recovery.img to my Huawei LYO-L01. When prompted where to i selected boot without looking it up first :crying: Now when i open my phone i get a black screen that says
Android system recovery <3e>
LYO-L21C479B102
Reboot system now
apply update from ADB etc. etc.
I can still boot into TWRP and have a folder with some recovery files from when i rooted my phone.
How can i get my phone back into a bootable state?
I imagine i can just get a fresh boot img form extracting this update.app i see everyone taking about but i dont know where to get an update.app. Can someone point me towards a download?
Click to expand...
Click to collapse
Its complicated
Sent from my KIW-L21 using Tapatalk
Al Fareed GSM said:
Its complicated
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
I'm kinda desperate to get my phone working agian so any help is appreciated
Can you tell me what makes this problem complicated?
On a side note, what is the intended use of stock_recovery.img and stock.img and where am I meant to flash them?
ok i now see i WAS meant to run "flash recovery stock_revovery.img" or something to that effectin the console but i guess i have bigger fish to fry right now
oh wait i had a backup PANIC AVERTED
Anyone know how to fix a boot loop issue? Looks like my smartphone decided to go into a boot loop. My Realme GT2 Pro isn't seen by my PC in this state.
Soft-brick or hard-brick? Can you access the bootloader? Do you have ABD drivers on your PC?
I don't know the difference between a soft brick and hard brick. It starts to boot and recycles. I can manage only to get into this strange recovery mode. I tried all 3 options you see on the screen and there is no difference.
{
"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"
}
https://imgur.com/DE0nePX
It's soft-bricked... it's easy to fix... But do you flashed the phone or just started bootlooping all of nothing?
It just started this yesterday for no reason. I was deleting some apps I don't use when it started.
How can I fix this when the device can't be seen by the PC?
Since you said that tried all three options from Recovery mode means that there's no more data to recover... So, just re-flash the phone... You'll need the ADB drivers for the PC to recognize the phone on bootloader...
I managed to get the phone into a condition where it is recognized by a qualcomm QDLoader. Where do I go from here?
This is EDL mode... This is for severe cases, which is not yours, for now... Is your phone unlocked?
I think the phone is unlocked right now
No fastboot available so how do I flash an image in EDL mode?
Are you sure you doesn't have access to bootloader? Start the phone with the power button + volume down...
Anyway, in EDL mode you can flash your phone with QFIL, but it's very buggy... Or with MSM Download Tool, which is flawless, but the problem is getting access to this software... That was my problem until today as you can see here...
MSM Downloaf Tool for realme GT 2 Pro
Does anyone know how to access this tool? This is ridiculous, realme has no useful tool to flash their phones and the one that is useful are impossible to access... The only one that I have access was one patched for some especific Oppo phone...
forum.xda-developers.com
I guess I'm willing to pay to have this resolved or return for a refund
I paid a small fee and this was resolved
robert3892 said:
I paid a small fee and this was resolved
Click to expand...
Click to collapse
the solution is change slot
aaronisaacm said:
the solution is change slot
Click to expand...
Click to collapse
Change slot?
Hello, so I decided to try an root this junky phone I have which is a moxee m2160. I followed a guide on youtube, I unlocked the bootloader, then got magisk. I then created the patched-magisk.img then used my computer & fastboot to flash it too the device. I was pretty sure I had gotten it until I rebooted it an it booted back too the bootloader. I'll upload pics of my screen to show you where Im stuck. Am I able to fix the phone with my pc somehow? I probably should've gathered more info before I did it. Thanks for any answers in advance.
{
"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"
}
This Is the name
e..
Is there anything I can do through adb or fastboot to fix it?
whisper42000 said:
Is there anything I can do through adb or fastboot to fix it?
Click to expand...
Click to collapse
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Something like this part I forgot the part with the empty vbmeta or from stock. Search. Good luck more I don't can help. I read it only somewhere
I've done the same thing to this phone every option on that screen doesn't do anything just reboots to the same screen. Does anyone out there have this phone and have the stock ROM or anything at all that would help restore this phone. I found out it is made by KonnectOne it is a government assistance phone from Assurance Wireless and that is pretty much all I can come up with. Any assistance at all would help a noob like myself, learning as I go. Thanks.
Specs for this devices are here https://phonedady.com/moxee-m2160
Greetings members. The support team over at KonnectOne has granted my request for factory firmware for this smartphone. I am presently in the process of establishing a secure file transfer protocol with support to download the package. I will have it later this week if any members are in need of it
I have the stock Firmware.. just got it today. Who needs it
dexscam37 said:
I have the stock Firmware.. just got it today. Who needs it
Click to expand...
Click to collapse
It's been officially released by the manufacturer, after weeks of haggling with KonnectONE's office of general counsel. Here's the link.
File on MEGA
mega.nz
I have three earlier builds as well if anybody needs them.
Now to go root my moxee
What about a twrp ?
Viva La Android said:
I have three earlier builds as well if anybody needs them.
Click to expand...
Click to collapse
how to i flash the stock firmware???
dexscam37 said:
how to i flash the stock firmware???
Click to expand...
Click to collapse
QFIL (Qualcomm Flash Image Loader)
Download Qualcomm Flash Image Loader (QFIL) - Qualcomm Tool
Download Qualcomm Flash Image Loader (QFIL) to flash stock firmware on Qualcomm based Smartphone and Tablets easily in few clicks.
androidmtk.com
You will find a how-to guide in the link I sent. You will need to install the Qualcomm EDL drivers and boot your phone into EDL mode in order to use QFIL. To boot into EDL, hold volume up and down simultaneously while connecting your phone and PC.
I will be posting a full QFIL guide this weekend.
Hi guys!
Wo, i've got a question about Realme 7 bootloader, since i dont really know where else i could ask.
I unlocked my phone using THIS guide.
Everything went smoothly, until the end. After the phone rebooted, i tried going into fastboot mode (bootloader). Well... I encountered a problem:
For a few seconds, there was a string of numbers, and at the bottom was this message:
"the serial is not match.
fastboot_unlock_verify fail"
Sorry for the bad quality​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And well, i wanted to ask if anyone had simillar issue, and do you maybe know how to fix it?
I think you would be able to install a custom recovery and ROM within the recovery menu cause the Fastboot mode is only enabled thru the DeepTest which I don't think it worked (it also didn't in my situation)
DaCrab said:
I think you would be able to install a custom recovery and ROM within the recovery menu cause the Fastboot mode is only enabled thru the DeepTest which I don't think it worked (it also didn't in my situation)
Click to expand...
Click to collapse
Well, actually fastboot worked after i flashed stock ROM, but i couldnt boot at all to the bootloader. But i still wasnt able to install TWRP through realme recovery, idk how to even do this.
I red in a forum that someone had the same problem but managed to install a custom recovery thru the recovery menu cause the fastboot mode
I had also managed to do the same but I didn't have any custom recovery afterwards idk why but when I tried it just kep flashing "Recovery..." and not redirecting me anywhere
DaCrab said:
I red in a forum that someone had the same problem but managed to install a custom recovery thru the recovery menu cause the fastboot mode
I had also managed to do the same but I didn't have any custom recovery afterwards idk why but when I tried it just kep flashing "Recovery..." and not redirecting me anywhere
Click to expand...
Click to collapse
Hmm this is a weird problem. First and last time buying realme phone for anything root-related haha. I also had a problem with magisk, since it just said "download failed" after i tried flashing it in recovery. I did download the .apk file and rename it for zip file, zo it should be good to go, but idk.
Hello Realme 7 user,
Don't worry I had this problem too, I had a hard time unlocking the bootloader and after that I was disappointed fastboot wasn't working when I entered the RUI recovery, for most phones fastboot is enabled after you unlock the bootloader and the key combination for Realme 7 isn't actually POWER BUTTON + VOLUME DOWN, this key combination will bring you in the normal RUI recovery.
I found a method which is working but I don't know if it really depends on the firmware (I was using RUI1 A10 when I found this) but you actually boot into the OS, then go to developer options, enable USB debugging and fire up an ADB Shell and then type adb reboot fastboot.
Don't be scared, it will reboot into the RUI recovery but fastboot it's actually enabled now. You can verify if fastboot is enabled by typing fastboot devices. See if it works now.