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
Related
So I read the tutorial on how to remove the MTD mod. I cant seem to get it to uninstall though. I tried flashing a new recovery image through terminal emulator and then doing a factory reset/wipe. Here are the steps I did to attempt to get rid of the MTD mod, please let me know where I went wrong here, thanks.
Flashed a new recovery via terminal emulator
Rebooted phone into recovery
Performed a nandroid backup of current ROM
Performed factory reset/wipe
Rebooted recovery
Nandroid restore of ROM
When this didn't work I attempted this:
Rebooted into recovery
Modified mtdpartmap.txt file with MTD 0
Ran the boot patcher
Factory reset/wipe
Nandroid restore
Both methods did not remove the MTD resizing I did. What/where did I go wrong?
All I do is run the boot patcher then reboot.
Wouldn't nandroid restore just return it to whatever it was when you backed it up?
PcFish said:
All I do is run the boot patcher then reboot.
Wouldn't nandroid restore just return it to whatever it was when you backed it up?
Click to expand...
Click to collapse
Nandroid restore only restores the ROM itself though doesn't it which wouldnt impact the recovery image and boot flasher?
Ok, so I did the nandroid restore and then I ran the custom boot patcher with my mtdpartmap.txt set to MTD 0 and rebooted...looks like im stuck at the start up splash screen...what is going on???
EDIT: Figured it out:
Formatted system, data, and cache
Resized mtdpartmap.txt to "mtd 0"
Flashed boot patcher
Advanced nandroid restore of system, data, and cache
reboot
ROM booted right up and I am back to stock partition sizings.
Hi All,
Just tried to install the Latest Leedroid ROM (GB) but then the desire hung on the HTC white screen.
I used Clockwork to install the ROM, but before doing so backed up via clockwork.
Now i want to restore that backup, but can't find a way of doing it.
I have been able to get to the recovery screen using 'Flash ROM', however from here when i try installing clockwork via the the zip file it does not work.
I used the option resotre from Nand but no Nandroid folder exists.
Having interrogated the SD Card there is a folder called clockworkrecovery and it does contain a backup folder with files that have a .img extension.
Can someone please help me get back to a working ROM, or explain a way i can use the backup i took to recover my phone.
Thanks in advance.
I have been looking for a simple enough guide to follow (2hrs +) but i have found nothing.
the_last_don said:
Hi All,
Just tried to install the Latest Leedroid ROM (GB) but then the desire hung on the HTC white screen.
I used Clockwork to install the ROM, but before doing so backed up via clockwork.
Now i want to restore that backup, but can't find a way of doing it.
I have been able to get to the recovery screen using 'Flash ROM', however from here when i try installing clockwork via the the zip file it does not work.
I used the option resotre from Nand but no Nandroid folder exists.
Having interrogated the SD Card there is a folder called clockworkrecovery and it does contain a backup folder with files that have a .img extension.
Can someone please help me get back to a working ROM, or explain a way i can use the backup i took to recover my phone.
Thanks in advance.
I have been looking for a simple enough guide to follow (2hrs +) but i have found nothing.
Click to expand...
Click to collapse
Can you boot to recovery? ie; turn phone off. Hold volume button (-) and press power button? Should boot to recovery. Then you can navigate to select the recovery file.
Yes i can get to recovery, it give me a red triangle with an exclamation mark, at that point i use Flash ROM - recovery-windows.bat to get into recovery, it at that point i am stuck, because none of the options give me the ability to restore from the backup i took via clockwork
First go to Normal recovery (Red Triangle) by maintaining Vol Down + Power
and then press Vol Up + Power
This will bring you to another recovery menu where you can : Reboot , Flash from sd , Wipe Data/factory ,Wipe Cache
THANKS!!!!
Can't believe i spent that long for such a simple task!
the_last_don said:
THANKS!!!!
Can't believe i spent that long for such a simple task!
Click to expand...
Click to collapse
Not such a simple task, if you don't know about it.
On a more personal note, I've been reading a lot of issues with LeeDroid ROMs lately. Maybe it is the spring weather. And it concerns updating.
Just a notice...
Be sure to hit Thanks! If it helped.
Hi,
I need to restore the sense rom that I backed up with Clockworkmod GUI. Normally I'd boot into CWMRecovery and select it, but what I have backed up is a folder, not a zip. It has the boot.img inside. How do I restore this without using the GUI (in android)? Do I need to zip the folder up? I can't use the GUI in android because when it tries to download the CWMrecovery the app crashes. So I need to do it when I boot up if possible?
I hope someone can help?
there is no need for zip. you hav to do through recovery
Boot into recovery, select "backup/restore", then "restore", then select your backup. The same way you always would (cwm backups are never zips).
Note: recovery won't restore the boot.img, so you'll need to flash this manually via fastboot. Copy the boot.img from the backup folder to your PC before you start.
I need help to restore a nand backup: bootmenu was fired!
my defy+
ROM 4.5.1-134_DFP-89
KERNEL 2.6.32.9-gbdd614e
after reading on xda of a guy that could run the CM10 in multiboot, I thought "well" to update my multiboot and bootmenu convinced that it was the 1.1.18, however I found the bootmenu 2.0.0 beta touch that does not allow me access to recovery, and make nand backup/restore, on the other hand at least it can turn on and make calls.
But I have NOT a working wifi and I can't even reinstall bootmenu from "defy 2ndinit 2.3" app (crash while applying).
killer update is bm_cwm_mb_v1.2-signed.zip found in theese pages. Browsing in, I noticed that there is an installation script that does the backup of system files (folder \ system \ bootmenu and other files) and that there is also a script to restore. I also verified that; in folder \system there is backup folder but I don't know how to run script. I would like keep it as a last option (I'd prefer to do nand restore), but if some kind soul may explain to me how walking on this second way I'll be grateful.
thanks in advance
I just tried from cmd:
adb reboot recovery
then defy rebooted with warning prompt picture
press both + and - volume rocket
when recovery menu appeared: install zip file from sd: bootmenu1.0.4+CWM5.0.3.1+modules.zip
but while verifying signature it fails :crying:
If it is corrupted, the easiest way is to start over from RSD Lite. Start with a stock Tom.
Sent from my MB526
j16sdiz said:
If it is corrupted, the easiest way is to start over from RSD Lite. Start with a stock Tom.
Sent from my MB526
Click to expand...
Click to collapse
mmmh I just began starting titanium backup.. now while copying my app and data I see the not free option "restore from nand". may be my case?
searching for rsd tutorial and 4.5.1-134_DFP-89 rom (found "only" ...DFP-139)
Done! first time flash .now I have an updated rom and unaspected absence of lost data. only re-rooted and re-installed bootmenu. thanks a lot
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.