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
Related
Hello XDA Guys,
I have my Memo Pad ME172V broken while I was trieng to Root it and I have used the command "adb reboot bootloader"
so it went down and did not came back again
when I start it it goes directly to this screen " No USB cable connected"
{
"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 when I connect it to My PC I find in device manager uninstalled device "WM8950 USB Device"
I tried to install a driver for it it only accept Android ADB driver and APX driver but not running as one so I can not use ADB command with it or APX mode
After I install the driver the logo on the screen changes to a green android man with a yellow helmet and written "Ready for download"
I tried everything I know till now
Using power and volumes button in many different combinations
also tried to use Easyflash
changing the USB windows Driver
but no luck at all
PLEASE HELP ME
Thanks
Same issue here man - a friend has given me theirs to try and fix. Did you sort it out?
I've tried multiple Fastboot drivers, but fastboot devices doesn't see anything.
Any Help From XDA Profissionals
Hey Guys, any one here Can help Me
I am not an expert, but does the device still recognise external SD?
If so, maybe this will work:
1. Download a stock util from here https://www.mediafire.com/folder/23ycdy8i4f8mu/ASUS-me172v
(I previously used http://www.mediafire.com/download/3rn6cnzh95va6np/SD_RESTORE_UTIL_20130724_STOCK.ZIP)
2. Format external SD in FAT32 (so at least 4GB microSD card)
3. Extract contents of the stock util zip to the root of the SD
4. Put SD in the device and hope it'll boot from there, so you can restore a previous flash.
Maybe the device has to be rooted for this to work, in that case look here: http://forum.xda-developers.com/showthread.php?t=2216390&page=27 and search Google for Me172vRootUtil_v0.1.zip
I hope this works, and if not, maybe someone else can help you!
hi guys..
same condition.anyone has solve it..? device was working but i only went to fastboot mode then "ready for download"..
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
Hi there,
I'd really be grateful for any help anyone can give. Yesterday, my Honor 7C got stuck in a boot loop, restarting at the blue Honor screen continually until the battery runs out. It's impossible to boot it into recovery mode using any combination of key presses. It just keeps restarting.
Can someone please help? I don't really mind losing the phone, but ideally I would like to save some of the data on it, as it had been a while since I backed up.
I understand that the way to do this might be to flash the stock ROM, root the phone and then run a data recovery program like EaseUs. Is this correct?
Also, I have tried to flash the stock ROM but really have no idea how to do it. I got half way through using SP Flash Tool before I realised that the Honor 7C is not a Mediatek phone.
Also, I can't find the stock ROM (LND-L29) anywhere except on pretty dodgy looking websites. Is there a reliable source for stock ROMs anywhere?
Any help would be really gratefully received. Thanks!
B7C
@Bricky7C
Your Honor 7C has a Qualcomm chip-set hence you might use free-of-charge QPST ( read: Qualcomm Product Support Tool ) to re-flash device's Stock ROM.
{
"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"
}
Turns out my bootloop was caused by a hardware problem after all - ripping open the side of the phone solved it.
However, for anyone who stumbles across this thread with a similar problem, jwoegerbauer's suggestion of QPST was very helpful, but the tool on the site would not install for me on Windows 10. I kept getting an "installation was interrupted error". However, I found a working version of the tool at:
androidmtk dot com fslash download-qpst-flash-tool
[I'm a new user so XDA won't allow me to post a URL]
I scanned for viruses and the installation didn't cause me any issue, though I never ended up having to use it in the end.
Hello everyone!
I have a ulefone armor x5 pro (MT6762). I tried to install twrp without success, as the port available in the forum is for the MT6763 chip variant. Before further experimenting (my phone entered in a bootlop that i resolved reflashing recovery.img), After that experience, I decided to make a backup of my own stock rom as the available on the ulefone official site seems not to be the right one (armor X5 not pro). Using SP_Flashtools, I tried to do a full reading of my device, and the power supply was cut off in the process. At this point, the device was dead. Then I was able to flash the rom provided by the manufacturer. The process was completed successfully. However, the phone did not turn on again. I disassembled it to disconnect the battery and sp flashtools recognizes it, but it remains stuck in "downloading DA 100" and does not advance any further. Try reinstalling drivers, changing laptops, different versions of the program, and SP_MDT but the same thing always happens. Downloading DA 100% (red bar at the bottom) and nothing else. At this point I don't know what else to do. My phone does not turn on at all. Any suggestion will be highly appreciated.
Thankyou!
EDIT: PROBLEM SOLVED. The problem was the firmware that i tried to download. The manufacturer has many variants of the same device name. Now the phone has back to life.
Hi, I have the Ulefone Armor X5 2020 version (android 10)with the mt6762 mediatek processor ( description of the seller, the ticket on the box and Ulefone description) this is very confuse why the stock rom for this device is for mt6765 and I read mt6765 with sp flash software.
My problem is what this was bricked from factory, its work unstable and rebooting ramdomly.
I try many things like factory reset, wipe the cache, (when wipe the cache the display show E: Fota installation aborted, E:: No such file or diretory) reflash the stock firmware, reflash preloader and recovery separately, but the problem persist.
And one of the first messages i read was system corrupted.
{
"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"
}
Please Help!!!
Hi, first time playing vith custom ROMs
I've SIM unlocked and unlocked bootloader of my old XPERIA XZ1.
I followed this tutorial https://www.getdroidtips.com/lineage-os-18-1-sony-xperia-xz1-compact/ in order to install Lineage OS 18.1 using TWRP
So I've downloaded all the software, images, drivers and such... then used adb and fastboot to flash TWRP.
When I finally managed to boot with TWRP my screen looked like this
{
"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"
}
The display appears to be somewhat broken or misconfigured, with a smaller version of the display on the top left corner of the screen and everything else is RGB snow.
Touchscreen is responding on the non broken part of the screen only. It looks like this as soon as the screen turns on, even before Xperia booting sequence.
I couldn't manage to install Lineage properly either. I got stuck in a weird boot loop. Taking up to minutes to boot with the lineage loading animation and a black screen. I was able to interact with the parameter tab but could open any app or do anything else.
Then I decided to restart from scratch and reinstalled a stock ROM with Sony Xperia Flash Tool, following this tutorial https://www.getdroidtips.com/sony-xperia-xz1-stock-firmware/
Now I have a working Android system running on the phone but it didn't fix the screen.
It doesn't detect my SIM card either.
This isn't my main phone so it doesn't really matter to me if SIM doesn't work, but i'd like to fix the screen.
It might have something to do with the fact that I've tried to flash a Lineage ROM made for Sony Xperia XZ1 Compact. Mine is not a compact, but there was no official ROM for my specific model. This was the closest match and I thought this should be OK. I was SO wrong, lol
I couldn't find another thread with the same screen glitch, but I highly doubt it to be unique. I'm probably just using the wrong keywords.
Any hint would be greatly appreciated
Thanks !