Related
I tried to install overcome 8.9 v2.3.1.
but I download the update & not the FULL zip [TEH N00B]
to make things worst I did not backup my system !!!!!!
I can access to the CWM-recovery so im not afraid of my tablet bricked
but the only zip i do have is not complete,
how i can move the the proper file to the tab?
or I need to go the odin route?
in that case what rom should I use?
many thanks
Don't have my tab with me at the moment but doens't the tab show up on a computer if it's in download or recovery mode?
Are you using CWM 5.5.0.4? if yes here is my suggestion...
First you need adb installed on your computer..
Second, you already have overcome full zip file..
This is the step..
Connect your device with computer
From device, Go to recovery - advance menu - mount /system and mount /data
From your computer go to adb terminal and type this
Code:
adb shell "ls /data/media/"
If you can see list of file from your device sdcard, so you make adb work for your device ..
Place your zip file on your path, says on C://overcome.zip and you want to copy the file to /sdcard/download/
This is the code
Code:
Adb push overcome.zip /data/media/download/.
wait for copying progress done..
After you done with moving file to device sdcard check content of your sdcard with this code
Code:
Adb shell "ls /data/media/download/"
When you found your file from list, you can flash overcome.zip from recovery
Thanks for you quick answer
I do have recovery 5.5.0.4
I can get to mount /system & mount/data
when i go to adb and use the command to list the files i got this error
C:\android\sdk-windows\platform-tools>adb shell "ls /data/media/
- exec '/system/bin/sh' failed: No such file or directory (2) -
and tryng to do this command i got this error
C:\android\sdk-windows\platform-tools>adb get-state
unknown
seems like the device is connected
i tried this and the tablet rebooted (not in recovery but reboot)
C:\android\sdk-windows\platform-tools>adb reboot-bootloader
many thanks
Ok I found the way to make that work
i post the reply maybe can help someone else.
suwandiapr should get the credit anyway.
In a phone you have one wrong rom or somenthing and you can get a good one
and copy that to the sd, in a tablet or any device without microsd you need to push the file using this command adb push
let's say you got a rom called supernoob.zip
adb push supernoob.zip /data/media/supernoob.zip
and remeber if you are using a tablet o phone without sd always keep 2 roms in case
Yes i made a simple batch file for windows in development section...
just bought p7310 today and same boot loop actually
hi all
even if i believed i was a geek with nexus or android phones i was wrong !!!!!i just brick my new P7310 wifi tab
-first i root OK
-after i ran rom manager (so manytimes used with my nexus one...) OK
-i flashed CWM but i chose "10.1" (no 8.9 choice at this time) so when rebooting i got this famous (hum) reboot loop just after the welcome screen "samsung galaxy tab 8.9" ..pffffffffff what a stupid beginer i fell about myself ....
- i tried to go in revovery but the loop appears and appaers .....
so i read and read and read forums and probably the solution or a step to a little begining of solution seems to be here ...
i dl Odin v3 and hope to be able to use it and installing a good version ...
thanks to read me and sorry for my english (i m french)
brunobassman said:
hi all
even if i believed i was a geek with nexus or android phones i was wrong !!!!!i just brick my new P7310 wifi tab
-first i root OK
-after i ran rom manager (so manytimes used with my nexus one...) OK
-i flashed CWM but i chose "10.1" (no 8.9 choice at this time) so when rebooting i got this famous (hum) reboot loop just after the welcome screen "samsung galaxy tab 8.9" ..pffffffffff what a stupid beginer i fell about myself ....
- i tried to go in revovery but the loop appears and appaers .....
so i read and read and read forums and probably the solution or a step to a little begining of solution seems to be here ...
i dl Odin v3 and hope to be able to use it and installing a good version ...
thanks to read me and sorry for my english (i m french)
Click to expand...
Click to collapse
Go to dowload menu and try to flash stock recovery in your tab..
Here is the stock recovery for p7300/p7310
Start odin, and put the file in pda slot..
Please see entire thread for your own safety..
I'm trying to get the ZIP file copied to the sdcard. I have followed Verygreens instructions and have the imaged burned and able to boot into CWM.
I have ADB up and working. When I copy the ZIP file to the SDCARD with ADB with this command: "adb push cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip /sdcard" the ZIP does not show up in CWM when you go to install zip from /sdcard.
When I do a directory list in ADB the ZIP shows up in internal memory.
In the Nook android developer documentation the external sdcard is referenced as /ext_sdcard and the internal card as /sdcard.
When I try to push the file to /ext_sdcard I get a permission denied error.
Are verygreens instruction for Lunix not PC. I'm using Windows 7. I've got all the parts working I just can't get the ZIP file to where it needs to be.
Can you install the ZIP from the internal memory? instead of the sdcard?
Any help appreciated.
knotmeter said:
I'm trying to get the ZIP file copied to the sdcard. I have followed Verygreens instructions and have the imaged burned and able to boot into CWM.
I have ADB up and working. When I copy the ZIP file to the SDCARD with ADB with this command: "adb push cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip /sdcard" the ZIP does not show up in CWM when you go to install zip from /sdcard.
When I do a directory list in ADB the ZIP shows up in internal memory.
In the Nook android developer documentation the external sdcard is referenced as /ext_sdcard and the internal card as /sdcard.
When I try to push the file to /ext_sdcard I get a permission denied error.
Are verygreens instruction for Lunix not PC. I'm using Windows 7. I've got all the parts working I just can't get the ZIP file to where it needs to be.
Can you install the ZIP from the internal memory? instead of the sdcard?
Any help appreciated.
Click to expand...
Click to collapse
Are you using ADB WITH CWM? It soudns like you have adb going with the nook booted to stock. You boot to CWM, then go to mounts and storage, mount the /sdcard, THEN adb with CWM running and copy the zip over.
ADB not working with CWM
dbh369 said:
Are you using ADB WITH CWM? It soudns like you have adb going with the nook booted to stock. You boot to CWM, then go to mounts and storage, mount the /sdcard, THEN adb with CWM running and copy the zip over.
Click to expand...
Click to collapse
If I boot the NOOOK HD+ into CWM and mount the sdcard, then ADB will not connect to the NOOK, I do the adb devices command and no devices are found.
If I do the push command anyway, I get a "no device found error". If I tale the sdcard out and boot to stock CWM works again.
What am I doing wrong?
knotmeter said:
If I boot the NOOOK HD+ into CWM and mount the sdcard, then ADB will not connect to the NOOK, I do the adb devices command and no devices are found.
If I do the push command anyway, I get a "no device found error". If I tale the sdcard out and boot to stock CWM works again.
What am I doing wrong?
Click to expand...
Click to collapse
I'm having the exact same problem, adb finds device when booted into stock, but when I boot with cwm adb can't find it.
lemdaddy52 said:
I'm having the exact same problem, adb finds device when booted into stock, but when I boot with cwm adb can't find it.
Click to expand...
Click to collapse
Scroll down to where verygreen's post says "If you don't have operational adb...." and follow instructions from there.
lkmiller said:
Scroll down to where verygreen's post says "If you don't have operational adb...." and follow instructions from there.
Click to expand...
Click to collapse
Thanks but that's why I got adb working, because I can't see the correct partition in windows to copy it there. Is there a reason adb is working in stock and not on the cwm image? Is there a way to fix it?
lemdaddy52 said:
Thanks but that's why I got adb working, because I can't see the correct partition in windows to copy it there. Is there a reason adb is working in stock and not on the cwm image? Is there a way to fix it?
Click to expand...
Click to collapse
No clue as far as adb. Reading through the thread, some people used a linux vm or a linux cd to see the correct partition.
lkmiller said:
No clue as far as adb. Reading through the thread, some people used a linux vm or a linux cd to see the correct partition.
Click to expand...
Click to collapse
Ok, got it. What mine did when booted to cwm was find the nook hd+ and wanted to install drivers for it. But the adb devices driver would'nt work. What i did was right click on the hd plus device and selected update driver and installed the same driver as for the adb interface. When I did that the nook hd+ disappeared out of device manager and the adb interface device showed up and it worked. Thx for the help trying to get it. Hope this helpes someone else.
Device ID problem solved ADB working in CWM
I figured it out. When using Windows 7 64bit the device ID for the nook HD+ running CWM is incorrect in the android_winusb.inf.
After you plug your Nook HD+ into your PC, look in device manager for "NOOK HD+" under other with a question mark next to it.
Right click on properties and then go to the details tab. Look for the device ID. This is the ID that should be in the android_winusb.inf file.
My inf file had this line for the NOOK HD+
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0005&MI_01
The device ID on my system for the Nook HD+ was VID_18D1&PID_D001 so I changed the entry in the INF file to:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
There may be more than one copy of this line in the INF file. Be sure to change them all.
Save the file then unplug the NOOK usb and plug it back in. You should see the Android composite ADB interface start working in device manager.
Now you can use ADB to push the ZIP file to the sdcard.
Remember you need to mount the sdcard in CWM before doing this.
knotmeter said:
I figured it out. When using Windows 7 64bit the device ID for the nook HD+ running CWM is incorrect in the android_winusb.inf.
After you plug your Nook HD+ into your PC, look in device manager for "NOOK HD+" under other with a question mark next to it.
Right click on properties and then go to the details tab. Look for the device ID. This is the ID that should be in the android_winusb.inf file.
My inf file had this line for the NOOK HD+
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0005&MI_01
The device ID on my system for the Nook HD+ was VID_18D1&PID_D001 so I changed the entry in the INF file to:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
There may be more than one copy of this line in the INF file. Be sure to change them all.
Save the file then unplug the NOOK usb and plug it back in. You should see the Android composite ADB interface start working in device manager.
Now you can use ADB to push the ZIP file to the sdcard.
Remember you need to mount the sdcard in CWM before doing this.
Click to expand...
Click to collapse
^^ All I can say is THIS solved my problem. Working on this for 2 days and finally stumbled upon this post.
I was never able to copy the CM file because everytime I rebooted the Nook HD+ to CWM mode ADB would
stop being able to recognize it because it reloaded in Device Manager as "Barnes & Noble Nook HD+" instead
of the generic device ADB used when booted into Nook mode.
For anyone unable to get ADB working because it will not recognize the Nook HD+ once in the CWM, Try this. :good:
I too am having this same problem. I can write the image file to the sd card but after the nook re-partitions the card, my computer only sees the E:boot. When I look at the sd card with a partition manager, I can see the 4 partitions that were created but only boot has a letter designation.
How can I copy the cwm and gapp files to the cm10sdcard partition or how can I make adb function? Even with adb, will i see the added partitions? Please help. I am using a Nook HD+ and following Verygreens instructions for cm10. Also, are there other zips that are useful to copy to my card?
kedijoka said:
I too am having this same problem. I can write the image file to the sd card but after the nook re-partitions the card, my computer only sees the E:boot. When I look at the sd card with a partition manager, I can see the 4 partitions that were created but only boot has a letter designation.
How can I copy the cwm and gapp files to the cm10sdcard partition or how can I make adb function? Even with adb, will i see the added partitions? Please help. I am using a Nook HD+ and following Verygreens instructions for cm10. Also, are there other zips that are useful to copy to my card?
Click to expand...
Click to collapse
Ok try!
You are done with this:
For first time install only (you will need 4G or bigger sdcard, smaller ones are not supported and not tested):
gunzip cwm image and write it to your sdcard (entire sdcard not just one partition of it), use either dd on Linux/MacOS or Win32 Image Writer for those impaired by Windows. Make sure to use sdcard rated for fast small IO for best results.
Click to expand...
Click to collapse
Now next step:
Insert the card into the Nook and reboot the nook, CWM should start.
(This will also automatically repartition the card into a correct layout no matter the size (but no smaller than 4G).
In the CWM:
Go to "mounts and storage", choose "mount /sdcard".
Click to expand...
Click to collapse
Now connect your device with USB cable to PC and continue with guide:
Press power button to go back to the main menu.
Now do on PC: adb push cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip /sdcard
Click to expand...
Click to collapse
Here goes step when you can use "adb push" command to load any wanted zip or other files to Nook HD+. Actually you can push or send later your apk or other files to Nook HD+ too. This part is only for this, when you need install something before first run (some kernel or mandatory system changing files).
Now next part on CWM:
Next, choose "install zip from sdcard", and then "Choose zip from sdcard" and choose cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip (which one you just copied to device over ADB
Click to expand...
Click to collapse
Done? Ok next step:
When done installing, press the power button to go one level up in the menu and then choose reboot.
This will reboot you into CM10.
Click to expand...
Click to collapse
Remember! Sometimes it stuck on first boot. Just push power button, device shuts down, remove SD card. Boot your Nook HD+ to original soft, insert SD and shut down Nook HD+. Now power it again and it start with CM 10.
With ADB problems you got solution before on this thread.
I try to inform VeryGreen about making some changes on guide.
knotmeter said:
I figured it out. When using Windows 7 64bit the device ID for the nook HD+ running CWM is incorrect in the android_winusb.inf.
After you plug your Nook HD+ into your PC, look in device manager for "NOOK HD+" under other with a question mark next to it.
Right click on properties and then go to the details tab. Look for the device ID. This is the ID that should be in the android_winusb.inf file.
My inf file had this line for the NOOK HD+
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0005&MI_01
The device ID on my system for the Nook HD+ was VID_18D1&PID_D001 so I changed the entry in the INF file to:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
There may be more than one copy of this line in the INF file. Be sure to change them all.
Save the file then unplug the NOOK usb and plug it back in. You should see the Android composite ADB interface start working in device manager.
Now you can use ADB to push the ZIP file to the sdcard.
Remember you need to mount the sdcard in CWM before doing this.
Click to expand...
Click to collapse
After 3 hours of frustration, you saved me! lol
I do not have ADB running. Is there another way to copy cm10 file (and others) to the cm10sdcard partition? I am trying to go thru Nook Development instructions to get ADB running but it is a pain. Is Android SDK required? Java? Nook emulator?
kedijoka said:
I do not have ADB running. Is there another way to copy cm10 file (and others) to the cm10sdcard partition? I am trying to go thru Nook Development instructions to get ADB running but it is a pain. Is Android SDK required? Java? Nook emulator?
Click to expand...
Click to collapse
You can run ubuntu from a live-cd using VirtualBox.
I don't have ubuntu live-cd or virtualbox. I am still having problems getting ADB to work. I am reinstalling the Android SDK. I just noticed that when it tried to install the Android SDK Platform-tools, the Android SDK Manager came up with Stopping ADB Server failed (code 1). Any help would be greatly appreciated. I am using windows Vista.
Great. Got ADB push to work. You do need SDK Manager, JAVA, I had to copy the cm10 file and gapp file to the system32 file for ADB push to find them. What are other useful zips to push besides gapp and cm10? :victory:
kedijoka said:
Great. Got ADB push to work. You do need SDK Manager, JAVA, I had to copy the cm10 file and gapp file to the system32 file for ADB push to find them. What are other useful zips to push besides gapp and cm10? :victory:
Click to expand...
Click to collapse
Great, glad you got it to work! Sorry for not replying earlier, but in general, both ubuntu and virtualbox are free downloads. I just put those two and get all the other apps from the play store.
Well,
I couldn't get the driver to show up in Device Manager for Win7 64bit when in recovery mode or CWM and then I tried updating driver software in the unknown device.
1. Right click Unknown Device and select Update Driver Software...
2. Browse my computer for driver software...
3. Let me pick from a list of device drivers on my computer...
4. *Choose the top, can't remember the name but it had "List all" or something like that.
5. Have Disk...
6. Go to the folder that has the driver and choose "android_winusb"
7. Choose "Android Composite ADB Interface"
And that's it, ever since it will have the correct driver after battling to get one after it said unknown device in Device Manager Win7.
---------- Post added at 02:51 AM ---------- Previous post was at 02:31 AM ----------
knotmeter said:
1. I'm trying to get the ZIP file copied to the sdcard. I have followed Verygreens instructions and have the imaged burned and able to boot into CWM.
2. I have ADB up and working. When I copy the ZIP file to the SDCARD with ADB with this command: "adb push cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip /sdcard" the ZIP does not show up in CWM when you go to install zip from /sdcard.
3. When I do a directory list in ADB the ZIP shows up in internal memory.
4. In the Nook android developer documentation the external sdcard is referenced as /ext_sdcard and the internal card as /sdcard.
5. When I try to push the file to /ext_sdcard I get a permission denied error.
6. Are verygreens instruction for Lunix not PC. I'm using Windows 7. I've got all the parts working I just can't get the ZIP file to where it needs to be.
7. Can you install the ZIP from the internal memory? instead of the sdcard?
8. Any help appreciated.
Click to expand...
Click to collapse
1. Able to boot into CWM? Good
2. Do yourself a favor and don't rename it with that whole file name, abbreviate it if you can to cm10 or cm20130120. Verify that it transferred, it should indicate the transfer rate and also take a minute or two transferring the whole 100+ MB file, so be patient.
3. That's a good sign
4. I also read that but don't bother with it, here is /sdcard a real SD Card.
5. I didn't do that and got away with it.
6. Mine is Win7 64bit and his instructions on how to burn it were pretty good. Remember this only works on a first time basis, it will not work a second try so you have to reburn the image again and mount sd card and then push it.
7. Nope, so far.
8. Here is mine.
Ok, i got cm10 running, and first loaded gapps 20121130 and always got "unfortunately keyboard has stopped running" error. I saw on another thread that I may have the wrong gapps, so I downloaded gapps 20111011, pushed and mounted it. Still getting the keyboard error. Do I have the right gapps? Do need to uninstall the first gapps before mounting from sdcard the second gapps? Please help. Without keyboard, I can't do much.:frustrated:
PS: Got it going, worked to wipe to factory, reinstall cm10 and gapp 20121011 only. Thanks to leapinlar and all others for you wisdom and help.
Hi all, I wrote a long-winded Tutorial to put Evervolv KitKat on a stock N1. I don't have a stock N1 (I stumbled all the way through this process and got done yesterday, was so excited I wrote this tutorial) and don't know how to get it back to stock, so I'm wondering if anyone who has one and has experience putting new ROMs on other devices would like to test this out and let me know if anything doesn't work as written. Please go ahead if you like and reply your updates! Once it's dialed I'll make it a thread in the N1 ROMs forum.
Here's the text:
How to put KitKat on a Nexus One (And have computing power & space to spare):
Things you'll need:
1. A Windows/Linux computer with internet connection, USB port, and terminal
2. A USB Cable
3. A Nexus One with the most recent stock gingerbread rom (Settings->about, look for Android 2.3.6 or GRK39F, else apply/google updates to get to that version)
Before you begin, note that you're playing with a generally safe form of fire, but when playing with fire, you may brick your phone. The maker of this guide and any sites you visit during the process assume no responsibility, the user assumes full responsibility for lost work and damaged or ruined phones. Your warranty will be voided about six times over. Save all your stuff somewhere, save apps with Titanium Backup (Google it) or something, and do a full Nandroid backup (Goog that too) before you begin. You will be fully wiping your phone and SD card multiple times. Make sure at every step of the process that your battery is at least half full. Running out of battery during an update can cause bricks. In this guide, “Boot” means standard boot, the way it normally turns on. Not hboot or fastboot or recovery.
I did part of this from a Windows7 computer on Cygwin and part on Ubuntu 12.04, each presented some annoyance but by far the greatest was due to my Linux ineptitude with PATH and Root. If you're trying the same, I've made an appendix for that.
It may help to have a brief conceptual overview of what you'll be doing in case you run into snags and have to step out of the walkthrough. Your N1 has a few basic parts: Internal memory that is chopped into 3 partitions: One for the system files (System) , one for the files that they will need to make during the first bootup and use in order to operate, along with your apps and their created files (Data) and one for temporary files that your OS and apps can regenerate (Cache). Somewhere in there it also has space for a Radio (that also includes some critical power functions, flashing a new radio is the easiest way to brick an N1 but we won't), as well as a Recovery partition and an Hboot&Fastboot partition. We will be messing with Recovery and Hboot. The virtual machine that turns all the friendly pseudo-english computer code into 1s and 0s for the processor to deal with is called Dalvik, named after a town in Iceland where some old dev's family is from. It has its own Cache (the VM, not the town, as there are no longer any fish in Iceland ). It's SOP to wipe Cache & Dalvik before and after applying any updates, and wipe Data (Factory reset) before applying most updates. Sometimes when my phone bogs I reboot to recovery and wipe caches just for funsies. This makes it take longer to boot the phone and to use each app just the first time after that, while the files are created fresh. The phone also should have an SD-Card. You should have or buy an 8+MB, Class 10 SD card. The class relates to read/write speed, anything less than 10 will noticeably slow your Nexus One's operation. Why?
Because we're going to put some of your operating system on the SD card. We're going to use a special recovery system (aka recovery ROM) called “4ext” to partition your SD card. Mine is 16GB, partitioned to 14GB for storage and 2GB to use as fake internal memory, where my system's Data and Cache live. The KitKat System files that normally live on internal memory's System partition are too big for a normal N1, so we'll use a special Hboot called BlackRose to repartition your internal memory so you can fit KitKat, and then after you first boot it up we'll use an app called Mounts2SD to install a startup script so that every other time you boot it up after that, it will know to find Data and Cache on the SD card. In order to install BlackRose, you'll need to be running CyanogenMod Rom as your main OS, and in order to do that you'll need ClockWorkMod Recovery ROM. So the installation order will be: ClockworkMod recovery->Cyanogen7OS (Gingerbread based)->4ext recovery to partition SD card->BlackRoseHboot to repartition internal memory->Evervolv KitKat-based N1 ROM-> run Mounts2sd for startup scripts ->reboot to your new life among the anatomically modern cyborgs (and then you're on your own for getting all your apps and music and contacts and stuff back on the phone from wherever you saved it).
Ready? Here we go!
1. Install the Android SDK on your computer.
1. Get the appropriate version here: http://developer.android.com/sdk/index.html
2. Unzip it.
3. Run the setup.exe (if using windows)
4. When asked which packages to install, choose “Android SDK Tools”, “SDK Platform Android 2.1″, and “Usb Driver package” (If you use eclipse, check that last link for instructions on using the ADT plugin (Not the same ADT that cuts your paycheck, much less inept))
5. Make sure the USB drivers installed properly (windows).
1. Go to printers and devices in the control panel, or device manager
2. If you see an android device with no warnings, you're golden. If it has warnings, right click it and go properties->update driver (driver can be found in your android sdk directory where you unzipped the sdk bundle, in \usb_driver).
6. Boot up your N1 and plug it in to the computer. If the computer recognizes it and they play nice, you're set with the sdk. To extra check, open terminal and cd to the sdk's platform-tools folder that should contain the adb utility. Type #adb devices and see if it comes up with a message telling you that it's running a daemon on a port like 5037, and then lists something like HT9CPP800063 device. This is your phone, it's telling you you're beyond connected. You've got the sdk working. Else have your friend Google help you get the SDK properly installed.
2. Root the phone so it will let you dig in.
1. Put your N1 in USB debugging mode (Settings > Applications > Development > USB Debugging)
2. In the terminal, in the platform-tools folder, type #adb reboot bootloader. (((My phone has a power hardware issue and will not reboot while plugged in ever to any mode ever at all ever, if yours does too you can unplug (first type #adb kill-server to make it ok to unplug) the usb cable, power down, wait five seconds, and hold the trackball and power button to power back up into the bootloader, then plug in again. There was a lot of unplugging, waiting fifteen seconds, booting while holding buttons, plugging in, adb devices -ing that I will omit henceforth due to low likelihood that you have the same problem.)))
3. Using the onscreen directions on the phone and the hard buttons, navigate to fastboot mode. It may be unresponsive and throw some not-found messages for five seconds before it lets you do anything.
4. In the terminal on your computer, in the platform-tools folder, type #fastboot devices to see if your devices is connected (it should come up with the same HT#XXX###### number).
5. This step will gain Root access, unlock the bootloader, and WIPE ALL YOUR ****. Now type #fastboot oem-unlock . You may have to accept the warranty voiding. If for whatever reason it doesn't work, use this method http://code.google.com/p/bexboot/, and unzip the files to the platform-tools folder.
6. Using the phone buttons, reboot. Your little lock logo during the bootup should be unlocked now.
7. Power down and boot again for good measure. Re-enable usb debugging in the phone app dev settings.
3. Get ClockworkMod Recovery.
1. Download koush's ClockworkMod Recovery from : recovery-clockwork-5.0.2.0-passion.img and put it in the platform-tools folder.
2. To make sure the file is not corrupted and will not brick your goods, check the md5sum. This is the result of a complicated equation that easily reveals even a single flipped bit in the file by vastly changing the output. Google how to do this, in windows you'll need to download a tool like winmd5free. The output for this particular file should be: md5: 45716c8d51ed2375873f01f0b14b2184 If it's anything else don't use it.
3. Reboot to the bootloader again, either by #adb reboot bootloader or by powering up while holding the trackball, and navigate to fastboot.
4. Verify that you're connected with #fastboot devices
5. Flash ClockworkMod Recovery by typing #fastboot flash recovery recovery-clockwork-5.0.2.0-passion.img
6. It should give a success message. Reboot to recovery from the fastboot menu. It should be a sweet new blue and white ClockWorkMod recovery. Power down and reboot to recovery by holding volume up as you power up, just for good measure.
4. Get CyanogenMod7 ROM.
1. On your computer, go to http://download.cyanogenmod.org/?device=passion&type=stable and download the latest stable CM7 zip. Put it in the platform-tools folder.
2. Check its md5 as you did in part 3.
3. Do #adb-devices, which should give you that serial again, and the word recovery.
4. Place the zip file on the root of your SD card by doing #adb push cm-7.2.0-passion.zip /sdcard/
5. If that last step failed, try running #adb shell mount /sdcard or #adb kill-server then #adb devices then #adb shell mount /sdcard, then try the push again. Or mount the sdcard through the recovery menu before running that push command. Or use your computer's file system to drag and drop the .zip to the root (lowest) folder of the sd card.
6. Using the recovery menu, in backup and restore options, backup your current ROM.
7. In the format menu, do a wipe data/factory reset. Wipe the cache and dalvik cache while you're at it.
8. Back in the main recovery menu, do install zip → choose zip from sd card.
9. Select that CM7 zip file.
10. Return to the main menu and reboot the system. It should come up with a totally different looking leaner meaner version of Gingerbread, that gives you more control and speed and saves battery. But even with this system, given modern app sizes, you'll soon run out of room on the internal memory if you stop now. And besides, you're having too much fun.
5. Get 4EXT recovery
1. Go to 4ext.net and download the free .apk file: http://www.4ext.net/get.php?apk Congratulations if you're about to install your first not market app (apps are now .apk, not just something you get from the store's GUI.). Save it in platform-tools. Or, to be really nice to Max, you can just buy the app in the play store and skip the next two steps.
2. Enable USB debugging, plug in and #adb-devices.
3. # adb install 4EXTRecoveryUpdater.apk. You should get back a success message in a fistful of seconds.
4. At this point you may need to back out to regular settings, turn on wifi, and hook up to your wifi router.
5. Open the 4ext recovery updater app. Go to settings. Allow superuser permissions and everything else. It should detect Nexus One, connect to the internet, and boot you back to the main menu.
6. Go to online install. They're all release candidates and no stable versions, so just go with the newest one. Select install.
7. Wait for it to finish and then reboot to recovery, either by # adb reboot recovery or manually. You should have a beautiful new touchscreen recovery.
6. Partition your SD Card
1. In recovery, go to tools->partition sd card->remove all partitions and start from scratch.
2. For the first Ext partition, where you'll be keeping a good chunk of your OS, The consensus online is not to go above either 1.5GB or 2GB. I'm working fine with 2GB aka 2048MB.
3. You can skip the 2nd Ext partition.
4. The internet says Swap size should be 0.
5. Internet says File system should be ext4. This should do the partitioning, the rest of your SD card will still be great for storage as before.
7. Repartition internal memory using BlackRose:
1. I have never used BlackRose on Windows, but here goes: go here : http://forum.xda-developers.com/showthread.php?t=1270589 and download this zip archive: http://forum.xda-developers.com/attachment.php?attachmentid=1016437&d=1334971685; It has windows and linux files. The site also has a manual in case this walkthrough lets you down.
2. Unzip it into a folder in your platform-tools. Execute it with a ./ in linux or a .exe in win. It should say waiting for devices.
3. Reboot your phone manually. BlackRose should hijack the startup, install itself, and quit. Boot your phone up again.
4. Blackrose is rumored to have an interactive guide to partitioning, but it didn't work for me and at least some other genius on the internet, but being an industrious Austrian, he figured out the fix: Run Blackrose in Editor mode. Type resize as prompted.
5. The post here http://forum.xda-developers.com/showthread.php?t=2540366 on Evervolv KitKat implies that 250MB for System works with enough space for Gapps (Google does not allow their standard apps like Play Store to be included with Mod roms anymore, so you will need to install them from recovery too, but they distribute them bundled so it's not hard.), and some commenter said 260MB, but that didn't work for me long enough to run startup scripts and move some of it off. So I had to redo it and I went with 265MB for System and 10MB for Cache, which is working fine. Give it a name, I went with Kat.
6. BlackRose will shut down, but it will leave a golden turd in the form of a file called hboot_brcust.nb0 probably in the folder called “other.” That's what you want.
7. Put that file in the same folder as the Blackrose utilities fastboot-l and fastboot-w if it's not already there. Then boot your phone into fastboot again, via adb or manually. I think. Maybe try this from being standard booted up if the next part doesn't work.
8. Run # fastboot-l flash hboot hboot_brcust.nb0 . Windozers should use fastboot-w instead. Blackroot will wait for the device again.
9. Reboot your phone into the bootloader manually, by holding the trackball while powering up. The image should install on this boot, resizing your phone's internal memory partitions.
10. Run # fastboot -w. Your Bootloader should be loaded up, with the 1st line saying something about BlackRose and the 2nd line saying 265/10/161. This is how you know it worked. That 265 is where it's at for KitKat. Your main OS had been destroyed, but your Recovery ROM should still work.
8. Install Evervolv KitKat.
1. Go here http://evervolv.com/devices/passion and download the latest stable release. At press time that's the 4.0.0p4.2 version. Save it to platform-tools.
2. Reboot to Recovery from the menu in the BlackRose bootloader.
3. Do # adb devices. Then do # adb push ev_passion-4.0.0p4.2-perdo-squished.zip /sdcard/ . If it doesn't work, try using the touch recovery menu to toggle mount USB, then push, then unmount. Or mount USB, use the computer's file system to move the file to the root of the sd card, then unmount USB. Or try as root if you're using linux.
4. From the main recovery menu, select install zip from SD card → choose zip → select the ev_passion-4... zip. Wait up, it could take a while.
5. Success!! Right? Right. #adb kill-server, you can unplug now and won't need to plug back in! Reboot the phone, you're getting perilously close! This boot could take five plus minutes, or just one, but be patient.
9. Install Gapps.
1. You are such a lucky dog. Gapps bundled updates are available through the Evervolv toolbox. So you can get Play Store and everything else will come easy. Go to settings → wifi, turn it on, hook it up to your wifi router.
2. Back up to settings, and go Evervolv Toolbox → Updates and swipe over to the Gapps section. Tapp the most recent Gapps-kk zip. Tap the down arrow to download.
3. Reboot manually to recovery.
4. From the main recovery menu, select install zip from SD card → choose zip → select the gapps-kk... zip. This could also take a sec.
5. Reboot again! You're almost done! When it's all loaded up, Play Store should now be installed, as well as various google options that you can enable through the Evervolv settings.
10. Install Mounts2sd.
1. Go to the Play Store and get Mounts2sd.
2. Hit the top right corner for application settings. You'll need to install a startup script. Agree, give it permanent superuser status.
3. Reboot.
4. Go back into Mounts2sd, and go to the Tool menu (Wrench). Note that boxes aren't checked unless they're green-checked.
5. Enable the Cache to move cache partition to data or sd-ext. Storage threshold is up to you. Make sureApplications, Libraries, Data, and Media are all checked. Dalvik should stay unchecked, System apps can too.
6. Reboot again.
11. You're done!!! Or at least we're done. You still have to restore your apps and put all that music back on and figure out how to resync your contacts and... Good Luck.
12. If you want to get extra tricky, it's believed to be possible to leave app data on the real internal memory by default, and use Titanium Backup to move the data of most of your apps to the SD-ext, thereby leaving the data of your favorite apps on real internal memory. Use at your own risk.
ENJOY!!
Appendix 1:
Linux PATH env: I put all my android stuff in a file called androidy, so my path to my platform-tools was /androidy/adt/sdk/platform-tools, and my blackrose was in there too. So to set my PATH, I used: $ export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/sean/androidy/adt/sdk/platform-tools:/home/sean/androidy/adt/sdk/platform-tools/blackrose_120421/binary"
In order to make sure that while using it as root (as was necessary for some fastbot operations), I referenced the same PATH instead of the messed up root PATH, I used sudo env PATH = $PATH a few times.
Appendix 2:
The only actual bug I've noticed in a few days with this ROM is that my Chrome bookmarks don't add shortcuts to the homescreen when I tell them to from within Chrome. The widget-adder (longpress homescreen) has a bookmark option though, so if you bookmark it you can put it on the homescreen from there.
Huge Thanks to everyone involved with ClockworkMod, Cyanogen, 4Ext, BlackRose, and Evervolv!
Sources:
http://wiki.cyanogenmod.org/w/Install_CM_for_passion
http://nexusonehacks.net/nexus-one-...n-how-to-unlock-bootloader-on-your-nexus-one/
http://marian.schedenig.name/2012/07/22/installing-android-4-ics-on-the-google-nexus-one/
http://forum.xda-developers.com/showthread.php?t=2540366&page=24
Wooooh, Amazing book ! Everything is soo.... deep. In my opinion, tutorials should be only few lines.
Some mistakes :
Why installing CM7 and then backing up ? (You can install non market apps without CM7, and when flashing CM7 you erase all user data)
Why using m2sd if the rom has a built-in feature called a2sd ?
Why installing CWM then 4EXT recovery ? (TWRP is a touch one, and you can flash recovery once you have root access)
"You should have or buy an 8+MB, Class 10 SD card" ? typo ?
In my mind, big steps should be :
1) Backup SD, and SMS and Apps
2) Root
3) Install recovery (TWRP is advised by evervolv, but CWMRecovery is OK)
4) Partition SD
5) Install Blackrose (using 260mB system)
6) Flash ROM
7) Flash GAPS
8) A2SD Y N Y
Notes :
About SD-Ext size, i recommend reading this post from his creator : http://forum.xda-developers.com/showthread.php?t=1716124
A2SD is an old version of INT2EXT+
Using terminal is not friendly for beginners. Avoid it at maximum.
Provide a link for a MD5 sum checker.
I don't know if it works with actual stock rom, but when i rooted my n1, i used SuperOneClick. Plug, Click, Wait, Smile. (I still have it if needed)
ldFxl said:
In my opinion, tutorials should be only few lines.
Click to expand...
Click to collapse
This tutorial doesn't need to exist at all. All the information is available elsewhere on the internet, I did nothing original. Its only value is that it puts all the information in full detail in one place so you don't have to look in the forums for elaboration on each line of a more concise tutorial. Hopefully with info this detailed, someone with more chops than me could script it.
ldFxl said:
Why installing CM7 and then backing up ? (You can install non market apps without CM7, and when flashing CM7 you erase all user data)
Why using m2sd if the rom has a built-in feature called a2sd ?
Click to expand...
Click to collapse
I had already installed CM7 when I thought to write this, Marian (my 3rd source) seems pretty skilled as he is the only one who could make BlackRose work for me so I trusted his advice that it was the easiet procedure he found. Have you put TWRP Recovery on from stock after unlocking the bootloader (fastboot oem unlock)? And have you successfully repartitioned SD (fat32 &ext4) from TWRP? If so and you want to quickly write up the steps, I'd gladly replace my steps 3-6, that would save people a lot of time and doing.
ldFxl said:
Why installing CWM then 4EXT recovery ? (TWRP is a touch one, and you can flash recovery once you have root access)
Click to expand...
Click to collapse
4EXT is also touch, CWM cannot repartition SD. If you can go stock to TWRP this might be the best option. Or if not, stock to 4ext.
ldFxl said:
"You should have or buy an 8+MB, Class 10 SD card" ? typo ?
Click to expand...
Click to collapse
Yes! Thanks.
ldFxl said:
Using terminal is not friendly for beginners. Avoid it at maximum.
Click to expand...
Click to collapse
Don't you have to use terminal to use the built in A2SD? At any rate, it didn't work for me (I'm kind of a beginner), Mounts2SD's GUI seemed a little more beginner friendly. Also I certainly wouldn't have been able to make BlackRose work
ldFxl said:
Provide a link for a MD5 sum checker.
Click to expand...
Click to collapse
Good idea
ldFxl said:
I don't know if it works with actual stock rom, but when i rooted my n1, i used SuperOneClick. Plug, Click, Wait, Smile. (I still have it if needed)
Click to expand...
Click to collapse
I once used SuperOneClick on another phone, it looked like it struggled and finally worked with a DDoS style attack, it seemed simpler to just do it the way the manufacturer intended (if that's even a thing). But I suppose if it works with one click it really is simpler as seen by the user. Anyone have a report on whether it worked from stock N1?
Fituate said:
I had already installed CM7 when I thought to write this, Marian (my 3rd source) seems pretty skilled as he is the only one who could make BlackRose work for me so I trusted his advice that it was the easiet procedure he found. Have you put TWRP Recovery on from stock after unlocking the bootloader (fastboot oem unlock)? And have you successfully repartitioned SD (fat32 &ext4) from TWRP? If so and you want to quickly write up the steps, I'd gladly replace my steps 3-6, that would save people a lot of time and doing.
Click to expand...
Click to collapse
On my first flash, i was pretty beginner, so i followed a tutorial ; ) . And they used CWM. But flashing a recovery procedure from .img file doesn't differ with the recovery. TWRP allows you to partition SDCard. I did it last week (on HTC wildfire S, TWRP 2.6 as for N1).
Flashing step is the same -> just replace img file name. You can get it Here (From official TWRP Website)
Procedure from TWRP Website said:
Download the above file. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fasboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Click to expand...
Click to collapse
6. Partition your SD Card
1. In recovery, Tap Advanced
2. Tap Partition SD Card
3. Set 2048 (MB max) on EXT Size and 0 on Swap Size
4. Tap EXT4 then swipe to start partitioning
Fituate said:
3. Reboot your phone manually. BlackRose should hijack the startup, install itself, and quit. Boot your phone up again.
Click to expand...
Click to collapse
Backrose is a custom Bootloader-> it replaces your HBoot/Fastboot
You don't need to reboot your phone to install blackrose. You just need your phone in ADB over USB, then the win setup will install blackrose.
Once done, run setup again, your phone will automaticaly go to HBoot, then choose 1, and 1 again.
Then enter "resize", "260" and "8".
In case that the installer don't work correctly, you can get flashable HBOOT from [Provide a nb0 (texasice recommend 260/8/168) AND MD5 Checksum]
While googling to find some infos (I don't remember me unlocking my bootloader) I found this guide : http://forum.xda-developers.com/wiki/HTC_Nexus_One/Flashing_Guide
Apperently SuperOneClick does not even need unlocked bootloader on 2.3.3 or previous ...
Isn't what we are trying to write down ?
There are many links pointing to this forum aswell.
Disclaimer: I'm relatively new to the realm of modding the the kindle. I have a 2012 7" hd. I rooted it and loaded a 2nd bootloader and recovery via various tutorials. I attempted to to load a rom (lolipop 5.1 and corresponding gapps). The process seemed to go fine and when it booted into android the initial setup screens appeared (connect to wifi etc); but then I got a message that the setup wizard had failed. I tried "skipping" screens etc and regardless of what I did I couldn't get past that screen. I clearly either did something wrong or didn't have a good rom file. I was an idiot and didn't create a backup before flashing the new rom. So I mounted it in recovery and loaded a factory image that way and flashed back to norm. My intention was to start things over. I rooted again, went through the whole process; however, I'm seeing a weird phenomenon. When I am in windows (or ES explorer for that matter) and access the files on the sd card partition...I can load files onto there (for flashing in recovery etc); however, once I am actually in recovery and go to "install" the partition that I view in recovery is the files I had from the very first flash. I can create new files in windows or ES explorer and everything works as expected....but once in recovery, none of those folders are present...and the only zip files that are available to "install" are the ones I used the first time that didn't work. I'm clearly looking at some other partition or image in recovery than I am in windows. I have cleared cache and everything I can think of (again I'm a complete amateur). Does anyone have a suggestion of what I am doing wrong or how to resolve? Thanks in advance.
Cranky
The issue with your first problem was that it could have been a bad gapps, in the future try different gapps if you see weird problems like that, to your second problem, when flashing lollipop on a device that had ICS it'll change the directory of the SDcard, no biggie though, just search in recovery data/media/legacy or data/media/0 it should be in one of those that your files are in.
Sent from my Nexus 9 using Tapatalk
Try this.
Try to send files over using adb whilst in recovery. If you do not know how then watch this youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
I have managed to screw myself by wiping the OS without a backup when I got TWRP up and running and ended up with what essentially is a bricked MemoPad. It said in droidboot mode the version is WW_K013 and the Android it ran before I wiped it was 4.4.2.
I was hoping to install this: https://forum.xda-developers.com/me...-unofficial-lineageos-16-0-asus-memo-t3929600 to get it up to Android 7 but every attempt at installing one of the mentioned archives always ends in failure.
All I have managed to get up and running was TWRP. I did not use an SD card (only one I have keeps saying write protected, and even using diskpart clear readonly attributes doesn't seem to work) so I just dragged the archives into the tablet itself on its internal storage and attempted to install them via TWRP from there. I don't know if this is even possible to do.
Attempting to install the Lineage OS package as is gave me:
E: unkown command [log]
Attempting to Install the ESP 0.3.0.zip simply says
"Error flashing zip '/sdcard/esp-0.3.0.zip' (dunno why it says it's in sdcard when I clearly ain't using one)
And attempting to do a fastboot devices on cmd gives me an empty list even when the tablet is plugged in on my pc (the list was showing up on work laptop earlier, but doesn't show up on pc, so something is missing in this case). I used the Windows Zip for platform tools from here:
https://wiki.lineageos.org/adb_fastboot_guide.html
and added its path to environment variables to recognize fastboot command
What would the next logical step be for me? Every option I've tried has failed thus far. I'm trying to install Android Studio maybe fastboot recognizes the device when the Studio is installed and is up and running, since my work laptop had the full Android studio in place.
UPDATE: Kept messing about, when I exited TWRP and reloaded in fastboot the devices was indeed listed under fastboot when I ran the command (duh). Attempted to run the fastboot flash ESP esp.img but I got a "Can't find OSII index!!" error instead.
Still not sure what to do with that. The tablet itself says FAIL(flash_cmds error!)
Solution to this problem that I just finally did:
I acquired the basic ROM from this resource, quoted below: https://forum.xda-developers.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965
WW .182 ROM
http://dlcdnet.asus.com/pub/ASUS/Eee...3_2_23_182.zip
Click to expand...
Click to collapse
It's important to extract this zip file to get another zip file, and then use that zip file to install using TWRP.
To install TWRP (temporarily, have to redo each time you exit recovery) I used the following resource:
https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
And once TWRP launched, I dragged the file using my Windows pc to the internal storage of my K013 (When TWRP is launched it makes the device accessible on PC)
I chose Install and selected the zip file mentioned above to install. Took a short while but executed successfully. I could once again use my Tablet.
Next up I'll need to figure out how to get it to Lollipop from 4.4.2 and possibly move on to install Lineage OS and get it up to Android 7+ But that's for later. :silly:
i need help
hello i have a asus memo pad 7 k013 which come whit kikat 4.4 i decided to install lineage os 14 but searching in xda get that i have to upgrade to android 5 lollipop well first i installed this TWRP from here
https://www.htcmania.com/showpost.ph...69&postcount=7
after that any zip i downloaded failed whit error 7 lineage os 14 an 16 unnoficial also a update.zip whit signal 11 error
ANY IDEA GUYS