Related
I currently running I5 update from Kies and would like revert back to the stock rom. I found this posting http://forum.xda-developers.com/showthread.php?t=740077 and would like to use it to flash back to stock. My question, anyone know of any problems with using STock_Vibrant.zip referenced in the above posting.
Keep in mind, I'm newbie to Android.
The ROM you should use is JI6 (the latest official stock release).
I would recommend downloading Mini-Kies and see if you can upgrade to JI6 from JI5. If that doesn't work (someone has probably posted whether you can do this or not), then use ODIN to flash to the original stock JFD rom, then use Mini-Kies to upgrade to JI6.
You can find a link to download mini-kies from the Samsung support page for Vibrant.
Tried and all I get is unregistered device. Kies mini wants the original stock rom, which is why I'm reverting back.
Sent from my SGH-T959 using XDA App
http://forum.xda-developers.com/showthread.php?t=810130
http://forum.xda-developers.com/showthread.php?t=790026
http://forum.xda-developers.com/showthread.php?t=739091
These should help. Use Odin 1.3
Pig Vomit said:
http://forum.xda-developers.com/showthread.php?t=810130
http://forum.xda-developers.com/showthread.php?t=790026
http://forum.xda-developers.com/showthread.php?t=739091
These should help. Use Odin 1.3
Click to expand...
Click to collapse
PV,
Dude this was painless and the video just made the entire process easy.
Thank you!!!!
I just got the droid x about 5 days ago and immdiatley rooted it and installed the darkslide rom on it. a couple of days later i tried to use the slacker radio app and it error out (error: 1, -17) so i tried pandora and it just says it couldn't play the the station on every station, and later i tried to play a youtube video and none of them work.
I've tried to factory reset and different roms but none of that works. I'm on 3g and have tried it several places. Does anybody have any idea what is going on.
*On a side note I can't get my Youmail app to work either
Are you able to play mp3's or videos? The other day I made a huge mistake by
installing a patch from Rubix that was intended to patch .320 or .340 and I was
still on .15. When I did it, nothing media related would play. I basically had to SBF.
Something in the media player(s) was corrupted as I checked my build log.
Maybe unroot it. That's why I don't root my phones. I never had an issue with my phones. I see to many problems with rooting. I rely on my phone way to much. Besides I think android does enough without rooting.
Sent from my DROIDX using XDA App
spacecasespiff said:
Maybe unroot it. That's why I don't root my phones. I never had an issue with my phones. I see to many problems with rooting. I rely on my phone way to much. Besides I think android does enough without rooting.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
The op's issue is related to the custom rom installation... most likely using roms built with a different base. It has nothing to do with rooting, per se.
As my fiance says to me, after helping my uncle and cousin set up their non-rooted Xs, "I can see why you have done this to your phone, I didn't like their's at all!" She has an incredible, and she now wants me to root it for her... I'm going to be jealous because I'll be loading some cyanogen mod that I've been missing since my nexus one was passed off... ahh, the days of bad ass roms and a crappy network...
Anyway, the op most likely needs to sbf (ensuring the correct version is used). Then making sure to update to the latest .340 system version (check for updates in settings if not already there, please verify bootloader, kernel, and baseband match those in the .340 update), followed by rooting, making a clean back up, and then flashing gummyjar. I'm kidding about gummyjar, but I'm staying here for awhile after trying apex (next favorite), tranq, fission and even plain stock motoblur.
Google, and forum search will go into greater detail.
Good luck, and keep rooting.
Edit: btw, if you find out you never did the .340 update (verify the above please) you should be able to return to your original backup (you made one right away after rooting right?). If not, no worries, just sbf (again, verify the version!!!! Do you think that's important?)
Sent from my DROIDX using XDA App
rossiscatch said:
Anyway, the op most likely needs to sbf (ensuring the correct version is used). Then making sure to update to the latest .340 system version (check for updates in settings if not already there, please verify bootloader, kernel, and baseband match those in the .340 update), followed by rooting, making a clean back up, and then flashing gummyjar. I'm kidding about gummyjar, but I'm staying here for awhile after trying apex (next favorite), tranq, fission and even plain stock motoblur.
Google, and forum search will go into greater detail.
Good luck, and keep rooting.
Edit: btw, if you find out you never did the .340 update (verify the above please) you should be able to return to your original backup (you made one right away after rooting right?). If not, no worries, just sbf (again, verify the version!!!! Do you think that's important?)
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Thanks that looks like some great info but you must forgive me. I just came from the droid 1 and I had Koush rom manager so I am super spoiled and really don't know how to do any of that stuff you speak of. I don't even know what the .340 update is. (apparently i'm a noob), but if I factory rested to the original would that not fix that issue?
If you could provide some steps on your instructions or some links to instructions that would be great.
Alright, start by telling me your system, baseband, and kernel versions. These can be found in, settings --> about phone.
Next enter stock recovery by turning your phone off, then turn it back on while pressing and holding the power, camera and down volume buttons at the same time (release after 5 seconds or so). Once there, tell me your boot loader version... likely 30.03 or 30.04.
We'll work from there.
Sent from my DROIDX using XDA App
flowtime said:
but if I factory rested to the original would that not fix that issue?
Click to expand...
Click to collapse
That depends on how you did a factory reset. If you simply did it through settings --> privacy, then no, that will not fix your issue.
Did you make a backup of your phone through rom manager or bootstrap recovery before you started flashing roms?
Also, I am almost positive you have installed rom(s) intended for the latest ota without actually having the ota installed on your phone. If that's the case you'll need to either sbf or return to a stock rom (backup?) and then update to the latest ota, but we'll get to that after you answer my questions in the above post.
Sent from my DROIDX using XDA App
I am on DarkSlide v4.1, and do not have any of the issues mentioned. You will need to be on the latest .340 OTA update as DS is based on that. I cannot link to the SBF files required (due to a C&D notice), but there are guides in the DS thread over at MDW that explain the process.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.
rossiscatch said:
That depends on how you did a factory reset. If you simply did it through settings --> privacy, then no, that will not fix your issue.
Also, I am almost positive you have installed rom(s) intended for the latest ota without actually having the ota installed on your phone. If that's the case you'll need to either sbf or return to a stock rom (backup?) and then update to the latest ota, but we'll get to that after you answer my questions in the above post.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I'm sure of that too. Exactly what happened to me. Installed a ROM intended for the latest ota and had to end up doing the sbf on rsb lite.
rossiscatch said:
Alright, start by telling me your system, baseband, and kernel versions. These can be found in, settings --> about phone.
Next enter stock recovery by turning your phone off, then turn it back on while pressing and holding the power, camera and down volume buttons at the same time (release after 5 seconds or so). Once there, tell me your boot loader version... likely 30.03 or 30.04.
We'll work from there.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I use the koush droid x bootstraper app v2.5.0.6. (Just fyi)
The bootloader 30.04
I just did a factory reset from the droid x bootstraper and this is this is the information there
{
"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: You guys are right. My wife got her droid x same time as I did but I didn't root hers and I just checked system updates and she had one there. So I know I didn't update mine before installing the roms. Thanks for the help guys. Now if you could provide the steps to how to fix it I would be must appreciative. Ya'll are AWESOME
I Fixed it!
Hey everybody thanks for the help. I fixed the issue you. You all were spot on. I use rsd lite and reinstalled from the sbf. found this great guide.
http://www.droidforums.net/forum/hacking-help/106839-restore.html
Once i got it up i did the update rerooted then re-romed and everything runs smoothly
flowtime said:
Hey everybody thanks for the help. I fixed the issue you. You all were spot on. I use rsd lite and reinstalled from the sbf. found this great guide.
http://www.droidforums.net/forum/hacking-help/106839-restore.html
Once i got it up i did the update rerooted then re-romed and everything runs smoothly
Click to expand...
Click to collapse
Glad you were able to get it fixed. I remember when it happened to me I was
crapppin bricks. But all in all, it's a good learning experience and was kind of fun.
Glad you got it working!
Sent from my DROIDX using XDA App
Okay so yesterday i flashed the LEAKED Froyo DL30 into my phone. but i didnt know i didnt update the Baseband version. So i flashed the DL30 on DH12. And i flashed froyo, everything worked fine except DOWNLOADING & 3G & Texting... is there any way to fix this?? like go back to Eclair or over flash anything to fix this problem?? please help thank you
Sangwoo said:
Okay so yesterday i flashed the LEAKED Froyo DL30 into my phone. but i didnt know i didnt update the Baseband version. So i flashed the DL30 on DH12. And i flashed froyo, everything worked fine except DOWNLOADING & 3G & Texting... is there any way to fix this?? like go back to Eclair or over flash anything to fix this problem?? please help thank you
Click to expand...
Click to collapse
Why would you flash the ORIGINAL build's baseband on the latest build ???? Doesn't common sense tell you it won't work ????
To fix your issue, you need to flash either the DJ05 or the DL09 radio, which can be located under the android development section of this forum.
I think he meant that he's never flashed any radio newer than DH12, not that he downgraded the baseband. If you just flash the DL09 radio, you should be fine.
Posted from my DL09 SuperClean Fascinate with Voodoo
Yeah if you want the latest flash dl09 not dl05
if you wanna know what the difference between the two then google it lol but yeah
adrynalyne said:
Radio:
http://adrynalyne.us/files/roms/DL09modem.tar
This gets flashed via Odin, in the PDA section.
Click to expand...
Click to collapse
This should be all that you need. If it still doesn't work, try flashing the full DL09 package, then installing your DL30 rom/kernel.
FYI for those having Text\SMS issues like sending texts and them showing up blank on the receiving end and not receiving texts, I installed DL09 (was on DI Radio) and it fixed them right up! My wife is happy she can use her Fascinate again she was stuck on her old droid all day and wasn't happy
Thanks for the help guys!!
Flash the DL09 radio using odin and you'll be in business. GPS is darn near spot on too!
Sent from my Froyo Fascinate using Tapatalk Pro.
ivorycruncher said:
I think he meant that he's never flashed any radio newer than DH12, not that he downgraded the baseband. If you just flash the DL09 radio, you should be fine.
Posted from my DL09 SuperClean Fascinate with Voodoo
Click to expand...
Click to collapse
Woops that came out wrong. I meant flash the latest build ON TOP of the original baseband.
Hey,
I'm coming from a rooted Thunderbolt and I understand a bit about flashing different roms, but this seems different.
My little brother decided that he wanted to update his Froyo X to the leaked gingerbread before it was rooted. Well, he did. But now he's getting random reboots and wants to either move back to Froyo or just move to something stable. What exactly needs to be done to do this?
Like I said, I have a rooted thunderbolt so I was exposed to using adb to get root. Would the process be similar in this case? Also, is there a way to flash back to Froyo without doing a full data wipe? He said he didn't do a wipe when he installed gingerbread.
Do a search on how to SBF for the Droid X. You can "sbf" back to stock froyo and reroot with z4root app. From there, he can upgrade to stable rooted GB or stay at froyo. If you'd like to know how to upgrade to a rooted version of GB, visit mydroidworld.com and there's lots of info there on how to do so and all the files you need.
http://www.youtube.com/watch?v=N0jrXqqiepI&feature=youtube_gdata_player
Good sbf video tutorial
Sent from my DROIDX using XDA App
What is this?This is a warning that multiple users, including myself, have hard bricked their devices by SBF flashing to 1.8.3 after installing an official 4.5.91 update.How can I avoid this brick?You can avoid bricking your device by not flashing any over-the-air updates to Android 2.3.4. Instead, try flashing the 2.3.4 zip over here. Or, flash the pure stock images from here.What if I already flashed the official 4.5.91?If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though.What happens when you hard brick?The error shows:
SVF:105.1:2
Failed to boot 0X1000
{
"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"
}
samcripp said:
the .91 update is the same as leak. Same binary 100% identical, not only do i confirm it, its confirm by every other dev. Dont listen to miss inform people. Once you update you will never be able to downgrade using sbf. You can sbf 4.5.91 because it has the same identical bl bp pass. Anything else will end up in a hard brick.
The only time this is an exception is for those who never unlocked. This folks after installing ota experience a semi hard brick when flashing pudding. This semi hard brick is similar in that it shows you 0x1000. But other than that it is just a semi hard brick.
What can you do to not hard brick your phone. Well easy, either you can use one of the widely available roms, any of the stock images, or a fruit cake. They are all base off .91
YOU COULD ALSO STOP USING SBF ALL TOGETHER. ITS NOT SAFE. RSD/SBF IS FOR INTERNAL CARRIER/MOTO USE. IT WAS NEVER MEANT FOR ANYONE TO EVER DOWNGRADE. PUT DOWN THE FLASE AND PRAISE THE SAFE METHODS.
safe methods:
fastboot
CWM
sbf with pudding already in it!
Click to expand...
Click to collapse
kennethpenn said:
If you flash the official over-the-air update to get to 4.5.91 Gingerbread, you risk a hard brick.
The brick occurs when you flash the 1.8.3 SBF file in RSD mode over an officially updated 4.5.91 Gingerbread.
The stock ROM flashable I released is completely safe to use and should not brick your device if you choose to go back to 1.8.3.
Click to expand...
Click to collapse
I really think theres something wrong with 1.83 it's junk I'm using 1.26 only and manually updating from there from now on.
Gutterball said:
I really think theres something wrong with 1.83 it's junk I'm using 1.26 only and manually updating from there from now on.
Click to expand...
Click to collapse
so is it safe to go from the ota to 1.26?
Could this be related to changes made to the bootloader in support of the discovered unlockability?
geishroy said:
so is it safe to go from the ota to 1.26?
Click to expand...
Click to collapse
We're not sure at the moment.
kennethpenn said:
We're not sure at the moment.
Click to expand...
Click to collapse
how about using a cwm backup from gingerblur instead? would that be safer. i know it's hard to say i just want your opinion if it comes to that. thanks.
This should be stickied.
Sent from my MB860 using XDA App
Replacement Atrix
I have a replacement Atrix that was sent to me a couple of days ago. I havne't sent the old one back (vibration issues) I can update to the latest update and then try and flash back the 1.26 to see if that works.
I can try this out later tonight when I get home to make sure.
NoNameAtAll said:
This should be stickied.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Just took care of that ;-)
I just flashed the OTA update from the other thread by renaming the file to update.zip.
It wouldn't surprise me if Moto did something to prevent you from flashing back to a earlier version sort of like what Apple does with the iPhone. Hopefully somebody will figure this out though. What about a NVFlash?
so i had issues with 2.3.4 and flashed back to 1.8.3 before i read this and its bootlooping after the ATT splash. what can i do to fix this...im scared to flash anything else at the moment. somebody please help.
Has the official OTA started getting sent out yet? im still running gingerblur 4.5 with a locked bootloader and im not wanting to do anything until the offical one comes out. My plain is to flash 1.2.6 sbf and start all over and do all the OTA updates all the way to gingerbread then unlock the boot loader after that. Is that way the safest way
lilgmaine04 said:
so i had issues with 2.3.4 and flashed back to 1.8.3 before i read this and its bootlooping after the ATT splash. what can i do to fix this...im scared to flash anything else at the moment. somebody please help.
Click to expand...
Click to collapse
I would try and flash 1.2.6 original ROM. Which version did you update with. Through CWM or through the regular android recovery?
dang and i was about to flash the oem to, hey all did you try to flash back with something other the 1.83? I'd say it wont make a difference, probably brick no mater which file you flash.
Terrific...at least the good news is I'm safely on the new update. I'm scared now.
Hold me
mudd_cat23 said:
Has the official OTA started getting sent out yet? im still running gingerblur 4.5 with a locked bootloader and im not wanting to do anything until the offical one comes out. My plain is to flash 1.2.6 sbf and start all over and do all the OTA updates all the way to gingerbread then unlock the boot loader after that. Is that way the safest way
Click to expand...
Click to collapse
No an official official OTA has not been sent.
lilgmaine04 said:
so i had issues with 2.3.4 and flashed back to 1.8.3 before i read this and its bootlooping after the ATT splash. what can i do to fix this...im scared to flash anything else at the moment. somebody please help.
Click to expand...
Click to collapse
Did you wipe data? Going between Android versions, in this case Android 2.3.4 back to 2.2.2, you should always wipe.
THANKS KENNETH! I updated my guide for surfing the MotoBlur servers with a warning and a link back to this sticky!
So far all I've installed is the sbf for the new radio. Any thoughts on that?
i was using the HKTW build first and flashed the other one on top with the CM recovery...everything went smoothly except for the inverted touchscreen, so I decided to flash back to 1.8.3 with RSD and now its looping. Soooo I have my phone here now awaiting orders from somebody alot better than me lol
i've been playing around with the 4.5.91 updates for the past few hours
things i've noticed:
1. I was able to easily and without any problems install kennethpenn's .zip for 4.5.91 over my "stock" (slightly modded, themed, but not a ROM) 1.8.3 using the new "untethered" CWM
2. Decided to try the "Stock 4.5.91", so I tried to flash 1.8.3 with RSD Lite 5.3.1 over-top of kennethpenn's 4.5.91, it FAILED EVERY TIME, both on my VirtualBox running Windows XP, as well as on my friend's extremely powerful laptop running Windows 7.
Getting worried, I reinstalled RSD Lite 5.3.1, the Atrix drivers from motorola's website, and downloaded and extracted a fresh 1.2.6 sbf.
I was able to flash 1.2.6 over kennethpenn's 4.5.91 and update back to 1.8.3 with no problems at all.
not sure if this helps you guys at all, but if it does, or if anyone has any questions and is interested in what i've been playing around with all day (keep your minds out of the gutter !)
just let me know somehow between a pm or a post here
AllTheWay said:
I have a replacement Atrix that was sent to me a couple of days ago. I havne't sent the old one back (vibration issues) I can update to the latest update and then try and flash back the 1.26 to see if that works.
I can try this out later tonight when I get home to make sure.
Click to expand...
Click to collapse
This will be awesome if it works. Hope you are able to do so and report back soon!
Sent from my MB860 using XDA App