I might not have got enough sleep last night, so please excuse me if I missed this out right in the how to.. but I was up to 5 am last night putting Preware on my HP Touchpad and CM 2.1. The installing of Apps and playing in both ensued into the wee hours..
In my excitment I woke the wife.. and not thinking straight I thought I could get to the CWM via the same method as I used to building it. I pressed Vol Up and Power and it went back to USB bootie mode, and I couldnt get it out of that mode.. eventually I just reran the Acme installer. thewife went back to bed unimpressed.
So here is my question, I know how to boot from CM how via reboot into recovery mode, and then I can choose to boot to WebOS or CM. But from WebOS, how do I boot into Android? Or how do boot back into the Clock work menu so I can choose again ?
Thanks,
SorrowsTyr
.
There is an application in Preware called Cyboot that allows for what you want.
Or
You can install the patch that adds new buttons to the drop down power menu
Or
You can go to "Device Info" > "Reset Options" > Reboot
Yes! That us exactly what I want. Installed cyboot and Adv. Reset Options.
Thanjs!
Sent from my LG-P999 using XDA App
sorry for hijacking the thread,
but if i am stuck on the white usb screen, how do i get out of it?
Like for my phone, if i am in download mode i just take out the battery and restart my phone...but i dont we can remove battery in the Touchpad....
If you followed the instructions in the Dev section you should have installed Moboot, which give you the option to choose your OS when booting/rebooting.
viny2cool said:
sorry for hijacking the thread,
but if i am stuck on the white usb screen, how do i get out of it?
Like for my phone, if i am in download mode i just take out the battery and restart my phone...but i dont we can remove battery in the Touchpad....
Click to expand...
Click to collapse
Hold down power and home for about 30 sec.
Related
YUP. I "soft bricked" my t-mobile galaxy s (vibrant here in the us) or so I hope. The phone was rooted via z4 on the latest android t959uvji6 from t-mobile.
How did i do it? Brick my phone that is...
The 3d gallery was pissing me off by picking up everything on the phone. I tried clearing the default setting via the manage app but nothing changed so I decided to delete it. First backing up the apk and odex file from the system folder with titanium backup then deleted them from the system folder via root explorer. Rebooted the phone, pulled out the battery, waited for 30 seconds or so, popped in the battery and booted up the phone w/o any issues.
I tried installing the backup 3d gallery apk file and got the "app not installed" error on numerous attempts. Then tried simply copying it over again with ti backup and nothing happens. Gave up and said the heck with and went the factory restore route, got all the relevant apps installed and tried reinstalling the 3d gallery apk but resulting in the same "app not installed" error prompt. So I again copied over the apk and odex file into the system folder. Rebooted and nothing... phone does not boot into the home screen.
At this point here is what the phone is able to do.
It will boot up and display the default galaxy s animation, goes through it's array of colors then comes to a stop at all white letters then the screen goes blank and nothing happens - zip. nadda. i left it on for 12hrs like that - blank screen w/all the hard keys lit up.
What i did notice was win7x64 recognizes the phone after it gets into the blank screen of death as mass storage units.
So far i've tried booting into the recovery screen via the three button method and none of them works.
Did the karma-volume up-home-power twist - nothing
Did the karma-volume down-home-power roll - nothing
Did the karma-volume up and down-power jiggy - nothing
I tried the key combos for about 2hrs without any success then jumped into adb. After reading for a bit I realized that the phone was still rooted and the debug mode was enabled the last time i shutdown the phone (good'ol ti-backup)
For a while there adb did not recognize the phone at all but with an odd power cycling while spamming "adb reboot recovery" it was able to finally nab hold of the phone and jump into the recovery console. At first I thought it was pure luck so unplugged everything and tried it again - works every time if i did the odd out of sequence power cycle while spamming the adb console with "adb reboot recovery".
In the reboot recovery - deleted the user data and did the restore.
Here's where I think I really screwed up - now the phone is no longer in debug mode.
Long story short - is there a way to get into the recovery screen w/o debug mode on?
**quickly pulls on flack jacket**
but seriously any suggestions would be great
Wrong section bro. You probably won't get an answer here.
To answer your question. Yes, Remove Battery, Plug your phone to USB, Press and hold the volume down and the power button Put the batter back on. This should get you into download mode. Use ODIN to restore.
the usb jig trick did the work - now i have two phones!!!! (bought the nexus s yesterday) lol
Time to ODIN.
To access Download mode.
Unplug. press volume up and down togheter, and connect USB. VOILA!
If ODIN does not recognize it, plug and unplug again
chichu_9 said:
To answer your question. Yes, Remove Battery, Plug your phone to USB, Press and hold the volume down and the power button Put the batter back on. This should get you into download mode. Use ODIN to restore.
Click to expand...
Click to collapse
no!
Why the hell are people giving others ideas on how to get into download when their doing it wrong.
its JUST THE VOLUME BUTTONS, NOT THE POWER BUTTON ALONG WITH IT.
volume + power = Recovery, which in this case you probably cant get into
Volume - Power = Download mode, which everyone can get into unless if they somehow hard bricked, if its possible.
SO i installed android on my friends touchpad. Every went off without a hitch. I rebooted into recovery to flash a new rom and without thinking, i forgot that His home button isnt working. SO now im in recovery and i cant get out. I can only move up and down. The power button only goes back so i cant use it to choose "reboot"
ANy suggestion on getting this thing out of recovery?
Tama
wait for the battery to die?
Plug it into ur PC .. and do adb shell reboot
Sent from my Touchpad using xda premium
I just let the battery die on it. Got it back on.
Its kind if useless at some points. Like i cant use the dual boot option to pick an OS cause i cant press enter.
If almost the power button was set as an enter button then we would be in business.
Thanks for the tip guys.
PS: I couldnt use the ADB command as it wouldnt pick up the device when i inquired for devices.
Tama
My Amaze 4G won't turn on...
So this is what has happened:
- I rooted my phone following the guide on this forum and installed recovery successfully
- I then flashed BeastMod 2.3.0
- Wiped out everything, then I tried to turn on my phone it would be stuck on the HTC screen when you first turn the phone on. (only thing that was able to be booted was the bootloader and recovery)
- I was like CRAP! What did I forget?! Then I was like I think I read something about kernel... I was like crap...
- I took the SD card plugged it into my MyTouch 3G Slide and downloaded BeastMod 1.3 (I think, the one without needing a kernel).
- I then proceeded to install it through Recovery. It installed.
- To my amazement, it worked I was like YESSSS.
- Then I proceeded to install the Faux Kernel v007 and then BeastMod 2.30
- IT WORKED, I got to witness the lockscreen of the beastly BeastMod 2.30!!! I was like this is amazing. Then I was like I think it said a full wipe.
- So I went back into the recovery. I wiped/formated everything it let my format/wipe. I was like clean install FTW. (I don't know if I should've)
- To my dismay, when I rebooted it. ONCE AGAIN THE HTC SCREEN ARGHHHH. So I tried factory resetting it (which I don't know whether or not it does bring me back to stock YIKES...)
- Then I was like its late at night, I should go to sleep. I took out the battery. Put it back in. Plug it into the wall charger and went to sleep. I thought I would fix this problem tomorrow.
- Now when I woke up a few hours ago... my phone is not turning on. It was clearly plugged in and everything to the wall charger. Orange LED light on when I plugged it in. I searched this up on Google to no success in solving this problem.
Currently while writing this post I have taken my battery off for 10 minutes to see if it resets the phone's battery stats, etc.
I have some experience of knowing how to root and flash. I have flashed a MyTouch 3G slide (a bunch of times), a G2, and a G2x. The G2x experienced the same not turning on problem, but it was fixed somehow after a while.
The ultimate question is... how do I fix my Amaze 4G by getting it to turn back on and successfully flashing the latest BeastMod (which I have heard has beastly battery life) with a 100% clean install?
Oh and when I have it plugged into my computer. It keeps having that beep (repeatedly in an interval of 5 - 7 seconds) when you first plug the usb in to the computer.
EDIT (QUICK UPDATE): My phone is back on. I frantically pressed the power button like no tomorrow and it finally turned on, but its still stuck on the HTC screen. Right now I'll try reflashing BeastMod 2.30. Hopefully it works. :/
EDIT: ON BOOTLOADER, it says:
"battery voltage is too low
please change a battery."
bad battery already... the heck?
DarxMalFur said:
Oh and when I have it plugged into my computer. It keeps having that beep (repeatedly in an interval of 5 - 7 seconds) when you first plug the usb in to the computer.
EDIT (QUICK UPDATE): My phone is back on. I frantically pressed the power button like no tomorrow and it finally turned on, but its still stuck on the HTC screen. Right now I'll try reflashing BeastMod 2.30. Hopefully it works. :/
EDIT: ON BOOTLOADER, it says:
"battery voltage is too low
please change a battery."
bad battery already... the heck?
Click to expand...
Click to collapse
Get back into recovery and wipe battery stats. Should be fine afterwards.
Sent from my GT-P7510 using xda premium
Remember, if you can get into Recovery...you're OK!!!! Relax! It still sounds like you're shooting in the dark a bit (i.e. could have read up a little more before you took the leap), but...
1) Bad battery issue - really doubt it. It probably drained...why you might ask?
2) Which leads into the question of which Recovery did you install? Some of them apparently have "charging" issues. That might have contributed to the "battery voltage is too low please change a battery" message.
In any case, if you can charge the battery/swap with one of your friends with a compatible one (Sensation and Evo3D I think use the same battery), try that out. Or, try your luck at charging it some. Again, if you can get to Recovery, 99.99% of the time, you aren't screwed.
verkion
I always thought you have to wipe (cache, dalvik and factory reset) prior to flashing ROM because the ROM installs into the freshly wiped partitions.
Sent from my HTC Amaze 4G using XDA App
This is actually a very easy to fix issue.
You read that you needed to wipe after the phone was already on. You the proceeded and wiped/factory reset.
- After you do that, everything erases; therefore, you do not have a ROM installed in your phone anymore.
So the fix is:
1) Go into recovery
2) Wipe/factory reset (yes again, idk what you might have done)
3) Wipe cache
4) Advanced / wipe dalvik cache
5) Adcanced / wipe battery stats
5) Install .zip from SD card / choose .zip from SD card
6) Beastmod.zip (or whatever it might be called)
7) Restart the phone... it all works.
(You don't exactly have to do all those steps, but I would suggest you do to start your phone 100%% fresh for the new rom)
Enjoy!
- Xologist
xologist said:
This is actually a very easy to fix issue.
You read that you needed to wipe after the phone was already on. You the proceeded and wiped/factory reset.
- After you do that, everything erases; therefore, you do not have a ROM installed in your phone anymore.
So the fix is:
1) Go into recovery
2) Wipe/factory reset (yes again, idk what you might have done)
3) Wipe cache
4) Advanced / wipe dalvik cache
5) Adcanced / wipe battery stats
5) Install .zip from SD card / choose .zip from SD card
6) Beastmod.zip (or whatever it might be called)
7) Restart the phone... it all works.
(You don't exactly have to do all those steps, but I would suggest you do to start your phone 100%% fresh for the new rom)
Enjoy!
- Xologist
Click to expand...
Click to collapse
I tried all the instructions (except for flashing a new ROM, since I can't get the ROM to flash...) and it's still stuck on the HTC main page, when it first starts...
Help?
Download stock recovery and search for relock bootloader and search for stock ROM. Go to your hot boot and download stock recovery, after relock and put your stock ROM on your SD card. And the phone is going to boot on the factory (the same as you bought the phone).
william.laing said:
I tried all the instructions (except for flashing a new ROM, since I can't get the ROM to flash...) and it's still stuck on the HTC main page, when it first starts...
Help?
Click to expand...
Click to collapse
Just saying .. when i first flashed I also was scared on the htc screen but you actullay have to wait..
... Did u atleast wait like 2 to 3 mins... It takes time to load up the first time u install a mod..
---------- Post added at 11:59 PM ---------- Previous post was at 11:44 PM ----------
zab911 said:
Just saying .. when i first flashed I also was scared on the htc screen but you actullay have to wait..
... Did u atleast wait like 2 to 3 mins... It takes time to load up the first time u install a mod..
Click to expand...
Click to collapse
nvm I see u said u have flashed b4.. so Iam sure u waited long enough..
william.laing said:
I tried all the instructions (except for flashing a new ROM, since I can't get the ROM to flash...) and it's still stuck on the HTC main page, when it first starts...
Help?
Click to expand...
Click to collapse
This Happened to me..
I used command prompt and brought the device to the recovery mode and flashed the rom. Now the phone runs ICS and works like a charm.
You need to download android sdk for windows/mac or whatever OS you have on our computer and install it.
1. Download and copy a ROM or TWO on your microSD and put it back in your Amaze.
2. Open the Command Prompt.
3. Type adb devices and hit "Enter"
4. It should display HTC device
5. type adb reboot bootloader
6. Use the volume button to move to "recovery" and select it by pressing the power button.
7. Then select the install zip from SD card.
8. Select one of the ROM's from your microSD and once the install is Complete, hit the return arrow at the bottom of your phone's home screen and press power button to select "reboot phone now".
rahulntinku said:
This Happened to me..
I used command prompt and brought the device to the recovery mode and flashed the rom. Now the phone runs ICS and works like a charm.
You need to download android sdk for windows/mac or whatever OS you have on our computer and install it.
1. Download and copy a ROM or TWO on your microSD and put it back in your Amaze.
2. Open the Command Prompt.
3. Type adb devices and hit "Enter"
4. It should display HTC device
5. type adb reboot bootloader
6. Use the volume button to move to "recovery" and select it by pressing the power button.
7. Then select the install zip from SD card.
8. Select one of the ROM's from your microSD and once the install is Complete, hit the return arrow at the bottom of your phone's home screen and press power button to select "reboot phone now".
Click to expand...
Click to collapse
or you can just press volume down + power while turning the phone on.. and it goes into bootloader menu.
I think it's those 2 keys
VOLUME DOWN + POWER
uhg, i came across this thread after searching google. my amaze is down. i cant read the screen because it isnt back lit. i am using my co-workers iphone LED "flash-light" to be able to barely read it. i have done all of this:
1) Go into recovery
2) Wipe/factory reset (yes again, idk what you might have done)
3) Wipe cache
4) Advanced / wipe dalvik cache
5) Adcanced / wipe battery stats
5) Install .zip from SD card / choose .zip from SD card
6) install bullet proof rom zip
7) Restart the phone...
and when it restarted in launched with the HTZ logo, and then went black again.. I will have to wait till i get home to try another battery... let me know if anyone has any more suggestions.. i may need to try to download the stock rom and everything again? i hope my phone isnt FUBAR
he has 5.0.2.6 recovery flash my latest one 5.5.0.4 with working charge off
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
HI Everyone,
So here's what I did.
I installed clockworkmod recovery using rom manager (after unlocking and rooting) and then installed the touch recovery using the blob method.
then i booted into cwm touch recovery and was fiddling around when i touched "key test" in the advanced menu.
I got a message that debugging mode is on or something like that and 'press "back" to exit debugging mode"
It shows me a number based on what key I press or which direction i swipe etc. but i cant go "back" which means i'm stuck here!
now in my previous device (x10 mini pro) i just used to yank the battery out in case of screw ups like this. but i obviously cant do that in my prime. and i dont want to wait till the battery runs out.. prime has a gigantic battery it could be a full day till that happens!
Please...somebody... help!
EDIT: NVM Held power button +vol_down for a few seconds and it rebooted
Thank you so much. I thought I was going to have to wait for the battery to die.
rosshalz said:
HI Everyone,
So here's what I did.
I installed clockworkmod recovery using rom manager (after unlocking and rooting) and then installed the touch recovery using the blob method.
then i booted into cwm touch recovery and was fiddling around when i touched "key test" in the advanced menu.
I got a message that debugging mode is on or something like that and 'press "back" to exit debugging mode"
It shows me a number based on what key I press or which direction i swipe etc. but i cant go "back" which means i'm stuck here!
now in my previous device (x10 mini pro) i just used to yank the battery out in case of screw ups like this. but i obviously cant do that in my prime. and i dont want to wait till the battery runs out.. prime has a gigantic battery it could be a full day till that happens!
Please...somebody... help!
EDIT: NVM Held power button +vol_down for a few seconds and it rebooted
Click to expand...
Click to collapse
Just saying.. you should really install twrp instead of cwm... it will burn you at some point.... if you dont want to go the nvflash route with the modded bootloader.. message me cause I do have an older version that doesn't require it....
Gage_Hero said:
Just saying.. you should really install twrp instead of cwm... it will burn you at some point.... if you dont want to go the nvflash route with the modded bootloader.. message me cause I do have an older version that doesn't require it....
Click to expand...
Click to collapse
yup.. that's what I did, eventually instaled TWRP... after i had some issues with backups in CWM.. dont remember what never looked back since