Develop Bugs

[Q] CM 6.1 Nightly Boot Loop

Hello everyone-
This is my first time modding the G2, and I've run into a problem at the last stage of the project. Let me go through what I have done so far to help clarify:
1. Rooted through "rage"
2. gfree -f to full unlock
3. hboot install (confirmed s-off)
4. Factory reset to clear data and settings
5. Clockworkmod Recovery install
6. adb pushed cm_vision_full-85.zip + gapps-hdp-201011 to sdcard
7. Recovery boot > install zip from sdcard > selected cm_vision_full-85.zip > apply > reboot (rinse and repeat for gapps)
*used the "wipe data" setting for the clockworkmod
On reboot, I'm getting a Cyanogenmod boot animation stuck in a loop. Am I missing a step?

Aha! After wiping data and cache in Clockworkmod Recovery, the phone booted after a minute of the logo. PLEASE DISREGARD! Thanks-

Wow need help from the experts

Im flashing my GF defy green lense. I myself have a htc hd2 and im no novice when it comes to flashing and modding but the defy really makes my head hurt. its out of warranty and its been running really crapp. I want to flash the: [ROM][05.02.2012]MS2Ginger - Android 2.3.6
Ive managed to root the device but i cant seem to get Clockwork mod on it to flash. Maybe because its late but ive been following the beginners guide but im stumped what to do next.
Any help from the experts would be superb
Thanks Baker0

Ive managed to root the device but i cant seem to get Clockwork mod on it to flash.
Click to expand...
Click to collapse
Do you mean you can't install clockworkmod, or that you're having trouble using it to flash the rom? To install Clockworkmod, just use this app: http://forum.xda-developers.com/showthread.php?t=1032212
Run the app and install custom recovery, then reboot the phone. The first time you reboot, the custom BootMenu will display. Use the volume buttons to navigate the menu and the power button to select an option. Select Boot > Set Default > Normal > Go Back > Reboot System. After the phone has fully booted up, power it off and reboot again. If the custom recovery installed properly, a blue LED on the phone should briefly light up each time the phone reboots (while the Motorola logo is being displayed).
To use the recovery, turn off USB debugging on the phone (Settings > Applications > Development > USB Debugging), then power off the phone. Press the power button to turn the phone on again, and as soon as the blue LED lights up, press the volume down button. The custom BootMenu will display. Select Recovery > Custom Recovery.

Thanks it makes more sense now i'll give it ago tonight. Very much appreciated

Glad I could help. Let me know if you need further assistance.

I do ive got further..ive done
Root your DEFY and Install BOOTMENU - CWM (2ndInit-Installer 2.0.apk - install 1.0.7) or use this SndInitDefy_2.0.apk
CM7/9 and MIUI user can start with step 2
2. REBOOT
3. run 2nd-init (voldown on blue LED)
4. Go to "Recovery"
5. Go to "Latest or Stable or Custom Recovery"
6. "wipe data and cache"
7. Go to "Backup and Restore"
8. Go to "Advance Restore"
9. Select "MS2Ginger3.0"
Once i select Ms2Ginger3.0 its coming up with :
Clockworkmod recovery v2.5.1.8
Checking MD5 sums...
MD5 Mismatch!
Then nothing else. Ive had a look on the forums but i cant find a solution. Ive formatted the SD card as fat32. Ive re-downloaded the file. Do I need to do something else before with my factory 2.2 defy?
Any help would be great
Cheers
Baker0

Did you unzip the "MS2Ginger3.0-RTM.zip" file? You have to unzip that file and put the "nandroid.md5" and "system.ext3.tar" files on your SD card in clockworkmod/backup/MS2Ginger. (The "MS2Ginger-Greenbread.zip" file should NOT be unzipped, however, and should be in the root of the SD card.)
If you did that correctly and you're still getting an MD5 mismatch error, try checking the MD5 sum yourself using an app like AFV (Android File Verifier), which is available free on the android market. (Open AFV and browse to the md5sum file, long-press it, and select “md5sum –c Type Check”.) Does AFV show a mismatch too?

ahh i didnt unzip. I dont do that with the hd2
Next step... Sorry I feel like a complete n00bie
All im getting now is system.img not found skipping restore of /system/.
Both files nandroid.md5" and "system.ext3.tar are in the folder....
Thank you

You need newer CWM, backup format changed recently. I'm typing from a phone, can't give you more directions now.

miscz said:
You need newer CWM, backup format changed recently. I'm typing from a phone, can't give you more directions now.
Click to expand...
Click to collapse
Yeah, that might be the problem. Download this: http://forum.xda-developers.com/attachment.php?attachmentid=787176&d=1321653982
Don't unzip it; just put it on the root of your SD card. Then boot into custom recovery, select Install zip from sdcard > choose zip from sdcard, and install it. That will update your recovery to the latest version.

Problem Installing GGL Rom

Hello,Guys im not able to install GGL Roms....im followed exact steps but still not able to install GGL Rom phone is rebooting and it's just booting into stock 2.2.2 any way to fix it im on 2ndinti

Is your defy with green lens? are you trying this with multi boot? do you have the 5+ version bootmenu and recovery.
GGL roms are based on ginger bread kernel, once restoring the system we need to restore boot/devtree for gb kernel installations, it is to be done through customer recovery restore. You should be able to boot into GGL rom once you do this.
If it is still taking you to stock 2.2.2 means, probably you are trying in multi boot and it will not work the ROMs with different kernels. For you to boot into virtual system, you should go to boot menu and select 2ndboot option.

premaca said:
Is your defy with green lens? are you trying this with multi boot? do you have the 5+ version bootmenu and recovery.
GGL roms are based on ginger bread kernel, once restoring the system we need to restore boot/devtree for gb kernel installations, it is to be done through customer recovery restore. You should be able to boot into GGL rom once you do this.
If it is still taking you to stock 2.2.2 means, probably you are trying in multi boot and it will not work the ROMs with different kernels. For you to boot into virtual system, you should go to boot menu and select 2ndboot option.
Click to expand...
Click to collapse
Yes,My Defy with Green Lens..im on stock 2.2 im not trying to multiboot...and jst i want to use the GGL Rom and followed the instructions and my boot it is 2ndinit and not cwm

you have CWM installed right, for you to restore nandroid backup?
If you have this, just go to custom/latest recovery and restore system+data,boot,devtree and recovery from the nandroid of GGL rom, after this youshould be able to boot into GGL, what am I missing here?

This is my Boot Menu imo it's not cwm

L7iharsha said:
This is my Boot Menu imo it's not cwm
Click to expand...
Click to collapse
The option that you selected is 'Recovery' only right, which I couldnt read it properly, that is CWM mode.
If you go there, you will find number of other options like install from update.zip, install from zip, backup and restore etc.
You should select backup and restore, and then Restore options, system+data by selecting GGL ROM directory after that Advance Restore and then boot&devtree restore.
Before this I assume you have put GGL nandroid directory inside sdcard/clockworkmod/backup.

premaca said:
The option that you selected is 'Recovery' only right, which I couldnt read it properly, that is CWM mode.
If you go there, you will find number of other options like install from update.zip, install from zip, backup and restore etc.
You should select backup and restore, and then Restore options, system+data by selecting GGL ROM directory after that Advance Restore and then boot&devtree restore.
Before this I assume you have put GGL nandroid directory inside sdcard/clockworkmod/backup.
Click to expand...
Click to collapse
Still it's not booting...

L7iharsha said:
Still it's not booting...
Click to expand...
Click to collapse
put the nandroid folder in sdcard/clockworkmod/backup/, if you access your SD card you should find GGLRom folder inside that, and if you further open the GGLRom folder you should see immediately boot.img, devtree.img, system.ext3.tar etc. (You can use any file explorer, preferably root-explorer or total-commander) Once you ensure these things, then you are set to install.
Restart your phone and when BlueLED lights, immediately press Vol-down, this would take you to boot-menu. Since the screenshot tells that you are at 1.0.5 bootmenu version, you should atleast have 5.0.3.1 and up recovery installed. Select 'Recovery' inside boot-menu, this would take you to recovery mode, you can select 'Stable' or 'Custom recovery' anything is Okay. ( incase you installed and use multi-boot, then stable recovery is for your main-rom, and custom/latest recovery is for virtual-rom)
Do factory data/reset, then go to Advanced and wipe Dalvik Cache. Then comeback and select Backup and Restore. Select Restore with the nandroid folder of GGLRom, restore system+data. Go to Advanced Restore, select using nandroid folder of GGLRom, restore boot, devtree and recovery(if there).
Just precautionary, you can wipe cache data/factory reset, and Advanced wipe Dalvik cache. Reboot Now. Wait for few minutes, since dalvik cache is wiped, it may take 3-5min for complete bootup.
Your defy should now start with GGL Rom if all the steps are done correctly. This is the procedure for any nandroid ROM installations.

Thanks For Guiding Me Fixed it

[Q] CWM v6.0.4.3 N7100 problem in supporting Stock 4.3 ROM restoration

I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.

fatice said:
I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
Click to expand...
Click to collapse
I did not find the problem with restoration using CWM, but did find out what causes the wakelock: "Automatic call recorder Pro".
Disable the auto start function and battery drains is back to 1% per hour during standby.

fatice said:
I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
Click to expand...
Click to collapse
I have to say, I did encounter the replication of the same exact problem. It kept popping up "unfortunately com.google.process.gapps has stopped". I was using the same CWM recovery 6.0.4.3 for my N7100 using stock android 4.3.
Try to do so many things but fail to get rid of the pop up. At the end, I ended up having to flash rom using Odin.
Anyway, I think, there's some bug with CWM recovery 6.0.4.3 that caused the error to happen. I managed to use TRWP 2.6.3.1 without any problem to restore after that.
Regards,

Had exactly same problem, i downgraded cwm from 6.0.4.6 to 6.0.4.4 by using odin
Than restore works fine no problems with services.
Note 3 sm-n900w8

warlab said:
Had exactly same problem, i downgraded cwm from 6.0.4.6 to 6.0.4.4 by using odin
Than restore works fine no problems with services.
Note 3 sm-n900w8
Click to expand...
Click to collapse
Hi.
How did you downgraded CWM using odin? I am stuck in the same problem.
Khizer Jalal

khizerjalal said:
Hi.
How did you downgraded CWM using odin? I am stuck in the same problem.
Khizer Jalal
Click to expand...
Click to collapse
Download image and overwrite existing one

Now i see that i have entered the rooting world in it's darkest time
I had the exact same problem of yours with CWM 6.0.4.3 and and the exact same problem with titanium backup(when i restore APP DATA for almost all apps they crash and keep popping messages). so there was no restore feature for me for long time
BUT TB restoring of App data is fixed when i updated TB to latest version and the CWM nandroid after-restore problem is fixed when yesterday i upgraded to philz 6.46.3, the restored ROM works flawlessly.
Now I think(not sure) what was going on is related to something called "FIX Permissions" or in other words when we restore system + data things get messed up that each app can't find it's own DATA folder causing it to crash. CWM and titanium backup didn't use to fix that mess but now they do so these problems won't occur anymore.

[SOLVED]Unable to boot to recovery; Storage 'Unavailable' SD storage unavailable.

Hello, thank you for reading my thread I am thrilled to hear some great solutions !
Let me go ahead and share some back story to how I got where I am at.
1. I rooted, unlocked bootloader and installed twrpv20.img
2. My phone has been on the stock rom rooted with an unlocked bootloader since August 2015.
3. Reading around I found that there is CM 13 and I loved the CM builds on my HTC One m7. I decided I would download it and flash the rom through TWRP.
THIS IS WHERE I SCREWED UP(I think)
4. I cleared my cache, davik and data. Proceeded to install CM13 hima nightly 2/29/16 rom. The install failed.
5. Whatever reasoning I was thinking, I decided that maybe why this did not install is because of the age of twrpv20, I would flash twrpv20 recovery to the current CM nightly recovery that was with the CM13 rom.
6. I proceeded to attempting to flash the CM13 Rom from my SD Card... but wait... my SD card was not there anymore, I could not find the file system. I then proceed to plug my sd card into my computer and it was there...
7. I booted into my regular stock 5.1 android HTC one rom and proceeded my day.
8. Through my day I found out that my phone storage was 'unavailble' and my sd card storage was unavailable.
9. So my storage(s) became corrupted somehow.
10. I decided that it would be best if I attempted to revert through adb fastboot to TWRP and either reinstalling stock or attempt CM13 again on a more updated twrp3.0.0.2-hima.img
11. I successfully flashed it on my computer, yet on the phone it was unable to boot into recovery mode.
<span class="EmojiInput mj232" title="Black Diamond Suit "></span>This is where I am at now.
<span class="EmojiInput mj232" title="Black Diamond Suit ♦"></span>I have a 'google play services not running' error
<span class="EmojiInput mj232" title="Black Diamond Suit ::diamonds::"></span>my storage is 'corrupted' (in PC it is displayed as 'generic hierarchy' and I cannot view it.
<span class="EmojiInput mj232" title="Black Diamond Suit ::diamonds::"></span>In the phones photos/file explorer/setting-storage it shows as null/empty/unavailable
My questions are:
• How do I recover my recovery mode?
• How do I flash to CM13 successfully after installing ______ recovery?
Note: Ideas I have thought of from reading other topics as well as some random youtube videos is factory reset on the phone(complete wipe).
Another idea was to format the internal storage of the phone from my PC(sounds like a terrible idea).
The best idea, I do not know how to do, is somehow format my internal storage from my phone in download mode from ADB.
Best regards, Insan3

Try flashing twrp 2.9.0.1.
Sent from my HTC One M9 using Tapatalk

Agreed, you need an up-to-date version of twrp. Also, what firmware are you on? I don't think CM13 will boot on anything but MM firmware.

So I figured out what happened. When I was in the initial TWRPv20.img recovery, fiddling around with the buttons in there I hit mount USB storage(note this unmounts your internal storage).
Okay so what I did to fix this(Shout out to https://www.youtube.com/watch?v=H-vf5eHV3_s - Team Nocturnal)
I followed the instructions of the video(to an extent)
Booted into download mode - adb reboot download
Fastboot flash recovery (Path\:HIMA_UHL_Stock_Recovery_1.32.401.8)
In the phone I booted to bootloader -> recovery -> format/wipe data -> reboot to bootloader -> reboot to download
Fastboot flash recovery Path\:twrp-2.8.5.0-hima.img
From there: -> booted into bootloader - > booted into recovery - > successfully booted into TWRP 2.8.5.0
Selected "Mount"
Checked the 'Mount' for internal storage.
For the SD card I plugged the SD card via USB reader and used 'Scan and fix' option my PC prompted me with.