Related
First of all I would like to say hi to everybody, this is my first post on this awesome forum I found just today. I would also like to say that I bought my first smartphone a few days ago(HTC Wildfire of course) and when browsing on the internet trying to find out stuff I could do with the new found device I found a lot of people reffering to something called 'rooting' and 'flashing' and 'ROMs' and that doing this enables your phone to have a lot more new functions and stuff like that.
Therefore I have some questions to ask you nice people, so here they are:
- What is 'rooting', 'flashing' and what are 'ROMs' in the first place?
- I found a lot of abbrevations when people described 'rooting' their phones which I did not understand so I'm kindly asking if anyone could please explain the process clearly? (is this the correct process? -> forum.xda-developers.com/showpost.php?p=7895908&postcount=127 , if it is what is the OTA update?)
- If someone could please explain the process of 'flashing' to me?
- Are there any recommendable 'ROMs' I could try?
I truly thank anyone who would be able to explain this to me and take their precious time to do so. I'm sorry if my questions seem silly but I'm extremely new to the smartphone android thing and therefore I don't understand everything.
Thank you again for your replies, ciroman
- What is 'rooting', 'flashing' and what are 'ROMs' in the first place?
Rooting = gives you/apps on the phone acess to root acount in android wich gives you acess to do things wich you can not do normally. read more about root and superuser(su) here: http://en.wikipedia.org/wiki/Superuser
ROM = is sort of the operating system wich most often comes in zip files and is possible to flash to the phone with a custom recovery. this often include apps and modifications wich is made of the person who makes the ROM. also includes superuser acess (root) not allways but often.
custom recovery = a recovery mode wich allows you to do backup of your current settings and evrything else you have on the phone. also makes it possible to flash ROMs wich you have saved on the SD-card
Flashing = this is when the recovery takes your zip file and exctract it to your phone. when this is done you have a new "operating system" on the phone
- I found a lot of abbrevations when people described 'rooting' their phones which I did not understand so I'm kindly asking if anyone could please explain the process clearly? (is this the correct process? -> forum.xda-developers.com/showpost.php?p=7895908&postcount=127 , if it is what is the OTA update?)
Yes this looks like the process of rooting/installing a recovery.
OTA = Over The Air
- If someone could please explain the process of 'flashing' to me?
wont explain this.. it should be explained somewhere else..
- Are there any recommendable 'ROMs' I could try?
There are only a few ROMs out at the moment..
The only one I can recomend for you rigth now is wildpuzzle ROM by danne_jo there is more ROMs out but I dont know how stable theese are.
Click to expand...
Click to collapse
I dont garantue that this info is 100% correct and anyone who feels like please correct me if im wrong.
I also take no responsibility for any damage made to your phone by following any of the above information.
Thank you so much for your quick explanation. I must say though that searching for how to flash and root this phone was quite painful for a newcomer like me-took me hours to find the first part and then some to find the second.
I hope following these two guides will get me there
shinelt said:
Prep
Before beginning the process, I would recommend doing the following to your phone:
(1) If you have the original unrevoked root installed, uninstall it by using "Menu", "Settings", "Applications", "Manage Applications" and scrolling to "Unrevoked" at the bottom. Tap it, click "Force Stop" at the bottom and then "Uninstall", "OK" to uninstall it. Then power off/on your phone just to be sure.
(2) If you haven't already installed the OTA 1.47 update, do it now: "Menu", "Settings", "System Updates", and "HTC software update" at the bottom, then click "Check Now" to get the 1.47 update. If you do this update, it takes up to 10 minutes so be patient and let the phone reboot (a few times) until it is done. Then once the update is done, power off/on one last time to get a clean start.
(3) Set your phone to "Charge Only": "Menu", "Settings", "Connect to PC", tap "Default connection type" and select "Charge Only".
(4) Enable USB debugging: "Menu", "Settings", "Applications", "Development", and put a check in "USB debugging".
The root process
(1) Go to Control Panel on your system and uninstall any "HTC" software such as "HTC Sync".
(2) Download the unrevoked3 install package: Go to
unrevoked3 recovery reflash tool, v3.0 and click "Download for Windows". Save the "Reflash-bundle.exe" file somewhere that you can find it on your system.
(3) Using Explorer, run the "Reflash-bundle.exe" file you just downloaded. It'll ask where to install it. Don't just accept the default: change the install location to a folder you can remember: it's just going to unzip some files there: it isn't really a software installer.
(4) Once the files have unzipped, go to the folder you chose in the above step. You should find an "hboot driver.htm" file in that folder: double click on that to open the html instructions on how to install the drivers. Follow the instructions in the html file starting with downloading the actual driver files at the very top. When you download those driver files and unzip those, those are the files (the folder) you'll point to in subsequent steps in those instructions. When done with the html instructions, you should have drivers installed and shouldn't have to come back to this step.
(5) At this point, if you needed to install the drivers, you are probably still sitting at a boot menu on your phone. UNPLUG the phone from USB and select "Fastboot" and then "Reboot" to reboot the phone to restart it. Before the next step, your phone should be on and booted up in its normal operating state (not some boot menu).
(6) If you are running anti-virus software, turn it OFF or disable it now.
(7) Now go to the folder where you unzipped the reflash bundle (step 3 above). In XP or older systems, just double click the "Reflash.exe" file. On Vista and Win7 systems, I'd recommend right clicking on "Reflash.exe" and selecting "Run as Administrator". While this may not be necessary, I know that some USB drivers get really mad if you try to access the USB port without admin privileges (sorry, I'm a coder so I run into that stuff and warn you so you don't have to) so I did it as a precaution.
(8) You should get a window with "Unrevoked 3" on it (on the computer of course). Just follow the instructions in smaller font below "Unrevoked 3" to finish rooting. Note that when it says "Waiting for device", it wants you to plug your phone into the computer via the USB cable. Note that it wants the wildfire to be fully booted normally (not in the Hboot or recovery menus). The prompts at this point are very specific so no need to repeat them. If all works as it is supposed to, the only thing you really have to do is scroll to an item on the phone and select it when instructed. The rest is automated and should result in a "Done" message. The whole thing at this point took maybe one minute so it isn't something you have to wait for or stare at for a long time so if something gets "stuck" for a while... there's likely a problem.
(9) Don't forget to turn your anti-virus software back ON.
Now, when I followed these steps on my Win7 x64 system, reflash.exe detected the phone and started working (we're in step 8 here) but about 4 messages into the process I got the "communications lost... try again" message that unrevoked refers to on today's Twitter. Some say that (contrary to step 1) installing HTC sync actually solves the problem. I didn't try that. After about 6 tries on my Win7 system and even pulling some "tricks" to try to pause reflash.exe at certain points, I gave up and simply booted my old XP laptop and repeated the above steps and it worked perfectly the first time. At the point of the failure, you hear the two tone usb-device-disconnected sound followed by a use-device-connected sound about 20 seconds later. Somewhere in between is where the "communications lost" message appears so it looks like some sort of USB ack/nack issue. Hopefully it'll be resolved soon. My best advice if you get that error: try a new machine. The XP machine that worked perfectly for me had never seen any HTC software. Maybe that helped. And maybe after I uninstalled the HTC software on my Win7 x64 system (the one that didn't work) I should have rebooted before continuing: I didn't because it didn't prompt for a restart and I couldn't find anything "HTC" running in task manager.
do wipe data/factory reset
put all files to sd from puzzle rom. ( go to partitions menu > mount usb storage)
(put those 01 , 10 , 52 ,300 , 400)
go to nandroid> backup
go to install zip from sdcard
and install files from 01 to 400.
go back and press reboot system now.
Click to expand...
Click to collapse
fireplayer said:
I'm just as n00b as you on this. But I'll help you out...
1. After using unrevoked once - reboot your Wildfire.
2. Go to first page on this thread that you read right now.
3. Download the things you want to flash - all links are in the 1st post. - put them on your SD-Card - start with flashing 0001_WildPuzzleROM_v2.zip first - to do this - download that file and save it - anywhere on your SD-card (somewhere you'll remember where you put it). Download and save all you want from 1st post on this thread - to your SD-card...do NOT open the zip files - just copy them to the SD-card.
4. Turn off your Wildfire
5. Turn on your Wildfire while holding Volume Down button - you have to have your SD-card with all the files you want - inside your phone now.
6. This get's you to the boot screen. Wait for HBOOT to say no image...blabla..
7. Push Volume Down to get to option "Recovery" - press Power button.
8. Phone will Reboot to a white HTC screen - and from there go to ClockworkMod Recovery screen - if you did everything correct.
9. Press Volume Down several times - until you get to option "nandroid"
10. Press the round button at the bottom of your Wildfire - the one you use to take pictures when using Camera functions, let's call it the Camera button.
11. You see "Backup". Press Camera button, and wait until it's done backing up your system. Do NOT turn off your phone! Wait until it's done. It will say Backup complete!
12. Next if you want. But only if you want - you don't have to - you can Wipe / Factory Reset your phone, saves a lot of ROM space and Memory. Phone WILL be slightly faster if you choose to do this - but all your programs and settings will be gone - Your choice.
IF you do NOT want to Factory Reset your phone, skip steps 12 & 13.
IF you want to do this then push Volume Down until you get to option "wipe data/factory re" (probably reset, but only show until re on my phone) and then press the Camera button.
13. As to make sure you really want to do this, you need to confirm... push Volume Down until you reach option "Yes -- delete all u" - then press Camera button and wait.
14. Now you can start flashing. Push Volume Down until you reach option "install zip from sdcard" Press Camera button.
15. Push Volume Down until you reach option "choose zip from sdcard". Press Camera button.
16. Find where you put the files you downloaded from post 1 on this thread. Choose 0001_WildPuzzleROM_v2.zip. Press Camera Button.
17. Push Volume Down until you reach option "Yes - Install 0001_W". Press Camera button. Wait for it to be done.
18. Repeat steps 14-17 with the other files you want to flash. IF you want to Flash files that are 0900 or higher. Reboot and change Wallpapers before you do.
To reboot Press Power button to go back and Press Camera button on option "reboot system now". Then repeat steps 5-7. If you need help changing wallpapers too let me know and I'll try to explain that too.
When done flashing the files you want. Reboot. And you're done.
First reboot after flashing Wild Puzzle Rom takes a very long time. Be patient.
I hope this guide made sense. If there's anything unclear let me know and I'll be happy to clarify. Thanks and Good Luck!
*EDIT* Just saw that someone else made a guide too, well at least there are people wanting to help us n00bs. Thanks. and I think both guides should work. Hopefully you'll make some sense of them *ENDS EDIT*
Click to expand...
Click to collapse
Thanks again!
I've had a Droid 3 for a little under a year now. For the past few months I was having an 'issue' where the phone would not vibrate when I got an SMS message. Apparently this is a known issue caused by installing a non-stock SMS app from the app-store. I took it to the Verizon store and the guy put in a request for a replacement phone. He knew I'd rooted it and just said to make sure I unroot it, uninstall the bootloader, and factory reset before sending it in. I did all 3 things however the reset didn't reset my custom boot animation so I figured I'd activate the phone real quick, reroot, change that, and unroot. I started the activation process and I get to the "Add Accounts" screen, added my Google account, and hit Done. It asks about location services, I hit "Next" and then com.motorola.setup crashes and I have to force close. If I hit the Home button it takes me right back to the "add accounts" screen and I'm stuck in that infinite loop. I can still receive texts and reply to them from the notifications menu, I can send and receive phone calls with voice commands, I can access the browser, but that's about it. I cannot get to the home screen and I cannot open the settings 'app'.
I brought it back to the Verizon store and they were baffled, told me that Verizon would probably charge me full retail for the replacement if I sent this once back, so I sent back the replacement phone and am stuck with this one now.
I think what caused this is that I had the 'Bloat Freezer' app installed and I had frozen a bunch of the default Verizon apps. I didn't unfreeze them before the factory reset and I have a feeling that's what's causing the issue. I had the idea to re-root the phone and install Bloat Freezer again from the Play store but the Play store isn't recognizing my Droid 3 anymore.
Any suggestions?
Factory reset is a deceiving term. It resets it to factory user data (none) and settings. It doesn't restore the system. What you need is an SBF to flash the entire phone to factory software, overwriting all partitions. First though, you must find which system you had. Since you didn't recently get this phone, did you accept an OTA update within the last month or so? If so, head over to the Dev area and download the stickied SBF file to return you from .906 to .890. If not, there is an SBF in the General area called Quick Unbrick or something like that.
http://www.youtube.com/watch?v=pcne9tFtBxY
Awesome! Thanks for the info. I'll give this a try when I get home from work tonight. Do you know if there's any way to tell what version I need without the settings app? Or perhaps if there's a way to forcibly open the Settings app?
If you've had your D3 for over a year and have not updated to .906, then you'll need .890. The .906 update is fairly recent (a couple months old I think?) so if you don't explicitly remember taking it, use .890.
Side note, check the rom you used before this happened. Check if it's based on .906 or .890.
Sent from my DROID3 using xda premium
JDiPierro said:
Awesome! Thanks for the info. I'll give this a try when I get home from work tonight. Do you know if there's any way to tell what version I need without the settings app? Or perhaps if there's a way to forcibly open the Settings app?
Click to expand...
Click to collapse
Do you know if you enabled USB debugging? (from settings->applictaions->development - check "USB debugging" on.) Many root apps require that.
Anyway, if you did, you can install the Android SDK's adb app and, from a command prompt, you can try to type the following command (with the phone on and cabled to the computer)
adb shell cat /system/build.prop | grep "version"
This should show you a bunch of lines, one of which will be "ro.build.version.full". The system version follows that text on the line - I have last month's OTA, so mine is Blur_Version.5.7.906.XT862.Verizon.en.US (so I have 5.7.906).
You can most easily get adb (for Windows) with instructions from here: http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
After you get those files unzipped in c:\android, you can start a command prompt by hitting start, type "cmd" and enter in the search box - this will start a black command prompt window. From there, enter the command cd \android and then enter the adb command I put up above.
I'm not sure it will work, but it should.
You can bypass the activation. Starting with the top left corner, press each corner in a clockwise rotation. This will bring your phone to the home screen so you can then find which version it's on.
doogald said:
Do you know if you enabled USB debugging? (from settings->applictaions->development - check "USB debugging" on.) Many root apps require that.
...
adb shell cat /system/build.prop | grep "version"
Click to expand...
Click to collapse
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
eww245 said:
You can bypass the activation. Starting with the top left corner, press each corner in a clockwise rotation. This will bring your phone to the home screen so you can then find which version it's on.
Click to expand...
Click to collapse
I had tried this but it still brought me straight to the "Add Accounts" screen, not to the home screen.
JDiPierro said:
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
I had tried this but it still brought me straight to the "Add Accounts" screen, not to the home screen.
Click to expand...
Click to collapse
Needs to be I. Charge only mode. On stock rom I believe its called none
Sent from my XT860 using xda premium
JDiPierro said:
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
Click to expand...
Click to collapse
You can grep: because you are running a shell command, I believe it is running on the phone, not on the windows computer.
(The grep is not all that critical, though, as I believe the version number line is one of the last lines displayed by that command.)
You can do an:
adb devices
before you run the shell command to verify that the computer and phone are communicating; it should return a line of characters that represents your phone, if it is connected.
hi folks,
I tried to disable Google search and now can't do anything on the phone.
I'm on CyanogenMod 11, Release 12 on Samsung Galaxy S Plus.
Kernel is K^Kernel, 416MB, ver 2.8.
I have the Google Now Launcher. I froze the Google Search package using Performance Control app since it was running 100% and consumed a lot of battery. My battery was going down drastically.
After closing it i cannot come back to the home screen.
It's black and nothing happens. Because I also cleared the recent app list I cannot go back into Performance control also.
Tried rebooting but it's stuck at the Cid logo. Rebooted into recovery cleared Cache/Dalvik and rebooted but after adjusting the apps its stuck at the Starting Apps screen.
Anyway to unfreeze the Google search package (or any frozen packages) thru recovery mode ?
Factory reset and restore your data. Theres no way to recover from a bootloop without massive work.
Gesendet von meinem Nexus 5 mit Tapatalk 2
Reflash the ROM may help.
Sent from my GT-I9001 using XDA Free mobile app
SOLVED !
Thanks folks, but luckily i was able to resolve this.
Even though the booting process seemed stuck the phone had started in the background. Maybe only the Cid image was running. Came to know because i sent a text to the phone and it beeped (with the Cid boot animation spinning). Then i made a call to the phone and the phone started ringing (Cid still on). After 10 seconds the calling screen was displayed.
I selected the message option (to go into any other screen). Then after disconnecting the call (from other phone) opened the QS panel, opened settings. Could not think of any idea to start Performance Control from there.
Then did the following.
> Checked package name for Performance Control thru Settings>Apps
> Tried to start it thru adb shell
adb shell am start -n com.brewcrewfoo.performance/com.brewcrewfoo.MainActivity
Got this error
Activity class {com.brewcrewfoo.performance/com.brewcrewfoo.MainActivity} does not exist
>Tried using only package name and got this error
Bad component name: com.brewcrewfoo.performance
>Finally using Eclipse created an app which opened the app using the below lines
Intent i;
PackageManager manager = getPackageManager();
try {
i = manager.getLaunchIntentForPackage("com.brewcrewfoo.performance");
if (i == null)
throw new PackageManager.NameNotFoundException();
i.addCategory(Intent.CATEGORY_LAUNCHER);
startActivity(i);
} catch (PackageManager.NameNotFoundException e) {
}
and installed and started the app.
Defrosted the Google search package from there and rebooted. Phone is alive and kicking now
anoopgkris said:
Thanks folks, but luckily i was able to resolve this.
Even though the booting process seemed stuck the phone had started in the background. Maybe only the Cid image was running. Came to know because i sent a text to the phone and it beeped (with the Cid boot animation spinning). Then i made a call to the phone and the phone started ringing (Cid still on). After 10 seconds the calling screen was displayed.
I selected the message option (to go into any other screen). Then after disconnecting the call (from other phone) opened the QS panel, opened settings. Could not think of any idea to start Performance Control from there.
Then did the following.
> Checked package name for Performance Control thru Settings>Apps
> Tried to start it thru adb shell
adb shell am start -n com.brewcrewfoo.performance/com.brewcrewfoo.MainActivity
Got this error
Activity class {com.brewcrewfoo.performance/com.brewcrewfoo.MainActivity} does not exist
>Tried using only package name and got this error
Bad component name: com.brewcrewfoo.performance
>Finally using Eclipse created an app which opened the app using the below lines
Intent i;
PackageManager manager = getPackageManager();
try {
i = manager.getLaunchIntentForPackage("com.brewcrewfoo.performance");
if (i == null)
throw new PackageManager.NameNotFoundException();
i.addCategory(Intent.CATEGORY_LAUNCHER);
startActivity(i);
} catch (PackageManager.NameNotFoundException e) {
}
and installed and started the app.
Defrosted the Google search package from there and rebooted. Phone is alive and kicking now
Click to expand...
Click to collapse
this is an perfect example of searching and working to find an answer
good job bro.
:good:
cool story bro
Was it not simpler to
go to recovery,
mount data,
lauch file manager inside recovery
and delete com.google.android.launcher-x.apk from data\app?
Then phone will revert to default Trebuchet launcher?!
And even simpler:
http://forum.xda-developers.com/showthread.php?p=55450190#post55450190
Power off >> Power on. After the SAMSUNG and ADC-Team logo's, menu and back keys will light up. Press and hold the menu key. You then see the android bootup animation (if you have it). Keep holding the menu key, it should finally boot and you will see a SAFE MODE overlay in the bottom-left corner.
bobdynlan said:
Was it not simpler to
go to recovery,
mount data,
lauch file manager inside recovery
and delete com.google.android.launcher-x.apk from data\app?
Then phone will revert to default Trebuchet launcher?!
And even simpler:
http://forum.xda-developers.com/showthread.php?p=55450190#post55450190
Power off >> Power on. After the SAMSUNG and ADC-Team logo's, menu and back keys will light up. Press and hold the menu key. You then see the android bootup animation (if you have it). Keep holding the menu key, it should finally boot and you will see a SAFE MODE overlay in the bottom-left corner.
Click to expand...
Click to collapse
Thanks man, i find the mount a bit tricky. Developing the app was pretty easy
But the SAFE mode is the best, thanks for putting it here, i'd searched for that and didnt find it.
On threads of lollipop flashing, There are quite lots of people asking about the black screen issue, but not really clear solution's out there.
These are the symptoms:
1. After booting, you get black screen with just upper notification bar and back button below
2. If you turn on the screen after a few second, you see the normal screen but only for a fraction of second.
3. You can hear some notification sound, but notification bar still says "no notification" (or something, well I'm not using english ui )
4. no response on cancel button
The reason is that, you've set a lock screen before, but your phone thinks you've never performed initial setup, so your phone gets confused and doesn't know what to do.
You can solve this by deleting /data/system/gesture.key (for gesture lock) or /data/system/password.key (for password lock) on recovery mode. Now your lock screen's gone, and you can normally boot your phone. If you're doing this on recovery, you should mount /data partition to locate the file.
There could be some other problems because your phone still thinks that you haven't initiallized it, so you should manually run initial setup by "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" on normal boot.
I hope this helps!
credit : @nighthammer http://forum.xda-developers.com/showpost.php?p=56715651&postcount=7664
FreakyTux said:
On threads of lollipop flashing, There are quite lots of people asking about the black screen issue, but not really clear solution's out there.
These are the symptoms:
1. After booting, you get black screen with just upper notification bar and back button below
2. If you turn on the screen after a few second, you see the normal screen but only for a fraction of second.
3. You can hear some notification sound, but notification bar still says "no notification" (or something, well I'm not using english ui )
4. no response on cancel button
The reason is that, you've set a lock screen before, but your phone thinks you've never performed initial setup, so your phone gets confused and doesn't know what to do.
You can solve this by deleting /data/system/gesture.key (for gesture lock) or /data/system/password.key (for password lock) on recovery mode.
after that, you should manually run initial setup by "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" on normal boot, to avoid several problems.
I hope this helps!
credit : @nighthammer http://forum.xda-developers.com/showpost.php?p=56715651&postcount=7664
Click to expand...
Click to collapse
This would be sweet except for some reason I hadn't accepted the adb authorization request on my device before I went all darkscreen duck.
wipe it is.
perdid0 said:
This would be sweet except for some reason I hadn't accepted the adb authorization request on my device before I went all darkscreen duck.
wipe it is.
Click to expand...
Click to collapse
You can delete the file via recovery, with file explorer or adb.
Since you have to unlock the bootloader to flash a factory image, you can flash a recovery image any time if you need one.
FreakyTux said:
You can delete the file via recovery, with file explorer or adb.
Since you have to unlock the bootloader to flash a factory image, you can flash a recovery image any time if you need one.
Click to expand...
Click to collapse
i cannot find that file in the location you specified. any other suggestions for locating it?!
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
actually.......i found it!!!! same place you said!!! deleted both .key files and rebooted.......the screen was gone allowing me to accept the adb autorization and run the setupwizard!!! woot woot.....thanks a billion!!
perdid0 said:
i cannot find that file in the location you specified. any other suggestions for locating it?!
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
actually.......i found it!!!! same place you said!!! deleted both .key files and rebooted.......the screen was gone allowing me to accept the adb autorization and run the setupwizard!!! woot woot.....thanks a billion!!
Click to expand...
Click to collapse
I'm glad that it helped!:highfive:
Hey man, thank you for your post !
I delated the file you said, but i didn't understand what should I do then ? Does it work if I don't do that adb setup (that I don't know what it is..)
Thank you for your help !
jordanl68 said:
Hey man, thank you for your post !
I delated the file you said, but i didn't understand what should I do then ? Does it work if I don't do that adb setup (that I don't know what it is..)
Thank you for your help !
Click to expand...
Click to collapse
Check the help threads for Nexus devices, there are "how-to" ADB & fastboot guides just everywhere. It works for all Nexus devices just the same way.
tetakpatalked from Nexus 7 flo
Please add this to your post. I had the black screen, but I never had a password set up. The black screen was happening because before I flashed an update, I had a system profile set to bypass the lockscreen. Once I put it back on the default profile (which you can do from the notification bar) everything was fine.
HELP! BLACK SCREEN ISSUE (Lollipop)
I flashed cm12 on my Galaxy Grand 2,but everytime i push the power button to unlock the screen,All i get is a black screen.I can hear touch sounds and responses and the harware buttons light up,but that's it.The black only goes on rebooting and I have to reboot my phone everytime I unlock it.Please Help?
Better Explanation
To make this guide appear better , and make it more easy doing etc etc..
Add this instead of a line method (well explained)
Download Aroma File Manager
Place it in your scdard directory
Boot in recovery
Mount Data
Go to Install and flash this zip..
Navigate to /data/system
Now delete password.key if a normal password or
gesture.key if a gesture
akastixx said:
Please add this to your post. I had the black screen, but I never had a password set up. The black screen was happening because before I flashed an update, I had a system profile set to bypass the lockscreen. Once I put it back on the default profile (which you can do from the notification bar) everything was fine.
Click to expand...
Click to collapse
I don't understand what you're saying. I've never seen "system profile set to bypass the lockscreen". could you tell me more specifically?
Aman_Arora said:
To make this guide appear better , and make it more easy doing etc etc..
Add this instead of a line method (well explained)
Download Aroma File Manager
Place it in your scdard directory
Boot in recovery
Mount Data
Go to Install and flash this zip..
Navigate to /data/system
Now delete password.key if a normal password or
gesture.key if a gesture
Click to expand...
Click to collapse
Thanks for your help. that's also a great workaround, but you know, it was nexus 5 that I was working on. If you were to place the file on the device, you would have to use adb anyway.
how can you do anything while screen is black? You just do not have any options displayed. I mean I am a layman
As everyone involved seems to be new to rooting, judging from the number of posts , tell them to READ READ READ . There is something called running before you can walk.
A clean install avoids the BS to begin with ...
Doesn't work with Nougat 7.1.1 (Dark ROM)
Does anyone know what if this solution works with Nougat 7.1.1 (Dark ROM)? I couldn't find the given files under /data/system, but I've found one as gatekeeper.password.key. However, if I delete it and reboot, I still get black screen.
Also, trying to run the setup wizard using ADB gives me a "SecurityException: Permission Denial: starting intent { ... } from null ( ... ) not exported from uid 10020".
Any ideas?
I have a 2011 NordicTrack 1750 with a 7" android tablet that is mechanically just fine. Recently an automatic update must have failed, because now it's stuck in a low level boot loop. Unlike the other threads I've found on the net, none of the iCON applications ever load. I only get to the blue generic android screen and no farther before it eventually reboots.
The symptom is that after the system boots it eventually throws the error "Process System is not responding" and whiter I select force quit or wait, the system eventually reboots.
I have both latest.apk file that I downloaded from a bit.ly link I found in a NordicTrack thread that I assume holds the latest icon application. I also have the $93 USB drive that I purchased from Icon fitness that has the if it-video.tgz and mp10.tgz files. I also have a mini-SD card formatted as FAT32.
I can boot the tablet into safe mode, but it eventually throws that error and then eventually reboots again.
I have been able to get to the Applications and Files menu selection and the iCon Fitness application is completely missing, though I do have the icon fitness keyboard. I think I have the icon application in the latest.apk file.
It seems like I need to do a full factory reset and reinstallation to fix the android problems and then reinstall the icon application. But, I don't know how to do that or if I have the right files for that.
Through various combinations of putting the files I have on the miniSD card and rebooting, I've seen it attempt to update the firmware, but eventually go back into the reboot loop. I also watched it try to verify the checksum of the iCON USB key only to eventually reboot and go back to the loop.
There is a thread that looks promising talking about hacking the elite 9500 pro, but I'm not a developer, so I can't post directly to that thread.
I think the tablet is a Hannstar JMV-7 (from a thread I found on the Net)
From the About screen here are some specifics:
Model: sec_smdkv210
Kernel: 2.6.32.9
Build: sec_smdkv 210-eng 2.2 FRF91 eng.android.20110301.153856 test-keys
Does anyone have an image of such a device that I could just blast onto this thing -- if so how would I do that? Any help figuring out how to get this thing back up and running will be greatly appreciated. All the icon helpline offers to do is sell me a whole new 7" replacement tablet for $1300. Not something I'm thrilled about.