Related
Hi there, I'm new here and I need your help.
My ViewPad7 haven't an original <3e> recovery because i get it from another and it run cooked rom.
Now i want to back to the stock rom following here: http://forum.xda-developers.com/showthread.php?t=1601117 but it need an original <3e> recovery.
Could you kindly help me to get it, if you have a backup of original <3e> recovery from your ViewPad7, please send it for me.
Or you can backup your stock recovery follow this guide: http://forum.xda-developers.com/showthread.php?t=1015005 then help me.
Thank you so much. Sorry for my English.
Anyone, please help?
For Vpad7 - do you have the "older" non-ITE or "newer" ITE (multi-touch) screen - original/stock recovery image file or whatever?
If you aren't sure - post your Vpad7's production date, which is on the printed label on the back as that should help ...
I don't know about the 'non-ITE' or ITE screen of my device. Its production date is: 28-4 2011
Please help me!
Thanks Letitride
Based on device's production date, it's "most" likely an ITE device (there is nothing certain or definitive about it ...)
Okay, calvary to the rescue for fellow XDA's.
AS - please check your PM too (you got mail ...)
Letitride said:
Based on device's production date, it's "most" likely an ITE device (there is nothing certain or definitive about it ...)
Okay, calvary to the rescue for fellow XDA's.
AS - please check your PM too (you got mail ...)
Click to expand...
Click to collapse
I'm having the same problem here. Letitride can u help me out also?
Lanfear28 said:
I'm having the same problem here. Letitride can u help me out also?
Click to expand...
Click to collapse
Have you read the following thread & try it to see if you can restore your device ?
http://forum.xda-developers.com/showthread.php?t=1601117
If not or it failed, please be a little more specific about your issues and error messages/description of bootup problem, etc. ?
sadonsu assailants
I have the cwm recovery and cant get back the original <3e> recovery to flash the original Viewsonic firmware(v3_420)
@Letitride
Works like a charm
Lanfear28 said:
I have the cwm recovery and cant get back the original <3e> recovery to flash the original Viewsonic firmware(v3_420) @Letitride ... Works like a charm
Click to expand...
Click to collapse
Restored & working w the "alternative" *.img as referenced in PM then, excellent & enjoy the Vpad7 - only wished it's a bit faster, overclocking or whatever. But, it is what it is and loved the 7" factor, much easier to slip into a pouch, pocket, jacket, etc. to take along.
Is there anybody with original Viewsonic firmware(v3_420) and with working internet thru mobile data?
i got the viewpad7 back to original with stock recovery that i extracted it from stock rom, thanks
Hello, sorry for bumping this thread but it is relevant to what I need.
EDIT: Moving to thread for visibility.
I recently rooted my Viewsonic Viewpad 7 and put on a custom ROM. I noticed that wifi was not working so I tried some fixes, which none of them worked. One of those fixes involved formatting the sd card. After formatting, I realized I made a huge mistake as my backups are now all gone.
So I have the clockwork recovery installed (v5.0.2.6) and I think it is causing problems. I tried using Software Update Tool L3 (SUT L3) in order to restore the firmware back to normal using the .nbo from the Viewsonic site but I think I need the original <3e> recovery. Whenever I try to recover using the tool, it reboots the device into Recovery mode and after a few minutes I get the error:
Error Code: 0xc60e
Error: Download fail,
Error = SE_ERR_SUT_DETECT_DEVICE_FAIL (0xC60E).
I believe this is because it is expecting the original 3e recovery and doesn't recognize the clockwork recovery. I tried to find a copy of the original recovery.img but I can't find it online anywhere. This thread is the closest I've gotten. Please let me know if there is anything I can do to fix this. Or if anyone has a copy of the original 3e recovery, it may help me out.
Thanks!
FTM Mode Info:
SWVer=3.240
MODEL:FM6-0001
HWVer:107
clandor said:
... rooted my Viewsonic Viewpad 7 and put on a custom ROM ... So I have the clockwork recovery installed (v5.0.2.6) and I think it is causing problems. I tried using Software Update Tool L3 (SUT L3) in order to restore the firmware back to normal using the .nbo from the Viewsonic site but I think I need the original <3e> recovery. Whenever I try to recover using the tool, it reboots the device into Recovery mode and after a few minutes I get the error:
Error Code: 0xc60e
Error: Download fail,
Error = SE_ERR_SUT_DETECT_DEVICE_FAIL (0xC60E).
I believe this is because it is expecting the original 3e recovery and doesn't recognize the clockwork recovery. I tried to find a copy of the original recovery.img but I can't find it online anywhere. This thread is the closest I've gotten. Please let me know if there is anything I can do to fix this. Or if anyone has a copy of the original 3e recovery, it may help me out.
FTM Mode Info:
SWVer=3.240
MODEL:FM6-0001
HWVer:107
Click to expand...
Click to collapse
Are you using the "correct" factory *.nbo file with SUTL3 (which ver.) as it looked like your model is likely an ITE (newer) model ?
Can you boot the device into CWM Recovery mode now? Does it start up with the VS Android boot animation?
I will have to look for my backups as I've them on a backup server somewhere and/or in cloud storage ... will look & see what I have?
Haven't flash/done any factory restoration work on the Vpad7 in over a year+ now but, as I recall, flashing the *.nbo file via the PC with the factory update utility will wipe the device clean and restore it to factory fresh, locked mode so it should NOT matter what recovery you have on the device now.
Please describe in greater details the steps you took in trying to restore ... it's still a joy to go back to the Vpad7 but hard to let go of the new Nexus 7 quad-core "toy" these days for me ...
Thank you for your help.
I am pretty sure it is an ITE model. It's HWVer is 107, and I used this thread to help figure that out.
I downloaded firmware (.nbo) v3_420 and v3_62 from here. (Under Downloads > Drivers)
Here are the steps I took in order to try and restore.
I started off by enabling USB debugging and plugging in the tablet.
I opened up SUTL3 v1.7.9 and selected one of the firmwares (both yield same result). The update option I set to Erase user data. Once I hit next, it says Updating the Phone software, please wait.
The device restarts into recovery mode. The recovery menu title says CWM-based Recovery v5.0.2.6 which is a custom one I changed. I do not know how to get it back to the original as I have lost the backup.
After about a minute or so, I get
Error code: 0x4000
Error: Download fail,
Error = DEVICE_NOT_CONFIGURE (0x4000).
At this point when I retry using SUT L3 without leaving the recovery mode, I will only get the error from the previous post.
I'm not sure what my options are but my goal is to get back to the original ROM or get wifi working again on the current ROM. The current ROM I am using is CleanView Ice v1.3. I tried both the ITE version and non-ITE version and there seems to be no difference.
The only thing I seem to be able to do is Install ZIP from sdcard which lets me switch between custom ROMs but it doesnt fix the wifi problem or let me go back to original.
---
Edit: I tried doing the same thing a few more times with my antivirus disabled and it's still the same.
Also, I'm not sure if this will help at all but I tried to use the Synchronization tool that shows up on the PC when plugging in the device. It gave me the error "Can't access data on handheld! Please check the connection between desktop and handheld and at least enter Contacts once if you just clear your data!" These may be related as I have accessed Contacts and even added one in to test and this error comes up every time.
Maybe some kind of driver problem?
clandor said:
I am pretty sure it is an ITE model. It's HWVer is 107, and I used this thread to help figure that out.
I downloaded firmware (.nbo) v3_420 and v3_62 from here. (Under Downloads > Drivers) ... Maybe some kind of driver problem?
Click to expand...
Click to collapse
Okay, let's see - yours is ITE (UK-based) and running the same firmware as mine (USA) and v3_62 will work too, mine is on v3_420.
You still have working CWM 5.x on your device and can boot into it (small pin hole on the button to reset, etc.)
Okay, a # of points - the SUTL3 is run from the PC together with the *.nb0 file - running Windows XP or Vista, go the Command Prompt - Vpad7 drivers are already installed, give it a try - does it work as that will restore it to factory state - it should not need the Stock Recovery to flash it (I could be mistaken as it's been a while) Unpack the Zip file so that the utility will read the *.nb0 file directly.
First suggestio, however, is that if you have working CWM - my recommendation would be to flash from custom recovery, EUv1.7-ITE firmware in Zip file format - as linked here in Dropbox account of mine, OP/developer's link is no longer accessible or available. https://dl.dropbox.com/u/64025118/EUViewpad7v1.7b-ITE.zip
Download & transfer to mSD card, reboot into CWM, wipe dalvik cache, cache & system/full reset - then, flash the zip file and it should be done in about 10 minutes, be patient and go thru the Setup - if all goes well, your ITE device is back to life again. This is my preferred ROM and WiFi works well, if necessary - do a Master Reset again from the running Rom if necessary, reboot once & then setup your WiFi again.
Turn-off Antivirus & Firewall on the PC while flashing ... let me know whether you can get into the EU Rom as it will save you the extra work of going stock and rooting, etc. if your original challenge was just trying to get a good WiFi signal.
The previous times that I tried to install the .nbo files with SUT L3, I extracted them from the zip.
Also, I got firmwares on the UK site but I am Canadian. Most likely mine is also USA-based as many of our electronics are. I just could not find the files on the USA site.
I am running Windows 7 so some drivers installed automatically. I did use Setup.exe to install some other drivers but I have noticed no difference between the two times. Running setup.exe doesn't install anything anymore.
--
Here are the steps I took after your post:
I first transferred EUViewpad7v1.7b-ITE.zip to the microSD card and after rebooted into CWM-based Recovery. I wiped Dalvik cache, cache and "data/factory reset". I then flashed the .zip file and restarted the device after it finished loading.
I noticed the new intro logo so it seems switching the new ROM was a success.
I went into wireless and network settings and I turned on Wifi in the Wifi settings. The device scans for networks for about 30 seconds, then stops and displays "Unable to scan networks" and turns off.
I know for sure there are networks in the area and the wifi was working before I swapped to another ROM.
This is where I am currently stuck.
Again, thank you for your help.
clandor said:
... Most likely mine is also USA-based as many of our electronics are. I just could not find the files on the USA site. I am running Windows 7 so some drivers installed automatically. I did use Setup.exe to install some other drivers but I have noticed no difference between the two times. Running setup.exe doesn't install anything anymore.
--
Here are the steps I took after your post:
I first transferred EUViewpad7v1.7b-ITE.zip to the microSD card and after rebooted into CWM-based Recovery. I wiped Dalvik cache, cache and "data/factory reset". I then flashed the .zip file and restarted the device after it finished loading. I noticed the new intro logo so it seems switching the new ROM was a success.
I went into wireless and network settings and I turned on Wifi in the Wifi settings. The device scans for networks for about 30 seconds, then stops and displays "Unable to scan networks" and turns off. I know for sure there are networks in the area and the wifi was working before I swapped to another ROM. This is where I am currently stuck ...
Click to expand...
Click to collapse
Great, that's major progress - first, let's check & verify a few things and do it step-by-step:
Go to Settings - About phone - check that the following is same or similiar (they should be identical or almost)
Android 2.2.2
Baseband PR3.7_125
Kernel version Apps_2.6.32.9
Build number 4027_3_420
Check under Mobile network settings -
Data enabled (it should NOT matter, only if you are using a Sim card for voice and/or data in Canada)
Under WiFi settings -
WiFi - enabled, cycled it OFF and ON again, does it see various open and/or secured networks nearby
If NOT, press the soft "Menu" key on the lower right (in landscape mode) - it should open up & show "Scan" & "Advanced"
Can you do a manual "Scan" - make sure you have a known working WiFi, either secured or open (McDonalds/Starbuck or public library, etc.)
Next - open "Advanced"
Wi-Fi sleep policy (mine is set to "Never when plugged in" - try to temporary set it to "Never" for this purposes
MAC address - the unique ID for your device should be shown
Tap the WiFi network that you wanted to connect to - check its setting/status for Security, Signal strength, Link speed & IP address
If it previously connected but no longer worked, press "Forget" to delete it, and when it attempt to reconnect (if it is a secured one) - re-enter the password to see if you can connect.
For your restoration purposes, you might want to use WEP or WPA instead of WPA2, or even temporary changed your router to an "Open" WiFi so that any devices including the Vpad7 nearby can connect insecurely, assuming that your router is assigning DHCP automatically and giving out its IP address.
If NONE of these steps are working still, go back into WiFi settings and manually delete any and ALL saved stored networks (named) on the device, leaving just "Add Wi-Fi Network" as the only option.
Next, run a TB backup of your Apps if necessary and boot back into CWM, and do a Backup first to your mSD card (and cover it to a PC if necessary, as you can always restore it back instead of going thru flashing & Set-up) and you will have working boot.img (kernel) saved along with system, etc.
Exit and boot back to ADB (Android) Go to Settings - Privacy setting, and hit "Factory data reset" - next go first into CWM again, wipe dalvik cache & cache again, then continue with regular Setup including WiFi - your device should be able to pickup a nearby & strong WiFi signal.
If all these are still not working, you will likely need to get to a PC or laptop, earlier users had reported having issues with Win7 OS running, I would recommend borrowing/using one with Vista or XP-SP3 running, make sure the USB device drivers are automatically installed first and that it recognize the device. Then, reconnect and run SULT3 and flash the factory *.nb0 file - as I also suspect that there might be other hidden USB device drivers on your existing Win7 system that's casuing the *.nb0 installation to fail.
Keep me posted on your progress and any error messages or crashes (FC) encountered.
(Apparently, some of the custom Roms ended up "corrupting" the WiFi settings and codes, leaving residual settings that casued it to stop connecting to WiFi's - if you look & check some of the posting under "Development" (for some of the Rom's) - you will see some discussions about it. The EUv1.7 custom Rom (non-ITE was initially done and ITE later on) is among the better ones with few WiFi issues to speak of, 15+ months later, still relatively bug-free and updated all the Apps and add-ons of my own from Google Market (Play Store) automatically, with working Flash Player patched, and Angry Birds happily running along - the CPU is slow but with App2SD helping, not too bad for a device running Android 2.2.2 (Froyo)
I checked the settings in the About section and they are identical to the ones you posted.
I left Data enabled however I haven't inserted a SIM card throughout this whole process. I have no data plan anyways with the current SIM card I am going to put in.
Under the advanced settings in Wifi, I changed the sleep policy to Never and the MAC address says "Unavailable". So far there is still no result. I will try connecting in an area where I know there are open networks later today as I live in a public house where I have no access to the router's settings.
Also just a note about cycling Wifi ON and OFF, it automatically turns off after the message "Unable to scan for networks" shows up and no networks actually show up in the Wifi Networks section throughout the whole process. It stays empty even though there are networks around.
There are currently no stored wifi networks either so Add Wi-fi Network is the only option. I recieved this device from someone recently and I completely formatted the mSD card to start fresh so losing any sort of data is no problem to me.
---
I used the backup option in CWM to create another backup and after that I backed up the mSD card through USB to keep the working boot.img and other stuff onto the PC.
Under privacy settings I selected Factory Reset and let the device do its thing. I noticed the intro looked like normal however the Android's "theme" is still like the EUv1.7. I went into CWM and did a dalvik cache wipe along with a cache wipe and reset the device.
I tried the wifi again at this point and still no change.
I also tried SUT L3 with the .nbo and I yeild the same errors as before (0x4000 first time when using from Android screen, 0xC60E after the first time when using SUTL3 without leaving recovery mode).
--
I will test open wifi later today and I will edit the result. I'll also take a look at the discussion on wifi not working around the development forum. Thank you.
---
Edit:
I tested it out on some wifi networks without any protection and still none showed up.
I also noticed that if you right-click the Setup.exe icon in the taskbar after plugging in the Viewpad 7 it gives you the option to uninstall everything that the setup installed. I tried uninstalling and running SUT L3 but there was no difference. Also no difference after reinstalling, just so you know.
clandor said:
I started off by enabling USB debugging and plugging in the tablet.
I opened up SUTL3 v1.7.9 and selected one of the firmwares (both yield same result). The update option I set to Erase user data. Once I hit
Maybe some kind of driver problem?
Click to expand...
Click to collapse
I re-read some of the posts about flashing & restoring factory ROM, and it mentioned turning OFF USB debugging mode (from within the device's Settings - submenu) before -
If you want are ready to give up on this donated/given to you device, you might want to try this as a last resort - then, run SUTL3 with the *.nb0 file to restore it to factory stock condition - and hopefully, get the WiFi working.
From your last description of the error MSG - MAC address unavailable, the settings are definitely corrupted / damaged. Some of the Vpad7 owners had to RMA back to Viewsonic for repairs, obviously it is beyond the warranty and not worth the expense now with this "aging" Froyo OS.
The solution, as you probably read it by now, was to wipe clean & go back to stock, root it again and then try a different custom ROM ...
* * * * * * * * P.S. Please check your PM/in-box for a special message [/B] * * * * * * * *
KWBR V4.2 custom Rom, still available for download, will work with ITE hardware - http://forum.xda-developers.com/showthread.php?t=1386469
Since your CWM is still working, give it a try by flashing and perhaps it can get your WiFi working.
I ended up fixing the problem.
I downloaded PdaNet (PdaNetA350x64.exe) and installed it. I used it to get some drivers for the Viewpad 7 when plugging it in. After that, I replaced the custom recovery menu with an original recovery menu file. Once the recovery was back to normal, I tried running SUT L3 and using the v3_420 .nbo file. It worked fine that time and my device's software was back to default.
--
Afterward, I rooted it and put on a custom recovery menu again. This time I used EUViewpad7 v1.7b ITE version and it did not break my wifi. My original cell phone broke and this device will serve as a pretty good replacement for a little while.
Thanks again for your help, Letitride.
Before Christmas I tried to do a OTA update on my Prime, which has not been successful and I have not been able to use the Prime since.
It has previously been rooted and previously have always been successful in using Voodoo OTA Rootkeeper to retain root after updates. I've not unlocked the Prime.
Now when I try to boot it spends a while 'optimizing' the applications (as if it was the first time i've booted it since the update), and then once it is started, no apps will startup, all of them resulting in saying "unfortunately xyz has stopped"
A video of the problem: youtu.be/e1yfTtGiR78 (sorry can't post full link as am a new user).
I'd like to get it working again, possibly installing the Androwook ROM (or at the very least, just working on the stock rom). What steps do I need to do from where I am at the moment?
There are many threads about flashing roms, brick-fixing (some more up to date than others), but I'd just like a bit of advice about this problem and what I should do next (maybe some good links?). I haven’t gone near doing any flashing on the Prime, and it would be nice to seperate the things I could do, from the things I -should- do (I don't know where to start).
I believe as the Nvidida logo is on the bottom right this means I'm on the JB bootloader? Currently the settings menu shows I'm on android 4.1.1, but not sure if this is pre or post the failed update.
Thanks for any help,
Steve
A factory reset will fix you up. You'll lose your data
Hold vol down + power when booting to access the boatloader menu. Select wipe with vol down and use vol up to confirm.
Hi,
Thanks, I've done the reset, but I still seem to have the same problem.
imageshack.us/photo/my-images/502/imag0217c.jpg
I can't actually proceed throuh the inital set up, because it closes itself when it gets to the account setup page.
Any ideas?
I have resolved this.
I downloaded the latest firmware from the ASUS support website, extracted the zip file from within the downloaded zip file and renamed it to EP201_SDUPDATE.ZIP .
Put this on a microSD card (which I had formatted to FAT32), inserted it into the Prime, then booted into the bootloader menu.
Selected the RCK option, it did the update, and 10 minutes later it was up and running again.
From what I have read, it won't try to complete the update if it thinks you have already got that version installed already, but I guess it knew it hadn't successfully completed the update previously.
Glad it's working again.
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
This has worked for me few days ago!! All went too smooth!
Good Job Raider! This will be useful to so many people.
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
How do you go about doing this"Don't forget to uninstall package disabler then install the 6.3 version and disable the update package" where in the phone i much go to uninstall and disable update package
joseph- said:
How do you go about doing this"Don't forget to uninstall package disabler then install the 6.3 version and disable the update package" where in the phone i much go to uninstall and disable update package
Click to expand...
Click to collapse
In my case, my date wasn't deleted. I had "Package Disabler Pro" application installed (the latest update which didn't show the OTA packages).
I uninstalled it, then downloaded the 6.3 version (which shows the packages) and disabled the OTA files
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
Funny because i tried same thing and odin failed. It won't allow rolling bk to original rom.
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
WORKED FOR ME AS WELL!!! Green Battery is back! now lets see if it charges over 60%
I've downloaded Package Disabler Pro 6.3 on my Note 7 after sucessfully using Odin to go back one software update.
However, I've disabled all the following...
com.policydm
com.sec.android.soagent
com.samsung.android.omcagent
com.wssyncmldm
com.sec.spp.push
Except for the most important ones...
com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp
Because they don't come up.
Will this be an issue?
Can you not just root and install a custom rom?
marvi0 said:
Can you not just root and install a custom rom?
Click to expand...
Click to collapse
No root for the snapdragon
Maiesta_Miyabi said:
I've downloaded Package Disabler Pro 6.3 on my Note 7 after sucessfully using Odin to go back one software update.
However, I've disabled all the following...
com.policydm
com.sec.android.soagent
com.samsung.android.omcagent
com.wssyncmldm
com.sec.spp.push
Except for the most important ones...
com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp
Because they don't come up.
Will this be an issue?
Click to expand...
Click to collapse
Did you have a previous version installed?
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
So this is funny but i kinda fixes my phone lol now it charges up to 100. I tried koodo firmware and i was able to restore it. Originally i tried the general Samsung firmware for note 7 nd it kept on failing in odin then i realized wen i put my simcard in back wen first got the phone it looked to koodo. Now i used pkg disabler to disable updates too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No previous version installed.
Att version
Mine is SM-930A. It's the AT&T version. Please help.
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
worked thank you
I did the same thing as instructed and was able to downgrade my note 7 snap dragon to a previous stock version before the forced update. Battery is back to 100%, no update messages everything seems to be running great. However I noticed my Secure folder is no longer working. Has anyone else having this issue? When I try to open secure folder or setup the folder it gives me a error message saying " Secure folder cannot be set up because unauthorized software was installed on the device. I got the rom from Sam mobile for my Rogers phone Sept update. Sometimes the error messages says " Failed to create knox mode. Try again. When I use an app to check my if my knox has been tripped is says everything is normal, 0x0 valid warrenty. Any ideas what a solution could be?
By the way... Thanks for posting how to downgrade and get my note 7 back to normal working condition!
goldensun7 said:
I did the same thing as instructed and was able to downgrade my note 7 snap dragon to a previous stock version before the forced update. Battery is back to 100%, no update messages everything seems to be running great. However I noticed my Secure folder is no longer working. Has anyone else having this issue? When I try to open secure folder or setup the folder it gives me a error message saying " Secure folder cannot be set up because unauthorized software was installed on the device. I got the rom from Sam mobile for my Rogers phone Sept update. Sometimes the error messages says " Failed to create knox mode. Try again. When I use an app to check my if my knox has been tripped is says everything is normal, 0x0 valid warrenty. Any ideas what a solution could be?
By the way... Thanks for posting how to downgrade and get my note 7 back to normal working condition!
Click to expand...
Click to collapse
Ok looks like I fixed the problem. I only flashed the larger AP file and not all the files in the stock rom. Once I flashed the other files, secure folder became available.
Be sure to flash all files in the stock rom.
oh man I cant thank you enough for helping me bring some life back into my phone! the 60% was brutal! back to 100% charge now!!!
I did run into some issues, and in case this helps anyone else who couldnt get odin to pass the most important thing is to make sure your downloading the right carrier version of the firmware. You need to use the carrier version that matches the same one the phone was originally activated. In my case, my Bell note 7 was originally activated using a virgin mobile sim card so odin would fail until I used the VMC region instead of BMC.
Thanks again!
would someone be kind enough to post a youtube video for those of us who are not so familiar with using ODIN
Thank You.
Its great that some of you are able to fight back against the 60 percent update, i blocked mine before it even happened but nothing will help us when the carriers block our devices... i just got off the phone with sprint (US) and they told me they will definately block the note 7s in the near future long before the 8 comes out... if someone has a solution, please pm me or post it here if you can...
Personally my story about keeping the no seven is probably a lot different than most people...
In February my now ex wife stole my Note Edge and kicked me out of my own house at gunpoint.... thankfully i got away with my tab 4... but it got stolen when i was homeless from being kicked out and living in my car...
So two devices stolen from me in less than a year, but hope was on the horizon. I had heard the note seven was coming out and so I stayed without a phone for three to four months and got the note seven the day it was released.
The note 7 is my trophy, it is my monument to not ever getting robbed again and then samsung wants to take it.
rkawli said:
would someone be kind enough to post a youtube video for those of us who are not so familiar with using ODIN
Thank You.
Click to expand...
Click to collapse
check youtube there are a lot of instructional vids. the process is the same for every ROM. you can download the ROM from sammobile.com firmware section. let me know if you can't figure it out still. I can try and help.
trying to help a friend who's SM-T820 wifi started to fail. Switch it on, it spins for a while and switches off. (stupid me) I did a factory reset. Upon boot, it says someone tried to do a factory reset, please sign in to confirm. Well, can't sign in because wifi wont turn on....so on to ODIN and stock firmware tried T820XXU1AQF3 rom and in ODIN I get FAIL! (Auth). On the TAB it says:
CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, FRP lock is enable, OEM lock is enabled, ... SW REV CHECK FAIL : [boot] Fused 1 > Binary 0
Reboot, and I'm back to the please sign in to confirm reset. Can't go to settings to disable OEM lock. Where should I look next?
howudodat said:
trying to help a friend who's SM-T820 wifi started to fail. Switch it on, it spins for a while and switches off. (stupid me) I did a factory reset. Upon boot, it says someone tried to do a factory reset, please sign in to confirm. Well, can't sign in because wifi wont turn on....so on to ODIN and stock firmware tried T820XXU1AQF3 rom and in ODIN I get FAIL! (Auth). On the TAB it says:
CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, FRP lock is enable, OEM lock is enabled, ... SW REV CHECK FAIL : [boot] Fused 1 > Binary 0
Reboot, and I'm back to the please sign in to confirm reset. Can't go to settings to disable OEM lock. Where should I look next?
Click to expand...
Click to collapse
AQF3 firmware is an older firmware. If the device has been updated you need to use that or newer firmware. You can't flash an older firmware so that's probably the problem.
ok, I finally found the right rom to be able to flash, flashed the BL, AP and CSC images. Rebooted, and it went to: "an unauthorized attempt..." not a problem I know the username and password, but wifi still wont turn on. Ideas?
howudodat said:
ok, I finally found the right rom to be able to flash, flashed the BL, AP and CSC images. Rebooted, and it went to: "an unauthorized attempt..." not a problem I know the username and password, but wifi still wont turn on. Ideas?
Click to expand...
Click to collapse
First, boot into the stock recovery and clear the cache. If that doesn't work then try flashing just the AP in Odin.
wipe cache: same result - an unauthorized attempt...and wifi unable to turn on
ap flash only: same result
also almost every tutorial I see on bypassing FRP lock requires that wifi be working. wifi is not working for some reason.
ok, so maybe a combination ROM for T820XXU2BRJ1 will help, that is the stock that is installed. Anyone know where I can find that?
howudodat said:
ok, so maybe a combination ROM for T820XXU2BRJ1 will help, that is the stock that is installed. Anyone know where I can find that?
Click to expand...
Click to collapse
If you're looking for the stock firmware go to updato.com. It looks like the bootloader was unlocked at one time? Can you bypass the initial setup and get into settings? If so see if developer options is there. If not see if you can get to about tablet, software information. Then tap build number 7 times. That should initiate developer options. In there allow oem unlock. But, if you haven't gotten the firmware from updato get that first and flash it in Odin.
jd1639 said:
If you're looking for the stock firmware go to updato.com.
Click to expand...
Click to collapse
I'm not looking for stock. I tried installing the stock already
jd1639 said:
It looks like the bootloader was unlocked at one time?
Click to expand...
Click to collapse
Maybe, but I dont think so. My friend wouldn't know how to do that.
jd1639 said:
Can you bypass the initial setup and get into settings? If so see if developer options is there. If not see if you can get to about tablet, software information. Then tap build number 7 times. That should initiate developer options. In there allow oem unlock. But, if you haven't gotten the firmware from updato get that first and flash it in Odin.
Click to expand...
Click to collapse
I can't bypass the initial setup. The initial problem was that wifi wouldn't turn on, (spins for a few seconds then turns back off). I have tried visual assist, select a word, keyboard settings, but cant seem to make the jump to regular settings to be able to get to dev options. That's why I'm asking for a combination rom, I've heard that they have the engineering features I need to jump straight to settings.
of course if there is another solution I'm all ears
howudodat said:
I'm not looking for stock. I tried installing the stock already
Maybe, but I dont think so. My friend wouldn't know how to do that.
I can't bypass the initial setup. The initial problem was that wifi wouldn't turn on, (spins for a few seconds then turns back off). I have tried visual assist, select a word, keyboard settings, but cant seem to make the jump to regular settings to be able to get to dev options. That's why I'm asking for a combination rom, I've heard that they have the engineering features I need to jump straight to settings.
of course if there is another solution I'm all ears
Click to expand...
Click to collapse
I'm not familiar with combination roms but I found this, https://www.hardreset.info/devices/...-tab-s3/faq/faq/samsung-combination-firmware/. Maybe that helps? If you could get into developer options you could enable oem unlock and possibly flash a custom rom. I was going to suggest rorymc928's rom in the roms, kernels, etc section.
have you fixed it? it's easy all you need is to flash the combination firmware to remove the FRP lock (by resetting to factory settings from combination firmware) and reflash stock rom after that, no need to unlock bootloader to do all this.
blinkycan said:
have you fixed it? it's easy all you need is to flash the combination firmware to remove the FRP lock (by resetting to factory settings from combination firmware) and reflash stock rom after that, no need to unlock bootloader to do all this.
Click to expand...
Click to collapse
Do you know where you can get the combination firmware for the t820?
ok I was able to get past the FRP lock, finally. Now we're are back to the original problem. Turn wifi on, it spins for about 30 seconds and turns back off again.
jd1639 said:
Do you know where you can get the combination firmware for the t820?
Click to expand...
Click to collapse
i have used the T820XXU2ARI1 because T820XXU1AQB was not working for me (SW REV CHECK FAIL : [boot] Fused 1 > Binary 0) from www .getdroidtips. com/galaxy-tab-s3-combination-rom-files/ (i can't post links because new user)
howudodat said:
ok I was able to get past the FRP lock, finally. Now we're are back to the original problem. Turn wifi on, it spins for about 30 seconds and turns back off again.
Click to expand...
Click to collapse
How? I have the exact same tablet and problem, I did the reset too.
My completely stock Pixel 6 has been pretty smooth since the Jan update until I was using Google Maps today and my keyboard wouldn't open in any other app except tapping the search bar in Maps.
So I rebooted my phone.
Now, I'm permanently on a screen that says "Phone is starting...". I cannot enter my PIN. I can access notifications (but they don't populate). If open Settings from notifications, I can't tap anything otherwise it goes back to the "Phone is starting..." screen. I can't switch to the guest user. If I connect a USB and enable file transfer the device doesn't connect (I assume because I haven't signed into the phone). I don't have USB Debugging enabled.
I'm trying to get some photos and videos off the phone that I recorded today before they were uploaded to Google Photos.
Trying everything before factory resetting this piece of garbage.
Here's a video demonstrating things:
It's not bricked. Bricking means it can only be used as a brick, factory reset it will be the easiest thing you can do
Just factory reset it, or flash the ROM with the android flash tool
Android Flash Tool
flash.android.com
try this, make sure you unselect full wipe
After 247 posts, bricked needed defining?