I followed the guide at http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod three times carefully and every single step appeared to work. On the final reboot it simply sits there on the MyTouch 3G green screen and doesn't go any further. I left the phone overnight so I know its not a time issue.
My SIM card requires a custom APN to access the internet so if the ROM is trying to do some internet access stuff at that point it will get stuck.
On IRC they asked for a logcat but while I have installed ADB on Vista so far I haven't been able to get it to work, "adb devices" is always blank. I'm going to try adb on linux.
Is there a "known good" version of cyanogen that will definitely work using this method that I should try? Anything else I can do to move past this green screen? Phone is not bricked recovery flasher works perfectly.
Phone: T-Mobile MyTouch 3g purchased outright in the US. Previously upgraded all the way up to 1.6.1 on T-Mobile before downgrading
Cyanogen: 4.2.8
Recovery: Recovery Flasher 1.4 + JF
Thanks very much for your help.
I updated to 4.2.8.1 and still no dice.
Here is the logcat:
http://pastebin.com/f73625a72
W/zipro ( 120): Size mismatch on inflated file (2435741 vs 2437468)
W/zipro ( 120): Size mismatch on inflated file (2435741 vs 2437468)
W/ResourceType( 120): Unable to get buffer of resource asset file
W/dalvikvm( 120): Exception Landroid/content/res/Resources$NotFoundException; thrown during Landroid/text/AutoText;.<clinit>
E/Zygote ( 120): Error preloading android.text.AutoText.
E/Zygote ( 120): java.lang.ExceptionInInitializerError
The problem was a corrupt framework-res.apk file .
To fix:
1. Boot the phone (let it get stuck in its screen)
2. ./adb remount
3. ./adb push ~/download/system/framework/framework-res.apk /system/framework/framework-res.apk
(where this is a known good unzip'd copy of cyanogen)
I can't believe its working, so happy right now
idk what to do
so i did the same thing trying to load the cyanogen or whatever it is and i am getting the green screen now it wont even load or anything what do i need to do to fix this can you please help me i saw you posted a fix but that makes no sense to me.. can you give me a step by step
dudeusmc said:
so i did the same thing trying to load the cyanogen or whatever it is and i am getting the green screen now it wont even load or anything what do i need to do to fix this can you please help me i saw you posted a fix but that makes no sense to me.. can you give me a step by step
Click to expand...
Click to collapse
Firstly install the android SDK, you can get it here:
http://developer.android.com/sdk/index.html
There are lots of guides.
Then boot you phone and use adb logcat to look at what its doing with the green screen. See whether you appear to be having the same problem as me.
If it is the same problem, then the adb commands I posted should work for you.
If its not post your logcat output and maybe someone can help.
I just tried 4.2.11.1 and the problem file instead was:
/system/framework/framework.jar
SDK?
Sorry i do not know much about all this, that is probably my first problem lol.. what is an SDK?
dudeusmc said:
Sorry i do not know much about all this, that is probably my first problem lol.. what is an SDK?
Click to expand...
Click to collapse
Make sure you are flashing the correct version for your phone. I accidentally flashed the 32A version on my 32B MyTouch and it froze at the screen. Since I am very good at trouble shooting I figured my problem out fast.
I have searched google far and wide, found a few cases of similar issues but haven't found a solution yet. Got my T-mobile g2 /DZ about 2 months ago, love the hardware and the form factor, but I cannot stand stock froyo. First of all:
Phone build/firmware (?) number is: 1.22.531.8
Release keys: cl277427
I initially tried rooting the phone with visionary r14, which gave me a temp root, then rebooted when I tried perm-root. Ever since then, the program hangs when trying to even temp root (I have tried visionary r11,12,13, and 14, as well as uninstalling and reinstalling countless times [not to mention downloading from different sources]).
After a bit of searching, decided to try rage method - again it didnt work (terminal emulator > /data/local/tmp/rage - permission denied) no matter how many times I tried it.
Tried rage method with gfree (both .02 and .04), which is where I had the most success. I managed to get s-off, but still no superuser access. The problem occurs when I enter the code /data/local/tmp/root
described in this page: http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF where it tells you how to 'lock in' the root.
After entering the '/data/local/tmp/root' code, I get an error message that reads something like:
mkdir failed for /system/xbin/, File exists
cp: can't stat `/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
I have checked, double-checked, and triple-checked that I have pushed busybox etc correctly, and they definitely write to the folder as I am not getting any error messages in CMD.
I would greatly appreciate anyone who can give me a straight answer as to what to look for (somebody said you can't have a file/folder on SD card called 'su' so I have checked that). This is driving me crazy - I bought the G2 thinking froyo would be so much better than Symbian/Motoblur, but I am really disappointed. Even Launcherpro etc are pretty lame compared to some of the custom roms out there.
Please help me!
Alternatively, seeing as I have s-off, any way to flash a rom without superuser? Sorry for the noob question
s-off and gfree ? i don't have g2 version, only desire z. but you can always flash clockwork recovery from adb fastboot. using that, you can switch to other ROM or backup the current one...
fajarep said:
s-off and gfree ? i don't have g2 version, only desire z. but you can always flash clockwork recovery from adb fastboot. using that, you can switch to other ROM or backup the current one...
Click to expand...
Click to collapse
Can you give me a bit more detail? About to try and flash a pre-rooted modaco rom. Will probably have to wipe the phone so if it doesnt work I will try gfree again on the wiped phone
Bumping bump
Anybody?...
Still needing help on this
Hey folks
Small problem here:
Every time I attempt to fix permissions using ROM manager I get an error message:
'an error occurred while trying to run privileged commands'
When I type 'su' into terminal, superuser wants to grant root access so I guess that I'm rooted properly.
It's not a huge deal but it is kinda annoying
Running stock ICS on gt19020 UK 3G version.
Thanks for your time in reading this,
All the best
casmael said:
Hey folks
Small problem here:
Every time I attempt to fix permissions using ROM manager I get an error message:
'an error occurred while trying to run privileged commands'
When I type 'su' into terminal, superuser wants to grant root access so I guess that I'm rooted properly.
It's not a huge deal but it is kinda annoying
Running stock ICS on gt19020 UK 3G version.
Thanks for your time in reading this,
All the best
Click to expand...
Click to collapse
Fix permissions in recovery!
I've read the dedicated thread on rooting the TF700t with DebugfsRoot_v1.9 (http://forum.xda-developers.com/showthread.php?t=1706588&page=48).
I did successfully root a TF700t with 9_4_5_22.
Now I tried the same method after upgrading another TF700t from stock to 9_4_5_26.
Everything works fine during rooting (I've tried both manual and automated DebugfsRoot 1.9) with the following exceptions:
1. during the 3rd stage of rooting, I get
/system/bin/sh: /system/xbin/su: not executable: magic 7F45
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
I tried both under XP and 7/32 on the same device, no errors but root does not seem to be active. Between rooting attempts, I restored stock ROM.
Other details:
Asus USB drivers installed (off Asus website)
Asus synch is disabled and prevented from launching.
Security/Unknown sources is checked.
Developer options / USB debugging is ON/checked.
What do you think goes wrong?
Any help is appreciated. Thx
the same..
I have nearly the same problem...
I have updated my rooted .21 to .26, then unlocked it and as it seems have lost root. I dont really know if it happened afted updating or afted unlocking...
None of my R-applications can get root, and so on...
I've tried to use the same method i used to get root on .21 and got this:
Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs:
debugfs: debugfs: Allocated inode: 1469
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
And still no root...
What am i doing wrong? What to do next?
Thanks!
Is it a superuser problem?
EnginesRun said:
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
Any help is appreciated. Thx
Click to expand...
Click to collapse
Can't help yet but I am having a similar problem with SU; its presence suggest I have root but it denies everyone else SU permissions...
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
alienedd said:
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
Click to expand...
Click to collapse
nope. doesnt help in my case..
---------- Post added at 10:17 AM ---------- Previous post was at 09:37 AM ----------
ok, i've solved my problem.
the idea mentioned by alienedd helped me to see that i could have a working root but faulty superuser app.
so i started with installing it from market.
then i ran DebugfsRoot_v1.9.
till it got to this point:
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(m ount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),30 03(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
then i have cleared all the data held by superuser app through settings\apps, stopped it and uninstalled.
after that i continued with the script and it installed me superuser app again.
after installing i've launched it and then ckecked my root-needed apps. they are ok now.
Ahhh, yeah. Read about that in the DebugFS thread that sometimes one needs to uninstall superuser then reinstall for it to run properly. Didn't think about that. Glad that its all working now for yas.
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
henbone11 said:
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
Click to expand...
Click to collapse
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
alienedd said:
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
Click to expand...
Click to collapse
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
henbone11 said:
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
Click to expand...
Click to collapse
Yeah, I understand. Um, I know I've repeated this several other times but I don't see it in your list of things you've done. Were you able to open up the superuser application? It seems that if it opens, you have root, and in some cases might not work until it is opened. It's both fortunate and unfortunate that I did not encounter many problems while rooting so my experience with possible errors isn't that expansive. However, you've run the package(s) completely so it's not a driver issue and you can adb and see su access. It just seems like the tablet isn't recognizing that it does have it.
yeah, I ran superuser immediately after rooting. then rebooted each time. http://forum.xda-developers.com/showpost.php?p=29951628&postcount=494
lol thats everything that I have tried. kinda sucks, but im sure someone will figure it out at some point.
weird thing is, if I run a command prompt from within the package folders I see that its rooted. if I run terminal on the device it says permission denied and prompt is still $. just odd.
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
alienedd said:
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
Click to expand...
Click to collapse
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
henbone11 said:
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
Click to expand...
Click to collapse
Perhaps this then?
d14b0ll0s said:
Perhaps this then?
Click to expand...
Click to collapse
Ok, I followed this http://forum.xda-developers.com/showpost.php?p=28519641&postcount=11 and was successful in rooting mine and my gf's infinity's.
one thing though. after manually rooting, after the final reboot, go into the Superuser app. DO NOT UPDATE IT FROM WITHIN THE APP. for some reason, updating from within Superuser borks the app. at least it did for mine and my gf's.
optional:
close Superuser. go to the play store and download busybox installer (needed to run titanium backup), root checker (there are a ton, just pick one of the top ones), adaway, ota rootkeeper and titanium backup. doesnt matter what order. I would run busybox installer first though once you have everything installed. after busybox installs, you can run root checker, adaway or titanium to check root. I say after you install busybox because some apps do require busybox to be installed before they consider you rooted. if you get the superuser prompt to allow/deny, everything is working fine. once you know that you have root and everything is working ok, run ota rootkeeper.
my only question at this point is regarding OTA updates. to my understanding, simply rooting will allow you to continue to receive OTA updates, but unlocking the bootloader will prevent you from getting OTA updates...is this correct?