Hey guys
I successfully installed the Ubuntu Touch Developer Preview onto my GNex, had a play around with it and have decided its definitely not ready for prime time!
However I'm having a hell of a time trying to restore Android onto my GNex - I've googled how to restore Android onto the GNex with Ubuntu Touch installed but the processes there are for people who use Ubuntu desktop OS
Can anyone help at all? I'm no subject matter expert however I do know my GNex has TWRP installed sand so far my Windows 8 notebook does not allow me to explore my GNex when its connected via USB
Sent from my Nexus 7 using xda app-developers app
Bump for this thread?
Sent from my Nexus 7 using xda app-developers app
Hold Volume Up + Volume Down + Power (from a powered off state) to boot into fastboot. Then hit Volume Up twice and then the power button to make your way back to recovery and restore a NANDROID backup (if you made one), or wipe System, Data, Cache, Dalvik Cache and flash a new ROM.
Worst case scenario, you'll have to follow the instructions here: https://wiki.ubuntu.com/Touch/Install
Scroll down to "Restoring Android".
Sent from my Galaxy Nexus using xda premium
Related
What does the amons recovery do. I wanna get it but I don't know if what I have will mess my phone up? How do I tell what recovery image I have now?
Sent from my Vanilla Tazz using XDA App
And my phone corrected then topic. Oops hah
Sent from my Vanilla Tazz using XDA App
If you have purchased a PC in the last few years, it has a portion of your harddrive partitioned off, and in that partition is software to restore your computer. It includes a menu of options, plus the windows software to allow you to rebuild your computer. Amon Ra is the same basic thing for your phone.
To see if you have it, hold the volume-up button while your phone powers up. You should get a menu (green print) with a list of options to flash an update, backup & restore, reboot, wipe, and install a zip. This is the recovery menu. You can & should make a full system backup first thing, in case you mess something up later. Then you can use this menu to install new ROMs, or restore from an old backup.
Instead of Amon Ra, you might have Clockwork recovery instead. They both pretty much do the same thing. I personally like Amon.
Oh Aright. Well that happens but I don't know which one I have ha. Thanks.
Sent from my Vanilla Tazz using XDA App
Next time I reboot ill look at mine to see how to ID it. I'm too ADHD to remember...
Sent from my ERIS using XDA App
I just looked but I can't remember it all (old age setting in).
Anyway, amon's at the bottom says something like "Build: RA v1.6.2"
Sent from my ERIS using XDA App
Ill check mine in the morning. Do you know anything about why when I flashed celbfroyo it didn't ask for a setup an didn't have a market??
Sent from my Vanilla Tazz using XDA App
danielahl137 said:
Ill check mine in the morning. Do you know anything about why when I flashed celbfroyo it didn't ask for a setup an didn't have a market??
Sent from my Vanilla Tazz using XDA App
Click to expand...
Click to collapse
It doesn't have the google apps as part of the rom.
Quoting Conap: "Please flash the googleapps for froyo after flashing rom. This google apps will fix the google goggles issue...
Google Apps Make sure you get the mdpi file."
Hi, I'm almost ready to release a working version of the recovery for this tablet.
It works properly with adb, but it has a UI glitch, as the stock kernel does not fully support framebuffering swaps.
It will probably be released within the next couple of days... just waiting for some final touches.
Sent from my HTC Desire using XDA App
Awesome! Ty! Will eagerly wait.
Sent from my Ideos S7 using XDA App
Lets do it
Sent from my Ideos S7 using Tapatalk
Sweet.
Sent from my HTC Vision using XDA App
Just got my S7 and dying to unlock and flash! Looking forward to all the fun hidden in this monster!
Sent from my Ideos S7 using XDA App
some news about recovery ?
Sent from my S7 using XDA App
Is this similar to ClockWorkMod?
Topic seems dead, no more news about the tools...
Sent from my X10i using XDA App
Any update?
Sent from my HTC HD2 using Tapatalk
I put together a partially working version of Clockworkrecovery that works better, but it renders only around 50% of the screen. It on my external + internal SD version of S7:
http://www.multiupload.com/0JBBOE4NAL
Changes were made to graphics.c in the recovery source code to workaround the framebuffer issues.
I was able to make a successful nandroid with this.
I am not a developer, so this is not just unfinished, but buggy.
I posted details here: http://www.androidtablets.net/forum...-recovery-help-needed-lcdc_panel-s70-c-2.html
I want to know if there is a good way to deploy this to pre-rooted users. If not, it might be better if we put together something.
This can be flashed in fastboot, or with a flash_image binary. .
xaueious said:
I put together a partially working version of Clockworkrecovery that works better, but it renders only around 50% of the screen. It on my external + internal SD version of S7:
http://www.multiupload.com/0JBBOE4NAL
Click to expand...
Click to collapse
THANK YOU! (pointless comments but i know our battle here!)
Loading though fastboot would be a pain for most new users, I wonder if we can get something simular to the archos SDE running on the huawei then we could load the custom rom and ditch the main kernel. ideas?
Someone will figure something out.
For now, you can fastboot boot this recovery image to make a working nandroid and restore as well.
I have tested nandroid now, and it works. Not tested for apps2sd though, because I do not have that setup.
I recommend that everyone would this first though: http://forum.xda-developers.com/showthread.php?t=968850
this is working on my s7 too
i tested today and recovery is working the fact that it only uses a third of the screen is not an issue in my view.
i did a nandroid backup of my system and have all mtd files saved on my desktop
my device get on a zombie state after power off the 18d1:d00d google inc appears on lsusb but the device doesnt do anything i had to reboot and do the volume and power aggain for it to respond.
on ubuntu 64 at least on my system i had to run fastboot as root
this is nice work thanks xaueious
I fixed the weird misc bug. I was using razor950's device files, which has BOARD_HAS_NO_MISC_PARTITION := true defined. My Singapore ROM has the misc partition.
Anyhow, working S7 recovery now for BestBuy version:
http://www.androidtablets.net/forum...lockworkmod-recovery-port-xaubeta-0-11-a.html
Hello there.
I own a Kyocera M6000. I believe our recovery partitions act in a similar way, in that upon reboot to recovery (of the stock recovery, that is), the device will wipe data/cache.
This is preventing clockwork recovery from loading when flashed to our recovery partitions.
I was wondering if someone here would be able to explain this issue in more detail, and any steps taken for a work around?
Much Appreciated.
Can anyone help me find a site with stock roms for lg e739 or the lg mytouch 4g? I need it to flash my phone back to stock. Any help would be greatly appreciatied.
Tsk Tsk Tsk, on you for not backing up your stock.
You could always try the LG Mobile Support Tool
www[DOT]lg[DOT]com/us/support/mobile-devices/phone-support
I havent tried to use this method yet so I'm not 100% sure it puts you back to stock, as it came out of box.
Download and install LG mobile support tool, run LG Mobile Update. Click on Customer Support in the menu, then click recovery. Remember to have your e739 connected via usb.
I did make a backup. It just won't restore. Even tried removing the Android secure file from my backup and got a md5 sum mismatch. Downloaded someone else's backup and it shut my phone off before the restore was complete just like my backup before I removed the Android secure file. Now I'm stuck wit cm7.2. Should I flash cwm before I restore like I did when I installed cm7 the first time?
Sent from my LG-E739 using xda premium
You got the md5 error because you removed something from the nandroid...thus changing the ckecksum.
I would say try flashing that nandroid that you downloaded. Makin sure its named correctly. Without removing any files from it.
Also try to redownload that stock nandroid backup n try again. Btw which one was it?
Did you wipe cache system and data partitions before flashing nandroid?
Do not wipe sd card.thats where nandroid would be.
On my e739 during flashing nandroids Ive had it get stuck at lg logo once or twice. All I did then was use adb reboot-restore...then tried reboot from cwm again...if that didnt work then do adb again to get to recovery and flash nandroid again...dont give up. If you want stock keep trying.
You could flash ur cm again to get working on ur phone again but thats not what you want is it?
Sent from my LG-P999 using XDA
If you cant boot into an android you can use adb to push files to ur sd card...If you dont want to do that then ull have to flash cm n use file manager of choice.
Sent from my LG-P999 using XDA
I would offer my e739 stock backup...but i got it from a third party..and it has extra bloat and carrier iq on it. so im keeping it in a safe place.
Sent from my LG-P999 using XDA
Id trade you LOL... mine wont root
Sent from my LG-E739 using xda premium
I don't know how to get adb to work. I downloaded the sdk and jdk but don't know how to set the path. I wiped data, cache, dalvik, and battery stats before I tried to restore. Still running cm7 but upgraded to the RC. It's quite smooth. Scared to try another restore since each time it stops I get a bootloop and have to hard reset to get back into recovery. And Odin doesn't support my lg. :-( any other suggestions?
Sent from my LG-E739 using xda premium
If you lived close enough I would willingly trade. No lol. Real talk! But have you tried unlock root? Our worked like a charm on my e739.
Sent from my LG-E739 using xda premium
To get adb working put phone in debugging mode
applications>development>tick debugging mode
Connect via usb..start>run>cmd type: cd c:\androidSDK\platform-tools
press enter
you can now type adb commands
type: adb devices hit enter that will show you connected devices
to get into recovery type: adb reboot recovery
device should now reboot into recovery
Sent from my LG-P999 using XDA
Well still not able to get adb for ask to work but on a brighter note, I finally got my phone to restore to stock. Wiped everything 3x's factory/data reset, cache, and dalvik. Then I formatted my system,hit restore, and voila! It went back. Back to cm7.2 RC since TMobile now wants to charge extra to tether. Even tried ICS or cm9 but think I'm gonna wait till there is a more stable version
Sent from my LG-E739 using xda premium
well have you tryed one of many of the apps on the market to unroot it, but i cant help you with the restoring your backup if you cant restore it from cwm without problems because i have a galaxy s gt i9000
I already know how to unroot was having a prob restoring tmobiles software but its all good now!
Sent from my GT-P7510 using xda premium
I wiped system when I was flashing a new ROM and the ROM did not flash correctly so I tried to reboot and manually put into recovery but the phone will only boot to white HTC screen. I don't know if there is anything else I can do to force the phone into recovery? I tried the volume up/down with power every way I could.
Thank you for the help in advance!
Sent from my Nexus 4 using xda app-developers app
Keep holding power button and volume down for awhile it will put you into recovery
Just to let you know please search the forms before starting a new thread because this issue has been answered more than one time in this section. Not trying to be mean but it's an easy way to fix it. Just side load the rom.
Sent from my HTC6435LVW using xda app-developers app
As promised a while ago now we have an official twrp support from TeamRecovery.
All credits and hard work is due to those guys.
Am just here for the announcement and download links which i ask and got permission for.
So time for the main dish
Enjoy TWRP OFFICIAL!!!
Disclaimer:
http://www.teamw.in/project/twrp2/183
Download Links:
http://goo.im/devs/OpenRecovery/acclaim
http://techerrata.com/browse/twrp2/acclaim
And as always Enjoy your Nooks!
Didn't see this coming Awesome work! Now I'm waiting for 4.3 AOSP to fully release (it might have, not sure) I'm totally ready to compile!
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
So to flash this, we open cyanoboot -> start fastboot, and then
Fastboot flash recovery openrecovery.IMG?
Sent from my Barnes & Noble Nook Tablet
That is correct. :good:
Is this compatible with the CM updater for automatic flashing?
Sent from my Barnes & Noble Nook Tablet using Tapatalk 4 Beta
Yup.
Sent from my Galaxy Nexus
I installed via Goo Manager, as recommended by the TWRP web page. All seemed to go normal but I have a problem with all the buttons "sticking" while in the recovery. Especially the keyboard. I reflashed & things seemed a little better but still there. I did do a couple BU's & was given the "Successful" reply. Has anyone experienced this button problem or is it just my flashing-thru-the-app problem?
Sent from my Barnes & Noble Nook Tablet using Tapatalk 2
What is the difference between TWRP and CWM recovery? Is there a benefit this has over CWM?
djd338 said:
I installed via Goo Manager, as recommended by the TWRP web page. All seemed to go normal but I have a problem with all the buttons "sticking" while in the recovery. Especially the keyboard. I reflashed & things seemed a little better but still there. I did do a couple BU's & was given the "Successful" reply. Has anyone experienced this button problem or is it just my flashing-thru-the-app problem?
Sent from my Barnes & Noble Nook Tablet using Tapatalk 2
Click to expand...
Click to collapse
I get the "sticky" buttons on this release, as well as the previous TWRP for acclaim. I've learned to just deal with it, it is still a bit easier to use than CWM.
Agree & thx. I can live with the button prob vs the other recovery also. Just wanted to confirm if it was only me.
Due to the fact that is official its fixable but I think we should migrate to emulated SD cards in 4.3 so I have to talk with kuzma first.
Στάλθηκε από το LG-P880 μου χρησιμοποιώντας Tapatalk 2
rajsris said:
So to flash this, we open cyanoboot -> start fastboot, and then
Fastboot flash recovery openrecovery.IMG?
Sent from my Barnes & Noble Nook Tablet
Click to expand...
Click to collapse
I just got the nook 8gb today with an 8gb microsd card already flashed with CM10 4.1.2 and am new to its development. Sorry for the noob questions but how do I access cyanboot to get to fastboot to flash TWRP?
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Reboot. If it has the CyanoBoot bootloader, then at the beginning of the boot cycle you'll get a prompt to "hold 'n' for menu". It's there in the menu. I've always used the Goo Manager app which flashes the recovery for you. Never had a problem, & is what I used to get 2.6.0.0 installed. Beware the "sticky" button issue tho. Works fine other than that.
Sent from my Nexus 7 using Tapatalk 2
djd338 said:
Reboot. If it has the CyanoBoot bootloader, then at the beginning of the boot cycle you'll get a prompt to "hold 'n' for menu". It's there in the menu. I've always used the Goo Manager app which flashes the recovery for you. Never had a problem, & is what I used to get 2.6.0.0 installed. Beware the "sticky" button issue tho. Works fine other than that.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Upon boot it shows N2ACards which is the program that was originally used to make the SD bootable of CM10 4.1.2. (This is secondhand info from the guy I traded this off of on craigs list.) It doesn't show the cyanboot bootloader or the n menu prompt. So the Goo Manager app is an alternative to flashing the recovery through cyanboot boot loader? What steps do I take to flash the recovery via Goo Manager?
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Juanito216 said:
Is this compatible with the CM updater for automatic flashing?
Sent from my Barnes & Noble Nook Tablet using Tapatalk 4 Beta
Click to expand...
Click to collapse
Where can I get the CM updater. I'm currently on CM10 4.1.2
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
It's in the settings in About Tablet
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Any updates on the "sticky" button issue?
Sent from my Barnes & Noble Nook Tablet
I see TWRP updated to 2.6.1.0 which I also updated using Goo Manger with no problem, But buttons are still sticking. Using the recovery is a small chore & don't even think about trying to name a backup! Other than that it does Backup & Restore... so far.
Sent from my Nexus 7 using Tapatalk 2
djd338 said:
I see TWRP updated to 2.6.1.0 which I also updated using Goo Manger with no problem, But buttons are still sticking. Using the recovery is a small chore & don't even think about trying to name a backup! Other than that it does Backup & Restore... so far.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The sticky keyboard is a huge PITA, for sure. I did manage to name a backup but it took nearly 20 minutes to do so.