Database Info

[Q] Messed up trying to install lollipop for blue htc one s

hi everyone, good to finally sign up after being a long time reader here, unfortunately I have a problem.
My htc one s is rooted and I am running twrp and wanted to install the latest cm nightly so I downloaded it, googled instructions and used these instructions from a website.
Steps to Install Android 5.0.2 Lollipop on HTC One S via Official CyanogenMod 12 Nightly ROM
Boot into Recovery mode via adb or hardware buttons or use the QuickBoot app if your device is rooted.
In recovery mode, back up data on your current ROM. If using TWRP, select Backup and perform a Swipe to Back Up from the bottom of the screen.
Then select Wipe and do a Swipe to Factory Reset from the bottom of the screen.
Return to the main menu of TWRP recovery and select Install (if using CWM then choose Install Zip from SDcard.
Browse to the file where you saved the CM12 ROM zip file, select it and Swipe to Confirm Flash on the bottom of the screen. Now, wait until the flashing process completes.
After the ROM is flashed, repeat step 8 to flash the Gapps package as well.
Once both the files are flashed, return to recovery's Main menu and select Reboot > System.
I did all that and it installed fine, however, when I restarted the phone, it showed the htc logo then it just went black so I had to go back into twrp.
Instead I changed my mind and tried to install 4.1.1. jelly bean (since I needed to update anyways and couldn't because I'm running twrp and in that whole process I ended up deleting the version of jellybean and basically my phone has no jellybean or lollipop installed at all so my only option is going back into twrp.
After that, I read that my phone has to be S-off so I looked up instructions on how to install it (I'm on a mac) and apparently I'm supposed to flash the boot.img (kernel) via fast boot but in order to do that you need to have jellybean or some kind of rom running to have debugging mode on and I don't so basically this is where I'm stuck.
My apologies for the lengthy explanation but if anyone knows what to do from here that would be amazing thanks.

Can't access bootloader.

Hi,
My friend has an Xperia L with cyanognemod 11 running on it. Tried to flash resurrection remix ROM and ended up bad. These are the steps I followed:
1. cwrp recovery was already installed and bootloader was already unlocked.
2. I copied the resurrection remix zip file into sd card
3. Went to recovery, wiped cache partition. (Did not do a factory reset. My mistake).
4. Installed the zip
5. Installed the WRONG version of Gapps. Installed gapps for 4.4 instead of 5.1.
6. Device successfully booted to resurrection remix. However, the wallpaper and apps that were already there is still there! It was like I upgraded the phone to lolippop. However, it is not possible to use the phone because com.android.phone keeps crashing and everything is very sluggish. I was hoping for a fresh install.
7. Now the problem - I can't access the bootloader. If I do adb reboot bootloader or select bootloader from recovery, it just gives me a blue charging light and that's it. But I can access recovery and boot to os still. Also, cwrp recovery is now replaced by cyangenmod recovery and I can't factory reset/wipe cache from it. It fails with 'cannot load volume /misc' when I try to flash the same ROM again.
8. I can't even do a factory reset after booting into resurection remix. I press 'reset factory settings' and nothing happens.
So any ideas? The really bad thing is that I can't access the bootloader and hence cannot use fastboot.

lonesword said:
Hi,
My friend has an Xperia L with cyanognemod 11 running on it. Tried to flash resurrection remix ROM and ended up bad. These are the steps I followed:
1. cwrp recovery was already installed and bootloader was already unlocked.
2. I copied the resurrection remix zip file into sd card
3. Went to recovery, wiped cache partition. (Did not do a factory reset. My mistake).
4. Installed the zip
5. Installed the WRONG version of Gapps. Installed gapps for 4.4 instead of 5.1.
6. Device successfully booted to resurrection remix. However, the wallpaper and apps that were already there is still there! It was like I upgraded the phone to lolippop. However, it is not possible to use the phone because com.android.phone keeps crashing and everything is very sluggish. I was hoping for a fresh install.
7. Now the problem - I can't access the bootloader. If I do adb reboot bootloader or select bootloader from recovery, it just gives me a blue charging light and that's it. But I can access recovery and boot to os still. Also, cwrp recovery is now replaced by cyangenmod recovery and I can't factory reset/wipe cache from it. It fails with 'cannot load volume /misc' when I try to flash the same ROM again.
8. I can't even do a factory reset after booting into resurection remix. I press 'reset factory settings' and nothing happens.
So any ideas? The really bad thing is that I can't access the bootloader and hence cannot use fastboot.
Click to expand...
Click to collapse
There are many ways to get out of this. Nothing is really messed up. If you get a blue led, it means you're in the bootloader. Try reinstalling your fastboot drivers. Firstly, get a fota recovery. If you can boot into android, install this app, [APP][RECOVERY][ROOT]Recoveries and Recovery Installer for Taoshan , allow root access (Enable under developer options), and install Twrp. Boot into twrp, and you can wipe system, data, cache and reinstall your rom without gapps.

The app is hardly recommended by me in this case ( okok i know xD )
After reboot bootloader you get blue led... THAT is fastbootmode
And btw you cant load volumen /misc because our device have no so thats not a error (you can ignore it )
Sent from my mint using XDA Free mobile app

Thanks agent_fabulous and barbarossa, but when the blue light was on 'fastboot devices' did not list any devices. Also, unplugging the device from my pc seemed to turn it off. So I thought it was some sort of charging mode rather than fastboot. Thanks for the information, I will try them and get back to you. This community rocks!

Solved!
Using that app to install twrp worked. Wiped everything and flashed the ROM again. Working like a charm. Thanks a lot

Mate 8 Soft-brick - Any Advice?

Hi all:
I enjoyed KangVIP 386 for a couple of days and decided I wanted to fix the fingerprint sensor and i used the instructions below. Then, when I booted and tried to go back into TWRP to flash Kang VIP, my TWRP was read-only and it didn't read my internal storage. It was completely wiped and I couldn't flash the ROM. And the OS it booted into was some DL 380 version and nothing would open, no apps or chrome so it's not usable.
I tried Unbrick method via Italian knife, but it didn't work and now I can only get in the Your Device is Rebooting menu and it sticks there, or i can get into the eRecovery menu (download latest version and recovery) - but nothing works. Can't get into TWRP or boot.
Any tips?????
Thanks!
TRIED THIS ON l29 b386 kANG:
This build B386 finger print dont working? Please i flash yesterday un L29 and dont see option please help
1) Download the following:
https://basketbuild.com/filedl/devs?...e 8/boot.img
https://basketbuild.com/filedl/devs?...e 8/TWRP.img
https://basketbuild.com/filedl/devs?...208/update.zip
2) Boot into recovery and flash update.zip BUT DO NOT REBOOT
3) Afterwards back out of the install completed screen and switch TWRP to flash images in the bottom right
4) Flash boot.img to the Boot partition and TWRP.img to the Recovery partition
5) Reboot. Can take some time to finish booting, that's normal.
6) Boot back into TWRP and flash the ROM.

OK, I think I had the wrong TWRP image in the Unbrick folder for the Italian Knife unbrick function. I copied the TWRP 4.1 in there, re-did Italian Knife unbrick, then was able to get into TWRP and flashed Kang VIP. I am back in business. AND I have fingerprint working!
Man, this phone is NEUROTIC!! I'm not modding this anymore! This will be a #2 device and then I'll pick up a Pixel or something else to upgrade from my Nexus 6.

[SOLVED] Installing ANY custom ROM bricks Oneplus 6

Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
INSTALLATION TUTORIAL
Italic = recommended, but not mandatory. Do it if something doesn't work properly
0) DON'T RESTORE your apps until everything is set up, otherwise you'll have issues with GCM (getting instant notifications from messaging apps for example)
1) Reboot to blu spark TWRP
2) step deleted
3) Flash OOS
4) Flash TWRP
5) Reboot to recovery
6) Flash OOS
7) Flash TWRP
8) Reboot to recovery
9) Flash your custom ROM + TWRP + reboot to TWRP
10) Flash again your custom ROM + TWRP
11) Reboot to recovery
11 bis) Wipe data ("factory reset")
12) Flash Magisk
13) Reboot to system. It's just to make sure the installation worked.
... more on link
Click to expand...
Click to collapse
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.​- reboot, let it complete​- apply again​2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 7​14 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery​[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.​16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.

This is a bad phone .. I have it too
تم الإرسال من ONEPLUS A6003 باستخدام Tapatalk

But you seem (from post history) to be able to install ROMs :crying:
As most of those who try i guess.
Maybe my phone is somehow damaged

What some guides miss out is that you have to install everything twice. Once on slot A and once on slot B and after each install, verify what slot you are on before reboot and then check what slot you are on after reboot. I ran into issues flashing Havoc OS onto my phone too and figured it out in the end after so many times that I was in fact installing stuff twice on the same slot because it never switched over. I'll run you through the order I did things so hopefully you can follow.
-Use MSM Tool to revert everything back to stock and once the phone is booted, update to 9.0.9 either by downloading the update through the phone or by local upgrade if you have the file to hand. (remember to only have the OOS file present as any other OS in zip form crashes the local updater). You don't need to do this if you are already rocking stock Oxygen OS.
-Once the phone has restarted after the upgrade, let the post update procedure finish before continuing.
-Enter developer mode and enable OEM unlocking, Advanced Restart and USB Debugging. From here, reboot to bootloader.
-Plug your phone into the PC now and assuming you have fastboot setup ready on your PC, type 'fastboot oem unlock' and use the volume keys to select the option to unlock and press the power button to select.
-After the phone has completed it's wipe cycle, re-enable Advanced Restart and USB Debugging. The OEM unlock option should be greyed out as it's already been enabled. Make sure you don't add a pin code or password just yet as you will enable encryption which will make the next steps harder than it should be.
-Boot back to bootloader and type 'fastboot boot twrp.img' (or whatever you named it. Make sure that the image file is in the same folder you initiated cmd or powershell)
-Once booted into TWRP, flash blu_spark TWRP as that supports encryption apparently and is more stable than any other. To make sure that the script executed on both slots, hit reboot and check what slot you are on and tap the button for the other slot. Now reboot back to recovery, check you are on the other slot and flash it again.
-Now flash your 9.0.9 OOS zip followed by TWRP once on slot A and once on slot B while making sure you are on the other slot when doing it a second time. Remember that you have to re-flash TWRP after any flashable file that alters the boot partition before you reboot or you will undo all your work. Just make it habit that you re-flash it every time and you should be good.
-Once OOS and TWRP have been flashed on BOTH slots, reboot back to recovery and do the whole process again with your custom ROM (Remembering to flash TWRP before you reboot and checking which slot you are one before and after each flash).
-Once that has completed, reboot back to recovery and flash Magisk on each slot and GApps or MicroG if your ROM supports it. You don't need to re-flash TWRP after this but I do anyway to keep the habit lol.
-Entirely up to you, but before you reboot to your fresh new OS, you can wipe internal storage ONLY if you want all traces of your previous OS gone, but this will also remove personal files etc. I generally just head into TWRP file manager and delete the Android folder and keep the rest.
If you run into issues like crashes on your new OS, reboot to recovery and do a factory reset, but you will also need to re-flash Magisk again. GApps installs itself to system, so you won't need to re-flash that. MicroG does not and will need setting up again. One thing that took me a while to realise is that if you try rebooting while your USB is plugged into your PC, you will sometimes enter download mode, so only keep it plugged in when you need it for MSM Tool or to transfer files across.
I'm pretty sure I put everything down the way I did it and didn't miss anything, but it is late and I am half asleep. Will check back in the morning and double check with a fresh brain.

Many thanks for your exhaustive reply!
Will follow this tomorrow morning with a fresh brain

Fixed!
Now I'll write a guide for those in the same situation.

franticboe said:
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.​- reboot, let it complete​- apply again​2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 7​14 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery​[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.​16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
Click to expand...
Click to collapse
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.

i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
Click to expand...
Click to collapse
If you are stuck on fastboot try
fastboot set_active other
then try rebooting recovery if fails try
fastboot boot pc-stored-twrp
I found changing the active slot via fastboot may unbrick it without msm. It all depends on what steps you actually take during installation.
For installing LOS try not flashing twrp after installation. Los comes with its own recovery. Anyway if it says no OS installed you HAVE to fix recovery bootloop.

Unlock bootloader, flash twrp, vbeta, flash rom...ok but phone no boot!!!

Guys!!! what the hell!
i did everyting was written in here. Bootloader unlock, everything ok, flashed twrp, flash vbeta.img then flash any rom but the phone never boot! still go always and alwasy again to recovery!!!
What am i missing?

Format data in twrp.then reboot

I've done everything. Format everything ecc but nothing has changed...still no boot and recovery immediately.
I've tried to put the stock recovery again and it boots (i flashed of course via twpr the c.01 RUI ozip file before). I really can't understand.
I've tried to root the phone but again problem. I put the twrp recovery again (on the C.01 stock rom) then flashed magisk 20.1 or the latest. Everything ok, rebooted and....it says the boot img is corrupted, write or go to the service support! So i entered again in fastboot and flashed a new boot.img. No boot but can enter recovery. Put again the twrp, flashed stock rom again, put stock recovery, format data and now eveyrhing ok. Why so hard to even root???

Did you check format data on right bottom of twrp.this is not same as the wiping data

i made all format.
another curious stuff is. I put twrp, vbeta img . Reboot in twrp. ok. I reboot phone, go to RUI then i try to go again in recovery and .....no more twrp! but stock one! twrp has been replaced! why!!!!!?

Correct,Stock rom will replace twrp to stock recovery.but custom rom not changing recovery

I was doing the same mistake.
You must Format Data after flashing Rom and if on reboot to system it says Os not installed then first reboot to recovery.

waqar bukhari said:
I was doing the same mistake.
You must Format Data after flashing Rom and if on reboot to system it says Os not installed then first reboot to recovery.
Click to expand...
Click to collapse
uhm ok.
So basically - Flash twrp - go to twrp - flash rom (pixel experience for example) - format data - and then reboot to recovery again?? what's the point sorry

oh man i missed up the format stuff.
Thank you very much. I made it. After format data then i insalled the pixel experience rom via adb sideload now it started let's see hows it the modding rom world on this device!

I followed all those steps. My phone boots, stays on Lineage logo for 4-5 minutes and then it reboots back to orange recovery. Any idea? Thanks!