Related
Hi All
Sorry for my bad English
I wanted to flash the following rom http://forum.xda-developers.com/showthread.php?t=1626331
but after flashing my phone keeps rebooting (looping on on boot)
On the same thread I came across a solution that creating a partition through recovery >> advance will fix the looping issue. But no matter which option is select in recovery menu the screen goes blank with REVOLUTIONARY logo in the center.
please HELP !!!
I flashed the rom through ROM MANAGER app in market
I have flashed other roms before and they worked fine but this one didn't.
Thanks in advance
Use the trackball to select, not power button.
Lesicnik1 said:
Use the trackball to select, not power button.
Click to expand...
Click to collapse
Thank you for replying
I'm able to select the option from menu but when I select advanced (or any other option from menu) and press the power button the enter it comes up with REVOLUTIONARY logo
Please help, Im not sure what to do now
Like I said use the trackball (little circular button on the bottom) to select. Not the power button.
swimmer21 said:
I'm able to select the option from menu but when I select advanced (or any other option from menu) and press the power button the enter it comes up with REVOLUTIONARY logo
Click to expand...
Click to collapse
I think what Lesicnik1 meant was: you use the power button to select recovery in HBOOT. In Clockworkmod you should use the trackball to select - not the power button
(although I remember slightly you could set the other too - but I'm not sure)
--- EDIT ---
On the other hand - if you already flashed other ROMs you should be used to that.
So if that's not your problem: have you tried to reflash this - or a different ROM? Besides that CM9 is officially experimental bootloops often are caused by not wiping caches. It's also a good idea to format system before flashing a totally different ROM.
eventcom said:
I think what Lesicnik1 meant was: you use the power button to select recovery in HBOOT. In Clockworkmod you should use the trackball to select - not the power button
(although I remember slightly you could set the other too - but I'm not sure)
--- EDIT ---
On the other hand - if you already flashed other ROMs you should be used to that.
So if that's not your problem: have you tried to reflash this - or a different ROM? Besides that CM9 is officially experimental bootloops often are caused by not wiping caches. It's also a good idea to format system before flashing a totally different ROM.
Click to expand...
Click to collapse
Thanks
I'm able to select the advanced option and I also created a partition EXT size 512 SWP size 0 but my phone is still not booting it keeps looping.
I have also noticed that very time I partition my SD card it gets completely formatted (even deleting the Zip file)
I have always been using the ROM manager app to install it worked fine but this rom keeps looping
should I partition and then install the Zip file or the other way ?
Am I doing any thing wrong .
Thanks again @Lesicnik1 and @eventcom
Partitioning the SD card does format it.
Do this.
Partition SD Card (not needed if you already did)
Go back to the main menu of the recovery
Mounts and Storage
Wipe Data
Wipe System
Connect USB cable to phone
Mount USB Storage
Put ROM's .zip file on
Re-flash ROM
I see (haven't read carefully) not an ICS ROM - just ICS style. If you used to have a CM ROM before wiping system shouldn't be necessary (but it wouldn't harm also) - I always do the following when flashing a new ROM: format system, wipe cache, flash the new ROM, flash GApps. The requirements of the thread say furthermore: "Wipe Dalvik,Cache and Data" - so first: have you done that?
Do you use custom mtd partitions on your phone? (as you always have to reflash the bravo-boot-file afterwards...)
eventcom said:
I see (haven't read carefully) not an ICS ROM - just ICS style. If you used to have a CM ROM before wiping system shouldn't be necessary (but it wouldn't harm also) - I always do the following when flashing a new ROM: format system, wipe cache, flash the new ROM, flash GApps. The requirements of the thread say furthermore: "Wipe Dalvik,Cache and Data" - so first: have you done that?
Do you use custom mtd partitions on your phone? (as you always have to reflash the bravo-boot-file afterwards...)
Click to expand...
Click to collapse
It worked it worked!!
I almost thought I killed my phone
I understand its not ICS. I just wanted a different UI
Thanks you so much @Lesicnik1 and @eventcom
swimmer21 said:
It worked it worked!!
I almost thought I killed my phone
I understand its not ICS. I just wanted a different UI
Thanks you so much @Lesicnik1 and @eventcom
Click to expand...
Click to collapse
glad to see you could solve it :good:
Hi, I am running TWRP v2.2.2.1 and my kindle fire is rooted. When I go to flash a rom it seems like it is finished, but never gives me the success popup. It also says its verifying the partition sizes and filesystems. The home and restart buttons appear and so once I flash it I restart and the bootloader for each rom I have installed consistently just keeps loading indefinitely and never goes into the OS. Any idea's? In the mean time I have a backup and am running the stock os.
Restarting the bootloader selection puts your device in fastboot. Try selecting system after your flash that`s what you should be doing.
Thepooch said:
Restarting the bootloader selection puts your device in fastboot. Try selecting system after your flash that`s what you should be doing.
Click to expand...
Click to collapse
after i flash "wipe cache, home, and reboot system" appear. Do you mean reboot system or am I wrong. The success popup never showed up again.
Jlobel said:
after i flash "wipe cache, home, and reboot system" appear. Do you mean reboot system or am I wrong. The success popup never showed up again.
Click to expand...
Click to collapse
Depends on what your flashing as far as the wipes go but yes when you select reboot then you select system if prompted. If you are flashing a completely different system. Wipe factory reset , wipe cache, wipe dalvik, wipe system, flash Rom and flash gapps then select reboot and select system if prompted.
Edit: The final thing that TWRP does during a flash is verifying file systems and verifying partitions sizes. When you see the buttons show for wipe davik/cache and reboot this indicates the flash is complete even if it doesn't throw a successful statement
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.
I have tried several ROMs (Genesys, Imperial, RR, CM, stock) and can not seem to be able to encrypt my phone. I have done the
Code:
su
pkill -KILL daemonsu
exit
thing and the phone reboots but does not encrypt. I have even gone as far as installing the unrooted stock ROM and setting it up, then encrypting it, THEN rooting it. However, I get tons of FC's and can not enter in the password to decrypt the device.
Does anyone have any ideas on getting encryption working with a rooted device? And no, running pure unrooted stock is not an option.
It can be tricky. Very tricky. Try disabling/freezing SuperSU. Also try going into safemode, then try. I've done it before, it just took a ton of trying. Hold the power off button until you get to the menu. Then press and hold the off option. You should see an option for safe mode in a second or two.
Since SuperSU is a system app, I believe it still starts in SAFE MODE. Also, I couldn't find SuperSU in Titanium Backup even when "System" apps were checked so I couldn't freeze it.
I think I might have succeeded. Here's how I did it:
Download Genisys 3.8 & Genisys Theme 3.6
Reboot to recovery
Wipe system, data, cache, and dalvik (3 times)
Flash Genisys 3.8
Boot up and sign in
*OPTIONAL* Reboot to recovery and flash Genisys Theme 3.6 and reboot system
Open SuperSU and under Settings ---> Full Unroot (should reboot automatically, if not reboot manually)
Encrypt phone ---> Full encryption ---> set pin (DO NOT set boot up pin/password, only unlock pin/password/knock/pattern)
Verify encryption by going to Settings --> Security ---> Encrypt Phone (Should say "Encrypted")
*OPTIONAL* Encrypt SD Card
Reboot to recovery and flash UPDATE-SuperSU-v2.46.zip.
Reboot System
No guarantees, but this worked for me. Remember, DO NOT set the boot up pin because there are tons of FC's preventing you from entering your pin/password on this screen. Just set the lockscreen pin/password/knock/pattern.
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
I have the same problem
Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???
I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.
Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.
karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9