One day, I got tired of the lame and boring Kindle interface, so I decided to use CyanogenMod to fix that problem. The Kindle Model I had was the 2012 HD Kindle "Soho" model, the one they had a warning on not to mod. So I previously rooted my tablet, and after unknowingly installing the wrong TWRP version, I got Recovery Reboot from the Google Play .apk I got. The first time I used the app, it gave me a red triangle saying I should reset to factory default or reboot. Each time I rebooted got the same triangle, but factory resetting fixed that problem. I logged my Amazon account back in and got all my apps back, then re-rooted and got the Google Play .apk from before. I saw the warning about the Soho models after going back to the CyanogenMod wiki to see what I did wrong, and I gave up and stayed with the boring interface. BUT, my Kindle ran out of battery, and it automatically shut down, and when I charged it, it rebooted into the familiar red triangle. I rebooted again a couple times, didn't work, factory reset didn't work either, and leaving it on for a few hours to completely drain the battery didn't work. I think the TWRP files were still hidden in the system files after I reset it the first time, and rebooting with charging the tablet activated the reboot into recovery, which triggered the TWRP files into action, but it was the wrong version, leading to this brick. How do you fix this? Do I need a fast boot cable?
Related
Hi guys, my phone is right borked and I hope someone can help me out. I've been searching forums all day and I find bits and pieces of advice that apply to parts of my situation, but haven’t found a fix yet.
I installed CyanogenMod on my Rogers Samsung G3 a couple months back. Everything has been going smoothly until last night when I installed an update.
The phone rebooted and got stuck on the Samsung splash screen with the blue cyanogen dude. I left it for 30 min and when I got back, it was still the same.
I took the battery out, turned it back on and ended up in the same spot. I took the battery out again, turned it on and left it over night. Same thing this morning.
On advice from this forum I put the phone in recovery mode. I thought I had TWRP, but Clockwork Recovery comes up.
I did a factory reset, and cleared the cache. Rebooted and still the same thing.
I tried to flash the ROM, but it doesn't work. The android dude just lies there, dead. Poor guy.
I plugged it into my computer but even though the computer makes the connection ‘cah-ching’ its not recognized. Through the recovery screen I tried unmounting and mounting everything, and mounting as usb and the computer still won’t pick it up. I uninstalled Kies, and the drivers for the phone and re installed everything. The driver pop up says MTP has failed.
Any suggestions?
Alright, so yesterday I tried to root my tablet (Samsung Galaxy Tab 3 10.1 Wifi) yesterday by installing TWRP and then loading the Superuser zip found in their link in the play store. It worked fine--I had root access and all was going fairly well. I then tried to make a small tweak to the build.prop file by changing ro.build.version.codename from REL to L.
When I rebooted to apply that change, I could not start up, so I did a factory reset (not a big deal, no essential files on there). It then booted fine, but when I reinstalled/updated all my apps, the Google services were crashing like mad. So I reverted the build.prop file back to REL and again it would reboot, so I did another factory reset and all was good; the Google apps were fine.
Well I was still rooted and I wanted to take advantage of all that time I spent doing it, so I downloaded the bootanimation zip found on this thread and replaced my bootanimation.zip that was already on there. I restarted to see the animation, and this is when the real nightmare started happening. I could not boot now at all.
I did another factory reset, and still it wouldn't boot. I then used TWRP to do a full reset, and still nothing. I did an advanced reset and somehow managed to delete the operating system files (I have no idea how), causing TWRP to say that no operating system was installed. I still couldn't boot, of course.
Finally, I decided I had had enough of this rooting ****. I searched all over the internet looking for a North American version of my stock ROM, and finally found one posted on this forum post. I wouldn't normally trust any random file, but I was getting desperate here. I used Odin to flash that ROM, and there were no errors. Now when I go into recovery, it gives me stock and not TWRP, so I know that was probably successful.
However, I still cannot boot. I get stuck on the screen that says Samsung Galaxy Tab 3, which sometimes goes away and then comes back. I can't send it in for warranty, because it still says "custom" in the recovery mode. How can I fix this? any ideas?
I really want my tablet back :crying:
Battery was getting tired, so I ordered a replacement -- and installed it yesterday afternoon..
The phone worked normally -- until this morning.
I noticed a notification from my text app that it couldn't connect and that I should check my settings.
I went to settings and began by refreshing the PRL. During that process the phone froze and then went dead.
Totally dead.
So, I opened it up again to check the battery terminal connection -- and I believe it WAS loose -- so I reconnected it and checked it. Phone goes on!
But it only goes to the splash screen and then repeats. No boot animation.
It will go to the bootloader, but not boot the system nor recovery from there.
Using the fastboot commands, I re-flashed bootloader, radio, boot, system, (From 5.1 stock image) TWRP recovery and erased the cache.
Still stuck at the Google splash screen.
Anyone care to point me in a better direction?
Must be expiration time for Nexus 5 batteries from the initial run. I had to replace mine today as well. Try reflashing the cache and not erasing it after. I made that mistake a month or so ago and kept bootlooping.
Later edit5: Tried to restore my nandroid backup and TWRP froze. Had to hard reboot the phone...
Later edit4: It started working. It f***** started working. Out of nowere. Last night, the last thing i tried was this: https://forums.oneplus.net/threads/fix-for-sudden-death-and-boot-loop.146107/
I rebooted the phone and it didn't work. I gave up.
This morning I turned it back on and ... surprise, surprise... it started working (optimizing apps and actually booting into cos12.1).
My happiness didn't last because as soon as the phone started updating some apps, it crashed, and entered a boot loop again. Good thing i managed to copy one of my previous backups.
Can someone explain this behavior?
Later edit3: my phone is still stuck in a bootloop. Neither roms are working.
Things I've tried:
- flash new roms
- erase/ flash persist
- flash color os
Nothing works!
Later edit2: while on cm13, i plugged it in to recharge. While connected to wall plug it did nothing(working fine, as it should be). As soon as i unplugged it started rebooting over and over again... a boot loop. This phone is starting to look like one of the biggest mistakes i ever made. I regret purchasing it.
Later edit: now it just turned off, and pressing the power button won't turn it back on. Had to press it for about 10 - 15 seconds. ANNOYING!
OP: I've been experiencing random reboots on my oneplus ONE since I've had it.
When i first got the phone, i was so excited about it and started flashing custom roms, just for fun and to see which one suites me. I messed up the phone (my camera wouldn't work anymore. All the roms gave me the same message"Camera has stopped working" ) and sent it back to warranty, here in my country, at the shop from which i've bought it. After two weeks they sent it back to me with the note "restored to factory settings". I've checked the "About" section and it was running cos12.1, 1 jan 2016 security patch, kernel 3.4.67.
So I've decided to stick with this rom because I didn't want to mess it up again. But, out of nowhere it rebooted. First i thought that it was an app that needed the phone to reboot. I didn't mind it. I've left my phone over the night and in the morning it was saying "enter pin" as it has rebooted.
Long story short, ever since it reboots at least 1 time a day, and it is getting really frustrating! Sometimes when i'm in an app, sometimes when it just lays around.
Reasons it rebooted:
- no reason, just siting and it rebooted
- opened waze app
- browsing chrome
- tried to connect to a saved wireless network, it rebooted and afterwards the network was not recognized anymore and had to retype the password
- no reason!!! just sitting!!
- fresh install of cos 12.1, i queued about 20 apps to install... it rebooted and continued installing after reboot.
- sometimes i heavily use it and it runs perfectly, but when i stop using the phone and lay it down it reboots. (this only happend one time)
Things I've tried:
- factory reset
- clear cache and dalvik cache
- power cicle the phone
- new rom
None of these worked.
Today I installed sultans CM13, with his 3.4.0 - sultan - caf kernel, hoping that my problems would disappear. (I installed TWRP 2.8.7.0.5, flashed the rom, cleared the cache, flashed the gapps, cleared the cache and reboot.)
It ran flawlessly. I've installed all my apps, played a little with it, configured it as I pleased and I've left it the table for about 15 minutes. When i picked it up, it rebooted(AGAIN!) out of nowhere.
What could it be? As I read through the forums i found out that a log with the exact problem is impossible to get because it gets deleted.
Could it be the wireless network? Could it be the sim card I am using or the phone modem? Could it be because of the launcher?
(for now, i've disabled my sim pin so when my phone reboots i don't miss phone calls if i don't notice it has rebooted)
Please help, as this problem is getting more and more frustrating...
Reboot log
Quickly after a reboot i reconnected the phone, opened cmd and typed adb logcat.
This is the log. 22:17 is the time when the phone rebooted so i extracted only that fragment of the log.
I am going to flash the stock cm13 nightly with the "stock" version of gapps. (until now i always flashed "nano").
I have the US 32gb unlocked version. Tried to do the downgrade to install CM using the method mentioned several times that changes the version from a command put in twrp.
First I unlocked bootloader, then installed twrp, then did the command line thing to lower the fw version, then put the v1.12 firmware on zip then rebooted to install.
Well, the install failed so I decided to stop there and try to put everything back to stock by using the latest ruu exe from HTC. The exe started sending a file to phone, then locked up and threw an error. I restarted the exe and it finally passed. I got everything set up and went to bed while it was updating apps.
This morning, shut off phone to put in SD, and when turning on it was optimizing apps then when done, would reboot and optimize again. The phone was stuck in this loop until I let the battery die. I couldn't do anything with it.
Battery finally died and tried to run the ruu exe again. This time it would not pass at all, no matter how many tries. I wanted to try to run the zip from SD but the latest firmware I can only find as exe.
Finally decided to just do a factory reset from recovery mode. This let the phone boot normally and I could do set up again. I tried doing a soft reboot, and it booted fine. Then I disabled apps I don't use, and did a full power down, now the phone is back to doing the 'optimizing apps' bootloop.
Right now I'm waiting for it to run its battery down again so I can at least get to download mode/recovery. Maybe I will try a full power off and app disabling separately, to see which is causing the loop.
Anyone have an idea what's going on? A link to the latest ruu in zip form? I really need a sure fire way to get this thing full clean stock (remember the exe is failing for me) to eliminate if thats the cause. Is it because I edited the version number?
Edit: just realized I put this in the wrong section
Update: Once battery died, I did factory reset again from recovery. Went through setup, and I then immediately shut the phone completely off and turned back on. It booted up fine. I then went to disable the same apps as before, EXCEPT for the "Google App". Phone still powers up fine, so I left it there and phone is working fine. I didn't want to see if disabling the Google App was causing the phone to boot loop. I had that app disabled the entire time I've had the phone, but don't think I've ever completely shut the phone down, so maybe that's why I never had the problem.
Still don't know why the ruu exe didn't work. Hopefully it was the computer, and I can still take updates.
I have the same problem, can't disable apps without phone going into bootloop on restart. Can you tell me what apps did you disable? Facebook, Instagram, Google docs, HTC apps etc,etc...
hmedved said:
I have the same problem, can't disable apps without phone going into bootloop on restart. Can you tell me what apps did you disable? Facebook, Instagram, Google docs, HTC apps etc,etc...
Click to expand...
Click to collapse
I think what caused my problem was disabling the app called "Google App". No problem disabling all the Facebook and Instagram apps.
What about Google docs, slides and news apps? Can those be disabled?
Same problem with my A9 bought a week ago. Like Rouyal, I recall disabling the Google App and then came the OTA update and the bootloop. Tried alll permutations of buttons and even when I could get to RECOVERY MODE, all the options looped as well, returning to the same screen: no bootloader, no recovery. The only alternative screen was the "Enter your code to decrypt your drive" after leaving RECOVERY MODE. It looped as well. Copied the stock RUU to an external SD card; did nothing (with HTC Sync).
SOLUTION: Enter wrong codes for the "decrypt your drive" screen 30 times; that is the limit before the drive gets a factory reset. After the 30th it was factory reset. On restarting, the systems asks for the SAME email that was used previously.