yashsingh1/xdaforums huggingface dataset:
[Nexus 7 3G Android Development] mateorod:
Glad to hear that the web builder is finally producing images that boot. It has been compiling the whole time, but the sbin folder was incomplete. Porting it by hand produced a working image, but not usable if you understand.

I added a CWM Touch image to the OP.
[Nexus 7 3G Android Development] gatebil:
Touch version working perfect.
[Nexus 7 3G Android Development] gftey:
i rooted my n7 gsm using wugfresh toolkit. after rooting, i installed rom manager v5.5.0 to install the recovery.

will the recovery provided by rom manager work fine on the n7 gsm?

or can i flash the touch version image directly on top of the current recovery using wugfresh's advanced utility to push the touch recovery?

thanks for the help!
[Nexus 7 3G Android Development] gatebil:
Yes it will work fine and yes you can flash it with wugfresh's toolkit.
[Nexus 7 3G Android Development] Sib64:
Send you a PM, can you give an answer please.

Thanks in advance ;)
[Nexus 7 3G Android Development] gftey:
thanks gatebil!:)
[Nexus 7 3G Android Development] kamaliqwan:
Sorry guys..im a biggest noobie here...

I just know how to use odin, cwm (big samsung fan) :p

And now i really dont understand how to use the command / flash the .img file

My Tilapia is rooted, with TWRP but failed to install Paranoid (status 7)

Anyone can guide me... btw im using windows :D
[Nexus 7 3G Android Development] knitler:
I keep getting:

mv: can't rename 'recovery-from-boot.p': No such file or directory

Any ideas?
[Nexus 7 3G Android Development] Sib64:
Apparently you can go to the recovery.

So you can use this post. Really simple and faster : HELP FOR FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND

and maybe than you root is failed. So you can root again with [ROOT] Superboot - Nexus 7 WiFi / 3G root solution by paulobrien

Just rename it recovery

and in the command line, type this :

c:\fastboot>fastboot flash recovery recovery.img
[Nexus 7 3G Android Development] knitler:
Hmm it looks like the problem is that the file doesn't exist. I cant see it in Root Explorer either. I dont get it. I followed the directions exactly as in the 1st post.
[Nexus 7 3G Android Development] mateorod:
Status 7 means you are flashing an mismatched rom/recovery set. On of those is for a different device. If you are using the time recovery from this thread, you will not have status 7 errors flashing a tilapia ROM.

That means the file is already gone. That file isnmonky in stock Roms, so if you already moved or renamed it or if you have a custom ROM, it will be gone. That file just reflashes stock recovery,which you don't want because it is severely neutered. If it is gone, don't mourn it.
[Nexus 7 3G Android Development] knitler:
Is there a place I can get it so I can still restore if I ever need/want to?
[Nexus 7 3G Android Development] mateorod:
You can flash stock recovery(the action of the file) or system.img (replace the file itself) with fastboot at anytime. But I have literally NEVER heard of anyone restoring that file after rooting. Once you have custom recovery there isn't one reason to go to stock recovery. That is a limited recovery which is only there to handle OTA's for those people who have never heard of adb, fastboot or XDA.
[Nexus 7 3G Android Development] knitler:
I'm just thinking about if I am to sell it in the future.
[Nexus 7 3G Android Development] mateorod:
Okay, we're drifting out of the scope of this thread here, but you can completely restore this device to stock easily. You download a factory image from Google (provided for this express purpose) and restore anything you want.

Just be careful and don't erase your boot loader and you have a device that can always go back to stock or sent in for warranty. Look in the grouper forums, you'll see a bunch of guides about restoring to stock. But just use the 'nakasig' images from Google, which are the Nexus 7 3G.
[Nexus 7 3G Android Development] ledinhsonhp:
Sorry for the OT, when i rooted my Nexus 7 by using this Toolkit [Toolkit] Wug's Nexus Root Toolkit v1.6.1 [Updated 11/30/12] and either installed Custom Recovery TWRP from this Toolkit, it shows the version v2.3.2.1 of TWRP, so i have a question that what is the different betwen your ported TWRP v2.3.1.2 and TWRP v2.3.2.1 from that Toolkit, which one is better?
[Nexus 7 3G Android Development] FReaKRaNT:
The one in Wug's toolkit is a grouper TWRP. He will replace it with Tilapia when there is an official release.

Cheers, FReaKRaNT
[Nexus 7 3G Android Development] mateorod:
Which means that it won't flash any of the roms for this device. And you can't get twrp recovery for Nexus 7 3g from Team Win either. Only here.

I consider flashing grouper recovery to a tilapia device, especially with a one-click tool where your users mostly won't know any better, to be a lapse of judgement, at minimum. If that is happening and If he doesn't want to include unofficial recoveries, he should withdraw trwp support for this device.

The twrp recovery I linked to is actually 2.3.2.1 and I mistyped it, so this recovery is basically the same. There is a 2 commit difference, one of which is simply the versioning bump. However, I will have a 2.3.3.0 build coming out today.

And I see that the use of the word porting is throwing some people off some. When recovery, be it CWM or TWRP, is brought to a new device, it is always called porting. TWRP was ported to grouper just like it was ported to tilapia. The only thing that is not 100% compiled from source in this recovery is the manually ported sbin folder, which is simply because of a non-functioning binary. I found some time to work on this yesterday, and I think I have it solved.

Eyeballer from Team Win and I have put out a rom together, so if it boots, I will shoot him my fork and then it can become the Official release for TWRP. Then you (and mskip) can get it from the Team Win website as it is updated.

Edit: And for the record, you can't tell me that using the wrong recovery isn't dangerous simply because we have a Nexus device. Synman and ShinJ1eva have both permanently lost their IMEI by flashing a baseband for the wrong device. That is advanced stuff, sure, but the type of mistakes that happen when you disregard the safety checks built into the recoveries that are meant for your device.
[Nexus 7 3G Android Development] ledinhsonhp:
I hope that next version will come with flashable zip.
[Nexus 7 3G Android Development] kamaliqwan:
Ooo yeah....thats why i got status 7 error when i flashing Paranoid-(for tilapia)

Can someone make TWRP in flashable zip...?

:fingers-crossed: :fingers-crossed: :fingers-crossed:

Merry christmas guys!! :D
[Nexus 7 3G Android Development] SirRastusBear:
I don't know about Wug's toolkit, but mskips's toolkit has function to install .img file to recovery (that is how I installed mateorod's twrp port). There is also flash image GUI app that you can get from play store to install,although I can not vouch for it's viability.

Happy Merry!
[Nexus 7 3G Android Development] kamaliqwan:
dude thanks a lot for the info

i manage to flash the TWRP.img file using flash image GUI app :good::good::good:
[Nexus 7 3G Android Development] seandarcy:
twrp: restore system, data or boot ??

I used goomanager to install twrp 2.3.3.0. Used twrp to backup. Wiped. Flashed temasek rom.

Now I want to reinstall the apps that were on the phone. In recovery twrp gives me the options of System, Data and Boot.

Which do I choose to just reinstall my apps?

sean
[Nexus 7 3G Android Development] Sib64:
If you haven't backup all of your user apps with a apk as Titanium backup or others...

Why you don't use your Gmail account for restore all of your apps ?

But before you must have ticked in previous install and in your settings > Backup and reset > Tick all

And if you restore your system, it will be the last system of your latest rom...

If you restore the boot, it will be the last boot of your latest rom...
[Nexus 7 3G Android Development] seandarcy:
restore Data a bad idea

I did use my Gmail account to restore the apps, but that didn't include usernames and passwords. Also there were some apps that didn't come from the Play Store.

I didn't want the system of my latest rom, or the last boot. So I just restored Data.

That was a bad idea. On reboot, I just get an endless CyanogenMod boot screen. I'll let it sit for an a while longer, but I think i'm back to a full wipe and reinstall.
[Nexus 7 3G Android Development] wanzer:
Reinstall, then use App Extractor to find your last nandroid and select the apps in it that you want to restore. Done!

Inviato dal mio HTC One X con Tapatalk 2
[Nexus 7 3G Android Development] mateorod:
Since you are a first time flasher, my bet is that you don't have a nandroid backup. You can make those in recovery to back up your whole system. But yeah, wiping the device to install a custom ROM will cost you your data, unfortunately. To fix your boot loop, wipe again and reinstall temasek's build. Five minutes of boot loop is too long.

Now that you are rooted, you never need for this to happen again, no matter what ROM you choose. Look into the free root app Titanium Backup this is what it's for.
[Nexus 7 3G Android Development] p0izn:
Well known to me, that path for cwm backups is "shell/emulated. "

But how can i delete some of them in a file manager?

Thank you
[Nexus 7 3G Android Development] fers:
I need help

Edited:

At the end, after pushing power button for 20 or 30 seconds, my machine switch on. I've flashed CWR again. All is Ok now.

Thanks

---------------------

Hi Guys,

This is my first post, so firstly I want to say hello.

I think I have a big problem with my Nexus 7 after trying with what this thread explains . At this moment my Nexus 7 is bricked, that is, nothing happend when I'm trying to swith on. The screen is black, whatever I do. I can't open in Recovery mode; in my linux, "adb devices" command doesn't list the device, neither "fastboot devices" one.

What I did was:

1- Following instrucctions of post #1

- Step 1: was Ok

- Step 2: was Ok

- Step 3: was OK with recovery-CWM-touch-6.0.2.3-tilapia.img

- Step 4: was OK (no error message after aplying mv command)

- Step 5: was complicated. I tried with "adb push CWM-SuperSU-v0.99.zip /sdcard/" but I couldn't find the zip file with 'choose zip from sdcard' in CWM. The I repeated with "adb push CWM-SuperSU-v0.99.zip /sdcard/0" without success. Finally at my risk I tried installing the .img file with the CWM function of "Sideload option" (or something like this). It seemed to work.

- When I reboot I answerd "No" about stock recovery question

2- After I booted without problems from the CWM screen. My Nexus 7 started without problems. I configured my Google Account and recover from my Google Backup.

3..- Finally I switch off my machine to re-start again and make a nandroid backup. From this moment, my machine is a black machine.

Could somebody help me?

Thanks a lot, and excuses for my English
[Nexus 7 3G Android Development] fers:
Question about grouper or Tilapia

Hi,

After aplying the process I see in the "/" directory de following files: "fstab.grouper", "init.grouper.rc", "init.grouper.usb.rc" and "ueventd.grouper.rc"

My question is: Does it mean I have a Grouper Recovery in my machine? I don't remember what there were there before applying the process.

Just to avoid future problems,

Thanks
[Nexus 7 3G Android Development] mateorod:
Just the way the build system is set up. They have a bunch of common device files. I actually think that those files being titled grouper should be resolved at a source level, and for just this reason. It is inaccurate as tilapia has it's own board. (which is why I started this thread...official threads on XDA were advising to install grouper recovery, in this day and age...)

I may send something upstream when I have time...I am not even sure if this is an AOSP or simply CM issue, although my money is that AOSP has it right and that CM just hasn't looked at it....

But yes, it's fine. The information within those files are accurate for tilapia's info.
[Nexus 7 3G Android Development] Master Gowa:
How come 2.3.3.0 isn't listed in your achive? Wugs toolkit downloaded 2.3.3.0 tilipia for me. Is 2.3.3.0 a bad version or something?
[Nexus 7 3G Android Development] kenkiller:
It's just not updated in the first post. Besides, the official version already supports tilapia, so no more need to self compile.
[Nexus 7 3G Android Development] servellia:
I have rootet my device by using the Nexus 7 toolkit and let it do its magic (includiing flashing a custom recovery) Do I still need to flash the newest TWRP or can I just go and flash cm 10.1?
[Nexus 7 3G Android Development] FReaKRaNT:
Boot to recovery and see if it is the latest version.

It should be 2.3.3.0

Cheers, FReaKRaNT
[Nexus 7 3G Android Development] servellia:
I have ClockworkMod Recovery 6.0.1.9 installed.
[Nexus 7 3G Android Development] faust.deaconu:
how much time does it supposed to last the unlock? i typed fastboot oem unlock and it is waiting for device, and waiting and waiting. latest tilapia i saw is 2.3.2.1. where can i find 2.3.3.0?
[Nexus 7 3G Android Development] Sib64:
Now,

it's 2.4.1.0 by TWRP for Tilapia

, you can use it without problem ;)
[Nexus 7 3G Android Development] faust.deaconu:
i am on ubuntu last release. and fastboot oem unlock doesn t work. i ve instaled adb and fastboot. do i need another package?
[Nexus 7 3G Android Development] Sib64:
The last release is 12.04 or 12.10 ?

but I believe that there are some problems with the latest version of Ubuntu, but I'm not sure of that.

Have you use this guide : Ubuntu 11.10 and ADB and fastboot

and try this : [GUIDE] - Updated 30Jan - Unlock and Root a Nexus7 3G “Nakasig- Tilapia”
[Nexus 7 3G Android Development] cmstlist:
Waiting for device should only take a few seconds. You need to get the correct fastboot drivers and be booted into fastboot. Use the command "fastboot devices" to verify if it can see the device.
[Nexus 7 3G Android Development] xtoudi:
Try with sudo.

Works on 12.10
[Nexus 7 3G Android Development] faust.deaconu:
worked with sudo. but now can t make twrp permanent recovery. can t boot to recovery mode by presing volume up. i got into twrp recovery from bootloader menu but i can t "adb shell" or even "sudo adb shell". it says "insufficient permissions for device". i also tried to install cm10.1 from temporary twrp but instalation aborted.
[Nexus 7 3G Android Development] andy034:
How do i update my recovery?

I used a nexus 7 toolkit by Mark skippen and installed cwm 6.0.1.9. i think this is a grouper cwm as I am unable to install 4.2.2 for tilapia using this. it is giving me an assert failure. Now that my bootloader is unlocked, should i still have to follow all the steps in OP? Or can I flash any file to get a tilapia recovery?

thanks
[Nexus 7 3G Android Development] mateorod:
Wait...he still is installing grouper recovery? That should never have been happening in the first place. No wonder people are so down on tool kits. I hope he likes getting bug reports.

Flash recovery that is made for your device (the one is this thread will work fine.)

Edit: Did you uninstall any system apps?(Currents, Books, etc?) That will give you an assert failure even with tilapia recovery.
[Nexus 7 3G Android Development] cmstlist:
I took a TWRP backup of my existing Nexus 7 3G (latest available official TWRP from Goo Manager on both devices) and restored it to the new one Google sent as a warranty replacement. It booted up and had all the apps, but was in a weird state where the home button didn't work and the quick settings didn't work from the upper right corner - which usually is the state that results from improperly skipping setup.

More confoundingly, all my apps were there but the app data had failed to restore properly. It remembered basics such as wi-fi settings, but all app data seemed to have been lost in translation.

Any idea why this would have happened?

I flashed both tabs to the latest CWM from ROM Manager and tried again. After hours of slow data transfer from one tab to the other, I finally restored the backup and it runs perfectly. Is there something wrong with TWRP?

I used compression and the data backup was split over 3 files due to its size.
[Nexus 7 3G Android Development] compact2559:
6.0.2.3 Touch .zip anyone?

Does anyone have a flashable zip of the 6.0.2.3 CWM Touch for TIlapia? Can't seem to see it in the thread
[Nexus 7 3G Android Development] sgw99:
Greets, I am a rookie N7-3G user (yes, tilapia) and immediately flashed CM10.1 last week ;)

I flashed recovery-CWM-tilapia-regular.img at first ... but the step "mv system/recovery-from-boot.p system/recovery-from-boot.bak" did not work for me as the file system/recovery-from-boot.p does not exist (checked again right now).

CM10.1 installed, works fine, I am on the nightly from 0525 now.

But when I use the CyanogenMod-Updater it does not flash the updates correctly ... it says "untrusted Package".

"E:failed to verify whole-file signature" etc.

The recovery is "CWM-based Recovery v6.0.2.1". I retried this several times already to avoid corrupt downloads and make sure that it pulls the latest nightly. Does anyone have a hint for me? Do I miss something?

Thanks, Stefan

UPDATE: solved by flashing/using openrecovery-twrp-2.5.0.0-tilapia.img ... sorry for the noise, but maybe this posting helps someone else ;)
[Nexus 7 3G Android Development] gtizon:
Does anyone have the most updated cwm recovery in a zipfile? Thanks!
[Nexus 7 3G Android Development] Sib64:
Go to the index for N7 3G and you will see that ;)

[RECOVERY] ClockworkMod Recovery 6.0.2.3 [Fastboot&Flashable Zip] by htchoi5609
[Nexus 7 3G Android Development] ultimatepichu:
isn't that for Grouper?
[Nexus 7 3G Android Development] mateorod:
Jeez, good catch. The whole reason this thread was created was because I saw the various toolkits and "indexes" (why need an index I will never know, the list of threads is enough for me) were recommending and installing grouper recovery. Since there was no CM10.1 yet, and no TWRP for 4.2 yet, I patched and built CWM and TWRP myself. I knew that anyone who installed grouped recovery would have a pretty hard time uodatingnto a proper tilapia ROM, whenever they came out.

So this was them only place to get tilapia recovery, for nearly a month in TWRPs case. But now it is everywhere, I only leave it up because you never know who might need clear root instructions.

Google "tilapia recovery", rooters of the future, and get the most recent recovery.img. Then follow the OP. I will be closing this thread shortly
[Nexus 7 3G Android Development] mateorod:
This was only in development because at the time it was the only working recovery for tilapia at all, and I believe it was the only TWRP for Android 4.2 anywhere, for the first month or so (until TWRP merged versions of my patches). Now Google search can get you any recovery for this device you want so thread is closed.

The only other reason to post here would be porting advice for later Android versions, which I would probably not see in time anyway.

If you need help rooting, read the OP and then if you have more problems/questions, post in Q&A. Thanks for the fish!!
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] Extreme_One:
Only got the replacement yesterday, upgraded to 4.0.26, did a full charge overnight to 100%

Been at work all day so had very minimal useage; few emails / browsing. The tablet's been asleep most of the day and already I'm down to 35% charge!?!

Is this a problem with the new firmware? Does it sound to anyone else like the device may be faulty?
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] hb1972:
Me 2

Don't matter, u are not alone, i have the same problem.

Since firmware 4.0.25 (also 4.0.26) i need to charge my G9 everday, by very less use.

With the old firmware 4.0.7 i could use my device 3 days without charging.

I hope Archos fix this problem quickly, i this way te tablet is worse too use.
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] Extreme_One:
For me, the second day is better. I did another full charge overnight and today it seems a bit better...

I'll keep a close eye on it.
[T-Mobile Samsung Galaxy Note II] svavrek:
So... when the phone is at full brightness (which is often, I like it) and I launch the browser, the damn thing dims for the browser but still shows @ full brightness... what setting un-f's this? Soooo annoying! I cant find it anywhere... :mad::mad::mad:
[T-Mobile Samsung Galaxy Note II] jtn7040:
Been answered so many times lol..... hit menu browser has a sperate brightness setting in it
[T-Mobile Samsung Galaxy Note II] meechieervin:
When I had the galaxy s2 my phone used to do the same thing, it was because the battery was getting to hot
[T-Mobile Samsung Galaxy Note II] geekempire:
Even setting the brightness all the way up in the browser it still is not as bright as the rest of the phone. I hate that they do this, its the worst part of any phone from Samsung.
[T-Mobile Samsung Galaxy Note II] SMARTPHONEPC:
Agree Samsung is totally annoying with that. When are companies going to start listening to users?

In Android settings there should be a check box in display->brightness to apply globally overriding app specific brightness settings as I have come across other apps that try to control brightness independently as well.

Another reason to install other browsers..
[Samsung Infuse 4G] themightyjanbur:
Hi,

I'm getting the attached screenshot when I boot. It boots to this every time. Any magic to get around this?

Thanks in advance,

Janbur
[Samsung Infuse 4G] psal217050:
Looks like you need to flash GB bootloaders.

Do a search for it.
[Samsung Infuse 4G] Skwerl23:
Qkster one click to stock. Then reflash(qkster one click) with boot loaders. (Basically qkster one click twice but the second time you tick the boot loader option)

Then flash entropys one click to cwm.

Then flash cm7 or cm9.

Don't flash cm10 till after cm9
[HTC Sensation] dstauffer:
Or at least it won't show any signs of life. No response to the power button, no LEDs when plugged in. Left it plugged in for several hours to no avail. Tried my wife's battery, but that made no difference either. It started with a series of re-boots while using common apps (G+, Twitter). Once or twice it went to the boot loader screen, and now nothing. I've removed the sim and SD card, but still nothing. I had done a factory reset about 10 days ago for performance and battery issues, but that all seemed to be fine until this happened.

I did have an issue about 2 months ago where the phone would reboot to the boot loader screen (if that's what its called) constantly. I solved this issue by removing the Sim and SD cards. It then booted normally and I put the cards in one at a time. Not sure if that would have any connection.

I'm in Canada on the Bell network, and I'm outside my one year warranty.

I have seen things like the unbrick project, but I don't know if those steps apply to my situation. There's probably some obvious steps to start with, but I'm not sure what to try, since I didn't root the phone or do any customizations or anything. Thanks in advance for any tips or ideas.
[Samsung Epic 4G Touch] UnderworldDemon666:
How does one simply create an Odin One-Click. I have searched all over the interwebs and have found no guide. I am planning to deodex the latest FK23 leak, and would like to package it as a One-Click.
[Samsung Epic 4G Touch] rwilco12:
Creating a one-click can be very tricky. It requires a working knowledge of Linux and ADB, a pc with both Windows and Linux and a lot of patience.

What you're proposing is actually something Agat and I were working on but you had to build the ROM in a zip, flash it to your phone, do a system dump, compile it into a TAR ball and then compile the one click. The tricky part was that if you weren't really careful your activation data and personal info could wind up in the one-click.

We temporarily scrapped it for other projects that were less time consuming and less risky.