I've been trying to root my wife's HTC Rhyme and in my efforts, something hosed the WiFi. All I get is "ERROR" under WiFi in the wireless network settings menu. This happened to me once or twice on my incredible and a kernel re-flash fixed it. I really want to root it so that she can have the benefit of being able to completely backup everything. I've tried ZergRush, TocoRoot, SuperTool, OneClick, SuperOneClick... none of it worked. The only thing that I've been able to do successfully is unlock/re-lock the bootloader.
Is it possible to extract the ROM and/or all critical system files from a stock rooted phone and use them to restore another phone that is malfunctioning? I was thinking that if I found someone with a rooted HTC Rhyme who would be willing, they could send me whatever files I would need to completely restore the phone, WiFi and all.
Any help with at least the WiFi issue wold be appreciated. Rooting would be nice too but I don't want to be greedy.
Thanks.
I was able to install an RUU which fixed the WiFi issue, but now the phone is stuck in a boot-loop. I've flashed it three times (doing it twice each attempt) but its the same result every time. The phone boots normally the first time, then goes into loop on the next restart. Could be the wrong RUU, could be corrupted or maybe I'm doing it wrong. I don't know.
Please... Any suggestions would be most appreciated.
I fixed it.
RuLEoF2 said:
I fixed it.
Click to expand...
Click to collapse
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks!
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
RuLEoF2 said:
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
How did you get the ruu to run i keep getting a error 140 wrong bootloader version i tried ruu 1.26.605.11 and 1.26.605.6 i attempted to flash a ics rom and the phone got stuck on the splash screen so then i used my backup i made before i flash the ics rom and wouldnt boot so i extracted the boot.img from the ruu and flashed it to get the phone back up and running the phone is still rooted but i have no wifi no bluetooth no cam i been searching everywhere for a rhyme kernel bt no luck if anyone could help that would great
Click to expand...
Click to collapse
Hello,
If anyone could help me get my phone back into a functioning state, I would very much appreciate it! I have been playing around with the Cyanogenmod 10 nightlys. All was going well until I decided to try encryption. It encrypted the phone okay, but I decided to format the phone and get it back to an unencrypted state, except it wouldn't allow me to factory reset. The button to start the reset did nothing except reboot the phone a few minutes after pressing it.
No problem, I thought, I made a nandroid backup before I started playing with ROMs, I'll just restore that, except that didn't work because CWM couldn't mount the encrypted volumes. So, I copied the CWM backups to an SD card using root explorer, and tried to restore from there. It gave me an error advising it couldn't mount/format /system. So, I rebooted, only to get stuck on the Samsung boot logo.
I can still get into download mode though. so I tried flashing the stock firmware with Odin. Odin reported the software flashed succesfully, and the phone boots now with the stock animation so presumably it did work, but it still asks for the encryption key. I put in the key I used originally but it rejects it.
I don't know what else to do to restore my phone to a stock state.
This is my first Android phone and I was just playing around out of curiosity, so pleas excuse any noob errors I may have made along the way. I shall be sure to learn from them.
Please tell me I can get my phone back to the original state!
s0mmie said:
*snip*
Click to expand...
Click to collapse
It seems I have managed to get back to a working state by using the Android recovery menu. Phew. I shall not be messing with encryption again. All part of the learning curve though, I suppose!
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
I'm updating this for anyone else who runs into issues like this: I went ahead and formatted the SD card from within windows, then relocked the phone, reinstalled the RUU and I'm back in a workable mode
itsmattgw said:
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
Click to expand...
Click to collapse
I had the exact same problem. I just reformatted the internal storage and that fixed a lot of my issues. I can't however get the RUU to work. Can't seem to find my phone, neither can HTC Sync. Is this just a problem caused by MeanBean? I use to run MeanBean but then switched to CM10 for a few months and was going to switch back. Never had an issue like this before.
I recently rooted my phone and everything was fine. This morning I installed a debloated rom http://forum.xda-developers.com/showthread.php?t=2296109 and It seemed to work but after I rebooted the phone just sits at a screen that says
Samsung
an unlocked icon
Custom
I can still get into Odin and TWRP but nothing I do seems to solve my problem. I have verified the MD5 of the image as well as trying to install a backup I made prior to flashing but the restore fails.
Does anyone know what I can do?
I should add that TWRP asks for a password when I load it but I never explicitly set one and also it seems to have trouble with the partition table.
Update: Solved maybe? I got this phone to boot but I am not sure what happened. I flashed a rom from TWRP several times and finally one took ... still would like info from someone who actually knows what is going on as I am not sure this wont happen again
Update: So it seems that every time I something happens and the drive or loader gets encrypted and it no longer boots. the "solution" is to do a full wipe then install a rom. This happens every time i reboot and I would really like a solution to this.
So after updating my bootloader to the new version so I can run Android Nougat however I wasn't getting any LTE connection and decided to restore the EFS backup I had from android MM.
My phone started having problem more problems (SIM card not being detected) and I decided to run the OPX recovery and switch back to default.
However this resulted in my bootloader getting locked for some reason and whenever I try to reboot my phone the screen is black and the LED indicator turns white.
I can boot into the factory OPX recovery but I'm forced to use the volume and lock buttons because I can't use my touchscreen whilst using this (no idea whether this is normal).
I can still boot into fastboot mode and have tried to sideload a new ROM however this has been to no avail.
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Hmm, okay thanks for your reply. But is it really a hardware problem? It sounds weird but maybe replacement is a way...
It strange, since I had the problem with my phone there are 3-4 new threads now in this forum were people have exactly this problem, black screen with white led.
I will not flash my phone again in the foreseeable future and just use gravitybox instead.
Mutchatcho said:
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
Click to expand...
Click to collapse
I did the exact same thing as you and ended up in this situation.
adefigo said:
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Click to expand...
Click to collapse
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Miniheadshot said:
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Click to expand...
Click to collapse
With the new mainboard and the new rom build, it is impossible to use twrp or root. I didn't know that when I wrote I would be using gravitybox from now on and not flash custom roms again.
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Mutchatcho said:
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Click to expand...
Click to collapse
What is your built number?
adefigo said:
What is your built number?
Click to expand...
Click to collapse
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Mutchatcho said:
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Click to expand...
Click to collapse
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Ah okay, I didn't know that. Obviously then I got maybe the other one.. but not sure if this makes the difference.
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
dchrono said:
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
Click to expand...
Click to collapse
No, did not change twrp versions during flashing new ROM and wipe to restore backup. Don't know if I remember correctly but I think I was on Bluesparks twrp (was it 3.0.0?) and did not change that during the processes.
i also had same problem
i try to update my twrp recovery with flashify. it was successful but now i cant boot into recovery. i dnt know bootloader is locked or not. i can use many fastboot commands like fastboot reboot-bootloader, fastboot continue. please help me. i try many times to update or remove twrp but nothing happend. rom is working.
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
I never changed twrp version during this until it was removed by MsmDownloadTool.
I also noticed that adb sideloading using OOS's old stock recovery with a OOS OTA zip doesnt work, it either gets stuck at logo or loops. Sideloading newer OTA zips kills the phone more because I tried to flash a MM zip and found that recovery no longer works. I've tried redownloading the MsmDownloadTool package and using this other modified MsmDownloadTool here a few replies down https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Another thing I noticed is that windows detects a bunch of unreadable local drives, with one readable containing only an 'images' folder, with useful-looking stuff like adsp.b00, adsp.b01 all the way to adsp.b12 and also .mbt files. I can provide the full list if it's useful. It's also detected in the device manager as "Marshall London HS-USB Diagnostics 9006 (COM6)" under Ports.
I really hope that I don't need to send this phone back to oneplus.
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
Click to expand...
Click to collapse
Exactly what I did and what happened to my phone. I had to send it back to repair and got it back with a new mainboard in a state that I cannot use twrp any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Did you try to adb sideload flash the 3.1.4 on the 14 version?
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt phone back to oneplus.
Click to expand...
Click to collapse
I had flashed a ROM and wanted to restore a backup of MOOS. The back up restored no problem but when I booted it wouldn't detect sim trays and no wifi. When I typed *#06# no iemi's and finally when I checked about phone I had no baseband. I had a back up of efs and persist but wouldnt help. If this sounds like your issue or if anyone's having this problem its actually easy fix. With adb commands had to delete modem1 and modem2 files. I had my doubts but after reboot sims trays detected, wifi and iemi's restored.