hello,
how are you team,
the problem with g955u,,,, its converted to g9550, so i flashed g955u and after flash baseband is gone,
so i try to flash lot of combinations latest FW,s u/u1 but still same ,,, now i,m in u5,
so i need to suggestion or solution to fix this **** ,
share your experience.
You mean you lost imei? Have you tried way to recover it via combination fw? If yes, then what you see in imei page in combination fw? Null, zero, or blank
i have the exact same problem sadly and no solution yet
ionut2003 said:
i have the exact same problem sadly and no solution yet
Click to expand...
Click to collapse
try this method problem will solve (IN SHA ALLAH)...
1.Boot into TWRP recovery.
2.From TWRP’s main screen, select Advanced » then Terminal.
3.Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
4.Reboot device.
Related
Just got a notice that there was an Android update, I'm assuming a small patch. But now I'm stuck in at the LG boot logo. I can still boot into TWRP recovery. But no matter what I can't start my phone all the way up. How do I fix this?
gpitner said:
Just got a notice that there was an Android update, I'm assuming a small patch. But now I'm stuck in at the LG boot logo. I can still boot into TWRP recovery. But no matter what I can't start my phone all the way up. How do I fix this?
Click to expand...
Click to collapse
You should never install updates if you have installed a custom recovery.
Did you do a factory reset from recovery? That should fix it.
If doing a factory reset doesn't fix your phone, then you need to flash your stock firmware or a custom rom.
Cheers
What worked for me was from the TWRP terminal command was to type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter,
and type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
However I won' take credit for coming up with this, Weston Madsen over at androidcentral and the IRC xda-devs helped me put it all together. A huge thanks to them!
never do update if you have a custom recovery
Ok so I am stuck, I recently rooted my device and accepted the ota, big error on my part. I then proceeded to install twrp via adb commands, in Ubuntu... problem not is I am now stuck in twrp 2.6.3.2, and the touch in this version is very jenky, the bottom half doesn't accurately register touch commands. Can anyone help me to restore this device?
-note twrp bypasses download mode
-and factory restore doesn't work
-I was able to flash cloudy g3 but I can't get past twrp
-also I did an advance wipe but still couldn't get anywhere.
Please help!
nicklefloss said:
Ok so I am stuck, I recently rooted my device and accepted the ota, big error on my part. I then proceeded to install twrp via adb commands, in Ubuntu... problem not is I am now stuck in twrp 2.6.3.2, and the touch in this version is very jenky, the bottom half doesn't accurately register touch commands. Can anyone help me to restore this device?
-note twrp bypasses download mode
-and factory restore doesn't work
-I was able to flash cloudy g3 but I can't get past twrp
-also I did an advance wipe but still couldn't get anywhere.
Please help!
Click to expand...
Click to collapse
From the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
jsho31 said:
From the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
Thanks but that doesnt work because my phone doesnt register on ubuntu
nicklefloss said:
Thanks but that doesnt work because my phone doesnt register on ubuntu
Click to expand...
Click to collapse
you use the terminal command via TWRP, not your lcomputer
Dear friends.. My Moto G default boot is always going to recovery. The way i could enter the system/rom is just with Bootloader option "Normal powerup". I already try many ways, reflash custom recovery (TWRP, CWM, CM), reflash stock, and reflash custom rom, but they do nothing to this case. Is there any way to change it back to normal? I'm currently on CM 12.1 Unofficial and running TWRP 2.8.6.0. It is not so bad since i still can access the system, it just anoying that couldn't restart device straight to system. Thanks in advance guys..
[SOLVED]
This problem is solved by following demlak post on twofie thread.
Here are the original post from demlak:
on #cyanogenmod channel on freenode user spudowiar helped me..
the problem:
partition /misc is fault.. and twrp (for example) does not mount this partition to wipe it correctly..
you can wipe it manualy by dd it..
adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Click to expand...
Click to collapse
but do a backup before! (just in case)
adb pull /dev/block/platform/msm_sdcc.1/by-name/misc misc.img
Click to expand...
Click to collapse
Click to expand...
Click to collapse
FYI: I do the adb command on the mount twrp
[SOLVED]
Sorry for my English... I have a problem with my moto g XT1032 with bootloader unlocked and version recovery latest TWRP, I rooted and was running CM13, until I began to present faults so I decided to restart the phone, from that the phone turned on in recovery mode and when I check if everything is fine, says I have no OS installed, I review the status of the internal storage (all this is from the recovery TWRP) it says it is 0mb,i tried to flash from the bootloader the original firmware and all commands says FAILED when it's gonna write it (failed to erase partition). Anyone who has had this problem before and have fixed or knows how to fix it?
Try this tool: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522 .
Via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
lost101 said:
Via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
I try to do it but it says
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on device
:crying::crying::crying:
Maybe try:
adb shell
cd /dev/block/platform/msm_sdcc.1/by-name
dd if=/dev/zero of=./misc
lost101 said:
Maybe try:
adb shell
cd /dev/block/platform/msm_sdcc.1/by-name
dd if=/dev/zero of=./misc
Click to expand...
Click to collapse
Sorry for hijacking the thread but i am afraid that I am with similar problem, when using my G its just rebooted and after that the battery drop to 20% (previous 76%) and a lot of files disappear, like amnesia any idea why?
BryanByteZ said:
Sorry for hijacking the thread but i am afraid that I am with similar problem, when using my G its just rebooted and after that the battery drop to 20% (previous 76%) and a lot of files disappear, like amnesia any idea why?
Click to expand...
Click to collapse
Sounds like classic 'emmc corruption' symptomatology. Fastboot flash the latest factory firmware image for your model. However it may well be game over for your handset.
lost101 said:
Sounds like classic 'emmc corruption' symptomatology. Fastboot flash the latest factory firmware image for your model. However it may well be game over for your handset.
Click to expand...
Click to collapse
Oh sh**, okay thanks for the info!
when I flashed falcon_502_partitions_nomodem.zip on my moto g XT1028 and then I reboot to bootloader nothing is there and when I tried to restart my devices the screen is black and the fastboot mode is also not visible and I'm not able to flash anything to make my device work.
Aditya2512 said:
when I flashed falcon_502_partitions_nomodem.zip on my moto g XT1028 and then I reboot to bootloader nothing is there and when I tried to restart my devices the screen is black and the fastboot mode is also not visible and I'm not able to flash anything to make my device work.
Click to expand...
Click to collapse
Post here and only here: http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
If your model is not supported, then you may never be able to resolve the situation.
Solved
I faced the sane problem with my moto g3. actually after booting it into recovery it went to loop of recovery and off.
Then downgraded twrp to 3.0.2 using fastboot from pc.
Then it booted into recovery but was showing 0mb internal storage.Lastly i used format data under wipe in twrp then it got back to normal.
Hello, so the was a magisk update some time ago, I decided to do it this friday (a week ago) (from v23 to v24.1). My phone went into a boot loop so I decided to just flash stock and reflash 24.1, I tried for a few hours, but 24.1 didn't work and I always had a boot loop, so I got back the 23 and thought that's the end. Sadly my IMEI became invalid in the process. I'm not sure what is needed to fix this, or what info would be needed, so please tell me in the comments or something. I don't have any backups of EFS.
I've same problem. Also looking for way to bring my device back to life
Hmm I didnt get this. IMEI not showing in system properties?
*Wait you didnt have backups? Live and learn my friends.
(I keep one that is 15gb on my measely 64gb card in my phone, and a base backup copy on my desktop.)
Nope IMEI is not showing in properties.
Yep I know, no backup is my fault, totally my fault.
My phone even tells me I can't use the *#06# code because it's not supported on show imei, I didn't even know you could break your IMEI. Is there any way of writing the IMEI or something or is it just done?
Sunderw3k said:
My phone even tells me I can't use the *#06# code because it's not supported on show imei, I didn't even know you could break your IMEI. Is there any way of writing the IMEI or something or is it just done?
Click to expand...
Click to collapse
*#06# doesn't work for me nether.
Altho I was aware of possibiity of breaking IMEI, I was in rush which led to wiping/overwriting efs partition I think
Hello. I have the same problem with the Imei number on this phone. * # 06 # does not work. Displays info that Imei is not supported on this model.
NetBos said:
*#06# doesn't work for me nether.
Altho I was aware of possibiity of breaking IMEI, I was in rush which led to wiping/overwriting efs partition I think
Click to expand...
Click to collapse
Well so we are in that together, I found something about fixing the IMEI with combination firmware, but it didn't work for me... "Please get the approval to use factory binary : param". Maybe you can try it. Tell me if it works for you
Guys, are your phones also a32's? If so can you check on a rooted phone if /data/nvram Is here? I'm pretty sure that's something important and it's missing for me.
Sunderw3k said:
Guys, are your phones also a32's? If so can you check on a rooted phone if /data/nvram Is here? I'm pretty sure that's something important and it's missing for me.
Click to expand...
Click to collapse
Rooted. I made the warning thread so survived it. No data/nvram present on phone.
i have the same problem i have efs folder but how to restore?
Try
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
In TWRP console maybe?
I'm having the same problem with an a32 4g so I'm lurking.
TimmyP said:
Try
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
In TWRP console maybe?
Click to expand...
Click to collapse
doesn't that mean to completely erase those two modem partitions? Won't it finish destroying the phone capabilities?
Hi,
Same problem here after flashing my SM-A326B (A32 5G) with boot.img patched with magisk 23.0 (tried to use v24.1 but phone enters bootloop): it lose the IMEI at the instant I tried to call someone (it was working for a few days, until I tried to call. Receiving a call was no pb.).
I do have a BACKUP of EFS and SEC_EFS partitions made with the "Partitions Backup" app (by Wanam) just after rooting (because you need root to make backup of those partitions). I restored them, which restored IMEI #2 (not the first one) for a few minutes before being empty again (I think it was when I activated WiFi). SIM card was not in the slot. Now restoring the partitions does not change anything. IMEI always empty.
Maybe I should try to flash the original unpatched image and restore the EFS partitions to get the IMEI back (hopefully), then root again using TWRP this time...? The thing is I already have data and apps on the phone and I am tired of reinstalling everything.
I hope description of my pb helps to solve this bug...
dronkit said:
I'm having the same problem with an a32 4g so I'm lurking.
doesn't that mean to completely erase those two modem partitions? Won't it finish destroying the phone capabilities?
Click to expand...
Click to collapse
Ya, but when you reboot it might reset efs after they are wiped. Seen this in the past. Phones are already missing \efs completely with no backup.
TimmyP said:
Try
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
In TWRP console maybe?
Click to expand...
Click to collapse
I tried this, doesn't work (error partition not found)
rousselmanu said:
I tried this, doesn't work (error partition not found)
Click to expand...
Click to collapse
this isn't for Mediatek based phones as far as I know, only for Qualcomm Snapdragon.
Even with a backup of EFS/SEC_EFS, it seems that it doesn't help much to recover the IMEI numbers...
I flashed the original firmware, installed TWRP plus magisk 23 from TWRP, then flashed the .img of EFS and SEC_EFS with adb using following commands:
adb shell
su # root
dd if=/dev/zero of=/dev/block/sdc2 # wipe EFS partition
dd if=/dev/zero of=/dev/block/sdc3 # wipe SEC_EFS partition
dd if=/mnt/sdcard/efs.img of=/dev/block/sdc2 # restore img of EFS before loosing IMEI
dd if=/mnt/sdcard/sec_efs.img of=/dev/block/sdc3 # idem for SEC_EFS
(phone automatically reboots between dd commands). Then I entered TWRP and wiped cache/davlik/data.
IMEI is still empty.
I reinstalled again the original firmware with ODIN (no root, no twrp), hoping that the restored EFS partition would do it with the untouched firwmare => IMEI still empty.
All in all, it seems that a backup of EFS/SEC_EFS doesn't help. Maybe these partitions are not damaged by magisk after all?
Comparing content of the img files before/after loosing IMEI I can spot a few differences in the files, I can detail if someone is interested...
TimmyP said:
Ya, but when you reboot it might reset efs after they are wiped. Seen this in the past. Phones are already missing \efs completely with no backup.
Click to expand...
Click to collapse
No, EFS is not reset after wiping with:
adb shell
su
dd if=/dev/zero of=/dev/block/sdc2 # wipe EFS partition
dd if=/dev/zero of=/dev/block/sdc3 # wipe SEC_EFS partition
For those who succeeded in rooting the A32 5G without this IMEI issue, could you detail the procedure? With version of the tools etc?
BTW, how come that even just unlocking the bootloader can erase the IMEI? see : https://forum.xda-developers.com/t/sim-not-working-on-a326br.4398149/