Related
i was reading instructions on how to root but i belive its more difficult to root a 32b version. can someone show me the easiest way to root a 32b mytouch?
thank you so much.
Check out the Cyanogen wiki for instructions to flash his rom on your Mytouch, the instructions are simple. Yes, you also get root access.
when i attempt to flash to the sappimg i get an error saying "Main version is older"
and in the cyan wiki it says the goldcard method does not work.
im having the same problem...i never had these many problems rooting a phone . I have a g1 that i rotted flawlessly. not only did i hear the gold card method doesn't work but it also is very complicated. Im stuck! I really wish the one click root method work for the 1.6
Pvt 32b
hboot 1.33.0007 sapp3000
cpld10
radio 2.22.19.26i
when i had my g1 rooting was easy, this is a nightmare.
I think you have to downgrade to 1.5 to root. That's what I did. Good luck!
Also as mentioned before, check out the cyanogenmod wiki. It gives a very detailed instructions list to help you out.
downgrading to 1.5 is the problem we CANT!!!!
BossLady said:
downgrading to 1.5 is the problem we CANT!!!!
Click to expand...
Click to collapse
exactly. if i could downgrade i wouldnt have made this thread
someone please help us.
does this not work?
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
methodz said:
does this not work?
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
for the third time...no. i cannont downgrade my phone.
i got an error saying "Main version is older"
trexxcrap2 said:
for the third time...no. i cannont downgrade my phone.
i got an error saying "Main version is older"
Click to expand...
Click to collapse
ARE WE THE ONLY TWO THAT GET THIS?!!!?
I think the only way is either suck it up and use the goldcard method or wait until flashrec updates the apk. we're screwed!
I had this message when I rooted my 32b device yesterday so I followed the gold card option and everything worked without a hitch.
I was told it didnt work in Windows 7 but it worked fine on my xp pc.
Happy to help if you have questions.
Cheers
Dave
Guess its a 32B problem, im able to downgrade to 1.5 but them im getting an error when im trying to use Flash Recover to back up my files.
http://www.youtube.com/watch?v=lR2bvjPXMdQ&feature=related
this video helped me root it by downgrading. If this doesn't work, I don't know..
Jeffmeister said:
Guess its a 32B problem, im able to downgrade to 1.5 but them im getting an error when im trying to use Flash Recover to back up my files.
Click to expand...
Click to collapse
Are you following this steps form the cyanogen wiki?
h t t p ://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod
I had the problem with flash recovery when I was running it under 1.6. Once I downgraded back to 1.5, it works fine without a hitch. Flashrec version: flashrec-20090815.apk.
same error message
I'm getting the same error message. I have previously rooted around 10 mytouch phones without problems, but using the same procedure now is giving me that error. It looks like the Hboot software has been updated on any newer phones and is having an issue with updating (or backdating, I suppose) to 1.5
If anyone has a work around I would love to know it.
The old version of Hboot that used to work is HBOOT-1.33.0006
The new version, which is not working, is HBOOT-1.33.0007
Anyone know of a way to backdate the HBOOT software?
WTF....
This phone is impossible to root (over acting,but pissed off) I've tried everything I've read online...I was able to build a goldcard from unlockr's web page,and when installing the sappimg file the damn phone still doesn't want to give up the 1.6....there has got to be something or someone out there that has encountered this bullchip and fixed it
I have a 32B mytouch. did you try unrooting first, before rooting? Just a thought bc i had to do it before rooting, and i had never rooted my phone before that.
do i have root???
HBoot - 1.33.0006 (SAPP 30000)
CPLD - 10
Radio - 2.22.19.261
As i search the forum, i realized that i have "perfected SPL"...that would require me to go through "goldcard" method. I tried and it was so complicated for me...
And then i saw this thread http://forum.xda-developers.com/showthread.php?t=633895 which said you should follow cyanogen's method on this site http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod.
so i follow the steps and everything worked out and now i have cyanogens rom running on my MT3G. .... now my question is ....do i have root??...
can i flash other people's roms assuming i have all the right radio and SPL...
when i try to install Amon_RA's recovery img through Terminal Emulator, after i type $su and hit enter....nothing happens....it does not ask me for su permission????.....
Please Help....If i dont have root how was i able to flash cyanogens rom??
do i need to do the goldcard method....or am i set...with root.??
Hey guys, I have spent the last 8 hours trying to figure this out.
I have a MyTouch 3g 1.2 and I want to root it and install Cyanogen's new ROM. I have been following the rooting guide from TheUnlckr.com.
I am able to complete everything fine (I needed to substitute the sappimg for the Sapphire one to make it work), but it finally completed.
When I go to fastboot with SDK, I can see my device, so everything looks fine. However, when I go to flash the radio, hboot, and recovery images, I get a error that says:
Code:
C:\AndroidSDK\tools>fastboot flash radio radio.img
sending 'radio' <21504 KB>...FAILED <remote: not allow>
finished. total time: 0.016s
This is the pattern for each of the files I try to flash...
This is where I'm at, and I haven't even gotten to flashing the ROM yet. So, I currently just have a stock device. Can someone please help me out?
I tried using the following sappimg:
2.53.707.2_-_sappimg
SAPPIMG_Sapphire_T-Mobile_US_2.10.531.4_release_signed
the following SPL:
update.Engineering-SPL-HBOOT-1.33.2010-signed
the following recovery images:
recovery-RA-sapphire-v1.6.2G.img
flashrec-1.1.2-20090909.apk
flashrec-1.1.3-20091107-2
flashrec-20090815
I'm clearly all over the place now. Someone please point me in the right direction. I tried several different ways to fix it, but none of them worked. The most reason I tried was the method of using the flashrec to flash a recovery image while the phone is on, instead of fastbooting it. That didn't work because it kept saying it was the wrong image for the phone.
Thanks in advance guys. And believe me, I've been searching and searching.
Dane
before you can flash anything with fastboot, you have to shoehorn that engineering SPL into the phone somehow (probably have to make a goldcard, but I don't know for sure on the 1.2 mytouch)
which rooting guide are you using? (there are many different ones on unlockr, some of which are terribly obsolete)
also, flashrec isn't a recovery image, its a one-click rooting app that only works on android 1.5 (pretty sure the 1.2 mytouch only runs 1.6)
adavis159 said:
before you can flash anything with fastboot, you have to shoehorn that engineering SPL into the phone somehow (probably have to make a goldcard, but I don't know for sure on the 1.2 mytouch)
which rooting guide are you using? (there are many different ones on unlockr, some of which are terribly obsolete)
also, flashrec isn't a recovery image, its a one-click rooting app that only works on android 1.5 (pretty sure the 1.2 mytouch only runs 1.6)
Click to expand...
Click to collapse
This was the guide I was using. (I can't link to outside sites, so I'll just copy it as text) http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
I also successfully created a goldcard, and installed all the ADB stuff. The part that's hanging me up is the flashing of the recovery image via fastboot usb.
I'm so close! I have successfully rooted two other mytouch devices, but they were not the 1.2 version.
Any more help would be great!
Dane
danegerous said:
I am able to complete everything fine (I needed to substitute the sappimg for the Sapphire one to make it work), but it finally completed.
Click to expand...
Click to collapse
what "sapphire" image did you substitute? and what happened when you tried to use the sappimg that they gave you in the instructions?
When I tried using that image, it just said "wrong file for this phone" or something like that. I know the goldcard was done right, though, because it works with another sappimg. I'm trying to follow cryptsmoker's guide now. I'm going to try and use the engineering img/SPL now. We'll see how it goes.
Ok, now I'm getting frustrated.
Here is my info:
Sapphire PVT 32A Ship S-on G
Hboot-1.33.0013 (Sapp31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009
I just got the Model ID incorrect!
Update Fail!
This happens with every sappimg I use except T-Mobile 2.10.531.4. I'm sure that's the stock one, so that's probably why. I'm just so ticked.
To clarify again, After I hboot the sappimg, I reboot and instead of being taken to the Magic screen, I'm taken to a standard MyTouch splash, then Android splash, then MyTouch setup screen. My touchscreen works the entire time. Is this because I basically just reinstalled the stock ROM?
I just can't seem to get ANY other sappimg to work beside the stock one. I've used three different goldcards and all of them work the exact same way.
Please help!
Dane
yeah, you are just reinstalling the stock files (stock SPL and radio)
just because the t-mobile sappimg works doesn't mean you made the goldcard right.
the point of the goldcard is to trick the phone into installing a non-stock sappimg, you could take a brand new SD card, put the stock sappimg on it and you would still be able to flash it using vol-down+power
open the goldcard.img in HxD and make sure it contains all the lines (including all of line 170), if it doesn't then you need to start over from the beginning (get cid again, reverse it again, get a new goldcard.img)
If goldcard.img is ok, open the sd card in HxD again and make sure all of the first 170 lines of the sd card match the goldcard.img
also, some SD cards just don't work for making goldcards. I used a lexar 1gb, and kingston 2gb cards are reported to work
I didn't paste over the entire 170 line while making the goldcard. I used the "select" feature and chose 0-170...that could be my mistake. Here we go again!
I actually never got this to work the first time. I was really excited since I heard I would be getting the T-Mobile update soon, but then I read a little further and saw that the 2.1 is not yet included...so, I will be figuring this out today, mark my words!
Wish me luck!
Dane
I had a similar problem and it was the goldcard. Although I had made the goldcard and it worked before, using the same goldcard I get the same error message as you. I made a new goldcard and it worked flawlessly to flash using fastboot. Make sure you are using one of the brands that are know to work.
OK, new problem now. I installed everything and got it all to work. I actually had the stock cm rom working (an out of date version from the unlockr). Well, I tried to update and I started by flashing the 6.35.16.19 radio. Apparently that worked but now nothing else will.
In the HBOOT screen, I see this:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-6.35.16.19
Oct 21 2009,
Every time I try and update the Sappimg file, I get stuck at the updating phase of the radio_v2 portion. Please help guys, I don't know enough about this to figure it out and it's really killing me!
I figure I need to get back to the stock radio I started with (3.22 or whatever), but I can't. Even when I try to flash the radio in fastboot, it takes way too long and never finishes.
Your speedy replies are greatly appreciated.
Thanks
Dane
Got your pm.
Facts: STOP MESSING UP YOUR DEVICE.....
You are working in the blind... mixing bad spl and radio combos.....
So STOP what you doing and read and understand before you continue.
You can't just take any sappimg.zip and apply it... I has complete partitions layout... like the spl, radio, recovery ect...
So if you take whatever you find on the net and apply it, you will **** your device up... just like you did now...
Having the 6.35 radio and a perfected 1.33 spl... Just bad for business!
What is your current status:
Access to adb?
Access to fastboot?
Access to recovery?
Access to rom/system?
Also post fastboot info...
Then we can take it from there :0)
And for gods sake... STOP flashing stuff.
I have access to adb, fastboot, and hboot. No ROM/system or recovery.
Clarification: Since I cannot access the system of the phone, I do NOT have access to ADB. I cannot see the device when I type in 'adb devices' within the AndroidSDK\tools path.
Fastboot info:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
Aug 21 2009
The radio used is: Radio_HTC_PVT_32A_6.35.10.18.img
the hboot: hboot-1.76.2007.nb0
the recovery: recovery-RA-hero-v1.6.2.img
I have since tried to go into one of your other threads and at least match up my SPL/Radio combo. Any and all help is greatly appreciated.
OK.... you are now in a god situation...
You have a good combo and eng spl...
We can work with this....
1) boot into fastboot
2)download the fastboot commander (magic).... check my signature
3)start the tool... does it print the device info?
If yes, do this:
Go to the magic 32A tab.
Push "flash old".
IF all successful, then go to "misc" tab and push "reboot device".
When device has rebooted, push "print device info".
Now copy all text and posted here...
IF you get ANY errors... DO NOT REBOOT, DO NOT CLOSE THE TOOL...
Just take the output + the content of the "actual tab" and post here....
Again, IF you get ANY errors... DO NOT REBOOT, DO NOT CLOSE THE TOOL!
If the tool does not print the device info, then post here...
mumilover said:
ok... don't do **** until i post back here... give me like 15 min.
Click to expand...
Click to collapse
I'm seriously just sitting here waiting. Thanks a ton. I'll buy you a beer.
just updated my last post
look up :0)
Now i'm the one waiting :0)
Sorry, my battery died, I'm running around to trying to piece everything together. Here I go...
Just do what i wrote.... Read, understand, read, understand, execute.
Ok, i just want to say hello to all members, and i hope you'll be abe to help me.
I have HTC Magic with these specifications:
SAPHHIRE PVT 32A SHIP S ON H
HBOOT 1 76 2009 (SAPP10000)
CPLD 12
RADIO 6 35 08 29
Dec 8 2009 17 38 48
Firmware ver 1 5
Kernel Version 2 6 27 5b476e83 htc kernel and18 2 989
Build Number 3 05 401 3 CL 98222 release keys (coulndt put dots between number again, because I'm new user)
I have downloaded and installed the HTC Sense update on this phone few months ago. (I couldn't download the Sense update from the HTC site with my phone's serial number that i entered, instead I found and downloaded the update here on the forum, that someone posted.)
Before the update, my phone SPL was 1 33 something and radio was 2 22 something if I remember correctly.
I have tried this:
How to root the HTC magic in one click guide on unlockr site (cannot provide you the link cause i'm a noob user and cand post links
I wanted to do the rooting the easy way but it was a "no go" i guess
With the FlashRec.apk application couldn't get past the "backup failed" message, because of the SPL i guess??
Then i tried this, because the first article said at the and that i need to unroot the phone with this guide "how to unroot your mytouch 3g" guide also from unlockr site.
I downloaded the sappimg NBH file from the provided link and put it in the root of the SD card, tried the fastboot (volume down + power button) but i could flash the phone, got the "wrong main version" message.
At the end of the article it says that the known issue is
"Issue: Phone says that the wrong Main Version is Older or Wrong Model ID"
and that the solution is:
"Solution: Use our Goldcard Method instead."
I am going to buy a gold card tomorrow, and i would be very thankful if you could point me into the right direction and give me some explanations and hints what should i do next, considering that i have a very "root unfriendly" versions of SPL and Radio. All help is appreciated.
You don't buy a gold card, you make one with an ordinary microsd card and some software you download. Here are instrucitons to get you started:
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
And since the Wiki is down, go to this thread and follow those instructions.
Ok, guys, i made the Goldcard, according to the instructions on the unlockr site, and everything seems ok. I get the problem when i try to load SAPPIMG file from HBOOT, it picks up the sappimg file and start loading it but does not ask me to flash or anything similar, just finishes the process of checking and stays in the HBOOT screen, like nothing happened. Could this be because of a 1.76.0009 perfected SPL that my Magic has? Can my magic be even rooted?
I have done the Goldcard rooting method on the unlockr site, just for the info.
It should tell you to push "action" to continue after it checks the sappimg, with the "action" being to push the trackball.
Sent from my HTC Magic using XDA App
I've made it. It's rooted now.
Used instructions for rooting 1.76.0009, from Orange_24 (whom i thank soooo much)
I have installed Amon_RA's recovery image RA-sapphire-v1.6.2H.
I am still having problems.
I can't install [32a][3.22][6.35] CM6 - FroyoRedux Mod v1.5 (08/01/2010) Froyo Supreme ROM. I start recovery mode (home + power) button, and start Flash Zip form sdcard (i previously copied the CM6-FroyoRedux-v1.5-32a-blk.zip file to the sdcard root) and I always get the "verification failed" message" and that some file is corrupted (it's not the same file always).
My SPL and Radio now are:
SAPHHIRE PVT 32A ENG S OFF H
HBOOT 1.76.2007 (SAPP10000)
6.35.xxx
Check that the ZIP file was downloaded correctly and that your SD card isn't broken. Best way to check would be to copy a file on your card and check if it has the same MD5 sum as on the computer.
God da*n it!
Why do I have problems every step of the way!!??
I have checked the MD5 and managed to install the ROM. Now i'm stuck at the infinite boot screen. Please help, i'm really running out of patience. (I have made Nand backup and stored it on my PC if all else fails).
Don't get me wrong, but from this little experience that i have until now i got the feeling that the rooting concept is just too cumbersome and that all this problems and inconsitencies are the reason why many people never let them selves into the rooting thing. I just hope the reward will be proportional to the amount of problems that an average ROOT beginner user comes in contact for the first time.
PLEASE HELP THIS IS URGENT!!!
I might have bricked my phone. After succesfull install of CM6, my phone went to boot loop, so i tried to NAND restrore my phone. I got the error message to do the NAND restore. I got the error message, saying that to do it from the adb. I didnt know how to do it, so i tried to put some other ROM, just to get the phone working. I tried with the Amon RA's clean donut ROM. Also got the infinite boot. So i tried other recovery, the recovery-RA-sapphire-v1.7.0H, flashed it through recovery adb and got the sporadic restarts after flashing when i go into the recovery mode.
After that i flashed the recovery-RAv1.2.0H.img from fastboot because this recovery is mentioned on the unlockr site instructions on how to install custom ROM. Now i cant get into recovery mode, and cant flash none of the above mentioned recoveries from fastboot.
I really need help and information is my phone bricked. Please, i have been on my computer for the whole weekend, messing around with my android phone.
ill look into wut u can do..
Flash this recovery: http://www.theandroidkitchen.com/fi...download=recovery-RA-Magic32A-6.35-v1.6.2.img and use only ROMs made for NEW RADIO/NR/6.35. Either that, or flash the old radio/spl using eyegor's Radio Switcher (see dev thread).
^ Thank you in advance
The current state of the phone is, just to give you info:
Engineering SPL, S-OFF, HBOOT is 1.76.2007, Radio 6.35.08.29, recovery (flashed from Fast Boot) recovery-RAv1.2.0H which is stuck at boot loop, and Amon RA's clean donut ROM which is also stuck at boot loop.
I suppose the only way to fix this problem is to use adb from Fastboot USB or using gold card?
What are the symptoms of a definitively bricked phone?
keinengel said:
Flash this recovery: http://www.theandroidkitchen.com/fi...download=recovery-RA-Magic32A-6.35-v1.6.2.img and use only ROMs made for NEW RADIO/NR/6.35. Either that, or flash the old radio/spl using eyegor's Radio Switcher (see dev thread).
Click to expand...
Click to collapse
Can you give me the console command to flash it from fastboot? Is that the only way to flash recovery? I have tried flash recovery <recovery_name.ext>, but with no success, i get the :
C:\android-sdk-windows\tools>fastboot flash recovery recovery-RA-Magic32A-6.35-v1.6.2.img
error: cannot load 'recovery-RA-Magic32A-6.35-v1.6.2.img'
EDIT:
Me stupid, forgot to place the recovery in tools folder
I'll try now to load some ROM for 6.35 radio, or maybe downgrade the SPL/Radio
After hearing about the potential issues with the gfree method i decided to go back and completely unroot my phone and start fresh from the traditional method. Everything seems to be fine except one small problem, no matter what i cannot get S=ON. I've tried the gGfree unroot method, ive never installed the ENG boot loader, i did use the gfree command to turn the flag off but the reverse command doesn't seem to turn it back on either. Ive even re flashed a stock image file through Hboot but alas no luck. Any pointers?
Do you have a link for the potential issues? I am curious about what they are.
http://forum.xda-developers.com/showthread.php?t=1079025
Its been getting worse recently judging from the number of posts about it.
Doogitronix said:
http://forum.xda-developers.com/showthread.php?t=1079025
Its been getting worse recently judging from the number of posts about it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1035278
Hey could you tell me if this is also gfree? I am new to the MT4G so im not so caught up with certain terms yet. I ill get ENG SPL then to be safe.
That is the Gfree method. For now its probably best not to use it until the causes of the bad partition issues are found and resolved.
Rooting the phone with either method can cause this,no one knws why & how this happens,it just does.. I mean if u full wipe completely at least twice & let the kernel set after phne boots,u shouldnt have this issue just be mindful of what u doin.. Flash recovery before goin into clockwork to wipe system,thats what I do & havent had this problem since my 1st mytouch 4g
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
Kernel-ckisgen-smartass-v1.1
You may be right, but back to the original issue i still cant get S=ON no matter which method i use to root or unroot. I did find something odd though when rooting with the root.sh file, i get this error.
sh root.sh
Inserting kernel module
insmod: init_module '/sdcard/root/wpx.ko' failed (Function not implemented)
Duplicating hboot
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.650 secs (1613193 bytes/sec)
I wonder if that's an issue.
On a side note i went ahead and flashed the ENG boot loader and it shows my CID is still CID = 11111111, which from what i have read is all around SU permissions on the phone. One more question, how do i find out if i successfully re locked the SIMLOCK?
I wanted to thank you for informing me of this and I hope you fix your MT4G too, now I have upgraded to eng for safety.
-Best wishes
Looks like i found a resolution! I followed jjackson56's method detailed here
http://forum.xda-developers.com/showthread.php?t=924923&highlight=unroot
but instead of running the script i went by the helpful tip of one of the commentators on the thread erickdj who basically spelled it out for me.
"I was having issues using the automated script to unroot(mostly to turn s-on), so I realized all I needed to do was run "./gfree --secu_flag on" to turn security "ON" and then flash the PD15IMG.zip file through hboot, that set the phone back to stock really fast and easy. Didn't have to mess with part7backup files or nothing like that. "
So in summary, download and unzip the PD15IMG.zip to your sd card from that thread and run the "./gfree --secu_flag on" then reboot into hboot and select yes to run the update, itll take restart if you have the ENG bootloader because it relflashes the stock hboot then itll carry on and restore everything else.
(Note i used this process while on an ENG bootloader obviously so if you try with a stock hboot and fail consider flashing an ENG loader then trying again)
The 2 root methods i know about
1. sh root.sh
2. gfree
is there any other ?
Today I accidently turned it on (the thing in the bootloader) and now I can't turn it off no matter what so I can do a revert to stock .img, I used the PDI15.img or w.e that would revert back to stock forgetting that I had the newest radio and now I can't revert to stock or turn S-OFF. Please help
Current Configurations:
GLACIER PVT SHIP S-ON
HBOOT - 0.86.0000
MICORP - 0429
RADIO - 26.09.04.26_M
eMMC - BOOT
More Info:
When I use a PDIMG or w/e file it errors out as being old
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
XxKOLOHExX said:
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
Click to expand...
Click to collapse
dude! I noticed this also this morning. I am rooted(using setcpu and root explorer just fine) but in hboot it says s=on. I was also wanting to flash the stock .img and start fresh. thought I was the only one having this problem. tried everything you did and got the same results.
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
How is the progress on fixing your phone?
jdkoren said:
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
Click to expand...
Click to collapse
currently on Evil D mTGB v1.0, Faux 0.0.7 CFS lv leak kernel. everything works fine, no FC's or anything. just having the same issues as XxKOLOHExX. I really have no idea how it turned on by itself, I dont remember doing anything out of the ordinary
I was trying to get back to stock from the rom i was on. (MIUI) and when I used the stock .img though the bootloader it went all good till it rebooted, then it said failed because the file was old and now I am stuck with s-on and I don't know how to turn it off
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
PermROOT said:
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
Click to expand...
Click to collapse
It flashed the bootloader when I flashed the PD15IMG.zip, it just stop when I did the whole procedure. Nope never flashed an Engineer Bootloader. I used theunlockr.com sites method
I tried that, it uziped then tried to flash the radio then just went back to the original menu for the bootloader
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
PermROOT said:
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
Click to expand...
Click to collapse
Yeah I know that, I Was trying to go back to stock everything using the unrooting method(PD15IMG.zip). Using this file I was able to get through the first step and it rebooted, then it went back to bootloader and now it won't take the PD15IMG.zip saying that it is an older file. Yes I am one of the devs, That's why before posting I tried everything I could think of, gfree, old unrooting methods, etc. I didn't use a dump lol I'm not that noobish haha
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
Thank you so much for the help
PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
lol sorry for the extra work, just dont wanna have the chance of bricking my phone but like XxKOLOHExX I wanted to revert back to stock from mTGB using the stock PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M_release_155771_signed. everything he described is happening to me also, step by step. I rooted with the visionary+ and permroot method(unlockr). I did download and flash the 26.08.04.30 radio. heres what I see in hboot
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.08.04.30_M3
eMMC-boot
Sep 27 2010, 11:12:59
so what youre saying is that we should try flashing the stock radio first, wipe the whole phone(including sdcard?), then flash the stock PD15IMG? Ill give it a shot real quick, thanks
*edit* hboot wont even let me flash the stock radio, itll say checking but wont actually let me update it
Well clarknick27 the problem here is that root.sh to gain PermROOT via VISIONary+ just push the 0.85.2007 eng hboot and giving temporary S=OFF, the true security flag as we know it is controlled in the radio. So when you try to revert back using stock PD15IMG (rom/radio) it reverted back to the stock 0.86.0000 hboot thus turning on the security flag on.
What you all should have done is reverted back same way you installed it. Which would have been first use PD15IMG.zip (stock radio) and then use stock PD15IMG.zip (radio/rom). I still need some sleep lol I just wokeup after sleeping 2hours.
The MT4G I tested on I rooted it via VISIONary+ and then flashed GB Leak rom not the PD15IMG.zip (leak radio/rom) which contained the 0.89.0005 hboot. So after flashing stock radio PD15IMG.zip (radio 26.03.02.26_M) I was able to flash stock PD15IMG.zip (rom/radio) without problem. Which is same as I suspected even after S=ON due to same version radio no problem. If I had newer radio after that point it would be locked out. Let me go to sleep and wakeup and ill see what happens from there. As I have clean MT4G ill have to reroot it first.
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
PermROOT said:
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
Click to expand...
Click to collapse
1) currently running Evil D's mTGB v1.0 rom with Faux's 0.0.7 CFS LV leak kernel. tried rooting with visionary and terminal first, no success. I then tried out the gfree method, and got "Attempting to power cycle eMMC...failed. Module failed to load: No such file or directory."
2) I installed Visionary using Astro file manager, then run Visionary. I click on "temproot now" and it starts, but then the screen goes black and doesnt do anything. I have let it sit on the black screen for well over 15mins before with no luck. I can click on "attempt to permroot" and it will ask for permissions and reboot and everything. my s=on but I still have root access and 0.86.000 bootloader. this is what I see using terminal before rebooting to see if s=off
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
PermROOT said:
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
Click to expand...
Click to collapse
thanks for taking the time to help out, Ill give it a shot
*edit* just tried pushing the eng bootloader through adb and it didnt stick or flash, rebooted into hboot and it still says 0.86.0000, s=on, 26.08.04.30_M3 radio