Tried to adjust the dpi and I guess I went too far because now it goes from the Google screen to a black screen and stays that way
What can I do?!
Sent from my HTC Sensation using xda premium
Can you access adb over USB?
Sent from my ARCHOS 80G9 using xda premium
Yes I have fastboot and adb available
Sent from my HTC Sensation using xda premium
Go and grab the nexus 7 factory image. found here ( https://developers.google.com/android/nexus/images ). Then extract the files. Fastboot flash the boot.img, recovery.img, and the system.img
Commands: fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
I believe this is what I did. Oh and make sure the files are in the platform-tools folder
I hope this helps.
nickL0V3 said:
Yes I have fastboot and adb available
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I remember reading about this issue on another thread and the problem was solved through this.
http://www.youtube.com/watch?v=-E-EF0QC0Gc
I don't suppose there's a way to do this where I DON'T lose all of my data is there? And is my media safe? The stuff that would normally go on the sd card
Sent from my HTC Sensation using xda premium
Like perhaps I could pull the build.prop and fix the dpi and push it back? If anyone knows the correct path to it. Maybe?
Sent from my HTC Sensation using xda premium
I'll see if i can find the right build.prop path for you.
It says location: ( /system/build.prop )
hope that helps
Can someone please figure out the stock lcd density? I successfully pulled the build.prop
Sent from my HTC Sensation using xda premium
stock dpi = 213
---------- Post added at 10:09 PM ---------- Previous post was at 10:05 PM ----------
Use rom toolbox from the market. It's easier using the app. I had to do the same thing you did except I just redid the whole thing.
Repaired the build.prop and still won't boot so I guess I'm going to the stock image.
Thanks for trying to bail me out
While I have your attention, I'm new to the no sd card thing. Will a CWM wipe erase my pictures and videos and such?
Sent from my HTC Sensation using xda premium
unfortunately yes. but i re flashed all three file. Try and flash the bootloader-grouper-3.34.img file. I know since I did the syste.img file, that might have erased the memory.
I had to do the same thing to but I also noticed that my permissions on the build.prop file got changed. Some how it was set to rw-rw-r-- and should have been rw-r--r--. Once I changed the permissions, it booted right up.
I've tried to change the dpi 10 times now. Kept bricking and had to fastboot back to stock each time. I think I can live without Tablet UI.
Since I've got you all here (and since my n7 is booting now) what is a good number to try to get the tablet ui?
Sent from my HTC Sensation using xda premium
Jadedjak said:
I had to do the same thing to but I also noticed that my permissions on the build.prop file got changed. Some how it was set to rw-rw-r-- and should have been rw-r--r--. Once I changed the permissions, it booted right up.
Click to expand...
Click to collapse
What were the adb commands to fix this *Unix noob and windows user*
Sent from my Samsung Galaxy S III
nickL0V3 said:
Since I've got you all here (and since my n7 is booting now) what is a good number to try to get the tablet ui?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
160.
theoneofgod said:
160.
Click to expand...
Click to collapse
That's the lucky number that started this thread lol. I guess I'll go without for now
Sent from my HTC Sensation using xda premium
After restoring with the stock image its only showing 5gb available. It's a 16gb model.
Uh oh
Sent from my HTC Sensation using xda premium
nickL0V3 said:
After restoring with the stock image its only showing 5gb available. It's a 16gb model.
Uh oh
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I would reflash the factory image once more and flash cwm and root manually (The one click methods still need a little work) then once you change the DPI (170) worked for me,Connect to your PC and use adb to reboot and it should work perfectly. These are the method's I used and everything works great now,Nova launcher is also working pretty good with it too,The N7 is pretty much unbearable to use without the DPI change.Good luck and if you need any of the files I used just PM me & I'll create a link for you
Sent from my Nexus 7 using xda premium
Related
hmm was bored so i moved my density to 160... lol made everything small and now the launcher keeps failing... so how can i change the density in adb or something without using my phone?
you'd have to pull your build.prop via adb and edit it I guess notepad++? Then find where is says dpi or resolution whereever you find the 160 at and change it back to 240 save it and push it back in the /system
Sent from my SPH-D700 using xda premium
I've never used adb shell ill have to look into how to using it for later usage
Sent from my SPH-D700 using xda premium
thanks but i already restored a old backup... i was told though to reflash the rom and that would fix it
steviee7 said:
thanks but i already restored a old backup... i was told though to reflash the rom and that would fix it
Click to expand...
Click to collapse
Would have been simplier and faster to use abd
Sent from my SPH-D700 using xda premium
hi guys, I am not sure whether I am in the right sections. I have a Asus eee pad slider sl101.just now I tried flashing a new ROM using power button and volume down. I flashed a cm9 for tf101.now it is stocked at the boot screen with nothing happening. what have I did wrong? Thanks in advance.
Sent from my HTC Desire S using xda premium
hisname said:
hi guys, I am not sure whether I am in the right sections. I have a Asus eee pad slider sl101.just now I tried flashing a new ROM using power button and volume down. I flashed a cm9 for tf101.now it is stocked at the boot screen with nothing happening. what have I did wrong? Thanks in advance.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
You flashed the ROM using CWM, correct? What was the name of the ROM?
yes, it is correct I flashed using Clockworkmod by team rogue. I am not really sure what ROM I flashed. but I attached a image of the boot screen. but the ROM I flashed was for TF101(which I think should be compatible with my SL101). or do I need to flash a Asus stock recovery image to solve this issue? BTW is this a boot loop? thanks for the reply.
Edit: I found out the ROM that I flashed.
md5sum: dd80806298385a7a8057b21b384d389f. This is the stable ROM for TF101
Sent from my HTC Desire S using xda premium
hisname said:
yes, it is correct I flashed using Clockworkmod by team rogue. I am not really sure what ROM I flashed. but I attached a image of the boot screen. but the ROM I flashed was for TF101(which I think should be compatible with my SL101). or do I need to flash a Asus stock recovery image to solve this issue? BTW is this a boot loop? thanks for the reply.
Edit: I found out the ROM that I flashed.
md5sum: dd80806298385a7a8057b21b384d389f. This is the stable ROM for TF101
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
If you're getting a bootloop, then something either something went wrong with the installation or with the ROM. I don't think it's kernel related since you're getting to the ROM's boot animation. I would try to relash to ROM or try a different one that clearly states it's compatible with the Slider, because I still don't know which one you flashed.
then how do I flash another ROM when the slider is still in the boot animation? also what ROM is recommended for the slider? I have searched most forums and most of them are for the transformer.
Sent from my HTC Desire S using xda premium
I think even on that rom you should be able to boot in recovery mode. Perhaps you need to wipe data / cache and reboot again.
farsight73 said:
I think even on that rom you should be able to boot in recovery mode. Perhaps you need to wipe data / cache and reboot again.
Click to expand...
Click to collapse
even I boot into recovery mode, it is only "clear data" or "android", if I wipe data, wouldn't my data be gone?
Sent from my HTC Desire S using xda premium
hisname said:
even I boot into recovery mode, it is only "clear data" or "android", if I wipe data, wouldn't my data be gone?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
A ROM that is guaranteed to work on the Slider is Android Revolution, created by mike1986. If I were you, I would just start over completely and flash that ROM.
Solar.Plexus said:
A ROM that is guaranteed to work on the Slider is Android Revolution, created by mike1986. If I were you, I would just start over completely and flash that ROM.
Click to expand...
Click to collapse
so I just connect my slider to the computer, go into recovery, and flash the ROM?
Sent from my HTC Desire S using xda premium
after flashing the Android revolution hd, it got worse. Now it does not even go into boot animation. It is stuck on asus screen
Sent from my HTC Desire S using xda premium
hisname said:
after flashing the Android revolution hd, it got worse. Now it does not even go into boot animation. It is stuck on asus screen
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Did you install the compatability pack
hisname said:
so I just connect my slider to the computer, go into recovery, and flash the ROM?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
This here doesn't sound right. You don't connect your Slider to a computer to flash ROMs. You flash the ROM (zip file) from recovery on your Slider.
Also, Android Revolution doesn't require flashing any compatibility pack. Since it is already based on Asus stock ROM, it already has the necessary files.
Solar.Plexus said:
This here doesn't sound right. You don't connect your Slider to a computer to flash ROMs. You flash the ROM (zip file) from recovery on your Slider.
Also, Android Revolution doesn't require flashing any compatibility pack. Since it is already based on Asus stock ROM, it already has the necessary files.
Click to expand...
Click to collapse
oh ok, but after flashing android revolution hd, it just got onto asus boot screen. do I do a full factory wipe to salvage this situation?
Edit: i took a video of what i did and uploaded to my dropbox account.here is the link: http://db.tt/YhJUuT7N
Sent from my HTC Desire S using xda premium
zachf714 said:
Did you install the compatability pack
Click to expand...
Click to collapse
what compatability pack are u talking about?mind if u put a link?
Sent from my HTC Desire S using xda premium
hisname said:
what compatability pack are u talking about?mind if u put a link?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
In the development section for the tf101
---------- Post added at 11:18 AM ---------- Previous post was at 11:14 AM ----------
hisname said:
what compatability pack are u talking about?mind if u put a link?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
It's called slider SL101 compatability pack
hisname said:
what compatability pack are u talking about?mind if u put a link?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Don't worry about the compatibility pack for the Android Revolution ROM.
To flash this ROM, you MUST first flash the SUPER WIPE file that is listed in the Android Revolution thread.
Solar.Plexus said:
Don't worry about the compatibility pack for the Android Revolution ROM.
To flash this ROM, you MUST first flash the SUPER WIPE file that is listed in the Android Revolution thread.
Click to expand...
Click to collapse
the lite version or full version?
Sent from my HTC Desire S using xda premium
hisname said:
the lite version or full version?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
In theory, either should be fine.
ok, after flashing the super wipe lite and I flashed the ROM, it is still stuck on asus screen, do I use a nandroid back up and use the super wipe full version? it has been a week already and my problem still can't be solved. I am really getting very desperate.... what had happened????
Edit: problem solved. I use a factory wipe and flash a Cm9 and it worked!! but just a small question, what is the command to mount and unmount SD card in terminal emulator? my SL101 can't read my SD card
Sent from my HTC Desire S using xda premium
Anyone managed this successfully? I changed the build.prop to 160dpi, how tablet then refuses to boot. Reflashed 4.2.2, miss my lower dpi!
On stock rom by the way.
Sent from my Nexus 7 using XDA Premium HD app
Have you tried using a utility like this to make the changes?
rifraf1 said:
Have you tried using a utility like this to make the changes?
Click to expand...
Click to collapse
Yeah, tried root toolbox pro and build.prop editor, they dont seem to gain access to the file to change it. Have you had any luck with it?
Give it a try..
https://play.google.com/store/apps/...251bGwsMSwxLDEwOSwibHYubjNvLmxjZGRlbnNpdHkiXQ
Don't forget to love the thanks button if I help you.
Hasn't worked since 4.0, used to use it on my s2!
Sent from my Nexus 7 using XDA Premium HD app
OK, in case anyone else runs into this, remember to change the permissions back to 644 after you have made your changes!
Sent from my Nexus 7 using XDA Premium HD app
herghost said:
Anyone managed this successfully? I changed the build.prop to 160dpi, how tablet then refuses to boot. Reflashed 4.2.2, miss my lower dpi!
Click to expand...
Click to collapse
I managed to change my dpi to 160 with no issues. I actually prefer it on 177.
Sent from my HTC Sensation 4G using xda app-developers app
Hey guys how do i resize CM nav bar?
Sent from my Nexus 4 using xda app-developers app
Theres no actual option in the rom, but you could check out this: http://forum.xda-developers.com/showpost.php?p=38102614&postcount=25
I would make nandroid before flashing it just in case
Nandroid whats that? Ohh and i checked the forum out but it wasn't helpful any other forums?
Sent from my Nexus 4 using xda app-developers app
JayMix said:
Nandroid whats that? Ohh and i checked the forum out but it wasn't helpful any other forums?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nandroid is the backup you make through recovery
Okay. Well i have searched around several times and i can't seem to fine anything that on resizing CMs nav bar.
Sent from my Nexus 4 using xda app-developers app
You can't change it from within CM, but you can flash different mods in recovery (like the one posted above) to change it manually.
Ill be honest if You dont know what a nandroid is you may want to take some time and do some basic research before you end up bricking your phone. Messing with the OS of a device is NOT fool proof. Things can go wrong and then you are stuck with a non working device that you cant return.
Ok just learned what nandroid is and so i guess the next step is to nandroid backup my phone and then flash the mod from the link right?
Sent from my Nexus 4 using xda app-developers app
JayMix said:
Ok just learned what nandroid is and so i guess the next step is to nandroid backup my phone and then flash the mod from the link right?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yep. And if something goes wrong after flashing the mod (systemui crashing, bootloop, etc) just restore the nandroid.
Sent from my HTC Desire using xda app-developers app
Hey guys it didn't work what did i do wrong?
Sent from my Nexus 4 using xda app-developers app
JayMix said:
Hey guys it didn't work what did i do wrong?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You probably didnt do anything wrong, its just that the mod didnt work lol.
Try out this tutorial. It should work, but its a bit of work.
These are the lines that you have to change:
Code:
<dimen name="navigation_bar_height">[COLOR="Red"]38.0[/COLOR]dip</dimen>
<dimen name="navigation_bar_height_landscape">[COLOR="red"]38.0[/COLOR]dip</dimen>
<dimen name="navigation_bar_width">[COLOR="red"]38.0[/COLOR]dip</dimen>
The link you provided is broken.
Sent from my Nexus 4 using xda app-developers app
JayMix said:
The link you provided is broken.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That's odd. It was just working fine...and now it says account suspended .
Anyways this is basically what you have to do(may require some other searching):
-navigate to system/framework and copy the framework-res.apk to your computer
-decompile framework-res.apk
-in the decompiled folder navigate to /res/values/ and open the file named dimens.xml in a text editor
-edit the lines that I posted above to your liking
-recompile framework-res.apk and push it back to the phone. Also make sure the permissions are set to rw-r-r
Hey what does bar width do? hey I am having issues signing and pushing files back to my phone?
Sent from my Nexus 4 using xda app-developers app
JayMix said:
Hey what does bar width do?
Click to expand...
Click to collapse
You should keep it the same as the height. All three values should be the same
hey I am having issues signing and pushing files back to my phone?
Click to expand...
Click to collapse
Whats the issue? You cant just put a question mark at the end of your vague statement and expect someone to figure out your problem
Sorry typo, by the way thx for all your help so far. I have edited my framework nav bar to 36 but i dont know how to replace my original framework.
Sent from my Nexus 4 using xda app-developers app
you should try a rom with more control built in like aokp, slim, or pa if you want to change stuff more and dont quite know how to mod system files correctly
anyway, heres what i found with a quick google: http://forum.xda-developers.com/showthread.php?t=2159270
its pretty complicated but the instructions are clear
---------- Post added at 08:39 PM ---------- Previous post was at 08:35 PM ----------
JayMix said:
Sorry typo, by the way thx for all your help so far. I have edited my framework nav bar to 36 but i dont know how to replace my original framework.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
just copy the original framework incase you want to go back to it and paste the modded framework in place of the original framework and reboot you phone
JayMix said:
Sorry typo, by the way thx for all your help so far. I have edited my framework nav bar to 36 but i dont know how to replace my original framework.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
-Make a nandroid backup just in case
-Download an root file manager. I would recommend root explorer (paid), but there are other free ones like es file explorer.
-Copy the framework-res.apk from your computer to your phone. (just use the usb cable and transfer it over using MTP)
-Open the root file manager and copy the framework-res.apk from where you put it
-Navigate to system/framework and rename the existing framework-res.apk to framework-res.apk.bak
-Paste the new framework-res.apk
-Long press the new framework-res.apk and go to permissions and change them to rw-r-r
-reboot
yep I do that but as soon as I get done renaming framework.apk.bak the phone restarts and goes into boot loop.
I reflash CM10.1 and nandroid backup and everything is fine again. then I tryed just replacing framework but same thing happens.
ohh and mbucks911 the reason why I dont use AOKP is becasue my battery life with AOKP is terrible it causes my phone to run at around 38c which is warm enough to make my hands sweat and my battery drains 10% for every 10mins my screen is on. when I use CM my phone barely gets over 30c and operates around 27c for every and 10% of my battery thats almost 2 hours of sot thats why i am trying to stick with CM.
JayMix said:
yep I do that but as soon as I get done renaming framework.apk.bak the phone restarts and goes into boot loop.
I reflash CM10.1 and nandroid backup and everything is fine again. then I tryed just replacing framework but same thing happens.
Click to expand...
Click to collapse
Try using adb to push it.
Code:
adb remount
adb push \path\to\framework-res.apk /system/framework/
adb reboot
I flash a new rom yesterday for my nexus 4. Unfortunately, it was stuck in the custom rom logo.
I want to fix it via recovery mode. Sadly, my volume key was broken:crying:
Does anybody knows how can I boot my nexus 4 without using volume key? (it was stuck in the custom rom logo.)
Is it an other way that is possible to fix my phone?
And don't pick on my english, I know that is poor:angel:
Use the application goo manager, it gives you the option to reboot into recovery
Sent from my Nexus 4 using xda app-developers app
XxLostSoulxX said:
Use the application goo manager, it gives you the option to reboot into recovery
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The phone bootloops. Did you try to use adb reboot recovery when bootanimation shows up? It could work
Sent from my Nexus 4 using xda premium
gallardo5 said:
The phone bootloops. Did you try to use adb reboot recovery when bootanimation shows up? It could work
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I wonder if he made a nandroid. However if your volume Kris are broken obviously you'd want to fix that.
Sent from my Nexus 4 using xda app-developers app
I'm trying
gallardo5 said:
The phone bootloops. Did you try to use adb reboot recovery when bootanimation shows up? It could work
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you for your suggestion
I'm trying, but CMD said that my computer cannot found my device
What can I do:crying:
Bouser Cheung said:
Thank you for your suggestion
I'm trying, but CMD said that my computer cannot found my device
What can I do:crying:
Click to expand...
Click to collapse
Oh, I try it two times, and that is work
Thank you so much:highfive: