Develop Bugs

[Q] Kindle Fire Stuck in Boot Loop

I am stuck in the boot loop with standard rom installed.
What I think I did was I edited the png files in the update.zip file. (Used paint)
then i installed the edited rom on my fire with TWRP.
I cleared the cache(s)
Then I rebooted.
When the fire started up i showed the Kindle Fire Logo. (no TWRP or FIREFIREFIRE Triangle)
AND IT STUCK there.
I used the KFU to check it and it says:
ABD:Offline
Boot Status: 4002
Fastboot status: offline
I dont know how to fix this
Please help
Thanks.......

First you need to get the adb working. Based on your post, the KFU doest recognize your KF.
I recommend to configure your PC to use Android composite driver to communicate to KF., then use KFU to do next steps such as installing FFF or recovery tool or ROM.
Sent from my Amazon Kindle Fire using Tapatalk

Try this: http://forum.xda-developers.com/showthread.php?t=1428428
It helped me unbrick my KF when I was stuck in a bootloop this weekend. Hope it helps.
sent from my CommandCenter using xda premium

Thanks But Still Not working
ADB doesnt see my kindle still,
And the program you sent didnt do a thing.
Every option keeps telling me device not found, or just waiting for device.
Can I use push to re copy the photos i edited?

wayoung said:
ADB doesnt see my kindle still,
And the program you sent didnt do a thing.
Every option keeps telling me device not found, or just waiting for device.
Can I use push to re copy the photos i edited?
Click to expand...
Click to collapse
You need to install drivers as ADB Composite, or else you'll probably be stuck there forever. The device not found error is due to a lack of working drivers.

http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
and check the adb_usb.ini file in your .android folder in your personal folder
it has to be existent and has to include 0x1949 (i use to add 0x18d1 in a separate line also)
without this folder/file/entries adb will never work !
if they are missing just create this folder and copy the file from c:\kfu\drivers\kindle

Kindle Fire boot loop problem
I still have a boot loop issue with my kindle fire which I just received some days ago (right, I had only 1 day to use it until first the web browser started closing when calling a page, then after repoot, the boot process does not finish, still seeing the kindle fire logo). draining the battery did also not solve the issue.
I installed the android sdk, the usb drivers, configured them and the kindle fire is recognized as device.
Afterwards I installed the Kindle Fire Utility 0.9.3, and tried it, with no success. Here the results:
Activity: kindle fire started (boot logo visible) - plugged it into the pc - started kfu
-------------------------------------------------------------
KFU Screen:
***********************************************
* Kindle Fire Utility 0.9.3 *
***********************************************
1 Bootmode Menu
2 BurritoRoot (Temporary)
3 Install Permanent Root with Superuser
4 Obtain Stock update.zip
5 Install latest TWRP Recovery
6 Install FireFireFire
7 Extras
0 Recheck Device Status
ADB Status: Online
ADB Rooted: No
Boot Status: 0x4000
Please make a selection or hit ENTER to exit
------------------------------------------------------------------------
Now I selected option 1 and tried every boot mode, with similar messages:
Activity: select option 1 (bootmode)
-----------------------------------------------------------------------
KFU screen:
***********************************************
* Kindle Fire Utility 0.9.3 *
***********************************************
1 Normal (4000)
2 Fastboot (4002)
3 Recovery (5001)
0 Recheck ADB/Fastboot Mode
ADB Status: Online
ADB Rooted: No
Boot Status: 0x4000
Please make a selection or hit ENTER to return:
----------------------------------------------------------------------
Activity: typing 2 (fastboot)
----------------------------------------------------------------------
KFU screen
***********************************************
* Activating Fastboot (4002) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC
1054 KB/s (1164225 bytes in 1.078s)
[1] Segmentation fault pm install -r /d...
Activating BurritoRoot...
[1] Segmentation fault am start -W -a a...
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: not found
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
The kindle has been told to reboot in Fastboot Mode.
-------------------------------------------------------------------------
Activity: restarting kfu (though it does not return to selection)
-----------------------------------------------------------------------
KFU screen:
***********************************************
* Kindle Fire Utility 0.9.3 *
***********************************************
1 Bootmode Menu
2 BurritoRoot (Temporary)
3 Install Permanent Root with Superuser
4 Obtain Stock update.zip
5 Install latest TWRP Recovery
6 Install FireFireFire
7 Extras
0 Recheck Device Status
ADB Status: Online
ADB Rooted: No
Boot Status: 0x4000
Please make a selection or hit ENTER to exit:
-------------------------------------------------------------------------
--> boot status is still 4000, i.e. no change to fastboot even though the message (which was somehow weird) told this.
Activity: select option 3 (install permanent root)
------------------------------------------------------------------
KFU screen:
***********************************************
* Installing Permanent Root *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC
1455 KB/s (1164225 bytes in 0.781s)
[1] Segmentation fault pm install -r /d...
Activating BurritoRoot...
[1] Segmentation fault am start -W -a a...
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: not found
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
mount: Operation not permitted
mount: Operation not permitted
/data/local/tmp/BurritoRoot3.bin: not found
***********************************************
* Root Installed *
***********************************************
Permanent root has been installed.
With great power, comes great responsibility.
Please be careful with how you use root.
It is HIGHLY recommended you have TWRP installed before using root (check your
device's screen for installation instructions).
***********************************************
* Thanks to Jcase *
***********************************************
Please consider donating to jcase by purchasing any of his apps on the market.
...
Or search for "Donate to JCase/TeamAndIR" on the android market.
--------------------------------------------------------------------------
--> after the last action, during the script running, the kindle fire does automatically deactivate and activate the driver on the pc (while the kindle still displays the kindle fire logo).
Does anybody have an idea how I can get this thing up and running again?

if the kf is'nt booting up normally kfu may have problems
i assume you don't have fff & twrp installed - right ?
you can try to install it with option 5
if it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
or install manually
tell about the progress

Kindle Fire Stuck in Boot Loop
right, fff and twrp are not installed. I tried option 5, which prompts the following result:
----------------------------------------------------------------
Make sure to follow instructions given to you
recovery.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC
1774 KB/s (1164225 bytes in 0.640s)
[1] Segmentation fault pm install -r /d...
Activating BurritoRoot...
[1] Segmentation fault am start -W -a a...
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: not found
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
----------------------------------------------------------------------
After power-off by holding the power button for sth. about 20 sec. and power on
nothing happens, kfu is still waiting for the device.
how can I install manually?

it's a good practice to move kfu to c:\ and rename it to "kfu" so that it is c:\kfu
- copy recovery.img from c:\kfu\recovery to c:\kfu\tools (check it is ~10mb)
- open a (elevated) command prompt and cd to c:\kfu\tools
- issue "fastboot -i 0x1949 boot recovery.img"
- in case it says <waiting for device> do as in my last post

Kindle Fire Stuck in Boot Loop
I also tried this, but still after power-off and power-on the <waiting for device> does not disappear.
Any other ideas?

what it telling the device manager under android phone ?
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
just reviewed your post - correct me if i'm wrong
- your on stock os 6.2.2
- not rooted
- no fff & twrp
- stuck on "kindle fire" static or animated ?

Kindle Fire Stuck in Boot Loop
The device manager tells me :
Android Composite ADB Interface
I cannot tell the fastboot interface though I am not able to start with fastboot.
Concerning your questions for verification:
- Android OS version: I am not sure which version I have, I didn't check the day I received the device, and the second day it did not boot correct.
- not rooted
- no fff & twrp
- static boot logo, stuck with

could you please try to issue the following commands from command prompt in c:\kfu tools:
"adb devices"
and
"adb shell"
please paste the results
just to verify my guess ...

Kindle Fire Stuck in Boot Loop
sure, the results are:
---------------------------
C:\kfu\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
7864002600000001 device
C:\kfu\tools>
--------------------------------
and
-------------------------------------
C:\kfu\tools>adb shell
$
--------------------------------------

hey cool - thought the shell is messed up - it's not - you can get to fastboot - great
would suggest to follow this thread starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
and your allready downloaded twrp is recovery.img not twrp-blaze-2.0.0RC0.img
simply adapt the corresponding command in the above thread
is you want stock rom i would suggest to use a prerooted stock rom (i prefer the unsecure version):
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20

Just wondering
Did my changing the stock logo images (png) inside the zip file have anything to do with why the Kindle Fire gets stuck at the logo?
Is there a way with ADB to push the correct images to replace the edited ones?
This seems logical to me as thats what I did and now it is hung on the logo.
Please I'm desperate because Amazon wont even help me cause im canadian
They said they would replace it no problem until I gave my address, and then it was Ohhhh Im msoooo sorry (my butt)
Thanks to all who have responded to the cries of a desperate man.

Update
I have found out that the kindle is mounted read only.
my device now shows
need to know how to change mount to r/w
can i do this with adb?

Kindle Fire Stuck in Boot Loop
hey b63, there is some progress, thank you!
now I have the screen on my kindle where i can select various things, like "advanced settings", "reboot", etc.
how do I install the rom you mention and do I need it to be able to boot without getting stuck again?

wayoung said:
I have found out that the kindle is mounted read only.
my device now shows
need to know how to change mount to r/w
can i do this with adb?
Click to expand...
Click to collapse
yes you can:
"adb remount"
there are also some other commands - try this one first
---------- Post added at 10:49 AM ---------- Previous post was at 10:42 AM ----------
manni4711 said:
hey b63, there is some progress, thank you!
now I have the screen on my kindle where i can select various things, like "advanced settings", "reboot", etc.
how do I install the rom you mention and do I need it to be able to boot without getting stuck again?
Click to expand...
Click to collapse
you should be in twrp now - is this correct ?
it's quite blue - landscape - 8 buttons
if yes resume with point 8 of the description
and yes - i think you have to flash a new rom because your old one seems to be messed up according to your description

LG Optimus Chic (E720) Rooting, Custom Recovery and ROM

How to install custom ROM
For LG Optimus Chic (E720)
Please note that I do not assume any responsibility in case of brick or malfunction of your device! Do it at your own risk!
Step 1: Rooting your device
Root your device using an app like Z4Root to permanently give root access to the Optimus.
• Go to http://forum.xda-developers.com/showthread.php?t=833953 and download the .apk
• Allow unknown sources to install apps on your devices (done by going to Settings - Applications)
• Install Z4Root
• Once it’s install, open the app from the Launcher and chose Permanent Root.
• Once Z4Root has done, your phone will reboot and you should have the SuperUser app installed
• To check that you really have root access you can install Terminal Emulator form the Play Store as we’ll need it after. https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=fr
• After you’ve install it, open a terminal session and you should see a «$». Just type ‘’su’’ and a window will open prompting you to allow super user. Chose «Allow». You will notice that the «$» had changed for a «#» this meaning that you have rooted your Android device !
Step 2: Install a custom recovery
In order to have a custom ROM, we will need a recovery to flash the .zip to the phone
• Download the recovery image and the flash_image by going to http://forum.xda-developers.com/showthread.php?t=1046135
• Once both files are downloaded, unzip them on the root of your SD card.
• After that, form the Terminal Emulator or an ADB Shell type the following commands in order to install the custom recovery.
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 0755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (notice this file install-recovery.sh may not be on your device if it gives an error or file not found move on)
flash_image recovery /sdcard/recovery-alessi-gnm.img
sync
• Power off your phone and boot in recovery mode by holding the Vol+ , Vol- and Power until you see the recovery on the screen.
• The message «E: bad boot» is normal. It will show up for everyone.
• You now have a custom recovery installed. It’s now time for the ROM itself!
Step 3: Installing the ROM
To make sure if anything go wrong, please do a nandbackup by going to Backup/Restore on the recovery before proceeding.
• First of all you got to find the right ROM for you. I choose a nighty version of CM7 because it’s light, fast and easy to find not like a CM9 ROM. You can download it form http://get.cm/?device=e720
• Because this ROM don’t have Gapps (Goolgle Apps) in it, we will download it to have the Play Store working on our device. http://goo.im/gapps/gapps-gb-20110828-signed.zip
• Once all of the files are copied on the root of the SD card (Make sure you haven’t unzip them!) boot into recovery mode and perform a wipe of your device.
• After, flash the ROM on the device and after the GApps.
• When everything is done, you can proceed in the process of rebooting.
• Take note that the first boot after you have flashed a ROM may take WAY longer than usual.
• Voilà! You now have your phone running CM7! Make sure to have fun!

Thanks emidesja
I followed your guide and it worked great. I would offer the following links for those not familiar with setting up ADP. It sure beats using a terminal emulator on the phone.
What is ADP - addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Android Debug Bridge (commands) - developer.android.com/tools/help/adb.html
I think I only used the commands ADB devices, then ADB shell before being able to enter your code. Also, after entering su I needed to click allow superuser on the phone. I can also add that when booting to recovery I needed to push quite firmly between volume up and down, so that the whole button is pressed and not toggled. In step 3 the wipe you mentioned offers many options. I choose to wipe only to wipe the cache partition and the Dalvik Cache.
Thanks again.

[ROOT][CWM][UNLOCK BL] Everything from the scratch for extreme beginners.

This guide is for extreme noobies who are new to the android platform.
[IF YOU ARE VISITING THIS PAGE USING MOBILE THEN PLEASE VISIT IT USING YOUR PC]
Before you proceed make sure you have
* A windows pc [This tuorial is for windows 7 and newer version of windows with x86/32bit system]
* An internet connection [ To download files over 400mb ]
* Patience
You need to download these files
* adt-bundle-windows
* Java
* recovery.img [Given in attachment]
* UPDATE-SuperSU-v2.45.zip [Given in attachment]
After you have downloaded the file follow the procedure.
* First of all install Java (the setup will download some files then it will be installed)
* Now after installing java you have make it run in windows environment. To do so, go to properties of Mycomputer.
* From the left panel click on advanced system settings.
* The system properties window will popup. Now from the advanced tab click on Environment Variables button.
* The Environment variable windows will popup. From system variables scroll down and click on Path.
* Now click Edit button.
* Edit System variable window will popup.In the Variable value Add ";C:\Program Files\Java\jre7\bin;" without quotes
[Asuming that Java is installed in C:\ Drive on a 32bit system][WARNING: Do not erase previous value, just add the above value at the end]
* Now click on ok to close Edit System variable window,ok to close Environment variable windows and apply then ok in system properties window.
------------------------ Now Java will run in windows environment ---------------------------------
* Now Extract the adt-bundle-windows-x86-20140702.zip file in c:\ drive
* Now rename the extracted folder to adt-bundle-windows.
* Go to properties of Mycomputer.
* From the left panel click on advanced system settings.
* The system properties window will popup. Now from the advanced tab click on Environment Variables button.
* The Environment variable windows will popup. From system variables scroll down and click on Path.
* Now click Edit button.
* Edit System variable window will popup.In the Variable value Add "C:\adt-bundle-windows\sdk\tools;C:\adt-bundle-windows\sdk\platform-tools" without quotes
[WARNING: Do not erase previous value, just add the above value at the end]
* Now click on ok to close Edit System variable window,ok to close Environment variable windows and apply then ok in system properties window.
-------- Now adb,fastboot etc will run in windows environment -----------------------------------------
To test adb is running or not, do the following
* Open command prompt and type adb and press Enter button
* Or open RUN application and from there type adb and press Enter button
* If working your command window should look like the below screenshot this when you scroll to top
To test Java is running or not, do the following
* Open command prompt and type java and press Enter button
* Or open RUN application and from there type Java and press Enter button
* If working your command window should look like the below screenshot this when you scroll to top
Now you have to update the Google USB driver [If not up-to-date], do the followings
* Go to the drive where you extracted the ZIP file [C:\adt-bundle-windows]
* Open the folder adt-bundle-windows
* From there you will find 2 Folders and SDK Manager.exe
* Run or open SDK Manager.exe [It will take some seconds to start, if not then Java may not be installed properly]
* [Make sure you are connected to internet, to update the files before opening SDK Manager]
* Now in SDK Manager Uncheck all checked pacakages, From Extras Tick only the google usb driver.
[If update is available the status will show Update available, if not close SDK Manager]
* Now click the Install Packages button [Check the progressbar at the bottom]
* After updating Close SDK Manager.
CONGRATULATIONS Now Every setup is complete.
-> Turn off your phone
-> Connect your phone to computer using your phones USB cable
(Your PC will install your phones driver)
-> After the installation is complete unplug USB cable.
UNLOCKING THE BOOTLOADER of your phone, do the following
* Turn off your phone
* Press volumeup + power button at a time for few seconds
* Now select Fastboot mode using volume down button [volume up to navigate between options]
* Conect your phone to pc using usb
* Open Command prompt in your pc
* Now type the following command in command prompt to Unlock bootloader
fastboot oem unlock
* and press Enter button
* Now check your phone it will ask to unlock bootloader, press volume down button to unlock.
* After unlocking type the following command in command prompt
fastboot format userdata
* and press Enter button
* To reboot your device type the following command in command prompt
fastboot reboot
* and press Enter button to reboot your phone
* unplug usb cable from phone
CONGRATS now you have unlocked your phones boot loader
INSTALLING CWM recovery on your phone
* copy the downloaded recover.img to C:\ drive
* Now run command prompt and type
cd\
* Now press Enter
* Turn off your phone
* Press volumeup + power button at a time for few seconds
* Now select Fastboot mode using volume down button [volume up to navigate between options]
* Conect your phone to pc using usb
* Open Command prompt in your pc
* Now type the following command in command prompt to install the CWM recovery
fastboot flash recovery recovery.img
* and press Enter button
CONGRATS now you have installed CWM recovery
* To reboot your device type the following command in command prompt
fastboot reboot
* and press Enter button to reboot your phone
* unplug usb cable from phone
ROOTING your phone
* copy the downloaded file UPDATE-SuperSU-v2.45.zip to sdcard
* Reboot your phone into recovery by pressing volumeup + power button at a time for few seconds
* Now select Recovery mode using volume down button [volume up to navigate between options]
* in CWM recovery, select install zip [Volume up and volume down to navigate and power button to select a option]
* now select choose zip from /external_sd
* now select UPDATE-SuperSU-v2.45.zip
* CWM recovery will ask you to install zip yes or no, choose yes to install
* now go back, select reboot system now
[ if CWM recovery says Root access possibly lost. fix ? then select no]
CONGRATS your phone is now rooted
// If you are confused in a step you can ask me before doing
// If i have missed any step, tell me
// If you want to know about the downloaded files you can ask
/******************************************************
You now may have lost your phones warranty.
Don't worry you can gain it again
******************************************************/
I AM NOT RESPONSIBLE FOR ANY.............................................
Ohhh THIS WAS SO BORRINNGGG.
Hit thanks if you appreciate my hard work (TYPING)

Hi, can i unlock my verizon sgs3 i535 boot loader running on android 4.4.2 thanks
Sent from my GT-I9300 using XDA Free mobile app

@Buntyagrwl, you could have used 'Minimal ADB and Fastboot' instead of using the complete package

ya
GokulNC said:
@Buntyagrwl, you could have used 'Minimal ADB and Fastboot' instead of using the complete package
Click to expand...
Click to collapse
Because the SDK provides Google driver. That's why I used the complete package.

Please find in your phones relevant forum. Thanks

Hey Buntyagrwl,
Iam confused with this phone of mine it has a frimware of i9300 but when i go in odin mode it shows i535
Sent from my GT-I9300 using XDA Free mobile app

Hey man I know I'm a noob lol but about to try this out and wanted to make sure of couples things.
1. Does this work for moto x 2nd gen?
2. Do you know how to factory default setting if I mess up?
3. Is this out dated or still work?
Thanks appreciate everything.

Ekim5050 said:
Hey man I know I'm a noob lol but about to try this out and wanted to make sure of couples things.
1. Does this work for moto x 2nd gen?
2. Do you know how to factory default setting if I mess up?
3. Is this out dated or still work?
Thanks appreciate everything.
Click to expand...
Click to collapse
No, this is for Android One devices only.
For your device, check here: Moto X

Thanks

Before unlocking the bootloader, when I connected the phone in switched off condition, it did not install anything. Also, while trying fast boot, it said waiting for device and nothing happened on the phone, can you help?

Can't do IMEI/NVRAM backup MTK, can't root

Hey, guys.. I can't get through following issues. Phone's firmware is full vanilla since the very beginning - only updated from Jelly Bean/ICS to 4.4.2 with OTA.
I want to install TWRP Recovery and then try some custom firmwares. I started with making a backup of IMEI/NVRAM by MTK Droid R&T just to be safe.
I can't, IMEI/NVRAM button is greyed out. Log:
Code:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
I've looked for solutions. They suggest e.g. searching for MTK app from different source. It doesn't help.
Setting up a root is also a trouble. I tried to use the simpliest, well known method within the reach based on Batch script.
Log:
Code:
[*] Waiting for device...(Connect your LGOG via USB in Charge Only Mode)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
Beginning Root Process
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
Press any key to continue . . .
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
Device is properly connected to adb.
Code:
(...)\ZV9-ZVB-Universal-Root>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
LGE9751acf27d9 device
I'm aware that those problems might be trivial to fix. In that case, sorry for wasting your time. Still, thank you greatly for help. I can provide all needed info.
<< I can't post screenshots :/ - newbie user.

Glaeqen said:
Hey, guys.. I can't get through following issues. Phone's firmware is full vanilla since the very beginning - only updated from Jelly Bean/ICS to 4.4.2 with OTA.
I want to install TWRP Recovery and then try some custom firmwares. I started with making a backup of IMEI/NVRAM by MTK Droid R&T just to be safe.
I can't, IMEI/NVRAM button is greyed out. Log:
Code:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
I've looked for solutions. They suggest e.g. searching for MTK app from different source. It doesn't help.
Setting up a root is also a trouble. I tried to use the simpliest, well known method within the reach based on Batch script.
Log:
Code:
[*] Waiting for device...(Connect your LGOG via USB in Charge Only Mode)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
Beginning Root Process
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
Press any key to continue . . .
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
Device is properly connected to adb.
Code:
(...)\ZV9-ZVB-Universal-Root>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
LGE9751acf27d9 device
I'm aware that those problems might be trivial to fix. In that case, sorry for wasting your time. Still, thank you greatly for help. I can provide all needed info.
<< I can't post screenshots :/ - newbie user.
Click to expand...
Click to collapse
How I root my device:
1. Download the towelroot apk http://towelroot.en.uptodown.com/android
2. Go to Settings > Security > Unknown Sources (enable/allow it)
3. Select the towelroot on the notification dropdown and install
4. Launch towelroot and root your device
5. Download Root Checker on Playstore to double check if you've successfully rooted your device

@erkasmoter
App returns message: "This phone isn't currently supported". :/ Thx, tho. I really want to get TWRP working..

adb sideload cannot read .....

Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
I have installed the latest [TOOL]Minimal ADB and Fastboot [1-6-17] in my Win 10 64bit PC, The PC recognizes me device, I can install the TWRP (.28) by fastboot and works great later flash again the stock recovery (recovery_OBT8N.img) and try to install the oficial OTA with sideload, it say "cannot read", I try:
* Re-installing the ADB drivers from others.
* With the original file name, and with the name modified "update.zip".
* Reboot my PC and device.
* Used the Ccleaner.
* With Adm CMD
* Leaving and entering the address where are the drivers and the file, with the CMD
* Typing: adb kill-server. adb root. adb sideload update.zip
* typing the file name: "update.zip" - "update" - "update.zip.zip"
* Putting the drivers in another direction
* Try differents files: ("OB10.zip" and "OOS4.zip"
* Use generic adb and nexus adb
* The lasted Stock recovery (recovery_OBT8N.img)
I know I can install OOS4 with twrp, I know because I have it, but I wanted to remove the DM-verity message and I followed this guide: [FIX] Device-Mapper-Verity fix for Oxygen OS Nougat Rom ( 4.0 and Open Beta's) And that's how I knew I can not use the sideload....
If anyone knows that I could try more, thank you very much, thank you.

ERNZT said:
Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
Click to expand...
Click to collapse
More info would be a pleasure ur on twrp? Boot into it type adb push Filename /sdcard/ it should push the file to /sdcard/ so you can manually flash it.

ERNZT said:
Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
I have installed the latest [TOOL]Minimal ADB and Fastboot [1-6-17] in my Win 10 64bit PC, The PC recognizes me device, I can install the TWRP (.28) by fastboot and works great later flash again the stock recovery (recovery_OBT8N.img) and try to install the oficial OTA with sideload, it say "cannot read", I try:
* Re-installing the ADB drivers from others.
* With the original file name, and with the name modified "update.zip".
* Reboot my PC and device.
* Used the Ccleaner.
* With Adm CMD
* Leaving and entering the address where are the drivers and the file, with the CMD
* Typing: adb kill-server. adb root. adb sideload update.zip
* typing the file name: "update.zip" - "update" - "update.zip.zip"
* Putting the drivers in another direction
* Try differents files: ("OB10.zip" and "OOS4.zip"
* Use generic adb and nexus adb
* The lasted Stock recovery (recovery_OBT8N.img)
I know I can install OOS4 with twrp, I know because I have it, but I wanted to remove the DM-verity message and I followed this guide: [FIX] Device-Mapper-Verity fix for Oxygen OS Nougat Rom ( 4.0 and Open Beta's) And that's how I knew I can not use the sideload....
If anyone knows that I could try more, thank you very much, thank you.
Click to expand...
Click to collapse
Most of the times the problem is really on the desktop configuration, ie usb drivers, adb version, usb port power, user profile permissions, etc. Note that you need a newer adb version to do stuff such as sideload. From the top of my head, I think you need 1.0.32 or newer. I know it seems overkill, but until google decides to distribute the platform tools in a separate minimal bundle, the best option is to install the android SDK. You can choose then to selectively install only the platform tools that include adb.
Sent from my ONEPLUS A3000 using Tapatalk

https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47 is definitely the best fix i found, if it doesn't work reboot your PC and do it again it worked for me.
Hope it can helps