Hi guys,
After an update to 30th March nightly on Lineage OS (had only migrated from CM 12.1 OS to Lineage OS a day before with the 23rd March nightly), the boot got stuck to TWRP.
I could get into the Fastboot mode while TWRP was accessible.
Tried reverting back to stock ROM manually (& with a lot of guesswork) and the "fastboot flash system system.img" command was stuck too long on sending; I rebooted manually and the Cyanogen recovery showed up next with a error message. I pressed a button by mistake and since then the phone is stuck on the Zuk+powered by Android boot screen. Would appreciate help as it is no longer entering Fastboot or Recovery.
Update: somehow got into Cyanogen recovery after I had kept the phone away after trying many times. Have connected the phone to the computer but have no clue what to do next. Would appreciate exact steps with commands to get out of this mess.
Badly screwed this up. Was only beginning to enjoy the new Lineage OS when this series of mishaps and errors happened. :crying:
Connect your Lenovo ZUK Z1 device to your computer via USB and run this command as root: adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
(try this in recovery mode)
You can also go to the TWRP terminal and run: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
This solves your problem..
Thank you
First somehow you will need to find a way to switch your phone off and then follow this : https://www.youtube.com/watch?v=9t1HMXfO5ic
thanks srk, bhattyash.
i couldn't figure out how to do your method; couldn't locate = on the twrp screen and didn't know how to exactly give the adb shell command; so didn't attempt your methods.
i however tried flashing again manually; this time the system flash command changed into something that breaks up the system img into files less than 512 kb/mb or so. can't locate that very helpful flash command; but that's what helped me boot back to stock ROM
Hello there,
I have exactly the same issue, cant get in fastboot or recovery mode, just the black screen with "ZUK powered by android" logo. i tried connecting the phone to my computer and it recognize my zuk as " ShenQi Composite ADB Interface " . When i run power shell in my adb folder, after type adb devices i get "List of devices attached" but no devices at all in that list just an empty line.
The YouTube link doesn't work and I can't fully undesrtand how did you fix your phone, I don't know what to do.
Thanks and excuse my bad English !
TRY AT YOUR OWN RISK I AM NOT RESPONSIBLE FOR ANY DAMAGES
It may or may not work
So I spent the last 48 hours trying to fix my phone following a lot of tutorials and finally after combining some methods together here is the simplest solution.
1- install twrp 32-bit
2- wipe everything including internal storage
3- with twrp connect to pc
4- transfer the debloated stock firmware download from here
5- flash it
6- reboot to system after full boot still no signal
7- turn off and boot to bootloader
8- run commands (fastboot erase modemst1, modemst2)
9- reboot and voila signal is back + imei is back (cant fix the 4g if any know how let me know)
If you want to install a custom rom 8.1.0 like pixelexperience follow these steps after the previous ones
1- reboot to recovery
2- install no-verity-opt-encrypt-5.1 download from here
3- reboot to recovery
4- wipe > advanced wipe > data only
5- reboot to bootloader
6- flash twrp 64 bit
7- start recovery
8- wipe > slide to factory reset
9- flash custom rom
10- reboot to system > error in sim card detection
11- reboot and voila works like charm but also no 4G only 3G
Can you post the twrp 32-bits? I can't find it
//---//
I do with twrp-3.1.1.0 and the imei keeps 0
Fehra said:
Can you post the twrp 32-bits? I can't find it
//---//
I do with twrp-3.1.1.0 and the imei keeps 0
Click to expand...
Click to collapse
It's on the first page of the dev section
Click here
AhmedtSadek said:
So I spent the last 48 hours trying to fix my phone following a lot of tutorials and finally after combining some methods together here is the simplest solution.
1- install twrp 32-bit
2- wipe everything including internal storage
3- with twrp connect to pc
4- transfer the debloated stock firmware download from here
5- flash it
6- reboot to system after full boot still no signal
7- turn off and boot to bootloader
8- run commands (fastboot erase modemst1, modemst2)
9- reboot and voila signal is back + imei is back (cant fix the 4g if any know how let me know)
If you want to install a custom rom 8.1.0 like pixelexperience follow these steps after the previous ones
1- reboot to recovery
2- install no-verity-opt-encrypt-5.1 download from here
3- reboot to recovery
4- wipe > advanced wipe > data only
5- reboot to bootloader
6- flash twrp 64 bit
7- start recovery
8- wipe > slide to factory reset
9- flash custom rom
10- reboot to system > error in sim card detection
11- reboot and voila works like charm but also no 4G only 3G
Click to expand...
Click to collapse
First thnks for sharing, i spend all day on it trying a lot of ways and nothing, i followed the steps with the stock rom and the signal looks like came back in the first view, but i went to see the IMEI and still 0, i tried to make a call and nothing, rebooted and the signal was lost. I really don't know what to do anymore, everything that i try fails =\
A possible solution from the G5 Plus forum
Hi all - I've done some work on potter (Moto G5 Plus) around the IMEI issue. I was wondering if someone would be able to see if what I have found for the G5 Plus, applies to other Moto phones. Below is my thread:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
So, if someone is willing to help out, all you need is a stock rom with root access. Ideally I'd get two volunteers - one who has never flashed an oreo rom, and a second who has flashed an oreo rom and has had IMEI 0 at some stage (if it appears resolved, that's OK, you can still help). What is important for both scenarios is that you have never flashed someone else's persist.
All you'd need to do to help out is run the following commands via adb or in a shell, and paste the results:
Code:
su
ls -l /persist
That ensures a root shell (su), then lists details about the top level files in the persist folder, including their permissions and ownership.
The second one is this (still in a root shell, so su again if need be):
Code:
find /persist -type f
If anyone has questions, I'll keep an eye on this thread, and I'm also happy to take private messages.
Cheers
NZedPred said:
Hi all - I've done some work on potter (Moto G5 Plus) around the IMEI issue. I was wondering if someone would be able to see if what I have found for the G5 Plus, applies to other Moto phones. Below is my thread:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
So, if someone is willing to help out, all you need is a stock rom with root access. Ideally I'd get two volunteers - one who has never flashed an oreo rom, and a second who has flashed an oreo rom and has had IMEI 0 at some stage (if it appears resolved, that's OK, you can still help). What is important for both scenarios is that you have never flashed someone else's persist.
All you'd need to do to help out is run the following commands via adb or in a shell, and paste the results:
Code:
su
ls -l /persist
That ensures a root shell (su), then lists details about the top level files in the persist folder, including their permissions and ownership.
The second one is this (still in a root shell, so su again if need be):
Code:
find /persist -type f
If anyone has questions, I'll keep an eye on this thread, and I'm also happy to take private messages.
Cheers
Click to expand...
Click to collapse
I tried that thread but it gives me error "chown: bad user 'rfs'"
AhmedtSadek said:
I tried that thread but it gives me error "chown: bad user 'rfs'"
Click to expand...
Click to collapse
Hi, as I stated in the potter thread and above, I need someone who has never installed an Oreo rom to run the commands in my post above. Then I will be able to see the correct ownership for cedric. The 'fix' commands in my Potter thread are specific to Potter.
So to take something from what you posted in the Potter thread, I can see a similar issue, as the owner of your rfs folder is a user and group called "oem_2903" which indicates that the same issue is present.
renanfamous said:
First thnks for sharing, i spend all day on it trying a lot of ways and nothing, i followed the steps with the stock rom and the signal looks like came back in the first view, but i went to see the IMEI and still 0, i tried to make a call and nothing, rebooted and the signal was lost. I really don't know what to do anymore, everything that i try fails =\
Click to expand...
Click to collapse
Yes same problem bro.. with me xda help us plzz what we can do
Hey again, I've worked on another workaround that I have tested on my G5 Plus, that should work with the G5 as well. This will also allow me to identify the correct owner of the rfs folder, which is key to making this work.
For someone who is willing, please back up your persist partition first, then try the following:
Boot into stock rom, ensuring that you have root enabled
Run the following commands via adb or a shell
Code:
su
chmod -R +X+r+w /persist/rfs
chmod -R +X+r+w /persist/hlos_rfs
Then reboot. Your IMEI should be recreated now. Now run the following and post the full output so that I can work out who the correct owner of the rfs and hlos_rfs folders are:
Code:
su
ls -lR /persist/rfs
I flashed a 8.1 Oreo room and then used fastboot erase modemst1,2. This recovered 4g and imei ( no voltle)
I got my volte after flashing stock Oreo.. by fedrey.
Sonisudhanshu said:
I flashed a 8.1 Oreo room and then used fastboot erase modemst1,2. This recovered 4g and imei ( no voltle)
I got my volte after flashing stock Oreo.. by fedrey.
Click to expand...
Click to collapse
Did you had ever restored that moto g4 Persist backup for volte.?
akshu2697 said:
Did you had ever restored that moto g4 Persist backup for volte.?
Click to expand...
Click to collapse
First of all this a g5 thread.
secondly i just simply installed stock oreo and that recovered my 4g imei and volte automatically
akshu2697 said:
Did you had ever restored that moto g4 Persist backup for volte.?
Click to expand...
Click to collapse
Sonisudhanshu said:
First of all this a g5 thread.
secondly i just simply installed stock oreo and that recovered my 4g imei and volte automatically
Click to expand...
Click to collapse
I'm from the G5+ forums. In case it's not common knowledge here, never restore a persist from another device. We have had numerous threads recommending to flash the persist of a G4/G4+ to restore Volte and other functionality. That has been the cause of countless permanent semi-bricked and bricked G5+ devices. The persist is unique to each device, and without your own, you can no longer guarantee full functionality, and in the worst case, you will permanently lose your IMEI.
NZedPred said:
Hey again, I've worked on another workaround that I have tested on my G5 Plus, that should work with the G5 as well. This will also allow me to identify the correct owner of the rfs folder, which is key to making this work.
For someone who is willing, please back up your persist partition first, then try the following:
Boot into stock rom, ensuring that you have root enabled
Run the following commands via adb or a shell
Code:
su
chmod -R +X+r+w /persist/rfs
chmod -R +X+r+w /persist/hlos_rfs
Then reboot. Your IMEI should be recreated now. Now run the following and post the full output so that I can work out who the correct owner of the rfs and hlos_rfs folders are:
Code:
su
ls -lR /persist/rfs
Click to expand...
Click to collapse
When I execute it, it says "chmod: bad mode '+ X + r + w'".
Do you know why it happens?
Code:
adb shell
cedric:/ $ su
cedric:/ # hmod -R +X+r+w /persist/rfs
sh: hmod: not found
127|cedric:/ # chmod -R +X+r+w /persist/rfs
chmod: bad mode '+X+r+w'
1|cedric:/ # chmod -R +X+r+w /persist/hlos_rfs
chmod: bad mode '+X+r+w'
1|cedric:/ #
[CODE]
TioNacho said:
Hey again, I've worked on another workaround that I have tested on my G5 Plus, that should work with the G5 as well. This will also allow me to identify the correct owner of the rfs folder, which is key to making this work.
For someone who is willing, please back up your persist partition first, then try the following:
Boot into stock rom, ensuring that you have root enabled
Run the following commands via adb or a shell
Then reboot. Your IMEI should be recreated now. Now run the following and post the full output so that I can work out who the correct owner of the rfs and hlos_rfs folders are:
When I execute it, it says "chmod: bad mode '+ X + r + w'".
Do you know why it happens?
Code:
adb shell
cedric:/ $ su
cedric:/ # hmod -R +X+r+w /persist/rfs
sh: hmod: not found
127|cedric:/ # chmod -R +X+r+w /persist/rfs
chmod: bad mode '+X+r+w'
1|cedric:/ # chmod -R +X+r+w /persist/hlos_rfs
chmod: bad mode '+X+r+w'
1|cedric:/ #
[CODE][/QUOTE]
Just follow the guide here:
[url]https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147[/url]
Those commands above only worked in certain environments (e.g. with a particular version of something, can't remember which).
Click to expand...
Click to collapse
Hi All, Am Moto G5 plus XT1687 user. I installed number of custom ROM's and finally head back to Stock. This is my headache now, I lost my IMEI & VOLTE. I tried so many steps as mentioned in XDA, same I also tried installing with someone's persist .win file. Permanently I lost my IMEI & VOLTE. If you guys need anything from my phone to find a solution, please ping me. Now I can use that phone as 2g device only.
[email protected] said:
Hi All, Am Moto G5 plus XT1687 user. I installed number of custom ROM's and finally head back to Stock. This is my headache now, I lost my IMEI & VOLTE. I tried so many steps as mentioned in XDA, same I also tried installing with someone's persist .win file. Permanently I lost my IMEI & VOLTE. If you guys need anything from my phone to find a solution, please ping me. Now I can use that phone as 2g device only.
Click to expand...
Click to collapse
Since my Moto G5 Plus (XT1687) isnt my primary phone I just flashed it back to stock 7.1 and when I got the Oreo OTA it fixed the IMEI problem.
sabbotage said:
Since my Moto G5 Plus (XT1687) isnt my primary phone I just flashed it back to stock 7.1 and when I got the Oreo OTA it fixed the IMEI problem.
Click to expand...
Click to collapse
Thanks for the reply. Please update with stock room details that you used. I will try the same and revert.
I tried all the methods mentioned in the threads already present in the forum, but none of the methods seems to work for me. " no space left on the device " this is the error i get when i execute command "dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc" .
That command is if you are stuck in bootloop that boots to recovery, not bootloader. Also, if you meant it boots to recovery, your path to misc. may be different, 7824900.sdhci is for moto g5 plus xt1687. May be for others also, but to be sure, run
Code:
#cd /dev/block/platform/soc
#find . -name misc
to verify 7824900.sdhci is correct address.
[email protected] said:
That command is if you are stuck in bootloop that boots to recovery, not bootloader. Also, if you meant it boots to recovery, your path to misc. may be different, 7824900.sdhci is for moto g5 plus xt1687. May be for others also, but to be sure, run to verify 7824900.sdhci is correct address.
Click to expand...
Click to collapse
I posted this query earlier and all of them stated this solution to the problem. My problem is my device never reboots itself it reboots into bootloader and from there i have to manually press start to boot into rom and also my device is XT1686
As I posted, run the commands to be sure your misc. address is 7824900. If it returns something different, modify the
Code:
dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
command to reflect your misc. address. Also I believe those commands need to executed as root.
I had the same issue after upgrading the stock firmware to Oreo. Running the command via terminal wouldn't work either, I had to connect to a PC and run the command via ADB while in twrp. Worth a shot if you hadn't tried it.
JohnSmith8786 said:
I had the same issue after upgrading the stock firmware to Oreo. Running the command via terminal wouldn't work either, I had to connect to a PC and run the command via ADB while in twrp. Worth a shot if you hadn't tried it.
Click to expand...
Click to collapse
Yes, ADB/Fastboot is always preferred, terminal is where you must run as root with su commands, and you must be rooted with Majisk .
First of all, I'd like to state that I'm a newbie on android. I was trying to edit /system/etc/mkshrc file but I couldn't because system directory is in read-only. So after searching for a workaround on google, I tried to remount the system directory (I executed mount -o rw,remount /system as root from adb shell on my laptop) and then I restarted my device. But now my device is stuck on the boot logo. In fact, the ASUS boot logo appears for aprox. 3~4 seconds and then it disappears and then I'm stuck on a black screen. I still have my patched_boot.img file on my computer. I also tried executing fastboot flash boot patched_boot.img which worked previously when I was stuck on the recovery menu earlier after upgrading to Magisk 18 but this time it has no effect. I don't really care if I lose my data, all I want is to be able to use my phone again.
Moreover, for some reason fastboot can see my device but adb doesn't see it. Maybe it's normal since I'm in bootloader in fastboot mode? Idk like I said I'm a newbie.
My problem is very similar to this one, but no solution has been given.
I would really appreciate it if anyone could help me find a solution.
BTW this is what I was originally trying to do in mkshrc file.
Hardware/Versions
Zenfone AR (ZS571kl / no verizon)
Android 7.1 Nougat
Magisk 17.3
Magisk manager 6.0.1
Laptop OS: Ubuntu 18.10
Bootloader Infos
Code:
[COLOR="Red"]FASTBOOT MODE[/COLOR]
PRODUCT_NAME - Siva
STORAGE VARIANT - UFS
BOOTLOADER VERSION - 1.23
VERSION - version-empty
SERIAL NUMBER - HBAKC...
SECURE BOOT - enabled
[COLOR="red"]DEVICE STATE - unlocked[/COLOR]
Hi all,
I was planning to downgrade the Lollipop to Kitkat (or maybe a ROM away from Google) and now that I have had the time to try it out, I'm running into issues regarding trying to unlock the bootloader.
I've read the article here: https://developer.nvidia.com/sites/.../docs/HowTo-Flash-TN7-WiFi-Recovery-Image.txt
and also downloaded the WHQL Shield USB driver from nvidia's website (https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB) though it doesn't seem to be doing much here.
I ran
Code:
adb reboot bootloader
and I have this:
Code:
[bootloader] (built on Apr 24 2015, 02:51:15)
Device - locked
Serial Number XXXXX
Press <Power> to select, <Volume Up/Down> for selection move
Continue
Fastboot Protocol
Recovery Kernel
Reboot
Poweroff
I then tried to run
Code:
fastboot oem unlock
and it says:
Code:
< waiting for device >
On the tablet, I select Fastboot Protocol, but all it does is go back to the bootloader.
I tried running
Code:
fastboot devices
and no device is appearing. Running:
Code:
fastboot device
or
Code:
fastboot oem unlock
still says:
Code:
< waiting for device >
Can anyone help me? The issues with Lollipop from the touch screen craziness, and the heat and tablet slow downs are well documented on Lollipop so I want to make this tablet usable again. Please let me know what I'm missing here.
Apparently, I wasn't missing anything. I switched to my Linux laptop where fastboot and ADB were installed via Android SDK.
I ran fastboot devices which picked up the tablet. Then I could run OEM unlock command. Off to the ROM flashing adventure!
Just flashed using OTA 2.5 from Nvidia's website and that seems to have ruined the install. It now only goes into APX mode. I read somewhere that the links Nvidia put for the P1988W were actually for the P1640. That's not good.
I wonder if there's a significance with the flash_tegratab_p1988.bct file that I found on another firmware website. Cannot seem to download it though.
EDIT: Found a firmware and will need to study the differences of this APX image to the Advent one.
EDIT2: Alternatively, as I have another Cherry Mobile tablet as backup, if I can use this to dump the image: https://forum.xda-developers.com/t/...d-partition-with-nvflash-on-the-gtab.1010659/
Been tinkering with the flash.sh script to see what it does and on an interactive shell, this seems to be the command:
Code:
sudo nvflash --bct flash_tegratab_p1988.bct --setbct --odmdata 0x4069C000 --configfile flash.cfg --create --bl bootloader.bin --reset normal 0
I'll continue to poke around. Strange that the script doesn't ask for p1988 if there's a secure boot (it only does for p1640).
Hey niniendowarrior,
I fell down the same rabbit hole around a year ago after doing the exact same thing as you, installing the 2.5 OTA from the NVidia site.
I've mostly given up. But, I got thinking that the NVidia sources available from their site might compile a compatible nvflash. The issue there is that compiling it requires a lot of outdated libs. I don't know when I'll have the time to try it out, but it might be a possible avenue for you to explore!
Best of luck.