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)
Related
Currently I have a rooted Sensation.
I tried to install a theme using Rom Manager.
It said it installed successfully.
I reboot.
And when I boot up everything is weird. The drop shadow on all windows is green.
The Desktop isn't showing at all.
I can select applications from the locked menu. (Before I unlock) Like camera, mail etc.
Any thoughts on what might be wrong and how to fix?
Themes may require you to have a de-odexed rom. Is the rom you have odexed or de-odexed?
Either that, or you downloaded a bad file. Re-download and install again to see if it works.
Dave2582 said:
Themes may require you to have a de-odexed rom. Is the rom you have odexed or de-odexed?
Either that, or you downloaded a bad file. Re-download and install again to see if it works.
Click to expand...
Click to collapse
I don't know what odexed means.
I have tried to install it again.
And maybe I should mention that I installed it through bootloader? Recovery or what it is called.
I saw that you were able to install other themes simply using the apk file. But this one required you to install it through recovery.
Currently I am able to take photos and call people. There's no home screen.
When I try to view messages I get an error.
Is there any way I can like reset it to before I installed the theme? I was told to back it up before installing the theme, which I didn't do. Any other way to fix this?
Check out this thread. It will help you get back to a stock rom, since you never made a backup.
I would strongly advise to to backup up everything before you start messing around. That way you have a backup to fall back on in case something like this issue happens.
When I first started messing around with root and custom roms, I never did a nandroid, and the phone was bootlooping. So I had to start over from scratch.
Dave2582 said:
Check out this thread. It will help you get back to a stock rom, since you never made a backup.
I would strongly advise to to backup up everything before you start messing around. That way you have a backup to fall back on in case something like this issue happens.
When I first started messing around with root and custom roms, I never did a nandroid, and the phone was bootlooping. So I had to start over from scratch.
Click to expand...
Click to collapse
Tried Method 2 of debranding since it was the easiest one. Made no difference.
Trying Method 1 right now. Will report back with progress.
Just realized that I am not able to use Method 1 since it requires me to have USB Disk Drive mounted, which I can only do from recovery mode. And since I did not remove the image file it now constantly asks me if I want to update in HBOOT. So I can't really get past it.
If I update, it updates and reboots. If I click cancel it reboots.
What should I do?
Run a RUU. Which carrier are you coming from?
Dave2582 said:
Run a RUU. Which carrier are you coming from?
Click to expand...
Click to collapse
Did you not read my post?
I can not do anything in recovery mode, I.e not enable disk drive.
Just to clarify: There is no way of transferring ANY files from my PC to my phone that I am aware of at the moment.
You should take this into consideration before you come telling me to install stuff.
P1raten said:
Just to clarify: There is no way of transferring ANY files from my PC to my phone that I am aware of at the moment.
Click to expand...
Click to collapse
ever tried plugging your sdcard into your computer?
P1raten said:
You should take this into consideration before you come telling me to install stuff.
Click to expand...
Click to collapse
i smell a little attitude. you should take into consideration that this is not a customer support site. no one has to help you. so please be courteous, even if it means repeating what youve already said.
sweetnsour said:
ever tried plugging your sdcard into your computer?
i smell a little attitude. you should take into consideration that this is not a customer support site. no one has to help you. so please be courteous, even if it means repeating what youve already said.
Click to expand...
Click to collapse
I do not have an adapter.
P1raten said:
Did you not read my post?
I can not do anything in recovery mode, I.e not enable disk drive.
Click to expand...
Click to collapse
I said to run a RUU. It stands for Rom Utility Update. This is an executable program that you can run from the PC to your phone. It will take an image that was made specifically for your phone and flash over what you currently have, and once it's done and you power your phone on, it should look like you just took the phone out of the box. Download the RUU that matches your phone to the PC. Be sure that you pick the right one. Run the RUU on your PC. It will instruct you what to do as far as plugging your phone to the PC, when to turn it on/off, etc.
Once the program finishes, your phone should be reset, stocked, and back to normal.
Dave2582 said:
I said to run a RUU. It stands for Rom Utility Update. This is an executable program that you can run from the PC to your phone. It will take an image that was made specifically for your phone and flash over what you currently have, and once it's done and you power your phone on, it should look like you just took the phone out of the box. Download the RUU that matches your phone to the PC. Be sure that you pick the right one. Run the RUU on your PC. It will instruct you what to do as far as plugging your phone to the PC, when to turn it on/off, etc.
Once the program finishes, your phone should be reset, stocked, and back to normal.
Click to expand...
Click to collapse
How do I check which version is on my phone so I do not pick the wrong one.
P1raten said:
I do not have an adapter.
Click to expand...
Click to collapse
Buy one off EBay it only cost £2
Sent from my HTC Sensation
Ok, I was able to fix so that I can moun the USB Mass Storage device in Revolutionary CWM(In HBOOT). But the setup can not find my phone.
Any tips on how to deal with this? Is there maybe a way of installing a zip from the sdcard?
Okay, so I got my phone semi running like before.
And I plugged it into my computer and choose HTC Sync.
My phone was picked up by the computer.
So I tried starting the setup. And it worked!
Great success!
P1raten said:
Okay, so I got my phone semi running like before.
And I plugged it into my computer and choose HTC Sync.
My phone was picked up by the computer.
So I tried starting the setup. And it worked!
Great success!
Click to expand...
Click to collapse
I'm glad you got it working. Just have some patience if you run into problems.
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
neonblur said:
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
Click to expand...
Click to collapse
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
neonblur said:
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
Click to expand...
Click to collapse
yea that inf file is the one you need to modify. but you already have adb composite interface... so that means drivers are installed.
what happens when you do adb devices after you get into cwm. what's the output?
Sent from my Nook Tablet CM7 BETA using xda premium app
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
neonblur said:
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
Click to expand...
Click to collapse
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
neonblur said:
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
Click to expand...
Click to collapse
ok well now you have adb working. now the problem is how to fix your problem lol... I'll see if I can think of something.
in the meantime can you go into detail as to how you got tto your current situation?
EDIT: do you get any errors when booting into cwm? like not being able to mount a certain drive or something?
Sent from my Nook Tablet CM7 BETA using xda premium app
no errors booting into cwm internal and never had a problem when booting into it from an sd card. i flashed it internally hoping it would be a little easier seeing as how i only have one sd card but i am going to go get another today just to work through this.
nook started on 1.4.3 i rooted it using brianf23 and indirects sd card method. market and everything worked great. so i flashed Veronica's CM7beta_ribbon_ICS rom. everything for the most part was working, tho i did notice that some menu items would not open for me but they were noting i really needed to mess with at the time. so i installed a few apps and was done for the day. turned it on the next day and got stuck in a bootloop, so powered off and rebooted but got the same bootloop. booted into recovery did the standard dalvik cache ect and reflashed the rom, hoping this might fix the loop. upon rebooting is when i got stuck at the 'please reboot your device' screen. i have tried several methods of just flashing to stock ect, formatted my sd correctly and made sure it was active to try and flash back to stock that way but my nook will not boot from sd. so 12+ hours later i hung my head and asked for help lol! thanks to you i am able to start ADB no clue what to do but hey....step in the right direction!
Happy Dance
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
neonblur said:
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
Click to expand...
Click to collapse
good job on the fix. glad to help
Sent from my Nook Tablet CM7 BETA using xda premium 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..
Hi there,
I have been given a Sony Tablet S (S1) by a family member who said if i can fix it i can keep it. Im used to rooting phones and other tablets but I just want to make sure I'm not going to make this worse.
Basically the tablet is soft bricked and stays on the Sony boot screen. I can enter recovery. As far as I can tell, the tablet got this way after it lost power in the middle of an official OTA update.
What recovery image should I be using to instal on the recovery screen? HC, ICS? ive been looking for a while and I'm either just finding dead links or rooted images.
Whatever I try it has to be something i can put on the sd and access from the recovery as i cannot get my computer to recognise the tablet for any adb stuff.
4743hudsonj said:
Hi there,
I have been given a Sony Tablet S (S1) by a family member who said if i can fix it i can keep it. Im used to rooting phones and other tablets but I just want to make sure I'm not going to make this worse.
Basically the tablet is soft bricked and stays on the Sony boot screen. I can enter recovery. As far as I can tell, the tablet got this way after it lost power in the middle of an official OTA update.
What recovery image should I be using to instal on the recovery screen? HC, ICS? ive been looking for a while and I'm either just finding dead links or rooted images.
Whatever I try it has to be something i can put on the sd and access from the recovery as i cannot get my computer to recognise the tablet for any adb stuff.
Click to expand...
Click to collapse
What was the android version revision? r1a,r5,r5a?
If you can access recovery try the latest update from stiflizs sig or his post "faq please sticky this" in general try flashing it twice with the tablet either pluged in or fully charged also try installing the drivers manually thru device manager on pc. Your sd card must be fat32 formatted with the ota update or thetab will not see it
By the sounds of it you might have to push the update thru adb or part there of as the previous attempt might have changed your incremental higher and it wont take the same update again get a logcat after the flash and post here fot stif to look at
If you explain the situation to sony they might fix for free that's a big might
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
4743hudsonj said:
Hi there,
I have been given a Sony Tablet S (S1) by a family member who said if i can fix it i can keep it. Im used to rooting phones and other tablets but I just want to make sure I'm not going to make this worse.
Basically the tablet is soft bricked and stays on the Sony boot screen. I can enter recovery. As far as I can tell, the tablet got this way after it lost power in the middle of an official OTA update.
What recovery image should I be using to instal on the recovery screen? HC, ICS? ive been looking for a while and I'm either just finding dead links or rooted images.
Whatever I try it has to be something i can put on the sd and access from the recovery as i cannot get my computer to recognise the tablet for any adb stuff.
Click to expand...
Click to collapse
See my FAQ and links for updates, both in my signature. Try the latest update 120914XXX for your region device Done
smgdev said:
What was the android version revision? r1a,r5,r5a?
Click to expand...
Click to collapse
How could I find out? I can only enter recovery.
I've attached what appears when I'm in recovery
dex9mm said:
If you can access recovery try the latest update from stiflizs sig or his post "faq please sticky this" in general try flashing it twice with the tablet either pluged in or fully charged also try installing the drivers manually thru device manager on pc. Your sd card must be fat32 formatted with the ota update or thetab will not see it
By the sounds of it you might have to push the update thru adb or part there of as the previous attempt might have changed your incremental higher and it wont take the same update again get a logcat after the flash and post here fot stif to look at
If you explain the situation to sony they might fix for free that's a big might
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
stifilz said:
See my FAQ and links for updates, both in my signature. Try the latest update 120914XXX for your region device Done
Click to expand...
Click to collapse
Thanks guys I'll try this tomorrow and post back if it works
Having some trouble here. I have tried numerous links now and all of them when transferred to my SD (or any other flash device) come up with the message "please insert the last disk of the multi-volume set". Windows also cannot open the folders and just says the zips are empty. I have tried new and old UK, US and AUS zips from the sony links in your thread and our own 4shared account stifilz. Whats going on???
4743hudsonj said:
Having some trouble here. I have tried numerous links now and all of them when transferred to my SD (or any other flash device) come up with the message "please insert the last disk of the multi-volume set". Windows also cannot open the folders and just says the zips are empty. I have tried new and old UK, US and AUS zips from the sony links in your thread and our own 4shared account stifilz. Whats going on???
Click to expand...
Click to collapse
For starters they are encrypted so you won't be able to unzip them normally. You are copying the intact zip over? Will be a problem with you pc then. Do you have another to try?
stifilz said:
For starters they are encrypted so you won't be able to unzip them normally. You are copying the intact zip over? Will be a problem with you pc then. Do you have another to try?
Click to expand...
Click to collapse
I thought that but I downloaded one on my other tab, transferred it to its SD and tried that. The sony tab still could not see it.
stifilz said:
For starters they are encrypted so you won't be able to unzip them normally. You are copying the intact zip over? Will be a problem with you pc then. Do you have another to try?
Click to expand...
Click to collapse
I have just tried downloading the file directly from chrome into the SD. The tab still doesn't see anything. After clicking "Update system from SD card" this is what I get...
4743hudsonj said:
I have just tried downloading the file directly from chrome into the SD. The tab still doesn't see anything. After clicking "Update system from SD card" this is what I get...
Click to expand...
Click to collapse
Yellow line at the bottom.... Either your SD card is buggered (or needs a format) or you tablet can't mount the sdcard??
stifilz said:
Yellow line at the bottom.... Either your SD card is buggered (or needs a format) or you tablet can't mount the sdcard??
Click to expand...
Click to collapse
Unfortunately the latter. I have tried 2 cards both formatted to FAT32. I guess this isn't looking good?
4743hudsonj said:
Unfortunately the latter. I have tried 2 cards both formatted to FAT32. I guess this isn't looking good?
Click to expand...
Click to collapse
Damn, must be the tablet then. Not looking good I'm afraid.
Hi guys,
I've been using my Sola for over a year now and I like the phone, i got the CM9 build from freeXperia on it (FXP 210 CM 9 PEPPER) with cwm on it and loved it.
Two weeks ago trouble began when the phone was very unreliable, it rebooted several times a day, sometimes I noticed that the phone got very warm when rebooting.
I found out that there was no diskspace left, so I deleted some of the playlists on Spotify that I downloaded and that gave me back about 2 gb of internal room.
Since yesterday some processes where quitting and this happened a couple of times (it was the google media process), this morning after being on the adapter for the night the problem was still there. So I rebooted the phone (normal reboot) and then the trouble really kicked in.
When I boot now I see a message stating "Android is being updated, starting apps" then I see my normal lockscreen and the errors start rollling in.
The only errors I can see are the "android.phone process stopped working" and "NFC service stopped". When I press close on those they keep coming back, so fast I cant't even get past my lockscreen anymore.
On the phone is some very critical data to me, I have to restore that data (its in a encrypted app database). As long as I can save that data and restore it to use when the android/app is restored I'm fine.
Can someone give me advise on how to continue?
**bump, I really need my phone
VeldMuijz said:
**bump, I really need my phone
Click to expand...
Click to collapse
Bump! Getting desperate here...
VeldMuijz said:
Bump! Getting desperate here...
Click to expand...
Click to collapse
Where is that data located? If it's on internal memory in it's own directory it will remain intact if you repair/flash firmware.
EDIT: some other thoughts, try to remove the SIM or switch to airplain mode.
I'm not 100% percent sure where it is located, It's on the internal memory but I'm not sure if where it is exactly. It's a database of an app.
Won't I lose all my files on reflash? Reflash can be done with fastboot right? And I should reflash the firmware (kernel?)? Not the rom itself?
Already tried rebooting with SIM and sdcard out, no luck though.
No luck on connecting to ADB, I tried but USB debugging is turned off and my drivers seem to let me down... I can get connect to fastboot
Other ideas?
VeldMuijz said:
I'm not 100% percent sure where it is located, It's on the internal memory but I'm not sure if where it is exactly. It's a database of an app.
Won't I lose all my files on reflash? Reflash can be done with fastboot right? And I should reflash the firmware (kernel?)? Not the rom itself?
Already tried rebooting with SIM and sdcard out, no luck though.
No luck on connecting to ADB, I tried but USB debugging is turned off and my drivers seem to let me down... I can get connect to fastboot
Other ideas?
Click to expand...
Click to collapse
Too bad USB debugging is off.
If database is on device memory than it will be lost if you wipe data on flash. If you don't wipe data you may still have those errors, but you can take your chances and try without wiping data.
Yes with flashtool, do you have the FTF file for the firmware you are currently using?
Is it tooted and have CWM on it?
I don't have the FTF anymore, but I know where to find it.
Luckily I have CWM on it.
Do I have to reflash with the zip or just run the update?
VeldMuijz said:
I don't have the FTF anymore, but I know where to find it.
Luckily I have CWM on it.
Do I have to reflash with the zip or just run the update?
Click to expand...
Click to collapse
I think best is to make your own FTF.
Start repair with PC Companion, and when it finish downloading the files and ask to shut down the phone, stop and create the FTF as explained here.
The FTF can only be flashed with flashtool.
I don't mean to sound rude but why do I want my own FTF?
Do you mean a FTF from the OEM firmware, they can be downloaded from XDA as well.
Or do you mean creating an FTF from the files that are now on my phone?
VeldMuijz said:
I don't mean to sound rude but why do I want my own FTF?
Do you mean a FTF from the OEM firmware, they can be downloaded from XDA as well.
Or do you mean creating an FTF from the files that are now on my phone?
Click to expand...
Click to collapse
I've seen a few people hat flashing firmware they download didn't work well for them but flashing with SUS or PCC did.
I'm not twisting your hand, if you rather use FTF you can download somewehere and it works then do that.
Ok so i tried to flash the kernel, the flashing went well but the error persists.
I think it's time to conclude that my data is gone..
It gave me some headaches and I sweared a lot but i got it working again.
I've flashed the boot.img, didn't resolve the issue.
I've updated the same rom over my old rom, didn't solve the issue.
I wiped cache only (to try and see if it would work) and this worked.
So it might have been a cache problem after all.
The updating android thingy was shown again only this time it said it had to update 100+ apps, and it did. After that I could use my phone again.
First things first, lets make a backup .
Thanks ChickeD (i've thanked you on XDA for your help)
This can be marked as [RESOLVED]