I managed to dual boot to Ubuntu thanks to lilstevie
http://forum.xda-developers.com/showthread.php?t=1191141
But then I went to install Prime ROM 1.7 (thanks to Roach2010 great work).
http://forum.xda-developers.com/showthread.php?t=1191387
I've used the flash provided by rdnetto
http://forum.xda-developers.com/showthread.php?t=1204267&highlight=rom+3.2&page=15
Tried download-ubuntu.sh and lilsteview download.sh but I am unable to boot to Ubuntu anymore since lilstevie uses recovery mode to boot to 2nd OS.
Right now it would bring up clockworkmod recovery. ANyway to disable that and boot back to Ubuntu like before?
Thanks everyone.
Related
Totally n00bed my Nexus S.
Was running the latest Miui and installed ROM Manager. Decided to download stock Android and install.
Now the phone is boot-looped (stuck on the Nexus boot image) and Recovery seems to be gone.
I tried pushing the recovery image file but adb won't detect the device.
Any advice?
I had that once when I installed stock. I fixed it by going into recovery and clearing cache and dalvik
Sent from my Nexus S using XDA App
I can't boot into recovery though - It's missing.
theadb said:
Totally n00bed my Nexus S.
Was running the latest Miui and installed ROM Manager. Decided to download stock Android and install.
Now the phone is boot-looped (stuck on the Nexus boot image) and Recovery seems to be gone.
I tried pushing the recovery image file but adb won't detect the device.
Any advice?
Click to expand...
Click to collapse
you need to install the proper nexus s drivers.easiest way is to go to the pdanet website http://junefabrics.com/android/ , download their free product, and let it install the drivers for you. did you flash the recovery through rom manager originally? anyways, then wipe(data. factory reset) and reflash the stock rom. you always have to wipe before flashing a DIFFERENT rom, or youll get stuck in a bootloop.
I installed the 64-bit drivers from PDA already but I'm running XP 64-bit (could that be the issue?)
theadb said:
I installed the 64-bit drivers from PDA already but I'm running XP 64-bit (could that be the issue?)
Click to expand...
Click to collapse
maybe?????
Will adb still work even though I can't boot my phone and turn usb debugging on?
Unfortunately I have 64-bit windows at work, but I'll try on my Win7 or Mac at home.
Still can't get adb to or fastboot to recognize the device...maybe I'm missing something...
I have no recovery and can't boot - what can I do?
Bump. In the exact same mess.
I was on MIUI ICS and tried to go to a stock GB rom, ended up stuck at the boot animation in the fresh rom (which kept looping). Recovery was a no-go too. I tried using adb to push another stock rom which again, installed but got stuck at the boot animation. After that even adb stopped detecting the phone.
What do I do now? theadb how did you fix it?
ADB is working as I plugged in my HD2, which was detected immediately.
Er bump?
Use fastboot to flash a new recovery, then boot into recovery and do what is needed. Recovery will probably be replaced by stock each time you attempt to boot into android while the stock ROM is installed.
I'm in the exact same situation and I don't really think there's anything we can do. We can't enter fastboot. We can't go into download mode. We can't boot into recovery there is literally zilch that we can do to fix the phone.
Finally dusted off the Gtab to give to my son as a gaming console (Im using a samsung galaxay 8.9 now).
It was rooted with flashback honecomb which im pretty sure is a 1.2 bootloader...at any rate it kept deleting his games so i went to flash it to something else, re acquaitned myself with NVflash and then boom, bootloop.
Then i remmebered the orginial flash was probably bootloaded 1.1 so i did the reformat process and then reinstalled the orginal nvflash tnt and it boot loops again.
At this point i dont know if its a partition issue or what.
I decided to just flash right to a different rom and my CWM is totally gone corrupt (possibly in the reformat process)..so now i have no CWM and no way to install CWM because i get a boot loop every time i run NV flash.
So.., i found a recovery method to flash CWM using nvflash..it runs but will not boot into cwm still.
Now im thinking maybe use nvflash to flash a room directly.....like vegan tab maybe?
Whats the command for flashing a vegan rom directly using nvflash????
or....link me to another method of using NVflash to directly install another version of CWM
Or....maybe a link to a different version of NVflash (rather than the original...i saw Roebeets mention of other updated versions on "his site' but alas....i did not see a link to those updated versions in the thread).
3.5 hours into this and about to chunk it...
Any help appreciated.
Try nvflashing both CWM-2.5.1.1-bekit-v0.8 (for the 1.1 bootloader) and CWM-3.0.2.8 (for the 1.2 bootloader).
Try booting into CWM (power off, then hold Power and Vol +) after each nvflash.
If you can boot into CWM, then
a) Repartition the (internal) SD card.
b) Format cache.
Hi all !
First my apology for the reason of those words. I'm an Android-noob
Well I've Rooted my TF101 with EasyFlasher, it's a good thing, installing RogueXM Touch v1.5.0-R1 Recovery.
I launched an AOKP JB milestone 1 and it was well installed.
But I did a mistake, I didn't done a NAND backup.
Now when I try running my TF101, it starts, and run the AOKP JB Milestone 1, but no keyboard, no configuration, well I'm stuck there. Anyway I reboot in recovery trying install another rom pushing file into it by ADB.
Nothing works
I can't reflash Stock rom, EasyFlasher tall me that's ok but when I boot the TF101 I'm always return under AOKP
I don't know who could I flash the Stock rom to be able to repair this $*%£ tablet
If someone has a clue ?
Thank you
[Q] means you should post it in Q&A.
This is the development forum.
sorry I just realize I'm not in the good forum
Since you cannot boot, there are really only 2 options:
Use ADB when in recovery to unbrick (Push new ROM to flash, use the dd command to install a different recovery) - also, be sure to update to the Naked Drivers for ADB for it to work best.
Use APX mode and EasyFlasher or NVFlash to push the stock ROM or a different recovery.
I HIGHLY recommend using TWRP for recovery, it can see the internal and external microSD (FAT32 only).
Moved to correct board.
frederuco said:
Since you cannot boot, there are really only 2 options:
Use ADB when in recovery to unbrick (Push new ROM to flash, use the dd command to install a different recovery) - also, be sure to update to the Naked Drivers for ADB for it to work best.
Use APX mode and EasyFlasher or NVFlash to push the stock ROM or a different recovery.
I HIGHLY recommend using TWRP for recovery, it can see the internal and external microSD (FAT32 only).
Click to expand...
Click to collapse
Well I did that.
But I had big troubles to win
I flashed ics_92117_WW_stock_EBT_SOS.zip and then the AOKP JB Milestone who's working perfectly
I'm trying to dual boot Firefox. os and king kang aokp I replaced the updater script and oc kernel. provided by 7alvi but. after I install it and rebooted I can't even see the boot animation (boot loop ) also I partitioned at correct size and order
also that in other roms oc kernel doesn't. work
please help it says it has no os installed when i go to recovery mode is there a way i can install it with an sd card? where can i download it from please help
Friend - how are we supposed to help if you give us NO information????
How did you get yourself into this pickle?
I used the coffee grounds from my afternoon latte to guess this:
You have a custom recovery installed and can boot into it - which one?
You wiped from recovery and included your system partition. Not a good idea if you're not prepared to flash the rom right afterwards....
You ran some custom rom - which one?
What bootloader do you have installed?
Fastboot access working or ADB in recovery?
If you're really lucky all you have to do is copy your favorite custom rom on a fat32 formatted microSD, stick it in the tablet, boot to recovery and flash the rom.
That is if you have the correct bootloader and recovery installed, but how would I know?