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.
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
jmserapion said:
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
Click to expand...
Click to collapse
First off are you rooted? Do you have a custom recovery installed? Are you running a custom ROM or kernel? If you you have a custom recovery did you make a backup? If you can provide some more details I can try to help you out.
Sent from my SCH-I535 using xda premium
Alcatel OT5020t - Mediatek BOOTLOOP SOLVED!!
jmserapion said:
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
Click to expand...
Click to collapse
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Pop c7 7041x
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
I have 7041x stuck in boot loop. Flashing a rom by CVM doesnt even help. Could you please tell us how you fixed yours.?
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
hello,
can anyone help me please ? i have flashed my alcatel one touch fierce 2 7040n with the wrong flash, now it's stuck in bootloop i have just access to recovery mode so i tried wipe data/factory reset and wipe cache partition but there's no change. then i installed adb and all usb drivers on my pc and tried to send the zip package with adb sideload but it dosen't work. so i tried my last chance to update from sd card, i put the zip file package in the root of a formatted sd card, the phone detect the sd card and mount it correctly but the files was not showing (just like it's empty) i don't know why, is there any solution for that issue ?
i really need your help and thank you in advance.
nabil_rachak said:
hello,
can anyone help me please ? i have flashed my alcatel one touch fierce 2 7040n with the wrong flash, now it's stuck in bootloop i have just access to recovery mode so i tried wipe data/factory reset and wipe cache partition but there's no change. then i installed adb and all usb drivers on my pc and tried to send the zip package with adb sideload but it dosen't work. so i tried my last chance to update from sd card, i put the zip file package in the root of a formatted sd card, the phone detect the sd card and mount it correctly but the files was not showing (just like it's empty) i don't know why, is there any solution for that issue ?
i really need your help and thank you in advance.
Click to expand...
Click to collapse
It's been so long since i messed with these Alcatel phones. But if i recall, you can take the rom zip or update zip, and you have to rename it to some special name. Then you put it on sd card and it'll install to phone.
But in your case, if you flashed wrong. There might be something else.
But either way. Since you can boot into recovery or bootloader you should be able to push stock firmware to device. You need to make sure you get the correct files for your device.
This is most i can tell you. I've been using samsung devices for past years and forgot alot about flashing devices such as this through adb.
All i can say is, at least it doesn't seem like your hard bricked. As long as you can get into bootloader mode or recovery, you should have a way to fix. Search and Google around! Good luck!
---------- Post added at 06:35 PM ---------- Previous post was at 06:23 PM ----------
Whenever learning to mess with phones and roms with adb and fast boot. As a lot of devices are different, but some simple key facts to follow are as follows.
Find out your devices partition layout (which partition is boot, system, recovery)
Don't mess with any other partition but them.
Always, always make a backup of all partitions with 'dd' command. And keep safe.
Need build prop
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
Where would I find the build prop bro? Thx
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.
Hello.
How it happened
I rooted my HTC One S, then flashed CyanogenMod on it. Used it for a few months, very happy with it. Then I tried to update - automatically, not manually (that was mistake number 1). The phone was then stuck in a bootloop into recovery. (Off>Recovery>Off>Recovery). I didnt know what to do, so I pressed 'Reset phone', or something like that. Since then, the problem has gotten much worse. Now there's a different bootloop: Off>HTC opening screen. That's it. Im desperately trying to access recovery mode, to flash a new ROM to fix the situation.
What did I try
1. Power + VolumeDown does nothing.
2. Installed the HTC One S toolkit. When pressing 'boot into recovery', it says 'device not found'.
3. Tried to boot into recovery from ABD tools, but it says device not found. I tried putting screenshots here, but XDA forum new user limitation doesnt let me. Anyway, if you add this to the imgur url, youll see the screenshots (sorry about this inconvenienace):
/SblBm3M
/6HEvZDk
TL;DR
Phone is stuck in a bootloop. Cant access recovery. Is there any way to fix this situation?
Thank you very much in advance for your time to help me out.