Database Develop

[Q] Bootloop hell

I apologize in advance if this same issue has been replied to elsewhere. I'm in kind of a unique situation and couldn't find an answer anywhere.
I'm got an N1 with 2.3.6 stock ROM, rooted. Recently I downloaded Titanium Backup PRO and while attempting to integrate dalvik cache to ROM, my phone rebooted into a bootloop. I'm assuming this is a bootloop. I get the colorful splash screen, it freezes for a second of two, then continues on, and on, and on....
Is there a way to get me out of this loopwithout having to wipe all my data, so I can backup all my stuff before I flash a custom ROM?
Everything I see about bootloops, mentions unlocking the bootloader and wiping all your data. I've seen downgrading using PASSIMG and loading stock rom. I'd really just like a simple way to get out of this loop hell and get my phone back up. It's in teh ship now getting it's power button fixed.
Thanks in advance

first thing i do on bootloops is pull battery
if no go pull battery and then pwr on by pressing pwr and trackball at same time--you can then get to recovery and maybe wipe dalvik and cache and reboot
i have never used TB for anything other than backup/restores, so can't help with dalvik integration

You might be able to fix it by wiping your cache from recovery.
Sent from my Nexus One using xda premium

Thanks for the advice! I'll give it a try as soon as I get my phone back from being fixed.

Hey guys, I hope you can help. I got my phone back with new power button, Yay! When I try to boot into recovery, teh Nexus X logo comes on for a moment and then I get a white triangle with an orange exclamation point. Do I need to use ADB to try and go to recovery and wipe my cache? I've never installed a recovery image. Do I need to do that or should there be a stock image already on my phone? Am I SOL?

One more thing that might help. I notice that when I go into HBOOT, the phone searching for 4 images from my SD card and can't find them. They go by too fast to write them all down but I think some are PASSIMG, PASSDIAG, etc. Again, do I need to load a recovery like clockworkmod on my phone first and then go into recovery to attempt to wipe my cache?

I get the same passimg all the time--no problem
If your phone came back from repair, you are probably unrooted and hence the triangle. At least that is the way I remember it, but has been two years since I rooted
If that is comfirmed by someone else, you wil need to reroot and install a recovery
A good time, if you haven't, to install android sdk and root/install recovery the right way and have full adb/fastboot features
there other ways I am not familiar with
does the lock show unlocked on the screen, they could have relocked bootloader
the wiki has the instructions, just have to navigate to the htc smartphones and N1

jus to make sure that if u still got root. install su checker app from play store and confirm.
if not root using SUPER ONE CLICK ROOT.
flash recovery (4EXT is good) www.4ext.net
do a backup and then flash the rom u want
Sent from my Nexus One using Tapatalk

Thanks I'll check. I only had teh power button fixed and not by HTC so I doubt they unrooted it. I'm still in a bootloop but I can use superoneclick still, so I'll give that a try.

so what I'm trying to do is wipe my cache without wiping my data. I don't think my bootloader is unlocked. Am I screwed?I'm in a bootloop, so I can 't install anything to the phone. I probably could put a recovery image on the SD card, but if my bootloader is locked, I'm guessing that won't work. I'm rooted. When I go to HBOOT, the phone looks for passim files and doesn't find them, then when I choose recovery I get the white triangle. I've try to flash a recovery image through ADB but I get an error, failed to load image. Again, is that a bootloader issue?
I'm almost at the point of just wiping my data and hoping I can get it all back somehow.

holtonhj said:
so what I'm trying to do is wipe my cache without wiping my data. I don't think my bootloader is unlocked. Am I screwed?I'm in a bootloop, so I can 't install anything to the phone. I probably could put a recovery image on the SD card, but if my bootloader is locked, I'm guessing that won't work. I'm rooted. When I go to HBOOT, the phone looks for passim files and doesn't find them, then when I choose recovery I get the white triangle. I've try to flash a recovery image through ADB but I get an error, failed to load image. Again, is that a bootloader issue?
I'm almost at the point of just wiping my data and hoping I can get it all back somehow.
Click to expand...
Click to collapse
You really know nothing huh. The triangle is the recovery. Press power button and volume up at the same time, it will the show you some options like wipe cache.

n1newbie said:
jus to make sure that if u still got root. install su checker app from play store and confirm.
if not root using SUPER ONE CLICK ROOT.
flash recovery (4EXT is good) www.4ext.net
do a backup and then flash the rom u want
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Did you miss the "stuck in boot loop" part?

sorry,
meant that the triangle is your stock recovery--
you install recovery thru fastboot not adb
i would still, if you haven't, install android sdk on pc-unlock bootloader (fastboot oem unlock) and fastboot recovery--all in wiki
i think it was mentioned--holding down pwr and tb will get you into fastboot mode--phone connected and usb debugging selected on phone
you'll just have more flexibility with flashing roms etc and getting out of trouble

[Q] Incredible S gets stuck on white htc boot screen

I was using my Incredible S normally, when it suddenly faded to black and was totally freeze so I decided to restart it (Taking the battery out)
Then after reboot, It got stuck on white Htc logo (with "quietly brilliant animation playing again and again"). So restarted it again and tried to use the fast reboot option (restarting and holding the VOL DOWN button), but this also didn't work.
Some details: I Have Android Revolution (ROM) with S-OFF
Hope somebody help me!

Bastian_n said:
I was using my Incredible S normally, when it suddenly faded to black and was totally freeze so I decided to restart it (Taking the battery out)
Then after reboot, It got stuck on white Htc logo (with "quietly brilliant animation playing again and again"). So restarted it again and tried to use the fast reboot option (restarting and holding the VOL DOWN button), but this also didn't work.
Some details: I Have Android Revolution (ROM) with S-OFF
Hope somebody help me!
Click to expand...
Click to collapse
Did you remove battery ,then replace battery then
volume down and power?(after the first restart).And im assuming also that you want to go to recovery to redo a backup..

Yes, I just did that (also tried with another battery). But when I pushed recovery, It restarts and still getting stuck on the boot screen. (but now with some vibrations and then goes off)
I was thinking about reinstall the ROM, but that's my last option because I don't have a way to make a backup

Bastian_n said:
Yes, I just did that (also tried with another battery). But when I pushed recovery, It restarts and still getting stuck on the boot screen. (but now with some vibrations and then goes off)
I was thinking about reinstall the ROM, but that's my last option because I don't have a way to make a backup
Click to expand...
Click to collapse
if it allows you to get to recovery screen,did you try to go to any of the other options it gives you to see if it just reboots then as well, or is it just the recovery that reboots? And are you sure your batteries have charge,is your phone plugged in to a charger?

I tried with fastboot>reboot, recovery, and factory reset, all having the same result (reboot and then nothing). I'm not sure what are HBOOT USB and IMAGE CRC used for, and of course, I have not checked the SIMLOCK option.
Thanks for your replies.

Is it possible to make a backup from the recovery mode?

I don't think making a backup of what's going on would help any..but yeah if you can get into recovery you can backup.
Sent from my HTC Incredible S using xda premium

Bastian_n said:
I was using my Incredible S normally, when it suddenly faded to black and was totally freeze so I decided to restart it (Taking the battery out)
Then after reboot, It got stuck on white Htc logo (with "quietly brilliant animation playing again and again"). So restarted it again and tried to use the fast reboot option (restarting and holding the VOL DOWN button), but this also didn't work.
Some details: I Have Android Revolution (ROM) with S-OFF
Hope somebody help me!
Click to expand...
Click to collapse
I would suggest booting to the HBOOT menu and then connect your phone to the coputer you used when you ran Revolutionary to gain S-OFF.
Then select the FASTBOOT menu selection and see if you get into FASTBOOT USB mode. If you do, then I would try to reflash ClockworkMod recovery.

Thanks, I'm going to try that, but first I have to find the drivers.
Thanks Again, tell you later.

After got FASTBOOT USD, how should I continue to reflash ClockworkMod recovery?. Doing this, will I lose everything?
Edit:
I realized I can't reach recovery mode, so I can't reflash :s.

I'm not sure if you'll lose everything but use the command
fastboot flash recovery (name of image)
Make sure the recovery image is in the same folder as fastboot and adb
Sent from my HTC Incredible S using xda premium

Bastian_n said:
After got FASTBOOT USD, how should I continue to reflash ClockworkMod recovery?. Doing this, will I lose everything?
Click to expand...
Click to collapse
FallenSuisydal said:
I'm not sure if you'll lose everything but use the command
fastboot flash recovery (name of image)
Make sure the recovery image is in the same folder as fastboot and adb
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
Flashing a custom recovery will not cause you to lose anything. Once you get recovery installed, any backups you made should then be available to restore.
But based on what you described happened to your phone, restoring a previous backup sounds like the best thing you could do.

Anyone please?
I have gone so far, I mean, I've tried to flash the recovery using fastboot usb but I got an error that said: FAILED (remote: now allowed). I also tried using Android Flasher, but I got an error too. It said: Your phone require ENG bootloader. after that I tried to flash another bootloader, but with no success :/.
I'm starting to get stressed, every different way I try, there's another problem...
EDIT : I'm sure I connected everything well. On screen said FASTBOOT USB, so I supose I got into this mode correctly

Bastian_n said:
Anyone please?
I have gone so far, I mean, I've tried to flash the recovery using fastboot usb but I got an error that said: FAILED (remote: now allowed). I also tried using Android Flasher, but I got an error too. It said: Your phone require ENG bootloader. after that I tried to flash another bootloader, but with no success :/.
I'm starting to get stressed, every different way I try, there's another problem...
EDIT : I'm sure I connected everything well. On screen said FASTBOOT USB, so I supose I got into this mode correctly
Click to expand...
Click to collapse
Looks like you need to resort to reloading a stock ROM. I would suggest you use the PG32IMG.zip method (copy an official RUU ROM.zip to your SD card and rename it PG32IMG.zip) and install it from HBOOT.

tpbklake said:
Looks like you need to resort to reloading a stock ROM. I would suggest you use the PG32IMG.zip method (copy an official RUU ROM.zip to your SD card and rename it PG32IMG.zip) and install it from HBOOT.
Click to expand...
Click to collapse
It didn't work :/, I got a RUU.exe then I extracted Rom.zip file and put into my SD as PG32IMG.zip. The phone readed the file without problems, but after "parsing" it rebooted and the same, some vibes, and got stuck again. also tried to extract the recovery file and just parse that one, but still the same.
I think is not a recovery problem, should I parse something else?

Have you Got the RUU specific to Your Device..????
or try making a Gold card and then flash the Downloaded RUU to avoid CID mismatch error...
---------- Post added at 06:41 AM ---------- Previous post was at 06:36 AM ----------
And have you by any chance removed the battery while the device was stuck on the white HTC screen..???
and one more imporatnt do you have your warranty..???

[HOW-TO] How to flash a factory image / return to stock / unlock / root #

I have created this thread to give a step-by-step on how to flash a stock ROM build available on Google's developer site. (For those that are unaware, an unlocked bootloader is needed, and unlocking is part of the instructions below.)
I've also added a section on how to root for those that want it.
Note: There are other methods that are abbreviated and/or faster, but I wanted to spell out each step in the process for the purposes of learning. I'm a big believer in doing things manually before using a "toolkit", much the same way that, in school, we are taught to do math first, before being allowed to use a calculator. See here for some further explanation.
So, without further ado:
How to flash a stock ROM
Step-by-step
Notes:
1) For the n00bs: read the entire post before proceeding;
2) MacOS-specific instructions: a) no drivers needed, and b) replace fastboot in the steps below with ./fastboot-mac
A. Install the drivers
1) Do not install LG drivers or the PDAnet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here or from here;
3) Install the drivers. See here on how to install them. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). (To enable USB Debugging, you first need to enable Developer options by going to Settings->About phone and tapping 7 times on the build number.) If you are using Windows 8, you will need to do this before installing the drivers.
B. Backup your data
1) Backup all your personal data (e.g., photos, music, etc.) OFF of your device and onto your computer by using whatever method you want that works for you, e.g., MTP, ADB, email, Dropbox, Box.net, whatever.
2) This method will wipe your entire device, including the /sdcard folder, so once you do this, you will not be able to retreive anything that was on your device previously.
3) See here on how to backup your apps and app data if you don't have root.
C. Download the required files to your computer and extract them
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
3) Download the version of Android you want from here. Make sure you are using an occam image which is for the Nexus 4. Most old versions are not usually available on that site; however, there is a mirror on this site: Random Phantasmagoria.
4) Download the appropriate version (for your computer) of 7-zip from here and install it.
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (which will obviously delete all your data & files in /sdcard...). Or do this.
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU or Koush's Superuser; NOTE: So far, only SuperSU v1.43 and newer currently work properly with JWR66V (i.e., 4.3). I've attached v1.51 below.
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: Only if you are running the z20i bootloader: the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
6) Wait for it to boot;
7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
8) Reboot. Done.
Notes:
1) Yes, you will receive the OTA update notification (when it is available) for the next update. WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the bootloader, radio, boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically.
2) There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
3) Do NOT re-lock your bootloader after you are finished. The is no need. 2) Having an unlocked bootloader does not affect anything related to the ROM/GoogleWallet/OTAs. Nothing at all. If your bootloader is locked, you CANNOT use fastboot commands. This is pretty much the only thing it affects. If your bootloader is locked, and you need to unlock it, it will wipe everything, including /sdcard. This is the major drawback of re-locking your bootloader. If you do want to lock your bootloader, the command is: fastboot oem lock

How to return to stock if your USB port is broken
I am adding this how-to in case people need it, for return their device to Google, etc.
This is NOT meant to replace going through the steps in post #1. They are there for your learning, and should be used as a primary method of returning your device to stock. However, if your USB port is indeed messed up, then you will not be able to use the instructions in post #1.
Warning: if your USB port is indeed broken, and you complete all the steps below, you will have NO possible way at all to unlock your bootloader, or get root, or install a custom recovery. Period.
1) Ensure that you have root, and a custom recovery (CWM or TWRP) installed;
2) Download segv11's BootUnlocker app from the Play Store, install it and lock your bootloader with it;
3) Download the odexed version of this file (stock JDQ39 ROM) and place it on your device;
4) Download the JDQ39 stock boot image from here and the stock JDQ39 recovery from here.
5) If you want, you can also download the 0.48 radio and the z10o bootloader from here.
6) Reboot into CWM and flash the three files you downloaded in steps 3 and 4, and the file(s) you downloaded in step 5;
5) Turn off your device and reboot into the bootloader;
6) Go to recovery and access the stock recovery menu (i.e., when you see the android with the red triangle, hold power and press vol up) and do a factory reset and then wipe cache.
7) Reboot your device. Do NOT install any OTA updates if they present themselves. Read and follow this post.
8) Done. Now you are fully stock JDQ39 with a locked bootloader.

Reserved.

Awesome! Thanks again efrant!

Ok...
So I consider myself fairly good at this stuff. I've been rooting and doing custom stuff since the N1. I have messed up somewhere...
So initially I used the "1-click" script method (I know) to unlock/root/BB/etc... It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.
That ended up being unable to get passed the Google screen.
I then used your method, which appeared to work...
First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.
I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!
Ummmm... ****! I even rooted the Desire HD back when you had to do a bunch of weird terminal stuff. What happened? Little help?
EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....
Jesus...

tomedic said:
So initially I used the "1-click" script method (I know) to unlock/root/BB/etc...
Click to expand...
Click to collapse
Yeah, you know I personally don't recommend that
tomedic said:
It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.
That ended up being unable to get passed the Google screen.
Click to expand...
Click to collapse
If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.
tomedic said:
I then used your method, which appeared to work...
First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.
I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!
EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....
Click to expand...
Click to collapse
Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.

efrant said:
Yeah, you know I personally don't recommend that
If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.
Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.
Click to expand...
Click to collapse
Ya, I did the format system out of habit because I usually did that when flashing ROM's.
So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!
I turned the phone off. I await your guidance...

tomedic said:
Ya, I did the format system out of habit because I usually did that when flashing ROM's.
So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!
I turned the phone off. I await your guidance...
Click to expand...
Click to collapse
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.
Ok, do you have data on your device you want to keep?
If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.
If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.

efrant said:
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.
Ok, do you have data on your device you want to keep?
If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.
If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.
Click to expand...
Click to collapse
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...
---------- Post added at 10:05 PM ---------- Previous post was at 09:50 PM ----------
tomedic said:
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...
Click to expand...
Click to collapse
Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.
Any other suggestions? Your stuff works, it's just not booting...

tomedic said:
Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.
Any other suggestions? Your stuff works, it's just not booting...
Click to expand...
Click to collapse
Strange. All the images flashed fine (without errors) and it won't boot?
Can't think of anything else to try at the moment.
Sent from my Galaxy Nexus using Tapatalk 2

Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.
Just verifying that's all.

efrant said:
Strange. All the images flashed fine (without errors) and it won't boot?
Can't think of anything else to try at the moment.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...
I will try your method from the beginning again tomorrow.
I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...

evaradar said:
Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.
Just verifying that's all.
Click to expand...
Click to collapse
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2

tomedic said:
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...
I will try your method from the beginning again tomorrow.
I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...
Click to expand...
Click to collapse
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.

Maverick1707 said:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Click to expand...
Click to collapse
This is indeed strange, as steps D10 and D13 do exactly that: factory reset and wipe cache.
In any case, I will make a note of it in the first post.

efrant said:
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
So just a heads up if anyone runs into this problem.

Maverick1707 said:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Click to expand...
Click to collapse
It worked! Thanks man!
And thank you efrant. Now to switch recoveries and get root! :laugh:
---------- Post added at 10:55 AM ---------- Previous post was at 10:40 AM ----------
evaradar said:
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
So just a heads up if anyone runs into this problem.
Click to expand...
Click to collapse
Yup, I just rooted and had to do the same thing.
I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?
Thanks again all. These little hiccups make it interesting!

evaradar said:
By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Click to expand...
Click to collapse
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.
evaradar said:
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
Click to expand...
Click to collapse
Again, interesting. Not sure why this is.
tomedic said:
I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?
Click to expand...
Click to collapse
Correct.

efrant said:
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.
Again, interesting. Not sure why this is.
Correct.
Click to expand...
Click to collapse
I'm assuming that like the GN we need to rename the recovery-from-boot.p file if we want our custom recovery to survive a reboot?
EDIT- never mind I just looked through your 101 thread and answered my own question- thanks!!

Thank you for making this thread over here. Glad to have you as a moderator. I hope every noob reads all of your threads.
Sent from my BAKED N7

[Q] Soft/Hard Bricked, Lost Root, Lost Recovery, USB Not Recognized

Hi all, this is a last ditched effort at maybe saving my phone. I did an update on my SU and for some unknown reason it rebooted my phone. It then loaded up my rom until the kernel settings loaded then rebooted once again. I then tried to go into recovery to flash a backup and it booted me straight into my unlocked fastboot. I then tried to reboot once again in hopes I could fast navigate into twrp through rom manager, once in I was prompted that I no longer had root. I then decided to start over from scratch and load a recovery in fastboot. Once I had everything good to go I plugged everything in and instead of recognizing my phone as a drive, HTC manager popped up instead. I then updated my drivers to see if maybe that would fix the problem with no luck. I am at a loss at this point. I would greatly appreciate any help you guys can offer.

grimzen said:
Hi all, this is a last ditched effort at maybe saving my phone. I did an update on my SU and for some unknown reason it rebooted my phone. It then loaded up my rom until the kernel settings loaded then rebooted once again. This is completely normal, you should have just rebooted the phone and been done I then tried to go into recovery to flash a backup and it booted me straight into my unlocked fastboot. Again totally normal, thats the bootloader use the vol to move down and choose recovery and hit power this will boot you to TWRP I then tried to reboot once again in hopes I could fast navigate into twrp through rom manager, once in I was prompted that I no longer had root. I then decided to start over from scratch and load a recovery in fastboot. Why ? Once I had everything good to go I plugged everything in and instead of recognizing my phone as a drive, HTC manager popped up instead. You should not have Sync installed only the drivers I then updated my drivers to see if maybe that would fix the problem with no luck. I am at a loss at this point. I would greatly appreciate any help you guys can offer.
Click to expand...
Click to collapse
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?

clsA said:
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
Click to expand...
Click to collapse
I was doing a SU update. It restarted into a loop that boots about 1 min after the splash screen then resets. I've tried to redownload root through SU app as I can no longer connect through usb but it reboots to soon. I used Rom Manager to try and get into recovery as a second alternative.

grimzen said:
I was doing a SU update. It restarted into a loop that boots about 1 min after the splash screen then resets. I've tried to redownload root through SU app as I can no longer connect through usb but it reboots to soon. I used Rom Manager to try and get into recovery as a second alternative.
Click to expand...
Click to collapse
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
flash in recovery
use adb push UPDATE-SuperSU-v1.86.zip /data/media/0
to get the file on the phone
Reboot to bootloader / fastboot USB
and from command line on pc
fastboot erase cache
fastboot reboot

I cant understand why people using those ROm manager apps to install stuff. And you said it rebooted after you update your SU. Then i tink you pressed reboot into recovery instead of NORMAL. Am i wrong?

clsA said:
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
Click to expand...
Click to collapse
bihslk said:
I cant understand why people using those ROm manager apps to install stuff. And you said it rebooted after you update your SU. Then i tink you pressed reboot into recovery instead of NORMAL. Am i wrong?
Click to expand...
Click to collapse
I no longer have a recovery to be able to flash anything. When I try to load into recovery it just boots right back into fastboot. I was just using rom manager to boot into recovery after I couldn't get into recovery through fastboot, not to flash anything. I was updating Super Su through the actual app itself. it seemed to be downloading something when it rebooted itself and I lost root, recovery and the ability to connect to my computer.

grimzen said:
I no longer have a recovery to be able to flash anything. When I try to load into recovery it just boots right back into fastboot. I was just using rom manager to boot into recovery after I couldn't get into recovery through fastboot, not to flash anything. I was updating Super Su through the actual app itself. it seemed to be downloading something when it rebooted itself and I lost root, recovery and the ability to connect to my computer.
Click to expand...
Click to collapse
I have updated SuperSU many times and never got any problem so there is something you did. Are you on custom or stock rom?
Are you s-off / unlocked bootloader?

bihslk said:
I have updated SuperSU many times and never got any problem so there is something you did. Are you on custom or stock rom?
Are you s-off / unlocked bootloader?
Click to expand...
Click to collapse
My bootloader is unlocked and i'm running Viperrom. I've never gone through the process of s-off but for some reason it says it at the top of my fastboot screen...not sure if that's normal or not.

grimzen said:
My bootloader is unlocked and i'm running Viperrom. I've never gone through the process of s-off but for some reason it says it at the top of my fastboot screen...not sure if that's normal or not.
Click to expand...
Click to collapse
Ok. I think you need to reflash recovery again.
Boot into bootloader and fastboot usb
then download TWRP recovery from here http://techerrata.com/browse/twrp2/m7 and pick 2.6.3.3-m7.img
put it into your fastboot folder and flash it "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img and hit enter
now try to reboot into recovery. When there Wipe Dalvik and Cache and reboot. If recovery ask you to root your device then accept it and reboot.
Remember to connect phone to right USB port not 3.0. Use 2.0 port and try annother cable also.

bihslk said:
Ok. I think you need to reflash recovery again.
Boot into bootloader and fastboot usb
then download TWRP recovery from here http://techerrata.com/browse/twrp2/m7 and pick 2.6.3.3-m7.img
put it into your fastboot folder and flash it "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img and hit enter
now try to reboot into recovery. When there Wipe Dalvik and Cache and reboot. If recovery ask you to root your device then accept it and reboot.
Remember to connect phone to right USB port not 3.0. Use 2.0 port and try annother cable also.
Click to expand...
Click to collapse
I've tried a few different cords and all 3 ports I have still nothing but the HTC manager thing. It will recognize it but only for a split second while booting up but it says HTC BUTTERFLY as the drive and i'm not sure if that's a problem or not but it won't recognize it at all through fastboot.

you cant boot up. if it doesnt recognize it in bootloader mode then i dont know.
Try restart PC. Maybe you have several adb at same time. Adn uninstall htc sync if not but keep drivers

bihslk said:
you cant boot up. if it doesnt recognize it in bootloader mode then i dont know.
Try restart PC. Maybe you have several adb at same time. Adn uninstall htc sync if not but keep drivers
Click to expand...
Click to collapse
Ok will try that now. thanks so much for the help.

I hadthe same problem after flashing a kernel. I repeatedly tried the bootloader (audiodown key + power button) until it started. Recovery was not available, in the red triangle screen press audio up key,got the system recovery screen, wipe cache, reboot the system and then try installing Twrp recovery. It worked.
Sent from my HTC One using xda app-developers app

jpaulpra said:
I hadthe same problem after flashing a kernel. I repeatedly tried the bootloader (audiodown key + power button) until it started. Recovery was not available, in the red triangle screen press audio up key,got the system recovery screen, wipe cache, reboot the system and then try installing Twrp recovery. It worked.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I'm not familiar with the red triangle screen is there a way to boot into it?

Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk

grimzen said:
I'm not familiar with the red triangle screen is there a way to boot into it?
Click to expand...
Click to collapse
bihslk said:
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I think @jpaulpra was telling him to reflash stock recovery
then boot to it and do clear cache.. then reflash twrp

When I got into bootloader, I lost the Twrp recovery. So when I selected recovery I got the screen with a "triangle and exclamation mark". If you leave it will reboot the system after couple of minutes. But if the audio up key is pressed, it will show a system recovery screen, where cache can be wiped
Sent from my LT26i using Tapatalk

bihslk said:
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Basically all I'm trying to do now it's find a way to get my computer to recognize my phone as a drive. When I go into viper settings and go to advance menu (with the short time I have before boot loop) there is an option to mount drive. When I select the option to do so it hands on splash screen and I have to hold power button to recycle back on. Once back in it's no longer selected. I've never seen a boot loop go pay the flash screen. Is this normal?

Pretty SOL with my son's Nabi2
I'm having a issue with my sons Nabi2 pretty similar. I messed up bigtime guys I rooted it and started messing aroung with the system files. Then didn't get a boot afterwards, wiped everything from twrps system, data, the whole shabang! Even lost my root! and access to on board flash cause I've been trying to recover using twrp with absolutley no luck. I still have the original stock unrooted backup saved to my pc from when I first installed twrp. Can someone please help me? I'm really out here trying to reach out for some help. didn't even know where to post this. Thank you guys. Note to moderators: If this is the wrong place to post this then please point me to the right direction and I apologize.

Bricked my myphone uno using Android One Toolkit

After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?

t-rayms said:
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
Click to expand...
Click to collapse
If you could tell us more clearly about what did you do actually and which instructions did you followed?

DNA_Uncut said:
If you could tell us more clearly about what did you do actually and which instructions did you followed?
Click to expand...
Click to collapse
i followed(or tried to) the instructions from the site of androidmtk with topic
"how to root android one devices easily"
sorry but system will not let me paste the actual link.
Process involved the use of android one toolkit.
and now my phone no longer boots. Stuck with those 4 animated circles. I have to remove the battery to get out of that screen. But no matter what i did, isn't there a way to just install android? Like installing windows on a blank hard drive? Start from scratch? Loss of data is not a factor

t-rayms said:
i followed(or tried to) the instructions from the site of androidmtk with topic
"how to root android one devices easily"
sorry but system will not let me paste the actual link.
Process involved the use of android one toolkit.
and now my phone no longer boots. Stuck with those 4 animated circles. I have to remove the battery to get out of that screen. But no matter what i did, isn't there a way to just install android? Like installing windows on a blank hard drive? Start from scratch? Loss of data is not a factor
Click to expand...
Click to collapse
Just follow the thread
http://forum.xda-developers.com/dream-uno/development/stock-rom-spice-dream-uno-mi498-t2915844
Download ROM (from the same thread)
http://forum.xda-developers.com/showpost.php?p=61588267&postcount=23
You should get back to stock kitkat (if you follow the instructions as explained). Once you get back your phone to working. Install ota updates you receive that will get you to stock 6.01

t-rayms said:
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
Click to expand...
Click to collapse
You don't need to go back on kitkat as DNA uncut says .....your device is running on which recovery ??

devil anand said:
You don't need to go back on kitkat as DNA uncut says .....your device is running on which recovery ??
Click to expand...
Click to collapse
im sorry but i dont know what "recovery" is. The phone is also no longer turning on so i cant get that info. But im ok with trying kitkat and if the flashing of the ROM works, at least ill have a working phone. And go from there and experiment some more to get the most out of the device.

When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
---------- Post added at 03:58 AM ---------- Previous post was at 03:49 AM ----------
t-rayms said:
im sorry but i dont know what "recovery" is. The phone is also no longer turning on so i cant get that info. But im ok with trying kitkat and if the flashing of the ROM works, at least ill have a working phone. And go from there and experiment some more to get the most out of the device.
Click to expand...
Click to collapse
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see

DNA_Uncut said:
Just follow the thread
http://forum.xda-developers.com/dream-uno/development/stock-rom-spice-dream-uno-mi498-t2915844
Download ROM (from the same thread)
http://forum.xda-developers.com/showpost.php?p=61588267&postcount=23
You should get back to stock kitkat (if you follow the instructions as explained). Once you get back your phone to working. Install ota updates you receive that will get you to stock 6.01
Click to expand...
Click to collapse
i installed the Android CDC Driver. DL the SP Flash Tool and the custom ROM. Rebooted the PC. Ran the SP Flash Tool. The final stage where i click on DL and connect my phone, nothing happens. The scrolling progress bar at the bottom of the flash tool doesnt start. With or w/o batteries in the phone. What do i do next?

devil anand said:
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
---------- Post added at 03:58 AM ---------- Previous post was at 03:49 AM ----------
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
Click to expand...
Click to collapse
when i selected the recovery option, the next screen is a picture of the android robot lying face up. With its body panel door open with red triangle with black exclamation markm, "No command" prompt

t-rayms said:
when i selected the recovery option, the next screen is a picture of the android robot lying face up. With its body panel door open with red triangle with black exclamation markm, "No command" prompt
Click to expand...
Click to collapse
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Link - kernel- http://www.thunderzap.in/downloads/
SuperSU - https://download.chainfire.eu/741/SuperSU?_e_pi_=7,PAGE_ID10,5223979215

devil anand said:
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Link - kernel- http://www.thunderzap.in/downloads/
SuperSU - https://download.chainfire.eu/741/SuperSU?_e_pi_=7,PAGE_ID10,5223979215
Click to expand...
Click to collapse
great. thanks. it worked. still cant believe it. But thank you very very very much.

t-rayms said:
great. thanks. it worked. still cant believe it. But thank you very very very much.
Click to expand...
Click to collapse
Just hit thanks!!
I went to Android mtk website ...then I knew where was the problem.
Note : SuperSU zip is used to root a phone via custom recovery (twrp,philzz) ...but in marshmallow you can't root your phone just by installing SuperSU zip ....you need to install a custom *kernel* first ....remember next time??

devil anand said:
Just hit thanks!!
I went to Android mtk website ...then I knew where was the problem.
Note : SuperSU zip is used to root a phone via custom recovery (twrp,philzz) ...but in marshmallow you can't root your phone just by installing SuperSU zip ....you need to install a custom *kernel* first ....remember next time
Click to expand...
Click to collapse
i take it that this step Then tap on wipe option and then factory reset and confirm it. fixed the bricking of the phone
and these steps After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
rooted the phone right?
One other thing is, whenever theres a system update, during the rebooting it does an error and i have to remove battery to restart the phone. Does rooting the phone cause updates not to work?

t-rayms said:
i take it that this step Then tap on wipe option and then factory reset and confirm it. fixed the bricking of the phone
and these steps After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
rooted the phone right?
One other thing is, whenever theres a system update, during the rebooting it does an error and i have to remove battery to restart the phone. Does rooting the phone cause updates not to work?
Click to expand...
Click to collapse
You took a bit ....if you have rebooted your phone after just factory reset .....you may have got bootloop again.....(stuck on boot animation).
About your second problem ....
When the error happens in between these steps of installation .......you tap on reboot and install and your phone goes to recovery and after successful installation your reboots .
What's the error ??
Yeah rooting your phone changes system which causes problem while installation of the original update...??

devil anand said:
You took a bit ....if you have rebooted your phone after just factory reset .....you may have got bootloop again.....(stuck on boot animation).
About your second problem ....
When the error happens in between these steps of installation .......you tap on reboot and install and your phone goes to recovery and after successful installation your reboots .
What's the error ??
Yeah rooting your phone changes system which causes problem while installation of the original update...
Click to expand...
Click to collapse
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.

t-rayms said:
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
Click to expand...
Click to collapse
Just unroot your phone and try updating again !!!??

devil anand said:
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Click to expand...
Click to collapse
It worked for me too, but now I can`t update SuperSU.
Update from OS failed, from TWRP gives bootloop.
I`m on CM13 SNAPSHOT.
... also front camera cant take picture, but preview works ok.

Johnny_16 said:
It worked for me too, but now I can`t update SuperSU.
Update from OS failed, from TWRP gives bootloop.
I`m on CM13 SNAPSHOT.
... also front camera cant take picture, but preview works ok.
Click to expand...
Click to collapse
What's the need of updating SuperSU ..,...
Use Google camera ....
Sent from my A1 using XDA-Developers mobile app

t-rayms said:
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
Click to expand...
Click to collapse
You've root? And which update do you wanna install on your phone!?
Just tell me what's your build number.. I'll help ya out.

HELP
My cousins Myphone Uno is not turning on when pressing the power button, but if I put in a charge the screen turns on after a few minutes showing the battery but I don't know if it is charging. after a minute the display will go out and the screen flashes a once or twice then off and screen turns on and display the battery it will be on a loop, I can still get to boot option when screen flashes starts,
it shows:
[Recovery Mode]
[Fastboot Mode]
[Normal Boot]
[Normal Boot +ftrace]
[Normal slub debug off]
but when I select any options or not to ,the phone will turn off. Can you help me find a way to make this phone work again? thank you in advance!
PS: If I connect it in my PC it wasn't detected and the the loop will go on and on.
Usb debugging mode is also turned off