So I pulled out my old Droid-X today to use for secondary reasons (rooting, development, etc)..
Unfortunately, after charging and attempting to power on, it hangs at the "M" (Motorola) Logo Screen indefinitely!
:crying:
I AM however able to power it on into the Recovery options!!
(I whiped the system Cache but it didn't help)..
Anyhow..
At this point, I want to explore options how to Recover the phone - ways to Root it and load a Custom ROM.
Unfortunately though, I am NOT ABLE to access the Phone's Settings to allow Debug mode, or allow Third-party apps, etc..
So is there a way to Recover the phone by Rooting+Custom ROM, considering it wont Boot past the "M" Logo?
Any and all help is VERY MUCH appreciated!
Thanks in advance!
ender87i said:
So I pulled out my old Droid-X today to use for secondary reasons (rooting, development, etc)..
Unfortunately, after charging and attempting to power on, it hangs at the "M" (Motorola) Logo Screen indefinitely!
:crying:
I AM however able to power it on into the Recovery options!!
(I whiped the system Cache but it didn't help)..
Anyhow..
At this point, I want to explore options how to Recover the phone - ways to Root it and load a Custom ROM.
Unfortunately though, I am NOT ABLE to access the Phone's Settings to allow Debug mode, or allow Third-party apps, etc..
So is there a way to Recover the phone by Rooting+Custom ROM, considering it wont Boot past the "M" Logo?
Any and all help is VERY MUCH appreciated!
Thanks in advance!
Click to expand...
Click to collapse
hello!!
As you said the phone isn't booting up.
so i may recommend you flashing a stock rom first through the working recovery.
or if you want to have a custom one then it will let you do so through the fastboot ( but device should be rooted!).
if you are interested to install a custom rom that can be done but you need to reflash your phone to the stock rom.
that's the fix.
Thanks for the reply! So when you say to "flash a stock rom", you're just saying to boot up into the recovery menu using the volume key, and simply selecting the factory wipe/restore option? Correct? From there, (assuming it was able to successfully flash to stock and boot up completely), I would then be able to achieve root and flash a new rom.. Sounds simple enough. Thanks. Also though, you said "or if you want to have a custom one then it will let you do so through the fastboot" -- how exactly would I go about doing that? ..you say "but device should be rooted" which it's not. So I'm guessing that makes the 2nd option impossible, meaning I only have 1 option, which is the factory wipe, is this correct?
Thanks! :good:
pratyaksh tyagi said:
hello!!
As you said the phone isn't booting up.
so i may recommend you flashing a stock rom first through the working recovery.
or if you want to have a custom one then it will let you do so through the fastboot ( but device should be rooted!).
if you are interested to install a custom rom that can be done but you need to reflash your phone to the stock rom.
that's the fix.
Click to expand...
Click to collapse
ender87i said:
Thanks for the reply! So when you say to "flash a stock rom", you're just saying to boot up into the recovery menu using the volume key, and simply selecting the factory wipe/restore option? Correct? From there, (assuming it was able to successfully flash to stock and boot up completely), I would then be able to achieve root and flash a new rom.. Sounds simple enough. Thanks. Also though, you said "or if you want to have a custom one then it will let you do so through the fastboot" -- how exactly would I go about doing that? ..you say "but device should be rooted" which it's not. So I'm guessing that makes the 2nd option impossible, meaning I only have 1 option, which is the factory wipe, is this correct?
Thanks! :good:
Click to expand...
Click to collapse
Just booting into recovery and factory reset is not the method .you need to flash a stock ROM from the update option.
Then only you will boot. Here is the link to the stock ROM (gingerbread)
http://forum.xda-developers.com/showthread.php?t=1517985
Hope it might help.
Download file( PC) put it on sdcard and flash it. Done.
Then you can install CM 11 on your device after you root it through kingoroot once you install this stock ROM
You can also yourself search for stock ROM for droid X if this didn't helped.
Good luck:good:
Hit thanks if helped
Related
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Did you wipe before restore?
davebugyi said:
Did you wipe before restore?
Click to expand...
Click to collapse
Yes, I did a full wipe including dalvik cache before all restores. At this point, though, my primary concern is just finding a path back to usability!
DIncLover said:
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Click to expand...
Click to collapse
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
bruuuno said:
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
Click to expand...
Click to collapse
I can try this when I get home today.... I'm just concerned because the method involves nvflash .... which I thought didn't work from the newer TF models (I have a model B80). I needed to wait for the RazorClaw exploit because previous attempts at using nvflash failed....
Then NVFlash will fail still...
davebugyi said:
Then NVFlash will fail still...
Click to expand...
Click to collapse
So am I hopelessly hosed?
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
baseballfanz said:
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
Click to expand...
Click to collapse
OK .... my bad.... I guess I wasn't pressing the buttons in the right sequence/duration. I CAN get to CWM!
So, once again, I try to restore the Nandroid backup and after rebooting, end up with the screen situation as in the reference you provided.
So, I am assuming my Nandroid backup is not restoring the kernel that it needs. I was running a recent OTA update; I believe the version was 8.6.5.19.
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
DIncLover said:
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
Click to expand...
Click to collapse
Look here
http://www.gnufabio.com/revolver/dls/
Same issue, no recovery though
Hi,
I have the same issue as the original poster, B80 serial, RazorClaw root. However, when I boot to recovery I get the green android with yellow triangle and exclamation mark.
I need to restore a recovery on my device as I may need to unroot to send to Asus. I have an even deeper problem of having to have the device connected to power for it to turn on after shut down.
However my main question is for that serial number and root method, what is the best way to flash a recovery on my device (stock or CWM) if I can not get into recovery to begin with?
P.S. RecoveryInstaller will not work, after installing the apk, I click the flash recovery button, the system holds for a bit, then nothing happens.
I will continue to search the forms for some answers, any insights or direction will be appreciated.
I can get into apx mode.
Thank you community!
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
gee one said:
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
Click to expand...
Click to collapse
Everything I see in the forms requires one of several conditions which my TF doesn't currently meet.
1. Recovery. I can not go into any recovery, thus I can not perform any flashing of any other rom or recovery.
2. B70 or later. Because of the security in the boot for these new serials, I can not use the NVFlash tools to un-brick / flash.
I am already rooted, however I do not know the reason for lack of recovery on this device. I unfortunately bought it yesterday from Craigslist, so not sure what this guy did before I got it.
I searched for flashing recovery staging partition and did not find anything immediately relevant. Please advice is there is a different wording I should use in my search as I am now getting an immense download on all of this trying to figure out what to do. I am also fairly new to Android devices having 1 other phone that is rooted.
Thank you for all the support and quick response! wonderful community here.
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
gee one said:
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thank you gee one. I have since been able to install clockworkmod. My issue with the power not turning on if not plugged in still persists, I have started a separate thread.
I found your post on the staging partition here:
http://forum.xda-developers.com/showthread.php?t=1309949&highlight=power
Do you recommend this for the issue still persisting?
If so, considering I am on 8.6.5.19 will I have to use the blob from that? It is not on Asus website as I got it from the firmware update option in the settings before loading up my new ROM.
Do you recommend this step as the only resolution or is there another way?
Ok let me get this straight:
You have clockworkmod installed. Can you boot into it and do the buttons work?
Are you getting a garbled screen when you boot into the rom? Or are you just trying to unroot?
The tricky part is to avoid the bootloops of death.
sent from my cyanogen(mod) vision
Honestly what i would do if i were you, assuming i understood correctly that you can get into clockworkmod, just reflash the prime rom you didnt like(after wiping everything, including cache and dalvik), and if it boots and everythings okay, at least you know nothings really wrong with ur tablet. As for the plug in situation, make sure your battery isnt simply dead. As far as i know, it wont charge from recovery, so if uve been stuck without a booting rom for a while, it being dead could definitely be possible. Once you are in a working rom and you sorted out the charging issue, then you should worry about getting back to stock.
Thank you camaros,
I am able to load stock ROM successfully.
Battery is not dead as it is fully charged, and will run un tethered after powerup. I will test resetting it although I doubt that is causing it.
What i would like to determine is, is this related to a hardware or software issue?
Also, is there a way to restore stock recovery from CWM?
I have been searching for hours..and still couldn't find an asnwer..
at first when my phone was still alright I did a factory reset and after that
it stuck on a boot screen with android in the middle...for a long time
then I use vol down + power method to reset it and clean everything (like system,cache and boot) all of them...
now I stuck on the green htc boot screen
I tried to install rom and kernel but still won't work I wonder whats the problem now
any idea???
thanks
nias9527 said:
I have been searching for hours..and still couldn't find an asnwer..
at first when my phone was still alright I did a factory reset and after that
it stuck on a boot screen with android in the middle...for a long time
then I use vol down + power method to reset it and clean everything (like system,cache and boot) all of them...
now I stuck on the green htc boot screen
I tried to install rom and kernel but still won't work I wonder whats the problem now
any idea???
thanks
Click to expand...
Click to collapse
You haven't searched that bad, if not you would have come across this:
http://forum.xda-developers.com/showthread.php?t=1396229
Anyway, are you rooted? if you are rooted and did a factory reset then you don't have a Rom in your phone and that is why you are stuck on the splash screen. You even wiped everything, so probably erased usb debugging drivers from the device.
Well, you have these choices: 1) If you still can access your custom recovery (CWM or 4EXT) then you need to put a rom in your sdcard and flash it. You will have your phone back. You can even restore a nand backup and have your system as it was at that time.
2) If you are S-OFF, but can not access a custom recovery, then flash it again and follow option 1)
3) Use a PD98IMG.zip file to flash a RUU in hboot and you will get back. In the link I provided above, you have several links to those files.
In all cases, you will need an sdcard reader or someway to get the files to your sdcard.
Hope it helps....
thanks!!!!
problem solved
I'm having the same problem stuck on the android boot screen I can access recovery and tried to flash a few different roms but with the same results.
Fortis4Eva said:
I'm having the same problem stuck on the android boot screen I can access recovery and tried to flash a few different roms but with the same results.
Click to expand...
Click to collapse
Did you read the link that glevitan posted a couple posts above yours? Did you try what it says? Which option? What happened?
It seems I'm stuck in bootloop after font installation.
I have an HOV on primou.
If I understand it correctly, I should be able to boot into recovery from the phone and just install the backup I made from CWM- correct?
Problem is, I can't access the recovery menu on the phone...
Did this option change when I flashed a new ROM?
Stock hov gave access to this using the power and volume keys...
Of course hoping to do this from the phone w/out the pc.
Anyway, I advice is greatly appreciated thanks.
Yes, as stated in the subject, I've reverted to stock firmware for my specific device (Photon Q C Spire) from trying a few different custom roms, and have this issue now. It will load properly if I don't install custom recoveries. I've tried different CWM and TWRP versions, and none will load Android as the stock recovery does.... Any suggestions?
p.s. I was looking into possibly using something called an SBF file...
Reverting to the stock firmware, you use RSD Lite to flash a FXZ file - you have already done this or not?
Yes, I that's how I got back to factory settings. I lost my root and custom recovery in the process of course. But after booting Android, and doing the initial setup and activation, I decided to install a custom recovery to root it that way. Well, couldn't boot past recovery, so, had to revert back to stock recovery and root via the exploit with Android running in developer mode... sucks. But I'm currently rooted on a fully functional 4.1.2 C Spire FXZ.
So what's you end goal? Stock ROM with custom recovery?
You fastboot flash the custom recovery of your choice, boot said recovery, take a backup.. and then when you try to 'Reboot System' to boot Android, it fails to boot? How long did you let it boot? Do you get a boot animation?
No boot animation, because it boots straight into recovery no matter if I hard reset, soft reset, power/down power up or any means of trying to load Android. Also, the bootloader/fastboot screen wouldn't even load, it goes straight into the custom recovery every time. The only way I could get into bootloader/fastboot was by holding the Vol+Pwr keys. So, what I did was install stock recovery, and it then booted normally.
sulken2000 said:
No boot animation, because it boots straight into recovery no matter if I hard reset, soft reset, power/down power up or any means of trying to load Android. Also, the bootloader/fastboot screen wouldn't even load, it goes straight into the custom recovery every time. The only way I could get into bootloader/fastboot was by holding the Vol+Pwr keys. So, what I did was install stock recovery, and it then booted normally.
Click to expand...
Click to collapse
Well it seems like you're good then...?
When I was on stock, I installed TWRP and immediately took a backup of my stock configuration. I still have that backup, and it still works fine.
hello everyone, today i tried to flash twrp on my phone (rooted with magisk and running stock samsung rom), the flash was successful and i was able to boot into twrp but i coudnt access my storage or anything else, so i saw a guide saying to change the filesystem to ext2 then ext4, after i did that i could access most of the other folders but not the storage foldier as it still showed 0mb. i thought i just need to reboot my device to fix the issue but now im stuck on a bootloop. i cant poweroff the device since no button combination is currently working. is there anything i can do to power it off or do i have to wait a few days till the battery drains to 0?
[RECOVERY][UNOFFICIAL] TWRP for Galaxy A53 5G (Exynos)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
this is the link i used to flash twrp except i didnt follow the wipe instructions because i dont want to use a custom os.
and if nothing else works and i have to wait a few days till it drains to 0, will i be able to boot back into samsung's recovery mode or is this device hard bricked?
help will be greatly appreciated.
This phone doesn't have the nice feature of holding the power button for force off so that is a negative here.
I don't think you should have edit:changed the partition types. If that was necessary it would be a ridiculous thing for other Android roms to have to do. Its all Android so should have worked without that.
Its unlikely that anything new will result from a cold boot verses a warm boot. Worth a shot I suppose but don't hold your breath. Expect nothing new.
If its stuck without Odin, fastboot, ADB, all buttons not doing anything, can't ingest and do something from sd card, can't show up via USB on computer, etc with nothing at all then its totally finished since nothing can be done. Consider it a loss and learn from it.
I'd like to also state that there are for some reason people who supposedly bring roms over to devices and they don't have the device so therefore don't really know if it works or not. You have to be careful about the guides you follow. I've seen someone try with a device that could not be unlocked ever for anyone and that person thought it would work. Live and learn.
sandsofmyst said:
This phone doesn't have the nice feature of holding the power button for force off so that is a negative here.
I don't think you should have edit:changed the partition types. If that was necessary it would be a ridiculous thing for other Android roms to have to do. Its all Android so should have worked without that.
Its unlikely that anything new will result from a cold boot verses a warm boot. Worth a shot I suppose but don't hold your breath. Expect nothing new.
If its stuck without Odin, fastboot, ADB, all buttons not doing anything, can't ingest and do something from sd card, can't show up via USB on computer, etc with nothing at all then its totally finished since nothing can be done. Consider it a loss and learn from it.
I'd like to also state that there are for some reason people who supposedly bring roms over to devices and they don't have the device so therefore don't really know if it works or not. You have to be careful about the guides you follow. I've seen someone try with a device that could not be unlocked ever for anyone and that person thought it would work. Live and learn.
Click to expand...
Click to collapse
hello, i was able to boot the phone into twrp and do a factory reset, i had to time the vol up + power button at exactly the time when the screen went black and it worked!. but now i have a question, if i want to get twrp again and i dont plan to flash a custom rom like it says in the guide, how do i get twrp to recognize my storage? and do you flash twrp before installing an os or after because ive done it after installing the os.
floppen22 said:
hello, i was able to boot the phone into twrp and do a factory reset, i had to time the vol up + power button at exactly the time when the screen went black and it worked!. but now i have a question, if i want to get twrp again and i dont plan to flash a custom rom like it says in the guide, how do i get twrp to recognize my storage? and do you flash twrp before installing an os or after because ive done it after installing the os.
Click to expand...
Click to collapse
yeah so it seems like the issue isnt with changing the file system or anything because i installed twrp again and tried rebooting and i got the same bootloop issue, but if i flash a rom then ill lose twrp like it happened last time so i dont understand what im supposed to do
you have to format data in twrp otherwise it won't see your storage folder.
once formatted reboot to twrp then reboot to system, it should reboot to stock rom and the set up pages.
beanbean50 said:
you have to format data in twrp otherwise it won't see your storage folder.
once formatted reboot to twrp then reboot to system, it should reboot to stock rom and the set up pages.
Click to expand...
Click to collapse
wipe>format data>type yes>reboot to recovery. i did that and still cant reboot to system bootloop issue persists
yes you did it correctly this time, is there anyway to undo your 'filesystem to ext2 then ext4'?
or maybe you have to flash the custom kernel to get it all up and running again
beanbean50 said:
or maybe you have to flash the custom kernel to get it all up and running again
Click to expand...
Click to collapse
how do i do that? the kernel folder in the guide doesnt have any tar or .img file to flash
floppen22 said:
how do i do that? the kernel folder in the guide doesnt have any tar or .img file to flash
Click to expand...
Click to collapse
it's a zip file so it should flash in twrp
beanbean50 said:
it's a zip file so it should flash in twrp
Click to expand...
Click to collapse
yes i was able to boot into my phone after flashing the kernel. thank you so much.
Try a different version of TWRP I remember this happened to me before and I installed a different version and it was fine