Hello,
I recently had a "HTC" (Chicony) Hero GSM donated to me. I have managed to root it, but I am unable to load a custom ROM, which kind of defeats the purpose.
I CAN INSTALL MOST MARKET APPLICATIONS, which to me indicates it has most of the legit android system.
To root it I pushed su via adb and then used su on SuperUser.apk, which I downloaded from the market. This worked fine.
However I can't download ROM manager though. It is not available in the market. If I try to copy the .apk file (newest or an old version 1.8.?) it says it can't be installed on the phone. I suspect my "version" of android is not supported.
I was hoping to get some help...
My version of android is:
Model number
G03CE
Version information
05020008_76A805
Also if I type in lsusb I get:
Code:
Bus 001 Device 006: ID 04f2:a142 Chicony Electronics Co., Ltd
Things I have tried:
Ubuntu 10.10:
1. Fastboot - fail can't boot to recovery
2. adb flash_image recovery recovery.img - fail CAN'T FIND RECOVERY PARTITION
3. Install RomManager - fail can't install
4. Z4root - fail can't install
5. Unrevoked3 - fail nothing happens
6. Put recovery.img in /system/ - fail nothing happens but I get a force close error about the recovery.img on startup also kills my usb connectivity
7. Install romdump both via adb and terminal emulator - fail won't install just hangs
8. flash-rec.apk - fail can't backup or flash recovery: gives unknown ebi version as error msg and flash recovery is greyed out.
Windows XP:
9. SuperOneClick Root - fail waiting for device (no drivers?)
10.
HTML:
http://forums.regawmod.com/showthread.php?tid=6
- fail (no drivers?)
11.
HTML:
http://forum.xda-developers.com/showthread.php?t=559622
- fail (no drivers?)
Getting Drivers on Windows XP:
1. Install Google SDK.exe and download drivers - appeared to work but did not allow device to have recovery flashed
2. Installed latest version of HTC sync - fail no device connected
3. Installed version 2.4 of HTC sync - fail no device connected
4. Installed PDANET on phone and PC appeared to work (only with google drivers though) and did not allow any of the apps to flash a custom recovery.
Also I can't get it to boot into recovery via any combination of keys. However I was able to get:
Code:
adb reboot recovery
to reboot to a broken recovery screen with a big exclaimation mark and a picture of a phone. However even in this screen fastboot devices yields nothing.
My opinion of the problem:
I do not have a recovery partition. I checked this by:
Code:
adb shell
su
cat /proc/mtd
This yielded that all mtb1, mtb2 etc were all empty. They should be boot, recovery, etc as I understand it.
HTML:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Apparently romdump can be used to create new partitions, see here:
HTML:
http://www.addictivetips.com/mobile/how-to-backup-your-android-phones-boot-recovery-and-system-partition-images/
But I could not make it work even with root.
Anyway I am pretty confident if I can just force it to make a recovery partition and dd copy the files from an .img file to that partition I can make it work. But I am a n00b at android rooting (I have only rooted one nexus one and that is it).
I am all out of ideas. If someone could please help it would be greatly appreciated.
Thanks,
Glen.
Hey guys, I'm having a problem with my entire GNex being read-only. I currently can't get the device to boot into Android (after unsuccessfully trying to flash franco's 4.3 kernel to my 4.3 ROM) and am stuck in TWRP 2.6.
There are a couple versions of Paranoid Android on there but when I try to flash one of them, all I get is "Failed" in red font (with no other error message); the only version that I'm able to flash is the most recent 4.3 build, but that doesn't boot past the Google logo.
I've wiped everything multiple times except for Data but that didn't help, and fixing permissions only gives me the "Failed" error again.
I can use adb to pull anything I want from the device, but it refuses to accept any files via the push command, and I get a message saying "failed to copy 'filenamehere.ext' to '/sdcard/filenamehere.ext': Read-only file system".
How do I fix this error? I have adb and fastboot working correctly on Windows 8.
Also, when I try to fix permissions, I get a message in the log that says "E: Unable to chown '/data/app/com.yackovsky.holle" (the name is cut off, but it's the package name for this app: https://play.google.com/store/apps/details?id=com.yackovsky.holler.wht&hl=en , although I doubt the app has anything to do with the problem).
Also tried following the steps from this post http://forum.xda-developers.com/showpost.php?p=22970837&postcount=14 but still got errors about the filesystem being read-only.
Ended up formatting the phone to solve the problem. /thread
Hey guys,
I was googling for the past few days who else might experience such problem, but I haven't stumbled upon such case. The problem is, I'm stuck on the bootloader part.
The initial goal was to root the device, so:
- I unlocked the bootloader,
- installed clockwork-touch-6.0.4.7
- wiped everything
- when I try to install SuperSU & new ROM I'm getting errors like
Code:
Can't mount /cache/recovery
Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (No such file or directory)
Can't mount /cache/recovery/log
and a few other errors in this fashion about cache.
When I actually run the
Code:
abd sideload aicp_flo_n-12.0-UNOFFICIAL-20161020.zip
the installation tries to mount folders like /data but gets an error.
Finally it says
Code:
E1001: Failed to update system image
Installation aborted
Is there a way to re-format everything to FAT using fastboot and then begin everything from scratch? I have a feeling this is filesystem problem that it can't read properly or something... Maybe I'm wrong? What would be your suggestions?
Thanks!
I had a similar issue on mine a few days ago. I was completely stock and wanted to unlock bootloader, flash a custom recovery and then finally a custom ROM. I was successfully able to unlock the bootloader and flash the recovery (latest TWRP). But, when I tried to boot into recovery, it went past the recovery logo and then showed me errors like yours inside the recovery and rebooted. It then automatically booted into the recovery, showed the same errors and rebooted again. I wasn't able to do anything apart from booting into bootloader by sending an adb command.
Now coming to the part which fixed my errors. What I did was used the "fastboot -w" command (without the quotes) while I was in bootloader to wipe everything and after that, flashed the recovery again. Then I was able to successfully boot into recovery and everything has been fine since then.
I was rooted on 9 with Magisk. Updated to 10 via Google update on the phone. All worked. Still rooted but didn't have TWRP installed- it wouldn't work. But no worries. I was rooted which is the main thing.
Tried to do the DEC OTA with Magisk. Didn't work. Flashed factory image of December and it worked. Tried to boot img of TWRP. didn't work. Tried to use Magisk to root with the boot.img patch from PC. Didn't work. Phone wouldn't boot.
Reflashed factory image and it didn't work. Changed cord to same USB A and and got it working again. Rinse, repeat. Eventually it stopped working period. adb and fastboot were not talking to the phone.
Used different USB A port and newer cord (same as above) and was able to reinstall Dec factory and it worked. Used new cable to boot twrp.img. Worked. Used that to flash TWRP. Worked. Tried to flash Magist in TWRP. Got TWRP bootloot. Used TWRP to fix bootloop. It restored boot (so far as I can tell- what do I know? I'm just a lawyer) and phone worked but no root. Rinse repeat a number of times. Got Magisk working and THEN tried to flash TWRP. Bad plan. Broke.
Went to screen saying whole thing was broke (Their recovery sort-of screen saying files corrupted in red and I could retry or wipe in blue. But I could factory reset. I avoided that and tried to reflash (using flash-all.bat after removing -w) a number of times. It finally worked. Gave it the overnight to calm down. Me, too.
10 was working. Cord seemed to be working. Came home after work and booted image of TWRP. That worked. Flashed Magisckzip. That dumped me into TWRP which I swear to god I had not flashed, just temp booted. So tonight was rinse and repeat of yesterday's woes.
Anyhow, many attempts to reinstall Dec factory image finally worked (using various cords, USB A & C ports.)
Rinse, repeat.
I have my SD card backed up on my PC so it isn't any kind of disaster for me to do a factory rest but dammit! I don't wanna! It should work.
At the present time I am working with Dec factory image, stock recovery, and not rooted. (Although Tasker seems to be working in location-sound off circumstances. WTAF?)
Taking any and all advice. Thanks.
Aside from full wipe. If that's your only advice please just say "wipe" and move along. If you have another suggestion, please use lots of words.
(My husband says it's the testosterone sensor but I'm the one who fixes the computers, phones, and network so I think my cover is deep enough...)
janehull said:
I was rooted on 9 with Magisk. Updated to 10 via Google update on the phone. All worked. Still rooted but didn't have TWRP installed- it wouldn't work. But no worries. I was rooted which is the main thing.
Tried to do the DEC OTA with Magisk. Didn't work. Flashed factory image of December and it worked. Tried to boot img of TWRP. didn't work. Tried to use Magisk to root with the boot.img patch from PC. Didn't work. Phone wouldn't boot.
Reflashed factory image and it didn't work. Changed cord to same USB A and and got it working again. Rinse, repeat. Eventually it stopped working period. adb and fastboot were not talking to the phone.
Used different USB A port and newer cord (same as above) and was able to reinstall Dec factory and it worked. Used new cable to boot twrp.img. Worked. Used that to flash TWRP. Worked. Tried to flash Magist in TWRP. Got TWRP bootloot. Used TWRP to fix bootloop. It restored boot (so far as I can tell- what do I know? I'm just a lawyer) and phone worked but no root. Rinse repeat a number of times. Got Magisk working and THEN tried to flash TWRP. Bad plan. Broke.
Went to screen saying whole thing was broke (Their recovery sort-of screen saying files corrupted in red and I could retry or wipe in blue. But I could factory reset. I avoided that and tried to reflash (using flash-all.bat after removing -w) a number of times. It finally worked. Gave it the overnight to calm down. Me, too.
10 was working. Cord seemed to be working. Came home after work and booted image of TWRP. That worked. Flashed Magisckzip. That dumped me into TWRP which I swear to god I had not flashed, just temp booted. So tonight was rinse and repeat of yesterday's woes.
Anyhow, many attempts to reinstall Dec factory image finally worked (using various cords, USB A & C ports.)
Rinse, repeat.
I have my SD card backed up on my PC so it isn't any kind of disaster for me to do a factory rest but dammit! I don't wanna! It should work.
At the present time I am working with Dec factory image, stock recovery, and not rooted. (Although Tasker seems to be working in location-sound off circumstances. WTAF?)
Taking any and all advice. Thanks.
Aside from full wipe. If that's your only advice please just say "wipe" and move along. If you have another suggestion, please use lots of words.
(My husband says it's the testosterone sensor but I'm the one who fixes the computers, phones, and network so I think my cover is deep enough...)
Click to expand...
Click to collapse
Oh my, where to start. Definitely sounds like you've got the famous P2XL USB cable bugaboo...at least somewhat. Here's what I would do.
Extract the boot.img from the factory image, place it on your phone and patch it again, then transfer it to your platform-tools folder.
Make sure your platform tools are up to date. Latest version is 29.0.5
Have you also fastbooted the factory image to both slots? If not, do that first. You can manually change slots with..fastboot --set-active=a or b depending what slot your currently on.
If your phone is booting, then go back and fastboot your patched boot.img to both slots with...
..fastboot flash boot magisk_patched.img --slot=all..
If the phone boots you should be rooted.
If you still want twrp, download it again to your pc, put one copy in your platform-tools folder, and one on your phone, remove your screen lock and set it to swipe or none. Then fastboot the twrp 3.3.0-0.img which should boot you into twrp. If it's working, then select install, select image, then flash the twrp image to your recovery ramdisk partition. That should keep your recovery as twrp. Boot up, and you should be good to go :good:
Yes, latest platform tools. After first difficulties I dumped everything, did new downloads and upzips of of factory image, platform-tools, and got new twrp.img, twrp.zip and magisk.zip. Checkedsum on all of them I could.
No. It never occurred to me to fastboot factory image to both slots. I guess I just assumed that The Google (tm) would know what they were doing. Thank you for that. I will give it a shot in the morning. I need enough lead time to fix it if it breaks because my life and office are on that phone.
And now, after learning how to see which slot is active I can learn how to flash to both! Thanks a lot.
janehull said:
Yes, latest platform tools. After first difficulties I dumped everything, did new downloads and upzips of of factory image, platform-tools, and got new twrp.img, twrp.zip and magisk.zip. Checkedsum on all of them I could.
No. It never occurred to me to fastboot factory image to both slots. I guess I just assumed that The Google (tm) would know what they were doing. Thank you for that. I will give it a shot in the morning. I need enough lead time to fix it if it breaks because my life and office are on that phone.
And now, after learning how to see which slot is active I can learn how to flash to both! Thanks a lot.
Click to expand...
Click to collapse
Just a little additional FYI...if you want to keep twrp as your recovery, flash the same image file, NOT the twrp zip file, once you enter twrp after fastbooting it.
And, if you want to know what slot your currently on, the command is...fastboot getvar all. Best of luck to you :good:
Better and better. Now I have no USB. When I go to it in Settings ALL usb prefs are greyed out. Needless to say I haven't tried to flash anything because I can't. So I guess a factory reset is in my future. At least I copied my SD card and Titanium Backup folder. /sigh
Safe mode makes no difference.
If anyone knows how to get the USB working without wiping that would be appreciated.
Oh, and in other "It ain't workin' rite" news, it keeps going back to pixel launcher instead of Nova.
I had a crappy day and now I'm going to bed.
Welp! The Google (tm) is sending my replacement phone...
TWRP 3.3.0.0 Issue on Android 10
My phone is Google Pixel 2XL that is runnung under Android 10 and TWRP 3.3.0.0 img and installer.
I was unable to backup any ROM file under TWRP Recovery.
The error is "Backup Name is: 'PixelDust--14-59-50'
I:Backup_Folder is: '/data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50'
I:Calculating backup details...
* Total number of partitions to back up: 3
* Total size of all data: 7486MB
* Available space: 46798MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50
Invalid encryption mode 'ice:aes-256-heh'
Failed to mount '/system' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/system_a', current file system: 'ext4'
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50/recovery.log"
I had tried to flash Magisk.img but it did not work due to error.
The error log is "- Device platform: arm64-v8a
- Copying image to cache
1566+0 records in
1566+0 records out
1603584 bytes (1.5 M) copied, 0.006409 s, 239 M/s
1045+1 records in
1045+1 records out
1070668 bytes (1.0 M) copied, 0.004831 s, 211 M/s
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed"
I was unable to root on my phone.
How can I fix these issues?
Touareg2013 said:
My phone is Google Pixel 2XL that is runnung under Android 10 and TWRP 3.3.0.0 img and installer.
I was unable to backup any ROM file under TWRP Recovery.
The error is "Backup Name is: 'PixelDust--14-59-50'
I:Backup_Folder is: '/data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50'
I:Calculating backup details...
* Total number of partitions to back up: 3
* Total size of all data: 7486MB
* Available space: 46798MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50
Invalid encryption mode 'ice:aes-256-heh'
Failed to mount '/system' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/system_a', current file system: 'ext4'
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50/recovery.log"
I had tried to flash Magisk.img but it did not work due to error.
The error log is "- Device platform: arm64-v8a
- Copying image to cache
1566+0 records in
1566+0 records out
1603584 bytes (1.5 M) copied, 0.006409 s, 239 M/s
1045+1 records in
1045+1 records out
1070668 bytes (1.0 M) copied, 0.004831 s, 211 M/s
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed"
I was unable to root on my phone.
How can I fix these issues?
Click to expand...
Click to collapse
You really can't fix it until, and if, twrp is updated to deal with the new partition system that google implemented with A10. However, you can try this slightly outdated adb method that still works
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
Now the phone is unable to boot to system, I have no idea what I could do to fix it as there is no way to use adb or fastboot command…
I remember that the stock rom version is S11a, it have some problems when I tried to root it, and failed to flash recovery even I've got the root permission (response "write error: no space left")
------↑solved by using LG flashtool↑------
Now I am facing the problem that unable to install TWRP recovery using dd, it responds “ write error: No space left on device” I’ve reinstall the LG drivers, reboot the phone, reboot the computer, unroot and root again, but the problem still occurs.
----- update ------
solved by using flashify, and TWRP version 3.3.1 instead of latest 3.6.1, so that it won’t have “secure boot error” warning, and boot to recovery successfully.
But there is a new problem now, when I tried to sideload MindTheGapps after installed LOS 18.1 successfully, it warns me “could not mount /mnt/system! Aborting”. This is the third phone that having this warning for me, and I still couldn’t figure out which step goes wrong.
Nothing goes wrong after flashed to lineage recovery, installed MindTheGapps now.
--update--
I also tried to flash lineage recovery from TWRP on my D855, it also works, I installed MindTheGapps and everything works fine. So this is the problem of TWRP? Or reinstall the recovery is the solution? Maybe I would have a test later.