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.
Related
[update 2013/04/10]
And it is back to life! :victory:
I still cannot believe it! I decided to have another go using the Haier W718 USB cable and guess what? The cable supplied with the Zhou Xing i9300 is basically a big piece of s****.
I can confirm that the test point which worked for me are also GND + KCOL0
I have flashed the ROM wich link yuweng supplied. Thanks, again, bro :good:
Most things work except:
1) The ribbon cable running from the volume keys to the upper board is detached and I am not sure of how to fix this. Is it crazy to "superglue" it?
2) The IMEIs are not recognised. I have tried setting them up manually (following a video from Colonel Zap and taking the digits printed underneath the battery slot). No joy, no matter what SIM card slot I try, I get "IMEI invalid". In engineer mode, under bandmode, I have actually noticed that no band is selected. I check those applicable in Spain and click on "Set", but it basically ignores it.
So I am trying to get now a new ROM, hopefully closer to our settings in Spain. I have contacted a fellow member from a Spanish forum. Fingers crossed.
Oh, I almost forgot. Since the volume keys are not working because of the detached ribbon cable, I have ported TWRP recovery for the Zhou Xing. I thought a touch screen recovery would come in particularly handy now! Here it is.
BACKGROUND STORY BELOW:
Hi all!
I softbricked my Zhou Xing i9300 (MT6577) and now it won't boot :silly:. I cannot even get into recovery mode.
The only way I can access the phone is by SP Flash Tool. Thanks to another member of this forum (Dragonevo) I got hold of the stock ROM. However, this file is in a zip format, so the kind I have seen updating from recovery mode. Only the boot.img file is found out of all the files SP Flash tool looks for. Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
khankll said:
so what is the update ?
copy all the info in first post so it is easy to keep track of goings so far.
Click to expand...
Click to collapse
Thanks, khankll So here is the update on the 1st post. Sorry, but I am leaving in an hour and will be away for the whole week, so this is as much I can tell at this point.
khankll said:
the first thing is that you make it recognizable by pc .
Click to expand...
Click to collapse
At first I still got it recognised as MTK device, but right now the best I get is an "Unknown device" under USB devices (not under COM ports). This is with the phone completely assembled and battery inserted. When I dismantle the phone to try to trigger test point, no sign of life whatsoever. If I try to update the drivers, I get something like "Windows determined the best drivers are already present". I guess Windows is only detecting the device as some kind of USB memory and that is 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"
}
khankll said:
for rom do search at china-iphone.ru forum .. also 4pda.ru ..
Click to expand...
Click to collapse
I already found a ROM thanks to dragonevo's pointer here. The problem is, I guess, this ROM is in a format to be used when you can boot into Recovery mode. I say "I guess" because I have never got to see Recovery mode on this phone. I am not even sure of the key combination (tried Power & Volume + and Power & Volume -). I am using SP Flash Tool and it looks first for a scatter text file, and several other files that are not in that ROM zip, (only the boot.img is there). And from what I gather all these files also are specific to the phone model.
This is why I raised my original question in this post, so that I could use the ROM found in Flash Tool.
khankll said:
try all the connections to be ok .. usb connector should be making proper connection .. try checking continuity b/w the pins inside connector and the point where they attach to pcb.. ( u can attach a thin wire to the probe of multimeter and insert that into usb port .. its hard but possible . i did checked like it ..)
Click to expand...
Click to collapse
I am not sure I get this, but I will try when I get back in one week
khankll said:
also what is the battery voltage ? is it charged ?
Click to expand...
Click to collapse
2.9 v (I have a spare one which reading is 4.1 v)
Reminder: when I try the test point, the battery is not present (it cannot be since the board has to be completely dismantled on this phone to access KCOL and GND points. commonwarrior has another phone model but exactly the same board and it has worked for him this way. If I got this right, the battery is not required and Flash Tool (since yesterday I am using the latest supplied by commonwarrior) actually has an option called "Autodetect", which is supposed to work either way, with and without battery). file is in a zip format, so the kind I have seen updating from recovery mode. Only the boot.img file is found out of all the files SP Flash tool looks for. Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
[update 2013/02/14]
Sorry about vanishing, guys. I actually bumped into a bigger problem. My PC hard disk crashed. Anyway, I recovered my older (and smaller capacity) hard disk and installed it. As to the OS, I have just installed Ubuntu 12.04 + Windows XP as a virtual machine. I am a novice to Ubuntu, so please forgive me if the ending of this story is still delayed as I have other priorities to take care of right now.
Thanks a bunch again to yuweng for the correction for the test point and finally the files to flash from SP Flash Tools. I have downloaded the files and will have another go when I get the chance.
To be continued...
[update 2013/02/18]
I am afraid I am giving up on the Zhou Xing. No matter what test point I try, I never get any response in Flash Tool (I have also tried different versions including the latest one uploaded by commonwarrior).
With all the handling, the flat small cable that runs from the Volume up and down keys is detached from the contacts on the main board and I cannot see how I could weld these back.
So I am closing this chapter on my end. I hope it has been helpful to other people. At least now we have the files to flash from Flash Tools for this phone model. I wish we had found them before I screwed it completely.
Thanks again for all your help, particularly to yuweng and commonwarrior
Zhou xing bricked.
2x1 said:
Hi all!
I softbricked my Zhou Xing i9300 (MT6577) and now it won't boot :silly:. I cannot even get into recovery mode.
The only way I can access the phone is by SP Flash Tool. Thanks to another member of this forum (Dragonevo) I got hold of the stock ROM. However, this file is in a zip format, so the kind I have seen updating from recovery mode. Only the boot.img file is found out of all the files SP Flash tool looks for. Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
Click to expand...
Click to collapse
I bricked my Zhou xing.
It's dead...
I followe the system explained here http://forum.xda-developers.com/showthread.php?p=34912486#5...but I don't know exactly the test point on the mother board...so without success
Do you know a system to enter again in recovery ? also by spflash?
Could you shared the original rom..please.?
Thanks in advance...in this moment I'm in a big panic:crying:
pigu36 said:
I bricked my Zhou xing.
It's dead...
I followe the system explained here http://forum.xda-developers.com/showthread.php?p=34912486#5...but I don't know exactly the test point on the mother board...so without success
Do you know a system to enter again in recovery ? also by spflash?
Could you shared the original rom..please.?
Thanks in advance...in this moment I'm in a big panic:crying:
Click to expand...
Click to collapse
Sorry, pigu36, I actually never got into Recovery mode. I flashed mine (and softbricked it) with SP Flash Tool.
Regarding the stock ROM, you will find the link in Dragonevo's post.
Maybe in that same thread, somebody will be able to tell you how to get into Recovery mode. As far as I am concerned, I have tried pressing "Power + Volume up" keys, but it has never worked.
Whatever I find out, I will share it here and in the other thread.
Good luck!
so whats the issue of playing with test points if u can make it detect thorugh spf ?
just search for ok rom and flash it ..
khankll said:
so whats the issue of playing with test points if u can make it detect thorugh spf ?
just search for ok rom and flash it ..
Click to expand...
Click to collapse
Sorry about the confusion, khankll.
This was before I tried to flash something else because I thought it could not get worse and maybe I could flash some kind of Recovery which would allow me to update from the SD card (where I have a copy of the stock ROM in a zip file).
However... things could get worse and they did. The phone is not detected any more even in SP Flash Tool, not charging... well you know the symptoms. So I found the test point thread and fingers crossed with all the advice you guys are helping with
If I am lucky with the test point method, I will still need the type of files SP Flash Tool looks for. Unless you know a way of getting them (converting repacking, I don't know what the right word would be) from the stock ROM zip file.
Model: ZhouXing I9300 MTK6577 Dual Core Android 4.0 3G GPS 4.7 Inch 8.0 MP Camera Smart Phone
Some pics
so what is the update ?
copy all the info in first post so it is easy to keep track of goings so far.
the first thing is that you make it recognizable by pc .
for rom do search at china-iphone.ru forum .. also 4pda.ru ..
try all the connections to be ok .. usb connector should be making proper connection .. try checking continuity b/w the pins inside connector and the point where they attach to pcb.. ( u can attach a thin wire to the probe of multimeter and insert that into usb port .. its hard but possible . i did checked like it ..)
also what is the battery voltage ? is it charged ?
2x1 said:
Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
Click to expand...
Click to collapse
Sent you pm previously & notice that you haven't been online since 8th February 2013 08:20 AM...
Good news, found your Stock ROM here, credits to Анатолий... :laugh:
it turns out the testpoint KCOL0 & GND is wrong, credits to orx65...
Hopefully, this infos here will be useful for Zhou Xing users to unbrick their device too... :fingers-crossed:
Cheers...
Many, many, thanks for this rare rom. So I was able to unbrick my phone without any hardware experiments. I searched several Weeks!
My only problem is, that there is no touchscreen-response.
Any Idea to solve this problem?
Thanks and regards
Herby53
Hmmm, could i be that you forgot to install back the Touch Screen panel Flex Ribbon Cable...
Attach example is my friend's Touch Diamond2 9300 i help him replace the Touch Screen panel, hopefully it will be useful as a guide...
Another possibility is that may be this ROM is not for your Zhou Xing... :laugh:
Could you comfirm that the testpoint for your Zhou Xing is KCOL0 & DM
yuweng said:
Hmmm, could i be that you forgot to install back the Touch Screen panel Flex Ribbon Cable...
Attach example is my friend's Touch Diamond2 9300 i help him replace the Touch Screen panel, hopefully it will be useful as a guide...
Another possibility is that may be this ROM is not for your Zhou Xing... :laugh:
Could you comfirm that the testpoint for your Zhou Xing is KCOL0 & DM
Click to expand...
Click to collapse
Thanks for the fast response, Yuweng
I have installed back the Ribbon Cable, but not correct and without complete contacts. Now the TouchScreen works, but the touches lands not there where they should. Especially noticeable when using the phone keypad #1-3 = #4-6. I think I have to calibrate the touchscreen, but don't know how.
Second problem: the hardware- (volume up / down) - and sensor buttons (menu, home and back) are without function. I hope I did not damaged the flat cable searching the testpoint.
Your question about the testpoint:
See thread ..... / / forum.xda-developers.com/showthread.php? p = 36908056
# 240
The first image shows the backsite of the board. Testpoint for me wars KCOLO & GND to start flashtool download => there is no Point DM.
Greetings
Herby
Hmm, according to orx65 photo on previous page, its definitely not KCOL0 & GND ( the two red dots )....
Big problem ! To calibrate Touch Screen, you need to boot into Factory mode....
Shut down the phone then hold Volume Down, don't let go & press power button until you see that it boots into Factory mode then only let go... :fingers-crossed:
Then it will display all the keys that you need to press once then only you can proceed with the Factory mode calibration...
ESC, BACK, MENU, VOLUME UP, VOLUME DOWN, POWER
Thanks once more!
I first have to repair the definitly broken flat cable for the hardware buttons. It already looked a bit cracked out of delivery.
But my fingers and my soldering iron are to big. :laugh: I must look even if there's a trick!?
Testpoint:
The combination on first picture (with phone 9 ContactPoints) ist KCOLO (2nd row/ center) & GND (first row/ center) worked for me.
It's shown in the picture thereunder.
There is no Contact with DM. 3rd Row right Contact is named DP, but I don't know if this ist what you are looking for.
There is one crazy idea on repairing the Flex Ribbon Cable here with a staple... :laugh:
Can't see it clearly on those photos, so what i meant was : does KCOL0 with DP works, if not then i'll remove the photo on previous page...
... for me only KCOLO & GND works ...
Hey! You don't have ti flash it under a virtual machine. It causes problems. 1st of all, you have to download the stok rom, unpack.it on a pc with a windows installed. Install the.phone.drivers. disassembly the.phone and do a little.test point.to recognize the.flash mode. Run the.flash tool.loading the scatter file of.your stok, start the flashing in all the ports using the Automatic flag in battery section, the Preloader flag under the battery section. Also check.the usb option, just enable.the.Usb and not mpre.connetions kind. Start the flashing.in alk the ports, make.a.little test point and you.will see the loading.flashing.bar sorry for the errors in my typing.thw qwerty touch is very hard to use
Sent from my lt29i modded phone!
commonwarrior said:
Hey! You don't have ti flash it under a virtual machine. It causes problems. 1st of all, you have to download the stok rom, unpack.it on a pc with a windows installed. Install the.phone.drivers. disassembly the.phone and do a little.test point.to recognize the.flash mode. Run the.flash tool.loading the scatter file of.your stok, start the flashing in all the ports using the Automatic flag in battery section, the Preloader flag under the battery section. Also check.the usb option, just enable.the.Usb and not mpre.connetions kind. Start the flashing.in alk the ports, make.a.little test point and you.will see the loading.flashing.bar sorry for the errors in my typing.thw qwerty touch is very hard to use
Sent from my lt29i modded phone!
Click to expand...
Click to collapse
Thanks, commonwarrior
Just for the record, I never tried flashing under a virtual machine. The Ubuntu + VirtualBox set up took place after many tests under Windows 7 when my hard disk failed. I may have another go on my laptop (running Windows XP) and if I succeed, I will let you know.
Cheers!
2x1 said:
Thanks, commonwarrior
Just for the record, I never tried flashing under a virtual machine. The Ubuntu + VirtualBox set up took place after many tests under Windows 7 when my hard disk failed. I may have another go on my laptop (running Windows XP) and if I succeed, I will let you know.
Cheers!
Click to expand...
Click to collapse
This is a capture for the flash tool settings. In option, leave just the usb flag and disable the RID flags. Just copy all the options you see in this picture and start the flashing in all the ports to be sure.
Sent from my lt29i modded phone!
I solved the problem
pigu36 said:
I bricked my Zhou xing.
It's dead...
I followe the system explained here http://forum.xda-developers.com/showthread.php?p=34912486#5...but I don't know exactly the test point on the mother board...so without success
Do you know a system to enter again in recovery ? also by spflash?
Could you shared the original rom..please.?
Thanks in advance...in this moment I'm in a big panic:crying:
Click to expand...
Click to collapse
If you don´t have solved the problem I have the original Zhou xing android 4.1.1 rom flash usb cable intallation
USB problem?
Hi guys. I few weeks ago I received my Zhou Xing i9300 and everything work great, but now, some days ago it start to no be recognized by my PC.
It simply dont do nothing.
I already try a new USB cable and even try to connect to another PC here i my home, and stay won't working.
Any idea about what possibly happens?
Any help will be veeeeeery appreciated.
Hey,
Tried as hard as I could not to have to ask, looked everywhere I could think of, searched through dozens of threads and found nothing in regards to my Trio Stealth G2 tablet.
My question is, what method of rooting should I use for my tablet, and once I do root would there be a custom ROM I could use?
I've seen people mention they messed up flashing a custom ROM to the Stealth Pro 7, but I'm not sure if any ROM made for a 7" Cortex A9 tablet would work. Don't want to brick this though so thought I wouldn't chance it.
Thanks
I got the other day an I am to wanting to root it I think bin4ry root method would work but adb won't work cause there's no fastboot on the thing it dose have a recovery but its 3e
Sent from my G2 using xda premium
I think I got some progress today while its pluged into ur computer press pwr+vol- to get off of battery charging screen then hold them till u here ur computer make the sound like something got pluged in an ur tablet will be under m3-chipset in device manager search the internet for aml flash tool I have got it to connect to my pc
Sent from my G2 using xda premium
Not gonna use aml flash tools cause I can't find any good info on it found a safe mode on the thing today an got root with bin4ry to finally pick up the device its using adb still no root cant get a backup made with it an adb in cmd won't pick it up I know the tab has it tho I found the adb file on it after looking forever View attachment 2107849
{
"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"
}
Sent from my G2 using xda premium
here is a method that might work for you
go to my thread: forum.xda-developers.com/showthread.php?p=44294370#post44294370
I would post it here but i would just take up alot of posting space writing it down..the way i did it worked for me and believe me i was going for hours trying to find someway to root my trio stealth g2 until i found out how lmao let me know how it goes
U really got root on it
Sent from my G2 using xda premium
Yeah I did i have it rooted now with the play store mod
Sent from my G2 using xda app-developers app
Trio Stealth G2
Just got this tablet today. I was able to root it using the One Click Root and it has rooted it properly so it would seem so far.
slick97477 said:
Just got this tablet today. I was able to root it using the One Click Root and it has rooted it properly so it would seem so far.
Click to expand...
Click to collapse
Hi, slick97477. Where did you get the One Click Root tool? I didn't see any forums for this (or any other Trio) device on here.
Thank you in advance.
http://forum.xda-developers.com/showthread.php?t=1734365
One click
I got it from here
just google oneclickroot
and just run it. Couldn't believe it worked but it did.
However today went to try and turn it on and nothing, Just hung and the Trio logo. Let it sit for about 10 minutes. Decided maybe battery was dead and plugged it in still nothing. No battery logo nothing. Hit reset button and plugged it in again and nothing. Screen doesnt come on now nothing but however weird thing is it shows up as winusb now under devices which is amlogic driver for flashing firmware which im not sure how this has happened but it has. I have took it apart and took pics of the mainboard and cpu. Would like to see if perhaps there is firmware out for this...Have done quite a bit of research and numerous different things so far..
I have downloaded the firmware installer from amlogic but so far no firmware seems to like my cpu....Hmmm well cannot upload pictures yet for some reason..If anybody is interested in trying to help me figure out which firmware will work on it I would greatly appreciate it. I used it the night before and it worked great. Have not installed anything new or anything so I am a bit baffled in how the firmware got torched but I am pretty sure that is what has happened any ideas I am willing to try. I have recently dived into really messing with the android devices but had not done anything with this tablet yet because I had not found a way to back up the current firmware on it...so was really being nice to it for now....
(Edit) Pics are included just didn't try hard enough
try this
Yea id like to help try turning it on while its pluged in ur computer then hold the power button till u here the sound like something got pluged in ur computer then then hit the power button to turn it on if this dosnt work try turning it on then after the @9 boot logo hold both volume keys that should put it in safe mode only the apps that came on the tab will work
Trio Stealth g2 tablet issues
Hi I was reading your posts about the g2 and I seem to be having a similar issue. The tablet is frozen on the trio stealth g2 loading screen and I have pushed all the buttons including the reset button on back to no success. I got the tablet to recognize as m3 chip on my pc and was able to aml flash tool but every time I try to upload a rom like stock jellybean or some custom rom its asking for a upgrade config file which of course I do not have there has to be a way to just completley wipe this tablet and install a new os any ideas on how I can get this thing to flash, I was hoping I could load a sd card and push some buttons on the tablet to flash from the sd card but I have no clue if thats possible
Stealth G2 9.7"
damncheaptablets said:
Hi I was reading your posts about the g2 and I seem to be having a similar issue. The tablet is frozen on the trio stealth g2 loading screen and I have pushed all the buttons including the reset button on back to no success. I got the tablet to recognize as m3 chip on my pc and was able to aml flash tool but every time I try to upload a rom like stock jellybean or some custom rom its asking for a upgrade config file which of course I do not have there has to be a way to just completley wipe this tablet and install a new os any ideas on how I can get this thing to flash, I was hoping I could load a sd card and push some buttons on the tablet to flash from the sd card but I have no clue if thats possible
Click to expand...
Click to collapse
I too have a g2 with the same issue but i've gotten it into ADB Recovery. When using the AML Flash tool, after you import the upgrade file and it asks you to manually input a config file use the config_progress.xml file that is in the AML flash installation directory possibly under \resource\
This is what got me to ADB recovery but anytime I try to reboot the tablet it reverts back to Worldcup Device in device manager so I'm stuck. Hope this helps.
Issue
spurloc said:
I too have a g2 with the same issue but i've gotten it into ADB Recovery. When using the AML Flash tool, after you import the upgrade file and it asks you to manually input a config file use the config_progress.xml file that is in the AML flash installation directory possibly under \resource\
This is what got me to ADB recovery but anytime I try to reboot the tablet it reverts back to Worldcup Device in device manager so I'm stuck. Hope this helps.
Click to expand...
Click to collapse
Hey I was able to flash the tabley with aml but I used novo 7 fire and now nothing comes up, no boot screen or anything, however when its plugged into my pc I can access the internal storage and Micro sd card storage, but I need to remove the rom and get one that works correctly for the tablet, unlike before It wont let me push the power and vol button to make it go to the m3 chip which then I could use the aml world cup driver so some how I have to flash it from the internal storage or by some means but I have no clue at this point. The driver is Portable media player MID Novo7 I changed the driver to android ADB which it installs but then I cant access the internal storage, is there anyway to re flash this? I tried pushing diffrent buttons on the tablet to see if a diffrent chip is recongized like the m3 was from before but nothing
damncheaptablets said:
I tried pushing diffrent buttons on the tablet to see if a diffrent chip is recongized like the m3 was from before but nothing
Click to expand...
Click to collapse
From my experience with the stealth g2 9.7" if you open up the tablet and use a pin or small screwdriver to short (connect) nand pins 7 & 8 (counting down from top right of chip, yours maybe 5 & 6 or 6 & 7 ) as seen in picture below the circled area, while powering the unit on, should erase the nand and revert to Worldcup device in device manager which will allow the AML flash tool to see the device again.
Image -- freaktab(.)com/attachment.php?attachmentid=3068&d=1377544440
Umm ur awesome
spurloc said:
From my experience with the stealth g2 9.7" if you open up the tablet and use a pin or small screwdriver to short (connect) nand pins 7 & 8 (counting down from top right of chip, yours maybe 5 & 6 or 6 & 7 ) as seen in picture below the circled area, while powering the unit on, should erase the nand and revert to Worldcup device in device manager which will allow the AML flash tool to see the device again.
Image -- freaktab(.)com/attachment.php?attachmentid=3068&d=1377544440
Click to expand...
Click to collapse
Thanks alot, I opened my tablet, found the tf boot and it worked, now if I can just get the right firmware installed
damncheaptablets said:
Thanks alot, I opened my tablet, found the tf boot and it worked, now if I can just get the right firmware installed
Click to expand...
Click to collapse
Nice! Glad it worked. At this point we're in the same boat. I'm not sure how to properly flash a new firmware even though i've got an identical working one. It seem's I've tried everything and the closest i've gotten is just getting the screen to light up blank, which hasn't happened in a long while now. I used the instructions in the PDF file below except i replaced the bootloader.img, boot.img & recovery.img files from a backup I made, ran heroflash.bat and rebooted the device and now the screen comes on blank. Not sure where to go from here though. I'll keep trying
Instructions - PDF Link
svet-tabletu(.)cz/podpora/Ainol_Novo_10_Hero/ENG_NOVO10HERO_Unbrick_Instruction_0_4_RC.pdf
package link
mediafire(.)com/download/nq0ppsle1t662ht/AML_USB_Unbrick_AINOL_HERO_10.rar
Yeah im stuck now
spurloc said:
Nice! Glad it worked. At this point we're in the same boat. I'm not sure how to properly flash a new firmware even though i've got an identical working one. It seem's I've tried everything and the closest i've gotten is just getting the screen to light up blank, which hasn't happened in a long while now. I used the instructions in the PDF file below except i replaced the bootloader.img, boot.img & recovery.img files from a backup I made, ran heroflash.bat and rebooted the device and now the screen comes on blank. Not sure where to go from here though. I'll keep trying
Instructions - PDF Link
svet-tabletu(.)cz/podpora/Ainol_Novo_10_Hero/ENG_NOVO10HERO_Unbrick_Instruction_0_4_RC.pdf
package link
mediafire(.)com/download/nq0ppsle1t662ht/AML_USB_Unbrick_AINOL_HERO_10.rar
Click to expand...
Click to collapse
Yeah I tried to flash 40D_resque.zip with aml and I would either get W/ Import upgrade file C:\Users\Jy\Desktop\_USB-Burning-Tool\resources
\40D_resque.zip
W/ [P2][19:41:11]Loading spl ...
W/ [P2][19:41:12]Transfer Complete! total size is 18556 Bytes
E/ [P2][19:41:13]Spl code,identy(-1)
E/ [P2][19:41:13]Load uboot failed 1 times
E/ [P2][19:41:14]Spl code,identy(-1)
E/ [P2][19:41:14]Load uboot failed 2 times
E/ [P2][19:41:15]Spl code,identy(-1)
E/ [P2][19:41:15]Load uboot failed 3 times
E/ [P2][19:41:16]Spl code,identy(-1)
E/ [P2][19:41:16]Load uboot failed 4 times
E/ [P2][19:41:16]Load uboot failed 3 times, retry from 0 step
W/ [P2][19:41:17]Loading spl ...
W/ [P2][19:41:17]before loadSpl, identify return -1
and have to use a screwdriver to reboot it in m6 chip, before I was able to get about 80% with flash but then got a boot error about unable to find device and at that time the tablet would change device name from the worldcup driver to portable media device with a drive letter like H:/ but I couldnt access it, man this is making me
damncheaptablets said:
Yeah I tried to flash 40D_resque.zip with aml and I would either get W/ Import upgrade file C:\Users\Jy\Desktop\_USB-Burning-Tool\resources
E/ [P2][19:41:16]Spl code,identy(-1)
E/ [P2][19:41:16]Load uboot failed 4 times
E/ [P2][19:41:16]Load uboot failed 3 times, retry from 0 step
W/ [P2][19:41:17]Loading spl ...
W/ [P2][19:41:17]before loadSpl, identify return -1
and have to use a screwdriver to reboot it in m6 chip, before I was able to get about 80% with flash but then got a boot error about unable to find device and at that time the tablet would change device name from the worldcup driver to portable media device with a drive letter like H:/ but I couldnt access it, man this is making me
Click to expand...
Click to collapse
It looks like there's an issue with that specific u-boot.bin (u-boot-orig.bin) within that package. Although the fact that it shows up in device manager as Portable device means that part of it was written by the flash utility. Have you tried force-ably replacing the drivers from portable device to android adb drivers. This might allow you to access the adb recovery mode.
Alternatively if ADB doesnt show any devices after replacing the drivers, you might want to uninstall the adb drivers that didnt work, once it appears as portable device again, the tablet might be looking for its new firmware on the sdcard. Check out the page in the link and follow the instructions for "Method One - SD Card Method for a "soft" brick". It involves restoring a factory image onto the sdcard using a handy tool "USB Image tool" and then rebooting. It might kick in an update from the sd.
link --
slatedroid(.)com/topic/41478-how-to-unbrick-your-amlogic-aml8726-mx-series-tablet-v20/
Also I could upload the aml flash files that are getting me into adb recovery mode every time
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
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
TL;DR: Removing com.coloros.weather.service through ADB and upgrading to Realme UI 2.0 will cause a flicker-brick on the lock screen.
Possible solutions:
Run adb shell cmd pm enable com.coloros.weather.service; will only work if you keep the USB debugging enabled and tick 'Always allow connection from this PC' during previous ADB sessions.
Wait for Realme to release an OTA to fix this problem. No one knows how long it will take to develop and propagate, no one even knows whether they see this issue yet, and once they saw it, no one knows whether they'll consider fixing it.
Quick wins:
How to allow running adb-command during this flicker-brick state? USB debugging is enabled; however, since I did not tick 'always allow', the device shows as 'unauthorized' on adb devices.
How to raise this issue to Realme? How to let their relevant (technical) team know about this problem? Usually, a case from customer service has to be escalated multiple times to reach the technical team.
Spoiler: Plea
As listed on recovery options below, one of the quick solutions for this problem is to simply wipe the device or flash an ozip over it. However, I just lost my wife last month to COVID. We sent each other a lot of voice messages during her final days. I tried reinstalling WhatsApp using the same number. The latest backup WhatsApp found on Google Drive is dated early July. There are also many camera roll pictures not showing on Google Photos. Hence my worst-case solution is worded "wipe the phone, move on, and make amends". However, I am not ready to accept this solution yet.
======================= Full issue description and analysis =======================
Hi! I need some help regarding the "lock screen flicker" issue upon upgrading Realme 7 RMX2151 to Realme UI 2.0 (based on Android 11). The problem is widely known, and the suspected root cause is already found. However, I'm here to seek suggestions and ideas.
The issue is not specific to Realme 7; it generally applies to all Realme UI 2.0 upgrades. But since my device is Realme 7 RMX2151, I decided to post it here. The title might be a bit misleading since the flicker is unlike a CRT flicker, but simply the screen turns on and off frequently. To watch the issue:
Spoiler
It's not my video, but the problem is the exact same.
What still works:
Alarm works, also snoozing and dismissing them
Receiving and rejecting calls works, but the contact name won't appear since the phonebook is still encrypted
Pressing and holding the power button will trigger a grey rectangle that persists during the flicker
Pressing and holding power + volume up will reboot the device
Pressing and holding power + volume up + volume down will reboot the device into Recovery
The Recovery works perfectly, including OTA updates
The root cause is the removal of com.coloros.weather.service package. A user may choose to remove this package to 'debloat' their phone and remove the unused app. Little did they expect that this seemingly unimportant package will cause the lock screen flicker issue upon upgrade. This has been acknowledged by Mywk on his thread "[GUIDE][EU/IN ROM] REALME UI Debloat List"
Mywk said:
Weather Service
[WARNING] Uninstalling this and updating your phone to Android 11 WILL BRICK your device.
Code:
adb shell pm uninstall -k --user 0 com.coloros.weather.service
Click to expand...
Click to collapse
Suggested solutions so far:
Enabling com.coloros.weather.service through adb
This solution only works if:
- you enabled USB debugging (a prerequisite for debloating through ADB) and did not disable it afterwards
- you ticked 'always allow connection' (forgot the exact wording) when using adb to save the keys on the device
- some kind of luck that the device will allow debugging even though it had not been unlocked after the first boot
From r/Realme Discord Server
{
"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"
}
Click to expand...
Click to collapse
[CONFIRMED DATA LOSS] Get into recovery mode and wipe the device. However, some users reported that the issue persists after the device wipe unless the device is downgraded to Realme UI 1.0. For Realme 7 RMX2151 (non-EU), the official downgrade package can be downloaded here. Copy the ozip into the root of the SD Card and install it through Recovery. It is appropriately signed, so it can be used on stock recovery.
Wait for Realme to release an OTA update to fix this issue and make it available. It could take months for it to propagate, though. I'm not sure whether they are aware of this issue or think it is worth fixing (debloat = user's fault?)
[SUSPECTED DATA LOSS] Flash an ozip of the same or more recent firmware. The ozip flash feature of stock recovery does not clearly state 'Keep Data', unlike check OTA that says so directly under the command. But shouldn't an update ozip (to a more recent version, not a rollback) works like regular OTA?
[CONFIRMED PARTIAL DATA LOSS] Pulling the internal storade through recovery mode. App data will be lost.
This solution only works if:
- you enabled USB debugging (a prerequisite for debloating through ADB) and did not disable it afterwards
- you ticked 'always allow connection' (forgot the exact wording) when using adb to save the keys on the device
Boot into recovery mode. Choose to install ozip from the device. Recovery will then ask for the device password to decrypt the internal storage. Do not choose any file. Connect the phone to the computer and do an adb pull.
Use a Boot ROM (BROM) exploit by Dinolek and k4y0z to inject the package com.coloros.weather.service. Or, in my specific case (USB Debugging enabled but RSA Public Key not saved on device), write the public key on /data/misc/adb/adb_keys.
However, I need more guidance on how to do this, as most tutorials I saw was to overwrite the phone with a custom ROM, while my current objective is to return my phone to normal function through reinstalling com.coloros.weather.service or at least decrypt the internal storage and pull the files out (app data will be lost). I cannot understand and adapt the tutorial to my objective or even know whether this BROM exploit will help me.
Possible outcomes:
Best scenario: You could magically issue an ADB command to reinstall com.coloros.weather.service in the flicker-bricked state. I did keep USB debugging enabled, but I did not save my computer's RSA key on the device; hence the device shows up as 'unauthorized' on adb devices. Any suggestions?
Not-so-bad: somehow, an ADB command could be issued in recovery mode or normal boot to pull the data. The same problem occurs: I did not save my computer's RSA key on the device; hence the device shows up as 'unauthorized' on adb devices. Any suggestions?
Another scenario: Realme realizes this issue and works on a fix. The fix is made available as an OTA and can be downloaded through recovery mode. Any ideas where to ask to increase the chance of this happening?
Worst case: wipe the phone, move on, and make amends with whatever App Backup, Google Photos, WhatsApp Cloud Backup, etc., successfully keep.
any updates? usb debug not working i removed long time ago weather service didnt know that issue with new realme ui 2.0 now my phone is broken... realme 6
droi1 said:
any updates? usb debug not working i removed long time ago weather service didnt know that issue with new realme ui 2.0 now my phone is broken... realme 6
Click to expand...
Click to collapse
No updates so far.
Realme stated that they won't fix this issue. Debloating through adb is considered an unsupported modification of base OS. If the OTA breaks the OS, their direction is to wipe the device (data will be lost).
I consider this is lousy engineering and hazardous to user data, though.
said1219 said:
No updates so far.
Realme stated that they won't fix this issue. Debloating through adb is considered an unsupported modification of base OS. If the OTA breaks the OS, their direction is to wipe the device (data will be lost).
I consider this is lousy engineering and hazardous to user data, though.
Click to expand...
Click to collapse
is there maybe a way to enable usb debugging via recover mode? Or at least backup my data from it? Or go back to Realme UI 1.0 im realy lost....
droi1 said:
is there maybe a way to enable usb debugging via recover mode?
Click to expand...
Click to collapse
No. If there is, then it would be a HUGE security bug.
droi1 said:
Or at least backup my data from it?
Click to expand...
Click to collapse
Enter recovery mode.
Decrypt your storage. Choose "Install Updates" -> "From storage". Enter your device Password/Pattern/PIN. Do not choose any file. We're doing this only to get the recovery to decrypt storage.
Run adb root (this requires you to tap 'always allow' the first time you set up adb, see this screen. If you don't tick that box, then you're out of luck. No way to recover data.)
Run adb pull /data/media/0/path/to/file. e.g. adb pull /data/media/0/DCIM/Camera/IMG_20211002_211234.heic. If you want to pull 10.000 files, run this command 10.000 times. Please note that this command cannot pull your application's data. The named file will be copied to the directory that adb resides.
After doing that for like, 2 weeks straight, I succesfully get all my data except the chat history of WhatsApp, Signal, and Threema.
droi1 said:
Or go back to Realme UI 1.0 im realy lost....
Click to expand...
Click to collapse
No. Please refer to my post on another thread.
said1219 said:
No. If there is, then it would be a HUGE security bug.
Run adb root (this requires you to tap 'always allow' the first time you set up adb, see this screen. If you don't tick that box, then you're out of luck. No way to recover data.)
Click to expand...
Click to collapse
my phone is not rootet i get this error in minimal adb:
unable to connect for root: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
droi1 said:
my phone is not rootet i get this error in minimal adb:
unable to connect for root: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Click to expand...
Click to collapse
The command is to gain root access, not to root your phone. The command to root your phone is adb oem unlock to unlock the bootloader, flashing a custom bootloader (e.g. TWRP), and then flashing a root zip file (e.g. Magisk).
The error message indicated that you did not tick 'always allow' the first time you set up adb (see this screen). Sorry, you're out of luck. No way to recover data.
said1219 said:
The command is to gain root access, not to root your phone. The command to root your phone is adb oem unlock to unlock the bootloader, flashing a custom bootloader (e.g. TWRP), and then flashing a root zip file (e.g. Magisk).
The error message indicated that you did not tick 'always allow' the first time you set up adb (see this screen). Sorry, you're out of luck. No way to recover data.
Click to expand...
Click to collapse
i only want backup Photos from Whatsapp and DCIM not even this is possible? I will never ever debloat my Phone again with ADB...
droi1 said:
i only want backup Photos from Whatsapp and DCIM not even this is possible? I will never ever debloat my Phone again with ADB...
Click to expand...
Click to collapse
No. Your PC is not authorized to access the data in your phone.
thanks for your help
i did wipe data in recovery (retain contacts, mesages & photos) but same issue the weather service is not back so i have to format the phone
ended up in same situation on my xt
droi1 said:
thanks for your help
i did wipe data in recovery (retain contacts, mesages & photos) but same issue the weather service is not back so i have to format the phone
Click to expand...
Click to collapse
they trapped us real good. sneaky bastards. lets make sure to let them know that they are only digging their own grave.
Any solution yet? I'm stuck, too.
The problem's been discussed in this thread, too (however, no solution either - yet) :
Flicking Lock Screen after update to latest Android 11 OTA update
I just saw an update notification that Android 11 had been released. Since my phone was running Android 10, I proceeded the update without hesitation (and without backup). The phone is running stock rom without root (I guess I did unlock the...
forum.xda-developers.com
said1219 said:
No updates so far.
Realme stated that they won't fix this issue. Debloating through adb is considered an unsupported modification of base OS. If the OTA breaks the OS, their direction is to wipe the device (data will be lost).
I consider this is lousy engineering and hazardous to user data, though.
Click to expand...
Click to collapse
Is this an official Realme statement? Where did you find this?
Thx.
said1219 said:
[CONFIRMED PARTIAL DATA LOSS] Pulling the internal storade through recovery mode. App data will be lost.
This solution only works if:
- you enabled USB debugging (a prerequisite for debloating through ADB) and did not disable it afterwards
- you ticked 'always allow connection' (forgot the exact wording) when using adb to save the keys on the device
Boot into recovery mode. Choose to install ozip from the device. Recovery will then ask for the device password to decrypt the internal storage. Do not choose any file. Connect the phone to the computer and do an adb pull.
Click to expand...
Click to collapse
So uh my phone is 6 pro and enabled always allow button just before this incident but whenever I I connect my phone to my laptop it doesn't read, does it probably have to do with that prompt that asks the phone to "allow files" &"charging only" thing?? If so how can my lappy read my device again?
Edit: idk how to delte comment I apologise for this
said1219 said:
...
Click to expand...
Click to collapse
said1219 said:
...
Click to expand...
Click to collapse
Quasar.Illumia said:
So uh my phone is 6 pro and enabled always allow button just before this incident but whenever I I connect my phone to my laptop it doesn't read, does it probably have to do with that prompt that asks the phone to "allow files" &"charging only" thing?? If so how can my lappy read my device again?
Edit: idk how to delte comment I apologise for this
Click to expand...
Click to collapse
You can't delete the post your self, but you can request using the report form to do that, anyway, you can replace all the words from the duplicated posts, by, for example, three points ... or by some word.
What are you trying to do onto your device?
If you are trying to see your device while in stock recovery then it's not possible, while in other stock recoveries you can at least, perform ADB sideload, in Realme stock recoveries (as in Xiaomi), this is disabled (by normal means), you can update only either browsing to internal or an SD card.
jime1 said:
they trapped us real good. sneaky bastards. lets make sure to let them know that they are only digging their own grave.
Click to expand...
Click to collapse
I immediately switched to Samsung after that incident, although I keep my bricked Realme charged regularly, hoping that RUI 3.0 flashed on top of the flicker-bricked phones will fix the phone.
I considered getting a cheaper Samsung (priced like Realme), but after considering the performance penalty and remembering that I upgrade my phone biannually, I got the S20 FE which are priced twice as expensive but I plan to keep using this for 4 years.
lowbu said:
Is this an official Realme statement? Where did you find this?
Thx.
Click to expand...
Click to collapse
Half a year ago I came to largest Realme Service Center in Jakarta, considered their Level 3 support desk nationally, and had a screaming match over this issue.
Quasar.Illumia said:
So uh my phone is 6 pro and enabled always allow button just before this incident but whenever I I connect my phone to my laptop it doesn't read, does it probably have to do with that prompt that asks the phone to "allow files" &"charging only" thing?? If so how can my lappy read my device again?
Click to expand...
Click to collapse
ADB should be run in the lockscreen, the screen that "flickers" upon boot finish. Not in the recovery mode as per your photo.
Have you reinstalled Windows on your PC? Since reinstalling Windows erases the ADB keys if not backed up properly from user folder.
How long since you last connected your phone to your PC? If I remember correctly, unused ADB keys are automatically deleted after a period of time from your phone.
And I think you need to either pick MTP or PTP to allow ADB. "Allow charging only" disables data exchange entirely. This is to prevent an attack like this: a public USB charging port is provided at a public location, e.g. airport. Unbeknownst to the user, the charging port is connected to a laptop which then automatically tries to pull the entire content of any device connected to it. "Allow charging only" will cause the laptop to see nothing, exactly like your photo that said "no device attached", although in your case I suspect it's due to the device not being in normal booted state.
said1219 said:
Have you reinstalled Windows on your PC? Since reinstalling Windows erases the ADB keys if not backed up properly from user folder.
How long since you last connected your phone to your PC? If I remember correctly, unused ADB keys are automatically deleted after a period of time from your phone.
Click to expand...
Click to collapse
Just few days ago like literally a day before the incident, and yeah I think the adb keys resets but idk about that since its just 3 days as of now
said1219 said:
And I think you need to either pick MTP or PTP to allow ADB. "Allow charging only" disables data exchange entirely. This is to prevent an attack like this: a public USB charging port is provided at a public location, e.g. airport. Unbeknownst to the user, the charging port is connected to a laptop which then automatically tries to pull the entire content of any device connected to it. "Allow charging only" will cause the laptop to see nothing, exactly like your photo that said "no device attached", although in your case I suspect it's due to the device not being in normal booted state.
Click to expand...
Click to collapse
And this one is my only problem, the mtp thing should asks the user of the phone to allow a device do a "file transfer" right? I can't do that due to the screen doing the flicker thingy. Idk about your de ice but my lappy can't read my phone without it
Edit: also question, does the adb key resets depending on laptop used?
And also my phone again is realme 6 pro, does reformating my phone guaranteed to fix this?I think Im out of options since I saw posts about the OTA thingy not fixing this too and my online classes are near too