Related
I used the tool on my HTC Vivid running 4.0.3 ICS
Unlocked bootloader - easy
Flash arecovery - easy
More Flash Recovery documentation is needed. Without documentation, how do you know which recovery to install. The tool lists the following: 1) CWM 5.5.0.4 (GB) 2) WCXs CWM(GB / ICS). Does GB stand for Ginger Bread and ICS for Ice Cream Sandwich?
Also, to root the phone, do you need to install a Kernel? If so, some documentation on the various kernels available would be very helpful.
Also when performing perm root, instructions say press a button to complete the process. What button? Phone power/volume or Enter on DOS prompt. I've tried this n times x n ways without success.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
"Android is installing" on EVERY reboot
Could it be that after "Perm Root" is run the phone reboots. During bootup the phone always goes into an Android is installing loop. Maybe the endless update loop always overwrites the root that was just applied.
"Android is installing" on EVERY reboot
Going to "Settings/Storage" and performing a "Factory Data reset" did not take care of the "Android is Installing" that occurs every time the phone restarts.
After bootup the phone works ok; however, if I restart the phone the "Android is Installing" will repeat.
What's the solution?
Still trying to fix "Android is Upgrading" issue
A forum entry suggested setting fastboot mode to fix the "Android is Upgrading" issue.
Goto -> settings/Power/Fastboot checked
Performed restart
"Android is Upgrading" loop occurred again
This above did not work
Still trying to fix "Android is Upgrading" issue
A forum suggested wiping the davlic cache to fix the "Android is Upgrading" loop.
From All-In-One Kit, applied perm root
# FYI: this leaves phone in recovery screen
wipe davlic cache from Recovery menu
reboot
same "Android is Upgrading" loop occurred again
Above did not work
HTC White Screen after Flash Stock Kernel
I flashed the Stock Kernal using the "Hasoon2000's HTC Vivid All-In-One Kit"
NOTE:
> The Kernel Flash failed on "adb remount" - output shown below.
> Other command seemed successful.
After flashing reboot, the phone stays on HTC white screen forever.
I need help to Unbrick this phone.
Note: If I pull out/in the battery, I can successfully perform the following:
> adb reboot-bootloader
> or adb reboot recovery
#####################
# Flash Stock Output
#####################
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Unknown error: 0
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>adb push Kernels/ModulesStock/system /system
push: Kernels/ModulesStock/system/lib/modules/spidev.ko -> /system/lib/modules/spidev.ko
push: Kernels/ModulesStock/system/lib/modules/lcd.ko -> /system/lib/modules/lcd.ko
push: Kernels/ModulesStock/system/lib/modules/cpaccess.ko -> /system/lib/modules/cpaccess.ko
push: Kernels/ModulesStock/system/lib/modules/bcm4330.ko -> /system/lib/modules/bcm4330.ko
4 files pushed. 0 files skipped.
2001 KB/s (608638 bytes in 0.297s)
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>adb reboot bootloader
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>fastboot flash boot Kernels/Kernel-HereStock/boot.img
< waiting for device >
sending 'boot' (2838 KB)... OKAY [ 0.735s]
writing 'boot'... OKAY [ 1.088s]
finished. total time: 1.823s
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>fastboot reboot
rebooting...
finished. total time: 1.937s
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
More on my HTC Vivid Behavior
Please see the following. Any help fixing my phone will be highly appreciated.
#################################################
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb reboot-bootloader
Phone screen shows:
*** UNLOCKED ***
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0025
MICROP-0360
Mar 1 2012,17:09:49
...
*** The above worked
Selected power down
################################################
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb reboot recovery
Phone screen shows:
Android system recovery
- Reboot system now
- USB-MS toggle
- Backup/Restore
...
- Developer menu
- Power off
------------------------
...
RA Revamped
Build: Made for WCX ILLUMINATI SERIES BY GINM
#################################################
From Recovery wipe / all
reboot
same, get's stuck at HTC White screen
Have to pull battery out and start again
################################################
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb get-serialno
HT1ASVJ27111
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb get-state
unknown
################################################
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb shell
~ # ?[6nls
ls
/sbin/sh: ls: not found
~ # ?[6nls -la
ls -la
/sbin/sh: ls: not found
~ # ?[6ncd /
cd /
~ # ?[6nls
ls
/sbin/sh: ls: not found
~ # ?[6n
Was S-On the reason for the flash failure?
Did the Flash Kernel to Stock fail because my phone was S-On?
It seems Hasoon2000's HTC Vivid All-In-One Kit is not noob proof.
Almost Solved - Restored HTC Vivid to Stock
I restored my HTC Vivid to Stock using the PROCEDURE below
PROCEDURE:
1) Perform PROCEDURE: Put phone in bootloader
2) Perform PROCEDURE: Relock bootloader
3) Perform PROCEDURE: Obtain Flash Media (PH39IMG.zip)
4) Perform PROCEDURE: Flash back to Stock
5) Your phone should now be restored to stock
Discovered all is not well:
The Radio on the restored phone is not working.
PROCEDURES ARE SHOWN BELOW:
##################
# PROCEDURE: Put phone in bootloader
##################
power off phone (remove/insert battery)
connect phone to computer via usb
Open command prompt
C:\Android\VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
##################
# PROCEDURE: Relock bootloader
# NOTE: I Ignored the FAILED meesge
# WHY? Put phone back in bootloader, the screen says "relocked"
##################
C:\Android\VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.027s
##################
# PROCEDURE: Obtain Flash Media (PH39IMG.zip)
##################
Download PH39IMG.zip file - this includes recovery, system, everything stock
Verify the file is good by Using WinMd5Sum utility
Good MD5 = ab2ad5f3eebbbbb246da204b4d78d418
save the file at the root of your sd card
power off phone (i.e. remove battery)
put the microSD card back into your phone
##################
# PROCEDURE: Flash back to Stock
##################
Perform PROCEDURE: Put phone in bootloader
FROM the phone's bootloader:
- boot to bootloader to initiate the update
- It should automatically find the zip file in the microSD and flash the stock image
*** What I remember about the upgrade - may not be exact ***
When the upgrade starts the phone says some stuff about the image
THE upgrade installs 3 or 4 items
reboots to continue the upgrade
continues installing a list of items, you should see all ok's for each
After upgrade completed, the screen displayed a Green battery
I pressed power button and the phone rebooted correctly
*** Yahoo my phone is fixed!!! I am back to stock. ***
##################
# Lesson Learned
##################
Be very careful. Read, read, and read some more. Learn to be patient.
Don't trust anything blindly do your home work.
##################
# Credits
##################
Obtained the raw procedure from the following post:
http://forum.xda-developers.com/showpost.php?p=20807914&postcount=2
##################
# Future s-off reading
##################
Without s-off you cannot flash other kernels
S-off seems to be required for perm root
ControlBear (the wire trick) for s-off: http://unlimited.io/
Revolutionary s-off (not supported on htc vivid as of 5/23):
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
Factory Data Rest killed the phone
From the phones settings menu, I performed a factory reset. I did this because of the radio issue.
The phone is now 100% dead. Does not do anything. I don't think this is a happy ending. I tried.
Hello everyone
I am the owner of a Vodafone 858 smart/Huawei u8160 approximately 2 months and i have been tested more custom ROMs. Recent am downloadat Vodafone858C02B617-update_signed (original ROM) and installed, after this flash rom i have problems:
- device start but stuck at first screen
- trying recovery mod "power + volum up" nothing happen
Trying to work under adb or fastboot.
===========================================================
adb method
- typing adb device (work and see my device 80B686285DD5 recovery)
- typing adb reboot (Work)
- typing adb shell (not working - exec '/system/bin/sh' failed: No such file or directory (2) -)
- typing adb push "file/dir" "target dir" (not working/not rooted failed to copy 'sh' to '/system/bin': Permission denied)
-----------------------------------------------------------------------------
Fastboot method
Dont work
- typing fastboot device (dont see my device)
============================================================
Drivers are working on my pc, no error/unknown at computer drivers, i belive i have right drivers. If u have any sugestion plz feel free to speak. If any of u can help me plz do.
Thank you in advance for your efforts.
Katallyn
I have exactly the same problem
happened after flashing a kernel on my P990...
btw: I've booted into CWR, formatted my /system partition and re-installed a ROM
that did the trick without losing any user data
Katallyn said:
adb method
- typing adb device (work and see my device 80B686285DD5 recovery)
- typing adb reboot (Work)
- typing adb shell (not working - exec '/system/bin/sh' failed: No such file or directory (2) -)
- typing adb push "file/dir" "target dir" (not working/not rooted failed to copy 'sh' to '/system/bin': Permission denied)
Click to expand...
Click to collapse
You might try adb remount before the adb push command. Hopefully you have a good copy of sh to do this with.
-Snags
Hello everyone,
I have unlocked my ASUS TF700T and then attempted to TWRP and a custom ROM. Once I did this, I began having issues. It wouldn't boot. I couldn't restore from TWRP backup. I can't seem to write to the system partition for some reason via fastboot but I seem to be able to do this just fine when in CWM or TWRP. Can anyone suggest what I may try from here? I can only get into recovery via VOL DOWN when booting and then selecting the wipe option. Right now I have two major issues. One is that for the life of me, I have never been able to get fastboot to show the actual serial of the device. It has always shown a single question mark. I have gone as far as building a Linux mint box just to get ADP and FASTBOOT drivers to install correctly on a 32-bit machine with USB 2.0. No luck, save result. My second issue is that I am unable to write to the system partition via fastboot. It gives me a remote () error message on fastboot and a could not process the command error in red on my tablet. I will have the exact error message for you shortly but right now I just wanted to get this posted. Any suggestions?
I can't flash the stock blob via fastboot and I can't seem to install a custom ROM via TWRP or CWM. Please advise.
I suspect me not being able to use ADB is my biggest problem. I can't see a serial number when I use fastboot devices. I have tried endlessly to get this resolved and I can't get it to change, AT ALL. I have installed google drivers, 32-bit fresh Linux OS, and plenty of utilities to auto install. No luck. If anyone can help with this, I'd appreciate it.
Here are my issues in a nutshell.
1.) I am unable to boot into recovery directly. I have to go into fastboot and select wipe, it then reboots and starts up in the recovery kernel. TWRP simply executes a command and then restarts and CWM actually boots and allows me to use it.
2.) No matter what I've tried, I have not been able to get the serial number to come up via fastboot. It simply shows a single questionmark. I have tried many solutions for this, but nothing changes.
3.) I am not sure but I believe the bootloader may be the problem. I can currently use fastboot but adb does not recognize the device.
Any assistance would be greatly appreciated. Thank you! I have tried different version of TWRP and clockwork mod but all seem to have the same result. I also attempted to install another custom rom just for good measure and CWM states that
-Tony
Boy oh boy! Mate, your post is one of the most confusing (and confused) posts I have read in a long time. I think you need to go back to the drawing board, forget everything you think you know and start fresh.
Let's clear some of it up:
1) CWM is a recovery (ClockWorkMod), I think you mean your rom is CM (CyanogenMod)
2) When you boot with Volume Down and Power you are booting into the bootloader, you see the bootloader menu and the tablet is in fastboot mode. The bootloader menu consists of 3 icons (if you are on a 4.2 bootloader):
RCK (recovery),
Android (system),
Wipe Data (stay away - it's a small miracle that you are not hard bricked already if you used this)
Are you saying you don't have those three in the BL menu????
RCK should be flashing and pushing Volume Up should boot you into recovery. There is no way to boot directly into it unless your rom has a modified restart menu.
3) adb and fastboot are two different protocols to connect PC and tablet. You use adb when Android is running, you use fastboot when the tablet is in fastboot mode.
Don't know what you tried to get the correct drivers working, but you probably have to go back to square 1 here too. If you use Windows check in Device Manager if your tablet is recognized at all:
Open Device Manager, boot the tablet int the bootloader and connect it via original USB cable to the PC. Do you see any change in Device Manager?
You left out the most important bits:
What bootloader version are you on?
Which version of TWRP?
How did you install TWRP if you don't have fastboot working?
What CM version are you running?
Thanks for the reply. I'll try and be more concise...
Hello,
First of all, I'd like to say thank you. I am all over the place. I will attempt to be more detailed and concise with my wording. Here are my responses below:
berndblb said:
Boy oh boy! Mate, your post is one of the most confusing (and confused) posts I have read in a long time. I think you need to go back to the drawing board, forget everything you think you know and start fresh.
Let's clear some of it up:
1) CWM is a recovery (ClockWorkMod), I think you mean your rom is CM (CyanogenMod)
Click to expand...
Click to collapse
I am familiar with the difference. I have not used nor flashed CyanogenMod. I have indeed installed CWM on recovery and can still do so. I just can't boot into recovery without using the dreded WIPE option on my bootloader. Once I use this, it restarts in CWM and I can use it (still fails to install anything on system though.)
berndblb said:
2) When you boot with Volume Down and Power you are booting into the bootloader, you see the bootloader menu and the tablet is in fastboot mode. The bootloader menu consists of 3 icons (if you are on a 4.2 bootloader):
RCK (recovery),
Android (system),
Wipe Data (stay away - it's a small miracle that you are not hard bricked already if you used this)
Click to expand...
Click to collapse
I have 2 options for my bootloader when I boot into it, fastboot(USB Icon) and wipe (I think we all know this one.) That's it. This is part of the reason why I can't get to recovery mode without using the WIPE option. (I stayed away from the wipe optoin for weeks until I was convince there was nothing else to try. Once I tried this, I was able to boot into recover with CWM or TWRP. TWRP however ONLY runs some sort of script and then reboots again. CWM allows me to use it. Hope this makes sense. Please let me know if I should clarify further.
berndblb said:
Are you saying you don't have those three in the BL menu????
RCK should be flashing and pushing Volume Up should boot you into recovery. There is no way to boot directly into it unless your rom has a modified restart menu.
Click to expand...
Click to collapse
I do not. Since I first installed TWRP, ran a TWRP backup and installed the custom 4.4.2 (I believe) rom I have not seen any other options.
berndblb said:
3) adb and fastboot are two different protocols to connect PC and tablet. You use adb when Android is running, you use fastboot when the tablet is in fastboot mode.
Don't know what you tried to get the correct drivers working, but you probably have to go back to square 1 here too. If you use Windows check in Device Manager if your tablet is recognized at all:
Open Device Manager, boot the tablet int the bootloader and connect it via original USB cable to the PC. Do you see any change in Device Manager?
Click to expand...
Click to collapse
I have gone over multiple times but I am willing to start again. I show ASUS Android Device in Device Manager for Windows 8.1 64-bit. (I have tried flashing many times on Windows 7 32-bit and Linux 32-bit both on USB 2.0. No luck, same issues, same results.
berndblb said:
You left out the most important bits:
What bootloader version are you on?
Which version of TWRP?
How did you install TWRP if you don't have fastboot working?
What CM version are you running?
Click to expand...
Click to collapse
I have no clue how to check the bootloader version without getting into Android. My bootloader doesn't seem to show it on the upper left hand side. Do you know how I can get it?
I have tried TWRP 3.2.1.0, TWRP 2.6.3.2, CWM 6.0.4.7 and Phil's CWM based recovery for the TF700. So far, none have been able to flash a custom ROM again nor the stock rom when I use recovery GUI for them. Please advise.
Also, it seems I am able to write to any partition with fastboot except for system. When I write to the system partition my tablet shows red text on the screen that states "the command flash:system failed 0x170003 or something similar. Fastboot shows a failed: (remote() error after trying to write to the partition. Someone told me my boot loader was the problem, but I have no idea how to change it without using the 'staging' or 'flash system commands.'
I'm not sure if this matters but I thought I'd post it. When I run fastboot -w it fails saying that the file system is not supported. When I run fastboot erase userdata or cache. It seems to work without any issues. Here is a sample of the output I get:
Code:
c:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 10.093s]
finished. total time: 10.093s
c:\adb>erase cache
Could Not Find c:\adb\cache
c:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 1.980s]
finished. total time: 1.980s
c:\adb>fastboot -w
erasing 'userdata'...
OKAY [ 10.031s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.001s]
erasing 'cache'...
OKAY [ 1.972s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.001s]
finished. total time: 12.006s
c:\adb>
When I try to use fastboot to flash the stock firmware using the staging command, I get this on my command prompt:
Code:
c:\adb>fastboot -w flash staging blob
sending 'staging' (800927 KB)...
OKAY [139.757s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 140.900s
c:\adb>
on my tablet it reads in red text failed to process command flash:staging error 0x170003. I have to do a cold boot to get it back up to fastboot mode.
-Tony
qzmicro said:
Hello,
When I try to use fastboot to flash the stock firmware using the staging command, I get this on my command prompt:
Code:
c:\adb>fastboot -w flash staging blob
sending 'staging' (800927 KB)...
OKAY [139.757s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 140.900s
c:\adb>
on my tablet it reads in red text failed to process command flash:staging error 0x170003. I have to do a cold boot to get it back up to fastboot mode.
-Tony
Click to expand...
Click to collapse
Tony try this instead:
Code:
fastboot -i 0x0B05 flash system blob
I have tried it with -i 0x0B05 but it never has different results
sbdags said:
Tony try this instead:
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
Exact same results:
Code:
c:\adb>fastboot -i 0x0B05 flash system blob
sending 'system' (800927 KB)...
OKAY [141.843s]
writing 'system'...
FAILED (remote: ()
finished. total time: 143.016s
c:\adb>
Thanks for the advise though.
-Tony
qzmicro said:
I have 2 options for my bootloader when I boot into it, fastboot(USB Icon) and wipe (I think we all know this one.) That's it.
I have no clue how to check the bootloader version without getting into Android. My bootloader doesn't seem to show it on the upper left hand side. Do you know how I can get it?
Click to expand...
Click to collapse
What does your bootloader show? Can you post a photo?
qzmicro said:
I have tried TWRP 3.2.1.0, TWRP 2.6.3.2, CWM 6.0.4.7 and Phil's CWM based recovery for the TF700. So far, none have been able to flash a custom ROM again nor the stock rom when I use recovery GUI for them.
Click to expand...
Click to collapse
So you can still flash different recoveries via fastboot and enter them from the bootloader. That means you should also be able to use "adb shell" to connect to your recovery (when it is running). What does the recovery do when you try to flash a ROM?
If adb shell to your recovery works, exit it again and run these commands to assess your situation:
adb shell ls -l /dev/block > devblock.txt
adb shell dmesg > dmesg.txt
adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
and post the resulting files.
Tony - consider yourself lucky since you caught the attention of two of the best people in this business. Do try to get the info _that was asking for.
I am just trying to clarify things:
Do you remember what stock rom you had before you started this adventure?
It sounds as if you were on pre-JB 4.2 stock rom, then flashed some TWRP version and then a KitKat rom?
If you can flash recoveries, you do have fastboot access to the tablet.
@_that, @sbdags Would it be an option for Tony to flash a CWM recovery that "let him use it" and try to flash sbdags' bootloader/TWRP package?
Tony - don't do anything before you get their advice.
OS
Tony I see that your using a windows PC.. I would highly recommend a Linux Mint OS... There are to many bugs in windows when you are working with low level Android/SoC platforms .... Im not going to say it will fix your issues, but I have seen it do just that for lots of users.... Just let me know if this sound like something for you, when and if your ready, the community with be here to help you out....As always thx lj
I am getting my Linux mint 32-bit OS on my laptop with USB 2.0... again.
Hi guys,
I thank you deeply for your time. I have learned so much trying to un-brick this thing, and yet have had no results. I will be putting together my mint box in just an hour or so and then testing/trying your suggestions. Please check back in an hour or two. Cheers.
-Tony
Here is what my bootloader looks like.
_that said:
What does your bootloader show? Can you post a photo?
Click to expand...
Click to collapse
I have attached the screenshot below.
_that said:
So you can still flash different recoveries via fastboot and enter them from the bootloader. That means you should also be able to use "adb shell" to connect to your recovery (when it is running). What does the recovery do when you try to flash a ROM?
Click to expand...
Click to collapse
It usually fails when it tries to write to the system partition. Please refer to the posts above. It tends to show the FAILED (Remote() error after the write command. My tablet also shows an error saying it could not process the command.
_that said:
If adb shell to your recovery works, exit it again and run these commands to assess your situation:
adb shell ls -l /dev/block > devblock.txt
adb shell dmesg > dmesg.txt
adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
and post the resulting files.
Click to expand...
Click to collapse
Giving it a try now, I'll let you known what happens.
-Tony
I do not recall. At the time I knew, but not anymore.
berndblb said:
Tony - consider yourself lucky since you caught the attention of two of the best people in this business. Do try to get the info _that was asking for.
I am just trying to clarify things:
Do you remember what stock rom you had before you started this adventure?
It sounds as if you were on pre-JB 4.2 stock rom, then flashed some TWRP version and then a KitKat rom?
If you can flash recoveries, you do have fastboot access to the tablet.
@_that, @sbdags Would it be an option for Tony to flash a CWM recovery that "let him use it" and try to flash sbdags' bootloader/TWRP package?
Tony - don't do anything before you get their advice.
Click to expand...
Click to collapse
I do not recall the stock ROM but I DO KNOW I updated to the latest firmware right after I opened it (Big mistake I know... now.) So, I had no choice but to factory unlcok it with the ASUS TOOL. This was for X-Mas two months ago, so I should be the latest I'd immagine.
I did indeed install a kit kat rom on my first attempt and someone told me I forgot to put the proper bootloader prior and that is why I bricked it. So, I think you are dead on about that but can't confirm.
I do indeed... only problem is that I always get a damn ? for my serial number. I do not believe it has ever shown anything but.... though I didn't check until after I had this problem. I do not recall checking prior to using TWRP to install the kit kat rom zip files.
I will wait. i am very greatful to have help, especially from the top dawgs. xP Cheers!
-Tony
I'm on mint 32-bit OS.
lj50036 said:
Tony I see that your using a windows PC.. I would highly recommend a Linux Mint OS... There are to many bugs in windows when you are working with low level Android/SoC platforms .... Im not going to say it will fix your issues, but I have seen it do just that for lots of users.... Just let me know if this sound like something for you, when and if your ready, the community with be here to help you out....As always thx lj
Click to expand...
Click to collapse
I'm on it. I installed mint on my laptop and am using a USB 2.0 interface. I am willing and able to try whatever you might suggest. Cheers.
-Tony
I get a permissions error when using adb shell in CWM recovery...
_that said:
If adb shell to your recovery works, exit it again and run these commands to assess your situation:
adb shell ls -l /dev/block > devblock.txt
adb shell dmesg > dmesg.txt
adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
and post the resulting files.
Click to expand...
Click to collapse
After the first command I received:
Code:
Tonys-Mint antonio # adb shell ls -l /dev/block > devblock.txt
error: insufficient permissions for device
This is the error I get when running the first command you asked for _that. Please advise, thank you! Is this something we can fix? Thanks.
Code:
Tonys-Mint antonio # adb shell ls -l /dev/block > devblock.txt
error: insufficient permissions for device
Tonys-Mint antonio # adb shell dmesg > dmesg.txt
error: insufficient permissions for device
Tonys-Mint antonio # adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
error: insufficient permissions for device
Tonys-Mint antonio #
They all basically told me I have no permissions to my device. Any thoughts? If anyone can/wants to assist outside these forums, please just let me know. I can't offer to pay but I can offer a free pizza at your house no matter where you live! LOL. Cheers fellas!
-Tony
qzmicro said:
I do not recall the stock ROM but I DO KNOW I updated to the latest firmware right after I opened it
Click to expand...
Click to collapse
Your photos show a 9.4.5.x bootloader (and I'm 100% sure about this), which is strange because normally the bootloader is updated together with the stock firmware - so if you updated to the latest firmware, you should also have the latest bootloader (10.6.1.14.x).
qzmicro said:
After the first command I received:
Code:
Tonys-Mint antonio # adb shell ls -l /dev/block > devblock.txt
error: insufficient permissions for device
This is the error I get when running the first command you asked for _that. Please advise, thank you! Is this something we can fix? Thanks.
Click to expand...
Click to collapse
What did the tablet screen show while you ran these commands? The recovery's menu? Which recovery (and version) do you currently have installed?
_that said:
Your photos show a 9.4.5.x bootloader (and I'm 100% sure about this), which is strange because normally the bootloader is updated together with the stock firmware - so if you updated to the latest firmware, you should also have the latest bootloader (10.6.1.14.x).
What did the tablet screen show while you ran these commands? The recovery's menu? Which recovery (and version) do you currently have installed?
Click to expand...
Click to collapse
It just sits there on the main screen as if nothing has happened. Here is a screenie...
-Tony
qzmicro said:
It just sits there on the main screen as if nothing has happened. Here is a screenie...
Click to expand...
Click to collapse
hmm... ok. Try running these commands:
Code:
adb kill-server
adb devices
and post the output.
For the first time EVER, I see the serial number!
_that said:
hmm... ok. Try running these commands:
Code:
adb kill-server
adb devices
and post the output.
Click to expand...
Click to collapse
Here is the output:
Code:
Tonys-Mint antonio # adb kill-server
Tonys-Mint antonio # adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015d2a50692c0a08 recovery
Tonys-Mint antonio #
Please note that this is the first time the device has EVER shown it's serial number since this all started. Usually it just shows a single question mark. Good sign?! Please advise.
-Tony :fingers-crossed:
qzmicro said:
Here is the output:
Code:
Tonys-Mint antonio # adb kill-server
Tonys-Mint antonio # adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015d2a50692c0a08 recovery
Tonys-Mint antonio #
Click to expand...
Click to collapse
That looks good so far. Try
Code:
adb shell
and see if you get a shell prompt from the tablet. If you do, type "exit" to get out again, then run the 3 commands I posted earlier.
_that said:
That looks good so far. Try
Code:
adb shell
and see if you get a shell prompt from the tablet. If you do, type "exit" to get out again, then run the 3 commands I posted earlier.
Click to expand...
Click to collapse
Hello, this is what I get...
Code:
Tonys-Mint antonio # adb shell
~ # adb shell ls -l /dev/block > devblock.txt
/sbin/sh: adb: not found
~ # adb shell dmesg > dmesg.txt
/sbin/sh: adb: not found
~ # adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
/sbin/sh: adb: not found
~ #
I am getting excited, I had not made any leway in over 4 weeks. Those commands seem to have failed though. I kindly await your response. Cheers.
-Tony :cyclops:
qzmicro said:
I am getting excited, I had not made any leway in over 4 weeks. Those commands seem to have failed though. I kindly await your response. Cheers.
Click to expand...
Click to collapse
You forgot to type "exit". But adb shell is working now, that is good. Type "exit" now, then run the 3 commands again, then post the 3 resulting files.
nexus 5
android 4.4.2
bootloader version: HHZ11K
Secure boot: enabled
unlocked
rooted
encrypted (i have set a pattern to unlock)
TWRP 2.6.3.4
Xposed module (not sure which version or if it is relevant at all)
xprivacy (not sure which version or if it is relevant at all)
suddenly, while i was surfing twitter, the phone restarted and attempted to install an update (not sure if it was 4.4.3 or Lollipop).
The phone went into bootloop.
My concern here , for now, is not how to fix it. I just need to retrieve my data (contacts, pics, calendar,...).
I held the power button and volume down to load into bootloader. from there i started TWRP. I was greeted with "please enter your password". I entered my pattern following the below arrangement
1 2 3
4 5 6
7 8 9
after several attempts which always ended with "Password failed. Please try again" i hit "cancel". This took me to the main TWRP screen.
I was worried about my data so i tried to copy everything to my pc through "adb pull sdcard/ C:\test" through terminal but i only got two folders namely "sys" and "tmp" but none of my personal data
In TWRP i touched "mount" to find the following..
"Select Partition to Mount:"
[ ] System
[ ] Cache
[ ] Persist
[ ] firmware
[ ] USB-OTG
below them there is a line that says "Storage: Internal Storage (0 MB)"
below that it says "Decrypt Data". If i touch it, it asks to enter my password. Again, i enter my password and it says password failed.
The log has this:
Updating Partition details...
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
E:Unable to mount ' /cache'
E:Unable to mount ' /cache'
E:Failed to decrypt data.
I think that i need to update TWRP to 2.8.2.0 at least in order to decrypt my data as previous versions don't support decryption and/or pattern passwords. Am i right?
if so, how can i update TWRP to the latest version ?
I tried flashing 2.8.4.0 through fastboot with no luck. I have tried the following during the flashing process:
1) flashed it and then tried starting TWRP immediately.
2) flashed it and then restarted bootloader and then tried starting TWRP
3) flashed it and then started system, which took me into bootloop, shutdown phone
and restart into bootloader then tried starting TWRP.
No matter what i do it always goes back to 2.6.3.4 :crying:
I tried to update it from within TWRP. I pushed TWRP 2.8.4.0 which was in zip format (jjd-openrecovery-twrp-2.8.4.0-hammerhead.zip which i took from this thread ) to the main directory "/". Then inside TWRP i went to install, choose the zip file, swiped right to confirm flash to only get the following:
at the top it says "Zip install complete"
then in like a feedback window this is written:
E : Mount : unable to find partition for patch '/jj
error flashing zip 'jjd-openrecovery-twrp-2.8.
updating partition details...
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
finally at the bottom it says Failed (in red)
no need to say that it is still stuck on 2.6.3.4
Am i heading in the right direction ? if yes how can i update TWRP?
If not, Is there any other way to retrieve my data ?
Is it possible to fix this thing with out a wipe and keep my data intact?
Help plz
have you tried flashing only the cache partition through fastboot?
Thanks for your reply
I downloaded the factory image for nexus 5 from "developers dot google dot com/android/nexus/images#hammerhead" (version 4.4.2 (KOT49H) )
I kept extracting the zip file until I arrived at cache.img
copied it to the folder fastboot.exe is located in
run the command
Code:
fastboot flash cache cache.img
through terminal while in fastboot mode
i got the following:
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (13348 KB)...
OKAY [ 0.671s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.983s
I started the phone, it passed by the bootloop but then i got a message that says:
Unfortunately, google search has stopped
Unfortunately, the process com.google.process.gapps has stopped
Unfortunately, Google play has stopped
and couple of other similar messages
then i'm greeted with android setup screen (as if I'm running the phone for the first time; choosing language, time ...etc
while I'm in the middle of the setup process, the phone restarts. and it keeps happening again and again
Is there anything else I can do ?
crobh said:
Thanks for your reply
I downloaded the factory image for nexus 5 from "developers dot google dot com/android/nexus/images#hammerhead" (version 4.4.2 (KOT49H) )
I kept extracting the zip file until I arrived at cache.img
copied it to the folder fastboot.exe is located in
run the command
Code:
fastboot flash cache cache.img
through terminal while in fastboot mode
i got the following:
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (13348 KB)...
OKAY [ 0.671s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.983s
I started the phone, it passed by the bootloop but then i got a message that says:
Unfortunately, google search has stopped
Unfortunately, the process com.google.process.gapps has stopped
Unfortunately, Google play has stopped
and couple of other similar messages
then i'm greeted with android setup screen (as if I'm running the phone for the first time; choosing language, time ...etc
while I'm in the middle of the setup process, the phone restarts. and it keeps happening again and again
Is there anything else I can do ?
Click to expand...
Click to collapse
That means it's borked. You have to RMA it with Google or send it to LG repair.
BirchBarlow said:
That means it's borked. You have to RMA it with Google or send it to LG repair.
Click to expand...
Click to collapse
I have bought it from google directly but I live overseas.
Tried the local LG maintenance center, they guy there didn't seem knowledgeable on the issue. He said he can try formating it and it might work again but has no idea of recovering the pics and other personal data.
I'm starting to lose hope :crying:
new attempt
I tried wiping cache from twrp and then starting the system. this happen:
Google logo for few minutes
then the four circles merging into white circle animation
then three message pops up,one by one, saying
"Android us upgrading" at the top in blue (this stays in all three messages)
and below it, it says
starting apps
upgrading contacts database
finishing boot
and then it returns to the four circles and then the messages again and again and again
Try flashing just the system.img.
Wakamatsu said:
Try flashing just the system.img.
Click to expand...
Click to collapse
So i extracted System.img from 4.4.2 (KOT49H) and then through terminal while in fastboot i wrote
Code:
fastboot flash system system.img
and the result was..
erasing 'system'...
OKAY [ 0.140s]
sending 'system' (702500 KB)...
OKAY [ 24.866s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 25.178s
What could be the reason for this ?
Sounds like yet another corrupted emmc. The usual test for this is to try locking the bootloader. If nothing happens and it reverts to unlocked it's dead. You could try the lg service but I have no idea if they would accept a warranty /rma
Sent from my Nexus 5 using XDA Free mobile app
This is a guide on rooting the new Chuwi Vi7 Phablet as a result of spending lots of hours on this proyect with the hope that others find it useful.
This is work in progress, do not attempt it if you are not ready to flash back the original rom in case you soft brick your Chuwi
PREREQUISITES:
A) For LINUX users:generally install the android-tools package so you have the adb command available.
In Manjaro linux and Arch Linux just do
Code:
sudo pacman -Sy android-tools
In Ubuntu probably
Code:
apt-get update && apt-get install android-tools
A) windows users would need to (presumibly; not tested)
For WINDOWS users:
install the intel drivers for android and user the attached adb.exe with dm-verity support
Most ADB.EXE do not have dm-verity. Try installing Java (prerequisite to install Android Studio) and installed Android Studio (download full package, but only install SDK part).
The file reported to work fine is android-studio-bundle-141.2117773-windows.exe
The ADB version is 1,011,200 bytes with date of 02/14/2015 07:12 PM.
1) (Recommended) Apply the over the air update; you know you have it when you can see the Google Playstore installed.
2) Connect your Chuwi Vi7 to your PC with a microusb cable
First we need the ability to write to the system partition so in order to do this, run these commands:
Code:
adb root
adb disable-verity
adb reboot
wait 30 seconds now we are going to do a backup of SYSTEM and DATA just in case
(if you are in Windows remove the ./ before system_068 and data_069)
This will take some minutes
Code:
adb boot recovery
Wait a few seconds until you are in the stock recovery
Code:
adb root
adb pull /dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068 ./system_068
adb pull /dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069 ./data_069
adb reboot
3) unzip the attached file and transfer all the individual files contained to the Chuwi´s /data/local/tmp folder
Code:
adb root
# Now we are going to push the whole folder contained in the archive we just extracted
adb push RootChuwiVi7 /data/local/tmp/
4) Now from a terminal run this command:
Code:
adb shell /system/bin/sh -x /data/local/tmp/vi7root
alternatively run
Code:
./rootnow
and that´s it!
Now open Root Verifier (it´s an app) to check if your Chuwi is rooted...
If you like my work dont forget to press the THANKS button and/or donate
TIPS: If you do not get prompted to allow root access by superSU, do adb root from the command line
If you need to flash the phablet here you can download the rom and flashing tool:
https://mega.nz/#!QVFCGDCa!oz4jXrxdsE6pJ4rVt4AlbUHN-VY9NwTF7SNfeir0mSk
Password: jopasaps
You need to install the intel drivers and the flash drivers and run Flash E2, load all the rom files, click on custom order, tick all the boxes, select generic usb, click on NEXT, turn off the phablet, then click on USB1 and very very quickly plug the phablet to your PC while holding VOLUME- you will see some activity in the screen and within 1 minute it will be ready.
If it is ready within 5 seconds then you did not load all the files. Depending on why your phablet is soft bricked it may be enough to flash only some of the files.
KNOWN ISSUES: Open Source superuser by koush does not work as the su binary needs recompiling. We are therefore using SuperSU by chain, I suggest you don't update SuperSU in the Play Store.
TROUBLESHOOTING: the command adb reboot ptest_clear is reported to work with soft bricked devices (put here as a courtesy, not needed in principle)
UPDATE: Download this file to update your SYSTEM partition to the latest version of the firmware, including some debloating and with English as default language. This update is done from recovery, through an adb push command
Thanks for this! I'm trying but can't get it to work. Running the script generates errors and I've boiled it down to doing the permissions -- I can't mount /system as RW no matter what syntax I've tried. I'm in the ADB shell and running under SU (#). Also tried mounting explicit as /dev/block/dm-0 but it still only comes back as "mount: Read-only file system".
Try again from the beginning, you will be able to mount read/write system now...
ALSO VERY IMPORTANT, download the new attachment and use instead ...
Thanks, I tried to disable verity before and it didn't work. I'll try again this time.
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
Can you by any chance post your ADB.exe which has support for disable-verity command?
My adb is simple to install...
1) Install Manjaro linux
2) Run: pacman -Sy android-tools
and... that´s it! you get adb and fastboot
and no need to install android drivers
the sequence then I use to be able to write to the system partition on the Chuwi Vi7 is:
adb root
adb disable-verity (that needs to be done only once)
adb remount
Let me know whether it works in windows ...
TheAndroidGeek said:
Thanks, I tried to disable verity before and it didn't work. I'll try again this time.
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
Can you by any chance post your ADB.exe which has support for disable-verity command?
Click to expand...
Click to collapse
casacristo said:
My adb is simple to install...
1) Install Manjaro linux
2) Run: pacman -Sy android-tools
and... that´s it! you get adb and fastboot
and no need to install android drivers
the sequence then I use to be able to write to the system partition on the Chuwi Vi7 is:
adb root
adb disable-verity (that needs to be done only once)
adb remount
Let me know whether it works in windows ...
Click to expand...
Click to collapse
For WINDOWS users:
I had various flavors of ADB.EXE and none of them had the dm-verity. Finally installed Java (prerequisite to install Android Studio) and installed Android Studio (download full package, but only install SDK part).
The file I used as android-studio-bundle-141.2117773-windows.exe
The ADB version is 1,011,200 bytes with date of 02/14/2015 07:12 PM.
Now rooted... but not sure what to do with this very low spec tablet I have so many other tablets (Onda, Teclast, Acer, etc).
Thanks casacristo!
Yeoh Master Shifu Arturo, its been awhile, how are you, only today notice your thread here, sorry for a little OT...
i own the first variance of x3(c3130), damn intel for making it so hard to root... :laugh:
Code:
[[email protected] ~]$ adb root
[COLOR="blue"]adbd cannot run as root in production builds[/COLOR]
[[email protected] ~]$ adb disable-verity
[COLOR="blue"]error: closed[/COLOR]
i was trying a different approach, root via recovery & i wonder if you have tried the FlsTool, can't figured out the correct commands to repack back ported custom recoveries...
Code:
[URL="https://github.com/android-ia/vendor_intel_build/blob/master/FlsTool/FlsTool"]FlsTool[/URL]
FlsTool v.1.21
This tool can do several different operations of FLS files.
Use the 'Action' option to select to required operation.
Actions:
-p [ --pack ] Packing multiple FLS files into one
-i [ --inject ] Inject NVM, Certificates or Security into FLS file
-x [ --extract ] Extract all image parts from the FLS file(s)
--extract-fls Extract embedded files from the FLS file(s)
--extract-prg Extract PRG file
-b [ --to-bin ] Convert a single Hex file to binary file
--hex-to-fls Create an Fls from a Prg file
--sign Formerly known as FlsSign
--to-fls2 [ arg ] Force output file format to Fls2
--to-fls3 [ arg ] Force output file format to Fls3
-d [ --dump ] Dump the meta data of an FLS file.
--sec-pack Dump all SecPack data of an FLS file.
HexToFls options:
--prg arg Choose a PRG file to create the Fls from
--psi arg Add a PSI to the Fls file (replaces if '-r' option)
--ebl arg Add an EBL to the Fls file (replaces if '-r' option)
--meta arg Inject any meta file to the Fls file (Equal to --version or -v in HexToFls)
--xml arg Add an XML file to the Fls file (replaces if '-r' option)
--zip arg Add a ZIP file to the Fls file (replaces if '-r' option)
--script arg Add a Script file to the Fls file (replaces if '-r' option)
--tag arg Specifies the memory region tag to insert the input file (replaces if '-r' option)
Inject options:
-n [ --nvm-path ] arg Path to the NVM input files
Generic Options:
-o [ --output ] arg Output path
-r [ --replace ] [ arg ] Defaults to replace when trying to add a section which is already existing
-v [ --verbose ] [ arg ] Set verbosity
--prompt [ arg ] Prompt before quitting
--version Show the version of this tool
-h [ --help ] Show command line help
Please specify an input file
@jasonx3
try this file:
https://mega.co.nz/#!UMVwTQIR!w04Pidyd2TRDLyWnqMfCL_qxXRtJmapD0UFmp0hQnx4
it is a full rom with root and gapps, with a script that flashes it (provided
you have a root shell)
@Vadim Shved
Can you be more specific?
I use link2sd without problems to convert apps to system apps.
do this:
adb root
adb remount
what is the output?
Hello Yuweng, good to see you, yes it has been a while... I don´t change hardware very frequently nowadays and not always I feel I can make a substantial contribution to the community
I have not used FlsTool but I have something to offer you....
Download this file:
https://mega.co.nz/#!UMVwTQIR!w04Pidyd2TRDLyWnqMfCL_qxXRtJmapD0UFmp0hQnx4
It is a complete dd copy of my system partition with a script that will verify the md5sum is correct and flash it.
I think this should work fine if you can be root though a recovery.
This system image has already root, busybox, google updates integrated
yuweng said:
Yeoh Master Shifu Arturo, its been awhile, how are you, only today notice your thread here, sorry for a little OT...
i own the first variance of x3(c3130), damn intel for making it so hard to root... :laugh:
Code:
[[email protected] ~]$ adb root
[COLOR="blue"]adbd cannot run as root in production builds[/COLOR]
[[email protected] ~]$ adb disable-verity
[COLOR="blue"]error: closed[/COLOR]
i was trying a different approach, root via recovery & i wonder if you have tried the FlsTool, can't figured out the correct commands to repack back ported custom recoveries...
Code:
[URL="https://github.com/android-ia/vendor_intel_build/blob/master/FlsTool/FlsTool"]FlsTool[/URL]
FlsTool v.1.21
This tool can do several different operations of FLS files.
Use the 'Action' option to select to required operation.
Actions:
-p [ --pack ] Packing multiple FLS files into one
-i [ --inject ] Inject NVM, Certificates or Security into FLS file
-x [ --extract ] Extract all image parts from the FLS file(s)
--extract-fls Extract embedded files from the FLS file(s)
--extract-prg Extract PRG file
-b [ --to-bin ] Convert a single Hex file to binary file
--hex-to-fls Create an Fls from a Prg file
--sign Formerly known as FlsSign
--to-fls2 [ arg ] Force output file format to Fls2
--to-fls3 [ arg ] Force output file format to Fls3
-d [ --dump ] Dump the meta data of an FLS file.
--sec-pack Dump all SecPack data of an FLS file.
HexToFls options:
--prg arg Choose a PRG file to create the Fls from
--psi arg Add a PSI to the Fls file (replaces if '-r' option)
--ebl arg Add an EBL to the Fls file (replaces if '-r' option)
--meta arg Inject any meta file to the Fls file (Equal to --version or -v in HexToFls)
--xml arg Add an XML file to the Fls file (replaces if '-r' option)
--zip arg Add a ZIP file to the Fls file (replaces if '-r' option)
--script arg Add a Script file to the Fls file (replaces if '-r' option)
--tag arg Specifies the memory region tag to insert the input file (replaces if '-r' option)
Inject options:
-n [ --nvm-path ] arg Path to the NVM input files
Generic Options:
-o [ --output ] arg Output path
-r [ --replace ] [ arg ] Defaults to replace when trying to add a section which is already existing
-v [ --verbose ] [ arg ] Set verbosity
--prompt [ arg ] Prompt before quitting
--version Show the version of this tool
-h [ --help ] Show command line help
Please specify an input file
Click to expand...
Click to collapse
Mine is a dual-sim c3130, ro.secure=1, ro.adb.secure=1, no adb while at stock 3e recovery, fastboot flash recovery twrp-recovery.img doesn't work, non of the existing exploit rooting software works, in fact, nothing works on this piece of sh#t but its so cheap... :laugh:
Got mine for less than a month, its a rebrand of Teclast X70, only last week the oem release the firmware, thats where i found out about FlsTool, its actually also available on Windows, i'll leave the linux copy here for everyone to explore...
Thanks! and by all means let us know if you succeed...
yuweng said:
Mine is a dual-sim c3130, ro.secure=1, ro.adb.secure=1, no adb while at stock 3e recovery, fastboot flash recovery twrp-recovery.img doesn't work, non of the existing exploit rooting software works, in fact, nothing works on this piece of sh#t but its so cheap... :laugh:
Got mine for less than a month, its a rebrand of Teclast X70, only last week the oem release the firmware, thats where i found out about FlsTool, its actually also available on Windows, i'll leave the linux copy here for everyone to explore...
Click to expand...
Click to collapse
casacristo said:
@Vadim Shved
Can you be more specific?
I use link2sd without problems to convert apps to system apps.
do this:
adb root
adb remount
what is the output?
Click to expand...
Click to collapse
I did everything from your tutorial. Root checker says that root is present. BUT! I cant do opearations with system partiotion. I tried to: 1)adb root 2)adb remount. After that in command promt I see that remount succeeded. Root checker say that root is present... But I still cant do anything. System partiotion cant be r/w
Edit: Sorry, but I thing that it is a problem of some apps that are not ready for android 5.1.x
Is there original rom available anywhere with tools to flash it? (got my vi7 in a state where it show only first "chuwi" logo, no "intel" logo - just black screen (but PC for example sees ADB interface; unfortunately "no permission"). I'm hoping that's only software problem.
Edit: CRANE_EVB firmware (seems to be some vi7 compatible device, not vi7 itself) finally worked. Required that I force (in devices manager) "intel usb driver for android devices" to be used for my detected chuwi vi7 "adb interface", then "adb.exe reboot ptest_clear" and it starts, no more black screen, no more "PTEST VER 1.41" problem etc.
Anyway still looking for original vi7 rom (not that crane_evb thing).
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Updates - 01-Sept-2015
Huge Thanks to best98 for carrying out numerous of tests... :good:
Conclusion : No point to further develop custom recoveries, after unlocking bootloader, vi7 will refuse to boot unless you press Vol+ for 3 seconds then only it will boot up normally, no one would wanna do that...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
best98 said:
Hi
So, I tried to flash stock 3e recovery..
Code:
"Warning: Chip mismatch. HW is [Sofia_3G_R] SW expects [Sofia_3G]
Device synchronized.
Using: Faster CRC, Writing all blocks , Skip data CRC , Skip protocol CRC
Start downloading item 'CUST:recovery.fls'' from file 'C:\Android\Chuwi_V7\stock-3e-recovery.fls''.
Checksum OK (0x0000)
Process time was 656 msec.
Total time was 1359 msec.
Channel 1 is succesfully closed."
Still boots with the green/red/black screen..
Did the fastboot eom lock
Code:
PS C:\> fastboot oem lock
...
(bootloader) Please confirm the device state action using the UI.
(bootloader) got key event 1
(bootloader) EV_DOWN received
(bootloader) got key event 2
(bootloader) EV_POWER received
(bootloader) Userdata erase required, this can take a while...
OKAY [ 11.506s]
finished. total time: 11.511s
Now, got the bootloop.. -> flashing the whole firmware : boots ok.
adb reboot fastboot
fastboot oem unlock
Code:
PS C:\> fastboot oem unlock
...
(bootloader) Please confirm the device state action using the UI.
(bootloader) got key event 1
(bootloader) EV_DOWN received
(bootloader) got key event 2
(bootloader) EV_POWER received
(bootloader) Userdata erase required, this can take a while...
OKAY [ 11.299s]
finished. total time: 11.300s
Black/green/red screen..
fastboot format cache + fastboot format data = same Black/green/red screen..
I hit 'Vol+' it goes forward.. shows Intel logo and boots..
Pierrick
Click to expand...
Click to collapse
fastboot oem unlock confirm
gets
< waiting for device >
and nothing else happens
yuweng said:
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Click to expand...
Click to collapse
Is it possible to overclock this device? 900mhz.... it sucks.
Hmm.. I could try.. nothing to loose, but can't get the communication to work.
I unlocked the bootloader throug the Developer Option menu. Is it enough ?
yuweng said:
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Click to expand...
Click to collapse
Thank You so much for participating in Development... :good:
Fyi, OP can't test b'cos he drop & break his vi7 while i'm having a different variance of x3...
First you need to unlock the bootloader & if you didn't then it will brick your vi7 but then again, you guys have the firmware to unbrick it...
Steps
If you're using Windows then download fastboot from here, if you're using linux then follow tips from OP
To reboot to fastboot => adb reboot fastboot -> There is no intel Droidboot, only green distorted screen but fastboot command works
To unlock bootloader -> fastboot oem unlock then follow PC on-screen for instructions & for formatting data & cache partition too. Mine have to issue the command fastboot oem unlock confirm
After this to reboot -> fastboot reboot
At PC, setup intel USB driver -> right click -> Run As Administrator
Start FlsTool -> Switch off your vi7 -> wait awhile -> Click at Next -> Click Start USB1 -> Plugin your vi7 & it'll download
After boot up Android -> adb reboot recovery & if TWRP doesn't boot then unplug USB, press & hold Power for 10 seconds & it power off then follow the same procedure to reinstall back stock 3e recovery
For more info, refer to the FlsTool attach pdf file for details
Additional info
At the Russian forum mentioned you'll need to check the option Manual (no auto start) while on my x3 with default Auto Start works fine...
Hi
Not changing the bootloader butusing a mix of the OP script and Chinese tablet -Intel Root- script worked.
One of the big deal was to have the ADB compatibility with "disable-verity" which is the last release.
Now, I will try to focus on TWRP.. but FLS with COM to USB mapping makes it a little bit complicated !
Pierrick
OK.. just tried this, and now, I have a green screen ..
Rolling back the 3e recovery worked but the result is still showing me, black/green and red lines.
Right now, tablet does not boot anymore, except those lines in green/black and red.. where no text is written - looks like locked inl in fastboot.
Willing to hear from you to get back the control of the tablet
Here are the settings I used - thumbnail !
BTW - attaching adb.exe that handles the disable-verity
yuweng said:
Thank You so much for participating in Development... :good:
Fyi, OP can't test b'cos he drop & break his vi7 while i'm having a different variance of x3...
First you need to unlock the bootloader & if you didn't then it will brick your vi7 but then again, you guys have the firmware to unbrick it...
Steps
If you're using Windows then download fastboot from here, if you're using linux then follow tips from OP
To reboot to fastboot => adb reboot fastboot -> There is no intel Droidboot, only green distorted screen but fastboot command works
To unlock bootloader -> fastboot oem unlock then follow PC on-screen for instructions & for formatting data & cache partition too. Mine have to issue the command fastboot oem unlock confirm
After this to reboot -> fastboot reboot
At PC, setup intel USB driver -> right click -> Run As Administrator
Start FlsTool -> Switch off your vi7 -> wait awhile -> Click at Next -> Click Start USB1 -> Plugin your vi7 & it'll download
After boot up Android -> adb reboot recovery & if TWRP doesn't boot then unplug USB, press & hold Power for 10 seconds & it power off then follow the same procedure to reinstall back stock 3e recovery
For more info, refer to the FlsTool attach pdf file for details
Additional info
At the Russian forum mentioned you'll need to check the option Manual (no auto start) while on my x3 with default Auto Start works fine...
Click to expand...
Click to collapse