Related
Hi
I am trying to install the Jellybean 4.1.1 ROM on my rooted Nexus S.
The history of my attempts so far are here: Rooted Nexus S OTA Upgrade to 4.1 http://forum.xda-developers.com/showthread.php?t=1833420
I have downloaded the "image-soju-jro03e.zip" form the Android open source website, and used the Nexus Root Toolkit to install it.
This failed, and I attempted to install the image using ROM Manager.
This also failed, and produced a lengthy Recovery Log.
I have read through it and it seems to be telling me that certain files or folders are missing from the download.
e.g can't open /dev/tty0: No such file or directory
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
can't find /sd-ext in /etc/fstab
Is that what this means?
How can I correct it?
The full log is here: https://docs.google.com/document/d/1HWeYsXPnppQbgoloz72RH81E8a479LBmvYXIlzYPETo/edit
S
Help with recovery log
Hello?
Can anyone help me to understand this recovery log?
Should I direct my question to the "ROM Manager" people?
I have tried without success to install JB 4.1.1 from the Google Android Images page, and I think it must because something is missing from the file structure of my current ROM.
Am I on the right track?
M S
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
new hope
nightsky87 said:
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
Click to expand...
Click to collapse
Hello nightsky ( is that like, "nice guy",?) thanks for taking a look.
My phone is a Nexus S i9020, no suffix.
It is running Andriod 4.0.4 ICS. It is "rooted" and "unlocked".
I have Clockwork Mod v.6.0.1.0. Superuser v.3.1.3. and ROM Manager v.5.0.2.0.
I have tried over and over again without success to upgrade to JB 4.1.1 and I am getting sick and tired of this stupid game.
I would be happy to just stick with ICS 4.0.4, but every week, the phone tells me that an "update is available", and I have to dismiss the message every time I look at the phone! When I tried to apply the update It used to crash, requiring a battery-pull reset. Now I have CWM it takes over and says "failed to verify file signature", "install untrusted package?"
If I press on and install, it fails and the android is on its back with a red triangle on its belly.
If you look at the posts I have linked to, I have been on a steep learning curve regarding ROM flashing, and I understand the basic idea, its just that when I follow the instructions given on the forum, It doesn't happen that way for me and I suspect that there is something wrong with the file structure on my phone. That is why I have posted the link to my recovery log.
If you can help, please reply.
I have had a look at the "Random Phantasmogoria" site that you recommend, is it offering anything different than the Google developers site https://developers.google.com/android/nexus/images that I have downlooaded my image from?
MS
another version!
PS I have just had a look at the Google Dev. site and there appears to be a new version of 4.1.1 called JRO03L.
My next attempt, I'll try that.
MS
goodnight
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
jus to add on the post above. the instruction to install the factory images are on the same page where you downloaded the image in question.
and there is something to be wary of : flashing the factory image will WIPE the phone CLEAN (except what's on the usb storage o/c).
albundy2010 said:
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
Click to expand...
Click to collapse
Smashing buttons and hoping something works?
That's not very nice, or fair!
If you take the trouble to read my post, and the linked previous posts, you will see that I am trying my best to follow the instructions given on this forum, where I hoped to find knowledgeable professionals who contribute their valuable time free of charge to help noobs like me.
So far I have followed the instructions, only to get something other than the result described. This is why I am asking for your help to understand the recovery log, so that I can work out for myself what went wrong, and what I should change next time to get it right.
At this point in the journey I am still unsure about backup. I have "backed up" using the nexus root tool kit, which is a Nandroid back up, and I have "backed up" using ROM manager, but Titanium Back-Up does not recognise the backups and wants me to "back up" some more. After all this is over will I be able to clear out all the dross that my phone memory is accruing? Is there any point backing up Apps like "Google Earth" when I can easily download them from the Play Store after I have my new OS? etc... etc...
Anyway, I am going to try again, this time with the new JRO03L image, and this time I shall do it Command Line style instead of the "one click crap", as you recommend, my friend. I'll let you know how I get on.
MS
Hi.
Here, i have a very difficult issue with my unlocked transformer tf700t.
I wanted to install cyanogenmod ... I was to wipe data but it got interrupted
I have read many threads already like those:
http://www.2toer.com/2012/10/reset-button-transformer-pad-infinity-tf700t.html
(held for more than 50 seconds and it shaked but didn't help. tried to reset repedeatly too.)
http://www.transformerforums.com/fo...oot-into-android-after-jelly-bean-update.html
I also download "universal naked driver"
http://forum.xda-developers.com/showthread.php?t=2263822
But i am totally unsure how to install the driver and windows itself won't see its .inf files as valid. (windows 8).
I could use my cellphone's SD card but i can't run the recovery tool, can't boot, the very initial screen says "device is unlocked" and it is... But i can't enter the recovery mode and run RCK or wipe data.
http://www.technipages.com/how-to-soft-and-hard-reset-asus-eee-pad-transformer.html
However how eternally i could hold vol down + power ... it won't launch into recovery mode... It's much like freezing.
I should maybe have directly run rck instead of doing wipe data...
Is there a way to send any signals to the tablet via usb with a windows tool?
[edit]
Right now i'm checking with the .blob solution...
http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html
Yes, there is a method to access your tab from your computer, it's called Fastboot. But you don't seem to be able to get to the bootloader menu at all to get into fastboot mode, are you? By booting holding Power and Volume Down buttons?
If that is true, you are hard bricked, I am sorry to say, and my only suggestion would be to try this method I read about on the TF300 forum:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Win 8 seems to really suck for fastboot and adb, try to get a Win7, XP or Linux machine.
Good luck!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
Click to expand...
Click to collapse
I really can't... The procedure won't trigger anything or it freezes before it could. It may have got corrupted while the wipe data has been interrupted... :\
Matthieu.s said:
I really can't... It may have got corrupted while the wipe data has been interrupted... :\
Click to expand...
Click to collapse
Sorry friend - it's a brick :crying:
You can send it to Asus to have the motherboard replaced or try to find one sold for parts on ebay and replace it yourself.
Just for forensic purposes: Did you execute "Wipe Data" from the bootloader menu?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Yes... From the boot menu. What parts do i need to replace? Any workaround possible before giving up hope?
Can you get back to recovery at all or the bootloader?
Matthieu.s said:
Yes... From the boot menu. What parts do i need to replace? Any workaround possible before giving up hope?
Click to expand...
Click to collapse
You need to replace the motherboard.
My guess is, you flashed a custom recovery and then used 'Wipe Data' from the bootloader menu.
The instructions you followed probably advised you to wipe data before flashing the rom, but you had to do that from your custom recovery - not the bootloader menu. 'Wipe data' from the BL menu with a custom recovery installed is a very, very risky business.
Sorry mate.....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
you mean... That from all tutorials that i've read, not a single author had the idea of putting a screenshot of "don"t wipe" from menu...
Or shouldn't have the utility's author chose a synonym instead of using the same word as the device makers did?
Or that this nearly 600$ crap that's keyboard is almost worth the half of itself and doesn't even come along, that doesn't even charge on USB, that has the crappiest android interface and that lags like hell even after a factory reset with its useless 4 cores... doesn't even come with an emercency secure-rom partition?
Dude. I should have bought a laptop.
It's like... This wipe data utility has only one use: autodestruction? that's it? Is it a way to make sure that the richest of us will buy a new one as soon as the old new one breaks?
I don't understand why this process also erased ... the bios? It's like... How would anyone be able to do anything without the bios?
Hmm... It discharged by night. The battery icon still loads and at its current state... It still checks for its charge state... It's still alive... There must be a way to wake it up from its sleep...
Maybe the interface isn't frozen but just doesn't respond to the voldown+power button?
Maybe there exists something to plug on the 60 pins plug that could force-access the partition?
Matthieu.s said:
you mean... That from all tutorials that i've read, not a single author had the idea of putting a screenshot of "don"t wipe" from menu...
Or shouldn't have the utility's author chose a synonym instead of using the same word as the device makers did?
Or that this nearly 600$ crap that's keyboard is almost worth the half of itself and doesn't even come along, that doesn't even charge on USB, that has the crappiest android interface and that lags like hell even after a factory reset with its useless 4 cores... doesn't even come with an emercency secure-rom partition?
Dude. I should have bought a laptop.
It's like... This wipe data utility has only one use: autodestruction? that's it? Is it a way to make sure that the richest of us will buy a new one as soon as the old new one breaks?
Click to expand...
Click to collapse
Do you still be able to fastboot or access from your pc? You might have a chance to flash a new blob for you device..
Matthieu.s said:
you mean... That from all tutorials that i've read, not a single author had the idea of putting a screenshot of "don"t wipe" from menu...
Or shouldn't have the utility's author chose a synonym instead of using the same word as the device makers did?
Or that this nearly 600$ crap that's keyboard is almost worth the half of itself and doesn't even come along, that doesn't even charge on USB, that has the crappiest android interface and that lags like hell even after a factory reset with its useless 4 cores... doesn't even come with an emercency secure-rom partition?
Dude. I should have bought a laptop.
It's like... This wipe data utility has only one use: autodestruction? that's it? Is it a way to make sure that the richest of us will buy a new one as soon as the old new one breaks?
I don't understand why this process also erased ... the bios? It's like... How would anyone be able to do anything without the bios?
Hmm... It discharged by night. The battery icon still loads and at its current state... It still checks for its charge state... It's still alive... There must be a way to wake it up from its sleep...
Click to expand...
Click to collapse
I understand that you are upset - I would be if I were you. But you can hardly blame Asus or the author(s) of whatever instructions you were following for bricking your tablet.
The disclaimer you have to read before you unlocked could not be more clear: They strongly discourage you to do it and make it abundantly clear you are on your own if you do.
Every set of instructions on flashing I have read also states: "Don't blame me if something goes wrong - you are doing this at your own risk" in one or the other form.
You did it anyway and made a mistake.
I do feel for you! It's a huge bummer to wreck a $600 device, no doubt about it.
Wipe Data from the bootloader menu is a feature of the stock rom. If I understand it correctly (and please someone correct me, if I'm not) it's a last ditch method to reflash the tablet with stock firmware.
It wipes everything except the stock recovery and assumes that you have a copy of the stock firmware on a microSD waiting to be flashed.
Asus provided a safe Factory Reset option from the settings menu for the average user and I bet they do not want users to access the bootloader and mess with it's options at all. There's a reason it's not exactly intuitive to get there.
Yes, I agree, there should be a warning before Wipe Data does it's thing.
Unfortunately there isn't....
But again, you can hardly blame Asus for a feature of the stock system not working with custom software you installed.
And again, I am sorry for your loss....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
LetMeKnow said:
Do you still be able to fastboot or access from your pc? You might have a chance to flash a new blob for you device..
Click to expand...
Click to collapse
maybe if i had the files on a sd card it could load them indeed..
Something like putting usual partition files on the sd card and see if it loads... It may check for its missing files on the SD if i'm lucky... Can i do this and go directly to cyanogen? I'll check the topics that discusses it furthermore... But my situation may vary... Major thing is that i really can't access it from PC from boot welcome screen so it discards all topics that asks for a usb connection... And the boot-to-CRW button makes no effect meaning it's also broken... Maybe putting CRW on the SD card and process the cyanogen file that should still be on the storage's base folder?
berndblb said:
I understand that you are upset - (...)
But again, you can hardly blame Asus for a feature of the stock system not working with custom software you installed.
And again, I am sorry for your loss....4
Click to expand...
Click to collapse
Don't worry friend i still have hope... Maybe the solution is in what you spoke of and is to use SD in some way i spoke in the previous comment but i'll need just a bit of help and guidance ... and links I'll use my cellphone's sdcard and backup>format it and do whatever required to wake the tablet's system up just enough to restore its missing files... Like... If the machine does check for SD (maybe bootscreen isn't frozen but just idle) maybe it could check for its required files like CWM or base firmware... I really believe the SD card plan is a good idea but the only thing is that it must be made automatically or if isn't i probably won't be able to trigger from vol_down+power... Or maybe could... Let's see ^^
What do you believe about this post? It's not tf700t related but it discusses the method a bit? http://forum.doozan.com/read.php?6,8904
And this thread is interesting but i'm unsure... http://www.transformerforums.com/fo...irmware-tf700-tf300-tf101-possibly-tf201.html
This is what i will attempt. http://androidforums.com/nookcolor-...rkmod-twrp-bootable-sd-card-06-04-2013-a.html
Citation from site
Now what can you do with your new bootable CWM/TWRP sd card?
You can flash a rom. Plug it into your computer and copy your rom file to it
You can backup your rom. (under "backup and restore" menu.)
You can restore a recovery backup, should your new rom never boot.
Click to expand...
Click to collapse
x( Failed :/ I need something to trigger the system to bypass its instructions and run SD instead... Trigger from USB or something...
I'm still not clear. Do you have access to the bootloader or not.
It sounds like you do in which case all is not lost. Give up on the SD method though. The trick here is to ensure you have the right PC USB drivers installed.
Is the device registered in device manager when plugged into the PC?
See this post here
http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
sbdags said:
I'm still not clear. Do you have access to the bootloader or not.
It sounds like you do in which case all is not lost. Give up on the SD method though. The trick here is to ensure you have the right PC USB drivers installed.
Is the device registered in device manager when plugged into the PC?
See this post here
http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Click to expand...
Click to collapse
I don't think he can get to the bootloader, if you read post #3. I referred him to exactly the same method and it didn't seem to work....
Sent from my DROID4 using Tapatalk 2
Here's what i get from device manager (it finally shown up in the list)
Code:
Unknown device
Tab 1
Device type: other devices
Maker: unknown
Location: Port_#0004.Hub_#0005
Windows stopped this device because it had problems (code 43)
Tab 2
All marked unavaillable/not signed
Tab 3
USB\DEVICE_DESCRIPTOR_FAILURE
Tab 4
Device configured (null)
Device USB\VID_0000&PID_0002\6&1512c192&0&4 was configured.
Driver Name: null
Class GUID: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device ID:
Outranked Drivers:
Device Updated: false
Device not started
Device USB\VID_0000&PID_0002\6&1512c192&0&4 had a problem starting.
Driver Name: null
Class GUID: {00000000-0000-0000-0000-000000000000}
Service:
Lower Filters:
Upper Filters:
Problem: 0x2B
Status: 0x0
It shows signs of life.
The drivers were already installed on Windows... But i guess that they are not meant for this procedure? What about universal naked drivers?
I'll continue researches tomorrow... Thanx ^^
Hi did you ever get the fix for this ? also same boat tried 2 3rd party cables no luck .. first error code I got was 43 then forces drivers got code 10 then I got what you get in events
Matthieu.s said:
Here's what i get from device manager (it finally shown up in the list)
Code:
Unknown device
Tab 1
Device type: other devices
Maker: unknown
Location: Port_#0004.Hub_#0005
Windows stopped this device because it had problems (code 43)
Tab 2
All marked unavaillable/not signed
Tab 3
USB\DEVICE_DESCRIPTOR_FAILURE
Tab 4
Device configured (null)
Device USB\VID_0000&PID_0002\6&1512c192&0&4 was configured.
Driver Name: null
Class GUID: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device ID:
Outranked Drivers:
Device Updated: false
Device not started
Device USB\VID_0000&PID_0002\6&1512c192&0&4 had a problem starting.
Driver Name: null
Class GUID: {00000000-0000-0000-0000-000000000000}
Service:
Lower Filters:
Upper Filters:
Problem: 0x2B
Status: 0x0
It shows signs of life.
The drivers were already installed on Windows... But i guess that they are not meant for this procedure? What about universal naked drivers?
I'll continue researches tomorrow... Thanx ^^
Click to expand...
Click to collapse
Hi
I am new to hacking android. I have built linux distros in the past, and have worked with Linux for 15 years,
I have just rooted a ZTE V965. It doesn't come pre-installed with Play store, and has all sorts of ZTE-specific Chinese apps. It has a good baseband circuit, a good screen, reasonable camera and I think is a great value phone, apart from the awful UI.
It is an android phone, although heavily customised. It has an MTK6589 processor coupled with 4Gb ROM and 512Mb RAM.
I have other phones which operate a much more "Vanilla" android. For example, the Guophone 9105 which also uses an MTK6589. This has a troubling tendency to reboot every random interval. Approx 6 times a week.
I have had success in the past running Linux systems built for much earlier kernels on later kernels. This suggests the ABI (application binary interface) for the Linux kernel changes rather slowly.
I am wondering how well the userland apps are separated from the kernel and drivers on Android.
Specifically, is it feasible to dump all the UI stuff from one phone onto another then change the init to launch the other UI?
Would this risk bricking the phone, or would the shell commands and ADB infrastructure still likely operate?
I guess I should change the bootloader to one that supports fastboot first, right? Is ther a how-to on achieveing this from the root shell?
Thanks for any thoughts
Nick.
Nick Hill said:
Hi
I am new to hacking android. I have built linux distros in the past, and have worked with Linux for 15 years,
I have just rooted a ZTE V965. It doesn't come pre-installed with Play store, and has all sorts of ZTE-specific Chinese apps. It has a good baseband circuit, a good screen, reasonable camera and I think is a great value phone, apart from the awful UI.
It is an android phone, although heavily customised. It has an MTK6589 processor coupled with 4Gb ROM and 512Mb RAM.
I have other phones which operate a much more "Vanilla" android. For example, the Guophone 9105 which also uses an MTK6589. This has a troubling tendency to reboot every random interval. Approx 6 times a week.
I have had success in the past running Linux systems built for much earlier kernels on later kernels. This suggests the ABI (application binary interface) for the Linux kernel changes rather slowly.
I am wondering how well the userland apps are separated from the kernel and drivers on Android.
Specifically, is it feasible to dump all the UI stuff from one phone onto another then change the init to launch the other UI?
Would this risk bricking the phone, or would the shell commands and ADB infrastructure still likely operate?
I guess I should change the bootloader to one that supports fastboot first, right? Is ther a how-to on achieveing this from the root shell?
Thanks for any thoughts
Nick.
Click to expand...
Click to collapse
Hi Nick, I have the same phone. I'm also very new to android, last phone was iOS and before that windows. I managed to root the V965 using Vroot. I also managed to install SuperSU and CWM. However, the CWM is not fully functional, I can only do a factory reset, not install any packages or roms. Probably the phone has a locked bootloader. I can't check, because the USB driver with the phone doesnt support fastboot.
I really need to get google play working in this phone, read a lot of stuff, tried many things, but I havent succeeded yet. Please let me know if you make any progress.
In China they are flashing this phone, found some ROMs even, but I am not sure how they manage and google translate isn't much help there.
http://www.romjd.com/Device/zte-v965/hot/all/1
Hmmm my V965 is having some issues now
After a factory reset, the setup wizard keeps crashing. Even after another resest. So I can't get in the phone anymore.
Any chance you can send me the USB drivers that are on the phone? My phone isnt deteceted anymore, so I can't access the drivers, which I want to reinstall. And of course they are not on the ZTE website.
Byte_Me said:
Hmmm my V965 is having some issues now
After a factory reset, the setup wizard keeps crashing. Even after another resest. So I can't get in the phone anymore.
Any chance you can send me the USB drivers that are on the phone? My phone isnt deteceted anymore, so I can't access the drivers, which I want to reinstall. And of course they are not on the ZTE website.
Click to expand...
Click to collapse
Hi
You can temporarily download the ZTE v965 USB drivers from
www dot nickhill dot co dot uk forward slash ztev965usb dot zip
Byte_Me said:
Hi Nick, I have the same phone. I'm also very new to android, last phone was iOS and before that windows. I managed to root the V965 using Vroot. I also managed to install SuperSU and CWM. However, the CWM is not fully functional, I can only do a factory reset, not install any packages or roms. Probably the phone has a locked bootloader. I can't check, because the USB driver with the phone doesnt support fastboot.
Click to expand...
Click to collapse
Fastboot and ADB appear to be standard protocols, at least on my Ubuntu, which don't need special drivers. However, it does appear that the stock boot loaader on the v965 does fail to incorporate the fastboot option.
If you remove the battery, replace it then turn on holding the volume down, you will get a menu, but fastboot is not there.
I don't know for a fact, but I do suspect that if you have access to the running android system as root, then you could in principle change any of the internal flash data. Therefore, in principle, I guess you could replace the boot loader or anything else in the running android system. Anyone please correct me if I am wrong, or confirm if I am right.
The feature set of this phone seems to be the same as the feature set of my Guophone. MTK6589, dual SIM, etc. So this image may be a good place to start if considering a transplant.
If you have ROMs, then perhaps it is possible to flash the ROM from a root terminal. I'm thinking add the uncompressed ROM to the Micro SD card, then using the dd command, block copy it to the appropriate image area on the internal ROM, reboot, reset to factory defaults.
If anyone more experienced than me with the nuts and bolts of Android can confirm or deny this will work, or where it should be put, please let me know.
An important factor is that the NAND is not locked on the ZTE V965. So if you have a root shell on the phone, you can issue the following command:
mount -o remount,rw /[email protected] /system/
Once you have done this, you will have read/write access to the system partition.
The only thing I then need to know is what should I avoid changing that may break the ADB bridge/root console?
And is all the UI stuff kept together, if so, where?
Shuffle it around a bit, make a new ROM
Thanks for the driver!
Unfortuntely it doesn't help
I found out the culprit, I tried to install gapps (google apps package) to the system app folder. I thought these changes would be reversed with a factory reset, but they are not. Setupwizard.apk keeps crashing and is preventing me from accessing my phone, so I must find a way to remove it from the system app folder. However, since this error occurred, I am not able to contact the phone in any way from the PC. Adb toolkit does not detect it, even when I reinstalled your driver. It's quite puzzling, I dont understand why in recovery mode I cannot connect adb-toolkit anymore.
Got my V965 working again, but it was a lot of hassle with shell access. Still not fully functional, no drives detected when i connect to USB, which is quite annoying, but not more than that. If you ever make any progress with google apps or flashing, please keep me informed, that would make this phone much more useable. I'll also keep hacking away at it, but without a bootloader unlock (I still think this is the problem), I don't think it will be possible.
I'm convinced it's possible to flash the phone, it seems they do it a lot in China.
I found a website with a couple of custom ROMs specific for the V965:
http://www.romjd.com/Rom/Detail/17086
And what I suspect is a rooting & flashing tool. Rooting works, I haven't figured out flashing yet.
http://dl.vmall.com/c0xa12brvo
I've also tried flashing from the settings - update menu in the phone, but it never finds the ROM (update.zip)
I did find another problem, I can't be reached on my phone, it always goes to voicemail. Same SIM in another phone works fine. No idea what's causing this.
Byte_Me said:
Got my V965 working again, but it was a lot of hassle with shell access. Still not fully functional, no drives detected when i connect to USB, which is quite annoying, but not more than that. If you ever make any progress with google apps or flashing, please keep me informed, that would make this phone much more useable. I'll also keep hacking away at it, but without a bootloader unlock (I still think this is the problem), I don't think it will be possible.
Click to expand...
Click to collapse
Hi
I might be able to help you with the problem.
I have a mint, unused ZTE v965. I have used MTK Droid root and tools to extract a backup of the entire new phone. It is currently uploading to www dot nickhill dot co dot uk forward slash ZTE-V965_new_backup.zip
You should be able to write this back to your phone using flashtool.exe.
I don't know for sure if this will work, so entirely at your own risk! Just trying to help. If unsure, ask around.
I am new to this forum, so please remember to click the thanks button if you find anything I have done helpful!
Meanwhile, the MTK droid root and tools has a function to remove much of the chinese stuff (once the system has been installed) and there is always the cyanogenmod gapps package. This may be worth investigating.
Nick Hill said:
Hi
I might be able to help you with the problem.
I have a mint, unused ZTE v965. I have used MTK Droid root and tools to extract a backup of the entire new phone. It is currently uploading to www dot nickhill dot co dot uk forward slash ZTE-V965_new_backup.zip
Click to expand...
Click to collapse
The file size should be 635,972,093 bytes and should finish uploading at 04:00 GMT
md5sum 17ecfdd1040d5dbfab70a3adbc24e07a
Thanks for the ROM, i'll give it a go. I will try to install it using the update option in the settings, that seems the safest.
Be careful with gapps. setupwizard.apk + factory reset = a lot of problems (if you install in system app folder)
OMG that tool is awesome. created CWM boot, installed your ROM, then installed a clean ROM, then installed gapps, all working!!!
Byte_Me said:
OMG that tool is awesome. created CWM boot, installed your ROM, then installed a clean ROM, then installed gapps, all working!!!
Click to expand...
Click to collapse
Firstly, I'm glad it's working for you.
Secondly, which tools did you use? Did you unpack the zip, open flashtools, select the scatter file then program the phone, or did you use some other method?
Which clean ROM did you then install, and how did you install it?
Did you then use MobileUncle to install CWM then use the cyanogenmod 10.1 gapps, or did you do something different?
It is useful to remember that MTKdroidtools has a useful function to remove chinese stuff. I think if more people contributed to the list of Chinese files that are safe to remove, that would be blade.
A detailed step-by-step guide might be helpful for anyone else with the same problem. One of the general problems I find is that there are plenty of guides around referring to this program, or that program, but few are detailed enough for someone who doesn't already know about those programs to use.
I pretty much bricked a Lenovo A766 yesterday, and it took several hours to learn about the tools to eventually unbrick it.
I would have rather spent my time understanding what is really going on, rather than spending my time learning vaguely what tool achieves what end result. If I understood more about the Android system, and built that knowledge on my understanding of Linux, I reckon I could achieve much more.
One thing I notice is that tablets and smartphones are actually replacing desktops and laptops. February this year, windows machines were down 7% YOY. I use Ubuntu for my main computer. Using these tools on Windows led me to significant frustration! This has led me to understand why there is a move. Maybe the tools provided for windows need to eventually move to android. We could then potentially use USB OTG to service other android devices. MTKdroidtools and flashtools runnng as a host on a separate Android system would be cool.
Nick Hill said:
Firstly, I'm glad it's working for you.
Click to expand...
Click to collapse
Thanks, me too
Secondly, which tools did you use? Did you unpack the zip, open flashtools, select the scatter file then program the phone, or did you use some other method?
Click to expand...
Click to collapse
I used MTK tools as described in that topic, rooted, made backup, installed CWM
Which clean ROM did you then install, and how did you install it?
Click to expand...
Click to collapse
I used the update tool from CWM to flash this ROM:
http://www.romjd.com/Rom/Detail/17086
That ROM is not very clean though, You might as well clean your own ROM
Did you then use MobileUncle to install CWM then use the cyanogenmod 10.1 gapps, or did you do something different?
Click to expand...
Click to collapse
CWM is installed using MTK Droid Root and Tools:
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
This gapps version I installed: gapps-jb-20121011-signed
It's installed using CWM bootloader: install .zip package
It is useful to remember that MTKdroidtools has a useful function to remove chinese stuff. I think if more people contributed to the list of Chinese files that are safe to remove, that would be blade.
Click to expand...
Click to collapse
I used the delete China function, but it didnt catch very much. But with all the functions available now, it's quite easy to clean manually.
A detailed step-by-step guide might be helpful for anyone else with the same problem. One of the general problems I find is that there are plenty of guides around referring to this program, or that program, but few are detailed enough for someone who doesn't already know about those programs to use.
Click to expand...
Click to collapse
Yes, I plan to make a topic for this phone, but at the moment I am still testing many things.
I pretty much bricked a Lenovo A766 yesterday, and it took several hours to learn about the tools to eventually unbrick it. I would have rather spent my time understanding what is really going on, rather than spending my time learning vaguely what tool achieves what end result. If I understood more about the Android system, and built that knowledge on my understanding of Linux, I reckon I could achieve much more.
Click to expand...
Click to collapse
I know how you feel, I was ready to toss this phone in the trash
One thing I notice is that tablets and smartphones are actually replacing desktops and laptops. February this year, windows machines were down 7% YOY. I use Ubuntu for my main computer. Using these tools on Windows led me to significant frustration! This has led me to understand why there is a move. Maybe the tools provided for windows need to eventually move to android. We could then potentially use USB OTG to service other android devices. MTKdroidtools and flashtools runnng as a host on a separate Android system would be cool.
Click to expand...
Click to collapse
I have no idea about the possibilities there. I'm not a programmer, just someone who is good with computers and knows a little bit of everything.
PS. I could also use some thanks as well, maybe get some respect around here
Nick Hill said:
...
Click to expand...
Click to collapse
Did you give it a try yet? Another user did and google apps are working for him, so thats 2 for 2.
Are you still on your original ROM? If so, I have a question for you. Do you get notification badges on your icons, for instance, when you have a missed call, is there a red box with a 1 on the phone icon? Also, do your contacts get ID-ed when they call you? I have some problems with that, caused by the country code prefix. I am still running that ROM I downlaoded from the Chinese forum, but if your ROM doent have these issues, I will switch back ASAP.
Nick Hill said:
Firstly, I'm glad it's working for you.
Click to expand...
Click to collapse
as you are a Lenovo a766 owner, may you help me with this?
http://forum.xda-developers.com/showthread.php?p=49076877#post49076877
Where are configuration settings stored accross factory resets?
I have come to the (perhaps erroneous) conclusion that the user interface and what the user will experience is governed primarily from:
the APKs in
/system/app/
/system/vendor/operator/app/
and the configuration files pertaining to the installed apps, which is located at:
/data/user/0/
I guess that when the android device is factory reset, the /data partition is completely cleared, right?
Is there a set of standard configurations which are unpacked from somewhere into /data/user/0/ after a factory reset, or is it normal for all configurations to be stored in their respective APKs?
Recently updated my Pixel 4a and have run into an issue that causes a strange boot loop to a screen that states "Cannot load Android system. Your Data may be corrupt." and prompts to either factory data reset or try booting again. What's strange is that when attempting to boot it again, it is able to load into the device and I have normal access to the phone for about 30-60 seconds before it restarts and prompts a factory reset again.
My main issue is that I need to backup/upload about 900 photos to google photos that were not saved. So far the phone has been rebooting, connecting to wifi and uploading about 0-3 items to google photos per boot until it restarts. Eventually I may be able to secure all my photos this way but I want to know if there is a more efficient method to do this.
Things to know:
Bootloader is locked (can't unlock due to wipe) -> cannot use custom recovery/ flash twrp
USB debugging is enabled and I have sideloaded the latest OTA (sunfish) via ADB sideload in recovery mode but the boot loop has not resolved.
I can successfully use ADB pull /sdcard/DCIM/Camera for only up to 60 seconds until it force restarts. When I attempt to pull again on the next boot, it will pull the same files because it is copying and not moving them.
Does anyone have a solution to this rather than to just factory reset or continuously rebooting? It is frustrating because I still have access to the phone's files but only for about less than a minute. I have scavenged reddit threads, forums, and google for some way to do this but to no avail. (Also is there a way to use the stock recovery's "mount /system" option?)
It's not very elegant, but I could totally imagine a script that listed the files and then copied a few at a time, waiting for the phone to reboot before continuing...
I have a python script that uses adb to "sync" a directory on the phone with a directory on the PC, but it's doing a push, not a pull.
a1291762 said:
I have a python script that uses adb to "sync" a directory on the phone with a directory on the PC, but it's doing a push, not a pull.
Click to expand...
Click to collapse
I modified my script a bit to pull instead of pushing, it's ... awfully rough (eg. you have to manually create a Camera directory to store the files it copies) but it seemed to work in principle. It might be enough for you, or it might serve as a base for a better solution. No doubt it'll need a few mods anyway, especially if you're on Windows (in which case ls won't work).
You might also try booting into safe mode, in case that stops the phone from rebooting? https://www.androidauthority.com/how-to-enter-safe-mode-android-801476/
a1291762 said:
I modified my script a bit to pull instead of pushing, it's ... awfully rough (eg. you have to manually create a Camera directory to store the files it copies) but it seemed to work in principle. It might be enough for you, or it might serve as a base for a better solution. No doubt it'll need a few mods anyway, especially if you're on Windows (in which case ls won't work).
You might also try booting into safe mode, in case that stops the phone from rebooting? https://www.androidauthority.com/how-to-enter-safe-mode-android-801476/
Click to expand...
Click to collapse
Thank you for the reply! I am on Windows and I am not too script savvy out of writing a few simple AHK actions so I am not entirely sure how to proceed with what you have there.
Booting into safe mode did not work unfortunately. Seems the time until restart was the same as well.
Expressionize said:
Thank you for the reply! I am on Windows and I am not too script savvy out of writing a few simple AHK actions so I am not entirely sure how to proceed with what you have there.
Click to expand...
Click to collapse
I do have a windows PC for gaming so I'll fire it up and see if I can make it work there.
a1291762 said:
I do have a windows PC for gaming so I'll fire it up and see if I can make it work there.
Click to expand...
Click to collapse
I was able to brute force the process and finally made my way through the photos. There was one lucky boot that allowed normal access for about 3 minutes and that was enough time for adb pull to completely grab what I needed. I appreciate your time and help.
I guess it still doesn't solve the issue if someone else runs into my similar situation though, but it seems like a rare enough problem.
Expressionize said:
I was able to brute force the process and finally made my way through the photos. There was one lucky boot that allowed normal access for about 3 minutes and that was enough time for adb pull to completely grab what I needed. I appreciate your time and help.
Click to expand...
Click to collapse
No worries. I'm glad you got your photos.
I had to go out, but I got back and literally just finished updating the script so it runs on Windows and is a bit smarter (eg. waiting for the phone to come back when it goes away). I'll attach it here in the event someone else finds it useful
There's a few variables at the top to configure it. It needs python and adb but shouldn't need anything else.
python3 fetch_files.txt
It's got a .txt extension instead of the more typical .py because XDA won't let me upload a .py file.
Found my old phone from high school. Turned it on and looks like I never factory reset it, and I would love to see all of the photos and messages I left behind, however I can not for the life of me remember the pin I used. Browsed around and tried to delete the gesture.key using ADB but permission is denied, and I wasn't able to find a custom recovery tool for this specific phone either. Anyone have any possible solutions? Thank you
Shiiiba said:
Found my old phone from high school. Turned it on and looks like I never factory reset it, and I would love to see all of the photos and messages I left behind, however I can not for the life of me remember the pin I used. Browsed around and tried to delete the gesture.key using ADB but permission is denied, and I wasn't able to find a custom recovery tool for this specific phone either. Anyone have any possible solutions? Thank you
Click to expand...
Click to collapse
If you cannot remember the PIN, you're most likely going to have to factory reset. There is no way around this that I know of, unfortunately.
you can just dump the whole userdata partition off flash memory in EDL mode, loop mount partition image from linux and modify it's content (like deleting locksettings.db)
Shiiiba said:
Hi there, thanks for responding to my forum post. I can give it a shot, however I was wondering if you would be willing to help me with attempting this. Im familiar with root and devices but I’ve not had any experiencing with dumps or tools like the one you provided on github. I have an extra ZTE Flash to test on but some extra insight would be nice. I also had two questions:
1: can I just take the locksettings.db and somehow retrieve my pin from it instead of modifying and dumping?
2: if I do end up having to dump, will the environment be the same (IE logged in apps, id like to see my message history in apps that are there)
Thanks so much, and sorry for disturbing.
Click to expand...
Click to collapse
you need a firehose programmer matching your SoC and OEM. the tool comes with collection (loaders) for quite few devices, just give it a try.
1. might be possible with password.key
2. yes by just deleting locksettings.db nothing is changed