Develop Bugs

[Q] Please help me get a usable phone again

I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.

tn6 said:
I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.
Click to expand...
Click to collapse
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.

Worked, I think
MrHaPpY66 said:
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.
Click to expand...
Click to collapse
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?

tn6 said:
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?
Click to expand...
Click to collapse
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313

No luck
MrHaPpY66 said:
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313
Click to expand...
Click to collapse
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."

tn6 said:
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."
Click to expand...
Click to collapse
for the supersu, you probably need to go update it on the market or disable KNOX

assert failed... getprop("ro.bootloader")
MrHaPpY66 said:
for the supersu, you probably need to go update it on the market or disable KNOX
Click to expand...
Click to collapse
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?

tn6 said:
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?
Click to expand...
Click to collapse
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help

MrHaPpY66 said:
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help
Click to expand...
Click to collapse
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310

tn6 said:
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310
Click to expand...
Click to collapse
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?

MrHaPpY66 said:
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?
Click to expand...
Click to collapse
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.

resolved
tn6 said:
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.
Click to expand...
Click to collapse
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.

tn6 said:
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.
Click to expand...
Click to collapse
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.

MrHaPpY66 said:
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.
Click to expand...
Click to collapse
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.

tn6 said:
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.
Click to expand...
Click to collapse
so how's the rom so far? probably going to get it myself.

MrHaPpY66 said:
so how's the rom so far? probably going to get it myself.
Click to expand...
Click to collapse
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.

tn6 said:
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.
Click to expand...
Click to collapse
so i see it's a lot better than stock. i'll install it as soon as i can and thanks for the link to the rom

Verizon LG G Pad 8.3 system update

I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work?
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol. How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.

Anthony-m said:
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work? .
Click to expand...
Click to collapse
Simply rooting a device doesn't keep it from TRYing to update via OTA. Rooting can prevent an OTA from succeeding, plus can hard or soft brick if you try to take an OTA, although usually only if you've gone beyond just rooting by installing a custom recovery or changing the contents of any partition besides Data by, fire example, downgrading your bootloader (aboot.img) or modem, running a custom kernel, debloating system apps, etc.
There are at least three variants of the G Pad 8.3. I have the VK810.4G, which do you have?
I know on the VK810.4G, Verizon just released a very, very minor update from LG build #23A to 24A. Still KitKat.
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol.
Click to expand...
Click to collapse
There's the main problem, you had a custom recovery installed. OTAs are applied with the stock recovery, that's why it (probably soft) bricked it.
How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Click to expand...
Click to collapse
You might not be able to fix it from TWRP. You could try @autoprime 's fix recovery zip available the same page his flash2 scripts are. You'll have to Google:
autoprime flash2
Click to expand...
Click to collapse
.
Otherwise, you'll have to restore to 100% stock unrooted and start from scratch. Two methods.
One is using LG's official Mobile Tool, which will download the latest official ROM in KDZ format (takes 20+ minutes to download) and flash it with your tablet in Download mode (probably with the tablet off, hold both up and down volume buttons in and while holding them, turn the tablet on.
I've got to go do something so hopefully someone else will help further or I can get back to you later, dont know when though.
Good luck!
Sent from my VK810 4G

I did the TWRP terminal commands from the thread listed below and it got me right out of that jam...
http://forum.xda-developers.com/lg-g-pad-83/help/vk810-download-mode-boot-loop-t2991512

OK now that I am up and running fine the system update message keeps popping up. This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?

Anthony-m said:
... This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Click to expand...
Click to collapse
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).

DeanGibson said:
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
Click to expand...
Click to collapse
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...

Anthony-m said:
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Click to expand...
Click to collapse
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).

DeanGibson said:
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
Click to expand...
Click to collapse
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.

Anthony-m said:
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Click to expand...
Click to collapse
FYI I just froze the update using Titanium backup pro and my problem is solved for now..

What Steps Do I Take To Update From 2.19.40.20?

So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?

I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.

So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse

Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.

I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse

Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.

DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?

Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.

Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse

Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.

So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?

Made a full root-uninstall on CM12.1 - how to properly re-root?

After successfully flashing CM12.1 and playing around with it a little bit, I wanted to completely remove root (to get a few apps running). So I was advised to download SuperSU and use it to make a full/complete root removal. After that I de-installed SuperSU and disabled root in the Developer Options.
Well, that worked, I could run the apps that were unhappy with just root disabled in Developer Options. But now I want to have root back and I read in a couple of place that just flashing the latest SuperSU.zip from recovery might be a bad idea.
Any suggestions how to properly re-root my CM12.1 ?

aalemann said:
After successfully flashing CM12.1 and playing around with it a little bit, I wanted to completely remove root (to get a few apps running). So I was advised to download SuperSU and use it to make a full/complete root removal. After that I de-installed SuperSU and disabled root in the Developer Options.
Well, that worked, I could run the apps that were unhappy with just root disabled in Developer Options. But now I want to have root back and I read in a couple of place that just flashing the latest SuperSU.zip from recovery might be a bad idea.
Any suggestions how to properly re-root my CM12.1 ?
Click to expand...
Click to collapse
Not sure what would be bad about it. If it's an issue with latest version, just use 2.46

levone1 said:
Not sure what would be bad about it. If it's an issue with latest version, just use 2.46
Click to expand...
Click to collapse
ok, thanks for the prompt answer! I am currently trying to find where I read this..... anyway, will then probably just flash it and see if it works

aalemann said:
ok, thanks for the prompt answer! I am currently trying to find where I read this..... anyway, will then probably just flash it and see if it works
Click to expand...
Click to collapse
https://download.chainfire.eu/696/supersu/

levone1 said:
https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
this is exactly the version I flashed onto my CM12.1, worked flawlessly

SafetyNet FAILED after stock rom and relocked bootloader? (Cant use Google Pay)

I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?

ntelas said:
I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?
Click to expand...
Click to collapse
Just an idea, take a look at your build.prop and see if anything looks off. Maybe you need to format some partitions before flashing the stock zip?
Cheers!

Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?

ntelas said:
Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?
Click to expand...
Click to collapse
I think that certain partitions need to be formatted you might want to search about that. I think TWRP can access the build.prop but not sure. I suggested checking build.prop because it will show different models, builds and basically would be an easy way to see if you are truly back to stock.
Good luck!

Thanks! I would have to install TWRP again maybe ?

ntelas said:
Thanks! I would have to install TWRP again maybe
Click to expand...
Click to collapse
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.

uweork said:
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.
Click to expand...
Click to collapse
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive

ntelas said:
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive
Click to expand...
Click to collapse
Then You didn´t read Properly.
I didn´t mean Root itself more Remnant parts of Root, that cause ur Saftynet fail.
on Samsung S2 once i thought so too, but banking app said no no no...
Only an Option

a user from this forum said that you need to take the line "ro.build.firgenprint=..." of the any MM/LP build.prop and insert it into the N build.prop (including reboot btw) and try again if google pay works for you...
I don't know if it works, I don't tried it, but you say us.