[SOLVED] Archos recovery files - Gen8 Android Development

Hi, all
I am trying to install UrukDroid to Archos 35 Home Connect (gen8 device).
But its installation script cannot navigate in menu using volume keys as they are touch in my device.
As archos recovery is able to use them I suppose that UD install script uses older (?) version of auibox (I know it is used in recovery)
Could you please send the auibox file from archos recovery or tell me a way how to get it from recovery?
thanks!

Golomidov said:
Hi, all
I am trying to install UrukDroid to Archos 35 Home Connect (gen8 device).
But its installation script cannot navigate in menu using volume keys as they are touch in my device.
As archos recovery is able to use them I suppose that UD install script uses older (?) version of auibox (I know it is used in recovery)
Could you please send the auibox file from archos recovery or tell me a way how to get it from recovery?
thanks!
Click to expand...
Click to collapse
For those who are interested
Solved using this thread http://forum.xda-developers.com/showthread.php?t=880321

Related

[Q] How do I restore a borked bootloader ?

Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
obarthelemy said:
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
Click to expand...
Click to collapse
If you can still use ADB your tablets bootloader is likely not messed up, it sounds like you booted the tablet into fastboot mode not recovery. To get into recovery you can enter it by holding a key combination the most common combination is holding volume up plus the power button at the same time. If that doesn't work from ADB you should be able to get into recovery by running the command:
Code:
adb reboot recovery
Also ROM manger doesn't always work right with every device so I would recommend just uninstalling ROM Manager for now. If it is booting fine into bare ICS then your tablet should be ok, if your looking for Google Apps for ICS they can be found here http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
obarthelemy said:
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
Click to expand...
Click to collapse
obarthelemy said:
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
Click to expand...
Click to collapse
obarthelemy said:
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
Click to expand...
Click to collapse
The recovery you are referring to is to the standard Android 3e recovery it is included in every version of Android, and will always be like that unless you install a custom recovery such as CWMR and or TWRP. As a general rule you should never install a custom ROM without having a custom recovery image installed first, essentially all the stock 3e recovery is good for is installing OTA updates and preforming a basic factory reset of your phone. You should try and fix your recovery before going any-further, you can sign the un-signed zip by using this tool. Overall, I would focus on trying to fix the recovery to prevent any further damage to your tablet and so that way you have a simple way to recover from anything that might go wrong when flashing ROMs, mods, and other zip files.
issue with the uImage linked
The uImage linked on the download pages for the CM10 and CM9 version ends in ".*"
I have no clue what the normal extension should be; replacing that *.zip doesn't work. Is the file bad, or am I just too clueless about what to do with it ?
Ok so the question is:
1- which "recovery mode" file should I install on my tablet, especially since the mod author's ones seem flaky
2- how do I do that via ADB since my tablet no longer seems to have a working "recovery mode".
I'm sorry to hassle you with those questions... I've looked around, I can't find info nor files I'm confident about ?

[Q] Unable to boot into CWM with Sanei n10 tablet.

Hey guys,
I have a bit of a head scratcher. I am currently trying to flash my new Sanei n10 tablet with CM10 and it is proving much more difficult than I first imagined.
My main problem seems to be that the device just does not want to boot in CWM. I have installed the latest version of CWM (found here) via the Terminal Emulator but it doesn't boot into CWM Recovery, but rather just boots normally. I have also tried using the hard keys to boot into it but all that does is boot me into the default android system recovery (3e) which is useless as it will only update from verified roms.
The device is rooted and I have ROM Manager installed. I have given Terminal Emulator superuser permissions... It just doesn't seem to want to boot into CWM Recovery. I have tried using both ROM Manager as well as NOVO7 Tools to boot into it but I get the same results (device just reboots normally)
I think that it might be something to do with the stock ICS 4.0.4 that came with the device.that is causing me so much hastle, but I was hoping someone out there might have experienced a similar issue or can offer some insight to where I am going wrong.
Thanks in advance!
M
msm1003 said:
Hey guys,
I have a bit of a head scratcher. I am currently trying to flash my new Sanei n10 tablet with CM10 and it is proving much more difficult than I first imagined.
My main problem seems to be that the device just does not want to boot in CWM. I have installed the latest version of CWM (found here) via the Terminal Emulator but it doesn't boot into CWM Recovery, but rather just boots normally. I have also tried using the hard keys to boot into it but all that does is boot me into the default android system recovery (3e) which is useless as it will only update from verified roms.
The device is rooted and I have ROM Manager installed. I have given Terminal Emulator superuser permissions... It just doesn't seem to want to boot into CWM Recovery. I have tried using both ROM Manager as well as NOVO7 Tools to boot into it but I get the same results (device just reboots normally)
I think that it might be something to do with the stock ICS 4.0.4 that came with the device.that is causing me so much hastle, but I was hoping someone out there might have experienced a similar issue or can offer some insight to where I am going wrong.
Thanks in advance!
M
Click to expand...
Click to collapse
here
1. Download the latest ClockWorkMod for Allwinner A10 tablets from here:
http://forum.xda-developers.com/show....php?t=1802268
2. Put all three files in the ZIP inside the root of a MicroSD card and insert it in the tablet
3. Check from the Terminal app inside the tablet to see if the MicroSD card is mounted in /sdcard (just type "ls /sdcard").
4. If the "ls" command doesn't show anything (that's what happened in my case), then you must modify the "install-recovery.sh" file and replace all instances of "/sdcard" with "/mnt/extsd".
5. With the proper "install-recovery.sh" file, run the commands specified in the above xda link (in my case the card is in "/mnt/extsd" instead of "/mnt/sdcard" as the original example shows):
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
6. The tablet will then reboot to CWM recovery. Then follow the regular steps to install Cyanogenmod (wipe plus install ROM + GApps + Compatibility). This time the Recovery menu won't care about the files being unsigned and will install them right away!

Help booting TWRP

I rooted my Nook using the method here. I then downloaded Goo Manager though the app store and installed TWRP recovery. If I choose "reboot recovery" in Goo Manager, it will grant SU access and reboot, however it will not boot in to TWRP. it will just reboot the Nook normally. Then I powered down normally and now my Nook won't boot at all! It just shows the splash screen and shuts off or bootloops if i plug it in. What's up?
Edit: I tried doing the root method over again to unbrick it. I could boot in to recovery but the tablet still won't boot after I flash.
Unfortunately I can't help you. Just give my view that whenever I have tried TWRP there has been issues. EIther "not just doing the job" which is annoying but not much more. But also getting stuck in bootloop. When that happened to me I stumbled on the repart.im recover image that put my Tablet back to "out of the box" condition. I ran it and after that I have used CWM without issues.
Hopefully someone will come along with a better answer to you.
asawi said:
Unfortunately I can't help you. Just give my view that whenever I have tried TWRP there has been issues. EIther "not just doing the job" which is annoying but not much more. But also getting stuck in bootloop. When that happened to me I stumbled on the repart.im recover image that put my Tablet back to "out of the box" condition. I ran it and after that I have used CWM without issues.
Hopefully someone will come along with a better answer to you.
Click to expand...
Click to collapse
How did you flash CWM? I can't find any flashable files anywhere. Did you do it through Rom Manager or something like that or did you download a file and flash it through a bootable SD recovery?
Back when I origianlly did it I did it like I outline in this post (under C): http://forum.xda-developers.com/showthread.php?t=2081981
Nowadays I do it differently though, but that process should still work.
GooManager does not flash the right recovery image for some root methods. The Nook Tablet one has acclaim in the name, and when I rooted mine, I realized it tried to flash a build for blaze. I just booted from a CWM SD to install my ROMs, and then flashed TWRP to internal using fastboot.
alevineman said:
GooManager does not flash the right recovery image for some root methods. The Nook Tablet one has acclaim in the name, and when I rooted mine, I realized it tried to flash a build for blaze. I just booted from a CWM SD to install my ROMs, and then flashed TWRP to internal using fastboot.
Click to expand...
Click to collapse
Where did you get the TWRP to flash and what is fastboot?
Snakebear said:
Where did you get the TWRP to flash and what is fastboot?
Click to expand...
Click to collapse
Fastboot is a tool in the Android SDK that can do a lot, including flashing a recovery.
Steps to use
Make a Ubuntu 13.04 virtual machine
Open Terminal
Put in : "sudo apt-get install android-tools-fastboot"
Install CyanoBoot if not already
When booting Press n in cyanoboot
Choose start fastboot using buttons
Plug into computer and hook up to VM
Download TWRP internal 2.4.3.0 from iamafanof.wordpress.com
Open terminal
Type cd Downloads
Type ls
Look for a file that starts with twrp
Type fastboot flash recovery then type the file name of the twrp file
Done
Snakebear said:
How did you flash CWM? I can't find any flashable files anywhere. Did you do it through Rom Manager or something like that or did you download a file and flash it through a bootable SD recovery?
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=40998406&postcount=3.
my nook tablet stopped in read forever.
my nook tablet stopped in read forever.
volume buttons not working
needs twrp recovery
any help?

Hp 7 plus 1301 root

Im successfuly root my hp tab with help off vroot.. But every reboot tablet automatic factory reset and all data,apps remove any solution?????????
Anyone port cwm aosp base ROM
Where is cwm recovery ???????
Anyone try
Source Code for 1301 7 HP tab,,
http://h20392.www2.hp.com:80/openso...&e=true&fam=Tablet+PCs&prd=HP_7_Plus_13XX-OSP
Solution
rakshakb said:
Im successfuly root my hp tab with help off vroot.. But every reboot tablet automatic factory reset and all data,apps remove any solution?????????
Click to expand...
Click to collapse
I am in the same boat with the factory resets... did you ever find a solution?
Yes, flash update.zip via fastboot adb sideload
Sent from my D2105 using XDA Free mobile app
http://ftp.hp.com/pub/softlib/software12/COL53679/ob-134254-1/update.zip
Sent from my D2105 using XDA Free mobile app
infidellife said:
I am in the same boat with the factory resets... did you ever find a solution?
Click to expand...
Click to collapse
I think in bootloader something that reset after root here is bootloader.fex in update.zip
https://docs.google.com/file/d/0B0hC3FvuMXfEUlFLRG5mTG5lRVU/edit?usp=docslist_api
Sent from my D2105 using xda Forum
Here is boot.img
https://docs.google.com/file/d/0B0hC3FvuMXfETzIxVlhuSVlTUGs/edit?usp=docslist_api
Sent from my D2105 using xda Forum
attachments
Update. Zip
ramdisk
Ramdisk
rakshakb said:
Yes, flash update.zip via fastboot adb sideload
Sent from my D2105 using XDA Free mobile app
Click to expand...
Click to collapse
Could you please tell me how to do that?
How flash hp 7 1301 official 4.2
You need. --
1-) computer
2-)update.zip of tablet (country wise)
3-)fastboot minimal pack.exe (Google it)
4-)tablet
After download files install fastboot minimal pack.exe in your computer. Now copy update zip in computer/c/program file/minimal adb folder. Now open tablet setting scroll down about tablet open it. Tap 8 time on build version . you see development option in setting open it and mark usb debging.now open adb fastboot in window. Conect tablet to compute via usb.enter ADB REBOOT RECOVERY press enter.-now tab is restart in recovery mode now select adb sideload in tablet recovery (use volume button and power button for ok). type in adb ADB SIDELODE UPDATE.ZIP. press enter. File will automaticlly send to tablet and install
Now tablet is official ..........
No success
Tried twice using adb sideload with the update.zip file.
Any ideas?
Solutions?
SkipWire said:
Tried twice using adb sideload with the update.zip file.
Any ideas?
Click to expand...
Click to collapse
Tried the steps set out by http://forum.xda-developers.com/showthread.php?t=2422353 with
no success.
The device can be rooted by enabling developer and select USB debug on 1301 device. Installing and running ADB and Impact applications in windows; .
When the device reboots it defaults to factory settings with no root.:silly:
Can you give me the link of hp 7 plus 1301 asian tablet?
please bro if you have the file give me its link
Anonymous222 said:
please bro if you have the file give me its link
Click to expand...
Click to collapse
SkipWire said:
Tried the steps set out by http://forum.xda-developers.com/showthread.php?t=2422353 with
no success.
The device can be rooted by enabling developer and select USB debug on 1301 device. Installing and running ADB and Impact applications in windows; .
When the device reboots it defaults to factory settings with no root.:silly:
Click to expand...
Click to collapse
rakshakb said:
You need. --
1-) computer
2-)update.zip of tablet (country wise)
3-)fastboot minimal pack.exe (Google it)
4-)tablet
After download files install fastboot minimal pack.exe in your computer. Now copy update zip in computer/c/program file/minimal adb folder. Now open tablet setting scroll down about tablet open it. Tap 8 time on build version . you see development option in setting open it and mark usb debging.now open adb fastboot in window. Conect tablet to compute via usb.enter ADB REBOOT RECOVERY press enter.-now tab is restart in recovery mode now select adb sideload in tablet recovery (use volume button and power button for ok). type in adb ADB SIDELODE UPDATE.ZIP. press enter. File will automaticlly send to tablet and install
Now tablet is official ..........
Click to expand...
Click to collapse
Guys, KITKAT is out for HP 7 Plus. I had successfully rooted the tablet on JB with no bootlooping issues but lost root when updated to Kitkat. Plz update your tablets and let us all work together in developing Custom ROMs and Recoveries.
Dom3616 said:
Guys, KITKAT is out for HP 7 Plus. I had successfully rooted the tablet on JB with no bootlooping issues but lost root when updated to Kitkat. Plz update your tablets and let us all work together in developing Custom ROMs and Recoveries.
Click to expand...
Click to collapse
Kitkat is available but it's flawed. Received "update -1" and left in recover mode until I rolled back.:silly:
SkipWire said:
Kitkat is available but it's flawed. Received "update -1" and left in recover mode until I rolled back.:silly:
Click to expand...
Click to collapse
No, it is not flawed. When you flash the zip the first time in recovery, it flashes your bootloader and recovery. Reboots into recovery again showing received update-1. Then choose the zip again. You have to do this 3 or 4 times. Keep on choosing the revovery zip again until it says completed.
Has everyone given up?

Cubot cheetah root

Hi guys,
anyone know how to root this phone?
root on Cubot Cheetah 2
https://forum.xda-developers.com/ge...bot-cheetah2-information-reviews-5-5-t3509666
I flashed TWRP, attachted as rar file. I did it like this:
http://forum.xda-developers.com/android/general/guide-clones-t3421539
Did you know that devices has build in recovery menu?!
It can only backup some user data for you
You can get into by pressing POWER and Volume+ for a few sec. while turned of tile boot.
Hold Volume + and press Power again.
***Do not press Volume down, it is "enter" in first recovery screen you maybe start fastboot or normal
***Volume + is for navigate in first recovery screen
Do not flash other super user as in thread... i did and had a heavy bootloop (;
hello
i cooked my 1st rom for a Cubot like this https://forum.xda-developers.com/showthread.php?t=1801690.
Then i flashed it with the recovery. As installation stoped i got a message: "no os installed do you realy like to reboot?!"
So i cancel process to restore systemfiles which i backed up befor. *
But now all system app are gone and recover them with Titanium backup doesn´t work well. I also got those files from stock image and maybe most by another backup by root explorer. What to do right now?
Try to install my rom again? Via fastboot? Or flashing a clean stockrom i don´t know.
I´m uploading Cheetah 2 rom i cooked since hours, it is ~2gb
Maybe someone can look into it
My pc is to slow to run a emulator to test it. That´s why i try flashing befor posting download link dang
stock rom:
CUBOT_6143C_CHEETAH_2_V02_20161027.zip https://mega.nz/#!VUc1TIjK!0FK1U5bt0NIL8RNEt-LkV-U5byVBroqV0PU92VzM5iE
http://forum.cubot.net/viewtopic.php?f=21&t=1176
other:
http://forum.cubot.net/viewforum.php?f=21
*did i just miss to wipe data .. i need some sleep ^o^
url to my rom
(part 1 /3) http://www.mediafire.com/file/0rwbkc84afgqd38/Cubot+Cheetah+2+6143c+V02+20161027+xda.7z.003
(part 2&3) soon here ~3hours+
HAPPY NEW YEAR
Do not install wip-rom.
This on your own risk:
https://www.mediafire.com/folder/5k0832h9u1cce/Cubot_Cheetah_2
Ok, after new installation and wipe partition my phone still alive
But all system app are missing! And no superuser!
toBsucht Psp said:
I flashed TWRP, attachted as rar file. I did it like this:
http://forum.xda-developers.com/android/general/guide-clones-t3421539
Did you know that devices has build in recovery menu?!
It can only backup some user data for you
You can get into by pressing POWER and Volume+ for a few sec. while turned of tile boot.
***Do not press Volume down, it is "enter" in first recovery screen you maybe start fastboot or normal
***Volume + is for navigate in first recovery screen
Do not flash other super user as in thread... i did and had a heavy bootloop (;
Click to expand...
Click to collapse
Thanks, but it didn't work for me...
Any other?
Do you use same firmware as me? That very importat!
What doesn´t work for you?
Are you in develop mode, enable debugging or connected as android bridge?
I flashed today TWRP to another Cheetah 2! But this super user installation blow my mind and device!!! Installed chainfire (2.52) as in linked thread made my phone hang on cubot bootlogo. Then i downloaded SR2-SuperSU-v2.79-SR2-20170103215521.zip and i pass the boot but now all system apps are gone again! Recovered it with my TWRP backup.
Thinking about retry 2.72 SuperSu which maybe was reason of bootloop on 1st cubot rooting :fingers-crossed:
Keep in mind to backup your whole system if you enter TWRP 1st time, befor installing SuperSu. Suggesting befor install TWRP make backup with stock recovery!
Maybe a video i made on that 2nd rooting procedure is helpful to you?
https://youtu.be/wqXhLF_WOKI
unlock bootloader
https://youtu.be/4dtMelJsGx0
I have cubot cheetah (1st edition). I Installed twrp, but it doesn't work. Touch doesn't work. Everything you posted, it's for 2nd edition.
Sent from cubot cheetah
I´m pretty sure boot into recovery is same as on Cheetah 2. I also believe you still not unlocked bootloader!
I Installed twrp, but it doesn't work. a) you did not Touch doesn't work. b) bootloader and stock recovery navigation via hardwarebutton TWRP via Touch
Click to expand...
Click to collapse
Do a websearch: "unlock bootloader adb" example
It is basicly same step as in ultimate MT6753 thread url = see me 1st reply
You just need fastboot.exe and your Cheetah running as adb device to install TWRP.
Make sure you got it installed Cheetah via ADB driver not as MTP device or else!
TWRP is same on cheetah 1 & 2 not 100% sure, maybe ask megathebest .
Alternative method:
adb.exe to unlock and
Sp flashtool with vCOM-driver installed
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
https://androidmtk.com/install-android-cdc-driver-manually
Some links for you but you don´t need those files at the moment:
Cubot Cheetah 1 ROM Download - PC Flash Files http://forum.cubot.net/viewtopic.php?f=21&t=1146
Cubot Cheetah 1 ROM Download - T Card Flash Files 2 http://forum.cubot.net/viewtopic.php?f=21&t=1025
http://www.needrom.com/category/cubot/cheetah-cubot/
--------------------------------------------------------------------------------------------------------------------------
Another method to install TWRP is via update.zip but if you have to unlock oem via adb (minimal adb fastboot.exe) why manuel flash it.
How:
Rename twrp.zip to XXX-stock-rom name-XXX.zip place it at you internal memory boot into fastboot by power and volume button.
Ya, there are loads of tutorial on the internet about TWRP 3.1.1 For Cheetah 2 which means root is possible for the device running the latest Android OS.
Here is a guide which has shared the latest TWRP 3.1.1 with rooting guide
tiringer said:
I have cubot cheetah (1st edition). I Installed twrp, but it doesn't work. Touch doesn't work. Everything you posted, it's for 2nd edition.
Sent from cubot cheetah
Click to expand...
Click to collapse
i had the same problem but was very easy coming out. just connect the otg cable to your phone since the handset supports otg functionality then use the pc mouse once you have rebooted into recovery mode. works swiftly!!!!

Categories

Resources