Hey I'm new to this forum and Android Tablets in general. I have received a Vodafone Smart Tab 4G, which doesn't boot up. It's an old Tablet and it hasn't been used in a couple years. I want to see if I can make it boot up and test whether it's still usable for minor tasks. I thought I'd try to install an update using an SD card, but it's surprisingly impossible to find anything from an official source. The service menu does say "KTU84P release-keys" which seems to suggest that it has Android 4.4.4 installed.
What I've tried so far:
1: Go into the service menu and do a factory reset.
2. Try to find an update file to install through SD card method (to no avail)
3. Put some alleged stock roms onto an SD card and try to use the update function (fails on the verification step)
4. Installed ADB & Unsigned Mediatek Vcom Drivers on Windows 10. ADB has no connection to the Tablet.
5. Downloaded and tried SmartTab4G_Recovery_KK_benjaminwan to no avail. It gets stuck at "waiting for device".
6. Downloaded SP Flash tool, but failed to find a ROM for the Smart Tab 4G with a scatter file.
7. Out of desperation I tried to flash it with a Smart Tab 3G Rom which had a scatter file, but when I press download nothing happens.
My current understanding is that the standard service menu isn't meant to be used to flash the firmware. If I had an official update file I might have had some success, but I couldn't find one. All the other attempts involving a connection to my Windows 10 PC failed, which seems to indicate that I might be using bad drivers. I'm honestly at my wits' end and I don't understand why this is any more complicated than going to the manufacturers website, finding my device, downloading the most recent system software and flashing it through the service menu. Hope someone can help me out with this one.
Update: Tried a different computer. Partial success. Device manager actually recognized an Android device this time. I installed the usb driver and the recovery batch actually didn't get stuck on "waiting for device" this time. That's great news, although I didn't get much further. Here's what I got:
{
"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"
}
Thread can be closed. I got it after all with the help of the available information. Turns out the recovery.bat was a dead end. Not sure why it didn't work for me with the batch. I tried the approach explained here with cmd and it worked fine.
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
Once I was in the cwm everything went smoothly since verification was disabled and I could install a custom rom. This probably took me way longer than it should've, but at least it's working now.
Related
So I tried to flash CyanogenMod 12 to my phone, however, because this was my first time doing this sort of thing, I missed turning off the security on my phone before I wiped the phone. Obviously, at this point it was bricked, and after searching around, I discovered ADB Sideload. So I went through the process to get ADB, downloaded Android SDK and installed the platform tools, and I thought I was going to be able to save my phone. However, when I ran the TWRP ADB sideload, this happens when trying to input my file View attachment 3306335
I tried to check the drivers and found the HTC One X+ drivers, however when I try to install the drivers, this happens
{
"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"
}
When it does sometimes work, it gets to around 40% then just stops, or does "Total transfer 0.01" or something like that
There's also the problem that I couldn't actually flash a recovery without using the tool built for it by somebody on here, and that wouldn't let me get ClockworkMod Recovery for some reason
Please help me here, I'm incredibly stuck and even trying a RUU doesn't do anything
By the way it seems to connect just fine outside of ADB Sideload, it even gets detected by ADB when the server actually works and doesn't fail to start "ACK"
(EDIT) I do hear the phone disconnect and reconnect when I enter Sideload
TezzaBP said:
So I tried to flash CyanogenMod 12 to my phone, however, because this was my first time doing this sort of thing, I missed turning off the security on my phone before I wiped the phone. Obviously, at this point it was bricked, and after searching around, I discovered ADB Sideload. So I went through the process to get ADB, downloaded Android SDK and installed the platform tools, and I thought I was going to be able to save my phone. However, when I ran the TWRP ADB sideload, this happens when trying to input my file View attachment 3306335
I tried to check the drivers and found the HTC One X+ drivers, however when I try to install the drivers, this happens View attachment 3306350
When it does sometimes work, it gets to around 40% then just stops, or does "Total transfer 0.01" or something like that
There's also the problem that I couldn't actually flash a recovery without using the tool built for it by somebody on here, and that wouldn't let me get ClockworkMod Recovery for some reason
Please help me here, I'm incredibly stuck and even trying a RUU doesn't do anything
By the way it seems to connect just fine outside of ADB Sideload, it even gets detected by ADB when the server actually works and doesn't fail to start "ACK"
(EDIT) I do hear the phone disconnect and reconnect when I enter Sideload
Click to expand...
Click to collapse
Uninstall HTC sync and leave drivers. If that is indeed installed.
Lloir said:
Uninstall HTC sync and leave drivers. If that is indeed installed.
Click to expand...
Click to collapse
I'll try that
Unfortunately that didn't do anything
Hello,
First I want to thank this forum for providing the information. This forum was a help in the process finding out this fix!
NOTE: I'm not claiming that this methode will fix this problems for everyone but it worked for me so maybe you can give it a try.
Problem/My situation:
I've tried to root a Samsung Galaxy S3 GT-I9300 with the CF-Root-SGS3-v6.4, but after the proces my device wasn't rooted so I placed a SuperSu zipfile on my internal storage and flashed twrp-3.0.0-0-klte with odin on the device. I booted in recovery and installed SuperSu. Now my phone was rooted properly said the Root Checker app. But... when booting I'm never asked for a SIM pincode and my IMEI disappeared. After some googling I found out I had to fix the files in the EFS map..
I only backed up through 'Backup and restore' with my samsung account.. so that was quite useless.
What you need:
-Phone must be bootable in recovery and download mode
-PC with Kies and internet connection
******************your data will be lost********************
What I did/Solution:
Boot in recovery, go to 'Wipe' > 'Advanced', I checked ALL boxes and did the wipe.
I turned my device of.
Now what you got to do is pull your battery out and take note of the 'S/N', mine has this format: xx0xx0x0xxx
Now start Kies on your pc and connect your phone. Under 'Tools' you will find: Firmware upgrade and initialization, go there. You will be asked for your model, enter: GT-I9300, after that you must enter the S/N you found on the sticker under your battery.
As you follow the proces you put the phone in download mode (volume down, home and power button) and if you follow the steps mentioned on screen you will eventually get to a screen with 'Software update and initialization completed', it will tell you that the device will reboot and that you have to connect the cable afterwards...
Now, wait till you see the android logo and wait till you get to the
{
"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"
}
.
In my case it got stuck here, so I pulled out the battery.. And I placed it back in and booted normally.. Everything was okay, it worked!
So that's all, I hope this will help you with this problem!
EDIT:
Now, If you want to root the device:
1. Connect the phone to your PC
2. Download twrp-2.8.6.1-i9300.tar (Make sure it is this version! https://dl.twrp.me/i9300/twrp-2.8.6.1-i9300.tar )
3. Download SuperSu zip (I used 2.65)
4. Place the SuperSU ZIP on the phone's storage
5. Open Odin and load the twrp tar in AP and flash..
6. After rebooting turn your device off and boot in to recovery
7. Go to 'Install' and navigate to the Supersu zip and install..
8. After rebooting you should have a rooted GT-I9300
Hey there,
Thank you for your post.
I unforunately am in the same position as you and the above method I've tried many times, but it doesn't seem to work.
I'm currently playing around with other ways and means, so hopefully i'll be able to figure something out cause I flat out refuse to arrange hardware to fix it or send it to a Samsung Service place. They messed it up using the software updates surely they can fix it too!
I'll let you know how I get on.
Cheers
So, I've bought a Xiaomi Mi Pad 3 with a Chinese Rom, and I was following a tutorial to flash a new rom into it.
I basically did the following:
Installed MediaTek Drivers on PC
Opened "Smart Phone Flash Tool"
Specified Download-Agent as DA_SWSEC.bin and Scatter-loading File as the ROM
Unchecked preloader and clicked on "Download"
Connected the Xiaomi Mi Pad 3 to the computer while pressing Volume Down
Then, at this point, the computer crashed with a blue screen of death with the error "BUGCODE_USB_DRIVER". Here is the diagnosis of the error:
{
"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"
}
After that, the Mi Pad won't turn on, won't respond to any button and is not recognized by the computer.... I think I might have hard-bricked it.
I've found a tutorial about recovering a Mi Pad 1, but one of the steps is to make a bridge in the SD Card slot, which Mi Pad 3 don't seem to have.
I'm a developer myself, I know my way on things, I have a VM Linux, I'm willing to open the tablet and do whathever it costs to recover it.
Please, what can I do??
Please, anyone?
I FUC*ING RECOVERED MY FUC*ING TABLET. FUC* YEAH!!!!!!!!!!!!!!
I don't know exactly what it was, but I kinda did the following:
- Installed the latest SP Flash tool from spflashtool.com on my PC
- Installed Mi PC Suite for drivers and such
- To help debug, I had a freeware called "Free Device Monitoring Studio", to better understand what's going on on my USB ports
- I was playing a little with the connection/desconnection of the device on my computer, trying to understand how it was. I saw that Kali Linux running under Oracle VM kinda recognized it as a Mediatek device, but couldn't do anything else than that. With that info, my hopes went a little higher, because it wasn't completely dead after all.
- I opened Flash tool, configured it to used the same ROM and files I was using when I bricked it, because I'm pretty sure they weren't the cause of the brick and clicked "Download"
- Then I began messing with the tablet trying to make it be recognized by SP Flash Tool, upon turning it on and off and switching USB ports and connecting them directly to the motherboard USB ports instead of the frontal USB ports
- Then at one point it suddenly recognized and started downloading and flashing the new ROM. I faced some errors but with Format all + Download and having to disconnect/reconnect the batery to make it recognizable again and some little tweaks here and there, it ended up working.
My tablet is working fine now
Hello there,
my issue is that when i go in bootloader mode, i have a blackscreen, then my phone switch off. The system ui (custom rom Crdroid) and the recovery (orange fox) are working well.
I recognize also that when i reboot, i don't have anymore the MI logo where you have the status of your bootloader when it's unlocked.
More of it, when i plug it on windows , i cannot access to its usb storage (i tried also in mounting it through twrp, but same issue), nothing appears. For example, with an "adb devices" cmd command, no device can be found.
When i check the Windows devices manager, i can see an "unknown usb device" (i tried to force to reinstall drivers on it like the latest google usb driver, but windows refuse it, saying that it has the best and latest one for it).
{
"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"
}
Debugging mode is well enabled
Drivers have been reinstalled (the latest miflashtool install all what is needed)
Nothing appears on my smartphone when i plug it to windows (before i had a notification ot choose in charge mode, usb mode, etc...)
Plug to different usb port has been done without succeess
The phone doesn't appear in miflashtool obv
Restoring a previous backup didn't change the issue (i'm using the custom rom crdroid).
I guess all the things are linked but how i can fix it if i don't have access anymore to my bootloader mode to be able to flash some *.img via fastboot or if i cannot transfer files to my phone to operate in recovery, and more WHAT to do?
I hope you guys, will be able to help. The issue can be really annoying, and stuck me in "no rom update and no transfers of anything possible" situation.
Thank you beforehand
@bonbonboy
Try flashing the firmware through recovery from here https://androidfilehost.com/?fid=11410963190603850663 then reboot device and send it to bootloader via command adb reboot bootloader
It works like a charm!
Mi logo back, adb commands run, usb transfers work and no more error in the device manager.
You saved my day :good::good::good: Thanks a lot !
Hello my question is how to downgrade my samsung j330f from android 9 pie to 7 nougat ?
I try all firmwares with odin but bootloader on my phone sad device 4, binary 3 . How to solve that .
how to do this downgrade ? Can anybody help me ? must be some way...
On odin sad FAIL
{
"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"
}
did you ever figure out how to?
Step 1: Enable USB Debugging
The first thing you need to do is turn on Developer Options on your phone by going to Settings, finding the About phone section, and then tapping the Build number until you get a message that says You are now a developer!.
Next, go into Developer Options and enable USB debugging and OEM unlocking.
Step 2: Connect Your Phone to Your Computer
Connect your phone to your PC with a USB cable.
On your PC, navigate to the location where the SDK Platform Tools folder is saved and put the Android factory image you downloaded there. Factory images usually come in ZIP files that contain IMG files; unzip the factory image right there in the Platform Tools folder.
Now, while still in the Platform Tools folder, hold Shift and right-click inside the window, and then select Open PowerShell window here.
In the PowerShell window that opens, type adb devices to check if your phone is being detected. If it is, you should see its serial number listed. If not, try using a different USB cable.
Step 3: Unlock the Bootloader
Once your device is in fastboot mode, now it's time to unlock your phone's bootloader. This is a crucial step as without unlocking the bootloader, you can't install the previous version of Android on your phone.
Depending on your device, type fastboot oem unlock, and if this doesn't work, type fastboot flashing unlock instead. If everything goes well, you should see a confirmation on your device that the bootloader is now unlocked. This step will also wipe your device.
Step 4: Install the Older Version of Android
Some manufacturers will include a "flash-all" script as part of the downloaded factory image that will automatically flash everything for you. If this is the case, the script should be in the SDK Platform Tools folder along with the IMG files you extracted.
Now, double-click on the flash-all.bat script. A box should pop up showing you the flashing process as it happens. Please do not unplug your phone during this process!
Your phone should now restart. If everything went well, you should now be running a downgraded version of Android. You'll need to set your phone up again from scratch.
Greetings,
J Wick