Related
To senior Mytouch 4gers:
Let's just start recommending the root.sh/visionary method to beginners and people who haven't rooted yet. It might not be the rooting method that causes issues but so far it looks like it plays a role in it. only gfree rooters have had this issue so far, so let's stay on the safe side, huh? just link this thread: http://forum.xda-developers.com/showthread.php?t=834225 and we can notify people later on about whether or not they should use gfree, as it's easy to use even after the root.sh method.
UPDATE:
It turns out that the rooting method may have little to no effect on this issue. Please read the bottom past the "update" title
Most of my data here will be pulled from http://forum.xda-developers.com/showthread.php?t=1074922 and similar threads.
Many of you probably have already read about this, but it has been becoming more and more common for people to get errors in recovery saying that certain partitions cannot be mounted, usually data and/or cache. The issue is that they cannot be re-formatted in recovery because the recovery partition is messed up as well.
Some people escape this using PD15IMG, but about 50% hit another error - Fail-PU in hboot when trying to use this. The only recovery here is available if you have the engineering hboot (Which at this point i would highly recommend you flash). without it, the phone is effectively bricked (I know, i know, not really bricked if you can get to hboot, but it's to the point that there is no recovery and the phone is unusable.)
We have narrowed it down to this: these errors only happen to people who used the gfree method to root. one (convincing) theory was posted in the previously linked thread by xdviper:
xdviper said:
Alright well I've been reading logs from G2_Root channel from April 26th and so on, and it looks like the G2 has two different types of the emmc chip. Gfree powers off this chip and then initializes the chip again in order to get around the write protection. I remember before we had root access on the G2 (before I traded for a mytouch) I would lurk around the irc channel and read progress. I remember having to get the chip to power on in order to get around the write protection.
Now it looks like while the phone is being used, or booting up and or trying tto read or write from emmc the chip suddenly dies. This is what causes us to get force closes, freezes and not being able to get past the splash screen and also explains the recovery not being able to mount partitions.
We're going to need people to join in the G2 channel preferably ones who still have their defective phones to get some data off it.
Again, this is a very vague summary of what I've been able to read off the irc logs.
Why the G2? Because we're using the same gfree method to root our phones and with our phones dying it makes sense.
I think, they have already ruled out recovery and the Eng hboot to be culprit but this is just too early in the game to determine.
Here's a thread from the G2 side, if anyone still has this problem with their cache not being to mount please check out post #13.
I'll look.around more and see what I find from the G2 side.
http://forum.xda-developers.com/showthread.php?t=1039504
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
In addition to (Hopefully) discovering the issue, we believe we have something you can do to lower your chances of being afflicted by this issue. IF you use the gfree method, reflash recovery a couple times, and hopefully it will work correctly. If you are not in need of a sim unlock, carrier unlock, whatever gfree does, use the visionary method with root.sh. At this point there are no documented cases of these issues happening with users that used that method.
Root.sh method:
http://forum.xda-developers.com/showthread.php?t=834225
Thanks for reading, have fun and be safe!
Mod: I feel it would be beneficial if this thread was stickied.
UPDATE
It turns out that the rooting method may have little to no effect having this issue, in a quote from Guhl99:
guhl99 said:
Hi !
After analyzing this issue a lot and also discussing this with scotty2 on #G2ROOT yesterday I would like to say that we can see no way how gfree could be causing this issue that effects the G2/DZ/DHD/MT4G.
We see that it seems to effect people that used gfree to radio S-OFF and root the phone but this is very likely only an statistical effect as gfree is the most used rooting method now.
The only thing that we know fur sure (or at least with a very very high probability) is that only emmc chips with the name M4G2DE are effected. You can find the name of your emmc chip by using the following command (in a terminal or adb shell):
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
To be sure that you really are effected by the emmc issue (and not other partition corruption issues that show similar symptoms) you have to look at the kernel messages when booted to clockworkmod recovery. Do to this boot the phone into recovery and then (in and adb shell) issue the following command:
Code:
cat /proc/kmsg | grep mmc0
or
Code:
dmesg | grep mmc0
If you see output like (not necessarily in this order) :
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
then you are effected by this issue.
Basically the emmc chip does not initialize any more after the first attempt to access it in write mode.
Based on our current knowledge this is a hardware issue and can not be cured. We will keep investigating this issue and welcome everybody to discuss it on #G2ROOT.
Have fun - Guhl
Click to expand...
Click to collapse
I looks like M4G2DE is the bad one and SEMO4G is the good one. We don't have any cases of other ones, but please post yours if it is different. Keep in mind we still aren't 100% sure about this being the cause, but it's very probable, as a logcat on booting in to recovery shows this chip dying. Also be aware that this is a hardware issue, no software can fix this. you have the bad one or you don't.
Also, it would be nice if when you post you would list these things:
1. what method of rooting you used
2. which version of hboot do you have
3. which emmc chip serial do you have
4. have you encountered this issue before
Let's not throw away the idea that the rooting method still plays a big role in this issue! please post any information you have about the partition errors and FAIL-PU errors! All information is welcomed!
If we're still not sure why it's happening, then how do we know reflashing recovery a couple times will fix it? The cause is still unknown, right? Cuz I've gfree'd several Glaciers and haven't encountered this problem.
i personally do not trust auto-rooting. I did the visionary and root.sh way of rooting and have engineering bootloader and have not had a single issue.
Wow lucky I read this. I need to SIM unlock my phone. Should I wait till this issue has been figured out? I am afraid I might brick my MyTouch 4G. I am not with T-Mobile and also not in the US, bought the phone off ebay, so can't really call them to get unlock code. Do i have any other options?
dacquesta1 said:
i personally do not trust auto-rooting. I did the visionary and root.sh way of rooting and have engineering bootloader and have not had a single issue.
Click to expand...
Click to collapse
Same here. Root.sh all the way.
Here is the method I used. Very similar to grankin's linked to in the OP, but slightly more simple: http://forum.xda-developers.com/showthread.php?t=858021. Follow that and you'll be fine.
Good to know! I rooted via the root sh method and have been considering doing gfree, not now!
Sent from my MyTouch4G running RoyalGinger 2.0
dacquesta1 said:
i personally do not trust auto-rooting. I did the visionary and root.sh way of rooting and have engineering bootloader and have not had a single issue.
Click to expand...
Click to collapse
So thats a no on auto rooting. for me.
clem2595 said:
So thats a no on auto rooting. for me.
Click to expand...
Click to collapse
Unless you need SIM unlock I would highly recommend the root . sh method. Go to theunlockr.com there is a very simple video guide in the "how to's" section.
Sent from my MyTouch4G running RoyalGinger 2.0
Towle said:
Unless you need SIM unlock or are planning on flashing radios I would highly recommend the root . sh method. Go to theunlockr.com there is a very simple video guide in the "how to's" section.
Click to expand...
Click to collapse
I know that the root.sh method isn't "true" S-OFF and that the radio's security flag is still technically "on", but does that mean you aren't able to flash new radios after rooting that way?
I didn't use gfree, just root.sh, and I've flashed 4 radios no problem...
Sent from my HTC Vision using XDA App
No issue flashing radios here. Never a single issue flashing roms radios recoveries anything.
Sent from my HTC Panache using XDA Premium App
TeeJay3800 said:
I know that the root.sh method isn't "true" S-OFF and that the radio's security flag is still technically "on", but does that mean you aren't able to flash new radios after rooting that way?
Click to expand...
Click to collapse
I've flashed a couple radios and I rooted the visionary/root.sh method. If I'm not supposed to be able to, I guess I got lucky.
Sent from my HTC Glacier using XDA App
It's still not clear whether you're "supposed" to be able to flash radios or not, but it seems to be working for everyone that has rooted with root.sh. I'll just blame you guys if I brick my phone.
Sorry very bad wording on my part.
I guess I should have said radio s-off
Onefast said:
I didn't use gfree, just root.sh, and I've flashed 4 radios no problem...
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my MyTouch4G running RoyalGinger 2.0
rooting the visionary method gives radio s=off...mine has been like that since i rooted and i have flashed all four radios and countless ROMs
dacquesta1 said:
rooting the visionary method gives radio s=off...mine has been like that since i rooted and i have flashed all four radios and countless ROMs
Click to expand...
Click to collapse
Do I have the fastboot commands correct here?
I also used the unlocker how to and worked great. Uses visonary and root. sh
Reply via MT4G Royal Ginger 2.0 on the #1 android forum app- XDA
TeeJay3800 said:
Do I have the fastboot commands correct here?
Click to expand...
Click to collapse
truthfully i do not know. i don't use command lines to flash anything. i just put radio images on the root of my sd card and go into the bootloader and flash it there and i flash roms from recovery...never any issues.
I have gotten this error for the second time on the same device...the first time I recovered by flashing a 2.x.x.x CWM in EBL and the formating cache in the old recovery, reflashing CWM 3.0.2.4 in EBL and I was all set after restoring a NANDroid. BUt the second I got the error I have tired everything so far and nothing gets it to go away, I cant even flash the old CWM in EBL I get an error in adb
Hey to all of you that are saying we don't really know the solution, im aware of that. The reflashing of recovery is merely the most we can do at this point. it won't save you, but it's a theory that can't hurt to try.
Sent from my HTC Glacier using XDA App
I own a T-mobile G2 and it has recently had a problem with the touch screen. I would not like to return it and get a new one because I am still under the warranty but i must unroot it first. I have tried to follow a few other posts about how to do this but none of them have worked. Now because of that i am still in cyanogen mod 7 but i have S-on. Could anyone lead me in the right direction
If you would, please post your hboot info so we can see where you are at and advise accordingly.
Sent from my T-Mobile G2 using Tapatalk
Got your back buddy. I just did this today WITH A BLACK SCREEN. I couldn't see anything going on, but it's THAT easy.
theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision
You only need to do Step III. Ignore the hex editing part because if you do step II, you'll notice that Cyanogenmod has edited it already so you can easily just drop the zip file onto your sdcard and run it from your Pwr + Volume Down menu. Very very simple if you're running CM7.
Ask if you have any questions, but it really shouldn't matter...it was a joke (after I spent nearly three days researching how to install ADB for a G2 -- It's very, very complicated and unnecessary)
nik.the said:
Got your back buddy. I just did this today WITH A BLACK SCREEN. I couldn't see anything going on, but it's THAT easy.
theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision
You only need to do Step III. Ignore the hex editing part because if you do step II, you'll notice that Cyanogenmod has edited it already so you can easily just drop the zip file onto your sdcard and run it from your Pwr + Volume Down menu. Very very simple if you're running CM7.
Ask if you have any questions, but it really shouldn't matter...it was a joke (after I spent nearly three days researching how to install ADB for a G2 -- It's very, very complicated and unnecessary)
Click to expand...
Click to collapse
Link isn't working for me, is it working for anyone?
nik.the said:
Got your back buddy. I just did this today WITH A BLACK SCREEN. I couldn't see anything going on, but it's THAT easy.
theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision
You only need to do Step III. Ignore the hex editing part because if you do step II, you'll notice that Cyanogenmod has edited it already so you can easily just drop the zip file onto your sdcard and run it from your Pwr + Volume Down menu. Very very simple if you're running CM7.
Ask if you have any questions, but it really shouldn't matter...it was a joke (after I spent nearly three days researching how to install ADB for a G2 -- It's very, very complicated and unnecessary)
Click to expand...
Click to collapse
I'm in the exact same position at the moment, I have a black screen
nik.the could you please tell me the button combination I need to press once I put the stock rom on the SD root and turned the phone on (I know i got to hold vol down and power but that's it :S)
On another not it was such a painful process to root this Desire Z and with my past 3 HTC's needing repair I think I'll look at another brand after the life of this repaired phone ends.. this forum and dev support is the best thing HTC has going for it at the moment.
I went through that process (had to go through step II as well even though I was on CM), but it failed:
Upgrade process completed - stock rom got installed, bootscreen changed, etc, but i still have S-Off.
I really need to send the phone off for repairs today, any advice would be greatly appreciated...
(also not sure if i used gfree or visionary, but inclined to say i used this guide (says it uses visionary/gfree):
http://forum.xda-developers.com/showthread.php?t=928160
mapin0518 said:
Link isn't working for me, is it working for anyone?
Click to expand...
Click to collapse
The link works for me.
I used this method for the first time I had to return a G2 to T-mo. Worked for me.
iokke said:
I went through that process (had to go through step II as well even though I was on CM), but it failed:
Upgrade process completed - stock rom got installed, bootscreen changed, etc, but i still have S-Off.
I really need to send the phone off for repairs today, any advice would be greatly appreciated...
(also not sure if i used gfree or visionary, but inclined to say i used this guide (says it uses visionary/gfree):
http://forum.xda-developers.com/showthread.php?t=928160
Click to expand...
Click to collapse
I also still have S-off. I would also like an answer to this problem because I'll have to send this back within the week. I think I used Visionary first to perm root it then I used Gfree to unlock everything else.
From what i've read, T-Mobile doesn't seem to care that you have S-off, either that or they don't check. Many people have mentioned that they sent back unrooted phones still showing S-off and did not get charged for returning a rooted device.
I hope that's true. It gets a little tiring doing things like this and they never work out like I think they will. This phone is unrooted as far as I'm concerned. I can't do anything on it but I don't know if that is because it is basically unrooted or if it is because my power button is effed. When I'm in the bootloader can I not scroll down to recovery when the phone is unrooted?
nivlac978 said:
I hope that's true. It gets a little tiring doing things like this and they never work out like I think they will. This phone is unrooted as far as I'm concerned. I can't do anything on it but I don't know if that is because it is basically unrooted or if it is because my power button is effed. When I'm in the bootloader can I not scroll down to recovery when the phone is unrooted?
Click to expand...
Click to collapse
i returned my wifes g2 to tmo last month. it was rooted, and the speaker quit working. just factory wiped and returned it. no big deal.
Well that's good news. I feel a little better but I'll still be stressing about that for a few weeks. lol
ok so for any1 on here need to get s-off back to s-on here is the stock part7back up
well sry can upload a .bin so if anyone know a way for me to getr it to you plz let me kniow
I think i still have the partition 7 backup. Do I just use gfree to get that back in there?
Sent from my T-Mobile G2 using XDA App
Download the stock pc10img.zip and do it that way the use visionary to temp then use the part7back up to get s-on back and BAM back to stock s-on
And next time, it may behoove you to search. It would save you some time and avoid waiting for answers.
All of these ppl have asked this same question. I am sure you can find an answer if you have no already.
Yea u can search but why do that when the fourms are full of crap....better off asking.....just look at my last post that will fix ur prob guy
kitila said:
Yea u can search but why do that when the fourms are full of crap....better off asking.....just look at my last post that will fix ur prob guy
Click to expand...
Click to collapse
I'll give that a shot thanks. And of course I searched but found a lot of conflicting information and old information. Best thing to do on a forum if you are unsure of something is to ask. Multiple "how too guides" doesn't always cut it.
Sent from my T-Mobile G2 using XDA App
You can use gfree to s-off. There are detailed instructions in the wiki. Will need to be done on froyo so you can use the temp shell root.
nik.the said:
Got your back buddy. I just did this today WITH A BLACK SCREEN. I couldn't see anything going on, but it's THAT easy.
theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision
You only need to do Step III. Ignore the hex editing part because if you do step II, you'll notice that Cyanogenmod has edited it already so you can easily just drop the zip file onto your sdcard and run it from your Pwr + Volume Down menu. Very very simple if you're running CM7.
Ask if you have any questions, but it really shouldn't matter...it was a joke (after I spent nearly three days researching how to install ADB for a G2 -- It's very, very complicated and unnecessary)
Click to expand...
Click to collapse
i did exactly as said, but im still "s-off", i need to get s-on so i could return mine for a warranty swap, when i did the this process, shortly after i got 3 up dates, i installed them all hoping it will turn my s-on like some people where saying on other post, but no luck. now im 2.3.4 unrooted but still "s-off" ive been searching but there are different methods and some older post, not sure if i could try another one since i unrooted it using this method, any help please THANKS
ok let me just preface this by saying that i am a complete moron and didn't make a nandroid back up. i am new to this stuf obviously and didnt research enough before i dove in.
also this is referring to the htc on v cdma on virgin mobile.
so i was able to successfully unlock and root the phone. bootloader says unlocked and root checker from the market said i had full root access.
i installed the team win recovery on the phone. the first rom i flashed was the cdma pacman rom from here. i did a full wipe and flashed the rom, and then flashed the kernel from said rom via fastboot on my pc. upon firing it up, it boots and gets through the boot animation and into the OS. but after about 10 seconds my service shuts off (it shows a little R above my reception bars) and the phone reboots. just does this over and over.
so i thought maybe it was the ROM so i tried AOKP jellybean. same issue.
any idea what i did wrong here? thanks in advance.
lol, i had the same problem as you. It happens because of the OTA update or radio version, try using this:
http://forum.xda-developers.com/showthread.php?t=2018518
I just followed Solution 1 and it worked for me, I was originally on CWM but moved to TWRP cause it's more convenient.
After using the RUU you'll be back to bone-stock and will have to unlock the bootloader and all that fun stuff all over again that's if you use solution 1; however, atleast you'll be able to get the stock-rom backed up again for just-in-case. Skip OTA updates, and then proceed to recover and then start rom flashing/fastbooting kernel and all that fun stuff.
reID_entify said:
lol, i had the same problem as you. It happens because of the OTA update or radio version, try using this:
http://forum.xda-developers.com/showthread.php?t=2018518
I just followed Solution 1 and it worked for me, I was originally on CWM but moved to TWRP cause it's more convenient.
After using the RUU you'll be back to bone-stock and will have to unlock the bootloader and all that fun stuff all over again that's if you use solution 1; however, atleast you'll be able to get the stock-rom backed up again for just-in-case. Skip OTA updates, and then proceed to recover and then start rom flashing/fastbooting kernel and all that fun stuff.
Click to expand...
Click to collapse
awesome thank you so much. i am slightly confused on which one to download though. i am assuming it is this one here, the only one i see with sprint/vm branding. RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00... i'll give it a shot
yea that's the one, it's an executable file, just make sure you follow the directions for RUU.
reID_entify said:
yea that's the one, it's an executable file, just make sure you follow the directions for RUU.
Click to expand...
Click to collapse
worked like a charm! thanks so much!!!
now to try putting a new rom on here again lol....
For future references I suggest not updating the OTA since its known to cause a lot of problems due to radio discrepancies. I'm glad you were able to fix yours though.
Sent from my Full Android on PrimoC using xda premium
Hi everybody, I was thinking whether to open new "story" or not and I thought I can do it by myself..but..I did everything I could, I have read hundreds of forums..some things totally confused me and some simply I don't understand..so however I decided to open new thread because I really need professional help here.
Here is the story,
I've bought used HTC DHD before two days with an custom rom android 4.2.2 but WI-FI not worked and also camera not worked very well (when I take a shot phone turns off). i have tried few roms in hope that will fix the problem (PACman v23, CM10.1 and JT 4.2.2 - and still on JT) but nothing. In bootloader says Unlocked but security is damn ON. So, I worked two whole fckin day without success. I have tried many tools, guides etc but it simply won't make S-OFF. Also I've tried to flash to few stock RUU roms to do a downgrade but every time when try I'm getting some errors (140, 150, 170 or even unknown error xD). I really don't know what to do anymore and because I'm pissed off I came here. I love this phone and I won't sell it third day already. I gave last money for this smartphone..I won't money back..I won't new phone..I just want this to be working device. On pic you can see what I already tried..
So please, be patient and take your time to solve this **** together.
Come on guys, I know this can be fixed. I need just little of your time. and thank you very much in advance.
NO idea why you so desperately want S-OFF in the first place as you can flash custom ROMS without it and there is no other way you can fix wifi on software level (so most probably it's a hardware problem), but anyone have access to search in the upper right corner if you wish.
As for the phone shutting down when taking photos, it's a common problem and is thought to be related to aging battery, but you have a great chance of fixing(compensating) it by increasing CPU voltage a couple of notches. Install CPU Master and increase the mV of corresponding maximum frequency used, it should be 1Ghz to look at if not overclocked, try to increse it by 50mV
You are unlocked and still s-on so, as with every one who has issues like yours, you need to flash the boot.IMG via fastboot from the ROM you want to install, after you've installed the rom.
I suggest switching to SVHD by mygamers, every thing works, its super smooth and is great on battery too.
P.s. unless you REALLY really need the advanced functions of s-off, I wouldn't worry to much about it.
"Some" advantages to unlocked bootloader and s-off are:
Flash new Roms direct with out having to flash boot.img
Restore nandroids that are different from current installed rom easier
Flash radios
Change splash screen (you may only see it when you turn on phone, but it can be awesome thing to show off a bit)
Sent from my GT-I9505 using xda app-developers app
First, why do you need S-Off? You can flash ROMs without S-Off, and S-Off won't fix your WiFi problems. It's not clear whether you're successfully flashing ROMs right now, but you can. You do need to flash the ROM zip's boot.img from fastboot each time after you flash s ROM from recovery.
Second, please bump a thread only once every 24 hours per the forum rules.
It's pretty damn clear that he have tried other ROMS.
dante.24 said:
i have tried few roms in hope that will fix the problem (PACman v23, CM10.1 and JT 4.2.2 - and still on JT)
Click to expand...
Click to collapse
-SmOgER said:
It's pretty damn clear that he have tried other ROMS.
Click to expand...
Click to collapse
But he finishes that line with "but nothing." Given the number of "flash the boot.img" posts I've had to write lately, I was wondering if that meant he managed to get them to boot or not.
Sorry guys that I did't mentioned before but mainly what I want to do is to bring back stock rom but I can't..someone said that I need S-OFF for that, I heard that when you flash stock rom can fix wi-fi and camera and then if you want can install new custom rom after. About damaged hardware, everything is possible. I was in service shop and guy there said that hardware is modem in essence that controling wi-fi, GSM, bluetooth and GPS. Maybe I understood him wrong. But my BL and GSM working just fine. I have to try new step-by-step tutorial, I'll be back soon.
dante.24 said:
Sorry guys that I did't mentioned before but mainly what I want to do is to bring back stock rom but I can't..someone said that I need S-OFF for that, I heard that when you flash stock rom can fix wi-fi and camera and then if you want can install new custom rom after. About damaged hardware, everything is possible. I was in service shop and guy there said that hardware is modem in essence that controling wi-fi, GSM, bluetooth and GPS. Maybe I understood him wrong. But my BL and GSM working just fine. I have to try new step-by-step tutorial, I'll be back soon.
Click to expand...
Click to collapse
You don't need to get S-Off. Just relock your bootloader with fastboot and run the RUU executable from your computer while the phone's connected to it.
bananagranola said:
But he finishes that line with "but nothing." Given the number of "flash the boot.img" posts I've had to write lately, I was wondering if that meant he managed to get them to boot or not.
Click to expand...
Click to collapse
OK, let's clear this. Every rom I've tried worked but wi-fi not again, camera is little stable in JT 4.2.2. Only rom that not worked was JT 4.3 beta 3. Installed very well but when it boots it stays on splash screen forever.
bananagranola said:
You don't need to get S-Off. Just relock your bootloader with fastboot and run the RUU executable from your computer while the phone's connected to it.
Click to expand...
Click to collapse
OK, I'll try it..
Locked bootloader as you said, started exe from PC and I got error 131 "CUSTOMER ID ERROR"..what's that??
You need to find a RUU compatible with your phone's region.
bananagranola said:
You need to find a RUU compatible with your phone's region.
Click to expand...
Click to collapse
How can I know that man, when I try to flash RUU it says "would you like to update from 3.13.000 to 3.13.405.12"..something like that..Ive already tried two stock roms.
Edit: I've tried WWE and ARA RUUs, do I need to try US and UK versions too??
dante.24 said:
How can I know that man, when I try to flash RUU it says "would you like to update from 3.13.000 to 3.13.405.12"..something like that..Ive already tried two stock roms.
Edit: I've tried WWE and ARA RUUs, do I need to try US and UK versions too??
Click to expand...
Click to collapse
You could make a goldcard to run any RUU, or you could try the US or UK RUUs.
-SmOgER said:
It's pretty damn clear that he have tried other ROMS.
Click to expand...
Click to collapse
Excuse me, but its "pretty damn clear" that only jellybean roms have been tried!
Why are you getting so agro (agrovated for non Aussie readers)) at the mention of trying to use something other than jellybean?
Only trying to help someone out, mate, have you got issues or you got some reason for hating!
Sent from my GT-I9505 using xda app-developers app
umm if your stuck on splash screen you haven't flashed the kernel. Extract the zip, then place the boot.img into your adb folder. Reboot your phone into hboot then fastboot. Now go to your adb folder type in fastboot flash boot boot.img from cmd.
If that doesn't work to achieve s-off on newer versions of android is 1) Make a goldcard 2) Downgrade with a ruu 3) Get root exploit 4) Get s-off exploit (This was back in 2010 so I don't know if the procedure changed but I s-offed with this. It's probably easier since its 2013:silly
For future reference, Unlocked bootloader means the boot.img is restricted from recovery YOU need to flash kernels via fastboot with Unlocked Bootloader, S-OFF means nothing is restricted apart from splash image, ENG-Soff is engineering mode is same as s-off but with a Eng tag and splash screen is changeable.
Click to expand...
Click to collapse
ranger4740 said:
Excuse me, but its "pretty damn clear" that only jellybean roms have been tried!
Why are you getting so agro (agrovated for non Aussie readers)) at the mention of trying to use something other than jellybean?
Only trying to help someone out, mate, have you got issues or you got some reason for hating!
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
First of all there was no any hate nor any of this "agro" of yours lol.
Secondly, none of the mentioned JB ROMS have wifi issues, so there is really no point in wasting time and trying every available ROM.
Cheers and I hope you now got it, we all learn from our mistakes, don't beat yourself up too much. :laugh:
Thanks dude, I'll try it. I have GC tool but problem is this site revskills are down and can't get .img file. Any alternative for this?
-SmOgER said:
First of all there was no any hate nor any of this "agro" of yours lol.
Secondly, none of the mentioned JB ROMS have wifi issues, so there is really no point in wasting time and trying every available ROM.
Cheers and I hope you now got it, we all learn from our mistakes, don't beat yourself up too much. :laugh:
Click to expand...
Click to collapse
I must say, your a total gentleman to clear that up, it is my mistake to believe we are not playing nice and trying to help each other out here, without deliberately flaming or being just simply malice towards fellow xda members...
Don't worry I won't beat myself up to the point I need hospital admission even though that is where I am right now.
Cheers my xda friend I got it now! :thumbup:
Sent from my GT-I9505 using xda app-developers app
Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.