Database Users

[Q] Probs installing Cyanogenmod 7.1 on x8(E15i)

Hey.
I'm having difficulties with new cyanogenmod 7.1
I Followed different tutorials and none of them helped me.
I started with stock 2.1 rom and did all the unlocking bootlader stuff , then installed custom kernel and managed to install cyanogenmod 7.1 but then occurred a funny thing . There was only FreeXperia logo showing up, nothing else, and it rebooted all the time. Then I flashed stock rom again and tried to understand what's wrong and tried to use different kernels and nothing.
So my question is. Is there anything I'm missing here?
Henri.

Full wipe after you install rom.
Dot forget to make backups first.

about that...
i always do full wipe after installing roms, so it has to be something else.
Thnks anyway..
But after browsing several topics in XDA forum I saw that I'm not only one with the problem.
If anybody has had the problems like I do and got the solutions, every kind of tips are welcome.

Thread closed
I got it all working, but I don't know what was the reason, because, I just did the whole thing again about three or four times, and then it just booted and worked.

I never could install Cyanogenmod in my phone... could you?

Hey!!!
I could write a total working tutorial how I managed to get to work everything, but it takes time, so if you want tutorial send me private message , so I create it for you.
Henri

Does wifi and/or 3G work for you longer then 15 minutes?

No, but at the moment I'm using RC1 flawlessly.
Sent from my E15i using XDA App

coffee-break said:
I could write a total working tutorial how I managed to get to work everything, but it takes time, so if you want tutorial send me private message , so I create it for you.
Henri
Click to expand...
Click to collapse
umm..why not post it publicly man ? It will be useful for everyone including myself.

Would also like that tutorial

ok,
i'm gonna post it here after finishing it.

So, the wanted tutorial is here!
Firstly it's for xperia x8(E15i) to be superclear.
I'm gonna put that tutorial into steps.
STEP 1
You need to have stock 2.1 rom with baseband XXX015 , if you don't have it, then go to Sony Ericsson's webpage and download the upload service and flash it back into your phone.
STEP 2
You phone has to be rooted. Easieset way is using Superoneclick(sorry, i'm not gonna provide the link, because it's just google-ing thing to you who need rooting program)
STEP 3
Now, everything comes to the unlocking process for bootloader. there is also tutorial how to succeed when using s1tool and msm7227 (if you have problem, then I don't know). Try to undestand the tutorial of doing it.
S1tool is for identifying if your phone is unlocked or not.
and msm7227 is for unlocking
tut is here - LINK
I wish luck, don't brick your phone, but it's not so hard to understand tutorials if you have right phone and right tutorial.
STEP 4
I totally suggest to install stable rom. The reason is that released 7.1 has bugs and incompatibility with some phones and i haven't got wifi and 3g working , but tried different roms and kernels.
I provide links i got from deani77, big thanks to him.
You can try this link for FXP028 ROM - http://www.multiupload.com/IIWIPG1ALH
For FXP030 kernel try this link - http://hotfile.com/dl/132650338/7b17...USTOM.ftf.html
(that release is RC1 of Cyanogenmod 7.1 but I think it's the best at the moment!)
and you download all the files as usual. Rom zip package should be in the SD card's root folder, so you can easily install it after flashing kernel
STEP 5
installing is quite simple actually. You need to use flashtool that is provided with rom(link in step 3)
firstly you flash kernel. Kernel file is the one you downloaded .ftf file. You have to put that file(X8_custom.ftf) into firmware folder which is inside of flashtool folder.
Then you open flash tool and you click FLASH, then appears little window and you click ok and then you need to plug in your phone into usb while holding down back button. Your phone has to be off when you are doing that. Then flashtool identifies your phone and will flash the kernel into your phone. when everything comes smooth then you now have fxp custom kernel. it has clockworkmod recovery and you need to click several times back button when FreeXperia logo appears.
STEP 6
You have to do factory reset and format, also i suggest from advanced menu using format system.
Then you select from the recovery menu install custom zip... and you browse your rom .zip file and if everything is OK then it should display "installing update or smth" if it's done then good for you, you reboot and it should work.
IF YOU WANT GOOGLE APPS , then google the link and install it same way you did with the rom. You can do it any time.
..
So if anything is not understandable then ask. I'm not an expert or anything, I just did things like I described.
Best,
Henri.

i have still had problems with bootloop and passing md5 checksum any idea on how to fix this?

mm.. at the moment I don't know but what that md5 checksum means?

I fixed my bootloop issue when I flashed back to stock rom, then I just did all the steps I describe again (not unlocking bootloader because it was unlocked already) .. but I don't know what's really does the bootlooping thing. I just got lucky. It took me like billion hours until I got it working...

Before installing official gingerbread

Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!

I don't know, maybe I've been preaching to deaf ears or something...but...you can re-install the old ROM back, the CWM recovery won't work with the official GB - that much is true - but you will be able to downgrade to an official 2.2.2 (I used the B162) version with the regular update method (at least I was and everything is working just as normal as it used to).
So, irreversible - I don't think so
with the current CWM recovery - it's a no-go
edit: that being said, what works for me, doesn't necessarily work for everyone, so be careful and blame the guy in the mirror -not me, if it doesn't work for you. =)

I think Huawei says wrong here. I flashed 2.3 yesterday. After that, because of the haptic issue I flashed back to official 2.2. Only problem after the 2.2, recovery console had opened. I did factory reset there and phone started without a problem. Then, I had upgraded to 2.3 again. Still haptic don't vibrate. Other than, no problem here. Maybe, I will go back again to 2.2.

Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!

what 2.2 version is that and you did it after or before rooting?

Have you tried with internal sd? I copied dload folder to internal and started the upgrade process from Storage-Upgrade Firmware. Where did your phone stuck?
Edit: I didn't root my phone. Waiting proper solution. I had used B138.

no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001

Druida69 said:
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
Click to expand...
Click to collapse
Well, like I said, what works for me doesn't necessarily work for you.
Anyway, this is what I did and it worked, maybe it can help others.
0. Copy the original B162 ROM ("dload"-folder which has two files, UPDATE.APP AND UPDATE_CUST.APP) to the root of your SDCARD
1. Update to B162 by holding down +- keys while turning on the phone
2. After the first reboot, it's giving error messages for not being able to mount this and that...just ignore it and...
--> Wipe data / factory reset --> remove battery
3. Update the B162 again --> this time everything should go OK, if so, your phone is back to stock B162 and you're ready to use it or update a custom rom (just install Clockwork recovery like you used to and start from there)
The last point (3) may be unnecessary, but I did so just to make sure everything's ok.
Edit: OK, and I meant b162, not b160...

Druida69 said:
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Click to expand...
Click to collapse
For me it also works. I have downgrade without any problem and I use to the b 162 version. Now Ian back to oxygen
Sent from my u8800 using XDA App

yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.

Druida69 said:
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Click to expand...
Click to collapse
And then there's the fact that the official gb is still beta, it's not supposed to work perfectly. But as long as the dev team here stays active, I think that I'm gonna stick with custom roms too.

ho my god.
didn't work.
is always booting into recovery

I am stuck here also (
Nothing worked
I tried clockwork recovery - it doesnt get to. It is just rebooting.
I tried with various dload UPDATE.IMG's (GB Overseas, GB orig chinese,B162,B138) nothing is working - stucked in "Step 1/2 Unpacking" window forever.
Anyone has solution for this ?

Two weeks ago I've flashed the U8800Pro version - real mistake
I've started a topic here:
http://forum.xda-developers.com/showthread.php?t=1327715
katu2006 and on the second page flibblesan gave me a method to start my phone working well.
Post #4, #11 and #13.
Maybe this will help you,too?

sbasil said:
Anyway, this is what I did and it worked, maybe it can help others. (...)
Click to expand...
Click to collapse
You sir are a LEGEND. My phone "lives" again! On CM7 again...

manage to install miui.
several versions now up to the newest one.
I noticed on all of them that it mount the SD card when connected to USB but only shows the system files and not allow writing, copy, cut, etc.
Saying that I dont have permission to change the SD

Druida69 said:
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
Click to expand...
Click to collapse
I have just flashed with new U8800V100R001C00B517G001(Beta1.0)(Overseas Normal)(Gingerbread) but after flashing I kept waiting for start my phone. I restasted many times but same, then I format data its worked and when restarted again it goes in same condition any help ?

until flash disk is writable and it is - there will always be way to go back to old versions it just files.. like reinstalling windows on your pc.

Since the new Rom is public I have read all posts about it here. Maybe I had lucky, or simple due it without messing with the files.
Yesterday I made the upgrade to the new rom, directly from the last Oxigen version, without downgrade to 2.2. I simply create the dload folder on SD card, put there de update file, boot with +- Power, and chose upgrade from SD card.
After step 2 I reboot the phone a install step 3 upgrade. Everything as installed fine, no boot loops, nothing...
Also the root method decribed in this forum as work on first time.
24 hours after the upgrade, and some reboots to test, I never se the boot loops, and the phone is working well.
The new ROM, even in beta stage, to me is a great improvement.

Well either you were lucky or me and the majority were unlucky.
But issues only start to happens when rooting.
So that you can see it fried me the 1 USB cable. This cable is only good to charge the battery now....
Also, ****ed the device USB storage MOUNT.
I connect it to the computer and the computer sees it as a CD drive not allowing any changes.
Also when press the button to mount the USB on the device it never gets mounted and gives the messages that the SD can now be removed.
So I have put this issue many times but up to the moment no one even reply to help.

Cannot root U8800Pro. SuperOneClick hangs at step #7

Hello,
I have a problem when trying to root my wifes U8800Pro. The SuperOneClick gets always stuck at step #7. I have done everything as instucted (enabled logging and usb debug, disabled fast boot, etc).
Before you say that I should search, this has been discussed before. Yes I know, I have searched and found couple threads, but they didn't help.
I'm guessing that the problem is that I have too new stock firmware? I had this in the phone originally:
u8800pv100r001c00b535
custnorc306d002
But now I downgraded (?) or upgraded to:
U8800Pro V100R001C00B512G001
And the SuperOneClick still isn't working. I don't know what to do. I can't find any older stock 2.3.5 firmwares and don't know if it would even help me if I could downgrade to some older version.
Could someone please help me how to root this phone. I have done Galaxy S before, but it wasn't this complex
BTW, the SD card stopped mounting when I flashed V100R001C00B512G001. I have to take it out and re-insert it to make it work every time.

I'll answer to my self. I don't know if all this is correct, but anyone can correct me if they want.
The stock roms can be rooted in various different ways. Most used options might be SuperOneClick and "pink screen" boot.img change.
SuperOneClick doesn't seem to work with at least newer versions of 2.3.5 at all. It's only usable in older stock roms.
Another option is using the "pink screen" method, with boot.img and it goes like this:
1. Power off, and then Power on with Vol + & - pressed to get to the Pink Screen.
2. Connect the phone to your computer with USB cable.
3. Browse the phone contents with your computer. You should only see one folder called "image". Go inside the folder.
4. Backup the boot.img file to your computer. You will deed it if you want to unroot / return to stock later.
5. Replace the boot.img with a rooted one. You have to find a boot.img specific to your firmware version. I haven't found one for 2.3.5. I'm not sure if they are different between U8800 and U8800Pro, but I guess they are.
6. Once done, detach the usb cable from the phone and restart it by taking the battery out and reinserting it.
You should have now rooted your stock firmware phone and you should see a Super User app in your app drawer.
But if you are going to load a custom firmware to your phone, there is no need to root the stock firmware. In this case you should use Clockwork Mod Recovery to load the custom firmware into your phone, because custom firmwares are already rooted.
It goes like this:
1. Power off, and then Power on with Vol + & - pressed to get to the Pink Screen.
2. Connect the phone to your computer with USB cable.
3. Browse the phone contents with your computer. You should only see one folder called "image". Go inside the folder.
4. Backup the recovery.img file to your computer. You will deed it if you want to return to stock later.
5. Replace the recovery.img with the CWM Recovery file. You need to make sure that you have the correct version for the rom that you are going to load. The needed version is usually mentioned in the rom description. I think the latest one is this: [Recovery] Unofficial CWM Recovery 5.0.2.7[u8800pro&u8800] (?)
6. Once done, detach the usb cable from the phone and restart it by taking the battery out and reinserting it.
7. You can now install custom roms with CWM Recovery by holding volume + and power to boot up your phone. Look at the install instructions of the rom you are going to install.
Be sure to backup your phone with CWM Recovery as soon as you have installed it in case anything goes wrong.
See how to create nandroid backups with CWM Recovery here.

http://forum.xda-developers.com/showpost.php?p=23565074&postcount=7

Experiences said:
http://forum.xda-developers.com/showpost.php?p=23565074&postcount=7
Click to expand...
Click to collapse
This is for regular u8800 not pro.
Sent from my U8800 using Tapatalk 2

I'm going to reply to this thread as this is kind of on topic... could someone more experienced answer at least some of the questions below, thanks.
Does anyone know where I could find stock firmwares for U8800Pro? I'm having hard time to find any even from Huawei's site. I only found this there and that says it's only usable in Russia.
I had this in the phone originally when I purchased it:
u8800pv100r001c00b535
custnorc306d002
Was that the newest stock firmware? Where can I find the newest one?
Is there a "rooted" boot.img for the latest stock firmware? Is the boot.img different for every firmware version? Is it different between U8800 and U8800Pro?
Is this the latest CWM Recovery and should I use that? I'm going to put some ICS rom in to the phone after I've tested the official demo version which is coming "soon" I hear.

I'll answer to my self once again..
Here's some stock firmwares for U8800Pro:
http://madmodder.co.uk/huawei/u8800-pro/huawei-u8800pro-firmware-list.htm
I guess the newest stock version is V100R001C00B572G001.
For the "rooted" boot.img I have no clue where to find one, or are they firmware specific or different between U8800 and U8800Pro.
As to the CWM, here's the official releases. There's no releases for U8800Pro, I don't know if it has different recovery.img as the U8800 has. I guess the one which I linked to is the latest "unofficial" version. Reading the comments seems to point that it works for some and some have problems. I guess that should be used still if you want to go for ICS rom.
Anyone care to comment on any of this?

I have the same problem i did every thing perfectly and i couldn't get to root my u8800 pro ... i tried super one click, z4root , easy root, unlock root , changing boot.img, ... i have my drivers installed correctly.. checked usb debugging.. disable fast boot....switched to logged on ( project menu ) and i still got stuck on step 7 on super one click.. another program mentioned.. ( adb server out of date.. ) and ( failed to copy superuser.apk due to system read only..) ... so I'm stuck now for 2 month..can any one help ???
Sent from my U8800Pro

[Q] unbricking selfbricked stock A500

My colleague brought his stock A500 to me in a bricked condition last week.
I need a way to restore it. If I try to do a wipe it will say bootloader error if i try the recovery the droid falls down with the red sign with the exclamation mark.
This tablet has never been rooted, my colleague is not in to such things, it's lived its life with ordinary acer otas and the occational very young human (5 year old) trial wich it has survived.
He has installed all the OTAs he ever got on the tablet and this is in Sweden so it would probably be a 4.0.3 acer stock on it now.
I'm guessing it has died during a OTA or something. if i turn it on it will sit at the acer logo indefinitly.
I Bricked my A500 during a rooting atempt resulting in me needed to flash a stock rom to get it working again, but i cant find the thread i read to un-brick my A500.
Please Help!

try this http://forum.xda-developers.com/showthread.php?t=1839313

dibb_nz wrote:
try this http://forum.xda-developers.com/showthread.php?t=1839313
Click to expand...
Click to collapse
Well that thread seems to hold all i need, although i can't do a full wipe. when i do the flipswitch wipe procedure it halts with bootloader error
Im hoping to just be able to flash the stock rom from the link you gave me. Is it entirely necessary to do the wipe prior to flash? can i wipe it afterwards?

Hogbola said:
Well that thread seems to hold all i need, although i can't do a full wipe. when i do the flipswitch wipe procedure it halts with bootloader error
Im hoping to just be able to flash the stock rom from the link you gave me. Is it entirely necessary to do the wipe prior to flash? can i wipe it afterwards?
Click to expand...
Click to collapse
we're assuming the tab is full stock and currently on ICS...
and we're assuming he never tried to 'fix' his tab by flashing one thing or another...
the bootloader error worries me...what exactly does it say...
Yes the wipes are really important!! and not being able to use the button method to do so is concerning...
what happens with the Over The Air (OTA) updates is its just that...an update...it leaves all your settings/data intact. When you OTA from one build to another, like Gingerbread 3.0 to Honeycomb 3.1/2 and then to ICS 4.0 - you drag all your apps and settings with you and of course some things that work with 3.2 will not work under ICS....fjor instance, lots of folk had trouble with wifi disconnects, once they got to ICS - or they had apps force closing and other 'glitches'. This is why everyone tells you to do the wipes - as this fixes these things! In the case of stock ICS my gmail would f/c all the time no matter how many times I wiped/formatted....So for a smooth running tab - flash a custom rom!!!!!!
But getting back to you...
From that link i gave you...download the 3.1_Full.zip....its decrypted so just extract it and get the "update.zip" from it..
This "update.zip" is not an incremental "update" but the full stock rom....
once installed you'll be on GB you will need to root it with iconia root and then use acer recovery installer to flash cwm....(get these from the playstore)
do a backup or adb devices so you can get your CPUID....this is important...if anything goes wrong at any stage this is the only thing that will get you unbricked....see the cpuid link in my sig for more on this, please take the time to read it, even if it doesnt make much sense to you, read it anyway....
AFTER you have retrieved your cpuid, you can nvflash the patched bootloader/recovery pkg which means you are able to flash ICS/JB custom roms
they cannot be flashed via cwm like normal...you must use nvFlash to do it....
OR
take the OTA route to ICS...this takes a bit of time...I did it last week and it was a good 6-7 hours to go from GB to ICS
there are pre-rooted stock roms if you wanna stay stock see civato's stock rom thread for that here http://forum.xda-developers.com/showthread.php?t=1633907
official stock rom list by blackthund3r are here http://forum.xda-developers.com/showthread.php?t=1816560
civs guide to flashing the unlocked bootloader here http://forum.xda-developers.com/showthread.php?t=1622425

I am in a similar situation. Push the power button and it goes to a screen with white acer on black and stays there. Totally stock ICS, no root. I tried the update.zip thing and after automatically rebooting it says "Boot verified failed...". I don't have my cpuid, or have installed previously CWM or anything like that. I can get into APX mode. This guy here: http://forum.xda-developers.com/showthread.php?t=1751978 could only get into APX with no cpuid as well, but i don't understand all of the ubuntuu and command line stuff. I would love for someone to be able to walk a dummy like me through this mess. Thanks for any help.

if u got boot verified fail error you need nvFlash to repair that....as u know, with nvflash you need yr cpuid....wot about usbdeview? if you've never plugged yr tab into yr PC - then it won't work and the ONLY other way is Linux....
might be best to start yr own thread with a descriptive title, not just a help I'm bricked no uid, thread there are hundreds of those....the more effort u put into the title the more likely you will attract the attention of someone who can actually help...and remember you just don't need a bit of help but a blow by blow description of what to do and how....this will be very time consuming....at the very least get ubuntu installed, maybe just try a few things, anything to show you are capable of at least giving it a go yourself..
there are others who would like 2 know how to do this as well...having a specific thread of its own would be great
good luck
dibb
Sent from my GT-I9300 using Tapatalk 2

Actually, I have connected it to my PC before. Only for transferring media though. If I've done that, is the some way to retrieve my cpuid from the PC?

yup...usbdeview.zip see the bottom of the OP in the cpuid guide in my sig

Thanks alot for your help. I used usbdeview and got my cpuid. Now I should use nvflash? Know where a good step by step is for that one?

you could try the one in my sig??

dibb_nz said:
you could try the one in my sig??
Click to expand...
Click to collapse
Right. Sorry, I didn't notice that before. Thanks again for your direction.
"To install one of these roms you will need a custom recovery and to get that you must flash the patched bootloader FIRSt - once its patched you can install a recovery any old way you like"
Looking at that guide, would you please tell me what a custom recovery is and how to get one? Btw, I don't plan to do a custom ROM yet, I just want to get the damn thing working first. Was thinking of using the HC EUUs from the firmware files list. However there are two files, a .rar and a .exe listed. Which do i use?

NvigR8 said:
Right. Sorry, I didn't notice that before. Thanks again for your direction.
"To install one of these roms you will need a custom recovery and to get that you must flash the patched bootloader FIRSt - once its patched you can install a recovery any old way you like"
Looking at that guide, would you please tell me what a custom recovery is and how to get one? Btw, I don't plan to do a custom ROM yet, I just want to get the damn thing working first. Was thinking of using the HC EUUs from the firmware files list. However there are two files, a .rar and a .exe listed. Which do i use?
Click to expand...
Click to collapse
The .rar EUU is for an A500, the .exe is for the A501, which do you have?

I've got the a500. However, I decided to go with a custom ICS rom after all. I managed to put a new bootloader and custom recovery on using the a500apx flash tool. That part went fine. I flashed this rom:
Acer_AV041_A500_1.054.00_WW_GEN1-FULL-ROOT (original odex)
and that appeared to go well according to twrp, but after rebooting, it just shows the bootloader again and stops there. Not sure what i did wrong.
I renamed the rom update.zip. Should i not have done that?

well congrats for getting thru the flash process with no probs!!!
as far as renaming to update.zip that was not such a good move...hopefully things havent been screwed up too much
just go back into recovery and do a FULL wipe/format
then to flash use the option "install from zip file" not sure where that is in TWRP but it will have one

Okay. I will reflash the rom after completely wiping again. Thanks.
On a different note, why do roms require particular bootloaders?
Also different, how do you like your SGS3? If i can manage to fix this thing, perhaps I'll root my phone...

NvigR8 said:
Okay. I will reflash the rom after completely wiping again. Thanks.
On a different note, why do roms require particular bootloaders?
Click to expand...
Click to collapse
The stock ICS BL is encrypted - more or less - the only way to 'flash' a recovery or rom is to have the "key" that "unlocks" - it more or less - if you dont use the right key then the OS will not boot - the 'key' is based on your cpuid which is why everyone is forever telling you to save it somewhere safe....
Also different, how do you like your SGS3? If i can manage to fix this thing, perhaps I'll root my phone...
Click to expand...
Click to collapse
I enjoy the big screen, took awhile to get used to it in my hand, kept dropping it....then I ran it over with my 44tonne truck after 3 days and munted it!!!!
I have a case for it now, and its gr8 - I havent installed a rom on it yet...the forums over there are jampacked and I have no idea what I'm doing, lol - its the first android device I've had that I've left stock for so long...but it does what I want...the camera is awesome -burst mode is the bomb - BUT do I think it was worth the money???? Still on the fence about that one.....

Ouch. Sorry to read about running over your phone. That would kill me. I really like my SGS3. I think I'll look into rooting it just to be able to back it up and get rid of the bloatware. I did that on my Captivate and prior to today, thats all I've ever done modding wise to an android device.
So, I managed to get my tab up and running again. Yay! I reflashed the rom w/out changing the name and worked like a charm. Now If only I knew why this happened in the first place... Thanks for all your help.

NvigR8 said:
Ouch. Sorry to read about running over your phone. That would kill me. I really like my SGS3. I think I'll look into rooting it just to be able to back it up and get rid of the bloatware. I did that on my Captivate and prior to today, thats all I've ever done modding wise to an android device.
So, I managed to get my tab up and running again. Yay! I reflashed the rom w/out changing the name and worked like a charm. Now If only I knew why this happened in the first place... Thanks for all your help.
Click to expand...
Click to collapse
yeh sometimes happens with the tab for some reason - thank your lucky stars it didn't get stuck in apx mode...if that happens its normally a hardware fault so theres not alot u can do...I'm just pleased you got sorted without too much drama and it was as easy as reflashing the zip....so now you have the v8 BL - you're gold!!!

dibb_nz said:
we're assuming the tab is full stock and currently on ICS...
and we're assuming he never tried to 'fix' his tab by flashing one thing or another...
the bootloader error worries me...what exactly does it say...
Yes the wipes are really important!! and not being able to use the button method to do so is concerning...
what happens with the Over The Air (OTA) updates is its just that...an update...it leaves all your settings/data intact. When you OTA from one build to another, like Gingerbread 3.0 to Honeycomb 3.1/2 and then to ICS 4.0 - you drag all your apps and settings with you and of course some things that work with 3.2 will not work under ICS....fjor instance, lots of folk had trouble with wifi disconnects, once they got to ICS - or they had apps force closing and other 'glitches'. This is why everyone tells you to do the wipes - as this fixes these things! In the case of stock ICS my gmail would f/c all the time no matter how many times I wiped/formatted....So for a smooth running tab - flash a custom rom!!!!!!
But getting back to you...
From that link i gave you...download the 3.1_Full.zip....its decrypted so just extract it and get the "update.zip" from it..
This "update.zip" is not an incremental "update" but the full stock rom....
once installed you'll be on GB you will need to root it with iconia root and then use acer recovery installer to flash cwm....(get these from the playstore)
do a backup or adb devices so you can get your CPUID....this is important...if anything goes wrong at any stage this is the only thing that will get you unbricked....see the cpuid link in my sig for more on this, please take the time to read it, even if it doesnt make much sense to you, read it anyway....
AFTER you have retrieved your cpuid, you can nvflash the patched bootloader/recovery pkg which means you are able to flash ICS/JB custom roms
they cannot be flashed via cwm like normal...you must use nvFlash to do it....
OR
take the OTA route to ICS...this takes a bit of time...I did it last week and it was a good 6-7 hours to go from GB to ICS
there are pre-rooted stock roms if you wanna stay stock see civato's stock rom thread for that here http://forum.xda-developers.com/showthread.php?t=1633907
official stock rom list by blackthund3r are here http://forum.xda-developers.com/showthread.php?t=1816560
civs guide to flashing the unlocked bootloader here http://forum.xda-developers.com/showthread.php?t=1622425
Click to expand...
Click to collapse
When i do the wipe it says
Code:
Erasing userdata...
Code:
Unrecoverable bootloader error (0x19000008)

Unrecoverable bootloader error (0x19000008)
Hogbola said:
When i do the wipe it says
Code:
Erasing userdata...
Code:
Click to expand...
Click to collapse
I googled your error - the consensus from what I read is a corrupt OS due to running OTA updates...
Some had luck with rebooting. Others had to send it to Acer.
Did you run the update.zip? so what happens when you run the update.zip
Are you able to get into "apx mode"? If you can, hook up to your PC and see if your tab is recognised as an "apx device" - check "Hardware, Printers in win7"
Thats all I can suggest atm - if your tab does get into apx mode OK then you can find your cpuid by running Linux -
Maybe ask the guy if he's ever had the tab hooked up to his PC like to transfer files and stuff - get him to download "USBdeview" to his PC -
this will show every single device thats ever been connected to the PC and it will show the "cpuid"...
Even if we do get the uid theres no guarantee it will fix the bootloader error - but we may as well explore all the options we can....
dibb_nz said:
USBDeview will only work when you have previously plugged your tab into the PC WHILE you were running HC Rom and BL
1. If you haven't plugged your tab into this pc before, do so now, before you run the program. HC ROM/BL ONLY
1a. Run the exe and you will be presented with a window of all the USB devices you have ever plugged into your computer.
2. Click on "VendorID" column along the top to sort them
3. Look for the number "0502" under Vendor ID AND "3325" Product ID
4. In the serial number column will be a 15-digit number this is your device ID.
5. Write the number down and put a 0 in front of it and now you have your CPU ID!!!
Click to expand...
Click to collapse

[Q] Recovery problems on Defy+ while updating to CM11

Hey!
I had CM10.2 on my Defy+, and tried to just follow Quarx simple post:
http://forum.xda-developers.com/showthread.php?t=2515036
I had some trouble with the update recovery (bad zip), reformatted my SD with sdcard.org's official formatting tool, and it worked.
The Quarx website seems to be down, so I downloaded the CM11 rom with the most recent date from http://defy.bytekiste.de/cm11-nightly-defy+/
Which is where I got the update-recovery as well, so I figured that would be fine.
Got a status 7 error (this package is for "MB526" but your device is ""), so I tried fiddling with the verification, editing the rom script (those few lines you have to delete), according to various topics on the status 7 subject. Nothing worked.
People in treads advice different recovery files, so I manually flashed TWRP from here:
http://teamw.in/project/twrp2/91
I rebooted into recovery again, an it just gives a blank (but lit) screen. I can still access the bootmenu, but not recovery, so I guess TWRP doesn't work with my phone. Should have read the comments on that downloadpage I guess... So I went on to find this "goomanager" people are talking about but all I get are dead links, so I tried the ROMManager and TWRPManager apps, but I can't find any reference to Defy+, Jordan or MB526 within those apps when they ask you to select a device.
I'm not an expert, so I was like, lets start all over from scratch to get recovery working again. Any recovery, I don't care. So I went back to:
http://wiki.cyanogenmod.org/w/Insta...alling_bootmenu_.26_the_ClockworkMod_Recovery
Which is what I used for when I bought the phone to get root, bootmenu & recovery through ADB from the windows command line.
I'm trying to follow that to at least recover the ICS recovery which I had, but I'm stuck there as well. When I switch USB from mass storage mode to "tools only", ADB disconnects, and when I leave it in mass storage mode, well, the sdcard is not mounted to the phone so I can't use ADB on it.
Can anyone give me a push in the right direction? Can I restore the update-recovery from Quarx CM11 thread somehow?

So I got adb to function (how, I do not know), ran the stuff here:
http://wiki.cyanogenmod.org/w/Insta...alling_bootmenu_.26_the_ClockworkMod_Recovery
Which gives me Bootmenu 0.6.1 (I had Bootmenu 2.0.0 before?). And it doesn't include a functional recovery, or a functional 2ndinit, so I completely (soft)bricked my phone now :laugh: Both recovery & boot give errors about missing sh scripts.
Soooo... I installed RSD Lite & motorola drivers with the intention of flashing a stock SBF.
http://forum.xda-developers.com/showthread.php?t=1618718
http://forum.xda-developers.com/showthread.php?t=1828639
Dead links, dead links everywhere.... sigh.

okdewit said:
Soooo... I installed RSD Lite & motorola drivers with the intention of flashing a stock SBF.
http://forum.xda-developers.com/showthread.php?t=1618718
http://forum.xda-developers.com/showthread.php?t=1828639
Dead links, dead links everywhere.... sigh.
Click to expand...
Click to collapse
Soooo, are you simply pointing out the fact that the links haven't been updated (or maybe expressing frustration), or are you saying that you didn't find the new location of the sbf files? The links do have a trail that lead to the new location of the sbf files -- yes, you have to go through several pages to get there and then you have to select the specific sbf that you want, but it's there (here for Defy: http://sbf.droid-developers.org/phone.php?device=27 or here for Defy+: http://sbf.droid-developers.org/phone.php?device=28).
Don't forget, these tutorials, as well as most everything on this forum, are written by people who freely (as in free beer) give of their time to help those of us that are less knowledgeable and therefore may not get updated in a timely manner or maybe not updated at all.
JimboN

JimboN said:
Soooo, are you simply pointing out the fact that the links haven't been updated (or maybe expressing frustration), or are you saying that you didn't find the new location of the sbf files? The links do have a trail that lead to the new location of the sbf files
Click to expand...
Click to collapse
Yesterday when I tried it, the whole droid-developers website just gave an Nginx server error, but I'm glad to see it's up again. Gonna load up RSDLite now and give it one last try!
JimboN said:
Don't forget, these tutorials, as well as most everything on this forum, are written by people who freely (as in free beer) give of their time to help those of us that are less knowledgeable and therefore may not get updated in a timely manner or maybe not updated at all.
JimboN
Click to expand...
Click to collapse
I fully realize that, it's mostly frustration with myself and a series of bad actions which led me to lock up my phone further and further with each action. I realized the risk in advance, so luckily I do have a full backup and a backup phone, but it still hurts a bit to see your beloved device dying on the operating table because of your own stupidity.

Sweet victory, I got froyo back at least! Thanks!
Now to tread very carefully...

okdewit said:
Sweet victory, I got froyo back at least! Thanks!
Now to tread very carefully...
Click to expand...
Click to collapse
Glad to hear you were successful.
Yep, know the frustration of my own stupid actions screwing up my phone and when you go to fix it, that don't work right either -- been there & done that.

Sweet victory #2: Now I have CM11 working! :laugh:
(using the SBF flash & the section in the guide for stock to kitkat: http://forum.xda-developers.com/showthread.php?t=2737990)
I've found one BIG culprit in my previous methodology: copying files through motorola phone portal is just plain wrong. I kept getting "bad zip" and other verification errors. Even by using the USB "Mass Storage" option in the stock Froyo rom the files didn't match exactly 1:1, at least not according to the checksums. It took multiple tries to copy the framaroot/2ndinit apk files to the SD card correctly, and the CM rom zip was just plainly impossible to get on there.
So for the rom itself I just mounted through "USB Mount" in TWRP recovery, It's copies way faster as well. I've also used the windows program Teracopy (for CRC checks) instead of the built-in windows explorer file copier. :good:
Thanks a lot for the support, if you had not pointed out that the SBF filehost was working fine again, this nice phone would've been thrown away.

okdewit said:
Sweet victory #2: Now I have CM11 working! :laugh:
(using the SBF flash & the section in the guide for stock to kitkat: http://forum.xda-developers.com/showthread.php?t=2737990)
Click to expand...
Click to collapse
Fantastic! CM11 works better for me than any other rom that i've tried (certainly smoother and probably faster), still has a few bugs but so did all the others. Best of all it's the latest android and can run all the latest apps.
okdewit said:
Even by using the USB "Mass Storage" option in the stock Froyo rom the files didn't match exactly 1:1, at least not according to the checksums. It took multiple tries to copy the framaroot/2ndinit apk files to the SD card correctly, and the CM rom zip was just plainly impossible to get on there.
Click to expand...
Click to collapse
Hmm... That's interesting. I've used USB Mass Storage to do just what you attempted to do without a problem -- good to know as a potential issue.
okdewit said:
So for the rom itself I just mounted through "USB Mount" in TWRP recovery, It's copies way faster as well.
Click to expand...
Click to collapse
Thanks for the tip.