Related
I rooted my device using Gingerbreak.
I have 2.2.2 installed out of the box. I installed CWM. I installed busybox.
Busybox failed. I tried all the versions that it contains.
I checked root status, and RootCheckBasic says I'm rooted.
I installed Flash ClockworkMod Recovery. It will not reboot to CWM.
It only reboots to the standard Android recovery.
I'm trying to install Bumblebee ROM 2.4.
Here are some things I am having issues understanding with it...
Backup current apps and their data with Titanium Backup (available in the Market). Is this required? The phone is new. I have nothing to back up.
Do a nandroid backup in recovery before doing anything else below.
And the nandroid backup is done with CWM? Again CWM won't reboot, only the standard Android recovery boots.
Required if installing BB 2.x for the first time: Wipe. Wipe it all. Data, cache, system, dalvik-cache, sd-ext if you've got it (might need to look under Advanced or Mounts in recovery to do the last two, and while you're there format /system). I assume you wipe it all with CWM while in recovery?
If upgrading from BB 2.3, wipe cache (and only cache) in recovery.
Does not apply to me
If not upgrading from 2.3, install Wiper zip (see below), just to be extra sure that all is wiped. Don't reboot yet. Installing wiper.zip is done by sideloading using adb commands?
Install ROM zip (see below).
I assume this too is done by copying the zip to the external SD, then selecting update from SD card in recovery... right?
Please someone shed some light on this for me.
In standard Android recovery it says e3. I know on my Captivate I had to use Odin to install GB loaders to get it to work.
THANKS!
Flashwork mod recovery? Never heard of it.
Try downloading rom manager from the market and use that.
Everything else should be simple
tvall said:
Flashwork mod recovery? Never heard of it.
Try downloading rom manager from the market and use that.
Everything else should be simple
Click to expand...
Click to collapse
Flash ClockworkMod Recovery
It's in rom manager.
Which I installed from the market.
But I don't get the CWM recovery when I reboot into recovery mode.
I get the standard Android recovery
-you know... the one that just has "install update.zip"
bulltproof said:
Flash ClockworkMod Recovery
It's in rom manager.
Which I installed from the market.
But I don't get the CWM recovery when I reboot into recovery mode.
I get the standard Android recovery
-you know... the one that just has "install update.zip"
Click to expand...
Click to collapse
Oh, okay, um... are you using the reboot into recovery option in rom manager right after flashing?
After flashing what?
I reboot into recovery through rom manager and get:
Android system recovery <3e>
reboot system now
apply sdcard: update.zip
wipe data/factory reset
wipe cache partition
_________________________________________________________
Android System recovery...
Do not pull out the battery!!
After hitting flash clockworkmod recovery, immediately hit reboot recovery
After hitting anything in CWM it did nothing more than reboot into the standard android recovery.
This phone has 2.2.2 on it. Problem? Probably.
I followed instructions at androidcentral and got it to work.
Needed Xionia_CWMA_12518.6_VM
Installed BACKside-IHO-VM670-11222011
using Xionia_CWMA_12518.6_VM_Recovery-signed
Had a little problem today and needed to activate the phone. BUUUUT......
the rom didn't allow activation.
So I installed Bumblebee. No go.
Then I tried [rom] basic stock rom.
Neither of these will let my phone boot. It gets stuck at boot.
Nothing happens.
I can still boot into Xiona_CWMA. But no roms will work.
PLEASE HELP!!!!
Dude i m noob, and i m facing same problem,
I did root with super one click soc, and it is rooted and i am using root needed apps,
But when i m trying to clobk work recovery (i did flashing CWR from rom manager and aft that i select boot from cwr option from rom manager) it just factory reset i did this 3time all time just factory reset, then i again did but while rebooting i click home button so it gave me same option which came to above member said some e3............
And i try to select any option from it with menu button it was not applied, and no use so i removed battry and place again and start then device started dont know more what to do, help
Sent from my LG-P500 using Android-HQ App
Ok, so I CAN load different recoveries.
They work, or at least seem to.
I can flash roms, but nothing happens (bootloop) or the phone comes on and works with a black screen.
I can call my number and can hear the call, but can't see anything.
Bullet if u found solution pls tell me too
Sent from my LG-P500 using Android-HQ App
bulltproof said:
Ok, so I CAN load different recoveries.
They work, or at least seem to.
I can flash roms, but nothing happens (bootloop) or the phone comes on and works with a black screen.
I can call my number and can hear the call, but can't see anything.
Click to expand...
Click to collapse
I believe that may be due to the newer display in your phone (I'm new to this device so I dont know much yet). From the little bit of information I've gathered, devices manufactured recently have a different display that requires a kernel that supports it. In the iho roms this is included, on others you'll need to flash a kernel right after the rom.
For the stock rom I can upload what I use if you need it. Its basically the one posted here just with the boot.img swapped with one from a nandroid backup I made before switching roms
I think you're spot on with that idea.
I loaded CM7 variant, and it worked.
My question is, how do I get another ROM on it if it has the newer screen?
I loaded different kernels that were supposed to fix it, but no go.
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
New radios might help. Are you wiping EVERYTHING before flashing?
We're comin from a pure power source.
How can I flash this new radio? Just install .zip of the file from recovery, correct?
I do "factory reset" on the twrp 2.0 recovery before I install any rom
ninten5 said:
I do "factory reset" on the twrp 2.0 recovery before I install any rom
Click to expand...
Click to collapse
I'm using twrp2 and I do
Factory reset
Wipe cache
Wipe dalvic cache
Wipe system
Factory reset (again)
Flash Rom
Reboot system.
And i never have any bootloops or stuck in HTC white screen or any issues.
Sent From My Optimized R3Dimensions
Yea. Factory reset isn't enough. I encountered that issue when doin restores on me og evo. I had to wipe cache and dalvik to get it to work.
We're comin from a pure power source.
Use cwm older 4 version as recovery.
Fastboot boot recovery.img. make sure you have a copy of it in your adb folder.
Wipe everything and flash rom
OK ill try that.
What about backup and restores, my nAndroid backups don't work
ninten5 said:
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
Click to expand...
Click to collapse
Either one of two things:
your phone is defective
stop using so many apps for stuff like checking on system statuses. Just install a ROM fresh and leave it for a week with just your base essential apps like email and stuff. If the problem doesnt arise you know all your crap is causing it.
A radio update isnt going to do anything for a system issue as it is just your signal and stuff that the radio firmware would affect.
Sounds like the flash went bad due to not a full wipe or boot.img.
Twrp 2.0 is known to have its own issues.
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
ninten5 said:
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
Click to expand...
Click to collapse
Do this man
Get cwm 4.0 version ok now flash that then leave a copy of it in your adb folder where adb is...
Now make sure debug is on
adb reboot bootloader
fastboot boot recovery.img
Then wipe everything but not your SD card
and flash rom works this way just like the S off users use. You don't have to use flash gui or pull boot img..
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
ninten5 said:
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
Click to expand...
Click to collapse
cwm 4 is better for this phone dude. he said 4 not 5.
I just did the biggest F-Up of my flashing life. While following QBKing77's Rooting & CWM with unlocked, at approx 3:50, during the flashing of the root SYSTEM.img file, rather than that file, I used the wrong file to flash used an IMG file that was meant for cwm, which is a completely different task.
So now I am trying to get into fast boot and try to do it with correct SYSTEM.IMG, then to find out I never got it downloaded, the link was deadand now I can not find where to DL it from. I must've not been paying attention and got ahead of myself.
Anyone know where I can a mirror of the file found here. Its the first link in the root section labelled "moto-fastboot flashable /system image".
Am I screwed? Does anybody have a copy of that system.img file laying around. I can not find any mirrors. That is the only way I can see this getting fixed bc I can still go into fastboot mode.
ckeck this ????
http://rootzwiki.com/topic/4137-pudding-photon-pudding-bootloader-unlock-updated-8302011/
Use at own risk. ???
Can u get into rsd mode and flash 154_5 sbf
Sent from my MB855 using xda premium
Important files
Thank shabbypenguin for those
If you can get into rsd mode and connected/recognized in rsd lite you should be able to flash one of those sbf files and return to stock.
I read the instructions carefully! It said to put the oven on 350 degrees for 10mins but for some out of this world reason I put it on broil and let it cook for 20mins :/
Sent from my MB855 using XDA App
LOL no kidding Custodian. I did get a laugh out of that.
Thanks CubanLuke & ShabbyPenguin. I did use RSDLite to flash the current sbf you directed me to, I can boot into the phone again. Thanks again.
Now as to how to proceed, I will have to unlock the bootloader again, np, but when I run into that very step where I broiled it, the rooting via speedboot.... would it be okay to root using AIO instead because I can not find the SYSTEM.IMG needed to follow along w/ the video using this method.
Can I just root a different method, then proceed on with CWM recovery, then flash rom from the video?
enzyme said:
LOL no kidding Custodian. I did get a laugh out of that.
Thanks CubanLuke & ShabbyPenguin. I did use RSDLite to flash the current sbf you directed me to, I can boot into the phone again. Thanks again.
Now as to how to proceed, I will have to unlock the bootloader again, np, but when I run into that very step where I broiled it, the rooting via speedboot.... would it be okay to root using AIO instead because I can not find the SYSTEM.IMG needed to follow along w/ the video using this method.
Can I just root a different method, then proceed on with CWM recovery, then flash rom from the video?
Click to expand...
Click to collapse
- Unlock using derpunlock.sbf
- use fastboot to erase recovery and install CWM recovery
- boot into CWM
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
SOLVED!!! THANK YOU EVERYONE!
KTT16 said:
- Unlock using derpunlock.sbf
- use fastboot to erase recovery and install CWM recovery
- boot into CWM
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
Click to expand...
Click to collapse
Thanks KTT. Okay, I'm back on track now. I am unlocked again, rooted as well. but I am not sure about 2 things. This will be my very first android rom flash and just coming from a big whoopsies, I just want to be sure.....
1) Format system: in cwm recovery, which option is that? I don't see "format system" in the main or advanced menu. Maybe its worded differently?
2) Flash ROM: I can only assume its either "Apply Update from SD" or Update from SD". Not sure which one though.
enzyme said:
SOLVED!!! THANK YOU EVERYONE!
Thanks KTT. Okay, I'm back on track now. I am unlocked again, rooted as well. but I am not sure about 2 things. This will be my very first android rom flash and just coming from a big whoopsies, I just want to be sure.....
1) Format system: in cwm recovery, which option is that? I don't see "format system" in the main or advanced menu. Maybe its worded differently?
2) Flash ROM: I can only assume its either "Apply Update from SD" or Update from SD". Not sure which one though.
Click to expand...
Click to collapse
1) Format system is in the "mount" options. Although it's unneeded to flash a ROM. Personally I just wipe data/factory reset and then wipe cache and have zero issues. Others may tell you different though.
2) "Install .zip from SD Card" then select whichever .zip you're looking to install.
Sent from my MB855 using xda premium
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Flashing the 198_7 sbf unroots and relocks, so you're back to square one.
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Reboot into stock recovery, when you get the recovery logo thing push both volume up and volume down at the same time to get the recovery options. Then do a factory reset and it should boot for you. After that, root and unlock again. And you didn't have the Market because you forgot to install Gapps...
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
The reason cm7 didn't have the market is that you needed to flash gapps. Try doing a hard reset. http://www.hard-reset.com/motorola-photon-4g-hard-reset.html That should do it.
try the 154 sbf
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
i had the same problem i think and was going thru boot loops but some one told me to start into recovery when you try you get that ? android screen from there hold down volume up and down at same time then wipe phone booted up fine after that.
It worked like a charm. Thanks. I'm still very new to android and hate to admit it but will be running into problems like these again. The best way to minimize it for me is, not only follow certain directions correctly to get out of these binds, but to understand them.
- So theres an image of the stock ROM stashed away on the phone regardless? And it can be accessed only via the stock recovery? Because after I succeeded in flashing cm7.1, I did a factory reset once from settings>privacy and that restored me to a fresh CM7.1. The factory reset from settings>privacy and in CWM is the same, but both different from the factory reset via STOCK RECOVERY?
- Also what would be the correct method to go from one custom ROM to another? Would it be this? :
(in CWM)
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
Or can I just jump to install from zip ?
- Also regarding SD Storage (internal), only holds storage files? So on any fresh ROM there shouldn't be anything in that partition relating to that new ROM yet right? So I can delete things without worry?
You should not have to reboot into recovery, once your wipes are complete, normally you can just flash your ROM of choice in the same recovery session.
Before I flashed anything I would make a backup with CWM so you don't have to keep rooting and unlocking. You can just restore your backup.
Sent from my MB855 using xda premium
After flashing 198 7 sbf, all u need to do is flash derpunlock not go through oem unlocking, then reflash recovery.
Simple generic process for going between roms (assuming already unlocked + cwm recovery flashed; process may be different for some roms, always make sure to read directions, but this is the general concept)
1. Download rom (and gapps if necessary) and put on your sdcard
2. Boot into recovery and make a nandroid backup
3. You made a nandroid backup right?
4. Secure your nandroid backup (move it to your pc or something).
5. You know where your nandroid backup is right?
6. Wipe data/factory reset.
7. Install zip from sd (flash), choose the rom.
8. Reboot system.
At this point your rom should be all set. If for some reason you don't like it, simply boot into recovery and restore your nandroid backup. You can even make nandroid backups of various roms if you want to swap between them for whatever reason.
I've been running AOKP Milestone 6 for about 2 months now. It always had a problem unlocking the lockscreen at full battery as it didn't receive touch input so I just restarted the tablet. Then it would just reboot as the tablet would not turn off if the power button was held. I dont care. Dont turn it off enough for that to make a difference.
Well one day I woke up turned on the tablet and like normal there was no touch recognition. Oh well reboot like normal. Then my tablet stuck in the AOKP animation. It just froze. About halfway through the animation. I used the hard reboot (vol- and power) and it froze again at about the same place. I WTF and go to CWM and reflash the ROM and it froze at applying data. Hard reboot. Flash Galaxy Task. Freeze at applying data. Flash a backup I made on AOKP milestone 6. Froze at applying data. Plug into computer and flash stock root package. SUCCESS!! Then the AOKP boot animation comes up and freezes at the same place as before. I have no idea what to do as I decided I would flash 1 ROM and leave it on my tab because I've hard bricked my infuse before and didn't want to send this in have it come back broken and buy a new one.
Galaxy tab 10.1 wifi running http://forum.xda-developers.com/showthread.php?t=1459287
What version/mod of CWM are you running?
Grab CWM 5.5.0.4 at this address.works pretty well:
https://sites.google.com/site/arashtarafar/
Remember to wipe data/cache after flashing processes...
arashtarafar said:
What version/mod of CWM are you running?
Grab CWM 5.5.0.4 at this address.works pretty well:
https://sites.google.com/site/arashtarafar/
Remember to wipe data/cache after flashing processes...
Click to expand...
Click to collapse
I'm Running 4.0.0.4. Wasnt planning on flashing a lot of ROM so flashing that would be not so important to me. Checking that site out now.
I noticed I forgot to mention it's a wifi model. will update OP.
This currently happen to me too.
Will try to find 3g stock Rom and try to upgrade CWM
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 2
I am currently having this problem too.
It all started when my wifi started not working so I rebooted my tablet. Suddenly im stuck in a bootloop with no way to get out of it.
I'm able to access CWM and have tried wiping cache, but that didnt work. Now i've tried wiping /data but it freezes.
I'm unable to access my USB as it repeatedly says "E:unable to open ums lunfile (No such file or directory).
I've tried using ADB to push a new flash image which worked but im still stuck in a brand new bootloop (presumably because i cant wipe /data).
Can anyone help? I have NO idea how this happened.
Flash a stock ROM using Odin in download mode...now that you are in such trouble flashing a 3G ROM doesn't make much difference...
So, I was able to successfully unlock my bootloader, got TWRP 2.6 on it, and put a few different ROMs on my machine; however, I have yet been able to install a ROM and get it to move past the boot animation.
I have tried the latest nightly ROMs for CyanogenMod 10.1 and 10.2 for my TF201, both of which get stuck in CM's boot animation. I just tried the same with the newest Baked ROM, only to be stuck in its boot animation as well.
I'm trying to figure out if there was something I forgot to do. I have been able to revert to a backup of my stock Jellybean 4.1.1 that I stored using TWRP, but haven't been able to use anything else.
Are there any thoughts on this? Have I missed something? I was able to use the unlocker utility and each boot offers the confirmation in the top-left that my bootloader is unlocked. I am able to enter TWRP from the recovery mode. Shouldn't it be as simple as selecting a ROM's zip archive and installing it from TWRP?
Have you done a full wipe before installing, including cache and dalvik cache partitions?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Try installing twrp 2.5. AS I just read in another thread there are problems with 2.6..
Sent from my MB526 using xda app-developers app
Factory reset
After flashing CM 10.1 nightly last night i had the same issue. I booted into my recovery console (flatline cwm) and performed a factory reset. This seemed to clear whatever issue was bothering the tablet. Still sat there for about five minutes on the animation after the reset but then progressed into setup.
Doubt if it makes a difference but mine was connected to the dock too.
If you're still stuck the method that worked for me yesterday was:
Used Flatline CWM as the recovery, installed using fastboot
Used an external memory card to copy the relevant zip files to my sdcard, recovery couldnt find them otherwise using adb push
Installed from zip using Flatline CWM
Installed gapps using Flatline CWM
Booted, got the issue you had
Booted into recovery, performed a factory reset
Told recovery to restart the machine
Booted into setup screen after loading for a few minutes