Please note, this is NOT my own work. It's on the CM Wiki, but since so many people seem to not want to be bothered to read the damn wikis for their intended purpose, I'm going to be a ratbastard enabler and post the steps HERE in a thread, so next time someone goes to post to ask how, IF they use the search function they'll find THIS thread and not threadnaught this forum with questions about how to do it.
This has been tested and works 100%. I have not tried it for CM6, and I don't suggest anyone try it on a 911 patched Rogers Dream until CM6 is stable AND there's a proper kernel image for Dream/Magic 32A/32B. As usual, I hold no responsibility if this bricks your Dream. I have made ROMs for the Raphael, Rhodium, Topaz, and Kaiser, and am an expert on those devices but this is my first actual Android device that I've had for less than a week, and just rooted/flashed it today, so I am NOT an Android expert AT ALL.
Original Guide: Here!
(Note: This guide is for CM5)
Step 1) Download all of the required software. SDK, Fastboot, Exploid from DroidXRoot, SPL 1.33.2005, Amon_Ra Recovery for CM, CM5 Itself, Googleapps, and extra kernel for Rogers Dream.
Step 2) Install extract the SDK archive and rename it to 'sdk' for easier use. In Windows, extract to C:\sdk, linux ~/home/sdk, mac .. wherever you want. Extract the Fastboot.zip to the sdk/tools folder. Move exploid, SPL, and Recovery to sdk/tools for easier use with adb.
Step 3) On your Dream, go to Settings->Applications->Development and enable USB Debugging, and connect your Dream to your computer via USB cable.
Step 4) Enter your sdk/tools directory and type the following:
Code:
* adb push spl-signed.zip /sdcard/1_33_2005_spl.zip
* adb push update-cm5* /sdcard/update-cm5*
* adb push gapps-ds-ERE36B-signed.zip /sdcard/gapps-ds-ERE36B-signed.zip
* adb push bc-5.0.x-ebi1-signed.zip /sdcard/bc-5.0.x-ebi1-signed.zip
* adb push recovery-RA-dream-v1.7.0R-cyan.img /data/local
* adb push exploid /sqlite_stmt_journals
* adb shell chmod 777 /sqlite_stmt_journals/exploid
(*whatever your CM image is.)
Step 5) Running Exploid!
Code:
adb shell /sqlite_stmt_journals/exploid
should produce the following:
Code:
$ adb shell /sqlite_stmt_journals/exploid
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by birdman for the DroidX
[+] Using basedir=/sqlite_stmt_journals, path=/sqlite_stmt_journals/exploid
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
Now unplug/replug USB cable to apply exploit. ROOOOOTED!
Step 6) Custom Recovery time!
Type the following:
Code:
adb shell
this will take you to a $ prompt (that's the shell.)
Code:
rootshell
this will ask for a password, which is 'secretlol' without quotes.
Now that you're at a root shell, type
Code:
chmod 666 /dev/mtd/mtd1
exit
Now you're back at the regular shell prompt, type:
Code:
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
If this gives a "mtd: read error at 0x00000000 (Out of memory)" error, it's okay, just type it again and it should work without the error. This is normal, do not panic.
Once this is complete, type
Code:
exit
and power down the phone. (long hold end key)
Step 7) SPL
Hold Home and press the End key to power up the Dream. At the recovery menu select
Code:
Flash Zip from SDCARD
and select the
Code:
1_33_2005_spl.zip
.
Now reboot by holding home+back. It will take you back to the recovery shell, and this is okay. This is actually what we want. Now, type
Code:
adb shell reboot bootloader
and watch the screen to verify that you see:
Code:
HBOOT: 1.33.2005
RADIO: 3.22.26.17
Now, run the following Fastboot commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot oem powerdown
Step 8) Flashing CM!
Press home+end to power up the phone in recovery mode, and select
Code:
Flash Zip from SDCARD
, Select your CM image, then
Code:
Flash Zip from SDCARD
and select gapps-ds-ERE36B-signed.zip, and finally
Code:
Flash Zip from SDCARD
and select bc-5.0.x-ebi1-signed.zip.
Once that is complete, home+back to reboot, and you're done. That's it. First CM boot may take 5-15 mins.
Reserved for updates
Click to expand...
Click to collapse
Time for the update!
CyanogenMod6rc3
EBI1 Kernel for CM6rc3
Google Apps, Mdpi Tiny for CM6
Use these the same way you would in the above steps for flashing CM5, obviously replacing the zip files from CM5 with the ones from CM6 during the adb push, and the flashing from zip in recovery console. This should work exactly the same as the above version, but the end result is that you'll have FroYo instead of Eclair.
I waited until RC3 for this update because, in my opinion, RC2 was a bit laggy and overall wasn't as stable.
Also note: This process will work for roms OTHER than CyanogenMod so long as they're either based on CM or have an EBI1 Kernel available. Make sure you use the correct EBI1 Kernel by checking what gapps version the Rom uses if it's CM-based but doesn't link to an EBI1 Kernel. For example, if it's gapps-mdpi-FRF91-3 then it's the CM6rc2 EBI1 Kernel you need.
Any questions? Post 'em here.
Thanks for posting this. I know some people got confused.
I highly recommend people also look at the pre existing thread: http://forum.xda-developers.com/showthread.php?p=7306638#post7306638 if they have questions as that is where the q/a is at.
ezterry said:
I highly recommend people also look at the pre existing thread: http://forum.xda-developers.com/showthread.php?p=7306638#post7306638 if they have questions as that is where the q/a is at.
Click to expand...
Click to collapse
The difference is your thread is a vague shortened process that assumes people are going to follow all the links in your post and read through pages of comments to figure out the exact steps of your "simplified process", where my thread gives them a one-stop-shop from stock to a stable rom. You've linked to your thread, so now people who don't mind looking around then posting tons of questions have their place to go.
Tl;dr version: this thread is for the people who can barely be bothered to use the search function and want everything in one place, your thread is for "everyone else".
Sent from my HTC Dream using XDA App
agentfusion said:
The difference is your thread is a vague shortened process that assumes people are going to follow all the links in your post and read through pages of comments to figure out the exact steps of your "simplified process", where my thread gives them a one-stop-shop from stock to a stable rom. You've linked to your thread, so now people who don't mind looking around then posting tons of questions have their place to go.
Tl;dr version: this thread is for the people who can barely be bothered to use the search function and want everything in one place, your thread is for "everyone else".
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
Don't worry I'm following this thread so *I* don't inadvertently support people who don't follow links.
It just sucks that people really are that lazy. Seriously. They waste more time typing a question that has been answered 20 times than it would take to search for the proper answer.
So yeah, thanks for posting a topic that has a lot of great information for those of us who aren't lazy, I do personally like yours and think it should be in the informative links sticky. I just wish I had found yours first while I was searching for my answers because it really is informative for those of us not afraid to read and not have things spoonfed to them.
Sent from my HTC Dream [CM5] with xda app.
Thanks for the How-To. It was very easy to follow.
AverageCanadian said:
Thanks for the How-To. It was very easy to follow.
Click to expand...
Click to collapse
No problem! Glad you found it useful. All of those steps now work for CM6, so I will be adding links for CM6rc3 later tonight
Sent from my HTC Dream using XDA App on CM6rc3
update bump.
Tks for the guide. Total newbie here and trying to root my HTC Dream.
Up to now, i fallowed WIKI loll to the letter, tho, when i try to download the EXPLOID, either from your link or the WIKI one, it pup's out as a TROJAN program Exploit.Linux.Lotoor.e !
Is it safe to get it or i shouldn't go there???
I'm stuck to this step now and not sure what to do
Tks for the info..
Wood's said:
Tks for the guide. Total newbie here and trying to root my HTC Dream.
Up to now, i fallowed WIKI loll to the letter, tho, when i try to download the EXPLOID, either from your link or the WIKI one, it pup's out as a TROJAN program Exploit.Linux.Lotoor.e !
Is it safe to get it or i shouldn't go there???
I'm stuck to this step now and not sure what to do
Tks for the info..
Click to expand...
Click to collapse
To the best of my knowledge, it comes up as a trojan because it's a rootkit for Android, which is based on Linux... so virus scanners will consider Exploid as a "virus/trojan" because using a rootkit on a linux machine is basically using a trojan to get root access, which is what you're doing to your phone.. you're using an exploit to get root access.
I have Alcatel OT 995 with Android Gingerbread 2.3.6 and use Ubuntu. I tried Superoneclick (but it works with 2.3.5 :/ ), Casual (doesn't work), Superuser.apk.. all without effects. Anyone has any suggestions?
Hi I did it the following way (Alcatel OT 995):
Get the android sdk, run path_to_sdk/tools/android sdk and install the platform-tools (you need adb and fastboot, they then are placed into path_to_sdk/platform-tools )
Get the cwm recovery for the device from hxxp://dump.pargon.nl/alcatel/cwm-recovery/
Get the su binary (arm) from superuser.apk: hxxp://androidsu.com/superuser/
Follow hxxp://dump.pargon.nl/alcatel/cwm-recovery/README for how to boot into cwm recovery
Inside recovery go to the mount menu and mount /system (and it is a good idea to use the backup menu item before doing this all )
Unpack the su binary somewhere and do adb push path_to_your_su/su /system/bin/su
Use adb shell chmod 4755 /system/bin/su to give it proper rights.
Boot back into the android system, run Superuser.apk, it will, of course, tell you if it worked.
Maybe you should include the device Name into the Thread title because rooting is a somewhat device specific issue.
Oh it seems someone here decided to be unfriendly to new users so hxxp==http...
Try memprodroid
tamtamtam23 said:
I have Alcatel OT 995 with Android Gingerbread 2.3.6 and use Ubuntu. I tried Superoneclick (but it works with 2.3.5 :/ ), Casual (doesn't work), Superuser.apk.. all without effects. Anyone has any suggestions?
Click to expand...
Click to collapse
If you only want root, otherwise want to stick to a stock system, the most conservative method (rooting, no tampering with any other ROM partitions) is mempodroid. It only works within a specific range of linux kernels (it relies on a bug that got introduced into linux kernel but was fairly rapidly stomped on), but I think 2.3.6 kernel is probably one of them. See http://forum.xda-developers.com/showthread.php?t=1461736 for details. If it doesn't work (you don't have the right kernel), you haven't broken anything, you just won't have root.
I own an irulu K1001L1 10.1 (build number A20_K1001_K1001L1.20130713), a cheap one.
Many people complain about "partial rooting" and being unable to remount system in rw mode. Clueless as I was, I had tried several times with Uberizer, z4root and SRSroot, to no avail (the problem is not in the root, in my tablet su came by default in xbin directory).
D_rex (http://forum.xda-developers.com/showthread.php?t=2606510&page=2) found an effective solution which also helped in my situation: I think my tablet came with "su" application by default (notice overclocking worked) but due to /dev/block/nandd ext4 partition (I think /system starts at some offset) containing some errors (seen in dmesg) and due to this partition having the "s_errors" flag (behavior when errors detected) set to "mount read-only (02)", the partition is ALWAYS mounted read only, and remount as root doesn't change anything. More info on this ext4 option can be found here
For me, the solution that worked was changing that flag s_errors to continue (01). I wasn't able to run e2fsck as the partition is already mounted; and I wasn't able to do a fsck in recovery mode since the recovery mode of this tablet lacks seems to lack both shell and e2fsck.
Tune2fs (old version precompiled here) can change that flag in the partition. Using adb shell I pushed it to de device, set attribute as executable and run it, successfuly changing that "behavior when errors detected" in both partitions.
It has been suggested filesystem errors are linked to stability and realiability problems. Unfortunately this tablet lacks a version of CWM o TWRP as a recovery custom rom. I also adjusted the "max-mount-counts" value via tune2fs -c hoping it forces Android to run e2fsck, but it seems dmesg keeps displaying errors. I can only hope this problem is given more attention by developers.
After this I used the usual tools to root the device, noticing I had spent many hours in this cheap tablet.
On a side note, the adb driver setup tool found here didnt work for me (it seems &USER_PROFILE% in the .bat file should be replaced by "%USER_PROFILE%" and Desktop should be replaced according to the language of your operating system. Nevertheless the tool didn't work for me and I had to install another driver found in Uberizer distribution as the official "android_winusb.inf" didn't work in my Windows XP computer.
Thanks to the creators of tune2fs, to D_rex and other people/programs mentioned here. This is my experience with this problem; I'm not responsible if anyone tries this and bricks his device. All brands are property of their owners.
edition: should also mention by default now my tablet mounts in read-only mode (which is of course safer) but lets me change to rw whenever I want
Hi there,
Sorry but this forum is not for guide and tutorials.
The mission of XDA Assist is to provide basic help to those who have tried searching but can't find what they are looking for and need assistance. This is not a "helpdesk" providing technical assistance but more to point you in the correct direction with your problem. Perhaps you can't find posts on how to root your phone, install custom recovery or maybe you have questions about how to navigate and use features on the site.
Click to expand...
Click to collapse
You can post your thread, in this forum:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck
Thread closed
adb devices
list of device attached
8AC7QGZ7GA
adh shell
[email protected]:/ $
adb devices
list of device attached
[ No device detected at shell !]
So my device not detecting when I put it into rootshell , same from Terminal Emulator
I tried 'adb remount' but still !
What should I do ?
XDA Visitor said:
adb devices
list of device attached
8AC7QGZ7GA
adh shell
[email protected]:/ $
adb devices
list of device attached
[ No device detected at shell !]
So my device not detecting when I put it into rootshell , same from Terminal Emulator
I tried 'adb remount' but still !
What should I do ?
Click to expand...
Click to collapse
I found this about ADB:
Beginner’s Guide to the Android Debug Bridge
[GUIDE] ADB Workshop and Guide for everyone
[GUIDE] ADB For Beginners (Setup, Use, and More!)
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.2
[TOOL]Minimal ADB and Fastboot [11-6-14]
Maybe one of those can help already.
If not, search for your device in "Type to find device..." at the top of xda site (on browser) and post your question in the device's Q&A forum.
Good luck !
Good , there my problem are missing . You tell me how can I fix permission denied problem ?
sabithpkcmnr said:
Good , there my problem are missing . You tell me how can I fix permission denied problem ?
Click to expand...
Click to collapse
I'm still not sure what exactly your issue is.
And I don't know your device.
Hard to help. ..
Maybe this can help : [Q] Permission denied to push vending.apk.
Permission denied can also occur when access right is not sufficient (root issue of missing "su" command before the push) or the file's permissions are not set correctly.
My tapatalk signature:
Device: SGS5 (SM-G900F)
ROM: AllianceROM v5.6
Kernel: Stock G900FXXU1ANG2
Recovery: TWRP by Ktoonsez
Modem: G900FXU1ANG7
If you have any question about or any issue with your SGS2, just ask in the New members friendly Q&A thread.
... for the SGS5, just ask in the Noob friendly S5 All in one support thread
If you need general help/assistence, please go to XDA-Assist.
Thread closed. Thank you.
Is there a way to get any information about partitions while a phone is in Download mode?
For example, can I see partition sizes? Can I copy/download images? Generate a hash?
This post shows four useful techniques, but all require ADB (not available to me)
https://android.stackexchange.com/questions/5232/how-can-i-view-the-android-internal-partition-table
df, cat /proc/mounts, cat /proc/partitions, ls -al /dev/block/platform/msm_sdcc.1/by-name
My Galazy A3 (2016) is currently exhibiting a "Custom binary blocked by FRP lock" bootloop, and I am studying how to fix it without any data loss. I've read that I need to flash the stock boot.img and recovery.img
Seems that general techniques regarding partition information should apply to most (all?) current Samsung phones.
I'm curious if I can find any information about what is currently on my phone, before flashing.
ScottHW said:
Is there a way to get any information about partitions while a phone is in Download mode?...
Click to expand...
Click to collapse
I don't have this device but, the following is the dedicated area of the forum for your device.
https://forum.xda-developers.com/samsung-a-series
With that stated...
The following threads may have some information similar to your issue and a possible solution or you can post your issue for some member guidance.
https://forum.xda-developers.com/showthread.php?t=3694816
https://forum.xda-developers.com/showthread.php?t=3619425
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE