Okay, I am new to the rooting and modifying android devices.. I rooted my Nexus 7 using supersu and was making modifications with ROM toolbox pro. I changed the boot screen, the font, and the wireless icon(starting out small) well when I restarted my tablet it wouldn't get past the lboot screen that I set to.
When I went into recovery mode, I tried to recovery my old system but it giving me md5 missing.. so I'm kinda of stuck
is there a direct approach to the solution?
Nice tip. Only use stuff like mods tha are on xda. Use metamorph to impalement theming stuff or flashable zips. Regaurds your situation ty flashing the rom again. Wipe data factory reset. If all else fails flash the google factory image and learn from your mistakes you made. Most problems you get in the future are pretty easily fixed with a bit of patience
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
Nice tip. Only use stuff like mods tha are on xda. Use metamorph to impalement theming stuff or flashable zips. Regaurds your situation ty flashing the rom again. Wipe data factory reset. If all else fails flash the google factory image and learn from your mistakes you made. Most problems you get in the future are pretty easily fixed with a bit of patience
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was afraid you were going to say that.. alright thank you, I will try this a soon as possible and report back.
Hohokam337 said:
I was afraid you were going to say that.. alright thank you, I will try this a soon as possible and report back.
Click to expand...
Click to collapse
Okay so wiping the data/factory reset didn't work, how do i go about flashing the google factory image?
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app
http://forum.xda-developers.com/sho...Factory Image with fastboot / return to stock
Sent from my Galaxy Nexus using Tapatalk 2
Now i am running into this error with the command prompt..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Move your android folder to the C: Drives root folder and try directing the command prompt from there.
Type :-
cd c:\Android\android-sdk\platform-tools
adb
mr_tris said:
Move your android folder to the C: Drives root folder and try directing the command prompt from there.
Type :-
cd c:\Android\android-sdk\platform-tools
adb
Click to expand...
Click to collapse
Got it,
Thank you all for the help
Related
YOU MAY NEED THE NEW OTA (can someone confirm) i know this kinda belongs in the theme section but.... it works will post pics
here is one that i found that worked: http://forum.xda-developers.com/showthread.php?t=752088
when it tells you to reboot click yes! It does a soft boot so the theme stays.
requires temproot. I found that many Nexus one themes work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It doesn't work for me, it asks me to reboot but doesn't reboot
Sent from my T-Mobile G2 using XDA App
djdant said:
It doesn't work for me, it asks me to reboot but doesn't reboot
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
try again if it doesn't once more you will have to initiate one through adb
Says I don't have enough free space in /system
EDIT: Nevermind, a little buggy but is working just fine...! Thanks. OP, this should tide me over till enomther makes a new Manup456 ROM compatible with OTA.
SuperDave81 said:
Says I don't have enough free space in /system
Click to expand...
Click to collapse
it showed that error for me a couple of times just keep trying or reboot phone and try again...
Argggg, only worked the first time, now the reboot prompt just keeps popping up and not actually rebooting.
When i was using it, it made my phone get stuck in a constant reboot, it just doesnt work for me
Sent from my T-Mobile G2 using XDA App
It works fine for me just keep trying it and you'll get it to work.
U can force a soft reboot by type stop on the hard keyboard then hit enter. Then type start , then hit enter.
Fyi it only works on pre ota. Bevause it go patched n the ota
Sent from my T-Mobile G2 using XDA App
all i want is a black notification bar with white fonts.. but i haven't the slightest clue what to do lol
To all those having problems - is busybox installed correctly? Last I checked it was a major requirement of metamorph.
So are the no other ways to partition the KF internal storage without being on a custom ROM? Got hit with a message today, see image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Learned GNU and went old school.
Sent from my Kindle Fire using xda premium
xolanir said:
So are the no other ways to partition the KF internal storage without being on a custom ROM? Got hit with a message today, see image.View attachment 960608
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
no -- you cannot partition in any mode but recovery. So therefore you can either 1. do it with the recovery or 2. adb shell (in recovery) and use Parted
http://www.gnu.org/software/parted/manual/html_mono/parted.html
http://luv.asn.au/overheads/parted/index.html
except you would go..
adb shell
~ # parted dev/block/mmcblk0
which starts off the Parted program
and then ... I played around a bit.
Just bacl up your data and print your tables each step of the way so you know what you started off with....
androidcues said:
no -- you cannot partition in any mode but recovery. So therefore you can either 1. do it with the recovery or 2. adb shell (in recovery) and use Parted
http://www.gnu.org/software/parted/manual/html_mono/parted.html
http://luv.asn.au/overheads/parted/index.html
except you would go..
adb shell
~ # parted dev/block/mmcblk0
which starts off the Parted program
and then ... I played around a bit.
Just bacl up your data and print your tables each step of the way so you know what you started off with....
Click to expand...
Click to collapse
This looks to be a very difficult process in the hands of a noob. Gonna need to do more reading up before attempting. Thx for the tip.
Sent from my Kindle Fire using xda premium
xolanir said:
This looks to be a very difficult process in the hands of a noob. Gonna need to do more reading up before attempting. Thx for the tip.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I would not suggest playing with the internal storage of the kindle if you are not completely comfortable with adb and how partitioning works.
What ever happened with fireparted? Did the dev take it down cos of issues people are having with repartitioning the KF? As of now, are there no other alternative methods to get the work done? Thx
sent from my CommandCenter
This is weird. I never had this problem with my Galaxy S3.
I've enabled USB Debugging on the phone.
Even toggled it off, rebooted and turned it on again.
I've also rebooted my computer and even updated SDK Toolkit.
No change in problem though.
Every time I try to connect to my phone from ADB, it just tells me the device is offline (see attached pic).
Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
StolenVW said:
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
I'm not getting any popup for that.
CZ Eddie said:
I'm not getting any popup for that.
Click to expand...
Click to collapse
Try this
http://www.wugfresh.com/faqs/how-to-fix-adb-device-is-listed-as-offline-on-android-4-2-2/
And if you do a Google search for
how to fix adb device offline
It comes up with other things to try
Sent from my A500 using Tapatalk HD
Thanks, I tried the info in that link but never got the pop-up asking for ADB permissions.
I did google prior to posting also. I listed in my OP what I tried (which is what my googling suggested).
I'm about to ODIN back to factory stock anyways. So I'll try again after that. Maybe I messed something up during all the bloatware removal I did yesterday.
Nope, a fresh ODIN install of stock ROM didn't help at all.
Guess I'll have to uninstall & reinstall Android Toolkit maybe.
EDIT:
Using Motochopper root tool, I finally got the popup. And made sure to select "always allow from this computer". I think that should fixit.
EDIT #2:
Nope, that didn't help at all. Still "offline".
EDIT #3:
Actually, using the ADB from Motochopper does work. It's just the ADB from my Android Toolkit that doesn't work.
Sounds like one in android tool kit is out of date
Try updating the android sdk
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
So after the first week with this device I get a strange QuickRemote problem. It give me a blank page after tipping something in the app. QuickRemote.apk data/cache clear don't help. What could I do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Clear cache and data in app settings. ...I had an issue with mine disappearing. ... this fixed it
Sent from my LG-D803 using XDA Premium 4 mobile app
xdafoundingmember said:
Clear cache and data in app settings. ...I had an issue with mine disappearing. ... this fixed it
Sent from my LG-D803 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I rldy say that the Cache and date clearing dont help
Edit: Just saw other 2 pics. No idea. Give people a bit more info to what all you did to your phone otherwise.
Steamer86 said:
Edit: Just saw other 2 pics. No idea. Give people a bit more info to what all you did to your phone otherwise.
Click to expand...
Click to collapse
If really nothing. I have even not rooted phone
I added 2 TV's and 1 Selteka Set-top Box that all. After night I wanted to turn my TV on and thats what happened...
```
deleted
Someone help...
Wipe...
stefy97100 said:
Wipe...
Click to expand...
Click to collapse
Cache and Data Cleaning DONT HELP
There was a report from a member with the exact same issue as you have, however, he said he did root and also delete one of the corresponding file, that was his problem, and soon after he move that file back into the system, QR worked as normal. Your case is kind of strange since you haven't rooted it yet.
My suggestion is factory reset.
Remember, you will lose everything, so backup first.
votinh said:
There was a report from a member with the exact same issue as you have, however, he said he did root and also delete one of the corresponding file, that was his problem, and soon after he move that file back into the system, QR worked as normal. Your case is kind of strange since you haven't rooted it yet.
My suggestion is factory reset.
Remember, you will lose everything, so backup first.
Click to expand...
Click to collapse
Done a LG Backup , transfered to my sister N4 and after factory reset made a reset of backup It seems that it worked Thanks you.
Was QuicksetSDK frozen or removed? Quick Remote needs that file to work properly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PREVIEW:
Download Here (flashable via recovery)
removed
i like it besides the random last part that's red.. which i don't know what its about
I love it! However, to this day I still don't understand why certain boot animations cause the boot to freeze. Which is a problem I unfortunately have with this boot animation.
Looks nice!! Can you make one with the adventure time characters? .!!
Sent from my Nexus5™. On PA™.
" Nothing's ever locked..."
kitlenc Allegro
anthonyly said:
i like it besides the random last part that's red.. which i don't know what its about
Click to expand...
Click to collapse
me don't get it, too
this is the best bootanimation i've seen thx
Wow best ever clean and skill. Can you make some android?
Sent from my Nexus 5 using Tapatalk
I love this bootanimation so much but can do one to Galaxy Nexus ???
The phone freezes after the red part for me
I really love this though
I removed the download link because it seems that this boot will stuck after the red part..
i'm sorry.. i tested yesterday over a stock and no problem..
have same problems on N7 ... i don't know why
I will share the frames and You can use, rescale to other resolutions...and try to fix or send to a bootanimations expert because don't have much time ..
You can try also to follow all the guidelines here, and also ask to the creator of bootanim factory
http://forum.xda-developers.com/showpost.php?p=49865118&postcount=2
frames here:
https://www.dropbox.com/s/up112dumsoa2rqc/BootAnimation Frames.zip
thanks
Ramis said:
The phone freezes after the red part for me
I really love this though
Click to expand...
Click to collapse
long-press power button + volume up + volume down until it shutdown... after that reboot immediately in recovery and connect your phone to a pc..
Copy the stock bootanim inside platform tools folder on your pc or where you have adb and other tools
download the boot from here
http://d-h.st/4kc
Open a terminal in platform-tools folder
in recovery select install zip from sideload..
and sideload the bootanimation
Code:
adb sideload kitkat_Bootanimation.zip
it will flash the stock bootanim, reboot when finished and you will be able to boot your phone
Thread closed at the OPs request.