Related
Can anyone tell me how to get the original boot animation back on a bootlooping d3. Then I could return it
Nevermind xda please erase. Verizon is sending me a new phone
Sent from my DROID2 using Tapatalk
How did you fix it
Sent from my DROID3 using xda premium
I didn't yet
Sent from my DROID2 using Tapatalk
with any luck, you'll get charged for it.
for anyone who wants to actually fix it themselves; power down, hold x and power to boot into recovery, wipe data and cache. problem solved.
You're weak.
brewcrewwheels said:
with any luck, you'll get charged for it.
Click to expand...
Click to collapse
Amen. Don't ruin it for the rest of us. Learn SBF, etc, or get out.
sparkyman216 said:
Can anyone tell me how to get the original boot animation back on a bootlooping d3. Then I could return it
Nevermind xda please erase. Verizon is sending me a new phone
Sent from my DROID2 using Tapatalk
Click to expand...
Click to collapse
I would like to thank you for being one of those people who abuse the system and ruin it for us all. By what you are doing has forced carriers to want to ban rooting and other fun stuff we have right now. I hope vzw charges you out the rear end for this. I may just submit this link tixs vzw so they can be on the look out for your phone and charge you. Thanks again for being a idiot and not owning up to your mistake w/ vzw.
Oh and I really don't care what you think of me or my response. I am sick of you people.
brewcrewwheels said:
with any luck, you'll get charged for it.
for anyone who wants to actually fix it themselves; power down, hold x and power to boot into recovery, wipe data and cache. problem solved.
Click to expand...
Click to collapse
That doesn't fix lol, that's just making it worse cuz then ur losing adb.
But then I completely agree about the 1st part.
Sent from my DROID3 using xda premium
yeah, i was talking out of my ass with that. i mean, it fixes bootloops on just about every other droid. the point is, there is no way it's unfixable. based on the fact the op is posting from a d2 shows he has a backup. do some reading or ask around. don't be a douche and just send it back because you don't know what you're doing.
WHAT!!!! DON'T DO THAT AT ALL. LOSE ADB? LOL
Wipe data/factory reset is the answer.
IF your phone is bricked, and YOU caused it, you deserve to be charged for any replacement phone. And I hope that if you receive a new one, you don't tinker with it at all.
frenetic said:
WHAT!!!! DON'T DO THAT AT ALL. LOSE ADB? LOL
Wipe data/factory reset is the answer.
IF your phone is bricked, and YOU caused it, you deserve to be charged for any replacement phone. And I hope that if you receive a new one, you don't tinker with it at all.
Click to expand...
Click to collapse
The boot animation is stored in /system/framework -- wiping data (factory reset) erases your /data and /cache partitions and re-runs preinstall (if any). This will not fix your boot animation if you modified it.
It's true that you will lose ADB on a factory reset because your preference for 'USB Debugging' is saved in /data. Simply turn it back on to re-gain ADB access.
I 100% agree that people abuse the lost/stolen phone route of having a replacement device sent when they're the ones that screwed it up.
He's bootlooping though, and he can't turn it back on if he wipes
Sent from my DROID3 using xda premium
psouza4 said:
The boot animation is stored in /system/framework -- wiping data (factory reset) erases your /data and /cache partitions and re-runs preinstall (if any). This will not fix your boot animation if you modified it.
It's true that you will lose ADB on a factory reset because your preference for 'USB Debugging' is saved in /data. Simply turn it back on to re-gain ADB access.
I 100% agree that people abuse the lost/stolen phone route of having a replacement device sent when they're the ones that screwed it up.
Click to expand...
Click to collapse
I don't think he'd be returning it if it wasn't bootlooping
Is a sbf available for it? Ask team black hat. Don't return it your screwing us all
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sparkyman216
way to abuse the system timmy
This is why we can't have nice things...
Morse coded via my DROID 3
sparkyman216 said:
Can anyone tell me how to get the original boot animation back on a bootlooping d3. Then I could return it
Nevermind xda please erase. Verizon is sending me a new phone
Sent from my DROID2 using Tapatalk
Click to expand...
Click to collapse
Please do everyone here a favor and trade your D3 for an iPhone...
sic4672 said:
Please do everyone here a favor and trade your D3 for an iPhone...
Click to expand...
Click to collapse
LOL really though..
psouza4 said:
The boot animation is stored in /system/framework -- wiping data (factory reset) erases your /data and /cache partitions and re-runs preinstall (if any). This will not fix your boot animation if you modified it.
It's true that you will lose ADB on a factory reset because your preference for 'USB Debugging' is saved in /data. Simply turn it back on to re-gain ADB access.
I 100% agree that people abuse the lost/stolen phone route of having a replacement device sent when they're the ones that screwed it up.
Click to expand...
Click to collapse
FYI, the bootanimation is in /system/media.
How and why this dude is getting the error is beyond me, even moreover why he thinks replacing the bootanimation will fix his errors escapes me.
hte only way bootanimation if fixed with wipe is if you placed your boot ani in the /data/local/ folder then it gets cleared and lets the original boot run...
NyghtGT said:
FYI, the bootanimation is in /system/media.
How and why this dude is getting the error is beyond me, even moreover why he thinks replacing the bootanimation will fix his errors escapes me.
Click to expand...
Click to collapse
He's bootlooping and wants to return the phone and dupe VZ, but he changed the stock BA (clear giveaway of being rooted)
morse coded via my DROID 3
Has anyone tried this yet? http://www.gottabemobile.com/2012/04/18/droid-4-update-brings-better-battery-life-backlight-fixes/
I downloaded last night, installed Voodoo Rootkeeper, unfroze any apps that I had frozen, and then chickened out. LOL! I'm not sure what this will do with safestrap installed. Makes me a little nervous with no fastboot files.
I'm thinking it might be best to uninstall safestrap first and then apply the update. Any thoughts anyone?
On the D3, I would switch to non-safe system, apply the update in recovery, reboot, re-root, reinstall safestrap recovery from the safestrap app, reboot into safestrap, switch back to safe and everything was peachy. No need to even reinstall safe system as everything was still there. Did it twice for the 905 and 906 updates, dont see why it would be any different for the D4
EDIT: the only difference I may have is that I keep my non-safe system stock, I dont freeze/remove bloat, just root.
Glad to see wifi is on the list of bug fixes. I haven't been able to connect to my work wick, and my home wifi drops all the time (tethering from phone works perfectly though,go figure).
I probably will wait until this officially drops, though. Bleh, why no fastboot files yet?!
The download has been pulled anyone have this file they can upload elsewhere?
swjpilot said:
The download has been pulled anyone have this file they can upload elsewhere?
Click to expand...
Click to collapse
http://db.tt/YIiI5SU3
Sent from my DROID4 using XDA
kwyrt said:
http://db.tt/YIiI5SU3
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Thanks!!! Got it!
Just rebooted after applying the update. I'm running stock ROM. I unfroze everything I had frozen, hid root w/ Voodoo OTA, rebooted, did a backup (just in case), applied the update, restored root with Voodoo OTA and everything appears to be working.
Hope this really does fix the wifi problem. Been having some problems with the wifi here at work.
Took the plunge. I was running stock rooted with voodoo rootkeeper and safestrap recovery installed. Here are the steps I took:
1. Unfroze apps I had frozen in Titanium Backup.
2. Uninstalled safestrap recovery via the safestrap app (Shouldn't need to uninstall the app itself).
3. Backed up Superuser using Voodoo then selected "temp. un-root".
4. Rebooted and installed the update via the instructions from the link (FYI: You will need to have the update zip in /sdcard-ext, not /sdcard).
5. Rebooted and the phone shows the updated software version.
6. Restored root via Voodoo.
7. Reinstalled safestrap recovery using the safestrap app.
Success!
Wifi still dropping off randomly. I don't think this phone likes the 802.1xEAP security they are using here. Droid incredible worked just fine on it though.
Sent from my DROID4 using Tapatalk 2
Do you have to remove root to apply this?
I wonder why it was posted and then removed? Anyone?
redddog said:
Do you have to remove root to apply this?
I wonder why it was posted and then removed? Anyone?
Click to expand...
Click to collapse
Cuz it is still in soak test, which is confidential. Motorola doesn't want it out there in the wild yet.
You have to use voodoo root keeper. If you flash the update without voodoo root keeper you will lose root. But motofail still works so you can always reroot
Sent from my DROID4 using Tapatalk 2
i just got an update today but it downloads 215 not 219.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my DRIOD 4 Husky Edition
Question:
I updated my original, non-safe system just fine. Kept root, reinstalled safestrap no problems. However, upon switching back to my safe-system it loads the safe-system before the update. I don't know how to reset my 2nd system to match the non-safe system, and I don't dare trying to install the update while using safestrap. Is there anyway to get this updated system to carry over to my safe-system? Or do I need to wait until someone makes a ROM to flash?
Thanks in advance!
Sent from my DROID4 using telepathy
The Magician Type 0 said:
Question:
I updated my original, non-safe system just fine. Kept root, reinstalled safestrap no problems. However, upon switching back to my safe-system it loads the safe-system before the update. I don't know how to reset my 2nd system to match the non-safe system, and I don't dare trying to install the update while using safestrap. Is there anyway to get this updated system to carry over to my safe-system? Or do I need to wait until someone makes a ROM to flash?
Thanks in advance!
Sent from my DROID4 using telepathy
Click to expand...
Click to collapse
I assume you are running stock GB on your non-safe system then? If that is the case the easiest way I could see to update it to the new software version would be to make a backup of your non-safe system, then flash that to your safe system, just don't wipe data and it shouldn't mess up your current configuration.
kwyrt said:
I assume you are running stock GB on your non-safe system then? If that is the case the easiest way I could see to update it to the new software version would be to make a backup of your non-safe system, then flash that to your safe system, just don't wipe data and it shouldn't mess up your current configuration.
Click to expand...
Click to collapse
Yeah, stock Motoblur on the latest update. I had considered that, but wasn't sure I could flash a non-safe backup to the safe system. I'll give it a try and hope for the best.
Thanks!
Sent from my DROID4 using Carrier Pigeons
So I tried just that, restoring the non-safe backup to the safe system. Everything transfered over, apps, data, etc. Except, the safe system is still on the original .215, not .219...
I don't know then. That was my best guess. Not sure why it wouldn't work. You made a fresh backup of your non-safe system after the update and flashed that, right?
Sent from my DROID4 using XDA
Yes, and I'm confused as well. One would think the ability to transition between ROMs switching GB and ICS, a simple little upgrade would work as well. I guess I'll wait for a ROM version or something, not that I really need this update, I just like being on top of things.
Does anyone have the 6.13.219.XT894 patch instead of the 6.13.215.XT894 patch that is floating around?
Thanks!
edit: solved. read later posts for details.
OK.
So I sold my unlocked droid 3 ( the verizon droid with the tut ) and everything worked great for me on AT&T.
So I sell it on ebay and the person contacts me saying it sais " sim not found" or whatever on it. HOWEVER he sais hes trying to use it on the AT&T gophone plan...
I know this isnt AT&T ( its just a seperate service provided by them ), but should it still work or would u think its incompatible?
I DONT KNOW IF IT MATTERS but before I shipped it out i did a factory restore via safestrap or whatever. ( it wipes /data ). Would that also change the radio back to the verizon one?
If this is my fault i would sadly have to take a return but if its fixable or what?
I gave her the gophone apn but i doubt that would help.
Was the backup done when running stock? If so then from my understanding the radio was replaced with the stock radio
Sent from my iPad using Tapatalk HD
KayxGee1 said:
Was the backup done when running stock? If so then from my understanding the radio was replaced with the stock radio
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
no, the backup was done on Mavrom 4.0
All a factory reset does is wipe /data and /cache. It would not touch the radio.
Sent from my XT860 using xda premium
Allright well I have no idea whats going on with the phone.
She tried to do a factory reset via the phones menu, which you are not supposed to do with a rooted phone, and it booted up but it wouldnt let her touch the android continue button...
SO I told her to restore it in safestrap using the backups i made
and now supposedly it kinda works again, but at the lockscreen, their is no "slide to unlock" button...
dufaq? i bet im going to have to refund her now -_-
Juicy555 said:
Allright well I have no idea whats going on with the phone.
She tried to do a factory reset via the phones menu, which you are not supposed to do with a rooted phone, and it booted up but it wouldnt let her touch the android continue button...
SO I told her to restore it in safestrap using the backups i made
and now supposedly it kinda works again, but at the lockscreen, their is no "slide to unlock" button...
dufaq? i bet im going to have to refund her now -_-
Click to expand...
Click to collapse
A factory reset isn't always a bad thing on a rooted phone. It just depends on what you've done to the phone. You can bypass the Android button by pressing all 4 corners of the screen, in I believe clockwise. I find I have to do it several times before it works.
Sent from my GT-P5113 using XDA Premium HD app
Juicy555 said:
OK.
So I sold my unlocked droid 3 ( the verizon droid with the tut ) and everything worked great for me on AT&T.
So I sell it on ebay and the person contacts me saying it sais " sim not found" or whatever on it. HOWEVER he sais hes trying to use it on the AT&T gophone plan...
I know this isnt AT&T ( its just a seperate service provided by them ), but should it still work or would u think its incompatible?
I DONT KNOW IF IT MATTERS but before I shipped it out i did a factory restore via safestrap or whatever. ( it wipes /data ). Would that also change the radio back to the verizon one?
If this is my fault i would sadly have to take a return but if its fixable or what?
I gave her the gophone apn but i doubt that would help.
Click to expand...
Click to collapse
I don't know anything about at&t, since I live in Canada, I tried to find out what spectrum go phone uses, I imagine it's the same as at&t but really, really who knows. Have them try the *#*#4636#*#* and make sure it's on gsm auto. I'm afraid I can't help too much on this, I've never had to do the radio hack, plus I have no idea what you have done with the phone or what this person has done.
If they are working in safe mode, and assuming you never flashed or modded the non safe, have them switch to it. The radio hack should work no matter what mode they are in. You could try getting them on XDA and part of this thread, for more direct assistance
Sent from my GT-P5113 using XDA Premium HD app
Endoroid said:
I don't know anything about at&t, since I live in Canada, I tried to find out what spectrum go phone uses, I imagine it's the same as at&t but really, really who knows. Have them try the *#*#4636#*#* and make sure it's on gsm auto. I'm afraid I can't help too much on this, I've never had to do the radio hack, plus I have no idea what you have done with the phone or what this person has done.
If they are working in safe mode, and assuming you never flashed or modded the non safe, have them switch to it. The radio hack should work no matter what mode they are in. You could try getting them on XDA and part of this thread, for more direct assistance
Sent from my GT-P5113 using XDA Premium HD app
Click to expand...
Click to collapse
Yes I remember safestrap was always on... so if i tell her to turn it OFF it will still work on AT&T?
Can someone give me detailed instructions i can use? I dont have a droid 3 on me and would appreciate it beacuse i cant see it anymore.
sorry for the double post, but she also said she tried the "4 corners" thing, but then it said android something has stopped working...
then it went back to the lockscreen with no "slide to unlock" button... sooo weird..
Juicy555 said:
Yes I remember safestrap was always on... so if i tell her to turn it OFF it will still work on AT&T?
Can someone give me detailed instructions i can use? I dont have a droid 3 on me and would appreciate it beacuse i cant see it anymore.
Click to expand...
Click to collapse
Reboot
Press menu when the safestrap splash screen shows up
Using the volume up/down highlight safe boot menu and power to select
Toggle safe mode
If for some reason this fails(I've had it happen) you can use quick toggle but you MUST factory reset after
When done select reboot
Radio is totally separate from the rom. However I know that the radio hack needs build.prop edits, we will have to think of an easy way for her to do this. Let me ponder
Sent from my XT860 using xda premium
Endoroid said:
Reboot
Press menu when the safestrap splash screen shows up
Using the volume up/down highlight safe boot menu and power to select
Toggle safe mode
If for some reason this fails(I've had it happen) you can use quick toggle but you MUST factory reset after
When done select reboot
Radio is totally separate from the rom. However I know that the radio hack needs build.prop edits, we will have to think of an easy way for her to do this. Let me ponder
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
The build.prop is already installed. Will that change when , or if she switches to non-safe mode?
I have already have her factory reset ( inside safestrap ), and wipe the cache but still nothing.
Juicy555 said:
The build.prop is already installed. Will that change when , or if she switches to non-safe mode?
I have already have her factory reset ( inside safestrap ), and wipe the cache but still nothing.
Click to expand...
Click to collapse
Safe and non safe are totally separate. So if you put the build.prop changes in one mode, it won't have gone into the other. So it all depends on if you made the edits in non safe or not. Same goes for factory reset. When you switch modes it backs up and restores the /data and /cache for each mode. The only reason I say to factory reset if she quick toggles is because it doesn't do this backup/restore when you quick toggle, which will almost certainly cause problems. If the regular toggle works there is no need to factory reset.
I should ask, did you doing any modding, flashing, or even use the non safe. Ie did you use it a bunch before installing safestrap and switching to safe
Sent from my XT860 using xda premium
Endoroid said:
Safe and non safe are totally separate. So if you put the build.prop changes in one mode, it won't have gone into the other. So it all depends on if you made the edits in non safe or not. Same goes for factory reset. When you switch modes it backs up and restores the /data and /cache for each mode. The only reason I say to factory reset if she quick toggles is because it doesn't do this backup/restore when you quick toggle, which will almost certainly cause problems. If the regular toggle works there is no need to factory reset.
I should ask, did you doing any modding, flashing, or even use the non safe. Ie did you use it a bunch before installing safestrap and switching to safe
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
No. Phone was flashed to mavrom 4.0 before an worked fine. I took my sim out, and didnt use it for a week or so. When she bought it, i did a factory reset / wipe data so it was ready for a new person. I had never switched it out of the mode it was in.
She sent me a message saying it would not detect her sim, and i said its probally something wrong with her sim ( not enough pressure on sim contacts ).
Then she contacted me saying she did a factory restore IN THE SETTINGS MENU IN PRIVACY... which you are not supposed to do... THEN it would not let her touch the "press android to continue" thing when you first set it up. I told her to do the press the corners trick and then she said it worked for a second and then the touch screen just "stopped" working... an it said android force closed and went to a lock screen that didnt have the slide to unlock slider
NOW she is saying after restoring the backup i did before shipping it out ( the backup was done while it was working , i actually made 2 backups to internal and external ) that there is no "slide to unlock" button.
dufaq is going on?
Here is the pic she sent me...
im not even sure if i got this back I could fix it!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
edit: http://postimage.org/image/vqfeg9da7/
Juicy555 said:
Here is the pic she sent me...
im not even sure if i got this back I could fix it!!!
edit: http://postimage.org/image/vqfeg9da7/
Click to expand...
Click to collapse
Well a sbf would fix it, but that would undo the radio hack, as it would flash a new radio. You could motofastboot just /system and /preinstall, which would leave the radio intact, but i don't know how tech capable she is, to use fastboot. Not that it's really difficult, but you do need to kinda know your way around a computer a bit. That would remove safestrap and would make it out of the box new, albeit still with the modded radio. Also would need the build.prop edits still.
I could actually mod ovelayers 1-click to flash all but the radio probably. I'm fairly sure that would fix all problems without Causing anymore maybe ill pm him the link to this thrwad and see what he says. But we still have to figure out the build.prop
Sent from my XT860 using xda premium
Endoroid said:
Well a sbf would fix it, but that would undo the radio hack, as it would flash a new radio. You could motofastboot just /system and /preinstall, which would leave the radio intact, but i don't know how tech capable she is, to use fastboot. Not that it's really difficult, but you do need to kinda know your way around a computer a bit. That would remove safestrap and would make it out of the box new, albeit still with the modded radio. Also would need the build.prop edits still.
I could actually mod ovelayers 1-click to flash all but the radio probably. I'm fairly sure that would fix all problems without Causing anymore maybe ill pm him the link to this thrwad and see what he says. But we still have to figure out the build.prop
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Im not sure, since she didnt know that your not supposed to factory reset with a rooted phone i dont want to stress her out...
I was worried i would have to deal with something like those -_-
alright, since im down to basically no more ideas , i gave her the instructions to toggle to safe system...
If it works, can i just give her the modified build.prop and guide her to replace it?
If not, i see a refund and a faulty phone coming to me
Juicy555 said:
alright, since im down to basically no more ideas , i gave her the instructions to toggle to safe system...
If it works, can i just give her the modified build.prop and guide her to replace it?
If not, i see a refund and a faulty phone coming to me
Click to expand...
Click to collapse
It should. If the non safe is bone stock, then it should work. If my 1-click idea is valid, it's Damn easy. Literally 1 click
I've asked ovelayer to check this out.
Sent from my XT860 using xda premium
Endoroid said:
It should. If the non safe is bone stock, then it should work. If my 1-click idea is valid, it's Damn easy. Literally 1 click
I've asked ovelayer to check this out.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Thanks. She hasnt replied back in 25 minutes or so not sure whats going on ATM.
Il post back in the morning, thanks for your replies and help.
edit: ok, NOW SHES IN A SOFT BRICK! It just keeps saying droid.. so something went wrong i guess, or the non safe is corrupted...
Juicy555 said:
Thanks. She hasnt replied back in 25 minutes or so not sure whats going on ATM.
Il post back in the morning, thanks for your replies and help.
edit: ok, NOW SHES IN A SOFT BRICK! It just keeps saying droid.. so something went wrong i guess, or the non safe is corrupted...
Click to expand...
Click to collapse
Boot into safestrap and while on non safe factory reset
Sent from my XT860 using xda premium
TESTED AND WORKING!
My phone previously was running TWRP with a custom ROM and kernel on MDL baseband. I wanted to switch ROM's anyway and didn't care about retaining information, so I was looking for the simplest thing to do without reverting to stock. Do the steps below and you can go from an MDL rom to an MF9 rom as well as MF9 kernel and modem in a matter of minutes.
1) Upload TriForceROM to your SD card. You can technically use any MF9 compatible ROM, but this is the one I used.
2) Boot in to TWRP and do a full wipe, then install TriForceROM. When the install is done reboot the phone into the ROM. Note: First time it loads it may take a minute, don't panic. And yes, an MF9 rom will boot to MDL firmware.
3) When Android comes up do NOT do anything in the OS. Some features will NOT work. Simply shut the phone down immediately. You must turn the phone all the way off! Then turn phone back on and boot into Download Mode by holding VOL UP + POWER. Press VOL UP to get it ready to receive data. Plug your phone into the computer (if not already) and open Odin 3.07. Note: You can NOT reboot from the OS into download mode, you must shutdown completely and then go in to download mode. Don't ask me why.
4) Proceed to flash the MF9 modem and other firmware updates as instructed in noobnl's post. You must follow the step to flash the bootloader as well.. it takes like 2 seconds to fix, don't forget it!
5) When Odin flash is done, reboot phone and let it load into TriForceROM and voila... everything is MF9 now.
When TriForce opens for the first time Android will say "finalizing update" and may reboot one more time (it did for me)... once you come back to the ROM you can look under About Phone and it will say MF9. If it says MDL still then the Odin flash did not work properly.
Easiest firmware upgrade ever.
Damn, I'm currently updating to MF9 AFTER flashing to stock. If I had only read this post! Thanks!
BTW: It's power + home + volume down, not volume up.
This is a good guide if you do want to update the modem and etc to the latest but for anyone who is lazy, you still can just flash an MF9 rom, like TriForce over MDL or even MDC (which I'm still on) and everything works fine.
My nandroid is to a freshly rooted MDC stock rom and I just flash any MDL/MF9 rom over that and I'm fine. Though it is customary to update the modem and etc to the current version of whatever your on - you don't need to. I never once updated my GS3 from what it came with and just flashed whatever rom that was based on the latest.
Sent from my SPH-L720 using xda app-developers app
inlineboy said:
This is a good guide if you do want to update the modem and etc to the latest but for anyone who is lazy, you still can just flash an MF9 rom, like TriForce over MDL or even MDC (which I'm still on) and everything works fine.
My nandroid is to a freshly rooted MDC stock rom and I just flash any MDL/MF9 rom over that and I'm fine. Though it is customary to update the modem and etc to the current version of whatever your on - you don't need to. I never once updated my GS3 from what it came with and just flashed whatever rom that was based on the latest.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Well you're right and wrong. Sure it works, but think about it like this... if you put diesel in your regular gasoline engine, it might turn over and run for a bit, but eventually you'll blow the engine.
MF9 roms may try to access MF9 firmware features. So without the latest firmware installed with the mod, the ROM may crash if you attempt to do anything firmware specific.
I recommend everyone be on the latest firmware. If you were on MF9 firmware and and wanted to run MDL ROM's then that would be ok, but I don't recommend doing it how you're doing it.
Will this get me apps to sd?
Sent from my SPH-L720 using xda app-developers app
Fuzzy Wuzzy said:
Damn, I'm currently updating to MF9 AFTER flashing to stock. If I had only read this post! Thanks!
BTW: It's power + home + volume down, not volume up.
Click to expand...
Click to collapse
And actually you don't have to use home button just vol down and power
Sent from my SPH-L720 using xda premium
Any one getting random reboots with this update? And.... how do I solve this problem?
Sent from my SPH-L720 using xda app-developers app
kinextions said:
Any one getting random reboots with this update? And.... how do I solve this problem?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
It appears to be kernel related. Either adjust the KT kernel (not sure the particulars) or use another kernel like Agats 3.3.
Sent from my SPH-L720 using xda premium
kinextions said:
Any one getting random reboots with this update? And.... how do I solve this problem?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I had one random reboot one time. And it seemed to be related to using Viper4Android.
Other than that it was working fine for me.
Worked perfectly as u said but I wanted to ask if I flash an mdl rom do u know if I lose the mf9 features like apps to sd? And i also want to say thanks for your excellent work
Sent from my SPH-L720 using xda app-developers app
jonnoh said:
It appears to be kernel related. Either adjust the KT kernel (not sure the particulars) or use another kernel like Agats 3.3.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Sorry but where do I find agats kernel.
Sent from my SPH-L720 using xda app-developers app
Can anyone tell me why when I go to Settings > More > and under System Manager the icon next to "about device" is yellow...
When I click on it everything is grayed out except Status, Legal information and Device Name... Baseband and Software version both say MF9 but could anyone tell me why the icon is Yellow?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cytality said:
TESTED AND WORKING!
1) Upload TriForceROM to your SD card. You can technically use any MF9 compatible ROM, but this is the one I used.
Click to expand...
Click to collapse
Please forgive the very stupid question, but does this mean that any Rom listed as MF9 can be used following the exact steps you laid out, with the only difference being which zip I download?
beerindex said:
Please forgive the very stupid question, but does this mean that any Rom listed as MF9 can be used following the exact steps you laid out, with the only difference being which zip I download?
Click to expand...
Click to collapse
As I understand it yes. You can use any rom. The .tar with the modem/firmware updates is generic and brings the phone to Sprint's MF9 level firmware but should work with ANY MF9 Rom.
Cytality said:
TESTED AND WORKING!
My phone previously was running TWRP with a custom ROM and kernel on MDL baseband. I wanted to switch ROM's anyway and didn't care about retaining information, so I was looking for the simplest thing to do without reverting to stock. Do the steps below and you can go from an MDL rom to an MF9 rom as well as MF9 kernel and modem in a matter of minutes.
1) Upload TriForceROM to your SD card. You can technically use any MF9 compatible ROM, but this is the one I used.
2) Boot in to TWRP and do a full wipe, then install TriForceROM. When the install is done reboot the phone into the ROM. Note: First time it loads it may take a minute, don't panic. And yes, an MF9 rom will boot to MDL firmware.
3) When Android comes up do NOT do anything in the OS. Some features will NOT work. Simply shut the phone down immediately. You must turn the phone all the way off! Then turn phone back on and boot into Download Mode by holding VOL UP + POWER. Press VOL UP to get it ready to receive data. Plug your phone into the computer (if not already) and open Odin 3.07. Note: You can NOT reboot from the OS into download mode, you must shutdown completely and then go in to download mode. Don't ask me why.
4) Proceed to flash the MF9 modem and other firmware updates as instructed in noobnl's post. You must follow the step to flash the bootloader as well.. it takes like 2 seconds to fix, don't forget it!
5) When Odin flash is done, reboot phone and let it load into TriForceROM and voila... everything is MF9 now.
When TriForce opens for the first time Android will say "finalizing update" and may reboot one more time (it did for me)... once you come back to the ROM you can look under About Phone and it will say MF9. If it says MDL still then the Odin flash did not work properly.
Easiest firmware upgrade ever.
Click to expand...
Click to collapse
Will it be possible to downgrade back to MDC after upgrading to MF9 with this method?
TheGoodFellas said:
Will it be possible to downgrade back to MDC after upgrading to MF9 with this method?
Click to expand...
Click to collapse
Yes you can you just need to odin back to mdc stock.
Sent from my SPH-L720
Fuzzy Wuzzy said:
Damn, I'm currently updating to MF9 AFTER flashing to stock. If I had only read this post! Thanks!
BTW: It's power + home + volume down, not volume up.
Click to expand...
Click to collapse
BTW its power + volume down. You don't need the home button.
Sent from my SPH-L720 using xda premium
My build number is now an MF9, but my Baseband version is MDL. Does that mean it did not work?
Fixed it myself. Can't seem to delete the post.
I've been on TriForce 3.1 for the last few days, can I still go ahead and reflash the MF9 firmware? I really would rather not have to reflash the ROM and change all my damn settings and apps again.
Thanks
Burtonrider said:
I've been on TriForce 3.1 for the last few days, can I still go ahead and reflash the MF9 firmware? I really would rather not have to reflash the ROM and change all my damn settings and apps again.
Thanks
Click to expand...
Click to collapse
Bump? Having a lot of crashes and reboots that I'd like to work on fixing. I have yet to find an answer if it's OK to try a different kernel w/o going to MF9 first.
Wish I stayed with 4.2.2
This was allegedly a STABLE version as those are the only ones Im pdating to per my CM update settings.
I do not use nightlies.
Unfortunately I lost connection to GOOGLE PLAY STORE on both of my Nook hd+ tablets...same night I ran the update to 4.3 from 4.2
Im getting the constant *No connection..Retry* error.
Watched many *fix-it* videos on YouTube.....none of the tricks worked.
cleared, data, cache, force stopped, rebooted, unistalled, reinstalled......nothing.
unistalled again 4.4.21 and even istalled the latest 4.4.22 Gogle play store......still the same error.
very frustrated since this was allegedly a STABLE version.
Now I cannot access the Play Store with both of our tablets.
Any advice will be greatly appreciated !
Did you remember to upgrade your gapps when you moved to cm 10.2? It requires 20130813.
Sent from my BN NookHD+ using xda premium
leapinlar said:
Did you remember to upgrade your gapps when you moved to cm 10.2? It requires 20130813.
Sent from my BN NookHD+ using xda premium
Click to expand...
Click to collapse
That did the trick.....
I remember the need for new gaps when 4.3 came out a while ago.
I thought it needed to be done only then by those that wanted to upgrade early.
I (wrongly) presumed that the new gapps would be included with new 'stable' versions CM ROMs.
(Especially since no warning or instructions for new gapps popped up during 4.3 installation).
Now I know that gapps is something that always needs to be installed separately.
Thank you for your reply leapinlar !!
Where can I download 20130813? When I go to goo.im I get "The file you requested was not found"
Mugby said:
Where can I download 20130813? When I go to goo.im I get "The file you requested was not found"
Click to expand...
Click to collapse
That is not the whole name. It is gapps-jb-20130813-signed.zip.
Sent from my BN NookHD+ using xda premium
leapinlar said:
That is not the whole name. It is gapps-jb-20130813-signed.zip.
Sent from my BN NookHD+ using xda premium
Click to expand...
Click to collapse
Yes, and none of the links work
File appears to be down for now. Try searching the web for alternate locations using the full name.
Sent from my BN NookHD+ using xda premium
leapinlar said:
File appears to be down for now. Try searching the web for alternate locations using the full name.
Sent from my BN NookHD+ using xda premium
Click to expand...
Click to collapse
I got mine from here:
http :// www . androidfilehost. com/? fid=23060877490000124
(please put the link together. I a mnot able to post since I have only a few posts)
Installing new gapps solved the problem. Thank you again, leapinlar !
PS:
I am either getting too old or blind or cognitively challenged, but this forum has
the most difficult (I am trying to be nice here IMAGE VERIFICATION system I have ever encountered.
WatchFan1 said:
I got mine from here:
http :// www . androidfilehost. com/? fid=23060877490000124
(please put the link together. I a mnot able to post since I have only a few posts)
Installing new gapps solved the problem. Thank you again, leapinlar !
PS:
I am either getting too old or blind or cognitively challenged, but this forum has
the most difficult (I am trying to be nice here IMAGE VERIFICATION system I have ever encountered.
Click to expand...
Click to collapse
There is no need to look for newer version of Gapps. Just follow the guide below
techkhoji.com/android/no-connection-retry-google-play-store
nexusguy7 said:
There is no need to look for newer version of Gapps. Just follow the guide below
techkhoji.com/android/no-connection-retry-google-play-store
Click to expand...
Click to collapse
The guide you linked attempts to look for solutions to the issue, which may not solve the issue.
The best/only way is to update gapps if you upgrade your Android version.
You can download all gapps from here: http://goo.im/gapps (they are current changing servers which host the files, so you may run into problems if you try right now; later on should be perfect).
All the best.
leapinlar said:
Did you remember to upgrade your gapps when you moved to cm 10.2? It requires 20130813.
Sent from my BN NookHD+ using xda premium
Click to expand...
Click to collapse
I have the same issue and I did update the gapps after I updated to the cm10.2. But I still can't access the store. I have internet, but nothing Google. I've flashed gapps twice after realizing I had no play access. Any ideas?
eddytholland said:
I have the same issue and I did update the gapps after I updated to the cm10.2. But I still can't access the store. I have internet, but nothing Google. I've flashed gapps twice after realizing I had no play access. Any ideas?
Click to expand...
Click to collapse
Have you tried clearing the cache for the store? Do you use any custom resolutions or DPI settings?
jpisini said:
Have you tried clearing the cache for the store? Do you use any custom resolutions or DPI settings?
Click to expand...
Click to collapse
all i did was do an upgrade. then loaded the appropriate gapps.zip. idk how to delete the cache from the store itself. also whenever i try to use anything google related, it basically cause the gapps process to force close.
Go to settings apps all you will find all the Google apps listed there. If that doesn't work do a factory reset and try again,
Sent from my Nook HD+ using xda app-developers app
I had all the same issues, but when i rent to a rest i still didn't have any Google services. I tried a new cw11 nightly and now i can't get past the nook boot screen. Hiw do i get back to a functional nook hd+?
silinthar said:
I had all the same issues, but when i rent to a rest i still didn't have any Google services. I tried a new cw11 nightly and now i can't get past the nook boot screen. Hiw do i get back to a functional nook hd+?
Click to expand...
Click to collapse
To get back to a functional HD/HD+, go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD. Use that to flash a plain stock zip from item 6 followed by a factory reset with CWM. That should take you back to stock and you should be able to start over.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
To get back to a functional HD/HD+, go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD. Use that to flash a plain stock zip from item 6 followed by a factory reset with CWM. That should take you back to stock and you should be able to start over. =QUOTE]
If I Create a CWM SD will it boot up? I'm not even getting past the nook screen of the bootscreen. I can't get to a recovery menu to even load a mod.
Click to expand...
Click to collapse
silinthar said:
leapinlar said:
To get back to a functional HD/HD+, go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD. Use that to flash a plain stock zip from item 6 followed by a factory reset with CWM. That should take you back to stock and you should be able to start over. =QUOTE]
If I Create a CWM SD will it boot up? I'm not even getting past the nook screen of the bootscreen. I can't get to a recovery menu to even load a mod.
Click to expand...
Click to collapse
It should, but others have reported problems getting a CWM SD to boot after installing CM11 and CWM 6045+ to internal memory.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
leapinlar said:
silinthar said:
It should, but others have reported problems getting a CWM SD to boot after installing CM11 and CWM 6045+ to internal memory.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I'll give it a try.
Click to expand...
Click to collapse
silinthar said:
leapinlar said:
I'll give it a try.
Click to expand...
Click to collapse
Nope, didn't work. My NookHD+ doesn't gets passed the Nook boot screen. Is there something I'm missing that can at least get me passed the Nook boot screen or is it just toast?
Click to expand...
Click to collapse