Alright, guys, I need some help here. I flashed Phiremod V7 t2. Don't know what I did wrong, but when it boots, it shows the "Cyanogenmod" startup, but after that the screen flashes and goes dark. If I boot into recovery, the screen is still dark. I've been trying to ADB it back to stock, but whenever I "ADB Shell", I get this "- exec '/system/bin/sh ' failed: No such file or directory (2) - ". I've been working on it for the last couple of days, and can't figure it out. Any help would be greatly appreciated. Thanks.
Have you tried booting off of a CWM bootable SD card? You can usually flash back to whatever base ROM you'd like using that route. If you don't have one, check out the following link: http://forum.xda-developers.com/showthread.php?t=987735
Thank you. Don't know why I didn't come here sooner.
Related
I bought it yesterday from some guy on craigslist with a dead battery, but after chrarging it with my carger it would not boot, just the G1 screen. i can not enter the recovery menu, but the boot loader menu does work. Is there anything I can do? I tried reloading the rc29 Dreaimg.nbh, but won't boot. It has the pvt 32b and seeing as how that one is easier to root, I am hoping it's a random issue and not a rooting brick.
As a side note, I have searched. through millions of forums, google, and even my attic for answers. there is always people who get no recovery and no Boot loader screen, then there are those who can access both, but I have not heard of one who can access one witout the other.
did the guy tell u if it had been rooted? if so you can flash a custom recovery image
do you know how to use fastboot? if not have a look around and then try this:
try flashing cyanogens recovery image found here:
http://forum.xda-developers.com/showthread.php?t=523558&highlight=recovery
hopefully this will allow you to do a wipe and flash a new image
if you cant do this give me a shout and il think of something else
The guy did not tell me it wouldn't work, he said it worked fine and then this happened. i traded him an old PSP I had laying around for it, so no big loss on my side. I have emailed him, but no response. Well, How would I type in those commands? Through the phone, or the PC? Thos directions are pretty unclear.
what happened when loading the Dreaimg.nbh
Did it successfully do it? It could take a while to boot afterwords so be patient.
find a guide to setting up fastboot.if ur running windows i cant help but if u run ubuntu or some other linux i can....
after setting up fastboot
boot into the spl by holding camera+power with the usb plugged in
and type the commands in on the computer (again just follow instructions on using fastboot)
its the 2nd set you should use, the ones with "fastboot clear...." etc
Oh thanks. I have jaunty installed on my other pc will see how that goes. The dreaimg.nbh file worked. No errors. Do I just restart with green+menu+red, or was I supposed to wait?
restarting should have been fine...
http://forum.xda-developers.com/showthread.php?t=537508
you may find this useful when trying to set up fastboot in jaunty....
remember when you first plug the phone in to type "sudo adb enable-server"
then "adb devices" to make sure it is detected
the first command needs to be sudo whereas the other doesnt otherwise your device wont be detected
adding the line to bashrc didnt work for me so i tend to do it from within
~/androidsdk/tools/
and it works perfect
good luck
if u dont get a reply here i may not be looking at my computer, so u can email me or gtalk me on [email protected] and il always get it (tnx to my g1 )
I was successful in running all the fastboot/adb files in Windows, but while doing some more research, I don't think this phone was rooted. I am not getting the fastboot menu when I hit back button and my PC won't read the phone.
Last night I found out that after leaving it on for like 15-20 minutes it restarts, but after the second restart the phone died. It had been charging all day as I was using it. Seeing as how it was plugged into the PC. I am heading to a t-mobile store and am going to see if I can get a hold of an extra battery, not buy one mind you just ask "politely" to see one. Seems crazy, but I have a hunch it might be that my battery has gone dead. None of the nbh files I tried did anything except the rc30, that one caused my phone to start restarting, before it would stay on the g1 one for more than thirty minutes without a restart.
Sounds like its unrooted and stock but somehow has a corrupted rom.. It should be recoverable. Try the goldcard method to get RC30 on there:
http://forum.xda-developers.com/showthread.php?t=485364
I have been reading through that thread, but I have no idea how to actually use the goldcard that was generated. Anyone can help me through it seeing as I can not enter commands from my phone.
Ok I went to my Mac because dd command does not work under cygwin that well for me( I'm more familiar with terminals from ubuntu and OS X) Well I can't get the goldcard.img onto my micro sd card. I have been reading and no one seems to have any troubles other than actually generatiiong the gold card. I will report back after I finish the whole thread. Also they suggest an allocation size of 4096, but my sd card only gooes to 100* something.
ok, bad news, I just finished the gold card instaallation and put my sd card into my phone. Now it won't go to the bootloader. Too bad.
Good news. Yesterday I tried to boot it while placing the phone in a drawer and it booted to the recovery menu! I did not have an as card at all so there was nothing I could do so I tried to wipe everything and it finished, but it went back to where it was. I had left it in blue light mode all night. So last night I left it to try and redo what I had done, but it did not work. Atleast it goes back to the bootloader. Gold card did not work but I blame it on the CID number. I can't seem to get the right one. I'm looking though.
I realized what I did. I did not mess with it. I took the battery out last night an did not touch it till just now and it booted to the android screen then froze and restarted and went back to the G3 screen I'm going to leave it like this and see if it gets fixed by tomorrow. Than while booting try to get to the recovery menu. Hopefully it will fix the problems. I seriously think it might be the battery. Tmobile store did not have a spare one though.
Just a suggestion, may or may not work.. I got a new G1 the other day, and have rooted it, etc.. Mine did the same thing, on the G1 screen for hours, never left it.. Take the SD card out of it, and try to start it.. Mine would not load due to the partitioning, I had a 47mb ext2, a fat32, and another ext2 partition, which caused it to hang on the G1 screen.. If no luck there, this site is what helped me root mine, gives the files, and the steps.. http://www.getyourdroidon.com/wiki/index.php5?title=How_to_Root_your_G1
Just take the sd card and put it on your computer via an adapter or something to copy the files (Make sure it's formatted fat32)
If by some reason, my explanation above did work, use partition manager 9 to fix the card.
I booted it withoutth sd card, but same deal. Left it without the battery last night and got it to the recovery menu but would not find the update file. Ended up freezing on me so I went ahead and rebooted. Same deal. I guess I will try again tomorrow.
Phone booted up, was entering my log in info and it froze.... I'm still trying to fix this.
At this point, I would try to go completely back to a fresh OEM install, which I'm not sure you've done since you started to get access to Recovery.
Download the original T-mobile bootloader. Rename it to update.zip and copy it along with dreaimg.nbh to the SD card. Enter Recovery and alt-s to install the bootloader... reboot using Home+Back. It will probably lock up at some point as it's been doing. Turn off the phone and get into bootloader to flash dreaimg.nbh.
Report back after you do this.
First off im sorry im adding another rooting post to these boards.
So i decided to root my 32B magic today copyed the recovery.img over and update file from the rooting wiki, loaded recovery mode then updated, but now my phone when turned on loads to the vodafone screen and freezes id left it for afew hrs but still no luck.
Here is what i know so far:
I am able to get to fastboot and fastboot usb
I cant however get to recovery mode by pressing menu+power
I can get to the recovery mode using the sdk\tools
my problem is that im sure the fix is relativly simple i.e. load some files onto sd and start again, but the problem is that i have no other way to load the files onto the sd card than through the phone and my knowledge of adb isnt that great although has improved greatly today lol.
Im not sure how correct i am on this, but would it be a possible fix to load say a rom update.zip onto the sd card and load that through recovery mode to bring it up? If that would fix it could i possible get help on the adb code needed to pass the file from computer to the phone through fastboot usb or recovery.
Thank you very much for your help
Ok i think i have figured how to push files to my sd card however whenever i try it come up saying Failed ( remote:signature verify fail)
ok well i managed to move Cyanogen's newest rom over and update to that but its still hanging up at the vodafone screen upon booting, im lost for ideas.
Please any help how ever small would be amazing right now.
please help is desperatly needed.
i am having the same issue.... and it seems NO ONE has a bloody answer to why it is failing
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
i had the same problem, what i did was that i found a sd card adapter and hooked it up to my computer, its pretty quick and less hassle
waacow said:
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
Click to expand...
Click to collapse
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
I still have a pretty red splash screen and stucked.
neoxtian said:
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
Click to expand...
Click to collapse
I have same problem, but your solution didn't work for me.
I did as follows.
#1. typed following command in terminal.(well, I'm using Mac)
Code:
fastboot-mac flash recovery recovery-RAv1.2.0G.img
#2. pulled battery off from phone.
#3. pluged USB cable to phone and also Mac.
#4. pressed (ENTER) in the terminal, then fastboot-mac said '< waiting for device >'.
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
#8. On the phone, pretty red splash screen was still there. Nothing was changed.
Those are all I have done many times for last 2 days.
But, it didn't work.
Please let me know if there is something I missed.
I tried and stuck in the exactly same problem as [robotician]. I have MT3G.
robotician said:
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
Click to expand...
Click to collapse
THe red vodafone should not come up. You have to hold the back key longer perhaps, because it's supposed to go into the fastboot screen with all sorts of text and three androids on skateboards at the bottom.
@Niaski
was your rom made for the 32B or the 32A?
They are very diferent phones and mixing the roms causes the issue you are seeing.
Hi,
I have weird situation with my T-mob MyTouch3G. Did a lot of searching – couldn’t find anything similar. About 3 weeks ago I used Recovery Flasher to load CyanogenMod (4.0.1), later upgraded to 4.0.4. When booting into recovery I see that I am running "Build: CyanogenMod v1.4 + JF". Phone works fine (kudos to Cyanogen), but when i decided to partition my SD card i got into the following situation:
1. When I try to use "parted" from terminal emulator, I am getting "not found" (I do su before), when it is clear that CM recovery 1.4 contains Gparted.
2. When in recovery mode I select "Console(Alt-x)", I get "press enter" in horizontal layout and then white dots start moving on the screen from left to right, eventually (in about 2 min) occupying the whole screen.
3. When I tried to reflash CM recovery through fastboot I get "not allowed" - although this might be due to the fact that i am still running original "perfect" SPL. When trying to re-flash recovery though adb, no error message is shown and the process is done immediately.
So, my question is what is wrong here? How do I get fully functional CM recovery?
Any help is appreciated!
Sounds to me that you hit it on the head... go back through the root process and rid your self of that buggered SPL.
I will try to revert to the original state and then repeat the process, but is there any other ideas? B/s restrictive SPL does prevent re-flashing, but i dont see why CM-recovery rom which is already installed and able to flash roms is itself not fully installed/function.
Thanks!
Edit: Im not sure if the title is right. Im trying to run the Android from my sd without actually rooting the Nook. Sorry. Wanted to clarify.
Im using the instructions here: http://forum.xda-developers.com/showthread.php?t=1000957
I can get the image to write on my sd card which is an 8GB if that matters. I load the CM7 onto the sd cards root and insert it into the Nook. I used this build: cm-7-20120624-NIGHTLY-encore.zip
It starts to do its thing and gets stuck with this message: "Please download it from nook.linuxhacker.ru
and put on first partition of this SD card the name should start with updatei-cm and end with .zip".
I searched the topic in several different areas and found some replys but none that made any sense to me. Im hoping someone can "dumb it down" a little for me. What do I need to change/do to solve this? If I didnt include a piece of info needed please let me know and ill do my best. Thanks.
Just rename the cm- file to start with update-. Then try booting again.
leapinlar said:
Just rename the cm- file to start with update-. Then try booting again.
Click to expand...
Click to collapse
That worked great! Thanks so much! Unfortunetly it lead to another issue. I followed the instructions to install gapps file. This is the one I used: gapps-gb-20110828-signed.zip from the site in the instructions. I booted into recovery using the method of going into Android and powering off and selecting recovery but nothing happened. I came back to the decktop and nothing changed.
So i need to rename something again?
Brad7196 said:
That worked great! Thanks so much! Unfortunetly it lead to another issue. I followed the instructions to install gapps file. This is the one I used: gapps-gb-20110828-signed.zip from the site in the instructions. I booted into recovery using the method of going into Android and powering off and selecting recovery but nothing happened. I came back to the decktop and nothing changed.
So i need to rename something again?
Click to expand...
Click to collapse
Use the boot menu method. Power completely off, then boot, holding the n button until the boot menu comes up. Select SD and recovery and boot. It will go into the SD recovery which is the little penguin guy and install the gapps. (You did put the gapps file in the boot partition by putting card in the PC didn't you?)
leapinlar said:
Use the boot menu method. Power completely off, then boot, holding the n button until the boot menu comes up. Select SD and recovery and boot. It will go into the SD recovery which is the little penguin guy and install the gapps. (You did put the gapps file in the boot partition by putting card in the PC didn't you?)
Click to expand...
Click to collapse
Yep. I put it in the pc. I was having trouble booting it to recovery with the method you described but ill try until i get it right. Thanks for your time and helpbthus far. Ill let you know how it goes.
Hi guys, getting kinda desperate here, appreciate any advice.
I've been mucking around with my phone trying to install some of the mod roms from here, but always get stuck in an endless reboot sequence or on the 'huawei' screen. Havent been able to get CM10.1 or 7 installed and working.
I have followed the instructions, including the partition size mod....
This is not my current issue, however, just the background.I was at a loss so after giving up last night I tried to copy b162 to my sd card, but was read only for some reason - showed up as CD rom on my PC.
Out of desperation I formatted the sd (in CWM) and tried again, but couldnt even get CWM, only pink or blue screen.
Pink screen I tried copied recover.img to the one available drive on my PC (windows), no luck. It copies over, but will not enter CWM with vol up + power.
Went out and bought a card reader this AM, have tried to install the stock roms B162 and B136.
I can copy the .app files to the SD card (root/dload), but my phone when going to pink screen does not start updating, just stays in pink screen.
Have formatted the card in windows (fat32) checked for errors etc. Does anyone know if the 'allocation file unit' during formatting makes a difference? I have left it as standard at 32kb....
The current rom boots as far as the animated huawei (splashing stars thing) logo then cycles.
Cant get shell access with ADB on pink or blue screen.
Never really used linux but Im willing to try anything to save my phone.
I have some experience with microcontrollers and think there are some jtag pads on the back of the phone that might be useful but am reluctant to try this as I fear I will make things worse....
Many thanks in advance!
To add ? volume label important?
Just managed to get into the stock recovery screen, selected 'apply update from sdcard and got reply 'failed to mount /sdcard (no such file or directory).
I cant swap out the recovery.img file in the purple screen, I dont have acess to that part of the memory from purple screen, perhaps wrong version of android on previous install?
Was wondering if volume label should be something? I just left it blank, and have tried again as 'sdcard' still no luck.
Thanks again....
OK I did a factory reset from within the stock recovery sftward (couldnt even get this before) and it will now boot heh.
Oh well, thanks for listening! Will have another crack at aurora now =)
AucklandMatt said:
Just managed to get into the stock recovery screen, selected 'apply update from sdcard and got reply 'failed to mount /sdcard (no such file or directory).
I cant swap out the recovery.img file in the purple screen, I dont have acess to that part of the memory from purple screen, perhaps wrong version of android on previous install?
Was wondering if volume label should be something? I just left it blank, and have tried again as 'sdcard' still no luck.
Thanks again....
OK I did a factory reset from within the stock recovery sftward (couldnt even get this before) and it will now boot heh.
Oh well, thanks for listening! Will have another crack at aurora now =)
Click to expand...
Click to collapse
so have you fixed ur phone sir ? tell me how to do that sir bcoz same problem here