Related
I'm making 2 ROMs right now.
One will be a deodexed, rooted, base for any dev to use to make a ROM. No need to ask for permission, just give me credit. That's all I ask.
There other will be for people who want to go back to complete stock that do not have the RUU.
AT&T Stock ROM (credits to olorolo for providing the nandroid!)
http://d-h.st/e2m
AT&T Stock Deodexed Rooted Base (Devs Only)
http://d-h.st/qmd
Both files are now uploaded!
Thanks man! Getting it now for that "just in case" moment.
Sent from my HTC One X+ using Tapatalk 2
droidiac13 said:
Thanks man! Getting it now for that "just in case" moment.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
That was the purpose of it
hasoon2000 said:
I'm making 2 ROMs right now.
One will be a deodexed, rooted, base for any dev to use to make a ROM. No need to ask for permission, just give me credit. That's all I ask.
There other will be for people who want to go back to complete stock that do not have the RUU.
AT&T Stock ROM (credits to olorolo for providing the nandroid!)
http://d-h.st/e2m
AT&T Stock Deodexed Rooted Base (Devs Only)
http://d-h.st/qmd
Click to expand...
Click to collapse
Wow you are fast. Thanx
Sent from my HTC One X+ using xda premium
Excuse the newbie questions I am about to ask. Feel free to point me in a different direction.
I was working on a friends phone and I unintentionally loaded the wrong boot.img when attempting to root his phone.
Now his phone is stuck at the boot screen.
When i try to run recovery it just sits there at the recovery screen with a red !.
I downloaded your files but I cant load it to the phone because my PC wont load the mass storage device. (
I am stuck. I appreciate any help I can get at this point.
dekend said:
Excuse the newbie questions I am about to ask. Feel free to point me in a different direction.
I was working on a friends phone and I unintentionally loaded the wrong boot.img when attempting to root his phone.
Now his phone is stuck at the boot screen.
When i try to run recovery it just sits there at the recovery screen with a red !.
I downloaded your files but I cant load it to the phone because my PC wont load the mass storage device. (
I am stuck. I appreciate any help I can get at this point.
Click to expand...
Click to collapse
Pull boot.IMG from my zip. Place it in the kernels folder of my toolkit. Boot into bootloader. Press "with this command" to flash the boot.img.
Support is done for the night. Goodnight!
Sent From My HTC Amaze 4G via Someone's Room
Questions about the AT&T Stock ROM. When you say "for people who want to go back to complete stock"....
Will this lose root then? Also, will it replace TWRP recovery?
Thanks!
wmg316 said:
Questions about the AT&T Stock ROM. When you say "for people who want to go back to complete stock"....
Will this lose root then? Also, will it replace TWRP recovery?
Thanks!
Click to expand...
Click to collapse
Yes and yes. You might need to relock the bootloader if you flash a stock RUU (not officially available for AT&T yet). Once installed you can unlock and root again.
wmg316 said:
Questions about the AT&T Stock ROM. When you say "for people who want to go back to complete stock"....
Will this lose root then? Also, will it replace TWRP recovery?
Thanks!
Click to expand...
Click to collapse
Since there is no RUU, this is a flashable zip in TWRP. You can flash this to get your phone up and running. However, this will not replace TWRP.
If your phone is messed up and you want root as well, flash the deodexed and rooted ROM.
hasoon2000 said:
Since there is no RUU, this is a flashable zip in TWRP. You can flash this to get your phone up and running. However, this will not replace TWRP.
If your phone is messed up and you want root as well, flash the deodexed and rooted ROM.
Click to expand...
Click to collapse
Oh! OK. My phone is not messed up, I am just waiting on an AT&T deodexed ROM to be made!
So...that leads me to one more question, and I'll leave you alone!
The 'AT&T Stock Deodexed Rooted Base (Devs Only)' ROM in the OP is a fully operational ROM? The statement in the OP "One will be a deodexed, rooted, base for any dev to use to make a ROM" made me think these were base files to be used to create a ROM. So if it is a fully operational ROM, I could use that, right...even if my phone is NOT messed up? (well, that was two questions). I am still stock at the moment...
wmg316 said:
Oh! OK. My phone is not messed up, I am just waiting on an AT&T deodexed ROM to be made!
So...that leads me to one more question, and I'll leave you alone!
The 'AT&T Stock Deodexed Rooted Base (Devs Only)' ROM in the OP is a fully operational ROM? The statement in the OP "One will be a deodexed, rooted, base for any dev to use to make a ROM" made me think these were base files to be used to create a ROM. So if it is a fully operational ROM, I could use that, right...even if my phone is NOT messed up? (well, that was two questions). I am still stock at the moment...
Click to expand...
Click to collapse
It's a fully operational ROM. You can flash it even if your phone isnt messed up. So think of it as a custom ROM. You can just flash it in TWRP.
Downloading now! This marks day 3 with no phone! I hope this ends my nightmare. Thank you so much.
hasoon2000 said:
It's a fully operational ROM. You can flash it even if your phone isnt messed up. So think of it as a custom ROM. You can just flash it in TWRP.
Click to expand...
Click to collapse
Thanks. Just to make sure I have the steps straight (in a manual method):
Copy 'evitareul_dev_base.zip' to my internal memory ("/storage/internal memory/" in Solid Explorer)
Unlock device with Unlock Code from HTC.dev
Install AT&T Recovery provided in the All-In-One Tool; reboot to bootloader and flash recovery
fastboot flash recovery recovery.img
Enter Recovery and flash the 'SuperSU.zip' from the all-in-one tool folder
At this time I would be stock and rooted, correct?
Return to bootloader and install kernel provided in the 'AT&T Stock Deodexed Rooted Base (Devs Only)'
fastboot flash boot boot.img
Return to recovery and perform wipes....here is where I am unsure after reading the "Important and Read" threads about the /data/media. I am accustom to doing these wipes from TWRP on my OneX: (1) factory reset, (2) wipe dalvik cache and (3) wipe System....Is that what I need to do for the OneX Plus?
Install 'evitareul_dev_base.zip' ROM from recovery
I appreciate your response! I don't want to mess anything up...I guess I'm over precautious!!
I wiped, guess i wiped the wrong thing, now rom wont boot. i can get to recovery, twrp, but how do i now get this zip on to the phone since i cant boot? mount in twrp im not seeing anything on my computer. ATT X+
@nugzo. Did you have the zip on the device prior to entering recovery and performing the wipes?
EDIT: If so, what wipes did you perform?
wmg316 said:
@nugzo. Did you have the zip on the device prior to entering recovery and performing the wipes?
EDIT: If so, what wipes did you perform?
Click to expand...
Click to collapse
yes i did but it was the wrong zip. It was mikes 1986 rom, at the time i didnt realize it wasnt for ATT. So after wiping, i guess i wiped the stock rom. Wiped system, data, and davlik. now it just sits at HTC quietly brilliant screen.
---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------
trying the sideload adb in twrp but that didnt work, says no device found. when i do adb devices my device shows though. now i, trying to get this stock rooted installed.
Wiping System, Data, Dalvik definitely wipes the stock ROM!
Hmmmm. Mike's OP states nearly on the first line of his thread: "Not working with AT&T One X+ LTE"
All that I've read is that you have to have the ROM on the device before booting to recovery...but there was a statement that it could be adb pushed:
http://forum.xda-developers.com/showthread.php?p=34358646#post34358646
With "no device found"...I'm not sure what to do...Hopefully one of the devs will ring in for you.
title
hasoon2000 said:
I'm making 2 ROMs right now.
One will be a deodexed, rooted, base for any dev to use to make a ROM. No need to ask for permission, just give me credit. That's all I ask.
There other will be for people who want to go back to complete stock that do not have the RUU.
AT&T Stock ROM (credits to olorolo for providing the nandroid!)
http://d-h.st/e2m
AT&T Stock Deodexed Rooted Base (Devs Only)
http://d-h.st/qmd
Click to expand...
Click to collapse
thanks. im sorry im noob i think are many people look around for this maybe if you include AT&T in the thread title more people are happy. excuse my english. thanks againg.
---------- Post added at 08:59 AM ---------- Previous post was at 08:00 AM ----------
hi i have unlimit internet no lte (i dont wan it because change my monthly pay) with my past at&t vivid i change the apn and still with unlimit internet with 5 to 7 mb speed with my international HOX i change the apn and still with unlimit iternet but no more than 3mb speed. now with your AT&T Stock Deodexed Rooted Base can i change the apn and still with my unlimit internet. i dont wan LTE. thanks. i go now to buy my new at&t HOX+.
Lloir said:
providing you dont touch the "wipe internal memory" button all is good, i use TWRP and i've been performing about 20-30 wipes a day, and my internal sd is still intact with my TWRP backups
Click to expand...
Click to collapse
from the other thread
I was on Stock rom 1.73.720.1 (Rooted). Today, i installed an app from market named 'Font Installer*Root*'. After installing fonts from that app, when i restarted my phone it won't start.
I mean the phone boots up but it gets stucked at HTC logo & Beats audio logo.
I did factory reset and wiped data from recovery but still stucked.
Any help here?
rockhardy said:
I was on Stock rom 1.73.720.1 (Rooted). Today, i installed an app from market named 'Font Installer*Root*'. After installing fonts from that app, when i restarted my phone it won't start.
I mean the phone boots up but it gets stucked at HTC logo & Beats audio logo.
I did factory reset and wiped data from recovery but still stucked.
Any help here?
Click to expand...
Click to collapse
You must go back to the stock RUU, and make the updates. After this operation you can install custom roms , follow this steps
1) Lock phone
a. Boot into fast boot
b. Connect USB
c. With command prompt : “fastboot oem lock”
2. Install original RUU
a. Reboot system
b. Connect USB
c. Run original RUU.exe
d. Follow onscreen instructions.
3. System will be rebooted. Follow setup instructions. Don’t bother too much with the settings, although make sure you set language to English and set up a WIFI if possible. That will be useful for downloading the update.
4. Update OTA
a. Go to settings >> about >> software updates >> check now
b. If asked select to download the update.
c. After downloading select ‘Install now’.
d. This will take a while. When finished you can check your version in about >> software version.
5. Unlock phone
a. Boot into fastboot
b. Connect USB
c. Run “fastboot flash unlocktoken” unlock_code.bin
install your custom rom
it is a long way, but it works
Thanks for replying.
But i can't find suitable RUU for me. I am from India and the RUU here i can see is of Chinese ROM. So, won't there be a problem installing that?
Look, maybe it works
http://forum.xda-developers.com/showpost.php?p=35362091&postcount=5
flight727 said:
Look, maybe it works
http://forum.xda-developers.com/showpost.php?p=35362091&postcount=5
Click to expand...
Click to collapse
on the old ROM AND BASEBAND is this right - but I do not believe that this will works for downgrade to the old version - as the Version 1.730.720.1 come with a new baseband ....
...
I had the same problem with this app ... and the only way to solve this, was to advanced restore "SYSTEM" from a CWM BACKUP .....
I was on Stock rom 1.73.720.1 (Rooted).
Click to expand...
Click to collapse
In my opinion you have two ways to solve your problem:
The First Solution
If you have a backup - you only have to do the same ..
boot into recovery and use the advanced restore function
second way
is to download the flashable zip of aka_noodle
Version 1.73.707.1 ASIA (works fine on our devices)
http://forum.xda-developers.com/showthread.php?t=2044839
flashing this kernel (boot.img) is mandatory to have full BT and WIFI Function
the way to flash it can you find in the same posting
or flash the other ZIP from aka_noodle from this posting
Version 1.73.404.3 EUROPE(I will test this version this night)
http://forum.xda-developers.com/showthread.php?t=2007243
Hope I could help you
Thanks a lot for your Help, tomcatz.
tomcatz666 said:
on the old ROM AND BASEBAND is this right - but I do not believe that this will works for downgrade to the old version - as the Version 1.730.720.1 come with a new baseband ....
I had the same problem with this app ... and the only way to solve this, was to advanced restore "SYSTEM" from a CWM BACKUP .....
Click to expand...
Click to collapse
You're right. But if you desire to do an OTA update, you need the downgrade with a matching RUU.
In my Chinese T328w I could downgrade the following RUU "RUU_PRIMO_DS_ICS_40A_HTCCN_CHS_CU_1.56.1402.6_Radio_1.06.34D.05_20.22.30.23U_release_264849_signed" perform.
Or I'm wrong????
AW: Phone not starting up
flight727 said:
You're right. But if you desire to do an OTA update, you need the downgrade with a matching RUU.
In my Chinese T328w I could downgrade the following RUU "RUU_PRIMO_DS_ICS_40A_HTCCN_CHS_CU_1.56.1402.6_Radio_1.06.34D.05_20.22.30.23U_release_264849_signed" perform.
Or I'm wrong????
Click to expand...
Click to collapse
Thats right for OTA you must be on original Stock, but therefor you should make a backup with cwm recovery BEFORE you flash anything other than the Stock... And if you want to get the OTA for your device, then restore the backup, relock the phone and anything is okay.
Btw Last night I flashed the european custom rom from aka_noodle and the Phone stocked long time at boot screen... I solved this by restoring only the DATA with the advanced restore option of cwm recovery... after that I flashed the boot_1.img via the adb fastboot command and now I am an EUROPEAN with full function of Wifi and BT
Sent from my HTC Desire V using xda premium
I've the same problem installing chain fire 3d
now stuck on htc screen.
I had backed up with titanium.. All aps and systm
but dunno how to exactly restore.... pls pls hlp
Sent from my GT-N7000 using xda premium
---------- Post added at 06:13 PM ---------- Previous post was at 06:08 PM ----------
my restore is not working.. It says md 5 mismatch
Sent from my GT-N7000 using xda premium
hi
saifkhantt said:
I've the same problem installing chain fire 3d
now stuck on htc screen.
I had backed up with titanium.. All aps and systm
but dunno how to exactly restore.... pls pls hlp
Sent from my GT-N7000 using xda premium
---------- Post added at 06:13 PM ---------- Previous post was at 06:08 PM ----------
my restore is not working.. It says md 5 mismatch
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
you also need to go back to stock RUU and install rom again
Also Me Get This Problem with my Phone
My Phone: HTC Desire SV T326e ( Dual Sim )
Any can help me ?, Please
Dumb question but as I have only ever used CWM and 4ext, I am unsure what settings to use for backing up my rom in TWRP. Can someone enlighten me so that I can perform a backup just in case future flashing goes wrong I have a full backup to return to.
Would I be right in thinking there is no point in backing up the boot image, so I should just choose system and data? I just figured recovery can't flash a boot image anyway.
Bit confusing with the internal storage.
Thanks,
maritimesbob said:
Dumb question but as I have only ever used CWM and 4ext, I am unsure what settings to use for backing up my rom in TWRP. Can someone enlighten me so that I can perform a backup just in case future flashing goes wrong I have a full backup to return to.
Would I be right in thinking there is no point in backing up the boot image, so I should just choose system and data? I just figured recovery can't flash a boot image anyway.
Bit confusing with the internal storage.
Thanks,
Click to expand...
Click to collapse
You should use the TWRP
You boot into recovery mode.Select Backup.Tick all the options (system, data, cache etc..) And then drag the slider from left to right is done. Wait it finished backup and reset the machine you already have a full rom backup that
I wish you success
I am trying to run twrp without flashing it to the recovery partition. I read that I may be able to run it (once, without any permanent modification) with:
Code:
# fastboot boot openrecovery-twrp-2.3.3.0-enrc2b.img
downloading 'boot.img'...
OKAY [ 0.896s]
booting...
OKAY [ 0.008s]
finished. total time: 0.904s
but after typing that (htc one x+ intl unlocked) the device reboots and remains stuck at the boot with the HTC logo. My current goal would be to run twrp to backup the recovery partition (as first noob step) and possibly without making any permanent change to the phone. Is that even possible? Am I doing something wrong? Thank you.
AW: [Q] TWRP backup
it doesnt work.
recovery could not be backup at S-ON state
R: [Q] TWRP backup
it doesnt work.
recovery could not be backup at S-ON state
Click to expand...
Click to collapse
So I would be able to flash (write) it but not back it up (read) at S-ON?
If that's the case I would still prefer not to overwrite the recovery in order to use twrp to backup the system or for any other task. I also would like to test twrp before eventually flash it. It looks like:
Code:
fastboot boot boot.img
would be handy if I could get it to work.
Should I get to the S-OFF state for that?
Sent from my HTC One X+ using xda premium
fastboot flash boot boot.img
fastboot flash recovery <insert.img name here>
R: [Q] TWRP backup
Lloir said:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Sorry for my extreme cautiousness but I'm still researching before taking action.
Is flashing the boot.img potentially dangerous? If by accident I'll flash the wrong boot.img would I brick my device? For "brick" I mean a state where I can fix the issue only by physically opening the phone (I'm not concerned about data loss).
If the boot.img is wrong/damaged would fastboot still work?
Lloir said:
fastboot flash recovery <insert.img name here>
Click to expand...
Click to collapse
I have no doubt that this is going to work but I was wondering if I could run it without any modification as the "fastboot boot" command suggests.
Anyway at the moment what I want to do is a full backup of my device (boot.img, recovery.img, ...) so that later on I can eventually revert everything. Is there any guide about this?
Sent from my HTC One X+ using xda premium
maritimesbob said:
Dumb question but as I have only ever used CWM and 4ext, I am unsure what settings to use for backing up my rom in TWRP. Can someone enlighten me so that I can perform a backup just in case future flashing goes wrong I have a full backup to return to.
Would I be right in thinking there is no point in backing up the boot image, so I should just choose system and data? I just figured recovery can't flash a boot image anyway.
Bit confusing with the internal storage.
Thanks,
Click to expand...
Click to collapse
I understand you, I was a bit lost at first but it's pretty much the same. Take good advice that TWRP can not charge your phone in Recovery mode so make sure you have enough battery before entering Recovery. Battery level will always show 66% what ever the battery of your phone, it's known bug.
Reboot in Recovery -> select Backup -> (in Backup Device section) tick or untick what you want to preserve ( I personally do one full backup except cache and one with data only.) You can set a specific name via the Set Backup Name, once done you just have to slide the arrow button to start the backup process.
That's it, that easy.
No need to backup recovery, it stays in previous condition when you return to it in case need to
fedez1 said:
Sorry for my extreme cautiousness but I'm still researching before taking action.
Is flashing the boot.img potentially dangerous? If by accident I'll flash the wrong boot.img would I brick my device? For "brick" I mean a state where I can fix the issue only by physically opening the phone (I'm not concerned about data loss).
If the boot.img is wrong/damaged would fastboot still work?
Click to expand...
Click to collapse
Can anyone answer that?
Just to be more clear on what I'm trying to achieve; it's exactly what's explained here (for the galaxy nexus, but I thought it was possible on hox+ too):
youtube.com/watch?v=Z_5jgJe8G9k
(sorry I cannot post urls yet)
Thanks.
i would like to point out, it IS EXTREMELY HARD to brick our devices while it's S-ON, you would have to be doing really stupid stuff to brick your device with S-ON enabled.
fedez1 said:
Can anyone answer that?
Just to be more clear on what I'm trying to achieve; it's exactly what's explained here (for the galaxy nexus, but I thought it was possible on hox+ too):
youtube.com/watch?v=Z_5jgJe8G9k
(sorry I cannot post urls yet)
Thanks.
Click to expand...
Click to collapse
I guess I am having trouble comprehending why you want to do this. Just flash the recovery to the phone permanently. Or use CWM as it has no charging issues.
Lloir said:
i would like to point out, it IS EXTREMELY HARD to brick our devices while it's S-ON, you would have to be doing really stupid stuff to brick your device with S-ON enabled.
Click to expand...
Click to collapse
Sorry to be really pedantic but can you give me an example of a stupid thing that I could do to brick it? Downloading the wrong/corrupted boot.img and flashing it would brick (physical intervention required to repair) my device?
(Again sorry for asking again but I'm trying to really understand how things work. I'm a pretty experienced linux user so I would understand technical details).
---------- Post added at 12:59 AM ---------- Previous post was at 12:52 AM ----------
Kraizk said:
I guess I am having trouble comprehending why you want to do this. Just flash the recovery to the phone permanently. Or use CWM as it has no charging issues.
Click to expand...
Click to collapse
Since it's quite impossible to find the stock RUUs around, what I want to do now is to backup everything (even the stock recovery) before starting to flash anything new. Maybe what I'm trying to do doesn't make sense, can you explain me why I shouldn't care about the stock recovery? (eg: is it restored by the stock RUU before any ota update?, ...)
Also, being able to run twrp/cwm without flashing anything looks quite neat. I wonder why it works with the galaxy nexus and not with the hox+. Maybe it's somehow related to the S-ON (just a noob guess).
By flashing a boot.img of a wrong device is one example
Sent from my HTC One X+ using Tapatalk 2
fedez1 said:
Sorry to be really pedantic but can you give me an example of a stupid thing that I could do to brick it? Downloading the wrong/corrupted boot.img and flashing it would brick (physical intervention required to repair) my device?
(Again sorry for asking again but I'm trying to really understand how things work. I'm a pretty experienced linux user so I would understand technical details).
---------- Post added at 12:59 AM ---------- Previous post was at 12:52 AM ----------
Since it's quite impossible to find the stock RUUs around, what I want to do now is to backup everything (even the stock recovery) before starting to flash anything new. Maybe what I'm trying to do doesn't make sense, can you explain me why I shouldn't care about the stock recovery? (eg: is it restored by the stock RUU before any ota update?, ...)
Also, being able to run twrp/cwm without flashing anything looks quite neat. I wonder why it works with the galaxy nexus and not with the hox+. Maybe it's somehow related to the S-ON (just a noob guess).
Click to expand...
Click to collapse
Are you on the international or at&t variant. If international what country and carrier. I am almost positive I can find you an RUU to save. Also both stock recoveries are available on these forums.
Sent from my HTC One X+ using xda premium
AW: [Q] TWRP backup
fastboot is a tool with commands...
if hboot okay, phone is not bricked
Kraizk said:
Are you on the international or at&t variant. If international what country and carrier. I am almost positive I can find you an RUU to save. Also both stock recoveries are available on these forums.
Click to expand...
Click to collapse
That would be great! It's an UK Sim Free (I suppose international then), it doesn't have a specific carrier, but I'm using it with three.
I tried to follow some links for the stock RUU/recoveries but they're all not functioning.
Thanks.
---------- Post added at 09:51 AM ---------- Previous post was at 09:45 AM ----------
skdubg said:
fastboot is a tool with commands...
if hboot okay, phone is not bricked
Click to expand...
Click to collapse
That was my impression too. So probably the thing that I really need to understand is:
Code:
fastboot flash boot boot.img
is replacing hboot or some other part of the boot process? (eg. kernel/initram)
If it's replacing some other part of the boot process how flashing a broken/wrong boot.img can brick my phone? Wouldn't I be able to still use fastboot to flash a stock/correct boot.img again?
Thanks for all your clarifications.
we CANNOT even touch hboot with s-on, the ONLY thing flashing a boot.img is replacing the ramdisk and kernel. the worst that can happen if you flash a boot.img and it's corrupt or anything, you'll end up stuck at the HTC screen and forcing yourself to reboot into bootloader. FASTBOOT will be available for you to "repair" the device.
thanks
-Lloir
Hello there,
I have decided to ask for help after reading at least 100 threads here and on Android forum. I wanted to get custom ROM, so I've checked all guides - man everything over here, and I still managed to brick my phone! ( yellow triangle and no boot? )
----------
-at first I checked the bootloader, and I managed to unlock it using 2nd option in particular thread - some kind of software SE..+ code
-then downloaded Flashtool - done the drivers, changed firmware in the folder; download. OctanE, Gapps zip to my SD card.
and then I bricked my phone by incorrectly plugging, pressing and all that stuff while in Flashtool.
-so then I got Wotan, followed instruction, and of course I got stuck again.
-so I got LuPuS kernel and successfully flashed it, please do not ask how I have no idea.
Right now i would like to get OctanE, but I get to safe mode only by pressing volume down key.
Can somebody of you guys be so kind and guide me step by step ( I really do not understand what to do, sorry) how to get CWM, how to root it because I've got ROM Manager from Google play and it says the phone's not done.
thanks guys,
Veronika
Dear why you are doing such confusing activity.
Just do one thing if your booloader is unlocked then you just connect your phone to flashtool in fastboot mode and flash suitable custom kernel of your phone, by the way the kernel flashing is 5 seconds process,
And if you have flashed Lupus kernel then use POWER KEY WHEN MOBILE BOOTS UP AND PURPLE LED BLINKS instead of vol key to enter in recovery
Sent from my Xperia Live with Walkman using xda app-developers app
---------- Post added at 06:06 AM ---------- Previous post was at 06:03 AM ----------
Which phone you are using dear
Sent from my Xperia Live with Walkman using xda app-developers app
Hello,
i'm using xperia active st17i, ICS.587,
the problem is that when i flash custom kernel i.e. LuPuS, the phone is still not rooted, this one contains boot.img, and ROM Manager shows incorrect rooting.
belavera said:
Hello,
i'm using xperia active st17i, ICS.587,
the problem is that when i flash custom kernel i.e. LuPuS, the phone is still not rooted, this one contains boot.img, and ROM Manager shows incorrect rooting.
Click to expand...
Click to collapse
are you sure your bootloader unlocked properly?
Try to unlocked wth SE unlocked bootloader by quangnhut123, just 3 clicks Done . . .
Sent from my WT19i
gsOaymo Eighth
Hello,
problem Solved after 10 hours!! of fixing, un-bricking and frustration. Let me explain:
-------
I've had ICS .587 with bootloader unlocked and could not root it by downgrading to .0.62, my phone got bricked everytime. I didn't understand I could just flash pre-rooted one. So I have downloaded, flashed it and it contained CWM aswel.
Then I've flashed custom kernel Vengeance, after that OctanE, but my phone was a bit unstable, so I got LuPuS.
All done, there are too many guides and I got really confused.
Thanks for help
V.
Hi everyone, i get desire s yesterday .
I dont know what to do i only see this on screen when I go to bootloader. it hasn't a rom, only 1-2 sec a video like demo. I hear that this phone was promotial in market and dont have system.
What can I do? I know to download, a custom rom and install form TWRP because i use HTC One S but is it all i must to do on this desire S?
Look at the picture
Use fastboot to flash a recovery then flash ROM through new recovery
Sent from my Nexus 4 using Tapatalk 2
Is it all I need to do?
Go to htcdev.com and unlock your bootloader. Then flash a recovery using fastboot.
---------- Post added at 09:39 PM ---------- Previous post was at 09:31 PM ----------
Can you access your system?
wuksha said:
Is it all I need to do?
Click to expand...
Click to collapse
Cant say for sure as all you can tell me is you got a phone and it doesnt boot, this would be the first step in troubleshooting though
vhngu930 said:
Go to htcdev.com and unlock your bootloader. Then flash a recovery using fastboot.
---------- Post added at 09:39 PM ---------- Previous post was at 09:31 PM ----------
Can you access your system?
Click to expand...
Click to collapse
The phone is s-off, unlocking the bootloader with htcdev would be a step backwards
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Cant say for sure as all you can tell me is you got a phone and it doesnt boot, this would be the first step in troubleshooting though
The phone is s-off, unlocking the bootloader with htcdev would be a step backwards
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
What is s-off?
The top line on the pic, he has an engineering bootloader with radio secure flags removed (s-off)
Sent from my Nexus 4 using Tapatalk 2
Thanks guys,
i will record video tomorrow what I can see on phone and i hope it will bi enought to establish the diagnosis of a problem.
Hi again,
i flash recovery (there were only "!" in red triangle when I access recovery) , I try TWRP but touch function didn't work so i flash clockwork and i installed custom ROM but when i try to reboot only appear white screen with green text "htc" and it is all, i change ROMs several times but problem is the same. I dont know what to do now.
Look at the picture, near the touch there is "fail".
How did you install the ROM?
When in recovery make sure you do a full wipe, even better do this from fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery
Now boot to your new recovery again, wipe all, install a common stable ROM for your phone (like cyanogen) then before your reboot go to advance and copy recovery log, now reboot
If you still get stuck at splash post your recovery log
Sent from my Nexus 4 using Tapatalk 2
I flash clockwork recovery from fastboot and put rom on sd card and install from recovery.
i dont know what to do next, I changed hboot to ver 7.00.1002. and again only
appear.
Same again
Thanks demkantor, i tried that and problem didn't disappear. Only change is that after 10seconds phone turn off and again the same thing appear but this time forever. I notice that when I enter hboot i have this on screen on 1s look at the picture with green words. (I captured that earlier, now hboot ver is 7.00).
the second picture is about log I captured .
From the bootloader choose image CRC, it takes about 5 minuets capture but get it and then compare before and after flashing ROMs, if it changes its at least flashing to the right partition. And double check that the recovery your using is meant for your phone, also if you pull the full recovery logs onto SD card and then look at them you can check what partitions its trying to flash to
Sent from my Nexus 4 using Tapatalk 2
here is a pictures with old rom, when enter commands you give me at the botoom of this page, when i enter recovery, when instalation completed (I use this time ViperSaga2.2.0), and image CRC after installing ROM and Log after all of this.
Theres something missing and off hand I'm just not sure what, it sounds as if you are doing everything correctly.
I see you flashed a ROM with aroma installer, can you flash again only this time save the log at the end (from within aroma) and upload it?
Sent from my Nexus 4 using Tapatalk 2
I'm poor guy, i installed this and after that i can't access recovery and boot, now after every 10 seconds phone restart. look at the video in the link, I'm stupid now i dont know how to go step back.
Now the phone is boot only in bootloader. unlucky I...
VIDEO
There is probably a PG88IMG.zip that may help, but being I've never used your device before I would suggest asking your questions in your device's forum as someone there is sure to at least know what is going on. Probably should link this thread too in your new one.
There may be a common problem/solution for your phone that those in that forum will know, and being I'm on mobile its hard for me to search the forums to help without spending a huge amount of time
Best of luck and hopefully you can find your answer!
Sent from my Nexus 4 using Tapatalk 2