Well I am truly stumped, I'm not new to flashing phones I've been flashing rooting and repairing androids for 6 years but have never seen this happen. Came across a tmobile t889 note 2 that had Jedi Master on it and it was bootlooping. (not sure which jedi master I think x2) first I tried to boot into recovery, saw the twrp logo then it just rebooted went back to booting jedi. So I tried to reflash twrp through odin... Nothing, same thing. So then I tried to flash cwm, odin said success no errors but goes right back to twrp, tried philz, same thing. Tried the stock 4.1 rom, 4.3 rom basically every stock rom available, each time odin says success and yet each time jedi master and twrp remain. I tried every single version of odin from 1.85-3.12. I just don't know what else to try, I can't find any threds with even a similar problem except one from an s3 and the solution was only return to samsung... Anyone have sny ideas? Note:it's s not a power button issue the phone doesn't turn off when booting jedi master just syayscon the jedi master bootscreen indefinitely.
Just an update my problem remains, but I found the t889 pit that didn't work, tried to uncheck auto reboot and manually reboot that didn't work. Gave up on odin and tried heimdall with both the command line and the user interface, same thing flashed successfully but nothing really flashed. If anyone has ever used the windows program "deep freeze" It seems like as if that's what happened to the phone... No matter what you flash it just reverts back. I even went as far as trying to purposely brick it by flashing an impropper kernel, I know what that would have done but I just had to see, but nope... Didn't brick... Did nothing... Still has twrp still has jedi master still boot loops
If anyone is interested in seeing a visual of the problem I made a video https://www.youtube.com/watch?v=W3zL069w8io
were you able to solve this?
Just went through this
I was changing roms
And this happened.
Odin the latest Twrp for your phone and do all the rules
Flash the exact Rom that was on it before.
That worked on my t889
You'll probably get partition mount problems..wasn't an issue for me....couldn't flash anything but that Rom.
I'm on jedi x2
It probably had a dual boot
Related
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
mozphoto said:
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
After flashing through odin did you format data?If not try it.
Go into recovery and wipe data.
**SOLVED**
Thanks xXFl4sh, I had tried that.
Solved!
Alright where do I start? How about RTFM Some how I had missed the part about flashing a bootloader and a modem after the ROM. Not recalling having to do that before, I skipped right over it. Once the recovery CWM 6.0.3.1 was finally loaded, getting the flashing the ROM, the bootloader and the modem was easy as usual.
The key was having to use Odin to install a recovery in .tar or .tar.md5 format since I could not access a Recovery Mode on the GS3, as well as a rooted stock image (I used root66_ATT_I747UCDLK3.tar.md5 which is a rooted Android 4.1.1 for AT&T) For the recovery, I couldnt' find a .tar or .tar.md5 for ClockWorkMod (did find a utility to convert it, but didn't want to introduce another variable into the mix) so I used one from Team Win Recovery (v2.6.3.0) and with that I loaded the CWM recovery. Once all of that was in place, I proceed to factory reset, clear data, cache, system and then flash the new ROM, bootloader and modem.
In all of this I learned quite a bit about the whole process and how to narrow down possible resolutions. I still see the "Rom may flash stock recovery on boot" message after flashing either a ROM, bootloader or modem, but just backing out without answering Yes or No seems to work. Also (and this may be related, I don't see the option to restart in recovery from shutdown menu). Don't really know what that's all about for now, and honestly don't want to mess around (at least for a while)
I know the steps are general, but I hope this can help some else if they get their devices in a soft brick situation. As for the i747z v3 ROM with 4.3, I really like it, everything works (Wifi,Blutooth,tethering) and the battery seems good as well.
Thanks!
The background story: Was having a lot of FC issues with Beanstalk 4.4, along with other things like battery life/signal that I was growing to be unhappy with and decided to flash one of the 4.3 ROMs with Note 3 features on the fly. I didn't have signal after doing so (didn't read all the comments so I do know this is all my fault) and thought that I would have needed to flash the 4.3 bootloader that was suggested in the OP since using the modems I had on hand did not help.
End result, phone was perpetually stuck in bootloop.
Symptoms: Doesn't go past the Samsung splash screen with the logo flashing. Even when plugging it in it's stuck on the empty battery with the loading wheel.
Attempted solutions:
I have tried the EFR attempt but could not get Kies to recognize my Note II in downloading mode. Kies is currently updated to the lastest 2.6.1.x.x.x
The emergency code option isn't viable since I don't have one(?)
Flashed the appropriate stock ROM (for Bell SGH-I317M) through Odin as it was recognized, but still cannot get past bootloop.
Tried firmware upgrade and initlization instead, PC cannot download firmware to device
Attempted to flash other ROMs both stock and whatnot through CWM. Doesn't seem like it'll take anymore AOSP mixed/based ROMs as they all fail?
With all of these attempts I have pulled out the battery for a little bit prior to actually performing the restoration.
Hopefully somebody can point out a mistake or something I need to do instead.
And as a side note, the Galaxy S2 is too damn small and Windows phones (Lumia 1020) kind of....suck.
Bump. Hopefully somebody can point something I missed.
Have you tried Odin to stock then wiping all user data/ factory reset?
bbrennan said:
Have you tried Odin to stock then wiping all user data/ factory reset?
Click to expand...
Click to collapse
Attempting to wipe anything other than cache in CWM gives me an error mounting.
If you Odin to stock it would have factory recovery on it, not cwm, Odin to factory then under stock recovery wipe data factory reset
bbrennan said:
If you Odin to stock it would have factory recovery on it, not cwm, Odin to factory then under stock recovery wipe data factory reset
Click to expand...
Click to collapse
You sir, deserve the rest of the day off with a pat on the back and a beer in hand. Many thanks!
Okay here is the problem guys. I have my note three for three weeks now. Rooted it day one. But It seems with every phone I have addiction with flashing roms. I change around a lot. I have owned four devices this year. S4, note 3, nexus 4 and galaxy nexus. Rooted every device never had an issue that couldn't be fixed by flashing the stock tar via odin. The other day I flashed compulsion kernel and put me in a boot loop. So I did the natural thing and download the stock tar and flash via odin. First time was a bust. It said it was successful. Still put me in boot loop so I downloaded the stock tar from another location and tried again. Still no dice and still have boot loop. Tried flashing a custom rom after flashing the stock tar. Nothing still boot loop and I've also tried different recoveries and still nothing. I know its not hard bricked because I can still boot into recovery. I am actually a sales rep at a corporate tmobile store and did a warrarnty exchange and they are overnighting me another note three and I am going to send this one back. Little concerned as to having the rooted status on the device is going to go over. A couple times after I flashed the stock tar I got it to boot but then it would say "process system stopped responding wait or ok" then after clicked okay it reboots. I really hope there is someone out there with a solution.
HELP
This isnt your usual soft brick. If someone could please help I would appreciate it!!
Dude my phone out of nowhere bricklooped today like literally. I installed different roms no dice. 3 backups including the stock one and nothing still bootlooped I tried the brickloop fixer on jovys darthstalker v6 and I'm back up and running but if I reboot or turn off phone and reboot it goes into same bootloop he's a smart, brilliant dev I'm sure he can help me out as well as you
Sent from my SM-N900T using xda app-developers app
So here's the back story. I'm usually good with roms/recovery/flashing. Even did some custom rom work on my old Galaxy S 4G, so not a noob. I have a Wind T999V.
Had Touch-CWM installed, ran a few 4.4 ROM's for a while, tried LP, Liquid smooth. Liked it ok, but wanted to try OctoROM LP. It needs TWRP. Had a few problems with TWRP before on my phone, the Wind variant seems somewhat different in small ways, but figured I'd give it a try again to flash OctoROM since it needs TWRP. Thought maybe the TWRP has improved since I tried last, so installed TWRP, tried to flash Octo, but TWRP wouldn't see my internal SD card at all. The same problem I had before. I didn't feel like digging out a SD card from my camera to put Octo on, so rebooted the phone, installed CWM back, rebooted again, got a bootloop somewhere along the way.
Figured I'd go with Odin back to stock and start over. Grabbed odin (hard now, lots of spam/scam copies) and my stock firmware for the Wind version from Doc's thread. Flash the tar, which took forever (used a sort of crappy cable) and it auto rebooted after like 20 mins of flashing, just stuck at the sammy logo for like 20 mins. Too long, still looped I think.
Grabbed a different cable and a newer version of a good odin I know from my network I had laying around, 3.09, and tried again. At the pulsing samsung logo again, going to wait, but if I did softbrick it, do I need to repartition and a pit file to get the FS back to something different than any of the KK or LP rom's I ran?
EDIT:
Read some threads and took doc's advice and booted into stock recovery and wiped data and cache, and it finally booted. Phew.
So my issue is pretty similar, see what you guys think. i been trying everything i can think of.
i updated from xtrestolite 2.1 to 2.2 with out wiping. everything worked fine except when i would make calls, the other people could not hear me. so i updated the bootloader and modem again (i had done it before) and the problem persisted. i flashed back to stock and was getting stuck at the s6 edge screen. the only way to get around this was and get my phone to boot was to flash aou kernel. i was still having a similar issue with calling so I download a modem from a diffrent server and all of a sudden, it was working again on stock firmware... AWESOME!
now that i had all that done and my phone working as it should, i reset my phone for the first time and i got the FRP lock, wont boot phone because custom kernel. GREAT
I then flashed stock of6 again, the tar ball, and the 4 piece version. no dice
i then found of8, tried to flash that still no dice.
id love to flash twrp and load a rom on, but FRP is a alsjdflajs.
the phone will flash successfully, but upon reboot, it will go into recovery, run its course, reboot, and get stuck that the galaxy s6 edge screen.
i use the vol and power click during recovery to see what its doing and everything seems to go fine. it will then say failed to mount /data. im hoping flashing this with the pit file will work, but i cannot download the pit file from my work computer (hahah its blocks on 4shard and mega).
anyone have any other advice? i will update if i figure it out.
Regards team,
-Mad
p.s. none of this is xtrestolite's fault, that rom has been nothing but good to me.. my phone has been picky though. after 5.1.1 i had to flash a custom kernel in order for the digitizer to function properly.... any help is appriciated guys.
SO UPDATE!
nothing good, i tried the pit with of6 and of8, no dice. still stuck.
anyone got a s6 edge w a broken screen? you can claim it lost for all i care.
no one?
i guess if anything past flash stock firmware people dont know? was hoping for alittle more insight.
im sure if i could flash a kernel i could get it to turn on, but FRP has be at bay...
no help for you bro...Samsung just needs to release there software fixing for this comunity...I'm looking a for a dev to answer my question in this section about just flashing zip files in twrp instead of using odin or whatever other methods that can avoid all these problems that are all similar...hopefully in next few months it will be addressed
Hey mate, try this...
http://forum.xda-developers.com/showthread.php?p=61531848
Sent from my SM-G925T using Tapatalk 2
holy... fu34%# /S45it.... IT BOOT?!
after flashing every firmware 100000 times...
THANK YOU!
I initially used odin to flash OI1 update, after a rom I was using caused problems and I got bootloop. It changed bootloader value to b:3 and I'm unable to downgrade now so I used smart switch which didn't recognize device so used emergency recovery and still bootloop. I have factory reset and wipe cache multiple times along with adb side load and individual flashes of bootloader, modem, kernel, flashed custom kernel and twrp to access fix permissions and to mount partitions with advanced wipe etc and still wont boot past logo. Also during one fix attempt phone said can't mount system.. Idk I'm not understanding where the problem is .everything says successful but I'm still in bootloop. Please help. I've spent hours everyday for the past week searching & trying different things that seem might help so open to any suggestions.