Hi to all! I did a lot of nonsense. I wanted to make a permanent root. I made the last point of the instructions chrulri and the device is no longer boot. I decided to do all over again. But after installing SDE, the device is no longer to enter in the menu recovery and not load firmware. The device simply hangs at the first appearance of the logo archos. What do I do?
Related
I got a new archos g9 80 in the mail today. I was following guides in the forum to root my device.
Here is what I did:
Flashed the ics aos file.
Paul's temp root.
ran enable_sde
Current State of tablet:
When booted normally, loops splash logo.
When recovery boot, shows recovery and displays on computer for split second. Then turns off.
What can I do to fix this? I am not sure what went wrong.
Edit: After I enabled SDE, I forgot to remove /data/local.prop to disable temp root. Would that contribute to the problem? How can I remove temp root now?
Edit 2: So here is the funny part, I hope you guys all get a laugh out of this. this is not actually my tablet. I have been helping a good friend of mine over webcam. When booting into the recovery, she would hold the power button still. I thought it was crashing, but she was just powering it off because she wouldn't let go of the button.
just remove it then everything should work normaly.
when i installed pawl s root my tablet needed minutes to boot!
just connect it to your pc and wait for it to boot then it will be connected in debugging mode then remove paul s root.
Thanks for the help, but I got it working now. See Edit 2 in the original post. Once we could access the recovery. I flashed Petru's root and busybox ICS rom.
So a friend recently bought this spanish voxter tab 97 IPS (16GB) and after a few days of usage and several attempt to install a custom ROM, the tablet stopped booting. According to him, he tried loading a "compatibility bla bla bla.zip" file with CMW which I really do not know what it is, and since he did the installation, the tab stopped booting into system. Every time it's turned on, it just stops at the boot screen and nothing more. Although before this, he had installed a custom recovery and had also done a Nandroid backup with the recovery. However, what baffles me is, CMW is no longer accessible through the normal "power + volume up" key combo and I'm quite unsure of how to boot into fastboot.
That aside, I tried booting into recovery with adb because apparently, adb recognizes the device whenever it's stuck at boot screen, this also failed, neither did rebooting into fastboot via adb work. All I need to know is if this device is totally bricked, or if there's still something I can do. If there's any, I really would appreciate every help offered. Thanks..
I'm not an expert in Android, nor am I an expert with computers, just an average joe in the Android world. Since the time I got myself into this community I never stopped learning something small. I was able to root my phone, install custom firmwares, unroot my device, do a NANDroid back up. All of this done with the help I got from an online source. Now, I'm looking forward to do further tweaks in my device's system. It might sound risky, but I'm enticed by how far an android device can be further improved. But before I do any of this, I'd like to know the appropriate steps to do when something goes wrong like what if device ends up on boot loop.
Questions:
1) What is boot loop?
2) What causes boot loop?
3) Is it the same with a bricked phone?
4) Can the phone be recovered from it (boot loop / brick)?
5) What should be done when a phone is on boot loop?
I humbly ask everone to share a bit of your knowledge about this.
Thank you.
1 - Is kinda of obvious. Bootloop is when your device is stuck at some of bootscreens (model screen, Samsung logo screen) and it doesn't boot properly. Even if you remove the battery and insert it again to turn it on, it doesn't turn on.
2 - There are various reasons: incompatible kernel, incompatible rom, edits on build.prop, rom poorly flashed. And, for our device, if you try to reboot into recovery directly and it has CWM installed, it may enter on recovery bootloop.
3 - I''d say it is a "soft bricked phone". If you has access to recovery or download mode, congrats, you can undo the mess. But if you can't, you got a hard brick. So, it will need repairs.
4 - As I said before, if you has access to recovery or download mode, it is possible to recover it.
5 - It depends. First I would undo my last actions. If I don't have success, I would reflash stock rom, it's almost guaranteed.
So, it happened to my phone when I attempted to do a "Recovery Back Up" using "[ROOT] Rashr" app. I had a Recovery Boot Loop, which boots only into Recovery Mode. But it's fixed now. Here's the thread: http://forum.xda-developers.com/grand-quattro/help/s-o-s-device-boots-cwm-t2981980
This is a reference for those who have the same problem.
Hello all,
I recently tried updating my Archos 70c Titanium to Lollipop and started with rooting the device with Kingo Root.
After that I've tried Archtool app and CWM to deploy the custom recovery console to be able to install custom ROM. This somehow gone bad, and now I cant access the recovery console any longer.
Means, either with any app that can boot into recovery nor by pressing the hardare button combination. Both ways do NOT work any longer.
Since regular OS (Androis 4.4) is still properly booting, I guess I "simply" have to install a new custom recovery console.
Can someone share some info or guideline about how to do so?
The Kingo Root seems not to be reboot persistant. Is that correct? Which apps/tool are known to work with Archos 70c containing the Rockchip RK3026?
Any help is appreciated.
THanks much.
Hey all,
I've tried re-rooting the device with KingoRoot and it seems the device hangs on next reboot. At least I cant activate wireless any longer, and thus cant proceed with any other tool.
The next reboot, the device does not boot at all and hangs in a welcome boot logo loop. Only pressing the Hardware reset button on the back, makes it boot normally again. But then rooting is gone.
Anyone any idea how to proceed or troubleshoot.
Thanks for input.
[closed] recovery console broken on Archos 70c Titanium
Got some support in another forum purly focusing on the Archos devices.
For further reference, here's the thread: http://www.arctablet.com/blog/forum...titanium-rk3026-recovery-mode-not-accessible/
This can be closed.
I have a Umidigi Crystal (2/16) and it´s not booting anymore.
How that came is a long story.:crying:
I got the phone, wanted to root it and while I was enabling usb debugging in developer options, I noticed you can root it from there as well.
I have no idea whether thats a Umidigi special or if that was seen on other phones too, basically I had a slider option to enable root access.
After a reboot, SuperSU was installed automatically, root checker, file explorer and rom toolbox worked fine with it but I actually rooted to get Xposed Installer.
That worked very well too, only did I want to have a custom recovery to prepare my phone in case of a bootloop.
So I followed these instructions.
I hadn´t unlocked the bootloader by the time and since the instructions said I would have to unlock it I did that first using these instructions.
Everything worked as expected but from this point on, on the pre-bootanimation picture my screen would say
Code:
Orange State
Your device has been unlocked and can't be trusted
Booting in 5 sec...
As everything else was the same as before, I just ignored it.
Then I moved on to installing TWRP by, again, these instructions.
The process seemed to work but after finishing, I was unable to boot into recovery mode, my phone would just boot into the normal OS(which still worked by the time).
I wanted to get around that by using this app but because of the unlocked bootloader my phone was factory reset
and I had to root again.
I was going for the same way I already did it beforehands and I was asked to reboot again.
After that point, my phone was stuck in the pre-bootanimation screen saying it´s orange state thingy again and would just stay there forever.
I tried installing the stock rom from here ((2/16 - V1.0_20171026)) to get rid of the root setting I enabled.
Now I get the pre-bootanimation screen with the orange state text again and after 5 seconds it keeps the background image but the text disappears.
Thats where it´s stuck for like 3 hours now.
When I press the power key a couple of seconds, that loop starts again, I can´t turn the phone off.
Things I can still do:
•Reboot (holding the power button, still get stuck the same way though)
•Access a PC, the internet, an SD Card and electricity
•Charge the phone
•I still have all the drivers on my PC properly installed
Things I can´t do
•Keep the phone turned completely off
•Boot into fastboot, recovery or normal OS
•Get the PC to recognize my phone (not even the adb)
What I want (if possible in that order):
•Boot into literally any OS
•Use the current OS or any custom rom
•Have root access without the developer option method
•Have TWRP
•Unlocked Bootloader
I know, I ask for a lot but this is the only phone I have right now and I badly need it.
Getting it to boot again is really the primary goal here.
Thanks so much to everyone who tries to help me, it really means a lot