Related
I'm not too sure how many people know this, but when Kies is downloading your new ROM, you can copy it and put it somewhere on your hard drive for use later on (if necessary).
On my computer (Windows XP) Kies puts the ROM in the temp folder, on my computer, here...
C:\Documents and Settings\Ian\Local Settings\Temp, where Ian is my name on my computer, you go to where all your files are located.
While downloading the new ROM it'sin a temp file called tmp1B2.tmp.
Once it's done, it puts the file in a folder called tmp1B2.tmp.zipfolder
Just copy the file from this folder and paste it anywhere you want.
The file will disappear after your phone is finished upgrading, so make sure you don't wait too long.
Ian
Thanks! Though I don't suppose there is a method of actually getting the firmware WITHOUT actually going through the process of upgrading?
You can also download the firmware straight from Samsung using check fus downloader without even having to run kies.
Sent from my GT-I9000M using Tapatalk
Can someone take a look at this picture and tell me why my SDK is not updating to revision 16? It keeps giving me an error and I've tried turning the antivirus off too.. Thanks again!
Yeh, that happens for the SDK Tools bit. Just go into android-sdk/temp and extract the tools zip file and copy that into the android-sdk folder, replacing the original and outdated tools folder. If that doesn't work and gives an error, move the zip file elsewhere e.g. desktop and extract and replace the original tools folder in android-sdk.
Thank you so much! Worked like a charm!
HTC Thunderbolt & ASUS Transformer Rooted!
Congratulations I might buy myself a Transformer Prime when it comes out in Australia, sounds like a very worthwhile buy. Anywho, back on topic, I never bothered to figure out why the SDK update fails like that though I have a sneaking suspicion that one of the smaller components/tools may be open whilst it is updating or it might just be glitched.
You should, it seems like it will be a great tablet! But I think it might be a glitch, but I don't know. Everything worked smoothly after it transferred though.
Hi guys.
I was playing with my rooted device, but something went wrong after upgrading SuperUser from the market and
I wasn't unable to login as root anymore (neither through adb nor through terminal emulator).
The tremendous problem is that in the meanwhile I have got rid of all Lenovo useless apps, but also of Mobility Manager! Without this program I am not able to apply the rooting exploit again!!!
So, please, someone could send me the Mobility manager apk (I was in 0076_WE)? Is there a way I could restore the 0076_WE full image?
Thanks a lot!
UPDATE: I found the Mobility Manager apk, but even if I reinstalled it, the root exploit is still not working! I guess I have to try with a full image!
there aren't full roms as far as i know but you can download your version here:
http://download.lenovo.com/slates/think/tablet1/
Don't know if its flashable again but you can extract the zip files an get the mobility manager apk.
Koshu said:
there aren't full roms as far as i know but you can download your version here:
Don't know if its flashable again but you can extract the zip files an get the mobility manager apk.
Click to expand...
Click to collapse
Unfortunately, even if I reinstall Lenovo mobility manager, it goes under the "data" folder not the system one. From there, the root exploit doesn't work!!!
jck_dnt said:
Unfortunately, even if I reinstall Lenovo mobility manager, it goes under the "data" folder not the system one. From there, the root exploit doesn't work!!!
Click to expand...
Click to collapse
Tried to reflash the image from lenovo?
jck_dnt said:
Unfortunately, even if I reinstall Lenovo mobility manager, it goes under the "data" folder not the system one. From there, the root exploit doesn't work!!!
Click to expand...
Click to collapse
Have you tried to do a reset from privacy menu?try to back up what ever is important on the internal SD cause it will be formatted
Sent from my ThinkPad Tablet using Tapatalk
Okay, now i have three cases with my phone when the phone boots up
1.Hello moto boot animation with sound
In this case my phone works fine (only for few minutes though )
2.Hello moto boot animation without sound
In this, i cant hear any audio from my phone speaker , have to put on my headphones even to answer a call
3.No hello moto animation
Now, its gone, i couldnt use any app related to sound, no music,no calls nothing related to sound, ive to reboot my phone until any of the first two cases to come.
Model:XT1643
Variant:India
Current Rom: nougat 7.0.0(hope ive flashed the perfect stock)
Note: Ive unlocked my bootloader, this problem appeared after some good 20 days
Things that i already did:
1.Factory reset
2.Flashed RR,CM and some other roms
3.Flashed vegito and other kernels
4.Relocked the bootloader
5.Flashed many stock roms
6.All primitives(safe mode,factory mode,clearing cache,wiping dalvik)
7.Saw the logs and found something like
/proc/asound/card---- state failed no such directory found
Now im on my stock rom with bootloader locked.Till yesterday i was in case 2 but phone switched off due to low batter and when i power it on now my phone is back to the worst case 3.
Please help me , i hope xda forums got many android experts and developers
From Case 1 and 2.
I have seen this similar problem (on old Nokia phone), on my phone that happened because of water damage, few drops of water went to jack and it started to show "connected headphone" so it stopped playing music through speaker but worked fine with earphones..
It's rainy season, can you confirm this?
About 3rd case,
it iss un-understandable, can you tell more about that?
Also you have filled half post with what you have done to solve this, i would suggest you to write condition of phone before this happened, what actually you did before this problem started ? This will help others to understand problem..
Edit: about error in log,
Are you still on unlocked bootloader ?
Can you tell, (use any root browser / file manager)
Is there anything in /proc/asound/ ?
In my phone 6 files and card folder (shortcut to msm8952*****) contains other 200+ files...
____Mdd said:
From Case 1 and 2.
I have seen this similar problem (on old Nokia phone), on my phone that happened because of water damage, few drops of water went to jack and it started to show "connected headphone" so it stopped playing music through speaker but worked fine with earphones..
It's rainy season, can you confirm this?
About 3rd case,
it iss un-understandable, can you tell more about that?
Also you have filled half post with what you have done to solve this, i would suggest you to write condition of phone before this happened, what actually you did before this problem started ? This will help others to understand problem..
Edit: about error in log,
Are you still on unlocked bootloader ?
Can you tell, (use any root browser / file manager)
Is there anything in /proc/asound/ ?
In my phone 6 files and card folder (shortcut to msm8952*****) contains other 200+ files...
Click to expand...
Click to collapse
3rd case i mean moto boot involves
big M moto logo and then hello world and then some animation with sound
in the 3rd case only Moto logo will be shown for some seconds and phone boots up
And yeah, i can confirm that my phone's never been wet
the problem started when i tried rooting my phone, i successfully unlocked the bootloader and flashed wrong supersu file(I was a noob in this stuff back then).ended up in boot loop,Flashed some stock rom available in the net and phone worked perfectly for some days before this problem begun.
Since i dont have root access, i guess i couldnt access /proc/asound/
and now i have a locked bootloader
thanks for your time on replying my post
Warm regards.
Can you try to re-unlock it ?
[It's DARK here, i will not check any threads now, but suggest you to check threads in Q&A section about re-unlocking bootloader after updating to latest firmware, i don't wish any buddy's phone gets damaged, so please check]
Then see /proc/asound/
I will provid one from mine xt1643 if yours is something wrong..
Another question: does this happen with custom ROM too ?
Yeah sure, I will reunlock the bootloader,
Do I have to root my phone or reunlocking is sufficient to see system files?
And one more question
In twrp recovery I found fix se Linux contexts
Can I do that? Safe to do ? Does it have any chance of solving my problem?
Im quite experienced in locking and unlocking bl
I'll do it tomorrow and post the result here.
And yeah same with custom Roms also
Facing the same problem too
https://forum.xda-developers.com/moto-g4-plus/help/audio-moto-g4-plus-completely-zero-sound-t3637714
Just unlocked boot loader and rooted so, these are the files in my /proc/asound directory .
So the card folder and the shortcut is missing..please send me
Karthik Veenam said:
7.Saw the logs and found something like
/proc/asound/card---- state failed no such directory found
Click to expand...
Click to collapse
As here log said, "card" folder is missing in asound folder (your SS)
Check my SS, i am little confused about sharing card folder, because there is shortcut folder msm8952***** that directs to same card folder.
____Mdd said:
As here log said, "card" folder is missing in asound folder (your SS)
Check my SS, i am little confused about sharing card folder, because there is shortcut folder msm8952***** that directs to same card folder.
Click to expand...
Click to collapse
Can you mail me the entire proc folder?
i have taken it with different methods,
1st: i took flashable zip of /proc/asound with "zipME" app,
here: https://drive.google.com/file/d/0BwXhUjfgNMqyVnhyME8yREc2TXc/view?usp=drivesdk
2nd: copied with file manager, you have to unzip and paste into /proc/asound/
Here: https://drive.google.com/file/d/0BwXhUjfgNMqyQjJfNFlvLTM0Y28/view?usp=drivesdk
PS: i have taken whole asound folder, i suggest you to 1st copy card folder only and see..
____Mdd said:
i have taken it with different methods,
1st: i took flashable zip of /proc/asound with "zipME" app,
here: https://drive.google.com/file/d/0BwXhUjfgNMqyVnhyME8yREc2TXc/view?usp=drivesdk
2nd: copied with file manager, you have to unzip and paste into /proc/asound/
Here: https://drive.google.com/file/d/0BwXhUjfgNMqyQjJfNFlvLTM0Y28/view?usp=drivesdk
PS: i have taken whole asound folder, i suggest you to 1st copy card folder only and see..
Click to expand...
Click to collapse
Can you suggest me a good root browser for doing the copy paste operations? Everything sucks in my phone.
And thanks a ton
____Mdd said:
i have taken it with different methods,
1st: i took flashable zip of /proc/asound with "zipME" app,
here: https://drive.google.com/file/d/0BwXhUjfgNMqyVnhyME8yREc2TXc/view?usp=drivesdk
2nd: copied with file manager, you have to unzip and paste into /proc/asound/
Here: https://drive.google.com/file/d/0BwXhUjfgNMqyQjJfNFlvLTM0Y28/view?usp=drivesdk
PS: i have taken whole asound folder, i suggest you to 1st copy card folder only and see..
Click to expand...
Click to collapse
Bro none of the root browser can paste successfully.
So the other choice is flashing the zip directly in twrp ryt?
Karthik Veenam said:
Can you suggest me a good root browser for doing the copy paste operations? Everything sucks in my phone.
And thanks a ton
Click to expand...
Click to collapse
I am using X-Plore since symbian.. LoL. It provides good facilities, but for new user it may be confusing as it has dual pane view and stuff..
But i have seen most of users prefer ES file explorer and solid explorer... You can try them, and see what makes your work easy..
____Mdd said:
i have taken it with different methods,
1st: i took flashable zip of /proc/asound with "zipME" app,
here: https://drive.google.com/file/d/0BwXhUjfgNMqyVnhyME8yREc2TXc/view?usp=drivesdk
2nd: copied with file manager, you have to unzip and paste into /proc/asound/
Here: https://drive.google.com/file/d/0BwXhUjfgNMqyQjJfNFlvLTM0Y28/view?usp=drivesdk
PS: i have taken whole asound folder, i suggest you to 1st copy card folder only and see..
Click to expand...
Click to collapse
Not enough space in directory(root) so do u advice me to flash in twrp?
Karthik Veenam said:
Not enough space in directory(root) so do u advice me to flash in twrp?
Click to expand...
Click to collapse
Try and report..
I flashed but nothing happened and the files were not added I'm the directory..the directory still remains the same
Are you sure u gave the correct directory to the flashable zip?
Karthik Veenam said:
I flashed but nothing happened and the files were not added I'm the directory..the directory still remains the same
Are you sure u gave the correct directory to the flashable zip?
Click to expand...
Click to collapse
Yes those were taken form correct directory, but surprisingly those are getting overwriten at some time events, i just restarted my device and you can see it's date/time is close to clock (ss attached)... It's something issue with your device that it's not getting written..
Yeah, but copy pasting the missing folder will atleast work as a temp fix,
Can't I do anything to do that? I mean copy paste in the directory
And yeah even my 6 files are modifying with time, but those folder and shortcut is missing
It's full of surprise, can you check that with xplore (available on playstore)
TWRP is also not showing those folder but x-plore does..
____Mdd said:
It's full of surprise, can you check that with xplore (available on playstore)
TWRP is also not showing those folder but x-plore does..
Click to expand...
Click to collapse
It gives me the error " some files couldn't be copied"
Hey everyone,
I'm trying to comply update to my device using the B32 firmware downloaded on ZTE USA Support site. The file is large, too large for FAT32, at 5.39GB.
I have tried copying it using android transfer on my mac, ejecting the microSD and using a regular SD adapter and copying it that way, and I have also tried just downloading right from the Software Update screen. The first two methods errored with (https://ibb.co/kjh4yG).
The software update fails with a message explaining that the firmware found and downloaded by the phone does not match the device...?
I have been on the old firmware for what feels like a year now. I'm hoping you all can shed some light on this.
Thanks
macboss said:
Hey everyone,
I'm trying to comply update to my device using the B32 firmware downloaded on ZTE USA Support site. The file is large, too large for FAT32, at 5.39GB.
I have tried copying it using android transfer on my mac, ejecting the microSD and using a regular SD adapter and copying it that way, and I have also tried just downloading right from the Software Update screen. The first two methods errored with (https://ibb.co/kjh4yG).
The software update fails with a message explaining that the firmware found and downloaded by the phone does not match the device...?
I have been on the old firmware for what feels like a year now. I'm hoping you all can shed some light on this.
Thanks
Click to expand...
Click to collapse
You have two ways to do this:
-If your internet is decent enough just forget about the SD card and download the update on your phone. Afterwards, download 'RAR' from the play store, find the downloaded file (in Downloads), and open the zip file. If you find a PDF and a file called 'update.zip' inside, simply select it and unzip it to the root of your sd card (put '/storage/emulated/0/ on the Destination path). So you will have an 'update.zip' file there. You don't need to unzip this one. Now go to Settings, Updates, then let it scan and it should find the file, update and voila
-Format your SD Card to exfat and pop the file right in
It's weird that the update file is that huge, since usually files for the A2017G are around 2.1 gigs
It worked my friend!!!
I installed RAR, then went inside the downloaded file, found update.zip and unzipped it to '/storage/emulated/0. Did not find any PDF file though, not sure what that would have been for..? Anyway, saw the MiFavor firmware update screen which meant we were on our way to finish line. After that it booted to a small tiny linux penguin symbol and black background. Tried rebooting by holding down the power button. Rebooted. Saw penguin again for like 5 seconds, then booted straight to the axon wavy weird startup sequence. I DID IT!! I really appreciate the help on this one. Great idea. And it worked flawlessly.
Thank you. Choose an username.. Your username might be strange but your solutions are a lifesaver.
Cheers!
macboss said:
It worked my friend!!!
I installed RAR, then went inside the downloaded file, found update.zip and unzipped it to '/storage/emulated/0. Did not find any PDF file though, not sure what that would have been for..? Anyway, saw the MiFavor firmware update screen which meant we were on our way to finish line. After that it booted to a small tiny linux penguin symbol and black background. Tried rebooting by holding down the power button. Rebooted. Saw penguin again for like 5 seconds, then booted straight to the axon wavy weird startup sequence. I DID IT!! I really appreciate the help on this one. Great idea. And it worked flawlessly.
Thank you. Choose an username.. Your username might be strange but your solutions are a lifesaver.
Cheers!
Click to expand...
Click to collapse
Lol. The signup dialog said 'Choose an username...', so i said, why not?
I think you downloaded directly the update.zip. Maybe the RAR part wasn't needed, I dunno. If there's a folder somewhere there called 'update' then just delete it, and the update.zip too
A larger than 5Gb update would have to be the file fully unzipped into a folder structure.
Update files are zipped and that's what the phone wants.
Choose an username... said:
Lol. The signup dialog said 'Choose an username...', so i said, why not?
I think you downloaded directly the update.zip. Maybe the RAR part wasn't needed, I dunno. If there's a folder somewhere there called 'update' then just delete it, and the update.zip too
Click to expand...
Click to collapse
I downloaded one of the two raw zips from the ZTE USA site that had a very long name.zip with all numbers. The "update.zip" was nestled inside after unzipping the file on the phone. I just picked that file and moved it to ther root and applied the update. It went through successfully. Did i not apply it correctly? Should i have just renamed that whole file to "update.zip" and moved the entire folder? A little confused. But i imagine if the update took and i saw the 32 in the current build of the device it took. But im not sure.
macboss said:
I downloaded one of the two raw zips from the ZTE USA site that had a very long name.zip with all numbers. The "update.zip" was nestled inside after unzipping the file on the phone. I just picked that file and moved it to ther root and applied the update. It went through successfully. Did i not apply it correctly? Should i have just renamed that whole file to "update.zip" and moved the entire folder? A little confused. But i imagine if the update took and i saw the 32 in the current build of the device it took. But im not sure.
Click to expand...
Click to collapse
Nah that's okay. I thought you downloaded the 'update.zip' directly. Happens sometimes
It’s weird the update was only about 2 GB. What do you think was the rest of the file?
Maybe in case it needed the full firmware. In this case it didn’t probably. Just a guess
macboss said:
Maybe in case it needed the full firmware. In this case it didn’t probably. Just a guess
Click to expand...
Click to collapse
No, that doesn't make sense. No idea really.
It couldn't have gone wrong so don't stress out. Your phone works. If it didn't work then yeah, something was wrong...