Related
Today I rooted my sensation using clockwork mod recovery and then installed supersu. It was working fine until I restarted my phone. Now whenever I try to turn it on I get stuck the the t-mobile stick together screen. I tryed factory resetting from the bootloader and nothing happened. Please keep any answers noob friendly. Not good with the technical terms. Thanks
Got this info from this command fastboot getvar all
not sure what it means but figured it would help
version: 0.5
version-bootloader: 1.27.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 3.32.531.14
product: pyramid
platform: HBOOT-8260
modelid: PG5810000
cidnum: T-MOB010
battery-status: good
battery-voltage: 3801mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 617f0a98
hbootpreupdate: 11
gencheckpt: 0
Hi,
Firstly ,you should hide your IMEI and serial number.
Can you please explain again exactly what you were doing?
You do not appear to have any radio...
malybru said:
Hi,
Firstly ,you should hide your IMEI and serial number.
Can you please explain again exactly what you were doing?
You do not appear to have any radio...
Click to expand...
Click to collapse
Okay so first thing I did was install the clockwork mod thing (it opens when I click recovery in bootloader)
Then I installed SuperSu through the sd card and clockwork
My phone worked fine for a little, but then no apps would open and I clicked reboot and it got stuck at the stick together screen... I tried installing mEMBERS rom to fix it just a few minutes ago, but nothing changed... thanks
More detailed steps
First I unlocked the bootloader with htcdev.
Then I flashed clockwork mod using onex installer tool kit (I think it's something like that)
I put the supersu zip on the ad card
I went into bootloader and went to recovery
I installed the supersu zip using that
Relocked the bootloader
reflash the RUU of tmobile one ..this way you can get the phone in working condition but will lose all the data fine ?
connect the phone from bootloader to pc and then double click on RUU thats all (btw you should relock your bootloader ..which i think you did it )
TMOUS ICS RUU ..here
Hi all!
Im in a big pickle here and I cant get myself out at the moment.
First hand.. The info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.17.31501S.10_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3917mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Now i've been running cyanogenmod 10 stable since I started rooting etc...
And it's been amazing, but now since there has been a release candidate for 10.1, I was looking into updating it.
I ran into an issue where my boot-loader was not accepted , therefor i would run into an error on Clockwork mod stopping me from flashing 10.1
The bad thing was that I erased my previous installation without backing up the stock and CM10.
So now i'm left with no system. Though I can get into Fastboot and ADB via recovery.I
For some reason if I try to flash CM10 (The rom and the boot file) the cyanogenmod logo will continue spinning.
I tried to fiddle around with my RUU afterwards because I currently have S-On. But i later learned that i need superCID.
^(Which i learned that you need your phone on to alter it to the 8 "1"s) Which i cant do because i have no system.
I might have already altered some files guessing that my boot-loader is named "dirty-d92cc658" and im afraid that I messed up something internally.
So anyways. Im here with my Ville S4 plugged in on fastboot not knowing what to do.
Any Help would be amazing , thank you
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
c19932 said:
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
Click to expand...
Click to collapse
Do I need to have superCID to flash RUU's ?
Mozziliac said:
Do I need to have superCID to flash RUU's ?
Click to expand...
Click to collapse
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
tivofool said:
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
Click to expand...
Click to collapse
How can I superCID my phone if I cant boot into the rom?
I've never superCid, can't help you there.
Good news is you can get into bootloader still.
You could fastboot flash a boot.img and flash a rom in recovery.
Just need to mount usb storage in recovery to put the rom.zip on your phone.
Edit: reread that you tried that but rom didn't boot. Hopefully you waited 5-10 min for first load.
try wipedata/factory reset from CWM like 3 times then flashing?
Good luck to ya.
Edit 2: kind of wondering if you can run the Rogers RUU with that low of a bootloader (version-bootloader: 1.13.0000)
Maybe someone can chime in, because that would be nice not having to SuperCid.
Alright so I seemed to get it running on CM 10 by switching recoveries and flashing it's boot.
Then I was able to superCID the phone, which then lead my into S-off'ing it.
Then I was able to update the hboot firmware to 2.15
Cleared the cache and installed the new kernel and flashed cyanogenmod 10.1 rc
Everything went well after that. I did run into a laggy issue, which I then fixed by switching the CPU governor to ondemand instead of interactive.
Thanks for the post guys
Ok, I'll start from the beginning.
I purchased my phone from Rogers at April 2012. So it was Rogers stock 4.0.x rom, everything was locked at that time. I FORGOT the stock hboot/ruu version number for Rogers ONE XL.
From the time being, I rooted it, superCID, unlocked via HTC DEV. After these, I flashed customer recovery, and successfully flashed several roms from time being. Finally I stayed with ViperXL.
Then, facepalm s-off is released, and I s-offed my phone. Everything worked just fine.
The problem occurred when I started to flash sense 5 roms about couple weeks ago. I did not upgrade my firmware and I flashed sense 5 based roms (this is my bad), so I'm experiencing random reboot and signal drops. Then I upgraded my firmware using the instruction in this tread: http://forum.xda-developers.com/showthread.php?t=2423735 . I verified my installtion with ./fastboot gervar all . At this time, there were two warnings on the top of my bootloader: "tampered" and "unlocked".
So, at this time, I tried several sense 5 roms. My recovery at this time was TWRP 2.6.3.0. All the roms have one common problem on my phone: after I locked the screen and left my phone for a while, if I wanna wake my phone/display, nothing happened by pressing the power button. I have to press the power button for 10+ seconds to restart my phone. If I just left my phone for a short time and wake it, it will work properly.
I was thinking are these sense 5 problems, so I tried to flash cm roms yesterday. I followed the instructions in http://forum.xda-developers.com/showthread.php?t=2382933 to upgrade my RUU to 3.18. I flashed TWRP 2.6.3.0, and tried to flash cm 10.1 and 10.2. For cm 10.2, there were a lot of force close when I boot my phone. For cm 10.1, it is so unstable with random reboots as well as did not respond when I try to wake up the phone. I am not questioning CM's roms, I am sure there were something wrong with my phone or what I've done to it.
So, I tried to flash viper rom again with ruu 3.18 installed. The rom won't even boot...... However I found something interesting when I am flashing the viper rom. The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.
Then I re-installed the RUU 3.18 update on my phone. Right now, the AT&T stock rom also will not respond after I left my phone idle for a moment......
User timmaaa kindly reminds me about something. I am posting the original post I started in another tread.
Originally Posted by snake3276120 View Post
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/show....php?t=2382933
I boot into bootloader, and ran fastboot getvar all, the result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT246W304864
(bootloader) imei: 359691041684351
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4122mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I'm assuming "(bootloader) version-main: 3.18.502.6" is the RUU version. I also flashed an hboot 2.14, it became 3.17.xxxxxxx. That'w why I am assuming this is the RUU number.
Ok, regardless of the build number or ruu...... I think there is something wrong with my bootloader. It doesn't matter which hboot I flash (hboot 2.14 with version-main 3.17/3.18, or hboot 2.15 with version-main 5.08), and I tried several twrp (2.4.4.0 and 2.6.3.0). The time it took to flash viper xl is really short while viper xl has 700MB. It is even shorter than the time I flash CM, which is around 180 MB. (Sorry for the bad English, I actually mean "The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.")
I guess I'll start with the current AT&T stock rom (which still lose respond after I left the phone open for a while, and I have to press the power button for 10 secs to reset my phone)on hboot 2.14 and ruu 3.18. Root it, try to s-off again. Not sure if this will solve the problem.
Something interesting when I'm booting my phone, when the phone displays only the green HTC in the middle of the display, there is some text below it... saying something like "This is an internal build, do not distribute outside of HTC, failure may cause to law action". However, the AT&T stock rom I'm running right now does not have this.
timmaaa:
It's a bit hard to follow what you're saying there but here goes. It's not the RUU number it's the build number. An RUU is the program that updates your phone, the reason you see them referred to as the 3.18 RUU is because they're known by the build number that they update your phone to.
Did you check the md5 of the downloaded file as someone else suggested? It might be corrupt. Also, maybe you should try TWRP 2.6, versions 2.4.x and 2.5.x are well known as being very buggy, and I've seen people have issues with version 2.6.3 too. 2.6 is rock solid though.
The red text you see when the phone boots up is completely normal for a modified phone so you needn't worry about that. The reason the stock ROM doesn't have it is because the RUU has returned your phone to being completely stock, therefore not modified, therefore no red text.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
OK, I am wondering where I can get my RUU number......
Also, in this case, what I should do now? Install TWRP 2.6.0.0 and try to flash everything again?
Currently "tampered" is gone from my bootloader, only "unlocked" stays there.
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
Because some posts are saying RUU 3.17 or 3.18, so I got confused...... but as long as it's a program, I will assume they are talking about the firmware or bootloader after running RUU 3.17 or 3.18 upgrade.
timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
I fixed the qoute
Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita
timmaaa said:
Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita
Click to expand...
Click to collapse
That's right, I didn't even flash recovery... Well, my stock rom just self-rebooted, and stuck at booting animation while adb is still able to recognize it, and I can issue a reboot from adb. This also applies to my sense 5 roms.
If it's hardware problem, looks like upgrading to hboot 2.15 ruined my hardware, which is hard to believe...... Everything works fine before I upgrade my hboot to 2.15
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I know... it is unfortunate...
timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.
snake3276120 said:
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.
Click to expand...
Click to collapse
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.
Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita
timmaaa said:
Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita
Click to expand...
Click to collapse
I used 2.6.0.0 to flash my current magiorom 4..... well at least it is usable now, with app/sense/notification bar/wake phone do not respond sometimes... I'm not blaming the rom, I am blaming my phone... probably now it's the time to get a new one lol
redpoint73 said:
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.
Click to expand...
Click to collapse
Here you are, boss.
PS E:\Program Files (x86)> cd '.\Minimal ADB and Fastboot'
PS E:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3874mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
PS E:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I think the result is the same in thread http://forum.xda-developers.com/showthread.php?t=2423735
Quoted from the thread:
Install:
Installing the rom:
Download the rom and copy to your sdcard
Reboot to Recovery
Flash rom
I recommend you wipe data before or after flashing the rom
For root access, flash this: Flash this in recovery for root access
Reboot
OPTIONAL: Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this! Flash at own risk!)
Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
Run: fastboot oem rebootRUU
Run: fastboot flash zip <PathToFirmware.zip>
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN
If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
Verify everything was successful by running: fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Reboot into Android: fastboot reboot or into recovery: fastboot reboot-recovery
Click to expand...
Click to collapse
Please refer to the attachment for a photo of my bootloader
Will TWRP 2.3.3.0 solve my problem? It looks like most roms recommend this recovery.... btw I'm running 2.6.0.0 at the moment.
No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita
timmaaa said:
No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita
Click to expand...
Click to collapse
lol thanks... Every time before I flash a new rom, I just format everything...
I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita
timmaaa said:
I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...
snake3276120 said:
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...
Click to expand...
Click to collapse
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4
sandys1 said:
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
Ok I'll do a backup and try tonight....latest twrp do u mean 2.6.3.0, or there is another new release?
Hey guys already tried everything and everything is still same so what's my problem here we go. 5 Hours ago or less downloaded stock rom and installed with recovery mods everything was great until the phone restarting after android boot logo appears after 1 min device starting to boot loopping . Also i cant handle recovery or factory reset. While installing the rom something comes around " want to install supersu?" and i said no , and why answered no , because thought already this rom has superuser mod . so why i have this problem i know about rooting and i cant open anything to install superuser also with adb i cant handle the device some commands working but others not. Please help me searched almost all the words but still i cant fix that .
Thanks.
Edit: Also when trying to push ROM to sdcard getting " error: device is not found" downloaded all the sdk things and drivers still cannot connect to cmd prompt.
Edit2 : So still trying to do something i think the problem is as i said rooting. The main question is how i can root my device without recovery mode because i cant handle it also i cant push anything with adb , and its so annoying i cant handle anything please help me :/
Korvacs said:
Hey guys already tried everything and everything is still same so what's my problem here we go. 5 Hours ago or less downloaded stock rom and installed with recovery mods everything was great until the phone restarting after android boot logo appears after 1 min device starting to boot loopping . Also i cant handle recovery or factory reset. While installing the rom something comes around " want to install supersu?" and i said no , and why answered no , because thought already this rom has superuser mod . so why i have this problem i know about rooting and i cant open anything to install superuser also with adb i cant handle the device some commands working but others not. Please help me searched almost all the words but still i cant fix that .
Thanks.
Edit: Also when trying to push ROM to sdcard getting " error: device is not found" downloaded all the sdk things and drivers still cannot connect to cmd prompt.
Click to expand...
Click to collapse
Is your one mini international or at&t?also, can you go to your boot loader? just hold down the power button until ur phone is turn off and hold volume down and power. if ur model is the at&t one, you can take the at&t ruu. if not idk what u can do.
abzboi said:
Is your one mini international or at&t?also, can you go to your boot loader? just hold down the power button until ur phone is turn off and hold volume down and power. if ur model is the at&t one, you can take the at&t ruu. if not idk what u can do.
Click to expand...
Click to collapse
Nope its international i bought it from Turkey i think its international also tried HBOOT recovery thins as i said recovery mode is doesnt working anymore . Entering recovery text appear then black screen coming and then device continue loopping forever.
Still waiting for any help guys please.
Also device information here maybe it helps to make something.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.22.40e.00.07
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3ADWA03301
(bootloader) imei: 35586605630****
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-871d213f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Korvacs said:
Still waiting for any help guys please.
Also device information here maybe it helps to make something.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.22.40e.00.07
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3ADWA03301
(bootloader) imei: 35586605630****
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-871d213f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
If your boot loader is unlocked, then flash a recovery. Flash the twrp 2.6 one not that newest one. And I hope it'll work. Good luck
abzboi said:
If your boot loader is unlocked, then flash a recovery. Flash the twrp 2.6 one not that newest one. And I hope it'll work. Good luck
Click to expand...
Click to collapse
Wont work flashed recovery again and still same thing happened boot loopping
Korvacs said:
Wont work flashed recovery again and still same thing happened boot loopping
Click to expand...
Click to collapse
Can you go to recovery after flash the twrp 2.6.0.0?
Edit: Hey I think I know what you did wrong. Did you flash the boot.img from the zip in the boot loader after flashing the rom? If not go ahead and try. You won't be able to boot through htc logo until you flash the boot.img.
abzboi said:
Can you go to recovery after flash the twrp 2.6.0.0?
Edit: Hey I think I know what you did wrong. Did you flash the boot.img from the zip in the boot loader after flashing the rom? If not go ahead and try. You won't be able to boot through htc logo until you flash the boot.img.
Click to expand...
Click to collapse
Yup first flashed recovery then flashed boot.img but still same thing stuck at htc boot screen and recovery wont working.
Here we go Flashed this http://forum.xda-developers.com/showthread.php?t=2594253 recovery mode and worked now what to i dont know but still trying to fix it.
Korvacs said:
Here we go Flashed this http://forum.xda-developers.com/showthread.php?t=2594253 recovery mode and worked now what to i dont know but still trying to fix it.
Click to expand...
Click to collapse
reflash the rom?
abzboi said:
reflash the rom?
Click to expand...
Click to collapse
Yeah trying to move rom file to sdcard but its more harder for me , i think . Also in ADB Cmd promt while in sideload recovery mode my device was there so its good growth for me So after installing rom.zip getting weird error .
Korvacs said:
Yeah trying to move rom file to sdcard but its more harder for me , i think . Also in ADB Cmd promt while in sideload recovery mode my device was there so its good growth for me So after installing rom.zip getting weird error .
Click to expand...
Click to collapse
Try to install a different rom. The newest 4.3 rom that trigger made
abzboi said:
Try to install a different rom. The newest 4.3 rom that trigger made
Click to expand...
Click to collapse
You mean magio rom ? i am trying to install stocked rom i think its better than modded rom . Also i cant move rom file to sdcard the problem is here i think . I can give teamviewer id pw if u want to help me please.
Korvacs said:
You mean magio rom ? i am trying to install stocked rom i think its better than modded rom . Also i cant move rom file to sdcard the problem is here i think . I can give teamviewer id pw if u want to help me please.
Click to expand...
Click to collapse
Is adb not working for you?
Solved
Anyway fixed everything and flashed stocked rom from trigger. This device make a so much headcache nevermind thanks for helping " abzoi"
Korvacs said:
Anyway fixed everything and flashed stocked rom from trigger. This device make a so much headcache nevermind thanks for helping " abzoi"
Click to expand...
Click to collapse
No problem, glad to hear that your device is working again I hope you'll enjoy you one mini
abzboi said:
No problem, glad to hear that your device is working again I hope you'll enjoy you one mini
Click to expand...
Click to collapse
Yup finally i fixed it but it took almost 24 hours to work it Flashed 4.3 rooted stock rom and working well :good:
Korvacs said:
Yup finally i fixed it but it took almost 24 hours to work it Flashed 4.3 rooted stock rom and working well :good:
Click to expand...
Click to collapse
I had a problem too yesterday. I finally know how to use adb now.
Hello,
I'm looking for sensation's backup or boot.img for mainver 3.33.707.51 and HTC__044 CID
Urgently !
Thank's
octopus82 said:
Hello,
I'm looking for sensation's backup or boot.img for mainver 3.33.707.51 and HTC__044 CID
Urgently !
Thank's
Click to expand...
Click to collapse
what did you do exactly?
post also your bootloader info pls
rzr86 said:
what did you do exactly?
post also your bootloader info pls
Click to expand...
Click to collapse
I've flashed another boot.img, for old version then I have error wifi
and I think that the device run with an custom rom with s-on
bootloader 1.27
Thank's
octopus82 said:
I've flashed another boot.img, for old version then I have error wifi
and I think that the device run with an custom rom with s-on
bootloader 1.27
Thank's
Click to expand...
Click to collapse
just download the rom you have
extract the boot.img and flash it via fastboot command
rzr86 said:
just download the rom you have
extract the boot.img and flash it via fastboot command
Click to expand...
Click to collapse
I CAN'T FIND MY VERSION DUDE
so I hope if some one have it or can make an backup to help me
Thank's
octopus82 said:
I CAN'T FIND MY VERSION DUDE
so I hope if some one have it or can make an backup to help me
Thank's
Click to expand...
Click to collapse
actually mate we have to know what rom you have
the only thing i can tell you now is to flash a custom rom from recovery
edit: go to phone info
maybe it is says something there
rzr86 said:
actually mate we have to know what rom you have
the only thing i can tell you now is to flash a custom rom from recovery
edit: go to phone info
maybe it is says something there
Click to expand...
Click to collapse
I'm on s-on and I can't go on s-off, I have error issu everytime with JB method
another solution please ?
octopus82 said:
I'm on s-on and I can't go on s-off, I have error issu everytime with JB method
another solution please ?
Click to expand...
Click to collapse
you confused me now
do you have wifi error or are you trying to S-OFF?
if you have trouble with jb method say what error you have
rzr86 said:
you confused me now
do you have wifi error or are you trying to S-OFF?
if you have trouble with jb method say what error you have
Click to expand...
Click to collapse
I have wifi error, et and I'm trying to s-off to change cid cause I can't find my mainver rom
version: 0.5
version-bootloader: 1.27.0000
version-baseband: 11.24A.3504.31_M
version-cpld: None
version-microp: None
version-main: 3.33.707.51
serialno: ###############
imei: ################
product: pyramid
platform: HBOOT-8260
modelid: PG5813000
cidnum: HTC__044
battery-status: good
battery-voltage: 4148mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 617f0a98
hbootpreupdate: 11
octopus82 said:
I have wifi error, et and I'm trying to s-off to change cid cause I can't find my mainver rom
version: 0.5
version-bootloader: 1.27.0000
version-baseband: 11.24A.3504.31_M
version-cpld: None
version-microp: None
version-main: 3.33.707.51
serialno: ###############
imei: ################
product: pyramid
platform: HBOOT-8260
modelid: PG5813000
cidnum: HTC__044
battery-status: good
battery-voltage: 4148mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 617f0a98
hbootpreupdate: 11
Click to expand...
Click to collapse
ok then in order to S-OFF you must have stock rom in your device
you can use the flashable zip(link in my signature)
otherwise you can use the appropriate ruu.exe for your device
see this thread
http://forum.xda-developers.com/showthread.php?t=1672425
relock first the bootloader(if it is unlocked)
rzr86 said:
ok then in order to S-OFF you must have stock rom in your device
you can use the flashable zip(link in my signature)
)
Click to expand...
Click to collapse
flashble with s-on ?!
rzr86 said:
if you have trouble with jb method say what error you have
Click to expand...
Click to collapse
S-OFF Failed
Errorcode: 66732337
ErrorMsg: Still sober
when I do a wire strike the sd card not working after that
I've found this in htcdev/download
http://dl4.htc.com/RomCode/Source_and_Binaries/pyramid-ics-crc-3.0.16-8626210.zip
it's a file for mu mainver
I've flashed it with PG58IMG.zip from bootloader with sd card, but still wifi error
Can somebody tell if I can excrat an firmware.zip from this file ?
Thank's
octopus82 said:
flashble with s-on ?!
Click to expand...
Click to collapse
yes you can
just put it in your sdcard
boot your device into recovery(i suggest to install 4ext recovery if you don't have it already)
format all partitions from except sdcard from 4ext
enable smartflash from 4ext(because you are on S-ON)
flash the rom
octopus82 said:
S-OFF Failed
Errorcode: 66732337
ErrorMsg: Still sober
when I do a wire strike the sd card not working after that
Click to expand...
Click to collapse
format your sdcard or try with a different one
octopus82 said:
I've found this in htcdev/download
http://dl4.htc.com/RomCode/Source_and_Binaries/pyramid-ics-crc-3.0.16-8626210.zip
it's a file for mu mainver
I've flashed it with PG58IMG.zip from bootloader with sd card, but still wifi error
Can somebody tell if I can excrat an firmware.zip from this file ?
Thank's
Click to expand...
Click to collapse
you can't flash firmware while on S-ON
did you try to use any ruu.exe?
rzr86 said:
yes you can
just put it in your sdcard
boot your device into recovery(i suggest to install 4ext recovery if you don't have it already)
format all partitions from except sdcard from 4ext
enable smartflash from 4ext(because you are on S-ON)
flash the rom
format your sdcard or try with a different one
you can't flash firmware while on S-ON
did you try to use any ruu.exe?
Click to expand...
Click to collapse
Thank you very very much dude, I'll never forget your help
The problem is solved
octopus82 said:
Thank you very very much dude, I'll never forget your help
The problem is solved
Click to expand...
Click to collapse
wifi is working mate?
rzr86 said:
wifi is working mate?
Click to expand...
Click to collapse
evreything work perfectly
Thank's