Droid 3 update help please - Motorola Droid 3

just read this thread: http://forum.xda-developers.com/showthread.php?t=1334704 and was really wanting the update. It is critical that I don't ruin my new phone for financial reasons, but I am obsessed with upgrading the damn thing. Can someone walk me through the process of getting the update without bricking it? I really need someone who knows what they are doing, no offense to others that would try to help but might not be as capable.
My Droid 3 (about 2 days old), is one-click rooted with the DARK DROID ROM. Also just downloaded and installed the camera fix (sorry, I looked for the link but couldn't find it). Here are a few screen shots for information. Would you or anyone else that really knows what they are doing help me out with this?
Here are some screen shots, hopefully they can provide info I forgot to mention.
{
"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"
}

You need to go back to a pure /system to flash the update. And I do not know if our current root methods work for it or not (I haven't read that thread yet).
BTW, you had the fixed camera when you flashed DarkDroid

If you are talking about the leaked OTA update, then you need to get back to the original Motoblur ROM, with all of the bloatware still on it. Then download the update and put it in the root of your internal storage. At that point, (don't quote me on this, im trying it tomorrow) you will power off your phone, and hold x and power at the same time, and the recovery mode will boot up (use the volume keys to make the menu pop up). At that point, scroll down to the install/apply update thing, ( can't remember exactly what its called ) then find the update file.
Im not sure yet if you need to change the file name to update.zip, and make sure your battery is above 70% when you do this.
Any other people that know how to do this, feel free to correct me or add on to what I posted.
Sent from my DROID3 using XDA App

Oh and remember to get a root keeper app. Because the update removes root and moto/verizon removed the root exploit.
Sent from my DROID3 using XDA App

dpwhitty11 said:
You need to go back to a pure /system to flash the update. And I do not know if our current root methods work for it or not (I haven't read that thread yet).
BTW, you had the fixed camera when you flashed DarkDroid
Click to expand...
Click to collapse
Thanks, and that was some nice work on the ROM btw.
ChaoticWeaponry said:
If you are talking about the leaked OTA update, then you need to get back to the original Motoblur ROM, with all of the bloatware still on it. Then download the update and put it in the root of your internal storage. At that point, (don't quote me on this, im trying it tomorrow) you will power off your phone, and hold x and power at the same time, and the recovery mode will boot up (use the volume keys to make the menu pop up). At that point, scroll down to the install/apply update thing, ( can't remember exactly what its called ) then find the update file.
Im not sure yet if you need to change the file name to update.zip, and make sure your battery is above 70% when you do this.
Any other people that know how to do this, feel free to correct me or add on to what I posted.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
ChaoticWeaponry said:
Oh and remember to get a root keeper app. Because the update removes root and moto/verizon removed the root exploit.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks for the advice man. Check in with me tomorrow. Hopefully we'll both have working phones, LOL.

Grimace78 said:
Thanks, and that was some nice work on the ROM btw.
Thanks for the advice man. Check in with me tomorrow. Hopefully we'll both have working phones, LOL.
Click to expand...
Click to collapse
Haha, well I'll keep you updated, hard to screw up with updates though..

ChaoticWeaponry said:
Oh and remember to get a root keeper app. Because the update removes root and moto/verizon removed the root exploit.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I found 2 free apps for protecting an existing root. Voodo OTA and My Backup Root. Not sure if they will do the trick, but I am SO tempted to go ahead and try this update. Probably wait till tomorrow though.

Wish me luck! I can't hold off any longer and am going for it.

Grimace78 said:
Wish me luck! I can't hold off any longer and am going for it.
Click to expand...
Click to collapse
Good luck, I'm in the process of unbricking my phone (not from the update)

ChaoticWeaponry said:
Good luck, I'm in the process of unbricking my phone (not from the update)
Click to expand...
Click to collapse
what happened?

Grimace78 said:
what happened?
Click to expand...
Click to collapse
Installed a Bootstrap ROM on Safestrap. phones okay now, running Mavrick Beta.. lol

ChaoticWeaponry said:
Installed a Bootstrap ROM on Safestrap. phones okay now, running Mavrick Beta.. lol
Click to expand...
Click to collapse
I did the exact same thing, only I can't get past the MM symbol, and for the life of me cannot get into recovery either. The computer won't even recognize the phone. I think I'm screwed unless someone has a solution. The ONLY response that the phone has is to show the Motorola emblem if it is plugged into the wall, and afterwards turning it off is only possible by either letting the battery drain down or to pull it. I can't even turn it off and on.

Use my 5 min unbrick method. AP fastboot should never be broken.
Sent from my DROID3 using XDA App

ChaoticWeaponry said:
Use my 5 min unbrick method. AP fastboot should never be broken.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Found an odd way to "trick" it into CWM, but it won't stay in it. I think this could be a battery issue.

I would be very cautious as you say you have to keep this thing in good shape for financial reasons. There is an sbf but make sure you know how to use it and what you are doing before attempting the update.

pedwards3x said:
I would be very cautious as you say you have to keep this thing in good shape for financial reasons. There is an sbf but make sure you know how to use it and what you are doing before attempting the update.
Click to expand...
Click to collapse
Your warning was a good one, but I believe I got it done correctly (once I unbricked it, LOL). Does the system info look right to you?

Related

[Q] Official Froyo XXJPO Root

Hi all,
Sorry to ask this but with all the various firmware versions I am confused about which is a good Rooting program for the Official JPO Froyo release. Can someone point me in the right direction?
Thank you in advance
search is your friend.
Sent from my GT-I9000 using XDA App
CF root using Odin
Sent from my GT-I9000 using XDA App
Actually I have the same question as was confused about which method to use as well. My phone is JPO/JPP/JP3. I have searched but all the root methods I found were for earlier versions of froyo and users reported problems.
kiwijunglist said:
Actually I have the same question as was confused about which method to use as well. My phone is JPO/JPP/JP3. I have searched but all the root methods I found were for earlier versions of froyo and users reported problems.
Click to expand...
Click to collapse
Thank you glad to hear I am not alone
andrej.marinic:
Search is what started the confusion its hard to read all the threads to find out the end result.
I would also like to know if there is one that you can apply via the recovery method (like copying update.zip to sdcard) so I do not have to use a program like ODIN.
Thank you again in advance,
I did it using the CF method: http://forum.xda-developers.com/showthread.php?t=788108
its very easy and pain free
padlad said:
I did it using the CF method: http://forum.xda-developers.com/showthread.php?t=788108
its very easy and pain free
Click to expand...
Click to collapse
I also saw this but some people have had issues so I am bit reluctant to try it
cf-root works like a charm on JPA. no issues for me.
Sent from my GT-I9000 using XDA App
Cf root but make sure your 3 button download mode works as a failsafe
Sent from my GT-I9000 using XDA App
cenonmin said:
I also saw this but some people have had issues so I am bit reluctant to try it
Click to expand...
Click to collapse
Just make sure you use CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip
I have the official Germany Froyo. I will wait for the 3 Button fix and OCLF fix for the official Froyo.
I did tested other things and it made my phone slower and quickly out of memory. So I reset ( all data gone - but I did Backup my apps ) everything and it went normal
Just better wait until they find a solution for the official Froyo and not the unofficial Froyo.
I am using CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip flashed via Odin. Took 30 seconds and now I can use stuff like Titanium Backup and other useful apps. All on the official JPO through Kies.
silverstorm said:
I am using CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip flashed via Odin. Took 30 seconds and now I can use stuff like Titanium Backup and other useful apps. All on the official JPO through Kies.
Click to expand...
Click to collapse
Did you have any issues with 'un-rooting'??
EDITED:
What I am saying here is Kies totally bricked my phone and as such I won't use it again but instead Odin.
You however mention you are still using Kies. Did you have any issues in un-rooting when using Kies for the next flash... or have you not tried this yet?
Beards said:
Did you have any issues with 'un-rooting'??
Click to expand...
Click to collapse
Erm, not had a reason to un-root yet so haven't tried. But since this is flashed as a Kernel I presume I would have to flash another non-rooted Kernel through Odin in order to un-root. but don't know why I'd want to. If I wanted to upgrade to a newer version of Froyo, the root shouldn't affect it as far as I'm aware, it's only LagFixes really that are required to be disabled.
But to be on the safe side, you could re-flash a stock non-rooted JPO firmware from samfirmware.com through ODIN prior to going ahead with a Kies update, but this will mean you'll lose your data. I always go through this route anyway and then use Titanium backup to restore. (for which you'll require root!)
silverstorm said:
Erm, not had a reason to un-root yet so haven't tried. But since this is flashed as a Kernel I presume I would have to flash another non-rooted Kernel through Odin in order to un-root, but don't know why I'd want to. If I wanted to upgrade to a newer version of Froyo, the root shouldn't affect it as far as I'm aware, it's only LagFixes really that are required to be disabled.
Click to expand...
Click to collapse
Really... I could have sworn you have to take off any root prior to the next flash.
Beards said:
Really... I could have sworn you have to take off any root prior to the next flash.
Click to expand...
Click to collapse
Just lag fixes need to be disabled in order to flash via kies, the last couple of flashes i did had root already on, flashed no problem.
padlad said:
Just lag fixes need to be disabled in order to flash via kies, the last couple of flashes i did had root already on, flashed no problem.
Click to expand...
Click to collapse
Well what do you know...... Something new learned today.
Thanks Guys.
{
"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"
}
To root froyo use simpleoneclick.
Sent from my GT-I9000 using XDA App
tt4079 said:
To root froyo use simpleoneclick.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Links please.
http://forum.xda-developers.com/showthread.php?t=833953
Breaking News: New One Click Root app from RyanZA, the maker of the famous OCLF.

[INVALID] GingerBlur/GreyBlur + ALL AT&T Themes - DEPRECATED

This thread is no longer supported. Please reffer to: this thread
NOTES:
Attempted 3 times total. Working sucessfully for numerous users.
Followed guide above to the letter:
End result = Screenshots below.
Interestingly enough... System version of my phone = 4.1.5.7 Lol.... who knows what version it really is.
Baseband shows as: N_01.87.00R
This just means that the build.prop files was overwritten to display this:
ro.build.id=OLYFR_U4_1.5.7
ro.build.display.id=GreyBlur 2.0
ro.build.version.release=2.2.1
SCREENSHOTS:
Stock GreyBlur - Second Flash
{
"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"
}
Honeycomb theme for 1.5.7 deodex - on TELSTRA 1.4.2 - GreyBlured..
D_one said:
I'm all for one atrix community, alot of the mods work on both bell and atrix, I think this is great news but would like more clarity on the specific differences between builds. Why does the factory wipe allow it to work?
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
Click to expand...
Click to collapse
Thats the fun part... XDA community can work together to find this out...
I was willing to put my phone in the fire based on random tips people wrote.
but not only that I went ahead and tested various methods, themes on top of that..
So this is really interesting considering what we thought and knew could not work.
This working on AT&T?
I saw someone saying this worked, I thought it was a fluke, amazing! So all the optimization to SD card speed and memory work? Any chance this would also work on stock bell (.37)?
If your version is matching at&t I wonder what's really happening? Could it just be a custom build.prop file?
That's some hybrid of a system you got there Seven
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
DannyV94 said:
This working on AT&T?
Click to expand...
Click to collapse
You mean on 1.8.x?
Give it a go dude BE FEARLESS.. lol ionno but i'm freakin stoked because it worked on my Bell ATRIX
Dont try stock... just flash man, you will probably brick so just go 1.4.2 and thats that... either way its not like it matters because once you flash this you'll overwrite Stock and never get it back...
seven2099 said:
You mean on 1.8.x?
Give it a go dude BE FEARLESS.. lol ionno but i'm freakin stoked because it worked on my Bell ATRIX
Click to expand...
Click to collapse
I definitely would try it, but this phone needs to last at least another year, lol.
Don't really wanna brick it.
EDIT: BTW I'm not stock, I'm on GreyBlur 2.1 as of right now.
this is somewhat unnecessary since ken has started on a telstra sbf optimized version anyways, you might as well wait a few days and get a version that isn't quite as risky to install as this.
raybond25 said:
this is somewhat unnecessary since ken has started on a telstra sbf optimized version anyways, you might as well wait a few days and get a version that isn't quite as risky to install as this.
Click to expand...
Click to collapse
Thanks for that update on what ken's doing
raybond25 said:
this is somewhat unnecessary since ken has started on a telstra sbf optimized version anyways, you might as well wait a few days and get a version that isn't quite as risky to install as this.
Click to expand...
Click to collapse
Yeah i suppose you could do this if you were really impatient. We have already been waiting a while anyways so there is no harm in waiting just a couple more days
seven2099 said:
Dont try stock... just flash man, you will probably brick so just go 1.4.2 and thats that... either way its not like it matters because once you flash this you'll overwrite Stock and never get it back...
Click to expand...
Click to collapse
If I brick can't I still flash telstra? I'm pretty sure I can though I'll check first, I think someone did just that.
I'm going to sit tight with stock for the moment
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
raybond25 said:
this is somewhat unnecessary since ken has started on a telstra sbf optimized version anyways, you might as well wait a few days and get a version that isn't quite as risky to install as this.
Click to expand...
Click to collapse
zero risk... whats wrong witchu..
Do you have any idea what this could mean for DEVs?
The idea that this phone was thought not compatible with ATT sbfs... yet we have managed to get a perfectly working nandroid of it working.
D_one said:
If I brick can't I still flash telstra? I'm pretty sure I can though I'll check first, I think someone did just that.
I'm going to sit tight with stock for the moment
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
Click to expand...
Click to collapse
No brick, both ROMs work 100% flawlessly and yes I re-flashed in between.
seven2099 said:
zero risk... whats wrong witchu..
Do you have any idea what this could mean for DEVs?
The idea that this phone was thought not compatible with ATT sbfs... yet we have managed to get a perfectly working nandroid of it working.
No brick, both ROMs work 100% flawlessly and yes I re-flashed in between.
Click to expand...
Click to collapse
except sbf's still don't work, unless you've gone ahead and flashed a stock AT&T sbf then the fact that this is cross compatible simply means that ken didn't hit any fatal system differences in his pseudo-ROM changes.
raybond25 said:
except sbf's still don't work, unless you've gone ahead and flashed a stock AT&T sbf then the fact that this is cross compatible simply means that ken didn't hit any fatal system differences in his pseudo-ROM changes.
Click to expand...
Click to collapse
yepp and? this means what?
I can now flash any other theme from any other person and have no problem getting it to work on my phone as well as not needing any ports just to have them remake their framework for my phone.
Tested:
Tangerine
HoneyComb
Next in line for test is:
Arc Theme. (LOVE THIS.. can't wait to see how it works out.)
I have only found one bug and this is with swype. This was fixed by restoring old swype back up. This means nothing to me anyways but if a dev wanted to he could make a universal pseudo ROM that would allow people to do their thing instead of flash and find maybe 0 or 1 themes for their crappy framework.
This has the potential to unite a community and not instead keep things seperate and everytime simply get more and more fragmented as we bell users know, we are TINY.. if even numerically tangible on here. So.. give that a thought for a bit.
I'm all for one atrix community, alot of the mods work on both bell and atrix, I think this is great news but would like more clarity on the specific differences between builds. Why does the factory wipe allow it to work?
PS. I was referring to trying it on stock
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
D_one said:
I'm all for one atrix community, alot of the mods work on both bell and atrix, I think this is great news but would like more clarity on the specific differences between builds. Why does the factory wipe allow it to work?
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
Click to expand...
Click to collapse
Thats the fun part... XDA community can work together to find out why.....
I was willing to put my phone in the fire based on random tips people wrote.
but not only that I went ahead and tested various methods, themes on top of that..
I'd like a DEV to take a look at these results... because this is really interesting. No SBF needed and my phone behaves like 1.5.7.
I have tested, Webdock, mirroring.. all the functions except for swype (easily fixed).. WORKING.
So this is really interesting considering what we thought and knew could not work.
I would like to know from a DEV is how do I find out what I really have on my phone now..?
seven2099 said:
Thats the fun part... XDA community can work together to work this out.
I was willing to put my phone in the fire based on random tips people wrote.
but not only that I went ahead and tested various methods, themes on top of that..
I'd like a DEV to take a look at these results... because this is really interesting. No SBF needed and my phone behaves like 1.5.7.
I have tested, Webdock, mirroring.. all the functions except for swype (easily fixed).. WORKING.
So this is really interesting considering what we thought and knew could not work.
I would like to know from a DEV is how do I find out what I really have on my phone now..?
Click to expand...
Click to collapse
So your telling me that if i install it your way i can use the Webtop files from the AT&T build? i could never.. EVER figure that out for my phone for some reason.
Ratchet556 said:
So your telling me that if i install it your way i can use the Webtop files from the AT&T build? i could never.. EVER figure that out for my phone for some reason.
Click to expand...
Click to collapse
Lol you should check Sograth's thread.
I had that confirmed and working on 0.37 from bell..
Sograth even made a script fix just for us bell users son...
old news.
seven2099 said:
Lol you should check Sograth's thread.
I had that confirmed and working on 0.37 from bell..
Sograth even made a script fix just for us bell users son...
old news.
Click to expand...
Click to collapse
Yeah i tried it a while ago with no luck. ill try it again just for old times sake but im on 1.4.2 now and im not sure if it works with that yet.
Ratchet556 said:
Yeah i tried it a while ago with no luck. ill try it again just for old times sake but im on 1.4.2 now and im not sure if it works with that yet.
Click to expand...
Click to collapse
EDIT: I believe it should work as is atm. It just requires a bit of re-writing in his script.

[TOOL] HTC Vivid S-Off All-In-One Toolkit v1.0 [6-6-2012]

Post 1 - Information
Post 2 - Downloads and Release / Change Information
Post 3 - Bugs, Future Additions to the GUI, FAQ
Introducing Hasoon2000's New HTC Vivid All-In-One S-Off Toolkit!
This toolkit is here to get the party started to those who are looking to S-Off their devices!
If this helped you out, Please press the thanks button and if you want, you can always donate!
Prerequisites
- Must be on a stock ROM
- Must be HTCDev unlocked
- Must be rooted​
FEATURES​
- Links to a video and instructions to prepare you to S-Off your device
- HTC Drivers
- Command to flash an HBOOT of your choosing (Be sure you know what you are doing!)
- Command to flash a Recovery of your choosing
- Links
Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this!
Juopunutbear S-Off Thread
Juopunutbear Website
PM me if you need a phone unlocked (XDA/AD)
S-Off Toolkit Thread (XDA)
Here is a screenshot.
{
"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"
}
How To Use. THIS IS FOR THE PC ONLY. No plans ever for Mac or Linux. Sorry.
1. Download the toolkit DO NOT RENAME THE FOLDER
2. Download Winrar from here. Install it after you download it
3. Extract the folder anywhere.
4. Run the program.
Credits
- The guys at the AutoIT help forum that helped me learn how to make the script!
- Developers that made ControlBear!
- The community for being awesome!
- HTC for making us the phone so we can be a community!
- To everyone else I may have forgotten!
*DISCLAIMER*​
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given
PLEASE NOTE: S-OFF CAN RENDER THE SD CARD IN OPERABLE! PLEASE USE A SMALL 1GB MEMORY CARD OR AT LEAST BACK UP YOUR FILES JUST IN CASE!!
DONATIONS​​
Downloads - All my Downloads will now be in my Dev-Host Account.
Link to All Available and Future Toolkits
http://d-h.st/users/hasoon2000/?fld_id=2769#files
V1.0 6-6-2012
- Initial Release
Bugs
- Directory has to have one word.
Ex:
Will Work. This will solve any issues if the buttons don't work when you press them.
C:\Users\John\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
C:\Users\John_Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
Will NOT work. Your directory will look something like this and buttons won't work when you press it.
C:\Users\John Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
If you have 2 words, put the folder in Drive C:
Ex. This will solve any issues if the buttons don't work when you press them.
C:\Amaze_All-In-One_Kit_V2.4
Click to expand...
Click to collapse
Looking to add in the future
- S-Off Mods
FAQs
Q - Why Did you make this?
A - To make life easier
Q - You are limited on features. Why?
A- You can always make a request!
Q - Will this work on other devices?
A - NO!!!!!!!!!!!!!!!!!!!!!!!! DO NOT DO THIS ON ANOTHER DEVICE!
Q - Will you support more devices in the future?
A - If people REALLY want, I can make it happen. I just don't want to make anything that nobody would use.
Q - Awesome! Can I make a donation?
A - Of course! Do not feel obligated though. If you would like to make a donation, you can click the button on my toolkit or under my username.
So cool, thanks for your hard work
Sent from my HTC PH39100 using XDA
ki11bert said:
So cool, thanks for your hard work
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Took a long time to do so I hope you guys truly enjoy it!!!
Sent from my HTC_Amaze_4G using Tapatalk 2
Well the vid from the program is not working. Says its removed and me being a long time flasher. i almost feel like a noob with this guide. where is the hboot.img im supposed to put in the folder? cant find it. and does this method require the wire trick?
saywhat4118 said:
Well the vid from the program is not working. Says its removed and me being a long time flasher. i almost feel like a noob with this guide. where is the hboot.img im supposed to put in the folder? cant find it. and does this method require the wire trick?
Click to expand...
Click to collapse
I guess they removed the video?
I do not provide HBOOTs.
- Command to flash an HBOOT of your choosing (Be sure you know what you are doing!)
Click to expand...
Click to collapse
Since many people do not know what it is, I do not provide them since people will brick their phones since they have no clue what an HBOOT is.
This does require the wire trick. I just made everything simplified.
hasoon2000 said:
I guess they removed the video?
I do not provide HBOOTs.
Since many people do not know what it is, I do not provide them since people will brick their phones since they have no clue what an HBOOT is.
This does require the wire trick. I just made everything simplified.
Click to expand...
Click to collapse
Got it, thank you.
could yoou reup the video? doesnt seem to be working on the program
oneslow5oh said:
could yoou reup the video? doesnt seem to be working on the program
Click to expand...
Click to collapse
They deleted it. I can show you a similar video (it is the same process)
Sent from my HTC_Amaze_4G using Tapatalk 2
hasoon2000 said:
They deleted it. I can show you a similar video (it is the same process)
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Who deleted it? Where did you have the video posted?
Sent from an HTC Vivid via XDA Premium
The op of the s-off wire trick
Sent by my WCX powered Vivid
#Winning
http://www.xda-developers.com/android/easy-s-off-for-amaze-vivid-rezound-and-mytouch-4g-slide/
Good job.
first of, i wanna thank hasoon2000 for all your hard work including this method to s off. bec of all your easy steps, i successfully permroot my htc raider from rogers, canada, and then s offed. however, im currently facing a major problem, and im hoping anyone in this thread could help me out. i recently relocked my bootloader without knowing that i wont be able to unlock it again with the same procedure using the htcdev unlock.bin command after being s offed. can anyone plz plz help me what to do...
is there a special command for this or method i could use; thanks much in advance guys.
JohnL_83 said:
first of, i wanna thank hasoon2000 for all your hard work including this method to s off. bec of all your easy steps, i successfully permroot my htc raider from rogers, canada, and then s offed. however, im currently facing a major problem, and im hoping anyone in this thread could help me out. i recently relocked my bootloader without knowing that i wont be able to unlock it again with the same procedure using the htcdev unlock.bin command after being s offed. can anyone plz plz help me what to do...
is there a special command for this or method i could use; thanks much in advance guys.
Click to expand...
Click to collapse
S-off is an unlocked bootloader. Forget about HTCDev. You never have to use it again once you have S-Off
Sent from my HTC_Amaze_4G using Tapatalk 2
hasoon2000 said:
S-off is an unlocked bootloader. Forget about HTCDev. You never have to use it again once you have S-Off
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
so then, how come im not able to install your cwm again from the vivid all in one v2.2
i thought about that too; once ur s off, you pretty much can do anything. but i cant get the cwm back bec im getting some error from ur vivid 2.2. this happened before the whole s off; i cant use the recovery menu from bootloader if its locked, so i knew i had to unlock it to get it worked.
JohnL_83 said:
so then, how come im not able to install your cwm again from the vivid all in one v2.2
i thought about that too; once ur s off, you pretty much can do anything. but i cant get the cwm back bec im getting some error from ur vivid 2.2. this happened before the whole s off; i cant use the recovery menu from bootloader if its locked, so i knew i had to unlock it to get it worked.
Click to expand...
Click to collapse
Did you install the JB HBOOT?
Sent from my HTC_Amaze_4G using Tapatalk 2
hasoon2000 said:
Did you install the JB HBOOT?
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
yes i did
well i guess if tell u the whole story, u'll know whats goin on. the reason i had to relock the bootloader was coz i was trying to install an official ics ruu (the at&t us ver) from one of the forums here. i was successful of doin it, except one thing was missing: i couldnt use my data to browse the net. i thought if i had my bootloader again locked, it would work. but still didnt.
i wasnt still able to fix that but its not really my main concern right now.
one thing i noticed tho after i installed the jb hboot after s off was successful - the lock/unlock mssg on top of my bootloader was changed w/ jb name. but after i installed the ics ruu and went to my bootloader, it was backed to unlock/lock msg; it was till s offed tho...
so basically thats the whole jits of it. before this whole mess i was able to do a nandroid backup on my sd card with everything on it, including permroot. since then i've been trying to get it backed unlock to get the cwm back and do a restore...
can I get a link to the video pllz...
Thanks in advance.

A friend wants me to root his phone

So a friend wants me to root his phone for him and put a custom rom on it. Its the galaxy I9000. I assume from reading posts that I use super one click to root, then rom manager to flash I9000 recovery and I will then have root/custom recovery? When I rooted my Infuse there were a lot of extra steps like having a modded recovery file in order to flash in rom manager. Is this phone just must easier or am I off on some steps?
WRONG PLACE.
Enviado desde mi GT-I9000 usando Tapatalk 2
So you are not rooting the phone but xda is?
Verstuurd van mijn GT-I9000
Cjohns8792 said:
So a friend wants me to root his phone for him and put a custom rom on it. Its the galaxy I9000. I assume from reading posts that I use super one click to root, then rom manager to flash I9000 recovery and I will then have root/custom recovery? When I rooted my Infuse there were a lot of extra steps like having a modded recovery file in order to flash in rom manager. Is this phone just must easier or am I off on some steps?
Click to expand...
Click to collapse
If im not mistaken then Super 1 click only works on Froyo and not with gingerbread but if your friends on froyo then that should work. If you can get into download mode then you could flash an odin stock rom like this one http://www.theandroidsoul.com/xxjvu/ then root with this http://www.theandroidsoul.com/root-xxjvu-firmware/ which adds root and clockworkmod then from there you can flash any rom you want. Or even just flash a CF-root which is compatable with whichever rom the phone is on
A friend of mine wants me to slap you.
It's easy to root the SGS, all you need is a rooted kernel for the version of Android you are using.
That being said, it is also easy to brick the phone if you are not familiar with proper flashing procedures for the Galaxy S.
There are a couple of good threads on how to flash the SGS, I advise you to read them.
Ian
I can't belive what I'm reading here! Is this some sort of joke I haven't heard of? Definitely wrong place!
Sent from my GT-I9000 using xda premium
A friend of mine wants me to slap you.
Click to expand...
Click to collapse
THIS !!
bhu1 said:
A friend of mine wants me to slap you.
Click to expand...
Click to collapse
Ahahahaha good one but slapping once only wont help here
This must be understood seriously,so he needs to be slapped very seriously too,not once or twice but a couple of times so he gets our point
Has 89 posts and doesn´t know how to flash OMG
This post gave me Cancer.
PinkAfro said:
This post gave me Cancer.
Click to expand...
Click to collapse
not funny at all, thats not a joke
{
"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"
}
Wow 89 posts and you still don't know where to put them. Lmao. Flaming is 100% deserved here.
Sent from my SAMSUNG Infuse using XDA
Wow guys I get you guys flaming him but at least help the guy out.
To the OP:
I rooted such a long time ago that I am not sure if I am remember correctly but I can give you a link follow the instructions on it.
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
Read the rule before you post dude
Everyone needs to relax! everyone has posted in the wrong spot or were we all experts from the beginning.
Now using this forum s search tool while in the galaxy s i9000 general forum. Good luck
Sent from my GT-I9000 using Tapatalk 2
Cjohns8792 said:
So a friend wants me to root his phone for him and put a custom rom on it. Its the galaxy I9000. I assume from reading posts that I use super one click to root, then rom manager to flash I9000 recovery and I will then have root/custom recovery? When I rooted my Infuse there were a lot of extra steps like having a modded recovery file in order to flash in rom manager. Is this phone just must easier or am I off on some steps?
Click to expand...
Click to collapse
first the slap.
second:read the stickies in general section for i9000.its very easy
Cjohns8792 said:
So a friend wants me to root his phone for him and put a custom rom on it. Its the galaxy I9000. I assume from reading posts that I use super one click to root, then rom manager to flash I9000 recovery and I will then have root/custom recovery? When I rooted my Infuse there were a lot of extra steps like having a modded recovery file in order to flash in rom manager. Is this phone just must easier or am I off on some steps?
Click to expand...
Click to collapse
When rooting anything use lube and hang on!
Sent from my GT-I9000 using Tapatalk 2
bambam1978 said:
Everyone needs to relax! everyone has posted in the wrong spot or were we all experts from the beginning.
Now using this forum s search tool while in the galaxy s i9000 general forum. Good luck
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
No one has asked such question when we had already posted 89 times.
bambam1978 said:
Everyone needs to relax! everyone has posted in the wrong spot or were we all experts from the beginning.
Now using this forum s search tool while in the galaxy s i9000 general forum. Good luck
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
+1

[Q] Bricked my tablet. Could use some help

Followed this tutorial to the letter and bricked it. I should have known that it would happen, the video it self was rather sketchy to begin with http://youtu.be/fXDvq5SaA70
Anyways, i was hoping maybe someone here could help? The errors im getting are as follows"
E:Failed to mount /efs (invalid argument)
E:check_selective_file:Cant mount /efs
E: Failed to mount /preload (invalid argument)
E: Install_application_for_customer: Cant mount /preload
your storage not prepared yet, please use UI menu for format and reboot actions [my sd card is in the tablet so i dont know why i am getting this error]
E:Failed to mount /efs (invalid argument)
E: multi_csc: Can't mount /efs
Multi-csc applied failed
Dealing with phones seems much simpler... never had a problem rooting other devices.
Does it matter that i did it with odin rather then with heimdall? Im use to odin so i just rather not use heimdall
If you can go to download mode, use overcome method like thousands other.
Follow my signature for the link.
I am assuming yours is P1000 since you didn't say.
Sent from my GT-N7100 using xda app-developers app
I have the verizon one, no idea if that means its the p1000 version.
just got this http://forum.xda-developers.com/attachment.php?attachmentid=835192&d=1325238872
Why is rooting this device so difficult? Never had as much problems with other devices. I'll go ahead and try the overcome method but im willing to bet something goes wrong even then.
The Barron said:
I have the verizon one, no idea if that means its the p1000 version.
just got this http://forum.xda-developers.com/attachment.php?attachmentid=835192&d=1325238872
Why is rooting this device so difficult? Never had as much problems with other devices. I'll go ahead and try the overcome method but im willing to bet something goes wrong even then.
Click to expand...
Click to collapse
Nah..if you try the overcome method..and you download all the needed file and the guide..then follow exactly what the guide told you..nothing going to go wrong..it's foolproof..but verizon..isn't p1000..and i don't remember if overcome method suppot verizon or not..
Edit: just check..overcome don't support SCH-I800..
Correct me if I'm wrong..:thumbup::thumbup:
(҂`☐´)︻╦̵̵̿╤── .:system:.
Confirms not supported
And that video you follow too... For P1000 from the title. I didn't watch.
I guess you flashed a P1000 ROM?
Sent from my GT-N7100 using xda app-developers app
priyana said:
Confirms not supported
And that video you follow too... For P1000 from the title. I didn't watch.
I guess you flashed a P1000 ROM?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Yeah thats what happened then.
It seems like there's almost no information or love for the sch-i800 haha oh well. If you guys find anything on it though let me know! I'll continue looking tomorrow (about to hit the hay!) but right now it seems like there may not be a solution to my problem :crying: Thank you guys for all the help so far!
The Barron said:
Yeah thats what happened then.
It seems like there's almost no information or love for the sch-i800 haha oh well. If you guys find anything on it though let me know! I'll continue looking tomorrow (about to hit the hay!) but right now it seems like there may not be a solution to my problem :crying: Thank you guys for all the help so far!
Click to expand...
Click to collapse
{
"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"
}
Here you go..
http://forum.xda-developers.com/showthread.php?p=11601647
It might be old..but that should be a good place to start..
Edit: would you look at that..priyana used to help a similar problem.. and it maybe would help you..
http://forum.xda-developers.com/showthread.php?p=35118206
P/s: try to search the general and Q&A section using "SPH-I800" or "Verizon"
(҂`☐´)︻╦̵̵̿╤── .:system:.
A lot of the links are broken in the original post
Edit: I think the tablet is hard bricked now... wont turn on or display anything
The Barron said:
A lot of the links are broken in the original post
Edit: I think the tablet is hard bricked now... wont turn on or display anything
Click to expand...
Click to collapse
Thats why i told you to "start" from there..
And try to charge it for 4 hour..and try to power on..
Edit: don't just read the op..read other post too..there's might be someone post a working link..
(҂`☐´)︻╦̵̵̿╤── .:system:.
mike_disturbed said:
Thats why i told you to "start" from there..
And try to charge it for 4 hour..and try to power on..
Edit: don't just read the op..read other post too..there's might be someone post a working link..
(҂`☐´)︻╦̵̵̿╤── .:system:.
Click to expand...
Click to collapse
I mean, i tried to start from there and it seemed bricked haha.
Power was dead -.-
Well im gonna see what i can do then with that. Thank you!
Would it matter if i just installed the correct rom of cyanogenmod instead of stock?
The Barron said:
I mean, i tried to start from there and it seemed bricked haha.
Power was dead -.-
Well im gonna see what i can do then with that. Thank you!
Would it matter if i just installed the correct rom of cyanogenmod instead of stock?
Click to expand...
Click to collapse
About the power..you shoud try to let it charge for 4 hour..with wall adapter and if that doesn't work try with usb..then try to power it up..
About installing straight with cyanogenmod..that wouldn't work..coz you need custom recovery (eg. clock work mod[cwm]) to install it..and with your device stuck in secondary download mode..which mean you can't even go to stock recovery mode..
cyanogen must be install via custom recovery mode..
With that being said..
It's matters..
(҂`☐´)︻╦̵̵̿╤── .:system:.
Make sense
Alright i will let it charge for a couple of hours it keeps switching back from secondary download mode to not even on!
Also found this, sounds like it will work! http://www.droidforums.net/forum/samsung-galaxy-tab/113084-how-restore-vzw-galaxy-tab-stock-dj11-9.html#post2118311 Thank you Milke!
I hate to double post but it would be nice if someone could help me out a bit here:
So i made some progress, i can get into download mode now and there is a charging screen and a boot noise (no animation). The problem is when i try to go into recovery mode, i get a whole bunch of screen tears and random red and yellow lines appear the screen and then, well i presume it crashes, reboots, and goes back tot he charging screen.
What im thinking is somehow my bootloader got deleted?
Ive been searching nonstop for a boatloader to put into odin or heimdall but to no avail. Do you guys have any ideas?
You are quite right on. The multi coloured bands is usually bad bootloader. Not deleted, but I knew when people patched their GB bootloader ( with patch meant for Froyo), that happens.
You need to find a complete Rom package that is with boot.bin and Sbl.bin
Within its tar file.
I am not knowledgeable in Verizon tab, so can't help much. But there is a thread in dev forum that has stock rooted Verizon or sprint.
Sent from my GT-N7100 using xda app-developers app
Did you try to take stock samsung rom from samfrimware? And then try the rooting proses again?
-----------------------------------
(҂`☐´)︻╦̵̵̿╤── .:system:.
-----------------------------------
-----------------------------------
priyana said:
You are quite right on. The multi coloured bands is usually bad bootloader. Not deleted, but I knew when people patched their GB bootloader ( with patch meant for Froyo), that happens.
You need to find a complete Rom package that is with boot.bin and Sbl.bin
Within its tar file.
I am not knowledgeable in Verizon tab, so can't help much. But there is a thread in dev forum that has stock rooted Verizon or sprint.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Okay so i got both of these things, where do i put them in respect to heimdall? I know one has to go in the primary bootloader slot (im assuming its boot.bin that goes there), but where does the other one go? And should i load all the extra files with it or just these two files by themselves?
Also mike i got the stock samsung rom but not from samfrimware, there was a google doc page with a zip file with all the stock samsung stuff for the cdma/sch-i800 which i downloaded and used to get out of my hard brick. So i believe its the right one but now its just a question of fixing the bootloader
The Barron said:
Okay so i got both of these things, where do i put them in respect to heimdall? I know one has to go in the primary bootloader slot (im assuming its boot.bin that goes there), but where does the other one go? And should i load all the extra files with it or just these two files by themselves?
Also mike i got the stock samsung rom but not from samfrimware, there was a google doc page with a zip file with all the stock samsung stuff for the cdma/sch-i800 which i downloaded and used to get out of my hard brick. So i believe its the right one but now its just a question of fixing the bootloader
Click to expand...
Click to collapse
Yeah..notice that priyana said..there some rom with gb bootloader..with patch meant for froyo..?
But if you confirm that you got yhe correct stock rom..i recommended that you go to heimdall guide..
Here:
http://forum.xda-developers.com/showthread.php?p=22777739
-----------------------------------
(҂`☐´)︻╦̵̵̿╤── .:system:.
-----------------------------------
-----------------------------------
The thread just tells me a lot of stuff i already know, it doesn't discuss the primary bootloader much though.
So im thinking this would be a good setup. Pretty much the exact thing ive been running except i put the boot.bin in the primary bootloader slot as well.
Also dont mind the progresso bread crumbs i have in my tabs

Categories

Resources