Related
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 ?
Help - I have an A1CS Fusion 5 tablet which I've managed to install CWM v6.0.3.1 but in the process of trying to install CM 10 or 9 I cannot get the tablet to boot into android, it always boots straight into the CWM recovery. This is common tablet which is identical to the Protab 2xxl which I've found a single rom image file but I'm unsure how to flash. I don't have access to a windows box to use livesuit as I hope there are equivalent Linux tools, but as a last resort I can borrow a win pc.
Within CWM I've tried to flash the CM 9 or 10 .ZIP which it claims to do successfully but it still boots into recovery. I've wiped all the data/cache/system/dalvik partitions many times before each install.
Through much fiddling I've found that I can gain adb access to the tablet whilst it is in CWM recovery mode, but I'm unsure what to do next? I've also found I can put the tablet into bootloader mode (black screen) and I'm able to read / write raw mem using rkflashtool, but I don't know how to split the single .img file or CM ROM .ZIP file into separate sections to flash each partition?
Although I'm fairly technical on Windows & Linux, I'm a newbie with Android so any help would be very welcome to avoid it becoming an expensive paper weight.
Thanks in advance
Andrew
Hope that sounds enough interesting to get you here
to my problem:
I have a Huawei MediaPad 10 Link+ and theres NOTHING out there for it. So i decided to make it on my own.
belive me theres no recovery or rom for this tablet.
i had a long journy so dont think this is my first problem
i dumped my boot.img, recovery.img and system.img
i used this tool to unpack my recovery modified it, repacked it and flashed it. but the recovery wont boot up. just stuck at the first mediapad logo.
Even if i NOT touch it. ( just unpack / repack )
my problem is not to restore it. i want a modifyd recovery. maybe sobody here can help me.
thanks in advance
PS: the best would be if somebody could port me CWM or TWRP
i tried to make it on my own but ubuntu says no and punchd me in the face
The Author of the tool stated, that it won't work on every device.
But if you plan to build cwm or twrp for your device, you will need ,sooner or later, linux.
So save yourself some trouble and time and install linux in a virtualbox.
It will make numerous things easier for you :good: .
Hi, I need help with my phone, I accidentally changed the permissions (using ROM Toolbox Lite) from the system folder making the phone crash shortly after. Now it shows the Alcatel logo and shuts off and back on in recovery mode.
I'm new with adb and CWM/TWRP stuff, but I can't find the device using adb (I installed the usb drivers correctly) , it only finds on sideload and even then I get "error: closed"...and with CWM/TWRP I can't use sideload because:
"You need adb 1.0.32 or newer to sideload to this devices" (and I used 1.0.36)
And with zip file (CWM) method I get:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted"
Please help, I can't find the stock rom for this phone
Did you find a solution? HAve a Bootloop too
Prestnaut said:
Did you find a solution? HAve a Bootloop too
Click to expand...
Click to collapse
Nope unfortunately
Any news ?
HAve a Bootloop too , after trying to unroot with kingo .
Need stock boot.img or recovery.img in order to build custom rom from source
VTRF8FF.TMP said:
Hi, I need help with my phone, I accidentally changed the permissions (using ROM Toolbox Lite) from the system folder making the phone crash shortly after. Now it shows the Alcatel logo and shuts off and back on in recovery mode.
I'm new with adb and CWM/TWRP stuff, but I can't find the device using adb (I installed the usb drivers correctly) , it only finds on sideload and even then I get "error: closed"...and with CWM/TWRP I can't use sideload because:
"You need adb 1.0.32 or newer to sideload to this devices" (and I used 1.0.36)
And with zip file (CWM) method I get:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted"
Please help, I can't find the stock rom for this phone
Click to expand...
Click to collapse
Hi, My 6044d also in boot loop, not rooted so I can't get stock boot.img or recovery.img in order to compile CWM and CM from source for this particular phone. Please someone post it and of course, when compiled I'll post back de results for all of us that need a custom ROM for this phone. It's crazy that this phone is not so popular and the common custom roms don't have one for it out of the box, that's why I decided to compile it myself, but I can't get my boot.img or recovery.img to configure build environment for this especific phone.
Thanks in advance!
miuserdexda said:
Hi, My 6044d also in boot loop, not rooted so I can't get stock boot.img or recovery.img in order to compile CWM and CM from source for this particular phone. Please someone post it and of course, when compiled I'll post back de results for all of us that need a custom ROM for this phone. It's crazy that this phone is not so popular and the common custom roms don't have one for it out of the box, that's why I decided to compile it myself, but I can't get my boot.img or recovery.img to configure build environment for this especific phone.
Thanks in advance!
Click to expand...
Click to collapse
Hey, sorry for taking so long to answer, i actually got 2 mega.co.nz links for this, another user gave them to me ^^
https://mega.nz/#F!XAkUDajB!EaYNGGsABPapaVFkeGNqTw
and
https://mega.nz/#!Ncx2VASY!gfxVbnQj9HK9WUGiidKY83pJZA7ToTQu5RFDfu2miWE
I found your other post too, and given that im a noob i tried to reply there, then i was trying to private message you (failed cause im not smart xD) and now im here :3
Tell me if something goes wrong, i didnt check this myself cause i sent my phone to repair, it was so broken they didnt knew it was rooted xD
Best of Luck ^^
And yeah, this phone is not popular at all, not even Alcatel cares, i emailed them to see if they were gonna release some updates, didnt even got a reply until now
But well, im gonna check out what youre doing, sowwie im a copycat xD
Good luck again ^^
I'm a little bit late but if you still need or someone else needs it just let me know as I have Carliv Touch and stuck recovery for this device.
Little late as well, but do you still have that recovery? i picked up my phone again and i wanna mess with it
Hi everyone. I recently bought an Alcatel 1t 7 (8067) tablet, 1Gb ram, 16Gb rom, just wifi (no 4G), mt6580 processor, android oreo go edition; a very simple and cheap tablet, but it seemed me a very nice one, because is slim and lightweight; worhty of root access, but also a custom recovery. I prefer TWRP recovery because it's more organized... ¡Anyway!... So I got down to work, but at first, as I didn't know how to backup all firmware, and when I learned how to do it and did it (esentially I could "tame" sp flash tools, hehe), I had already lost my original recovery file. Is needless to say that TWRP recovery, as far as I know, isn't available for this model, so I needed to port it, but as at first, I didn't know how to back it up, I overwritten it with other recoveries that didn't work. I mean, at this time, the tablet is working but is without recovery tool. I'm not going to talk about root access, because I already could get it, by using magisk manager, but I need my recovery image file, back; both to reinstall it and port it to TWRP.
So finally, if anyone has this stock recovery file, the full stock rom for it, or even better the ported TWRP for this tablet, please share it to me.
Thanks in advance for your attention.
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
aIecxs said:
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
Click to expand...
Click to collapse
Thank you for reply. Ok, I booted android. I have enabled usb debugging so, when android booted, I connected it to adb, and opened "adb reboot recovery" command, to be sure that android would reboot into that mode; but it didn't, it just rebooted several times on boot screen, and when it "got tired" of rebooting, it booted into android. Didn't boot into recovery, so I guess, It didn't repair it.
PS: I was looking for that file "recovery-from-boot.p" on that path, and there isn't such file, i can't find it.
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
you can port TWRP with kernel from boot. you can use this TWRP as base
aIecxs said:
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
Click to expand...
Click to collapse
¿Must that file have the same size that the original recovery image? Because the only file named recovery that i can find on that path is named "recovery-resource.dat" and its size is 807kb, and as I have seen before, is that recovery images have several Mb of size.
aIecxs said:
you can port TWRP with kernel from boot. you can use this TWRP as base
Click to expand...
Click to collapse
Two questions about it; as far as I can remember twrp image must be compatible not only for the same chipset, but the same screen resolution ¿Am I right? Also, this tablet is 600x1024 px, or 1024x 600 on landscape mode. All TWRP that I have installed on former machines, worked on portrait mode, so I wonder miself ¿Could TWRP also work on landscape mode?
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
aIecxs said:
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
Click to expand...
Click to collapse
Ok... I can find that file on my tablet, but I'm not so skilled android user, as for rebuild recovery from that file or even port TRWP from that file, so ¿Is there an easy way to do it ( or at least, comprehensible for middle skilled android users) ? ¿How? (and supposedly this machine is easy to port and root, they say on internet. I also have a huawei y7 2018 for rooting, that seems harder to root. But that's a another (my next) struggle in here, hehe)
aIecxs said:
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
Click to expand...
Click to collapse
Another question. ¿Are those programs who claim to help to port TWRP with just some clicks, reliable? (for instance TWRP porter for mediatek)
aIecxs said:
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
All the TWRP recoveries that i have ported before, have had a working touchscreen, but as I understand, resolution requirement is not only for touch calibration, but for correct displaying of TWRP GUI (that all buttons and options fit on the screen), Now I've read that new versions of TWRP adjust automatically to any screen resolution, ¿Is that right?
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
HCU-client needs 4 credits for Huawei.
I may reply in new thread.
aIecxs said:
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
Click to expand...
Click to collapse
¡No, man! If TWRP porting is kinda hard having the stock recovery image, without it, is a brain smashing task (or at least for me). I mean, I really don't understand well, how to port twrp starting only with boot.img, I mean, without recovery img. I've saw tutorials about the use of carliv kitchen (windows version), and seems easy, but all tutorials are made with stock recovery.img available, not with boot.img. So, what can I do there?
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
aIecxs said:
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
Click to expand...
Click to collapse
I saw a tutorial about. It said that I must to unpack stock recovery and twrp recovery, and replace some files of unpacked twrp recovery, with respective unpacked stock recovery files, and edit some files on twrp unpacked folder, and finally repack it.
Until that point, I assume that it should work, I mean, having stock recovery. But I did that, but using boot.img, I renamed all boot resources, to recovery, for instance, boot.imgkernel to recovery.imgkernel; and replaced it, repacked it, and reflashed it, but nothing happened, I mean, it didn`t want to boot into recovery. It`s interesting to "experiment", but I`m gonna try to find its original stock recovery, to at least get it back.
Hello!
I would like some help, alcatel 1T7" 8086 no4g I likely bricked it. There's nothing else than a black screen. The tablet doesn't react to anything. The computer finds it as unknown USB tool. No visibilty is shown. What can i do with it,for it to work? Or should i just put it in the trash?
Thank you for the reply.