Related
Hi. I tried installing a rom and know it just sits at the boot screen. I can get into ADB and it works. I have the Wifi Version. How would I get this thing back up.
Can you please post the links to files I need to download.
ysuleman said:
Hi. I tried installing a rom and know it just sits at the boot screen. I can get into ADB and it works. I have the Wifi Version. How would I get this thing back up.
Can you please post the links to files I need to download.
Click to expand...
Click to collapse
wrong section this belongs in Q&A but all you need to do is get into recovery (adb reboot recovery) and then try wiping data and re flashing the rom
Can you get into Clockwork Mod Recovery? If so, just reflash.
All you have to do is reboot the thing when you see the Motorola Dual Core screen (its red) count 3 seconds and press volume down. Select what ever option you are going to use to fix your device with the volume down. Volume up to select. Its very difficult to "Brick" a Xoom.
If ADB is working just use adb reboot recovery. If thats not working use the method above and use fastboot and reflash recovery, fastboot erase recovery then fastboot flash recovery recovery.img (or flash Tiamat recovery/Rogue).
something like that pretty easy really.
ysuleman said:
Hi. I tried installing a rom and know it just sits at the boot screen. I can get into ADB and it works. I have the Wifi Version. How would I get this thing back up.
Can you please post the links to files I need to download.
Click to expand...
Click to collapse
Go to the appropriate sub forum and ask this.
Hey everyone,
Basically I was trying to flash a new ROM onto an old Nexus S of mine and when I tried to boot into recovery there was just a black screen. I pressed the power button and a single line saying "Clockwork mod Recovery" and the version number popped up. I assumed that the recovery must've been corrupted so I erased it and installed the latest version using fastboot which seemed to work fine.
Now whenever I try to boot into recovery I just get a blank screen with nothing else. I've tried using other recovery images such as twrp but the same problem happened, I just get the background wallpaper/image and nothing else.
I searched the forums and apparently people were having this issue earlier on when the i9023 was first released but now most custom recoveries are supposed to work with both i9020 and i9023.
Also the touch buttons light up and vibrate whenever I touch them when I'm in recovery mode.
Any help to this problem would be greatly appreciated as atm I have an old ROM which is buggy as hell and I need to get rid of it.
Cheers!
I had the same Issue. If you can boot into the rom, you can try to download the rommanager-app and install the recovery from there.
Hey I tried that already that and instead of booting into recovery it just went into the bootloader and said "No Recovery or Bootloader found".
Any other ideas?
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Hey
I have the i9023 and I install rom manager. install CWM and if I reboot into recovery it works and I get in to CWM recovery.. but after reboot into os.. if I go into Rom manager and reboot to recovery it dont work? I just get the android figur and a "!".. then I just can Power + vol up and I'm in bootloader recovery..
Do I have to install CWM every time i want to use it? and can't I access CWM on boot op ?
sorry for my bad English
Normaly you have to flash the recovery only once.
Try to flash the newer clockwork-recovery with fastboot.
http://forum.xda-developers.com/showthread.php?t=988686
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
bedalus said:
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
Click to expand...
Click to collapse
I havent unlock my phone, but I can get in to bootloader is it then necessary to unlock ?
I try to delete the /install-recovery.sh
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Xziped said:
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Then it must be unlock as default.. I havent unlock it.. just delete the install install-recovery.sh and it works every time now.
now I just have to find a ROM to try..
Xziped said:
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Simultaneity said:
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Click to expand...
Click to collapse
what happens when you try to temporary boot into the recovery?
instead of "fastboot flash recovery recovery.img", try to "fastboot boot recovery.img"
Just look for an recovery.img that works temporary and then try to flash it permanently.
I'll try it and get back to you Xziped. If anyone else can think of any other ideas please just throw'em at me, I'm willing to try anything!
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Simultaneity said:
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Click to expand...
Click to collapse
Sorry but if not even the temporary recovery boots up, i dont know what else we can do
did you try some of the older recoverys? is your bootloader unlocked?
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Simultaneity said:
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Click to expand...
Click to collapse
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
khartaras said:
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
Click to expand...
Click to collapse
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Simultaneity said:
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Click to expand...
Click to collapse
Just look @ http://www.samfirmware.com/ .
There you should find all you need
Sent from my Full Android on Crespo using XDA App
Hellooooooooooooooooooooooooooooooooo!!!
this is my first thread in this forum, mi name is Nicolas and i ve a very big problem with my new tablet.
I was trying to install the new Jelly Bean (OS_Acer_RV09RC08.WW.GEN1_A41J_A) and everything was OK
I unlocked the bootloader .......and....
I try to root and just bricked....
Everytime i turn on the tablet i can see the "Acer logo" and the line: Bootloader Version JB-653b3d3 (Unlock Mode)
I cant get into the recovery mode.....
Sorry for my bad english....i need your help ppl!!!!
Thanks for ur time.
Nicolas.
May you can get into Fastboot mode and reflash the recovery.
Give it a try =)
Do you have a androids of your original ROM?
I did the exact same thing just yesterday...
If you have a JB image to work from, get it in fastboot mode and look at the thread on CWM Recovery 6.0.1.5...
Sent from my A700 using xda premium
thks for the replies.....
i downloaded the stock rom from the Acer web page
i tried with:
"adb reboot-bootloader" and NOTHING.....i ve the line: <waiting for the device> ....and ....5 min later nothing.
then:
tried to get the fastboot mode (vol + & PWR) and the tablet just get the same boot = nothing.
:crying:
freejack84 said:
thks for the replies.....
i downloaded the stock rom from the Acer web page
i tried with:
"adb reboot-bootloader" and NOTHING.....i ve the line: <waiting for the device> ....and ....5 min later nothing.
then:
tried to get the fastboot mode (vol + & PWR) and the tablet just get the same boot = nothing.
:crying:
Click to expand...
Click to collapse
To get into fastboot mode, it's the following combination;
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] then cycle your rotation lock button left and right till you see the the text start to appear.
Unless you;re going to try and fastboot a system image setup or recovery image or another boot.img, not sure what you wish to accomplish.
I would guess you would be better off installing maybe the GB full version JellyBean update.
Also, I understand there,s a a700 ICS service rom out there somewhere. That might help you also.
But these are just guesses at this point.
What would help, is to know exactly what you did to get yourself into this situation. Like What root procedure from what post? If you tried one of the ICS Boot.image flashes, when you had JB updated, well, no wonder it borked up. If that's the case, it's simple just to fastboot a JB Boot.img back in.
So which thread did you get the root procedure from EXACTLY?
One more thing, this thread belongs in Q&A Forum, so I put in a request to have it moved.
MD
Moscow Desire said:
To get into fastboot mode, it's the following combination;
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] then cycle your rotation lock button left and right till you see the the text start to appear.
Unless you;re going to try and fastboot a system image setup or recovery image or another boot.img, not sure what you wish to accomplish.
I would guess you would be better off installing maybe the GB full version JellyBean update.
Also, I understand there,s a a700 ICS service rom out there somewhere. That might help you also.
But these are just guesses at this point.
What would help, is to know exactly what you did to get yourself into this situation. Like What root procedure from what post? If you tried one of the ICS Boot.image flashes, when you had JB updated, well, no wonder it borked up. If that's the case, it's simple just to fastboot a JB Boot.img back in.
So which thread did you get the root procedure from EXACTLY?
One more thing, this thread belongs in Q&A Forum, so I put in a request to have it moved.
MD
Click to expand...
Click to collapse
Thks MD for ur instant reply.
Sorry for dont put my thread into the Q&A Forum. It was a mistake. Sorry again
My situation is: "like i remember" i tried to make the root with the "flash-ICS-patchedBoot.bat".....i know that BAT is for ICS and not for JB but i take that mistake doing the thing really fast. :angel:
Ok...i need them to get the fastboot with the JB Boot.img like you said.
The JB Boot.img is into the Rom??? because i saw the boot.img into the JB update.zip
Can u tell me the command to get that flash? Is "fastboot flash boot boot.img"?
Thks for ur patience
freejack84 said:
Thks MD for ur instant reply.
Sorry for dont put my thread into the Q&A Forum. It was a mistake. Sorry again
My situation is: "like i remember" i tried to make the root with the "flash-ICS-patchedBoot.bat".....i know that BAT is for ICS and not for JB but i take that mistake doing the thing really fast. :angel:
Ok...i need them to get the fastboot with the JB Boot.img like you said.
The JB Boot.img is into the Rom??? because i saw the boot.img into the JB update.zip
Can u tell me the command to get that flash? Is "fastboot flash boot boot.img"?
Thks for ur patience
Click to expand...
Click to collapse
It's no problem.
So you fastbooted an ICS boot.img on a JB rom
So, you need to see if you can manually get it into fastboot mode with the procedure I pointed out above (note it will probably wipe your user data, but who cares)
If you get it in fastboot mode, verify via windows device manager, then just put a JB Boot image in there. I have a little package in my Boot.image thread Full /System RW-Root. Don't use the boot mage in it, as it's for a 701. Just copy your JB boot.image in there and fastboot it. You have the correct command.
Verboth has a new rom, that contains an unsecure boot.img for the 700 JB. You can use that one also. It's what you were trying to do originally, just with a wrong image (ICS)
The reason ADB doesn't see it, is because the system isn't running. The newer CWM recoveries should have adb enabled through CWM, but I don't think you put that in yet.
Hopefully you'll get it fastbooted.
MD
Moscow Desire said:
It's no problem.
So you fastbooted an ICS boot.img on a JB rom
So, you need to see if you can manually get it into fastboot mode with the procedure I pointed out above (note it will probably wipe your user data, but who cares)
If you get it in fastboot mode, verify via windows device manager, then just put a JB Boot image in there. I have a little package in my Boot.image thread Full /System RW-Root. Don't use the boot mage in it, as it's for a 701. Just copy your JB boot.image in there and fastboot it. You have the correct command.
Verboth has a new rom, that contains an unsecure boot.img for the 700 JB. You can use that one also. It's what you were trying to do originally, just with a wrong image (ICS)
The reason ADB doesn't see it, is because the system isn't running. The newer CWM recoveries should have adb enabled through CWM, but I don't think you put that in yet.
Hopefully you'll get it fastbooted.
MD
Click to expand...
Click to collapse
Okay, so since I just did this, I'm going to try and give you a "how to" on how I fixed it...
MD and pawitp both are the authorities on this, but I think this will help and I a, sure they will correct me where I go wrong.
First, use the manual process for getting your A700 in fastboot.. power button + down vol, wait for the first buzz then release only the power button, wait for the second buzz then press the up volume button. Your tab should now be in fastboot mode.
Connect it to your computer.
Get a copy of the proper recovery image "recovery-a700-6015" and the following ROM ( http://forum.xda-developers.com/showthread.php?t=1952124) and save them to a directory where you can find it easily.
Pull the SD card from your tab and put the ROM from above in the base directory and put it back in your tab.
From the c prompt on your computer use the following fastboot command:
Fastboot devices
----#make sure that the computer sees your a700
Fastboot boot <save directory>recovery-a700-6015.img
----#your tab will reboot into CMR Recovery
In recovery format system, data, cache, dalvik
Still in recovery install the ROM from your external SD card.
The Aroma Installer will guide you through it, but make sure you tell it to install the new firmware.
Reboot.
You should be on the stock rooted ACER Great Britain release.
From there you can download and install CM10 (which is what I did), or any other ROM you would like.
Sent from my A700 using xda premium
well.......30 minutes with the tablet and:
I put the tablet in Recovery state with the last instructions.....but now i ve too much errors lines:
Important: all this error are "before" flash again the recovery
The recovery cant:
mount /cache/recovery/command
mount /cache/recovery/log
mount /cache/recovery/last_log
cant open cache/recovery/log
and.....
cant mount SDCARD, EXTERNALSD, SYSTEM, CACHE, etc etc...
when i try to flash again the recovery: <waiting the device> and nothing......i cant put the tablet in fastboot mode.
i have the same problem before. 無得整的, 要上acer換底版的
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
Click to expand...
Click to collapse
Uhmmmm.... didn't I state that the other day?
Glad you got it going Mate :good:
MD
thks ppl
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
:
Click to expand...
Click to collapse
I didnt have the same exact issue like the other users BUT this key combination to finally get back into fastboot during a hanging ACER logo bootup with a red failure msg at the corner was the LIFE SAFER!!!!!
VOL - (left button with two knobs) & PWR and then CYCLE THE ROTATION LOCK
tattoo this on your arms!!! :laugh:
LukeRG said:
I didnt have the same exact issue like the other users BUT this key combination to finally get back into fastboot during a hanging ACER logo bootup with a red failure msg at the corner was the LIFE SAFER!!!!!
VOL - (left button with two knobs) & PWR and then CYCLE THE ROTATION LOCK
tattoo this on your arms!!! :laugh:
Click to expand...
Click to collapse
LOL
pls step step explain ı recovery my tablet but ı want to back syock rom tablet internal storage not ready in pc ı cant see internal storage ı see only sc card camera dont workk how back to syock rom pls help..
thank's man
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
Click to expand...
Click to collapse
Thank's... you just safe my problem today
u welcome .......
Hello everybody,
I think I have NOT exactly the same problem but very similar.
Let me explain how I got there:
I had JB bootloader and CM11 installed for long and working fine.
Last days I tried out the CM12.1 unofficial rom with successful installation.
I noticed that the camera focus was not working. Usually I never use the camera and was not sure if it worked before. So I went back to CM11 to look if it is rom dependent. In CM11 it still was not working and I went back to stock. The stock rom I found was Android 4.0.4 and I tried to make OTA update what showed me a “not allowed to your device” –error.
However, at this moment I was quite sure that the camera focus is a hardware defect and wanted to go on testing the new CM12.1. I installed it again from CWM recovery and it was not booting anymore.
The problem is, that the stock rom flashed an ICS bootloader which is not compatible anymore. I also cannot boot into recovery anymore but fastboot is working.
Power-On:
shows Bootloader Version ICS-MR1-a055314 (Unlock Mode) and nothing more
Power-On + Vol.Down:
Bootloader Version ICS-MR1-a055314 (Unlock Mode)
Erasing Cache before SD update…
SD update cnd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Then for just a second CWM is shown:
CWM-based Recovery v6.0.5.1
Finding update package
E:unknown volume for path [SDCARD:update.zip]
E:Can't mount SDCARD:update.zip
Installation aborted.
Rebooting...
Then it holds on Bootloader Version ICS-MR1-a055314 (Unlock Mode)
I could not find any button combination to boot something else.
What I tried and what did not make any changes:
Flashing the recovery.img again
Erase userdata, cache, system
Please help me to boot up recovery again and flash a JB bootloader and new rom.
Thanks and kind regards,
Gandlz
Well, in between I found a solution and can answer my own question now:
The trick is to flash the CWM Recovery not to the recovery partition but to the boot partition. (fastboot flash boot recovery.img)
After restarting the tablet it boots directly into CWM Recovery.
I found a newer stock rom with jelly bean android and installed it to come back to JB-Bootloader. Now I could install CM10.2 CM11 or CM12.1 again.
The stock rom is from a german forum:
android-hilfe.de/thema/a700-zurueck-aufs-deutsche-stock-rom-flashen-anleitung-imagefile.329590
By the way: I’m running CM10.2.1 and it is very much faster than CM11 or CM12.1. I don’t need the newer features and like the old design even more. And also the camera focus is working now, so it is definitely a software issue with newer CM versions.
Best regards,
Gandlz
Hey guys, I installed CWM on my buddies HTC one S (ville) and I keep getting a weird problem with CWM. I have successfully flashed CM10 multiple times and have made only one back up. Every time his phone dies and he plugs it in and tries to power it on it boots straight to recovery and after you press reboot phone it boots right back to recovery again and again... The only way it fixes itself is when you restore the back up and then it sets him back to that date. I'm wondering if this is a problem with CWM or something else... I'm new to HTC devices because I have always been on the Galaxy line from Samsung so some of this is a little new to me...
Thanks in advance!!
This is a known glitch with CWM. If you plug it in when its off and try to turn it on, it'll automatically Boot into CWM Recovery. I prefer TWRP personally, had too many problems with CWM and getting into the same exact pain-in-the-neck Bootloop as you're referring to.
As far as I am aware, there isn't a way to get out of the CWM Bootloop unless you just let the phone run out of Battery, get into the Bootloader (Which is somewhat of a challenge with the CWM Bootloop), and then flash a different Recovery from Fastboot. Correct me if i'm wrong on there not being any other way around this.
It's happened to me once, I flashed the.stock boot.img and it worked fine.after that. Not sure if its a fix but it got me outta of it.
echo en Android
Thanks guys I think I'll try TWRP but just to check does CM10 work with TWRP and if so how do I flash a new recovery?
yes cm10 worx with twrp. For flashing recovery, download d appropriate recovery.img for ur device. place this in the fastboot folder or the platform-tools folder.
now, boot into bootloader and enter fastboot then connect phone to PC , it should say fastboot USB .
Now open a command window and use this command---
fastboot flash recovery recoveryname.img.
Sent from my One V
mattytom87 said:
Thanks guys I think I'll try TWRP but just to check does CM10 work with TWRP and if so how do I flash a new recovery?
Click to expand...
Click to collapse
Cyanogenmod 10 does indeed work with TWRP as far as I know. Along with mihirengg19's Reply above, there is also an Alternative way to flashing a new Recovery, and that is to use the HTC One S All-In-One Toolkit. Its the easiest/safest way, if you don't know what you're doing.
yes toolkit is great but manually is best...
Sent from my One V
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
agk.ganesh said:
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
xu3sno said:
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
Click to expand...
Click to collapse
androidck said:
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
Click to expand...
Click to collapse
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
agk.ganesh said:
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
Click to expand...
Click to collapse
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Are you sure that you are booting into cwm v5.0.2.0?
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Click to expand...
Click to collapse
+1
CM10.1.6 worked
ibub said:
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
mns123 said:
+1
Click to expand...
Click to collapse
Thanks.
agk.ganesh said:
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
Thanks.
Click to expand...
Click to collapse
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Thanks
ibub said:
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I will try installing now new recovery and then new ROM.
Very glad to see the support from you guys... Thanks ibub and all..
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Thanks
akiratoriyama said:
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Click to expand...
Click to collapse
Thanks @akiratoriyama.
I have upgraded CWM recovery 6.xx through CWM 5.0.2.0 and successfully installed MukulSoni's Kitkat ROM.
And enjoying eating kitkat..
Thanks all..