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.
Related
This may void your warranty, cost you your soul, and cause your spouse to leave you - ALL OF WHICH I AM NOT RESPONSIBLE FOR!
So, if it's because you screwed up flashing something, bricked your tablet with an OTA update after you installed CWM, or whatever, this is how you get it back to its outta-da-box shape!
(Please note, this assumes you have both installed CWM on your DS7 AND have installed the latest SDK on your computer).
1. Download the three attached .img files
2. Boot into CWM (since there really isn't anything else you can do)
3. In CWM, mount your SD card (so that you can view files via USB)
4. Plug in your DS7 to your computer, and copy the three .img files to the root of your SD card
5. Unmount your SD card, but leave the USB cable plugged into computer
6. Mount as many things as you can (ie system, boot, etc)
7. Open up command prompt, and navigate to your Android/tools folder, and type "adb devices"
8. There should be a number that shows up, or a "?" - either at this point is fine
9. Type the following command:
Code:
adb shell
a hash tag should show up that looks like this:
Code:
#~
10. Now, type the follow two commands one at a time:
Code:
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
11. now, select "reboot" from DWM to reboot your device. It should boot and say something like "Formating Misc", and then it will reboot repeatedly
12. Use something small to push the RESET button on the DS7 (it's next to the SD card slot)
Your screen should go blank
13. Now, press and hold both the POWER button and the VOLUME - button until the screen comes on saying that the "fastboot downloader" is booted
14. Copy the three .img files into the your Android/tools folder
15. Now type the following code:
Code:
fastboot devices
16. There should be a number that shows up, or a "?" - either at this point is fine once again
17. Now type the following commands one at a time. The first will take a while to complete - this is okay:
Code:
fastboot flash system system_orig.img
fastboot flash recovery recovery_orig.img
fastboot flash boot boot_orig.img
Now, if after every command a "finished." is given, along with the total time each command took, you may continue.
18. You may now type the triumphant command:
Code:
fastboot reboot
Which will reboot your device.
Give it a little bit to boot, but when all is done you should see the original T-Mobile boot animation and everything.
Special thanks to DJ_Steve, bogdi1988, and [email protected] for all your help!
Needed files:
system_orig.img
recovery_orig.img
boot_orig.img
[Edit]
For those users who need the original "flash_image.zip" file, I have uploaded it and it is available here.
PS: As an added note: **** you Koush! From all of the DS7 community!
Just what was needed
sent from somewhere
thanks but if you would of search there was a thread made already but i am sure the more the marrier
mooch777 said:
This may void your warranty, cost you your soul, and cause your spouse to leave you - ALL OF WHICH I AM NOT RESPONSIBLE FOR!
So, if it's because you screwed up flashing something, bricked your tablet with an OTA update after you installed CWM, or whatever, this is how you get it back to its outta-da-box shape!
(Please note, this assumes you have both installed CWM on your DS7 AND have installed the latest SDK on your computer).
1. Download the three attached .img files
2. Boot into CWM (since there really isn't anything else you can do)
3. In CWM, mount your SD card (so that you can view files via USB)
4. Plug in your DS7 to your computer, and copy the three .img files to the root of your SD card
5. Unmount your SD card, but leave the USB cable plugged into computer
6. Mount as many things as you can (ie system, boot, etc)
7. Open up command prompt, and navigate to your Android/tools folder, and type "adb devices"
8. There should be a number that shows up, or a "?" - either at this point is fine
9. Type the following command:
Code:
adb shell
a hash tag should show up that looks like this:
Code:
#~
10. Now, type the follow two commands one at a time:
Code:
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
11. now, select "reboot" from DWM to reboot your device. It should boot and say something like "Formating Misc", and then it will reboot repeatedly
12. Use something small to push the RESET button on the DS7 (it's next to the SD card slot)
Your screen should go blank
13. Now, press and hold both the POWER button and the VOLUME - button until the screen comes on saying that the "fastboot downloader" is booted
14. Copy the three .img files into the your Android/tools folder
15. Now type the following code:
Code:
fastboot devices
16. There should be a number that shows up, or a "?" - either at this point is fine once again
17. Now type the following commands one at a time. The first will take a while to complete - this is okay:
Code:
fastboot flash system system_orig.img
fastboot flash recovery recovery_orig.img
fastboot flash boot boot_orig.img
Now, if after every command a "finished." is given, along with the total time each command took, you may continue.
18. You may now type the triumphant command:
Code:
fastboot reboot
Which will reboot your device.
Give it a little bit to boot, but when all is done you should see the original T-Mobile boot animation and everything.
Special thanks to DJ_Steve, bogdi1988, and [email protected] for all your help!
Needed files:
system_orig.img
recovery_orig.img
boot_orig.img
PS: As an added note: **** you Koush! From all of the DS7 community!
Click to expand...
Click to collapse
Thanked using the Thanks button and Thanks for your post!
Just to remind me a little as I may miss something,
why we **** Koush? It is not his fault that we stuck at CWM, or is it????
jiwengang said:
Thanked using the Thanks button and Thanks for your post!
Just to remind me a little as I may miss something,
why we **** Koush? It is not his fault that we stuck at CWM, or is it????
Click to expand...
Click to collapse
No its not his fault.. people shouldn't have tried to install the ota update while having cwr installed.. instead should have waited for a zip of the update that hell posted on behalf of did steve. As I have said if you have cwr you really can't get ota updates and install them the normal way. If the update was an update.zip you could flash through cwr but dell uses pgk files not zip.. so the only way to update is to wait for a dev to release a flashable cwr zip fike
Sent from my HTC Glacier using XDA App
The reason I made this post was so that we could have one concise, iD10t proof solution for people who were dumb like me. There's other posts, but you have to go back and forth to get the solution.
And the "Koush-****ing" was because of his unannounced abandonment of his projects, and those he was working with.
And thank you for the kind thanks!
Sent from my Dell Streak 7 using XDA App
mooch777 said:
The reason I made this post was so that we could have one concise, iD10t proof solution for people who were dumb like me. There's other posts, but you have to go back and forth to get the solution.
And the "Koush-****ing" was because of his unannounced abandonment of his projects, and those he was working with.
And thank you for the kind thanks!
Sent from my Dell Streak 7 using XDA App
Click to expand...
Click to collapse
Did he retire completely?
graffixnyc said:
Did he retire completely?
Click to expand...
Click to collapse
Think so!
From my CM7 UrBan Glacier
Hi,
I am the situation described above as I tried the OTA and am now stuck in CWR.
I followed the directions putting the 3 files on the root of my DS7 and am stuck at the following:
~ # flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
failed with error: -1
~ #
Any ideas.....?
Thanks
SkI
Error 1
Error 1 means that the file is not where it is supposed to be. In this case on the SD card. Check and make sure that you have the right file, with the right file name on the root of your SD card and try again!
Good Luck
What does
"Error scanning partitions" means?...
jiwengang said:
What does
"Error scanning partitions" means?...
Click to expand...
Click to collapse
nvm, it is solved. don't use your own flash_image. use the stock one.
dj_ski69 said:
Hi,
I am the situation described above as I tried the OTA and am now stuck in CWR.
I followed the directions putting the 3 files on the root of my DS7 and am stuck at the following:
~ # flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
failed with error: -1
~ #
Click to expand...
Click to collapse
+1 same here...
I find that at step 3... I mount sdcard... it shows on PC... I copy the 3 files to drive... unmount sdcard... mount everything else... run the other commands then get error... when I repeat the process I notice the files I copied are not there... ?
so I tried to adb push the files... they say they went thru correctly... but still get the same result as above...
any ideas?
dfspot said:
+1 same here...
I find that at step 3... I mount sdcard... it shows on PC... I copy the 3 files to drive... unmount sdcard... mount everything else... run the other commands then get error... when I repeat the process I notice the files I copied are not there... ?
so I tried to adb push the files... they say they went thru correctly... but still get the same result as above...
any ideas?
Click to expand...
Click to collapse
when you adp push to sdcard, make sure you mounted it already.
after that , it always help to adb shell ls /sdcard to make sure all files are there.
then you go to adb shell,
use the stock flash_image to flash. remember point to the path to flash_image
eg. flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
my understanding, if you don't mount sdcard, you canot see your sdcard FROM the tablet's perspective.
I mean, for table's flash_image to work, it has to be able to access its drive, in this case, is sdcard 's content.
so did you try leave sdcard mount and do the command above?
Hey Team...
can someone help me find the stock flash_image plz.....
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
chris73 said:
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
Click to expand...
Click to collapse
What command did you do.
Sent from my HTC Glacier using XDA App
chris73 said:
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
Click to expand...
Click to collapse
do I need to push flash_image to my tablet?
If I remember correctly it needs to be in the nvflash folder
Sent from my Dell Streak 7 using XDA Premium App
Hello...i've search4ed and searched and no answer pertains to my problem that I can find. I followed this guide to get CM7.2 loaded on my 16gb sandisk sd card: http://forum.xda-developers.com/showthread.php?t=1000957 The gapps I'm using the CM7 download link. The CM7.2 rom is the newest one available on the download link
Everything loaded smooth and works great except when I get to the part of installing gapps, I reboot into recovery mode (blue penguin with scrolling writing) and everytime it cannot find gapps installer so it ignores it!! I don't know what else to do here.. I've verified the hash using md5sum and it matches... I have my gapps.zip file located on the ROOT of my sd card /sdcard/gapps.zip. I've also tried putting gapps in /sdcard/boot. I've also tried changing the name to gapps-update.zip, update-gapps.zip, gapps-gd....etc.zip, etc etc etc. No matter what or where I put the file it isn't found.
When I boot the NC i can get to a boot menu from there, i've tried all combinations of booting (internal, sd, normal, etc etc). I've tried installing through boot manager and that doesnt work. It reboots to recovery mode and still doesn't find the file. I've flashed clockwork in boot manager and that didn't help anything.
I'm not sure what I just did, but i rebooted and now I have a "burrito manager" icon. I tried installing through that and no go. Don't know what else to do.
I DO have wifi setup/connected.
*EDIT... not sure if it matters, but I do seem to have an issue. I'm connected to wifi but NTP isn't updating my clock settings. It is setup in settings to auto update the date/time using network settings and it doesn't update. Could this be an issue with getting market to show up if the time is wrong??
Its most likely you are not placing gapps in the root of the boot partition... try this:
if adb works for you:
adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push ***GAPPS INSTALLER*** /sdcard/boot
then when you reboot to sd recovery mode it will see the gapps installer.
DizzyDen said:
Its most likely you are not placing gapps in the root of the boot partition... try this:
if adb works for you:
adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push ***GAPPS INSTALLER*** /sdcard/boot
then when you reboot to sd recovery mode it will see the gapps installer.
Click to expand...
Click to collapse
Hello...thanks for the reply! But I'm a little confused what you mean? I manually put the gapps.zip file on /sdcard/gapps.zip AND also copied to /sdcard/boot/gapps.zip. The file is there. What is the filename supposed to be??? I've tried gapps-...zip, update-gapps...zip, gapps.zip, etc.
Is there something that adb does that copy on the terminal doesn't do??
See attached screenshot, the file is there. For some reason the installer script in recovery mode isn't finding it. That's why i was asking what filename it's looking for?
ballgum said:
Hello...thanks for the reply! But I'm a little confused what you mean? I manually put the gapps.zip file on /sdcard/gapps.zip AND also copied to /sdcard/boot/gapps.zip. The file is there. What is the filename supposed to be??? I've tried gapps-...zip, update-gapps...zip, gapps.zip, etc.
Is there something that adb does that copy on the terminal doesn't do??
See attached screenshot, the file is there. For some reason the installer script in recovery mode isn't finding it. That's why i was asking what filename it's looking for?
Click to expand...
Click to collapse
Do not put the file in 'sdcard'. It needs to go in the boot partition like dizzy said. Take the card out of the nook and put in your PC. That will show the boot partition. Put the gapp file there. Make sure the name starts with gapps-gb-. Put the card back into the Nook and reboot to recovery like before.
leapinlar said:
Do not put the file in 'sdcard'. It needs to go in the boot partition like dizzy said. Take the card out of the nook and put in your PC. That will show the boot partition. Put the gapp file there. Make sure the name starts with gapps-gb-. Put the card back into the Nook and reboot to recovery like before.
Click to expand...
Click to collapse
That worked! thank you very much...
I had the SD card issue where it wasn't seeing all my files. Recovery mode would see files I could not locate within the os.
What I did:
Backed up my contents. Always have a nandroid backup!
Downloaded and md5sum checked Trickdroid 8.0.0
Booted into recovery, wiped phone. Formatted all partitions.
My next plan of action was to adb push trickdroid. This failed, its not seeing my sdcard partion. I have attempted to format /sdcard. It returns no errors. I got to mount /sdcard, It fails to find the directory.
When I boot into fastboot (Thinking at the very worst I could relock my device nad flash an RUU)
It does not see any devices. I have verified multiple times that I am using the correct driver. I have removed all drivers from the system, attempted to use htc sync, uninstalled that, used the Naked Drivers, uninstalled those (still no device in fastboot), installed the ADB Driver installer (found using the search button). Still, no devices in fastboot.
If someone could point me in the right direction I would greatly appreciate it. I have been using adb and flashing devices for a number of years and have not yet encountered a problem like this.
-Erik
voltage88 said:
I had the SD card issue where it wasn't seeing all my files. Recovery mode would see files I could not locate within the os.
What I did:
Backed up my contents. Always have a nandroid backup!
Downloaded and md5sum checked Trickdroid 8.0.0
Booted into recovery, wiped phone. Formatted all partitions.
My next plan of action was to adb push trickdroid. This failed, its not seeing my sdcard partion. I have attempted to format /sdcard. It returns no errors. I got to mount /sdcard, It fails to find the directory.
When I boot into fastboot (Thinking at the very worst I could relock my device nad flash an RUU)
It does not see any devices. I have verified multiple times that I am using the correct driver. I have removed all drivers from the system, attempted to use htc sync, uninstalled that, used the Naked Drivers, uninstalled those (still no device in fastboot), installed the ADB Driver installer (found using the search button). Still, no devices in fastboot.
If someone could point me in the right direction I would greatly appreciate it. I have been using adb and flashing devices for a number of years and have not yet encountered a problem like this.
-Erik
Click to expand...
Click to collapse
I fixed it!!! Anyone that has a similiar issue. This is what I did.
In a previous thread, I saw that 4.2 will redo the sd card structure. After some research, it was recommended to change the path to /data/media/0. I was then attempting to do the command as follows 'adb push Trickdroid_8.0.0.zip /data/media/0' (without tick marks)
The file was pushing as it should (no progress bar) however, it would fail at the very end saying it was unable to locate the directory.
After seeing adb fail in that manner, I knew my sdcard was not mapped to the above path. What I did was boot into recovery, go to mounts and storage, mount my sdcard. Go back to the first menu now.....From here, select advance, and view log. It will tell you where your sdcard is being mapped to. Simply push your zip file to this directory and success! I have a working phone again.
Fastboot still doesn't recognize my device however. I'd be more then happy to be educated as to what I may have done wrong.
Recently i wanted to a full wipe including internal storage on my nexus 5 and since nexus 5 does not have external storage i found it a bit tricky to flash a rom again...
so,here im going to explain the easiest and simplest way to install a rom via adb sideload on nexus 5 using TWRP after a complete wipe
I am not responsible for bricked devices.
Please do some research if you have any concerns about adb sideload
BACKUP YOUR DATA FIRST
1.Download the file and place it on desktop View attachment Nexus5.zip
2.boot your device into recovery, wipe everything and connect it to pc and make sure drivers are installed. if not do as follows:
open device manager in control panel and if drivers are already installed, it shows something like ANDROID ADB INTERFACE,
if not,it shows some name with yellow symbol..
right click on it and select update drivers and select browse my computer and select let me pick..
click next > have disk>browse> and select the usb_drivers in downloaded file> open > open > ok
now it shows as ANDROID ADB INTERFACE..
3.In TWRP, select advanced and choose sideload option.
4.open command prompt and change the directory to where you downloaded the file ( easy if on desktop )
to open command prompt: win+r>cmd
for changing directory: cd desktop > cd nexus5
5.Now type adb devices in command prompt and it should show list of devices with your device code name and mode as sideload mode.
if not install drivers again.
6.copy your ROM zip file to the folder 'Nexus5' which you downloaded.
7.type adb sideload romzipname
8.now it starts copying and wait till it shows 100%. after copying it automatically starts installing.
when the installing is finished,it shows reboot system. reboot and njoy :highfive:
Note: If stuck while flashing rom, hold power and volume down until it reboots to fastboot then go to recovery and repeat the same procedure.
Please hit the 'thanks' if this helped you.
jaj473 said:
Recently i wanted to a full wipe including internal storage on my nexus 5 and since nexus 5 does not have external storage i found it a bit tricky to flash a rom again...
so,here im going to explain the easiest and simplest way to install a rom via adb sideload on nexus 5 using TWRP after a complete wipe
I am not responsible for bricked devices.
Please do some research if you have any concerns about adb sideload
BACKUP YOUR DATA FIRST
1.Download the file and place it on desktop View attachment 2461684
2.boot your device into recovery, wipe everything and connect it to pc and make sure drivers are installed. if not do as follows:
open device manager in control panel and if drivers are already installed, it shows something like ANDROID ADB INTERFACE,
if not,it shows some name with yellow symbol..
right click on it and select update drivers and select browse my computer and select let me pick..
click next > have disk>browse> and select the usb_drivers in downloaded file> open > open > ok
now it shows as ANDROID ADB INTERFACE..
3.In TWRP, select advanced and choose sideload option.
4.open command prompt and change the directory to where you downloaded the file ( easy if on desktop )
to open command prompt: win+r>cmd
for changing directory: cd desktop > cd nexus5
5.Now type adb devices in command prompt and it should show list of devices with your device code name and mode as sideload mode.
if not install drivers again.
6.copy your ROM zip file to the folder 'Nexus5' which you downloaded.
7.type adb sideload romzipname
8.now it starts copying and wait till it shows 100%. after copying it automatically starts installing.
when the installing is finished,it shows reboot system. reboot and njoy :highfive:
Note: If stuck while flashing rom, hold power and volume down until it reboots to fastboot then go to recovery and repeat the same procedure.
Please hit the 'thanks' if this helped you.
Click to expand...
Click to collapse
in the cmd prompt it keeps telling me it cannot read my rom file. any helpm please?
b_rangel29 said:
in the cmd prompt it keeps telling me it cannot read my rom file. any helpm please?
Click to expand...
Click to collapse
Did you copy the rom file to Nexus5 folder?
Why not use WugFresh's tool.... that thing does everything.
Sent from my Nexus 5 using Tapatalk
We try to discourage the use of toolkits as they remove the "ability" element or the "learning" aspect.
Doing things manually teaches the skills to get out of trouble later on.
Sent from my Nexus 5 using Tapatalk
try to update usb driver. browse the file inside dowloaded file but it came result windows was unable to instal your nexus 5
i'm using windows 7
any sugestions?
Help
So, I have/had a N5 on stock 4.4.4 rom, rooted & Xposed installed with TWRP & a lollipop preview on MultiRom.
Was installing the new Lollipop .zip. In an act of hurried stupidity, I wiped my phone, including the internal storage.
Which for some reason also wiped my NANDROID backup. I thought that is not supposed to be wiped even when doing an internal storage wipe, BUT it did.
Now, all i have is TWRP on my phone with no rom installed.
I tried connecting my phone to the pc to see if i can just transfer the rom file onto the internal memory, but nothing shows up when i connect my phone to PC.
after some searching, I ended up in this thread.
The problem is, when i connect my phone to the PC, the phone doesn't show up in the device manager.
So i cannot install the drivers & android SDK itself.
So, How do i Install a rom onto it?
I have a PC & a MAC, so i can use either of the machines. But i don't have much technical knowledge about stuff, I did all the above modifications with the help of tutorials & guids. so ELI5 please.
Please help!
Thank you.
Jugal.PM said:
So, I have/had a N5 on stock 4.4.4 rom, rooted & Xposed installed with TWRP & a lollipop preview on MultiRom.
Was installing the new Lollipop .zip. In an act of hurried stupidity, I wiped my phone, including the internal storage.
Which for some reason also wiped my NANDROID backup. I thought that is not supposed to be wiped even when doing an internal storage wipe, BUT it did.
Now, all i have is TWRP on my phone with no rom installed.
I tried connecting my phone to the pc to see if i can just transfer the rom file onto the internal memory, but nothing shows up when i connect my phone to PC.
after some searching, I ended up in this thread.
The problem is, when i connect my phone to the PC, the phone doesn't show up in the device manager.
So i cannot install the drivers & android SDK itself.
So, How do i Install a rom onto it?
I have a PC & a MAC, so i can use either of the machines. But i don't have much technical knowledge about stuff, I did all the above modifications with the help of tutorials & guids. so ELI5 please.
Please help!
Thank you.
Click to expand...
Click to collapse
Read here - http://forum.xda-developers.com/showthread.php?p=48915118
Sent from my Android 5.0 Nexus 5
accidently wiped internal memory in lenovo p1m
i accidently wiped internal memory using twrp. so now can i flash a custom rom for my lenovo p1m
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.