Related
Hello
I have lg g3 d855 32gb,rooted i wanted to flash new lolipop androidnow 3.2,but when i wanted to do a wipe i accidentally mark internal storage.So all the restore and boot.img laf.img...is gone.So i cannot restore back to previous rom.When i wanted to go to download mode it goes to fastboot mode but the computer dont detect telephone(in fastboot).I can go to twrp recovery mode but if i flash the room there is lg error logo,but i can flash lolipop 5 but there is no button and notifications and any stuff.Can i flash firmware somehow true trwp?
Is it possible to fix download mode or if some one send me flash boot.img laf.img or restore i can upload it to sd card.Will restore from someone else working to my phone?
So can someone help me please,sorry for my english...
Kind regards
Mitja
MicFic said:
Hello
I have lg g3 d855 32gb,rooted i wanted to flash new lolipop androidnow 3.2,but when i wanted to do a wipe i accidentally mark internal storage.So all the restore and boot.img laf.img...is gone.So i cannot restore back to previous rom.When i wanted to go to download mode it goes to fastboot mode but the computer dont detect telephone(in fastboot).I can go to twrp recovery mode but if i flash the room there is lg error logo,but i can flash lolipop 5 but there is no button and notifications and any stuff.Can i flash firmware somehow true trwp?
Is it possible to fix download mode or if some one send me flash boot.img laf.img or restore i can upload it to sd card.Will restore from someone else working to my phone?
So can someone help me please,sorry for my english...
Kind regards
Mitja
Click to expand...
Click to collapse
i have the some problem please help me !
AviLgG3 said:
i have the some problem please help me !
Click to expand...
Click to collapse
Probably you are not going to like what I have to suggest because it's a little longer process. My suggestion would be to download the LG Support Tool from http://www.mylgphones.com/lg-software-tools-download
Download LG drivers as well from the same link. Connect your phone to PC. Let the support tool download and install the stock firmware. Then root the device and install twrp recovery. Then proceed with wiping and installing 20A. Yes, it's a longer way but the proper way in your situation. It should not take you more than 30 minutes to be back in the business. Good Luck!
Didn t work
tnx but i allready try it,i try lg flash tool lg flashtool 2014,problem is i cannot go to download mode and the computer dont recognize pc.Only if i go to lolipop 5 but there is no buttons,notifications and i cant to nothing,cant copy to telephone.Becouse the files are missing who i delete it accidentally
I can go to recovery twrp 2.8.0.0 and flash from there.
Adb mode
So i can acces to adb mode from computer.Is there any way to install stock firmware true adb mode or i have to go to download mode?
MicFic said:
So i can acces to adb mode from computer.Is there any way to install stock firmware true adb mode or i have to go to download mode?
Click to expand...
Click to collapse
Don't know about stock firmware but you will be able to download a custom rom and then adb sideload it from recovery. Least you will have your phone up and running while you sort the rest out.
MicFic said:
tnx but i allready try it,i try lg flash tool lg flashtool 2014,problem is i cannot go to download mode and the computer dont recognize pc.Only if i go to lolipop 5 but there is no buttons,notifications and i cant to nothing,cant copy to telephone.Becouse the files are missing who i delete it accidentally
I can go to recovery twrp 2.8.0.0 and flash from there.
Click to expand...
Click to collapse
Flashtool is different than support tool... But in your situation it probably wouldnt work anyway.. So are you stuck in fastboot? If so youll need to flash the boot.img and laf.img for your device. If you can get into recovery just flash a compatible rom. You might need to still flash a boot.img first though if it was erased. I don't think a lot of roms have a boot.img included unless it's bumped not sure about that, I have d851.
Display problem
Swizzle82 said:
Flashtool is different than support tool... But in your situation it probably wouldnt work anyway.. So are you stuck in fastboot? If so youll need to flash the boot.img and laf.img for your device. If you can get into recovery just flash a compatible rom. You might need to still flash a boot.img first though if it was erased. I don't think a lot of roms have a boot.img included unless it's bumped not sure about that, I have d851.
Click to expand...
Click to collapse
No i allready flash lolipop 5 and works great.So i wanted to solve problem with download mode.So i find this link http://forum.xda-developers.com/showthread.php?t=2766437 and flash aboot.img,boot.img,and laf.img.
i type: fastboot flash ____ ____.img
Then i restart i have to flash the new rom becouse was deleted.And there is the big problem.There is something wrong with display after flash.
Here is the link for pictures of my phone: http://shrani.si/f/2p/vw/4IPcVwnK/2/dsc0050.jpg and http://shrani.si/f/5/YC/3NWvutnm/1/dsc0052.jpg
First i thought i burned the display but i think its software error.So i need to restore download mode so i can go back to stock and see if the display wiil fix it,i hope...So i need a little help,do i have to flash some other files on that link,it is for d855 version.
MicFic said:
No i allready flash lolipop 5 and works great.So i wanted to solve problem with download mode.So i find this link http://forum.xda-developers.com/showthread.php?t=2766437 and flash aboot.img,boot.img,and laf.img.
i type: fastboot flash ____ ____.img
Then i restart i have to flash the new rom becouse was deleted.And there is the big problem.There is something wrong with display after flash.
Here is the link for pictures of my phone: http://shrani.si/f/2p/vw/4IPcVwnK/2/dsc0050.jpg and http://shrani.si/f/5/YC/3NWvutnm/1/dsc0052.jpg
First i thought i burned the display but i think its software error.So i need to restore download mode so i can go back to stock and see if the display wiil fix it,i hope...So i need a little help,do i have to flash some other files on that link,it is for d855 version.
Click to expand...
Click to collapse
To restore download mode you need to flash the laf.img. So what I would do is type fastboot erase laf. Then with the new laf.img file you got from your link placed in the proper location, type fastboot flash laf laf.img. Once download mode is back you can kdz flash and return to stock. You might follow the same procedure with the boot.img just be safe but this should be all you need to get back to stock.
...
Swizzle82 said:
To restore download mode you need to flash the laf.img. So what I would do is type fastboot erase laf. Then with the new laf.img file you got from your link placed in the proper location, type fastboot flash laf laf.img. Once download mode is back you can kdz flash and return to stock. You might follow the same procedure with the boot.img just be safe but this should be all you need to get back to stock.
Click to expand...
Click to collapse
Ok i try it but it s the same.i dont know if i do right i copy aboot laf and boot.img to adb folder.Then I do like you told me all 3 files erase and flash it back but it s the same just fastboot(only these 3 files i flash it from that link).Or i have to copy them to sd on telephone ?(maybe i am doing something wrong)
What do you think about the screen is it software issue ?Maybe something is mixing together some files maybe...
I did the same thing.....
I took my sd card out and placed aospa rom on it and then flashed it in twrp...then when i have access to the phone again i reinstalled my favoured (cloudy) rom...For some reason i couldnt flash any rom via SD other that the AOSPA one
simples
[/COLOR]
MicFic said:
Ok i try it but it s the same.i dont know if i do right i copy aboot laf and boot.img to adb folder.Then I do like you told me all 3 files erase and flash it back but it s the same just fastboot(only these 3 files i flash it from that link).Or i have to copy them to sd on telephone ?(maybe i am doing something wrong)
What do you think about the screen is it software issue ?Maybe something is mixing together some files maybe...
Click to expand...
Click to collapse
Does it say success? You might need to change directory in fastboot commands. If you type adb devices does it pop up information about your phone? If you can still get into twrp do like above. I think cloudy restores the entire system on to your phone. I could be wrong I don't use custom roms. I flashed it once for the hell of it and I think I remember it formatting the system and rewriting it.,.
...
Swizzle82 said:
[/COLOR]
Does it say success? You might need to change directory in fastboot commands. If you type adb devices does it pop up information about your phone? If you can still get into twrp do like above. I think cloudy restores the entire system on to your phone. I could be wrong I don't use custom roms. I flashed it once for the hell of it and I think I remember it formatting the system and rewriting it.,.
Click to expand...
Click to collapse
It says sending laf...okay..writing laf ...ok...finished total time 1,680s if i write adb devices says listed of devices attached.Yes i have twrp and custom rom is workin but the there is something wrong with the screen if you see the picture i linked it.Cloudy i dont have it.The big problem is the screen now becouse it happend when i flashed aboot.img and laf.img happens problems with screen.And now o want download mode to restore it to stock that i see if the screen repair or else i have to change...i dont know what is wrong...
MicFic said:
It says sending laf...okay..writing laf ...ok...finished total time 1,680s if i write adb devices says listed of devices attached.Yes i have twrp and custom rom is workin but the there is something wrong with the screen if you see the picture i linked it.Cloudy i dont have it.The big problem is the screen now becouse it happend when i flashed aboot.img and laf.img happens problems with screen.And now o want download mode to restore it to stock that i see if the screen repair or else i have to change...i dont know what is wrong...
Click to expand...
Click to collapse
Ok so then try installing cloudy g3. Then hook it up to the Lg support tool(not flashtool or flashtool 2014 or whatever it is) and see if it recognizes your phone. If it does under options select upgrade recovery and let it do its things.
...
Swizzle82 said:
Ok so then try installing cloudy g3. Then hook it up to the Lg support tool(not flashtool or flashtool 2014 or whatever it is) and see if it recognizes your phone. If it does under options select upgrade recovery and let it do its things.
Click to expand...
Click to collapse
It didnt work.It recognize the telepone then download software but when it is installing it stuck at 2 %...I tried to restore download mode but i think i don t have the right files.Becouse i erased and flashed again recovery,aboot,laf and boot.img.After that i don t have hard reset and nothing i can go to twrp recovery true adb command and install custom room that s it.
So anyone have lg g3 d855 international and send me this files and i can try again if it works.
...
It didnt work.It recognize the telepone then download software but when it is installing it stuck at 2 %...I tried to restore download mode but i think i don t have the right files.Becouse i erased and flashed again recovery,aboot,laf and boot.img.After that i don t have hard reset and nothing i can go to twrp recovery true adb command and install custom room that s it.
So anyone have lg g3 d855 international and send me this files and i can try again if it works.
Problem solved.
Thx all for your help
Hi. I have a weird issue. I have a D855 phone which is running on kitkat v10n. I thought of Upgrading it to official 5.0 or 6.0 firmware and decided to check for the option software update in my phone. But I didn't find any. So i thought of installing TWRP recovery to my phone. and I flashed through flashify and cant boot into recovery menu but i can see fastboot menu started and some other 2,3 lines at the top left corner of the phone. I cant even reset the phone also as doing that going into same fastboot menu but when i pull the battery and place it it is booting.
The real thing starts from here. I want to check whats wrong with my phone and found that actually my phone motherboard is LS990.Not D855. So I came to know that as i wrong flashed the recovery, I am getting fastboot mode. So can I flash tot file directly now or not? if doing so will it result in hard/soft brick or in boot loop? Please help me to upgrade from kitkat to lollipop without any damage to my phone. Expecting a resolution from you. Thank u..
Can you still boot into download mode or not?
You did not see the upgrade because either your sd card is full or too small for update to fit. Happened to me once. When you sort this up, make some room on your sd card and then let the OTA do the thing.
itsbighead said:
Can you still boot into download mode or not?
Click to expand...
Click to collapse
Yes. I can boot into download mode..My phone i think is running on kitkat rom v10n. Its motherboard is ls990 but in software info its showing D855. I only cant reset the phone, cant go into recovery and cant update through OTA and also through Flash tool. How to get recovery menu (custom or even stock recovery) and i want to get rid of fastboot menu.
krishna13 said:
Yes. I can boot into download mode..My phone i think is running on kitkat rom v10n. Its motherboard is ls990 but in software info its showing D855. I only cant reset the phone, cant go into recovery and cant update through OTA and also through Flash tool. How to get recovery menu (custom or even stock recovery) and i want to get rid of fastboot menu.
Click to expand...
Click to collapse
Ops , your phone ls990 and flashing d855 software ?
fOxunO said:
Ops , your phone ls990 and flashing d855 software ?
Click to expand...
Click to collapse
yes.by seeing the software info i did.can u help me in this??
krishna13 said:
yes.by seeing the software info i did.can u help me in this??
Click to expand...
Click to collapse
If you can boot into download, it would be possible to flash kdz. Just you must find the right one for your phone!!
Edit: you will have to use LG flash tool. LGUP is only for D855.
Post here before you do anything.
Navuhodonosor said:
If you can boot into download, it would be possible to flash kdz. Just you must find the right one for your phone!!
Edit: you will have to use LG flash tool. LGUP is only for D855.
Post here before you do anything.
Click to expand...
Click to collapse
no.for ls990 there is no kdz i think so.only tot and dll files.but i am doubtful in flashing anything before fixing the fastboot menu as i could brick my device if anything wrong happens..
Ufff.
This is the hard way but at least first you check your memory for errors, and somewhere in the text it clearly says that fastboot is a no-go.
http://open-freax.fr/guide-unbrick-your-lg-g3/
I personally would go with a download mode and tot files, AND DISBLED ALL THE THINGS THAT WANT TO KILL PROCESSES. like antiviruses, win-defender etc.
Trust me, I know how you feel, maybe some more ideas drop into the thread.
krishna13 said:
Hi. I have a weird issue. I have a D855 phone which is running on kitkat v10n. I thought of Upgrading it to official 5.0 or 6.0 firmware and decided to check for the option software update in my phone. But I didn't find any. So i thought of installing TWRP recovery to my phone. and I flashed through flashify and cant boot into recovery menu but i can see fastboot menu started and some other 2,3 lines at the top left corner of the phone. I cant even reset the phone also as doing that going into same fastboot menu but when i pull the battery and place it it is booting.
The real thing starts from here. I want to check whats wrong with my phone and found that actually my phone motherboard is LS990.Not D855. So I came to know that as i wrong flashed the recovery, I am getting fastboot mode. So can I flash tot file directly now or not? if doing so will it result in hard/soft brick or in boot loop? Please help me to upgrade from kitkat to lollipop without any damage to my phone. Expecting a resolution from you. Thank u..
Click to expand...
Click to collapse
krishna13 said:
no.for ls990 there is no kdz i think so.only tot and dll files.but i am doubtful in flashing anything before fixing the fastboot menu as i could brick my device if anything wrong happens..
Click to expand...
Click to collapse
So lets explain few things first. You can safely flash tot files via download mode. Tot file contains your stock recovery partition as well. So everything will be flashed to stock. So if you find tot file to flash for your model fell free to flash it.
Instead what I would suggest is for you to flash TWRP, and after that flashing Lollipop zip with TWRP.
Here is how:
You download TWRP zip for LS990 from here if you are sure that's your model:
https://www.androidfilehost.com/?fid=24052804347763136
then you extract recovery.img file from the zip,
then to flash it either use flashify or these adb commands:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Ofc if you use these exact adb commands you need to place recovery.img to root of your /sdcard.
So now you confirm that you have a working TWRP. Try to boot into it.
If it succeeds you have Sprint Lollipop files provided here:
http://downloads.codefi.re/autoprime/LG/LG_G3/LS990/stock_partitions/ZVA
You only need these files: system.img, boot.img, modem.img, rpm.img, tz.img
IMPORTANT: boot.img you download from here not from the link above:
http://forum.xda-developers.com/attachment.php?attachmentid=3165683&d=1423941988
After downloading them and placing them in root of sdcard, boot to TWRP open terminal and write these:
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/zv8_boot_fixed.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
dd if=/sdcard/rpm.img of=/dev/block/platform/msm_sdcc.1/by-name/rpm
dd if=/sdcard/tz.img of=/dev/block/platform/msm_sdcc.1/by-name/tz
That's it.
Credit for these files goes to the OP of this thread @autoprime
http://forum.xda-developers.com/spr...stock-sprint-lg-g3-ls990-zva-tot-ota-t3142061
Navuhodonosor said:
Ufff.
This is the hard way but at least first you check your memory for errors, and somewhere in the text it clearly says that fastboot is a no-go.
http://open-freax.fr/guide-unbrick-your-lg-g3/
I personally would go with a download mode and tot files, AND DISBLED ALL THE THINGS THAT WANT TO KILL PROCESSES. like antiviruses, win-defender etc.
Trust me, I know how you feel, maybe some more ideas drop into the thread.
Click to expand...
Click to collapse
thanks for the suggestion friend
NatusVincere said:
So lets explain few things first. You can safely flash tot files via download mode. Tot file contains your stock recovery partition as well. So everything will be flashed to stock. So if you find tot file to flash for your model fell free to flash it.
Instead what I would suggest is for you to flash TWRP, and after that flashing Lollipop zip with TWRP.
Here is how:
You download TWRP zip for LS990 from here if you are sure that's your model:
https://www.androidfilehost.com/?fid=24052804347763136
then you extract recovery.img file from the zip,
then to flash it either use flashify or these adb commands:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Ofc if you use these exact adb commands you need to place recovery.img to root of your /sdcard.
So now you confirm that you have a working TWRP. Try to boot into it.
If it succeeds you have Sprint Lollipop files provided here:
http://downloads.codefi.re/autoprime/LG/LG_G3/LS990/stock_partitions/ZVA
You only need these files: system.img, boot.img, modem.img, rpm.img, tz.img
IMPORTANT: boot.img you download from here not from the link above:
http://forum.xda-developers.com/attachment.php?attachmentid=3165683&d=1423941988
After downloading them and placing them in root of sdcard, boot to TWRP open terminal and write these:
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/zv8_boot_fixed.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
dd if=/sdcard/rpm.img of=/dev/block/platform/msm_sdcc.1/by-name/rpm
dd if=/sdcard/tz.img of=/dev/block/platform/msm_sdcc.1/by-name/tz
That's it.
Credit for these files goes to the OP of this thread @autoprime
http://forum.xda-developers.com/spr...stock-sprint-lg-g3-ls990-zva-tot-ota-t3142061
Click to expand...
Click to collapse
Hi thanks a lot. I already knew that reflashing the LS990 TWRP works but waiting for the confirmation. Anyhow thanks a lot for ur help. Now Instead of fastboot menu I can go to TWRP recovery menu.Now I need to flash either lollipop stock rom or marshmallow stock rom( if available for my sprint version). But presently lollipop is ok. I cant find the system.img. can you please provide me a link of the lollipop flash files please??
krishna13 said:
Hi thanks a lot. I already knew that reflashing the LS990 TWRP works but waiting for the confirmation. Anyhow thanks a lot for ur help. Now Instead of fastboot menu I can go to TWRP recovery menu.Now I need to flash either lollipop stock rom or marshmallow stock rom( if available for my sprint version). But presently lollipop is ok. I cant find the system.img. can you please provide me a link of the lollipop flash files please??
Click to expand...
Click to collapse
I assumed that system.img was provided in links above. It isn't.
So here:
http://downloads.codefi.re/autoprime/LG/LG_G3/LS990/stock_partitions/ZVB/
Download zips only. Flash them, no need to use dd command. It is prerooted Lollipop. Again credits to @autoprime.
And perhaps if you would like to check Marsmallow here's a thread:
http://forum.xda-developers.com/lg-g3/development/rom-lge-d855-android-marshmallow-ported-t3285025
NatusVincere said:
I assumed that system.img was provided in links above. It isn't.
So here:
http://downloads.codefi.re/autoprime/LG/LG_G3/LS990/stock_partitions/ZVB/
Download zips only. Flash them, no need to use dd command. It is prerooted Lollipop. Again credits to @autoprime.
And perhaps if you would like to check Marsmallow here's a thread:
http://forum.xda-developers.com/lg-g3/development/rom-lge-d855-android-marshmallow-ported-t3285025
Click to expand...
Click to collapse
Thanks a lot. I checked the marshmallow post. i found that it has some issues. Am i right?? Data is no working and some call issues also. Is there any other Marshmallow stock feel rom??
so as you said to flash, flashing system.zip and modem .zip is enough?? What about boot.img,tz.img and rpm.img?
krishna13 said:
Thanks a lot. I checked the marshmallow post. i found that it has some issues. Am i right?? Data is no working and some call issues also. Is there any other Marshmallow stock feel rom??
so as you said to flash, flashing system.zip and modem .zip is enough?? What about boot.img,tz.img and rpm.img?
Click to expand...
Click to collapse
I would wait for MM to settle a bit, some guys have icons problem, some LTE, some stuff is downgraded to work properly. How ever you go, you will not get clean MM. Only if you do not want root, and that is a no-no for me.
krishna13 said:
Thanks a lot. I checked the marshmallow post. i found that it has some issues. Am i right?? Data is no working and some call issues also. Is there any other Marshmallow stock feel rom??
so as you said to flash, flashing system.zip and modem .zip is enough?? What about boot.img,tz.img and rpm.img?
Click to expand...
Click to collapse
You checked Marsmallow post, that's how it is. I have d855 so I have official Marsmallow, cant tell you about that port. You can always test it if you wish then revert back.
Yes flash zips only. All those partitions are provided in them (LG-LS990ZVB-Flashable.Modem.RPM.TZ.zip; LG-LS990ZVB-Flashable.System.Boot.zip).
NatusVincere said:
You checked Marsmallow post, that's how it is. I have d855 so I have official Marsmallow, cant tell you about that port. You can always test it if you wish then revert back.
Yes flash zips only. All those partitions are provided in them (LG-LS990ZVB-Flashable.Modem.RPM.TZ.zip; LG-LS990ZVB-Flashable.System.Boot.zip).
Click to expand...
Click to collapse
I flashed it but after booting android process is force closing for every 5 seconds and its showing the same message. So I went into recovery menu, wiped dalvik cache and cache,data and system and made a factory reset again and rebooted it. But my phone stuck on LG logo only. Now i can't even enter into TWRP Recovery . What to do?? Flashing tot is only the solution? I can go into download mode..
Edit: I tried going to TWRP manually. First I tried by going to recovery mode by watching a video showing holding volume down+power button and release after the LG logo is seen and within half second again should hold back. That didn't work for me. I only holded volume down+power button untill I see "Recovery mode loading" screen and after 2 seconds it taken me to TWRP. I successfully re-flashed back the zip files again. Thanks for your help. but i am getting invalid sim and showing hands free activation on my phone.. So should I need to unlock it?? now big trouble with the sim problem.Can u provide any solution??
Edit 2: Even this I solved myself.. thanks a lot.Hitting thanks button
NatusVincere said:
You checked Marsmallow post, that's how it is. I have d855 so I have official Marsmallow, cant tell you about that port. You can always test it if you wish then revert back.
Yes flash zips only. All those partitions are provided in them (LG-LS990ZVB-Flashable.Modem.RPM.TZ.zip; LG-LS990ZVB-Flashable.System.Boot.zip).
Click to expand...
Click to collapse
I cant find APN settings. So cant able to access data. Any help again??
krishna13 said:
I flashed it but after booting android process is force closing for every 5 seconds and its showing the same message. So I went into recovery menu, wiped dalvik cache and cache,data and system and made a factory reset again and rebooted it. But my phone stuck on LG logo only. Now i can't even enter into TWRP Recovery . What to do?? Flashing tot is only the solution? I can go into download mode..
Edit: I tried going to TWRP manually. First I tried by going to recovery mode by watching a video showing holding volume down+power button and release after the LG logo is seen and within half second again should hold back. That didn't work for me. I only holded volume down+power button untill I see "Recovery mode loading" screen and after 2 seconds it taken me to TWRP. I successfully re-flashed back the zip files again. Thanks for your help. but i am getting invalid sim and showing hands free activation on my phone.. So should I need to unlock it?? now big trouble with the sim problem.Can u provide any solution??
Edit 2: Even this I solved myself.. thanks a lot.Hitting thanks button
Click to expand...
Click to collapse
krishna13 said:
I cant find APN settings. So cant able to access data. Any help again??
Click to expand...
Click to collapse
Troublesome. I have no knowledge what "hands free activation" is. I belive it's something connected with Sprint?
As for the invalid SIM, was your phone SIM locked? Where did you buy it and why did it even have d855 system flashed onto it if its ls990?
Can you make calls and have you made a backup of your old system in TWRP before flashing?
NatusVincere said:
Troublesome. I have no knowledge what "hands free activation" is. I belive it's something connected with Sprint?
As for the invalid SIM, was your phone SIM locked? Where did you buy it and why did it even have d855 system flashed onto it if its ls990?
Can you make calls and have you made a backup of your old system in TWRP before flashing?
Click to expand...
Click to collapse
I followed one link and replaced some files and got the signal back. But I am unable to access data in my phone. also in settings i am seeing activate this device. I disabled hands free activation thing which is very annoying. But flashing any other lollipop rom, can I use data in my phone? Can you suggest any best lollipop rom like cloudy or other than cloudy?
Hi guys I got bootloop in my moto g5. First I got "failed to mount /data", now the phone boots in unlocked warning screen then says "erasing" then reboots and start over again.
Before the procedure my actions was:
- I got OTA update
- inserted a microSD
- unlocked bootloader
- boot on TWRP 3.1.0
- backup to microSD
-install TWRP
as shown by bootloader screen, my model is "cedric XT1672 32GB P5", M8937_8000.122.02.45R CEDRIC_BRAZILDSDS_CUST.
What I don't understand is why TWRP don't restore, as a made a backup before the procedure.
I appreciate if somebody could help me out!
I had the same problem. Wiping /data corrupted my partition table or system partition.
You need to flash the system and / or the partition table via fastboot from the extracted stock rom (see the other thread arround here, make sure you use the right link (cedric, not the potter one)
-> boot to fastboot
fastboot flash system system.sparsechunk.0
fastboot flash system system.sparsechunk.1
...
It should boot normally afterwards, but probably twrp is gone / twrp has no access to your /data again. See the twrp thread, i'm facing the same issue. But at least the phone works again - without root
Greetings,
Chris
-> boot to fastboot
fastboot flash system system.sparsechunk.0
fastboot flash system system.sparsechunk.1
Click to expand...
Click to collapse
Did not work for me!
I hope you flashed all the system files?
Otherwise try to flash the full stock rom via fastboot. There are tons of guides explaining
Help NPP25.137-33 It doesn't work filefactory
.sirhc said:
I hope you flashed all the system files?
Otherwise try to flash the full stock rom via fastboot. There are tons of guides explaining
Click to expand...
Click to collapse
Help with stock NPP25.137-33 someone who has it in google driver to download
Got it back I, like you said! The first time I think I got any of those system file corrupted!!
I just dont know until when it gonna be good cos I am going to root this s.. now!
thks
linsspinho said:
Got it back I, like you said! The first time I think I got any of those system file corrupted!!
I just dont know until when it gonna be good cos I am going to root this s.. now!
thks
Click to expand...
Click to collapse
// already found how to root. won't do it right now as there are no success stories
•••••• Qualcomm Moto E (4th Gen) Perry ••••••
Factory Firmware & Flashing/Restoration Guide
MetroPCS / T-Mobile Moto E4 (XT1765)
OVERVIEW:
This guide provides factory firmware for both the MetroPCS and T-Mobile branded variants of the Moto E4 Perry (xt1765). While these two packages appear to be similar and multi-compatible, I do not own the xt1765 and cannot confirm this. So, to be safe, use only the firmware package for your branded carrier. This guide can be used to repair a device which is buggy, unstable, or stuck in a boot loop. Likewise, device owners wishing to restore their device to an unmodified, stock factory state will also find this guide beneficial. Installing this firmware will remove any custom mods from your device, such as root binaries, BusyBox binaries, Xposed framework, etc. Also, force encryption and verified boot (dm-verity/avb) will be enabled. If you have TWRP custom recovery installed, it will be replaced by the stock recovery image.
DISCLAIMER:
You are using this guide and flashing firmware to your device solely at your own risk. While these firmwares have been tested and confirmed to work on their respective variants, by proceeding further, you are absolving me of any liability or responsibility in the event you brick your device or otherwise render it inoperable. Follow the simple instructions carefully and things should go smoothly.
SPECIFICATIONS:
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•MetroPCS Moto E4 (xt1765) Perry
•Android Version: 7.1.1 Nougat
•Build No. NCQS26.69-64-3
•System Version: 26.261.9.perry_metropcs.en.US
•Radio Version: M8917TMO_18.08.04.18R
•Security Patch Level: March 1, 2018
•Kernel Version: Linux 3.18.31-perf
•Build Date: March 16, 2018
•Firmware Package Size: 1.36 GB
•Download Link: https://drive.google.com/file/d/17sJS8VpxSAHupqiqJQQb4wa1jHIP61uT/view?usp=drivesdk
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•T-Mobile Moto E4 (xt1765) Perry
•Android Version: 7.1.1 Nougat
•Build No. NCQS26.69-64-6
•System Version: 26.271.7.perry_tmo.tmo.en.US
•Radio Version: M8917TMO_18.08.04.18.01R
•Security Patch Level: May 1, 2018
•Kernel Version: Linux 3.18.31-perf
•Build Date: May 2, 2018
•Firmware Package Size: 1.33 GB
•Download Link: https://drive.google.com/file/d/1C21fgdBVn6hhPtAo5yult-PdB6DSr4HS/view?usp=drivesdk
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
REQUIREMENTS:
This guide assumes that you have the latest version of the Minimal ADB & Fastboot utilities installed on your PC or laptop. If you do not, you can download the latest version, v1.4.3, from this MediaFire link: http://www.mediafire.com/file/ccnnv843a20tqbn/minimal_adb_fastboot_v1.4.3.zip It is also a good idea to have at least a rudimentary understanding of fastboot command line execution. There are some excellent guides here on XDA which outline the subjects of fastboot mode & fastboot commands.
In addition, to ensure that up-to-date USB device drivers are installed on your PC, download & install the latest Motorola Device Manager. You can get the latest version directly from this Motorola support link: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
NOTE:
Because these are factory firmware packages, in theory, xt1765 owners should be able to flash these packages, using the below instructions, to devices with a locked bootloader. Please note, however, that these firmwares were leaked by the manufacturer and may or may not be digitally signed by the OEM. In sum, I cannot confirm whether these firmwares will flash to a locked bootloader device. I can only confirm that the firmware will install normally on a device with an unlocked bootloader. As confirmation becomes available from other members in this regard, I will add the info to this thread.
On a second note, flashing this factory firmware does not re-lock an already unlocked bootloader. Also, contrary to popular misbelief, re-locking your bootloader IS NOT required in order for your device to be able to install OTA update packages. To enable your device to install OTA updates, you need only install the firmware package for your variant using the below instructions.
WARNING: The below instructions include a command for wiping your /userdata partition (fastboot erase userdata) which will effectively wipe all of your saved files, photos, videos, app data and other media. This is recommended for a clean install of the firmware, and to ensure optimal results. However, if you are stuck in a boot loop, for example, and have important files saved to internal storage that you want to try and salvage, simply skip over the "fastboot erase userdata" command and give it a try.
INSTRUCTIONS:
• 1. Download the firmware package for your branded carrier on your PC or laptop. Extract the contents of the package to your ADB/Fastboot directory;
• 2. Boot your device into fastboot mode and connect your device to your PC with the OEM or a quality equivalent micro USB to USB sync cable;
• 3. Open a command window in the path of your ADB/Fastboot directory and execute:
fastboot devices
If your device and PC are properly connected, the command window will return an alphanumeric value synonymous of your device serial number;
• 4. Once a proper connection has been established, execute the following commands, preferably in this order:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
Done. Now execute:
fastboot reboot
Upon reboot, your device should be restored to unmodified stock condition, and your device will be capable of installing pending or future OTA update packages.
Thanks for posting this! Looks very comprehensive and nOObproof.... I'm going to try this out in the next few days and I will report back if I had any trouble following the instructions and let your know if I feel anything needs to be clarified. I don't foresee having any problems with this though. I appreciate you and your hard work to put this together
AesopRock127 said:
Thanks for posting this! Looks very comprehensive and nOObproof.... I'm going to try this out in the next few days and I will report back if I had any trouble following the instructions and let your know if I feel anything needs to be clarified. I don't foresee having any problems with this though. I appreciate you and your hard work to put this together
Click to expand...
Click to collapse
No problem. I've been reading a lot of posts of members needing more up-to-date xt1765 stock firmware, so I hope it helps some members. These are the same instructions and structural format that I use on all of my Moto/Lenovo firmware threads. The order of the command lines are set out exactly the same as those used in certified Motorola/Lenovo service centers. If you follow the instructions to the letter, there is no doubt that you'll have your device fully restored to stock factory condition.
When I have the time to do so, I'll use these firmwares with my Android Kitchen to cook up TWRP flashable stock ROMs for the MetroPCS & T-Mobile xt1765 models.
MotoJunkie01 said:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
My question is if i want to keep twrp as my recovery is it as simple as not running the command fastboot flash recovery recovery.img?
AesopRock127 said:
My question is if i want to keep twrp as my recovery is it as simple as not running the command fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Yes. It is that simple. Just be advised that an OTA will not install normally unless stock recovery is in place. The OTA installation script runs checksums for stock recovery.
The best policy is to flash the firmware in full, install any pending OTAs while running unmodified stock, then reinstall TWRP once you're up to date on the latest firmware build.
MotoJunkie01 said:
Yes. It is that simple. Just be advised that an OTA will not install normally unless stock recovery is in place. The OTA installation script runs checksums for stock recovery.
The best policy is to flash the firmware in full, install any pending OTAs while running unmodified stock, then reinstall TWRP once you're up to date on the latest firmware build.
Click to expand...
Click to collapse
Shiiiiiit I didn't think about that I have an update I'm going to try to do it if it doesn't work guess I'll redo the full process all over again..... By the way I pmd you
EDIT: 69-64-6 updated no problem And immediately offered me 69-64-9 so maybe these updates aren't large enough to worry about twrp instead of stock recovery? Only time will tell I guess
Sent from my Motorola XT1765 using XDA Labs
AesopRock127 said:
Shiiiiiit I didn't think about that I have an update I'm going to try to do it if it doesn't work guess I'll redo the full process all over again..... By the way I pmd you
EDIT: 69-64-6 updated no problem And immediately offered me 69-64-9 so maybe these updates aren't large enough to worry about twrp instead of stock recovery? Only time will tell I guess
Click to expand...
Click to collapse
To simplify things, just keep installing OTAs until you are on the current build. Then, reinstall TWRP. You shouldn't have to redo the whole thing as long as you haven't mounted system as r/w in TWRP. And as long as you haven't flashed Magisk or SuperSU for root. Just reboot into fastboot and flash the stock recovery and OTAs should be fine.
so i know im a pain in the ass but i followed this guide with no issues and updated fully before installing twrp and root and then couldnt install xposed and ran into a bootloop so decided to go nuclear and start over. My only issue now is after fully following this guide again my OTA updates are failing in stock recovery and when i reboot i get tons of tmobile and moto app FC issues and it says im fully updated even though i started on 69-64-3 and it failed in stock recovery it still says im on 69-64-6 and ive been on 69-64-9 before so not only do i know im not fully updatedd but these FC are driving me nuts. Trying again but does anyone have any clues what could be causing my issues? im having a lot of problems with noverity flashing right and getting the newest twrp to flash instead of only temp boot as well and i feel these issues are all cnnected somehow. I might go back to RR if possible because i was able to get my phone the way i wanted on there for the most part im not sure why stock is giving me such issues? Unfrotunately i cant provide any logs or anything because i am retrying this guide again and see how it goes and didnt think until after the fact to post this
AesopRock127 said:
so i know im a pain in the ass but i followed this guide with no issues and updated fully before installing twrp and root and then couldnt install xposed and ran into a bootloop so decided to go nuclear and start over. My only issue now is after fully following this guide again my OTA updates are failing in stock recovery and when i reboot i get tons of tmobile and moto app FC issues and it says im fully updated even though i started on 69-64-3 and it failed in stock recovery it still says im on 69-64-6 and ive been on 69-64-9 before so not only do i know im not fully updatedd but these FC are driving me nuts. Trying again but does anyone have any clues what could be causing my issues? im having a lot of problems with noverity flashing right and getting the newest twrp to flash instead of only temp boot as well and i feel these issues are all cnnected somehow. I might go back to RR if possible because i was able to get my phone the way i wanted on there for the most part im not sure why stock is giving me such issues? Unfrotunately i cant provide any logs or anything because i am retrying this guide again and see how it goes and didnt think until after the fact to post this
Click to expand...
Click to collapse
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
MotoJunkie01 said:
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
Click to expand...
Click to collapse
Ok thanks. I will try redownloading if it persists but is there any log or anything that would help out in identifying the problem if it still persists after a redownloading of the firmware? It's annoying that stock recovery says error! With no code to help identify the issue
AesopRock127 said:
Ok thanks. I will try redownloading if it persists but is there any log or anything that would help out in identifying the problem if it still persists after a redownloading of the firmware? It's annoying that stock recovery says error! With no code to help identify the issue
Click to expand...
Click to collapse
When stock recovery says ERROR during installation of an OTA, the problem is with the checksums. In other words, the OTA installer is telling stock recovery that you are not running an unmodified stock setup. You can get an error like that from just mounting /system or /oem as r/w. The installer checks your /boot, /recovery, /system and /oem partitions to make sure they are untouched, unmodified stock.
Also, @AesopRock127, there is a quicker and simpler method to install stock firmware to a Moto/Lenovo device called RSD Lite. You can Google for the basic instructions.
Here's a link to RSD Lite v6.2.4: https://drive.google.com/file/d/1MwZPdifKVpR4ZTsE3SSNAFBNr6KU29wY/view?usp=drivesdk
MotoJunkie01 said:
Also, @AesopRock127, there is a quicker and simpler method to install stock firmware to a Moto/Lenovo device called RSD Lite. You can Google for the basic instructions.
Here's a link to RSD Lite v6.2.4: https://drive.google.com/file/d/1MwZPdifKVpR4ZTsE3SSNAFBNr6KU29wY/view?usp=drivesdk
Click to expand...
Click to collapse
Okay so I redid this and the updates are sticking like you said I must have changed something and made it non-stock.... So I do not need the RSD Lite as of yet but I did download it. Looking into it it seems that I may use it to root my device when I get to that point? For now I'm just setting everything up the way I like it and fully intalling stock updates before I get into TWRP and rooting. The goal is a up to date stock, rooted, debloated, and running Xposed and gravitybox. Last time everything went smoothly until I hit xposed. I think it's due to my crappy understanding of selinux permissions, encryption and dm verity.... The best thing about struggling to install stuff like this is it gives you an opportunity to learn. In the past I've been able to follow guides and everything worked as stated so I had no need to get technical and delve into some of the things I've needed to on my xt1765. Thank God for XDA and helpful people like @MotoJunkie01 or I would have hit this phone with a Sledge hammer or chop it in half with a chop saw like I did with the Samsung j3 ?
AesopRock127 said:
Okay so I redid this and the updates are sticking like you said I must have changed something and made it non-stock.... So I do not need the RSD Lite as of yet but I did download it. Looking into it it seems that I may use it to root my device when I get to that point? For now I'm just setting everything up the way I like it and fully intalling stock updates before I get into TWRP and rooting. The goal is a up to date stock, rooted, debloated, and running Xposed and gravitybox. Last time everything went smoothly until I hit xposed. I think it's due to my crappy understanding of selinux permissions, encryption and dm verity.... The best thing about struggling to install stuff like this is it gives you an opportunity to learn. In the past I've been able to follow guides and everything worked as stated so I had no need to get technical and delve into some of the things I've needed to on my xt1765. Thank God for XDA and helpful people like @MotoJunkie01 or I would have hit this phone with a Sledge hammer or chop it in half with a chop saw like I did with the Samsung j3 ?
Click to expand...
Click to collapse
That's good news. I intend on making a TWRP flashable stock ROM for the xt1765 in the very near future. Once you are on the latest stock build, if you could make a TWRP backup of your system image and boot image and upload them, I could use the images to cook up an up-to-date stock ROM for the xt1765.
MotoJunkie01 said:
That's good news. I intend on making a TWRP flashable stock ROM for the xt1765 in the very near future. Once you are on the latest stock build, if you could make a TWRP backup of your system image and boot image and upload them, I could use the images to cook up an up-to-date stock ROM for the xt1765.
Click to expand...
Click to collapse
Absolutely. will do this ASAP. Seems best if I do nothing except boot into TWRP and make the backup? Or can I flash it and it will still work? Basically is the stock recovery needed or can I flash TWRP before I make the backup
so system and boot only or system, system image, and boot? making one now with both systems and one with just normal system since im not sure which you need and dont want to give you to much **** to sift through. also does data need to be decrypted for this to be helpful to you? sorry dont know much about it but am willing to help lol
AesopRock127 said:
Absolutely. will do this ASAP. Seems best if I do nothing except boot into TWRP and make the backup? Or can I flash it and it will still work? Basically is the stock recovery needed or can I flash TWRP before I make the backup
so system and boot only or system, system image, and boot? making one now with both systems and one with just normal system since im not sure which you need and dont want to give you to much **** to sift through. also does data need to be decrypted for this to be helpful to you? sorry dont know much about it but am willing to help lol
Click to expand...
Click to collapse
System image and boot backup with TWRP. Encryption of data isn't relevant to the backups. Whether you boot into TWRP or flash TWRP ....either will work
@MotoJunkie01 Nanodroid backup of encrypted fully uptodate stock system and boot.img only https://ufile.io/b0x6q
uploading the one with the system image too
MotoJunkie01 said:
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
Click to expand...
Click to collapse
Also verify checksums (MD5, SHA-1, etc) when offered. Fastest way to validate large file integrity. As a matter of practice I never flash critical partitions sans checksum validation.
Davey126 said:
Also verify checksums (MD5, SHA-1, etc) when offered. Fastest way to validate large file integrity. As a matter of practice I never flash critical partitions sans checksum validation.
Click to expand...
Click to collapse
Excellent point. A corrupt flash to a critical partition can equal lights out -- the proverbial hard brick.
This has happened to me before, I think -- I restarted, and my phone unrooted itself. What's that about, again? How do I stop it?
My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.
ctfrommn said:
My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.
Click to expand...
Click to collapse
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?
DanHakimi said:
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?
Click to expand...
Click to collapse
You can just go flash the patched boot again.
ctfrommn said:
You can just go flash the patched boot again.
Click to expand...
Click to collapse
Welp... I did that, and now my phone is stuck booting, it won't go past the G screen.
I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.
Bob nesta said:
I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.
Click to expand...
Click to collapse
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.
DanHakimi said:
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.
Click to expand...
Click to collapse
I only mentioned flashing a custom kernel since your patched boot.img messed you up so I threw that out there because sometimes it's a way to get out of a boot problem. (I'm not trying to plug other peoples' kernels/work or anything like that.)
But you got things up and running, so...carry on