Related
Bricked bml5 and stl5 file with dd
command of terminal emulator.
dd if=/dev/block/stl5 of=/sdcard/
stl5.img
dd if=/sdcard/stl5.img of=/dev/block/stl5
Now cant go to recovery, cant switch
on the phone when i try to switch on
the phone screen blinks like grey
color for 1 second. But can go to download mode, tried
flashing with odin with one package
and with 4 files also no luck same
thing happens everytime after getting
success also.
Help me.
This is a boot menu that will allow you to select if you want to boot a kernel or reboot in to recovery. I highly recommend everyone install this so you always have a way to boot in to recovery in case of problems. Just like recovery, it will sit at a black screen for an abnormal amount of time before showing. It's something like 20 seconds. But once it shows, you will have 5 seconds to make a selection. It defaults to booting the kernel, but you can use the up down keys to change the selection. Once it hits 0, it will do whatever option is selected. You can also hit enter and it will do that right away.
Right now, this is a very rough version 1.0. I plan to add some more features to it and would like to hear feedback from people to see what they think about it.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV. Of course, this requires root and unlock.
Installation
Install CWM version 6.0.5.1.4 or higher. You MUST VERIFY CWM is at least 6.0.5.1.4 and it works BEFORE proceeding. You WILL BRICK your Fire TV if you are not properly unlocked, and verifying 6.0.5.1.4 or higher is working will do that.
For the following instructions, replace bootmenu.img with whatever filename you downloaded from this post, for example firetv-bootmenu-1.0.img. Copy bootmenu.img to /sdcard (via adb or whatever). Then from adb shell run this: DO NOT COPY PASTE THE WHOLE THING, DO EACH COMMAND ONE AT A TIME.
Code:
su
mount -o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Once you have verified it is working, you can replace /system/boot/boot.img with whatever kernel you want. Whether it be the overclocked kernel, or a Fedora kernel, or something else. And you never have to worry about bricking or getting back in to recovery.
Notes
Flashing anything that updates boot.img will cause you to loose bootmenu support. All pre-rooted roms 51.1.4.0 and lower will do this. Anything past 51.1.4.0 will only support booting their kernels through this method. When flashing 51.1.4.0 or lower when using bootmenu, you must repeat the entire bootmenu installation procedure because those roms will overwrite the bootmenu.
Changelog and Downloads:
Nov 15, 2014 - 1.0 (md5sum: a8a3c28baafe43f354d92e6cc8b392d3)
Hmm, tried this and didn't seem to do anything. It did sit at the black screen for a while but then no boot menu comes up. Tried rebooting normally and to recovery but either way no boot menu come up, just boots straight to recovery or to XBMC (I've set XBMC as my launcher).
I'm using your 6.0.5.1.4a recovery, bootloader partially unlocked etc.
AQKhanTheOne said:
Hmm, tried this and didn't seem to do anything. It did sit at the black screen for a while but then no boot menu comes up. Tried rebooting normally and to recovery but either way no boot menu come up, just boots straight to recovery or to XBMC (I've set XBMC as my launcher).
I'm using your 6.0.5.1.4a recovery, bootloader partially unlocked etc.
Click to expand...
Click to collapse
It's completely blank? I timed from 'adb reboot' to when the menu showed up and it was 24 seconds. Then you should see *something* on the screen, and then 5 seconds later it should reboot the firetv and then the kernel should start loading. 25 seconds after adb reboot, try hitting the down arrow and then waiting a few seconds. It should boot into recovery. Does that work? Also, are you using overscan in recovery?
Yes completely blank. Actually it only sat at the blank/black screen the first time it rebooted after the install. After that each reboot to either recovery or to XBMC does not result in the long blank screen at all. Though there is the briefest lightening of the screen right before the white amazon logo comes up. And no, I'm not using overscan. The result of the install is below if that helps. It's likely I've made a mistake.
Code:
[email protected]:/ $ su
mount -o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
smount -o remount,ro /system
u
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/bootmount -
o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
[email protected]:/ # mount -o remount,rw /system
[email protected]:/ # mkdir /system/boot
dcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.939 secs (5407818 bytes/sec)
[email protected]:/ # mount -o remount,ro /system
[email protected]:/ # exit
AQKhanTheOne said:
Yes completely blank. Actually it only sat at the blank/black screen the first time it rebooted after the install. After that each reboot to either recovery or to XBMC does not result in the long blank screen at all. Though there is the briefest lightening of the screen right before the white amazon logo comes up.
Click to expand...
Click to collapse
Well it has no effect on recovery, just the main system. It should do it every time. Not quite sure why you aren't seeing it though.
rbox said:
Well it has no effect on recovery, just the main system. It should do it every time. Not quite sure why you aren't seeing it though.
Click to expand...
Click to collapse
I did rename the downloaded file to bootmenu.img to avoid having to change the name in the shell command. Don't know if that makes a difference.
AQKhanTheOne said:
I did rename the downloaded file to bootmenu.img to avoid having to change the name in the shell command. Don't know if that makes a difference.
Click to expand...
Click to collapse
No, the name doesn't matter. Try this version. It should have a solid blue background to start and then if you hit the down arrow it'll switch to red. Blue will boot the kernel, red will boot recovery.
EDIT: Okay. I reread your post and saw you included the output from the shell. Don't copy paste it all at once. Do the commands one at a time.
rbox said:
No, the name doesn't matter. Try this version. It should have a solid blue background to start and then if you hit the down arrow it'll switch to red. Blue will boot the kernel, red will boot recovery.
EDIT: Okay. I reread your post and saw you included the output from the shell. Don't copy paste it all at once. Do the commands one at a time.
Click to expand...
Click to collapse
Okay, that did the trick! Now I get the colorful Rbox's Boot Menu with two options, Boot Kernal and Boot to recovery.
Thanks as always for all your great work!
Well this looks like its going to be handy.
In with no issues Rbox and countdown
Idea: Press and hold key on the remote or keyboard to get to boot-menu (unsure if this can be done)
Press nothing boots to FTV
Thanks
Works perfect here, the remote doesnt work tho right? need to use a keyboard?
nhumber said:
Works perfect here, the remote doesnt work tho right? need to use a keyboard?
Click to expand...
Click to collapse
Yeah. Just like recovery it needs the keyboard.
works great , thank you for all your efforts
rbox said:
Yeah. Just like recovery it needs the keyboard.
Click to expand...
Click to collapse
Thanks a lot rbox. This works as described though I am not sure at this point what to do with it. I just installed it as you said it would be useful
heyredy141 said:
Thanks a lot rbox. This works as described though I am not sure at this point what to do with it. I just installed it as you said it would be useful
Click to expand...
Click to collapse
My main goal with it was to always be able to get to recovery. Secondary goal is to easily use alternate kernels without risk of not being able to get back to recovery. Which really gets back to the main goal. A side effect is that people can load fedora kernels easy without having to screw around with their partitions.
Im trying to wrap my head around how this works.. I get what we are doing, but wont flashing something (ie anything with a boot.img) with CWM overwrite the bootmenu?
mastafunk said:
Im trying to wrap my head around how this works.. I get what we are doing, but wont flashing something (ie anything with a boot.img) with CWM overwrite the bootmenu?
Click to expand...
Click to collapse
That's very much correct. I think I'm going to make all my future prerooted images put their boot.img in /system/boot and not flash it to the boot partition.
rbox said:
That's very much correct. I think I'm going to make all my future prerooted images put their boot.img in /system/boot and not flash it to the boot partition.
Click to expand...
Click to collapse
Thanks for your quick reply. Glad I'm on the same page .. I'm working on a custom ROM and was thinking that was something i would address the same way but then thought for a sec maybe you had moded the newer cwm to just do that instead of flashing the boot.img.
EDIT
might want to put some more thought into doing that for the newer pre-roots as someone may flash back to an older one then flash forward and screw themselves.. maybe include some sort of checking in cwm? And maybe include a warning in the OP if they flash any pre-root they loose the safetynet of the bootmenu.img until applied again.
Worked great for me. Thanks rbox for all of the support you've given this device!
so I ran the first commands and it looks like I have boot.img in /system:
[email protected]:/system/boot # ls -l
ls -l
-rw------- root root 1675264 2014-11-21 18:19 boot.img
My concern is that I don't have any free space in system at all:
/system 756M 756M 0K 4096
is this normal to be this tight on the 51.1.4.0 prerooted rom?
I have even removed WhisperplayCore.apk when I was trying to get the chromecast receiver app working (sadly looks like that's fruitless at this point, but that's a separate topic)
I haven't copied the bootmenu image over just incase there is an issue with that boot.img that may not have been a full copy or something. Just trying to be extra careful.
One tiny suggestion: Change the wording in your post "When flashing 51.1.4.0 or lower when using bootmenu, you must reflash bootmenu." to "When flashing 51.1.4.0 or lower when using bootmenu, you must repeat the entire bootmenu installation procedure."
The reason: After setting up bootmenu on my test device, I realized it was on 51.1.3.0 when I thought it was on 51.1.4.0. I installed 51.1.4.0 then re-read your note to "reflash bootmenu". I thought "ah simple, i'll just re-run the last dd step since everything is still in place." Of course, I forgot that installing 51.1.4.0 wiped out /system/boot/boot.img so when I put bootmenu in place I no longer had a stock boot image on the box. It was a simple fix (I just used bootmenu to get into recovery and reinstalled 51.1.4.0), but probably best to be explicit with the above sentence.
My EFS partition was corrupted after an EFS restore from TWRP (Check post #2 for link to explanation).
I was in panic mode when the super helpful folks over at #twrp sorted me out with this solution (thank you so much @jcadduono). Thought I would share it so it could possibly help someone else.
This has worked on my OnePlus 3, but it might even work on other devices.
Do this AT YOUR OWN RISK. I am not responsible for your device.
Boot into TWRP (Poweroff, then power on using Vol Down + Power Button)
Go to Advanced > Terminal
Type in the following commands:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot
Alternatively, you could also do this from your computer over adb with the following commands:
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
Alternatively, you could try this [Though I haven't tested this myself]:
Make sure you have fast boot and drivers (for info look here)
Boot into fastboot (Poweroff, then power on using Vol Up + Power Button)
Type in the following commands into terminal:
Code:
fastboot erase modemst1
Code:
fastboot erase modemst2
Reboot
Good luck and I hope this helps!
PS: It is best to backup your EFS before something like this happens.
Take 5 minutes out of your day to do this. You can find a tool to do this here, or do it yourself by following the instructions here.
I'm just going to go ahead and link here for an explanation:
http://forum.xda-developers.com/showpost.php?p=68500121&postcount=64
BTW: Is this issue still present on OnePlus 3 official TWRP? If so we can recompile it, we *should* have all the bugs fixed in android-6.0 latest branch right now. Currently main development is happening on android-7.0 branch of omnirom/android_bootable_recovery (TWRP) but we've backported bug fixes to android-6.0 only and it's probably a good idea for developers to use that as a "stable" branch for now.
jcadduono said:
I'm just going to go ahead and link here for an explanation:
http://forum.xda-developers.com/showpost.php?p=68500121&postcount=64
BTW: Is this issue still present on OnePlus 3 official TWRP? If so we can recompile it, we *should* have all the bugs fixed in android-6.0 latest branch right now. Currently main development is happening on android-7.0 branch of omnirom/android_bootable_recovery (TWRP) but we've backported bug fixes to android-6.0 only and it's probably a good idea for developers to use that as a "stable" branch for now.
Click to expand...
Click to collapse
So, I'm not sure what version of TWRP I used to backup, but whatever it was, I only had a single efs backup (efs1.emmc.win). efs2.emmc.win was not present at all. I am guessing during restore, this is what must have caused the problem. I am not sure if TWRP should be checking for sub partitions before restore, but it definitely didn't throw any errors. Only if I had md5 check enabled did it complain that the md5 did not match '' (empty string), which is when I realized what had happened.
kgs1992 said:
So, I'm not sure what version of TWRP I used to backup, but whatever it was, I only had a single efs backup (efs1.emmc.win). efs2.emmc.win was not present at all. I am guessing during restore, this is what must have caused the problem. I am not sure if TWRP should be checking for sub partitions before restore, but it definitely didn't throw any errors. Only if I had md5 check enabled did it complain that the md5 did not match '' (empty string), which is when I realized what had happened.
Click to expand...
Click to collapse
Yeah the adb backup patch went in and broke restore and backup of subpartitions, backup was fixed not much later so you must have had a twrp build from just after the adb backup patch (which broke stuff), it wasn't for a few weeks until the restore issue was noticed, where it restored 1st partition in the backup to all subpartitions of it. Those are all fixed now but there could still be builds out there with any or all of those issues.
Reason it wasn't so noticed was not many devices with multiple subpartitions attached to one partition and not many people backing up and restoring efs. (which is often subpartitioned in twrp)
3rd way worked for me. thx
NickosD said:
3rd way worked for me. thx
Click to expand...
Click to collapse
You're welcome, but it's the folks at twrp that deserve to be thanked.
sry if my question too noob
but im curious
whats that "fastboot erase modemst1" meaning?
delete something or what?
im google it before asking here, haha
D4almond said:
sry if my question too noob
but im curious
whats that "fastboot erase modemst1" meaning?
delete something or what?
im google it before asking here, haha
Click to expand...
Click to collapse
Yes, you are erasing that partition, which the modem then rebuilds, as mentioned in the link in post #2
Thx for the explanation!
Nice thread btw, i believe this will save many hard ass out there, kek
Sent from my A0001 using Tapatalk
This worked successfully on my Mi 5. So basically I restored a backup with TWRP 3.0.2-2 and it messed up my modem, lost IMEI etc.
I followed the steps in TWRP itself > Terminal and typed the codes. Rebooted and worked.
Thank you so much for putting up the guide. I though I'd be buying an iPhone 7+ or LGV20 but because this fixed my phone, you saved me a lot of money.
@ northropgrummanrq180
Please Help ME! Save US!
http://forum.xda-developers.com/mi-5/how-to/xiaomi-mi5-efs-backup-restore-methods-t3432730
https://xiaomi.eu/community/threads/mi5-no-imei-no-modem-no-baseband-need-help.36225/
Thank you for sharing this and everyone at TWRP!!!!!!! I thought my phone was deader than a door nail!!! Method 1 worked for me perfect. Has this bug been fixed yet in the latest official version of TWRP??
I've fixed my MI5, which didn't have a baseband anymore after I've accidentally restored the efs in TWRP, using this tutorial. Thanks so much!
kgs1992 said:
My EFS partition was corrupted after an EFS restore from TWRP (Check post #2 for link to explanation).
I was in panic mode when the super helpful folks over at #twrp sorted me out with this solution (thank you so much @jcadduono). Thought I would share it so it could possibly help someone else.
This has worked on my OnePlus 3, but it might even work on other devices.
Do this AT YOUR OWN RISK. I am not responsible for your device.
Boot into TWRP (Poweroff, then power on using Vol Down + Power Button)
Go to Advanced > Terminal
Type in the following commands:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot
Alternatively, you could also do this from your computer over adb with the following commands:
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
Alternatively, you could try this [Though I haven't tested this myself]:
Make sure you have fast boot and drivers (for info look here)
Boot into fastboot (Poweroff, then power on using Vol Up + Power Button)
Type in the following commands into terminal:
Code:
fastboot erase modemst1
Code:
fastboot erase modemst2
Reboot
Good luck and I hope this helps!
PS: It is best to backup your EFS before something like this happens.
Take 5 minutes out of your day to do this. You can find a tool to do this here, or do it yourself by following the instructions here.
Click to expand...
Click to collapse
"by-name" here means?
I didn't have wi-fi unusable or anything on my OP3, but I was only getting signal for emergency calls before trying a series of things including this. This happened after flashing open beta 9 from an earlier community build. First let me just say in my case in TWRP I wiped then changed /data partition to f2fs and clean flashed the beta as usual along with superSU. Then started my phone and realized I was only able to make emergency calls.
So I tried playing in Settings > Sim & Network > SIM 1 & tried resetting network operators & finding automatically. That may have helped.. but I didn't see any improvement so I removed my sim, reinserted & restarted. It didn't seem to be fixed by then so I tried the 3 methods OP posted. Only#1 worked in my case, but data appears to be working normally now. Whether it was the last thing I tried or some combination, IDK.
Just wanted to write all this out in case anyone is still having issues after following OP's instructions.
Thanks!
Used the dd commands in both adb shell and twrp terminal and get "dd: /dev/block/bootdevice/by-name/modemst1: No space left on device". Also tried the fastboo0t commands and got "FAILED (remote: Partition flashing is not allowed)" Any ideas?
Worked like a charm
Thank you so much! you just saved my new Mi5 prime which i messed up by trying to unlock more LTE bands.
kenboyles72 said:
Used the dd commands in both adb shell and twrp terminal and get "dd: /dev/block/bootdevice/by-name/modemst1: No space left on device". Also tried the fastboo0t commands and got "FAILED (remote: Partition flashing is not allowed)" Any ideas?
Click to expand...
Click to collapse
am also having the same issue with my htc one e8, am getting remote: partition is not allowed. Please anyone with a solution about this should share
thank you very much hope GOD replied to your knowledge
Great explanation! My phone was stuck in a soft-brick mode yesterday. Followed the mega unbrick guide and got it working again, albeit being reverted to OOS 3.1.2. The cellular network is fine (I can make and receive calls, and mobile data is working), although WiFi and Bluetooth don't work. I tried rebooting into fastboot and erasing the two
Code:
modemst
files but to no avail.
Any reason as to why this is happening?
Hey all.
This is my first Post.
I have registered myself because I've got a problem.
Last week i rooted my phone [ Sony Xperia E1 ]
I used Kingoroot for it.
i was reading some stuff about tweaking in the BuildProp file in the System folder.
i wanted to disable the boot animation on boot up.
So i Copied the BuildProp File to my Re moveable SDcard as backup and Added in
the original BuildProp file the line debug.sf.nobootanimation=1 .
I Added it right under the last line with debug.sf.
instead of debug.sf.nobootanimation = 1 i added debug.sf.nobootanimation=1 .
it worked - there was no boot animation but i noticed my phone was doing a kind of funny [slow,lacks,randomly reboot].
so i decided to recover my phone by copying the BuildProp file from the re moveable SDcard and Pasted it in System.
when it asked to overwrite the original file i said Yes.
So i thought the BuildProp File in System was back to normal.
I Rebooted my phone and then it happened.
It shows "Sony" and when it want to go to the boot animation the screen flashes 1 time with some lagging "Sony" and shutdown.
If i want to reboot it again it will not boot up and no lights turn on.
it drains my battery while it looks like the phone is off.
I can not reboot my phone until i remove the battery and when i do the problem keeps happening.
i tried to boot in recovery mode [Volume Up , Power Button] but nothing happen only it shows "Sony" and then the ERROR with the shutdown.
i Tried to boot [Volume Down, Power Button] but if do this the phone does not do anything at all and after this i cant boot the phone until i remove the battery.
USB Debugging is on.
When i connect my phone by USB to my Computer and at the same time [Volume Up] the light becomes Blue and the phone does not Boot.
Then i start ADB in CMD [adb devices -l] but it say's there is no device.
But if i give the command to Reboot [adb reboot recovery] it say's no device.
same with [adb reboot boatloader]
if i plug in pc without [Volume Up] and use [adb devices -i] it say's " The Serial - Not authorized"
But if i give the command to Reboot [adb reboot recovery] it say's Not authorized
same with [adb reboot boatloader]
if i Fastboot in CMD it connects to my phone [fastboot devices] is gives the serial number.
if i give the command to Reboot [fastboot reboot], my phone reboots but gives the same problem.
fastboot erase userdata - Command not Allowed
fastboot erase cache - Command not Allowed
fastboot reboot-boatloader - Command not Allowed.
it looks like i,m not be able to reboot my phone in Recovery Mode or To Reset my Phone to Factory Settings.
If i connect my phone by USB to my PC and the phone light turns blue my PC shows the program Sony PC Companion.
But if i start this program it shows my phone is not connected.
It keeps doing every 25 seconds.
Also i can not open any map by PC in my phone.
I dont know what to do, is there any solution or solutions for this.
I did not Flashed any Custom Roms or Kernels so it is the Stock ROM and Kernel.
Sorry for my bad English.
I tried to describe my problem so good as i can but my English is not very good.
Can anybody Help me?
ArakisRico said:
Hey all.
This is my first Post.
I have registered myself because I've got a problem.
Last week i rooted my phone [ Sony Xperia E1 ]
I used Kingoroot for it.
i was reading some stuff about tweaking in the BuildProp file in the System folder.
i wanted to disable the boot animation on boot up.
So i Copied the BuildProp File to my Re moveable SDcard as backup and Added in
the original BuildProp file the line debug.sf.nobootanimation=1 .
I Added it right under the last line with debug.sf.
instead of debug.sf.nobootanimation = 1 i added debug.sf.nobootanimation=1 .
it worked - there was no boot animation but i noticed my phone was doing a kind of funny [slow,lacks,randomly reboot].
so i decided to recover my phone by copying the BuildProp file from the re moveable SDcard and Pasted it in System.
when it asked to overwrite the original file i said Yes.
So i thought the BuildProp File in System was back to normal.
I Rebooted my phone and then it happened.
It shows "Sony" and when it want to go to the boot animation the screen flashes 1 time with some lagging "Sony" and shutdown.
If i want to reboot it again it will not boot up and no lights turn on.
it drains my battery while it looks like the phone is off.
I can not reboot my phone until i remove the battery and when i do the problem keeps happening.
i tried to boot in recovery mode [Volume Up , Power Button] but nothing happen only it shows "Sony" and then the ERROR with the shutdown.
i Tried to boot [Volume Down, Power Button] but if do this the phone does not do anything at all and after this i cant boot the phone until i remove the battery.
USB Debugging is on.
When i connect my phone by USB to my Computer and at the same time [Volume Up] the light becomes Blue and the phone does not Boot.
Then i start ADB in CMD [adb devices -l] but it say's there is no device.
But if i give the command to Reboot [adb reboot recovery] it say's no device.
same with [adb reboot boatloader]
if i plug in pc without [Volume Up] and use [adb devices -i] it say's " The Serial - Not authorized"
But if i give the command to Reboot [adb reboot recovery] it say's Not authorized
same with [adb reboot boatloader]
if i Fastboot in CMD it connects to my phone [fastboot devices] is gives the serial number.
if i give the command to Reboot [fastboot reboot], my phone reboots but gives the same problem.
fastboot erase userdata - Command not Allowed
fastboot erase cache - Command not Allowed
fastboot reboot-boatloader - Command not Allowed.
it looks like i,m not be able to reboot my phone in Recovery Mode or To Reset my Phone to Factory Settings.
If i connect my phone by USB to my PC and the phone light turns blue my PC shows the program Sony PC Companion.
But if i start this program it shows my phone is not connected.
It keeps doing every 25 seconds.
Also i can not open any map by PC in my phone.
I dont know what to do, is there any solution or solutions for this.
I did not Flashed any Custom Roms or Kernels so it is the Stock ROM and Kernel.
Sorry for my bad English.
I tried to describe my problem so good as i can but my English is not very good.
Can anybody Help me?
Click to expand...
Click to collapse
Do a Google search for:
"Return to stock (your model number)"
Sent from my SM-S903VL using Tapatalk
LEECO LE2 X526
Lost both sim function and wifi when using ROM ressuruction remix... { Thing is battey drained out completely and when i recharged it back , no sim card were detected...only wifi was working } .
Then i installed stock rom but same issue, moreover in stock rom wifi is also not working { but only wifi works when i install nougat based rom } ... I tried lots of tips and tricks found over forum but no help.
I tried restoring qcn file by editing it with my own imei but qpst says error.
Erasing modemst1/2 file aslo didnt help.
So if any body got any idea then please do share..
9xmb said:
LEECO LE2 X526
Lost both sim function and wifi when using ROM ressuruction remix... { Thing is battey drained out completely and when i recharged it back , no sim card were detected...only wifi was working } .
Then i installed stock rom but same issue, moreover in stock rom wifi is also not working { but only wifi works when i install nougat based rom } ... I tried lots of tips and tricks found over forum but no help.
I tried restoring qcn file by editing it with my own imei but qpst says error.
Erasing modemst1/2 file aslo didnt help.
So if any body got any idea then please do share..
Click to expand...
Click to collapse
try flash stock rom eui for ur x526 5.8.19 or 5.9.21
haardx said:
try flash stock rom eui for ur x526 5.8.19 or 5.9.21
Click to expand...
Click to collapse
i installed both and and also other version eui but didnt help... wifi and dual sim are gone
..i get wifi only when using nougat rom ..so i am now using only wifi...
This works
Install the Rom S2_X520-CN-FN-IEXCNFN5902303111S-5.9.023S
... I have the x527 version ... it works with this version .... then flash a rom you like
https://devs-lab.com/download-letv-o...stock-rom.html (Le 2 (Qualcomm) Stock ROM)
i did that too...
i also tried restoring imei qcn file...but it says model mismatch....(i have x526 ver and i used same ver qcn)
Also i noticed my phone shows as x520 while in twrp recovery mode in pc..... (but phone info and pc details reads x526 while device is 0N )
Are all device shown x520 in twrp recovery ??.....and yes i use latest ver twrp.
not solved
Da-Fied said:
This works
Install the Rom S2_X520-CN-FN-IEXCNFN5902303111S-5.9.023S
... I have the x527 version ... it works with this version .... then flash a rom you like
https://devs-lab.com/download-letv-o...stock-rom.html (Le 2 (Qualcomm) Stock ROM)
Click to expand...
Click to collapse
i did that too...
i also tried restoring imei qcn file...but it says model mismatch....(i have x526 ver and i used same ver qcn)
Also i noticed my phone shows as x520 while in twrp recovery mode in pc..... (but phone info and pc details reads x526 while device is 0N )
Are all device shown x520 in twrp recovery ??.....and yes i use latest ver twrp.
Look at this:
http://forum.xda-developers.com/le-2/help/help-pro-bricked-x527-t3700958
I had the same issue. Good luck!
---------- Post added at 08:38 AM ---------- Previous post was at 08:27 AM ----------
Boot into recovery.
In twrp goto advanced >> terminal
Type the following
dd if=/dev/zero of=/dev/block/mmcblk0p14
Press enter
Type
dd if=/dev/zero of=/dev/block/mmcblk0p13
Press enter
Reboot phone.
Now your sim cards must be detected...
quasimodo88 said:
Look at this:
http://forum.xda-developers.com/le-2/help/help-pro-bricked-x527-t3700958
I had the same issue. Good luck!
---------- Post added at 08:38 AM ---------- Previous post was at 08:27 AM ----------
Boot into recovery.
In twrp goto advanced >> terminal
Type the following
dd if=/dev/zero of=/dev/block/mmcblk0p14
Press enter
Type
dd if=/dev/zero of=/dev/block/mmcblk0p13
Press enter
Reboot phone.
Now your sim cards must be detected...
Click to expand...
Click to collapse
Thanks but it doesnt help.... i already did that ....i literally tried every thing i found on the forums threads...
9xmb said:
Thanks but it doesnt help.... i already did that ....i literally tried every thing i found on the forums threads...
Click to expand...
Click to collapse
Hmm okay, for me it works. Try to make a clean install of the stock 19s rom and reboot your phone. If you have the same issue, then try again my instruction. Normally it should work.
quasimodo88 said:
Hmm okay, for me it works. Try to make a clean install of the stock 19s rom and reboot your phone. If you have the same issue, then try again my instruction. Normally it should work.
Click to expand...
Click to collapse
and remove and insert the sim
haardx said:
and remove and insert the sim
Click to expand...
Click to collapse
Nothing works...heard some where about UMT tool .... will try to write imei through it,,,,
Try to flash another baseband Or kernel for le 2.
9xmb said:
LEECO LE2 X526
Lost both sim function and wifi when using ROM ressuruction remix... { Thing is battey drained out completely and when i recharged it back , no sim card were detected...only wifi was working } .
Then i installed stock rom but same issue, moreover in stock rom wifi is also not working { but only wifi works when i install nougat based rom } ... I tried lots of tips and tricks found over forum but no help.
I tried restoring qcn file by editing it with my own imei but qpst says error.
Erasing modemst1/2 file aslo didnt help.
So if any body got any idea then please do share..
Click to expand...
Click to collapse
Follows these steps in this exact order, dont skip any even if you tried something similar. Especially in step 19. you must erase the blocks in the stated order.
1. root your rom
2. enable usb debugging
3. install minimal adb on your computer, goto the folder you installed it in, hold shift then right click, select open command prompt here, connect phone to pc.
4. in command window, enter the following ( each line followed by pressing enter)
5. adb shell
6. su
7. grant su request on phone screen
7b. command prompt should look similar to "[email protected]_s2_na:/ #" without the quotes depending on the version of your phone.
8. on command prompt type
9. ls -al /dev/block/platform/soc.0/7824900.sdhci/by-name/
10. this lists out all your phones partitions ( not really necessary if you are using an le 2 but it's a good practice to confirm for the following steps)
11. confirm the following entries appear in the list
11a. fsg -> /dev/block/mmcblk0p18
11b. modemst1 -> /dev/block/mmcblk0p13
11c. modemst2 -> /dev/block/mmcblk0p14
11d. these three entries are where the phone stores the imei, wifi mac address, and Bluetooth address.
12a. if they don't then... if you are technical enough you cant edit this guide to suit your needs else STOP!!!
12b. if they do then you are all good. continue
13. on the command prompt enter
13a. dd if=/dev/block/mmcblk0p18 of=/sdcard/fsg.bin
13b. dd if=/dev/block/mmcblk0p13 of=/sdcard/modemst1.bin
13c. dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst2.bin
14. this will backup the partitions and create 3 files on your sdcard 'fsg.bin' 'modemst1.bin' and 'modemst2.bin'
15. copy these to a safe place on your computer
16. this part restores your backup, on the command prompt enter
16a. dd if=/sdcard/fsg.bin of=/dev/block/mmcblk0p18
16b. dd if=/sdcard/modemst1.bin of=/dev/block/mmcblk0p13
16c. dd if=/sdcard/modemst2.bin of=/dev/block/mmcblk0p14
16d. reboot
17. after your phone reboots repeat steps 5 & 6
18. cross fingers
19. the next step will zero out (erase) the partitions so your phone can hopefully recreate them with the correct data
19. in the command prompt enter the following in this exact order
19a. dd if=/dev/zero of=/dev/block/mmcblk0p18
19b. dd if=/dev/zero of=/dev/block/mmcblk0p14
19c. dd if=/dev/zero of=/dev/block/mmcblk0p13
20. without rebooting your phone try to check the imei by dialing *#06#
If this doesn't work you can try qcn restore with qpst, but note that in order to restore a qcn backup you MUST first zero out fsg, modemst1/2
Side note, you might be able to make your wifi work in stock by flashing overload2.3 miui kernel, I never figured out why this is.
Also with a root explorer check /persist folder for the following files in the pics
i did as you said..... i checked in root explorer for the following files but i could only find the files from pic 1 .......
i tried restoring .qcn file but it says received invalid command from phone..
yes i wiped .fsg first and connected phone in 901D port ...
Le2 x526 baseband unknown
brother is your phone repaired, i have same issue, please help me