Related
If you are looking for how to get back to stock Bell, go HERE.
Disclaimer: I have not tested this on anything but my phone. This is a development section of a hacking website. Make backups. Know what you are doing.
Credits:
Brut.all for apktool
edgan for 2nd-init
designgears for aroot inspiration.
xda for being a source of info.
Requirements:
Windows 7 or Ubuntu 10.10+ (10.10 and 11.04 tested)
Java installed. (For applymods, it uses apktool)
Running Phone, not in recovery mode, etc.
Tips:
Don't factory reset please if something goes wrong, it just erases your personal settings, it doesn't write to the system partition. It also deletes your data partition, making it harder to get back to stock.
Early usb mode, turn your phone on while holding down the lower volume button, when it says fastboot, release and press volume down repeatedly until it says early usb enumeration, then press up volume. It takes 30 seconds or so before adb is ready.
Version 9:
Download it here.
What's new:
Added support for 2nd-int (WIP, tested on stock Bell only)
shsu updated to allow a super user to become a super user, acts like sh in that case.
fixed linux install_recovery.sh and uninstall_recovery.sh scripts to use shsu instead of remaining using su. Ditto with ApplyMods.sh
Boot animation now smaller, using jpegs instead of png files, no difference in appearance.
Version 8:
Download it here.
What's new:
Added full phone backup and full restore phone options to the menu. It will download a backup if there is none found.
root script more universal, tries psneuter first, then gingerbreak.
Early usb recovery updated, now uses a tmpfs for system, also mounts /sdcard and /sdcard-ext.
Deodexed French 2.1.1 files incorporated.
Misc fixes
Version 7:
What's new:
New Menu script for windows and linux in the top folder, double click Menu and enter options.
ApplyMods and other scripts updated to use /data/local/tmp/system, this means I can update system.tar.gz and add folders to be copied into system.
Early USB enumeration recovery option. (experimental but useful as is)
Fixed bugs in windows scripts. Can't get user input from bat file while in a parenthesis block apparently.
Bloat backed up to sdcard now
root and unroot scripts updated with more prompts for rebooting phone.
Version 6:
What's new:
Support for Telstra 1.4.2.
ApplyMods can create signed update.zips now, Create_update.bat updated. both using basic ready made scripts in main bin folder instead of creating them on the fly, CR LF issues.
Updated root and unroot scripts, more fool proofing, has to be Bell stock firmware (psneuter doesn't work on telstra).
Includes basic boot animation, and mod for Bell apn on telstra firmware. (Have to reset to default under access point names in settings.)
transparent status bar, yellow tinted white for text color, matches front buttons somewhat.
Version 5.1:
Features:
Works under Linux and Windows 7
Includes root and no ads scripts
Patch system for applying modifications.
What's new:
New scripts for doing mods, fixes issues with patch 9 images.
Updated root and unroot scripts, more fool proofing.
New RestoreSystemPartition script
Custom apktool for more [hopefully] bug free installations.
How to use:
Extract archive, keeping folder structure intact.
run a command prompt/terminal (There is a link to one in the windows folder)
run root.bat or root.sh from the linux or windows folders, depending on which one you are using.
Turn the phone off after that is done and turn it back on again.
The rest of the scripts shouldn't be run with psneuter affecting the phone.
run ApplyMods.bat (.sh) [OPTIONAL] This applies webtop hack and translucent status bar, translucent notification drop down, etc. Select update system.tar.gz.
run install_bell_deodex.bat or .sh
System image of stock Bell.
Mirror of above
Cheers!
Very nice! Looks good!
Will try this when I get home
Sent from my Motorola Olympus
So what is the benefit of this? Will I be able to theme my device with some of the themes that are available? Or should I play it safe and wait for a bell. Sbf to leak before I try anything and brick my phone again lol thanks in advance
EDIT: i see that you have included soft_brick.bat is it the same as this one http://forum.xda-developers.com/showthread.php?t=982859 because that one did not work for me thanks again
Sent from my MB860 using XDA Premium App
cool, i'll try this tomorrow when i don't still have a ****load to do and only 5 hours to sleep
nice to see a Bell dev here!
Also I just wanted to say major props for the crazy awesome idea of doing over-the-air download and installation. Really smart and original.
Atrices, just so you know
NFHimself said:
Hi,
(What is the plural of Atrix?)
Click to expand...
Click to collapse
Can I run this on my mac? Sorry relatively new to adb
Sent from my Motorola Olympus
you could run it on a mac, just had to edit the script a bit.
Hi,
So what is the benefit of this? Will I be able to theme my device with some of the themes that are available? Or should I play it safe and wait for a bell. Sbf to leak before I try anything and brick my phone again lol thanks in advance
Click to expand...
Click to collapse
I wouldn't try theming with ATT files, I would take what was done to them and apply them myself to the deodexed files here. There may or may not be differences that are not obvious. I am never really sure if there is any benefit to this stuff, it's fun to do, about it.
EDIT: i see that you have included soft_brick.bat is it the same as this one http://forum.xda-developers.com/showthread.php?t=982859 because that one did not work for me thanks again
Click to expand...
Click to collapse
The soft_brick.bat script is specific to the folders I am using for transferring data to /system/app and /system/framework. It tries to get root via psneuter, mounts system read write, deletes dalvik-cache files, and tries to copy the files already on the phone to the right folders. It could be that just one file caused the phone to crash mid copy and copying it again will fix things. This avoids trying to do a usb data transfer of all the files which you don't have time to do otherwise. I was also thinking that install-recovery.sh would be a good place to do this, (and then clobber it later with the init.d hack) but I couldn't find setprop and I wasn't in need enough to select a file to use as a semaphore.
Can I run this on my mac? Sorry relatively new to adb
Click to expand...
Click to collapse
It would be easier to do it all from a sh script really, and that would likely be more compatible with a Mac.
Also I just wanted to say major props for the crazy awesome idea of doing over-the-air download and installation. Really smart and original.
Click to expand...
Click to collapse
Thanks!
Cheers!
maledyris said:
Atrices, just so you know
Click to expand...
Click to collapse
Thanks, a lot, really, 10 chars..
How do I recover from a softbrick from this? Thanks.
Before anything is done, all the files are extracted to /data/local/tmp/app and /data/local/tmp/framework. If you run into problems put the phone into fastboot/early usb enumeration mode (see here) and run soft_brick.bat (.sh for linux)
Quote:
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
This is the message I get when i run the batch file.
This is of course when invoking Early USB Enumeration.
Wait for the count down to finish ...
'TIMEOUT' is not recognized as an internal or external command,
operable program or batch file.
clearing Dalvik cache..
rm failed for /data/dalvik-cache/[email protected]*.dex, No such file or directory
rm failed for /data/dalvik-cache/[email protected]*.dex, No such file or director
y
rm failed for /data/dalvik-cache/[email protected]*.odex, No such file or directory
rm failed for /data/dalvik-cache/[email protected]*.odex, No such file or directo
ry
reinstalling apps
cp: cannot stat '/data/local/tmp/app/*': No such file or directory
reinstalling framework..
cp: cannot stat '/data/local/tmp/framework/*': No such file or directory
done.
The timeout message means you are running a version of windows without timeout, see adeo thread.
The lines for rm just mean there are no files to delete in the Dalvik-cache, which is normal, you should see that the second time around.
The cp lines are saying that there are no files in /data/local/tmp/app (/framework).
So, that's unusual, in order to get soft bricked using my script you would to have copied files from /data/local/tmp to /system, and if you are bricked would be unable to delete the files afterword.
sequence:
cd /system
cp /data/local/tmp/app/* app/
sync
reboot now
**brick**
So, how are the /data/local/tmp/app files being deleted?
No clue. I'm not sure what to do here? Is my phone permanently bricked? Any other way to recover from this? The one thing that could have gone wrong is I tried installing from my behind my works firewall. Maybe I could not download the proper files.
No, you are soft bricked, you only made a change (that I know of) in system files.
Were you rooted before you tried this?
If you copy the soft_brick.bat files and change the last line to be adb.exe shell ls -R /data/local/tmp, what do you get?
Basically, it sounds like to need to get the files copied over to data/local/tmp, how they are missing/inaccessible is odd. So, create a script to copy the files over bit by bit, might take a while but it should be able to be done.
EDIT:
Do this:
from command prompt:
adb.exe shell ./data/local/tmp/psneuter
wait a few seconds
type this:
adb shell ls -l -R /data/local/tmp
if psneuter fails, it isn't in /data/local/tmp, which is also odd.
I was rooted before this. So I should attempt all these commands while Early USB Enumeration right? That doesn't give me much time Lol.
OK, here's the output.
C:\bell_deodex>adb.exe shell ./data/local/tmp/psneuter
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
property service neutered.
killing adbd. (should restart in a second or two)
C:\bell_deodex>adb shell ls -l -R /data/local/tmp
/data/local/tmp:
-rwxr-xr-x root root 585731 2011-01-09 02:02 psneuter
-rw-r--r-- mot_tcmd mot_tcmd 4 2011-03-30 21:00 ap_tcmd.pid
C:\bell_deodex>^A
And sorry to be a pain. How would I create the script? What are the files that need to be copied? Are they included in your script?
Okay, so this is a doozy. I recently got a Droid3 to replace my original Droid. I've had it for less than 3 months. Its been rooted using Pete's One Click Root for this entire time without any issues.
Last week the following symptoms manifested:
1) Most applications, including system applications, force close constantly.
2) I'm usually unable to run any applications, including the Market.
3) What applications are having issues is not consistent.
4) The phone will reboot itself randomly, sometimes constantly.
5) Sometimes after a reboot it gives me no service and has the "Touch Android to begin" screen again. The phone is completely unusable when it does this, and the only fix is to pull the battery and then its back to its previous state.
5) Any changes made to the phone do not survive a reboot.
This last one is the real kicker. I can go through, uninstall every application I've ever downloaded but if you restart the phone or it restarts itself they will all return. This goes for everything on my Internal Storage. The SDCard seems unaffected...
I tried the SBF trick here from rootzwiki. (can't link since I'm new)
This did not work. How it failed might be important:
1) The primary method (psouza4's) acts like its successful but doesn't actually do anything.
2) RSDLite method will fail in step 3 (mbmloader.bin) every time, no matter what fastboot file I try to use.
3) After doing RSDLite I had the "flashboot flash failed" error and the phone was unusable. I then tried psouza4's method again and my phone has reverted to the same broken state it was in when I started.
So I'm not at all sure what I can do here. Since the bootloader isn't cracked yet I have no means to load another ROM. The only method I can find for Droid3 is through a Marketplace app that, on the rare instances I can install it, force closes immediately!
Any advice or ideas at all would be nice.
As for what started this, only two things happened out of the normal phone usage:
1) My girlfriend tried to text me a picture for the first time (of some chairs she wanted to buy for those curious/suggestive ) which never got to me initially but when it finally did after the 4th attempt I was never able to download the image.
2) I put a PDF file on the Internal Storage. Its one I've had for years and its just some manual I needed mobile and I don't have a laptop. Confirmed its malware free as far as any software can tell.
Working theory is I unplugged my phone from the USB too quickly after uploading the file but I don't know for sure. Nothing else was done unless Verizon had a OTA update that would break a rooted phone (guessing not since no one else seems to have this issue anywhere).
Again, any help someone can provide would be excellent. I'm going to have to load up my broken Droid in the mean time. Keyboard doesn't work and the touchscreen is failing but it can take calls more reliably than my Droid3 currently!
Cowmonaut said:
Okay, so this is a doozy. I recently got a Droid3 to replace my original Droid. I've had it for less than 3 months. Its been rooted using Pete's One Click Root for this entire time without any issues.
Last week the following symptoms manifested:
1) Most applications, including system applications, force close constantly.
2) I'm usually unable to run any applications, including the Market.
3) What applications are having issues is not consistent.
4) The phone will reboot itself randomly, sometimes constantly.
5) Sometimes after a reboot it gives me no service and has the "Touch Android to begin" screen again. The phone is completely unusable when it does this, and the only fix is to pull the battery and then its back to its previous state.
5) Any changes made to the phone do not survive a reboot.
This last one is the real kicker. I can go through, uninstall every application I've ever downloaded but if you restart the phone or it restarts itself they will all return. This goes for everything on my Internal Storage. The SDCard seems unaffected...
I tried the SBF trick here from rootzwiki. (can't link since I'm new)
This did not work. How it failed might be important:
1) The primary method (psouza4's) acts like its successful but doesn't actually do anything.
2) RSDLite method will fail in step 3 (mbmloader.bin) every time, no matter what fastboot file I try to use.
3) After doing RSDLite I had the "flashboot flash failed" error and the phone was unusable. I then tried psouza4's method again and my phone has reverted to the same broken state it was in when I started.
So I'm not at all sure what I can do here. Since the bootloader isn't cracked yet I have no means to load another ROM. The only method I can find for Droid3 is through a Marketplace app that, on the rare instances I can install it, force closes immediately!
Any advice or ideas at all would be nice.
As for what started this, only two things happened out of the normal phone usage:
1) My girlfriend tried to text me a picture for the first time (of some chairs she wanted to buy for those curious/suggestive ) which never got to me initially but when it finally did after the 4th attempt I was never able to download the image.
2) I put a PDF file on the Internal Storage. Its one I've had for years and its just some manual I needed mobile and I don't have a laptop. Confirmed its malware free as far as any software can tell.
Working theory is I unplugged my phone from the USB too quickly after uploading the file but I don't know for sure. Nothing else was done unless Verizon had a OTA update that would break a rooted phone (guessing not since no one else seems to have this issue anywhere).
Again, any help someone can provide would be excellent. I'm going to have to load up my broken Droid in the mean time. Keyboard doesn't work and the touchscreen is failing but it can take calls more reliably than my Droid3 currently!
Click to expand...
Click to collapse
I can say a couple words to describe my reaction.. OH ****. Your phone seems to have too many problems to be software related. Try to flash back to stock 5.6.890 and get a new phone.
Sent from my DROID3 using XDA App
Hmm, I guess for the mean time I'll just have to keep trying to get the Marketplace ROM Manager to install and launch. Should be a way to install straight to the SDCard that doesn't have problems.
Thinking it over, my Internal Storage may just have a bad sector... Yeesh.
Have you tried formatting /system in mounts and storage in CWM? Then reinstalling a fresh rom on top?
Sent from my DROID3 using xda premium
Negative. I didn't have CWM installed (stock ROM just rooted for certain apps) and apps are usually crashing now.
I'll give that a shot though. Sometimes I can use an app so maybe if I'm persistent...
and to verify, you are using the verizon droid 3 xt862? Are you on 5.5.959 or 5.6.890 (or possibly 5.7.894)?
Yea can't get any new apps to run. Interestingly, the camera app seems to crash the OS at the moment.
I think I'm going to have to try to RMA...
MrJudylicious said:
and to verify, you are using the verizon droid 3 xt862? Are you on 5.5.959 or 5.6.890 (or possibly 5.7.894)?
Click to expand...
Click to collapse
Its running 5.6.890. Unless I'm mistaken its the xt862. I've only had it since September.
well as long as root isnt showing and the /system hasnt been changed from stock rom, it should work. i do find it bad that rsd didnt work. i wonder if you were trying to flash the .959 sbf on your .890 system? I would def try again to sbf and wipe data/cache through stock recovery after that using volume buttons (android!)
Well, that's kind of the problem. Changes don't survive a reboot so i haven't been able to unroot the phone. I double checked and the file was the .890 flashboot. Wiping data/cache literally does nothing.
Is there a way to format this offline, from a PC? Going to try some more Google searches...
wiping data/cache should erase all of your saved data and force you to *228. Make sure USB debugging is on, set usb to Charge Only, try petes motorola tools to unroot but using RSD 5.5 fastboot .890 found http://forum.xda-developers.com/showthread.php?t=1255198
MrJudylicious said:
wiping data/cache should erase all of your saved data and force you to *228. Make sure USB debugging is on, set usb to Charge Only, try petes motorola tools to unroot but using RSD 5.5 fastboot .890 found http://forum.xda-developers.com/showthread.php?t=1255198
Click to expand...
Click to collapse
1) How do you unroot with Pete's motorola tools? Is it a different version than the one click root? Cause that's how I rooted my phone in the first place but it doesn't seem to have an option to unroot...
2) The link for the flashboot file gives a 404 error. The attached .RAR only has the .XML file.
Any place else I can get that version?
just enter stock recovery by holding down the x key on the keyboard when you boot up and wipe data
Edit: srry didnt read the full post
jellydroid13 said:
just enter stock recovery by holding down the x key on the keyboard when you boot up and wipe data
Click to expand...
Click to collapse
If you read the original post, that doesn't work.
Okay so I had an outdated version of Pete's tools which is why I didn't see the unroot option. Mine is the older one that was a batch file, not a application.
Got that sorted out and it still doesn't work. Seems I may have some permissions issues:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
[email protected]_solana:/$ su
exit
exit
exit
Permission denied
sh[email protected]_solana:/$ /system/xbin/su
Permission denied
[email protected]_solana:/$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]_solana:/$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
[email protected]_solana:/$ exit
(success)
That's part of the ADB log. There are a lot of other permission denied messages, which is a little comforting. The only thing I could think of that happened is permissions didn't get set right when Internal Storage was unmounted from my PC.
Since I can use ADB to access the shell, how can I format /system on the droid3? I can't seem to find the correct root name to use.
Cowmonaut said:
Okay so I had an outdated version of Pete's tools which is why I didn't see the unroot option. Mine is the older one that was a batch file, not a application.
Got that sorted out and it still doesn't work. Seems I may have some permissions issues:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
[email protected]_solana:/$ su
exit
exit
exit
Permission denied
[email protected]_solana:/$ /system/xbin/su
Permission denied
[email protected]_solana:/$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]_solana:/$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
[email protected]_solana:/$ exit
(success)
That's part of the ADB log. There are a lot of other permission denied messages, which is a little comforting. The only thing I could think of that happened is permissions didn't get set right when Internal Storage was unmounted from my PC.
Since I can use ADB to access the shell, how can I format /system on the droid3? I can't seem to find the correct root name to use.
Click to expand...
Click to collapse
Have you tried to root manually? Here are the original instructions vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/
[edit] I guess I miss read that you are trying to unroot.
try http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/ but you cant go from .890 back to .959! no idea about mounting, sorry.
MrJudylicious said:
try http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/ but you cant go from .890 back to .959! no idea about mounting, sorry.
Click to expand...
Click to collapse
That's the reference to Rootzwiki I made in the original post, doesn't work sorry.
Using ADB I mounted /system as rw and tried to manually remove certain apps. Once I re-mounted they were there again. So something is preventing me from making real changes to the Internal Storage.
Cowmonaut said:
That's the reference to Rootzwiki I made in the original post, doesn't work sorry.
Using ADB I mounted /system as rw and tried to manually remove certain apps. Once I re-mounted they were there again. So something is preventing me from making real changes to the Internal Storage.
Click to expand...
Click to collapse
You don't have superuser permissions.. In the ADB shell your command line should start with a # indicating superuser permissions.. you have a $
ChaoticWeaponry said:
You don't have superuser permissions.. In the ADB shell your command line should start with a # indicating superuser permissions.. you have a $
Click to expand...
Click to collapse
Where do you get that idea?
When I do this manually:
1) I'm running the command prompt as Administrator
2)I'm launching into adb using the command "adb shell".
3) First thing I do is type in "su"
4) second thing I do is approve "unknown" in the superuser app on account of it never remembering I already did that.
5) I use the command "mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system"
6) I use the "ls" command on /system/app and find an .apk to uninstall (not all my apps seem to be installed in this location either...)
7) I use the "pm list packages" command to find the rest of the files for that .apk
8) I use "rm <filename>.apk" followed by "pm uninstall <whatever that developer chose to name things>" command to fully uninstall.
I should note on my phone at this point it disappear from the application list.
9) I use the command "mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system"
10) I use the "ls" command on /system/app to confirm and voila, the apk file is back!
The app doesn't show up in my app manager until I reboot the phone. Changes to /system and /data are not persisting and I have no idea why.
I can't seem to unmount them either so I can't format via ADB...
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!...
Recently my phone had a low battery status. It booted up but apparently lost power somewhere when restoring the Apex Launcher screens.
Since then it just shows the Samsung logo and gets rather hot. I left it in this state for over an hour with no progress.
Boot and recovery mode work fine. Unfortunately adb is not in root by default, as such pulling is useless as nothing is mounted.
issuing
Code:
adb root
will result in:
Code:
adbd cannot run as root in production builds
I can issue for instance:
Code:
adb shell
su
e2fsck -pv /dev/block/mmcblk0p10
mount -t ext4 /dev/block/mmcblk0p10 /data
Unfortunately I cannot tar gzip and copy to the externalSD nor pull the data folder.
Starting dalvikvm fails:
Code:
127|[email protected]:/ # dalvikvm
dalvikvm
Dalvik VM init failed (check log file)
What options do I have to backup my data? Please provide me with concrete ideas and steps.
Many people are having similar problems, and I sincerely thank you if you can help me figure out a way to backup my data at this stage.
After reading the first two sentences and the title:
Buy a new battery.
Install something else, you are still on an early leak and not an official release.
I found a quick solution. All kudos and thanks go out to Philz as well as
TAHER128
Instructions and files are here:
http://www.youtube.com/watch?v=1TinSwsehZ8
After the new recovery mode and kernel is installed, reboot into recovery mode and go to the mount menu in order to select "mount USB storage". Backup everything to your PC.
From hereon out you are safe.
Install busybox if you want. Reflash a stock or custom rom if you want and/or dig your way through logs and fixes within a now powerful bash shell.
blairmiller said:
This problem is difficult to solve by your phone itself. Maybe you need to install some software to help you.
Click to expand...
Click to collapse
This thread is 2 months old
root
The reasons for getting a bootloop on your Android device might be anything. If you wish to know the reason why your Android phone is stuck on the bootloop, you need not type your problem on the Google search box. Just calm yourself for a while and think what you did just before. It could be anything! Here are some major reasons why your Android device is caught in a bootloop.
I upgraded to 4.3 from 4.2 and found I'd been SCROOGLED again. If any Google android developers happen upon this thread, I would really love an explanation as to exactly why we aren't allowed to use CIFS (and other external filesystems for that matter) out of the box. It doesn't really make much sense...unless you're trying to force us into using your stupid cloud services and to purchase media we already own from the Play store. You really wouldn't be trying to do that now would you? Anyhow, I had CIFS mounting working great under 4.2 by using a local connection to ADB and scripts to replace /system/bin/mount and umount. But, after going to 4.3 I found that not only did those googley bastards remove loadable module support from the kernel, but they also "jailed" ADB in their stupid namespaces. What that means is that it is now absolutely impossible to get CIFS working using the stock kernel and ADB. Thanks a lot Google! A thousand curses upon you and your progeny!
So, to get around this mess I've compiled the latest grouper AOSP kernel using the default config and added loadable module support. I've also compiled the CIFS, md4, nls_utf8, and configs (they removed the /proc/config.gz in 4.3. Why?) modules. Then, I built sshd, ssh, and ssh-keygen from the Android source. The paths were all messed up for the ssh client with the default configuration, so I changed them. It's set so sshd stores it's configuration and keys in /data/ssh, and the client uses /data/.ssh. I ran into some weird issues with the libcutils.so library which sshd is linked to. It doesn't come with Android by default and it seems if I install it to /system/lib it breaks everything and the tablet won't even boot. So, I just statically linked it to sshd. I also altered the /init.rc script to start the ssh daemon and created mount and umount scripts which simply ssh to localhost and run the mount/umount commands through busybox with whatever arguments they're given. The scripts replace the /system/bin links and the mount script creates /cifsmnt/0-9. You can change this if you need more mount points by editing the mount script. Since sshd is started by init outside of dalvik and ADB we don't have to worry about the stupid private namespaces. I'm now able to mount my CIFS shares again and actually use them from all applications. Instructions are below.
DISCLAIMER: This worked for me, but I'm making no guarantees. If you have weird issues, lose data, brick your tablet, whatever; I take no responsibility for it.
1. Download one of the two update .zip attachments below. One contains the kernel and modules I've built. The other just has the altered /init.rc, ssh binaries, libssh.so, and mount scripts. If you would like to use a different kernel than the one I've compiled, use that one. I haven't tested it, but it should work as long as the kernel has CIFS/md4/nls_utf8 modules/built-in. Just save the .zip to your tablet and install it from recovery.
2. When your device boots back up, start a shell and run:
Code:
su
ssh localhost
It will ask if you want to continue connecting. Enter yes. It will fail to connect, but that's OK.
3. From the same shell run:
Code:
ssh-keygen
This will create the public/private RSA keys.
4. From the same shell run:
Code:
cat /data/.ssh/id_rsa.pub >> /data/ssh/authorized_keys
This will allow the user root to open a local ssh session without a password (they aren't even supported under Android anyhow)
If you use Cifsmanager and are using my kernel (other kernels may not need to load modules or the modules may be kept in a different path):
5. In CifsManager's settings, check "Load cifs module" and "Load via insmod". Then set "Path to cifs.ko[:<modpath>]*" to:
Code:
/sdcard/modules/cifs.ko:/sdcard/modules/md4.ko:/sdcard/modules/nls_utf8.ko
6. Create your share in CifsManager and under options put:
Code:
rw,file_mode=0777,dir_mode=0777,uid=1015,gid=1015
(and any others you may need) . For the mount point, use one of the the mount points created under /cifsmnt (0-9).
Hey, sorry for the necrobump, but would the no_kernel zip work for the 2013 nexus 7 LTE?
Also, when I try running "ssh" in a terminal emulator, it says that the command wasnt found. Sorry if I sound oblivious, Im kinda a noob at these things
suffer1989 said:
Hey, sorry for the necrobump, but would the no_kernel zip work for the 2013 nexus 7 LTE?
Also, when I try running "ssh" in a terminal emulator, it says that the command wasnt found. Sorry if I sound oblivious, Im kinda a noob at these things
Click to expand...
Click to collapse
It may. I don't have one, so I can't be sure. You'll still need to get a kernel with CIFS support/modules though. You'll also need to compare the init.rc in my zip with yours and see if there's anything in yours that will need to be added to the one in the zip. If you post your init.rc I can take a look at it. Also, it's saying command not found for ssh because ssh doesn't come with android, it's part of the zip.
jmtw000 said:
It may. I don't have one, so I can't be sure. You'll still need to get a kernel with CIFS support/modules though. You'll also need to compare the init.rc in my zip with yours and see if there's anything in yours that will need to be added to the one in the zip. If you post your init.rc I can take a look at it. Also, it's saying command not found for ssh because ssh doesn't come with android, it's part of the zip.
Click to expand...
Click to collapse
I realized that I need a kernel with CIFS support so I downloaded and flashed this one:
http://forum.xda-developers.com/showthread.php?t=2389022
from
http://www.androidfilehost.com/?fid=23212708291674219
Do I still need to flash your zips since I flashed a kernel that supports CIFS?
CIFS support is the one thing holding me back from really fully utilizing my nexus 7 :-/.
suffer1989 said:
I realized that I need a kernel with CIFS support so I downloaded and flashed this one:
http://forum.xda-developers.com/showthread.php?t=2389022
from
http://www.androidfilehost.com/?fid=23212708291674219
Do I still need to flash your zips since I flashed a kernel that supports CIFS?
CIFS support is the one thing holding me back from really fully utilizing my nexus 7 :-/.
Click to expand...
Click to collapse
You will still need to use my zip that does not contain the kernel. It has the other stuff (ssh, sshd, mount script, init.rc) that allows CIFS mounts to work. But like I said, you need to make sure that there isn't anything in your init.rc which isn't in the one in my zip, as it will replace yours so that sshd will start.
jmtw000 said:
You will still need to use my zip that does not contain the kernel. It has the other stuff (ssh, sshd, mount script, init.rc) that allows CIFS mounts to work. But like I said, you need to make sure that there isn't anything in your init.rc which isn't in the one in my zip, as it will replace yours so that sshd will start.
Click to expand...
Click to collapse
Thanks, ill look through your Zip file, as well as the rom I am using to compare and contrast and see if it is safe to put into my 2013 preKK nexus 7.
I played a little bit with it, but get stuck at some time with just getting "Invalid argument" when trying to mount.
I have 4.4.2 with franco kernel (r12).
I looked into your "nokernel" zip and was surprised that you have a boot.img that for my understanding includes the ramdisk and a kernel.
So I unpacked the franco kernel img using http://forum.xda-developers.com/showpost.php?p=35181780.
I changed the init.rc file in the ramdisk image and removed the "disabled" on the service sshd statement.
Somehow it still does not start sshd on boot using the repacked boot.img
Another issue I had was the updater script. It did not mount the correct partitions for me.
I modified it:
Code:
ui_print("Installing CIFS Mount Support");
ui_print("Mounting /system");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
delete("/system/bin/mount");
delete("/system/bin/umount");
package_extract_dir("system", "/system");
set_perm(0, 0, 0755, "/system/bin/mount");
set_perm(0, 0, 0755, "/system/bin/umount");
set_perm(0, 0, 0755, "/system/bin/sshd");
set_perm(0, 0, 0755, "/system/bin/ssh");
set_perm(0, 0, 0755, "/system/bin/start-ssh");
set_perm(0, 0, 0755, "/system/bin/ssh-keygen");
unmount("/system");
ui_print("Mounting /data");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/userdata", "/data");
package_extract_dir("data", "/data");
unmount("/data");
ui_print("Write boot.img");
package_extract_file("boot.img", "/dev/block/platform/sdhci-tegra.3/by-name/boot");
The next issue was with the mount script. The remount rw of / did not work in the script and leave the system without the mount folders.
So I created them myself with:
Code:
busybox mount -o remount,rw /
mkdir /mnt/cifs
chmod 755 /mnt/cifs
mkdir /mnt/vids
chmod 755 /mnt/vids
busybox mount -o remount,ro /
Now that sshd didn't start I started it myself, what could be the problem when I trying to mount the cifs later.
sshd showed me that he had to create the keys in /data/ssh. Could it be the problem with init.rc trying to start sshd without the keyfiles there?
I was able to "ssh localhost". I tried manually mounting inside the ssh session and always got "Invalid argument".
For example with this command:
Code:
busybox mount -t cifs -o username=user,password=password 192.168.0.1/share /mnt/cifs/vids
Any suggestions?
Could there be a way without having to edit the ramdisk or is this the necessary way to have sshd in the right name space?
The solutions posted for the same issues with 4.2 http://forum.xda-developers.com/showthread.php?t=2106480 would not work on 4.4?