Related
Hi.
I heard from someone that there is an app that enables a danish Magic to fully access the android market thereby bypassing the region restriction. Is that true?
I´ve done a search. Nothing found.
yes, google for marketenabler
Thanks. Cheers.
You must root your phone for that to work.
maedox said:
You must root your phone for that to work.
Click to expand...
Click to collapse
I´ve just rooted the phone and the enabler tells me that everything is ok. But I still only get the free apps in market..
How do I check to see it my phone really is rooted? Might be that I´ve messed up ?
Did you remember to kill your market process and clear its cache before trying to go in again?
Did it and it works.. thanks..
Tuco Benidicto Pacifico Juan Maria Ramirez?
I've been having problems with this app. My phone IS rooted yet whenever I try to choose a source in the list I get the "we got a problem houston " error message! Can someone please help?
BTW, I'm a Rogers customer.
rickytenzer said:
I've been having problems with this app. My phone IS rooted yet whenever I try to choose a source in the list I get the "we got a problem houston " error message! Can someone please help?
BTW, I'm a Rogers customer.
Click to expand...
Click to collapse
use the new 3.0.1 beta version. works for me when the older one doesnt.
nmesisca said:
use the new 3.0.1 beta version. works for me when the older one doesnt.
Click to expand...
Click to collapse
Could you explain your steps to me? No matter what version I try, I ALWAYS get the "we got a problem Houston " error message. This is what I did:
Downloaded MarketEnabler_v3.0.1-beta.apk
Put it in C:\AndroidSDK\
Opened cmd from run
Went to C:\AndroidSDK\
adb install MarketEnabler_v3.0.1-beta.apk
Completed successfully
Went to applications in my Magic and force stopped Market as well as cleared the cache
Opened Market Enabler and tried the German source
Error message comes up!
Thanks for the help
And yes, my phone IS rooted.
EDIT: Didn't have Superuser installed! It works fine now although ATM it doesn't show any paid apps...
rickytenzer said:
Could you explain your steps to me? No matter what version I try, I ALWAYS get the "we got a problem Houston " error message. This is what I did:
Downloaded MarketEnabler_v3.0.1-beta.apk
Put it in C:\AndroidSDK\
Opened cmd from run
Went to C:\AndroidSDK\
adb install MarketEnabler_v3.0.1-beta.apk
Completed successfully
Went to applications in my Magic and force stopped Market as well as cleared the cache
Opened Market Enabler and tried the German source
Error message comes up!
Thanks for the help
And yes, my phone IS rooted.
EDIT: Didn't have Superuser installed! It works fine now although ATM it doesn't show any paid apps...
Click to expand...
Click to collapse
try clearing the cache again. it definitely works every time for me.
hey guys can u please help me out i need to root my phone but am unable to do so.. I am from india .and i guess have regional restrictions on...I do not have the market ...??:-( i tried to use the instructions on
http://forum.xda-developers.com/showthread.php?p=4335330#post4335330
but i get stuck on point 6, am unable to get the command prompt it.. i get a message saying " this path does not exist "??/ wt am i doing wrong?? have i typed something wrong in step 3?
can anyone please tell me wt to do???
aamodr said:
hey guys can u please help me out i need to root my phone but am unable to do so.. I am from india .and i guess have regional restrictions on...I do not have the market ...??:-( i tried to use the instructions on
http://forum.xda-developers.com/showthread.php?p=4335330#post4335330
but i get stuck on point 6, am unable to get the command prompt it.. i get a message saying " this path does not exist "??/ wt am i doing wrong?? have i typed something wrong in step 3?
can anyone please tell me wt to do???
Click to expand...
Click to collapse
step 3 is enabling debug mode, so i dont know what you could have typed wrong.
point 6 is just to open a command prompt. have you tried with the Command Prompt icon in Windows?
aamodr said:
hey guys can u please help me out i need to root my phone but am unable to do so.. I am from india .and i guess have regional restrictions on...I do not have the market ...??:-( i tried to use the instructions on
http://forum.xda-developers.com/showthread.php?p=4335330#post4335330
but i get stuck on point 6, am unable to get the command prompt it.. i get a message saying " this path does not exist "??/ wt am i doing wrong?? have i typed something wrong in step 3?
can anyone please tell me wt to do???
Click to expand...
Click to collapse
You can try to use the method ekindangen is showing in this thread:
[ROM] Change the perfected SPL HBOOT 1.33.0010 to 1.33.0009
And after that you can choose to use flashrec to get recovery-RAv1.2.1H.img on your device or just use adb fastboot method. And then flash the rom you desire into your mobile.
But before you do so please confirm that you got a 32A with the perfect SPL 1.33.0010 for your own sake You should have, and method worked for me and was really easy!
My phone has no network and it says no sim card. After further investigation it appears that this is because the IMEI number has just gone, it doesnt exist on the phone. It is standard I have never changed software so have no idea how this could happen. Tried factory reset but nothing works. Any ideas greatly appreciated.
Re flash stock firmware and it should come back
Sent from my Nexus 5 using Tapatalk
Flash it to stock.
Root it
Install es explorer or any root explorer
Install hex editor
In es explorer go to efs folder in root
Open nv_data.bin in hex editor
Goto position 00188020 and check. .
Sent from my GT-I9500 using XDA Premium HD app
amit.talukdar said:
Flash it to stock.
Root it
Install es explorer or any root explorer
Install hex editor
In es explorer go to efs folder in root
Open nv_data.bin in hex editor
Goto position 00188020 and check. .
Sent from my GT-I9500 using XDA Premium HD app
Click to expand...
Click to collapse
This is still not a Samsung forum.
Sent from my OmniROM-powered LG Optimus 4X HD
Try to pull dev/block/platform/sdhci-tegra.3/by-name/NVA
Open with text editor.
Check if imei is stored.
This partition is recreated on flashing dz/kdz. I am not sure if IMEI is read from here. If you give email i will send you my NVA partition to compare. Don't post it or people will see your IMEI
Sent from my LG-P880 using xda app-developers app
Hi...I have similar problem ...my LG-P880 dont show the IMEI and factory reset is also not working...as per above I have checked in NVA folder it cotains proper IMEI number...so any idea how to fix the situation...? Thanks in advnace...
jigneshandroid said:
Hi...I have similar problem ...my LG-P880 dont show the IMEI and factory reset is also not working...as per above I have checked in NVA folder it cotains proper IMEI number...so any idea how to fix the situation...? Thanks in advnace...
Click to expand...
Click to collapse
Try Flashing using either by KDZ or LG Flash tool it might help you,
Try below link for procedure of LG Flash Tool
http://forum.xda-developers.com/showthread.php?t=2179126
KDZ Method
http://forum.xda-developers.com/showthread.php?t=2069723
Read the steps and understand it properly,
Hit thanks button below,if this help you out
Good Luck:good:
Salman Al-Badgail said:
Try Flashing using either by KDZ or LG Flash tool it might help you,
Try below link for procedure of LG Flash Tool
http://forum.xda-developers.com/showthread.php?t=2179126
KDZ Method
http://forum.xda-developers.com/showthread.php?t=2069723
Read the steps and understand it properly,
Hit thanks button below,if this help you out
Good Luck:good:
Click to expand...
Click to collapse
Thanks for your guidance...I have tried both option but it get stuck in middle somewhere and not able to flash the kdz file.
So at this moment LG Mobile support tools not able to cross 10% in firmware update process and stops due to some error.
With KDZ update tools, same situation....and device can connect to adb terminal no other recovery mode options.
So using adb terminal is there any chances to do some fix ?
I think I have currupted my boot loader during installation of third party recovery software without doing boot loader unlock option.
Please guide or suggest any other try.....
Thanks
jigneshandroid said:
Thanks for your guidance...I have tried both option but it get stuck in middle somewhere and not able to flash the kdz file.
So at this moment LG Mobile support tools not able to cross 10% in firmware update process and stops due to some error.
With KDZ update tools, same situation....and device can connect to adb terminal no other recovery mode options.
So using adb terminal is there any chances to do some fix ?
I think I have currupted my boot loader during installation of third party recovery software without doing boot loader unlock option.
Please guide or suggest any other try.....
Thanks
Click to expand...
Click to collapse
How you get into this problem?
Give me your BL - status, Secondly try changing PC. Also let me know what ROM you were using before getting into this problem (Stock/Custom)
Thirdy Party softwares (recovery) like....?
If you just give us info, someone might help you properly. I am just a Junior Member here, helping you out the info i had.
[Edited : Sorry for my English, I am Arabic]
Salman Al-Badgail said:
How you get into this problem?
Give me your BL - status, Secondly try changing PC. Also let me know what ROM you were using before getting into this problem (Stock/Custom)
Thirdy Party softwares (recovery) like....?
If you just give us info, someone might help you properly. I am just a Junior Member here, helping you out the info i had.
[Edited : Sorry for my English, I am Arabic]
Click to expand...
Click to collapse
It was happened like......the phone was working ok with latest official updates V20A and suddenly lost the IMEI number so Mobile network also. After some try finally I have done factory reset..but it was not working as expected...some time it has shown IMEI but lost also...tried many time factory reset but not worked...so tried with LG Mobile repair under upgrade and recovery option but it was failing at 10 % everytime. So thought lets intall new ROM so decided to install cyanogonmod so for preparation rooted phone and installed CWM recovery ....as doing all this first time so may be forgot to unlock the bootloader so after installation of CWM recovery phone has not booted and also not going to recovery menu. After that under upgrade mode tried to burn KDZ file using LG mobile support tool but that also not working.
So now the situation is, the can only go in to firmware update mode and some time getting connected to adb terminal.
So now is there any change of BL repair through adb terminal or the only option remain is visit LG support....?
Please guide....
Thanks,
jigneshandroid said:
It was happened like......the phone was working ok with latest official updates V20A and suddenly lost the IMEI number so Mobile network also. After some try finally I have done factory reset..but it was not working as expected...some time it has shown IMEI but lost also...tried many time factory reset but not worked...so tried with LG Mobile repair under upgrade and recovery option but it was failing at 10 % everytime. So thought lets intall new ROM so decided to install cyanogonmod so for preparation rooted phone and installed CWM recovery ....as doing all this first time so may be forgot to unlock the bootloader so after installation of CWM recovery phone has not booted and also not going to recovery menu. After that under upgrade mode tried to burn KDZ file using LG mobile support tool but that also not working.
So now the situation is, the can only go in to firmware update mode and some time getting connected to adb terminal.
So now is there any change of BL repair through adb terminal or the only option remain is visit LG support....?
Please guide....
Thanks,
Click to expand...
Click to collapse
Did you check your BL status for now?
3845#*880#
Salman Al-Badgail said:
Did you check your BL status for now?
3845#*880#
Click to expand...
Click to collapse
At present phone is not booting so not able run any short cut commands....but before crash it was showing status locked...
I will try as per your message ...will update the results...
Thanks
jigneshandroid said:
At present phone is not booting so not able run any short cut commands....but before crash it was showing status locked...
I will try as per your message ...will update the results...
Thanks
Click to expand...
Click to collapse
Great, will be waiting for your answer
Salman Al-Badgail said:
Great, will be waiting for your answer
Click to expand...
Click to collapse
I am trying with the links you have provided to flash the ROM, but before I start it...getting problem to keep the device connected to USB port...in device manager on connection it shows connected under Ports but in few seconds it gets disconnected (like timeout)..so exploring how can I keep it connected so that can try the tools once more.
jigneshandroid said:
I am trying with the links you have provided to flash the ROM, but before I start it...getting problem to keep the device connected to USB port...in device manager on connection it shows connected under Ports but in few seconds it gets disconnected (like timeout)..so exploring how can I keep it connected so that can try the tools once more.
Click to expand...
Click to collapse
Did you downloaded the files??
Install Drivers and follow the steps properly,
this should work for you to keep connected,
One more thing run drivers and flashtool as administrator, I already PM you.
Still having problems, please let me know.
If your phone is still not booting, I am afraid that you bricked it.
Good Luck
Salman Al-Badgail said:
Did you downloaded the files??
Install Drivers and follow the steps properly,
this should work for you to keep connected,
One more thing run drivers and flashtool as administrator, I already PM you.
Still having problems, please let me know.
If your phone is still not booting, I am afraid that you bricked it.
Good Luck
Click to expand...
Click to collapse
I am able connect my device to LGFlashTool on com Port1 but download fails with below log on port1
StartDownload()
Saved result to XML file.
Failure : 207
FAIL
and same thing repeating as software retries the same.
Can somebody guide what is this situation ?
Thanks and best regards,
Jignesh
jigneshandroid said:
I am able connect my device to LGFlashTool on com Port1 but download fails with below log on port1
StartDownload()
Saved result to XML file.
Failure : 207
FAIL
and same thing repeating as software retries the same.
Can somebody guide what is this situation ?
Thanks and best regards,
Jignesh
Click to expand...
Click to collapse
Post a screenshot so that anyone could help you.
jigneshandroid said:
I am able connect my device to LGFlashTool on com Port1 but download fails with below log on port1
StartDownload()
Saved result to XML file.
Failure : 207
FAIL
and same thing repeating as software retries the same.
Can somebody guide what is this situation ?
Thanks and best regards,
Jignesh
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2179126
Try using post #7 by RuedasLocas
and read it untill you get it.
:good:
Salman Al-Badgail said:
http://forum.xda-developers.com/showthread.php?t=2179126
Try using post #7 by RuedasLocas
and read it untill you get it.
:good:
Click to expand...
Click to collapse
OK..thanks I will check this post whether somebody has reported similar problem...do you mean page 7 is it ?
:good:
jigneshandroid said:
OK..thanks I will check this post whether somebody has reported similar problem...do you mean page 7 is it ?
:good:
Click to expand...
Click to collapse
Page 1 -> post #7 by RuedasLocas
Hi All,
So I have been searching the interwebs for the last four hours with no luck.
I have a Nexus 6 and I was trying to update the OTA developer preview from google that I signed up to test.
Problem is that I ended up on a bootloop. I am able to get into Fastboot but I am unable to make any commands work since the device is locked. All commands end with a Failed (command write failed error).
I am able to go into recovery to access ADB but that is also not very useful because it seems i am unable to push anything to the phone. The only thing which seems to want to work is when I try and load an OTA image.
This loads until 100% and I get an error which says the image I have is to new and it requires a specic image.
I am currently on 6.0.1/MMB29V/2554798.
I have tried factory reset but no help there.
Also when I try select update from SD Card it says it Couldnt mount/sdcard.... Unknow volume for path
Any help?
qbzee007 said:
Hi All,
So I have been searching the interwebs for the last four hours with no luck.
I have a Nexus 6 and I was trying to update the OTA developer preview from google that I signed up to test.
Problem is that I ended up on a bootloop. I am able to get into Fastboot but I am unable to make any commands work since the device is locked. All commands end with a Failed (command write failed error).
I am able to go into recovery to access ADB but that is also not very useful because it seems i am unable to push anything to the phone. The only thing which seems to want to work is when I try and load an OTA image.
This loads until 100% and I get an error which says the image I have is to new and it requires a specic image.
I am currently on 6.0.1/MMB29V/2554798.
I have tried factory reset but no help there.
Also when I try select update from SD Card it says it Couldnt mount/sdcard.... Unknow volume for path
Any help?
Click to expand...
Click to collapse
Very difficult. Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=3053783
NLBeev said:
Very difficult. Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=3053783
Click to expand...
Click to collapse
Tried it and it seems I have no other option but to return.
Problem is that i am in South Africa and have no idea how to go about.
Bought off Amazon
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
qbzee007 said:
.....Problem is that i am in South Africa and have no idea how to go about.
Bought off Amazon
Click to expand...
Click to collapse
your n6 is bricked and you could try all the options from XDA.
There is a thread about the Nexus Root Toolkit of Wugfresh. This kit runs on a Windows PC and has a menu with option for bricked phones.
When you can start in recovery mode (long press start button + volume down) you could give it a try. http://forum.xda-developers.com/showthread.php?t=2947452
When there is no result, you could send it to Amazon for repair. But check the costs.
The total costs of mail, assurance and repair are probably more than $ 100,=.
I have seen some posts that the of a new N6 is every month lower.
TriguyRN said:
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Click to expand...
Click to collapse
I was going to suggest this too. The link posted leads to this link that has instructions on installing.
alryder said:
I was going to suggest this too. The link posted leads to this link that has instructions on installing.
Click to expand...
Click to collapse
Thank you very much.
This worked.
Booting as I type this. Best Easter Monday gift.
Thanks Again
Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
Code:
loading: 'C:\Users\dpowell\Downloads\shamu-mob30o.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.
dpowell11 said:
Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.
Click to expand...
Click to collapse
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...
5.1 said:
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...
Click to expand...
Click to collapse
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
Code:
E:footer is wrong
E:signature verification failed
Installation aborted.
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.
dpowell11 said:
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.
Click to expand...
Click to collapse
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...
5.1 said:
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...
Click to expand...
Click to collapse
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
Code:
Installing update...
Target: google/shamu/shamu:7.1.1/N6F26Y/3821691:user/release-keys
Patching system image unconditionally...
E:unknown command [log]
E:unknown command [log]
Writing bootloader...
Writing radio...
script succeeded: result was [1.000000]
Install from ADB complete.
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.
dpowell11 said:
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.
Click to expand...
Click to collapse
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...
5.1 said:
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...
Click to expand...
Click to collapse
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.
dpowell11 said:
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.
Click to expand...
Click to collapse
Hey,
Great! I'm glad for you...
Keep reading on this site. There's plenty of usefully threads, infos, etc...
Enjoy your phone...
Cheers...
Hello everyone i'm looking for a specific firmware, the PRA-LX1C55B120, i can't get a hold of it from FirmwareFinder, is there another source? Thanks in advance
Anyone?
https://mobiletech360.co/huawei-p8-lite-2017-stock-firmwarerom-android-7-nougat-pra-lx1/
there is a link for c55b183 but even though you download it, i doubt that you can use the dload or twrp to install the firmware.
marstonpear said:
https://mobiletech360.co/huawei-p8-lite-2017-stock-firmwarerom-android-7-nougat-pra-lx1/
there is a link for c55b183 but even though you download it, i doubt that you can use the dload or twrp to install the firmware.
Click to expand...
Click to collapse
Thanks for the answer, but i already can get that from FirmwareUpdater, the one i need is the B120, which is on FU, but apparently the link is broken.
Also why you say that? I think i should be capable of flashing with adb.
oxidyzed said:
Thanks for the answer, but i already can get that from FirmwareUpdater, the one i need is the B120, which is on FU, but apparently the link is broken.
Also why you say that? I think i should be capable of flashing with adb.
Click to expand...
Click to collapse
I haven't tried the adb method as it may screw up your phone if anything goes wrong. On the other hand I tried dload method many times but it always gave me an error. My phone was named P9Lite2017 and it was PRA-LX1 C464, so I installed PRA-LX1C432b191 via Firmware finder, and now I can't even revert back to the C464. I bricked my phone many times too but recovered it thx to erecovery. Still the phone doesn't like it when you change its firmware. Cheers
marstonpear said:
I haven't tried the adb method as it may screw up your phone if anything goes wrong. On the other hand I tried dload method many times but it always gave me an error. My phone was named P9Lite2017 and it was PRA-LX1 C464, so I installed PRA-LX1C432b191 via Firmware finder, and now I can't even revert back to the C464. I bricked my phone many times too but recovered it thx to erecovery. Still the phone doesn't like it when you change its firmware. Cheers
Click to expand...
Click to collapse
Understood, but the erecovery doesn't work for me, every time i try it fails getting the "package from the server"
oxidyzed said:
Understood, but the erecovery doesn't work for me, every time i try it fails getting the "package from the server"
Click to expand...
Click to collapse
I don't know bro, erecovery saved my ass a couple of times, and whenever I screw up the system I just boot into erecovery and tap on 'Download Latest Version and Recovery'. It makes the device like new. Never faced the problem you're facing though.
marstonpear said:
I don't know bro, erecovery saved my ass a couple of times, and whenever I screw up the system I just boot into erecovery and tap on 'Download Latest Version and Recovery'. It makes the device like new. Never faced the problem you're facing though.
Click to expand...
Click to collapse
Ok, will see if i can try something else