Hi,
maybe you can help me.
I have a working nook, but I'm stuck with the 1.0.0 firmware. I can't update it or restore it, each time the flashing procedure fails.
Here's a summary of the situation and what I already tried :
- When I got my nook, I made a backup that seemed to be OK (the size was good) before rooting it.
- Problem, it didn't update automatically, so I downloaded the update form B&N site to update it manually. But it didn't work, it reached the flash screen, but the update failed (I found a log file somewhere on the nook, it seems to be a signature problem)
- I restored from my backup, but same thing, the update fails.
- I deregistered, and tried again, no change.
- I tried to trigger the factory restore (via 8 failed boots and via ros87 image) but idem, the restoration fails.
- I even tried to use clockworkmod to flash either the update (not possible) or the restoration zip found somewhere on the nook (I got stuck on a boot loop after that, had to restore my backup).
I'm starting to think that my initial backup was not as OK as I thought (in fact, I can't remember if I correctly unmounted the nook before the backup...).
If I knew someone with another nook, I could try to make a backup from theirs to try (replacing the unique files by mine) but unfortunately it's not the case.
Do you have any new idea I haven't tried yet ?
Thanks.
Tbh, unless you feel you did something bad to your NST that prevents it from updating, you should contact B&N customer support about this.
Well, except for the root, I haven't done anything bad.
Not being in the US, I hoped for another solution, but if you think it's the best thing to do, I'll do it.
Thanks
If it's saying something about a signature, it might be possible the download became corrupted partially?
That would be too simple, that's the first thing I thought about it and tried re-downoading it several times, be it 1.0.1 or 1.1.
Well, if the Factory Restore fails as well, then this is not about signatures as there are no such thing involved in the Restore process, and beside a signature check on the update file itself I highly doubt there are any signature checks involved for the update process as well.
Like I said, I'd start with B&N Customer Support and eventually come back here if they're unable to help.
Related
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA
Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?
Me too. Update failed to install. Not sure why. I have also tried unrooting.
FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?
ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.
I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.
gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?
OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are
the log is \cache\recovery\last-log
Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time
I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **
I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!
SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.
No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger
Acer Recovery?
Did Acer Recovery come with the tablet?
I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.
Hello all together,
I've got a huge problem: My tablet is stuck in a boot loop, it shows the boot animation and the Nvidia tegra logo alternating and does not go beyond it.
And that's what happened:
- I couldn't install OTA2.5 since I deleted some system apps and couldn't restore them with titanium
- so I changed the update-script within the update.zip , so that some patches were neither checked nor applied
- I forgot to delete the commands concerning the install-recovery (that was the mistake)
- so after applying the update via CWR, it started booting, but got stuck.
- I thought I could restore an image with CWR, but during boot, the old android recovery was restored
- I already tried a cache wipe / factory reset, but neither does help to get out of the boot loop
Does anybody have an idea what to do?
here are my ideas:
- write a new update-script to get CWR back (probably won't work since the recovery checks the zip-signature)
- find a way to restore the original lenovo ROM (is there a signed version which I could use?)
- send it to lenovo (do I have any chance that they flash the original rom?)
I'd be really happy if anybody has an idea what to do.
Thanks, lump
I think it could be send to Lenovo.
Just said that you got problem during OTA 2.5 (not enough battery or something else) and you got bootloop.
The problem is in deleting some neccessery apps. Download OTA again from Lenovo server manually and install it with original ie. installed recovery.
Thank you for your advice, I think I will try to send it back to Lenovo.
I already tried installing the OTA2.5 update manually, but it aborts during the assert tests, since some apps are missing.
Does anybody know, if the ICS update will be incremental as the OTA updates before? If not, it might be possible to install it.
You could send a pm to bsnf, Mark_Lenovo, or someotherguy at the Lenovo forums and ask if they would please send you the full system image for your tablet. They might be willing to help, that is your best shot without sending it back.
Hello,
I have a MB525 that I purchased retail in the United States so it was never locked to any carrier. Currently I'm a T-Mobile customer and have no interest in changing that. I have to say I love this phone, mainly because it seems indestructible. Even years later the battery life is still good, but the stock 2.2.2 Froyo has become something of a problem because many of the Apps I would like to use have started requiring newer versions of Android.
I can't stay in the past forever, but I'm not quite ready to give up on this device so I started looking around at my options, and would you believe I found lots of other people who have this device and have worked very hard to produce updated Android OSes for it, and who have reported reasonably good success updating the device. I figured, Its already out of warranty, so I can't void a warranty I don't have. I also figured I'm a reasonably intelligent individual and have enough experience with Unix like operating systems that even if I get in trouble, I'll be able to ask the right questions to get out of trouble. Guess what point I have gotten to?
I started following the guide wikiDOTcyanogenmodDOTorg/w/Install_CM_for_jordan The Framaroot Gimli exploit worked great. I installed bootmenu 6.1 and Clockwork Mod Recovery. Fantastic. At this point, I was able to enter CMR and backup my mostly still factory ROM. If I understand correctly this is a nandroid backup. I copied that backup off of my SD Card to my PC. From this point I felt reasonably confident I could try things and in a worst case scenario restore to this backup.
Now I happen to have a stock ROM that seems to be a bit rare online, Blur_Version.34.4.806.MB525.Latam.en.01, so I figured at this point I'd do a service and create a backup using CWM after having done a factory reset. So I booted into the stock recovery, did a factory reset, restarted, and the OS was in a like new state. Perfect. Rebooted into CWM, and made a second backup of the factory reset state. I copied this off the SD Card to the PC. Now I figured I was ready for real fun.
I figured, I might as well put the most recent Android version I could find that people were reporting success with. This appeared to be @quarkx Kitkat build. The thread is almost a year old and has 500+ replies and so I guessed that most of the major kinks would have been worked out by now. I followed the directions on quarx2kDOTru and installed cm-11-20141015-NIGHTLY-mb52x.zip from Quarx2k.ru, and low and behold it worked. CM11 booted and everything looked great. WiFi worked. Gapps worked. Play store started installing my apps.
There was one small problem. The phone refused to connect to T-Mobile at all. So I did the reasonable thing. I searched and learned about base band switching, and consulted T-Mobile on what would be the correct APN settings. Occasionally it would connect to AT&T for emergency calling, but it never connected to T-Mobile no matter what I did. From my home I was normally getting excellent signal on the stock ROM, so I am reasonably certain that the actual signal in the area was not the problem, and that this had to be some kind of configuration or software issue. A wiser person probably would have gotten on the forum and asked for help, but wisdom be damned, I wanted to do it for myself.
So more research and at some point I thought, Well, I'll go back to the Stock ROM so the phone will be usable again, and I'll take another crack at CM11 again later. It was at this point that I realized that CMR had been replaced with Team Win Recovery Project. This recovery looked to be more feature rich and easier to use, so I accepted that. I backed up my CM11 install. then went to restore my original backup. Well you might have guessed by now that TWRP and CMR don't use exactly the same backup formats. I saw no obvious way to get back to my backup and couldn't find information that would allow reinstalling CMR. This was the first warning signal I foolishly ignored.
At this point I started looking around for slightly earlier builds of CM11 that might not have had the the problem connecting to T-Mobile. Here is where things get fuzzy about how things got into this state, since the work was spread over two days at this point. Somehow between all the flashing backing up and restoring, the device got to a state where the OS never actually finished could do here is yank the battery and reboot into TFRP.
At this point, attempting to restore would just result in the messages 'E: Unable to mount '/cache' and 'E: Unable to mount '/data' in the terminal. So After searching around I learned that I probably needed to format /cache and /data because somehow they were broken. Terminal commands, I can handle this. I start reading up and find the correct command and parameters for the format, and I type into the terminal inside TWRP and low any behold format can't be found. I start looking around the directories in my file system from inside TWRP and I've got a complete directoty structure, but no files in any directories other than on /sdcard. Well fuuuu.
Not sure what made me even try, but copying any file from my sdcard into /data somehow put /data into a state where a TWRP restore would work. So at this point I was able to restore the CM11 backup, and my phone now boots into CM11, 11-20141007-NIGHTLY-mb526. But.... the cellular network still doesn't work.
But now I am wiser and I am back to the point where a wiser person would have asked for help. So... Help?
Is 11-20141007-Nightly-mb526 the best rom an appropriate rom for my device? I'm guessing I missed something because other discussions on this forum mention newer builds, and also, my device is definitely a 525 not a 526.
Is my baseband version EPU93_U_00.60.03 right? The baseband selector allows me to pick from three T-Mobile settings: 3.4.2.-107-4, 3.4.2.-107-9, and 6.xx.0, none of which seems to allow me to connect to the cell network.
Thanks in advance for any assistance offered.
Sorry for the long potato.
Here is what I did to fix my problem.
I started with the original backup of my stock rom, and I used the unyaffs.exe from this thread: http://forum.xda-developers.com/showthread.php?t=1199416 to convert my CMR backup into individual files. I then went into those files, and found \system\etc\motorola\bp_nvm_default\ and pulled out the original radio firmware from my device. From there I used advice from several pages to create my own update.zip, copied it to my SD card and I booted into TWRP and installed the zip there. Reboot and Voila, It connected right at startup to T-Mobile with the normal speeds I get from my home.
Bonus, I attached my zip in case anyone else comes across this and needs it.
My Device has an FCC ID of IHDP56LC1 if that helps anyone match their hardware.
Hey !
I have a nook simple touch for a long time. It was modified software and worked very well.
Recently, when I tried to charge him after a long break, he warmed up a lot. I opened the case and unplug the battery.
When he cooled down I connected everything again and there was a problem: Installing rom ---> Install Failed
How can I restore the original software?
All my attempts end with "Install Failed!"
He probably tries to restore the software but the recovery partition can be empty. All modifications were made a long time ago and I do not remember the details
panzerkampf said:
Hey !
I have a nook simple touch for a long time. It was modified software and worked very well.
Recently, when I tried to charge him after a long break, he warmed up a lot. I opened the case and unplug the battery.
When he cooled down I connected everything again and there was a problem: Installing rom ---> Install Failed
How can I restore the original software?
All my attempts end with "Install Failed!"
He probably tries to restore the software but the recovery partition can be empty. All modifications were made a long time ago and I do not remember the details
Click to expand...
Click to collapse
Mmm.....that warming up thing does not sound good. But if you want to try to bring the thing back to life, the simplest thing to try first would be to make a NookManager card and try the Factory Restore option. If your NST will boot from the card, then you may have good luck with that.
If that does not work, it might be possible to re-image your NST with the original US software. You can find the details and files for that here: https://sites.google.com/site/xcdguides/nook/nookregion
I've tried both of your tips.
Unfortunately, I still "instll failed". NookManager factory reset happens without effect. After restarting, continue the same
However, the second tip gives me an error in many languages.
zapodaj. net/c6c797ba91d21.jpg .html
zapodaj. net/6a9912dfbce9d.jpg .html <--- I can't post pic directly
zapodaj .net/7b038e1ff25ef.jpg .html
I have the impression that the error appears regardless of the actions taken: /
@panzerkampf PM
*If this gonna work I gonna translate it and post here
Hello,
I've done quite a bit of reading here before posting this. I found bits and pieces of information that I tried to put together, but the outcome is not what I want, so maybe someone here knowledgeable could help me.
Device = Moto G5+
I've unlocked the bootloader, loaded twrp over the recovery partition, rooted the phone, performed a twrp backup prior to installing a custom rom. Then I tried another rom and another. They all have bugs or things to correct, so I decided to go back on my original load by recovering the «start» partiton from my twrp backup. That went well enough. However, since I restored the backup, I get errors and applications (like Settings !) crashing. There is obviously some sand in the gears somewhere. I then tried to reload the phone with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip using Minimal ADB & Fastboot, but that fails. The first 2-3 steps work, then up on the 4th or 5th, I get an error message stating that flashing is unallowed (these are not the exact words, but close enough. I can provide exact words upon demand). From what I read, it seems like I cannot use the NPNS25.137-93-4 load on my phone because my phone shows version NPNS25.137-93-8 which is newer than NPNS25.137-93-4. From there, I am lost. Must I wait until I can get POTTER_RETAIL_7.0_NPNS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip or is there a way around that.
My ultimate goal is to reload my phone with a 100 % working software, relock the bootloader and wait for slow Moto to release Oreo over OTA.
Note : My twrp backup is version NPNS25.137-93-4, but an update came in right after I restored from the backup, but upon instaling, the update concluded with a failure status.