I'm sorry in advance if this is a really stupid question, but I couldn't find anything after searching Google, or maybe I wasn't searching for the right thing? Anyways I'd appreciate any help on this.
I'm a complete noob in the world of rooting. I thought I'd give it a go this morning. Everything went well and I think I was successful. I was trying to remove some apps (bixby) with a root access app remover and restarted my tab 6 when I encountered this problem. I keep getting the message 'downloading... do not turn off target' instead of rebooting into the system like normal. I've tried going into recovery mode and redoing the steps from the rooting guide I followed, but I'm getting the same blue screen.
What should I do now? What did I mess up?
You're booting into download mode - What packages did you "remove" because it's possible you removed something that the Tab relies on, especially if you were removing Samsung stuff.
You could try booting into recovery, then clearing dalvic and cache.
I assume you didn't flash TWRP?
Your only other option I think will be to refresh stock.
If you're a noob and planning on messing with the system files, you should really install TWRP and create a full backup before you do anything else so recovering from issues is a bit easier.
Related
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
m_hawkmoon said:
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
Click to expand...
Click to collapse
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Theonew said:
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Click to expand...
Click to collapse
The phone rebooted automatically. Did not give me the chance to do anything beforehand.
As you said the phone was soft bricked so when i got home that day i just fixed it. No problem. However I am really really into getting to find out how a 1 day old back up can get corrupted.
i don't exactly remember what i did, i was in the middle of rooting my phone through z4root and i pulled the battery out..when i started it again it went in bootloop now i don't know how to recover from that.I've done this before but my phone was full of crap and i HAD to reset it since opening the app drawer was lagging. I've gone into recovery mode and already used the options wipe factory data reset and cache but its still the same..please help!
I'm thankful on every answer that i get and i don't know how to use odin either, i can't even find the files for my phone, i downloaded android sdk on my computer too if thats any help
aman9991 said:
i don't exactly remember what i did, i was in the middle of rooting my phone through z4root and i pulled the battery out..when i started it again it went in bootloop now i don't know how to recover from that.I've done this before but my phone was full of crap and i HAD to reset it since opening the app drawer was lagging. I've gone into recovery mode and already used the options wipe factory data reset and cache but its still the same..please help!
I'm thankful on every answer that i get and i don't know how to use odin either, i can't even find the files for my phone, i downloaded android sdk on my computer too if thats any help
Click to expand...
Click to collapse
Search for the how to use odin thread. That tells you all you need. Then you just download a ROM whether its a custom ROM or a stock ROM. Open odin and flash it. Your phone will be fixed.
I rooted my phone back in December and have been using it without problems since then. I've rebooted it tons of time, haven't installed anything unusual or tried to modify anything. I just followed the normal instructions for rooting and flashing a custom rom. Today, I rebooted my phone and now it's hanging at the Galaxy SIII logo screen. Taking out the battery didn't help. I have no idea why it would do this out of the blue. What are my options for fixing this? Can I recover my data?
blueintegral said:
I rooted my phone back in December and have been using it without problems since then. I've rebooted it tons of time, haven't installed anything unusual or tried to modify anything. I just followed the normal instructions for rooting and flashing a custom rom. Today, I rebooted my phone and now it's hanging at the Galaxy SIII logo screen. Taking out the battery didn't help. I have no idea why it would do this out of the blue. What are my options for fixing this? Can I recover my data?
Click to expand...
Click to collapse
Should be easy to fix. Common issue.
Try booting into recovery. If you can then clear cache and dalvik. Try rebooting then.
If that doesn't work try re flashing the rom,
If you can't reboot into recovery but can get into download mode then you can easily fix it at the cost of losing all your data.
Let me know how it turns out.
At this point, my phone is just one big tweak.
Wiping the caches didn't work, so I ended up having to reflash the rom. Everything seems to be back to normal now though, thanks!
I own a rooted Huawei Ascend Mate 2 on 4.2. stock ROM. The Huawei ROM is aggressive at killing apps, and I decided perhaps moving Kik into the system would help prevent it from being killed so much (I miss messages more often than I get notified). Guess that was stupid, as now my screen will not come on after the booting animation. ... It just goes black. Clicking the power/unlock button will make it vibrate quickly, but that is all. I can reboot by pressing and holding, and the boot animation comes back up, but goes black again. The phone appears to be on even though the screen keeps sleeping, my computer detects it. I cannot confirm if it registers charging, as I have my LED disabled. I do not have a nandroid backup (that IS, indeed, stupid of me), so I know a factory reset would bootloop the device due to the modifications I have made. Please, any suggestions on how to wake this thing?
I dont need to hear "Well sounds like it's baked lolz" because im already afraid that's what im looking at.
Update:
I've been trying to push TWRP in, and struggling.
In Command, it seems everything is ok up until a certain point. I go through all the code, then try to 'reboot-bootloader' but it comes back with 'error: device offline'
How can I get around this to fix this thing??
Im using Win7 if it helps.
Bump
TWRP is installed now after a lot of fuss. Can't get the stock Rom to install now. It keeps saying 'error flashing zip '/sdcard/TWRP_BACKUPS_stock-system-with-root.zip'
Ive wiped cache, dalvik cache, wiped the previous ROM (which also was stock), and the error keeps happening.
Any help??? I would really appreciate someone contributing to this thread.
zombunny said:
Bump
TWRP is installed now after a lot of fuss. Can't get the stock Rom to install now. It keeps saying 'error flashing zip '/sdcard/TWRP_BACKUPS_stock-system-with-root.zip'
Ive wiped cache, dalvik cache, wiped the previous ROM (which also was stock), and the error keeps happening.
Any help??? I would really appreciate someone contributing to this thread.
Click to expand...
Click to collapse
Hello.
Thank you for using XDA Assist.
Please ask for help in your specific device forum for Q and A.
That can be found here:
http://forum.xda-developers.com/ascend-mate2/help
Also, for future reference, here is your device's main forum area:
http://forum.xda-developers.com/ascend-mate2
Your device experts are located there.
Good luck!
Hi everyone,
I hope I am in the right forum to post my query. I am trying to find a solution to the existing Problem. Before I get to describe the problem specifically I must make it clear that this is my first time on any android forum. While trying to find a solution for the existing problem, I had to google words like Bootloop, Softbrick, TWRP, Custom Recovery, Root, Flash, ROM etc. They still do not make much sense to me (I will be reading more about them in the coming days). So now you can imagine how big of a Noob I am.
Well, I own a Moto G 1st Gen XT1033. Since yesterday it is in a Bootloop. The phone boots completely at times but automatically restarts itself after a while. Sometimes I have 1-2 minutes at maximum to use the phone. Until now I have been able to delete quite a bit of data for example pictures and certain apps because I thought that Bootloop was happening because of no space on the memory. The last app that I installed 3 days back from Google Play after which this problem started occurring, I was also able to uninstall it. Until now I have tried wiping out Cache by going in the recovery mode but that didnt fix the Reboot problem. I also tried holding the Volume Up + Volume Down + Power button for 2 minutes (I read it on internet somewhere as a fix to the problem) but that didnt help either. I have never created a backup and I don't want to do a Factory Reset as a fix to the problem because I don't want to lose the data. I also tried to follow your solution for backing up data but I got lost. I don't know where to start from. Thats why I am writing here.
I don't know if my phone is rooted. I did turn on Developer Mode on my phone in the past (if this info helps).
I do not know which Android version I have but I am guessing that it is Lollipop.
I never installed TWRP or any Custom Recovery software on my phone before.
The battery is working ok.
What I am looking for is:
1) Step by step guide to create a backup
2) Resolving Bootloop issue if possible
Thanks
without custom recovery no data backup is possible.
u need to unlock your bootloader and install The Twrp recovery to perform the backup.
but only fix for you is factory reset.
jbanti said:
without custom recovery no data backup is possible.
u need to unlock your bootloader and install The Twrp recovery to perform the backup.
but only fix for you is factory reset.
Click to expand...
Click to collapse
Thank you @jbanti Apologize for my late response. As far as I know unlocking the bootloader will erase the memory. One can recover data by ADB Pull by using these Threads:
https://forum.xda-developers.com/moto-g/help/moto-g-1st-gen-xt1033-boot-loop-stock-t3357472 (Post #4)
https://forum.xda-developers.com/showthread.php?t=2426426
So I know that there it is possible using`adb pull` command to take backup of whole device but I don't know how. I get lost in the 2nd thread. Any lead would be appreciated
Thanks