Database Info

installing a rom, problem

Hello guys,
I know this might not be a problem for most of you, but for me it is :|
I tried to install a custom rom (Pixel Rom or CM9) but i got stuck. I used a tutorial, and then I tried to install Pixel ROM with TWRP recovery. After installing and rebooting, the phone gets stuck on the ROM's logo. I waited at least 15 minutes for every ROM but it won't pass it..
What can I do ? How can I make my phone work again ?

dsorinn said:
Hello guys,
I know this might not be a problem for most of you, but for me it is :|
I tried to install a custom rom (Pixel Rom or CM9) but i got stuck. I used a tutorial, and then I tried to install Pixel ROM with TWRP recovery. After installing and rebooting, the phone gets stuck on the ROM's logo. I waited at least 15 minutes for every ROM but it won't pass it..
What can I do ? How can I make my phone work again ?
Click to expand...
Click to collapse
did you do a data wipe, factory reset, before flashing one of those roms? try going back and wiping data, then flash one of those roms.

simms22 said:
did you do a data wipe, factory reset, before flashing one of those roms? try going back and wiping data, then flash one of those roms.
Click to expand...
Click to collapse
I did everything, but nothing worked with custom rom, then I flashed an official rom and started all over again with installing CMW, and now I managed to instal Pixel rom.

Anytime you decide to flash a new ROM make sure you follow whatever instructions the ROM developer has laid out. Proper wipe followed by flashing the ROM itself and then Gapps if not included in your ROM.
And never flash a custom kernel until after the first boot.
If you get stuck in a bootloop just pull your battery and hold Volume up + power to boot into your bootloader and select recovery and try again.

thanks for the advice guys I managed to install Pixel Rom

CleanRom 6 R2 hanging on first boot---"Broken" root?

Hi all,
I just discovered CleanROM yesterday, and I'm trying to throw it on my S3 now. Everything installs fine, I go through all of the choices, and at the end TWRP pops up and tells my that it ppears that mt root is "broken" and asks if I want to repair permissions. I tell it 'yes', it seems to do its job, and I reboot.
After that, I have waited 20 minutes with no boot. It starts the boot animation, which is a 4-color 'X' on the screen, and nothing more. I have looked around, and people say that on first boot, there are sometimes orphan files that need to be resolved, but they said maybe 6 or 7 minutes, not 20.
Some background:
I probably rooted about a month ago in order to install CyanogenMod
I am not sure what method I used to root the phone with, mostly because I had issues from the beginning(Apparently not unheard of with the S3), but I know that I am rooted.
My bootloader is also unlocked, AFAIK, since I wouldn't have been able to instal CM10 otherwise.
I am using TWRP 2.4 as my recovery and it seems to be working wonderfully.
Process:
I boot into recovery
Choose 'Install'
Point to my download of CleanROM and follow all prompts, choosing launcher, file manager, etc.
Tell it to wipe data and cache
After the install, there is the message from TWRP telling me that root is "broken"(I think that's the term it uses), and asks me if I want to repair permissions, and I of course repair them.
After rebooting is when nothing happens. I finally pull the battery and either try again, or restre my phone so I can use it. I'm probably 0/4 at this point, I downloaded the ROM from the Dev's site, and have no problems, since it gives no errors during install.
So I guess I have three questions:
1. Can I re-root my device? Will this help, or could it frak things up worse?
2. Is there a way to fix those file permissions for good? The fix doesn't seem to be holding when I choose "repair" in TWRP.
3. Is this a ROM issue instead, and should I downgrade a version? Also, is anyone else seeing this?
Thanks in advance for any help guys! :good:

Mikey1969 said:
Hi all,
Process:
I boot into recovery
Choose 'Install'
Point to my download of CleanROM and follow all prompts, choosing launcher, file manager, etc.
Tell it to wipe data and cache
After the install, there is the message from TWRP telling me that root is "broken"(I think that's the term it uses), and asks me if I want to repair permissions, and I of course repair them.
After rebooting is when nothing happens. I finally pull the battery and either try again, or restre my phone so I can use it. I'm probably 0/4 at this point, I downloaded the ROM from the Dev's site, and have no problems, since it gives no errors during install.
So I guess I have three questions:
1. Can I re-root my device? Will this help, or could it frak things up worse?
2. Is there a way to fix those file permissions for good? The fix doesn't seem to be holding when I choose "repair" in TWRP.
3. Is this a ROM issue instead, and should I downgrade a version? Also, is anyone else seeing this?
Thanks in advance for any help guys! :good:
Click to expand...
Click to collapse
I think you are referring to the /root partition, not actually being rooted.
The problem is your order of operations. You are wiping the ROM after you install! You are supposed to wipe data/cache BEFORE you install the ROM.
This is not a ROM issue, I just installed CleanROM 6r2 and it is fast as heck and worked fine. I suggest you boot into twrp and perform the install correctly.

shutin said:
I think you are referring to the /root partition, not actually being rooted.
The problem is your order of operations. You are wiping the ROM after you install! You are supposed to wipe data/cache BEFORE you install the ROM.
This is not a ROM issue, I just installed CleanROM 6r2 and it is fast as heck and worked fine. I suggest you boot into twrp and perform the install correctly.
Click to expand...
Click to collapse
I wondered about that, but using TWRP in the 'Install' mode, it doesn't prompt for wipe until after(Unless I'm doing something wrong there). Just to be clear, you're just suggesting that I manually wipe first, then let TWRP and CleanROM take me through the process after that, right?
Thanks

Boot into twrp.
Hit the wipe menu.
Wipe the top four boxes
(Wipe cache
Wipe dalvik cache
Factory reset.
Wipe system.)
Install ROM
Should boot within 2 minutes tops.
Sent from that young galaxy.
God bless the American People.

barrackOBAMA said:
Boot into twrp.
Hit the wipe menu.
Wipe the top four boxes
(Wipe cache
Wipe dalvik cache
Factory reset.
Wipe system.)
Install ROM
Should boot within 2 minutes tops.
Sent from that young galaxy.
God bless the American People.
Click to expand...
Click to collapse
That did it. Thanks!!

You mind hitting the thanks Button.
I'd greatly appreciate it
Sent from that young galaxy.
God bless the American People.

There ya go... Sorry, didn't even know the thing existed until yesterday.

[Q] Samsung Galaxy SIII d2spr

Hey guys, I am having trouble flashing some roms on my Sprint Galaxy SIII. Some of the unflashable roms include: Carbon 1.6, Pac-Man, and a few other's I can't remember the name of at the moment. Successful flashes so far are Slim, Cyanogenmod 10, and Carbon 1.5 (but with some minor issues). I googled this and the only things that came up where possible bad downloads but I have downloaded these bad ones over and over and have no different outcome. Okay so what happens when I try to flash these is it will say successful in clockwork recovery, then when I reboot the device it get's frozen in boot. On Carbon it just was black but the power button wouldn't respond until I pulled the battery out and put it back in so I assume it was in boot. Pac-Man shows the blue android Galaxy SIII screen and just stays there. I read somewhere to leave the phone for 15 minutes after a flash so I have tried that with both of these and nothing changes. The successful flashes don't take more that a minute or two. So I have no idea what is going on and now I am begging to think it might have something to do with my rooting method choice. Any suggestions or words of wisdom for me? Thank you!!!
Also so rule out some questions ahead of time: Yes I wipe system/factory reset, yes I wiped cache, yes I wiped Dalvik cache, I flashed them from my external sd card (sdcard1), I used the motochopper method of rooting from here: http://forum.xda-developers.com/showthread.php?t=2286241 , I had no problems with the motochopper root process according to the instructions. Okay I think that is all the standard questions, please ask if I missed one. Thank you again!

JacobGates said:
Hey guys, I am having trouble flashing some roms on my Sprint Galaxy SIII. Some of the unflashable roms include: Carbon 1.6, Pac-Man, and a few other's I can't remember the name of at the moment. Successful flashes so far are Slim, Cyanogenmod 10, and Carbon 1.5 (but with some minor issues). I googled this and the only things that came up where possible bad downloads but I have downloaded these bad ones over and over and have no different outcome. Okay so what happens when I try to flash these is it will say successful in clockwork recovery, then when I reboot the device it get's frozen in boot. On Carbon it just was black but the power button wouldn't respond until I pulled the battery out and put it back in so I assume it was in boot. Pac-Man shows the blue android Galaxy SIII screen and just stays there. I read somewhere to leave the phone for 15 minutes after a flash so I have tried that with both of these and nothing changes. The successful flashes don't take more that a minute or two. So I have no idea what is going on and now I am begging to think it might have something to do with my rooting method choice. Any suggestions or words of wisdom for me? Thank you!!!
Also so rule out some questions ahead of time: Yes I wipe system/factory reset, yes I wiped cache, yes I wiped Dalvik cache, I flashed them from my external sd card (sdcard1), I used the motochopper method of rooting from here: http://forum.xda-developers.com/showthread.php?t=2286241 , I had no problems with the motochopper root process according to the instructions. Okay I think that is all the standard questions, please ask if I missed one. Thank you again!
Click to expand...
Click to collapse
It's a good practice to wipe cache and dalvik AFTER flashing the ROM. Also, sometimes I'll have better luck flashing a particular ROM with TWRP if it doesn't flash well with CWM, and vice versa.

mcgrabowski said:
It's a good practice to wipe cache and dalvik AFTER flashing the ROM. Also, sometimes I'll have better luck flashing a particular ROM with TWRP if it doesn't flash well with CWM, and vice versa.
Click to expand...
Click to collapse
Oh, I haven't heard about wiping cache and dalvik after before, I will try that with one of them and see what happens. I did try TWRP once but it wouldn't do much of anything; I couldn't get it to mount the sd card, nandroid back up, and a few other things that I don't remember at the moment but maybe I had a bad download or install with that. Any suggestions on where to get it? I did it through goomanager last time.

JacobGates said:
Oh, I haven't heard about wiping cache and dalvik after before, I will try that with one of them and see what happens. I did try TWRP once but it wouldn't do much of anything; I couldn't get it to mount the sd card, nandroid back up, and a few other things that I don't remember at the moment but maybe I had a bad download or install with that. Any suggestions on where to get it? I did it through goomanager last time.
Click to expand...
Click to collapse
Nandroid backups are NOT compatible between TWRP and CWM, so that can always be tricky trying to switch between the two and still being able to restore if needed. As long as you don't delete the folder where your backup is stored on the SDCard, you should be able to flash back to your other recovery and restore if it doesn't work out.
I've flashed recoveries through GooManager, Rom Toolbox Pro and Rom Manager as well as downloading the recoveries directly from their website and flashed them manually. (CWM or TWRP)

strange bootloops

hey y'all i have a 6045i US and it keeps bootlooping it all started by flashing CM 12.1 4/03/16 verison by the marionetteso i also flashed gapps xposed and root so it gave me the bootloops so what i did is wipe data factory reset nothing worked so i flashed another ROM wipe data everything and flashed bootloop fix kernel and nothing,same results im at the homescreen and im doing things and bootloops from there even recovery rebooted alot lol im not sure why so i flashed another older verison of it (i risked btw) and it worked so with that recovery i flashed a TWRP backup from one of the threads to stock ROM wipe data etc. and nothing same results!!! bootloops from homescreen so if theres another way to fix id appreciate it so much a clean install as in out of the box also i tried the alcatel upgrade app and nothing everytime i shut down the phone and plug the USB it just turns on for some reason bootloader works still with fastboot commands so i dont know whats going on this is my first issue with this phone,thank you
EDIT: fixed i finally got the alcatel app to work mods please close this thread

OnePlus One - Won't boot RR , boot loop happens

Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment

wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!

Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful

wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination​ of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241

Thanks a lot, once again

Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!

HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM

wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?

HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?

Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.

HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode