Related
Hi all,
prior to any comment, yes, i know there are already posts on this issue, however looking through them didn't help at all unfortunately.
I have a Moto Milestone, origin is Israel.
somewhere along the way i've updated the bootloader to 90.78 and since then - the phone is stuck in the notorious loop and cannot restart the OS.
Tried already to reflash the phone without luck using RSD Lite (downloaded the SBF through http://and-developers.com/sbf:milestone - the 'official' Cellcom IL SBF that was there...)
anyway - i can still access the bootloader which tells me the phone is not fully bricked, however i can't seem to find any proper SBF so it'll reflash itself back to an operative state.
One major problem here - the phone won't get into recovery mode (i've tried all the combinations i know and that have worked before)
i've also read about wiping the cache and user data however - as far as i know, this can only be done by entering the recovery mode, right?
one last resort i've tried - trying to split the SBF and reconstructing it - still no joy.
does anyone here have any advice or solution o this issue? what kind of SBF do i need? how to manually reconstruct the SBF with proper files? etc.
Thanks in advance,
Tomer
Have you tried loooking into fastboot?
Sometimes a phone wont respond to to adb commands and the recovery is corrupted, but you can still flash partitions using fastboot. I "saved" a Moto dext in this fashion once. Cant remember the exact commands, but it was similar to the adb flash commands. I reflashed the recovery partition and then used recovery to flash a ROM in update.zip format. For some reason RSD lite was failing on this phone.
Just something you may want to look into if you are desperate about saving your MS.
Sent from my Milestone using XDA App
Caz666 said:
Have you tried loooking into fastboot?
Sometimes a phone wont respond to to adb commands and the recovery is corrupted, but you can still flash partitions using fastboot. I "saved" a Moto dext in this fashion once. Cant remember the exact commands, but it was similar to the adb flash commands. I reflashed the recovery partition and then used recovery to flash a ROM in update.zip format. For some reason RSD lite was failing on this phone.
Just something you may want to look into if you are desperate about saving your MS.
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
barvaz_t said:
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
Click to expand...
Click to collapse
are you sure your drivers for the phone are installed properly? what RSD lite version are you using? What system? windows 32 or 64 bits?
vladstercr said:
are you sure your drivers for the phone are installed properly? what RSD lite version are you using? What system? windows 32 or 64 bits?
Click to expand...
Click to collapse
I'm quite sure they're installed properly as i managed to upgrade my bootloader version using the RSDlite.
my system is 32 bits and the drivers are the ones i installed throught the Motorola website. I've first used RSDlite 4.6 but after reading a bit I understood there are some differences between versions hence upgraded to 4.9.
barvaz_t said:
I'm quite sure they're installed properly as i managed to upgrade my bootloader version using the RSDlite.
my system is 32 bits and the drivers are the ones i installed throught the Motorola website. I've first used RSDlite 4.6 but after reading a bit I understood there are some differences between versions hence upgraded to 4.9.
Click to expand...
Click to collapse
Try the 90.78ch bootloader from http://and-developers.com/sbf:milestone ...
"XT702 variant of the 90.78 bootloader (notes from 90.78 apply here too).
It's reported to work on the A853 too. "
You've got nothing to loose on trying this. Let me know!
vladstercr said:
Try the 90.78ch bootloader from http://and-developers.com/sbf:milestone ...
"XT702 variant of the 90.78 bootloader (notes from 90.78 apply here too).
It's reported to work on the A853 too. "
You've got nothing to loose on trying this. Let me know!
Click to expand...
Click to collapse
*** [update]
I'm now on 90.78ch and see no difference whatsoever.
I've now started investigating how to re-compile an older SBF file so it'll contain the new RAMDL
(I want to flash the Brazilian version however it contains only 90.74 RAMDL)
I've compiled a new file, however the checksum is incorrect.
How it is possible to recompile this properly?
Already tried the website, the mirror there is no leading to the bootloader itself but to a wiki site.
i've tried searching almost anywhere i know, but this bootloader is non available to download.
if there's another mirror site such as rapidshare or megaupload - i'd be happy to be pointed towards it..
Hi barvaz_t!
barvaz_t said:
...
somewhere along the way i've updated the bootloader to 90.78 and since then - the phone is stuck in the notorious loop and cannot restart the OS.
...
Click to expand...
Click to collapse
Why did you upgrade the bootloader
barvaz_t said:
...
i've also read about wiping the cache and user data however - as far as i know, this can only be done by entering the recovery mode, right?
...
Click to expand...
Click to collapse
Right, is it possible to boot into recovery on your device by holding 'X' button?
barvaz_t said:
*** [update]
I'm now on 90.78ch and see no difference whatsoever.
I've now started investigating how to re-compile an older SBF file so it'll contain the new RAMDL
(I want to flash the Brazilian version however it contains only 90.74 RAMDL)
I've compiled a new file, however the checksum is incorrect.
How it is possible to recompile this properly?
Click to expand...
Click to collapse
You locked yourself out by upgrading the bootloader to the latest one.
Neither downgrade of bootloader would be possible, nor flashing older firmware SBF's.
Apart from that the milestone uses signature check on certain parts of the firmware. I really doubt that it's possible to tweak/recompile a complete SBF.
Something worth to try, is to flash vulnerable recovery SBF from within bootloader mode using RSDlite.
Here's the link to gitorious: http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
If the link does not work for you, there are also some mirrors of this file floating around. Just search!
I guess this should work, because the recovery SBF is using RAMLDR 90.78 (do know about the sign check during flash, but i guess checksum should be O.K.).
With vulnerable recovery properly installed, you might then use OpenRecovery to check your system and restore to some working state.
Good luck!
scholbert
scholbert said:
Hi barvaz_t!
Why did you upgrade the bootloader
Right, is it possible to boot into recovery on your device by holding 'X' button?
You locked yourself out by upgrading the bootloader to the latest one.
Neither downgrade of bootloader would be possible, nor flashing older firmware SBF's.
Apart from that the milestone uses signature check on certain parts of the firmware. I really doubt that it's possible to tweak/recompile a complete SBF.
Something worth to try, is to flash vulnerable recovery SBF from within bootloader mode using RSDlite.
Here's the link to gitorious: http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
If the link does not work for you, there are also some mirrors of this file floating around. Just search!
I guess this should work, because the recovery SBF is using RAMLDR 90.78 (do know about the sign check during flash, but i guess checksum should be O.K.).
With vulnerable recovery properly installed, you might then use OpenRecovery to check your system and restore to some working state.
Good luck!
scholbert
Click to expand...
Click to collapse
Thanks Scholbert for the detailed answer.
the link you gave directs to an image the RSDlite cannot flash (=error validating image).
If your interntion was that I'm supposed to flash the vulnerable recovery only, than bad news - It's already 'installed' on my device (and it shows no error whatsoever during this installation..)
Well, thanks again for trying to help, I think I'm officially out of suggestions or options here unless anyone can give further advice...
barvaz_t said:
...
If your interntion was that I'm supposed to flash the vulnerable recovery only, than bad news - It's already 'installed' on my device (and it shows no error whatsoever during this installation..)
...
Click to expand...
Click to collapse
So can you still enter recovery?
Regards,
scholbert
No, never did (since the upgrade)
If I had access to the recovery i would have at least managed to install OpenRecovery or something and manage to reflash the device
barvaz_t said:
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
Click to expand...
Click to collapse
Did you try to fastboot flash only the boot.img? What about recovery? I seem to remember flashing a recovery.img on the dext...but this was last year. I may be wrong but i believe i flashed only a recovery image and then was able to access the recovery (which would allow all sorts of additional goodies).
I find it strange that fastboot reports only downloading. I seem to remember some error messages and timeouts?
Sent from my Milestone using XDA App
Caz666 said:
Did you try to fastboot flash only the boot.img? What about recovery? I seem to remember flashing a recovery.img on the dext...but this was last year. I may be wrong but i believe i flashed only a recovery image and then was able to access the recovery (which would allow all sorts of additional goodies).
I find it strange that fastboot reports only downloading. I seem to remember some error messages and timeouts?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Nope.
trying to flash the recovery / boot images only results in the message 'downloading...' and nothing (waited for like 3 hours..)
when I terminate the action by Ctrl+C and then trying again - the message is instantly 'FAILED..' along with specification that the action of sending the command has failed.
I'm literaly out of ideas, don't know what to do..
Sent from my Milestone using XDA App
I am starting to think that there is something wrong with your device (like broken hardware).
In all my experimenting with rsd/fastboot, i did not once get a "hang". I would get checksum/signature errors, size errors, etc...but i always got some type of error code or status.
This is on 3 different Mot devices that run Android.
Sorry
Sent from my Milestone using XDA App
Caz666 said:
I am starting to think that there is something wrong with your device (like broken hardware).
In all my experimenting with rsd/fastboot, i did not once get a "hang". I would get checksum/signature errors, size errors, etc...but i always got some type of error code or status.
This is on 3 different Mot devices that run Android.
Sorry
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
The device was working fine before upgrading the bootloader, so it seems that this is not a hardware issue.
Either way - guess i'll be taking it to a lab and let them figure this out..
idea
is the milestone n droid from usa same sbf file used if so i have the right sbf file i found i had couple times i had to reinstall to stock if u want to try it i can email it it work for me saved me from bricks its rooted phone just fyi
streetracer89101 said:
is the milestone n droid from usa same sbf file used if so i have the right sbf file i found i had couple times i had to reinstall to stock if u want to try it i can email it it work for me saved me from bricks its rooted phone just fyi
Click to expand...
Click to collapse
@streetracer89101 - no, as far as i know Droid and Milestone use different firmware so it won't help unfortunately. Not that it would matter if I did flash my device - it's not like I can use it anyway..
Thanks again for trying to help out
Tomer
90.78ch bootloader
Hello, I really need the bootloader 90.78ch maybe you can me it someone give Many Thanks
300zxtt said:
Hello, I really need the bootloader 90.78ch maybe you can me it someone give Many Thanks
Click to expand...
Click to collapse
Attached. Enjoy
VS910ZV9_05.S9_05.P58014.R5.tot​
how use this frimware been waiting too root it u never know jcase
Holy crap... where did you get this?
This can't be real...
I'm confused what exactly is this?
nasirahmed said:
VS910ZV4_04.S4_04.P58008.R5.user.tot​
Click to expand...
Click to collapse
One million internets to you, sir(or madam)...
Sent from my VS910 4G using Tapatalk
is this so we can get developers to make a custom recovery??????????
it is supposed to be the stock firmware for the revolution which would allow you to flash your system back to stock.
I have scanned the file and there are 3 files contained inside. I have not been able to extract them however. There are 3 img files inside which tally some 700+ meg.
Haxcid said:
it is supposed to be the stock firmware for the revolution which would allow you to flash your system back to stock.
I have scanned the file and there are 3 files contained inside. I have not been able to extract them however. There are 3 img files inside which tally some 700+ meg.
Click to expand...
Click to collapse
I have not found a way to extract the embedded files either. This is used with a Verizon only tool that is readily available. I wouldn't recommend flashing this unless you brick or destroy your phone (as a last result).
how u flash this
blkhwk5177 said:
how u flash this
Click to expand...
Click to collapse
It's a program called: LGNPST. You can Google it and you will find a few download locations.
I looked everywhere to find out how to load this, can somebody with lg experience point me in the right direction. im coming from a droid x, i would just sbf to restore a phone; that was easy
LGPNST does not support this device yet that I know of.
Verizon has a tool as well but I don't think it works with TOT files.
Haxcid said:
LGPNST does not support this device yet that I know of.
Verizon has a tool as well but I don't think it works with TOT files.
Click to expand...
Click to collapse
Yeah, you have to have the proper DLL, and we haven't found it yet. Cubed said he'd have a stock ROM out here shortly.
After that, he plans to deodex and release a cleaned version of stock (debinged)
majorpay said:
Yeah, you have to have the proper DLL, and we haven't found it yet. Cubed said he'd have a stock ROM out here shortly.
After that, he plans to deodex and release a cleaned version of stock (debinged)
Click to expand...
Click to collapse
I'm really looking forward to de-binged, de-odexd etc. Rom!!!
Hi,
this is the factory soft provided by LG to update VS910.
[LGDP2V42]only_VS910_20110430_download
but this soft need a protection dongle (need to be attached to PC) to run. LG Service Centers have this. It will be intersting if someone can find something useful from it.
I don't know if it works or not but...
http://www.mobile-files.com/forum/showthread.php/1384-How-load-TOT-file-with-LGNPST-LAB.1.2
So i guess in LGNPST, you just click browse, then put *.* in file name, hit enter, then select your .tot.
The problem isnt getting the software its the fact that unlike motorola the lg program requires a device specific .dll file so without that file the flash software and firmware are really of no use
Sent from my rooted and de-Bing-ed LG Revolution
vs910 dll for npst
here is the dll u need to flash this firmware... as far as firmware u should be able to flash with npst lab version. u need to register dll first
lazarus2297 said:
The problem isnt getting the software its the fact that unlike motorola the lg program requires a device specific .dll file so without that file the flash software and firmware are really of no use
Sent from my rooted and de-Bing-ed LG Revolution
Click to expand...
Click to collapse
give me the link for the lab installer and the rest of the steps
I rooted my father's O4X HD using the System Backup App method. I then used that app to boot into TWRP. (TWRP isn't permanent). The bootloader is locked. Basically, the phone is stock except it is rooted.
He is running ICS and would like to update to JB. He doesn't care that the device is rooted and he doesn't use the root.
My question is: Can I completely unroot with SuperSu, then update via OTA?
I've done countless hours of research and I cannot get an definite answer. I will be trying to unroot, then applying the OTA update tonight. Are there any risks involved? If I do brick it, how do I reflash the stock ROM?
samgoalie17 said:
I rooted my father's O4X HD using the System Backup App method. I then used that app to boot into TWRP. (TWRP isn't permanent). The bootloader is locked. Basically, the phone is stock except it is rooted.
He is running ICS and would like to update to JB. He doesn't care that the device is rooted and he doesn't use the root.
My question is: Can I completely unroot with SuperSu, then update via OTA?
I've done countless hours of research and I cannot get an definite answer. I will be trying to unroot, then applying the OTA update tonight. Are there any risks involved? If I do brick it, how do I reflash the stock ROM?
Click to expand...
Click to collapse
If I'm wrong then I'm sure someone will correct me, but the JB update isn't avaliable via OTA. It was released to be flashed manually from a PC only.
as far as i know you only can update via lg pc suite to official JB.
or flash it via kdz/dz
but woth lg pc suit you will get 100% the right rom for your country/area.
and if you softbrick it there is a tut in general section how to recover it. but there is a low risk that you brick it. I don't know if the official pc suite needs an unrooted device. just do it via SuperSU should do it.
good luck
Sent from my LG-P880 using xda app-developers app
SimonTS said:
If I'm wrong then I'm sure someone will correct me, but the JB update isn't avaliable via OTA. It was released to be flashed manually from a PC only.
Click to expand...
Click to collapse
Thank you for your response. Let's say I'm talking in general, if I used that method, would it be possible to OTA? I'm worried when the update is released I might brick his phone or I won't be able to update...
tobixdev said:
as far as i know you only can update via lg pc suite to official JB.
or flash it via kdz/dz
but woth lg pc suit you will get 100% the right rom for your country/area.
and if you softbrick it there is a tut in general section how to recover it. but there is a low risk that you brick it. I don't know if the official pc suite needs an unrooted device. just do it via SuperSU should do it.
good luck
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
Does it matter which region/country I flash from?
samgoalie17 said:
Does it matter which region/country I flash from?
Click to expand...
Click to collapse
actually not. only baseband will be different but i hadn't any connection problems with that i tested. but if the provider of your fathers phone has his own rom there are some preinstalles apps you may find useful.
and if you flash it via pc suite and something goes wrong lg has to reflash the phone for free (warranty, at least as far as i know, im not 100% sure). But unroot it before. just to be sure
Sent from my LG-P880 using xda app-developers app
samgoalie17 said:
Thank you for your response. Let's say I'm talking in general, if I used that method, would it be possible to OTA? I'm worried when the update is released I might brick his phone or I won't be able to update...
Click to expand...
Click to collapse
If you fully unroot then you should be able to upgrade by OTA to whatever was the latest v10x code (ICS) for his device.
Two useful sites;-
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=abcdefghijklmnopq
Replace 'abcdefghijklmnopq' with the device IMEI to find the latest v20x code that you can get if you want to go down that route.
http://lg-phone-firmware.com/index.php?id_mod=15
List of all firmware available, check what the latest v10.x code for the device was and you'll see if there is any reason to unroot and check OTA.
Hello everyone,
my D405n is partially correctly recognized as w7n:
ro.product.board=w7n
ro.build.product=w7n
ro.cm.device=w7n
ro.product.device=w7n
ro.build.product=w7n
ro.cm.device=w7n
However partially incorectly as w7ds:
ro.hardware=w7ds
ro.boot.hardware=w7ds
I have unrooted my L90 using towelroot, unlocked bootloader and install recovery with
[GUIDE] Unlock Bootloader and Flash Custom Recovery L90 D410, D405n, D405 [CWM][TWR] method using file for D405n and flashed ROM from @Quarx. In order to flash the ROM I had to remove hardware=w7 check. Now automatic update works in the sense, that incremental update is downloaded, but due to hardware=w7 check I have to modify the updater script every time. Any idea how to correct ro.hardware and ro.boot.hardware entries? I have attached my build.prop file and output from getprop command, if that could be helpful.
Best regards
lecterek said:
Hello everyone,
my D405n is partially correctly recognized as w7n:
ro.product.board=w7n
ro.build.product=w7n
ro.cm.device=w7n
ro.product.device=w7n
ro.build.product=w7n
ro.cm.device=w7n
However partially incorectly as w7ds:
ro.hardware=w7ds
ro.boot.hardware=w7ds
I have unrooted my L90 using towelroot, unlocked bootloader and install recovery with
[GUIDE] Unlock Bootloader and Flash Custom Recovery L90 D410, D405n, D405 [CWM][TWR] method using file for D405n and flashed ROM from @Quarx. In order to flash the ROM I had to remove hardware=w7 check. Now automatic update works in the sense, that incremental update is downloaded, but due to hardware=w7 check I have to modify the updater script every time. Any idea how to correct ro.hardware and ro.boot.hardware entries? I have attached my build.prop file and output from getprop command, if that could be helpful.
Best regards
Click to expand...
Click to collapse
I'll send @Quarx a link to this thread.
Strange, I have a D405n too, but never had this issue. I wrote a guide explaining the way I unlocked the bootloader here. I used Quarx' latest TWRP, which can be found in his thread and just did a full wipe and flashed CM after that. Seemed to work for me. I would just try reflashing the KDZ again and restarting the unlock process with the newest files available.
EDIT: I just checked my build.prop and my w7n is recognized as a w7. The device is still recognized as the D405n though, so NFC does show up in the menu.
shinobisoft said:
I'll send @Quarx a link to this thread.
Click to expand...
Click to collapse
OK, thx. I hope he could provide some suggestions.
SubliemeSiem said:
Strange, I have a D405n too, but never had this issue. I wrote a guide explaining the way I unlocked the bootloader here. I used Quarx' latest TWRP, which can be found in his thread and just did a full wipe and flashed CM after that. Seemed to work for me. I would just try reflashing the KDZ again and restarting the unlock process with the newest files available.
EDIT: I just checked my build.prop and my w7n is recognized as a w7. The device is still recognized as the D405n though, so NFC does show up in the menu.
Click to expand...
Click to collapse
Is it necessary to flash the KDZ? Flashing/dd aboot.bin again should be sufficient I think. I did it, but situation is the same. I have checked aboot.bin files for D405n linked by people in different posts over xda forum (your link as well) and all the files are identical, so in my opinion there is no newest aboot.bin. Concerning TWRP I have tried latest Quarx version and also this version. No difference concerning w7n and w7ds mismatch.
Yesterday I tried also to flash Quarx' CWM instead of TWRP and surprisingly automatic update worked with no problem with hardware=w7 check. However, output/content of getprop command and build.prop file are unchanged. Strange. Looks like with TWRP hardware=w7 check fails while with CWM everything is OK, which would indicate different getprop output for different recovery.
Might be you guys got the D405n with softwareversion 10a, where my device had 10b.. Seen this before and most users with that combination seem to have issues. Might also be a total coincidence though. I don't know what the difference is, but I do know the Russians that made the aboot.bin files made a seperate one for D405n_10b and for D405_10a. So either the version for D405n combined with 10a is missing or you should be able to use one of those two versions.. But once again, this is pure speculation, I don't know if this can cause these issues.
SubliemeSiem said:
Might be you guys got the D405n with softwareversion 10a, where my device had 10b.. Seen this before and most users with that combination seem to have issues. Might also be a total coincidence though. I don't know what the difference is, but I do know the Russians that made the aboot.bin files made a seperate one for D405n_10b and for D405_10a. So either the version for D405n combined with 10a is missing or you should be able to use one of those two versions.. But once again, this is pure speculation, I don't know if this can cause these issues.
Click to expand...
Click to collapse
Is it OK, to use aboot.bin_D405_10a for D405n? I mean, no soft brick in that case? With stock ROM I had 10b as well.
lecterek said:
Is it OK, to use aboot.bin_D405_10a for D405n? I mean, no soft brick in that case? With stock ROM I had 10b as well.
Click to expand...
Click to collapse
I'm not sure, but even then you should still be able to flash the kdz and start over. It doesn't take that long to go through the entire process, I've done it multiple times already. I don't have these problems, so I can't experiment with these files.
Hi, recently i managed to brick my Korean F340L G Flex so bad. I've tried almost everything software wise.
-The solution:
I'm planning to change the logic board from a Sprint LS995 model. I think it will work ok. Of course I'll have to some how get an unlock code in order to use it in Greece where I live.
I've seen in ebay some users providing for a small amount of money this code.
So, what do you think. Will it work as I'm thinking? Any comments, suggestions, guides welcome. Thanks
Here is a short story:
"Hello, to all, I'd like to share my experience and problem with my LG G Flex, as a last hope to find a solution to unbrick it.
I know that the talk here is about G2's, but I saw many users reviving their Flexes with OP's method.
So here is what I did in steps:
1)I rooted my Lg g flex F340L
2)New OTA, downloaded, but failed to install after reboot. The message was no OTAs for rooted devises
3)Tried to unroot, but with no success. Still no installation of OTA.
4)Found, and flashed the stock F340L rom , (had an EFS backup), from another user here(.tot file), with LGFlashTool.
5)SIM card was not recognized any more (Greece, Vodafone), so no calls. Did all the updates, but no SIM, still.
6)Hard reset, still no SIM.
7)Decided to flash stock F340K kdz rom, and install CWR. All good, SIM detected, OTA downloaded, but after reboot stuck at CWM nenu. Whatever I do just CWM.
8)No download mode, or usb support, just an LG FLEX unknown device. Got some drivers only to be seen as lenovo ADB device.
9)I found the test point on the motherboard and short circuit it. Got a qhsusb_bulk(qualcomm 9008) under COM ports, but not on a specific port.
10) No flash capability, and no partitions to try and flash the 10 or so, images. Ubundu, no luck with the partition detection either.
11)After many reboots and button long presses the CRW came back...again
Well as I can see, there is not so much support for the korean variants and I might have destroyed my phone. So, I need your advise in changing the motherboard. I found M/B's from AT&T and Sprint variants, to install to my F340L. I think it will work. After I will purchase an unlock code from lets say ebay to unlock it to all GSM networks ( I live in Greece).
What is CRW or CWR?
Are you referring to CWM? The recovery?
If you can boot into cwm your phone has a chance to be saved no need to change the mb.
By the way sprint doesnt give out unlock codes like att. There is an specific process to sim unlock sprints variant.
Alex_XV6700 said:
What is CRW or CWR?
Are you referring to CWM? The recovery?
If you can boot into cwm your phone has a chance to be saved no need to change the mb.
By the way sprint doesnt give out unlock codes like att. There is an specific process to sim unlock sprints variant.
Click to expand...
Click to collapse
Yes sorry, CWM I was refering to. Well, since I have no other option at the moment. I'll try to find that specific process you've mentioned when I get the board(help or hint welcome)
As, for the M/B change, no system partitions are recognized in order to flash individual .images to unlock them.
If you can access CWM you dont need to flash the .img files for your phone. Instead you could flash a stock zip through adb sideload or flash twrp through sideload too. Twrp allows MTP use so someone using an F340K can help you with a stock backup and you can unbrick instead of changing board.
Alex_XV6700 said:
If you can access CWM you dont need to flash the .img files for your phone. Instead you could flash a stock zip through adb sideload or flash twrp through sideload too. Twrp allows MTP use so someone using an F340K can help you with a stock backup and you can unbrick instead of changing board.
Click to expand...
Click to collapse
The only stock image I have is in .TOT file for the L variant. I also have stock .kdz file for the K variant. I can sideload to /sdcard/0/ directory only, if that helps. I'll try to find twrp.zip and try it. But the main problem is to find stock rom in .zip format.
I've managed to install twrp 2.8.0.0...
N3M3SYS said:
I've managed to install twrp 2.8.0.0...
Click to expand...
Click to collapse
Ok
now you could try to flash this rom.
let me know how it goes.
Alex_XV6700 said:
Ok
now you could try to flash this rom.
let me know how it goes.
Click to expand...
Click to collapse
Thnx for the link, but this rom says is for F340K, I have a F340L. In addition the download link is not working...
N3M3SYS said:
Thnx for the link, but this rom says is for F340K, I have a F340L. In addition the download link is not working...
Click to expand...
Click to collapse
Ok, this will take time friend.
I will try to make you a flashable zip of stock F340L KK.
Maybe it will take me some 4 or 5 hrs.
Alex_XV6700 said:
Ok, this will take time friend.
I will try to make you a flashable zip of stock F340L KK.
Maybe it will take me some 4 or 5 hrs.
Click to expand...
Click to collapse
That would be a miracle for me, I'll be waiting!