Related
Hi all
Tonight I decided to buy that little usb jig and flash the lite'ning rom v5 for first time.
Okay things started alright..
Downloaded lite'ning rom v5 followed the guide, and flashed it via Odin v1.85.
Phone booted as it should, I noticed that all my apps and messages was still there, oh well (I come from custom x10i roms) I decided to go into recovery and did wipe data/ reset. Thought it would wipe the stuff there.
Then it startet to bootloop when I rebooted it.. Hmm funny, I tried to flash lite'ning v5 again but still bootloop. Then I found a guide how to get back on stock software with odin, I downloaded from here: http://forum.xda-developers.com/showthread.php?t=1113928
The danish vesion + stock kernel flashed both.
Still bootlooped.
Hm The guide mentioned that I could try the villainrom v1.1 I did that and I got into the phone atlast!.
Ok then I tried to flash the stock software again from there boot loop again.. And now im back on villainrom :s seems like every thing I flash exept the villainrom I get bootloops. Even stock software? wtf ?
Could anyone please explain to me how I get the lite'ning rom v5 installed correctly without getting into bootloop.
And I found another guide http://forum.xda-developers.com/showthread.php?t=1108499&highlight=loop
I followed it 100% thats where I got the villainrom from btw.. Seems like its the only way I'm able to use my phone right now :s ?
So please anyone could you give me a hint on what I should do to fix this mess i've made..
Thanks,
Best regards Rasmus Mikkelsen
Denmark
did you try to wipe delvic as well when you did the wipe?
might solve the problem for you
eeebbr said:
did you try to wipe delvic as well when you did the wipe?
might solve the problem for you
Click to expand...
Click to collapse
I only tried it once i think, ill give it a try thanks
How come when I connect it to KIES im not allowed to do a reinstall from there?
I remember PC companion / sony ericsson software update just plug it in and you'd be back on stock software unrooted, isnt this possible on the samsung?
Rasmusvm said:
How come when I connect it to KIES im not allowed to do a reinstall from there?
I remember PC companion / sony ericsson software update just plug it in and you'd be back on stock software unrooted, isnt this possible on the samsung?
Click to expand...
Click to collapse
You have to clear the flash counter with a jig to be able to update using kies again. I did anyway. I had a similar bootloop problem myself. I fixed it by flashing to a stock firmware with odin, making sure to flash something for phone, pda and csc. I figured that maybe something from lightning ROM was left over and causing incompatibilities. This may not be the reason but the solution worked for me.
For lite'ning rom you cannot do wipe userdata (reset) using Clockwork Recovery. It wipes out something that is required to boot the rom. There is something missing from lite'ning rom that cannot use an empty userdata partition.
To be able to exit boot loop, you will have to go to download mode, flash a stock kernel, boot into samsung recovery, then do a factory reset.
It should boot right in. Then go back to download mode, then flash the latest speedmod kernel. Since there is already data in the userdata partition, it will not boot loop unless you use clockwork recovery to wipe userdata (factory reset).
If that doesn't work, then you will have to goto download mode, reflash a stock rom, goto samsung recovery, do a factory reset, boot into the rom, which will then put stuff back into the userdata partition, then go back to download mode, and reflash lite'ning rom.
It is weird, but all stock rom, and stock rom derivatives will get the boot loop issue when you use clockwork recovery to wipe userdata partition. So far, the only rom that does not have this issue with clockwork recovery wipe userdata function is CM7 and Devnull.
The problem in my view is not the rom's problem, but more of the kernel problem. It is missing a script to rebuild empty userdata.
Do this to get rid of a boot loop.
1) Flash a stock ROM via ODIN
2) Go into stock recovery, do factory reset
3) Re-flash stock ROM via ODIN.
pulser_g2 said:
Do this to get rid of a boot loop.
1) Flash a stock ROM via ODIN
2) Go into stock recovery, do factory reset
3) Re-flash stock ROM via ODIN.
Click to expand...
Click to collapse
This! Helped me Thanks!
And thanks Life1688 aswell
It appears everything is back to normal now.
Simply flash stock rom, factory reset it in stock recovery, and reflash stock rom
Best Solution to run Lite'ning Rom 5
Rasmusvm said:
Hi all
Tonight I decided to buy that little usb jig and flash the lite'ning rom v5 for first time.
Okay things started alright..
Downloaded lite'ning rom v5 followed the guide, and flashed it via Odin v1.85.
Phone booted as it should, I noticed that all my apps and messages was still there, oh well (I come from custom x10i roms) I decided to go into recovery and did wipe data/ reset. Thought it would wipe the stuff there.
Then it startet to bootloop when I rebooted it.. Hmm funny, I tried to flash lite'ning v5 again but still bootloop. Then I found a guide how to get back on stock software with odin, I downloaded from here: http://forum.xda-developers.com/showthread.php?t=1113928
The danish vesion + stock kernel flashed both.
Still bootlooped.
Hm The guide mentioned that I could try the villainrom v1.1 I did that and I got into the phone atlast!.
Ok then I tried to flash the stock software again from there boot loop again.. And now im back on villainrom :s seems like every thing I flash exept the villainrom I get bootloops. Even stock software? wtf ?
Could anyone please explain to me how I get the lite'ning rom v5 installed correctly without getting into bootloop.
And I found another guide http://forum.xda-developers.com/showthread.php?t=1108499&highlight=loop
I followed it 100% thats where I got the villainrom from btw.. Seems like its the only way I'm able to use my phone right now :s ?
So please anyone could you give me a hint on what I should do to fix this mess i've made..
Thanks,
Best regards Rasmus Mikkelsen
Denmark
Click to expand...
Click to collapse
Follow 3 simple steps to get Lite'ning Rom 5 working as its supposed to:
1 - Download and Flash Lite'ning Rom 5 via odin as normal.
2 - Download and Flash the Ninphetamine-2.0.5 Kernel from the link bellow:
http://forum.xda-developers.com/showthread.php?t=1179814
If you download the TAR file, you need to flash it via ODIN, or if you download the ZIP file, you need to flash it via RECOVERY.
3 - Go into recovery and do a full wipe and restart the phone.
Start enjoying Lite'ning Rom 5 without any bootloops what so ever.
Its a real pitty Lite'ning Rom Dev didnt even bother mentioning this on his main page, knowing that this bootloop issue comes with his rom.
kwazyivan - Thanks
I just did what you said. Seems to run smooth
I wonder if its possible to remove the social hub and gamehub and that samsung stuff? I never use it anyways.
Also I have another question, I come from the x10i custom roms. How come the FPS cap isnt removed in the custom kernels? Not that it matters Phone is fast as hell anyways, just wondering
I hope this explains it
Rasmusvm said:
kwazyivan - Thanks
I just did what you said. Seems to run smooth
I wonder if its possible to remove the social hub and gamehub and that samsung stuff? I never use it anyways.
Also I have another question, I come from the x10i custom roms. How come the FPS cap isnt removed in the custom kernels? Not that it matters Phone is fast as hell anyways, just wondering
Click to expand...
Click to collapse
The hubs in the system, doesnt cause any slowdowns or extra ram usage from my experience but if you want to remove them you can always download Titanium Backup from the Market, once you start the TB app go to Backup/Restore, from the list of installed apps, tap on any program and choose the Uninstall option that you wish to remove permanently.
The screen has a refresh rate of 60, so even if the cap is removed it would be completely pointless as the framerate would still be 60 for any graphics app such as games and benchmarks, again in my opinion 60fps is all we need to see smooth rendering graphics, anything more than that is just to satisfy our own greed and hunger for power.
Thanks alot man, explains my questions !
Much appreciated
Rasmusvm said:
Thanks alot man, explains my questions !
Much appreciated
Click to expand...
Click to collapse
Sure mate, No problem
Hey guys,
So i have my S2 for like 6 months now and never had any issue with flashing custom roms/kernels till yesterday. i installed XXKI4 and everything went perfect.
Few hours later i decided to flash CM7( wiped system,data,cache dalvik etc and flashed the zip 2x) so after this i rebooted my phone and it gave a bootloop. I was not able to boot in recovery mode so i had to reflash with odin to a stock rom. Well i did that and i was on stock rom again. i decided to flash the latest speedmod kernel, i flashed it and bam phone not booting, shows the Samsung Galaxy S II GT-i9100 text with the yellow triangle and its stuck at this screen for an hour now. i just cant use ANY custom kernel/rom on my phone because they all give bootloops and i want CM7 so bad. Any idea's and suggestions will be truly welcome.
Stock Samsung Roms are working great, but dont want that ;p
thx!
Coentje44 said:
Hey guys,
So i have my S2 for like 6 months now and never had any issue with flashing custom roms/kernels till yesterday. i installed XXKI4 and everything went perfect.
Few hours later i decided to flash CM7( wiped system,data,cache dalvik etc and flashed the zip 2x) so after this i rebooted my phone and it gave a bootloop. I was not able to boot in recovery mode so i had to reflash with odin to a stock rom. Well i did that and i was on stock rom again. i decided to flash the latest speedmod kernel, i flashed it and bam phone not booting, shows the Samsung Galaxy S II GT-i9100 text with the yellow triangle and its stuck at this screen for an hour now. i just cant use ANY custom kernel/rom on my phone because they all give bootloops and i want CM7 so bad. Any idea's and suggestions will be truly welcome.
Stock Samsung Roms are working great, but dont want that ;p
thx!
Click to expand...
Click to collapse
Have you done 2x flash in a row of CM7? its a know bug (but unknown reasons) it just dosnt start until you flash it 2x in a row.
Suggested method:
1. Enter ClockWorkMod recovery
2. Wipe data/cache factory reset
3. Wipe cache
4. From mount and storage menu, use Format System
5. From advanced menu, use the Wipe dalvik cache
6. Flash CM7 latest nightly
7. Reflash CM7 latest nightly
8. Reboot the phone
Not sure if this can help you, since you experience a problem that is not exactly the one i saw some times on forum (you cant even enter recovery mode after the flash) but this is how usually ppl makes CM7 work
Oh on a side note, i suggest to not use rom manager, it's confirmed (at least, from various posts here on xda) to not be really 100% working on our SGS2 and can cause problems.
If all this isnt working, it may be worth downgrade to KI3 or KH3 stock one, root again and then do the above system.
I can assure you 100% this system works over KI3 and KH3
yep you need to flash 2 x CM7.
First time it will flash very fast.
Go back to the stock rom and then install CM7 again
can you boot in CWM or are you getting some errors ?
Cangir said:
yep you need to flash 2 x CM7.
First time it will flash very fast.
Go back to the stock rom and then install CM7 again
can you boot in CWM or are you getting some errors ?
Click to expand...
Click to collapse
nah, this won't do it, believe me! coz i have exactly same issue with mine. I've done this countless number of times and nothing works... i just came to accept the fact that my phone doesn't support custom anything whether kernel or ROMs, until someone finds out the solution.
meanwhile you can try siyah kernel 1.7.8 or so, it worked with mine, see if it works with yours.
cheers!
henrychukx said:
nah, this won't do it, believe me! coz i have exactly same issue with mine. I've done this countless number of times and nothing works... i just came to accept the fact that my phone doesn't support custom anything whether kernel or ROMs, until someone finds out the solution.
meanwhile you can try siyah kernel 1.7.8 or so, it worked with mine, see if it works with yours.
cheers!
Click to expand...
Click to collapse
i know this problem, my phone was stuck at boot too but i flashed back to stock rom and i fixed my phone. my problem was i can't use cwm its was dead.
i already tried to flash cm7 like 10 times and it doesnt work i can only boot stock roms with the speedmod kernel other kernels give bootloop.
Ugh this is pretty frustrating, will try to downgrade to xxki3.
Btw, after i flashed Cm7 twice my phone bootloops, then when i flash a CWM kernel to boot in recovery mode i get Can't mount /cache/blabla. really weird, i have never seen this on a phone ! =)
Yay its working!! downgraded to XWKI4 and flashed the cwm kernel! now im running CM7! thx peeps! =)
For the other people that had problems, you have to flash the codeworkx kernel because cf root kernel has a modified CWM that is not compatible withCM7
i have almost the same problem,but me i can flash any rom,but the problem is with the kernel my phone refuses to boot on any other kernel else than cf-root and the speedmod,it freezes in the kernel loading so i must turn it off and reflash via odin cf-root or speedmod to get it works again.
teknoman17 said:
i have almost the same problem,but me i can flash any rom,but the problem is with the kernel my phone refuses to boot on any other kernel else than cf-root and the speedmod,it freezes in the kernel loading so i must turn it off and reflash via odin cf-root or speedmod to get it works again.
Click to expand...
Click to collapse
+1, i have the same problem.
Please Help
teknoman17 said:
i have almost the same problem,but me i can flash any rom,but the problem is with the kernel my phone refuses to boot on any other kernel else than cf-root and the speedmod,it freezes in the kernel loading so i must turn it off and reflash via odin cf-root or speedmod to get it works again.
Click to expand...
Click to collapse
Yes, its all the same problem, flashing a rom with a diff kernel won't boot up, will just be stuck on boot logo...
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
Phew! NOW I HAVE CM7 RUNNING ON MY PHONE!!
I'm gonna try to explain how i fixed my issue, as clear and explanatory as i can..
lucky i didn't brick my phone during all this, because I tried so many things and none worked.I unsuccessfully tried downgrading to XWkI4, ZCKI4, and alot others via Odin... after flashing all i get is tons of error messages(on 3e recorvery) E: can't open/cache or E:failed blah bla bla to load /efs... i thought OMG! my phone is bricked! then i recalled reading somewhere that flashing the 3 tar (PDA,MODEM,CSC) files usually should work(maybe better than flashing a 1 tar file), so i found a 3 files xxKI3 rom, flashed it and BAM! it booted up this time without any error. so now i went ahead and rooted it since the tar files came unrooted, then went into CWM to flash cm7 ROM, flashed it twice and ofc i got stuck on boot logo.....i didn't panic much, i pulled out the battery, and restarted to CWM where i cleared cache/ dalvik/ and did wipe/factory reset, then i reflashed CM7 again (twice) and it worked!!!! YES, CM7 is fiannly working on my SG2!
thanks for everyone for helping, and i hope this can help others in same boat as me..
abhigupta7 said:
+1, i have the same problem.
Please Help
Click to expand...
Click to collapse
+1 here also can only get the CF kernel to work. Any rom seems to work but only if the kernel is replaced with CF
andybarron said:
+1 here also can only get the CF kernel to work. Any rom seems to work but only if the kernel is replaced with CF
Click to expand...
Click to collapse
Try what i said and see if it works.
try the siyah 2.1.1 kernel,it solved my problem
First I had XXLPQ then I flashed siyah kernel v3.2.8 through CMW, I used it for like a day then everything started crashing so I just rebooted and then I got a bootloop.
I flashed XWLP7 it got stuck at the bootlogo(before animation screen) so I went into recovery mode and then it said "successful csc install (KOR)" something like that then I flashed siyah kernel v3.3.1 though ODIN, now I tried to change the CSC though the menu by using *#272*IMEI No# then it just never booted it just stays at the "Samsung Galaxy S II" the one before the animation screen.
I tried searching i found nothing similar...
I think its a boot loader problem, How do i flash a boot loader ?
pleease help
EDIT: I finally got it into download mode, now can someone please tell me whats the issue ?
bootloaders are roughly half way down 1st post http://forum.xda-developers.com/showthread.php?t=1075278
edit: if youve got it into download mode just flash a stock rom for now so you have a working device again
skimminstones said:
bootloaders are roughly half way down 1st post http://forum.xda-developers.com/showthread.php?t=1075278
edit: if youve got it into download mode just flash a stock rom for now so you have a working device again
Click to expand...
Click to collapse
Thanks yes as I said I flashed a new stock rom and kernel but no use anyway am gona flash a bootloader which I finally found here
I think there was an issue with the bootloader and kernel, i flashed the bootloader but it didnt work so I flashed a CF-root kernel and it finally worked .
Ba7rani123 said:
I think there was an issue with the bootloader and kernel, i flashed the bootloader but it didnt work so I flashed a CF-root kernel and it finally worked .
Click to expand...
Click to collapse
So now it boots past the Galaxy S2 screen? I have experienced that for 2-3 times now, same thing where everything started crashing and rebooting the phone will end up stuck at the bootscreen. What I had to do is to wipe data, dalvik, and cache then only it would work again.
It could be due to the particular ROM used as I have not experienced it after using the newer XWLPD for a few weeks now.
nanoronline said:
So now it boots past the Galaxy S2 screen? I have experienced that for 2-3 times now, same thing where everything started crashing and rebooting the phone will end up stuck at the bootscreen. What I had to do is to wipe data, dalvik, and cache then only it would work again.
It could be due to the particular ROM used as I have not experienced it after using the newer XWLPD for a few weeks now.
Click to expand...
Click to collapse
its a siyah kernel v2.3.8 issue where some files get corrupt, so even after flash v3.3.1 some files maybe corrupt also. So a full wipe is advised after backup.
Hoesntly I dont know but I think that its linked to the rom :/.
Ba7rani123 said:
its a siyah kernel v2.3.8 issue where some files get corrupt, so even after flash v3.3.1 some files maybe corrupt also. So a full wipe is advised after backup.
Hoesntly I dont know but I think that its linked to the rom :/.
Click to expand...
Click to collapse
No back then I was still using the stock kernel. Just rooted with ChainFire's method and that's all.
nanoronline said:
No back then I was still using the stock kernel. Just rooted with ChainFire's method and that's all.
Click to expand...
Click to collapse
Maybe a bootloader issue, see this thread it explains alot
http://forum.xda-developers.com/showthread.php?t=1457458
If u can boot to recovery then its fine but if u can only boot into download mode then u have corupption
Ba7rani123 said:
Maybe a bootloader issue, see this thread it explains alot
http://forum.xda-developers.com/showthread.php?t=1457458
If u can boot to recovery then its fine but if u can only boot into download mode then u have corupption
Click to expand...
Click to collapse
No I could boot into both recovery and download modes. Back then I tried flashing the same firmware and newer firmware but both still ended stuck at the boot screen. Only after I booted into recovery to wipe data, Dalvik cache and cache then it booted past the bootscreen and working again.
nanoronline said:
No I could boot into both recovery and download modes. Back then I tried flashing the same firmware and newer firmware but both still ended stuck at the boot screen. Only after I booted into recovery to wipe data, Dalvik cache and cache then it booted past the bootscreen and working again.
Click to expand...
Click to collapse
maybe some of the data was corrupt *-)
Every ROM zip file I attempt to flash via CWM or TWRP doesnt work. I was on stock ICS (4.0.4) which I flashed using Odin. Every JB rom, stock or custom I attempt to flash with a recovery freezes either at boot up or first screen of initial setup. No errors are given on actual flash, it always looks good. . I wiped everything I can wipe, which is everything but emmc I think. What could be the problem? I have now flashed official JB through Odin twice with no issues.
Do you check that the ROM is downloaded properly by checking the md5 hash?
EVOO2 said:
Every ROM zip file I attempt to flash via CWM or TWRP doesnt work. I was on stock ICS (4.0.4) which I flashed using Odin. Every JB rom, stock or custom I attempt to flash with a recovery freezes either at boot up or first screen of initial setup. No errors are given on actual flash, it always looks good. . I wiped everything I can wipe, which is everything but emmc I think. What could be the problem? I have now flashed official JB through Odin twice with no issues.
Click to expand...
Click to collapse
Try flashing a new recovery using odin then try to flash the rom in recovery afterwards.
Sent from my SGH-T989 using Tapatalk
richardlibeau said:
Try flashing a new recovery using odin then try to flash the rom in recovery afterwards.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Ive flashed twrp 2.5 twice through odin and then tried to flash a rom with no improvement. Im really stumped 'cause flashing roms with odin works fine everytime, so it would seem nothings physically wrong with my device. Should I try a different recovery program? Using cwm and twrp give the same result, so Im skeptical a third recovery would be any different.
cheers
EVOO2 said:
Ive flashed twrp 2.5 twice through odin and then tried to flash a rom with no improvement. Im really stumped 'cause flashing roms with odin works fine everytime, so it would seem nothings physically wrong with my device. Should I try a different recovery program? Using cwm and twrp give the same result, so Im skeptical a third recovery would be any different.
cheers
Click to expand...
Click to collapse
Only thing i can think of is look at the file format that youre trying to flash.
Is it zip? tar?
I may be wrong but cwm only works for .zip files from my experience. not .tar md5 etc.
why do you need to flash it via cwm? if its flashing through odin whats the problem?
It sounds like what ^^^^ is saying. Recovery flashes zip files and Odin flashes tar files. Don't confuse the zip files your pc uses to download the files with these.
When using odin I have to use ROM s which are .tar, so this basically limits me to stock ROMS. The custom ROMS are .zip which I can only flash with a custom recovery like twrp or cwm. I'd obviously like to flash the custom ROMS which are .zip , however it isn't working for me as I mentioned in the opening post . Not sure how to fix this problem .
EVOO2 said:
When using odin I have to use ROM s which are .tar, so this basically limits me to stock ROMS. The custom ROMS are .zip which I can only flash with a custom recovery like twrp or cwm. I'd obviously like to flash the custom ROMS which are .zip , however it isn't working for me as I mentioned in the opening post . Not sure how to fix this problem .
Click to expand...
Click to collapse
extraxt the rom that your saying is .zip. it "should" extract a file that will be something odin will recognize
dweeezy said:
extraxt the rom that your saying is .zip. it "should" extract a file that will be something odin will recognize
Click to expand...
Click to collapse
Good idea. In a recovery zip file will be a couple of folders. One of them will have a tar file you can flash in the phone or pda a lot in Odin.
Thanks for the suggestion but I had no luck . I have tried extracting padawan JB and a debloated stock JB rom and they extract many files, folders, apks but no tar I could locate. Also I am not sure even if there was a tar i could use if it would be safe to use. If all this was good, it would still be a cumbersome workaround and wouldnt fix my problem of not being able to get a ROM installed via recovery to work.If I have no choice I'll use odin to flash custom ROMs (if there is a way) but Id rather get it to work with recovery.
EVOO2 said:
Thanks for the suggestion but I had no luck . I have tried extracting padawan JB and a debloated stock JB rom and they extract many files, folders, apks but no tar I could locate. Also I am not sure even if there was a tar i could use if it would be safe to use. If all this was good, it would still be a cumbersome workaround and wouldnt fix my problem of not being able to get a ROM installed via recovery to work.If I have no choice I'll use odin to flash custom ROMs (if there is a way) but Id rather get it to work with recovery.
Click to expand...
Click to collapse
If you're flashing between TW based to AOPS, or pretty much from a rom to a completely different rom, you will need to WIPE your data too, or better, do a complete wipe (factory reset). I had this issue when moving from Stock TW-based rom to Padawan JB rom. I did a factory reset (complete wipe) and it booted fine. But then again, I'm used to TW so I flashed that back.
fbauto1 said:
If you're flashing between TW based to AOPS, or pretty much from a rom to a completely different rom, you will need to WIPE your data too, or better, do a complete wipe (factory reset). I had this issue when moving from Stock TW-based rom to Padawan JB rom. I did a factory reset (complete wipe) and it booted fine. But then again, I'm used to TW so I flashed that back.
Click to expand...
Click to collapse
I've wiped everything I can wipe between flashes (includes factory reset), many times trying both TWRP and CWM for flashing and wiping with no luck unfortunately. The wiping doesnt seem to help, different custom recoveries don't help, so I'm stumped as to what the problem could be.
EVOO2 said:
I've wiped everything I can wipe between flashes (includes factory reset), many times trying both TWRP and CWM for flashing and wiping with no luck unfortunately. The wiping doesnt seem to help, different custom recoveries don't help, so I'm stumped as to what the problem could be.
Click to expand...
Click to collapse
What roms are you trying to flash? Sometimes ive seen where you must rename them or do specific things.
dweeezy said:
What roms are you trying to flash? Sometimes ive seen where you must rename them or do specific things.
Click to expand...
Click to collapse
Ive tried padawan JB, debloated rooted canadian JB rom, and debloated ATT rom.
dweeezy said:
What roms are you trying to flash? Sometimes ive seen where you must rename them or do specific things.
Click to expand...
Click to collapse
Ive tried padawan JB, debloated rooted canadian JB rom, and debloated ATT rom.
OP, are you still having this issue? Were you able to resolve it?
I have the exact same issue as you. Exactly the same.
513263337 said:
OP, are you still having this issue? Were you able to resolve it?
I have the exact same issue as you. Exactly the same.
Click to expand...
Click to collapse
Me too. Every rom freezes during the app optimization screen...usually at about 3/4th the way through. What's going on???
*edit* Tried to restore factory w/Odin. I'm bricked now. Time for some JTAG love.
Exactly the same issue here.
Every jelly bean ROM, 4.1 or 4.2, stock or custom, as long as I install them via recovery, it either doesn't boot up or gets stuck on the first screen.
If I use ODIN to install the stock ROM, it works fine.
Driving me nuts...
Just throwing suggestions out there but try sideloading the rom and see if itll install that way? Also are you odin flashing recovery? Maybe try to load twrp through goomanager and see if maybe recovery is corrupted?
Sent from my SAMSUNG-SGH-I717 using xda premium
Hai.
I have a galaxy note 3 sm n9005. Have already rooted by finding forum from xda and even install twrp recovery following the guides given.
But im trying to install custom rom. And tried all the roms tat is given from xda for note 3 and could install single one.
Please help to resolve this problem. Im confuse.
Tq.
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
es0tericcha0s said:
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
Click to expand...
Click to collapse
Im using twrp 3.0.2.1 and everytime i try to install a rom it stuck at samsung screen.
And it show md5 not found.
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
es0tericcha0s said:
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
Click to expand...
Click to collapse
Resurrection remix.unicorn.slim.and all cynogen rom is working. Im trying install s7edge custom rom for darkwolf and darklord. I even updated the bootloader and modem according to tutorial. I used odin to flash them..
N9005xxugboa1
Lrx21v.n9005xxugbob6
I have my stock rom n internl backed up. I try all. And still it always stuck on samsung screen.
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
es0tericcha0s said:
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
Click to expand...
Click to collapse
How can install kernel after. Everytime i install it reboots its self to samsung screen. Or should go back to recovery and install the kernel back. And thank you for your help till now.
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
es0tericcha0s said:
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
Click to expand...
Click to collapse
I have uncheck the reboot after install. When i install the rom it automatically reboot itself. It doesnt show anything or show done. Once it even show os not found.
Hi
Where can i install or find the latest kernel
It's in the installation instructions for the rom.
es0tericcha0s said:
It's in the installation instructions for the rom.
Click to expand...
Click to collapse
Hi.
I have found the bootloader and modem for my sm n9005 from the installation instruction for the rom.
I try to flash according to the tutorial.and my baseband didnt change. I try flash using odin 3times.
Im not sure where i did wrong.can u help me
Tq
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
tq
es0tericcha0s said:
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
Click to expand...
Click to collapse
Tq
Will try and let you know
sitijohn85 said:
Tq
Will try and let you know
Click to expand...
Click to collapse
Hi
I tried as said and it didnt chnge.
Can i ask bootloader should be at bl and modem should be at cp. Is it correct.
Hi
Thank you for your help.
I did the change on bootloader and modem.
Now im i need to know two more thing.
I download 2 dffernt kind of bootloader n modem.
I flash blxxxxxbpb1 and cpxxxxxboj1..this 2 files were tar.md5 files
Another one which i didnt flash. Blxxxxxxbpb1 and cpxxxxxxxbpb2..this 2 files are tar.tar files..
Can i know whats the different with this 2 files.
One more thing is when i chnge the bootloader and modem will the kernel changes. Or is it different.
Please guide me..im confuse.
Someone might have just mislabeled them. Flashing those will not affect kernel. Different partition of the phone.
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
sitijohn85 said:
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
Click to expand...
Click to collapse
This is the recommended kernel
https://www.androidfilehost.com/?fid=24572369242687310
Recommended recovery is TWRP 2.8.7.0 not the newer 3.0+
Flash other recovery. Boot to TWRP. Wipe system, data, cache, dalvik. Flash rom. Wipe caches. Flash kernel. Reboot. Should work according to lots of people on the thread for that rom.
Hi.
How flash kernel.
just flash the tar.md5 file or the tar.zip file