Related
Hi guys
I hope this is the right forum here, but I have still the same problem after asking google for hours.
I unlocked my one s via htcdev and the I want to install trickdroid but after flashing the boot.img nothing works any longer.
At the moment I get team win recovery running and I try to install cyanogen but it doesn't load. There is only the boot animation.
Hopefully you can help me to get anything running on my one s.
swtcw
PS: I'am really new to android!
swtcw said:
Hi guys
I hope this is the right forum here, but I have still the same problem after asking google for hours.
I unlocked my one s via htcdev and the I want to install trickdroid but after flashing the boot.img nothing works any longer.
At the moment I get team win recovery running and I try to install cyanogen but it doesn't load. There is only the boot animation.
Hopefully you can help me to get anything running on my one s.
swtcw
PS: I'am really new to android!
Click to expand...
Click to collapse
So as i understand it you can get into recovery ? how did you flash the boot.img?
Did u clear cache and factory reset?
swtcw said:
Hi guys
I hope this is the right forum here, but I have still the same problem after asking google for hours.
I unlocked my one s via htcdev and the I want to install trickdroid but after flashing the boot.img nothing works any longer.
At the moment I get team win recovery running and I try to install cyanogen but it doesn't load. There is only the boot animation.
Hopefully you can help me to get anything running on my one s.
swtcw
PS: I'am really new to android!
Click to expand...
Click to collapse
What hboot/exact steps for flashing? S3 or S4 processor?
Whats the exact rom and version you're trying to flash?
Sent from my HTC One S using xda premium
Check the HBOOT version that you are using with that required. That is the biggest problem when it comes to bootloops in this phone.
Basic question - are you flashing the correct boot.img for the ROM you want.
ie for Cyanogenmod you need to flash the exact boot.img from that ROM.
Thanks for your answer.
At the moment I am running clockwork as recovery. I've tried to flash trickdroid and I used these instructions at
trickdroid.org for the international one s. But after flashing the boot.img and doing fastboot erase cache
nothing happens and I couldn't load anything anymore.
PS: My phone has a S4 processor (with 1,5GHz is this right?)
swtcw said:
Thanks for your answer.
At the moment I am running clockwork as recovery. I've tried to flash trickdroid and I used these instructions at
trickdroid.org for the international one s. But after flashing the boot.img and doing fastboot erase cache
nothing happens and I couldn't load anything anymore.
PS: My phone has a S4 processor (with 1,5GHz is this right?)
Click to expand...
Click to collapse
Yep, S4 is 1.5GHz
Sent from my HTC One S using Tapatalk 2
Can I reflash my originial stock rom? I have no backup.
I found an instruction at usp-forum.de/htc-one-s-root-flash-hack/87944-how-to-htc-one-s-stock-rom-wiederherstellen.html - it worked fine,
I flashed the stock_recovery.img with "fastboot flash recovery stock_recovery.img" and the I did "fastboot oem lock".
I also downloaded a installer exe with the RUU - it found my device and started to install, but it stopped sometimes and said, that
I have a wrong installer or RUU (something like signature error 132). Where and how can I find the right RUU?
I made the mistake of running a cm10 rom on my htc one s that didnt work on i so now i can only access TWRP and my phones bootloader from my One S so I'm trying to find my phone's stock RUU but there are so many out there! Can anyone tell me how to find one? Or another way to get into my phone using another ROM? My phone is rooted with Twrp recovery, Unlocked bootloader obviously and S-on. All my phone does is show the htc bootscreen and then go black but I can still enter bootloader and the TWRP menu and I can connect it to my computer fine. Any help would be VERY greatly appreciated!
IsaacDroid said:
I made the mistake of running a cm10 rom on my htc one s that didnt work on i so now i can only access TWRP and my phones bootloader from my One S so I'm trying to find my phone's stock RUU but there are so many out there! Can anyone tell me how to find one? Or another way to get into my phone using another ROM? My phone is rooted with Twrp recovery, Unlocked bootloader obviously and S-on. All my phone does is show the htc bootscreen and then go black but I can still enter bootloader and the TWRP menu and I can connect it to my computer fine. Any help would be VERY greatly appreciated!
Click to expand...
Click to collapse
Don't give up. I had the same issue with my telus One S. I think I fixed it by falshing boot image separately and after flashing CM10. I believe this happens if the phone is rooted but is in S-ON mode, whatever that means. I remember it really gave me a hard time and as I was going to give up i flashed the boot image and it worked. You have to do it through a command window on your PC. There should be an all-in-one tool in this forum somewhere to simplify the steps a bit. Good luck!
Thanks!
new_convert said:
Don't give up. I had the same issue with my telus One S. I think I fixed it by falshing boot image separately and after flashing CM10. I believe this happens if the phone is rooted but is in S-ON mode, whatever that means. I remember it really gave me a hard time and as I was going to give up i flashed the boot image and it worked. You have to do it through a command window on your PC. There should be an all-in-one tool in this forum somewhere to simplify the steps a bit. Good luck!
Click to expand...
Click to collapse
Thank you very much! Could you tell me what boot image you flashed and maybe how to get it and also how you flashed it? Thank you so much for the response!
IsaacDroid said:
Thank you very much! Could you tell me what boot image you flashed and maybe how to get it and also how you flashed it? Thank you so much for the response!
Click to expand...
Click to collapse
It is in the zip file that you download to flash, i.e. your new ROM. So when you download CM10, open the zip file. BOOT.IMG will be there. Extract it and flash it to your phone. I believe everything was in One_S_All-In-One_Kit_v3.4. Look it up in the forum and it has all the tools you need. I admit that it was a pain and nothing was straight forward. I always root my android devices and install new ROMs. But HTC One S was particularly tricky.
Good luck!
Hello there! Fellow HTC One S user here! Don't give up on CM10! It's way better than stock on your one S! What you need to remember is that HBoot versions higher than 1.09 can't flash the boot while installing the rom, so you need to do that after flashing a rom! The boot for your version is going to be included in the rom's zip file. Look for the boot.img file located in the zip file's root. Every rom should have this. Place this boot.img file in the kernel folder of the One S all in one kit and flash it. You should be good to after that!
Don't hesitate to ask for more help if needed!
Simon
seoman81 said:
Hello there! Fellow HTC One S user here! Don't give up on CM10! It's way better than stock on your one S! What you need to remember is that HBoot versions higher than 1.09 can't flash the boot while installing the rom, so you need to do that after flashing a rom! The boot for your version is going to be included in the rom's zip file. Look for the boot.img file located in the zip file's root. Every rom should have this. Place this boot.img file in the kernel folder of the One S all in one kit and flash it. You should be good to after that!
Don't hesitate to ask for more help if needed!
Simon
Click to expand...
Click to collapse
When I try to flash a ROM through fastboot it sends it fine but then it says: FAILED (remote: not allowed), and I tried pushing the ROM with adb but when I tried to put it on the sdcard, it said permission denied, do you know why? I am S-ON, would that be a problem? Thanks!
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Hkyx said:
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Click to expand...
Click to collapse
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
astar26 said:
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
Click to expand...
Click to collapse
Hi,
It's not possible to use 4ext, because the phone doesn't boot. he's stop at the boot loader.
I've try with adb for mac but I think I don't do the good command to flash by adb the kernel
ADB does not work, you have to use fastboot! Just follow the instructions by astar26. Connect your phone to your PC/mac and type "fastboot reboot-bootloader" and then "fastboot flash boot boot.img"
Regards
Gesendet von meinem HTC Sensation mit Tapatalk 4
astar26 said:
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
Click to expand...
Click to collapse
Hi, I'm trying to flash a Cyanogenmod ROM for a friend on his HTC Sensation Z710e (rooted, bootloader unlocked) - my own phone is an Xperia Ray so I'm not too familiar with the process. Do I need to flash the Kernel before I flash the ROM? What's the best way to do it? If it's a matter of following the process you outlined above then I'm afraid I can't really follow it - I really need an idiot-proof 'how-to' guide I'm afraid, like I said, I'm a total noob when it comes to the HTC Sensation.
Hope you can help.
seamo123 said:
Hi, I'm trying to flash a Cyanogenmod ROM for a friend on his HTC Sensation Z710e (rooted, bootloader unlocked) - my own phone is am Xperia Ray so I'm not too familiar with the process. Do I need to flash the Kernel before I flash the ROM? What's the best way to do it? If it's a matter of following the process you outlined above then I'm afraid I can't really follow it - I really need an idiot-proof 'how-to' guide I'm afraid, like I said, I'm a total noob when it comes to the HTC Sensation.
Hope you can help.
Click to expand...
Click to collapse
Usually the ROM is flashed before the kernel, this is what I did
Babyhustle said:
Usually the ROM is flashed before the kernel, this is what I did
Click to expand...
Click to collapse
I have no idea how to flash a kernel on the HTC - that's my main problem
seamo123 said:
I have no idea how to flash a kernel on the HTC - that's my main problem
Click to expand...
Click to collapse
astar26 explained how it works. If the sensation of your friend has 4ext recovery use smartflash, if twrp use htc dumlock then you don't need to flash the kernel seperately.
Hkyx said:
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Click to expand...
Click to collapse
To flash a ROM on the Sensation:
Go to recovery
(Wipe. Then) flash the .zip of the ROM
That's it. There is, however, a catch for S-ON devices. HTC hasn't allowed flashing of /boot from recovery. This means that, for S-ON devices, the kernel cannot be flashed.
The best way around this is to use 4ext recovery. It has a option called Smartflash. That will flash your kernel even if you're S-ON.
(Some roms, like ViperS 3.1.x require an additional kernel flasher as SmartFlash doesn't work there).
The other way is to manually flash the boot image (kernel). Go to fastboot USB (this is NOT ADB), and execute:
Code:
fastboot flash boot boot.img
The boot.img is your new boot image.
Thanks for the reply!
We've already tried flashing the ROM as normal [using ROM Manager] but it doesn't work.
1. How do I know the device is 'S-on?' or not? Can it be changed? What's 'S-on' anyway?
2. Do you have a link handy for that recovery system you mentioned that allows flashing of kernels?
3. I haven't a clue how to manually flash the boot image - with my Xperia Ray I just use the Sony flash tool and fastboot. Can you give me an idiot's guide to doing this?
Far_SighT said:
To flash a ROM on the Sensation:
Go to recovery
(Wipe. Then) flash the .zip of the ROM
That's it. There is, however, a catch for S-ON devices. HTC hasn't allowed flashing of /boot from recovery. This means that, for S-ON devices, the kernel cannot be flashed.
The best way around this is to use 4ext recovery. It has a option called Smartflash. That will flash your kernel even if you're S-ON.
(Some roms, like ViperS 3.1.x require an additional kernel flasher as SmartFlash doesn't work there).
The other way is to manually flash the boot image (kernel). Go to fastboot USB (this is NOT ADB), and execute:
Code:
fastboot flash boot boot.img
The boot.img is your new boot image.
Click to expand...
Click to collapse
seamo123 said:
Thanks for the reply!
We've already tried flashing the ROM as normal [using ROM Manager] but it doesn't work.
1. How do I know the device is 'S-on?' or not? Can it be changed? What's 'S-on' anyway?
2. Do you have a link handy for that recovery system you mentioned that allows flashing of kernels?
3. I haven't a clue how to manually flash the boot image - with my Xperia Ray I just use the Sony flash tool and fastboot. Can you give me an idiot's guide to doing this?
Click to expand...
Click to collapse
Ah, I see:
Power off and pull out the battery. Press Power + Vol down. Once the bootloader screen comes up it'll either say S-ON or S-OFF.
For flashing ROMs S-ON use this (also includes 4ext recovery). Read about S-ON here.
Just use smartflash (see link in 1). For the special cases I mentioned in previous post (no smartflash), just see the ROM's thread for S-ON flashing.
Note that if you want just want to flash ROMs the above method is good. For S-OFF, either use this, in case you followed above steps, or use this, in case you want to S-OFF first. S-OFF is not needed for flashing ROMs.
htc sensation z710e wifi problem
Hello friends!
Two months I have a problem with my HTC SENSATION! The problem is due to wifi,I read many forums about this problem, I tried many solutions, but without success! I assumed that the problem is due to "wifi country code". I tried this solution "WiFix Manager", but did not help.
I tried this option http://forum.xda-developers.com/showthread.php?t=1469428,
because my phone is unlocked with HTCdev, back to factory rom 2.3.3 hboot 1.17.11 to be able to achieve S-OFF method revolutionary s-off.
I did everything, but after a while the problem still occurs. The only way to fix it is by re-install the Rom again.Most often breaks when I restart phone while is connected to the wifi network,when my phone starts, this wifi error appears.I can not write scripts or fix them, so I can not do this option: http://forum.xda-developers.com/showthread.php?t=2368501 . My phone is from England, Orange UK is the operator of which is purchased,I do not know if there is any difference!? And now my phone is rooted, revolutionary s-off, got super CID, 4ext recovery....
What else do I need to have no more this wifi problem?
I'm not very good at Development or haking, so if someone can explain to me what to do to solve my problem, I would appreciate it!
I just want to install "Revelation 1.0.3" and only use it! I am from Bulgaria by the way.
VS23BG said:
Hello friends!
Two months I have a problem with my HTC SENSATION! The problem is due to wifi,I read many forums about this problem, I tried many solutions, but without success! I assumed that the problem is due to "wifi country code". I tried this solution "WiFix Manager", but did not help.
I tried this option http://forum.xda-developers.com/showthread.php?t=1469428,
because my phone is unlocked with HTCdev, back to factory rom 2.3.3 hboot 1.17.11 to be able to achieve S-OFF method revolutionary s-off.
I did everything, but after a while the problem still occurs. The only way to fix it is by re-install the Rom again.Most often breaks when I restart phone while is connected to the wifi network,when my phone starts, this wifi error appears.I can not write scripts or fix them, so I can not do this option: http://forum.xda-developers.com/showthread.php?t=2368501 . My phone is from England, Orange UK is the operator of which is purchased,I do not know if there is any difference!? And now my phone is rooted, revolutionary s-off, got super CID, 4ext recovery....
What else do I need to have no more this wifi problem?
I'm not very good at Development or haking, so if someone can explain to me what to do to solve my problem, I would appreciate it!
I just want to install "Revelation 1.0.3" and only use it! I am from Bulgaria by the way.
Click to expand...
Click to collapse
flash the boot.img of your current rom and see if wifi works
rzr86 said:
flash the boot.img of your current rom and see if wifi works
Click to expand...
Click to collapse
And I tried, I installed program KGS Utility,did not help! I tried with the "ADB" command to flash the boot.img, just flashed it, but it did not help!
And now, whenever my wifi give me error, I installed a new Rom! So I solved the problem, but this solution is temporary. The problem manifests itself sooner or later. End i chenge Rom again, there is a good side, will test all Roms which is on this site!
Thank you for your attention!
VS23BG said:
And I tried, I installed program KGS Utility,did not help! I tried with the "ADB" command to flash the boot.img, just flashed it, but it did not help!
And now, whenever my wifi give me error, I installed a new Rom! So I solved the problem, but this solution is temporary. The problem manifests itself sooner or later. End i chenge Rom again, there is a good side, will test all Roms which is on this site!
Thank you for your attention!
Click to expand...
Click to collapse
May be a firmware problem. Do a Ruu and see what happens.
Happy to help.
Far_SighT said:
May be a firmware problem. Do a Ruu and see what happens.
Happy to help.
Click to expand...
Click to collapse
RUU? Recommend me to back factory Rom using Ruu.exe? Already done it! Return factory Rom 2.3.3 HBOOT 1.17.11,to achieve revolutionary s-off. :good:
VS23BG said:
RUU? Recommend me to back factory Rom using Ruu.exe? Already done it! Return factory Rom 2.3.3 HBOOT 1.17.11,to achieve revolutionary s-off. :good:
Click to expand...
Click to collapse
lift up gently the antenna which is responsible for wifi in the back cover
I think I finally found the solution to the wifi problem!
The solution is in this post:
http://forum.xda-developers.com/showpost.php?p=23554125&postcount=1804
Now I use Android Revolution HD 7.3,sometimes the problem occurs again, but now I have a solution!
Just repeat the procedure described in the post and wifi working again.
When you delete a file "wpa_supplicant.conf", I have to re-enter all the router's password which I linked, but this is not such a big problem!
Hiya. Any help appreciated here, Got hold of a Rogers One X (evita)
Heres where I am at right now:
I unlocked the bootloader and attempted to flash CM11 (Got an error regarding update package) *I made no backup- Noob, I know.*
Now, at the very most all I can get into is CWM/TWRP (I can flash both of these without issue using fastboot)
I have attempted to re-lock the bootloader (which says relocked) but I have tried the 2 rogers RUU files I managed to find and both fail with an error 115 and leave me on the htc logo, and boot to bootloader only.
I tried to flash some custom roms, some seem to flash ok but just boot-loop.
I am not SuperCID, and the phone is S-ON.
Hboot-2.14.0000
Radio-0.23a.32.09.29
Nov 26, 2012
I cannot figure what to do next. I dont care what goes on the phone as long as i can get it working. Its been a long time since I messed with android, I only bought this phone for this reason lol, but I made the mistake of staying up too late and probably skipping half of the tutorials i was following.
Any help appreciated.
:laugh:
What version of TWRP are you using? Why did you relock the bootloader? You should unlock that again. Did you flash the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP? You need to do this because you're s-on. You should read the Evita FAQ thread in my signature, as well as the How-To Guide For Beginners thread.
Sent from my Evita
timmaaa said:
What version of TWRP are you using? Why did you relock the bootloader? You should unlock that again. Did you flash the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP? You need to do this because you're s-on. You should read the Evita FAQ thread in my signature, as well as the How-To Guide For Beginners thread.
Sent from my Evita
Click to expand...
Click to collapse
Wow, timmaaa, thanks for the superfast answer chap!
So, unlock the bootloader, flash the Rom (CM11), then the Boot.img extracted from the rom via fastboot?
Sounds like a plan. I will try that now. I think to be honest, I came home last night and ended up following a bit of one tut, a bit of another, and never really read properly. Call it friday evening alcohol induced noobness syndrome.
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
timmaaa said:
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
Thank you. The boot.img thing got me a bit further so far. I will get that version of TWRP installed and try the CM11 again, as i think thats where I want to be at. It should be as simple as CM11 flash, Boot.img flash, then Gapps and im done, right?
Perform a full wipe (cache/dalvik cache/factory reset/system), flash CM, flash gapps, flash boot.img, reboot into ROM.
Sent from my Evita
timmaaa said:
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
Ok one last question Timmaaa, I have installed that TWRP, flashed CM11, also Gapps and the boot.img , and now I just get the rom bootlogo (spinning cyanogen etc) and nothing, it just sits there. Is there anything else that may need to be done? If theres not anything obvious, ill go read some more!
Thanks for the help so far!
scibot said:
Ok one last question Timmaaa, I have installed that TWRP, flashed CM11, also Gapps and the boot.img , and now I just get the rom bootlogo (spinning cyanogen etc) and nothing, it just sits there. Is there anything else that may need to be done? If theres not anything obvious, ill go read some more!
Thanks for the help so far!
Click to expand...
Click to collapse
What is the filename of the ROM zip you flashed? Did you check the md5 of the file after you downloaded it? Are you sure the flashing of the boot.img was successful?
Timmaaa, it seems it just took ages. I went downstairs for some juice, came back up and there it was, the setup screen! Beautiful.
Thanks for the help, it seems its not the technical i need to brush up on, but my paying attention and reading - lol!
Thanks again man! :good:
I have an AT&T HTC One x. Its ***Tampered*** ***Unlocked*** HBOOT 1 .09. 0000 S-ON
I had been running an older version of TWRP, and decided I was going to clear my phone and do a fresh start. I know, I know, I should have made a backup, but I felt pretty confident in what I was doing, and was in too much of a hurry to rationalize this.
I wiped both the OS and previous version of TWRP in order to update to the new ones. While in fastboot I flashed CLEANrom and the new version of TWRP, and my administrative command prompt confirmed that they were installed successfully. Even cleared the cache afterwards. Now is the difficult part. I've researched, and researched, and cannot find a solution for this problem. I keep having a Boot Loop.... I'm stumped guys... I need some sort of help, be it technical, or something to drink lol
Previous ROM was CM 10, with TWRP and PA GAPPS :good:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
timmaaa said:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
Click to expand...
Click to collapse
I don't see anything in your FAQ that I haven't already tried unfortunately.....
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
It's the newest version of TWRP that is out, and yes, I flashed it via Fastboot, and it says successful on both the recovery install and ROM install.
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
1332858898
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.7. And yes, I have flashed about 4 Roms all succeeded according to fastboot and still getting the boot sequence.:good:
Yes I have extracted the boot.img
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
Click to expand...
Click to collapse
yes the boot.img file was extracted. I get a confirmation that it was successful when I flash it on fastboot
Exactly which ROMs have you tried to flash?
Sent from my Evita
timmaaa said:
Exactly which ROMs have you tried to flash?
Sent from my Evita
Click to expand...
Click to collapse
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
outcold32 said:
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
Click to expand...
Click to collapse
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
exad said:
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
Click to expand...
Click to collapse
If you would have read the thread, you would have noticed, that I am in bootloop, therefor I cannot access the recovery. And I have to have access to the ROM on my phone in order to flash anything via TWRP so this is moot. My question isn't how to flash roms, it's why am I getting a loop when I am successful on a clean partition and clean flash of both the recovery and ROM? And to me, fastboot is way easier than TWRP. I guess I could get a UART and try to debug the sequence myself, but I have more important things to do than that. I was posting to see if anyone had any similar problems. And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place. I ran the RUU after I re-locked the bootloader, and I'm at least out of the loop. I'm just going get to a more stable version so that this process will be more streamline when I re do my unlock and stuff.
So I guess the only solution at this point I have for any problem like this is to use the proper RUU. I tried a couple of times with no success, and it seemed the charm was to re lock the bootloader ( Fastboot oem lock) in order to properly and successfully get the RUU to work.:good:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
exad said:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
Click to expand...
Click to collapse
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Okie dokie. No point in arguing. You're right. I'm wrong. Glad it's all working now.
Sent from my One XL using xda app-developers app
outcold32 said:
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Click to expand...
Click to collapse
Exad is right in saying that the reason you're having problems is because you're attempting to flash ROMs with fastboot. That isn't how it's done. The correct way is to flash your ROM with recovery. You're barking up the wrong tree, not only that but you're arguing with experienced people who are only attempting to help get you out of the mess that you've gotten yourself into. You came here for advice, but there's no point in asking for advice if you're just going to argue and dismiss what you're being told to do.
You said you can't access your ROM so you can't flash anything, that makes absolutely no sense, which leads me to believe you don't really know what you're doing. Get out of the mindset that you need to use fastboot, it's wrong. You're dealing with people who have extensive and intimate knowledge of this device, trust us, we know what we're talking about.
Exactly why can't you access recovery? If you can issue fastboot commands that means you can access your bootloader, if you can access your bootloader that means you can use your volume keys to scroll through the options and the power button to select recovery. What happens when you do that? Exactly which recovery have you flashed to your device? I need to the full filename of the recovery that you've flashed.
Sent from my Evita
outcold32 said:
And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place.
Click to expand...
Click to collapse
S-on is a downright dangerous place to be, if the phone is also SuperCID (which is very likely, since its the AT&T variant). exad is right in recommending s-ff, as he is about a good many things.