Related
Hey so this issue is actually solved. If you want to see the process that I went through to get to the solution, please do! Its not that hard, I promise. Maybe a little stressful, but totally doable. Cheers!
----------------------------------------------------------------
I'm currently stumped on how to fix this issue that I'm currently having with my HTC Rezound at the moment. I did not buy this from any Verizon retailer, I bought it online in 2012. Anyway, the only issue that I've had the past few months is just that my battery kept dying super quickly and that my phone would randomly shut off after flashing Liquid Smooth ROM on my phone. I originally live in California but I moved to Spain, so any option of "take it to a retailer" or "take it to a cellphone repair shop" is not practical since NOBODY in Granada has ever heard of this phone.
The last time I had my phone operational was when I was using Mobile Data to chat with one of my friends on an app when it died, as usual. This time, I wasn't home to immediately plug it into the charger. One other thing I'd like to point out is that the number one reason why I think my battery kept dying so quickly is that while I was in Morocco, I was using an adapter to charge my phone. Maybe the difference in voltage fried my battery, not sure.
Anyway, I was out for at least 3-4 hours before I finally got home to put it on the charger. I plugged it in and went to bed without even looking at my phone. Woke up the next morning to power it up to find that not even the orange light is on (or green when fully charged). I unplug it, plug it back in and nothing happens. I take out my battery, keep it out for a couple hours and put it back in. I hold the Power button until the phone vibrates, screen turns on with the green HTC logo on a white screen, and then turns off. I take out the battery a couple more times and still same thing. I decide to leave the battery out for 2 hours and then put it back into the phone and directly to charge. The orange light turns on for about 3-5 seconds before turning off.
If I try to push the power button, nothing happens unless I take out the battery again. So I leave the battery to charge but then my phone started to get a little warm. Instead I just disconnect and leave the battery out of the phone for about 3 weeks until I had 2 spare new batteries shipped to me here in Spain. Once I got the batteries, I tried once again to get my phone working by replacing the batteries. Orange light comes on for 3-5 seconds before going out and its the same thing as before. I plug it into my laptop, use the CMD "adb devices" and I get nothing listed or "error: device not found". I can only boot into hboot by using Power + Down Volume and thats about it. By the way, its S-OFF and rooted with a custom ROM (Liquid Smooth) and the recovery should be Amon Ra.
If I get to fastboot/hboot and I select Factory Reset, Recovery, or Reboot, the screen dims, vibrates a bit and flashes the HTC logo on a white screen for 3 seconds before turning off. As of now, I can't connect to my phone through the PC as it doesn't even read via USB port, HTC Sync doesn't read, and I can't reach my phone through CMD prompt. Does anyone have any information on how I could fix this? And even though I have read most articles about the orange light thing and clockworks recovery, I'm still open to any/all solutions.
Update #1
Since I have not gotten any help from any community members or from other people, I decided to pursue this on my own to the best of my abilities. I decided to start looking up different articles with the same symptoms that I have and to see what the solutions were. Long story short, I combined a few solutions and one of the things some people did was just reinstall stock ROM altogether. For now, I am happy to say that I can access my phone via Command Prompt, but ONLY with "fastboot" commands. I came to this realization when I was looking up how to install stock ROM when one of the commands was to put "fastboot reboot-bootloader" and I happily had much success. Just make sure you're in FASTBOOT USB or else it won't work. I also ended up reinstalling all my HTC Drives and HTC Sync. At the moment, I cannot access internal memory via USB nor connect to HTC Sync. Also, to see what other commands that are available to your disposal, you can type "fastboot help".
Update #2
Since the last post, I've been looking around. Found out that the best solution would be to flash a stock RUU onto the phone. Requirements before flash would be to erase everything but the only command I can get to erase is with "fastboot earse cache" and thats about it. Everything else is unsuccessful. Anyway, instead of just going straight to downloading and flashing stock RUU, I accidentally decided to try following a procedure I read step by step by first locking bootloader with the command "fastboot oem lock" command and phone immediately shuts off. I try to power on again but just does same as before: boots to green HTC logo on white, stays on a for a few seconds, and turns off. This time, though, without the bootloader coming up. I believe I have bricked my phone.
Can you still get to Fastboot? If so, unlock again, and then download the latest TWRP recovery, and try:
fastboot boot recovery.img
replace recovery.img with the name of the recovery image file for TWRP.
Once that is done, look at your mounts and see if you can access any partitions.
Update #3
acejavelin said:
Can you still get to Fastboot? If so, unlock again, and then download the latest TWRP recovery, and try:
fastboot boot recovery.img
replace recovery.img with the name of the recovery image file for TWRP.
Once that is done, look at your mounts and see if you can access any partitions.
Click to expand...
Click to collapse
Alright so right now I am EXTREMELY happy!!! Thank you so much for the advice. My phone happened to not get into fastboot anymore for some reason after I thought I bricked it. The final attempt I made before going to bed that night was to put my Micro SD into my phone and attempt to get into fastboot one last time and by some miracle my phone decided to. This is the steps I took to get my phone back operational so please excuse the length. At the moment, its not completely solved until I get my phone 100% operational, but this is what I have so far. I listed a few notes before I started so here goes.
Update #3:
HTC Rezound 2014:
- S-OFF and rooted with Liquid Smooth ROM and Amon Ra recovery
- fastboot oem LOCKED (no bootloader access available)
- batteries all low powered, 1 fried (3 total)
- when plugged, charging light turns on for 3-5 seconds and turns off without charging battery or
allowing phone to power back on; requires battery pull to restart process
- Power + volume normally takes to bootloader; recovery, factory reset, and reboot option fail
- when attempting to boot, phone will vibrate, power on to green HTC logo on white screen and then
turns off to black
- any attempts to turn on phone result in said description and requires battery pull after each attempt
Current issues:
Batteries are not fully charged
Cannot access bootloader because of last command in console, "fastboot oem lock"
PC cannot read devices despite drivers installed and fully working USB cord
Possible causes:
- Extra batteries just aren't fully charged to allow phone to fully boot
- System files are corrupted; no recovery, no boot.img, no OS; nothing for the phone to read to start up
Attempt 1:
- Plug phone with battery inside and cover off
- Clear memory off SD card
- Remove battery and insert SD Card
- Note: Battery has little to no power
- Plug into USB cord connected to computer
- Before orange light comes on, hold down Power + Down Volume
- Failed; repeat (unplug from phone, battery pull and reinsert)
- Attempt to leave battery to charge for 8 minutes via USB
- Charge attempt failed; orange light turns on for 3 seconds before turning off
Attempt 2:
- Remove phone cover, take out battery and reinsert
- Hold Power + Down Volume and go into Fastboot USB
- If successful, plug into PC via USB cable
- Open console (Shift + Right Click in folder AndroidSDK\platform-tools)
- For list of fastboot commands, type in the console (which should read slike C:\AndroidSDK\platform-tools\) "fastboot help" without quotations
- To make sure you are connected, type the command "fastboot reboot-bootloader"
- If the phone reboots into FASTBOOT USB after the command, then you're good
- Type in the command "fastboot devices" to make sure your devices can be read by your computer (should show up like HT18BY892363 fastboot)
- Since the last thing I did on my phone was "fastboot oem lock", use the command "fastboot oem unlock" and hope for success
- Command prompt will read something like:
...
<bootloader> [ERR] Command error !!!
OKAY [ 0.014s ]
finished. total time: 0.017s
- Type into command "fastboot oem get_identifier_token"
- Submit Identifier Token to HTC Dev (need to create an account)
- Download file and save in platform-tools folder with the adb.exe and fastboot.exe files
- Type "fastboot flash unlocktoken Unlock_code.bin" into console
- Select "Yes" option and phone will reboot as follows: vibrates, shows HTC logo on white screen for 3 seconds and turns off
- Unplug phone from USB, take out battery and reinsert
- Hold Power + Down Volume and boot into FASTBOOT USB; should read "*** UNLOCKED ***" at top of screen
- Using TWRP 2.8.0.1F, extract "recovery.img" into "platform-tools" folder
- Type command "fastboot boot recovery.img" and profit!
Glad you got it working!
acejavelin said:
Glad you got it working!
Click to expand...
Click to collapse
I actually have another issue now. I have managed to install TWRP onto my phone but when I attempt to flash a RUU I downloaded, I get this error:
Installing '/external_sd/PH98IMG.zip' . . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/'external_sd/PH98IMG.zip'
Error flashing zip '/external_sd/PH98IMG.zip'
Updating partition details . . .
E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/devlog
E: Unable to mount storage.
Your partition table is corrupted... Being S-Off you have an option, you need to run an EXE RUU, not flash a ph98img... I think the last one was 3.12.605.12 and you run it from a Windows PC with the phone in download mode... If that doesn't work only a JTAG programming can fix it, if it can be fixed. Once you get to this point that all partitions are not mountable, it is tough to recover, if it can be done at all. You have about a 50/50 chance at best.
acejavelin said:
Your partition table is corrupted... Being S-Off you have an option, you need to run an EXE RUU, not flash a ph98img... I think the last one was 3.12.605.12 and you run it from a Windows PC with the phone in download mode... If that doesn't work only a JTAG programming can fix it, if it can be fixed. Once you get to this point that all partitions are not mountable, it is tough to recover, if it can be done at all. You have about a 50/50 chance at best.
Click to expand...
Click to collapse
So how would I go about finding an EXE RUU? Do I just google "HTC Rezound 3.12.605.12 RUU exe"? And I apologize for the noobish questions, this is actually my first time getting this bad with my Rezound haha. I found this article (although it isn't associated with the phone) and was wondering if I should give it a try or not. http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
shock_and_awe said:
...
E: Unable to mount '/system' <<<<<< THIS is the real problem
E: Unable to mount '/devlog
Click to expand...
Click to collapse
Without /system being mountable, or even formatable, there isn't much you can do..
Since ALL partitions are unmountable it likely means the PIT (Partition Information Table) for the internal 16GB storage area is corrupted and it needs to be recreated.
This MAY be fixable manually if you have a Linux machine, and understand the partitioning of THIS device... The Linux part I have no issue with, but I no longer own the is device and do not have a copy of the partition table to help you repartition it.
Honestly, for all the work involved, why not just grab a cheap phone online and use it? I mean you can get a Galaxy Nexus, a replacement Rezound, or a handful of other LTE devices for under $100 on swappa.com
acejavelin said:
Without /system being mountable, or even formatable, there isn't much you can do..
Since ALL partitions are unmountable it likely means the PIT (Partition Information Table) for the internal 16GB storage area is corrupted and it needs to be recreated.
This MAY be fixable manually if you have a Linux machine, and understand the partitioning of THIS device... The Linux part I have no issue with, but I no longer own the is device and do not have a copy of the partition table to help you repartition it.
Honestly, for all the work involved, why not just grab a cheap phone online and use it? I mean you can get a Galaxy Nexus, a replacement Rezound, or a handful of other LTE devices for under $100 on swappa.com
Click to expand...
Click to collapse
I see what you mean. Honestly I would get another phone if I could but I'm no longer living in the States, I'm studying in Spain. Shipping is super expensive so I'll have to go local or figure something out. Its the only phone I have at the moment but I'll most likely just get another phone for cheap. I really appreciate the help and the advice though. If anything, this will be my "side project" to work on when I'm SUPER bored and fix it for sh**s and giggles.
shock_and_awe said:
I see what you mean. Honestly I would get another phone if I could but I'm no longer living in the States, I'm studying in Spain. Shipping is super expensive so I'll have to go local or figure something out. Its the only phone I have at the moment but I'll most likely just get another phone for cheap. I really appreciate the help and the advice though. If anything, this will be my "side project" to work on when I'm SUPER bored and fix it for sh**s and giggles.
Click to expand...
Click to collapse
Spain has mostly GSM service, correct? Why not look into cheap devices locally? Amazon.es has several devices under 200 euros, Moto G, Moto E (89 euro), LG G2 mini, Xiaomi Red Rice, BQ Aquaris E5, etc... Or local classifieds online.
Update #4
SOLVED!!!
The solution (as it appears to be on a few success stories) is to completely install an Official Stock RUU. You just have to be content with losing ALL your data (if there was anything to save in the first places). What I ended up doing was using a microSD adapter this whole time and I would not have been able to get my phone back without it. This is what I did (following the installation of TWRP Recovery):
Official Stock RUU:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Update #4 (Final):
For this process I used a microSD adapter, in which I plugged into my laptop and put the required files in there.
- Download file from Android Police and rename to "PH98IMG.zip"
- Using your storage device (whatever way you choose just do this) put the .zip file onto the SD card
- Place the SD card into your phone and boot into HBOOT using Power + Down Volume
- Wait a few minutes until the PH98IMG.zip is finished loading and press Volume Up for "Yes" when asked "Do you want to start update?"
- After about 10-15 minutes, the phone will ask you to reboot the system
- Profit!!!
- Don't forget to remove the PH98IMG.zip file from your SD card or else every time you boot into HBOOT, it will reload the file
acejavelin said:
Spain has mostly GSM service, correct? Why not look into cheap devices locally? Amazon.es has several devices under 200 euros, Moto G, Moto E (89 euro), LG G2 mini, Xiaomi Red Rice, BQ Aquaris E5, etc... Or local classifieds online.
Click to expand...
Click to collapse
I actually JUST fixed my phone haha but yeah there are a few local mobile phone stores here (like Phone House) where they sell discounted phones. I appreciate all the help and thank you so much for everything. Above all else, thank you for sticking through with this post
Glad its working!
I have a Nexus 9 Wi-Fi model, my PC runs Windows 8.1, and I am not new to rooting and custom ROMs. I attempted to install the M dev preview to the tablet following the instructions on Google's site. In the process, my console window showed one of the instances of "sending sparse 'system'" had FAILED. Now the device will not boot. It is stuck on the white Google logo splash screen. ADB does not recognize it, although it does appear in Windows Device Manager as "MTP USB Device". When I attempt to turn the device off or reboot it using any combination of power and volume keys, the screen will go blank for a few seconds and then return to the Google logo. I cannot turn the device off.
I've never seen this before, even with a failed flash... it's supposedly just the system partition that failed, anyway. Any ideas how I can break free of this?
EDIT: I ended up locating this post. If I hold the power button down until the screen turns off and then immediately press and hold power+voldn, it will launch the bootloader.
I've no experience with flashing M. But I have a suspicion that you flash of the system.img failed because of an obsolete fastboot on your PC. I'd suggest starting by updating your Android SDK. Then you can try fastboot flashing the M system.img again. Or fastboot flash the stock 5.1.1/factory image to return to stock.
soft bricked is all it is.
Made sure I had the latest Fastboot, ADB
Rebooted into Fastboot
Ran the Flash All batch file and it failed to install the System
I found instructions on flashing manually this from what was post is very common.
You extract all files, flash the boot, reset, and flash all the others.
Do a Google search it was easy enough to find.
I'd appropriate it, if anyone would be willing to help me out with my issue.
I have a LG G2 D801, 32GB.
Had it ROOTED, TWRP Recovery, and Lineage OS 14.1 running perfectly just fine. Until I recently tried to Flash Lineage OS 15.1, which then caused my phone to completely go into a black screen with a dead Android Robot having a exclamation point in a red triangle coming out of it's belly.
Yes, I'm able to get into: Android System Recovery <3e> LRXX22G
- Tried, Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Tried, Wipe Cache Partition, then Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Tried, Wipe Data/Factory Reset, then Wipe Cache Partition, then Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Last but not least, leaving me with the only real option I have left to help fix my phone is the, Apply Update From ADB. (Yes, I tried that one too) Which is why I need your help!
Here's a quick scenario of what happens after trying that last option. (Apply Update From ADB)
-Basically my phone then asks me to ADB Sideload files.
-I connect my phone to my PC. (Windows 7, x64)
-Check my Device Manager to see if it's fully connected, but my D801 connects each time under SAMSUNG Android Phone - AndroidNet Sooner Single ADB Interface. (which I know has to be wrong)
-I go into my CMD Prompt, to access my installed ADB Shell, to search for attached ADB Devices. (Yes, it sees my phone as: LGD801cb55c4e4 sideload)
-I proceed to try to sideload a ROM and after about 30% Signature Verification, Fails causing my D801 to Abort Installation. (no matter what I throw at it, IMG/KDZ/TOT files fail as well.)
Now when it comes to trying the methods listed in: https://forum.xda-developers.com/showthread.php?t=2432476 to Flash Stock Firmware, I simply can't because my D801 doesn't connect to my PC in Device Manager under Ports or QHSUSB_BULK. (it connects each time under SAMSUNG Android Phone - AndroidNet Sooner Single ADB Interface.
I've also tried SRKtool_2.1_droidth which ends up leaving me at another dead end.
If you have the time please help, and or point me in the right direction.
I've already installed the needed drivers:
qualcomm-driver
adb-setup-1.4.3
LGMobileDriver_WHQL_Ver_4.2.0
Downloaded all the corresponding files to my PC for my D801:
Firmware Files (KDZ & TOT also Extracted)
LG Flash Tool 2014 & 2015
SRKtool_2.1_droidth
Megalock DLL File
D801 DLL File
LGUP
Silly suggestion perhaps, but after freaking out for about an hour when this happened to me I ended up realizing I could reboot to TWRP using the hard keys. Honestly, I only mention it because I was trying everything else too. If you didn't already try it (I didn't see it in your description) I think it's the power key and volume down key while it's off and as soon as you see the splash screen, release them both and immediately repress and hold them both until you see TWRP. Just a thought.
I loved that phone!
Sent from my [device_name] using XDA-Developers Legacy app
Just tried your technique @C-Tec. Thank you. But that only brings up the Factory Data Reset Screen (to Erase all user data & Restore default settings) instead of the TWRP Recovery screen. (so that's a dead end)
Because, after selecting Yes, Erasing data and Restoring default settings, my phone reboots in to the same loop I started from, as if I never did anything to remedy the situation.
Update on my progress:
-So I was able to get in to Download Mode. (holding the VOLUME UP button, while the phone is off)
-Followed by the Firmware Update Screen after plugging my phone in to my PC via USB. (which then read my phone as - LG Mobile USB Serial Port. (COM8) under Ports in Device Manger)
-I then Flashed the D801 Stock Lollipop KDZ. (by using the LG Flash Tool 2014)
-Waited for the progress bar to completely fill to 100% and BOOM! I fixed my problem.
-Android Lollipop running like NEW. (that's 2014 NEW :crying
-Now to retry Lineage OS 15.1.
Here's a helpful Video Clip, to understand how to use the Flash Tool. -
Just search for: LG G2 - Fix LG Logo Stuck/ Boot Loop Fix / Flash Firmware - EASY METHOD in YouTube.
Being that I'm low ranked I cant post any links just yet, sorry.
I even went out of my way and ordered a LG V20 off of Swappa, which arrives tomorrow. Due to this issue.
Hi guys. After several attempts to unbrick my stratos 2 I now suspect 2 filesystem is corrupted for good because nothing works and I'm still stuck at the logo screen. Anyways, as a last resort, I decided to seek the opinion and knowledge from people who have more experience.
I tried the simpler methods trying to access the bootloader through adb but the command 'adb shell reboot bootloader' didn't work because there was no '/system/bin/sh'. I think it tells something about the filesystem, maybe. I even ran 'adb ls /system/bin' but there's nothing there.
After that I found a method to enter fastboot using the device buttons and etc. Before that I also unlocked the bootloader. 'fastboot getvar all' shows 'unlocked: yes'.
Than I tried the following:
First I tried the method described in this post:
https://forum.xda-developers.com/t/...e-installer-2-3-13-0-amazfit-stratos.3764636/
Everything worked during the process, but after boot the device I'm still stuck at the logo screen.
After that I tried the method describes in this post (deep flash):
https://forum.xda-developers.com/t/...-stratos-3-verge-deep-flash-tutorial.3908237/
Again, the process ran smoothly, the images where written but again, after rebooting, still stuck at logo screen.
After both procedures I executed 'adb shell' but still getting a message telling me there's no /system/bin/sh. Looks like nothing happened after the procedures.
So I don't know what else I can do or even if there is something else to do.
Any thoughts?
UPDATE:
I almost got it to work after trying method 1 another time. I passed the logo screen, the initialization process even got to the end and I was able to pair with the smartphone, but it was VERY slow, with several little hangs during the process. Some error occurred too that caused the device to reboot.
After that it was still too slow and I rebooted again. Guess what: stuck in logo screen again. So it's pretty clear to me that this is a storage corruption, but I still want a second opinion.
iranmarcius said:
Hi guys. After several attempts to unbrick my stratos 2 I now suspect 2 filesystem is corrupted for good because nothing works and I'm still stuck at the logo screen. Anyways, as a last resort, I decided to seek the opinion and knowledge from people who have more experience.
I tried the simpler methods trying to access the bootloader through adb but the command 'adb shell reboot bootloader' didn't work because there was no '/system/bin/sh'. I think it tells something about the filesystem, maybe. I even ran 'adb ls /system/bin' but there's nothing there.
After that I found a method to enter fastboot using the device buttons and etc. Before that I also unlocked the bootloader. 'fastboot getvar all' shows 'unlocked: yes'.
Than I tried the following:
First I tried the method described in this post:
https://forum.xda-developers.com/t/...e-installer-2-3-13-0-amazfit-stratos.3764636/
Everything worked during the process, but after boot the device I'm still stuck at the logo screen.
After that I tried the method describes in this post (deep flash):
https://forum.xda-developers.com/t/...-stratos-3-verge-deep-flash-tutorial.3908237/
Again, the process ran smoothly, the images where written but again, after rebooting, still stuck at logo screen.
After both procedures I executed 'adb shell' but still getting a message telling me there's no /system/bin/sh. Looks like nothing happened after the procedures.
So I don't know what else I can do or even if there is something else to do.
Any thoughts?
UPDATE:
I almost got it to work after trying method 1 another time. I passed the logo screen, the initialization process even got to the end and I was able to pair with the smartphone, but it was VERY slow, with several little hangs during the process. Some error occurred too that caused the device to reboot.
After that it was still too slow and I rebooted again. Guess what: stuck in logo screen again. So it's pretty clear to me that this is a storage corruption, but I still want a second opinion.
Click to expand...
Click to collapse
If you get the watch booting and passing the initial A logo, reboot into fastboot before the system crashes and do a factory reset in fastboot
fastboot erase cache
fastboot erase data
And let's see if that fixes something.
Hi, thanks for the answer.
I already did that. I even erased system partition, but unfortunately it didn't work either.
Giving more information, after erasing the partitions I did a test: I rebooted the device (right after fastboot erase) and executed 'adb ls /' to see if something changed, but apparently not. There was still several directories and files, like nothing was erased.
Should I try to format these partitions maybe? Either way, I'm still stuck in the A logo. At least I didn't kill the device completely (yet).
Saratoga79 said:
If you get the watch booting and passing the initial A logo, reboot into fastboot before the system crashes and do a factory reset in fastboot
fastboot erase cache
fastboot erase data
And let's see if that fixes something.
Click to expand...
Click to collapse
UPDATE:
I erased cache and data partitions again and rebooted the device. After that I was able to get to the QR code screen. I even was able to enter 'adb shell' and execute a 'top' command to see what was happening during the initialization process.
But after it got to the QR code screen the device rebooted by itself and I got stuck in the A screen again.
So I erase the partitions one more time, reboot the device but there was no way I get passed the A logo screen.
When I execute 'adb ls /system/' there are no files.
iranmarcius said:
Hi, thanks for the answer.
I already did that. I even erased system partition, but unfortunately it didn't work either.
Giving more information, after erasing the partitions I did a test: I rebooted the device (right after fastboot erase) and executed 'adb ls /' to see if something changed, but apparently not. There was still several directories and files, like nothing was erased.
Should I try to format these partitions maybe? Either way, I'm still stuck in the A logo. At least I didn't kill the device completely (yet).
Click to expand...
Click to collapse
After several attempts, erasing data and cache partitions the device is working again.
Looks like after erasing partitions and rebooting it was necessary to wait a long time until all process in the device did their jobs, including app optimization, with can take several minutes, but sometimes with no feedback on the screen.
I'm still trying to figure out a way to check partitions for erros, maybe using e2fsck, but when i try to do it, even using -b option, I got a message that I must have RW access to the partition or be root.
Anyone can help me on that?
Continuing the saga, I rebooted the device using a rooted image and from that I was able to check the partitions using e2fsck -n. The results:
e2fsck 1.42.9 (28-Dec-2013)
Warning! /dev/block/platform/jzmmc_v1.2.0/by-name/data is in use.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (545541, counted=616333).
Fix? no
Free inodes count wrong (172802, counted=172856).
Fix? no
/dev/block/platform/jzmmc_v1.2.0/by-name/data: 1086/173888 files (6.3% non-contiguous), 148731/694272 blocks
So /data partition has some errors but I couldn't fix it because it's reported busy. Maybe some processes are using it, but I don't know which ones. The best that occurred me is that if I kill those processes I can fix the partition errors. don't know if this is the correct way to do it.
iranmarcius said:
After several attempts, erasing data and cache partitions the device is working again.
Looks like after erasing partitions and rebooting it was necessary to wait a long time until all process in the device did their jobs, including app optimization, with can take several minutes, but sometimes with no feedback on the screen.
I'm still trying to figure out a way to check partitions for erros, maybe using e2fsck, but when i try to do it, even using -b option, I got a message that I must have RW access to the partition or be root.
Anyone can help me on that?
Click to expand...
Click to collapse
Hi all,
Well, operator error is definitely at fault here... I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and obviously ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Hi, would anyone like to weigh in on this issue?