Related
I think I bricked my Viewsonic G Tablet. I was running VEGAN perfectly then I decided to jack around with Ubuntu the Karmic link found here on XDA under "Ubuntu on G tablet" Did everything the best I could, failed, failed.. booted into clockwork, went to factory reset, no back up found anywhere, formatted EVERYTHING (data, cache, rom) If I plug the USB cable into my laptop it reads as H drive but when I click on H drive it says "please insert a disk in H:" if I put anything on the sd external, I can't get my tablet to even read the external. Every time I click on "mount SD ext" it just says failed. Without clockwork, I just get big red letters "Magic value mismatch" Please tell me I didn't brick it good...
I can get the roms or the zip files etc on the external SD but without being able to boot to or from it, I'm lost.
Thanks
http://forum.xda-developers.com/showthread.php?t=861950
Start there. If you need more help search for "nvflash" and you'll find lots of helpful posts.
Thank you for your quick reply! I am afraid to say that I am SOOOO ignorant on this stuff. I followed the link and it had a lot of information on running the nvflash (I think when you didn't have clockwork installed??) It said stuff about lots of stuff I don't understand, I am SO SORRY to be so basic. I do run Linux Ubuntu 10.10 and Windows 7 on a dual boot with my machine so we can work in either environment. I donwloaded the prereqs from the drop box so I have the files along with two different ROMs, but I can't get the Viewsonic tab to even recognize (via my laptop) the internal SD card. Then the External SD card either so I do not know of a way to get any of these files to the tablet?
Please continue to help me in the MOST basic way you can, if you will. I would be so VERY grateful and give kudos, thanks, or whatever needed. I just want to make it work.
If you are able to boot into recovery then go to advance, then select the option to partition your sd card then select 2048 then 0. See if that helps to get your internal sd card recognized. That has helped me before.
Just an idea. No guarantees it will work.
Start by relaxing and taking a few deep breathes. The instructions there are about as basic as you can get. Main thing istonot get ahead of yourself or read more into it than it says.
I find it easiest to use Linux.
Create a directory to hold the nvflash package.
Extract the nvflash_linux_2010110500.tar.gz archive into the directory.
Extract the nvflash_gtablet_2010110500.zip into the directory.
Put the gtablet into APX mode. From off turn it on while holding the volume down button. You should see the splash screen then it will go black. Plug it into your computer with the USB cable.
Open a terminal window and confirm that your computer can "see" the gtablet by typing "lsusb" command (without the quotes). It should respond with "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
If all is well at this point change into your nvflash directory and type the following command.
./nvflash_gtablet.sh
Now let the magic happen. In a few minutes you'll be back to factory specs ready to go.
THANK YOU THANK YOU A MILLION times thank you! I can donate to you or XDA via paypal, please let me know how to repay you all! You are wonderful!
No problem. Here to help when I can. If you really feel the need then donate to roebeet (the author of the original instructions).
Have a great day.
K J Rad said:
Start by relaxing and taking a few deep breathes. The instructions there are about as basic as you can get. Main thing istonot get ahead of yourself or read more into it than it says.
I find it easiest to use Linux.
Create a directory to hold the nvflash package.
Extract the nvflash_linux_2010110500.tar.gz archive into the directory.
Extract the nvflash_gtablet_2010110500.zip into the directory.
Put the gtablet into APX mode. From off turn it on while holding the volume down button. You should see the splash screen then it will go black. Plug it into your computer with the USB cable.
Open a terminal window and confirm that your computer can "see" the gtablet by typing "lsusb" command (without the quotes). It should respond with "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
If all is well at this point change into your nvflash directory and type the following command.
./nvflash_gtablet.sh
Now let the magic happen. In a few minutes you'll be back to factory specs ready to go.
Click to expand...
Click to collapse
THANK YOU!!!!! Man, I thought I had a $400 brick on my hands! I couldn't even boot into recovery! I'll donate to whoever I need to at this point!
These machines are incredibly hard to brick. I've tried ;-)
If you'd like to donate pick one of worthy developers from the GTablet Android Development section and support their work. I use Roebeet's TnT Lite and those instructions above were first written and posted by him as well, so...
Glad you got it working. Have a great day!
Ok I've got a generic tablet from Walmart, the DOPO MD-740. It's running ICS 4.0.3. I've been in contact with customer service about this thing, and while they're friendly and courteous, they really don't know anything about their product. According to their lead tech "there is no recovery or download mode".
Headache.
Well fooling around with this device, I've found.... SOMETHING....
While holding the volume up button at the same time as the power button, it boots straight to one single image, shown below. I have a feeling it's the download mode. Whatever it is, it's progress. Can anyone recognize what I got into? It's not a fatal error-- when I hit the reset button and reboot the tablet normally, all is fine.
I've tried to reboot into recovery via adb but I get the message that the command is not allowed. And of course, su is not allowed either.
Anyone have any suggestions on running adb on my computer... what process I would need to follow to manually root an ICS tablet? Would I just follow the same steps as I would in manually rooting a gingerbread device, or is there different lines of code I would need to use for ICS?
As for what device the kernel for THIS device has been ported from (it's obviously emulating something that has a magnometer which this unit doesn't have, etc...)... tech support doesn't know that either. The only clue I have that MIGHT help (other than the kernel version, build number, etc... all this is documented in another post, if anyone cares to take a look) is the FIRST boot image is of the penguin.
I would appreciate ANY feedback/information/advice anyone could offer in progressing with this "adventure"!
Thanks
Well with another twenty minutes of blindly pressing buttons I've found the recovery mode. From the screen displaying the android with the open panel (which I have concluded is NOT the download mode), pressing volume up, back, and power at the same time opens the recovery mode. The recovery is:
Android system recovery <3e>
Recovery system v4.00
No option to apply zip from sd, I guess this is to be expected on a stock device.
hi
in application select usb debug mode
install from unknown sources
connect to pc and run DooMLoRD_v4_ROOT
should work
regards
fred
didn't work.
After adb started successfully, sat for two hours and did nothing.
hi
are you using windows ?
is it reconized by windows ? do you have the drivers installed ?
ich processor use that tablet ?
Yeah I'm running Windows Vista, and my PC does recognize the device when it's connected (says drivers have been installed properly when connected under USB debugging mode, no problem transferring files in USB mode)
It's the ARMv7 processor
The device is recognized as Full ASOP on Rk29sdk
I've run across a new problem, which might actually be the main issue of the WHOLE problem. I was trying to push some files with adb from my laptop and it came to my attention that the driver for my device only acknowledges it as a mass storage device, even when the tablet is NOT mounted for mass storage. SOOOO... I guess I need a driver that will allow me to use adb. Any suggestions?
did you try with the drivers package from sdk ?
yup. Even gone as far as uninstalling the adb and sdk programs I had on my pc, downloading the newest versions and reinstalling. My computer "recognizes" the divice, but only as folders. Even when it's not mounted as mass storage.
STILL having te driver issue. Anyone have any suggestions on how to fnd a driver that will work with adb?
Sent from my Full AOSP on Rk29sdk using XDA
How did I root my “Full AOSP Rk29sdk”-MID 7-inch tablet (Android 4.0.3)
Hi Wingnut79 and others,
I have an Android 4.0.3 Tablet 7 inch, named "Full AOSP Rk29sdk" - and was also eager to root it....
After hours of search, trial and error, I succeeded.
My tablet is now fully rooted, and I can use ROM manager and all the aps for rooted android-devices....
How did I do that ?
I explain it here, in the attachment...
As you can see, my Windows is in the Dutch language, so I nevertheless hope everyone can understand what to do where...
I hope this can help...
Make sure it's not a Chinese Apad!
Make sure it's not a Chinese Apad! If u go on ebay u will see tons of tablets with ics 4.0.3. but the android on it it's a modified and weird version. I doublt it even is ics. One of my friends have it, and he cannot use the App Market, bcuz it said "Device not compatible with Market". Did u successfully downloaded stuff form the Market? If not, that maybe it's a piece of Chinese crap and u should call walmart for a refund.
It downloads apps from Android Market, Getjar, Amazon etc... just fine.
BAUDI--
I will try this later this afternoon, is it going to be an issue that my laptop OS is windows vista?
Mine tablet is a chinese tablet - but it's clearly really Android 4.0.3.
So, I also download and install applications from Playstore /Android Market/ etc.
It has Wifi, Bluetooth, 3G, GPS-AGPS, FM-radio,.... and evrything works really fine.
My sole problem was: no rootaccess (what I didn't understand, because it's "Android Open Source Project"...?)
Wingnut79,
as far as described in the guide I refer to, it works equally well on Vista. Just sometimes a little bit other name or place to find the properties or so - but should not be a problem at all.
I forgot to insist on the need to kill and restart adb after each change. I am not sure its really necessary each time, but I experencied that when I first thought "again nothing", it seemed well to work after "adb kill-server" and then "adb start-server"....
At some steps (I can't remember wich) I even rebooted my PC....
Now, everything works immediately...
So ROM Manager etc. works well, I have SuperUser... etc .
Good luck!
baudi said:
Mine tablet is a chinese tablet - but it's clearly really Android 4.0.3.
So, I also download and install applications from Playstore /Android Market/ etc.
It has Wifi, Bluetooth, 3G, GPS-AGPS, FM-radio,.... and evrything works really fine.
My sole problem was: no rootaccess (what I didn't understand, because it's "Android Open Source Project"...?)
Wingnut79,
as far as described in the guide I refer to, it works equally well on Vista. Just sometimes a little bit other name or place to find the properties or so - but should not be a problem at all.
I forgot to insist on the need to kill and restart adb after each change. I am not sure its really necessary each time, but I experencied that when I first thought "again nothing", it seemed well to work after "adb kill-server" and then "adb start-server"....
At some steps (I can't remember wich) I even rebooted my PC....
Now, everything works immediately...
So ROM Manager etc. works well, I have SuperUser... etc .
Good luck!
Click to expand...
Click to collapse
Just because it says it is 4.0.3 doesn't mean its pure AOSP. Remember that the China gov has its hands into a lot and there are things that they like to install on their devices to monitor the users and then close it up so it can't be changed.
Sent from my Inspire 4G using Tapatalk 2
this app rooted my Full AOSP on rk29sdk
I tryed many ways trying to root my tablet, even unlockroot.exe
I found SuperOneClickv2.3.3 and it found my tablet right off, it said my tablet looks rooted( but I knew it was not) so I let it do the root process, it installed superuser also
SuperOneClickv2.3.3
you may have to temp turn your virus program off, I use avira so I right clicked the task bar icon and unchecked realtime protection
universel root
try the universel root for the version of android you have or of similar tabs
asdera-and said:
try the universel root for the version of android you have or of similar tabs
Click to expand...
Click to collapse
Where can we find this?
Is there a download link?
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
carl1961 said:
I tryed many ways trying to root my tablet, even unlockroot.exe
I found SuperOneClickv2.3.3 and it found my tablet right off, it said my tablet looks rooted( but I knew it was not) so I let it do the root process, it installed superuser also
SuperOneClickv2.3.3
you may have to temp turn your virus program off, I use avira so I right clicked the task bar icon and unchecked realtime protection
Click to expand...
Click to collapse
Hello,
So SuperOneClick did work for you?
What kind of tablet do you have?
What version of Android was it running when you used SuperOneClick?
Thank you,
baudi said:
Hi Wingnut79 and others,
I have an Android 4.0.3 Tablet 7 inch, named "Full AOSP Rk29sdk" - and was also eager to root it....
After hours of search, trial and error, I succeeded.
My tablet is now fully rooted, and I can use ROM manager and all the aps for rooted android-devices....
How did I do that ?
I explain it here, in the attachment...
As you can see, my Windows is in the Dutch language, so I nevertheless hope everyone can understand what to do where...
I hope this can help...
Click to expand...
Click to collapse
I tried this and it worked. I got root on my device thanks alot for the guide.
Now to the real problem. I have two identical devices (rk29sdk). One is not booting and I can't manage to reset it.
My idea is make a full backup of the working device and somehow install it on the other one (the broken).
How can I do that - when I try to connect with adb it says:
Code:
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF device
Then this
Code:
C:\Windows\system32>
C:\Windows\system32>adb backup -apk -shared -all -f /backup/mybackup.ab
adb: unable to connect for backup
So it sees the device but I can't backup?
[edit]Now I connect to the device, the 'adb reboot' command works and the device responds. it's just the backup command that is not working.
Please help
asemore said:
I tried this and it worked. I got root on my device thanks alot for the guide.
Now to the real problem. I have two identical devices (rk29sdk). One is not booting and I can't manage to reset it.
My idea is make a full backup of the working device and somehow install it on the other one (the broken).
How can I do that - when I try to connect with adb it says:
Code:
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF device
Then this
Code:
C:\Windows\system32>
C:\Windows\system32>adb backup -apk -shared -all -f /backup/mybackup.ab
adb: unable to connect for backup
So it sees the device but I can't backup?
[edit]Now I connect to the device, the 'adb reboot' command works and the device responds. it's just the backup command that is not working.
Please help
Click to expand...
Click to collapse
i am not at my computer to post the commands, but you can type the commands to backup your system (or dump it) from a androids term console, you need busybox installed
edit: try this link
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
;;
Sent from my Full AOSP on Rk29sdk using xda premium
---------- Post added at 03:40 AM ---------- Previous post was at 03:25 AM ----------
Beeg Boy said:
Where can we find this?
Is there a download link?
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
Hello,
So SuperOneClick did work for you?
What kind of tablet do you have?
What version of Android was it running when you used SuperOneClick?
Thank you,
Click to expand...
Click to collapse
yes it worked for root, my chinese phone just shows Full AOSP on Rk29sdk
Sent from my Full AOSP on Rk29sdk using xda premium
carl1961 said:
i am not at my computer to post the commands, but you can type the commands to backup your system (or dump it) from a androids term console, you need busybox installed
edit: try this link
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Click to expand...
Click to collapse
The thing is I don't have access on my tablet. It won't boot.
So I can't start an app from the tablet, or maybe I can?
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
iainwith2is said:
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
Click to expand...
Click to collapse
Install the adb/fastboot drivers. Google is your friend
Firstly thank you for your reply.
I have tried your install but it hasn't worked. I can tell I have been following a smilar update route looking at the pictures you uploaded also, although these screen snaps were obviously from a new OS (windows 7 perhaps).
Whats interesting to note however, is that in my device manager the phone is clearly shown twice, at the top as "Android Device", with "Google Nexus ADB Interface" below it and then again further down as "Other Devices" with MTP below with the familiar yellow exclamation mark.
Significant?
You actually don't need debugging mode if you're intending to manually flash the ROM. Debugging mode is only an android setting and you flash the ROM using fastboot which is outside of android.
Also you don't need the SDK.
I would say go to general > sticky roll-up then read my adb and fastboot thread to start
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
If you used the adb and fastboot installer in my thread, did you use the "install system wide" option?
If not, do.
If you did and it did not work, read more of that section as the manual steps are also mentioned, which you'll need to follow.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
He should already have it from my thread. Its just a question whether he used it correctly or whether it doesn't set up the environment variables on xp properly
Yes installed the 15 second install, Y,Y,N, then installed the Clockmod driver.
I'll go back and read it again, guess I must've missed something.
Have you rebooted? Try that. Is still no, you'll need to manually populate the environment variables.
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
iainwith2is said:
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
Click to expand...
Click to collapse
Don't copy and paste it. The text is generic. You must put your text there....then reboot.
this is what I pasted:
;c:\adb_fastboot
?
iainwith2is said:
this is what I pasted:
;c:\adb_fastboot
?
Click to expand...
Click to collapse
Which is generic. Is the folder your adb and fastboot executables are in called c:\adb_fastboot? If you used the installer, it is not.
Where would the installer put them? I've searched my computer for "fastboot" and its found the exe that I put in a folder on my desktop. This looks a similar address to what I changed the path to previously...
Oy vey
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Oy vey
Pardon?
Click to expand...
Click to collapse
OK so my path is broken so I won't be able to run adb commands?
Did you look at the root of c:? C:\adb perhaps? Its all covered in my thread isn't it? Are you reading it or skimming it? You don't even *need* to put it in the path. Its just easier. Please read to the end of the thread
Also, you don't need to run any adb commands
Yes I've scanned c: drive.
I've read and understood what I can, I'm not an expert so I can only compute what I understand.
I have reinstalled the adb setup a few times and I have noticed that it clearly says "0 files copied" after I select the exe files and system wide options.
I have also tried to run the adb and fastboot devices commands in the command window which gives me the aforementioned error messages.
For some reason, these programs are not being installed onto my machine?
Hi,
Had a xperia Z3 (6603) for a few weeks now and looking at going down the root option already tbh. Just aggrivates me the limited access and the fact that apps are quite happily uploading/downloading data by themselves and could share personal info, etc. I keep my pc quite tight security wise and just can't imagine living with my phone being so open.
Spent several days trawling the internet reading up on it but tbh just came accross loads of spam sites offering `one-click` soloution programmes, etc and lots of conflicting information. Got myself more confused than ever with it all. Stumbled accross this forum which tbh seems to have one of the best reputations out there. I understand I'll lose low light camera functions but I can live with that tbh. Use my posh camera for important/work photos anyway.
I'm pretty computer savvy in that I can build websites and do a lot of CAD modelling/rendering, etc inmy spare time but some of the phone terminology is catching me out as all very new to me. Willing to learn though. Want my phone clean and clear so I can build it up as I want it and control everything moving on/off it with something like PDroid.
Can anyone point me in the direction of a `how to` thread/page? Need something step by step that I can't really go wrong with tbh. Any help greatly appreciated.
Right found this thread after a lot of searching. -
http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
Off to do a lot of reading and researching my software number and unlocking bootloader, etc. Hope you guys don't mind some questions if I get stuck? Want to make sure I'm 100% certain on things before go ahead. Don't want to end up with a brick.
Ashamed to say I'm stuck already and it's not with the process of unlocking the bootloader I just can't seem to get the android SDK program I downloaded to pick up or detect the Java JDK I downloaded. Googled it to death and still can't seem to get it to pick up the JDK. 32bit system, windows 7.
SDK installed fine but wont start up and tells me to set up environment variable.
I've put the "JAVA_HOME" in my computer environment variables as described and put the link to "C:\Program Files\Java\jdk1.8.0_25". Still not picking it up though. Also tried a JAVA_HOME and a JDK_HOME with same link to folder and still no joy. It's definately the right path to the JDK. What am I doing wrong as driving me nuts!
As last ditch effort I logged off and logged in as admin and the program fired right up. Something to do with access rights I guess same as my dreamweaver software.
Now busy setting up n downloading updates, etc.
Good luck! I'll be rooting mine tomorrow evening I suspect... after it shows up at my door step
charlatan01 said:
Good luck! I'll be rooting mine tomorrow evening I suspect... after it shows up at my door step
Click to expand...
Click to collapse
Cheers. Steep learning curve for me as whole thing is new to me but chipping away at it bit by bit. Still downloading updates, etc but process itself seems straightforwards enough once got everything in place on computer.
Get bootloader unlocked then start looking at rooting process. Going to take me several evenings of effort n stress to do what someone knowledgable could do in 10 minutes but everyones got to start somewhere. :good:
To really help it sink in.
Write down all your steps from untouched firmware to root access and recovery.
It will help you to better understand the process and help others who are looking to do the same thing, plus it is a valuable tool if you run into any problems and need help
krankdroid said:
To really help it sink in.
Write down all your steps from untouched firmware to root access and recovery.
It will help you to better understand the process and help others who are looking to do the same thing, plus it is a valuable tool if you run into any problems and need help
Click to expand...
Click to collapse
Good advice, thanks for that. Printed out all the processes on paper and went over them all several times. Going to work through ticking off each item and taking photos of phone screen at each stage so got a log of everything entered, etc.
Biggest problem for me is the software tbh. The file sizes are huge and I have satellite broadband setup as live in remote area. Comparable to dial up download speeds. It took and entire day for the SDK programme to fully download.
Having problems connecting to Fastboot. Following the official sony unlock bootloader instructions.
Z3 connected to pc with cable, (holding down volume up button as connected), and blue light on. Next step on proceedure states "Open a command window on your computer and go to the `platform-tools` folder within the Android SDK folder before entering command "fastboot devices".
So what I'm doing is opening a opening a command prompt window through the windows start button and typing in the path to the `platform-tools` folder. Tried entering "C:\Users\John\AppData\Local\Android\Sdk\platform-tools" path in command prompt to get to the correct folder but just not accepting it. Am I missing something?
ianmoonescalpay said:
Having problems connecting to Fastboot. Following the official sony unlock bootloader instructions.
Z3 connected to pc with cable, (holding down volume up button as connected), and blue light on. Next step on proceedure states "Open a command window on your computer and go to the `platform-tools` folder within the Android SDK folder before entering command "fastboot devices".
So what I'm doing is opening a opening a command prompt window through the windows start button and typing in the path to the `platform-tools` folder. Tried entering "C:\Users\John\AppData\Local\Android\Sdk\platform-tools" path in command prompt to get to the correct folder but just not accepting it. Am I missing something?
Click to expand...
Click to collapse
try "cd" at the front of the command to change directories
Or just goto the correct folder and right click whilst holding shift and then choose open command window here
gregbradley said:
try "cd" at the front of the command to change directories
Or just goto the correct folder and right click whilst holding shift and then choose open command window here
Click to expand...
Click to collapse
Thanks got in to it now. `Fastboot` command itself works and lists options, etc but when enter `devices` or `fastboot devices` it doesn't recognise the command. Think I've buggered up somewhere. :/
My suggestion is not to bother with all that sdk,
Just install this
Minimal adb and fastboot
It has enough of the sdk to work with adb and fastboot
Install that, it should goto the directory of your program files
Navigate to it and open the command window there, then try it
You can also install flashtool from flashtool.net run the drivers.exe from the installation directory (In C:\flashtool\drivers) and choose flashmode, fastboot and Z3 drivers. That will ensure you have the correct drivers for the phone
EDIT
the correct command is
fastboot devices
You can also attach the phone turned on and try
adb devices
to see if you get a return, that way you know something is working.....
Tried the flashtool route using this guide - http://www.theandroidsoul.com/unlock-bootloader-sony-xperia-z3/
Installed the drivers, connected device and it brought up the choose device window. Clicked Z3 (66XX) and it says "bootloader unlock not allowed officially" even though on phone menu it says bootlocker allowed - yes
Looks like I cant do it. Hey ho.
Tried it again with the minimal adb and fastboot lin you mentioned. Installed the program and it worked fine and confirmed with an OK. Bizarre!
Phone now says Bootloader unlocked: YES
Onto rooting next. Thanks for the help. Greatly appreciated!:good:
Jeez, Sony provides a complete how to on rooting the phone along with the disclaimer on removed functionality. Look it up.
Sent from my D6603 using XDA Free mobile app
tweker said:
Jeez, Sony provides a complete how to on rooting the phone along with the disclaimer on removed functionality. Look it up.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
As far as understand. Sony provides a way of unlocking your bootloader, using a method where they require your IMEI number and then marks it as having a broken warranty in return for a unlocked bootloader.
That's not a service. That's damage control for companies trying to maximize their profit to not cover some smug bricking their device.
i would however love to learn more about this official grant of superuser access to the Z3.
Do you have a link ?
krankdroid said:
As far as understand. Sony provides a way of unlocking your bootloader, using a method where they require your IMEI number and then marks it as having a broken warranty in return for a unlocked bootloader.
That's not a service. That's damage control for companies trying to maximize their profit to not cover some smug bricking their device.
i would however love to learn more about this official grant of superuser access to the Z3.
Do you have a link ?
Click to expand...
Click to collapse
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Did I miss something, or is there another way to unlock the z3 bl without going down the Sony
route and surrendering your imei number to them?
No
3 day powercuts and big chunk of my roof missing thanks to 120+ mph storm. Joyous. Did manage to go through the root process though which went pretty effortlessly tbh.
Looking at sorting out my PDroid app and putting things back onto my phone, etc. :good:
Hey guys,
Can anyone tell me how to root the Acer Iconia one 7 (b1-750)? It's a new model and I couldn't find anything about rooting it.
Please help!
||FREAKOUT|| said:
Hey guys,
Can anyone tell me how to root the Acer Iconia one 7 (b1-750)? It's a new model and I couldn't find anything about rooting it.
Please help!
Click to expand...
Click to collapse
XDA offer a guide to rooting all devices, you can find it here
Any news? thanks for everything
Hi man, i managed to root my Iconia One 7 (B1-750).
I downloaded and used the tool on this thread http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 i used the T3 Option.
Be carefull when removing the Acer files as i had problems when my device would reboot when it woke from sleep so i suggest to make a backup of them with Titanium befor you remove them.
If you do remove them like me on acident without making a backup look for the stock B1-810 rom which is on xda somewhere and pull the apks from there to your device the files are in the system/app and system/priv-app folders.
Guys, please i need your help, i just tried to use xposed installer but after installing the required files in /system and rebooting my tablets softbricked. Tried to make a factory reset but it stucked at formatting data. I still can access cwm through the software used in this thread : http://forum.xda-developers.com/andr...p-cwm-t2975096
Anyone has an idea how i can fix it :/
Ben Alaya Karim said:
Guys, please i need your help, i just tried to use xposed installer but after installing the required files in /system and rebooting my tablets softbricked. Tried to make a factory reset but it stucked at formatting data. I still can access cwm through the software used in this thread : http://forum.xda-developers.com/andr...p-cwm-t2975096
Anyone has an idea how i can fix it :/
Click to expand...
Click to collapse
I managed to fix it, just performed a factory reset on cwm then on stock recovery and now it works
What ROM did you install afterwards?
Ben Alaya Karim said:
I managed to fix it, just performed a factory reset on cwm then on stock recovery and now it works
Click to expand...
Click to collapse
Sounds good that you guys have been able to root it.
What ROM have you installed afterwards?
My son has this tablet and mainly I am bugged by the fact that apps can not be installed on SD card.
Need help with flash browser, would rooting help?
I have a new Acer Iconia B1-750 and I am trying to use the paid version of Puffin Browser to access a Learning Management System to play elearning modules developed in flash. I have the free version which installed without any problem but when I try to buy the paid version to have a flash browser i get "Unexpected error, please try again later". Has anyone come across this issue or is there a way around it - it doesn't have to be Puffin but I know these modules work with this browser. I have tried dophin and UC browser but they keep giving me a Flash failed to Load error. Would rooting my tablet help me get around this?
Detua said:
Sounds good that you guys have been able to root it.
What ROM have you installed afterwards?
My son has this tablet and mainly I am bugged by the fact that apps can not be installed on SD card.
Click to expand...
Click to collapse
Currently there is no custom rom you can flash and i think there would never be
It's an Intel tablet, the bootloader is locked and unknown so wow
Personally i advice you to not try anything unless someone else did it and it worked ! I remember myself when i tried xposed installer and it didn't work, my tablet was stuck and i really though it was over [Imagine , my savings gone ! ] i will never do it again, it's not like those chienese tablets that when you mess up with them, you just connect it to your pc and flash a rom with sp flashtool.
Hello.
I have a problem with the tablet Acer Iconia one 7 b1-750.
I rooted and then I deleted some applications with root explorer.
But now that the camera does not start, I get a message "Unable to connect the camera."
I have restored the tablet and continues with the same fault, is there any way to reinstall the software factory.
Any solution?
See if someone can help me. Thanks in advance. A Greeting.:good:
U can use Kingo root at ur own risk.
Sent from my GT-I8160 using XDA Premium 4 mobile app
SeanP86 said:
Hi man, i managed to root my Iconia One 7 (B1-750).
I downloaded and used the tool on this thread http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 i used the T3 Option.
Be carefull when removing the Acer files as i had problems when my device would reboot when it woke from sleep so i suggest to make a backup of them with Titanium befor you remove them.
If you do remove them like me on acident without making a backup look for the stock B1-810 rom which is on xda somewhere and pull the apks from there to your device the files are in the system/app and system/priv-app folders.
Click to expand...
Click to collapse
Hello,
I'm trying to root my iconia B1-750 but can't get the adb layer to work, in fact I can't find the right driver, the ones provided by aecr on their website does not install.
Could you please tell me wich driver you used ?
Thanks.
damdam76 said:
Hello,
I'm trying to root my iconia B1-750 but can't get the adb layer to work, in fact I can't find the right driver, the ones provided by aecr on their website does not install.
Could you please tell me wich driver you used ?
Thanks.
Click to expand...
Click to collapse
It's a bit tricky. The device drivers do not include this specific device. I have the exact change you need at home, but here's what you need to do.
Extract the Acer driver files to your HDD.
Browse to the inf folder.
Open the file intc_adb.inf.
Look for the arch your desktop is running, either [Generic.NTx86] for x86 or [Generic.NTamd64] for 64 bit.
Under the section header from the previous step, look for the CPU model. In this case it's "; Intel Baytrail Android".
Open your device manager, find the ADB device in the tree. Right click it and go to the Details tab.
Change the Property drop list to "Hardware IDs". Take note of the values in the list.
Go back to your .inf file you are editing. Find the line that says "%CompositeAdbInterface% = USB_Install, USB\VID_0502&PID_3705&MI_01 ; ADB + MTP"
Update the line with the harware ID's you noted previously.
Save the file.
Now update the driver the usual way and the ADB driver should work fine.
After doing all that I still was not able to get the device rooted (using the T3 option). It stops at the DROIDBOOT screen. If you get past it, post back with how you did it please.
Hi Domito,
Thanks for the answer.
Wih your help, I managed to install the driver.
When I launch the .bat file, the tablet reboots under droidboot, unfortunatly I get these message, them nothing else happens :
Code:
E:installer device ignored
FASTBOOT INIT ...
E:Failed to mount device '/dev/block/sda1' as installer partition using fs_type 'vfat'
E:installer device ignored
E:installer device ignored
E:No valid installer medium found.
FASTBOOT CMD WAITING...
Could not open /sys/devices/virtual/blacklight
Has anybody also experienced this ?
Can you please help ?
Thanks
Hello, I was stucked at the same screen. But there is one solution. When you see this log you will have to open device manager. There will be "android device" or something like that. Then you will have to enter driver update, choose android devices and then acer composite adb driver. After that the CWM will show up at tablet. Sorry for my english.
damdam76 said:
Hi Domito,
Thanks for the answer.
Wih your help, I managed to install the driver.
When I launch the .bat file, the tablet reboots under droidboot, unfortunatly I get these message, them nothing else happens :
Code:
E:installer device ignored
FASTBOOT INIT ...
E:Failed to mount device '/dev/block/sda1' as installer partition using fs_type 'vfat'
E:installer device ignored
E:installer device ignored
E:No valid installer medium found.
FASTBOOT CMD WAITING...
Could not open /sys/devices/virtual/blacklight
Has anybody also experienced this ?
Can you please help ?
Thanks
Click to expand...
Click to collapse
Hi,
i have the same problem.
When I launch the .bat file, the tablet reboots under droidboot, unfortunatly I get these message:,
Code:
E:installer device ignored
FASTBOOT INIT ...
E:Failed to mount device '/dev/block/sda1' as installer partition using fs_type 'vfat'
E:installer device ignored
E:installer device ignored
E:No valid installer medium found.
FASTBOOT CMD WAITING...
Could not open /sys/devices/virtual/blacklight
I think fastboot isn´t install correct but I don´t know how I can install it correctly. After 2 hours I´ver installed the adb driver correctly and I was very happy
And know this problem...
In device manager from PC I see "Android Phone" with an yellow " ! "
Can anybody help me please?
Thanks a lot.
PS: Thanks on the XDA Team for thís very good Forum!!!!! Thanks Thanks Thanks
My friends did not know what to do to end the root of this model?
Acer B1 - 750
why its too hard to update adb driver from acer???
i cant even add the property in my pc with the tutorial.
i hate this.
an universal adb driver will work?
arghhhhhh i hate acer/intel for that.
anybody else has more solutions?
Help with the buck up for the acer b1-750 !!
hi guys ! can you guys please help me up so i can get that a buck up for the ACER B1-750 and as a change i will give you the insttructions to root this tablet as well , wich for sure it work!! pleaaase!!
wwechampion100 said:
Hello.
I have a problem with the tablet Acer Iconia one 7 b1-750.
I rooted and then I deleted some applications with root explorer.
But now that the camera does not start, I get a message "Unable to connect the camera."
I have restored the tablet and continues with the same fault, is there any way to reinstall the software factory.
Any solution?
See if someone can help me. Thanks in advance. A Greeting.:good:
Click to expand...
Click to collapse
I don't know why, but that happens when you remove the korean keyboard. You must reflash the original ROM and then proceed to remove all the bloatware except the korean keyboard.