[Q] Root Issue - G Pad 8.3 Q&A, Help & Troubleshooting

Hello I'm trying to root my gpad v500 and during the root.bat steps I get this error,
error: more than one device and emulator
- waiting for device -
error: protocol fault <status read>
This happens after the step warning about invalidating the warranty
I'm following this root method
http://forum.xda-developers.com/showthread.php?t=2553192
Code:
**************************************************
Easy root for LG G Pad 8.3
Modified By Dalingrin
Originally By IOMonster (thecubed on XDA)
See [url]http://tinyw.in/mXhw[/url] for details
**************************************************
Original root idea from [url]http://optimusforums.com/threads/how-to-root-the-lg-g2-f[/url]
320.8846/
Enable Developer Settings on the G Pad:
--Go to Settings->About tablet->Software information
--Tap on Build number until Developer Settings are unlocked
In Developer Settings:
--Enable USB debugging
Plug in the G Pad via USB to a PC.
Press any key to continue . . .
Looking for device...
error: protocol fault (status read)
Pushing g_security...
error: more than one device and emulator
*******************************************************
Now, please unplug usb, go to developer options and
disable USB debugging and re-enable it.
Once you've done that, re-plug your usb...
*******************************************************
Press any key to continue . . .
Waiting for device...
error: protocol fault (status read)
Now it's time to install su and superuser.
Please note! This will trip LG's rootchecker!
This means your phone will show ROOTED in the settings menu,
and in the LG Download mode.
If you do not want to possibly invalidate your warranty
press CTRL-C to stop this script.
You will have a rooted ADB, but no apps on the phone will be able
to access root functions.
Press any key to continue . . .
Mounting system RW and pushing SU, then remounting system RO again
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Installing superuser
error: more than one device and emulator
- waiting for device -
error: protocol fault (status read)
- waiting for device -
error: protocol fault (status read)
- waiting for device -
error: protocol fault (status read)
- waiting for device -
error: protocol fault (status read)
- waiting for device -
error: protocol fault (status read)
- waiting for device -
error: protocol fault (status read)
- waiting for device -
Ignore this thread please, I managed to fix the issue myself by rebooting both, PC and Tablet.

Related

Advanced Ace Hack Kit fails downgrade pls help me

Hello everybody, I am new here and I hope that you can help me with this issue.
My device
HTC Desire HD
Android-Version 2.3.5
HTC-Sense-Version 3.0
Software-Number 3.12.405.1
If you need some other information, please ask me.
I want to root my device but have too less knowledge to solve the upcomming issues.
How I tried
I firstly read the effen manual several times. (I really read it completely)
I activated USB-Debugging and turned charge only to default (so that I wont be asked anymore)
Than I run the aahk-12062012 on a Ubuntu-32 Live-CD.
My problem
The problems appear when the kit tries to downgrade.
It seems that the RUU-download isnt available on the Internet anymore. And my hboot file (PD98IMG\PD98IMG.zip) cant be found.
I tried several versions of PD98IMG.zip files containing several hboot.nb0 files but It never worked.
Here is the wohle content of the Terminal I got during my latest try.
I hope you can tell me what to do.
(I am sorry but I had to censore the links)
Ace Advanced Hack Kit [Linux/OSX/Windows] attn1 2011/2012
___________________________
MAIN MENU | |
| Only ONE Menu Step to: |
1 - Hack Ace <----------------------------+ * S-OFF |
| * SIM Unlock |
2 - DONATE (Encouraged, but optional) | * SuperCID |
link | * Root |
link | * Busybox |
| |
**********************************************************************
o - Options Menu (Return to Stock, Flash radios, etc)
**********************************************************************
t - Toggle Flash Method - current method is: hbootPD98IMG
*********************************************************************
q - Quit
Input Selection and press ENTER : 1
This version of Android cannot use the hack kit at this time.
You can downgrade if you like, then rerun the hack step.
WARNING: THIS WILL WIPE DATA
Would you like to DOWNGRADE? y/n y
Download this RUU? (y/n) y
--2013-04-02 15:06:31-- tau.shadowchild.nl/files/PD98IMG-GB2.zip
Resolving tau.shadowchild.nl (tau.shadowchild.nl)... 176.9.40.154
Connecting to tau.shadowchild.nl (tau.shadowchild.nl)|176.9.40.154|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-04-02 15:06:31 ERROR 404: Not Found.
Flash this RUU? (y/n) y
This version of Android cannot use the hack kit at this time.
You can downgrade if you like, then rerun the hack step.
WARNING: THIS WILL WIPE DATA
Would you like to DOWNGRADE? y/n y
Woah dude[tte] - bogus md5sum! Bad mojo.... skipping flash.
Check it out - renamed the file to PD98IMG/PD98IMG-GB2.zip-20130402:150635
You can re-download the file and keep going....
Download this RUU? (y/n) n
pushing rom to sdcard - this takes time, please be patient.
cannot stat 'PD98IMG/PD98IMG-GB2.zip': No such file or directory
Setting up to temproot....
519 KB/s (21215 bytes in 0.039s)
2230 KB/s (572752 bytes in 0.250s)
470 KB/s (19240 bytes in 0.039s)
going for temproot using zergRush....
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219c4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd26019 0xafd39ef7
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
setting mainver lower for downgrade...
--set_version set. VERSION will be changed to: 1.31.405.6
Misc partition is "/dev/block/mmcblk0p17"
Patching and backing up misc partition...
Creating goldcard....
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
Donations can be made to the Electronic Frontier Foundation:
eff.org/
or to B. Kerler:
psas.revskills.de/
0+1 records in
0+1 records out
384 bytes transferred in 0.001 secs (384000 bytes/sec)
starting downgrade...
** The phone will now reboot into HBOOT.
** It will then check the file just sent.
** If everything is okay, the phone will
** prompt you to continue by pressing
** VOLUME UP. It will reboot, flashing twice.
**** PUSH POWER WHEN THIS STEP COMPLETES ****
If downgrade is successful, you may set up the phone and try to hack it again.
Once the downgrade is successful, press a key to return to the menu......
Otherwise, cut and paste the output to the screen into a text file for evaluation.... then press a key.
pushing rom to sdcard - this takes time, please be patient.
error: device not found
Setting up to temproot....
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Starting stock recovery the first time to init....
Steps:
1. When you see the ugly red triangle, push/hold vol-UP and then push power to start stock recovery.
2. When you get to the blue stock recovery menu, choose reboot and push power.
/data/local/tmp/tacoroot: not found
Starting stock recovery for the last time....
Steps:
1. When you see the ugly red triangle, push/hold vol-UP
and then push power to start stock recovery.
2. When you get to the blue stock recovery menu, choose
reboot and push power.
/data/local/tmp/tacoroot: not found
allowing time for the rom to settle.....
Creating goldcard....
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
Donations can be made to the Electronic Frontier Foundation:
eff.org/
or to B. Kerler:
psas.revskills.de/
/dev/block/mmcblk1: cannot open for write: Permission denied
setting mainver lower for downgrade...
--set_version set. VERSION will be changed to: 1.31.405.6
Misc partition is "/dev/block/mmcblk0p17"
Patching and backing up misc partition...
Error opening input file.
rm failed for /data/local.prop, No such file or directory
starting downgrade...
** The phone will now reboot into HBOOT.
** It will then check the file just sent.
** If everything is okay, the phone will
** prompt you to continue by pressing
** VOLUME UP. It will reboot, flashing twice.
**** PUSH POWER WHEN THIS STEP COMPLETES ****
If downgrade is successful, you may set up the phone and try to hack it again.
Once the downgrade is successful, press a key to return to the menu......
Otherwise, cut and paste the output to the screen into a text file for evaluation.... then press a key.
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
************* PROBLEM PROBLEM PROBLEM ************
** SD card is either damaged or not mounted.
** Are you sure Charge Only mode is DEFAULT
** and not just switched on? READ THE EFFEN MANUAL
************* PROBLEM PROBLEM PROBLEM ************
**************** PRESS ENTER ****************
error: device not found
************* Downgrade failed *************
** Either:
** GoldCtixiard/SDCard failed
** USB connections are not working 100%
************* Downgrade failed *************
**************** PRESS ENTER ****************
Click to expand...
Click to collapse
AAHK is retired. Server hosting the files is gone.
bananagranola said:
AAHK is retired. Server hosting the files is gone.
Click to expand...
Click to collapse
I don't know what I could use else.
Unlock bootloader.

[Q] TWRP v2.1.2 custom rom install failed. no backup

I've searched around for a couple hours and couldn't figure out how to fix my situation.
I've tried installing the rom: OmniMetal-4.4.2-20140523-maguro
but it failed with:
E:Error in /tmp/sideload/package.zip
(Status 7)
* Verifying filesystems...
* Verifying partition sizes...
Error flashing zip '/sdcard/0/OmniMetal-4.4.2-20140523-maguro.zip'
I don't have a backup of the original rom on the device.
I've tried using ADB to push the original rom but I get:
error: device not found
Also in windows Device Manager the phone shows up as $ro.product.model which may be why ADB doesn't recognize it.
TWRP 2.3+ has sideload but that doesn't help me as I have 2.1.2 installed
Any help from you guys in getting my phone fixed would be greatly appreciated!
Bryan
EDIT:
I've finally been able to connect to the phone with ADB and have fixed it.

[TWRP][UNOFFICIAL][3.2.3-0] For nx569j/h

WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
How to install:
1. Download twrp
2. Install fastboot tools from google's sdk on your PC
3. Enter fastboot mode on device
4. Unlock your bootloader
5. Run "fastboot flash recovery twrp-3.2.3-0-nx569j.img" via command line
6. Reboot
Download:
https://mega.nz/#!bwsTHD4J!1TaMAuJWL4LNhlsBgW0x9L3aYVd7T7itBzMTFPLz1oo
What is different from the previous version I mean the RedWolf one I saw that you have posted once (Sorry for my bad english)
jsbeyond said:
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
How to install:
1. Download twrp
2. Install fastboot tools from google's sdk on your PC
3. Enter fastboot mode on device
4. Unlock your bootloader
5. Run "fastboot flash recovery twrp-3.2.3-0-nx569j.img" via command line
6. Reboot
Download:
https://mega.nz/#!bwsTHD4J!1TaMAuJWL4LNhlsBgW0x9L3aYVd7T7itBzMTFPLz1oo
Click to expand...
Click to collapse
Wow,
Tks 4 your honesty, this a UNOFFICIAL version and I trst more in you than others... > https://twrp.me/Devices/Nubia/
Can I update a "[OFFICIAL][RECOVERY] TWRP 3.2.1-0 for Nubia Z17mini" version of this TWRP?
RicardoAB said:
Wow,
Tks 4 your honesty, this a UNOFFICIAL version and I trst more in you than others... > https://twrp.me/Devices/Nubia/
Can I update a "[OFFICIAL][RECOVERY] TWRP 3.2.1-0 for Nubia Z17mini" version of this TWRP?
Click to expand...
Click to collapse
Ofcourse???
E:[MTP] error opening '/data/media/0/nubiaShopDown' -- error: No such file or directory
E:[MTP] error opening '/data/media/0/data' -- error: No such file or directory
E:[MTP] error opening '/data/media/0/TitaniumBackup' -- error: No such file or directory
E:[MTP] error opening '/data/media/0/panoramas' -- error: No such file or directory
E:[MTP] error opening '/data/media/0/com.facebook.katana' -- error: No such file or directory
E:[MTP] error opening '/data/media/0/beam' -- error: No such file or directory
E:[MTP] error opening '/data/media/0/pptv' -- error: No such file or directory
E:[MTP] error opening '/data/media/0/.com.taobao.dp' -- error: No such file or directory
E:[MTP] error opening '/data/media/0/MusicCut' -- error: No such file or directory
E:[MTP] error opening '/data/media/0/neoRecorderTemp' -- error: No such file or directory
E:[MTP] error opening '/data/media/0/neoRecorder' -- error: No such file or directory
mount: mounting /dev/block/mmcblk0p46 on /data failed: Device or resource busy
run_program: child exited with status 255
Is it necessary to install as sytem app?
Is it necessary? It eats up memory and battery if installed as system app. Also it is very tough to force stop!
jsbeyond said:
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
How to install:
1. Download twrp
2. Install fastboot tools from google's sdk on your PC
3. Enter fastboot mode on device
4. Unlock your bootloader
5. Run "fastboot flash recovery twrp-3.2.3-0-nx569j.img" via command line
6. Reboot
Download:
https://mega.nz/#!bwsTHD4J!1TaMAuJWL4LNhlsBgW0x9L3aYVd7T7itBzMTFPLz1oo
Click to expand...
Click to collapse
there is a problem with date and time of twrp-3.2.3. date goes to 2018-06-13.
I took backup and noticed that backup was taken in 2018
Any way to correct this?
I don´t have this bug but you don´t need this unofficial version
official is available since years
https://dl.twrp.me/nx569j/
.... dont know why the f... teamwin webadmin don´t do it on the main directory site. report this missing link 6313653 times
dewois said:
I don´t have this bug but you don´t need this unofficial version
official is available since years
https://dl.twrp.me/nx569j/
.... dont know why the f... teamwin webadmin don´t do it on the main directory site. report this missing link 6313653 times
Click to expand...
Click to collapse
Nope. I installed that. still time is set to 2:00hrs and date back to June 2018

newflasher not working

I downloaded firmware (G8441_Service Exchange Unit_1309-6969_47.1.A.2.281_R2B) using flashtool 64 and extracted the newflasher files to the folder. When I run newflasher.exe I get the following error:
Code:
Device path: \\?\usb#vid_0fce&pid_b00b#6&df2ee03&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus devices
Device Instance Id: USB\VID_0FCE&PID_B00B\6&DF2EE03&0&6
Optional step! Type 'y' and press ENTER if you want dump trim area, or type 'n' and press ENTER to skip.
Do in mind this doesn't dump drm key since sake authentifiction is need for that!
n
ERROR: GetOverLapped_out_Result: failed with error code 1 as follows:
Incorrect function.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
End. You can disconnect your device when you close newflasher.exe
Press any key to continue . . .

[SOLVED] Unable to flash a rom or restore after motherboard replacement (t700)

Hello,
My tablet had a battery drain problem so I changed the motherboard and tried to install lineageos 14.1 again.
After replacing the motherboard, I turned on the tablet to activate usb debugging. The rom installed wasn't "complete", it looked like an interface for professionals to copy data from the old motherboard to the new... Maybe one of you knows what I'm talking about.
I flashed twrp and booted in recovery mode. Then I tried to wipe data but got errors (for instance "cache partition not found" or "hidden partition not found" or something like this. I'm sorry I didn't copy the error message :/
I tried to reboot anyway but I'm now unable to boot on the rom nor on recovery mode. I have a message : "POWER RESET or UNKNOWN UPLOAD MODE" and "ATconsole=ram loglevel=4 sec_debug. Level=1 cluster_power=1 androidboot. debug_level=0x494d sec_"
Only download mode is working.
So I'm trying to install the stock rom, downloaded from sammobile. On linux via Heimdall I got this error when flashing system.img and hidden.img :
Code:
Uploading SYSTEM
0%
1%
ERROR: Failed to unpack received packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...
On windows via Odin, I cannot flash the tar.md5 file either, it fails.
Someone could help ?
Or at least explain why I got these errors in twrp?
Thank you very much !!!!!!
Update :
I found a way to boot in recovery mode (twrp 3.3.1-klimtwifi) : unplug the battery, replug it and home + vol up + power.
So here is the error when I try to wipe data : "Failed to mound '/hidden' (Invalid argument)"
I installed the old motherboard and I'm doing a full backup on my sd card on TWRP, including EFS partition.
On the new motherboard I can't restore the backup because in twrp > restore > sd card : "No partitions selected to restore".
So here's where I am now :
I can boot into twrp but have an error message when trying to wipe data.
I have a full backup of the old motherboard with lineageos installed and working but i'm not able to restore it
Any help appreciated
And also, when I try to sideload the lineageos zip file I get this :
Code:
Starting ADB sideload feature ...
Installing zip file '/sideload/package.zip'
Target: samsung/klimtwifixx/klimtwifi:6.0.1/MMB29K/T700XXU1CRF1:user/release-keys
detected filesystem ext4 for /dev/block/platform/dw_mmc.0/by-name/SYSTEM
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Ok, I fixed the restore issue by moving the backup files to : sd_external/twrp/BACKUP/[myserialnumber]
So now I can restore all partition except System, System Image and Hidden.
Error : extractTarFork() process ended with ERROR: 255
I still can't sideload the custom rom. But the error message "Failed to mound '/hidden' (Invalid argument)" disapeared
I fixed/unbricked the tablet by using SamFirm to download a 3 files stock firmware.
I installed it with Odin and it worked like a charm.
Then I could install a custom rom

Categories

Resources