I'm not having much success in switching to a 4.3 rom. I would appreciate any feedback I can get. I have repeated these steps multiple times including re-flashing twrp with no luck.*
SGS4 L720 4.2.2 MF9
CF autoroot
GooManager -> TWRP v2.6
Factory reset
Wipe data, cache, dalvik & system
Install pa_jfltespr-3.98.zip
Install pa_gapps-full-4.3.zip
Reboot system and I'm still in *4.2.2 with all data intact.*
TWRP is not wiping or installing but at each step it says successful. What am i missing?*
Try installing twrp 2.5.0.2 here http://forum.xda-developers.com/showthread.php?t=2361378 . Alot of people are reporting problems with 2.6...
Thanks for the quick response. Ok, I downloaded and used Odin to install TWRP 2.5.0.2
I again went through the steps outlined above - wipe, and install but no joy.
I still have all my files intact - nothing was wiped and 4.3 was not installed.
This is so bizarre I have to assume I am royally screwing something up.
I can't seem to find anyone else having a similar problem so that further confirms it must be operator error. But I can not figure it out!
Again, all suggestions would be much appreciated!!!
I just tried flashing cwm in recovery without success. Still stumped.
I have used all available custom recoveries and I stay on 4.3 much of the time. I've had the best luck with latest cwm recovery. I have not had any wipe issues that I know of but what I have had is I do get stuck on Samsung screen after I reboot from time to time on various 4.3 roms. I was told by Cordell to just hold power down, reboot and that has been how ive gotten around that. Currently using Slim Bean beta 3 and have NOT had the issue since updating. I was also told its not rom related but I don't quite understand as beta 3 slim is fine but 2 outa 3 reboots on beta 2 would have me stuck on Sammy screen until another reboot... Glad it hasn't been.an issue since beta 3 for whatever the reason.. anyway thats what my issues have been with 4.3.. I know the 1st thing to go when a phones been flashed too much is recovery but I've been crackflashing since 2010 (daily, sometimes multiple times one day..;o ) and never had a phone crap on me yet. (KnockonWood) Hope you get this resolved.
I suggest maybe odining back and catching ETAs to mf9 then flash supersu and see if that changes anything for you. Just try things and maybe something will fix it. Looking forward to twrp update. I used 2.5.0.2 for a while with no probs but if it is a recovery issue some are having i believe DTroy will address it and either him or Koush would probably know the answer.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Solved!
Thanks for the advice!
Odin to MDC
Forced OTA to MF9
Rooted& TWRP 2.5.0.2
Success!
Hello,
I've only yesterday rooted my phone for the very first time and followed a guide on how to flash PA. In the guide it told me to flash a radio and boot loader, which apparently I wasn't supposed to flash because I was on 4.3 already. So I didn't have service, someone told me to reflash 4.3 which I did using the stock rom downloaded from android dev page. But It won't flash the system it returns an error regarding the usb port. I flashed 4.2.2 which did flash the system but is apparently stuck on the loading screen (nexus X) for about 20 mins or so. Any help on how to reflash stock 4.3 and then reflash just PA 3.99 and Gapps?
cheers
RabbeV said:
Hello,
I've only yesterday rooted my phone for the very first time and followed a guide on how to flash PA. In the guide it told me to flash a radio and boot loader, which apparently I wasn't supposed to flash because I was on 4.3 already. So I didn't have service, someone told me to reflash 4.3 which I did using the stock rom downloaded from android dev page. But It won't flash the system it returns an error regarding the usb port. I flashed 4.2.2 which did flash the system but is apparently stuck on the loading screen (nexus X) for about 20 mins or so. Any help on how to reflash stock 4.3 and then reflash just PA 3.99 and Gapps?
cheers
Click to expand...
Click to collapse
Go into recovery and do factory reset, that should get u past the nexus X... Then just flash pa and gapps your done, flashing a radio and bootloader shouldn't have hurt anything unless u flashed wrong ones, recheck your versions on the files. U should be on a radio that ends in 84 (it works on 4 2.2 so dont worry... U dont need to be on 4.3 to flash pa, just factory reset first
drawde40599 said:
Go into recovery and do factory reset, that should get u past the nexus X... Then just flash pa and gapps your done, flashing a radio and bootloader shouldn't have hurt anything unless u flashed wrong ones, recheck your versions on the files. U should be on a radio that ends in 84 (it works on 4 2.2 so dont worry... U dont need to be on 4.3 to flash pa, just factory reset first
Click to expand...
Click to collapse
I wanted to do that but my sd had been wiped, but it's been solved
Hello, xda. I have a lot of time using the Motorola android phones, but faced with the problem of firmware change on my xt907 for the first time. I'm on stock 4.4.2 (182.46.10) with root, custom recovery, but now would like to try CM or gummy.
I met a problem that after cm-11-20140914-NIGHTLY or any other ROM installed from recovery, during the first boot, after language selecting my phone starts cyclic reboot.
I tried cwm 6.0.3.9 and twrp 2.8.0.0, 2.7.1.0, doing all wipes before (or/and after) installation. I try to install this ROMs over 4.4.2 stock and on the clean system (after erase /system). But nothing worked. With RSDLite I can always switch back to 4.4.2 I can always switch back to 4.4.2, but the inability to use CM bother me.
I have original xt907 from verizon, but I use it abroad (gsm).
I will be glad to hear any ideas and suggestions about this situation, many thanks
And sorry for my pigin-English
Do you wipe data before installing the ROM?
Klen2 said:
Do you wipe data before installing the ROM?
Click to expand...
Click to collapse
Sure. Before and/or after. From fastboot (first time), from recovery. And i`m telling about clean stock 4.4.2 from RSDLite
Short Story: My phone works fine when its stock 4.4.4 , no root. If i root it and flash a custom recovery using WUG it gets stuck on starting ups.
Long Story: I was running the latest version of PA, rebooted my phone because of a franco kernel update, and it got stuck on the bootscreen. Tried everything, couldnt get it to boot, so I finally flashed stock using WUG, it worked. I then rooted and flashed custom recovery, and it got stuck on starting apps. Flashed stock again and it worked, repeated the root, and it got stuck on starting apps.
Anybody know whats going on?
wasa67 said:
Short Story: My phone works fine when its stock 4.4.4 , no root. If i root it and flash a custom recovery using WUG it gets stuck on starting ups.
Long Story: I was running the latest version of PA, rebooted my phone because of a franco kernel update, and it got stuck on the bootscreen. Tried everything, couldnt get it to boot, so I finally flashed stock using WUG, it worked. I then rooted and flashed custom recovery, and it got stuck on starting apps. Flashed stock again and it worked, repeated the root, and it got stuck on starting apps.
Anybody know whats going on?
Click to expand...
Click to collapse
You should do a CLEAN install, wipe dalvik / cache / System and Data, the last two ones are very important to wipe, otherwise you got stuck on boot.
It is best to flash your rom using recovery and forget the toolkit, just upload your rom on your N4, get to recovery => install => choose the rom, that's it.
blusydays said:
You should do a CLEAN install, wipe dalvik / cache / System and Data, the last two ones are very important to wipe, otherwise you got stuck on boot.
It is best to flash your rom using recovery and forget the toolkit, just upload your rom on your N4, get to recovery => install => choose the rom, that's it.
Click to expand...
Click to collapse
I did all that before, and it still didn't work.
I think your problems are related to flashing the recovery, did you try to revert back the the old one ?
Hi guys im a bit rusty again in all this since i rooted my S3 and HTC desire years ago ,
I have an Galaxy S5 SM-G900F (bought seperately without any provider)(EU)
after 2-3 months now and getting the official android 5.0 upgrade, i thought it be time to Root my device again ,
i followed this link and how to from ChainFire "http://forum.xda-developers.com/showthread.php?t=2696537"
wich i been using on my Galaxy Tab 7 Lite(T110) as well and worked flawlessly
I followed the exact steps as usual , rooting went fine, phone rebooted as it should , i updated SUPERSU and its binaries and installed Ericson's Busybox,. ,and everything worked as it should ,
then i put off my phone and boot in to recovery mode to flash the Philz_touch_6.26.1-klte.zip (touch recovery)
when im in my stock recovery i facepalm'd myself because i hadnt put the flashable recovery file on my internal storage yet ,
so i wanted to reboot back in the phone so i could put the file on my internal storage so id be able to flash it from stock recovery ,,..
this is where it all got strange,.
My phone stays black after Boot logo, gives me errors like ,. SYSTEM UI STOPPED ,. and so on for about everything that keep the phone running , i mean really everything STOPS , after about 15 minutes and klicking away all the Stopped msg's , it just reboots again to do the same.
i tried starting the phone in SAFE MODE ,. . Same thing,...
this all just came up after i booted to STOCK RECOVERY ,. and back to Android without changing anything,.
Android 5.0
Stock Rom
CF Autoroot klte SM-G900F
Please help ?
Thank you in advance
Mike130784 said:
Hi guys im a bit rusty again in all this since i rooted my S3 and HTC desire years ago ,
I have an Galaxy S5 SM-G900F (bought seperately without any provider)(EU)
after 2-3 months now and getting the official android 5.0 upgrade, i thought it be time to Root my device again ,
i followed this link and how to from ChainFire "http://forum.xda-developers.com/showthread.php?t=2696537"
wich i been using on my Galaxy Tab 7 Lite(T110) as well and worked flawlessly
I followed the exact steps as usual , rooting went fine, phone rebooted as it should , i updated SUPERSU and its binaries and installed Ericson's Busybox,. ,and everything worked as it should ,
then i put off my phone and boot in to recovery mode to flash the Philz_touch_6.26.1-klte.zip (touch recovery)
when im in my stock recovery i facepalm'd myself because i hadnt put the flashable recovery file on my internal storage yet ,
so i wanted to reboot back in the phone so i could put the file on my internal storage so id be able to flash it from stock recovery ,,..
this is where it all got strange,.
My phone stays black after Boot logo, gives me errors like ,. SYSTEM UI STOPPED ,. and so on for about everything that keep the phone running , i mean really everything STOPS , after about 15 minutes and klicking away all the Stopped msg's , it just reboots again to do the same.
i tried starting the phone in SAFE MODE ,. . Same thing,...
this all just came up after i booted to STOCK RECOVERY ,. and back to Android without changing anything,.
Android 5.0
Stock Rom
CF Autoroot klte SM-G900F
Please help ?
Thank you in advance
Click to expand...
Click to collapse
Boot to recovery, wipe the caches, reboot, see how you get on then
*Detection* said:
Boot to recovery, wipe the caches, reboot, see how you get on then
Click to expand...
Click to collapse
thank you for your reply
i have wiped the Cache partitions as its the only cache to wipe in stock recovery,. rebooted ,. but still the same thing
Mike130784 said:
thank you for your reply
i have wiped the Cache partitions as its the only cache to wipe in stock recovery,. rebooted ,. but still the same thing
Click to expand...
Click to collapse
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
*Detection* said:
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
Click to expand...
Click to collapse
i used Odin3-v3.07
but after flashing the root everything worked installed superSU and updated it and its binaries and installed busybox,.
it all stopped working after i went into Stock Recovery and back
id prefer not to do a factory reset Wipe,. unless i really have to to fix it ,.
im going to try reflash with the latest version then,.
i have swapped SD card to galaxy tab to put the Flashable touch recovery on the SD card, and swapped back to the phone so i could Flash the Recovery when im in stock ,.
but ill try flashing Root with latest Odin first.. thank you
*Detection* said:
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
Click to expand...
Click to collapse
the new odin is a bit less informative (to me as beginner)
i managed to use AP to flash the root again
all goes fine , it reboots
and its now upgrading android as it says and opening app's
then Black screen again,. i klick a button,. and it shows me again all the STOPPED msg's of all internal apps that are crashing,. litterally all apps,
what can i do ?
If clearing cache didn't work, fixing permissions in recovery didn't work, only thing left I can think of is factory reset
--
*Detection* said:
If clearing cache didn't work, fixing permissions in recovery didn't work, only thing left I can think of is factory reset
--
Click to expand...
Click to collapse
i cant fix persmission in stock recovery and flashing the philz touch recovery didnt work something about not verify signature,.
al i can do i guess is wipe data factory reset ,.but im affraid it wont fix anything
Try TWRP recovery instead
http://teamw.in/project/twrp2/229
No reason a factory reset won't fix things, worst comes to worst, flash the whole ROM again from ODIN, that will fix everything as it wipes and reinstalls the lot
Grab a stock ROM from sammobile
Thank you for all your replys mate..
I managed to get it working again by doing a factory reset in stock recovery after I flashed root with latest odin
Even tho it was my last resort there was nothing else I guess .
I'm not sure tho if this will happen again when I go back to recovery like I did when this all happend the first time while I actually want to flash a more advanced recovery then stock recovery ..
But I'll take my chances and just leave it as it is
Again thank you for your help and suggestions .
This thread could be closed
Sent from my SM-G900F using XDA Free mobile app
Pleased you got it working again, I would say if you think you might want to flash another advanced recovery in the future, it might be best to do that now since you have already factory reset the phone, that way if this happens again, you don't lose months of data and settings and files that you have gathered between now and whenever you decide to flash recovery
*Detection* said:
Pleased you got it working again, I would say if you think you might want to flash another advanced recovery in the future, it might be best to do that now since you have already factory reset the phone, that way if this happens again, you don't lose months of data and settings and files that you have gathered between now and whenever you decide to flash recovery
Click to expand...
Click to collapse
i have actually ,. i installed the TWRP u mentioned,. by taking there app from the Playstore,. and flashed the new recovery, within android and without rebooting (just in case)
im used to the old CWM thats why i first wanted the Touch recovery as its based on it,
but always open for trying new things
Thank you
Good stuff
Id say the whole entering recovery / apps crashing thing was a problem with the ODIN version you used to root, too old for Lollipop is my guess, so I wouldn't worry about entering recovery again.