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
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..."
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
Ok so i dont know if this is a dumb question or maybe it is. but hey Im no expert. Can someone please advise if i was to update the new update or the gingerbread, will i lose my root and unlock cus im using this phone on rogers network & we all know this is a bell phone. Please help.
you will not lose the unlock but root will be gone. You can root it after you install gingerbread the same easy way you rooted before...
Root wouldn't be a problem as you could re-root again (very easy). If you install a custom gingerbread rom it is probably pre-rooted.
As for the unlock your phone should stay unlocked, I don't think the update mess with your /efs partition.
One problem could be the loss of the 850 MHz band. I don't know if it's better to flash the KC1 modem.
zorxd said:
Root wouldn't be a problem as you could re-root again (very easy). If you install a custom gingerbread rom it is probably pre-rooted.
As for the unlock your phone should stay unlocked, I don't think the update mess with your /efs partition.
One problem could be the loss of the 850 MHz band. I don't know if it's better to flash the KC1 modem.
Click to expand...
Click to collapse
See now this freaks me out, cus my biggest pet peave is to root this phone, Im scared to brick it. I use to have a desire andit was so easy just to root and have clockwork onit and install roms but since I bought this phone I havent done ay rom works cus im too scared to brick it. Anyways I guess ill just stay on 2.2, cusi don't wana get into the 850 issue, im on rogers and I dont wann lose the 3g.
junooni.1980 said:
See now this freaks me out, cus my biggest pet peave is to root this phone, Im scared to brick it. I use to have a desire andit was so easy just to root and have clockwork onit and install roms but since I bought this phone I havent done ay rom works cus im too scared to brick it. Anyways I guess ill just stay on 2.2, cusi don't wana get into the 850 issue, im on rogers and I dont wann lose the 3g.
Click to expand...
Click to collapse
You are aware it's easier to brick a desire than a Galaxy S right?
Note!
Furry Atom said:
You are aware it's easier to brick a desire than a Galaxy S right?
Click to expand...
Click to collapse
I have has my Galaxy S sence Dec and flashed the hell out of it without any problems. Thought I bricked it a few times but perhapes I'm lucky?
ramrod54 said:
I have has my Galaxy S sence Dec and flashed the hell out of it without any problems. Thought I bricked it a few times but perhapes I'm lucky?
Click to expand...
Click to collapse
Soft brick =/= actual brick. A bricked phone would be past the point of using odin to restore.
The SGS is probably the easiest phone to root. Just install a custom pre-rooted kernel trough odin/heimdall. No risk as you can flash back your old kernel the same way.
You are more likely to brick your phone flashing the phone with GB than rooting it once you have GB. That being said, the risk is very low. Follow directions and you'll be fine. I'm on an i9000m and unlocked it and have been running JVK for about a week with the KC1 modem and LOVE it.
Sent from my GT-I9000 using XDA App
Ok guys the Galaxy S is one of the most hardest phone to brick out there. Sure a lot of people experience soft brick where you enter a boot loop but download mode still there and you can flash with odin back to stock.
As to 850 Mhz you can enable it on any model firmware with a little trick found here
And as you can see it works I have 850Mhz working on JVK modem wich is the modem from the leaked GB before it was official. I founded it to be more battery friendly than JL2 and as fast if not faster.
p.s. That make me think I need to update my signature
{
"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"
}
Updated to gingerbread today and used docs kitchen and then went back and flashed the kg1 modem and csc files
Works just great so far!
Sent from my GT-I9000 using XDA App
lgsshedden said:
Updated to gingerbread today and used docs kitchen and then went back and flashed the kg1 modem and csc files
Works just great so far!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Are you talking about KC1 modem, if yes than make a little test and let your phone with anything than phone at off (wi-fi/3G off and nothing open). Check how many percent of you battery you lose per hours during the night and then do the same after upgrading to JVK modem.
Fo me it was half the consumption with JVK compared to KC1 so I decidec to stay on JVK modem.
yes I did mean KC1 modem: initially installed the JVK but couldn't get the 850 activated -- can you remind me how please. Know it is a simple fix but didn't have the instructions with me when I did the install so flashed KC1 to ensure I had service.
Will let you know how the battery drains today on KC1 before I play around and swap so we can save others the experimentation: appreciate your help, thanks.
I think the process would be similar to this: http://forum.xda-developers.com/showpost.php?p=12172219&postcount=35147
lgsshedden said:
yes I did mean KC1 modem: initially installed the JVK but couldn't get the 850 activated -- can you remind me how please. Know it is a simple fix but didn't have the instructions with me when I did the install so flashed KC1 to ensure I had service.
Will let you know how the battery drains today on KC1 before I play around and swap so we can save others the experimentation: appreciate your help, thanks.
Click to expand...
Click to collapse
lgsshedden said:
yes I did mean KC1 modem: initially installed the JVK but couldn't get the 850 activated -- can you remind me how please. Know it is a simple fix but didn't have the instructions with me when I did the install so flashed KC1 to ensure I had service.
Will let you know how the battery drains today on KC1 before I play around and swap so we can save others the experimentation: appreciate your help, thanks.
Click to expand...
Click to collapse
Here is the real procedure http://forum.xda-developers.com/showpost.php?p=12156313&postcount=438
I've also made a new thread explaning this method in our i9000 general forum as this one comes from the aptivate forum. Hope it will get quote in the big guide list.
FYI : It's in my signature
thanks: and yes it is, sorry for not paying closer attention!
Hey, just flashed JVB with JL2 modem. If I go into the *#2263# and if under combi bands 850 has a * beside it...does that mean I have the 850 band still?
sp991 said:
Are you talking about KC1 modem, if yes than make a little test and let your phone with anything than phone at off (wi-fi/3G off and nothing open). Check how many percent of you battery you lose per hours during the night and then do the same after upgrading to JVK modem.
Fo me it was half the consumption with JVK compared to KC1 so I decidec to stay on JVK modem.
Click to expand...
Click to collapse
Just curious if you've compared the two modems in a low reception area? Unfortunately I spend most of the day in a concrete building and found that my reception wasn't as good with JVK compared to KC1 (this was with JVK rom, i've since gone back to 2.2.1 with KC1 modem) Would love to have better battery life though!
I tried Simply Honey 3.1 and found unacceptable battery life. It was the first time I tried the KC1 modem so that may have been to blame.
I flashed Doc's beta JVB ROM, and it seems much better so far.
I wish I had stayed on the froyo ROMs that worked better, but I can't help to be on the bleeding edge.
I'm hoping Darky puts together a JVB ROM soon.
Sent from my GT-I9000 using XDA App
SWave711 said:
Hey, just flashed JVB with JL2 modem. If I go into the *#2263# and if under combi bands 850 has a * beside it...does that mean I have the 850 band still?
Click to expand...
Click to collapse
The JL2 modem always had the 850 band enabled by default.
has anyone been able to root their phones after the new update just pushed by verizon..When they pushed it, it bricked my phone so I used the "guide" to put it back to ed05... then allowed it to update, and then used the "Guide" to root again it it bricked it again.... so going back to ed05, let it update again, but now want to root again but the question is how????
Thanks guys and gals...
[email protected] said:
has anyone been able to root their phones after the new update just pushed by verizon..When they pushed it, it bricked my phone so I used the "guide" to put it back to ed05... then allowed it to update, and then used the "Guide" to root again it it bricked it again.... so going back to ed05, let it update again, but now want to root again but the question is how????
Thanks guys and gals...
Click to expand...
Click to collapse
odin eh03 gb then root it. no need for ed05 or ota update...follow section 4 then section 5 of my guide.
is there anything good about the update??? what was new with it??? minus messing up rooting??
Stock eh03 gingerbread is alot faster than stock ed05 Froyo imo...cant comment on anything else because I have not ran stock eh03 longer than 20min, that was just to see If I could flash cm7 from it.
ok thank you
I used odin to root my phone after verizons update.
Just Odin the stock EH03 package and then flash SuperClean v3.05 in cwm and you'll have all the rooted, deodexed, debinged and debloated Gingerbread glory that you can stand! It has caused me to fall in love with my Fascinate all over again!
Can someone please tell me where to download the ROM's other than Multiupload.
Download time there for me says it is over 3 hours.
Looks like I got the OTA during the night and my Fascinate is stuck in recovery now.
Since I am hosed anyway I want to finally make the jump and start flashing some ROM's.
If I can ever get a download link that works
Thanks,
Fury22 said:
Can someone please tell me where to download the ROM's other than Multiupload.
Download time there for me says it is over 3 hours.
Looks like I got the OTA during the night and my Fascinate is stuck in recovery now.
Since I am hosed anyway I want to finally make the jump and start flashing some ROM's.
If I can ever get a download link that works
Thanks,
Click to expand...
Click to collapse
Look in the development section. Here is a link to Superclean to get you started.
Also multi upload is just a list of links where to download.
http://www.multiupload.com/P40GUMW9FN
Sent from my SCH-I500
wish this worked for me
johnsma22 said:
Just Odin the stock EH03 package and then flash SuperClean v3.05 in cwm and you'll have all the rooted, deodexed, debinged and debloated Gingerbread glory that you can stand! It has caused me to fall in love with my Fascinate all over again!
Click to expand...
Click to collapse
I did the EH03 flash in ODIN and the phone works again but now it wont connect to usb to use odin again to root. I have tried numerous factory cables and pcs but nothing works. surely someone else has had this problem? is there another way to root it?
johnsma22 said:
Just Odin the stock EH03 package and then flash SuperClean v3.05 in cwm and you'll have all the rooted, deodexed, debinged and debloated Gingerbread glory that you can stand! It has caused me to fall in love with my Fascinate all over again!
Click to expand...
Click to collapse
Did the same completely different phone now.
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...