• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [CDMA] rooting evo 3d

scotty85

scotty85

Extreme Android User
Evo3dnme said:
Ive seen on some threads that you are an expert on htc's, so im asking for help. Okay so i have been trying to root my evo 3d for a few months now and i dont have an idea how. I have got as far as unlocking the bootloader and that is it. When i search for how to root it, since the phone is and older model everything is outdated and i cant find anything that will work for my phone right now. My phone has an unlocked bootloader(as mentioned),1.58...software 2.89...android version 4.0.3..sense 3.6. If there is anything else you need to help me ill let you know, i would very much appreciate your help in rooting my phone,seeing how im having trouble.
Thanks,
Evo3Dnme.
Click to expand...

hi Evo3dnme,ive moved your question out into the forum,so that others may also benefit from its discussion :)
 
I assume this is from a PM he sent you ??
 
you can stay s-on and be rooted,and flash roms if you want to,but be aware that htcdev has limitations and you will have to use special procedures to flash roms.

i personally only recomend htcdev as a means of root access,to be able to use other tools or exploits.

more info on the pains of htcdev,and ways to deal with them,here(this is for the rezound,but the info applies): http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html

i would strongly recomend to become s-off. THIS Allows access to all partitions,and allows recovery to be able to install the kernel,and thus makes your life a bunch easier when flasing roms and restoring backups.

if all you have done is unlock your bootloader,youll need to either permantly or temporarily install a recovery,and use that to install superuser root files.

after that,you can use the juopunutbear tool to achieve s-off.
Unlimited.IO
 
you are allready htcdev unlocked,but you can use steps 2 and 3 of this guide to flash recovery,and install super user:

i sometimes refer folks to my rezound guide in other forums,so i decided to make a slightly more "universal" version that i could replicate in other forums,so everyone has a dedicated guide,and there are not accidents with accidental application of rezound specific details or files. devices i am familiar with i will try and tweak and add device specific recovery downloads/info. whatever device youre working on,please feel free to post in this thread,i will be happy to assist you :)

before we get started,however,be aware that htcdev does have its limitations. it can be used if you only wish to add root access to delete bloat and run a few root requiring apps,but IMO it is best used as a "steppig stone" to get root for downgrade,or for other exploits to run. if s-off is availble on any "downgradeable to" firmware,i do highly recomend to try and achieve that goal if you wish to activly flash roms. im happy to help with this,as well,if needed. :)

the basic steps will be:
1)unlock with htcdev
2)temporarily or permanently flash a recovery
3)flash root files

before you start,go ahead and download these files:
-mini-adb.zip: mini-adb.zip
-the latest custom recovery image of your choice, for your device( for cdma(sprint or virgin mobile use this: PG86IMG-recovery_ext_4.zip )
-superuser files: for froyo use superuser 3.07 (found on revolutionary public wiki). for GB or ICS,use the latest superSU from this thread on xda (the download link is where is says: CWM installable ZIP: CWM-SuperSU-v0.96.zip )
-go to HTCdev - Unlock Bootloader and register an account



1)unlock with htcdev
first thing you need is drivers for adb to see your phone. if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary

most guides simply say "follow the directions to unlock with htcdev" but im gonna go thru it with ya :) the mini-adb.zip file is all the files that htcdev is telling you to download and put into a folder,so allready this should be a lil easier ;)

1)prepair ADB
-unzip your mini-adb.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC(sorry, you mac guys will need to develop this for yourself,i dont have a mac). root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "mini-adb_devicename" since youll be putting some device specific files in here. (directions from here forward will assume this folder to be named "mini-adb_vigor",as an example)
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your mini-adb_vigor directory. type the following at the prompt in your cmd window:

cd c:\mini-adb_vigor

your command promt should change to "c:mini-adb_vigor>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)entered the name of the folder correctly ("mini-adb_vigor" in this case)

-now make sure usb debugging is checked in settings/apps/development,and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:

adb devices

if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

2)unlock using htcdev
-go to HTCdev - Unlock Bootloader and sign in to your account. chose your device from the "select your device bar"(or "other supported devices" if its not listed) and click the green "begin unlock bootloader" button underneath.
-click yes to procede,then read the warnings before checking the boxes and clicking yes to continue,as they are basically explaining that your warranty is now void,and any repairs that your phone needs that may have been a result of unlocking your bootloader and messing with your phones operating system may no longer be covered under mfgr warranty

*check your hboot screen. if you allready have an htc compatible hboot, then skip ahead to the next step,you dont need this.if you have a pink **locked** at the top of the hboot screen,then it is compatible with htcdev. if you dont have a compatible hboot,then download the RUU for the new hboot. right click it,and run as administrator. plug in your phone when prompted to. it will ugrade your hboot to the htcdev unlock compatible version.

-steps 1-4 are describing how to get your phone into bootloader mode and connect it to your PC,wich we have done above. ignore these steps and simply type in your cmd window:

adb reboot bootloader

it may take several seconds,but this command should boot your phone into the "fastboot" screen wich is white with a bunch of colored writing. once this happens,make sure your phone is still being seen in fastboot. type:

fastboot devices

again,this should return your phones serial number.

-click the green procede to step 5 bubble.
-steps 5-7 are telling you how to find the files and utilities inside your mini-adb folder. you have them,so ignore steps 5-7.
-click the green procede to step 8 bubble.
-heres where steps are important,steps 8-10 are telling you how to get your unlock token,and send it to htc. its phone specific(so they prolly know your serial number,meid,etc) so no,you cant use your buddys unlock token and not have htc know that youve unlocked your bootloader. ;) copy this line either from below,or from step 8,and paste it into the prompt in your cmd window. you have to right click to paste in cmd,you cannot control/v :

fastboot oem get_identifier_token

-after yuo hit enter,you will get a bunch of letters that are your identifier token. not much i can say,other than follow the directions in steps 9 and 10 to copy and submit your identifier token to HTC. make sure you get the characters as shown in the pic,with no extra lines or letters. note that you can also hit the "enter" key on your PC to copy,as well as right clicking.
-click the green submit button. wait patiently for an email containing your unlock code. (dont worry,it should come pretty fast :p )
-save the unlock_code.bin that htc sends you directly to your mini-adb folder(if your PC automatically downloads somewhere else,no biggie. just move the unlock code to mini-adb folder)
-click the link in your email to get the rest of the unlock instructions
-step 12 is where them magic happens :D copy from below,or from htc dev:

fastboot flash unlocktoken Unlock_code.bin

-youll see the purdy screen pictured in step 13. use the vol rocker to chose "yes unlock bootloader" and select it with the power button. your phone will reboot,performaing a factory data reset in the process. your data is gone,sorry :( this boot may take a bit longer than they normally do,dont freak out this is normal

as you can see,once the adb files are put in one place to download,its not hard to use,and the commands are pretty simple. below is what you will see in your command window,the red are my inputs.

Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]


c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
                              ... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
INFO021839BFA7465CD0788664688DCCFDEA
INFO33A2FD2C96C7308DD3C57A517DBA8E14
INFO8048F98A9FEA06B8F2AD05D4D3497CFE
INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
INFO27C33E209D472E6C11753E9D7BCBCE6D
INFO90D9F226E827B6C26165A029B6F7DFF2
INFO63E382B4C82F9F6D866C01B9823ED1BC
INFO0EEFA859327E6B5AC4C24533C9DFA7AF
INFODBD70D55E4666B4B41828B76FFBD010C
INFO1B916E350EFF199EA5B096FF3337FE19
INFO40E6CA9E7F1DD5B33D8D4780DD775289
INFO953404686AEC4C3CB6F1BBB9DC69BA13
INFO8738C00DAFF280ECF02D0C7A66E13855
INFO1D756616732FF47915EAD551A6933E08
INFO10C541C7RD02C14991E83CC49FCA4B92
INFO<<<<< Identifier Token End >>>>>
OKAY [  0.069s]
finished. total time: 0.070s

c:mini-adb_vigor>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
  sending 'unlocktoken' (0 KB)... OKAY [  0.143s]
         writing 'unlocktoken'... INFOunlock token check successfully
OKAY [  0.011s]
finished. total time: 0.156s

c:mini-adb_vigor>

2)flash a recovery
if you want to run stock,do not permanently install your recovery. keeping the stock recovery on the phone will ensure that you recieve OTAs without a hitch,wich i know is important to alot of users. YES,the OTA will break root. its no big deal. one good thing about htcdev is that you will always be able to reroot after,simply by following steps 2 and 3 again to launch recovery,flash superser.

once youve either skipped past all the setup,or have re-set up and are ready to root,chose either of the following options to either permantly or termporarily install a recovery:

1)temporary recovery:
-move the recovery image file you downloaded above and place it into the mini-adb folder.
-put the superuser zip file onto your phones sd card
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:

cd c:\mini-adb_vigor

-make sure youre connected by typing:

adb devices

-should return serial number
-check the md5 of your recovery image:

md5sums <recoveryname>.img

**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)

-boot to bootloader:

adb reboot bootloader

-check for connectivity:

fastboot devices

-should return serial number
-temporarily launch your recovery to phone memory:

fastboot boot <recoveryname>.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.

in your command window you will see(red are my inputs):
Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]

c:mini-adb_vigor>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img                 915d5e3cb662076f36f3d6e54759e951

c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot boot recovery-ra-vigor-3.14-gnm.img[/COLOR]
        downloading 'boot.img'... OKAY [  1.518s]
                       booting... OKAY [  0.005s]
finished. total time: 1.523s
2)permanently install your recovery
-move the image file you downloaded above and place it into the mini-adb folder.
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:

cd c:\mini-adb_vigor

-make sure youre connected by typing:

adb devices

-should return serial number
-check the md5 of your recovery image:

md5sums <recoveryname>.img

**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)

-boot to bootloader:

adb reboot bootloader

-check for connectivity:

fastboot devices

-should return serial number
-permanently flash your recovery to phones recovery partition:

fastboot flash recovery <recoveryname>.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. amon ra is now permanently on your phone when you need it. be aware that you can no longer accept OTAs,unless you reinstall the stock recovery at some point before the next OTAs are pushed.
-to get to recovery,push the power button to select hboot. once in hboot wait for the green writing to flash and disapear,then select recovery.

*note that you can still launch recovery by using the command from scenario 1 above.
-youll then see the HTC splash screen,then your recovery.

and the code(again,red my inputs):
Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="red"]cd c:\mini-adb_vigor[/COLOR]

c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img                 915d5e3cb662076f36f3d6e54759e951

c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot flash recovery recovery-ra-vigor-3.14-gnm.img[/COLOR]
  sending 'recovery' (7074 KB)... OKAY [  1.659s]
            writing 'recovery'... OKAY [  5.179s]
finished. total time: 6.840s
3)flash superuser root files*
there is not much to explain with this one. if booted to recovery from above,use the recovery menu on your phone to:
-make a backup of your stock,unrooted rom. completely optional,but a very good idea,IMO.
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-reboot

*congratulations,youre rooted :D
if your device has procedures to s-off,or procedures to downgrade to more exploitable firmware,you can procede with that now :)

if youre considering leaving htcdev unlock,read this if you want to flash roms: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html

s-off is better,and worth whatever extra efforts to achieve if available.

*hope it helps,holler if you have questions :)

donate to my device fund :)
Click to expand...

just let us know what specific questions you have,and well be happy to help :)
 
Looks like we will have to create one for the 3VO, J, has a good one but I guess some of the files are outdated since the HBoot 1.58 release. I would C&P but it is not my work and I think it should be posted by you so you get the proper credit, I will post the link in the sticky section though for quick viewing for those that want it.

Damn that is a lot of stuff there, great work Scotty. ;)



scotty85 said:
you can stay s-on and be rooted,and flash roms if you want to,but be aware that htcdev has limitations and you will have to use special procedures to flash roms.

i personally only recomend htcdev as a means of root access,to be able to use other tools or exploits.

more info on the pains of htcdev,and ways to deal with them,here(this is for the rezound,but the info applies): http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html

i would strongly recomend to become s-off. THIS Allows access to all partitions,and allows recovery to be able to install the kernel,and thus makes your life a bunch easier when flasing roms and restoring backups.

if all you have done is unlock your bootloader,youll need to either permantly or temporarily install a recovery,and use that to install superuser root files.

after that,you can use the juopunutbear tool to achieve s-off.
Unlimited.IO
Click to expand...
 
That guide was the last one I tried, it had an issue with the 'adb' files, my computer said they were out of date and killed them ,
 
Nalej said:
https://www.youtube.com/watch?v=jt25eiIBJ14&feature=bf_prev&list=FLMZlTum49KSeSqtLG5FqKXw

I'm a little slow and learn and feel better by watching.
I found this youtube video online. I watched it and read the noob guide to rooting here
and it all seems pretty similiar.
My concern is that the video claims for GSM and CDMA which I'm sure is not the case.
... Would you guys recommend this video?
Click to expand...

Cdma and gsm uses 2 different files etc for root, I'd say ehhh I wouldn't go by the video.

Sent From My Paranoid Evo 3D Using TapaTalk 2
 
Nalej said:
Okay, I just had the same issue :(
Click to expand...

Update: I tried "fastboot device" vice "adb device" and it progressed. First time. I'm sure I'm messing something up.

Update 2: Alright! Just finished step 2. Backing up stock ROM and clearing all that you recommended then installing superuser. Thanks! Im rooted!!!!!!! I'm definitely going to donate. Noob guide was legit.
 
glad it worked for you. the main difference is in the recovery files. the gsm recovery should work on cdma and vice versa(tho i would NOT recomend trying it),but the gsm recovery will not know its not on a gsm device :eek: this will lead to a very bad experience if one tried to use rom manager,as it would only be displaying gsm roms.

if you go on to become s-off,you would not want to use a cdma download for the s off tool on gsm or vice versa,as it will not install the correct hboot,wich would lead to a bricked device(actually i think the tool would know its not the correct one and not run,but again, i wouldnt try it ;))

if youre considering stoping here,and using htcdev to flash roms,make sure you read this: http://androidforums.com/cdma-evo-3...install-recovery-root-htcdev.html#post5137811

IMO s-off is well worth the efforts to achieve. it makes your life a TON easier. there is some s-off faq and info here:
http://androidforums.com/cdma-evo-3...fo-faq-root-s-off-cdma-evo-3d-all-hboots.html
 
Evo3dnme said:
That guide was the last one I tried, it had an issue with the 'adb' files, my computer said they were out of date and killed them ,
Click to expand...

Nalej said:
Okay, I just had the same issue :(
Click to expand...

if you guys are refering to the "adb server is out of date,killing..." error,it is nothing to be concerned with. this wont impact the ability to use the file to comunicate with the phone over adb or fastboot.

if anyone has an error after this message,post specifically(a copy/paste of the cmd window is ideal) the error message and well help figure it out,as the out of date message is not hindering any progress :)
 
Okay, I flashed an ICS rom just to check it out. Worked like a charm.
I then repeated the steps of "wipe cache, wipe davlek(?) cache then did a factory reset"
I then attempted to flash another rom and when I did, everything looked normal.
(or the same as the prior attempt... which was my first time ever)
The white screen on start up with the green 'htc' popped up and then just stayed there.
I figured this may take some time and it was already 2am so I just passed out.
I woke up to a dead phone and whenever I start it up it stays on that white screen-green 'htc' screen.
I then tried removing the battery and pressing power and volume down and nothing happens :(
I hold it down and nothing happens and when I let go, it starts up normally and goes to the white background-green htc screen :(

The two ROMS I used are from xda [ROM]SolidRom Suite[JB 4.1.2][JB 4.1.1][Sense4.1][Sense3.6][Senseless/AOSP][MyUI]:

http://forum.xda-developers.com/showthread.php?t=1808332

Did I ruin the phone?
 
I am on my way out right now, and don't have to check the full thread here, but what HBoot are you on, I believe that Rom needs to be on the new base, and HBoot 1.58, see below quote. I will check in later when I get into work ;)

You need to flash 1.58, the new firmware to flash my Rom.
And just have 4ext recovery, have smart flash enabled, wipe all partitions except sdcard and then flash like normal.
Click to expand...



Nalej said:
Okay, I flashed an ICS rom just to check it out. Worked like a charm.
I then repeated the steps of "wipe cache, wipe davlek(?) cache then did a factory reset"
I then attempted to flash another rom and when I did, everything looked normal.
(or the same as the prior attempt... which was my first time ever)
The white screen on start up with the green 'htc' popped up and then just stayed there.
I figured this may take some time and it was already 2am so I just passed out.
I woke up to a dead phone and whenever I start it up it stays on that white screen-green 'htc' screen.
I then tried removing the battery and pressing power and volume down and nothing happens :(
I hold it down and nothing happens and when I let go, it starts up normally and goes to the white background-green htc screen :(

The two ROMS I used are from xda [ROM]SolidRom Suite[JB 4.1.2][JB 4.1.1][Sense4.1][Sense3.6][Senseless/AOSP][MyUI]:

http://forum.xda-developers.com/showthread.php?t=1808332

Did I ruin the phone?
Click to expand...
 
Yes, I'm on hboot 1.58. That rom was the only JB one that worked on 1.58. All the rest required 1.5 or less.
(Talk about a major bummer once I finally was able to root for the first time lol)

Thanks man!


edit: I contacted the guy from the youtube video I used as a cross reference and he responded with:

DON ,T BE SCARED (are u?)
this thing is called BOOTLOOP
the rom has problems OR U DID NOT FLASH THE KERNAL!!!!
to flash the kernal u need a working software and install an&#65279; program called flash image gui
restore your nandroid back u created before flashing
DID U MADE A NANDROID BACK UP
If no
then u need to download the ruu image of your phone GOOGLE TIME keep searching until u got one
Click to expand...

1-I didn't know I needed to flash the kernel if I was going to stick with the one provided with the custom ROM (is that a gross conceptual error?)
2-If I do need to flash the kernel first... I have no idea how.
3-I looked up flash image gui and all the instructions assume your phone is working fine so I'm not sure what I'm suppose to do with that.

I was so excited when the first rom (ICS) worked... guess that's what I get for then trying to upgrade to JB.


edit2: I finally figured out how to fastboot. I keep trying clear caches then factory reset. I install new rom and then it bootloops again. What am I doing wrong?
 
Okay, my phone's in another bootloop. This one now shows the HTC symbol, then the custom design comes up then the phone shuts off and repeats.

This is what I'm doing:

hboot menu
A) Wipe Cache
B) Wipe Dalvik Cache
C) Wipe Everything (Data Factory Reset)
[All from the Noob guide for rooting]

From the developer:
Make sure to format all partitions except sdcard. And then format dalvik-cache.
--How do I format the dalvik-cache specifically? I don't see that as an option.
I'm using 4ext recovery as the developer recommended as well.

Then I upload the custom rom zip
Reboot


Then I'm stuck in a reboot again
 
I put the back to stock and then retried it with the same bootloop. Is that what you mean by a fresh install?
Also, the develop said to enable smart flash if you were S-On. I'm not. Though I did try it one of my tries with no effect.
 
Nalej said:
Yes, I'm on hboot 1.58. That rom was the only JB one that worked on 1.58. All the rest required 1.5 or less.
(Talk about a major bummer once I finally was able to root for the first time lol)
Click to expand...

if your other roms require hboot 1.5 or less,you just need to run an ruu containing that one or less. we can help you find one :)

generally speaking,roms designed to work on 1.58+ are never going to work on roms that need 1.50-,no matter what your install porocedure is. there were a couple of critical changes in mount points between gingerbread and ICS,thus making them firmware specific
 
Thus why I asked, but I believe he said that was why he tried that JB Rom, bc it was for HBoot 1.58 which he said he was on ;)

I suggest you, I and Brian, get together and make a questionnaire for members when they have issues, and lets add it to the stick thread and whenever we see a member with an issue, this way we can get all the relevant info needed. ;)



scotty85 said:
if your other roms require hboot 1.5 or less,you just need to run an ruu containing that one or less. we can help you find one :)

generally speaking,roms designed to work on 1.58+ are never going to work on roms that need 1.50-,no matter what your install porocedure is. there were a couple of critical changes in mount points between gingerbread and ICS,thus making them firmware specific
Click to expand...
 
Thanks! Yea, whatever help you can give I'd appreciate greatly.
The Nexus 4 not being available for Sprint (yet?) gave me the push to just upgrade what I have already instead of buying a new phone I don't love.
 
DonB said:
Thus why I asked, but I believe he said that was why he tried that JB Rom, bc it was for HBoot 1.58 which he said he was on ;)
Click to expand...
right... just trying to get the point across that roms will have different firmware requirements,and that he will need to make sure he is on the correct firmware for the roms he wants to try. if hes on 1.58,and flashes one that requires 1.5 or less,then there is no question that it wont work ;) its quite understandalbe for a new rooter to not really understand the importance of things working together(hboot,radio,rom,etc)

i personally would run whole ruus to switch between 1.5 and 1.58 hboots(unless one of us wants to pull all the firmware from both versions) as from things ive seen,just changing part of a firmware package can have not-so desireable affects,anywhere from not booting,to unstable data. luckily,s-on devices do not even permit you to change fimrware,as doing mix-and matching while s-on can leave the device potentially hard bricked :eek:

DonB said:
I suggest you, I and Brian, get together and make a questionnaire for members when they have issues, and lets add it to the stick thread and whenever we see a member with an issue, this way we can get all the relevant info needed. ;)
Click to expand...

ill send yall a PM :)
 
Not to stick my nose in, but I would appreciate something like that(even though I think I'm getting it straight). Used to (and sometimes still), I didn't know whether to put my left hand in, my left hand out, or shake it all about... B-)
 
You must log in or register to reply here.
Back
Top Bottom