Hi i was just looking for some quick clarification if anyone is willing.
Boot into Clockwork Recovery. -DONE
Navigate to "mounts and storage". -DONE
Select "mount USB storage". -DONE
Copy /usr/src/tegratab/boot-custom-kernel.zip to the mounted filesystem. -HOW?
I tried adb push /usr/src/tegratab/boot-custom-kernel.zip /sdcard I dont believe it worked since nothing actually happened. I didnt even get my command line back. Im just waiting though, its been about 10 minutes though, I really dont think anything is happening. Actually it just finished, and now my tab is locked up. After I fix this I hope someone will be able to tell me how to properly install this. Also when I go into the android system then turn on usb storage device and try and drag and drop it says its going to take 3 hours?
I cant seem to figure out how to copy my file to "the mounted filesystem" I dont get a filesystem that I can drag and drop my zip into, I dont see or know of a command to do it through the terminal. So how can I accomplish this?
Thanks!
DKS1282 said:
Hi i was just looking for some quick clarification if anyone is willing.
Boot into Clockwork Recovery. -DONE
Navigate to "mounts and storage". -DONE
Select "mount USB storage". -DONE
Copy /usr/src/tegratab/boot-custom-kernel.zip to the mounted filesystem. -HOW?
Click to expand...
Click to collapse
Need details--
Whose kernel is this? Is it for the gTab? Where was it compiled from (source)? Is it stable? Has it been tested? Why is the guy telling you to copy the zip file onto the internal SD via ClockworkMod when you can do it more easily by other means? Can I have a look at the contents of the zip file?
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
DKS1282 said:
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
Click to expand...
Click to collapse
This kernel better be able to sing and dance for you if it's that big. What the hell is in there? I want to see what's in there now.
DKS1282 said:
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
Click to expand...
Click to collapse
This is why I asked you for the details. A compiled kernel for the gTab, along with the most useful modules, plus the installer program, is about 3MB, max.
The complete Linux kernel source, uncompressed, is around 450MB. Compressed, it is ~100MB. A compressed 1.5GB file would therefore contain a heck of a lot more than just the kernel sources. What were you expecting to happen here? Ram a boat-load of source into the tablet and it should automatically compile and install everything for you?
Actually no... I followed a link and followed directions and I actually thought I was doing well till I saw the size of the file... Im actually going to work on recompiling the kernel again. It was a version of pershoots but I think the tutorial I was working off of is incorrect as are most of them on the net. Im learning but sadly not at the pace I would like, Im new to linux and android. Thank you all for the help so far. I'll post what ive done here in a lil bit and I was wondering if I would be able to get advice on how to install it... Ill even link the tutorial I follow. Here it is http://forum.xda-developers.com/showthread.php?t=916198
Now that Ive gone over it again its an issue in the zipping... For some reason my 28.7M file zips to 1.6gb WTF? Here is the command I used
From inside the file where the contents is to be zipped zip -r /usr/src/tegratab/boot-custom-kernel *
Yes evey time I zip it it comes out to 1.6 gigs. The system file is is pretty small but after its been ziped it actually takes most of the 1.6gb... Could I possible send the meta file, kernel file, and system file? Or maybe someone could tell me how to correctly do this? Ive followed the directions in that link and thought I was getting a legit output but I guess that im not even close.
GOOD NEWS EVERYBODY! I can save you 15% on car insurance...
Actually I was able to figure out what has happened... There were some symlinks that didnt get removed so it grabbed everything in that link and zipped it as well... after I fixed the issue it zipped correctly and I was even able to get it to install... Sadly the prolific driver for the 2303 is still not included even though it shows on the kernel menuconfig as being included, I guess Im going to try again and make it modular and see if I can get the driver file to install that way.. Ill let you know how it goes and also upload and link it if I can get it to work in case someone else wants to grab it and build off it. Im also planning on helping out the forums a little bit...
Thank you again.
DKS1282 said:
Sadly the prolific driver for the 2303 is still not included even though it shows on the kernel menuconfig as being included...
Click to expand...
Click to collapse
Attach the .config (kernel configuration file) so I can look at it.
Does running dmesg on the new kernel show the driver loading/initializing?
Are the /dev/ttyUSB* device files present? Are the permissions for those serial devices correct? I'm not sure what they ought to be, but try making them read+write for all--at least while you are testing things: chmod 666 /dev/ttyUSB* as root.
Here is actually the zipped kernel file. When it compiles it does show the drivers being installed, I just cant get the device to recognize the Prolific cable. Ive tried including them, Ive tried modular, im not sure how to make it work, or if there is something im missing entirely. Thanks again.
http://www.mediafire.com/?nil9bh3spu6sp78
DKS1282 said:
Here is actually the zipped kernel file.
Click to expand...
Click to collapse
The binary is no use to me--I don't have your hardware. The .config file is what I need.
When it compiles it does show the drivers being installed, I just cant get the device to recognize the Prolific cable.
Click to expand...
Click to collapse
The real test is the dmesg output, not whether the driver is being compiled in.
However, I think your problem is that you've compiled the wrong driver. What you need is the driver for "Prolific PL-2301/2302 based cables" which is included by enabling:
config USB_NET_PLUSB
which depends on
config USB_USBNET and
config EXPERIMENTAL
The module will be called plusb.ko, I think.
Sorry for being really uneducated on this. But I can not find any of thoes that you listed in the kernel. Also I cant even find the config file. I know where im targeting it from command line but if I try to move it it says file not found, and if I try and go there visually the file isnt there.
Id love to be able to upload what you want to see, and Id love to be able to add in the items you just suggested. But alas. neither seems possible.
Its honestly odd to me.. Ive been reading a couple different posts on the net that say you install this driver for the Prolific 2303. But not the PL2303.... So why is it included when it doesn't do what its supposed to do? Ive tried a lot of different methods and none of them work. It sucks cause I see people using it. Maybe Its not the kernel and its the android OS? I really have 0 clue at this point and about to just give my resignation at my employment.
The .config file will be present in the kernel's main directory (/usr/src/tegratab/gtab-2632/.config) if you have already built a kernel.
It looks like there are 2 drivers for Prolific hardware in the source tree. One is for host-to-host cables with Prolific chips (which is not enabled by default, and which, I think, is what you want), and the other for a Prolific USB serial port adapter (which is already enabled by default).
To build the module for the first, do a make menuconfig, then select:
Device Drivers > Network device support > USB Network Adapters > Prolific PL-2301/2302 based cables
However, you should verify what you have before you build the module. Do a "lsusb" then check the USB device IDs against the USB ID database in /var/lib/usbutils/usb.ids on a regular Linux machine.
Hints:
0. See pershoot's hints to another user here and further along in the same thread.
1. Make sure that you have downloaded the correct pershoot kernel: froyo or gingerbread.
2. You don't need to include all the modules in your kernel zip file. Just overwrite the kernel proper (zImage), the wireless driver (bcm4329.ko) and then add only the prolific driver module. Otherwise you're just wasting space on the /system partition.
3. Sign the zip file after creating it.
Thank you so much for the attempt.
But my .config file is not located where you have directed me. I checked there before, I could send you a screen shot showing you this.
Thank you for showing me where the driver for the cables where, I would not have checked network adapters looking for USB.... Alas, this has not solved my problem. The cable is still undetected by the OS. Although almost EVERY other usb is detected.
Im really not sure why this wont work. It installs 100% fine I have 0 issues on this, but the Prolific 2303 usb to serial cable will not show up in log cat or anything.. Although when i adb shell and do lsusb I see it and it has a device ID and everything.
Thank you again for the help..
DKS1282 said:
But my .config file is not located where you have directed me.
Click to expand...
Click to collapse
It is created in the kernel's top-level directory (ie. the same directory as the file REPORTING-BUGS) after you do "make menuconfig".
If you still can't find it, do,
find /some/path/ -name .config
after you've finished "make menuconfig". Replace /some/path/ with your kernel source dir (or / to search everything that is mounted).
Alas, this has not solved my problem. The cable is still undetected by the OS. Although almost EVERY other usb is detected.
Click to expand...
Click to collapse
If the driver is built as a module then the kernel will recognize it only after you have loaded the module. Load the correct module first, either plusb.ko or pl2303.ko, depending on your hardware, then check for detection/initialization messages from the module by issuing a "dmesg" command immediately after the "insmod /some/path/driver.ko" command.
Im really not sure why this wont work. It installs 100% fine I have 0 issues on this, but the Prolific 2303 usb to serial cable will not show up in log cat or anything.. Although when i adb shell and do lsusb I see it and it has a device ID and everything.
Click to expand...
Click to collapse
Still lacking details:
1. Did you download the correct kernel--Froyo/GB?
2. Are you sure you're running the new kernel after flashing the zip file?
3. Did you insmod the correct module?
4. What is the USB device ID shown?
5. Did you run dmesg--not logcat--after you insmod'ed the correct module? Can I see that dmesg output?
I can not find a .config file anywhere on this computer. it just does not exist.
Yes I am using a gingerbread version.
Insmod does not install anything for me. Although I installed the modules before even packaging the kernel. Ive verified this by checking in the the correct driver files once installed.
I dont remember the device Id exactly but its something similar to 067b:2303
I didnt run dmesg, honestly, this is way beyond me. I have absolutely no clue what im doing at all... I wasnt even hired for this job.. I was supposed to create an app that will use this specific cable on this specific device, although they did not give me the device able to use the cable... So now I have to figure out how to do this, and im just going to resign and tell them im not a hacker im a developer. Thank you very much for your effort but I am turning in my resignation here now at the end of the day. Thank you again and I'll give you thanks.
You had asked a while back if dev/ttyUSBx has shown, and I did get that to show last night. its dev/ttyUSB0 Ive tried to use a usb to serial api but the app couldn't open the serial port... Im guessing because android does not support that (since they dont really support anything) I personally dont even understand why these things sell... Its a giant useless phone that can not make phone calls. Im in the wrong business I need to sell useless products to consumers.
DKS1282 said:
I can not find a .config file anywhere on this computer. it just does not exist.
Click to expand...
Click to collapse
You a) didn't search correctly, b) haven't built the kernel yet, or, c) done a "make mrproper" and cleaned up.
Yes I am using a gingerbread version.
Click to expand...
Click to collapse
Which ROM?
I dont remember the device Id exactly but its something similar to 067b:2303
Click to expand...
Click to collapse
You cannot be vague about this. Run a Terminal emulator on the gTablet (download one from Market if needed), then type in the command in bold:
Code:
$ [B]lsusb[/B]
Send me the output of lsusb.
I didnt run dmesg,...Thank you very much for your effort but I am turning in my resignation here now at the end of the day.
Click to expand...
Click to collapse
Steady on, mate--we'll get you sorted: Just send me the lsusb output and I'll build a kernel for you--if the current kernel sources include the driver code.
You had asked a while back if dev/ttyUSBx has shown, and I did get that to show last night. its dev/ttyUSB0 Ive tried to use a usb to serial api but the app couldn't open the serial port...
Click to expand...
Click to collapse
Does the app have permissions to read/write the device? Use the chmod command I gave in an earlier post to give permissions.
Next: once the actual hardware is connected to the Prolific cable, is data appearing on /dev/ttyUSB0? Run,
Code:
$ [B]hexdump -C /dev/ttyUSB0[/B]
to see if any data appears.
But, this depends on the device. Some devices need to be triggered, either electrically or by sending commands to the port, before they will send anything back. Other devices will spit data out as soon as power is applied to them.
Which kind is yours?
lsusb returns 067b:2303
My device needs to have data sent to it in order for it to start spitting out data. Otherwise there is nothing happening. It requires a 16bit hex "Start Command". So of course $ hexdump -C /dev/ttyUSB0 returns nothing.
I have the kernel I built here, as well as the gingerbread 2.3.4 rom i am using, and Ive also included the Gaps I needed to install into 2.3.4 to activate the USB feature. (why isnt that feature standard since its really the only difference for 2.3.3 and 2.3.4?
http://www.mediafire.com/?1phzkmvhtr0li
Thank you again.
Honestly you know what would fix all of this... Being able to install windows 7 on this tablet. I know the viewsonic view pad has a dual boot android / windows 7 how cool is that?
DKS1282 said:
lsusb returns 067b:2303
My device needs to have data sent to it in order for it to start spitting out data. Otherwise there is nothing happening. It requires a 16bit hex "Start Command". So of course $ hexdump -C /dev/ttyUSB0 returns nothing.
Click to expand...
Click to collapse
That's assuming that /dev/ttyUSB0 is the correct port, which may not be the case.
Right after the tablet has booted, load both the Prolific kernel modules (or only plusb.ko, if the other is built into the kernel--you still haven't sent me your .config file), attach the Prolific cable to the tablet, then attach the actual device to the cable, then run a
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
command. Attach the dmesg.txt so I can look at it.
Couldnt do it. Lost the job. Thanks anyway.
Related
I am by no means an expert, i just dove into this project 4 days ago, and since then, I've had to reformat my SD card about 8 times before I figured out how to get it stable. But now I have it running pretty stable, there are some issues still, but it at least runs linux pretty well. I'm mainly posting this because this would have saved me a lot of digging 4 days ago, and I figured I would help out any n00bs that just got a lapdock and just started playing with webtop.
*Disclaimer* I am not an expert, if you have a problem with any of these steps, please do not post them here, but in their respective threads. I take no credit for developing any of this, im just posting a list of steps from multiple sources. Also, if you break something, its not my fault*
The Guide
By the end of this guide, you will have a more functional linux as your webtop, with the XFCE4 interface. This uses webtop2sd, so if you break anything, you should be able to start over.
You will need a rooted Atrix, a lapdock (or other external device for using webtop on), and a microSD card, I suggest 2GB or bigger. I have a 32GB PNY class 10 card, for example.
1. Lets format/partition the SD card. Sogarth explains here how to do that. I highly suggest NOT doing this on your phone,and use a PC instead.
http://forum.xda-developers.com/showpost.php?p=15109152&postcount=5
2. Here, he explains how to install it after you partition your SD card. The app you need is in the bottom of the first post.
http://forum.xda-developers.com/showpost.php?p=15109140&postcount=4
3. Now plug it in to your lapdock, and it should boot up into the new webtop. You should see 2 icons in the middle, the awn-dock config tool, and the webtop config tool. We just need to focus on the latter one. Open that up, click on Administration on the left,and click on Install by lxterminal. Try clicking on the terminal icon on the dock, if it comes up, you are gold. If it acts funky, like your screen goes black but doesn't open the terminal, open up the webtop config tool again, and the button to install it should be lit up again. You know its installed if you click install,close out the config tool, and reopen it to see Install grayed out.
4. If all goes well, you should be at a terminal. The first thing we want to do, is fix a really annoying and OS breaking bug, regarding the tzdata package. It seems to be corrupted, so we want to make sure it doesn't get in the way of installing other packages. This issue was the bane of my existence for 3 days.
following these steps, we will fix it
http://forum.xda-developers.com/showpost.php?p=18465066&postcount=3
type this into the terminal to bring up the said file so you can edit it
Code:
sudo leafpad /var/lib/dpkg/info/tzdata.postinst
then put exit 0 on the 3rd empty line
I would reboot your phone after doing this, just for good measure
5. When you get back into the webtop, lets run the Webtop Scripts, the files and instructions are here for that. This will fix many broken dependencies. Arvati did a great job with these fixes!
http://forum.xda-developers.com/showthread.php?t=1192488
just put that file in your downloads folder, then run the commands from that first code box, and I just said yes everytime it asked you what you wanted to do. I would reboot your phone again after this.
6. Now lets start installing stuff! Lets start with synaptic, which works a lot better if you install via command line instead of the webtop config tool.
So run this from the terminal:
Code:
sudo aptitude install synaptic
7. Open up synaptic by typing 'sudo synaptic' into the terminal. Lets install XFCE4 now, just search for that there,and install the XFCE4 package, it should install all of the other required packages to run the new interface.
8. Once it is installed,we need to disable the webtop interface,and enable xfce4. I referenced this thread to do that:
http://forum.xda-developers.com/showthread.php?t=1054213
Type this into the terminal to edit the right file
Code:
sudo leafpad /osh/usr/local/bin/start-oshwt-2.sh
put a # in front of
sfalv -i "awm-autostart"
sfalv -i "webtop-wallpaper"
so it looks like
#sfalv -i "awm-autostart"
#sfalv -i "webtop-wallpaper"
then add these 2 lines
sfalv -i "xfce4-session"
sfalv -i "xfce4-panel"
save it then reboot your phone. Hopefully you should be in XFCE4 now!
OPTIONAL:
*To fix an issue with mounting USB storage devices:
I had the same problem, got it to work by adding this to /etc/PolicyKit/PolicyKit.conf
Code:
<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<match user="myaccountnamehere">
<return result="yes"/>
</match>
</match>
</config>
Click to expand...
Click to collapse
http://www.linuxquestions.org/quest...b-storages-debian-squeeze-723251/#post3537149
* To Fix mounting Windows network shares
Chimpdaddy has posted a way to get Samba file shares to work, this requires having a custom kernel though:
http://forum.xda-developers.com/showpost.php?p=22018703&postcount=67
Chimpdaddy said:
Firstly you need to have a kernal, like Faux's, that supports CIFS.
Then install Samba4, via synaptic package manager if you like.
Probably an idea to reboot.
Then create a folder (using terminal) where you want yr share, 'sudo mkdir /media/SHARE' for eg..
then run this;
sudo mount -t cifs -o username=guest //YOURSHAREIP/SHARE /media/SHARE
if you get no errors yr golden
If you want it to mount on startup edit /etc/fstab to include
//YOURSHAREIP/SHARE /media/SHARE cifs username=guest,_netdev 0 0
check this with 'mount -a'
That should do you.
Click to expand...
Click to collapse
OR
You could use an app like ESFileExplorer on your phone to drag and drop files, this is what I have been using,and it works pretty well for both direct windows shares and FTP. The Mobile View is great for having a window open for secondary tasks like this.
EXPERIMENTAL:
This can be buggy,so use at your own risk!
To install chromium browser, follow these steps. This is said to have better performance than the built in firefox, but for me, it crashed a lot, I went back to firefox
http://forum.xda-developers.com/showthread.php?t=1374567
ISSUES STILL PENDING:
*currently no major issues*
LIST OF SUGGESTED APPS:
OpenOffice.org
Qalculator
XChat IRC
This looks good. I just got my lapdock on Thursday and I have been putting togther all of the Docs to get it the way I want, but this is pretty much the results I wanted. I will try your instructions and get back with you.
Thanks.
Which ROM are you running on?
stock ROM.....
Thanks for the guide.
There is one link that appears to be broken though,
On step 5, the thread goes nowhere. That's where I'm stuck right now
my bad,fixed
i actually managed to do all this on my own, but just recently came into a unexpected problem. i'm kind of a linux noob, and it seems like the file manager button on xfce4-panel doesn't lead to the stock file manager i was using before (doesn't lead to anything), does anyone have any suggestions for a good file manager to replace it with?
Thanks for the fix, I've completed all steps and it was working for about an hour. Until I installed chromium.
I have a weird problem where the lapdock doesn't detect webtop and says no hdmi input detected. Not sure if you know anything about that, but just wanted to let you guys know (might be a defect on my lapdock). I'm trying to figure out a fix for that now.
I would suggest starting over if that happened,sounds like something broke
as for an XFCE4 file manager, it should install Thunar by default
teeth_03 said:
I would suggest starting over if that happened,sounds like something broke
as for an XFCE4 file manager, it should install Thunar by default
Click to expand...
Click to collapse
sudo apt-get thunar fixed the problem for me, thanks though
followed your steps and it works great ,i've been messing with this for over a week trying to get this to work ,that ztdata bug fix did the job.. THANK YOU.....
toe451 said:
followed your steps and it works great ,i've been messing with this for over a week trying to get this to work ,that ztdata bug fix did the job.. THANK YOU.....
Click to expand...
Click to collapse
dont thank me, thank the guy who figured out how to fix it
webtop2sd app crashes on first run...any ideas?
Here's the answer
http://forum.xda-developers.com/showpost.php?p=19993891&postcount=671
bigworm50 said:
webtop2sd app crashes on first run...any ideas?
Click to expand...
Click to collapse
To the point of installing XFCE4, and synaptic just sits on preparing packages forever... I let it sit for 30+ minutes last night and going on almost 60 minutes currently...is something wrong or does it take that long?
you might want to cancel that, reboot your phone and try again, it should not take that long
can you do one on how to install Chrome instead of Firefox for a noob like myself. Thank you.
there is already a link to the chromium browser thread in the OT
I would caution that its kind of experimental, I installed it and it kept on crashing for me, so when I re-did my webtop after that,I just decided to use firefox
For step 1, can we partition this as ext4 as faux kernels support it?
added info on fixing an issue with mounting USB drives, and a note about chrome
Hi guys, I have the Rock Jaw Vi phone which by all sense and purpose seems to be a clone of the HTC One. It's Quad Core with 2 mega pixel camera on the front and 8 mega pixel on the back. The case and all outward appearances are that of the HTC, the phone info screen displays the following ...
Model Number = RJViJGTL32SM
Andoid version 4.2.1
Baseband version = moly.wr8.w1248.md.wg.mp.v6.p8,2013/08/12 15:55
Kernel version 3.4.5 [email protected] #1 Mon Aug 19 16:54:14 CST 2013
Build Number = 0502H026_20130819
I can get into the boot options screen by doing the On/Volume Down press but the menu's are all in Chinese and just seem to go through self diagnostics and tests. I can drag n drop file from Mac OSx but none of the apps I have found so far will communicate with the phone via USB. I am trying to get root so i can do a full back-up and then to try and put HTC Android 4.3 on it.
Do you guys have any idea on how I can achieve this or to get the phone to display it's boot options in English ?
I am pretty much clueless and stuck, any advice, tips, hacks etc would be really appreciated
I did follow a link at one stage on the web that went to SRSroot but their tool was windows only
Hmmm More messing with the phone has revealed power on with volume up depressed gets me to some very small text menu with the options;
Boot Normal
Fastboot
Boot(UART)
Boot UART is all the test screens that I was getting in Chinese but now they are touch screen buttons and labeled in english ao that's good to know.
Using fastboot-mac from HTCRootOne tries to talk to it but comes back with error: could not clear input pipe; result -536854449, is this something that's platform specific, ie it's not a true HTC so the version of fastboot-mac is no good and needing a non specific version ?
Ok that error is generated to the oem get_identifier_token...
If i do a fastboot-mac devices i get the reply "mt6589_phone_720pv2 fastboot" ...
I'm getting there slowly
Done some more digging with the phone attached to the Mac here and checking my systems profile I see that the phone is listed under usb connections as seen in the screen grab, still referring the as a HTC. Getting a new usb cable delivered to see if the phones usb cable provided is for charging only. If anyone here has any other suggestions I would be all ears or eyes as the case might be
Done more grubbing around and have found it to be a HDC One, HTC One clone .... Now to go see if any are rooted on here
Can anyone help me
Well i am pretty much stuck here so if anyone is reading this and wants to offer some help and advice I could do with it
I have looked around on the phone and can't see any bin or system folders even with show hidden i can't find them.
adb wont give me a remote shell, it complains that there is no bin/bash
when i try and do an adb backup i get 0 byte files grrrrr!!
I still need to find a way of getting root
This phone is a tricky beast for a learner - lol
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
gbl08ma said:
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
Click to expand...
Click to collapse
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
tpwuk01 said:
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
Click to expand...
Click to collapse
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
gbl08ma said:
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
Click to expand...
Click to collapse
I already had the phone in usb debug mode. Had to set the phone to use usb as MTP and not mass storage device connection type. Now it allows me to get in to the blighter with adb, fastboot still errors with pipes. That method allows me to get adb shell running and i can get android file transfer .... back to the reading part again
Thanks for the information gbl08ma - if i can find a way to back-up the rom i will share it somewhere
Hmm yummy - lots of interesting things in there .... Forgive my ignorance again please, but if i can create an update.zip file from the shell on the device that compresses all files from \ and all subdirs would that be the same thing as a safe ROM backup ? i wanna be safe before i attempt to root the phone as someone on here has a lower spec version of this phone and says it's a partial brick now.
TpwUK
Rooted
This phone is easily rooted with the motochopper
http://forum.xda-developers.com/showthread.php?p=40747604
Now should I push my luck further and go for the ROM - lol
TpwUK
I believe i own the same mobile
@tpwuk01
I also asked the same here; http://forum.xda-developers.com/showthread.php?t=2180425&page=92
but i was only able to root using frama root app, and it worked like a charm, but thats the only thing i could achieve, dont know but it seems theres no official thread of developement going on for any cloned device, mine runs the MOLY.WR8.W1248.MD.WG.MP.V6.P8 2013/08/12 15:55 Baseband.
After root i just installed some root apps, ads blockers, cant get any recovery to work, (Playing safe actually not to brick this now, since no support yet) but would have appreciated trying out kitkat on it, using antutu to view up specs, its impressive, i got to find out our 13MP camera at the back can do a great job than it currently is we only need to figure out how to change the image compression, the one i stumbled upon online was the blast, the 13MP was great also the flash light was tweaked to be 50X its current brightness, our 1GB application space was increased to 3.5GB, GPS and the rest was also modded to work really great.
Would like to hear any new updates you stumble upon bro.
Still a nice and featured packed device.
I am attempting to build a compatibility file for my Polaroid PMID1000. Unfortunately this old device uses a special touch screen driver I have never found on other devices, and it is using kernel "3.0.8 #139 PREEMPT". I am using an older rom found here: http://www.slatedroid.com/topic/64378-rom-carbonrom-422/ and have success booting on my compatibility file. The issue is the touch screen is not interacting with the OS (there are other issues but I want to tackle this first). The kernel allows me to boot and the android GUI starts up (I can interact with a mouse just fine). Getevent shows me interacting with the screen so touches are being generated, but they are not getting to the GUI. Looking for any help you may want to provide.
Files can all be found here, including a logcat, dmesg, lsmod my compatibility zip as well as the carbon rom and gapps . https://drive.google.com/folderview?id=0B0c1jpaziDZ-S2hoczN0U0FiN3M&usp=sharing
going forward not backward
So I built a new kernel (3.0.101+) and have the gsensor and touch working now. Install the Carbon ROM, the GAPPS and the new compatibility file: PMID1000_carbon.compatibility-v1.zip
The only issue I have is no sound from the speaker, if you plug in a head set the sound is there.... anyone have an idea on this?
Domenic
new script.bin for sound and aokp support
I have updated the file and there is now sound support. I had a typo in my script.bin! I have also included a zip file for aokp_907_unofficial_2013-08-03.
PMID1000_carbon.compatibility-v2.zip
PMID1000_aokp.compatibility-v2.zip
Domenic
the process
domenictroilo said:
I have updated the file and there is now sound support. I had a typo in my script.bin! I have also included a zip file for aokp_907_unofficial_2013-08-03.
PMID1000_carbon.compatibility-v2.zip
PMID1000_aokp.compatibility-v2.zip
Domenic
Click to expand...
Click to collapse
So...I have the PMID1000, but what exactly is the process for this? I plan on using the CarbonROM(most likely). I have the Livesuite software on my pc, and all. I'm just curious as to what steps I need to take to make this thing work well? haha
I apologize for my ignorance,
Jonathan
jonathanhatch88 said:
So...I have the PMID1000, but what exactly is the process for this? I plan on using the CarbonROM(most likely). I have the Livesuite software on my pc, and all. I'm just curious as to what steps I need to take to make this thing work well? haha
I apologize for my ignorance,
Jonathan
Click to expand...
Click to collapse
Firstly remember that all data will be wiped from the tablet, and the camera's will not work; also I would not expect a beginner to attempt this so I will not write up a detailed step-by-step, but an overview of the files and when/how they will be used. Of course you will require a computer and a USB connection to the tablet and the drivers required. I am not certain if Windows Update will find them, so you may need to find them as well.
With all the above in mind lets start (note I am doing this from memory as I do not have the tablet handy):
You need to start by installing cwm (cwm6028-a10-9part-v2.zip) on the tablet. For this you will need a copy of adb.exe, which I have provided as the file adb.zip on my Google Drive which includes the files you need. The tablet will need to have USB Debugging enabled.
Enable USB Storage
Unzip all files in cwm6028-a10-9part-v2.zip and transfer them to the tablet.
Turn off USB Storage
From a command prompt (cmd.exe in windows) change to the directory when you have unzipped adb.zip and run the command 'adb shell' you will get another prompt. Note I have 'quoted' the commands but the quotes are not required when you run the commands.
type 'cd /mnt/sdcard'
type 'ls' and verify the file recovery.img is in this directory and if it is
type 'cat recovery.img > /dev/block/nandg'
once this command has finished type 'echo -en "boot-recovery\0" > /dev/block/nandf; sync; reboot'
The tablet will restart in cwm.
To move around in cwm use the home button to move the selection down and the power button to select.
copy the following files (do NOT unzip them) to the same directory as you put adb.exe.
CARBON-JB-UNOFFICIAL-20130619-1010-907.zip
gapps-jb-20130812-signed.zip
PMID1000_carbon.compatibility-v2.zip
On the tablet choose the option "install zip from sideload"
At the windows command prompt type 'adb sideload CARBON-JB-UNOFFICIAL-20130619-1010-907.zip'
Note you may need to run the command again if your computer has not found the tablet device.
Repeat the above two steps for the other two zip files.
Once completed on the tablet choose the option "wipe data/factory reset" then the option "reboot system now" Note the first reboot of the table will take longer than you would expect, don't worry you will get back to a functional tablet in about 5 minutes. Note the "wipe data/factory reset" is extremely important as you will not get a functional tablet if you skip this step.
Domenic
WOW. Far superior to my half-root/play store work around I was using before.
Thank you! This works really well on my PMID1000. Great instructions too!
I've noticed that with the Carbon ROM I don't have on-screen volume keys. Is that normal, or should I try clearing the cache, and doing another wipe data/factory reset?
I'm going to try the AOKP ROM next.
Thanks again, Domenic! It's hard to find anyone doing any development for these. I guess that means I should upgrade sometime haha
Jonathan
P.S. Any chance you know how I could adjust the internal partition to allow more space for apps?
I have not found a way to get the volume on the bottom screen, these builds do not allow for it.... but you could try an app from the play store, look for status bar volume and you should find something. The one other real issue I have besides the camera not working is the speakers do not disable when you plug in a head phone. It is fine until you want to use it on the bus and don't want to distract anyone.
I am not certain that you can make the app size larger, but you could try to install Link2SD from the playstore. It allows you to move (link) applications to you SD card freeing up space.
PS I am not a real developer, just a bit of a hack to cobble this together...
Hi all,
EDIT
Thanks to techdudester on the second page, getting rid of the malware is now even easier!
Just flash the image he found here with the following procedure and you're good to go!
Instruction:
1. Flash the new ROM.
a. Get the ROM here . (Use this ROM only if you have a Venstar V140D tablet!)
b. Follow the linked tutorial to install the flash software and flash the new ROM on your device with: Phoenix Suit.
Voila, ready!
Enjoy your malware free tablet!
Tips and tricks. (or something...)
Get adb working (needed for all the other tricks down below):
1. Download the Google development tools (sdk) here and install them on your computer. I assume you have windows 7 installed during the rest of this tutorial.
2. Connect your device to your computer and make sure it is installed correctly.
a. Connect your device while its powered on via USB to your pc.
b. Go to Start, right click "My Computer" and select "Properties". Click "Device Manager".
c. Right click the Android device with the exclamation mark and select "Update Driver Software...".
d. Select "Browse my computer for driver software".
e. Select "Let me pick from a list of device drivers on my computer".
f. Keep "Show All Devices" selected and click Next.
g. Click "Have Disk..." and click "Browse..."
h. You can find the drivers in the "SDKInstallLocation"\sdk\extras\google\usb_driver directory and click OK. Replace SDKInstallLocation with the location that you selected during installation of the SDK.
i. Select the "Android ADB Interface" driver from the list and click Next.
j. Confirm installation by clicking on "Yes". Sometimes you also have to click on "Install" if a screen pops up to ask you again if you really want to install the driver...
k. Click "Close".
To use it:
Open a command prompt (in search type "cmd" followed by ENTER) and go to the following directory ""SDKInstallLocation"\sdk\platform-tools".
If you want a backup of your tablets system directory (highly recommended!) use:
"adb pull /system C:\system"
where C:\system is the target location on your local computer where you want the backup of the system directory.
Remove the update package (this doesn't work for updating the tablet, so, useless.)
adb remount
adb shell
cd system/app
rm Update.apk
exit
Remove the unwanted apps (dragonfire.apk etc)
adb remount
adb shell
cd system/preinstall
rm *
exit
If you would like to have your tablet in the correct time zone after factory reset, you will have to adjust the build.prop file.
First you need to get it to your pc so you can edit it:
in the command prompt window and at the same location as in the tutorial above type "adb pull /system/build.prop C:\temp\build.prop".
Just in case, make a copy of the build.prop in Windows Explorer so you always have the original file if something goes wrong.
Now you can edit the build.prop, but DON'T EDIT IT WITH THE WINDOWS NOTEPAD! Use Notepad++ or similar to edit the build.prop.
After you made the changes (and be careful here, you could end up with a tablet that does not want to boot up, solution further down below) you have to upload the file back to your tablet.
in the command prompt type:
adb remount
adb push C:\temp\build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
Don't forget the last line! If you do not chmod the file (set the correct permissions) your tablet will not boot up.
Changes in the build.prop:
Time zone:
Default time zone is "persist.sys.timezone=Europe/London"
you can change this to your locale time zone like "persist.sys.timezone=Europe/Amsterdam" (for the netherlands )
Search the internet for valid time zones.
Change the default language:
The default language is determined by these two values in the build.prop:
persist.sys.language=en
persist.sys.country=US
For dutch change them to:
persist.sys.language=nl
persist.sys.country=NL
and again, search the internet for valid language values.
Higher brightness after factory reset:
Add the following line to the build.prop file (at the top of the file)
ro.ph.def_brightness=225
You pushed the build.prop without changing the permissions:
No problem. Just connect your booting tablet to the PC, install the driver if its not installed correctly like explained in the tutorial, and then change the rights via adb. It's no problem that it's not fully booted!
in a command prompt in the adb directory:
adb remount
adb shell chmod 644 /system/build.prop
adb reboot
If you pushed a wrong non functioning build.prop, just use this method to push the original build.prop (you know, the copy you made ) back to the device (followed by setting the correct permissions of course).
Remove the (in my opinion) irritating boot sound:
adb remount
adb shell
cd system/media
rm boot.wav
exit
rom download
can you provide another way to download the rom file ,i cant seem to get the registration process to work
stevethesignguy865 said:
can you provide another way to download the rom file ,i cant seem to get the registration process to work
Click to expand...
Click to collapse
I have dropped it here. Hope this helps
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
1ce/ said:
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
Click to expand...
Click to collapse
Yes, all applications will be removed. As soon as you configure the tablet again with the same gmail account, it will probably start installing the applications and games automatically, but in game progress will be lost for most (not online) games.
I am re-uploading the file. Will update this post with the link as soon as it finishes
edit: upload finished, get it while its there LINK
BlueFlame said:
edit: upload finished, get it while its there LINK
Click to expand...
Click to collapse
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
1ce/ said:
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
Click to expand...
Click to collapse
Yes, thats correct. Once unpacked it will be around 520 MB.
Good luck!
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Maylar said:
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Click to expand...
Click to collapse
On request. You can find it here. (Adjusted link. Stored on Google Drive)
Thanking you. Very much appreciated.
Thank's for a fantastic procedure... Worked very well.
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Is that the firmware that I provided?
If not, try to download it again.
If so, I think that your tablet has a newer firmware than this one. You could contact the seller of your tablet for the current (latest) firmware for this tablet.
If you get a newer firmware, please share
Image file invalid
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
mcwheelz said:
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
Click to expand...
Click to collapse
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
BlueFlame said:
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
Click to expand...
Click to collapse
Uploaded again! same link (just made it a new version in Google Drive).
Open Firmware failed - possible solution
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Try to put the image file in a directory without special characters (i.e. c:\temp). Worked for me.
wundabua
Te real FIX is In!
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
The REAL answer is actually very quick and easy compared to all these other recommended methods.
In the first place, model V140d image is only used for these infected tablets. The actual model is V11 and once you use the quick restore method I discovered, you will have a malware free V11 model. The whole secret to this method, is the fact that these units were designed to be quickly, automatically and completely restored in less that 5 minutes through the use of their built in micro SD slot.
Imagine that!
If you check your tablet that came new in the box as something other than V140d, the method I used will most probably not work for you.
Anyway, the quick method I discovered, can be seen on my own tech support site. To find it, Google: Just Call Techdude
Then click on the support link at the top of the page on my site and all will be revealed.
techdudester said:
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
Click to expand...
Click to collapse
Hi techdudester,
The combination "pro tech with 25 years in the trenches" and "very complicated "solutions"" sounds a bit strange.
But either way, a THANK YOU is in order!
The ROM you found works on my tablet (flashed yesterday) and so far so good. No popups and no unwanted application downloads!
I will adjust my initial post to incorporate this image.
None of this is my work and all recognition goes to the awesome developers that made this possible, I will link their guides in here with some minor notes for newbies like me that may had some issues trying to unlock and root the Fire Stick (FS) 4K
DISCLAIMER: BE WARNED THAT YOU HAVE TO OPEN YOUR FIRE STICK AND IT WILL VOID YOUR WARRANTY, THIS IS NOT FOR THE FAINT OF HEART AND NEITHER THE DEVELOPERS OR MYSELF ARE RESPONSIBLE IF YOU BRICK YOUR DEVICE OR VOID YOUR WARRANTY
Ok, now let's begin:
UPDATE: Per Sus_i, this makes perfect sense:
"Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen)."
First very important, I wish I would have known this before but make sure you have a Laptop and a Monitor to Connect the FS to, so basically the USB Power cable from the FS connect it to your laptop and connect the HDMI portion to a monitor or TV
I also strongly recommend to have your FS deregistered before continuing as this will prevent your FS from automatically updating after rooting
In order to unlock the bootloader follow "THIS GUIDE"
I made a quick video on how to open your device and how to Short it using Aluminum Foil:
https://www.youtube.com/watch?v=h4I6ifBLWJ4
Process is pretty self explanitory, make a USB ISO from the image provided on that thread, boot into it and open terminal, make sure you put the file he provides on a RW location, my mistake was that I put it inside a RO folder and it would not load the script, so I mounted the kamakiri-mantis-v1.2.zip unto the /mnt directory of the usb and I was able to run the script successfully, make sure to run the commands quickly as the first time that I it finished the ./bootrom-step.sh script and I left it sitting for 10 minutes to grab a bite, I couldn't run the second script and had to start all over. After the second ./fastboot-step.sh script, your device will be on the TWRP recovery, now on the same terminal page or a new one enter these commands:
Code:
adb devices
adb shell
exit
You should see your device's serial number from the first command with "device" to the right of it and the second command will basically put you inside the device's directory assuming you have established a successful connection. The last command just put you back to your starting point, now open the firefox browser on the FireOS USB and navigate to the URL below
Download the Pre-Rooted Image from "HERE" This image contains Magisk already so you don't have to worry about installing it separately, the image is larger than the available partition on this USB so this is a good time to either get a second USB or if you want to download the file to your local hdd and pull them from there its up to you, then run these commands:
Code:
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
This basically installs the pre-rooted image to your device, after the last command, you should see on your monitor the Fire Stick Reboot and boot to the Amazon GUI Splash Screen, now very important if you followed my previous instructions of deregistering your device before performing all these steps, it should bring you up to the Amazon Initial Setup Screen, now what you want to do is do the following commands before continuing on terminal:
Code:
adb devices *you should see something your screen where the FS is connected to, click accept or enter can't remember*
Now it should show you in terminal your serial number and "device" next to it, meaning you can run adb commands in which you will run the following to disable OTA updates:
Code:
adb shell
su *after this command you should see something again on your screen, click the check the box "Always Remember" and click ok" *
if "su" was successful, you should see something like this:
mantis:/ $ su
mantis:/ # *the hash means you're running as root, if you don't have a "#" you are not running as root"
Than continue with these commands and should get the following results:
pm disable com.amazon.tv.forcedotaupdater.v2
***Package com.amazon.tv.forcedotaupdater.v2 new state: disabled***
pm disable com.amazon.device.software.ota
***Package om.amazon.device.software.ota new state: disabled***
pm disable com.amazon.device.software.ota.override
***Package com.amazon.device.software.ota.override new state: disabled***
After running all these commands exit adb and continue with the normal Amazon Setup including adding your amazon account. After you get to the screen where you can see all the apps, open a new web page browser in firefox and download "This Add-On" , this one is less than 200MB so it should fit on the Fire OS USB, so I would download it and copy it to /mnt for ease of access, go back to terminal and type this:
Code:
adb devices
adb push <your download location you decided earlier here>/AFTV-MM-1.7-6.2.6.8.zip/ sdcard/
adb reboot recovery *it will boot into TWRP*
adb shell
twrp install /sdcard/AFTV-MM-1.7-6.2.6.8.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
Your device will reboot and if everything went smoothly, you should have a rooted amazon fire stick 4k, Congrats :good:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Edit: S̵i̵n̵c̵e̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵ ̵c̵a̵n̵'̵t̵ ̵b̵e̵ ̵p̵a̵t̵c̵h̵e̵d̵,̵ ̵i̵t̵'̵s̵ ̵i̵n̵ ̵m̵y̵ ̵o̵p̵i̵n̵i̵o̵n̵ ̵t̵h̵e̵ ̵b̵e̵s̵t̵ ̵t̵o̵ ̵d̵o̵ ̵t̵h̵e̵ ̵s̵e̵t̵u̵p̵ ̵a̵t̵ ̵t̵h̵e̵ ̵b̵e̵g̵i̵n̵n̵i̵n̵g̵,̵ ̵p̵a̵i̵r̵ ̵t̵h̵e̵ ̵r̵e̵m̵o̵t̵e̵,̵ ̵t̵h̵e̵n̵ ̵u̵p̵d̵a̵t̵e̵ ̵t̵o̵ ̵t̵h̵e̵ ̵l̵a̵t̵e̵s̵t̵ ̵o̵v̵e̵r̵ ̵f̵i̵r̵e̵O̵S̵.̵ ̵T̵h̵a̵t̵ ̵w̵a̵y̵ ̵y̵o̵u̵ ̵a̵v̵o̵i̵d̵ ̵a̵ ̵p̵e̵n̵d̵i̵n̵g̵ ̵u̵p̵d̵a̵t̵e̵ ̵n̵a̵g̵ ̵s̵e̵t̵u̵p̵ ̵s̵c̵r̵e̵e̵n̵ ̵a̵f̵t̵e̵r̵ ̵d̵o̵i̵n̵g̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵.̵ ̵T̵h̵e̵n̵ ̵e̵n̵a̵b̵l̵e̵ ̵A̵D̵B̵ ̵a̵n̵d̵ ̵u̵n̵k̵n̵o̵w̵n̵ ̵s̵o̵u̵r̵c̵e̵s̵.̵ ̵ After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Edit: Update: meanwhile, the fix for the mentioned 'contact manufacturer' error is known...
Take a look here and here.
Edit/Update: Due to efuses (blocking the bootrom access), it isn't recommended to do any update infront of the unlock...
Sus_i said:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Click to expand...
Click to collapse
Ops Typo let me edit it, I meant to put 6.2.6.8 on the command lol, and aaaa I see I didn't know the exploit couldn't be patched great info, so than yes I will revise my instructions thank so much
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
nandroidint said:
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
Click to expand...
Click to collapse
No. If I remember correct, it has something to do with flashing, i.e. the vendor partition wasn't flashed propperly.
Maybe you flashed not the prerooted!? With the Kamakiri TWRP version is flashing full ota update packages (renamed to zip) also possible... and in the prerooted thread is such a full 6.2.6.8 ota linked.
Edit: Could be that this error is prime video related, idk. rbox said he looks into it soon...
Just for clarification: The prerooted rom is a perfect thing since years.
My suggestion 'avoid any rom flashing' from my last post is just an attempt to keep it simple for beginners.
By the way, if the stick gets all updates in front of the unlock, it makes no sense to update it after the unlock again (unless addon.d support is needed).
I hope that has become clear I very much appreciate all the prerooted stuff
thanx for the tut nandroidint this is exactly what I needed, I wasn't sure how to do the shorting so the video helped out a lot now I'm ready to do this. But I'm sorta a noob when it comes to android so I got few questions tho, 1) what are the main benefits in rooting the fIrestick 4K 2) are there different roms to install? 3) are there root only .apks? 4)also one main thing I would like to be able to do is spoofing the Mac address any idea if that's possible?
5)Oh and lastly what OTB cable do you recommend? sorry for all the questions ?
'std::bad_alloc'
After running the adb push of the manthis.zip Im getting terminate called after throwing an instance of 'std::bad_alloc'.... What Im I doing wrong?
i gave root can i remove amazon services
i dont want google launcher jsut remove services
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable ?
Can I please get some support guys ? previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
davinci2798 said:
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
Click to expand...
Click to collapse
Did you deregister before rooting like the tut says? This is why I’ve been hesitant on rooting because of the lack of support on this forum
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
tsynik said:
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
Click to expand...
Click to collapse
Nice! That’s awesome thanx for the info and reply.
davinci2798 said:
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
Click to expand...
Click to collapse
Hey so have you figured out what was the problem yet? If so could u explain how you managed to fix it? I’m going to root sometime this week and would hate to run into this issue.
USB drive for storage
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
Yes, You can use a USB drive for App loading and Movie storage.
See Troypoint.com for good video.
I suggest a single USB OTG Cable and a USB HUB for your drive.
Then you can add a Keyboard and Mouse which make it MUCH easier to type commands.
Good Luck
How might one do this on a Mac?
Thanks
gogorman said:
How might one do this on a Mac?
Thanks
Click to expand...
Click to collapse
Do what? The only thing u can do on the MacOS is to create the bootable iso usb, you can follow these steps to do so https://www.google.com/amp/s/www.le...-on-an-apple-mac-os-x-from-an-iso?hs_amp=true
After your create the bootable usb just reboot and hold down option and select the bootable usb, once in open up Firefox and download the kamakiri-mantis-v1 and open a terminal window and change the directory to where u have the kamakiri folder, in terminal type cd then just drop in the kamakiri and hit enter. From there u can just follow the tut, FYI the bootable usb you create is a Linux OS so that’s how you can do it on a Mac, you just can’t do the rooting on MacOS, just clarifying Incase that was your question.
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Step by step instructions would be great?
chinkster said:
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
RPM99 said:
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
Click to expand...
Click to collapse
The link he provided explains all that https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459 all except for when to connect to the tv, but I assume it’s after running the kamakiri script, btw it’s not software, you just download the kamakiri mantis while in the Linux usb os, open a terminal and change the directory of the terminal to the kamakiri folder in order to run the ./bootrom-step.sh and ./fastboot-step.sh commands
Edit: just follow the main guide from the link above then read this guide after, that’s the best way to understand it.