Database Users

[Q] installing a new rom

Hello, i own two vega. I bought one of the with cm7 installed, i exchanged several roms [corvus, cm7, different nightly] always with rom manager or from clockwork recovery. Never had a problem.
Bought a second vega with modaco r8 installed. Installed last rom manager, installed throught it the last recovery, downloaded the corvus image [checked hash, correct] and finally choose to flash with a full wipe, erased cache ect ect. Device rebooted, screen black. After 5 mins i pushed the power button, device turned on [screen backlight was on] but nothing else. Everything black.
Downloaded the official firmware 1.10, connected the vega to the pc and restored stock 1.10. Got root access with z4root, installed the market, downloaded rom manager, installed tfhe last recovery image. Rebooted in recovery and manually wiped and erased the caches. Installed tghe corvus. All processes went ok. Rebooted and once again black screen, not able to boot in recovery and not able to boot in corvus. Had to go back once again to stock 1.10
Whats wrong? Do i miss something?

I9505 Stuck at Boot + Recovery update loop after CM10.1 Nightly update

I'm having a rather weird issue right now. I've been running Victorator's Unofficial CM10.1 builds for a while and a couple of days ago I switched to the Official CM10.1 build for the I9505 (nightly of June 10th). Yesterday I updated manually to the June 11th nightly build (meaning I downloaded the zip file and installed it from Philz Touch Recovery). Today however, I tried updating to the nightly build of June 12th through the phone itself instead of manually downloading it and installing through the recovery.
The problem I have now is this:
- I updated to the new nightly build (June 12th) through Settings -> About -> CyanogenMod Updates
- The phone rebooted into Philz Touch Recovery and completed the update as far I know.
- It rebooted again but it was stuck on the boot logo (Samsung SIV GT-I9505).
- I pulled the battery and booted into the Recovery again
- The recovery is in an update loop, I can't wipe anything or do a factory reset.
- Pulled the battery again and booted into the recovery, it still wants to update (I tried multiple reboots from that point on).
So basicly, I can't boot into Android since the update probably failed, booting into the recovery gives me that update process every time. I can't access the functions of the recovery at all, I only get the update screen again and again. I'm at work now so I can't really do anything about it I guess, unless somebody has some tips? If not I'll try to install the Stock ROM again at home through Odin, since that's the only solution in my head right now. Hopefully it'll work after that, but to be honest, I'm not updating on the phone itself anymore, I'm just gonna do it manually on the PC from now on.

thisisfraa said:
I'm having a rather weird issue right now. I've been running Victorator's Unofficial CM10.1 builds for a while and a couple of days ago I switched to the Official CM10.1 build for the I9505 (nightly of June 10th). Yesterday I updated manually to the June 11th nightly build (meaning I downloaded the zip file and installed it from Philz Touch Recovery). Today however, I tried updating to the nightly build of June 12th through the phone itself instead of manually downloading it and installing through the recovery.
The problem I have now is this:
- I updated to the new nightly build (June 12th) through Settings -> About -> CyanogenMod Updates
- The phone rebooted into Philz Touch Recovery and completed the update as far I know.
- It rebooted again but it was stuck on the boot logo (Samsung SIV GT-I9505).
- I pulled the battery and booted into the Recovery again
- The recovery is in an update loop, I can't wipe anything or do a factory reset.
- Pulled the battery again and booted into the recovery, it still wants to update (I tried multiple reboots from that point on).
So basicly, I can't boot into Android since the update probably failed, booting into the recovery gives me that update process every time. I can't access the functions of the recovery at all, I only get the update screen again and again. I'm at work now so I can't really do anything about it I guess, unless somebody has some tips? If not I'll try to install the Stock ROM again at home through Odin, since that's the only solution in my head right now. Hopefully it'll work after that, but to be honest, I'm not updating on the phone itself anymore, I'm just gonna do it manually on the PC from now on.
Click to expand...
Click to collapse
Since its not going to recovery properly i also see one option which is flash a stock firmware using ODIN

123hiten said:
Since its not going to recovery properly i also see one option which is flash a stock firmware using ODIN
Click to expand...
Click to collapse
I just got home and I immediately booted into download mode to flash the stock firmware through Odin, but it keeps failing on me.
On the other hand, when I boot into the recovery it now says that the firmware upgrade encountered an error and that I need to recover the phone through Kies. I'm now trying to flash a custom recovery again, but Odin freezes up in the middle of the process

Ok, another USB-port, USB-cable, some battery pulls and driver re-installs later I managed to flash the stock rom again. It didn't boot into the stock rom though, it was stuck in a boot loop. Then I flashed a custom recovery again (this one) and I'm not getting the update loop anymore. I restored a backup I made yesterday (thank God I made one) and the phone is working again.
Instead of updating to the latest nightly build of CM10.1 on the phone itself, I'm now gonna try doing it manually.
So happy right now :laugh:

thisisfraa said:
Ok, another USB-port, USB-cable, some battery pulls and driver re-installs later I managed to flash the stock rom again. It didn't boot into the stock rom though, it was stuck in a boot loop. Then I flashed a custom recovery again (this one) and I'm not getting the update loop anymore. I restored a backup I made yesterday (thank God I made one) and the phone is working again.
Instead of updating to the latest nightly build of CM10.1 on the phone itself, I'm now gonna try doing it manually.
So happy right now :laugh:
Click to expand...
Click to collapse
Finally happy to hear that :thumbup:
Sent from my GT-I9500 using xda premium

From other comments I've seen, the cm update feature causes problems. You are best off manually flashing updates.
Trick: you can create an Odin flashable recovery by:
- unzip the recovery installation zip file
- create a tar file of the recovery.img using 7zip.
Sent from my GT-I9505

[Q] Stuck on bootlogo after flashing custom rom

I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...

No suggestion, but I just flashed SlimBean on mine from a full wipe, and I'm having the same issue.
I tried SlimBean again, and it worked. Here's what I did:
1. Updated my bootloader. Mine was still 4.13, and it looks like the most recent version is 4.23. I flashed the img from this post using NRT.
2. Went back to unrooted stock with NRT. (I had to update my bootloader to do this.)
3. Let it boot back into unrooted stock, wept with joy, made a nandroid from NRT.
4. Flashed the SlimBean 1.9 weekly and minimal gapps from NRT's advanced area.
5. Watched in amazement as it boots obediently. Let sit about 10 min, and rebooted.
I'm essentially lazy, so yes I used NRT instead of manually pushing everything with ADB. ADB was plan B. It was briefly plan A, but I got tired of trying to convince the Android SDK that I did in fact have the Java JDK installed.

Mhhhh....
PatrickMac said:
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
Click to expand...
Click to collapse
Well I have the same problem with booting Ubuntu touch.... Either it's stuck on white Google Logo or stuck on Cyanogenmod Logo... Have flashed it with TWRP and MultiROM...

[Q] Having trouble installing Quarx's new CM11 build

Hey guys,
As I wrote in the title I ran into a problem when installing the new CM11 nightly build from Quarx on my Defy. Here's what I did:
1) Downloaded the recovery update: http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip
2) Downloaded this CM11 nightly build: http://quarx2k.ru/roms/defy-cm11.0/cm-11-20140501-NIGHTLY-mb526.zip
3) Rebooted into recovery and installed the recovery update. The install seems to have finished without problems, although after another reboot my recovery still read as "JB Recovery v5.7.0-jordan".
4) Did a data and cache wipe.
5) Tried installing CM11, but the installation was aborted by a "status 0" error right after the "installing update..." part.
What am I doing wrong? I assume this has something to do with the recovery update, but since as far as I can tell it was successfully installed I don't know what could I do to fix it.

Now that I got time I started reading Quarx's CM11 thread and apparently in these cases installing CM10.2 first may help (I was using CM10), as it also updates the recovery, which is TWRP in the case of the as of now latest CM10.2 nightly. After I did this I tried installing CM11 again and this time the install went without a hitch. So if anyone else runs into this issue try this first.

For the next time remember that you've to reboot the device after installing that recovery in order to TWRP do the actualization

MaicolS said:
For the next time remember that you've to reboot the device after installing that recovery in order to TWRP do the actualization
Click to expand...
Click to collapse
I did restart my phone after installing the recovery update, I just forgot to mention it.
Since my last post I realized that the problem was that the CM10 nightly build I used before still came with the CWM recovery, not with TWRP. The reason is that some of Quarx's old builds didn't play nice with TWRP at the time. Since Quarx didn't explicitly say in his thread that the recovery update was for TWRP I just assumed that it was for his old builds that came with CWM. That doesn't seem to be the case however.

Chawitsch said:
Now that I got time I started reading Quarx's CM11 thread and apparently in these cases installing CM10.2 first may help (I was using CM10), as it also updates the recovery, which is TWRP in the case of the as of now latest CM10.2 nightly. After I did this I tried installing CM11 again and this time the install went without a hitch. So if anyone else runs into this issue try this first.
Click to expand...
Click to collapse
Easier method: just flash defy_twrp_recovery_2.6.3.0.zip, as explained in the installation guide.

Thanks for the link Proverbs, I'll do that the next time I'll need to update TWRP. Like I said, I didn't realize that Quarx's recovery update was for TWRP. If I did, I would have flashed TWRP separately and then CM11. What matters is that everything turned out OK in the end.

Mako always booting into recovery

Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.

Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse

Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.

+1
Done the whole process from scratch again and worked like a charm

Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?