okay, here's my issue. I was running Illusion v.2.5 and I created a backup with TWRP because I wanted to try out Touch Wiz rom because ASOP doesn't have the multi-window function. So, I flashed JellyBomb and when I was about to reboot, I said no OS installed. I then restored the backup I recently created and it worked. I then downloaded Synergy and flashed it and got the same error "no OS installed". I did another restore back to Illusion rom and now I'm getting the "no OS installed", wtf?!?! I need some help plz.
shunmyles said:
okay, here's my issue. I was running Illusion v.2.5 and I created a backup with TWRP because I wanted to try out Touch Wiz rom because ASOP doesn't have the multi-window function. So, I flashed JellyBomb and when I was about to reboot, I said no OS installed. I then restored the backup I recently created and it worked. I then downloaded Synergy and flashed it and got the same error "no OS installed". I did another restore back to Illusion rom and now I'm getting the "no OS installed", wtf?!?! I need some help plz.
Click to expand...
Click to collapse
Okay, I did the restore again and it worked this time. But why is it saying no OS installed when I tried to flash Jellybomb and Synergy? I really want to go back to a touch wiz based rom so I can use the multi-window function; which is the main reason I bought the note 2 last yr.
really? you're posting this ... stuff in the Dev section?
wrong section, read the sticky/rules, or be more careful.
brace for flaming in 3... 2...
OP your first issue is not reading the Forum Rules on posting....
Thread Closed.
Related
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Wipe
Data
Cache
Delvik Cache
and Factory Reset.
Make sure you're flashing the correct GApps for android 4.2.x
Flashing a kernel has nothing to do with a status 7 error.
A status 7 error points to a outdated recovery or bootloader.
You should get ANY errors.
If you hate flashing why do it??
I honestly don't get that...
If you're here to make your phone to look "cool" you're in the wrong place.
Galaxy S3 / AoCP / V4A / Turbocharged
duoblade said:
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Click to expand...
Click to collapse
I would get TWRP recovery.. wipe dalvik / factory reset. and re-flash your rom.. I'm on Rogers as well and the status 7 error means that your recovery / bootloader is outdated.
So start by getting the most recent TWRP. I got it from goo.
btw: if you don't like custom rom, i suggest going to the sammobile site and getting your factory firmware. Use Odin to reflash back to stock. That should solve your hiatus towards custom roms...
correction
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
duoblade said:
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
Click to expand...
Click to collapse
sure but its fine custom Roms can be a Pain in the A$$ thats why am running stock rooted stable, great battery life, fast like custom roms, everything is perfect give a try with stock rooted no issues or problems like custom roms
Synergy Rom 4.1.2 w/ Ziggy Kernel using ATT Galaxy S3
HAPPY ROOTIN :cyclops:
I recently rooted my AT&T Samsung Galaxy S3 running Android 4.3 using odin. I loved the features, I flashed the ROM CyanogenMod and had that working just fine. Until just recently I made the mistake of installing a new ROM. I used ROM manager and decided to go with stratatak7 . Now after doing this, my phone has been downgraded from 4.3 to 4.1.1 and is not running properly and crashes. So I went back into ROM manager and tried to get CyanogenMod back, but am unable too, every time I try to install I get an error. I am looking for ANY way to fix this. I mainly want to get my phone back to COMPLETE factory settings and Android 4.3. Im currently running Build Number Intergalactic 2.5.
PLEASE HELP!!!
EraOfDiscovery said:
I recently rooted my AT&T Samsung Galaxy S3 running Android 4.3 using odin. I loved the features, I flashed the ROM CyanogenMod and had that working just fine. Until just recently I made the mistake of installing a new ROM. I used ROM manager and decided to go with stratatak7 . Now after doing this, my phone has been downgraded from 4.3 to 4.1.1 and is not running properly and crashes. So I went back into ROM manager and tried to get CyanogenMod back, but am unable too, every time I try to install I get an error. I am looking for ANY way to fix this. I mainly want to get my phone back to COMPLETE factory settings and Android 4.3. Im currently running Build Number Intergalactic 2.5.
PLEASE HELP!!!
Click to expand...
Click to collapse
Step #1 - Dont use ROM manger to install roms.
Step #2 - Flash back to stock and start over. If you need help with this there are stickies all over the general and q&a sub forums.
dntesinfrno said:
Step #1 - Dont use ROM manger to install roms.
Step #2 - Flash back to stock and start over. If you need help with this there are stickies all over the general and q&a sub forums.
Click to expand...
Click to collapse
Thanks for the reply, but now a new problem has happened, now when I boot up it gets stuck at the Samsung Galaxy SIII boot logo... any suggestions?
EraOfDiscovery said:
Thanks for the reply, but now a new problem has happened, now when I boot up it gets stuck at the Samsung Galaxy SIII boot logo... any suggestions?
Click to expand...
Click to collapse
All by itself? Or did you manage to flash back to stock? If so the fix is to boot into recovery and factory reset. Also note it will take a little longer to boot after a stock flash (or wiping the cache) as the cache needs to be rebuilt.
Since I just created an account here, I cannot post this as a reply on its rightful thread, but hopefully someone will see my question here.
I have used many different ROMS, and I had just installed GOOGLE EDITION 4.4.2 BY Danvdh, Kryten2k35 & Ktoonsez (http://forum.xda-developers.com/showthread.php?t=2539361) after installing this ROM, I quickly realized my phone showed I had no service, even in areas where I know I did.
I then tried to install the Wicked v10 ROM, as I have heard many good things about it. However, After running the Aroma installer, I was unable to boot into the Wicked ROM. My S$ just kept booting into the Googe Edition Rom.
tl;dr: After running the Aroma installer succsesfully, my S4 boots into my old ROM ( GOOGLE EDITION 4.4.2 BY Danvdh) and does not boot in into the Wicked v10 ROM.
Did you performed a FULL wipe?
☞ Sent from here ☜
baseballfanz said:
Did you performed a FULL wipe?
☞ Sent from here ☜
Click to expand...
Click to collapse
Not the internal sd, but I usually never have to, also the Aroma installer has a wipe function.
spmiller said:
Since I just created an account here, I cannot post this as a reply on its rightful thread, but hopefully someone will see my question here.
I have used many different ROMS, and I had just installed GOOGLE EDITION 4.4.2 BY Danvdh, Kryten2k35 & Ktoonsez (http://forum.xda-developers.com/showthread.php?t=2539361) after installing this ROM, I quickly realized my phone showed I had no service, even in areas where I know I did.
I then tried to install the Wicked v10 ROM, as I have heard many good things about it. However, After running the Aroma installer, I was unable to boot into the Wicked ROM. My S$ just kept booting into the Googe Edition Rom.
tl;dr: After running the Aroma installer succsesfully, my S4 boots into my old ROM ( GOOGLE EDITION 4.4.2 BY Danvdh) and does not boot in into the Wicked v10 ROM.
Click to expand...
Click to collapse
What recovery are you using? Is it the most recent version of that recovery?
Skipjacks said:
What recovery are you using? Is it the most recent version of that recovery?
Click to expand...
Click to collapse
CWM Touch Req0very v1.0.3.3
I have no clue if its the most recent
spmiller said:
CWM Touch Req0very v1.0.3.3
I have no clue if its the most recent
Click to expand...
Click to collapse
I've had lots of issues with TWRP recovery, I would get bootloops with the 4.4 roms and typically the only solution was to downgrade to one of my old backups. I've switched to CWM with no issues but don't use the touch version, you may want to install the non touch recovery just to eliminate that as a potential cause of the problem. Regardless make sure you're on the most current recovery rev.
spmiller said:
Since I just created an account here, I cannot post this as a reply on its rightful thread, but hopefully someone will see my question here.
I have used many different ROMS, and I had just installed GOOGLE EDITION 4.4.2 BY Danvdh, Kryten2k35 & Ktoonsez (http://forum.xda-developers.com/showthread.php?t=2539361) after installing this ROM, I quickly realized my phone showed I had no service, even in areas where I know I did.
I then tried to install the Wicked v10 ROM, as I have heard many good things about it. However, After running the Aroma installer, I was unable to boot into the Wicked ROM. My S$ just kept booting into the Googe Edition Rom.
tl;dr: After running the Aroma installer succsesfully, my S4 boots into my old ROM ( GOOGLE EDITION 4.4.2 BY Danvdh) and does not boot in into the Wicked v10 ROM.
Click to expand...
Click to collapse
Are you certain you are flashing Wicked? Maybe you selected the wrong Rom to flash. I asked that for two reasons. 1) If you flash Rom A, it cannot boot to Rom B. 2) I don't remember the Wicked v10 aroma having any wipe features. I could be wrong on number 2 because it's been a while since I ran Wicked.
Tapatalk Pro 4 - GS4(M919)
?dbombRom is dbestRom?
phrotac said:
Are you certain you are flashing Wicked? Maybe you selected the wrong Rom to flash. I asked that for two reasons. 1) If you flash Rom A, it cannot boot to Rom B. 2) I don't remember the Wicked v10 aroma having any wipe features. I could be wrong on number 2 because it's been a while since I ran Wicked.
Tapatalk Pro 4 - GS4(M919)
?dbombRom is dbestRom?
Click to expand...
Click to collapse
No I'm flashing Wicked
Sent from my SGH-M919 using Tapatalk
spmiller said:
Since I just created an account here, I cannot post this as a reply on its rightful thread, but hopefully someone will see my question here.
I have used many different ROMS, and I had just installed GOOGLE EDITION 4.4.2 BY Danvdh, Kryten2k35 & Ktoonsez (http://forum.xda-developers.com/showthread.php?t=2539361) after installing this ROM, I quickly realized my phone showed I had no service, even in areas where I know I did.
I then tried to install the Wicked v10 ROM, as I have heard many good things about it. However, After running the Aroma installer, I was unable to boot into the Wicked ROM. My S$ just kept booting into the Googe Edition Rom.
tl;dr: After running the Aroma installer succsesfully, my S4 boots into my old ROM ( GOOGLE EDITION 4.4.2 BY Danvdh) and does not boot in into the Wicked v10 ROM.
Click to expand...
Click to collapse
No service? You flashed the modem through odin before flashing a custom rom through recovery right?
Did you by any chance flash a dual boot patcher? If you went through aroma successfully when you flashed wicked and booted into Aosp when done, it sounds like dual boot. From what I understand you have to have a TW ROM as the primary ROM or you may have issues. There's a ROM switcher app here http://forum.xda-developers.com/showthread.php?t=2447534 this is just a suggestion. I'm not assuming you actually installed dual boot but it's worth the try. Good luck!!
Sent from my SGH-M919 using xda app-developers app
mrzhadow said:
Did you by any chance flash a dual boot patcher? If you went through aroma successfully when you flashed wicked and booted into Aosp when done, it sounds like dual boot. From what I understand you have to have a TW ROM as the primary ROM or you may have issues. There's a ROM switcher app here http://forum.xda-developers.com/showthread.php?t=2447534 this is just a suggestion. I'm not assuming you actually installed dual boot but it's worth the try. Good luck!!
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I have installed the Liquidsmooth ROM instead of Wicked and I like it a lot, so I don't think I'll make an attempt to switch.
Sent from my SGH-M919 using Tapatalk
Hey guys, i just upgraded from our t989 to a moto x and i decided to start testing roms out on the t989 since its not my main phone anymore, i only flashed about two roms and i have already done something wrong, flashed Aokp Milestone first, nothing wrong here enjoyed aokp back in 4.2.2 days. now i have always wanted to use Jedi mind trick but i was worried about the problems with it, so i made a backup of Aokp and Wiped data/wiped cache and flashed darkside wipe then flashed Jedi mind trick and rebooted. it got stuck at the splash screen like the details in the rom said but now when i try to make a backup, wipe data, cache, flash Jedi mind trick, flash darkside wipe it will freeze, i have tried flashing Cyanogenmod 10.2 and still freezes, i decided to just restore to stock but Odin 1.8.5 will not find my Device when it goes into download mode. right now i am trying my aokp Backup it had been going Fine for awhile but it looks like it might have Froze on /storage/sdcard0: mounted. any help please? i dont think i could google this problem.
Edit: now when i boot into cwm it says Can"T open /cache/recovery/last_log twice.
plugged it into a different computer and got odin working, could anyone show me the correct way to install Jedi mind trick? also it comes with that kernel so it can be overclocked to 2ghz right?
Trozzul said:
plugged it into a different computer and got odin working, could anyone show me the correct way to install Jedi mind trick? also it comes with that kernel so it can be overclocked to 2ghz right?
Click to expand...
Click to collapse
Not sure about specific jedi issues, its been inactive a long time.
But for any 4.1.2 touchwiz roms ...personally I flash twrp 2.5.0.0. 2.6.0.0 is probably OK, but any higher can cause issues with 4.1.2.
Also, you should use the infamous wipes. Darkside is outdated. I believe infamous wipes are based on dark side, but they've been updated for jelly bean. Darkside wipes stopped being updated at ICS.
See how that works.
Oh, and for more current 4.1.2 ROMs, @Rushing has a few.
I have a T989, not a T989D, running TWRP 2.7.1.0 and UVMC6 radio, coming from a JB 4.1.2 Slimrom.
Also I have taken out the board and inspected the power button, and everything seems okay there. I don't think it's being caused by a faulty button or some other hardware problem because I can flash my old Slimrom, and that boots up just fine.
I wanted to give Paranoid Android a whirl with the latest Wild kernel, and though I've tried 8 different PA builds, a PACman, a Slimkat, and an Alpine rom, ALL KitKat roms so far are bootlooping. [EDIT: Even PA 3.99 JB 4.3 is doing it. So it's more than just KitKat even.]
I'm doing the following:
Wipe system, data, cache, dalvik, and perhaps android secure and preload as well
Flash ROM & Gapps
Wipe cache & dalvik
Reboot
I reach the splash, and maybe it even finishes booting. But invariably, it takes about 60-90s from initialization before the screen dims, everything freezes for 2-5s, and it reboots.
I'm out of ideas.
Why won't my phone work with KitKat?
Thanks in advance
Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin.
Edit: If your phone came with 4.1.2 jellybean, you already have the newest drivers.
meekrawb said:
Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin.
Edit: If your phone came with 4.1.2 jellybean, you already have the newest drivers.
Click to expand...
Click to collapse
I read something to that effect. Haven't seen a .tar file for it, only .zip.
jaybird16 said:
I read something to that effect. Haven't seen a .tar file for it, only .zip.
Click to expand...
Click to collapse
If you sign up for an account on sammobile.com you can download from there. Just type "t989" in the search box.
meekrawb said:
If you sign up for an account on sammobile.com you can download from there. Just type "t989" in the search box.
Click to expand...
Click to collapse
Okay, I did that. Flashed the latest Paranoid Android 4.45. No dice. Same story.
jaybird16 said:
Okay, I did that. Flashed the latest Paranoid Android 4.5. No dice. Same story.
Click to expand...
Click to collapse
That was the only thing I could think of. Maybe someone else has some ideas.
I had the same problem. Turned out it had to do with the recovery. I redownloaded twrp, used flashify to install it. And that fixed the problem.
meekrawb said:
That was the only thing I could think of. Maybe someone else has some ideas.
Click to expand...
Click to collapse
Much appreciated. My phone shipped at the tail end of Gingerbread. So now I have whatever drivers from 4.1.2, and that's one more potential problem eliminated.
The stock rom ran just fine, btw, once I factory reset (the documentation was nil, but at 750mb, I knew it was more than just UVMC6 radio firmware...)
So 4.1.x seems to be okay, but not 4.3.x or 4.4.x. Next I'll have to try a flavor of 4.2.x and see how it feels about that.
Lokke9191 said:
I had the same problem. Turned out it had to do with the recovery. I redownloaded twrp, used flashify to install it. And that fixed the problem.
Click to expand...
Click to collapse
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.45. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
jaybird16 said:
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.5. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
Click to expand...
Click to collapse
Never. Ever. Rule out leprechauns!
Lokke9191 said:
Never. Ever. Rule out leprechauns!
Click to expand...
Click to collapse
LOL, good point.
w00t! TWRP 2.1.8 for the Hercules just dropped!
I was thinking maybe the MD5 wouldn't have checked out the first time you downloaded, but would have the second time. I don't usually bother unless I have a reason to think that's a problem. I can always look after the fact.
Downloaded 2.1.8 and MD5 checks out...now to flash it...
jaybird16 said:
LOL, good point.
w00t! TWRP 2.1.8 for the Hercules just dropped!
I was thinking maybe the MD5 wouldn't have checked out the first time you downloaded, but would have the second time. I don't usually bother unless I have a reason to think that's a problem. I can always look after the fact.
Downloaded 2.1.8 and MD5 checks out...now to flash it...
Click to expand...
Click to collapse
Nice. Lemme know how it works out. Oh. The new PA is awesome.
My bad. I saw the number "8" at the bottom of the page which had not been there earlier and assumed it was next after after "7". No, that's an ancient recovery from 2012.
TWRP 2.8.1 for the Hercules has NOT just dropped!
Okay, so, my first test with a newly downloaded, MD5 checked, and flashed TWRP 2.7.1 recovery, and an MD5 checked PA 4.45 has not produced any different result.
However, you've made me realize that I can't hope to troubleshoot this without being fastidious about MD5 from here on out, so, thx 4 that.
...same goes for a 2nd test with an MD5 checked PA 4.5 Alpha3...
...same goes for a 3rd test with an MD5 checked PA v3.69 (4.2)...
...But Slim-Star v4.12 (4.2) loads no problem...go figure...
Fix permissions?
I tried to install the PA 4.5 Beta, and same problem. It bootloops.
Could it have anything to do with permissions?
jaybird16 said:
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.45. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
Click to expand...
Click to collapse
when i had an issue like this i re-installed the factory original rom and started from the very beginning. if you've tried that and it doesn't work, well i'm pretty much unhelpful here. :crying:
Also note that WildKernel has a special version of v9 out for recent roms (roms released within the last two months).
Any other version of wildkernel will lead to bootloops in my experience.
If your rom is older than two months, then v8 or v9 should do fine
ayr0 said:
Also note that WildKernel has a special version of v9 out for recent roms (roms released within the last two months).
Any other version of wildkernel will lead to bootloops in my experience.
If your rom is older than two months, then v8 or v9 should do fine
Click to expand...
Click to collapse
There were problems reported of even the latest version of Wild! not working with Paranoid.
jrc2
Sent from my T-Mobile S2 using Tapatalk.
I'm having the same issues, but no one knows what's up. I've tried so many ROM's and only the older ones work.
http://forum.xda-developers.com/showpost.php?p=55050951&postcount=9
This is my post with the logs I got from the constant crash on cm11. I tried pa and had the same result.
Issue solved
After sharing some logs with Sultanxda, he pointed out this bootloop issue due to the CM kernel and helped me get it fixed.
My problem was that my phone would not boot on MOST JellyBean ROM's or ANY KitKat ROM. It would crash/kernel panic on or before the set up screen.
I do not know if the latest KitKat ROM's have the issue patched, but I asked if he could upload the patch for the kernel to source for other ROM's to use.
This thread should be solved I guess.