Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Same problem. When WiFi is ON.
When I put WiFi OFF - the tablet works fine.
Last firmware doesn't help, reset too. I think there is no solution at this moment, except maybe to flash an old firmware with Android 6.
I'll replace it in store. No idea about Asus control quality of their firmware... but this problem is pretty common.
???
Belnadifia said:
Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Click to expand...
Click to collapse
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
coolbeans2016 said:
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
Click to expand...
Click to collapse
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
I'll give you that
diplomatic said:
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
Click to expand...
Click to collapse
The link on the Z380M is what threw a flag for me because that Asus tab isnt rootable. If this is some combo of slipups between tools & devices that lines up just right to get TWRP on its not described very well in the OP. Using the 5.132 (?) you can not readback with that option.ini file.... so what am I missing? The bootloader unlock app isn't written for this tablet is it? written for the zenphone 2 (3)?
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Just want to mention for anyone else struggling with this issue, what fixed it for me:
I found the reboot would only happen when wifi was turned on, and even more weird, it would only happen when connected to specific wifi networks. After doing a factory reset I was able to set it up again by tethering to the wifi on my phone. I then found that I actually was able to connect to the problematic wifi network but only by setting a static IP! This has completely resolved the issue for me.
Thaniks
diplomatic said:
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Click to expand...
Click to collapse
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
coolbeans2016 said:
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
Click to expand...
Click to collapse
Ohhh... ok. No problem man. Just please get your facts straight before posting next time. Good luck. BTW, I'm not sure if you saw this post on the TWRP thread from 2 weeks ago. You didn't reply.
diplomatic said:
What is the error that you got when trying to flash it? Can you post a screenshot of the Download tab along with the Help/About dialog box?
Click to expand...
Click to collapse
I found a used LG G4 that was locked to Koodo for a friend of mine. I researched to make sure that it supports the AWS 1700/2100 band since my friend is on Eastlink (similar to Freedom Mobile). At first everything worked fine, but now he is getting intermittent disconnections from the network where it says "no service." I had him choose the option without LTE, and at first he got service again, but then he didn't get mobile data, and the connection randomly dropped anyway (for calls and texts).
I had him open the service menu via *#*#4636#*#* to turn off the radio, but as soon as he goes to "Phone Information," he gets the message "This application does not work on this device." So Koodo blocked the menu. Wonderful.
At this point, I'm really not sure what to do. Has anyone had similar issues? I've rooted and installed custom ROMs on my own phones several times before. Would installing a custom ROM help? Or maybe just flashing another modem file?
If anyone could help, it would be greatly appreciated. I was trying to help my friend save some money. His old phone was 8 years old and was a cheapo that was laggy from the start. I recommended a "higher end" used phone rather than another cheapo. He's running a business and has 9 kids, so... I would really like to get this working for him.
Edit:
Problem is solved. My friend is no longer experiencing intermittent "no service'" or anything. Here is what I did:
1. Followed these instructions to unlock the bootloader.
2. Flash stock Nougat zip (instructions also say "After that and while still in TWRP: Choose Reboot -> RECOVERY ! This should ensure TWRP will not be overwritten on Android boot")
3. Flash Nougat modem zip
4. Flash my model's baseband (again; was already done during bootloader unlock)
I realize now that I might have not needed to unlock bootloader at all, and could have used LG Up (new) to flash a kdz. But oh well, it's all done, and now my friend has Nougat (the Canadian variant abandoned updates before Nougat).
threehappypenguins said:
I found a used LG G4 that was locked to Koodo for a friend of mine. I researched to make sure that it supports the AWS 1700/2100 band since my friend is on Eastlink (similar to Freedom Mobile). At first everything worked fine, but now he is getting intermittent disconnections from the network where it says "no service." I had him choose the option without LTE, and at first he got service again, but then he didn't get mobile data, and the connection randomly dropped anyway (for calls and texts).
I had him open the service menu via *#*#4636#*#* to turn off the radio, but as soon as he goes to "Phone Information," he gets the message "This application does not work on this device." So Koodo blocked the menu. Wonderful.
At this point, I'm really not sure what to do. Has anyone had similar issues? I've rooted and installed custom ROMs on my own phones several times before. Would installing a custom ROM help? Or maybe just flashing another modem file?
If anyone could help, it would be greatly appreciated. I was trying to help my friend save some money. His old phone was 8 years old and was a cheapo that was laggy from the start. I recommended a "higher end" used phone rather than another cheapo. He's running a business and has 9 kids, so... I would really like to get this working for him.
Click to expand...
Click to collapse
Assuming he's carrier unlocked, if he's using an old sim card from a previous carrier, he should purchase a new sim card from his current carrier.
If he hasn't already tried this, suggest he do a network reset: Settings > Backup & reset > Network settings reset.
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW. He should backup his userdata first.
If bootloader unlocked (UsU) he could re-flash his modem.bin or modem.img file from a SALT extract of his appropriate kdz.
sdembiske said:
Assuming he's carrier unlocked, if he's using an old sim card from a previous carrier, he should purchase a new sim card from his current carrier.
If he hasn't already tried this, suggest he do a network reset: Settings > Backup & reset > Network settings reset.
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW. He should backup his userdata first.
If bootloader unlocked (UsU) he could re-flash his modem.bin or modem.img file from a SALT extract of his appropriate kdz.
Click to expand...
Click to collapse
I've already done a factory reset of the phone. Is a network reset necessary, or would the factory reset cover that? His bootloader is not unlocked... yet. I will attempt re-flashing his kdz and/or just the modem if the network reset at this point is unnecessary. I'm looking at lg-firmwares.com and don't see Koodo on that list (the phone was originally put out by Koodo), so I assume Telus (Koodo's parent network) would be a safe one to use (MM)?
I found a bigger list here. I found the link in this guide.
threehappypenguins said:
I've already done a factory reset of the phone. Is a network reset necessary, or would the factory reset cover that? His bootloader is not unlocked... yet. I will attempt re-flashing his kdz and/or just the modem if the network reset at this point is unnecessary. I'm looking at lg-firmwares.com and don't see Koodo on that list (the phone was originally put out by Koodo), so I assume Telus (Koodo's parent network) would be a safe one to use (MM)?
Click to expand...
Click to collapse
Network reset is your first & best option. Re-flashing the kdz is your last option.
Use this site for the kdz download and scroll down to and use this Telus kdz ( H81220z_00_0327.kdz: it does work on Koodo as well): https://lg-firmwares.com/lg-h812-firmwares/firmwares/
Refer to this link for flashing with LGUP-NEW: https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
As a 'Senior Member" you should know that it is an XDA courtesy to use the Thanks button - you should have learned to use it by now - bottom right of the post
sdembiske said:
Assuming he's carrier unlocked, if he's using an old sim card from a previous carrier, he should purchase a new sim card from his current carrier.
If he hasn't already tried this, suggest he do a network reset: Settings > Backup & reset > Network settings reset.
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW. He should backup his userdata first.
If bootloader unlocked (UsU) he could re-flash his modem.bin or modem.img file from a SALT extract of his appropriate kdz.
Click to expand...
Click to collapse
sdembiske said:
Network reset is your first & best option. Re-flashing the kdz is your last option.
Use this site for the kdz download and scroll down to and use this Telus kdz ( H81220z_00_0327.kdz: it does work on Koodo as well): https://lg-firmwares.com/lg-h812-firmwares/firmwares/
Refer to this link for flashing with LGUP-NEW: https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
As a 'Senior Member" you should know that it is an XDA courtesy to use the Thanks button - you should have learned to use it by now - bottom right of the post
Click to expand...
Click to collapse
Thanks! I am getting him to do a Network settings reset right now. I'll wait and see if that resolves the issue. If it doesn't I will attempt flashing.
I do have a question about the bootloader. You said that it is required to be unlocked. But I read that on the H812 you can't unlock the bootloader. So how does that work? Can I just flash a Marshmallow kdz onto the existing MM OS? I see that his current software version is H81220z. I thought that since there is no root (and no bootloader unlock?) for MM, that I have to downgrade to Lollipop (as explained in these instructions). I thought an unlocked bootloader is always a prerequisite?
Aha! I searched and searched and eventually found this key post. It points to this thread here about (kind of, sort of) unlocking the bootloader and also recommends a backup with SALT.
threehappypenguins said:
Aha! I searched and searched and eventually found this key post. It points to this thread here about (kind of, sort of) unlocking the bootloader and also recommends a backup with SALT.
Click to expand...
Click to collapse
Yes, quite a number of us now have unlocked our bootloader, thanks to the unwavering steadfastness of @steadfasterX, author of the UsU unlock method.
Ensure you do upgrade to the latest Telus 1220z MM kdz (even though he is on it already), I linked first with LGUP-NEW to see if the network connection is restored and then do a SALT backup as recommended before unlocking. It is very important you read the OP in the USU unlock thread thoroughly, making sure you understand it complete;y, to avoid easily avoidable screw-ups. You should make sure your friend understands the process and risks as well before proceeding.
steadfasterX has also prepared custom roms for our unlocked H812's and I can recommend both the ASOCP N and the Lineageos O roms for your H812, if your friend doesn't rely on any LG stock proprietary apps, otherwise you can flash him a special stock Nougat LG rom (all available in the Downloads section in the UsU thread).
sdembiske said:
Yes, quite a number of us now have unlocked our bootloader, thanks to the unwavering steadfastness of @steadfasterX, author of the UsU unlock method.
Ensure you do upgrade to the latest Telus 1220z MM kdz (even though he is on it already), I linked first with LGUP-NEW to see if the network connection is restored and then do a SALT backup as recommended before unlocking. It is very important you read the OP in the USU unlock thread thoroughly, making sure you understand it complete;y, to avoid easily avoidable screw-ups. You should make sure your friend understands the process and risks as well before proceeding.
steadfasterX has also prepared custom roms for our unlocked H812's and I can recommend both the ASOCP N and the Lineageos O roms for your H812, if your friend doesn't rely on any LG stock proprietary apps, otherwise you can flash him a special stock Nougat LG rom (all available in the Downloads section in the UsU thread).
Click to expand...
Click to collapse
My friend's phone says that it's MM and software version is H81220z, so he should be good there.
I'm interested in Lineage Oreo, and I'm a little confused about the instructions, if you don't mind enlightening me. So first off, I understand that UsU is required first. In the UsU instructions, it says:
Flash the baseband package now: <model>_UsU_baseband_flash-in-twrp.zip
Click to expand...
Click to collapse
But in the Lineage O instructions, it says:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
Click to expand...
Click to collapse
So I assume that I'm supposed to just skip flashing the baseband in the UsU instructions? What about installing SuperSU afterwards? Is flashing that new baseband required?
I guess what I'm wondering is, should I flash the baseband, like in UsU instructions, then revert back to the original baseband, like in the Lineage O instructions, or should I just skip flashing the baseband in the first place?
threehappypenguins said:
My friend's phone says that it's MM and software version is H81220z, so he should be good there.
I'm interested in Lineage Oreo, and I'm a little confused about the instructions, if you don't mind enlightening me. So first off, I understand that UsU is required first. In the UsU instructions, it says:
But in the Lineage O instructions, it says:
So I assume that I'm supposed to just skip flashing the baseband in the UsU instructions? What about installing SuperSU afterwards? Is flashing that new baseband required?
I guess what I'm wondering is, should I flash the baseband, like in UsU instructions, then revert back to the original baseband, like in the Lineage O instructions, or should I just skip flashing the baseband in the first place?
Click to expand...
Click to collapse
The reason you should re-flash the same kdz, is to see if it gets the network connectivity issue solved before proceeding with anything else as you may find the problem still exists.
If you are planning to go the the LG Nougat stock rom, the baseband should be flashed. If you're going to the H812 Lineage O rom, just flash the modem.bin file from the SALT backup you do - you can always flash the baseband later if there is a problem and it is needed. Flash SuperSu after.
You're still forgetting the Thanks button, eh ... ? Hint: It's a good habit to get into when receiving help from other members.
sdembiske said:
The reason you should re-flash the same kdz, is to see if it gets the network connectivity issue solved before proceeding with anything else as you may find the problem still exists.
If you are planning to go the the LG Nougat stock rom, the baseband should be flashed. If you're going to the H812 Lineage O rom, just flash the modem.bin file from the SALT backup you do - you can always flash the baseband later if there is a problem and it is needed. Flash SuperSu after.
You're still forgetting the Thanks button, eh ... ? Hint: It's a good habit to get into when receiving help from other members.
Click to expand...
Click to collapse
Well, I successfully unlocked the bootloader using UsU. I flashed the the baseband package, because I figure I will first re-flash the same kdz. I also decided I will flash stock Nougat because I figure it will be more stable for my friend. Unfortunately, I only got as far as flashing the baseband package and SuperSU.zip. When I try to boot into the OS, it just hangs on the "LG Life's Good" logo forever. Should I go ahead and flash the MM kdz using LG Up new anyway? I already tried a factory reset, and it didn't make a difference.
threehappypenguins said:
Well, I successfully unlocked the bootloader using UsU. I flashed the the baseband package, because I figure I will first re-flash the same kdz. I also decided I will flash stock Nougat because I figure it will be more stable for my friend. Unfortunately, I only got as far as flashing the baseband package and SuperSU.zip. When I try to boot into the OS, it just hangs on the "LG Life's Good" logo forever. Should I go ahead and flash the MM kdz using LG Up new anyway? I already tried a factory reset, and it didn't make a difference.
Click to expand...
Click to collapse
If you want to hard brick your friend's phone and possibly lose a friend, sure, ignore the UsU thread OP warnings ... i.e., DO NOT flash with LGUP-NEW now that the phone is unlocked. If you're going to the stock Nougat, flash the N modem from the UsU thread. If that doesn't work, flash the MM modem from a SALT extraction of a clean Telus H81220z kdz.
Suggest you read the OP in the UsU thread fully, i.e., all of it including the FAQ's and make sure you understand it all this time.
I finally figured out why I'm so confused. Original, when you said this:
sdembiske said:
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW.
Click to expand...
Click to collapse
I misread. I thought you said "assuming he's bootloader unlocked." So I kept thinking that in order to do ANYTHING (flash the kdz), his bootloader had to be unlocked.
I read the OP over and over, and didn't see the part about never kdz flashing with LGUp, coupled with my misunderstanding that I had to be bootloader unlocked in order to flash with lgup. But I finally found what you're talking about in the FAQ.
You can't! At least for the KDZ flashing part: not yet.
SALT will allow flashing of KDZ files with the upcoming version 4.0 but until then do not flash with lgup and do not use the LG Android internal updater --> You WILL 100% brick your device.
Click to expand...
Click to collapse
I realize all this is a risk to my friend's phone, it's just that I was the one who talked him into buy a used decent phone, rather than buying a new cheapo crappy phone. I just wish I didn't misread what you had said and tried flashing with LGUp *before* I bootloader unlocked.
It's been a long week.
P.S. - I wouldn't lose him as a friend over this. He is very technologically challenged, and keeps thanking me over and over for helping him with all his previous phones, for giving his wife one of our used old phones (she previously had no phone), for helping set up his network with a Tomato firmware router and OpenDNS so he can know what in the world his kids are doing online and have control over the network, etc. So if I bricked his phone, I would just buy another one used for him. He wouldn't care. He just needs a half decent, inexpensive phone to run his small business. Right now, he's just using his old phone for the time being. It's a MotoE that he's had for the last 8 years and he says, "I need to upgrade." Lol
I searched and searched for the Nougat modem (at this point, I might as well upgrade to Nougat), and this is what I found. Is this correct? Or is there another version that I need because that one isn't compatible with my phone? I also assume that the modem zip is flashable via TWRP? I see the "META-INF" folder.
This is the stock Nougat I was going to flash (with TWRP? It looks like a flashable zip). My ARB is 0. My GPT compatibility is H811.
I see in the N stock that there is already a modem.bin file. So should I first flash the stock N zip, and THEN flash the separate N modem? Also, the instructions say:
16) I just wanna flash Nougat STOCK. Are there any worry free UsU downloads for it available?
Sure: here
After flashing ensure you flash your model baseband package!
After that and while still in TWRP: Choose Reboot -> RECOVERY ! This should ensure TWRP will not be overwritten on Android boot
Click to expand...
Click to collapse
So, in summary:
1. Flash stock Nougat zip
2. Flash Nougat modem zip
3. Flash my model's baseband (again)?
And if none of that works:
flash the MM modem from a SALT extraction of a clean Telus H81220z kdz
Click to expand...
Click to collapse
?
threehappypenguins said:
I searched and searched for the Nougat modem (at this point, I might as well upgrade to Nougat), and this is what I found. Is this correct? Or is there another version that I need because that one isn't compatible with my phone? I also assume that the modem zip is flashable via TWRP? I see the "META-INF" folder.
This is the stock Nougat I was going to flash (with TWRP? It looks like a flashable zip). My ARB is 0. My GPT compatibility is H811.
I see in the N stock that there is already a modem.bin file. So should I first flash the stock N zip, and THEN flash the separate N modem? Also, the instructions say:
So, in summary:
1. Flash stock Nougat zip
2. Flash Nougat modem zip
3. Flash my model's baseband (again)?
And if none of that works:
?
Click to expand...
Click to collapse
Yes. Refer to FAQ #22 in the UsU thread and the Stock N report by @grantdb.
The reason why you get intermittent service because the phone you found had been blacklisted by the original owner
deltadiesel said:
The reason why you get intermittent service because the phone you found had been blacklisted by the original owner
Click to expand...
Click to collapse
It was locked to Koodo, and the original owner told me that. I called Koodo, gave the IMEI, and they gave me the Network unlock code. If it was blacklisted, wouldn't Koodo have said something?
sdembiske said:
Yes. Refer to FAQ #22 in the UsU thread and the Stock N report by @grantdb.
Click to expand...
Click to collapse
I flashed stock Nougat, then Nougat modem, then the H812 baseband, then rebooted directly back to TWRP. Then I booted up the phone and it was in Spanish. So I changed that to English. Then I had rebooted the phone again (adding a SIM card for testing), and it was in Spanish again, so I changed it back to English. Then I rebooted the phone again, and it was in Russian, so I changed it back to English, and also deleted all the extra keyboards which included Spanish and Russian (at least, it looked like it was Russian). Rebooted the phone a couple more times, and it stays in English.
So far, everything is working.
Thanks again for your help! Will report back if the intermittent issue comes back, or if everything continues to work well, in case anybody with the same issue is looking for a fix.
On another note, out of curiosity, I tried *#*#4636#*#* on the Phone's dial pad to open the service menu, and noticed that Phone Information is still blocked. Just curious... is that a ROM thing? Or a baseband/modem thing?
threehappypenguins said:
I flashed stock Nougat, then Nougat modem, then the H812 baseband, then rebooted directly back to TWRP. Then I booted up the phone and it was in Spanish. So I changed that to English. Then I had rebooted the phone again (adding a SIM card for testing), and it was in Spanish again, so I changed it back to English. Then I rebooted the phone again, and it was in Russian, so I changed it back to English, and also deleted all the extra keyboards which included Spanish and Russian (at least, it looked like it was Russian). Rebooted the phone a couple more times, and it stays in English.
So far, everything is working.
Thanks again for your help! Will report back if the intermittent issue comes back, or if everything continues to work well, in case anybody with the same issue is looking for a fix.
On another note, out of curiosity, I tried *#*#4636#*#* on the Phone's dial pad to open the service menu, and noticed that Phone Information is still blocked. Just curious... is that a ROM thing? Or a baseband/modem thing?
Click to expand...
Click to collapse
Not sure about the language issue as I haven't used the stock N rom but if it continues to hold, no problem. Make sure you do a TWRP backup when you have it where you want it.
The 'secret' menu accessed from the dial pad hasn't worked for me in AOSCP N or Lineage O so it may be a rom thing. *#546368#*812# is the dial pad code that should be tried in any event.
I just wanted to report that my friend no longer has any more issues with no service. Everything is working well. I will edit my first post to state that the problem is solved and what I did.
Problem is in the title. Here are the Cliff's Notes:
1) got Moto E4 from Textnow
2) fastboot boot TWRP.img (cant recall which image I used but pretty sure it was proper. if this makes a difference I can dig out the TWRP I used and attach it, but I really cannot recall which one it was. Pretty sure I got it from xda though, not the official TWRP page)
3) took TWRP backup of bone-stock device.
4) unlock bootloader at Motorola.com
5) check out the custom roms and found out about the LTE problem. Seanstars fix didnt work for me on several roms, but in his defense I may have done something wrong. I didnt want to mess with it anymore and decided to go back to stock.
6) I found out that I lost my bone-stock-TWRP backup through my own idiocy. I honestly have no idea how I got back to stock but I managed it. Seems to be awful hard to get a stock rom to work with. I must not be looking hard enough but it seems like all the links for Perry stock roms here are dead.
Now to the problem.... after all that I cant get OTA updates. I get notifications, the update downloads,, but no joy.
Device does *not* restart after the update downloads.
Manual restart begins the update process, but then I get the Android on the Operating Table screen. I relocked the bootloader thinking that might be the issue, but now I fear that there is some sort of signature verification issue that is stopping the update.
Trying to give relevant info from the bootloader:
Baseband: M8920_15000.280.06.58.02R PERRY_NA_CA_CUST
Product/Variant: perry XT1766 16GB P3B
I really dont know where to go from here though. Any help is appreciated, thanks in advance.
knoober said:
Problem is in the title. Here are the Cliff's Notes:
1) got Moto E4 from Textnow
2) fastboot boot TWRP.img (cant recall which image I used but pretty sure it was proper. if this makes a difference I can dig out the TWRP I used and attach it, but I really cannot recall which one it was. Pretty sure I got it from xda though, not the official TWRP page)
3) took TWRP backup of bone-stock device.
4) unlock bootloader at Motorola.com
5) check out the custom roms and found out about the LTE problem. Seanstars fix didnt work for me on several roms, but in his defense I may have done something wrong. I didnt want to mess with it anymore and decided to go back to stock.
6) I found out that I lost my bone-stock-TWRP backup through my own idiocy. I honestly have no idea how I got back to stock but I managed it. Seems to be awful hard to get a stock rom to work with. I must not be looking hard enough but it seems like all the links for Perry stock roms here are dead.
Now to the problem.... after all that I cant get OTA updates. I get notifications, the update downloads,, but no joy.
Device does *not* restart after the update downloads.
Manual restart begins the update process, but then I get the Android on the Operating Table screen. I relocked the bootloader thinking that might be the issue, but now I fear that there is some sort of signature verification issue that is stopping the update.
Trying to give relevant info from the bootloader:
Baseband: M8920_15000.280.06.58.02R PERRY_NA_CA_CUST
Product/Variant: perry XT1766 16GB P3B
I really dont know where to go from here though. Any help is appreciated, thanks in advance.
Click to expand...
Click to collapse
A number of partitions need to be pure stock for OTAs to work on Moto devices - including many that are not normally mounted. Likely one or more was altered by previous tinkering. Obviously system (never mounted r/w) and recovery; data must not have had dm-verity disabled. Etc, etc.
I really need help. I don't have a usable phone.
It's a long sad story but I had a working rooted phone with stock Android 9 and Magisk. Because I could not get OTA updates I wanted to update the old version installed, but never succeeded. To make a long story short, since I had a recent Twrp backup so I did a twrp restore.
Rebooting after that caused a boot loop. I finally flashed a stock boot.img using adb and ended with either a boot loop or just the Moto image staying static.
I gave up and decided to do a factory restore.
TWRP is no longer available as recovery. I now get the dead android with red exclamation mark. I got to the options and selected factory restore with wipe user data. Reboot now gives me a static Moto image and nothing further.
I repeated factory restore with wipe user data 2 more times with same result.
How do I get a working phone again?
Please help. Thank you.
Hi there,
I had a similar problem with my phone a few days ago.
Did you try to flash back your stock os with a blank flash? for me this worked, I just had to make sure that ALL files of the Rom image were included in the batch/shell script. For me with a reteu image one was missing (I think the vendor.002 or something like that), otherwise my phone was also stuck at boot.
Maybe that helps! good luck!
Blankflash can be complicated; at least it was for me. Do a Google search, maybe, for LMSA. It's a software program from Lenovo (make sure when you find it that it is lenovos website) and download this app on your windows PC. Normally, and with a little luck, you can put your phone in fastboot mode (it instructs you through all this, too), go-to Restore and LMSA will download the most recent firmware and flash you back to stock. Hope you have some luck! if not I can try to be more helpful with blank / because it took me months to figure out and find a compatible one but I still have it somewhere.
DrHelicopter said:
Hi there,
I had a similar problem with my phone a few days ago.
Did you try to flash back your stock os with a blank flash? for me this worked, I just had to make sure that ALL files of the Rom image were included in the batch/shell script. For me with a reteu image one was missing (I think the vendor.002 or something like that), otherwise my phone was also stuck at boot.
Maybe that helps! good luck!
Click to expand...
Click to collapse
I finally was able to flash stock rom again, re root and restore my apps with Titanium backup. I remembered a partially broken old phone I had and got it working. That relieved the stress of not having a phone and allowed me to work more calmly on my main phone. Still don't know why the twrp restore messed the phone up. Makes me bother why I'm using twrp for backups.
clintongsan said:
Blankflash can be complicated; at least it was for me. Do a Google search, maybe, for LMSA. It's a software program from Lenovo (make sure when you find it that it is lenovos website) and download this app on your windows PC. Normally, and with a little luck, you can put your phone in fastboot mode (it instructs you through all this, too), go-to Restore and LMSA will download the most recent firmware and flash you back to stock. Hope you have some luck! if not I can try to be more helpful with blank / because it took me months to figure out and find a compatible one but I still have it somewhere.
Click to expand...
Click to collapse
I tried LMSA. It had entries for several Moto G7 phones (plus, etc) but not the plain G7. Strange.
maybeme2 said:
I tried LMSA. It had entries for several Moto G7 phones (plus, etc) but not the plain G7. Strange.
Click to expand...
Click to collapse
I don't know if you still want to flash via fastboot, but there is a good guide for the g7 plus here .
You just need the last part, if your bootloader is working. Just keep in mind you need another image from lolinet, the standard G7 is codenamed 'river' as far as i know, so this should be the place for you.
And remember to check if all files (of the extracted image) are included in the 'flashfile.bat' to ensure the flash is complete, otherwise it maybe won't boot.
Hope this helps recovering your phone!
RE:
maybeme2 said:
I tried LMSA. It had entries for several Moto G7 phones (plus, etc) but not the plain G7. Strange.
Click to expand...
Click to collapse
Hmm, okay. That is strange but maybe you have the G7 Plus variant? I don't know that model but the regular G7 is codenamed to (river) xt1962-1. So if you boot into fastboot (from power off; volume down and power held until the fastboot screen appears), look for the third or fourth line down, it will read something like "Product/Variant: river XT1962-1 64GB..." just to ensure that you are looking at the right forum/device. If you are still having issues and if all else does not prove successful, let me know and I can share the blankflash that worked for me along with the best instructions from memory on how I did it. My phone was once bricked to the point where no screen came on at all and I thought it was a goner (actually did it to two seperate G7s as I was learning why Lineage isn't my favorite custom ROM at the time lol) so I know the blankflash I have will work but I would recommend it as a last measure due to the fact that any and all data will be wiped so you won't be able to hold onto anything that is on the device's storage, itself. Hope you got it fixed and wishin you luck!
---------- Post added at 11:13 PM ---------- Previous post was at 11:10 PM ----------
DrHelicopter said:
Hi there,
I had a similar problem with my phone a few days ago.
Did you try to flash back your stock os with a blank flash? for me this worked, I just had to make sure that ALL files of the Rom image were included in the batch/shell script. For me with a reteu image one was missing (I think the vendor.002 or something like that), otherwise my phone was also stuck at boot.
Maybe that helps! good luck!
Click to expand...
Click to collapse
Hey there; do you happen to have a page or website handy that explains blankflash and how the script runs? I remember there being so much confusion over it such as some people had me thinking I needed to find an external firehose program, codes, etc., and as it turned out I only needed the correct blankflash. I was able to fix my devices a couple of months ago but I was just still a bit curious as to the behind-the-scenes details that the software runs in order to be such an awesome fix. Thanks, in advance. Take care!
Fortunately I was finally able to download the latest stock android 9 from Lolinet and flash it to the phone with fastboot. I rooted again with Magisk, flashed copypartitions, and restored my apps and data from a recent Titanium Backup. So I am good now. But, it was very stressful for 2-3 days because I'm not an expert.
Yes the phone is river XT1962-1 64GB, but for some reason my LMSA did not recognize it. Extremely strange but unimportant now since I'm now back in business. I don't know for sure what happened but I suspect it may have had something to do with Moto G7's A / B partitions getting mixed up.
LMSA needs to be updated if there is no Moto g7 option. I just checked on my install and the option was there.
Has anyone ever actually used a TWRP restore? I have tried numerous times to no avail. It's rather annoying but I hope it'll get fixed one day to do backups/restores...same goes for adb backups.
clintongsan said:
Has anyone ever actually used a TWRP restore? I have tried numerous times to no avail. It's rather annoying but I hope it'll get fixed one day to do backups/restores...same goes for adb backups.
Click to expand...
Click to collapse
I've successfully used twrp restores several times on previous phones. Saved me many times. But they were all on Nexus phones and earlier android versions.
The only time I used it on the Moto G7 I got stuck in a bootloop. Maybe it's the newer A B dual partitions causing my problems. Don't know for sure. But without a dependable system restore capability, twrp loses its value to me.
Now I am even afraid to try another twrp restore as a test in case I get thrown back into a boot loop. See my note on
https://forum.xda-developers.com/g7-plus/development/recovery-twrp-3-3-0-moto-g7-plus-t3930050/page9