Hello all
New posting, but long time lingering in the forums.
Just picked up an htc one, got it rooted and started to flash roms.
First one I tried, Android revolution (newest one) to find out that it wasn't compatible with my SPRINT phone. It had me stuck on the bootloader screen so my only option was to ADB sideload another rom,
so I tried the newest VIPER rom version 1.1.0
Everything went great and i was excited, it even updated my apps.
Now, When i get to the home screen it just BLACK unresponsive and after a min or so, it reboots. It keeps doing this unless i hold down the volume key to get it into bootloader.
I have access to recovery (twrp 2.5.0.0) and bootloader.
Please help, been at this for two days now and I need my phone to work..
where do I begin? how do i fix this?
thanks
Did you try wiping then reflashing?
sauprankul said:
Did you try wiping then reflashing?
Click to expand...
Click to collapse
yes.
ive even tried restoring the nandroid when it was rooted stock.
no luck.
i tried flashing a stock rooted rom aswell
It booted, got me to the set up screens and a few seconds in as i was relived, it crashed and sent me to bootloader.
before I RUU, i just want to make sure i tried all options.
Really, if you can, then RUU. You don't want to risk REALLY messing something up.
I say RUU while you can.
Matteeeus said:
yes.
ive even tried restoring the nandroid when it was rooted stock.
no luck.
i tried flashing a stock rooted rom aswell
It booted, got me to the set up screens and a few seconds in as i was relived, it crashed and sent me to bootloader.
before I RUU, i just want to make sure i tried all options.
Click to expand...
Click to collapse
I am quite sure doing the following with fix it, but I am not positive (This will completely wipe your sdcard). From recovery click advanced / partition external sdcard then sideload and flash ViperRom again.
---------- Post added 12th August 2013 at 12:27 AM ---------- Previous post was 11th August 2013 at 11:40 PM ----------
This might work too, I think your partitions are messed up. http://forum.xda-developers.com/showthread.php?t=2321685
Thanks for the help,
I RUU' d the phone and got back to stock. everythings good to go :laugh:
Now im back at square one, ill have to re root and flash another rom.
I guess flashing that android HD rom in the first place really messed things up.
Related
This is an update on a previous post, this time however you don't have to sieve through Chinese websites to get them....i have spent time to get them for you!
This Will revert your HTC Salsa to Stock
By using these you will wipe everything you have done. Recovery will be wiped, unknown about lock/unlocked boot-loader as i haven't attempted this with unlocked boot-loader before as.i had s-off at the time.
You do this at your own risk, i take no responsibility at all for anything that may or may not happen lol
Instructions for use.
HTC SYNC installed but not running, you want the cable driver mainly.
Instead of following on screen instruction via the RUU, set your phone into fastboot mode yourself then activate/run the RUU.exe you require, i would suggest run as administrator (right click on application)
This will take some time to install, i did it on 3rd attempt, first 2 were relying on the RUU to boot the phone for me...3rd i booted into fastboot/bootloader myself and away it went.
if for any reason it doesn't respond to you or it doesn't install stock or freezes, whip out the battery and do it all again!
Below are the RUU's please find the correct region your in and download accordingly. EU RUU is a common one if the others don't work. all roms are based of this version.
RUU_Icon_G_HTCCN_CHS_1.24.1400.4_Radio_47.14.35.3030H_7.47.35.17_release_204455_signed.exe
RUU_Icon_G_HTC_Europe_1.12.401.1_R_Radio_47.14.35.3030H_7.47.35.17_release_193257_signed.exe
RUU_Icon_G_O2_UK_1.18.206.2_Radio_47.14.35.3030H_7.47.35.17_release_198160_signed.exe
RUU_Icon_G_hTC_Asia_HK_1.16.708.3_Radio_47.14.35.3030H_7.47.35.17_release_197702_signed.exe
RUU_Icon_G_hTC_Asia_India_1.12.720.2_Radio_47.14.35.3030H_7.47.35.17_release_193467_signed.exe
RUU_Icon_G_HTC_TUR_1.18.468.2_Radio_47.14.35.3030H_7.47.35.17_release_199341_signed.exe
RUU_Icon_G_Hutch_AUS_1.18.861.1_Radio_47.14.35.3030H_7.47.35.17_release_197619_signed.exe
RUU_Icon_G_Voda-Hutch_AU_1.17.862.2_Radio_47.14.35.3030H_7.47.35.17_release_198433_signed.exe
RUU_Icon_G_Chunghwa_1.13.751.1_Radio_47.14.35.3030H_7.47.35.17_release_193940_signed.exe
RUU_Icon_G_hTC_Asia_WWE_1.12.707.2_Radio_47.14.35.3030H_7.47.35.17_release_193464_signed.exe
as the link in the lower post suggested you can also try this
*this wasn't provided by me please don't blame me if anything goes wrong*
1. Download your RUU
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
3. Enter the fastboot mode on your phone by pressing volume down + power button after the device has been turned off.
4. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
5. Using fastboot tools, open the Command prompt and navigate to "C:\fastboottools" then run this command on cmd: "fastboot flash system system.img"
6. Dont reboot, Using fastboot tools, run this command on cmd: "fastboot flash boot boot.img"
( The two commands in step 5 and 6 are different, make sure to type each one correctly and to do them straight after each other )
7. Reboot phone. let it boot up, you will still get bootloop or error message.
8. Take out the battery.
9. Boot back into bootloader ( Volume down + power ).
10. Now choose recovery.
11. Phone should now reboot itself and bam, all should now work fine.
Well it seems a lot of you shadows hiding away wanted these lol, as the downloads in 1 day surprised me lol.
BigBear is using Xparent Tapatalk Purple
I managed to revert back to stock using this method http://forum.xda-developers.com/showthread.php?t=1631121
Now I am running 2.3.3
Now i just want to update to 2.3.5 if possible, haven't been able to get OTA updates. Do you know how i can go about it?
CWM recovery is still intact.
Thanks
The salsa will never have 2.3.5 ota. HTC stopped at 2.3.3 and discontinued updates for us. well the stopped producing the salsa and totally dropped it.
that's why we have 2.3.5 roms that are not meant for us...ie no FB button that works correctly, no mirror or front facing camera.
and this is probably why noone is still running stock roms anymore
BigBear is using Xparent Tapatalk Purple
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Now I have relocked the bootloader and tried the Europe Salsa RUU.... It is giving me Error 140 now claiming the bootloader version is invalid.
HBOOT is updated and I notice that the Radio version mentioned on Fastboot Bootloader screen is different than mentioned in the RUU.
Mine says:
*** Relocked ***
ICON_G PVT SHIP S-ON RL
HBOOT-1.08.0000
MICROP-0558
RADIO-7.51.35.19
Dec 16 2011,16:12:07
razasohail said:
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Click to expand...
Click to collapse
Did you take a nandroid backup in recovery at all?, if so restore it.if recovery isn't there reinstall recovery and restore your backup.
BigBear is using Xparent Tapatalk Purple
Get the phone to Stock
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
arekapudi said:
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
Click to expand...
Click to collapse
this guide wasn't provided by me, i do know what this means but its hard to explain to a newbie...
for the more technical side of go here >http://forum.xda-developers.com/showthread.php?t=1631121, it may help you...
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Saturn007 said:
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Click to expand...
Click to collapse
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
BigBearEvo said:
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
Click to expand...
Click to collapse
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Saturn007 said:
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Click to expand...
Click to collapse
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
BigBearEvo said:
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
Click to expand...
Click to collapse
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
gagan313 said:
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
Click to expand...
Click to collapse
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
BigBearEvo said:
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
Click to expand...
Click to collapse
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
gagan313 said:
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
Click to expand...
Click to collapse
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
BigBearEvo said:
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
Click to expand...
Click to collapse
thats just the thing you see....
for some reason, if i try the stock.zip i always have wifi issues as well as facebook issues and well... i have tried all the facebooks from 1.9.9 to the black one and it dosnt seem to sign in... evern after i have unin installed and moved to sd card using links2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
gagan313 said:
that's just the thing you see....
for some reason, if i try the stock.zip i always have WiFi issues as well as Facebook issues and well... i have tried all the Facebook from 1.9.9 to the black one and it doesn't seem to sign in... even after i have uninstalled and moved to sdcard using link2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
Click to expand...
Click to collapse
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
BigBearEvo said:
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
Click to expand...
Click to collapse
ok ill give it a shot
Hello guys,
I'm in a bit of a pickle here....
I've got a HTC One which I've rooted and unlocked though not S-Off by the looks of things and I had SinLess rom installed fine, it started playing up so I though I'd update it. Bung the new one version on there via sideload and install... Marvelous.
Only now, it gets to the welcome screen as silly ol' me did a factory wipe as well as all cache and after about 5 seconds of Welcome - Choose language. It restarts.
I then decided to try a new rom, so grabbed Android Revolution. To no avail either....
On bootloader it shows as HBOOT - 1.54
S-On
**TAMPERED**
**UNLOCKED**
What can I do to actually get a working rom on this thing?
If there is any more details I need to give please say so as this is my first time flashing something as complicated as this. All my old android devices were far far simplar :crying:
- Here's the facepalm moment - I didn't do an nandroid backup due to it not working and I wanted to put a new ROM on there so I didn't look into getting it working. If I could injure myself I would.
Any help will be greatly appreciated. :good:
Kind regards, Ian.
Jeffaruni said:
Hello guys,
I'm in a bit of a pickle here....
I've got a HTC One which I've rooted and unlocked though not S-Off by the looks of things and I had SinLess rom installed fine, it started playing up so I though I'd update it. Bung the new one version on there via sideload and install... Marvelous.
Only now, it gets to the welcome screen as silly ol' me did a factory wipe as well as all cache and after about 5 seconds of Welcome - Choose language. It restarts.
I then decided to try a new rom, so grabbed Android Revolution. To no avail either....
On bootloader it shows as HBOOT - 1.54
S-On
**TAMPERED**
**UNLOCKED**
What can I do to actually get a working rom on this thing?
If there is any more details I need to give please say so as this is my first time flashing something as complicated as this. All my old android devices were far far simplar :crying:
- Here's the facepalm moment - I didn't do an nandroid backup due to it not working and I wanted to put a new ROM on there so I didn't look into getting it working. If I could injure myself I would.
Any help will be greatly appreciated. :good:
Kind regards, Ian.
Click to expand...
Click to collapse
Hey your'e stuck in a boot loop, its usual
just download a good stable rom
clear data/ cache
flash the rom and you'll be out of it,
If this thing doesnt work out download the orignal RUU and get back to stock
Tech.Nik said:
Hey your'e stuck in a boot loop, its usual
just download a good stable rom
clear data/ cache
flash the rom and you'll be out of it,
If this thing doesnt work out download the orignal RUU and get back to stock
Click to expand...
Click to collapse
Yeah, after attempting to install 3 different roms.
Sinless, ARHD and SkyDragon, I'm going to try a different recovery as I'm currently using TWRP 2.6.3.3 and I know there is an update but also I want to see if CWM can do anything with the 6.0.4.3 version....
Jeffaruni said:
Yeah, after attempting to install 3 different roms.
Sinless, ARHD and SkyDragon, I'm going to try a different recovery as I'm currently using TWRP 2.6.3.3 and I know there is an update but also I want to see if CWM can do anything with the 6.0.4.3 version....
Click to expand...
Click to collapse
Hello,
To no avail, after trying different recoveries, nothing.
Looks like I've got a metal slab...
It just keeps restarting itself at the welcome screen, the only other thing I can think of would be to fully wipe EVERYTHING on the phone but I'm not sure that's too good of a move either...
Argh.
You have to be s-off to run these Roms
Hi guys so this is a little embarrassing but I'm fairly certain sprint update has bricked my phone. Sprint pushed the update to 4.4 2 nights ago for me and everything was going fine. My phone is rooted and custom recovery so I slapped on the stock recovery to process the update. The update starts off fine and dandy until about halfway through the dreaded red triangle/exclamation mark popped up. I instantly cursed and watched as my phone entered into an infinite boot loop. I thought it might have worked at first because the lock screen popped up, but when you unlock the phone the white htc logo is still there and the phone reboots after 10 seconds. So after making sure something went astronomically wrong with the update, I went into the boot loader and adb pushed twrp back onto the phone. the update somehow updated my hboot to 1.55 so my s-off is now s-on and I have no wawy to tell if the kernal for the phone is functioning. My only guess to this matter is that the boot sector for the phone is corrupt, but I tried to restore the stock twrp backup i have, and nothing. It boots, the lockscreen unlocks, but it still reboots. Now it was unlocked long enough for me to get into settings and see that it wiped ALL of my phones id info. All the meid, meie, carrier, everything is blank. So it seems that the phone crashed somewhere in the update where it was in the process of wiping things? I then tried to flash a completely different rom on there to see how that went. I first tried viperone 5.0.0 then the newer 5.8.0 and neither would boot (waited 1 hour each to make sure). Then I tried arhd 61 and again, no boot. So I'm not quite sure where to go from here. My stock backups aren't working at restoring, new rom flash isnt working, I can't take it into sprint to check on it since its rooted, I can't update the kernel due to s-on (correct me if im wrong). I'm smart enough to know when I'm out of my depth and I'm clearly trying to tread water in the middle of the ocean in this instance. So please if someone could give me a hand I would appreciate it so much.
xanex18 said:
Hi guys so this is a little embarrassing but I'm fairly certain sprint update has bricked my phone. Sprint pushed the update to 4.4 2 nights ago for me and everything was going fine. My phone is rooted and custom recovery so I slapped on the stock recovery to process the update. The update starts off fine and dandy until about halfway through the dreaded red triangle/exclamation mark popped up. I instantly cursed and watched as my phone entered into an infinite boot loop. I thought it might have worked at first because the lock screen popped up, but when you unlock the phone the white htc logo is still there and the phone reboots after 10 seconds. So after making sure something went astronomically wrong with the update, I went into the boot loader and adb pushed twrp back onto the phone. the update somehow updated my hboot to 1.55 so my s-off is now s-on and I have no wawy to tell if the kernal for the phone is functioning. My only guess to this matter is that the boot sector for the phone is corrupt, but I tried to restore the stock twrp backup i have, and nothing. It boots, the lockscreen unlocks, but it still reboots. Now it was unlocked long enough for me to get into settings and see that it wiped ALL of my phones id info. All the meid, meie, carrier, everything is blank. So it seems that the phone crashed somewhere in the update where it was in the process of wiping things? I then tried to flash a completely different rom on there to see how that went. I first tried viperone 5.0.0 then the newer 5.8.0 and neither would boot (waited 1 hour each to make sure). Then I tried arhd 61 and again, no boot. So I'm not quite sure where to go from here. My stock backups aren't working at restoring, new rom flash isnt working, I can't take it into sprint to check on it since its rooted, I can't update the kernel due to s-on (correct me if im wrong). I'm smart enough to know when I'm out of my depth and I'm clearly trying to tread water in the middle of the ocean in this instance. So please if someone could give me a hand I would appreciate it so much.
Click to expand...
Click to collapse
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Bairdog35 said:
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I will Definitely check it out. I was hesitant to try an RUU because all the ones I was looking at were talking about flashing modded kernels and needing s-off and such. But I will definitly try it and update if it works.
Bairdog35 said:
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Alright mate, I'm gunna need a mailing address to send my first born son to. You are a god send with that link. It worked perfectly
xanex18 said:
Alright mate, I'm gunna need a mailing address to send my first born son to. You are a god send with that link. It worked perfectly
Click to expand...
Click to collapse
I'm glad it worked ?
Sent from my HTCONE using Tapatalk
A friend has asked me to try and fix there M7 ul. It was. Completely stock on O2 UK. They got a notification for system update (4.4.2 Sense6.0). While installing they left the phone and when they came back it was off. After some fiddling they managed to get it to come on but it would only boot to the bootloader which had Tampered and Locked flags.
This is where I came in so I tried booting to stock recovery to see if the OTA would complete but it was a no go. The screen just stayed black for ages then eventually would show the phone picture with red exclamation. Using volume up+power to get the recovery menu to reset cache returned it to the normal picture with green arrows. But reboot and repeat So I tried fastboot erase cache and attempted ota again with same results.
At this point I told them that anything more I tried may void the warranty so better to send it in but there is no warranty so asked me to do whatever I can. Naturally for me the next step was to unlock the bootloader to regain some control. First I just let the phone boot this time no bootloader screen but it just looped on the HTC splash screen.(i kind of expected that). So next I reboot bootloader and flash twrp2.6.3.3 erase cache and boot recovery. ARHD rom was already in my android folder so pushed it strait over. Ran into some pitfalls trying to flash the rom like instant reboots when flashing started and disappearing zip files fixed with e2fsck, zip failed message fixed with Format data and eventually got the rom installed. I know first boot normally takes a while but this seemed longer than expected but eventually booted the rom and everything seemed to be working fine.
After setting up the basics and testing a few things (installing and running apps. Playing music and so on) I rebooted the phone but again it bootloops on HTC splash screen. Tried everything to get it to boot like wipeing cache/dalvik, dirty flash, clean install even fix permissions nothing worked except Format Data in Twrp Full wipe, re-push rom re-flash rom. Phone took a while but booted and again worked perfectly while setting up and using the phone. So tried restart and again bootloop on HTC splash
So I'm now at a point where I think I've narrowed it down to the Kernel or Ramdisk or atleast the partition there installed on. Since if I use the Superwipe script to wipe only the boot partition cache/dalvik then refresh the boot.img or flash a kernel from recovery (i've been using bulletproof kernel) the phone will boot with the rom and settings intact.
If there is a problem with this partition I do not know how to fix it. I know mmcblk0p33 is the boot partition but is it where the boot.img actually lives or is that the bootloader partition?
If it is the boot.img partition can I repair it with mke2fs or e2fsck or some other tool?
There is an ruu available for the device so if I can just stop the bootloop I could s-off and then ruu and return it to stock. But firewater won't work and I think it's because of the procedure involved in getting the phone to boot is interfering with the push somehow. Firewater will push ok and chmod works but when I try to run firewater nothing happens and then the firewater file disappears and I have to push it again which means re-wipeing and flashing the kernel. I'm really not sure where to go from here any help or suggestions would be most appreciated thanks in advance :fingers-crossed:
Ok so s-off is out of the question since this phone has emmc cid 9001 best I can hope for now is a firmware.zip. I did keep trying firewater and eventually got it to run but sure enough I got Whelp this sucks!!
Would using cwm to format boot be any different to what superwipe dose? It says Format Boot but dose it actually format it or just wipe the data from it? I haven't used cwm since my galaxy ace days.
Danny201281 said:
Ok so s-off is out of the question since this phone has emmc cid 9001 best I can hope for now is a firmware.zip. I did keep trying firewater and eventually got it to run but sure enough I got Whelp this sucks!!
Would using cwm to format boot be any different to what superwipe dose? It says Format Boot but dose it actually format it or just wipe the data from it? I haven't used cwm since my galaxy ace days.
Click to expand...
Click to collapse
you could try a full wipe firmware.zip and HBOOT, you will have to use the one you currently have on the device or the next newer one due to s-on, it will / should re-write your partitions, try looking here:
(searching for link)
Seanie280672 said:
you could try a full wipe firmware.zip and HBOOT, you will have to use the one you currently have on the device or the next newer one due to s-on, it will / should re-write your partitions, try looking here:
(searching for link)
Click to expand...
Click to collapse
Thanks for reply.
Yep I've been looking for a firmware.zip it on 5.12.206.3 all I can find is an ruu.exe but it's the version before. I searched the updates thread and no one seems to have captured the OTA file so can't even extract from there.
Danny201281 said:
Thanks for reply.
Yep I've been looking for a firmware.zip it on 5.12.206.3 all I can find is an ruu.exe but it's the version before. I searched the updates thread and no one seems to have captured the OTA file so can't even extract from there.
Click to expand...
Click to collapse
trouble is, you will need the full firmware, not just an OTA, and the wipe version, usually I see the page with the HBOOTs and firmwares everywhere, do you think I can find it now I need it...........
found it finally, check see if yours is in there, full wipe section: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
---------- Post added at 01:50 PM ---------- Previous post was at 01:40 PM ----------
trouble is too, you cant s-off without a working rom on it, unless you can find someone who can do it by java card for you which is all done from the bootloader.
Seanie280672 said:
trouble is, you will need the full firmware, not just an OTA, and the wipe version, usually I see the page with the HBOOTs and firmwares everywhere, do you think I can find it now I need it...........
found it finally, check see if yours is in there, full wipe section: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
Click to expand...
Click to collapse
Thanks for looking I'll start searching for it now. I hope there's something out there. :fingers-crossed:
Danny201281 said:
Thanks for looking I'll start searching for it now. I hope there's something out there. :fingers-crossed:
Click to expand...
Click to collapse
is it the HTC one ? or the HTC one Mini ?
Danny201281 said:
Thanks for looking I'll start searching for it now. I hope there's something out there. :fingers-crossed:
Click to expand...
Click to collapse
I can get a working rom no problem but it will only boot if I superwipe the boot partition and reflash kernel. Other wise it just bootloops.
But I've already had the whelp this sucks message so no s-off that's why's I need a matching firmware.
Seanie280672 said:
is it the HTC one ? or the HTC one Mini ?
Click to expand...
Click to collapse
HTC one M7_UL
Danny201281 said:
HTC one M7_UL
Click to expand...
Click to collapse
The only RUU I could find is 4.xx.206.xx, you really need s-off to sort it, as you cant use that RUU, there is no RUU for your current version as its all ota's to get to that point, you may have some luck if you can find the next one up which will be 6.06.206.xx.
however, if you are in the UK and can live without your phone for a few days, then give these guys a call, book your phone in with them, and send it to them, they will s-off it by java card and send it back the same day, overall it takes about 3 or 4 days, its who I used, they were very helpful and friendly bunch of guys, best £15 quid ive ever spent.
http://www.fonefunshop.co.uk/Unlocking/htc_s-off_service.htm
---------- Post added at 02:09 PM ---------- Previous post was at 02:01 PM ----------
actually, im over thinking things, have you tried this, it should also re-write your partitions: http://forum.xda-developers.com/showthread.php?t=2770684
Seanie280672 said:
actually, im over thinking things, have you tried this, it should also re-write your partitions: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Yes I remember this thread starting up I had considered this but not sure it would work as phone isn't in qhusb dload plus no evidence so far (i've still got some posts to read) it works with s-on. But I'll definitely give it a try if all else fails. Thanks again
Well I don't know if it's from the repeated wiping and flashing of the kernel or what but the phone seems to boot every time without the need to reflash the kernel now. Only it takes about 20mins looping once or twice on the splash screen. Once it gets past that from the boot animation onwards it works flawlessly. I can't get my head around it.
Just to put some closure to this. It's determined to be a hardware problem. Possibly a damaged memory chip. I did manage to return it to stock before handing it back to the owner with the bad news. But it will not boot the stock Rom at all just loops endlessly on the HTC LOGO splash screen.
Case closed
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
I have a note 3 that I'm trying to get Cyanogenmod 11 on to. I should note that I got this working with my Droid Razr earlier today using the exact same process. I get to the point where I flash the rom and it only takes like 5 seconds then says "successful". When I boot the rom I just get a black screen that I have to hold the power button down to get out of. My note 3 is running 4.4.2 I have root and busybox is installed. I've tried safestrap 3.72 and 3.75. I've even tried the stock slot (and then reverted back when it didn't work). I'm out of things to try and I can't find anyone else who has had a similar issue. Anyone got any ideas?
If its an N900A or N900V, you can only run TW based roms because the bootloader is locked.
andygev35 said:
If its an N900A or N900V, you can only run TW based roms because the bootloader is locked.
Click to expand...
Click to collapse
How are people getting cyanogenmod 11 on their att note 3s if not through safestrap?
I don't know of anyone with an at&t note 3 running CM. It's possible they're using an N900T, or an N9005 Note 3 on at&t.
andygev35 said:
I don't know of anyone with an at&t note 3 running CM. It's possible they're using an international note 3 on at&t.
Click to expand...
Click to collapse
Well that's sad. I'm assuming any of these will work in the meantime? http://forum.xda-developers.com/note-3-att/#romList
They should, just make sure if you're on KK to choose a KK rom.
noob over here needing help
i have the ATT Note 3 with the locked bootloader. i cant rememeber the model name but i think its like I900A. anyway i have had it rooted for about 5 months or so and i have had safestrap and busybox and use Xposed wanam. also using twrp and titanium backup. well i have never flashed anything on it cuz ive always been sketched out with the locked bootloader and not being able to flash kernals and all that. so yesterday i figured i would try one out and see if i could get it. i used the "S5 Experience" rom and i downloaded it from MEGA onto my ext. SD under a new folder i made called "s5 experience". i then went into recovery mode through safestrap and went to "backup" and then made a backup of data, cache, and system. after that i went to "wipe" and did a factory reset/wipe. when that was done i went to "install" and found my "s5 experience" on my ext. SD and installed it. when that was done i rebooted my device and it popped up with the samsung note 3 emblem and under it the little lock underneath it in the unlocked position just like it always has. then went to safestrap with the little red robot and "safestrap: disabled" like always. so i hit continue and from there is when my problem started. the blue LED light on the top left turned on and stayed on but the screen stayed black. this is the problem i am still having right now. if i press the power button it will vibrate or double vibrate and eventualy if i hold it down i can get it to restart. after that i went into recovery again and tried to restore from my backup i had made just earlier. when i try that it goes for a while and then will eventually say that restore has failed. ive mesed with some of the settings and stuff in the twrp recovery interface but not much because im new and not sure what i should and should not be doing. so i started looking here. i didnt find any help on the S5 Experience forum and i havent found and other forums that have this problem except maybe this one. so i am asking for help, if someone would be so kind as to walk me through how to fix my phone and what i did wrong it would be greatly greatly appreciated. if at all possible i would love to keep all of my pics and apps and stuff but if that is not possible then i wont complain if i have to lose it all. i would be happy just to have a working phone again. thanks in advance and sorry if i have posted this in the wrong place.
sethers said:
i have the ATT Note 3 with the locked bootloader. i cant rememeber the model name but i think its like I900A. anyway i have had it rooted for about 5 months or so and i have had safestrap and busybox and use Xposed wanam. also using twrp and titanium backup. well i have never flashed anything on it cuz ive always been sketched out with the locked bootloader and not being able to flash kernals and all that. so yesterday i figured i would try one out and see if i could get it. i used the "S5 Experience" rom and i downloaded it from MEGA onto my ext. SD under a new folder i made called "s5 experience". i then went into recovery mode through safestrap and went to "backup" and then made a backup of data, cache, and system. after that i went to "wipe" and did a factory reset/wipe. when that was done i went to "install" and found my "s5 experience" on my ext. SD and installed it. when that was done i rebooted my device and it popped up with the samsung note 3 emblem and under it the little lock underneath it in the unlocked position just like it always has. then went to safestrap with the little red robot and "safestrap: disabled" like always. so i hit continue and from there is when my problem started. the blue LED light on the top left turned on and stayed on but the screen stayed black. this is the problem i am still having right now. if i press the power button it will vibrate or double vibrate and eventualy if i hold it down i can get it to restart. after that i went into recovery again and tried to restore from my backup i had made just earlier. when i try that it goes for a while and then will eventually say that restore has failed. ive mesed with some of the settings and stuff in the twrp recovery interface but not much because im new and not sure what i should and should not be doing. so i started looking here. i didnt find any help on the S5 Experience forum and i havent found and other forums that have this problem except maybe this one. so i am asking for help, if someone would be so kind as to walk me through how to fix my phone and what i did wrong it would be greatly greatly appreciated. if at all possible i would love to keep all of my pics and apps and stuff but if that is not possible then i wont complain if i have to lose it all. i would be happy just to have a working phone again. thanks in advance and sorry if i have posted this in the wrong place.
Click to expand...
Click to collapse
If you can boot to stock recovery (power+home+volume up) NOT safestrap recovery do a factory reset from there. That'll reflash stock rom and you can reroot + busybox + SS. Make sure to check what build you are on as well - if you are on NC2 kitkat you can only flash kitkat-based roms.
Sethers, please do not hijack and do not double post your questions in multiple threads.
graydiggy said:
Sethers, please do not hijack and do not double post your questions in multiple threads.
Click to expand...
Click to collapse
sorry graydiggy. this seemed like a thread that had something to do with the same black screen i was getting. besides this one i only posted it on the stupid questions thread.
---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------
brisinger08 said:
If you can boot to stock recovery (power+home+volume up) NOT safestrap recovery do a factory reset from there. That'll reflash stock rom and you can reroot + busybox + SS. Make sure to check what build you are on as well - if you are on NC2 kitkat you can only flash kitkat-based roms.
Click to expand...
Click to collapse
brisinger08, thanks for the input. i was running kit kat. i figured the s5 experience would be based off of kitkat too but i guess i should have checked first. i just tried that. when i got into the recovery boot the little android guy falls over. then i went to factory wipe and let it wipe. after that i went to reboot. when it rebooted it still had the little lock under the Samsung logo and after that screen it went straight to safestrap again. it hasn't seemed to change anything as far as i can tell. any other ideas?
sethers said:
sorry graydiggy. this seemed like a thread that had something to do with the same black screen i was getting. besides this one i only posted it on the stupid questions thread.
---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------
brisinger08, thanks for the input. i was running kit kat. i figured the s5 experience would be based off of kitkat too but i guess i should have checked first. i just tried that. when i got into the recovery boot the little android guy falls over. then i went to factory wipe and let it wipe. after that i went to reboot. when it rebooted it still had the little lock under the Samsung logo and after that screen it went straight to safestrap again. it hasn't seemed to change anything as far as i can tell. any other ideas?
Click to expand...
Click to collapse
If you're on the A3 bootloader then reflashing NC2 with odin will clear this up, (double-check in download mode) then follow the instructions in this thread. If you're on A2 you can still do this but it will overwrite your bootloader and lock you into NC2 so if that's the case you might want to read through that thread to make sure you're ok with that!