Related
I am planing on buying the droid incredible soon but the only problem i see is root i came before different possibilities on how to root the device and now i see the test device is dead thanks to hurricane sandy i came across this solution to root is someone brave enough to try it?
Requirements
Usb debugging on
Intructions
Decompres the whole attached zip and run the root.bat inside it and also be advised the script will make reboot your phone
Explanation
This is how the one x users got perm root so since they achieved temp root by the local.prop hack(our temp root) why not try it since it is the same thing but modified to stick after reboot!!!
Ps I think the bootloader should show tampered as with temp root
Disclaimer as usual im not responsible for anything but i may help
Ps i named zip mygift because this would try to be my first gift for this forum
Extra Ps if someone could upload me the vold.fstab file in system/etc i can make flashable zip for you to swap sdcards meaning microsd mounted as /sdcard and the 8gb internals of this phone as /sdcard2
Edit: im uploading a second zip trying to get the perm root we need anyone wanting to help try please report back
the instructions are the same
Sdcard swap mod
Reserved if permanent root achieved to post the sdcard swap mod mentioned above
Edit: andybones sent me the required file so as i promised ill attach the flashable zip as soon as i finish editing it, ill attach it here
Edit: now attached for anyone lucky enough to have his/her bootloader unlocked
So... what do you need?
Only a tester all you have to do is enable usb debugging in settings download and extract the zip attached and run the root.bat file inside
Okay I'll try in the am in guessing there's a risk?
The same as on the temp root guide as far as i know i read the script many times and i dont see much risk it only modifys the data partition and pushes the superuser app to system\app and also system\xbin and if im not wrong they are the same on our temp root method so dont worry
Ps thanks for being my tester as i dont own the device if something goes wrong(i dont think so,very difficult) flash the ruu
Rgr thanks bud
---------- Post added at 07:13 AM ---------- Previous post was at 06:43 AM ----------
I tried running the script but it didnt work. it kept failing and saying permission denied
failed to copy busy box, superuser, su > permission denied
unable to chmod data/local/busybox, su, superuser.apk no such file or directory
failed on data/local/tmp permission denied
thats what im seeing everytime
Thanks for all im gonna keep trying
vold.stab
Okay so what files am i supposed to use now? Root try 2? Vold. zip?
Root try 2 please
restoring first backup...
please authorize the backup on your phone, and
press enter when backup restore has been completed
on my phone the screen says "a full restore of all data from a connected desktop computer has been requested do you want to allow this to happen? if you didnt request the restore yourself blah blah blah this will replace any data on your phone
please enter device encryption password
if restore data is encrypted please enter password"
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
i dont think i have a backup, or can you make backups with stock recovery?
it means everything is going according to the pan it is your decision to pres yes or no i think it would wipe the data partition(possibly not because htc dev does that part) and get us supercid , with supercid we can htcdev unlock again
Only continue if you want, all htc one x users did the same
I've already temprooted, and bootloader says tampered. I will try this too.
Sent from my ADR6410LVW using xda app-developers app
Ok now that you see that dont do anything as i think your data would be wiped im gonna investigate if you can make backups that way and remember you contacts and info are on your google account
Linch89 said:
restoring first backup...
please authorize the backup on your phone, and
press enter when backup restore has been completed
on my phone the screen says "a full restore of all data from a connected desktop computer has been requested do you want to allow this to happen? if you didnt request the restore yourself blah blah blah this will replace any data on your phone
please enter device encryption password
if restore data is encrypted please enter password"
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
i dont think i have a backup, or can you make backups with stock recovery?
Click to expand...
Click to collapse
You should only need a fake backup that's basically just the default background. I would recommend you make a real backup first though (adb backup -all).
Sent from my ADR6410LVW using xda app-developers app
You should do what captainrewind says hes correct
Linch89 you should make the backup and thencopy the files in a separate folder in case the new backup replaces the fake we are trying to get in
okay. in order to adb backup all i need sdk installed correct
i found this site
http://forum.xda-developers.com/showthread.php?t=1886460
i remember using this.
i cant really say much more
use at own risk
Manual Updating: How-To Preserve Root Access and Bootloader Unlock!
update... as of Nov 10 2014:
Official Lollipop for D855 and F400 has come out... following my instructions here you can still get bump'd - http://forum.xda-developers.com/showpost.php?p=56650179&postcount=59
So far, no anti-rollback in sight but I would still be careful of future updates.. and all other G3 devices models should be careful before taking an OTA (AT&T/Verizon... maybe).
Follow the steps above and you will ALWAYS have access to root/bump and flash anything you want.
This thread assumes you are already rooted, have TWRP installed and can read English.
If you have those 3 covered the rest is EASY as long as you read.
If you are unsure of any terms used in this post please search XDA/Google instead of asking in here.
Background
I'll get this out of the way right now... if you do not care about having access to Bump or root you can ignore all of this and continue to take LG's OTA updates. One could argue that taking OTA updates is required to maintain any level of safety/security... but that goes out the window once you start rooting and installing recovery/roms anyway. Regardless, I am not telling anyone not to update. But if you do update... do it manually. As of Oct 18 2014, every single G3 variant has root and bootloader unlock.. either out of the box(D851) or thanks to Bump. There is no need to ever take an OTA from here on out. The latest D855 and F400 OTA updates have blocked TowelRoot, IORoot and even Stump.. pretty sure only PurpleDrake works on them for now... I would expect PurpleDrake to be patched soon enough. And with official Lollipop updates coming root will only get harder. But.. as long as we install everything through TWRP manually we can update while keeping root/unlock/Bump.
Yes, we can downgrade using LG FlashTool but that could be blocked at any time with an OTA update to prevent rollback(Samsung does this).
Yes, it's possible to complete an OTA upgrade and maintain root but there is no way to know for sure if root will stick. And the OTA is upgrading the bootloader. Why gamble? This post is just a suggestion on how to stay updated without locking yourself out of anything... but it's not a rule. Just one of many options you can take. But if you do lose root or bootloader unlock after an OTA... don't go asking any devs when then next root tool is coming out or if there's a magical way to downgrade the bootloader. Overview
With all that said... now that we're all rooted and unlocked I decided to make a thread on how to:
1. Block OTA updates and remove OTA packages and that annoying notification. Easy!
2. Download updates manually.. no OTA zip needed. Easy!
3. Manually flash updates without losing root or Bump. Easy!
Most of us have access to the same files found in the latest OTA.. either with a .KDZ or .TOT(Sprint and AT&T refuse to release KDZ files..it seems they would prefer you to not be ale to fix the phone yourself). We can extract the individual partition files from a KDZ/TOT and easily flash them through TWRP. ATT/Sprint users will need leaked TOT files... or something like a pre-patched System.img/Boot.img/Modem.img from a user who has run a modified OTA update... yet managed to keep/regain root. More on that possibly in the future.
The main things we want out of a new OTA update:
A. Radio/Modem.img - although newer isn't always better
B. Kernel/Boot.img - this is often where root is blocked in new updates. But update manually and it no longer matters since we can root system through TWRP.
C. Rom/System.img - this is where most of the "fixes" in updates happen.. and what most people want from an OTA.
D. *Optional: Bootloader stack/Aboot.img,SBL1.img, DBI.img, LAF.img, RPM.img, TZ.img - this is where downgrading and Bump could be blocked. Avoid updating for now unless you are 110% sure you know what you're doing.How-To Block and Remove OTA Updates
If you are flashing custom roms in TWRP.. I'd expect OTA updates to already be removed. If you get an OTA update while running a custom flashable rom be sure to ask the dev why he can't make a proper custom rom that keeps you safe from OTA updates.
Block
Open LG Hidden Menu (3845#*851#) --> WLAN Test --> OTA Setting --> Disable
*Replace "851" with your devices model number, 850, 852, 855 etc.
This seems to only work on D851, D851 and D855 versions (possibly D857/8/9 and F400). AT&T, Verizon and Sprint users have reported the Hidden Menu method does not work. If you have one of those devices you can use a RootExplorer-type app to find the OTA related APK and rename the file to ____.apk.bak or use Titanium Backup to freeze it. If using Titanium Backup look for com.lge.lgfota.permission, OTA or System Update and freeze it. If looking for apk and odex file to rename.. search for OTA or FOTA or LGDMSClient.. etc
If you see an "Apps update" that just might be the "LG Apps" and not a firmware update. Updating LG apps is safe.. firmware is not (if you want to be able to maintain root/mods).
Remove OTA Update(and notification)
If an OTA notification is on your device you most likely already have the OTA file on your phone. If rooted, you can remove the OTA files and get rid of that annoying notification.
Updates are found in the /cache/ folder on your phone. Using a RootExplorer-type app(or ES File Explorer) browse to the root of your phone(NOT the root of your internal storage, /sdcard/, but the actual phone). If using ES File Explorer you may have to use the "show hidden files" option and grant the app root. You will see the update .zip file in cache if you did everything correctly. If no one has already uploaded the OTA zip.. copy the update to your sdcard and then upload for everyone else. Now delete the zip file from /cache/.
Deleting the file in /cache/ will get rid of the OTA but will not get rid of the notification. To get rid of notification:
1. Pull the notification shade down on your phone
2. Long press on the OTA notification until you see the App Info option pop up.
3. Click App Info and uncheck the Show Notifications box.
How-To Download Updates and Extract KDZ/TOT Files
1. Easiest way to obtain updates would be to look in this around XDA in your proper subforum for an update already posted by someone else. With Bump, many flashable rom zips will be popping up. Roms usually contain "system" and "boot"... which are two of the three things we generally want from an update. The third being the modem.. which is never included in a flashable rom and often not required to be updated. If you want the updated modem you will have to look around for the file or use the steps below to get it yourself.
2. If there is a new OTA update, no one has already posted the updated flashable files and you can't wait any longer... it is time to take matters into your own hands. Instead of giving in and taking the official OTA or begging others for help.. download the updated KDZ for your device yourself. And NO, we will NOT be not flashing the full KDZ.. we are just taking some files from it.
You can get your devices KDZ by visiting THIS LINK and entering in your MEID or IMEI.. it will give you a link to the latest available KDZ from LG. Sometimes KDZ files take a few days to show up after the OTA.. give it a little time. Do not beg in thread for KDZ files. Help yourself or wait for someone to post the files you were looking for.
It is encouraged to share not only KDZ and TOT files... but the extracted System/Boot/Modem images you extract from them as well. Only one person needs to download a KDZ per DeviceVariant/SoftwareVersion... that person can then share and everyone else just downloads from their link. You no longer have to be a "rom dev" of even know how to make a flashable zip to help share updates with others.
Anyway... to extract these partitions after downloading the KDZ/tot you can check out the following posts for scripts/tools to make things easy:
a. CLICK HERE [Tool][python] LG Compressed KDZ Extractor - by thecubed Script to extract partitions from KDZ.
b. CLICK HERE SystemMerger.py - by cybojenix Script to merge split system files from extracted KDZ.
c. CLICK HERE [TOOL]LG Bin Firmware Extractor - by xonar_ Script to extract TOT files and merge system.img's into one.
d. CLICK HERE [TOOL] KDZ and TOT Extractor - by bullghost Windows tool, adds all features of the scripts above with an easy to use UI.
invisiblek has updated xonar_'s LGBinExtractor to work with some more G3 devices - https://github.com/invisiblek/LGBinExtractor
If you have a question about an extraction tool be sure to read everything in the 4 threads. Post in the above threads if your question is still unanswered. Between the 5 extraction links above you can extract any G3 KDZ/TOT on Linux, OSX or Windows.
And remember, the main partitions we want from the TOT or KDZ: modem, boot and system.
Alternatively you can extract the KDZ directly on your phone -- click HERE.
Since more than a few people are having issues manually extracting... I will show an example that came from this thread and how to correct it:
KDZFileTools.py -f D85510L_00.kdz -x
[!] Error: Unsupported KDZ file format.
[ ] Expected: 0x28 0x5 0x0 0x0 0x34 0x31 0x25 0x80 ,
but received 0x28 0x5 0x0 0x0 0x24 0x38 0x22 0x25
Two things wrong here... first, the command is incorrect. when using the KDZFileTools.py "-x" is not used.. you want "-s 0" to extract the DZ.
Example:
Code:
python KDZFileTools.py -f D85510L_00.kdz -s 0
The second error is the "Expected.. but received" message. To fix this just open the .py script up in a proper text editor(notepad++ on windows for example).. find "x28x05x00x00x34x31x25x80" in the script...
replace it with "x28x05x00x00x24x38x22x25" (or whatever string is given after the "but received" output.. use logic) then save script.
rerun script. DZ will now extract into the "kdzextracted" folder. Once that finishes extracting you can use the Windows GUI tool to extract the .DZ file into individual partitions (and merge system). Or you can continue using the manual script methods.
To manually extract the DZ you're going to now use the DZFileTools.py script to split the DZ file (that's in the kdzextracted folder) into individual partitions.
Example:
Code:
python DZFileTools.py -f kdzextracted/D85510l_00.dz -x
that command will extract all your partitions into the dzextracted folder. Now drop the SystemMerger.py - by cybojenix file linked above into the dzextracted folder.. cd into the dzextracted folder and run that script to merge all the split system partitions into one system file.
Code:
python SystemMerger.py
All done.. you now have the boot, modem and full system.img to flash on your phone (along with every other partitions that comes with a kdz). :good:
3. Other methods for obtaining updated files would be grabbing the OTA update zip from the /cache folder and trying to pull files out of that.. or having an "in" and getting some leaked files or TOT. Sprint and AT&T users would benefit most from a leaked updated TOT.
Where-To Download KDZ Files
In this section I want to start a collection of all the latest KDZ files for all G3 devices.
You can help me out by either posting your KDZ link with FULL info about the KDZ/DEVICE..
Example of a helpful post:
derp said:
Hi, here is my model info and kdz url below...
LGD855
A6NEWH
D85510L_00
16GB
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW978806432109876543213/D85510L_00.kdz
Click to expand...
Click to collapse
OR you can PM/Private Message me your IMEI so I can look up all the models and latest KDZ's myself. This would help me the most but I understand the security concern. If security is an issue.. you could leave the last 3 digits off the end so I dont have your exact #. If you trust me.. please consider sending me your IMEI if you own one of the devices I need listed below...
KDZ Links Below
Team Codefire had to come through once again and supply TOT files to the USA carriers that provide no public KDZ (AT&T, Sprint, Verizon)
AS985 (USA Regional) - NEED IMEI
D850 (USA AT&T) - 10D TOT (AT&T has no public KDZ files. Feel free to complain to them.)
D850PR (Puerto Rico Claro) - NEED IMEI
D851 (USA T-Mobile) - 10M KDZ
D852 (Canada) - NEED IMEI for D852 Bell, D852 Rogers and D852G
D855 (Europe) - 10L Netherlands 16GB | 10L Germany 16GB NEED MORE IMEIS
D855AR (Argentina) - NEED IMEI
D855K (Australia) - NEED IMEI
D855P (Brazil / Mexico) - NEED IMEI
D855TR (Turkey) - NEED IMEI
D857 (China) - 10C KDZ NEED IMEI STILL
D858 (China / Hong Kong) - NEED IMEI D858 and D858HK
D859 (China) - NEED IMEI
F400 (Korea)- F400L 20E,
LS990 (USA Sprint) - ZV4 TOT (Sprint has no public KDZ files. Feel free to complain to them.)
US990 (USA US Cellular) - 10C KDZ
VS985 (USA Verizon) - 12B
Click to expand...
Click to collapse
How-To Manually Flash/Update Device w/ System.img, Boot.img and Modem.img
1. You downloaded a custom rom flashable zip a rom has made for the community. Roms contain "system" and "boot"
Flash these in TWRP and follow any instructions in the thread/post where you downloaded it. Rom questions belong in those specific rom threads.
You may have to wipe data/factory reset in TWRP, depending on rom.. or you may need to flash a gapps zip if using an aosp-type rom.. etc..
There's no need to worry about OTA's using this route. Proper custom roms will never include the bootloader stack or anything that could remove your bootloader unlock. And just about all custom roms come with a pre-rooted "system" so you don't have to worry about root either. Remember to make a backup in TWRP before flashing anything.
2. You obtained some boot.img,modem.img,system.img files... either extracting from TOT/KDZ yourself or downloaded files another XDA member has uploaded. This method is something you can do all by yourself... no help from a dev needed. To make this method just as easy as flashing a custom rom zip in method #1.. I have made 3 flashable zip files - [Flash2System.zip, Flash2Boot.zip and Flash2Modem.zip]
Download them to your phone using the link below then follow the directions that follow...
DOWNLOAD FLASH2 FILES FROM CODEFIRE HERE
A. Make a new folder on your internal sdcard called: flash2
B. Download and place Flash2System.zip, Flash2Boot.zip and Flash2Modem.zip on your phone. Internal/external sdcard.
C. Stick system.img, boot.img and modem.img into the /sdcard/flash2/ folder. Files must be named system.img, boot.img and modem.img
D. Create backup's in TWRP.
E. In TWRP, flash Flash2System.zip and/or Flash2Boot.zip and/or Flash2Modem.zip to install your updated images.
F. If you have flashed a stock system.img you will need root. After the flash completes press Reboot System and TWRP will ask if you want root. Go thru the process in TWRP then reboot. After booting you may have a notification to finalize root. Few more clicks and you're rooted... it's that easy. No more worrying if root is patched in the latest OTA update... or having to undo everything you changed in stock so that the OTA doesn't brick you.
Flash2*.zip didn't work? Make sure your system/boot/modem.img files are in the /sdcard/flash2/ folder. Internal sdcard!
How-To Properly Share KDZ/TOT and other Update Files
If you have a new KDZ or have already extracted the KDZ.. please share it with the rest of us in this thread! Please post the KDZ link along with the exact model, region software version and size. Example: D855 Germany 10L 16GB KDZ.
If you want to share your extracted system.img, boot.img and modem.img files please upload them somewhere and share the link. Please specify if you would like others to mirror your files or not (if hosting them on personal server).
Please label all shared files properly! Name them appropriately with boot, modem or system in the name.. as well as the FULL model and software version. Entering my IMEI into the KDZ generator from the last section I can see my device info such as: LGD851TN and D85110M_00. Exact models and software versions are important so other users know which files they need to flash and which to avoid. You should only flash files for your exact device variant. An example name based on my info above: LGD851TN_10M_00_Boot.img (this can be renamed later to boot.img once downloaded or placed on sdcard).
Click to expand...
Click to collapse
More G3 Flash2 Threads:
[FIX] Stuck in Custom Recovery [TWRP/CWM] (After trying OTA)
[EFS] LG G3 EFS Backup and Restore
XDA:DevDB Information
Flash2, Tool/Utility for the LG G3
Contributors
autoprime
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-18
Last Updated 2014-12-11
Reserved
Nice. On the LS990 (Sprint), it appears that the APK responsible for OTA is titled "com.lge.lgfota.permission" version 4.4.2-LS990ZV41403169216
If I'm looking at the wrong app, someone please correct me, so that other users don't freeze this app and think they're covered, but I froze it and rebooted with no problems.
I also had to run the command line "am start com.lge.hiddenmenu ....[etcetera]" to get into the OTA enable/disable screen.
Block and remove instructions won't show, "spoiler" text reads "blocked"
Sent from my LG-D850
I have Verizon and after i enter : am start com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons in to adb i get an error:
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
starting: intent {act=android.intent.acton.MAIN cat =[android.intent.category.LAUNCHER] cmp=com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons} does not exist.
cali4nia831 said:
I have Verizon and after i enter : am start com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons in to adb i get an error:
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
starting: intent {act=android.intent.acton.MAIN cat =[android.intent.category.LAUNCHER] cmp=com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons} does not exist.
Click to expand...
Click to collapse
did you install the hiddenmenu.apk as the link instructed?
then entered the following commands like the URL says:
Code:
adb shell
su
am start -a android.intent.action.MAIN -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
which should then give you the hidden menu where you can "WLAN Test --> OTA Setting --> OFF"
Yes I did install the apk as instructed. It does open up the hidden menu after i enter those commands and after that error message but there is no WLAN TEST in the hidden menu that i can see.
---------- Post added at 10:55 PM ---------- Previous post was at 10:42 PM ----------
autoprime said:
did you install the hiddenmenu.apk as the link instructed?
then entered the following commands like the URL says:
Code:
adb shell
su
am start -a android.intent.action.MAIN -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
which should then give you the hidden menu where you can "WLAN Test --> OTA Setting --> OFF"
Click to expand...
Click to collapse
Okay so i got it to the hidden menu to pop up as well as OTA enable/disable page even though it still gives me the same error message. I tap ENABLE and it says ENABLE but then i go back to the hidden menu and it still isn't listed...
EDIT:
Ended up just renaming the LGFOTA.apk file listed in the first reply above. So I should be good to go...
cali4nia831 said:
Yes I did install the apk as instructed. It does open up the hidden menu after i enter those commands and after that error message but there is no WLAN TEST in the hidden menu that i can see.
---------- Post added at 10:55 PM ---------- Previous post was at 10:42 PM ----------
Okay so i got it to the hidden menu to pop up as well as OTA enable/disable page even though it still gives me the same error message. I tap ENABLE and it says ENABLE but then i go back to the hidden menu and it still isn't listed...
Click to expand...
Click to collapse
Don't tap Enable.. Tap Disable... and that's it. OTA disabled... off.. all done.
Someone can provide me with img files? I dont have a PC, just using my phone PM if you can help me.
autoprime said:
word
XDA:DevDB Information
Flash2, Tool/Utility for the LG G3
Contributors
autoprime
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-18
Last Updated 2014-10-18
Click to expand...
Click to collapse
Don't stick threads.. stick the man
He knows too much
Thanks for all your work
Edit: Can someone sticks his threads ?
Sorry for my noobish post, but where can I find tool for extracting KDZ for LG G3? You just provide link for GitHub, not for .exe program. Thanks.
First of all, thanks for the guide! It will help a lot of users in preserving bump and root
I don't think that leaving boot/etc .img out will help. LG engineers aren't stupid. The can, for example, do it like this: after "m" update all our phones will reflash aboot/etc partitions to patched versions on 1 jan 2015. The partition's images will be hidden in some big system file, while the waiting daemon will be hidden in, for example, healthd. We will never discover it until it's too late. GG WP.
That said, I really doubt that they will do it that way, but this is still a possibility. I guess i'll flash AOSP/CM/OMNI/smthing rom ASAP.
pRo_lama said:
Sorry for my noobish post, but where can I find tool for extracting KDZ for LG G3? You just provide link for GitHub, not for .exe program. Thanks.
Click to expand...
Click to collapse
link a, b ,c , d in the O.P. mate.. He provided all you need.... =)
The Python scripts and Windows GUI App, don't work for my D855 kdz files.
Don't have linux currently setup to test the last one (needs to be compiled).
L10nH34Rt said:
The Python scripts and Windows GUI App, don't work for my D855 kdz files.
Don't have linux currently setup to test the last one (needs to be compiled).
Click to expand...
Click to collapse
I'm on windows 8 mate... use the phython first with the kdz, then you can use the one with GUI for the dz file....
The hidden menu setting ever resets? Not after reboot, factory reset etc?
teddy0209 said:
I'm on windows 8 mate... use the phython first with the kdz, then you can use the one with GUI for the dz file....
Click to expand...
Click to collapse
I get an unsupported KDZ format error, that's my problem.
L10nH34Rt said:
I get an unsupported KDZ format error, that's my problem.
Click to expand...
Click to collapse
Well, I just extracted mine.... d855, v10i..
Check the command...
teddy0209 said:
Well, I just extracted mine.... d855, v10i..
Check the command...
Click to expand...
Click to collapse
I tried to extract v10l and it failed.
i deleted system updates with tibu should i delete LGFOTA.apk? under system,etc security there are a file named otacerts.zip should i delete that one to.
Well, I "had" an HDX at 14.3.2.6. I had the hdxposed module and I renamed the otacerts.zip to otacerts.bak. When the downgrade method came out, I named the otacerts.bak to otacerts.zip and I removed and uninstalled the HDXposed module. Then I changed the build prop to match the guides, and tried to update. I keep on getting an update fail, despite multiple reboots. I have checked to make sure that the .bin is in the root of storage, but nothing is happening. Please help me.
I put a pause in the batch, and manually copied the files to the right location, and I believe what happened is I did the build.prop and one more thing, then I accidently rebooted and its a brick.
XxD34THxX said:
Well, I "had" an HDX at 14.3.2.6. I had the hdxposed module and I renamed the otacerts.zip to otacerts.bak. When the downgrade method came out, I named the otacerts.bak to otacerts.zip and I removed and uninstalled the HDXposed module. Then I changed the build prop to match the guides, and tried to update. I keep on getting an update fail, despite multiple reboots. I have checked to make sure that the .bin is in the root of storage, but nothing is happening. Please help me.
Click to expand...
Click to collapse
Please clarify what did you plan to achieve with this and with what you need help exactly?
Is your kindle still usable (rom booting, but freeze at some point and is unusable or rom booting correctly, only update is failing)?
What recovery are you using (stock, safestrap or TWRP 2.8.x.x) and can you access it?
Your firmware was stock + rooted or some custom rom?
Please link the "guides" you worked with and if possible mark the point in which guide recommend something, but your kindle refuse(d) to continue?
XxD34THxX said:
Well, I "had" an HDX at 14.3.2.6. I had the hdxposed module and I renamed the otacerts.zip to otacerts.bak. When the downgrade method came out, I named the otacerts.bak to otacerts.zip and I removed and uninstalled the HDXposed module. Then I changed the build prop to match the guides, and tried to update. I keep on getting an update fail, despite multiple reboots. I have checked to make sure that the .bin is in the root of storage, but nothing is happening. Please help me.
Click to expand...
Click to collapse
Not sure why you needed to mess with build prop when starting from 3.2.6. According to this guide (which I have successfully used several times) it's simply a matter of dropping the renamed image in root, rebooting and allowing the 'update' to be processed naturally. What am I missing?
You're following the wrong guide...Those instructions are only for x.3.2.4 and below.
See http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204.
Well.. If this is not the case..
Did you set the permissions on the build.prob? I forgot it last time and my kindle was bricked. And Warrenty was out of time. But I got a new With 4.5.2 -.-'
@Davey126 I used that guide and it says to edit build.prop
@EncryptedCurse Uhmm, chrome and firefox both don't like the rollback for my HDX... Also, do I run the bat on the kindle or on my PC? And what folder exactly...
@oOFrAnzOo Permissions were all r/w
@jeryll Only update is failing. Everything works fine. Firmware and everything is stock + towelroot and Xposed. No safestrap
you need to read carefully...
edit build.prop is only up to 3.2.4...
you way to do is the mentioned post from encryptedcurse...
before that, edit the build.prop back to what it was before...
you need to extract it first on pc, and copy the update 3.1.0bin to that folder, and run the .bat from there....
after that copy the 3.1.0 to kindle (mentioned in the how to)
if you can't get the rollback.zip, disable your antivirus for a minute and use internet explorer...
(if remeber right, there are two download buttons, the blue one was the right one...)
XxD34THxX said:
@Davey126 I used that guide and it says to edit build.prop
Click to expand...
Click to collapse
I am afraid not. You need to read more carefully. The first section (where it mentions modifying build.prop) is for versions up to 3.2.4. The section further down is for 3.2.5-3.2.6. Look for the bold red highlighted text delineating sections.
(yes, it could be more clear. Maybe blinking red. That said, volunteers post this information; I am grateful for their contributions even if it takes a couple readings to fully digest)
Now if I can start IE...
The HDX has to be in fastboot mode correct?
wait, The kindle DOES NOT need to be connected to the PC when running the batch right? Also, is the reboot for the HDX or PC?
XxD34THxX said:
wait, The kindle DOES NOT need to be connected to the PC when running the batch right? Also, is the reboot for the HDX or PC?
Click to expand...
Click to collapse
The batch file simply issues a bunch of adb commands on your behalf. So yeah, it needs to be connected. Reboot is for HDX. Make sure you understand what you are doing; you can easily 'damage' or permanently brick your device with a simple mistake.
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
XxD34THxX said:
The HDX has to be in fastboot mode correct?
Click to expand...
Click to collapse
No...where does it say that?
Davey126 said:
The batch file simply issues a bunch of adb commands on your behalf. So yeah, it needs to be connected. Reboot is for HDX. Make sure you understand what you are doing; you can easily 'damage' or permanently brick your device with a simple mistake.
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
No...where does it say that?
Click to expand...
Click to collapse
OK, so I installed ADB drivers... going to try this now. I'm still used to safestrap, which needed little work
Alright, I ran the batch, the .bin was in the same folder, Kindle was connected, ADB enabled in settings. I rebooted, moved .bin to the root of storage, and I get the same "Last Update Failed" Error again...
XxD34THxX said:
OK, so I installed ADB drivers... going to try this now. I'm still used to safestrap, which needed little work
Alright, I ran the batch, the .bin was in the same folder, Kindle was connected, ADB enabled in settings. I rebooted, moved .bin to the root of storage, and I get the same "Last Update Failed" Error again...
Click to expand...
Click to collapse
Did you mess with the otaupdate apk's from amazon to previously blick ota updates? That is the error you get when you try to update & it can't launch the updater app. The same error you get when disabling the OTA's & then trying to search for updates.
You may need to rename the OTA apk's ***AFTER DISABLING WIFI*** & then trying to start the process again. I think it will require a reboot to bring those services on line again, as well.
Ermmm.. The OTAcerts is a .zip... Is it supposed to be a .apk?
XxD34THxX said:
Ermmm.. The OTAcerts is a .zip... Is it supposed to be a .apk?
Click to expand...
Click to collapse
otacerts.zip is correct.
Davey126 said:
otacerts.zip is correct.
Click to expand...
Click to collapse
well, it's a .zip and located in /System/etc/Security. HDXposed is off, and I did several reboots to make sure. Then I did the batch...
XxD34THxX said:
well, it's a .zip and located in /System/etc/Security. HDXposed is off, and I did several reboots to make sure. Then I did the batch...
Click to expand...
Click to collapse
Not sure what to say. Seems something is still amiss and needs to be tracked down. Suggest you go through previous posts and validate everything. I am sure you have already done this but something must be off. Frustrating for sure...we've all been through it at some point.
Perhaps someone else has a better idea.
XxD34THxX said:
well, it's a .zip and located in /System/etc/Security. HDXposed is off, and I did several reboots to make sure. Then I did the batch...
Click to expand...
Click to collapse
Try a factory reset from within the settings.
Code:
* USE IT AT YOUR OWN RESPONSIBILITY because rewrite recovery partition.
*
* This batch file works "kindle fire hdx 8.9" ONLY
* This is not tested.
*
* If do not want rollback, Close this window.
*
* IF you want to rollback,
* Put "update-kindle-14.3.1.0_user_310079820.bin" in SAME folder,
* Push Enter key 5 times
*
* If it is requested from super su, please allow superuser.
*
Press any key to continue . . .
Press any key to continue . . .
Press any key to continue . . .
Press any key to continue . . .
Press any key to continue . . .
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>7z.exe e update-kindle-14.3.1.0_user_310079820.bin "boot.img" "recovery/recovery-from-boot.p" "system/etc/recovery-resource.dat" "system/etc/security/otacerts.zip"
7-Zip 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: update-kindle-14.3.1.0_user_310079820.bin
file boot.img
already exists. Overwrite with
boot.img?
(Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit? a
Extracting boot.img
Extracting recovery\recovery-from-boot.p
Extracting system\etc\recovery-resource.dat
Extracting system\etc\security\otacerts.zip
Everything is Ok
Files: 4
Size: 8875856
Compressed: 833418977
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb shell mkdir /sdcard/recovery
mkdir failed for /sdcard/recovery, Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push build.prop /sdcard/recovery/build.prop
failed to copy 'build.prop' to '/sdcard/recovery/build.prop': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push otacerts.zip /sdcard/recovery/otacerts.zip
failed to copy 'otacerts.zip' to '/sdcard/recovery/otacerts.zip': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push boot.img /sdcard/recovery/boot.img
failed to copy 'boot.img' to '/sdcard/recovery/boot.img': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push recovery-from-boot.p /sdcard/recovery/recovery-from-boot.p
failed to copy 'recovery-from-boot.p' to '/sdcard/recovery/recovery-from-boot.p': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push recovery-resource.dat /sdcard/recovery/recovery-resource.dat
failed to copy 'recovery-resource.dat' to '/sdcard/recovery/recovery-resource.dat': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push install.sh /sdcard/recovery/install.sh
failed to copy 'install.sh' to '/sdcard/recovery/install.sh': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb shell sh -v /sdcard/recovery/install.sh
sh: /sdcard/recovery/install.sh: Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>pause
Press any key to continue . . .
That's the log for the batch... I added a pause at the end and a check for this. a crap ton of errors... Oh yes, I did a factory reset...
Hi,
I am Using LAVA A97 device recently launched. I need to root this mobile to apply some tweaks. I tried various methods like flashing the zip from the SD card and sideload. The error I got always is "Signature Verification Failed". I tried finding custom recoveries and even tried porting custom recoveries but all stopped at the boot image.
Please help me to root this device or port me a custom recovery. I will provide you the files you needed.
Have you tried enabling OEM bootloader setting in developer options?
vshlkmr said:
Have you tried enabling OEM bootloader setting in developer options?
Click to expand...
Click to collapse
Ya I allowed oem unlocking in developer options. But when i boot to fastboot mode and enter command
Code:
fastboot oem unlock
it struck on the boot screen. I have waited for an hour but nothing happened. I just removed battery and rebooted my mobile.
I can give you the stock rom can you make it pre rooted
Please tell me the procedure to add su files in marshmallow system.img and flash it
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
karljsamuel said:
Please tell me the procedure to add su files in marshmallow system.img and flash it
Click to expand...
Click to collapse
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
vshlkmr said:
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
Click to expand...
Click to collapse
I tried the above mentioned steps in my Ubuntu 16.04 with Android Kitchen and Superr's Kitchen. With Android kitchen, I unpacked the system.img and the kitchen made the boot image and made the ro.secure=0. Then I added the necessory files from @Chainfire SuperSU.zip as per the update-binary script mentioned and repacked system.img with Superr's Kitchen. When I flashed modified system.img and boot.img with flash tool.
The superSU app said that su binaries are not installed and it cant install them also it asked me to reroot the mobile phone.
I also tried with Dirtycow exploit also but not worked.
Mobile is running Marshmallow API 23
Can you make me a custom recovery. I followed the steps mentioned in this forum to port a custom recovery but it struck in the boot logo.
The Stock Firmware file Now I have in my mobile can be downloded from Google Drive.
Boot.img Recovery.img and build.prop file is uploaded as Zip to Google Drive
How are you flashing the files back to phone? What software you using? And maybe superuser cannot find the binaries bcoz maybe lava a97 picks it's binaries from someplace else (like maybe /system/bin)
vshlkmr said:
How are you flashing the files back to phone? What software you using? And maybe superuser cannot find the binaries bcoz maybe lava a97 picks it's binaries from someplace else (like maybe /system/bin)
Click to expand...
Click to collapse
Flashed with SPD upgrade tool.
The su binaries and apk files are placed as mentioned by chainfire in the update-binary provided by him for flashing the zip via custom recovery.
It told me to run su --install but the adb shell does not work after customising the rom
karljsamuel said:
Flashed with SPD upgrade tool.
The su binaries and apk files are placed as mentioned by chainfire in the update-binary provided by him for flashing the zip via custom recovery.
It told me to run su --install but the adb shell does not work after customising the rom
Click to expand...
Click to collapse
Is USB debugging enabled?? Also switch the phone to cd rom and install the drivers
While installing the modified system.img it give me error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Even there is no such file in the stock rom. only a file named sh0 was present
I reflashed the rom and adb shell is working properly without the /system/bin/sh file
How to root lava a97
Hey bro I read your thread and also I myself tried many ways to root my lava a97
Did u got any method to root it??
Please tell
karljsamuel said:
Ya I allowed oem unlocking in developer options. But when i boot to fastboot mode and enter command
Code:
fastboot oem unlock
it struck on the boot screen. I have waited for an hour but nothing happened. I just removed battery and rebooted my mobile.
I can give you the stock rom can you make it pre rooted
Click to expand...
Click to collapse
Lava A97 is CortexA7 device
use fastboot tools to flash TWRP and then flash SuperSU.zip
I'm gonna port TWRP for Lava A97 soon
And will test it.
pm me and I'll give you TWRP after success in testing
OK?
---------- Post added at 09:40 AM ---------- Previous post was at 09:35 AM ----------
vshlkmr said:
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
Click to expand...
Click to collapse
Thanks alot bro???
TWRP port test failed
Hey bro i have rooted my lava a97 IPS
Recovery- cyanogen recovery ported by me
And flash super su
Can anyone Provide me the recovery & Su files Please?
---------- Post added at 04:42 AM ---------- Previous post was at 04:40 AM ----------
Mrutunjaya said:
Hey bro i have rooted my lava a97 IPS
Recovery- cyanogen recovery ported by me
And flash super su
Click to expand...
Click to collapse
I Also Want 2 Root My Device Please Can U Help Me?
I recently bought this new chinese phone ( out from 3 months, android 7.0 ) but after many hours i still was not able to root this, tried all 1click junk and nothing worked, tried PC apps.. followed many guides, nothing worked.
I would like at least to install TWRP, but of course, device is not supported, and i dont know where to get proper IMG file for my phone.
any help would be appreciated.. thanks
Edit: Tried Mtk tools, since its a mt6580, it does detect phone but there are errors,
TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64
Uknown rom structure, backup not possible
innersphere1 said:
I recently bought this new chinese phone ( out from 3 months, android 7.0 ) but after many hours i still was not able to root this, tried all 1click junk and nothing worked, tried PC apps.. followed many guides, nothing worked.
I would like at least to install TWRP, but of course, device is not supported, and i dont know where to get proper IMG file for my phone.
any help would be appreciated.. thanks
Edit: Tried Mtk tools, since its a mt6580, it does detect phone but there are errors,
TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64
Uknown rom structure, backup not possible
Click to expand...
Click to collapse
no way to root this??
Hi, I also just aquired the allcall rio.
Can you help me out with a few things,
1. does the back come off in order to reach the battery?
2. on a normal phone pressing the middle button normally gains you access into the app menu, for some reason i can only access the home screen with the apps being accessed by sliding the home screen to multi home screens, is this normal?
3. have you rooted your phone and if so can you leadme to where you done this?
I like the phone, just wondering whether what iv stated are normal features or a fault with mine
Thanks in advance for any help / info
Cheers
Rooted / ish
innersphere1 said:
no way to root this??
Click to expand...
Click to collapse
Hey,
I have not found a root method but iv found a way to access all sysytem files and folders.
Go to app store and download ROOT BROWSER by JRummy Apps.
Open the app once installed and it will ask you to download files to make it work, it downloads quickly from inside the app.
When its finished you can then access the phones root files as tho your phone was rooted.
Its better than nothing for now and im sure there would be a way to insert the nesscerry files for rooting into the correct folders.
Hope it works for you
ronyon78 said:
Hey,
I have not found a root method but iv found a way to access all sysytem files and folders.
Go to app store and download ROOT BROWSER by JRummy Apps.
Open the app once installed and it will ask you to download files to make it work, it downloads quickly from inside the app.
When its finished you can then access the phones root files as tho your phone was rooted.
Its better than nothing for now and im sure there would be a way to insert the nesscerry files for rooting into the correct folders.
Hope it works for you
Click to expand...
Click to collapse
So can you modify files in /system with ROOT BROWSER?
---------- Post added at 07:51 AM ---------- Previous post was at 07:26 AM ----------
innersphere1 said:
no way to root this??
Click to expand...
Click to collapse
SP flash to flash a custom TWRP recovery .
I have ported one recovery image from TWRP 3.0.0-0 for Tecno W4 using carliv image kitchen. And it works like charm.
I would put the link up If I could, but right now I still need to make a few more posts to gain the privilege .
innersphere1 said:
no way to root this??
Click to expand...
Click to collapse
Hi again, I've found the better way to get root using Magisk, available here in XDA.
first download the 0808 firmware from allcall's official website and flash it with SP flash.
wireless upgrade to 20170819, unlike 0728 and 0808, this version has remove all bloatware and malware
take boot.img from the firmware folder and put it to phone storage
install Magisk Manager v5.3, hit install, patch the boot image.
copy the patched boot.img to PC and SP flash it. (no need to unlock bootloader)
done!
everything for allcall rio
ALLCALL RIO- SOFTWARE+TWRP+PHILZ+SUPER SU+FLASH TOOL+SN WRITE TOOL needrom download success:good:
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
AllCall-RIOWCDMA-1GB+16GB-7.0-20171207 by radu13
ciroradu said:
ALLCALL RIO- SOFTWARE+TWRP+PHILZ+SUPER SU+FLASH TOOL+SN WRITE TOOL needrom download success:good:
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
AllCall-RIOWCDMA-1GB+16GB-7.0-20171207 by radu13
Click to expand...
Click to collapse
Can you help me rooting my allcall rio I just can't tryied every root apk and pc softwares