So, when you install the Alpha CyanogenMod 7 build, chances are ClockworkMod Recovery will fail. This tends to be because the custom overclocked kernels in WebOS take up a lot of room in the /boot partition, and ACMEInstaller does NOT (And maybe cannot) resize this partition. If you want to use ClockworkMod, you need to boot it via novacom.
1. Unzip the update-cwm_tenderloin-1012.zip file into the same directory as Novacom.
2. Make sure your TouchPad is plugged into your computer, and reboot it while holding volume up. You should see a USB icon.
3. In the command line, browse to the directory Novacom is installed in.
4. Type this into the command line prompt:
Code:
novacom boot mem:// < uImage.ClockworkMod
You should now be able to flash gapps or whatever else you need to install (Except moboot, which you need to use ACMEInstaller to install)
Novacom is probably installed in: "C:\Program Files\Palm, Inc" for most users.
To get there in the command line, type:
Code:
C:
cd "C:\Program Files\Palm, Inc\"
Then you can continue on to step 4.
Thanks for this info , it worked great. So am I to assume if I remove overclock Kernel thenI wont have this problem and will be able to install CWM through ACme with no problems ?
Edit. Tried to uninstall F15C to no avail.
27scoob said:
Thanks for this info , it worked great. So am I to assume if I remove overclock Kernel thenI wont have this problem and will be able to install CWM through ACme with no problems ?
Edit. Tried to uninstall F15C to no avail.
Click to expand...
Click to collapse
I don't know, but I kinda suspect not, because I brought my touchpad back to stock and *completely* wiped my touchpad before installing CM7, and I had problems with installing CWM through ACME. I don't understand the inner workings, but that seems like it may answer your question?
OP: Thanks!!!
Reckon I will be tied to a cord when it comes to CWM ....
The oc kernels get written to the main boot partition... I'm unsure which, but one of the oc kernel's can consume too much space, not leaving enough room to flash cwm... try booting into webos and removing your oc kernels... and try again... you don't have to flash the entire thing... you can just flash the cwm with the acme installer...
thanks!
I am in the CWM-based Recovery v5.0.2.6 but nothing works, not even the reboot option... any option i select does nothing.
any ideas?
Hold home and power, go back to USB download, start ACME install process from step one. If you follow instructions exactly, it should all work. There are occasions where you need to do the same thing twice... but your patience will pay off.
Yeah I tried to remove the F15C overclock kernel and do just that with the installer . No dice , can't remove the OC kernel go to remove it and reboot to replace and it just reboots into F15C then in Preware go to put the stock kernel on goes through shows install asks for restart and just boots F15C back again .. I have also tried to just flash the CWM zip afew times throught the installer and get the error half way through about there not being enough available space..ugh..
Try installing one of the smaller oc kernels through preware? If not, crack out the webOS doctor..
WebOS Doctor
Tried several times, but the recovery boot did not respond, i see the menu options, backup/restore, reboot, install from ZIP, etc... but when I select the options they didnt do anything...
After several tries I decided, let me start all over so I installed webos doctor. Unfortunately I cannot share the link here..
Unfortunately after I ran it and finally clicked DONE, my touchpad wont boot, has a battery icon with a question mark inside. (The battery level should be at least 25% before you run WebOS Doctor). I left it charging for at least an hour but still on the same status, so I assume it got bricked when running the webos doctor. If the battery just went bad at the same time it would be a big coincidence.
There is a chat support which seems to be pretty good. DO NOT TELL THEM that you were trying to install Android, I assume you all know that lol..
portal dot webos dot com (Sorry, couldnt share the link here)
If battery doesnt work in an hour or 2, then I may have to send it back to repair...
My CVM recovery works.
When I did the install yesterday I put the cm install,cvm,mboot and market all in the cminstall folder everything installed except the cvm, went back into webos and put it back in the cminstall folder and ran the ACMEInstaller again and it was there this time.
Used the CVM to install the google market update this morning.
I had Webos O/C also
I installed mboot, cm7, and cwm with acmeinstaller and my CWM works just fine. Flashed gapps with it no problem....seems like a strange problem for you and misleading if you ask me
I had a similar issue getting clockwork to flash. The problem is that some custom kernels take up too much space in the boot partition and doesnt leave enough room for cwm. Changing your webos kernel should fix the problem.
Sent from my Android powered Tenderloin
crump84 said:
I had a similar issue getting clockwork to flash. The problem is that some custom kernels take up too much space in the boot partition and doesnt leave enough room for cwm. Changing your webos kernel should fix the problem.
Sent from my Android powered Tenderloin
Click to expand...
Click to collapse
That actually makes perfect sense to me...i probably never had an issue due to the fact i didnt mess with my webos kernel.
+1 for you sir
Stroid01 said:
I installed mboot, cm7, and cwm with acmeinstaller and my CWM works just fine. Flashed gapps with it no problem....seems like a strange problem for you and misleading if you ask me
Click to expand...
Click to collapse
Nothing strage or misleading the OC kernel is the culprit.. Just cause it orks fine on one device does not mean different things will happen on others ...Thats how things work and how this thread got started...
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
crump84 said:
I had a similar issue getting clockwork to flash. The problem is that some custom kernels take up too much space in the boot partition and doesnt leave enough room for cwm. Changing your webos kernel should fix the problem.
Sent from my Android powered Tenderloin
Click to expand...
Click to collapse
Yeah I thought the smae thing but I can not remove the F15C kernel.. I go through preware and uninstall , reboot , F15C boots up and then go back into preware and install stock kernel and then reboot and F15C still boots up. I have not tried to start from scratch with the Web DR. ... just trying to see if there are any other avenues try first..It's been fun trying to figure some out though lol...
27scoob said:
Nothing strage or misleading the OC kernel is the culprit.. Just cause it orks fine on one device does not mean different things will happen on others ...Thats how things work and how this thread got started...
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
Yeah I thought the smae thing but I can not remove the F15C kernel.. I go through preware and uninstall , reboot , F15C boots up and then go back into preware and install stock kernel and then reboot and F15C still boots up. I have not tried to start from scratch with the Web DR. ... just trying to see if there are any other avenues try first..It's been fun trying to figure some out though lol...
Click to expand...
Click to collapse
If you can't switch kernels you may have to use the doctor. Thats actually what I did before I found out about the kernel size. I didnt really care as I dont plan on using WebOS.
Sent from my PG06100 using Tapatalk
I have restored the palm kernel.
But ACMEInstaller doesn't resize partition a second time !
Is there a way to force the installation ?
The boot partition cannot be resized, at least not by ACME. That is the problem. In my opinion, pushing Clockwork Recovery via USB is preferable to uninstalling an OC'd kernel. You should rarely need to use Clockwork Recovery, and in fact, most things you would normally install using it would, in the case of the Touchpad, not work.
: (
I know this is kinda old but im new to this, But im having this problem, I just installed CM9 and it boots nd everything, But no gapps, I went to go flash them and clockwork mod disappeared. So i stumbled on to this, When it goes to flash threw novacom It blinks the linus penguins and white words then gos backinto the boot loader with no Clockwork Recovery. I tried twice, What do i do?
Just trying to install Android on the TP for the first time... I seem to also be having this problem. Is there an update to this problem? Any new fixes? Or is everyone just dealing with either getting rid of an overclocked kernel or being tethered to a PC to get into CWM?
Related
I downloaded a new rom to try out. It said to flash the rom, gapps, and the launcher so i downloaded it all and put it on my sd card. everything working fine.
So I went to the recovery mode, but my trackball won't scroll up or down. So i thought " Oh well" I went into rom manager, flashed my rom, and it rebooted. Turns out I was suppose to use the Android Recovery so I could flash everything first. So it boots up and everything and i can unlock it, but then it turns black. I can't do anything at all. Can't search for apps. So im stuck. My trackball won't scroll on the Recovery and I don't have any type of home. All i can do is reboot my phone. I've tried the trackball paper trick, alcohol trick, everything! I have no idea what to do. Any ideas?
Thanks,
Justin
Well, there is a trackball optional version of Amon_RA. It would have been a lot easier if you had a running system to install from, but if you can get the Android SDK installed and can run adb from your computer while you are connected via USB, you can use Scenario 4 to install the new recovery and then work from there.
I'm a Mac use myself, so I can't really help with you with getting the SDK on a Windows computer, but I am sure that there are others who can point you in the right direction.
Alternate recovery: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html (as I said, use the instructions in Scenario 4.)
adb set up instructions for windows
xxjustin24xx said:
I downloaded a new rom to try out. It said to flash the rom, gapps, and the launcher so i downloaded it all and put it on my sd card. everything working fine.
So I went to the recovery mode, but my trackball won't scroll up or down. So i thought " Oh well" I went into rom manager, flashed my rom, and it rebooted. Turns out I was suppose to use the Android Recovery so I could flash everything first. So it boots up and everything and i can unlock it, but then it turns black. I can't do anything at all. Can't search for apps. So im stuck. My trackball won't scroll on the Recovery and I don't have any type of home. All i can do is reboot my phone. I've tried the trackball paper trick, alcohol trick, everything! I have no idea what to do. Any ideas?
Thanks,
Justin
Click to expand...
Click to collapse
I got my trackball working again in recovery by pulling down on the usb port with my thumbnail while scrolling the trackball. That might help you get things working again. As others have said you should install the recovery made for inoperable trackballs.
Thanks everyone.
I do have a mac. And I'll be sure to look into adb
xxjustin24xx said:
I do have a mac. And I'll be sure to look into adb
Click to expand...
Click to collapse
The Mac is easier, actually.
Mac instructions that should be pretty good for installing the SDK. That's really all that you need to do - install the SDK. See http://androidforums.com/eris-all-things-root/125436-detailed-leak-root-tutorial.html
You just need steps 1 through 7 from that Mac tutorial. The rest of the instructions you would follow from Scenario 4 of the alternate recovery instructions.
Selling a fully rooted Droid Eris running CM7 port ROM for $90...interested PM me.
"Proudly running Skyraider 4.0 w/CleDinc red theme"
Skruffy Jew said:
Selling a fully rooted Droid Eris running CM7 port ROM for $90...interested PM me.
"Proudly running Skyraider 4.0 w/CleDinc red theme"
Click to expand...
Click to collapse
You're seriously hijacking threads for this? Why not just start your own thread for it or put it on ebay or craigslist?
CondemnedSoul said:
You're seriously hijacking threads for this? Why not just start your own thread for it or put it on ebay or craigslist?
Click to expand...
Click to collapse
agreed
now for the OP. I had the same issue and installed the trackball optional RA. went smoothly. (in fact trackball is working better again) If you feel more comfortable doing that through the ROM and using gscript, you can still use the trackball if you plug in the usb and kinda wiggle it around (similiar to the using your fingernail, like another has said). in fact it might scroll for you
good luck.
So basically i got the ICS Encryption unsuccessful error and now my phone wont get past the vibrant splash screen. I tried odining back to stock but it just goes to splash screen and then turns off. i cant get into recovery mode. please please pleaseeee help!
jig or get to download mode
odin EUGENE373_SamsungS_Froyo_PDA (read directions)
then flash back to stock then try not too "brick" the unbrickable vibrant again.
this does not fix the problem. the /data partition is the cause of the problem and i dont know how to fix it. repartitioning in odin doesn't fix it either. :/
I had the same thing happen to me.. ive tried everything i could think of
enter download mode
dvryu said:
enter download mode
Click to expand...
Click to collapse
and then what? anything i flash gets me bootloader screen. eugene's unbrickable rom gets me to stock recovery but buttons dont work in that rom to let me select anything.
Unfortunetly there is no fix as of now. The problem seems to be the internal flash memory 16gb is unable to mount. SD card (External) mounts perfectly fine as i was able to pull some files using adb commands. Hope you have a spare phone cuz there is no way to fix your phone as of today.
A warning to ICS rom users. You phone could potentially become paperweight so be extremely careful. You might want to consider using Gingerbread or some other rom other than ICS until someone finds a solution to this problem.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
Nirmalspeed said:
and then what? anything i flash gets me bootloader screen. eugene's unbrickable rom gets me to stock recovery but buttons dont work in that rom to let me select anything.
Click to expand...
Click to collapse
The buttons in recovery don't work after flashing Eugene's rom.
You can only reboot your phone through the adb command:
adb reboot
Of course you must also have the android debugging bridge installed on your computer to issue these commands. Including the SDK. Good luck.
i have two other vibrants in my family right now. what do you think i could do with those to fix mine?
http://forum.xda-developers.com/showthread.php?t=1447303
OP, what ROM were you running when this happened intially? Also what kernel?
I have been reading most of the morning and am looking into some things. Alex's thread does show how to workaround the problem but it seems that the internal sd is lost (for now).
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Woodrube said:
OP, what ROM were you running when this happened intially? Also what kernel?
I have been reading most of the morning and am looking into some things. Alex's thread does show how to workaround the problem but it seems that the internal sd is lost (for now).
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Click to expand...
Click to collapse
i was running ICS Passion 13 with the Kiss kernel that came with it. and i've looked around and many people with ics have gotten this problem both on our device and on the AT&T's captivate.
If you loaded Eugene's rom, and are stuck at the recovery, don't wait so long to type that adb reboot command and don't unplug the usb just type the command. let the rom load then get the phone back in download mode and flash the stock rom.
Eugene's rom properly set up will fix your issue. try again!
cotbu said:
If you loaded Eugene's rom, and are stuck at the recovery, don't wait so long to type that adb reboot command and don't unplug the usb just type the command. let the rom load then get the phone back in download mode and flash the stock rom.
Eugene's rom properly set up will fix your issue. try again!
Click to expand...
Click to collapse
that wouldn't work as the /data partition isn't being red by the phone. Nothing happens when i try that command.
These are the instructions, Eugene's rom write like a lowlevel format, either you are not following directions or you actually bricked the vibrant.
But....you say you've made it to Eugene's recovery if you did you should be good to go.
Okay, Now with the Caution Posted, Lets Begin with the Froyo that Don't Brick
I have Tested this 5 Time's to Make Sure! Only install What I Post!
First,
You must already Have Odin installed & Know how to boot into Down-loader Mode!!
Do Not Select Repartition In ODIN Flasher
Quote:
Installing...
Extract the .zip file
Open ODIN Flasher, Select the Pit File.
Select Eugene373_GalaxyS_Froyo_PDA.tar
Select start..
Second,
Once Odin had Done Flashed, & you are in Recovery Mode you will not be able to Access anything & need to be at a Computer with Samsung Driver's installed & a working SDK pre-installed..
Side note: you will get an error in recovery, Don't be worried!!!! Ignore this!
Third,
Open a CMD Prompt & type:
Quote:
adb reboot
Froyo with Downgrading back to Stock Possible:
Download here > EUGENE373_SamsungS_Froyo_PDA.zip
*Stock Froyo with*
~ Root
~ SuperUser.apk
~ Build.prop now Correct
~ Defualt.prop Also Correct
****
*Issue's
Volume Key are Reversed
****
*Not working*
~ Rom Manager via reboot to Recovery!
~ Selectable Menu in Recovery
~ 3.5 Head-jack
~ Hot Spot Tethering
sorry for stressing but, I have a 4yr old that loves playing with the vibrant and I think I've brought it back from every brick situation possible. As long as the vibrant has power, it will not stop! xd!
Okay folks, I am at oss and need to know if I am just flat out screwed or if maybe, just
Maybe I might have a shot at storing my EVO 3d. I was running meanrom. Everything was running smoothly but I decided to give ViperROM a shot. So I d a wipe, rebooted into recovery and flashed ViperROM. Initially I thought everything had gone according to plan until I realized something was amiss when I attempted to start 4g. 4g wouldn't start. I did some looking into and came to tonclusion that because as far as I could tell because I had been running meanrom when I flashed viper the kernel no longer stock was not compatible with viper. So I started flash image GUI, found stockkernel.zip on my sd card and flashed or so I thought the stock kernel in hopes that after I did then the 4g would work on ViperROM. Well I was mistaken. When the phone rebooted, after the initial HTC screen rather than next seeing the ViperROM boot animation my screen went black. It remained there laughing at me till the phone automatically rebooted and then once again went to a darn black screen. It seems my phone is stuck in an endless loop. HTC screen, black scree reboot, HTC... Ect. I then booted into recovery wiped again and tried to then just reinstall meanrom. Well, according twrp recovery the installation went smoothly but after HTC screen, my phone goes straight to black screen. Ive tried various variations of reinstallations and nothing has worked so far. Am I stuck like this or is there something that can be done. Any pointers or suggestions would be more than appreciated
le?OR am I
3ncrypt3d said:
Okay folks, I am at oss and need to know if I am just flat out screwed or if maybe, just
Maybe I might have a shot at storing my EVO 3d. I was running meanrom. Everything was running smoothly but I decided to give ViperROM a shot. So I d a wipe, rebooted into recovery and flashed ViperROM. Initially I thought everything had gone according to plan until I realized something was amiss when I attempted to start 4g. 4g wouldn't start. I did some looking into and came to tonclusion that because as far as I could tell because I had been running meanrom when I flashed viper the kernel no longer stock was not compatible with viper. So I started flash image GUI, found stockkernel.zip on my sd card and flashed or so I thought the stock kernel in hopes that after I did then the 4g would work on ViperROM. Well I was mistaken. When the phone rebooted, after the initial HTC screen rather than next seeing the ViperROM boot animation my screen went black. It remained there laughing at me till the phone automatically rebooted and then once again went to a darn black screen. It seems my phone is stuck in an endless loop. HTC screen, black scree reboot, HTC... Ect. I then booted into recovery wiped again and tried to then just reinstall meanrom. Well, according twrp recovery the installation went smoothly but after HTC screen, my phone goes straight to black screen. Ive tried various variations of reinstallations and nothing has worked so far. Am I stuck like this or is there something that can be done. Any pointers or suggestions would be more than appreciated
le?OR am I
Click to expand...
Click to collapse
Your phone is alright and working , dont worry.
..............................................................................
I am assuming you are unlocked via htcdev.com .
Follow the steps:
Copy the img file of the recovery you are using to the fastboot/adb folder (folder which you have used to unlock the bootloader).
1.Now boot your phone in bootloader
2.Select Fastboot and connect to PC.(phone should say "fastboot-usb")
3.now open command prompt and navigate to your fastboot folder.
4.Type "fastboot boot <recovery name>.img". Your recovery should boot now.
5.Wipe everything , and install any ROM you want.
6.Then reboot your phone as normal and your problem should be solved.
7.If you get stuck at HTC screen or that black screen , just open the zip file of the ROM that you've just flashed and copy the boot.img file to your fastboot/adb folder > then boot your phone into bootloader > select fastboot > connect to PC > in command prompt type "fastboot flash boot boot.img" > then reboot.
Hope this helps........
Did you make a nand backup before you flashed vipers rom? Or do what he said ^^^^^^^
Did you look in the meanrom folder on ur SD card. Inside of there is the stock kernel. Second try to flash cleanROM and see if that helps. And if that doesn't work, look for the modifiedsuperwipe.zip. if all else fails..... I had the boot loop a while a go. All I did was flash the modifiedsuperwipe.zip and then flashed the ROM of choice and i was good to go. Hope this helps a lil
I'm stumped
So I did the modified wipe. I thought it was going to be smooth sailing well, I plugged in the phone and went to fast boot tried sending my phone a command line but it hangs on waiting for device. So now I'm stuck wondering wtf. No go on fastboot commands for now that is unless someone has an idea on that. Is there a way to perhaps browse root from recovery and transfer the boot image from my sd card to the folder in needs to. Go to? Or can I mount as a usb storage device and move the boot.img file to where it needs to go from the computer. I'm so desperate to fix this issue without surrendering to defeat and bringing it somewhere for someone else to do it. Hell I probably can't afford it if I have to. Whelp, if you have any thoughts I'm grateful. Thanks for the assistance thus far fellas. When bootloader loads it says I believe loading PG86DIAG.zip no image found if that means any more to any of you. I also tried reinstalling meanrom. I booted into recovery via hold power +. Volume up then choose recovery. Twrp loads. Choose meanrom zip flash image. According to twrp this goes down swell with not a problem but when I boot to system still I get the black screen. It mocks me still.
oh yes. Probably worth mentioning. Today I was working from a bit installation of windows. It was a pain on the as o get the adb drivers workingnet but finally found something called pdapal installed it and it got things squared away or so I thought on the windows drivers side of things. So in device manager there are no errors and it says the android device is working properly now alert symbols over the driver or anything but still can't get the phone to accept fastboot commands.
3ncrypt3d said:
So I did the modified wipe. I thought it was going to be smooth sailing well, I plugged in the phone and went to fast boot tried sending my phone a command line but it hangs on waiting for device. So now I'm stuck wondering wtf. No go on fastboot commands for now that is unless someone has an idea on that. Is there a way to perhaps browse root from recovery and transfer the boot image from my sd card to the folder in needs to. Go to? Or can I mount as a usb storage device and move the boot.img file to where it needs to go from the computer. I'm so desperate to fix this issue without surrendering to defeat and bringing it somewhere for someone else to do it. Hell I probably can't afford it if I have to. Whelp, if you have any thoughts I'm grateful. Thanks for the assistance thus far fellas. When bootloader loads it says I believe loading PG86DIAG.zip no image found if that means any more to any of you. I also tried reinstalling meanrom. I booted into recovery via hold power +. Volume up then choose recovery. Twrp loads. Choose meanrom zip flash image. According to twrp this goes down swell with not a problem but when I boot to system still I get the black screen. It mocks me still.
Click to expand...
Click to collapse
4ext has kernel flashing for hboot 1.5 works good i am no good with hboot i got lucky i got soff in 1.5 look into 4ext its a good recovery
Thanks
I've got twrp flashed fine. However my phone won't respond to commands while in fastboot from the command prompt. It says waiting for device and never responds. Is there a possibility that usb debugging is not working. Is there a way to the? this on from recovery if you needed. I'm not nt intimidated by advanced procedures Im an analyst programmer and am stuck doing super boring things most of the day. I can't believe I'm being thrown a curve ball like this. I'm definitely humbled. Just saying that anything you throw out there Ide be willing to give a shot at this point.
3ncrypt3d said:
I've got twrp flashed fine. However my phone won't respond to commands while in fastboot from the command prompt. It says waiting for device and never responds. Is there a possibility that usb debugging is not working. Is there a way to the? this on from recovery if you needed. I'm not nt intimidated by advanced procedures Im an analyst programmer and am stuck doing super boring things most of the day. I can't believe I'm being thrown a curve ball like this. I'm definitely humbled. Just saying that anything you throw out there Ide be willing to give a shot at this point.
Click to expand...
Click to collapse
could be the abd drivers are not on your pc for your phone the reason i said to get ext4 recovery is you can flash kernels now you still cant do that with twrp but with your phone plunged in, in fastboot go to my computer right click propertys go to hardware tab click device manager and look for a question mark that says android phone if it is their you need the drivers
hope i helped you out
3ncrypt3d said:
I've got twrp flashed fine. However my phone won't respond to commands while in fastboot from the command prompt. It says waiting for device and never responds. Is there a possibility that usb debugging is not working. Is there a way to the? this on from recovery if you needed. I'm not nt intimidated by advanced procedures Im an analyst programmer and am stuck doing super boring things most of the day. I can't believe I'm being thrown a curve ball like this. I'm definitely humbled. Just saying that anything you throw out there Ide be willing to give a shot at this point.
Click to expand...
Click to collapse
Are you sure you are accessing fastboot from bootloader ? By your words, it seems like you are checking fast boot in settings> power
Does the bootloader say fastboot-usb? If not select it and press power.
Sent from my PG86100 using XDA App
Still Trying
Yeah, I'm definitely in fastboot through bootloader. Yes it says fastboot usb. I think despite the fact that it says drivers are installed properly in device manager there might still be some kind of driver issue. I'm away from home and don't have access to. My usual computers? I'm stuck on an installation of windows 7 64bit. Originally I was having issues getting the right drivers installed and so I installed pda net and that seemed to solve the issue in device manager but I'm still having issues. If there's some recovery I could flash which would allow me toove boot.img to the right path manually that might be a way I could solve this. Hell, I'll give anything a try. So that's where I am so far. Any advice on what I might be doing wrong or where I might go from here?
hboot 1.5 s-on
I've got the same specs as you save the rom and kernel. @ itzloltraim.
I did try flashing clockwork mod using rom manager before my phone started having issues but even though rom manager said it flashed when I booted to recovery next twrp was still there. Is there somewhere I can download a flashable zip from? I couldn't find one last time I looked. From what I remember the Dev Site Links to rommanager to get it. If you have a link that would be a help.
Questions
Hboot?
Base?
Have you tried flashing clockworkmod?
Sent from my PG86100 using Tapatalk
iTzLOLtrain said:
Questions
Hboot?
Base?
Have you tried flashing clockworkmod?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
That plus what is he doing rooting or trying to flash a recovery?
Yea, I have the same problem...
I was running MeanROM4.1 with the dodava kernel. Being an idiot I flashed the new Anthrax kernel and now my phone gives me a black screen. When the phone starts up, theres no lock ring. Ive been trying to flash another kernel but i dont seem to be doing it properly. im using 4ext as recovery.
Im currently performing a Superwipe then factory reset. Ill reply with my findings. Good thing I backed up at MeanROM3.91, but if I cant get my screen to work...shall I assume bricked?
**problem solved. I flashed a kernel using the fastboot method. Someone posted it and it worked fine for me.**
Hello, I am new to this whole smartphone world, and I have no idea what to do next.
I asked in multiple forums why my new battery's life sucks even after calibration, which after reboot the battery goes from 65% to 98%, everytime.
So I was told to get CWM for my atrix, and last time I did, I almost got bricked. I got this error:
SVF:105.1:2
Failed to boot 0X1000 -- I always thought this was a HARD BRICK
I have root access and unlocked, using T-Mobile, and everytime it boots it says "unlocked" at the top during the Motorola logo.
So what are my steps to get CWM on the phone (for 2.3.6), and will my phone still work with t mobile, and will my battery not die in 20 minutes of reading text?
You can install CWM, either through fastboot (recommended) or through ROM Manager (personally I dislike it). However I don't think any of this is likely to fix your battery issues. Unless you're seriously exaggerating, your battery draining so fast could indicate some hardware problems. Might just be time for a new battery.
ravilov said:
You can install CWM, either through fastboot (recommended) or through ROM Manager (personally I dislike it). However I don't think any of this is likely to fix your battery issues. Unless you're seriously exaggerating, your battery draining so fast could indicate some hardware problems. Might just be time for a new battery.
Click to expand...
Click to collapse
Oh I see. Could you provide me a link, can't seem to find one for 2.3.6.
Also the battery is BRAND NEW, got it yesterday in the mail, and the phone is new as well.
Hm, then I guess it shouldn't be a hardware failure.
CWM has nothing to do with your OS or its version. Just flash whichever you want (the latest version would make the most sense).
ravilov said:
Hm, then I guess it shouldn't be a hardware failure.
CWM has nothing to do with your OS or its version. Just flash whichever you want (the latest version would make the most sense).
Click to expand...
Click to collapse
Ah okay, would I get this error again:
SVF:105.1:2
Failed to boot 0X1000
Also flashing CWM doesn't delete stuff right? Only flashing custom ROMS does?
I don't know if you'll get that error or not, but that error is easily solvable. Yes, like I said, CWM has nothing to do with your normal system unless you're flashing the system through CWM.
Please read this thread, most things are already explained there.
ravilov said:
I don't know if you'll get that error or not, but that error is easily solvable. Yes, like I said, CWM has nothing to do with your normal system unless you're flashing the system through CWM.
Please read this thread, most things are already explained there.
Click to expand...
Click to collapse
Okay! well how do I install CWM, nobody explains anything. I can;t find any steps anywhere. There are some, but say just flash it. Well what commands do I put in cmd? Idk what to do...
----------------
Okay I installed CWM recovery, but when I go into "android recovery" I don;t see all the the options. I mean I get past the triangle, but I only see four options.
Did I get cwm recovery or not? I followed the steps installing the .img file.
What options do you see? And what exactly did you install, and from where?
It's possible you installed some older version. Personally I use RomRacer's recovery which is based on CWM, pretty happy with it.
ravilov said:
What options do you see? And what exactly did you install, and from where?
It's possible you installed some older version. Personally I use RomRacer's recovery which is based on CWM, pretty happy with it.
Click to expand...
Click to collapse
I used the link you provided the second post shows how to load fastboot, and the third post show how to flash the recovery, and I used this: the latest CWM recovery from here, which is the newest.
I see reboot at the top
"wipe data/factory reset"
wipe cache partition
and wipe baseband data
can I follow this? I did this before and bricked the phone
Hm. Not sure why you'd want to follow some random tutorials on random sites. Everything you need is available on this forum alone.
Also, no idea why you see only those options, there should be much more AFAIK...
I'm using this recovery, it might be old but it's rock-solid, reliable and dependable. Might want to try with that one. The procedure is the same, just with a different IMG file.
ravilov said:
Hm. Not sure why you'd want to follow some random tutorials on random sites. Everything you need is available on this forum alone.
Also, no idea why you see only those options, there should be much more AFAIK...
I'm using this recovery, it might be old but it's rock-solid, reliable and dependable. Might want to try with that one. The procedure is the same, just with a different IMG file.
Click to expand...
Click to collapse
GOT IT!!!! Finally! my computer was acting weird and I guess the moto drivers didn't install properly. After reboot and new drivers on comp, it flashed fine and I am in cwm recovery. I flashed this: 0408_1720-signed.apk
so I guess from there could I clear the battery stats, after 100% charge, then let die and charge again off?
Aregvan said:
so I guess from there could I clear the battery stats, after 100% charge, then let die and charge again off?
Click to expand...
Click to collapse
Yes, it's worth a shot. Won't do any harm and it might just fix your problem.
MY GOD PROBLEM AFTER PROBLEM!!!
So after installing cwm recovery. I wanted to fix the crappy battery, so I let the phone on until it died, and connected the phone to the wall charger, and it boots into CWM automatically.
I don't even see the charge screen. After hitting reboot, the phone than boots into the normal android OS.
SO HOW can I charge the phone when it's off, without having it turn on by itself?
---
Okay WTH! Now it boots fine, but won't get into CWM recovery. Even selecting android recovery takes me to the crappy stock recovery with the four options only. WTH is wrong?
I am going back to $10 phones.
Good bye.
Hmm, I don't know... Either you're doing something wrong (no idea what) or your device is borked in some way.
Maybe someone else can chime in...
Yo.
So nothing whatsoever seems to be able to make this phone boot into recovery. Whether its a soft or hard boot, it just will not happen. It will always boot as normal. I'm so frustrated and completely stumped.
Any ideas?
James Bartlett said:
Yo.
So nothing whatsoever seems to be able to make this phone boot into recovery. Whether its a soft or hard boot, it just will not happen. It will always boot as normal. I'm so frustrated and completely stumped.
Any ideas?
Click to expand...
Click to collapse
How did you install recovery?
How are you trying to boot into recovery?
blueether said:
How did you install recovery?
How are you trying to boot into recovery?
Click to expand...
Click to collapse
Ah man, you've got me. This is all in the hope of installing a custom rom. Installing the recovery was one of a few things I hadn't done before. I think I did it using Fastboot. I've got a head like a sieve. More frustratingly, my own PC died a death a few days ago, so A) I haven't got whatever stuff I downloaded so cant refer to that to see what I did, and B) anything from here on would ideally be done without a computer, although I could probably borrow one if needed. Can you use Fastboot to install a custom recovery? If so, then thats how I did it. I remember downloading a .img file on the PC and doing something from there. Sorry I couldn't be more clear, and thanks for your help buddy.
Sorry, I missed the second question there. I have tried a number of ways to boot into recovery. Holding vol-up or vol-down while powering on, or a handful of apps that have a boot into recovery option. I've tried using CWM's Rom Manager to install the PA rom .img I have saved on the phone, but that is telling me I need to install CW recovery, and then says its not available for my device. Confused as hell about that one. I feel that once I'm in recovery I'm golden. I don't know if this is relevant, but at the minute, I don't have write access to /system, so I guess this would be a half root job.
You still having issues? I can help and yes you will need a computer and you will need to download the android SDK and set that up.. Let me know