Related
Hi,
I almost bricked my daughter's ChaCha. Half a year ago I unlocked the bootloader to be able to install and run Link2sd to increase performance of the phone and have my daughter have all the apps on it she wants. But a week or so ago the phone started to act up and I decided to take a look.
End of the story is that the phone, when turned on, boots into fastboot automatically but the volume and power keys do not work at all. So I can't select reboot or recovery or anything. I have to remove the battery to switch it off...
Apparently system and recovery are gone cause when I issue 'fastboot oem boot' the response is '(bootloader) [ERR] Boot/Recovery image does not exist!!!'. That can't be good...
The bootloader got relocked in the process of trying to fix it which complicates the problem. Now I can't re-unlock it because the volume and power keys don't work. I can get fastboot in unlock mode but can't select 'yes' and continue because the keys do not work...
I tried re-installing stock rom via RUU with various results. Version 1.33 complains about a customer id (error 131), version 1.13 thinks it's a signature error (error 132) and version 1.18 (I must be desperate) doesn't like the bootloader version (error 140).
I tried creating an old school goldcard to get the phone to accept RUU 1.33 but obviously that failed too. Since I can't get into the phone over adb (only fastboot) I can't get the phone's CID. Also, system is reported to be nonexistent so trying to extract the CID is a dead end anyway.
I think I've tried everything and I'm about to give up. But I thought, before I do that, I better check with the experts here to see if anybody else has a brilliant idea to solve my problem. I'm considering buying the XTC clip but I'm not sure if that will work since the phone is so far gone already. Maybe someone here knows the answer to that?
Below is what 'fastboot getvar all' gives me. Hopefully that helps in answering my question: Is this phone bricked or is there still hope?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.10.0000
(bootloader) version-baseband: 7.51.35.19
(bootloader) version-cpld: None
(bootloader) version-microp: 0557
(bootloader) version-main: 1.57.0.0
(bootloader) serialno: HT16GV409974
(bootloader) imei: 355746042148642
(bootloader) product: chacha
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PH0611000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d86ac222
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
It doesn't look like it's anything you've done. If the bootloader is now locked, I would take advantage of that and send it back to the shop to get it repaired. (obviously, don't mention that you tampered with it). That shouldn't happen, I've got link2SD, and so has my partner and we've never had any problems like that, so I think it must be something wrong with your phone :/
Progress
Thanks for your reply. I thought about returning it the phone to have it repaired but it's apparent the phone has been unlocked and re-locked again. That will probably void warranty.
I don't think Link2sd caused this problem. Something else must have happened but I doubt it's a hardware problem.
I've made a bit of progress in the meantime. Somehow (I don't know how) the phone got in to recovery. The screen was black though but I could get into it with adb shell! So I got my CID and created a goldkey. I hoped that was all I needed but I still can't flash a stock rom over RUU because now they all complain about my hboot version which is 1.10
I think I need a RUU rom (exe) that supports hboot 1.10. Or, a way to downgrade to 1.07 or 1.05. Or a way to flash or push something onto the phone while in recovery.
Any help will be appreciated...
NoLimit64 said:
Hi,
...when turned on, boots into fastboot
Click to expand...
Click to collapse
Well if you are able to boot into fastboot maybe you can try this method. I used this to revive my friend's chacha.
Download this tool (it is, I believe, adlx's small fastboot tool). Extract it and navigate to it with cmd (I did this on windows). But before that download a RUU for your chacha (I used 1.3.3 version since it was the only one I could find), run RUU but don't flash it and don't exit the application as well. Then locate your temp folder (%temp%) and find somewhere in one of the folders a zip named Rom.zip (use the search function if you prefer). Copy the Rom.zip anywhere you like and extract system.img, boot.img and recovery.img and place them in the same folder where you extracted fastboot tools. And now enter these commands in cmd (don't forget to navigate to the folder you placed all the files):
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
When it is finished, reboot your phone (you will probably need to do this by pulling the battery out) and hopefully you will have the stock rom installed.
Hope that this will help you.
Regards
didije said:
Well if you are able to boot into fastboot maybe you can try this method. I used this to revive my friend's chacha.
Download this tool (it is, I believe, adlx's small fastboot tool). Extract it and navigate to it with cmd (I did this on windows). But before that download a RUU for your chacha (I used 1.3.3 version since it was the only one I could find), run RUU but don't flash it and don't exit the application as well. Then locate your temp folder (%temp%) and find somewhere in one of the folders a zip named Rom.zip (use the search function if you prefer). Copy the Rom.zip anywhere you like and extract system.img, boot.img and recovery.img and place them in the same folder where you extracted fastboot tools. And now enter this commands in cmd (don't forget to navigate to the folder you placed all the files):
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
When it is finished, reboot your phone (you will probably need to do this by pulling the battery out) and hopefully you will have the stock rom installed.
Hope that this will help you.
Regards
Click to expand...
Click to collapse
I had an issue with flashing an RUU because of HBOOT version, but as didje said, the 1.33 RUU version works with that HBOOT version
ethancottier said:
I had an issue with flashing an RUU because of HBOOT version, but as didje said, the 1.33 RUU version works with that HBOOT version
Click to expand...
Click to collapse
I always have issues flashing RUUs. Error this, error that, really annoying, so I don't flash them anymore. Now, I just flash manually those three files and I have no worries.
didije said:
I always have issues flashing RUUs. Error this, error that, really annoying, so I don't flash them anymore. Now, I just flash manually those three files and I have no worries.
Click to expand...
Click to collapse
Sorry, no luck....
C:\Fastboot\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (3172 KB)... OKAY [ 2.480s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\Fastboot\Fastboot>fastboot flash system system.img
sending 'system' (259524 KB)... OKAY [ 62.605s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\Fastboot\Fastboot>fastboot flash boot boot.img
sending 'boot' (2572 KB)... OKAY [ 2.282s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
As I mentioned. bootloader is relocked (my bad) so flashing the individual files will not work. Unlocking the bootloader won't work either because for some reason the volume and power keys do not work while in bootloader
Running the 1.33 RUU (RUU_Chacha_HTC_Europe_1.33.401.1_Radio_47.17.35.3033H_7.48.35.14_2_release_204385_signed.exe) returns error 140 Bootloader version error when run with goldkey inserted. Without the goldkey it returns error 131 customer id error... At least the goldkey seems to work but my phone does not accept this version but I can't figure out why.
Strang thing though, the RUU says I currently have version 1.57 which means I'm downgrading to 1.33.
I'm going to try this method: http://forum.xda-developers.com/showthread.php?t=1320392
Thanks so far!!
Ah, bootloader is re-locked.. I missed that part. Bummer... Hope you will find a way. It is really strange that vol. keys do not work.
didije said:
Ah, bootloader is re-locked.. I missed that part. Bummer... Hope you will find a way. It is really strange that vol. keys do not work.
Click to expand...
Click to collapse
Did you disable fastboot in the settings? (Not sure in which part it is... Thought apps)...
If you uncheck the marker, you should be able to enter recovery, etc, again... Worked for me when I had this problem... It wasn't the bootloader that was locked, just me using the fastboot.
When you press vol down+pwr when Fastboot is enabled, you won't see your bootloader screen, it just boots fast...
Maybe worth a try...
Bunnybugs_007 said:
Did you disable fastboot in the settings? (Not sure in which part it is... Thought apps)...
If you uncheck the marker, you should be able to enter recovery, etc, again... Worked for me when I had this problem... It wasn't the bootloader that was locked, just me using the fastboot.
When you press vol down+pwr when Fastboot is enabled, you won't see your bootloader screen, it just boots fast...
Maybe worth a try...
Click to expand...
Click to collapse
Oh my, you must have misunderstood us. He CAN enter the bootloader menu, but he cannot do anything because the bootloader got re-locked (opposite to HTC Dev unlocking - when you enter hboot, bootloader menu or what is called you can see on the top "locked", "unlocked" or in my case "re-locked" - I relocked mine to take it to the service but I didn't thought that it will say RE-locked ) so he cannot flash anything unless he finds a way to unlock it again or s-off the device. That is the problem.
didije said:
... in my case "re-locked" - I relocked mine...
Click to expand...
Click to collapse
I got the same HTC chacha CID: HTC_E11, its something like "Nederlanden" version.
Re-locked don't undo Lock - just simply lock "bootloader".
You will never go back
You should Unlock by "htcdev . com/bootloader/unlock-instructions/page-3"
Then You'll be able to flash via fastboot ,sysem.img, boot.img, recovery.img
i have same problem
NoLimit64 said:
Hi,
I almost bricked my daughter's ChaCha. Half a year ago I unlocked the bootloader to be able to install and run Link2sd to increase performance of the phone and have my daughter have all the apps on it she wants. But a week or so ago the phone started to act up and I decided to take a look.
End of the story is that the phone, when turned on, boots into fastboot automatically but the volume and power keys do not work at all. So I can't select reboot or recovery or anything. I have to remove the battery to switch it off...
Apparently system and recovery are gone cause when I issue 'fastboot oem boot' the response is '(bootloader) [ERR] Boot/Recovery image does not exist!!!'. That can't be good...
The bootloader got relocked in the process of trying to fix it which complicates the problem. Now I can't re-unlock it because the volume and power keys don't work. I can get fastboot in unlock mode but can't select 'yes' and continue because the keys do not work...
I tried re-installing stock rom via RUU with various results. Version 1.33 complains about a customer id (error 131), version 1.13 thinks it's a signature error (error 132) and version 1.18 (I must be desperate) doesn't like the bootloader version (error 140).
I tried creating an old school goldcard to get the phone to accept RUU 1.33 but obviously that failed too. Since I can't get into the phone over adb (only fastboot) I can't get the phone's CID. Also, system is reported to be nonexistent so trying to extract the CID is a dead end anyway.
I think I've tried everything and I'm about to give up. But I thought, before I do that, I better check with the experts here to see if anybody else has a brilliant idea to solve my problem. I'm considering buying the XTC clip but I'm not sure if that will work since the phone is so far gone already. Maybe someone here knows the answer to that?
Below is what 'fastboot getvar all' gives me. Hopefully that helps in answering my question: Is this phone bricked or is there still hope?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.10.0000
(bootloader) version-baseband: 7.51.35.19
(bootloader) version-cpld: None
(bootloader) version-microp: 0557
(bootloader) version-main: 1.57.0.0
(bootloader) serialno: HT16GV409974
(bootloader) imei: 355746042148642
(bootloader) product: chacha
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PH0611000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d86ac222
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
i tried to relock my htc chacha and baaamm. now hboot is locked and dead because no work any volume or power keys in hboot menu. i cant select any option. doesnt work vol+ or vol- or power here. also android os doesnt start normally if i restart to this phone directly opening hboot menu (also doesnt see any device on pc). but only way to access my phone via command. my way is:
1. shutdown phone (only way is remove your battery this status )
2. plug in usb cable your pc and phone
3. dont push to start button only wait until led is on
4. push to red(end call) button
5. now your phone is detected by the pc
6. you can use (phone is power off status still) fasboot commads
7.i use fastboot reboot command and start the phone.
anyway phone is accessible still . i have relocked phone using a nonsafe software i think hboot data damaged. QUESTION IS THAT: HOW CAN WE REPAIR HBOOT ON LOCKED STATUS WITHOUT USING ANY HARDWARE (JTAG OR XTCLIP).
Hi, Iam newone here. So i need your help. I have HTC One SV where it's bricked the only info where i have is :
*** TAMPERED ***
*** UNLOCKED ***
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
OS-311.401.1
eMMC-boot 1024MB
So i tried to restore,nothing happen. fastory reset nothing happen.
I tried to install latest TWRP but it stuck ot logo of TWRP and after 5min it reboots.
I tried to turn s-on to s-off but adb can not find my device.
i tried to the latest ruu nothing again.
i tries to install rom from fastboot but i says that it can not verify signature.
I tried too remove the trampered but again adb can not see my device
HELP PLEASE.....
p.s.: sorry for my english i'm not good.....
If you using win8 try 7 cuz 8 is kind of creepy in recognizing new devices. And make sure you got the right ruu.
I'm sure @Modding.MyMind can help more.
georgekap said:
Hi, Iam newone here. So i need your help. I have HTC One SV where it's bricked the only info where i have is :
*** TAMPERED ***
*** UNLOCKED ***
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
OS-311.401.1
eMMC-boot 1024MB
So i tried to restore,nothing happen. fastory reset nothing happen.
I tried to install latest TWRP but it stuck ot logo of TWRP and after 5min it reboots.
I tried to turn s-on to s-off but adb can not find my device.
i tried to the latest ruu nothing again.
i tries to install rom from fastboot but i says that it can not verify signature.
I tried too remove the trampered but again adb can not see my device
HELP PLEASE.....
p.s.: sorry for my english i'm not good.....
Click to expand...
Click to collapse
Ok, you had already 4.2.2 on it, thats good, no firmwareupgrade needed!
- Make sure bootloader is unlocked.
- Download and flash (with fastboot) TWRP 2.7.0.1 recovery from here (1. post)
Now you should be able to boot into recovery!
You have two ways you can go now:
- Either download this rom (k2ul version) and flash from TWRP. Don't forget, boot.img must be flashed with fastboot, because you are S-on!
- Or download this stock TWRP backup, place it on your external sd and restore it from recovery.
The location on ext_sdcard for the backup is: \TWRP\BACKUPS\"Put here the serial number of your device"
Sorry, just now reading this. Currently having battery issues with my device. May be finally taking a crap on me and since this is my only one I may be forced to get a new device thus possibly leaving this community.... Still playing with my phone to determine if it will be neceassary or not.
Sent from my C525c using Tapatalk
J.ali.li said:
If you using win8 try 7 cuz 8 is kind of creepy in recognizing new devices. And make sure you got the right ruu.
I'm sure @Modding.MyMind can help more.
Click to expand...
Click to collapse
I'm using win ultimate 7 x64
old.splatterhand said:
Ok, you had already 4.2.2 on it, thats good, no firmwareupgrade needed!
- Make sure bootloader is unlocked.
- Download and flash (with fastboot) TWRP 2.7.0.1 recovery from here (1. post)
Now you should be able to boot into recovery!
You have two ways you can go now:
- Either download this rom (k2ul version) and flash from TWRP. Don't forget, boot.img must be flashed with fastboot, because you are S-on!
- Or download this stock TWRP backup, place it on your external sd and restore it from recovery.
The location on ext_sdcard for the backup is: \TWRP\BACKUPS\"Put here the serial number of your device"
Click to expand...
Click to collapse
I tried to flash twrp but it stuck on htc and at the top it is writes entering recovery...
i tried an other one twrp 2.7.0.1 but it stucks on teamwin and after few min it reboot back to htc logo.
Have you also tried the older version Recovery_TWRP_2.6.3.2_K2_UL.img from same post?
How do you flash it?
old.splatterhand said:
Have you also tried the older version Recovery_TWRP_2.6.3.2_K2_UL.img from same post?
How do you flash it?
Click to expand...
Click to collapse
from fastboot with this command fastboot flash recovery reovery.img
i tried and the older version but it stuck on htc logo with on the top writes entering recovery
georgekap said:
from fastboot with this command fastboot flash recovery reovery.img
i tried and the older version but it stuck on htc logo with on the top writes entering recovery
Click to expand...
Click to collapse
from fastboot with this command fastboot flash recovery recovery.img *
i tried to flash the rom k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from the phone.
i rename it pl80img.zip. and now is stuck on htc logo and reboots
Then i think your phone has another issue. Both recoveries are proved working for k2u & k2ul.
This rom is for flashing in recovery, not for the bootloader.
old.splatterhand said:
Then i think your phone has another issue. Both recoveries are proved working for k2u & k2ul.
This rom is for flashing in recovery, not for the bootloader.
Click to expand...
Click to collapse
when i flash recovery from fastboot. whene im try to get in recovery mode after how many min its boot to recovery?
No minutes, just a few seconds.
old.splatterhand said:
No minutes, just a few seconds.
Click to expand...
Click to collapse
How can i downgrade os???
Not possible without a working OS.
@ old.splatterhand
I have same problem k2_ul. phone just restart after 10 sec
i try hard reset, enter recovery with TWRP but nothing happened .
what should i do at now?
More detailed please.
The phone restarts after booting?
After you have entered the pin number?
Also without simcard/sdcard/plugged into charger (while charging)?
Which OS you are running?
Which TWRP?
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
This is fastboot info.
phone not getting to booting.just htc logo 10 sec then again restart phone continue.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.415.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT313Txxxx
(bootloader) imei: 3528xxxxxxxxx
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3655mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
Please remove also your serial number.
You are able to enter recovery or not?
Post the link, where you've got the recovery from?
no i cant recovery mode.
i try many recovery.img but when i enter recovery its just give me "entering recovery" logo!!
Use this recovery.
Hey there XDA, I have a strange problem. Maybe you can help me out.
I just got my Moto G today and after unlocking the bootloader, the first thing I did was flash TWRP (fastboot flash recovery TWRP-2.7.0.0-falcon.img).
I did this with the normal fastboot from the Android SDK, not the Motorola version.
Now everytime I start the device, it always boots right into recovery. Always. Doesn't matter if there's TWRP, CWM or Stock installed.
I also flashed the device to GPE afterwards (using the Motorola fastboot) which should've erased everything, but it still does it.
The only way I can get into the actual system is by flashing the normal boot.img as recovery (fastboot flash recovery boot.img).
Can someone please shed some light on this for me? I'd be eternally grateful.
Thanks in advance.
Kenny
twofive said:
Hey there XDA, I have a strange problem. Maybe you can help me out.
I just got my Moto G today and after unlocking the bootloader, the first thing I did was flash TWRP (fastboot flash recovery TWRP-2.7.0.0-falcon.img).
I did this with the normal fastboot from the Android SDK, not the Motorola version.
Now everytime I start the device, it always boots right into recovery. Always. Doesn't matter if there's TWRP, CWM or Stock installed.
I also flashed the device to GPE afterwards (using the Motorola fastboot) which should've erased everything, but it still does it.
The only way I can get into the actual system is by flashing the normal boot.img as recovery (fastboot flash recovery boot.img).
Can someone please shed some light on this for me? I'd be eternally grateful.
Thanks in advance.
Kenny
Click to expand...
Click to collapse
on the custom recovery menu screen, when you press REBOOT then REBOOT SYSTEM, does it? Or does it just reboot back into recovery?
3RAN7ON said:
on the custom recovery menu screen, when you press REBOOT then REBOOT SYSTEM, does it? Or does it just reboot back into recovery?
Click to expand...
Click to collapse
It boots right back into Recovery. It always does that, no matter if I do it from the OS, the bootloader, whatever.
Have you tried flashing through fastboot the update for your device ?
twofive said:
Hey there XDA, I have a strange problem. Maybe you can help me out.
I just got my Moto G today and after unlocking the bootloader, the first thing I did was flash TWRP (fastboot flash recovery TWRP-2.7.0.0-falcon.img).
I did this with the normal fastboot from the Android SDK, not the Motorola version.
Now everytime I start the device, it always boots right into recovery. Always. Doesn't matter if there's TWRP, CWM or Stock installed.
I also flashed the device to GPE afterwards (using the Motorola fastboot) which should've erased everything, but it still does it.
The only way I can get into the actual system is by flashing the normal boot.img as recovery (fastboot flash recovery boot.img).
Can someone please shed some light on this for me? I'd be eternally grateful.
Thanks in advance.
Kenny
Click to expand...
Click to collapse
You could try re flashing the stock firmware. http://forum.xda-developers.com/showthread.php?t=2542219 Good luck, it will delete everything on the phone.
Sent from my Moto G using XDA Free mobile app
twofive said:
It boots right back into Recovery. It always does that, no matter if I do it from the OS, the bootloader, whatever.
Click to expand...
Click to collapse
hmmm....something similar happened to me about 2 days ago when I DL the ota, then tried to install it, but it failed. the phone rebooted into the system and a minute later it roobooted itsself back into recovery and tried to install the update again. Of course, the ota's are DL to the /cache folder by default, but once install is attempted, it erases it from that folder, but phone kept rebooting and trying to install, it failed then rebooted again into recovery. It did this like 5x until I was able to stop this by restoring a prev backup. Not sure if this is your situation, but in posting this experience it might help someone
---------- Post added at 09:53 AM ---------- Previous post was at 09:44 AM ----------
Also, check in your recovery if there is something called 'DISABLE RECOVERY FLASH' and make sure it is checked before rebooting the first time after installing recovery. I maybe mistaking, but I thought it was a bug only found on some earlier CWM builds, not found on TWRP...but recovery flash would make the phone do what you are describing
twofive said:
Hey there XDA, I have a strange problem. Maybe you can help me out.
I just got my Moto G today and after unlocking the bootloader, the first thing I did was flash TWRP (fastboot flash recovery TWRP-2.7.0.0-falcon.img).
I did this with the normal fastboot from the Android SDK, not the Motorola version.
Now everytime I start the device, it always boots right into recovery. Always. Doesn't matter if there's TWRP, CWM or Stock installed.
I also flashed the device to GPE afterwards (using the Motorola fastboot) which should've erased everything, but it still does it.
The only way I can get into the actual system is by flashing the normal boot.img as recovery (fastboot flash recovery boot.img).
Can someone please shed some light on this for me? I'd be eternally grateful.
Thanks in advance.
Kenny
Click to expand...
Click to collapse
You shouldn't have that issue, but you might have to try the latest 2.6.x branch of TWRP. I've seen both but never know which one is really better.
Also, why use the GPE edition? The moto stuff in the moto g is better than the google equivalents, especially the camera app and moto assist, but to each his own.
sprockkets said:
Also, why use the GPE edition? The moto stuff in the moto g is better than the google equivalents, especially the camera app and moto assist, but to each his own.
Click to expand...
Click to collapse
I also own a Nexus 5, Xperia Z Ultra flashed to GPE, and a Nexus 7. I just like having the same Software on all of them.
Hey try this.
twofive said:
I also own a Nexus 5, Xperia Z Ultra flashed to GPE, and a Nexus 7. I just like having the same Software on all of them.
Click to expand...
Click to collapse
https://docs.google.com/file/d/0Bx3fLPcfAf3BcmRmdENLWHhPaDQ/edit?pli=1
http://forum.xda-developers.com/showthread.php?t=2746401
Booting to recovery (twrp&cmw) when rebooting to system
twofive said:
hey there xda, i have a strange problem. Maybe you can help me out.
I just got my moto g today and after unlocking the bootloader, the first thing i did was flash twrp (fastboot flash recovery twrp-2.7.0.0-falcon.img).
I did this with the normal fastboot from the android sdk, not the motorola version.
Now everytime i start the device, it always boots right into recovery. Always. Doesn't matter if there's twrp, cwm or stock installed.
I also flashed the device to gpe afterwards (using the motorola fastboot) which should've erased everything, but it still does it.
The only way i can get into the actual system is by flashing the normal boot.img as recovery (fastboot flash recovery boot.img).
Can someone please shed some light on this for me? I'd be eternally grateful.
Thanks in advance.
Kenny
Click to expand...
Click to collapse
dear all,
pls help me.. I'm facing the same problem when i'm rebooting system from my recovery screen and it's rebooting to recovery . I cannot find any relevant solution for this anywhere. So please help me. I'm using moto g falcon (xt1033)
princehpd said:
dear all,
pls help me.. I'm facing the same problem when i'm rebooting system from my recovery screen and it's rebooting to recovery . I cannot find any relevant solution for this anywhere. So please help me. I'm using moto g falcon (xt1033)
Click to expand...
Click to collapse
Which version you were before that i mean lollipop or marshmallow and stock or custom roms?
Cyanogenmod 13
abhi0502 said:
Which version you were before that i mean lollipop or marshmallow and stock or custom roms?
Click to expand...
Click to collapse
BEFORE ROOTING I WAS ON ANDROID LOLLIPOP AND AFTER THAT I FLASHED CYANOGENMOD 13. RECENT ONE WAS CrDROID BASED ON ANDROID MARSHMALLOW. PLS HELP..
Ok I now have this problem also
Even flashing stock rom does not fix it.
Does anyone have any suggestions ??
The phone will say boot loader unlocked as usu then black screen then flashes stock recovery no command screen , then the device turns off. I can access boot loader mode !
That's about all I have :/
Any help would be greatly appreciated
I have the same problem, or similar. I installed CM13 but it didn't like me so much and when I wanted to reboot the phone to restore my previous backup I went to "Advanced reboot menu" and then just reboot recovery. And the phone never could boot again to system, I tried flashing 5.1 and various recoveries but nothing happended.
As nobody responses my trhead I was obliged to send my Moto G to an unofficial customer service, I have to go today to take up my phone, it should be ready, I hope.
Good luck, if they told me how they fixed it I'll post here.
Ok I think I may have found the fix. Flash all of the stock files normally , then flash boot.img once more. Then the phone will boot normally but only for one time. Quickly run though setup , then in the setting app factory reset your device. Your device will reboot and reset once more. Then the device will always boot normal This actually seems to work. I spent all night yesterday trying to fix my device and I finally found the solution. ! ��
therealduff1 said:
Ok I think I may have found the fix. Flash all of the stock files normally , then flash boot.img once more. Then the phone will boot normally but only for one time. Quickly run though setup , then in the setting app factory reset your device. Your device will reboot and reset once more. Then the device will always boot normal This actually seems to work. I spent all night yesterday trying to fix my device and I finally found the solution. ! ��
Click to expand...
Click to collapse
Man, I did that but it didn't work for me. Now when I reboot from fastboot the device power up directly to fastboot mode and on the log it shows
Fastboot reason: UTAG "bootmode" configured as fastboot
Anyway if I powerup from fastboot mode the phone sucks on the bootloader screen.
I had the same problem and was searching from this noon. Just now, i downloaded and flashed with Cyanogen Recovery "cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon-recovery" and my problem is over now. Tried a couple of power off and restarts and now my reboots and power on will not go to recovery any more.
File is available to download at cyanogenmod website
Please make sure about your model before download. I use a Moto G 2013 XT1033 Asia Retail edition with 8GB.
I tried installing that recovery but I'm getting the exact same issue...
Any other solution? No one has solved it yet?
I got the same problem here.. My Moto G default boot is to recovery. The way i could enter the rom is with Bootloader option "Normal powerup". I already try many ways, reflash custom recovery (TWRP, CWM, CM), reflash stock, and reflash custom rom, but they do nothing to this case. Is there any way to change it back to normal? I'm currently on CM 12.1 Unofficial and running TWRP 2.8.6.0. It is not panic attack, it just anoying. Thanks in advance..
same here.. booting always into recovery by default..
tried different twrp versions (incl. 2.8.7), CWM and cyanogen recovery.. and also tried wiping the complete system.. reinstalling stock rom incl. bootloader, recovery, etc..
everytime the same boot into recovery by default
using "fastboot reboot" in bootloader mode also boots into recovery
in bootloadermode i'm able to boot my fresh installed CM12.1 by selecting "Normal Powerup"
maybe something happened with the bootloader configuration? where to edit it?
this also did not help:
mfastboot oem fb_mode_clear
Click to expand...
Click to collapse
(as i understand.. this just clears the fb_mode_set value.. which directs to bootloader on boot
edit:
# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 66FFC4020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 19 2:19:55 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 19:06:25 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 2/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.057s
Click to expand...
Click to collapse
S-off ONLY!!
As many of you are aware, flashing roms to our phone comes with risk. That risk is dimished by the availability of an RUU for our phone.
I have created as much of an RUU as we can put together at this point. This is for s-off users only. I repeat...s-off only.
This zip is an RUUmode/hboot flashable stock RUUish compilation of the current boot/hboot/system/recovery/radio/firmware images. Just like an RUU... this WILL wipe your phone (internal memory). IF you are able...backup data prior to using this. This works EXACTLY like an RUU for s-off users. Two options exist for using this zip. This will land you on STOCK kitkat 4.4.3 pre-rooted with stock recovery. I have tested this on my kid's wife's M8 (she has no choice... ).
NOTE...HTC started preloading some files to /data on the latest Rom. There's not a clean way to add them to an ruu so please flash the following file in recovery after getting your phone back to stock. If you don't, the only problem would be that gallery is missing the sticker files under edit.
If coming from 4.4.4 firmware you will need to flash 4.4.3. in RUU mode prior to flashing this..
- https://www.androidfilehost.com/?fid=23622183712470028
Option 1
Copy 0P6BIMG.zip to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
Option 2 (Might not be working!)
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now either do one of two things 1)##reboot or 2)flash a custom recovery. IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
Optional If you wish to flash a custom recovery before leaving RUU mode you can. This is helpful if you have relocked for any reason as you CAN flash a recovery using this method while locked (since s-off). Download the ruuM8TWRP_2_7_1.zip below and place it in your working fastboot/adb directory. Once in place, issue the following command.
fastboot flash zip ruuM8_TWRP_2_7_1.zip
##example output
C:\Users\dottat\Downloads\mini-sdk-1.0.31-windows>fastboot flash zip ruuM8_TWRP_2_7_1.zip
target reported max download size of 1830711296 bytes
sending 'zip' (11756 KB)...
OKAY [ 1.404s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=1
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,7
(bootloader) [RUU]UZ,recovery,13
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,27
(bootloader) [RUU]UZ,recovery,36
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,62
(bootloader) [RUU]UZ,recovery,69
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,84
(bootloader) [RUU]UZ,recovery,90
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 3.713s]
finished. total time: 5.117s
Once completed you can issue the command "fastboot reboot-bootloader" to return to hboot so you can enter recovery.
Downloads Do NOT mirror these elsewhere.
RUU link
- https://www.androidfilehost.com/?fid=23622183712470087
md5 f223e75d24266c379849e9e4a606f3d1
RUU Mode TWRP 2.8
- https://www.androidfilehost.com/?fid=23622183712470114
md5 2c654e1eadc0c3f3d1477591fb4e84b7
Stickers Fix
- http://www.androidfilehost.com/?fid=23329332407590188
md5 dda3713d8d0c4b50a1c80814c8bd07c5
HTC backup app (highly recommend this gem)
- http://www.androidfilehost.com/?fid=23329332407589902
md5 b7ec08c021b5fb8b1b86a0ab3535c1dd
mine................
You had me all excited for a minute!!! Great to see your getting ready tho. Thanks for all of your hard work.
Sweet!
Nice!.... Your last ruu saved my a$$!
ughhhh, i almost wet my pants
Sweet
Oh yes, the new 4.4.3 firmware we've all been waiting for....
nope! Just dottat (in my Chuck Testa voice)
JWhetstone02 said:
Oh yes, the new 4.4.3 firmware we've all been waiting for....
nope! Just dottat (in my Chuck Testa voice)
Click to expand...
Click to collapse
You guys crack me up. Enjoying the wait eh?
dottat said:
You guys crack me up. Enjoying the wait eh?
Click to expand...
Click to collapse
Patience is a virtue... Unfortunately, not one of mine.
Well played, almost had me ready to leave work early and head home hahaha
JediMindTrixx said:
Patience is a virtue... Unfortunately, not one of mine.
Click to expand...
Click to collapse
Hah... you don't have to explain... I DID get my moto 360 this weekend.. so i understand completely
dottat said:
Hah... you don't have to explain... I DID get my moto 360 this weekend.. so i understand completely
Click to expand...
Click to collapse
I know its off topic but since we are waiting, what are your thoughts on the moto 360 so far?
JediMindTrixx said:
Patience is a virtue... Unfortunately, not one of mine.
Click to expand...
Click to collapse
Bwuahahaha I hear that @JediMindTrixx I've been patient for far to long. Hope soon it's released. No more 4min wait boot up*yaay*.
Sent from my Insanely powered M8 using Tapatalk
Code:
[QUOTE="dottat, post: 55361775, member: 3472611"][B][SIZE="5"]S-off ONLY!![/SIZE][/B]
As many of you are aware, flashing roms to our phone comes with risk. That risk is dimished by the availability of an RUU for our phone.
I have created as much of an RUU as we can put together at this point. This is for s-off users only. I repeat...s-off only.
This zip is an RUUmode/hboot flashable stock RUUish compilation of the current boot/hboot/system/recovery/radio/firmware images. Just like an RUU... this WILL wipe your phone (internal memory). IF you are able...backup data prior to using this. This works EXACTLY like an RUU for s-off users. Two options exist for using this zip. This will land you on STOCK kitkat 4.4.3 pre-rooted with stock recovery. I have tested this on my [STRIKE]kid's[/STRIKE] wife's M8 (she has no choice... :)).
NOTE...HTC started preloading some files to /data on the latest Rom. There's not a clean way to add them to an ruu so please flash the following file in recovery after getting your phone back to stock. If you don't, the only problem would be that gallery is missing the sticker files under edit.
[B][SIZE="5"]Option 1[/SIZE][/B]
Fastboot RUU mode (preferred). This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
[HIDE][/HIDE]
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now either do one of two things 1)##reboot or 2)flash a custom recovery. IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
[B]Optional[/B] If you wish to flash a custom recovery before leaving RUU mode you can. This is helpful if you have relocked for any reason as you CAN flash a recovery using this method while locked (since s-off). Download the ruuM8TWRP_2_7_1.zip below and place it in your working fastboot/adb directory. Once in place, issue the following command.
fastboot flash zip ruuM8_TWRP_2_7_1.zip
##example output
[HIDE]C:\Users\dottat\Downloads\mini-sdk-1.0.31-windows>fastboot flash zip ruuM8_TWRP_2_7_1.zip
target reported max download size of 1830711296 bytes
sending 'zip' (11756 KB)...
OKAY [ 1.404s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=1
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,7
(bootloader) [RUU]UZ,recovery,13
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,27
(bootloader) [RUU]UZ,recovery,36
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,62
(bootloader) [RUU]UZ,recovery,69
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,84
(bootloader) [RUU]UZ,recovery,90
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 3.713s]
finished. total time: 5.117s[/HIDE]
Once completed you can issue the command "fastboot reboot-bootloader" to return to hboot so you can enter recovery.
[B][SIZE="5"]Option 2[/SIZE][/B]
Copy 0P6BIMG.zip to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
[B]Downloads[/B]
[B]RUU link [/B]
[url]pending[/url]
md5
[B]RUU Mode TWRP 2.7.1[/B]
[url]https://www.androidfilehost.com/?fid=23622183712469358[/url]
md5 db77a00008eed750b4900f4c1ebb59a8
[B]Stickers Fix[/B]
[url]http://www.androidfilehost.com/?fid=23329332407590188[/url]
md5 dda3713d8d0c4b50a1c80814c8bd07c5
[B]HTC backup app (highly recommend this gem)[/B]
[url]http://www.androidfilehost.com/?fid=23329332407589902[/url]
md5 b7ec08c021b5fb8b1b86a0ab3535c1dd[/QUOTE]
So, what improvements are made with this, what will it change, how dangerous is it, and will it affect me on AOSP roms?
bracketslash said:
Code:
So, what improvements are made with this, what will it change, how dangerous is it, and will it affect me on AOSP roms?
Click to expand...
Click to collapse
They added more bacon, the version number will change, dwarves may eat your cat but other than that you're safe, and finally no it shouldn't affect aosp unless your cat maintains the device in which case being eaten by a dwarf will hamper releases.
bracketslash said:
Code:
So, what improvements are made with this, what will it change, how dangerous is it, and will it affect me on AOSP roms?
Click to expand...
Click to collapse
This is the latest article I could find that explains most of the changes. Hope this helps.
http://www.android.gs/verizon-htc-one-m8-android-4-4-3-update-available-now-for-download/
mademan420 said:
I know its off topic but since we are waiting, what are your thoughts on the moto 360 so far?
Click to expand...
Click to collapse
My daily driver phone is a one max.. so far.. my moto 360 and my one max seem to be linked on battery life. At the end of the day, I have almost half of the battery on each device left. I have my moto 360 screen not set to that mode that keeps the screen on all the time. I like it. It does exactly what i was hoping it would and it's not killing the battery.
Nandroid Backup Beforehand
This may be stupid but would I be able to flash the RUU and then restore a nandroid i made right before to get all my data and apps etc back on the phone with the new firmware??
Seanzle said:
This may be stupid but would I be able to flash the RUU and then restore a nandroid i made right before to get all my data and apps etc back on the phone with the new firmware??
Click to expand...
Click to collapse
I do it that way when i'm on a stock rom that i've made changes to that i'm too lazy to undo... If it's very close to stock, usually restoring just /data works fine. Alternatively, you can use the HTC backup app in the OP to have your texts/email accounts/desktop/apps(no app data)/etc backed up.
Hi guys, so a while ago I flashed Venom Rom to my one s c2.
In the recent weeks I noticed, that the memory was getting more and more full. But I couldn't find the files responsible for that.
So I did a factory reset, which didn't help. So I tried to wipe the storage in TWRP 2.6.3.0. . Furthermore I did a "total wipe" so I checked every option in the wipe section.
After that, I couldn't boot the phone, because there seemed to be no OS installed. So i tried to flash the ROM which I loaded onto the phones storage but it was gone.
When I tried to transfer a ROM to the phone's storage it said "unable to mount sdcard". So I couldn't transfer any files to my phone.
After hours of reading through various threads, I tried to get it back to stock by running a RUU.
Unfortunately I couldnt find the exact one for my device. This is what fastboot displays when i type in "fastboot getvar all":
version: 0.5
version-bootloader: 3.01.0000
version-baseband: 16.15.20.29_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: SH25YW404475
imei: 352762055439276
meid:
product: villec2
platform: HBOOT-8260
modelid: PJ4020000
cidnum: HTC__102
battery-status: good
battery-voltage: 4014mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 9006d003
hbootpreupdate: 11
gencheckpt: 0
So I tried these ones (tried running as administrator as well):
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.09.401.101_Radio_16.11.20.02U_16.05.20.11_M2_release_261381_signed
and
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.101_Radio_16.12.20.02U_16.05.20.16_M2_release_261661_signed
But they didnt work out. It always displays "error 155" and on the phone's display it says "older hboot version" .
And now I can't even access the recovery anymore... And because I tried to run a RUU I relocked my bootloader....
I really can't find a RUU with the correct Radio and don't know how to identify the hboot version of the RUU.
I already tried to flash a recovery again via fastboot, but it didn't work as well :
C:\*****\platform-tools>fastboot flash recovery twrpvillec2.img
sending 'recovery' (6420 KB)...
OKAY [ 1.291s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.079s
I'm really lost guys, I hope I didn't hardbrick my phone.
If anyone has any suggestions, please help.
Thanks!
maybe you can try this rom http://androidruu.com/download.php?...326a10c55adc0bf34ecb3f5611d8b1015471164225450 "RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe"
you must have your bootloader relock to use a run. and unlock to flash a custom recovery
JavierG123 said:
maybe you can try this rom http://androidruu.com/download.php?...326a10c55adc0bf34ecb3f5611d8b1015471164225450 "RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe"
you must have your bootloader relock to use a run. and unlock to flash a custom recovery
Click to expand...
Click to collapse
Thanks for your suggestion!
I tried the RUU, but it didnt work out. Still Error 155 and the phone says "Hboot Version is older" ...
How can I read the HBOOT Version in the filename, anyway?
But running a RUU is the correct and only way to go in my situation, isnt it?
So, as I already knew, the problem was the hboot Version of my device...
So I'm now trying to downgrade my hboot version and try one of the RUUs again...
So...downgrading Bootloader doesnt work... tried every hboot version listed in this post
Maybe trying a JB RUU, which doesnt really fit all the other requirements...trying that now
Still no success, since I can't find a unbranded JB RUU fitted for my phone....
running out of ideas here...
anyone else got any suggestions?
btw: I reflashed twrp 2.6.3.0. but still cant access the internal sd...cant even mount it.
DonKaio said:
Hi guys, so a while ago I flashed Venom Rom to my one s c2.
In the recent weeks I noticed, that the memory was getting more and more full. But I couldn't find the files responsible for that.
So I did a factory reset, which didn't help. So I tried to wipe the storage in TWRP 2.6.3.0. . Furthermore I did a "total wipe" so I checked every option in the wipe section.
After that, I couldn't boot the phone, because there seemed to be no OS installed. So i tried to flash the ROM which I loaded onto the phones storage but it was gone.
When I tried to transfer a ROM to the phone's storage it said "unable to mount sdcard". So I couldn't transfer any files to my phone.
After hours of reading through various threads, I tried to get it back to stock by running a RUU.
Unfortunately I couldnt find the exact one for my device. This is what fastboot displays when i type in "fastboot getvar all":
version: 0.5
version-bootloader: 3.01.0000
version-baseband: 16.15.20.29_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: SH25YW404475
imei: 352762055439276
meid:
product: villec2
platform: HBOOT-8260
modelid: PJ4020000
cidnum: HTC__102
battery-status: good
battery-voltage: 4014mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 9006d003
hbootpreupdate: 11
gencheckpt: 0
So I tried these ones (tried running as administrator as well):
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.09.401.101_Radio_16.11.20.02U_16.05.20.11_M2_release_261381_signed
and
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.101_Radio_16.12.20.02U_16.05.20.16_M2_release_261661_signed
But they didnt work out. It always displays "error 155" and on the phone's display it says "older hboot version" .
And now I can't even access the recovery anymore... And because I tried to run a RUU I relocked my bootloader....
I really can't find a RUU with the correct Radio and don't know how to identify the hboot version of the RUU.
I already tried to flash a recovery again via fastboot, but it didn't work as well :
C:\*****\platform-tools>fastboot flash recovery twrpvillec2.img
sending 'recovery' (6420 KB)...
OKAY [ 1.291s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.079s
I'm really lost guys, I hope I didn't hardbrick my phone.
If anyone has any suggestions, please help.
Thanks!
Click to expand...
Click to collapse
You need to unlock your bootloader again than flash the stock recovery there you can make a factory reset and than your storage is back if you need the stock recovery
Or stock backup than say it...
pauldey said:
You need to unlock your bootloader again than flash the stock recovery there you can make a factory reset and than your storage is back if you need the stock recovery
Or stock backup than say it...
Click to expand...
Click to collapse
Yes please, I actually do have some older backups, but I don't know how to flash them since I can't move files to the phone anymore.
Thanks for your help!
i can suggest you install SaM ROM. this is the threat http://forum.xda-developers.com/htc-one-s/c2-development/rom-sam-rom-sense-7-blinkfeed-t3117135 using this recovery http://file.mikhei777.org.ua/HTC_VilleC2/openrecovery-twrp-2.7.1.0-villec2.img
DonKaio said:
Yes please, I actually do have some older backups, but I don't know how to flash them since I can't move files to the phone anymore.
Thanks for your help!
Click to expand...
Click to collapse
hey, here is the stock recovery:https://www.dropbox.com/s/qavj4ythvc0v4gg/recovery.img?dl=0
you need to unlock your booloader again, than go to fastboot and flash the recovery like every other: fastboot flash recovery recovery.img than: fastboot erase cache and fastboot reboot-bootloader
than you go in the stock recovery there you can make a factory reset
here you find all how you can use the stock recovery: http://llabtoofer.com/2014/02/24/how-to-manually-install-ota-updates/
and than you can flash the recovery from my backup folder after this you can mount your sd card and push the stock backup on your phone and restore the backup
and here the stock backup: https://www.dropbox.com/s/hhggqd1gith8pkf/4.1.1%20stock%20rom%20C2%20TWRP%202.6.3.0.rar?dl=0
pauldey.
Thanks guys, worked great!
Awesome!
I have the same problem. In adb devices I see some serial and 'recovery', maybe its the phone, but I got an error when tried to move another file into phone.
I've tried to unlock it again but I that code to use it in bootloader is not showing up.