The LG G Pad 8.3 has a locked bootloader, and to bypass it we have two different tools: Open bump and Loki. Most custom roms now use Open bump (recommended), but some still use Loki. Jellybean and Kitkat bootloaders have different backlight settings, and kernels need to be adapted to match those backlight settings. So here I provide some flashable zips, so you can choose the bootloader that best suits your custom rom.
IMPORTANT: to install these files, reboot into recovery and flash the zip of your choice. After that, reboot into recovery again so the changes take effect. If you are stuck on Lollipop bootloader and have no access to recovery, check this post.
V50020F Bootloader is needed if the kernel in your custom rom/recovery is adapted to Kitkat bootloader backlight, like CyanogenMod 12.1 and TWRP official builds.
V50020F Bootloader: https://www.androidfilehost.com/?fid=24352994023707804
*** DEPRECATED (below) ***
V50010B Bootloader is needed if the kernel in your custom rom is adapted to Jellybean bootloader backlight, like those based on CyanogenMod old code.
V50010B Bootloader: https://www.androidfilehost.com/?fid=23991606952613674
V50020D Bootloader Loki is needed if the kernel in your custom rom is adapted to Kitkat bootloader backlight, but it's packed with Loki. All the files are from V50020D, except aboot.img from V50010B. This should not be used anymore, every custom rom should use Open bump instead of Loki. If you are a developer and want to use Open bump instead of Loki, check this commit.
V50020D Bootloader Loki: https://www.androidfilehost.com/?fid=23991606952613676
* If you are a developer and want to use Kitkat bootloader backlight settings (instead of Jellybean), check this commit.
Wow I may not have my Gpad yet but I think its getting easier now because of this base flashable zip. Thanks
This will automatically replace old version of TWRP if flash for the first time like this one?
http://forum.xda-developers.com/showthread.php?t=2641409
@jsevi83 Great Idea! :good:
How can we exactly use this?
Just want to make sure nothings bad gonna happen
Im currently on LRS Kitkat and old TWRP. If I want to replace it with CM 4.4.2 ROM. I have to wipe the system then use 4.2.2 base then the full CM ROM?
Just found out that even the new TWRP 2.7.0.1 is still not compatible LRS ROM
Its possible to replace recovery.img with old TWRP or perhaps Philz CWM?
Yeah, I'm a little lost too on how to proceed. If you can post some detailed instructions, it'd be much appreciated
yawako said:
How can we exactly use this?
Just want to make sure nothings bad gonna happen
Im currently on LRS Kitkat and old TWRP. If I want to replace it with CM 4.4.2 ROM. I have to wipe the system then use 4.2.2 base then the full CM ROM?
Just found out that even the new TWRP 2.7.0.1 is still not compatible LRS ROM
Its possible to replace recovery.img with old TWRP or perhaps Philz CWM?
Click to expand...
Click to collapse
ptargino said:
Yeah, I'm a little lost too on how to proceed. If you can post some detailed instructions, it'd be much appreciated
Click to expand...
Click to collapse
It's pretty simple, If your on a 4.4 stock (not aosp) and want to flash an aosp 4.4 rom (which uses 4.2 bootstack) flash the 4.2 zip then reboot into recovery from recovery (important) and then flash your rom normally. If your on 4.2 stock or aosp and want to flash a 4.4 stock rom, flash the 4.4 zip then do the same by rebooting into recovery from recovery and flash away. Its important to reboot into recovery from recovery after flashing these because if you boot your current rom, the kernel and other boot partitions won't match - bad things will happen.
annoyingduck said:
It's pretty simple, If your on a 4.4 stock (not aosp) and want to flash an aosp 4.4 rom (which uses 4.2 bootstack) flash the 4.2 zip then reboot into recovery from recovery (important) and then flash your rom normally. If your on 4.2 stock or aosp and want to flash a 4.4 stock rom, flash the 4.4 zip then do the same by rebooting into recovery from recovery and flash away. Its important to reboot into recovery from recovery after flashing these because if you boot your current rom, the kernel and other boot partitions won't match - bad things will happen.
Click to expand...
Click to collapse
Thanks, I added the instructions to the first post and mentioned you in the credits.
What do you meant boot into recovery from recovery?why boot into it twice? Im on stock 4.2 and want to flash 4.4
jsevi83 said:
Thanks, I added the instructions to the first post and mentioned you in the credits.
Click to expand...
Click to collapse
ok, so i did the thing where bad things happen, i tried flashing the 4.4.2 one thinking i had 4.2.2 and now its bootloop hell. Goes to teamwin screen then it auto runs "Running Open recovery script" then bootloops again. Hard reset does not work, just goes back into loop.
How can i undo the stupidity? thanks
RyanEJ25 said:
What do you meant boot into recovery from recovery?why boot into it twice? Im on stock 4.2 and want to flash 4.4
Click to expand...
Click to collapse
Boot into recovery, flash the chosen base zip, then press the reboot button and then recovery, this way it reboots into recovery again and the changes are applied. Then you flash the rom you want.
erwaso said:
ok, so i did the thing where bad things happen, i tried flashing the 4.4.2 one thinking i had 4.2.2 and now its bootloop hell. Goes to teamwin screen then it auto runs "Running Open recovery script" then bootloops again. Hard reset does not work, just goes back into loop.
How can i undo the stupidity? thanks
Click to expand...
Click to collapse
It depends on what rom you want to have. If you want stock 4.4.2, flash any of the zips found in the forum (like the flashable V50020B), it will also change the base. If you want CM11 or any other AOSP based rom, flash the 4.2.2-base.zip, reboot into recovery again and then flash the zip of the rom.
jsevi83 said:
Boot into recovery, flash the chosen base zip, then press the reboot button and then recovery, this way it reboots into recovery again and the changes are applied. Then you flash the rom you want.
It depends on what rom you want to have. If you want stock 4.4.2, flash any of the zips found in the forum (like the flashable V50020B), it will also change the base. If you want CM11 or any other AOSP based rom, flash the 4.2.2-base.zip, reboot into recovery again and then flash the zip of the rom.
Click to expand...
Click to collapse
I understand that part. Problem is I don't have the chance to do anything. It goes from LG screen to teamwin logo to the flashing screen then back to the LG screen.
How can I stop the boot looping?
erwaso said:
I understand that part. Problem is I don't have the chance to do anything. It goes from LG screen to teamwin logo to the flashing screen then back to the LG screen.
How can I stop the boot looping?
Click to expand...
Click to collapse
I don't understand how you got into that situation, I tested the zips a lot before publishing them. Anyway, if I were you I would install the KDZ file to get back to stock. There are some threads in the forum explaining how to do that.
erwaso said:
I understand that part. Problem is I don't have the chance to do anything. It goes from LG screen to teamwin logo to the flashing screen then back to the LG screen.
How can I stop the boot looping?
Click to expand...
Click to collapse
Free thanks...
Anyways, can you get into download mode?
Sent from my LG-V500 using Tapatalk
annoyingduck said:
Free thanks...
Anyways, can you get into download mode?
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Yes sir. But while I use the mobile tool in Windows Vista, it keeps stopping at 30% during extraction. I saw that YouTube video for unbricking going from 5 to 80 in a second during extraction.
So annoyed lol. Never happened to me before.
---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------
jsevi83 said:
I don't understand how you got into that situation, I tested the zips a lot before publishing them. Anyway, if I were you I would install the KDZ file to get back to stock. There are some threads in the forum explaining how to do that.
Click to expand...
Click to collapse
I was already in trouble before, I was rooted on 4.2.2 and did a factory reset before updating to Stock 4.4.2. I got stuck in twrp home screen and no matter what I tried to wipe or flash it went back to twrp home. So I tried to flash your 4.4.2 zip and now it's all boot loop happy lol
I saw that kdz thread. I'll try it when the kids aren't running around me in circles
erwaso said:
Yes sir. But while I use the mobile tool in Windows Vista, it keeps stopping at 30% during extraction. I saw that YouTube video for unbricking going from 5 to 80 in a second during extraction.
So annoyed lol. Never happened to me before.
---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------
I was already in trouble before, I was rooted on 4.2.2 and did a factory reset before updating to Stock 4.4.2. I got stuck in twrp home screen and no matter what I tried to wipe or flash it went back to twrp home. So I tried to flash your 4.4.2 zip and now it's all boot loop happy lol
I saw that kdz thread. I'll try it when the kids aren't running around me in circles
Click to expand...
Click to collapse
Use mobile tool and do it again. Be sure your using the regular mobile tool, not the modified one for the kdz method. Get in dl mode, choose upgrade recovery option + manually enter your model # and serial #. Give it a good 5+ min to determine if it's actually hanging. If it does, unplug it and plug it back in and it'll continue. I did that once and it worked fine.
-VZW LG G2 VS980
annoyingduck said:
Use mobile tool and do it again. Be sure your using the regular mobile tool, not the modified one for the kdz method. Get in dl mode, choose upgrade recovery option + manually enter your model # and serial #. Give it a good 5+ min to determine if it's actually hanging. If it does, unplug it and plug it back in and it'll continue. I did that once and it worked fine.
-VZW LG G2 VS980
Click to expand...
Click to collapse
Thanks! I'll try it and report back. Appreciate the assist!
Ended up deleting all LG related anything on my comp, then reinstalling them as suggested in another thread. This worked lol. Now to root ioroot and see if I can't screw up again.
Thanks.
jsevi83 said:
It depends on what rom you want to have. If you want stock 4.4.2, flash any of the zips found in the forum (like the flashable V50020B), it will also change the base. If you want CM11 or any other AOSP based rom, flash the 4.2.2-base.zip, reboot into recovery again and then flash the zip of the rom.
Click to expand...
Click to collapse
I still don't get it. If I am on Pacman that says 4.4.2, what do I flash? How do I know if a certain rom is AOSP based, and what bootstack when it says 4.4.2? And if I'm already on PacMan 442, and want to get rid of the dim light issue, do I flash the appropriate zip, then reflash the rom? Or do I need to downgrade to stock 4.2.2 then flash 422 zip, then flash the custom rom again???
graphdarnell said:
I still don't get it. If I am on Pacman that says 4.4.2, what do I flash? How do I know if a certain rom is AOSP based, and what bootstack when it says 4.4.2? And if I'm already on PacMan 442, and want to get rid of the dim light issue, do I flash the appropriate zip, then reflash the rom? Or do I need to downgrade to stock 4.2.2 then flash 422 zip, then flash the custom rom again???
Click to expand...
Click to collapse
If you have the dim light issue at boot, flash the 4.2.2 base zip. If you want to install a custom rom based on stock 4.4.2, install the 4.4.2 base zip.
jsevi83 said:
If you have the dim light issue at boot, flash the 4.2.2 base zip. If you want to install a custom rom based on stock 4.4.2, install the 4.4.2 base zip.
Click to expand...
Click to collapse
Thank you for the prompt reply and help. Lest I belabor the point, I understand what you're saying from the beginning, but what confused me was the mention by another member that the 4.4.2 customs roms used 4.2 "bootstack" (whatever that means). So the question again is: if a custom rom says 4.4.2, is it really 4.4.2 or 4.2 boot stack (whatever that is)? And in which case, which zip do I use?? I can do it by trial and error, but need to be assured that shooting from the hip won't mess my tab unnecessarily. Again thanks for the help.
Related
I'm having troubles when i wan't to install this ROM :
http://forum.xda-developers.com/showthread.php?t=2555350 .
I'm using the dl from the first post, i'm using fastboot flash boot boot.img (the boot.img i'm getting from the zip-file).
I do a factory reset from the bootloader, then i do a factory reset in the twrp recovery
then i flash the boot.img in the jb hboot 1.25.0002
then i flash the zip file and i reboot.
but i never get to see the boot image. just a black screen...
Can someone help me?
tcornelis said:
I'm having troubles when i wan't to install this ROM :
http://forum.xda-developers.com/showthread.php?t=2555350 .
I'm using the dl from the first post, i'm using fastboot flash boot boot.img (the boot.img i'm getting from the zip-file).
I do a factory reset from the bootloader, then i do a factory reset in the twrp recovery
then i flash the boot.img in the jb hboot 1.25.0002
then i flash the zip file and i reboot.
but i never get to see the boot image. just a black screen...
Can someone help me?
Click to expand...
Click to collapse
You're definitely using a TWRP recovery made for JB hboot? @GtrCraft, did you put the right boot.img inside the zip?
Also, you can try flashing a custom JB kernel of your choice.
@dansou901 I believe so, flashing this (http://forum.xda-developers.com/showthread.php?t=2344254) work like a charm (except for the rom that hasn't got any wifi, ...)
How can i check to be sure?
tcornelis said:
@dansou901 I believe so, flashing this (http://forum.xda-developers.com/showthread.php?t=2344254) work like a charm (except for the rom that hasn't got any wifi, ...)
How can i check to be sure?
Click to expand...
Click to collapse
For booting that ROM a CM kernel is needed. As you have installed one (if it works like you said), you need to install a JB Sense kernel (just pick one from Original Android Development section). Then reinstall SuperSense and you should be fine.
I'll give that a go and let you know
@dansou901 , i've used this boot.img (http://forum.xda-developers.com/showthread.php?t=2337389) because i've already been able to flash that rom as well.
but now i can't seem to get rid of my previous custom rom. i've done a factory reset, i wiped everything there is to wipe, i've flashed the above boot.img and supersense but it's still another custom rom on my device :s
tcornelis said:
@dansou901 , i've used this boot.img (http://forum.xda-developers.com/showthread.php?t=2337389) because i've already been able to flash that rom as well.
but now i can't seem to get rid of my previous custom rom. i've done a factory reset, i wiped everything there is to wipe, i've flashed the above boot.img and supersense but it's still another custom rom on my device :s
Click to expand...
Click to collapse
That's a CM kernel as well. I told you to use a Sense kernel. Use this one for example: http://forum.xda-developers.com/showthread.php?t=2483489
and your recovery should work again as expected. Btw, which recovery did you install? Please give the link.
this is the twrp recovery.img http: // teamw . in / project / twrp2 / 140 (yeah, can't post outside links yet)
i'll give that one a shot
tcornelis said:
this is the twrp recovery.img http: // teamw . in / project / twrp2 / 140 (yeah, can't post outside links yet)
i'll give that one a shot
Click to expand...
Click to collapse
That one's made for ICS, if I recall correctly... Don't use it. Use this one instead: http://forum.xda-developers.com/showthread.php?t=2099513 But be sure to use a JB version.
After changing my recovery, finally i was able to flash the custom rom. I used the boot.img you gave me, but is that going to affect some of the features in the rom?
And i would like to thank you allready
tcornelis said:
After changing my recovery, finally i was able to flash the custom rom. I used the boot.img you gave me, but is that going to affect some of the features in the rom?
And i would like to thank you allready
Click to expand...
Click to collapse
No, it's not. You can however choose the kernel yourself as I said... But keep in mind that it has to be a JB Sense kernel (just read the OP of the kernel thread carefully, then you'll know). For recoveries, keep this in mind.
No Title Here
The boot.img in the SuperSENSE-dx5 zip is stock, every JB Sense kernel should work though
GtrCraft said:
The boot.img in the SuperSENSE-dx5 zip is stock, every JB Sense kernel should work though
Click to expand...
Click to collapse
His problem wasn't the kernel but the wrong recovery he used, it's fixed now.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
His problem wasn't the kernel but the wrong recovery he used, it's fixed now.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect :good:
Hi, i'm new in these things so have a few questions.
Iwould like to flah thecyanogenmod but my galax 2s syas it is not a gt-I9100.
So i read some things about removing the assert line from a script and so on.
Do i need to flah an older rom before the cm11 nightly?
Do i need to flash the kernel first? or just use the latest cwm? (or rom manager/clockword?)
Can i reflash the S2 with an cyanogenmod kitkat version after i flashed it with an other kitkat rom for this device?
(still i did not succed to flash any rom to it)
thanks for any help !
JJSJJS said:
Hi, i'm new in these things so have a few questions.
Iwould like to flah thecyanogenmod but my galax 2s syas it is not a gt-I9100.
So i read some things about removing the assert line from a script and so on.
Do i need to flah an older rom before the cm11 nightly?
Do i need to flash the kernel first? or just use the latest cwm? (or rom manager/clockword?)
Can i reflash the S2 with an cyanogenmod kitkat version after i flashed it with an other kitkat rom for this device?
(still i did not succed to flash any rom to it)
thanks for any help !
Click to expand...
Click to collapse
First of all check if it g version or not.
To best of my understanding you can install it directly as far as you are rooted.
Sent from my GT-I9100 using xda premium
You don't need to flash an older version before KK. You just need KK compatible recovery. Or you can flash a KK compatible kernel, reboot to recovery and flash your KK rom.
Hello, thank you both for your replies.
Finally some clear answers
The model says GT-I9100 and not with g behind it, thanks.
I found some things about the status 7 error and about removing some line in a script in the zip.
So i will try the kitkat recovery (in my understanding this is also the kernel?) and then flash it with kitkat rom.
I would like to flash the one from cyangenmod, but doe it really mather which custom kitkat rom i take? At least they are all without the providers code like Vodafone or others?
Thanks again. I will update the thread if it succeeds or not.
Hi,
so i could not install the latest Recovery_CWM_6.0.4.7_I9100.zip as it gave an error E: signature verification failed.
then i tried recovery-clockwork-touch-5.8.1.5-galaxys2.zip and this works. But with this i can't install CM11. as i get the status 7 error.
So i will try some other versions kitkat compatible.
I also took a look at the kernels section but it is not clear wich one to use for CWM6 as i don't know what XXLSR or DDLS3 means, and which is correct for Netherlands.
Do you have any idea? (i am not allowed to post there yet)
Thanks for your help.
For choice of kernel -
1. Gustavo's - I don't remember the version. Check the op.
2. Dorimanx - you can try 10.43v100.
3. Apollo - 7.0b Cm
They will bring the KK compatible recovery you want on your phone. Then after rebooting to recovery you can flash any custom rom as they are not locked by any carriers.
banjara said:
For choice of kernel -
1. Gustavo's - I don't remember the version. Check the op.
2. Dorimanx - you can try 10.43v100.
3. Apollo - 7.0b Cm
They will bring the KK compatible recovery you want on your phone. Then after rebooting to recovery you can flash any custom rom as they are not locked by any carriers.
Click to expand...
Click to collapse
Thank you very much Banjara !
i'll keep trying, will report if i succeed
oh oh no good.....
JJSJJS said:
Thank you very much Banjara !
i'll keep trying, will report if i succeed
Click to expand...
Click to collapse
oh boy oh boy
i followed this http://forum.xda-developers.com/galaxy-s2/development/kernel-lazing-safe-stock-kernels-t2293576
and now it is stuck on boot screen, can't even reboot in recovery mode to get the back rom back pfffff
what should i do now......even the usb cable aint working, i'm flashing to the external sdcard via an other phone and the replace the sdcard to the galaxy s2
thanks for any help :crying::crying::crying::crying::crying:
JJSJJS said:
oh boy oh boy
i followed this http://forum.xda-developers.com/galaxy-s2/development/kernel-lazing-safe-stock-kernels-t2293576
and now it is stuck on boot screen, can't even reboot in recovery mode to get the back rom back pfffff
what should i do now......even the usb cable aint working, i'm flashing to the external sdcard via an other phone and the replace the sdcard to the galaxy s2
thanks for any help :crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
If you are able to go back to download mode
1. Flash a stock rom via odin
2. Flash a custom kernel via Odin. You might find some in the link you put there or you can search for hirox kernel. Remember, you have to download Odin flash able kernel and follow the op.
3. Once you have custom kernel, reboot to recovery. Flash any of the kernels in clockworkmod mentioned in my previous post.
4. Reboot to recovery. Flash your rom.
If you are unable to go to download mode try all the methods mentioned in the below link to bring it back to normal. It will need patience and perseverance. http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Thank you for your patience and your help Banjara.
This forum and it's people are 100 times better the on Gyanomed were totally no support is given...
I will try it and come back, at least the phone able to start in the download mode.
Probably the usb connector has some loose contacts as i can get no contact with pc.
I got this phone from my brother and he told me that it never worked, just loading the battery
So i tried an other cable from an cheap android pad, but also no luck
maybe tommorow, i have another cable from an android stick pc at my job, maybe it will work
else i have to open it to check the connector under a microscope and probably resolder(hotair) it with a lot of flux... what a pitty... :crying:
lucky i have some experience on it, i repaired a lot of qtek phone, some years ago, always that connector broken.
I'm originally an tv(crt,lcd,plasma) repair technician, but now on an other job
Pfew, i managed to rsolder the connector with help of the microscope on my job.
I could even connect to odin. so that's is good progression. i had a wrong kernel downloaded, so it failed.
now i have the correct one and will use Siyah-s2-v6.0b5.tar
But unfortunately the battery is really emptying quickly when it stays in the phone, i don't know why.
So i will have to charge it an then give it another try with this kernel.
The ROM should still be original as i did not flash it before, just the kernel.
The phone is now saying battery empty, can't download.
To be continued...
Jippieeee!
GREAT !!!!
It worked! flashed the kernel Siyah-s2-6.0b5 and it started ! :victory:
Now what is the best way to proceed, there are so many topics on this it is overwhelming.
Should i first flash a Kernel or first a rom?
Can i flash them right after each other? (kernel reboots) so ROM and directly Kernel in one go?
thanks for your help!
{SOLVED}
Ok this is solved, thank you guys and dolls !
i managed to flash the cwm 6++++ and then the OMNI kitkat (latest) and the gAPPs
and it is working ! i am verry happy ! :laugh::laugh::laugh::laugh::laugh:
:thumbup::beer::beer:
one more thing
i noticed there is also another kernel now in the phone.
How to get rid of the yellow exclamation mark?
i saw some footage on youtube how to do it with the correct kernel.
But can i also extract the kernel from the ROM.tar i used and flash it with Odin?
Or is there another way?
thanks for your help. ---> edit
ok found some here: http://forum.xda-developers.com/galaxy-s2/orig-development/30-10-2012-k-la-lp-t1103399
but is it also good enough to unroot your device or are some functionality's then lost when using OMNI- rom ?
Thanks for your help
there arent any funcions lost it just gives your phone informations so that it thinks its all fine and dont displays the yelow horror . Btw i used TWRP KK kernel on my gs2 and installed prerooted rom aosp neatrom 5.8 kk and dont have problems with triangle. Also neatrom 4.1.2 with extended battery life is there if you dont like kitkat =D
Radelos said:
there arent any funcions lost it just gives your phone informations so that it thinks its all fine and dont displays the yelow horror . Btw i used TWRP KK kernel on my gs2 and installed prerooted rom aosp neatrom 5.8 kk and dont have problems with triangle. Also neatrom 4.1.2 with extended battery life is there if you dont like kitkat =D
Click to expand...
Click to collapse
Thanks Radelos, then i will try to unroot it again. And that will be it then.
Now using the OmniKK nightly of 8th of june, it runs very smooth, no issues till now, all is working well. :good:
btw idk what is the exact rom your willing to use but for no triangle would also do an clean install of stock rom, then root with framroot that you can find here on site and then flash KK compatible recovery and ofc kk rom with it. Here is the rom i used, its prerooted and on first boot starts direct into recovery so its for lazy ppl =D factory format data/system then flash TWRP touch recovery and in cwm reboot recovery option. And then just flash rom
Rom
http://uloz.to/x13p4YVr/drhd-base-lpq-re-light-tar
KK TWRP touch recovery
http://uloz.to/xyw9UkTk/kk-kernel-21-04-twrp-zip
Radelos said:
btw idk what is the exact rom your willing to use but for no triangle would also do an clean install of stock rom, then root with framroot that you can find here on site and then flash KK compatible recovery and ofc kk rom with it. Here is the rom i used, its prerooted and on first boot starts direct into recovery so its for lazy ppl =D factory format data/system then flash TWRP touch recovery and in cwm reboot recovery option. And then just flash rom
Rom
http://uloz.to/x13p4YVr/drhd-base-lpq-re-light-tar
KK TWRP touch recovery
http://uloz.to/xyw9UkTk/kk-kernel-21-04-twrp-zip
Click to expand...
Click to collapse
So with this process, will there be no yellow triangle?
I looked around for one but was unable to find one. Maybe Twi5sted's stock has the original kernel but encryption fails when I attempt it.
Any suggestions?
Yep, muinz_ri created a Stock De-Odexed ROM. I was successfully able to install Xposed by flashing everything through FlashFire and still have Knox 0x0.
http://forum.xda-developers.com/tmo...ow-to-update-to-stock-rooted-ob1-5-0-t3049676
Direct link to ROM download: https://www.androidfilehost.com/?fid=24052804347762756
TheAH said:
Yep, muinz_ri created a Stock De-Odexed ROM. I was successfully able to install Xposed by flashing everything through FlashFire and still have Knox 0x0.
http://forum.xda-developers.com/tmo...ow-to-update-to-stock-rooted-ob1-5-0-t3049676
Direct link to ROM download: https://www.androidfilehost.com/?fid=24052804347762756
Click to expand...
Click to collapse
That's awesome, wish I had known before I tripped Knox but oh well.
I'm getting a bootloop with a very bright split second tmobile splash screen just before it reboots. I have latest TWRP, link2sd and encryption... I wonder what the problem could be...
how to make stock recovery flashable?
I do have another question regarding this rom - would you happen to know how I may be able to make the embedded recovery image flashable? TWRP doesn't seem to be working at the moment with regard to decrypting and formatting /data but the stock recovery does. It can come in handy if there is a way to do it via mobile odin possibly or via some other program.
fishinpercolator said:
I do have another question regarding this rom - would you happen to know how I may be able to make the embedded recovery image flashable? TWRP doesn't seem to be working at the moment with regard to decrypting and formatting /data but the stock recovery does. It can come in handy if there is a way to do it via mobile odin possibly or via some other program.
Click to expand...
Click to collapse
Do you have twrp installed right now?
ShinySide said:
Do you have twrp installed right now?
Click to expand...
Click to collapse
Right now I have stock recovery as I recently reflashed the Rom. At some point however I plan to go back to TWRP.
If I run into encryption problems and need to do a reset, I would like to see if I can flash TWRP using TWRP app while booted in safe mode (if I am able to get that far).
What do you think?
fishinpercolator said:
Right now I have stock recovery as I recently reflashed the Rom. At some point however I plan to go back to TWRP.
If I run into encryption problems and need to do a reset, I would like to see if I can flash TWRP using TWRP app while booted in safe mode (if I am able to get that far).
What do you think?
Click to expand...
Click to collapse
Well encryption will be fine on stock recovery. I thought you had twrp and just wanted the stock recovery which I was going to tell you to post the stock recovery and I'll put it in a twrp flashable zip
ShinySide said:
Well encryption will be fine on stock recovery. I thought you had twrp and just wanted the stock recovery which I was going to tell you to post the stock recovery and I'll put it in a twrp flashable zip
Click to expand...
Click to collapse
I appreciate that... at some point I will be on TWRP though so I can post the stock recovery when I get home. Or how can I do it myself?
fishinpercolator said:
I appreciate that... at some point I will be on TWRP though so I can post the stock recovery when I get home. Or how can I do it myself?
Click to expand...
Click to collapse
Here, download this, extract the zip, put the recovery.img in the extracted folder, highlight meta-inf system and recovery.img and zip all three and flash it. Only use this zip for stock or custom recoveries
ShinySide said:
Here, download this, extract the zip, put the recovery.img in the extracted folder, highlight meta-inf system and recovery.img and zip all three and flash it. Only use this zip for stock or custom recoveries
Click to expand...
Click to collapse
Hey thanks! So I did as you said and flashed the stock recovery from the deodexed rom and it's still TWRP. Strange isn't it? It would make sense if the deodexed ROM came with TWRP but when I initially flashed it I can confirm it was stock android.
I'm confused....
fishinpercolator said:
Hey thanks! So I did as you said and flashed the stock recovery from the deodexed rom and it's still TWRP. Strange isn't it? It would make sense if the deodexed ROM came with TWRP but when I initially flashed it I can confirm it was stock android.
I'm confused....
Click to expand...
Click to collapse
Obvious question - did you reboot back to recovery after flashing?
fishinpercolator said:
Hey thanks! So I did as you said and flashed the stock recovery from the deodexed rom and it's still TWRP. Strange isn't it? It would make sense if the deodexed ROM came with TWRP but when I initially flashed it I can confirm it was stock android.
I'm confused....
Click to expand...
Click to collapse
Oh wait, I did something very wrong... fixing now...
Yay it worked, thanks a lot
I guess I should keep the stock recovery installed with this thing encrypted because TWRP seems broken (at least version 2.8.7.0). I emailed the developer about it.
Now I'm wondering for added flexibility, how I may be able to flash the stock recovery from MobileOdin. That seems to take .md5 files and not zips. Is this feasible to do?
fishinpercolator said:
Yay it worked, thanks a lot
I guess I should keep the stock recovery installed with this thing encrypted because TWRP seems broken (at least version 2.8.7.0). I emailed the developer about it.
Now I'm wondering for added flexibility, how I may be able to flash the stock recovery from MobileOdin. That seems to take .md5 files and not zips. Is this feasible to do?
Click to expand...
Click to collapse
Post the img I'll make you one tonight. It'll be 10x easier for me since I run Linux then telling you how on windows
ShinySide said:
Post the img I'll make you one tonight. It'll be 10x easier for me since I run Linux then telling you how on windows
Click to expand...
Click to collapse
Well thanks! Maybe you can point me toward the Windows way as I would like to do the same for the stock kernel, xposed, and the tethering addon.
fishinpercolator so are you having trouble with TWRP? What I did in FlashFire was flash the pre-rooted de-odexed ROM (that I linked earlier) then booted that. It was de-odexed and worked fine but boot took about 15 minutes (as it is de-odexed).
In FlashFire you need to hit the + and press Flash ZIP or OTA.
Then I installed FlashFire again (it was erased because I flashed a new ROM) and downloaded the Samsung 5.0 Xposed ZIP and flashed that in FlashFire using Flash ZIP or OTA. Basically since I have Knox 0x0, I use FlashFire as my "recovery" and it might be easier for you than finding a working TWRP image (although I am sure ShinySide is more than eager to help you). Then I installed the Xposed APK and had to reboot before it recognized the Xposed ZIP was installed.
After that, most Xposed modules started working for me.
TheAH said:
fishinpercolator so are you having trouble with TWRP? What I did in FlashFire was flash the pre-rooted de-odexed ROM (that I linked earlier) then booted that. It was de-odexed and worked fine but boot took about 15 minutes (as it is de-odexed).
In FlashFire you need to hit the + and press Flash ZIP or OTA.
Then I installed FlashFire again (it was erased because I flashed a new ROM) and downloaded the Samsung 5.0 Xposed ZIP and flashed that in FlashFire using Flash ZIP or OTA. Basically since I have Knox 0x0, I use FlashFire as my "recovery" and it might be easier for you than finding a working TWRP image (although I am sure ShinySide is more than eager to help you). Then I installed the Xposed APK and had to reboot before it recognized the Xposed ZIP was installed.
After that, most Xposed modules started working for me.
Click to expand...
Click to collapse
I haven't used flashfire but will look into it. I've already tripped knox a while ago so that's not my prime concern. I want this phone to be encrypted and would like to learn a way to fix on the fly while on vacation (and without a laptop) in the event a catastrophe happens. It seems TWRP may not be removing the crypto footer when I format data as I still get the encryption password prompt.
Seems like flashfire allows you to flash roms from USB? I will need instructions for that.... <pokes around>
::update::
For some reason I thought flashfire was command line driven... I have Mobile Odin and I read that it contains flashfire, something worth looking into.
Is there a way to flash roms using ADB from a usb stick?
(NOTE- I should clarify, is there a way to flash from a command prompt assuming custom recovery is not installed and the phone is soft-bricked).
fishinpercolator said:
Well thanks! Maybe you can point me toward the Windows way as I would like to do the same for the stock kernel, xposed, and the tethering addon.
Click to expand...
Click to collapse
Here https://www.androidfilehost.com/?fid=24052804347792016
ShinySide said:
Here https://www.androidfilehost.com/?fid=24052804347792016
Click to expand...
Click to collapse
Well thanks!
Reading threads since I've flashed the official OG6 firmware I'm guessing I can't downgrade to anything lower now? Is it still possible?
I've installed HispAsian's Trap kernel to gain root, and installed TWRP but there's only one OG6 rom as far as I can tell (Maverick 5.1.1) and it bricks my phone for some odd reason. I'd really just like a debloated OG6 version and I'd be happy but I can't find anything. Should I downgrade to OF6 just so I can install a rom? Are there other OG6 roms out there I don't know about?
Also I'm assuming since there's knox on OG6 that's why I keep getting the notification that "Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.". I'm scared to restart my phone because I don't know what that'd do.
I'm sorry if this is newbish or self-apparant but I'm pretty confused when it comes to Samsung phones. The other android phones I've had before were very straightforward.
okay ROM creator of Maverick
download twrp on your phone check
flash my rom
profit thats it.
make sure you odin og6 with a power off power on and download mode
malbert16442 said:
okay ROM creator of Maverick
download twrp on your phone check
flash my rom
profit thats it.
make sure you odin og6 with a power off power on and download mode
Click to expand...
Click to collapse
Hey! I'd love to install your rom, but when I do flash it, it gets bootloops on the T-mobile boot screen. I've followed your instructions for both flashing the firmware as well as your rom but still happens. No idea why.
My process I've tried several times:
Odin official OG6 firmware
Odin TWRP recovery
Flash HispAsian Trap Kernel for OG6 to gain root access
Flash Maverick
On bootup it gets stuck on the T-Mobile Carrier screen, and then bootloops over and over again. Not sure what I've done wrong, but maybe I'll try re-downloading Maverick 9.2 when I get home and try again.
EDIT: Omg I'm an idiot. I've been trying to flash 9.2 without flashing 9.1 first, I just read that. DUH
I know why don't flash no trap kernel for root boot into twrp wipe data partions internal and system
Then flash 9.1 of my rom then 9.2 update
Ps my rom doesn't have any t mobile boot screen that's why I'm worried
Sent from my SM-G900T using Tapatalk
malbert16442 said:
I know why don't flash no trap kernel for root boot into twrp wipe data partions internal and system
Then flash 9.1 of my rom then 9.2 update
Ps my rom doesn't have any t mobile boot screen that's why I'm worried
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Sorry I meant it bootloops at the Samsung animation, and also I thought 9.2 was a standalone lol.
Thanks for the help! I think flashing 9.1 should solve my problems, however if I have to reflash stock and re-root, how do I do that without trap kernel?
jonnyboy2040 said:
Sorry I meant it bootloops at the Samsung animation, and also I thought 9.2 was a standalone lol.
Thanks for the help! I think flashing 9.1 should solve my problems, however if I have to reflash stock and re-root, how do I do that without trap kernel?
Click to expand...
Click to collapse
Just steps by steps get 9.1 to boot then install 9.2 then we talk
Sent from my SM-G900T using Tapatalk
Hai.
I have a galaxy note 3 sm n9005. Have already rooted by finding forum from xda and even install twrp recovery following the guides given.
But im trying to install custom rom. And tried all the roms tat is given from xda for note 3 and could install single one.
Please help to resolve this problem. Im confuse.
Tq.
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
es0tericcha0s said:
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
Click to expand...
Click to collapse
Im using twrp 3.0.2.1 and everytime i try to install a rom it stuck at samsung screen.
And it show md5 not found.
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
es0tericcha0s said:
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
Click to expand...
Click to collapse
Resurrection remix.unicorn.slim.and all cynogen rom is working. Im trying install s7edge custom rom for darkwolf and darklord. I even updated the bootloader and modem according to tutorial. I used odin to flash them..
N9005xxugboa1
Lrx21v.n9005xxugbob6
I have my stock rom n internl backed up. I try all. And still it always stuck on samsung screen.
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
es0tericcha0s said:
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
Click to expand...
Click to collapse
How can install kernel after. Everytime i install it reboots its self to samsung screen. Or should go back to recovery and install the kernel back. And thank you for your help till now.
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
es0tericcha0s said:
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
Click to expand...
Click to collapse
I have uncheck the reboot after install. When i install the rom it automatically reboot itself. It doesnt show anything or show done. Once it even show os not found.
Hi
Where can i install or find the latest kernel
It's in the installation instructions for the rom.
es0tericcha0s said:
It's in the installation instructions for the rom.
Click to expand...
Click to collapse
Hi.
I have found the bootloader and modem for my sm n9005 from the installation instruction for the rom.
I try to flash according to the tutorial.and my baseband didnt change. I try flash using odin 3times.
Im not sure where i did wrong.can u help me
Tq
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
tq
es0tericcha0s said:
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
Click to expand...
Click to collapse
Tq
Will try and let you know
sitijohn85 said:
Tq
Will try and let you know
Click to expand...
Click to collapse
Hi
I tried as said and it didnt chnge.
Can i ask bootloader should be at bl and modem should be at cp. Is it correct.
Hi
Thank you for your help.
I did the change on bootloader and modem.
Now im i need to know two more thing.
I download 2 dffernt kind of bootloader n modem.
I flash blxxxxxbpb1 and cpxxxxxboj1..this 2 files were tar.md5 files
Another one which i didnt flash. Blxxxxxxbpb1 and cpxxxxxxxbpb2..this 2 files are tar.tar files..
Can i know whats the different with this 2 files.
One more thing is when i chnge the bootloader and modem will the kernel changes. Or is it different.
Please guide me..im confuse.
Someone might have just mislabeled them. Flashing those will not affect kernel. Different partition of the phone.
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
sitijohn85 said:
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
Click to expand...
Click to collapse
This is the recommended kernel
https://www.androidfilehost.com/?fid=24572369242687310
Recommended recovery is TWRP 2.8.7.0 not the newer 3.0+
Flash other recovery. Boot to TWRP. Wipe system, data, cache, dalvik. Flash rom. Wipe caches. Flash kernel. Reboot. Should work according to lots of people on the thread for that rom.
Hi.
How flash kernel.
just flash the tar.md5 file or the tar.zip file