Database Info

Can't get to ClockworkMod

I installed Flashback 10.1 a while back. Today I wanted to install 10.3 and found out that I couldn't get into ClockworkMod at all. It would do a normal reboot instead of going to the recovery mode.
Any help is appreciated.

Just to be sure, you *are* holding the volume + button when you press the power button and keeping it held down until you see "recovery key detected" in the upper left corner?

Yes, I see
recovery key detected
Booting recovery kernel image
But it would stay there with the birds and "View Sonic - See the difference" forever, never go further than that.

Use nvflash and reload only ClockworkMod. Use the commands in this thread.

rajeevvp said:
Use nvflash and reload only ClockworkMod. Use the commands in this thread.
Click to expand...
Click to collapse
Hello rajeevvp,
I tried this method but I get the following error message...
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
When I run download.bat by itself, I get a message, "USB device not found".
Can you offer any suggestions?
Thanks,
ssummerlin

ssummerlin said:
I tried this method but I get the following error message...
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
When I run download.bat by itself, I get a message, "USB device not found".
Can you offer any suggestions?
Click to expand...
Click to collapse
That's a very strange error. What led to it?
Try these suggestions one by one.
1. Use a different USB cable and port on the PC. Bad cables and USB ports have been known to cause problems.
2. Open the gTab up and use the reset button, then disconnect and reconnect the battery.
3. Do the nvflash on Linux.

Did you ever find a fix for this, cub2000?
I ran into the same thing, when I attempted to update to CWM 5.5.04 (via flashable zip) using the procedures outlined in the [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery - TEAM DRH thread.
After doing so, I figured my best bet was to roll back to bekit's original image, so I followed the procedures outlined in the [STICKY][ROM] nvflash FULL restore, using bekit's original image (Instructions) thread to roll back to TnT 1.0-2638.
I can't remember the specific ROM I was on before -- it's been ages since I last powered up my gTab. It may have been TnT Lite. Whatever it was, I'm fairly certain I was running Bootloader v1.1.
After nvflashing back to 1.0-2638, TnT offers an update as soon as I connect to wifi, but the update fails in the same way that CWM fails. It hangs here:
recovery key detected
Booting recovery kernel image​
The awful, original TnT still runs on my tab, so it's not a true bricking (or even a soft-brick), but now I'm stuck with... well, I'm stuck with the awful, original TnT.
If I find a way around this, I'll let you know. If you've already found one, please let me know!
Thanks.

See this thread.

Thanks, rajeevvp. I actually found a different solution before I got your recommendation; just hadn't had a chance to update this thread yet.
Solution: I didn't have any important data on my device, so I did a Full Stock NVFlash with CWM v5.5.0.4 (Touch), then flashed AOKP (and cleared my cache) from CWM before I ever booted into the stock ROM.
I'm up and running now! I may have chosen a different path, but I appreciate the help.

colbymulkey said:
Solution: I didn't have any important data on my device, so I did a Full Stock NVFlash with CWM v5.5.0.4 (Touch), then flashed AOKP (and cleared my cache) from CWM before I ever booted into the stock ROM.
Click to expand...
Click to collapse
You mean you flashed AOKP and then booted into AOKP?
BTW, did you expand "system" to more that 250MB for AOKP?

rajeevvp said:
You mean you flashed AOKP and then booted into AOKP?
Click to expand...
Click to collapse
No. I couldn't get into CWM to flash AOKP directly. Instead, I used NVFlash to flash a package that was titled Full Stock NVFlash with CWM v5.5.0.4 (Touch). (I found it in a thread on these forums, but I can't seem to find that thread now.) I'm pretty sure this is what got my bootloader and CWM back in sync...
I never actually booted into the stock ROM that I NVFlashed though. Instead, I immediately:
went into recovery mode
USB-mounted the gTablet's internal SD card
dropped the AOKP ZIP onto my device's filesystem
flashed AOKP
cleared the devices cache using CMW
booted into AOKP
rajeevvp said:
BTW, did you expand "system" to more that 250MB for AOKP?
Click to expand...
Click to collapse
I did not expand my system partition, and I may be paying the price now. I've reflashed the gapps, and I can install APK's directly, but the Play Store won't update apps. I can browse the store; just can't update anything. (The app updates never time out or give me any errors, they just perpetually show as Update Available and/or Update in Progress.

colbymulkey said:
No. I couldn't get into CWM to flash AOKP directly. Instead, I used NVFlash to flash a package that was titled Full Stock NVFlash with CWM v5.5.0.4 (Touch).
Click to expand...
Click to collapse
That package would've made your system partition 256 MB in size.
I never actually booted into the stock ROM that I NVFlashed though. Instead, I immediately:
went into recovery mode
USB-mounted the gTablet's internal SD card
dropped the AOKP ZIP onto my device's filesystem
flashed AOKP
cleared the devices cache using CMW
booted into AOKP
Click to expand...
Click to collapse
That's what I thought: You booted directly into AOKP after flashing it.
I did not expand my system partition, and I may be paying the price now. I've reflashed the gapps, and I can install APK's directly, but the Play Store won't update apps. I can browse the store; just can't update anything. (The app updates never time out or give me any errors, they just perpetually show as Update Available and/or Update in Progress.
Click to expand...
Click to collapse
Since you've used the TeamDRH nvflash package, you should have a 256 MB system partition now, but, that will not be enough for AOKP which needs ~262 MB for everything. Most likely the Gapps would've all been copied, but, the face-detection bits would not all be there. This isn't an issue now because the camera isn't working.
Go back into CWM and do a "wipe data/factory reset". See if that clears your market problems.

rajeevvp said:
That package would've made your system partition 256 MB in size.
That's what I thought: You booted directly into AOKP after flashing it.Since you've used the TeamDRH nvflash package, you should have a 256 MB system partition now
Click to expand...
Click to collapse
There's probably a way to confirm this within CMW (or by utilizing APX+NVFlash), but I haven't verified it yet. Still, I suspect there would be major stability issues if my system partition were too undersized -- and while there's lag at times, I haven't experienced many system app crashes.
rajeevvp said:
That will not be enough for AOKP which needs ~262 MB for everything. Most likely the Gapps would've all been copied, but, the face-detection bits would not all be there. This isn't an issue now because the camera isn't working.
Click to expand...
Click to collapse
Face detection is of little interest to me on this device; not too worried about that. Still, I don't really see a problem with upping my system partition a few MB -- especially if it'll help future-proof the system. I'll check the other threads to see if there's a recommended size; not sure if I should set it at 262MB, or err on the side of caution and aim a little higher.
rajeevvp said:
Go back into CWM and do a "wipe data/factory reset". See if that clears your market problems.
Click to expand...
Click to collapse
I'll give the factory reset a shot and let you know if it works; may even attempt to repartition the system partition, just to make sure everything's kosher.
Thanks for recommendations!

colbymulkey said:
I'll give the factory reset a shot and let you know if it works...
Click to expand...
Click to collapse
The factory reset didn't fix my Play Store issues. I was going to settle on the Amazon AppStore as a work around, except I can't even seem to install the APK for the Amazon AppStore. It downloads, but I can't launch it directly from my notification tray, and it's not listed in the "Downloads" app.
I love AOKP on my SII, but I may flash another ROM to see if I find something that works a little better (for me) on my gTablet.
Thanks, again, for your help rajeevvp!

colbymulkey said:
There's probably a way to confirm this within CMW (or by utilizing APX+NVFlash), but I haven't verified it yet.
Click to expand...
Click to collapse
In CWM or in the ROM, run this dmesg command right after the system boots:
Code:
$ [B]dmesg | fgrep -i 'Kernel command line'[/B]
<5>[ 0.000000] Kernel command line: [email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 cpuid=200102 devicetype=1002 bspversion=0202100908 btmac=6037cf131a00 tegraboot=nand mtdparts=tegra_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[B][email protected](system)[/B],[email protected](cache),[email protected](bootbmp),[email protected](logodata)
In APX mode, use the ``--getpartitiontable'' flag and look through it for the APP partition:
Code:
C:\> .[B]\nvflash --bl bootloader.bin --getpartitiontable p.txt[/B]
Multiply the NumSectors and BytesPerSector parameters.
Still, I suspect there would be major stability issues if my system partition were too undersized -- and while there's lag at times, I haven't experienced many system app crashes.
Click to expand...
Click to collapse
Well, that depends. If critical bits have not been written then you will have immediate crashes or bootloops. OTOH, if unused files have not been written then you won't notice any problems until something attempts to use them. Going by what the AOKP ROM installation script does, the last thing to be written is the face-detection stuff as I said. This would account for your not noticing any major problems.
If you look at the /tmp/recovery.log file right after you install AOKP you'll be able to see precisely which files have not been copied owing to lack of space.
I'll check the other threads to see if there's a recommended size; not sure if I should set it at 262MB, or err on the side of caution and aim a little higher.
Click to expand...
Click to collapse
Go for 270 MB.

[Q] CWM won't install Cyanogenmod 10 - HELP!!

I rooted my phone, installed CWM and all that stuff. I downloaded cm-10.0.0-crespo.zip and mounted my usb storage, put it in the root folder, then rebooted into CWM. I formatted system, and went to install it from zip. I choose it, and it acts like it's gonna install it, but then I get an error at Opening update package:
E:Can't open /sdcard/cm-10.0.0-crespo.zip
(bad)
I tried rebooting, but it gets stuck at the Google screen. I can't mount USB storage in CWM for some reason, so I can't fix/replace the zip. I think I'm screwed. Is there a way to fix this??
Help is greatly appreciated!

OrbitGum22 said:
I rooted my phone, installed CWM and all that stuff. I downloaded cm-10.0.0-crespo.zip and mounted my usb storage, put it in the root folder, then rebooted into CWM. I formatted system, and went to install it from zip. I choose it, and it acts like it's gonna install it, but then I get an error at Opening update package:
E:Can't open /sdcard/cm-10.0.0-crespo.zip
(bad)
I tried rebooting, but it gets stuck at the Google screen. I can't mount USB storage in CWM for some reason, so I can't fix/replace the zip. I think I'm screwed. Is there a way to fix this??
Help is greatly appreciated!
Click to expand...
Click to collapse
Follow the directions for unbricking using nexus root tool kit... And then on how to flash a ROM...
Sent from my Nexus S using xda premium

Also could be a bad download, try re-downloading. Could also try to sideload from CWM. Also would recommend CM10.1 RC5 much better then 10.0 and faster too.

philosopherssage said:
Also could be a bad download, try re-downloading. Could also try to sideload from CWM. Also would recommend CM10.1 RC5 much better then 10.0 and faster too.
Click to expand...
Click to collapse
How do you side load? Whenever I try it gives me this list of commands.

OrbitGum22 said:
How do you side load? Whenever I try it gives me this list of commands.
Click to expand...
Click to collapse
Reboot to bootloader,
Select recovery to start CWM
Select -install zip from sideload
ON Computer open command window
IN Command window: ADB sideload cm-10.1.0-RC5-crespo.zip
this is assuming that cm-10.1.0-RC5-crespo.zip is in the same directory as ADB

I had the same problem.. I downloaded Cyanogenmod from it's original site 3 times.. and every time I got the (bad) error and it wouldn't install...
I was downloading it with IDM and every one of those files failed to install..
Then I downloaded via the browser bypassing my download accelerator.. and bamm! it works...
So sometimes the answer is so simple and so stupid.. it leaves you stupified!

[Q] Installation failed CM 10.2 on HTC Google Nexus One

My first post Hurray!
Hi guys.
I want to install Android 4.3 to my HTC Google Nexus One. I followed this post.
I installed everything needed and when I try to install the update I get the following results:
Formatting System
Installing CM 10.2
Setting symlinks and premissions...
Setting symlinks...
Setting permissions..
set_perm: some changed failed
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I have Fastboot access to the phone when connected via USB to my Windows 7 laptop.
I am using recovery versions 5.0.2.0 for my Google Nexus One phone.
Flashing ROM: CM 10.2 Rom for the N1
How can I solve this issue, need your help. Thanks in advance. :cyclops:
Other things I've tried: Flashing the rom from boot.img from the zipped file via fastload
I also checked for assert command in the script file but there aren't any.

IdanShechter said:
My first post Hurray!
Hi guys.
I want to install Android 4.3 to my HTC Google Nexus One. I followed this post.
I installed everything needed and when I try to install the update I get the following results:
I have Fastboot access to the phone when connected via USB to my Windows 7 laptop.
I am using recovery versions 5.0.2.0 for my Google Nexus One phone.
Flashing ROM: CM 10.2 Rom for the N1
How can I solve this issue, need your help. Thanks in advance. :cyclops:
Other things I've tried: Flashing the rom from boot.img from the zipped file via fastload
I also checked for assert command in the script file but there aren't any.
Click to expand...
Click to collapse
might need to get a higher vesion of CWM. otherwise google Status 7 error

Hi,
Which version is recommended, the highest that is compatible. According to the ROM manager page of clockworkmod, this is the only one available for the nexus one.

IdanShechter said:
Hi,
Which version is recommended, the highest that is compatible. According to the ROM manager page of clockworkmod, this is the only one available for the nexus one.
Click to expand...
Click to collapse
you would have to get a ported (non offical: should work just as fine as offical but there could be some other added stuff.) version since you want Cm 10.2 5.x.x.x should work but just to be on the safe side you should try getting 6.0.4.5. should only have to download a zip of whatever you find and flash it in your current recovery.

Trozzul said:
you would have to get a ported (non offical: should work just as fine as offical but there could be some other added stuff.) version since you want Cm 10.2 5.x.x.x should work but just to be on the safe side you should try getting 6.0.4.5. should only have to download a zip of whatever you find and flash it in your current recovery.
Click to expand...
Click to collapse
I get Image Update Error when updating the 6.0.4.5 version. I've chosen on for another device because there isn't any 6.0.4.5 version for Nexus One.

I checked the free available space. In the SD Card I've have plenty (more than 2GB), but /system has 0% available. This might cause the flash to fail. Is there any option to free up space before I flash the ROM?
Update: even after formatting the system directory I still get the same error, this it not the problem so it seems.

IdanShechter said:
I checked the free available space. In the SD Card I've have plenty (more than 2GB), but /system has 0% available. This might cause the flash to fail. Is there any option to free up space before I flash the ROM?
Update: even after formatting the system directory I still get the same error, this it not the problem so it seems.
Click to expand...
Click to collapse
your gonna have to ask the nexus ones offical Q&A then http://forum.xda-developers.com/nexus-one/help if i right with this problem you have to do something specifically and differently for every device so just ask the pros on your device first.

IdanShechter said:
My first post Hurray!
Hi guys.
I want to install Android 4.3 to my HTC Google Nexus One. I followed this post.
I installed everything needed and when I try to install the update I get the following results:
I have Fastboot access to the phone when connected via USB to my Windows 7 laptop.
I am using recovery versions 5.0.2.0 for my Google Nexus One phone.
Flashing ROM: CM 10.2 Rom for the N1
How can I solve this issue, need your help. Thanks in advance. :cyclops:
Other things I've tried: Flashing the rom from boot.img from the zipped file via fastload
I also checked for assert command in the script file but there aren't any.
Click to expand...
Click to collapse
Status 7 error comes due to system folder being full.. I m not a nexus one user and its a common problem..
Open the rom zip of your file delete some apps from system/app then flash the rom..
This will solve your status 7 error..

[Q] Help! Can't flash anything

I did not make a back up (lesson learned...) and erased everything.. There is no OS loaded on it and the only thing I can get into is TWRP and Fastboot Mode (Just shows logo).
Strange thing is, I used the Mac Toolkit to root and unlock boot loader but as far as I know, not it's saying that it is not rooted (When it indicates "Not rooted; install SuperSU to do so?") and also in some cases, it displays that the boot loader is locked as well. I do have a PC to work with (which is super slow but it works..) but OSX workaround would be ideal.
Please help as I hope the phone is not bricked. I've looked around the forums for about a week and can't seem to find a thread where there is a similar situation.
Dummy-101 instructions would be very much appreciated!

While you have the device booted into TWRP you should be able to copy a ROM from your PC to the phone using the MTP connection. So just download a ROM + gapps to your PC, copy them across, and flash.
Transmitted via Bacon

timmaaa said:
While you have the device booted into TWRP you should be able to copy a ROM from your PC to the phone using the MTP connection. So just download a ROM + gapps to your PC, copy them across, and flash.
Transmitted via Bacon
Click to expand...
Click to collapse
That's what my initial tries were; but there comes an error when trying to flash a ROM.
E: Error executing updater binary in zip '/sdcard/Download/[ROMName]' (Trying to install BlissPop)
From there I shut things off until I can figure this out.. that's where I encounter
"Install SuperSU? Your device does not appear to be rooted. Install SuperSU now? This will root your device. '
I swipe to install but does nothing and shuts down in a millisecond.

Is that the only error you get? What's the full filename of the ROM file that you're trying to flash? Are you checking the md5 after downloading the file?

timmaaa said:
Is that the only error you get? What's the full filename of the ROM file that you're trying to flash? Are you checking the md5 after downloading the file?
Click to expand...
Click to collapse
Trying to installl BlissPop-v1.8-bacon-OFFICIAL-20150124.1647
Not sure how to check md5 sum - is it to verify the file before installing?

sdkim89 said:
Trying to installl BlissPop-v1.8-bacon-OFFICIAL-20150124.1647
Not sure how to check md5 sum - is it to verify the file before installing?
Click to expand...
Click to collapse
It is indeed to verify the integrity of the file. At the download page you can see the ROM zips and directly below each ROM zip is the md5sum file too. Looking at the md5sum for the file you're trying to flash I can see that the md5 should be 85bdc2efffa404bf5864555984628665. So you need to use an md5 checking app to ensure that the md5 of the actual file you've downloaded matches that.

I'm having the same issue. tried wiping, md5 checked, it matches, this problem still persists. any ideas?
EDIT: doh, flashing firmware update fixed it

[Completed] (Nexus 5) Error 7, made multiple mistakes, "assert" fix isn't working

As I understand, my situation is fairly specific, and so I need to address a few points:
This is my first time rooting a phone- I've made several mistakes but managed, at this point, to avoid bricking my phone
I'm using a Nexus 5, and flashing the pwnphone system (Android Open Pwn Project)
I've followed all the standard steps (except one... see below) for unlocking, rooting, and using TWRP as my recovery
I've also successfully flashed AOPP once, although I made an error I couldn't fix during setup and needed to reinstall
To my stupidity, I forgot to make a Nandroid backup on both attempts
I've just used TWRP to wipe my phone's Dalvik/ART Cache, system, data, and cache, assuming I could reflash the same zip I used before
MD5 check is disabled
Zip validation is disabled
Okay, so let's get down to the heart of the issue now. My phone is sitting here, plugged into my computer, I have a command prompt running, and adb is working properly. I try to flash THE SAME ZIP file I used, just before, to start from a clean slate AOPP install, and now I'm recieving an Error: 7.
I looked up the fixes for this, and ran into a problem: I'm already using the most recent version of TWRP- and I just made an alternate AOPP.zip where I removed the asserts from /META-INF/com/google/android/update-script. I was hoping this would solve my problem, but it didn't.
Now, instead of getting an Error: 7, I'm getting an "invalid zip format" notice with very little other information.
Installing zip file '/sdcard/aoppfix.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Invalid zip file format!
Error installing zip file '/sdcard/aoppfix.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
I have no idea what to do at this point. In my earlier error, I failed to make a Nandroid backup file- and much to my dismay- I can't even find one someone has uploaded elsewhere which I could use to at least have a functioning phone to to boot into.
Can someone please help figure out what my next course of action is?

Hi and welcome to XDA Assist !
I`ve searching and I couldn`t find that rom on the Nexus 5 development forums so it`s hard to figure out what`s the problem
Your attempts to modify that script are courageous but I`m afraid that is more than a script issue
Try to flash a different rom with xda support and you`ll get more info and help , good luck !