[Q] Recovery not working and additional problems - Motorola Droid and Milestone General

Hi guys,
I have a few problems with my Motorola Milestone.
1. I can't get in to recovery. I only get an black screen (backlight is on)
2. I don't get any video in the bootloader. but RSD lite does recognizes it, and is able to flash it. When it's flashing I do get video only stating that there is software update busy.
3. When I boot up my phone I don’t get, a Motorola logo, but just a black screen (back light on) followed by the Android logo after a few minutes.
4. If I try to wake up the phone, the screen remains black, but the hardware keys to light up, I have to press the lock button multiple times to activate the screen. - Note when the screen remains black, it is responsive and I can unlock the phone, but it still remains black. And sometimes the colors are inverted, but when i make a screen of it with Screen Grabber (shoot me) it's in normal colors.
That kind of sums it up.
I have tried a few things to fix it. I have:
1. Cleared caches, and personal data
2. Flashed a different SBF en recovery
And since I can’t get in to recovery, I had to get Root via Z4 Root method and it works fine.
Afterwards I downloaden Rom-manger, and installed the ClockWork recovery, and tried to boot in Recovery via clockwork, but that didn’t work either. I also can’t get in to Recovery via a cold boot
I think the problems started when I was using CyanogenMod 7 RC4. It worked just fine, but after I installed it I couldn't get in to recovery.
Can I try something else to fix it? or should I flash it back to original state and RMA it?
Edit some additional information:
Frimware: 2.2.1
Frimware configuration: GAS_EMEA_UCAMS1FRYOQWRTEU_P005
Baseband version: 3GSMPU91A_U_91.09.00I
Baseband configuratuin version:UCALHLSMR2EMEAB1B806E.0R
Kernel Versuin: 2.6.32.9-ge635aa4 [email protected]#1
Build Number: SHOLS_U2_05.06.0
And is it possible to restore the orginal boot animation, without recovery?
TL.DR: Motorola Milestone --> CyanogenMod 7 RC4 --> no recovery & no video @ bootloader, plus additinal video problems --> back to orginal --> same problems.

BUMP: is there anyone with a possible soulution?

ClockWork recovery doesn't work on milestone.
So CM7 does boot up?

zeppelinrox said:
ClockWork recovery doesn't work on milestone.
So CM7 does boot up?
Click to expand...
Click to collapse
CM7 doesn't anymore as I removed it, and flashed a different SBF and recovery.
CyanogenMod 7 RC4 worked fine but I had a few video problems, and I could get in to recovery.
I will flash a different recovery tonight and try it out.

Only use androidiani open recovery
Sent from my Milestone using Tapatalk

zeppelinrox said:
Only use androidiani open recovery
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Flashed a different .sbf and placed the androidiani open recovery files on the Sd card root, but i still can't get in to recovery. I won't even get the /!\ screen. The phone does turn on, but will only get a black screen.

Which sbf?
Sent from my Milestone using Tapatalk

UK SHOLS_U2_02.36.0
I think I bricked it, I'm going to try to restore it or buy a new phone... >.<

BloemBlaster said:
UK SHOLS_U2_02.36.0
I think I bricked it, I'm going to try to restore it or buy a new phone... >.<
Click to expand...
Click to collapse
I don't think you bricked it... but damaged it in some way.
Could also be some hardware related stuff in the end.
Anyway try to wipe everything, that could be wiped.
Start into bootloader and try to install G.O.T. 2.2.1 using RSD again.
This one got the vulnerable recovery already integrated.
Then try to use the specific G.O.T. OpenRecovery on your sdcard to check system integrity.
Please try to take care of every single step and check out what happens....
If your hardware is doing fine, i'm pretty sure that you will get a working phone again.
P.S.: How about your bootloader version?
Good luck,
scholbert

scholbert said:
I don't think you bricked it... but damaged it in some way.
Could also be some hardware related stuff in the end.
Anyway try to wipe everything, that could be wiped.
Start into bootloader and try to install G.O.T. 2.2.1 using RSD again.
This one got the vulnerable recovery already integrated.
Then try to use the specific G.O.T. OpenRecovery on your sdcard to check system integrity.
Please try to take care of every single step and check out what happens....
If your hardware is doing fine, i'm pretty sure that you will get a working phone again.
P.S.: How about your bootloader version?
Good luck,
scholbert
Click to expand...
Click to collapse
I think my boatloader is 90.47 I'm not sure as I won't get any video in the boatloader.
I flashed the G.O.T 2.2.1but I can't get in to recovery, there is still no video only a blackscreen.
Is it posible the may have deleted the files for the logo?

BloemBlaster said:
I think my boatloader is 90.47 I'm not sure as I won't get any video in the boatloader.
I flashed the G.O.T 2.2.1but I can't get in to recovery, there is still no video only a blackscreen.
Is it posible the may have deleted the files for the logo?
Click to expand...
Click to collapse
You can try upgrading your bootloader to 90.78 from here.
Then try flashing GOT 2.2.1, then see if AOR boots up.

sileshn said:
You can try upgrading your bootloader to 90.78 from here.
Then try flashing GOT 2.2.1, then see if AOR boots up.
Click to expand...
Click to collapse
I flashed 90.78, and then reflashed GOT 2.2.1, but is still can't get into te recovery. I getting the same result, no motorola logo and a black screen with no /!\ logo

If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.

I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/

Hi guys,
sorry for the late reply, but I'm also moving at the moment.
I have tired numerous things.
If I flash the 2.2.1 Firmware SHOLS_U2_05.26, I can get to the recovery selection screen, with the /!\ screen.
But if apply update.zip I will get an error message, stating "EOCD marker occurs after start of EOCD E:signature verification failed", something like that, I don't know the specific message out of my head
And if I flash a vurnable recovery only sbf, with the SHOLS_U2_05.26 I can't get the recovery screen, only a black screen.
zeppelinrox said:
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Click to expand...
Click to collapse
I will try thiss when I get home.
sileshn said:
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
Click to expand...
Click to collapse
I will try this if zepplelinrox method fails becaus I don't have any experince with adb. But the phone is recognised.

...........strange....
BloemBlaster said:
If I flash the 2.2.1 Firmware SHOLS_U2_05.26, I can get to the recovery selection screen, with the /!\ screen.
But if apply update.zip I will get an error message, stating "EOCD marker occurs after start of EOCD E:signature verification failed", something like that, I don't know the specific message out of my head
Click to expand...
Click to collapse
This is standard error, if vulnerable recovery is not installed and you try to start OpenRecovery.
BloemBlaster said:
And if I flash a vurnable recovery only sbf, with the SHOLS_U2_05.26 I can't get the recovery screen, only a black screen.
Click to expand...
Click to collapse
This is strange behaviour...
My last guess is, that something might be wrong with your vulnerable recovery sbf file (file corruption ???). There should have been some errors during flash...
Anyway, you might grab it here and try again:
http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
Good luck!
scholbert

sileshn said:
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
Click to expand...
Click to collapse
Still trying this, no luck yet. ADB isn't my strongest point
zeppelinrox said:
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Click to expand...
Click to collapse
The same goes for you, no luck yet. QtADB, work and it recognise my phone, but i can't any (re)boot commands.
scholbert said:
This is standard error, if vulnerable recovery is not installed and you try to start OpenRecovery.
This is strange behaviour...
My last guess is, that something might be wrong with your vulnerable recovery sbf file (file corruption ???). There should have been some errors during flash...
Anyway, you might grab it here and try again:
http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
Good luck!
scholbert
Click to expand...
Click to collapse
I actually have no idea how to download the sbf, form the site you have provided.
nevermind, I found it out . but now if my phone to connect to windows it doesn't recognizes it :S

BloemBlaster said:
but now if my phone to connect to windows it doesn't recognizes it :S
Click to expand...
Click to collapse
Before or after flashing the vulnerable recovery again?
Confusing...
scholbert

scholbert said:
Before or after flashing the vulnerable recovery again?
Confusing...
scholbert
Click to expand...
Click to collapse
Sorry for being confusing, it was after flashing vulnerable recovery, but my I'm flashing with a different system now and it working just fine.
If I try the .sbf you provided RSD gives a error "Failed flashing process. failed flashing process (0x17100);phone connected"

BloemBlaster said:
Sorry for being confusing, it was after flashing vulnerable recovery, but my I'm flashing with a different system now and it working just fine.
Click to expand...
Click to collapse
No problem...
BloemBlaster said:
If I try the .sbf you provided RSD gives a error "Failed flashing process. failed flashing process (0x17100);phone connected"
Click to expand...
Click to collapse
O.K. seems that something went wrong during download grab it here:
http://forum.xda-developers.com/showpost.php?p=13039348&postcount=17
BTW the link points to the OpenRecovery developers git rep... so this file is absolutely save.
Cheers,
scholbert

Related

CyanogenMod

Guys,
I'm losing my mind here.
I've tried to install the CyanogenMod but I've run into some problems.
Why is it so damn difficult to install this?
I've spent 4 hours following different guides and none of them are step by step.
The ones that come close, never mention possible issues along the way which you then have to find on other forums.
Anyway,
can someone please help me with the following:
I'm getting stuck on booting into recovery.
I run the command and the phone reboots. however, it then presents a Triangle and an exclamation mark!
The instruction show that I am supposed to see a Green text recovery screen.
I'm having to hit the up volume and power button, which gives a blue text recovery screen with limited options.
I've tried the Amon_Ra's Recovery process and the ClockworkMod Recovery process to no avail!!!
I also tried the rom manager but the app keep giving "An error occurred while attempting to run privileged commands"
I know it's something that I'm doing wrong but I'm very close to throwing this phone out the window and going back to an iphone... This is just not ****ing worth it.
I've done everything up to reboot to recovery part from this guide: http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide
/please help.
Your Bootloader is unlocked?
artii said:
Guys,
I'm losing my mind here.
I've tried to install the CyanogenMod but I've run into some problems.
Why is it so damn difficult to install this?
I've spent 4 hours following different guides and none of them are step by step.
The ones that come close, never mention possible issues along the way which you then have to find on other forums.
Anyway,
can someone please help me with the following:
I'm getting stuck on booting into recovery.
I run the command and the phone reboots. however, it then presents a Triangle and an exclamation mark!
The instruction show that I am supposed to see a Green text recovery screen.
I'm having to hit the up volume and power button, which gives a blue text recovery screen with limited options.
I've tried the Amon_Ra's Recovery process and the ClockworkMod Recovery process to no avail!!!
I also tried the rom manager but the app keep giving "An error occurred while attempting to run privileged commands"
I know it's something that I'm doing wrong but I'm very close to throwing this phone out the window and going back to an iphone... This is just not ****ing worth it.
I've done everything up to reboot to recovery part from this guide: http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide
/please help.
Click to expand...
Click to collapse
Go to this thread. Read it. Download the apk. Root your device (you could not flash a custom recovery because you are not rooted!...). Download RomManager from the Market. Install a custom recovery through RomManager and you are done.
Reading other thread now.
dadennis said:
Your Bootloader is unlocked?
Click to expand...
Click to collapse
Yes,
Ran the following: fastboot oem unlock
artii said:
Yes,
Ran the following: fastboot oem unlock
Click to expand...
Click to collapse
mhhh ok. So you probably have no insecure boot image. That's probably why you can't flash any recovery from RomManager....
Try this at MoDaCo. Download an unsecure boot image... And try again.
Downloaded Universal Androot.
Clicked to root, goes OK ok ok ok ok ok ok ok then "Failed ! No ~~~ Fu Goo ~~~
edit - trying superoneclick
artii said:
Downloaded Universal Androot.
Clicked to root, goes OK ok ok ok ok ok ok ok then "Failed ! No ~~~ Fu Goo ~~~
Click to expand...
Click to collapse
if your running android 2.2.1 it wont work mate! try z4 root off the market worked for me!
ok, superoneclick seemed to have work and rooter the phone!
using rom manager to flash the clockwordmod recovery now. Lets see if it fails and gives and permissions error. If not, I'll boot into recovery and see if that works.
thanks for the assistance thus far.. /puts iphone back in the drawer.
recovery worked, ran the update.zip
downloaded the Cyanogen mode via rom manager, but when it tried the clockwork recovery, I get the triangle again... frustrating.
artii said:
recovery worked, ran the update.zip
downloaded the Cyanogen mode via rom manager, but when it tried the clockwork recovery, I get the triangle again... frustrating.
Click to expand...
Click to collapse
what update .zip?
I have the same problem...Well i rooted with superclick then when i go into recovery mode and click on recovery it shows a white triangle. I removed the memory card while rooting, could that be the problem?
You need to delete the following two files, and reinstall your custom recovery. These files restore the stock recovery during a full boot.
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App
Is it ok if i factory set and redo all the processes?
artii said:
Guys,
I'm losing my mind here.
I've tried to install the CyanogenMod but I've run into some problems.
Why is it so damn difficult to install this?
I've spent 4 hours following different guides and none of them are step by step.
The ones that come close, never mention possible issues along the way which you then have to find on other forums.
Anyway,
can someone please help me with the following:
I'm getting stuck on booting into recovery.
I run the command and the phone reboots. however, it then presents a Triangle and an exclamation mark!
The instruction show that I am supposed to see a Green text recovery screen.
I'm having to hit the up volume and power button, which gives a blue text recovery screen with limited options.
I've tried the Amon_Ra's Recovery process and the ClockworkMod Recovery process to no avail!!!
I also tried the rom manager but the app keep giving "An error occurred while attempting to run privileged commands"
I know it's something that I'm doing wrong but I'm very close to throwing this phone out the window and going back to an iphone... This is just not ****ing worth it.
I've done everything up to reboot to recovery part from this guide: http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide
/please help.
Click to expand...
Click to collapse
Did you try superboot? Works perfectly for me.
guy27 said:
Is it ok if i factory set and redo all the processes?
Click to expand...
Click to collapse
Yes
Sent from my Nexus One using XDA App
This is my preferred method of rooting.
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Remember, once rooted you will need to instal a custom recovery. You will also need to delete the two files I mentioned above, otherwise you will lose custom recovery when you boot...
Sent from my Nexus One using XDA App
danger-rat said:
You need to delete the following two files, and reinstall your custom recovery. These files restore the stock recovery during a full boot.
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Sorry, I'm a bit new to all this.
Can you please tell me exactly how to remove these files?
Do I need to download a terminal for the nexus one and run some rm commands?
aggazz said:
what update .zip?
Click to expand...
Click to collapse
The CyanogenMod file that I downloaded. Number 7. I changed it's name to update.zip and moved it to root of sd card when trying to do it manually without rom manager before.
artii said:
The CyanogenMod file that I downloaded. Number 7. I changed it's name to update.zip and moved it to root of sd card when trying to do it manually without rom manager before.
Click to expand...
Click to collapse
so are you now rooted and running cm7-build#10 nightly or still trying to do it?

[Q] Help please Milestone wont boot into recovery

Hi, can anyone please help with this?
I have a milestone that has root access, have followed step by step instructions on how to get into recovery so that I can flash a custom rom, vulnerable recovery has been flashed to it and open recovery been put on the memory card but it wont recognise open recovery, it just goes into normal bootloader screen. What sshould be done to make it enter boatloader as instructions have been followed step by step?
Thanks for your help
rtardedman said:
Hi, can anyone please help with this?
I have a milestone that has root access, have followed step by step instructions on how to get into recovery so that I can flash a custom rom, vulnerable recovery has been flashed to it and open recovery been put on the memory card but it wont recognise open recovery, it just goes into normal bootloader screen. What sshould be done to make it enter boatloader as instructions have been followed step by step?
Thanks for your help
Click to expand...
Click to collapse
As stated in the name, to get into OpenRecovery you want to enter Recovery mode. When the phone is off, hold power+x until you see the Motorola logo. Then hold camera+vol-up to enter recovery mode, select update.zip and then you will be in OR.
I've done that but the only thing that shows up is the bootloader which says batteryk
ok to program
transfer mode: usb
thats the part that it wont go past
did you turn off the phone before you tried?
Yes, tried it with phone off first but no luck
Sent from my Milestone using XDA App
I hv the same problem. The update file is corrupted.
I flashed back to original rom then recovery then open recovery...
finally, custom rom.
Happened to me to way before. It was because the sbf file we flash through rsd lite was corrupted or something. If you need a good version maybe I can tell you where to find it.good luck.
rtardedman said:
I've done that but the only thing that shows up is the bootloader which says batteryk
ok to program
transfer mode: usb
thats the part that it wont go past
Click to expand...
Click to collapse
Sent from my Milestone using XDA App
Yeah because I tried it with 3 sbf roms, could you post a link to the one that you used? Thanks heaps

Droid 3 Stuck at M Logo - Bricked?

Hey guys,
I just recently got a refurb Droid 3 after my old one had the backlight go out, I hand't had a chance to bootstrap it and put ICS on it. But I was able to get it rooted. I restarted my phone today and ever since it has been stuck at the M logo screen and I've tried everything I can find to remedy this.
I updated this morning to the most recent OTA update (5.7.906 I believe) and then rooted it.
To fix the issue I've tried a few different things. I tried Pete's SBF to 5.7.890 but I was getting an error about the cbt.bin file. I found that with the recent changed to 5.7.906 you aren't able to directly flash over it to go back to 5.7.890. I then found another post on here which had a script to go back to 5.7.890 from 5.7.906. I ran that and still had the same result.
Any other ideas or anything that I am missing?
I can get into fastboot, I've been using the scripts with moto-fastboot. Normal boot is just leaving me at the M logo, booting into recovery yields the same result.
Any help would be appreciated since I have no clue what else I can do at this point...
seems like a soft brick... should be fixable...
With the phone off, hold me, then the power button... then go down to BT TOOLS and select it ( volume up is the select button _ so when u do that it doesnt go to it?
try following this thread
http://forum.xda-developers.com/showthread.php?t=1336980
heres a download link
http://minus.com/lbkaxv58pO5MDp
Juicy555 said:
seems like a soft brick... should be fixable...
With the phone off, hold me, then the power button... then go down to BT TOOLS and select it ( volume up is the select button _ so when u do that it doesnt go to it?
try following this thread
http://forum.xda-developers.com/showthread.php?t=1336980
heres a download link
http://minus.com/lbkaxv58pO5MDp
Click to expand...
Click to collapse
I don't have a BT Tools selection. I do have BP Tools though. I selected it and it just sits there on the M logo as well...
I've tried a few of Pete's scripts with no luck so far (worked on the old Droid 3 when I put it back to stock before shipping it back).
Juicy555 said:
seems like a soft brick... should be fixable...
With the phone off, hold me, then the power button... then go down to BT TOOLS and select it ( volume up is the select button _ so when u do that it doesnt go to it?
try following this thread
http://forum.xda-developers.com/showthread.php?t=1336980
heres a download link
http://minus.com/lbkaxv58pO5MDp
Click to expand...
Click to collapse
Gave the one that you linked a try, get "Preflash validation failure" for Recovery and Boot.
Any other ideas?
imperpetual said:
Gave the one that you linked a try, get "Preflash validation failure" for Recovery and Boot.
Any other ideas?
Click to expand...
Click to collapse
it will not flash if your phone is not charged to at least 50%.. make sure its charged...
Juicy555 said:
it will not flash if your phone is not charged to at least 50%.. make sure its charged...
Click to expand...
Click to collapse
It is charged. When it's not charged it gives the "LOW BATTERY" error.
click the link in my signature
and follow the directions in my thread and you will be fine
you updated your phone to. 906 all of the older sbf's wont work..but mine will as it is specifically for. 906
ovelayer said:
click the link in my signature
and follow the directions in my thread and you will be fine
you updated your phone to. 906 all of the older sbf's wont work..but mine will as it is specifically for. 906
Click to expand...
Click to collapse
Your 1 Click SBF ran fine and completed without errors but I'm still getting the same result, stuck at M logo.
Is there something I could be missing which is making it not boot that most SBFs don't include? That's the only thing I can think of at this point.
imperpetual said:
Your 1 Click SBF ran fine and completed without errors but I'm still getting the same result, stuck at M logo.
Is there something I could be missing which is making it not boot that most SBFs don't include? That's the only thing I can think of at this point.
Click to expand...
Click to collapse
okay right after you use the 1click sbf
go HERE
download the. 906 update
place it on your external sdcard..
reboot into STOCK recovery and install the update
reboot
try that
ovelayer said:
okay right after you use the 1click sbf
go HERE
download the. 906 update
place it on your external sdcard..
reboot into STOCK recovery and install the update
reboot
try that
Click to expand...
Click to collapse
I'm fairly certain that could work, if I could ever get into the Stock recovery....I'm not able to boot into anything. Going to try a few other things, if nothing else works I'll just take it in and see if I can get yet another warranty replacement.
Thanks for the responses, if you have any other ideas just let me know.
I think the main thing that needs to be addressed is that I need to be able to get into recovery and then I will be set to fix it. Right now it just sits at the M logo for Recovery (and any other options from the boot menu).

[Q] Boot loop stock

Hello, folks!
I have a Milestone with stock android (2.1 I guess, after an OTA update from the provider) that was in the drawer for ca. 2 years because the POWER/VOL/CAM flat cable was bad. I changed the cable, was able to boot normally one or twice.
Now the phone freezes with the white motorola symbol.
When I turn it on with PWR + D-pad UP, I get into the bootloader v. 90.73.
Werid thing is that when I try to boot into recovery (PWR + CAMERA), I still get into the bootloader, so I can't get into recovery to try installing another rom to circumbent the boot lock-up.
Ideas to solve this?
Thanks!
It seems like your bootloader is corrupted.
If i were you, i would upgrade it to the latest version (90.78) and try with it.
(Also you should consider using CM7 or even CM10.)
Thanks!
How can I upgrade the bootloader? Is there a zip or an img file somewhere to push?
I dont know exactly, i didnt have to do it before.
I'm pretty sure, you can brick your device with this if something goes wrong.
I think you will need the following:
-Drivers
-RSDLite
-proper SBF file from here
But i dont know if you need to boot into bootloader mode or something.
Please, be very-very careful, maybe you should wait if someone with more knowledge gives you any advice.
Erovia said:
-proper SBF file from here
Click to expand...
Click to collapse
Thanks! I'll try to flash a newer bootloader.
Nope, Didn't work.
Still freezing on boot.
Sorry, but i'm out of ideas.
Maybe someone with more knowledge could help.
Good luck.
Erovia said:
Sorry, but i'm out of ideas.
Maybe someone with more knowledge could help.
Good luck.
Click to expand...
Click to collapse
Well, thanks anyway.
Did you manage to get the Device manage to take the new boot loader via usb?
If it did load the SBL try loading the vulnerable recovery sbf then put open recovery on to your SD card. If you can get that fair then I'd imagine you could load a new OS on to it without much issue. Lots of guides out there.
motorola xt3
motorola xt3 usb diver win xp plz

I have a paperweights, help...

I have root and unlocked bootloader. I did an update of lg and thereafter blocked, do not know if this was the problem.
Install the CWM by room (room enox iodak08 +), I can enter the bootloader, installing, when reboot the sistem entering the boot but does not start with the system and back to CWM after being taken. I can not get into the room and I can get into CWM. I've done factory reset and wipecache, I returned instal to the room, and nothing, enters the boot but does not start with the room.
I'm in a tricky situation, I stopped to have a mobile phone and I stick one paperweights. Need a little help.
Manholas said:
I have root and unlocked bootloader. I did an update of lg and thereafter blocked, do not know if this was the problem.
Install the CWM by room (room enox iodak08 +), I can enter the bootloader, installing, when reboot the sistem entering the boot but does not start with the system and back to CWM after being taken. I can not get into the room and I can get into CWM. I've done factory reset and wipecache, I returned instal to the room, and nothing, enters the boot but does not start with the room.
I'm in a tricky situation, I stopped to have a mobile phone and I stick one paperweights. Need a little help.
Click to expand...
Click to collapse
As always - flash a kdz and start from scratch if you can't get it working. And ... SEARCH
SimonTS said:
As always - flash a kdz and start from scratch if you can't get it working. And ... SEARCH
Click to expand...
Click to collapse
I can not get the pc to recognize the phone. I already have the KDZ file (V20A_00.kdz)
Manholas said:
I can not get the pc to recognize the phone. I already have the KDZ file (V20A_00.kdz)
Click to expand...
Click to collapse
Install or reinstall latest drivers from LG and try again when it does'nt work change usb port or try it on other PC.
Good Luck..
as I am in CWM recovery, removed the sd card and put a room.zip and flash. Did the installation but when "reboot sistem" back to cwm recovery.
The problem is that the Phone was locked into CWM recovery. And I have no way to recognize the phone on PC. Is there any way to unlock the CWM recovery v6.0.4.5?
Manholas said:
The problem is that the Phone was locked into CWM recovery. And I have no way to recognize the phone on PC. Is there any way to unlock the CWM recovery v6.0.4.5?
Click to expand...
Click to collapse
no. boot into s/w mode and flash kdz. there are plenty of guides. if your pc cant detect your phone while it's in s/w mode, then reinstall drivers
Manholas said:
The problem is that the Phone was locked into CWM recovery. And I have no way to recognize the phone on PC. Is there any way to unlock the CWM recovery v6.0.4.5?
Click to expand...
Click to collapse
As you stated in your first post...
Manholas said:
I have root and unlocked bootloader. I did an update of lg and thereafter blocked, do not know if this was the problem.
Click to expand...
Click to collapse
It has been stated time and time again that your must NEVER carry out a vendor OTA on a rooted or modified device. It causes a problem 90% of the time as the OTA has no flexibility to deal with something it isn't expecting to find - so you get exactly what you have.
Just be thankful that it is almost impossible to hard-brick our device or you really would have a paperweight. Instead you just need to search and read a little to get it back up and running.
Flying_Bear said:
no. boot into s/w mode and flash kdz. there are plenty of guides. if your pc cant detect your phone while it's in s/w mode, then reinstall drivers
Click to expand...
Click to collapse
If you turn on the mobile it goes into CWM recovery. The problem is that the Phone was locked into CWM recovery. And I have no way to recognize the phone on PC. Is there any way to unlock the CWM recovery v6.0.4.5?
SimonTS said:
As you stated in your first post...
It has been stated time and time again that your must NEVER carry out a vendor OTA on a rooted or modified device. It causes a problem 90% of the time as the OTA has no flexibility to deal with something it isn't expecting to find - so you get exactly what you have.
Just be thankful that it is almost impossible to hard-brick our device or you really would have a paperweight. Instead you just need to search and read a little to get it back up and running.
Click to expand...
Click to collapse
Ok, thanks for the warning was a real oversight. But, .. and help. I'm just locked into CWM recovery and I can not enter the phone otherwise. thanks
Flying_Bear said:
no. boot into s/w mode and flash kdz. there are plenty of guides. if your pc cant detect your phone while it's in s/w mode, then reinstall drivers
Click to expand...
Click to collapse
Manholas said:
Ok, thanks for the warning was a real oversight. But, .. and help. I'm just locked into CWM recovery and I can not enter the phone otherwise. thanks
Click to expand...
Click to collapse
As @Flying_Bear has already said to you...
Manholas said:
Ok, thanks for the warning was a real oversight. But, .. and help. I'm just locked into CWM recovery and I can not enter the phone otherwise. thanks
Click to expand...
Click to collapse
You need to get your PC to recognise the phone, thats the first step in this repair (unless the usb port is broken, there's no reason why it wont recognise, whats your OS and version, usb 2 or 3?)
why not put cm10.1 on a microsd and flash it from there?
JoinTheRealms said:
You need to get your PC to recognise the phone, thats the first step in this repair (unless the usb port is broken, there's no reason why it wont recognise, whats your OS and version, usb 2 or 3?)
why not put cm10.1 on a microsd and flash it from there?
Click to expand...
Click to collapse
it still won't work, after upgrading it ota while having custom recovery installed, a person will be locked to recovery for some reason (atleast other people were). the only way to fix it that i know of is to reflash a kdz
Manholas said:
If you turn on the mobile it goes into CWM recovery. The problem is that the Phone was locked into CWM recovery. And I have no way to recognize the phone on PC. Is there any way to unlock the CWM recovery v6.0.4.5?
Click to expand...
Click to collapse
cmon, pay some attention you don't need to turn on the phone, or boot into the system itself to boot into s/w mode. now, there are tons (like 3 or 4 guides, plus many other topics opened by people with exact same problem like you) threads that tell you what to do (hint: figure out how to boot into s/w mode), so i'll let you search around for the guide.
I suggest using this method: http://forum.xda-developers.com/showthread.php?t=2682146
It's easier, faster and safer than flashing a .kdz file. (Plus, it tells you how to get into the s/w upgrade mode!)
Greetings from my Nexus 7 FHD!
balloon27 said:
I suggest using this method: http://forum.xda-developers.com/showthread.php?t=2682146
It's easier, faster and safer than flashing a .kdz file. (Plus, it tells you how to get into the s/w upgrade mode!)
Greetings from my Nexus 7 FHD!
Click to expand...
Click to collapse
I think this method also flashes a kdz, but does it automatically for you. But yeah, this one is easier than manually flashing. Thanks for posting it
Also, thiy method will format internal sd card. My suggestion is to do a data/system format from cwm before you go in to flashing a kdz, either manually or automatically, so you don't end up with formatted internal sd card
A big thanks to SimonTS, JoinTheRealms, Flying_Bear and balloon27. This is a fantastic forum and you guys are spectacular. Due to professional reasons only going back to the forum after seven days, I go to the sea and I'm without net. Got this getaway just to thank you for the care provided, the mobile phone is the same and will just touch it after a week. Once again, thank you very much.
I just make the process advised by balloon27 (http://forum.xda-developers.com/show....php?t=2682146). I have my 4X hd back .... yupi, yupi, yupi, yupi, yupi, ..... you guys are just the greatest. Once again a big thank you all of you. The 4X HD is working like a charm, a thank-you to the forum.

Categories

Resources