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:
Related
Hello, I just got my Rezound today and the first thing I did was Unlocked the phone, Installed CWM and Rooted it Via [TOOL] [7-3-2012] HTC Rezound All-In-One Toolkit V2.1.
Everything was working fine. I could get into CWM recovery. I could still boot into the stock rom.
Next I downloaded NeWts-One-XxX-RLS-3.1.2-odex-signed.zip.
I wiped data/factory reset. wiped dalvik cache. installed the rom successfully..
When I reboot, I get stuck at the white HTC boot screen. I can still access CWM. I tried wiping and reinstalling. I tried downloading a different version of this rom. Nothing worked.
Should I try installing AmonRa? Can I just install right over CWM?
To clarify, I have not done anything other than what I have just said. I have not installed any custom kernels. Did not make a backup of the original rom (because it froze mid backup). I did not even use the phone at all before unlocking/rooting other than to make sure it booted.
Thanks in advance
Mike
i guess u on S-ON
so u need to install the kernel
Proz00 said:
i guess u on S-ON
so u need to install the kernel
Click to expand...
Click to collapse
I am S-ON. Which Kernel?
Thanks for the reply :good:
You need to extract the boot.img file from the rom zip then use fastboot on your PC to flash it.
If you're not sure how to set up fastboot, I believe the all in one toolkit contains the needed files, following the instructions in the thread to download, install and use it.
http://forum.xda-developers.com/showthread.php?t=1504824
mjones73 said:
You need to extract the boot.img file from the rom zip then use fastboot on your PC to flash it.
If you're not sure how to set up fastboot, I believe the all in one toolkit contains the needed files, following the instructions in the thread to download, install and use it.
http://forum.xda-developers.com/showthread.php?t=1504824
Click to expand...
Click to collapse
Oh okay. Wasn't familiar how to flash kernels on this device.
Its working now. :good::good:
thanks and have a splendid day!!
mtotho said:
Oh okay. Wasn't familiar how to flash kernels on this device.
Its working now. :good::good:
thanks and have a splendid day!!
Click to expand...
Click to collapse
Be aware that if you are on Gingerbread firmware (you are!) and running ICS ROMS, you need to flash the "Oldfirmware" patch to mount the SD card correctly.
Since you are S-on...every time you flash a rom you will have to flash...
1. The rom
2. the kernel (boot.img) that goes with the rom. You'll either have to pull this out of the rom itself or most dev. provide it as a PH98img file to flash in bootloader.
3. If an ICS ROM...flash oldfirmware patch.
ALSO, you didn't mention it but there is a patch to RLS 3.2.1 that correct some minor bugs. Its on themikmik ! Have fun.
EEK....use AmonRA NOT CWM
mtotho said:
Oh okay. Wasn't familiar how to flash kernels on this device.
Its working now. :good::good:
thanks and have a splendid day!!
Click to expand...
Click to collapse
No problem, that's some good advice from topgun also.
I've unlocked the bootloader of my Desire X, but whenever I try to install Android revolution, it gives me a bunch of errors saying the file couldn't be opened, any rom I stick on the SD has trouble being read by Nexus recovery , I've tried 3 other SD cards. Also after I rooted the phone, I still can't give applications such as Titanium backup root privileges because it says it couldn't find the root binary?
I've got Nexus recovery installed on stock 4.2.
I've also wanted to try other recoveries, is it as simple as flashing a new one through fastboot or do I have to do something else?
I really need help, so I'd be grateful for any you can offer me
Fahim92 said:
I've unlocked the bootloader of my Desire X, but whenever I try to install Android revolution, it gives me a bunch of errors saying the file couldn't be opened, any rom I stick on the SD has trouble being read by Nexus recovery , I've tried 3 other SD cards. Also after I rooted the phone, I still can't give applications such as Titanium backup root privileges because it says it couldn't find the root binary?
I've got Nexus recovery installed on stock 4.2.
I've also wanted to try other recoveries, is it as simple as flashing a new one through fastboot or do I have to do something else?
I really need help, so I'd be grateful for any you can offer me
Click to expand...
Click to collapse
If you are on stock 4.2, you also have HBoot 1.25, so maybe you can't install these roms because your HBoot it isn't 1.24 or lower.
Try to re-flash stock recovery, then flash neXus' again.
Or maybe it can be kernel stuff, did you flash the attached boot.img?
JoseluSpark said:
If you are on stock 4.2, you also have HBoot 1.25, so maybe you can't install these roms because your HBoot it isn't 1.24 or lower.
Try to re-flash stock recovery, then flash neXus' again.
Or maybe it can be kernel stuff, did you flash the attached boot.img?
Click to expand...
Click to collapse
But the rom does say it is available for 1.25+
and do I have to flash a stock recovery? Can't I install another recovery (not stock) by using the fastboot command?
Fahim92 said:
But the rom does say it is available for 1.25+
and do I have to flash a stock recovery? Can't I install another recovery (not stock) by using the fastboot command?
Click to expand...
Click to collapse
Also, is there a recovery that's sure to work with Hboot 1.25 JB?
If so, can I just flash that recovery over my current one?
Anybody?
Fahim92 said:
Anybody?
Click to expand...
Click to collapse
If you want, PM me your skypename and i'll guide you step by step.
ShadowCodeGaming said:
If you want, PM me your skypename and i'll guide you step by step.
Click to expand...
Click to collapse
I don't have Skype
Can you just provide help for me on here? I'd really appreciate it.
Here's my situation in case I wasn't clear in OP, I installed the Nexus recovery but it wasn't able to flash the rom I wanted, so now I want to flash another recovery, and was just wondering whether I could just flash another recovery on top of the old one or if I have to do something else?
Fahim92 said:
I don't have Skype
Can you just provide help for me on here? I'd really appreciate it.
Here's my situation in case I wasn't clear in OP, I installed the Nexus recovery but it wasn't able to flash the rom I wanted, so now I want to flash another recovery, and was just wondering whether I could just flash another recovery on top of the old one or if I have to do something else?
Click to expand...
Click to collapse
Look in the 'Desire X Original Android Development' Section for a TWRP recovery for JB hboot. It's working great for me. You can flash it the same way you flashed the NexusRecovery (fastboot)
ShadowCodeGaming said:
Look in the 'Desire X Original Android Development' Section for a TWRP recovery for JB hboot. It's working great for me. You can flash it the same way you flashed the NexusRecovery (fastboot)
Click to expand...
Click to collapse
So I can just flash it over the current recovery I have? I don't need to go back to stock?
Right
Sent from my black pearl using Tapatalk 2
Fahim92 said:
So I can just flash it over the current recovery I have? I don't need to go back to stock?
Click to expand...
Click to collapse
Yeah. You can just flash it over the NexusRecovery. You never have to go back to stock.
Okay, I just flashed TWRP over my current recovery.
I've tried to flash Sense revolution and it just fails through TWRP, why is this?
Wipe the phone and try again.
Maybe It can be because of MD5 verification. Only happens on that ROM?
Enviado desde mi HTC Desire X
Fahim92 said:
Okay, I just flashed TWRP over my current recovery.
I've tried to flash Sense revolution and it just fails through TWRP, why is this?
Click to expand...
Click to collapse
Try both ics and jb twrp
Sent from my HTC Desire X using xda app-developers app
Title says it all but there are ROMs that include a boot.img in them and some others don't.
What do I do with this boot.img?
A Wild Magikarp said:
Title says it all but there are ROMs that include a boot.img in them and some others don't.
What do I do with this boot.img?
Click to expand...
Click to collapse
Well let me give you the steps
1. Make a backup of your contacts and apps if you want
2. Be sure you have at least 50% battery left
3. Go to the custom recovery and make a nandroid backup incase something goes wrong
4. Do a full wipe in recovery (data, cache and dalvik. System is not needed but I recommend to do that one also)
5. Install your rom in recovery
6. After that is complete go to fastboot and flash boot.img if that's needed (like going from JB to ICS or otherwise)
6a. If you have boot.img that works with the new rom and you don't want anothet you don't need to flash it again
7. Let the phone boot for the first time (this takes 10 minutes max)
8. Setup your phone and restore your apps if you want
That's it
Just to explain your question directly: For JB Sense based ROMS, you can use every JB kernel from Original Development section including stock kernel. That's why there is no kernel installer in each ROM thread. You can use a kernel Installer of your choice, replace boot.img with one of your choice and run the bat file while your phone is connected in fastboot mode to your PC.
Sent from my HTC Desire X using XDA Premium 4 mobile app
A Wild Magikarp said:
Title says it all but there are ROMs that include a boot.img in them and some others don't.
What do I do with this boot.img?
Click to expand...
Click to collapse
The most important thing u have to take care of is that the roms is for ur Hboot version as you are JB I guess your Hboot should be 2.24 so look for that kind of roms and follow the steps given by @GtrCraft
Hope everything go well
EDIT:someone can tell me how to link an user? maybe @GtrCraft ?
GtrCraft said:
Well let me give you the steps
1. Make a backup of your contacts and apps if you want
2. Be sure you have at least 50% battery left
3. Go to the custom recovery and make a nandroid backup incase something goes wrong
4. Do a full wipe in recovery (data, cache and dalvik. System is not needed but I recommend to do that one also)
5. Install your rom in recovery
6. After that is complete go to fastboot and flash boot.img if that's needed (like going from JB to ICS or otherwise)
6a. If you have boot.img that works with the new rom and you don't want anothet you don't need to flash it again
7. Let the phone boot for the first time (this takes 10 minutes max)
8. Setup your phone and restore your apps if you want
That's it
Click to expand...
Click to collapse
If I follow these steps and reboot the phone, it boots with the stock rom and some new apps only.. no new rom is installed :s
geforce660 said:
If I follow these steps and reboot the phone, it boots with the stock rom and some new apps only.. no new rom is installed :s
Click to expand...
Click to collapse
You are using the wrong recovery for your hboot: JB is hboot 1.25 and ICS is hboot 1.24
Take a look at this:
http://forum.xda-developers.com/showthread.php?t=2502327&highlight=guide+hboot
GtrCraft said:
You are using the wrong recovery for your hboot: JB is hboot 1.25 and ICS is hboot 1.24
Click to expand...
Click to collapse
It says "HBOOT - 1.25.0002", so it is JB. I thought I used the right recovery.. will install another recovery. To install the recovery I have now, I used the Windroid toolkit for the Desire X.. Maybe I chose the wrong version or something ..
dansou901 said:
Take a look at this:
http://forum.xda-developers.com/showthread.php?t=2502327&highlight=guide+hboot
Click to expand...
Click to collapse
Thanks for the link. Will try to install another recovery for JB when I get home from work.
EDIT: I tried it, but it still failed.. any other suggestions?
hey guys please please help i had the custom rom pac nightly now here is where the sh*t went down, i tried to put on carbon and flashed the kernel with that and since then im unable to get back root i have locked the bootloader and tried unlocked the bootloader, the screen comes up to the point where the rom loads and the lil vibrate happens, and then pufff it just goes back to the boot up and then again and again !!! how can i fix this please help
Flash a boot.img with recovery and reflash.
Sent from my Z Ultra
LordManhattan said:
Flash a boot.img with recovery and reflash.
Sent from my Z Ultra
Click to expand...
Click to collapse
thanks buddy for the response but tried it and wont work !!!
Is your bootloader unlocked at the moment?
It should work as lordmanhattan said.
Flash boot.img from carbon
Flash carbon from recovery.
You could start over and flash new ftf then do the above instructions...
Sent from CarbonROM on my Z-Ultra
blueether said:
Is your bootloader unlocked at the moment?
It should work as lordmanhattan said.
Flash boot.img from carbon
Flash carbon from recovery.
You could start over and flash new ftf then do the above instructions...
Sent from CarbonROM on my Z-Ultra
Click to expand...
Click to collapse
yes bootloader is unlocked
sorry i know im being tedious but just to re check ...
1. flash ftf (my zu is from HK so the latest is .681 ftf)
2. then fash the boot.img from carbon
3. then flash carbon onto my phone
in this order you reckon it would fix my problem?
(going ahead and giving it a try anyways in the above order lets see if it pans out)
ashankanand said:
yes bootloader is unlocked
sorry i know im being tedious but just to re check ...
1. flash ftf (my zu is from HK so the latest is .681 ftf)
2. then fash the boot.img from carbon
3. then flash carbon onto my phone
in this order you reckon it would fix my problem?
(going ahead and giving it a try anyways in the above order lets see if it pans out)
Click to expand...
Click to collapse
As you seem to be having issues I would go back to stock and satrt again, and the steps above should do just that for you. I would boot up after the first step just to check that everything is upto speed on the phone.
I wouldn't worry about getting a HK firmware, just use any of the unbranded/generic US/EU 757 FTFs
I cant see why it didn't work straight from PAC , hell the kernel in Carbon boots the latest PAC just fine
blueether said:
As you seem to be having issues I would go back to stock and satrt again, and the steps above should do just that for you. I would boot up after the first step just to check that everything is upto speed on the phone.
I wouldn't worry about getting a HK firmware, just use any of the unbranded/generic US/EU 757 FTFs
I cant see why it didn't work straight from PAC , hell the kernel in Carbon boots the latest PAC just fine
Click to expand...
Click to collapse
ok bud tired it now the problem is the dam phone keeps going into recovery boots and gets stuck on sony and then reboots and goes into recovery any advice!!!
Flash a stock tft with flashtool in flashmode and it should work again.
Anyways flashing the kernel with the boot.img in fastboot mode should work.
Have tried that flashed the latest ftf. Then used the root guide didn't work used the boot.img from carbon from pac rom. Still just reboots , my issue is I want a custom rom cos I'm happier with a custom rom, so I get root on the stock. But I can't seem to load a custom rom, first it was midway boot now it's recovery reboots , I want a custom rom any advice .
Sent from my C6833 using XDA Free mobile app
ashankanand said:
Have tried that flashed the latest ftf. Then used the root guide didn't work used the boot.img from carbon from pac rom. Still just reboots , my issue is I want a custom rom cos I'm happier with a custom rom, so I get root on the stock. But I can't seem to load a custom rom, first it was midway boot now it's recovery reboots , I want a custom rom any advice .
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
Do it like this:
- flash boot.img (flashtool: fastboot mode)
- wipe cache/dalvik cache (CWM Recovery)
- flash the ROM[.zip] (CWM Recovery)
- flash the GAPPS[.zip] (CWM Recovery)
- reboot
That should work.
I mean flashed ftf , fastbooted boot.img from carbon, had recovery reboots (meaning the phone would boot up stuck on Sony logo and then reboot into recovery ) then tried pac rom boot.img no help, infact flashed ftf cleard cache and data and then flashed boot.img flashed rom , had same recovery issue, then tried a full wipe, (ofcourse flashed ftf again) I mean went into mount storage and formated cache data system etc etc, now I'm really baffeld I have tried everything I find myself getting everything to work except putting the custom rom someone help
Sent from my C6833 using XDA Free mobile app
ashankanand said:
I mean flashed ftf , fastbooted boot.img from carbon, had recovery reboots (meaning the phone would boot up stuck on Sony logo and then reboot into recovery ) then tried pac rom boot.img no help, infact flashed ftf cleard cache and data and then flashed boot.img flashed rom , had same recovery issue, then tried a full wipe, (ofcourse flashed ftf again) I mean went into mount storage and formated cache data system etc etc, now I'm really baffeld I have tried everything I find myself getting everything to work except putting the custom rom someone help
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
You forgot to flash the rom itself. Just flashing the kernel (boot.img) doesn't to anything instead of flashing
the kernel. You need to flash the ROM to have working Operation System. That's why just the logo shows
up and goes into recovery. Put the ROM (the .zip file of the rom) on your SD Card and go into recovery
and go to "install .zip" and choose your file. After that the ROM should be loading after Boot Logo. Don't forget
to flash the GAPPS after flashing rom.
Pacman Rom: www.blownco.com/index.php/doc_download/13688-pac-togari-4-3-build-1-20131214-044914
Pacman Gapps: www.blownco.com/index.php/doc_download/13604-gapps-jb-20130813-signed
here is an example for installing the rom and gapps:
https://www.youtube.com/watch?v=n0In32vjxIg&feature=player_embedded
Just do the same with your files.
Flashed the rom buddy , every time ofcourse I thought I didn't need to mention that hehe ,
Sent from my C6833 using XDA Free mobile app
ashankanand said:
Flashed the rom buddy , every time ofcourse I thought I didn't need to mention that hehe ,
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
I was wondering man. Can you provide us with a link of the rom you want to use.
tr0teK said:
I was wondering man. Can you provide us with a link of the rom you want to use.
Click to expand...
Click to collapse
carbon rom : http://forum.xda-developers.com/devdb/project/dl/?id=5119
Pac-rom : http://pacman.basketbuild.com/download.php?file=main/togari/nightly/pac_togari-nightly-20140505.zip
How to reproduce your error step by step ?
tr0teK said:
How to reproduce your error step by step ?
Click to expand...
Click to collapse
ok not so clear on what you are asking but here goes
had a c6802 cracked the screen (using carbon rom on it loved it) bought a c6833 wanted to try pac rom put it on realized my batt consumption is way too high so tried to switch back to carbon now, while doing so i flashed carbon rom Double tap to wake and carbon kernel, here started the spiral, first few hours couldn get any thing to work read up looked up a few of the forum, and ftf fashed the generic hk rom things got ok, but then root was the issue so found out the root method, fastboot .img and flash cmw supersu.zip, all fine and dandy didnt mess with it in anyway
since then as i have explained im gettin a recovery loop even when i flash the stock rom (cmw flash not ftf) so now i have the latest stock rom with root but i have sony's stock i want a rock in which i can add a menu button and change the dip and everything doesnt crash if you know what i mean....
ashankanand said:
ok not so clear on what you are asking but here goes
had a c6802 cracked the screen (using carbon rom on it loved it) bought a c6833 wanted to try pac rom put it on realized my batt consumption is way too high so tried to switch back to carbon now, while doing so i flashed carbon rom Double tap to wake and carbon kernel, here started the spiral, first few hours couldn get any thing to work read up looked up a few of the forum, and ftf fashed the generic hk rom things got ok, but then root was the issue so found out the root method, fastboot .img and flash cmw supersu.zip, all fine and dandy didnt mess with it in anyway
since then as i have explained im gettin a recovery loop even when i flash the stock rom (cmw flash not ftf) so now i have the latest stock rom with root but i have sony's stock i want a rock in which i can add a menu button and change the dip and everything doesnt crash if you know what i mean....
Click to expand...
Click to collapse
maybe the solution for you would be too install xposed framework which gives you the features you want. It allows your to "modify" your stock rom like the advanced power button menu, editing the navigation and status bar and stuff like that.
http://repo.xposed.info/module/de.robv.android.xposed.installer
you obviously need ROOT for this.
tr0teK said:
maybe the solution for you would be too install xposed framework which gives you the features you want. It allows your to "modify" your stock rom like the advanced power button menu, editing the navigation and status bar and stuff like that.
http://repo.xposed.info/module/de.robv.android.xposed.installer
you obviously need ROOT for this.
Click to expand...
Click to collapse
so yeah not to be a buzz killl buddy i know i am here asking for help and i really appreciate it but i tried that and gives me system ui errors cos i would have been ok with xposed but its not working great especially the special xposed for xperia cos the generic xposed is not workin anyway
ashankanand said:
so yeah not to be a buzz killl buddy i know i am here asking for help and i really appreciate it but i tried that and gives me system ui errors cos i would have been ok with xposed but its not working great especially the special xposed for xperia cos the generic xposed is not workin anyway
Click to expand...
Click to collapse
Which ROM do you have installed exactly ? In which country do you live ?
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.