Related
Hi Moto guys
I bought this RAZR. It is a GSM one without operator customizing.
I rooted it normally and tried to update to ICS leak (this one if I remember well).
It didn't work.
Anyway I downgrade back to Gingerbread and tried to flash in recovery the MIUI V4 zip.
It bootlooped.
So I wanted by the same way to downgrade to 2.3.6 again.
It was a fail.
From this, I had the flash failure screen at the beginning and lost the recovery.
Because of a "Battery Low" I made a factory cable and I can access again to the "flash failure" screen.
I found a tuto relating to the same problem than me and tried to apply it.
I downloaded this rom (SPDREM_U_01.6.5.1-167_SPU-15-M2-1-DE_1C.91P_0A.6C_TMDE_CFC_HWp2b_SIGNED.xml.zip) as explained and tried to flash it in RSD lite.
The problem is:
I have no error message, it just stays stuck on "6/11 flash system "system_signed".
I let it several hours, it never passed away this step.
With "Eternityprj_Fla**** script it's the same, it's blocked at "system writing..."
I don't really know if I'm considered to be on ICS or GB. My bootloader version is 0A.75 so I guess ICS one.
Any idea to reanimate this XT910?
Thanks for the help you could bring to me
P.S: I tried these roms since the first fail
-SPDREM_U_01.6.5.1-167_SPU-15-M2-1-DE_1C.91P_0A.6C_TMDE_CFC_HWp2b_SIGNED.zip
-SPDREM_U_01.6.5.1-167_SPU-15-M2-1-FR_SIGNEuropeAustraliaEMEA_USASPDRRTFR_HWp2b_Service1FF_fastboot.xml.zip
-SPDREM_U_01.6.5.1-73_SPU-11-PASS-10_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
-SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
Since I use XP in a VIRTUALBOX machine, I have an icon with activity on device.
During this operation, the activity on the phone is important
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe flash system sy
stem.img
sending 'system' (793344 KB)...
OKAY [ 28.541s]
Click to expand...
Click to collapse
As it is to this step, no activity...
writing 'system'...
Click to expand...
Click to collapse
I tried with normal fastboot executable from SDK and erpj-fastboot.exe, no difference.
Is it possible I make something wrong with my factory cable?
I don't think so because it makes my phone booting as I plug it and it writes normally boot.img for example with fastboot.
Your help would be appreciated very much guys ^^
Thanks!
Solved!
I can't explain why but I managed to access recovery even if system flash with fastboot never ended.
I flashed ICS rom and it booted well.
So it's solved even if I can't give explanations.
Thanks anyway.
flash fails...repeatedly
This has been covered extensively, but mine is still screwed up, i rooted the phone with clockwork mod. When the official ICS cam eout, i tried to manually download it. I have unrooted the phone and tried to install ics, it failed. So i tried flashing back to factory because clockwork was still popping up on boot. The flash continues to fail. I have tried using moto-fastboot in command prompt, i ha tried rsd lite with the flash(4 different ones). It keeps failing and i end up in the ap fastboot mode. it takes 2 tries to get the phone to boot normally and occasionally the clockwork boot menu pops up on reboot. Any ideas how to just start from scratch. As seen by the problems i have caused myself, i am a complete amateur here.
A little info, the phone is about 8 months old, rooted it once successfully, it is currently unrooted(i tried to reroot but got hung up in ap fastboot), updated drivers twice, moved the flash files all arounf my computer, using windows 7 64 bit. thanks to anyone who may help
Ok ok ok...
if i have an advice, before flashing, read read & read again.
So now.
Give me more info about your phone(xt910 / xt912 / europe / asia / latam /usa ) ??
Can you rsd to system_signed, or flash it manually through fastboot ?
When you installed ics manually which error did you have?
If you can, try to flash system_signed then reflash the OTA package with official recovery & wipe data. But i guess it wont work. For now i can't help you more without more info.
So tell me all you can and write it clear.
Or try this through rsd lite or fla**** http://forum.xda-developers.com/showthread.php?p=28199183
Sent from my XT910 using xda premium
yes, now ics fastboot file is out, you can easily fastboot to get back.
it is usa...i am downloading the ics fastboot now. I have tried the fastboot method with the latest gingerbread build, and also using the command prompt and flash commands....will let you know
thanks
Flash failed right away....how do i know i have the correct drivers? any other ideas?
I had the same issue when attempting to flash. Make sure you switch to a usb 2.0 port.
After that find the moto-fastboot package and then flash all the files manually using moto-fastboot instead of regular fastboot.
You have to do that for every single file. The file names are in the xml in the fastboot file.
For use on Verizon variant HTC ONE MAX only!!!
S-off users only!!!!
Software version 1.11.605.4
Stock Recovery-
http://www.androidfilehost.com/?fid=23252070760974293
flash via fastboot
fastboot flash recovery recovery.img
Stock Kernel (insecure)-
http://www.androidfilehost.com/?fid=23252070760974294
flash via fastboot
fastboot flash boot boot.img
System Image (must unrar first to get system.img)
http://www.androidfilehost.com/?fid=23252070760974295
flash via fastboot
fastboot flash system system.img
Flashable radio-
download this:
https://www.mediafire.com/?ucj15e2zavewnbq
vzw_max_radio.zip ba7f0302040731949a4db3cb0c9c4e98
double check the md5 matches above.
flash in ruu mode:
-phone in fastboot
-open cmd
-enter:
fastboot devices
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip vzw_max_radio.zip
fastboot reboot-bootloader
if you see a baseband in the bootloader screen now,thats a good sign
fastboot reboot
Credits- Scotty1223 for working his radio magic
Jiggity Janx - afh mirrors
Awesome sauce, thank you :good:
@dottat is it possible to write a script for those for the n00bs that may be the faint of heart type? Like a flash-all deal? I'm good with manually flashing them all individually but for those that aren't that would be dope.. Can you even do that with the .img's for HTC devices?
Murrda said:
@dottat is it possible to write a script for those for the n00bs that may be the faint of heart type? Like a flash-all deal? I'm good with manually flashing them all individually but for those that aren't that would be dope.. Can you even do that with the .img's for HTC devices?
Click to expand...
Click to collapse
dottat worked with the Flashify dev to get it working with the One Max. Recommend everyone use that.
HELP !!!
I tried flashing the system img, but keep on getting this error msg below. Can't do anything else but go into Custom Recovery.
error: cannot load 'system.img': Not enough space
---------- Post added at 09:27 PM ---------- Previous post was at 09:15 PM ----------
mustangmao said:
HELP !!!
I tried flashing the system img, but keep on getting this error msg below. Can't do anything else but go into Custom Recovery.
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
When sending boot image after i use fastboot erase boot commend, it just stuck on sending 'boot' <16384 kb> and nothing happens. Any help suggestion?
...Send boot.img when flashing boot. Send system when sending system. Can't flash system into boot partition
The boot partition is only 16 megs so if you try to flash a 2 gig file into it you'll prolly hang.
Flashing the 2gig system.img to the system partition properly will likely take some time. You have screenshots?
Sent from my HTC6600LVW using Tapatalk 4
That's exactly what i did following your instruction. Here's the steps i did (BTW: I will take screenshots as soon as i am home)
1) Went into TWRP and performed a wipe (Data, cache and system)
2) Connect MAX to PC (Win 7 64bit)
3) Go into Fastboot mode (tested using Fastboot devices and results came back with serial number)
4) Copied System and Boot img into the same folder as Fastboot/ADB
5) Issue commend: fastboot flash boot boot.img ---- Error: 1st it was stuck on sending, nothing happens for like 10 minutes, unplug then tried Run CMD with local admin, got a different error msg, this time it says FAILED (remote: not allowed)
6) Then I tried flash just system.img using fastboot flash system system.img --- got error: cannot load 'system.img': Not enough space
I then went back into TWRP, basically did a complete wipe of everything (lucky TWRP was intact), went back into Fastboot mode and did another erase.
1) Enter Fastboot mode and issued: Fastboot erase boot, recovery and system -- All went fine
2) Then tried flash individual recovery/boot/system into its partition, same error msg as above
I thought i am toast for sure, but upon rebooting, i still have TWRP and Thank God i had a Full Backup stored on my external SD card, I just did a restore and everyone is back to where i left off..
thanks for your quick response
---------- Post added at 12:29 AM ---------- Previous post was at 12:08 AM ----------
mustangmao said:
That's exactly what i did following your instruction. Here's the steps i did (BTW: I will take screenshots as soon as i am home)
1) Went into TWRP and performed a wipe (Data, cache and system)
2) Connect MAX to PC (Win 7 64bit)
3) Go into Fastboot mode (tested using Fastboot devices and results came back with serial number)
4) Copied System and Boot img into the same folder as Fastboot/ADB
5) Issue commend: fastboot flash boot boot.img ---- Error: 1st it was stuck on sending, nothing happens for like 10 minutes, unplug then tried Run CMD with local admin, got a different error msg, this time it says FAILED (remote: not allowed)
6) Then I tried flash just system.img using fastboot flash system system.img --- got error: cannot load 'system.img': Not enough space
I then went back into TWRP, basically did a complete wipe of everything (lucky TWRP was intact), went back into Fastboot mode and did another erase.
1) Enter Fastboot mode and issued: Fastboot erase boot, recovery and system -- All went fine
2) Then tried flash individual recovery/boot/system into its partition, same error msg as above
I thought i am toast for sure, but upon rebooting, i still have TWRP and Thank God i had a Full Backup stored on my external SD card, I just did a restore and everyone is back to where i left off..
thanks for your quick response
Click to expand...
Click to collapse
BTW: Reason I need to flash the Stock Rom is because my One Max has this weird charging problem, where once the phone is turned on, it only charges to 35-37% and it stops, however if I leave it powered off and charge, it charges to 100% all the way. It must be a software issue and since I am using it on AT&T, Verizon CS and retail store doesn't even want to offer at help. So, i am kinda stuck with fixing the issue myself.
mustangmao said:
That's exactly what i did following your instruction. Here's the steps i did (BTW: I will take screenshots as soon as i am home)
1) Went into TWRP and performed a wipe (Data, cache and system)
2) Connect MAX to PC (Win 7 64bit)
3) Go into Fastboot mode (tested using Fastboot devices and results came back with serial number)
4) Copied System and Boot img into the same folder as Fastboot/ADB
5) Issue commend: fastboot flash boot boot.img ---- Error: 1st it was stuck on sending, nothing happens for like 10 minutes, unplug then tried Run CMD with local admin, got a different error msg, this time it says FAILED (remote: not allowed)
6) Then I tried flash just system.img using fastboot flash system system.img --- got error: cannot load 'system.img': Not enough space
I then went back into TWRP, basically did a complete wipe of everything (lucky TWRP was intact), went back into Fastboot mode and did another erase.
1) Enter Fastboot mode and issued: Fastboot erase boot, recovery and system -- All went fine
2) Then tried flash individual recovery/boot/system into its partition, same error msg as above
I thought i am toast for sure, but upon rebooting, i still have TWRP and Thank God i had a Full Backup stored on my external SD card, I just did a restore and everyone is back to where i left off..
thanks for your quick response
---------- Post added at 12:29 AM ---------- Previous post was at 12:08 AM ----------
BTW: Reason I need to flash the Stock Rom is because my One Max has this weird charging problem, where once the phone is turned on, it only charges to 35-37% and it stops, however if I leave it powered off and charge, it charges to 100% all the way. It must be a software issue and since I am using it on AT&T, Verizon CS and retail store doesn't even want to offer at help. So, i am kinda stuck with fixing the issue myself.
Click to expand...
Click to collapse
Are you unlocked? Because remote not allowed word indicates you are not. Can you confirm?
If your kernel is what got hosed you always flash my boot.IMG using the app flashify from the market from a booted rooted rom....assuming you are unlocked. Otherwise you will have create a flashable 0p3img.zip file and flash your kernels from hboot.
Sent from my HTC6600LVW using Tapatalk 4
dottat said:
Are you unlocked? Because remote not allowed word indicates you are not. Can you confirm?
If your kernel is what got hosed you always flash my boot.IMG using the app flashify from the market from a booted rooted rom....assuming you are unlocked. Otherwise you will have create a flashable 0p3img.zip file and flash your kernels from hboot.
Sent from my HTC6600LVW using Tapatalk 4
Click to expand...
Click to collapse
Yes, i am unlocked and S-OFF and rooted.
Tried another PC and using factory HTC cable, still the same error when flashing system.
Now, if the issue is with my OS, all i need to flash is just System.img and nothing else, right?
mustangmao said:
Yes, i am unlocked and S-OFF and rooted.
Tried another PC and using factory HTC cable, still the same error when flashing system.
Now, if the issue is with my OS, all i need to flash is just System.img and nothing else, right?
Click to expand...
Click to collapse
Load flashify (free) from the app store. Copy the boot.IMG to your SD card and flash boot from that app and report back.
Sent from my Nexus 7 using Tapatalk 4
dottat said:
Load flashify (free) from the app store. Copy the boot.IMG to your SD card and flash boot from that app and report back.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Flash boot.img from SDcard, everything went fine, just rebooted the phone, no issues. Now, how do i flash the System.IMG, which is the key to hopfully solve the battery charing issue? thanks
It should be via fastboot...but your fast boot install doesn't seem to like flashing anything to your phone. Do you have any other pcs you can try and can you see if your charging issue was fixed before proceeding ?
Sent from my Nexus 7 using Tapatalk 4
dottat said:
It should be via fastboot...but your fast boot install doesn't seem to like flashing anything to your phone. Do you have any other pcs you can try and can you see if your charging issue was fixed before proceeding ?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Wow, i am amazed, just flashing the boot.img and my phone starts chargin pass 37% now while the phone is powered on. Maybe i don't need to flash system.img after all. You rocks dude, thanks so much. Keep up the good work !!!
for what its worth,ive never been able to fastboot flash system system.img ive always gotten that space error.
ive just skimmed thru this,but the easiest way7 for you guys to flash this is to just open the radio zip and add the other images to it. then you can use those directions(oem rebootRUU,etc) and flash them all in one shot.
i could work with you guys to dump the relevant images that usually come in an ruu if you want to make up a full(unsigned) ruu.
I also had the charging issue.(wouldn't charge past 37%....Switched charger and the issue is no more.
sent from my humongous VZW HTC ONE MAX
mustangmao said:
Wow, i am amazed, just flashing the boot.img and my phone starts chargin pass 37% now while the phone is powered on. Maybe i don't need to flash system.img after all. You rocks dude, thanks so much. Keep up the good work !!!
Click to expand...
Click to collapse
Sorta figured that would happen...good deal.
Sent from my HTC6600LVW using Tapatalk 4
scotty1223 said:
for what its worth,ive never been able to fastboot flash system system.img ive always gotten that space error.
ive just skimmed thru this,but the easiest way7 for you guys to flash this is to just open the radio zip and add the other images to it. then you can use those directions(oem rebootRUU,etc) and flash them all in one shot.
i could work with you guys to dump the relevant images that usually come in an ruu if you want to make up a full(unsigned) ruu.
Click to expand...
Click to collapse
Lets make that
Sent from my HTC6600LVW using Tapatalk 4
I know someone was working on decrypting the verizon ruu. He said recently he had gotten busy with some other stuff. So itbis out there and somewhat done already. Just didnt want you guys to put a lotbinto it when there may be other avenues.
Jiggity Janx said:
I know someone was working on decrypting the verizon ruu. He said recently he had gotten busy with some other stuff. So itbis out there and somewhat done already. Just didnt want you guys to put a lotbinto it when there may be other avenues.
Click to expand...
Click to collapse
Good to know, thanks for the heads up.
Jiggity Janx said:
I know someone was working on decrypting the verizon ruu. He said recently he had gotten busy with some other stuff. So itbis out there and somewhat done already. Just didnt want you guys to put a lotbinto it when there may be other avenues.
Click to expand...
Click to collapse
any idea where it is? I hadn't seen one but there's an app for decrypting
I am new to cell phone mods. My goal was to gain some experience by rooting and replacing the os image on my Atrix 4G. I use it for my alarm clock which uses an application that won't run on newer version of android than v2.x.x. I successfully rooted and installed super use. I then installed Titanium Backup and did a full backup to sdcard. I installed Rom Manager, chose ClockworkMod Recovery and then the correct image, and told it to flash the recovery partition. Rebooted. Got an error with the android logo and a circle with a triangle. Went back to all the how to's and attempted to install unlockable_bootloader. It now comes up to rsd, seems to fail, then goes into fastboot. Fastboot devices sees it and I can reboot from fastboot but it goes back to the same place. HELP.
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Try this guide. http://forum.xda-developers.com/showthread.php?t=2262869
ravilov said:
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Click to expand...
Click to collapse
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
flash recovery failed
andresrivas said:
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I previously found a thread that described that process and tried it. Fastboot reported it failed flashing recovery.
That usually happens if the BL is not unlocked (properly).
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
reflash the pudding sbf to unlock the bl, then go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
flash boot failed
palmbeach05 said:
reflash the pudding sbf to unlock the bl, th
en go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
Click to expand...
Click to collapse
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Phatdaddy said:
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Click to expand...
Click to collapse
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
palmbeach05 said:
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
Click to expand...
Click to collapse
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Phatdaddy said:
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Click to expand...
Click to collapse
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
palmbeach05 said:
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
Click to expand...
Click to collapse
ls of /system/etc/install-recovery.sh says the file does not exist.
When I bricked my atrix i used the xatrix tool to unbrick it. works really well and once unbricked was fully unlocked so was easy to flash new roms
xatrix (dot) webs (dot) com
once on there website click to download tab to get the downloads
This tool will remove everything from phone root, unlock and install cwm. What you do after that is upto you. sometimes its easier to start over then figure out what went wrong when installing a mod.
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
And thats the part that confuses me. It says 141, but the recovery issue is acting like its a 145. I'm stumped, but i do believe there is an install-recovery.sh script or something thats preventing this thing from sticking after flashing. I'm really baffled by this b/c i ran 141 for the longest time, i did all my rooting, unlocking, and recovery flashing on 141, and got no issues. I could advise that you download and flash the ICS leak (the true leak, not the ROMs we have available) via fastboot and see if that changes the situation, but i don't want to advise you to do something and then a bigger mess appears.
Sent from my MB886 using xda app-developers app
Phatdaddy said:
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
Click to expand...
Click to collapse
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
overboard1978 said:
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
Click to expand...
Click to collapse
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
palmbeach05 said:
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
Click to expand...
Click to collapse
That should do it. If for some reason it doesnt the xatrix tool will wipe everything off the phone and start it over with 141 unlocked bootloader, with cwm. Only automated tool i found that will unbrick phone with rsd lite. Make sure phone is fully charged before starting xatrix tool as it wipes battery fast and if it dies you will need to start over.
Erase cashe was successful, erase data failed. Found reference to additional file to delete but it did not exist either. If I conttinue, I will repost. Thanks for everyone's effort trying to get this working.
Hi guys, after 10 hours of trying to get my P760 to life I finally, as a last resort, decided to open this threadh. Heres the deal, my friend gave me his P760 which was stuck at the boot logo, I firstly tried to fix it with LG mobile support tool but it got stuck at 15% after countless tries. Then I tried fixing it with Lg flash tool but it also gave me some errors "omap factory download fail lg p760". After that I couldnt access S/W mode anymore nor did the phone turn on, only black screen. When I connect it to my pc it just makes sounds of new device connected/disconnected. I tried this fastboot method http://forum.xda-developers.com/showthread.php?t=2292828 but couldnt make it work. Is the phone completely dead or is there anything more I can try? Any help is appreciated, thank you very much.
What was done to brick it in the first place?
Sent from my KYOCERA-C6745 using Tapatalk
I am not sure, my friend brought it to me and he didnt know the reason. Anyway I managed to get into fastboot on another computer and i tried to flash x loader and uboot with the bulit in options and i get the following error "FAILED (remote partition doesnt exist). What can I do next? Thank you for the reply.
EDIT I have tried to get the phone in S/W mode using this guide http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4 but I couldnt do it.
I am sure I have to flash something in fastboot so it would be great if someone could point me to exactly what. Thanks again.
EDIT 2 I tried to flash xloader and u boot from post #7 http://forum.xda-developers.com/showthread.php?t=2242444 and it gave me the remote partition error failed again. Is the phone "officially" dead?
My experience with this phone is that it is basically unbrickable, at least software wise, thanks to omap4boot. Fastboot is basically telling you the partition you specified doesn't exist. Check you are using the correct syntax. It should be fastboot flash u-boot u-boot.img and fastboot flash x-loader x-loader.img (I am assuming the files are named u-boot.img and x-loader.img).
Another possibility is that the partition table of the phone somehow got corrupted. In my opinion this is very unlikely, but it could happen if the phone is disconnected while flashing the GTP table with LGFlashTool. Let's hope that's not the case.
Good luck.
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Maha23 said:
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Click to expand...
Click to collapse
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
EdwinMoq said:
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
Click to expand...
Click to collapse
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Maha23 said:
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Click to expand...
Click to collapse
I'm seeing you using lelus method to fastboot...
1) Be sure you are in fastboot whith this command: fastboot devices
2) if the l9 is still in lg logo, just flash a recovery img into boot and recovery partition:
a) fastboot flash boot recovery.img
b) fastboot flash recovery recovery.img3)reboot the device, it must enter in recovery mode by force.
4) once in recovery just flash a custom rom as you wish
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
lecorbusier said:
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
Click to expand...
Click to collapse
Thanks for the reply. How do I perform the force hard reset? Yes, I couldnt get fastboot to work on win 10, on win 7 it works flawlessly.
Sent from my LG-D855 using XDA-Developers mobile app
Hello,
I have exactly the same problem with my p760, fastboot works so far but remote partition error and the phone stays always completely black.
Is there someone who has a new idea to fix it?
Hey,
I found this: http://massimoronca.it/2016/03/17/fastboot-failed-remote-partition-does-not-exist.html
but i dont really understand it, can someone help me?
Maha23 said:
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
Click to expand...
Click to collapse
readme again... try to flash a recovery.img into the boot partition
fastboot flash boot recovery.img
and then reboot... this foce the l9 to enter in recovery and then you can fotmat partitions in wipe options
---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------
Elsewhere you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
Hard reset is 10s power.
Such a swap of recovery and kernel could have happened after unbricking the phone, when the key combo for fastboot produces the LG recovery. That's why I flash stock twice, then it's right again & ready to root, install TWRP etc.
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Maha23 said:
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Click to expand...
Click to collapse
you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
puntoazul said:
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Srsly?
recovery partition image on boot?
Probably true. That would explain the strange behaviour of the key combos during boot, after unbricking the phone for the first time. The recovery has replaced the kernel, but the phone can still boot. Strange. Fastboot is unavailable, and the key combo for the recovery shows the "dead droid" and performs a factory reset.
Groszexxx said:
Srsly?
recovery partition image on boot?
Click to expand...
Click to collapse
Yes... is an effective method to boot by forced on TWRP or other recovery and then proceed to format all partitions and flash any rom consecutively. After flashing any rom the boot partition is rewrited by the boot.img of the rom.
I did this before on my own L9 for repair and other friends devices. Is totally safe
By the way, I'm not in warn
Hi all,
My phone has thrown a hissy fit
Bootloader was unlocked, then phone was rooted. All was running fine for approx. 2 months?
Opened stock camera app and phone crashed and rebooted followed by continuous bootloop.
I can't access TWRP (it just bootloops again) to wipe/flash firmware to start from fresh, so I tried reflashing recovery using fastboot which completed ok but still can't access TWRP (more bootloops).
Next I tried download mode and Lgup etc but can't get into download mode - more bootloops!
They only thing I can access is fastboot which I think works - "fastboot devices" shows its connected (And it flashed TWRP). I've wiped user data and cache with fastboot also.
Thoughts? Suggestions?
Cheers!
Adam
Sent from my SM-N910G using Tapatalk
Try to flash boot.. Fastboot flash boot boot.img
Thanks blazerempty - Have tried that now but no difference!
Got the boot.img from codefire, I saw on there all sorts of other files so; in for a penny and all that.
Flashed recovery.img, laf.img (which is download mode) neither made any difference!
I also tired aboot.img but It wouldn't let me flash that with unlocked bootloader so re-locked it (fastboot oem lock) and tried again but wouldn't let me flash it with a locked bootloader! Good ol' LG.
I've noticed the option to flash an update.zip file - can I download a full stock flashable zip try that?
I'm starting to think this may actually be a hardware issue!
Cheers!
Adam
So I sent the phone off to be repaired under warranty.
They had it nearly 2 weeks then told me they were waiting on parts (a new mainboard) to fix it.
Now they have told me they can't get the parts to fix it, so are sending out a new phone!
Sent from my SM-N910F using Tapatalk