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
Related
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.....
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
I'm using [ROM]MIUI/CM7 Hybrid v3 multi-lang update 04/07/2012 and haven't had any issues whatsoever. Tonight I updated a bunch of Play Store apps that I've been putting off for a while and the only one that I could think of that could possibly have caused a problem is MiHome. Everything else was a pretty standard app/game.
Well my phone rebooted and now after it boots and shows the lock screen it goes blank a few seconds later. I tried unlocking it before it went blank and and I did see the home screen but it went blank again before the icons showed up. I can tell it's still on because there is a very slight glow from the screen if you look at it from an angle.
PLEASE HELP ME. I have no idea how to fix this and wouldn't even know where to begin!!
You've flashed a ROM before, you should know this already... Reboot into recovery, do a wipe data/cache (factory reset), reboot. If that doesn't work then wipe all and re-flash the ROM+gapps.
If you've been messing with system files, it's probably best to go straight to wipe all and re-flashing.
Re-install apps, re-configure the dozen or so apps you actually use on a normal day-to-day basis, and set a lovely wallpaper when you're done. 1 hour tops.
At the very least you'll be available for phone calls and text messages again within the next 10min.
Next time make sure to do a backup so you can restore a working copy of your data and cache whenever you need.
Unless you already know what the issue is, or how to fix it, sorry to say it, but the above steps are likely the quickest way to a resolution.
You're right I am very familiar with those steps but I can't reboot into recovery or any other method. My screen is blank and everything is unresponsive. The only way I can reboot is to pull the battery. I do remember there is a way to boot into recovery from a power off status but I can't remember how to do that.
BTW...thank you for your quick reply!
loanerdave said:
You're right I am very familiar with those steps but I can't reboot into recovery or any other method. My screen is blank and everything is unresponsive. The only way I can reboot is to pull the battery. I do remember there is a way to boot into recovery from a power off status but I can't remember how to do that.
BTW...thank you for your quick reply!
Click to expand...
Click to collapse
Hold down the volume-down key while booting up, when you see the Fastboot option appear, press the volume-down key repeatedly to cycle through the selections until you get to Android Recovery, then volume-up to select.
Try this:
- remove the battery
- press Volume Down and hold
- insert the battery (tricky part when holding Volume Down)
- wait till system menu appears
- release Volume Down
- press Volume Down again few times till "Recovery" shown.
- press Power
Thank you guys (or girls)! That's what I couldn't remember. Wiping now and will reinstall ROM.
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.
How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.