Hi,
Does anyone know how to fix the problem in the attached pictures?
Thanks,
Seems to be an issue with your bootloader, try flashing a new one through fastboot
fastboot flash hboot hboot.img
Sent from my Nexus 4 using xda premium
i got same problem, Does anyone know how to fix it?
Fastboot flash a Google stock image for it. Worked for me..... twice
Sent from carbon note 2 on XDA premium app
Booting Failed
Im having the same problem, Can someone help me? I am a bit of a noob. i did download nexus root tool kit. But now i cant even get it to be seen on the computer. all i can hit is restart bootloader or power off. Everything else leads to booting failed.please help need tablet for school.
Help!!!
Okay. i messed up somewhere when trying to flash back to factory rom and completely restore my Nexus 7(I had rooted it and flashed to a custom rom perfectly fine, just wanted to go back to factory just because). Because now whenever i turn on my nexus it says booting failed. Can someone use team viewer or something with me to help me get this fixed. i really need my Nexus for school...
If you need teamviewer I'll be at a PC soon but you should be able to do all this yourself quite easily
Which model do you have 2012? 2013? WiFi? Gsm?
Do you have adb and fastboot set up on PC?
Windows? Linux?
Bootloader locked or unlocked right now?
Boot to bootloader and write down everything on screen here
Let me know and I'll get you the proper software
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for replying
demkantor said:
If you need teamviewer I'll be at a PC soon but you should be able to do all this yourself quite easily
Which model do you have 2012? 2013? WiFi? Gsm?
Do you have adb and fastboot set up on PC?
Windows? Linux?
Bootloader locked or unlocked right now?
Boot to bootloader and write down everything on screen here
Let me know and I'll get you the proper software
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the 2012 wifi version of the Nexus 7. i have ADB set up on my computer but i'm not sure about fastboot... Bootloader is unlocked. just booted to bootloader, it says google in the middle, a little unlocked lock at the bottom, and with the volume up and down i can choose start, restart bootloader, recovery mode, and power off. When i press start, nothing happens, the screen flashes though for half a second.... Sometimes it will say boot failed at the top left.
Thanks in advanced. i would extremely prefer to do this in team viewer because i'm good with electronics most of the time, but when it comes to this stuff i have no clue what to do. i have watched countless videos with no success.
You'll need to download factory image here
https://developers.google.com/android/nexus/images
Unzip it
Run flash all.bat from fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
I won't be near a PC for about 7-8 hours. If your stuck let me know around then and I can help
Sent from my Nexus 4 using XDA Premium 4 mobile app
THanks!
demkantor said:
You'll need to download factory image here
https://developers.google.com/android/nexus/images
Unzip it
Run flash all.bat from fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
I won't be near a PC for about 7-8 hours. If your stuck let me know around then and I can help
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok so i did the flash all thing and it worked!!! Now do i follow the custom recovery steps? because still when i press start it says booting failed
Edit: i went ahead and did the recovery thing from the one i downloaded from the site you told me to go to. and i still get booting failed
Try this
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now double check you downloaded the correct factory image probably a good idea to check md5sum as well
Then run flashall.bat again
Let me know if that works
Sent from my Nexus 4 using XDA Premium 4 mobile app
errors
demkantor said:
Try this
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now double check you downloaded the correct factory image probably a good idea to check md5sum as well
Then run flashall.bat again
Let me know if that works
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
when typing in the first command it gave me all okays until erasing 'cache'...
Failed <command write failed <No such device or address>>
After that i thought "hmm maybe thats supposed to happen?" so i went ahead to the erase boot command, again
erasing 'boot'...
Failed <command write failed <unknown error>>
Please help. im soooo confused im about to explode... haha
Thanks
EDIT: i realize whenever i run the flash all file, it says
sending bootloader
Failed <command write failed <Invalid argument>>
and then bootloader reboots fine...
then
checking version-bootloader...
Failed
Device version-bootloader is '4.18' .
Update requires '4.23' .
Is this why its not working?? if so how do i update my bootloader?
Can you either attach a pic or write down everything from bootloader screen line by line
Sent from my Nexus 4 using XDA Premium 4 mobile app
Pics
demkantor said:
can you either attach a pic or write down everything from bootloader screen line by line
sent from my nexus 4 using xda premium 4 mobile app
Click to expand...
Click to collapse
View attachment 2551680
View attachment 2551681
First Picture is the flashall file
Second picture is when i type the fastboot erase system -w command
xlilCHeesEitxX3 said:
View attachment 2551680
View attachment 2551681
First Picture is the flashall file
Second picture is when i type the fastboot erase system -w command
Click to expand...
Click to collapse
If you meant the bootloader screen of my nexus im sorry!!
okay so it has the volume rocker buttons and stuff at the top right as usual.
now in order from top to bottom
Fastboot mode (red letters)
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader Version - 4.18
Baseband version - N/A
Serial Number - 015d24a42b23ea09
Signing - not defined yet
Lock State - Unlocked (red letters)
hope this is what you were looking for
well I'm at a PC if you want to use team view, if you don't get this until later what I would do is flash everything separate
fastboot flash bootloader bootloader-grouper-4.23.img
(or whatever it is labled)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash boot boot.img
if this doesn't work than put up the screenshots of cmd again
Team Viewer
demkantor said:
well I'm at a PC if you want to use team view, if you don't get this until later what I would do is flash everything separate
fastboot flash bootloader bootloader-grouper-4.23.img
(or whatever it is labled)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash boot boot.img
if this doesn't work than put up the screenshots of cmd again
Click to expand...
Click to collapse
I really hope you are still able to use Team Viewer at the time. I tried flashing everything separately but still a no go ....
Thanks so much for all the help so far.. i really appreciate it.
Screenshots
xlilCHeesEitxX3 said:
I really hope you are still able to use Team Viewer at the time. I tried flashing everything separately but still a no go ....
Thanks so much for all the help so far.. i really appreciate it.
Click to expand...
Click to collapse
View attachment 2552860
View attachment 2552861
1st image is when i flash the system
2nd is when i flash the bootloader
Yeah this is not looking too good, I've seen a few times that people have gotten there nexi working when the failed boot pops up but when all these flashes fail it becomes unlikely. Is warranty up? If it is we can try when I get to a PC again but that may not be for a while.
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Yeah this is not looking too good, I've seen a few times that people have gotten there nexi working when the failed boot pops up but when all these flashes fail it becomes unlikely. Is warranty up? If it is we can try when I get to a PC again but that may not be for a while.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think my warranty is up... but alright. maybe im doing something wrong? who knows hopefully we can get it fixed
---------- Post added at 10:54 AM ---------- Previous post was at 10:26 AM ----------
xlilCHeesEitxX3 said:
I think my warranty is up... but alright. maybe im doing something wrong? who knows hopefully we can get it fixed
Click to expand...
Click to collapse
i finnaly got the bootloader to flash. so now everything works except when i try to flash the system... it says
erasing 'system'...
OKAY ( 0.095s)
Sending 'system' <471804 KB>...
FAILED <unknown status code>
finished. total time: 61.355s
hopefully you know of a fix
Related
Ok so i got the 2.3.5 soak test installed awhile ago and wanted to try to go back to 2.3.4 so after going through the forums i found a way to use recovery with bootstrap so then i went and installed the Stock-rooted-198_7 that loki posted and now my mopho turns on with no motorola logo it only says failed to boot 1 starting rsd protocol
willistheyounger said:
Ok so i got the 2.3.5 soak test installed awhile ago and wanted to try to go back to 2.3.4 so after going through the forums i found a way to use recovery with bootstrap so then i went and installed the Stock-rooted-198_7 that loki posted and now my mopho turns on with no motorola logo it only says failed to boot 1 starting rsd protocol
Click to expand...
Click to collapse
I'd hate to tell you this but you are LOCKED. The bad part is you need to flash a Locked ROM but without access to bootstrap it's going to be a problem. Try this;
battery pull
power on holding down the volume down button
pray to the phone spirits for "fastboot" to show up
Post you results
Lokifish Marz said:
I'd hate to tell you this but you are LOCKED. The bad part is you need to flash a Locked ROM but without access to bootstrap it's going to be a problem. Try this;
battery pull
power on holding down the volume down button
pray to the phone spirits for "fastboot" to show up
Post you results
Click to expand...
Click to collapse
yes i can get it to fast boot but i have no idea what to do
willistheyounger said:
yes i can get it to fast boot but i have no idea what to do
Click to expand...
Click to collapse
This is good news. I'm going to need some time (couple hours) but I may have a way to get you running. I need to get things set up as I'm working on Ubuntop right now and need to flash back.
Lokifish Marz said:
This is good news. I'm going to need some time (couple hours) but I may have a way to get you running. I need to get things set up as I'm working on Ubuntop right now and need to flash back.
Click to expand...
Click to collapse
ok thanks
Oh, while you are waiting, download this root-unlock-relock pack. It's going to have the driver files and software you will need for me to walk you through this.
i already have it
Extract the zip I pm'd you and place "system.img" it in the "Unlock" folder of the root-unlock-relock
Download and extract RDL3_unlocked.smg and place it in the "Unlock" folder
Boot phone while holding down the volume down button
When you see "fastboot" on the phone's screen hit volume up
Connect the phone to your computer
In the "Unlock" folder, double click the "command prompt" shortcut
Enter the following commands
Code:
moto-fastboot flash rdl.bin RDL3_unlocked.smg
moto-fastboot devices
moto-fastboot erase system
moto-fastboot flash system system.img
moto-fastboot reboot
If this does not work I'm not sure where to go at this point. There is no 2.3.5 "update.zip" or SBF that you could flash right now. You may very well have to get a replacement.
I'm not going to be able to help beyond this point as I killed my battery with no way to charge it so we both may be SOL
This is what i get
C:\Users\Will\Desktop\Photon\Root-Unlock-Relock\Root-Unlock-Relock\moto-fastboot
>moto-fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)... OKAY [ 0.289s]
writing 'rdl.bin'... OKAY [ 0.001s]
C:\Users\Will\Desktop\Photon\Root-Unlock-Relock\Root-Unlock-Relock\moto-fastboot
>moto-fastboot devices
038061024440b4d7 fastboot
C:\Users\Will\Desktop\Photon\Root-Unlock-Relock\Root-Unlock-Relock\moto-fastboot
>moto-fastboot erase system
erasing 'system'... FAILED (command write failed (Unknown error))
C:\Users\Will\Desktop\Photon\Root-Unlock-Relock\Root-Unlock-Relock\moto-fastboot
>moto-fastboot flash system system.img
sending 'system' (262144 KB)... FAILED (command write failed (Unknown error))
C:\Users\Will\Desktop\Photon\Root-Unlock-Relock\Root-Unlock-Relock\moto-fastboot
>
I don't see a moto-fastboot oem unlock in there after devices and shouldn't it be moto-fastboot erase recovery?
willistheyounger said:
This is what i get
Click to expand...
Click to collapse
So unlocked RAMloader exploit is a fail. The only other thing I could think of is SBF a 2.3.5 engineering build? If that won't work then yes you have bricked until we get a full update zip or SBF for this.
Again. Don't feel bad as I'm now (hopefully only) softbricked with a dead battery and no charger.
Kevets said:
I don't see a moto-fastboot oem unlock in there after devices and shouldn't it be moto-fastboot erase recovery?
Click to expand...
Click to collapse
You are thinking about unlocking. This is dealing with bricked 2.3.5
Its really not that big of a deal i can go to sprint and have them get me another one i mainly use my epic touch
Sent from my SPH-D710 using XDA
but if you can help me out it would be better because then i wont have to make something up
Sent from my SPH-D710 using XDA
willistheyounger said:
but if you can help me out it would be better because then i wont have to make something up
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I'm bricked because battery died during flashing in fastboot and will be without a phone for at least a couple days.
Unless the policy has changed recently, it doesn't matter. If you have the service coverage they simply replace it.
Oh **** man now i feel bad
Sent from my SPH-D710 using XDA
willistheyounger said:
Oh **** man now i feel bad
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
It's all good. It's my fault for not buying and external charger when I got rid of my dev photon.
yea whats worse for me i just ordered 2 cases a extra battery a car dock and should get it tuesday
Sent from my SPH-D710 using XDA
Maybe a solution to this problem is flashing electrify 2.3.5 sbf, just to get the phone working.
But then you will be stuck with electrify.
maxon_yalta said:
Maybe a solution to this problem is flashing electrify 2.3.5 sbf, just to get the phone working.
But then you will be stuck with electrify.
Click to expand...
Click to collapse
I was trying not to send him down that road but that is an option
I already made an appointment at my local sprint store
Sent from my SPH-D710 using XDA
A long while back I used the HTC official unlock ( cant remember what it is called ), I installed clockword recovery (5.8.1.5) and rooted but didnt mess with my rom beyond that.
Today my daughter was playing a game and the phone suddenly rebooted (saw it happen) it reboots to recovery. I tried clearing the cache and factory reset still wouldnt boot. Decided to try a ROM to see if that would fix it (did CG ROM Jelly Bean) no change. Not really sure what my next step should be.
It does say "E:unknown misc partition fs_type "ext4"" at the bottom of the clockwork recovery page.
still working on this to no avail, not really sure what to try next. I am worried the tablet may have died proper like.
Halp please!
Sent from my SPH-L900 using xda app-developers app
yehoshua said:
Halp please!
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
try flashing ruu with fastboot see http://forum.xda-developers.com/showthread.php?t=1428104
copperdawgnc said:
try flashing ruu with fastboot see http://forum.xda-developers.com/showthread.php?t=1428104
Click to expand...
Click to collapse
Sorry for the long reply, I spent a TON of time figuring out how to do all this stuff for the version of stuff I beleive I have. At any rate the problem I am consistantly encoutnering is that I cant get to hboot at all. I also cant find advice on how I might repair hboot from recovery. I do have adb access from recovery and can do adb reboot-bootloader but it just thinks for a bit and comes back to recovery. I also tried many times doing the vol-down + power button to get to hboot.
So what is the next step if you cant get to hboot?
so have you done something like
adb reboot-bootloader
fastboot flash zimage zImage
fastboot flash zimage zImage
fastboot reboot
copperdawgnc said:
so have you done something like
adb reboot-bootloader
fastboot flash zimage zImage
fastboot flash zimage zImage
fastboot reboot
Click to expand...
Click to collapse
Yes, when I do adb reboot-bootloader it just reboots into recovery again. fastboot gives the <waiting for device>. I also tried copying the rom.zip from the ruu to an sd card and then using recovery to flash to it. It starts to try then ends with "Installation Aborted".
Not sure if there is a small easy to flash to rom that I could try, even if it wouldnt have much in the way of function. Not sure if this whole thing implies my flash is partially dead or something.
Thanks
Anyone have any ideas for me? I don't really see other posts covering this problem.
Thanks
yehoshua said:
Anyone have any ideas for me? I don't really see other posts covering this problem.
Thanks
Click to expand...
Click to collapse
Moderator moved the thread (thanks), mayhap someone in here can help. Anyone have any ideas?
Only thing I can think of is grabbing a proper RUU executable, there might be a thread in the view dev area that links to some, plugging in your view and try running that. You'll loose root and all but it may bring it back to life
Sent from my ADR6410LVW using Tapatalk 2
gersto said:
Only thing I can think of is grabbing a proper RUU executable, there might be a thread in the view dev area that links to some, plugging in your view and try running that. You'll loose root and all but it may bring it back to life
Sent from my ADR6410LVW using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the idea Gersto but I cant get to fastboot so I cant use an RUU (Unless there is something I dont know). I experimented a bit trying to get the errors about the misc partition and ext4 to go away but nothing I did to that stuff seemed to persist. I do have root and can access it from adb shell.
Not sure if it is the culprit but if anyone knows how to fix the problem wit my misc partition I am all earsl.
Thanks
I take no responsibility for any damages incurred to your phone
Please use this script only when necessary
Here is a little script I put together to fastboot L9s with ability to flash/restore ics xloader and uboot (p760, p765, p768, p769) jb (p760)
*I've only tested it on Win 7, but it should work on Vista , not sure about XP and 8
Very useful post about installing the drivers
*Some phones may need a different timing, 4 seconds won't work, worth to try between 0 to 4s and see what works best
Original thread about fastboot
http://forum.xda-developers.com/showthread.php?t=2119090
It's based on wpark - [DEV][Bootloader] u-boot / omap4boot for P920/P720/P940 and its variant
update: file updated, mylk Thanks for catching the mistake!
update2: added p769 20f
Thanks, I'll try this out once I'm home, maybe my phone will finally let me fastboot. Whenever I've tried before, it just normally reboots, doesn't switch to fastboot mode.
Sent from my LG-P768
i think there is some errot in your start.bat .
IF /I '%INPUT%'=='6' GOTO Selection5 ( i think it should be Selection6 , right ? )
and here is my p1.bin an p2.bin . mine is P765 JB (HongKong V20D) . hope you can put this into your file . and may help others .
View attachment 1986726
Tried the method in the link in the 1st post, didn't work. Tried this, still nothing. I get the same "unexpected 2ndstage response" error.
is there somebody who has tried fastboot ?
how is the screen like of the phone ?
is it just a black screen ?
and why the cmd just go to the folder of "yours" then i cant find anything in this folder .
sorry for my nood question ......
cris7i said:
Tried the method in the link in the 1st post, didn't work. Tried this, still nothing. I get the same "unexpected 2ndstage response" error.
Click to expand...
Click to collapse
Both work the same under the hood. Perhaps you've wrong drivers if you get same error msg.
mylk said:
is there somebody who has tried fastboot ?
how is the screen like of the phone ?
is it just a black screen ?
and why the cmd just go to the folder of "yours" then i cant find anything in this folder .
sorry for my nood question ......
Click to expand...
Click to collapse
#1 is just a general fastboot, you can put whatever (boot.img, recovery.img, etc) you want to flash via fastboot in "yours" folder - type: fastboot devices and you'll see if your phone is recognized
and the rest is mainly for recovery, ics xloaders and uboots work nicely with offline flashing method also several people mistakenly soft bricked their phones with omap4boot by flashing prada files which can't happen with this tool
For me general fastboot works on ArchLinux. But I only put recovery with it...
Rixx666 said:
For me general fastboot works on ArchLinux. But I only put recovery with it...
Click to expand...
Click to collapse
of course if you have functional rom and unlocked bootloader you don't need it
Hi there, its been a while since I tried fastboot again, but I have good news. Fastboot worked on my P768 using this method, I selected option 1. Then I was able to send recovery to my phone and then root the phone using a flashable SuperSU zip! 'adb reboot recovery' takes me straight into CWM!
I have some questions though.
Is fastboot permanently on the phone like it is on the P760 now? or do I have to use this program each time to send fastboot commands?
Does this mean that I could potentially flash a custom rom to my phone now? I know all the custom roms out there are not for the P768, so I will get camera problems. But is this the missing piece of the puzzle for custom rom development/testing?
Thank you lelus for this great tool!
donk165 said:
Hi there, its been a while since I tried fastboot again, but I have good news. Fastboot worked on my P768 using this method, I selected option 1. Then I was able to send recovery to my phone and then root the phone using a flashable SuperSU zip! 'adb reboot recovery' takes me straight into CWM!
I have some questions though.
Is fastboot permanently on the phone like it is on the P760 now? or do I have to use this program each time to send fastboot commands?
Click to expand...
Click to collapse
Fastboot is definitely there but something doesn't get passed along during adb reboot bootloader or oem-unlock and phone just reboots instead of booting to fastboot.
Does this mean that I could potentially flash a custom rom to my phone now? I know all the custom roms out there are not for the P768, so I will get camera problems. But is this the missing piece of the puzzle for custom rom development/testing?
Click to expand...
Click to collapse
I'm pretty sure* you can use Android Kitchen to replace these files in latest Cyanogenmod zip with ones from p768 jb and have camera working.
*i might be wrong
Lelus said:
Fastboot is definitely there but something doesn't get passed along during adb reboot bootloader or oem-unlock and phone just reboots instead of booting to fastboot.
I'm pretty sure* you can use Android Kitchen to replace these files in latest Cyanogenmod zip with ones from p768 jb and have camera working.
*i might be wrong
Click to expand...
Click to collapse
great, keep it up @donk165
Thanks. When I find the time. I'm going to make a guide for unlocking the boot loader, pushing CWM with fastboot and rooting.
I'm not confident in building CM, but I did see another user who was willing to try but was stuck with a locked boot loader. Hopefully together we can get the ball rolling for P768 development.
Sent from my LG-P768 using xda app-developers app
donk165 said:
Thanks. When I find the time. I'm going to make a guide for unlocking the boot loader, pushing CWM with fastboot and rooting.
I'm not confident in building CWM, but I did see another user who was willing to try but was stuck with a locked boot loader. Hopefully together we can get the ball rolling for P768 development.
Sent from my LG-P768 using xda app-developers app
Click to expand...
Click to collapse
i think we need help from devs to port camera from official p760 cm to p768 maybe @markolino631 can do it for us, seen we had unlocked bootloader and able to push cwm using fastboot.
I got a P769 from a friend and it is total dead,black screen, no SW update or hard reset key combinations works, only can fastboot and shows a mirrored LG logo , on top right it says V0.5, but unable to flash x-loader, u-boot or recovery, always show the error "remote partition does not exists", i tried to erase the partitions with fastboot but still the error is same. does somebody experienced the same? they call this phone un-brickable
AttiqAamir said:
I got a P769 from a friend and it is total dead,black screen, no SW update or hard reset key combinations works, only can fastboot and shows a mirrored LG logo , on top right it says V0.5, but unable to flash x-loader, u-boot or recovery, always show the error "remote partition does not exists", i tried to erase the partitions with fastboot but still the error is same. does somebody experienced the same? they call this phone un-brickable
Click to expand...
Click to collapse
My guess is corrupted nand or partition table.
What did your friend do to the phone?
Well I don't know, he just sent me that it is not booting. Is there any tool / way to initialize the nand?
AttiqAamir said:
Well I don't know, he just sent me that it is not booting. Is there any tool / way to initialize the nand?
Click to expand...
Click to collapse
Not that I know of
Hey I know this has been a long time to reply but since nothing is working try this command in fastboot
fastboot oem format
I found this information here
http://www.omappedia.com/wiki/Android_Fastboot
The website has a lot of information
Sent from my LG-P769 using xda app-developers app
kuma82 said:
Hey I know this has been a long time to reply but since nothing is working try this command in fastboot
fastboot oem format
I found this information here
http://www.omappedia.com/wiki/Android_Fastboot
The website has a lot of information
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Just heads up, the fastboot files are from lg prada p940 which has somewhat different partition setup but it's definitely worth trying as a last resort if nothing else works.
Thank you for your help, i tried as you advised but it failed it replied as
FAILED (remote failure)
finished. total time: 0.001s
After screwing up when flashing the wrong u-boot and xloader in fastboot, my phone won't connect in debug mode and the notification bar crashes on 15% battery. I've tried everything imaginable to fix this, factory reset, flashing almost every kdz, updating through ota, completely removing everything through fastboot and reflashing a stock kdz. Please help, i've had this problem for 3 months and nobody else has this. I just need an estimate, does it sound like a hardware problem or a software problem?
Try flashing my persist image with fastboot and see if it fixed adb.
https://mega.co.nz/#!8pt0xCqA!3-uV70G_ItL46LwE8mYCQ7FUYMEXGYNU0KDUqQRVVbo
Messing with the persist image will mess up adb
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
Try flashing my persist image with fastboot and see if it fixed adb.
https://mega.co.nz/#!8pt0xCqA!3-uV70G_ItL46LwE8mYCQ7FUYMEXGYNU0KDUqQRVVbo
Messing with the persist image will mess up adb
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OMG, Kuma you are god sent. Thank you so much, I almost cried just seeing that device in adb. My phone is scanning the sd but if the camera and battery percentage works, everything will be fixed. No doubt thanked your post. Haha, again thanks soo much!!
If anyone else has this same problem this is what I did:
1.Downloaded kuma's persist.img
2.Moved the persist.img to the fastboot yours folder
3.Opened fastboot selected option 1, then used the command (fastboot flash persist persist.img)
4.reboot
Thank you both. This fixed my issue with ADB not showing up. Yay I have ADB back!
Sent from my LGMS769 using Tapatalk
can you reupload please mega link isn't working. thank you very much
tatsuyin said:
can you reupload please mega link isn't working. thank you very much
Click to expand...
Click to collapse
Hi tatsuyin, mega link has worked fine for me just now.
Cheers . Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
tatsuyin said:
can you reupload please mega link isn't working. thank you very much
Click to expand...
Click to collapse
If you're trying to download the mega file from your phone, once the web page loads press the menu button and select/check "request desktop site" and you should be able to download it.
OMG !! I cant belived.
Thank you !!!!
Almost . . . . . . . .
AlbinoCookie said:
If anyone else has this same problem this is what I did:
1.Downloaded kuma's persist.img
2.Moved the persist.img to the fastboot yours folder
3.Opened fastboot selected option 1, then used the command (fastboot flash persist persist.img)
4.reboot
Click to expand...
Click to collapse
So i thought it wad gonna work. Then at the end....it says this.....
writing 'recovery'...
C:\Users\Weldon Evridge\Android-Mobile-Phone-Tools\droid manager\Android_AIO_Flasher_1.00_by_Fonehacker\Android_AIO_Flasher\tools>
FAILED (remote: partition does not exist)
finished. total time: 2.275s
Hi, I think I might have a similar problem. I was running on stock JB for a while and then decided to give a try to CM10 or 11. I tried to flash CM11 without artas's recovery, so it did not work. So I've tried CM10, which seemed pretty buggy and camera was not working. Then I did all the reading etc and tried about 10 different roms based on 4.3, .4.4 and even stock rom, camera did not work anywhere.
Every time I try to open an app using camera, it reports: Unfortunately: com.android.camera has stopped. I have tried all kinds of resets (everything available in both CWM and TWRP), online kdz fix, back to stock rom (tried multiple versions of JB) but nothing seems to help. Any ideas? I've tried to flash this persist.img using adb but I got the same error saying that there is no such partition.
Thanks for response.
WeldonEvridge said:
So i thought it wad gonna work. Then at the end....it says this.....
writing 'recovery'...
C:\Users\Weldon Evridge\Android-Mobile-Phone-Tools\droid manager\Android_AIO_Flasher_1.00_by_Fonehacker\Android_AIO_Flasher\tools>
FAILED (remote: partition does not exist)
finished. total time: 2.275s
Click to expand...
Click to collapse
I'm not sure if you have fixed your phone yet, but try having a fresh offline flash, then copy the persist img.
Help bro
It (persist image) use only LG L9 .
Can I use for my motorola razr. Because I have same problem on my phone.
kuma82 said:
Try flashing my persist image with fastboot and see if it fixed adb.
https://mega.co.nz/#!8pt0xCqA!3-uV70G_ItL46LwE8mYCQ7FUYMEXGYNU0KDUqQRVVbo
Messing with the persist image will mess up adb
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hello, can you upload again this file?
Thanks!
So, the other night my Rezound slipped off a shelf and into the toilet. I pulled it out immediately, popped open the case and used a blow dryer on it, then stuck it in a bag of rice. The next day I stuck the battery in and it seemed to be working alright. Then I went to respond to a snapchat and found that the camera was not working. I thought maybe a simple restart might help, but the phone never restarted. I stuck it back in the bag of rice, thinking maybe their was still some moisture that could be pulled out. Today, after roughly 48 hours in the rice, I put the battery in, and it goes into the bootloop.
I pulled the SIM, tried going into recovery, factory reset, wipe cache, etc. Everything I can find on any forum does not work. I found a couple different PH89IMG.zip files, but after the bootloader analyzes them, it says that it can't do anything because they're older versions that what is on the device, which is "4.05.605.14 710RD" according to my wife's phone. I also downloaded the RUU, but the device has to be powered on for that to work, and it won't go past the white screen with green htc logo.
I would really love to resolve this without doing a factory reset, because there are a few things saved on the device itself that I can't really replace. Does anybody have any ideas for anything else I could try? Including maybe having the PH89IMG.zip file for the stock version of Android...
Is there a way that I could extract the PH89IMG.zip file from my wife's rezound, or utilize her phone in any way to repair my own?
ggoodman1022 said:
Is there a way that I could extract the PH89IMG.zip file from my wife's rezound, or utilize her phone in any way to repair my own?
Click to expand...
Click to collapse
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
mjones73 said:
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
Click to expand...
Click to collapse
Thanks. I'll give that a shot. It was working the next day, but then stopped after a restart. And it was only in the water for maybe 2 seconds, max. My wife's phone fell in a pool before, and got pulled out about a minute later, then worked after about 48 hours in rice.
mjones73 said:
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
Click to expand...
Click to collapse
So editing the version listed in the .txt file made it so it didn't hang up on loading the file, but then it just refreshed the main bootloader screen. When I select fastboot, or go to restart the phone, it's still hung up in the bootloop :crying:
I'm not up for an upgrade until November 1, so I've been using my OG Incredible...
ggoodman1022 said:
So editing the version listed in the .txt file made it so it didn't hang up on loading the file, but then it just refreshed the main bootloader screen. When I select fastboot, or go to restart the phone, it's still hung up in the bootloop :crying:
I'm not up for an upgrade until November 1, so I've been using my OG Incredible...
Click to expand...
Click to collapse
Can you get to recovery? I see you have no recovery. You can try to fastboot a recovery.img, I am sorry but sounds like you screwed up your system, you will be lucky if it accepts a recovery. I deal with lots of broken phones in the business I am in and sorry to say once they are water damaged they 90 percent of the time they end up useless. If you need help with fastboot I will help.
jhr5474 said:
Can you get to recovery? I see you have no recovery. You can try to fastboot a recovery.img, I am sorry but sounds like you screwed up your system, you will be lucky if it accepts a recovery. I deal with lots of broken phones in the business I am in and sorry to say once they are water damaged they 90 percent of the time they end up useless. If you need help with fastboot I will help.
Click to expand...
Click to collapse
How does one go about trying to "fastboot a recovery.img?" I'm very limited in my knowledge on these things...
ggoodman1022 said:
How does one go about trying to "fastboot a recovery.img?" I'm very limited in my knowledge on these things...
Click to expand...
Click to collapse
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
kcipopnevets said:
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
Click to expand...
Click to collapse
I'll give this a shot next time I have access to a windows machine... Some time in the next few days or so
ggoodman1022 said:
I'll give this a shot next time I have access to a windows machine... Some time in the next few days or so
Click to expand...
Click to collapse
This can be done on a Mac or Linux box as well, ADB is available for both, just substitute the appropriate filenames or commands for each OS.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
This can be done on a Mac or Linux box as well, ADB is available for both, just substitute the appropriate filenames or commands for each OS.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Sweet!! I'll look into it after I finish my homework
kcipopnevets said:
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
Click to expand...
Click to collapse
So I finally got around to doing this, after buying a replacement phone off a guy on Craigslist, but I would still like to try and get this phone back up and running... I downloaded all the files and installed adb, etc. When I try to run the command, "fastboot flash recovery TWRP_2.6.3.0_Vigor_PH98IMG.zip" I get the following in the terminal:
sending 'recovery' (6323 KB)...
OKAY [ 1.464s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.780s
Any other ideas??
ggoodman1022 said:
So I finally got around to doing this, after buying a replacement phone off a guy on Craigslist, but I would still like to try and get this phone back up and running... I downloaded all the files and installed adb, etc. When I try to run the command, "fastboot flash recovery TWRP_2.6.3.0_Vigor_PH98IMG.zip" I get the following in the terminal:
sending 'recovery' (6323 KB)...
OKAY [ 1.464s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.780s
Any other ideas??
Click to expand...
Click to collapse
You don't flash the zip, extract the file and flash the recovery.img file.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
You don't flash the zip, extract the file and flash the recovery.img file.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
got it. thanks! it said the recovery was successful, but it still gets stuck in the bootloop :crying:
It may be time to admit what I feared from the moment it hit the water...
ggoodman1022 said:
got it. thanks! it said the recovery was successful, but it still gets stuck in the bootloop :crying:
It may be time to admit what I feared from the moment it hit the water...
Click to expand...
Click to collapse
Wipe, flash a ROM, and manually flash boot image... Other than that, could be toast.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
Wipe, flash a ROM, and manually flash boot image... Other than that, could be toast.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Can it be a stock ROM, or would it have to be something like CyanogenMod?
ggoodman1022 said:
Can it be a stock ROM, or would it have to be something like CyanogenMod?
Click to expand...
Click to collapse
I think its irrelevant at this point... Personally, I would use EclipticRez v9 or Tachyon as they are both rock solid ROMs. EclipticRez includes an Aroma installer script, so it might be a little easier (select S-ON and Lunar kernel).
Sent from my Nexus 4 using Tapatalk
acejavelin said:
I think its irrelevant at this point... Personally, I would use EclipticRez v9 or Tachyon as they are both rock solid ROMs. EclipticRez includes an Aroma installer script, so it might be a little easier (select S-ON and Lunar kernel).
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I actually found this thread earlier - http://forum.xda-developers.com/showthread.php?t=2632629 and followed the instructions, it was giving me some trouble around step 10 and kept going back into the bootloop. Then I tried it for probably the 5th time and it finally worked!! So the phone is back to full function now. I've been out of the house for a few hours, but it worked before your last reply literally right before I walked out the door.
Thank you SOOOO SOOOO SOOOOO much for the advice both on this thread and on that one I mentioned above (since it was also your instructions there)
ggoodman1022 said:
I actually found this thread earlier - http://forum.xda-developers.com/showthread.php?t=2632629 and followed the instructions, it was giving me some trouble around step 10 and kept going back into the bootloop. Then I tried it for probably the 5th time and it finally worked!! So the phone is back to full function now. I've been out of the house for a few hours, but it worked before your last reply literally right before I walked out the door.
Thank you SOOOO SOOOO SOOOOO much for the advice both on this thread and on that one I mentioned above (since it was also your instructions there)
Click to expand...
Click to collapse
No prob... glad you got it working. Water damage is weird, hopefully it sticks!
acejavelin said:
No prob... glad you got it working. Water damage is weird, hopefully it sticks!
Click to expand...
Click to collapse
The [semi] good news is that I found one on Craigslist (same phone because I really like it) for just $60 a couple days after I got fed up with using the OG Incredible. And the guy had 2 extra batteries, a case, and ghost armor on the screen as well. So now I have the original Rezound and the spare.