I installed Lollipop rom after I upgraded to new bootstack. I decided to go back to KitKat, loaded kitkat bootstack and used twrp to restore the backup, but I get the following errors: Error: "Boot certification verify" and "Secure booting Error!"
I have noticed that the bootstack for kitkat comes with tarp 2.8.something. I had 2.7.1 if my memory serves me right. Could that be a culprit? I don't want to go back and reinstall everything. I had T-mobile rooted stock KK rom when I created backup and then I loaded rooted Tmobile LP rom if this helps. Any information on how to fix this would be helpful.
tpaxadpom said:
I installed Lollipop rom after I upgraded to new bootstack. I decided to go back to KitKat, loaded kitkat bootstack and used twrp to restore the backup, but I get the following errors: Error: "Boot certification verify" and "Secure booting Error!"
I have noticed that the bootstack for kitkat comes with tarp 2.8.something. I had 2.7.1 if my memory serves me right. Could that be a culprit? I don't want to go back and reinstall everything. I had T-mobile rooted stock KK rom when I created backup and then I loaded rooted Tmobile LP rom if this helps. Any information on how to fix this would be helpful.
Click to expand...
Click to collapse
go back to stock via kdz method or tot file
thanks for the reply. Are you suggesting flashing the stock first and then trying to do backup restore?
try flashing dorimanx kernel, after restoring your backup..
Related
Should I flash the latest KK image to ensure the modem and bootloader are latest version..
The baseband says: M8974A-AAAANAZM-1.0.190082
I received it with 2.7.0.0 twrp and there were custom rom zips all over.. so I can not tell when it was rooted..
Open to suggestions..
Hey mystique
If you want to start with a clean slate I recommend getting your stock image from here
And use the lg flashtool in the back to stock guide to flash it.
Incidently, since your on twrp 2.7 I assume that you're on the jb boot loader
What was that "phone info tool" to find the bootloader version..
Looks like the device was initially rooted in July 2014..
Assuming that they had kk and such..
I installed Simple ROM Stock lollipop on my D802, and now if I installed KitKat rom my device wont boot up.
WIPE do not solved my problem
What I can do? why?
saarxee said:
I installed Simple ROM Stock lollipop on my D802, and now if I installed KitKat rom my device wont boot up.
WIPE do not solved my problem
What I can do? why?
Click to expand...
Click to collapse
Return to stock: http://forum.xda-developers.com/showthread.php?t=2432476
I do not want to install Stock, I want to install KK custom rom...
and If I install Stock my data was removed and pictures...
saarxee said:
I do not want to install Stock, I want to install KK custom rom...
and If I install Stock my data was removed and pictures...
Click to expand...
Click to collapse
Well did you keep ANY KIND FORM OF BACK UP TO RESTORE BEFORE GOING TO LOLLIPOP?
If not,
1. Returning to stock will bring you back to Stock KitKat ROM.
2. Back up your data and pictures to the cloud or Hard Drive.
3. Download your .kdz file using your IMEI from www.lg-firmware-rom.com
4. Like @raulx222 said, Return to Stock Firmware.
5. CREATE A NANDROID BACKUP.
6. Install your desired custom KitKat ROM.
Give more info please. When you flashed lollipop, which ROM you flashed? you flashed other files too?
Anyway, flashing the stock firmware is almost any time a way to solve the issues ..You could backup your files from TWRP via MTP and then flash the stock firmware. You also can backup your files with TWRP using a usb flash stick and a OTG cable.
restore to kitkat
Hello just flash this attached file in recovery. After that flash jb bootloader for d802 and baseband and recovery you use for roms you use. Everything will work
Btw the zip contains stock kk 20H partitions you need to restore. Simplerom to work on lollipop modify this partiton on your device to be as f320 model in some areas to get lollipop booting
Tell me did you make it boot
Hi, I came from CG3 KK rom then I flashed RR Rom w/c is LP Rom. Can I restore my KK rom directly or do I have to flash something like KK baseband first before restoring my backup? Thanks!
Anyone? Please. Thanks
marshygeek said:
Hi, I came from CG3 KK rom then I flashed RR Rom w/c is LP Rom. Can I restore my KK rom directly or do I have to flash something like KK baseband first before restoring my backup? Thanks!
Click to expand...
Click to collapse
Updating to Lollipop messes with all your initial KitKat partitions. There are 2 solutions to what you're asking.
Solution 1 (SAFE):
It's highly recommended you DON'T just flash a KitKat ROM back onto your device, this will render your device useless. Return to stock KitKat by using the Return To Stock method, then flash your KitKat ROM back over. Doing it this way will first make sure your device has the proper KK partitions. Of course if you have a KK Nandroid back up just flash that back on once you're back on KitKat , and if you don't have a KK Nandroid backup.. just make sure you back up your LP data/media before returning back to stock :victory:.
Solution 2 (UNSAFE, D802 ONLY):
This method unfortunately is only FOR THE D802 by somboons in this thread which I have NOT tested. It involves flashing a .zip to revert your KitKat partitions. More room for errors, but less work. Your call. Obviously if your device is not a D802, don't even attempt this solution, seriously.. just go with Solution 1 .
How to restore KK partitions/flash other ROM (credits to droidth):
- Download this flashable zip: LGG2 -droidth-fixed-KK-partition.zip
- Reboot to recovery and flash LGG2 -droidth-fixed-KK-partition.zip, DONT REBOOT!
- Flash backup or other G2 stock based ROM.
Click to expand...
Click to collapse
d00lz said:
Updating to Lollipop messes with all your initial KitKat partitions. There are 2 solutions to what you're asking.
Solution 1 (SAFE):
It's highly recommended you DON'T just flash a KitKat ROM back onto your device, this will render your device useless. Return to stock KitKat by using the Return To Stock method, then flash your KitKat ROM back over. Doing it this way will first make sure your device has the proper KK partitions. Of course if you have a KK Nandroid back up just flash that back on once you're back on KitKat , and if you don't have a KK Nandroid backup.. just make sure you back up your LP data/media before returning back to stock :victory:.
Solution 2 (UNSAFE, D802 ONLY):
This method unfortunately is only FOR THE D802 by somboons in this thread which I have NOT tested. It involves flashing a .zip to revert your KitKat partitions. More room for errors, but less work. Your call. Obviously if your device is not a D802, don't even attempt this solution, seriously.. just go with Solution 1 .
Click to expand...
Click to collapse
Thank you man. That sums it all. :highfive:
d00lz said:
Updating to Lollipop messes with all your initial KitKat partitions. There are 2 solutions to what you're asking.
Solution 1 (SAFE):
It's highly recommended you DON'T just flash a KitKat ROM back onto your device, this will render your device useless. Return to stock KitKat by using the Return To Stock method, then flash your KitKat ROM back over. Doing it this way will first make sure your device has the proper KK partitions. Of course if you have a KK Nandroid back up just flash that back on once you're back on KitKat , and if you don't have a KK Nandroid backup.. just make sure you back up your LP data/media before returning back to stock :victory:.
Solution 2 (UNSAFE, D802 ONLY):
This method unfortunately is only FOR THE D802 by somboons in this thread which I have NOT tested. It involves flashing a .zip to revert your KitKat partitions. More room for errors, but less work. Your call. Obviously if your device is not a D802, don't even attempt this solution, seriously.. just go with Solution 1 .
Click to expand...
Click to collapse
How can I get into recovery if I flash a lp rom? I think rom delete it and can't get into it neither on download mode.... And got no imei.... I am fu+-ed right?
I decided to check on CloudyG2 LP which requires 20 bootloader which went find. I decided to flash back to stock LP which requires 30b bootloader. After flashing back to stock (30b bootloader and stock zip file) I am stuck at T-Mobile boot screen. It seems like 30b bootloader isn't flashing but I didn't get any errors in TWRP when flashing it. Any suggestions?
Download Mode says 'secure boot error'
I can get into TWRP
I can flash the CloudyG2 rom again and it boots.
I have tried download mode and the LGFlashTool with the kdz as well as the flash tool with the TOT and they both fail.
Did you flash just bootloader or the whole bootstack zip? I would flash the whole stack just in case. We're you on stock lp before cloudy lp and did you make a backup? If you have one, restore it, it should have all the partitions working properly.
I have a Galaxy S4 AT&T i377 UCSGOK3 5.01. I have been fiddling with it and broke the recovery mode. When I select "reboot system now" it reboots, BUT has numerous "Unfortunately...has stopped" errors, finally resulting in unresponsive blank screen. I then have to factory reset and rebuild again. I CAN use recovery mode, IF I remove the battery instead of "reboot system now".
Here are the chain of events leading up this this:
- successfully rooted with Kingroot and replaced with Super SU
- attempted to install TWRP with "Official TWRP App" (I know, should not have done that)
- before attempting TWRP install, made backup of recovery.img (original one) with Official TWRP App
- tried to reinstall original recovery.img with Official TWRP App, Odin, and Flashify. Not working, does not boot into recovery mode.
- installed extracted NB1 recovery.img. From "AT&T Galaxy S4 SGH-I337 UCUFNB1 (Android 4.4.2)" with Odin. This one works, but has the reboot error problem.
Questions:
Is there a Stock AT&T OK3 firmware I can get a recovery.img from or will it still be a NB1 recovery?
Would it be helpful to do a complete re-install of stock firmware? Which one?
Can I install Safestrap on OK3?
Is there a fix for the numerous "Unfortunately...has stopped errors" after recovery reboot?
Thanks in advance,
Todd K.
The bootloader on the phone is locked and cannot run any version of TWRP or any custom ROM that is not based off a stock Samsung ROM.
The reboot problem may be due to a mismatch between the bootloader and recovery.
There is no stock OK3 ROM because AT&T never released a Odin-flashable version of the ROM. OK3 was only offered as an OTA update.
I suggest going back to stock OK3. This thread may help: https://forum.xda-developers.com/showthread.php?t=2616221
The S4 is a great phone and I still have one as my backup phone.
audit13 said:
I suggest going back to stock OK3. This thread may help:
Click to expand...
Click to collapse
Thanks Audit13. just to clarify, Do you suggest sticking with stock OK3 instead of safestrapping to some compatible custom ROM?
For some people, a rooted and no-bloat stock ROM is the most suitable as it's pretty stable and works with many apps.
You can try a custom ROM with safestrap but they'll all be based off a stock ROM which may not run the apps you need.
audit13 said:
For some people, a rooted and no-bloat stock ROM is the most suitable as it's pretty stable and works with many apps.
You can try a custom ROM with safestrap but they'll all be based off a stock ROM which may not run the apps you need.
Click to expand...
Click to collapse
Thanks, I got it to Stock OK3 rooted after a couple of tries. 1st time, I installed the rootable NB1, rooted with towelroot. It wouldn't take the upgrade zips to get from NB1 to OK3. I started over with the plain Stock NB1 ROM, then upgraded in steps from NB1 to OK3, no problem. Then kingrooted and replaced with SuperSU using root.sh script.
I then de-bloated with "System app remover (ROOT)" I wasn't sure what was safe to remove and was afraid of bricking it and having to start over, but it seems to be OK as I was conservative.
Which method do you recommend to de-bloat?
Finally is there a way to do a complete system, app, data, settings backup without CWM/TWRP? Safestrap? ADB? I have Titanium Backup but I don't think it will restore settings and ONLY the apps I want without the bloatware.
Thanks,
Todd K.
I have never owned the sgh-i337 as I'm in Canada and the sgh-i337m (unlocked bootloader, works with TWRP) is the version carried by Canadian carriers.
When dealing with bloatware, I either manually freeze or remove it with Titanium Backup.
toddk63 said:
Thanks, I got it to Stock OK3 rooted after a couple of tries. 1st time, I installed the rootable NB1, rooted with towelroot. It wouldn't take the upgrade zips to get from NB1 to OK3. I started over with the plain Stock NB1 ROM, then upgraded in steps from NB1 to OK3, no problem. Then kingrooted and replaced with SuperSU using root.sh script.
I then de-bloated with "System app remover (ROOT)" I wasn't sure what was safe to remove and was afraid of bricking it and having to start over, but it seems to be OK as I was conservative.
Which method do you recommend to de-bloat?
Finally is there a way to do a complete system, app, data, settings backup without CWM/TWRP? Safestrap? ADB? I have Titanium Backup but I don't think it will restore settings and ONLY the apps I want without the bloatware.
Thanks,
Todd K.
Click to expand...
Click to collapse
I use the mybackup app (formerly called my backup root) to debloat/freeze bloat. It's sort of like titanium backup. You can use flash fire on the play store to do a system backup without safe strap, just using safe strap is better and probably faster.