Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.
hushpup131 said:
Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.
Click to expand...
Click to collapse
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053
jamcar said:
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053
Click to expand...
Click to collapse
I am not able to get into the APX mode. The basis of my belief is there is no audible signal (USB to PC) and there is no new window opening inviting me to explore a new drive.
I have disconnected the battery both short term as well as over night, no response from the power only and power plus volume – buttons.
The charge light has turned green; no response from the buttons.
Measuring the voltage at the charger tip read 12+ volts. I am using a new USB to PC cable. Out of curiosity I unplugged the battery connector and re-connected to see the charge light switch off and on while the charger was connected. As a novice here, I suspect that test eliminated the charging circuit as a fault.
I'm in UBUNTU
loaded and extracted gtab.nvflash.1.1.branch.20110422 with cwmv8.zip
the response says:
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
@set /p batuserinput=Press enter to continue:
- what does this mean?
1. Is there any sort of display brightening (even briefly?) after you power on? In APX mode, for example, the screen will brighten slightly, then go dead again.
2. Try this test on Ubuntu to see if the tablet has gone into APX mode:
Code:
[I]Power off gTab.
Power on gTab using Power & Vol [-].[/I]
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[18045.279886] usb 1-1.2: new full speed USB device number 6 using ohci_hcd
[18045.384823] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7820[/B]
[18045.384830] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[18045.384835] usb 1-1.2: Product: APX
[18045.384839] usb 1-1.2: Manufacturer: NVIDIA Corp.
$
A USB product id of 7820 indicates APX mode on the gTab.
Post the exact output (if any) of your run here.
For reference this is the output when the gTab is running either CWM or the ROM:
Code:
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to the gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[17516.799429] usb 1-1.2: new full speed USB device number 5 using ohci_hcd
[17516.911353] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7100[/B]
[17516.911361] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17516.911366] usb 1-1.2: Product: NVIDIA Harmony
[17516.911370] usb 1-1.2: Manufacturer: NVIDIA
[17516.911374] usb 1-1.2: SerialNumber: 0270308341006257
$
The product id will be 7100.
[email protected]:~$ coonected USB to Gtab, power button plus vol minus 2 minutes
coonected: command not found
[email protected]:~$ sudo dmesg -c >/dev/nul
bash: /dev/nul: Permission denied
[email protected]:~$ pwd
/home/ubuntu
[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ pwd
/
[email protected]:/$ sudo dmesg -c >/dev/null
[email protected]:/$ dmesg
[email protected]:/$
[email protected]:/$
It's not surprising that you got no output--I screwed up. The sequence of steps was incorrect: the cable has to be connected between the 2 dmesg commands. Please repeat.
(If you want to insert inline comments on the command line do it like this:
Code:
$ [B]# This is just a comment.[/B]
The shell will ignore everything from the `#' character to the end of the line.)
And, this video is what I recommend to people whose bootloader seems to be trashed--which is what I think your problem is: How to unbrick your Viewsonic G-Tablet
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$
The first 2 commands are not needed:
hushpup131 said:
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$
Click to expand...
Click to collapse
Yeah, as I suspected, its a bad bootloader and/or other critical partition problem.
If you are certain that the USB cable and ports are OK (check using another device--try a "sudo adb devices" command with a phone, for instance) and you ran the second dmesg command after connecting the USB cable (otherwise, power off and do the sequence again), then your only option now is to follow the K1 pad-shorting procedure shown in the video.
BTW, you didn't answer question #1 in post #5, above. Is there any change in the display brighness after powering on?
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
[13557.908045] usb 4-1: new low-speed USB device number 4 using uhci_hcd
[13558.145227] input: Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00 as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input17
[13558.145525] generic-usb 0003:045E:00E1.0003: input,hidraw0: USB HID v1.11 Mouse [Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00] on usb-0000:00:1a.1-1/input0
[13558.256080] usb 1-4: new high-speed USB device number 6 using ehci_hcd
[13558.397196] scsi9 : usb-storage 1-4:1.0
[13559.397403] scsi 9:0:0:0: Direct-Access Motorola A855 0001 PQ: 0 ANSI: 2
[13559.398816] sd 9:0:0:0: Attached scsi generic sg3 type 0
[13559.403602] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[email protected]:~$
question one, post five... there was no change in the display
There was no change in the display after shorting K1
hushpup131 said:
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
Click to expand...
Click to collapse
Your USB cable seems OK, but, I don't like that line above. Can you describe exactly what you did when you captured that output?
And, run through that dmesg sequence once again exactly as described and post the output. Also, connect the gTab directly to a USB port, and not through a hub.
Related
UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/
well I see you fixed it. did you get adb going?
Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk
are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.
Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone
Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
Verifying connectivity with lsusb results in:
Code:
[email protected]:/home/badday/Downloads# lsusb
(...)
Bus 002 Device 011: ID [B]1b3f[/B]:8300 Generalplus Technology Inc.
So the device seems to be present. I also added /etc/udev/rules.d/51-android.rules with
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1b3f", ATTRS{idProduct}=="8300", MODE="0666", OWNER="badday"
and made sure that rights are correct:
Code:
[email protected]:/home/badday/Downloads# chmod a+r /etc/udev/rules.d/51-android.rules
[email protected]:/home/badday/Downloads# service udev restart
However, fastboot does not find the device:
Code:
[email protected]:/home/badday/Downloads# ./fastboot devices
[email protected]:/home/badday/Downloads# ./fastboot -i 0x1b3f getvar VERSION
< waiting for device >
As you can see I am running it as root. When booted normally, device is recognized (of course with different vendor ID etc.) with adb and I can make it boot to recovery mode, but not to bootloader mode. Trying to do so will result in a normal reboot (from what I can see).
Anyone having some idea?
Thanks a lot,
badday
root
badday2 said:
Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
Verifying connectivity with lsusb results in:
Code:
[email protected]:/home/badday/Downloads# lsusb
(...)
Bus 002 Device 011: ID [B]1b3f[/B]:8300 Generalplus Technology Inc.
So the device seems to be present. I also added /etc/udev/rules.d/51-android.rules with
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1b3f", ATTRS{idProduct}=="8300", MODE="0666", OWNER="badday"
and made sure that rights are correct:
Code:
[email protected]:/home/badday/Downloads# chmod a+r /etc/udev/rules.d/51-android.rules
[email protected]:/home/badday/Downloads# service udev restart
However, fastboot does not find the device:
Code:
[email protected]:/home/badday/Downloads# ./fastboot devices
[email protected]:/home/badday/Downloads# ./fastboot -i 0x1b3f getvar VERSION
< waiting for device >
As you can see I am running it as root. When booted normally, device is recognized (of course with different vendor ID etc.) with adb and I can make it boot to recovery mode, but not to bootloader mode. Trying to do so will result in a normal reboot (from what I can see).
Anyone having some idea?
Thanks a lot,
badday
Click to expand...
Click to collapse
Hey can you please guide me how did you root this device? I am having the same and I need to root it. Thanks.
badday2 said:
Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
... [CUT FOR SPACE] ...
Thanks a lot,
badday
Click to expand...
Click to collapse
I have the exact problem badday has, but with the Ainol Novo7 Paladin. Any help will be appreciated in my corner as well!
Unable to root Zync z930
I have the same need to root the Zync z930 tab, currently there is nothing available on the internet to root this tab. If anyone of you manages to crack it please let me know, thanks!
---------- Post added at 08:27 PM ---------- Previous post was at 08:22 PM ----------
I have the same need to root the Zync z930 tab, currently there is nothing available on the internet to root this tab. If you managed to crack it please let me know, thanks!
To clarify things: I did not root my device so far.
Some additional information I found out:
Try to reboot in adb via "reboot-bootloader" results in normal startup. Furthermore, booting to fastboot mode (with vol-up-button down) with Micro-SD-Card inserted makes the device not to appear any more in lsusb.
Anyway, that made me having even less clues than more :crying:
This is cheap chinese phone with an equally defective android implementation. The battery just lasts about an hour, I am sick of it.
abdulmomin said:
This is cheap chinese phone with an equally defective android implementation. The battery just lasts about an hour, I am sick of it.
Click to expand...
Click to collapse
Anyone found any method to root z930?
I'm not sure for linux but I think you will have to download drivers ,,,,,,,I had to do this for my computer (running win 7) to read my phone in fast boot
I downloaded an app called driver tools and that fixed it ....hope this helps
Ps : It maybe that your running 64 bit Os
@abdulmomin, jaydeepkhalpada: Rooting thread can be found here: http://forum.xda-developers.com/showthread.php?t=2028740
@fredworxz: Yes, I use a 64bit OS. However, for GNU/Linux drivers should not be needed as adb runs out of the box (please correct me if I am wrong).
Resolved! - See my post! http://forum.xda-developers.com/showthread.php?t=2045173
I've not only installed JB in Z930 but also successfully ADB'd it to root it
Here:
http://forum.xda-developers.com/showthread.php?t=2045173
Actually I cannot install the driver which might be some problem as I use 64bit OS and have no 32bit available. Anyhow, according to the name scheme, there should also be a 64bit version included.
Apart from that I have also problems with this Chinese software, does it need adb drivers to be installed? Actually when I boot in this mode with vol-up-button, there appears absolutely nothing in the device manager.
Would be great if you could help me out as I need this tablet for some sort of NGO project.
Greetings from Delhi,
badday
This is not fastboot mode
as your trying to unlock fastboot ,but this is not fastboot mode
this is for flashing firmware through G+massprotection tool..
There is no fastboot mode in Z930..
but you can goto recovery menu by pressing
1st press & release Power button then press and hold vol+ button
My problem is my tablet is visible in normal mode on my pc. Bootloader 4.2.1, The Device is unlocked ok. adb devices: #serie ok, and adb reboot-bootloader function works. The tablet will reboot into fastboot mode, but I am unable to find a driver that works on my pc. I installed 1.97 pc asus sync, google sdk, minimal adb fasboot driver, all indicates error code 10
"fastboot devices" does not work. Rck is on and the icon does not flashes, the fastboot reboot feature is '' Waiting for device ". So if I disconnect and reconnect the USB cable, the tablet will restart on the OS...
Even tried with a live linux cd and still the same problem...
Note my usb cable has been replaced by a generic for my original cable had become unstable.
It can be the cause of my problem. Of course I tested with 2 cables? Factory reset and unlocke with v7 and v8 apk, and also an OEM recovery to latest firmware 10.6.1.27.5-20130902
I would like to set up a recovery to try others Roms,
Thanks for your help.
cyborg3691 said:
I would like to set up a recovery to try others Roms,
Click to expand...
Click to collapse
First of all, your boot loader must end with 27.5. Check it out when you are unsure before you do anything more.
Then try to flash Kang TWRP from your SD Card with Terminal Emulator using the following code:
dd if=/sdcard/ twrp_tf300t_kang_2.8.7.2.img of=/dev/block/mmcblk0p4
For more information have a look at Josh’s thread http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
For this soluce the tablet need to be root...
I have make this but not working, the terminal not see the file on sd card....
On terminal i see
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4
/sdcard/foo.img cannot open for read: no such file or directory
1 [email protected]:/ #
help me
SOLUCE With another computer...
My problem was my computer z87 motherboard with incompatible usb port? I try front and rear usb ports,
with a generic usb cable, I have solutioned this problem, with a other old computer and minimal adb fastboot v. 1.3.1 with a netbook msi wind u100 runing xp and now, tf300t was detected in adb and fastboot mode the command devices works fine. I intall twrp and intall and try another rom.
Thanks for your help.
Read this whole guide before starting.
This is for the 6th gen Fire HD8 (giza).
Current version: amonet-giza-v1.3.zip
NOTE: This process does not require you to open your device, but should something go horribly wrong, be prepared to do so.
NOTE: This process will modify the partition-table (GPT) of your device.
NOTE: Your device will be reset to factory defaults (including internal storage) during this process.
What you need:
A Linux installation or live-system
A micro-USB cable
Install python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu something like this should work:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
1. Extract the attached zip-file "amonet-giza-v1.2.zip" and open a terminal in that directory.
NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by @diplomatic from here and place (the unpacked binary) into amonet/bin folder
2. Enable ADB in Developer Settings.
3. Start the script:
Code:
sudo ./step-1.sh
Your device will now reboot into recovery and perform a factory reset.
NOTE: If your PL/TZ/LK versions are too new, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
If you chose the brick option, you don't need to run step-2.sh below:
Make sure ModemManager is disabled or uninstalled:
Code:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
After you have confirmed the bricking by typing "YES", you will need disconnect the device and run
Code:
sudo ./bootrom-step-minimal.sh
Then plug the device back in.
It will then boot into "hacked fastboot" mode.
Then run
Code:
sudo ./fastboot-step.sh
NOTE: When you are back at initial setup, you can skip registration by selecting a WiFi-Network, then pressing "Cancel" and then "Not Now"
NOTE: Make sure you re-enable ADB after Factory Reset.
4. Start the script:
Code:
sudo ./step-2.sh
The exploit will now be flashed and your device will reboot into TWRP.
You can now install Magisk from there.
Going back to stock
Extract the attached zip-file "amonet-giza-v1.2.zip" and open a terminal in that directory.
You can go back to stock without restoring the original partition-table, so you can go back to unlocked without wiping data.
Just use hacked fastboot to
Code:
sudo fastboot flash recovery bin/recovery.img
If you want to go back completely (including restoring your GPT):
Code:
sudo ./return-to-stock.sh
Your device should reboot into Amazon Recovery. Use adb sideload to install stock image from there.
Important information
In the new partitioning scheme your boot/recovery-images will be in boot_x/recovery_x respectively, while boot/recovery will hold the exploit.
TWRP takes care of remapping these for you, so installing zips/images from TWRP will work as expected.
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.) (If you do anyway, make sure you flash them to boot_x/recovery_x)
Should you accidentally overwrite the wrong boot, but your TWRP is still working, rebooting into TWRP will fix that automatically.
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).
It is still advised to disable OTA.
Very special thanks to @xyz` for making all this possible and releasing the original amonet exploit for karnak.
Special thanks also to @k4y0z for making all this possible and porting the exploit to 64 bit devices.
Special thanks also to @diplomatic for his wonderfull mtk-su, allowing you to unlock without opening the device.
Special thanks also to @lovaduck for all the testing.
Unbricking
If Recovery OR FireOS are still accessible there are other means of recovery, don't continue.
If your device shows one of the following symptoms:
It doesn't show any life (screen stays dark)
You see the white amazon logo, but cannot access Recovery or FireOS.
If you have a Type 1 brick, you may not have to open the device, if your device comes up in bootrom-mode (See Checking USB connection below).
Make sure the device is powered off, by holding the power-button for 20+ seconds
Start bootrom-step.sh
Plug in USB
In all other cases you will have to open the device and partially take it apart.
1. Extract the attached zip-file "amonet-giza-v1.2.zip" and open a terminal in that directory.
2. Start the script:
Code:
sudo ./bootrom-step.sh
It should now say Waiting for bootrom.
If you're lucky and have an old preloader (Up to FireOS 5.3.2.0), you can just hold the left volume button while plugging the device in.
If you're on a newer preloader, there are two options:
Open the device and short the marked pin (CLK) in the attached photo to ground while plugging in.
Downgrade to 5.3.1.0 firmware (google drive mirror) via adb sideload in Amazon recovery, then proceed to use the left volume button to enter boot-rom.
NOTE: Using option two may brick your device until you have successfully finished the process.
4. When the script asks you to remove the short, remove the short and press enter.
5. Wait for the script to finish.
If it fails at some point, stop it and restart the process from step 2.
6. Your device should now reboot into unlocked fastboot state.
7. Run
Code:
sudo ./fastboot-step.sh
The device should reboot to TWRP. Format data and use TWRP to flash a custom ROM, Magisk or SuperSU.
Checking USB connection
In lsusb the boot-rom shows up as:
Code:
Bus 002 Device 013: ID 0e8d:0003 MediaTek Inc. MT6227 phone
If it shows up as:
Code:
Bus 002 Device 014: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
instead, you are in preloader-mode, try again.
dmesg lists the correct device as:
Code:
[ 6383.962057] usb 2-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.0
Source Code:
https://github.com/R0rt1z2/amonet-giza
https://github.com/R0rt1z2/android_device_amazon_giza
https://github.com/chaosmaster/android_bootable_recovery
Reserved #1
Great job by Roger, everything worked very much at first attempt while I tested. Now I have revived an old tablet that was not in use anymore!
I would advise everybody trying this process to keep in mind that things can always go wrong, but you have nothing to lose anyways. Hack at your own risk.
So good luck with the mod, and again, kudos to @Rortiz2
I get the following when running step 1:
This is only for the "giza" - Amazon Fire HD 8 (2016) - , your device is a "full_giza"
Click to expand...
Click to collapse
Is there much of a difference between the two and if not should I just edit the check in step-1.sh & step-2.sh?
cultofrobots said:
I get the following when running step 1:
Is there much of a difference between the two and if not should I just edit the check in step-1.sh & step-2.sh?
Click to expand...
Click to collapse
Oh well, my fault, let me fix that.
EDIT: Fixed the product check, use the v1.1 package.
Wrong thread.... deleted.
Rortiz2 said:
Oh well, my fault, let me fix that.
EDIT: Fixed the product check, use the v1.1 package.
Click to expand...
Click to collapse
That worked. Thanks.
thankssssss my frind , but i want root for fire hd8 5gen veeeeeerynessry sory bad englash
also i can buy it form you pleassss
789mod said:
thankssssss my frind , but i want root for fire hd8 5gen veeeeeerynessry sory bad englash
also i can buy it form you pleassss
Click to expand...
Click to collapse
Unfortunately, the Amazon Fire HD8 2015 (thebes) uses MT8135 which is pretty different to MT8163. Since I don't own the device, I can't really help you with that.
Rortiz2 said:
Unfortunately, the Amazon Fire HD8 2015 (thebes) uses MT8135 which is pretty different to MT8163. Since I don't own the device, I can't really help you with that.
Click to expand...
Click to collapse
have you any way to root these ) fire HD 10 5gen ?
I need it to my wrok
my work it unlockbootloader
Hi. I have a problem on Step 2
adb: error: cannot stat 'bin/boot0short.img': No such file or directory
Click to expand...
Click to collapse
I checked bin directory and really didn't found boot0short.img. Maybe it should be generated by the script. I checked code and didn't found any other mentions about this file...
What I doing wrong?
sancho_sumy said:
Hi. I have a problem on Step 2
I checked bin directory and really didn't found boot0short.img. Maybe it should be generated by the script. I checked code and didn't found any other mentions about this file...
What I doing wrong?
Click to expand...
Click to collapse
I've updated the main post with the v1.2 version, can you try with that one, please?
(https://forum.xda-developers.com/attachments/amonet-giza-v1-2-zip.5405917/)
Rortiz2 said:
I've updated the main post with the v1.2 version, can you try with that one, please?
(https://forum.xda-developers.com/attachments/amonet-giza-v1-2-zip.5405917/)
Click to expand...
Click to collapse
Now I have a brick...
Dark screen after "Rebooting into TWRP"
Dark screen, device didn't responce on power button...
sancho_sumy said:
Now I have a brick...
Dark screen after "Rebooting into TWRP"
Dark screen, device didn't responce on power button...
Click to expand...
Click to collapse
Bricked after running the 1.2 version? That makes no sense, unless your RPMB was updated. What's the output of "lsusb" when you plug in the tablet to the computer"?
Rortiz2 said:
Bricked after running the 1.2 version? That makes no sense, unless your RPMB was updated. What's the output of "lsusb" when you plug in the tablet to the computer"?
Click to expand...
Click to collapse
Yes. I run Step 2 from 1.2 version.
After "Rebooting into TWRP" screen off and didn't on anymore.
It's not listed in lsusb:
[email protected]:~/Downloads/amonet-giza-v1.2$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:2113 Acer, Inc Integrated Camera
Bus 001 Device 005: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
After plug in to USB dmesg:
usb 1-3: USB disconnect, device number 7
Click to expand...
Click to collapse
Is there any chances to fix it? :-(
sancho_sumy said:
Yes. I run Step 2 from 1.2 version.
After "Rebooting into TWRP" screen off and didn't on anymore.
It's not listed in lsusb:
After plug in to USB dmesg:
Is there any chances to fix it? :-(
Click to expand...
Click to collapse
don't worry
first short your devices after this
2. sudo ./boot-fastboot.sh
the screen still black
after that
unplug your USB write sudo ./ fastboot-step.sh and plug it
and wait 1sec
will successfully..
thank
789mod said:
don't worry
first short your devices after this
2. sudo ./boot-fastboot.sh
the screen still black
after that
unplug your USB write sudo ./ fastboot-step.sh and plug it
and wait 1sec
will successfully..
thank
Click to expand...
Click to collapse
do you have any detailed instruction how to short it?
sancho_sumy said:
do you have any detailed instruction how to short it?
Click to expand...
Click to collapse
before short ,
try this commands
sudo ./boot-fastboot.sh
and wait 3sec
and
sudo ./fastboot-step.sh
Hello, guys
first i read the diff between soft/hard brick, and i think i'm in the soft case, cause i can get in recovery menu.
adb dont see the phone at all,
fastboot can, but not 'fastboot oem unlock' , neither 'fastboot boot recover.img' works. Actually command prompt wait there for ever, untin the PC kernel ( linux deb 11), break fastboot usb connection, with a reason of connection timeout. this timeout is after 30minutes ....
i manage to backup user data for the recovery menu, in 3 files 2x2G 1x1.7G ( i think because of fat ),
but the revcovery menu fail to [ wipe data/factory reset ]. Strange ? Any ideas?
here is the model f the tablet,
==> /var/log/syslog <==
Nov 6 20:12:48 localhost kernel: [1024828.830129] usb 5-2: New USB device found, idVendor=0bb4, idProduct=0c01, bcdDevice= 1.00
Nov 6 20:12:48 localhost kernel: [1024828.830135] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 6 20:12:48 localhost kernel: [1024828.830138] usb 5-2: Product: Android
Nov 6 20:12:48 localhost kernel: [1024828.830140] usb 5-2: Manufacturer: MediaTek
Nov 6 20:12:48 localhost kernel: [1024828.830142] usb 5-2: SerialNumber: mt6582_phone
#---------------------------------------------------------------------------------------------------
# ID 0bb4:0c01 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo / FP1
#---------------------------------------------------------------------------------------------------
# Android system recovery (3e)
# A7-30DC_S0000129_150831_ROW
#---------------------------------------------------------------------------------------------------
1. To successfully run ADB and/or Fastboot commands you need to have installed on computer the "Android USB Driver" provided by device's manufacturer.
2. ADB only will work if it got enabled on Android device.
jwoegerbauer said:
1. To successfully run ADB and/or Fastboot commands you need to have installed on computer the "Android USB Driver" provided by device's manufacturer.
2. ADB only will work if it got enabled on Android device.
Click to expand...
Click to collapse
i know, everythinks works just fine, with other android devices.
( i'm using linux by the way )
My problem right now is,
why the stock recovery fail to wipe/factory reset ?
no fastboot or adb
The tablet stuck in he lenovo logo on boot for ever,
so adb dont have any way in this stage
I try 'update cache from ADB' just to see if adb can see it, but no
when 'fastboot boot recovery.img'
the phone (tablet), report get some bytes
but nothing else
when 'fastboot oem unlock', nothing happens, both the phone and the terminal
i use this links for recovery images:
https://forum.xda-developers.com/attachments/recovery_p780_cwm_6-0-1-5-7z.2840100/
https://forum.xda-developers.com/attachments/p780_recovery_twrp_2-6-3-0-zip.2840101
any pins on hardware, to triger factory reset .... ?