I'm trying to install the SUPERLITE CM10 JB4.1.2 RoM by vincom. I've followed the installation instructions as well as I can, using TWRP 2.4.2.0 and making sure to wipe cache, dalvik, system and factory reset twice. TWRP finishes flashing the new rom without giving any error messages, which I assume means all went well.
However, when I reboot from TWRP after flashing the rom, it stays stuck at the boot animation. Vincom's guide says the initial boot after the flash should take a minute, but I've left it for up to ten minutes and it just stays at the looping boot animation. If I pull the battery and restart the phone, it'll go back to the boot animation, but then a message appears, saying "android is being upgraded | 0/61 apps". It'll go up to 61/61 then disappear, which I assume means whatever it was doing is finished, but just stays stuck on the boot animation. And yes, I've made sure the MD5 checksum of the downloaded file matches the one listed at the download website.
For the time being, I'm going to go back to nandroid backup and install CWM recovery, and try to reflash the new rom from there, but I'm wondering if anyone has any idea why this is happening?
If it makes any difference, the rom I was on before is [TouchWiz] EMBRYO 6 -5 (The Gold Standard) (now the rom is up to release 6 -8, I am currently on 6 -5 but I was too lazy to update, then I decided to switch to vincom's superlite CM10)
Very good possibility you had a bad download. Try downloading it again and see if the problem persists
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Unfortunately, it still fails. There are two versions of the superlite CM10 rom, one with slim gapps and the other without. I made sure the MD5 checksums match the ones listed on the download pages. Both stay stuck at the boot animation. Flashing from CWM recovery didn't change anything, either.
RGM79 said:
Unfortunately, it still fails. There are two versions of the superlite CM10 rom, one with slim gapps and the other without. I made sure the MD5 checksums match the ones listed on the download pages. Both stay stuck at the boot animation. Flashing from CWM recovery didn't change anything, either.
Click to expand...
Click to collapse
This may sound like a real pain to do...but... you can go thru Odin and return to stock. Erase your internal memory and sd card. Then re-root.
I did that myself not to long ago due to my phone lagging on any rom I flashed.
I am now running Jedi Jelly 6....and it the SH%T.
Alright, I'll give that a try when I have time and I'll see how it goes, thanks.
In that case that rom's kernel was faulty. You can either restore to your old backup or mount sd card and install another rom. If you want that rom really bad wait for an update and pm the developer
---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------
I dont think it is ur phone or the current rom your running's fault i think it is just a bad rom u downloaded.
Yeah, that does sound right. I've updated my current rom instead for the time being, thanks for the replies.
Related
So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.
Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you tried unrooting and rooting again?
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Lastly - I have heard people needing to reflash several times before it "takes" which it sounds like maybe you've tried & I realize these may be very basic things for you but you never know hopefully someone can help the more info you provide.
ldd_recoil said:
Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you ever successfully loaded a custom rom on this particular phone?.... because you may have improperly rooted
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Click to expand...
Click to collapse
I am on a custom rom now and everything is fine..but when I try to flash anything other than a Touchwhiz rom it seems to fail. I had paranoid running for a little while but I could not access my external sd so went back to my Jedi Mind Trick rom and everything was fine...so I decided to try a different paranoid thinking the issue was with this specific rom and it would not boot..went back to JMT and then tried aosp cm10 rom thinking and it wouldn't boot.
i have tried everything you have suggested except for the Factory Reset after the flash. Never really check the MD5 though. Might give it a try later on when I get bored with this rom again.
Thanks,
T
Sorry, reread your post now that I have the right context... Try unrooting and rerooting if you continue to have new rom flash issues.
toreone said:
So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.
Click to expand...
Click to collapse
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:
srikanth.t989 said:
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:
Click to expand...
Click to collapse
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
EDIT::: THIS WORKED...IT WAS HUNG UP ON BOOT IMAGE..FOLLOWED INSTRUCTIONS ON TOP AND BINGO!!!! I SAW THE MAGIC
toreone said:
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
Click to expand...
Click to collapse
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
I actually tried this yesterday and it went through the motions and when I restarted into recovery it was just like a blue background with the Team Win on it but never made it past that...so I had to flash back to CWM through Odin to get it to be able to flash again..
cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
After doing this try downloading quickboot to boot into twrp recovery, if that doesn't help you might need to flash back to stock/re-root and start from square one =/
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
so i had trouble updating my infamous rom and decided to wipe everything. i didnt like twrp so i reinstalled cwm wia odin and then restarted the phone into cwm and selected install zip. i then selected the new liquid smooth kang and it says in cwm that the insta;ll was sucsessful and then i reboot and i know that it can take up to 5 minutes to get past the initial boot up and into android for the first boot. yet the phone hasnt made it past the liquidsmooth loading screen and has not booted into android after 10 minutes. i have tried to install a different rom instead with the same issues. any ideas what my issue could be?
Sounds like you might have a bad download. Did you verify an MD5 checksum? Try to re-download the file and see how that one goes. Of course let us know what you find.
Edit: I noticed you tried with another ROM as well. What version CWM are you running and what is your procedure to wiping the phone.
Sounds like a case of the infamous Liquid RC brick. Can you post the exact file name you downloaded?
Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
djwuh said:
Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
Click to expand...
Click to collapse
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
xBeerdroiDx said:
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
Click to expand...
Click to collapse
I have sgh i747 at&t us model. Unlocked Sim for Tmobile use. Before having problems. I flashed vanilla rootbox att nightly. it was running fine then I flashed acid audio mod. And it worked but not well with my player of choice. So i flashed a restore from fright before the sound mod. And all I got was 2 different Samsung logos then black screen. At this point Twrp started asking for a password. I tried an older backup. (rootbox stable) and it booted fine. Everything seemed to be working. But when I rebooted again I got the 1St SG logo then black screen. Now recovery doesn't read anything on the internal card as well as the other problems I stated. I used mskips toolkit to flash Twrp originally and now I've been flashing back and forth between recoveries using recovery flashable zips. Also every time I flash roms or restore I did factory wipe/cache/dalvik and after I started having these issues I tried wiping system and that didn't help either. Thanks for trying to help
Sent from RootBox infected sensation or my PacMan e739
what recovery are you currently sitting on?
Twrp 2.4.4.0 is what I started with and now I'm back on it but from a flashable zip this time instead of whatever mskips toolkit used
Sent from RootBox infected sensation or my PacMan e739
here is the link to an odin flashable twrp 2.5.0.0 tar: http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.5.0.0-d2att.tar
and here's a recovery flashable twrp 2.5.0.0 zip link: http://forum.xda-developers.com/attachment.php?attachmentid=1917517&d=1367104589
if you flash in recovery, be sure to reboot recovery in order to boot into the new version. i'm sure you know most of this but i'm just trying to cover all the bases.
is twrp still asking for the password or were you able to get passed that?
if you have a micro sd card, you could place a ROM/gapps on it, flash this latest twrp recovery from odin or recovery, perform a full wipe (cache, dalvik, data, system) and flash the ROM/gapps. see if that remedies your situation.
if you dont have a micro sd card, and it appears you've wiped the system so there's no OS, you may have to odin back to rooted stock and start over. keep me posted
Still no luck. i flashed twrp2.5 through recovery and after rebooting back to recovery it still asked for a password so I hit cancel at which point it lets me continue and after full wipe as you described above and a fresh flash of stable rootbox 3.9.1 (md5 matched) im still in the same situation. also factory wipe says failed still
I think at this point if it were me, I would Odin flash back to stock then start from scratch. Pain in the butt I know, and no guarantee, but usually flash back to stock is a safe bet.
Another option is to grab the Odin flashable cwm tar in the "root from recovery" method in the general section. Flash the tar, boot into recovery and flash the 6.0.3.1 zip in post #2 of my signature link. Reboot recovery and try wiping/flashing again.
Since you're not entering the password in TWRP, I think that's why you're not getting successful wipes and flashes.
now I used the power+home+vol down button combo to see if bootloader would start. it gave me a choice to download a custom rom or cancel so I canceled and the phone rebooted and i was blessed with the beautifull rootbox animation. my rootbox 3.9.1 nandroid booted and seems to be running fine. Now Im afraid to reboot in fear it will start the whole process over again. any suggestions? or should I just leave it powered on for the rest of its life lol
edit: well I got up the guff to reboot and everything came back fine again WTH. this is so weird, I wish I had a clue what happened. anyways I just wanted to thank you guys one more time for you help. hopefully we wont have to come back to this thread. Peace ;-]
Man that is strange. If that ever happens again it would be interesting to see the log if you can get it. I wonder if there were issues mounting a partition and/or your SD card. If TWRP and CWM were both having an error and the files were on your SD card that would probably be the only thing in common that could cause something like this. Some Transformers seemed to have the password issue, but doesn't seem related to your experience. Glad you got it sorted.
I have a Verizon GNex, Toro. I was running PA 3.60 4.2.2 and all was fine, but I go the bug for 4.3
I flashed FTL 4.3 rom for toro, had it booted up the first time, and was loading apps and setting up my phone, when it froze after about 15 minutes and I had to pull battery.
I tired to reboot but it got stuck on Google logo for 10-15 each time, nothing would happen, so I wiped and tried to restore my old backups, all of them failed, i try to restore everything but data and is it says successful in TWRP (v2.5.0.0) but when I go to reboot system it hangs again on the Google logo for long periods of time, I've waited upwards of 15 minutes.
I still have the PA 3.60 files in my downloads so I tried to wipe and flash it back on my phone, again it hangs at the Goggle logo and wont go past it.
I can get to the bootloader, I can get to TWRP, but nothing else.
Any advice on what I should try next?
Do I need to flash a stock image? I'm at work at the moment so I will have to wait till later to do it, but at home I have a Mac, which makes things that much more confusing for me.
mhport2 said:
I have a Verizon GNex, Toro. I was running PA 3.60 4.2.2 and all was fine, but I go the bug for 4.3
I flashed FTL 4.3 rom for toro, had it booted up the first time, and was loading apps and setting up my phone, when it froze after about 15 minutes and I had to pull battery.
I tired to reboot but it got stuck on Google logo for 10-15 each time, nothing would happen, so I wiped and tried to restore my old backups, all of them failed, i try to restore everything but data and is it says successful in TWRP (v2.5.0.0) but when I go to reboot system it hangs again on the Google logo for long periods of time, I've waited upwards of 15 minutes.
I still have the PA 3.60 files in my downloads so I tried to wipe and flash it back on my phone, again it hangs at the Goggle logo and wont go past it.
I can get to the bootloader, I can get to TWRP, but nothing else.
Any advice on what I should try next?
Do I need to flash a stock image? I'm at work at the moment so I will have to wait till later to do it, but at home I have a Mac, which makes things that much more confusing for me.
Click to expand...
Click to collapse
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
I'm beginning to suspect that people are either getting bad downloads or the data cables being used are not working properly which is causing bad flashes. This is just speculation, but I am using the data cable supplied with my phone and have yet to have one single problem flashing the 4.3 ROM.
jaizero said:
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
Click to expand...
Click to collapse
No, I did not flash a new bootloader, I followed the FTL steps he posted except for wiping cache and davilk cache.
Instructions:
1) Download ROM:
Dev-Host: http://d-h.st/s7b
2) Download Gapps:
Dev-Host: http://d-h.st/UDe
Source: http://forum.xda-developers.com/show...38&postcount=1
*** Goo.im Gapps for 4.2.2 did not work. Use other Gapps at your own risk! ***
3) Download SuperSU:
Dev-Host: http://d-h.st/h3h
4) Backup Device
5) Flash the zips in order
Click to expand...
Click to collapse
jaizero said:
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
I'm beginning to suspect that people are either getting bad downloads or the data cables being used are not working properly which is causing bad flashes. This is just speculation, but I am using the data cable supplied with my phone and have yet to have one single problem flashing the 4.3 ROM.
Click to expand...
Click to collapse
I downloaded the files directly from chrome on the phone. Is that a problem? That is how I have done most of the ROM's I have ever downloaded.
Try this..
Boot into recovery
Factory reset
Wipe dalvik/cache
Install ROM
Install Gapps
Install SU zip
Reboot
The first boot can take a few minutes so be patient. You'll sit at the "Google" screen for a minute or two then the "android" boot animation for 2-5 minutes. I also wouldn't recommend restoring any backups as I ran into some issues doing this. If you can get the ROM to boot do a fresh install of all your apps from the Play Store.
I never flashed the bootloader and I have had zero problems with flashing and booting 4.3. I dont know what people are doing to have issues. One thing I can think of is after flashing everything and you select restart device, it gives you this option that doesnt usually show up. I cant think of the wording. Something about "erasing flash something or other". there is a whole list of "No" and one line of "erase....". Are people clicking the option to erase and get problems from it? I always just select to go back and it restarts.
jsgraphicart said:
I never flashed the bootloader and I have had zero problems with flashing and booting 4.3. I dont know what people are doing to have issues. One thing I can think of is after flashing everything and you select restart device, it gives you this option that doesnt usually show up. I cant think of the wording. Something about "erasing flash something or other". there is a whole list of "No" and one line of "erase....". Are people clicking the option to erase and get problems from it? I always just select to go back and it restarts.
Click to expand...
Click to collapse
The OP is using TWRP which is what I used and I got no such options.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
mhport2 said:
I downloaded the files directly from chrome on the phone. Is that a problem? That is how I have done most of the ROM's I have ever downloaded.
Click to expand...
Click to collapse
It could be, I can't speculate on that as I have only downloaded the files to my PC.
jaizero said:
The OP is using TWRP which is what I used and I got no such options.
Click to expand...
Click to collapse
Oh. I never use TWRP. I have never liked it. I dont know how TWRP handles stuff then.
jaizero said:
Try this..
Boot into recovery
Factory reset
Wipe dalvik/cache
Install ROM
Install Gapps
Install SU zip
Reboot
The first boot can take a few minutes so be patient. You'll sit at the "Google" screen for a minute or two then the "android" boot animation for 2-5 minutes. I also wouldn't recommend restoring any backups as I ran into some issues doing this. If you can get the ROM to boot do a fresh install of all your apps from the Play Store.
Click to expand...
Click to collapse
I have tried this a few times now, it just hang at the Google Logo, I have waited 15 minutes now, that shouldn't be right.
mhport2 said:
I have tried this a few times now, it just hang at the Google Logo, I have waited 15 minutes now, that shouldn't be right.
Click to expand...
Click to collapse
My next suggestion is going to be a /system wipe. Not sure If you want to go this route but if you choose to (at your own risk)..
Boot into recovery
Factory reset
wipe dalvik/cache
wipe /system
install ROM
install Gapps
install SU zip
reboot
As a warning if this doesn't work you will not have a booting system. You will be forced to reinstall an older factory image via fastboot.
Do you have a 4.2.2. ROM saved on your SD card that you can install? It might be a good idea to get a booting system first before trying anything else from this point on.
Still nothing works, I formatted all data and do not have an OS at this point.
When I get home I will adb sideload a 4.2.2 rom and gapps (Most likely Mmuzzy for the time being) from my mac and install it in TWRP. I've done this before and it should work and get me out of this mess.
Thanks for your help.
mhport2 said:
Still nothing works, I formatted all data and do not have an OS at this point.
When I get home I will adb sideload a 4.2.2 rom and gapps (Most likely Mmuzzy for the time being) from my mac and install it in TWRP. I've done this before and it should work and get me out of this mess.
Thanks for your help.
Click to expand...
Click to collapse
did it work? i am also having this problem but when i go into my bootloader it tells me my device is tuna even though its a toro if that matters. and to make things wierder when i try to adb it says i dont have fastboot even though i had it less than 3 hrs ago when i was flashing the rom.(supernova) it worked then i shut off and rebooted the next morning and i just get stuck at the google logo. if anyone can help me i would appriciate it.