I tried to update my brothers phone to 4.4 from 12B because he kept saying that it would try to update but would fail which I didn't understand why because he only had root but that's not the problem. I installed TWRP and made a backup right away. I then installed the boot stack from this thread http://forum.xda-developers.com/showthread.php?t=2715408 then rebooted and was bootlooping. So, I put it in recovery mode and think I probably messed something up so I'll just restore the backup I made. I restore it and everything is looking good no errors or anything until I go to reboot it and it's still bootlooping. I'm stuck here because everything I've tried has failed.
I recommend following the restore to stock instructions (the tot method going to 11a then OTA to 12b) in the general section. Then use Cloudy's Malidus 2.0.2 files to update to 4.4.2.
Sent from my VS980 4G using Tapatalk
Related
So i just got a brand new LG G2 , wanted to start straight with a custom rom, read that it was safest to take the 11A onwards route to be safe cause the new way the bootloader is flashed may cause hardware issues.
So i flash the11A tot
Root using IOroot
install PhilZ recovery using Flashify
then from recovery pushed the 11A to 24A zip.
i tried installing the Malladus rom however it completed in 5 seconds and i dont think it really flashed
Rebooted to TWRP ( Which i suppose came from the malladus) tried the same, ofcourse did the factory rest too , still the same
Then tried sideloading which gave me the error code 7
tried another file which just didnt push itself
What am i doing wrong here , if someone could shed some light the best way to get from 11A to kitkat would be much appreciated.
i have installed the TOT now back to 11A.
nm figured it out , had to reboot recovery post updating the bootloader for kitkat
Ok, so I tried following the method described here:
http://forum.xda-developers.com/showthread.php?t=2712039
I was on JB. Installed SS 3.71, downloaded the odexed version of UrDroid and odin files.
Procedure I followed:
Booted into SS
Factory reset
Install urdroid - deodexed
Installation failed, zip wouldn't open
Booted back up, downloaded urdroid again - odexed version this time
pulled battery, booted to safestrap
factory reset
install new zip, worked this time
tried booting to download mode with vol down key, didn't work for some reason. just went to SS splash screen then tried to boot
pulled battery, booted SS again, used the reboot menu to get to download mode
followed steps to set up partitions in ODIN, seemed to work fine
Now when I try to boot it just shows me the SS splash screen, then when I let it boot it just goes to a black screen with a solid blue indicator LED.
Next, I tried to verify the MD5 on the UrDroid zip and it didn't match. I downloaded it again, copied it to my external SD, and it then checked out.
Wiped, installed, ran the odin stuff again. Same problem.
I'm guessing the next step is to restore it back to MJ5 using this method: http://forum.xda-developers.com/showthread.php?t=2559715&page=118
Except several of the files linked there are no longer available....
I'm feeling a little panicked now, this is my only phone lol. Can anyone give me a hand?
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
andygev35 said:
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
Click to expand...
Click to collapse
I thought that once you update to KK, you can't go back to JB... except I don't know if I ever completed the update. I'm not entirely sure how this process even works.
Do you flash the rom, and then the ODIN portion of it prepares your phone for KK?
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
andygev35 said:
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
Click to expand...
Click to collapse
First of all, thank you for your help.
In recovery, it just says "Android system recovery <3e>". Then goes down to the options you can select.
Before you posted, I tried installing a MJ5 custom rom (FireNote) in the stock slot and now it successfully boots. Which is certainly an improvement. I tried the same process again with UrDroid and had the same result as before - no boot. Now I'm back on FireNote again.
Since FireNote works fine, is it safe to conclude that the Odin process did not properly prepare my boot system for KitKat, and that is why the KK rom isn't working at all?
Have I stumped XDA?? Haha.
I went over the guide again and can't see anything that I've done wrong, but I certainly could have. Are there glitches in Odin3 with Windows 7 that I should be looking out for or anything?
Another thought: I was attempting to do this with SafeStrap 3.71 installed. I thought that 3.72 should be sideloaded after I had switched to KitKat. Was this incorrect? Should I have started by installing 3.72 in my JB rom?
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
steveh_131 said:
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
Click to expand...
Click to collapse
I wouldn't say you're an idiot. You're human!
Let me start by saying that after the error, through the use of the power and volume down buttons (the timing was different, seemed a little slower, if that makes sense), I was able to get my phone to boot into TWRP and restore the nandroid I made just prior to the error, so I'm up and running fine. What I don't understand is 1.) Why it happened and 2.) How to restore my other nandroid.
After flashing xdabbeb's 26A Bootstack and his VS982.5 ROM and all was running well, I wanted to go back to my nandroid prior to flashing the VS982.5, which is simply the stock Verizon ROM on 25b. I made a backup of VS982.5, then went and restored my previous stock backup. After I restored my stock backup, I got the following error when I tried to boot, and then the phone would go black.
boot certification verify
--------------------------------
secure booting error!
cause: boot certification verify
Based on the other threads I have read regarding the error, it seems like I was very lucky to get back into recovery. Can anyone tell me why this happened so I understand what I did wrong and avoid it in the future and what I might be able to do to restore my previous backup should I want or need to go back to Stock?
I didn't think this was specific to xdabbeb's ROM so I put it under general help instead.
wrswldo said:
Let me start by saying that after the error, through the use of the power and volume down buttons (the timing was different, seemed a little slower, if that makes sense), I was able to get my phone to boot into TWRP and restore the nandroid I made just prior to the error, so I'm up and running fine. What I don't understand is 1.) Why it happened and 2.) How to restore my other nandroid.
After flashing xdabbeb's 26A Bootstack and his VS982.5 ROM and all was running well, I wanted to go back to my nandroid prior to flashing the VS982.5, which is simply the stock Verizon ROM on 25b. I made a backup of VS982.5, then went and restored my previous stock backup. After I restored my stock backup, I got the following error when I tried to boot, and then the phone would go black.
boot certification verify
--------------------------------
secure booting error!
cause: boot certification verify
Based on the other threads I have read regarding the error, it seems like I was very lucky to get back into recovery. Can anyone tell me why this happened so I understand what I did wrong and avoid it in the future and what I might be able to do to restore my previous backup should I want or need to go back to Stock?
I didn't think this was specific to xdabbeb's ROM so I put it under general help instead.
Click to expand...
Click to collapse
I believe it's because your 25b isn't bumped. Xdabbeb's newest ROM is bumped. You'll have to downgrade to non-bumped kernel to restore that backup.
Fixed it?
wrswldo said:
Let me start by saying that after the error, through the use of the power and volume down buttons (the timing was different, seemed a little slower, if that makes sense), I was able to get my phone to boot into TWRP and restore the nandroid I made just prior to the error, so I'm up and running fine. What I don't understand is 1.) Why it happened and 2.) How to restore my other nandroid.
After flashing xdabbeb's 26A Bootstack and his VS982.5 ROM and all was running well, I wanted to go back to my nandroid prior to flashing the VS982.5, which is simply the stock Verizon ROM on 25b. I made a backup of VS982.5, then went and restored my previous stock backup. After I restored my stock backup, I got the following error when I tried to boot, and then the phone would go black.
boot certification verify
--------------------------------
secure booting error!
cause: boot certification verify
Based on the other threads I have read regarding the error, it seems like I was very lucky to get back into recovery. Can anyone tell me why this happened so I understand what I did wrong and avoid it in the future and what I might be able to do to restore my previous backup should I want or need to go back to Stock?
I didn't think this was specific to xdabbeb's ROM so I put it under general help instead.
Click to expand...
Click to collapse
Were you able to fix this? I did a similar thing. I am stuck on the on the black screen and can't in recovery.
Thanks!
So I had root on 4.4.2 with busybox and safestrap. I attempted to flash the OC1 file which is the stock 5.0 rooted lollipop, but it failed. Now my phone boots and shows the paddle lock boot screen, but bypasses safe strap and goes into an Android system recovery withe the android guy. Ive tried to target my original backup, but it fails. I'm going into the twrp directory on my external storage that has the stock backup, but when i click it, it opens and shows 4 md5 files.
data.ext4.win000.md5
data.ext4.win001.md5
system.ext4.win000.md5
system.ext4.win001.md5
Is there a way to get the phone to boot? I've just tried to wipe data as well but it connects to odin for a few seconds, then goes into removed status when it goes into Android System Recovery <3e>.
Have u flashed the twrp recovery?
Sent from my A0001 using XDA Free mobile app
i was able to get it to boot to ODIN and i just put it back to 4.4.2. After root, I'll dig into the forums to see what i did wrong. I'd like to use the stock lollipop rooted but safestrap kept failing when it was verifying the partition.
lesd777 said:
i was able to get it to boot to ODIN and i just put it back to 4.4.2. After root, I'll dig into the forums to see what i did wrong. I'd like to use the stock lollipop rooted but safestrap kept failing when it was verifying the partition.
Click to expand...
Click to collapse
Did you make sure to flash the lollipop kernel in safestrap before rebooting? You can't use regular twrp on our locked bootloader, so safestrap and flashfire are the only options. But safestrap doesn't work out the door with L, so you have to use flashfire or the safestrap workaround. Make sure you read, read, and read some more to get where you're trying to go. Good luck.
Ok a little backstory. So I just got a Verizon G2 and put it on Straight Talk, everything works great.
I rooted via Stump Root. I was on Version 27A
Installed TWRP via AutoRec
Flashed the latest CM for the VS980
Flashed gapps
Gapps install failed, now I get the LG splash screen, then just a black screen. Phone won't boot or anything. Any thoughts on what happened or what to do?
This is the link tot he gapps I downloaded and tried to install. http://opengapps.org/?api=6.0&variant=nano
The options I chose were:
ARM
Android 4.4
Full
If I need to go back to stock, I need to know what the latest version is that I need to flash for the TOT file.
Currently in the process of going back to stock via LG Flash Tool. Nothing is working. Returning the phone to stock is not working. On the phone itself it just gets stuck at 1% and doesn't move when I choose "CSE Flash." When I choose "Normal Flash" it's just stuck at 0% and doesn't move. It doesn't fail, but it doesn't move either.
For reference I was on 27A and am trying to restore 24A
Phone is restoring now after using the TOT method to restore 24A, and changing the model dll to the LGUP dll file.