Related
Before it was noted that the theme was for 3G only, I went ahead and pushed both the framework-res.apk and systemui.apk of the BigDX Theme into my Xoom Wifi. Now all I am able to do on my Xoom is stare at the boot animation. I need some help please!...UPDATED:I did the one-click unroot and now Im stuck on the Dual Core Tech. Screen, doesn't even get into a boot loop now!...FINAL UPDATED:I manually rebooted into fastboot(Vol Down + power keys) and then reapplied the instructions from the root thread(adb and fastboot method) and I am back in baby!!! So if any of you get stuck in a boot loop, feel free to hit me up! PM or Gtalk(same as)!
Did you install the Tiamat kernel at any point?
Sent from my Xoom using Tapatalk
JungleJiujitsu said:
Before it was noted that the theme was for 3G only, I went ahead and pushed both the framework-res.apk and systemui.apk of the BigDX Theme into my Xoom Wifi. Now all I am able to do on my Xoom is stare at the boot animation. I need some help please!
Click to expand...
Click to collapse
I should note that immediately after pushing both the themed apk's:
1) I pushed the stock files/images back into my Xoom.
2) I performed the instruction in the root thread(unlocking and rooting through fastboot and adb)
3) And I flashed the stock system.apk
B Dizzle said:
Did you install the Tiamat kernel at any point?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yes, its the kernel included in the root zip files...http://forum.xda-developers.com/showthread.php?t=1010568...I can post the logcat now if you'd like, but its MASSIVE!
Just attach the text file instead of posting the whole thing.
Sent from my Xoom using Tapatalk
B Dizzle said:
Just attach the text file instead of posting the whole thing.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
How do you create a txt file of the results again?
use ddms or:
adb -d logcat > logcat.txt
ctrl+c to stop it
sangreal06 said:
use ddms or:
adb -d logcat > logcat.txt
ctrl+c to stop it
Click to expand...
Click to collapse
My bad, Im gonna need a few mins, cmd is not recognizing device any longer, have to reboot PC
sangreal06 said:
use ddms or:
adb -d logcat > logcat.txt
ctrl+c to stop it
Click to expand...
Click to collapse
I keep getting device not found now!
JungleJiujitsu said:
I keep getting device not found now!
Click to expand...
Click to collapse
Nvmd, I got to mount and I was able to run logcat, but now that I typed adb logcat > logcat.txt its just sitting there.
JungleJiujitsu said:
Nvmd, I got to mount and I was able to run logcat, but now that I typed adb logcat > logcat.txt its just sitting there.
Click to expand...
Click to collapse
Ok, my bad again, I just check and its there, just had to do crtl + C there too lol ....its says it exceeds for this file type so I had to rar it.
JungleJiujitsu said:
Ok, my bad again, I just check and its there, just had to do crtl + C there too lol ....its says it exceeds for this file type so I had to rar it.
Click to expand...
Click to collapse
I am no expert but it looks like there is a boot.img - system.img mismatch.
EDIT:
Just noticed this is resolved. What was done to fix the issue?
Please detail how you fixed this. I did the same thing, except I accidentally installed the wifi version on my 3g.
also, did it wipe your data?
arrtoodeetoo said:
Please detail how you fixed this. I did the same thing, except I accidentally installed the wifi version on my 3g.
also, did it wipe your data?
Click to expand...
Click to collapse
I apologize for only now getting back to you, but for future reference, the steps I took to get out are in the OP. Yes it did wipe data.....And if you are still having issues, please feel free to PM me, probably the best way to get my attention!
Ok I got in the boot loop after trying to apply the UI string, here is the way to fix it 100% of the time.
1. power off xoom
2. power on xoom, while at dual core logo press vol down wait a few seconds and press it again doing so will give you option to reboot into recovery
3. press vol up to boot into cwr
4. apply 3.1 update, apply bootfix update (if on wifi), factory reset
5. reboot and it will boot up fine
graklore said:
Ok I got in the boot loop after trying to apply the UI string, here is the way to fix it 100% of the time.
1. power off xoom
2. power on xoom, while at dual core logo press vol down wait a few seconds and press it again doing so will give you option to reboot into recovery
3. press vol up to boot into cwr
4. apply 3.1 update, apply bootfix update (if on wifi), factory reset
5. reboot and it will boot up fine
Click to expand...
Click to collapse
+1 exactly the same here. Except didn't reset as I had already 3.1 installed, but if you haven't definately factory reset. I didn't lose anything except my Google accounts, but adding those quickly resolved everything.
UI string dilemma, just so attractive to have a fix yet that was a unfortunate detour
Newbie stuck in boot loop !!!
I appreciate you guys help, I'm pretty much a tech rookie. gotta explain this to me like I'm an 8 year old...
How do I apply "3.1 update" in CWR? where is it located?
How do I apply "bootfix update" in CWR? where is it located?
I have a rooted wifi xoom. tried to flash the UA string and now stuck in a bootloop!
any simple, non-tech-savy help would be appreciated! --never shoulda went this far if i didn't totally know what I'm doing!
I just rooted in adb and fast boot method on 3.1 xoom wifi 32gb. I am now stuck in boot loop. I can go into recovery but I cannot get past the boot video screen..
what do you guys suggest I should do?
Well........ there may be other solutions...but I eventually bit the bullet and went back to stock....
device was wiped... all downloads and info gone... pretty much back at square one...... eh well... at least i'm back in !!
So I've been messing around with android phones for a while now and I'm stuck. I was on the oxygen 2.1.6 Rom then decided to make a back up. However instead of going into CWR it just went into fast boot. When I go into recovery it just says fast boot mode no reboot or recovery img. I tried to odin back to stock like I usually do but adb wont recognize my device like it usually does. Please don't tell me I'm bricked and that I messed up bad. Any help would be appreciated. Thanks in advance.
I tried reinstalling drivers etc etc. Somebody help me lol
futuralabs87 said:
So I've been messing around with android phones for a while now and I'm stuck. I was on the oxygen 2.1.6 Rom then decided to make a back up. However instead of going into CWR it just went into fast boot. When I go into recovery it just says fast boot mode no reboot or recovery img. I tried to odin back to stock like I usually do but adb wont recognize my device like it usually does. Please don't tell me I'm bricked and that I messed up bad. Any help would be appreciated. Thanks in advance.
I tried reinstalling drivers etc etc. Somebody help me lol
Click to expand...
Click to collapse
It sounds like you flashed a bad recovery. Download a new recovery , boot into fastboot, and
Code:
fastboot flash recovery yourrecoveryfile.img
adb wont recognize my device so how do I flash a new recovery
futuralabs87 said:
adb wont recognize my device so how do I flash a new recovery
Click to expand...
Click to collapse
Adb only works when the phone is booted normally, provided usb debugging is on.
Use fastboot. If you want to make sure it's working, boot into fastboot mode and
Code:
fastboot devices
If it's working, you will see your serial number.
If the other options can't help you get your problem solved try Odin.
www.samfirmware.com
get the right files for your device and Odin program itself. There are tutorials on here how to use it.
sorry I was being an idiot. I tried fastboot and it showed nothing connected. When I flashed a recovery it just hung waiting for device. I have all the drivers loaded on the computer but my device is still unknown and wont be recognized. I have all the odin files and I have used odin before. This sucks
btw appreciate the help guys
futuralabs87 said:
btw appreciate the help guys
Click to expand...
Click to collapse
Try installing pdanet, that will install all the drivers you need for fastboot and Odin.
Sent from my Nexus S using XDA Premium App
Have you tried to run shabbys 1 click root to get the recovery in place? Assuming your on sprint that is
Sent from my Nexus S 4G using Tapatalk
dreamsforgotten said:
Have you tried to run shabbys 1 click root to get the recovery in place? Assuming your on sprint that is
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
shabbypenguin said:
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
Click to expand...
Click to collapse
Sorry I didn't say anything, it was a burp
Sent from my Nexus S 4G using Tapatalk
shabbypenguin said:
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
Click to expand...
Click to collapse
Maybe not, but it does include some handy files. ;-)
Download and unzip Shabby's OneClickRoot
Install pdanet. (See the readme for which one.)
Reboot your computer.
Then try using his version of fastboot.
I'm assuming you are in fastboot mode (it will say so) and that you're using the usb cable that came with the phone.
I will give it a go now I do have PDA installed too
No luck boys just bought a sensation but still wanna fix my nexus s
Sent from my HTC Sensation 4G using XDA Premium App
Like the title says.
I'm in recovery, I wiped it all (unfortunately even the ROM as zip I put on it) and now I don't have no ROM on it and no zip to flash a ROM.
Thought this was no problem, knowing from smartphone recoveries to mount sdcard and copying the file on it. But Nexus 7, well, has no sdcard.
What can I do?
As it is now, I don't have nothing on it and rebooting it wouldn't lead to anything useful.
I need help.
What can I do?
Thanks in advance.
l33ch0r said:
Like the title says.
I'm in recovery, I wiped it all (unfortunately even the ROM as zip I put on it) and now I don't have no ROM on it and no zip to flash a ROM.
Thought this was no problem, knowing from smartphone recoveries to mount sdcard and copying the file on it. But Nexus 7, well, has no sdcard.
What can I do?
As it is now, I don't have nothing on it and rebooting it wouldn't lead to anything useful.
I need help.
What can I do?
Thanks in advance.
Click to expand...
Click to collapse
If you have Android SDK installed, you can use adb push to push the zip file to your internal storage. Put the ROM zip file in your Android SDK - Platform Tools folder on your computer, reboot the N7 into Recovery (connected to computer of course!), open Command Prompt window and change directories to where ever you keep your Android SDK (for me, it's: cd sdk/platform-tools). Then type:
Code:
adb push <name of ROM zip file> /sdcard
Wait, and after about 20 - 60 seconds it'll complete, then you can flash the ROM. It'll be on the root of your internal sdcard (/sdcard).
Sounds difficult for a bloody rookie like me - is there really no easier way? Like transfering via recovery by just telling recovery to mound internal-sd so that it'll pop up on my pc? (know that from CWM and 4Ext on my smartphone)
Or could you explain the steps so that even the bloodiest rookie of them all could understand it properly :-/
aaaw **** -.-
by the way, device is still in recovery
l33ch0r said:
Sounds difficult for a bloody rookie like me - is there really no easier way? Like transfering via recovery by just telling recovery to mound internal-sd so that it'll pop up on my pc? (know that from CWM and 4Ext on my smartphone)
Click to expand...
Click to collapse
Maybe, I don't know. Have you tried it? What recovery are you using? I use TWRP.
RMarkwald said:
Maybe, I don't know. Have you tried it? What recovery are you using? I use TWRP.
Click to expand...
Click to collapse
TWRP as well. Just unlocked, rooted and flashed recovery and now I wanted to have a custom rom.
I tried to mount data and what else there was in "advanced" - my PC doesn't show me anything
Edit: not in advanced, it's the point "mount"
Restock and reroot.You can use Wugfresh toolkit for this. You just install the toolkit and if you can boot in bootloader mode you're saved. That's what I did and it solved my problem.
Sent from my Nexus 7 using xda premium
l33ch0r said:
TWRP as well. Just unlocked, rooted and flashed recovery and now I wanted to have a custom rom.
I tried to mount data and what else there was in "advanced" - my PC doesn't show me anything
Edit: not in advanced, it's the point "mount"
Click to expand...
Click to collapse
How'd you root/unlock, toolkit of some type?
Using the adb command mentioned is the only way that I know of to push a file to your N7. It's not as difficult to do as it sounds.
RMarkwald said:
How'd you root/unlock, toolkit of some type?
Using the adb command mentioned is the only way that I know of to push a file to your N7. It's not as difficult to do as it sounds.
Click to expand...
Click to collapse
Toolkit by WugFresh - I may try to get into bootloader and get back to stock - hopefully it works...
l33ch0r said:
Toolkit by WugFresh - I may try to get into bootloader and get back to stock - hopefully it works...
Click to expand...
Click to collapse
Yeah that would work, as long as you don't re-lock via fastboot. That's what probably wiped out your sdcard, was the fastboot unlock of your device, as it wipes your sdcard.
andymihail said:
Restock and reroot.You can use Wugfresh toolkit for this. You just install the toolkit and if you can boot in bootloader mode you're saved. That's what I did and it solved my problem.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Is it important which current status I choose?
There are 2 to be chosen: Soft-Bricked/Bootloop and Device is on/Normal
If "Device is on" means, that it's turned on, then this'll be my choice, right?
Totally shocked right now
This ain't even my device :-/
RMarkwald said:
Yeah that would work, as long as you don't re-lock via fastboot. That's what probably wiped out your sdcard, was the fastboot unlock of your device, as it wipes your sdcard.
Click to expand...
Click to collapse
No, wiping of my /sdcard was all my fault. I guess I have to take all credit for that
Well downloading the Stock with the toolkit takes quite some time...
foolish me -.-
Thanks for your help so far.
I'll definetely report whether it worked or not
I've never used any of the toolkits out there, I've done it using adb/fastboot commands in a Command Prompt window.
l33ch0r said:
Is it important which current status I choose?
There are 2 to be chosen: Soft-Bricked/Bootloop and Device is on/Normal
If "Device is on" means, that it's turned on, then this'll be my choice, right?
Totally shocked right now
This ain't even my device :-/
Click to expand...
Click to collapse
I can't remember my choice, was a few months ago.
Don't think you can go wrong with either.
I would try device is on.
Sent from my Nexus 7 using xda premium
RMarkwald said:
I've never used any of the toolkits out there, I've done it using adb/fastboot commands in a Command Prompt window.
Click to expand...
Click to collapse
I would've used your solution immediately but I'm just too unfamiliar with this method
Toolkits are probably the easiest way - and it was pretty easy - who could expect me to wipe the zip, I just moved to the storage before flashing it?...
Why does this file has to be hosted on goo.im?
Goo.im gives me roundabout 120kb/s...
It took a while for me also, but in the end everything worked well.
Sent from my GT-I9100 using xda premium
andymihail said:
It took a while for me also, but in the end everything worked well.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I desperately hope to have the same luck...will the bootloader still be unlocked after that procedure? I understand that root definetely is gone, but that shouldn't be a problem at all.
l33ch0r said:
I desperately hope to have the same luck...will the bootloader still be unlocked after that procedure? I understand that root definetely is gone, but that shouldn't be a problem at all.
Click to expand...
Click to collapse
It will remain unlocked until/unless you run the fastboot command: fastboot oem lock
If you don't run this, it will remain unlocked.
Whoaaaa I could scream!
Now that I downloaded the right one and try to flash it through the toolkit, it tells me, that there's no adb to be found. He doesn't recognize the device in bootloader.
What should I do?
OH THANK GOD! Tried it via recovery, he found it and restarted into bootloader
First of all: thank you so much guys - I was really shocked, but it all worked out
One more question before I make the same mistake again. Where should I put the zip which I wanna flash? When I have it connected to the pc, it shows me a portable device where the folders of the internal storage are (like Alarms, Android, DCIM, Download etc pp) - that's where I put the ZIP before.
Shall I keep it there?
And another question: what should I wipe in order to get it done properly?
Edit: Figured it out - got me CWM, much more familiar with that one
but thanks again for all your help guys
Finally, i have solved it !!! A couple of days ago, i forgot my pattern and clicked on forgot pattern, but i didn't get a prompt to turn on wifi. So basically, i was stuck, unless i wanted to do a factory reset and lose all of my data. Here's my unique solution to this problem, :
First of all, you need to be rooted and to have usb debugging ON. Otherwise, it won't work.
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Here's what i did:
First, i booted the modified boot image and by using either adb or the toolkit, i pulled /data/data and /data/app to my pc.
Second, I made a full wipe and set up my N7 as usual. At this point, you need a good root file explorer in order to get to the /data folder. I installed colornote (from the app backup i made, because i wan't sure that there was a new version and,if there was, it could be a possible failure, because i wasn't sure how it would behave with the last version's data) and rebooted (in order for colornote to get into the dalvik cache).
Third, i opened up colornote's folder in /data/data and just replaced the databases folder with the one from my backup and i went to /data/dalvik-cache and deleted the corresponding color note dalvik file. Afterwards, i just rebooted and voila, all my stuff that i had written in color note was staring at me.
Now, i want to mention that i've only tried this with colornote (as it was my foremost priority to get to the essays that were stored there) and i've tried this on only 4.1.2. I can't guarantee that it will work on other apps or that you won't get damage to your precious Nexus 7, so please, proceed with caution, and don't blame me if something unexpected comes up. Good luck !!!
P.S. If you get more than one device or emulator, it's because you have bluestacks, disable or uninstall it, and you're good to go !!!
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
iAndroidOS said:
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Click to expand...
Click to collapse
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
NIMBAH said:
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I tried that and it didn't work
bftb0 said:
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
Click to expand...
Click to collapse
Thank you for reminding me, it is imperative to restore the permissions
iAndroidOS said:
I tried that and it didn't work
Click to expand...
Click to collapse
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
NIMBAH said:
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I dunno, i went into adb and used the adb shell rm /data/system/gesture.key
command and as soon as it finished, i unplugged my N7 and rebooted it, and the login prompt was still there.
Hey so yesterday I mucked around with the mounting/unmounting/formatting stuff in fastboot. Now it's not booting up, it's stuck at the GOOGLE logo. I left it on overnight, and it's still stuck there. I can still turn off the device and enter fastboot mode. Anyone know what's wrong?
Thanks
How do you want to know what's happening to your device if don't tell us which commands you have done exactly with fastboot and why ?
Nico_60 said:
How do you want to know what's happening to your device if don't tell us which commands you have done exactly with fastboot and why ?
Click to expand...
Click to collapse
Sorry
I went to the fastboot menu and unmounted everything, and formatted everything. Then I deleted all user data and the cache partition. I'm running xenon HD rom.
Thanks
You were running xenon rom before you formatted everything! Now if you want to stay with xenon you have to push the rom in your device using adb and install it with recovery.
Nico_60 said:
You were running xenon rom before you formatted everything! Now if you want to stay with xenon you have to push the rom in your device using adb and install it with recovery.
Click to expand...
Click to collapse
I could care less about the rom. I just want to turn on the device...
It could be stock, I'll just root it again.
I'm kind of a beginner with this, how exactly do I push the rom
Anyways, thanks
nicetaco said:
I could care less about the rom. I just want to turn on the device...
It could be stock, I'll just root it again.
I'm kind of a beginner with this, how exactly do I push the rom
Anyways, thanks
Click to expand...
Click to collapse
I can't push it because it's not being recognized on my computer
Anyone help please?
92 views an only 1 person helping..
I would say to get Wug's tool kit and use that to unbrick/flash back to stock. To get your computer to recognize the tablet you likely need to install the proper drivers, which are included with the toolkit and instructions on installing them.
Edit: link http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my LG-P999 using xda premium
Волк said:
I would say to get Wug's tool kit and use that to unbrick/flash back to stock. To get your computer to recognize the tablet you likely need to install the proper drivers, which are included with the toolkit and instructions on installing them.
Edit: link http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
The problem is, I don't have USB debugging on, so it's impossible to install the drivers.
Go in bootloader/fastboot mode and then type "fastboot devices" to see if your device is recognized
Nico_60 said:
Go in bootloader/fastboot mode and then type "fastboot devices" to see if your device is recognized
Click to expand...
Click to collapse
Sorry if I sound stupid, but I don't think I can type in bootloader mode...
Nico_60 said:
Go in bootloader/fastboot mode and then type "fastboot devices" to see if your device is recognized
Click to expand...
Click to collapse
This may sound stupid, but I cant type in bootloader mode
You did already use fastboot commands no?
Nico_60 said:
You did already use fastboot commands no?
Click to expand...
Click to collapse
No, I didn't...
nicetaco said:
No, I didn't...
Click to expand...
Click to collapse
Please help I think I'm going crazy o.0
nicetaco said:
Please help I think I'm going crazy o.0
Click to expand...
Click to collapse
OK never mind I fixed it. I just installed the ROM through a USB from a OTG cable. Thanks a lot for your help though!
-Kevin
Enjoy my thanks
same case with me...
my nexus 7 3g now stuck on google screen
buncit8 said:
same case with me...
my nexus 7 3g now stuck on google screen
Click to expand...
Click to collapse
what did you do before it was stuck at the Google logo?
Nico_60 said:
what did you do before it was stuck at the Google logo?
Click to expand...
Click to collapse
i want to install xenonHD rom but failed with error bla bla bla... (status 7).
so i try to wipe data, wipe cache, wipe dalvik cache, and format system
when i do reboot, it stuck on google logo
really need help,
Did you reflash the ROM and gapps after doing the wipes? Otherwise, try: factory reset, format system, flash ROM, flash gapps, reboot.