Device info: Samsung galaxy s plus (I9001)
I tried to install the custom ROM DOOMNEXUS V2 20121012, before i did this i rooted my device (checked it with the rootchecker to make sure it had worked), installed CWM v5.5.0.4, wiped the cache and data/factory reset.
After i rebooted my device after i had done the above, my device would straight into recovery mode.
I tried installing the custom rom with team power 2.2.1 recovery but with the same result. Each time the device booted straight into recovery mode and i had to use odin to reinstall my stock firmware.
I also tried using other custom roms for jelly beans like cm 10 alpha, but also with the smae result as stated above.
I have no idea what i did wrong or how i can fix it, so that it boots into jelly beans
Do any of you guys know how to fix it?
Plz help
I'm also having the same issue with same device.. Please help us get out of this...
I have had same problem with... was it CM9 alpha2? Anyway, then there was a flashable zip and that fixed the problem
I have always also formatted dalvic cache.
Anyway, new Doomnexus is out: http://forum.xda-developers.com/showthread.php?t=1936749
Mine DoomNexus V3 works awesome well, i have the kernel 3.0-version. I am using CWM 6.0.1.4 recovery http://forum.xda-developers.com/showthread.php?t=1843825
You had a bootloop.
Read here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001 under point 3.5.
I was flashing air kernel with cwm and succeded, but when i rebooted afrer flashing, the phone won't get to Google logo. I flashed Blue color + 65 fps HELP PLEASE
Nexus S, stock jelly bean 4.1.2, rooted, tried to flash air kernel..
Please someone reply. After the Google logo, the phone just goes blank... tried a battery pull and nothing..
matejilic said:
I was flashing air kernel with cwm and succeded, but when i rebooted afrer flashing, the phone won't get to Google logo. I flashed Blue color + 65 fps HELP PLEASE
Nexus S, stock jelly bean 4.1.2, rooted, tried to flash air kernel..
Please someone reply. After the Google logo, the phone just goes blank... tried a battery pull and nothing..
Click to expand...
Click to collapse
can u still go into recovery ??
power + volume up
ahmadalraii said:
can u still go into recovery ??
power + volume up
Click to expand...
Click to collapse
yes, i can. I tried to flash Matr1x kernel, reflash Air and flash AOKP milestone 1, situation is the same, it shows only the google logo, after that i can see nothing, blank screen..
did u try a whole new combo..
try hellybean rom 4.2 with airkernel..
not all roms works with all kernels some roms have thier own kernels like cm
is your problem that u want this specific rom to boot and u have tried many kernels and stuck in bootloops
or ur phone is not working with any rom ? and any kernel >?
be carefull if flashed a jelly bean rom to flash a jellybean kernel ..or hust try to boot with the provided kernel with the zip rom
Wipe data in CWM. Make a backup first.
Factory reset and wipe data,cache before trying it again.
Sent from my Nexus S
ahmadalraii said:
did u try a whole new combo..
try hellybean rom 4.2 with airkernel..
not all roms works with all kernels some roms have thier own kernels like cm
is your problem that u want this specific rom to boot and u have tried many kernels and stuck in bootloops
or ur phone is not working with any rom ? and any kernel >?
be carefull if flashed a jelly bean rom to flash a jellybean kernel ..or hust try to boot with the provided kernel with the zip rom
Click to expand...
Click to collapse
my phone worked with stock. Then i tried to flash air kernel to stock rom to increase performance, but i got stock in bootloop i guess (wont go past the google logo..)
seibott said:
Factory reset and wipe data,cache before trying it again.
Sent from my Nexus S
Click to expand...
Click to collapse
tried multiple cache wipes/ dalvik cache wipes and factory resets.. i guess i'll try to flash stock image from google in hope to fix it...
i managed to flash cm 10 on my nexus s and it fixed all the problems. thank you for your help guys, cheers!
matejilic said:
i managed to flash cm 10 on my nexus s and it fixed all the problems. thank you for your help guys, cheers!
Click to expand...
Click to collapse
cheers ...:laugh:
I am trying to update my Radio/modem file with the JB Android 4.3 Radio file. It requires that I install CWM 6.0.3.7. Can I install this alongside my TWRP 2.6.3.0 installation or as I have read, it will overwrite my TWRP recovery mode? If it will overwrite, how do I switch between? Just reflash through ODIN using PDA? That seems like a lot of work and the possibilities of breaking might be high just overwriting Customer Recoveries?
If I would install this JB Radio for Android 4.3, how would I go back to GB? I can't find a single GB Radio/Modem. Could I use Radio files for GB instead of wiping and installing stock GB ROM [No Root, No Custom Recovery, but it includes the GB Radio/modem]. The reason I am worried about this, if I need to load my original stock GB 2.3.6 backup with root from my nandroid, I would need the original GB Radio and the nandroid backup/restore feature doesn't include that. All advice is greatly appreciated.
The Radio Does Not Get Backed Up By Cwm/twrp Backup(nandroid) Method.
Click to expand...
Click to collapse
[RADIO][UCMC1] For I727/I727R [09-APR-2013]
http://forum.xda-developers.com/showthread.php?t=2228292
[Q] I have CWM and TWRP installed, is that OK?
http://forum.xda-developers.com/showthread.php?t=2122152
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012] [It has ICS radio files, but no GB files]
http://forum.xda-developers.com/showthread.php?t=1754473
Just flash it with twrp. It'll work just like if you did it with cwm.
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Pick a recovery and use it. Backups are not cross compatible. If you make a backup with cwm it won't work with twrp.
You can flash radios with either. Just pick one.
Sent from my HTC One using Tapatalk 4
lowao said:
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Click to expand...
Click to collapse
If you have not already installed a 4.3 ROM, then you are recommended (nay, required) to use CWM 6.0.3.7 to do the initial wipe and install, after that you can switch to TWRP for any flashing after that.There is something that 6.0.3.7 does to the data partition that TWRP doesn't, on the initial setup. Once that is done, it doesn't matter. Flash the JB radio when you flash the 4.3 ROM. And going back to GB if you need to is fairly simple, just follow Vincom's guide. There are lots of flashable zips of GB radios you can use.
I am still a bit confused regarding TWRP & CWM being installed at the same time or side by side. So, let me get this straight. If I want to install JB 4.3 ROM, I must first boot into ODIN, install CWM through ODIN, reboot, boot into CWM, wipe the system, reboot, boot back into ODIN, install TWRP, reboot, boot into TWRP, install the JB 4.3 ROM, and finally preform the last reboot. Is this correct & it won't break either of the custom recoveries? However rpr69 said "switch back to TWRP." Are you inferring TWRP & CWM can be installed side by side? If so, how do I access one over the other?
Regarding GB's radio files:
Which of the following links is the Radio/modem files? Is it the second one? I know of them is the official stock ROM and the other requires the OTA updates. However the poster didn't include the OTA updates yet...
ATT-UCLI3-odexed-cwm.zip http://d-h.st/rDZ
kernel-ucli3-sgh-i727-RD01-cwm.zip http://d-h.st/QfR
[ROM][ICS][UCLI3][09-NOV-2012] Stock odexed & deodexed UNTOUCHED
http://forum.xda-developers.com/showthread.php?t=1982467
Try this, wipe cache and dalvik.....no promises lol [Link is dead.]
https://dl.dropbox.com/u/60567424/modem-UCLI3.zip
http://forum.xda-developers.com/showpost.php?p=33344009&postcount=22
Sadly no link for UCLI3 [GB's Radio files.]
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012]
http://forum.xda-developers.com/showthread.php?t=1754473
The 1Stop post from Vincom:
http://forum.xda-developers.com/showthread.php?t=1785999
Sadly there are no more links for GB / UCLI3 radio files.
I know you posted but its confusing, let me simplify, I hope:
im assuming you have either cwm or twrp installed, if on stock read this.
you cannot have two recoveries installed at the sametime:
recovery install procedure:
if not on cwm6037 flash cwm6037 with what ever recovery you have now and reboot back into recovery.
then flash any custom jb4.3 rom, preferably latest cm10.2 nightly found here and reboot rom at least twice.
if you like cwm 6037 stay with it, I don't, or else just flash twrp 2.6.3.0 w/cwm 6037 and reboot back into recovery or rom.
now you can just stay w/the cm10.2 nightly you flashed with cwm 6037 or flash any other rom w/twrp 2.6.3.0 which is now your installed recovery.
that's it you should not have the reboot problems on any jb4.3 roms.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
above recovery install procedure is only if a jb4.3 rom on its 2nd reboot just has a black screen and wont boot into rom, but 2nd boot does usually take longer than normal upto a full minute.
if flashing a rom or restoring from nandroid(recovery backup) prior to jb4.3 and then later decide to flash a jb4.3 rom you need todo above recovery installation procedure b4 flashing a jb4.3 rom.
restoring backups only work with whatever recovery they were made with, you cannot restore a cwm backup w/twrp recovery and vice a versa.
newest versions of recoveries should restore backups made with their older versions.
why do u want an old radio, they will not work w/jb roms
old radios are linked in the 1stop sticky under "old stuff".
installing the radio has nothing todo with the recovery you are using.
flash jb radios for jb roms which happen to be all the current roms.
reread the radio section in the 1stop sticky.
I linked this post in the recovery section of the 1stop sticky
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
lowao said:
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
Click to expand...
Click to collapse
u can return any phone that has any stock firmware, with our phones that would be stock jb4.1.2 and using odin would be the way to do it , link in my sig. this is assuming your carrier used the latest firmware as with att and rogers.
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
these are untouched full official stock firmwares( radio, recovery, kernel and apps/bloatware), just use odin and flash whatever version you want, all info is in the restore to stock sticky
lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
nope, both are fine and are still available officially. You don't need gingerbread to return it.
Sent from my HTC One using Tapatalk 4
I have to go to Samsung's website and download their Kies software to upgrade to Jelly Bean right? It won't be pushed out through Settings > About Phone > System Update then?
Or you can use Odin.
Sent from my HTC One using Tapatalk 4
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
beachmiles said:
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
To properly set everything up, you need to use the recommended CWM for 4.3, do a full factory wipe, and make sure that data is formatted. Then install the ROM and boot it up. Reboot to verify it works properly. Then you can go to TWRP 2.6.0.1 or later.
I've been using twrp since release and not had any issues why do we need cwm? What's the technical reasoning.
Sent from my XT1080 using Tapatalk
Didn't work
I followed this procedure exactly and it still didn't work.
I gave it ten minutes between boots and ended up having to pull the battery each of the three times I rebooted.
Fortunately I've gotten into the habit of making a backup before flashing, so it was just a loss of 45 minutes of my evening.
I was trying to get the latest CM10.2 Stable build. Has anyone gotten this thing to flash and work as well as 10.1.3 RC2 or 10.1.3 Final? This issue started for me with the second 10.2 Nightly.
...
Just NOW began seeing the replies to the main post. I don't have ANOTHER fresh install in me: I've already had to do that twice with the 2012 Nexus7 and once with the Skyrocket in the last six weeks.
today i tried to install the custom rom 'liquid smooth' but my phone got stuck on an old recovery mode. i tried everything a couldn't go back, so i just flashed the stock rom again.
the question is, can someone tell what happened? what did i do wrong?
i am root and i had cwm installed so i just dont' get it.
i just need a stable rom for my phone!!!
First flash CM by dhiru and then flash LS over it.
Sent from my GT-I9003
so straight to the point, i rooted my phone, then i flashed cwm then I accidentally installed a KitKat ROM instead of Jelly bean -_- resulting in the Costum ROM NOT booting up, bad news is my sd card slot does NOT work so i cant go to recovery and install another ROM so im stuck with ODIN. Any idea of what file should I run? ive tried a couple M919UVUAMDL but they fail also MK5. I need to get this fixed as soon as possible!
YoungCNYC said:
so straight to the point, i rooted my phone, then i flashed cwm then I accidentally installed a KitKat ROM instead of Jelly bean -_- resulting in the Costum ROM NOT booting up, bad news is my sd card slot does NOT work so i cant go to recovery and install another ROM so im stuck with ODIN. Any idea of what file should I run? ive tried a couple M919UVUAMDL but they fail also MK5. I need to get this fixed as soon as possible!
Click to expand...
Click to collapse
What phone are you using exactly, we can't help unless we know this as there are numerous devices on T-Mobile