yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] alainsr:
[MENTION=4546353]ShadowEO[/MENTION], that's the kind of advice I was hoping for, thank you.

Before I go and try what you already suggested, is the first suggestion is as dangerous as the second one?

Also, if you could be patient and kind, I would like to tell a bit more about my situation and ask for your advice, even if you are not familiar with this specific device. It came with Kitkat installed and it's "SKU" (locale, I think) is WW (which probably stands for "worldwide", as opposed to what appear to be Chinese and Taiwanese markets specific version) and later upgraded to Lollipop (Asus version "3.23.40.52", SKU still = WW). Then I rooted it. Months pass, and I mistakenly authorize an OTA to the latest version ("3.24.40.78"), entering a bootloop state. To solve it I installed TWRP and tried to flash several official zip files provided by Asus, but none of them work. Either I get a wrong SKU or a wrong pre-installed version (too high or too low). It seems that when the updater script checks the installed version the result is the latest one ("3.24.40.78"), but the SKU is blank.

Now, having said all that, I would like to know your opinion: what version would you install (after formatting /system, for example)? The sucessfully rooted one ("3.23.40.52") or the latest and apparently currently installed one ("3.24.40.78")?

In case you can easily/readily identify issues that my prevent your previous suggestions to work, I will paste the full contents of the updater-script file of both these two lollipop versions below.

I will also paste the updater-script of the latest Kitkat version ("2.22.40.54"), if you think it's a good idea to downgrade or at least to downgrade first (and later raise it to lollipop again).

Sorry if posting all the code below is abusive (if so, please forgive me), but I don't who who else to talk to. Again, I appreciate your help a lot!
[Android Q&A, Help & Troubleshooting] ShadowEO:
To remove the SKU check: remove this line

getprop("ro.build.asus.sku") == "WW" || abort("Please use the right SKU for updating...");

With all luck, you should be booting again on the correct SKU. I would be sure to format the /system partition. If you'd like to play around with that some more. It looks like all of the getprop() statements are for checking device hardware in this script.

Make sure to remove META-INF/manifest.* files or resign the ZIP.
[Android Q&A, Help & Troubleshooting] alainsr:
[MENTION=4546353]ShadowEO[/MENTION], I think this could work, in fact I'm confident it will. But I realized that my previous attempt messed with the bootloader and recovery. My computer still recognizes my device, but I can't boot to bootloader nor recovery! :( Is there any way I can try to flash TWRP again without fastboot access? I have access to adb when I plug the device in and get it charging, but I don't think I can execute elevated commands (su). This is worse than I ever tought...
[Android Q&A, Help & Troubleshooting] ShadowEO:
Uhh... Well.. you could try a download mode, but at that point you may be screwed. :( You may need to see if you can get a replacement. Fastboot is the only thing I could think of bit you say you can't get bootloader access. At this point, I'd say it is no longer a softbrick.
[Nexus 6P Q&A, Help & Troubleshooting] fleebailey33:
For work I have to use mobileiron, which detects everything from root to the unlocked bootloader. I am not sure if it simply detects the unlocked bootloader or detects because of the warning that comes up, I would guess its the latter.

So not only can't I root, I can't unlock my bootloader in the current state. At the very least I would like to enable wifi tether, and I would do that through TWRP but then I can't unlock my bootloader. So way to relock without wiping.

So I guess the question is for people who don't know about MobileIron is will we be able to unlock the bootloader without setting off any other options? or is there way to at least edit build.prop without root or unlocked bootloader?

I guess ideally if I could root without unlocking the bootloader then unroot that would solve my problems. Thoughts anyone?
[Nexus 6P Q&A, Help & Troubleshooting] vladashram:
Here is a thought, although it might fail. You could unlock your bootloader, boot TWRP without flashing(fastboot boot twrp-rgvrg.img), make your changes, then boot back into the bootloader and relock it.

Still can't say for sure it would work and it will virtually guarantee your userdata be wiped.
[Nexus 6P Q&A, Help & Troubleshooting] flex360:
Buy a second phone for work related purposes

I'd never spend so much on a phone just to let my company lock it down
[Nexus 6P Q&A, Help & Troubleshooting] Aridon:
You could always test out various configs and see what trips the software or not. You might be able to keep TWRP and root just turned off via supersu and everything work. Similar to android pay. You might not even be able to unlock the bootloader. Anything in between in possible.

Regardless it is pretty trivial to go back to stock and get everything locked back up again. So there is little risk in trying.

If it were me I'd try root and see if it worked. No? Ok, try to disable root with supersu. Will work or not. If not then make your host file edits for adaway and such and then completely remove root. See if that works.

You can also try to unlock the bootloader now as stock and see if it impacts the software. See exactly where it trips and prevents you from using it. Then work from there.

If nothing works, go back to 100% stock and lock the bootloader again. At least you gave it a go and had some fun for the evening. If I had to guess something in between will work and you can work around the limitations.
[Galaxy Note 10.1 Android Development] armanote:
This rom is like a theme and update for gnabo rom

The links and screen shots add sooner....please be patient

Change log..

Transparent weather widget

Transparent music widget (in work )

Full Tab S2 icons

Tring to add more features like transparent notificatin panel

.

.

..
[Galaxy Note 10.1 Android Development] armanote:
Reserved

Reserv
[Galaxy Note 10.1 Android Development] armanote:
Reserved

Res
[Galaxy Note 10.1 Android Development] furkey:
It's nice to see that Note 10.1 section is still alive. Will try asap! Keep up with the work!
[Honor 7 General] nukes_king:
Hello everyone

Can any one find a way to make PLK-UL00 suppout more 4g band?

I'm actuelle in France and i can't get 4g signal with PLK-UL00

My operater is free mobile

Thanks a lot:D
[Honor 7 General] KirinRaikage:
Where did you buy it ? And how long has it been since you have that issue ? I live in France as well, and I have 4G (with Free). But there is an issue with Free for the last 3 days so it may be Free-related and not H7-related.
[Honor 7 General] piskr:
According to all accessible information Free Mobile operates only on LTE 2.6GHz. And PLK-UL00 doesn't support 2.6GHz, it works in Europe only on 1.8GHz.

It seems that this phone supports only Bouygues LTE in France and even that partially.
[Honor 7 General] Nyssa1104:
The Honor7 from Three UK supports bands 1,3,7, 8,20 LTE.

Tested sim cards on O2, Only, SFR, Orange, Tmobile and of cause 3 In store
[Honor 7 General] samcro94:
The only model full 4G in France is PLK4L01
[Mi 3 Q&A, Help & Troubleshooting] SxScread:
Hi, due to multiple problems on Lollipop ROMs on MI3, I finally came back to the latest sMIUI ROM.

I know that the new Kernels can be applied to KitKat ROMs, but is there benefits for it? I mean, will it bring back the 5.x problems like HDR not working, etc?

And more technically, how can those Kernels are finally able to work on both 4.4 and 5.1 now, and not from the beginning?

Thank you in advance.
[Mi 3 Q&A, Help & Troubleshooting] $îMpŁÿ_¢ØmPłİÇåŤęĎ:
HDR is now working in custom Roms :p
[Mi 3 Q&A, Help & Troubleshooting] SxScread:
Ah, good news! But HDR isn't the reason I left Lollipop, I kept having network and touchscreen problems :

- Impossible to send or receive MMS (no matter what APN or setting I use)

- Impossible to access to some services or update applications data over 3G (couldn't download a file on Google Drive, couldn't see a video on YouTube, couldn'd refresh posts on 9gag...)

- And sometimes, the touchscreen was buggy, it didn't responded well, so I had to lock-unlock the phone a few times before it start working properly

So for now I'll stay on MIUI KitKat, but I would like to tweak it so it will be at its best
[Mi 3 Q&A, Help & Troubleshooting] 24likan:
No flashing custom kernel in smiui does not bring lollipop problems
[Mi 3 Q&A, Help & Troubleshooting] SxScread:
Thank you, I will search and flash one ASAP so
[Mi 3 Q&A, Help & Troubleshooting] 24likan:
Yeah. Welcome. Enjoy flashing
[Mi 3 Q&A, Help & Troubleshooting] fluster84:
Sorry to hijack the thread, but can someone recommend a good LP kernel that is worth flashing with the new MIUI7 and/or the Xiaomi.eu MIUI rom?
[Mi 3 Q&A, Help & Troubleshooting] 24likan:
First thing is you cannot use a lp kernel in kitkat rom such as miui and smiui. But you can use custom kernels like GOD'S KERNEL, MOSHI etc. Search the forum.
[Mi 3 Q&A, Help & Troubleshooting] narugan26:
try God's Kernel r4 it's blazing fast and battery life is ridiculous ?
[Mi 3 Q&A, Help & Troubleshooting] Me_Ashish_:
Did you remove roaming or whatever it is called in mobile networks (which is in general enabled by default)
[Mi 3 Q&A, Help & Troubleshooting] MM.626:
My power button is loose and I use zeurionx, I think it's compatible with miui and aosp. It has wake gestures dt2w and s2w.
[Mi 3 Q&A, Help & Troubleshooting] haysthecoder:
Not very

Not very
[Xperia Arc Q&A, Help & Troubleshooting] dwengs:
About Loader.sin Error

I did get Loader.sin Error a few times. But when I use previous Flashtool version, there was no loader.sin error.
[Xperia Arc Q&A, Help & Troubleshooting] miXXed404:
"In configuration section, it says Bootloader Unlock Allowed: No. As far as I learned from XDA forums, that means bootloader is locked again. Because it must be unlocked or unlock allowed: yes." It means you cannot unlock bootloader! Its not possible , your phone is locked , i mean you cant run fastboot mode , its locked , install stock firmware and thats all , you cant install any custom firmwares as Cyanogenmod or custom kernel anymore. If you can't understand it sorry because english is not my main language.
[XDA Assist] TheAlmightyBrick:
So today i tried to use a new ROM on my AT&T Samsung Galaxy S3. It bricked because instead of pressing "Reboot" me being an idiot I pressed "Install SU into sbin" or something. It wont turn on. I read up on jigs and was wondering if a jig will set it into download mode so I can fix it.
[XDA Assist] Calin:
Hi and thank you for using XDA Assist :)

Don't worry it's not bricked just make a clean flash of the ROM with all the usual wipes and this time just make sure to don't press flash SuperSU but reboot.

Good luck!
[Desire 816 Q&A, Help & Troubleshooting] re2fl:
When I restore a nandroid backup I have no Wi-Fi so I have been searching for a flashable radio zip, I unzipped the RUU.exe, and the OTA update but did not find a radio zip, cannot seem to find one anywhere, if anyone has one they'd like to share or a link to where I can download one, it would be greatly appreciated, thank you in advance.
[ONE Q&A, Help & Troubleshooting] Lidor167:
Hey, Currently using SlimKat ROM (4.4.4 Custom ROM).

Is there anyone with experience with this ROM while Running ART instead of DALVIK? does it work?

thanks :)
[G4 Q&A, Help & Troubleshooting] dominik-p:
Happy that my guide has helped you :)

As I said here:

http://xdaforums.com/g4/help/rooting-lg-h735-g4-beat-t3192491/page5

Everyone who is interested to inject root must edit the autoroot.sh from the inject.zip and use the correct files from SuperSU

More information about the files:

https://su.chainfire.eu

Maybe you have to use other files. Not the files from the inject.zip

Download the Update-SuperSU zip from http://download.chainfire.eu/supersu

Copy the files you need to the "su" folder of the extracted inject.zip

For information which files are needed read the "update-binary" file from the SuperSU zip.

(located here META-INF/com/google/android/update-binary)

Good luck everyone :good:
[G4 Q&A, Help & Troubleshooting] jen.magnolis:
Thanks again for the links! I'll try again soon, when I get time for it, and report the results here :)

By the way, here's the ls -lR of my system.
[G4 Q&A, Help & Troubleshooting] dominik-p:
Ok, no problem, take your time.

I've got also lot of other work to do...

I just read your system.txt (thanks)

According to these lines:

lrwxr-xr-x. 1 root 2000 13 Aug 24 02:05 app_process -> app_process32
-rwxr-xr-x. 1 root 2000 13588 Aug 24 02:05 app_process32

It seems that the firmware is 32 bit.

More info about your firmware is in /system/build.prop

So you have to take the right lines from update-binary and copy them and edit the autoroot.sh

Please don't ask me which lines. It's a bit difficult... (you have to understand the logic in update-binary)

Then copy the files from the right folder (arm?) to the "su" folder.

Sorry. I'm out now here for the next time. I have a H815 and happy with it.

I think you will find the solution. :good:
[G4 Q&A, Help & Troubleshooting] benji5688:
Custom Recoverys

Hi All

Are there any custom recovery's for the G4 beat/G4s

Thanks
[G4 Q&A, Help & Troubleshooting] jen.magnolis:
Thanks dominik-p for your help. Good luck with your other work, don't worry I won't distract you with asking questions ;) You already helped a lot.

benji5688, you can check for official firmware (.kdz file) on this link, pasting your IMEI instead of YOUR-IMEI in the link below.

http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI

I did not find any for mine there, but I did find it on

http://devtester.ro/projects/lg-firmwares/

Which brought me to this link where I could find mine:

http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz

but you should look for your specific model.
[G4 Q&A, Help & Troubleshooting] xsteacy:
LOL

I did the exact same thing as you, and really the EXACT, I also contacted dominik-p for the same problem you got with the bs. LOL

Was about to do the same thing you did here too ;) just told that to dominik-p lol.

You post is great, well detailled. Hope someone found something ;)

But got something different. my phone is the LGH731 LG G4 Vigor from Videotron in Canada.

If someone need files or system.img LINK

That's not the exact same thing as the post owner but i'm pretty sure the root method will be. (DON'T use this system.img to inject in you H735) it's from a H731 and they don't have the same partition size.
[G4 Q&A, Help & Troubleshooting] jen.magnolis:
Ha, that's funny, and you got the same problem of course (frozen logo boot).

We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.

First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back :)

Meanwhile, if you get any new results, let me know.

Cheers
[G4 Q&A, Help & Troubleshooting] xsteacy:
Yes i'm trying this today (the 32-64 bits thing)
[G4 Q&A, Help & Troubleshooting] benji5688:
Custom recovery

What does this file do though?

Is it a custom recovery or is it the stock rom?

Thanks Benji
[G4 Q&A, Help & Troubleshooting] jen.magnolis:
It's the stock ROM. It can be used for recovery, depending what your problem is. If you destroyed your ROM by trying to root, you can recover with this.

If you mess with something in your system partition (where the Android OS is installed), you'd need a copy of your individual system partition (like a "backup") to restore. This highly depends on your phone/version, so you have to do this backup yourself. You can follow the instructions with the dd parameters, linked to from the main thread.
[G4 Q&A, Help & Troubleshooting] benji5688:
Are there any custom recoverys

Hi

Are there any custom recovery available, I want to get Xposed.

Can anyone make one?

Thanks for all the help
[G4 Q&A, Help & Troubleshooting] xsteacy:
I far as I know to get Xposed you need to be rooted... Well there is no root method availaible, well you can try the methods that Jen explained here but I doubt they will work... if yes, you lucky **** :)
[G4 Q&A, Help & Troubleshooting] larsdennert:
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
[G4 Q&A, Help & Troubleshooting] xsteacy:
No the problem is really just changing the 64 bits command to make then use the 32 bits ones

I manage everything except this one

chcon --reference=operatingtable/bin/app_process32 operatingtable/bin/app_process64_original
[G4 Q&A, Help & Troubleshooting] jen.magnolis:
I agree with xsteacy, this will most likely not work, that's why we opened this discussion ;)

We just have to find the right files to use (instead of the 64 bit ones).

I will get back onto the subject by Wednesday when I have time.
[G4 Q&A, Help & Troubleshooting] jen.magnolis:
I solved it! My phone is rooted :D

I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.

Good times! :D
[G4 Q&A, Help & Troubleshooting] dreamnoob:
0.0 OH!?
[G4 Q&A, Help & Troubleshooting] jen.magnolis:
Ok I'm putting it out there for others to test as well.

Please report if it worked so I can take this into account before updating the main thread instructions.

In the attached .zip file there is a README with instructions.

Note: Thanks goes to [MENTION=4465149]konsolen[/MENTION] who shared instructions on how to open the COM port on the H735.

The script in konsolens post is essentially the upater-binary script of the SuperSU package, but with a few modifications.

That may have been necessary on konsolens phone, but it didn't work on mine. For me, using the original script worked.

However, the zip file has to be extracted manually with busybox before the updater-binary script is started. I am not

sure if busybox absolutely needs to be in the /sbin folder, but that's where I saw elsewhere that it belonged, so

I moved it over there in my script. I haven't tested this with busybox being elsewhere.

Thanks goes also to [MENTION=6895020]dominik-p[/MENTION] for sharing the link to excellent documentation and for his instructions on how

to make a backup (with dd) of your system, in case anything goes wrong.

UPDATE: I did all commands in root_lgh375.sh manually when I found it already worked, so please report if all is good with the script, but I think it should be, it only does what I did manually.
[G4 Q&A, Help & Troubleshooting] dominik-p:
Congratulations [MENTION=7058880]jen.magnolis[/MENTION] :D

Well done ;)
[G4 Q&A, Help & Troubleshooting] benji5688:
Do you have a custom recovery?

Do you have a custom recovery with your root? (I rooted with the King root app) but couldn't find a custom recovery.
[G4 Q&A, Help & Troubleshooting] jen.magnolis:
I guess with "custom recovery" you mean a zip file which can be used from within the recovery mode, and then roots your phone?

Do you also have the LG H735?

Because on mine I can't even go into recovery mode. That may be why you have not been able to find something like that.

You have to do it manually, as in the instructions (see README.txt in my .zip).

If you are after the .kdz file to use with the Flash Tool, there are also links in the README. But that won't root your phone, you can only use it to restore it to how it was before, in case something goes wrong with the root.

PS: if you rooted with kingroot you may want to use the flash tool to get rid of kingroot, it will remain on your phone forever otherwise
[G4 Q&A, Help & Troubleshooting] benji5688:
I also have the G4 beat, when you try to go into recovery mode all it says is factory reset or reboot. I want to install a zip for xposed. Can anyone make a custom recovery?
[G4 Q&A, Help & Troubleshooting] dreamnoob:
dosent really work for me.. after '#sh root_lgh735.sh' nothing really happens as in the command line didnt run
[G4 Q&A, Help & Troubleshooting] xsteacy:
Rooting method until Jen update her post!

1. First use the file that Jen posted... extract it and start "Init_Root.bat" on a phone that is in normal state (where you can make call etc.)

2. Put your phone into download mode with DIAG port unblocked(look at the first post in this thread to know how if you don't!)

3. Get the command line by pressing shift+right click on the extracted folder.

4. Write down Send_command.exe \\.\COMX (where the X is your port number!) usually 3 for these phone!

5. Write down each of these(It maybe have too much but it worked for me so...:

(6.) If you want to make sure everything is good... Just write down ls after the #, if it list you a lot of folder/files... your good to go!

mv /data/local/tmp/busybox /sbin/busybox

chmod 755 /sbin/busybox

ls -l /sbin/

mkdir /tmp

mkdir /tmp/supersu

/sbin/busybox unzip /data/local/tmp/supersu.zip -d /tmp/supersu

mv /data/local/tmp/supersu.zip /tmp/supersu/

sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip

Happy rooting! And don't forgot to say thanks to the person who wrote this post in the first place!!

*****And for those with the LG G4 Vigor(Canada one) LG-H781 it work also... I have this phone ;)
[G4 Q&A, Help & Troubleshooting] dreamnoob:
OMG it worked!! holymoly! ran rootchecker ✔and supersu is also installed! <3 omg thank you guys soo much! now i should be able to get bigger micro sd space and install non important apps there!!
[G4 Q&A, Help & Troubleshooting] jen.magnolis:
Yayyy I'm so happy it worked for you too, guys!

As I suspected it was the script I punched together (root_g4h736.sh) without testing it (I had warned about that btw ;) ). I just put all commands in the script that I had manually done to get it working. That's all commands that xteacy posted in the thread above (but the two lines with "-n -e" won't do anything if typed into the shell directly, that was meant to be a function ui_print. You don't need the #!bin/sh and OUTFD line either).

Thought it may also work putting all my lines in a script, but it obviously didn't. And then I wasn't in the mood to do the root all over again, besides, when the phone is already rooted, it may have been different. So we'll have to trial this on more people with a new script :)

I will post our results in a new thread tomorrow, so people can follow the instruction afresh without reading through all our posts here, haha :silly: I'll write the script again without the ui_print stuff, and just say to people that if it doesn't work with the script, they should punch it in manually.

Thanks for testing and reporting back!

It's very satisfying to win over the limitations imposed on us poor users with no rights on our own hardware, isn't it? CHAKKKKAAAA!
[G4 Q&A, Help & Troubleshooting] jen.magnolis:
By the way, I'll also post my experiences with cleaning out the memory tomorrow in another thread.

I highly recommend Link2SD, it's soooo worth the 2 bucks for the pro version! You don't need any other management app to clean stuff out.

You probably already know this, but just in case: "linking" stuff onto SD is much better than the classic Android move-apps, you can avoid lots of problems with that. You will also need a good SD card (fast r/w speeds), and format it with a second ext4 partition which you can use to move apps on. I'll post how to do that tomorrow.