Hey everyone,
So I was extracting the framework-res.apk to replace the battery .pngs. Everything was going fine but when I was replacing the framework-res.apk in Root Explorer the nook rebooted and thus has sent me into a bootloop. I tried reverting to stock using the sdcard method but it boots into CWM. Not sure if the acclaim_update.zip can be used in CWM i tried anyway getting the error "asset failed: (ro.product.device") == "blaze"
So basically I am extremely stuck. Any suggestions?
Get in CWM and plug your device to the machine you used for root or working nook drivers, in CWM go to mounts and storage> and mount /system, take the stock or custom framework-res.apk and put it in C:\ntroot ( where adb should be) , it will look like this C:\ntroot\framwork-res.apk , open CMD as administrator and run:
Code:
> cd C:\ntroot
> adb devices (Check if your device really gets recognized)
> adb push framework-res.apk /system/framework
Good Luck!
~ Veronica
I went through the process and after a reboot it now is going into a faster bootloop. So I was researching a bit deeper and came across your post on the same process for the /system folder with the acclaim.zip. I went through that process also replacing all folders and still am in a bootloop. I know the adb is pushing properly. Sorry, Im still learning. Your help is greatly appreciated.
Maybe format /system folder and start from strach in CWM? Also what exact folders need replaced?
heric1 said:
I went through the process and after a reboot it now is going into a faster bootloop. So I was researching a bit deeper and came across your post on the same process for the /system folder with the acclaim.zip. I went through that process also replacing all folders and still am in a bootloop. I know the adb is pushing properly. Sorry, Im still learning. Your help is greatly appreciated.
Maybe format /system folder and start from strach in CWM? Also what exact folders need replaced?
Click to expand...
Click to collapse
Well you just messed up with framwork-res.apk which is located in /system/framework folder so that means only the framework folder. Unmount system, wipe cache, dalvik cache and fix permissions i CWM or in adb you fix permissions like this
Code:
adb shell chmod 644 /system/framework/*.apk
and change owner like this:
Code:
chown root /system/framework/*.apk
Good luck!
~ Veronica
Still not working, just constantly rebooting. I am honestly so stumped. Is there any way I just can restore?
heric1 said:
Still not working, just constantly rebooting. I am honestly so stumped. Is there any way I just can restore?
Click to expand...
Click to collapse
When you installed CWM did you make a backup? possibly if so try making a restore, if not then try a hard factory reset , thought i don't know if that or the acclaim_update.zip might work with the CWM we have. I personally did not installed CWM and won't because of this kind of things still for me is not fully tested perhaps not really a must for now. I have tested the adb method while in CMW in my smartphones there is still things to fix in the nook tablet.
Bed time catch you tomorrow, wish you luck!
~ Veronica
Yeah silly me, didn't create a backup in CWM. Also I cannot do a hard factory reset as the bootloop is so fast, it barely reaches the 'read forever' logo. I honestly do not know what I can even do at this point until wait for a custom ROM to flash over everything in CWM. I also PMed Zapcorns who is having a similar issue. Regardless thanks so much thus far and hopefully someone has a fix.
I forgot to tell you to try a wipe data too in CWM, cross fingers. Hopefully that makes it
~ Veronica
Sent from XDA premium using my Nook Tablet
Sadly nope, still stuck.
Well, if it makes you feel any better mine doesn't even loop. It boots to the "read forever" and then just stays there. I'm going to try flashing the acclaim_update zip because that's the only thing I've read so far that might fix it. If it works I will let you know...but I have a sinking feeling I'm screwed.
Can you boot into CWM? If so I think your far from screwed. If you don't have CWM installed you should be able to revert to stock via the sdcard method. I just feel stuck in limbo as I can not revert to stock recovery nor can I flash a ROM as they dont exist yet.
I can get to CWM recovery but now it's just a matter of finding a flashable zip that will undo what my stupidity has wrought. It's encouraging to hear I may not be totally SOL.
Edit: I think we may be in the exact same state. I can't do the factory reset either. All I can do is boot to CWM for now. I did manage to experiment with Indirect's gapp zips and get those to flash.
Denmmurray said:
I can get to CWM recovery but now it's just a matter of finding a flashable zip that will undo what my stupidity has wrought. It's encouraging to hear I may not be totally SOL.
Edit: I think we may be in the exact same state. I can't do the factory reset either. All I can do is boot to CWM for now. I did manage to experiment with Indirect's gapp zips and get those to flash.
Click to expand...
Click to collapse
Did you make a CWM backup when you installed it? or you did not too, the last 2 options that you guys have is try to get a clean CWM backup from a user(Still could simply not work) or try Goncezilla sdcard method to flash stock recovery so bye bye CWM and then try to flash the acclaim_update.zip.
Good Luck to both of you, and hope you learn the lesson and don't mess up around without be cautious.
~ Veronica
Asking for boot.img might be a bit much, plus you said it still has a possibility of not working. I was looking over Goncezilla's post but not quite understanding how to do the process with stock recovery instead of CWM? And also worst case scenario I am assuming when ROMs start coming out I can just flash one over this mess?
Once again thanks and this has been quite a learning experience.
heric1 said:
Asking for boot.img might be a bit much, plus you said it still has a possibility of not working. I was looking over Goncezilla's post but not quite understanding how to do the process with stock recovery instead of CWM? And also worst case scenario I am assuming when ROMs start coming out I can just flash one over this mess?
Once again thanks and this has been quite a learning experience.
Click to expand...
Click to collapse
Have you tried the CWM backups from this site in the ROM's sections - they are NOT flashable zips!
~ Veronica
Never been so happy to see my homescreen! Worked perfectly. Thank you so much for that link and your patience.
heric1 said:
Never been so happy to see my homescreen! Worked perfectly. Thank you so much for that link and your patience.
Click to expand...
Click to collapse
Cool, glad it worked.
Here thank this Guy for take the tame to root with both both methods and upload them
http://forum.xda-developers.com/showpost.php?p=21748940&postcount=57
Sent from XDA premium using my Nook Tablet
lavero.burgos said:
Get in CWM and plug your device to the machine you used for root or working nook drivers, in CWM go to mounts and storage> and mount /system, take the stock or custom framework-res.apk and put it in C:\ntroot ( where adb should be) , it will look like this C:\ntroot\framwork-res.apk , open CMD as administrator and run:
Code:
> cd C:\ntroot
> adb devices (Check if your device really gets recognized)
> adb push framework-res.apk /system/framework
Good Luck!
~ Veronica
Click to expand...
Click to collapse
Where can I get the nook tablet 8gb drivers so I could try this? can you post a link?
mysteriousme said:
Where can I get the nook tablet 8gb drivers so I could try this? can you post a link?
Click to expand...
Click to collapse
If you're stuck in a boot loop, this YouTube vid by raywaldo might help get you out of it:
http://www.youtube.com/watch?v=ZIrgkjen8ro&feature=related
Related
Rooted last night, superuser was working fine but this morning I lost all superuser access. Uninstalled SU and reinstalled it. Rom manager gained access but others won't. Now even when I try to flash CWM recovery it says "an error occurred while attempting to run privileged commands!". Any ideas?
you might have to look in this thread, and get the working SU that way
http://forum.xda-developers.com/showthread.php?t=1003088
magneticzero said:
you might have to look in this thread, and get the working SU that way
http://forum.xda-developers.com/showthread.php?t=1003088
Click to expand...
Click to collapse
Thanks, I was reading over that a few minutes ago. I'll give it a try
Tried to flash that patch but I can't boot into recovery. It boots into the bootloader, I select recovery and it just goes back to the white bootloader screen. Am I missing something?
since su works with rom manager, press menu and clear cache and try to push clockwork back on your phone. also there is a option to wipe clockwork mod everytiem you update it. alot of people have success with that.
magneticzero said:
since su works with rom manager, press menu and clear cache and try to push clockwork back on your phone
Click to expand...
Click to collapse
I did that, rebooted like 10 times trying to get into recovery and for some reason I know have su permissions again.... I dunno what happened.
But how do I get into cwm to install rom's and backup/restore? I keep getting the white bootloader screen for some reason.
Sorry, double post....
ugadroid said:
I did that, rebooted like 10 times trying to get into recovery and for some reason I know have su permissions again.... I dunno what happened.
But how do I get into cwm to install rom's and backup/restore? I keep getting the white bootloader screen for some reason.
Click to expand...
Click to collapse
there is an option in rom manager to boot into clockwork recovery, but i edited my last post.. maybe you need to push clockwork again if it isnt going into recovery the manual way, might not be loading the files properly
magneticzero said:
there is an option in rom manager to boot into clockwork recovery, but i edited my last post.. maybe you need to push clockwork again if it isnt going into recovery the manual way, might not be loading the files properly
Click to expand...
Click to collapse
Seems like something might have gotten messed up. Now I lost all su permissions again. lol. I probably should unroot and do the process over again. I've tried the option in rom manager but it takes me to the bootloader screen and when I select recovery it just takes me right back.
I also had this same exact problem. The reason was I had messed something up during the root process. What happened to me is I switched the RUU's around and ended up with the wrong one. My opinion would be to re-root using the original ADB method and make sure you are using the correct RUU. If you need assistance just PM me and I will guide you step through step to re-rooting your T-Bolt.
stedrocklp said:
I also had this same exact problem. The reason was I had messed something up during the root process. What happened to me is I switched the RUU's around and ended up with the wrong one. My opinion would be to re-root using the original ADB method and make sure you are using the correct RUU. If you need assistance just PM me and I will guide you step through step to re-rooting your T-Bolt.
Click to expand...
Click to collapse
I thought for sure I used the right RUU files but it was late so I could have messed up. I would appreciate any help, I used the windows one click method. Not too familar with ADB but I have played with it a lil. PM me when ever you get a chance. Thanks bro.
Mad props to stedrocklp for all the help last night. The help that people give on this site is why it's the best.
I have a nandroid stock backup that I would like to restore to, however system restores but boot image is stuck at "Restoring boot image..." and goes back to the main CWM screen with reboot system now etc.
in dire need of assistance, can't get out of CWM recovery and when trying to adb the Prime now has an error exclamation mark on it. I have CWM 5.8.1.8
radici said:
I have a nandroid stock backup that I would like to restore to, however system restores but boot image is stuck at "Restoring boot image..." and goes back to the main CWM screen with reboot system now etc.
in dire need of assistance, can't get out of CWM recovery and when trying to adb the Prime now has an error exclamation mark on it. I have CWM 5.8.1.8
Click to expand...
Click to collapse
Did you make the backup in 5.8.1.8 or did you make it back in the old 5.5.0.4 version? If you made it back then, then you will not be able to restore boot as that version did not back it up in the first place.
If however you made the backup with your current version of CWM, then I am at a bit of a loss. I have had no issue whatsoever restoring any and/or all of my backups.
When you say that when trying to use ADB the Prime now has an error exclamation mark, please elaborate as to where you are seeing this exclamation mark. Is it in the terminal/command prompt?
I made the backup in the old 5.5.0.4 version. I'm using naked drivers which fixed the exclamation mark in pc's device manager however still can't push anything to Prime as adb reports "device not found"
fixed
radici said:
I made the backup in the old 5.5.0.4 version. I'm using naked drivers which fixed the exclamation mark in pc's device manager however still can't push anything to Prime as adb reports "device not found"
Click to expand...
Click to collapse
You're screwed. You have no backup.
goodintentions said:
You're screwed. You have no backup.
Click to expand...
Click to collapse
He said in the post above yours that it was fixed. He should probably add that to the Thread title and also detail how he fixed it for other folks who find themselves in a similar situation.
Please I need help with similar situation. I'm using cw 5.5.0.4 n tried installing a Rom but doesn't go past ee pad screen. I don't see my back up. How do i use the USB while in recovery?
Sent from my ADR6400L using xda premium
inspeckta_dek said:
Please I need help with similar situation. I'm using cw 5.5.0.4 n tried installing a Rom but doesn't go past ee pad screen. I don't see my back up. How do i use the USB while in recovery?
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
OK, we need to do a couple of things here. Number one can your computer see your device with ADB? If you are unfamiliar with using ADB read this thread http://forum.xda-developers.com/showthread.php?t=1427008 and then come back here.
If your comp can see your device, we can push a new ROM to your sdcard by making sure you have the ROM in your ADB directory on the computer, and then in a terminal/command prompt you will need to type "adb push *ROM.ZIP* /sdcard" replacing *ROM.ZIP* with the actual name of the ROM (also omit the *s) This will take a while but have patience and eventually you will have a message telling you that it completed successfully.
Now we need to get you a new CWM image onto your Prime. There are 2 methods you could use both detailed in my thread here http://forum.xda-developers.com/showthread.php?t=1576937
If you've followed all of this so far, then give yourself a pat on the back, you are no longer the noob that you were when you set out on this quest. We're almost done.
Reboot into CWM the usual way and wipe all partitions. Flash your ROM and it should flash everything including boot.
After verifying that you can get into a working OS, reboot into recovery and make a new backup immediately.
I wish you luck my friend.
Doktaphex said:
OK, we need to do a couple of things here. Number one can your computer see your device with ADB? If you are unfamiliar with using ADB read this thread http://forum.xda-developers.com/showthread.php?t=1427008 and then come back here.
If your comp can see your device, we can push a new ROM to your sdcard by making sure you have the ROM in your ADB directory on the computer, and then in a terminal/command prompt you will need to type "adb push *ROM.ZIP* /sdcard" replacing *ROM.ZIP* with the actual name of the ROM (also omit the *s) This will take a while but have patience and eventually you will have a message telling you that it completed successfully.
Now we need to get you a new CWM image onto your Prime. There are 2 methods you could use both detailed in my thread here http://forum.xda-developers.com/showthread.php?t=1576937
If you've followed all of this so far, then give yourself a pat on the back, you are no longer the noob that you were when you set out on this quest. We're almost done.
Reboot into CWM the usual way and wipe all partitions. Flash your ROM and it should flash everything including boot.
After verifying that you can get into a working OS, reboot into recovery and make a new backup immediately.
I wish you luck my friend.
Click to expand...
Click to collapse
I have a win 7 pc... When I connect the prime in device manager it comes up as all android on emulator..with yellow exclamation.
Sent from my ADR6400L using xda premium
Sent from my ADR6400L using xda premium
inspeckta_dek said:
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Have you tried the naked drivers from here http://forum.xda-developers.com/showthread.php?t=1426502
I would follow that guide, and then see if you can get it working.
Nope will check it when I get home. Is it suppose to see it in recovery? Will def try it
Sent from my ADR6400L using xda premium
Doktaphex said:
OK, we need to do a couple of things here. Number one can your computer see your device with ADB? If you are unfamiliar with using ADB read this thread http://forum.xda-developers.com/showthread.php?t=1427008 and then come back here.
If your comp can see your device, we can push a new ROM to your sdcard by making sure you have the ROM in your ADB directory on the computer, and then in a terminal/command prompt you will need to type "adb push *ROM.ZIP* /sdcard" replacing *ROM.ZIP* with the actual name of the ROM (also omit the *s) This will take a while but have patience and eventually you will have a message telling you that it completed successfully.
Now we need to get you a new CWM image onto your Prime. There are 2 methods you could use both detailed in my thread here http://forum.xda-developers.com/showthread.php?t=1576937
If you've followed all of this so far, then give yourself a pat on the back, you are no longer the noob that you were when you set out on this quest. We're almost done.
Reboot into CWM the usual way and wipe all partitions. Flash your ROM and it should flash everything including boot.
After verifying that you can get into a working OS, reboot into recovery and make a new backup immediately.
I wish you luck my friend.
Click to expand...
Click to collapse
ok i tried the new driver zip and it installed. its says asus android device and then samsung galaxy nxus.. does that mean its connected?
SOLVED, see post #6
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
=JKT= said:
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
Click to expand...
Click to collapse
okay, I just found out that I can access adb in the state that recovery is in.
Is it possible to reflash either the rom or the recovery from a shell in here? or would that be "bootstrapping" since I'm already in recovery?
perhaps I can adb push a backup to /system?
of course the ./adb reboot bootloader doesn't work
I'm using a mac and I've had trouble getting fastboot to recognize my device in the past...I think last time I just borrowed someone's pc to do it.
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Can't test it right now, but I think the process would go something like this (recovery means on the phone, computer means on the computer):
Code:
[I]recovery>[/I] mount /sdcard
[I]computer>[/I] adb push recovery.img /sdcard/
[I]recovery>[/I] flash_image recovery /sdcard/recovery.img
[I]recovery>[/I] umount /sdcard
[I]recovery>[/I] reboot recovery
Note once again that this is untested, it's straight from my head, so it might need adjustments.
ravilov said:
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Click to expand...
Click to collapse
thanks for the idea. I can't access any of the functions of the recovery. it's just a splash screen. ADB recognizes the device on my computer though. I can adb push files...I'm wondering if I can push something from a backup to my phone through adb. I guess I'd need to push the /system and /boot to it. I can't seem to get mmcblk0p12 to mount though...
edit: I didn't see the code you added.
I tried it and got this message:
error scanning partitionsfailed with error: -1
I can't seem to get any partitions to mount (ie mmcblk0p12 etc)
I'm nervous about totally borking recovery since it's my only access to the phone right now. I might have to borrow a pc to get fastboot to work.
=JKT= said:
I might have to borrow a pc to get fastboot to work.
Click to expand...
Click to collapse
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
[SOLVED]
ravilov said:
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
Click to expand...
Click to collapse
SOLVED!!
First I found out that if I type fastboot -i 0x22b8 before every command, they worked fine.
then I stumbled across moto-fastboot, which is apparently a special fastboot for moto devices.
I used that to flash a new recovery the standard way and it worked out just fine.
Thanks so much for your help, ravilov!!
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
ravilov said:
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
Click to expand...
Click to collapse
I've only had the Atrix for about a week. Still learning the ropes: coming from an HTC device, so I'm used to doing things a certain way and relearning some basics lol
Cheers!
Sent from my MB860 using xda app-developers app
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
bmxer4130 said:
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
Click to expand...
Click to collapse
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
lolo9393 said:
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
Click to expand...
Click to collapse
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
bmxer4130 said:
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
Click to expand...
Click to collapse
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
lolo9393 said:
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
Click to expand...
Click to collapse
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
E: Unable to write to ums lunfile (No such file or directory)
Click to expand...
Click to collapse
So yeah, its the internal memory.. now if i could just get adb shell to work right
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
bmxer4130 said:
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
Click to expand...
Click to collapse
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
lolo9393 said:
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
Click to expand...
Click to collapse
Ok, I was able to adb shell and rebuild the partition table, and it was indeed messed up, and I can mount usb storage, but I still can't get it to boot into any rom, and it refuses to boot into cwm recovery unless its just rebooted from odin. in recovery in the log it has an error about libc.so, idk if that has anything to do with it though. I'm beginning to think the problem may have to do with my usb cable. I accidentally switched the stock one with a Galaxy SII one, which should be fine, but maybe not.
bmxer4130 said:
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
So yeah, its the internal memory.. now if i could just get adb shell to work right
Click to expand...
Click to collapse
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Mevordel said:
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Click to expand...
Click to collapse
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
bmxer4130 said:
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
Click to expand...
Click to collapse
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
lolo9393 said:
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
Click to expand...
Click to collapse
Yes, I tried flashing it in cwm, along with eryigit (both with entropys kernel flashed over them) and PA venturi, but it refuses to boot properly. If it is the bootchain, how can I get a dump of a working one?
And I was able to dump a lot of stuff from [adb pull */*] and can access logs and dmesg, but havent inspected them fully. Is there an easy way to read the boot log and/or setup a custom log to run preboot? I figure that wouldnt be necessary since the linux kernel does a fine job of logging itself.
And yes I think I am skilled enough now, just was confused how to get to the adb shell, but I'm fairly well versed in linux, so the shell is relatively comfortable for me.
But if I'm able to figure it out I'm going to make a How To thread including what I've found and what you've found and posted to make it easier for nooblets in the future, maybe even make a simple shell script to repartition the US 8gb model.
I fixed it
how?
Jistropy said:
how?
Click to expand...
Click to collapse
Mainly luck hehe. But actually from the mentioned threads ^^^^^ and this nifty trick, but use caution as I have no clue how well this works for other devices, if it all. And a large part of the problem was that my battery was dead because it wasn't charging correctly when plugged into my computer; and it kept dying in Odin.
Do you have a similar problem?? I can probably help..
I was trying to disable FSYNC using the method described by poofyhairguy. I did it via terminal, in su. I mounted /system in rw mode, I copied libsqlite.so and libsqlite_jni.so into backup copies, and overwritten them with copied provided by poofyhairguy. Alas, I forgot to chmod, so they were left with whatever permission they came from. I rebooted the tablet and now it is permanently in the starting screen with big ASUS letters across. I cannot even turn it off!
Help, please, what do I do? I don't really know much about Android, so please use simple explanation.
Just to add some details. My Prime is stock, rooted but not unlocked.
I also don't seem to be able to reach it from ADB. I did install ADB and drivers on my PC a while ago, when I rooted it. I'm trying this now:
- connect Prime to PC
- reboot with volume down, select a USB symbol
- PC says "installing drivers" and "ready"
- in adb shell, when I try "adb devices" it shows an empty list
Any help?
OK, here is more information and more questions. I can start the tablet in fastboot mode (USB symbol on screen). After reinstalling ASUS suite and Google SDK I connected the tablet to my Windows 7 laptop. It searched for drivers for a while, installed and said "ready".
"adb devices" returns and empty list. "fastboot devices" returns one entry, a long hexadecimal number and the word "fastboot". Does it mean that I can see my tablet via fastboot but not adb? Does adb work when tablet is in fastboot mode at all?
Does it mean that the only option is to reflash ASUS firmware?
@Felisek Did you tried to wipe aka hard reset the device via bootloader? or you have important files which you don't want to reset? or you don't see wipe option in bootloader?
Sorry, I'm not much expert in android underhood that I can help you more but looking at your problem doesn't look like you have bricked your device so keep hopes. Someone having more knownledge might come and help you.
btw; AFAIK, adb and fastboot are different kinds. You see fastboot.exe in the sdk package? yes that links with fastboot option on the devices. But I might be wrong as well.
May be you try entering into fastboot and use fastboot.exe, then go to the path where you modified the files. Either replace them to original ones or chmod. But I don't know whether this gonna work.
CRACING said:
Did you tried to wipe aka hard reset the device via bootloader? or you have important files which you don't want to reset? or you don't see wipe option in bootloader?
Click to expand...
Click to collapse
There is a wipe option, but I don't think it is going to work. As far as a know (correct me if I'm wrong), factory wipe does not change /system folder. In particular, there are two "wrong" files in /system/lib that cause the problem, so wiping everything else is not going to help. I need to change/restore these files.
I think I can reflash the stock ROM using recovery, but I'd like to try and fix it without wiping everything first. I don't have anything unmissable on the tablet, but reinstalling everything and rooting is a bit of a hassle.
Felisek said:
There is a wipe option, but I don't think it is going to work. As far as a know (correct me if I'm wrong), factory wipe does not change /system folder. In particular, there are two "wrong" files in /system/lib that cause the problem, so wiping everything else is not going to help. I need to change/restore these files.
Click to expand...
Click to collapse
Hmm may be you are right so reflashing whole ROM is required.
Felisek said:
I think I can reflash the stock ROM using recovery, but I'd like to try and fix it without wiping everything first. I don't have anything unmissable on the tablet, but reinstalling everything and rooting is a bit of a hassle.
Click to expand...
Click to collapse
Recovery? but you said you haven't unlocked or you mean stock recovery?
Yeah, upon reflashing, you will lose root but hey, you can root again using the new method (motorola's) and its not at all risky as unlocking. :good:
May be you can wait for sometime, I hope someone comes up guiding you how to replace/modify the system files using adb or fastboot.
CRACING said:
Recovery? but you said you haven't unlocked or you mean stock recovery?
Click to expand...
Click to collapse
There is a "RCK" option on startup, I thought that was recovery. But, yes, I mean stock recovery, if this is how it is called. Download stock firmware, put it on a microSD, rename it to EP201_SDUPDATE.ZIP, reboot and apparently it installs automatically.
When I was making my guide I tried using the old ICS libsqlite.so and libsqlite_jni.so files and softbricked in the same mannor. The only way I found to fix it was to flash the stock ROM as it says to do in my guide.
Note that unless you purposefully wipe your data in the recovery your data should remain intact from my experiance with it. The way the stock Asus recovery seems to do it is to blow /system away (so yes you must re-root, etc).
Good news. I unbricked my Prime by reflashing the stock ROM, using the method described by poofyhairguy. All my apps and settings survived. I only lost root, so even rootkeeper cannot recover it. Not too bad, after all.
Sent from my Transformer Prime TF201 using Tapatalk HD