Database Users

[Q] Xoom files doesnt change

Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this

wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day

You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?

If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?

Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?

okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.

Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .

okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now

I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?

Team Win Recovery Loop

Hello, I am new to XDA as being a member. This is my first post, and I promise I have spent at least an hour looking for similar threads to no avail.
Now to explain my problem,
Last night I rooted my kindle again after the 6.3 update that destroyed my last root. I used the Kindle Fire utility 9.5 by Vashypoo, and selected install permanent root with superuser.
As I discovered after this, I needed to get team win recovery before getting 6.3, so the KFU installed it for me, and it backed up my data before continuing with the rest of the root. After it said complete, I booted up my kindle, to find a yellow triangle and in a couple seconds, i got sent to this page automatically that I know now is the team win main menu. Every time I boot up my kindle, I get sent to the team win main page. I saw on a video by Nat3mil that the reason this was happening was because my kindle was automatically booting in recovery, so I tried to use kindle's bootmode menu to change the bootmode back to normal (4000) whenever I try, I get a message saying "The system cannot find the drive specified", and it would stop doing anything. I tried to manually set the bootmode back to normal by using command lines from a forum here on xda, similar to my problem, HOWEVER, whenever I try to connect my kindle to the pc, 9 out of ten times, my computer doesnt even recognize my kindle is connected, and when it does, it installs software, KFU says adb is online, and STILL whenever I try using KFU, command lines, or the Kindle Unbrick utility, it says "waiting for device". I literally cannot do a thing without help.... So to sum up, my problem is that I cannot connect my kindle to the computer, and second, I don't know what else to try... I really need help, and I have been doing tons of research (over six hours) to no avail, or progress.
Thank you for your time, and I hope that someone can help me.

Read this guide. It will give you an idea of what your problem is and what you are doing wrong. Its lengthy but worth it if you want do much with your Kindle, like installing recovery.
http://forum.xda-developers.com/showthread.php?p=23747567
Sent from my Amazon Kindle Fire using xda premium

your on the right path When you get it to say waiting for device hold the power button to shut the kindle off and then turn it back on and it will connect during boot up

soupmagnet said:
Read this guide. It will give you an idea of what your problem is and what you are doing wrong. Its lengthy but worth it if you want do much with your Kindle, like installing recovery.
http://forum.xda-developers.com/showthread.php?p=23747567
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread

MLS_Dumpster said:
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread
Click to expand...
Click to collapse
You have to get it to how you had it to say waiting for device... reinstall the drivers, reboot comp what ever you have to do than do what i posted... you can even open a command promp from the KFU tools folder by going to tools hold shift and right click... open command than type..
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot

It happens randomly, You see, another problem I have been having is that, My kindle has no problem connecting to the computer, in device manager, I have adb interface up and running, my kindle connected, but it isnt useable, it says my adb is offline, and whenever that happens, I cannot do a thing... There is no tred whatsoever as to how to get adb working, as it happens at random tries of me installing the drivers, and restarting my comp/kindle, do you have any idea how to get it working? Thanks by the way, You literally are a lifesaver.

MLS_Dumpster said:
It happens randomly, You see, another problem I have been having is that, My kindle has no problem connecting to the computer, in device manager, I have adb interface up and running, my kindle connected, but it isnt useable, it says my adb is offline, and whenever that happens, I cannot do a thing... There is no tred whatsoever as to how to get adb working, as it happens at random tries of me installing the drivers, and restarting my comp/kindle, do you have any idea how to get it working? Thanks by the way, You literally are a lifesaver.
Click to expand...
Click to collapse
Im on linux so idk how to set it up on windows.... i have read of people having issues with the drivers and having to reinstall them after using kfu.. id just make sure you delete the kindle driver and the android adb composite driver and start fresh.. or even try and mount it threw twrp mabe that will help

Thanks for helping me, seriously. Windows is annoying with drivers. I'll try what you suggested. Thanks again

DJLamontagneIII said:
Im on linux so idk how to set it up on windows.... i have read of people having issues with the drivers and having to reinstall them after using kfu.. id just make sure you delete the kindle driver and the android adb composite driver and start fresh.. or even try and mount it threw twrp mabe that will help
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU
IT WORKED. YOU, sir, are a life saver.
Thanks again.

MLS_Dumpster said:
THANK YOU THANK YOU THANK YOU THANK YOU
IT WORKED. YOU, sir, are a life saver.
Thanks again.
Click to expand...
Click to collapse
Awsome

MLS_Dumpster said:
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread
Click to expand...
Click to collapse
I wasn't trying to be rude but the exact problem you were having was covered in the thread that I posted along with the same solution suggested by DJLamontagnelll.
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
I wasn't trying to be rude but the exact problem you were having was covered in the thread that I posted along with the same solution suggested by DJLamontagnelll.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I think I sounded more harsh than I meant to be. The solutions on the thread only cover one of my problems, and thats the drive thing. Thanks, you did help.
Sent from my Kindle Fire using XDA

Hello.
I write to you because I have a big problem with mi LG G2 D802.
Yesterday I tried to install a CRM apk to use in a signature of the University. I was using CM11, but the apk had failed. So, I restored my ROM STOCK backup and when the phone start, a new update was downloaded and installed. Then, the phone only enter in recovery mode. I tried the different wipes, restore again ROM Stock, install again CM11 ROM but the problem was not solved.
I tried to enter in bootleader (pushing vol+ and insert the usb cable), but the phone reboot in recovery.
Now, I don´t know why, the phone is empty. I tried to restore ROM Stock backup from USB OTG but the recovery don´t recognizes the folders.
Please, can anybody help me? I need the pone!
Thanks.
Regards,
Nicolas.

nicolas_h18 said:
Hello.
I write to you because I have a big problem with mi LG G2 D802.
Yesterday I tried to install a CRM apk to use in a signature of the University. I was using CM11, but the apk had failed. So, I restored my ROM STOCK backup and when the phone start, a new update was downloaded and installed. Then, the phone only enter in recovery mode. I tried the different wipes, restore again ROM Stock, install again CM11 ROM but the problem was not solved.
I tried to enter in bootleader (pushing vol+ and insert the usb cable), but the phone reboot in recovery.
Now, I don´t know why, the phone is empty. I tried to restore ROM Stock backup from USB OTG but the recovery don´t recognizes the folders.
Please, can anybody help me? I need the pone!
Thanks.
Regards,
Nicolas.
Click to expand...
Click to collapse
Please post in correct forum. G2 Q&A, Help & Troubleshooting

[Q] Ooooppppssss.... NOOB.... Nexus 7 NO OS after failed root

Hi
Tried to root my new Nexus 7 on 4.2.1
It failed and somehow I managed to delete the OS??????
I can get it into bootlader and can find TWRP.
When I try to reboot it states NO OS installed.
Any suggestions? I have looked on the forums but cant find anything as I prob dont know what I am looking for.
Thank you in anticipation
Regards

capt208 said:
Hi
Tried to root my new Nexus 7 on 4.2.1
It failed and somehow I managed to delete the OS??????
I can get it into bootlader and can find TWRP.
When I try to reboot it states NO OS installed.
Any suggestions? I have looked on the forums but cant find anything as I prob dont know what I am looking for.
Thank you in anticipation
Regards
Click to expand...
Click to collapse
As long as bootloader is viable, you should be fine.
Download the FULL system image from Google:
https://developers.google.com/android/nexus/images#nakasi
Make sure you chose nakasi for WiFi or nakasig for 3G tablet, depending on the one you own.
Download file, extract tgz and extract zip inside of that.
Make sure you have adb/fastboot installed and in your path and that your tablet is connected and recognized. Boot into bootloader mode (which needs to be unlocked). Then do a full flash (you can omit the -w option to prevent the flash from wiping sdcard).
This will restore your device OS back to stock.
Depending on what you did, which you didn't really explain, there is probably a quicker/easier option. But without more info, the only advice I can give you is what I did, which should work fine for all circumstances.

Sticky post above this one is the solution..
It seems like you from your post you used a tool kit and something went wrong or you missed a step. Follow one of the following guides.
I recommend the first one..
Manual adb/fastboot
http://forum.xda-developers.com/showthread.php?t=1907796
Took Kits Automated flashing/ rom install ..
This one is a Windows interface.
......... http://forum.xda-developers.com/showthread.php?t=1766475..........
CMD Interface.
...............http://forum.xda-developers.com/showthread.php?t=1809195..........
I recommend the Manual method But only after reading post in all the threads. This will help you get a better understanding of Android..
Good Luck... the post above mine is also correct if you already have a adb environmental set up

Thank you
Thank you all for your advise
The nexus is once again alive
Have a very happy holiday season
Regards

Thank you
Thank you all for your advise
The nexus is once again alive
Have a very happy holiday season
Regards

how can I access my nexus, when I am in TWRP? windows cant connect to it cause of no driver..

jonny_pasta said:
how can I access my nexus, when I am in TWRP? windows cant connect to it cause of no driver..
Click to expand...
Click to collapse
Get the driver?
______________________________
Sent from my cellular telephone. Battery problems? >>>> http://forum.xda-developers.com/showthread.php?t=2461864

kj2112 said:
Get the driver?
______________________________
Sent from my cellular telephone. Battery problems? >>>> http://forum.xda-developers.com/showthread.php?t=2461864
Click to expand...
Click to collapse
no, you have to get to bootloader, I figured that out, now I'm sutck on "archive does not contain boot.sig" etc..

Hi
I got the same issue....
I can access the fastboot mode and the recovery mode, but not the bootloader. I go back on fastboot mode if I try to load bootloader...
I want to reinstall but windows doesn't recognize my n7 :/ so I'm stuck at this point :/

[Q] Bricked Nexus 7

so my nexus 7 (original) was getting laggy so i tried reflashing the factory image. It wasn't working, so i downloaded the nexus root toolkit and tried flashing the stock ROM. It erases the boot, cache, system, etc, but it keeps getting stuck on the "sending bootloader" part. It just says:
sending 'bootloader' <2100 KB>...
what should i do? is it my computer? i really don't want a bricked nexus. please help...

Try flashing in boot loader
Type : flash fastboot boot boot.img
in C:\Andriod or path of the adb

no one help you - if you can not get access to fastboot - buy new nexus
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

leeamsi97 said:
so my nexus 7 (original) was getting laggy so i tried reflashing the factory image. It wasn't working, so i downloaded the nexus root toolkit and tried flashing the stock ROM. It erases the boot, cache, system, etc, but it keeps getting stuck on the "sending bootloader" part. It just says:
sending 'bootloader' <2100 KB>...
what should i do? is it my computer? i really don't want a bricked nexus. please help...
Click to expand...
Click to collapse
The solution here is at least in part not to use the toolkit so you can see for yourself what is going wrong. Download the appropriate factory image for your device and the Android platform tools, and then you can use fastboot to flash the relevant images over.
The bigger question is what state your device is in. Are you able to kick the machine into fastboot mode still?
sambistt said:
no one help you - if you can not get access to fastboot - buy new nexus
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
This is possibly one of the most useless posts I have yet seen here. We don't even know the status of the OP's device.

This is possibly one of the most useless posts I have yet seen here. We don't even know the status of the OP's device.
Click to expand...
Click to collapse
my post help him, your post just waste of time
- if him can`t access device via fastboot - how can it resolve command from it?
don`t bully this user - you cann`t help him - its not soft bricked !!!

sambistt said:
my post help him, your post just waste of time
- if him can`t access device via fastboot - how can it resolve command from it?
don`t bully this user - you cann`t help him - its not soft bricked !!!
Click to expand...
Click to collapse
Him no say him no can use fastboot. You assume too much and obviously have no clue what you're talking about.
Sent from my Nexus 7 using xda app-developers app

sambistt said:
my post help him, your post just waste of time
- if him can`t access device via fastboot - how can it resolve command from it?
don`t bully this user - you cann`t help him - its not soft bricked !!!
Click to expand...
Click to collapse
I'm not "bullying" anyone, I'm pointing out that your post is based off of nothing but conjecture right now. If OP killed even fastboot then yes, his options are limited, but your post is inviting an even larger waste of time based on inadequate information-- which is exactly how these problems occur.

Solved
Thanks everyone. I got it to work. I should have mentioned that i did use flashboot initially but used the toolkit when it didn't work. In the end, I finally got fastboot to flash the image. Thanks again for replying.

where can I go for help?

Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?

permutations said:
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
Click to expand...
Click to collapse
Have you tried booting to recovery from bootloader and regaining an ADB connection? This should be all you need.

permutations said:
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
Click to expand...
Click to collapse
The more information you provide, the better. Please provide more information regarding your device so that your thread can be placed in the correct forum.

Magnum_Enforcer said:
The more information you provide, the better. Please provide more information regarding your device so that your thread can be placed in the correct forum.
Click to expand...
Click to collapse
I was updating my Nexus 10 tablet - had gotten to the system partition - when I lost the ADB connection. I've since learned that's a problem with newer Macs (I was connected to Windows through Parallels). Here's a link to a thread about that:
https://code.google.com/p/android/i...Stars Reporter Opened&groupby=&sort=&id=65301
Because of the lost connection, the system partition did not flash and my tablet is bricked. There is no operating system so it can't boot into Android, but it can boot into the Bootloader and Recovery mode. All the other partitions are fine.
I have a custom recovery (TWRP) and an unlocked bootloader, but I'm at a loss to figure out how to flash the system.img file. I can't boot to Android so I can't connect through ADB in Fastboot mode to flash the ordinary way. I am connected through ADB when I'm in Recovery mode, but I can't use the flash command in Recovery mode. Nor can I figure out a way to make TWRP flash the partition by running it as a zip file - mainly because I can't figure out what the update.zip file should consist of. There was an OTA update file on my device when I started the manual update (manual updates fail), but I didn't look at it and didn't save it.
I tried pushing the system.img file to the Nexus 10 using the Linux dd command, but that doesn't work with the system partition, which uses a special format. The details are explained here, but I don't fully understand it:
http://www.modaco.com/forums/topic/327661-how-to-backup-the-systemimg-bootimg-and-recoveryimg/
After spending about 8 hours on this last night, I believe the only way I can fix it is to create an update.zip file that uses a Linux script to flash the system partition, but this is way beyond my skill set and I can't find a model for how to do this anywhere. All tutorials I've found for creating zip files for flashing are for installing apps, not flashing a system partition - which is even more complicated than flashing, say, a boot partition. Nor can I find an update.zip file from someone's cache (sure wish I'd saved mine) to use as a model. I'm looking for someone with this kind of high level knowledge who can give me guidance - or someone who can refer me to someone who has this kind of knowledge.

I solved this problem.