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..
Related
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
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
Hi, got a problem, long story short, cant acces internal storage in any way, tried to flash gapps for cmx by lloir but cwm and twrp dont allow me to do it in any way (fastboot flash, adb sideload zip), does anyone had similar problem or even better, found a solution?
myusernamewastoken said:
Hi, got a problem, long story short, cant acces internal storage in any way, tried to flash gapps for cmx by lloir but cwm and twrp dont allow me to do it in any way (fastboot flash, adb sideload zip), does anyone had similar problem or even better, found a solution?
Click to expand...
Click to collapse
Make sure your adb is up to date and supports sideload and make sure you have the proper drivers on your pc to recognize the hox+
Once those terms are met, flash TWRP and do the sideload process again and ditch CWM
Sent from my HTC One X+ using xda premium
yes, adb is up to date, it supports sideload, there was no other way to flash rom (which is quite logical), i am using linux, screw windows-style "proper drivers" (and yes, I have proper drivers), adb/fastboot devices returns me serial code for plugged phone and yes, tried to sideload that zip in twrp (sending ok, writing failed) and in cwm (dunno, adb sideload gapps.zip didnt work anyway). I acctualy tried to figure out whats going on before posting, but nothing helped :/
P.S. I woke up sick today, which is bad for my stretched program, so I may be a bit rude...
i assume you have "enabled" sideload in TWRP
advanced > sideload
or you can just adb push filename.zip data/media/0/whatever.zip (if you use 4.2.1 just remove the 0) within the recovery without needing to hit sideload
yes, i have enabled sideload, in cwm, device was not found, in twrp terminal quoted sending ok, writing failed
adb push was I think endless waiting for device, or error (cant try it again right away, dont have hox+ here), but i am not sure i tried right path when i am looking at data/media/... :/ will try in few hours
You can also just push the file to your sdcard and then flash by putting in adb push then the file /sdcard
Sent from my HTC EVARE_UL using xda app-developers app
Dunno if you cant read or what, but I cant just adb push or fastboot flash it, I cant put in internal storage by any mean I can think of thats whole point of this thread...
Yes I did understand bit mounting sd storage is not possible at the time , and if sideload does not work which I have experienced myself , adb push does work in recovery.
Sent from my HTC EVARE_UL using xda app-developers app
Finaly did it (several days ago, too busy to post)thx for help, but I have come to interesting problems... when I run camera, it just pops error saying that i dont have any storage to store photos and FC...
same problem - HELP!
myusernamewastoken said:
Finaly did it (several days ago, too busy to post)thx for help, but I have come to interesting problems... when I run camera, it just pops error saying that i dont have any storage to store photos and FC...
Click to expand...
Click to collapse
Hey, I have ran into the same issue with not being able to sideload any ROMs or zip files to my sdcard after flashing. How did you correct this issue so that the sd card is available and camer/etc work?
thanks for the help
mmgill said:
Hey, I have ran into the same issue with not being able to sideload any ROMs or zip files to my sdcard after flashing. How did you correct this issue so that the sd card is available and camer/etc work?
thanks for the help
Click to expand...
Click to collapse
I didnt solve it sofar, still trying...
P.S. somebody on national android forum told me to flash different rom, it should fix according to him, didnt seems to work... help anyone?
Can you tell why you say it is not working? Because you didn't find the ROM_NAME_FILE_YOU_SIDELOADED.zip?
Is this the situation?
Lucky Thirteen said:
Can you tell why you say it is not working? Because you didn't find the ROM_NAME_FILE_YOU_SIDELOADED.zip?
Is this the situation?
Click to expand...
Click to collapse
Hmm... topic name was solved out, now I have different problem described later, dont really get your post, its too late for combination of me and sarcasm and honestly i dont care about someone beiing sarcastic in forum, I was in plenty of flamewars and I grew up. If you wanted to say something meaningful, sry, didnt get it, eventhough my english is fine and I am smart guy.
@mmgill I solved it in a weird way for me (maybe someone can explain), I tried to flash paranoid android, flashing OK, but it didnt boot after really long time, so I decided to put there CMX by llior again (found out its sofar only rom working for me). And like a miracle, external storage was avaliable for camera, file managers, windows and ubuntu (after making whole MTP concept work in ubuntu). Will try to flash some other roms my friend wanted to use (I dont own HOX+, it resembles dining plate for me, its my friends phone and it was his first root ).
myusernamewastoken said:
Hmm... topic name was solved out, now I have different problem described later, dont really get your post, its too late for combination of me and sarcasm and honestly i dont care about someone beiing sarcastic in forum, I was in plenty of flamewars and I grew up. If you wanted to say something meaningful, sry, didnt get it, eventhough my english is fine and I am smart guy.
Click to expand...
Click to collapse
Well if you take some time to read all my posts you will understand that I wasn't making fun of you and never flame people. I do realize now that I forgot to quote mmgill when I responded (he PM'd me about this issue), this is where you got lost.
Greetings.
Ok, then I am sorry... anyway, problem solved by flashing another rom, its not really my phone, its my friends, we were unable to do this earlier, cos hes not as much educated in all this and he downloaded several roms, which were all for AT&T HOX+ (he has international version), I did believe him that he choosed roms compatible with his phone, but hes dumbass and I feel terrible to loose many hours of my time when I could write my thesis and even worse to not check it earlier after him (its honestly very stupid rookie mistake), it just occured to me out of blue while chewing tobbaco... Thanks for help anyway, some things said helped to resolve this issue much faster...
.
.
.
so dumb... and now I am typing fastboot flash boot XYZ.img in my dreams...
using the right version of TWRP
Just a thought, if this is still an issue for anyone. But if you aren't able to mount your internal storage make sure you have installed the correct recovery installed. You can check at the end of the .img, Sprint ends with M7wls, international ends with M7, and there are others.
If you don't have the correct recovery installed it may not load your storage.
Hope this helps,
Cheers.
Hello. I'm annoyed
I rooted to get rid of problems... So
I followed these tasks: http://forum.xda-developers.com/showthread.php?t=1653566 and the root worked for a few days - then moved into a boot loop.... how/why... I don't know.
Ive tried many of the different .aos files to find a correct one for my 101g9 250gb, but I still can't get it out of the loop.
This is where I've been getting the different Aos files: http://forum.xda-developers.com/showthread.php?t=1468925
I get 2 different results 1)error 207 (update failed) or 2) boot loop.
One stange thing did happen once - It's managed to reload the android installer, I selected a language, then it crashed again. Of course I tried the same thing again, but it never got past the boot loop again.
After 2 weeks of trying, I'd like some help.
I always have it plugged in. It's not the battery. It's the HDD model and I don't know exactly which version came with the device. I think 4.0.25.. not 100% sure
Please help
I don't have the HDD model so don't know what to tell you exactly..
What I would do on my flash model is boot into recovery. completely reformat the system and use recovery to update the firmware with an Archos firmware (aos file) onto it.
Reformating it from recovery would bring the filesystem back to stock so it should fix anything wierd any of the other roms might have done. So dropping an Archos firmware on it should in theory fix it. Though you WILL lose your root and anything else you have on the drive.
Djirin said:
I don't have the HDD model so don't know what to tell you exactly..
What I would do on my flash model is boot into recovery. completely reformat the system and use recovery to update the firmware with an Archos firmware (aos file) onto it.
Reformating it from recovery would bring the filesystem back to stock so it should fix anything wierd any of the other roms might have done. So dropping an Archos firmware on it should in theory fix it. Though you WILL lose your root and anything else you have on the drive.
Click to expand...
Click to collapse
Thanks for your help, but no luck- that didn't work. I'm sure I lost all my data a long time ago with the amount of reformats I've done. What I'm curious about is, can the tablet actually become a brick just by using these rooted firmwares? I'm assuming that it's fine and that I just have to 'crack to code' to installing the right firmware in the right order.....
I'm still curious if anyone else has had this problem..
Hmm.. Try going back into recovery and try the Reset Android option?
Maybe do Reset Android. Reformat Device. Upgrade Firmware?
The device boots.. so it has to be something causing it.. Have you tried to see if you can use ADB to get into the device and look at any log entries?
Djirin said:
Hmm.. Try going back into recovery and try the Reset Android option?
Maybe do Reset Android. Reformat Device. Upgrade Firmware?
The device boots.. so it has to be something causing it.. Have you tried to see if you can use ADB to get into the device and look at any log entries?
Click to expand...
Click to collapse
ADB? ok, I didn't know what it was. But it's now installed and I followed a random setup on youtube, but when I type ADB devices, nothing comes up.
So now I have it installed, but I so far I can't get win7 to detect the tablet in device manager
Regarless, can the ADB detect problems on the tablet when the archos is only connected waiting for the AOS file (A101H-REC - 299MB)?
Btw, you've already got me waaaaay over my head on this stuff - but still, I'm learning.
pwnami said:
ADB? ok, I didn't know what it was. But it's now installed and I followed a random setup on youtube, but when I type ADB devices, nothing comes up.
So now I have it installed, but I so far I can't get win7 to detect the tablet in device manager
Regarless, can the ADB detect problems on the tablet when the archos is only connected waiting for the AOS file (A101H-REC - 299MB)?
Btw, you've already got me waaaaay over my head on this stuff - but still, I'm learning.
Click to expand...
Click to collapse
Let me join the conversation
Adb works only is it is enabled in developer settings.
What kind of system do you have in use?
In your case i would probably try exporting hdd in sde. This allows you to browse files inside your hdd in linux operating system through usb.
If it is empty, i would export data partition through sde. This allows you to see if there are any files in your data partition.
You said that the device bootloops, yes? That means that the reformat device is not working. It would remove the system, so you shouldnt even see the bootanimation.
Sent from my ME301T using xda app-developers app
julle131 said:
Let me join the conversation
Adb works only is it is enabled in developer settings.
What kind of system do you have in use?
In your case i would probably try exporting hdd in sde. This allows you to browse files inside your hdd in linux operating system through usb.
If it is empty, i would export data partition through sde. This allows you to see if there are any files in your data partition.
You said that the device bootloops, yes? That means that the reformat device is not working. It would remove the system, so you shouldnt even see the bootanimation.
Sent from my ME301T using xda app-developers app
Click to expand...
Click to collapse
Hi, thanks - any advice is welcome. I only have windows7 - Sorry.
As for the bootloop, yes that's the status. I hadn't even considered that the reformatting process wasn't actaully working [but it is] - I reformatted the device and didn't install an AOS. now every restart brings me straight into the Recovery menu [which should happen i assume].
So, with a "clean" but stubborn device, what would you advise to try to isolate the problem? (rather than me simply blindly trying random things)
Thanks
pwnami said:
Hi, thanks - any advice is welcome. I only have windows7 - Sorry.
As for the bootloop, yes that's the status. I hadn't even considered that the reformatting process wasn't actaully working [but it is] - I reformatted the device and didn't install an AOS. now every restart brings me straight into the Recovery menu [which should happen i assume].
So, with a "clean" but stubborn device, what would you advise to try to isolate the problem? (rather than me simply blindly trying random things)
Thanks
Click to expand...
Click to collapse
So reformat works. Have you tried to flash the official 4.0.28(http://update.archos.com/9/gen9/gen9_4.0.28/firmware_archos_it4.aos)?
After searching about your error 207, I found this:http://forum.archosfans.com/viewtopic.php?f=35&t=56037
Code 207 is issued by aosparser when the .aos upgrade file doesn't
pass the signature check.
...
There's more bad news... If the genuine original .aos files are also
giving the same error it means the signing keystore may also have been
damaged.
Click to expand...
Click to collapse
Of course, this is for Archos 5, so hopefully this is not the case.
julle131 said:
So reformat works. Have you tried to flash the official 4.0.28(http://update.archos.com/9/gen9/gen9_4.0.28/firmware_archos_it4.aos)?
After searching about your error 207, I found this:http://forum.archosfans.com/viewtopic.php?f=35&t=56037
Of course, this is for Archos 5, so hopefully this is not the case.
Click to expand...
Click to collapse
Yeah, I've used the aos from the archos site a bunch of times - still no luck. btw, that link to the 4.0.28 didn't work....
by "Flash" I hope you mean install.... not some other random process
pwnami said:
Yeah, I've used the aos from the archos site a bunch of times - still no luck. btw, that link to the 4.0.28 didn't work....
by "Flash" I hope you mean install.... not some other random process
Click to expand...
Click to collapse
Yeah... I just noticed it was broken. And yes, I meant install.
I am sorry, but I'm out of ideas.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Yeah... I just noticed it was broken. And yes, I meant install.
I am sorry, but I'm out of ideas.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
So, do you know if I can access/use ADB on a win7 pc when the archos doesn't have an aos on it?
http://forum.xda-developers.com/showthread.php?t=2104491&highlight=wlan
You could try this. it's written that it doesn't work on hdd model. but it can't get much worse it think. If I understand things correctly, you don't need to have installed any aos before installing this rom. with other roms you get a archos.ext4.update so you need a running system. yust give it a try but don't blame me if your tablet's completely dead afterwards. i don't know what will happen.
Or you could just follow the steps 1-7 (from link above!) to get cwm, maybe that helps for sth, but i don't know.
sry, but my writing style is bad. and do it on your own risk, I'm not that expirienced but that's what I would do...
Good luck
noaddress said:
http://forum.xda-developers.com/showthread.php?t=2104491&highlight=wlan
You could try this. it's written that it doesn't work on hdd model. but it can't get much worse it think. If I understand things correctly, you don't need to have installed any aos before installing this rom. with other roms you get a archos.ext4.update so you need a running system. yust give it a try but don't blame me if your tablet's completely dead afterwards. i don't know what will happen.
Or you could just follow the steps 1-7 (from link above!) to get cwm, maybe that helps for sth, but i don't know.
sry, but my writing style is bad. and do it on your own risk, I'm not that expirienced but that's what I would do...
Good luck
Click to expand...
Click to collapse
I gave up on this 6 months ago. but I turned it on 2 days ago and it magically worked.... Now, it's back in a bootloop again. Everything was working for two days, except sometimes the HDD wasn't reading the files, or the system wasn't detecting the HDD...
Could the HDD be damaged? If so, is there a way to check if it is (I was thinking about the ssd option)
Hello all.
As you might have guessed from the title, I recently broke my Galaxy SII's screen and I need to get all my precious info off it for my new S4 Active. Problem is, the screen is kept locked and with a broken screen I obviously can't unlock it in the normal manner. Fortunately the phone still works.
Unfortunately, my phone is unrooted and USB debugging is turned off (I think, I'm running on that assumption) so that doesn't help matters.
After some tinkering and learning (thanks to the sticky on recovery mode ) I have booted into recovery mode and have the Android SDK installed so while I can look at some things on the phone, not everything seems to be available.
Essentially, how can I get my data off my phone? It looks like I have to root the phone or something like that, but wouldn't that delete all my data (and thus defeat the purpose)?
Nothing like a broken screen to get you into learning Android development, and of course all responses are hugely appreciated
ArnoldJR28 said:
Hello all.
As you might have guessed from the title, I recently broke my Galaxy SII's screen and I need to get all my precious info off it for my new S4 Active. Problem is, the screen is kept locked and with a broken screen I obviously can't unlock it in the normal manner. Fortunately the phone still works.
Unfortunately, my phone is unrooted and USB debugging is turned off (I think, I'm running on that assumption) so that doesn't help matters.
After some tinkering and learning (thanks to the sticky on recovery mode ) I have booted into recovery mode and have the Android SDK installed so while I can look at some things on the phone, not everything seems to be available.
Essentially, how can I get my data off my phone? It looks like I have to root the phone or something like that, but wouldn't that delete all my data (and thus defeat the purpose)?
Nothing like a broken screen to get you into learning Android development, and of course all responses are hugely appreciated
Click to expand...
Click to collapse
It will depend on what data you're trying to get off the phone. My guess is photos/videos/music? If it's anything else, please specify.
You're on the right track, I'm pretty sure you'll need to root. But no, that won't delete any data My tip would be to root using Odin & Siyah kernel, as it's PC-based, if you were on JB 4.1.2 you'll need Siyah v6 (beta 4 or 5). The Odin link in my signature has a link which is an introduction to Odin flashing which you should find helpful. PC rooting with Odin (vs using Philz kernel) avoids using the busted screen for the rooting operation. Once you've flashed Siyah, you'll have root and a new custom recovery.
My next move would be to flash Dorimanx kernel, because it has an 'auto-mount' feature from recovery. Essentially that means the computer will recognise your internal SD (and external SD if you have one) as soon as you plug it in to your computer in recovery mode. To flash Dorimanx, you have a couple options. The easiest would be to download Dorimanx v8.43, and put it on a microSD card. Put that card in your phone, and from Siyah recovery, navigate to that file and flash it.
From there, reboot to your new recovery and plug into your computer. If all goes well then you can literally just copy your entire internal SD card to your computer and sift through for what you need
Hope that helps :highfive: Quote my post if you reply, else I won't notice it. I don't get time to go on Q&A much for now.
EDIT: Actually, an alternative would be not to flash Dorimanx on top of Siyah. From Siyah recovery, you could go: mounts & storage> mount USB storage and then plug into PC. Your PC should recognise it from there to copy all data from internal SD. If not, then flash Dorimanx for the auto mount feature.
hey.
my advice to you is to try using a "micro usb to hdmi" in most cases the touch works wile the screen does not.
its very common and cheep, i also suffered from the same problem, and i borrowed one from a friend, and thats what saved my data loss.
usually the phone interacts automatically with the usb-hdmi thing so you dont need to "click" on anything to make it work.
the touch tho is pretty tricky.. and you will learn it pretty fast!
hope one of your friends got one of these.. if not just buy one.. its a nice thing anyway.
hope i helped.
Hopper8 said:
It will depend on what data you're trying to get off the phone. My guess is photos/videos/music? If it's anything else, please specify.
You're on the right track, I'm pretty sure you'll need to root. But no, that won't delete any data My tip would be to root using Odin & Siyah kernel, as it's PC-based, if you were on JB 4.1.2 you'll need Siyah v6 (beta 4 or 5). The Odin link in my signature has a link which is an introduction to Odin flashing which you should find helpful. PC rooting with Odin (vs using Philz kernel) avoids using the busted screen for the rooting operation. Once you've flashed Siyah, you'll have root and a new custom recovery.
My next move would be to flash Dorimanx kernel, because it has an 'auto-mount' feature from recovery. Essentially that means the computer will recognise your internal SD (and external SD if you have one) as soon as you plug it in to your computer in recovery mode. To flash Dorimanx, you have a couple options. The easiest would be to download Dorimanx v8.43, and put it on a microSD card. Put that card in your phone, and from Siyah recovery, navigate to that file and flash it.
From there, reboot to your new recovery and plug into your computer. If all goes well then you can literally just copy your entire internal SD card to your computer and sift through for what you need
Hope that helps :highfive: Quote my post if you reply, else I won't notice it. I don't get time to go on Q&A much for now.
EDIT: Actually, an alternative would be not to flash Dorimanx on top of Siyah. From Siyah recovery, you could go: mounts & storage> mount USB storage and then plug into PC. Your PC should recognise it from there to copy all data from internal SD. If not, then flash Dorimanx for the auto mount feature.
Click to expand...
Click to collapse
I would like to get anything that's worth getting from the phone, so most important is the contacts and then photos/videos/app data.
It seems the link to download Odin is dead
Odin can be easily found with a Google search (or an XDA search). You're going to have to show at least a little bit of initiative if you want this done.
Edit - Also, you haven't specified which S2 variant you have. If you have any of the US variants, don't proceed with the above advice.
ArnoldJR28 said:
I would like to get anything that's worth getting from the phone, so most important is the contacts and then photos/videos/app data.
It seems the link to download Odin is dead
Click to expand...
Click to collapse
MistahBungle said:
Odin can be easily found with a Google search (or an XDA search). You're going to have to show at least a little bit of initiative if you want this done.
Edit - Also, you haven't specified which S2 variant you have. If you have any of the US variants, don't proceed with the above advice.
Click to expand...
Click to collapse
Just thought I'd make people aware of the dead link.
Phone variant is the I9100T (in Australia here).
Hopper's advice applies then.
ArnoldJR28 said:
I would like to get anything that's worth getting from the phone, so most important is the contacts and then photos/videos/app data.
It seems the link to download Odin is dead
Click to expand...
Click to collapse
I have no idea what you mean by the Odin link is dead. All links and attachments in my guide are up to date and working. I know, I just checked.
MistahBungle said:
Odin can be easily found with a Google search (or an XDA search). You're going to have to show at least a little bit of initiative if you want this done.
Edit - Also, you haven't specified which S2 variant you have. If you have any of the US variants, don't proceed with the above advice.
Click to expand...
Click to collapse
Good point, thanks. Had skimmed over the variant issue
Hopper8 said:
I have no idea what you mean by the Odin link is dead. All links and attachments in my guide are up to date and working. I know, I just checked.
Good point, thanks. Had skimmed over the variant issue
Click to expand...
Click to collapse
Not to worry, it was 404'ing for me, but I just went and googled it like Mistah said.
Flashing and pulling files from recovery mode worked like a charm so much appreciated, Hopper
ArnoldJR28 said:
Not to worry, it was 404'ing for me, but I just went and googled it like Mistah said.
Flashing and pulling files from recovery mode worked like a charm so much appreciated, Hopper
Click to expand...
Click to collapse
Good to hear it worked, and that you've got your data back :good: Now you know to keep regular backups of all the things you value, so get in that habit
Hopper8 said:
Good to hear it worked, and that you've got your data back :good: Now you know to keep regular backups of all the things you value, so get in that habit
Click to expand...
Click to collapse
Sorry to pester you but it seems I'm only halfway to the finish line. It looks like I only got some of my files and not others as when I "ls" folders in the shell like data, they're empty so I don't seem to have full access. Being Superuser doesn't let me see anything either.
Disregard, turns out all I had to do to see the contents of the /data folder was to mount it. The things you learn