Related
I need to send my D2 back to Verizon for a replacement (Keyboard isn't registering presses, double letters, etc.)
I had rooted my D2 originally.
I have pushed the stock SFB to the Phone (Which did not wipe out my apps/settings?)
I then ran Root Checker which returned False, and indicated the folders + files did not exist.
I then did a System Reset, and went back to square one. I re-activated the phone (Did not add any accounts though).
Is there anything else I should do before sending it back to Verizon?
Thanks!
Edit:
On a similar note, What's the difference between an Oxidized and Deoxidzed SBF? Same with System-Only and Full.
(I pushed the Full SBF to the phone, but I'm curious what the other ones are)
Lord Ned said:
I need to send my D2 back to Verizon for a replacement (Keyboard isn't registering presses, double letters, etc.)
I had rooted my D2 originally.
I have pushed the stock SFB to the Phone (Which did not wipe out my apps/settings?)
I then ran Root Checker which returned False, and indicated the folders + files did not exist.
I then did a System Reset, and went back to square one. I re-activated the phone (Did not add any accounts though).
Is there anything else I should do before sending it back to Verizon?
Thanks!
Edit:
On a similar note, What's the difference between an Oxidized and Deoxidzed SBF? Same with System-Only and Full.
(I pushed the Full SBF to the phone, but I'm curious what the other ones are)
Click to expand...
Click to collapse
It didn't delete your apps or data? Interesting. You should have gone into a bootloop after the SBF, requiring you to go into the stock recovery to format system/cache....
As far as odex and deodex'd. Stock ROM's have odex files for every system app installed on the phone. Supposedly they are supposed to help speed up the startup time of the phone.
Deodex'd is obviously when the odex files have been removed, usually to save room in /system and also to allow themeing.
Full SBF includes EVERYTHING the phone came with (ROM, Kernel, Bootloader, Radio, etc.)
System only SBF is only the operating system. You would use this if your not worried about going back to complete stock, and just need to reload the OS.
Hope this has helped!
That's what I thought @ Still had data.
(Unless this process requires an SD card to work, I don't have one in my phone because it's dead )
I flashed it twice, once with the phone on and connected via RSD Lite 4.8, I just selected the phone there, picked the SBF and hit start... It restarted the phone into some boot-loader like menu, said it was recieved a SW Update, restarted itself and... nothing change.
So then I did it again but started it in the boot-loader like menu to no difference, so I just did a factory reset.
Thanks @ Explanation though!
You should be good. Just make sure your system version is 2.3.20 (I think that's the latest version, haven't had a d2 for a while). Make sure your boot logo and boot animation are stock, and that you don't have superuser install.
Sent from my HTC GingerBolt powered by the lastest Synergy ROM
They are indeed stock.
I took my D2 into the store today to see what they had to say, I have no idea if this is truthful or if the guy was just making it up to sound smart (Never can be sure after listening to other people talk about your own field )
Said that the missed keypresses + double repeats I was getting was from the phone having overheated at some point, and the keyboard is coming away from the keys a bit (The rubber mat is 'bubbled' a bit in some spots) were indicators of overheating too.
No idea if this is true or not, but he said warrenty should cover it and I just have to call into Verizon so I'll do that.
I'd have to say the phone would have had to get pretty damned hot to do that, but who knows. As long as warrenty will cover it its all good.
Sent from my HTC GingerBolt powered by the lastest Synergy ROM
I agree... The previous owner might have left it in the sun or something... Did that with my DS, turned itself off but it was fine in the end.
Gonna call Verizon tomorrow, too late now. Thanks for the help!
I'm still curious as to why the full-sbf didn't factory reset it though.
is Root Checker an app?
The Albatross said:
is Root Checker an app?
Click to expand...
Click to collapse
Yes. It attempts to do something that requires Root to do. If it fails, it tells you. It then checks if the superuser app exists and if the folders for root exist.
I have the same problem with double entries on the physical keyboard. I've had my phone for a year and I'm pretty sure I have never had an overheat (and definitely have never left my phone out in the sun). I attributed this to CM7 nightlies, but now I doubt that.
Anyone else have this problem?
Sent from my DROID2 using XDA Premium App
I thought I'd start a thread solely dedicated to problems with the upgrade since the announce thread seems to be getting loaded fast.
I'm one of those with problems, but don't know why. The first boot was great. I rebooted, and now stuck in endless boot loop. My tablet is encrypted, so I have to type password initially, then type it again, and I'm at my desktop, but while it's loading apps, it freezes, crashes, and begins all over again. I'm going to try to wipe data to solve this, which sucks because I spent a lot of time putting my app collection together (well, it seemed like a lot of time ) but I need to unstick this.
I would try cold booting it...it may help.
I downloaded the update this morning, it stopped at 95%. I then rebooted and the download finished...went to install it, passed the integrity check but errored our on installing (android with red triangle).
So it booted back into ICS. Went to check for update again and no Update found message....rebooting,cold rebooting, removing the . blob file isnt working...i am stock rooted with stock build.prop.....only thing not stock is the boot animation. Someone help me out or let me know how to manually update this thing....I would really hate to have to factory reset but I am willing to do it as a last resort.
Edit: I had some frozen apps that I forgot to defrost...so anyone that renamed system apps or froze them with titanium...you need to get them back working then reboot before applying the update. Learn from my experience.
stuck on a boot loop too :/ it boots and it after a couple of seconds restarts. Tried doing cold boot once and keeps doing it
Fixed it unnistalling EZoverclock
jgaf said:
stuck on a boot loop too :/ it boots and it after a couple of seconds restarts. Tried doing cold boot once and keeps doing it
Fixed it unnistalling EZoverclock
Click to expand...
Click to collapse
Wish I would have seen that earlier. The wipe helped in the loop regard, but I'm having trouble getting my root back. Checker says no, voodoo acts like it doesn't need to restore anything. I do seem to still have root access via ADB though.
Anyone got any command line knowledge to get things back in order so root checker will show green again?
So far my I/O benchmark scores seem worst than before :/
jgaf said:
So far my I/O benchmark scores seem worst than before :/
Click to expand...
Click to collapse
but does it feel more responsive?
For now it feels about the same, I had a bunch of tweaks that helped the past FW be better, so right now without those tweaks it feels pretty good
I'm wondering if the update changed something on the file system. I have such inside system/cabin but it still says no root access.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I'm experiencing major issues since the update. was rooted w/ a modified build prop file. restored original build.prop file and saved root w/ OTA rootkeeper and unrooted before I upgraded. I even rebooted the tab. The download & install of the JB firmware went flawlass. But now I keep getting the same error messages/force close boxes, one right after the other - process.com.google.gapps, Google Account Manager, among other Google apps (Google Talk, Picassa), also saw an Asus Sync in there. They all appear to be sync and account related apps. I did a factory reset figuring it would clear out all accounts, syncing & whatever is causing the force closings and they still pop up as soon as I boot up to the JB screen. I cant re-add my account b/c Google Account Manager has force closed. Not sure what my options are besides using my warranty and trading this one in. anyone experiencing the same issue and have any ideas on how to solve it?
I haven't tried to get into recovery yet, usually turn off device and power on pressing either volume up or down + power button and see if you can factory reset / wipe dalvik cache from there
tried a factory reset a few times that way, no dice. my bootloader is still locked so I never installed TWRP or CWM to keep my warranty intact or else I'd reflash the JB update. but as it came as an OTA, i think I'm pretty screwed here
This may sound crazy to you, but if you've already wiped then it doesn't matter. Go and get the .30 firmware from Asus, extract the first zip into root of sdcard, the extract will be a zip too. Tablet should pick it up, think its a downgrade and prompt you to continue. It reloads, but when finished you will still be on jellybean. That's what I did to solve another problem and that was the result. Not what I wanted but it might help you.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
This may sound crazy to you, but if you've already wiped then it doesn't matter. Go and get the .30 firmware from Asus, extract the first zip into root of sdcard, the extract will be a zip too. Tablet should pick it up, think its a downgrade and prompt you to continue. It reloads, but when finished you will still be on jellybean. That's what I did to solve another problem and that was the result. Not what I wanted but it might help you.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
that does sound pretty crazy, but I'm crazy enough to try it. what issue were you having that you thought to try this method? and did it solve it. "not what I wanted" makes me think it didn't help you. so you say it picks it up like a downgrade, but doesn't actually downgrade anything? i'm thinking the upgrade didn't go thru correctly and some system apps didn't update properly causing all my issues. I even called ASUS to RMA this pad, they didn't even know the JB update was rolling out, telling me the lastest OTA was still ICS. they are clueless.
Is it possible to downgrade to previous firmware to restore all of my originally installed apps? It seems if you root, then uninstall system apps the jellybean update fails. I factory reset, but it seems that whatever you uninstall or modify doesn't get restored that way. I'm reluctant to go through pushing .30 over via adb. Is there a way I can just drop an update.zip on my internal sdcard and reboot into recovery somehow? Any help would be greatly appreciated. I'm pretty confident I can root jelly bean by manipulating the file system. I'll leave that for later. Just waiting for CM10 to become a bit more stable before pulling that trigger. The asus firmware isn't so bad anyways. So....how do I "downgrade" to .30 or even .29 and restore the tablet to pure factory???
AFAIK you can't, you need to find out what system apps you removed and push them back using adb then reboot
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
jgaf said:
AFAIK you can't, you need to find out what system apps you removed and push them back using adb then reboot
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Surely I can take a factory blob and push it over. I'm looking at a downgrade guide now. The blob is over 300 megs. Surely it has all the system apps with it.
The full ICS blob was 800MB. The upgrade.zip for the JB update alone was 300MB using patch.
The problem I am having is some weird force closes in the Settings app. But nothing too major there.
I came from a fully stock ICS, so the improvement in browsing (Chrome, especially) is much better.
There are still some stuttering in the OS, but overall I am pleased with the improvements.
I am finding that I cannot change the keyboard locale when attached to the dock. THis isn't a huge deal for me though.
paedz718 said:
that does sound pretty crazy, but I'm crazy enough to try it. what issue were you having that you thought to try this method? and did it solve it. "not what I wanted" makes me think it didn't help you. so you say it picks it up like a downgrade, but doesn't actually downgrade anything? i'm thinking the upgrade didn't go thru correctly and some system apps didn't update properly causing all my issues. I even called ASUS to RMA this pad, they didn't even know the JB update was rolling out, telling me the lastest OTA was still ICS. they are clueless.
Click to expand...
Click to collapse
My issue was...
I was rooted on .30. After the update to jb I got stuck in a reboot loop. It got to the desktop then crashed.
Thought I could resolve by wiping data. When I did that, lost root and cannot get it back due to updates to the permissions of the /data folder.
So I thought why not try and reinstall .30. And you know my result.
I learned later my looping was most likely caused by the ezoverclock app, but I read that too late. So I'm on jb without root and appear to be stuck that way until another exploit is found or I unlock the boot loader.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
gotcha. I can't even get past the Google account screen, that crashes immediately. I tried loading the .30 firmware on the SD card but since I can't get to the desktop, it won't pick it up to update. I can only get to the settings screen. I could probably unlock the bootloader and flash another ROM to get me thru this, but I'd like to keep it locked. going to get this RMA'd as soon as their system gets back up.
paedz718 said:
gotcha. I can't even get past the Google account screen, that crashes immediately. I tried loading the .30 firmware on the SD card but since I can't get to the desktop, it won't pick it up to update. I can only get to the settings screen. I could probably unlock the bootloader and flash another ROM to get me thru this, but I'd like to keep it locked. going to get this RMA'd as soon as their system gets back up.
Click to expand...
Click to collapse
Perhaps there is one more thing you can try.
As part of the update the bootloader got updated. I was playing with this last night and I see a new USB graphic to choose. If you select it you can engage the tablet via fastboot. Now other than initial contact and a couple of minor test commands I didn't do anything with it, but perhaps you could flash the ROM with that?? It will load USB drivers for boot loader interface when you do this the first time.
BTW if you don't know, hold power and vol down to get to it, then when you see the graphics keep pressing vol down until the USB symbol lights up, then press vol up.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
i have a nexus thats completely stock( out of the box) worked fine for about a month, let the tablet die and has been unplugged for about a week. got it charged up and and would not turn on. using the nexus root toolkit i was able to get to turn on. unlocked the device( unlock logo below google icon on startup) was unable to get past that point. now finally i can get past the nexus boot logo but it gets stuck on aindroid is upgrading " optimizing app 1 of 11" i cant root using the root tool kit bc when i unlocked device it got rid of developer options ( by what the msg said before i unlocked). im simply trying to get my device to turn back on. i dont plan to root or install a rom, im fine with the stock rom. i just want to damn device to turn back on. when i was able to power on the device when i first got it i did upgrade to the newest jelly bean rom. any one can help me on this issue ??
thanks
Boot into temporary custom recovery using Nexus root toolkit(Advance menu). Now wipe cash and devlock than try rebooting into system. If it doesn't work you can try factory reset. Last but not the least will be Flash Stock + Unroot(Soft brick/boot loop).
ok i wiped cache and devlock was able to to pass the nexus logo into what looks like another android is upgrading screen it got up to 14 of 20 and froze. between my 1st post and yours i was able to get android to fully run. did all the 1st time setup but after about a couple screen taps the device kept freezing and coming up with crash reports. there were a few times that the stock launcher even forced close. after a couple of restarts it finally quit again and would not even pass the nexus logo. ill try to do the other options that u stated in your post. any other thoughts ?
dac2009 said:
ok i wiped cache and devlock was able to to pass the nexus logo into what looks like another android is upgrading screen it got up to 14 of 20 and froze. between my 1st post and yours i was able to get android to fully run. did all the 1st time setup but after about a couple screen taps the device kept freezing and coming up with crash reports. there were a few times that the stock launcher even forced close. after a couple of restarts it finally quit again and would not even pass the nexus logo. ill try to do the other options that u stated in your post. any other thoughts ?
Click to expand...
Click to collapse
If the factory reset doesn't work just go for the Flash. I don't think you are much worried about the data so it's not a big deal for you. and I'm quit sure this is gonna work. Best of luck.
ok did that. went smooth but then once again it just gets stuck at the nexus logo. waited for over 10 mins like the notes say after re flashing and nothing. so i did a restart this time it passed the nexus logo, went to android is upgrading optimizing app and gets stuck at 4 of 11. being that this is pure android are there custom roms out there that i could try to flash via odin. ive rooted and installed roms before on my other android devices no problem but they were never pure google. am i missing something here. also what would cause a brand new nexus 7 just to go "ape ****" on its self.
dac2009 said:
ok did that. went smooth but then once again it just gets stuck at the nexus logo. waited for over 10 mins like the notes say after re flashing and nothing. so i did a restart this time it passed the nexus logo, went to android is upgrading optimizing app and gets stuck at 4 of 11. being that this is pure android are there custom roms out there that i could try to flash via odin. ive rooted and installed roms before on my other android devices no problem but they were never pure google. am i missing something here. also what would cause a brand new nexus 7 just to go "ape ****" on its self.
Click to expand...
Click to collapse
Okay, that's weird!!!
Are you using Nexus Root Toolkit?? If yes are you using pre-downloaded android??
Try Automatically download + Extract.....
Last of all I'm really confused how there could be a problem when you got a fresh OS and Stock.
I agree with the messing thing that you told... Try checking and double checking everything... Check if you have selected the correct device or not.
And do a full wipe(including system) using TWRP before flashing again.
Edit: Make sure you are using the latest toolkit. You can get it from the link bellow.
http://forum.xda-developers.com/showthread.php?t=1766475
Try flash stock image throught toolkit.
i have the most current root toolkit. i installed the rom that was available to download via the app which was android 4.2.2 jdq39
dac2009 said:
i have the most current root toolkit. i installed the rom that was available to download via the app which was android 4.2.2 jdq39
Click to expand...
Click to collapse
I don't see a way how the problem still exists... :S
Whatever the problem is it's seems to be with android OS. But how it exists in completely new android. Sorry can't find a reason behind the problem. You can still try flashing any older android (like 4.1.2).
ok i got a zip of stock 4.1.2 and using the root tool kit i can install a zip via the twrp but it wont let me bc it says adb device not found and that developer options need to be turned on. im un able to turn it on bc i cant even get into the rom on the device.
thanks
ok i got it working. i was able to flash the older rom to my device and its working so far. no force closes yet.
thanks for everyone's help
ok im about to throw this tablet out the window. was messing around with the tablet and it auto installed ( well at least tried to) the 4.2 update. it downloaded the update went to install and now im stuck at this screen(check pic) and cant even get it into recovery mode. im at the point now to cut my loss and say the hell with it. anyone else have any ideas on whats my next step. the thing that wireds me out is of the roms ive been able to use it all works great for only about 5 mins. it seems like the more i touch the screen to do anything it will freeze on me(it will do it after 5 mins or so after a restart). https://www.dropbox.com/s/arnauysa4oglp5b/2013-05-21%2018.37.24.jpg
dac2009 said:
ok im about to throw this tablet out the window. was messing around with the tablet and it auto installed ( well at least tried to) the 4.2 update. it downloaded the update went to install and now im stuck at this screen(check pic) and cant even get it into recovery mode. im at the point now to cut my loss and say the hell with it. anyone else have any ideas on whats my next step. the thing that wireds me out is of the roms ive been able to use it all works great for only about 5 mins. it seems like the more i touch the screen to do anything it will freeze on me(it will do it after 5 mins or so after a restart). https://www.dropbox.com/s/arnauysa4oglp5b/2013-05-21 18.37.24.jpg
Click to expand...
Click to collapse
I can't just think of anything else. Just telling you the things that I'd have done if I were you.
* reinstall boot
* change kernel
* turn off the auto update of android.
* try some costume room.
Don't throw it out the window you call always donate it to me if you really wanna throw it or make a drop test video...
Last of all just don't lose hope keep trying. you'll find out something surely and share it with us.
Sent from my Nexus 7 using XDA Premium HD app
Daft question, but the few times you managed to get it running, was your Wifi on?
Sent from my GT-I9300 using xda app-developers app
yes my wifi was on and was able to stream . spotify among other things
Not the exact same situation, but I found certain Wifi router's would trip my nexus into reboots until I rooted
Sent from my GT-I9300 using xda app-developers app
Phone is stuck in "Android is upgrading. Optimizing application 1 of 1" HELP!!!!!!!!!
hey guys, my phone is stuck in "Android is upgrading. Optimizing application 1 of 1"
and all I can do is
1. apply sdcard/update.zip
2. reboot system now ( does NOT work coz it brings me back to optimizing apps )
3. apply update from external storage
4. wipe data / factory reset
5. wipe cache partition
6. apply update from cache
is there a way i can backup first all my files before factory resetting my phone (if thats the only option i have)????
help me please
Please someone help me or tell me who I can PM to help please.
Yesterday my razR M was just randomly rebooting, it stop doing this after about 5 reboots. I then proceeded to fully charge my phone twice to do the radiocomm edit and root, using DROID RAZR M Utility 1.20 since i'm on 4.1.2 *I did not factory reset*, the phone so that the battery wouldn't die while doing either and mess up the phone. I was trying to do the entitlement edit with all free file managers with root permissions which didn't work and I realized my phone was freezing while doing simple tasks (during boot animation, inputting password to unlock phone, switching between homescreens and opening app drawer) and rebooting.
It wasn't turning on or showing any indication of being plugged in, but while I was writing this it just magically went to the battery percentage indicator and I was able to turn it on and after about 20 seconds of being booted the led indicator is flashing green again.
I can't have this happen next week when I'm on my trip, I won't have the time and my access to computers and internet will be limited. If anyone knows what could be causing this and or how to fix it PLEASE TELL ME
Update (3:25 AM): IT HAPPENED AGAIN, ready to cry want to try to flash back to stock but don't know how
Update #2 (4:13AM): So after a lot of button pressing I got it stuck on the red m then eventually into the bootloader; saw that the random reboots is not unusual for razr hd/maxx hd users on 4.1.2 with the only way to fix being to flash to CM10. Also realized that i'm not the only one whose phone requires a soft reset to charge/boot, no longer contemplating flashing back to stock seeing as i'll probably still have the reboots
ccdsatt said:
Please someone help me or tell me who I can PM to help please.
Yesterday my razR M was just randomly rebooting, it stop doing this after about 5 reboots. I then proceeded to fully charge my phone twice to do the radiocomm edit and root, using DROID RAZR M Utility 1.20 since i'm on 4.1.2 *I did not factory reset*, the phone so that the battery wouldn't die while doing either and mess up the phone. I was trying to do the entitlement edit with all free file managers with root permissions which didn't work and I realized my phone was freezing while doing simple tasks (during boot animation, inputting password to unlock phone, switching between homescreens and opening app drawer) and rebooting.
It wasn't turning on or showing any indication of being plugged in, but while I was writing this it just magically went to the battery percentage indicator and I was able to turn it on and after about 20 seconds of being booted the led indicator is flashing green again.
I can't have this happen next week when I'm on my trip, I won't have the time and my access to computers and internet will be limited. If anyone knows what could be causing this and or how to fix it PLEASE TELL ME
Update (3:25 AM): IT HAPPENED AGAIN, ready to cry want to try to flash back to stock but don't know how
Update #2 (4:13AM): So after a lot of button pressing I got it stuck on the red m then eventually into the bootloader; saw that the random reboots is not unusual for razr hd/maxx hd users on 4.1.2 with the only way to fix being to flash to CM10. Also realized that i'm not the only one whose phone requires a soft reset to charge/boot, no longer contemplating flashing back to stock seeing as i'll probably still have the reboots
Click to expand...
Click to collapse
not sure if your situation has been resolved, but it appears that the battery just drained all the down. from that point, you need to plug in your phone (into an outlet, not computer), and leave it alone for a good 30 minutes (don't even look at it).
from that point, you should be able to enter the Rom by powering up or recovery via volume up + volume down + power.
if you are still having troubles, you might be best to simply perform a hard reset (I think you can do that from the stock recovery menu).
after you are able to do that, I would suggest to root, unlock bootloader, install TWRP. then setup your phone settings to your liking, then go back into recovery and make a backup. i have soft-bricked my phone several times, and entering TWRP recovery and restoring my previous setup has helped every time.
Its OK now
jco23 said:
not sure if your situation has been resolved, but it appears that the battery just drained all the down. from that point, you need to plug in your phone (into an outlet, not computer), and leave it alone for a good 30 minutes (don't even look at it).
from that point, you should be able to enter the Rom by powering up or recovery via volume up + volume down + power.
if you are still having troubles, you might be best to simply perform a hard reset (I think you can do that from the stock recovery menu).
after you are able to do that, I would suggest to root, unlock bootloader, install TWRP. then setup your phone settings to your liking, then go back into recovery and make a backup. i have soft-bricked my phone several times, and entering TWRP recovery and restoring my previous setup has helped every time.
Click to expand...
Click to collapse
My phone was always 100% percent charged as I wanted to do stuff with the utility. After getting it into safemode, where it still froze and rebooted twice each time I booted into the mode, I got to power off then turn off then back on the regular way and left it on and has been fine since then. I currently have safestrap and cm10 zip on the phone in the event it acts up again. I backed up using safestrap like suggested. I haven't unlocked the bootloader yet, I have the app installed though, as I saw something from one of the devs for my previous moto device that said that if your bootloader is unlocked and we get another OTA and install* it our phones could get messed up.
*I know I can just install a stock 4.2 ROM*
ccdsatt said:
My phone was always 100% percent charged as I wanted to do stuff with the utility. After getting it into safemode, where it still froze and rebooted twice each time I booted into the mode, I got to power off then turn off then back on the regular way and left it on and has been fine since then. I currently have safestrap and cm10 zip on the phone in the event it acts up again. I backed up using safestrap like suggested. I haven't unlocked the bootloader yet, I have the app installed though, as I saw something from one of the devs for my previous moto device that said that if your bootloader is unlocked and we get another OTA and install* it our phones could get messed up.
*I know I can just install a stock 4.2 ROM*
Click to expand...
Click to collapse
well, most folks are going via the TWRP recovery route now (and I believe that all custom ROMs going forward will be flashable this way only, and not SS).
you will find that using TWRP is much easier than SS
jco23 said:
well, most folks are going via the TWRP recovery route now (and I believe that all custom ROMs going forward will be flashable this way only, and not SS).
you will find that using TWRP is much easier than SS
Click to expand...
Click to collapse
I realized that while looking at roms this afternoon. Before I go down the custom route though do you know if it affects the usage of gsm there are no CDMA carriers in Jamaica so I can't flash to anything?
Sent from my XT907 using xda app-developers app
ccdsatt said:
I realized that while looking at roms this afternoon. Before I go down the custom route though do you know if it affects the usage of gsm there are no CDMA carriers in Jamaica so I can't flash to anything?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Most of the ROMs need a gsmfix zip flashed, but they'll work on GSM with that
Sent from my Nexus 7 using Tapatalk HD
Ok, I'm still a noob when it comes to Android.
I have a rooted Sprint S4 on the OTA MJA update and TWRP Recovery 2.6.3.0.
I want to know how to get ROM Toolbox to perform the randomly selected boot animations I have downloaded from ROM Toolbox application itself.
What do I need to do get the random boot animations to work when the phone reboots because it is still showing the same Samsung/Sprint boot animations?
Cookbook instructions please.
TIA
I thought xda was supposed to be the place to go for help, even for noobs, guess I was wrong...not a single reply. :'(
mrrsquared1979 said:
I thought xda was supposed to be the place to go for help, even for noobs, guess I was wrong...not a single reply. :'(
Click to expand...
Click to collapse
XDA favors those who search. It's NOT a support/help site. Though most go out of their way to help those that help themselves.
Okay </preach>
So you can try starting here. This enabled me to use my cutom boot animation zips. One thing to make sure is that you have the right screen size on any images (1080 1920) you are planning on using for this device - wrong screen size can send you into a bootloop that requires a nandroid restore.
And here.
With the stock (Odexed) ROMs it is often more difficult to use custom boot animations they might not always work (or you'll have to delete the qmg files first)
leaderbuilder said:
XDA favors those who search. It's NOT a support/help site. Though most go out of their way to help those that help themselves.
Okay </preach>
So you can try starting here. This enabled me to use my cutom boot animation zips. One thing to make sure is that you have the right screen size on any images (1080 1920) you are planning on using for this device - wrong screen size can send you into a bootloop that requires a nandroid restore.
And here.
With the stock (Odexed) ROMs it is often more difficult to use custom boot animations they might not always work (or you'll have to delete the qmg files first)
Click to expand...
Click to collapse
Seems I am getting farther down the rabbit hole, now running TriForceROM 5.0 and that has proved to have an improved battery life.
mrrsquared1979 said:
Seems I am getting farther down the rabbit hole, now running TriForceROM 5.0 and that has proved to have an improved battery life.
Click to expand...
Click to collapse
You may need the ktoonsez kernel from the TF5.0 aroma. Then download the boot animation you want from your Rom Manager then install through your recovery, wipe cache and dalvik and fix permissions, reboot.
Haven't done this yet on TF5.0 but that's exactly how I did it on the last release. Went with the golden skull and bones. Not sure if you can get it to toss up a random one on each reboot though on the S4. Think RM was focused on a different set of phones altogether so maybe all the options in it won't play nice with the S4, just thinking out loud.
Or do what leaderbuilder said
I'm still trying to make my own, have to make time though. A lot of it.
Sent from my SPH-L720 using xda app-developers app
I seem to really like the one where the android is urinating on the Apple.