CleanRom 6 R2 hanging on first boot---"Broken" root? - Verizon Samsung Galaxy S III

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.

Related

miui and CM7 keeps cycling the inital loading

hi all,
Ok, I'm new to this stuff.
1. used the simple root and it worked great.
2. I then flashed CM7 and it worked great except market was not on it.
3. I downloaded and flashed gapps-hdpi-20101114-signed.zip by mistake, not realizing I had to use another gapps.
4. After I flashed it, the cm7 and android setup screens kept cycling between each other.
5. I restored to clockworkmod (sp) and then deleted the gapps and tried to then flash cm7. It didn't cycle between cm7 and android setup, but the cm7 screens kept cycling and never got past that.
6. I thought perhaps it was just cm7 now, so I tried miui and it's doing the same thing. It's cycling between the gingerbread man and MIUI with the status bar and won't do anything else.
Very frustrated. what have I done and how do I fix it?
Thanks folks,
Brett
I believe that those ROMs both require ENG S-OFF. Open simple root on your computer, click Fixes, then apply the fix there. Also, did you make sure you cleared your Dalvik cache before flashing? Always do a factory reset AND clear dalvik cache when changing ROMs.
make sure you have wifi off in your first boot
ardynine said:
make sure you have wifi off in your first boot
Click to expand...
Click to collapse
From reading the first post, he got in, rebooted to flash gapps and ended up in bootloop afterwards
EtherealRemnant said:
From reading the first post, he got in, rebooted to flash gapps and ended up in bootloop afterwards
Click to expand...
Click to collapse
Thanks ER. I'll try your method this evening.
I'll report back.
thanks!
brett
EtherealRemnant said:
I believe that those ROMs both require ENG S-OFF.
Click to expand...
Click to collapse
I can say with no doubt whatsoever, no.
id10terrordfw said:
I can say with no doubt whatsoever, no.
Click to expand...
Click to collapse
any suggestions then???????
I tried doing the ENG-off and still the same hang up on the front screen.
Any help please?
thanks,
brett
what method do you use to flash cm7? what exactly do you do.
to clarify what is your exact process for flashing the rom?
mudknot2005 said:
what method do you use to flash cm7? what exactly do you do.
Click to expand...
Click to collapse
Hi. Thanks.
I use rom manager to boot to recovery. Then I install zip from sd card. I go through the process until it says reboot. It's when I reboot that I get stuck in the bootloop. It just cycles from the CM7 circular arrow to blank and then to the arrow thing again. MIUI does the same between the gingerbread guy and the status bar and back.
I then take the battery out, take out the sdcard, down volume & power, reinsert sdcard and do a restore so I can use my phone again in clockworkmod 3.0.0.6.
thanks,
brett
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
mudknot2005 said:
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
Click to expand...
Click to collapse
actually, I did that.
it's weird. I restored a few times, did the above you suggested, and still in a loop. The first time I installed CM7 it was great, then the gapps thing seems to have screwed it up.
I'm lost.
brett
bdws1975 said:
actually, I did that.
it's weird. I restored a few times, did the above you suggested, and still in a loop. The first time I installed CM7 it was great, then the gapps thing seems to have screwed it up.
I'm lost.
brett
Click to expand...
Click to collapse
Probably a silly question but you're doing full reinstalls, right? Not using a nandroid backup? I can't think of any reason that you should be boot looping permanently from flashing the gapps if you're going into clockwork, doing a factory reset, wiping the cache, then wiping the Dalvik cache, then flashing the ROM.
EtherealRemnant said:
Probably a silly question but you're doing full reinstalls, right? Not using a nandroid backup? I can't think of any reason that you should be boot looping permanently from flashing the gapps if you're going into clockwork, doing a factory reset, wiping the cache, then wiping the Dalvik cache, then flashing the ROM.
Click to expand...
Click to collapse
hmm. I'm a little new to this, but I'm using the backup/restore option in recovery mode and am then flashing one of the backups. Could that be the problem?
If it is, how do I do a full reinstall?
thanks again for your help,
brett
mudknot2005 said:
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
Click to expand...
Click to collapse
Without a full wipe I thought it would just bootloop?
Do a full wipe then reinstall cm7 and gapps.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
bdws1975 said:
hmm. I'm a little new to this, but I'm using the backup/restore option in recovery mode and am then flashing one of the backups. Could that be the problem?
If it is, how do I do a full reinstall?
thanks again for your help,
brett
Click to expand...
Click to collapse
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
EtherealRemnant said:
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
Click to expand...
Click to collapse
I'll give it a shot and then get back to you.
I do believe, however, that the restore I'm doing is the backup I did right before I did the original cm7 flash. I'll try.
thanks!
If you toggle wifi on after the first boot it goes into a bootloop. This is a know bug not a hunch.
EtherealRemnant said:
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
Click to expand...
Click to collapse
DUDE!!!! You freaking rock. I got it!
I installed MIUI and it's amazing. Thank you very much.
Brett
Mustang302LX said:
Without a full wipe I thought it would just bootloop?
Do a full wipe then reinstall cm7 and gapps.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
Click to expand...
Click to collapse
thank you!!!!! I really appreciate your help!

[Rom] CM9 Barely Alpha ***UPDATED OP***

To Flash****UPDATED******
- Boot into safestrap
-Select safe system
-toggle safe system on
(It seems we have an issue wiping the safe strap /data and /cache so these additional steps are needed for now)
-quick toggle safe system off *****MUST BE A QUICK TOGGLE*****
-wipe data/factory reset
(To be safe wipe the following)
-Wipe Cache partition
-format /system
-wipe dalvik cache (Found a bug in safestrap that prevents us from wiping dalvik cache see thread)
-quick toggle safe system on *****MUST BE A QUICK TOGGLE*****
Now, flash the rom. (Selecting external Sdcard)
Safestrap works alot like a dual boot, so you can always return to your stock system by simply disabling safestrap in the safe boot menu.
http://forum.xda-developers.com/showthread.php?t=1425026
This is ics for the droid 3 by hashcode, same guy that gave us permission to unofficially port and support safestrap. It does boot and work on our phones.
This is what i know for sure right now
-Wifi works
-Most tasks and apps work
-market is broken
-calling/texting is broken, looks like its stuck on cdma?
-accelerometer is broken
What I'd like to see from here is some one willing to take over my project on this rom. I have a few of my own flash able zips complied with various tweaks to hopefully be able to make and receive calls, no success yet. I will keep trying but this is a project better suited for some one who is not so new to the linux environment. (I just got my first linux box 2 weeks ago)
Please enjoy and the thanks button is below the download link
http://forum.xda-developers.com/showthread.php?t=1425026
Proof It works! http://youtu.be/B_J3fs80dV0
**************-Edit*************************************************************************
I have decided to take on this project. I will post a more "ported" version as I progress on it, These things take time so please be patient. The information contained above should only be used as a "prof of concept" sort of thing. Anyone willing to help may do so here: http://forum.xda-developers.com/showthread.php?t=1428117
Great work !!! Thank you very much!!! Waiting the update!!
Don't we need the source code for the Atrix 2 to make this work?
I've followed all the steps in safestrap, got it working, except mounting SD (is that expected?), but after I flash the CM9 zip while in safe mode, I reboot and get stuck with a black screen. Anyone else get this working? It seems to flash rather fast which seems abnormal to me.
I agree that this Alpha 4 is stuck on CDMA. If anyone has gotten 3g to work, please let me know how you did it. I tried entering their little trick *#*#4636#*#*, rebooted, wiped cache and dalvik like they said and still nothing.
lfaber06 said:
Flash this using safestrap only.
To Flash
Boot into safestrap
Select safe system
toggle safe system on
wipe data/factory reset
(To be safe wipe the following)
Wipe Cache partition
format /system
wipe dalvik cache
Now, flash the rom. (Selecting external Sdcard)
Safestrap works alot like a dual boot, so you can always return to your stock system by simply disabling safestrap in the safe boot menu.
http://forum.xda-developers.com/showthread.php?t=1425026
This is ics for the droid 3 by hashcode, same guy that gave us permission to unofficially port and support safestrap. It does boot and work on our phones.
This is what i know for sure right now
-Wifi works
-Most areas of the phone work
-phone is broken, looks like its stuck on cdma?
What I'd like to see from here is some one willing to take over my project on this rom. I have a few of my own flash able zips complied with various tweaks to hopefully be able to make and receive calls, no success yet. I will keep trying but this is a project better suited for some one who is not so new to the linux environment. (I just got my first linux box 2 weeks ago)
Please enjoy and the thanks button is below the download link
http://forum.xda-developers.com/showthread.php?t=1425026
Click to expand...
Click to collapse
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Why can't I get this to boot? I go into safestrap, put it on safemode, wipe all the necessary things, flash the zip, reboot, and I get a black screen. If I take it off safe mode it goes back to my stock ROM successfully.
Calundle said:
Why can't I get this to boot? I go into safestrap, put it on safemode, wipe all the necessary things, flash the zip, reboot, and I get a black screen. If I take it off safe mode it goes back to my stock ROM successfully.
Click to expand...
Click to collapse
Try this. Using safestrap, make a Full backup Including webtop to be safe. then disable safe mode and factory reset, then wipe dalvik cache, then format /system, then wipe /data, enable safe mode, flash it, and let me know.
lfaber06 said:
Try this. Using safestrap, make a Full backup Including webtop to be safe. then disable safe mode and factory reset, then wipe dalvik cache, then format /system, then wipe /data, enable safe mode, flash it, and let me know.
Click to expand...
Click to collapse
Alright I'm trying it as we speak. So is the SD card currently unmountable in safestrap? If I do a backup while in safemode, won't that backup the safemode ROM, which is the CM9 one I can't get to work? I don't really understand how the safemode/no safemode works. I was under the impression that my stock ROM is under no safemode so anything I do with safemode off will effect that (meaning when I do the format and wipes you're talking about it would do that to my stock ROM), then when I turn safemode on everything I do effects the other ROM. Can you clarify for me?
Calundle said:
Alright I'm trying it as we speak. So is the SD card currently unmountable in safestrap? If I do a backup while in safemode, won't that backup the safemode ROM, which is the CM9 one I can't get to work? I don't really understand how the safemode/no safemode works. I was under the impression that my stock ROM is under no safemode so anything I do with safemode off will effect that (meaning when I do the format and wipes you're talking about it would do that to my stock ROM), then when I turn safemode on everything I do effects the other ROM. Can you clarify for me?
Click to expand...
Click to collapse
Not exactly..... safestrap knows which ROM is your stock system, and which one is the "safestrap". It calls your stock rom /systemorig or something similar, and then when in safe mode, it will mount the stock system to /systemorig and back that up as well as /system, which will be the CM9 rom, that is why you had to partition your card a certain way, to make this work right.
jimbridgman said:
Not exactly..... safestrap knows which ROM is your stock system, and which one is the "safestrap". It calls your stock rom /systemorig or something similar, and then when in safe mode, it will mount the stock system to /systemorig and back that up as well as /system, which will be the CM9 rom, that is why you had to partition your card a certain way, to make this work right.
Click to expand...
Click to collapse
Ah thanks for the explanation. So, when you backup it does a backup of both system and systemorig, both roms, how do you go about wiping one rom and not the other? Am I correct in saying if you have safemode off and do wipes/restores it will do that to your stock rom, but if it's on it will do it to the systemorig one, then backing up with it off does a backup of stock rom, and when it's on it backs up both?
Calundle said:
Ah thanks for the explanation. So, when you backup it does a backup of both system and systemorig, both roms, how do you go about wiping one rom and not the other?
Click to expand...
Click to collapse
Safestrap will only allow you to wipe your non safe data. it will not let you wipe your safe system aka "stock rom".
lfaber06 said:
Safestrap will only allow you to wipe your non safe data. it will not let you wipe your safe system aka "stock rom".
Click to expand...
Click to collapse
Awesome. Sorry for all of the questions, I'm familiar with CWM, but this is new territory for me. I really appreciate it. I'm doing the steps you provided. Am I basically doing a complete backup, complete wipe of both ROMs, then trying to install CM9 on the safe partition?
EDIT: I don't want to clutter this thread with questions about safestrap so I'll take any further questions to it's thread. Thanks again.
Calundle said:
Awesome. Sorry for all of the questions, I'm familiar with CWM, but this is new territory for me. I really appreciate it. I'm doing the steps you provided. Am I basically doing a complete backup, complete wipe of both ROMs, then trying to install CM9 on the safe partition?
Click to expand...
Click to collapse
No, you will only be making changes to the safestrap ROM, not the system ROM.... The backup will currently only be the stock ROM. now if when you enable safestrap do a backup, then disable safestrap, while in safestrap and taking a backup, you can backup the "safetrap" ROM, not the system ROM....
Now if you follow the directions in the original post, you will end up with two bootable ROMs on your phone. you really are only interested in the safestrap one right now, so doing the backup before flashing will ONLY backup the stock ROM. and you will not wipe the stock ROM either so to speak, because you can "dual" boot both ROMs by enabling and disabling the safestrap.
jimbridgman said:
No, you will only be making changes to the safestrap ROM, not the system ROM.... The backup will currently only be the stock ROM. now if when you enable safestrap do a backup, then disable safestrap, while in safestrap and taking a backup, you can backup the "safetrap" ROM, not the system ROM....
Now if you follow the directions in the original post, you will end up with two bootable ROMs on your phone. you really are only interested in the safestrap one right now, so doing the backup before flashing will ONLY backup the stock ROM. and you will not wipe the stock ROM either so to speak, because you can "dual" boot both ROMs by enabling and disabling the safestrap.
Click to expand...
Click to collapse
Ah okay okay, I think I understand how it works now. I've tried the steps in the OP and the ones faber mentioned and I'm still getting a blank black screen after reboot. How long should it take to flash the CM9 zip? It takes like 6-10 seconds for me and from my experience that's rather short for a ROM. Could the zip have gotten corrupted?
jimbridgman said:
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Click to expand...
Click to collapse
Yup just tried it, I get "Unfortunately, phone has stopped" over and over so i guess its force closing.
So, without phone or 3g capabilities, this port is basically just pretty window dressing for our Atrix 2 right?
jimbridgman said:
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Click to expand...
Click to collapse
Has anyone tried this yet? If not I will mess with it and let you know what happens.
lfaber06 said:
Yup just tried it, I get "Unfortunately, phone has stopped" over and over so i guess its force closing.
Click to expand...
Click to collapse
duke8804 said:
Has anyone tried this yet? If not I will mess with it and let you know what happens.
Click to expand...
Click to collapse
Yep lfaber06 tried it, and if you read his reply noted in the top quote here in my reply it keeps force closing..... To bad, I am guessing because it is ICS and not GB, like out phone is currently.
jimbridgman said:
Yep lfaber06 tried it, and if you read his reply noted in the top quote here in my reply it keeps force closing..... To bad, I am guessing because it is ICS and not GB, like out phone is currently.
Click to expand...
Click to collapse
Sorry about that, I guess i overlooked that one.

[Q] Problem with S'perience ROM - Loses root when I install

I'd post a reply to the official thread, but I still can't as of now due to low number of posts.
So I downloaded S'perience ROM from here:
http://forum.xda-developers.com/showthread.php?t=1888350
Then I tried flashing it as needed. The phone restarts and voila, S'perience. However, I found out that I had lost my root.
Busy Box is installed, but when I checked via Root Checker, it told me that some SU binaries are not present, therefore my phone has lost root.
I tried rerooting my phone and flashing S'perience three times, but the same thing happen. Yeah, I did the usual factory rest, cache and data wipe, etc, and I have no idea why my phone loses root when I flash this ROM.
Can anyone help me?
I just contacted the author of that ROM.
Hopefully they'll be able to help you out
''Evil corrupts the mind of the weak but fails to feed off the mind of the strong''
Hi dude why didnt you pm me anyways Download this: http://forum.xda-developers.com/attachment.php?attachmentid=1266013&d=1345206743 and Flash it will fix your root Problem
Sent from my SK17i using xda app-developers app
So I just flash this right after I flash S'perience, right?
Thank you so much for your replies!
Okay, so I finally installed S'perience on my LWW. And for the sake of comparison and exploration, I'm trying out Hyperbeam.
So I did the following:
1. flashed .58 firmware,
2. unlocked bootloader
3. installed Rage Kernel
4. CWM
5. wipded data (factory reset)
6. wiped cache
7. wiped dalvik cache
8. flashed base ROM (Hyperbeam)
9. flashed patch
10. flashed lockscreen
Then reboot.
Now, my phone's undergoing bootloop for a good fifteen minutes. And it's still continuing as I type this. Anything I did wrong?
Thank you so much in advance.
holocoz said:
Okay, so I finally installed S'perience on my LWW. And for the sake of comparison and exploration, I'm trying out Hyperbeam.
So I did the following:
1. flashed .58 firmware,
2. unlocked bootloader
3. installed Rage Kernel
4. CWM
5. wipded data (factory reset)
6. wiped cache
7. wiped dalvik cache
8. flashed base ROM (Hyperbeam)
9. flashed patch
10. flashed lockscreen
Then reboot.
Now, my phone's undergoing bootloop for a good fifteen minutes. And it's still continuing as I type this. Anything I did wrong?
Thank you so much in advance.
Click to expand...
Click to collapse
You forget to wipe system
Do this
Wipe data
Wipe Cache
Wipe dalvik Cache
Under mounts and storage,Format system
Then Flash the Base,your patch and the lockscreen
Today i will Update my Roms to all in One ZIP
Sent from my SK17i using xda app-developers app

[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)

I have a custom rom, no Gapps, no root. please help

So my cousin had the this tablet she hadn't us for a while and she asked to to fix it up. Root it put some apps on it blah blah blah. So i rooted it using this: http://forum.xda-developers.com/showthread.php?t=1681155/
Everything was fine and it went smoothly, I had root access, TWRP recovery that it came with and it was working fine.
I wanted to put a ROM on it for my cousin to match her phone so I found this: http://forum.xda-developers.com/showthread.php?t=2584265
So, I flashed the Rom and it was fine. Then I flashed the Gapps and it said that the system partion didn't have enough space.
Here is where I screwed up (I think). TWRP said that I lost root access and i had to fix it BUT i had to swipe a bar at the bottom to fix it. My dumbass pressed the button in the middle of the screen which was to ignore it. I didn't see what i was doing and i messed up
So I lost root or something and when i turn on the device and try to boot into recovery by holding the Power + Vol Down keys it does not work!
Now I have a tablet with android 4.4.3, no Gapps, no root, no recovery. I have tried to factory reset it but the one in settings do not work.
I'm stuck and I need help from someone smarter. Thank you for anything.
Id start again, sounds like something in recovery got messed up if it thinks the system partition is not big enough for gapps
Flash TWRP with Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
Download ROM & Gapps to MicroSD Card
I suggest KatKiss #29 & Gapps from this link
http://forum.xda-developers.com/showthread.php?t=2592890
Factory reset & Wipe everything except External Storage from TWRP
Flash ROM
Flash Gapps
Wipe Cache & Dalvik Cache
Reboot
Nothing more nothing less is needed, so if it doesn't work by doing the above, there are other problems
ok so i installed the drivers it easyflasher was asking for and now it asks whether the device is SBK1 or SBK2, how do i find out whether the device is B70 or above... I feel dumb again... It also asks if its in APX mode... i need help again
ok i figured out the easyflasher and i get the recovery but, when im done flashing all the files and boot the device it says that i have to repair root, like before and even if i say to do so i lose the recovery every time meaning i have to go and put the recovery back onto it and do everything again.....
alrighty so ive got the recovery to stick, and i got the KitKatKiss rom which is actually really nice, however i don't have root, i keep trying to flash the supersu file but it does not work. thanks for everything already. it would be nice to have it rooted.......
RoughRunner said:
alrighty so ive got the recovery to stick, and i got the KitKatKiss rom which is actually really nice, however i don't have root, i keep trying to flash the supersu file but it does not work. thanks for everything already. it would be nice to have it rooted.......
Click to expand...
Click to collapse
KatKiss is already rooted by default, you should not flash an additionnal supersu zip.
Just Flash the rom then gapps from the KatKiss thread
wipe cache + dalvik-cache
then reboot.
If you're coming from another rom version, a full wipe / factory reset is recommended before flashing too.
RoughRunner said:
alrighty so ive got the recovery to stick, and i got the KitKatKiss rom which is actually really nice, however i don't have root, i keep trying to flash the supersu file but it does not work. thanks for everything already. it would be nice to have it rooted.......
Click to expand...
Click to collapse
QUOTE:
Nothing more nothing less is needed, so if it doesn't work by doing the above, there are other problems
--
As Tim says, and as I said, if you had just followed my instructions and not tried adding your own section of the process, you would have had no problems
timduru said:
KatKiss is already rooted by default, you should not flash an additionnal supersu zip.
Just Flash the rom then gapps from the KatKiss thread
wipe cache + dalvik-cache
then reboot.
If you're coming from another rom version, a full wipe / factory reset is recommended before flashing too.
Click to expand...
Click to collapse
ok thanks theres the problem all fixed thanks

Categories

Resources