Obviously there are reasons for wrong doing but after soft bricking my vibrant (not really doing anything just started force closing upon a morning reboot and now i'm stuck) I'm wondering why this happens? I've seen a lot of posts saying that from "flashing too many ROMS" but i flashed a boatload of roms on my g1 and as long as I did it correctly it was fine because it should be wiping all data and replacing it with a whole new ROM but yet when I flash the exact zip files that have worked before they all result in a black screen, i'm currently trying to find a solution to get to stock ( i have a mac ) but I mean, I want to go back to bionix fusion but not if I know that after every couple flashes the phone will go black on me and ill have to start all over at stock again. Sorry, I just want more of a specific reason than "flashing too many roms"
joe.kerwin said:
Obviously there are reasons for wrong doing but after soft bricking my vibrant (not really doing anything just started force closing upon a morning reboot and now i'm stuck) I'm wondering why this happens? I've seen a lot of posts saying that from "flashing too many ROMS" but i flashed a boatload of roms on my g1 and as long as I did it correctly it was fine because it should be wiping all data and replacing it with a whole new ROM but yet when I flash the exact zip files that have worked before they all result in a black screen, i'm currently trying to find a solution to get to stock ( i have a mac ) but I mean, I want to go back to bionix fusion but not if I know that after every couple flashes the phone will go black on me and ill have to start all over at stock again. Sorry, I just want more of a specific reason than "flashing too many roms"
Click to expand...
Click to collapse
Step 3: Flash Bionix Fusion
This is the final step of the installation. This presumes you are already rooted and ready to go. If you are not, then you will need to root and install rom manager first.
1. Download the rom of your choice and place the file onto the root of your internal sdcard.
2. Reboot into Clockwork Recovery.
- From Rom Manager app, select 'boot into clockwork recovery'
- From ADB, type 'adb reboot recovery'.
3. From the main clockwork recovery menu, use the 'down' volume control to scroll to 'install zip from sdcard'. Press the power button. this will take you to a second menu screen.
4. From thet second menu screen, scroll to 'choose zip from sdcard' and select with the power button.
5. Scroll to the file name of the rom you downloaded and press the power button. It will ask you to confirm your choice, select 'yes' and the rom will begin to flash. DO NOT TURN OFF YOUR PHONE DURING THIS PROCESS!
6. Once the flash is complete, select 'go back'. Now select 'reboot' from this menu.
7. Allow your phone to reboot completely. The first boot will take a few minutes, please be patient.
8. Once booted into the home screen, please allow your phone to sit for 5-10 minutes to allow all boot procedures to take place. Keep in mind, you've just heavily modified your device, it needs time to adjust to the new changes.
9. Wait roughly 15 minutes after the first initial boot and then restart your phone one time. You may do this by holding the 'power button' and selecting either shut down or reboot.
chichu_9 said:
Step 3: Flash Bionix Fusion
This is the final step of the installation. This presumes you are already rooted and ready to go. If you are not, then you will need to root and install rom manager first.
1. Download the rom of your choice and place the file onto the root of your internal sdcard.
2. Reboot into Clockwork Recovery.
- From Rom Manager app, select 'boot into clockwork recovery'
- From ADB, type 'adb reboot recovery'.
3. From the main clockwork recovery menu, use the 'down' volume control to scroll to 'install zip from sdcard'. Press the power button. this will take you to a second menu screen.
4. From thet second menu screen, scroll to 'choose zip from sdcard' and select with the power button.
5. Scroll to the file name of the rom you downloaded and press the power button. It will ask you to confirm your choice, select 'yes' and the rom will begin to flash. DO NOT TURN OFF YOUR PHONE DURING THIS PROCESS!
6. Once the flash is complete, select 'go back'. Now select 'reboot' from this menu.
7. Allow your phone to reboot completely. The first boot will take a few minutes, please be patient.
8. Once booted into the home screen, please allow your phone to sit for 5-10 minutes to allow all boot procedures to take place. Keep in mind, you've just heavily modified your device, it needs time to adjust to the new changes.
9. Wait roughly 15 minutes after the first initial boot and then restart your phone one time. You may do this by holding the 'power button' and selecting either shut down or reboot.
Click to expand...
Click to collapse
Well at least we know you can copy and paste. You obviously didn't read my post correctly.
joe.kerwin said:
Well at least we know you can copy and paste. You obviously didn't read my post correctly.
Click to expand...
Click to collapse
Well, if you follow the instructions mentioned in the fusion post it should clean wipe your phone and give you a stable phone, give it a try without tweaking the kernel or anything to make sure you are not getting any black screens.
1 question though did you overclock your phone?
I would take 1 step at a time, first get your phone to stabilize. The reason I referenced Fusion is because, Fusion is much more stable than the Stock Samsung JFD.
joe.kerwin said:
Well at least we know you can copy and paste. You obviously didn't read my post correctly.
Click to expand...
Click to collapse
Did you flash anything over Voodoo?
i've never used voodoo and no i wasn't overclocking even though i had an OC capable kernel. My problem was my phone doesn't turn on, and i dont have a PC to use ODIN also I mentioned that no matter what ROM I flash my phone wont turn on, flashing fusion would not fix it. Anyways I went to tmobile and just told them "my phone doesn't work" and this really cool guy just swapped it for me no questions asked even though i'm well beyond that two week grace period.
Bricks don't happen from flashing too many roms. I've been flashing roms constantly for the last couple weeks, and I've yet to brick my phone. Bricks are usually caused by people not carefully following instructions, or by flashing incompatible rom/kernel combinations. If you play it safe and are careful, you won't brick your phone.
joe.kerwin said:
i've never used voodoo and no i wasn't overclocking even though i had an OC capable kernel. My problem was my phone doesn't turn on, and i dont have a PC to use ODIN also I mentioned that no matter what ROM I flash my phone wont turn on, flashing fusion would not fix it. Anyways I went to tmobile and just told them "my phone doesn't work" and this really cool guy just swapped it for me no questions asked even though i'm well beyond that two week grace period.
Click to expand...
Click to collapse
Most probably the oc/uv kernel, some phones cannot handle undervolting.
Sent from my bionix powered Vibrant
My phone is pretty new... I only had it unlocked and rooted.
It just soft bricked on me this morning after listening to music... Not exactly sure why.....
Related
My Amaze 4G won't turn on...
So this is what has happened:
- I rooted my phone following the guide on this forum and installed recovery successfully
- I then flashed BeastMod 2.3.0
- Wiped out everything, then I tried to turn on my phone it would be stuck on the HTC screen when you first turn the phone on. (only thing that was able to be booted was the bootloader and recovery)
- I was like CRAP! What did I forget?! Then I was like I think I read something about kernel... I was like crap...
- I took the SD card plugged it into my MyTouch 3G Slide and downloaded BeastMod 1.3 (I think, the one without needing a kernel).
- I then proceeded to install it through Recovery. It installed.
- To my amazement, it worked I was like YESSSS.
- Then I proceeded to install the Faux Kernel v007 and then BeastMod 2.30
- IT WORKED, I got to witness the lockscreen of the beastly BeastMod 2.30!!! I was like this is amazing. Then I was like I think it said a full wipe.
- So I went back into the recovery. I wiped/formated everything it let my format/wipe. I was like clean install FTW. (I don't know if I should've)
- To my dismay, when I rebooted it. ONCE AGAIN THE HTC SCREEN ARGHHHH. So I tried factory resetting it (which I don't know whether or not it does bring me back to stock YIKES...)
- Then I was like its late at night, I should go to sleep. I took out the battery. Put it back in. Plug it into the wall charger and went to sleep. I thought I would fix this problem tomorrow.
- Now when I woke up a few hours ago... my phone is not turning on. It was clearly plugged in and everything to the wall charger. Orange LED light on when I plugged it in. I searched this up on Google to no success in solving this problem.
Currently while writing this post I have taken my battery off for 10 minutes to see if it resets the phone's battery stats, etc.
I have some experience of knowing how to root and flash. I have flashed a MyTouch 3G slide (a bunch of times), a G2, and a G2x. The G2x experienced the same not turning on problem, but it was fixed somehow after a while.
The ultimate question is... how do I fix my Amaze 4G by getting it to turn back on and successfully flashing the latest BeastMod (which I have heard has beastly battery life) with a 100% clean install?
Oh and when I have it plugged into my computer. It keeps having that beep (repeatedly in an interval of 5 - 7 seconds) when you first plug the usb in to the computer.
EDIT (QUICK UPDATE): My phone is back on. I frantically pressed the power button like no tomorrow and it finally turned on, but its still stuck on the HTC screen. Right now I'll try reflashing BeastMod 2.30. Hopefully it works. :/
EDIT: ON BOOTLOADER, it says:
"battery voltage is too low
please change a battery."
bad battery already... the heck?
DarxMalFur said:
Oh and when I have it plugged into my computer. It keeps having that beep (repeatedly in an interval of 5 - 7 seconds) when you first plug the usb in to the computer.
EDIT (QUICK UPDATE): My phone is back on. I frantically pressed the power button like no tomorrow and it finally turned on, but its still stuck on the HTC screen. Right now I'll try reflashing BeastMod 2.30. Hopefully it works. :/
EDIT: ON BOOTLOADER, it says:
"battery voltage is too low
please change a battery."
bad battery already... the heck?
Click to expand...
Click to collapse
Get back into recovery and wipe battery stats. Should be fine afterwards.
Sent from my GT-P7510 using xda premium
Remember, if you can get into Recovery...you're OK!!!! Relax! It still sounds like you're shooting in the dark a bit (i.e. could have read up a little more before you took the leap), but...
1) Bad battery issue - really doubt it. It probably drained...why you might ask?
2) Which leads into the question of which Recovery did you install? Some of them apparently have "charging" issues. That might have contributed to the "battery voltage is too low please change a battery" message.
In any case, if you can charge the battery/swap with one of your friends with a compatible one (Sensation and Evo3D I think use the same battery), try that out. Or, try your luck at charging it some. Again, if you can get to Recovery, 99.99% of the time, you aren't screwed.
verkion
I always thought you have to wipe (cache, dalvik and factory reset) prior to flashing ROM because the ROM installs into the freshly wiped partitions.
Sent from my HTC Amaze 4G using XDA App
This is actually a very easy to fix issue.
You read that you needed to wipe after the phone was already on. You the proceeded and wiped/factory reset.
- After you do that, everything erases; therefore, you do not have a ROM installed in your phone anymore.
So the fix is:
1) Go into recovery
2) Wipe/factory reset (yes again, idk what you might have done)
3) Wipe cache
4) Advanced / wipe dalvik cache
5) Adcanced / wipe battery stats
5) Install .zip from SD card / choose .zip from SD card
6) Beastmod.zip (or whatever it might be called)
7) Restart the phone... it all works.
(You don't exactly have to do all those steps, but I would suggest you do to start your phone 100%% fresh for the new rom)
Enjoy!
- Xologist
xologist said:
This is actually a very easy to fix issue.
You read that you needed to wipe after the phone was already on. You the proceeded and wiped/factory reset.
- After you do that, everything erases; therefore, you do not have a ROM installed in your phone anymore.
So the fix is:
1) Go into recovery
2) Wipe/factory reset (yes again, idk what you might have done)
3) Wipe cache
4) Advanced / wipe dalvik cache
5) Adcanced / wipe battery stats
5) Install .zip from SD card / choose .zip from SD card
6) Beastmod.zip (or whatever it might be called)
7) Restart the phone... it all works.
(You don't exactly have to do all those steps, but I would suggest you do to start your phone 100%% fresh for the new rom)
Enjoy!
- Xologist
Click to expand...
Click to collapse
I tried all the instructions (except for flashing a new ROM, since I can't get the ROM to flash...) and it's still stuck on the HTC main page, when it first starts...
Help?
Download stock recovery and search for relock bootloader and search for stock ROM. Go to your hot boot and download stock recovery, after relock and put your stock ROM on your SD card. And the phone is going to boot on the factory (the same as you bought the phone).
william.laing said:
I tried all the instructions (except for flashing a new ROM, since I can't get the ROM to flash...) and it's still stuck on the HTC main page, when it first starts...
Help?
Click to expand...
Click to collapse
Just saying .. when i first flashed I also was scared on the htc screen but you actullay have to wait..
... Did u atleast wait like 2 to 3 mins... It takes time to load up the first time u install a mod..
---------- Post added at 11:59 PM ---------- Previous post was at 11:44 PM ----------
zab911 said:
Just saying .. when i first flashed I also was scared on the htc screen but you actullay have to wait..
... Did u atleast wait like 2 to 3 mins... It takes time to load up the first time u install a mod..
Click to expand...
Click to collapse
nvm I see u said u have flashed b4.. so Iam sure u waited long enough..
william.laing said:
I tried all the instructions (except for flashing a new ROM, since I can't get the ROM to flash...) and it's still stuck on the HTC main page, when it first starts...
Help?
Click to expand...
Click to collapse
This Happened to me..
I used command prompt and brought the device to the recovery mode and flashed the rom. Now the phone runs ICS and works like a charm.
You need to download android sdk for windows/mac or whatever OS you have on our computer and install it.
1. Download and copy a ROM or TWO on your microSD and put it back in your Amaze.
2. Open the Command Prompt.
3. Type adb devices and hit "Enter"
4. It should display HTC device
5. type adb reboot bootloader
6. Use the volume button to move to "recovery" and select it by pressing the power button.
7. Then select the install zip from SD card.
8. Select one of the ROM's from your microSD and once the install is Complete, hit the return arrow at the bottom of your phone's home screen and press power button to select "reboot phone now".
rahulntinku said:
This Happened to me..
I used command prompt and brought the device to the recovery mode and flashed the rom. Now the phone runs ICS and works like a charm.
You need to download android sdk for windows/mac or whatever OS you have on our computer and install it.
1. Download and copy a ROM or TWO on your microSD and put it back in your Amaze.
2. Open the Command Prompt.
3. Type adb devices and hit "Enter"
4. It should display HTC device
5. type adb reboot bootloader
6. Use the volume button to move to "recovery" and select it by pressing the power button.
7. Then select the install zip from SD card.
8. Select one of the ROM's from your microSD and once the install is Complete, hit the return arrow at the bottom of your phone's home screen and press power button to select "reboot phone now".
Click to expand...
Click to collapse
or you can just press volume down + power while turning the phone on.. and it goes into bootloader menu.
I think it's those 2 keys
VOLUME DOWN + POWER
uhg, i came across this thread after searching google. my amaze is down. i cant read the screen because it isnt back lit. i am using my co-workers iphone LED "flash-light" to be able to barely read it. i have done all of this:
1) Go into recovery
2) Wipe/factory reset (yes again, idk what you might have done)
3) Wipe cache
4) Advanced / wipe dalvik cache
5) Adcanced / wipe battery stats
5) Install .zip from SD card / choose .zip from SD card
6) install bullet proof rom zip
7) Restart the phone...
and when it restarted in launched with the HTZ logo, and then went black again.. I will have to wait till i get home to try another battery... let me know if anyone has any more suggestions.. i may need to try to download the stock rom and everything again? i hope my phone isnt FUBAR
he has 5.0.2.6 recovery flash my latest one 5.5.0.4 with working charge off
Recently i flashed the CM9 rom onto my Droid X2. Followed the instructions and everything installed correctly. Since it has been a couple of days and I have installed all my programs and got everything where i wanted it, i wanted to make a backup.
Soon i discovered that I didnt have System Recovery installed. SO i began looking into my SD card and i have two files,MOTODX2_Bootstrap_signed.apk. So i decided to install it, everything went fine but now my phone is stuck in a boot loop. It wont even boot into CM9.
Is there another BSR that i should be flashing instead of this one. Maybe the ReRecovery one? i know theres a [patched] BSR to install but i gave me the same problems.
Thanks EHB
Hi, for Cyanogenmod9 use the CM7 PATCHED BSR. It works just fine for me everyday. I'm kind of addicted to flashing ROMs for some reason and usually am on different ones multiple times a day. Always in BSR either restoring or backing up. The patched BSR for CM7 works just fine for me. For reference, in the app drawer it should say "CM7 System Recovery" not just System Recovery.
I'm not sure if it has been looked into by dev's yet or not, but the day CM9 was released I actually did flash the CM7 ReRecovery zip and I was able to boot to BSR from a powered off state just by plugging in. I wasn't sure if it was okay to use, so I installed a fresh CM9 without it. I don't know if this is 100% safe or if there would be any issues from using the ReRecovery zip. I would recommend just installing the patched CM7 apk and trying to use that.
Here's the link to the patched CM7 Recovery. Pulled straight from the CM7 thread
http://www.mediafire.com/?pzz4413k6wggcao
***^That BSR is an application. You download, install and run it on your phone. The ReRecovery is a flashable zip you can install once already inside of BSR allowing you to get into custom recovery say for example, if you're boot looping. ***
================================================
If you're still having bootloop issues, try this;
-Grab your ECOMOTO charger, plug into A/C power, pull battery, replace & plug into wall.
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
-When you see the battery charging icon, unplug your phone and pull your battery.
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
This will take you to a screen that shows a picture of an android next to a triangle with an exclamation mark (!) inside of it.
-From that screen press both the VOLUME UP and VOLUME DOWN keys at the same time.
If you made it this far, you're now in the stock android recovery. Using the volume buttons, key down to Wipe Cache Partition then press the power button to select. You will be taken to a confirmation screen. Key down and select Yes. Wait for it to complete. After you wipe the cache try rebooting back into CM9. This will take slightly longer than usual as your cache has to rebuild itself. If you can boot back up successfully, click the link above. Download the patched CM7 Bootstrap Recovery and install it. If you don't know what to do from there, open the application "CM7 System Recovery" and click "Install Recovery" -- You will now be prompted to grant or deny it superuser permissions. Allow them. You will receive a message saying the install was a success! Click OK. Now plug your phone back into the wall outlet and hit "Recovery Mode" and your phone will boot into BSR! From there just go to backup and save it to your external SD card. You can find your backups later via the file explorer of your choice under /mnt/sdcard/clockworkmod/backup. Note: You can rename the file so you know which ROM is which, just don't add spaces to the file name or it will ruin your backup and you will not be able to restore it. NO SPACES!!!
FYI you will still see the Motorola logo immediately after it turns back on. It takes a minute or two to boot into custom recovery.
I've been through a lot of trial and error with the X2 and these steps have helped me plenty of times. Hopefully they do the same for you....Good luck.
Cyanogenmod all day
Thanks for the information.
I knew basically everything you said except for the "wipe cache partition". Why is this necessary? I know that it doesn't delete personal information but what does it wipe/delete?
Im going wait to do this tomorrow - my day off. Im just worried that its going do the same thing and ill have to reflash and start all over again.
Thanks again EHB
Wiping the cache partition clears any/all application data and common app components. It does not wipe apps themselves, rather the files that the app generates when used.
Wiping it is necessary because when core system components are changed, the resources used by the apps also (could) change. Having stale app data after a system change or tweak can cause problems, which is why it is best to clear it. It gets rebuilt as apps are used.
RoyJ said:
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
Click to expand...
Click to collapse
I'm afraid I'm in the same boat and am going through these steps to hopefully get back on the right track. When you say the battery charging icon can take several minutes... are you suggesting 3-5 minutes, or up to 30 minutes? Because... I'm at about 35 minutes right now and am getting pretty nervous.
just skip to this part, if you can
remove charger and battery
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
Click to expand...
Click to collapse
Patched BSR, please help!!
RoyJ said:
Hi, for Cyanogenmod9 use the CM7 PATCHED BSR. It works just fine for me everyday. I'm kind of addicted to flashing ROMs for some reason and usually am on different ones multiple times a day. Always in BSR either restoring or backing up. The patched BSR for CM7 works just fine for me. For reference, in the app drawer it should say "CM7 System Recovery" not just System Recovery.
I'm not sure if it has been looked into by dev's yet or not, but the day CM9 was released I actually did flash the CM7 ReRecovery zip and I was able to boot to BSR from a powered off state just by plugging in. I wasn't sure if it was okay to use, so I installed a fresh CM9 without it. I don't know if this is 100% safe or if there would be any issues from using the ReRecovery zip. I would recommend just installing the patched CM7 apk and trying to use that.
***^That BSR is an application. You download, install and run it on your phone. The ReRecovery is a flashable zip you can install once already inside of BSR allowing you to get into custom recovery say for example, if you're boot looping. ***
================================================
If you're still having bootloop issues, try this;
-Grab your ECOMOTO charger, plug into A/C power, pull battery, replace & plug into wall.
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
-When you see the battery charging icon, unplug your phone and pull your battery.
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
This will take you to a screen that shows a picture of an android next to a triangle with an exclamation mark (!) inside of it.
-From that screen press both the VOLUME UP and VOLUME DOWN keys at the same time.
If you made it this far, you're now in the stock android recovery. Using the volume buttons, key down to Wipe Cache Partition then press the power button to select. You will be taken to a confirmation screen. Key down and select Yes. Wait for it to complete. After you wipe the cache try rebooting back into CM9. This will take slightly longer than usual as your cache has to rebuild itself. If you can boot back up successfully, click the link above. Download the patched CM7 Bootstrap Recovery and install it. If you don't know what to do from there, open the application "CM7 System Recovery" and click "Install Recovery" -- You will now be prompted to grant or deny it superuser permissions. Allow them. You will receive a message saying the install was a success! Click OK. Now plug your phone back into the wall outlet and hit "Recovery Mode" and your phone will boot into BSR! From there just go to backup and save it to your external SD card. You can find your backups later via the file explorer of your choice under /mnt/sdcard/clockworkmod/backup. Note: You can rename the file so you know which ROM is which, just don't add spaces to the file name or it will ruin your backup and you will not be able to restore it. NO SPACES!!!
FYI you will still see the Motorola logo immediately after it turns back on. It takes a minute or two to boot into custom recovery.
I've been through a lot of trial and error with the X2 and these steps have helped me plenty of times. Hopefully they do the same for you....Good luck.
Cyanogenmod all day
Click to expand...
Click to collapse
I am having a similar but different problem with the patched BSR. I had it running fine while using CM9 on my Droid X2, but now I am running MIUI, and when I install and attempt to get into the custom recovery, it seems like it attempts to load it, but does not. What I get is a jumbled screen that has the colors of the custom recovery, so I can tell it is attempting to come up, but something is going wrong. It shows that jumbled screen for a few seconds, then goes black and eventually just shuts down. I have tried EVERYTHING I can think of to fix this. I have tried a fresh download of the patched BSR, and even did a fresh SBF and reinstall of MIUI, but nothing fixes it. Any advice you have would be greatly appreciated. Thanks!
I would re flash sbf
if you have been using ezSBF
use rsd lite, vise versa, or try a different sbf version like 2.3.3 and take ota update
or see if someone could upload a nandroid backup
Sent from my MB870 using xda premium
The odd thing is, if I restore to CM7 or CM9, then the patched BSR will work again. It seems it only goes bad with MIUI. Could the ROM somehow affect the BSR installation and/or function? I wouldn't think this is the case, as other are using the patched BSR with MIUI without trouble.
Sent from my MB870 using xda app-developers app
Hello
I rooted my Galaxy s2 i777 using 2.3.6 (I think that was it - what ATT pushed out earlier in the summer) and next flashed CWM using ODIN. I noticed that the menus weren't working in CWM. When I use the home or menu buttons it just toggles a logo screen, and power does nothing (volume keys do work). I noticed others had this issue with this phone but didn't encounter any solutions.
Poking around the Rom Manager application I noticed a reboot into recovery mode feature and thought I'd try it. It did as advertised. But now when I reboot by holding down power it immediately reboots into recovery mode. I'm guessing what happens is the "reboot into recovery mode" feature put itself at the head of the boot sequence and instead of removing itself from there on load, which it probably should, it waits until the user exits the program cleanly. Unfortunately, because I can't get the keys to work in the program, the only way I can exit is to hold down power. I can navigate to the "power off" or "reboot" options but I can't execute them (press "enter"). So it stays at the head of the boot sequence (just my theory) and I can't get out. Actually when I power off by holding down the power key the phone just reboots immediately, right back into cwm recovery, so there seems to be something more going on.
I have a backup of the system but I can't figure out how to get out of the sequence. I tried the download mode and recovery mode key sequences but they don't work (not even sure if they're supposed to work in this recovery screen). Any ideas? I have a backup of the system, so I'm happy to attempt scorched earth suggestions. Kies can't recognize the phone anymore. Many thanks.
Jason Farnon said:
Hello
I rooted my Galaxy s2 i777 using 2.3.6 (I think that was it - what ATT pushed out earlier in the summer) and next flashed CWM using ODIN. I noticed that the menus weren't working in CWM. When I use the home or menu buttons it just toggles a logo screen, and power does nothing (volume keys do work). I noticed others had this issue with this phone but didn't encounter any solutions.
Poking around the Rom Manager application I noticed a reboot into recovery mode feature and thought I'd try it. It did as advertised. But now when I reboot by holding down power it immediately reboots into recovery mode. I'm guessing what happens is the "reboot into recovery mode" feature put itself at the head of the boot sequence and instead of removing itself from there on load, which it probably should, it waits until the user exits the program cleanly. Unfortunately, because I can't get the keys to work in the program, the only way I can exit is to hold down power. I can navigate to the "power off" or "reboot" options but I can't execute them (press "enter"). So it stays at the head of the boot sequence (just my theory) and I can't get out. Actually when I power off by holding down the power key the phone just reboots immediately, right back into cwm recovery, so there seems to be something more going on.
I have a backup of the system but I can't figure out how to get out of the sequence. I tried the download mode and recovery mode key sequences but they don't work (not even sure if they're supposed to work in this recovery screen). Any ideas? I have a backup of the system, so I'm happy to attempt scorched earth suggestions. Kies can't recognize the phone anymore. Many thanks.
Click to expand...
Click to collapse
1. you obviously flashed a kernel WITH CWM via Odin.
2. Rom Manager should not be used.
Flash a rooted stock ROM via ODIN.
read around in the stickies of the i777 forum, and get acquainted with things.
Boot into CWM correctly, and go about flashing whatever you want knowing what you just learned by reading the correct stuff.
Welp, first things first.
1. Read, search, Google, only look at results from this forum, i.e. the ATT Galaxy S2 I777 forums on XDA. Any info from any other sites is more likely to get you nowhere or brick your phone further.
2. After having done so, you'll learn never to use Rom Manager. EVER.
3. Also after having done #1, you'll learn to never try to flash CWM separately. As Moto implies, CWM for our phones is built into custom kernels, it is not separate.
4. Follow this guide to start over and get back to stock.
5. Then follow this guide to root and flash custom ROMs and kernels.
You sound like an intelligent guy, so as long as you do more reading around here you'll figure everything out slowly. Make sure to read stuff multiple times until you fully understand everything, and feel free to ask questions about stuff you don't understand, but only after reading said guides multiple times.
EDIT: Gah Moto, why you gotta post ahead of me D:
Actually the problem is most likely the fact that he is probably using an old version of cwm where the home button selects stuff. And rom manager.
Sent from team Pirate! Using Tapatalk 2
karate104 said:
Welp, first things first.
1. Read, search, Google, only look at results from this forum, i.e. the ATT Galaxy S2 I777 forums on XDA. Any info from any other sites is more likely to get you nowhere or brick your phone further.
2. After having done so, you'll learn never to use Rom Manager. EVER.
3. Also after having done #1, you'll learn to never try to flash CWM separately. As Moto implies, CWM for our phones is built into custom kernels, it is not separate.
4. Follow this guide to start over and get back to stock.
5. Then follow this guide to root and flash custom ROMs and kernels.
You sound like an intelligent guy, so as long as you do more reading around here you'll figure everything out slowly. Make sure to read stuff multiple times until you fully understand everything, and feel free to ask questions about stuff you don't understand, but only after reading said guides multiple times.
EDIT: Gah Moto, why you gotta post ahead of me D:
Click to expand...
Click to collapse
Thanks, that did it. I'd actually read the stickies, I just didn't think I could get into download mode because the phone was stuck in that auto-reboot loop.
For anyone else stuck in that loop cwm recovery loop, the download mode entry method (press both volume keys and insert usb) needs to be timed just so, since you usually perform the sequence when the phone is powered down (in stable way) but in this situation you only have a moment before it restarts. After powering down, just as it restarts automatically you can see the capacitative buttons blink for an instant, and that's when I started the sequence. Took me about half a dozen times but I eventually caught it. Am I the only one struggling with how hard these captchas are getting over the years? there's probably a sticky for that too I guess nvm.
If I'm not mistaken you can get into download mode without having a battery plugged in, so no need for trying to time it. Just hold volume buttons and plug in USB. For future reference; glad you got it worked out. Make sure to read the second guide thoroughly so you know how to safely flash stuff, and hit my thanks button if i helped you out.
Sent from my SGH-I777
I would like to give credit to everyone who has worked on the android roms, and other guides. I have taken some of the info for this guide from the WIKI
It seemed we were due for a friendly how to guide on how to load a NAND rom on a RHOD device. I decided to write a step by step guide to help people out. This guide does provide a very basic ADB setup, but it is just enough to get you up and running. If you want to do advanced things you should get the full ADB, and learn more about it.
This guide is written for a RHOD400, Android GBX0*+3.4.26 rom, and a Win7 pc, but should be almost identical for the rest of the RHOD family, other versions of Windows, and most other roms.
It is assumed that you have unlocked your phone for custom rom loading in the past at some point. This is not the same as unlocking the sim card. This is 100% required. Please read here and/or here, and/or here if you need help with unlocking your phone.
This guide assumes that you know what a command prompt is, how to load windows drivers for a device, and can open zip files. If these things are not within your skill sets I would recommend that you find someone who understands these things to assist you.
Things you need.
1. A RHOD phone.
2. A micro SD card that is at least 512mb in size.
Tip: I suggest a sd card that is less than 4gb in size. There tends to be less compatibility issues with non SDHC cards. SDHC cards usually work, but if you have trouble this is a good thing to change. The SD card does have to be less than 64gb in size as the phone can not read cards larger than 32gb.
3. A usb based micro sd card reader. A usb based card reader is need to be compatible with the HP format tool. Some built in ones are usb based others are not. If you have one, you can try it and see if it works. It is not recommended to use your phone's sd card reader for prep work.
4. A usb cable that is known to work. Test it in WM first. On rare occasion I have seen cables that did work with WM and not Android. If you have issues, this is also something good to swap out during trouble shooting.
5. A windows based pc. *DO NOT USE USB 3.0 PORTS* Many reports about have come in about them causing issues.
The procedure.
1. Back up anything you want to keep from your phone. Everything on the phone will be wiped during this process.
2. Put the micro sd card into your USB card reader and format with the HP format tool. It needs to be a full fat32 format. Windows format is known to have issues on occasion, and this step is a work around for that problem. It is not 100% required, but if you have trouble it is 100% required during trouble shooting.
3. While this is formatting you can download the recovery (recovery_cwr_6.0.1.3.img) ***It has been found that the 6.0.1.3 recovery does not make backups correctly, resulting in md5 errors. You may use it if you are not planning on using the backup feature, or the older one by acl works fine. You can rename it to use the included scripts if you wish.***, rom (GBX0*+3.4.26 Full) , the boot loader, the needed usb android drivers, and the adb files.Gapps is optional.
4. Make sure your battery is at least 50% charged. I recommend a 100% charge. A dead battery in the middle of flashing can brick your phone.
5. Copy the RHODIMG.NBH, rom (GBX0*+3.4.26 Full), and the gapps (optional) files to the sd card and put it in your phone with the phone turned off.
6. Press the hold down the volume down button while pressing the power button. This will bring up the tri colored screen. It will then automatically go to the white rom update screen.
7. Follow the directions (press the power button on the RHOD400) to start the update. This should take less than 1min.
Troubleshooting tip:
If the phone sits at loading 0%, and never moves after 10 min you may not have unlocked your phone or there is an issue with your RHODIMG file. Verify that you have unlocked your phone (you can try loading a WM custom rom), format the SD card, re-download the RHODIMG file, and try again. Also try another SD card and SD card reader.
8. If the phone reboots automatically, that is fine. Otherwise when the phone says Update Success you can pull the battery to shut it off.
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.
11. Install the USB/fastboot driver for the phone. On Win 7 the phone showed initially as android device under other folder in the device manager. After the driver is installed it should be called My HTC.
12. Open the ADB Tools zip file, and put the platform-tools folder on c:\
13. Open a command prompt and go to c:\platform-tools\.
Once there type:
Code:
fastboot devices
You should get a response similar to this:
C:\platform-tools>fastboot devices
HT04TM300704 fastboot
If this is not working stop now and troubleshoot.
14. Now to wipe the phone in prep for loading (or reloading) the android rom.
There is a wipe.bat file I have included. You may run it, or you may type the following commands.
Code:
Fastboot erase recovery
Fastboot erase boot
Fastboot erase misc
Fastboot erase system
Fastboot erase userdata
Fastboot erase cache
15. Place the recovery (recovery_cwr_6.0.1.3.img) file into c:\platform-tools.
16. Now load the recovery image. If it is named recovery_cwr_6.0.1.3.img you may use the reload_recovery.bat or type:
Code:
fastboot flash recovery recovery_cwr_6.0.1.3.img
to load the recovery image then
Code:
fastboot boot recovery_cwr_6.0.1.3.img
to boot the recovery image.
17. Install the rom.
Using the volume keys highlight 'Install zip from sdcard' then press the call button to select it.
Highlight 'choose zip from sdcard' and press the call button to select it.
Highlight the rom file (GBX_3.4.26_Full.zip) and press the call button to select it.
Highlight yes and press the call button to select it.
The rom will now install. This will take a few minutes.
18. (optional) Install Gapps.
Using the volume keys highlight 'Install zip from sdcard' then press the call button to select it.
Highlight 'choose zip from sdcard' and press the call button to select it.
Highlight the gapps file (probably gapps-gb-20110828-signed.zip) and press the call button to select it.
Highlight yes and press the call button to select it.
Gapps will now install. This will take a few minutes.
19. Press the back arrow, and select reboot system now.
The phone should reboot into the Android rom now. It will take about 10min the first time. If you have waited more than 30 something has gone wrong. You should troubleshoot and try again.
At this point you have the basics all in place, and can start using your phone.
If you want to do basic ADB tasks (along the lines of installing apps remotely/side loading or pushing/pulling files) you will need to install the adb windows driver.
20. Press the thanks button if you liked this guide.
P.S.
If you have issues getting adb to work later, download and use USBDeview.exe to remove the HTC driver entries and then install pdanet for android to get the correct adb drivers installed.
So is my RHOD500 not supported by this Rom ?
denva said:
So is my RHOD500 not supported by this Rom ?
Click to expand...
Click to collapse
This is a guide, not a rom...
wizardknight said:
This is a guide, not a rom...
Click to expand...
Click to collapse
I know Is a guide . But need to know why my device keeps restarting at startup :crying:
denva said:
I know Is a guide .
Click to expand...
Click to collapse
Then why ask if your phone is supported by this rom?
denva said:
But need to know why my device keeps restarting at startup :crying:
Click to expand...
Click to collapse
Well if you have not listed all your trouble shooting steps, you will not get help from anyone. Our physic abilities are lacking these days.
Also posting specific questions in the thread about the rom you are trying to install will have a higher chance of getting useful feedback.
wizardknight said:
Then why ask if your phone is supported by this rom?
Well if you have not listed all your trouble shooting steps, you will not get help from anyone. Our physic abilities are lacking these days.
Also posting specific questions in the thread about the rom you are trying to install will have a higher chance of getting useful feedback.
Click to expand...
Click to collapse
Am refering you to this thread HERE av done all necessary things but still i get my device rebooting
http://forum.xda-developers.com/showthread.php?t=870081
denva said:
Am refering you to this thread HERE av done all necessary things but still i get my device rebooting
http://forum.xda-developers.com/showthread.php?t=870081
Click to expand...
Click to collapse
Well if you have done all necessary things, then your phone must not be compabtiable.
Maybe if you provided a list of your troubleshooting steps we might be of more help... Otherwise we have no choice, but to bow to your knowlage of having done all necessary things.
wizardknight said:
Well if you have done all necessary things, then your phone must not be compabtiable.
Maybe if you provided a list of your troubleshooting steps we might be of more help... Otherwise we have no choice, but to bow to your knowlage of having done all necessary things.
Click to expand...
Click to collapse
Thank you WizardKnight for replying me.
This is the steps i use to do.
1. I use RhodiumWUnlocker to unlock my rhod500 , to get any rom loaded with it
2. I copy RHODIMG.NBH, GBX_3.4.24_Full, recovery_cwr_6.0.1.3 all to my 4gb SDard
3. Vol- + PWR and phone turns to the tri color screen, then the phone started to load the image files
4. I press PWR butt to start the update, within a couple of seconds the phone update successfully
I press resest button for the phone to boot up to see if it will go to the fast boot screen.
But i was unlucky always the phone restart itself within some seconds.
This is my Prb
denva said:
Thank you WizardKnight for replying me.
This is the steps i use to do.
1. I use RhodiumWUnlocker to unlock my rhod500 , to get any rom loaded with it
2. I copy RHODIMG.NBH, GBX_3.4.24_Full, recovery_cwr_6.0.1.3 all to my 4gb SDard
3. Vol- + PWR and phone turns to the tri color screen, then the phone started to load the image files
4. I press PWR butt to start the update, within a couple of seconds the phone update successfully
I press resest button for the phone to boot up to see if it will go to the fast boot screen.
But i was unlucky always the phone restart itself within some seconds.
This is my Prb
Click to expand...
Click to collapse
Ok. I see the standard steps outlined in the guide that you have done. Now what troubleshooting have you done?
denva said:
Thank you WizardKnight for replying me.
This is the steps i use to do.
1. I use RhodiumWUnlocker to unlock my rhod500 , to get any rom loaded with it
2. I copy RHODIMG.NBH, GBX_3.4.24_Full, recovery_cwr_6.0.1.3 all to my 4gb SDard
3. Vol- + PWR and phone turns to the tri color screen, then the phone started to load the image files
4. I press PWR butt to start the update, within a couple of seconds the phone update successfully
I press resest button for the phone to boot up to see if it will go to the fast boot screen.
But i was unlucky always the phone restart itself within some seconds.
This is my Prb
Click to expand...
Click to collapse
Sounds like you just need to flash CWM... the CWM recovery image doesn't go on your SD card, you flash that from your computer using the "fastboot flash" command...
You can also try "fastboot boot <recovery.img>" - w/o the < >. Remember, this is done on your computer. That's why you need the fastboot drivers...
arrrghhh said:
Sounds like you just need to flash CWM... the CWM recovery image doesn't go on your SD card, you flash that from your computer using the "fastboot flash" command...
You can also try "fastboot boot <recovery.img>" - w/o the < >. Remember, this is done on your computer. That's why you need the fastboot drivers...
Click to expand...
Click to collapse
Ok Can you guide me how to do this on the P.C. ?
denva said:
Ok Can you guide me how to do this on the P.C. ?
Click to expand...
Click to collapse
It's in the guide, is it not...? Please read the guide. It walks you through everything necessary...
Edit - following the guide, you should be on step 9 at this point. Please continue with the guide.
arrrghhh said:
It's in the guide, is it not...? Please read the guide. It walks you through everything necessary...
Edit - following the guide, you should be on step 9 at this point. Please continue with the guide.
Click to expand...
Click to collapse
You Mean This .
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
My Phone doesn't bring this window
denva said:
You Mean This .
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
My Phone doesn't bring this window
Click to expand...
Click to collapse
You described this screen (scrolling text, blue background?) I remember you said you got it to fastboot, no?
Where is your phone getting to?
edit: nevermind fiddled with it, dont know what i did but it worked
I have a rhod400. I have been messing with OMGB as my daily phone OS since July 2012 and just installed this one about a week ago.
I have two questions/issues
1) Every time I try to reboot, it freezes. When I try to power off, it sometimes freezes, but usually reboots.
2) I can't seem to make persistent changes to the hosts file. After every reboot, it's set to the same old generic "127.0.0.1 localhost"
During boot, does the OS unpack a .img or something with the hosts file packed inside it? If so, where is it?
Thanks, guys. Other than these 2 issues, this flavor of android for rhodium is pretty solid. i like it.
jdoggsc said:
I have a rhod400. I have been messing with OMGB as my daily phone OS since July 2012 and just installed this one about a week ago.
I have two questions/issues
1) Every time I try to reboot, it freezes. When I try to power off, it sometimes freezes, but usually reboots.
2) I can't seem to make persistent changes to the hosts file. After every reboot, it's set to the same old generic "127.0.0.1 localhost"
During boot, does the OS unpack a .img or something with the hosts file packed inside it? If so, where is it?
Thanks, guys. Other than these 2 issues, this flavor of android for rhodium is pretty solid. i like it.
Click to expand...
Click to collapse
Please put rom specific questions in that rom's thread.
If you are running a newer than.27 kernel the reboot and power off functions do not work properly in any rom.
I believe that the host file is overwritten by the ram disk/boot.img on boot every time. Any changes will not stick.
There is a chance these issues may be fixed on the next release of GBX, but no promises.
arrrghhh said:
You described this screen (scrolling text, blue background?) I remember you said you got it to fastboot, no?
Where is your phone getting to?
Click to expand...
Click to collapse
My Device always restarting after passing through all the tutorials
denva said:
My Device always restarting after passing through all the tutorials
Click to expand...
Click to collapse
This isn't enough information to help you.
If you're not going to provide detailed information on what is happening, no one will be able to help you.
Perhaps NAND is not for your device. Flash back to WinMo.
arrrghhh said:
This isn't enough information to help you.
If you're not going to provide detailed information on what is happening, no one will be able to help you.
Perhaps NAND is not for your device. Flash back to WinMo.
Click to expand...
Click to collapse
Yeah sir i think so , bcz av search all ova the net only rhod400 is ok
Unlucky for rhod500 am waiting maybe nxt update
anyway thank you arrrghh and wizardknight for your help :good:
Guys,
I'm rooted, with MDK base, and THOUGHT I had a working version of CWM (maybe 6.0.2.3?)
I was in the process of getting ready to try out a new ROM; going through the usual motions, formatting system, data, cache, and for good measure, I finished with a Wipe Data/Factory Reset (which I believe just does the same things again).
The phone suddenly rebooted and froze at the samsung custom screen. When I try to get back to recovery, I can't (hold down up-vol and power; blue message appears and disappears quickly in upper left, and back to Samsung custom lock screen.
I'm stuck. In the past, I always got into recovery by rebooting with ROM Manager, so I haven't really had to use the power-on/ vol up method (thus it may never have worked).
I can get into download mode. So I'm thinking - assuming - that the first thing I should try is to Odin CWM. But I'm admittedly confused, because all of the posts that relate to installing CWM seem to be in the context of the rooting process, and assume you have the ability to place certain files in rooted directories (like loki), which I obviously can't b/c I can't boot.
1) Is re-flashing CWM the right approach ? If so, is there a .TAR file somewhere with just CWM? I can't find an Odin-flashable .tar. EDIT: I found one, but it's designated for i9505. Same thing?
2) If that's not the right approach (or I'm just an idiot and don't know how to get into a working recovery), please advise
Thanks!
Turn the phone off.
Hold volume up and press the power button until it vibrates.
When it vibrates let go of the power and stay holding volume up until you see the recovery splash.
I've found that sometimes continuing to hold the power button will cancel the call for recovery boot. Not sure why.
You can always Odin if that doesn't work.
And I don't know of an Odin package for vzw recovery.
sent from my GE gs4
Dubbsy said:
Turn the phone off.
Hold volume up and press the power button until it vibrates.
When it vibrates let go of the power and stay holding volume up until you see the recovery splash.
Click to expand...
Click to collapse
O - M - G !? Unbelievable. Thanks a BILLION! You just saved me a ton of time.
EDIT: Cr*p. Not out of the woods yet. Now, when choosing 'Install from SD Card' I'm getting 'E: Can't mount /sdcard/'
I'll post this issue in a separate Q.