Hey,
I have JB 4.1.2 by bruce2728 version 10-20121114 kernel 3.0.51-jelly-00183-g0707900-dirty [email protected] #1.
I want to to upgrade to 4.2.x but no version works(I tried almost all latest versions from:
http://bruce2728.mabsoft.dk/
Then I tried to install KANG 4.2.2 from this thread:
http://forum.xda-developers.com/showthread.php?t=2115520,
after installation the system did not start (just HTC logo and nothing happened more).
. After wipe/factory reset all the version did not work.
Where could be problem? old firmware?
Please help, gonna crazy
vasek2 said:
Hey,
I have JB 4.1.2 by bruce2728 version 10-20121114 kernel 3.0.51-jelly-00183-g0707900-dirty [email protected] #1.
I want to to upgrade to 4.2.x but no version works(I tried almost all latest versions from:
http://bruce2728.mabsoft.dk/
Then I tried to install KANG 4.2.2 from this thread:
http://forum.xda-developers.com/showthread.php?t=2115520,
after installation the system did not start (just HTC logo and nothing happened more).
. After wipe/factory reset all the version did not work.
Where could be problem? old firmware?
Please help, gonna crazy
Click to expand...
Click to collapse
if you are S-ON install 4ext recovery(if you don't have it already)
enable smartflash from it
flash the rom
Hi, Could we know your about in settings, and your Hboot Settings (VolDown + PowBtn) read and write informations..
After that we can helps u
Related
I am using MIUI zero 2.11.30 by ahmedsalahais. (http://forum.xda-developers.com/showthread.php?t=2016648)
I saw that our ds is officially supported by MIUI and I wanted to give a try to install official release just for curiosity. I tried to flash miuiandroid.com 2.11.30 version but it does not boot. It is stuck with a black screen.
Then I followed this tutorial: http://miuiandroid.com/community/threads/tutorial-for-installing-miui-v4-desire-s.17470/
I installed official ICS using this guide: http://forum.xda-developers.com/showthread.php?t=1858508
After official ICS, I flashed official MIUI 2.11.30. This time MIUI boot animation logo appeared. But I didn't succeed to boot again. I tried releases from miui.us, miui.com china but I did not succed to boot successfully with these official releases.
What am I missing? Why miuiandroid version needs stock 4.0 for desire s and specific hboot version, I did not understand but anyway I followed the steps but no luck. Can you tell me how to flash an official MIUI release (for example: 2.11.30) successfully? I will be glad if you help about this issue.
My HBOOT version is 7.00.1002 now
RADIO: 3831.17.310
I am S-OFF
here follow my tutorial and then just flash this rom and kernal http://forum.xda-developers.com/showthread.php?t=1678485
ben_s247 said:
here follow my tutorial and then just flash this rom and kernal http://forum.xda-developers.com/showthread.php?t=1678485
Click to expand...
Click to collapse
Which tutorial?
sorry forgot to post the link
http://forum.xda-developers.com/showthread.php?t=2021403
zihinsiz said:
I am using MIUI zero 2.11.30 by ahmedsalahais. (http://forum.xda-developers.com/showthread.php?t=2016648)
I saw that our ds is officially supported by MIUI and I wanted to give a try to install official release just for curiosity. I tried to flash miuiandroid.com 2.11.30 version but it does not boot. It is stuck with a black screen.
Then I followed this tutorial: http://miuiandroid.com/community/threads/tutorial-for-installing-miui-v4-desire-s.17470/
I installed official ICS using this guide: http://forum.xda-developers.com/showthread.php?t=1858508
After official ICS, I flashed official MIUI 2.11.30. This time MIUI boot animation logo appeared. But I didn't succeed to boot again. I tried releases from miui.us, miui.com china but I did not succed to boot successfully with these official releases.
What am I missing? Why miuiandroid version needs stock 4.0 for desire s and specific hboot version, I did not understand but anyway I followed the steps but no luck. Can you tell me how to flash an official MIUI release (for example: 2.11.30) successfully? I will be glad if you help about this issue.
My HBOOT version is 7.00.1002 now
RADIO: 3831.17.310
I am S-OFF
Click to expand...
Click to collapse
Just flash it how u would flash any other rom. Put the zip in the sd, clean wipe, install, reboot.
edit : bankup 1st before all else, always a must.
ben_s247 said:
sorry forgot to post the link
http://forum.xda-developers.com/showthread.php?t=2021403
Click to expand...
Click to collapse
rain987 said:
Just flash it how u would flash any other rom. Put the zip in the sd, clean wipe, install, reboot.
edit : bankup 1st before all else, always a must.
Click to expand...
Click to collapse
I know how to flash a rom normally. But this time, for official miui it didn't work. I wanted to learn if there are any different steps when flashing miui. But now my problem has solved. I formatted all partitions three times, wiped data, cache and dalvik, flashed the official miui rom from miuiandroid.com and magically it booted.
Hi to All,
I want to share my experience about revert to stock for users that have new HBOOT, unlocked bootloader and custom recovery; can't execute official RUU. ( This method i think is more safe that downgrade HBOOT )
Step ONE:
Install this custom ROM: MaximuS ROM ( read the thread for instruction about installation of this ROM )
( this ROM allow you to receive the message of OTA JB update, if you know another ROM that receive this message you can use as well i think )
Step TWO:
install the stock recovery of HTC One S via fastboot ( after flashing recovery erase cache )
Step THREE:
Reboot your phone in system, configure the rom for first use, go to settings, information, software update and press check now for update.
You'll receive the message for an update, download and install, and now you have stock JB ROM. after reboot you can do a reset ( go to setting => backup and restore ) to clean the application migrated from previous ROM ( MaximuS )
I hope this can help someone else.
p.s. Sorry for my English!
Thanks bro for this, but my problem is not resolved because this rom couldn't install on my HTC One S, i dont know why... Log show me: MD5 files not found
CybulPL said:
Thanks bro for this, but my problem is not resolved because this rom couldn't install on my HTC One S, i dont know why... Log show me: MD5 files not found
Click to expand...
Click to collapse
Witch recovery are you using at the moment? I installed this ROM ( MaximuS ) with Team Win Recovery ( TWRP ) v2.3.3.0 and it's works for me.
( after flashing ROM from recovery remember to flash boot.img by fastboot )
Maverick87Shaka said:
Witch recovery are you using at the moment? I installed this ROM ( MaximuS ) with Team Win Recovery ( TWRP ) v2.3.3.0 and it's works for me.
( after flashing ROM from recovery remember to flash boot.img by fastboot )
Click to expand...
Click to collapse
I use TWRP and CWM and the same. My mate told me that i have unmount 1 and 2 partition in recovery but i don't know how.
Hi everyone,
thanks a lot, this saved my ass ... I had upgraded my stock ICS to stock JB and then tried to go back to stock ICS with a CWM backup - with the result that I had a brick booting only to a black screen.
I still had access to CWM recovery and so could install the Maximus 2.5 ROM and also the update to stock JB ran through just fine.
I did a factory reset afterwards, is it 100% sure that I now have a pure stock JB or could there be some leftovers from the Maximus 2.5 ROM?
Cheers,
Tim
tim_h said:
Hi everyone,
I still had access to CWM recovery and so could install the Maximus 2.5 ROM and also the update to stock JB ran through just fine.
I did a factory reset afterwards, is it 100% sure that I now have a pure stock JB or could there be some leftovers from the Maximus 2.5 ROM?
Cheers,
Tim
Click to expand...
Click to collapse
Yes you have a stock JB, because with factory reset you've removed all extra application that there is inside MaximuS v.2.5.
All other unneeded file or executable ( like root executable and all other script in /system ect. ) was removed during installation of new ROM.
Remember just that you need to revert to stock to give your phone back to HTC for guarantee, I thinks you must leave on it the stock recovery.
tim_h said:
Hi everyone,
thanks a lot, this saved my ass ... I had upgraded my stock ICS to stock JB and then tried to go back to stock ICS with a CWM backup - with the result that I had a brick booting only to a black screen.
Cheers,
Tim
Click to expand...
Click to collapse
It's happened because from recovery the system was unable to flash the boot partition. So after you did the CWM restore, you have all the phone with ICS android, but JB kernel, this cause your black screen after boot!!!
If you have the boot.img ( with suitable kernel of your old ROM ) to flash after you did the CWM recovery, you can get back to your BACKUP without any problem.
Also if you don't have the exactly boot.img of your previous ROM of the backup, you can flash any boot.img by fastboot of ICS kernel and this is should be enough to keep your backup running again.
Thanks very much for the additional explanations. I do have the boot.img of my original CWM backup, so should be able to restore it via fastboot. Great!
But first I have to send in my phone to have the USB port fixed under warranty.
Holy ****, is working, thanks man...
zujko said:
Wait to see if i understood, i have now Custom ( Virtuous Ville+ RC-1) JB ROM, with hboot 2.15.0000... unlocked, root, twrp
1.install maximuS V2.5, wipe..
2. flash boot.img with fastboot
3.Check update for JB, and flash new update JB?
And that's it?
I guess we have to make relock bootloader, after flash ICS?
Tnx
Click to expand...
Click to collapse
You just forgot in the list to install the HTC Stock recovery before check the message of update, so:
1 => Wipe and install MaximuS V2.5 ROM
2 => flash with fastboot boot.img of MaximuS V2.5 ROM
3 => flash stock HTC Recovery via fastboot ( fastboot flash recovery ville_recovery_signed.img , then fastboot erase cache ) or get it from One_S_All-In-One_Kit_v1.0
4 => start the phone and check for the JB update
5 => after JB installation do a factory reset to clean up the ROM from the extra application that MaximuS ROM have.
You don't need to relock your bootloader, you just need to install the stock recovery, that's enough.
Hmm, wait, why need install stock recovery?
This JB will be working with custom twrp?
EDIT: I got it
I did it! I unmounted first 3 partitions in TWRP and installation successful.
I am on stock Rom now and used HTC offical update to get to jb...do u think I will have trouble rooting again?
Sent from my HTC One S using xda premium
k1llacanon said:
I am on stock Rom now and used HTC offical update to get to jb...do u think I will have trouble rooting again?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I will let you know if I can get it working and flashed it will be rooted in seconds just need stock recovery.
Rooted without a problem, recommend the attached superuser app.
Maverick87Shaka said:
You just forgot in the list to install the HTC Stock recovery before check the message of update, so:
1 => Wipe and install MaximuS V2.5 ROM
2 => flash with fastboot boot.img of MaximuS V2.5 ROM
3 => flash stock HTC Recovery via fastboot ( fastboot flash recovery ville_recovery_signed.img , then fastboot erase cache ) or get it from One_S_All-In-One_Kit_v1.0
4 => start the phone and check for the JB update
5 => after JB installation do a factory reset to clean up the ROM from the extra application that MaximuS ROM have.
You don't need to relock your bootloader, you just need to install the stock recovery, that's enough.
Click to expand...
Click to collapse
Will this work on a T-Mobile HOS with CID HTC__001?
I have followed all the steps from above
- installed the rom
- installed the stock recovery
- then I was able to start the update but when it finished downloading .. I was told that the HTC software on my device has been modified and please revert back and try the update again and it would not preform the update.
What am I doing wrong?
Thanks in Advance
Hi once more,
after going back to pure stock JB this way, can I relock the bootloader to get "RELOCKED" instead of "UNLOCKED/TAMPERED"? (That would be good for sending in my phone under warranty.) Or will the phone stop booting if I relock the bootloader?
As far as I understood, the "canonical" way to get "RELOCKED" would be to lock the bootloader and install the RUU, but since there is no RUU for the unbranded JB yet and downgrading with an older RUU is not possible, I cannot do this.
Cheers,
Tim
tim_h said:
Hi once more,
after going back to pure stock JB this way, can I relock the bootloader to get "RELOCKED" instead of "UNLOCKED/TAMPERED"? (That would be good for sending in my phone under warranty.) Or will the phone stop booting if I relock the bootloader?
Cheers,
Tim
Click to expand...
Click to collapse
You can do Relock bootloader, i think it will boot to system without problem(?)
blah blah blah said:
Will this work on a T-Mobile HOS with CID HTC__001?
I have followed all the steps from above
- installed the rom
- installed the stock recovery
- then I was able to start the update but when it finished downloading .. I was told that the HTC software on my device has been modified and please revert back and try the update again and it would not preform the update.
What am I doing wrong?
Thanks in Advance
Click to expand...
Click to collapse
+ 1
Sent from my HTC One S using xda app-developers app
The only word of caution that I think needs to be shared on almost all threads related to JB updates is to make sure you DO NOT have SuperCID... There have been numerous reports of phones bricking with the OTA JB update with a SuperCID... So if you had previously SuperCID your phone with 11111111, definately change it to something else.
AKToronto said:
The only word of caution that I think needs to be shared on almost all threads related to JB updates is to make sure you DO NOT have SuperCID... There have been numerous reports of phones bricking with the OTA JB update with a SuperCID... So if you had previously SuperCID your phone with 11111111, definately change it to something else.
Click to expand...
Click to collapse
I had to go supercid to run the euro ruu and changed it to HTC__001. Ota still didn't work
Sent from my HTC One S using xda app-developers app
Hi all,
a friend of mine has bought his HTC One S 3 days ago, but after using the all in one toolkit we aren't able to flash anything....Let me explain better:
1) we follwed everything step by step (unloocking and rooting) with success
2) we can mount the sd card from the recovery and copy any ROM
3) when flashing nothing happens, just errors messages (we tried with Viper and TrickDroid)
4) As far as I understood, the boot.img must be flashed AFTER flashing the ROM, not before, right?
The CID phone is vodap102. It was updated to the latest JB before messin'it up....so it has Hboot 2.15. The latest RUU for this Cid is unavailable so we can't back to stock...how can we solve this?? any idea???
Please help us, we're quite desperate :crying:
Thanks a million guys!
P.S. Just noticed that when rebooting from the recovery it say that SuperSU is not installed and can't be pushed to the sd .....if I install it manually says "successful", but that message, when rebooting, appears again...
Try with older version of twrp
Verstuurd van mijn One S met Tapatalk
Solved!
real187 said:
Try with older version of twrp
Verstuurd van mijn One S met Tapatalk
Click to expand...
Click to collapse
Great, after thousand of various recoveries we found the right one (TWRP 2.2.2.0) and we flashed Viper's ROM!
Thank you man!:good:
Where did you get that you have to flash the boot.img after the whole ROM?
Sent from my HTC One S using xda app-developers app
Before or after..doesn't matter
HTC_One_S | S-OFF | DeviantXone | Bubba_3.7b_SoftOV
TWRP v 2.2.2.1 I can't flash Jelly Bean 4.2.2 .zip on HTC one s (s3)
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
Hi, One HTC S (S3) there is no ROM 4.2.2. Did you use the wrong ROM (S4)
mikebryant2807 said:
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
Click to expand...
Click to collapse
As the poster above said, it's good that the 4.2.2 ROM wouldn't flash, or your device would have bricked by now with possibly no means to recover it. Flash a ROM from the S3 Development section.
Can’t Flash Anything on TWRP
Hello,
I’m using a Kindle Fire HD ( 1st Gen ). I rooted it and I’m running on CyanogenMod 9 ,Android version 4.0.4 . I also have TWRP installed,version 2.2.2.1 .I have decided to sell my Kindle Fire but I have to unroot it first. So I booted into TWRP 2.2.2.1 and tried to flash the Kindle Fire update bin file which is zipped. After flashing it, it says “ Error flashing zip ‘/sdcard/update-kindle-6.3.2_DO1E_4110520.BIN.ZIP’”.What should I do to unroot my kindle now? Please Help !!! :crying:
I have my TF300T with official rom, but unlocked and installed TWRP 2.3.3 about 1 years ago,
after that I didnt do anything special liking flashing rom except regular use
Yesterday, my wife complained the tablet is too slow, so i tried to flash the customized rom PAC-ROM 4.3, then my device enters reboot loop.... and it hangs at the ASUS logo for about 30 second for every reboot.
since I still can enter recovery and run TWRP, so i searched around and followed some posts by doing wipe system, factory reset, reflashing multiple times....but nothing helped. I also did the wipe data button on the recovery menu besides the RCK, but after reading some posts, i am afraid that i softbricked my device by doing that.
however, now i still can enter TWRP, but dont know what to do to restore my device, I wish some one can help me here by giving some suggestions
I would also to know the cause of the failure, my device is running the offical 4.1 ROM, and i followed exactly the steps mentioned by the post on PAC_MAN, Is that because my TWRP is too old?
shelper said:
...i tried to flash the customized rom PAC-ROM 4.3, then my device enters reboot loop....
...my device is running the offical 4.1 ROM...
Click to expand...
Click to collapse
There is two version of JB bootloaders. It looks like You have an older one and all current custom roms require new one. So here is Your mistake. To unbrick Your device it need to be reflashed to 4.1 stock rom. Then, if You still need to flash pac-rom, upgrade to 4.2 stock rom first.
Thanks so much!
i just want to confirm, since i already did wipe data button, do i need to goto fastboot to push the stock rom?
or i can just flash the 4.1 stock (or customized rom) using twrp?
in addition,how should i upgrade to 4.2 stock rom? can you refer me a thread?
thanks again!:good:
Graiden05 said:
There is two version of JB bootloaders. It looks like You have an older one and all current custom roms require new one. So here is Your mistake. To unbrick Your device it need to be reflashed to 4.1 stock rom. Then, if You still need to flash pac-rom, upgrade to 4.2 stock rom first.
Click to expand...
Click to collapse
I think fastboot is prefered to restore 4.1 stock. And IMHO best way to upgrade to 4.2 is stock recovery.
sorry that i am a newbie without much experience.
i am not very clear about the steps.but if i understand correctly, i need to
1. goto fastboot to restore stock 4.1, which will automatically remove TWRP and replace it with stock recovery
2. copy stock 4.2 rom to the root of a sdcard and run stock recovery for udpate
3. root the device again? and install TWRP
4. use TWRP to install the PC-man 4.3
am i miss anything?
thanks alot!
Graiden05 said:
I think fastboot is prefered to restore 4.1 stock. And IMHO best way to upgrade to 4.2 is stock recovery.
Click to expand...
Click to collapse
All right. Little hint: twrp for new bootloader have 4.2 in the end of file name and version 2.5.0.0 is most stable.
Hope this Helps
Try here. http://forum.xda-developers.com/showthread.php?t=2187982
Basically, you have 2 options. If you want to stay on 4.1 bootloader, download the older 4.1 Asus factory image zip (v10.4.x.x) from this thread, http://forum.xda-developers.com/showthread.php?t=1949758, and install it using one of the three options mentioned in the first thread.
Option #2 is to update to the newest 4.2 bootloader, download the newest 4.2 Asus factory image zip from the same thread (v10.6.x.x), and install it
I would go with #2 because most of the newer custom ROM are made for 4.2 bootloader, plus it's the offical newest Asus bootloader. The only reason I can think of to use option #1 is for some of the older custom ROM that still uses 4.1 bootloader.
Hope this helps.
---------- Post added at 12:32 AM ---------- Previous post was at 12:27 AM ----------
mlee18 said:
Try here. http://forum.xda-developers.com/showthread.php?t=2187982
Basically, you have 2 options. If you want to stay on 4.1 bootloader, download the older 4.1 Asus factory image zip (v10.4.x.x) from this thread, http://forum.xda-developers.com/showthread.php?t=1949758, and install it using one of the three options mentioned in the first thread.
Option #2 is to update to the newest 4.2 bootloader, download the newest 4.2 Asus factory image zip from the same thread (v10.6.x.x), and install it
I would go with #2 because most of the newer custom ROM are made for 4.2 bootloader, plus it's the offical newest Asus bootloader. The only reason I can think of to use option #1 is for some of the older custom ROM that still uses 4.1 bootloader.
Hope this helps.
Click to expand...
Click to collapse
Make sure to follow the instructions in RED exactly, there's a reason they are in red.
Hi
I installed CyanogenMod M10 as an update to my Nightlies Built-...0910
The Booting process can complete But Keep Rebooting as soon as Lock-Screen appears!
I m Multi-ROM user
Internal ROM: Rooted Stock Android
Kernel: Kexek 4.4.4
(I can boot to another ROM)
Click to expand...
Click to collapse
I tried reflash CM-M10 but problem still here...
I m looking for a Solution (instead of Wiping anything, if possible!)
& I searched for get back to previous version and lots of member not recommend it, what about you?
---
>> Solution was Flashing a Previous version of CM (at this moment last version is CM...Nightlies...0915)
as the other say Dirty Flash or something like this
:good: