Related
Thought I'd share my experience in case it would help anyone.
Got a good deal on a new used US Cellular version tab. Hadn't come here yet to check things figuring all tabs would be the same.... wrong obviously.
First, because not everyone necessarily clearly mentions the difference between the GSM and CDMA versions, I almost went down the wrong path and tried to load a GSM rom. Caught that luckily in time. Rooting sucked as Kies would not, with 6 different computers and just as many different versions of Kies, recognize my device. Luckily I stumbled on the Z4root app which worked great.
All is good, but of course, no one mentions the us cellular version at all when it comes to roms. Studied up and noticed the model numbers and specs between us cellular version and verizon version matched. Great. Loaded beta clockwork mod for verizon, but only the stock recovery would come up when I tried to get into recovery.
Decided to load the voodoo kernal for cdma verizon. This is where it got ugly. Wouldn't convert partition to ext4 and just sat there. Took creators advice and booted into recovery. Suprisingly, it now went to the clockwork mod recovery, but nothing I did there helped, so I rebooted into recovery from clockwork mod recovery as per the instructions so I could do a data wipe and factory reset. Not all I had was a boot loop and it would no longer even go into recovery. Pretty sure I was screwed at this point. Only thing I had going for me was that I could still get into download mode. Got lucky and found the files necessary to go to bone stock verizon vie heimdall. Loaded them up and rebooted. A little hairy, but then I had a running system again. Since I knew I could always redo that, I decided to load the voodoo kernal again and this time it worked (maybe because my system was now basically verizon???).
Anyways, if anyone needs the files to go back to stock, I do have them and would be more than willing to share. I know one thing, if it wasn't for the wealth of information here I would have a bricked tab right now.
So I just bought a used US Cellular tab and wish I'd understood there would be issues.
I just rooted via z4Root as well and now don't know what to do. Were you able to flash any ROMs after getting into recovery? I'd imagine Verizon Roms might work?
I don't care about cellular data as I'm using it as wifi only.
Would you be kind enough to share the stock rom you mentioned? I've run into problems restoring my US Cellular GT. Thanks!
This is the exact same thing that happened to me as well except that I have a vzw tab.
I used sgs kernal to flash which went successful then tried to load a rom through cwm and got stuck in the boot screen.
I was able to go into download mode but had no idea how to use heimdall nor did I know what files I needed.
Luckly I bought through vzw 13 days ago so I just went in and exhanged it.
Wanna try again but would like to have the stock files needed to restore my tab in case I soft brick it again.
Can you please email me the files to [email protected]???
Yes please share the stock files
I would also like to request stock file as well. Thanks!!!!
Over the weekend my Nexus 4 decided not to start. Saturday night it was working, and I hooked it up to charge. By Sunday morning it had turned off. When I restarted it, it got as far as asking for my password (encryption key), and then the four circles just danced around for hours. After letting it sit for a few days, the phone started again. But the experience made me decide it was time to update the system from Kit Kat.
So, more or less, I followed the instructions on the Team Android site. (As a new member of this forum, I'm not allowed to include the link. But Google "Update Nexus 4 to Android 6.0.1 Pure Nexus Project Marshmallow Custom ROM.") The main differences were (1) I only copied the ROM file over and (2) I used TWRP instead of CWM for the recovery. I was having trouble copying the Gapps file, so I thought it would be easier to install Marshmallow first and do the apps later.
Everything was backed up and copied around 7 PM yesterday, when I then wiped the data, did a factory reset, wiped the cache, wiped the dalvik cache, and finally started the installation. It's now almost 1 AM, and the ROM is still being flashed.
What should I do next?
Well it seems like the ROM you downloaded is a corrupt zip file.
I would like you to go to Original Development and download one of the ROMS from there, and then google opengapps, choose, ARM>6.0.1>Pico package (or any other package of your choice). I recommend Pico for your first install which is barebones google play services and Google Play store.
TWRP is perfectly compatible with most recent roms.
And for 6.0.1 , Flash the ROM and then flash GAPPS right away. After flashing, wipe dalvik/cache and then reboot.
If you have any questions, do not hesitate to post them here. good luck
EDIT: If you want Vanilla android with zero modifications, get this one:
http://forum.xda-developers.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900
Also, if it helps, I got 4 hours of Screen On Time on this ROM, I never got it on any other ROM so it is very light and is exactly what you would be getting on a nexus device.
mohsinkhan35 said:
Well it seems like the ROM you downloaded is a corrupt zip file.
I would like you to go to Original Development and download one of the ROMS from there, and then google opengapps, choose, ARM>6.0.1>Pico package (or any other package of your choice). I recommend Pico for your first install which is barebones google play services and Google Play store.
TWRP is perfectly compatible with most recent roms.
And for 6.0.1 , Flash the ROM and then flash GAPPS right away. After flashing, wipe dalvik/cache and then reboot.
If you have any questions, do not hesitate to post them here. good luck
EDIT: If you want Vanilla android with zero modifications, get this one:
http://forum.xda-developers.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900
Also, if it helps, I got 4 hours of Screen On Time on this ROM, I never got it on any other ROM so it is very light and is exactly what you would be getting on a nexus device.
Click to expand...
Click to collapse
Thanks, Mohsinkhan35. I followed the link you included and downloaded the ROM and TWRP 3.0.0-0, as the site requires. (I currently have TWRP 2.7.1.0 installed.) I was unable to download the Pico Gapp from that site, since the link seems to be broken. No problem. It's available from lots of locations.
So, as I understand it, my first step should be updating TWRP. I found instructions on how to do this at PhoneArena.com. Although written for Windows users, basically one starts the phone in bootloader mode and then uses adp commands to flash the new recovery (TWRP file).
But now Android File Transfer is not connecting to the phone. I wouldn't expect it to connect if the phone wasn't booted, as the file system is encrypted. Nonetheless, I tried this way without success. Then I tried using bootloader mode, with similar results. I then booted up in RM and got into TWRP, but AFT still doesn't see the phone. This is not altogether unexpected. If the new OS has settings and drivers to connect to my computer (a Yosemite iMac), and I've wiped the old one to make way for the new install, then how can the phone communicate with the PC?
For each of these cases (normal start, bootloader, and RM), I also tried issuing "adb devices" from a command prompt, but it's also returning nothing.
So any suggestions for the next step?
Von Neumann said:
Thanks, Mohsinkhan35. I followed the link you included and downloaded the ROM and TWRP 3.0.0-0, as the site requires. (I currently have TWRP 2.7.1.0 installed.) I was unable to download the Pico Gapp from that site, since the link seems to be broken. No problem. It's available from lots of locations.
So, as I understand it, my first step should be updating TWRP. I found instructions on how to do this at PhoneArena.com. Although written for Windows users, basically one starts the phone in bootloader mode and then uses adp commands to flash the new recovery (TWRP file).
But now Android File Transfer is not connecting to the phone. I wouldn't expect it to connect if the phone wasn't booted, as the file system is encrypted. Nonetheless, I tried this way without success. Then I tried using bootloader mode, with similar results. I then booted up in RM and got into TWRP, but AFT still doesn't see the phone. This is not altogether unexpected. If the new OS has settings and drivers to connect to my computer (a Yosemite iMac), and I've wiped the old one to make way for the new install, then how can the phone communicate with the PC?
For each of these cases (normal start, bootloader, and RM), I also tried issuing "adb devices" from a command prompt, but it's also returning nothing.
So any suggestions for the next step?
Click to expand...
Click to collapse
NEVERMIND!!!!
Experimenting with several different USB cords and ports finally yielded a good connection! Even a native USB port on the back of the iMac didn't work, and neither did some of the ports on my USB 3.0 (2.0 compatible) hub. But finally one worked, and I ran with it. Currently reinstalling my apps on the shiny new Marshmallow system!
THANKS Mohsinkhan35!!!!!
Von Neumann said:
NEVERMIND!!!!
Experimenting with several different USB cords and ports finally yielded a good connection! Even a native USB port on the back of the iMac didn't work, and neither did some of the ports on my USB 3.0 (2.0 compatible) hub. But finally one worked, and I ran with it. Currently reinstalling my apps on the shiny new Marshmallow system!
THANKS Mohsinkhan35!!!!!
Click to expand...
Click to collapse
Sorry about the late reply Von I just saw your replies, I am glad that you got it to work!!
For Future purposes, The easiest way to update TWRP is to download the .img from TWRP, put it on your phone, go to TWRP recovery, and instead of flashing .zip file, choose .img from dropdown list, then select the image file, select recovery option from the list.
Enjoy your new system! Which MarshMallow ROM did you end up flashing?
I found that MM breathe a new life into my Nexus, can't imagine going back to Lollipop, I don't know how you managed to stay with KitKat haha
Greetings,
I need some help. I purchased OneClickRoot for my Verizon S5. Everything went swimmingly right up until it didn't. I got root after several hours with the oneclick tech team. he gave me instructions on how to flash a ROM, but left out the apparently important step where I should have skipped the signature verification. So I had SafeStrap, wiped everything and tried to flash an unsigned ROM. now the phone is dead wit no OS and seemingly no ability to get back to safestrap. Should I just toss this phone in the rubbish and buy a new one or can it be saved? When I boot to recovery, it is Android recovery and it keeps failing on the verification.
All advice is welcome.
Doug M.
dwmackay said:
Greetings,
I need some help. I purchased OneClickRoot for my Verizon S5. Everything went swimmingly right up until it didn't. I got root after several hours with the oneclick tech team. he gave me instructions on how to flash a ROM, but left out the apparently important step where I should have skipped the signature verification. So I had SafeStrap, wiped everything and tried to flash an unsigned ROM. now the phone is dead wit no OS and seemingly no ability to get back to safestrap. Should I just toss this phone in the rubbish and buy a new one or can it be saved? When I boot to recovery, it is Android recovery and it keeps failing on the verification.
All advice is welcome.
Doug M.
Click to expand...
Click to collapse
I'm unfamiliar with Verizon variants, but have you tried using Odin to flash the original stock?
https://forum.xda-developers.com/showthread.php?t=2784880
Sent from my Samsung SM-G900I using XDA Labs
Yea dude as long as you can get into download mode (or Odin mode whatever you feel like calling it) you're fine just flash whatever version you feel like being on and I would follow these instructions for root and ROMs and possible bootloader unlock since it's Verizon https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
So Close!!
Thanks for the help. I followed this guide ( https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529) and got it back; ...sort-of.
In Step 13, I used the 6.0 firmware.
In Step 14 I used the "latest stock rooted Lollipop Rom" that was recommended.
I have what appears to be a rooted 5.0 factory rom installed. However, when booting, I get process stopped errors for the first 2 minutes. Maybe 15 or 20 of them. After that, they stop.
Current Problems:
1) the radios are dead. Wi-Fi will not turn on and it does not know that my SIM card is installed
2) when the screen times-out I have to pull the battery to get it back.
3) All the error messages (android.process.media)
4) It does not see the SD card
Questions:
A) Can you help me fix the radio problems?
B) Once I get the radios working again, can I flash any G900V ROM with safestrap and it will likely solve 2, 3 &4?
C) Are the custom roms on 6.0 and higher rooted? I was looking at this one (https://forum.xda-developers.com/galaxy-s5/unified-development/rom-cosmic-os-3-1-t3553838)
Thanks for any assistance you can provide.
Idk if i can help bt i can try haha Well first thing first it sounds like you used marshmallow firmware but then flashed a lollipop ROM which yes it will boot up bt stuff like your radio and GPS, etc won't work so first thing is first i would say is do a complete wipe and get your self back to stock through Odin and get everything working first before worrying about ROMs then I have to ask is what is what is your emmc are you 15 (bootloader unlock and can easily root 6.0.1 or higher) or emmc 11 (can only root 5.0)
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.
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Smellfungus said:
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Click to expand...
Click to collapse
The only way I know of to successfully root a Tab A is by flashing TWRP and then using it to flash SU or Magisk. What version of TWRP are you using and what version of Odin? Using the correct ones won't brick a T585.
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
webzo said:
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
Click to expand...
Click to collapse
I honestly don't remember
But it should work on either one - only difference now is that we have an official recovery that can be downloaded from twrp.me directly :highfive:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
webzo said:
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
Click to expand...
Click to collapse
Update:
I tried to restore the backup via TWRP and ended up with a "unable to mount /system" error.
My /system partition was showing zero size.
Many wipes and restores didn't help.
Eventually, what seemed to help was to choose repair the system partition, change file system to FAT, change file system back to ext4. Saw it in a youtube video- https://www.youtube.com/watch?v=T-7neHzSIvc
After /system error was fixed, I did an install of RR again and it went smooth.
All is well now.
Hope this helps someone.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Back then we had no working official version and the Omni6 one was the only one without issues. Now we have the official and it should work just fine.
No idea why you had those problems, but I'm glad you got it all sorted