I was trying to manually install RC29 and for some reason when it goes to install it says that there are "No Signature" and that it cant update. Anyone have a way to fix this or had this issue?
Even when I tried to manually update to that it gave me the same No Signature error and wouldnt update it. Basically I cant get passed the Google log in because something must have happened to the phone because when I restored my phone and went to set it up with my new gmail account it wont get passed that screen and wont connect to the servers. So basically I wanted to update it again with a full install of RC29 in hopes of it fixing the problem.
ballaholyk84 said:
I was trying to manually install RC29 and for some reason when it goes to install it says that there are "No Signature" and that it cant update. Anyone have a way to fix this or had this issue?
Even when I tried to manually update to that it gave me the same No Signature error and wouldnt update it. Basically I cant get passed the Google log in because something must have happened to the phone because when I restored my phone and went to set it up with my new gmail account it wont get passed that screen and wont connect to the servers. So basically I wanted to update it again with a full install of RC29 in hopes of it fixing the problem.
Click to expand...
Click to collapse
Have you edited anything on the phone? Have you touched the OTAcerts.zip file?
neoobs said:
Have you edited anything on the phone? Have you touched the OTAcerts.zip file?
Click to expand...
Click to collapse
Yes I did. I did the mod hack that JesusFreke posted and looking to add them back or reverse the process.
ballaholyk84 said:
Yes I did. I did the mod hack that JesusFreke posted and looking to add them back or reverse the process.
Click to expand...
Click to collapse
That is why you get the no signature file error. OTAcerts.zip is the signature file.
neoobs said:
That is why you get the no signature file error. OTAcerts.zip is the signature file.
Click to expand...
Click to collapse
So is there a way that I can get those back on the phone?
ballaholyk84 said:
Yes I did. I did the mod hack that JesusFreke posted and looking to add them back or reverse the process.
Click to expand...
Click to collapse
to reverse look in that AndroidMod.zip JesusFreke posted look for update - Restore Orginial RC29 Boot Image.zip. hope i helped
"Finally, the "update - Restore Original RC29 Boot Image.zip" file is an update.zip file signed with the test keys, which will restore your boot partition back to the stock RC29 image. Useful if you accidentally hose your boot partition.."-JesusFreke
humble said:
to reverse look in that AndroidMod.zip JesusFreke posted look for update - Restore Orginial RC29 Boot Image.zip. hope i helped
"Finally, the "update - Restore Original RC29 Boot Image.zip" file is an update.zip file signed with the test keys, which will restore your boot partition back to the stock RC29 image. Useful if you accidentally hose your boot partition.."-JesusFreke
Click to expand...
Click to collapse
I see that but How do I apply it since I cant get into the phone?
ballaholyk84 said:
I see that but How do I apply it since I cant get into the phone?
Click to expand...
Click to collapse
try naming it update.zip and updating it from the sdcard.
neoobs said:
try naming it update.zip and updating it from the sdcard.
Click to expand...
Click to collapse
Got that to work thanks! Now if only I can transfer this damn RC29 to my card without some part being corrupt. I Have tried about 5 times with something being corrupt
Help i need to restore the recovery.img for the G1 RC29
I mest up my G1 it no longer could take my RC33 update, i get an error
E:Failure at line 5 assert getprop("ro.build.fingerprint")== "tmobile/kila/dream/trout:1.0/TC4-RC30/116143:users/ota-rel-keys,release-keys" l l getprop("robuild.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys.release-keysInsta
i was going to do the multitouch on my G1 but when i started to follow this link
http://hehe2.net/gadgets/howto-multitouch-tethering-task-manager-for-android-g1/
i got stuck on the telnet command for the
rm -f /system/recovery.img
it would not accept it, andy my Dumass decided to skip that step and enter the
flash_image recovery /sdcard/recovery_testkeys.img
since i knew that i had the recovery_testkeys.img in my sdcard
(to be honest, i dont know squad about telnet with the G1, i am familiar with the linux terminal but its not the same)
so i stop there because i started to get nervous about my G1 getting **** up, i figure that i would just do a factory reset and wala ill be back in business but nah, after the factory rest i obiously was going to be in the RC29, so i tried doing the manual update to the RC33 but now it will not take it, i keep on getting the message that is in the beginning of this post, i know the update file i am using is not corrupt or incorrect, i had my girls G1 that i just purchase for her and i decided to test out the update in hers, since its still on the RC30, and it work fine.
Please Someone help, i know i should had tough my firmware.....
Related
My G1, which has been converted to a JF ADP1.1, gave me the following popup message just now:
! A system update is available
-----------------------------
Holiday phone update 2 of 2: This is
a full system update. Your data and
settings will be preserved.
Update now Update later
I'm going to click "Update later" since I don't know exactly what this is.
I searched the XDA Dream forums for "Holiday phone" without finding anything, but if this is something previously discussed I'm sorry for the double post.
I have tried to attach a picture of the screen as well.
~Christopher
I went to Device Info, and clicked "Check for upgrade".
The result was:
Pending upgrade:
signed-holiday_devphone-ota-130444-debug.55489994.zip
Download status:
Completed (200): 45722649 of 45722649 bytes
Check-in status:
CHECKIN_SUCCESS
grenness said:
Pending upgrade:
signed-holiday_devphone-ota-130444-debug.55489994.zip
Download status:
Completed (200): 45722649 of 45722649 bytes
Click to expand...
Click to collapse
Does anyone know where in the phone file system these files go?
If I can find it, I can probably copy it to the SD card and then attach it to this thread.
~Christopher
so this update is only for ADP?
any idea what's new in it yet? or have you not updated?
i imagine it will just be RC33 for ADP, with Latitude etc.
only one way to find out
Meltus said:
so this update is only for ADP?
any idea what's new in it yet? or have you not updated?
Click to expand...
Click to collapse
I'm guessing this is for ADP only, since my phone (as far as Google knows) is an ADP (converted from a G1 using JesusFreke's ADP image) and the name of the .zip contains *devphone*.
No, I haven't proceeeded with the upgrade, I would like some other inputs from the forum first.
~Christopher
hrm, mine is saying its up to date when I hit the update checker. Guess i'll keep checking, as I would much rather stay on adp code and not run the tmobile.
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
kash04 said:
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
Click to expand...
Click to collapse
So it has the update for "Check for updates". Looks like it probably is the ADP1's answer to the RC33...
kash04 said:
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
Click to expand...
Click to collapse
I appreciate the link, but JF-ADP1.1 is based off the images you linked to. Whatever the holiday update is is different.
Can you look in /cache and see if you see an update file? I'd love to get a copy. (Also, run 'logcat' and look for urls.)
I went ahead and accepted the update.
Took two reboots (one was probably the radio upgrade which I had installed several days ago), but now it's stuck on the pulsating android boot screen :-(
~Christopher
grenness said:
I went ahead and accepted the update.
Took two reboots (one was probably the radio upgrade which I had installed several days ago), but now it's stuck on the pulsating android boot screen :-(
~Christopher
Click to expand...
Click to collapse
RC33 takes -forever- to do it's first boot. On the order of 10 mins for some people.
Does 'adb logcat' show anything?
I left it on the table in front of me, I swear it took around 10 minutes before it proceeded with the boot-up, and now it seems to work fine. Has Google voice search and Latitute.
Don't know what's missing - looks like Sansdroid auto-rotate no longer works.
~Christopher
the download url is similar to rc OTA updates , just need to replace filename:
Code:
https://android.clients.google.com/updates/signed-holiday_devphone-ota-130444-debug.55489994.zip
I am the one that made a post on http://andblogs.net/2009/01/new-adp1-images-leaked/
I installed both updates and now have Google Latitude en Voice Search available. I tried to look at logcat but the information was not there anymore.
I made a post on the Google Android forum (http://groups.google.com/group/android-developers/browse_thread/thread/4fc696bd66b988f6#) and got responses from JBQ. But I doesn't make sense to me. I want to know if this update is an official one.
Is it possible to use this update directly on a ADP 1 with 1.0 image?
A friend of mine has not updated his ADP to 1.1 yet.
jcdekoning said:
I am the one that made a post on http://andblogs.net/2009/01/new-adp1-images-leaked/
I installed both updates and now have Google Latitude en Voice Search available. I tried to look at logcat but the information was not there anymore.
I made a post on the Google Android forum (http://groups.google.com/group/android-developers/browse_thread/thread/4fc696bd66b988f6#) and got responses from JBQ. But I doesn't make sense to me. I want to know if this update is an official one.
Click to expand...
Click to collapse
It is, it just might not be released yet.
cannot upgrade from JF1.41 RC33
after verifying update package...
message: failure at line 4
assert getprop ("ro.bootloader") =="0.95.0000"
Installation aborted.
Which image do I need to be able to flash?
endolin said:
after verifying update package...
message: failure at line 4
assert getprop ("ro.bootloader") =="0.95.0000"
Installation aborted.
Which image do I need to be able to flash?
Click to expand...
Click to collapse
It doesn't like the bootloader test. (And you won't be able to go from rc33 to adp1.1 anyway, since the userdata is different.)
If you are comfortable with the signing process, you can unpack it, remove the bootloader line from META-INF/com/google/....../update-script and resign it and it'll work. Alternately, give me a little time and I'll post one with no checks.
thanks for your quick reply.
i'm not familiar with the signing process, therefore I'd be glad to see a modified
release from you.
Disconn3ct said:
It doesn't like the bootloader test. (And you won't be able to go from rc33 to adp1.1 anyway, since the userdata is different.)
If you are comfortable with the signing process, you can unpack it, remove the bootloader line from META-INF/com/google/....../update-script and resign it and it'll work. Alternately, give me a little time and I'll post one with no checks.
Click to expand...
Click to collapse
http://andblogs.net/2009/02/new-adp1-update-official-with-google-voice-and-more/ has the download that does no system checks. So anyone should be able to apply it as update.zip
i want to flash my phone with jf's roms but i want to know if he already has a rom that has root and wont need to be activated because i dont have a data plan
The ADP1 updates (incl the JFMod version) have an option on the initial setup wizard to bypass activation. However, running ADP1 means you won't be able to buy apps from the Market. Alternately, install the JFMod version of RC33 and follow the instructions in the "How to register the G1 without a sim or dataplan" thread.
ruffrider5956 said:
i want to flash my phone with jf's roms but i want to know if he already has a rom that has root and wont need to be activated because i dont have a data plan
Click to expand...
Click to collapse
just to let you know your going to get flamed for this. There is a sticky thread on this exact subject that you just asked a question on. Which is NO MORE than 10 topics to read to find what your looking for. Please read before posting and you will enjoy your stay here a little more.
inpherno3 said:
just to let you know your going to get flamed for this. .
Click to expand...
Click to collapse
Easy now don't be so silly ....
jshields said:
Easy now don't be so silly ....
Click to expand...
Click to collapse
lol silly is the new angry you didn't know?
jashsu said:
The ADP1 updates (incl the JFMod version) have an option on the initial setup wizard to bypass activation. However, running ADP1 means you won't be able to buy apps from the Market. Alternately, install the JFMod version of RC33 and follow the instructions in the "How to register the G1 without a sim or dataplan" thread.
Click to expand...
Click to collapse
wrong.
you can download and buy apps from the market.
what you can't do with an ADP is buying protected apps only and they are very few.
inpherno3 said:
just to let you know your going to get flamed for this. There is a sticky thread on this exact subject that you just asked a question on. Which is NO MORE than 10 topics to read to find what your looking for. Please read before posting and you will enjoy your stay here a little more.
Click to expand...
Click to collapse
i read the sticky but it said rc30 i reread it and it was for rc30 up so i got that down so anyway if i flashed with a modded rc33 i can unlock using the method posted in the sticky right and can someone give me a link to the modded rc33 i think i found it but im not sure and i dont want to brick my phone so thank you guys for the help
so this how you flash the phone with a different rom
1. Format your phone's SD card to FAT32 mode:
* Hook your phone up to your computer using a USB cable and then wait for the notification to show up in your title bar of your phone.
* Click the notification, and then click "Mount".
* A new removable disk should show up on your computer. Right click it and select Format, and select FAT32 as the file system type.
2. Download and unzip the RC29 or RC7 image file. Copy the DREAMIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
3. Turn the device power off.
4. Hold Camera button, and press Power button to entry bootloader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
5. As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS.
6. After it is finished, perform the restart your phone.
but instead of using rc29 i want to use the modded rc33 so i would be going from stock rc33 to modded rc33 because i read it was already rooted if anyone can tell me thats right ill appreciate it
ruffrider5956 said:
so this how you flash the phone with a ut instead of using rc29 i want to use the modded rc33 so i would be going from stock rc33 to modded rc33 because i read it was already rooted if anyone can tell me thats right ill appreciate it
Click to expand...
Click to collapse
Nope.
Gotta go RC33 > RC29 > Rootit >RC33 JF Edition.
ruffrider5956 said:
but instead of using rc29 i want to use the modded rc33 so i would be going from stock rc33 to modded rc33 because i read it was already rooted if anyone can tell me thats right ill appreciate it
Click to expand...
Click to collapse
That would be nice. I wouldn't call it "wrong" like the other guy did, because wanting something isn't wrong. It just won't work since there is no mod-RC33 image available *in the required format*. Problem is that in order to write a system image to a stock consumer device, that system image needs to be digitally signed with a private key that we simply don't have available.
So the procedure becomes... write the older system image that has a known exploit available, and use that exploit to root the device, allowing you to write the engineering bootloader, which allows the installation of your desired system image.
ok so if i go from rc33 to rc29 and root it how do i got to jf's rc33 wont i loose the root
ruffrider5956 said:
ok so if i go from rc33 to rc29 and root it how do i got to jf's rc33 wont i loose the root
Click to expand...
Click to collapse
AAAAHhhhhhhhhhhhh lol
No you wont cause JF roms are modded so we wont.
Don't ask how lol
Mikey1022 said:
AAAAHhhhhhhhhhhhh lol
No you wont cause JF roms are modded so we wont.
Don't ask how lol
Click to expand...
Click to collapse
lol bro then why cant i just go from rc29 to the modded rc33 why do i have to first root rc29 then go to modded rc33 and also do i flash the modded rc33 just how i did the rc29 or is it going to be different
Read,Read, and Read some more.
ruffrider5956 said:
lol bro then why cant i just go from rc29 to the modded rc33 why do i have to first root rc29 then go to modded rc33 and also do i flash the modded rc33 just how i did the rc29 or is it going to be different
Click to expand...
Click to collapse
I'll just ask this.....Why does the sun rise from the East and not the West.
There are just some things you dont ask why to. It just is.
ruffrider5956 said:
also do i flash the modded rc33 just how i did the rc29 or is it going to be different
Click to expand...
Click to collapse
rc33 has to be renamed update, place it on your cards root, reboot *home+menu+power key* let go of menu and power key when your phone restarts booting up. HOLD THE HOME KEY STILL, till you enter recovery mode.
Click Alt+l
Click Alt+s
when update is one installing,
Click Home+back key.
Cross your fingers that your phone won't blow, if it doesn't, you did it
your best solution
get the Haykuro Sapphire port...the latest 4.9 is working awesome, you can just click the SKIP button on the registration, but if you are going to use the market later on, you need to connect on wifi and login with you gmail account. plus, you will have many other features on your phone like auto-rotate, camcorder, stereo BT (Still buggy) and many more.. Hope this helps you. good luck.
Tomorrow i send in my g1. and it is rc33 rooted, on the phone the htc person told me that they will inspect it to make sure there is not any 3rd part software on it for warranty void purpases. please help me! i need to get this done!
re-flash to RC29
Done!
You might consider using the search function. This subject has been considered many, many times before.
flash the Dreaming.nbh file from the original files you downloaded when you were rooting your phone and that will take you back to rc29 and it will automaticlly update its self back to rc33 and u wont have anything to worry about
dang you beat me to it...lol
only by a second!
idragbody said:
flash the Dreaming.nbh file from the original files you downloaded when you were rooting your phone and that will take you back to rc29 and it will automaticlly update its self back to rc33 and u wont have anything to worry about
Click to expand...
Click to collapse
what is the name of the file sopossed to be on the memory card
dreaming.nbh.zip or dreaming.zip dreaming.nbh errrr what
jbettt said:
what is the name of the file sopossed to be on the memory card
dreaming.nbh.zip or dreaming.zip dreaming.nbh errrr what
Click to expand...
Click to collapse
DREAIMG.nbh (DREAm + IMaGe)
Look at the spelling very carefully, it must have the correct spelling to work.
http://forum.xda-developers.com/showthread.php?p=3690555&highlight=dreaimg.nbh
Question answered and has been asked before.
Closed
Dave
.... or maybe download link from google?
Hello all,
Wondering if someone could try this since I already upgraded won't work but when i got the update on my phone I was able to go to the cache folder and extract from fumo file the following zip that is on mediafire.
Called OTApkg.zip like the mt3g update file.
Should be the current update.
Anyone on the original firmware should be able to flash this from recovery and be up and running with new firmware
Let us know if it worked.
Just rename update.zip and put to root of memory card
boot with vol down and power.
down and select recover
vol up and power to get options
select update from update.zip and should run.
Download:
http://www.mediafire.com/?jm90w7hr922bpd4
You didn't get a chance to test this at all? Can anyone test this and tell me if it works. Before even thinking about rooting I always like to have a set of file to recover with. G1, original mytouch, and slide i all have had way to undo before I rooted.
Didn't work for me. When I tried it I got an error that said
Code:
-- Invalid operation --
On a side note, when I reboot into recovery I get this
Code:
E:Can't open /cache/recovery/command
Anyone else? Is this correct?
Reviewing the code does look like the right file but may not be able to be flashed manually.
First line in update script is mount ( "MTD" , "system" , "/system" )
Looks like boots is a special "fota" mode that will allow modification and this update run like that won't initialize it.
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
travisjames said:
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
Click to expand...
Click to collapse
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Beast84 said:
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Click to expand...
Click to collapse
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
travisjames said:
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
Click to expand...
Click to collapse
Great that means theres no problem with my phone. I feel so much better now
Beast84 said:
Great that means theres no problem with my phone. I feel so much better now
Click to expand...
Click to collapse
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
travisjames said:
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
Click to expand...
Click to collapse
Very true. In the Vibrant section, those guys were able to make update.zip's that were flashable through the stock recovery. Maybe someone can do that for us with this update. I have no dev experience at all but I am willing to test whatever comes up.
It was weird because when I looked at it
It was in the cache directory but not directly
in the cache directory was a file fumo which on browsing just looked like a file on the phone using sufbs.
But when I copied it to the device using the app that is when fumo turned into a folder and opened and saw that file.
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
bobsbbq said:
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
Click to expand...
Click to collapse
No, there isn't a way for T-Mo to push the OTA to you.
Did the rep say anything about the other update?
If you bought the phone full price instead of on contract be sure to check online and change the phone Tmobile has for you to a Mytouch 4g I think that could have something to do with it. I had mine listed as a Mytouch 3G still and I went and changed it and hope it'll make a difference.
Pretty sure that just changing the phone on my tmo wont change. Only thing that i can think of minus something being changed since i got it off the device vs a direct download if someone can get the link or call tmo to check on thier plans if past thier time frame they may be able to do something
Just hopefully someone could get the google link for it instead.
Sent from my HTC Vision using XDA App
I called T-Mobile today about the OTA and they said that it did matter that my plan wasn't set a mytouch package. They told me the OTA should have gone out after my first phone call. Sounds like a bunch of bull**** to me, just figured I'd fill in anyone who was interested. They told me I should have it within 48 hours. *crosses fingers*
*edit* my friend works at T-mobile, she just received the phone herself and after your phone is set as a Mytouch4G, use *#*#checkin#*#* should help start the process, now were both waiting...
I've been waiting since Sunday. Hopefully has nothing to do with having debugging enabled.
Been leaving the phone connected most of the time running
Code:
adb logcat | findstr clients.google
to try and snag the link for the update.
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
johnowa636 said:
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
Click to expand...
Click to collapse
I've been messing with this. It seems you can put in a filter (I put clients.google) but it doesn't matter if you set it to save to your card periodically it saves the entire logs... but you can open those on a pc later and search them or if you're a linux type you can cat file | grep "clients.google"
Hi,
I'm kind of a newbie with phones but good with computers so:
I used the following Fix for the call volume issue on my OPO:
https://forums.oneplus.net/threads/tool-jlouder-v1-0-rc2-makes-your-phone-call-louder.69733/
Seems that because of this Fix I get an error when trying to run the the update OTA or sideloading.
I get following error:
E error in tmp sideload package.zip status 7 installation aborted
Others who have used this fix have same issues. Any easy way out??? I'm not rooted and otherwise stock.
"I think it's the volume fix that changes the md5 checksum on the xml file and therefore kills the update."
Thanks In Advance,
Ken
kenfb1 said:
Hi,
I'm kind of a newbie with phones but good with computers so:
I used the following Fix for the call volume issue on my OPO:
https://forums.oneplus.net/threads/tool-jlouder-v1-0-rc2-makes-your-phone-call-louder.69733/
Seems that because of this Fix I get an error when trying to run the the update OTA or sideloading.
I get following error:
E error in tmp sideload package.zip status 7 installation aborted
Others who have used this fix have same issues. Any easy way out??? I'm not rooted and otherwise stock.
"I think it's the volume fix that changes the md5 checksum on the xml file and therefore kills the update."
Thanks In Advance,
Ken
Click to expand...
Click to collapse
Don't you have a stock backup?
If you don't, have you tried reverting the values?
Wait... if you're not rooted then how did you perform the change in the file in the first place? Did you root, do the change and then unroot?
Like what badjoras said, revert back to the stock file and then apply the OTA.
I haven't followed up on the whole OTA readings, but there are zips out there that will bypass the check of the files. You can try looking into those as well.
zephiK said:
Wait... if you're not rooted then how did you perform the change in the file in the first place? Did you root, do the change and then unroot?
Like what badjoras said, revert back to the stock file and then apply the OTA.
I haven't followed up on the whole OTA readings, but there are zips out there that will bypass the check of the files. You can try looking into those as well.
Click to expand...
Click to collapse
Hi,
Not rooted, I just followed the steps in the fix I posted above.
To revert back to stock file, will that wipe all data? Don't want that.
I'm not great at the phone stuff yet , still learning but trying to be careful.
Can I sideload the previous version without losing data??
Recovery on this phone option is "wipe data factory reset???"
Sorry for being a dummy, it's a big learning curve for me,
Thanks, Ken
Hi
kenfb1 said:
Hi,
Not rooted, I just followed the steps in the fix I posted above.
To revert back to stock file, will that wipe all data? Don't want that.
I'm not great at the phone stuff yet , still learning but trying to be careful.
Can I sideload the previous version without losing data??
Recovery on this phone option is "wipe data factory reset???"
Sorry for being a dummy, it's a big learning curve for me,
Thanks, Ken
Click to expand...
Click to collapse
Hi,
After trying several options, I'm still in Limbo with this.
Can't get the update to install, still looking for ideas.
Ken