Related
I have an unlocked milestone ( telus originally) that i bought off kijiji, and he said it was rooted, but when i open rom manager said that it is not.
How can i tell if it is? Its running super choppy and want it sped up! It has 2.2.1 on it currently!
You can download this app: http://www.appbrain.com/app/android-terminal-emulator/jackpal.androidterm
And then type
su (hit enter)
From here it might pop up with a superuser access request, that would say that you have root access.
If not, then follow by typing whoami. If it says root, then you have root access.
Hope that helps.
root?
I downloaded that and typed in su and then hot enter and i get access denied!
Typed in the whoami one as well and same thing.
So does that mean it has definately not been rooted?
Also, if not then what would be the best way to go about rooting? If it has 2.2.1 then that is more then likely just the regualar telus froyo update right?
Yeah, that means it probably isn't rooted.
There are various ways to root the phone. I used Universal Androot, but you can also just flash the vulnerable recovery SBF via RSD Lite, load Androidiani Open Recovery onto your phone and then boot into recovery, and there will be an option to root the phone that way.
http://forum.xda-developers.com/showthread.php?t=983516
I did the sbf thing with my other milestone and i lost my gps features.
I heard the the universal androot is pretty easy though. I just want to root it so i can put milestone overclock on it to speed it up.
how easy did you find universal androot, and if you dont mind the steps to do this?
Any other tips and tricks to speed it up?
I found the apk on androidforums.com. It's called Universal Androot v1.6.2 beta 5.
What you can do is run zeppelin's scripts to supercharge your phone.
I have heard that Milestone Overclock is actually quite dangerous because of not changing the proper vsel's
My reccommendation is to root the phone, then install a custom ROM, most already include an O/C(FroyoMod is 900MHz, CM7 is 1GHz)
I just modified the files directly using Root Explorer.
Sent from my Milestone using XDA Premium App
I have have read that 800mhz is about right for the overclock.
What ROM would you suggest to use with it that will also have all the features still?
Right now, I think that CM7 is one of the most stable and it's also updated fairly frequently.
What you want to do to before you apply the update is to download TitaniumBackup and backup all apps with data.
Once you flashed the vulnerable recovery, you want to install AOR.
Before you flash CM7, you want to create a Nandroid backup. It's all specified in the thread I posted.
After that, place CM7 AND the Google Apps update into OpenRecovery/Updates. Boot into AOR (Power+x, see the Moto M and hold camera+volume up button) select apply update. You will now you are in AOR when you see the Android Andy dressed up as Mario, if not, then select apply update.zip. Select wipe dalvik cache, wipe cache partition and select Wipe data/Factory Reset. Select Apply Update, choose CM7. Once that's done, wipe dalvik and cache partition again. Apply update again and then choose the Google Apps. When that completes, wipe dalvik and cache partition again.
Select change baseband from AOR Main Menu, and choose whichever one you want. In your case it will probably be Telus.zip.
If you followed those steps you should be good.
Sent from my Milestone using XDA Premium App
rooting also can be done via AOR...
I thought it might be useful to put all the info into one thread.
I hope it's completely needless to say that I don't take any credit, since I haven't contributed anything to make that possible
This guide is for rooting your CURRENTLY installed firmware, flashing custom roms, or if you want to upgrade to Gingerbread
If you are NOT S-OFF yet, you either need to get / use an XTC Clip, or use a software exploit / hack (AlpharevX).
The basic differences between both approaches are the following:
AlpharevX:
"Software" S-OFF using an exploit
Bootloader S-OFF
It will flash a hacked HBOOT that sets your device S-OFF.
If you flash an unmodified RUU, or anything that replaces this HBOOT, you will lose S-OFF
-> Not a problem if you stay with custom roms!
Completely free and great solution!
XTC Clip:
Complete "hardware" S-OFF
All locks removed including sim and cid lock.
Permanent solution (radio S-OFF)
-> You can flash anything and won't lose S-OFF
Costs money, or you need to find someone that owns a Clip to do this for you
UPDATE:
Hawkysoft posted about a rare occurrence that has been reported after using AlpharevX:
If you get a security warning in hboot, you will need an XTC Clip to get you running again!
Of course you might also send your phone to repair, but you'll most likely need to pay for that.
So if you experience this problem, either get someone with an XTC Clip to help you out, or buy an "XTC Clip Pay as you go", which is a very cheap variant that comes only with one use (rechargeable) and costs around 30USD.
See the following tutorial to set your device S-OFF with AlpharevX: GUIDE -> S-OFF
And pause at the point where you should install CWMR (ClockworkMod Recovery) to consider the following options:
Do you want to switch to a custom rom after S-OFF?
-> continue with the guide above installing CWMR
Do you want to keep your official firmware and replace your official recovery with CWMR?
--> continue with the guide above installing CWMR,
but before you install a custom rom, make a backup of your current firmware in CWMR!
Do you want to keep your orig firmware AND the official recovery?
--> don't continue with the guide above and follow this guide instead
Be it Froyo or Gingerbread doesn't matter.
If you insist you only want to root your Froyo rom and not upgrade to Gingerbread immediately, please scroll further down.
A rooted Froyo rom is NOT necessary for flashing and afterwards rooting Gingerbread!
If you need further details about flashing custom roms just scroll down.
If you haven't done so already (you didn't get an OTA or you didn't do it manually yet) and you want to upgrade to Gingerbread, here's a short guide on how to flash it first..
How to install the Gingerbread update
download one of the Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1033922
This link is for the Incredible S only of course, but the following works also for the Desire S, but then please use a rom for your phone
ATTENTION: If you are NOT S-OFF yet and you are planning to using AlpharevX, you MUST use an ruu compatible with AlpharevX! Check that first!
start the RUU installer
[*]go into your tmp folder to get rom.zip from the extracted files of the RUU installer:
Access the tmp folder by clicking on start/run and put %tmp% into the textbox. Or for windows 7 put this into this search textbox in the "start menu"
Look for the most recent folder (sort by date). In that folder look for rom.zip or simply do a search.
After acquiring rom.zip from your tmp folder you can exit the RUU installer
[*]Put rom.zip onto your sdcard and name it PG32IMG.zip.
boot into the bootloader.. (press and hold vol.down + press power) it will automatically start to install it and ask you if you want to proceed.
After a reboot remove PG32IMG.zip from your sdcard (otherwise it would ask you to reinstall the update each time you boot into the bootloader)
use morelocales2 from the market if you need additional languages
finished. Now follow the steps below for rooting the fw
Guide below partly out of date!
It works, but there are easier methods available now.Work in progress
What you need if you want to root your Gingerbread rom:
an incredible S / Desire S that is S-OFF
Gingerbreak OR SuperOneClick newest version
Busybox
UPDATE:
Some users reported that they weren't able to root using SuperOneClick or Gingerbreak.apk no matter what they tried.
After I reflashed my IS I also run into problems. Although it's not unusual that it doesn't work the 1st time, I decided to do it manually.
I have attached a zip with all the files needed and a script that you could try which does everything for you.
It doesn't do any magic or different than SuperOneClick, but if you do it this way you get to see what's actually happening and if it fails and where / why.
When using this you also don't need to reboot between the tries, reinserting / remounting your sdcard is sufficient.
Please report any bugs.
How to use:
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
download the zip file: View attachment 596033
extract the zip and open a shell/command prompt and change into that directoy
on Linux start runexploit.sh, on Windows start runexploit.cmd
if Gingerbreak doesn't finish and you ONLY get to see lots of "sendmsg() failed?" without any other messages in between, you should try any of the following options:
hit ctrl + c to abort, unmount / remount your sdcard and start over. It could take a few tries
Doublecheese reported it took him 8-9x
WHILE Gingerbreak is running and printing "sendmsg() failed?" forever, pull and take out your SDcard completely and reinsert it
this worked well for vontdeux, jkolner and me
Thanks to Vontdeux, Doublecheese, jkolner and everyone else afterwards for the feedback!
now, after you see '#', you can hit ctrl + c or close the shell
run root.sh on Linux or root.cmd on Windows from the same directory. This will install su, SuperUser.apk and busybox
when it's finished you're done and have root
then it's very recommended to get "rom manager" from the market, open it and install clockworkmod recovery for installing custom roms, backing up your system et.c.
Files:
Big thanks to Chainfire for GingerBreak and CLShortFuse for SuperOneClick!
SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682
OR Gingerbreak: get the latest version here: http://forum.xda-developers.com/showthread.php?t=1044765
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
use the latest SuperOneClick which might be easier.
start the application and select "GingerBreak" as exploit.
But respect the info and warning of the creator of the Gingerbreak.apk:
Chainfire said:
WARNING: Apparently on some devices the root exploit causes the SD card (internal or external) to be formatted. Also, if it gets stuck but you do see the card mounting/unmounting, try formatting your SD card yourself and try again (or use a different SD card) often this works (a fix for both issues is being looked at)
Click to expand...
Click to collapse
click root check Chainfire's post if you run into problems (also with SuperOneClick because it uses his exploit): http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
after it's finished your phone will reboot and you're essentially done.
Alternatively, don't use SuperOneClick but follow the guide of Chainfire from the beginning to install Gingerbreak on your device and root your phone: http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
What you need if you want to root your Froyo rom:
an Incredible S / Desire S that is S-OFF
SuperOneClick newest version
(optional, but highly recommended) Busybox installer app
Files:
Update: apparently the current SuperUser app is crashing for some users.
If you experience these problems see the next section
Big thanks to CLShortFuse for SuperOneClick!
SuperOneClick:: http://forum.xda-developers.com/showthread.php?t=803682
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:
use the latest SuperOneClick
start the application and select "psneuter" as exploit.
click root
after it's finished you might need to reboot for getting Superuser app to pop up when needed.
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
So how to flash custom roms?:
it's extremely easy
put your favorite custom rom onto your sdcard
install rom manager if you haven't done so already
open rom manager and click "install ClockworkMod Recovery
next click "install rom from sdcard"
select your custom rom you put on your sdcard
select to backup your currently installed rom just in case you want to revert back
Most of the time you also need to check wipe cache and data (follow the instructions of the creator of that custom rom to find out if you need to do that or not. If you wipe your data, all your current settings will be lost however so make a backup!)
wiping Dalvik Cache is always a good idea and won't harm your settings
after pressing ok, Rom manager will boot into Recovery, backup your current rom (if you told it to), wipe (if you told it to), install the custom rom and reboot
Solution for SuperUser crashing:
All thanks go to rmk40 who patched SuperUser for us running newer versions of Sense:
http://forum.xda-developers.com/showthread.php?t=886999
rmk40 said:
The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
Click to expand...
Click to collapse
How to install the patched version
Update 5/14: Fixed a serious bug in the replace_su script that made it pretty much useless
If you didn't root your phone yet
You might want to patch SuperOneClick before using it the first time.
Either download the patched su and SuperUser.apk, or just use the already patched version of SuperOneClick attached to this post. View attachment 591017
If you already rooted your phone:
Usually the first app requesting root access does work with the unpatched version, so you can use this to gain root access on the shell to replace SuperUser and su with the patched versions. If SuperUser doesn't pop up, open Superuser and remove all apps you already whitelisted for su access and try again
To keep it simple, I have attached an archive with a script to do this for you: View attachment 595753
make sure USB Debugging is enabled (in settings/apps/development)
extract replace_su.zip on your windows or linux pc
open a terminal and change into that directory
on windows run replace_su.cmd, on linux run replace_su.sh
the script needs root access so you need to press allow when SuperUser pops up on the phone
If you already installed a custom recovery and want to do it that way:
Just download rmk40's flashable zip: http://forum.xda-developers.com/showthread.php?t=886999
put it onto your sdcard
reboot into recovery by starting rom manager and selecting reboot into recovery
if this doesn't work because SuperUser fc, shutdown your phone completely (fast boot disabled in settings/power). Press and hold vol-down and press power. From the bootloader menu: select "recovery"
use ClockworkMod to flash the zip. "install/flash zip from sdcard.."
you can also just replace those files (SuperUser.apk and su) in your SuperOneClick directory and then re-run SuperOneClick.
Here's the "patched" SuperOneClick View attachment 591017
Update 5/14: Fixed an error in the replace_su script.
Update 5/10: updated because of a request to re-add the Froyo rooting info
Update 5/09: updated because of SuperUser crashing issue
Update 4/27: updated due to new version of SuperOneClick now supporting Gingerbreak
Update 4/26: updated because of Gingerbreak, which makes this much shorter and easier. Thanks very much Chainfire for all the hard work!
Update 4/24: thanks very much to Hawkysoft for pointing out that psneuter doesn't work for Gingerbread and further instructions)
So if you are already gingerbreaded, please scroll down
Update 4/23: OFFICIAL CLOCKWORKMOD RECOVERY NOW AVAILABLE!!
Big thanks to Koush and Hawkysoft!
Hawkysoft said:
time has arrived, after supplying all the info, koush did a hell of a job with creating this
download rommanager from the market
and install the recovery for the Incredible S
WARNING DO NOT PARTITION SDCARD <- THIS WILL BRICK YOUR DEVICE, A FIX IS ON THE WAY
all thanks go out to koush offcourse
i tested:
backup, whipe data, restore, reboot... all worked
bugs found:
sdcard > if you do parition this, you will end up jtaggin your device cuz its bricked! (the fix is on the way)
backup time > in the folder it shows a wrong time that it has been created atleast for me it does.. it shows a 3 hour difference idk how its set but its not a big deal in my opinion
Click to expand...
Click to collapse
Please check the post by Hawkysoft!
http://forum.xda-developers.com/showthread.php?t=1046759
Nice, thanks!
OTA Updates
TimMun said:
Nice, thanks!
Click to expand...
Click to collapse
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
madmaxx82 said:
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
Click to expand...
Click to collapse
I don't know the answer to this question but first I would like to actually see an update
TimMun said:
I don't know the answer to this question but first I would like to actually see an update
Click to expand...
Click to collapse
Haha, it was really funny coincidence. After I s-offed the phone I got an OTA
BTW: If anyone wants to be S-OFF and doesn't mind visiting me in Austria, I'd help you out. For free of course
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
timbo007up said:
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
Click to expand...
Click to collapse
Thanks, so if it doesn't work you'd need to reflash the original recovery first..
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
Ahh thanks for the warning
Since the custom recovery is installed already anyway when there's an OTA update available, wouldn't the following work?
If I get notified about an available OTA update, I could flash a complete RUU, then get the OTA and afterwards re root + reflash the custom recovery?
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
nikant said:
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Correct. Its only needed to flash custom roms.
Sorry for newb question... What does S-OFF mean?
Read the rooting topic in the dev section,
But to make it easy for you: S-OFF means Security Off.
Which allows us to (over)write system files
timbo007up said:
Correct. Its only needed to flash custom roms.
Click to expand...
Click to collapse
And nandroid Can't live without it... of course especially if you flash custom roms, but also if you don't, titanium is just not always 10.000% enough
There is another recovery available from GOAPK with Reboot function that works.
can you confirm that it fully works with backin up and restoring?
since the current one failes at restoring
;p
testing it...
first try to backup FAIL <- Error while generating md5 sum!
second time as well this is a major failing recovery
I am going to try porting clockwork myself from scratch tonight
Sent from my HTC Incredible S using Tapatalk
With this recovery in the first post, I had an error at the time of restoration, with the one I posted, an error of md5 sum, but with the tutorial as an attachment, the worries of md5 sum is adjusted by 5 minutes
So I can now restore quietly after each crash, as I try to adapt a framework-res.apk to my Incredible S
Just at it now
creating md5 sums failed.. restore of course also failes..
I just restored a previously created backup with the one from llnhhy successfully
So we have a recovery that has all the functions, but has trouble creating md5 sum, and another that did not have the reboot function with a problem of restore, by mixing the two should do it .. .
Hello Nookers,
I myself and pndo1 of XDA have posted guides for dual booting CM7 and Stock 1.2. My first one was crappy, my second one was a little less crappy, and pndo1's was pretty good, but had too many steps. So yeah, I decided to clear this up once and for all. Alright, enough of that garbage, let's get on with the guide!
0. Make a CWM sd card using these instructions.
1. Download CM7 to your sd card. I recommend the latest version from here. Also, if you would like to overclock download this. Lastly, if you would like to remap Volume + and - to Menu and Back, download this too. Also, your gonna want (duh) have a copy of Nook Color Stock 1.2. This one is the best in my opinion. Also, if you would like to root Stock 1.2, get this. Now get gapps from here. Almost! Download thishere. And now the multiuboot! Grr... this is tiring... but lasties! Get it here. Put ALL the files you downloaded on your SD Card.
1. Boot into CWM. Go into Backup+Restore and create a backup. Then go into Mounts+Storage and unmount the sd card. Put in an MicroSD reader in your computer. Navigate to /sdcard/clockworkmod/ and find the backup. Copy it to your computer. You can now delete it from the SD Card. Put the SD Card back in the nook. Go into Mounts+Storage and hit "Mount sd card" Now from the same place, wipe system, data, and cache. Now go to the root menu (hit the power button once). Hit "Install zip from sd card" then "Choose zip from sd card" Select prep.dualboot.zip. Then redo the choose zip Select your downloaded 1.2 Zip. It should be called "update_nc_stock_1.2_keepcwm.zip" Flash that. Now wait for it to install. Reboot your Nook. It will boot and will ask you to setup the Nook. Set it up but if you don't have wifi, follow these instructions. After setting up, boot back into CWM using your sd card.
2. Now Choose the zip from sd again, but select ManualNooter. That will take one minute to flash. Reboot again. Make sure your root is setup. To confirm, download an app from the market. Any app.
3. Once that is done, boot back into CWM. Flash the zip "eclair-to-dualboot-0.2.zip" It will duplicate Stock 1.2 to the Second partition. Now go into Mounts+Storage, and wipe system+data+cache. Now choose zip again, but this time pick CM7. Then Choose again, pick GAPPS. Then anything else, like that KeysMod or OC kernel. Now flash Multi-Uboot-0.3.zip. Now reboot without holding anything. It should boot CM7. Reboot, but this time hold the home button. BAM! Stock 1.2. Hope it worked for ya!
To those whom it doesn't work:
yelloguy said:
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
Click to expand...
Click to collapse
Credits:
@GirLuvsDroid for the feedback and testing
@GabrialDestruir for 1.2 Manual Nooter
@Koush for ROM Manager and CWM Flashes
@yellowguy for telling us to flash prep.dualboot
@Anyone else who helped but escapes my mind at the moment
@pndo1 (Who has moved on to better things than our little NC's... aka Flyer) for this orignal project
I've been wanting to dual boot my NC for a while now, but I've read several sets of instructions and kept getting twisted up in them. I was also concerned that having a dual boot would make it difficult to impossible to continue installing the CM7 nightlies and the latest Dal kernels.
These instructions look really clear and easy to follow and I thank you for that!
I just want to clarify my understanding: both CM7 and stock 1.2 are run from eMMC, correct? And, because stock 1.2 is on the second partition, it's just business as usual to install the nightlies and the latest kernel on the first partition, right?
Again, thanks for taking the time to rework your instructions again. Your contributions are much appreciated!
Why a special uboot? Stock cm7 uboot (based on bn 1.2) already does multiboot... (hold down n on boot for info) and dalingrin's nook tweaks lets you set up default options from prefs menu...
That said, I didn't read the instructions carefully so maybe there's a reason...
@GirLuvsDroid Your welcome, and yes both run from the emmc. Flash nightlies and kernel like anything. Just nothing to the dual boot partition.
@fattire For me the CM7 Alternate boot option hangs. But again, that's me.
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
MHotovec said:
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
Click to expand...
Click to collapse
MH, it's the link in the OP that says this: "Last one (yes, really!) here." It's not the Multi-Boot-Uboot-0.3.zip but the eclair-to-dualboot-0.2.zip.
Disgregard this post -- I'm an idiot and apparently blind, as well.
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
MHotovec said:
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
Click to expand...
Click to collapse
I must be blind -- I don't see where it says to flash both. I only see the eclair-to-dualboot in the instructions.
Nevermind -- I found it. It's the last step. I stand corrected and I'm glad I do because I'm planning to do this when I get home from work tonight. Thanks for setting me straight!
Reflashing the eclair to dualboot wasn't the answer, now is doesn't even TRY to boot the stock 1.2.
Now where did I leave that drawing board....
I found the download link for the Multi-Boot-Uboot-0.3.zip:
http://api.viglink.com/api/click?fo...dified u-boot.bin based on B&N 1.2 source
GLD, if anyone tells you that you're not a goddess, you tell them that I said you are.
Of course, that didn't solve the problem. (sigh)
I ran the entire routine again, and this time used the v.03 multi-boot that you found, same problem. It will boot into CM7 just fine, but it hangs up when booting into stock.
ahhhhhh, that's just so sweet, MH!
I just went through the whole process myself and everything went perfectly right up until I tried to boot into stock 1.2. Exactly like you, it hangs on the N and won't boot up. CM7 boots just fine, though.
Well, at least I know it's not just me.
By any chance, have you run the app that changes your Nooks RAM from 'new way' to 'old way'? (1gb data, 5gb apps).
I have, I wondering if that has something to do with it (just fishing of course, it's not like I actually KNOW anything).
Yes, I had a blue dot NC that I repartioned, but I did it using the custom partition (around 2GB data).
Well, multi-boot link added.
Oh, to those whom it doesn't work (stuck on N), try flashing 1.2 zip and manual nooter without rebooting and then eclair2dualboot then wipe system,data, and cache. Then flash cm7 and goodies. Not one reboot. Try it and only then say if it works or doesn't.
I'll try this no-boot method when I get a chance tomorrow. One question for you -- assuming I get this to work, is there any reason I can't restore /data from the CWM backup of my original setup that I made before I started the dual boot process?
I get the same result with the no boot method. CM7 boots fine, Nook stock hangs on the 'N' screen.
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
@GLD Yes, I think you can restore safely.
@yellowguy You don't need prep dual boot because eclair2dualboot already takes care of that. And if my instructions didn't work, try yellowguys, a slightly refined method.
I download the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
was the INIT.D HACK installed correctly?
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
I don't know what to do now.
thanks
you need to either toggle safe system off, or flash a ROM to use for safe system, and then flash the init.d hack
and my suggestion is to flash CM7 or Monster, Mav, SD3, Liberty, Etc. Im on CM7, works very nice http://hash-of-codes.blogspot.com
thanks MrJudylicious,
but sorry don't know how to do it...
this is my first android phone i just follow the steps that Chaoticweaponry told on the other topic:
"1: Root your Droid 3 using the 1 click root method (search around XDA/Google)
2: Download Safestrap from Hashcode's website. - USE BOOTSTRAP IF YOU'RE ON STOCK/NON-SAFESTRAP ROMS
3: Install the .apk file using AppInstaller from the Android Market.
4: Start Safestrap (or similar) and allow superuser permissions - then install recovery.
5: Get Download All Files from Android Market.
6: Download the init.d hack.
7: Turn your phone off.
8: Press m + power, scroll down to BP Tools (volume down key) and select it (volume up key)
9: Scroll down to install zip from SD card (select using power button)
10: Go to internal sd card - downloads folder.
11: Find the init.d file, and install it.
12: Reboot the device (go to main menu on safestrap (or similar) recovery)
13: Done."
I don't know what is flash a ROM...
so the init.d hack is not working?
as I said, I put system safe on and installed complete.. then it won't boot I don't know why..
so I put system safe off and it booted.
can you tell me what to do step by step please?
i'm thankful
Pedro
ps: I got one app called "droid3bootstrap" but idk if it will serve.
if you can, tell me what I need to download and what I should do...
sorry for the inconvenience
thanks
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
MrJudylicious said:
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
Click to expand...
Click to collapse
Thanks a lot MrJudylicious,
but what is this 'CM7 11-16 build'? what will it do on the phone?
I just wanted to install INIT.D HACK because I read that saves battery.
cm7 is a stripped down very functional, very fast operating system. if you want stock, you can visit his hash-of-codes.blogspot.com and under android downloads you can download the stock 5.6.890 /root + superuser ( http://goo.gl/3bTpJ ). you cannot flash to teh main system with safestrap, but you can with bootstrap. you could have issues installing more than one *strap, which is why i suggested you keep safestrap.
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
pedroramos said:
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
Click to expand...
Click to collapse
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
ChaoticWeaponry said:
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
Click to expand...
Click to collapse
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
pedroramos said:
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
Click to expand...
Click to collapse
This is why this didn't work
You install safestrap, it allows you to install roms to your /preinstall directory (directory for windows users ^^). You don't install a rom but install the init.d files to /preinstall and then try to boot off /preinstall (because safestrap is enabled). Obviously that wont work because when your phone boots it looks for system files in /preinstall but all that's there is the init.d hack.
You uninstalled safestrap, installed koush' and then installed the init.d files to /system which your phone actually runs off. At that point the init.d is correctly installed.
Another option(the one that people are telling you here) is to install safestrap, enable safestrap, install your rom to the safestrapped system and then install your init.d hack on top of the rom you just installed which is also correct.
it's 2 different ways to do the same thing slightly differently(although with the second method you basically have 2 /systems). I hope this helps clear up your confusion.
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
pedroramos said:
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
Click to expand...
Click to collapse
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
You can test that this works on your roms by flashing and then checking for a ".ItWorks" file in /data partition. If you are using ES File Explorer or similar you will need to be sure to allow it to show hidden files, otherwise you won't see this file.
Click to expand...
Click to collapse
In his development thread. This might work for you.
Willis111 said:
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
In his development thread. This might work for you.
Click to expand...
Click to collapse
I opened root explorer and there was a ".itworks"(with a medal of sheriff) on /data partition
you said that safestrap won't change my system because it install the ROM in a different partition and the boot is made by there.
doesn't bootstrap happen the same? bootstrap overwrite the original system?
a case:
I used bootstrap and suppose that I want to unflash the init.d.. how can I do it?
thanks a lot
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
pedroramos said:
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
Click to expand...
Click to collapse
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
calash said:
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
Click to expand...
Click to collapse
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
It works 4 me
pedroramos said:
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
Click to expand...
Click to collapse
Ok, so right now it sounds like you are using the basic Clockwork Mod recovery, identified by the installed Droid 3 Bootstrap from the market/downloaded. In this case you do not have a backup from before the change you applied (Side note: Backups are also called nandroid backups. They are the same, just a different term).
If you wanted to remove the init.d hack it would be a bit more difficult at this point. Not impossible but you may end up losing all your data. It depends on if the changes the init.d hack made are well documented or not. It is a fairly safe hack so I would not worry too much about it at this point.
For your reference the bootstrap you installed, also called Clockwork Mod, and SafeStrap do nearly the same thing, providing you with the menu at the very beginning when you power on the device and allows you to flash (what you did to install the init.d have), backup, and some other neat features.
The big difference is that SafeStrap allows you to have two operating systems, also called Roms, on the phone. These are identified as Safe and non-Safe. non-safe is whatever OS (or Rom, the terms mean the same on our phones) you start with while the Safe is a new install that you do in the same way as you flashed the init.d have.
As you work with it more you will get the hang of the various terms and software packages. For now you should be in good shape, even without a stock backup. We have ways to get back to a pure stock image if that needs comes up, just check the threads in the development forum for more information.
T-Mobile/Samsung have rebranded the Exhibit II 4G, giving us a new kernel, a bump to Android v2.3.6 and performance improvements (they claim) in the process. The phone we all love is now the Samsung Galaxy Exhibit 4G.
This stock ROM (UVLG3) is NOT vulnerable to USSD Dialer Attacks!
Rooting
Currently, zergrush will not root this phone's Android 2.3.6. Three known methods:
Root Stock 2.3.6 w/o a new kernel or ROM
root-stock.zip
Mirror
This zip will install Superuser, su and busybox, leaving you rooted, but otherwise no changes to your phone. ClockworkMod must be installed to flash this. So:
1. Flash ClockworkMod
2. Boot into ClockworkMod and flash root-stock.zip.
Rooted Community ROM (forkable)
t679.uvlg3.odex.01.zip
Mirror
(also see custom ROMs)
Linked above is Samsung's newest release for the Galaxy Exhibit, a stock rooted UVLG3 Gingerbread ROM. Busybox is also included. You must flash it via clockworkmod. Clockworkmod can be flashed with Samsung's stock recovery.
Custom rooted kernel
t679-root-v1.8.zip
Mirror
Kernel sources
The kernel is based on Samsung's kernel source. This kernel is rooted; if you flash it via stock recovery or cwm your ROM will be rooted with Superuser.apk, Busybox and the Galaxy Exhibit cwm-recovery installed. This kernel works with all Samsung Gingerbread releases.
Rooted ROM Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. The installation will format your data partition. I suggest Titanium Backup, available in the Market.
2. Download & copy the current t679.uv???.deodex.0x.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
3. Install Galaxy Exhibit Custom Recovery . If you're already rooted, you may install from the command line, otherwise you may install from Samsung's Recovery. Samsung's recovery only sees the internal SD, so copy the cwm zip there if you just have stock recovery. Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Select ROMwipe. This step is required!
6. Highlight install zip from sdcard, then press Home.
7. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
8. Highlight the rooted rom zip file, then press Home.
After you confirm your choice, installation should take less than three minutes.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied. Your first post-installation boot may be several minutes long.
Rooted Kernel Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. I suggest Titanium Backup, available in the Market.
2. Download & copy t679-root-v1.8.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
It's recommended to install Clockwork Mod, but you can also flash the kernel from Samsung's stock recovery. Samsung's recovery only sees the internal sd, so copy files there if you don't have cwm.
Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Highlight install zip from sdcard, then press Home.
6. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
7. Highlight the kernel zip file, then press Home.
After you confirm your choice, installation should take less than a minute.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied.
Please DO NOT PM me with support questions! They will be ignored! Post them in this thread!
Links and useful info
Galaxy Exhibit XDA Wiki
Galaxy Exhibit IRC channel
Galaxy Exhibit Themes
Custom ROMs
All ROMs listed require cwm for installation.
Peach Sunrise
RebelROM
XquiziT
CyanogenMod 9 Beta
Galaxy ExHibition
CM10 Port
AOKP (WIP)
CM7 (WIP)
CM9 Pure Nexus
Stalled, partially working
AOKP
KEMIUI
Help! I keep getting FCs!
Custom kernel for Rebel Rom
This is custom kernel 1.8 packaged specifically for RebelRom, tested on
version 3.0.8. This package includes kernel & modules only.
rrkernel.zip
Mirror 2
Stock 2.3.6 via Odin
uvlg3.odin.zip
Mirror
Adb for Windows
winadb.zip unzip and copy to your c:\Windows directory
Mirror
Flash2Stock
Flash2Stock (flash via cwm) will install stock UVLG3 and Samsung's stock recovery, un-rooting
your phone, removing ClockworkMod and returning your phone to factory condition.
uvlg3.flash2stock.zip
Mirror
SwapSD
SwapSD This simple app allows you to swap internal "usb storage" (aka /sdcard) and your removable sdcard (aka external_sd) so your larger "external sd" is mounted as "/mnt/sdcard/" and the smaller sd internal memory is mounted as "/mnt/sdcard/external_sd". This is done by changing a file called vold.fstab in your phone's /etc folder. The original device vold.fstab file is backed up to /etc/vold.fstab.backup when this app first runs. Your data on /mnt/sdcard and /mnt/sdcard/external_sd is not touched in any way whatsoever.
Dropbear (flash via cwm)
is a software package that provides a Secure Shell-compatible (ssh) server and client. It is designed as a replacement for standard OpenSSH for environments with low memory and processor resources, such as embedded systems. This archive also includes the scp and rsync utilities.
dropbear.zip
Mirror
Bloatware
These apps are safe to delete. You may also freeze them using Titanium backup.
AnalogClock.apk
Browser.apk (Only if you use an alternative browser)
Dlna.apk
DownloadProviderUI.apk
DualClock.apk
DualClock.apk
IQ-tmobile-release-signed-zipaligned-v1.1....
JobManager.apk
KiesAir.apk
MobileBackup-unsigned_v3.3.02.apk
MyFiles.apk(Only if you have an alternative File Browser i.e. Astro File Manager)
SamsungWidget_Program...
Swype.apk
TetheringManager2.apk(Only if you don't use T-Mo's tethering service)
TouchWizCalendar.apk
TouchWizCalculator.apk
TwCalendarAppWidget.apk
VideoPlayer.apk(Only if you have an alternative video player)
VoiceRecorder.apk
WiFi-Calling.apk(If you don't use it)
ZinioSettingsProvider.v2.03.3331.TMobile....
sihome-signed-tmo-android-8.apk
talkback.apk
tmobile_m4m_3_0_15.signed...
vvm-signed.apk
Partition Table
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20 all 0's
/dev/block/mmcblk0p21 all 0's
/dev/block/mmcblk0p22 all 0's
/dev/block/mmcblk0p23 all 0's
/dev/block/mmcblk0p24 all 0's
/dev/block/mmcblk0p25 all 0's
/dev/block/mmcblk0p26 all 0's
/dev/block/mmcblk0p27 efs (encrypted fs)
/dev/block/mmcblk0p28 /mnt/sdcard
Credits:VanillaTbone,s0unds,KemikalElite, jocala, Wildchild, bpear96, camcory, Intercepter and others. If your name belongs here or you have info that needs to be added please speak up!
Zergrush
Rooting the original Exhibit II via zergrush: Please read DooMLoRD's Easy Rooting Thread
Please note that this method does not work with Android 2.3.6 on the Galaxy Exhibit.
ClockworkMod
Galaxy Exhibit cwm-based recovery v6.0.1.2
6.0.1.2 has new features, including better support for both external and internal SD cards, faster backups and restores with a new backup format that de-duplicates data in between backups. Exclusive features for Galaxy Exhibit include:
wipe menu with rom wipe
All system wipes under one menu: rom (system/cache/data),cache,dalvik,cache/dalvik,data.
Stack zip files for installation:
Flash cm9 & gapps, etc. Select as many zip files for installation as you choose. Flash them all with one command.
Install system images:
Drop any recognized system image into a folder on your phone and recovery can flash it. You can even drop the entire contents of an odin tar/md5 file in a folder and cwm recovery will flash it all automatically.
All images must conform to Odin naming standards:
adsp.mbn
amss.mbn
boot.img
cache.img.ext4
preload.img.ext4
recovery.img
system.img.ext4
Click to expand...
Click to collapse
This is regular interface, not touch.
cwm.6012.t679.zip
Mirror
To initially install Galaxy Exhibit Custom Recovery you need to:
1. Copy cwm.galaxy.exhibit.zip to your internal SD storage.
2. Boot into stock recovery:
Starting recovery: Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons.
Or a different method some find easier:
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Recovery should start after the Galaxy Exhibit/T-Mobile logo.
3. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm.galaxy.exhibit.zip file.
If you already have cwm installed, to update follow the steps above, booting into your current cwm instead of stock recovery.
Should you need to install ClockworkMod via Odin:
cwm.6012.tar
Mirror
We have needed a new thread for our phone, thanks for making this!
kingdavidd said:
We have needed a new thread for our phone, thanks for making this!
Click to expand...
Click to collapse
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links and information.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any general discussion of our Galaxy Exhibits (concerning development as well). I also hope folks will evangelize and point people here rather than carry on in the older abandoned OP threads.
Nice job jocala! Thanks.
Sent from my Calculator with Android.
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct? Much rather flash that then go back to stock then update. Thank you for that.
Sent from my SGH-T679 using xda premium
jocala said:
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any discussion of our Galaxy Exhibits.
Click to expand...
Click to collapse
Yea all the old threads OP's abandoned them and the original post had all old info, I am glad you're dedicated to this phone!
SurgeRush said:
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct?
Click to expand...
Click to collapse
Yep, that's it. Purely stock except for root, busybox & recovery.
Cant wait to see what roms come out of this
Sent from my SGH-T679 using XDA
The rebranding works out nicely, if for no other reason than providing a point of demarcation.
Many props to Jocala who is awesome, as we all know. It can't be said too often but we'll try not to overdo it. :thumbup:
Sent via frazzled carrier pigeon -->
Ditto here man. We'd all be screwed & tattooed without his know-how. BTW worth mentioning I had to refreeze all the bloatware again after the update. Noticed how the phone lagged and then checked Titanium Backup. Sure enough all the crap was back. Also re-check settings in programs like Juice Defender and Rom Toolbox. I had to re-enter some of them again as well.
Has anyone managed to update successfully while already being rooted? (Specifically by Zerg Rush method)
I've yet to received the OTA notification and still holding off If i should update using the software. Stock ROM but just rooted. Holding off on "flashing" anything as I've never done it before.
ArtfulDodger said:
Ditto here man. We'd all be screwed & tattooed without his know-how.
Click to expand...
Click to collapse
That's not true at all, but thanks for saying it. Anyone handy with *nix can do what I do, and 95% (or more) of the techniques I use were pioneered by others here on xda.
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder(not in stock) T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though. It also looks like you might have taken a different approach to rooting the rom, maybe you could look at mine see if its just complete fail or not lol and or maybe pming me, to avoid clutter, on how you did urs.
ive made sooo many edits lol but just wanted to add too, thanx for all the work you have done for us.
cars1189 said:
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though.
Click to expand...
Click to collapse
The phones I use have always come odexed. I know of no other root methods. I don't have time to beta your rom, but feel free to post a link. I'm sure you'll have volunteers
cool, and no problem, and basically all i did was use the dsixd kitchen and added root(from in the kitchen menu), does that not really root it? does that just change the file permissions? cause when i did that it added the su binary so i assumed it did, but doesn't look like thats what you did, urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
cars1189 said:
urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
Click to expand...
Click to collapse
You are correct
Flashed the ROM, all went smooth, but I can't install anything from the Market. Every time I try I get "ERROR "Blah" Could not be downloaded due to an error." Any ideas? Did a full romwipe and dalvik before flashing. The markets not even updating to Play store either.