Database Develop

[Q] I'm stuck in StartUP Boot Screen

Hello XDAs
I'm middle of the way on rooting my phone (Nexus One, Android 2.3.4) & flashing a custom rom (cm7 passion-V106)
I follow the tutorial at below & i've done most of the steps
http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide
Here is what i've done,
-Unlocking the Bootloader
-Installing a Custom Recovery Image both Amon_Ra's Recovery & ClockworkMod Recovery but Amon_Ra is not working.... i unable to boot into Amon_Ra...
-Flashing Radio 5.08.00.04 but i receive a error message that the version is not supported
- Flashing CyanogenMod via ClockworkMod Recovery but i didn't receive install sucessfull message, it only return me back to ClockworkMod Recovery menu.
- Flashing Google Addon Apps via ClockworkMod Recovery - the only flashing that i receive install complete message
After i've done the process above and its come out that i have stuck on the CM7 Loading screen (Blue boot animation screen)
There is a few thing i've noticed which might be the problem...
1:The S_Lock is till On when i boot into Bootloader mode
2: My phone is still unrooted and i unable to use the ROM Manager from Apps Market.
3: sometimes i will not able to access ClockworkMod, it only shows me the " ! " Sign with an Android logo next to it.
Can someone help me with this... i'm stuck now and unable to turn on my phone...

http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
Sent from my Nexus One using XDA App

Unlocking the bootloader doesn't give you s-off or root. You would need a rooted rom to run root apps/superuser.
You need to wipe everything and flash the rom again in recovery (you can't have both recoveries installed at once btw). Your hboot may need updating.
Flash the radio via fastboot so you don't brick your phone. Download it again in case your version is corrupt. You might wanna flash the recovery again.
Might be easier to go back to your nandroid backup (that you must have made, right?) and have a working phone for a while until you read around the subject.
*edit* or just read the wiki lol

[Q] Flashing a ROM with Unlocked Bootloader but S-ON. Possible ?

Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks

anirudhgargi said:
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
Click to expand...
Click to collapse
as mentioned in the previous post you made, you need to install a custom ROM first in order to boot back into your phone. You have unlocked the bootloader and installed TWRP recovery. Now you need to sideload the ROM by adb sideload commands in order to boot the phone up again
Do not run an earlier RUU.zip as you will brick your phone. Firewater needs a working ROM, there are no ways to bypass this

Flash ARHD 81 or Insert Coin or Team Venom Rom
Step 1. Unlock Bootloader and Install TWRP 2.7.x.x recovery. Don't install Twrp v2.8.x.x, wont work with any roms.
Step 2. Boot to Recovery.
Step 3. Mount the system using twrp. I am assuming that you don't have custom rom on your phone storage.
Note that TWRP v2.7.x.x wont mount the phone storage. v2.7 and above always had issues. My recommendation is to install TWRP v2.8 for temporary purposes. Now mount the phone storage copy any rom you downloaded to the system.
Step 4. Assuming that you install TWRP v2.8 to copy rom files to phone storage. Boot to bootloader again and Install TWRP using fastboot. Command: "Fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img"
Step 5. Reboot to recovery. WIPE DATA, CACHE, DALVIK CACHE, SYSTEM > Install Rom.
Note do not wipe "internal storage." Otherwise you have to go back and start again with installing twrp v2.8, then copy rom...
Step 6: follow the steps.
IMO ARHD 81 is a stable rom, provides better battery life. If you like Sense then stick with this Rom, if you want Stock Android aka AOSP then try aospa legacy, CM, SlimKAT, AOSB and many more.
Moreover, i haven't found RUU for Sense 6 KK4.4.3, if you do please provide me a link as well.

As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho

Not able to copy my custom rom in phone.
stovie_steve said:
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Click to expand...
Click to collapse
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.

anirudhgargi said:
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
Click to expand...
Click to collapse
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again

No luck ! Fastboot mode also not getting detected now.
stovie_steve said:
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
Click to expand...
Click to collapse
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,

anirudhgargi said:
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
Click to expand...
Click to collapse
Sounds also like a driver issue
Try instling HTC sync to get the up to date HTC drivers and retry. Use different usb ports (2.0 preferably) and different cables. If it's saying fastboot ac then the phone is not being detected correctly, so it's a driver issue
You can also try manually installing the driver by searching for I think the Google naked driver

[Q] Issues with TWRP 2.8.2.1

Hello
I used WugFresh's awesome Nexus Root Toolkit to unlock, root and install custom TWRP recovery. I have 2.8.2.1 version installed. I am unable to do any tasks with this TWRP, however. It throw error when I try to Wipe Cache, make backup or anything else for that matter.
I tried to update using fastboot but I haven't figured that part out yet.
Can anyone provides some assistance as to what the cause of error could be? I am on 5.0.1 build, encrypted.
Thanks

Try:
Code:
fastboot flash cache cache.img
From your 5.0.1 factory image, keep extracting until you see all the .img files including cache.img.

I didnt have any issues with 2.8.2.1 but i have since switched to 2.8.2.0 since its the official version.
Download 2.8.2.0 from their website. Boot into bootloader and type fastboot flash recovery recovery.img where recovery.img is the downloaded twrp file.

I was able to flash cache.img, but TWRP is still giving error when I try to do any action. It keeps saying unable to mount storage.

JManekia said:
I was able to flash cache.img, but TWRP is still giving error when I try to do any action. It keeps saying unable to mount storage.
Click to expand...
Click to collapse
Flash the 2.8.2.0 twrp img

Thanks. It was the encryption doing its job. I had to put in the password to get it going. Appreciate all the help here

I can't seem to flash new ROMs - get an error message "E:Error executing updater binary in zip". Tried both slimRom and Liquidsmooth
I'm rooted on 5.0, decrypted, busyboxed, with the latest TWRP v2.8.2.1. Any ideas?
Any ideas?

I'm having the same issue, did you ever get it resolved?

i am also having this issue....I have a thread going. "HELP i cannot flash any custom roms"

The TWRP 2.8.3 is out and has been for a little while I would try the newest version (the one I said above) it seems to be working better for me than the earlier ones.

Trying to get back to stock rom

Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.

Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'

Pixel 5 is broken after flash

Hello, I wanted to free my pixel 5 (android12) from google and install the e.foundation os. I managed to unlock the bootloader. At further step something must have gone wrong and I came only in the recovery mode. Then I flashed TWRP and wanted to install android 11 from there. I did not know which version for my phone is the right one. TWRP has any errors displayed. I have a few years ago on another phone made a custom rom flash on it and thought I know what I'm doing but thought wrong. I selected all the check marks in the wipe data menu and formatted everything. Then nothing worked and the phone went into bootloop. Now I managed to get into the recovery mode. But I can not flash TWRP or rom. Can someone maybe give me a tip? or do I now have a 500 euro expensive stone here.
I am grateful for any advice. this flashing is very complicated for me a I had it somehow easier in memory.
I speak german and the text was created with deepl
there is a photo of the screen

Okay you can try this
Download ADB AND MINIMAL FASTBOOT
Download TWRP
1. Open ADB AND MINIMAL FASTBOOT
2. Type fastboot flash recovery /path/to/twrp.img
3. Try reboot to recovery mode.
4. If you can reboot to recovery mode (TWRP) - Copy stock rom to device and flash it.

I have also tried this with TWRP but i always get the error message:
FAILED (remote: Not allowed to flash (recovery))
i have also tried several roms to flash after unpacking.
fastboot flash bootloader runs through
fastboot flash radio runs through successfully
fastboot update image but not
and ends with the message:
FAILED (remote: Partition should be flashed in fastbootd).