After buying Lenovo K6, it was okay with the marshmallow firmware, then I recieved the Nougat update and I didn't really like it, So I installed AOKP custom rom and then I wanted to get back to the stock firmware, which is mm.
I flashed it fine but the second SIM is not working anymore, it says " No service | Orange EG "
It's detected but it doesn't really work, any help please ??
did u checked baseband
i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
@ilia1998, Oh my god .. you saved my life, I don't know how to thank you, trust me you're a life savior!!
Thanks a lot <33333
no problem bro...
Now VOLTE isuue
ilia1998 said:
i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
Click to expand...
Click to collapse
after doing this SIM 2 is working but now volte stopped working. What should I do now?
:crying::crying::crying::crying::crying:
Rkladwal said:
after doing this SIM 2 is working but now volte stopped working. What should I do now?
:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
i don't know about volte..which rom are you using?
working now
ilia1998 said:
i don't know about volte..which rom are you using?
Click to expand...
Click to collapse
Thanks for your response. I flashed stock Rom again and do this procedure again. Now both SIMs + VOLTE is working.
Rkladwal said:
Thanks for your response. I flashed stock Rom again and do this procedure again. Now both SIMs + VOLTE is working.
Click to expand...
Click to collapse
How did you fixed VoLte ? i am still not able to access VoLte i flashed Stock Rom also...
Hi , Many many thanks... Much appreciated. I have been trying it by re installing approx last 6month, and elapsed much time... NOW SUCCESS !!!! Thanks xda-developers.
ilia1998 said:
i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
Click to expand...
Click to collapse
I had a strange problem with my Lenovo K6 Power. It was working with 4G network only. In my place I have installed 2G network booster for better signal reception but my mobile was unable to get 2G network. I tried various solutions from resetting the phone to flashing older Marshmallow ROM but nothing works. Finally I arrive at this page and follow these steps and bingo! My mobile get full network and become useful once again! Thank you so much...!:good::good::good:
Lenovo k6 note sim2 and volte fix
Hi 2 all today I'll tell u an easy way to fix volte in lenovo k6 note so to fix this we have to flash stock rom here is the link for that --> mail.me after flashing stock rom u may get volte if u dont get volte do not worry just flow the steps
*Open ur dialpad type *#4636#*#* it will open engineering mode go to phone information and select lte only option and down there press button refresh and update button now come out to home screen and again open dialer and type ####862# it will open easy image there u have to select in(##) India and it will update ur system and u will get volte option enabled..have a gud day guys any doubts mail me email: [email protected] I will be in touch with u guys tq
After following the procedure I am not left with a bigger problem, the phone can't read simcard, the imei is blank and baseband version unknown. Anyone with a hint on how to restore the imei or another way to get my phone back to reading the simcard?
ilia1998 said:
i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
Click to expand...
Click to collapse
i tried these commands.....after that my phone serial number says unknown and imei number showing 0
please help me sir....any sim is not supporting anymore in phone....
Help me
Im using k6 note 4gb ram.
Sim2 error and i cant find any solution, baseband not showing error, booth imei also showed normal.
Please help me.
Pict attach
If you would have been near me i would have hugged and kissed you. It worked like a charm. After struggling for so many hours and watching umpteen videos i happened to come across your site. Thank You very much.
ilia1998 said:
i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
Click to expand...
Click to collapse
thanks
thanks
cupliz said:
Im using k6 note 4gb ram.
Sim2 error and i cant find any solution, baseband not showing error, booth imei also showed normal.
Please help me.
Pict attach
Click to expand...
Click to collapse
I have the same problem, flashing stock rom so many times but sim2 not working "no services"
i try this too :
" adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot"
but not solved the problem......trying with ####862# then select my country Code then also not solved the problem.
anyone in here can give me the solution ?
Me2018 said:
After following the procedure I am not left with a bigger problem, the phone can't read simcard, the imei is blank and baseband version unknown. Anyone with a hint on how to restore the imei or another way to get my phone back to reading the simcard?
Click to expand...
Click to collapse
restore the qcn file with QFIL tool u can resote ur imei numbers
https://forum.xda-developers.com/k6-power/help/qcn-file-lenovo-k6-note-t3663024
i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
Click to expand...
Click to collapse
I got my baseband unknown and iemi 0 because of this.
somehow i got someone's qcn file of k6 power and flashed it through QFIL, it had someone else's imei number, then i replaced my imei with something called WriteDuelIMEI application, at first it wasn't showing up COM port then i rooted my phone with magisk, and executed the following commands from adb
Code:
adb shell
su
setprop sys.usb.config diag,adb
and bingo, it showed COM port and I wrote both my IMEI numbers and clicked start, it successfully did put both IMEI numbers but still sim cards were off and no network.
Then on next day, I used Lenovo Moto smart Assistant and flashed again with the instructions from it.
after flashing and rebooting, it was showing both of my sim networks.
Though volte isn't working in my phone and never worked before for some reason.
Still it's good enough to make some calls thorugh 2G or 3G networks.
Hope it helps someone.
Related
Guys had some network problem and hence typed *#*#4636#*#* in the dial pad and went into the settings. But it was the worst mistake andi somehow set the radio band to USA and now cant revert back.The first sim has no network. What do i do?
-I am running stock android lolipop
Same Problem
I too did the same mistake. Can anyone give us solution for this problem?
TEJASMN said:
Guys had some network problem and hence typed *#*#4636#*#* in the dial pad and went into the settings. But it was the worst mistake andi somehow set the radio band to USA and now cant revert back.The first sim has no network. What do i do?
-I am running stock android lolipop
Click to expand...
Click to collapse
kabeeradam said:
I too did the same mistake. Can anyone give us solution for this problem?
Click to expand...
Click to collapse
Remove SIM(s)
From fastboot mode. Try the following command.
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Reboot and put SIM(s) back!
Sent from my XT1562 using Tapatalk
Thank you, This really worked.
Could you please tell in detail. How to use commands in fastboot mode. Via windows or what?
kumeipark said:
Remove SIM(s)
From fastboot mode. Try the following command.
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Reboot and put SIM(s) back!
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
this should put sticky!
kumeipark said:
Remove SIM(s)
From fastboot mode. Try the following command.
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Reboot and put SIM(s) back!
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
U just saved my Life (actually the hassle of going to moto service center)!!! Thanks.
---------- Post added at 08:59 AM ---------- Previous post was at 08:47 AM ----------
sudeepsurajsingh said:
Could you please tell in detail. How to use commands in fastboot mode. Via windows or what?
Click to expand...
Click to collapse
Just elaborating the steps.
1. Download & install Moto X Play drivers from moto website (Compulsory)
2.You need to run ADB commands : There are 2 options
a. Use Minimal ADB & Fastboot --- This is what i prefer - as it's hardly 2 MB & serves the purpose.
Link : http://forum.xda-developers.com/showthread.php?t=2317790
b. OR download the entire andriod SDK - which is > 1 GB
3. In the command prompt of minimal ADB, type "fastboot devices" to check for the connected devices
4. If your device is shown, then type "fastboot reboot" to reboot your device to fast boot
5. Then run the commands in sequence:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
6. Reboot and put SIM(s) back!
That's all!!!
Thanks to @kumeipark
adithya7187 said:
U just saved my Life (actually the hassle of going to moto service center)!!! Thanks.
---------- Post added at 08:59 AM ---------- Previous post was at 08:47 AM ----------
Just elaborating the steps.
1. Download & install Moto X Play drivers from moto website (Compulsory)
2.You need to run ADB commands : There are 2 options
a. Use Minimal ADB & Fastboot --- This is what i prefer - as it's hardly 2 MB & serves the purpose.
Link : http://forum.xda-developers.com/showthread.php?t=2317790
b. OR download the entire andriod SDK - which is > 1 GB
3. In the command prompt of minimal ADB, type "fastboot devices" to check for the connected devices
4. If your device is shown, then type "fastboot reboot" to reboot your device to fast boot
5. Then run the commands in sequence:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
6. Reboot and put SIM(s) back!
That's all!!!
Thanks to @kumeipark
Click to expand...
Click to collapse
****Before Step 3 and after step 2, In ADB command prompt, typr "Connect device" to connect first and then check for connected device.
On my OnePlus 2,
I changed the LTE band from service menu, & faced issues w.r.t 2G/3G networks not being recognized.
So following these fastboot commands, resulted in problem with SIM-Slot-2, not recognizing any network, Phone can detect the sim & network though, it just doesn't latch on to the network.
SIM-Slot-1, is working fine though, connecting to 2G/3G/4G.
Any help ?
Yes, restore backup of modem partitions.
You made a backup, right?
dreinulldrei said:
Yes, restore backup of modem partitions.
You made a backup, right?
Click to expand...
Click to collapse
I did not made any backup !
Can you provide me the necessary modem .zip file !
Nope, because the modem partitions very likely containt unique config data (e.g. IMEI, different for EVERY phone). This is why you should make backups...
Won't help here. Good luck that it's not a brick now...
osr.arora said:
I did not made any backup !
Can you provide me the necessary modem .zip file !
Click to expand...
Click to collapse
You are on the wrong forum, This is the moto x play's forum. Go to the Oneplus 2 forum
dreinulldrei said:
Nope, because the modem partitions very likely containt unique config data (e.g. IMEI, different for EVERY phone). This is why you should make backups...
Won't help here. Good luck that it's not a brick now...
Click to expand...
Click to collapse
Will reverting to Stock ROM, be of any help ?
osr.arora said:
Will reverting to Stock ROM, be of any help ?
Click to expand...
Click to collapse
No, i tried it, had a ROM backup with properly working modem partitions, restored, and no luck.
Please read my previous reply again. Thank you.
dreinulldrei said:
Please read my previous reply again. Thank you.
Click to expand...
Click to collapse
So the only two working options are:
1. Reflash the modem firmware from fastboot
2. Backup the working ROM partitions and restore if you manage to change the band?
The only options for messing with modem partitions are:
1. Backup your modem and related partitions.
2. MESS AROUND.
3. Restore from backup
Whatever you do, do a backup first. You can NOT recover modem data from stock firmware files.
dreinulldrei said:
The only options for messing with modem partitions are:
1. Backup your modem and related partitions.
2. MESS AROUND.
3. Restore from backup
Whatever you do, do a backup first. You can NOT recover modem data from stock firmware files.
Click to expand...
Click to collapse
Thanks for answering. Is the backup/restore solution tried and tested, meaning it's 100% working? Also, does the Partitions Backup app suffice for this?
First rule as always: Your warranty is now void and if you brick your device we'll laugh at you.
I can't say if it's 100% safe; I bet there are devices where you can backup the baseband config data ("modem" etc.), but can't re-flash them as the partitions by definition are protected. So there might be ways to kill them (by using functions that modify them and where you can't directly re-flash them). On my Moto X Play, I can erase and re-flash "modemst1" and "modemst2". But I really prefer just erasing as - to my understanding - erasing only clears certain parts of the config, but does not affect the IMEI data. I would suspect a wrong flash could completely kill your modem and thus render the phone a WiFi only device.
I'd still recommend doing a backup of such partitions the day you buy and root the phone. Can't be wrong.
I would recommend FlashFire as it's doing both, backing them up and re-flashing them.
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Flash Latest NON-HLOS.bin before flashing any volte ROM.
Flash through fastboot
File link
https://drive.google.com/file/d/0B8Vodzmhc0GlXzdtOUFjb29EOFU/view
Extract .zip
Copy NON-HLOS.bin in adb folder
Open command prompt here
Connect phone into fastboot mode
Type command
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Wait till process done.
Disconnect phone
Remove battery and insert again
Goto twrp recovery.
Install any volte enabled ROM.
Enjoy.:good:
OEM unlock command not found
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
nischait said:
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Click to expand...
Click to collapse
nithin1664 said:
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
Click to expand...
Click to collapse
Try without using 0x1ebf and report.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Yogesh1969 said:
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Click to expand...
Click to collapse
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
nischait said:
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
Click to expand...
Click to collapse
I couldnt find the ygdp version of Cynogen, any way I found a way from youtube which solved my problems.
Link : https://www.youtube.com/watch?v=2Gpz65r2pNM
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
For drivers problem install pdanet. And you can refer to the youtube video link (above post) if you want for all needs.
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
Getting your device connected is a very important stage, whether it is system,recovery or fastboot. From what I read , you can connsct through fasatboot, since you flashed cyanogen. Just flash TWRP 3.2.1 or so which is the latest, through fastboot:
fastboot flash recovery twrp.3.2.1 .img ( Remember the spaces, the name twrp.xxx.img should be same as you downloaded. If flash is successful, you can see twrp when you boot to recovery. Then flash supersu file and/or whichever rom you want.
Sorry for late answers.
I was lil busy and sorry for wrong address also.
You could get it from firmwarefile.com
I can't post link here but select yu yureka plus variant and download oldest CBP
I recently ran into the Unknown baseband problem on my G900I. It happended randomly. I couldn't call, and the phone baseband was "unknown" (the modem was failing to initialize). The phone randomly rebooted when the screen was off, and shutdown didn't work (look a very long time and would reboot.)
My attempts:
1. I didn't have an EFS/modemst1/modemst2 backup. Silly me, if I'd had those backups I would have saved a bunch of time! I did a new backup anyway just to be safe (who knows?). Restoring my new backup did nothing (apparently this works in some cases).
2. I was already on stock. Naturally I reflashed stock to unroot, but when that didn't fix it I did a full factory reset. The modem was still not working, so I even went all the way and did a NAND erase all + PIT + clear EFS in Odin. The modem still did not work!
3. EFS Professional could not connect to the modem ("send SPC" didn't work at all, rejected by phone error). In QPST I got "disk error while writing to file" when trying to backup the qcn. In retrospect, these methods probably failed because the modem had been failing to initialize at boot, so these tools weren't able to communicate with the modem. Also note that the Service Mode menu was completely blank, but the USB menu to enable modem diagnostics still worked.
At this point I was close to giving up and about to start finding a mobile phone repair shop who could fix this (I was thinking that I needed a z3c box), until I came across some threads which suggested that they fixed their unknown baseband problem by erasing modemst1 and modemst2. I didn't want to try this because I read somewhere that recent newer Samsung devices stored the IMEI in these partitions, and NOT in the EFS. (don't think this is true anymore...) I had already tried clearing the EFS in #2.
Whilst most of these threads were about non-Samsung devices (they used fastboot erase modemst1, but we don't have fastboot on Samsung), it can still be done in TWRP, see: https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
After erasing modemst1/modemst2, I rebooted, and WOW my modem now works! SIM is detected!! :good:
So... now I'm confused why people suggest to backup/restore the modemst1/modemst2 partitions in the first place, when erasing those partitions actually solved my problem - and without loosing my IMEI number/BT or Wi-fi MAC! EFS Professional and QPST tools now work as expected. I now wonder where the IMEI number really is stored?
Hope this helps someone!
Notes:
(NAND erase all doesn't actually clear everything. Perhaps there are multiple NAND chips or something)
very helpful, tnx!!!
dg1010 said:
very helpful, tnx!!!
Click to expand...
Click to collapse
Hi,
If it was helpful for you it would be better if you instead of saying "tnx" press his "Thanks button".
Regards
Sent from my SM-G900F using Tapatalk 2
Many40 said:
Hi,
If it was helpful for you it would be better if you instead of saying "tnx" press his "Thanks button".
Regards
Sent from my SM-G900F using Tapatalk 2
Click to expand...
Click to collapse
done
dg1010 said:
done
Click to expand...
Click to collapse
Not mine! Press Thanks button of navcar and mine remove please
Sent from my SM-G900F using Tapatalk 2
Will this work to fix the issue that I am having with Oreo roms on my s5 kltespr [kltedv]?
I am unable to get a signal once I flash any Oreo ROM. The signal lasts for a few seconds after first boot, then its gone.
SolarMaximus said:
Will this work to fix the issue that I am having with Oreo roms on my s5 kltespr [kltedv]?
I am unable to get a signal once I flash any Oreo ROM. The signal lasts for a few seconds after first boot, then its gone.
Click to expand...
Click to collapse
It worked!! It worked!! Thank you!!
7f sth
[
After erasing modemst1 & modemst2, u have to restore the efs partition
For some reason this doesn't work anymore
Worked for me, thanks a ton @navcar!
My issue was a zeroed IMEI on a G900F running LOS 14.1.
I made a backup of the broken EFS first to avoid breaking the poor thing even further. On a rooted adb shell:
Code:
klte:/data/asd # dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=efs.bak
klte:/data/asd # dd if=/dev/block/bootdevice/by-name/modemst1 of=modemst1.bak bs=4096
klte:/data/asd # dd if=/dev/block/bootdevice/by-name/modemst2 of=modemst2.bak bs=4096
klte:/data/asd # find /efs -exec ls -l {} \; > efs-permissions
And pulled the generated files plus the whole /efs dir. The last command is to keep a list of the permissions in /efs.
To modify modemst1 and modemst2 I used the TWRP terminal. dd complained about no space left. Then rebooted to system and my IMEI was back
Question: what if I have the imei present, but no signal? Because that's my case. I can't get the signal to work on Oreo,:crying:
Thank you!!! my problem is solved!! more power xda team!
I've the same problem on my J7 Prime(SM-610F).
IMEI Unknown
Baseband Unknown
No SIM card detected as a result.
Should I now try all of those above-mentioned methods? Or just follow the last one— erasing modemat1 and modemst2???
I need help, thank you!
I have a 900P, they sold me with a LL 5.01 version, I upgraded in past to Ressurection remix 7.1.2 and the baseband was not working. I solved the problem uploading (after a recovery wipe) the stock 6.01 G900PVPS3CQD1, then TWRP, then wipe again and again Ressurection Remix, than I tried also Lineage OS 7.1.2.
The phone worked for about 5-6 months, than no signal more. I flashed again the stock 6.01 and it tells me "invalid SIM card", the IME is present, also baseband show its version under info.
I flashed than TWRP and typed in its terminal the commands I've found here:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
It saif not enough space but it looks it copied around 3MB. I have no idea what this commands do. I rebbot the phone and nothing changed. Then I continue to read and I typed the following:
dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=efs.bak
dd if=/dev/block/bootdevice/by-name/modemst1 of=modemst1.bak bs=4096
dd if=/dev/block/bootdevice/by-name/modemst2 of=modemst2.bak bs=4096
find /efs -exec ls -l {} \; > efs-permissions
it looks it did all sucessfully but nothing solved the problem. I'm not a linux expert, I don't know how to copy these backup files to my pc ad eventually look on them, and what to edit and how to upload.
Please someone can kindly write a guide, I see someone has success here, not me, my baseband doen't work. Thank you a lot!!
Hello Friend. I have a samsung g900h, with operator rom, I had battery problems so I made the wipe cache. Question that was left without imei, and flashing a stock rom, still without imei. Could you place the tutorial or the steps you did to solve it? I suspect that I have the same problem, since yesterday the imei appeared for a few hours and then left again. I would appreciate your help, greetings!
jorgecuello90 said:
Hello Friend. I have a samsung g900h, with operator rom, I had battery problems so I made the wipe cache. Question that was left without imei, and flashing a stock rom, still without imei. Could you place the tutorial or the steps you did to solve it? I suspect that I have the same problem, since yesterday the imei appeared for a few hours and then left again. I would appreciate your help, greetings!
Click to expand...
Click to collapse
I already have twrp, the problem is that now when trying to write the commands in modemst1 I get "no such file or directory". I clarify that I am not root, is it necessary?
jorgecuello90 said:
I already have twrp, the problem is that now when trying to write the commands in modemst1 I get "no such file or directory". I clarify that I am not root, is it necessary?
Click to expand...
Click to collapse
If you aren't root you can't do nothing. Or you flash a rootable ROM, or you use terminal in TWRP
---------- Post added at 06:02 PM ---------- Previous post was at 05:52 PM ----------
I tried also to format mmcblk0p3 with mke2fs under TWRP but it hangs when writing..
Nothing changes, IMEI never lost, sim if inserted is not recognized, but the symbol is different than if not present at all.. so I suppose not an hardware fault.
Tried EFS professional, not working because open box doesn't give find command, but it is activated. I tried really all..
Barabba11 said:
If you aren't root you can't do nothing. Or you flash a rootable ROM, or you use terminal in TWRP
---------- Post added at 06:02 PM ---------- Previous post was at 05:52 PM ----------
I tried also to format mmcblk0p3 with mke2fs under TWRP but it hangs when writing..
Nothing changes, IMEI never lost, sim if inserted is not recognized, but the symbol is different than if not present at all.. so I suppose not an hardware fault.
Tried EFS professional, not working because open box doesn't give find command, but it is activated. I tried really all..
Click to expand...
Click to collapse
It's strange what happens to me. Now I have a signal, the imei and the baseband appear. The same thing happened to me a few days ago, and then I lost it again. For now I'm still waiting for the imei or signal to go.
I add that I flashed a stock rom last night, but it did not have imei. This morning when I got up there was a signal and I could see the imeil. Rare
No Such File or Directory.
navcar said:
I recently ran into the Unknown baseband problem on my G900I. It happended randomly. I couldn't call, and the phone baseband was "unknown" (the modem was failing to initialize). The phone randomly rebooted when the screen was off, and shutdown didn't work (look a very long time and would reboot.)
My attempts:
1. I didn't have an EFS/modemst1/modemst2 backup. Silly me, if I'd had those backups I would have saved a bunch of time! I did a new backup anyway just to be safe (who knows?). Restoring my new backup did nothing (apparently this works in some cases).
2. I was already on stock. Naturally I reflashed stock to unroot, but when that didn't fix it I did a full factory reset. The modem was still not working, so I even went all the way and did a NAND erase all + PIT + clear EFS in Odin. The modem still did not work!
3. EFS Professional could not connect to the modem ("send SPC" didn't work at all, rejected by phone error). In QPST I got "disk error while writing to file" when trying to backup the qcn. In retrospect, these methods probably failed because the modem had been failing to initialize at boot, so these tools weren't able to communicate with the modem. Also note that the Service Mode menu was completely blank, but the USB menu to enable modem diagnostics still worked.
At this point I was close to giving up and about to start finding a mobile phone repair shop who could fix this (I was thinking that I needed a z3c box), until I came across some threads which suggested that they fixed their unknown baseband problem by erasing modemst1 and modemst2. I didn't want to try this because I read somewhere that recent newer Samsung devices stored the IMEI in these partitions, and NOT in the EFS. (don't think this is true anymore...) I had already tried clearing the EFS in #2.
Whilst most of these threads were about non-Samsung devices (they used fastboot erase modemst1, but we don't have fastboot on Samsung), it can still be done in TWRP, see: https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
After erasing modemst1/modemst2, I rebooted, and WOW my modem now works! SIM is detected!! :good:
So... now I'm confused why people suggest to backup/restore the modemst1/modemst2 partitions in the first place, when erasing those partitions actually solved my problem - and without loosing my IMEI number/BT or Wi-fi MAC! EFS Professional and QPST tools now work as expected. I now wonder where the IMEI number really is stored?
Hope this helps someone!
Notes:
(NAND erase all doesn't actually clear everything. Perhaps there are multiple NAND chips or something)
Click to expand...
Click to collapse
brother I have done this but facing this issue
No Such file or directory .
my phone is rooted.
Thanks to xda member @Shooting Star Max for the original post for this solution
If your phone is always rebooting into recovery, and the only way to boot normally is by using the bootloader, follow these instructions:
Some users recommend removing your SD before doing the following as incorrectly formatted SD Cards could cause the phone to boot into recovery instead of booting normally.
1) Boot into TWRP recovery.
2) Plug your Cedric into your computer (which needs to have drivers and fastboot installed).
3) Open a command prompt window and type:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/misc misc.img
This will make a backup of the misc partition just in case.
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
5) Your Cedric will boot normally again
TheFixItMan said:
Thanks to xda member @Shooting Star Max for the original post for this solution
If your phone is always rebooting into recovery, and the only way to boot normally is by using the bootloader, follow these instructions:
1) Boot into TWRP recovery.
2) Plug your Cedric into your computer (which needs to have drivers and fastboot installed).
3) Open a command prompt window and type:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/misc misc.img
This will make a backup of the misc partition just in case.
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
5) Your Cedric will boot normally again.
Click to expand...
Click to collapse
I did the procedure and everything went back normal.
I did a backup with the twrp and when I went to restore and go back everything as before, it will continue to restart in the bootloader and I must confirm with the power key to boot the system.
I tried to repeat the procedure but nothing to do does not work anymore.
Some help thank you
masterdex said:
I did the procedure and everything went back normal.
I did a backup with the twrp and when I went to restore and go back everything as before, it will continue to restart in the bootloader and I must confirm with the power key to boot the system.
I tried to repeat the procedure but nothing to do does not work anymore.
Some help thank you
Click to expand...
Click to collapse
As long as you have fully booted your phone before trying again I don't see why you couldn't repeat it
Or reflash the recovery and try again
[/ATTACH]
TheFixItMan said:
As long as you have fully booted your phone before trying again I don't see why you couldn't repeat it
Or reflash the recovery and try again
Click to expand...
Click to collapse
Still tried on minimal adb and phower shell does not work. I attach pictures.
masterdex said:
[/ATTACH]
Still tried on minimal adb and phower shell does not work. I attach pictures.
Click to expand...
Click to collapse
Make sure adb is connected properly
Code:
adb kill-server
adb devices
Your device should be displayed as connected & should be the only device listed
If it still doesn't work then the only solution I can think of is restoring your stock firmware by fastboot - do not flash the bootloader part of the firmware
TheFixItMan said:
Make sure adb is connected properly
Code:
adb kill-server
adb devices
Your device should be displayed as connected & should be the only device listed
If it still doesn't work then the only solution I can think of is restoring your stock firmware by fastboot - do not flash the bootloader part of the firmware
Click to expand...
Click to collapse
Yes is connected. If only I could find the firmware for my XT1675 16gb / 2gb single sim model.
masterdex said:
Yes is connected. If only I could find the firmware for my XT1675 16gb / 2gb single sim model.
Click to expand...
Click to collapse
Same phone as mine & Iv never had this problem - I use lineageos - try flashing that
Other than that I can't suggest anything else
Thank you anyway. They persistently waited for Lenovo to provide the tools and release the firmware for my model that is currently unavailable.
I've tried all the constructions here, but they all have background noise during calls and fixed gps in over a minute and it's not accurate.
Do you have my own model with the same features?
masterdex said:
Thank you anyway. They persistently waited for Lenovo to provide the tools and release the firmware for my model that is currently unavailable.
I've tried all the constructions here, but they all have background noise during calls and fixed gps in over a minute and it's not accurate.
Do you have my own model with the same features?
Click to expand...
Click to collapse
I have the XT165 running lineageos
No problems with calls - iv changed the build.prop to edit call volume (see my last post in the lineageos thread)
No problem with gps
You could try running these commands in fastboot as this was a fix for gps in past moto devices
Code:
fastboot erase modemst1
fastboot erase modemst2
Okay, now I'm just trying to build stock, if I think I bought the phone, just the time to get home and unlock bootloader and put custom rom, I almost do not know the functions of building stock. Now I see how it behaves and I guess if I install Lineage again and make all the corrections you've suggested very kindly thanks.
TheFixItMan said:
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
Click to expand...
Click to collapse
Clearing the whole misc partition may be overkill and cause other issues. In the LG threads they currently suggest clearing only the first 256 bytes.
ST Dog said:
Clearing the whole misc partition may be overkill and cause other issues. In the LG threads they currently suggest clearing only the first 256 bytes.
Click to expand...
Click to collapse
This works fine for our users - its been tested & no one has reported any issues
TheFixItMan said:
This works fine for our users - its been tested & no one has reported any issues
Click to expand...
Click to collapse
That's cool. Just a thought.
Different OEs put different stuff there, but really no reason to clear it all if only part is the problem.
And one never knows when they might change the usage.
Oh, and masterdex above appears to have had some issue.
ST Dog said:
That's cool. Just a thought.
Different OEs put different stuff there, but really no reason to clear it all if only part is the problem.
And one never knows when they might change the usage.
Oh, and masterdex above appears to have had some issue.
Click to expand...
Click to collapse
It worked for him but then he restored old phone backups - I recommended flashing lineageos from scratch
Nothing to do, I tried again to download Lineage, make a clean installation by deleting all the entries in the TWRP, configuring the phone restarted in recovery, and rewriting the procedure, the result does not change always restarts the bootloader.
At this point you only have to install the firmware from scratch, someone knows where to find firmware stock model XT1675 16gb storage and 2 gb sin ram single sim?
masterdex said:
Nothing to do, I tried again to download Lineage, make a clean installation by deleting all the entries in the TWRP, configuring the phone restarted in recovery, and rewriting the procedure, the result does not change always restarts the bootloader.
At this point you only have to install the firmware from scratch, someone knows where to find firmware stock model XT1675 16gb storage and 2 gb sin ram single sim?
Click to expand...
Click to collapse
This is rom stock Cedric work on XT1675 16 gb 2 gb ram installed on Motog5 brand Tim :https://www.youtube.com/watch?v=EMyaDv1lcYg
TheFixItMan said:
I have the XT165 running lineageos
No problems with calls - iv changed the build.prop to edit call volume (see my last post in the lineageos thread)
No problem with gps
You could try running these commands in fastboot as this was a fix for gps in past moto devices
Code:
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I tried to give these commands fastboot but the result and that when I restart the phone no longer sees the sim and I have to reinstall the original firmware with fastboot. Tried twice the same result, are you sure you have the right commands?
My Cedric is listed on the adb devices code when it's turned on. But if I restart to twrp then it's not listed. Now how can I perform this
Sent from my Motorola Moto G 2014 using XDA Labs
---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------
It is listed when I turned off the Mtp. But when I give the first command to backup the misc folder I get
[?] /dev/block/platform/soc/7824900.sdhci/by-name/misc: 1048576/?.
Sent from my Motorola Moto G 2014 using XDA Labs
---------- Post added at 12:17 PM ---------- Previous post was at 11:57 AM ----------
Again solved it. I just backed up the misc in twrp itself by copying the misc file to the /sdcard using the inbuilt file manager of twrp. Then tried the second command. It worked like charm. Thank you
Sent from my Motorola Moto G 2014 using XDA Labs
Perfect!
Thank you, TheFixItMan! I have an XT1672, Android 7.0 Stock Rom, and I was having this problem after trying the November update via OTA. The correction steps worked perfectly! Happy New Year!
Thanks hope to try this tonight, have you had feedback that this works? Thanks
Hey there,
so my problem is, that I just cant unlock my bootloader anymore.
I dont know what to do.
The phone just shows the xiamoi logo for one second and then black screen.
Only fastboot mode does work.
Cmd says remote: oem unlock is not allowed. YES I know that I havent activated developer settings but I cant, because I wiped the system and cant do anything. And how to flash stock rom, when I havent got bootloader permissions.
Qfil and so on doestn work either.
Please respond asap.
heya
only you need to change the partition, ONLY WORK IF YOU DONT ERASE THE 2 SYSTEM PARTITIONS (system_a and system_b), to make that you need to follow instructions:
1.- open CMD in platform tools
2.- in CMD type Fastboot getvar current-slot
3(1).-if the CMD say current-slot:_a you need to type Fastboot set_active b
3(2).-if the CMD say current-slot:_b you need to type Fastboot set_active a
4.- reboot the phone typing fastboot reboot, and Ready!!!
Moratilla3 said:
only you need to change the partition, ONLY WORK IF YOU DONT ERASE THE 2 SYSTEM PARTITIONS (system_a and system_b), to make that you need to follow instructions:
1.- open CMD in platform tools
2.- in CMD type Fastboot getvar current-slot
3(1).-if the CMD say current-slot:_a you need to type Fastboot set_active b
3(2).-if the CMD say current-slot:_b you need to type Fastboot set_active a
4.- reboot the phone typing fastboot reboot, and Ready!!!
Click to expand...
Click to collapse
thanks for your reply, I typed it and it said active slot a, I typed... set_active b ...
I restarted it and I got black screen again... the problem is I cant flash software on it because I cant unlock the bootloader
klapfi said:
Hey there,
so my problem is, that I just cant unlock my bootloader anymore.
I dont know what to do.
The phone just shows the xiamoi logo for one second and then black screen.
Only fastboot mode does work.
Cmd says remote: oem unlock is not allowed. YES I know that I havent activated developer settings but I cant, because I wiped the system and cant do anything. And how to flash stock rom, when I havent got bootloader permissions.
Qfil and so on doestn work either.
Please respond asap.
Click to expand...
Click to collapse
Go to: "Settings" -> "Developer options" oem option activate ?
klapfi said:
Hey there,
so my problem is, that I just cant unlock my bootloader anymore.
I dont know what to do.
The phone just shows the xiamoi logo for one second and then black screen.
Only fastboot mode does work.
Cmd says remote: oem unlock is not allowed. YES I know that I havent activated developer settings but I cant, because I wiped the system and cant do anything. And how to flash stock rom, when I havent got bootloader permissions.
Qfil and so on doestn work either.
Please respond asap.
Click to expand...
Click to collapse
Did you try Mi unlock?
http://en.miui.com/unlock/
You must create a mi account and need to use a chinese proxy to validate registration
I solved it myself. As mentioned I had no OS installed so there was no way to activate developer settings. I couldtn enter edl mode via fastboot so I used testpoint to solve my problem. I then flashed it via Miflash and the phone works now fine :good:
klapfi said:
I solved it myself. As mentioned I had no OS installed so there was no way to activate developer settings. I couldtn enter edl mode via fastboot so I used testpoint to solve my problem. I then flashed it via Miflash and the phone works now fine :good:
Click to expand...
Click to collapse
Before flashing a rom and rom custom is better know how to return to initial configuration
klapfi said:
I solved it myself. As mentioned I had no OS installed so there was no way to activate developer settings. I couldtn enter edl mode via fastboot so I used testpoint to solve my problem. I then flashed it via Miflash and the phone works now fine :good:
Click to expand...
Click to collapse
can you tell how to do testpoint?
Balasubramaniyan said:
can you tell how to do testpoint?
Click to expand...
Click to collapse
Just go on youtube and search for testpoint xiamoi mi a1, I did the same and it worked for me.
Good luck
If you can access Fastboot. THIS WILL ERASE ALL OF YOUR DATA
1. Enter Fastboot Mode > Make sure drivers are installed correctly
2. Enter "fastboot oem edl" > > Ignore Error > Your phone notification led should now blink.
3. Use MiFlash to flash the fastboot ROM.
klapfi said:
I solved it myself. As mentioned I had no OS installed so there was no way to activate developer settings. I couldtn enter edl mode via fastboot so I used testpoint to solve my problem. I then flashed it via Miflash and the phone works now fine :good:
Click to expand...
Click to collapse
Is there a way you could be more specific on what you do please? I don't understand what do you have to do after the testpoint, how do you use miflash to reflash the rom? Please
JFGR11 said:
Is there a way you could be more specific on what you do please? I don't understand what do you have to do after the testpoint, how do you use miflash to reflash the rom? Please
Click to expand...
Click to collapse
When your phone is in testmode you are able to flash stock firmware via Miflash. Download the stock firmware in the internet just google it.
You have to install Miflash. Open it connect phone in fastboot (testpoint). Then select the downloaded firmware in Miflash and flash it.
There are many videos on youtube how to flash with miflash.
Mi A1 show on PC screen failed ( OEM unlock is not allowed)
And not on my device
guys can we unlock bootloader from site : http://en.miui.com/unlock/ ? anybody tried that ?
burimi007 said:
guys can we unlock bootloader from site : http://en.miui.com/unlock/ ? anybody tried that ?
Click to expand...
Click to collapse
no, our device is android one, so bootloader only need a fastboot command and no code/waiting/program needed...
Help
klapfi said:
I solved it myself. As mentioned I had no OS installed so there was no way to activate developer settings. I couldtn enter edl mode via fastboot so I used testpoint to solve my problem. I then flashed it via Miflash and the phone works now fine :good:
Click to expand...
Click to collapse
hi bro your problem and i am the same as me now, and i read from this chat reply that you can finish via testpoint mode, then if you can know what windows you use 7 or 10, because on my windows does not show Qualcom 9008 driver, please help I