Related
Is there anyone around with a Rogers HTC Dream?
if so, could you please do a nandroid backup of your phone and sent me the files?
I can't boot my phone after messing up reflashing it with incompatable firmware
Thanks in advance!
they are here
Yep they are there and I plan to leave them on that server permanently.
would i install these using fastboot... or what would I use?
the nandroid gives me errors
it refuses to back up my data and will not restore anything
if i use nandroid-mobile.sh backup in the console it says
error reading recovery no space left on device
PurpleFries said:
would i install these using fastboot... or what would I use?
the nandroid gives me errors
it refuses to back up my data and will not restore anything
if i use nandroid-mobile.sh backup in the console it says
error reading recovery no space left on device
Click to expand...
Click to collapse
yup fastboot.
k heres what i used
fastboot flash boot boot.img
fastboot flash system system.img
restarted and
still stuck on rogers screen
no change whatsoever
When I semi-bricked my phone these are the instructions I used.
Since you can get into fastboot you should be able to reload to factory settings no problem.
should be...
hmmmm, looks like you did the correct thing.
Just to let you know, after you reload the fresh copy of boot.img and system.img it will take much longer for your phone to turn on the first time, typically 5-10 minutes. It has to re-install the OS on the phone.
thats essentially what i did
however the link you gave me did not include a data.img
DISREGARD TEMPORARILY, waiting those 5-10 minutes
it doesnt work if i just flash the boot and system
also, would i need to reflash the recovery with the stock rom? because then i need the stock recovery rom as well
PurpleFries said:
thats essentially what i did
however the link you gave me did not include a data.img
Click to expand...
Click to collapse
The data.img would be personal. It's not needed, but if you don't have when you flash your Dream it'll be like you're starting over for the first time.
it doesnt work if i just flash the boot and system
also, would i need to reflash the recovery with the stock rom? because then i need the stock recovery rom as well
Click to expand...
Click to collapse
AFAIK, the stock from is the system.img file. How lond did you leave it on the Rogers screen before you manually restarted your phone?
as of now, it's been approx 10 minutes.
after ur post edit i wiped and re-fastboot-ed the stuff
gonna let it run for about 20 minutes before i conclude its still not workin
EDIT
18 minutes so far...
not looking favorable T.T
EDIT2
yea its been 20 minutes, no change...
any other ideas?
EDIT3
30 minutes...
def not working
PurpleFries said:
as of now, it's been approx 10 minutes.
after ur post edit i wiped and re-fastboot-ed the stuff
gonna let it run for about 20 minutes before i conclude its still not workin
Click to expand...
Click to collapse
yeah after 20 minutes it's certainly too long. I think mine only took about 5 minutes, but good luck. eeep
edit: worse comes to worse, take it back to the store and tell them your phone wont turn on.
Also you might be able to get more help tomorrow on the subject. I'm a fairly big newbie here so I don't know that much. There is a way for your computer to see at what point your phone may be frozen at but I can't remember how.
edit 2:
17. It's taking forever to boot!
The first boot will take longer than normal because dexopt needs to run. If you are nervous, connect USB and run "adb logcat" to watch the progress.
Click to expand...
Click to collapse
That is from cyanogen, but it should give you some insight as to what your phone may be doing.
doesnt help
it doesnt see my device as attached.
adb devices doesnt list a device
and adb logcat tells me its waiting for devices
I'm sure ill need some sort of explanation as to why it doesnt turn on... what could I say?
also, not sure if i thanked you before, but thanks for all of the assistance
EDIT
it sees the device if it is attached in recovery mode
I still cant logcat tho
it says: /sbin/sh: exec: line 1: logcat: not found
PurpleFries said:
doesnt help
it doesnt see my device as attached.
adb devices doesnt list a device
and adb logcat tells me its waiting for devices
I'm sure ill need some sort of explanation as to why it doesnt turn on... what could I say?
also, not sure if i thanked you before, but thanks for all of the assistance
EDIT
it sees the device if it is attached in recovery mode
I still cant logcat tho
it says: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
I would just tell them I turned it on this morning and this happened. Ask them if they can fix it and see what happens. Mention nothing about trying to root it.
Just to make sure you're doing the steps correctly.
You're downloading the files I provided for you and placing them in your android/sdk..../tools folder right?
Then you boot the phone into fastboot?
Then I think you press the talk button to usb connect
from there you type in the commands.
Is that what you're doing?
exactly word for word.
during entering the commands:
i flash the boot and system.img
and press the back button to reboot
then i do the adb logcat and it cannot detect the device
PurpleFries said:
exactly word for word.
during entering the commands:
i flash the boot and system.img
and press the back button to reboot
then i do the adb logcat and it cannot detect the device
Click to expand...
Click to collapse
have you applied the update.zip file? Perhaps try applying that again first and then try the recover again.
which update.zip?
you never told me to install an update.zip previously
it's done through the recovery menu correct?
PurpleFries said:
which update.zip?
you never told me to install an update.zip previously
it's done through the recovery menu correct?
Click to expand...
Click to collapse
Well from that earlier psot I showed you that linked to HOFO step #1 had this.
Assuming you installed the update.zip before or after rooting (you can do it at any point really), now you can begin the recovery. First, enter the following into the command prompt
Click to expand...
Click to collapse
So it looks like the phone has to be rooted before you can apply the backup and to root the phone correctly you need the update.zip file.
The instructions to install the update.zip file and the file itself can be found here
Perhaps try to follow all of those steps, well skip the nandroid backup and see if your phone boots after that. If it does not but you can install the update.zip file then try the recovery method you have been trying.
tried updating with the files given (update.zip, boot.img, recovery.img)
could not go into recovery mode, would not boot
tried updating with update.zip and other files from before(update.zip, boot.img, system.img)
still no booting
my phone was, however already root-ed before it stopped working
PurpleFries said:
tried updating with the files given (update.zip, boot.img, recovery.img)
could not go into recovery mode, would not boot
tried updating with update.zip and other files from before(update.zip, boot.img, system.img)
still no booting
my phone was, however already root-ed before it stopped working
Click to expand...
Click to collapse
Sorry then. I'm out of ways to help. I don't really know all that much about the process. Perhaps your phone is slightly different than the rest of our Rogers phones so my backup files wont work on yours.
how long ago did you get it?
this thursday
First of all I have a 16gb n7 currently on 4.2.1 JOP40D. It's unlock/rooted on STOCK rom.
First off I have tried installing the OTA update and would get an error everytime.
Then I tried installing CWM and manually pushing the update nakasi update and it still threw an error:
Verifying current system..
assert failed: apply_patch_check ("/system/build.prop", 38f7593c2ff2fa85a147 etc...)
E: Error in /sdcard/0/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(status 7)
Installation abborted.
So from googling/searching that I have figured that there is something not "stock" about my build.prop. I had edited it to get rid of the NAV bar but after re-editing it back to stock, it would still throw the same error.
So first I tried reflashing 4.2.1 ... threw the same error
Now I'm trying to get the build prop out of the JOP40D update but when I look in the files it is called "build.prop.p" ... I'm not sure what that last .p is about? Also when opening it there are just about 2 lines of chinese characters... Soooo this is where I'm stuck... I need to know how to extract a proper build prop from 4.2.1 or I need someone to post a stock 4.2.1 build prop.. thanks..
edit: before people suggest I have tried redownloading both the JOP40D and JPQ39 files
edit2: I am on a mac so flashing to stock from fastboot / abd isn't really an option
The checksum performed requires the file to be exactly identical to the original.
No extra spaces, identical line termination schemes et cetera - identical byte-for-byte. That means including characters you can not see in an editor.
You can certainly copy the original to a folder side-by with your hand-edited version and run any checksum on the both of them to see if you got it right, but it is probably easier to just copy the original into place.
Simply put, the only reason that check continues to fail is because the file you have there is NOT identical to the original.
good luck
canadianrider said:
edit2: I am on a mac so flashing to stock from fastboot / abd isn't really an option
Click to expand...
Click to collapse
since when does fastboot or adb not work on a mac????
http://developer.android.com/sdk/index.html
hint: they have the package for mac...download it and follow the directions to run fastboot/adb commands...its easier than you think
canadianrider said:
Now I'm trying to get the build prop out of the JOP40D update but when I look in the files it is called "build.prop.p" ... I'm not sure what that last .p is about?
Click to expand...
Click to collapse
That is a *patch* file. It is used to perform binary patching of the original file - it is neither the original nor the replacement for the original.
You need to dig the original build.prop out of the 4.2.1 factory distro, or your own nandroid backups ( you do make backups, right?) The 4.2.1 distros are no longer online from Google, but oldblue910 has your butt covered with his randomphantasmagoria (sp?) site. Check for the link in the OTA post by oldblue910 over in the dev forum.
http://www.randomphantasmagoria.com <--- choose nakasi or nakasig links on rhs of page as appropriate
the easiest option would be to fastboot
system.img
and
boot.img
from the 4.2.2 images google provides...
bftb0 said:
That is a *patch* file. It is used to perform binary patching of the original file - it is neither the original nor the replacement for the original.
You need to dig the original build.prop out of the 4.2.1 factory distro, or your own nandroid backups ( you do make backups, right?) The 4.2.1 distros are no longer online from Google, but oldblue910 has your butt covered with his randomphantasmagoria (sp?) site. Check for the link in the OTA post by oldblue910 over in the dev forum.
http://www.randomphantasmagoria.com <--- choose nakasi or nakasig links on rhs of page as appropriate
Click to expand...
Click to collapse
Thank you! That's what I was looking for.
I did make a backup .... many moons ago.. then the hard drive on my windows pc died. And there went my backups..
Pirateghost said:
since when does fastboot or adb not work on a mac????
http://developer.android.com/sdk/index.html
hint: they have the package for mac...download it and follow the directions to run fastboot/adb commands...its easier than you think
Click to expand...
Click to collapse
Yeah I looked that up after I posted this.. Now to figure out how to use ADB and Fastboot.
Pirateghost said:
the easiest option would be to fastboot
system.img
and
boot.img
from the 4.2.2 images google provides...
Click to expand...
Click to collapse
Not sure how to do that... I've been looking at the thread for putting the n7 back to stock with adb/fastboot .. haven't looked too closely yet (just sat down) but I don't want to relock the bootloader so im not sure if that applies to me. Is there a thread on how to flash firmware with ADB?
Cheers
canadianrider said:
Thank you! That's what I was looking for.
I did make a backup .... many moons ago.. then the hard drive on my windows pc died. And there went my backups..
Yeah I looked that up after I posted this.. Now to figure out how to use ADB and Fastboot.
Not sure how to do that... I've been looking at the thread for putting the n7 back to stock with adb/fastboot .. haven't looked too closely yet (just sat down) but I don't want to relock the bootloader so im not sure if that applies to me. Is there a thread on how to flash firmware with ADB?
Cheers
Click to expand...
Click to collapse
running adb and fastboot commands DO NOT require you to relock the bootloader
its simple. once you have your fastboot executables set up on your computer its literally as simple as putting the device in fastboot mode, and running:
fastboot flash system nameofsystem.img
fastboot flash boot nameofboot.img
Pirateghost said:
running adb and fastboot commands DO NOT require you to relock the bootloader
its simple. once you have your fastboot executables set up on your computer its literally as simple as putting the device in fastboot mode, and running:
fastboot flash system nameofsystem.img
fastboot flash boot nameofboot.img
Click to expand...
Click to collapse
No no I know it does not require you to relock the bootloader.. I just assumed the method used in the one thread I was talking about would relock the bootloader.. I'm just talking out of my ass here though.. I'll start reading on how to use fastboot soon.
If anyone has any good idiot proof guides I'd appreciate it.
follow GOOGLE's directions for setting up fastboot and adb.
it is literally 2 commands
fastboot flash system nameofsystemimgfile.img
fastboot flash boot nameofbootimgfile.img
while the device is in fastboot mode....its not complicated. download the files you need and get started. in the amount of time you have waited on a reply, you could have already had it done. you dont have to learn every command, you just need to 'install' fastboot and adb and put the files in the proper place.
https://developers.google.com/android/nexus/images
http://bit.ly/158k5Wr
ah hah! after a bit of reading and fumbling around with fastboot I did it! thanks for all the help guys. my blood pressure can go down now..
canadianrider said:
ah hah! after a bit of reading and fumbling around with fastboot I did it! thanks for all the help guys. my blood pressure can go down now..
Click to expand...
Click to collapse
see? it wasnt really that complicated.
Pirateghost said:
see? it wasnt really that complicated.
Click to expand...
Click to collapse
no it wasn't... but it was a little more complicated because there's no "this is how you flash on a mac" thread ... I just had to compile different parts from different threads.
canadianrider said:
no it wasn't... but it was a little more complicated because there's no "this is how you flash on a mac" thread ... I just had to compile different parts from different threads.
Click to expand...
Click to collapse
i provided a lmgtfy link, that had many threads listed on setting it up on a mac.
all nexus devices are the same in respect to fastboot/adb
any thread you find for n7, galaxy nexus, nexus4....pretty much universal
Ok, now just came across another issue.. I'm on 4.2.2 and all is well, but now I want to root.
And now adb is saying that my device is offline? I've tried restarting the device. Checking and unchecking USB debugging. Unplugging and plugging it back in but nothing? ... I've read on windows machines it might be a driver issue but with mac's we don't have to install drivers.
ADB worked perfectly fine before the update...
Has anyone made a version of the 4.2.2 update that can be installed even for those of us with modified system/app files? The only way I could get the last two updates was to hunt down this specific version of the update files.
canadianrider said:
Ok, now just came across another issue.. I'm on 4.2.2 and all is well, but now I want to root.
And now adb is saying that my device is offline? I've tried restarting the device. Checking and unchecking USB debugging. Unplugging and plugging it back in but nothing? ... I've read on windows machines it might be a driver issue but with mac's we don't have to install drivers.
ADB worked perfectly fine before the update...
Click to expand...
Click to collapse
What version of adb are you using? (command: "adb version")
With 4.2.2 you should see a pop-up on the tablet asking you to accept the device (PC/Mac) with the RSA fingerprint yadda-yadda-yadda... If you don't hit the accept/OK button within 2-3 seconds, adb will report the device offline ... even if you eventually press the OK/accept message in the popup on the tablet.
Try restarting the adb server on the Mac and be ready to press the button on the popup (make sure screen on tab is unlocked)
Code:
adb kill-server
adb devices
gavingt said:
Has anyone made a version of the 4.2.2 update that can be installed even for those of us with modified system/app files? The only way I could get the last two updates was to hunt down this specific version of the update files.
Click to expand...
Click to collapse
Pirate posted a link of the full 4.2.2 ROM that can be installed with fastboot.
bftb0 said:
What version of adb are you using? (command: "adb version")
With 4.2.2 you should see a pop-up on the tablet asking you to accept the device (PC/Mac) with the RSA fingerprint yadda-yadda-yadda... If you don't hit the accept/OK button within 2-3 seconds, adb will report the device offline ... even if you eventually press the OK/accept message in the popup on the tablet.
Try restarting the adb server on the Mac and be ready to press the button on the popup (make sure screen on tab is unlocked)
Code:
adb kill-server
adb devices
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.29
No pop up on the tablet
Ah nevermind.. I'm just reading on the ADB website that you need version 1.0.31 or higher with 4.2.2 .... thanks for the heads up!
Please note: This will not recover you from a bricked device. This applies to bootloops caused by modifications you made, AFTER successfully rooting.
So you changed your build.prop or deleted a system file you shouldn't have? Your phone is now constantly rebooting? Your variant doesn't have a KDZ available? Here's an easy, albeit time consuming method to recover. (without TWRP or KDZ and no data loss)
First off, if you haven't caused a bootloop yet and you are doing a lot of modifications, do the following. Go to SuperSU and allow su requests on boot. This will allow you to fix minor problems during the bootloop, such as restoring your backed up build.prop or other modified system file. Many times, people will forget to set permissions on a file, especially build.prop. This will cause a bootloop.
If you GRANTED su requests during boot in SuperSU:
Say you set the wrong permissions on build.prop:
While your phone is bootlooping, plug it into your PC, then execute the following commands:
Code:
adb shell
$ stop
$ su
# chmod 0644 /system/build.prop
# reboot
Say you screwed the build.prop up and need to restore a backup you made to your sdcard:
Code:
adb shell
$ stop
$ su
# cp /sdcard/build.prop /system/build.prop
# chmod 0644 /system/build.prop
# reboot
If you DID NOT grant su requests during boot in SuperSU (or if you have tried and failed other methods to recover):
While your phone is bootlooping, plug it into your PC, then do the following:
1. Locate the image you used to root your phone.
2. If the image is on your phone still, just re-root. Your phone will be fixed.
3. If you deleted it from your internal SD card continue to step 4.
4. Open command prompt in folder on your PC containing image, then issue the following command:
This will take a VERY long time (20-30 minutes)
Code:
adb push system_image_name.img /sdcard/system_image_name.img
Note: If you don't have adb mapped to your environment variables, move the image into your platform-tools folder, or whichever folder contains adb. Then run the above command.
5. Re-root
Can't wait to try this when i get home. I soft bricked my LG G4 with a bad system.img so i am trying to restore. Is this actually going to allow me to push the img file back to the phone even though i cant boot?
minirx7 said:
Can't wait to try this when i get home. I soft bricked my LG G4 with a bad system.img so i am trying to restore. Is this actually going to allow me to push the img file back to the phone even though i cant boot?
Click to expand...
Click to collapse
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
I KDZ back to stock, then re-rooted to fix mine. No data loss.
Sent from my VS986 using XDA Free mobile app
Meibs81 said:
I KDZ back to stock, then re-rooted to fix mine. No data loss.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
That is a great method to use, but several variants don't have KDZs :crying:
I'm on the Sprint variant and am getting the Security Error loop. I have no system.img yet, however I can't seem to adb push anything (or see the phone with ADB at all)... am I doing something wrong?
pcrhckyman said:
I'm on the Sprint variant and am getting the Security Error loop. I have no system.img yet, however I can't seem to adb push anything (or see the phone with ADB at all)... am I doing something wrong?
Click to expand...
Click to collapse
That would not be considered a bootloop. That's a brick. I'm sorry, but in your case unless you already had a system image on your phone to flash, you are SOL until we get a TOT file.
tabp0le said:
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
Click to expand...
Click to collapse
Well i am able to access factory reset and i am able to get into download mode and see it from the send_command tool.. HOpe that means my odds are 100% instead!
minirx7 said:
Well i am able to access factory reset and i am able to get into download mode and see it from the send_command tool.. HOpe that means my odds are 100% instead!
Click to expand...
Click to collapse
Not necessarily. Download mode and factory reset(recovery) are located on different partitions than boot and system. Do you at least get to the carrier boot animation while attempting to boot? If so, your chances are good. If not, your chances are bad. The initial commands, including adb push have to be run while the phone is attempting to boot. NOT in download mode or recovery.
tabp0le said:
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
Click to expand...
Click to collapse
tabp0le said:
Not necessarily. Download mode and factory reset(recovery) are located on different partitions than boot and system. Do you at least get to the carrier boot animation while attempting to boot? If so, your chances are good. If not, your chances are bad. The initial commands, including adb push have to be run while the phone is attempting to boot. NOT in download mode or recovery.
Click to expand...
Click to collapse
I get stuck on the LG logo where the light flashes on and off. While this happens if the phone is connected to the computer i hear the USB connection sound in windows. I will be trying it in a few hours.. hope it works!
minirx7 said:
I get stuck on the LG logo where the light flashes on and off. While this happens if the phone is connected to the computer i hear the USB connection sound in windows. I will be trying it in a few hours.. hope it works!
Click to expand...
Click to collapse
You may be able to do it then. Let us know how it goes!
Delete
Peeptastic said:
Can I use this method to solve my particular problem (bypassing setup - I cannot move forward in the setup after a hard reset). Thanks (Can give you more info if you need it)
Click to expand...
Click to collapse
You may be able to. Does your phone boot? How far does it get in the booting process? If you get to initial phone setup, and can't get to the settings app to enable developer options and debugging, then you probably can't use this.. I'm not sure it would work, but you could try-During boot, debugging might enabled by default. (I'm not sure) Right when your bootanimation comes on you might be able to run the command:
Code:
adb shell stop
Then run the rest of the commands/follow this guide. It would be worth a shot.
Delete
Peeptastic said:
I will try it. I can get into the phone to the screen right after entering wifi, then it just stalls. It doesn't freeze, but it also doesn't go anywhere. This is with wifi and data (I left the phone on for a bit and data picked up). If it's related, I turned on Voice Assistance and when the phone gets to the first set up screen she says something about Google play services not working and then "Hangouts needs Google Play services". That could be why I can't move on.....
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
I hear windows chime when it starts up, and the computer charges the phone. Running your command tells me: error: device not found.
Click to expand...
Click to collapse
How did you get in this situation to begin with? Are you able to get into settings at all?
Delete
Peeptastic said:
Factory reset because of the Google play error. Only it looks like Factory reset didn't fix it. And nope, can't get into settings because I can't get out of the set up screen (setup like when you first turn on the phone out of the box). I can get to download mode and stock recovery. As far as I know, there is no way to skip the original LG setup (clockwise button press doesn't work).
Can I adb sideload the image and try that way
Click to expand...
Click to collapse
Unfortunately that will not work. adb sideload is only for flashing .zip files.
tabp0le said:
Unfortunately that will not work. adb sideload is only for flashing .zip files.
Click to expand...
Click to collapse
Delete
every time I run the command while in bootloop it says "Device not found"
sarwaria23 said:
every time I run the command while in bootloop it says "Device not found"
Click to expand...
Click to collapse
This is what is happening to me too. I can see that the phone during boot loop is recognized. I check the device drivers and it shows up under windows as LG.
Crap. not good.
I was having some issue with a rom and figured it was time to reflash/flash a new one. I started the process in TWRP and Aroma froze half way through. I had to reboot. Unfortunately I had already wiped my rom. I can get to fastboot, but I cannot get anywhere else at all. Can anyone point me to a way to get back into recovery?
Should have mentioned, H918.
codman2728 said:
I was having some issue with a rom and figured it was time to reflash/flash a new one. I started the process in TWRP and Aroma froze half way through. I had to reboot. Unfortunately I had already wiped my rom. I can get to fastboot, but I cannot get anywhere else at all. Can anyone point me to a way to get back into recovery?
Should have mentioned, H918.
Click to expand...
Click to collapse
Download adb to your computer. Connect the phone to the computer. Open cmd and use cd or pushd to point cmd to the directory where adb is. Once you are in that directory (from cmd), use " adb reboot recovery "
If what jinkerz9430 suggests doesn't work,
You may have to go back to stock. Here is how to do it for 10j:
https://forum.xda-developers.com/sho...80&postcount=8
Then you reroot as before.
Fixed!
jinkerz9430 said:
Download adb to your computer. Connect the phone to the computer. Open cmd and use cd or pushd to point cmd to the directory where adb is. Once you are in that directory (from cmd), use " adb reboot recovery "
Click to expand...
Click to collapse
Thanks for the response. I ended up rooting around for a long while after this post and settled on using LGUP and found the correct files to reflash to stock. Adb would not work at all. I could get fastboot access, but that is gimped. No driver update would fix the adb problem. I've never had this issue before, with any phone. LG seems to make things more difficult than necessary. I miss Samsung.
Thanks
androiddiego said:
If what jinkerz9430 suggests doesn't work,
You may have to go back to stock. Here is how to do it for 10j:
https://forum.xda-developers.com/sho...80&postcount=8
Then you reroot as before.
Click to expand...
Click to collapse
That link seems to 404. I'd be interested in reading that though, if it isn't actually a 404. I believe what you are referring to is what I did though LOL. I found the kdz and dll, and used LGUP to get flashed back to stock. I'll never let it out of my sight again.
codman2728 said:
Thanks for the response. I ended up rooting around for a long while after this post and settled on using LGUP and found the correct files to reflash to stock. Adb would not work at all. I could get fastboot access, but that is gimped. No driver update would fix the adb problem. I've never had this issue before, with any phone. LG seems to make things more difficult than necessary. I miss Samsung.
Click to expand...
Click to collapse
If you flashed stock with lgup then everything is back to factory settings. Is this is the case, then the autorization you gave to your computer via usb debbug (where the prompt appears if the device is connected to a other device without authorization asking you whether you want to authorize it or not). Is also back to factory settings. Which means not even developer mode is on. But after you turn developer mode on and usb debbug then connect the phone to the computer and it will ask you once again for authorization
[/B]
codman2728 said:
That link seems to 404. I'd be interested in reading that though, if it isn't actually a 404. I believe what you are referring to is what I did though LOL. I found the kdz and dll, and used LGUP to get flashed back to stock. I'll never let it out of my sight again.
Click to expand...
Click to collapse
That's it!
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Neskobar said:
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Click to expand...
Click to collapse
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Choose an username... said:
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Click to expand...
Click to collapse
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Neskobar said:
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Click to expand...
Click to collapse
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
raystef66 said:
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
Click to expand...
Click to collapse
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Neskobar said:
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Click to expand...
Click to collapse
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
raystef66 said:
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
Click to expand...
Click to collapse
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
edit - I renamed the zip to "update.up" and couldn't get that to work either. It's not detected in the update section of settings, and I still get the same "Sorry, you can't sdcard upgrade" message.
edit #2 - I tried naming it to "update.up.zip" and it detected it this time, trying to run the update now.
Neskobar said:
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up, when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
Click to expand...
Click to collapse
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
raystef66 said:
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
Click to expand...
Click to collapse
Ah, I should have mentioned that. This is the message I'm getting when I try that:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Click to expand...
Click to collapse
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Neskobar said:
Ah, I should have mentioned that. This is the message I'm getting when I try that:
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Click to expand...
Click to collapse
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
raystef66 said:
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
Click to expand...
Click to collapse
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
raystef66 said:
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
Click to expand...
Click to collapse
Ok, I attached it to this post, hope it works.
Neskobar said:
Ok, I attached it to this post, hope it works.
Click to expand...
Click to collapse
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
raystef66 said:
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Click to expand...
Click to collapse
Yes, that's what I was concerned about. The very first update i tried to install was N-B09, and everything else has been an older update after that, so maybe it won't overwrite the newer files, or something? Or possibly something else went wrong in the first update, so everything else just wouldn't work because of that?
I'm putting N-B01 onto my SD card right now, so I'll test that, and if it doesn't work I'll wipe the phone and start again. If I do need to wipe the phone, however, which update would you recommend trying first? N-B09? That might confirm if it was just bad luck on the first try, or whatever.
RobboW said:
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Click to expand...
Click to collapse
Agreed, that sounds like a possibility to me. I'll probably end up wiping and starting over.
Choose an username... said:
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
Click to expand...
Click to collapse
Yes the tab autocomplete works on the "u" of update.zip and "o" of ota.zip, when I tried both. I have to admit, I was quite excited to see your suggestion there, as I thought that would be a really easy way to confirm if something isn't right with adb, but never mind.
I still don't understand why it gives me this error then, though: * cannot read 'update.zip' *.
ramnkc said:
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
Click to expand...
Click to collapse
Thanks for the suggestion, and yes, I did confirm that I renamed the right zip file. That would have been easy thing to fix though, sadly.
edit - I tried the same adb commands with windows powershell too, and got exactly the same error messages.
What ROM was on it before you flashed B09?
Updating to N-B01 worked! I've no idea why this happened the way it did, nor why adb didn't work for sideloading, but I'm really glad that it finally worked.
The order of events:
1) Installed N-B09 via transfer to SD using the android updater, no difference in android version, but appeared in update history.
2) Installed MM-B11, same as above.
3) Tried various methods of installing MM-B11, including:
- SD transfer
- recovery mode SD update (which the phone wouldn't let me do, saying, "Sorry, you can't sdcard upgrade").
- ADB sideload (which never worked even slightly. I always got the message, * cannot read 'update.zip'/'ota.zip'/'update.up.zip' *)
- Tried the above methods with variously named zip files, including "update, ota, and update.up".
- Tried the above methods, but wiping the cache in between processes.4) Installed N-B01 via transfer to SD using the android updater. This time the process took a lot longer and after rebooting the phone, went through the process of optimizing apps, which it had never done before.
Ok, I think that's everything.
The only theory I can come up with is that: Something (I have no idea what, though) went wrong with the first update attempt and every subsequent attempt to update to an older version didn't work because it didn't want to overwrite newer android version files? That doesn't seem quite right to me, though, as I would assume that whatever is in the update.zip would just overwrite everything as standard, because the assumption would always be that these files are newer than the existing ones.
What would you recommend that I do next? Should I try to push through the latest N update now, then? Has this outcome helped you figure out what the problem was/is?
Whatever the case, I'm happy to finally get an update working. Thanks very much for all your help and suggestions, guys. It was much appreciated!