Hi all, is it possible to have a kernel of the previous system build [9.16.1] that can be flashed through safe strap recovery, so that afterwards we may unlock our bootloader,?
Unknown1981 said:
Hi all, is it possible to have a kernel of the previous system build [9.16.1] that can be flashed through safe strap recovery, so that afterwards we may unlock our bootloader,?
Click to expand...
Click to collapse
Nope, there was an exploit in the tz partition to unlock but that's been patched now. You can't flash different kernels or downgrade anything but the system partition. Trying to will likely land you hardbricked
Sent from my XT907 using Tapatalk
Wraith is correct, you can't flash a kernel on a locked BL.
Thanx for the help, well on optimus g i have flashed both rom and kernel on the locked bootloader, through 2nd init cwm recovery.
Related
Hi... im currently running
CROMi-X v5.2.2, which is based on rom 10.6.1.27.5 with twrp 2.5.0.0 and my bootloader says is the one that came with us10.6.1.15.3-20130416...
To install omni kitkat, im been asked to have the latest bootloader, to avoid screwing up im planning on insalling the latest stock from asus...
However, each time i install a stock through twrp or cwr, the new image not only updates the bootloader and deletes all my data, but rewrites my recovery, for which then i have too reupload using fastboot to upload the recovery...
Is there any way to make sure i dont loose the recovery after flashing a stock firmware... or a way to flash the recovery from the recovery before rebooting after flashing the stock?
Thanks everyone!
mertonv said:
Hi... im currently running
CROMi-X v5.2.2, which is based on rom 10.6.1.27.5 with twrp 2.5.0.0 and my bootloader says is the one that came with us10.6.1.15.3-20130416...
To install omni kitkat, im been asked to have the latest bootloader, to avoid screwing up im planning on insalling the latest stock from asus...
However, each time i install a stock through twrp or cwr, the new image not only updates the bootloader and deletes all my data, but rewrites my recovery, for which then i have too reupload using fastboot to upload the recovery...
Is there any way to make sure i dont loose the recovery after flashing a stock firmware... or a way to flash the recovery from the recovery before rebooting after flashing the stock?
Thanks everyone!
Click to expand...
Click to collapse
Flashing the stock ROM reverts the tablet back to stock, so the recovery must go. Luckily, the bootloader you are on is compatible with the KitKat recovery (10.6.1.15.3) so you shouldnt have to flash the stock ROM at all. If you were on 10.6.1.8, you would have had to upgrade.
cmendonc2 said:
Flashing the stock ROM reverts the tablet back to stock, so the recovery must go. Luckily, the bootloader you are on is compatible with the KitKat recovery (10.6.1.15.3) so you shouldnt have to flash the stock ROM at all. If you were on 10.6.1.8, you would have had to upgrade.
Click to expand...
Click to collapse
Thanks, then guess i only need to flash the kitkat twrp...
Asked the same question about my bootloader at the omni thread to be sure, if they say that it works too, will go ahead and give it a try
I read somewhere that TWRP allows you to flash custom kernels on a locked bootloader . So I'm wondering if it's possible to flash CM or a custom kernel on a LG MS769 with a locked bootloader without possibly bricking the phone???
Sent from my LGMS769
Cj2114 said:
I read somewhere that TWRP allows you to flash custom kernels on a locked bootloader . So I'm wondering if it's possible to flash CM or a custom kernel on a LG MS769 with a locked bootloader without possibly bricking the phone???
Sent from my LGMS769
Click to expand...
Click to collapse
Hi
Short answer : NO
Regards
Hey all,
Its been a while since I have messed around with my XT926 and I am having some trouble flashing a 4.1.2 ROM on it. What I've done so far is to RSDLite to a 4.4.2 build (one that is still compatible with boot loader unlock) and unlocked the boot loader. I was having trouble getting a recovery to flash other than epinters cwm and twrp 2.8. I tried flashing nexesue v3.6 in both recoveries but am stuck on the Motorola symbol on blot. If I RSDLite back to a 4.1.2 build can I then flash an older recovery and then the ROM?
EDIT: phone is also rooted using towelroot.
Any help is appreciated.
DID you try twrp 7.1.0?
lysdexik said:
Hey all,
Its been a while since I have messed around with my XT926 and I am having some trouble flashing a 4.1.2 ROM on it. What I've done so far is to RSDLite to a 4.4.2 build (one that is still compatible with boot loader unlock) and unlocked the boot loader. I was having trouble getting a recovery to flash other than epinters cwm and twrp 2.8. I tried flashing nexesue v3.6 in both recoveries but am stuck on the Motorola symbol on blot. If I RSDLite back to a 4.1.2 build can I then flash an older recovery and then the ROM?
EDIT: phone is also rooted using towelroot.
Any help is appreciated.
Click to expand...
Click to collapse
See my post, had problem to install Nexesque too, but had success with specific CWM version. Also try to wipe all and flash boot.img as the op in Nexesque has stated.
http://forum.xda-developers.com/showpost.php?p=55752257&postcount=170
Hi,
I am currently running Zombi-pop 5.02 B4 and has TWRP 2.8.7 Kang on my TF700T. I would like to have nvflash access, can I downgrade to a JB stock version that allows such access? and if yes which stock rom and which boot loader?
many thanks
satnile said:
I am currently running Zombi-pop 5.02 B4 and has TWRP 2.8.7 Kang on my TF700T. I would like to have nvflash access, can I downgrade to a JB stock version that allows such access? and if yes which stock rom and which boot loader?
Click to expand...
Click to collapse
You don't need to downgrade, you can install the flatline recovery, pull your blobs, then reinstall TWRP.
_that said:
You don't need to downgrade, you can install the flatline recovery, pull your blobs, then reinstall TWRP.
Click to expand...
Click to collapse
Really, this is helpful. I was under the impression that a stock JB boot loader is required for nvflash to work. I shall give it a try and report back.
Many thanks
I have successfully done the nvflash access and generated the blobs for my TF700T and stored them in triplicates. My question now is that I have been left with AndroidRoot 10.6.1.14.4 bootloader and a primitive flatline recovery, can I flash TWRP Kang 2.8.6.0 back without problem?
many thanks once again.
Congrats! Yes, flash TWRP kang, reboot, then flash the stock bootloader from here: http://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
Reboot
All is good
Flatline CWM recovery couldn't flash the zips for bootloader and TWRP Kang, so I flashed the TWRP img via fstboot first, then booted into TWRP recovery and flashed the bootloader zip and it worked fine, no bricking whatsoever.
Hi all i just bought this mobile and i was curious to know if it was possible to install a custom rom.
I saw that the downgrade is the only solution to root and install custom recovery.
In my case i wish to know which file i have to flash with flashtool.
Thanks all
http://forum.xda-developers.com/showthread.php?t=3017056
You just have to follow this Guide...
Gesendet von meinem D6603 mit Tapatalk
My Z3 is totally stock i didn't made any backup and save of DRM TA etc. can i do the downgrade anyway?
Thanks
PdorITA said:
My Z3 is totally stock i didn't made any backup and save of DRM TA etc. can i do the downgrade anyway?
Thanks
Click to expand...
Click to collapse
Yes
Update:
Downgrade --> Done
Root and DualRecovery--> Done
Backup DRM TA --> done
Bootloader Unlock --> Done
I'm trying to flash custom room rebooting in Teamwin recovery the flash goes perfect but after when i reboot the Z3 it goes in boot loop and i can enter only in the recovery the Z3 won't start at all.
I've tryied with 2 custom ROm and the original rom lollipop rooted and patched.
What i do wrong? I just put the custom rom in the Micro-sd card and i flash it using the teamwin recovery (before i wipe cache and Dalvik). Do i have to flash before the boot.img?
Thanks
PdorITA said:
Update:
Downgrade --> Done
Root and DualRecovery--> Done
Backup DRM TA --> done
Bootloader Unlock --> Done
I'm trying to flash custom room rebooting in Teamwin recovery the flash goes perfect but after when i reboot the Z3 it goes in boot loop and i can enter only in the recovery the Z3 won't start at all.
I've tryied with 2 custom ROm and the original rom lollipop rooted and patched.
What i do wrong? I just put the custom rom in the Micro-sd card and i flash it using the teamwin recovery (before i wipe cache and Dalvik). Do i have to flash before the boot.img?
Thanks
Click to expand...
Click to collapse
You are either flashing an incompatible custom ROM or your boot loader is not unlocked.
Flash a stock FTF again, then goto the dialer and dial *#*#7378423#*#* then goto service info, configuration and post here what it says in the rooting status.
gregbradley said:
You are either flashing an incompatible custom ROM or your boot loader is not unlocked.
Flash a stock FTF again, then goto the dialer and dial *#*#7378423#*#* then goto service info, configuration and post here what it says in the rooting status.
Click to expand...
Click to collapse
Screenshot:
http://dl-1.va.us.xda-developers.com/3/6/5/9/4/7/7/Screenshot_2016-02-25-14-31-22.jpg?key=GrIQDs1awaejgcECU90NhA&ts=1456407354http://
ROM: http://forum.xda-developers.com/z3/development/d6603-23-1-1-28-t3102271
ROM2: http://forum.xda-developers.com/z3/development/rom-existenz-y-1-0-0-02-07-t3148877
PdorITA said:
Screenshot:
http://dl-1.va.us.xda-developers.com/3/6/5/9/4/7/7/Screenshot_2016-02-25-14-31-22.jpg?key=GrIQDs1awaejgcECU90NhA&ts=1456407354http://
ROM: http://forum.xda-developers.com/z3/development/d6603-23-1-1-28-t3102271
ROM2: http://forum.xda-developers.com/z3/development/rom-existenz-y-1-0-0-02-07-t3148877
Click to expand...
Click to collapse
Well, neither of those require an unlocked bootloader, but that should not make a difference.
What boot.img are you flashing, both of those ROMs require a stock kernel.
gregbradley said:
Well, neither of those require an unlocked bootloader, but that should not make a difference.
What boot.img are you flashing, both of those ROMs require a stock kernel.
Click to expand...
Click to collapse
at moment i have a 4.4.4 stock rooted http://dl-1.va.us.xda-developers.com/3/6/5/9/5/7/4/Screenshot_2016-02-25-15-46-09.jpg?key=4YW3-mNtbisUcXLWsSrQ_g&ts=1456411770
Which procedure i have to follow to flash a custom ROM?
i normally copy the rom zip on the external micro SD card
i go to teamwin recovery i do a wipe and after i do install
The install finish and i click on reboot
DO i have to do other steps to flash the stock kernel?
i didn't flash any boot.img and kernel until now
UPDATE
problem solved i flashed the stock 5.1.1 kernel before to flash the rom and the bootloop disappeared.
Now i'm with the custom Mod there is any possibility to restore the DRM functions with the custom rom?
PdorITA said:
at moment i have a 4.4.4 stock rooted http://dl-1.va.us.xda-developers.com/3/6/5/9/5/7/4/Screenshot_2016-02-25-15-46-09.jpg?key=4YW3-mNtbisUcXLWsSrQ_g&ts=1456411770
Which procedure i have to follow to flash a custom ROM?
i normally copy the rom zip on the external micro SD card
i go to teamwin recovery i do a wipe and after i do install
The install finish and i click on reboot
DO i have to do other steps to flash the stock kernel?
i didn't flash any boot.img and kernel until now
UPDATE
problem solved i flashed the stock 5.1.1 kernel before to flash the rom and the bootloop disappeared.
Now i'm with the custom Mod there is any possibility to restore the DRM functions with the custom rom?
Click to expand...
Click to collapse
Well, if you only want to stay on these stock based custom rooms there was no need to unlock the bootloader. You only need that for truly custom rooms like cm or aosp.
If you want these rooms with drm keys then do this.
Restore your T A backup. This will relocate your bootloader
If this results in a boot loop, then flash a stock ftf, and do everything again EXCEPT do not unlock the bootloader this time