hey everybody,
first of all, you need to know that im a noob.
today i tried installing another rom on my galaxy s2. everything went fine until i tried to find the rom on clockworksmod to get it installed. it was not there.
i placed the rom on my external sd card in stead of my internal storage. when i found out i tried restoring to a backup i had made. this failed as well. it said that android_secure.img was not found.
now when i try to boot up it stays on the galaxy s2 screen with the yellow triangle.
so basically all i can do know (to my knowledge) is boot clockwork or enter the downloading mode.
i think that there are three things i can do:
1. somehow install the miui rom from my sd card.
2. somehow get the rom onto my internal storage.
3. somehow fix the backup so i can boot my old rom(place android_secure.img in the right directory).
at this point i would prefer the third option.
do you guys have any idea on how to do any of these three options, preferably the third?
thomas
I'm a noob as well, but if you can get it into download mode, shouldn't you be able to install something like lite'ning rom into it through Odin?
Edit: now that I think about it you should also be able to flash the stock ROM into it, though I've never done that.
seems like it might work. i really don't want to completely brick my phone though, so im going to wait to see if there is another solution. thanks a lot though, that is at least something i can try. anyone got experience with this or knows another solution?
how might i do that? and where can i find the stock ROM?
I'm guessing here somewhere: http://forum.xda-developers.com/showthread.php?t=1075278
never mind that, i tried flashing lite'ning using odin and it worked!
i now have acces to my internal storage again, so now i can continue flashing miui.
you, my friend, are a lifesaver!
thanks for the quick responses.
thomas
Related
Hello:
I'm having a frustrating experience attempting my first root of my G2X.
I've had a previous thread from yesterday, attempting to do things from the Mac side:
http://forum.xda-developers.com/showthread.php?t=1172487&highlight=velanche
As of now, I've decided to revert to Windows 7 on my Mac to try and rectify things. I'm able to use One-Click Recovery Flasher, following the instructions, to flash the phone. I then downloaded an earlier nightly version of CM7, installed it on my flash drive, and did the install via ClockworkMod.
I had no errors from CWM, from the wipe to the install. I then choose the reboot open, and it powers off my phone.
Upon attempting to turn on my phone, I would get the LG screen, followed by a quick flash, followed by another LG screen with some horizontal blue background behind it. I'm taking it that it means that it's stuck, because I've waited 10 minutes before having to do a battery pull.
I did at one time attempted to flash back to the stock T-Mobile, but when the LG screen came it, it would just remain there without any progress.
At this stage, I don't know where else to go. I'm not sure if there's something amiss, because my phone, as far as I know, as been erased. If there's a way to progress to CM7, I'm game. But one thing I really need to do is to get my phone back.
I didn't backup my phone's contents initially because I was going to recreate everything anyway. Now I'm in a not-so-good place, save having to get a phone exchange.
Any assistance would be appreciated; thanks so much.
V.
Download one of the "Stock Rooted Nandroid Backups" from the development section, stick it on your SD card and do a Nandroid restore from CWM. That should get your phone working again...
On the CM7 installation problem, I have no idea what that could be. I've been flashing ROMs on Android devices since the G1 first came out a few years ago and the only reasons I had bootloops were from me trying to flash without wiping or flashing an unstable build.
Sorry to digress for a second here, but you DO have the T-Mobile branded G2x and NOT the Optimus2x, right?
Working on It
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
Sent from my Nexus 5g using XDA Ultimate App
velanche said:
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
Click to expand...
Click to collapse
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
Sent from my LG-P999 using XDA Premium App
LordButtersI said:
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
I don't know if this might have anything to do with why I've had problems getting CM7 to work, but I've noticed that when I plug the phone either into Windows or OS X, I've somehow lost the internal drive. I know that it's there because I've found a whole bunch of files on it while in CWN, but I'm suspecting that there's some link between neither computer seeing the internal drive and the issue with getting the phone to boot.
Yes, I can mount the external drive, either from CWM's mount on both platforms or when I press both volumes on my phone and plug in to Windows 7 via USB.
Do you have any insight on this? I was watching a few of The Unlockr vids, and I noticed that even though the guy's phone was rooted and flashed, he still could boot into his phone until he was ready to put on the new ROM (CM7, in this case).
Thanks!
Click to expand...
Click to collapse
scooter247 said:
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
I tried on the OS X side to do this, having to download an RAR app. I found the LG file, and told the app to extract it to the backup directory on my phone. I tried the restore again in CWM, but still a mismatch.
I will try it in Windows 7 tomorrow, and will let you know the outcome.
I'm beat; spent the whole weekend on this phone modding biz. I suspect I'll be really good by the time I finally am able to get things working.
V.
Click to expand...
Click to collapse
Is this an old SD card? Perhaps some bad sectors on it? Without holding the phone in my hands I can't think of anything else. Other than double check your steps, re-copy the files and try, try again.
The SD card is not old; about 2 months old. I tried formatting the card via Windows 7, but did it in FAT32. I take it that it's supposed to be formatted differently? The card is 16GB, but when I looked into CWM it's limit is 4GB.
I tried the steps again, and still get the same md5 mismatch. Is my guess correct that the card is supposed to be formatted a certain way? Unfortunately, I can access the previous OS via my phone, nor will the internal memory appear when the phone is plugged into the computer. However, I am able to mount the SD card within the computer's OS.
I almost feel like walking away from it for a week, but that means I'll be stuck without phone access for awhile. Tips or suggestions are most welcome.
BTW, there's apparently alternate instructions to deal with the md5 mismatch error. Though in Windows the NDIVIA driver is loaded for the phone, I tried the adb shell command but my device isn't detected by the software.
Thanks again,
V.
hello everyone,
I am new to Android and this is my 1st post on this web site. I would like to start off by saying everyone has done a great job with providing such a vast amount of information on one web page.
My question was, everytime that I try to install a custom rom I will go into recovery mode and it always tells me that it cant mount sd card. I have tried everything from removing the root and re rooting to formatting the sd. I have had my phone for about 3 weeks and it has been rooted since day one. However, not once have I been able to install a custom ROM.
ny help would be great thank you.
D1PL0M4T said:
hello everyone,
I am new to Android and this is my 1st post on this web site. I would like to start off by saying everyone has done a great job with providing such a vast amount of information on one web page.
My question was, everytime that I try to install a custom rom I will go into recovery mode and it always tells me that it cant mount sd card. I have tried everything from removing the root and re rooting to formatting the sd. I have had my phone for about 3 weeks and it has been rooted since day one. However, not once have I been able to install a custom ROM.
ny help would be great thank you.
Click to expand...
Click to collapse
is this stock recovery? (blue, says "3e" at the top) if so that's weird, it would normally give a signature verification error if you did something wrong. it shouldnt have any trouble with the sdcard mounting.
do you have clockwork mod recovery installed? by which method? (custom kernel, rom manager) what color is the text? (red, green, orange)
I used the clockwork recovery in rom manager. And when I go into recovery mode it is all orange.
would I be better off wiping everything and starting over?
Ok, so this is my first post. Been lurking for a while and doing a lot of learning. First rooted my NS 4G about a month ago. No problems at all. Well today, I was gonna flash CM9 rom but researched it a little first. I read where it said factory wipe and format. So thats what I did but I think I did a little something to much. All I can do is get into bootloader and the recovery. I have nothing on my SD cardexcept root.zip, to flash and I can't put anything on it cause it won't connect to the computer. Someone please tell me how to get this fixed. I'm gonna try the odin route and see if that does anything. I've searched and that seems to be the way to go. Wish me luck on that and someone who is more experienced knows a better solution, please tell. Just please don't tell me I'm screwed.
type fastboot flash recovery twrp-crespo-2.0.0RC0.img in cmd, in the correct folder.
Download that from this page: http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Once you flashed, go to recovery and this will get you into team win recovery project. From there choose mount and mount your sd card. Copy your rom into your sd card and than unmount. Go back and choose install and install your rom. If your rom required google apps, flash that too. Once your done reboot your system and bobs your uncle.
Thanks for the reply. I actually went the odin route, which I was then able to go back to completely stck and start over again. Glad I got it figured and to be honest, I probably jumped the gun in asking for help, but man I got worried when I couldnt do anything with it. Keep up all the great work everyone. About a month and a half ago, I never knew what rooting was. Now I can't wait for new updates on roms and kernels, to come out.
so i installed the cm9 alpha, restored stuff via titanium backup (only green marked stuff, and some whites) and i got into a bootloop. so i went into recovery and instead of going into clockwork i used the factory reset thing at the start. (probably the main problem this happened)
so now when i boot up my phone, i cant access my sdcard. what do i do?
ive checked around ADB methods on pushing stuff over, but naturally that didnt work. so im basically stuck here. PLEASE HELP
Jahrern said:
so i installed the cm9 alpha, restored stuff via titanium backup (only green marked stuff, and some whites) and i got into a bootloop. so i went into recovery and instead of going into clockwork i used the factory reset thing at the start. (probably the main problem this happened)
so now when i boot up my phone, i cant access my sdcard. what do i do?
ive checked around ADB methods on pushing stuff over, but naturally that didnt work. so im basically stuck here. PLEASE HELP
Click to expand...
Click to collapse
Try using the All in One tool in the dev section to reflash CWM Recovery, then keep trying to ADB push a stable ROM zip to your SD card. It might take a few tries but it does work. I saved my phone from a similar situation a few weeks back using the ADB push method.
Sent from my HTC One S.
thats what im currently trying to do. for some reason clockworkmod recovery just wont work. whenever i try to go into recovery, the phone just boots instead. and i tried multiple times to push over a rom, but it just wont get past 4mb.
http://i.imgur.com/o0WZm.jpg
this is what happens.
keep in mind i had to scratch the whole using clockwork and used the other recovery instead. that atleast lets me get to recovery. but as you can see, it wont even push over 4mb out of the 137mb of the newest cm9 build.
let me explain what im doing, im following this guide (i dont quite understand what he means with the first part "flash your recovery back to stock" i just assumed he meant to reinstall the recovery, so tell me if i did something wrong here) http://forum.xda-developers.com/showthread.php?p=25557817#post25850720
and im also looking in the how to push a rom with adb thread aswell. i feel like im doing the right thing here, and dont know what else to do. this is getting frustrating. a phone with no memory isnt all that enjoyable
Jahrern said:
http://i.imgur.com/o0WZm.jpg
this is what happens.
keep in mind i had to scratch the whole using clockwork and used the other recovery instead. that atleast lets me get to recovery. but as you can see, it wont even push over 4mb out of the 137mb of the newest cm9 build.
let me explain what im doing, im following this guide (i dont quite understand what he means with the first part "flash your recovery back to stock" i just assumed he meant to reinstall the recovery, so tell me if i did something wrong here) http://forum.xda-developers.com/showthread.php?p=25557817#post25850720
and im also looking in the how to push a rom with adb thread aswell. i feel like im doing the right thing here, and dont know what else to do. this is getting frustrating. a phone with no memory isnt all that enjoyable
Click to expand...
Click to collapse
I used this thread to salvage my phone:
http://forum.xda-developers.com/showthread.php?t=1667929
I followed the instructions to the letter, and got the ROM pushed on the third try. I reflashed and was back in business.
Sent from my HTC One S.
i tried that one aswell, but since my sdcard is not mountable, "- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount) " wont work for me. and it says that the file has to be in tools instead of permanent-tools, and that also did not work for me. ive tried basically everything up until now. theres still one thing i dwell on, and that is to flash to stock recovery. i dont know where to find that for a Norwegian Telenor handset. i can find the t-mobile one, but thats pretty much it
I had the same problem what I did was, I went to fastboot locked my hboot, "fastboot oem lock" and flashed original RUU in fastboot. RUU you cam find in development section. But first you have to lock your hboot.
Sent from my HTC One S
kaiser347 said:
I had the same problem what I did was, I went to fastboot locked my hboot, "fastboot oem lock" and flashed original RUU in fastboot. RUU you cam find in development section. But first you have to lock your hboot.
Click to expand...
Click to collapse
i have to admit i have no idea what you mean here. im not pro at this, so i honestly didnt understand much of that. RUU is also something i dont "quite" understand what it. i think it is the OS itself or something.
i have no idea what i did, but i think i just solved my problem without even knowing why:s i just did the same **** over and over again. and i didnt push over anything. i just decided to "screw this, turn that phone on" went to storage and there the sd card was for some unexplainable reason. now i dont have any of my stuff though, that kinda sux
Jahrern said:
i have no idea what i did, but i think i just solved my problem without even knowing why:s i just did the same **** over and over again. and i didnt push over anything. i just decided to "screw this, turn that phone on" went to storage and there the sd card was for some unexplainable reason. now i dont have any of my stuff though, that kinda sux
Click to expand...
Click to collapse
Looks like you found out for yourself; I was going to say that you may have to reboot your recovery a few times before the SD card shows up. I think I had to reboot CMW four or five times before it showed. After that, I was golden. Well, after pushing the ROM zip twice, that is. Make sure you always have a back up or ROM zip on the SD card from now on. It sucks that you may have to resort to a blank slate, but it's better than being stuck with a $500 paperweight!
Sent from my HTC One S.
i actually had a backup, and 2 roms on my sdcard, but that obviously didnt help from now on i will keep a backup on my computer aswell as on the sdcard. if i could ever get my stock backup back that would help. looks like im not gonna have a stock backup anymore. anyone redirect me to some place i can find that just in case i ever need to revert back to stock? Norwegian Telenor based phone if that is info you needed to redirect me. thanks for all the replies guys
I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha
And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?
I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.
I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\
Thanks
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
DroidTwe4kz said:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
Click to expand...
Click to collapse
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
vitortakeda said:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
Click to expand...
Click to collapse
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
DroidTwe4kz said:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
Click to expand...
Click to collapse
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
vitortakeda said:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
Click to expand...
Click to collapse
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.