I know I shouldn't be asking questions in development, but it is to do with development.
I am working on a little project for you GT540 users, but I need to extract the "kernel_ramdisk_OPEN_BAL.mbn" file that is found when you extract the DZ_GT540xxxxxx.dz file. Is there a way to unpack the file and re-pack it into a boot.img file? Also, this project is secret, but don't know if it will work or not
Jack
Edit: forgot to mention, the file will not extract with unyaffsmbn as boot images are not packed in yaffs.
I really don't know. If you can describe what project you're working on, probably I can help
tejasdj12 said:
I really don't know. If you can describe what project you're working on, probably I can help
Click to expand...
Click to collapse
I am basically wanting to extract the kernel and ramdisk from an official LG ROM. But as there is no boot.img, I cannot extract it using the conventional tools.
why don't you use quarx kernel?
JackG256 said:
I am basically wanting to extract the kernel and ramdisk from an official LG ROM. But as there is no boot.img, I cannot extract it using the conventional tools.
Click to expand...
Click to collapse
Instead I've compiled the kernel image (zImage) from the LG Source Code. I've attached the Kernel Image.
tejasdj12 said:
Instead I've compiled the kernel image (zImage) from the LG Source Code. I've attached the Kernel Image.
Click to expand...
Click to collapse
I guess i'm going to have to tell you what im doing lol
Basically i'm trying to get Android 1.6 back on to the GT540, for those who have upgraded to 2.1 and maybe want to get back to 1.6. I don't think this project is very significant, just wanted to do it for fun (i'm nerdy like that lmao) What I was aiming to do is basically just take the kernel and system and turn them into recovery backup/fastboot images.]
Jack
max1919 said:
why don't you use quarx kernel?
Click to expand...
Click to collapse
I can't as I need to use the 1.6 kernel.
aha!
I have found your solution maybe :L
http://4pda.ru/forum/index.php?showtopic=184435
Try that , If you're using Chrome , just click Translate to Polish , if not , use google translate to translate the page
P.S. I tried to install your V20E Baltics rom , but it constantly reboots , I was using a Data 2 System rom, but erased all partitions except recovery in recovery , anyway, doesn't matter , got back to 2.1 Europe open , and now im going back to the original software (Carphone Warehouse) I'm actually looking forward to see if this works , as I had 1.6 for all of about 5 minutes then installed 2.1 so I've never actually used it LOL
Jamielawther said:
aha!
I have found your solution maybe :L
http://4pda.ru/forum/index.php?showtopic=184435
Try that , If you're using Chrome , just click Translate to Polish , if not , use google translate to translate the page
P.S. I tried to install your V20E Baltics rom , but it constantly reboots , I was using a Data 2 System rom, but erased all partitions except recovery in recovery , anyway, doesn't matter , got back to 2.1 Europe open , and now im going back to the original software (Carphone Warehouse) I'm actually looking forward to see if this works , as I had 1.6 for all of about 5 minutes then installed 2.1 so I've never actually used it LOL
Click to expand...
Click to collapse
Strange, it worked fine for me, could be a kernel issue. I'll check that out, but anyways, I used them tools to unpack the system anyway, unyaffsmbn will not unpack boot images as boot images are not packed in yaffs.
Jack
Here is a little tool that I create a some time ago to convert boot.mbn to boot.img.
http://4pda.ru/forum/index.php?showtopic=184435&view=findpost&p=5277920
Mur4ik said:
Here is a little tool that I create a some time ago to convert boot.mbn to boot.img.
http://4pda.ru/forum/index.php?showtopic=184435&view=findpost&p=5277920
Click to expand...
Click to collapse
Thanks Mur4ik, you've saved the day, yet again
Edit, didn't boot, didn't even get past bootloader.
Jack
jack i think i will try and help you with this project i used to have a lg viewty that uses .mbn for its firmware i will see if those tools used on that can do anything for this project
look here
http://forum.xda-developers.com/showthread.php?t=1123968
might be on to something
Related
VS910ZV9_05.S9_05.P58014.R5.tot
how use this frimware been waiting too root it u never know jcase
Holy crap... where did you get this?
This can't be real...
I'm confused what exactly is this?
nasirahmed said:
VS910ZV4_04.S4_04.P58008.R5.user.tot
Click to expand...
Click to collapse
One million internets to you, sir(or madam)...
Sent from my VS910 4G using Tapatalk
is this so we can get developers to make a custom recovery??????????
it is supposed to be the stock firmware for the revolution which would allow you to flash your system back to stock.
I have scanned the file and there are 3 files contained inside. I have not been able to extract them however. There are 3 img files inside which tally some 700+ meg.
Haxcid said:
it is supposed to be the stock firmware for the revolution which would allow you to flash your system back to stock.
I have scanned the file and there are 3 files contained inside. I have not been able to extract them however. There are 3 img files inside which tally some 700+ meg.
Click to expand...
Click to collapse
I have not found a way to extract the embedded files either. This is used with a Verizon only tool that is readily available. I wouldn't recommend flashing this unless you brick or destroy your phone (as a last result).
how u flash this
blkhwk5177 said:
how u flash this
Click to expand...
Click to collapse
It's a program called: LGNPST. You can Google it and you will find a few download locations.
I looked everywhere to find out how to load this, can somebody with lg experience point me in the right direction. im coming from a droid x, i would just sbf to restore a phone; that was easy
LGPNST does not support this device yet that I know of.
Verizon has a tool as well but I don't think it works with TOT files.
Haxcid said:
LGPNST does not support this device yet that I know of.
Verizon has a tool as well but I don't think it works with TOT files.
Click to expand...
Click to collapse
Yeah, you have to have the proper DLL, and we haven't found it yet. Cubed said he'd have a stock ROM out here shortly.
After that, he plans to deodex and release a cleaned version of stock (debinged)
majorpay said:
Yeah, you have to have the proper DLL, and we haven't found it yet. Cubed said he'd have a stock ROM out here shortly.
After that, he plans to deodex and release a cleaned version of stock (debinged)
Click to expand...
Click to collapse
I'm really looking forward to de-binged, de-odexd etc. Rom!!!
Hi,
this is the factory soft provided by LG to update VS910.
[LGDP2V42]only_VS910_20110430_download
but this soft need a protection dongle (need to be attached to PC) to run. LG Service Centers have this. It will be intersting if someone can find something useful from it.
I don't know if it works or not but...
http://www.mobile-files.com/forum/showthread.php/1384-How-load-TOT-file-with-LGNPST-LAB.1.2
So i guess in LGNPST, you just click browse, then put *.* in file name, hit enter, then select your .tot.
The problem isnt getting the software its the fact that unlike motorola the lg program requires a device specific .dll file so without that file the flash software and firmware are really of no use
Sent from my rooted and de-Bing-ed LG Revolution
vs910 dll for npst
here is the dll u need to flash this firmware... as far as firmware u should be able to flash with npst lab version. u need to register dll first
lazarus2297 said:
The problem isnt getting the software its the fact that unlike motorola the lg program requires a device specific .dll file so without that file the flash software and firmware are really of no use
Sent from my rooted and de-Bing-ed LG Revolution
Click to expand...
Click to collapse
give me the link for the lab installer and the rest of the steps
I want to offer you a little fix for those of you who actually experience this problem. On some Samsung based ROMs, some people complain about not working cameras, no matter how often they tried to install a ROM after several wipes. This error may occur in case your camera uses a different firmware.
Most people however won´t experience this error.
I´ve created a little Fix which is actually very easy to apply as a flashable zip. It was intended to be used with my Samsung Galaxy S3 ROM, it may also work with every other Samsung based ROM
Here is the link: Camera Fix for Samsung based ROMs
Simply install this file through your custom recovery
Just in case this patch should not work for everyone, leave me a comment and I´ll see what I can do :angel:
What does it do?
Sent from my CM10.3 Galaxy S3.
This fix includes one missing binary which some specific cameras require in order to be able to be used.
If you don´t have any trouble starting the camera app, using the camera, you don´t need to flash this zip Even if everything works fine and you do install this fix, it wouldn´t harm your system
habylab said:
What does it do?
Sent from my CM10.3 Galaxy S3.
Click to expand...
Click to collapse
just flashed it, doesn`t work for me unfortunately. :crying: :crying: :crying:
i have this problem you told of since a very long time and i really can't get rid of it. makes me fckn sick. i could cry on and on.
what else is possible to do? every litte hint is very much appreciated.
There are more binaries available, the one I included is a more common one. Samsung uses 2 different cameras ( Sony or Samsung ).
Does your camera work 100% with a Stock ROM ? If so, have a closer look in /data/cfw and show me what you find inside ( eg. SlimISP_xx.bin ).
Flash a Stock Firmware, make sure to copy the file and add it here as a zip file. By installing custom ROMs, your cfw folder will be empty most the time if these files are not added by the ROM itself.
g.ott said:
just flashed it, doesn`t work for me unfortunately. :crying: :crying: :crying:
i have this problem you told of since a very long time and i really can't get rid of it. makes me fckn sick. i could cry on and on.
what else is possible to do? every litte hint is very much appreciated.
Click to expand...
Click to collapse
If that fix not help you can maybe make a camera fw upgrade.
[tapatalk]printed, scanned and faxed...[/tapatalk]
hi guys,
thx a lot for your words. here is what i've done:
i just flashed a stock rom and the camera works. then i installed cf root and root explorer but /data/cfw is an empty folder. so i can`t copy anything here.
with the custom rom and the cam not working i had a file like SlimlSp00.bin (or something similar) in this particular folder but not now.
what to do now or did i misunderstand something?
Gorgtech said:
There are more binaries available, the one I included is a more common one. Samsung uses 2 different cameras ( Sony or Samsung ).
Does your camera work 100% with a Stock ROM ? If so, have a closer look in /data/cfw and show me what you find inside ( eg. SlimISP_xx.bin ).
Flash a Stock Firmware, make sure to copy the file and add it here as a zip file. By installing custom ROMs, your cfw folder will be empty most the time if these files are not added by the ROM itself.
Click to expand...
Click to collapse
Just out of curiosity, did you try to remove this file ? Maybe your camera tries to load this binary though it´s not suitable for your model. You can try to create a different folder and first copy the found bin ( just to have a spare copy ), remove SlimlSpxxx out of your data/cfw folder.
Wipe your Dalvik Cache and restart the ROM
g.ott said:
hi guys,
thx a lot for your words. here is what i've done:
i just flashed a stock rom and the camera works. then i installed cf root and root explorer but /data/cfw is an empty folder. so i can`t copy anything here.
with the custom rom and the cam not working i had a file like SlimlSp00.bin (or something similar) in this particular folder but not now.
what to do now or did i misunderstand something?
Click to expand...
Click to collapse
this idea didn't come up of course
but i just tested it. i already had my custom rom backup restored. i moved the SlimlSP_BH.bin to my ext sd, so that /data/cfw was empty, rebooted to recovery, wiped dalvik and it doesn't worked. second try i wiped cache and dalvik and it also doesn`t work.
Gorgtech said:
Just out of curiosity, did you try to remove this file ? Maybe your camera tries to load this binary though it´s not suitable for your model. You can try to create a different folder and first copy the found bin ( just to have a spare copy ), remove SlimlSpxxx out of your data/cfw folder.
Wipe your Dalvik Cache and restart the ROM
Click to expand...
Click to collapse
If your camera doesn´t work with this binary, you may need another one..and there are lots of them to try but you have to chose one which is suitable for a Sony or a Samsung camera Well, there is a easier way out if you try to upgrade your camera firmware.
Before we proceed, I need some details first, which type of camera you have in order to pick up a suitable binary.
1) Dial *#34971539#
2) pick up this option: "Phone/Cam FW Check"
3) Show me what you see
4) Chose this option: "Phone/Cam FW Write"
A short explanation :
GDxxx = Sony
ZFxxx = Samsung
g.ott said:
this idea didn't come up of course
but i just tested it. i already had my custom rom backup restored. i moved the SlimlSP_BH.bin to my ext sd, so that /data/cfw was empty, rebooted to recovery, wiped dalvik and it doesn't worked. second try i wiped cache and dalvik and it also doesn`t work.
Click to expand...
Click to collapse
alright, i for sure will give you every information you need.
under "phone/cam fw ver check" i see
rear camera
cam fw ver: GDF
phone fw ver: GDFI02
front camera
cam&phone fw ver: S5K6A3
"Phone/Cam FW Write" isn't available in that form. options with "write" are only "phone to cam fw write (rear)" (but this is greyed out so i can't touch it) and "fw write count".
Gorgtech said:
If your camera doesn´t work with this binary, you may need another one..and there are lots of them to try but you have to chose one which is suitable for a Sony or a Samsung camera Well, there is a easier way out if you try to upgrade your camera firmware.
Before we proceed, I need some details first, which type of camera you have in order to pick up a suitable binary.
1) Dial *#34971539#
2) pick up this option: "Phone/Cam FW Check"
3) Show me what you see
4) Chose this option: "Phone/Cam FW Write"
A short explanation :
GDxxx = Sony
ZFxxx = Samsung
Click to expand...
Click to collapse
hi gorgtech, are you still here?
I´m still here but I´m not quite sure how to help you out. There is another way to enforce an upgrade of your Firmware but I´m not sure if this would work out for everyone.
I´ll see what I can do later and prepare a zip file for you
g.ott said:
hi gorgtech, are you still here?
Click to expand...
Click to collapse
Gorgtech said:
I want to offer you a little fix for those of you who actually experience this problem. On some Samsung based ROMs, some people complain about not working cameras, no matter how often they tried to install a ROM after several wipes. This error may occur in case your camera uses a different firmware.
Most people however won´t experience this error.
I´ve created a little Fix which is actually very easy to apply as a flashable zip. It was intended to be used with my Samsung Galaxy S3 ROM, it may also work with every other Samsung based ROM
Here is the link: Camera Fix for Samsung based ROMs
Simply install this file through your custom recovery
Just in case this patch should not work for everyone, leave me a comment and I´ll see what I can do :angel:
Click to expand...
Click to collapse
about time someone done this! thanks! i thought i corrupted the drivers, but thats for the fix!
Dude, brilliant, this works on KitKat roms also, I have spread the word and linked your thread to the benefit of all.
Thank you
Sent from my GT-I9300
does this really work? can someone add it to aosp code then? @XpLoDWilD @CarbonDev
ayoubij said:
does this really work? can someone add it to aosp code then? @XpLoDWilD @CarbonDev
Click to expand...
Click to collapse
Well it works perfectly for me, but @Moster2 says the md5 checksum is identical to the files already in place, but it works. I'm both happy but mildly confused! If you get the issue it's obviously with trying! You only need to flash the rom to remove it, so it's of no concern to try
Sent from my GT-I9300
metalgearhathaway said:
Well it works perfectly for me, but @Moster2 says the md5 checksum is identical to the files already in place, but it works. I'm both happy but mildly confused! If you get the issue it's obviously with trying! You only need to flash the rom to remove it, so it's of no concern to try
Sent from my GT-I9300
Click to expand...
Click to collapse
I'm wrong, this method went wayward for me in the end :banghead:
Sent from my GT-I9300
metalgearhathaway said:
I'm wrong, this method went wayward for me in the end :banghead:
Sent from my GT-I9300
Click to expand...
Click to collapse
Damn!
Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
Well done. Works perfectly.
I tried just about everything I could find regarding fixing the camera in my S3, including manually replacing the Camera2.apk and this is the first fix I tried that actually works. Thanks for putting the time and effort in to solve this annoying problem.
Hello to you guys,
with this thread I wanna help people who get a Live Demo Unit of Galaxy S5 and wanna "unlock" it, removing Retail Mode and getting an official firmware on it. A Live Demo Unit is recognizable cause the phone has an "X" after the "SM-G900" signature.
Before start explain, I wanna remember to all that with a Live Demo Unit YOU CAN'T DO PHONE CALLS or TEXT MESSAGING due to its nature. So, this custom friwmare will transform your Live Demo Unit in a beautiful and complete Galaxy S5 "WiFi Version" .
Ok, lets do this!
What you need for a great job is:
Samsung USB Drivers on your PC
Odin, downloadable from here http://odindownload.com/ (vers. 3.09)
TWRP Recovery, .tar extension (here is the link for the download http://techerrata.com/browse/twrp2/klte)
Firwmare of your country. You can get it form sammobile.com. I've done this with the G900F version and I've tested only with it but I think this kind of guide works for all devices. Be sure to download the correct Firmware of your device!!
A program named "cgywin" for create your own firmware for the Live Demo Unit http://cygwin.com/setup.exe
Do this AT YOUR OWN RISK!! If you're not sure to have understand something, please do not go any further.
Ok, so let's start to explain what to do. If you'll follow step by step this procedure, you'll reach the goal for sure
First, I think is better to do a good and complete backup of your actual firmware and system. To do that follow those steps:
Install Samsung USB driver in your PC (if you don't have it already). Be sure that the phone is visible by your PC.
Turn off the device and go into Download mode (pressing VolDown+Home+Power).
Open Odin and connect your device to the PC.
Now flash the TWRP Recovery (select "AP" voice on Odin and choose TWRP .tar file you have already downloaded)
Ok, now you can do a Nandroid backup of your entire phone, including system, with Recovery. So, turn off the device and go into Recovery, then choose "Backup" and flag ALL the voices (so you'll be sure to backup all). Save it in external MicroSD so you can get it simply if you need it.
After the complete backup, it's time to "prepare" the custom firmware:
Install cgywin (for a complete guide for How To Install this program, Google it)
Download the right firmware for your device
Once file is downloaded you will have something looking like this G900FXXU1ANCE_G900FITV1ANC7_ITV (this is the one I've used)
Extract the .zip file to get an .md5
Rename it with like ldu900x.tar
Go into the folder were you've install cgywin and put the ldu900x.tar here
Now, launch cgywin.exe and type those command
$ tar --delete --file=ldu900x.tar NON-HLOS.bin
$ tar --delete --file=ldu900x.tar modem.bin
After that, the ldu900x should have only those files on it:
- boot.img
- cache.img.ext4
- hidden.img.ext4
- recovery.img
- system.img.ext4
If there are other files that are not those I've checked above, please delete them using the command $ tar --delete --file=samrom.tar FileName on cgywin as explained. The final .tar file gotta have only those 5 files I've listed above.
Once the final ldu900x.tar is ready, you can flash it with Odin.
Before the flash, use TWRP for a TOTAL WIPE of the device (including system but do not wipe the extSDcard). This is for to be sure that the device will be ready for a good and clear flash.
After the flash with Odin, reflash the TWRP Recovery (following the steps above) so you can do other backup or restore the old firmware if you need it.
Hope this guide can help all the guys who need to use their LDU completely (excluding calls and SMS as said). Personally my LDU doesn't have Private Mode, Finger Scanner, S-Health, UltraPowerSavingMode and other stuff, but with this "custom" firmware made by myself, now works ALL! :victory:
Bugs: The only thing that does not work here is the upgrading of SHealth Services that does not allow to upgrade it to SHealth 3.1 version. If anyone know how to solve this I appreciate
Thank you guys for your support and thanks to:
@Dees_Troy for TWRP
@Sirus2012 for have opened the way
@jopa7 for suggestions
Fell free to offer me a beer (or a meat can for my 5 cats )
Have a good flash to all!
Reserved
Cool might be helpful
Sent from my SM-G900H using XDA Premium 4 mobile app
Got pumped when I saw rom.... Been waiting for aosp Lol...
Sent from my SM-G900F using Tapatalk
bjc112 said:
Got pumped when I saw rom.... Been waiting for aosp Lol...
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Same here... But might be helpful anyway [emoji106]
Great work , pm you to send you a beer! You could upload the tar to somewhere and put here the link.
Cheers
Sent from my HTC One max using xda app-developers app
Thank you guys! Sorry for give you an illusion of a SUPERPOWERFUL ROM @jopa7 I'm uploading it on my Dropbox. If you give me your email I can share it to you!
iorya984 said:
Thank you guys! Sorry for give you an illusion of a SUPERPOWERFUL ROM @jopa7 I'm uploading it on my Dropbox. If you give me your email I can share it to you!
Click to expand...
Click to collapse
You can install a superpower rom, mate. Install omega with omega kernel after root with chain CF auto root and install TRWP. Install latest omega zip via trwp chosing omega kernel too. You will get 37000 antutu score or more . By the way, GPS signal works
jopa7 said:
You can install a superpower rom, mate. Install omega with omega kernel after root with chain CF auto root and install TRWP. Install latest omega zip via trwp chosing omega kernel too. You will get 37000 antutu score or more . By the way, GPS signal works
Click to expand...
Click to collapse
Jopa7 are you talking about to flash Omega Rom on LDU? Did you do that?
iorya984 said:
Jopa7 are you talking about to flash Omega Rom on LDU? Did you do that?
Click to expand...
Click to collapse
works like charm!
Have you flashed the entire ROM, also with modem.bin?
iorya984 said:
Have a good flash to all!
Click to expand...
Click to collapse
Thanks a lot for instructions ...
it works
Question
hello to everybody, i have a question, i have an s5 ldu and when i enter those commands in cygwin says that those files doesnt exist in the archive but that's not true, some help? TY:silly:
gzincu said:
hello to everybody, i have a question, i have an s5 ldu and when i enter those commands in cygwin says that those files doesnt exist in the archive but that's not true, some help? TY:silly:
Click to expand...
Click to collapse
I was having same problem and then I downloaded Ubuntu live cd to delete those files
You will have to use terminal for that
Or you can pm author of this thread for precompiled version
help
He doesn't seem to be active on this forum, i would be very happy if you cand send to me the precompiled archive. Thanks alot!
gzincu said:
He doesn't seem to be active on this forum, i would be very happy if you cand send to me the precompiled archive. Thanks alot!
Click to expand...
Click to collapse
Send me your dropbox id through pm
Pre-Compiled version by iorya984
Pre-Compiled version by iorya984
Download Links:-
http://ul.to/dwe11uck
http://ul.to/uvu2vbt0
All Credit goes to iorya984
Proper Tutorial
jopa7 said:
You can install a superpower rom, mate. Install omega with omega kernel after root with chain CF auto root and install TRWP. Install latest omega zip via trwp chosing omega kernel too. You will get 37000 antutu score or more . By the way, GPS signal works
Click to expand...
Click to collapse
Hi all and thank you for this great tutorial. How did you manage to get the gps to work? It shows it's searching for gps signal but never gets it... did you flash a certain modem file?
Anyone get S health to work??
Thank all!!!
aaa82 said:
Anyone get S health to work??
Click to expand...
Click to collapse
same question from me
hello
thankyou for the precompiled files, i am a boot, i dont know what to do exactly, where i have to add the ldu900x.tar in odin? BL, AP,CP or CSC?
Hi Guys!
So I got my hands on an HTC One Mini 2 Demo Unit. Don't ask me how or why. (NOT STOLEN!)
I have tried to get rid of the Demo mode app but without success.
This is what I have done:
Unlocked the bootloader
Flashed TWRP
This is what I have tried to do to get rid of the demo mode:
Wiping and factory reset from TWRP. About 1 minute after the phone has booted it autoinstalls the Demo Mode again. Before it does all functions is available etc, after the demo mode is installed some options and functions is disabled.
Rooted, Installed Xposed and module BootManager to stop Demo Mode from booting, no success the demo app still starts upon boot
Tried to uninstall the app with various root uninstallers, they just fail.
Tried wiping ALL partitions etc from TWRP and restored an original HTC One Mini 2 system dump from another thread, same thing. After about one minute the Demo application autoinstalls itself and some functions is diabled and the annoying demo mode starts now and then, and blinkfeed is full of sh*t, demo contacts etc.
After I reboot all settings etc is restored to it's original state.
Any ideas how I can force the phone not to install the demo mode after reset?
Thanks!
Update: Flashing the Cyanogenmod firmware from another thread does not install the demo mode and the phone works as it should. I can call etc. But I only have 3G not 4G, don't know if it has to do with the sim or not (borrowed a nano-sim from a collegues iPhone 5s).
But anyhow I would like to have the HTC firmware instead, any ideas?
Maybe someone has another system dump/ruu/firmware or any of the sort I can try. Perhaps the firmware I tried in the other thread also was a demo-firmware (http://forum.xda-developers.com/showpost.php?p=55107684&postcount=6)
B3t4 said:
Update: Flashing the Cyanogenmod firmware from another thread does not install the demo mode
Click to expand...
Click to collapse
As you probably figured it was an app in the ROM so installing a custom ROM or reverting back to stock will get rid of the problem (as you've already done it)
yourmate said:
As you probably figured it was an app in the ROM so installing a custom ROM or reverting back to stock will get rid of the problem (as you've already done it)
Click to expand...
Click to collapse
Thank you for your answer. I have however tried to restore the original ROM and another original dump from this forum but the app installs itself anyway. Any idea where I can get another clean ROM or system dump?
B3t4 said:
Thank you for your answer. I have however tried to restore the original ROM and another original dump from this forum but the app installs itself anyway. Any idea where I can get another clean ROM or system dump?
Click to expand...
Click to collapse
I'd unlock it first on htcdev and then root and flash a custom recovery.
Then you'd either flash back to stock or flash a custom ROM.
I hope this helps
yourmate said:
I'd unlock it first on htcdev and then root and flash a custom recovery.
Then you'd either flash back to stock or flash a custom ROM.
I hope this helps
Click to expand...
Click to collapse
As stated in the OP I have already unlocked the bootloader and flashed a custom recovery. CyanogenMod works but very buggy build, and either way I would like to have the original ROM or something close to it (Sense). Unfortunately there are no custom roms for this phone yet (other then CM). I have only found one original TWRP dump that I tried but the demo mode installed itself on that dump as well. I don't know why it installed itself on the original rom from this forum... Thanks
B3t4 said:
As stated in the OP I have already unlocked the bootloader and flashed a custom recovery. CyanogenMod works but very buggy build, and either way I would like to have the original ROM or something close to it (Sense). Unfortunately there are no custom roms for this phone yet (other then CM). I have only found one original TWRP dump that I tried but the demo mode installed itself on that dump as well. I don't know why it installed itself on the original rom from this forum... Thanks
Click to expand...
Click to collapse
Sorry, my bad.
My understanding is that this is an app so if it's not in the ROM then it cannot run.
There are a few other custom ROM but if you want stock follow this by the letter.
yourmate said:
Sorry, my bad.
My understanding is that this is an app so if it's not in the ROM then it cannot run.
There are a few other custom ROM but if you want stock follow this by the letter.
Click to expand...
Click to collapse
Those instructions and ROMs are for the HTC One Mini and not the HTC One Mini 2. Also as far as I know there is no way to get S-OFF on the HTC One Mini 2 yet.
B3t4 said:
Those instructions and ROMs are for the HTC One Mini and not the HTC One Mini 2. Also as far as I know there is no way to get S-OFF on the HTC One Mini 2 yet.
Click to expand...
Click to collapse
Mini 2 works the very same way (obviously with its own ROM)
Do some digging
yourmate said:
Mini 2 works the very same way (obviously with its own ROM)
Do some digging
Click to expand...
Click to collapse
Thanks! I will give it a try, does not matter if I brick it anyways. My fiance dropped it and broke the glass so I will get a new demo unit.
B3t4 said:
Thanks! I will give it a try, does not matter if I brick it anyways. My fiance dropped it and broke the glass so I will get a new demo unit.
Click to expand...
Click to collapse
wow
I've flashed one two weeks ago (although not a demo unit but it was branded) it works OK
Changed several LCDs on Minis but not on Mini 2 yet.
Btw how much are the demo ones?
yourmate said:
wow
I've flashed one two weeks ago (although not a demo unit but it was branded) it works OK
Changed several LCDs on Minis but not on Mini 2 yet.
Btw how much are the demo ones?
Click to expand...
Click to collapse
What ROM/Backup did you use?
For me, free but can't tell the source. :good:
B3t4 said:
What ROM/Backup did you use?
For me, free but can't tell the source. :good:
Click to expand...
Click to collapse
So why don't you send two over and I'll do it and send you one back?
B3t4 said:
For me, free but can't tell the source. :good:
Click to expand...
Click to collapse
yourmate said:
So why don't you send two over and I'll do it and send you one back?
Click to expand...
Click to collapse
I've thought so that the conversation will dry out indeed
yourmate said:
I've thought so that the conversation will dry out indeed
Click to expand...
Click to collapse
Sorry I don't have permission to do that from my source.
I'll try to get some time over and try your suggestion, will get back with results.
did you have any luck removing the demo apps from the demo device, i also stuck with one
dest1 said:
did you have any luck removing the demo apps from the demo device, i also stuck with one
Click to expand...
Click to collapse
Download stock rim flashable via twrp and open it using WinZip or winrar goto system/etc/ and delete '.demo' folder. Then repack and flash, problem solved.
no need for reading the whole thread. in twrp mount preload and by using the twrp file manager navigate to /preload and delete everything you can find inside! do a factory reset and flashing "org" firmware should be done...
hypafly said:
Download stock rim flashable via twrp and open it using WinZip or winrar goto system/etc/ and delete '.demo' folder. Then repack and flash, problem solved.
Click to expand...
Click to collapse
I was going to do same thing, but how do you repack ? I mean I packed it with WinRAR, or 7Zip, but they compress the file, or maybe they don't pack it as TWRP format, so TWRP didn't recognise my file. Simply, how do you pack it ?
Ven99 said:
I was going to do same thing, but how do you repack ? I mean I packed it with WinRAR, or 7Zip, but they compress the file, or maybe they don't pack it as TWRP format, so TWRP didn't recognise my file. Simply, how do you pack it ?
Click to expand...
Click to collapse
Open the zip file that you want to flash with any zip manager you like, you don't need to extract the files, just navigate to the folder and delete the .demo folder and it will automatically repack it. Close it and copy it to your phone and flash normally. It will work.
Hello everyone.
Unfortunately my lg g4 bootlooped. And after extensive Google search, i see that most models have a tot file which disables big cores so u can run the phone on the small cores
Does the T-Mobile variant have such a tot file? if yes then can somebody give me the link? if no then can somebody create one using the following info?
Agimax said:
Why not just edit the files below for the two large cores (if you have root):
/sys/devices/system/cpu/cpu4/online (open file and change from a one to a zero)
/sys/devices/system/cpu/cpu5/online (open file and change from a one to a zero)
You could also just have the startup file do it (can modify the ripped system partition & put back on phone):
etc/dir/init.qcom.post_boot.sh (find your processor code - 8992 and add echo lines there with the rest of the cpu commands)
Click to expand...
Click to collapse
Please I'd be highly thankful if someone can help
XeniX_Force said:
Hello everyone.
Unfortunately my lg g4 bootlooped. And after extensive Google search, i see that most models have a tot file which disables big cores so u can run the phone on the small cores
Does the T-Mobile variant have such a tot file? if yes then can somebody give me the link? if no then can somebody create one using the following info?
Please I'd be highly thankful if someone can help
Click to expand...
Click to collapse
no such thing for any american variant
raptorddd said:
no such thing for any american variant
Click to expand...
Click to collapse
Cant someone with a working G4 crate one? i quoted a person who has given the way how to...
XeniX_Force said:
Cant someone with a working G4 crate one? i quoted a person who has given the way how to...
Click to expand...
Click to collapse
not sure . i cant...
sort of read this quickly does this help.? https://www.xda-developers.com/nexus-6p-bootloop-fix/
raptorddd said:
not sure . i cant...
sort of read this quickly does this help.? https://www.xda-developers.com/nexus-6p-bootloop-fix/
Click to expand...
Click to collapse
Well he also created modified boot images which disable the big cores. Can't someone create that for our device?
maybe @steadfasterX can
XeniX_Force said:
Well he also created modified boot images which disable the big cores. Can't someone create that for our device?
maybe @steadfasterX can
Click to expand...
Click to collapse
TWRP installed?
Then u could just modify the init file but I believe its too late. once bootlooping the run is over afaik.
.
steadfasterX said:
TWRP installed?
Then u could just modify the init file but I believe its too late. once bootlooping the run is over afaik.
.
Click to expand...
Click to collapse
yeah I'm bootlooped
Someone also fixed the Nexus 6 bootloop by creating modified images which disable the big cores.
Can't we(mostly you, you're the big dev) create a similar modified image that we can flash through LGUP?
XeniX_Force said:
yeah I'm bootlooped
Someone also fixed the Nexus 6 bootloop by creating modified images which disable the big cores.
Can't we(mostly you, you're the big dev) create a similar modified image that we can flash through LGUP?
Click to expand...
Click to collapse
you may have overseen it but I asked: TWRP installed?
and new question: bootloader unlocked?
I can't create TOT files
.
steadfasterX said:
you may have overseen it but I asked: TWRP installed?
and new question: bootloader unlocked?
I can't create TOT files
.
Click to expand...
Click to collapse
I'm bootlooped. can't reach anything except download mode
and yeah bootloader was unlocked.
oh you can't create tot files? aren't they just system images?
XeniX_Force said:
I'm bootlooped. can't reach anything except download mode
and yeah bootloader was unlocked.
oh you can't create tot files? aren't they just system images?
Click to expand...
Click to collapse
Afaik you need a box to create tot files.
Besides this I have never created any big core disabling but I know @the_naxhoo has.
if you can reach the download mode you could flash with the lglaf shell a modified boot image which is doing the job. If you do not have Linux get your copy of FWUL which has everything on board (like the lglaf shell).
The modded boot image has to disable the cores either by the cmdline or the sys echo or both. I saw that cmdline thing during my unlock attempts and think those are much better then the echo to sys..
Creating a kdz would be maybe possible
creating a TWRP zip for sure but I'm very very busy at the moment...
So just one more time (as still not answered.. ) do you had TWRP installed before the bootloop occurs?
...and If so what happens when you try to get into it?
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Afaik you need a box to create tot files.
Besides this I have never created any big core disabling but I know @the_naxhoo has.
if you can reach the download mode you could flash with the lglaf shell a modified boot image which is doing the job. If you do not have Linux get your copy of FWUL which has everything on board (like the lglaf shell).
The modded boot image has to disable the cores either by the cmdline or the sys echo or both. I saw that cmdline thing during my unlock attempts and think those are much better then the echo to sys..
Creating a kdz would be maybe possible
creating a TWRP zip for sure but I'm very very busy at the moment...
So just one more time (as still not answered.. ) do you had TWRP installed before the bootloop occurs?
...and If so what happens when you try to get into it?
.
Click to expand...
Click to collapse
i had twrp but now when i try to access twrp i get to wipe everything screen which then hangs when I choose yes
yeah I can get FWUL but i need steps to know what to do....
I even asked @XCnathan32 who just fixed the Nexus 6p bootloop to have a look into our device maybe he can benefit from this information u just posted.
XeniX_Force said:
i had twrp but now when i try to access twrp i get to wipe everything screen which then hangs when I choose yes
yeah I can get FWUL but i need steps to know what to do....
I even asked @XCnathan32 who just fixed the Nexus 6p bootloop to have a look into our device maybe he can benefit from this information u just posted.
Click to expand...
Click to collapse
Cmdline is how I disabled the cores on the Nexus, the fix is easy to do on a boot.img, but LG uses the KDZ files, which use a totally different file structure, and I'm not sure if the LG flash tool has file checks, even on unlocked bootloaders. I will do some research and see what I can do. If anyone has any knowledge on modifying kdz files, please tell me.
XCnathan32 said:
Cmdline is how I disabled the cores on the Nexus, the fix is easy to do on a boot.img, but LG uses the KDZ files, which use a totally different file structure, and I'm not sure if the LG flash tool has file checks, even on unlocked bootloaders. I will do some research and see what I can do. If anyone has any knowledge on modifying kdz files, please tell me.
Click to expand...
Click to collapse
asked steadfasterx about kdz and his reply is as follows
steadfasterX said:
me too. never created KDZs yet but there are tools for it - afaik.
My first approach would have been to flash the boot image in the download mode with the lglaf shell (https://github.com/steadfasterX/lglaf/tree/g4) .
requires to do a flash of a modified boot image with dd on /dev/block/mmcblk0 with the correct seek ..
.
Click to expand...
Click to collapse
XCnathan32 said:
Cmdline is how I disabled the cores on the Nexus, the fix is easy to do on a boot.img, but LG uses the KDZ files, which use a totally different file structure, and I'm not sure if the LG flash tool has file checks, even on unlocked bootloaders. I will do some research and see what I can do. If anyone has any knowledge on modifying kdz files, please tell me.
Click to expand...
Click to collapse
you may take a look on this: https://forum.xda-developers.com/showthread.php?t=2179431
not sure if that works though.. (quite old)
.
steadfasterX said:
you may take a look on this: https://forum.xda-developers.com/showthread.php?t=2179431
not sure if that works though..
.
Click to expand...
Click to collapse
But cant we just create a modified boot img and twrp img and flash through lglaf. then flash a rom zip though twrp?
XeniX_Force said:
But cant we just create a modified boot img and twrp img and flash through lglaf. then flash a rom zip though twrp?
Click to expand...
Click to collapse
sure thats what I said before
.
steadfasterX said:
sure thats what I said before
.
Click to expand...
Click to collapse
can u provide a stock boot img for Nathan to edit?
XeniX_Force said:
can u provide a stock boot img for Nathan to edit?
Click to expand...
Click to collapse
sure what was your installed ROM and version? best would be a link to it as well..
.
steadfasterX said:
sure what was your installed ROM and version? best would be a link to it as well..
.
Click to expand...
Click to collapse
stock. i was using lineage but I returned to stock and got bootloop after some days.
XeniX_Force said:
stock. i was using lineage but I returned to stock and got bootloop after some days.
Click to expand...
Click to collapse
tell me the exact version. v10h, v10n, v20g, v20o .. there are dozens of versions out there..
.