Related
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.
I was happy as a lark with TWRP. But 4.3 happened and it is a new process. There are variations, here is one way to get your phone and 4.3 to play nice together. I'm on Sprint Galaxy Note 2 and if you are coming to a 4.3 or 4.4 for the first time, or having trouble. Try this first! I give credits Below, but it's for all ROM's. "Google process stopped" is a common sign that this wasn't done. Or if it just hangs on the samsung screen... Btw it does seem like an eternity sometimes. Lol
General theory: skip to the next paragraph if you dont care. I've Googled and read. You should too. We are trying to clean and prepare your phone for 4.3. "Wipe" is not the same as "format. " We need to remove all the little pieces of data that may still be there from before. We need to start fresh. Also, the partitions sizes are different in 4.3. In general we need to clean.
PROCESS A is this link. Billard412 This is back to stock, completely cleaning your phone. It requires odin and a computer. If you want to try procees B alone, you can skip A and just do "process B" and see if that works. If you still have trouble, you know you need to do the full thing. Just a note, you might think it works, but then your nandroids don't restore.. Time for process A. Back to stock. It's good to do this once in a while to start fresh, also.
http://forum.xda-developers.com/showthread.php?t=2086769
Then install USE PHILZ recovery 6.07.9 (link below)
-Install philz. Some people have luck with TWRP , i didn't. I don't think TWRP works with 4.3
There is a newer Philz version, not sure all the bugs are worked out, use 6.07.9
One thing that might be confusing, the process A restore from billard recommends TWRP and I'm recommending Philz recovery. So best advice, although possibly confusing, is install TWRP, billard restore, then flash Philz. It's not any more work really. The back to stock will put you in a stock recovery. So you have to flash something. I was a TWRP fan too, but Philz has had less problems in 4.3.
1. You can follow billard 's instructions
2.there is a YouTube if you want to follow that in billards thread
or3 . Jlmancuso provided this to try and simplify the process:
a. Boot into download/bootloader mode.
b. Connect to pc and use odin to flash TWRP. Make sure you uncheck reboot and flash twrp in the pda slot.
c. Once flashed pull battery and disconnect from pc.
d. Press vol+ menu power buttons while inserting battery (yes it is difficult but can be done)
e. Now in recovery perform factory reset.
f. Flash this http://forum.xda-developers.com/showthread.php?p=36388145
g. Now reboot it will act/look weird but dont worry this is normal. It will reboot and take a long time to boot.
Now you are on stock mc2 (no knox anymore). Root using cf autoroot http://forum.xda-developers.com/showthread.php?p=33278464
Now use odin once again and flash your recovery again, this time Philz. Now you are rooted and have a custom recovery. Oh and you have a working phone again.
PROCESS B.
This is done before any ROM install and before any nandroid restore.
Preparation: BACK UP INTERNAL IF DESIRED, I WILL RECOMMEND WIPING IT in the next steps . NOT REQUIRED, BUT RECOMMENDED. You can move it to external, external doesn't need to be wiped.
In PHILZ recovery 6.07.9 (link below)
1. Mounts and Storage
Format / systemFormat / casheFormat / data Recommended optional. Format internal SD card
Format / data and /data /media (/sdcard) ALL INTERNEL SD CARD DATA IS LOST.PREVIOUS IS NOT EXTERNAL, EXTERNAL IS "SDCARD1" which i would not recommend
2. Power Options > reboot recovery
3. Wipe cashe partition
4. Advanced > Wipe dalvik cashe
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
I would stick with 4.3 and Philz backed up things. Don't restore something from before. Neither a 4.2 rom or a TWRP backup. Once you know you have got this process down, then try / do those sorts of things. Philz is supposed to be able to do that, but let's keep it simple until you have this figured out.
If you want to try process B first only , it may be all you need. But if it doesn't work, do all of it.
I hope this helps - LINKS & CREDITS in next post
4.3 general wiping and preparatory instructions
LINKS
same as above Billard412 back to stock - http://forum.xda-developers.com/showthread.php?t=2086769
alternate back to stock - Rwilco http://forum.xda-developers.com/showthread.php?t=2591898
Philz Recovery Thread - http://forum.xda-developers.com/showthread.php?t=2552653
On the Philz recovery site the "L900" looks more like "l900" and is confusing - so here is a more direct link - select 6.07.9 http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900
TWRP http://teamw.in/project/twrp2/117
To get root- one option is CF Autoroot-
[SPH-L900] CF-Auto-Root
http://forum.xda-developers.com/showthread.php?t=1956180
WIFI FIX just in case. Flash in the PDA tab of Odin http://d-h.st/6qX
If you want to change modems i use this (not required / optional) - http://forum.xda-developers.com/showthread.php?t=2537713
General
I am not trying to take credit for anything. Notice how none of this is my work. Just hoping to pull together and clarify this process. Others my post different ways, and you can try other ways, but if it doesn't work, use this process exactly. It works for many. If you want to post that you tried another way and it didnt work, you are welcome to, but then my reply will be to try it this way...or i wont reply. I just had to keep typing this over and over to many, and i figured I would put out a detailed version. This works. (you know the drill, its your phone, not my responsibilty, of course)
CREDITS AND ROMS
I picked up a lot of this process from Lorjay589's thread. His OP pointed me at the Billard412 back to factory
jlmancuso has posted refined and explained this process 100 times as well.
this is for SMOOTHEST ROM, CUSTOM ROM, SYNERGY ROM, DIGIBLUR ROM, FTW ANNIHILATION, ROM AND MANY OTHERS.
therfore jlmancuso, chaz187, ianmb, digiblur, lorjay589, rwilco12, phil3759, fryingpan0613, jimmydene84, cbucz24, wwjoshdew, agent soap AND MANY OTHERS.
constructive criticism is always welcome i have a tough skin, just be nice and don't hold back to let me know. i am not that knowledgeable, this is my first thread. Just been following some 4.3 threads for a while and saw a recurring problem.
Very nice guide Cole
Sent from my SPH-L900 using Tapatalk
Reserved
Darn it I want a reservation too!!
Thanks now I have a thread to link to instead of a single post.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Very nice tutorial. U nail all that we need to do for a smooth install
Thanks
SGNote2
Any reason why we should not use the latest version of Philz Recovery version 6.15.4?
justppc said:
Any reason why we should not use the latest version of Philz Recovery version 6.15.4?
Click to expand...
Click to collapse
Some people have just had some problems when using the new version, therefore the previous version is more reliable. Better chance of everything working. Once you have your phone running smoothly using this process, you are welcome to try it. If you have problems... Revert back.
Start with post 87 of the Philz thread, if you like.
http://forum.xda-developers.com/showthread.php?t=2552653
Thanks, this resolved an issue with 'Inconsistent System UIDs"
KNOX with options A/B
Will this process A or B or both, untrip your knox and reset everything to stock? Or does it just get you closest to stock as you can, with KNOX still tripped?
Thanks
Dedline said:
Will this process A or B or both, untrip your knox and reset everything to stock? Or does it just get you closest to stock as you can, with KNOX still tripped?
Thanks
Click to expand...
Click to collapse
Process A completely wipes your phone and resets it to stock. B is just general wiping process when flashing a new rom. You shouldn't have a Rom on your phone when you are done with either. (other than the one backed on you external sd)
Head on over the the Ballard thread to read more about process A
justppc said:
Thanks, this resolved an issue with 'Inconsistent System UIDs"
Click to expand...
Click to collapse
This hasn't worked for me. I've repeated this several times with no luck. I also can't install gmail. Any suggestions?
mr.pope said:
This hasn't worked for me. I've repeated this several times with no luck. I also can't install gmail. Any suggestions?
Click to expand...
Click to collapse
You could try to start all the way over by using ODIN to install stock MA7, then root it and take it from there.
justppc said:
You could try to start all the way over by using ODIN to install stock MA7, then root it and take it from there.
Click to expand...
Click to collapse
alas, I have tried that as well. I finally made some headway and think I have it. I had to fix permisions for all apps using Rom Toolbox Lite Looks like that has fixed it. Flashing forward as I type.
Just a bump to keep this where everyone can see it.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Gotta try this on my note 2
K
Sent from my SPH-L710 using xda app-developers app
Just a reminder
Hello,
I ended up getting a replacement phone from Best Buy and I ended up flashing a older version of twrp before trying the latest 2.7.0. I did a few backups just to have a stock rom to return to if all failed. Somehow after I tried flashing the new mk4 roms, I lost my 4g LTE in the process of flashing different ROMS and none of my back ups for twrp would work so I ended flashing Philz recovery and then Digiblur just to get my phone working again.
I ended up requesting another replacement so I can have my 4g LTE again. My question is. Is it possible to wipe a 4g LTE key when rooting and also is Philz the way I should of went when I rooted to make a stock backup if everything fails? Anything I should make sure to back up in particular to make sure I dont wipe nothing important. I just want to be extra careful this time around.
The phone was already updated to MK4 when I received it. Any help is appreciated!
Lyvewire said:
Hello,
I ended up getting a replacement phone from Best Buy and I ended up flashing a older version of twrp before trying the latest 2.7.0. I did a few backups just to have a stock rom to return to if all failed. Somehow after I tried flashing the new mk4 roms, I lost my 4g LTE in the process of flashing different ROMS and none of my back ups for twrp would work so I ended flashing Philz recovery and then Digiblur just to get my phone working again.
I ended up requesting another replacement so I can have my 4g LTE again. My question is. Is it possible to wipe a 4g LTE key when rooting and also is Philz the way I should of went when I rooted to make a stock backup if everything fails? Anything I should make sure to back up in particular to make sure I dont wipe nothing important. I just want to be extra careful this time around.
The phone was already updated to MK4 when I received it. Any help is appreciated!
Click to expand...
Click to collapse
Philz is the only way to go when choosing a recovery. Twrp will not backup or restore mk4 properly and wont woek correct with 4.4 aosp either. When ypu do your first backup choose custom backup and backup everything but Efs. When that is done go back into custom backup and only backup efs (it must be done by itself). I would then suggest copying both backups to a pc or cloud storage for safe keeping.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.
jonstowe78 said:
Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.
Click to expand...
Click to collapse
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
ok I will try that now ... I hope youre right!
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
bmatney said:
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Well, yeah, that's the reason,
According to gr8nole, bootloader is responsible for this, the updated version of bootloader have this problem
Sent from my SM-T211 using XDA Free mobile app
bmatney said:
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
No, it can happen if you are on 4.1.2 too, it happened to me on my SM-T211 while running 4.1.2 and I did used a software method to reboot to recovery and was stuck in recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
It will happen if you ever updated the firmware once, no matter if you revert back to previous version later
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
It will happen if you ever updated the firmware once, no matter if you revert back to previous version later
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Good to know ... GREAT, so since I updated that ONE time, from now on I can NEVER boot into recovery via software? It'll always be the 3B method .... that sucks! lol
jonstowe78 said:
Good to know ... GREAT, so since I updated that ONE time, from now on I can NEVER boot into recovery via software? It'll always be the 3B method .... that sucks! lol
Click to expand...
Click to collapse
Yes
Unless someone makes a fix for that!
Sent from my SM-T211 using XDA Free mobile app
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
I've been trying to find a way to downgrade back to 4.1.2 after finding out about kitkat's flaws. After I installed it, I noticed three things:
- NO extSD card permission
- FASTER battery drainage (it takes a whole day to charge it back from 0)
- Games like Temple Run can no longer be played cause tilt sensor malfunctions - accelerometer issues)
The first two are a major let down. If I had known about this prior the upgrade, I would have kept JB 4.1.2.
Now I'm looking for ways to safely downgrade back to Jelly Bean. From what I'd read, people are getting stuck in custom recovery because the kitkat bootloader or whatever is not compatible (or something like that)? Also, those who have successfully managed to get back to JB now have the issue of not being able to charge their sm-t210R unless it's turned ON. So if we fix one issue, we still got the other.
@jonstowe78, are you having any issues with charging while your device is turned off?
I read about flashing Philz custom recovery for sm-t20R, and after a (failed) attempt to root my tab 3 (which put me off from rooting), I know a bit about the 3B method to reboot. I flashed a custom 4.1.2 JB stock rom using Odin and that's how I got rid of the messed up screen that happened after I rooted.
I would LIKE to root to NoleKat, but like I said, one bad experience with rooting, forever leery of it. Unless someone can help me, please?
sscsps said:
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Ditto that. I got the firmware from sammobile.com & flashed (AP mode in Odin 3.09) and I was no longer stuck. At that point, I had stock 4.4.2. I then flashed phil via Odin 3.09 (AP) - the gr8nole version (check the nolekat thread) and was able to install any ROM I wanted.
Good luck
ameva said:
I've been trying to find a way to downgrade back to 4.1.2 after finding out about kitkat's flaws. After I installed it, I noticed three things:
- NO extSD card permission
- FASTER battery drainage (it takes a whole day to charge it back from 0)
- Games like Temple Run can no longer be played cause tilt sensor malfunctions - accelerometer issues)
The first two are a major let down. If I had known about this prior the upgrade, I would have kept JB 4.1.2.
Now I'm looking for ways to safely downgrade back to Jelly Bean. From what I'd read, people are getting stuck in custom recovery because the kitkat bootloader or whatever is not compatible (or something like that)? Also, those who have successfully managed to get back to JB now have the issue of not being able to charge their sm-t210R unless it's turned ON. So if we fix one issue, we still got the other.
@jonstowe78, are you having any issues with charging while your device is turned off?
I read about flashing Philz custom recovery for sm-t20R, and after a (failed) attempt to root my tab 3 (which put me off from rooting), I know a bit about the 3B method to reboot. I flashed a custom 4.1.2 JB stock rom using Odin and that's how I got rid of the messed up screen that happened after I rooted.
I would LIKE to root to NoleKat, but like I said, one bad experience with rooting, forever leery of it. Unless someone can help me, please?
Click to expand...
Click to collapse
Download stock md5 of 4.1.2 for your country from sammobile.com and flash it from Odin to downgrade to 4.1.2,
For rooting, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2822307
How to root any android device, easy, Noob friendly!
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
Download stock md5 of 4.1.2 for your country from sammobile.com and flash it from Odin to downgrade to 4.1.2,
For rooting, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2822307
How to root any android device, easy, Noob friendly!
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for your feedback!
The truth is, after I made that post, I did a lot of reading on custom recovery like TWRP, Philz Touch, and CWM, and then I read some more about NoleKat v2.0, and how it basically is like KK but it gives you root access and sd card rights back, so now I've decided to not downgrade. I've learned a lot from when I first tried to root (which ended in failure and a dim screen with flickering colors), so I'm more confident in how the process goes.
I was wondering though. If I install custom recovery (from any of those three), will they wipe my data? I know you can back up your data using the custom recovery, but which one do you think is the least likely to have issues with KK bootloader (assuming the custom recovs have all been updated to 'play nicely' with the KK so people won't get stuck in custom recov bootloop?)
ameva said:
Thank you for your feedback!
The truth is, after I made that post, I did a lot of reading on custom recovery like TWRP, Philz Touch, and CWM, and then I read some more about NoleKat v2.0, and how it basically is like KK but it gives you root access and sd card rights back, so now I've decided to not downgrade. I've learned a lot from when I first tried to root (which ended in failure and a dim screen with flickering colors), so I'm more confident in how the process goes.
I was wondering though. If I install custom recovery (from any of those three), will they wipe my data? I know you can back up your data using the custom recovery, but which one do you think is the least likely to have issues with KK bootloader (assuming the custom recovs have all been updated to 'play nicely' with the KK so people won't get stuck in custom recov bootloop?)
Click to expand...
Click to collapse
Gr8nole have updated the recovery for SM-T210 to not stuck in recovery bootloop(it used to happen only and only if you use any software method to enter in to recovery mode) download cwm for SM-T210 and you are good to go,
And none of the recovery will wipe your data, even if you select factory wipe from custom recovery, it will only delete all the installed applications,
And of you flash(install) a recovery, it won't delete any data/app
Sent from my SM-T211 using XDA Free mobile app
@gr8nole Please prepare two PARAM image from JB and KitKat firmware. Try both PARAM on your device, maybe one of it is the solution of this recovery bootloop issue.
To create Odin flashable param:
Code:
tar -H ustar -c param.bin > param.tar
md5sum -t param.tar >> param.tar
mv param.tar param.tar.md5
sscsps said:
Gr8nole have updated the recovery for SM-T210 to not stuck in recovery bootloop(it used to happen only and only if you use any software method to enter in to recovery mode) download cwm for SM-T210 and you are good to go,
And none of the recovery will wipe your data, even if you select factory wipe from custom recovery, it will only delete all the installed applications,
And of you flash(install) a recovery, it won't delete any data/app
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again for your feedback!
Wait, you mean the installed apps that came pre-installed with KK? Because that's what it sounds like if you say that the recovery will not wipe my data like game progress, rss feeds, recordings, etc?
So if that's true, should I still create a backup through the custom recovery?
Would that be called a dirty flash? Or a full wipe?
I've spent nearly this whole day reading through the NoleKat thread from v0.1 to v.2. I can see it's come a long way. Gr8nole is truly an amazing developer! I've seen issues like charging offline, recovery bootloop, boot animation issues fixed as each new update gets better and better.
ameva said:
Thanks again for your feedback!
Wait, you mean the installed apps that came pre-installed with KK? Because that's what it sounds like if you say that the recovery will not wipe my data like game progress, rss feeds, recordings, etc?
So if that's true, should I still create a backup through the custom recovery?
Would that be called a dirty flash? Or a full wipe?
I've spent nearly this whole day reading through the NoleKat thread from v0.1 to v.2. I can see it's come a long way. Gr8nole is truly an amazing developer! I've seen issues like charging offline, recovery bootloop, boot animation issues fixed as each new update gets better and better.
Click to expand...
Click to collapse
No, not the pre-installed apps, but the apps you installed will be uninstalled is you perform a wipe operation from recovery(custom)
It's just a apps wipe, it will leave only personal data like photos, songs, etc.
Sent from my SM-T211 using XDA Free mobile app
Hmm, I guess I'm just going to have to do a dirty flash then, mainly because I have this one game app, and even though it stores my game info in a folder, if I delete the app, I lose my account, and it's huge hassle to get it back.
So just to be clear, dirty flashing is basically no factory wipe/reset at all, right? Then what does the davlik or wiping cache do? I think we're still suppose to do that after flashing custom rom.
ameva said:
Hmm, I guess I'm just going to have to do a dirty flash then, mainly because I have this one game app, and even though it stores my game info in a folder, if I delete the app, I lose my account, and it's huge hassle to get it back.
So just to be clear, dirty flashing is basically no factory wipe/reset at all, right? Then what does the davlik or wiping cache do? I think we're still suppose to do that after flashing custom rom.
Click to expand...
Click to collapse
You can flash it without any risk of anything being deleted, flashing recovery won't delete anything (neither any app)
Cache memory stores dynamic things which helps apps to run smoothly, if you wipe that, your apps will have to make that memory again(when it runs for the first time/first time after you clear cache) to run smoothly in future, but Delvik cache helps android to run smoothly, every rom need different things to run smoothly, so we need to clear previous rom's Delvik cache in order to allow new rom to create is own Delvik cache of its own, this is the reason the first boot takes a bit longer time to compleat because it takes time to write is own Delvik cache, sometimes, different roms' Delvik cache conflicts, so it can be like you get stuck on boot screen, just clear Delvik cache to fix it
Hope it is clear, I might be wrong, but this is what I think it is!
Sent from my SM-T211 using XDA Free mobile app
touch screen bugging out
Ok so my phone for some reason can't click on the exact location i seem to want to press
idk i was trying to flash the silly roms you guys have around here. for stock galaxy note 4 spr
i've been flashing for a while
and it seems none of them work anymore
i use the latest TWRP even used the other one CWM or something like that
i used odin even up to .10 from 1.85 even lower and still can't
even when i install (seems to be the only rom i can cm12)
the locations i press on my screen are buged out. so i have to press higher than i should to even get a click and its hard to text or anything.
i did factory resets, cashe wipes. deleted partitions.. what am i doing wrong ??
why can't this annoying this go away what am i missing guys ???
and why is it only 1 rom can flash on my phone ?? and i can't go back to any lollipop or anything ??
(i also tried flashing a superSU from the tWRP .. when i used CM 12 and it all successed but still
i have this thing where i can't click anywhere im on my phone directly i have to try and feel it out.. please help
1)what software version are you on now?
2)what rom are you trying to flash?
Note4 Rocking a Hybrid Rom
Not long ago, it was discovered flashing the wrong recovery will mess up the lock-screen.
Some were solved with KIES firmware restore; no root, straight to dialer type *#2663# and then TSP FW update. If KIES won't update it, power down, pull battery 30 seconds, Odin stock tar and boot then the dialer code and update.
Do that after you determine which stock tar or KIES update is recommended from Your response above.
Sent from my SM-N910P using Tapatalk
schlepprock said:
1)what software version are you on now?
2)what rom are you trying to flash?
Note4 Rocking a Hybrid Rom
Click to expand...
Click to collapse
I am using
Cyanogenmod version
12.1-20150814-nightly-trltespr 5.1.1
kernel 3.10.40-gef59855
baseversion
N910PVPU4COG5
GALAXY NOTE 4 SPRINT
How ever im trying to flash back to stock evrything.
so that i can flash a rom that uses stock fetures of note 4 (windows mode etc)
the cm 12 does not utilize these and i need those badly.
so i tried to go back even factory reset wipe all cashes
but some reasn during all those fails my system UI says fail. and my touchscreen is not in sync correctly.
i heard of wiping system cache not sure if i done that but with TWRP i wipe everything but SD
it seems this has been a common issue the word we are looking for is calibration issues
it seems it happens to this person exactly how it is happening to me
there was a solution at the bottom but those buttons do not work for galaxy note 4 spr
does anyone know the codes for doing so ?
source:
http://forum.xda-developers.com/note-4-tmobile/help/touch-screen-issues-root-t2986883
Did you see post 3?
I suspect you need to flash OG5 first. Use KIES or Odin. I would suggest wiping all but ExtSdCard and factory reset or format data partition, then power off; pull battery 30 seconds prior to stock tar or KIES recovery.
There's a guide you can follow as well as the OP in this post/thread. But see the steps on post 3, this thread. Boot into stock right after stock flash to try to recover your touch screen. If your touch screen is OK, then follow the guide below to root stock.
http://forum.xda-developers.com/showthread.php?p=62241991
Sent from my SM-N910P using Tapatalk
NatsarYAhu said:
I am using
Cyanogenmod version
12.1-20150814-nightly-trltespr 5.1.1
kernel 3.10.40-gef59855
baseversion
N910PVPU4COG5
GALAXY NOTE 4 SPRINT
How ever im trying to flash back to stock evrything.
so that i can flash a rom that uses stock fetures of note 4 (windows mode etc)
the cm 12 does not utilize these and i need those badly.
so i tried to go back even factory reset wipe all cashes
but some reasn during all those fails my system UI says fail. and my touchscreen is not in sync correctly.
i heard of wiping system cache not sure if i done that but with TWRP i wipe everything but SD
Click to expand...
Click to collapse
I recommend you flash this rom. Mostly stock but very stable,and the developer is working on some goodies.
http://forum.xda-developers.com/showthread.php?p=62336588
I recommend that you back up everything you want to keep because you need to wipe everything EXCEPT external SD card. Wipe cache, dalvik , system, and data three times. Then factory reset three times and then flash this rom.
Note4 Rocking a Hybrid Rom
samep said:
Did you see post 3?
I suspect you need to flash OG5 first. Use KIES or Odin. I would suggest wiping all but ExtSdCard and factory reset or format data partition, then power off; pull battery 30 seconds prior to stock tar or KIES recovery.
There's a guide you can follow as well as the OP in this post/thread. But see the steps on post 3, this thread. Boot into stock right after stock flash to try to recover your touch screen. If your touch screen is OK, then follow the guide below to root stock.
http://forum.xda-developers.com/showthread.php?p=62241991
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Ok so this stock actually went through will get with you shortly to let you know if sync is fixed,
edit: still not synced correctly but phone does finally work how i want just the main problem is bugged trying the link with *#2663# now
Edit: IT WORKED !!! big UPS BRO thank you !!!
i have same problem after install twrp and flash custom firmware phone working fine but touch won't work
i tried that *#2663# but not working on custom rom any solution to solve touch problem on custom firmware
thanks
imeicodes said:
i have same problem after install twrp and flash custom firmware phone working fine but touch won't work
i tried that *#2663# but not working on custom rom any solution to solve touch problem on custom firmware
thanks
Click to expand...
Click to collapse
Odin stock tar and try again.
There's also an update to CFAR (Chainfire auto root) for Note 4. After you fix your touchscreen, root with it and make a TWRP backup once that is installed. A TWRP restore plus full un-root in SuperSU may make OTA possible; CFAR backs up stock recovery.
You can use Flashify to install custom recovery. You may have installed the wrong recovery to have the touch screen out of cal like it is.
Sent from my SM-N910P using Tapatalk