Related
Today I got one of the new Asus Trasformer Pad tablets. They just rev'd the line and this one is running Android 4.4.2 and has an Intel Bay Trail Z3745 processor.
This is a very new device: yesterday was the first day this variety of Intel processor was supposed to be available in a tablet, and I had this one on pre-order and it arrived today. Of course, I want to root it.
If anyone knows how I would love it, or pointers to ideas. I rooted my prior Intel Android tablet (an HP Slate 7 1800 "mesquite") with the TwerkMyMoto hack from this thread:
http://forum.xda-developers.com/showthread.php?t=2548742
which has been very helpful. (I find it quite limiting to do development on a non-rooted device, and what I'm working on doesn't run on an emulator). I am very much non-expert at rooting / recovery, and I'm not sure I would make any headway on my own. Depending how much of a limitation lack of root proves to be, if no one has better ideas then I may eventually just start trying things, and if I have any success, certainly I will post back here.
Cheers.
I just got this new tablet and like the performance very much!
I too am interested in rooting it. If anyone has any suggests please post here.
I have tried some generic root methods for x86 tablets, but have not had any luck. The bootloader in locked and when I try to run adb as root, I get an error message "adbd cannot run as root in production builds"
I am a newbie, but if anyone has any suggestions please let me know and I'll give it a try.
Thanks!
bit.perfect said:
I just got this new tablet and like the performance very much!
I too am interested in rooting it. If anyone has any suggests please post here.
I have tried some generic root methods for x86 tablets, but have not had any luck. The bootloader in locked and when I try to run adb as root, I get an error message "adbd cannot run as root in production builds"
I am a newbie, but if anyone has any suggestions please let me know and I'll give it a try.
Thanks!
Click to expand...
Click to collapse
I just picked up one of these today and am also interested in root
Does anyone have any updates?
If anyone has any suggestions please let me know I can test on my device.
It's been two weeks now and I managed to discover some drawbacks. In my case it is closing some applications without any reason. The message displayed says usually that application was suddenly closed or that there was some error etc. I appreciate asus issuing constantly some system updates but they just don't seem to be improving anything so far. Another thing is that I can't connect my HP LJ 1018 printer to USB port. NTFS formatted pendrive also doesn't work... Root access could make this device more useful for me. Anyone... please...
I've got mine 3 days ago and for now I'm satisfied. It would be better if it had an HDMI. I'm waiting for root too. Want to make an swap file to extend RAM memory. I hope someone will make tutorial for us.
Edit: My TF103 died and couldn't come back to life. I'd only had it for 15 days. I returned it and bought a Galaxy Tab 4 instead.
Got one as well
dublinman said:
It's been two weeks now and I managed to discover some drawbacks. In my case it is closing some applications without any reason. The message displayed says usually that application was suddenly closed or that there was some error etc. I appreciate asus issuing constantly some system updates but they just don't seem to be improving anything so far. Another thing is that I can't connect my HP LJ 1018 printer to USB port. NTFS formatted pendrive also doesn't work... Root access could make this device more useful for me. Anyone... please...
Click to expand...
Click to collapse
I picked one of these up before the weekend, and now its become my weekend. Here is what I've managed to figure out:
ASUS Transformer Pad MG10/TF103C
Enable the Developer menu:
Settings -> About -> Software information -> Tap Build number numerous times
Settings -> About -> Software information -> Tap Android version numerous times get a Kitkat animation (Easter egg, nothing helpful)
Using adb reboot bootloader, I have learned this about the bootloader:
DROIDBOOT bootloader
Version 2.0
and everything else you can make out in the picture. Sorry, the size restrictions were getting me.
Update.zip from ASUS
I'm not an Android developer, so forgive me if this question is a facepalmer. Asus has an update.zip for this new model, but its like the guy that updates their website was in a hurry for the weekend so half of the fields aren't filled in. I have determined which update.zip would apply to my particular device, and when I extract everything there is a boot.img, fastboot.img, recovery.img, etc
Can you build a root update package from this or is it not that simple? Currently, there isn't anything out as far as a unlocking package from ASUS or anyone else.
Am I on the right path or am I pissing in the wind?
Nebtastic said:
Can you build a root update package from this or is it not that simple? Currently, there isn't anything out as far as a unlocking package from ASUS or anyone else.
Am I on the right path or am I pissing in the wind?
Click to expand...
Click to collapse
You're on the right track. To get root via a flashable zip, you either need a custom recovery (to flash unsigned zips), or a way to sign the zip to make it look official to the device.
Usually once a custom recovery is available, custom roms follow pretty quickly.
Hello
i wan't any thing do Root for Asus TF103C.
-why there is nothing do Root for the tablet? (Is this for strong security of the tablet?)
Pleeeeaaaassssseee we want Root for this best tablet on Earth:highfive::silly:.
Developer are welcome
I'm also looking forward to have a root!.
I have tried all programs available, none works
Developer are welcome to root Asus TF103
Asus Support
{
"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"
}
Ok, I figured this would be a fruitless journey, but since they released bootloader unlock tools for the last Transformers I thought I would give them a shot.
Asus support says there is no unlocked bootloader. So at this time, there is no support from manufacturer to unlock bootloader or root this device. It looks like to root this device someone is just going to have to hack it.
I have used adb to install busybox and framaroot, but neither were successful. The applications show up in the collection, but when you execute them they fail and close because they cannot attain root access.
I just got this tablet a few days ago, and I love it!! I also long for root/unlockbootloader on this amazing device, I've also tried most rooting methods and without success. But I did discover that they have released the source for its kernel. what is the point of that if they are going to lock the bootloader? :c sorry I am new to this and I dont understand
(cant attach link to kernel yet, sorry!)
upupupupupupupupup
I just picked this a week ago...
cocopwr said:
I just got this tablet a few days ago, and I love it!! I also long for root/unlockbootloader on this amazing device, I've also tried most rooting methods and without success. But I did discover that they have released the source for its kernel. what is the point of that if they are going to lock the bootloader? :c sorry I am new to this and I dont understand
(cant attach link to kernel yet, sorry!)
Click to expand...
Click to collapse
I like this tablet, I use it in my office instead of my issued laptop. The best thing about it is its versatility and quick responsiveness, but it has applications I have no use for as well. If this device can be rooted it would be an added benefit to those of us using it. So, if anyone has the time and the patience I am sure it would be greatly appreciated. Thanks
only if we could obtain temp root :c intel's security seems very tough this time... due to vulernabilities in the past platforms they don't want to unlock the bootloader it seems.
Sent from my K010 using XDA
In case it helps I managed to get this device in fastboot mode and booted in safe mode (did not know that existed).
How to get device into Fastboot mode.
1. Press and hold the Volume + button and power button (while device is on).
2. When screen turns black release the power button, but remain holding the Volume + button.
Device should load the bootloader.
How to boot device into Safe Mode.
1. Press and hold the Volume - button and power button (while device is on).
2. When screen turns black release the power button, but remain holding the Volume - button.
Device should boot into safe mode.
I too am still looking for root method.
bit.perfect said:
In case it helps I managed to get this device in fastboot mode and booted in safe mode (did not know that existed).
How to get device into Fastboot mode.
1. Press and hold the Volume + button and power button (while device is on).
2. When screen turns black release the power button, but remain holding the Volume + button.
Device should load the bootloader.
How to boot device into Safe Mode.
1. Press and hold the Volume - button and power button (while device is on).
2. When screen turns black release the power button, but remain holding the Volume - button.
Device should boot into safe mode.
I too am still looking for root method.
Click to expand...
Click to collapse
This app works for me : asuszenfoneblog app ->rootzenfone-144r
I found the safe mode and the recovery well enough, and I am extremely pleased with this device having traded in my fly tf300t to get it(keyboard nightmare!). It is quick, attractive, and hard to stump.. except for that achilles heel.. For some reason, this guy doesnt enjoi transforming so much. Also, ive caught him in bootloop and having to reboot from recovery. It is an intermittent issue and there seems to some kind of formula to doing all of this smoothly EVERY time. I am interested to hear of issues anybody else is having and if any of you are balding because of the keyboard issue with the previous transformer.. .. and asking for a referal to a good therapist if there are similar issues with this guy..
Sent from my K010 using XDA Free mobile app
Hi, together.
I have a snopow m8 ( it's a device with mtk6589 ). I've tried to port Star N9500's rom ( miui v5 4.5.9 ). It's all ok, unless a little problem. In this device there are three buttons: SOS, PTT and Torch. Now, the device not detected these buttons. I replaced the usr folder but nothing. Thanks a lot. I entrust to you.
PS: sorry for my english.
Hi
What recovery tool did you use to backup your stock ROM and install new one? CWM? Can you please upload file?
What tutorial have you followed to adapt MIUI?
I want to experiment with this phone too. I have 20140405 ROM and it has TONS of issues - from broken OTA updated, crappy GPS EPO servers, not working YouTube, NFC doing kernel stack errors to frequent self restarts. I saw that 20140624 is available on www*needrom*com/mobile/snopow-m8 but MIUI also looks interesting,
Hi
bbkr said:
Hi
What recovery tool did you use to backup your stock ROM and install new one? CWM? Can you please upload file?
What tutorial have you followed to adapt MIUI?
I want to experiment with this phone too. I have 20140405 ROM and it has TONS of issues - from broken OTA updated, crappy GPS EPO servers, not working YouTube, NFC doing kernel stack errors to frequent self restarts. I saw that 20140624 is available on www*needrom*com/mobile/snopow-m8 but MIUI also looks interesting,
Click to expand...
Click to collapse
I use to backup my stock rom with mtk-tool and install cwm 5.x.x . I install the miui 4.5.9. I' m porting this n9500's rom to snopow m8. It's all ok, but I miss three function button. Tomorrow , maybe, they send me the snopow's stock rom. I uploaded the file soon as soon.
I use this guide: en*miui*com/thread-13383-1-1*html
SoloFirenze said:
I use to backup my stock rom with mtk-tool and install cwm 5.x.x .
Click to expand...
Click to collapse
I have to try MTK Droid tools (windows only... yuck!). I've tried to install CWM using ADB, but this phone cannot reboot into bootloader for some reasons.
SoloFirenze said:
Tomorrow , maybe, they send me the snopow's stock rom.
Click to expand...
Click to collapse
I've linked stock rom in my previous post.
SoloFirenze said:
but I miss three function button.
Click to expand...
Click to collapse
I think you should first debug if: those buttons do not send events OR events are not associated with any action/application. In ADB shell run...
Code:
getevent -lt /dev/input/event0
...and press flashlight button. On stock ROM system reports received event:
Code:
[1405204621.434233] EV_KEY 00fc DOWN
[1405204621.434242] EV_SYN SYN_REPORT 00000000
[1405204621.583587] EV_KEY 00fc UP
[1405204621.583590] EV_SYN SYN_REPORT 00000000
Now if you have the same result in MIUI then pressed key is recognised but system doesn't know what to do with it. In that case simply use tool such as http://forum.xda-developers.com/showthread.php?t=850464 to associate hardware key event with app.
SoloFirenze said:
Hi, together.
I have a snopow m8 ( it's a device with mtk6589 ). I've tried to port Star N9500's rom ( miui v5 4.5.9 ). It's all ok, unless a little problem. In this device there are three buttons: SOS, PTT and Torch. Now, the device not detected these buttons. I replaced the usr folder but nothing. Thanks a lot. I entrust to you.
PS: sorry for my english.
Click to expand...
Click to collapse
Hi, i've got a snopow M8 too. How did you port Star N9500's rom on the snopow? Did solve the google play service problem?
Thanks for help.
ludobillou said:
Did solve the google play service problem?
Click to expand...
Click to collapse
I gave up on YouTube app - no one knows how to get it working...
I removed whole app and I'm watching YT through Opera - works perfectly.
The phone is totally not worth the price. The amount of software bugs - broken OTA, broken NFC, Google apps problems, frequent restarts, NVRAM issues, EPO fails, and so on - is incredible.
BTW: Which ROM version do you have?
I've tried to port the rom MIUI for Star N9500 and my Snopow is totally brick now... When the touch interface installation of MIUI appeared, it ask me too choose my screen drivers. I select all because i didn't knew anyone choose. After a successful installation, i wiped the cache and reboot. Now i don't see anything but many horizontal stripes... And there's no more recovery. help :crying:
I think the solution is to download original rom from SP flash tool but the phone is not recognize by my computer, even with the USB VCOM drivers.
What do you think?
ludobillou said:
I've tried to port the rom MIUI for Star N9500 and my Snopow is totally brick now...
Click to expand...
Click to collapse
Try entering META mode - http://forum.xda-developers.com/showthread.php?t=1943442
Your device should be then visible for USB VCOM.
I'm not expert in unbricking so if you have any questions please ask there. But also please come back here later and share your experience.
bbkr said:
Try entering META mode - http://forum.xda-developers.com/showthread.php?t=1943442
Your device should be then visible for USB VCOM.
I'm not expert in unbricking so if you have any questions please ask there. But also please come back here later and share your experience.
Click to expand...
Click to collapse
Thanks for answer. I try the META mode, it work on my HERO h2000+ but not on my Snopow (~50% battery, volume up/down pressed when connect...etc). Does it come from the USB cable or the phone?
Thanks for help.
ludobillou said:
Thanks for answer. I try the META mode, it work on my HERO h2000+ but not on my Snopow.
Click to expand...
Click to collapse
I think this is called "Factory mode" on Snopow.
Turn off the phone. Unplug USB cable.
Press and hold volume down.
Press and hold power.
Do NOT release both buttons until Factory Mode appears. Its bunch of chinese letters, should look 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"
}
Connect USB cable. Check if VCOM driver detects device.
Yes but...
bbkr said:
I think this is called "Factory mode" on Snopow.
Turn off the phone. Unplug USB cable.
Press and hold volume down.
Press and hold power.
Do NOT release both buttons until Factory Mode appears. Its bunch of chinese letters, should look like this:
Connect USB cable. Check if VCOM driver detects device.
Click to expand...
Click to collapse
The Factory mode worked before i brick it but not now. I will try with OTG cable and i'll tell you what will happen.
Sorry for the delay. I've installed the miui 4.7.5 and all work, unless the three hard button. I'm going crazy!! Can someone help me? I don't know how to do this!! Help me!! please! I will upload the rom.
SoloFirenze said:
Sorry for the delay. I've installed the miui 4.7.5 and all work, unless the three hard button. I'm going crazy!! Can someone help me? I don't know how to do this!! Help me!! please! I will upload the rom.
Click to expand...
Click to collapse
Check my post above. I've written you how to debug it.
bbkr said:
Check my post above. I've written you how to debug it.
Click to expand...
Click to collapse
Sorry I didn't see this. How to do this?
SoloFirenze said:
Sorry I didn't see this. How to do this?
Click to expand...
Click to collapse
Well, reading my previous post about tracking events using ADB and following those instructions seems reasonable
You have to diagnose issue first to figure out how to fix it.
bbkr said:
Well, reading my previous post about tracking events using ADB and following those instructions seems reasonable
You have to diagnose issue first to figure out how to fix it.
Click to expand...
Click to collapse
this is "my" result. The hard keys not working.
www*mediafire*com/download/dxn0db63b2mcnud/miui_4*7*5*zip
SoloFirenze said:
this is "my" result. The hard keys not working.
www*mediafire*com/download/dxn0db63b2mcnud/miui_4*7*5*zip
Click to expand...
Click to collapse
And what is the result of events debugging?
my result is this:
adb shell -- getvent -lt /dev/input/event0
/system/bin/sh: /system/bin/sh: --: unknown option
SoloFirenze said:
my result is this:
adb shell -- getvent -lt /dev/input/event0
/system/bin/sh: /system/bin/sh: --: unknown option
Click to expand...
Click to collapse
Run "adb shell" first, wait for prompt.
And then "getvent -lt /dev/input/event0".
And press some phone buttons.
bbkr said:
Run "adb shell" first, wait for prompt.
And then "getvent -lt /dev/input/event0".
And press some phone buttons.
Click to expand...
Click to collapse
yes I've the same result. Now? Witch app I use for to do this?
Hello everyone,
I will share my experience with you, and I hope for a solution!
A few days ago I rooted my Lenovo tab 2 A10-30 successfully using Kingroot. Then, I tried to change Kinguser with SuperSU, which I also successfully did. However, I noticed that although the main root app was SuperSU, Kingroot was still on my phone, so I deleted it using a bloatware removal app and restarted the tablet. Now it won't turn on. It gets stuck at the Lenovo loading screen, and that's about it. When I press the power button + volume down button, it gets me to a Chinese menu that is not the recovery mode (there is no MMC, just options about voloume, colors, mic test etc). If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
I tried flashing the stock ROM using the Smart Phone Flash Tool, but the PC does not recognize fully the tablet (it just prompts me to install the Lenovo USB drivers, and I cannot access the tablet's internal storage). Moreover, the Lenovo windows applications do not recognize the tablet when I connect it to the PC.
I really do hope that there is a way I can fix it.. Thank you all in advance.
Hi,
I did almost exactly the same... Kingroot, tried to remove bloatware with another app, and ended up with a bricked tablet I can still access the bootloader, but flashing the tablet from there is to no avail.
I am still looking for the original ROM, which seems nowhere to be found. Did you, by any chance, make a backup first?
Another one here But I'am able to go into recovery and into adb sideload, from there I can view internal memory(/system). And it looks like system is trying to load supersu-daemon which was removed and it can't get past that. I tried to recover paths (to original ones), but it still wont go past loading screen. (it is just restarting the app_process32).
Now if we only could get the hold on original factory firmware... from there one we can sideload it via fastboot.
And for the drivers you need andorid usb drivers https://developer.android.com/studio/run/win-usb.html#top
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
So, I have spent about 5 hours attempting to find a way to dump the firmware without first rooting the device, so that I could share it with you guys (and have a backup for myself in case I attempt to root it myself.) Unfortunately it seems like it needs to be rooted before I can create a nandroid backup through adb. Unfortunately the tablet is not based on mtk, and I cannot find any qualcomm utils that can dump the firmware.
The one Qualcomm util I found (QFIL) seems like it is only for flashing, and for backing up some individual data for the tablet (I assume it may contain such as license keys for the commercial features in the recent phones such as Sony Xperia Z3). I also looked into fastboot, and that too can only flash a new firmware.
So, unless the tablet gets rooted I don't see any way to make a proper backup.
I am unable to post links in messages, so you need to do some manual editing.
dz0ny said:
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
Click to expand...
Click to collapse
This however seems like very valuable information, unfortunately the only places I can find that has this available for download is charging money for access to the file.
50$ at dlgsm,com www DOT dlgsm DOT com/register.php?file=TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip&dir=%2FFLASH-FILES%2FLENOVO%2FT_Series%2FTB2-X30F
or from 10$ at pars-hamrah,com: www DOT pars-hamrah DOT com/%D8%A7%D8%AE%D8%A8%D8%A7%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D8%A7%D8%AE%D8%AA%D8%B5%D8%A7%D8%B5%DB%8C-%D9%BE%D8%A7%D8%B1%D8%B3-%D9%87%D9%85%D8%B1%D8%A7%D9%87/38027-%D8%B1%D8%A7%D9%85-%D8%A7%D9%88%D8%B1%D8%AC%DB%8C%D9%86%D8%A7%D9%84-%D9%84%D9%86%D9%88%D9%88-lenovo-tb2-x30f-%D9%86%D8%B3%D8%AE%D9%87-s000015-%D8%A7%D9%86%D8%AF%D8%B1%D9%88%DB%8C%D8%AF-5-1-1-%D8%AF%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D9%82%D8%B1%D8%A7%D8%B1-%DA%AF%D8%B1%D9%81%D8%AA.html"]Here[/URL]
It might also be available www DOT fars-gsm DOT com/75531-tb2-x30f_usr_s000015_1601151950_q8009_row_qpst-zip.html, at least they list the changelog for the firmware.
Since I have no use for a firmware right now, I will not be buying access to one (unless I at some point manage to brick mine as well). But if anyone decides to do so, please share it so others can enjoy it as well. I also suspect that if the file was available, it would increase the probability of someone attempting to make a custom rom at some point as well, it is a very cheap tablet when on sale, so it should have good potential for a community.
PS: I also stumbled over something called vRoot, that might be an alternative to Kingroot, although I have no idea whether it is as good at rooting and not installing unwanted extra apps. I guess someone who has used it on a tablet/phone that has a backup available might be able to shed some light on that.
---------- Post added at 08:08 PM ---------- Previous post was at 08:02 PM ----------
omrtpsycho said:
If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
Click to expand...
Click to collapse
This is the QFIL (Qualcomm Flash something system) mode, however I do now know whether that helps anything at all. Since it seems to me it probably wont accept the TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip file mentioned in the thread. It seems to expect some xml file, maybe the zip file contains that?
Hi guys i have been strugling with this unit The last 3 days. I have eksakt same problem. I found these files: lenovo-forums.ru/files/category/106-прошивки-lenovo-tab-2-a10-30/
I extracted Them but dont know how to flash Them ?? Hope u guys Can help (sorry for bad english)
To Download files from Lenovo-forums.ru i logged in with my Google account
[PUT ROM TEMPORARILY HERE: https://www.wetransfer.com/download...024ee2974a44f8aa50e3dcd120160615184237/a84735 ]
Wow, suddenly action! With the help of Dead2 and Andersbp I have made some progress. Here are my steps:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
The smaller one is simply an update, which you could install easily:
1) boot into Recovery Mode
2) select "Apply Update from ADB"
3) run: adb sideload TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip
Which works... UNLESS YOU ROOTED THE DEVICE. Then it fails, and does not want to update. Thanks Lenovo
So, the larger one is a different type of ROM. This one will not load with adb sideload (gives footprint and signature error). But it DOES contain all the files to flash with QFIL (Qualcomm Flash something system).
Here I'm stuck. I followed this guide:
http://guidebelajar.blogspot.nl/2016/03/guide-how-to-flash-firmware-lenovo-vibe-p1.html
and tried to install these packages:
1) You must download and install USB Driver for Lenovo on your windows computer or PC.
2) QPST-2.7.422-qfil-qcom-Upgrade-Tool-20140422
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Furthermore, the site suggests to install something on the device itself:
5) Create a folder with the name sdfuse in the root of the SD-card phone
6) Put the qsb-firmware (file with the extension .qsb) in the folder sdfuse.
Here I have 2 problems: First, my device does not boot, so I cannot create/copy files. Seconly: I cannot find qsb-firmware.qsb anywhere...
@ Dead2: How did you go through these steps?
Zwartoog said:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
Click to expand...
Click to collapse
Great, thanks for sharing the firmware, I hope you and everyone else with a softbricked tablet can get it fixed now
I am sure some of those would be willing to donate a couple of bucks to you if they get theirs working again.
Zwartoog said:
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Click to expand...
Click to collapse
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
I got the driver package from here: www DOT teamandroiders DOT com/lenovo-usb-drivers-download/
Zwartoog said:
@ Dead2: How did you go through these steps?
Click to expand...
Click to collapse
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
I will assist in any way I can, but I will not attempt flashing my own tablet until I actually need to
Dead2 said:
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
Click to expand...
Click to collapse
We'll get this working
Dead2 said:
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
Click to expand...
Click to collapse
I tried that one too, but to no avail When I try to execute the executable, it ask for administrator permission, and after that vanishes...
I am running Windows 8, 64 bit. You?
Other question: when is your tablet recognised by Windows? Also in Recovery Mode?
Thanks!
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Andersbp said:
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Click to expand...
Click to collapse
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Zwartoog said:
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Click to expand...
Click to collapse
Sure Will try tomorrow
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
{
"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"
}
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Click to expand...
Click to collapse
Super! Will try this tonight. Just in case: which Windows version are you using?
Zwartoog said:
Super! Will try this tonight. Just in case: which Windows version are you using?
Click to expand...
Click to collapse
I use windows 10
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
Click to expand...
Click to collapse
Great work! I am glad I was able to help you guys get this fixed
Andersbp said:
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Click to expand...
Click to collapse
Yep, its at the bottom of my first post also, found that out by accident while trying to get into the normal recovery.
Now, hopefully someone will want to port TWRP and CM13 or Paranoid to this tablet
Doh i did not see that Dead2
Thanks everybody together we defeated the problem !
SUPER! Succes here as well! The trick was indeed to hold both vol UP and DOWN
Now: brand-new unrooted device
Thanks
Btw: I noticed that the rom from Andersbp is a TB2-X30L rather than the TB2-X30F. I used my F file (paid for it, dammit ), and that one also works well.
I am currently checking if I can modify the stock ROM to enable root / mult-user. Any hints?
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Andersbp said:
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Click to expand...
Click to collapse
Noo, no Kingroot. That's where all the disasters began. It is full of bloatware. Trying to uninstall Kingroot lead to bricking the device
Personally I am only interested in re-enabling the multi-user feature from lollipop. WHICH IS FOR SOME REASON DISABLED BY LENOVO Even when rooted and modifying the system/build.prop did not re-enable it.
I'm giving up now. At least I have a workable device. Restored pride. And more important: 3 happy kids
I think the TB2-X30L is the LTE version of the tablet, while the TB2-X30F is the wifi-only version. If correct, then there should be no problem
when using the LTE on a non-LTE model, but the other way around could potentially cause LTE to not work. The LTE firmware might have some
extra apps and settings enabled to cater to this ability, but it might also be completely identical. Btw, what does the model information say
after being flashed with the L firmware? In any case it is useful to know that they are cross-compatible, since sometimes there can be differences
in chipsets or screens that can cause minor or major problems.
As I mentioned earlier, another root alternative to kingroot seems to be vRoot, but I have not tried it myself. But now that it is possible to
recover a bricked tablet, it is also less risky to test such things.
BTW: Please remember to use the "Thanks!" button on posts you find helpful, I have tried to do so myself on the posts that I find helpful
{
"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"
}
Google Project Tango Tablet
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Unofficial Lineage OS 16.0 thread for the Google Project Tango Tablet, codename yellowstone.
How to Install:
Please follow the instructions on our Unofficial ODS Wiki page here.
If you don't follow these instructions, please don't expect support here. You NEED to flash the PSCI firmware via the process described in the wiki above, or you run a significant chance of bricking your device.
We also don't support 3rd party add-ons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Issues:
Camera's and flashlight don't and likely won't ever work due to incompatibilities in proprietary binaries.
Due to the fact the cameras are broken, the ATAP/Tango apps will crash upon opening.
USB Tethering is broken for some people.
SELinux is permissive (if you're a developer, you can help on this one!)
Downloads:
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps/Pixel goodies.
Add-ons (WeatherProviders/AddonSU packages
How to build yourself:
Follow the ODS Wiki Guide here here, except just after running
Code:
. build/envsetup.sh
run
Code:
repopick -f 279494
then proceed as described.
Returning to Stock:
Follow the ODS Wiki Guide here here starting at step two, except instead of downloading/using `yellowstone_pie_psci.zip`, use yellowstone_kitkat_stock.zip
XDA:DevDB Information
[UNOFFICIAL] LineageOS 16.0 for the Project Tango Tablet (ATAP), ROM for the Nvidia Shield Tablet
Contributors
npjohnson, ryanbg, steel01
Source Code: https://github.com/LineageOS/android_device_google_yellowstone
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Stock KitKat
Version Information
Status: Stable
Created 2020-10-16
Last Updated 2020-10-16
Thanks!
Could be me, but it looks like the links to the add-ons are 404. These should work, right?
https://download.lineageos.org/extras
I wanted to ask, what exactly needed changing to the bootloader stuff that allows newer custom ROMs to boot? I'm legitimately curious and I would like to know if those modifications basically open it up so that it all lands on the OS side for getting stuff like cameras working in the future if that's even possible.
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
xaxxelous said:
Thanks!
Could be me, but it looks like the links to the add-ons are 404. These should work, right?
https://download.lineageos.org/extras
Click to expand...
Click to collapse
The link provided is working for me but I don't see why you couldn't use those extras. Just make sure to grab the ones for LineageOS 16.0. But @npjohnson please correct me if I'm wrong.
EDIT: The main link works to the list of extras downloads but none of the extra downloads on the page work.
there is an issue with the script.
[[email protected] yellowstone_pie_psci]$ ./flash.sh
Nvflash 4.13.0000 started
unknown command: --g
[[email protected] yellowstone_pie_psci]$
there appears to be a typo. The last part of the command seems to be --go Got it working here
---------- Post added 17th October 2020 at 12:15 AM ---------- Previous post was 16th October 2020 at 11:48 PM ----------
Unless I'm wrong there's also a typo on the wiki page you made.
Lines like:
With the device powered off, hold Volume Down + <kbd+ Power until a menu is displayed. Use Volume Down to highlight “Recovery mode”, then press Power to select
Should probably be like:
With the device powered off, hold Volume Down + Volume Up + Power until a menu is displayed. Use Volume Down to highlight “Recovery mode”, then press Power to select
Well I did some testing and for the most part the tablet works better than it's ever had. Before I had an issue with it powering off with a "dead battery" but flashing a full charged battery icon after powering off. That issue has gone away now.
Thank you and anyone who has helped bring this ROM to life, it's really amazing to see newer software working so well on these old tablets. I honestly didn't think it would ever happen.
xaxxelous said:
Thanks!
Could be me, but it looks like the links to the add-ons are 404. These should work, right?
https://download.lineageos.org/extras
Click to expand...
Click to collapse
Fixed.
ShapeShifter499 said:
I wanted to ask, what exactly needed changing to the bootloader stuff that allows newer custom ROMs to boot? I'm legitimately curious and I would like to know if those modifications basically open it up so that it all lands on the OS side for getting stuff like cameras working in the future if that's even possible.
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
The link provided is working for me but I don't see why you couldn't use those extras. Just make sure to grab the ones for LineageOS 16.0. But @npjohnson please correct me if I'm wrong.
EDIT: The main link works to the list of extras downloads but none of the extra downloads on the page work.
Click to expand...
Click to collapse
Fixed.
And to answer the question - It's a hybrid of tn8's (Shield Tablet) nvboot and a heavily disassembled/reassembled applications bootloader to support the newer TLK/Secure World and PSCI kernel from tn8, allowing us to use kernel 3.10 from nv-tegra as opposed to 3.4 from Google. Much cleaner, must snappier, plus it lets us use Shield Tablet proprietary files for graphics, etc. which has an official Nougat release, which is way easier to work with than KitKat blobs from stock. We split out and use as many tn8 blobs as we can, and yellowstone stock where we need to.
It was designed almost entirely by @ryanbg -he's a legend, and one of the big reasons this device got anything more than cm-14.1 - I did most of the Android-side bringup (which was rough), but his work on kernel and firmware enabled it
ShapeShifter499 said:
there is an issue with the script.
[[email protected] yellowstone_pie_psci]$ ./flash.sh
Nvflash 4.13.0000 started
unknown command: --g
[[email protected] yellowstone_pie_psci]$
there appears to be a typo. The last part of the command seems to be --go Got it working here
---------- Post added 17th October 2020 at 12:15 AM ---------- Previous post was 16th October 2020 at 11:48 PM ----------
Fixed - don't know how I missed that, sorry.
Unless I'm wrong there's also a typo on the wiki page you made.
Lines like:
With the device powered off, hold Volume Down + <kbd+ Power until a menu is displayed. Use Volume Down to highlight “Recovery mode”, then press Power to select
Should probably be like:
With the device powered off, hold Volume Down + Volume Up + Power until a menu is displayed. Use Volume Down to highlight “Recovery mode”, then press Power to select
Click to expand...
Click to collapse
Fixed.
ShapeShifter499 said:
Well I did some testing and for the most part the tablet works better than it's ever had. Before I had an issue with it powering off with a "dead battery" but flashing a full charged battery icon after powering off. That issue has gone away now.
Thank you and anyone who has helped bring this ROM to life, it's really amazing to see newer software working so well on these old tablets. I honestly didn't think it would ever happen.
Click to expand...
Click to collapse
Yeah, that was an old bootloader bug. Plus we swapped to newer battery graphics to match Lineage branding
Also, not responding to anyone in specific, just noting, I also added instructions to build at home to the OP!
npjohnson said:
And to answer the question - It's a hybrid of tn8's (Shield Tablet) nvboot and a heavily disassembled/reassembled applications bootloader to support the newer TLK/Secure World and PSCI kernel from tn8, allowing us to use kernel 3.10 from nv-tegra as opposed to 3.4 from Google. Much cleaner, must snappier, plus it lets us use Shield Tablet proprietary files for graphics, etc. which has an official Nougat release, which is way easier to work with than KitKat blobs from stock. We split out and use as many tn8 blobs as we can, and yellowstone stock where we need to.
It was designed almost entirely by @ryanbg -he's a legend, and one of the big reasons this device got anything more than cm-14.1 - I did most of the Android-side bringup (which was rough), but his work on kernel and firmware enabled it
Click to expand...
Click to collapse
I was looking into it seeing if maybe I could help. I had been looking at the tos.img alone thinking that was it. But wow man I probably would have never gotten to the bootloader like that. Thank you and @ryanbg for putting all the work in.
So I have a new issue. My IMEI is blank and my sim card doesn't work. I had this sim working before on stock firmware, service through t-mobile
---------- Post added at 02:46 AM ---------- Previous post was at 02:25 AM ----------
I redownload the zip and the script inside still has an issue for Linux
[[email protected] yellowstone_pie_psci]$ ./flash.sh
Nvflash 4.13.0000 started
unknown command: --g
[[email protected] yellowstone_pie_psci]$
ShapeShifter499 said:
So I have a new issue. My IMEI is blank and my sim card doesn't work. I had this sim working before on stock firmware, service through t-mobile
---------- Post added at 02:46 AM ---------- Previous post was at 02:25 AM ----------
I redownload the zip and the script inside still has an issue for Linux
[[email protected] yellowstone_pie_psci]$ ./flash.sh
Nvflash 4.13.0000 started
unknown command: --g
[[email protected] yellowstone_pie_psci]$
Click to expand...
Click to collapse
This is weird... I use t-mobile on yellowstone - and it works fine. Can you get me logs?
npjohnson said:
This is weird... I use t-mobile on yellowstone - and it works fine. Can you get me logs?
Click to expand...
Click to collapse
I was able to use the package you uploaded to revert to kitkat stock and confirmed the t-mobile sim works with this tablet. It just doesn't work on the latest build you have.
This is from a fresh reinstall. Installed are the LineageOS Recovery (lineage-16.0-20201009-recovery-yellowstone.img), the LineageOS 16.0 main build (lineage-16.0-20201009-UNOFFICIAL-yellowstone.zip), and the LineageOS SuperSU add on (addonsu-16.0-arm-signed.zip). I grabbed a logcat from first boot, I tried to use the option to use the cellular network which failed and I skipped all google sign in so I could try toggling cellular network in the settings.
Logcat: https://gist.github.com/ShapeShifter499/51f14342a14416a44ed1fdec27c071cc
Here is one more logcat, taken after first boot. I toggled the "Airplane mode" in settings to no avail, SIM was still not detected and no network connection was made over cellular.
Logcat: https://gist.github.com/ShapeShifter499/856e638f29e33f1aac156ca19dc2c790
ShapeShifter499 said:
I was able to use the package you uploaded to revert to kitkat stock and confirmed the t-mobile sim works with this tablet. It just doesn't work on the latest build you have.
This is from a fresh reinstall. Installed are the LineageOS Recovery (lineage-16.0-20201009-recovery-yellowstone.img), the LineageOS 16.0 main build (lineage-16.0-20201009-UNOFFICIAL-yellowstone.zip), and the LineageOS SuperSU add on (addonsu-16.0-arm-signed.zip). I grabbed a logcat from first boot, I tried to use the option to use the cellular network which failed and I skipped all google sign in so I could try toggling cellular network in the settings.
Logcat: https://gist.github.com/ShapeShifter499/51f14342a14416a44ed1fdec27c071cc
Here is one more logcat, taken after first boot. I toggled the "Airplane mode" in settings to no avail, SIM was still not detected and no network connection was made over cellular.
Logcat: https://gist.github.com/ShapeShifter499/856e638f29e33f1aac156ca19dc2c790
Click to expand...
Click to collapse
Dmesg as well pls
npjohnson said:
Dmesg as well pls
Click to expand...
Click to collapse
Here is a dmesg
https://gist.github.com/ShapeShifter499/1912a442e3887df9458fa7d6a73828ee
I tried to install the recovery listed in the downloads page. It failed and said-- FAILED (remote: (InvalidSize)) I copy and pasted the name of the file, so that should have been ok. Not sure what I did wrong, and ideas would be helpful.
thew-tab said:
I tried to install the recovery listed in the downloads page. It failed and said-- FAILED (remote: (InvalidSize)) I copy and pasted the name of the file, so that should have been ok. Not sure what I did wrong, and ideas would be helpful.
Click to expand...
Click to collapse
Sounds like you didn't repartition yet...
I didn't seek anything in the wiki about how to partition, unless I completely missed, thanks for the quick response.
npjohnson said:
Sounds like you didn't repartition yet...
Click to expand...
Click to collapse
thew-tab said:
I didn't seek anything in the wiki about how to partition, unless I completely missed, thanks for the quick response.
Click to expand...
Click to collapse
It's literally the first several pages of the wiki.
The PSCI firmware package.
@npjohnson If I wanted to fork some of the repos to do my own edits, tests, and maybe port a different ROM to get working. Which of the repos contain the latest accepted edits? The LineageOS github ones or the ones on your own github? I figure at least I would get the proprietary blobs from your github or the last ROM.
Also got any ideas about the SIM card issue? I suspect this error I see in the dmesg is it but I don't know for sure "init: Could not find service hosting interface [email protected]::IRadio/slot1" which led me to this https://stackoverflow.com/questions...nterface-android-hardware-radio-config1-0irad
ShapeShifter499 said:
@npjohnson If I wanted to fork some of the repos to do my own edits, tests, and maybe port a different ROM to get working. Which of the repos contain the latest accepted edits? The LineageOS github ones or the ones on your own github? I figure at least I would get the proprietary blobs from your github or the last ROM.
Also got any ideas about the SIM card issue? I suspect this error I see in the dmesg is it but I don't know for sure "init: Could not find service hosting interface [email protected]::IRadio/slot1" which led me to this https://stackoverflow.com/questions...nterface-android-hardware-radio-config1-0irad
Click to expand...
Click to collapse
SIM is now fixed. And that error by proxy. Yes, just use lineage.dependencies to trace dependencies, all on lineageos org, and vendor is on themuppets as always.
17.1 doesn't boot at all, but that's a tegra t124 wide chipset issue - graphics crashes and panics the device. 16.0 is near to perfect.
ShapeShifter499 said:
Here is a dmesg
https://gist.github.com/ShapeShifter499/1912a442e3887df9458fa7d6a73828ee
Click to expand...
Click to collapse
Okay, this was an issue on my end - I fixed it, newest build via OTA fixes it.
npjohnson said:
Okay, this was an issue on my end - I fixed it, newest build via OTA fixes it.
Click to expand...
Click to collapse
Perfect, I can now connect to LTE, though I only seem to ever get slow H or H+ connections over T-Mobile. Same as on Stock. Probably the old cellular chipset to blame.
I do see two other issues but I don't know how fixable they are.
1) Charging over USB micro-B barely works when booted in. It doesn't like to draw much current. As example, one of my power banks shuts off when this tablet is plugged in to it. Another being that it seems to discharge when plugged into a USB wall wart rated at 5V 2A. I know with some devices it was possible to change the kernel to force a higher charge rate or temporarily toggle it. Does anyone happen to know if that's possible here?
2) 1080p videos work amazing when they are under 60FPS, 60FPS videos will studer but not slow down the system. Videos 1080p 30FPS play perfectly. 60FPS videos also play perfectly if they are under 1080p of quality.
I don't expect it to play anything higher than 1080p in quality but I wonder why the 60FPS is the limit for 1080p when 30FPS seems smooth.
ShapeShifter499 said:
Perfect, I can now connect to LTE, though I only seem to ever get slow H or H+ connections over T-Mobile. Same as on Stock. Probably the old cellular chipset to blame.
I do see two other issues but I don't know how fixable they are.
1) Charging over USB micro-B barely works when booted in. It doesn't like to draw much current. As example, one of my power banks shuts off when this tablet is plugged in to it. Another being that it seems to discharge when plugged into a USB wall wart rated at 5V 2A. I know with some devices it was possible to change the kernel to force a higher charge rate or temporarily toggle it. Does anyone happen to know if that's possible here?
2) 1080p videos work amazing when they are under 60FPS, 60FPS videos will studer but not slow down the system. Videos 1080p 30FPS play perfectly. 60FPS videos also play perfectly if they are under 1080p of quality.
I don't expect it to play anything higher than 1080p in quality but I wonder why the 60FPS is the limit for 1080p when 30FPS seems smooth.
Click to expand...
Click to collapse
It's not older chipset -- it's missing bands :/ - unfixable
1. Charging can't be fixed. The regulators are MESSED UP, and it is charging the best it possibly can. The dock quick-charges it safely. - Working as intended
2. Totally expected, older hardware, and the app may be using software rendering instead of hardware - the top result for "1080p 60fps" on youtube plays fine.
Hi Team,
Long story short - I have a problem with adb connection to Android device. And details below.
I've got a Goclever Zoom.me - Android 4.2.2 based photo frame. Really crappy device by the way... but, I really need to install some apk to have a possibility of remote connection to this device (FTP or SMB, or at least just create some network-shared directory). It would be also perfect to have any launcher with android menu and so on...
The issue is that it's impossible to connect to this device via adb. I remember that with old firmware it was actually possible, but long time ago (2015) I upgraded it to newer software, and official instruction to click 8 times a serial number in a device's software to enable USB debugging doesn't work anymore... I thought it had enabled debugging permanently but it seems to be not true, as adb nor fastboot don't see the device. PC recognizes it as a camera allowing to transfer files only.
Device doesn't have any hardware buttons except power and hard reset buttons. I was looking for any possibility to solder volume buttons, but didn't find a spot for them (mainboard is marked as: e351308 topwise-014).
I can connect OTG keyboard and mice instead, which may be helpful... but escaping nor ALT+ESC in the best case moves me to black screen with mouse cursor only...
Can you advice anything to connect to device via adb? What else can I try?
Modify the update perhaps? Seems to work.
GoClever Zoom.me and GApps
I need some help. I own a digital photo frame GoClever Zoom.me which is based on Android 4.2.2. It is rooted and USB debugging is on. I managed to install standard launcher but unfortunately there is no GApps installed on this device. I'm able...
forum.xda-developers.com
Still available
http://downloadfiles.goclever.com/Tablet/Zoom_me/ZOOM.ME_WiFi_Zmiana_Oprogramowania.pdf
80 page manual for a photo frame? LOL!
http://zoom.me/files/manual_en.pdf
Well, some say repetitio est mater studiorum, so they have put it there twice...
LOL! 40 page manual for a photo frame...
CXZa said:
Modify the update perhaps? Seems to work.
Click to expand...
Click to collapse
What do you mean by modifying the update? To modify /system/build.prop ?
I saw that thread, but the issue is that I can't update device again... PhoenixSuit nor adb can see it connected - seems like USB debugging is not enabled anymore and I can't enable it anyhow.
CXZa said:
80 page manual for a photo frame? LOL!
(...)
LOL! 40 page manual for a photo frame...
Click to expand...
Click to collapse
That frame was released with a huge marketing action...but it became a failure as it's a terrible design in total - from housing to software...
matisys said:
Hi Team,
Long story short - I have a problem with adb connection to Android device. And details below.
Can you advice anything to connect to device via adb? What else can I try?
Click to expand...
Click to collapse
That's really weird, because ADB since ever is integral part of every Android distribution. May be in the ROM your device is running on either ADB in fact isn't implemented or USB.debugging isn't allowed or ADB isn't bound to Android's USB-service.
matisys said:
What do you mean by modifying the update? To modify /system/build.prop ?
Click to expand...
Click to collapse
Meant flashing. So, do you have the MTK or Allwinner?
With one button it might be difficult to enter the update mode, but if opened you could possibly connect some pins to make boot to fail thus making it to boot such mode... IDK.
Other possibility is to make your wifi to connect to your own server instead of http://ota.zoom.me/ and let it "update" itself.
Their update zips are signed using test keys so you can make your own. (If recovery keys aren't changed when updated.) Or if you can enter the recovery mode then install it from sdcard.
I have multiple tools, but none can see the device without debugging on.
It's actually easy to open, but I didn't find a proper spot to enforce recovery mode...
CXZa said:
Other possibility is to make your wifi to connect to your own server instead of http://ota.zoom.me/ and let it "update" itself.
Their update zips are signed using test keys so you can make your own
Click to expand...
Click to collapse
How do you know that?
Running an own server is actually an easy part for me, but I'm not sure how to prepare a proper package...
There is actually an update package available to download:
http://downloadfiles.goclever.com/Tablet/Zoom_me/ZM7WIFI_20150717.img
But I couldn't modify it using Dragonface...
matisys said:
How do you know that?
But I couldn't modify it using Dragonface...
Click to expand...
Click to collapse
I checked the recovery in case build.prop lies.
Then again is their update a zip? Might be something exotic.
I also checked their ota apk and tested it.
It didn't download. Sent a lot of info from my tab. Some didn't match (faked what I easily could)... or no updates anymore...
Gave 502...
matisys said:
I didn't find a proper spot
But I couldn't modify it using Dragonface...
Click to expand...
Click to collapse
Another soc and device, but might work.
Entering to Flashing/Adfu mode (and Recovery mode too) - Actions Semi ATM7029 Quad-core ARM CPU devices
Entering to Flashing/Adfu mode (and Recovery mode too) - posted in Actions Semi ATM7029 Quad-core ARM CPU devices: The instructions given in this thread should work, but still as always, you use them at your own risk!If there is a hardware problem then the tablet probably is bricked for good...
www.slatedroid.com
Battery removing might be the safest...
Try imgRePacker...
OK, I managed to unpack the img file and to edit build.prop - Thanks fot that info One small step forward.
I added:
qemu.hw.mainkeys=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=ptp,adb (this one already exists)
Hoping it will allow me to access the system via adb or screen directly after reflash.
I didn't pack it back yet as I still didn't manage to access this device from computer...
I tried to find a spot on mainboard - I've made a connection on two spots:
{
"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"
}
But no luck...
There is more spots however, but none marked as recovery, ADFU, or similar...
And still no USB debugging, nor adb connection...:/
Tried of course some tricks with power button holding, clicking, reseting while hold, etc...
Any further suggestions...?
Maybe some ideas to enforce upgrade via wifi? I can establish a server, but not sure what exactly server should serve...? Just an img file is rather not enough...
Below that E351308 text, or above if other way around, is the target for those pin suggestions. But try battery, you can always solder it back together,.. or just let it go empty - might work...
> what exactly server should serve...?
yeah, there probably is some data exchange before the download..
BTW, this img appears to have adb enabled, so it's not the last one... Or it's disabled by other means...
Data it sent:
{"genderId":-1,"email":"","Locale":{"L":"eng","S":"en_US","C":"USA"},"deviceInfo":{"TIME":1419244414000,"FINGERPRINT":"ZOOM_ME\/ZM7WIFI\/ZM7WIFI:4.2.2\/JDQ39\/20141222:eng\/test-keys","HARDWARE":"gs702a","VERSION.SDK_INT":17,"BOARD":"exdroid","PRODUCT":"ZM7WIFI","DISPLAY":"ZM7WIFI_20141222","VERSION.INCREMENTAL":"20141222","DEVICE":"ZM7WIFI","TAGS":"test-keys","MODEL":"ZM7WIFI","BOOTLOADER":"unknown","CPU_ABI":"armeabi-v7a","CPU_ABI2":"armeabi","VERSION.CODENAME":"REL","MANUFACTURER":"ZOOM_ME","BRAND":"ZOOM_ME"}}
Click to expand...
Click to collapse
That hardware exposed me. It didn't get that from *.prop files.
OK, so currently it's like below.
I already tried some tricks with battery - disconnecting, connecting while booting, and no luck...
I tried with all spots marked below - one by one, and some combinations of few of them...
And the status is like that - spots 2 and 3 - seems to be ignored when connected - device behaves like nothing happened. It's more interesting when I connected 1 or 4. Device didn't start, and in a computer it appeared as unknown winusb device or Billboard device when connected 4 (USB\VID_1F3A&PID_EFE8&REV_02;3).
Universal ADB driver installer doesn't recognize it...
The only driver I managed to install was Allwinner driver and it appeared as USB Device(VID_1f3a_PID_efe8).
But still no luck with adb connection... Phoenix suite also doesn't recognize the device... In this state screen remains black and AXP223 (Power management) quickly becomes hot as hell (battery unplugged)...
Once unsoldered - it went back to life.
I also realized that my device says that it is version ZM7WIFI_20150717... what is confusing a bit because in other place it says it's 2.2 23-5.03.2015 software version...
But still no connection or any option to flash it
Can you tell me how do you run this software/hardware to see what does it send?
I can still use OTG keyboard and mouse - maybe there is some option to enter android settings and simply enable USB debugging?
Those pins that I mentioned at slatedroid are on the sides of that chip.. and don't solder, just place some tool - a needle between them. And if recognized remove it as after error it must function again in order to flash or what ever..
Here is one older post showing pin connecting for Amlogic,
that other was Actions Semi. Both go a mode that enables flashing when device looks dead. I don't know about Allwinner, is it similar...
How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0 - Ainol Novo 7 Crystal
Page 1 of 47 - How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0 - posted in Ainol Novo 7 Crystal: How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0If Ive helped you unbrick your device please consider a donation, even if it is small it will help!My laptop is currently all...
www.slatedroid.com
So it seems that would be all, and the device got bricked...
I started the device with 7 and 8 pin of Flash memory connected - it was connected to PC and PhoenixSuite with original img loaded was running.Phoenix asked me immediately if I want to format the device - I clicked no, and it still started to flash the memory... It finished succesfully, device restarted and...now it freezes on initial logo.
Phoenix and adb recognize the device now, but adb shell doesn't work:
- exec '/system/bin/sh' failed: No such file or directory (2) -
and when I try to repeat flashing, phoenix recognizes device, but once I click upgrade - device resets, and upgrade is not performed...
EDIT: It's not that bad... I managed to make it working again on original software, and after one more reflash - ADB works well
Thanks a lot for all your help!
Did the reset hole fix it?
Maybe you should have formatted it in case the data is the reason to the freeze. But how it recovered?...
This Allwinner seem to be quite good.
Open source and giving info.
FEL - linux-sunxi.org
linux-sunxi.org
Installing to NAND - linux-sunxi.org
linux-sunxi.org
FEL/USBBoot - linux-sunxi.org
linux-sunxi.org
matisys said:
after one more reflash - ADB works well
Thanks a lot for all your help!
Click to expand...
Click to collapse
Great! Now disable that ota updater apk so it doesn't update it again...
It's actually hard to tell how it got fixed... instruction tells to not format the storage to not loose the unique device number - so I didn't, but it seems that it got formatted by itself as I lost all my pictures, but number remained untouched.
Now adb is enabled and I can freely connect to it - seems that something simply went wrong during previous upgrade years ago.
build.prop file gets restored after every reboot, so I can't put and store any changes there...
And OTA is not an issue as this device is not supported for a long time now And I'm not exactly sure how to do it, and feel a bit afraid of touching it when it finally works...
But just to finish entire project - can you recommend some reliable android SSH and FTP server? Or maybe something to share a folder via SMB?
matisys said:
But just to finish entire project - can you recommend some reliable android SSH and FTP server? Or maybe something to share a folder via SMB?
Click to expand...
Click to collapse
Not really but that android version limits the choices nicely...
Here is one saying it's open source.
swiftp
A FTP Server for your Android device.
ppareit.github.io
I think I once tested cifs in that Action Semi but it was long ago and was ready made in that test boot img...
[HOW TO] 2-way network file sharing on Android
Hi everyone, just thought I'd write up some quick instructions on how to set up file sharing between Android and a PC - both mounting Windows shares on Android, and Android on Windows. I was always frustrated by iOS's inability to do this easily, and it was one of the major reasons I switched...
forums.androidcentral.com
Thanks. Finally, after some trials I used SSHDroid and it's quite decent...
Can you also tell me how to permanently edit build.prop file? Mine is reverted to original after reboot. Device is factory rooted.