The purpose of this thread is to work on porting an 4.1.2 AOSP rom for a tegra 3 device over to the OUYA. This is my first attempt at a port, so any warnings/advice moving forward is more then welcome! This thread will be used until we have a tested working build at which time I will post a [ROM] thread for it with clean instructions/documentation. Any builds posted here are to be assumed not working and could potentially brick your device...
I'm using RC-OUYA-1.0.264-r1_ota.zip as base rom
http://forum.xda-developers.com/showthread.php?t=2266629
I switched port rom to liquid smooth 4.1.2 for the TF700 (HTCdemon suggested closer hardware)
http://forum.xda-developers.com/showthread.php?t=1979464
I'm also working on a port rom with the stable tf700t CM10.0 build
http://get.cm/?device=tf700t
For my development environment I am using h311sdr0id's h311s|KITCHEN (ubuntu)
this has the kernel tools needed to pack/unpack boot.img as well as dsixda's android kitchen 0.221
http://forum.xda-developers.com/showthread.php?t=2152398
What I'm working on...
http://forum.xda-developers.com/showthread.php?t=1598713
The basic pieces needed;
A jb(4.1.2) rom made for the device (the OTA zip)
A jb(4.1.2) rom that I want to port (the AOSP zip)
if going from different manufacturer must have same processor (both tegra 3)
Ramdisk wise:
I have merged the AOSP tf700 boot.blobs ramdisk with ouyas OTA ramdisk to make a custom boot.img that "should" boot the AOSP rom.
I have attached the working copy of the merged boot.img in a flash-able zip. This "should" allow the AOSP rom to talk to the kernel. Although it has been tested and is working on stock OTA installs this build is for R&D only!
Update:
With porting just the roms (/system) they all install fine, but get stuck on the boot animation.
With porting with the new boot.img they install, but get stuck on a blank screen before boot animation
Update:
I am also waiting for my bus pirate to come in (mid next week) so I can get console output while booting to see where its crashing at to point me in the right direction.
I got it in and working.. instruction and links on page 6
Hey Professor, ran across some info on wikipedia that might help you out: http://en.wikipedia.org/wiki/Tegra#Tegra_3
Apparently there are 3 different versions of the Tegra 3, and the Ouya uses the latest version, the same as the HTC One X+. You may want to start there instead of the regular X if you haven't already seen this...
I have not, thanks I will take a look. That also has a lot of 4.1.2 roms... I want to stay in android 4.1.2, I now that there were changes to the blue tooth stack in 4.2 that cause the wiimote pairings to break. Not sure if this would effect the ouya controller, but one less thing to worry about.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
It'll also make porting a lot easier since the kernel is 4.1.2 and not 4.2. BTW, if you do get into building from source, I just found they released the Ouya Kernel Source 4 days ago on the Ouya Github.
https://github.com/ouya
CWM error status 6
So I see that status 6 has to do with parsing the updater script. Usually from if you edit the file in wordpad or something. I'm on ubuntu 12.04 andI edited in gedit and am getting this. I even took a look in vim and it looks good to me. Any other clues on what status 6 might mean? Here is a copy of the build I'm try to flash if anyone wants to take a look. I will keep digging online.
!!Warning!! This file may blow up your ouya, I wouldn't flash if I were you... not that you could.... status 6....
Deleted the file... didn't work anyway...
Actually the Ouya is pretty much a TF700T without screen ( aka the Asus Transformer Pad Infinity )
HTCdemon said:
Actually the Ouya is pretty much a TF700T without screen ( aka the Asus Transformer Pad Infinity )
Click to expand...
Click to collapse
Well since I've been spinning my wheels here on this status 6, let me try and port a tf700 rom real quick. I don't expect it to work 100%, just looking for a successful flash and maybe boot!
edit:
well I must be doing something wrong, getting the same status 6 with this one too.
I tried downloading the zip, but I get into some weird Authorize Download loop. Can you post just the updater-script to a pastebin? I ran into status 6 a couple times when I was making the CWM zip.
Sent from my Nexus 7 using xda premium
mybook4 said:
I tried downloading the zip, but I get into some weird Authorize Download loop. Can you post just the updater-script to a pastebin? I ran into status 6 a couple times when I was making the CWM zip.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
http://pastebin.com/CgmYJVQY
I think it has something to do with mounting system.
Im using dsixda's android kitchen to build and sign.
edit:
I get this when building, which I think is causing the issue but I dont see it in the script.
Please ensure these device mount statements are correct:
--------------------------------------------------------------------------
mount("MTD", "system", "/system"); "0 /system/
edit:
I see that theres an option in the kitchen for "Check update-script" it found some errors with the fonts. Pushing the zip now to try the new build.
nope same thing status 6.
When I mounted /system, I did it with
run_program("/sbin/mount","/system");
Click to expand...
Click to collapse
I unmounted it with:
run_program("/sbin/umount","/system");
Click to expand...
Click to collapse
These worked for me. I believe this works because the recovery.fstab defines /system. You could try replacing the mount lines with the lines above.
There's more going on in the script, so it could be something else.
Sent from my Nexus 7 using xda premium
from what I understand it runs line for line until it errors, and since my /system is never formatted I would say the error is probably that line.
edit:
While writing this I took a look in the actual zip rather then the working directory and the kitchen is changing the file!
this is whats in the updater-script after I build the rom.
format("MTD", "system");
mount("MTD", "system", "/system"); "0 /system/
package_extract_dir("system", "/system");
...
...
edit:
looks like one of the default setting in the kitchen says something about update script. When I choose this I only have an "update_script" and no "updater_script"... well its built, giving it a try...
CWM gives a message about the update_script not being supported and to switch to updater_script (which was what I was trying to use)... so there has got to be a setting/option I'm not seeing...
edit:
looks like I have to add the mount point to the edify_defs folder so the kitchen can build for the ouya...
http://forum.xda-developers.com/showthread.php?t=633246
edit:
ok, now the kitchen says;
Please ensure these device mount statements are correct:
--------------------------------------------------------------------------
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system"); "0 /system/
looks good, pushing zip now...
And!... status 6...
at least the updater_script looks correct now;
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p3");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system"); "0 /system/
package_extract_dir("system", "/system");
...
...
edit:
since this has yet to format system, I can always do that manually in CWM. I'm removing the format and seeing if just mount works.
So i'm sitting here right now looking at a liquidsmooth boot animation!
I let it sit for 10 minutes or so, looks like its stuck.
Once it get stuck in the boot loop you have to do the Alt+SysRq+i trick to get back into recovery.
so I went into recovery tried the zip, saw that it mounted and took off, so it did have something to do with format. after it finished I went to mounts menu option in CWM and formatted system cache and data manually and reran the install. reboot and I got the logo I was looking for. So still work to do to get it actull get into the system but a good step forward.
Here is a copy of the liquidsmooth 4.1.2 ouya port [link to original rom in first post] if anyone wants to take a look. The only changes I made to the rom are listed in the first post.
!!WARNING - this build will loop on boot animation, no real reason to flash right now!!
[removed link since it didn't work...]
let me know if this link doesn't work...
So, the to do list:
1. How to get past the boot animation loop (not sure if adb will work at that point... wifi for sure doesnt).
2. Need to work on the updater script to find the working format syntax.
3. Sleep!
You will be mine play store!... o yes, you will be mine....
I do not know if this will help or not but I have a Asus TF700 tablet that has the same tegra t33 processor amd mali gpu as Ouya. Here on xda there are some custom Asus TF700 4.1.2 roms that may be of some help. Check out sbdags CleanRoms based on stock Asus OS.
Well I'm on the same page as you, only not as far down... I followed mybook4's advice on mounting /system, removed the format line and replaced it with:
delete_recursive("/system");
to wipe the system partition, and got my build of CM10 to flash! YAY!!
Nothing... No splash, no bootanimation, no nothing. Adb devices returns:
???????????? No Permissions
So I had to do the same thing, alt+sys req+i, reflash stock firmware. I think it has to do with some missing proprietary files, I used the tf700t proprietary-files.txt but it's not quite good enough I think. I'm trying to find a good tutorial to tell me what exactly I need to extract from the Ouya, the CM porting guide is quite vague...
In other news, did anyone else get an OTA update today? If so I guess I'll be starting over on the OuyaPlus ROM. It's just as well. all the Ouya stuff stopped working after I deodexed it. Universal deodexer my shiny metal... well you know.
Have you tried to pm sbdags, maybe he could clear somethings up. He is very helpful. I do not think he ever sleeps.
One thing I wanted to try was to clear cache and dalvik after it gets stuck. Had that issue a few years back on some old roms. When I booted back up I did not get the boot animation, just a blank screen. So i wonder if something is getting stuck on a "start-up" script.
while at the blank screen or boot animation I cannot adb (usb or wifi via build.prop) to get a logcat going to see what shes stuck on. its in MTP mode while booting...
Also got rid of the init.d stuff just to see what happens.
... still formatting system, data, cache and dalvik on every try.
edit:
no change. Does anyone have any advise on debugging boot up? maybe a verbos boot mode? or logging that can point me at something other than "stuck on boot animation"?
lartomar2002 said:
Have you tried to pm sbdags, maybe he could clear somethings up. He is very helpful. I do not think he ever sleeps.
Click to expand...
Click to collapse
just now
ok, new thought since I don't see any debugging methods for boot or start-up, I'm going to look at running the rom in an android emulator so I can use the emulators terminal to hopefully work out the issue.... back to work...
http://forum.xda-developers.com/showthread.php?t=1599005
just for the hell of it I grabbed the stable TF700t CM10.0 build from http://get.cm/?device=tf700t tried a quick port of that with the same results. I get a really cool CM boot logo to look at though!
edit:
so at least I know its not that specific rom...
I've been following this tut for the porting process
http://forum.xda-developers.com/showthread.php?t=1908008
I think I'm going to try and leave the tf700 system alone and only change the device name in build.prop and edit the updater_script and see what happens.
pushing zip...
every time I flash a zip its like scratching a lottery ticket! come on...!! lol
looks cool!...
Related
Hi chaps,
I've just bought a Galaxy tab with plans to port Meego to the device.
I'm new to all the Android stuff, and tbh the myriad methods for doing this/that/the other and the relative lack of explanation of what's actually being done in these various methods/tools is quite confusing (and worrying).
So, if you'll bear with me, I have a few questions which are probably quite basic.
I've rooted my Tab using SuperOneClick, no problems there, I also understand that there is a leaked flashing tool called (Multi)Odin and an open source flashing tool called Heimdall. I understand adb.
So onto the questions:
Before I start messing about, how should I backup my existing firmware image? I see people talking about taking image dumps using dd, or Odin or Heimdall. What is the preferred method? And how should one then restore the device from these backups?
Alternatively is it possible to simply download the firmware directly from Samsung (I see links to later firmware, but really I'd be happy with what I have currently - P1000XXJK5 and FROYO.XWJJ7)?
I'm assuming that the best installation method would be to replace recovery, then I can add my own kernel and have it boot a rootfs mounted on the external SD card for example. Any thoughts?
I've seen one thread about people compiling their own kernels, with panics and the like which are solved by giving the full path to the initramfs extracted from the existing image. Any clues as to why the built version doesn't work? This is not so important as I can have a look at this when I build the Samsung source.
Is anyone looking at the bootloaders? Is there any information anywhere about them (as changing the bootloader to allow selection of the kernel to be booted would make life easier)?
Thanks for your patience!
Ok, so to partly answer myself, I see www dot samfirmware dot com has links to downloads of firmware images.
I'd really prefer to generate my own image of what's currently on the device rather than trusting a download site, but I guess it's better than nothing. Does anyone know how these images were generated anyway?
lardman said:
Ok, so to partly answer myself, I see www dot samfirmware dot com has links to downloads of firmware images.
I'd really prefer to generate my own image of what's currently on the device rather than trusting a download site, but I guess it's better than nothing. Does anyone know how these images were generated anyway?
Click to expand...
Click to collapse
Samfirmware get their images direct from Samsung insiders. They are not dumps.
If you want to dump from your device search "rotobackup" here in the dev forum.
Sent from my GT-P1000 using Tapatalk
alias_neo said:
Samfirmware get their images direct from Saunaing insiders. They are not dumps.
Click to expand...
Click to collapse
Ok that's reassuring.
alias_neo said:
If you want to dump from your device search "rotobackup" here in the dev forum.
Click to expand...
Click to collapse
Great, just what I was looking for, many thanks
So some more questions:
Any limit to the size of the kernel? Presumably just the size of the partition (which after extracting the image for backup seems to be a pretty large 15.4MB)?
What do all the .rc files in the raminitfs do? They are as follows: fota.rc, init.goldfish.rc, init.rc, init.smdkc110.rc, lpm.rc, recovery.rc
The init.rc is the normal init.rc file, so that's fine. Presumably the recovery.rc file is run if the bootloader detects that recovery mode is wanted (holding down keys during boot). The init.goldfish.rc? I guess this is to do with the emulator, though why it would be in a release image I don't know.
I assume that init.smdkc110.rc is automatically run somewhere along the line, though I don't see where it's started.
Any thoughts on lpm.rc and fota.rc? Are multiple .rc files run for the normal and recovery boots?
Thanks
lpm.rc is for low power mode that displays battery charging animation
goldfish is for running the rom under qemu.
backup your rom using rotobackup. compile samsung's kernel from sources, mix up default initramfs with meego's init scripts. pack all Meego stuff into loop mounted disk image. then flash zImage to kernel and your disk image to factoryfs using heimdall. I assume you have experience hacking N8xx/N900 and Maemo or Meego?
factoryfs is around 300MB so I think it should fit Meego and it (and kernel) can be easily restored with heimdall.
Thanks for the comprehensive reply
Yes I do have experience hacking Maemo/Meego, though have never really had to fiddle with init scripts before and this is as good a reason as any to learn.
I'd actually like to dual boot, so am modifying recovery.rc to bring up the Meego system on the external SD card.
Am just fiddling about building extra kernel modules now (needs btrfs for my image for example) and modifying the recovery.rc file.
Hmm, well I was all set to go and flash my new zImage and was looking for the heimdall command line, when I saw this at the top of one of the threads in this part of the forum (http://forum.xda-developers.com/showthread.php?t=870690):
Restoring to factory after using this process (you need using stock images):
heimdall flash --kernel stockzImage --recovery stockzImage --factoryfs factoryfs.rfs
Click to expand...
Click to collapse
Which has made me worry a bit that I've missed a recovery partition with its own kernel and wrongly assumed that the same kernel is used for both recovery and normal running, just with a different .rc file to be interpreted by init.
Any thoughts?
Do we trust the partition sizes reported here: http://forum.xda-developers.com/showpost.php?p=9471190&postcount=14
They seem very small for the kernel partition. I used RotoHammer's dd method to grab the contents of the partitions as a backup, so am assuming the sizes shown above are not correct (or represent something else?)
Going back to RECOVERY and ZIMAGE partitions - the ZIMAGE partition contains a recovery.rc, the question is really whether, even if they use the same zImage in both the ZIMAGE and RECOVERY partitions, the version in the RECOVERY partition is actually booted if recovery mode is selected (by holding the up volume key, etc.)? OTOH it may be that the RECOVERY partition is either empty or unused, has anyone tested specifically to see whether recovery.rc is run from the ZIMAGE partition?
Well I think I can answer my own question there, I flashed my modified kernel (modified recovery.rc) only to the KERNEL partition, and it boots normally if I don't touch anything, and just gets stuck on the first Samsung screen if I boot in recovery mode.
So it's doing something, I just can't tell what. Not sure if any kernel messages are getting lost behind that image, or perhaps they aren't even output to the framebuffer at all. I seem to remember seeing something about disabling the splashscreen so I'll go and have a look for that. Anyone got any other suggestions?
P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?
I see from the Nexus S port that including adbd in the image seems to be the way to go for early messages, I'll need to generate a new Meego image and have another go later on.
Interesting, I can't see that I've done anything wrong, and my extra init shell script is not started. I am trying to use the "exec" keyword in recovery.rc to start a shell script which will pass control to the Meego rootfs. At the start of my shell script I start adbd (i.e. still within the initramfs), so I should be able to tell if it has started, and it doesn't appear to do so.
Therefore I did some Googling, and I've seen that in some cases the initramfs init does not implement the "exec" keyword (http://forum.samdroid.net/f9/new-init-exec-import-implemented-3280/). This is troublesome for me as it's what I'm trying to use, but at least would explain why I don't seem to leave the init process
I couldn't see the Samsung specific source for init anywhere, has anyone found any? I'm not happy to replace it using the standard Android source as I'm guessing there's code missing which allows the bootloader to tell init how the device was started so that it knows which of the .rc files to run. Has anyone looked into this?
Thanks
Looking at the code in that link it looks pretty straightforward, just a case of parsing the kernel command line (though I might just reverse engineer the existing init first to make sure I'm not missing anything).
Would still be easier to get the actual source code from Samsung, so I've emailed their Open Source group.
lardman said:
P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?
Click to expand...
Click to collapse
I get it with CM
Does CM use a compressed initramfs? I'm using one of those and wondering if it's something to do with the (admittedly small) extra time required to move to init.
I don't have my Tab with me here, could someone post the output of /proc/cmdline please? You'll need to be root. Thanks.
Well it's booting you'll all be glad to hear.
More details to follow, but from memory the following were required:
Custom kernel to add btrfs support (as the image I'm booting is a btrfs partition on the external SD); kernel patch to allow compile-time cmdline to be added to the end of the bootloader cmdline (to enable console=tty0); replace Android init with init script to perform some basic setup then pivot_root to the Meego partition.
Next steps are to get the Meego system running usefully (which includes getting a terminal as currently I just have a login prompt but no way of inputting anything!) and also seeing whether I can get dual booting working with an Android system standard boot and Meego replacing the recovery boot.
Poor pic, but still: http://people.bath.ac.uk/enpsgp/Tab/PICT0040.JPG
Good stuff. Thanks for keeping us informed.
After you've got the groundwork for this done, how easy would it be to get Ubuntu running?
Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
Sent from my GT-P1000 using XDA App
brilldoctor said:
Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
That's using chroot, which I don't want. I want it running natively.
Sent from my Galaxy Tab
Backtrack5/Ubuntu v10.04 Up & Running On Tab 10.1
StatementHave this on my Samsung Galaxy S2 and working perfect so i figured i would give it a try on the Tab 10.1. There were alot of people who helped get this running for other devices i will mention them so dont worry. Alot of modifications had to be made in order to get this to run on the Tab because it was really made for a phone not a tablet so please follow all the steps cause there is certain code that i had to right to get the screen size to fit. Everything is fully functional and working. Finally i think this would be a nice addon to your Tab esp if your a big Ubuntu fan, I am currently working with other developers to see if we can update this so it has the new Ubuntu v11.10 but for now follow the steps and enjoy and if theres any questions or requests just write on the thread and PM me. ENJOY!!!
Disclaimer
I am not responsible for damaged devices, bricked devices, Soft bricked devices, and if you run wrong code ETC
Thanks To:DooMLoRD, anantshri, n1nj4dude, KingOfThaJungle None of this would be possible without these guys and if im missing anyone please let me know and im sorry
Before We StartThere are going to be 10 files attached at the bottom you need to download all 10, place them on your desktop for now i will explain what your going to do with them after. Next you need to download 7Zip heres the link http://www.7-zip.org/download.htmlOk now those 10 files waiting on your desktop extract ONLY 1! i chose to extract bt.7z.001 once you extract you will be given a .img file create a folder called bt and put all ten of the files inside bt including the .img so you now should have a folder on your desktop called bt with 11 files in it. Take this folder and put on the root of your Tab.Now there will also be another file attached called bt5_sgs2_shell_scripts_v2 take this file and put it on the root of your Tab. Reboot into recovery mode and wipe cache and davik cache and then flash that file once complete reboot your Tab.Once your rebooted use some kind of file explorer i used root explorer and check the /sdcard/bt folder for the following it should look like this when you explore it./sdcard/bt/bt/sdcard/bt/bt.img/sdcard/bt/installbt.sh/sdcard/bt/startbt/sdcard/bt/stopbtOnce your verify that the above if correct you can proceed
Instructions On Launching BTStart Terminal Emulator on your Tab and enter the following commands step by step.sucd /sdcard/btsh installbt.shstartbtbtNow your in Back Track 5 shell! You should see [email protected]:
Instructions On Launching VNC ServerDownload VNC Server from the marketThen still in terminal typevncserver -geometry 1280x700You then will be presented with [email protected]: againThen look under it were it says new 'X' desktop is localhost1 that it the last digit in your port number if you ever exit VNC or close terminal or reboot you will have to run some commands to get back witch i will show you in a minute but always look at that localhost # cause it will change if you reboot so pretty much if it says localhost2 your port would be 5902 get it?
Now Launch AndroidVNCEnter the following into AndroidVNCNickname: btPassword: 12345678Address: 127.0.0.1Port: 5901Username: (Leave Blank)Color Format: 24-Bit Color (4bpp)
Getting Back In After RebootType the following commands to get back insustartbtbt
Screenshots & LinksAt Bottom Thank you and Enjoy!!!
Go to this page for the 10 files http://www.mediafire.com/?f9gk3p3t9wip5
Uhm... file bt.7z.001 is corrupted!? Please check. However, thank you.
go onto the original thread and get the files from there sorry i only posted the mirrors heres the link and your welcome hope you enjoy
http://forum.xda-developers.com/showthread.php?t=1331419
Haven't tried yet but looks great, sweet!
works good. nice guide. i suggest people download bt5_sgs2_shell_scripts_v2 from the link in the 3rd post
Cool. Does the wireless "card" in this device support injection?
FillTheVoid said:
Cool. Does the wireless "card" in this device support injection?
Click to expand...
Click to collapse
I would love to know this
Sent from my GT-P7510 using Tapatalk
i believe it does but im not 100% on that
I cannot get this to work. Every time I try to install the bt5_sgs2_shell_scripts or bt5_sgs2_shell_scripts_v2, it says installation aborted. Needs to be Nandroid restored otherwise it won't boot. Any ideas?
So can i use both of honeycomb and ubuntu alternatively or together? Because in screenshots i can still see honeycomb taskbar at bottom over Ubuntu.
Nice work. And how to uninstall it?
Ok for JAYDAWGX7: are you wiping cache and davik cache before flashing and is your cwm up to date? if so and still having problem try a different kernal and get back to me
Ok for PARAG31: yes you can run bolth all backtrack5/ubuntu is doing is running threw vnc you are not loosing honeycomb you still have that as a base platform backtrack/ubuntu is just running threw vnc so to answer your question this does run bolth
I try with two diferents kernels and roms first task650 in paris v5 and other with task650 new honecomb 3.2 stock and no luck to install the zip file in recovery instalation aborted allways display. please post your roms and kernels info to migrate and run this on my gt
celtichazard said:
I try with two diferents kernels and roms first task650 in paris v5 and other with task650 new honecomb 3.2 stock and no luck to install the zip file in recovery instalation aborted allways display. please post your roms and kernels info to migrate and run this on my gt
Click to expand...
Click to collapse
Yep, same problem here. Any ideas? Any one else try this?
P7500 running Overcome 10.1 Rom, with Pershoot Kernel 2.6.36.4, with CWM v5.1.2.3. Yes with wipe of both cache.
EDIT:
After further investigation, the zip file only contains the files found in the bt folder. Just extract it to the /sdcard/bt dir. Assuming that it makes no other changes to system.
Got to [email protected], haven't done the rest yet! Will update post later.
EDIT:
Everything works after this.
Plus, i dont think monitor mode or injection works. Not without modified drivers (STILL HOPING ITS NOT THE CASE). Maybe usb? Hows usb hosting on this? Hope someone can answer these questioms.
I have a compatible wifi adapter, but no usb adapter for the tablet! I'll put it on my buy list.
Will this work on the 3G version also?
Edit: Awesome! It works perfect, thanks! Only remember to have busybox installed guys!
The correct resolution is 1280x752, so it is : "vncserver -geometry 1280×752"
also ur script isnt flashable. only thing in /data is busybox, just install busybox from market and change script
will work on 3g and wifi versions
very nice, also works on GTab 7310 (8.9 Wifi 3g)
heaven, thank you!
Awesome, works like a charm, and it blows everybody's mind.
I spent a little time on try to get capture mode to work, but gave up with the original network drivers.
I hoped it would be possible to use a normal usb wifi stick connected to the adapter, compile the drivers, and load them as modules, but i'm getting error messages when doing that, and that's where my knowledge of linux ends.
Anyone tried this yet? Any pointers? (currently flashing overcome 2.0, will try to post errormsg later)
Also, I read in one of the CarrierIQ threads that one of the pieces of the app actually uses libPcap to snoop on our asses. Would it be any help (or problem) that that's enabled in the parent OS?
Just one question: Can I use bluetooth keyboard/mouse with it? And will TrueCrypt run?
All credit for this find goes to alasdair529.
alasdair529 said:
What I did was, I went into LGPNST and I took the VS910 dll and the original VS910ZV4_04.S4_04.P58008.R5.user.tot
found here:
http://forum.xda-developers.com/show....php?t=1120062
and put my phone in download mode (emergency mode) holding power buttone and volume up
and I flashed it using LGPNST
and Voila my phone is back to normal, no more test mode. My phone is perfect working condition with all usb modes and internet connection working, no more test mode.
Also my phone is back to charging normal. I am so happy I fixed this, I was about to sell it and get something else
honestly there is nothing more to it then that took about 1 minute to set it all up then LGNPST did all the work, very simple, I just don't know why no one else on Google could figure this out or at least post a guide to it if they did, feel free to make a post in the development section, can't wait for mtmichaelson to see this and fix his phone too!
Click to expand...
Click to collapse
I tried to flash v4 or v6, but after that it doesn't boot.
v7, it boots well, but still shows me usb test mode or usb factory mode
weird...
lentm said:
I tried to flash v4 or v6, but after that it doesn't boot.
v7, it boots well, but still shows me usb test mode or usb factory mode
weird...
Click to expand...
Click to collapse
I've had factory cable connected a new USB cable fixed that.
Sent from my VS910 4G using xda premium
I found that fix out also, but I would like to know how to ax test mode without haveing to roll back to Froyo. Because, correct me if I'm wrong, but won't flashing the v7 tot file again just create the test mode issues all over again?
atomD21 said:
I found that fix out also, but I would like to know how to ax test mode without haveing to roll back to Froyo. Because, correct me if I'm wrong, but won't flashing the v7 tot file again just create the test mode issues all over again?
Click to expand...
Click to collapse
Yes it will
Sent from my Dread Ginger Revo using Tapatalk.
Not to dread this up again, but has anyone had any progress on this? Do we know where testmode is being set? Kernal, Radio, ROM...APK?
I would think if it were a bootup setting somewhere, we should be able to do a file or text-in-file search from root up up through the child folders within the core OS. If it were in the APKs, the settings could be in the XML prefs somewhere.. still very searchable.
I have my step-daughters phone stuck in test mode... /=
I dont what to re-create the wheel and spend hours doing stuff that has been done.... so I ask you all this: what do we know so far? Has a simple OS level search in the linux system been done? Is it something in in one of the .rc init files?
It must be somewhere and if we re-root after the TOT, then we should be able to fix this.
Any of the custom ROMs have this if we flash over the TOT? That would rule out APK and ROM settings.
Today I ended up doing a full factory reset, flashed clean V7 tot, then the V8 tot and re-rooted, and finally installed the new breakout rom and I'm still in test mode...
nasaiya said:
Today I ended up doing a full factory reset, flashed clean V7 tot, then the V8 tot and re-rooted, and finally installed the new breakout rom and I'm still in test mode...
Click to expand...
Click to collapse
So this would eliminate ROM and APK.
What are we left with... kernel, radio or recovery partition? Some other hidden partition?
The TOT does a complete re-partition so there must be some hidden key in here somewhere.
I wish I were one of the heavy ROM guys, but I'm just a linux novice and decent developer.
Lets keep brainstorming!
Well I'm just guessing here so bear with me...
AFAIK the cause is flashing in emergency download mode, which is something outside of the normal system, and also outside of the recovery partition. Based on that (and the previous post) I'd guess it set a test mode flag somewhere on another partition that gets "checked" at boot.
I figure we ought to be able to get images of all the partitions with dd but I wouldn't know what to do with that data once I had it... Maybe compare with a non-test-mode phone and look for inconsistancies.
I could be totally wrong though I'm not very familiar with the boot process and that sort of thing.
EDIT: found this: http://wiki.rootzwiki.com/LG_Revolution_Software_Breakdown
Maybe it sets a flag in the MISC partition like it does to boot into recovery or something like that. That stuff is a bit over my head though.
nasaiya said:
Well I'm just guessing here so bear with me...
AFAIK the cause is flashing in emergency download mode, which is something outside of the normal system, and also outside of the recovery partition. Based on that (and the previous post) I'd guess it set a test mode flag somewhere on another partition that gets "checked" at boot.
I figure we ought to be able to get images of all the partitions with dd but I wouldn't know what to do with that data once I had it... Maybe compare with a non-test-mode phone and look for inconsistancies.
I could be totally wrong though I'm not very familiar with the boot process and that sort of thing.
EDIT: found this: http://wiki.rootzwiki.com/LG_Revolution_Software_Breakdown
Maybe it sets a flag in the MISC partition like it does to boot into recovery or something like that. That stuff is a bit over my head though.
Click to expand...
Click to collapse
That's a great find. I'm going to spend some time reviewing that data in hopes that it is something as simple as tweaking one of those partitions.
Sounds good. I'm happy to help with this in any way possible, so let me know if you need anything...
Having to use adb to transfer files all the time is annoying!
I started playing around in the android OS and here are some files I found that ahve "testmode" within them. I tried doing a full system search, but the 'find' keeps stalling/freezing. init.rc has some, what looks like, programmer patch scripts in it that directly affect testmode. What's funny is that each "patch" is labeled by the devs email address! We could probably email the guy to find out how to disable testmode.... (=
# find . -type f -exec grep -l "testmode" {} + 2> /sdcard/err.log
./init.rc
./system/lib/libandroid_runtime.so
./system/lib/libhardware_legacy.so
./system/app/VerizonHiddenMenu.apk
./system/app/Settings.apk
./system/app/LgHiddenMenu.odex
./system/app/LgHiddenMenu.apk
./system/etc/efs.txt
./system/framework/framework.odex
./system/bin/btld
./system/bin/lg_diag_app
./sys/devices/platform/testmode/uevent
./sys/devices/platform/testmode/modalias
I emailed one of the engineers listed in the init.rc file.... MAYBE if we're lucky, he'll help us out.
So far, not looking good. I think he may be thinking I was it disabled in the core, but he doesn't understand that its running actively.
Code:
[B]Eric <[email protected]> Wed, Apr 4, 2012 at 9:13 AM
To: 김세현 <[email protected]>[/B]
[I]Thank you for your response!
Can testmode be disabled in Linux or from Android. Can we dial a code to turn it off?
How can I turn it off? Do you know how or can hint at how to do it?
Thank you again[/I]
[B]김세현 <[email protected]> Wed, Apr 4, 2012 at 9:25 AM
To: Eric <[email protected]>[/B]
[I]Impossible!!
If you are guru, then you can disable it and then it make a brick.
It’s useless job. Why are you trying that?
Give up I suggest. Testmode is lg version of QCT diag cmd set.
BR.[/I]
Guys, test mode is embedded deep inside the kernel source. Disabling it in one place will cause it to not build because it is referenced in another file. Remove it from there and it won't build because of another. Etc., etc., etc. Now what you can try is asking if he knows which partition holds the flag for test mode. It is obviously not /boot, /data, /system/, or /recovery.
Sent from my VS920 4G using Tapatalk
mtmichaelson said:
Guys, test mode is embedded deep inside the kernel source. Disabling it in one place will cause it to not build because it is referenced in another file. Remove it from there and it won't build because of another. Etc., etc., etc. Now what you can try is asking if he knows which partition holds the flag for test mode. It is obviously not /boot, /data, /system/, or /recovery.
Sent from my VS920 4G using Tapatalk
Click to expand...
Click to collapse
Hey mt,
Do we know why emergency mode installed tot's flag testmode whereas regular installed tot's (from cwm recovery or usbmode) dont flag flag testmode? Same tot's same kernel, right?
Is it possible to pull the other mounts images (not /system, /data, etc) and push them to a testmode device?
I don't believe it's tots flashed from emergency mode per se, but rather phones that had bad recoveries installed first, then flashed in emergency mode.
Sent from my VS920 4G using Tapatalk
mtmichaelson said:
I don't believe it's tots flashed from emergency mode per se, but rather phones that had bad recoveries installed first, then flashed in emergency mode.
Sent from my VS920 4G using Tapatalk
Click to expand...
Click to collapse
Agreed.
Now, where is the flag, byte offset, or whatever that is flagging the whole system to be in 'testmode'. If it can be set, it can be unset.
Since /system, /data and /cache are wiped and replaced with a new ROM, then that leaves one of the other.. what (3 or 4) mounted partitions that could contain this flag. Maybe the rootfs contains this flag as a byte offset?
Again, what if a partition from a non-testmode device was exported and pushed to a testmode device? Is there a way to compare these other partitions byte for byte between a good and testmode device?
How I wish I was a linux guru right now.... damn you Microsoft!
I found a program called wxHexEdit that seems about right for the job...
It can compare two binary files / images.
I'm currently having a peek at the MISC partition but I don't have a non-testmode copy to compare it with.
If someone could hook me up with an image (mmcblk0p8) from a non-test-mode phone that would be great!
I got out of test mode easy, just csll verizon and get a new phone.
THIS THREAD IS NOW OUTDATED. Page 17 and on contains information for Ubuntu Touch Saucy port.
NEW THREAD ON THE WAY.
http://forum.xda-developers.com/showthread.php?t=2426924
What works. Wifi+ADB+Touch.
What doesn't work: Sound+Bluetooth. Bluetooth doesn't work yet in Ubuntu Touch, and Sound doesn't work with the Evervolv source. Camera.
Download these files.
http://cdimage.ubuntu.com/ubuntu-to...c-demo/quantal-preinstalled-phablet-armhf.zip Ubuntu Touch RootFS
Recovery Image.
http://gdurl.com/A0mz/download
Put on your SDCARD and install in ClockWorkMod. You know.. when you first turn on the tablet, moboot loads.. you should see a menu for clockwork recovery mod.
EDIT: Oh yeah.. First do a factory reset in recovery mod, THEN install the zip files... The factory reset formats the cm-cache and cm-data partitions.. There are 3 partitions. cm-cache cm-data cm-system. Factory reset formats cache and data.. When you install the first zip, it formats the system partition. Then after that install the RootFS.zip that you downloaded from ubuntu... It extracts the RootFS to the cm-data partition, that you formatted. So it should be clean.
Reboot.
Enjoy!
Oh yeah.. Onscreen Keyboard is not sized right. Seems to be an Ubuntu bug... If your fonts are wrong. .reboot.. check out /system/etc/init.d/90userinit for the stuff I added.
thanks to the usual guys. JCSullins, Evervolv, Tigeris and litz and ompx in ubuntu-touch on irc. The wifi fix was an idea I got while stuck in traffic. Can't believe it worked.
Oh yeah.. THANK YOU DR. MARBLE.
PS. I read somewhere you need at least 600MB of free space, AFTER you copy the files to the sdcard, for the extraction to go well...
nice
Awesome, can't wait to try this out!
How to install that on tp?
Way too cool!! tnx for all the hard work
tux-world said:
How to install that on tp?
Click to expand...
Click to collapse
He says: POST IT SOON. In other words: you have to wait until he finishes the porting.
Crazy how the font turned out like that
Sent from my SAMSUNG-SGH-T989 using xda premium
Great news
SGA, thanks for your effort in bringing Ubuntu touch to Touchpad!
If you need help with testers, let me know
Vistaus said:
He says: POST IT SOON. In other words: you have to wait until he finishes the porting.
Click to expand...
Click to collapse
is this CM?
tux-world said:
is this CM?
Click to expand...
Click to collapse
No. It's Ubuntu Touch, but from what I have heard on XDA Developer T.V. (check 'em out on YouTube) it is based on CyanogenMod.
Sent from my Xperia S ~XZXperience~Unlocked BL~Rooted~6.1.A.2.55~
I'm assuming the install process will be similar to The Nexus line, flash the core system then the phablet zip.
Sent from my Nexus 7 using xda app-developers app
What source did you use to compile? I tried to compile it and kept getting some weird error got frustrated and gave up.
blmvxer said:
I'm assuming the install process will be similar to The Nexus line, flash the core system then the phablet zip.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I think that's how it will always be. The core zip is device specific and contains the CM base while the phablet zip is for all devices.
Off to 3.0.8
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
Going to try a newer kernel to get wifi working. We need Fanotify in the kernel for the network manager to see the wireless. Has to do with proc mounted inside of a chroot and daemons having permission. Sad because once you run ubuntu_chroot shell to get in, you can run iwlist wlan0 scan...
Status Update Complete.
How to compile. Grab evervolv's device folder, but not his vendor folder.. grab hardware/qcom hardware/atheros and the compat-wireless from.. some folder.. forgot the name... I got these from evervolv's ubuntuphone branch for tenderloin.. (the kernel) and his build of android.
Those are the current sources.. May change.. Be sure to change ev.mk file to cm.mk, and change /vender/ev (inside of ev.mk) to /vendor/cm, ev.dependencies file to cm.dependencies....
JCSullins announced he will start work on JB. So that is cool. But.. 3.0.8 Kernel doesn't have working sound or bluetooth. Until someone figures that out with 3.0.8, Ubuntu-Touch and the Touchpad WILL NOT HAVE SOUND. (cough cough nag jcsullins cough cough).. That guy is the man to go to for that.
Backporting Fanotify is not easy. You run into having to change the msm code. (I ran into msm-watchdog.c) So much you might as well just go to 3.0.8.. I have an odd feeling that is someone were to backport it, sound would stop working....
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
Backup you jellybean system folder to a tarball and then extract it somewhere.. Same with the Ubuntu Touch system folder.
(I was about to give up!)
cp -R -f /jellybean/lib/* /system/lib
cp -R -f /ubuntutouch/lib/* /system/lib
cp -R -f /jellybean/etc/firmware/* /system/etc/firmware (my adreno firmware was missing, so this will fix that)
reboot.. and it worked.. merged libraries.
Fonts are not bad all the time..... Going to try this with 3.0.8 tonight.. If someone is bored today, give it a shot. Let us know how it works.
To brunch tenderloin I have to manually create out/host/linux-x86/bin and stick mkimage in there.
go to vender/cm/vendersetup.sh and add add-lunch-combo cm-tenderloin-userdebug.. I think.
there is a mkimage in the ubuntu touch source.. I used that. /system/extras/mkimage.. it needs to be compiled gcc mkimage.c -o mkimage -lz
then copy it cp ./system/extras/mkimage/mkimage ./out/host/linux-x86/bin no idea if this is required.
there are 2 bzr branch commands that need to be run.. google that.. Should be in Ubuntu Porting guide, but it's not. ubuntuappmanager library and some other library.
edit: run this inside of the ubuntu touch source folder/ubuntu
"bzr branch lphablet-extras/libhybris hybris" stupid smiles. =)
"bzr branch lplatform-api platform-api"
http://forum.xda-developers.com/showthread.php?p=38745624
dont forget to run extract-files.sh and get-prebuild, etc.
source build/envsetup.sh
lunch (pick 14)
brunch tenderloin
I bring over ts_srv and that other ts program from jellybean to ubuntu and currently add commands to /system/etc/init.d/90userinit to get stuff running.. Lazy, I am.
Confused? That is my rough draft guide.
A dude by the name of tigeris, or something that started with tig.. he helped me a lot on ubuntu-phone on irc. So did another guy named.. omxy.. I think... I will find them. Gotta go,
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
My wife would really like someone to pick this work up.. She wants me to .. "come back to the family"....
Oh yeah.. Wifi does work.
To get wifi working..
do this.
ubuntu_chroot shell
mount -o proc proc /proc
network manager should now bomb.
this is for open security.
ifconfig wlan0 essid "your essid"
ifconfig wlan0 up
dhcpcd wlan0
dhcpcd taken from jellybean tar.gz from the bin folder.. So.. yeah.. but no network-manager without fanotify and some other daemons. be sure to take dhcpcd stuff from etc.
DONT RUN ubuntu_chroot all by itself.. It will crash.
ALSO you MUST unmount proc before shutting down or it will be stuck in mtab and you will have old stuff inside of the /proc folder, inside of chroot, or rather /data/ubuntu/proc..
Problems? Restore ubuntufs tarball in recovery.
I will release something sometime soon.. after testing 3.0.8.. but if you know how to do all this stuff, be my guest.
Why don't you create your own github and share with us?
I bet that there are a lot of devs who want to continue.
I am really interested but I kind of got lost when you said to get the files from Evervolv... Can you post links to be more specific please?
Thank you.
Its just githib.com/evervolv
Sent from my Touchpad using xda premium
Doing that tonight... By the end of tonight I will release something..
It will be 3 files.
The first will be the .zip file that has the actual /system folder
second is of course from ubuntu and is the rootfs.
Third will be a tarball you guys can extract once the tablet is booted that will just have touch and graphics working. You can use wifi if you run it from adb, and keep the tablet powered on.
I haven't even touched pixel ratio.
Oh.. a 4th file.. of the whole ubuntu touch folder.. cleaned and made proper.. Uploaded to google drive.. Or hell I guess I can look at github...
Gotta play mario with my little girl first.
jshafer817 said:
Gotta play mario with my little girl first.
Click to expand...
Click to collapse
LOL
Gotta always spend time with them :good:
So last night, I was beta testing a ROM. After playing with it for a while, decided to go back to my previous setup and work on something. I rebooted into TWRP, wiped my Dalvik Cache, data, cache, and system partitions, and tried to flash the nandroid of Kinology I had been running before testing the beta ROM. I rebooted... only to discover that my Kindle wouldn't boot past the 2nd bootloader.
I thought, "okay, no biggie, I can fix this. I tried wiping and then flashing a couple of other ROMs I had on my SD card. Didn't work. I rebooted the bootloader and flashed a trio of images I had on my hard drive via fastboot. Nope. I tried sideloading CM10.2. Still nope. I tried mounting USB and pushing a ROM to my SD card and flashing from there. Again, no (anyone noticing a pattern?).
No matter what I do, I can't flash anything or get anything to transfer over to my device.
Help!!
Why do I get the feeling this has something to do with the boot image... Does it ever boot to the point you can logcat? Also I thought I read about some issues restoring nandroid's after the system was using selinux, though I haven't experienced this with mine. You tried cm 11? I know it had full selinux support. If you can't get the logcat to work I think there's a module that gets dumped that you can access in twrp over adb. And of all things to ask, if you flash the ROM in testing back does it still boot? If so that would make me think something weird is going on with the boot image. Also what version of twrp are you using?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Why do I get the feeling this has something to do with the boot image... Does it ever boot to the point you can logcat? Also I thought I read about some issues restoring nandroid's after the system was using selinux, though I haven't experienced this with mine. You tried cm 11? I know it had full selinux support. If you can't get the logcat to work I think there's a module that gets dumped that you can access in twrp over adb. And of all things to ask, if you flash the ROM in testing back does it still boot? If so that would make me think something weird is going on with the boot image. Also what version of twrp are you using?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for answering. "adb logcat" doesn't work. It only shows "-waiting for device-". I tried flashing CM11 this morning, but the install failed. I also tried re-flashing your ROM again this morning, but same result. I've got TWRP 2.6.0.0. I've been meaning to flash the latest one from @Hashcode, but it slips my mind every time I think of it.
Something weird: whenever I push anything to the device over ADB, I push it to the SD card. But when I run "ls /sdcard/" in ADB shell, there's nothing there (even though it says it has been successfully pushed).
EDIT: Okay, I flashed the latest version of TWRP (2.6.3.1). I flashed CM11, and it reported that the flash was sucessful. But when I rebooted... nope.
This is weird... So weird. I'm almost at a loss, have you tried flashing a boot.IMG via fastboot corresponding with whatever ROM you flashed? I know I keep saying I think it's this without any real proof but this is kinda bizarre and if no ROM's are working and all you see is the kindkle logo I would assume that the init.RC scripts never got passed the pvrsrvinit or somewhere around that, possibly even before that since adb isn't working when the device is on the logo. You using adb from windows or Linux?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Ph0enix_216 said:
No matter what I do, I can't flash anything or get anything to transfer over to my device. Help!!
Click to expand...
Click to collapse
After I read this, I decided to try and restore and everything restored just fine *whew*. What I do know is that when ever this situation has come up (and a few people have stated they had this problem) only a complete factory restore fixed the problem. You're gonna have to break out the fastboot cord.
stunts513 said:
This is weird... So weird. I'm almost at a loss, have you tried flashing a boot.IMG via fastboot corresponding with whatever ROM you flashed? I know I keep saying I think it's this without any real proof but this is kinda bizarre and if no ROM's are working and all you see is the kindkle logo I would assume that the init.RC scripts never got passed the pvrsrvinit or somewhere around that, possibly even before that since adb isn't working when the device is on the logo. You using adb from windows or Linux?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
The init.RC scripts are still there, no matter how much I wipe in TWRP. I can see them using TWRPs file explorer. I haven't tried flashing the boot.img, I will try that. As for ADB, I'm using it on Windows 8, of all things.
LinearEquation said:
After I read this, I decided to try and restore and everything restored just fine *whew*. What I do know is that when ever this situation has come up (and a few people have stated they had this problem) only a complete factory restore fixed the problem. You're gonna have to break out the fastboot cord.
Click to expand...
Click to collapse
As I said before, I tried flashing two different sets of images via fastboot. Thanks for the response though. What all did you do in your restore process?
UPDATE
Okay, I tried re-installing CM10.2, and then flashing the boot.img from it via fastboot. Still no dice.
Is there any hope of recovering from this? It's been longer than a year, so I don't think Amazon will simply switch it out under warranty.
Agh, I was going to ask hashcode about it on the irc earlier and I forgot about it because my friend asked me to fix his pc...
Also remind me to slap this phone's spell check. It took me way longer to write the previous statement than it should have.
Edit: he's still in there but I think he's afk right now.
Sent from my LG-P769 using xda app-developers app
Ph0enix_216 said:
As I said before, I tried flashing two different sets of images via fastboot. Thanks for the response though. What all did you do in your restore process?
Click to expand...
Click to collapse
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
LinearEquation said:
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was gonna suggest to flash CM10.2 first and then move up to CM11 because that was the route those with this problem had to go (4.3 then 4.4.) Restoring CM11 right off the bat did not seem to work for some reason. That's why I keep a 4.3 nandroid in TWRP, for just such a case. But I see you tried that.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's weird, because I wiped then tried to restore my Kinology nandroid. Am I looking at an irreparable brick, or do I want to look into investing in a new tablet?
Wait until Monday, think you might get more info on a weekday... I have a theory of something that might fix your kindle but it could potentially hard brick it as well so I don't want to explain it yet until it's a last resort.
Edit: just talked to hashcode, he says to "adb pull /sdcard/ ." your sdcard and wipe internal storage, he also said because of kinology kernel not having selinux that if you want to use it you will have to downgrade twrp first and wipe everything again, you might find it easier to do it after flashing cm11 first. So basically back up the sdcard and wipe everything, check off everything including internal storage then push a Rom and flash it.
Sent from my LG-P769 using xda app-developers app
stunts513 said:
Wait until Monday, think you might get more info on a weekday... I have a theory of something that might fix your kindle but it could potentially hard brick it as well so I don't want to explain it yet until it's a last resort.
Edit: just talked to hashcode, he says to "adb pull /sdcard/ ." your sdcard and wipe internal storage, he also said because of kinology kernel not having selinux that if you want to use it you will have to downgrade twrp first and wipe everything again, you might find it easier to do it after flashing cm11 first. So basically back up the sdcard and wipe everything, check off everything including internal storage then push a Rom and flash it.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Checked everything. Wiped it all. Pushed a ROM via ADB. Not working.
I did some exploring with TWRP's built in file explorer. Despite wiping internal storage, I can still see some things I had on there previously. At the root of my device, however, I can also see this:
Code:
boot
cache
data
dev
efs
etc
license
proc
recovery
res
root
sbin
sdcard
supersu
sys
system
tmp
vendor
default.prop
file_contevts
fstab.bowser
fstab.goldfish
init
init.rc
property_contexts
seapp contexts
sepolicy
ueventd.bowser.rc
ueventd.goldfish.rc
ueventd.rc
I may be mistaken, but isn't that some of Firefox OS's stuff? The init.rc files you were talking about? It all may just mean nothing. Also, all my SD contents seem to be preserved in "/data/media/". I tried flashing CM11 from there as well. The flash was successful, but at boot... nada.
Still, thank you all for trying
Umm sorry I'm a little late to the party... Or funeral(if we cant fix your kindle) I was testing stunt's FireFox OS too and after testing I flashed back to my CM11 back up just fine, why not use the system image restore tool in the development section (minimize error, the tool is 99.9% fool proof) bailed me out multiple times when I thought my kindle was a goner(i know you manually flashed images. But why not try a tool?), and I have a theory... Stunt PMd me instructions on how to get the kindle to pick up/read the SD card I didn't try implementing the code because I'm not that techy but did you try it? What if the solution messed with your internal SD card since Firefox OS and Android Have their differences? Or something went wrong will modifying the commands stunts gave you?
And no...I'm not trying to insult Stunt's work or defame it, nothing is perfect and anything is possible so sorry if my response seems a bit disrespectful to the devs work.
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
I still think this has something to do with selinux... I would know more if you had a serial hookup to the kindles motherboard but I don't even have that, if I had some kernel output it would be useful... Those files you saw that I mentioned aren't Firefox OS specific, they are Linux specific, they are going to always appear there because they are loaded from the initial ram disk in the boot.IMG, since android uses a Linux kernel you have init.rc files and such. Some of those directories are from recovery, the folders that should know appear empty I think are /data, /cache, /system and I can't remember the rest offhand. I will have to ask hashcode about this more tomorrow. I can think of something you might do from fastboot that might fix this but I don't know the specifics and it might wipe the boot loader, which wouldn't necessarily be bad as long as you reflash it before rebooting, but I'd like to avoid my idea because it seems rather risky, anyways I will ask about this tomorrow, so don't look into my concept idea....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
when you said your sdcard contents are preserved, did you mean even after wiping internal storage that the sdcard's contents were still there?
stunts513 said:
when you said your sdcard contents are preserved, did you mean even after wiping internal storage that the sdcard's contents were still there?
Click to expand...
Click to collapse
Correct. Not only are they still there, but I can't seem to add anything to it. Pushing via ADB is successful on the PC end, but if I check the SD card, no change. Also, everything I had before the brick on my SD card is still in "/data/app", if that tells you anything.
Thanks for taking time to they and help me
>>>Sent from my ZTE Valet Z665C<<<
Ph0enix_216 said:
Correct. Not only are they still there, but I can't seem to add anything to it. Pushing via ADB is successful on the PC end, but if I check the SD card, no change. Also, everything I had before the brick on my SD card is still in "/data/app", if that tells you anything.
Thanks for taking time to they and help me
>>>Sent from my ZTE Valet Z665C<<<
Click to expand...
Click to collapse
ok um at this point hashcoed is helping me out and i tink i can fix it but it will be easier if i can msg you on skype or in the irc, whatever works best for ya, because this will involve some trial an error over an adb shell... i would try it on my own but it will involve me backing up quite a bit of data and you already have done that so i thought this might be easier than me formatting my own in the process...
Edit: Ok actaully try this first and see what happens, boot into recovery and run this in an adb shell
Code:
umount /data
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
that should actually format the userdata partition and hopefully fix this. though make sure that the unmount worked first, you don't want to try to format a partition while its mounted.
2nd edit:actually i'm a moron, you don't even need to umount /data, just uncheck it in the mount section, you can tell i'm way to used to normal linux... always a good idea to run mount and double check its not on the list but it shouldn't be.
SUCESS!!!
stunts513 said:
ok um at this point hashcoed is helping me out and i tink i can fix it but it will be easier if i can msg you on skype or in the irc, whatever works best for ya, because this will involve some trial an error over an adb shell... i would try it on my own but it will involve me backing up quite a bit of data and you already have done that so i thought this might be easier than me formatting my own in the process...
Edit: Ok actaully try this first and see what happens, boot into recovery and run this in an adb shell
Code:
umount /data
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
that should actually format the userdata partition and hopefully fix this. though make sure that the unmount worked first, you don't want to try to format a partition while its mounted.
2nd edit:actually i'm a moron, you don't even need to umount /data, just uncheck it in the mount section, you can tell i'm way to used to normal linux... always a good idea to run mount and double check its not on the list but it shouldn't be.
Click to expand...
Click to collapse
SUCESS!!! I did what you said and formated the data partition, and I was able to successfully push CM11 to my Kindle. I flashed it, it reported the flash as successful, and I rebooted.. I was greeted by new CM11 boot animation (right now, it's one of the most beautiful things I've ever seen.
Thank you to everyone who responded to this thread. It's nice to know that there are people nice enough out there to take the time and help someone in need.
Some questions though:
1.) With this SELinux or whatever, can I still switch ROMs as easily as I did before? Or am I now limited to CM11 and such?
2.) What exactly happened? I've never had this happen before, where my /data partition derped out and TWRP wouldn't flash anything.
I'm not to familiar with how selinux works but from we hat I remember I think it was something like this. You had a recovery that I think may have supported selinux but I'm not positive about that. The kinology ROM you had on there had no selinux support in the kernel. My ROM has some selinux support in it since I based it on 4.3, and I have no idea what happened that messed it up after that, all I can tell based on what you had to do to fix it is that the xattributes for selinux were not getting cleared off the partition and for some reason the ROM's that could handle selinux didn't seem to like it either. If you want to run kinology again you may need to downgrade twrp so you can reformat the partition again so it reformats without selinux but I'm a bit confused on this myself, this isn't my best field in computers.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app