I flashed the T999UVDLI6 package to my phone but cannot seem to Root now. I have tried everything that used to work and Superuser will not take. has anyone else flashed and succeeded in rooting?
Here is how I got here:
I tried to update using CWM and it failed
I reflashed STOCK T999UVALH2 and then updated using Android Recovery and the full update worked
I have tried flashing via Odin 3.04 like always and the CWM mod will NOT take- all I ever get is the Android Recovery
Interestingly, if I try to flash Superuser from SD card using Android system recovery it gives me an :E:signature verification failed" message.
Any thoughts?
You must be fully stock and also have stock recovery... When I did it I used mobile Odin to keep root, and but you can use ota root keeper
Sent from my SGH-T999 using xda premium
ktetreault14 said:
You must be fully stock and also have stock recovery... When I did it I used mobile Odin to keep root, and but you can use ota root keeper
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
So because I had CWM recovery it failed?
Yea
Sent from my SGH-T999 using xda premium
Rooting after upgrade
Fonz said:
I flashed the T999UVDLI6 package to my phone but cannot seem to Root now. I have tried everything that used to work and Superuser will not take. has anyone else flashed and succeeded in rooting?
Here is how I got here:
I tried to update using CWM and it failed
I reflashed STOCK T999UVALH2 and then updated using Android Recovery and the full update worked
I have tried flashing via Odin 3.04 like always and the CWM mod will NOT take- all I ever get is the Android Recovery
Interestingly, if I try to flash Superuser from SD card using Android system recovery it gives me an :E:signature verification failed" message.
Any thoughts?
Click to expand...
Click to collapse
I've flashed and succeeded in rooting, I did the same method as you described. Except I'm using Odin 1.85 not Odin 3.04 :cyclops:
Also, did you try doing a full wipe? I didn't see that in any of your steps. Might want to try that if you haven't already.
Wipe-o-rama
fishguts said:
I've flashed and succeeded in rooting, I did the same method as you described. Except I'm using Odin 1.85 not Odin 3.04 :cyclops:
Also, did you try doing a full wipe? I didn't see that in any of your steps. Might want to try that if you haven't already.
Click to expand...
Click to collapse
Yes- I wiped everything possible (data/factory reset, cache partition, and Dalvik Cache) and Odin would not load it which is why I ended up using the Stock Loader. I will have another crack at it
Hmmm
Fonz said:
Yes- I wiped everything possible (data/factory reset, cache partition, and Dalvik Cache) and Odin would not load it which is why I ended up using the Stock Loader. I will have another crack at it
Click to expand...
Click to collapse
Okay, I retraced my steps and everything still works fine for me...so I did some things to break my phone a bit to see how this can fail, and came out with a few results.
Using Odin, uncheck the "Auto Reboot" option, I think this ROM will reflash to stock upon reboot unless disabled, it's a "feature" found in the Galaxy Tab 2 also. CWM 6.0 will take care of that, as they ask you to disable that "feature" upon reboot from CWM. Now, in order to get there, you need to go directly from Odin mode to recovery. So here's what I did exactly to get the results that you are asking for:
Using Team Win Recovery Project (TWRP Recovery), I wiped dalvik, cache, system, data, and factory reset, and then I opened Odin, unchecked "Auto Reboot" option, flashed T999UVALH2 back to stock, rebooted into android recovery, factory reset, reboot back into android recovery, flashed T999UVDLI6, and then rebooted into android recovery, did a factory reset, and rebooted into Odin mode, where I kept that same box unchecked, and flashed TWRP recovery. After it flashed, I unplugged my cable, and rebooted directly into the custom recovery where I flashed SU. Booted my phone and I have root access with JB. Now, if you don't want to use TWRP as your recovery, then you should use the latest version of CWM.
I was typing this as I was doing it, so I know for sure this works. At least, for my phone it does. Good luck and I hope this helps!
Awesome. Thanks for taking the time to troubleshoot for me. I will try today and report back
Sent from my SGH-T999 using Tapatalk 2
Please clarify
I am fully stock and using stock recovery and I am getting an error regarding :E:signature not being valid when I try to flash. I have applied OTAs that my phone received in the past. Dose this mean I need to revert back to the default firmware image also or is there a different issue? Thanks
I've been flashing OTA leaks with CWM. Both ICS and JB. I don't lose CWM recovery. This process is a lot easier than some people think. I have never needed stock recovery to update to the OTA leaks.
1) Stop using CWM v5. Its time to upgrade to v6.
2) Get T999UVALH2 on your phone. Whether you have UVALEM and use the official OTA update to UVALH2, or do a full install of it. You need UVALH2. I personally still had a UVALEM nandroid, so I restored then factory reset. Then backed up the clean install. Then I ran the OTA through the phone settings > About phone > Software updates. Now I had UVALH2. Guess what? Nandroided that, too.
Also, make sure you flash the UVLH2 modem if using another version.
3) If needed, get CWM on there through Odin. Or if you got a prerooted version, get CWM on there through other means.
4) Download the OTA update here: http://www.sammobile.com/firmware/?page=3&model=SGH-T999&pcode=TMB&os=1&type=1#firmware
5) Flash update with CWM. Upon exit, it will ask you about recovery and root.
Now you have the new leak, CWM recovery, and root.
CWM 6 did the trick. Still rooted and running JB
Sent from my SGH-T999 using Tapatalk 2
Related
Sorry for the somewhat long post, but I've tried a lot to solve this problem. So the other day, I tried installing the Paradox II Love ROM from Juggernaut 5.0 and followed its instructions exactly. I used both the Super Wipe and Kernel Cleanser and the steps that followed. After my phone rebooted, it would load the new kernel and then immediately reboot into recovery mode.
So after failing to work a few more times, I decided to try Darkside Digital Warfare. Again, the kernel would load, but then this time, it would just get stuck on the kernel logo. I waited over 20 minutes, and it did nothing. In the thread for the ROM, apparently a few people have had the same issue. A possible solution was installing a different kernel. I tried several, and it continued to have the same problem.
So I decided to use my nandroid backup, which didn't work. Something about an md5 mismatch I think. So I decided to try and reflash Juggernaut 5, and that ROM now wouldn't load. So I try GBaxeEX which I was using before Juggernaut and that just reboots to recovery.
So far, all that works are stock ROMs or ROMs that are close to stock. Right now, I'm using a debloated ROM and have no problems. I've found I can load custom kernels, so I'm using Darkside Xv1.
I've tried using Odin to go back to stock before flashing new custom ROMs, I've tried manually wiping system data in recovery before flashing, I've tried not using the Super Wipe, and I've tried redownloading the ROMs in case of an error or incomplete download. I've also tried initiating the install from ROM Manager. My phone just refuses to accept custom ROMs anymore.
Any advice is appreciated. I've been flashing ROMs since the Vibrant first came out and have never had a problem like this.
Try running tdj super wipe. Then flash your rom of choice. I highly recommend darkside rom!
Sent from my SGH-T989 using xda premium
GreggoryD502 said:
Try running tdj super wipe. Then flash your rom of choice. I highly recommend darkside rom!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Like I said in my original post, I did try the Super Wipe and have tried it multiple times since. I've also tried using the Super Wipe and formatting system data in recovery.
segata said:
Like I said in my original post, I did try the Super Wipe and have tried it multiple times since. I've also tried using the Super Wipe and formatting system data in recovery.
Click to expand...
Click to collapse
You may have to ODIN back to stock then re-root. After that get CWM and start flashing again. This should work.
What I learned from my Vibrant days. If everything else fails, Odin Stock and start all over again.
BTW. Small hint. Use ROM Manager to create a .zip for CWM, rename it update.zip. Doing this will allow you to go directly from Stock recovery (volume +/- and power) to flashing without Rooting the device. Just load stock recovery and install the created update.zip by selecting Install Update. First flash of update.zip will go back to Stock recovery, second will load CWM.
Raistline said:
You may have to ODIN back to stock then re-root. After that get CWM and start flashing again. This should work.
What I learned from my Vibrant days. If everything else fails, Odin Stock and start all over again.
BTW. Small hint. Use ROM Manager to create a .zip for CWM, rename it update.zip. Doing this will allow you to go directly from Stock recovery (volume +/- and power) to flashing without Rooting the device. Just load stock recovery and install the created update.zip by selecting Install Update. First flash of update.zip will go back to Stock recovery, second will load CWM.
Click to expand...
Click to collapse
Again, this was something I tried multiple times and was mentioned in my original post. I was able to fix the md5 mismatch error thanks to a few other XDA threads, so I've restored a previous backup for my Juggernaut 5.0 setup.
Update: Since restoring a previous backup, I've successfully flashed Darkside Digital Warfare. However, Paradox II still refuses to install.
I tried to flash rooted stock rom or stock rom, either will result me in stock in boot logo. Anyway for me to use odin to flash ccw or recovery so I can wipe before flash Odin?
Whanksta said:
I tried to flash rooted stock rom or stock rom, either will result me in stock in boot logo. Anyway for me to use odin to flash ccw or recovery so I can wipe before flash Odin?
Click to expand...
Click to collapse
you're the 2nd person with the same issue in the last 10 mins...i wonder wth is going on with the stock files or odin. I'll tell you the same thing I told another user ...If you used odin 3.0.7...trying using 3.0.4 instead. Another user did that and it worked...so hopefully you'll get the same results.
defnow said:
you're the 2nd person with the same issue in the last 10 mins...i wonder wth is going on with the stock files or odin. I'll tell you the same thing I told another user ...If you used odin 3.0.7...trying using 3.0.4 instead. Another user did that and it worked...so hopefully you'll get the same results.
Click to expand...
Click to collapse
I tried using 3.0.4 and it did not work, however i was able to flash CWM through odin so now everything is wiped clean. Hopefully stock rom will go through this time.
Edit: yup, that did it. flashing CWM was so crucial.
Whanksta said:
I tried using 3.0.4 and it did not work, however i was able to flash CWM through odin so now everything is wiped clean. Hopefully stock rom will go through this time.
Edit: yup, that did it. flashing CWM was so crucial.
Click to expand...
Click to collapse
you should post what you did here...help em out.
http://forum.xda-developers.com/showthread.php?t=1886634
SIMPLE FIX....
preform factory reset in recovery before (or after) flashing stock.
Stock odin flash does not flash or wipe data partition. and some files that you have in there become incompatible with older firmware and stop stock from booting.
NOTE!!!!! factory reset from STOCK recovery WILL WIPE SD CARD TOO!!!
CWM recovery factory reset WILL NOT wipe sd card... backup your pics and downloads!!!!
hey, what file did you use to flash cwm my problem seems to be nearly identical to yours please reply
chemisch said:
hey, what file did you use to flash cwm my problem seems to be nearly identical to yours please reply
Click to expand...
Click to collapse
Pretty sure he followed this....
http://www.androidauthority.com/galaxy-s3-sgh-i747-att-clockworkmod-recovery-99791/
Sent from my SAMSUNG-SGH-I747 using xda premium
YESSSS! so i ended up geting it to work after flashing cwm and flashing stock rom that was still in bootloop but then i got a custome rom onto external sd card and loaded that and i got it working so ****ing happy been all day i've been thinking my phones ruined
I installed paranoidandroid 3.96a today and I had some errors before I was able to install it so I ended up formatting the data and then clearing the caches.
I flashed PA. Then I flashed the latest google apps. Then I flashed PA again and rebooted. My phone loaded fine and I was able to install everything I want.
Then if I reboot my phone it get stuck on the splash screen and cannot load. If I go into TWRP 2.5.0.0 recovery it asks me for a password (I have not yet a password although I recently bought this phone used on swappa so I've contacted the seller to ask if he set a password). If I push cancel at the password screen then I can get into TWRP but if I go to wipe the dalvik cache it say sit "failed." The test printed to the console is:
Updating partition details...
E: Failed to wipe dalvik
Updating partition details...
I also cannot browse the internal memory of my phone. There is no folder named "android" or similar.
Any thoughts would be greatly appreciated. I'm going to try to update TWRP to the latest version. After that I'm out of ideas
Try the latest twrp like you said. Then you can also try cwm. Before you csn browse your file system in recovery, you have to mount system.
Id try another factory reset and reboot though. If thst doesnt help try another kernel. If youre still stuck, idin flash back to full stock with the root66 firmware, then start over clean from there.
Sent from my SGH-T999 using xda premium
how long do you let the phone sit after rebooting? I'm currently on the same rom and noticed it takes longer than usual to reboot the device. it's seems like it takes just as long to reboot the phone as it does to boot up the phone right after flashing the rom.
try letting the phone sit for 5-10 mins and see if it boots up. it's kind of ridiculous it takes that long to reboot a phone, but then again the rom is in alpha. I might try reflashing the rom to see if this still happens.
Just posted in the ROM thread to see if anyone else has the same issue.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Try the latest twrp like you said. Then you can also try cwm. Before you csn browse your file system in recovery, you have to mount system.
Id try another factory reset and reboot though. If thst doesnt help try another kernel. If youre still stuck, idin flash back to full stock with the root66 firmware, then start over clean from there.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried installing PA again and then upgrading TWRP to 2.6.0.0 but it still said that it had 2.5.0.0. Then I installed CM10.1 and used that to upgrade to TWRP 2.6.0.0 which worked. I then tried installing PA3.96a again with the same results.
I think that the problem is with TWRP not recognizing android 4.3 installs correctly because I have the same problem with CM10.2 that I had with PA3.96a.
I don't think the problem is that I'm not waiting long enough because after the first restart (i.e. I flash it and restart loading the ROM fine--then when I restart it for the first time it gets stuck). When I go into TWRP after it hangs the first thing it does is ask me for my password. I don't have a password. I think that something is happening to the system partition after install that makes TWRP unable to read it on this phone. Also it says that 0 MB have been used on my phone ram so I think the problem is with TWRP not being able to read the system partition in 4.3 correctly.
Has anyone gotten android 4.3 working on the t-mobile s3 yet?
Edit: And I can't restore from a nandroid backup (unless I put it on my SD card because the phone cannot read from the system partition).
Did you try mounting /system in recovery?
I would seriously consider Odin flashing stock root66 firmware before anything else at this point. Maybe something is corrupted in one of the underlying partitions.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Did you try mounting /system in recovery?
I would seriously consider Odin flashing stock root66 firmware before anything else at this point. Maybe something is corrupted in one of the underlying partitions.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yes I did. If I mount it I still couldn't see /android or any other folders. I could also not clear the dalvik cache or do a factory reset.
Okay that's the consensus. I'll try restoring to stock sometime this weekend and see how that goes.
I just reverted back to stock using Odin. Reset the counter to be safe and then used odin to load a rooted stock. Then I installed goo manager and had it install TWRP 2.6.0.0.
Success! I can install and 4.3. Something must have been funky with the previous rooting job or something. Who knows. Thanks!
Right on! Good to hear you got it running good!
Sent from my SGH-T999 using xda premium
same thing
so i basically have the same thing but with mine i installed hyperdrive rom and flashing the stock rom like you said doesnt work and doesnt get rid of hyperdrive so it just has the hyperdrive boot screen and i cant get to my internal memory ect. like him please help i cant have ruined my phone by the way im a noob so please be specific and give me links thanks
Did you install stock with Odin?
I installed stock with Odin. I then installed a rooted stock and used that to reroot my phone by installing goo manager to install twrp 2.6.0.0.
Let me know if you want me to get the links for you. I got them on xda from googling
Edit: Found it. I used this http://forum.xda-developers.com/showthread.php?t=1900345.
Downloading the stock took about an hour so I would go ahead and just use odin to install the rooted stock. After you install your phone will reboot and then it will hang on a screen with Samsung on it (or at least it did for me). You then restart your phone and go into recovery and do a factory reset. Then install goo manager and reinstall the recovery by clicking on the options/settings button and selecting "Install OpenRecoveryScript." Then you can download whatever ROM you want to install. Reboot and go into recovery and you can install it.
Sent from my SGH-T999 using xda app-developers app
links please
bmdubs said:
Did you install stock with Odin?
I installed stock with Odin. I then installed a rooted stock and used that to reroot my phone by installing goo manager to install twrp 2.6.0.0.
Let me know if you want me to get the links for you. I got them on xda from googling
Edit: Found it. I used this http://forum.xda-developers.com/showthread.php?t=1900345.
Downloading the stock took about an hour so I would go ahead and just use odin to install the rooted stock. After you install your phone will reboot and then it will hang on a screen with Samsung on it (or at least it did for me). You then restart your phone and go into recovery and do a factory reset. Then install goo manager and reinstall the recovery by clicking on the options/settings button and selecting "Install OpenRecoveryScript." Then you can download whatever ROM you want to install. Reboot and go into recovery and you can install it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
that would be awesome if you could i want to make sure i do the same downloads as you its so nice knowing im not the only one. im so screwed if i cant fix this
imfukked said:
that would be awesome if you could i want to make sure i do the same downloads as you its so nice knowing im not the only one. im so screwed if i cant fix this
Click to expand...
Click to collapse
Check your flash counter and if it's anything over 0 run Triangle Away to set it back to 0.
Then follow the directions in the stickied thread for directions on how to revert back to stock. I installed the latest t-mobile ROM from this thread http://forum.xda-developers.com/showthread.php?t=1771687
Just make sure you get the T-mobile versions
bmdubs said:
Check your flash counter and if it's anything over 0 run Triangle Away to set it back to 0.
Then follow the directions in the stickied thread for directions on how to revert back to stock. I installed the latest t-mobile ROM from this thread http://forum.xda-developers.com/showthread.php?t=1771687
Just make sure you get the T-mobile versions
Click to expand...
Click to collapse
Triangle Away only after you have stock kernel and stock recovery back on your phone. Otherwise it wont do you any good.
Odin flash the root66 firmware, triangle away, then full unroot from the supersu app.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Triangle Away only after you have stock kernel and stock recovery back on your phone. Otherwise it wont do you any good.
Odin flash the root66 firmware, triangle away, then full unroot from the supersu app.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
how do i check my triangle and triangle away it ohh and my odin doesnt have pda it has bl ap cp csc
imfukked said:
how do i check my triangle and triangle away it ohh and my odin doesnt have pda it has bl ap cp csc
Click to expand...
Click to collapse
Reboot your phone and instead of pushing volume up to put it into recovery mode push volume down to bring it into download mode. This is also what you use to revert to stock via odin.
IT WORKED
HOLY **** IT WORKED I HAVENT HAD MY PHONE FOR A WEEK I THOUGHT I WAS SOO SCREWED YOU SAVED MY ASS THANK YOU SOOOOOOO MUCH!!!!!!!:laugh::laugh::laugh::laugh:
My understanding is that it's actually kind for of hard to brick your phone from doing software modifications. It is possible but I think only if you really screw something up. Like powering down while installing a recovery or something.
Sent from my SGH-T999 using xda app-developers app
Unplugging in the midst of a firmware flash, and flashing the wrong models firmware are the easiest ways people hard brick.
If you can get download mode and recovery to boot it can be fixed most of the time.
Sent from my SGH-T999 using xda premium
Yeah what happened with me is I downloaded hyperdrive to my internal and this was my first time and I didn't install cwm or anything like that so I did the factory reset and cleared cashe but then I relized there's no way to clear your dalvik and or launch hyperdrive so I tryed booting my phone and it got stuck on the samsung logo everytime so I used odin to put cwm on my phone and I couldn't access my internal or clear dalvik so I used an external and used my old galaxy s2 to download hyperdrive on to the external and then launched it on my s3 and it installed great it let me choose everything but when I went to launch the phone it got stuck on the hyperdrive boot animation so I tryed like 10 stock roms none of them worked it wouldn't get rid of the hyperdrive boot animation iether so then I was sher the link you gave me wasn't going to work but unlike the other odin ones I did it took time instead of only taking half a second and it worked
Sent from my SGH-T999 using xda app-developers app
So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.
Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.
To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.
Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement
GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)
My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.
You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.
In all my previous posts requesting help of why my phone wont boot 4.4.2 ive never gotten a clear answer or any troubleshooting steps.
when i flash 4.4.2 with any recovery it goes to rom logo and doesnt boot past that. the only rom ive been successful with flashing is omni rom. whats the difrence between omni rom and any other regular 4.4.2 rom/
all i want to do is use carbon kk i had 4.4.2 working once before i flashed 4.3 and the wifi fix and after i flashed the wifi fix my phone stopped booting into 4.4.2 ever since ive been trying to get a odin wifi fix removal for my phone. i want to see if that will fix it but no one will help
also in cwm recovery upon wiping
you get an android_secure not found or somthing like that
zachdees said:
In all my previous posts requesting help of why my phone wont boot 4.4.2 ive never gotten a clear answer or any troubleshooting steps.
when i flash 4.4.2 with any recovery it goes to rom logo and doesnt boot past that. the only rom ive been successful with flashing is omni rom. whats the difrence between omni rom and any other regular 4.4.2 rom/
all i want to do is use carbon kk i had 4.4.2 working once before i flashed 4.3 and the wifi fix and after i flashed the wifi fix my phone stopped booting into 4.4.2 ever since ive been trying to get a odin wifi fix removal for my phone. i want to see if that will fix it but no one will help
also in cwm recovery upon wiping
you get an android_secure not found or somthing like that
Click to expand...
Click to collapse
The android secure issue you see is actually nothing. It is stating it cant find that directory on you sdext partition which you dont have unless you partition your sdcard.
Now why you cant boot 4.4 is kind of odd. I have gone between all versions for our phone aosp and touch wiz without any problems. I would suggest installing twrp and then running billards back to stock mc2 with counter reset (located in development section). Make sure you read the op for that thread and follow his directions. After flashing that before rebooting flash a root.zip (dont use twrp's root). Once your booted you can use odin or an app to flash cwm or philz (6.07.9 recommended) then you can flash any 4.4 you want. Just remember to wipe/format your internal sdcard (data/media) before going to 4.4.
Sent from my SPH-L900 using XDA Premium 4 mobile app
My phone won't let me format the internal sd card it seems like Its locked or something also I've done back to stock 5 times and no luck
Which recovery and how are you trying to format internal?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Do what jlmancuso said. This will format your internal sd as well. Just go back to stock unrooted MC2 and don't bother with flashing the root till its back up and running stock unrooted. Once you do that use the Samsung Note 2 Toolkit (version 2 not 3) and choose the ALL IN ONE Root,recovery, busy box, etc option and choose the twrp recovery not clockwork. Once you get it rooted and on twrp recovery, immediately flash Phil's recovery. 6.07 version (or whichever version that has already been recommended). Then wipe everything as usual including dalvic, cache, internal sd. Then flash stock rooted MK4 in lorjay's thread. then use ODIN on your PC to flash the wifi fix. Do a prl and update profile while on stock rooted MK4. Once you are at this point you can then flash any KK rom and it should work fine. just make sure you set your phone down and let it complete the initial boot as it sometimes takes a few minutes to boot. If this does not work then you're screwed LOL. Good luck.
tx_dbs_tx said:
Do what jlmancuso said. This will format your internal sd as well. Just go back to stock unrooted MC2 and don't bother with flashing the root till its back up and running stock unrooted. Once you do that use the Samsung Note 2 Toolkit (version 2 not 3) and choose the ALL IN ONE Root,recovery, busy box, etc option and choose the twrp recovery not clockwork. Once you get it rooted and on twrp recovery, immediately flash Phil's recovery. 6.07 version (or whichever version that has already been recommended). Then wipe everything as usual including dalvic, cache, internal sd. Then flash stock rooted MK4 in lorjay's thread. then use ODIN on your PC to flash the wifi fix. Do a prl and update profile while on stock rooted MK4. Once you are at this point you can then flash any KK rom and it should work fine. just make sure you set your phone down and let it complete the initial boot as it sometimes takes a few minutes to boot. If this does not work then you're screwed LOL. Good luck.
Click to expand...
Click to collapse
The red additional steps are unnecessary and make little sense. Otherwise, yup.
I'm of the hunch-ish opinion that it is the "wifi fix" that causes lots of these problems in the first place. Most everyone who flashes 4.4.2 builds and that has issues usually share the common thread of having that "wifi fix" on their phone....and that is a hunch, yes, purely on my part. In any case MK4 (radio, ROM, etc) is in no way needed to flash 4.4.2 builds.
I Have done every flash to stock with counter reset. and no matter how many times ive tried it still bootloops i need a DIRECT WIFI FIX REMOVAL
There is no such thing. All the wifi fix is a flash of the param.bin which is in the mk4 odin file. Also those who took the ota have it. It in no way effects aosp!
Are you flashing anything besides the 4.4 rom?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Are you also performing the data wipe and factory reset AFTER FLASHING THE ROM AND GAPPS? Many miss this required step.
Sent from my SPH-L900 using xda app-developers app
thunderwagn said:
Are you also performing the data wipe and factory reset AFTER FLASHING THE ROM AND GAPPS? Many miss this required step.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I have never had to do that but it wont hurt to try it.
Sent from my SPH-L900 using XDA Premium 4 mobile app
i have always payed close attention to that step. im almost to the point of selling my phone for the note 3 this journey is almost over
zachdees said:
i have always payed close attention to that step. im almost to the point of selling my phone for the note 3 this journey is almost over
Click to expand...
Click to collapse
That is definitely a good idea...considering that last I knew Note 3 has yet to get working 4.4.2 builds.