Related
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
chewbz said:
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
Click to expand...
Click to collapse
I can handle the mac part if you can show me which files to flash in which order to make my phone work again.
Okay this will take your phone back to stock. Download the grj22 image files. When you open it up it should have like 4 or 5 img files. After that open up cmd and type in the commands buglesspete has in his first post. It should be under "return to stock" or sometime like that.
Sent from my Nexus S 4G using XDA App
XikkeN said:
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
Click to expand...
Click to collapse
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
rentaric said:
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
Click to expand...
Click to collapse
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
XikkeN said:
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
Click to expand...
Click to collapse
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
rentaric said:
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
Click to expand...
Click to collapse
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
chewbz said:
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Borky_16 said:
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
your assuming that the devs took the time to make sure to include that
First of all, I heard that Google had an API error in 4.1.2 that causes the mobile data or internet data to consume twice as fast. Which means you use 2x more data compared to normal. Is this true? and has it been fixed in CM10?
Secondly, if I am going to flash a new ROM, do I have to flash the ROM first then flash the boot.img separately? Or just flash everything together in the recovery? When should I flash the boot.img separately? I am kinda new to this new phones I so don't know about much these things.
Sent from my One X using xda premium
You only need to flash boot.img separately if you are on hboot 1.14 or higher. Otherwise, it will just flash in TWRP automatically when you flash the ROM.
Don't know about your other questions.
That's "tons" of questions??? That's just 2!
CalamitySir said:
First of all, I heard that Google had an API error in 4.1.2 that causes the mobile data or internet data to consume twice as fast. Which means you use 2x more data compared to normal. Is this true? and has it been fixed in CM10?
Secondly, if I am going to flash a new ROM, do I have to flash the ROM first then flash the boot.img separately? Or just flash everything together in the recovery? When should I flash the boot.img separately? I am kinda new to this new phones I so don't know about much these things.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Where did you hear that? Seems like bs because your carrier measures the amount of data on their servers
If you have hboot 1.14 then you have to flash the boot.IMG separately after you flash the ROM
Otherwise you flash everything in recovery all at once
Sent from my One X using Tapatalk 2
superchilpil said:
Where did you hear that? Seems like bs because your carrier measures the amount of data on their servers
If you have hboot 1.14 then you have to flash the boot.IMG separately after you flash the ROM
Otherwise you flash everything in recovery all at once
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Then how do I downgrade the hboot?
Another question is that when I tried to flash 4.1.1 ROMs when coming from 4.1.2 Roms, it stuck in the boot logo.
Sent from my One X using xda premium
You'll pretty much have to flash boot.IMG seperate every time... Or it will boot loop.
Sent from my One X using Tapatalk 2
InflatedTitan said:
You'll pretty much have to flash boot.IMG seperate every time... Or it will boot loop.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok now the question is, do i flash the boot.img first then flash the rom or flsah the rom first then the boot.img??!! The latter method was reccomendded by devs in the HOX section and the former one was used in ours?
I tried ROM then kernel on my cousins phone... Bootlooped.. Started fresh, flashed kernel then ROM and works perfectly every time
Sent from my One X using Tapatalk 2
Another question is the ss below, the total amount of data doesn't add up correctly....is this a bug or was it already predetermined like this?
Sent from my One X using xda premium
CalamitySir said:
Then how do I downgrade the hboot?
Click to expand...
Click to collapse
Tool here (but requires a Linux machine): http://forum.xda-developers.com/showthread.php?t=1982442
The total amount of data doesn't add up. Is this a bug in CM10?
Sent from my One X using xda premium
I'm still not seeing the "tons" of questions.
iElvis said:
I'm still not seeing the "tons" of questions.
Click to expand...
Click to collapse
maybe u cna help me answer the question regarding the data in page one, i have 2 screenshots for that.
Another question is how do i flash the b6 kernel for cm10? flash like normal in twrp or flash the boot.img? i am messed up!
CalamitySir said:
maybe u cna help me answer the question regarding the data in page one, i have 2 screenshots for that.
Another question is how do i flash the b6 kernel for cm10? flash like normal in twrp or flash the boot.img? i am messed up!
Click to expand...
Click to collapse
I have heard only that there may be a bug in CM that makes your data usage appear to be worse. That's all I know.
I have never used CM so I can't help with the kernel. If you're on 1.14 you have to flash it separately in fastboot.
iElvis said:
I have heard only that there may be a bug in CM that makes your data usage appear to be worse. That's all I know.
I have never used CM so I can't help with the kernel. If you're on 1.14 you have to flash it separately in fastboot.
Click to expand...
Click to collapse
ok. does fastboot makes me unable to downgrade the android version, i tried to flash 4.1.1 from 4.1.2, i did it separately and it didnt work, stuck at bootloop... any idea?
Well you have to flash the boot.img from the 4.1.1 rom. Maybe try flashing the older gapps http://goo.im/gapps/gapps-jb-20120726-signed.zip I would also wipe cache, dalvik and system. Use flashimagegui for kernel flashing so you dont need to use fastboot and a pc http://forum.xda-developers.com/showthread.php?t=1963896
Here's what I do and I have flashed every ROM in this section without a single boot loop.
Flash boot IMG in fast boot
Reboot to recovery
Wipe dalvik and cache
Wipe system
Factory reset
Flash rom and gapps or just ROM (sense)
Reboot system
Do I do steps I don't need? Perhaps. But the results are hard to argue
Sent from my One X using xda app-developers app
smolck said:
Here's what I do and I have flashed every ROM in this section without a single boot loop.
Flash boot IMG in fast boot
Reboot to recovery
Wipe dalvik and cache
Wipe system
Factory reset
Flash rom and gapps or just ROM (sense)
Reboot system
Do I do steps I don't need? Perhaps. But the results are hard to argue
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
do i have to follow this sequence to wipe everytime?
Usually if its same rom u dont need to factory reset[wipe data] but ive been wiping system alot each time though.
Hi everyone.
I have a TMOUS HTC One S (S4, mentioning because of some crazy people). I tried to install CyanogenMod 10 on it, but it fails. It just starts the splash screen.
Normally, I would flash an RUU, but now, the CID is HTC__001, and the Modelid PJ4011000. I am not allowed to install both European ROM and the stock TMOUS one. Oh, and to make things worse, it is relocked. Can someone help me, please???
mr_verystock
Unlock it, install custom recovery if you dont have it already, reflash the rom, fastboot flash the boot.img and it should start just fine.
Remember to wipe /system/, /data/, cache and dalvik-cache. Edit: Before you flash the rom, obviously.
Goatshocker said:
Unlock it, install custom recovery if you dont have it already, reflash the rom, fastboot flash the boot.img and it should start just fine.
Remember to wipe /system/, /data/, cache and dalvik-cache. Edit: Before you flash the rom, obviously.
Click to expand...
Click to collapse
Seems no one knows how to read any more... I'm pretty sure all ROM pages say flash boot.IMG... All these ROMs on this site flash and boot just fine if you follow directions...
Sent from my HTC One S using xda premium
$droyd$ said:
Seems no one knows how to read any more... I'm pretty sure all ROM pages say flash boot.IMG... All these ROMs on this site flash and boot just fine if you follow directions...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Very true... I think Ive written around 400 posts in the S section now, and it feels like at least 350 of them contains "fastboot flash the boot.img" lol
Thank you all you guy's help!!! Yes, I did it by watching a video online(noob!!!), and followed your hints. Thanks!!! 10 thank to you.
mr_verystock said:
Thanks, but it fails to wipe dalvik-cache(remote: not allowed). Please help once more.
Click to expand...
Click to collapse
Re install twrp recovery.IMG with fast boot. Flash boot.IMG with fast boot.. Then wipe everything including SD card... Mount phone to PC with twrp and copy ROM to phone.. Flash ROM and wipe both caches again...
Sent from my HTC One S using xda premium
Hi all, I just wanted to start by saying that xda is the shizz and has helped me through thick n thin. Anywho, I have a custom Rom and am trying to go to a different Rom. ViperX to be specific. I've tried before, but with little success. Extracted boot.img, fastboot flash boot boot.img in the command, put the Rom on my sd and installed via TWRP. Problem is, is that it never boots, only the HTC boot screen with the red writing. Anyone have any suggestions on what I need to do? I'm still S-on, but from what I understand, that doesn't matter if you fastboot the boot.img via command prompt. I also have Hboot 1.14.
Thanks.
Chuckles850 said:
Hi all, I just wanted to start by saying that xda is the shizz and has helped me through thick n thin. Anywho, I have a custom Rom and am trying to go to a different Rom. ViperX to be specific. I've tried before, but with little success. Extracted boot.img, fastboot flash boot boot.img in the command, put the Rom on my sd and installed via TWRP. Problem is, is that it never boots, only the HTC boot screen with the red writing. Anyone have any suggestions on what I need to do? I'm still S-on, but from what I understand, that doesn't matter if you fastboot the boot.img via command prompt. I also have Hboot 1.14.
Thanks.
Click to expand...
Click to collapse
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Will do thank you
Sent from my HTC One XL using xda app-developers app
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Apparently there's a TWRP 2.4.4 out, would it hurt me to flash the latest version?
Sent from my HTC One XL using xda app-developers app
Yes. It would hurt anyone with a one xl as 2.4 does not wipe our device properly. I tested 2.4.4 myself.
Sent from my HTC One X using xda app-developers app
ok, well I found another problem you might be able to help me with, but I'll shoot it to you anyway. I just found out my phone was originally a One X when I got it from the ATT store. Now apparently after I flashed the Rom I got (odex-JB-Sense4+.zip), It's saying my phone is an XL. Seems to me I have a whole new set of issues. Did I flash the wrong Rom? I though I did enough research to find a compatible Rom. How do I find out for sure what's going on with my phone and how to fix it properly?
Chuckles850 said:
ok, well I found another problem you might be able to help me with, but I'll shoot it to you anyway. I just found out my phone was originally a One X when I got it from the ATT store. Now apparently after I flashed the Rom I got (odex-JB-Sense4+.zip), It's saying my phone is an XL. Seems to me I have a whole new set of issues. Did I flash the wrong Rom? I though I did enough research to find a compatible Rom. How do I find out for sure what's going on with my phone and how to fix it properly?
Click to expand...
Click to collapse
No problem you have the correct ROM, if you had flashed wrong one it would have not worked correctly. Depending on the ROM sometimes it will show XL instead of X.
One xl is the proper model name, code named Evita, not to be confused with the real HTC One X international quad core version.
So in other words, nothing is wrong. This is normal. If you flashed the wrong rom you would know as you would now have a paperweight
Sent from my HTC One X using xda app-developers app
ok cool, I was kinda confused there for a sec lol. Ok, now for the TWRP. I'm assuming you were referring to 2.3.0.0? just because there is a 2.3.0.0, 2.3.1.0, 2.3.3.0, and a 2.3.3.1. I just want to make sure I have the correct one for Hboot 1.14
Doesn't matter which one. I use 2.3.3.1 myself.
Sent from my HTC One X using xda app-developers app
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
ok, downloading it now. I'll keep you updated.
bkmo said:
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ah I didn't catch that in the first post! Good eye.
bkmo said:
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
ok, I'll keep that in mind. Thank you!!
exad said:
Ah I didn't catch that in the first post! Good eye.
Click to expand...
Click to collapse
it's ok bud, just downloaded and installed TWRP 2.3.3.1 successfully, now i'm downloading ViperXL and hope everything comes out ok
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Should I need to be thinking about Kernels of any sort?
Chuckles850 said:
Should I need to be thinking about Kernels of any sort?
Click to expand...
Click to collapse
Yeah.......give bulletproof 1.1 a shot. Gonna give you better performance and battery, plus a no brainer install and its stable.
Sent from my Transformer TF101 using xda premium
bkmo said:
Yeah.......give bulletproof 1.1 a shot. Gonna give you better performance and battery, plus a no brainer install and its stable.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Ok cool. Any links?
Sent from my HTC One X using xda app-developers app
It's in Android development page. if not the first page then the second.
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
Click to expand...
Click to collapse
Except for ViperXL (and old builds of CleanROM, which may also happen with future builds if/when scrosler gets AROMA back in there) which is intended to flash the boot.img in AROMA.
Although, it doesn't always work for some folks, so they have had to flash boot.img manually. So yes, if at all in doubt (and you have a boot loop) flash boot.img manually.
I currently can't use my usb port to receive data, so adb isn't an option.
I'm looking to flash the new PAC rom, and need to update my TWRP recovery from 2.6.0.0 to 2.7.0.8. I'm using HBOOT 2.19 if that makes a difference?
I want to use Flashify to do this as its my only option without using adb that I can see.
Has anyone here had experience using this? If it doesn't work I don't have any other way of restoring my recovery and my phone will dead weight.
Also will updating my recovery wipe the sdcard? I hope not as I need the rom file to survive to be able to bring my phone back to life, as sideload won't work for me.
Thank you for any help received on this.
Sent from my GT-I9000 using xda app-developers app
i could be wrong mate but I'm sure I've read you can get ADB to work over WiFi, think you have to enable it in developer options.. surely there is a tutorial kicking around someplace on XDA.
flashing new recovery.img shouldnt wipe. only Unlocking the bootloader, super wipe, flashing a ruu, factory reset - they all wipe the phone
ill have a look about and get back to you
**UPDATE**
Found this amongst many other tutorials, not sure if it will work but worth a try
http://forum.xda-developers.com/showthread.php?t=2570432 apparantly he has updated it to http://forum.xda-developers.com/showthread.php?t=2707556
there is also a twrp manager app (by jmz) on playstore, i think you can flash a new recovery direct fom the app ????
I had problems flashing a boot.img via flashify. Flashed successfully but got problems later. flashed via fastboot and everything was fine.
Many thanks for the input. Will try this when I get my phone back from HTC.
@Braddison
Can you flash recoveries thru the android os over adb? Thought you had to do that thru hboot.
@theodorius123
What exactly did you try to flash with Flashify?
Sent from my GT-I9000 using Xparent Red Tapatalk 2
no idea what it was exactly, only know that it was a boot.img - as i wrote before
Not sure, but check out jmz app on play store.... Twrp manager I think you can do it from that or try goo manager, also on play store. i'm sure you can flash new recoveries directly from within these apps?
Good luck
twrp = https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
goomanager = https://play.google.com/store/apps/details?id=com.s0up.goomanager
again not sure as i haven't tried them myself
Or this one: http://forum.xda-developers.com/showthread.php?t=2730305
Ah! Forgot about the aroma recovery installer. That's a great option. Then it should just be a matter of flashing rom. Are you s-off? If so shouldn't need to flash boot. Img afterward
I am s-off. Think the aroma installer is my best bet. But I may not bother just because its to much of a risk without being able to use fastboot to restore things in case something goes wrong...
Bloody HTC.
Sent from my GT-I9000 using Xparent Red Tapatalk 2