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
Related
I've held off on rooting the N1 because was is just more convenient to OTA update to 2.2. Now that it is done, are there any anticipated or speculated forthcoming updates to the N1 in the next few months?
If not, I'm rooting. Need space for apps!
Thanks.
I am not sure about anything cool coming in the next few months, but I say just root it.
I got my phone in March and I just rooted last week finally. I wish I would have done it sooner. Even if you just want to use it to help with space limitations... the possibilities are endless.
I just wanted to root to have full control of my phone. Now I have turned into a ADB and ROM junky. Just read as much as you can on it before you do it. The community here is great, so you will have lots of help.
Google said they should be releasing the next version (Gingerbread) before the end of the year. If you want to root go ahead and do it, you can always go back to stock if you don't like it and it will help you to move more apps to the SD card.
Gingerbread is rumored to be released some time before the end of the year.
gingerbread is supposed to be out sometime between september-november and the N1 will be getting that for sure, other than that I can't say.
noiz7 said:
Google said they should be releasing the next version (Gingerbread) before the end of the year. If you want to root go ahead and do it, you can always go back to stock if you don't like it and it will help you to move more apps to the SD card.
Click to expand...
Click to collapse
blunden said:
Gingerbread is rumored to be released some time before the end of the year.
Click to expand...
Click to collapse
seeking said:
gingerbread is supposed to be out sometime between september-november and the N1 will be getting that for sure, other than that I can't say.
Click to expand...
Click to collapse
I hear Gingerbread is rumored to come out before the end of 2010.
[Delete Me ]
Lol i think we forgot to mention Gingerbread...
wdfowty said:
Lol i think we forgot to mention Gingerbread...
Click to expand...
Click to collapse
Doh! How could we... So yeah, Gingerbread is supposed to be coming out before the end of the year .
I'm sure you probably know this already but you can use the "Exploid" method on the final Froyo release (thread is somewhere on xda) and get your root without unlocking the bootloader or wiping.
I remember when FRF91 came out, a pre-rooted stock version was already available on XDA before it even rolled out to the general public. I think it is pretty safe to say, when Gingerbread comes out there will again be pre-rooted versions here on the forums.
And since I'm sure the "exploid" method will be patched by the next official release, you may well want to hold onto your root by sidestepping the OTA.
Tostino said:
Doh! How could we... So yeah, Gingerbread is supposed to be coming out before the end of the year .
Click to expand...
Click to collapse
ohh thanks for the info i didn't know gingerbread was coming lol jk
So you say around christmas ??
Hope I can sync it then with my laptop.
{
"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"
}
noiz7 said:
Google said they should be releasing the next version (Gingerbread) before the end of the year. If you want to root go ahead and do it, you can always go back to stock if you don't like it and it will help you to move more apps to the SD card.
Click to expand...
Click to collapse
cmstlist said:
I'm sure you probably know this already but you can use the "Exploid" method on the final Froyo release (thread is somewhere on xda) and get your root without unlocking the bootloader or wiping.
I remember when FRF91 came out, a pre-rooted stock version was already available on XDA before it even rolled out to the general public. I think it is pretty safe to say, when Gingerbread comes out there will again be pre-rooted versions here on the forums.
And since I'm sure the "exploid" method will be patched by the next official release, you may well want to hold onto your root by sidestepping the OTA.
Click to expand...
Click to collapse
Thanks for all the replies. Very helpful. I have not followed XDA/Android modding for some time so this is all new to me.
Some follow ups:
1) Unlocking the bootloader: This simply allows one to install different ROMs, correct? Can this be "undone", like it is possible w/ WM platforms?
2) Rooting: This allows one flexibility and control over the OS. If I don't intend to install a customized ROM, I presume I don't need to unlock the bootloader?
Again, can this be undone?
3) In the WM world, a new ROM (or hard reset) means wiping everything. But, with the right backup/restore software, everything can be put back fairly easily. With Android, does a new ROM also mean everything wiped? If so, how did the Froyo 2.2 do it without wiping?
I have yet to find a backup/restore that will completely restore the phone to the exact previous state...
Thanks again folks.
Cheers.
1. Yes. Currently there is no way to relock the bootloader
2. Yes. And rooting can be undone. Generally just by going back to a stock rom or restoring backup from before root
3. Unfortunately, changing rom (stock to cyanogen or cyanogen to enomther) usually requires wipe. But updating does not
Rellikzephyr
Sent from my Nexus One using XDA App
cmstlist said:
I'm sure you probably know this already but you can use the "Exploid" method on the final Froyo release (thread is somewhere on xda) and get your root without unlocking the bootloader or wiping.
I remember when FRF91 came out, a pre-rooted stock version was already available on XDA before it even rolled out to the general public. I think it is pretty safe to say, when Gingerbread comes out there will again be pre-rooted versions here on the forums.
And since I'm sure the "exploid" method will be patched by the next official release, you may well want to hold onto your root by sidestepping the OTA.
Click to expand...
Click to collapse
Thank you. Your post seems to suggest, if I understand it correctly, rooting _usually_ requires unlocking the bootloader. Why is this?
With the "exploid" method, is it still a "proper" root? Does the exploid methid leave my phone more vulnerable to malicious apps? If/when I decide to unlock the bootloader later, will I need to re-root?
Thanks again.
snovvman said:
Thank you. Your post seems to suggest, if I understand it correctly, rooting _usually_ requires unlocking the bootloader. Why is this?
With the "exploid" method, is it still a "proper" root? Does the exploid methid leave my phone more vulnerable to malicious apps? If/when I decide to unlock the bootloader later, will I need to re-root?
Thanks again.
Click to expand...
Click to collapse
Since the NexusOne is a developer/enthusiast phone, HTC/Google were kind enough to leave us geeks an easy way to get under the hood. You're able to unlock the bootloader with just a simple adb command. They even provided a pretty graphical screen on the phone to say "hey, hack away - just know that we won't be responsible if you break ****". Once the bootloader was unlocked, it was stupid easy to flash a custom recovery image, and then flash the necessary files to root the phone. This is the "official" way to root the NexusOne.
With some of the recent exploits, though, it has become possible to gain root-level access without unlocking the bootloader. These methods take advantage of known security weaknesses of the Android system. Once the root access is gained, a user has the sufficient permissions to flash a custom recovery image and install custom ROMs. The end result is exactly the same, it's just not following the pretty little path that Google/HTC laid out for us. Once your phone is rooted this way, you shouldn't ever need to unlock the bootloader. Your warranty can stay whole.
Neither method will have any direct effect on your phone's security - but both method will give you the escalated superuser privileges that could allow you to screw something up. With great power comes great responsibility and all that - know what you're doing before you break something
Android 3.0 (Gingerbread) Rumors Emerge
Expected dates are mid- October (around 15 -16th), 2010. First handsets shipping around in November/December.
snovvman said:
Thank you. Your post seems to suggest, if I understand it correctly, rooting _usually_ requires unlocking the bootloader. Why is this?
With the "exploid" method, is it still a "proper" root? Does the exploid methid leave my phone more vulnerable to malicious apps? If/when I decide to unlock the bootloader later, will I need to re-root?
Thanks again.
Click to expand...
Click to collapse
The question was pretty well answered by codesplice.
Basically if you have an unlocked bootloader you can reflash various images in bootloader mode (e.g. change the ROM, change the recovery). If you root through a vulnerability, you can carry out all the same modifications but just not through the bootloader.
If for whatever reason you wanted to unlock the bootloader later, and you've already rooted via a hack... you could take a nandroid and/or Titanium backup, then unlock (which will wipe your device), then restore the backup.
organizedfellow said:
android 3.0 (gingerbread) rumors emerge
expected dates are mid- october (around 15 -16th), 2010. First handsets shipping around in november/december.
Click to expand...
Click to collapse
those rumors are 100% false stop posting/referring to those!
codesplice said:
Since the NexusOne is a developer/enthusiast phone, HTC/Google were kind enough to leave us geeks an easy way to get under the hood. You're able to unlock the bootloader with just a simple adb command. They even provided a pretty graphical screen on the phone to say "hey, hack away - just know that we won't be responsible if you break ****". Once the bootloader was unlocked, it was stupid easy to flash a custom recovery image, and then flash the necessary files to root the phone. This is the "official" way to root the NexusOne.
With some of the recent exploits, though, it has become possible to gain root-level access without unlocking the bootloader. These methods take advantage of known security weaknesses of the Android system. Once the root access is gained, a user has the sufficient permissions to flash a custom recovery image and install custom ROMs. The end result is exactly the same, it's just not following the pretty little path that Google/HTC laid out for us. Once your phone is rooted this way, you shouldn't ever need to unlock the bootloader. Your warranty can stay whole.
Neither method will have any direct effect on your phone's security - but both method will give you the escalated superuser privileges that could allow you to screw something up. With great power comes great responsibility and all that - know what you're doing before you break something
Click to expand...
Click to collapse
Thank you for the explaination. I asked about the potential increased security risk from reading a comment in the Android Market.
One of the comments under "Easy Root Compatibility", a user named "timothy" wrote: "This app utilizes a hotplug security vulnerability that gives ALL apps root access..."
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
Anyone with luck flashing a Milestone X w/ a custom ROM?
Running Rooted 2.3.5 w/bloatware removed (but backed up) along w/ DROID X Bootstrapper.
Have made my first full system backup using this tool.
If complete ROMS could not be used, what components would I need to modify, replace, ... exchange to get it to work on C-Spire (say, Verizon).
I've heard that there are some ROMS that don't mess with the baseband and other communications settings, files, frequencies, protocol, etc... What are these type called if they exist? Where can I find them? Are these a safer alternative to full ROMS?
Will DX Bootstrapper get the job done? Reports ClockworkMod REcovery v2.5.0.6.
I would recommend staying off custom roms for the Milestone X until a working sbf for us makes an appearance. Myself and ngholson both had issues where we got stuck in a bootloop and the sbf just output more errors until a replacement device was needed.
Rocheforte said:
I would recommend staying off custom roms for the Milestone X until a working sbf for us makes an appearance. Myself and ngholson both had issues where we got stuck in a bootloop and the sbf just output more errors until a replacement device was needed.
Click to expand...
Click to collapse
agreed. [10chars...............
another thing to consider, since we cannot sbf at this time, is that the bootstrapper will break your ability to install any future ota updates. it modifies the logwrapper and makes a copy called logwrapper.bin, however, uninstalling the bootstrapper and restoring the logwrapper file does not correct the problem. best i can tell the only answer that i can find when this happens is to sbf back to stock... well you see where this is going.... currently we cannot do this, so unless you never want the ota upgrades i do not recommend installing the bootstrapper on cspire's milestone x.
oh well nevermind went back and re-read your post, you already have the bootstrapper installed. (at least you did it after ota)
here is a link to the post that has the sbf that is reported to work with cell south (cspire) http://forum.xda-developers.com/showthread.php?t=1117885
maybe someone else can try it again and report back.
daywalker04 said:
SBF flash for MB809 - Milestone X Generic North America
SHADO_X6_3.1.39_SHADOW_BP_C_02.06.00R_AP_BP_Flex_1E_signed_secure_dist_1ff_P3_USERBLD.sbf.gz
http://www.filesonic.com/file/11766...x_1E_signed_secure_dist_1ff_P3_USERBLD.sbf.gz
Compression MD5 - BF942D55992C774446F24B56116649A1
SBF MD5 - 2EAEBD1540D563114523BEB09539A8AF
Click to expand...
Click to collapse
abcleanonme said:
Well I can confirm it works on Cellular South.
Sent from my MilestoneX using XDA Premium App
Click to expand...
Click to collapse
I can confirm that the old sbf it does not work after ota update. I had to get a new phone. I have rooted, but I am not installing a bootstrapper until a working sbf is available. Hopefully that will happen soon.
I am on C spire out of Byram, MS and can in fact confirm that "Droid X Bootstrapper" from the market indeed works like a charm on the Milestone X with stock versions 2.2.2 and 2.3.5.
I use "Super One Click" to root, then the same prog to "Allow non market apps" then buy "Droid X Bootstrapper" from market, run it. Reboot while holding camera button and power button,,,,voila
Confirmed roms that I have and currently run or ran: CM 7 nightlies, Liberty 1.5, and Fission 2.5.7 DroidX
---------- Post added at 07:12 AM ---------- Previous post was at 06:57 AM ----------
A little trick I figured out to sbf back to stock,,,,download the latest ota from Cspire "Blur_Version.3.2.6.MB809.ACG-CellSouth.en.US" blah blah,,,,,rename it to "update.zip",,,,not "update.zip.zip"put it on the root of your sd card and boot into stock recovery or clockwork mod and run update.......BLAM! Simple as that...
Brickster said:
A little trick I figured out to sbf back to stock,,,,download the latest ota from Cspire "Blur_Version.3.2.6.MB809.ACG-CellSouth.en.US" blah blah,,,,,rename it to "update.zip",,,,not "update.zip.zip"put it on the root of your sd card and boot into stock recovery or clockwork mod and run update.......BLAM! Simple as that...
Click to expand...
Click to collapse
i tried that too it didn't work for me.
I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App
Brickster said:
I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
is there a reason that your not using the new liberty rom and used 1.5?
tylorjefcoat said:
is there a reason that your not using the new liberty rom and used 1.5?
Click to expand...
Click to collapse
Nah, it's a cool rom .....I'm just a flash whore. I like cm7 nightlies the best though.
Brickster said:
Nah, it's a cool rom .....I'm just a flash whore. I like cm7 nightlies the best though.
Click to expand...
Click to collapse
what has been the best in your opinion? i just upgraded from the hero and was running aosp and loved it.
i actually like some of the blur apps, hard to believe that i like a custom ui on android lol.
i have been reading on the droid x vs milestone x and i am weary of flashing update that also includes the radio/baseband.
what version of cm7 nightfiles are you on? any complaints?
Brickster said:
I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
I am getting the exact same error. Where do I need to go to eliminate this line of code. I have setup everything else up until this point and it works perfectly with recovery and everything. A bit of help please.
thenig said:
I am getting the exact same error. Where do I need to go to eliminate this line of code. I have setup everything else up until this point and it works perfectly with recovery and everything. A bit of help please.
Click to expand...
Click to collapse
Open the ROM zip and go: META-INF/com/google/android/ and in the updater-script, remove the code that asked for Kernel assert.
tylorjefcoat said:
what has been the best in your opinion? i just upgraded from the hero and was running aosp and loved it.
i actually like some of the blur apps, hard to believe that i like a custom ui on android lol.
i have been reading on the droid x vs milestone x and i am weary of flashing update that also includes the radio/baseband.
what version of cm7 nightfiles are you on? any complaints?
Click to expand...
Click to collapse
I too just upgraded from the Hero....and I still love that phone! My hero has had every rom known on it,,,and some that weren't even made for it....It's unbrickable! LOL
Yea, the Milestone is a little more finicky than the Hero, and with Motorola's locked bootloaders, one could get in a fix..
I've ran the past 3 nightlies and currently on cm_shadow_full-154.zip.
I tell ya, they all have some kind of bug somewhere. It all depends on what you want to put up with. Me, personally, I like the stock ota 2.3.5 from Cspire. It works. Plain and simple. Now, I would like some of the CM7 options and spare parts.
Brickster said:
Open the ROM zip and go: META-INF/com/google/android/ and in the updater-script, remove the code that asked for Kernel assert.
Click to expand...
Click to collapse
Open the updater-script with notepad (new to this) and found no mention of kernel assert. Almost there...a bit more help would get me in.
It should be the top 3 lines, if I remember correctly.... I checked it out on my phone to make sure but,,,, duh, I already removed it (face palm).
It's in there somewhere.
Run install again and right down all the errors... Then try to find them in the script file.
I'm new to this also (as far as motorola stuff) too. And I take risks that most people wouldn't..... Hell, if I mess something up bad enough , just sbf back.
I'll try to help you more when I get off work... Maybe send you my roms that have already been fixed.
Make sure to turn off script and signature asserts off in cwm... Sometimes that helps.
Sent from my Milestone X using XDA App
Brickster said:
It should be the top 3 lines, if I remember correctly.... I checked it out on my phone to make sure but,,,, duh, I already removed it (face palm).
It's in there somewhere.
Run install again and right down all the errors... Then try to find them in the script file.
I'm new to this also (as far as motorola stuff) too. And I take risks that most people wouldn't..... Hell, if I mess something up bad enough , just sbf back.
I'll try to help you more when I get off work... Maybe send you my roms that have already been fixed.
Make sure to turn off script and signature asserts off in cwm... Sometimes that helps.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
Thank you sir! I'm gonna try that.
Brickster said:
I too just upgraded from the Hero....and I still love that phone! My hero has had every rom known on it,,,and some that weren't even made for it....It's unbrickable! LOL
Yea, the Milestone is a little more finicky than the Hero, and with Motorola's locked bootloaders, one could get in a fix..
I've ran the past 3 nightlies and currently on cm_shadow_full-154.zip.
I tell ya, they all have some kind of bug somewhere. It all depends on what you want to put up with. Me, personally, I like the stock ota 2.3.5 from Cspire. It works. Plain and simple. Now, I would like some of the CM7 options and spare parts.
Click to expand...
Click to collapse
I despised that phone lol, wait i take that back, i guess i had "phone" envy lol Mine was a rom whore as well, it was rooted almost immediately after i got it with the ole gold card method.
the ota 2.3.5 is actually a good CLEAN rom, i do like the fact that it is so clean, just need a few tweaks as you said from the cm7 build, status bar tweaks ect..
may build up one.
built a rom for a tablet we are selling here, BIG learning curve but the locked boot-loader throws a real curve ball
now, have you gotten it to overclock?
Brickster said:
. Hell, if I mess something up bad enough , just sbf back.
Click to expand...
Click to collapse
that still amazes me. i haven't tried it on 2.3.5, but when i did it from stock 2.2.2 it was a no go.... maybe it will only work if you are already on 2.3? hell i dunno... motorola has me chasing my tail.... like everyone else, i came from the hero too, that was one awesome little phone. i read somewhere that the motorola bootloader had been cracked by someone on here but..... not sure what ever happened there.....
Hey folks n00bie here.
I have a general couple of questions regarding 'rooting' and what the risks are. I have a HTC Desire HD A9191 on the vodafone (UK) network (contract), there is no vodafone software branding on the phone nor no logo on the phone itself, I have the up-to-date version of Androd 2.3.5 and sense 3 and yes its already unlocked as I can insert different sim cards and they will work.
I've always considered the benefits of going down the root road but I'm a bit skeptical as I do not want to brick my phone on the first run and want to does the Advanced Hack Kit do it all for you, the procedure to root and is it optional to flash a custom rom later on ? Also with this process erase my contact lists (in phone memory) and SMS messages (in phone memory) and will it erase my music, photos and pictures on my SDCard? If so would it be applicable to back up the SDcard and the internal phone memory then root ?
Regards,
Craig.
muffintastic said:
Hey folks n00bie here.
I have a general couple of questions regarding 'rooting' and what the risks are. I have a HTC Desire HD A9191 on the vodafone (UK) network (contract), there is no vodafone software branding on the phone nor no logo on the phone itself, I have the up-to-date version of Androd 2.3.5 and sense 3 and yes its already unlocked as I can insert different sim cards and they will work.
I've always considered the benefits of going down the root road but I'm a bit skeptical as I do not want to brick my phone on the first run and want to does the Advanced Hack Kit do it all for you, the procedure to root and is it optional to flash a custom rom later on ? Also with this process erase my contact lists (in phone memory) and SMS messages (in phone memory) and will it erase my music, photos and pictures on my SDCard? If so would it be applicable to back up the SDcard and the internal phone memory then root ?
Regards,
Craig.
Click to expand...
Click to collapse
Backing up your phone before any procedure is advised. Look for Myphoneexplorer in the market, will back up all your contacts and sms.
It will not erase your SD card
As bob6600 said above me the hack kit won't erase your sd card, but it is advised that you backup your sd card anyway just in case. There is only a very small percent chance you may brick your phone using AAHK.
Sent from my inter galactic super fantastic communication device.
GuyInTheCorner said:
As bob6600 said above me the hack kit won't erase your sd card, but it is advised that you backup your sd card anyway just in case. There is only a very small percent chance you may brick your phone using AAHK.
Sent from my inter galactic super fantastic communication device.
Click to expand...
Click to collapse
I gather then well yes obviously it's necessary to backup on any update regardless. What is this small percent chance then ? I assumed if the process would be interrupted by a power failure of such half way through / pulling the cable out ? So basically the kit isn't full proof then and there is that small chance it'll brick my phone if I don't follow the guides ? and how long does the process take if you don't do the installation of the custom rom ?
muffintastic said:
I gather then well yes obviously it's necessary to backup on any update regardless. What is this small percent chance then ? I assumed if the process would be interrupted by a power failure of such half way through / pulling the cable out ? So basically the kit isn't full proof then and there is that small chance it'll brick my phone if I don't follow the guides ? and how long does the process take if you don't do the installation of the custom rom ?
Click to expand...
Click to collapse
That's the small percentage normally rooting takes about twenty minutes cause it has to downgrade the is so it can exploit it
Sent from my inter galactic super fantastic communication device.
GuyInTheCorner said:
That's the small percentage normally rooting takes about twenty minutes cause it has to downgrade the is so it can exploit it
Sent from my inter galactic super fantastic communication device.
Click to expand...
Click to collapse
Ok then that's re assured me also once its downgraded can I put the Android version back to 2.35 and then flash it with a custom rom I.e Ice cream sandwich and mod my camera for full 30 fps video and use the 0% compression setting for photos etc ? Basically use my full phone to its potential ?
You don't need to put it back to 2.3.5, just flash a custom rom and off you go.
Sent from my Desire HD using xda premium
Muikkuman said:
You don't need to put it back to 2.3.5, just flash a custom rom and off you go.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I'll give it a shot this week and report back. :silly:
Just an FYI, since the AAHK launched I've yet to see a handset permanently bricked through the AAHK failing.
Ensure you read and re-read the manual, this cannot be stressed enough, and carry out all the required steps relating to your computer.
If you do have any issues, just jump onto the AAHK IRC channel, you'll get help there usually quicker than on XDA.
andyharney said:
Just an FYI, since the AAHK launched I've yet to see a handset permanently bricked through the AAHK failing.
Ensure you read and re-read the manual, this cannot be stressed enough, and carry out all the required steps relating to your computer.
If you do have any issues, just jump onto the AAHK IRC channel, you'll get help there usually quicker than on XDA.
Click to expand...
Click to collapse
Basically to cut the long story short. I'm going to be using Ubuntu 12.04 for the 'root' process as I don't see Windows as being stable as its very prone to being sluggish and unreliable, The current software on my Desire HD (A9191) is all up-to-date, sense 3, 2.3.5 ETC. I've followed the instructions on the effen-manual, installed the latest build of AAHK on Ubuntu, hooked up my phone in debug mode and charge only mode, entered the key from cajun.txt and pressed option 1 and asked me to 'downgrade' is this a normal process and after this will I need to re-run the cmd file and from the xda video on the Desire HD it'll just be like that and when I see fit I can put a custom rom on when I see fit or re-run the software updater via the phone etc ? Would I undo what I am trying to achieve if I put it back to 2.3.5 and just put on rooted programmes etc ?
Too scared to do it lol - I've also attached some pictures regarding the current state of my non-rooted phone.
{
"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"
}
Using AAHK will downgrade and wipe your phone. You can update it back to your current s/w version and use it as you do today, knowing it is hacked and ready for a new rom. Or if you have a rom in mind, you could put it onto the sd card and install it from there using CWM recovery. AAHK manual can be a bit confusing but hey I did it and even with mistakes didn't brick my phone. Don't be scared, have some faith! Good luck.
Sent from my HTC Desire HD using xda app-developers app
Yes no problem. I just downgraded my phone and rooted it yesterday. Exactly the same configuration as you. Except mine was unlocked. First time for me, its really stressful but I'm sure everything will be fine.
Sent from my Desire HD using xda app-developers app
Quentharry said:
Yes no problem. I just downgraded my phone and rooted it yesterday. Exactly the same configuration as you. Except mine was unlocked. First time for me, its really stressful but I'm sure everything will be fine.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
Right I've successfully downgraded and rooted my phone, Now what ? lol. Can I just do a normal software update and put 2.3.5 back on or will i lose what i've done ?
muffintastic said:
Right I've successfully downgraded and rooted my phone, Now what ? lol. Can I just do a normal software update and put 2.3.5 back on or will i lose what i've done ?
Click to expand...
Click to collapse
You'll lose it. I recommend going for Cyanogenmod 7 as your first ROM. Great piece of software for new good
Sent from my inter galactic super fantastic communication device.
muffintastic said:
Hey folks n00bie here.
I have a general couple of questions regarding 'rooting' and what the risks are. I have a HTC Desire HD A9191 on the vodafone (UK) network (contract), there is no vodafone software branding on the phone nor no logo on the phone itself, I have the up-to-date version of Androd 2.3.5 and sense 3 and yes its already unlocked as I can insert different sim cards and they will work.
I've always considered the benefits of going down the root road but I'm a bit skeptical as I do not want to brick my phone on the first run and want to does the Advanced Hack Kit do it all for you, the procedure to root and is it optional to flash a custom rom later on ? Also with this process erase my contact lists (in phone memory) and SMS messages (in phone memory) and will it erase my music, photos and pictures on my SDCard? If so would it be applicable to back up the SDcard and the internal phone memory then root ?
Regards,
Craig.
Click to expand...
Click to collapse
One thing that i can tell you, i have 2 DHDs and have rooted them without any problem. AAHC is a superb tool. Go for it:laugh:
KeshavJave said:
One thing that i can tell you, i have 2 DHDs and have rooted them without any problem. AAHC is a superb tool. Go for it:laugh:
Click to expand...
Click to collapse
I also say go and do it. Backup your contacts, sms and your music etc and then go. Read the post for AAHC and do it...
Okay.. so i've got a Mytouch 4G Tmobile (yes screen is cracked i kno) that WAS running Cyanogen perfectly.. until one day something happened.. i believe i flashed a new rom OR i flashed a new kernel or radio... and now no matter WHAT ROM i flash it just BOOTLOOPS forever.. i dont know what to do. $20 to the person who provides the advice to get it working again. Here is photos of my recovery crap.
WHAT DO I DO LOL! Thank you SO much in advance guys, XDA Forums had taught me SO much! I need this phone to work again for my daughter.
$20 to the person who provides the advice that gets my phone to boot up! MY WORD!
{
"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 SPH-L720 using XDA Free mobile app
I have also tried flashing the stock signed PD15IMG.ZIP file and in TWRP it just sais error. (I think it was a good copy of pd15img.zip i downloaded at least...)
Sent from my SPH-L720 using XDA Free mobile app
Okay so i found the official stock rom for the tmobile glacier htc mytouch 4g and renamed it "PD15IMG" making sure not to add ".zip" to the end of it, and it just sais "cannot open zip file" heres a photo of the error in TWRP
What am i doing wrong??!! Ive followed every single tutorial i can find down to the letter... the only thing i havent done is setup ADB or anything.. is that what i need to do? I can flash roms succesfully, roms ive used before succesfully even... but it just bootloops on EVERY SINGLE ONE OF THEM... somethings wrong.. im BEYOND frustrated.. i am not new to flashing phones.. but this is just rediculous...
Sent from my SPH-L720
Update: so i found a post on 4shared of 6 different stock roms (PD15IMG.zip) files, the 2.2 and the 2.3 old and new, tried flashing all 6 but recieve the same exact error... my phone somehow became S-ON after flashing another rom when i got bored of CM7.. so i know i messed it up that way.. and all the tutorials ive read to S-OFF a glacier require you to be able to boot the phone up! SO... how can i even begin to achieve S-OFF status without a functioning rom? Or am i completely boned?
Sent from my SPH-L720
Darkarmy88 said:
Update: so i found a post on 4shared of 6 different stock roms (PD15IMG.zip) files, the 2.2 and the 2.3 old and new, tried flashing all 6 but recieve the same exact error... my phone somehow became S-ON after flashing another rom when i got bored of CM7.. so i know i messed it up that way.. and all the tutorials ive read to S-OFF a glacier require you to be able to boot the phone up! SO... how can i even begin to achieve S-OFF status without a functioning rom? Or am i completely boned?
Sent from my SPH-L720
Click to expand...
Click to collapse
A bit late but, s-on may have happened due to flashing the stock files. Do you still have your twrp?
A common mistake is not wiping all the data before flashing a rom. Make sure you wipe your data in recovery before flashing a rom.
Hope I helped
Sent from my SM-N900W8 using Tapatalk
---------- Post added at 11:12 PM ---------- Previous post was at 11:10 PM ----------
I think you may have to flash a boot.img separately.
Sent from my SM-N900W8 using Tapatalk
I believe I have flashed a boot.IMG or whatever too. So I've tried doing a COMPLETE wipe of eeeverything before flashing any ROM.. Still bootlooping. With any glacier ROM I try. So how do I achieve s-off again with no access to any ROM?
And yes I still have TWRP 2.2.2.1 functioning on the phone. But it is S-on status...
Any advice on what steps I should take to fix these issues? Even if it means a COMPLETELY stock, unrooted, regular mytouch 4g again I DONT care lol. Data is not important either. If losing it all means a functioning phone... So be it. But it won't even let me flash ANY of the stock ROMs. I've tried all 6.
Any advice is GREATLY appreciated. And my $20 offer still stands... I know it isn't much, but my daughter wants her phone SO bad... She asks me every day "daddy did you fix it?!" And having to tell her no is heartbreaking... XDA brothers.. Please help
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
Also... What boot.img should I flash? And should I flash it via TWRP or through recovery?
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
Darkarmy88 said:
Also... What boot.img should I flash? And should I flash it via TWRP or through recovery?
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
Click to expand...
Click to collapse
Try flashing a rom ( I recommend cm7), then flash the kernel from that rom in bootloader.
The kernel should be called boot.img when you open up the zip file.
Sent from my SM-N900W8 using Tapatalk
---------- Post added at 03:42 PM ---------- Previous post was at 03:40 PM ----------
S-off is done through a terminal emulator right?
Sent from my SM-N900W8 using Tapatalk
Where can I obtain the proper kernal? I have CM7 ready to go. And I can't use terminal emulator as no ROM will boot to use it lol
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
Darkarmy88 said:
Where can I obtain the proper kernal? I have CM7 ready to go. And I can't use terminal emulator as no ROM will boot to use it lol
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
Click to expand...
Click to collapse
In the cm7 zip file which you will flash. So open up that zip file and right there, there's gonna be file called boot.img
Also there is a terminal emulator you can use in recovery =) I'll find the link for you
Sent from my SM-N900W8 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1646108
That's the recovery file manager, when you get into recovery just flash it and you can access all your files. It you press options, then a tiny box will pop up at the bottom of the screen that says terminal. Click that and then try to s-off
Sent from my SM-N900W8 using Tapatalk
Thank you all so much for the help!! I will be trying all of this ASAP!!! SO... I just need to wipe everything, flash the boot.img (first?) Then go and flash CM7? Actually I think I need to S-off before I flash any ROM huh? Thanks for the link brother, hopefully I can s-off via the terminal emulator!! Ugh I'm so nervous.... Lol!
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
Okay. Re read it all... So,
1) wipe
2) flash cm7
3) flash cm7's boot.img via bootloader
4) see if cm7 boots.. If not...
5) install terminal emu above (thx!)
6) attempt s-off w/o killing myself
7) if s-off successful... Flash ROM and go
8) if all fails, sell phone to hobo and buy new one lol
Let me know if you guys think I should try things in a different order OR try different things period... I'm ALL EARS
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
Darkarmy88 said:
Okay. Re read it all... So,
1) wipe
2) flash cm7
3) flash cm7's boot.img via bootloader
4) see if cm7 boots.. If not...
5) install terminal emu above (thx!)
6) attempt s-off w/o killing myself
7) if s-off successful... Flash ROM and go
8) if all fails, sell phone to hobo and buy new one lol
Let me know if you guys think I should try things in a different order OR try different things period... I'm ALL EARS
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
Click to expand...
Click to collapse
Sounds good lol. Tell us how it goes
Sent from my SM-N900W8 using Tapatalk
I will! Haven't got a chance yet actually
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
If it doesn't work, then just Download a PD15IMG.zip (or try PD15DIAG.zip), leave it on the root of your SD storage, and boot into the bootloader (not recovery) it should find the zip and install it. After you have gone back to the factory ROM, try doing s-off from there.
the reason why the PD15IMG.zip wont flash in TWRP is because they aren't recovery zip format, they are made to be flashed in the way I explained above..
Yes I understand, as I stated above 4 or 5 comments down, I tried to flash all 6 different copies of pd15img.zip via BOOTLOADER with no success, it flashes " un " lol but as it finishes flashing it just returns to the menu with an error, with ALL six versions of the stock glacier ROM... So it doesn't work via bootloader or TWRP. BUT I have not tried the 2nd file you mentioned, any chance you could let me know where to find that other zip file? I've seen pd15img.zip all over the place, but not that one. This is overly frustrating lol, someone even said it may be a physical problem and I should "twist" my phone during the flash.... Troll perhaps?
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
Troll? Hahaha hahaha good luck bro.
Also, reread your own thread, nowhere do you mention flashing via bootloader, only via twrp. But since you obviously know more than me about it, I'll leave you be..
Wow... U must be an idiot because I was calling the GUY WHO SAID TO TWIST THE PHONE WHILE FLASHING A TROLL... Not you. Really? You really didn't catch that? Amazing lol
Sent from Galaxy S4 using XDA Forums App. Wish it was sent from my HTC Glacier though... $20 if you can help me fix my bootloop!!! PM me!
Yep, idiot perfectly describes me.. Good luck.