yashsingh1/xdaforums huggingface dataset:
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
thanks for your swift reply. that is the wiki i followed, but when i tried to install DangerSPL, i cannot go into recovery by holding HOME while power on the phone. it hangs at Rogers screen.

i checked radio and it is correct version. should i flash radio still?

any suggestion?

thanks,
[G1 Q&A, Help & Troubleshooting] ezterry:
Well you certainly need recovery..

The original steps for that process are here: http://xdaforums.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams

(as cm wiki sometimes is organized more for maintenance by people who don't use a rogers dream than being user friendly.. and they removed the link to the xda thread with all the q&a on the process)

the error however is either you are flashing the wrong recovery; or the flash of the recovery failed. make sure your flashing one of the '-R' ra-recoverys.

best to take it from the top.. if recovery still fails some people have found re-flashing the e911 rom and trying again helped (see 'Returning to Stock Rogers' on the xda wiki page)
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
still i cannot go into recovery.

can you tell me how long i have to hold HOME key in order to boot into recovery?

i push HOME and POWER together, and then i can only see ROGERS. it probably stays there forever.

one thing i cannot follow wiki before is LONG HOLD POWER TO TURN OFF PHONE.

thanks,
[G1 Q&A, Help & Troubleshooting] ezterry:
If you can boot normally but not recovery (ie you are stuck on the rogers logo and it never changes when you boot holding down home) their is a problem with the recovery you flashed. (We will not move on from this statement unless we find why there is an issue with the recovery or that the incorrect recovery was flashed)

As for long press power or end on the phone that is how you get the shutdown menu in the rogers and other roms.. so I'm not sure what is wrong if that is failing outside user error.

I need you to do the following if you want help:

1) flash (as per the restore stock rogers rom on the xda wiki) the e911 patched rogers nbh file

2) making sure you document every command you run and saving the console output to a text file run the e911 rooting process as per xda wiki

3) if you can't boot recovery post said output here.. however first check it with the sample output
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
thanks for your patience.

when i say long press power button cannot power off the phone, i mean i cannot turn off the phone by only press it, i have to go through two more windows, one is power down options and another is confirmation.

i will follow the instructions again to see what happen. do you suggest any recovery image? or something else i can do ?

thanks
[G1 Q&A, Help & Troubleshooting] Sleeepy2:
wait what. power down options?

I don't remember power down options on the stock rom
[G1 Q&A, Help & Troubleshooting] ezterry:
Certainly had power off and airplane mode.. probably reboot as well but I forget.

The recovery image with the md5 sum in the instructions is what most people use.
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
after i run exploid, i can see three files: hotplug, loading, and sim_lock_status were generated, as well rootshell in /system/bin.

i tried to go into recovery, but i cannot, because it hangs on ROGERS screen forever. i have to pull battery out to reboot. then i checked /sqlite_stmt_journals, exploid, loading, hotplug and sim_lock_status were all gone. there were two files there: screen_lock_status and pattern_lock_status.

i don't have sim card in the phone, can it cause the problem?

BTW: i even followed "how to root Droid" to install exploid, using chmod 755 and turn on/off wifi after running exploid.

any suggestion? thanks,
[G1 Q&A, Help & Troubleshooting] ezterry:
Please don't follow the droidx instructions, and follow the Rogers root instructions.. the root exploit is the same but the hardware and goal is different.

many others hard successfully rooted and some q/a on the process is in this thread: http://xdaforums.com/showthread.php?p=7306638#post7306638

You have not given the console output to your attempt so as I said earlier I have no additional recommendations than what I have already provided as we do not know what recovery you flashed.
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
i am very new to this thing. does "console out" mean the screen captures? i will supply tomorrow.

i had tried different recovery image, the results are same. could you send me a known working image for rogers dream?

honestyguy@live.com

thanks
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
please kindly have a look. thanks.

the output shows in the following:

D:\MyDocs\JD\android\adb_1.0.26>adb push spl-signed.zip /sdcard/1_33_2005_spl.zi

p

452 KB/s (0 bytes in 188246.000s)

D:\MyDocs\JD\android\adb_1.0.26>adb push recovery-RA-dream-v1.7.0R-cyan.img /dat

a/local

1159 KB/s (0 bytes in 4712448.003s)

D:\MyDocs\JD\android\adb_1.0.26>adb push exploid /sqlite_stmt_journals

372 KB/s (0 bytes in 11917.000s)

D:\MyDocs\JD\android\adb_1.0.26>adb shell chmod 777 /sqlite_stmt_journals/exploi

d

D:\MyDocs\JD\android\adb_1.0.26>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.

D:\MyDocs\JD\android\adb_1.0.26>adb shell

$ rootshell

rootshell

Password (echoed):secretlol

secretlol

# chmod 666 /dev/mtd/mtd1

chmod 666 /dev/mtd/mtd1

# exit

exit

$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img

flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img

mtd: write error at 0x00120000 (I/O error)

mtd: verification error at 0x00120000 (I/O error)

mtd: write error at 0x00120000 (I/O error)

mtd: verification error at 0x00120000 (I/O error)

mtd: skipping write block at 0x00120000

$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img

flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img

$ exit

exit

D:\MyDocs\JD\android\adb_1.0.26>
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
this is files under /dev/mtd:
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
does it have something to do with the "skipping writing"?

$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img

flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img

mtd: write error at 0x00120000 (I/O error)

mtd: verification error at 0x00120000 (I/O error)

mtd: write error at 0x00120000 (I/O error)

mtd: verification error at 0x00120000 (I/O error)

mtd: skipping write block at 0x00120000

$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img

flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
[G1 Q&A, Help & Troubleshooting] ezterry:
See now we know the error .. well that there was an error anyway.

I'm used to a memory error not the io error. Usually when flash_image fails it skips the block and writes the data in the next block.. if all is well the block is flagged bad and the spl booting the recovery does the same.. seems not all is well in your case.

Before going too crazy. . Lets see if we can make it work.

1) restore the rogers nbh

2) try to boot recovery (hopefully) you will enter stock recovery with the /!\ image.. alt+L will show a short list of options, you may reboot to the rogers rom.. if it fails to boot make a note to inform me in your next reply and reboot into the rogers Tom

3) try the root process again with the 1.6.2R recovery

3b) if it works you can use fastboot to flash 1.7.0 after installing the 1.33.2005 spl.. I think 1.7.0 will work then..

Report back if it works great. . If not things are a bit more complex. . Particular if the stock recovery also fails.
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
when you said "rogers nbh", do you mean Bootscreen.nbh?

can i use this: http://xdaforums.com/showthread.php?t=341753

sorry, i am new to this.

really appreciate
[G1 Q&A, Help & Troubleshooting] ezterry:
No I mean this: http://xdaforums.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams#Returning_to_Stock_Rogers
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
i restore rogers nbh. and i can go into recovery mode. after press alt-L, it shows:

android system recovery utility

there are three options:

reboot system now

apply sdcard:update.zip

wipe date/factory reset

but on the bottom there is warning:

E:Can't open /cache/recovery/command

what i supposed to do next?

thanks,
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
i tried to go through the instruction. but rootshell won't be generated after run exploid. i can see exploid had run, but in /system/bin there is no rootshell.

i tried

rootshell generated. but still i have this:

$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img

flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img

mtd: erase failure at 0x00120000 (I/O error)

mtd: erase failure at 0x00120000 (I/O error)

mtd: skipping write block at 0x00120000

it seemed there is something preventing writing to that block.

thanks
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
i tried 1.6.2, still:

$ flash_image recovery /data/local/recovery-RA-dream-v1.6.2R.img

flash_image recovery /data/local/recovery-RA-dream-v1.6.2R.img

mtd: erase failure at 0x00120000 (I/O error)

mtd: write error at 0x00120000 (I/O error)

mtd: verification error at 0x00120000 (I/O error)

mtd: skipping write block at 0x00120000

$ flash_image recovery /data/local/recovery-RA-dream-v1.6.2R.img

flash_image recovery /data/local/recovery-RA-dream-v1.6.2R.img

$
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
i used this command to save a recovery image to sd card.

# cat /dev/mtd/mtd1 > /sdcard/mtd1.img

and the flash it back. i had same error

and when i tried to boot into recovery, it too hangs at Rogers screen, but when i plug usb to it, it shows FASTBOOT USB in the top-left corner. and i can use fastboot to talk to it. if i flash recovery-RA-dream-v1.7.0R-cyan.img into phone, i cannot see it with fastboot.

summary:

1 in order to generate rootshell, i have to do

2 it always show:

i did this

and i saw 0X00120000 is in recovery. i don't know it is a physical damage or software prevention.

any idea or suggestions?
[G1 Q&A, Help & Troubleshooting] ezterry:
Likely physical.. but that just means a bad block (they are common actually .. it's not quite an explanation why recovery wont boot)

Ok.. we are going to try a smaller recovery since stock recovery works.

1) Download attached asop_R.zip

2) extract (stock_test_recovery-R.img) MD5: a9489e528c9590288888d75aa5ba0bfb

3) Run sections A, B, and C as per the wiki replacing 'recovery-RA-dream-v1.7.0R-cyan.img' with 'stock_test_recovery-R.img'

(in case the wiki changes .. this is the process up to and including flashing the rom and powering down the phone)

4) boot into recovery (but booting while holding [HOME]) you will see a screen with a /!\

5) press Alt+L for the options to appear

6) select 'apply sdcard:update.zip [Alt+S]' (this will actually apply 1_33_2005_spl.zip)

.. Note if you see a SD card read error (and only if its that error please) at the bottom of the screen select the option again..

7) reboot; you will see some flashing screen then the rogers rom will return

8) power off the rogers rom and boot while holding [CAMERA]

10) verify you have HBOOT-1.33.2005

11) press 'send' or 'back' as prompted on screen to enter fastboot mode

12) run the following fastboot commands (assumes you have recovery-RA-dream-v1.7.0R-cyan.img downloaded)

fastboot erase recovery
fastboot flash recovery recovery-RA-dream-v1.7.0R-cyan.img

13) press [MENU] once the flashes are complete to power down

14) press power and [HOME] to boot into recovery.. if it works you will at last see v1.7.0R

pick up the process at: D 'run the adb command adb shell reboot bootloader'
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
thanks, but i still got the error, same error.
[G1 Q&A, Help & Troubleshooting] ezterry:
Your phone seems to really like being stuck on the rogers rom...

Ok I have other ways of getting what you need but they require stepping over a safety fence and thus removing some of the safety net preventing you from bricking your phone. So please be very careful with the following procedure unless you really do want to brick your phone.

1) you need to restore the e911 patched rogers rom by flashing the rogers nbh again.

2) boot the phone into recovery, if the nbh was cleanly installed recovery will boot and show the /!\ symbol this is important if recovery can't boot on its own you have a very high chance of bricking your phone if you continue on

3) reboot back into the rogers rom and push files onto the phone:

adb push spl-signed.zip /sdcard/1_33_2005_spl.zip
adb push stock_test_recovery-R.img /data/local/
adb push exploid /sqlite_stmt_journals adb shell chmod 777 /sqlite_stmt_journals/exploid

4) regain root

adb shell /sqlite_stmt_journals/exploid

5) after exploid exits unplug/replug the usb wire so it creates rootshell

6) run 'adb shell', the 'rootshell' and type the password (setretlol) when prompted

7) (here is where it changes), run the following on the root shell:

flash_image boot stock_test_recovery-R.img

(If you get the memory errors try again, otherwise if you flash any other partition besides boot re-flash the nbh now)

8) reboot the phone.. if the flash worked you will be in my test keys asop recovery

9) select alt+l to see the options and select apply update.zip to flash 1.33.2005

10) once flashed reboot

11) one or more reboots will happen do not interrupt (you may press and hold send after the rogers screen returns it may help enter fastboot mode)

12) once done if you are not in fastboot mode power down and boot holding camera, then press send/back as prompted to enter fastboot

13) hopefully now you see hboot-1.33.2005

14) run the following fastboot commands

fastboot erase system -w
fastboot erase recovery
fastboot erase boot
fastboot flash recovery recovery-RA-dream-v1.7.0R-cyan.img

15) boot recovery.. if it boots install an ebi1 rom as per normal install instructions..

As I said this process is a bit less safe so read it carefully
[G1 Q&A, Help & Troubleshooting] JaydenCanada:
thanks to ezterry

i followed your last instructions and it works now. finally i got the freedom.

one more question: can i unlock it now after the installation of CM6?

i really appreciate your patience and help.
[G1 Q&A, Help & Troubleshooting] ezterry:
Good to hear, take note that you may always need to flash/modify recovery via fastboot. If you ever flash/modify recovery from the rom/recovery don't run 'reboot recovery' rather reboot normally and hold the home button. (This way if recovery is bad you will still be able to enter fastboot and not be a brick)

Sim unlock? Yes if you have the unlock code (well assuming no bug was introduced both cm4.2 and cm5 worked),

Just put in a sim card from another provider and boot it will ask for the code.. enter it if you have it and if the phone accepts it you will be unlocked for the rest of the phones life regardless of rom/radio currently flashed.
[Hero, G2 Touch Q&A, Help & Troubleshooting] surronix:
Anyone getting really bad battery life? Last night my battery was at 90% and when I woke it it was around 50%. I know I had wifi and a mail app on but isnt that kind of extreme? when I was walking to school I also listened to music how around 25mins, then used task killer. By the time 3 oclock rolled around my phone was dead.

My phones is only 2 weeks old could this be a battery defect or software issues? (Ive frequently use advanced task killer)

I'm on rcmix 2.1 btw
[Hero, G2 Touch Q&A, Help & Troubleshooting] ddotpatel:
Do you put your phone on and off charge a lot without letting it get to 100%?

I was charging my phone almost every day but am now getting min 48 hours.

It is long winded, and shouldn't need doing regularly as long as you start letting it charge to MAX capacity from now on.

1. Plug phone in. Through mains, not USB to PC/laptop. Let phone charge to full. Not just when the green light goes on,.. it should say charged (it does on FroydVillain anyway).

2. Turn phone off. Now red light will show again, could be for a few seconds, could be 1 - 2 minutes. Wait till Green light shows again.

3. Pull charger out. Restart phone. Let it fully start up.

4. Turn it off again.

5. Plug in charger, wait till green light shows again.

Finally finished. Restart phone, and remember to fully charge all the time. And try not to let it go flat, not good apparently.
[EVO 4G Android Development] myn:
Rooted and DeOdexed :)

This is the Vanilla/Stock 3.29.651.5 Sprint Sense ROM with the only addition being Superuser/su, BusyBox and DeOdexing.

ROM

myn-OTA_Supersonic_3.29.651.5-DEODEXED.zip

*Mirror 1*

*Mirror 2*

*Mirror 3*

*Mirror 4*

*Mirror 5*

*Mirror 6*
[EVO 4G Android Development] bighov:
wow

that was fast...thanks
[EVO 4G Android Development] Shyfe:
holy crap!
[EVO 4G Android Development] ZEDEK:
Thanks so much!!!!
[EVO 4G Android Development] Sporkman:
win Sir WIN !!!
[EVO 4G Android Development] tbistone:
holy crap h4x!! :eek:
[EVO 4G Android Development] cj10488:
Thanks for the quick update.. Any mirrors 65k at 165mb is a bit slow

James
[EVO 4G Android Development] Envynet:
Anybody have an ODEXED build??
[EVO 4G Android Development] SITH16:
Nice! Thx!
[EVO 4G Android Development] Sporkman:
beggars cant be choosers
[EVO 4G Android Development] tauzins:
ill have mirrors up soon !!!!
[EVO 4G Android Development] cj10488:
Am i begging? nope... Just asking.

James
[EVO 4G Android Development] m03sizlak:
post an odexed version please.
[EVO 4G Android Development] Sporkman:
same thing imho

im uploading to my dropbox
[EVO 4G Android Development] jkinnison90:
Downloading xD
[EVO 4G Android Development] nico4k:
swweeeeettt!
[EVO 4G Android Development] jkinnison90:
Were there any new radios?
[EVO 4G Android Development] jahnile:
Got to love our great dev, next is to integrate it in our daily/favorite Rom, Thanks.
[EVO 4G Android Development] b0ricua:
Nice work!

Downloading at 720 kB/s, Thanks!!!
[EVO 4G Android Development] martijua:
Thanks !!!!
[EVO 4G Android Development] chino331:
He wants the odexed version of the ROM. Just like me and others that have requested this... and you have ignored every request for the odexed version. It would be nice for you to release the odex/non modified version of the ROM for those that want it.
[EVO 4G Android Development] tatnai:
yeah, you just overwrote everything "new" with your old nandroid. wait, if you pulled just your data from the nandroid, I suppose that might work; haven't tried that myself.
[EVO 4G Android Development] Rydah:
+1

It's cool he released a version but come on, deodexd before odexed? At least release a rooted odexed version or share the untouched version. I'm kinda even feeling sketchy about this deodexed version.
[EVO 4G Android Development] myn:
LTNS. Glad you're here too :).
[EVO 4G Android Development] i-l-l:
This. I like themes and all but I rather all my apps auto update instead of hunting down the files.
[EVO 4G Android Development] notasimpleway:
Anyone have a flashable version of just the OTA as to not have to load a whole new ROM? Maybe just the kernel...
[EVO 4G Android Development] tatnai:
why don't you guys go clog this thread too? you've asked, myn does not seem interested; flash a stock rom and then pull the OTA for yourself. or if you can't, see if you can google a source. or if you can't, wait.

let it rest. someone interested enough will do the (small) work to get and share it. asking more times in this thread doesn't look like it is getting anywhere.
[EVO 4G Android Development] phelixian:
yeah i didn't. i did an advanced restore from nandroid of my previous backup which was also a stock rooted version.(revoked) all the versions are up to date and everything seems great. angry birds is def smoother and fps2d shows me cooking. I'm happy. Thanks a bunch Myn.

So don't know that I'd recommend what I did to everyone in this thread asking about maintaining your settings, but as long as you backup it is worth trying.
[EVO 4G Android Development] chino331:
there are quite a few people asking for it - obviously there is demand for it... there should have been enough decency to at least respond to one of the posts for it.

anyways all i asked is once. searching the net to find what i want. thanks.
[EVO 4G Android Development] xxbabiboi228xx:
Just curious if this is signed then why doesn't it have a meta-inf folder to go along with the system folder and boot.img
[EVO 4G Android Development] tatnai:
ok buddy, keep asking, makes a lot of sense to me. and looks like he responded. twice.
[EVO 4G Android Development] adriang5555:
Odexed version coming folks!!

New odexed version coming in 20 mins or so!!!!

Yes!!!! We are saved!!!!

http://xdaforums.com/showthread.php?p=8278001#post8278001
[EVO 4G Android Development] xxbabiboi228xx:
@myn

My bad it does have a meta-inf folder I had to go back into the extracted folder again thanks for the OTA
[EVO 4G Android Development] jkinnison90:
Now this thread can quit being ruined.

==

Anyways, thanks for this! I'm using it now. Getting really good battery life, and buttery smooth.
[EVO 4G Android Development] juancaperez2000:
if you compare CM6 with 7.6 turbo and this one do you se some difference on battery life
[EVO 4G Android Development] Trident:
In what way? Which is better? Any trade-offs?
[EVO 4G Android Development] Virus:
hey guys here is a mirror if you need it OTA_Supersonic_3.29.651.5-DEODEX.zip
[EVO 4G Android Development] bigzeak85:
i tried the perflock disable and i still cant clock it over 998 any other suggestions??
[EVO 4G Android Development] Eurasian Lynx:
Are you saying this rom broke your 4G?
[EVO 4G Android Development] jkinnison90:
I'd say I get better... the new HTC kernel from the 3.28 and now 3.29 has a good improvement on battery for me..

Not saying 7.6 turbo on CM6 gave me terrible battery, it provided me around 3 hours screen on and usually 20 hours standby. So it was still excellent for me.
[EVO 4G Android Development] myn:
Thanks :). Added to first post
[EVO 4G Android Development] juancaperez2000:
thanks, ill be doing a test tomorrow
[EVO 4G Android Development] luckylui:
Anyone haveing titanium backup problems? It keeps rebooting me..
[EVO 4G Android Development] luisrcastillo:
Works great. Thanks!!!
[EVO 4G Android Development] jdawg0024:
I had problems restoring my apps, ended up having to download all of them again through the market... small price to pay for the update with root access
[EVO 4G Android Development] Trident:
Can someone follow-up on this?
[EVO 4G Android Development] nugzo:
It's obvious there is way more demand for de-odexed. If you are in a hurry, track down the OTA and root it for yourself. I swear the nerve, demanding odex.... this is funny. You've probably sealed the fate on the odex version from this dev with all the complaining/demanding. good luck!
[EVO 4G Android Development] nugzo:
I have this rom setup completely like i like it, themed and all. It is running awesome. I cant even tell it's a stock rom. Thanks OP and Thanks HTC! I have a great feeling about this one. I wish i knew if the 30 fps cap was a hardware or software fix though.. anyway, it'll be known soon enough. Thanks again OP!
[EVO 4G Android Development] adriang5555:
Actually, yes. I couldn't restore any apps at all with it at first. Kept getting an error (can't remeber what it was exactly). Rebooted a few times (both voluntarily and non-voluntarily), ran the busy box update in TB twice, and it started letting me restore my apps again.
[EVO 4G Android Development] commandoscorch:
People seriously need to calm down about the odexed version. He stated that he would release it after he got off work tomorrow. I am eagerly awaiting an odexed version, but I am more than willing to be patient.