Hi, wondering if anyone can help.
I was running my note 2 n7100 on Omega rom v15 with perseus kernal v35. It was fine, until yesterday my phone started rebooting.
I reflashed Omega rom, I unrooted and reflashed stock rom, I rooted and tried other roms.. however, im still having problems.
Once the phone has restarted and got to home screen, whenever I do anything, the phone reboots. (on Cm10.1 rom varients - jellybam and pa3.5)
When using stock rom and omega rom the phone doesn't even go past the samsung galaxy note II logo screen.
I've read somewhere, that reflashing the bootloader may help, so I may give that a try..
Does anyone else have any ideas or similar problems?
Hi
Never had this issue but if I were you, I think I'll do all Wipe & format options from my recovery and then I'll flash a Factory firmware via Odin.
Memphis_ said:
Hi
Never had this issue but if I were you, I think I'll do all Wipe & format options from my recovery and then I'll flash a Factory firmware via Odin.
Click to expand...
Click to collapse
He did that.
Could be A hardware issue.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
He did that.
Could be A hardware issue.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Flashing a stock rom isn't a clean installation so this is not what I suggested.
Related
How does a Telus owner flash a rom for the T989 without boot loops? Is there a kernel or radio they have to flash?
Every Rom comes with a kernel. Well almost every Rom does. You just need to flash it normally. Telus and T-Mobile are completely identical. Shouldn't cause bootloops. sounds like user error?
Sent from my SGH-T989 using xda app-developers app
Teo032 said:
Every Rom comes with a kernel. Well almost every Rom does. You just need to flash it normally. Telus and T-Mobile are completely identical. Shouldn't cause bootloops. sounds like user error?
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
That's what I thought and I guess it could be user error, but I've tried to help several different Telus users that get bootloops unless the rom is specifically for the Telus. One finally got it to work by flashing a different radio but he never got back to me about which radio.
Radio shouldn't be the problem with the bootloop. Might it be the way you're flashing?
Sent from my SGH-T989 using xda app-developers app
Teo032 said:
Radio shouldn't be the problem with the bootloop. Might it be the way you're flashing?
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Its not me . I don't have the Telus. It was 2 or 3 different Telus users trying different roms. One was trying CM9, another Jedi Mind Trick, and I can't even remember the other. They would either get a boot loop or stuck at the boot up screen. I started thinking maybe it was something different a Telus user had to use. It sounded like they were flashing right and using Darkside Super and Cache wipe.
The one trying Jedi was told to update his radio and it worked. So that got me wondering about Telus and radios. I dunno ..
Depends on their recovery. The wipe scripts might not be preferred anymore. If they're flashing from gb then yeah they probably need to change to a ics radio.
Sent from my SGH-T989 using xda app-developers app
I haven't had any problems running T-Mobile ROMs and I'm with Telus. I've used 3 or 4 different GB ROMs, 3 ICS ROMs and one JB ROM. Some were Telus specific while others weren't.
All ROMs/kernels/radios were flashed using non touch cwm 5.0.2.7. I also use the darkside scripts.
mintharis said:
I haven't had any problems running T-Mobile ROMs and I'm with Telus. I've used 3 or 4 different GB ROMs, 3 ICS ROMs and one JB ROM. Some were Telus specific while others weren't.
All ROMs/kernels/radios were flashed using non touch cwm 5.0.2.7. I also use the darkside scripts.
Click to expand...
Click to collapse
Thanks, I talked to another Telus user who hasn't had a problem either. I guess it was just a user error with the other folks.
I have a boot loop problem with my Koodoo T989D on stock TLLG2 rom.
First I odin the recovery 5.0.2 to flash UVLH1, and then flash the CM10 10/22.
Next reboot the phone and it hangs at the CM10 boot animation screen.
Tried to odin back the UVLH1 stock rom but it fails to write at amss.bin.
Tried the Darkside cache wipe but doesn't make a difference
Can someone give me any suggestion?
RA017 said:
I have a boot loop problem with my Koodoo T989D on stock TLLG2 rom.
First I odin the recovery 5.0.2 to flash UVLH1, and then flash the CM10 10/22.
Next reboot the phone and it hangs at the CM10 boot animation screen.
Tried to odin back the UVLH1 stock rom but it fails to write at amss.bin.
Tried the Darkside cache wipe but doesn't make a difference
Can someone give me any suggestion?
Click to expand...
Click to collapse
Did you make a nandroid backup before you flashed UVLH1? Did you try to Odin back to the stock Koodo rom?
RA017 said:
I have a boot loop problem with my Koodoo T989D on stock TLLG2 rom.
First I odin the recovery 5.0.2 to flash UVLH1, and then flash the CM10 10/22.
Next reboot the phone and it hangs at the CM10 boot animation screen.
Tried to odin back the UVLH1 stock rom but it fails to write at amss.bin.
Tried the Darkside cache wipe but doesn't make a difference
Can someone give me any suggestion?
Click to expand...
Click to collapse
Use this recovery
http://forum.xda-developers.com/showthread.php?t=1844637
I had the same problem
supersain08 said:
Use this recovery
http://forum.xda-developers.com/showthread.php?t=1844637
I had the same problem
Click to expand...
Click to collapse
Thanks for your suggestion, I'll double check tonight.
FYI, last night I tried ODIN the T989D image (not T989) and finally it flash successfully with the modem.
I have a rooted note 2 with cwm installed. I am running omega rom. Whenver i boot into recovery and select the option full wipe/ data reset.. My recovery reboots. What can i do now ? I'm really scared.
Man please someone help :\
tanujS said:
I have a rooted note 2 with cwm installed. I am running omega rom. Whenver i boot into recovery and select the option full wipe/ data reset.. My recovery reboots. What can i do now ? I'm really scared.
Click to expand...
Click to collapse
which version of omega are you running?
i'd suggest flashing CWM again and see if you still have that issue first.
Thankyou...
I'm running omega v8.0
I flashed cwm again but still the same problem. But now somehow i managed to install cyanogen mod and then performed the data wipe. It worked now. Thankyou for your reply
tanujS said:
I'm running omega v8.0
I flashed cwm again but still the same problem. But now somehow i managed to install cyanogen mod and then performed the data wipe. It worked now. Thankyou for your reply
Click to expand...
Click to collapse
flash a different recovery with odin or mobile odin
try this link m8
http://d-h.st/beT
I was running on stock rom and was getting random reboots. It would not even boot completely and reboot again. Its been a while I havnt experienced that problem but its very scary. I love my phone too much for anything to happen to it
Sent from my GT-N7100 using xda premium
Use twrp. Imao its better. Far better.
Sent From Samsung's Galaxy Note II Using Internet
Flashing twrp bricked my phone. What to do now ?
Sent from my GT-N7100 using xda premium
What the ?
Sent From Samsung's Galaxy Note II Using Internet
---------- Post added at 12:37 AM ---------- Previous post was at 12:37 AM ----------
What do you mean bricked ? What is happening ?
Sent From Samsung's Galaxy Note II Using Internet
hmm..CWM so far worked ok for [email protected]@..maybe ur version of CWM is corrupted><
trioxyn said:
hmm..CWM so far worked ok for [email protected]@..maybe ur version of CWM is corrupted><
Click to expand...
Click to collapse
Yes.. I think my cwm got corrupted. I flashed cwm again and now it works like a charm.
Thanks guys for your help!
whenever i flash any custom rom whether the rom version is android 4.2/4.1.2/4.1.1 , my phone has no bootscreen and a messed up flashscreen when it sais (samsung galaxy note 2 GT-N7100) but then after waiting the appropriate time, the rom works fine but same problem when rebooting... i attached the flashcreen and how it looks like, i have no idea why this happens.i just press the lockscreen after rebooting and waiting and the rom works normally. i rooted using the Galaxy Note II Toolkit v3.0.0 GSM. i first experienced this right after flashing and entering recovery(cmw) but twrp worked fine then, now any rom i flash i experience this,
Is anyone faceing a similar problem or can help in anyway ?
stock rom works fine btw
try flashing Philz recovery
dr.ketan said:
try flashing Philz recovery
Click to expand...
Click to collapse
is philz recovery in the link u posted because i cant see it,
inorder to install it, i flash stock rec then philz via odin right?
http://forum.xda-developers.com/showthread.php?t=2028103
yes flash tar file with odin (no need to flash stock, straight way flash with odin)
dr.ketan said:
http://forum.xda-developers.com/showthread.php?t=2028103
yes flash tar file with odin (no need to flash stock, straight way flash with odin)
Click to expand...
Click to collapse
this is the second picture... i flashed philz and still same problem! stock works fine :S its making me crazy!
I have the same screen after installing cm 10.1 ... never tried to wait some time to boot.... tried several times with several recoveries... result the same. Before used s3 i9300 and never had such issue. Hope someone will help
Sent from my GT-N7100 using xda premium
T511 said:
I have the same screen after installing cm 10.1 ... never tried to wait some time to boot.... tried several times with several recoveries... result the same. Before used s3 i9300 and never had such issue. Hope someone will help
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
tell me a rom you tried that works fine with the bootanimation and everything please! because so far ive tried several! non have worked. and what recovery are you using?
karlada said:
tell me a rom you tried that works fine with the bootanimation and everything please! because so far ive tried several! non have worked. and what recovery are you using?
Click to expand...
Click to collapse
I tried rom managers cwm and twrp manager and cm 10.1 rom only. Tried several times and no luck. Same screen after install.
Sent from my GT-N7100 using xda premium
Guys here is my problem. I tried to upgrade my Samsung N7105 to 4.3 via OTA and it got stucked on bootloop.
I tried to access recovery mode but it fails, only download mode.
What i did is I downloaded the official 4.3 firmware at SamMobile and flashed it with Odin 3.09
Based on Odin it is successful but im still stuck on bootloop and recovery mode cannot still be accessed.
Tried to root it also and installed CWM to recover. I was able to to access CWM
so i restored factory setting, wipe cache and dalvik cache but still the phone bootloops.
Any suggestions on how to resolve my problem?
iamjerbergerber said:
Guys here is my problem. I tried to upgrade my Samsung N7105 to 4.3 via OTA and it got stucked on bootloop.
I tried to access recovery mode but it fails, only download mode.
What i did is I downloaded the official 4.3 firmware at SamMobile and flashed it with Odin 3.09
Based on Odin it is successful but im still stuck on bootloop and recovery mode cannot still be accessed.
Tried to root it also and installed CWM to recover. I was able to to access CWM
so i restored factory setting, wipe cache and dalvik cache but still the phone bootloops.
Any suggestions on how to resolve my problem?
Click to expand...
Click to collapse
just to add, i think i tripped the knox warrant void. its value is now 1 what this means?
Simply flash philz v5.00.5 and it should solve it, here's the link: http://link.tapatalk.com/api/click?...rs.com&subid=c157297d1a1ff043255bfb18530caaa2
Hope it works
With Regards,
Overdub
Sent from my Galaxy Note II using Tapatalk
OverDub said:
Simply flash philz v5.00.5 and it should solve it, here's the link: http://link.tapatalk.com/api/click?...rs.com&subid=c157297d1a1ff043255bfb18530caaa2
Hope it works
With Regards,
Overdub
Sent from my Galaxy Note II using Tapatalk
Click to expand...
Click to collapse
Was able to access custom recovery upon flashing. conducted wipe data / factory reset and wipe dalvik cache but still bootlooping was experienced. Is my phone dead already and needs replacement?
After flashing the philz, try flashing a custom ROM and see if u will unstuck from the bootloop, try cm 10.2, it's very light and mostly bug free
Sent from my GT-N7100 using xda app-developers app
OverDub said:
After flashing the philz, try flashing a custom ROM and see if u will unstuck from the bootloop, try cm 10.2, it's very light and mostly bug free
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Now working cm10.2 but now my next problem is there is no signal. it appeared that imei value is null. how do i repair this? thanks!
By the way after successfully running on cm10.2 I tried to reflash again with stock firmware. bootloop again. i think i will be stuckon using custom roms for now. The only thing I need to address is the no mobile signal problem.
OK so the bootloop problem is done and don't worry there are a lot of amazing custom roms that are based on the stock one and even better features like the note 3 features, as for the imei, please tell me you did an nfs backup if you do, there are a lot of ways you can restore your nfs backup, if you don't have an nfs backup, I don't know what to do.
With Regards,
Overdub
Sent from my GT-N7100 using xda app-developers app
Not very clued up on losing baseband but it happened to me once when I used a different revovery version to restore a back up. Dr Ketan has written a guide on restoring baseband, he will be able to fix it
Sent from my GT-N7105 using XDA Premium 4 mobile app
Please keep us updated and if it is fixed hopefully, please show us what you did.
With Regards,
Overdub
Sent from my GT-N7100 using xda app-developers app
Still not working
OverDub said:
Please keep us updated and if it is fixed hopefully, please show us what you did.
With Regards,
Overdub
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Sorry was on vacation for a long time. I wasn't able to update this thread.
Problem right now is I forgot to back the EFS so when I flashed CM 10.2
There is no baseband and IMEI is null. Tried to flash n7105 modem but still it still doesn't work
Have read that I should flash stock firmware to fix baseband and IMEI but 4.3 firmwares makes my phone go on bootloop.
Should I wait for 4.4 update? I want my phone to make it usable again.
My phone right now is useless and works like an itouch hahaha
Any suggestions???
Need expert advise
iamjerbergerber said:
Sorry was on vacation for a long time. I wasn't able to update this thread.
Problem right now is I forgot to back the EFS so when I flashed CM 10.2
There is no baseband and IMEI is null. Tried to flash n7105 modem but still it still doesn't work
Have read that I should flash stock firmware to fix baseband and IMEI but 4.3 firmwares makes my phone go on bootloop.
Should I wait for 4.4 update? I want my phone to make it usable again.
My phone right now is useless and works like an itouch hahaha
Any suggestions???
Need expert advise
Click to expand...
Click to collapse
You may try Hurricane modem changer and experiment with various modem versions. It's a longshot but it may help. Try finding very old modem version and flash that.
Hurricane Modem Changer is that an application?
Where to get it? Also, will it there be a possibility that when I flash Official 4.4 kitkat (when released) on my n7105.
Bandwidth and IMEI will be restored? I'm leaning towards to come back to touch wiz though many of you guys might say that a custom rom might be better.
For one thing, the problem in my n7105 started when i upgraded to 4.3 via OTA
iamjerbergerber said:
Hurricane Modem Changer is that an application?
Where to get it? Also, will it there be a possibility that when I flash Official 4.4 kitkat (when released) on my n7105.
Bandwidth and IMEI will be restored? I'm leaning towards to come back to touch wiz though many of you guys might say that a custom rom might be better.
For one thing, the problem in my n7105 started when i upgraded to 4.3 via OTA
Click to expand...
Click to collapse
Look HERE. One of the downloads is Hurricane Modem Changer.
mat9v said:
Look HERE. One of the downloads is Hurricane Modem Changer.
Click to expand...
Click to collapse
Thanks will try. Aside from this. Where can I find old modem?
Will hurricane modem changer work if I used ditto note 3 rom?
iamjerbergerber said:
Thanks will try. Aside from this. Where can I find old modem?
Will hurricane modem changer work if I used ditto note 3 rom?
Click to expand...
Click to collapse
Hurricane contains some older modems along with new ones and yes it will work if you used DN3.
mat9v said:
Hurricane contains some older modems along with new ones and yes it will work if you used DN3.
Click to expand...
Click to collapse
Is the hurricane modem changer link you provided will work on n7105? tried to flash it but aroma installer tells its for n7100 international version
iamjerbergerber said:
Is the hurricane modem changer link you provided will work on n7105? tried to flash it but aroma installer tells its for n7100 international version
Click to expand...
Click to collapse
No, it's for N7100 only - the modems are completely different (3G vs LTE).
Please read the original post carefully before flashing, if the HC was not protected you could have lost network functions completely.
mat9v said:
No, it's for N7100 only - the modems are completely different (3G vs LTE).
Please read the original post carefully before flashing, if the HC was not protected you could have lost network functions completely.
Click to expand...
Click to collapse
Im using an n7105 model. Guess this will not work. Any other suggestions?
From what I understand, the quickest solution is to flash stock firmwares however, i'm quite disappointed that
almost all 4.3 firmwares from sam mobile doesn't work in my phone (always bootlooping)
A technician told me that I should wait for the 4.4 kitkat release, since it might work for my phone.
Now my problem is, I need to have the phone operational. so im willing to flash custom roms for the meantime
but the baseband problem is really testing my patience. hehe
iamjerbergerber said:
Im using an n7105 model. Guess this will not work. Any other suggestions?
From what I understand, the quickest solution is to flash stock firmwares however, i'm quite disappointed that
almost all 4.3 firmwares from sam mobile doesn't work in my phone (always bootlooping)
A technician told me that I should wait for the 4.4 kitkat release, since it might work for my phone.
Now my problem is, I need to have the phone operational. so im willing to flash custom roms for the meantime
but the baseband problem is really testing my patience. hehe
Click to expand...
Click to collapse
It's pretty strange really as stock firmwares are a complete set of bootloader/modem/system that should in theory work perfectly well together without any incompatibility problems. Have you ever tried to install one of them without sdcard and/or simcard installed, maybe you have some leftovers from previous system (Android secure directory) that causes bootloops, also did you completely clean internal sdcard prior to flashing, it may create the same problems as external sdcard.
mat9v said:
It's pretty strange really as stock firmwares are a complete set of bootloader/modem/system that should in theory work perfectly well together without any incompatibility problems. Have you ever tried to install one of them without sdcard and/or simcard installed, maybe you have some leftovers from previous system (Android secure directory) that causes bootloops, also did you completely clean internal sdcard prior to flashing, it may create the same problems as external sdcard.
Click to expand...
Click to collapse
im not sure if i cleaned the internal sdcard prior to flashing.
It started with the OTA update that failed then I tried to flash stock firmware via odin
do i have to do a pre-requisite before flashing it again? so you are suggesting to remove the simcard and external sd card prior to flashing?
I am trying to install the W03 Slim ROM V7 on my Tmobile Galaxy Note 3 through Philz recovery and I am getting stuck in a boot loop.
These are the steps I tried
1. Used Chainfire's root method to root Kitkat 4.4.2 (which was updated through kies). Used the N9005 and not N900T like the instructions asked me to
2. Flashed Philz Recovery through Odin
3. Copied the ROM and Gapps to my Phone.
4. Rebooted into recovery
5. Wiped Data/Factory reset, Install from Zip, wipe cache, wipe dalvik and reboot.
This is where I get stuck. The phone boots with these words on the top left, "Recovery not enforcing seandroid" or something along those lines and keeps booting. I booted back to Recovery and 'Re'wiped' the phone/did a factory reset, but nogo
So I downloaded the right stock firmware from Sammobile, installed through Odin and repeated the steps and still the same issue.
What am I doing wrong? I made sure I am flashing hltetmo (for TMo Note 3).
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
nikhilnagaraj24 said:
I am trying to install the W03 Slim ROM V7 on my Tmobile Galaxy Note 3 through Philz recovery and I am getting stuck in a boot loop.
These are the steps I tried
1. Used Chainfire's root method to root Kitkat 4.4.2 (which was updated through kies). Used the N9005 and not N900T like the instructions asked me to
2. Flashed Philz Recovery through Odin
3. Copied the ROM and Gapps to my Phone.
4. Rebooted into recovery
5. Wiped Data/Factory reset, Install from Zip, wipe cache, wipe dalvik and reboot.
This is where I get stuck. The phone boots with these words on the top left, "Recovery not enforcing seandroid" or something along those lines and keeps booting. I booted back to Recovery and 'Re'wiped' the phone/did a factory reset, but nogo
So I downloaded the right stock firmware from Sammobile, installed through Odin and repeated the steps and still the same issue.
What am I doing wrong? I made sure I am flashing hltetmo (for TMo Note 3).
Click to expand...
Click to collapse
Sounds like a Recovery issue to me. Please look one more time and make sure if you used PHILZ TOUCH that you did in fact flash 6.19.3 HLTE. and not HLTETMO. Im also using philz and no problems flashing. However before it was known that this was the version to use, I did loop at the same point when experimenting with other versoins. Also, check your MD5 and verify that it is a good download.... maybe re download just for gits and shiggles.
---------- Post added at 02:10 AM ---------- Previous post was at 02:07 AM ----------
willham said:
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think the new slimKat is 4.4?
willham said:
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Had the same bootloop issue when I just tried it out. I updated my bootloader when I updated to stock KK through odin. I am assuming by 4.3 you mean the bootloader on SlimRom is the 4.3 bootloader even though it is a 4.4.2 rom?
willham said:
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep.... you are correct sir. 4.3 bootloader. No el flashy 4.3 roms if you updated to 4.4 Bootloader.... im running Echoe rom. Maybe give that a try. Its an international.
Found this on page 78
Sent from my SM-N900T using XDA Premium 4 mobile app
willham said:
Found this on page 78
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks everyone. It does look like it is the bootloader issue.
How do we determine if a particular ROM supports a particular bootloader version? At least the ROMs I have sort of explored and wanted to try, dont mention that anywhere. Or maybe they use some geek term to reference that but I dont understand it. How do noobs like me determine the bootloader version and compatibility of a particular ROM (before flashing and finding out the hard way)???
nikhilnagaraj24 said:
Thanks everyone. It does look like it is the bootloader issue.
How do we determine if a particular ROM supports a particular bootloader version? At least the ROMs I have sort of explored and wanted to try, dont mention that anywhere. Or maybe they use some geek term to reference that but I dont understand it. How do noobs like me determine the bootloader version and compatibility of a particular ROM (before flashing and finding out the hard way)???
Click to expand...
Click to collapse
Not really an answer to your question but I did flash pac-rom without issue. So there is one safe one.
Sent from my SM-N900T using Tapatalk
I think w03 slim rom v4 works with 4.4 bootloader
Enviado desde mi SM-N900T mediante Tapatalk