Stuck uploading APK to Lineage 18 ROM (read to the end) - General Questions and Answers

Preamble​I oft find in various forums that people are so filled with the milk of human kindness that they just can't wait to help, ( or may gain a few more badges~) ignoring everything but the heading.
And in doing so ask foolish questions.
So, please DO READ to the end.
UPDATE
Thanks to @ jwoegerbauer I now know I can't install the Lantern APK via recovery. I must use ADB which I have previously tried but failed.
Obviously, therefore I do not know what I am doing with ADB.
My tasks focus now is to install Lantern APK via ADB with the devices , tools and systems already mentioned. (below)
Unless someone, somewhere knows where I can find a Lantern ZIP file which I can flash. (seems I am good at that now at least~)
Please DO read everything below ladies and gents, my sense of humour and patience does have a limit~
Mobile Device Details​Samsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in brief​To install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?​During one of my many attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
I am happy with that, seems no big deal for me, I was able to successfully install the new OS + Gapps. And it is one less APP to install
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!

thebic said:
Mobile Device Details​Samsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in brief​To install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?​During one of my attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
Seems no big deal for me, I was able to successfully install the new OS + Gapps.
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
Click to expand...
Click to collapse
What recovery are you using? Have you tried different recoveries?

What version of twrp are you running?

An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>

Yeah you could use adb sideload in twrp.

jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Click to expand...
Click to collapse
Hehe, I can verify your first statement!
Do you have a link you can direct me to please as to how to do it via ADB in Lineage recovery as I did try that (side loading) via TWRP and it threw back an error. I can't recall but I think it was permissions or similar?
Sorry, I forgot to mention that in my post.
Thx for your constructive feedback - much appreciated.
P

Re-read my cited post: I've edited it.

jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Click to expand...
Click to collapse
Ohhhhh Kayyyyyy - coping.
Just.
You have added code?
Before I go ahead and destroy New York, I use that where?
How?
and errr... why?
I am guessing in Terminal, but I am not really sure what I am trying to achieve here.
Sorry, not arguing or being difficult, I just find it helps me if I know what EXPECTED outcomes are. Just in case it isn't what I should expect. :>(
Thx for your patience.
p

I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.

jwoegerbauer said:
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
Click to expand...
Click to collapse
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.

thebic said:
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
Click to expand...
Click to collapse
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$

I seem to be going in ever decreasing circles.
Please help me out- what is protocol.
Do I keep updating my progress - or lack of- here, in this dialogue, or should I continue to update my original post?
Which one best communicates to everyone where I am at?
Cheers

thebic said:
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
Click to expand...
Click to collapse
You forgot to add the exact file directory.

Keno_I said:
You forgot to add the exact file directory.
Click to expand...
Click to collapse
Did it work after adding the file directory?

You are right.
I am not sure how this forum works, so it was more of a post to jwoegerbauer.
Anyway, even opening the folder with terminal and using adb install lantern-installer failed with a CLOSE error message. I guess that meant close as in shut not closes as in almost!
I can, using Lineageos recovery access ADP on my phone with the instruction: " now send the package you want to apply to the device with "adb sideload <filename>"
However that triggers a screed of data in terminal which, frankly, is well beyond my rudimentary level of comprehension.
I have tried following 3 other on line tuts which suggest using ADB on my computer. All goes well until the instruction: <adb devices> which returns:
$ adb devices
List of devices attached
In other words, computer can't find phone!
I initially tried it in DOWLOAD mode, with the usual "download in progress, do not disconnect source."
Then reading the tuts again, none mentioned download mode so I tried with just the device attached to the machine in normal phone usage mode. Checked that SAMSUNG was visible and I could open the folders but again failed. ( sorry I forget what that error message was)
So far the most positive has been the direct ADB via Lineageos, but I have no idea where to go from there.
It is knocking on 37* here, too hot to think so I am taking a break.
Thx for your latest efforts.
Cheers
P

OK Finally!
[email protected]:~$ adb devices
List of devices attached
438f904d device
[email protected]:~$ adb install /home/bicyu/Sam-upgrade/lantern-installer/lantern-installer.apk
Performing Streamed Install
Success
[email protected]:~$
I have read so many posts all end with the <adb devices> and on each one I see zilch.
So, for anyone else in this boat, here is my solution.
In developer OPTIONS on your LINEAGEos device scroll down to
DEFAULT USB CONFIGURATION​Very likely it is set to FILE TRANSFER - mine was.
Change it to USB TETHERING
Then enter < adb devices> in terminal.
You should then see your Android listed.
Proceed with: adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
You should see a SUCCESS flag!
NOTES: This works in Lineageos ROM on Linux, ( Ubuntu / Zorin O/S)
I dunno about others.
You need to have dev options activated.
Change the USB setting back when done, otherwise it tends to mess up your Internet! (did mine anyway!)
This is the best background tut to ADB I found.
He talks about a USB3 bug which, apparently, creates the same problem - maybe THAT is your issue? It was that article which put me on the USB CONFIG train.
Hope this helps someone.
A REALLY HUGE thank you to jwoegerbauer for putting me
on the right track - wrong train, - but right track.
Cheers mate!

Glad to hear you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.

Yep! Well good luck

jwoegerbauer said:
Glad to here you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Click to expand...
Click to collapse
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p

thebic said:
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
Click to expand...
Click to collapse
Aroma File Manager, how nostalgic~
Now to wait till a mod closes this post

Related

[Q] Flash Google Apps on bSquare MDP 8660

Hi,
I tried finding a better place to post this, but there are no device forums for the bSquare MDP 8660 probably because its not that common and its a 'development phone'.
I'm using one of these devices in the lab I'm working in and I wanted to see if I could flash Google Apps on it since it comes without any of them (Market, Maps, Gmail, etc.).
Since it has an unlocked bootloader, can I just flash Google Apps (from Cyanogen's website) to it the same way you do it when installing the Cyanogen ROM? Are these files device independent? Or would this be an almost sure way of bricking the phone?
Device website: bsquare.com/snapdragon-mobile-development-platform.aspx
OS: Android 2.3.4
I would really appreciate any guidance/suggestions. Thanks!
gjain89 said:
Hi,
I tried finding a better place to post this, but there are no device forums for the bSquare MDP 8660 probably because its not that common and its a 'development phone'.
I'm using one of these devices in the lab I'm working in and I wanted to see if I could flash Google Apps on it since it comes without any of them (Market, Maps, Gmail, etc.).
Since it has an unlocked bootloader, can I just flash Google Apps (from Cyanogen's website) to it the same way you do it when installing the Cyanogen ROM? Are these files device independent? Or would this be an almost sure way of bricking the phone?
Device website: bsquare.com/snapdragon-mobile-development-platform.aspx
OS: Android 2.3.4
I would really appreciate any guidance/suggestions. Thanks!
Click to expand...
Click to collapse
Most probably yes.
Well here's my advice. Follow at your own risk. It might not probably brick it but there's always the slight risk of stuff going awry.
1) Make a Flash backup.
2) See if you have the system/app folder intact.
3) Flash the Google Market(yes, only the market.)
4) Install whatever the apps you want from the Market.
All Google apps except Market and Talk can be downloaded from the Market. You can of course flash the whole gapps update but downloading this way gives you some peace of mind and chances of avoiding any possible incompatible apps. (Like Voice Search which may not work properly on all ROMs. But, if it's AOSP, all Google apps would work and should work. )
Most of the Google apps would be device independent since most of them would use the Android API and not the native platform.
Flashing custom recovery - didn't work
Thanks for the guidelines.
I tried flashing ClockworkMod recovery so that I could make a backup of the phone, but every time I boot into recovery it shows a blank screen now. ADB doesn't recognize the device either. I tried Amon Ra's recovery and the phone is doing the same thing.
Before flashing any of the custom recoveries, the phone would just show the triangle when booting into recovery. It did show up on ADB though.
Would you have any suggestions on how I should continue? In case its of any use, I do have a package that I downloaded from the manufacturer's website that contains the original boot, recovery, and system images (along with some other files).
gjain89 said:
Thanks for the guidelines.
I tried flashing ClockworkMod recovery so that I could make a backup of the phone, but every time I boot into recovery it shows a blank screen now. ADB doesn't recognize the device either. I tried Amon Ra's recovery and the phone is doing the same thing.
Before flashing any of the custom recoveries, the phone would just show the triangle when booting into recovery. It did show up on ADB though.
Would you have any suggestions on how I should continue? In case its of any use, I do have a package that I downloaded from the manufacturer's website that contains the original boot, recovery, and system images (along with some other files).
Click to expand...
Click to collapse
As I told earlier, I'm not so familiar with the device.
If ADB is not working in recovery, it could either mean that the USB drivers(the drivers in the device, not PC) are corrupted or that the recovery is incompatible.
If CWM recovery you used is 100% compatible with your device(ie other people are using it without issues), it means that you must reflash all your files to factory and then flash a fresh copy of recovery. Simply, you must start it from scratch.
If you have no idea of the compatibility of CWM with your device,
1) Check and see if ADB/fastboot is working well with your device in other modes(boot, system). You can perform a simple file transfer and check the checksum of the original copy and copy on your device to ensure integrity.
2) If ADB/fastboot works well in all other modes but fails only in recovery, flash stock recovery(only recovery) and see if adb is working well. You can do the same thing as before. If adb/fastboot works well in stock recovery but fails in CWM recovery, it probably means CWM is not fully compatible with your device.
If CWM works well, go ahead and make a backup and proceed to flashing market. But, if like I said in 2), if CWM is not fully compatible with your device, proceed with caution.
As an an alternative, if you are going through all these ONLY to get the market, you can extract the market update and push the relevant files to the correct paths in the device using ADB in recovery or bootloader mode.
Installing only the Market app
Hi Nibras,
Sorry for not replying back to you. My college classes got started and I couldn't spend much time on this project.
I liked the idea of just extracting the Market app and installing that (since that is all I really need).
Do you think I could just use the procedure outlined below, even though I won't be doing it on Honeycomb:
Installing Android Market over your freshly installed HoneyComb will require a different approach than just installing an APK.
Make sure you have ADB up and running, and your device recognized. Refer to our guides on what is ADB and how to install it, and how to enable ADB USB drivers for NVIDIA Tegra and Tegra 2 based devices.
Download this version of the Market (2.2.11).
Download GoogleServicesFramework.apk.
Place the files in any folder on your computer and open a Command Prompt window, browsing to that folder.
Enter these commands in the Command Prompt window:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push Vending.apk system/app/Vending.apk
adb push GoogleServicesFramework.apk system/app/GoogleServicesFramework.apk
adb shell
cd system/app
chmod 6755 Vending.apk
chmod 6755 GoogleServicesFramework.apk
exit
adb reboot
Now go to apps, open the market and sign in. If the Market won’t open at first, reboot and try again and it should work.
Click to expand...
Click to collapse
gjain89 said:
Hi Nibras,
Sorry for not replying back to you. My college classes got started and I couldn't spend much time on this project.
I liked the idea of just extracting the Market app and installing that (since that is all I really need).
Do you think I could just use the procedure outlined below, even though I won't be doing it on Honeycomb:
Click to expand...
Click to collapse
That should work I guess. But, flashing via recovery is just a one step process. =)
Update.zip also does just the above process, I guess. It just saves us a couple of steps. Also, if you make a recovery backup, if anything goes wrong(say boot loop or force close of system at boot), you can revert very easily since recovery is independent of all the other data on phone.
And, I guess you might have to push Talk.apk too. I'm not sure about it though. Some people complained that removing Talk.apk broke the Market authentication.
If you want to push Talk.apk, get the apk file and,
Type adb push Talk.apk system/app/Talk.apk after adb push GoogleServicesFramework.apk system/app/GoogleServicesFramework.apk
Also, type, chmod 6755 Talk.apk after chmod 6755 GoogleServicesFramework.apk.
Btw, you can also ignore Android Market altogether and use Amazon App Store as well as GetJar.com. They both offer install-able Market apps. Of course, they don't have a collection as large as Android Market.
@gjain89:
Did you ever try pushing the Market files to the MDP? If so, then did it work? I have one of these and I'm in a similar position.
Thanks
I have one of these...
I used adb to push the files. However the system partition barely has any room for more apps. so apps larger than 2MB won't install, unless you obtain the APK from a secondary source.
Refer to this thread for more information: http://forum.xda-developers.com/showthread.php?t=1400737
And this one: https://developer.qualcomm.com/forum/qdevnet-forums/general-discussion/6864
Plus, many apps force close.
Enjoy!
PS: Let's try to stick together, we might be able to fix some of these problems. Maybe someone could build a custom rom.

I need an easier guide...

To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium

[GUIDE] [VIDEO] Various Guides Including Root and ROM reviews

Sticky Worthy?
How To Guides in Video Form:
How To One Click Unlock Bootloader http://www.youtube.com/watch?v=sSVD5b9nAcI&list=UU1J4DKcJXENzC-FkyMU6dow&index=15&feature=plcp
How To Manually Unlock Bootloader http://www.youtube.com/watch?v=sSVD5b9nAcI&list=UU1J4DKcJXENzC-FkyMU6dow&index=15&feature=plcp
One Click DebugFS method: http://www.youtube.com/watch?v=EpuiKIl7lpI&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Video Root Guide: http://youtu.be/cuiJYKV2GGU
^^This is just a Visual aid for the method provided by Invisiblek outlined here http://forum.xda-developers.com/showthread.php?t=1756885
How to Update Your Baseband/Modem to latest OTA : http://www.youtube.com/watch?v=K2dQ2kv9kYs&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
How To Nandroid backup in Cwm Recovery: https://www.youtube.com/watch?v=4zWSK7cO3xg&feature=youtube_gdata_player
How To Unbrick, Unroot, Factory Restore Galaxy S III http://youtu.be/p0T4FO_NZ8Y
How To Easily Backup Apps and Data to Flashable.zip http://youtu.be/OPPoKlu_4qw
How To Install CM9 or CM10: http://youtu.be/f68NgGgrwAQ
How To Back up and Restore IMEI: http://www.youtube.com/watch?v=dl6Ms3oVEDo&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
How To Use Your SGS3 as a Netflix Remote: http://www.youtube.com/watch?v=JICq0P1Ywg4&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Rom Reviews and Install Guides:
JellyWiz Touchwiz Jelly Bean 4.1.1 Rom Review and Install: http://www.youtube.com/watch?v=twDBZg4wkBk&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Liquid v2 RC3 Rom Review and Install http://www.youtube.com/watch?v=ieuy5Bx76-Q&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
AOKP 4.1.1 Rom Review and Install: http://www.youtube.com/watch?v=kjULad8XS-4&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
MIUI v4.1 Jelly Bean Review and Install for Unlocked Bootloaderhttp://www.youtube.com/watch?v=azkToBXLjig&list=UU1J4DKcJXENzC-FkyMU6dow&index=2&feature=plcp
Cyanogen Mod 10 Jelly Bean for Unlocked Bootloader http://www.youtube.com/watch?v=7nW0SRKxUQk&list=UU1J4DKcJXENzC-FkyMU6dow&index=14&feature=plcp
Clean Rom Full Review and Install For Unlocked Bootloader http://www.youtube.com/watch?v=0PtIKXddfNI&list=UU1J4DKcJXENzC-FkyMU6dow&index=7&feature=plcp
Bean's Custom Stock Rom Review and Install For Unlocked Bootloader http://www.youtube.com/watch?v=napoMpZKCDA&list=UU1J4DKcJXENzC-FkyMU6dow&index=13&feature=plcp
First ROM Stock Stripped by Invisiblek: for Locked Bootloader https://www.youtube.com/watch?v=9Oek_24wEXI&feature=youtube_gdata_player
Cyanogen Mod 10 Rom Review: for Locked Bootloader http://youtu.be/2efLx_iTBDk
AOKP Android Open Kang Project Milestone 6 Review and Install for Locked Bootloader http://youtu.be/ATiFaCssKHs
Synergy Rom (Battery life and Stability) Review and Install for Locked Bootloader http://youtu.be/bj7w2nu_sKk
fix your link. you forgot the opening [ preceding the closing youtube tag.
Could you please do a back-to-stock video as well?
Thanks for doing this. First Samsung phone so it's quite new to me. Appreciate the video, it'll definitely help
Sent from my PC36100 using Tapatalk 2
Always wish these were made for each phone, the devs put so much work into making roms and root methods, but usually skimp on the instructions for those of us who aren't as experienced. Thanks for this
I will try to update this thread with any other videos I make, or I might make a separate thread. Glad its helped though.
Sent from my Galaxy Nexus using xda app-developers app
Thanks for the video. I'll be going through this as quickly as I can get home from work tomorrow!!
Great video, but in your description, to install the SDK using the Java links, I installed the JDK but the SDK install still thinks it's missing, and won't go any further, making me Cancel out. No idea what to do now...no SDK = no ADB commands :-(
minmongoblin said:
Great video, but in your description, to install the SDK using the Java links, I installed the JDK but the SDK install still thinks it's missing, and won't go any further, making me Cancel out. No idea what to do now...no SDK = no ADB commands :-(
Click to expand...
Click to collapse
Alos agree great video and helped me do root in no time at all! However, like you I am unable to get the adb part of the video working. I followed your other video and written instructions to the "t", and I only got as far as..
"adb is not recognized as an internal or external command"
I got the Java JDK to install fine as well as the SDK with all the required installs you said were needed for it to work. I left out all others as I'm not really too familiar with adb is it is. I changed the path, and named folders and files exactly as you did in your video. However I could never get the cmd to show adb devices.
I know the original post stated that we should know how to use it before we try this, but after trying to do research on this for the past 4 hours last night.. I concluded I have no idea what I am doing wrong/nor how to do it properly apparently.
If anyone would be able to possibly give me some assistance that would be great .
Lemonhead8890 said:
Alos agree great video and helped me do root in no time at all! However, like you I am unable to get the adb part of the video working. I followed your other video and written instructions to the "t", and I only got as far as..
"adb is not recognized as an internal or external command"
I got the Java JDK to install fine as well as the SDK with all the required installs you said were needed for it to work. I left out all others as I'm not really too familiar with adb is it is. I changed the path, and named folders and files exactly as you did in your video. However I could never get the cmd to show adb devices.
I know the original post stated that we should know how to use it before we try this, but after trying to do research on this for the past 4 hours last night.. I concluded I have no idea what I am doing wrong/nor how to do it properly apparently.
If anyone would be able to possibly give me some assistance that would be great .
Click to expand...
Click to collapse
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Having the same problem. I see the long list of commands. But when I type "adb devices" nothing is listed.
trginter said:
Having the same problem. I see the long list of commands. But when I type "adb devices" nothing is listed.
Click to expand...
Click to collapse
I haven't tried it myself yet, but it sounds like you don't have the drivers properly installed.
Sent from my Ally (Cant wait to get rid of this POS and replace it with my S3 tomorrow!)
NightxFall said:
I haven't tried it myself yet, but it sounds like you don't have the drivers properly installed.
Sent from my Ally (Cant wait to get rid of this POS and replace it with my S3 tomorrow!)
Click to expand...
Click to collapse
That would be my guess. Put it in USB Debug mode, and plug the phone in, I think it auto-installs the ADB drivers.
Hmm, the phone is in USB Debugging Mode and plugged in, nothing downloaded.
trginter said:
Hmm, the phone is in USB Debugging Mode and plugged in, nothing downloaded.
Click to expand...
Click to collapse
What is the exact output when you type adb devices?
Good to know root is avail
Will try this tomorrow after work
s197 said:
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Click to expand...
Click to collapse
For those having problems with this, look up "how to add a path to the windows command line“. You should not have to CD to a directory to make a command work .
Sent from my SCH-I535
s197 said:
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Click to expand...
Click to collapse
Yes, usb debugging was on when I tried to do this. I usually always just leave it on honestly.
I guess I should have been more clear about where I was at, but yes i did the
cd platform-tools .. enter.. then adb.exe.. and thats when I got the 'adb' is not an internal or external command. I dont know where I messed up along the way... . I feel pretty confident I did everything correctly.
However there was one difference i did notice. On the path stated in the guide it says system32 something then you list the path to platform tools and whatnot.... but mine had something /windowspowershell/ or something like that.
I went back to the start and deleted my drivers and reinstalled them but deleted the jdk and sdk for the time being.. Maybe ill try again soon if I can figure it out better.
I believe this will help a lot of you. Thanks goes to Adrynalyne....
http://forum.xda-developers.com/showthread.php?t=879701
Lemonhead8890 said:
Yes, usb debugging was on when I tried to do this. I usually always just leave it on honestly.
I guess I should have been more clear about where I was at, but yes i did the
cd platform-tools .. enter.. then adb.exe.. and thats when I got the 'adb' is not an internal or external command. I dont know where I messed up along the way... . I feel pretty confident I did everything correctly.
However there was one difference i did notice. On the path stated in the guide it says system32 something then you list the path to platform tools and whatnot.... but mine had something /windowspowershell/ or something like that.
I went back to the start and deleted my drivers and reinstalled them but deleted the jdk and sdk for the time being.. Maybe ill try again soon if I can figure it out better.
Click to expand...
Click to collapse
It sounds like you're not moving to the right directory. Check to see where your adb file is, on the new SDK it's in platform-tools but if you downloaded ADB from a long time ago, it's in another folder (I think tools, but it's been a while).
What I would do is navigate to your adb file from "my computer". At the top, under address, it will show you the path you need to type. For instance, for me, I open my computer, C: drive, Android folder, then platform-tools. So my path would be:
Code:
cd C:\Android\platform-tools
Everyone's path is different depending on where you put your files.

[q] huawei u8812d

Can I root Huawei U8812D? pls someone advice me.
babbird said:
Can I root Huawei U8812D? pls someone advice me.
Click to expand...
Click to collapse
I am a new user so I cannot post a links yet but google your phone and there should be a link to ANDROID net forum. There you will find a video showing you how to do it.
found something on chinese site that looks good
babbird said:
Can I root Huawei U8812D? pls someone advice me.
Click to expand...
Click to collapse
This looks really rough, but apparantly there is a boot.img, then other cracking tools can be used.
I'd love to try it, but... well... my chinese is limited to google-translate.
The URL won't post so this is a big hint:
products . mobileuncle . com / thread-202642-1-1 . html
I think I got it root on g302d u8812d
j_chytown said:
This looks really rough, but apparantly there is a boot.img, then other cracking tools can be used.
I'd love to try it, but... well... my chinese is limited to google-translate.
The URL won't post so this is a big hint:
products . mobileuncle . com / thread-202642-1-1 . html
Click to expand...
Click to collapse
Currently on that URL is a approx 14 MB rar file download, I _think_ I just got it sorted!
I don't have time now to make this pretty, but some others who want to hack. add links, etc feel free to work with this...
in fact I dont know if all these steps are required.
General Broad steps (ymmv, you are doing this to your own dang phone, dont blame me for bricks viruses or earthquakes etc, etc/ etc).
on your computer, uninstall adb, pdanet and any other tools that use the adb drivers and dlls, reboot as needed.
install the mt6575 drivers (I forgot whether I downloaded these or if they were part of the 14 meg file) reboot as needed
power down phone.
remove battery from phone, don't plug into computer.
launch flash_tool.exe
load the included scatterloading file MT6575...emmc.txt
press the download button
plug in phone to usb
put battery in phone
watch the blinkinlights for a few seconds, wait for the big green O
then I disconnect phone and ensure power down.
install SDK
power up phone and plug in
test adb (adb shell)
kill adb server
download and install superoneclick
download extra superoneclick exploits
launch superoneclick
click the big root button.
Test (you can use something like rom manager)
Now people should be able to try to install various CWMs.
I haven't gotten that far yet.
CWM for u8812d g302d ?
j_chytown said:
Currently on that URL is a approx 14 MB rar file download, I _think_ I just got it sorted!
I don't have time now to make this pretty, but some others who want to hack. add links, etc feel free to work with this...
in fact I dont know if all these steps are required.
General Broad steps (ymmv, you are doing this to your own dang phone, dont blame me for bricks viruses or earthquakes etc, etc/ etc).
on your computer, uninstall adb, pdanet and any other tools that use the adb drivers and dlls, reboot as needed.
install the mt6575 drivers (I forgot whether I downloaded these or if they were part of the 14 meg file) reboot as needed
power down phone.
remove battery from phone, don't plug into computer.
launch flash_tool.exe
load the included scatterloading file MT6575...emmc.txt
press the download button
plug in phone to usb
put battery in phone
watch the blinkinlights for a few seconds, wait for the big green O
then I disconnect phone and ensure power down.
install SDK
power up phone and plug in
test adb (adb shell)
kill adb server
download and install superoneclick
download extra superoneclick exploits
launch superoneclick
click the big root button.
Test (you can use something like rom manager)
Now people should be able to try to install various CWMs.
I haven't gotten that far yet.
Click to expand...
Click to collapse
Okay I may have found a working CWM clockworkmod recovery, but I don't have access to the chinese site, so others out there may be able to download it and try it out.
mm-mpxteam . net / forum . php ? mod = viewthread & tid = 4203
or maybe this one:
products . mobileuncle . com / thread-203098-1-1 . html
got the uncles recovery on the phone!
j_chytown said:
Okay I may have found a working CWM clockworkmod recovery, but I don't have access to the chinese site, so others out there may be able to download it and try it out.
mm-mpxteam . net / forum . php ? mod = viewthread & tid = 4203
or maybe this one:
products . mobileuncle . com / thread-203098-1-1 . html
Click to expand...
Click to collapse
it isn't clockwork, but I got a mobileuncle recovery on the phone. Is kinda fun to try to translate!
pan . baidu . com / share / link ? shareid = 63706 & uk = 2483368669
---------- Post added at 06:39 PM ---------- Previous post was at 06:25 PM ----------
j_chytown said:
it isn't clockwork, but I got a mobileuncle recovery on the phone. Is kinda fun to try to translate!
pan . baidu . com / share / link ? shareid = 63706 & uk = 2483368669
Click to expand...
Click to collapse
installed gapps 20110828 (via mobileuncle recovery) and I now have a market that doesn't force-close!
still getting "partners" to force close, but a lot of other stuff is working.
Great work!!! I'll try this on my phone or wait until is working?
Are the recovery and rom in chinese?
Thank a lot for testing.
working well
hiosin said:
Great work!!! I'll try this on my phone or wait until is working?
Are the recovery and rom in chinese?
Thank a lot for testing.
Click to expand...
Click to collapse
It is working very well.
No need for you or anyone to wait.
Just please know what you are doing (do you have basic understanding of recovery mode, roms, factory mode, and the dangers) in other words, if this is your first time doing this on a phone.. ask someone who knows what they are doing for help because I am not able to put together a documented procedure, but the findings above should allow someone else to do that. Additionally, I have no idea of the legality or safety of the software at URLs above.
conceptually this is 4 steps
1) flash boot.img that will allow cracking
2) crack to get SU installed
3) install Mobile Uncle Recovery mode and app
4) install gapps.
The MobileUncle recovery mode is Chinese, But the mobileuncle app is kinda like rom manager, it lets you set up what happens at next boot so you don't need to read the chinese in recovery text mode.
The patched rom is working for me in English with root, no detectable problem except FC on google partners (and I can't tell if that actually does anything). Remember this is not a new rom, just a patch to the huawei rom that allows a root crack.
There are about 4 chinese apps that I am afraid to uninstall..
one appears to be a chinese app store too, kinda fun to browse
gapps must be flashed with mobileuncle recovery (don't just unzip them)
US google play store is working.
I am fully migrated to this phone now and use it for daily work.
Good luck, and remember that this is why you got an android instead of a i-Thing.
Thanks thanks again. I'll try it and don't worry this is not the first time to modify a mobile. If it is all ok i posted here.
Working u8812d
Ok... It was successfully working on my phone. I have root and change recovery and then installing gapps. Almost of the apps is working of the play store. Thanks again and hope there is a release of ICS or JB rom for our phones.
See ya!!!:good:
j_chytown said:
It is working very well.
No need for you or anyone to wait.
Just please know what you are doing (do you have basic understanding of recovery mode, roms, factory mode, and the dangers) in other words, if this is your first time doing this on a phone.. ask someone who knows what they are doing for help because I am not able to put together a documented procedure, but the findings above should allow someone else to do that. Additionally, I have no idea of the legality or safety of the software at URLs above.
conceptually this is 4 steps
1) flash boot.img that will allow cracking
2) crack to get SU installed
3) install Mobile Uncle Recovery mode and app
4) install gapps.
The MobileUncle recovery mode is Chinese, But the mobileuncle app is kinda like rom manager, it lets you set up what happens at next boot so you don't need to read the chinese in recovery text mode.
The patched rom is working for me in English with root, no detectable problem except FC on google partners (and I can't tell if that actually does anything). Remember this is not a new rom, just a patch to the huawei rom that allows a root crack.
There are about 4 chinese apps that I am afraid to uninstall..
one appears to be a chinese app store too, kinda fun to browse
gapps must be flashed with mobileuncle recovery (don't just unzip them)
US google play store is working.
I am fully migrated to this phone now and use it for daily work.
Good luck, and remember that this is why you got an android instead of a i-Thing.
Click to expand...
Click to collapse
This does not work for my u8812d, gives an error using flash tool
Still not rooting
j_chytown said:
Currently on that URL is a approx 14 MB rar file download, I _think_ I just got it sorted!
I don't have time now to make this pretty, but some others who want to hack. add links, etc feel free to work with this...
in fact I dont know if all these steps are required.
General Broad steps (ymmv, you are doing this to your own dang phone, dont blame me for bricks viruses or earthquakes etc, etc/ etc).
on your computer, uninstall adb, pdanet and any other tools that use the adb drivers and dlls, reboot as needed.
install the mt6575 drivers (I forgot whether I downloaded these or if they were part of the 14 meg file) reboot as needed
power down phone.
remove battery from phone, don't plug into computer.
launch flash_tool.exe
load the included scatterloading file MT6575...emmc.txt
press the download button
plug in phone to usb
put battery in phone
watch the blinkinlights for a few seconds, wait for the big green O
then I disconnect phone and ensure power down.
install SDK
power up phone and plug in
test adb (adb shell)
kill adb server
download and install superoneclick
download extra superoneclick exploits
launch superoneclick
click the big root button.
Test (you can use something like rom manager)
Now people should be able to try to install various CWMs.
I haven't gotten that far yet.
Click to expand...
Click to collapse
Thanks for the steps though the problems are still coming thick and fast, I have a new U8812D from China, no China unicom splashscreen but lots of 'bloatware' still. I've been trying for days to root this thing and nothing's working.
I'm pretty sure I need root access becasue the phone is currently preventing me from adding my Gmail account and using the google play market and apps, other bits and pieces like assigning incoming call number to a contact are supposedly fixed by getting the google thing right. The phone is good but I'm missing alot of functionality.
If the above description sounds like rooting is not the solution, please let me know and point me to the right forum, if rooting is the obviously the only way out, I'm hoping to clarify a few step in the above walkthrough to help me and others.
1. I cant install the mt6575 MediaTek drivers, installing directly gives error 'driver cannot be installed this way' there is no COM-LPT port in my device manager to attach it to as a manually locate driver, I can add a COM port with add remove hardware but I have Code 10 error, device cannot start and doesnt seem to accept the mt6575 driver as an update even when forced to it with locate new driver, apparently this is no problem from other forums, still bugging me. Maybe I havent the right files? how do i get COM-LPT ports to show up properly?
2. when 'install m6575 drivers ... reboot' is the phone plugged in? to what device do we install the drivers or should it be automatic?
3. launch flash tool, i have located two versions of the MT6575...emmc.txt file, one delivers error, block count fail and has no files paths for the item in the main table, the other refuses to open, giving error, incorrect scatter file format. The latter has considerably more data in it when read in notepad.
4. Becasue of these errors, SP flash tool does not download to phone. all subsequent steps fail.
Assuming the initial flashing steps are successful, I must to use SuperOneClick to root the phone, where do I find the extra exploits needed? or are tehy automoatically sourced by SOC? Succeeding the root access step, I assume i can freeze the apps causing problems to my google sign in or delete them. Or could I please be directed to the ATTPlain rom mentionned by JohnnyParanoia in 'Almost All Huawei Stock Roms (Firmware) - Updated 28/06/12' board.
Since so many of the resource files I've trawled through are bung, anyone who can point me to reliable/tested files known to work with the U8812d I'd greatly appreciate in on top of the great appreciation I already have for your patience with a Noob. I located the 14Mbit .rar file mentioned above but not all parts worked, had to dl the different programs individually and some files had to hunt down form fileshare sites.
Lastly, i am using an HP laptop, Windows 7 64-bit, Thanks in advance.
Michael

[Q] FileMate Clear 7" T720 tablet

Does anyone know if Z4Root will work on this tablet? Thanks!
I've been looking for one for 3 days now, I tryed onclickroot and z4root or something like that,, cant find anything Anyone please help!!
I'm still waiting for my tablet to be delivered...I'm gonna try SuperOneClick (crosses fingers)
I got one of these for my daughter for xmas. I spent a few days trying to root it with no luck. I'm not intimately familiar with android (some unix experience), but I tried all the options I could find for rooting Allwinner a10 devices. At first I ran into problems with adb unable to recognize the device for most one-click methods. I downloaded the android tools and was able to connect with the included adb. After studying the scripts, they all use the "adb root" command to gain root access on the device and copy the necessary files. Unfortunately, this command fails using adb from the tools. At first I thought this was due to my adb version, but after doing some research I think it is actually due to the device kernel. I believe it requires reflashing or some exploit to be able to gain root. I was able to install root explorer and I can browse all the necessary directories but I can't modify or copy the necessary files into them. Busybox told me there was an older version installed, but wouldn't let me install a newer version (again I think due to the permissions). Also, superuser would say it installed but the su binary did not show up on the bin directory. As the necessary directories are all owned by root, I couldn't figure out a way to modify the permissions...
I wound up returning the FileMate and got a Lenovo IdeaTab. Got that rooted in no time.
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
ferny_dx said:
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
Click to expand...
Click to collapse
Screw it, here it is for future reference.
How'd you do it!?!?
ferny_dx said:
Screw it, here it is for future reference.
Click to expand...
Click to collapse
FileMate Clear T720
Thank you very much for being the only person ever to have posted in regards to this tablet. I just got mine for christmas and have been trying to get it rooted. I've tried a lot of those one-click methods, and I've even tried this Bin4ary method. but it just hangs up on "daemon started sucessfully*"
Can you please direct me to the filemate drivers (if needed)
also, I have usb debugging endable, allowing 3rd party (not secure) files enabled. and pulling my hair out (enabled).
Thanks again.
Also, I'm running windows 7 and 8, (((maybe i should try win7))) hmm. i'll get back to you on that. Anyhow, any advice would be greatly appreciated, since returning it doesn't sound very fun.
jiberish05 said:
FileMate Clear T720
pulling my hair out (enabled)..
Click to expand...
Click to collapse
I laughed so hard. ok your going to have to install drivers by force,
first off do you happen to have android sdk installed? if you don't there is another way but its going to sound weird,
if you do have the android SDK installed:
1. go to your computer manager (by opening explorer, right click on the "computer" group on the left column and select manager)
2. look for any unrecognized item that appears, ( it will most likely be labeled "Clear" with a faded icon and a "?" sign on top
3. right click and choose "Update drivers", it will give you options, choose "Browse my computer for driver software", another option screen will show,
4. at the bottom of the window there will be an option that says "let me pick from a list of device drivers on my computer"
5. on the screen that appears there should be an option that says "ADB Interface", choose this
6. choose "Google, Inc.">"ADB Testing Interface version x.x.x.x" (I chose version 2.1.0.0)
that should do it next time you plug in the tablet try running ddms or open the cmd and type in "adb devices" (assuming you have adb installed) and it should show.
if this helps just hit the thanks button
[edit] I am running windows 8 btw [/edit]
ADB interface doesn't show up
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
jiberish05 said:
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
Click to expand...
Click to collapse
open up SDK manager and go to Extras>"Google USB Drivers"
also install everything in the "Android 4.0 (API 14)" section, I have other options installed if this still doesn't work.
its worth it just for the extra stuff that root comes with like titanium backup, but you cant over clock, if you go any higher than 1200 MHz it will lock up and you have to force it to reset.
cyberkeeper1 said:
HERE is the link to root as provided earlier
Click Here to download ADB universal drivers. they should work better than the google USB drivers.
---------- Post added at 12:20 AM ---------- Previous post was at 12:11 AM ----------
this seems kind of spammy. What backs up my claim is that you dont have more than 5 posts...
Click to expand...
Click to collapse
Thanks for the link to my post on android central, the link in that post just comes back the xda thread
Root MANY ANDROID! [Upd: 20.11.2013] - Added Z1 Root
Sent from my XT862 using Tapatalk
Rooted Filemate Clear
I just wanted to confirm I have also rooted the Clear with the Bin4ry v33 exploit using option 1. Although I received the following error:
remote object '/system/bin/ric' does not exist
.
Going to copy files to it's place
Rebooting again, please wait!
Could Not Find C:\Documents and Settings\Graham School\My Documents\Downloads\Ro
ot_with_Restore_by_Bin4ry_v33\ric
Restoring previous Backup! Please select the RESTORE MY DATA option now on your
device!
SuperSu installed and root apps working.
Rooted With Kingo
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, no problem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Jfender1005 said:
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, lem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Click to expand...
Click to collapse
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Kingoroot
cyberkeeper1 said:
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Click to expand...
Click to collapse
http://www.kingoapp.com/android-root.htm
That is the link for the Kingo site. The first time I saw it on here there was some question about whether it was safe becase it is not open source and used a Chinese SuperSu app. I felt safe using it on a tablet because I do no banking on it or anything, but the newest posts I have seen are that Kingo is safe. Hope that helps. And if you know where to find a custom recovery that will work with this app please let me know.

Categories

Resources