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.
Related
Hey,
I recently got a cheap, slightly used chinese version Nokia N1. But because without the Google Services its pretty much useless to me, I want to root it and install a custom ROM.
I followed 2 tutorials:
https://forum.xda-developers.com/nokia-n1/help/nokia-n1-root-t3125771
and
https://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
But I always get stuck on the part with the Recovery Launcher.
{
"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"
}
To give some background, here are the steps I did:
Because fastboot and the launcher won't see my device if its in MTP or PTP, I disabled both. That seems to work fine.
I "unlocked" oem in the developer settings and also allowed USB debugging.
I started the Recovery Launcher with admin privileges and used option T4.
It boots into recovery mode, but I just get errors all over the place bacause the device is still locked. So i just typed "fastboot oem unlock". Then T4 again.
Thats where this error occurs. From what I read, this should put me into a CWM recovery session. But it doesn't. It just stays in the fastboot mode window.
I'm pretty new to this android modding thing, so don't expect to much knowledge from me.
with much thanks
~David
Bump
I really hope bumps are allowed here
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
nuzzydev said:
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
Click to expand...
Click to collapse
The thing is, there are no other solutions out there I really know about. I searched google up and down and got no real result.
I think my problem is that my android version isn't 5.0.x, like almost every english tutorial suggests. It is 5.1.1.
oh God... my fault sorry
Recently I have found in my drawer an old Yarvik Noble 97ic+ (Tab09-410) tablet, I got around 2014. Unfortunately it had a broken DC charging connector and the microUSB wasn't enough to kickstart it back to life. So I decided to disassemble the tablet and after some time I managed to charge it and actually turn it on. It booted up and everything. I left it to charge a bit more, but after coming back I found that the tablet no longer boots and all I can get is the "YARVIK" logo stuck on the screen. I have found another customer with exactly the same problem - He charged the tablet for a bit too long and bricked it.
What I can do with the tablet is get it to show with the "adb devices" and I can get it to STOCK recovery, which unfortunately only allows to flash images verified by the manufacturer. I tried all the options in recovery - wiping the cache, data/factory reset and recovery system from backup.
The Yarvik brand, which was a small company in the Netherlands went bankrupt a while ago and there isn't any support or stock firmware images on the web. I only found some dead links on the site arctablet.com, where I also found some users that successfuly flashed a newer android - a rom for Odys Iron CM12.1 lp 5.1.1 (stock is 4.2.2)
When I reboot it into bootloader the screen is completely dark and "lsusb" command shows only the usb port without any device name.
When I tried the "adb reboot-bootloader" command in the console, the device is no longer recognized (with fastboot devices). I assumed it might be because of missing windows drivers, so after trying a whole bunch of them I connected the device to linux with same results. When I reboot it into bootloader the screen is completely dark and "lsusb" command shows only the usb port without any device name. Therefore I cannot install any custom recovery like CWM or TWRP which would allow to flash another than the original Yarvik image.
Is there anyone that could provide the original Yarvik "Tab09-410.img"? Any help is widely appreciated. Thank you for your precious time.
{
"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"
}
Bump. Anyone?
search for odys-iron-jb4.4.2-V1.04
willem
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?
Hi All,
A friend gave me his broken Pixel 6 phone to see if I could fix it (I hope that it can)
Would any of you know what I can do about the issue below?
Fastboot Mode
I do not even know how I reached this mode. Hope this helps in debugging the issue
{
"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 able to see the the device via adb (see image below), but I am unsure what to do next
Coleslaw1444 said:
Hi All,
A friend gave me his broken Pixel 6 phone to see if I could fix it (I hope that it can)
Would any of you know what I can do about the issue below?
Fastboot Mode
I do not even know how I reached this mode. Hope this helps in debugging the issue
View attachment 5630341
I am able to see the the device via adb (see image below), but I am unsure what to do next
View attachment 5630343
Click to expand...
Click to collapse
Try Android Flash Tool
Can you run adb reboot bootloader?
Lughnasadh said:
Try Android Flash Tool
Click to expand...
Click to collapse
Thank you for the resource. I am getting the following below...there is no prompt on my device
mhrussell1 said:
Can you run adb reboot bootloader?
Click to expand...
Click to collapse
I tried it via fastboot mode ("Restart Bootloader" option and when in recovery mode I typed the command) and it leads to the initial video.
Coleslaw1444 said:
I tried it via fastboot mode ("Restart Bootloader" option and when in recovery mode I typed the command) and it leads to the initial video.
Click to expand...
Click to collapse
I think that is different. The adb command should have the device stay in bootloader mode so you might be able to flash the latest factory image.
Got it to work. For future reference I needed to install the USB drivers and the Android Flash tool worked perfectly, thank you very much!
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 ?