Related
Hi all
I'm not new to flashing but I'm new to flashing cm7.
I odin back to stock jfd eclair. Root and Install CWM 2.xxx. I downloaded the stable cm7 and I started flashing. (after I wipe data/cache of course)
IN recovery, it said finding package, opening package, then my phone processed a series of lines and reboot automatically. On the startup, it says VIBRANT SAMSUNG, then GALAXY S CYANOGEN(mod) then the same recovery screen with many lines. It moved too fast into another reboot I couldn't read what was on the screen. And it kept doing this for quite 10 mins now.
Is it normal? if not, what did I do wrong? I can get into download mode and odin back to stock but I did it last night and I couldn't think what i did wrong.
Please help!
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
stumpyz9 said:
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
wavestar92 said:
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
Click to expand...
Click to collapse
Try reflashing cwm when your rooted, may have not flashed right
Sent from my Gewgle Phone via XDA App
This happened to me also, I went directly back to recovery, 3 button, and reflashed. Worked the second flash for some reason.
Thanks. I turn it off, get into recovery again, and re flash it successfully
Same exact thing happened. I have no idea how many time I odened back to stock trying to figure it out.
I did as you guys said, as soon as that loop began, pulled the battery and got back into recovery. flashed again and worked just fine!
same thing happened to me...i got back into recovery...i noticed cwm updated to 5.0.2.8 then i reflashed and all good...when i tried to flash at first. cwm was 2.5 ..maybe thats the issued it wont flash on that...has to be cwm 5.0
anyway getting ready enjoy some cm7 on my vibrant...
was installing the hyperdrive Rom using clockwork recovery mod, it says it installed sucessfully but when i go to reboot the device it just going into reboot loop, i can get back into recovery mod but when i try to factory reset and try it again it just does the same thing again, tried installing a different rom and still same thing, what am i doing wrong?
im having the same problem. i cant boot into recovery. is there anything i can do. i was on cm10.1 before this and it worked fine. i flashed hyperdrive using OUDHS and it installed and everything. i let it sit for 10 minutes like it said to then i continued to reboot... and now its stuck on the custom padlock screen and im cant boot into recovery for some reason...
OMsupp said:
im having the same problem. i cant boot into recovery. is there anything i can do. i was on cm10.1 before this and it worked fine. i flashed hyperdrive using OUDHS and it installed and everything. i let it sit for 10 minutes like it said to then i continued to reboot... and now its stuck on the custom padlock screen and im cant boot into recovery for some reason...
Click to expand...
Click to collapse
Try to get in to Odin mode. If you can flash the Stock Image and go from there.
RLS7 Verizon S4 continuous reboot loop
galaxyfans said:
was installing the hyperdrive Rom using clockwork recovery mod, it says it installed sucessfully but when i go to reboot the device it just going into reboot loop, i can get back into recovery mod but when i try to factory reset and try it again it just does the same thing again, tried installing a different rom and still same thing, what am i doing wrong?
Click to expand...
Click to collapse
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
abalgir66 said:
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
Click to expand...
Click to collapse
dont install any audio mod and also dont install any of the music players just the samsung one !
before you go through all the trouble of ODIN, which seems to be everyones answer now a days, it is a kernel issue, flash a verizon loki kernel. It should boot.
abalgir66 said:
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
Click to expand...
Click to collapse
First, if you have a back up, restore just the system partition (this will also format your current /system) Then do a factory reset and reboot. Now I if that doesn't work, Odin is your best bet.
Sent from my SCH-I545 using xda app-developers app
FOR anyone installing Hyperdrive, the most probable cause of boot loop in the Walkman Music App. Don't choose it in Aroma!!!
If you already have, the only way to fix the boot loop is to ODIN back to stock, as Dark Menace suggested.
He can PM you the stock image, which you will have to flash in ODIN to successfully boot up again.
hey I do plenty of flashing, and from time to time get into trouble... But ODIN is not the first choice to fix... Please read the forums:cyclops:
Sent a few PM's to see if that helps. You can try the kernels first then go from there.
Sent from my SCH-I545 using xda premium
fix
I had the same problem had to go back in odin mode and reflash a old stock. If that does not work reset data and cache and install a new rom. Worked for me
DarkMenace said:
Sent a few PM's to see if that helps. You can try the kernels first then go from there.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
I will try again without selecting the music app. I was always selecting the Sony one. I will try this afternoon and keep you informed.
Thanks
abalgir66 said:
I will try again without selecting the music app. I was always selecting the Sony one. I will try this afternoon and keep you informed.
Thanks
Click to expand...
Click to collapse
It worked perfectly if we do not select any music app. Thanks
Device gets stuck at S4 logo with blue font RECOVERY BOOTING, even after Odin, any ideas??
I'm so stuck!
TheAxman said:
before you go through all the trouble of ODIN, which seems to be everyones answer now a days, it is a kernel issue, flash a verizon loki kernel. It should boot.
Click to expand...
Click to collapse
I can't get my phone to see the the SD card in recovery. My Verizon Galaxy S4 is stuck in a boot loop thanks to Hyperdrive RLS12 and Odin fails every time I try it. Any help would be greatly appreciated!!
Surge1223 said:
First, if you have a back up, restore just the system partition (this will also format your current /system) Then do a factory reset and reboot. Now I if that doesn't work, Odin is your best bet.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I am trying hyperdrive on Baseband I545VRUEMJ7 and build JSS15J.I545VRUEMJ7 (4.3). I am able to root and install safestrap. Even hyperdrive/dirty unicorns (i tired both) installs fine, but ends up in reboot loop. am i missing anything here?.
Been playing with my phone all day and somehow it crashed/rebooted & now I'm getting "Process system isn't responding"ever time it boots back up. Im rooted and have TWRP recovery...made a backup before all this started. Tried restoring my backup, didnt work, nor did using ODIN to flash a stock file. Full wipes and format data doesn't do any good either...Any suggestions?
I had the same issue this morning and after wiping and odin'ing what seems liked 30 times for 4 hours, I ended up taking it back. BB swapped it out with no questions asked.
The only thing I can think that happened was I tried restoring a backup with TWRP. I thought I read on here that restoring was not a good idea right now.
Looks like I am going to have to return this as well...every time it boots I get that error message and then it reboots itself....Did you do anything to flash back stock status??
jauger said:
Looks like I am going to have to return this as well...every time it boots I get that error message and then it reboots itself....Did you do anything to flash back stock status??
Click to expand...
Click to collapse
Oh yes, many, many times! After I got stuck in a boot loop (or bootup system error), I wiped every partition I could find on the phone using stock TWRP and OUDH recoveries. Than I would odin multiple times using the MI3 tar. The odin process would be successful, but I would get stuck in a boot-loop every time. I'm fairly savvy with Samsung phones as I have rooted all 5 that I've owned but I couldn't figure this one out so I just took it back.
jauger said:
Looks like I am going to have to return this as well...every time it boots I get that error message and then it reboots itself....Did you do anything to flash back stock status??
Click to expand...
Click to collapse
After the successful Odin, have you tried booting into stock recovery and wiping data? That can often fix problems booting up after a restore..
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
lmemma16 said:
After the successful Odin, have you tried booting into stock recovery and wiping data? That can often fix problems booting up after a restore..
Click to expand...
Click to collapse
Edit: Nevermind, just read your op more carefully, lol. So you did try that?
runner77 said:
Oh yes, many, many times! After I got stuck in a boot loop (or bootup system error), I wiped every partition I could find on the phone using stock TWRP and OUDH recoveries. Than I would odin multiple times using the MI3 tar. The odin process would be successful, but I would get stuck in a boot-loop every time. I'm fairly savvy with Samsung phones as I have rooted all 5 that I've owned but I couldn't figure this one out so I just took it back.
Click to expand...
Click to collapse
I did the same thing, finally gave up and took it back for an exchange...( had my sad story all figured out.. :cyclops It felt like it should of been an easy fix but I could never figure it out...
same issues...
jauger said:
I did the same thing, finally gave up and took it back for an exchange...( had my sad story all figured out.. :cyclops It felt like it should of been an easy fix but I could never figure it out...
Click to expand...
Click to collapse
I have similar issues. I tried to recover my original TWRP backup and now my phone is in a boot loop. Even taking the original system and restoring it via ODIN won't fix this?
No questions asked by the store?
derail412 said:
I have similar issues. I tried to recover my original TWRP backup and now my phone is in a boot loop. Even taking the original system and restoring it via ODIN won't fix this?
No questions asked by the store?
Click to expand...
Click to collapse
I'm 99% sure that's what killed mine....TWRP restore. I told the store I woke up and my phone was boot looping. No further questions asked.
Sent from my Note 3 on Android
derail412 said:
I have similar issues. I tried to recover my original TWRP backup and now my phone is in a boot loop. Even taking the original system and restoring it via ODIN won't fix this?
No questions asked by the store?
Click to expand...
Click to collapse
All I said was a System Update notification popped up, I clicked OK and it went into a full on boot loop.....
jauger said:
All I said was a System Update notification popped up, I clicked OK and it went into a full on boot loop.....
Click to expand...
Click to collapse
Did you by at Sprint or BB or some other retailer? I'm afraid that I'm SOL as I bought from Sprint.
derail412 said:
Did you by at Sprint or BB or some other retailer? I'm afraid that I'm SOL as I bought from Sprint.
Click to expand...
Click to collapse
The Sprint store is not going to have the software to restore your phone yet. So they will replace it as they want even be able to tell its rooted...Well unless they go into download mode which i don't see why they would do that right now. .. BUT This is something you can fix yourself. From what i read you only flashed the stock TAR once. Flash it again and see what happens. Pay attention to what you are restoring. The first time i rooted i couldn't make phone calls...I have no idea what cause it. Now i am on Stock but mi3 as i forgot to pull the SD card.. And its not that serious to go to mi5 at this point.
Edit: If stock still dosent work after multiple attempts.... GO ahead and flash stock rooted ROM. In the next week or so everything will be figured. out. There want be any big updates that you miss in the next month. I wouldn't worry about being on stock rooted or stock unrooted. All the same for now.
I've retried several times with the STOCK unrooted tar. No go with that. Just boot loops...
I didn't see where there is a stock rooted ROM. I'll look in the development areas for it. If you have link would you reply with the link?
derail412 said:
I've retried several times with the STOCK unrooted tar. No go with that. Just boot loops...
I didn't see where there is a stock rooted ROM. I'll look in the development areas for it. If you have link would you reply with the link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2472664
Got it thanks!
No Luck...
jauger said:
All I said was a System Update notification popped up, I clicked OK and it went into a full on boot loop.....
Click to expand...
Click to collapse
derail412 said:
I have similar issues. I tried to recover my original TWRP backup and now my phone is in a boot loop. Even taking the original system and restoring it via ODIN won't fix this?
No questions asked by the store?
Click to expand...
Click to collapse
dallastx said:
http://forum.xda-developers.com/showthread.php?t=2472664
Click to expand...
Click to collapse
I downloaded the ODEX'd and Deodexed STOCK rooted ROMs and neither worked for me. I am at a loss for what to do. I'm not sure if I wait I'll have any better luck. I am so frustrated at this point...
I do appreciate your help. Thank you.
derail412 said:
I downloaded the ODEX'd and Deodexed STOCK rooted ROMs and neither worked for me. I am at a loss for what to do. I'm not sure if I wait I'll have any better luck. I am so frustrated at this point...
I do appreciate your help. Thank you.
Click to expand...
Click to collapse
Still bootloop?
Sent from my SM-N900P using Tapatalk 2
Sprint store....
Sent from my SM-N900P using xda app-developers app
Yes... still boot loop.
derail412 said:
Yes... still boot loop.
Click to expand...
Click to collapse
Just out of curiosity reboot your phone then press and hold the menu button when the Sprint boot screen pops up on reboot..see if by some weird chance your phone boots into Safe Mode...
jauger said:
Just out of curiosity reboot your phone then press and hold the menu button when the Sprint boot screen pops up on reboot..see if by some weird chance your phone boots into Safe Mode...
Click to expand...
Click to collapse
Wow just did this in my note 2 and it worked. Booted into safe mode. . Didn't know the phone had a safe mode. . Do you know what the difference is. . I didn't see my apps.. anything else?
Sent from my SPH-L900 using Xparent Purple Tapatalk 2
Need a bit of help. Stuck in a boot loop. I had Freeza's deodex running like a champ. Flashed TeamVenum's rom and it ran good, but I didn't like colors. I wiped data and reflashed freeza's, and the system would only boot to update apps then reboot and start a boot loop at samsung.
I finally did a odin restore to MI3, but it won't boot up either. It updates apps then does a Finalizing boot, the system freezes then starts a boot loop.
Any Suggestions? Tempted to take it back to Sprint.
mid3vil said:
Need a bit of help. Stuck in a boot loop. I had Freeza's deodex running like a champ. Flashed TeamVenum's rom and it ran good, but I didn't like colors. I wiped data and reflashed freeza's, and the system would only boot to update apps then reboot and start a boot loop at samsung.
I finally did a odin restore to MI3, but it won't boot up either. It updates apps then does a Finalizing boot, the system freezes then starts a boot loop.
Any Suggestions? Tempted to take it back to Sprint.
Click to expand...
Click to collapse
Odin should have fixed this.
Did you flash in PDA mode and un-check the "auto reboot" ?
Try downloading the restore tar again, maybe you had a bad download.
tt281gt said:
Odin should have fixed this.
Did you flash in PDA mode and un-check the "auto reboot" ?
Try downloading the restore tar again, maybe you had a bad download.
Click to expand...
Click to collapse
I didn't have auto reboot unchecked, i'll take a look.
As for bad download, i've tried 3 downloads of it
This happened to me as well. Had to switch my phone
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
schnergun said:
This happened to me as well. Had to switch my phone
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Exactly what I did yesterday. Swapped for another, tempted to root again to get my data back but like the phone too much to risk it again.
how did u do the swap...Sprint Store...Service and repair...or Asurion...???
ronny71 said:
how did u do the swap...Sprint Store...Service and repair...or Asurion...???
Click to expand...
Click to collapse
Sprint Store, within 14 days from purchase
Ur phone is bricked. Restore doesn't work, once u did that, u turned your phone into a $700 paperweight. So if u get a new phone and root it, do not do a restore of any kind
Sent from my SM-N900P using xda app-developers app
I installed a rom, got into a bootloop that wasn't working. I attempted to use odin to flash to factory, but now I get the "firmware upgrade issue" screen when powering on or recovery mode. I can get into download mode, but I keep getting fail when I try to get back to stock. If anyone can help me I would really appreciate it since I just got my note yesterday and want to get it working again (even on stock.)
note: I read for at least 2 hours and tried almost everything. My drivers are installed. New usb cord/port. Reboot computer etc.
hobokenshmo said:
I installed a rom, got into a bootloop that wasn't working. I attempted to use odin to flash to factory, but now I get the "firmware upgrade issue" screen when powering on or recovery mode. I can get into download mode, but I keep getting fail when I try to get back to stock. If anyone can help me I would really appreciate it since I just got my note yesterday and want to get it working again (even on stock.)
note: I read for at least 2 hours and tried almost everything. My drivers are installed. New usb cord/port. Reboot computer etc.
Click to expand...
Click to collapse
Need more info to be able to help....what firmware were you are before you flashed via Odin? We you rooted? Did you have custom recovery installed? What firmware version did you attempt to flash with Odin?
I was on the stock 4.3 firmware, rooted the phone via odin, everything went smoothly. Then I downloaded a rom for sprint note 3, when I rebooted (cleared cache and factory wipe) the samsung logo just kept popping up and rebooting. I was using clockworkmod, but now when I try to access it I just get the "firmware upgrade encountered an issue." ODIN just keeps failing no matter what I try. I am trying the latest N900P stock firmware.
is it time to throw in the towel and see if Asurion can get it replaced? or at this point is it fixable?
hobokenshmo said:
is it time to throw in the towel and see if Asurion can get it replaced? or at this point is it fixable?
Click to expand...
Click to collapse
What exactly is the file name of that which you are flashing in Odin?
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
What exactly is the file name of that which you are flashing in Odin?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I realized that I am an idiot and was using a different model number and downloaded MJ4, worked like a charm. But now I want to get to the root of the issue (pun intended.) Why did the rom I used start the bootloop that was not fixed by clearing the cache and factory wipe? I found it right here on the sprint note 3 section of XDA. It was the MINIMUS rom.