Database Users

Stuck at rogers logo

I flashed with the latest cyanogen on a 32A in CM's recovery image, i had the patch for the kernel (take it from 32B to 32A) but i didnt get to apply it yet.
when i rebooted my phone it hangs on the Rogers screen, i can get to fastboot and recovery mode (stock recovery mode). I made a nandroid backup (before the flash) but i cant get to it from the recovery mode menu, and when i connect the fastboot usb, my sd card doesnt show up on my computer. so i cant run the fastboot command to load the recovery image...
is there anything i can do?

some more information:
when i go into recovery mode, the "removable disk" shows up in my computer, but clicking on it just says "please insert a disc into drive..." which leads me to believe it is not mounted, any way to do this from recovery?

It'll never boot when you haven't installed the 32A patch.
And that means that you'll never be able to mount the SD card to have it show up in Windows. You can use adb to push the update.zip file to your SD card while in Recovery mode.
(You'll need the Android SDK installed for this)
Start up your phone in Recovery mode using the Power+Home buttons.
Once in recovery, wait for Windows to detect the phone (about 30 seconds).
Copy the 32A patch to your Android SDK tools folder, then run:
Code:
adb push <filename for your 32A patch>.zip /sdcard/update.zip
This will push your 32A patch to your SD card as update.zip.
Then apply update.zip through your Recovery environment.
A note to you... Before running the adb push, try running:
Code:
adb shell
mount /sdcard
exit
adb push <filename for your 32A patch>.zip /sdcard/update.zip
This will make sure that your SD card is properly mounted before copying the file to it.
To check that the file is there before trying to update, run this from your Command Prompt.
Code:
adb shell
cd /sdcard
ls | grep update.zip
You should see update.zip listed there.
After you've applied the 32A patch zip file through your Recovery environment, reboot your phone.
Should work now...
If you haven't installed the Amon_RA Recovery yet, it would be a good idea. It lets you save and update zip file to the root of your SD card without renaming it to update.zip first. You can apply any update zip file as an update.

thanks for the reply,
when i type adb shell i get:
"error: device not found"
typing adb devices also yields that the device is not listed
but windows does make the noise notifying that a device is connected, and the Removable disc still comes up in my computer

when i go into Device Manager, under disc drives it shows up as
HTC Android Phone Usb Device when the phone is in recovery
and if this makes any difference, press home+power again and look at the options in recovery the bottom says "E:Can't open /cache/recovery/command"

it worked in fastboot/recovery before, but that was when i had USB debugging selected and before i flashed CM i wiped. could this be the reason why im not able to access the phone with adb in recovery/fastboot?

for some reason i was able to fastboot into cm's recovery image and then the device was listed in adb, i followed your instructions and applied the patch, the phone booted up!
thank you!!!!! phew, that was a close one

zeotrope said:
for some reason i was able to fastboot into cm's recovery image and then the device was listed in adb, i followed your instructions and applied the patch, the phone booted up!
thank you!!!!! phew, that was a close one
Click to expand...
Click to collapse
The CM recovery works great but without a hardware keyboard it's not entirely functional.
I'd recommend flashing Amon_Ra recovery and using that. Read the directions carefully though. Make sure you use the right one for your phone.

got amon-ra's recovery permanently flashed on there, thanks again for your help

Stuck at boot screen

Hi.
It all happend when i wanted to replace the libwebcore.so file in the /system/lib.
So i did it. but its properly the wrong libwebore.
so i restarted the phone, but now, its stuck at the tattoo screen.
I can connect it to the computer. adb can see it. but i cant su neither mount which requires su.
It's the custom rom. i have no recovery image installed.
i CAN access fastboot AND recovery mode
I tried flashing a rom via HBoot by renaming the rom to CLICIMG.zip. but it doesnt work. phone says no image or wrong format.
Any suggestions?

Well, this really sucks
Now i cant even access adb. I pressed home+back key to reset the phone.
now its just stuck on the tattoo screen like just before but adb devices dont see anything.
Pleassee someone? i really need help on this one!
Hboot doesnt seem to help much. it cant detect anything. i had 3 files on the sdcard (all is amon_ra), just named differently: CLICDIAG.zip, CLICIMG.zip and CLICIMG.nbh
but it doesnt do anything :'(

Do you have a backup?
Have you tried to install recovery img via adb? If you can do this you can just do a backup of your current rom, try somehow to get your sd-card seen by the computer and copy the files of your old backup files to your new backup, asked to replace select yes.( I used a different phone to copy my backup files to the sd card when I couldn't get past startup screen.)
Good luck.

XabdullahX said:
Well, this really sucks
Now i cant even access adb. I pressed home+back key to reset the phone.
now its just stuck on the tattoo screen like just before but adb devices dont see anything.
Pleassee someone? i really need help on this one!
Hboot doesnt seem to help much. it cant detect anything. i had 3 files on the sdcard (all is amon_ra), just named differently: CLICDIAG.zip, CLICIMG.zip and CLICIMG.nbh
but it doesnt do anything :'(
Click to expand...
Click to collapse
Where you found these files?
To flash the rom from hboot you need the rom.zip file of your stock rom(renamed as CLICIMG.zip)

I have the same problem! stuck on "Tattoo" screen and boot again and again.
I have the goldcard with CLICIMG.zip and it loads on HBOOT and install all (boot,radio,recovery,etc.. ) but when it ends, returns to the same....
HELP PLEASEEE!!!

Do you have Amon_Ra or Clockworkmod recovery installed? If so you can try wiping the Dalvik cache and try rebooting. Most boot loops I had were resolved this way. Wiping data and cache totally might also help.
If you can access adb and device is rooted, you should be able to use "adb shell" command and have a rooted terminal with the "#" sign after running su. In that case you can also manually wipe Dalvik cache by deleting everything under /data/dalvik-cache/
$su
#cd /data/dalvik-cache
#rm *
#exit
$exit
Click to expand...
Click to collapse
Good luck!

tihe problem is that i can´t access to the phone by adb
i put "adb shell" and it says: "error: device not found"
the phone screen shows a phone and triangle with exclamation

[Q] MT3G bad recovery flash, stuck

Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.

truss said:
Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
Do you still have root? If you can get into ROM manager, reflash clockwork recovery, then wipe cache, dalvik, and run a fix permissions. That should get you back up and running long enough to try again to flash amon ra.
Not sure if the oem spl will let you fastboot flash a new recovery but that's your most reliable bet.
It sounds like it might be time to do a full wipe and reflash anyway. Have you heard of Ohsaka's SuperWipe?

I tried reflashing Clockwork through ROM Manager. It says "root granted", "clockwork flashed" immediately. When I try to boot into recovery - I get stuck on green MyTouch screen forever. Battery pull is the only way out.
I guess the problem is that I cannot get to any recovery anymore. Any ideas?

Do you have fastboot. If so you can flash recovery from there.

kodjo said:
Do you have fastboot. If so you can flash recovery from there.
Click to expand...
Click to collapse
Can I do that through adb shell? I don't think I built fastboot.

truss said:
Can I do that through adb shell? I don't think I built fastboot.
Click to expand...
Click to collapse
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B. http://www.filefactory.com/file/caa48b0/n/recovery-RA-sapphire-v1.7.0G-cyan.img
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.

Phateless said:
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B.
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.
Click to expand...
Click to collapse
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.

truss said:
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.
Click to expand...
Click to collapse
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.

Phateless said:
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.
Click to expand...
Click to collapse
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.

truss said:
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.
Click to expand...
Click to collapse
Nice! Glad you got it sorted out.

[Q] Bricked my Desire Z

It seems I bricked my Desire Z. That'll teach me for messing with custom roms
I only get the bootloader (the white screen with coloured text). Everything I do from there either does nothing or just goes to a white screen with a green HTC logo and then hangs.
I tried flashing Cyanogenmod by renaming the zip pc10img.zip, this failed. I tried installing an official G2 rom from the SD, this also failed. When I turn the thing on I get a green HTC logo, when I try to go to recovery it's the same story.
Can anyone help me get my phone back to life?

When you get in to recovery are you getting any error messages?
Have you tried restoring a nandroid backup or trying a different sd card?
And re-naming a rom to PC10IMG.zip will never work

I don't get an error message, it just hangs at the HTC logo. Same when I reboot the phone.
I don't have a backup since the last time I tried using one, it didn't work. Besides, I don't have Clockwork so I wouldn't be able to restore it even if I had one

Neko Koneko said:
I don't get an error message, it just hangs at the HTC logo. Same when I reboot the phone.
I don't have a backup since the last time I tried using one, it didn't work. Besides, I don't have Clockwork so I wouldn't be able to restore it even if I had one
Click to expand...
Click to collapse
You cant get in to clockwork. have you tried using adb?

Not yet. Is it possible to flash a rom or even just clockwork through adb?
I'm sorry for being such a n00b about this, I'm just not that experienced yet with android devices. Used to change roms on my WinMo device all the time but Android's... quite different

If you have the ENG Hboot you can flash the recovery from fastboot....
If you have the sdk set up on your computer do the command (after putting the clockwork recovery in your sdk folder):
fastboot flash recovery recovery.img
then go to the recovery, wipe and flash

I now have the issue that ADB won't see the phone. The phone says HBOOT USB PLUG so it knows it's connected through USB, it shows up in my device manager but ADB won't recognise it. Any suggestions?

adb won't work in hboot/fastboot mode, you need to get the fastboot executable.
It might be in your tools folder for adb.
You can make sure its working by running 'fastboot devices'
-Nipqer

Nipqer said:
adb won't work in hboot/fastboot mode, you need to get the fastboot executable.
It might be in your tools folder for adb.
You can make sure its working by running 'fastboot devices'
-Nipqer
Click to expand...
Click to collapse
Thanks! Fastboot detects the device Now I can try to fix stuff.

It worked! I managed to install Clockwork Recovery using Fastboot and after that installing Cyanogenmod was a piece of cake Thanks you guys!

The most important thing I learned from playing with roms is how to read the manual. Be careful out there.
Sent from my HTC Vision using XDA Premium App

Ahem, guys, where can I find fastboot executable? I checked everywhere in the android-sdk directory but I can't find it. I even updated to the latest SDK tools, and yet fastboot is still MIA.

Always and I mean ALWAYS create backups of your working roms, I cannot stress this enough.
You can copy files onto your sdcard using adb then force boot into cwm. Thank goodness for adb
Sent from Space using Tapatalk Pro

Phones in a bit of a state

Hey guys,
Yesterday I tried, after a few months of not modding my phone, to update my recovery as i was running a very old version of TWRP. Long story short I did something wrong somewhere and my phone has ended up in a bit of a weird state.
At the moment the OS is BlissRom, however it fails to boot. The loading screen runs very slowly and never actually boots the OS. The current recovery is the stock recovery.
The thing that is giving me an issue is the fact that somehow the bootloader has locked, so I am unable to flash a new OS onto my phone. I'm not able to flash anything onto my phone as it throws an error telling me the phone is locked.
Overall I aren't able to boot into the OS, however I have access to the stock recovery and fastboot. Unfortunately it looks as though the bootloader has locked some how.
Any ideas how I can fix this, or have I completely messed my phone up?
Thanks in advance.

Hi
U said u were running twrp before which means u have unlocked bootloader and flash roms already.
How did u end up with stock recovery?
Also is it phone being detected bycur PC?
Sent from my ONE A2005 using Tapatalk

I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.

colinbest2 said:
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
Click to expand...
Click to collapse
Did u also tried command fastboot oem unlock
Sent from my ONE A2005 using Tapatalk

Indeed I have, I get an error saying "phone is locked".
I think the resolution will be running the restoration tool fully but i cant seem to get it to do anything. It just sits there with no progress bars appearing.
Have you ever had any experience with this tool?

No I never used recovery tools.
Can u at any point let's say u boot into recovery and connect the device to PC, will it detected the internal storage?
Sent from my ONE A2005 using Tapatalk

Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.

Dude i think you have to use recovery tool now
Here is the link first read carefully https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Thanks for the link buddy.
I've gone through this thread, I think the issue preventing this from working for me is the fact that although I have installed the relevant drivers, when I plug my phone into my PC the drivers assigned to it are "Android Bootloader Interface". When I try to target another driver, using the Update driver functionality it just refuses to change, saying the driver already assigned is the newer one.
Any ideas how I can get around this? I know ideally it should appear as Qualcomm 9008. I've tried all the methods in the "How to Make the device show as Qualcomm 9008" section without any success.

colinbest2 said:
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Click to expand...
Click to collapse
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk

Brandon Indar said:
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.

colinbest2 said:
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
Click to expand...
Click to collapse
Try this one :
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip
If still stuck on boot logo, boot in fastboot, connect to PC and run command : fastboot erase userdata
If not work try sideload a rom u have with same steps[emoji4]
Sent from my ONE A2005 using Tapatalk