Related
I flashed Taboonay 2.1 to my Icona Tab A500 last night. Everything was great. I retrieved all my usual apps and previously purchased apps back down from the market, network was working fine. Turned on tab this morning and it is unable to connect to wifi. Keeps trying several times and then says the attempt has been disabled. It sees the Motorola Surfboard but can't connect. I thought I would try to re-flash since the .zip was still on my external SD. I attempted to boot into CWM but it won't come up. It just says loading image and never goes into CWM, that's it. So, I have no ability to connect by Wifi and am unable to download Acer Recovery Installer in order to re-install CWM. Apparently the CWM image is corrupt. The CWM ROM Manager Premium is still on my desktop but it can't do any sort of recovery because if I bring it up and choose "_install .zip from SDCard" it reboots into recovery mode and can't load the recovery image either. Does anyone have any ideas? Taboonay 2.1 is Android 3.2 it has the xda ad hoc wifi patch in it (which has never been quite right) in my opinion. So I found a copy of the 3.1 wpa_supplicant file and installed it into the /system/bin folder using root explorer to set the permission correctly after renaming the one installed by Taboonay to wpa_supplicant.old and re-enabled Wifi. Still it would not connect. The only difference I could see was that it no longer could see ad hoc wifi networks but still would not connect to my infrastructure wifi although it could see it. This particular wpa_supplicant file that I went back to came from Acer 3.1 stock ROM and worked perfectly under 3.1. I'm basically out of business at this point with no network and no way to flash a new ROM or restore a backup. Does anyone have any idea what to do next. Has anyone else had wifi issues with Taboonay 2.1? I did see an update 2.1b for Taboonay 2.1, but I can't get into CWM to apply it. I might as well be totally bricked. I can connect to the tablet and have full access to the 2 SD cards via Windows and a USB cable, but I can't download Acer's Installation Recovery from the market from a Windows browser. I'm sure its not the router because 3 Windows 7 SP2 Computers can connect to it and so can my wireless HP printer. Everything seems to be a Catch 22. Help! Anyone had trouble with Wifi on Taboonay? Does anyone have any ideas or how to get out of this situation? Any suggestion would be appreciated.
Hey gradyzero sorry to see the trouble buddy but the tabooney 2.1b update is made for wifi updates issues and SU perm, im currently running tabooney 2.1b and full with new market and i have no issues. As far as the recovery have you tried new THORS 1.5 cwm can you try using adb to push recovery.img to the tablet, or maybe using terminal emulator theres a new 1.5 cwm update you can try doing that. just extract recovery img to internal sd and go into thors website "google it" and follow every step except for #3
good luck buddy if not hit me up side PM ill see what i can do atleast to try to get recovery back
I don't think I had restored the terminal program back yet let me check. The apk is something I haven't tried. Thanks for the suggestion. I have thor's 1.5 update on my SD card but not quite sure what use it can be until I can get the ability to connect to boot up in recovery. I'll go to his web site and read the instructions there again, overlooking step 3. I have read them once before but didn't have this problem so I just grabbed the download and planned to update it after the Taboonay flash. Figured it would just have to be redone after the flash anyway. Thank for you idea. I should be able get an .apk onto the SD from Windows and should be able to install it. Again, thanks much buddy. I'll post back to this thread what the outcome is.
Restoration of boot image doesn't resolve the problem.
Okay Crashpsycho I download an Acer Install Recovery apk and CWM Launcher 1.0.0.0 apk. Both appeared to install correctly. Acer Install Recovery came up and I was able to choose to install CWM 1.3.4 image. However, when I reboot into recovery I still stop at "Booting recovery kernel image". So reinstalleing the CWM 1.3.4 image that the Acer Install Recovery show as an option didn't fix anything. Any ideas about why recovery might stop when loading the kernel image? When it says "the Kernel Image" is it talking about the base Linux kernel? I seem to recall reading somewhere that Taboonay replaced the Linux kernel with its own version. Is that true? I thought maybe the recovery image was corrupt but assuming the Acer Install Recovery really did reinstall the recovery CWM 1.3.4 image as it said, then something else is wrong. I did manage to get a terminal program installed so I'll try your second suggestion to force the CWM 1.5 image using adb. If Taboonay really did replace the stock Linux kernel, I have no idea how to recover from that. I'm not quit sure exactly where a recovery image goes and so I suspect that adb will ask for the destination. Maybe I'm wrong but do you know? Does adb know automatically where to install a recovery image? If the Linux kernel has to be replaced then I could get bricked if Tabtoonay won't boot up because a different Linux kernel is installed. What is your thinking about all of this? This is getting heavy. Thanks again for your help. Anyone else that has any fresh ideas is encouraged to jump in here and post to this thread. I'll post back here with the results once I try to force the CWM 1.5 image.
Installing other kernel solved issues for me, using thor kernel 3.5
installing 1.5 use terminal emu, extract the recovery.img from zip folder and place on root of sd go to thors website tegraowners and follow all steps except #3 and that will force 1.5 to tablet. have you tried installing stock recovery image using the acer recovery app
So Sector51 are you telling me you had the same issue. Where booting into recovery locked at loading kernel image? I'll try your suggestion. If it doesn't require you to be able to boot into recovery which I can't. Thanks for the tip.
Crashpsycho, I just completed the terminal method you suggested and followed all the instructions except #3 wihch was a mount, if I remember correctly. I extracted the image file from Thor's 1.5 put it on my external SD by copying it from Windows and then went through Thor's instructions step by step. Recovery boot still hangs at loading kernel image. Thor actually says to install itsmagic into /data/local directory both in his adb push and in his terminal emu methodology. There is no copy of itsmagic in his distribution and I can't find such a file on my tablet. BTW, I also tried the adb push from Windows but the recovery image is pushed to the SDCard so I assume he intents for me to then boot into recovery and to install it. So that's not going to work unless I have itsmagic. The Windows adb method also pushes itsmagic out to the /data/local folder but I can't complete that part and I think it is critical to both methods. Any idea where I get this file? Google search returns nothing except that one entry has been removed due to copyright issues. I think that it is the key to installing from the SDcard. I remember seeing that file on my rooted 3.1 but apparently Taboonay removed it. Can you enlighten me on itsmagic? What is it? Where do I get it? I have currently installed the Stock USA 1.31.06_COM_GEN1 recovery in Acer Recovery but reboot into recovery still hangs at loading kernel image.
This is another side issue but do you know if it would be possible to install the Taboonay 2.1b manually. Is it an update zip or a ROM flash? I'm beginning to think that if I could get back my Wifi back I would just forget the recovery reboot as a last resort. I'm going to investigate what is involved in the kernel update suggested by Sector51. But basically I'm not doing anything else until I can fully complete thor's 1.5 update. Man, I've spent 3 entire days trying to resolve this. I'm going bonkers. It certainly gives me a bad taste for Taboonay that probably isn't deserved because I don't see other post about this particular issue. So please educated me on itsmagic and we'll go from there. Thanks dude for all you help.
I found a copy of itsmagic here on xda. Downloaded it and completly went through the terminal emu process exactly as posted on Thoor's Website for 1.5. Everything seemed to work this time including the execution of itsmagic which spit out a nasty message to Acer something about Its Magic. Acer why did you say the bootloader is locked when it isn't? So this tells me that everything should now be good. I rebooted into recovery and this time it acted a bit different. It still said loading boot kernel but then in about 30 seconds rebooted back to Taboonay automatically. So I'm stumped. Does anyone have and new ideas? BTW, the 1.5 recovery image has a date of 29 Feb 2008. Is that right?
Finally suceeded with 1.5 Recovery, Thanks
This message is specifically addressed to Crashpsycho and Sector51. After four attempts I was finally successful at getting Thor's 1.5 recovery booted. I immediately backed up the current version of Taboonay 2.1 and then applied the 2.1b update. Everything in term of recovery is now good. One problem, the update did not fix the the WiFi problem as I am still unable to connect via WiFi. But that's a totally different issue, which I can deal with. Meantime thank to both of you for generously taking you time to help me resolve this recovery boot problem. I would still like to know what I did wrong during the original ROM flash to Taboonay 2.1 to destroy itsmagic. As well as what I did wrong in my first 4 attempts at repairing the recovery. However, I won't dwell on that as I need to proceed on with working on the WiFi issue. Thanks a million to both of you for all your help and suggestions. You are both what makes xda a truly wonderful and unique place for lovers of mobile devices. I am a programer and web developer and I hope I can contribute eventually to the growing Android mania. I personally think it will eventually dominate the table and phone market, if it already hasn't done so retail wise. I'll return to lurker stats for a while and learn more about the SDK while I try to resolve the WiFi issue. One side note, I recently flashed my HTC HD2 phone from Window mobile 6.5 to Widows mobile 7.5. That involved the flashing of 3 ROMs and then upgrading the OS. It runs beautifully and was much more complicated than what should have been a relatively simple task of upgrading to Taboonay 2.1. I'm sure I missed some small detail that caused the problem with the Icona Tab. You guys helped me greatly and I hope to be able to return the favor at some point. So I consider this issue closed and the moderator should feel free to consider it resolve. xda is power to the people.
Final Note: The adb push from Windows was the last attempt and was apparently the one that successfully fixed everything. As a certified Unix Engineer and somewhat of a Linux expert I opted to use the terminal emulator technique since I knew the commands and what they were doing, but typing in a long stream of commands is always more prone to user error. My advice to anyone else with this problem is to install the Windows Android SDK and use adb push to update as it appears the most recent version takes care of most all the permission issues and is almost fool proof. Again thanks to you guys. The Problem is resolved. Mister Moderator consider this thread closed and resolved.
great job man atleast you got the recovery to work. i cant say much for the wifi issue or what happen to recovery i would say if anything the issue must have came from the wifi ad hoc patch/change but im not fully technically skilled to say that it really was but great job hope you get it back up and going
I am enbrased to admit this but I feel it only fair since so many people attempted to help me. I've search around and apparenty no one has run into this here yet, but it needs to be posted for future reference. Most all of my boot recovery issues took place while the tablet was docked in the Acer A500 docking station. When I have trouble in recovery mode, with the image loading message just hanging up, 100% of the time removing the tablet from the docking station resoves the problem. Just thought I should pass this on. I know it is stupid that I didn't realize this before now. If you are docked, don't boot into recovery' not even with1.5 installed. I have no idea why this is true, but it is. If you have the Acer docking station DO NOT BOOT IN TO RECOVERY WHILE DOCKED!
Open up Rom Manager and click "Fix Permissions" let it do its thing then restart. That worked for me.
i am getting the tablet later this week. And since its the same as the advent vega i am hoping to flash a custom rom that supports market and .. well.. better..
i have rooted my HTC Desire Z. But i needed a guide. i guess i need the same with this project.
could someone help me out with something like that. atleast a point in the direction of how..
thanks
Well the way I found the best and easiest for me was to root it with Z4 root (you can find it easily here on XDA forums). It supports Advent Vega tablets and it worked for me like a charm... rooting was done in seconds.
Prior the flashing operation I recommend you to purchase ROM Manager app and use that for the installation of clockwork mod and later for flashing custom ROMs as it is the easiest and most safe way IMO. I'm having this tablet for two days and I've already flashed several ROMs using that way. Of course, I highly recommend you to backup your current ROM just in case. And guess what... you could do that too using the same app
Happy flashing and enjoy your tablet. It's great value for money!
It's reallyyy simple! I did it myself last week with the PoV Mobii..
- First, shut down your tablet.
- Download the recovery mode drivers for your tablet here: http://www.myadventvega.co.uk/SystemUSB.zip
- Extract the files to a folder on your pc.
- Now, connect the tablet to the pc with USB and bring the tablet in recovery mode:
1. Hold the back button 1 second.
2. Press the power button 1 second, but still hold the back button as well
3. Hold the back button 1 second more.
- Now, go to Configuration Panel -> Device Manager, you'll see a device called APX
- Click to update the APX Device drivers with the drivers you extracted a few steps before.
Now the tablet is ready to flash..
Download an arbitrary rom, (I have this one: http://forum.xda-developers.com/showthread.php?t=1221336, search this topic for the exe-version of the Build 9 without updates) and execute the file. The tablet should be updated when finished..
please ask questions in the general section. This is for development only. Thanks!
Mods please move this to general.
Take it easy.
cant seem to find the exe version without updates.
unless its the one mentioned in the first post:
And the last file:
Download VegaComb HC3.2 9b Installer.exe HERE!
This is a windows installer for the 9b Full ROM, you don´t need to install ModdedStock before, it makes it all for you
Click to expand...
Click to collapse
Can vegacomb be installed through ROM maneger?
krankdroid said:
Can vegacomb be installed through ROM maneger?
Click to expand...
Click to collapse
No. But you can install 9n throught CWM. Just remember to flash modded stock v2 first.
Firstly: Copy the main build and update file(If available) to the memory card inside the tablet
Make sure the main build is in the following format "Build.Zip",
Make sure the "Update" is in the following format also "update.zip"
1) run first nvfalsh Modded Stock v2,
1a)Boot-up and conplete installation, Reboot Twice
2)Now select Recovery in Applications
2a)Once you are in recovery, wipe Data, Cache and Dalvik. Select Fix Permissions.
3)Now select Install Main Build zip file form SD card
3a)Select Choose zip file from SD
3b)Select the Build 9n zip file
3c)Wait for it to complete installation and re-boot.
4)Boot it on and power down a few times to make sure it works.
5)Use the shut-down Menu to select Recovery.
5a)Tablet switches off and tries to boot-up, but hangs with a backlit screen.
5b)Press the Power button for 6 seconds to completely switch off the tablet.
5c)Press Power button to boot-up and wait patiently - CWM recovery WILL start.
6)Now select Update file from your SD card
7)After Install,Re-boot
Hi,
I try to downgrade my current A500 on HC 3.2 to 3.01 with any success.
I follow to tutorial based on "Vache" tips available at http://forum.xda-developers.com/showthread.php?t=1276227
I have done all the step, but when i launch PBJ20upgrade.exe as administrator, it ask me to plug again my iconia, it display the current installed version and version who will be replace, click on "Next" button and... progress bar doesn't move.. the iconia switch off (black screen). I have try many times and always the same result.
My current configuration is :
Kernel : 2.6.36.3+ - build : Acer_A500_7.006.01_COM_GEN1
My computer is on Windows 7 64bits.
Any ideas ?
Have a nice XDA Christmas.
Method 1 can take up to 10 minutes or longer to get action. Perhaps you didn't wait long enough.
Try Method 2. It's even easier.
Not sure if it matters, but set your USB Debugging to on. Settings/Applications/development
USB Debugging is set to on.
When you said "Method 1 can take up to 10 minutes or longer to get action." it's mean before seing the progress bar moving ?
In any case i will check method 2 but just a little bit afraid with the " gives errors and crashes but you only need it to root and install CWM"
One small question, with STEP 2, it will replace the current HC 3.2.1 by an unstable 3.01.
Let imagine after the procedure (root + CWM) i would like to put a ROM STOCK as my iconia was delivered, i think it's possible no (and where to find it because i have no img of my current version because not rooted).
And if i do it (install rom stock) it will be updated to HC 3.2.1 with OTA no ? Root and CWM will be lost again in this case ?
Thx for reply.
aranna said:
USB Debugging is set to on.
When you said "Method 1 can take up to 10 minutes or longer to get action." it's mean before seing the progress bar moving ?
In any case i will check method 2 but just a little bit afraid with the " gives errors and crashes but you only need it to root and install CWM"
One small question, with STEP 2, it will replace the current HC 3.2.1 by an unstable 3.01.
Let imagine after the procedure (root + CWM) i would like to put a ROM STOCK as my iconia was delivered, i think it's possible no (and where to find it because i have no img of my current version because not rooted).
And if i do it (install rom stock) it will be updated to HC 3.2.1 with OTA no ? Root and CWM will be lost again in this case ?
Thx for reply.
Click to expand...
Click to collapse
No Problem. Remember, sometime, systems will reboot. And sometimes, you have to wait. I cannot tell you that this is happening with your case. But, it is best to wait some time.
Both methods, I believe, will give you an unstable version of 3.0
Yes, both methods, will replace the current operating system. But, between errors, it will allow you to run the iconia root, and run the acer recovery. I don't think anybody has failed to do this, except for idiots who can't follow instructions.
I would suggest you download these, and put them to SD before starting the procedure. It saves having to get them from the net. Also, go ahead and download a rom you want to try. Might as well do all things at the same time.
True, basically, you will be without a stable recovery. Which is why, after you install Acer recovery, and install the recovery part, it is necessary to make a backup of the current system. Better an unstable one, than no system at all
Then, do your boot to recovery, system off, hold vol- and pwr till you see the text in the top left corner, then release.
Nav is by the vol - and +. Pwr to select an option.
Wipe;
1. User data
2. Cache Partition
3. Go to Advanced, wipe delvak cache
Go back to previous screen, and select Install From Zip, choose zip to install, and select your rom
Wait 10 minutes or so.
Now, when the rom boots, and it will, if you get several error mesages, then, you should reboot to recovery, only this time, goto mounts, and format the partitions. Usually, you don't have to do this. But, sometimes, traces of the opld rom remain behind. But, I think you will be ok with the previous procedures.
And, you're a good boy, as you ask questions before you do things
Spasibo bolchoï
Hi again,
Sorry but i have a stupid question. Based on solution 2 for downgrading (by using a SD card) if it's so simple why we don't use it to flash any ROM like Thor or Tabonnay ? just by placing the "update.zip" file on the SD card and boot on recovery stock ROM.
I understand that "rooting" a tablets allow to have full access on it (all partition) but why it's necessary to replace recovery tools by CWM ?
Sorry for this stupid questions but i love to understand what i'am doing.
Hi again, so i have done the downgrade with step 2 but have some issue.
V 3.0.1 is installed and iconia root 1.3 too
concerning "itsmagic" where to get it (when i should put adb push itsmagic /data/local)
Second, for the second part of tutorial http://forum.xda-developers.com/showthread.php?t=1126364, i need to type some bash command on the tablets, but how to ?
aranna said:
spasibo bolchoï
Click to expand...
Click to collapse
пожаловать
---------- Post added at 04:40 PM ---------- Previous post was at 04:38 PM ----------
aranna said:
Hi again, so i have done the downgrade with step 2 but have some issue.
V 3.0.1 is installed and iconia root 1.3 too
concerning "itsmagic" where to get it (when i should put adb push itsmagic /data/local)
Second, for the second part of tutorial http://forum.xda-developers.com/showthread.php?t=1126364, i need to type some bash command on the tablets, but how to ?
Click to expand...
Click to collapse
Easier to download Acer Recovery from the http Market, and install it on your tab. Then flash the Thor Recovery.
---------- Post added at 04:48 PM ---------- Previous post was at 04:40 PM ----------
aranna said:
Hi again,
Sorry but i have a stupid question. Based on solution 2 for downgrading (by using a SD card) if it's so simple why we don't use it to flash any ROM like Thor or Tabonnay ? just by placing the "update.zip" file on the SD card and boot on recovery stock ROM.
I understand that "rooting" a tablets allow to have full access on it (all partition) but why it's necessary to replace recovery tools by CWM ?
Sorry for this stupid questions but i love to understand what i'am doing.
Click to expand...
Click to collapse
To make a long story short, it won't work.
Basically, the OTA updates have a special script to run, also, they update the bootloader of the tab, which of course is more or less off limits to use poor people Not to mention the updates are "officially signed" by acer, to allow this method. And I am just guessing on this, but probably pretty close.
Anybody else have anything to add?
I suppose, a lot of time could be invested in creating a custom rom using this method, but it seems more simple to use the "recovery" method.
So it's mean that i don't need CWM and itsmagic but just "Acer recovery" ? i can cancel this part on STEP 2 ? :
5. then install CWM from thor's site (there you can find the latest version) or use Acer Recovery Installer from the Market, or look at the original thread here
6. Boot into CWM and flash whatever ROM you like!
The main problem with the market, i can connect but each time i use the tab keyboard i get an error message as describe on the unstable HC 3.01, is there a way to have an APK version (i can upload it on my microSD card).
Thx a lot.
aranna said:
So it's mean that i don't need CWM and itsmagic but just "Acer recovery" ? i can cancel this part on STEP 2 ? :
5. then install CWM from thor's site (there you can find the latest version) or use Acer Recovery Installer from the Market, or look at the original thread here
6. Boot into CWM and flash whatever ROM you like!
The main problem with the market, i can connect but each time i use the tab keyboard i get an error message as describe on the unstable HC 3.01, is there a way to have an APK version (i can upload it on my microSD card).
Thx a lot.
Click to expand...
Click to collapse
Yeah, that keyboard is a killer and causes a lot of issues. I heard where if you mess around with the keyboard settings (a lot), it will actually settle down and work with few errors (but looks bad)
Yes, skip the adb stuff
Use your computer to access the android market web site. Search for acer recovery
Download, put it on your sd for your tab, and install it using any file manager app. Then start the app, and install the Thor Recovery. You can get Thors recent recovery later, so it's not necessary right now.
Acer recovery is a tool that makes it easy for people who do not know how to use adb.
If you can't get it done that way, then you'll have to use adb.
The directories specified in the commands, are the locations they will push the files to. The img to the sd, and the it's magic to /data/local
Never used it myself, so I am not so sure where you are supposed to place the files to begin with. I would guess in the same directory as adb.
Thx for help, when you said "Then start the app, and install the Thor Recovery", Thor Recovery is included on the A.R.I apk file if i understand well but not the last version.
2) I donwload a ROM like TABOONAY or THOR on my microSD card
3) Just after, i reboot on recovery mode by using A.R.I
4) From CWM i select the image located on my microSD card to flash my tablet
right ?
aranna said:
Thx for help, when you said "Then start the app, and install the Thor Recovery", Thor Recovery is included on the A.R.I apk file if i understand well but not the last version.
2) I donwload a ROM like TABOONAY or THOR on my microSD card
3) Just after, i reboot on recovery mode by using A.R.I
4) From CWM i select the image located on my microSD card to flash my tablet
right ?
Click to expand...
Click to collapse
Ok, AFTER, you run the acer recovery, install, start app, and install the recovery. Should be the only choice you have
After it does it's thing. Then power off. Then, hold Vol - then PWR button, until you see text in the upper left corner of the tab, then release both buttons.
It will boot to the recovery menu.
Now, it's ok to copy the rom you want to use to the sd before doing all this. No problem.
With Taboonay, I would look at the procedure, as I believe you have to have 2.1 installed first, before upgrading to 2.2. (not sure why he decided to do it that way. Seems like a pain in the neck. I used to run 2.0 for awhile.
Harkon, is also a nice smooth rom.
Thor's V14 is also good (a500 only)
Then, very important. When you boot to recovery, go ahead and make a recovery image of your current rom (yeah, so it's unstable). Always most important to do this, as sometimes, a flash can go bad. Not often, but, better to have a recovery image to go back to, even if it's unstable.
Next, do your 3 wipes. No, not the toilet
1. User data
2. Cach partition
3. Go to Advanced, then dalvek cache.
After it's done, then, you can go back to the main menu, and select Install zip from SD
Then select your rom.
It takes awhile, so have a beer
And ... MAKE SURE you have at least 60% charge on your tablet!!! Before doing things.
People forget, and,,,, it ain't pretty...when your tab shuts down in the middle of a flash.
Nice, totaly clear for me right now. Many thx to you
And to finish, 3 last question (next beer will be paid by me of course )
1) If right now, at my current step (only donwgrade done to 3.0.1 at this moment) i do a factory reset on me main menu of my tablet, what version i will have ? Current unstable version or my previous HC 3.2.1 ?
2) When you said "Ok, AFTER, you run the acer recovery, install, start app, and install the recovery." by install the recovery you mean CWM provide on the A.R.I, there is a special menu on ARI to install it or it will be installed automatically during ARI APK installation ?
3) When you speak about "and select Install zip from SD" the ROM should be on the internal memory of the tablet or on the external (microSD card) ?
One thing that i don't understand yet is the internal structure of the partition on the tablet. As i understand, for the moment i just made a downgrade from HC 3.2.1 to 3.0.1, but we have the possibility to do a factory reset, so i think when we do that, the iconia will restore an img file or iso file from a specific partition.
So if i understand, on my current state, if i do a factory reset as usually, the HC 3.2.1 will be replaced no ?
In any case, thx a lot for time spend by you to explain me all this... this is the Russian POWER
aranna said:
Nice, totaly clear for me right now. Many thx to you
And to finish, 3 last question (next beer will be paid by me of course )
1) If right now, at my current step (only donwgrade done to 3.0.1 at this moment) i do a factory reset on me main menu of my tablet, what version i will have ? Current unstable version or my previous HC 3.2.1 ?
2) When you said "Ok, AFTER, you run the acer recovery, install, start app, and install the recovery." by install the recovery you mean CWM provide on the A.R.I, there is a special menu on ARI to install it or it will be installed automatically during ARI APK installation ?
3) When you speak about "and select Install zip from SD" the ROM should be on the internal memory of the tablet or on the external (microSD card) ?
One thing that i don't understand yet is the internal structure of the partition on the tablet. As i understand, for the moment i just made a downgrade from HC 3.2.1 to 3.0.1, but we have the possibility to do a factory reset, so i think when we do that, the iconia will restore an img file or iso file from a specific partition.
So if i understand, on my current state, if i do a factory reset as usually, the HC 3.2.1 will be replaced no ?
In any case, thx a lot for time spend by you to explain me all this... this is the Russian POWER
Click to expand...
Click to collapse
1. Do not do a factory reset. Honestly, I do not know what will happen at this point.
2. The Acer recovery, comes with Thor's recovery program. I think, that is the only one that comes with it. Technically, you can use it to flash roms, but, I advise using the recovery built into the tab afterwards. Usually, this program will go away after flashing a rom.
3. Always in the "root" of the SD (the first file you see when you look at your sd with a file manager).
4. If you're in Moscow, I will take that free beer
Not sure exactly what will happen when you do a "factory reset" I would suspect, the same OS your device came with, but I really don't know. Never had to do it. And, I see a lot of issues when other people try it.
so, today i have installed Rom Stock, Thor and Taboonay... all those has been tested and at the end Taboonay has win (Thor is pretty good but the fact that tab is detected as ASUS is not so good for me).
Many many many thanks to you Moscow Desire for you help concerning this, all is ok for me right now and more clear.
last question, if i want to update current version of CWM (provided by ARI) how to do it ?
I have download "update-recovery-thor2002ro-rev1.3.4.zip" i think i should use CWM itself (on recovery mode) to update it ? right ?
Have a nice christmas !!!!!
Good work. Glad things worked out for you!
I've been lazy, and haven't upgraded my recovery, but I believe you just place the Thorupdate.zip on the SD like you did with Taboonay, and boot to recovery, and flash just like your rom. But really, I haven't done this yet. Maybe this weekend.
Shouldn't be any need to do wipes.
Also, if you want to run a different Kernel on Taboonay, Then you need only to wipe Delvik cache before flashing it.
Merry X-Mas to you as well, but here, we celebrate New Years.
I know it for christman, i work sometime in Russia (near Moscow). Normally for you it's hollydays since yesterday, very lucky people in Russia.
Happy new year to all XDA members !!!!
FYI - if you do a Factory Reset with the unstable 3.01 rom installed, it puts the CURRENT OS back on, this being unstable 3.01. You have COMPLETELY replaced the other OS. This will happen whether you are running a custom OS, or official OS.
You can only have one OS on your tab at a time, unless you do the dual boot but that opens up a whhole new can of worms...
Hi, this is just a recompilation so that people don't have to get confused and scared.
Before your read this, please understand that this happened because of my own stupidity at somehow managing to delete the /boot from recovery 5.5.0.4, and caused a BLUESCREEN. When I tried to go to recovery, it went back to a pink screen. There were also other issues, such as a corrupted internal sd partitioning (warning, please be careful about doing partition, i highly recommend a proper partitioning zip which i'll link later in the post). In the end I was able to revive from the soft brick, and continued on to reinstall CM10.1 (it was version 7 at the time of the crash)
OKAY, let me repeat. Probably at this point you have a phone that has bricked. But if you can access PINK SCREEN, you're in luck (EVEN IF YOU DO NOT HAVE USB connection, its fine, as long as your EXTERNAL SD CARD is still accessible, physically.)
I'll put the stages in below:
WARNING I am not responsible for any loss, damage, or earthquakes or whatever crap that happens. Do this at your risk. Before you proceed, PLEASE OPEN THE BATTERY AND LOOK INTO THE BACK OF THE PHONE AND MAKE SURE IT SAYS MODEL: U8800 NOT U8800H, NOT U8800PRO. THIS IS FOR U8800 (okay, I admit i'm using U8800H but this is just an exception, probably)
PREPARATION:
STAGE 1: Getting the PINK SCREEN and booting into 2.2 Froyo / 2.3 Gingerbread
STAGE 2: Getting the TOUCH RECOVERY / CLOCKWORK RECOVERY, ROOT and SUPERUSER into the phone.
STAGE 3: Flashing the recovery, the partition, and the firmware
STAGE 4: Miscellaneous
PREPARATION
Click to expand...
Click to collapse
There are a few things that you need to prepare before hand.
1. A working computer (in this case i use windows)
2. Huawei USB drivers for windows. http://www.mediafire.com/?5z6i5cv8l6br292
3. Huawei Gingerbread base 528 ROM (this is BOOTLOCKED but don't worry, we can fix it just read up)
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDEyNTU=
4. BLEFISH's "get back your pinkscreen" zip file (to be used with item 3, listen!) http://forum.xda-developers.com/showthread.php?t=1457490
5. Super One Click http://www.multiupload.com/9AJDSU1Q11
6. Blefish's recovery.img for the CLOCKWORKMOD recovery
7. Forumber's PARTITION.ZIP (the better option thus far) http://forum.xda-developers.com/showthread.php?t=2145187&page=124
8.. A ROM OF YOUR CHOICE (http://forum.xda-developers.com/showthread.php?t=2166353) as for me i'll just wait for Blefish to release his version of JB / CM re-write.
Now we're done, let's proceed
BEFORE YOU BEGIN:
*credits to forumber2*
Forumber2 wrote in one of the responses (not in this thread) that caught my attention. Apparently, if you're using a B158 bootloader, you can still access the STORAGE if you remove the battery and plug in USB for 1 minute.
forumber2 said:
In Blue screen,connect your phone to PC and wait 1 minute. A storage will show if you was in B518 bootloader. If the storage shows,please report here
Click to expand...
Click to collapse
I am not sure what steps to take this (it is a new information for me) but I presume you can immediately restore the TCRW from there. Have to ask forumber2 though.
STAGE 1: Getting the PINK SCREEN and booting into 2.2 Froyo / 2.3 Gingerbread
Here are the steps.
1. Install the HUAWEI drivers for the phone, and also SUPER ONE CLICK for windows.
2. Take out the U8800's EXTERNAL SD CARD, and plug it into computer. (use a card reader if you don't have)
3. open (UNZIP) the downloaded OFFICIAL GINGERBREAD ROM. Inside it should be a manualand a folder called "STEP 1", and inside folder "STEP 1", another folder called "DLOAD".
3a) COPY the "DLOAD" folder (and its content) and place it into the ROOT of your EXTERNAL SD CARD. that means from your computer it should read like this: (when you navigate)
X:/EXTERNAL SD CARD/DLOAD/UPDATE.APP
(X is the name of the drive)
4. Unmount the EXTERNAL SD CARD, and then slot it back into the U8800 phone.
5. Pull out battery.
6. Stick USB into the port, and into computer. (WITHOUT THE BATTERY)
7. PRESS VOL+,VOL- and POWER together (Reboot into pink screen)
FIRMWARE UPDATE PROGRESS. it should be 1/2 then 2/2.
"Do Not turn off the device".
AFTER finishing step 4 (it takes some time)
there will be a "TICK" and it will say "RESTARTING".
QUESTION What if I can't? It doesn't work?
ANSWER There's another trick. Pull out the battery, plug the USB wire in (YES, just plug in without battery) and then boot into recovery. This should work. Assuming it does not, get another USB cable with data capabilities, and USB 2.0 ready port on the computer. This should provide MORE POWER to the phone (the phone has a weird failsafe system where it would not proceed with upgrade if the power is too low)
REASON: HUAWEI wanted the customers to have a simple update process, so they created the entire thing to just be unzip, plug in, and wait. Yeah. I know, you'll feel weird especially when other phones seem to be super sophisticated at this part and Huawei made it so easy. Even the remove the battery part. Yes.
QUESTION: But what if i'm stuck at 1/2? goddamnit?
ANSWER This did not happen to me with the file. Like I said, again, it depends on the firmware. What I've read and understood is that there is a possibility of 1) bad firmware (need to download another firmware) or 2) EXTERNAL SD CARD is badly formatted (please use an Android phone / tablet to format just to be sure) There's a thread with specific discussion about this but it was lost on my notes, but that's the gist about it. What I'll suggest you to do is download the 2.2 Froyo then upgrade back to 2.3 Gingerbread. Some people have made it through this stage by doing everything from 2.2 Froyo itself.
Reason: I'm not so sure what is wrong, but this is one of the irregularities that posters have asked when unbricking the phone.
NOTE:
After the installation part, it should restart itself a few times. Basically, after the big "TICK" and "RESTARTING", it will continue to restart again, and again, and again, and again. Then finally it should boot up properly, and then the HUAWEI logo, then the flying dust animation, then the Huawei lotus flower glowing animation, and then boot up into 2.2 Froyo or 2.3 Gingerbread (depending on your firmware)
QUESTION: Okay, I see the boot looping. However, it just boot loops, and does nothing. At times i see the animation stop. Something must be WRONG!
ANSWER This happened exactly to me. The answer was that for some reason the pinkscreen update DID not format cache and data, as well as dalvik, etc. This is a recovery issue. The way i solved this was, that I re-did the update (making sure that it really did update properly into the official stock rom), then wait for the boot animation loop, (which happened) Then, the next step was like this:
1. TURN off the phone.
2. Plug in battery (or remove it)
3. Plug in USB (yes, again!)
4. Hold POWER button and VOLUME UP button.
If you can somehow boot into a blue colored Android system recovery *3E* screen. This one is the recovery with menu, but it is HUAWEI's recovery.
5. FORMAT CACHE, FORMAT DATA
6. REINSTALL THE official ROM, (YES wait again for the "TICK" and "RESTARTING", then it should restart a few times, then boot up. Have patience and faith!
*note: apparently as noted by aashi02 when the said user was unbricking the u8800, the 3E recovery has a factory data reset which somehow clears up the entire phone and enables the phone to properly work with the stock factory-default firmware (instead of crashing again and again and again in 2nd boot onwards). So I would presume that after first boot, one would have to again boot into recovery and do a factory reset (or do it while in the settings in first boot). Not sure if there are any users to encounter "2nd boot force close syndrome" after this. (if there are, please tell me)
The phone should have booted. If it doesn't, please tell me. I can't help much but I'll try to record as many possible errors and steps to overcome it, if i see responses from others and proven to work.
STAGE 2: Getting the TOUCH RECOVERY / CLOCKWORK RECOVERY, ROOT and SUPERUSER into the phone.
Once you've got into the GINGERBREAD / FROYO, follow this thread
http://forum.xda-developers.com/showthread.php?t=1420728
Or I'll record the instructions here
Thatguy said:
Rooting the U8800 with SuperOneClick v2.3.3
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) Download SuperOneClick v2.3.3
6) Plug your U8800 into your computer but DO NOT mount SD Card.
7) Run SuperOneClick and press the ROOT Button, and let it do its thing (say yes to install drivers if asked).
8) Your phone should now be Rooted.
9) You can now go back and turn logging off if you want.
Click to expand...
Click to collapse
The next step immediately after this is NOT TO RESTART the phone, but to install the CWM
Thatguy said:
Installing ClockworkMod 5.5.0.4 on your U8800
1) On your U8800 go to Settings > Applications > Untick Fast Boot (if ticked)
2) Download Blefish's ClockworkMod from HERE (ClockworkMod v5.5.0.4)
3) Copy the recovery.img from computer to your SD Card.
4) Using Remount mount the .cust_backup/image folder as RW.
5) Using ES File Explorer or File Expert copy the recovery.img from the SD Card to .cust_backup/image (replacing existing)
6) ClockworkMod v5.5.0.4 will now be Installed on your U8800
7) Turn on your U8800 while holding [VOL+] to load ClockworkMod Recovery (keep holding [Power] + [VOL+] until ClockworkMod Loads)
Note: if you have a Synaptics screen you have to use the [VOL] buttons to navigate and [Power] button to select an option.
Click to expand...
Click to collapse
QUESTION: Okay, somehow somewhere when i boot the phone for the first time, its okay. Second time, everything goes to hell (Force Closure, errors, etc, i can't press anything!) Something must be wrong again! You suck!
ANSWER Well, yes, this happened to me. Again, please read the guide. I said, no reset. Just do everything in one GO. That's how i fixed the problem.
NOTE: by now you should be able to boot into CLOCKWORKMOD recovery.
STAGE 3: Flashing the recovery, the partition, and the firmware
This is where we want to go to, and this is where you want to fix all the problems. I should not need to elaborate here, but if you're reading this part, you can now close this thread and go to the ROM of your choice and install as per THEIR INSTRUCTIONS:
QUESTION: Wait a minute. Something's fishy. THAT EASY? You screwin' with me, noob?
ANSWER Technically it should. There should not be any other problems UNLESS you somehow again delete the /boot. NEVER EVER DELETE /BOOT. If you have installed any firmware higher than 518 (B522 and above) firmware, then you need to do the next step:
NOTE: HOW TO INDENTIFY your firmware base
This is from my own Android "about" screen:
Android version
2.3.5
Baseband version
404020
Kernel version
2.6.35.7-perf
[email protected] #1
Build number
U8800V100R001C00526G001
Click to expand...
Click to collapse
Notice the 526 in there? it means i installed base 526
QUESTION: Wait a minute. You asked me to download that frickin' partition.zip and what do you expect me to do?
ANSWER Read the answer to the next question.
QUESTION: Help! I haz problemz! i cannot install ROM! it haz fail / not enough space on my internal SD! helpz!
ANSWER IF, and I repeat IF, you're reading this, then you're probably installing something way bigger than the original partition's system partition. To help you imagine, think of it as a 10-car train. The basic idea is instead of 1 engine, you now put 2 engine, and sacrifice 1 compartment car (that means from "1engine-9car train" into a "2engine-8car train". This is where you'll find the partition.zip helpful.
BUT BEFORE YOU DEAL WITH PARTITION.ZIP, do install "GET YOUR PINKSCREEN" by Blefish, read it here:
http://forum.xda-developers.com/showthread.php?t=1457490
I quote Blefish:
Blefish said:
In the newer official ROMs, Huawei included a "feature" to lock the bootloader and therefore, get less bricks. But happened the opposite - if your cust partition gets corrupted/deleted, you'll have a high change of bricking your device.
The new bootloader is not actually locked, it's changed to use QPST (Qualcomm Product & Support Tools). As it needs a code, we can't use it.
This method flashes the B518 bootloader straight to your phone, so you will get back USB.
Apply only if you have upgraded your phone to B522 or newer. You may have a custom ROM on top, but the base has to be B522 or newer.
Tested by myself on B522, B526 & B528.
The steps required to get back pink/blue screen USB:
Automatic flashable zip is pretty much fail proof, but I have warned you.
Automatic method (recommended):
Download update-B518-bootloader.zip from MediaFire.
Save it to the root of your SD Card.
Start the phone in recovery mode (recommended recovery is 5.5.0.4)
Select "install zip from sdcard"
Select "chooze zip from sdcard"
Select the zip you downloaded before.
Select yes.
Reboot and enjoy!
Click to expand...
Click to collapse
Now that you've fixed the locked bootloader on 522/526/528, now its time to do the partition. zip
Follow this thread:
http://forum.xda-developers.com/showthread.php?t=2145187&page=124
I quote NERDO
Nerdo said:
RePartition
Note:After this operation;Phone's /data partition will be 1.4 GB,/system will be 360 MB /HWUserData (2GB Internal Memory) will be 1.02 GB and formatted
1.Download partition.zip in the attachments and copy to sdcard
2.Goto recovery
3.advanced > reboot recovery
4.Wipe data factory set
5.mounts and stroage > format system
6.advanced > reboot recovery
7."install from sdcard" and select partition.zip
*Phone will reboot to recovery after install partition.zip
7."install from sdcard" and select partition.zip again
*Phone will reboot to recovery after install partition.zip again
Click to expand...
Click to collapse
The KEY IDEA here is that you need to flash the partition 2 times.
B]QUESTION:[/B] Now what?
ANSWER Install your custom ROM as per your custom ROM's instruction.
B]QUESTION:[/B] No, really. Now what? I want to double make sure, because i don't trust you, noob.
ANSWER Okay, you need to format and clear, not everything. Follow these steps.
ROM Installation:
Use only Forumember partition.zip.
1. Copy package to SD card
2. Boot to recovery
3. Full wipe (data, cache, dalvik,) <--- This one is in main menu
4. Format /system, /data, /cache <--- This one is in ADVANCED MENU. NO NEED TO MOUNT and DISMOUNT, and DO NOT FORMAT BOOT
5. Reboot recovery
6. Install the custom ROM (and gapps if needed.)
7. Reboot. Take a deep breath.
The phone should now boot into your new custom ROM.
As per writing, i booted into CM10.1 v7 by ilyaa299. Still waiting for a better JellyBean ROM though.
Congratulations, enjoy your unbricked phone!
STAGE 4: Miscellaneous
Not all ROMs are created equal. And none stand peer to peer. No matter how many seasons have come and go, please remember the ROM is only alive as long as its developer remains commited to its releases and updates. Please thank them. They will appreciate it.
For most usage, I have no issues, except the piss poor memory of 300++MB. I have not found a way to solve this. There are APPS that claim to create a virtual RAM, but if you don't have class 6, or class 10 External SD card, don't bother, and from what I read it'll shorten your EXTERNAL SD CARD's life A LOT. use it at your own risk.
To help alleviate the situation, i installed "auto memory manager" and also "greenify". This has helped me a lot. Auto memory manager deals with current usage, but "greenify" deals with the apps that are inactive, but greedily and stealthily use RAM and hog it (as if they're some royalty of some sort)
One of the greatest points of this phone is that it has a SUPERIOR camera (even if its only 5.0mp) and it has superior HD viewing (watch movies, youtube, etc, in FULL HD, where other phones, even the MORE expensive ones cannot do)
Try to avoid apps that uses 'download as a process" like mangawatcher, because i somehow managed to fry my EXTERNAL SD card (total death) because i left it overnight to download some manga, and then it froze. Then again it probaby may be a ROM issue (its a custom ROM) but just be careful! I lost a 16GB class 4 SD card.
CREDITS:
Thanks to all that have posted to help me, big thanks to (by alphabetical order)
bdgraue
forumber2
kilroystyx
rqmok
reserved thanks to people named in the process written, especially forumber2 for his help in his post and his partition.zip. Without his post, he would not have triggered my thought process in thinking out of the box to unbrick my phone.
and a big thank you to YOU for reading, and (IF) responding to this thread to help make this thread better.
i made the same mistake, i would guess you formatted the /boot too.
you now have to take an original huawei rom, 2.3.5 will be suitable, and follow some instructions you should find in this forum already.
than u have to root your device again and install the rom you need.
Yes, you need to install the official 2.3.5 firmware again. Download it from Huawei's official website.
http://forum.xda-developers.com/showthread.php?t=1420728
in this thread you find almost every information about rooting the device.
and http://forum.xda-developers.com/showthread.php?p=22682229#post22682229 there are the instructions about installing the original rom
gl&hf
still does not work (pink screen)
Hello everyone, I did my homework by searching, but alas I could not revive my phone. (U8800)
How did it bricked: Installed CM10.1 v7, (ran fine, had to re-flash because i read that one must do /format system, /format cache, somehow probably i deleted something i wasn't supposed to, and now its bricked)
Symptoms:
1. Press power button: Blue Screen. This includes Power button and volume + together. Blue Screen. (NOTE: Huawei logo flashes briefly for less than 1 sec before screen goes blue)
2. Press power button and volume + & - together: Pink Screen.
3. (new#)Cannot access from Windows 8 (I have drivers installed, will not detect. Every time i plug the phone into win8 the phone boots up blue) but can't see internal SD.
What I know:
1. This is a U8800
2. CWM 5.5.0.4 was installed (it was bricked after i clear and format, and cannot re-enter the CWM anymore, it goes into pink screen instead)
3. Internal SD is not read-able. (this was documented when i wrote my issue, another forumer by the name of rqmok says its fine because i updated the partitioned.zip, therefore even if it cannot be read, but if it can be accessed from the android file browsers, it is okay. I believe him)
4. I can boot up the huawei + bluescreen, but no
What I did:
1. Because i was at CM10.1 v7, i renamed the entire thing as update.zip and place into external sd root folder . RESULT = nothing. just pink screen
2. grabbed an update (Gingerbread) from XDAFORUM u8800 wikipedia page (the international version), place as update.zip in external sd root folder. RESULT = nothing. just pink screen.
3# (new) I unplugged battery and the external SD, plugged the phone via USB to computer. Boot up (few seconds of Huawei logo) then bluescreen.
Yes, I understand that others have asked about this and somehow revived. What I've read, and understood was:
1. Blue screen = something about ./boot was deleted, and needs to be reinstalled.
2. Pink screen = still safe, has a chance to revive the phone.
What i do not understand:
1. Put ROM files as update.zip, but pink screen does not flash into any form of recovery.
2. Somebody from somewhere said use something called ubuntu / bt5 to "dive" into the phone's internal SD. (I don't know how to do this, and from what i understand it is risky because it involves partioning the internal SD again.
3. Any other way to rescue my phone?
What I would like to ask is some form of step by step help.
I would be very grateful if anyone can lend me some assistance. This is my first android phone (yes i'm a poor fellow) and its not even a week old. I do have an AcerA500 tablet and i have been able to update that tablet to any custom variations (ever since i owned it roughly 2 years ago), so i'm pretty confident that i am good in following instructions)
EDIT:
Okay, i'm able to update the firmware by doing the following:
1. PUT "DLOAD" folder into EXTERNAL SD, root.
2. Pull out battery.
3. Stick USB into the port, and into computer.
4. PRESS VOL+,VOL- and POWER together (Reboot into pink screen)
FIRMWARE UPDATE PROGRESS. it should be 1/2 then 2/2.
"Do Not turn off the device".
AFTER finishing step 4 (it takes some time)
there will be a "TICK" and it will say "RESTARTING".
And then the HUAWEI FLOWER (no animation).
And it repeats itself....
What do I mean by repeat itself?
1. BLANK
2. HUAWEI WITH FLOWER (NO ANIMATION)
After this, there is a green android picture and says "FORMAT /CACHE" and something like that.
Then it goes blank and huawei flowr (no animation) again, and again, and again.
*NEWv2*
I can enter the the blue colored Android system recovery *3E* screen.
formatted / data reset
it has formatted all (at first cannot format cache, causes many problems, now finally fixed). So somehow I managed to format data and clear cache.
It finally reboots. It starts up. And I thought problem over. It was not.
First time boot up was okay. It asks me to set up android, etc. Second time boot up, it will get stuck in a boot loop. Help!
I'm stuck here. Any help?
Can you access to phone from PC while pink screen?
forumber2 said:
Can you access to phone from PC while pink screen?
Click to expand...
Click to collapse
no, unfortunately no.
When I press the volume + up buttons, i can access the blue native recovery.
I updated my post as above.
Can you help me?
NEW:
again, it boots! But 2nd boot will cause issues like process.android.acore and process.google something something has stopped.
can you guys help me on this last one? (i've recorded what i've done and what happened and how i fixed it in previous post. will edit all posts later to do a proper walkthrough.
badiyee said:
no, unfortunately no.
When I press the volume + up buttons, i can access the blue native recovery.
I updated my post as above.
Can you help me?
Click to expand...
Click to collapse
Can the recovery detect sdcard?
forumber2 said:
Can the recovery detect sdcard?
Click to expand...
Click to collapse
yes, the recovery can detect the EXTERNAL SD.
But Internal SD, no. but when i click wipe data, and wipe cache (i think it does it on internal sd) it has no issues.
Again, first time boot =OKAY!
2nd time boot = F.C, all apps.
list of errors said:
The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly. Please try again)
The process android.process.acore has stopped unexpectedly. Please try again
Click to expand...
Click to collapse
I suspect the errors happen because of the fact that i installed JELLY BEAN CM10.1 v7 before, and flashed the gapps too.
Do i need to reflash gapps to GB version after formating the system? What should I do?
badiyee said:
I suspect the errors happen because of the fact that i installed JELLY BEAN CM10.1 v7 before, and flashed the gapps too.
Do i need to reflash gapps to GB version after formating the system? What should I do?
Click to expand...
Click to collapse
did you flash the original huawei rom first? or do you try to flash some custom rom immediately.
which version of original rom do you flash, when u do so?
bdgraue said:
did you flash the original huawei rom first? or do you try to flash some custom rom immediately.
which version of original rom do you flash, when u do so?
Click to expand...
Click to collapse
I flashed the original Huawei Rom first. I know i cannot flash custom rom because the recovery is *3E* recovery, not the CWM/TCW recovery.
any ideas?
I've recorded the errors.
Should I try to reinstall the original HUAWEI ROM again?
okay tried flashing Gingerbread GAPPS (FAIL SIGNATURE!)
formating data and cache again...
*ADD MORE INFO*
Huawei ROM via phone status says this
Android version
2.3.5
Baseband version
404020
Kernel version
2.6.35.7-perf
[email protected] #1
Build number
U8800V100R001C00526G001
Did I do any mistakes?
badiyee said:
Should I try to reinstall the original HUAWEI ROM again?
Click to expand...
Click to collapse
thats what i would do. first flash the huawei rom. start it, look that it works properly. after that i would root the phone, start again and look that all work as expected. then install rom manager and flash the cwm recovery, start again. boot into recovery, start again, always look if the phone is still working as it should. than take a good rom(aurora or cm10.1 v7) and flash it.
as often as you try it out and test if it all works as expected as early you can find out where errors come from.
only flash gapps if the rest works fine.
(which version of gapps do you try to flash? gapps-jb-20130301-signed.zip worked best for me over here)
Edit: http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDEyNTU=
this ist official 528 which worked very well for me. maybe 526 isnt the best suitable.
bdgraue said:
thats what i would do. first flash the huawei rom. start it, look that it works properly. after that i would root the phone, start again and look that all work as expected. then install rom manager and flash the cwm recovery, start again. boot into recovery, start again, always look if the phone is still working as it should. than take a good rom(aurora or cm10.1 v7) and flash it.
as often as you try it out and test if it all works as expected as early you can find out where errors come from.
only flash gapps if the rest works fine.
(which version of gapps do you try to flash? gapps-jb-20130301-signed.zip worked best for me over here)
Click to expand...
Click to collapse
This is the SAME ERROR i'm facing.
http://forum.xda-developers.com/showthread.php?t=2146478
I tried flashing gapps-20110828 it gave error. I also have the gapps jb20130301 file as well. But when i flash the GB gapps it says failed signature verification
QUESTION: could the partition be a problem because i used custom partition!
THANK YOU!
Thanks to everyone!
I have fixed the problem.
I will now re-write the ENTIRE post to help others that have similar issues as mine so that they would not need to be lost like I was.
Thanks again everyone!
badiyee said:
Thanks to everyone!
I have fixed the problem.
I will now re-write the ENTIRE post to help others that have similar issues as mine so that they would not need to be lost like I was.
Thanks again everyone!
Click to expand...
Click to collapse
I'll suggest you to install the patch from blefish if you are using B522, B526 or B528 as rom base.
You don't know when will be helpful to have a bootloader unlocked.
Find here: http://forum.xda-developers.com/showthread.php?t=1457490
kilroystyx said:
I'll suggest you to install the patch from blefish if you are using B522, B526 or B528 as rom base.
You don't know when will be helpful to have a bootloader unlocked.
Find here: http://forum.xda-developers.com/showthread.php?t=1457490
Click to expand...
Click to collapse
Question, how would I know my base ROM? I have read the thing, but there isn't a way in my status to know that its a B522, B526 or a B528 based ROM.
Answer: Look at the code of the installer:
E.G:
U8800V100R001C00526G001 means I have base 526 installed (LOCKED BOOTLOADER)
badiyee said:
Question, how would I know my base ROM?
Click to expand...
Click to collapse
badiyee said:
Huawei ROM via phone status says this
Android version
2.3.5
Baseband version
404020
Kernel version
2.6.35.7-perf
[email protected] #1
Build number
U8800V100R001C00526G001
Click to expand...
Click to collapse
at least after installing you will find the information in the area yoou mentioned yourselve.
if you use the original rom, the version should be in the filename. (U8800_Android 2.3 V100R001C00B528G001%28通用版%29.zip for me)
Wait, is your current recovery CWM recovery? If yes, try installing Aurora ICS. If no, first try rooting your phone and installing CWM recovery.
badiyee said:
Question, how would I know my base ROM? I have read the thing, but there isn't a way in my status to know that its a B522, B526 or a B528 based ROM.
Answer: Look at the code of the installer:
E.G:
U8800V100R001C00526G001 means I have base 526 installed (LOCKED BOOTLOADER)
Click to expand...
Click to collapse
Official Huawei GB roms have 3 different bootloaders, B517, B518 and B522, the first two are unlocked this mean you easily can reach to eMMC via pink screen. For B522 bootloader that comes into rom B522, B526 and B528 Huawei changed the way how to communicate, so we can’t reach eMMC via pink screen mode. To check if it is unlocked in pink screen mode connect to PC, if you can see the folder “image” your bootloader is unlocked.
Blefish explained in his topic that you have more chances to recover your device from soft-brick if you have a unlock bootloader because you are able to restore your device with a previous full backup done with “dd” command or with a similar program used in windows platform.
Change partition size have a high risk to corrupt them and get a soft-brick.
To have more chances to recover my device I usually follow some steps before start play with roms, see my checklist:
- Install B528
- Root the device
- Imei backup (if I haven’t done previously)
- Install CWM
- Flash Blefish’s patch, alternative I use my patch because I need my phone with SIM unlocked
- Full backup (if I haven’t done previously)
- Ready to play
rqmok said:
Wait, is your current recovery CWM recovery? If yes, try installing Aurora ICS. If no, first try rooting your phone and installing CWM recovery.
Click to expand...
Click to collapse
I think at the time of writing AURORA ICS is the most stable, usage-ready, and most complete ROM as of writing. In the future hopefully the newer ROMs like Jelly Bean, Key Lime Pie and others will be able to fit in, and be a PROPER, USABLE ROM just like how AURORA ICS and the MIUI ICS was for this phone.
kilroystyx said:
Official Huawei GB roms have 3 different bootloaders, B517, B518 and B522, the first two are unlocked this mean you easily can reach to eMMC via pink screen. For B522 bootloader that comes into rom B522, B526 and B528 Huawei changed the way how to communicate, so we can’t reach eMMC via pink screen mode. To check if it is unlocked in pink screen mode connect to PC, if you can see the folder “image” your bootloader is unlocked.
Blefish explained in his topic that you have more chances to recover your device from soft-brick if you have a unlock bootloader because you are able to restore your device with a previous full backup done with “dd” command or with a similar program used in windows platform.
Change partition size have a high risk to corrupt them and get a soft-brick.
To have more chances to recover my device I usually follow some steps before start play with roms, see my checklist:
- Install B528
- Root the device
- Imei backup (if I haven’t done previously)
- Install CWM
- Flash Blefish’s patch, alternative I use my patch because I need my phone with SIM unlocked
- Full backup (if I haven’t done previously)
- Ready to play
Click to expand...
Click to collapse
Ah, i forgot about the IMEI backup. But since mine wasn't an issue (just missing serial number, but can be found at the sticker behind phone (inside) anyways haha.
Alcatel OT POP C7 (7041x) [BACKUPS/ROOT/CWM/TWRP/TOOLS/DRIVER] [STOCK &amp;amp;amp;amp; MIUI V5 ROMs]
Last Update: Mon. AUG-03-2015
Hello,
I had bricked my "just" 4 hours old C7 a week ago because i was stupid enough to delete the custpacks from root and /system folders without even making a backup.
I had not flashed CWM and only rooted the device with RomasterSu_2.1.4 (aka iROOT, some Chinese one-click root / KingUser app) and i could not revive the phone through MTK Tools, Mobile Upgrade S or adb shell (either device not recognized or it couldn't push files, giving errors).
Today i got a new one, and hell i have not made the same mistake again.
After i unboxed the phone i immediately went into stock recovery and made a backup!
Secondly, i rooted the phone with RomasterSu and installed Uncle MTK Tools and made a IMEI backup (Just incase).
And lastely, i flashed CWM through Uncle and made a Full Backup of the current rom.
For anyone who happens to play with a rooted C7 on stock rom and accidentally bricked it, i will provide my Stock and CWM Backup Recovery's for anyone to use.
note: If you already flashed a custom recovery onto your device (e.g; CWM), the stock backup becomes obsolete! Use CWM instead.
[INFO]
Model: Alcatel One Touch 7041x
Firmware: 4.2.2
Baseband: MOLY.WR8.W1315.MD.WG.MP.V7
Kernel: 3.4.5
Build: 01003
Stock Recovery (Data) Backup (.backup):
- userdata_20100101_000117.backup (.rar / 83MB)
Place Stock Backup (Unpacked) into the root folder of your sdcard.
Reboot phone, Vol+&Power into stock recovery and select "restore user data" (or something alike) and select the .backup file.
New googledrive uploads:
-MIUI V5 (4.8.29) ROM (.zip)
-RootMaster / iRoot & SU (.apk)
-Uncle MTK Tools (.apk)
-CWM & TWRP Recovery (.img)
-Mobile Upgrade S (.exe)
-One Touch Center (.exe)
-USB Drivers (.rar)
-MTK DroidTools (Windows) (.zip)
-SP Flash Tools (.rar)
If you're familiar with flashing, i'd guess installing these files and how to use them propertly are self explainatory.
If not, you can ask me how to write a proper guide...
==============================================================================================================
--UPDATE--
I provided a stock rom and a MiUI V5 rom for people who don't want or prefer to use backup's. A custom Recovery is needed and will not work with stock recovery.
This is a vanila stock rom without the custpack games/apps bloatware. IIRC this rom is already rooted, but if not, you can always use iROOT.
Bare in mind that it's based on the first TCT Firmware build 01001 and not the latest Firmware Upgrade 01003.
The MiUI V5 rom is based on miui 4.8.29 (Jellybean 4.2).
Also, the installers are in Spanish and you can only select a handfull system languages for both roms, but atleast you can use these roms in English.
Both roms work absolutely fine, and faster than stock with custpack bloatware.
Stock (01001) ROM:
https://drive.google.com/file/d/0B_pc8K917q22RlJWNllGV2JLOVE/view?pli=1***
MIUI V5 (4.8.29) ROM:
http://www.mediafire.com/download/9l49h7gisxslx2s/Miui+v5+spanish.Alcatel+7041x.zip***
---UPDATE--- [AUG-03-2015]
KitKat 4.4.x Alcatel C7 (7041x):https://translate.googleusercontent...2.html&usg=ALkJrhh-v6soAAT7XuUrpiK_zGh5bODHaA***
*** I have not uploaded these ROMs, nor am i responsible for any damages or errors that might occur during flash, use at own risk and always make a backup first!
Making any custom changes to your device will void your warranty!
Bump Update!
Added files to google drive;
-MIUI V5 ROM (4.8.29) (.zip)
-RootMaster / iRoot & SU (.apk)
-Uncle MTK Tools (.apk)
-CWM & TWRP Recovery (.img)
-Mobile Upgrade S (.exe)
-One Touch Center (.exe)
-USB Drivers (.rar)
-MTK DroidTools (Windows) (.zip)
- SP Flash Tools (.rar)
https://drive.google.com/folderview?id=0B52SB5R_clyUVTNwVHlwMHpCZWM&usp=sharing
S5 7041X Rom
http://www.htcmania.com/showthread.php?t=976259
How to install stock ROM with Mobile Upgrade S,when installed custom CWM?How back to stock CWM?Mobile Upgrade S does not recognize the phone with custom CWM.Phone must be flashed with SP Flash Tool.After this,Mobile Upgrade S,recognizes phone.
_jussyy said:
http://www.htcmania.com/showthread.php?t=976259
Click to expand...
Click to collapse
Nice ROM,but it kills the battery.
mugy said:
Nice ROM,but it kills the battery.
Click to expand...
Click to collapse
Most roms need some time to settle, after 1 or 2 complete charges your battery should behave normally.
You can also use the 'Greenify' (Permit SU access) to blacklist any app that uses wakelocks or running backround processes.
This will save you some battery...
My best bet is going for the MiUiv5, which always ran fine when i used to own the C7. Never had any issues with that ROM other than a occasional 'SystemUi stopped working' when trying to use the Rom's OTA.
I installed CWM 5.5.0.4 but cannot see internal storage
Do you have any idea?
erdemdengel said:
I installed CWM 5.5.0.4 but cannot see internal storage
Do you have any idea?
Click to expand...
Click to collapse
A bit late but that's because I don't own the C7 anymore and hardly pay attention to these threads anymore, I'm sorry...
I have no idea why it would'nt show up in CWM. I always use TWRP on any device that has it's compatibility over CWM, mainly because of it's touch functions and ext partitioning functions. Normally your internal storage is sdcard0 and your SD is sdcard1, select "mount/unmount" to see whether it's listed or not (I guess you already did that obviously but still....) It should be listed, if not, reflash CWM (try latest available for the tct/alcatel, i don't know which build number out top of my head, or TWRP.
I suggest to switch to TWRP and most likely your problem will be solved.
I don't know where you got your recovery files, but the ones I got in my googledrive are guaranteed working since I tried them both before uploading, if you used my CWM try to reflash it with MobileUncle MTK Tools, but than again pick TWRP instead .
Sent from my ACER LIQUID Z500 using XDA Free mobile app
Bump Update
Sent from my HTC One using XDA Free mobile app
I tried to use both the CWM and TWRP recoveries and neither worked. When it tries to boot into them it just glitches out the boot screen and resets. I flashed them with Flashify if that's a problem. My tablets model is a P310A. So this is the right thread for it right?
It does the same thing when I flash with Uncle MTK Tools.
Update: So it seems that you need to use this recovery if you have a P310A. Sorry for the pointless bump.
White sreen when flashed
After I flash my phone I get white screen logo whitescreen logo etc.
I have the alcatel 7041x
Alcatel one touch pop C7 ,Dutch
It functional in 7040e?
Not reading us b
I can't download backup file
@dragonivell
No! 7041x only. If it would, i would've stated it at the "device compatibility list" (which doesn't exist in this topic, for that reason!)
@pricklain
I'm sorry, somehow the file got removed from my gdrive. Since I don't own this particular device anymore, i cannot re-upload the file in question.
Also, i'm unable to edit the OP for some reason, so i understand any complains about the backup file(s).
Note: I am hardly online on xda these days, so forgive me if my response is a bit late...
@jachthond
Heb je wat meer details wat er niet lukt met flashen, en welke files je daarvoor gebruikt hebt? Mischien kan ik je er door heen loodsen.
Nobody has to Alcatel One Touch Fierce 7024w ?
links please
Ebom
Because this thread was the first one I completly read and looked at many time again, I post my results in short here.
Its posible to "flash" or "download" the KitKat rom from Hungary (or whereever the rom came from) onto a stock Alcatel OT POP C7 (7041X). Note the X, I have only that phone so, find another thread or user if you dont have a x (the kitkat rom is from/for a 7041D, so maybe your in luck too if you have the D version)
https://forum.xda-developers.com/alcatel-pop-c7/help/alcatel-one-touch-pop-c7-kitkat-twrp-t3438624 this other thread has the working rom, tools, and scatter file.
I could write a tutorial, but i based my carefull work on that thread and the links he provided. I also watched the youtube video even tho I dont understand a word thats being said.
Basicly NEVER EVER overwrite or format the phone completly or do sh1t with the preloader. mobile_info we leave alone aswell and we dont like to touch NVRAM aswell. They kinda contain imortant stuff
Basicly i made backups of everything I could or wanted (some thread said "Readback" the preloader can break alcatel phones, Ive succesfully read my whole phone back, but NEVER tried "downloading" or flashing preloader, cause i dont want a brick.) so I have everything saved and i could compare my files against any other rom that ppl uploaded.
KitKat rom from that thread I linked you to, get it, just all of it just in case. then if you compare them using CRC/SHA1 or MD5 against your dumps. hopefully like me, MBR, EBR1 and EBR2 are all the same compared to the kitkat one. so i took the liberty of not flashing them.
left us to do the: UBOOT(lk.bin in my backups), BOOTIMG, RECOVERY, SEC_RO, LOGO, CUSTPACK, ANDROID.
I noticed diferences in the logo, recovery and sec_ro, so I followed the tutorial/video on "downloading" those onto my phone... real simple...
I now have KitKat on my 7041x
Phone calls itself a 7041D now and Gyroscope sensor is not working
simple fix for the phone name is in the build.prop file, either google how to edit that (using root, or adb tricks) or do as I tricked, changed the file inside custpack.img using an hexeditor (HxD is my favorite). When you find a 7041D, replace with X. I suggest you use your brain and computer skills to deduce how to "replace" a character instead of inserting seems to start at offset 0x03356000 (http://www-ccpp.tcl-ta.com/files/ALCATEL_ONE_TOUCH_7041X_KK.xml does excist, so it suggest an official rom either was made or support added anyway).
I replaced budhapest with amsterdam and could change the dualsim to false and compensating the file size change by removing some 0x00 after the file.. but felt it was too risky and only tried the D into X wich was succesfull. ill check if I can find the AcceleroMeter/Gyro? module or fix.
If anyone has a question, sure ask me. but the rom is there, make backups before ANYTHING, and never full format or touch the preloader. ive read it might be able to fix using some Jtag method, but I cant remember the thread and this is quite the old phone by now. if ever, ill try a newer rom, but probably have to make it myself. another kitkat rom Ive found wasnt clean but this one was like it was a OTA, the phone migrated the 58 apps, and all my settings where still there, whatsapp worked right away without trouble and I can now play Pokemon GO (the x version has the 1gig ram )
Bedank @JMailuhu for making this thread and pointing and warning people. within 1 week of fixing this free phone Ive updated to kitkat. Now ill try fixing the accelerometer problem and maybe try other roms (ow well, kitkat does work fine) no root or custom recovery sofar
TLDR: Have a cookie, sorry I talk too much. much better than "ROM NOW" comments