Related
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
lonoguge said:
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
Click to expand...
Click to collapse
Where did you get twrp?
lonoguge said:
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
Click to expand...
Click to collapse
What is "another rom"?
lonoguge said:
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
Click to expand...
Click to collapse
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
bhundven said:
Where did you get twrp?
What is "another rom"?
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
Click to expand...
Click to collapse
I got it from what I thought was the official XDA TWRP thread but I'm not sure if it was official or not
at first I tried reinstalling codename but now I'm trying Beam (Tuk edition) and it seems to be working
TWRP Major Boot Loop
hey guys, im new here and i desperately need help with my phone!
the other day i was flashing a rom on my samsung galaxy s 4g. Things were turning out fine, until i had some complications on my phone.. so, i removed the rom. when i rebooted my phone, it went directly into the team win recovery project boot loop and every time i try to reboot my phone, it goes into the twrp. I also can't wipe anything and i can't delete anything! Does anybody know how I can solve this or is my phone basically bricked
more details would be helpful..
As in what rom, or what kernel.... etc... and make sure you have the corret phone.
Same problem with t959p
Looks like I'm not alone.......here's my story
the other day I wanted to switch from a stock rom to a custom, so I flashed redux 1.3 which was actually a froyo rom, and it started draining my batt like crazy so I flashed another rom on top of the froyo rom not realizing what I was doing and somehow messed it up cuz now it will only boot into recovery.
Now just to be clear I know this was my fault, I know I should have odin'd back to stock first, but I wasn't thinking at the time.....Ohh and just so you know I've flashed this sucker hundreds of times and was always able to get out of any mess I got in.
So here is the situation as it stands now, 3 button combo to enter download does not work. I can only get it into download with the jig I made. the problem is even in download mode none of my pc's will detect the device as a Samsung composite device, so odin will not see it. I've installed every possible 32 n 64 bit driver I could find including reinstalling kies. Kies wont even see it. I've tried flashing a few roms that I know worked and still it just boots into recovery. Now one thing I'll tell you is that depending on which rom I flash I can get recovery to switch from cwm to twrp. right now I left it with cwm 6.x.
what I need is a cwm flashable stock telus t959p rom complete with bootloaders or at the very least a cwm flashable zip file containing the bootloaders to see if I can recover the phone.
ohh and if your thinking about telling me to google search for the answer then don't bother.......I've spent the last 4 days reading posts and going to different websites and repositories trying to find something that would help me and so far nothing has.
the only thing that might work as a last resort is pushing the bootloaders as per one of raver's or whitehawks posts but it's a little more complicated for me as I would have to set up a laptop with Linux as I don't think i'll be able to pull it off with any of my windows pc's, win7 and win 8 only.
so if anyone has the files I need or can make them please let me know....or if you think you have another solution I could try i'm all ears err eyes.
thanks
Jedi
Have you tried heimdall one-clicks? Maybe it's showing up as gadget or something like that. I've had luck using zadig and heimdall to bring it back from the brink of death.
http://forum.xda-developers.com/showthread.php?t=1358498
EDIT
Woops replied to the wrong thread .
Nothing to see here, move along
Would like to revive a slightly dead thread.
I upgraded to a Galaxy S3 and no longer use my SGS4G for daily use. I had AOKP and disliked it, FC's and didn't like the feel. I have been trying to install a new rom ( old rom, VH Black Ed. ). Every time It loads into TWRP I have the ability to select the zip, install, it says complete, but reboots right back to TWRP menu. I've tried flashing CWM and it will install, flash the rom, reboot, and right back to this TWRP B.S... what am I doing wrong? I want to continue to use this SGS4g for music and internet duties.
How can I install CWM and have it stay even after a reboot? This TWRP is starting to me off
Did you happen to one click to stock before you went ham at the recovery?
Sent from my SGH-T959V using Tapatalk 4
I have a Galaxy S Vibrant i9000M. Yesterday I decided to install CyanogenMod (I had stock on there previously), following the guide on the CM wiki (wiki (dot) cyanogenmod (dot) org/w/Install_CM_for_galaxysmtd). After successfully completing the section on installing ClockworkMod Recovery, I realized I had neglected to move the CM .zip file to my SD card. I tried to start my phone and it is now in a boot loop. I have access to Download mode, but not recovery mode. What steps do I take (ideally with Odin) to revert back to stock?
Ideally, I'd come out of this with CM installed and working well, but I'd be happy to just get back to stock at this point. Any help is appreciated!
shameless bump
rUncle said:
I have a Galaxy S Vibrant i9000M. Yesterday I decided to install CyanogenMod (I had stock on there previously), following the guide on the CM wiki (wiki (dot) cyanogenmod (dot) org/w/Install_CM_for_galaxysmtd). After successfully completing the section on installing ClockworkMod Recovery, I realized I had neglected to move the CM .zip file to my SD card. I tried to start my phone and it is now in a boot loop. I have access to Download mode, but not recovery mode. What steps do I take (ideally with Odin) to revert back to stock?
Ideally, I'd come out of this with CM installed and working well, but I'd be happy to just get back to stock at this point. Any help is appreciated!
Click to expand...
Click to collapse
I would search the forums under your model and find the latest kernel since you must have already rooted it. Download the tar file and flash with Odin in download mode using the PDA selection.That should give you Clock Work Mod recovery again. Good luck:laugh:
By some miracle I figured this out myself. I didn't root it, but must have confused some cache. I got it to connect to odin (it didn't originally) by reinstalling Samsung Mobile USB drivers. I flashed GB 2.3.3 to it from http://forum.xda-developers.com/showthread.php?t=1102881 and from there it booted and was able to factory reset to restore full functionality.
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
HoPi` said:
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
Click to expand...
Click to collapse
Download a clean copy of Odin and install .
Auto Reboot is normal .
Root and Recovery TWRP
http://forum.xda-developers.com/showthread.php?t=1851548
Root and Recovery CWM
http://forum.xda-developers.com/showthread.php?t=1831173
jje
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet. But since this is getting off topic, I might be better off asking in other threads.
Thanks anyway!
HoPi` said:
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet.
Click to expand...
Click to collapse
Then you are not understanding instructions .
What is your intention .
Root or flash a stock rom .
Root via either method i posted .
Stock rom direct flash tar file via Odin.
ODIN flash is a tar not a zip.
Custom rom via a rooted phone with recovery zip file from ext sd card or sd card .
jje
Come on, the instructions are pretty clear boot in Odin Mode, click a button in Odin, let it restart, finished. The SuperSU zip file is from another guide, where the tar-file didn't include it. So I tried to manually install it via CWM (I think it was 6.0.2.7 or 8), but that didn't work either. Whenever the device reboots, Root Checker Basic runs for a few minutes and says "Sorry, the device does not have proper root access". If it helps, I used this guide:
http://www.android-hilfe.de/root-cu...ly-root-fuer-anfaenger-n8000-n8010-n8020.html
Even though it's in german, the screenshots are pretty obvious.
Sorry never ever seen any method with those sort of instructions.Personally not a clue what they mean .
I have used two methods as posted to root note 4 or 5 times. Rooted standard Samsung phones with cwm and root hundreds of times without any of those instructions.
Even run one standard cwm root via Odin to allow a specific rom install followed by a reroot using TWRP this afternoon .
jje
Sent from my GT-N8010 using xda premium
Thanks to Darkman, I finally got it. The problem was the current firmware update from Samsung. I reflashed with the version from January, followed his tutorial (like I did before - wow, after doing this 3-4 times, it certainly becomes second nature), and BAM, the device is rooted. Thanks anyway JJegan
Hello All,
First, I apologize for the fact that I am a long time (years) lurker and this is my first ever post. I have prior experience with rooting and installing custom roms on my samsung moment, moto droid (original), HTC droid incredible, moto droid X, samsung fascinate, samsung galaxy nexus, and samsung galaxy s4. All were successful with minimal issues. Here's my current issue...
I have had my S5 for several months and finally decided to root it. My first attempt was to leave it on the stock 4.4.4 OTA that I had and attempt to Odin CF-Auto Root. This resulted in a "FAIL" during the flash at the cache.img.ext4 phase. Subsequently I tried every version of Philz and TWRP I could find with the same failure.
Then I did an Odin of full ANK that I found on SamMobile's site. This was successful. So I tried ALL of those recoveries on top of that flash. All failed. I tried reflashing the whole tar ball in between and I tried several recoveries back to back without the tar ball in between. I tried it both ways.
Then I flashed the new NKD build that is out there. This was successful. Then I tried every single on of those recoveries (including CF-Autoroot) on top of that an all failed. In between EVERY one, I have tried flashing back the full NKD tar ball.
I even tried the packages that someone put out which include the firmware and either Philz or TWRP. I tried both. Both FAIL in the same way on Odin.
Now when I try to go back to the ANK tar ball, it hangs in a boot loop on first boot. I don't care, I don't want ANK, I am just sharing the facts. It's back on the NKD leak now.
Every flash is done on my macbook pro running windows 7 in WM ware fusion. It's always done by entering download mode from a battery pull.
I have also tried repartitioning during some of these flashes with a PIT file I downloaded. NONE of this helped. My phone runs with the NKD leak on it, but I want root and I want a custom recovery.
My goal is to have a custom recovery and full root so I can go back to flashing custom roms. Yes I have already tripped my knox counter, and no, I don't mind. Can anyone help me get this thing rooted with a custom recovery on it?
Thanks in advance!
Use heimdall for mac or find a real Windows pc if you want to use odin.
That's right, I forgot to mention, I tried Heimdall to flash just the recovery and that fails too!
Since we've had a couple new firmwares and lots of other stuff going on in the last several weeks, I've probably used Odin 30 or 40 times so I'm thinking a cable or try a different pc.
And by the way, when I run the command as follows:
heimdall flash --recovery recovery.img --cache cache.img
I get the following:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
I HAVE tried another cable, but not another computer. No idea why it would flash full tar balls fine, but not work with just a recovery... EVER.
In terms of Odin, I should also mention that I have tried 3.07, 3.09 and 3.10. I tried to troubleshoot everything that I thought could be the culprit.
I understand that you're pc won't work with all tars & that a different pc may not be an option. If you are somehow able to flash ne5, you can follow the steps below without using computer the rest of the process to get root & custom recovery. I've done this method on 3 S5s so it's a sure thing & takes less than 5 mins after your on the ne5 bootloader.
1. flash ne5 full tar with odin
2. download towel root, install and run to gain root (Make it rain)
3. Install supersu from play store
4. Install flashify from play store, grant root access
5. Download recovery IMG (Make sure it's IMG and not tar or zip) twrp here >> http://techerrata.com/browse/twrp2/klte
6. Open flashify for root users and select recovery image, navigate to twrp or philz custom recovery you downloaded and flash within the app
7. Open supersu and follow steps to update binaries, phone will boot to recovery and complete the update then reboot automatically
8. Enjoy your rooted device and flash away!
This is awesome and worked perfectly. I had thought about trying to do something of this nature, but could not have pieced it together so flawlessly. How do I send a donation your way?
The last issue is now I am on NE5 baseband. Is there any way to get to ANK or later?
syntheticreality said:
This is awesome and worked perfectly. I had thought about trying to do something of this nature, but could not have pieced it together so flawlessly. How do I send a donation your way?
The last issue is now I am on NE5 baseband. Is there any way to get to ANK or later?
Click to expand...
Click to collapse
I'm no dev so I don't have a donation link set up. I do have a PayPal account I'll pm to you. I'm glad I was able to help get you up and running, I know what it's like. I have a Mac myself and no pc but was always afraid to try running a vm. Good to know that it's an option now
Sounds good. I figure I ought to buy to you a beer for the help!
I like beer ?
Glad you solved you problem. Its shows like you was downloading from rwilco12 site. All are bad.
Also if you want to try Philz, these is the real link.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/klte/
Sent from my SM-G900P
I have a Rogers Infuse 4G (i997r) and I have been trying to upgrade it to kitkat by using a unofficial Cyanogenmod rom. More recently have been trying to use Carbon rom to update it. I have been running into problem after problem, error after error and I have finally decided to post something on XDA in hopes that someone with more experience can help me out. More information about the errors and what I have done to the phone below.
About a year ago I got this Rogers infuse 4G from a friend. I messed around with it for a bit but what I really wanted to do with it was install a custom rom and update it to a more recent version of Android (It started out on gingerbread (2.3)).
I had a real hard time getting modified recovery 3e because there was not original recovery file in system>bin to replace.
I forget most of what happened but it ended with me using a application to convert the cwm recovery zip to a md5 because I couldn't get modified 3e to work.
I tried using odin to flash the files I made but odin got stuck (or was just taking forever) and I unplugged my Infuse.
The infuse was bricked and would only show "firmware upgrade encountered an issue please select recovery mode in kies and try again". The phone would'nt enter recovery or download mode. It was recognized by odin but seemed as if it was not responding.
About 3 days ago I finally decided to try to unbrick the phone again (I don't know why just felt like it) and I found GTG ultimate unbrick with a pit file. I tried uploading this using odin and the phone responded and downloaded the files.
The phone showed a AT&T splash screen and then the Samsung logo. It hanged at the Samsung logo for about 3 minutes then would turn off reboot, show the AT&T splash screen then the hang at the Samsung logo for 3 minutes again.
I decided that I didn't actually need to install working android because I just needed CWM Recovery and found a CWM Recovery that was flashable with odin.
Now that the phone would actually show a splash screen I could access download mode and the stock 3E recovery.
I went to download mode and flashed CWM Recovery 6 - Voodoo Lagfix with odin
In the CWM Recovery I clicked install update.zip
The phone said installing and when it finished it rebooted.
It showed the AT&T logo and then the Samsung screen then it started talking (which btw scared the **** out of me) and it said installing voodoo lagfix, estimated time remaining 2 minutes
After it was done installing it rebooted and I had the same problem as before. It would show the AT&T logo then hang at the Samsung screen for 3 minutes.
I reflashed the GTG unbrick with odin then I reflashed the CWM Recovery and I was back into the recovery. (It wouldn't just let me boot into it I had to reflash it which was weird)
This time instead of clicking install update.zip I installed the Cyanogenmod-11-infuse-4g-unofficial-2014(some build number).zip
I got (status 7) installation aborted.
when the phone rebooted it showed a cyanogen mod loading screen and I got really excited
after the loading screen it went straight to proper CWM Recovery then it instantly crashed with a little fallen over Android and a red triangle over it.
It kept boot looping like this so I asked for the unbrick files for a Rogers Infuse 4G and installed those.
Once I installed the Rogers Infuse 4G Rom I set it up but I ran into the same problem I had last time.
I can't install the modified 3E recovery because the recovery file is not system>bin. CWM Recovery also fails to install even though it says it has installed.
It turns out the recovery file is on the root of my phone not /system/bin
Im not really sure what to do and guidance would be appreciated.
It's because the CWM is not only device specific, but carrier specific (at least for the Infuse).
Flash the following file (extracted) with Odin. It will talk to you as well after reboot, but it will give you CWM red which you can use to move on to custom ROMs:
https://www.dropbox.com/s/t0kc92124jat6yt/CWM Infused Kernel.zip?dl=0
Be sure to disable Voodoo Lagfix before installing any ROM's, especially if shortcut'ing directly to CarbonROM (versus installing CM9, then CM10.1 and finally a KitKat ROM).
Good luck, let me know if you have any questions.
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error. Accidentally Double Posted... Im a noob. If someone could delete this repost it would be appereciated
OnfireNFS said:
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Click to expand...
Click to collapse
Just to be clear. With the original ROM file, did you try installing the ROM with this CWM and Voodoo Lagfix disabled? That is go into CWM's options menu, and disable there?
Just trying to pick the low hanging fruit, unfortunately I don't know where to go from there (as this is my only idea now, besides re-downloading the ROM).
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
OnfireNFS said:
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
Click to expand...
Click to collapse
It used to be that in order to get from Gingerbread to say, Jellybean, you needed to install the Ice Cream Sandwich ROM (CM9) first. This gives you a relatively new CWM in order to do your bidding. But you man need to install a Jellybean ROM (I suggest CM10.1) in order to get a CWM that will like the installation of KitKat.
So Stock (Infused CWM) -> CM9 -> CM10.1 -> CarbonROM 4.4.4
Of course, I did say used to. Apparently if you disable Voodoo lagfix in CWM you can go straight to CarbonROM. I never tried it, but it is worth a shot (avoids having to go on a scavenger hunt).
But if you already tried it with no success, now you know the classical way.
Thanks a lot. By upgrading to cm9 then cm10 then finally Carbon Rom I was able to get the phone to kitkat!
Cheers