This happened to me on the third day after I've got the ATRIX - so you could say I was still a bit of a newb on Moto Android stuff at that point.
I was using RomRacer's CWM recovery. When I went to school, I decided I'd wipe cache & dalvik & fix permissions until I put on the shoes. When I got out of the flat, it was all done. I could barely see anything on the screen, but I thought what the hell, I know how CWM looks like, I can navigate through it without too many problems.
I must have selected a line wrong, because I ended up formatting the external SD card. Well, I pressed on it, I selected an option (I didn't even realise what I was doing, ROFL), then... when I saw "formatting SD card", I was like "God, f*** me now". Battery pull, battery pull, BATTERY PULL.
After that, when I was booting the phone, instead of the M-logo with the DUAL CORE TECHNOLOGY text, I got #1 (see the first picture). After a few seconds, it would show #2 (see the second picture), and another few seconds after that, the boot animation of the ROM would appear.
As you can see, it shows "OS will boot in 5 seconds". In those 5 seconds, you can use the volume down key to navigate through those options (which are the options you get to choose when you normally boot the phone, say, to go to Recovery - only displayed in another way, since you have the M-logo boot screen, which I don't have, lol).
Option number 10 (Boot Android (No BP)) boots the OS, but without the baseband. Wi-Fi, Bluetooth work fine (didn't test GPS), but 2G/3G are offline; also, if I'd go in Settings -> About, under "Baseband version", it would show "Unknown" or "Unavailable".
Option number 15 (BP Tools), is enabled by default after 5 seconds, if you haven't selected another option. That turns on the BP (which I believe is the baseband), and the ROM boots after that.
If I wipe the partitions, it will show "No OS detected. RSD mode will activate in 5 seconds", or something like that.
Even though it says "Current choice is mode: RSD", after that, it is powering on the BP, and booting Linux... It isn't actually going into RSD mode. Unless I press a volume key, it doesn't change, and the phone boots normally.
-----
Notice the PwrReason: SW_AP_RESET text on the top side. It shows SW_AP_RESET because I used the Reboot function that my current ROM provides (Neutrino ROM). If I turn off the device and turn it back on (manual reboot, so-to-say, lol), PwrReason would be PWR_KEY_PRESS. If I turn off the phone and plug in the charger, it would show PwrReason: CHARGER.
If the OS freezes and the phone reboots, PwrReason is AP_KERNEL_PANIC.
-----
What do you think of this? What might have gone wrong?!
Anyways, this thing is awesome. Now it looks more like the way regular computers boot up (BIOS lines, etc.), which is more interesting to look at, instead of a shiny image which doesn't inform you of anything that your phone is doing RIGHT NOW.
-----
Some things I haven't stated. After I did that stupid thing in CWM, it was showing "No OS detected". I had to flash the ROM for it to properly boot up afterwards. Also, after that, the touchscreen was malfunctioning (the capacitive keys didn't work etc.), so I had to flash the PDS partition again, as well. But that's pretty much all I had to do.
I followed your link from the CM7 thread. It's just like turl said, you need a new logo.bin (boot logo). Here's a link to a thread in the Themes section that has it.
ghost_og said:
I followed your link from the CM7 thread. It's just like turl said, you need a new logo.bin (boot logo). Here's a link to a thread in the Themes section that has it.
Click to expand...
Click to collapse
I figured that was missing (a bit late, actually)... I just can't beleive how a simply "format external SD card" option from CWM can do such a thing... Format the PDS, boot animation and the ROM, without doing the purposed thing : FORMAT THE DANG SD. In a way, I'm happy it did that and not the thing it was supposed to do - I didn't had a backup of my SD, lol.
Well, thank you. Even though I kind of like the way my phone boots up now... I'd kind of like an image, too. It would be awesome to place some lines of that text in some corner of the animation, like PwrReason, for example... useful for when you wanna know why the phone was off when you thought it was on Anyway...
That is just smothered in awesome sauce. Is that an official how-to guide???
JdgM3NT4L said:
That is just smothered in awesome sauce. Is that an official how-to guide???
Click to expand...
Click to collapse
What are you talking about? That how to on making your own boot image?
lol, yep.
JdgM3NT4L said:
lol, yep.
Click to expand...
Click to collapse
Well, I don't know what you mean by "official", but that's a guide alright.
Related
Hello all. I'm a brand-noob (my phrase, thank you) here.
I have received a Verizon HTC Eris phone that boots to the red triangle with exclamation point (three droids on skateboards prior to the triangle screen). I have no information on what was done on this phone prior to my receiving it. I have read here that the three droids means that it has been rooted, and that the red triangle means a stock recovery is on it.
I can only "Up Volume + Power" to get this - "E:Can't open /cache/recovery/command". Other than that, I can't seem to get to anything else on the phone.
Now, upon connecting via usb to my computer (Windows 7), I can get Windows to recognize the "Android Phone", but not specifically an HTC Eris. I do not have HTC Sync installed. I have used ADB to root another phone (MyTouch), but this phone does not show up when I check for devices via "adb devices".
I am hoping someone can offer some simple steps that I can do to work towards fixing the phone. Thanks everyone for your time. !
This may help you:
http://forum.xda-developers.com/showthread.php?t=992916
Good luck.
Thanks for the reply phone_cell. I had already read/seen that post.
I cannot see any boot information at all, it shows the skateboarders, then the red triangle. The phone shows up on my computer, but only as an "android storage device". I'm not sure how I can check anything via my computer. I have installed PDAnet prior, and read that it should have installed the phone drivers. ? I installed HTCSync on a different computer and it doesn't see the phone.
If there is no way to fix this phone, then I understand. I would like to think that there are ways (standard methods ?) to check and/or re-install a phone (any phone) back from something like this. ? ...Thanks again for your time and expertise!
I was happy to try to help you. I recommend you send a PM to bftb0. If your Eris can be brought back to life, bftb0 will know what to do.
Bummer. bftb0 does not receive private messages, or at least not from me. Maybe someone could relay the forum post.
I am still digging and digging to try and figure something out. If I could get my computer to communicate properly with the phone, I'm sure I could re-install/fix the boot problem.
Anyone have ideas on how to install a usb device that's stuck in recovery?
As always, thanks thanks thanks. And thanks.
I made a post asking bftb0 to lend you a hand.
http://forum.xda-developers.com/showpost.php?p=15386610&postcount=33
Are you able to get it into fastboot mode? To do so, the phone needs to be completely off first...pulling the battery if needed. From there, first hold down the green send/call button then press and hold the red power/end button at the same time. Holding both should bring you to the fastboot screen which has three small skateboard andy's at the bottom and the word FASTBOOT highlighted in red. If you get there, post what the top two green lines say. Post #4 in the thread phone_cell gave shows an example of what you'll see. I would also try and follow bftb0's directions in post #5 about using the "Official" RUU utility to install usb drivers but make sure to stop before actually flashing anything to the phone. After that, download the fastboot tool and then with the phone connected through usb, see if the command "fastboot devices" lists your device ID.
Getting that far is promising and you can proceed with bftb0's directions in that thread to flash with HBOOT, load a recovery, hopefully eventually get a custom ROM flashed.
Hey MongooseHelix (great nick). Thanks for your reply.
No, the phone does not boot into fastboot, or anything else. There's plenty of resources here for all the different methods for booting and such. I've read hundreds of threads and pages. I've tried them all (and to success on other phones). It only gives me the recovery-stuck-ness.
The more I think about it, the more I think it has something to do with me not having this certain phone installed on my computer prior to receiving it. ? What would other people do to remedy something like that..? Find a working model to get the drivers working? Hmmm. Thanks and thanks again folks.
If you haven't already, how about installing the android-sdk(try the exe if on windows):
http://developer.android.com/sdk/index.html
Then run the SDK Manager.exe from the SDK directory. I'd download the latest SDK tools, SDK platform-tools, and the USB driver for Windows. Make sure to add the tools and platform-tools directories to your path...instructions at the end of Step 5:
http://developer.android.com/sdk/installing.html#sdkContents
With the phone on and connected through usb, see if running "adb devices" from the command prompt recognizes the Eris.
Yes, I had the android-sdk installed prior to receiving this phone. I did run it and update everything within it (per everything I researched online). But, the phone still doesn't show up via "adb devices". I feel like because the phone is stuck in recovery, it's not letting the computer do anything hardware-wise with it. ? Not sure.
Not sure what else to suggest. Without access to recovery, fastboot, or hboot along with not being able to connect through a comp, it unfortunately sounds like it might be hard-bricked. I'm certainly no expert at reviving an Eris so someone may know a way to to fix things...maybe bftb0 will come work his magic. Good luck and if I find or think of anything else I'll let you know.
The red triangle screen is indeed a splash screen for the stock recovery.
The next question is whether you are able to proceed beyond the "splash screen" and attempt to perform a "factory reset" procedure using the stock recovery menus.
There are two ways you get past the stock recovery splash screen, and it depends on which version of the stock recovery is installed on your phone have.
(1) press & hold Vol-Up+End simultaneously (with the "red triangle" splash screen showing)
or
(2) press the Home(soft-key)+End simultaneously (with the "red triangle" splash screen showing)
Do either of those cause the <2e> recovery menu to appear on the screen? If so, perform a "factory reset" using that menu, and THEN see if you can get alternate startup modes to occur (after powering off the phone before each trial):
End (only) => Does anything boot now?
VolDown+End => HBOOT
Send+End => FASTBOOT
VolUp+End => Recovery boot (red triangle screen again) **only works if HBOOT > 1.49.xxxx
Please do not say "I tried everything" in your reply. It is extremely non-specific, and conveys no information about what you actually attempted.
bftb0
Many thanks for the reply. !
With the recovery splash screen showing, upon holding "Volume Up + End (power)" I get = E:Can't open /cache/recovery/command Now, I am able to clear that message by pressing "Volume Up + End" again, however it just goes back to the recovery splash screen.
I held down Home (on the glass) + End (power) and nothing happened.
?? Any suggestions ?
Also... my reference to "tried them all" in my earlier post meant that I have tried just about every combination of simultaneous key pressing upon powering up (booting from no power) the phone. I am also familiar with the recovery menus on other phones - I have not seen it show up on this one (per my most recent post as well).
cjslugbug said:
I get = E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
That message is quite normal. However, what usually happens is that the (stock) recovery <2e> menus appear immediately after that message.
I guess this suggests that there is something wrong with the phone (hardware) or the recovery.
I'll give it some thought (check this thread every so often), but I don't see an immediate way out of your situation.
bftb0
Well, I certainly appreciate the replies. Thanks!
Does
VolDown+Send+End
do anything interesting - either from a phone off condition, or when the "can't open /cache/recovery/command" message is on the screen?
Was there a (properly formatted) SD card in the phone when you performed all the prior button-pressing experiments?
Booted with "Volume Down + Send + End" = same, straight to recovery splash screen.
I then "Volume Up + End" to get "e:can't open /cache...." and tried "Volume Down + Send + End" = no changes.
I have an sd card in it that I used to root a MyTouchSlide recently. It has ClockworkMod recovery on it (update.zip). I have done every procedure I've mentioned in this thread with and without the sd card in the phone.
I just reread the whole thread.
I understand that you tried all the standard button-press-startup methods, and the only thing you can get to work (partially) is the first part of the standard recovery boot. What you didn't say explicitly is, what exactly happens when the standard button-press operations fail:
- nothing at all (screen stays black, not a single LED blips, etc)? or,
- every start sequence results in the recovery splash screen? or,
- the three skating droids appear but the screen freezes that way? or,
- other?
Here is what you are up against:
The standard recovery does not start up an "adbd" daemon, so worrying about drivers is not likely to get you anywhere: under normal circumstances, "adb" simply doesn't work with a standard recovery.
There are two exceptions to this:
(1) The (leaked) HTC "Root ROM" does start an adbd daemon (but "adb shell" won't work)
(2) The Leak-V2 recovery had a race condition that allowed less than 20% of the folks who tried it to get an adbd daemon to persist. (Search for "tereg" root). It's a huge long shot.
Whether either of these apply to you is indeterminate, as we know neither the bootloader version that is on your phone, nor the version ofthe (damaged?) recovery on the phone.
One more question, and then some straws to grasp at:
- when you plug the phone into the charger, do you see the amber/green LED light up?
- repeat every one of the "standard-button-press" sequences, but make sure that before each start sequence, you pull the battery, press all buttons, wait 10 secs, and then reinsert the battery. Long shot, but what have you got to lose?
bftb0
- what exactly happens when the standard button-press operations fail:
The three skating droids appear (for a few seconds, as per a normal-type boot is beginning) but then the screen freezes to the recovery splash screen.
- when you plug the phone into the charger, do you see the amber/green LED light up?
Yes, I see the amber/green light. The light seems to operate as if it is charging normally.
I will try your 10 + second-battery-pull-button-combinations method here in a while.
Really appreciate the thoughts/help on the matter. !!!
Recently i flashed the CM9 rom onto my Droid X2. Followed the instructions and everything installed correctly. Since it has been a couple of days and I have installed all my programs and got everything where i wanted it, i wanted to make a backup.
Soon i discovered that I didnt have System Recovery installed. SO i began looking into my SD card and i have two files,MOTODX2_Bootstrap_signed.apk. So i decided to install it, everything went fine but now my phone is stuck in a boot loop. It wont even boot into CM9.
Is there another BSR that i should be flashing instead of this one. Maybe the ReRecovery one? i know theres a [patched] BSR to install but i gave me the same problems.
Thanks EHB
Hi, for Cyanogenmod9 use the CM7 PATCHED BSR. It works just fine for me everyday. I'm kind of addicted to flashing ROMs for some reason and usually am on different ones multiple times a day. Always in BSR either restoring or backing up. The patched BSR for CM7 works just fine for me. For reference, in the app drawer it should say "CM7 System Recovery" not just System Recovery.
I'm not sure if it has been looked into by dev's yet or not, but the day CM9 was released I actually did flash the CM7 ReRecovery zip and I was able to boot to BSR from a powered off state just by plugging in. I wasn't sure if it was okay to use, so I installed a fresh CM9 without it. I don't know if this is 100% safe or if there would be any issues from using the ReRecovery zip. I would recommend just installing the patched CM7 apk and trying to use that.
Here's the link to the patched CM7 Recovery. Pulled straight from the CM7 thread
http://www.mediafire.com/?pzz4413k6wggcao
***^That BSR is an application. You download, install and run it on your phone. The ReRecovery is a flashable zip you can install once already inside of BSR allowing you to get into custom recovery say for example, if you're boot looping. ***
================================================
If you're still having bootloop issues, try this;
-Grab your ECOMOTO charger, plug into A/C power, pull battery, replace & plug into wall.
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
-When you see the battery charging icon, unplug your phone and pull your battery.
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
This will take you to a screen that shows a picture of an android next to a triangle with an exclamation mark (!) inside of it.
-From that screen press both the VOLUME UP and VOLUME DOWN keys at the same time.
If you made it this far, you're now in the stock android recovery. Using the volume buttons, key down to Wipe Cache Partition then press the power button to select. You will be taken to a confirmation screen. Key down and select Yes. Wait for it to complete. After you wipe the cache try rebooting back into CM9. This will take slightly longer than usual as your cache has to rebuild itself. If you can boot back up successfully, click the link above. Download the patched CM7 Bootstrap Recovery and install it. If you don't know what to do from there, open the application "CM7 System Recovery" and click "Install Recovery" -- You will now be prompted to grant or deny it superuser permissions. Allow them. You will receive a message saying the install was a success! Click OK. Now plug your phone back into the wall outlet and hit "Recovery Mode" and your phone will boot into BSR! From there just go to backup and save it to your external SD card. You can find your backups later via the file explorer of your choice under /mnt/sdcard/clockworkmod/backup. Note: You can rename the file so you know which ROM is which, just don't add spaces to the file name or it will ruin your backup and you will not be able to restore it. NO SPACES!!!
FYI you will still see the Motorola logo immediately after it turns back on. It takes a minute or two to boot into custom recovery.
I've been through a lot of trial and error with the X2 and these steps have helped me plenty of times. Hopefully they do the same for you....Good luck.
Cyanogenmod all day
Thanks for the information.
I knew basically everything you said except for the "wipe cache partition". Why is this necessary? I know that it doesn't delete personal information but what does it wipe/delete?
Im going wait to do this tomorrow - my day off. Im just worried that its going do the same thing and ill have to reflash and start all over again.
Thanks again EHB
Wiping the cache partition clears any/all application data and common app components. It does not wipe apps themselves, rather the files that the app generates when used.
Wiping it is necessary because when core system components are changed, the resources used by the apps also (could) change. Having stale app data after a system change or tweak can cause problems, which is why it is best to clear it. It gets rebuilt as apps are used.
RoyJ said:
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
Click to expand...
Click to collapse
I'm afraid I'm in the same boat and am going through these steps to hopefully get back on the right track. When you say the battery charging icon can take several minutes... are you suggesting 3-5 minutes, or up to 30 minutes? Because... I'm at about 35 minutes right now and am getting pretty nervous.
just skip to this part, if you can
remove charger and battery
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
Click to expand...
Click to collapse
Patched BSR, please help!!
RoyJ said:
Hi, for Cyanogenmod9 use the CM7 PATCHED BSR. It works just fine for me everyday. I'm kind of addicted to flashing ROMs for some reason and usually am on different ones multiple times a day. Always in BSR either restoring or backing up. The patched BSR for CM7 works just fine for me. For reference, in the app drawer it should say "CM7 System Recovery" not just System Recovery.
I'm not sure if it has been looked into by dev's yet or not, but the day CM9 was released I actually did flash the CM7 ReRecovery zip and I was able to boot to BSR from a powered off state just by plugging in. I wasn't sure if it was okay to use, so I installed a fresh CM9 without it. I don't know if this is 100% safe or if there would be any issues from using the ReRecovery zip. I would recommend just installing the patched CM7 apk and trying to use that.
***^That BSR is an application. You download, install and run it on your phone. The ReRecovery is a flashable zip you can install once already inside of BSR allowing you to get into custom recovery say for example, if you're boot looping. ***
================================================
If you're still having bootloop issues, try this;
-Grab your ECOMOTO charger, plug into A/C power, pull battery, replace & plug into wall.
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
-When you see the battery charging icon, unplug your phone and pull your battery.
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
This will take you to a screen that shows a picture of an android next to a triangle with an exclamation mark (!) inside of it.
-From that screen press both the VOLUME UP and VOLUME DOWN keys at the same time.
If you made it this far, you're now in the stock android recovery. Using the volume buttons, key down to Wipe Cache Partition then press the power button to select. You will be taken to a confirmation screen. Key down and select Yes. Wait for it to complete. After you wipe the cache try rebooting back into CM9. This will take slightly longer than usual as your cache has to rebuild itself. If you can boot back up successfully, click the link above. Download the patched CM7 Bootstrap Recovery and install it. If you don't know what to do from there, open the application "CM7 System Recovery" and click "Install Recovery" -- You will now be prompted to grant or deny it superuser permissions. Allow them. You will receive a message saying the install was a success! Click OK. Now plug your phone back into the wall outlet and hit "Recovery Mode" and your phone will boot into BSR! From there just go to backup and save it to your external SD card. You can find your backups later via the file explorer of your choice under /mnt/sdcard/clockworkmod/backup. Note: You can rename the file so you know which ROM is which, just don't add spaces to the file name or it will ruin your backup and you will not be able to restore it. NO SPACES!!!
FYI you will still see the Motorola logo immediately after it turns back on. It takes a minute or two to boot into custom recovery.
I've been through a lot of trial and error with the X2 and these steps have helped me plenty of times. Hopefully they do the same for you....Good luck.
Cyanogenmod all day
Click to expand...
Click to collapse
I am having a similar but different problem with the patched BSR. I had it running fine while using CM9 on my Droid X2, but now I am running MIUI, and when I install and attempt to get into the custom recovery, it seems like it attempts to load it, but does not. What I get is a jumbled screen that has the colors of the custom recovery, so I can tell it is attempting to come up, but something is going wrong. It shows that jumbled screen for a few seconds, then goes black and eventually just shuts down. I have tried EVERYTHING I can think of to fix this. I have tried a fresh download of the patched BSR, and even did a fresh SBF and reinstall of MIUI, but nothing fixes it. Any advice you have would be greatly appreciated. Thanks!
I would re flash sbf
if you have been using ezSBF
use rsd lite, vise versa, or try a different sbf version like 2.3.3 and take ota update
or see if someone could upload a nandroid backup
Sent from my MB870 using xda premium
The odd thing is, if I restore to CM7 or CM9, then the patched BSR will work again. It seems it only goes bad with MIUI. Could the ROM somehow affect the BSR installation and/or function? I wouldn't think this is the case, as other are using the patched BSR with MIUI without trouble.
Sent from my MB870 using xda app-developers app
Hello,
about 2 hours ago I decided that I would unlock my device (before that I read maximum informations that I could). Unlocking went fine and I also installed TWRP 2.1.3 (through ViperMod). So far so good.
Then I made backup in TWRP in case something goes wrong. I was going to try AOKP v40 so I downloaded it via goo manager and then I flashed it in TWRP Install option (and also installed gapps) and wiped cache. Device rebooted and I was stuck at AOKP boot animation for about 15 minutes when I decided to recover back. So I rebooted, restored and rebooted.
Now I'm stuck at first boot logo (eee pad). When I try to do VolDown+Power to get into recovery it doesn't ask for VolUp, but goes straight to selection of Wipe or USB. When I select fastboot or wait 10 secs device frozes. (I haven't tried wipe, just in case it would be needed to unbrick).
I read thread about unbricking (http://forum.xda-developers.com/showthread.php?t=1514088) and to me it seems like option 3, but I don't see recovery option.
In device manager I have 'ASUS Fastboot Interface'.
Here's video how it looks like: http://www.youtube.com/watch?v=7BGd1PIVbn8
Please please could anyone help me?
Btw: Is there any chance to shut down? Holding power button just resets, so does pinhole... :/
qery said:
Hello,
about 2 hours ago I decided that I would unlock my device (before that I read maximum informations that I could). Unlocking went fine and I also installed TWRP 2.1.3 (through ViperMod). So far so good.
Then I made backup in TWRP in case something goes wrong. I was going to try AOKP v40 so I downloaded it via goo manager and then I flashed it in TWRP Install option (and also installed gapps) and wiped cache. Device rebooted and I was stuck at AOKP boot animation for about 15 minutes when I decided to recover back. So I rebooted, restored and rebooted.
Now I'm stuck at first boot logo (eee pad). When I try to do VolUp+Power to get into recovery it doesn't ask for VolUp, but goes straight to selection of Wipe or USB. When I select fastboot or wait 10 secs device frozes. (I haven't tried wipe, just in case it would be needed to unbrick).
I read thread about unbricking (http://forum.xda-developers.com/showthread.php?t=1514088) and to me it seems like option 3, but I don't see recovery option.
In device manager I have 'ASUS Fastboot Interface'.
Here's video how it looks like: http://www.youtube.com/watch?v=7BGd1PIVbn8
Please please could anyone help me?
Btw: Is there any chance to shut down? Holding power button just resets, so does pinhole... :/
Click to expand...
Click to collapse
Shouldn't it be volume and power down to get to the option to press volume up for recovery?
Are you familiar with fastboot flashing recoveries? Either way that will be helpful info for us to have.
Most important thing, this is no big deal at all, it's really a minor issue. Don't let yourself get stressed out over it, the community will make sure you're good to go.
CharliesTheMan said:
Shouldn't it be volume and power down to get to the option to press volume up for recovery?
Click to expand...
Click to collapse
Yes sure my bad, it was typo (I was kinda sleepy and tired when I was writing)
CharliesTheMan said:
Are you familiar with fastboot flashing recoveries? Either way that will be helpful info for us to have.
Click to expand...
Click to collapse
Nope, this is my first time flashing.
You say you dont see the VOL_UP message. From the video it looks like it is there. You just did not press it within 5 seconds.
Once it comes up, let go of the buttons ;p
leppie said:
You say you dont see the VOL_UP message. From the video it looks like it is there. You just did not press it within 5 seconds.
Once it comes up, let go of the buttons ;p
Click to expand...
Click to collapse
nope it's not there. I was holding voldown from the start and as soon as it should say 'press volup for recovery' (time 0:04) it jumps (skips 5 seconds of waiting) directly to wipe/fastboot options (wipe is one that is selected on video)
Ok so I managed to fix my problem thanks to hanzo001's thread (http://forum.xda-developers.com/showthread.php?t=1662158). Someone should add this instructions to the [HOW-TO] Unbrick your Transformer Prime (or not) thread.
qery said:
Ok so I managed to fix my problem thanks to hanzo001's thread (http://forum.xda-developers.com/showthread.php?t=1662158). Someone should add this instructions to the [HOW-TO] Unbrick your Transformer Prime (or not) thread.
Click to expand...
Click to collapse
glad it's fixed, im sure hanzo001 will appriciate a simple thanks on his thread too..and let others know it worked for you
Hi All,
So today I was messing around with a Led Zeppelin custom TTFont, I first tried installing it and changing the permissions and owner/group and rebooted. Rebooted fine, but no option in Display/Fonts to actually change it to that type. No biggie, I just edited the name to match Coffee font Regular, backed up the original of course and rebooted.
Now I am stuck in a boot loop. But here is what is weird (to me).
I go into the LG boot options screen (Hold down Power and Volume Down until LG screen appears, quickly release then reapply those two button combinations until screen appears) and cleared cache, no biggie, still boot looping. Again I go into the Boot options and this time I choose safe mode, still boot looping.
Now I am frustrated because I think I have probably load the .tot file and start over all my customizations, but before I do I restart the phone one or two times, hold the volume up while its bootlooping, then down, then all 3, then both volumes, basically just playing with different key presses while I watch the soccer match. No biggie and I have nothing to really lose at this point...
I pull the battery, hold the volume up key so I can start getting into download mode then all the sudden I feel the phone vibrate like it turned on but I get no screen, just black. So I plug in the USB thinking its waiting for me to start up the download mode since I never turned the phone on myself and all the sudden my windows machine which I have the USB plugged into shows the SDCard.... I double tap my screen and bam, phone is at my desktop never accessing the lock screen or showing the VZW logo.
So like the complete tool I am, I go back into /system/fonts and notice that I had renamed the Kashmir.TTF to the right file name (can't remember the exact name of the coffee font, but it was correct) but left the TTF in caps. I know from my linux days that things are case sensitive so I edit the file to "whateveritwas.ttf" check permissions, check owner and group again, and reboot. Now I am stuck in bootloop again and was wondering if anyone knows if I just hit some magical keystroke I didn't know about that bypasses the VZW file check @ boot which allowed the system to ignore the fact /system/fonts didn't match? Does the VZW G3 even do a file size check at launch like that? Could I have just let it sit there long enough and "thought" I pulled the battery but didn't and just after a while it worked itself out?
Anyway, I don't mind re-flashing that isn't the point of the post. I am more curious how I got it to boot without the VZW logo, bypassing my lock screen and allowing me to get to my phone without using safe mode. Any thoughts? If I can't figure it out in an hour or so I am just going to re-flash the tot file, but I wanted to mess with this for my own curiosity and wondered if anyone else has encountered this before I wipe my phone and start over.
Koroz said:
Hi All,
So today I was messing around with a Led Zeppelin custom TTFont, I first tried installing it and changing the permissions and owner/group and rebooted. Rebooted fine, but no option in Display/Fonts to actually change it to that type. No biggie, I just edited the name to match Coffee font Regular, backed up the original of course and rebooted.
Now I am stuck in a boot loop. But here is what is weird (to me).
I go into the LG boot options screen (Hold down Power and Volume Down until LG screen appears, quickly release then reapply those two button combinations until screen appears) and cleared cache, no biggie, still boot looping. Again I go into the Boot options and this time I choose safe mode, still boot looping.
Now I am frustrated because I think I have probably load the .tot file and start over all my customizations, but before I do I restart the phone one or two times, hold the volume up while its bootlooping, then down, then all 3, then both volumes, basically just playing with different key presses while I watch the soccer match. No biggie and I have nothing to really lose at this point...
I pull the battery, hold the volume up key so I can start getting into download mode then all the sudden I feel the phone vibrate like it turned on but I get no screen, just black. So I plug in the USB thinking its waiting for me to start up the download mode since I never turned the phone on myself and all the sudden my windows machine which I have the USB plugged into shows the SDCard.... I double tap my screen and bam, phone is at my desktop never accessing the lock screen or showing the VZW logo.
So like the complete tool I am, I go back into /system/fonts and notice that I had renamed the Kashmir.TTF to the right file name (can't remember the exact name of the coffee font, but it was correct) but left the TTF in caps. I know from my linux days that things are case sensitive so I edit the file to "whateveritwas.ttf" check permissions, check owner and group again, and reboot. Now I am stuck in bootloop again and was wondering if anyone knows if I just hit some magical keystroke I didn't know about that bypasses the VZW file check @ boot which allowed the system to ignore the fact /system/fonts didn't match? Does the VZW G3 even do a file size check at launch like that? Could I have just let it sit there long enough and "thought" I pulled the battery but didn't and just after a while it worked itself out?
Anyway, I don't mind re-flashing that isn't the point of the post. I am more curious how I got it to boot without the VZW logo, bypassing my lock screen and allowing me to get to my phone without using safe mode. Any thoughts? If I can't figure it out in an hour or so I am just going to re-flash the tot file, but I wanted to mess with this for my own curiosity and wondered if anyone else has encountered this before I wipe my phone and start over.
Click to expand...
Click to collapse
Interesting. It sounds like you may have found a button combination that allows full root access like custom recoveries regardless of minor changes to the integrity of the /system directory. This could be a major step towards a bootloader unlock or more likely a Loki exploit.
acparker18 said:
Interesting. It sounds like you may have found a button combination that allows full root access like custom recoveries regardless of minor changes to the integrity of the /system directory. This could be a major step towards a bootloader unlock or more likely a Loki exploit.
Click to expand...
Click to collapse
I know for a fact I bypassed VZW Logo and the lock screen 100% (or they just never displayed as the screen was black the whole time), the part I wasn't paying enough attention to was how it happened and I am really kinda irritated at it because its something I am usually paying attention to. I wish I had the old input recorders we had from Sony, anything we would key press during development would be recorded and when bugs would happen we could run them back.
I played with it probably for another 4 hours trying to recreate the situation again and it never happened for me. I then re-ran the tot file and put the Android L fonts on to see if it was just the Kashmir font (Led Zeppelin font) being size mismatched with the one I replaced, but all of the file sizes were the same on this L pack and it got through the VZW check, yet caused all sorts of UI problems and crashed upon load to the system shell. With that causing the systemui to crash over and over I was unable to do anything so I re-flashed again. I was going to re-create the bootloop tonight and see if I can do it again, but I went to hempfest instead. /shrug I have priorities man!
How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.