Database Info

Unable to flash ROMs

Hi guys!
Yesterday I successfully rooted my NS (it is a European SLCD model with stock 2.3.6 on it) following the newest guide on nexusshacks.com. So I ended up with TWRP recovery.
Then I thought the easiest to install CM is via Rom Manager. Therefore I had to change recovery for CWM. (I flashed the latest one.)
And here comes my question: why am I unable to flash CM?
First I tried it in Rom Manager, after wiping everything and rebooting system nothing happens, except for a big yellow exclamation mark.
Then I downloaded the proper CM myself and I tried to do the whole process manually in recovery menu. After wiping and choosing update from SD card I get a message like the process is aborted.
I also tried with an older CWM and with other ROM.
Any suggestions?
Thanks a lot
Sent from my Nexus S using XDA App

Boot into bootloader, then flash recovery via fastboot.
fastboot flash recovery recovery.img

stock firmware will rewrite your recovery after each boot. flash recovery then flash this right after.

Follow what SEAN SAys..............He is a Master in all these , and he helped me with details to root, flash cwm, make it sticky and flash custom ROMS.
It took me 5 minutes to do all those , and Now I am switching Roms like I switch my underwears every day twice.
I must say, Sean has the best possible way which is like a finger click.

Bootloop problem, totally perplexed

Problem: After installing CWM, the phone won't boot fully. It goes to the HTC screen (with some new red text about this being a development-only build) and then reboots to the same screen over and over.
What I've done based on what I've read here:
Cleared the caches in fastboot and rebooted.
Run the unlock token script again.
Installed TWRP, wiped everything.
Attempted to flash CM9 through TWRP (fails).
Attempted to install Scott's Roms 1.85 ROM throught TWRP (failed).
Reinstalled CWM to try to flash Scott's 1.85, but CWM will not go into recovery mode (just goes to the HTC screen and starts boot loop again).
Attempted to install CM9 and Scott's 1.85 through flashboot, no luck because of missing text files (am I using the wrong package?).
Factory reset just takes me to TWRP, and when I try to factory reset from there it goes back into bootloop.
What does work:
I can get to Fastboot on phone.
With TWRP installed, I can into TWRP recovery.
Does anyone have any thoughts on this?
Thanks.

makanai said:
Problem: After installing CWM, the phone won't boot fully. It goes to the HTC screen (with some new red text about this being a development-only build) and then reboots to the same screen over and over.
What I've done based on what I've read here:
Cleared the caches in fastboot and rebooted.
Run the unlock token script again.
Installed TWRP, wiped everything.
Attempted to flash CM9 through TWRP (fails).
Attempted to install Scott's Roms 1.85 ROM throught TWRP (failed).
Reinstalled CWM to try to flash Scott's 1.85, but CWM will not go into recovery mode (just goes to the HTC screen and starts boot loop again).
Attempted to install CM9 and Scott's 1.85 through flashboot, no luck because of missing text files (am I using the wrong package?).
Factory reset just takes me to TWRP, and when I try to factory reset from there it goes back into bootloop.
What does work:
I can get to Fastboot on phone.
With TWRP installed, I can into TWRP recovery.
Does anyone have any thoughts on this?
Thanks.
Click to expand...
Click to collapse
Uhhhhh...try to relock your bootloader (fastboot oem lock) and run an RUU. You'll go back to stock. Then follow these steps:
1. Re-unlock your bootloader using the same unlock token you used before
2. Flash TWRP from fastboot (or a one-click)
3. Reboot into TWRP
4. Mount storage and put whatever rom you want into whatever folder you want on the sdcard (CM9 Alpha 5, CleanROM, AOKP M6.2, etc etc)
5. Factory Reset
6. Flash the rom and anything that needs to go with the rom (like Gapps if you're flashing CM9 or AOKP)
7. Reboot and enjoy, be sure to update your SU binaries immediately after booting by opening up the SuperUser app
Also, do not use CWM, our device is not officially supported by the CWM team. Only TWRP is an officially supported recovery for our HOX.

stnguyen09 said:
Uhhhhh...try to relock your bootloader (fastboot oem lock) and run an RUU. You'll go back to stock. Then follow these steps:
1. Re-unlock your bootloader using the same unlock token you used before
2. Flash TWRP from fastboot (or a one-click)
3. Reboot into TWRP
4. Mount storage and put whatever rom you want into whatever folder you want on the sdcard (CM9 Alpha 5, CleanROM, AOKP M6.2, etc etc)
5. Factory Reset
6. Flash the rom and anything that needs to go with the rom (like Gapps if you're flashing CM9 or AOKP)
7. Reboot and enjoy, be sure to update your SU binaries immediately after booting by opening up the SuperUser app
Also, do not use CWM, our device is not officially supported by the CWM team. Only TWRP is an officially supported recovery for our HOX.
Click to expand...
Click to collapse
Worked. I had to leave town for a week as I was reading your reply stnguyen, so I didn't get a chance to try it until I got home tonight. I'm up and running again. Thanks a ton!

[Q] Flashed new kernel, won't boot

I used Hasoon2000's HTC All-In-One Kit to root my phone. That all worked.
The issue came when i flashed a new kernel. I placed the boot.img from King Kang's new ROM (http://forum.xda-developers.com/showthread.php?t=1959099)
Anyway, When i boot I get the HTC, quietly brilliant logo, and this in red letters "This build is for development purposes only. Do not distrubute... "
i can boot into recovery (pwr+ vol down)
And i get the ***TAMPERED*** AND ***unlocked*** tags at the top
I don't know where to go from here...
Thanks for the help.

Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.

ccamwilkins said:
Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.
Click to expand...
Click to collapse
You mentioned in your original post that you could boot into recovery, so is that not working now? Factory reset might've fubared the recovery piece, so you could do one of two things:
1) download the original RUU version for your phone, relock your phone, and flash the RUU and start over.
2) try reinstalling TWRP.
This whole thing sounds like trying to install a kernel or fastboot flash a boot.img without SuperSU correctly installed. This is what happened to me when I first unlocked my phone and tried to fastboot flash the CM10 boot.img after failing the flash from recovery twice. Without that super-user permission, bad things tend to happen. If you decide to continue on with reinstalling TWRP, make sure SuperSU.zip is flashed successfully from
TWRP, then try your rom/kernel combination again (or even a different combination if you're apprehensive).
BEWARE: sometimes partially flashing these things can corrupt your sd card. I had to reflash the original RUU to fix my phone BEFORE I rerooted and flashed a rom/kernel.

Have you fastbooted a SU to your phone after you rooted and unlocked? I'd imagine you did if you followed the toolkit.. So your on 2.20... Just download cleanrom 5.1 on your computer. Mount sdcard via recovery and drag cleanrom onto phone. Flash entire rom in recovery. I bet it works
Once your on a stable rom, download king kang from your phone. Download flashgui. Open flashgui app, navigate to king kang and let it find the boot img and flash it for you.. Once successful, immediately boot into recovery and flash entire rom through twrp.
Success
Sent from my One X using Tapatalk 2

[Q] Flashed boot.img in Fastboot, works - flashed in TWRP, does not work

Hey guys, thanks for all the previous help i've gotten from here.
Here's the deal, I have a 2.2, rooted and unlocked ATT HOXL. I flashed the SU binary and have root and everything. I'm on the stock 2.2 ROM.
Do you need to install a different ROM before flashing the kernel? If so, then I will wait until this download finished for CleanROM. If not, then continue below..
I flashed the boot.img for ElementalX-3.1 in Fastboot (Fastboot 1.14), rebooted phone like normal, phone came up, kernel is showing in the information page on the phone, it is running at 1.7ghz. That's fine, but then I realized I had never gotten any installer or anything. So, I went into recovery to flash the whole ZIP file. Go to reboot the phone and it hangs on boot after the first HTC logo.
I tried flashing the boot.img, then rebooting to recovery, and flashing the ZIP, then clearing the cache, and then rebooting. Still hangs. I am able to go into recovery and restore a backup if I need to, so at least my phone isn't dead, but I want to do this.
I also tried installing the ZIP, then rebooting into Fastboot and flashing the img, and then booting the phone up normal.
So as it sits now, I have the Kernel installed from ONLY the boot.img, I did not run the ZIP.
Do I need to flash a stock kernel in Fastboot, and then try just flashing the whole thing in TWRP? From what I have read, the steps for flashing the kernel on 1.14 is:
1. Flash boot.img
2. Reboot to recovery
3. Flash ZIP
4. Clear cache
5. Reboot phone as normal
Are those the correct steps? Do I need to flash a stock kernel before trying this again, or can I just start from square one, as if I were using a stock kernel?
Thanks

You can't flash kernels from recovery on the higher hboot. You have to fastboot them or use the flash image GUI app.
Some ROMs/kernels use a script that works around that, but not all do.

Can't install Custom Roms.

Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.

Observer000 said:
Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.
Click to expand...
Click to collapse
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM

Kungfu73 said:
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Alright, I check bootloader state, it says bootloader unlock done means it's unlocked.
I am going to flash twrp 3.0.2 and will update you soon!

Kungfu73 said:
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.

Observer000 said:
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.
Click to expand...
Click to collapse
Did TWRP 3.0.2 ultimately work with this?
If worked, I am also curious to know how much space is left there for apps in device memory, since the ROM seems to be Marshmallow based.