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.
Related
My scenario:
I updated my N1 to 2.1-update1 by applying an update.zip from the SD card. Everything worked fine for a while until a few days later I turned off my phone. On rebooting, it got stuck at the splash screen. I managed to reboot through the bootloader and got back in but have since had problems with a couple of apps force closing on startup and have been unable to send SMS. I decided that maybe I should start from scratch so rebooted into recovery mode again and wiped data and cache and reapplied the update. My phone will now not boot at all. It consistently gets stuck at the splash screen.
It's not bricked, as I can get to the bootloader and recovery menus but:
a) adb and fastboot won't recognize the phone as being connected
b) on the recovery menu I see "E: Can't open /cache/recovery/command"
c) when going in to the bootloader it complains about not finding PASSDIAG.ZIP
Anyone have any ideas what I can do? I can't connect via adb/fastboot so am not really sure what I can try...
Did you do a nandroid if so I would try to restore and start the update from that point.
I get an error when I go to my bootloader screen asking about passdiag.zip and passdiag.nbh but it hasn't ever caused any problems, it just complains about them. I don't get the issues with the recovery menu or USB though. Fairly sure that doesn't help you, just adding my experience in the off chance it helps someone diagnose.
I don't suppose anyone has any idea what passdiag is?
No one with any idea what passdiag is or what one might do to fix this issue?
Don't worry about passdiag.zip and passdiag.nbh. These files are the ROM dumps if i remember right from Google. Just let that pass. Is your phone unlocked running a RA recovery, or are you still at stock. If unlocked you will have to reflash whatever ROM it was you were using.
So here's how I got to having that error.
Originally I was using the stock ROM. No error.
Then I unlocked/rooted using the guide here. Error started appearing.
After that I flashed Amon-Ra's Recovery: Error still present.
Following that I flashed Cyanogen's Mod. Error still present.
I really would like to get rid of the error, even if it isn't hurting anything. I don't suppose there's a place I could get the files to push to my phone or somewhere in the phone I could tell it to stop looking for them?
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.
So, I am new to the community and just recently created an account to make a new topic because something happened:
I have a N6P and I was disappointed with the whole "Pixel exclusives" thing, so I decided to root and flash some of the new features into the phone. Everything I wanted I could find in the threads of this forum and it was nice and easy. I did get to a nice point where I had all the features I wanted, and then, I saw that there was a beta update for the new android version 7.1.1. From there I realized how little I know about the android system, and for that reason I want to ask a few questions. First, I'll describe the steps I took and the result i got:
1 - Backed Up data with TWRP (Boot, System, System Image, Vendor, Recovery)
2 - Updated to 7.1.1 through the phone settings
3 - Reboot
4 - Checked everything (all working fine until here), I had lost my root and TWRP because the new system took place.
5 - Reflashed TWRP
6 - Patched again the Pixel Launcher and SuperSu through TWRP
7 - Reboot
From that time on, the phone did boot, but the default launcher didn't start and a system app presented errors: Everythime I closed the error box, if popped again, blocking me from doing anything.
After the inicial problem, I promptly went to TWRP and tried to restore the backup I made. Now the phone became unable to start the OS, it runs the boot animation forever and nothing happens.
Now I am downloading a Stock ROM to flash through fastboot and do everything again.
Now to the questions:
1 - What did I do wrong? Why didn't the Backup work? What should I do differently from now on to have a reliable restore point of my device(just in case I screw up again)
2 - What can I do (besides flashing stock room) in order to recover my system? It is annoying to have to start from zero again thinking i had a backup made just to prevent that.
3 - Where can I learn more about the Android filesystem and OS architecture? (I am a developer, but I'm also lazy as ****, so i'd appreciate "explain like i'm 5" links)
Thank you all.
Yes this post is correctly dated. I've had this device a LOOOONNNGGG time.
The device has been rooted since shortly after I bought it new years ago. I've had very few problems since... which is why it's never been replaced.
I believe I have the stock ROM, sorry it's been a while.
When I start the device it gets stuck at the splash screen with the sprint logo.
I can get the device to "download mode" but I don't know what to do once there and I'm not sure I can do anything from here.
I can get the device to "android system recovery."
I know I installed TWRP when I rooted and installed the rooted ROM but when I boot to recovery it doesn't go there.
I've wiped the "cache partition" but the problem remained. I'm not sure what else to do from here and still be able to salvage data.
I'm trying to salvage the data on the internal storage. I'm pretty sure I could successfully "wipe data/ factory reset" and get it to "function" again but that's not the priority. I'm going to replace it regardless of success or failure. Data recovery is the priority here. (pictures and videos of my young children as well as less important stuff like contacts.)
I have an old laptop with an old version of ubuntu I can use or a newer one with windows 7 to work with. I mention this in case it makes this easier to help?
Thank you very much if you try to take a stab at this or refer someone that might!
Update:
So I managed to install TWRP via Odin.
I booted to this recovery and my data partition appears to be empty?
When I try to back up I get the error message "unable to mount '/data'"
I tried doing a wipe, not one of the fancy extra options ones just the regular wipe and it failed.
Any guidance will be extremely appreciated.
Edit:
So I've come to the conclusion that the data isn't accessible because of encryption and my pass code. Is there any way to enter it via recovery and access this info?
Is anybody out there?
Edit 2:
I hope this helps someone someday. I haven't solved the problem but I think I'm making progress.
First I had an old version of TWRP. I installed the latest for my device and tried backing up again. I'm not sure but I think it's working. TWRP dosen't seem to need my password for the backup. I imagine I'll just need it to access the data later.
Edit 3:
No sooner did I save the last edit and my backup failed.
Process ended with error : 255
Sorry in advance for my English. As the name makes clear, my SMT280 doesn't turn on. The thing is, after I reflashed it and installed TWRP, I needed to do a full data reset. I went to TWRP, and apparently accidentally put a check mark on the system item. After that, the system stopped loading and the tablet freezes on the logo screen. Also, the PC stopped recognizing it, so I can't flash it through Odin. In an attempt to fix something, I took boot.img, and recovery.img from stock firmware and installed them via TWRP. Now, of course, I lost TWRP, and with IT the last hope, because now I only have a default recovery, and all the above problems remain. As I said, I don't think the tablet is still recoverable, but still, if anyone knows of any way, I would be extremely grateful. Thanks.